RAPID-CITY :: rcStgPortInBadBpdus

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › RAPID-CITY › rcStgPortInBadBpdus

rcStgPortInBadBpdus

Module: RAPID-CITY

OID (symbolic): RAPID-CITY::rcStgPortInBadBpdus

OID (numeric): 1.3.6.1.4.1.2272.1.13.5.1.15

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of Bad BPUDs received by this port.

What is rcStgPortInBadBpdus?

This counter tracks the number of malformed Bridge Protocol Data Units (BPDUs) received on a spanning tree port. Bad BPDUs indicate either corrupted frames or non-compliant neighbor devices sending invalid spanning tree messages. Operators investigate high counts to identify switch configuration errors or faulty equipment in the network.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2272.1.13.5.1.15
snmpwalk -v2c -c public <target> RAPID-CITY::rcStgPortInBadBpdus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2272.1.13.5.1.15.1
snmpget -v2c -c public <target> RAPID-CITY::rcStgPortInBadBpdus.1

Start monitoring Bay Networks/Nortel Accelar and Ethernet Routing Switch (ERS) chassis switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RAPID-CITY::rcStgPortInBadBpdus OID value, configure state conditions and alerts, and monitor any Bay Networks/Nortel Accelar and Ethernet Routing Switch (ERS) chassis switches from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.2272rapidCityRAPID-CITY
1.3.6.1.4.1.2272.1rcMgmtRAPID-CITY
1.3.6.1.4.1.2272.1.13rcStgRAPID-CITY
1.3.6.1.4.1.2272.1.13.5rcStgPortTableRAPID-CITY
1.3.6.1.4.1.2272.1.13.5.1rcStgPortEntryRAPID-CITY
1.3.6.1.4.1.2272.1.13.5.1.15rcStgPortInBadBpdusRAPID-CITY