All MIBs › BAY-STACK-OSPF-EXT-MIB
Organization: Nortel Networks
Last Updated: 2009-11-10
Category: Routing Protocols, Vendor: Avaya
Description: Extends OSPF protocol configuration with Avaya/Nortel ERS-specific route redistribution and area parameters.
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.
What Is BAY-STACK-OSPF-EXT-MIB?
BAY-STACK-OSPF-EXT-MIB is a Nortel/Avaya (Bay Networks lineage) extension to the standard OSPF MIB, adding vendor-specific route-redistribution and per-interface OSPF configuration parameters for Ethernet Routing Switch (ERS)/BayStack platforms. It exposes objects for route-redistribution control, hardware-compatibility mode, and an extended OSPF interface table covering settings like MD5 authentication keys, MTU-ignore behavior, and 'advertise when down' behavior, plus a message-digest key table and notifications. Its monitoring role is configuration/protocol-state oriented: administrators check whether OSPF interfaces are configured consistently (authentication, MTU handling) across the network and watch bsoeNotifications for routing-relevant events, rather than reading physical hardware sensors. It explicitly extends and depends on the standard OSPF-MIB, reusing its interface indexing (bsoeOspfIfIpAddress/bsoeOspfAddressLessIf mirror OSPF-MIB conventions). It is deployed on Nortel/Avaya BayStack and Ethernet Routing Switch platforms running OSPF in enterprise or carrier LAN/WAN environments. Engineers can download the BAY-STACK-OSPF-EXT-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in BAY-STACK-OSPF-EXT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Nortel/Avaya BayStack / Ethernet Routing Switch (ERS)
Monitoring Examples
An operator would check bsoeOspfIfExtTable/bsoeOspfIfExtEntry entries, keyed by bsoeOspfIfIpAddress/bsoeOspfAddressLessIf, for bsoeOspfIfExtMtuIgnore and bsoeOspfIfExtType to confirm two adjacent routers agree on MTU handling and interface type, since a mismatch here is a classic cause of OSPF adjacency flapping. Checking bsoeOspfIfExtPrimaryMd5Key against bsoeMessageDigestTable confirms authentication keys are consistent, and unexpected bsoeNotifications traps would flag a redistribution or adjacency change worth investigating.
What Can Be Monitored
- OSPF interface extended configuration (MTU-ignore, type)
- MD5 authentication key consistency
- route redistribution settings
- OSPF-related trap notifications
Imported Objects
From IF-MIB
| InterfaceIndex |
From OSPF-MIB
| AreaID | |
| RouterID |
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| RowStatus | |
| TruthValue |
From SYNOPTICS-ROOT-MIB
| bayStackMibs | OBJECT-IDENTITY |
OIDs
RFC description
Extends OSPF management on BayStack switches with support for virtual interfaces and MD5 authentication.
Start monitoring Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) 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.