It is a question about receiving snmptrap.

[Med]

Hello!

There is a device that can send traps of version v1 or v2c or Inform of snmp in the monitoring target and it is set to trap in the trap of the current v1, so it can receive without problems and an event has occurred.
If you trap this setting with v2c trap or Infom, you can receive but it will be SNMP_UNMATCH_TRAP.
Do I need to change the setting of NetXMS?

OS Version: Windows2012 (64bit)
NetXMS Version: 2.2.6

Thank you.

[victor]

Hi,

it should not be version dependent. Could you take screenshot or export your SNMP trap configuration and provide example of actual trap received and incorrectly matched?

Best regards,
Victor

[Med]

Hi,

Thank you for the immediate reply.
Attach the setting and the log when actually generating the trap.

DiChangeValue.xml: Corresponding Event and SnmpTrap Configuration.
EventLog.csv: Event log when tasting in execution.
SnmpTrapLog.csv: Event log when tasting in execution.

I tested in the following order.
V1Trap -> DiChangeValue1 * OK *
V1Trap -> DiChangeValue 0 * OK *
V2Trap -> DiChangeValue1 * NG *
V2Trap -> DiChangeValue 0 * NG *
Inform -> DiChangeValue 1 * NG *
Inform -> DiChangeValue 0 * NG *

Thank you.

---

DiChangeValue.xml

EventLog.csv

SnmpTrapLog.csv

[victor]

Hi,

it seems that trap OID is different for version 1 and versions 2-3. For version 1 it is .1.3.6.1.4.1.2589.1.2.0.8 and version 2 it is .1.3.6.1.4.1.2589.1.2.8
 (no .0 before last element). I'm not sure if it is NetXMS bug in parsing trap PDUs or device bug - will check that further. Anyway you just need to create second mapping with v2/3 OID and it will work.

Best regards,
Victor

[Med]

Hi,

When notifying with V2c and Inform, we confirmed with the manufacturer that it is notified with OID different from V1.

Sorry.
Thank you very much for pointing out.