All MIBs › ENTITY-STATE-TC-MIB
Organization: IETF Entity MIB Working Group
Last Updated: 2005-11-22
Category: Hardware and Environment, Textual Conventions and Registries
Description: Defines textual conventions for representing entity states including administrative, operational, usage, alarm, and standby states of physical entities.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring ENTITY-STATE-TC-MIB with a free 30-day trial of IPNetwork Monitor.
What Is ENTITY-STATE-TC-MIB?
ENTITY-STATE-TC-MIB is a vendor-neutral IETF standards MIB (RFC 4268) that defines a set of textual conventions for representing the state of physical entities -- administrative state, operational state, usage state, alarm state, and standby/redundancy state. It does not itself define any data tables or notifications; instead it supplies reusable state-type definitions that other entity-related MIBs (such as extensions to the Entity MIB, RFC 6933) import to describe the condition of physical components like line cards, power supplies, or fans. Its relevance to hardware/software status monitoring is foundational rather than direct: any MIB that imports these textual conventions can report whether a component is enabled/disabled, in-service/out-of-service, actively used, in an alarm condition, or acting as a hot/cold standby, making this module a building block for consistent hardware fault/status reporting across vendors. It is explicitly a dependency for other entity-state-aware MIBs rather than something used standalone. It is used across essentially any standards-compliant networking or telecom equipment that models physical component state using the IETF Entity MIB framework. Engineers implementing or auditing this functionality typically reference the ENTITY-STATE-TC-MIB RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in ENTITY-STATE-TC-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 -- applicable to any networking/telecom equipment using the IETF Entity MIB framework
Monitoring Examples
This module defines only textual conventions (state type definitions) and contains no runtime data objects, tables, or notifications of its own, so there is honestly no direct monitoring scenario to describe -- it must be imported by another MIB before any of its state types become pollable. Other MIBs that import these conventions would use them to report, for example, that a power supply's alarm state is 'critical' or a line card's operational state is 'disabled', but that data lives in the importing MIB, not here.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
OIDs
RFC description
Defines textual conventions for administrative and operational state values used across IETF entity MIBs.
Start monitoring Networking/telecom equipment using IETF Entity MIB framework (state textual conventions, vendor-neutral) 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.