All MIBs › ASCEND-MIBPRROUTE-MIB
Category: Routing Protocols, Vendor: Ascend/Lucent
Description: Manages policy-based routing rules and next-hop selection on Ascend WAN 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-MIBPRROUTE-MIB?
ASCEND-MIBPRROUTE-MIB is a proprietary Ascend module governing policy-based routing rules and next-hop selection on Ascend WAN access equipment. It exposes configuration data defining routing policies that override default destination-based routing, selecting next-hops based on criteria such as source address or traffic type. Its monitoring role is primarily around software/configuration status — verifying policy routes are correctly applied and active — since an incorrect or missing policy route causes traffic to take an unintended (or no) path rather than producing a gradual performance symptom. It has no direct IETF standard counterpart, functioning as Ascend's proprietary policy-routing extension. It is deployed on WAN access routers where traffic needs to be steered along non-default paths, such as multi-homed enterprise or ISP edge routers. Engineers can download the ASCEND-MIBPRROUTE-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ASCEND-MIBPRROUTE-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 MAX/Pipeline WAN access routers (TAOS-based)
Monitoring Examples
This module's sample_objects list was empty, so the following is inferred from its stated purpose rather than confirmed object names. An administrator would check policy route table entries to confirm the expected next-hop is configured for a given traffic policy, and would investigate if traffic matching that policy was observed taking the default route instead of the intended path. This is normally cross-checked against the standard IP routing table to distinguish policy-routing issues from general routing failures.
What Can Be Monitored
- policy route rule configuration
- next-hop selection per policy
- policy route active/inactive status
Imported Objects
OIDs
RFC description
Defines private route table profile management for Ascend routing and switching platforms.
Start monitoring Ascend MAX/Pipeline WAN access routers 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.