MPLS-TE-MIB :: mplsTunnelHopListIndexNext

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsMPLS-TE-MIBmplsTunnelHopListIndexNext

mplsTunnelHopListIndexNext

Module: MPLS-TE-MIB

OID (symbolic): MPLS-TE-MIB::mplsTunnelHopListIndexNext

OID (numeric): 1.3.6.1.3.95.2.3

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: This object contains an appropriate value to be used for mplsTunnelHopListIndex when creating entries in the mplsTunnelHopTable. If the number of unassigned entries is exhausted, a retrival operation will return a value of 0. This object may also return a value of 0 when the LSR is unable to accept conceptual row creation, for example, if the mplsTunnelHopTable is implemented as read-only. To obtain the value of mplsTunnelHopListIndex for a new entry in the mplsTunnelHopTable, the manager issues a management protocol retrieval operation to obtain the current value of mplsTunnelHopIndex. After each retrieval operation, the agent should modify the value to reflect the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.

What is mplsTunnelHopListIndexNext?

Hands an admin the next free mplsTunnelHopListIndex value to use when defining a new explicit-route hop list for a tunnel; a value of 0 means either indexes are exhausted or the table doesn't support row creation on this device.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.3.95.2.3
snmpwalk -v2c -c public <target> MPLS-TE-MIB::mplsTunnelHopListIndexNext

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.3.95.2.3.1
snmpget -v2c -c public <target> MPLS-TE-MIB::mplsTunnelHopListIndexNext.1

Start monitoring Vendor-neutral IETF standard (MPLS-enabled provider-edge/core router, Traffic Engineering) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MPLS-TE-MIB::mplsTunnelHopListIndexNext OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (MPLS-enabled provider-edge/core router, Traffic Engineering) from a single console.

OID Breakdown

Upper-level ancestors (5 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.3experimentalAXON-MIB
Numeric OIDNameModule
1.3.6.1.3.95mplsTeMIBMPLS-TE-MIB
1.3.6.1.3.95.2mplsTeObjectsMPLS-TE-MIB
1.3.6.1.3.95.2.3mplsTunnelHopListIndexNextMPLS-TE-MIB