ERICSSON-ALARM-XPATH-MIB

File: ERICSSON-ALARM-XPATH-MIB.mib (77159 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMP-FRAMEWORK-MIB
ERICSSON-TOP-MIB ERICSSON-ALARM-TC-MIB ERICSSON-ALARM-PC-MIB
ERICSSON-TC-MIB ALARM-MIB ITU-ALARM-TC-MIB
IANA-ITU-ALARM-TC-MIB SNMP-TARGET-MIB SNMP-NOTIFICATION-MIB
SNMPv2-CONF

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Unsigned32 Gauge32 TruthValue
DateAndTime SnmpAdminString ericssonModules
EriAdditionalText EriLargeAdditionalText EriAlarmType
EriAlarmSequenceNumber EriAlarmIndex EriAlarmSpecificProblem
EriAdditionalInfo EriLargeAdditionalInfo EriAlarmRecordType
EriAppendedAdditionalInfo EriProbableCause EriPath
ResourceId ItuPerceivedSeverity IANAItuEventType
snmpTargetBasicGroup snmpNotifyGroup OBJECT-GROUP
NOTIFICATION-GROUP MODULE-COMPLIANCE

Defined Types

EriAlarmXActiveAlarmEntry  
SEQUENCE    
  eriAlarmXActiveIndex EriAlarmIndex
  eriAlarmXActiveMajorType EriAlarmType
  eriAlarmXActiveMinorType EriAlarmType
  eriAlarmXActiveSpecificProblem EriAlarmSpecificProblem
  eriAlarmXActiveYangNodeInstance EriPath
  eriAlarmXActiveEventType IANAItuEventType
  eriAlarmXActiveEventTime DateAndTime
  eriAlarmXActiveOriginalEventTime DateAndTime
  eriAlarmXActiveProbableCause EriProbableCause
  eriAlarmXActiveSeverity ItuPerceivedSeverity
  eriAlarmXActiveOriginalSeverity ItuPerceivedSeverity
  eriAlarmXActiveAdditionalText EriLargeAdditionalText
  eriAlarmXActiveOrigAdditionalText EriLargeAdditionalText
  eriAlarmXActiveResourceId ResourceId
  eriAlarmXActiveAdditionalInfo EriLargeAdditionalInfo

EriAlarmXAlertEntry  
SEQUENCE    
  eriAlarmXAlertIndex EriAlarmIndex
  eriAlarmXAlertMajorType EriAlarmType
  eriAlarmXAlertMinorType EriAlarmType
  eriAlarmXAlertSpecificProblem EriAlarmSpecificProblem
  eriAlarmXAlertYangNodeInstance EriPath
  eriAlarmXAlertEventType IANAItuEventType
  eriAlarmXAlertEventTime DateAndTime
  eriAlarmXAlertProbableCause EriProbableCause
  eriAlarmXAlertSeverity ItuPerceivedSeverity
  eriAlarmXAlertAdditionalText EriLargeAdditionalText
  eriAlarmXAlertResourceId ResourceId
  eriAlarmXAlertAdditionalInfo EriLargeAdditionalInfo

Defined Values

ericssonAlarmXpathMIB 1.3.6.1.4.1.193.183.6
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 YangNodeInstance and AlarmType. In this way, there is no ambiguity about how alarm and alarm clear correlation should be performed: the same YANG resource 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 YangNodeInstance 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 eriAlarmXIndAlert 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 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 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: 11/196 03-CXC 172 7549.
MODULE-IDENTITY    

eriAlarmXObjects 1.3.6.1.4.1.193.183.6.1
OBJECT IDENTIFIER    

eriAlarmXNotifications 1.3.6.1.4.1.193.183.6.2
OBJECT IDENTIFIER    

eriAlarmXNotifsPrefix 1.3.6.1.4.1.193.183.6.2.0
OBJECT IDENTIFIER    

eriAlarmXConformance 1.3.6.1.4.1.193.183.6.4
OBJECT IDENTIFIER    

eriAlarmXSummary 1.3.6.1.4.1.193.183.6.1.1
OBJECT IDENTIFIER    

eriAlarmXNotifObjects 1.3.6.1.4.1.193.183.6.1.2
OBJECT IDENTIFIER    

eriAlarmXActiveAlarms 1.3.6.1.4.1.193.183.6.1.3
OBJECT IDENTIFIER    

eriAlarmXAlerts 1.3.6.1.4.1.193.183.6.1.4
OBJECT IDENTIFIER    

eriAlarmXHeartBeat 1.3.6.1.4.1.193.183.6.1.5
OBJECT IDENTIFIER    

eriAlarmXSumIndeterminate 1.3.6.1.4.1.193.183.6.1.1.1
This object shows the number of currently active alarms with perceived severity 'indeterminate'. Note that only stateful alarms are included.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

eriAlarmXSumCritical 1.3.6.1.4.1.193.183.6.1.1.2
This object shows the number of currently active alarms with perceived severity 'critical'. Note that only stateful alarms are included.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

eriAlarmXSumMajor 1.3.6.1.4.1.193.183.6.1.1.3
This object shows the number of currently active alarms with perceived severity 'major'. Note that only stateful alarms are included.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

eriAlarmXSumMinor 1.3.6.1.4.1.193.183.6.1.1.4
This object shows the number of currently active alarms with perceived severity 'minor'. Note that only stateful alarms are included.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

eriAlarmXSumWarning 1.3.6.1.4.1.193.183.6.1.1.5
This object shows the number of currently active alarms with perceived severity 'warning'. Note that only stateful alarms are included.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

eriAlarmXNObjAdditionalText 1.3.6.1.4.1.193.183.6.1.2.1
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriAdditionalText  

eriAlarmXNObjMoreAdditionalText 1.3.6.1.4.1.193.183.6.1.2.2
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  TruthValue  

eriAlarmXNObjResourceId 1.3.6.1.4.1.193.183.6.1.2.3
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  TruthValue  

eriAlarmXNObjAdditionalInfo 1.3.6.1.4.1.193.183.6.1.2.4
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriAdditionalInfo  

eriAlarmXNObjMoreAdditionalInfo 1.3.6.1.4.1.193.183.6.1.2.5
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  TruthValue  

eriAlarmXNObjRecordType 1.3.6.1.4.1.193.183.6.1.2.6
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.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriAlarmRecordType  

eriAlarmXNObjAppendedAdditionalInfo 1.3.6.1.4.1.193.183.6.1.2.7
This scalar variable is used for spillover of the additional info in the append trap.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  EriAppendedAdditionalInfo  

eriAlarmXActiveNumber 1.3.6.1.4.1.193.183.6.1.3.1
This object shows the total number of currently active alarms, i.e. the total number of entries in the Alarm Table.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

eriAlarmXActiveLastChanged 1.3.6.1.4.1.193.183.6.1.3.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

eriAlarmXActiveLastSequenceNo 1.3.6.1.4.1.193.183.6.1.3.3
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.
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmSequenceNumber  

eriAlarmXActiveTableURL 1.3.6.1.4.1.193.183.6.1.3.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  SnmpAdminString  

eriAlarmXActiveAlarmTable 1.3.6.1.4.1.193.183.6.1.3.5
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 eriAlarmXActiveNumber. 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. eriAlarmXActiveTableURL provides a URL to the file.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    EriAlarmXActiveAlarmEntry

eriAlarmXActiveAlarmEntry 1.3.6.1.4.1.193.183.6.1.3.5.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  EriAlarmXActiveAlarmEntry  

eriAlarmXActiveIndex 1.3.6.1.4.1.193.183.6.1.3.5.1.1
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 - eriAlarmXActiveMajorType - eriAlarmXActiveMinorType - eriAlarmXActiveYangNodeInstance
Status: current Access: not-accessible
OBJECT-TYPE    
  EriAlarmIndex  

eriAlarmXActiveMajorType 1.3.6.1.4.1.193.183.6.1.3.5.1.2
In combination with eriAlarmXActiveMinorType, this provides a unique identification of the fault type. Different YANG Schema Nodes and instances can share alarm types, but if the same YANG resource instance 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 eriAlarmXActiveMajorType is not needed for identification purposes, it is not used and MUST be zero-valued.
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmType  

eriAlarmXActiveMinorType 1.3.6.1.4.1.193.183.6.1.3.5.1.3
In combination with with eriAlarmXActiveMajorType, this provides a unique identification of the fault type, not including the YANG Schema Node. Different YANG Schema Nodes and instances can share alarm types, but if the same YANG resource instance 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.
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmType  

eriAlarmXActiveSpecificProblem 1.3.6.1.4.1.193.183.6.1.3.5.1.4
This is a clear-text unique identification of the alarm type. There is a one-to-one mapping between eriAlarmXActiveSpecificProblem and [eriAlarmXActiveMajorType,eriAlarmXActiveMinorType]
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmSpecificProblem  

eriAlarmXActiveYangNodeInstance 1.3.6.1.4.1.193.183.6.1.3.5.1.5
An Abridged YANG Instance-Identifier that references the alarming resource within the Managed Element.
Status: current Access: read-only
OBJECT-TYPE    
  EriPath  

eriAlarmXActiveEventType 1.3.6.1.4.1.193.183.6.1.3.5.1.6
The event type as defined in X.733/X.736.
Status: current Access: read-only
OBJECT-TYPE    
  IANAItuEventType  

eriAlarmXActiveEventTime 1.3.6.1.4.1.193.183.6.1.3.5.1.7
A time stamp of the alarm state change event. Note that this variable represents the last change of the alarm state, like changed severity or 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.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

eriAlarmXActiveOriginalEventTime 1.3.6.1.4.1.193.183.6.1.3.5.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

eriAlarmXActiveProbableCause 1.3.6.1.4.1.193.183.6.1.3.5.1.9
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.
Status: current Access: read-only
OBJECT-TYPE    
  EriProbableCause  

eriAlarmXActiveSeverity 1.3.6.1.4.1.193.183.6.1.3.5.1.10
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.
Status: current Access: read-only
OBJECT-TYPE    
  ItuPerceivedSeverity  

eriAlarmXActiveOriginalSeverity 1.3.6.1.4.1.193.183.6.1.3.5.1.11
The original severity as reported by the alarm raise notification.
Status: current Access: read-only
OBJECT-TYPE    
  ItuPerceivedSeverity  

eriAlarmXActiveAdditionalText 1.3.6.1.4.1.193.183.6.1.3.5.1.12
A user friendly text describing the alarm. The text is both static depending on the alarm type (probable cause), and dynamic depending on YANG resource instance and other conditions. This string is longer than the corresponding varbind in the notification in order to manage large strings.
Status: current Access: read-only
OBJECT-TYPE    
  EriLargeAdditionalText  

eriAlarmXActiveOrigAdditionalText 1.3.6.1.4.1.193.183.6.1.3.5.1.13
A user-friendly text describing the alarm. The text is both static depending on the alarm type (probable cause), and dynamic depending on YANG resource instance and other conditions. This is the original text as reported by the first alarm notification, after which it is not altered.
Status: current Access: read-only
OBJECT-TYPE    
  EriLargeAdditionalText  

eriAlarmXActiveResourceId 1.3.6.1.4.1.193.183.6.1.3.5.1.14
In case the alarm refers to an object which is instrumented by SNMP this variable indicates the corresponding OID for the YANG resource instance.
Status: current Access: read-only
OBJECT-TYPE    
  ResourceId  

eriAlarmXActiveAdditionalInfo 1.3.6.1.4.1.193.183.6.1.3.5.1.15
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.
Status: current Access: read-only
OBJECT-TYPE    
  EriLargeAdditionalInfo  

eriAlarmXAlertNumber 1.3.6.1.4.1.193.183.6.1.4.1
The number of rows in the alert table.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

eriAlarmXAlertLastChanged 1.3.6.1.4.1.193.183.6.1.4.2
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.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

eriAlarmXAlertLastSequenceNo 1.3.6.1.4.1.193.183.6.1.4.3
The last sequence number used in alert notifications. This can be used to detect a lost notification.
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmSequenceNumber  

eriAlarmXAlertTableURL 1.3.6.1.4.1.193.183.6.1.4.4
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.
Status: current Access: read-only
OBJECT-TYPE    
  SnmpAdminString  

eriAlarmXAlertTable 1.3.6.1.4.1.193.183.6.1.4.5
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    EriAlarmXAlertEntry

eriAlarmXAlertEntry 1.3.6.1.4.1.193.183.6.1.4.5.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  EriAlarmXAlertEntry  

eriAlarmXAlertIndex 1.3.6.1.4.1.193.183.6.1.4.5.1.1
Index in the alert table.
Status: current Access: not-accessible
OBJECT-TYPE    
  EriAlarmIndex  

eriAlarmXAlertMajorType 1.3.6.1.4.1.193.183.6.1.4.5.1.2
In combination with eriAlarmXAlertMinorType, 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.
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmType  

eriAlarmXAlertMinorType 1.3.6.1.4.1.193.183.6.1.4.5.1.3
In combination with eriAlarmXAlertMajorType, 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.
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmType  

eriAlarmXAlertSpecificProblem 1.3.6.1.4.1.193.183.6.1.4.5.1.4
This is a clear-text unique identification of the alert type. There is a one-to-one mapping between eriAlarmXAlertSpecificProblem and [eriAlarmXAlertMajorType, eriAlarmXAlertMinorType]
Status: current Access: read-only
OBJECT-TYPE    
  EriAlarmSpecificProblem  

eriAlarmXAlertYangNodeInstance 1.3.6.1.4.1.193.183.6.1.4.5.1.5
An Abridged YANG Instance-Identifier that references a resource within the Managed Element.
Status: current Access: read-only
OBJECT-TYPE    
  EriPath  

eriAlarmXAlertEventType 1.3.6.1.4.1.193.183.6.1.4.5.1.6
The event type as defined in X.733/X.736.
Status: current Access: read-only
OBJECT-TYPE    
  IANAItuEventType  

eriAlarmXAlertEventTime 1.3.6.1.4.1.193.183.6.1.4.5.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  DateAndTime  

eriAlarmXAlertProbableCause 1.3.6.1.4.1.193.183.6.1.4.5.1.8
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.
Status: current Access: read-only
OBJECT-TYPE    
  EriProbableCause  

eriAlarmXAlertSeverity 1.3.6.1.4.1.193.183.6.1.4.5.1.9
The severity of the alert as defined by X.733
Status: current Access: read-only
OBJECT-TYPE    
  ItuPerceivedSeverity  

eriAlarmXAlertAdditionalText 1.3.6.1.4.1.193.183.6.1.4.5.1.10
A user friendly text describing the alert. The text is both static depending on the alert type and dynamic depending on YANG resource instance and other conditions.
Status: current Access: read-only
OBJECT-TYPE    
  EriLargeAdditionalText  

eriAlarmXAlertResourceId 1.3.6.1.4.1.193.183.6.1.4.5.1.11
In case the alert refers to an object which is instrumented by SNMP this variable indicates the corresponding OID for the YANG resource instance.
Status: current Access: read-only
OBJECT-TYPE    
  ResourceId  

eriAlarmXAlertAdditionalInfo 1.3.6.1.4.1.193.183.6.1.4.5.1.12
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.
Status: current Access: read-only
OBJECT-TYPE    
  EriLargeAdditionalInfo  

eriAlarmXHbInterval 1.3.6.1.4.1.193.183.6.1.5.1
The notification eriAlarmXHeartBeatNotif will be sent every eriAlarmXHbInterval. Managers can subscribe to the notification using the SNMP framework MIBS by using the snmpNotifyName 'heartbeat'. (SNMP-NOTIFICATION-MIB, snmpNotifyTable)
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

eriAlarmXIndeterminate 1.3.6.1.4.1.193.183.6.2.0.1
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 eriAlarmXNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of YangNodeInstance 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 eriAlarmXNObjMoreAdditionalText varbind, and sent with eriAlarmXAppendInfo. (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 eriAlarmXNObjMoreAdditionalInfo varbind, and sent with eriAlarmXAppendInfo. (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, eriAlarmXNObjResourceId will be set to 'true' and the resource ID will be sent in an eriAlarmXAppendInfo notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXWarning 1.3.6.1.4.1.193.183.6.2.0.2
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 eriAlarmXNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of YangNodeInstance 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, (eriAlarmXActiveAlarmTable). 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 eriAlarmXNObjMoreAdditionalText varbind, and sent with eriAlarmXAppendInfo. (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 eriAlarmXNObjMoreAdditionalInfo varbind, and sent with eriAlarmXAppendInfo. (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, eriAlarmXNObjResourceId will be set to 'true' and the resource ID will be sent in an eriAlarmXAppendInfo notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXMinor 1.3.6.1.4.1.193.183.6.2.0.3
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 eriAlarmXNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of YangNodeInstance 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, (eriAlarmXActiveAlarmTable). 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 eriAlarmXNObjMoreAdditionalText varbind, and sent with eriAlarmXAppendInfo. (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 eriAlarmXNObjMoreAdditionalInfo varbind, and sent with eriAlarmXAppendInfo. (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, eriAlarmXNObjResourceId will be set to 'true' and the resource ID will be sent in an eriAlarmXAppendInfo notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXMajor 1.3.6.1.4.1.193.183.6.2.0.4
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 eriAlarmXNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of YangNodeInstance 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, (eriAlarmXActiveAlarmTable). 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 eriAlarmXNObjMoreAdditionalText varbind, and sent with eriAlarmXAppendInfo. (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 eriAlarmXNObjMoreAdditionalInfo varbind, and sent with eriAlarmXAppendInfo. (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, eriAlarmXNObjResourceId will be set to 'true' and the resource ID will be sent in an eriAlarmXAppendInfo notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXCritical 1.3.6.1.4.1.193.183.6.2.0.5
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 additional info of an alarm. The eriAlarmXNObjRecordType varbind will indicate whether this is a new alarm instance or a change to an existing alarm instance. The combination of YangNodeInstance 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, (eriAlarmXActiveAlarmTable). 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 eriAlarmXNObjMoreAdditionalText varbind, and sent with eriAlarmXAppendInfo. (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 eriAlarmXNObjMoreAdditionalInfo varbind, and sent with eriAlarmXAppendInfo. (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, eriAlarmXNObjResourceId will be set to 'true' and the resource ID will be sent in an eriAlarmXAppendInfo notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXCleared 1.3.6.1.4.1.193.183.6.2.0.7
This notification is sent when a resource detects a cleared alarm state. The combination of YangNodeInstance 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, (eriAlarmXActiveAlarmTable). The sequence number will increase for every notification and can be used to detect lost notifications. 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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXAppendInfo 1.3.6.1.4.1.193.183.6.2.0.8
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 eriAlarmX notification. A zero-length string value for eriAlarmXNObjAdditionalText means that no additional text is being sent in this notification. A zero-length string value for eriAlarmXNObjAppendedAdditionalInfo means that no additional info is being sent in this notification. A null OID (0.0) value for eriAlarmXActiveResourceId means that no resource ID is being sent in this notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXIndAlert 1.3.6.1.4.1.193.183.6.2.0.10
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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXWarnAlert 1.3.6.1.4.1.193.183.6.2.0.11
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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXMinorAlert 1.3.6.1.4.1.193.183.6.2.0.12
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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXMajorAlert 1.3.6.1.4.1.193.183.6.2.0.13
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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXCriticalAlert 1.3.6.1.4.1.193.183.6.2.0.14
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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXAppendAlertInfo 1.3.6.1.4.1.193.183.6.2.0.15
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. If additional text/info is sent, do not confuse this with an actual change of additional text/info which is reported using the eriAlarmXAlert notification. A zero-length string value for eriAlarmXNObjAdditionalText means that no additional text is being sent in this notification. A zero-length string value for eriAlarmXNObjAppendedAdditionalInfo means that no additional info is being sent in this notification. A null OID (0.0) value for eriAlarmXAlertResourceId means that no resource ID is being sent in this notification.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXHeartBeatNotif 1.3.6.1.4.1.193.183.6.2.0.20
This is a heartbeat notification with interval according to the eriAlarmXHbInterval. It contains the last sequence numbers used for alarms and alarm events. These varbinds can be used to detect lost notifications. The notification eriAlarmXHeartBeatNotif will be sent every eriAlarmXHbInterval. Managers can subscribe to the notification using the SNMP framework MIBS by using the snmpNotifyName 'heartbeat'. (SNMP-NOTIFICATION-MIB, snmpNotifyTable).
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXAlarmListRebuilt 1.3.6.1.4.1.193.183.6.2.0.30
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.
Status: current Access: read-write
NOTIFICATION-TYPE    

eriAlarmXCompliances 1.3.6.1.4.1.193.183.6.4.1
OBJECT IDENTIFIER    

eriAlarmXGroups 1.3.6.1.4.1.193.183.6.4.2
OBJECT IDENTIFIER    

eriAlarmXBasicAlarmsCompliance 1.3.6.1.4.1.193.183.6.4.1.1
Minimal compliance for the Ericsson Alarm MIB. Minimal compliance is to support heartbeat, active alarm list, and alarm notifications for raise and clear.
Status: current Access: read-only
MODULE-COMPLIANCE    

eriAlarmXSummaryGroup 1.3.6.1.4.1.193.183.6.4.2.1
Group containing the summary counters for alarms.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXActiveAlarmsGroup 1.3.6.1.4.1.193.183.6.4.2.2
The group of objects needed to support the active alarm list.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXAlertsGroup 1.3.6.1.4.1.193.183.6.4.2.3
The group of objects needed to support the alert history.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXHeartBeatGroup 1.3.6.1.4.1.193.183.6.4.2.4
Only read is required for compliance
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXSNMPResourceGroup 1.3.6.1.4.1.193.183.6.4.2.5
Objects that support SNMP object identifiers for resource identification.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXChangeAlarmGroup 1.3.6.1.4.1.193.183.6.4.2.6
Objects that stores previous state of an alarm.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXActiveAlarmsAdditionalInfoGroup 1.3.6.1.4.1.193.183.6.4.2.7
The group of objects needed to support Additional Information for alarms.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXAlertsAdditionalInfoGroup 1.3.6.1.4.1.193.183.6.4.2.8
The group of objects needed to support Additional Information for alerts.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXRecordTypeGroup 1.3.6.1.4.1.193.183.6.4.2.9
The group of objects needed to support Record Type for alarms.
Status: current Access: read-only
OBJECT-GROUP    

eriAlarmXSimpleAlarmGroup 1.3.6.1.4.1.193.183.6.4.2.10
The notifications in this MIB module.
Status: current Access: read-only
NOTIFICATION-GROUP    

eriAlarmXAddAddInfoGroup 1.3.6.1.4.1.193.183.6.4.2.12
Notification to support appending of additional text.
Status: current Access: read-only
NOTIFICATION-GROUP    

eriAlarmXAlertNotifGroup 1.3.6.1.4.1.193.183.6.4.2.13
Notifications for stateless events, alerts
Status: current Access: read-only
NOTIFICATION-GROUP    

eriAlarmXHeartBeatNotifGroup 1.3.6.1.4.1.193.183.6.4.2.14
Heartbeat notifications.
Status: current Access: read-only
NOTIFICATION-GROUP    

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor