MIBs Depot

ERICSSON-ALARM-MIB

Registered at
1.3.6.1.4.1.193.183.4
Last updated
2021-06-16 00:00
Organization
Ericsson AB
Revisions
2021-06-16 00:00, 2021-02-04 00:00, 2017-08-11 00:00, 2017-05-19 00:00, 2017-04-13 00:00, 2016-06-24 00:00, 2008-10-17 00:00
Namespace
ericsson
Source file
ERICSSON-ALARM-MIB
Digest
sha256:29d14df63b17c5b7d95b6e9bc076fcd821ce7efe497148c12d27a423401ff006

Description

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 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, Additional Text and Additional Info 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 alerts, there are generic notifications to send the alerts with different severities. NOTE - Updated Definition of Alerts in TEA (The Ericsson Architecture): Alerts are used by service management systems to evaluate service impact, and are only applicable to very specific state changes with potential service impact like restart and redundancy shifts. Alerts SHALL NOT be used for fault indication. Alerts should always have Perceived Severity Indeterminate, and should only be sent using eriAlarmIndAlert notification. The other severity alert notifications should not be used, and are only present in this specification for backward compatibility reasons. 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 alerts. Since the stateless alerts 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 were 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.

Contact

IMF

Imports

FromSymbols
ALARM-MIBResourceId
ERICSSON-ALARM-PC-MIBEriProbableCause
ERICSSON-ALARM-TC-MIBEriAdditionalInfo, EriAdditionalText, EriAlarmIndex, EriAlarmRecordType, EriAlarmSequenceNumber, EriAlarmSourceIdentifierType, EriAlarmSpecificProblem, EriAlarmType, EriAppendedAdditionalInfo, EriLargeAdditionalInfo, EriLargeAdditionalText
ERICSSON-TC-MIBEriMO
ERICSSON-TOP-MIBericssonModules
IANA-ITU-ALARM-TC-MIBIANAItuEventType
ITU-ALARM-TC-MIBItuPerceivedSeverity
SNMP-FRAMEWORK-MIBSnmpAdminString
SNMP-NOTIFICATION-MIBsnmpNotifyGroup
SNMP-TARGET-MIBsnmpTargetBasicGroup
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIGauge32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso
SNMPv2-TCDateAndTime, DisplayString, TEXTUAL-CONVENTION, TruthValue

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

ALARM-MIB
ERICSSON-ALARM-MIB
ERICSSON-ALARM-PC-MIB
ERICSSON-ALARM-TC-MIB
ERICSSON-TC-MIB
ERICSSON-TOP-MIB
IANA-ITU-ALARM-TC-MIB
IANAifType-MIB
IF-MIB
INET-ADDRESS-MIB
ITU-ALARM-TC-MIB
RFC1158-MIB
RFC1271-MIB
RMON-MIB
RMON2-MIB
SNMP-FRAMEWORK-MIB
SNMP-NOTIFICATION-MIB
SNMP-TARGET-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC
TOKEN-RING-RMON-MIB

Objects

