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.
Parsed from file MPLS-TE-STD-MIB.mib
Module: MPLS-TE-STD-MIB
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.
mplsTunnelCHopAddrUnnum OBJECT-TYPE
SYNTAX TeHopAddressUnnum
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
View at oid-info.com
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.
Parsed from file rfc3812-MPLS-Traffic-Engineering-TE.mib.txt
Company: None
Module: MPLS-TE-STD-MIB
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.
mplsTunnelCHopAddrUnnum OBJECT-TYPE SYNTAX TeHopAddressUnnum MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { mplsTunnelCHopEntry 7 }
mplsTunnelCHopAddrUnnum OBJECT-TYPE SYNTAX TeHopAddressUnnum ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { mplsTunnelCHopEntry 7 }
Automatically extracted from RFC3812
mplsTunnelCHopAddrUnnum OBJECT-TYPE SYNTAX TeHopAddressUnnum MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { mplsTunnelCHopEntry 7 }
mplsTunnelCHopAddrUnnum OBJECT-TYPE SYNTAX TeHopAddressUnnum MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { mplsTunnelCHopEntry 7 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.10.166.3.2.8.1.1 | mplsTunnelCHopListIndex | 0 | 0 | Primary index into this table identifying a particular computed hop list. |
1.3.6.1.2.1.10.166.3.2.8.1.2 | mplsTunnelCHopIndex | 0 | 0 | Secondary index into this table identifying the particular hop. |
1.3.6.1.2.1.10.166.3.2.8.1.3 | mplsTunnelCHopAddrType | 0 | 0 | The Hop Address Type of this tunnel hop. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP. |
1.3.6.1.2.1.10.166.3.2.8.1.4 | mplsTunnelCHopIpAddr | 0 | 0 | The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelCH… |
1.3.6.1.2.1.10.166.3.2.8.1.5 | mplsTunnelCHopIpPrefixLen | 0 | 0 | If mplsTunnelCHopAddrType is set to ipv4(1) or ipv6(2), then this value will contain an appropriate prefix length for the IP addr… |
1.3.6.1.2.1.10.166.3.2.8.1.6 | mplsTunnelCHopAsNumber | 0 | 0 | If mplsTunnelCHopAddrType is set to asnumber(3), then this value will contain the AS number of this hop. Otherwise the agent shou… |
1.3.6.1.2.1.10.166.3.2.8.1.8 | mplsTunnelCHopLspId | 0 | 0 | If mplsTunnelCHopAddrType is set to lspid(5), then this value will contain the LSP ID of this hop. This object is otherwise insig… |
1.3.6.1.2.1.10.166.3.2.8.1.9 | mplsTunnelCHopType | 0 | 0 | Denotes whether this is tunnel hop is routed in a strict or loose fashion. |