| componentRowPointer |
.1.3.6.1.4.1.562.2.4.1.3.2.7.1 |
|
A pointer to the RowStatus variable of the component emitting
the alarm.
|
| componentName |
.1.3.6.1.4.1.562.2.4.1.3.2.7.2 |
|
The textual name of the component emitting the alarm in a format
suitable for use in commands entered on the `console'. It
includes the name of the node from which the alarm was
sent, as specified in `ModuleData nodeName'.
|
| eventTime |
.1.3.6.1.4.1.562.2.4.1.3.2.7.3 |
|
The date and time at which the alarmed event occurred.
|
| activeListStatus |
.1.3.6.1.4.1.562.2.4.1.3.2.7.4 |
|
The active alarm list status. This may be used by the
Manager to add (on receiving a set) and delete (on
receiving a clear) alarms from the alarm displays.
|
| severity |
.1.3.6.1.4.1.562.2.4.1.3.2.7.5 |
|
The severity of the alarm which should indicate what
priority that fixing this problem should be given. All
values are OSI-defined; refer to CCITT X.733/ISO 10164-4
for a more complete description.
|
| alarmType |
.1.3.6.1.4.1.562.2.4.1.3.2.7.6 |
|
The alarm type field as defined by OSI which is
used to indicate a broad category of what is wrong. The
first 6 values are OSI-defined; refer to CCITT X.733/ISO 10164-4
(for the first 5) and CCITT X.736/ISO 10164-4 (for the last)
for a more complete description.
The value 'operator' is used when an alarm is issued due to an
operator command. The values 'debug' and 'unknown' are for
compatibility with older switches and are used for debugging alarms and
for those which do not fit any of the above, respectively.
|
| probableCause |
.1.3.6.1.4.1.562.2.4.1.3.2.7.7 |
|
The probable cause for the alarm which usually qualifies
the Alarm Type field. Most values are OSI-defined; refer
refer to CCITT X.733 and X.736 (ISO 10164-4 and 10164-7) for a more
complete description.
|
| ntpIndex |
.1.3.6.1.4.1.562.2.4.1.3.2.7.8 |
|
An 8-digit code which is an index into an NTP to
provide more description of the alarm and possible actions to
take. The first 4 digits indicate a 'group' of alarms
(belonging to a particular subsystem or component, etc.). The last
4 digits are a subindex arbitrarily assigned by the application
which is responsible for them.
|
| commentData |
.1.3.6.1.4.1.562.2.4.1.3.2.7.9 |
|
Additional textual information for the network operator to use.
It contains only ASCII characters.
Note: The total number of bytes in commentData, operatorData,
and internalData may not exceed 750 bytes.
|
| notificationID |
.1.3.6.1.4.1.562.2.4.1.3.2.8.1 |
|
The notification Id of the alarm. The high-order byte is
the card number of the card from which this alarm originated.
The low-order 24 bits contain a sequence number which increases each
time an alarm is generated. Thus, this id provides a simple way of
uniquely identifying an alarm as well as the order in which alarms
are generated on a card. For cross-card ordering, one
would have to look at the time stamp (see dateAndTime).
|
| lpForHierClear |
.1.3.6.1.4.1.562.2.4.1.3.2.8.2 |
|
A pointer to the RowStatus variable of the Logical Processor
the component generating the alarm is running on. A component
generating an Alarm with `activeListStatus = set' can include
this variable in the Alarm. If the identified Logical Processor
generates a Hierarchical Clear Alarm, then it will clear the
Set Alarm.
|
| operatorData |
.1.3.6.1.4.1.562.2.4.1.3.2.8.3 |
|
Additional hexadecimal information for the network operator to
use. Note: The total number of bytes in commentData, operatorData,
and internalData may not exceed 750 bytes.
|
| pid |
.1.3.6.1.4.1.562.2.4.1.3.2.8.4 |
|
A string representation of the internal process id (Pid)
of the process which generated the alarm (for
internal use only). Note that it may or may not map to the
componentName field.
|
| fileName |
.1.3.6.1.4.1.562.2.4.1.3.2.8.5 |
|
An internal filename (for internal use only).
|
| fileLineNumber |
.1.3.6.1.4.1.562.2.4.1.3.2.8.6 |
|
An internal line number in the file (see filename)
referred to above (for internal use only).
|
| fileVersion |
.1.3.6.1.4.1.562.2.4.1.3.2.8.7 |
|
A version indicator of the file (filename) referred
to above (for internal use only).
|
| internalData |
.1.3.6.1.4.1.562.2.4.1.3.2.8.8 |
|
An additional internal hexadecimal information for
internal use only. Note: The total number of bytes in comment,
operator, and internal data may not exceed 750 bytes.
|
| cid |
.1.3.6.1.4.1.562.2.4.1.3.2.9.1 |
|
This is a Custom Identifier(CID) of the component which generated
the alarm
|
| criticalAlarm |
1 |
|
This trap is used to provide a real time indication of a critical Alarm
condition. The variables listed in the VARIABLES clause,
defined in the `mandatoryAlarmInfo' group are present
in all critical alarms. Additional variables as defined in
the 'optionalAlarmInfo' group may be included if appropriate.
|
| majorAlarm |
2 |
|
This trap is used to provide a real time indication of a major Alarm
condition. The variables listed in the VARIABLES clause,
defined in the `mandatoryAlarmInfo' group are present
in all major alarms. Additional variables as defined in
the 'optionalAlarmInfo' group may be included if appropriate.
|
| minorAlarm |
3 |
|
This trap is used to provide a real time indication of a minor Alarm
condition. The variables listed in the VARIABLES clause,
defined in the `mandatoryAlarmInfo' group are present
in all minor alarms. Additional variables as defined in
the 'optionalAlarmInfo' group may be included if appropriate.
|
| warningAlarm |
4 |
|
This trap is used to provide a real time indication of a warning Alarm
condition. The variables listed in the VARIABLES clause,
defined in the `mandatoryAlarmInfo' group are present
in all warning alarms. Additional variables as defined in
the 'optionalAlarmInfo' group may be included if appropriate.
|
| clearedAlarm |
5 |
|
This trap is used to provide a real time indication of a cleared
Alarm. The variables listed in the VARIABLES clause,
defined in the `mandatoryAlarmInfo' group are present
in all cleared alarms. Additional variables as defined in
the 'optionalAlarmInfo' group may be included if appropriate.
|
| indeterminateAlarm |
6 |
|
This trap is used to provide a real time indication of an indeterminate
Alarm condition. The variables listed in the VARIABLES clause,
defined in the `mandatoryAlarmInfo' group are present
in all indeterminate alarms. Additional variables as defined in
the 'optionalAlarmInfo' group may be included if appropriate.
|
