All MIBs › ASCEND-MIBDEST-MIB
Category: Routing Protocols, Vendor: Ascend/Lucent
Description: Manages destination-based routing configuration and next-hop tables on Ascend 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-MIBDEST-MIB?
ASCEND-MIBDEST-MIB is an Ascend Communications vendor-specific MIB, auto-generated by mibgen for TAOS 10.0.1 and later, that models destination-number dialing profiles rather than IP next-hop routing tables as its name might suggest. It defines a mibdestProfileTable keyed on destProfile-PlanNumber, holding a profile name (destProfile-Name), a destination-selection policy (destProfile-NumberOption: first-available, first-active, any-available), and an action trigger (destProfile-Action-o: create/delete profile), plus a nested mibdestProfile-DestNumberTable keyed on plan number and index that holds the actual destProfile-DestNumber-PhoneNumber and a destProfile-DestNumber-CallByCallId. This is a dial-plan/telephony destination configuration MIB for Ascend's dial-access equipment, not a generic Layer 3 routing MIB — monitoring it is useful for confirming which phone numbers are configured under a given destination plan and whether a profile's create/delete action has taken effect. It depends on ASCEND-MIB for the configuration OID subtree (configuration.73) it hangs off of, and it is deployed on Ascend dial-access/remote-access-server equipment running TAOS, where administrators can download the ASCEND-MIBDEST-MIB file to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in ASCEND-MIBDEST-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 dial-access (remote-access server) equipment running TAOS
Monitoring Examples
An operator polls mibdestProfileTable to review destProfile-NumberOption for a given destProfile-PlanNumber, then checks mibdestProfile-DestNumberTable for the destProfile-DestNumber-PhoneNumber entries under that plan; a profile stuck with destProfile-Action-o showing createProfile rather than noAction would indicate the create action never completed.
What Can Be Monitored
- destination profile plan table entries
- destination-number selection policy (first-avail/first-active/any-avail)
- profile create/delete action status
- per-plan phone number destination entries
- call-by-call ID mapping
Imported Objects
OIDs
RFC description
Ascend communications destination profile table for call routing and network configuration management.
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.