All MIBs › TE-MIB › teTunnelNextPathIndex
teTunnelNextPathIndex
Module: TE-MIB
OID (symbolic): TE-MIB::teTunnelNextPathIndex
OID (numeric): 1.3.6.1.2.1.122.1.2.1.3
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: An integer that may be used as a new Index for the next Path in this Tunnel.
The special value of 0 indicates that no more Paths can be created for this Tunnel, or that no more new entries can be created in tePathTable.
When this MIB module is used for configuration, this object always contains a legal value (if non-zero) for an index that is not currently used in that table. The Command Generator (Network Management Application) reads this variable and uses the (non-zero) value read when creating a new row with an SNMP SET. When the SET is performed, the Command Responder (agent) must determine whether the value is indeed still unused; Two Network Management Applications may attempt to create a row (configuration entry) simultaneously and use the same value. If it is currently unused, the SET succeeds, and the Command Responder (agent) changes the value of this object according to an implementation-specific algorithm. If the value is in use, however, the SET fails. The Network Management Application must then re-read this variable to obtain a new usable value.
What is teTunnelNextPathIndex?
The next unused path index available for creating a new path under this specific tunnel; a value of 0 means no more paths can be added to this tunnel.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.122.1.2.1.3 snmpwalk -v2c -c public <target> TE-MIB::teTunnelNextPathIndex
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.122.1.2.1.3.1 snmpget -v2c -c public <target> TE-MIB::teTunnelNextPathIndex.1
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::teTunnelNextPathIndex 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.122 | teMIB | TE-MIB |
| 1.3.6.1.2.1.122.1 | teMIBObjects | TE-MIB |
| 1.3.6.1.2.1.122.1.2 | teTunnelTable | TE-MIB |
| 1.3.6.1.2.1.122.1.2.1 | teTunnelEntry | TE-MIB |
| 1.3.6.1.2.1.122.1.2.1.3 | teTunnelNextPathIndex | TE-MIB |