ESAFE-MIB :: esafeErouterOperMode

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › ESAFE-MIB › esafeErouterOperMode

esafeErouterOperMode

Module: ESAFE-MIB

OID (symbolic): ESAFE-MIB::esafeErouterOperMode

OID (numeric): 1.3.6.1.4.1.4491.2.1.14.1.5.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object provides visibility to the current mode of operation of the DOCSIS eRouter eSAFE element of the eDOCSIS compliant device.

If the value of this object is disabled(1), the eRouter eSAFE element has been administratively Disabled. The eDOCSIS device will bridge traffic according to the configuration of the DOCSIS embedded cable modem (eCM)

If the value of this object is ipv4OnlyFwding(2), the eRouter eSAFE element is currently operating with the IPv4 protocol stack operational, is forwarding IPv4 traffic, and is not running an IPv6 protocol stack and not forwarding IPv6 traffic.

If the value of this object is ipv6OnlyFwding(3), the eRouter eSAFE element is currently operating with the IPv6 protocol stack operational, is forwarding IPv6 traffic, and is not running an IPv4 protocol stack and not forwarding IPv4 traffic.

If the value of this object is ipv4AndIpv6Fwding(4), the eRouter eSAFE element is currently operating with both the IPv4 protocol stack and IPv6 protocol stack operational, and is forwarding IPv4 and IPv6 traffic.

If the value of this object is noIpv4AndNoIpv6Fwding(5), the eRouter is currently operating with neither the IPv4 nor IPv6 protocol stack running. The eRouter is unable to pass traffic between the Operator-Facing Interface and the Customer-Facing Interface.

What is esafeErouterOperMode?

This reports the DOCSIS eRouter eSAFE element's actual current forwarding mode of operation. An admin uses it to confirm real traffic-forwarding behavior against the administratively configured mode, catching cases where forwarding has stalled. For example, seeing noIpv4AndNoIpv6Fwding(5) despite ipv4AndIpv6(4) being configured tells the admin the eRouter isn't actually passing traffic and needs investigation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.14.1.5.2
snmpwalk -v2c -c public <target> ESAFE-MIB::esafeErouterOperMode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.14.1.5.2.1
snmpget -v2c -c public <target> ESAFE-MIB::esafeErouterOperMode.1

Start monitoring Cable modem/gateway with embedded eSAFE service applications (DOCSIS CPE) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ESAFE-MIB::esafeErouterOperMode OID value, configure state conditions and alerts, and monitor any Cable modem/gateway with embedded eSAFE service applications (DOCSIS CPE) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4491cableLabsCLAB-DEF-MIB
1.3.6.1.4.1.4491.2clabProjectCLAB-DEF-MIB
1.3.6.1.4.1.4491.2.1clabProjDocsisCLAB-DEF-MIB
1.3.6.1.4.1.4491.2.1.14esafeMibCLAB-DEF-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4491.2.1.14.1esafeMibObjectsESAFE-MIB
1.3.6.1.4.1.4491.2.1.14.1.5esafeErouterMibObjectsESAFE-MIB
1.3.6.1.4.1.4491.2.1.14.1.5.2esafeErouterOperModeESAFE-MIB