SNMP 149
ID: um_t2gateway CP560 DVB-T2 Gateway User’s Manual Rev. 2.2 (3686)
9.5.4 Matching of on/off traps
As mentioned previously, a unitAlarmCleared message is sent after a unitAlarmAssert-
ed message and a unitDetailedAlarmCleared message is sent after a unitDetailedAlar-
mAsserted message.
The “cleared” event contains exactly the same identifiers as the “asserted” trap. This includes
the alarm ID, subid1, subid2 and subid3 fields. This set of four identifiers uniquely identifies
the source of an alarm.
A more easy way to match the traps is by using the unitEventRefNumber field. This is a
simple integer that is the same in an “asserted” trap and in a “clear” trap.
9.5.5 Legacy trap messages
Note: The information in this section relates to trap definitions that
are marked as deprecated in VIGW-UNIT-MIB. They are included for
backwards compatibility with earlier product versions and should not be
used for new deployments.
The legacy traps are defined under the vigwLegacyTraps node. Transmission of these traps is
specified by selecting “SNMPv1 (Legacy)” for the trap version field. The format of these traps
follow the SNMPv1 trap format.
In contrast to the SNMPv2 alarm messages, the SNMPv1 messages has its severity implicitly
encoded in the trap type.
The trap messages are defined in Table 9.3.
Table 9.3 List of legacy (SNMPv1) traps
alarmCleared This trap is sent when an alarm goes off (i.e. is cleared) in the system. The binding
unitTrapHistoryRefNumber matches the corresponding unitTrapHistoryRefNumber in
the “raise” trap message.
alarmIndeterminate This trap is sent when an alarm with severity level “notification” (level 2) is generated.
alarmWarning This trap is sent when an alarm with severity level “warning” is generated.
alarmMinor This trap is sent when an alarm with severity level “minor” is generated.
alarmMajor This trap is sent when an alarm with severity level “major” is generated.
alarmCritical This trap is sent when an alarm with severity level “critical” is generated.
All these trap messages contain variable bindings from the unitTrapHistoryTable. This table
is filled up with historical trap messages, only when SNMPv1 mode is selected.
The fields in these traps are fetched from the unitAlarmTrapHistoryTable. The meaning of
these fields correspond to the fields in the unitEventHistoryTable for SNMPv2 traps and are
not described in more detail here.
To Next Page
Loading...