HH3C-SECP-MIB :: hh3cSecpMatchPacketCount

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HH3C-SECP-MIB › hh3cSecpMatchPacketCount

hh3cSecpMatchPacketCount

Module: HH3C-SECP-MIB

OID (symbolic): HH3C-SECP-MIB::hh3cSecpMatchPacketCount

OID (numeric): 1.3.6.1.4.1.25506.2.166.1.1.1.3

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Number of packets matching the rule.

What is hh3cSecpMatchPacketCount?

This read-only counter reports the number of packets that have matched a specific security-policy rule on the HH3C device. An administrator monitors this to confirm that a given security policy rule is actually being triggered by real traffic, useful when verifying newly written rules are working as intended. For example, a newly added rule intended to block traffic from a known-malicious IP range would show this counter increasing if such traffic is indeed hitting the device.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.166.1.1.1.3
snmpwalk -v2c -c public <target> HH3C-SECP-MIB::hh3cSecpMatchPacketCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.166.1.1.1.3.1
snmpget -v2c -c public <target> HH3C-SECP-MIB::hh3cSecpMatchPacketCount.1

Start monitoring H3C router/switch/security gateway (zone-based Security Policy rules) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-SECP-MIB::hh3cSecpMatchPacketCount OID value, configure state conditions and alerts, and monitor any H3C router/switch/security gateway (zone-based Security Policy rules) from a single console.

How to Use in IPNetwork Monitor

Select an H3C router/switch/security gateway (zone-based Security Policy rules) 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 hh3cSecpMatchPacketCount 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. It reports the number of packets matching the rule. 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 Counter64-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.25506hh3cHH3C-OID-MIB
1.3.6.1.4.1.25506.2hh3cCommonHH3C-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25506.2.166hh3cSecpHH3C-SECP-MIB
1.3.6.1.4.1.25506.2.166.1hh3cSecpObjectsHH3C-SECP-MIB
1.3.6.1.4.1.25506.2.166.1.1hh3cSecpRunningInfoTableHH3C-SECP-MIB
1.3.6.1.4.1.25506.2.166.1.1.1hh3cSecpRunningInfoEntryHH3C-SECP-MIB
1.3.6.1.4.1.25506.2.166.1.1.1.3hh3cSecpMatchPacketCountHH3C-SECP-MIB