CISCO-ENTITY-ALARM-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-ENTITY-ALARM-MIB

Organization: Cisco Systems, Inc.

Last Updated: 1999-07-06

Category: Alarm and Event Management, Cisco Devices, Device Management, Hardware and Environment

Description: Supports monitoring of alarms generated by physical entities (chassis, modules, ports, power supplies) identified in the Entity-MIB entPhysicalTable.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-ENTITY-ALARM-MIB with a free 30-day trial of IPNetwork Monitor.

What Is CISCO-ENTITY-ALARM-MIB?

CISCO-ENTITY-ALARM-MIB supports monitoring of alarms generated by physical entities represented in the standard ENTITY-MIB's entPhysicalTable, including chassis, slots, modules, ports, power supplies, and fans across Cisco equipment. The data it exposes is fault/alarm-oriented: a mapping of vendor-specific alarm descriptions to entities, a table of alarm type and severity per description, human-readable alarm text, and aggregate counts of critical, major, and minor alarms currently active. As a hardware-fault MIB it is central to monitoring hardware health across a chassis, letting an administrator see at a glance how many critical versus minor alarms are outstanding and drill into which physical component (power supply, fan, module, port) triggered each one. It has an explicit, hard dependency on ENTITY-MIB, since every alarm is tied to a row in entPhysicalTable representing the physical entity it belongs to. It is broadly deployed across Cisco chassis-based platforms (routers, switches), where CISCO-ENTITY-ALARM-MIB SNMP monitoring gives granular per-component alarm visibility for proactive hardware fault management.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ENTITY-ALARM-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Cisco chassis-based router or switch

Monitoring Examples

A monitoring system first polls ceAlarmCriticalCount, ceAlarmMajorCount, and ceAlarmMinorCount for a quick chassis-wide health summary, then walks ceAlarmDescrTable / ceAlarmDescrEntry to find the ceAlarmDescrSeverity and ceAlarmDescrText for any active alarm types. Cross-referencing ceAlarmDescrMapTable / ceAlarmDescrMapEntry using ceAlarmDescrVendorType links a given alarm description back to the specific entPhysicalTable entry (such as a particular fan tray or power supply) that raised it. A sudden increase in ceAlarmCriticalCount combined with a fan-related ceAlarmDescrText would prompt immediate investigation into chassis cooling before a thermal shutdown occurs.

What Can Be Monitored

  • critical/major/minor alarm counts
  • per-entity alarm severity
  • alarm description text
  • physical entity associated with an alarm (chassis, module, power supply, fan)
Imported Objects

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From CISCO-TC

Unsigned32

From ENTITY-MIB

PhysicalIndex
entPhysicalIndexOBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

AutonomousType
DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue
OIDs

RFC description

Monitoring of alarms from physical entities including chassis, slots, modules, ports, and power supplies.

Start monitoring Cisco routers and switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-ENTITY-ALARM-MIB