ERICSSON-ALARM-IRP-MIB: View SNMP OID List / Download MIB

This SNMP MIB-module constitutes the Ericsson Alarm Integration Reference Point (IRP) solution set for SNMP, version 1:2. The purpose of this IRP is to define an interface though which a 'system' (typically a network element manager or a network element) can communicate alarm information for its managed objects to one or several 'actors' (typically network management systems). An alarm is a kind of object that represents an abnormal condition for a managed object. An alarm is active as long as the corresponding abnormal condition remains. The system maintains an 'Alarm Table' containing all currently active alarms for its managed objects. When an alarm is cleared, it is removed from the list and no longer accessible. Alarms can be forwarded to the actors either synchronously (requested through get, get-next or get- bulk PDUs) or asynchrously (through inform or trap PDUs) whenever an entry in the Alarm Table is created, modified or cleared.

This object represents the version of the Alarm IRP SNMPv2 Solution Set supported by the agent. The format is 'xy', where 'x' is the version of the information model and 'y' the version of the solution set corresponding to this information model.

This object determines the number of currently active alarms with perceived severity 'indeterminate'.

This object determines the number of currently active alarms with perceived severity 'critical'.

This object determines the number of currently active alarms with perceived severity 'major'.

This object determines the number of currently active alarms with perceived severity 'minor'.

This object determines the number of currently active alarms with perceived severity 'warning'.

This object determines the total number of currently active alarms, i.e. the total number of entries in the Alarm Table.

Table with information about the alarms that are currently active in the system.

One entry in the table holds one current alarm.

This object uniquely identifies an entry in the Alarm Table. It increases every time a new alarm occurs. Due to cleared alarms the index will not be contiguous. When the maximum is reached of Integer32, the value of this object rolls over to 1. The actor must use 'alarmEventTime' to sort on chronological order. The alarmId object is read-only even though it is used as index in the Alarm Table. The reason is that this facilities a convenient way to extract the corresponding value from a notification where the object is included.

This object identifies the class of network resources to which the subject alarm is related.

This object identifies the instance (of a class) of network resource to which the subject alarm is related.

This object represents the time of occurrence of the subject alarm. If the alarm changes 'perceivedSeverity', then this object represents the time of the last severity change, else it represents the time carried in the original alarm emitted by the alarmed network resource. The time indication is in UTC (Co-ordinated Universal Time).

This object represents the type of event according to the ITU recommendations X.733/X.736.

This object represents the probable cause identification code (generic classification) for the subject alarm according to the ITU recommendations M.3100/X.733/X.736 and ETSI recommendation GSM 12.11.

This object represents the perceived severity of the subject alarm according to the ITU recommendation X.733. If the system changes the perceived severity of an existing alarm to a higher value, the corresponding 'alarmAckUser' and 'alarmAckTime' objects are cleared.

This object represents the specific problem identification code for the subject alarm. This is a more detailed (product specific) identification compared to the (generic) 'alarmprobableCause'.

This object is used to define the id of a user that acknowledge the subject alarm. An alarm can be unacknowledged by clearing this object. This object shall always be set or cleared in the same set request as the 'alarmAckTime' object defined below. The system will respond with 'inconsistentValue' upon attempts to set this object without setting 'alarmAckTime'.

This object represents the time when the subject alarm was acknowledged. This object shall always be set or cleared in the same set request as the 'alarmAckUser' object defined above. The system will respond with 'inconsistentValue' upon attempts to set this object without setting 'alarmAckTime'. The time indication is in UTC (Co-ordinated Universal Time).

This object is used to define the id of a user that enters a comment for the subject alarm. This object shall always be set in the same request as the 'alarmCommentText' object defined below. The system will respond with 'inconsistentValue' upon attempts to set this object without setting 'alarmCommentText'.

This object represents a comment added by an actor to the subject alarm. This object shall always be set in the same set request as the 'alarmCommentUser' object defined above. The system will respond with 'inconsistentValue' upon attempts to set this object without setting 'alarmAckUser'.

This object represents some arbitrary additional text for the subject alarm.

This object uniquely identifies a notification. It increases every time a new notification is sent. When the maximum is reached of Integer32, the value of this object rolls over to 1.

This notification is sent when a new Alarm is generated and stored in the Alarm Table. Note that the notification does not include all objects for the corresponding entry in the Alarm Table. The reason is that some environments may have problems with large PDUs. Thus, the notification receiver must get the missing objects from the Alarm Table.

This notification is generated when any of the attributes of an Alarm has changed. Note that the EventTime value in the notification will be different than that in the original notifyNewAlarm if and only if the alarmPerceivedSeverity value is different from that carried in original notifyNewAlarm. Note that the notification does not include all objects for the corresponding entry in the Alarm Table. The reason is that some environments may have problems with large PDUs. Thus, the notification receiver must get the missing objects from the Alarm Table.

This notification is generated when an alarm is cleared. A cleared alarm is removed from the Alarm Table and is no longer accessible.

A collection of objects that are required for compliance to the ALARM-IRP.

A collection of mandatory objects holding administrative information.

A collection of optional objects for retrieval of the number of currently active alarms.

A collection of objects that represents mandatory alarm attributes.

A collection of objects that represents optional alarm attributes.

A collection of mandatory alarm notifications.

A collection of optional alarm notifications.