All MIBs › ASCEND-MIBOSPFVLNK-MIB
Category: Routing Protocols, Vendor: Ascend/Lucent
Description: Manages OSPF virtual link configuration and parameters on Ascend access equipment.
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 ASCEND-MIBOSPFVLNK-MIB?
ASCEND-MIBOSPFVLNK-MIB is a vendor-specific MIB from Ascend Communications (later acquired by Lucent) covering OSPF virtual link configuration on Ascend access and routing equipment. It exposes routing-protocol configuration data, specifically parameters for OSPF virtual links used to connect non-backbone areas to the OSPF backbone across a transit area. This is primarily a configuration and routing-topology module rather than a hardware health module, though its state fields can indicate whether a virtual link is currently up or down, which is important for detecting routing faults. It extends and depends on the standard OSPF-MIB (RFC 1850/4750) since virtual links are a native OSPF concept, adding Ascend-specific parameters not covered by the standard MIB. It is typically deployed in Ascend routers acting as Area Border Routers within enterprise or carrier OSPF networks. Engineers can download the ASCEND-MIBOSPFVLNK-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ASCEND-MIBOSPFVLNK-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
- Ascend routers
- Ascend/Lucent access equipment
Monitoring Examples
No sample objects were included for this MIB, so exact object names cannot be verified from source, but one would expect a virtual-link table (something like ospfVirtLinkTable-style entries) keyed by transit area ID and neighbor router ID. An administrator would poll such entries to confirm a virtual link's operational state and authentication settings, revealing a routing outage if a virtual link that should be up shows as down. This would explain a loss of reachability to a non-backbone OSPF area.
What Can Be Monitored
- OSPF virtual link operational state
- transit area configuration
- virtual neighbor router ID
- virtual link authentication settings
Imported Objects
OIDs
RFC description
Manages OSPF virtual interface profiles and link configuration parameters. Controls authentication, timers, and neighbor relationships for OSPF virtual links.
Start monitoring Ascend Communications (Lucent) MAX/Pipeline/TNT WAN access equipment (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.