8 Event notification
43
8.2.3.1
Trap OIDs
The type of a TRAP or INFORM is indicated by its OID. SNMPv2c and SNMPv3 include the full OID in the message;
SNMPv1 is different.
SNMPv1 traps are identified by the generic trap type (and correspond to the following trap OIDs):
• 0 — cold start (1.3.6.1.6.3.1.1.5.1),
• 1 — warm start (1.3.6.1.6.3.1.1.5.2),
• 2 — link down (1.3.6.1.6.3.1.1.5.3),
• 3 — link up (1.3.6.1.6.3.1.1.5.4),
• 4 — authentication failure (1.3.6.1.6.3.1.1.5.5),
• 5 — EGP neighbor loss (1.3.6.1.6.3.1.1.5.6).
If the generic trap type is 6, the trap is enterprise-specific (and is usually taken to correspond to OIDs using the
template "1.3.6.1.4.1.ENTERPRISE-OID.0.SPECIFIC-TRAP-TYPE").
Unless you send only generic traps or have a OID tree registered to you, you may want to send 'user-configured'
traps which carry no additional semantics other than the variable bindings. The
dlinGeneric
user-configured
trap type is designed for that. Its OID is 1.3.6.1.4.1.45770.0.1; this can be specified directly for SNMPv2c or SNM
←
-
Pv3, or as an enterprise-specific (generic trap type=6) DLI ("enterprise OID"=45770) trap #1 (specific trap type=1).
8.2.3.2
Security settings
SNMPv1 and SNMPv2c use the 'community' security model which essentially identifies users by a shared secret
which is sent over the network in plain text ('public' and 'private' being the most popular 'secrets'). That means
that they are very insecure and shouldn't be deployed over an untrusted network. SNMPv3 has a more reasonable
security model.
8.2.3.3
Variable bindings
All SNMP TRAPs and INFORMs accept the
snmp_values
event property to send extra values in the message.
The property, if not nil, must be an array of the following shape:
{{oid1,value1,type1},{oid2,value2,type2},...}
The order may be important; you may want to consult the MIB. The following types are supported:
• "integer",
• "unsigned",
• "counter32",
• "string",
• "hex string",
• "decimal string",
• "nullobj",
• "objid" or "oid",
• "timeticks",
• "ipaddress" or "ip",
• "bits".
Type names are case-insensitive. A type may be omitted, in that case it will be inferred (nil values will be encoded
as null objects, strings as octet strings, numbers as integers, "true" values as integer 1, and "false" values as integer
2 as per SMIv2).
DLI LPC9 User’s Guide: 1.7.24.0
Summary of Contents for LPC9
Page 1: ...DLI LPC9 User s Guide 1 7 24 0 ...
Page 81: ......
