TE-MIB :: teTunnelRerouted

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTE-MIBteTunnelRerouted

teTunnelRerouted

Module: TE-MIB

OID (symbolic): TE-MIB::teTunnelRerouted

OID (numeric): 1.3.6.1.2.1.122.0.4

Node type: NOTIFICATION-TYPE

Description: A teTunnelRerouted notification is generated when an active path for the Tunnel indexed by teTunnelName stays the same, but its route changes.

This notification MUST be limited to at most one every minute, in case the tunnel reroutes quickly.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' TE-MIB::teTunnelRerouted
snmptrap -v2c -c public <manager> '' 1.3.6.1.2.1.122.0.4

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:61851->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (247454619) 28 days, 15:22:26.19
  SNMPv2-MIB::snmpTrapOID.0 = OID: TE-MIB::teTunnelRerouted

Start monitoring MPLS-TE capable routers, vendor-neutral standards-based MIB (RFC 3970) (traffic-engineering tunnel/LSP status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TE-MIB::teTunnelRerouted OID value, configure state conditions and alerts, and monitor any MPLS-TE capable routers, vendor-neutral standards-based MIB (RFC 3970) (traffic-engineering tunnel/LSP status) from a single console.

OID Breakdown

Upper-level ancestors (6 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.122teMIBTE-MIB
1.3.6.1.2.1.122.0teMIBNotificationsTE-MIB
1.3.6.1.2.1.122.0.4teTunnelReroutedTE-MIB