Alpha Technologies AlphaNet DSM Series DOCSIS - Manual (Page 42)

42 745-814-B0-001, Rev. A
6.0 Data Management, continued
6.3
SCTE-HMS MIB Alarms, continued
6.3.2 SNMP Alarm Traps, continued
Trap on Normal
The XP-DSM has the capability of sending a “return to normal” trap once an alarmed
condition returns to a normal state. This feature is disabled by default, but can be
enabled by setting the ‘TRAP ON NORMAL’ parameter in the atiCibDiscreteTable to
a value of ‘1’. 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).
Warm Start Trap
In addition to the SNMP alarm traps, the XP-DSM will also send a warm-start trap
when it is initialized. Some SNMP monitoring software requires this trap for auto-
identification of the transponder. 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
Cold Start Trap
A cold-start trap will be generated by the XP-DSM anytime it initializes with a new
firmware version. This trap should only appear after the first time the XP-DSM has
been reset during a firmware upgrade.
Varbind Explanation
Binding #1
commonPhysAddress
OID: 1.3.6.1.4.1.5591.1.3.2.7.0
MAC Address of the transponder
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 transponder 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-6, SNMP Alarm Trap Varbinds and Explanations