The mplsTunnelCHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as computed by a constraint-
based routing protocol, based on the mplsTunnelHopTable for the outgoing direction of the tunnel. Thus at a transit LSR, this table (if the table is supported) MAY contain the path computed by the CSPF engine on (or on behalf of)
this LSR. Each row in this table is indexed by mplsTunnelCHopListIndex. Each row also has a secondary index mplsTunnelCHopIndex, corresponding to the next hop that this row corresponds to. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelCHopTable.
Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional. Furthermore, since the information in this table describes the path computed by the CSPF engine the entries in this table are read-only.
The indexes of the table are mplsTunnelCHopListIndex, mplsTunnelCHopIndex.
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
---|---|---|---|---|---|
1.3.6.1.2.1.10.166.3.2.8.1.1 |
mplsTunnelCHopListIndex |
Unsigned32{(1,4294967295)} |
not-accessible |
Primary index into this table identifying a particular computed hop list. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.2 |
mplsTunnelCHopIndex |
Unsigned32{(1,4294967295)} |
not-accessible |
Secondary index into this table identifying the particular hop. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.3 |
mplsTunnelCHopAddrType |
INTEGER{unknown(0),ipv4(1),ipv6(2),asnumber(3),unnum(4),lspid(5)} |
read-only |
The Hop Address Type of this tunnel hop. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.4 |
mplsTunnelCHopIpAddr |
OCTET STRING{(0,32)} |
read-only |
The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelCHopAddrType. If mplsTunnelCHopAddrType is set to unnum(4), then this value will contain the LSR Router ID of the unnumbered interface. Otherwise the agent should set this object to the zero-length string and the manager SHOULD ignore this object. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.5 |
mplsTunnelCHopIpPrefixLen |
Unsigned32{(0,2040)} |
read-only |
If mplsTunnelCHopAddrType is set to ipv4(1) or ipv6(2), then this value will contain an appropriate prefix length for the IP address in object mplsTunnelCHopIpAddr. Otherwise this value is irrelevant and should be ignored. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.6 |
mplsTunnelCHopAsNumber |
OCTET STRING{(4,4)} |
read-only |
If mplsTunnelCHopAddrType is set to asnumber(3), then this value will contain the AS number of this hop. Otherwise the agent should set this object to zero-length string and the manager should ignore this. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.7 |
mplsTunnelCHopAddrUnnum |
OCTET STRING{(4,4)} |
read-only |
If mplsTunnelCHopAddrType is set to unnum(4), then this value will contain the unnumbered interface identifier of this hop. This object should be used in conjunction with mplsTunnelCHopIpAddr which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero- length string and the manager should ignore this. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.8 |
mplsTunnelCHopLspId |
OCTET STRING{(2,2),(6,6)} |
read-only |
If mplsTunnelCHopAddrType is set to lspid(5), then this value will contain the LSP ID of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact. |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.10.166.3.2.8.1.9 |
mplsTunnelCHopType |
INTEGER{strict(1),loose(2)} |
read-only |
Denotes whether this is tunnel hop is routed in a strict or loose fashion. |
This object is implemented as defined in the corresponding MIB files. |