ATM-REROUTING-MIB :: reroutingVpReroutingOperationSuccessCounter

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ATM-REROUTING-MIB › reroutingVpReroutingOperationSuccessCounter

reroutingVpReroutingOperationSuccessCounter

Module: ATM-REROUTING-MIB

OID (symbolic): ATM-REROUTING-MIB::reroutingVpReroutingOperationSuccessCounter

OID (numeric): 1.3.6.1.4.1.353.5.9.3.1.1.3.1.6

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Indicates the number of rerouting operations initiated by this node that succeeded on this call.

The establishment of the initial call is not counted

What is reroutingVpReroutingOperationSuccessCounter?

Tracks how many ATM VP (Virtual Path) rerouting operations initiated by this node have completed successfully for a given call. The initial call setup is excluded from this count.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.353.5.9.3.1.1.3.1.6
snmpwalk -v2c -c public <target> ATM-REROUTING-MIB::reroutingVpReroutingOperationSuccessCounter

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.353.5.9.3.1.1.3.1.6.1
snmpget -v2c -c public <target> ATM-REROUTING-MIB::reroutingVpReroutingOperationSuccessCounter.1

Start monitoring ATM switches supporting PNNI rerouting with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ATM-REROUTING-MIB::reroutingVpReroutingOperationSuccessCounter OID value, configure state conditions and alerts, and monitor any ATM switches supporting PNNI rerouting from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.353atmForumATM-DXI-MIB
1.3.6.1.4.1.353.5atmForumNetworkManagementATM-FORUM-SNMP-M4-MIB
1.3.6.1.4.1.353.5.9atmfSignallingATM-POLICY-CONSTRAINT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.353.5.9.3atmfReroutingATM-REROUTING-MIB
1.3.6.1.4.1.353.5.9.3.1atmfreroutingMIBATM-REROUTING-MIB
1.3.6.1.4.1.353.5.9.3.1.1reroutingMIBObjectsATM-REROUTING-MIB
1.3.6.1.4.1.353.5.9.3.1.1.3reroutingVpTableATM-REROUTING-MIB
1.3.6.1.4.1.353.5.9.3.1.1.3.1reroutingVpEntryATM-REROUTING-MIB
1.3.6.1.4.1.353.5.9.3.1.1.3.1.6reroutingVpReroutingOperationSuccessCounterATM-REROUTING-MIB