EXTREME-ACL-MIB :: extremeAclStatsPktCount

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EXTREME-ACL-MIB › extremeAclStatsPktCount

extremeAclStatsPktCount

Module: EXTREME-ACL-MIB

OID (symbolic): EXTREME-ACL-MIB::extremeAclStatsPktCount

OID (numeric): 1.3.6.1.4.1.1916.1.48.1.1.1.5

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The total number of packets that matches this rule.

What is extremeAclStatsPktCount?

This read-only counter tracks the total number of packets that have matched a specific access control list (ACL) rule on an Extreme switch since the counter was last reset or the device rebooted. A network administrator monitors this to verify that a security or QoS ACL rule is actually being hit by real traffic, or to quantify how much traffic a particular filtering rule is affecting. For example, a rapidly climbing count on a rule that blocks a specific source subnet would indicate that subnet is actively sending traffic the switch is dropping.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1916.1.48.1.1.1.5
snmpwalk -v2c -c public <target> EXTREME-ACL-MIB::extremeAclStatsPktCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1916.1.48.1.1.1.5.1
snmpget -v2c -c public <target> EXTREME-ACL-MIB::extremeAclStatsPktCount.1

Start monitoring Extreme Networks switches and routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EXTREME-ACL-MIB::extremeAclStatsPktCount OID value, configure state conditions and alerts, and monitor any Extreme Networks switches and routers from a single console.

How to Use in IPNetwork Monitor

Select an Extreme Networks switch or router 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 extremeAclStatsPktCount 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. The total number of packets that matches this 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.1916extremeA3COM51-SS9000SX
1.3.6.1.4.1.1916.1extremeAgentEXTREME-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1916.1.48extremeAclEXTREME-ACL-MIB
1.3.6.1.4.1.1916.1.48.1extremeAclObjectsEXTREME-ACL-MIB
1.3.6.1.4.1.1916.1.48.1.1extremeAclStatsTableEXTREME-ACL-MIB
1.3.6.1.4.1.1916.1.48.1.1.1extremeAclStatsEntryEXTREME-ACL-MIB
1.3.6.1.4.1.1916.1.48.1.1.1.5extremeAclStatsPktCountEXTREME-ACL-MIB