EXTREME-ERPS-MIB :: extremeErpsRingNodeStatus

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EXTREME-ERPS-MIB › extremeErpsRingNodeStatus

extremeErpsRingNodeStatus

Module: EXTREME-ERPS-MIB

OID (symbolic): EXTREME-ERPS-MIB::extremeErpsRingNodeStatus

OID (numeric): 1.3.6.1.4.1.1916.1.46.2.1.13

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: General attributes giving the current status of the ring by specifying the events/status currently present.

signalFailOnEast(0) - Signal-failure on Ring Port 1 signalFailOnWest(1) - Signal-failure on Ring Port 2 remoteSignalFailOnEast(2) - Remote-signal-failure received on Ring Port 1 remoteSignalFailOnWest(3) - Remote-signal-failure received on Ring Port 2 rplBlocked(4) - Rpl-blocked waitToRestoreTimerRunning(5) - Wait-to-restore-timer-running holdTimerRunning(6) - Hold-timer-running guardTimerRunning(7) - Guard-timer-running

Value 1 of the bit signifies the presence of the event associated with that bit and value zero signifies the absence of that event For example: If a signal failure is received on Ring port 1 and R-APS(SF) is received on port 2, then Bit 1 and 4 will have the value as 1.

Signal failure on a port represents Port failure indication received from the monitoring entity. This does not depend on hold off timer status. If signal failure is received on ring port 1 and hold-off timer is started, then both signalFailOnEast and holdTimerRunning will have the value as 1.

What is extremeErpsRingNodeStatus?

A bitmask of active ring conditions such as signal failure on the East or West port, remote signal failure received on either port, the RPL being blocked, or the wait-to-restore, hold, or guard timers currently running, letting an admin see multiple simultaneous ring events at a glance rather than polling several separate objects.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1916.1.46.2.1.13
snmpwalk -v2c -c public <target> EXTREME-ERPS-MIB::extremeErpsRingNodeStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1916.1.46.2.1.13.1
snmpget -v2c -c public <target> EXTREME-ERPS-MIB::extremeErpsRingNodeStatus.1

Start monitoring Extreme Networks Ethernet switch, ring/metro backbone (ITU-T G.8032 ERPS) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EXTREME-ERPS-MIB::extremeErpsRingNodeStatus OID value, configure state conditions and alerts, and monitor any Extreme Networks Ethernet switch, ring/metro backbone (ITU-T G.8032 ERPS) from a single console.

OID Breakdown

Upper-level ancestors (8 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.1916extremeA3COM51-SS9000SX
1.3.6.1.4.1.1916.1extremeAgentEXTREME-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1916.1.46extremeErpsEXTREME-ERPS-MIB
1.3.6.1.4.1.1916.1.46.2extremeErpsRingTableEXTREME-ERPS-MIB
1.3.6.1.4.1.1916.1.46.2.1extremeErpsRingEntryEXTREME-ERPS-MIB
1.3.6.1.4.1.1916.1.46.2.1.13extremeErpsRingNodeStatusEXTREME-ERPS-MIB