EZ5 MIB Catalog

CISCO-ALARM-MIB

2020-08-31

Added hwCem(68) to existing CoiAlarmObjectTypeClass object.

Download CISCO-ALARM-MIB.txt Open CISCO-ALARM-MIB.txt in a new tab

TABLES (1) · TRAPS (1)

Tables (1)

NameOID
coiAlarmActiveTable1.3.6.1.4.1.9.9.869.1.1.1

Traps (1)

NameOID
coiAlarmStatusChange1.3.6.1.4.1.9.9.869.0.1

END OF TOC

Table details

coiAlarmActiveTable

1.3.6.1.4.1.9.9.869.1.1.1

Index: coiAlarmIndex · coiAlarmObjectIfIndex · coiAlarmObjectEntPhyIndex · coiAlarmType

A table of Active Alarms entries.

coiAlarmIndex

1.3.6.1.4.1.9.9.869.1.1.1.1.1

Integer32

AlarmIndex is hashIndex generated from combination of AID and EID. AlarmIndex will be set only when AlarmObjectIfIndex and AlarmObjectEntPhyIndex is not available, else default value is set to 0

coiAlarmObjectIfIndex

1.3.6.1.4.1.9.9.869.1.1.1.1.2

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

if the alarm is interface related, this is the index of the interface in the interface table, else default 0 will be set.

coiAlarmObjectEntPhyIndex

1.3.6.1.4.1.9.9.869.1.1.1.1.3

EntPhysicalIndexOrZeroThis textual convention is an extension of entPhysicalIndex. If non-zero, the object is an entPhysicalIndex. If zero, no appropriate entPhysicalIndex exists. Any additional semantics are object specific. (0..2147483647) · Integer32

if the alarm is raised from Physical Entity like LC, this field will be set to Physical Index of that Physical Entity, else default 0 will be set.

coiAlarmObjectName

1.3.6.1.4.1.9.9.869.1.1.1.1.4

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

User-visible name which uniquely identifies an object in the system.

coiAlarmObjectType

1.3.6.1.4.1.9.9.869.1.1.1.1.5

CoiAlarmObjectTypeClass1 = unknown2 = hwMemorySbe3 = hwMemoryMbe4 = hwMemoryParity5 = hwFreeze6 = hwFlopError7 = hwInternal8 = hwTimeout9 = hwHang10 = hwError11 = hwLinkCrc12 = hwCodeViolation13 = hwLinkDisparity14 = hwEnvmonSensorAlarm15 = hwEnvmonPemAlarm16 = hwEnvmonFanAlarm17 = swMemoryFault18 = swBusError19 = swProcessCrash20 = swMallocError21 = swFoobar22 = swConnectFail23 = swProcessRestart24 = swProcessFailure25 = swMandatoryProcessFailure26 = swServiceRestart27 = swServiceFailure28 = swPmHeartbeat29 = swHostosHeartbeat30 = swCccWdog31 = hwConfigErr32 = hwGenericErr33 = hwIndirectErr34 = hwOorThreshErr35 = hwUnexpectedErr36 = hwBoardReload37 = hwSliceReload38 = hwMiscErr39 = hwRxResourceErr40 = hwTxResourceErr41 = hwLinkStatChange42 = hwEtherBridge43 = swInitErr44 = swMiscErr45 = hwEnvmonEcuAlarm46 = hwEnvmonPwrFilterAlarm47 = hwSonet48 = hwG70949 = hwEthernet50 = hwOptics51 = hwGfp52 = hwSdhController53 = swFsdbaggPlane54 = hwOts55 = swMacsecMka56 = swSmartLicErr57 = swProvisionErr58 = hwSyncec59 = hwPci60 = swWdDiskUsage61 = swCfgmgr62 = swG709Otnsec63 = hwCpri64 = hwImfpga65 = swFsdbaggConnMismatch66 = hwFibreChannel67 = hwE168 = hwCemThis is the TC used to find out to which coiObjectTypeClass an alarm belongs to · Integer32

indicates the type of the entity which raised this alarm. (refer coiAlarmObjectTypeClass)

coiAlarmType

1.3.6.1.4.1.9.9.869.1.1.1.1.6

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Unique ID to identify an Alarm type in the system. Also, referred to in different systems as condition type, alarm identifier, or alarm mnemonic.

coiAlarmTimeStamp

1.3.6.1.4.1.9.9.869.1.1.1.1.7

Counter64 (0..18446744073709551615)

The time at which the alarm was raised by the system. This value is expressed in seconds since 00:00:00 UTC, January 1, 1970 (see time(2)).

