RAPID-CITY :: rcStatOspfRxBadPackets

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › RAPID-CITY › rcStatOspfRxBadPackets

rcStatOspfRxBadPackets

Module: RAPID-CITY

OID (symbolic): RAPID-CITY::rcStatOspfRxBadPackets

OID (numeric): 1.3.6.1.4.1.2272.1.12.3.9

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Used to indicate the number of packets received by OSPF that are bad.

What is rcStatOspfRxBadPackets?

This counter tracks the total number of malformed or invalid OSPF routing protocol packets received by the network device. Network operators examine this metric to diagnose OSPF protocol problems, configuration mismatches, or link quality issues that may cause routing information to be discarded.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2272.1.12.3.9
snmpwalk -v2c -c public <target> RAPID-CITY::rcStatOspfRxBadPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2272.1.12.3.9.1
snmpget -v2c -c public <target> RAPID-CITY::rcStatOspfRxBadPackets.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::rcStatOspfRxBadPackets 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.12rcStatRAPID-CITY
1.3.6.1.4.1.2272.1.12.3rcStatOspfRAPID-CITY
1.3.6.1.4.1.2272.1.12.3.9rcStatOspfRxBadPacketsRAPID-CITY