All MIBs › ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB › etsysIetfBridgeDot1dStpPortCistNonForwardingReason
etsysIetfBridgeDot1dStpPortCistNonForwardingReason
Module: ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB
OID (symbolic): ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB::etsysIetfBridgeDot1dStpPortCistNonForwardingReason
OID (numeric): 1.3.6.1.4.1.5624.1.2.31.1.1.1.1.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Indicates the reason why this port has been placed in a non-forwarding state on the CIST (other than as a result of normal Spanning Tree protocol operation).
none(1) - the port has not been placed in a non-forwarding state due to any exceptional condition.
disputed(2) - the port has been placed in listening state because it has a designated role and an inferior designated BPDU has been received.
spanGuardLocked(3) - the port has been placed in blocking state because it is configured as an admin edge port and a BPDU has been received.
loopProtectEvent(4) - the port has been placed in listening or blocking state because a BPDU timeout has occurred and the port is awaiting reception of a type 2 BPDU on a point-to-point link.
loopProtectAdvisory(5) - the port has been placed in listening state because a BPDU timeout has occurred (as with a Loop Protect event), but this condition may be normal because the link partner does not support the Loop Protect feature.
loopbackDetected(6) - the port has been placed in blocking state because a loopback condition has been detected.
What is etsysIetfBridgeDot1dStpPortCistNonForwardingReason?
This read-only enumeration explains why a port is not forwarding outside of normal STP operation (e.g. disputed BPDU, SpanGuard lock, Loop Protect event, or a detected loopback), giving an admin the specific root cause instead of just 'blocking'.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.31.1.1.1.1.4 snmpwalk -v2c -c public <target> ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB::etsysIetfBridgeDot1dStpPortCistNonForwardingReason
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.31.1.1.1.1.4.1 snmpget -v2c -c public <target> ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB::etsysIetfBridgeDot1dStpPortCistNonForwardingReason.1
Start monitoring Enterasys Networks switch (legacy, later Extreme Networks) (BRIDGE-MIB extensions: SpanGuard/Loop Protect) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB::etsysIetfBridgeDot1dStpPortCistNonForwardingReason OID value, configure state conditions and alerts, and monitor any Enterasys Networks switch (legacy, later Extreme Networks) (BRIDGE-MIB extensions: SpanGuard/Loop Protect) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.5624 | enterasys | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1 | etsysMibs | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1.2 | etsysModules | ENTERASYS-MIB-NAMES |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.5624.1.2.31 | etsysIetfBridgeMibExtMIB | ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.31.1 | etsysIetfBridgeMibExt | ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.31.1.1 | etsysIetfBridgeDot1dStp | ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.31.1.1.1 | etsysIetfBridgeDot1dStpPortTable | ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.31.1.1.1.1 | etsysIetfBridgeDot1dStpPortEntry | ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB |
| 1.3.6.1.4.1.5624.1.2.31.1.1.1.1.4 | etsysIetfBridgeDot1dStpPortCistNonForwardingReason | ENTERASYS-IETF-BRIDGE-MIB-EXT-MIB |