DOCS-SUBMGT-MIB :: docsSubMgtPktFilterMatches

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › DOCS-SUBMGT-MIB › docsSubMgtPktFilterMatches

docsSubMgtPktFilterMatches

Module: DOCS-SUBMGT-MIB

OID (symbolic): DOCS-SUBMGT-MIB::docsSubMgtPktFilterMatches

OID (numeric): 1.3.6.1.3.83.4.1.6.1.11

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This object counts the number of times this specific rule has been matched. This is incremented any time this rule is encountered and all components match. It is only incremented for the first (lowest-indexed) filter matching a packet.

What is docsSubMgtPktFilterMatches?

Running count of how many times this specific filter rule has matched a packet, incremented only for the first (lowest-indexed) rule a packet hits, useful for confirming a classifier is actually being exercised.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.3.83.4.1.6.1.11
snmpwalk -v2c -c public <target> DOCS-SUBMGT-MIB::docsSubMgtPktFilterMatches

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.3.83.4.1.6.1.11.1
snmpget -v2c -c public <target> DOCS-SUBMGT-MIB::docsSubMgtPktFilterMatches.1

Start monitoring DOCSIS CMTS (subscriber CPE IP control, vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOCS-SUBMGT-MIB::docsSubMgtPktFilterMatches OID value, configure state conditions and alerts, and monitor any DOCSIS CMTS (subscriber CPE IP control, vendor-neutral IETF standard) from a single console.

How to Use in IPNetwork Monitor

Select a DOCSIS CMT (subscriber CPE IP control, vendor-neutral IETF standard) 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 docsSubMgtPktFilterMatches 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. This object counts the number of times this specific rule has been matched. 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 (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.3experimentalAPERTUS-NPG-MIB
1.3.6.1.3.83docsDevEXP-DOCS-CABLE-DEVICE-MIB
Numeric OIDNameModule
1.3.6.1.3.83.4docsSubMgtDOCS-SUBMGT-MIB
1.3.6.1.3.83.4.1docsSubMgtObjectsDOCS-SUBMGT-MIB
1.3.6.1.3.83.4.1.6docsSubMgtPktFilterTableDOCS-SUBMGT-MIB
1.3.6.1.3.83.4.1.6.1docsSubMgtPktFilterEntryDOCS-SUBMGT-MIB
1.3.6.1.3.83.4.1.6.1.11docsSubMgtPktFilterMatchesDOCS-SUBMGT-MIB