eriAlarmAlertMinorType

ERICSSON-ALARM-MIB · .1.3.6.1.4.1.193.183.4.1.4.5.1.3
MIB view Table view

Object

column ERICSSON-ALARM-TC-MIBEriAlarmType 
In combination with eriAlarmAlertMajorType, this
provides a unique identification of the fault.
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.

Context

MIB
ERICSSON-ALARM-MIB
OID
.1.3.6.1.4.1.193.183.4.1.4.5.1.3
Type
column
Access
readonly
Status
current
Parent
eriAlarmAlertEntry
Table
eriAlarmAlertTable
Siblings
10

Syntax

ERICSSON-ALARM-TC-MIBEriAlarmType
Source
ERICSSON-ALARM-TC-MIBEriAlarmType
Base type
Unsigned32

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Sibling Objects
ObjectTypeSyntaxOID
eriAlarmAlertIndex
Index in the alert table.
columnERICSSON-ALARM-TC-MIBEriAlarmIndex.1.3.6.1.4.1.193.183.4.1.4.5.1.1
eriAlarmAlertAdditionalText
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.
columnERICSSON-ALARM-TC-MIBEriLargeAdditionalText.1.3.6.1.4.1.193.183.4.1.4.5.1.10
eriAlarmAlertResourceId
In case the alert refers to an object which is instrumented by SNMP this variable indicates the corresponding OID for the managed object.
columnALARM-MIBResourceId.1.3.6.1.4.1.193.183.4.1.4.5.1.11
eriAlarmAlertMajorType
In combination with eriAlarmAlertMinorType, this provides unique identification of the fault. Different managed object types and instances can share alarm types, but if the same m…
columnERICSSON-ALARM-TC-MIBEriAlarmType.1.3.6.1.4.1.193.183.4.1.4.5.1.2
eriAlarmAlertSpecificProblem
This is a clear-text unique identification of the alert type. There is a one-to-one mapping between eriAlarmAlertSpecificProblem and [eriAlarmAlertMajorType, eriAlarmAlertMinorTyp…
columnERICSSON-ALARM-TC-MIBEriAlarmSpecificProblem.1.3.6.1.4.1.193.183.4.1.4.5.1.4
eriAlarmAlertManagedObject
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…
columnERICSSON-TC-MIBEriMO.1.3.6.1.4.1.193.183.4.1.4.5.1.5
eriAlarmAlertEventType
The event type as defined in X.733/X.736.
columnIANA-ITU-ALARM-TC-MIBIANAItuEventType.1.3.6.1.4.1.193.183.4.1.4.5.1.6
eriAlarmAlertEventTime
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.
columnSNMPv2-TCDateAndTime.1.3.6.1.4.1.193.183.4.1.4.5.1.7
eriAlarmAlertProbableCause
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 s…
columnERICSSON-ALARM-PC-MIBEriProbableCause.1.3.6.1.4.1.193.183.4.1.4.5.1.8
eriAlarmAlertSeverity
The severity of the alert as defined by X.733
columnITU-ALARM-TC-MIBItuPerceivedSeverity.1.3.6.1.4.1.193.183.4.1.4.5.1.9