Does DX NetOps use SNMP4J for SNMP traps?

[MARUBUN SUPPORT]

Hi Team,

 

 

Product

DX NetOps PM22.2.2

 

 

Question

 

EventManager Format Usage

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/22-2/using/configure-notifications/traps-usage.html

 

In the above document, it is possible to send SNMP traps using the trap notification action in EventManager, 

but could you please tell me whether or not SNMP4J is used for this operation?

 

 

MARUBUN Support,

[Jeffrey Pinard]

Yes, we use SNMP4j in EventManager to send traps via notifications.

We also use SNMP4j for all SNMP calls in the data collector.

[MARUBUN SUPPORT]

Do you have any information about the following?

 

SNMP trap sending process” in the log monitoring function stops 497 days after system startup.

Does this phenomenon also occur in DX NetOps?

“SNMP trap sending process” in the log monitoring function stops after 497 days after system startup.

 

-

The “org.snmp4j.mp.SnmpConstants.sysUpTime” is the operating time of the log monitoring process defined as a parameter of SNMP4J.

JavaDoc specified value “new org.snmp4j.smi.TimeTicks(long)”, but not the MAX value of long (9223372036854775807),

If the value is set beyond the UnsignedInteger MAX value (4294967295),

SNMP4J would throw an exception “throw new IllegalArgumentException(”Argument must be an unsigned 32bit value“)”.

The SNMP trap sending process (thread) in the log monitoring function was terminated when the exception occurred.

-

[Jeffrey Pinard]

SNMP trap sending process” in the log monitoring function stops 497 days after system startup.
Does this phenomenon also occur in DX NetOps?
“SNMP trap sending process” in the log monitoring function stops after 497 days after system startup.
 
-
The “org.snmp4j.mp.SnmpConstants.sysUpTime” is the operating time of the log monitoring process defined as a parameter of SNMP4J.
JavaDoc specified value “new org.snmp4j.smi.TimeTicks(long)”, but not the MAX value of long (9223372036854775807),
If the value is set beyond the UnsignedInteger MAX value (4294967295),
SNMP4J would throw an exception “throw new IllegalArgumentException(”Argument must be an unsigned 32bit value“)”.
The SNMP trap sending process (thread) in the log monitoring function was terminated when the exception occurred.
-

Event Manager, where SNMP4j is used, will not be up for 497 days nor will it reach 4294967295 timeticks which is 1.36 years, as you will have upgraded the product much sooner to get security fixes, new features and bug fixes.  :)   

But I see no mention of either of these bugs being fixed in release notes for 1.0 to 2.8.x.