ERICSSON-ALARM-TC-MIB
File:
ERICSSON-ALARM-TC-MIB.mib (9771 bytes)
Imported modules
Imported symbols
Defined Types
| EriAlarmType |
|
| A unique identification of the fault, not
including the managed object. Alarm types are
used to identify if alarms indicate the same
problem or not, for lookup into external alarm
documentation, etc. A unique alarm type is
identified using the combination of two instances
of EriAlarmType. 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 to be 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
|
|
| EriAlarmIndex |
|
| Index used in the active alarm table. A row
shall never change its index during the lifetime
of the entry; for example renumbering entries is
not allowed when entries are deleted.
Renumbering after an agent restart is allowed.
Note that this index shall not be used to
identify alarms when performing
resynchronization, etc. The logical identity for
an alarm instance is the managed object and alarm
type. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
|
|
| EriAdditionalText |
|
| The string used in additional text
notifications. This MUST contain enough
information for an operator to be able to
understand the problem. If this string contains
structure, this format should be clearly
documented for programs to be able to parse that
information. This is a small size range in order
to guarantee delivery of notifications without
fragmentation. There is a corresponding textual
convention, EriLargeAdditionalText, to be used
for scalar and columnar objects. The string
should adhere to the rules for SnmpAdminString of
SNMPv3 framework MIBs. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4..256) |
|
| EriLargeAdditionalText |
|
| The string used in additional text. This MUST
contain enough information for an operator to be
able to understand the problem. If this string
contains structure, this format should be clearly
documented for programs to be able to parse that
information. This is a large additional text to
be used in tables. There is a corresponding
textual convention to be used in alarm
notifications, EriAdditionalText. The string
should adhere to the rules for SnmpAdminString of
SNMPv3 framework MIBs. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4..512) |
|
| EriAlarmSpecificProblem |
|
| Unique string for the Alarm Type. No different
alarm types may share specific problem. Specific
Problem and Alarm Type have a one-to-one
correspondance. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4..64) |
|
| EriAlarmSequenceNumber |
|
| This is a monotonically increasing counter. It
is increased every time a notification is sent.
The value is NOT increased for heartbeat
notifications. It is carried as a varbind in the
alarm notifications as well as in the heartbeat
notifications. Management systems can use these
varbinds to detect lost notifications. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
|
|
| EriAdditionalInfo |
|
| Additional Information, structured in a way that is
suitable for machine-to-machine communication.
Comprises a number of name=value pairs, separated by a
semicolon in the following format:
name1=value1;name2=value2;..
Allowed strings for use as 'name' are defined in
The Ericsson Architecture and updated upon internal
requests from Ericsson organizations.
This is a small size range in order to guarantee delivery
of notifications without fragmentation. There is a
corresponding textual convention, EriLargeAdditionalInfo,
to be used for scalar and columnar objects.
The string should adhere to the rules for SnmpAdminString
of SNMPv3 framework MIBs. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4..256) |
|
| EriAppendedAdditionalInfo |
|
| Used for spillover of Additional Info in the append trap. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4..512) |
|
| EriLargeAdditionalInfo |
|
| Additional Information, structured in a way that is
suitable for machine-to-machine communication.
Comprises a number of name=value pairs, separated by a
semicolon in the following format:
name1=value1;name2=value2;..
Allowed strings for use as 'name' are defined in
The Ericsson Architecture and updated upon internal
requests from Ericsson organizations.
This is a large additional info to be used in tables.
There is a corresponding textual convention to be used
in alarm notifications, EriAdditionalInfo.
The string should adhere to the rules for SnmpAdminString
of SNMPv3 framework MIBs. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4..768) |
|
| EriAlarmRecordType |
|
| This defines the alarm record type that is
being reported in an alarm notification. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
alarmNew(0), alarmChange(1) |
|
Defined Values
| ericssonAlarmTCMIB |
1.3.6.1.4.1.193.183.3 |
| This MIB defines textual conventions used by the
ERICSSON-ALARM-MIB.
Document number: 3/196 03-CXC 172 7549 |
| MODULE-IDENTITY |
|
|
|