ENTITY-STATE-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ENTITY-STATE-MIB

Organization: IETF Entity MIB Working Group

Last Updated: 2005-11-22

Category: Hardware and Environment, MPLS and Traffic Engineering

Description: Defines managed objects extending the Entity MIB to provide administrative, operational, and standby state information for physical entities.

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

What Is ENTITY-STATE-MIB?

This is a vendor-neutral IETF standards-track MIB (RFC 4268) that extends the Entity MIB with detailed administrative, operational, and standby/usage state information for each physical entity (e.g., card, power supply, fan, module) in a managed device's physical inventory. It exposes per-entity state objects such as administrative state (e.g., locked/unlocked), operational state, and standby/redundancy state (active, standby, hot-standby, etc.), enabling detection of failed or degraded hardware components. This is directly a hardware status monitoring MIB: it lets an operator determine whether a specific physical component such as a line card or power supply is enabled, functioning, or has failed over to a standby unit, which is central to detecting hardware faults and redundancy switchover events. It explicitly depends on and extends the ENTITY-MIB (RFC 4133), using its entPhysicalIndex as the indexing key for its state tables. It is broadly deployed across enterprise routers, switches, and chassis-based systems from many vendors that support ENTITY-MIB-based physical inventory with state extensions, and entity-state-mib remains a common reference for engineers implementing that support.

IPNetwork Monitor allows you to monitor SNMP objects defined in ENTITY-STATE-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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • chassis-based routers and switches with modular/redundant hardware components

Monitoring Examples

An NMS polling entStateAdmin and entStateStandby for each entPhysicalIndex-indexed physical entity (e.g., a redundant power supply or supervisor module) can detect if a component has been administratively locked, has failed, or has switched into standby/hot-standby mode following a fault. A power supply reporting a disabled operational state alongside a standby state change would indicate a power failure that triggered failover to a backup unit.

What Can Be Monitored

  • administrative state of physical entities
  • operational state of physical entities
  • standby/redundancy state (active/standby/hot-standby)
  • hardware component failover events
Imported Objects

From ENTITY-MIB

entPhysicalIndexOBJECT-TYPE

From ENTITY-STATE-TC-MIB

EntityAdminState
EntityAlarmStatus
EntityOperState
EntityStandbyStatus
EntityUsageState

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
mib-2

From SNMPv2-TC

DateAndTime
OIDs

RFC description

RFC 4268-defined MIB that extends Entity MIB with state information for physical components, including operational, administrative, usage, alarm, and standby states. Provides textual conventions for standardized entity state reporting.

Start monitoring Chassis-based router/switch with modular/redundant hardware (entity state extension, vendor-neutral IETF standard RFC 4268) 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 ENTITY-STATE-MIB