CISCO-ENTITY-ALARM-MIB

        This MIB module defines the managed objects that support the
monitoring of alarms generated by physical entities contained
by the system, including chassis, slots, modules, ports, power
supplies, and fans.  In order to monitor alarms generated by a
physical entity, it must be represented by a row in the
entPhysicalTable (see ENTITY-MIB).
    
Source file
CISCO-ENTITY-ALARM-MIB
Last revised
Identity
ciscoEntityAlarmMIB
Base OID
1.3.6.1.4.1.9.9.138
Imported Objects
CISCO-SMI ciscoMgmt
CISCO-TC Unsigned32
ENTITY-MIB entPhysicalIndex PhysicalIndex
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC AutonomousType DisplayString RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-ENTITY-ALARM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-ENTITY-ALARM-MIB::ciscoEntityAlarmMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-ENTITY-ALARM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ENTITY-ALARM-MIB::ciscoEntityAlarmMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (50)
.1.3.6.1.4.1.9.9.138
.1.3.6.1.4.1.9.9.138.1
.1.3.6.1.4.1.9.9.138.1.1
.1.3.6.1.4.1.9.9.138.1.1.1
.1.3.6.1.4.1.9.9.138.1.1.1.1
.1.3.6.1.4.1.9.9.138.1.1.1.1.1
.1.3.6.1.4.1.9.9.138.1.1.1.1.2
.1.3.6.1.4.1.9.9.138.1.1.2
.1.3.6.1.4.1.9.9.138.1.1.2.1
.1.3.6.1.4.1.9.9.138.1.1.2.1.1
.1.3.6.1.4.1.9.9.138.1.1.2.1.2
.1.3.6.1.4.1.9.9.138.1.1.2.1.3
.1.3.6.1.4.1.9.9.138.1.2
.1.3.6.1.4.1.9.9.138.1.2.1
.1.3.6.1.4.1.9.9.138.1.2.2
.1.3.6.1.4.1.9.9.138.1.2.3
.1.3.6.1.4.1.9.9.138.1.2.4
.1.3.6.1.4.1.9.9.138.1.2.5
.1.3.6.1.4.1.9.9.138.1.2.5.1
.1.3.6.1.4.1.9.9.138.1.2.5.1.1
.1.3.6.1.4.1.9.9.138.1.2.5.1.2
.1.3.6.1.4.1.9.9.138.1.2.5.1.3
.1.3.6.1.4.1.9.9.138.1.3
Integer32
.1.3.6.1.4.1.9.9.138.1.3.1
.1.3.6.1.4.1.9.9.138.1.3.2
.1.3.6.1.4.1.9.9.138.1.3.3
.1.3.6.1.4.1.9.9.138.1.3.3.1
.1.3.6.1.4.1.9.9.138.1.3.3.1.1
Enumeration
.1.3.6.1.4.1.9.9.138.1.3.3.1.2
.1.3.6.1.4.1.9.9.138.1.3.3.1.3
.1.3.6.1.4.1.9.9.138.1.3.3.1.4
.1.3.6.1.4.1.9.9.138.1.3.3.1.5
.1.3.6.1.4.1.9.9.138.1.3.3.1.6
.1.3.6.1.4.1.9.9.138.1.4
.1.3.6.1.4.1.9.9.138.1.4.1
.1.3.6.1.4.1.9.9.138.1.4.2
.1.3.6.1.4.1.9.9.138.1.4.3
.1.3.6.1.4.1.9.9.138.1.4.4
.1.3.6.1.4.1.9.9.138.1.4.4.1
.1.3.6.1.4.1.9.9.138.1.4.4.1.1
.1.3.6.1.4.1.9.9.138.1.4.4.1.2
.1.3.6.1.4.1.9.9.138.1.4.4.1.3
.1.3.6.1.4.1.9.9.138.1.4.4.1.4
.1.3.6.1.4.1.9.9.138.1.4.4.1.5
.1.3.6.1.4.1.9.9.138.1.4.4.1.6
.1.3.6.1.4.1.9.9.138.2
.1.3.6.1.4.1.9.9.138.2.0
.1.3.6.1.4.1.9.9.138.3
.1.3.6.1.4.1.9.9.138.3.1
.1.3.6.1.4.1.9.9.138.3.2
Dependencies (9) 7 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (5)
Unsigned32
OctetString range: 0..32
Enumeration
critical(1)
major(2)
minor(3)
info(4)
Integer32 range: 0..4
Integer32 range: 0..255
Conformance Groups (5)
A collection of managed objects defining the description
of alarms.
.1.3.6.1.4.1.9.9.138.3.2.1
A collection of managed objects defining alarm reporting
by physical entity.
.1.3.6.1.4.1.9.9.138.3.2.2
A collection of managed objects defining alarm logging.
.1.3.6.1.4.1.9.9.138.3.2.3
A collection of managed objects that control the generation
of all notifications and syslog messages.
.1.3.6.1.4.1.9.9.138.3.2.4
A collection of managed objects that support alarm filtering.
.1.3.6.1.4.1.9.9.138.3.2.5
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.138.3.1.1
The compliance statement for entities that implement the
CISCO-ALARM-MIB. Implementation of this MIB module is strongly
recommended for any platform targeted for a carrier-class
environment.
Required groups
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.9.138.2.0.1
The agent generates this trap when a physical entity
asserts an alarm.
.1.3.6.1.4.1.9.9.138.2.0.2
The agent generates this trap when a physical entity
clears a previously asserted alarm.