ATM-REROUTING-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ATM-REROUTING-MIB

Organization: The ATM Forum

Last Updated: 2001-04-26

Category: ATM

Description: Manages ATM connection rerouting procedures, monitoring reroute triggers, path selection, and restoration statistics.

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 ATM-REROUTING-MIB?

ATM-REROUTING-MIB is a vendor-neutral ATM Forum MIB (version 1.0) for managing domain-based rerouting of active point-to-point ATM calls, used for network restoration/resiliency. It exposes rerouting capability and version information, a hard-rerouting timer, and filter tables that determine which interfaces, connection kinds, service categories, or calling-party prefixes are eligible for automatic rerouting. This is primarily control-plane/configuration data governing restoration behavior rather than raw hardware sensors, though a spike in triggered reroutes on a given interface reflects underlying path or link instability. It depends on the ATM Forum's signalling (atmfSignalling) and network management framework. It is deployed on ATM switches participating in PNNI-based call rerouting for network resiliency. Engineers implementing or auditing this functionality typically reference the ATM-REROUTING-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in ATM-REROUTING-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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • ATM switch supporting PNNI rerouting

Monitoring Examples

An admin would check reroutingCapabilitiesSupported and reroutingHardReroutingTime to confirm the switch's rerouting behavior and timer, then inspect reroutingFilterTable/reroutingFilterEntry indexed by reroutingFilterIndex to verify filters such as reroutingFilterServiceCategory and reroutingFilterCallingPartyPrefix correctly scope which calls can be rerouted. A rising count of reroutes tied to a specific reroutingFilterInterface would point to instability on that link or path.

What Can Be Monitored

  • rerouting capability/version
  • hard rerouting timer
  • reroute filter rules per interface
  • eligible call/service categories
Imported Objects

From ATM-MIB

atmVclVciOBJECT-TYPE
atmVclVpiOBJECT-TYPE
atmVplVpiOBJECT-TYPE

From ATM-TC-MIB

AtmAddr

From IF-MIB

InterfaceIndex
ifIndexOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32
enterprises

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using reroutingVpReroutingOperationSuccessCounter OID:

Select an ATM switch supporting PNNI rerouting as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type reroutingVpReroutingOperationSuccessCounter into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. Indicates the number of rerouting operations initiated by this node that succeeded on this call. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

ATM Forum domain-based rerouting MIB for configuring and monitoring rerouting services on point-to-point ATM calls on switches and end systems.

Start monitoring ATM switches supporting PNNI rerouting 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.

Download ATM-REROUTING-MIB