ZXR10-PORTACL-MIB :: zxr10IPv4PortACLlogACLRuleHits

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsZXR10-PORTACL-MIBzxr10IPv4PortACLlogACLRuleHits

zxr10IPv4PortACLlogACLRuleHits

Module: ZXR10-PORTACL-MIB

OID (symbolic): ZXR10-PORTACL-MIB::zxr10IPv4PortACLlogACLRuleHits

OID (numeric): 1.3.6.1.4.1.3902.3.1100.2.7.1.6

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Rule hits of matching packets on the interface, Maximum(18446744073709551615): invalid log statistics because of lack of counter resources in PM

What is zxr10IPv4PortACLlogACLRuleHits?

This is a 64-bit counter of how many packets on this interface matched this specific ACL rule; the maximum value, all binary ones, specifically means the log statistic is invalid due to a lack of counter resources in the device's packet-processing hardware. Admins use it to see which individual rules within an ACL are actually being hit, rather than just the overall pass/deny outcome.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.1100.2.7.1.6
snmpwalk -v2c -c public <target> ZXR10-PORTACL-MIB::zxr10IPv4PortACLlogACLRuleHits

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.1100.2.7.1.6.1
snmpget -v2c -c public <target> ZXR10-PORTACL-MIB::zxr10IPv4PortACLlogACLRuleHits.1

SNMPv3 example:

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

Start monitoring ZTE ZXR10 switch (per-port ACL rule-binding/match-activity status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZXR10-PORTACL-MIB::zxr10IPv4PortACLlogACLRuleHits OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 switch (per-port ACL rule-binding/match-activity status) from a single console.

How to Use in IPNetwork Monitor

Select a ZTE ZXR10 switch (per-port ACL rule-binding/match-activity status) 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 zxr10IPv4PortACLlogACLRuleHits 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 rule hits of matching packets on the interface, Maximum(18446744073709551615): invalid log statistics because of lack of counter resources in PM. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. 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.3902zteUAS-MIB
1.3.6.1.4.1.3902.3zxr10ZXR10-BFD-MIB
Numeric OIDNameModule
1.3.6.1.4.1.3902.3.1100zxr10AclMIBZXR10-PORTACL-MIB
1.3.6.1.4.1.3902.3.1100.2zxr10PortACLZXR10-PORTACL-MIB
1.3.6.1.4.1.3902.3.1100.2.7zxr10IPv4PortACLlogTableZXR10-PORTACL-MIB
1.3.6.1.4.1.3902.3.1100.2.7.1zxr10IPv4PortACLlogEntryZXR10-PORTACL-MIB
1.3.6.1.4.1.3902.3.1100.2.7.1.6zxr10IPv4PortACLlogACLRuleHitsZXR10-PORTACL-MIB