RIVERSTONE-CMTS-MIB :: rsCmtsBaseBpduFilterHits

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RIVERSTONE-CMTS-MIB › rsCmtsBaseBpduFilterHits

rsCmtsBaseBpduFilterHits

Module: RIVERSTONE-CMTS-MIB

OID (symbolic): RIVERSTONE-CMTS-MIB::rsCmtsBaseBpduFilterHits

OID (numeric): 1.3.6.1.4.1.5567.2.11.1.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Counts number of BPDU filter hits on the headend.

What is rsCmtsBaseBpduFilterHits?

A running count of how many BPDU frames the headend's BPDU filter has blocked, which an admin checks to confirm rsCmtsBaseBpduFilter is actually catching unwanted spanning-tree traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5567.2.11.1.1.3
snmpwalk -v2c -c public <target> RIVERSTONE-CMTS-MIB::rsCmtsBaseBpduFilterHits

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5567.2.11.1.1.3.1
snmpget -v2c -c public <target> RIVERSTONE-CMTS-MIB::rsCmtsBaseBpduFilterHits.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> rsCmtsBaseBpduFilterHits.1

Start monitoring Riverstone Networks CMTS (cable modem termination system) modules (DOCSIS traffic filtering/config) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RIVERSTONE-CMTS-MIB::rsCmtsBaseBpduFilterHits OID value, configure state conditions and alerts, and monitor any Riverstone Networks CMTS (cable modem termination system) modules (DOCSIS traffic filtering/config) from a single console.

How to Use in IPNetwork Monitor

Select a Riverstone Networks CMTS (cable modem termination system) module (DOCSIS traffic filtering/config) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type rsCmtsBaseBpduFilterHits into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. Counts number of BPDU filter hits on the headend. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

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.5567riverstoneNetworksRIVERSTONE-SMI-MIB
1.3.6.1.4.1.5567.2riverstoneMibsRIVERSTONE-SMI-MIB
Numeric OIDNameModule
1.3.6.1.4.1.5567.2.11rsCmtsMibRIVERSTONE-CMTS-MIB
1.3.6.1.4.1.5567.2.11.1rsCmtsBaseTableRIVERSTONE-CMTS-MIB
1.3.6.1.4.1.5567.2.11.1.1rsCmtsBaseEntryRIVERSTONE-CMTS-MIB
1.3.6.1.4.1.5567.2.11.1.1.3rsCmtsBaseBpduFilterHitsRIVERSTONE-CMTS-MIB