NameOIDSyntaxAccessStatus
eriAlarmObjects
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.1
eriAlarmSummary
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.1.1
eriAlarmSumIndeterminate
OBJECT-TYPE
This object shows the number of currently active alarms with perceived severity 'indeterminate'. Note that only stateful alarms are included.
1.3.6.1.4.1.193.183.4.1.1.1Gauge32read-onlycurrent
eriAlarmSumCritical
OBJECT-TYPE
This object shows the number of currently active alarms with perceived severity 'critical'. Note that only stateful alarms are included.
1.3.6.1.4.1.193.183.4.1.1.2Gauge32read-onlycurrent
eriAlarmSumMajor
OBJECT-TYPE
This object shows the number of currently active alarms with perceived severity 'major'. Note that only stateful alarms are included.
1.3.6.1.4.1.193.183.4.1.1.3Gauge32read-onlycurrent
eriAlarmSumMinor
OBJECT-TYPE
This object shows the number of currently active alarms with perceived severity 'minor'. Note that only stateful alarms are included.
1.3.6.1.4.1.193.183.4.1.1.4Gauge32read-onlycurrent
eriAlarmSumWarning
OBJECT-TYPE
This object shows the number of currently active alarms with perceived severity 'warning'. Note that only stateful alarms are included.
1.3.6.1.4.1.193.183.4.1.1.5Gauge32read-onlycurrent
eriAlarmNotifObjects
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.1.2
eriAlarmNObjAdditionalText
OBJECT-TYPE
This is a scalar variable only used in notifications. It is size ranged with a smaller size than the corresponding type used in the active alarm table. This is in order to make sure that all alarm information will fit into one UDP packet. The additional text can be further appended by using the dedicated append notification.
1.3.6.1.4.1.193.183.4.1.2.1EriAdditionalTextaccessible-for-notifycurrent
eriAlarmNObjMoreAdditionalText
OBJECT-TYPE
This is a scalar variable only used in notifications. It tells the management system that the additional text will be appended by subsequent append additional text notifications. NOTE: this object exists simply because of the limitations of PDU size inherent in SNMP over UDP, which limits the size of the PDU+headers to under 1500 octets. Otherwise, the notification will be fragmented.
1.3.6.1.4.1.193.183.4.1.2.2TruthValueaccessible-for-notifycurrent
eriAlarmNObjResourceId
OBJECT-TYPE
This is a scalar variable only used in notifications. It tells the management system that there is an SNMP-based Resource ID (OID) that identifies the alarming resource. NOTE: this object exists simply because of the limitations of PDU size inherent in SNMP over UDP, which limits the size of the PDU+headers to under 1500 octets. Otherwise, the notification will be fragmented.
1.3.6.1.4.1.193.183.4.1.2.3TruthValueaccessible-for-notifycurrent
eriAlarmNObjAdditionalInfo
OBJECT-TYPE
This is a scalar variable only used in notifications. It is size ranged with a smaller size than the corresponding type used in the active alarm table. This is in order to make sure that all alarm information will fit into one UDP packet. The additional info can be further appended by using the dedicated append notification.
1.3.6.1.4.1.193.183.4.1.2.4EriAdditionalInfoaccessible-for-notifycurrent
eriAlarmNObjMoreAdditionalInfo
OBJECT-TYPE
This is a scalar variable only used in notifications. It tells the management system that the additional info will be appended by subsequent append additional info notifications. NOTE: this object exists simply because of the limitations of PDU size inherent in SNMP over UDP, which limits the size of the PDU+headers to under 1500 octets. Otherwise, the notification will be fragmented.
1.3.6.1.4.1.193.183.4.1.2.5TruthValueaccessible-for-notifycurrent
eriAlarmNObjRecordType
OBJECT-TYPE
This is a scalar variable only used in notifications. It tells the management system whether the alarm record being reported in the notification represents a new alarm instance or an update of an existing alarm instance.
1.3.6.1.4.1.193.183.4.1.2.6EriAlarmRecordTypeaccessible-for-notifycurrent
eriAlarmNObjAppendedAdditionalInfo
OBJECT-TYPE
This scalar variable is used for spillover of the additional info in the append trap.
1.3.6.1.4.1.193.183.4.1.2.7EriAppendedAdditionalInfoaccessible-for-notifycurrent
eriAlarmNObjSourceIdentifierType
OBJECT-TYPE
This is a scalar variable only used in notifications. It tells the management system the type of Identifier for the Source that raised the notification. This is needed for deployments where the Source IP Address of the IP packet does not reflect the original source of the alarm.
1.3.6.1.4.1.193.183.4.1.2.8EriAlarmSourceIdentifierTypeaccessible-for-notifycurrent
eriAlarmNObjSourceIdentifier
OBJECT-TYPE
This is a scalar variable only used in notifications. It tells the management system the Identifier for the Source that raised the notification. This is needed for deployments where the Source IP Address of the IP packet does not reflect the original source of the alarm.
1.3.6.1.4.1.193.183.4.1.2.9SnmpAdminStringaccessible-for-notifycurrent
eriAlarmActiveAlarms
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.1.3
eriAlarmActiveNumber
OBJECT-TYPE
This object shows the total number of currently active alarms, i.e. the total number of entries in the Alarm Table.
1.3.6.1.4.1.193.183.4.1.3.1Unsigned32read-onlycurrent
eriAlarmActiveLastChanged
OBJECT-TYPE
A timestamp when the active alarm table was last changed. The value can be used by a manager to initiate an alarm resynchronization procedure. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long.
1.3.6.1.4.1.193.183.4.1.3.2DateAndTimeread-onlycurrent
eriAlarmActiveLastSequenceNo
OBJECT-TYPE
The last used sequence number for a alarm state change notification. A management system can poll this variable in order to detect lost alarm change notifications.
1.3.6.1.4.1.193.183.4.1.3.3EriAlarmSequenceNumberread-onlycurrent
eriAlarmActiveTableURL
OBJECT-TYPE
A URL pointing to a location where the contents of the alarm table can be retrieved as a file. The actual format of the file is out of the scope of this MIB and can be found in the system documentation. A Uniform Resource Locator in accordance with RFC 4248. A string of length zero means that the agent does not have a URL to provide.
1.3.6.1.4.1.193.183.4.1.3.4SnmpAdminStringread-onlycurrent
eriAlarmActiveAlarmTable
OBJECT-TYPE
This table list all active alarms in the system. The aspect is the resource view of the alarms, not the administrative states and processes performed by users. The number of entries, active alarms, can be read in eriAlarmActiveNumber. Entries are created when a resource has a new alarm state. If the same resource has several active alarms, with different Alarm Types, this will be represented as separate rows. Rows disappear whenever the alarm is cleared in the resource. Rows can be changed when an alarm changes severity, additional text or additional info. Alarms where the clear state cannot be detected by the resource are not represented in this table. The contents of the active alarm table can also be fetched using file transfer. eriAlarmActiveTableURL provides a URL to the file.
1.3.6.1.4.1.193.183.4.1.3.5not-accessiblecurrent
eriAlarmActiveAlarmEntry
OBJECT-TYPE
One entry in the table holds one active alarm for a given resource. Entries are created by the system when a resource has a new alarm state. Entries are deleted by the system when a resource alarm state is cleared. Alarm severity, additional text and additional info can later be changed in a row.
1.3.6.1.4.1.193.183.4.1.3.5.1not-accessiblecurrent
eriAlarmActiveIndex
OBJECT-TYPE
A unique value, greater than zero, for each alarm. It is recommended that values are assigned contiguously starting from 1. The value for each alarm must remain constant at least from one re-initialization of the entity to the next re-initialization. Note that this index should not be used for alarm synchronization purposes since the 'logical' index for an alarm is - eriAlarmActiveMajorType - eriAlarmActiveMinorType - eriAlarmActiveManagedObject
1.3.6.1.4.1.193.183.4.1.3.5.1.1EriAlarmIndexnot-accessiblecurrent
eriAlarmActiveMajorType
OBJECT-TYPE
In combination with eriAlarmActiveMinorType, this provides a unique identification of the fault type. Different managed object types and instances can share alarm types, but if the same managed object reports the same alarm type, it is to be considered as the same alarm state. The alarm type is a simplification of the different X.733 and 3GPP alarm IRP alarm correlation mechanisms based on EventType, ProbableCause, SpecificProblem and NotificationId. For systems where eriAlarmActiveMajorType is not needed for identification purposes, it is not used and MUST be zero-valued.
1.3.6.1.4.1.193.183.4.1.3.5.1.2EriAlarmTyperead-onlycurrent
eriAlarmActiveMinorType
OBJECT-TYPE
In combination with with eriAlarmActiveMajorType, this provides a unique identification of the fault type, not including the managed object. Different managed object types and instances can share alarm types, but if the same managed object reports the same alarm type it is to be considered as the same alarm state. The alarm type is a simplification of the different X.733 and 3GPP alarm IRP alarm correlation mechanisms based on EventType, ProbableCause, SpecificProblem and NotificationId.
1.3.6.1.4.1.193.183.4.1.3.5.1.3EriAlarmTyperead-onlycurrent
eriAlarmActiveSpecificProblem
OBJECT-TYPE
This is a clear-text unique identification of the alarm type. There is a one-to-one mapping between eriAlarmActiveSpecificProblem and [eriAlarmActiveMajorType,eriAlarmActiveMinorType]
1.3.6.1.4.1.193.183.4.1.3.5.1.4EriAlarmSpecificProblemread-onlycurrent
eriAlarmActiveManagedObject
OBJECT-TYPE
The 3GPP naming convention shall be used as format for the managed object parameter. Note that the granularity must be good enough to guarantee unique alarm states and relevant resource identification to the operator. NOTE: The DN should be *relative* to the nodes *own* root.
1.3.6.1.4.1.193.183.4.1.3.5.1.5EriMOread-onlycurrent
eriAlarmActiveEventType
OBJECT-TYPE
The event type as defined in X.733/X.736.
1.3.6.1.4.1.193.183.4.1.3.5.1.6IANAItuEventTyperead-onlycurrent
eriAlarmActiveEventTime
OBJECT-TYPE
A time stamp of the alarm state change event. Note that this variable represents the last change of the alarm state, like changed severity, additional text/info. If the alarm has not changed state this variable represents the alarm raise time and will be the same as originalEventTime. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long.
1.3.6.1.4.1.193.183.4.1.3.5.1.7DateAndTimeread-onlycurrent
eriAlarmActiveOriginalEventTime
OBJECT-TYPE
The time-stamp of the original alarm raise notification. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long.
1.3.6.1.4.1.193.183.4.1.3.5.1.8DateAndTimeread-onlycurrent
eriAlarmActiveProbableCause
OBJECT-TYPE
The probable cause for the alarm originally defined by X.733 and subsequent standards. See also the ERICSSON-ALARM-PC-MIB. Due to the history of problems in maintaining a standardized probable cause the probable cause is not unique. A best effort mapping of the alarm to existing probable causes are used.
1.3.6.1.4.1.193.183.4.1.3.5.1.9EriProbableCauseread-onlycurrent
eriAlarmActiveSeverity
OBJECT-TYPE
The severity of the alarm as defined by X.733. Note that this may not be the original severity since the alarm may have changed severity.
1.3.6.1.4.1.193.183.4.1.3.5.1.10ItuPerceivedSeverityread-onlycurrent
eriAlarmActiveOriginalSeverity
OBJECT-TYPE
The original severity as reported by the alarm raise notification.
1.3.6.1.4.1.193.183.4.1.3.5.1.11ItuPerceivedSeverityread-onlycurrent
eriAlarmActiveAdditionalText
OBJECT-TYPE
A user friendly text describing the alarm. The text is both static depending on the alarm type (probable cause), and dynamic depending on managed object instance and other conditions. This string is longer than the corresponding varbind in the notification in order to manage large strings.
1.3.6.1.4.1.193.183.4.1.3.5.1.12EriLargeAdditionalTextread-onlycurrent
eriAlarmActiveOrigAdditionalText
OBJECT-TYPE
A user-friendly text describing the alarm. The text is both static depending on the alarm type (probable cause), and dynamic depending on managed object and other conditions. This is the original text as reported by the first alarm notification, after which it is not altered.
1.3.6.1.4.1.193.183.4.1.3.5.1.13EriLargeAdditionalTextread-onlycurrent
eriAlarmActiveResourceId
OBJECT-TYPE
In case the alarm refers to an object which is instrumented by SNMP this variable indicates the corresponding OID for the managed object.
1.3.6.1.4.1.193.183.4.1.3.5.1.14ResourceIdread-onlycurrent
eriAlarmActiveAdditionalInfo
OBJECT-TYPE
Additional Information for the alarm, structured in a way that is suitable for machine to machine communication. This string is longer than the corresponding varbind in the notification in order to manage large strings.
1.3.6.1.4.1.193.183.4.1.3.5.1.15EriLargeAdditionalInforead-onlycurrent
eriAlarmAlerts
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.1.4
eriAlarmAlertNumber
OBJECT-TYPE
The number of rows in the alert table.
1.3.6.1.4.1.193.183.4.1.4.1Unsigned32read-onlycurrent
eriAlarmAlertLastChanged
OBJECT-TYPE
A timestamp when the alert table was last changed. Can be used by a manager to initiate a an update of alerts procedure. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long.
1.3.6.1.4.1.193.183.4.1.4.2DateAndTimeread-onlycurrent
eriAlarmAlertLastSequenceNo
OBJECT-TYPE
The last sequence number used in alert notifications. This can be used to detect a lost notification.
1.3.6.1.4.1.193.183.4.1.4.3EriAlarmSequenceNumberread-onlycurrent
eriAlarmAlertTableURL
OBJECT-TYPE
A URL pointing to a location where the contents of alert table can be retrieved as a file. The format of the file is out of the scope of this MIB and system dependant. A Uniform Resource Locator in accordance with RFC 4248.
1.3.6.1.4.1.193.183.4.1.4.4SnmpAdminStringread-onlycurrent
eriAlarmAlertTable
OBJECT-TYPE
This table lists the last alerts in the system. An alert is a stateless event, that is no clear notification will be sent. Rows in this table are created when a new alert event is detected. Rows are deleted by the instrumentation at a predefined size or age.
1.3.6.1.4.1.193.183.4.1.4.5not-accessiblecurrent
eriAlarmAlertEntry
OBJECT-TYPE
One entry in the table holds one alert for a given resource. Rows in this table are created when a new alert is detected. Rows are deleted by the instrumentation at a predefined size or age.
1.3.6.1.4.1.193.183.4.1.4.5.1not-accessiblecurrent
eriAlarmAlertIndex
OBJECT-TYPE
Index in the alert table.
1.3.6.1.4.1.193.183.4.1.4.5.1.1EriAlarmIndexnot-accessiblecurrent
eriAlarmAlertMajorType
OBJECT-TYPE
In combination with eriAlarmAlertMinorType, this provides unique identification of the alert. This is a simplification of the different X.733 and 3GPP alarm IRP alarm correlation mechanisms based on EventType, ProbableCause, SpecificProblem and NotificationId.
1.3.6.1.4.1.193.183.4.1.4.5.1.2EriAlarmTyperead-onlycurrent
eriAlarmAlertMinorType
OBJECT-TYPE
In combination with eriAlarmAlertMajorType, this provides a unique identification of the alert. This is a simplification of the different X.733 and 3GPP alarm IRP alarm correlation mechanisms based on EventType, ProbableCause, SpecificProblem and NotificationId.
1.3.6.1.4.1.193.183.4.1.4.5.1.3EriAlarmTyperead-onlycurrent
eriAlarmAlertSpecificProblem
OBJECT-TYPE
This is a clear-text unique identification of the alert type. There is a one-to-one mapping between eriAlarmAlertSpecificProblem and [eriAlarmAlertMajorType, eriAlarmAlertMinorType]
1.3.6.1.4.1.193.183.4.1.4.5.1.4EriAlarmSpecificProblemread-onlycurrent
eriAlarmAlertManagedObject
OBJECT-TYPE
The 3GPP naming convention shall be used as format for the managed object parameter. Note that the granularity must be good enough to guarantee relevant resource identification to the operator. NOTE: The DN should be *relative* to the nodes *own* root.
1.3.6.1.4.1.193.183.4.1.4.5.1.5EriMOread-onlycurrent
eriAlarmAlertEventType
OBJECT-TYPE
The event type as defined in X.733/X.736.
1.3.6.1.4.1.193.183.4.1.4.5.1.6IANAItuEventTyperead-onlycurrent
eriAlarmAlertEventTime
OBJECT-TYPE
A time stamp of the alert. NOTE: All fields of the DateAndTime MUST be filled out, including the hours and minutes from UTC. As such, the value should be 11 octets long.
1.3.6.1.4.1.193.183.4.1.4.5.1.7DateAndTimeread-onlycurrent
eriAlarmAlertProbableCause
OBJECT-TYPE
The probable cause, originally defined by X.733 and subsequent standards. See also the ERICSSON-ALARM-PC-MIB. Due to the history of problems in maintaining a standardized probable cause the probable cause is not unique. A best effort mapping of the alert to existing probable causes are used.
1.3.6.1.4.1.193.183.4.1.4.5.1.8EriProbableCauseread-onlycurrent
eriAlarmAlertSeverity
OBJECT-TYPE
The severity of the alert as defined by X.733
1.3.6.1.4.1.193.183.4.1.4.5.1.9ItuPerceivedSeverityread-onlycurrent
eriAlarmAlertAdditionalText
OBJECT-TYPE
A user friendly text describing the alert. The text is both static depending on the alert type and dynamic depending on managed object and other conditions.
1.3.6.1.4.1.193.183.4.1.4.5.1.10EriLargeAdditionalTextread-onlycurrent
eriAlarmAlertResourceId
OBJECT-TYPE
In case the alert refers to an object which is instrumented by SNMP this variable indicates the corresponding OID for the managed object.
1.3.6.1.4.1.193.183.4.1.4.5.1.11ResourceIdread-onlycurrent
eriAlarmAlertAdditionalInfo
OBJECT-TYPE
Additional Information for the alert, structured in a way that is suitable for machine to machine communication. This string is longer than the corresponding varbind in the notification in order to manage large strings.
1.3.6.1.4.1.193.183.4.1.4.5.1.12EriLargeAdditionalInforead-onlycurrent
eriAlarmHeartBeat
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.1.5
eriAlarmHbInterval
OBJECT-TYPE
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)
1.3.6.1.4.1.193.183.4.1.5.1Unsigned32read-writecurrent
eriAlarmNotifications
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.2
eriAlarmNotifsPrefix
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.2.0
eriAlarmConformance
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.4
eriAlarmCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.4.1
eriAlarmGroups
OBJECT-IDENTITY
1.3.6.1.4.1.193.183.4.4.2

