BAY-STACK-MIB

Description: Provides core system identification, stack configuration, and chassis management for Avaya/Nortel BayStack ERS switches.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

BAY-STACK-MIB is a legacy Bay Networks/Nortel (now Avaya) MIB providing core system identification, stack configuration, and chassis management for BayStack Ethernet Routing Switch (ERS) stackable switches. It exposes stack-level configuration such as expected stack size, error notification behavior, reboot-on-failure policy, and retry counts, along with a per-unit configuration table covering rear stacking port administrative and operational mode. This MIB supports hardware/software status monitoring by letting an administrator confirm the stack is at its expected member count (bayStackConfigExpectedStackSize) and that each unit's rear stacking port is operationally up (bayStackUnitConfigRearPortOperMode), which together reveal whether a stack member has dropped out or a stacking cable/port has failed. It is a vendor-specific enterprise MIB from the Bay Networks/Nortel/Avaya lineage, typically used alongside standard IF-MIB and Nortel's broader chassis MIBs for full device coverage. It is typically deployed on BayStack/Avaya ERS stackable Ethernet switches in enterprise wiring closets and campus networks. Network engineers evaluating or troubleshooting this functionality can download the BAY-STACK-MIB file directly to load it into their MIB browser.

An administrator would compare the actual number of responding units against bayStackConfigExpectedStackSize to detect a stack member that has dropped offline, then check bayStackUnitConfigTable's bayStackUnitConfigRearPortOperMode against bayStackUnitConfigRearPortAdminMode for that unit to see if a stacking port failure (operational mode not matching administrative mode) is the cause. bayStackConfigStackRebootUnitOnFailure and bayStackConfigStackRetryCount would be reviewed to understand whether the stack is configured to automatically reboot a failed unit and how many attempts it will make, informing whether an automatic recovery is expected or manual intervention is needed.

Bay Networks-private MIB for Ethernet stack and switch fabric management (legacy platform).