ENTITY-STATE-MIB

Monitored by Observium
        This MIB defines a state extension to the Entity MIB.  
Copyright at The Internet Society 2005.  This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Status
Explore Observium network monitoring
Source file
ENTITY-STATE-MIB
Last revised
Identity
entityStateMIB
Base OID
1.3.6.1.2.1.131
Imported Objects
ENTITY-MIB entPhysicalIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DateAndTime TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the rfc 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 'ENTITY-STATE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ENTITY-STATE-MIB::entityStateMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ENTITY-STATE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ENTITY-STATE-MIB::entityStateMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (14)
2 directly used by Observium
.1.3.6.1.2.1.131
.1.3.6.1.2.1.131.0
.1.3.6.1.2.1.131.1
.1.3.6.1.2.1.131.1.1
.1.3.6.1.2.1.131.1.1.1
.1.3.6.1.2.1.131.1.1.1.1
.1.3.6.1.2.1.131.1.1.1.2
entStateOper OBS ✓
.1.3.6.1.2.1.131.1.1.1.3
entStateUsage OBS ✓
.1.3.6.1.2.1.131.1.1.1.4
.1.3.6.1.2.1.131.1.1.1.5
.1.3.6.1.2.1.131.1.1.1.6
.1.3.6.1.2.1.131.2
.1.3.6.1.2.1.131.2.1
.1.3.6.1.2.1.131.2.2
Dependencies (7) 4 direct · 3 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)
Enumeration
unknown(1)
locked(2)
shuttingDown(3)
unlocked(4)
Bits
unknown(0)
underRepair(1)
critical(2)
major(3)
minor(4)
warning(5)
indeterminate(6)
Enumeration
unknown(1)
disabled(2)
enabled(3)
testing(4)
Enumeration
unknown(1)
hotStandby(2)
coldStandby(3)
providingService(4)
Enumeration
unknown(1)
idle(2)
active(3)
busy(4)
Conformance Groups (2)
Standard Entity State group.
.1.3.6.1.2.1.131.2.2.1
Standard Entity State Notification group.
.1.3.6.1.2.1.131.2.2.2
Compliance Statements (1)

OID .1.3.6.1.2.1.131.2.1.1
The compliance statement for systems supporting
the Entity State MIB.
Required groups
mandatory entStateGroup
optional entStateNotificationsGroup This group is optional.
Object refinements
ObjectAccessSyntaxDescription
entStateAdmin readonly
Write access is not required.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.2.1.131.0.1
An entStateOperEnabled notification signifies that the
SNMP entity, acting in an agent role, has detected that
the entStateOper object for one of its entities has
transitioned into the 'enabled' state.

The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may explain why the physical entity has become
operationally disabled.
.1.3.6.1.2.1.131.0.2
An entStateOperDisabled notification signifies that the
SNMP entity, acting in an agent role, has detected that
the entStateOper object for one of its entities has
transitioned into the 'disabled' state.

The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may affect the physical entity's
ability to stay operationally enabled.