coiAlarmSeverity

1.3.6.1.4.1.9.9.869.1.1.1.1.8

INTEGER0 = unknown1 = notReported2 = notAlarmed3 = minor4 = major5 = critical · Integer32

The severity level indicating the criticality and impact of the alarm.

coiAlarmStatus

1.3.6.1.4.1.9.9.869.1.1.1.1.9

INTEGER0 = unknown1 = set2 = clear3 = suppress · Integer32

Alarm status represents if an alarm is currently raised or cleared.

coiAlarmServiceAffecting

1.3.6.1.4.1.9.9.869.1.1.1.1.10

INTEGER0 = unknown1 = notServiceAffecting2 = serviceAffecting · Integer32

Alarm service affecting flag specifies if an alarm is Service Affecting (SA) or Non-Service Affecting (NSA)

coiAlarmDescription

1.3.6.1.4.1.9.9.869.1.1.1.1.11

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Alarm Description used to inform operators about the alarm. This contains enough information for an operator to be able to understand the problem.

Trap details

coiAlarmStatusChange

1.3.6.1.4.1.9.9.869.0.1

This Notification is generated when ever an alarm is updated in the alarm mib. varbind coiAlarmIndex,coiAlarmObjectIFINdex and coiAlarmObjectEntPhyIndex indicates the index of the alarm i.e fow sw, interface and hw alarms will have the respective index varbind coiObjectName indicates the alarms name. varbind coiAlarmSeverity indicates the severity of the alarm. varbind coiAlarmStatus indicates the status of the alarm

coiAlarmIndex

1.3.6.1.4.1.9.9.869.1.1.1.1.1

Integer32

AlarmIndex is hashIndex generated from combination of AID and EID. AlarmIndex will be set only when AlarmObjectIfIndex and AlarmObjectEntPhyIndex is not available, else default value is set to 0

coiAlarmObjectIfIndex

1.3.6.1.4.1.9.9.869.1.1.1.1.2

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

if the alarm is interface related, this is the index of the interface in the interface table, else default 0 will be set.

coiAlarmObjectEntPhyIndex

1.3.6.1.4.1.9.9.869.1.1.1.1.3

EntPhysicalIndexOrZeroThis textual convention is an extension of entPhysicalIndex. If non-zero, the object is an entPhysicalIndex. If zero, no appropriate entPhysicalIndex exists. Any additional semantics are object specific. (0..2147483647) · Integer32

if the alarm is raised from Physical Entity like LC, this field will be set to Physical Index of that Physical Entity, else default 0 will be set.

coiAlarmObjectName

1.3.6.1.4.1.9.9.869.1.1.1.1.4

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

User-visible name which uniquely identifies an object in the system.

coiAlarmType

1.3.6.1.4.1.9.9.869.1.1.1.1.6

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Unique ID to identify an Alarm type in the system. Also, referred to in different systems as condition type, alarm identifier, or alarm mnemonic.

coiAlarmSeverity

1.3.6.1.4.1.9.9.869.1.1.1.1.8

INTEGER0 = unknown1 = notReported2 = notAlarmed3 = minor4 = major5 = critical · Integer32

The severity level indicating the criticality and impact of the alarm.

coiAlarmStatus

1.3.6.1.4.1.9.9.869.1.1.1.1.9

INTEGER0 = unknown1 = set2 = clear3 = suppress · Integer32

Alarm status represents if an alarm is currently raised or cleared.

coiAlarmDescription

1.3.6.1.4.1.9.9.869.1.1.1.1.11

DisplayStringRepresents textual information taken from the NVT ASCII character set, as defined in pages 4, 10-11 of RFC 854. To summarize RFC 854, the NVT ASCII repertoire specifies: - the use of character codes 0-127 (decimal) - the graphics characters (32-126) are interpreted as US ASCII - NUL, LF, CR, BEL, BS, HT, VT and FF have the special meanings specified in RFC 854 - the other 25 codes have no standard interpretation - the sequence 'CR LF' means newline - the sequence 'CR NUL' means carriage-return - an 'LF' not preceded by a 'CR' means moving to the same column on the next line. - the sequence 'CR x' for any x other than LF or NUL is illegal. (Note that this also means that a string may end with either 'CR LF' or 'CR NUL', but not with CR.) Any object defined using this syntax may not exceed 255 characters in length. SIZE (0..255) · OCTET STRING · hint 255a

Alarm Description used to inform operators about the alarm. This contains enough information for an operator to be able to understand the problem.

↑ To TOC