EasyManua.ls Logo

T-VIPS CP560 - Alarm Event Fields

T-VIPS CP560
200 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
148 SNMP
CP560 DVB-T2 Gateway User’s Manual Rev. 2.2 (3686) ID: um_t2gateway
9.5.3 Alarm event fields
A description of the fields in the alarm event traps is presented in Table 9.2. Most of the fields
are entries from the unitEventHistoryTable. The instance identifier for each variable binding
corresponds to the index in this table. This index is of kind CircularLog and will wrap around
at 2
32
.
Table 9.2 Variables in SNMPv2 traps and their meanings
Field Description
unitEventSeverity This field indicates the severity of the alarm, 2-6. 1 will never be used, as this condition is
indicated by transmitting a unitAlarmCleared message.
unitEventAlarmType This is an integer that describes the alarm type. Please refer to alarm documentation for
description. From this type, one can extract the actual meaning of the subid1 and subid2
values in the message.
unitEventAlarmId A unique identifier for this alarm type. Refer to alarm documentation in the user manual
for values.
unitEventAlarmName A fixed name corresponding to the alarm id.
unitEventRefNumber This field is provided to easily match asserted/cleared alarms. In the cleared alarm it is set
to the same number as in the asserted alarm.
unitEventSubId1 The first subidentifier to identify the source of the alarm. For products with single base
boards it is typically set to a fixed value (0 or 1) and can be ignored.
unitEventSubId2 This field’s purpose is dependent on the alarm type (alarm id). For some alarms it is not
used and set to zero. For other alarms, it may e.g. indicate the channel/port number for
the entity that generated the alarm.
unitEventSubId3 This field provide an even more detailed description of the alarm source. This field is only
present in the “detailed” type of trap messages (unitDetailedAlarmAsserted,
unitDetailedAlarmEvent). It’s usage is dependent on the alarm ID. For example, in
transport stream related alarms, subid3 is used to indicate the PID value that caused the
alarm.
unitEventSourceText A textual description of the source of the alarm. This is typically a textual description of
the subid1 and subid2 fields. For example, for transport stream related alarms, the text
indicates the name (with label) of the port that generated the alarm.
unitEventSubId3Label This field is fixed and indicates the label (meaning) of the subid3 field, contained in the
unitEventSubId3 variable. It is intended to make it easy to log the alarm.
unitEventDetails This is a generic text string that contains more details related to the alarm event. It’s
usage and content is dependent on the alarm ID.
unitAlarmStatus This variable contains the new, top level alarm status of the unit after the condition
leading to this trap messsage. It may be used to quickly update the top level status for the
device after receiving the trap message.

Table of Contents