H3C-OBJP-MIB :: h3cObjpZonePairMatchPacketCount

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › H3C-OBJP-MIB › h3cObjpZonePairMatchPacketCount

h3cObjpZonePairMatchPacketCount

Module: H3C-OBJP-MIB

OID (symbolic): H3C-OBJP-MIB::h3cObjpZonePairMatchPacketCount

OID (numeric): 1.3.6.1.4.1.2011.10.2.155.1.1.1.5

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Number of packets matching the rule.

What is h3cObjpZonePairMatchPacketCount?

This read-only counter reports the number of packets that have matched a specific zone-pair object-policy rule on the H3C device, a rule that governs traffic flowing between two defined security zones. An administrator monitors this to verify a security policy rule between two zones is actually being exercised by real traffic, useful for confirming a rule is correctly matching the traffic it was written for. For example, a zone-pair rule intended to permit traffic from a "DMZ" zone to a "Trust" zone would show a rising packet count here as long as that traffic pattern continues to occur.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.155.1.1.1.5
snmpwalk -v2c -c public <target> H3C-OBJP-MIB::h3cObjpZonePairMatchPacketCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2011.10.2.155.1.1.1.5.1
snmpget -v2c -c public <target> H3C-OBJP-MIB::h3cObjpZonePairMatchPacketCount.1

Start monitoring H3C Comware switch/router/security gateway (object-policy management) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the H3C-OBJP-MIB::h3cObjpZonePairMatchPacketCount OID value, configure state conditions and alerts, and monitor any H3C Comware switch/router/security gateway (object-policy management) from a single console.

How to Use in IPNetwork Monitor

Select an H3C Comware switch/router/security gateway (object-policy management) 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 h3cObjpZonePairMatchPacketCount 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 (9 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.2011huaweiEXPERTV2-MIB
1.3.6.1.4.1.2011.10h3cHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.10.2h3cCommonHUAWEI-3COM-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2011.10.2.155h3cObjpH3C-OBJP-MIB
1.3.6.1.4.1.2011.10.2.155.1h3cObjpZonePairObjectsH3C-OBJP-MIB
1.3.6.1.4.1.2011.10.2.155.1.1h3cObjpZonePairRunningInfoTableH3C-OBJP-MIB
1.3.6.1.4.1.2011.10.2.155.1.1.1h3cObjpZonePairRunningInfoEntryH3C-OBJP-MIB
1.3.6.1.4.1.2011.10.2.155.1.1.1.5h3cObjpZonePairMatchPacketCountH3C-OBJP-MIB