Notifications

NameOIDStatus
eriAlarmIndeterminate
NOTIFICATION-TYPE
This notification is sent when a resource detects a new alarm state with severity indeterminate. The notification is also used to change severity, additional text and/or additional info of an alarm. The eriAlarmNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. 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 be prepared for appending text to additional info, indicated by the eriAlarmNObjMoreAdditionalInfo varbind, and sent with eriAlarmAppendInfo. (Note do not confuse this with a change of additional info.) 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.
1.3.6.1.4.1.193.183.4.2.0.1current
eriAlarmWarning
NOTIFICATION-TYPE
This notification is sent when a resource detects a new alarm state with severity warning. The notification is also used to change severity, additional text and/or additional info of an alarm. The eriAlarmNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of ManagedObject and MajorType/MinorType is always unique and can 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 be prepared for appending text to additional info, indicated by the eriAlarmNObjMoreAdditionalInfo varbind, and sent with eriAlarmAppendInfo. (Note do not confuse this with a change of additional info.) 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.
1.3.6.1.4.1.193.183.4.2.0.2current
eriAlarmMinor
NOTIFICATION-TYPE
This notification is sent when a resource detects a new alarm state with severity minor. The notification is also used to change severity, additional text and/or additional info of an alarm. The eriAlarmNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of ManagedObject and MajorType/MinorType is always unique and can 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 be prepared for appending text to additional info, indicated by the eriAlarmNObjMoreAdditionalInfo varbind, and sent with eriAlarmAppendInfo. (Note do not confuse this with a change of additional info.) 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.
1.3.6.1.4.1.193.183.4.2.0.3current
eriAlarmMajor
NOTIFICATION-TYPE
This notification is sent when a resource detects a new alarm state with severity major. The notification is also used to change severity, additional text and/or additional info of an alarm. The eriAlarmNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of ManagedObject and MajorType/MinorType is always unique and can 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 be prepared for appending text to additional info, indicated by the eriAlarmNObjMoreAdditionalInfo varbind, and sent with eriAlarmAppendInfo. (Note do not confuse this with a change of additional info.) 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.
1.3.6.1.4.1.193.183.4.2.0.4current
eriAlarmCritical
NOTIFICATION-TYPE
This notification is sent when a resource detects a new alarm state with severity critical. The notification is also used to change severity, additional text and/or additionalinfo of an alarm. The eriAlarmNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of ManagedObject and MajorType/MinorType is always unique and can 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 be prepared for appending text to additional info, indicated by the eriAlarmNObjMoreAdditionalInfo varbind, and sent with eriAlarmAppendInfo. (Note do not confuse this with a change of additional info.) 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.
1.3.6.1.4.1.193.183.4.2.0.5current
eriAlarmCleared
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification. Note that it should not be required to send an append trap for a cleared alarm. Those varbinds which flag that an append trap will follow are kept here for backward compatibility reasons.
1.3.6.1.4.1.193.183.4.2.0.7current
eriAlarmAppendInfo
NOTIFICATION-TYPE
This notification is sent in order to append further info to an alarm notification. It might be additional text, additional info or a resource ID (OID) identifying the alarming resource using an OID. If additional text/info is sent, do not confuse this with an actual change of additional text/info which is reported using the eriAlarm<severity> notification. A zero-length string value for eriAlarmNObjAdditionalText means that no additional text is being sent in this notification. A zero-length string value for eriAlarmNObjAppendedAdditionalInfo means that no appended additional info 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.8current
eriAlarmIndAlert
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.10current
eriAlarmWarnAlert
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.11current
eriAlarmMinorAlert
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.12current
eriAlarmMajorAlert
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.13current
eriAlarmCriticalAlert
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.14current
eriAlarmAppendAlertInfo
NOTIFICATION-TYPE
This notification is sent in order to append further info to an alert notification. 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. It contains the Agent Address information to identify the Agent that raises the notification. If additional text/info is sent, do not confuse this with an actual change of additional text/info which is reported using the eriAlarmAlert<severity> notification. A zero-length string value for eriAlarmNObjAdditionalText means that no additional text is being sent in this notification. A zero-length string value for eriAlarmNObjAppendedAdditionalInfo means that no additional info 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.
1.3.6.1.4.1.193.183.4.2.0.15current
eriAlarmHeartBeatNotif
NOTIFICATION-TYPE
This is a 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. It contains the Agent Address information to identify the Agent that raises the notification. 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).
1.3.6.1.4.1.193.183.4.2.0.20current
eriAlarmAlarmListRebuilt
NOTIFICATION-TYPE
This notification 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. It contains the Agent Address information to identify the Agent that raises the notification.
1.3.6.1.4.1.193.183.4.2.0.30current

