BAYSTACK-IPV6-FIRST-HOP-SEC-MIB :: bsIpv6FHSSbtTblOverFlow

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBAYSTACK-IPV6-FIRST-HOP-SEC-MIBbsIpv6FHSSbtTblOverFlow

bsIpv6FHSSbtTblOverFlow

Module: BAYSTACK-IPV6-FIRST-HOP-SEC-MIB

OID (symbolic): BAYSTACK-IPV6-FIRST-HOP-SEC-MIB::bsIpv6FHSSbtTblOverFlow

OID (numeric): 1.3.6.1.4.1.45.5.45.1.1.9

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: SBT Table Overflow due to the maximum SBT entry restriction

What is bsIpv6FHSSbtTblOverFlow?

Reports whether the Secure Binding Table has overflowed due to reaching the configured maximum entry limit. Monitoring this value helps detect situations where legitimate IPv6 bindings are being dropped.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.5.45.1.1.9
snmpwalk -v2c -c public <target> BAYSTACK-IPV6-FIRST-HOP-SEC-MIB::bsIpv6FHSSbtTblOverFlow

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.5.45.1.1.9.1
snmpget -v2c -c public <target> BAYSTACK-IPV6-FIRST-HOP-SEC-MIB::bsIpv6FHSSbtTblOverFlow.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 BAYSTACK-IPV6-FIRST-HOP-SEC-MIB::bsIpv6FHSSbtTblOverFlow 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 bsIpv6FHSSbtTblOverFlow into the Find box to locate it in the OID tree, then select it and click OK. It reports sBT Table Overflow due to the maximum SBT entry restriction. 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 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.5bayStackMibsSYNOPTICS-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.5.45bayStackIpv6FirstHopSecMibBAYSTACK-IPV6-FIRST-HOP-SEC-MIB
1.3.6.1.4.1.45.5.45.1bsIpv6FirstHopSecObjectsBAYSTACK-IPV6-FIRST-HOP-SEC-MIB
1.3.6.1.4.1.45.5.45.1.1bsIpv6FHSScalVarBAYSTACK-IPV6-FIRST-HOP-SEC-MIB
1.3.6.1.4.1.45.5.45.1.1.9bsIpv6FHSSbtTblOverFlowBAYSTACK-IPV6-FIRST-HOP-SEC-MIB