How is a SNMPv1 trap OID constructed?

55 viewsSNMP traps snmpv1
1
0 Comments

Hi everyone,

I need help to confirm that my protocol.xml to process snmpv1 traps is correct.

Is it correct that for snmpv1 traps, DataMiner will automatically detect that if incoming snmpv1 trap has data:

generic-trap = 6 (enterpriseSpecific)
enterprise   = 1.3.6.1.4.1.1773.1.1.9
specific-trap= x

Would the expected trapOID to match be 1.3.6.1.4.1.1773.1.1.9.0.x?

Is this documented anywhere as this is not trivial?

Paulo Henriques [SLC] [DevOps Advocate] Answered question

1 Answer

2
1.66K 0 Comments

Yes, your understanding is correct.

For an SNMPv1 trap with:

  • generic-trap = 6 (enterpriseSpecific)
  • enterprise = 1.3.6.1.4.1.1773.1.1.9
  • specific-trap = x

DataMiner will translate this to the OID: 1.3.6.1.4.1.1773.1.1.9.0.x

This follows the RFC 2576 conversion rule: enterprise + ".0." + specific-trap.

In your protocol.xml, you'd match it like:

<!-- For a specific trap (x = 5): -->
<TrapOID type="complete">1.3.6.1.4.1.1773.1.1.9.0.5</TrapOID>

<!-- Or catch all traps from this enterprise: -->
<TrapOID type="wildcard">1.3.6.1.4.1.1773.1.1.9.0.*</TrapOID>

Is it documented? Not explicitly for SNMPv1 in DataMiner's own docs: the Traps connector guide and TrapOID schema docs show examples but don't call out the SNMPv1 -> OID conversion rule directly. The underlying behavior is standard per RFC 2576 §3 (SNMPv1↔v2 translation), which DataMiner follows internally.

Paulo Henriques [SLC] [DevOps Advocate] Edited answer