Conformance

NameOIDStatus
eriAlarmBasicAlarmsCompliance
MODULE-COMPLIANCE
Minimal compliance for the Ericsson Alarm MIB. Minimal compliance is to support heartbeat, active alarm list, and alarm notifications for raise and clear.
1.3.6.1.4.1.193.183.4.4.1.1current
eriAlarmSummaryGroup
OBJECT-GROUP
Group containing the summary counters for alarms.
1.3.6.1.4.1.193.183.4.4.2.1current
eriAlarmActiveAlarmsGroup
OBJECT-GROUP
The group of objects needed to support the active alarm list.
1.3.6.1.4.1.193.183.4.4.2.2current
eriAlarmAlertsGroup
OBJECT-GROUP
The group of objects needed to support the alert history.
1.3.6.1.4.1.193.183.4.4.2.3current
eriAlarmHeartBeatGroup
OBJECT-GROUP
Only read is required for compliance
1.3.6.1.4.1.193.183.4.4.2.4current
eriAlarmSNMPResourceGroup
OBJECT-GROUP
Objects that support SNMP object identifiers for resource identification.
1.3.6.1.4.1.193.183.4.4.2.5current
eriAlarmChangeAlarmGroup
OBJECT-GROUP
Objects that stores previous state of an alarm.
1.3.6.1.4.1.193.183.4.4.2.6current
eriAlarmActiveAlarmsAdditionalInfoGroup
OBJECT-GROUP
The group of objects needed to support Additional Information for alarms.
1.3.6.1.4.1.193.183.4.4.2.7current
eriAlarmAlertsAdditionalInfoGroup
OBJECT-GROUP
The group of objects needed to support Additional Information for alerts.
1.3.6.1.4.1.193.183.4.4.2.8current
eriAlarmRecordTypeGroup
OBJECT-GROUP
The group of objects needed to support Record Type for alarms.
1.3.6.1.4.1.193.183.4.4.2.9current
eriAlarmSimpleAlarmGroup
NOTIFICATION-GROUP
The notifications in this MIB module.
1.3.6.1.4.1.193.183.4.4.2.10current
eriAlarmAddAddInfoGroup
NOTIFICATION-GROUP
Notification to support appending of additional text.
1.3.6.1.4.1.193.183.4.4.2.12current
eriAlarmAlertNotifGroup
NOTIFICATION-GROUP
Notifications for stateless events, alerts
1.3.6.1.4.1.193.183.4.4.2.13current
eriAlarmHeartBeatNotifGroup
NOTIFICATION-GROUP
Heartbeat notifications.
1.3.6.1.4.1.193.183.4.4.2.14current
eriAlarmSourceIdentifierGroup
OBJECT-GROUP
The group of objects needed to support source identifier information for notifications.
1.3.6.1.4.1.193.183.4.4.2.15current