AVAYA-WLAN-MIB :: filterPackets

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAVAYA-WLAN-MIBfilterPackets

filterPackets

Module: AVAYA-WLAN-MIB

OID (symbolic): AVAYA-WLAN-MIB::filterPackets

OID (numeric): 1.3.6.1.4.1.45.8.1.1.11.4.1.34

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The number of packets that matched the filter

What is filterPackets?

A running counter of how many packets have matched this filter rule so far, useful for confirming a filter is actually being hit as expected.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.8.1.1.11.4.1.34
snmpwalk -v2c -c public <target> AVAYA-WLAN-MIB::filterPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.8.1.1.11.4.1.34.1
snmpget -v2c -c public <target> AVAYA-WLAN-MIB::filterPackets.1

Start monitoring Avaya wireless access points and WLAN controllers (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVAYA-WLAN-MIB::filterPackets OID value, configure state conditions and alerts, and monitor any Avaya wireless access points and WLAN controllers (legacy) from a single console.

How to Use in IPNetwork Monitor

Select an Avaya wireless access point or WLAN controller (legacy) 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 filterPackets 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 number of packets that matched the filter. 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.45synopticsSYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.8avayaWlan9100MibsSYNOPTICS-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.8.1wlanAVAYA-WLAN-MIB
1.3.6.1.4.1.45.8.1.1wapAVAYA-WLAN-MIB
1.3.6.1.4.1.45.8.1.1.11filterAVAYA-WLAN-MIB
1.3.6.1.4.1.45.8.1.1.11.4filterTableAVAYA-WLAN-MIB
1.3.6.1.4.1.45.8.1.1.11.4.1filterEntryAVAYA-WLAN-MIB
1.3.6.1.4.1.45.8.1.1.11.4.1.34filterPacketsAVAYA-WLAN-MIB