No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

MIB Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document provides the function overview, relationships between tables, description of single objects, description of MIB tables, and description of alarm objects.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
mplsTunnelCHopTable

mplsTunnelCHopTable

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 ofthe 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 index of this table is mplsTunnelCHopListIndex and mplsTunnelCHopIndex.

OID

Object Name

Syntax

Max Access

Description

Implemented Specifications

1.3.6.1.2.1.10.166.3.2.8.1.1

mplsTunnelCHopListIndex

MplsPathIndex

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

MplsPathIndex

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

TeHopAddressType

Read-only

The Hop Address Type of this tunnel hop. Note that lspid (5) is a valid option only for tunnels signaled via CRLDP.

The default value is ipv4.

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

TeHopAddress

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 ID of the unnumbered interface. Otherwise the agent should set this object to the zero-length string and the manager SHOULD ignore this object.

The default value is 0x00000000.

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

InetAddressPrefixLength

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.

Currently, the return value 32 is supported only.

1.3.6.1.2.1.10.166.3.2.8.1.9

mplsTunnelCHopType

INTEGER{strict(1),loose(2)}

Read-only

Denotes whether this tunnel hop is routed in a strict or loose fashion.

The value list as below:

strict (1), loose (2)

This object is implemented as defined in the corresponding MIB files.

Creation Restriction

The entries of this table cannot be created.

Modification Restriction

The entries of this table cannot be modified.

Deletion Restriction

The entries of this table cannot be deleted.

Access Restriction

To access this table, there must be a tunnel that passes through the device and the cspf must be enabled.

Translation
Download
Updated: 2019-06-05

Document ID: EDOC1000097213

Views: 120637

Downloads: 681

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next