See also Documentation and Use of the Ericsson
SNMP Alarm MIB, Document number EAB/OP-07:0139.
This MIB Module is an Ericsson-wide SNMP
interface for managing alarms. Main inputs to
the MIB design are the 3GPP Alarm IRP and X.733.
However, an important restriction is that the MIB
only represents the resource view and not
management activities like acknowledgment, etc.
It describes generic notifications used to send
alarm state changes and a table which represents
the current active alarms in the system. The MIB
supports both stateful alarms and stateless
alarms (that have no clear notification).
Stateless alarms are called alerts.
It is important to identify clearly what is to be
considered the same alarm object instance. All
unique alarm *types* are identified by
'AlarmType'. An AlarmType is a one-to-one
mapping with X.733 EventType, ProbabableCause and
SpecificProblem. A pair of integers are used to
specify the alarm type.
A unique alarm object *instance* is the
combination of managed object and AlarmType. In
this way there, is no ambiguity about how alarm
and alarm clear correlation should be performed:
the same managed object instance and AlarmType
shall be used. The same is true for changing
existing alarm states. Severity and
additionalText can be changed on an existing
alarm.
For stateful alarms there are notifications to
report a new alarm and a cleared alarm. Changing
an alarm is done via the new alarm notification.
The management system shall match the alarm by
using alarm type and managed object instance in
the same way as for clear notifications.
The MIB has different notifications for different
severities in order to support SNMP managers
which maps severities based on notification
identifiers. For stateless alarms, there are
generic notifications to send the alarm raise
with different severities.
A table lists all active alarms so that a manager
can read an initial state and also perform an
alarm resynchronization procedure. There is also
a table of latest stateless alarms. Since the
stateless alarms do not have a corresponding
clear message, the table size is limited by the
agent instrumentation.
The MIB supports two approaches for detecting
lost notifications:
- sequence numbers are used in the alarm
notifications, and are shown in the active
alarm table. The last used sequence number can
be read in a scalar variable
- a time stamp indicates the last time alarm
tables where updated.
Heartbeat mechanisms are supported both in pull
and push mode:
- Pull: the classical SNMP polling where a
manager polls a scalar variable, for example
the last sequence number used
- Push: the agent can be configured to send
heartbeat notifications. These contains the
last used sequence numbers.
Document number: 5/196 03-CXC 172 7549, Rev A
ication is sent when a resource
detects a new alarm state with severity
indeterminate. The notification is also used to
change severity and/or additional text of an
alarm. The combination of ManagedObject and
MajorType/MinorType is always unique and can be
used by management systems to correlate alarm,
alarm change, and alarm clear. A corresponding
row will be created in the Alarm Table. The
sequence number will increase for every
notification and can be used to detect lost
notifications.
A management system should be prepared for
appending text to additional text, indicated by
the eriAlarmNObjMoreAdditionalText varbind, and
sent with eriAlarmAppendInfo. (Note do not
confuse this with a change of additional text.)
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
eriAlarmIndAlert
.1.3.6.1.4.1.193.183.4.2.0.10
ication is sent when a resource
detects a new alert with severity indeterminate.
A corresponding row will be created in the Alert
Table. The sequence number will increase for
every notification and can be used to detect lost
notifications.
eriAlarmWarnAlert
.1.3.6.1.4.1.193.183.4.2.0.11
ication is sent when a resource
detects a new alert with severity warning. A
corresponding row will be created in the Alert
Table. The sequence number will increase for
every notification and can be used to detect lost
notifications.
eriAlarmMinorAlert
.1.3.6.1.4.1.193.183.4.2.0.12
ication is sent when a resource
detects a new alert with severity minor. A
corresponding row will be created in the Alert
Table. The sequence number will increase for
every notification and can be used to detect lost
notifications.
eriAlarmMajorAlert
.1.3.6.1.4.1.193.183.4.2.0.13
ication is sent when a resource
detects a new alert with severity major. A
corresponding row will be created in the Alert
Table. The sequence number will increase for
every notification and can be used to detect lost
notifications.
eriAlarmCriticalAlert
.1.3.6.1.4.1.193.183.4.2.0.14
ication is sent when a resource
detects a new alert with severity critical. A
corresponding row will be created in the Alert
Table. The sequence number will increase for
every notification and can be used to detect lost
notifications.
eriAlarmAppendAlertInfo
.1.3.6.1.4.1.193.183.4.2.0.15
ication is sent in order to append
further info to an existing alert. It might be
additional text or a resource ID (OID)
identifying the alarming resource using an OID.
This complements information sent in a previous
notification.
If additional text is sent, do not confuse this
with an actual change of additional text which is
reported using the eriAlarmAlert
notification.
A zero-length string value for
eriAlarmNObjAdditionalText means that no
additional text is being sent in this
notification.
A null OID (0.0) value for
eriAlarmAlertResourceId means that no resource
ID is being sent in this notification.
eriAlarmWarning
.1.3.6.1.4.1.193.183.4.2.0.2
ication is sent when a resource
detects a new alarm state with severity warning.
The notification is also used to change severity
and/or additional text of an alarm. The
combination of ManagedObject and
MajorType/MinorType is always unique and can be
used by management systems to correlate alarm,
alarm change, and alarm clear. A corresponding
row will be created in the Alarm Table,
(eriAlarmActiveAlarmTable). The sequence number
will increase for every notification and can be
used to detect lost notifications.
A management system should be prepared for
appending text to additional text, indicated by
the eriAlarmNObjMoreAdditionalText varbind, and
sent with eriAlarmAppendInfo. (Note do not
confuse this with a change of additional text.)
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
eriAlarmHeartBeatNotif
.1.3.6.1.4.1.193.183.4.2.0.20
heartbeat notification with interval
according to the eriAlarmHbInterval. It contains
the last sequence numbers used for alarms and
alarm events. These varbinds can be used to
detect lost notifications.
The notification eriAlarmHeartBeatNotif will be
sent every eriAlarmHbInterval. Managers can
subscribe to the notification using the SNMP
framework MIBS by using the snmpNotifyName
'heartbeat'. (SNMP-NOTIFICATION-MIB,
snmpNotifyTable).
eriAlarmMinor
.1.3.6.1.4.1.193.183.4.2.0.3
ication is sent when a resource
detects a new alarm state with severity minor.
The notification is also used to change severity
and/or additional text of an alarm. The
combination of ManagedObject and
MajorType/MinorType is always unique and can be
used by management systems to correlate alarm,
alarm change, and alarm clear. A corresponding
row will be created in the Alarm Table,
(eriAlarmActiveAlarmTable). The sequence number
will increase for every notification and can be
used to detect lost notifications.
A management system should be prepared for
appending text to additional text, indicated by
the eriAlarmNObjMoreAdditionalText varbind, and
sent with eriAlarmAppendInfo. (Note do not
confuse this with a change of additional text.)
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
eriAlarmAlarmListRebuilt
.1.3.6.1.4.1.193.183.4.2.0.30
ication is sent when the active alarm
list has reached a stable situation after a
restart or after a system internal audit process.
It is an indication to the manager to perform a
alarm resynchronization procedure.
eriAlarmMajor
.1.3.6.1.4.1.193.183.4.2.0.4
ication is sent when a resource
detects a new alarm state with severity major.
The notification is also used to change severity
and/or additional text of an alarm. The
combination of ManagedObject and
MajorType/MinorType is always unique and can be
used by management systems to correlate alarm,
alarm change, and alarm clear. A corresponding
row will be created in the Alarm Table,
(eriAlarmActiveAlarmTable). The sequence number
will increase for every notification and can be
used to detect lost notifications.
A management system should be prepared for
appending text to additional text, indicated by
the eriAlarmNObjMoreAdditionalText varbind, and
sent with eriAlarmAppendInfo. (Note do not
confuse this with a change of additional text.)
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
eriAlarmCritical
.1.3.6.1.4.1.193.183.4.2.0.5
ication is sent when a resource
detects a new alarm state with severity critical.
The notification is also used to change severity
and/or additional text of an alarm. The
combination of ManagedObject and
MajorType/MinorType is always unique and can be
used by management systems to correlate alarm,
alarm change, and alarm clear. A corresponding
row will be created in the Alarm Table,
(eriAlarmActiveAlarmTable). The sequence number
will increase for every notification and can be
used to detect lost notifications.
A management system should be prepared for
appending text to additional text, indicated by
the eriAlarmNObjMoreAdditionalText varbind, and
sent with eriAlarmAppendInfo. (Note do not
confuse this with a change of additional text.)
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
eriAlarmCleared
.1.3.6.1.4.1.193.183.4.2.0.7
ication is sent when a resource
detects a cleared alarm state. The combination
of ManagedObject and MajorType/MinorType is
always unique and shall be used by management
systems to correlate alarm and alarm clear. The
corresponding row in the alarm table will be
deleted, (eriAlarmActiveAlarmTable). The
sequence number will increase for every
notification and can be used to detect lost
notifications. A management system should be
prepared for appending text to additional text,
indicated by the eriAlarmNObjMoreAdditionalText
varbind, and sent with eriAlarmAppendInfo.
(Note do not confuse this with a change of
additional text).
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
A management system should also be prepared to
receive a resource ID (OID) identifying the
alarming resource if the system sending the
notification can provide that information. In
that case, eriAlarmNObjResourceId will be set to
'true' and the resource ID will be sent in an
eriAlarmAppendInfo notification.
eriAlarmAppendInfo
.1.3.6.1.4.1.193.183.4.2.0.8
ication is sent in order to append
further info to an existing alarm. It might be
additional text or a resource ID (OID)
identifying the alarming resource using an OID.
If additional text is sent, do not confuse this
with an actual change of additional text which is
reported using the eriAlarm
notification.
A zero-length string value for
eriAlarmNObjAdditionalText means that no
additional text is being sent in this
notification.
A null OID (0.0) value for
eriAlarmActiveResourceId means that no resource
ID is being sent in this notification.
ericssonAlarmMIB 
eriAlarmSumIndeterminate 
eriAlarmActiveAlarmTable 
eriAlarmActiveAlarmEntry 
eriAlarmActiveIndex 
eriAlarmIndeterminate