Alpha Technologies DSM3 for XM2 - Technical Manual - Manual (Page 50)

50 745-814-B8-001, Rev. C (03/2014)
6.0 Data Management
6.2.2 SNMP Alarm Traps, continued
Trap on Normal
The DSM3 Series has the capability of sending a “return to normal” trap once an alarmed condition
returns to a normal state. This feature is enabled by default, but can be disabled by setting the
"TRAP ON NORMAL" parameter in the the MIB point atiMgmtSnmpTrapOnNormal to a value of "2".
The contents of this trap message will be identical to the SNMP Alarm traps, but the value of the
Alarm "Type" defined in the 5th varbind will be "1" (NOMINAL).
SCTE-HMS Warm-Start Trap
In addition to the SNMP alarm traps, the DSM3 Series will also send an SCTE-HMS warm-start
trap when it is initialized. Some SNMP monitoring software requires this trap for auto-identification
of the Communications Module. The format of this trap will be similar to the alarm trap, but the only
information sent will be:
commonTrapCommunityString, OID 1.3.6.1.4.1.5591.1.3.1.11.0
commonPhyAddress, OID, 1.3.6.1.4.1.5591.1.3.2.7
commonLogicalID, OID 1.3.6.1.4.1.5591.1.3.1.1.0
SCTE-HMS Cold-Start Trap
An SNMP-HMS cold-start trap will be generated by the DSM3 Series anytime it initializes with a
new firmware version. In addition, a cold start trap is sent whenever the DSM3 configuration has
changed. If any parameter in the HMS PROPERTY table has changed since the last reset, a
cold-start trap will be sent upon the next reset.
Varbind Explanation
Binding #1
commonPhysAddress
OID: 1.3.6.1.4.1.5591.1.3.2.7.0
MAC Address of the Communications Module
Binding #2
commonLogicalID
OID: 1.3.6.1.4.1.5591.1.3.1.1.0
Optional user-configurable parameter that is often used to provide a unique logical name, or even
the physical address of where the Communications Module is installed.
Binding #3
alarmLogInformation
OID: 1.3.6.1.4.1.5591.1.2.3.1.2.1
This varbind was designed by the SCTE-HMS committee with the intention of being used by
sophisticated trap interpreters. The information is “coded” within the octet strings:
Octet 1-4: POSIX Time of alarm occurrence (most significant byte first)
Octet 5: Alarm Type (See description below)
Octet 6: Contents of commonNeStatus immediately after alarm occurred
Octet 7-m: Alarm Object Identifier (BER encoded)
Octet n-z: Alarm value (BER encoded)
Most trap interpreters cannot decode this message, which is why varbinds 4 and 5 were added that
provide the same information in a more useable format.
Binding #4
Alarmed Parameter OID/Value
OID:
1.3.6.1.4.1.5591.1.4.2.1.27.1
This field provides the varbind of the parameter that is alarming along with the value of that
parameter. This is the same information encoded in varbind #3 Octets 7 through Z.
In the example above the value would be:
OID: 1.3.6.1.4.1.5591.1.4.2.1.27.1.0 (psTamper)
Value: 2 (Open)
Binding #5
Alarm Location/Type
OID: 1.3.6.1.4.1.5591.1.1.2.1.2
This is the information from varbind #3 Octet 5 above. The alarm location will always be the
SCTE-HMS currentAlarmAlarmState and the type will be determined based on how the alarm was
configured in the SCTE-HMS PropertyIdent MIB tables.
OID 1.3.6.1.4.1.5591.1.1.2.1.2.0 (currentAlarmAlarmState)
Type: 1-7 based on SCTE definitions:
1 NOMINAL
2 HIHI
3 HI
4 LO
5 LOLO
6 Discrete Major
7 Discrete Minor
The Type will be determined by how the alarm is configured in the SCTE-HMS PropertyIdent MIB,
whether it is a Discrete or Analog alarm and the level of alarm defined for that state.
Table 6-8, SNMP Alarm Trap Varbinds and Explanations