BAY-STACK-IGMP-EXT-MIB :: bsIgmpExtFilterProfileDroppedPackets

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BAY-STACK-IGMP-EXT-MIB › bsIgmpExtFilterProfileDroppedPackets

bsIgmpExtFilterProfileDroppedPackets

Module: BAY-STACK-IGMP-EXT-MIB

OID (symbolic): BAY-STACK-IGMP-EXT-MIB::bsIgmpExtFilterProfileDroppedPackets

OID (numeric): 1.3.6.1.4.1.45.5.32.1.1.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of packets that were matched by this profile and dropped.

What is bsIgmpExtFilterProfileDroppedPackets?

Reports the number of IGMP packets that matched a specific filter profile and were subsequently dropped. This counter helps administrators measure the effectiveness and traffic impact of a filter profile.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.5.32.1.1.1.5
snmpwalk -v2c -c public <target> BAY-STACK-IGMP-EXT-MIB::bsIgmpExtFilterProfileDroppedPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.5.32.1.1.1.5.1
snmpget -v2c -c public <target> BAY-STACK-IGMP-EXT-MIB::bsIgmpExtFilterProfileDroppedPackets.1

Start monitoring Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BAY-STACK-IGMP-EXT-MIB::bsIgmpExtFilterProfileDroppedPackets OID value, configure state conditions and alerts, and monitor any Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) from a single console.

How to Use in IPNetwork Monitor

Select an Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (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 bsIgmpExtFilterProfileDroppedPackets 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 were matched by this profile and dropped. 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 Counter32-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.45synopticsSYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.5bayStackMibsSYNOPTICS-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.5.32bayStackIgmpExtMibBAY-STACK-IGMP-EXT-MIB
1.3.6.1.4.1.45.5.32.1bsIgmpExtObjectsBAY-STACK-IGMP-EXT-MIB
1.3.6.1.4.1.45.5.32.1.1bsIgmpExtFilterProfileTableBAY-STACK-IGMP-EXT-MIB
1.3.6.1.4.1.45.5.32.1.1.1bsIgmpExtFilterProfileEntryBAY-STACK-IGMP-EXT-MIB
1.3.6.1.4.1.45.5.32.1.1.1.5bsIgmpExtFilterProfileDroppedPacketsBAY-STACK-IGMP-EXT-MIB