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

Command Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
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).
Basic MPLS Configuration Commands

Basic MPLS Configuration Commands

authentication exclude

Function

The authentication exclude command configures LDP peers in a batch that a local device does not authenticate after LDP keychain or LDP MD5 is configured to authenticate all LDP peers or LDP peers in a specified group.

The undo authentication exclude command enables a local device to authenticate all LDP peers using LDP keychain or LDP MD5.

By default, a local device is enabled to authenticate all LDP peers using LDP keychain or LDP MD5.

Format

authentication exclude peer peer-id

undo authentication exclude peer peer-id

Parameters

Parameter Description Value
peer peer-id

Specifies the ID of an LDP peer.

This value is in dotted decimal notation.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, a local device is enabled to authenticate all LDP peers using LDP keychain or LDP MD5 after LDP keychain or LDP MD5 is configured for a peer group or all LDP peers. To disable the local device from authenticating some LDP peers, run the authentication exclude command.

Precautions

The following commands are mutually exclusive for a specified LDP peer:

Example

# Disable a local device from authenticating an LDP peer with IP address 4.4.4.4 after LDP keychain or MD5 is configured for all LDP peers or LDP peers in a specified group.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] authentication exclude peer 4.4.4.4

authentication key-chain

Function

The authentication key-chain command enables Label Distribution Protocol (LDP) keychain authentication.

The undo authentication key-chain command disables Label Distribution Protocol (LDP) keychain authentication.

By default, LDP keychain authentication is disabled.

Format

authentication key-chain peer peer-id name keychain-name

undo authentication key-chain peer peer-id

Parameters

Parameter Description Value
peer peer-id Specifies the ID of an LDP peer enabled with LDP keychain. The parameter is specified in the mpls lsr-id command.

The value is in dotted decimal notation.

name keychain-name Specifies the keychain name. The keychain name is specified in the keychain command.

The value is an existing keychain name.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Information spoofing may occur during an LDP session. To enhance security of an LDP session, configure keychain authentication for a TCP connection over which an LDP session is created.

During keychain authentication, a group of passwords are defined to form a password string, and each password is specified with the encryption and decryption algorithms such as MD5 and SHA-1, and is configured with a validity period. When sending or receiving a packet, the system selects a valid password based on the user's configuration. Within the password validity period, the system either uses the encryption algorithm matching the password to encrypt the packet before sending it or uses the decryption algorithm matching the password to decrypt the packet before receiving it. In addition, the system automatically uses a new password after the previous one expires, preventing the password from being decrypted.

The keychain authentication password, the encryption and decryption algorithms, and password validity period that construct a keychain configuration node are configured using different commands. A keychain configuration node requires at least one password along with encryption and decryption algorithms.

To reference a keychain configuration node, specify the required peer and the node name in the MPLS-LDP view. In this manner, an LDP session is encrypted. Different peers can reference the same keychain configuration node.

Keychain authentication involves a set of passwords. It uses a new password when the previous one expires. Keychain authentication is complex to configure and is therefore recommended only for networks requiring high security.

Prerequisites

You have performed the following operations:

Precautions

  • If a neighbor has been configured to be authenticated using MD5 algorithm by running the md5–password command, you cannot configure keychain authentication for the neighbor again.

  • Configuring LDP keychain authentication causes the reestablishment of LDP sessions.

Example

# Configure LDP keychain authentication for the peer with an LSR ID of 2.2.2.2. The referenced keychain name is kc1.

<HUAWEI> system-view
[~HUAWEI] keychain kc1 mode absolute
[*HUAWEI-keychain-kc1] quit
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] authentication key-chain peer 2.2.2.2 name kc1

authentication key-chain all

Function

The authentication key-chain all command enables keychain authentication in a batch for all LDP peers.

The undo authentication key-chain all command disables keychain authentication in a batch for all LDP peers.

By default, keychain authentication in a batch is disabled for all LDP peers. LDP keychain authentication is recommended to ensure security.

Format

authentication key-chain all name keychain-name

undo authentication key-chain all

Parameters

Parameter Description Value
name keychain-name

Specifies a keychain name. The keychain name is configured using the keychain command.

The value is a string of 1 to 47 case-insensitive characters. The string does not contain question marks or spaces. The string can contain spaces if it is enclosed with double quotation marks (").

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To help improve LDP session security, keychain authentication can be configured for a TCP connection over which an LDP session has been established. If a great number of LDP peers are configured, run the authentication key-chain all command to enable keychain authentication in a batch for all LDP peers.

Prerequisites

A keychain has been configured using the keychain command.

Configuration Impact

After the authentication key-chain all command is run, the referenced keychain is applied to all LDP peers. If keychain authentication fails, an LDP session fails to be established.

Precautions

  • LDP authentication configurations are prioritized in descending order: for a single peer, for a specified peer group, for all peers. Keychain and MD5 configurations of the same priority are mutually exclusive. Keychain authentication and MD5 authentication can be configured simultaneously for a specified LDP peer, for this LDP peer in a specified peer group, and for all LDP peers. The configuration with a higher priority takes effect. For example, if MD5 authentication is configured for Peer1 and then keychain authentication is configured for all LDP peers, MD5 authentication takes effect on Peer1. Keychain authentication takes effect on other peers.

  • Configuring LDP keychain authentication causes the reestablishment of LDP sessions.

Example

# Configure LDP keychain authentication for all LDP peers and use the keychain named kc1.

<HUAWEI> system-view
[~HUAWEI] keychain kc1 mode absolute
[*HUAWEI-keychain-kc1] key-id 1
[*HUAWEI-keychain-kc1-keyid-1] algorithm md5
[*HUAWEI-keychain-kc1-keyid-1] key-string abcDEF-13579
[*HUAWEI-keychain-kc1-keyid-1] send-time 14:30 2008-10-10 to 14:50 2008-10-10
[*HUAWEI-keychain-kc1-keyid-1] receive-time 14:40 2008-10-10 to 14:50 2008-10-10
[*HUAWEI-keychain-kc1-keyid-1] default send-key-id
[*HUAWEI-keychain-kc1-keyid-1] quit
[*HUAWEI-keychain-kc1] quit
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] authentication key-chain all name kc1

authentication key-chain peer-group

Function

The authentication key-chain peer-group command enables keychain authentication in a batch for a specified LDP peer group.

The undo authentication key-chain peer-group command disables keychain authentication in a batch for a specified LDP peer group.

By default, keychain authentication in a batch is disabled for all peer groups. LDP keychain authentication is recommended to ensure security.

Format

authentication key-chain peer-group ip-prefix-name name keychain-name

undo authentication key-chain peer-group

Parameters

Parameter Description Value
ip-prefix-name

Specifies the name of an IP prefix list. The IP prefix list name is configured using the ip ip-prefix command.

The value is a string of 1 to 169 case-sensitive characters, spaces not supported. The string can contain spaces if it is enclosed with double quotation marks (").

name keychain-name

Specifies a keychain name. The keychain name is configured using the keychain command.

The value is a string of 1 to 47 case-insensitive characters. The string does not contain question marks or spaces. The string can contain spaces if it is enclosed with double quotation marks (").

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To help improve LDP session security, keychain authentication can be configured for a TCP connection over which an LDP session has been established. If a great number of LDP peers are configured, run the authentication key-chain peer-group command to enable keychain authentication in a batch for LDP peers in a specified peer group. An IP prefix list can be specified to define the range of IP addresses in a group.

Prerequisites

The following steps have been performed:

  • An IP prefix list has been configured using the ip ip-prefix command.

  • A peer group is created using the peer group command.

  • A keychain has been configured using the keychain command.

Configuration Impact

After the authentication key-chain peer-group command is run, the referenced Keychain authentication is applied to a specified peer. If keychain authentication fails, an LDP session fails to be established.

Precautions

  • LDP authentication configurations are prioritized in descending order: for a single peer, for a specified peer group, for all peers. Keychain and MD5 configurations of the same priority are mutually exclusive. Keychain authentication and MD5 authentication can be configured simultaneously for a specified LDP peer, for this LDP peer in a specified peer group, and for all LDP peers. The configuration with a higher priority takes effect. For example, if MD5 authentication is configured for Peer1 and then keychain authentication is configured for all LDP peers, MD5 authentication takes effect on Peer1. Keychain authentication takes effect on other peers.

  • Configuring LDP keychain authentication causes the reestablishment of LDP sessions.

Example

# Enable LDP keychain authentication for LDP peers with IP addresses matching the IP prefix list named list1 in a specified peer group and use a keychain named kc1.

<HUAWEI> system-view
[~HUAWEI] keychain kc1 mode absolute
[*HUAWEI-keychain-kc1] key-id 1
[*HUAWEI-keychain-kc1-keyid-1] algorithm md5
[*HUAWEI-keychain-kc1-keyid-1] key-string abcDEF-13579
[*HUAWEI-keychain-kc1-keyid-1] send-time 14:30 2008-10-10 to 14:50 2008-10-10
[*HUAWEI-keychain-kc1-keyid-1] receive-time 14:40 2008-10-10 to 14:50 2008-10-10
[*HUAWEI-keychain-kc1-keyid-1] default send-key-id
[*HUAWEI-keychain-kc1-keyid-1] quit
[*HUAWEI-keychain-kc1] quit
[*HUAWEI] ip ip-prefix list1 permit 4.4.4.4 32
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] authentication key-chain peer-group list1 name kc1

auto-frr lsp-trigger

Function

The auto-frr lsp-trigger command configures a policy for triggering LDP to establish backup LSPs based on backup routes.

The undo auto-frr lsp-trigger command restores the default setting.

By default, LDP uses backup routes with 32-bit addresses to establish backup LSPs.

Format

auto-frr lsp-trigger { all | host | ip-prefix ip-prefix-name | none }

undo auto-frr lsp-trigger

Parameters

Parameter Description Value
all Specifies all backup routes to trigger LDP to establish backup LSPs. -
host Specifies backup routes with 32-bit addresses to trigger LDP to establish backup LSPs. -
ip-prefix ip-prefix-name Specifies IP prefix list to trigger LDP to establish backup LSPs. The value is an existing IP prefix list name.
none Specifies no backup routes to trigger LDP to establish backup LSPs. -

Views

MPLS-LDP view, MPLS-LDP-IPv4 view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On an MPLS network with the active/standby link, run the auto-frr lsp-trigger command to quickly switch traffic to the backup LDP LSP within 50 ms upon a fault on the active link.

Auto LDP FRR depends on the automatic reroute function of IGP. Auto LDP FRR is automatically enabled after IGP automatic reroute is enabled using the frr (IS-IS) or frr (OSPF) command. To change the policy for triggering LDP to establish backup LSPs, run the auto-frr lsp-trigger command.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp(system view) command in the system view.

Precautions

If both the auto-frr lsp-trigger command and the lsp-trigger command are run, the established backup LSPs are controlled by both the policy for triggering LDP LSP establishment and the policy for triggering backup LDP LSP establishment. For example, if the policy for triggering LDP LSP establishment is none and that for triggering backup LDP LSP establishment is all, the backup LDP LSP is established using the none policy.

The auto-frr lsp-trigger command takes effect in either the MPLS LDP view or MPLS-LDP-IPv4 view. If the command is configured in both views, only the latest configuration takes effect.

Example

#Configure the policy for specifying no backup routes to trigger LDP to establish backup LSPs.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] auto-frr lsp-trigger none

backoff timer

Function

The backoff timer command sets the initial and maximum values for an Exponential backoff timer.

The undo backoff timer command restores the default settings.

By default, the initial value is 15 and the maximum value is 120, in seconds.

Format

backoff timer init max

undo backoff timer

Parameters

Parameter Description Value
init Specifies the initial value of an Exponential backoff timer. The value is an integer ranging from 5 to 2147483, in seconds.
max Specifies the maximum value of an Exponential backoff timer. The value is an integer ranging from 5 to 2147483, in seconds.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After an LSR fails to process an LDP Initialization message or is informed that the peer LSR rejects the received LDP Initialization message, the LSR starts the Exponential backoff timer and periodically resends an LDP Initialization message to initiate an LDP session before the Exponential backoff timer expires.

When the Exponential backoff timer starts, the active role waits a period of time equal to the initial value of the Exponential backoff timer to attempt to set up an LDP session for the first time. Subsequently, the active role waits a period of time twice as long as the previous one to attempt to set up an LDP session. When the waiting period reaches the maximum value of the Exponential backoff timer, the active role waits a period of time equal to the maximum value of the Exponential backoff timer to attempt to set up an LDP session.

Run the backoff timer command to change the interval at which the active role attempts to set up a session.

By setting the initial value and maximum value for the Exponential backoff timer, you can flexibly control the reestablishment of sessions in different network environments.

  • When a device is being upgraded, increase the initial and maximum values to set a large interval at which the active role attempts to set up a session.
  • When a device that is transmitting services is prone to intermittent disconnections, reduce the initial and maximum values to set a small interval at which the active role attempts to set up a session.
NOTE:
The initial value for the Exponential backoff timer cannot be smaller than 15, and the maximum value cannot be smaller than 120.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp (system view) command.

Precautions

If a session is disconnected after the backoff timer command is run, the device attempts to set up a session based on the set initial and maximum values of the Exponential backoff timer.

Example

# Set the initial value to 20s and the maximum value to 160s for the Exponential backoff timer.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] backoff timer 20 160

bfd bind ldp-lsp

Function

The bfd bind ldp-lsp command creates a bidirectional forwarding detection (BFD) session for detecting LDP LSPs.

The undo bfd command deletes a specified BFD session.

By default, no BFD session is created for detecting LDP LSPs.

Format

bfd session-name bind ldp-lsp peer-ip ip-address nexthop ip-address [ interface interface-type interface-number ]

undo bfd session-name

Parameters

Parameter Description Value
session-name Specifies the name of a BFD session.
The value is a string of 1 to 15 case-sensitive characters without spaces.
NOTE:

When double quotation marks are used around the string, spaces are allowed in the string.

peer-ip ip-address Specifies the peer IP address bound to the BFD session. The value is in dotted decimal notation.
nexthopip-address Specifies the next hop IP address of the detected LSP. The value is in dotted decimal notation.
interfaceinterface-type interface-number Specifies the outbound interface that is bound to a BFD session.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A dynamic LSP is established using LDP on an MPLS network. It takes an interface a long period of time to detect a link fault. After a static BFD session is bound to the LDP LSP, the interface can quickly detect faults on LDP LSPs. This method applies to small networks.

Prerequisites

BFD has been enabled globally using the bfd command.

Precautions

  • When the IP address of the outbound interface of the detected LSP is lent or borrowed, an outbound interface must be specified.

  • When the LDP LSP is deleted but the LDP session exists, the BFD session is in Down state, but the configuration of the BFD session bound to the LDP session is not deleted.

Example

# Create a BFD session to detect the LDP LSP with the egress IP address being 4.4.4.4, the next hop IP address being 1.1.1.1, and the outbound interface being VLANIF100.

<HUAWEI> system-view
[~HUAWEI] bfd
[*HUAWEI-bfd] quit
[*HUAWEI] bfd 1to4 bind ldp-lsp peer-ip 4.4.4.4 nexthop 1.1.1.1 interface vlanif 100
[*HUAWEI-bfd-lsp-session-1to4]
Related Topics

display default-parameter mpls ldp

Function

The display default-parameter mpls ldp command displays the default configurations of MPLS LDP.

Format

display default-parameter mpls ldp

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

To view the default configurations of MPLS LDP, run the display default-parameter mpls ldp command.

Example

# Display the default configurations of MPLS LDP.

<HUAWEI> display default-parameter mpls ldp


 LDP Default Values:
 ----------------------------------------------------------
          Protocol version               : V1
          Graceful restart               : Off
            Neighbor liveness(sec)       : 600
            FT reconnect timer(sec)      : 300                                 
            Recovery timer(sec)          : 300    
          MTU signaling                  : On
          Global split-horizon           : On
          Label retention mode           : Liberal
          Label distribution mode        : Ordered
          Label advertisement            : DU
          Local hello-hold timer(sec)    : 15
          Remote hello-hold timer(sec)   : 45
          Keepalive-hold timer(sec)      : 45
          Backoff timer init(sec)        : 15
          Backoff timer max(sec)         : 120
          IGP-Sync delay timer(sec)      : 10
          Graceful delete                : Off
            Graceful delete timer(sec)   : 5
          Session Protection             : Off
            Duration timer(sec)          : 86400 
          mLDP MBB Capability            : --
          mLDP P2MP Capability           : --
          mLDP MP2MP Capability          : Off
          mLDP Recursive                 : --
 ----------------------------------------------------------
Table 11-1  Description of the display default-parameter mpls ldp command output

Item

Description

Protocol version

LDP version number.

Graceful restart

LDP GR capability status.
  • On: LDP GR is enabled.
  • Off: LDP GR is disabled.
By default, LDP GR is disabled. You can configure the LDP GR capability status using the graceful-restart command.

Neighbor liveness(sec)

Value of the neighbor-liveness timer, in seconds. The default value is 600s. You can set this value using the graceful-restart timer neighbor-liveness command.

FT reconnect timer(sec)

Value of the reconnect timer of an LDP session, in seconds. The default value is 300s.

Recovery timer(sec)

Value of the recovery timer of an LDP LSP, in seconds. The default value is 300s. You can set this value using the graceful-restart timer recovery command.

MTU signaling

MTU TLV status.
  • On: MTU TLV is enabled.
  • Off: MTU TLV is disabled.
By default, MTU TLV is enabled.

Global split-horizon

Split-horizon of the LDP protocol:
  • On: Split-horizon is enabled.
  • Off: Split-horizon is disabled.
By default, split-horizon is enabled.

Label retention mode

LDP label retention mode. Currently, only the liberal mode is supported.

Label distribution mode

LDP label distribution mode. Currently, only the ordered mode is supported.

Label advertisement

LDP label advertisement mode. Currently, only the DU mode is supported.

Local hello-hold timer(sec)

Value of the local Hello hold timer, in seconds. The default value is 15s. You can set this value using the mpls ldp timer hello-hold command.

Remote hello-hold timer(sec)

Value of the remote Hello hold timer, in seconds. The default value is 45s. You can set this value using the mpls ldp timer hello-hold command.

Keepalive-hold timer(sec)

Value of the keepalive hold timer for the local and remote LDP sessions, in seconds. The default value is 45s. You can set this value using the mpls ldp timer keepalive-hold command.

Backoff timer init(sec)

Initial value of the Exponential backoff timer, in seconds. The default value is 15s. You can set this value using the backoff timer command.

Backoff timer max(sec)

Maximum value of the Exponential backoff timer, in seconds. The default value is 120s. You can set this value using the backoff timer command.

IGP-Sync delay timer(sec)

Value of the LDP-IGP association timer, in seconds. The default value is 10s. You can set this value using the mpls ldp timer igp-sync-delay command.

Graceful delete

Graceful deletion. This function is disabled.

Graceful delete timer(sec)

Value of the graceful deletion timer, in seconds. The default value is 5s.

Session Protection

LDP session protection:

  • On: The LDP session protection is enabled.
  • Off: The LDP session protection id disabled.

By default, LDP session protection is disabled. You can configure LDP session protection function using the session protection command.

Duration timer(sec)

Remaining time when LDP session protection remains effective, in seconds. The default value is 86400s. You can set this value using the session protection command.

mLDP MBB Capability

Whether the mLDP make-before-break capability is enabled.

mLDP P2MP Capability

Whether mLDP P2MP is enabled global.

mLDP MP2MP Capability

Whether mLDP MP2MP is enabled global. The default value is "Off", indicating that LDP MP2MP is disabled globally.

mLDP Recursive

Whether an mLDP P2MP LSP is established across domains.

display default-parameter mpls management

Function

The display default-parameter mpls management command displays default configurations of the MPLS management module.

Format

display default-parameter mpls management

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

To view the default configurations of MPLS management module, run the display default-parameter mpls management command.

Example

# Display the default configurations of the MPLS management module.

<HUAWEI> display default-parameter mpls management
 Global Information:
 --------------------------------------------------------------
   Label advertisement mode     : Implicit null
   LSP trigger mode             : Host
 --------------------------------------------------------------
Table 11-2  Description of the display default-parameter mpls management command output

Item

Description

Label advertisement mode

Mode in which the egress node assigns labels to the penultimate hop.
  • Implicit null: The egress node assigns an implicit empty label to the penultimate hop. The value of the label is 3.
  • Explicit null: The egress node assigns an explicit empty label to the penultimate hop. The value of the label is 0.
  • Non null: The egress node assigns a label to the penultimate hop properly. The value of the label is not smaller than 16.
By default, the implicit null mode is used. You can set the label advertisement mode using the label advertise command.

LSP trigger mode

Policy for triggering LSP setup.
  • All: All static routes and IGP routing entries trigger the setup of LSPs.
  • Host: The IP route of the 32-bit address host triggers the setup of LSPs.
  • Ip-prefix: Only FECs that match entries in the IP address prefix list trigger the setup of LSPs.
  • None: The setup of LSPs is not triggered.
The default trigger policy is Host. You can set the LSP trigger mode using the lsp-trigger command.

display isis ldp-sync interface

Function

The display isis ldp-sync interface command displays information about LDP and IS-IS synchronization on an interface.

Format

display isis [ process-id ] ldp-sync interface

Parameters

Parameter Description Value
process-id Specifies the IS-IS process ID. The value is an integer ranging from 1 to 4294967295.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

For all the interfaces that are enabled with LDP and IS-IS synchronization, run the display isis ldp-sync interface command to view information about LDP and IS-IS synchronization.

Example

# Display information about LDP and IS-IS synchronization on an interface.

<HUAWEI> display isis ldp-sync interface

Ldp Sync interface information for ISIS(1)
------------------------------------------------------------------------------
 Interface       HoldDownTimer     HoldMaxCostTimer    LDP State    Sync State
 Vlanif100       10                10                  Down         Init      
Table 11-3  Description of the display isis ldp-sync interface command output

Item

Description

Interface

Interface connected to neighbors.

HoldDownTimer

Interval during which the interface waits for the LDP session establishment and does not create the IS-IS neighbor relationship. The default value is 10 seconds. You can set this value using the isis timer ldp-sync hold-down command.

HoldMaxCostTimer

Interval for IS-IS to notify the local device of the maximum metric in the link state PDU (LSP). The default value is infinite. You can set this value using the isis timer ldp-sync hold-max-cost command.

NOTE:

If the value of this field is infinite, IS-IS permanently notifies the local device of the maximum metric in the LSP before an LDP session is established.

LDP State

LDP session status, which can be:
  • Up: The LDP session is normal.

  • Down: The LDP session is disconnected.

  • GR: The LDP session is in GR state. If the interface is maintaining the session before GR, the LDP status is displayed as GR state during GR.

Sync State

Status of synchronization between LDP and IS-IS:
  • Achieved: The creation of an LDP session and establishment of the IS-IS neighbor relationship are synchronized.

  • HoldDown: indicates the state in which the interface waits to create an LDP session without creating the IS-IS neighbor relationship.

  • HoldMaxCost: indicates the state in which IS-IS advertises the maximum metric in LSPs sent by the local device.

  • Init: indicates the initial state.

display lspv statistics

Function

The display lspv statistics command displays LSPV statistics.

Format

display lspv statistics

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

In MPLS network management, the ping lsp or tracert lsp command can be used for LSP detection.

If the LSP detection fails, you can run the display lspv statistics command to view statistics about MPLS packets sent and received on the local device. If the number of MPLS packets that the local device sends is the same as the number of MPLS packets that the local device receives, but the ping or trace operation fails, the detection failure is caused by the fault of the local device, not the LSP.

Precautions

Before running the display lspv statistics command to collect LSPV statistics, run the reset lspv statistics command to clear the existing statistics.

Example

# Display LSPV statistics on the device.

<HUAWEI> display lspv statistics
Total sent: 1329 packet(s)
Total received: 1329 packet(s)
MPLS echo request sent: 2 packet(s), received: 1327 packet(s)
MPLS echo reply sent: 1327 packet(s), received: 2 packet(s)
Dropped because MPLS and virtual cluster access disabled: 0 packet(s)
Table 11-4  Description of the display lspv statistics command output

Item

Description

Total sent:

Total number of sent MPLS Echo Request packets and MPLS Echo Reply packets

Total received:

Total number of received MPLS Echo Request packets and MPLS Echo Reply packets

MPLS echo request sent: , received:

Total number of sent and received MPLS Echo Request packets

MPLS echo reply sent: , received:

Total number of sent and received MPLS Echo Reply packets

Dropped because MPLS and virtual cluster access disabled:

Total number of packets dropped because MPLS and virtual cluster are not enabled on the inbound interface

Related Topics

display mpls interface

Function

The display mpls interface command displays information about all MPLS-enabled interfaces.

Format

display mpls interface [ interface-type interface-number ] [ verbose ]

Parameters

Parameter Description Value
interface-type interface-number Displays information about the specified interface enabled with MPLS. -
verbose Displays detailed information about the interface enabled with MPLS. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After enabling basic MPLS functions, run the display mpls interface command to view information about the interface enabled with MPLS.

Precautions

If there is no interface enabled with MPLS, the output of display mpls interface command is empty.

Example

# Display information about all MPLS-enabled interfaces.

<HUAWEI> display mpls interface
Interface             Status    TE Attr   Effective MTU
Vlanif10              Up        En        1500     
Vlanif11              Up        En        1500     
Vlanif12              Down      Dis       1500     
Table 11-5  Description of the display mpls interface command output

Item

Description

Interface

Type and number of the interface enabled with MPLS

Status

Interface status:
  • Up

  • Down

TE Attr

Status of the TE attributes on an interface:
  • Dis: MPLS TE is disabled on an interface.

  • En: MPLS TE is enabled on an interface.

Effective MTU

MPLS maximum transmission unit (MTU) used during data forwarding:
  • If the MPLS MTU is not set, the interface MTU takes effect.

  • If the MPLS MTU is set, the smaller one between the MPLS MTU and the interface MTU takes effect.

# Display detailed information about a specified MPLS-enabled interface.

<HUAWEI> display mpls interface Vlanif10 verbose
No                    : 1
Interface             : Vlanif10
Status                : Up
TE Attribute          : Enable
MPLS MTU              : -
Interface MTU         : 1500
Effective MTU         : 1500
TE FRR                : Disable
Interface Index       : 0x18000206
Table 11-6  Description of the display mpls interface verbose command output

Item

Description

No

Sequence number

Interface

Type and number of the interface enabled with MPLS

Status

Interface status:
  • Up

  • Down

TE Attribute

Status of the TE attributes on an interface:
  • Disable: MPLS TE is disabled on the interface.

  • Enable: MPLS TE is enabled on the interface.

MPLS MTU

MPLS MTU value configured using the mpls mtu command. When no MPLS MTU is set, "-" is displayed.

Interface MTU

MTU value configured on an interface

Effective MTU

MPLS MTU used during data forwarding:
  • If no MPLS MTU is set, the interface MTU takes effect.

  • If the MPLS MTU is set, the smaller one between the MPLS MTU and the interface MTU takes effect.

TE FRR

Whether the Traffic Engineering (TE) fast reroute (FRR) is enabled or disabled on the interface:
  • Disable: indicates that no bypass tunnel is set up in manual FRR mode to protect the interface.

  • Enable: indicates that a bypass tunnel is set up in manual FRR mode to protect the interface.

Interface Index

Interface index value

display mpls label all summary

Function

The display mpls label all summary displays allocation information about all MPLS labels.

Format

display mpls label all summary

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After a session is established, the system collects statistics on label usage, including the allocation range and protocol type. You can use the display mpls label all summary command to view the allocation of label space and the corresponding protocol type.

Example

# Display allocation information about MPLS labels.

<HUAWEI> display mpls label all summary
TableType      MinValue    MaxValue    AvailableNum
Reserved              0          15              16
Static               16        4095            4080
Dynamic              16       49152           49137
Table 11-7  Description of the display mpls label all summary command output

Item

Description

TableType

Label type.

  • Reserved
  • Static
  • Dynamic

MinValue

Minimum label value.

MaxValue

Maximum label value.

AvailableNum

Number of labels that can be allocated.

display mpls ldp

Function

The display mpls ldp command displays global LDP configurations.

Format

display mpls ldp [ all | all verbose ]

Parameters

Parameter Description Value
all Displays all LDP information. -
all verbose Displays detailed information about the LDP protocol and all the LSRs. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After global MPLS is enabled, run the display mpls ldp command to view LDP configurations, including configurations of the GR timer, label distribution, and label management.

Example

# Display global LDP configurations.

<HUAWEI> display mpls ldp 
 LDP Global Information
 ------------------------------------------------------------------------------
 Protocol Version        : V1            Neighbor Liveness     : 600 Sec
 Graceful Restart        : Off           FT Reconnect Timer    : 300 Sec
 MTU Signaling           : On            Recovery Timer        : 300 Sec
 P2MP Capability         : Off           MP2MP Capability      : Off

 LDP Instance Information
 ------------------------------------------------------------------------------
 Instance ID             : 0             VPN-Instance          : --
 Instance Status         : Active        LSR ID                : 1.1.1.9
 Hop Count Limit         : 32            Path Vector Limit     : 32
 Loop Detection          : Off
 DU Re-advertise Timer   : 10 Sec        DU Re-advertise Flag  : Off
 DU Explicit Request     : Off           Request Retry Flag    : Off
 Label Distribution Mode : Ordered       Label Retention Mode  : Liberal
 Graceful-Delete         : Off           Graceful-Delete Timer : 5 Sec
 IGP-sync-delay Timer    : 10 Sec       
 IPv6-family             : Off
 Local-IPv6-transport-address   :  --
 ------------------------------------------------------------------------------
Table 11-8  Description of the display mpls ldp command output

Item

Description

LDP Global Information

Global LDP information.

Protocol Version

LDP protocol version.

Neighbor Liveness

Timeout period of the GR Neighbor-liveness timer.

Graceful Restart

Whether LDP is enabled with GR:
  • On: GR is enabled.

  • Off: GR is disabled.

FT Reconnect Timer

Timeout period of the GR reconnect timer.

MTU Signaling

Whether the MTU signaling is enabled:
  • On: The private MTU TLV is sent.

  • Off: The MTU TLV is not supported.

  • On(apply-tlv): The MTU TLV is sent according to RFC 3988.

Recovery Timer

Timeout period of the GR Recovery timer.

P2MP Capability

Point to multi-point (P2MP) capability.
  • On: P2P capability is enabled.

  • Off: P2P capability is disabled.

MP2MP Capability

Multipoint-to-multipoint (MP2MP) capability
  • On: MP2MP capability is enabled.

  • Off: MP2MP capability is disabled.

LDP Instance Information

Information about the LDP multi-instance.

Instance ID

ID of a VPN instance in the integer format.

VPN-Instance

Name of a VPN instance.

NOTE:

The switch does not support this parameter.

Instance Status

Status of an instance:
  • Active: The instance is in the Active state.

  • Destroy: The instance is in the Destroy state. For example, after the undo mpls ldp command is used, the instance is in the Destroy state.

LSR ID

LSR ID of an LDP instance.

Hop Count Limit

Hop count limit for loop detection.

Loop Detection

Loop detection status:
  • On: Loop detection is enabled.

  • Off: Loop detection is disabled.

Path Vector Limit

Path vector limit for loop detection.

DU Re-advertise Timer

DU re-advertising timer.

DU Re-advertise Flag

DU re-advertising flag:
  • On: The function is enabled.

  • Off: The function is disabled.

DU Explicit Request

Status of sending an explicit request in a DU session:

  • On: The sending of an explicit request is enabled.

  • Off: The sending of an explicit request is disabled.

Request Retry Flag

Status of resending a label request:

  • On: The resending of a label request is enabled.

  • Off: The resending of a label request is disabled.

Label Distribution Mode

Label distribution mode:
  • Ordered

  • Independent

Currently, the switch supports only the ordered mode.

Label Retention Mode

Label retention mode:
  • Liberal

  • Conservative

Currently, the switch supports only the liberal mode.

Graceful-Delete

Whether graceful deletion is enabled:
  • On: enables graceful deletion.

  • Off: disables graceful deletion.

Graceful-Delete Timer

Value of the Graceful-delete Timer, in seconds.

IGP-sync-delay Timer

Value of the igp-sync-delay timer, in seconds.

IPv6-family

Whether LDP IPv6 is enabled:
  • On: LDP IPv6 is enabled.
  • Off: LDP IPv6 is disabled.
NOTE:

The switch does not support this parameter.

Local-IPv6-transport-address

Globally configured IPv6 transport address.

NOTE:

The switch does not support this parameter.

display mpls ldp adjacency

Function

The display mpls ldp adjacency command displays information about LDP adjacencies.

Format

display mpls ldp adjacency [ interface interface-type interface-number | remote ] [ peer peer-id ] [ verbose ]

display mpls ldp adjacency all [ verbose ]

Parameters

Parameter Description Value
interface interface-type interface-number Displays information about the LDP adjacency of a specified interface.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-
remote Displays information about the LDP adjacency of a specified remote end. -
peer peer-id Displays information about the LDP adjacency of a specified peer. The value is in dotted decimal notation.
verbose Displays detailed information about LDP adjacencies. -
all Displays information about all LDP adjacencies. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After an LDP session is established, run the display mpls ldp adjacency command to view real-time information about LDP adjacencies, for example, the number of received Hello messages.

Example

# Display information about LDP adjacencies.

<HUAWEI> display mpls ldp adjacency
 LDP Adjacency Information
 R: Remote Adjacency, L: Local Adjacency
 An asterisk (*) before an adjacency means the adjacency is being deleted.

 -------------------------------------------------------------------------------
 SourceAddr      PeerID          VrfID AdjAge(DDDD:HH:MM) RcvdHello Type
 -------------------------------------------------------------------------------
 11.0.0.2        2.2.2.9             0 0001:01:36             19203 L
 2.2.2.9         2.2.2.9             0 0001:01:36              5121 R
 -------------------------------------------------------------------------------
 TOTAL: 2 Record(s) Found.
Table 11-9  Description of the display mpls ldp adjacency command output

Item

Description

SourceAddr

Source address of the Hello message received by an LDP adjacency.

PeerID

LSR ID of an LDP peer.

VrfID

ID of a VPN instance.

AdjAge(DDDD:HH:MM)

Time elapsed since the LDP adjacency was created, in DDDD:HH:MM format.

RcvdHello

Number of Hello messages received by an LDP adjacency.

Type

Type of an LDP adjacency:
  • L: local LDP adjacency.
  • R: remote LDP adjacency.

# Display detailed information about the LDP adjacency of the remote peer with the LSR ID of 3.3.3.3/32.

<HUAWEI> display mpls ldp adjacency remote peer 3.3.3.3 verbose
 LDP Adjacency Information
 ------------------------------------------------------------------------------
 LDP Peer ID                 : 3.3.3.3
 VPN Instance name           : --
 Create Date                 : 2013-09-30
 Create Time                 : 11:45:18
 Adjacency Age               : 0000:00:02
 Adjacency Type              : Local Adjacency
 Discovery Source            : Vlanif20
 UDP Source Address          : 11.2.1.1
 UDP Socket ID               : 1
 Sequence Number             : 1
 Configured Hello Hold Timer : 15 (sec)
 Hello Message Received      : 28
 ------------------------------------------------------------------------------
 TOTAL: 1 Adjacency(s) Found.
Table 11-10  Description of the display mpls ldp adjacency remote peer command output

Item

Description

LDP Peer ID

LSR ID of an LDP peer.

VPN Instance name

Name of a VPN instance.

NOTE:

The switch does not support this parameter.

Create Date

Creation date of an LDP adjacency.

Create Time

Creation time of an LDP adjacency.

Adjacency Age

Time elapsed since the LDP adjacency was created, in DDDD:HH:MM format.

Adjacency Type

Type of an LDP adjacency:

  • Local Adjacency.

  • Remote Adjacency.

Discovery Source

Discovery source of an LDP adjacency:
  • Interface: a discovery source of the local LDP adjacency.

  • Null: a discovery source of the remote LDP adjacency.

UDP Source Address

Source address of the UDP packet contained in the Hello message received by an LDP adjacency.

UDP Socket ID

Socket ID of the LDP adjacency to receive Hello message.

Sequence Number

Serial number carried in the received Hello message.

The default value is 0.

Configured Hello Hold Timer

Hello hold timer configured on the peer, in seconds:

  • Link Hello hold timer: maintains the local LDP adjacency. The default value is 15.

  • Target Hello hold timer: maintains the remote LDP adjacency. The default value is 45.

Hello Message Received

Number of Hello messages received by an LDP adjacency.

Related Topics

display mpls ldp adjacency statistics

Function

The display mpls ldp adjacency statistics command displays statistics about LDP adjacencies.

Format

display mpls ldp adjacency statistics

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

You can run the display mpls ldp adjacency statistics command to view the number of LDP adjacencies that are classified into local and remote LDP adjacencies.

Example

# Display statistics about LDP adjacencies.

<HUAWEI> display mpls ldp adjacency statistics
 LDP Adjacency Statistics Information
 ----------------------------------------------------
 AdjacencyType          Local      Remote       Total
 ----------------------------------------------------
 AdjacencyNumber            1           2           3
 ----------------------------------------------------
Table 11-11  Description of the display mpls ldp adjacency statistics command output

Item

Description

AdjacencyType

Type of LDP adjacencies.

AdjacencyNumber

Number of LDP adjacencies.

Local

Number of local LDP adjacencies.

Remote

Number of remote LDP adjacencies.

Total

Total number of LDP adjacencies.

display mpls ldp error packet

Function

The display mpls ldp error packet command displays information about LDP-related error messages.

Format

display mpls ldp error packet { tcp [ peer peer-id ] | udp [ interface interface-type interface-number ] }

Parameters

Parameter Description Value
tcp Displays information about TCP error messages related to LDP sessions. -
peer peer-id Specifies a peer LSR ID. If this parameter is configured, information about messages sent by a specified peer is displayed. The value is in dotted decimal notation.
udp Displays information about UDP error messages related to LDP sessions. -
interface interface-type interface-number Displays information about a specified interface.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

If an exception occurs on an MPLS network, run the display mpls ldp error packet command to view information about LDP-related error messages such as the number of received error messages.

Example

# Displays information about error TCP packets related to LDP.

<HUAWEI> display mpls ldp error packet tcp
 LDP Error TCP Packets
-------------------------------------------------------------------------------
 PeerID            : 2.2.2.9
 Date&Time         : 2013-09-24 07:10:12
 Error Reason      : Bad LDP Identifier
 VrfIndex          : 0
 Length            : 18
 Message Type      : -
 Packet Content    : 
 00 01 00 0E 02 02 02 09 00 00 02 01 00 04 80 00 
 A0 D8 
-------------------------------------------------------------------------------
 TOTAL: 1 Record(s) Found.

# Displays information about error UDP packets related to LDP.

<HUAWEI> display mpls ldp error packet udp
 LDP Error UDP Packets
-------------------------------------------------------------------------------
 Discovery Source  : Vlanif100
 Date&Time         : 2013-09-24 06:53:49
 Error Reason      : Bad Protocol Version
 VrfIndex          : 0
 Length            : 42
 Message Type      : Hello
 Packet Content    : 
 00 01 00 26 02 02 02 09 00 00 01 00 00 1C 00 01 
 F5 8A 04 00 00 04 00 0F 00 00 04 01 00 04 02 02 
 02 09 04 02 00 04 00 00 00 01 
-------------------------------------------------------------------------------
 TOTAL: 1 Record(s) Found.
Table 11-12  Description of the display mpls ldp error packet command output

Item

Description

PeerID

LDP session ID.

Discovery Source

Discovery source of an LDP peer.

Date&Time

Date and time when an error message was received.

Error Reason

Cause for an error:

  • Bad LDP Identifier: The LDP ID was incorrect.
  • Bad Protocol Version: The LDP PDU version was incorrect.
  • Bad PDU Length: The LDP PDU length was incorrect.
  • Bad Message Length: A message length was incorrect.
  • Bad TLV Length: A TLV length value was incorrect.
  • Malformed TLV Value: A TLV was incorrect.
  • Parameters Advertisement Mode: The label advertisement mode was incorrect.
  • Parameters Label Range: The label was out of a specified range.
  • Missing Message Parameters: Parameters in the message are missing.
  • Parameters Max PDU Length: The size reaches the maximum PDU length.
  • Unknown Ignore: An unknown error occurs.
  • Unknown Message Type: The type of the message is unknown.
  • Unknown TLV: The TLV in the message is unknown.

VrfIndex

Identifier of the VRF where an LDP session resides.

Length

Length of the error message

Message Type Type of an error message:
  • Label Request: Label Request message.
  • Label Mapping: Label Mapping message.
  • Label Release: Label Release message.
  • Label Withdraw: Label Withdraw message.
  • Label Abort Request: Label Abort Request message.
  • Hello: Hello message.
  • Initialization: Initialization message.
  • KeepAlive: KeepAlive message.
  • Notification: Notification message.
  • Address: Address message.
  • Address Withdraw: Address Withdraw message.
  • Capability: Capability message.
  • --: unknown message type.

Packet Content

Contents of the error message in the binary format.

display mpls ldp event adjacency-down

Function

The display mpls ldp event adjacency-down command displays events that LDP adjacencies go Down.

Format

display mpls ldp event adjacency-down [ interface interface-type interface-number | remote ] [ peer peer-id ] [ verbose ]

Parameters

Parameter Description Value
interface interface-type interface-number Displays events that LDP adjacencies on a specified interface go Down.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-
remote Indicates the remote LDP peer. -
peer peer-id Specifies the LSR ID of an LDP peer. The value is in dotted decimal notation.
verbose Displays details about events that LDP adjacencies go Down. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

Run the display mpls ldp event adjacency-down command to view the event that an LDP adjacency went Down. The information includes the time, reason, and the duration of the LDP adjacency.

Precautions

A maximum of 1024 events can be displayed.

Example

# Display the events that LDP adjacencies go Down.

<HUAWEI> display mpls ldp event adjacency-down
 LDP Adjacency Down Information
 A : The Adjacency is down because Hello Timer Expired.
 C : The administrator configuration to trigger.
 O : Other reason.
--------------------------------------------------------------------------------
 PeerID            Down Time                         Duration Time    Reason
--------------------------------------------------------------------------------
 2.2.2.9:0         2013-09-24 07:10:37               0 days, 00:00:01 A
 2.2.2.9:0         2013-09-24 07:10:39               0 days, 00:00:04 A
--------------------------------------------------------------------------------
 TOTAL: 2 Record(s) Found.
Table 11-13  Description of the display mpls ldp event adjacency-down command output
Item Description
PeerID LSR ID of an LDP peer.
Down Time Time when an LDP adjacency went Down.
Duration Time Time elapsed since an LDP adjacency established.
Reason Causes for the LDP adjacency Down event:
  • A: The LDP Hello-hold timer expired.
  • C: The configuration is changed.
  • O: other causes.

# Display detailed information that LDP adjacencies go Down.

<HUAWEI> display mpls ldp event adjacency-down verbose

 LDP Adjacency Down Information
--------------------------------------------------------------------------------
 SN                          : 1
 PeerID                      : 2.2.2.2:0
 VrfIndex                    : 0
 Down Time                   : 2011-09-29 05:52:24
 Duration Time               : 0 days, 01:17:55
 MaxInterval Time(sec)       : 6
 Reason                      : Interface Down
 Type                        : IPv4/Local Adjacency
 Discovery Source            : Vlanif20
--------------------------------------------------------------------------------
 SN                          : 2
 PeerID                      : 2.2.2.2:0
 VrfIndex                    : 0
 Down Time                   : 2011-09-29 06:11:04
 Duration Time               : 0 days, 00:14:14
 MaxInterval Time(sec)       : 5
 Reason                      : Interface Down
 Type                        : IPv4/Local Adjacency
 Discovery Source            : Vlanif20
--------------------------------------------------------------------------------
  TOTAL: 2 Record(s) Found, 2 IPv4 Record(s), 0 IPv6 Record(s).
Table 11-14  Description of the display mpls ldp event adjacency-down verbose command output
Item Description

SN

Serial number.

PeerID

LSR ID of an LDP peer.

VrfIndex

ID of a VPN instance.

The value 0 indicates the public network.

Down Time

Time when an LDP adjacency went Down.

Duration Time

Time elapsed since an LDP adjacency established.

MaxInterval Time (sec)

Maximum interval for sending a Hello message.

Reason

Reason for the LDP adjacency Down event:
  • Hello Timer Expired: The Hello timer expired.
  • LDP Interface Disable: LDP was disabled on an interface.
  • Remote Peer Delete: The remote LDP peer setting was deleted.
  • Transport Address Delete: A transport address was deleted.
  • Adjacency Stale: The adjacency aged.
  • Interface Down: The interface went Down.

Type

Adjacency type:
  • IPv4/Local Adjacency: Directly connected adjacency with an IPv4 address.
  • Remote Adjacency: Indirectly connected adjacency.

Discovery Source

Interface where an LDP peer is discovered.

display mpls ldp event session-down

Function

The display mpls ldp event session-down command displays events that LDP sessions go Down.

Format

display mpls ldp event session-down [ peer-id ] [ verbose ]

Parameters

Parameter Description Value
peer-id Specifies the peer ID. If this parameter is specified, events that LDP adjacencies on a specified peer go Down about are displayed. The value is in dotted decimal notation.
verbose Displays details about events that LDP sessions go Down. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Run the display mpls ldp event session-down command to view events that LDP sessions go Down, including the cause and time.

Example

# Display events that LDP sessions go Down.

<HUAWEI> display mpls ldp event session-down
 LDP Session Down Information
 R: Remote peer, L: Local peer.
 B: Both of local and remote peer.
 G: Graceful Restart Session.
--------------------------------------------------------------------------------
 PeerID            Down Time                        Duration Time    Flag Reason
--------------------------------------------------------------------------------
 10.2.2.9:0        2013-09-24 07:10:24              0 days, 00:00:02 R    Hello hold timer expire
--------------------------------------------------------------------------------
 TOTAL: 1 Record(s) Found.
Table 11-15  Description of the display mpls ldp event session-down command output

Item

Description

PeerID

LSR ID of an LDP peer.

Down Time

Time when an LDP session went down.

Duration Time

Time elapsed since an LDP adjacency established.

Flag

Peer type.

  • R: Remote peer, indicating that a remote session has been established.
  • L: Local peer, indicating that a local session has been established.
  • B: Both of local and remote peer, indicating that both local and remote sessions have been established.
  • G: Graceful Restart Session.

Reason

Description of the cause.

# Display detailed information about an LDP session that goes Down.

<HUAWEI> display mpls ldp event session-down verbose

 LDP Session Down Information
--------------------------------------------------------------------------------
 PeerID                  : 2.2.2.2:0
 IpFamily                : IPv4
 Socket ID               : 20
 Socket Flow Ctrl State  : FALSE
 Peer Transport Address  : 2.2.2.2
 Local Transport Address : 1.1.1.1
 Flag                    : Local
 Reason                  : Receive notification
 Sub Reason              : 10
 Down Time               : 2011-09-13 04:37:05
 Duration time           : 0 days, 00:01:49
--------------------------------------------------------------------------------
 PeerID                  : 2.2.2.2:0
 IpFamily                : IPv4
 Socket ID               : 22
 Socket Flow Ctrl State  : FALSE
 Peer Transport Address  : 2.2.2.2
 Local Transport Address : 1.1.1.1
 Flag                    : Local
 Reason                  : Undo MPLS LDP
 Sub Reason              : -
 Down Time               : 2011-09-16 02:52:55
 Duration time           : 2 days, 22:15:47
--------------------------------------------------------------------------------
 TOTAL: 2 Record(s) Found
Table 11-16  Description of the display mpls ldp event session-down verbose command output
Field Description
PeerID

Peer LDP ID

IpFamily

IP address family information

Socket ID

TCP socket ID

Socket Flow Ctrl State Socket flow control status:
  • TRUE: The socket is in the flow control state.
  • FALSE: The socket is not in the flow control state.
Peer Transport Address

Peer transport address used to establish the LDP session

Local Transport Address

Local transport address used to establish the LDP session

Flag Session type:
  • Remote: Remote peer
  • Local: Local peer
  • Local & Remote: Both of local and remote peers
  • GR: Graceful Restart Session
Reason

Reason for the session Down event:

  • Hello hold timer expire: The Hello hold timer expired.
  • Keepalive timer expire: The Keepalive timer expired.
  • Reset MPLS LDP: The reset mpls ldp command was run.
  • Undo MPLS LDP: The undo mpls ldp command was run.
  • Undo MPLS LDP remote peer: A remote LDP peer was deleted.
  • Config GR: LDP GR was configured.
  • Modify keepalive timer: The Keepalive timer value was modified.
  • Config transport address: The transport address was modified.
  • Modify MPLS LDP LSR-ID: An LSR ID of the LDP session was modified.
  • Receive notification: A Notification message was received.
  • Session role changed: The session type was changed.
  • Error message was received from a peer: An incorrect Notification message was received.
  • Socket error was received: An incorrect socket was received.
  • Others.
Sub Reason
Sub-reason for the session Down event:
  • A value is displayed if the Reason field is Receive notification.
  • A hyphen (-) is displayed if the Reason field is not Receive notification.
Down Time

Time when the session went Down

Duration time

Time elapsed since the LDP session was established

display mpls ldp interface

Function

The display mpls ldp interface command displays information about LDP-enabled interfaces.

Format

display mpls ldp interface [ interface-type interface-number | [ all ] [ verbose ] ]

Parameters

Parameter Description Value
interface-type interface-number Specifies the type and number of an interface. If the parameter is specified, the configurations of a specified LDP-enabled interface are displayed. -
all Displays information about all LDP-enabled interfaces. -
verbose Displays detailed information about LDP-enabled interfaces. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Run the display mpls ldp interface command to view configurations of LDP-enabled interfaces and some real-time information, such as the number of sent and received Hello messages.

Example

# Display information about LDP-enabled interfaces.

<HUAWEI> display mpls ldp interface
 LDP Interface Information in Public Network
 LAM:Label Advertisement Mode, IFName: Interface Name
 An asterisk (*) before an interface means the entity is being deleted.
------------------------------------------------------------------------
IFName                 Status   LAM  TransportAddress   Hello(Sent/Rcvd)
------------------------------------------------------------------------
Vlanif20               Active   DU   3.3.3.3            53/47           
------------------------------------------------------------------------
Table 11-17  Description of the display mpls ldp interface command output

Item

Description

IFName

Name of an LDP-enabled interface.

Status

Status of the local LSR:
  • Active

  • Inactive

LAM

Label advertisement mode:
  • DU: downstream unsolicited mode.
  • DoD: downstream on demand mode.
Currently, only the DU mode is supported.

TransportAddress

IP address of a node that initiates a TCP connection for an LDP session.

Hello(Sent/Rcvd)

Number of sent and received Hello messages.

# Display detailed information about LDP-enabled interfaces.

<HUAWEI> display mpls ldp interface verbose
 LDP Interface Information in Public Network
 --------------------------------------------------------------
 Interface Name    : Vlanif100
 LDP ID            : 1.1.1.9:0         Transport Address : 1.1.1.9
 Entity Status     : Active            Effective MTU     : 1500

 Configured Hello Hold Timer     : 15 Sec
 Negotiated Hello Hold Timer     : 15 Sec
 Configured Hello Send Timer     : --
 Configured Keepalive Hold Timer : 45 Sec
 Configured Keepalive Send Timer : --
 Configured Delay Timer          : 10 Sec
 Label Advertisement Mode        : Downstream Unsolicited
 Hello Message Sent/Received     : 143370/143408 (Message Count)
 Autoconfiguration Source        : OSPF
 -------------------------------------------------------------
Table 11-18  Description of the display mpls ldp interface verbose command output

Item

Description

Interface Name

Name of an LDP-enabled interface.

LDP ID

LDP identifier.

Transport Address

IP addresses used in the TCP connection of a session.

Entity Status

Status of this entity:
  • Active
  • Inactive

Effective MTU

MTU value used for creating an LSP.

Configured Hello Hold Timer

Timeout period of the configured Hello hold timer.

Negotiated Hello Hold Timer

Negotiated value of the Hello hold timer, which is the smaller value of the Hello hold timers configured on the local and remote LDP peers.

Configured Hello Send Timer

Timeout period of the configured Hello send timer.

Configured Keepalive Hold Timer

Timeout period of the configured Keepalive hold timer.

Configured Keepalive Send Timer

Timeout period of the configured Keepalive send timer.

Configured Delay Timer

Timeout period of the Delay timer, which, in LDP and IGP synchronization, is the time that an interface waits to establish an LSP after an LDP session is established.

Label Advertisement Mode

Label advertisement mode:
  • Downstream Unsolicited
  • Downstream on Demand
Currently, only the Downstream Unsolicited (DU) mode is supported.

Hello Message Sent/Received

Number of sent and received Hello messages.

Autoconfiguration Source

Whether LDP is enabled using the IGP auto configuration function on the interface:
  • ---: LDP is manually enabled.
  • OSPF: After OSPF is enabled, LDP is automatically enabled.
  • IS-IS: After IS-IS is enabled, LDP is automatically enabled.
  • OSPF&ISIS: After both OSPF and IS-IS are enabled, LDP is automatically enabled.

display mpls ldp lsp

Function

The display mpls ldp lsp command displays information about an LDP LSP.

Format

display mpls ldp lsp [ all | destination-address mask-length ]

Parameters

Parameter Description Value
all Displays information about all LDP LSPs. -
destination-address Specifies the destination IPv4 address of an LDP LSP. The value is in dotted decimal notation.
mask-length Specifies the mask length of the specified IPv4 address. The value is an integer ranging from 0 to 32.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After LDP LSPs are set up, run the display mpls ldp lsp command to view detailed information about LSPs such as the outbound interfaces, next hop addresses, total number, and types.

Example

# Display information about LSPs.

<HUAWEI> display mpls ldp lsp
 LDP LSP Information
 An asterisk (*) before an LSP means the LSP is not established
 An asterisk (*) before a Label means the USCB or DSCB is stale
 An asterisk (*) before a UpstreamPeer means the session is in GR state
 An asterisk (*) before a DS means the session is in GR state
 An asterisk (*) before a NextHop means the LSP is FRR LSP
 -------------------------------------------------------------------------------
 DestAddress/Mask   In/OutLabel    UpstreamPeer    NextHop          OutInterface
 -------------------------------------------------------------------------------
         1.1.1.9/32  3/NULL         2.2.2.9         127.0.0.1        Loop1
         2.2.2.9/32  NULL/3         -               11.0.0.2         Vlanif100
 -------------------------------------------------------------------------------
 TOTAL: 2 Normal LSP(s) Found, 0 Liberal LSP(s) Found
        0 FRR LSP(s) Found.
Table 11-19  Description of the display mpls ldp lsp command output

Item

Description

DestAddress/Mask

Destination address and mask of an LSP.

In/OutLabel

Values of the incoming and outgoing labels.

An asterisk (*) before In/OutLabel indicates that the LSP is in the Stale state and needs to be restored.

UpstreamPeer

Upstream peer of an LSP.

An asterisk (*) before UpstreamPeer indicates that the session is in the GR state.

NextHop

Next hop IP address.

An asterisk (*) before NextHop indicates that the LSP is an FRR LSP.

DS is short for DownStream. The address next to DS/ is the LSR ID of a downstream peer.

OutInterface

Name of an outbound interface.

Related Topics

display mpls ldp lsp fault-analysis

Function

The display mpls ldp lsp fault-analysis command displays causes for failures to establish LDP LSPs.

Format

display mpls ldp lsp fault-analysis ip-address mask

Parameters

Parameter Description Value
ip-address Displays causes for a failure to establish an LDP LSP with a specified IP address. The value is in dotted decimal notation.
mask Specifies the mask length of a specified IP address. The value is an integer ranging from 0 to 32.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

LDP LSPs can be established based on multiple conditions, such as LDP sessions, labels assigned by LDP peers, routes and their types, labels, or tokens. If LDP LSPs fail to be established, to view causes for failures to establish LDP LSPs, run the display mpls ldp lsp fault-analysis command. The command output contains causes related to the ingress, transit node, and egress.

Example

# Display causes for failures to establish LDP LSPs.

<HUAWEI> display mpls ldp lsp fault-analysis 10.1.1.1 32
Ingress:
  Lsp State                : Down
  Check Route              : Pass
  Check Policy             : Fail
  Check Ds Session         : ---
  Check Ds Mapping         : ---
  Check Limit              : ---
  Check Resource           : ---
Transit:
  Lsp State                : Down
  Check Route              : Pass
  Check Policy             : Fail
  Check Ds Session         : ---
  Check Ds Mapping         : ---
  Check Us Request         : ---
  Check Limit              : ---
  Check Resource           : ---
Egress:
  Lsp State                : Down
  Check Route              : Pass
  Check Policy             : Fail
  Check Us Request         : ---
  Check Limit              : ---
  Check Resource           : ---
Table 11-20  Description of the display mpls ldp lsp fault-analysis command output

Item

Description

Ingress

Ingress information

Lsp State

LSP status:
  • Up
  • Down

Check Route

Route check results:
  • Pass
  • Fail
  • ---: Routes are not checked.

Check Policy

Policy check results:
  • Pass
  • Fail
  • ---: Policies are not checked.

Check Ds Session

Downstream session check results:
  • Pass
  • Fail
  • ---: Downstream sessions are not checked.

Check Ds Mapping

Downstream label check results:
  • Pass
  • Fail
  • ---: Downstream labels are not checked.

Check Limit

Threshold-crossing event check results:
  • Pass
  • Fail
  • ---: Threshold-crossing events are not checked.

Check Resource

Resource check results:
  • Pass
  • Fail
  • ---: Resources are not checked.

Transit

Transit node information

Check Us Request

Upstream request check results:
  • Pass
  • Fail
  • ---: Upstream requests are not checked.

Egress

Egress information

display mpls ldp lsp statistics

Function

The display mpls ldp lsp statistics command displays statistics about LDP LSPs.

Format

display mpls ldp lsp statistics

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

The display mpls ldp lsp statistics command displays the statistics about an LDP LSP, whereas the display mpls lsp statistics command displays the statistics about all types of LSPs.

Example

# Display statistics about LDP LSPs.

<HUAWEI> display mpls ldp lsp statistics
 LDP LSP Statistics Information
 ------------------------------------------------------------------------------
 VPNInstanceName      Total   Ingress   Transit    Egress   Liberal       FRR
 ------------------------------------------------------------------------------
 --                       5         1         0         2         2         0
 ------------------------------------------------------------------------------
Table 11-21  Description of the display mpls ldp lsp statistics command output

Item

Description

VPNInstanceName

Name of a VPN instance:

  • Hyphens (--) indicates a public network instance.
  • If LDP multi-instance is configured, the name of the created VPN instance is displayed.
NOTE:

The switch does not support this parameter.

Total

Number of LDP LSPs in an instance.

Ingress

Number of ingress LSPs in an instance.

Transit

Number of transit LSPs in an instance.

Egress

Number of egress LSPs in an instance.

Liberal

Number of liberal LSPs in an instance.

FRR

Number of FRR LSPs in an instance.

display mpls ldp peer

Function

The display mpls ldp peer command displays information about LDP peers.

Format

display mpls ldp peer [ verbose | peer-id | all [ verbose ] ]

Parameters

Parameter Description Value
verbose Displays detailed information about LDP peers. -
peer-id Displays information about a specified LDP peer. The value is in dotted decimal notation.
all Displays information about all LDP peers. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

If an LDP LSP fails to be established, run the display mpls ldp peer command to view the DiscoverySource field and check the interface through which the peer relationship is established.

The system supports the coexistent local and remote LDP peers. When you run the display mpls ldp peer command, information about both local and remote LDP peers is displayed.

You can set the peer-id parameter to specify a peer.

Precautions

You can view information about LDP peers only after the peers have been established using the mpls ldp (interface view) or remote-ip command.

Example

# Display information about LDP peers.

<HUAWEI> display mpls ldp peer
 LDP Peer Information in Public network
 An asterisk (*) before a peer means the peer is being deleted.
 -------------------------------------------------------------------------------
 PeerID                 TransportAddress               DiscoverySource
 -------------------------------------------------------------------------------
 2.2.2.9:0              2.2.2.9                        Remote Peer : 2.2.2.9
 3.3.3.3:0              3.3.3.3                        Vlanif100
 -------------------------------------------------------------------------------
 TOTAL: 1 Peer(s) Found.
Table 11-22  Description of the display mpls ldp peer command output

Item

Description

PeerID

LDP identifier of the peer in the format of <LSR ID>:<label space>. The value of a label space can be either of the following:

  • 0: per-platform label space.

  • Non-0: per-interface label space.

TransportAddress

Transport address of an LDP peer.

The transport address is used to set up TCP connections.

DiscoverySource

Discovery source of an LDP peer:
  • Interface name: indicates the source that discovers the local LDP peer.

  • Remote LDP peer name: indicates the source that discovers the remote LDP peer.

# Display detailed information about LDP peers.

<HUAWEI> display mpls ldp peer verbose
 LDP Peer Information in Public network
 -------------------------------------------------------------------------------
 Peer LDP ID            : 1.1.1.9:0
 Peer Max PDU Length    : 4096         Peer Transport Address : 1.1.1.9
 Peer Loop Detection    : Off          Peer Path Vector Limit : --
 Peer FT Flag           : Off          Peer Keepalive Timer   : 45 Sec
 Recovery Timer         : --           Reconnect Timer        : --
 Peer Type              : Remote
 Peer Label Advertisement Mode : Downstream Unsolicited
 Distributed ID         : 0
 Peer Discovery Source  : remote peer: 1.1.1.9
 Capability-Announcement       : Off
 Peer mLDP P2MP Capability     : Off
 Peer mLDP MP2MP Capability    : Off
 Peer mLDP MBB Capability      : Off
 -------------------------------------------------------------------------------
Table 11-23  Description of the display mpls ldp peer verbose command output

Item

Description

Peer LDP ID

LDP identifier of the peer in the format of <LSR ID>:<label space>. The value of a label space can be either of the following:

  • 0: per-platform label space.

  • Non-0: per-interface label space.

Peer Max PDU Length

Maximum size of a PDU sent by an LDP peer.

Peer Transport Address

Transport address of an LDP peer.

The transport address is used to set up TCP connections.

Peer Loop Detection

Whether loop detection of an LDP peer is enabled:

  • On: Loop detection is enabled.

  • Off: Loop detection is disabled.

Peer Path Vector Limit

Indicates the upper limit of the Path Vector for an LDP peer.

Peer FT Flag

GR FT flag of an LDP peer:

  • On: LDP GR is enabled.

  • Off: LDP GR is disabled.

The flag can only be set after an Initialization message containing an FT TLV is received.

Peer Keepalive Timer

Configured value of the Keepalive timer on an LDP peer.

Recovery Timer

Timeout period of the Recovery timer of an LDP peer.

The value of the Recovery Timer field is not null only when the Peer FT Flag field is On.

Reconnect Timer

Timeout period of the Reconnect timer of an LDP peer.

The value of the Recovery Timer field is not null only when the Peer FT Flag field is On.

Peer Type

Type of an LDP peer:

  • Local

  • Remote

  • Local&Remote

Peer Label Advertisement Mode

Indicates the label advertisement mode of an LDP peer:
  • Downstream Unsolicited

  • Downstream on Demand

The switch supports the Downstream Unsolicited (DU) mode.

Distributed ID

ID of an LDP distributed instance.

Peer Discovery Source

Discovery source of an LDP peer:
  • If the interface is displayed, the source of the local LDP peer is the local interface.

  • If the configuration name of the remote peer is displayed, the source end of the remote LDP peer is the remote peer.

Capability-Announcement

Status of the LDP dynamic capability announcement function:
  • On: LDP dynamic capability announcement is enabled.

  • Off: LDP dynamic capability announcement is disabled.

Peer mLDP P2MP Capability

Whether the LDP peer supports mLDP P2MP:

  • On: The LDP peer supports mLDP P2MP.

  • Off: The LDP peer does not support mLDP P2MP.

Peer mLDP MP2MP Capability

Whether the LDP peer supports mLDP MP2MP:

  • On: The LDP peer supports mLDP MP2MP.

  • Off: The LDP peer does not support mLDP MP2MP.

Peer mLDP MBB Capability

Whether the LDP peer supports make-before-break:

  • On: The LDP peer supports mLDP make-before-break.

  • Off: The LDP peer does not support mLDP make-before-break.

display mpls ldp peer statistics

Function

The display mpls ldp peer statistics command displays statistics about LDP peers.

Format

display mpls ldp peer statistics

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Run the display mpls ldp peer statistics command to view the number of local LDP peers, remote LDP peers, and coexistent local and remote LDP peers.

Example

# Display statistics about LDP peers.

<HUAWEI> display mpls ldp peer statistics
 LDP Peer Statistics Information
 ------------------------------------------------------------
 PeerType         Local    Remote    Local&Remote    Total
 ------------------------------------------------------------
 PeerNumber           0         0               1        1
 ------------------------------------------------------------
Table 11-24  Description of the display mpls ldp peer statistics command output

Item

Description

PeerType

Type of LDP peers.

PeerNumber

Number of LDP peers.

Local

Number of local LDP peers.

Remote

Number of remote LDP peers.

Local&Remote

Number of coexistent local and remote LDP peers.

Total

Total number of all types of LDP peers.

Related Topics

display mpls ldp remote-peer

Function

The display mpls ldp remote-peer command displays information about a remote LDP peer.

Format

display mpls ldp remote-peer [ remote-peer-name | peer-id lsr-id ]

Parameters

Parameter Description Value
remote-peer-name Specifies the name of a remote LDP peer. The value is an existing remote LDP peer.
peer-id lsr-id Specifies the LSR ID of a remote LDP peer. The value is in dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Remote LDP peers are used to set up remote LDP sessions to transmit VPN services.

To view information about the configured remote LDP peers, run the display mpls ldp remote-peer command.

Example

# Display information about remote LDP peers.

<HUAWEI> display mpls ldp remote-peer
 LDP Remote Entity Information
 ------------------------------------------------------------------------------
 Remote Peer Name  : lsrc
  Remote Peer IP    : 3.3.3.9            LDP ID        : 1.1.1.9:0
 Transport Address : 1.1.1.9            Entity Status : Active

 Configured Keepalive Hold Timer : 45 Sec
 Configured Keepalive Send Timer : ----
 Configured Hello Hold Timer     : 45 Sec
 Negotiated Hello Hold Timer     : 45 Sec
 Configured Hello Send Timer     : ----
 Configured Delay Timer          : ----
 Hello Packet sent/received      : 253/251
 Label Advertisement Mode        : Downstream Unsolicited
 Auto-config                     : Session Protection
 Session-Protect effect          : NO
 Session-Protect Duration        : infinite
 Session-Protect Remain          : ----
 ------------------------------------------------------------------------------
 TOTAL: 1 Remote-Peer(s) Found. 
Table 11-25  Description of the display mpls ldp remote-peer command output

Item

Description

Remote Peer Name

Name of a remote LDP peer.

Remote Peer IP

IP address of a remote LDP peer.

LDP ID

Local LDP ID.

Transport Address

Transport address, which is used to set up the LDP session between the local and remote peers.

Entity Status

Status of a remote LDP peer:
  • Active
  • Inactive

Configured Keepalive Hold Timer

Timeout period of the configured Keepalive hold timer.

Configured Keepalive Send Timer

Timeout period of the configured Keepalive send timer.

Configured Hello Hold Timer

Timeout period of the configured Hello hold timer.

Negotiated Hello Hold Timer

Timeout period of the negotiated Hello hold timer.

Configured Hello Send Timer

Timeout period of the configured Hello send timer.

Configured Delay Timer

Timeout period of the Delay timer, which, in LDP and IGP synchronization, is the time that an interface waits to establish an LSP after an LDP session is established.

Hello Packet sent/received

Number of sent and received Hello packets.

Label Advertisement Mode

Label advertisement mode in an LDP session.

The default mode is DU.

Auto-config

Whether the remote peer is created by BGP AD.

Session-Protect effect Whether LDP session protection takes effect:
  • YES
  • NO
Session-Protect Duration Duration when LDP session protection remains effective.
Session-Protect Remain Remaining time when LDP session protection remains effective.

display mpls ldp session

Function

The display mpls ldp session command displays information about LDP sessions.

Format

display mpls ldp session [ peer-id | all [ verbose ] | verbose ]

Parameters

Parameter Description Value
peer-id Displays information about LDP sessions of a specified LSR ID. The value is in dotted decimal notation.
all Displays information about all LDP sessions. -
verbose Displays detailed information about LDP sessions. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After creating an LDP session, run the display mpls ldp session command to verify that the LDP session is created successfully and view information about the LDP session, such as the number of sent or received Keepalive messages.

Example

# Display information about all LDP sessions.

<HUAWEI> display mpls ldp session
 LDP Session(s) in Public Network
 LAM: Label Advertisement Mode,  KA: KeepAlive
 SsnAge: Session Age, Unit(DDDD:HH:MM)
 An asterisk (*) before a session means the session is being deleted.
--------------------------------------------------------------------------
 PeerID             Status      LAM  SsnRole  SsnAge       KASent/Rcv
--------------------------------------------------------------------------
 2.2.2.2:0          Operational DU   Passive  0000:01:36   387/386
 3.3.3.3:0          Operational DU   Passive  0000:01:30   361/361
--------------------------------------------------------------------------
TOTAL: 2 Session(s) Found.
Table 11-26  Description of the display mpls ldp session command output

Item

Description

PeerID

LDP identifier of the peer in the format of <LSR ID>:<label space>. The value of a label space can be either of the following:
  • 0: per-platform label space.

  • 1: per-interface label space.

Status

Status of an LDP session:

  • NonExistent: LDP peers at both ends of the LDP session exchange Hello messages to negotiate a TCP connection. After the TCP connection is established, the LDP session enters the Initialized state. The Non-Existent state is the initial state in the LDP session state machine.
  • Initialized: The LDP session is in the initialization state.
  • Open Sent: The LSR playing the active role in the LDP session sends an Initialization message to the LSR playing the passive role and waits for a reply during initialization.
  • Open Recv: LDP peers at both ends of the LDP session wait for receiving a Keepalive message from each other during initialization. If they receive a Keepalive message from each other, the LDP session enters the Operational state.
  • Operational: An LDP session is established successfully.

LAM

Label advertisement mode of an LDP peer.

The default mode is DU.

SsnRole

Role that an LSR plays in an LDP session:

  • Active: an LSR with a larger LSR ID between two LSRs.

  • Passive: an LSR with a smaller LSR ID between two LSRs.

SsnAge

Time elapsed since an LDP session was set up in DDDD:HH:MM format.

KASent/Rcv

Number of Keepalive messages sent and received by an LDP session.

# Display detailed information about all LDP sessions.

<HUAWEI> display mpls ldp session verbose
 LDP Session(s) in Public Network
 ------------------------------------------------------------------------
 Peer LDP ID     : 1.1.1.9:0            Local LDP ID   : 3.3.3.9:0
 TCP Connection  : 3.3.3.9 -> 1.1.1.9
 Session State   : Operational          Session Role   : Active
 Session FT Flag : Off                  MD5 Flag       : Off
 Reconnect Timer : --                   Recovery Timer : --
 Keychain Name   : --
 P2MP Capability      : Off
 MP2MP Capability     : Off
 Negotiated Keepalive Hold Timer   : 45 Sec
 Configured Keepalive Send Timer   : --
 Keepalive Message Sent/Rcvd       : 210/210 (Message Count)
 Label Advertisement Mode          : Downstream Unsolicited
 Label Resource Status(Peer/Local) : Available/Available
 Session Age                       : 0000:00:52  (DDDD:HH:MM)


 Outbound&Inbound Policies applied:
 outbound peer all split-horizon

 Addresses received from peer: ( Count: 1 )
 1.1.1.9
 ------------------------------------------------------------------------
Table 11-27  Description of the display mpls ldp session verbose command output

Item

Description

Peer LDP ID

LDP identifier of the peer in the format of <LSR ID>:<label space>. The value of a label space can be either of the following:

  • 0: per-platform label space.

  • 1: per-interface label space.

Local LDP ID

Local LDP identifier in the format of <LSR ID>:<label space>. The value of a label space can be either of the following:

  • 0: per-platform label space.

  • 1: per-interface label space.

TCP Connection

TCP connection of an LDP session:

  • The LSR with a larger LSR ID value plays an active role in establishing the TCP connection.

  • The LSR with a smaller LSR ID value plays a passive role in establishing the TCP connection.

Session State

Status of an LDP session:

  • NonExistent: LDP peers at both ends of the LDP session exchange Hello messages to negotiate a TCP connection. After the TCP connection is established, the LDP session enters the Initialized state. The Non-Existent state is the initial state in the LDP session state machine.
  • Initialized: The LDP session is in the initialization state.
  • Open Sent: The LSR playing the active role in the LDP session sends an Initialization message to the LSR playing the passive role and waits for a reply during initialization.
  • Open Recv: LDP peers at both ends of the LDP session wait for receiving a Keepalive message from each other during initialization. If they receive a Keepalive message from each other, the LDP session enters the Operational state.
  • Operational: An LDP session is established successfully.

Session Role

Role that an LSR plays in an LDP session:

  • Active: an LSR with a larger LSR ID between two LSRs.

  • Passive: an LSR with a smaller LSR ID between two LSRs.

Session FT Flag

Negotiated LDP GR capability:

  • On: Negotiated LDP GR capability is enabled.

  • Off: Negotiated LDP GR capability is disabled.

MD5 Flag

MD5 authentication flag:

  • On: MD5 authentication is enabled during the TCP connection establishment.

  • Off: MD5 authentication is disabled during the TCP connection establishment.

Reconnect Timer

Negotiated timeout period of the Reconnect timer.

The value of the Recovery Timer field is not null only when the Peer FT Flag field is On.

Recovery Timer

Negotiated timeout period of the Recovery timer.

The value of the Recovery Timer field is not null only when the Peer FT Flag field is On.

Keychain Name

Referenced keychain authentication name.

P2MP Capability

Whether P2MP LDP is enabled:
  • On: P2MP LDP is enabled.

  • Off: P2MP LDP is disabled.

MP2MP Capability

Whether MP2MP LDP is enabled:
  • On: MP2MP LDP is enabled.

  • Off: MP2MP LDP is disabled.

Negotiated Keepalive Hold Timer

Negotiated value of the Keepalive hold timer, which is the smallest value of the Keepalive hold timers configured on the local and remote LDP peers.

Configured Keepalive Send Timer

Timeout period of the configured Keepalive send timer.

Keepalive Message Sent/Rcvd

Number of Keepalive messages sent and received by an LDP session.

Label Advertisement Mode

Label advertisement mode:
  • Downstream Unsolicited

  • Downstream on Demand

The default mode is Downstream Unsolicited (DU).

Label Resource Status(Peer/Local)

Label resource status of the remote and local peers.

Session Age

Time elapsed since an LDP session was set up.

Outbound&Inbound Policies applied

Outbound and inbound policies that take effect.

Addresses received from peer

Contents of an Address message sent by an LDP peer.

The contents include the LSR ID of the peer and the IP address of the LDP-enabled interface.

display mpls ldp session statistics

Function

The display mpls ldp session statistics command displays statistics about sessions between LDP peers.

Format

display mpls ldp session statistics

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Run the display mpls ldp session statistics command to view the number of sessions between LDP peers. Statistics are collected based on the session type and status. The session type can be local, remote, or coexistent local and remote. The session status can be Not Operational or Operational.

Example

# Display statistics about LDP sessions.

<HUAWEI> display mpls ldp session statistics
 LDP Session Statistics Information                  
 -----------------------------------------------------------------
 SessionType          Local    Remote    Local&Remote    Total  
 -----------------------------------------------------------------
 Not Operational          0         0               0        0  
 Operational              0         0               1        1 
 -----------------------------------------------------------------
 SessionStatistics        0         0               1        1
 -----------------------------------------------------------------
Table 11-28  Description of the display mpls ldp session statistics command output

Item

Description

SessionType

Type of LDP sessions.

Local

Number of local LDP sessions.

Remote

Number of remote LDP sessions.

Local&Remote

Number of coexistent local and remote LDP sessions.

Total

Total number of sessions.

Not Operational

Number of sessions in the Not Operational state.

Operational

Number of sessions in the Operational state.

SessionStatistics

Total number of local sessions, remote sessions, and coexistent local and remote sessions.

display mpls ldp troubleshooting

Function

The display mpls ldp troubleshooting command displays device information when an LDP session is disconnected on a device.

Format

display mpls ldp troubleshooting

Parameters

None

Views

All view

Default Level

1: Monitoring level

Usage Guidelines

If an LDP session on a device is disconnected, run the display mpls ldp troubleshooting command to check the device information for troubleshooting.

Example

# Display device information when an LDP session is disconnected on a device.

<HUAWEI> system-view
[~HUAWEI] display mpls ldp troubleshooting
Session Troubleshooting:
Total counts: 5
--------------------------------------------------------------------------------
Sequence   Time                       Event Description                           
--------------------------------------------------------------------------------
1          2015-11-24 16:15:29        The LDP peer 5.5.5.5 went Down because a not
                                      ification of Hold Timer Expired was received
                                       from the peer. Please check the peer reacha
                                      bility.(CPU = 12%, PingResult = 0 packets su
                                      ccess, 5 packets timeout)                   
2          2015-11-24 15:51:32        The LDP peer 5.5.5.5 went Down because MPLS 
                                      LDP was disabled. Please check the LDP confi
                                      guration.                                   
3          2015-11-24 13:12:04        The LDP peer 5.5.5.5 went Down because MPLS 
                                      LDP was disabled. Please check the LDP confi
                                      guration.                                   
4          2015-11-24 13:04:35        The LDP peer 5.5.5.5 went Down because the r
                                      eset mpls ldp command was run. Please run th
                                      e display logbuffer command to check whether
                                       the reset mpls ldp command was run.        
5          2015-11-24 12:52:55        The LDP peer 5.5.5.5 went Down because the H
                                      ello hold time expired. Please check the pee
                                      r reachability.(CPU = 17%, PingResult = 0 pa
                                      ckets success, 5 packets timeout)           
 
--------------------------------------------------------------------------------
Table 11-29  Description of the display mpls ldp troubleshooting command output
Item Description
Session Troubleshooting Troubleshooting information for an LDP session disconnection
Total counts Total number of entries
Sequence Entry sequence number
Time Date and time when the information was recorded
Event Description Event description:
  • CPU: CPU usage
  • PingResult: number of discarded packets and sent packets among sent ping packets

display mpls lsp

Function

The display mpls lsp command displays information about LSPs.

Format

display mpls lsp [ { exclude | include } ip-address mask-length ] [ verbose ]

display mpls lsp [ outgoing-interface interface-type interface-number | nexthop ip-address ] [ lsr-role { egress | ingress | transit } ] [ verbose ]

display mpls lsp protocol ldp [ include ip-address mask-length ] [ outgoing-interface interface-type interface-number ] [ nexthop ip-address ] [ lsr-role { egress | ingress | transit } ] [ in-label in-label-value ] [ verbose ]

display mpls lsp protocol bgp [ nexthop ip-address ] [ verbose ]

display mpls lsp protocol bgp { exclude | include } ip-address mask-length [ lsr-role { egress | ingress | transit } ] [ verbose ]

display mpls lsp protocol bgp [ nexthop ip-address ] lsr-role { egress | ingress | transit } [ verbose ]

Parameters

Parameter Description Value
protocol Displays information about LSPs of a specified type. -
ldp Indicates LDP. -
bgp Indicates BGP. -
exclude Displays information about LSPs, excluding information about the specific FEC. -
include Displays information about LSPs, including information about the specific FEC. -
ip-address Displays information about LSPs of a specified IPv4 address. The value is in dotted decimal notation.
mask-length Specifies the mask length of the specified IPv4 address. The value is an integer ranging from 0 to 32.
outgoing-interface interface-type interface-number Indicates the type and number of an outbound interface. You can view the configuration of an LSP on a specified interface. -
in-label in-label-value Displays information about LSPs of a specified incoming label. The value is an integer ranging from 0 to 1048575.
nexthop ip-address Displays information about LSPs of a specified next hop IPv4 address. The value is in dotted decimal notation.
lsr-role Displays information about all LSPs on the current LSR that plays a specified role. -
egress Displays information about LSPs of an egress LSR. -
ingress Displays information about LSPs of an ingress LSR. -
transit Displays information about LSPs of a transit LSR. -
verbose Displays detailed information about LSPs. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

If you do not specify a parameter, information about all LSPs is displayed.

Example

# Display information about all types of LSPs.

<HUAWEI> display mpls lsp


-------------------------------------------------------------------------------
LSP Information: LDP LSP
-------------------------------------------------------------------------------
              FEC  In/Out Label    In/Out IF                      Vrf Name
        1.1.1.3/32 3/NULL          -/-                            
       1.1.1.12/32 NULL/0          -/Vlanif1002                   
       1.1.1.12/32 NULL/0          -/Vlanif1000                   
    10.12.12.12/32 NULL/0          -/Vlanif1002                   
    10.12.12.12/32 NULL/0          -/Vlanif1000                   
    10.13.13.13/32 3/NULL          -/-                            

# Display detailed information about all types of LSPs.

<HUAWEI> display mpls lsp verbose


-------------------------------------------------------------------------------
LSP Information: LDP LSP
-------------------------------------------------------------------------------
  No.                 :  1
  VrfIndex            :  --
  Fec                 :  10.2.2.2/32
  Nexthop             :  172.16.1.2
  In Label            :  NULL
  Out Label           :  3
  In Interface        :  --
  Out Interface       :  Vlanif20
  Lsp Index           :  5000002
  Type                :  Primary
  Out Segment Index   :  5000001
  Lsr Type            :  Ingress
  Outgoing Tunnel ID  :  0x0
  Label Operation     :  PUSH
  MPLS Mtu            :  --
  LSP Age             :  101 sec
Table 11-30  Description of the display mpls lsp command output

Item

Description

LSP Information

LSP information:
  • LDP LSP: created using LDP.

  • BGP LSP: an LSP created using BGP based on private or public IPv4 BGP routes.

  • L3VPN LSP: an LSP based on IPv4 VPN routes received by means of BGP.

FEC/Fec

Forwarding equivalence class. Usually, the value is the destination address of an LSP.

In/Out Label

Values of the incoming and outgoing labels.

In/Out IF

Names of the incoming and outbound interfaces.

Vrf Name

Name of a VPN instance.

No.

Serial number of an LSP.

VrfIndex

Index of a VPN instance.

Nexthop

IP address of the next hop of an LSP.

In Label

Value of an incoming label.

Out Label

Value of an outgoing label.

In Interface

Name of an inbound interface.

Out Interface

Name of an outbound interface.

Lsp Index

Index number of an LSP, which uniquely identifies an LSP that is established using a specific protocol.

Type

Type of LSP:

  • Primary: The LSP is the primary path LSP.

  • Backup: The LSP is the backup path LSP.

Out Segment Index

Indicates the OutSegment index.

Lsr Type

Role of an LSR on an LSP:

  • Ingress

  • Transit

  • Egress

Outgoing Tunnel ID

Index of an LSP to which traffic is iterated.

Label Operation

Type of a label operation:

  • PUSH

  • SWAP

  • POP

  • SWAPPUSH

MPLS Mtu

Maximum transmission unit (MTU) of an interface of an LSP.

LSP Age

Time elapsed since an LSP was set up.

display mpls lsp statistics

Function

The display mpls lsp statistics command displays statistics about the LSPs that are in the Up state and the number of the LSPs that are activated on the ingress, transit, and egress nodes.

Format

display mpls lsp statistics

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Run the display mpls lsp statistics command to view statistics about the LSPs that are in the Up state.

To view detailed information about the LSPs and CR-LSPs, run the display mpls lsp command.

Example

# Display statistics about LSPs.

<HUAWEI> display mpls lsp statistics
Lsp Type           Total   Ingress   Transit    Egress
----------------------------------------------------------------------          
STATIC LSP             0         0         0         0
STATIC CRLSP           0         0         0         0
LDP LSP                4         2         0         2
LDP IPV6 LSP           0         0         0         0
RSVP CRLSP             0         0         0         0
BGP LSP                0         0         0         0
ASBR LSP               0         0         0         0
BGP IPV6 LSP           0         0         0         0
L3VPN IPV6 LSP         0         0         0         0
----------------------------------------------------------------------          
LSP                    4         2         0         2
CRLSP                  0         0         0         0
----------------------------------------------------------------------          
Lsp Type           IngressLspBypassState         TransitLspBypassState
             ExistNotUsed          InUse   ExistNotUsed          InUse
RSVP CRLSP              0              0              0              0
----------------------------------------------------------------------
Table 11-31  Description of the display mpls lsp statistics command output

Item

Description

Lsp Type

Type of an LSP:
  • STATIC LSP: a static LSP.
  • STATIC CRLSP: a static CR-LSP.
  • LDP LSP: created using LDP.
  • LDP IPv6 LSP: an LSP created using LDP based on private IPv6 routes.
  • RSVP CRLSP: an MPLS TE tunnel created using RSVP-TE.
  • BGP LSP: an LSP created using BGP based on private or public IPv4 BGP routes.
  • ASBR LSP: created using BGP based on received IPv4 VPN route.
  • BGP IPV6 LSP: an LSP created using BGP based on private IPv6 routes.
  • L3VPN IPV6 LSP: created using BGP based on received IPv6 VPN routes.
  • LSP: Label Switched Path.
  • CRLSP: Constraint-based Routed Label Switched Path.
  • Detour CRLSP: automatically created a detour LSP on each eligible node along primary CR-LSP.

Total

Number of LSPs of a specific type.

Ingress

Number of LSPs on the local ingress LSR.

Transit

Number of LSPs on the local transit LSR.

Egress

Number of LSPs on the local egress LSR.

IngressLspBypassState

Status of LSPs protected by bypass tunnels on the ingress:
  • ExistNotUsed: LSPs are not used.
  • InUse: LSPs are used.

TransitLspBypassState

Status of LSPs protected by bypass tunnels on the transit:
  • ExistNotUsed: LSPs are not used.
  • InUse: LSPs are used.
Related Topics

display mpls route-state

Function

The display mpls route-state command displays routing information about a dynamic LSP.

Format

display mpls route-state [ { exclude | include } { idle | ready | settingup } | destination-address mask-length ] [ verbose ]

Parameters

Parameter Description Value
exclude Displays routing information excluding the specified route. -
include Displays information about a specified route. -
idle Indicates that a route is not used to establish an LSP. -
ready Indicates that a route has been used to establish an LSP. -
settingup Indicates that a signaling protocol is creating an LSP. -
destination-address Specifies the destination address. The value is in dotted decimal notation.
mask-length Specifies the mask length of a specified destination address. The value is an integer ranging from 0 to 32.
verbose Displays detailed routing information about an LSP. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

After completing LDP LSP configurations, run the display mpls ldp lsp command to view information about an LDP LSP. If the command output displays no information about the LDP LSP, run the display mpls route-state command to view LDP LSP routing information.

Example

# Display detailed information about routes of dynamic LSPs.

<HUAWEI> display mpls route-state verbose
Codes: B(BGP), I(IGP), L(Public Label BGP), O(Original BGP), U(Unknow)
--------------------------------------------------------------------------------
DestAddress/Mask   Next-Hop        Out-Interface              State LSP VRF Type
--------------------------------------------------------------------------------
       10.1.1.1/32 10.10.1.1       Vlanif100                  READY 1   0      I
     LspIndex: 5000003    InLabel: NULL       OutLabel: 3           
      10.10.1.0/24 10.10.1.2        Vlanif100                 READY 1   0      I
     LspIndex: 5000002    InLabel: 3          OutLabel: NULL 
Table 11-32  Description of the display mpls route-state verbose command output

Item

Description

DestAddress/Mask

Destination IP address and mask length.

Next-Hop

Next hop IP address.

Out-Interface

Outbound interface.

State

Routing state of the MPLS control plane:
  • IDLE: The route is not used to establish an LSP.

  • SETTINGUP: A signaling protocol is creating an LSP.

  • READY: The route has been used to establish an LSP. Static LSPs are only in READY state.

LSP

Number of LSPs reachable to the destination address. If the displayed value is not 0, there are LSPs reachable to the destination address and LSP information about these LSPs is also displayed.

VRF

Index of a VPN instance.

The value 0 indicates the public network.

Type

Route type:
  • B: BGP routes

  • I: IGP routes

  • L: labeled BGP routes of a public network

  • O: original BGP routes

  • U: unidentified routes (such as multicast routes)

LspIndex

Index of an LSP established using the route.

InLabel

Incoming label of an LSP established using the route. If NULL is displayed, the current node is the ingress node of the LSP; if a number is displayed, the current node is the transit or egress node of the LSP.

OutLabel

Outgoing label of an LSP established using the route.

display ospf ldp-sync interface

Function

The display ospf ldp-sync interface command displays the status of LDP and OSPF synchronization on an interface.

Format

display ospf [ process-id ] ldp-sync interface { all | interface-type interface-number }

Parameters

Parameter Description Value
process-id Specifies an OSPF process ID. The value is an integer ranging 1 to 4294967295. The default value is 1.
all Displays information about the synchronization status on all interfaces enabled with LDP and OSPF synchronization. -
interface-type interface-number Displays information about the synchronization status on a specified interface.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

For all interfaces that are enabled with LDP and OSPF synchronization, run the display ospf ldp-sync interface command to view information about the status of LDP and OSPF synchronization.

Example

# Display information about the status of LDP and OSPF synchronization on a specified interface.

<HUAWEI> display ospf ldp-sync interface vlanif 100

 Area 0.0.0.0
 Interface Vlanif100
 HoldDown Timer: 9         HoldMaxCost Timer: 50
 LDP State: Up             OSPF Sync State: Sync-Achieved
Table 11-33  Description of the display ospf ldp-sync interface command output

Item

Description

Area

ID of the OSPF area to which the interface belongs.

Interface

Interface connected to neighbors.

HoldDown Timer

Interval at which the interface waits to create an LDP session without creating the OSPF neighbor relationship.

The default interval is 10 seconds.

HoldMaxCost Timer

Interval at which OSPF advertises the maximum metric in LSAs sent by the local device.

The default interval is infinite.

NOTE:

If the value of this field is infinite, OSPF keeps advertising the maximum metric value in LSAs sent by the local device before the LDP session is reestablished.

LDP State

Status of an LDP session:
  • Up

  • Down

OSPF Sync State

Status of LDP and OSPF synchronization:
  • Sync-Achieved: The creation of an LDP session and establishment of the OSPF neighbor relationship are synchronized.

  • HoldDown: The interface is waiting to create an LDP session without creating the OSPF neighbor relationship.

  • HoldMaxCost: OSPF advertises the maximum metric in LSAs or LSPs sent by the local device.

  • Init: the initial state.

display snmp-agent trap feature-name ldp all

Function

The display snmp-agent trap feature-name ldp all command displays the status of all traps on the MPLS LDP module.

Format

display snmp-agent trap feature-name ldp all

Parameters

None

Views

All views

Default Level

3: Management level

Usage Guidelines

Run the display snmp-agent trap feature-name ldp all command to view the status of all traps on the LDP module. The status can be configured using the snmp-agent trap enable feature-name ldp command.

Example

# Display all trap messages on the MPLS LDP module.

<HUAWEI> display snmp-agent trap feature-name ldp all
------------------------------------------------------------------------------
Feature name: LDP
Trap number : 5
------------------------------------------------------------------------------
Trap name                      Default switch status   Current switch status  
Session-Down-MIB               off                     on                     
Session-Retry                  off                     off                    
Session-Up-MIB                 off                     off                    
hwmplsldpvirtualtunneldown     off                     off                    
hwmplsldpvirtualtunnelup       off                     off                    
Table 11-34  Description of the display snmp-agent trap feature-name ldp all command output

Item

Description

Feature name

Name of the module to which a trap message belongs.

Trap number

Number of trap messages.

Trap name

Name of a trap message of the MPLS LDP module:

  • Session-Retry: An LDP session is reestablished.
  • Session-Up-MIB: An LDP session goes Up through the MIB.
  • Session-Down-MIB: An LDP session goes Down through the MIB.
  • hwmplsldpvirtualtunneldown: An LDP virtual tunnel goes Down.
  • hwmplsldpvirtualtunnelup: An LDP virtual tunnel goes Up.

Default switch status

Default status of the trap function:
  • On: The trap function is enabled by default.
  • Off: The trap function is disabled by default.

Current switch status

Current status of the trap function:
  • On: The trap function is enabled.
  • Off: The trap function is disabled.

display snmp-agent trap feature-name mpls_lspm all

Function

The display snmp-agent trap feature-name mpls_lspm all command displays all trap messages on the MPLS LSPM module.

Format

display snmp-agent trap feature-name mpls_lspm all

Parameters

None

Views

All views

Default Level

3: Management level

Usage Guidelines

Run the display snmp-agent trap feature-name mpls_lspm all command to view the status of all traps on the MPLS LSPM module. The status can be configured using the snmp-agent trap enable feature-name mpls_lspm command.

Example

# Display all trap messages on the MPLS LSPM module.

<HUAWEI> display snmp-agent trap feature-name mpls_lspm all
------------------------------------------------------------------------------   
Feature name: MPLS_LSPM                                          
Trap number : 8                                        
------------------------------------------------------------------------------
Trap name                      Default switch status   Current switch status        
hwMplsLspThresholdExceed       off                     on   
hwMplsLspThresholdExceedClear  off                     on 
hwMplsLspTotalCountExceed      off                     on    
hwMplsLspTotalCountExceedClear off                     on 
hwMplsResourceThresholdExceed  off                     on  
hwMplsResourceThresholdExceedClear              
                               off                     on
hwMplsResourceTotalCountExceed off                     on    
hwMplsResourceTotalCountExceedClear                                
                               off                     on   
Table 11-35  Description of the display snmp-agent trap feature-name mpls_lspm all command output

Item

Description

Feature name

Name of the module to which a trap message belongs.

Trap number

Number of trap messages.

Trap name

Name of a trap message of the MPLS LSPM module:

  • hwMplsLspThresholdExceed: Enables the function to generate an alarm if the number of LSPs exceeds the alarm threshold.
  • hwMplsLspThresholdExceedClear: Enables the function to clear an alarm if the number of LSPs falls below the alarm threshold.
  • hwMplsLspTotalCountExceed: Enables the function to generate an alarm if the number of LSPs exceeds the maximum limit.
  • hwMplsLspTotalCountExceedClear: Enables the function to clear an alarm if the number of LSPs falls below the maximum limit.
  • hwMplsResourceThresholdExceed: Enables the function to generate an alarm if the number of used MPLS resources exceeds the alarm threshold.
  • hwMplsResourceThresholdExceedClear: Enables the function to clear an alarm if the number of used MPLS resources falls below the alarm threshold.
  • hwMplsResourceTotalCountExceed: Enables the function to generate an alarm if the number of used MPLS resources exceeds the maximum limit.
  • hwMplsResourceTotalCountExceedClear: Enables the function to clear an alarm if the number of used MPLS resources falls below the maximum limit.

Default switch status

Default status of the trap function:
  • on: The trap function is enabled by default.
  • off: The trap function is disabled by default.

Current switch status

Current status of the trap function:
  • on: The trap function is enabled.
  • off: The trap function is disabled.

graceful-delete

Function

The graceful-delete command enables LDP graceful deletion.

The undo graceful-delete command disables LDP graceful deletion.

By default, LDP graceful deletion is disabled.

Format

graceful-delete

undo graceful-delete

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

This command is used to resolve the problems in the following scenarios:

  • In the scenario where links are not backed up, when a non-physical link fault occurs and the LDP session goes Down, if the device immediately instructs the upstream device to withdraw labels, the upstream device will be informed of the fault and the entire network will become unstable.
  • In the LDP auto FRR scenario, if the LDP session on the primary link goes Down due to a physical link fault or an LDP session fault, and LDP on the local device immediately instructs the upstream device to withdraw labels, the LSP on the secondary link will require LDP to allocate labels to the upstream device again, prolonging the convergence time and FRR switching time. As a result, packet loss occurs.
  • In the LDP-IGP synchronization scenario, if the physical and protocol status of the primary link is proper but the LDP session on the primary link goes Down, LDP-IGP synchronization enables LDP to inform the IGP of the primary link fault, and the IGP configures the maximum cost value for the primary link. LDP then immediately instructs the upstream device to withdraw labels and allocates labels to the upstream device because a new LSP is set up on the secondary link, prolonging the LSP convergence time. As a result, packet loss occurs.

After LDP graceful deletion is configured, the preceding problems can be resolved. After the LDP session goes Down, LDP does not immediately instruct the upstream device to withdraw labels but keeps the LSP until LSP switchover is complete, ensuring uninterrupted traffic and preventing LDP LSP flapping on the entire network. This speeds up traffic switchover using LDP Auto FRR and LDP-IGP synchronization and improves the network reliability.

Prerequisites

The mpls ldp (system view) command is used globally to enable MPLS LDP.

Follow-up Procedure

Run the graceful-delete timer command to set the delay value after which LDP instructs the upstream device to withdraw labels.

Example

# Enable LDP graceful deletion.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] graceful-delete

graceful-delete timer

Function

The graceful-delete timer command sets the delay after which LDP instructs the upstream device to withdraw labels when an LDP session goes Down.

The undo graceful-delete timer command restores the default setting.

By default, LDP instructs the upstream device to withdraw labels 5 seconds after the LDP session goes Down.

Format

graceful-delete timer timer

undo graceful-delete timer

Parameters

Parameter Description Value
timer Specifies the delay after which LDP instructs the upstream device to withdraw labels when an LDP session goes Down. The value is an integer ranging from 1 to 65535, in seconds.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When an LDP session goes Down, the LSP and the LDP session will be deleted, causing service interruption. After LDP graceful deletion is configured, LDP does not immediately instruct the upstream device to withdraw labels but keeps the LSP until the LDP session is restored, ensuring uninterrupted traffic and preventing LDP LSP flapping. This improves the network reliability. Run the graceful-delete timer command to set the value for the graceful deletion timer. Restoring the default value for the graceful deletion timer is recommended.

Prerequisites

Graceful deletion has been enabled globally using the graceful-delete command.

Follow-up Procedure

Run the display mpls ldp command to check whether the configuration is complete.

Precautions

Do not set a large value for the graceful deletion timer, preventing labels for the faulty LSP from retaining for a long period of time.

Example

# Set the delay after which LDP instructs the upstream device to withdraw labels when an LDP session goes Down to 10 seconds.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] graceful-delete
[*HUAWEI-mpls-ldp] graceful-delete timer 10

graceful-restart (MPLS-LDP view)

Function

The graceful-restart command enables LDP GR.

The undo graceful-restart command disables LDP GR.

By default, LDP GR is disabled.

Format

graceful-restart

undo graceful-restart

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In LDP GR mode, when AMB/SMB switchover or protocol restart occurs on the neighboring device of the local device, the local device (GR helper) helps the device (restarter) to restart without interrupting packet forwarding.

If LDP GR is not enabled, during the AMB/SMB switchover or upgrade, the neighboring device deletes the LSP because the session is in the Down state. As a result, the traffic is interrupted in a short time. If LDP GR is enabled, the labels before and after unexpected AMB/SMB switchover or protocol restart can be consistent, and uninterrupted MPLS forwarding is ensured.

By default, the device with double MPUs uses NSR.

NOTE:

Currently, LDP supports only GR helper.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp(system view) command in the system view.

Precautions

Enabling or disabling GR causes the reestablishment of all LDP sessions.

Example

# Enable LDP GR.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] graceful-restart
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y

graceful-restart timer neighbor-liveness

Function

The graceful-restart timer neighbor-liveness command sets the value of the Neighbor-liveness timer.

The undo graceful-restart timer neighbor-liveness command restores the default setting.

By default, the value of the Neighbor-liveness timer is 600 seconds.

Format

graceful-restart timer neighbor-liveness time

undo graceful-restart timer neighbor-liveness

Parameters

Parameter Description Value
time Specifies the value of the Neighbor-liveness timer. The value is an integer ranging from 3 to 3600, in seconds.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The value of the neighbor-liveness timer defines the LDP GR period.

During LDP GR, the reestablishment time of the LDP session is negotiated as the smaller value between the value of the neighbor-liveness timer on the GR helper and the value of the Reconnect timer on the GR restarter.

In general, the default value of the timer is recommended. When the number of LSPs on a network is small, you can set a smaller value for the neighbor-liveness timer to shorten the GR period.

Prerequisites

MPLS and MPLS LDP have been enabled globally.

LDP GR has been enabled globally.

Precautions

Changing the value of the neighbor-liveness timer causes the reestablishment of all the LDP sessions.

Example

# Set the value of the Neighbor-liveness timer to 500 seconds.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] graceful-restart
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
[*HUAWEI-mpls-ldp] graceful-restart timer neighbor-liveness 500
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y

graceful-restart timer reconnect

Function

The graceful-restart timer reconnect command sets the value of the Reconnect timer of an LDP session.

The undo graceful-restart timer reconnect command restores the default setting.

By default, the Reconnect timer is set to 300 seconds.

Format

graceful-restart timer reconnect time

undo graceful-restart timer reconnect

Parameters

Parameter Description Value
time Specifies the value of a Reconnect timer of an LDP session. The value is an integer ranging from 3 to 3600, in seconds.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the GR restarter performs the active/standby switchover, the GR helper detects that the LDP session with the GR restarter fails, and then starts the Reconnect timer and waits for the reestablishment of the LDP session.
  • If no LDP session between the GR helper and the GR restarter has been established after the Reconnect timer times out, the GR helper immediately deletes the MPLS forwarding entries associated with the GR restarter and exits from the GR help process.

  • If the LDP session between the GR helper and the GR restarter is established before the Reconnect timer times out, the GR helper deletes the timer and starts the Recovery timer.

During LDP GR, when the reestablishment time of the LDP session is negotiated, the value of the Reconnect timer that actually takes effect on the local end is the smaller value between the value of the neighbor-liveness timer on the GR helper and the value of the Reconnect timer on the GR restarter.

Prerequisites

MPLS and MPLS LDP have been enabled globally.

LDP GR has been enabled globally.

Precautions

Changing the value of the Reconnect timer causes the reestablishment of all the LDP sessions.

Example

# Set the time of the Reconnect timer of an LDP session to 270 seconds.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] graceful-restart
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
[*HUAWEI-mpls-ldp] graceful-restart timer reconnect 270
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y

graceful-restart timer recovery

Function

The graceful-restart timer recovery command sets the value of the LSP Recovery timer.

The undo graceful-restart timer recovery command restores the default setting.

By default, the LSP Recovery timer is set to 300 seconds.

Format

graceful-restart timer recovery time

undo graceful-restart timer recovery

Parameters

Parameter Description Value
time Specifies the value of an LSP Recovery timer. The value is an integer ranging from 3 to 3600, in seconds.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the LDP session is reestablished, the GR helper starts the Recovery timer and waits for the recovery of the LSP.
  • If the Recovery timer times out, the GR helper considers that the GR process is complete on the GR restarter and deletes the unrecovered LSPs.

  • If all the LSPs recover before the Recovery timer times out, the GR helper considers that the GR process is complete on the GR restarter only after the Recovery timer times out.

When a network with a large number of routes is faulty, run the graceful-restart timer recovery command to increase the value of the Recovery timer to ensure that all the LSPs recover within the timeout period of the timer.

During the LDP GR process, the value of the LSP Recovery timer that actually takes effect on the local end is negotiated as the smaller one of the values of the LSP Recovery timers configured on both ends of an LDP session.

Prerequisites

MPLS and MPLS LDP have been enabled globally.

LDP GR has been enabled globally.

Precautions

Changing the value of the LSP Recovery timer causes the reestablishment of all the LDP sessions.

Example

# Set the value of the LSP Recovery timer to 330 seconds.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] graceful-restart
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
[*HUAWEI-mpls-ldp] graceful-restart timer recovery 330
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y

gtsm peer valid-ttl-hops

Function

The gtsm peer valid-ttl-hops command configures the generalized TTL security mechanism (GTSM) on a specified LDP peer.

The undo gtsm command deletes the GTSM on all LDP peers or a specified LDP peer.

By default, no LDP peer is configured with the GTSM.

Format

gtsm peer ip-address valid-ttl-hops hops

undo gtsm { all | peer ip-address }

Parameters

Parameter Description Value
peer ip-address Specifies the transport address of an LDP peer. The value is in dotted decimal notation.
valid-ttl-hops hops Specifies the maximum number of valid hops permitted by the GTSM. The value is an integer ranging from 1 to 255.
all Indicates all LDP peers. -

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The GTSM checks TTL values to verify packets and protect devices against attacks. LDP peers are configured with the GTSM and a valid TTL range to check TTLs in LDP packets exchanged between them. If the TTL in an LDP packet is out of the valid range, this LDP packet is considered invalid and discarded. The GTSM defends against CPU-based attacks initiated using a large number of forged packets and protects upper-layer protocols.

If the value of hops is set to the maximum number of valid hops permitted by GTSM, when the TTL values carried in the packets sent by an LDP peer are within the range [255 - Number of hops +1, 255], the packets are received; otherwise, the packets are discarded.

NOTE:

Configuring the GTSM on both ends of an LDP session is recommended.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp (system view) command.

Precautions

The valid TTL range is from 1 to 255 or from 1 to 64, depending on the specific vendor. If a Huawei device is connected to a non-Huawei device, set hops to a value in a valid range that both devices support; otherwise, the Huawei device will discard packets sent by the non-Huawei device, resulting in LDP session interruption.

Example

# On the LSR, set valid TTL values carried in LDP packets sent by the peer with transport address 2.2.2.9 to 254 and 255.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] gtsm peer 2.2.2.9 valid-ttl-hops 2

igp-sync-delay timer

Function

The igp-sync-delay timer command sets the value of the igp-sync-delay timer.

The undo igp-sync-delay timer command restores the default value of the igp-sync-delay timer.

By default, the value of the igp-sync-delay timer is 10s.

Format

igp-sync-delay timer value

undo igp-sync-delay timer

Parameters

Parameter Description Value
value Specifies the value of the igp-sync-delay timer. The value is an integer ranging from 0 to 65535, in seconds.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When an LDP session is reestablished on a faulty link, LDP starts the igp-sync-delay timer to wait for the establishment of an LSP.

After the igp-sync-delay timer times out, LDP notifies the IGP that synchronization is complete.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp (system view) command.

Precautions

If a large number of routes exist on a network, it is recommended that you set the igp-sync-delay timer to a large value. In most cases, every 400 routes require 1 second. For example, the timer is set to 25 seconds for 10,000 routes.

Example

# Set the value of the igp-sync-delay timer to 5 seconds.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] igp-sync-delay timer 5

ipv4-family (MPLS LDP view)

Function

The ipv4-family command displays the MPLS LDP IPv4 view.

By default, the MPLS LDP IPv4 view is not displayed.

Format

ipv4-family

Parameters

None

Views

MPLS LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The ipv4-family command displays the MPLS LDP IPv4 view. The lsp-trigger, propagate mapping, and auto-frr lsp-trigger, and outbound peer fec commands can be run in the MPLS LDP IPv4 view.

Prerequisites

The following operations have been performed:

  • Run the mpls command in the system view to enable MPLS globally.
  • Run the mpls ldp command in the system view to enable MPLS LDP globally.

Example

# Enter the MPLS LDP IPv4 view.

<HUAWEI>system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] ipv4-family
[*HUAWEI-mpls-ldp-ipv4]

isis ldp-sync

Function

The isis ldp-sync command enables synchronization between LDP and IS-IS on an interface.

The undo isis ldp-sync command disables synchronization between LDP and IS-IS on an interface.

By default, synchronization between LDP and IS-IS is disabled on an interface.

Format

isis ldp-sync

undo isis ldp-sync

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The LDP convergence speed depends on the convergence speed of IS-IS routes. To enable MPLS LDP on a network with the primary and backup links, the following problems may occur:
  • Upon a fault on the primary link, IS-IS routes and ISP are both switched to the backup link using LDP FRR. When the primary link recovers, IS-IS routes are switched back to the primary link earlier than LDP traffic because IGP route convergence is faster than LDP convergence. As a result, LSP traffic is lost.
  • If a fault occurs on the LDP session between nodes on the primary link where the IS-IS routes are working properly, the IS-IS routes still use the primary link and the LSP on the primary link is deleted. No IS-IS route exists on the backup link; therefore, no LSP can be established on the backup link. LSP traffic is lost.

Run the isis ldp-sync command to enable synchronization between LDP and IS-IS to prevent traffic loss in the preceding problems. Run this command on the interfaces on both ends of the link between the node where the primary LSP and the backup LSP diverge from each other and its LDP peer on the primary LSP.

Prerequisites

The IS-IS process has been started using the isis enable command in the interface view.

Example

# Enable synchronization between LDP and IS-IS on VLANIF100.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] isis enable 1
[*HUAWEI-Vlanif100] isis ldp-sync
# Enable synchronization between LDP and IS-IS on 10GE1/0/1.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] isis enable 1
[*HUAWEI-10GE1/0/1] isis ldp-sync

isis ldp-sync block

Function

The isis ldp-sync block command blocks synchronization between LDP and IS-IS on an interface.

The undo isis ldp-sync block command restores the default setting.

By default, synchronization between LDP and IS-IS is not blocked on an interface.

Format

isis ldp-sync block

undo isis ldp-sync block

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the ldp-sync enable command is run in an IGP process, Synchronization between LDP and IGP is enabled on the interfaces on which the neighbor status is Up. If the interfaces on a device carrying key services, ensure that the backup path does not pass through this device. In addition, you can block synchronization between LDP and IGP on a specified interface of the switch.

Prerequisites

The IS-IS process has been started using the isis enable command in the interface view.

Example

# Block synchronization between LDP and IS-IS on VLANIF100.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] isis enable 1
[*HUAWEI-Vlanif100] isis ldp-sync block
# Block synchronization between LDP and IS-IS on 10GE1/0/1.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] isis enable 1
[*HUAWEI-10GE1/0/1] isis ldp-sync block

isis mpls ldp auto-config disable

Function

The isis mpls ldp auto-config disable command disables IS-IS interfaces to be automatically enabled with the MPLS LDP function.

The undo isis mpls ldp auto-config disable command restores the default configuration of the MPLS LDP function on IS-IS interfaces.

By default, if the mpls ldp auto-config command is run in an IS-IS process, all interfaces that can establish IS-IS neighbors are automatically enabled with the MPLS LDP function. Otherwise, the function is disabled.

Format

isis mpls ldp auto-config disable

undo isis mpls ldp auto-config disable

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the mpls ldp auto-config command is run, all interfaces that can establish IS-IS neighbors in an IS-IS process are automatically enabled with the MPLS LDP function. To disable the MPLS LDP function on some interfaces, run the isis mpls ldp auto-config disable command in the interface view.

Precautions

If the mpls ldp auto-config command is not run in the IS-IS view, the isis mpls ldp auto-config disable command can be run normally, but does not take effect on interfaces.

If you run the isis mpls ldp auto-config disable command and then run the mpls ldp auto-config command, the isis mpls ldp auto-config disable command takes effect on interfaces.

Example

# Disable VLANIF10 to be automatically enabled with the MPLS LDP function.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 10
[*HUAWEI-Vlanif10] isis enable 1
[*HUAWEI-Vlanif10] isis mpls ldp auto-config disable
# Disable 10GE1/0/1 to be automatically enabled with the MPLS LDP function.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] isis enable 1
[*HUAWEI-10GE1/0/1] isis mpls ldp auto-config disable

isis timer ldp-sync hold-down

Function

The isis timer ldp-sync hold-down command sets the interval during which an interface waits for creating an LDP session before setting up the IS-IS neighbor relationship.

The undo isis timer ldp-sync hold-down command restores the default setting.

By default, the interval is 10 seconds.

Format

isis timer ldp-sync hold-down value

undo isis timer ldp-sync hold-down

Parameters

Parameter Description Value
value Specifies the interval during which an interface waits for creating an LDP session before setting up the IS-IS neighbor relationship. The value is an integer ranging from 0 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When the physical link with LDP and IS-IS synchronization enabled recovers, IS-IS enters the Hold-down state and starts the Hold-down timer to wait for the establishment of an LDP session. LDP and IS-IS are both switched back to the backup link.

Run the isis timer ldp-sync hold-down command to set the value of the Hold-down timer.

Prerequisites

The IS-IS process has been started using the isis enable command in the interface view.

Precautions

This command is circular in nature, and the latest configuration overrides the previous configurations.

Example

# Set the value of the Hold-down timer for VLANIF100 to 15 seconds, during which the interface waits for the establishment of an LDP session before setting up the IS-IS neighbor relationship.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] isis enable 1
[*HUAWEI-Vlanif100] isis timer ldp-sync hold-down 15

isis timer ldp-sync hold-max-cost

Function

The isis timer ldp-sync hold-max-cost command sets the interval during which IS-IS sends LSPs to advertise the maximum metric on the local device.

The undo isis timer ldp-sync hold-max-cost command restores the default setting.

By default, the local device running IS-IS keeps advertising the maximum cost in Link State PDUs.

Format

isis timer ldp-sync hold-max-cost { value | infinite }

undo isis timer ldp-sync hold-max-cost

Parameters

Parameter Description Value
value Specifies the interval during which IS-IS sends LSPs to advertise the maximum metric on the local device. The value is an integer ranging from 0 to 65535, in seconds.
infinite Indicates that IS-IS keeps advertising the maximum metric in LSPs on the local device before an LDP session is reestablished. -

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When the primary LSP recovers from a fault, run the isis timer ldp-sync hold-max-cost command to set the interval during which traffic is still transmitted along the backup LSP before the LDP session of the primary LSP is reestablished.

Select the parameters based on network requirements.
  • If IS-IS carries only LDP services, configure the parameter infinite to ensure that the selected IS-IS routes are always the same as the LDP LSPs.

  • If IS-IS carries multiple types of services including LDP services, set the parameter value to ensure that the teardown of LDP sessions does not affect IS-IS route selection or other services.

Prerequisites

The IS-IS process has been started using the isis enable command in the interface view.

Precautions

This command is circular in nature, and the latest configuration overrides the previous configurations.

Example

# Set the interval to 8 seconds, during which IS-IS sends LSPs to advertise the maximum metric on the local device.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] isis enable 1
[*HUAWEI-Vlanif100] isis timer ldp-sync hold-max-cost 8
# Set the interval to 8 seconds, during which IS-IS sends LSPs to advertise the maximum metric on the local device.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] isis enable 1
[*HUAWEI-10GE1/0/1] isis timer ldp-sync hold-max-cost 8

label advertise

Function

The label advertise command enables the egress node to advertise labels of a specified type to the penultimate hop.

The undo label advertise command restores the default setting.

By default, the egress node assigns implicit null labels to the penultimate hop.

Format

label advertise { explicit-null | implicit-null | non-null }

undo label advertise

Parameters

Parameter Description Value
explicit-null Disables Penultimate Hop Popping (PHP) and enables the egress node to assign explicit null labels to the penultimate hop. The value of the explicit null label is 0.
implicit-null Enables PHP and enables the egress node to assign implicit null labels to the penultimate hop. The value of the implicit null label is 3.
non-null Disables PHP and enable the egress node to assign normal labels to the penultimate hop. The value is equal to or greater than 16.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Run the label advertise command to configure the type of labels assigned to the penultimate hop on the egress node. The default configuration implicit-null is recommended. The setting eases the forwarding burden on the egress node, improving the forwarding efficiency.

You can choose a type as required.
  • implicit-null supports PHP, which allows the LSR at the penultimate hop to pop out the label from an MPLS packet and send the packet to the egress node. After receiving the packet, the egress node directly forwards the unlabeled IP packet or the single-labeled packet. PHP helps reduce the burden on the egress node.
  • non-null and explicit-null do not support PHP. The setting is resource consuming and is therefore not recommended.

    explicit-null supports MPLS QoS.

For LDP LSPs, run the reset mpls ldp command in the user view on the local LSR to validate the modification.

Prerequisites

MPLS has been enabled globally using the mpls (system view) command in the system view.

Precautions

The label advertise command takes effect only after the following requirements are met:
  • A master/slave MPU switchover is performed.
  • Users perform the following operations:
    • Run the reset mpls ldp command to restart the LDP instance of the public network.
    • Change the policy for triggering LDP LSP establishment and increase the route range used to trigger the LSP establishment.

      • Change the policy for triggering LDP LSP establishment from none to all. The policy can trigger the establishment of all LDP LSPs.
      • Change the policy for triggering LDP LSP establishment from host to all. The policy can trigger the establishment of LDP LSPs using all routes except for host routes.

Example

# Configure the egress node to assign explicit null labels to the penultimate hop.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] label advertise explicit-null
Related Topics

ldp-sync enable

Function

The ldp-sync enable command enables synchronization between LDP and IGP on all interfaces in an IGP process or instance.

The undo ldp-sync enable command disables synchronization between LDP and IGP on all interfaces in an IGP process or instance.

By default, synchronization between LDP and IGP is disabled on all IGP interfaces.

Format

ldp-sync enable [ mpls-binding-only ]

undo ldp-sync enable

Parameters

Parameter Description Value
mpls-binding-only Synchronization between LDP and IS-IS can only be enabled on MPLS LDP-enabled interfaces. This parameter can only be configured in the IS-IS view. -

Views

IS-IS view, OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Synchronization between LDP and IGP reduces LSP traffic loss on a network with both primary and backup LSPs. Traffic loss occurs in either of the following situations:
  • The primary LSP works properly and an LDP session between two nodes on the primary LSP fails. IGP guides traffic still through the primary LSP even though a primary/backup LSP switchover is performed.
  • If a link on the primary LSP or the primary LSP recovers, IGP routes converge. IGP routes associated with the primary LSP become reachable earlier than the primary LSP because IGP routes converge faster than LDP routes. IGP routes guide traffic through the primary LSP before the primary LSP recovers.

Synchronization between LDP and IGP delays IGP route advertisement so that the LDP session and IGP route can converge simultaneously.

After you run the ldp-sync enable command in the OSPF area view or IS-IS view:
  • If the IGP is OSPF, interfaces perform the following operations:
    • Interfaces whose neighbor status is Up on a P2P network run synchronization between LDP and IGP.
    • Interfaces whose neighbor status is Up on a broadcast network run synchronization between LDP and IGP between DRs and non-DRs/BDRs.
  • If the IGP is IS-IS, synchronization between LDP and IS-IS is enabled on all IS-IS interfaces.

Follow-up Procedure

Run the isis ldp-sync block or ospf ldp-sync block command to disable synchronization between LDP and IGP on desired IGP interfaces.

Precautions

Although the undo ldp-sync enable command has been run, synchronization between LDP and IGP configured using the isis ldp-sync or ospf ldp-sync command still takes effect on an IS-IS or OSPF interface.

When the isis ldp-sync command is configured on an interface, synchronization between LDP and IS-IS is enabled on the interface even if the mpls-binding-only parameter is specified in the IS-IS process.

Example

# Enable synchronization between LDP and IS-IS on all interfaces in an IS-IS instance.

<HUAWEI> system-view
[~HUAWEI] isis 100
[*HUAWEI-isis-100] ldp-sync enable

# Enable synchronization between LDP and OSPF on all interfaces in an OSPF instance.

<HUAWEI> system-view
[~HUAWEI] ospf 100
[*HUAWEI-ospf-100] area 0
[*HUAWEI-ospf-100-area-0.0.0.0] ldp-sync enable

loop-detect

Function

The loop-detect command enables a device to advertise the capability of loop detection during the initialization of an LDP session.

The undo loop-detect command disables a device from advertising the capability of loop detection during the initialization of an LDP session.

By default, a device cannot advertise the capability of loop detection during the initialization of an LDP session.

Format

loop-detect

undo loop-detect

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

The switch does not support the loop detection function. In the scenario where its neighbor supports the loop detection function and requires that the notification about whether the loop detection function is enabled be consistent on the two ends, run the loop-detect command to ensure that the switch sets up an LDP session with this neighbor.

Though the loop-detect command is run, the switch still does not support the LDP loop detection function but only has the loop detection negotiation capability.

Example

# Enable the device to advertise the capability of loop detection during the initialization of an LDP session.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] loop-detect

lsp-trigger bgp-label-route

Function

The lsp-trigger bgp-label-route command enables LDP to allocate labels to labeled BGP routes on the public network.

The undo lsp-trigger bgp-label-route command restores the default setting.

By default, LDP does not allocate labels to labeled BGP routes on the public network.

Format

lsp-trigger bgp-label-route [ ip-prefix ip-prefix-name ]

undo lsp-trigger bgp-label-route

Parameters

Parameter Description Value
ip-prefix ip-prefix-name Specifies the name of the IP prefix list that triggers the labeled BGP routes on the public network to set up LDP LSPs. The value is an existing IP prefix list name.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Both the lsp-trigger bgp-label-route command and the lsp-trigger command can be used to configure policies to trigger the establishment of LDP LSPs. The former command is used for labeled BGP routes on the public network, and the latter command is used for static routes and IGP routes.

NOTE:

Modifying the LSP-triggering policy during the LDP GR period is invalid.

Prerequisites

MPLS has been enabled globally using the mpls (system view) command.

Example

# Trigger the establishment of LDP LSPs according to labeled BGP routes on the public network.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] lsp-trigger bgp-label-route
Related Topics

lsp-trigger

Function

The lsp-trigger command sets a policy for establishing LDP LSPs.

The undo lsp-trigger command restores the default setting.

By default, LDP uses IP host routes with 32-bit addresses (excluding host routes with 32-bit interface addresses) to establish LSPs.

Format

lsp-trigger { all | host | ip-prefix ip-prefix-name | none }

undo lsp-trigger

Parameters

Parameter Description Value
all Indicates that all static and IGP routes trigger the establishment of LSPs. -
host Indicates that IP host routes with 32-bit addresses (excluding host routes with 32-bit interface addresses) trigger the establishment of LSPs. -
ip-prefix ip-prefix-name Specifies the name of the IP prefix list that triggers the establishment of LSPs. The value is an existing IP prefix list name.
none Indicates that the establishment of an LSP is not triggered. -

Views

MPLS view, MPLS-LDP-IPv4 view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After MPLS LDP is enabled, LSPs are automatically established. If no policy is configured, an increasing number of LSPs are established, wasting resources.

The lsp-trigger command configures a policy to allow LDP to use specified routes to establish LSPs. This setting prevents unwanted LSPs from being established and helps reduce resource wastes.

NOTE:

The lsp-trigger all command is not recommended. If this command is run, LDP uses all IGP routes to establish LSPs, causing a large number of unwanted LSPs to be established and wasting system resources. Before using this command, configure a policy for filtering out routes unnecessary for the LSP establishment. The policy helps reduce the number of LSPs to be established and save system resources.

Prerequisites

MPLS has been enabled globally using the mpls (system view) command.

Precautions

  • Modifying the LSP-triggering policy during the LDP GR period is invalid.

  • The lsp-trigger command can be used to configure policies only for ingress and egress LSPs on the public network and ingress and egress LSPs on the private network that are established using IGP routes. To configure a policy for triggering the transit LSP establishment, run the propagate mapping command.

  • The lsp-trigger host command can be run on either of the following nodes to provide a specific function:

    • Ingress: This command enables the ingress to use all routes with a 32-bit mask to establish LDP LSPs.
    • Egress: This command enables the egress to use local routes with a 32-bit mask to establish LDP LSPs.

    The lsp-trigger all command can be used to establish proxy egress LSPs. The lsp-trigger host command, however, cannot be used to establish proxy egress LSPs.

  • If the lsp-trigger command is run in both the MPLS view and MPLS-LDP-IPv4 view, the configuration in the latter view preferentially takes effect.

Example

# Trigger the establishment of LSPs based on all static and IGP routes.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] lsp-trigger all
Related Topics

lspv echo-reply compitable fec enable

Function

The lspv echo-reply compitable fec enable command enables a device to respond to MPLS echo request packets with MPLS echo reply packets that do not carry FEC information.

The undo lspv echo-reply compitable fec enable command disables a device from responding to MPLS echo request packets with MPLS echo reply packets that do not carry FEC information.

By default, a device is disabled from responding to MPLS echo request packets with MPLS echo reply packets that do not carry FEC information.

Format

lspv echo-reply compitable fec enable

undo lspv echo-reply compitable fec enable

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The tracert lsp command is used to check the fault point on a network, which facilitates fault diagnosis. This command uses MPLS echo request and MPLS echo reply packets to detect LSP connectivity.

When a Huawei device interworks with a non-Huawei device, if the Huawei device initiates a tracert lsp test, you can properly check the fault location on the network. If the non-Huawei device initiates a tracert lsp test and the Huawei device responds with an MPLS echo reply packet carrying FEC information, the non-Huawei device fails to identify the FEC information and therefore discards this packet, causing a test failure. To control the packet format and enable the device to respond to MPLS echo request packets with MPLS echo reply packets that do not carry FEC information, run the lspv echo-reply compitable fec enable command.

Prerequisites

The undo lspv mpls-lsp-ping echo disable command has been run in the system view to enable the device to respond to MPLS echo request packets before you run this command.

Example

# Enable a device to respond to MPLS echo request packets with MPLS echo reply packets that do not carry FEC information.

<HUAWEI> system-view 
[~HUAWEI] lspv echo-reply compitable fec enable

lspv mpls-lsp-ping cpu-defend

Function

The lspv mpls-lsp-ping cpu-defend command sets an upper limit for the rate of sending MPLS echo request packets to the main control board.

The undo lspv mpls-lsp-ping cpu-defend command restores the default rate.

By default, 1000 MPLS echo request packets are sent to the main control board per second.

Format

lspv mpls-lsp-ping cpu-defend cpu-defend

undo lspv mpls-lsp-ping cpu-defend [ cpu-defend ]

Parameters

Parameter Description Value
cpu-defend Specifies the rate of sending MPLS echo request packets to the main control board. The value is an integer ranging from 10 to 65535, expressed in packets per second.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

As the LSP connectivity checking is deployed on the main control board of a device, both the initiator and responder of an LSP ping test need to send LSP ping test packets to the main control board for processing. If a large number of packets are sent to the main control board, the CPU usage of the main control board increases, which adversely affects device operation. To prevent this problem, run the lspv mpls-lsp-ping cpu-defend command to set an upper limit for the rate of sending MPLS echo request packets to the main control board.

Configuration Impact

If the number of MPLS echo request packets sent to the main control board exceeds the specified upper limit, excess packets will be discarded.

Example

# Set the upper limit for the rate of sending MPLS echo request packets to the main control board to 1500 packets per second.
<HUAWEI> system-view
[~HUAWEI] lspv mpls-lsp-ping cpu-defend 1500

lspv mpls-lsp-ping echo disable

Function

The lspv mpls-lsp-ping echo disable command disables a device to respond to MPLS Echo Request packets.

The undo lspv mpls-lsp-ping echo disable command enables a device from responding to MPLS Echo Request packets.

By default, a device is enabled to respond to MPLS Echo Request packets.

Format

lspv mpls-lsp-ping echo disable

undo lspv mpls-lsp-ping echo disable

Parameters

None.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The ping and trace tests use ICMP packets to locate faulty nodes on a forwarding path. When an LSP fails, IP forwarding-based ICMP packets cannot be used to detect the faulty node.

In this case, the ping lsp and tracert lsp command can be used to locate the faulty node on the LSP. These commands use MPLS Echo Request and MPLS Echo Reply packets to detect the connectivity of an LSP. Both MPLS Echo Request and MPLS Echo Reply packets are encapsulated into UDP packets and transmitted through port 3503. The receiver distinguishes MPLS Echo Request and MPLS Echo Reply packets based on the port number. An MPLS Echo Request packet carries FEC information to be detected, and is sent along the same LSP as other packets with the same FEC information. In this manner, the connectivity of the LSP is checked. MPLS Echo Request packets are transmitted to the destination through MPLS, whereas MPLS Echo Reply packets are transmitted to the source through IP.

For network security or management, you can run the undo lspv mpls-lsp-ping echo disable command to enable a device to respond to MPLS Echo Request packets or run the lspv mpls-lsp-ping echo disable command to disable the device from responding to MPLS Echo Request packets. This function is implemented by enabling or disabling port 3503. By default, port 3503 is enabled.

After you run the ping lsp and tracert lsp command to detect the connectivity of an LSP, it is advised to run the lspv mpls-lsp-ping echo disable command to disable the device from responding to MPLS Echo Request packets to avoid occupation of system resources.

Precautions

If you run the lspv mpls-lsp-ping echo disable command to disable a device from responding to MPLS Echo Request packets, this device does not respond to the ping lsp and tracert lsp command. As a result, the ping or trace test with the address of the device as the destination address times out.

Example

# Disable a device to respond to MPLS Echo Request packets.

<HUAWEI> system-view
[~HUAWEI] lspv mpls-lsp-ping echo disable

lsr-id

Function

The lsr-id command sets the LSR ID of an LDP instance.

The undo lsr-id command restores the default setting.

By default, the LSR ID of an LDP instance is the LSR ID of the LSR where the LDP instance is configured

Format

lsr-id lsr-id

undo lsr-id

Parameters

Parameter Description Value
lsr-id Specifies the LSR ID of an LDP instance. The value is in dotted decimal notation.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, the LSR ID of an LDP instance is the same as the MPLS LSR ID configured using the mpls lsr-id command. On some networks such as the BGP/MPLS VPNs to which VPN instances apply, if the VPN address space and the public network address space overlap, configure LSR IDs for LDP instances to ensure the correct establishment of TCP connections.

Prerequisites

Precautions

Modifying or deleting the LSR ID of an LDP instance causes the reestablishment of all sessions in the LDP instance.

Example

# Set the LSR ID of an LDP instance to 2.2.2.3.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] lsr-id 2.2.2.3
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
Related Topics

md5-password

Function

The md5-password command sets the password that is used by a TCP connection during the creation of an LDP session.

The undo md5-password command disables MD5 authentication.

By default, MD5 authentication is disabled during the creation of an LDP session.

Format

md5-password { plain | cipher } peer-lsr-id password

undo md5-password peer-lsr-id

Parameters

Parameter Description Value
plain Displays the password in plain text.
NOTICE:

If plain is selected, the password is saved in the configuration file in plain text. In this case, users at a lower level can easily obtain the password by viewing the configuration file. This brings security risks. Therefore, it is recommended that you select cipher to save the password in cipher text.

-
cipher Displays the password in cipher text. -
peer-lsr-id Specifies the LSR ID of the peer, which identifies the peer LSR. The value is in dotted decimal notation.
password Specifies the password. The value is a string of characters, spaces not supported. For a plain password, the string is 1 to 255 characters. For an encrypted password, the string is 20 to 432 characters. When double quotation marks are used around the string, spaces are allowed in the string.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

MD5 authentication can be configured for a TCP connection over which an LDP session is established, improving security. Note that the peers of an LDP session can be configured with different encryption modes (plain or cipher text mode), but must be configured with a single password.

LDP MD5 authentication generates a unique digest for an information segment to prevent LDP packets from being modified. LDP MD5 authentication is stricter than common checksum verification for TCP connections.

A password can be set either in cipher text or plain text. A plain text password is a character string that is pre-configured and directly recorded in a configuration file. A cipher text password is a character string that is recorded in a configuration file after being encrypted using a specified algorithm.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

  • MD5 authentication and keychain authentication cannot be configured together on one peer. Note that MD5 encryption algorithm cannot ensure security. Keychain authentication is recommended.

  • If the password on a peer changes, the LDP session is reestablished and the LSP associated with the original LDP session is deleted.

Example

# Configure the local node to perform MD5 authentication when it establishes an LDP session with its peer.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] md5-password cipher 2.2.2.2 Huawei-123

md5-password all

Function

The md5-password all command enables LDP MD5 authentication in a batch for all LDP peers.

The undo md5-password all command disables LDP MD5 authentication in a batch for all LDP peers.

By default, MD5 authentication in a batch is disabled for all LDP peers. LDP MD5 authentication is recommended to ensure security.

Format

md5-password { plain | cipher } all password

undo md5-password all

Parameters

Parameter Description Value
plain

Indicates a simple text password.

A simple text password is saved in simple text in a configuration file. This format poses risks. A ciphertext password is recommended. To improve device security, periodically modify the password.

-
cipher Indicates a ciphertext password. -
password

Specifies an authentication password.

NOTE:
  • The new password is at least eight characters long and contains at least two of the following types: upper-case letters, lower-case letters, digits, and special characters.

  • For security purposes, you are advised to configure a password in ciphertext mode. To further improve device security, periodically change the password.

A password must not contain spaces. A simple text password is a string of 1 to 255 characters. A ciphertext password is a string of 1 to 255 characters. An MD5 ciphertext password is 20 bits to 432 bits long.

The string can contain spaces if it is enclosed with double quotation marks (").

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

MD5 authentication can be configured for a TCP connection over which an LDP session is established, improving security. LDP MD5 authentication generates a unique digest for an information segment to prevent LDP packets from being modified. LDP MD5 authentication is stricter than common checksum verification for TCP connections.

If a great number of LDP peers are configured, run the md5-password all command to enable MD5 authentication in a batch for all LDP peers.

Configuration Impact

After the md5-password all command is run, MD5 authentication takes effect on all LDP peers. If MD5 authentication fails, an LDP session fails to be established.

Precautions

  • LDP authentication configurations are prioritized in descending order: for a single peer, for a specified peer group, for all peers. Keychain and MD5 configurations of the same priority are mutually exclusive. Keychain authentication and MD5 authentication can be configured simultaneously for a specified LDP peer, for this LDP peer in a specified peer group, and for all LDP peers. The configuration with a higher priority takes effect. For example, if MD5 authentication is configured for Peer1 and then keychain authentication is configured for all LDP peers, MD5 authentication takes effect on Peer1.

  • The session is not re-established if the passwords on both ends are the same. If the interval between password settings on both ends exceeds the session Keepalive time and the passwords become different, the sessions is disconnected due to a timeout, causing an LSP to be deleted.
  • Note that the peers of an LDP session can be configured with different authentication modes (simple text or ciphertext), but must be configured with a single password.

Example

# Enable LDP MD5 authentication for all LDP peers.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] md5-password cipher all Huawei-123

md5-password peer-group

Function

The md5-password peer-group command enables LDP MD5 authentication in a batch for a specified LDP peer group.

The undo md5-password peer-group command disables LDP MD5 authentication in a batch for a specified LDP peer group.

By default, MD5 authentication in a batch is disabled for all peer groups. LDP MD5 authentication is recommended to ensure security.

Format

md5-password { plain | cipher } peer-group ip-prefix-name password

undo md5-password peer-group

Parameters

Parameter Description Value
plain

Indicates a simple text password.

A simple text password is saved in simple text in a configuration file. This format poses risks. A ciphertext password is recommended. To improve device security, periodically modify the password.

-
cipher Indicates a ciphertext password. -
ip-prefix-name

Specifies the name of an IP prefix list. The IP prefix list name is configured using the ip ip-prefix command.

The value is a string of 1 to 169 case-sensitive characters, spaces not supported. The string can contain spaces if it is enclosed with double quotation marks (").

password

Specifies an authentication password.

NOTE:
  • The new password is at least eight characters long and contains at least two of the following types: upper-case letters, lower-case letters, digits, and special characters.

  • For security purposes, you are advised to configure a password in ciphertext mode. To further improve device security, periodically change the password.

A password must not contain spaces. A simple text password is a string of 1 to 255 characters. A ciphertext password is a string of 1 to 255 characters. An MD5 ciphertext password is 20 bits to 432 bits long.

The string can contain spaces if it is enclosed with double quotation marks (").

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

MD5 authentication can be configured for a TCP connection over which an LDP session is established, improving security. LDP MD5 authentication generates a unique digest for an information segment to prevent LDP packets from being modified. LDP MD5 authentication is stricter than common checksum verification for TCP connections.

If a great number of LDP peers are configured, run the md5-password peer-group command to enable MD5 authentication in a batch for LDP peers in a specified peer group. An IP prefix list can be specified to define the range of IP addresses in a group.

Prerequisites

An IP prefix list has been configured using the ip ip-prefix command.

Configuration Impact

After the md5-password peer-group command is run, MD5 authentication takes effect on a specified LDP peer group. If MD5 authentication fails, an LDP session fails to be established.

Precautions

  • LDP authentication configurations are prioritized in descending order: for a single peer, for a specified peer group, for all peers. Keychain and MD5 configurations of the same priority are mutually exclusive. Keychain authentication and MD5 authentication can be configured simultaneously for a specified LDP peer, for this LDP peer in a specified peer group, and for all LDP peers. The configuration with a higher priority takes effect. For example, if MD5 authentication is configured for Peer1 and then keychain authentication is configured for all LDP peers, MD5 authentication takes effect on Peer1.

  • The session is not re-established if the passwords on both ends are the same. If the interval between password settings on both ends exceeds the session Keepalive time and the passwords become different, the sessions is disconnected due to a timeout, causing an LSP to be deleted.
  • Note that the peers of an LDP session can be configured with different authentication modes (simple text or ciphertext), but must be configured with a single password.

Example

# Enable LDP MD5 authentication for LDP peers with IP addresses matching the IP prefix list named list1.

<HUAWEI>system-view
[~HUAWEI] ip ip-prefix list1 permit 4.4.4.4 32
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] md5-password cipher peer-group list1 Huawei-123

mpls (system view)

Function

The mpls command enables MPLS on the local node and displays the MPLS view.

The undo mpls command deletes all MPLS configurations.

By default, no node is enabled with MPLS.

Format

mpls

undo mpls

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Run the mpls command on a network where MPLS services are to be deployed.

You can run MPLS-related commands only after running the mpls command.

Precautions

When MPLS services are configured on a network, LSR IDs must be configured. To specify an LSR ID, run the mpls lsr-id command in the system view, or the lsr-id command in the MPLS-LDP view.

The undo mpls command run in the system view deletes all MPLS configurations in the system view and interface view, except the MPLS LSR-ID.

When the system resource mode is set to large-arp, the device does not support the MPLS function. After the MPLS function is configured, you cannot change the system resource mode to large-arp.

Example

# Enable MPLS.

<HUAWEI> system-view
[~HUAWEI] mpls lsr-id 10.1.1.1
[*HUAWEI] mpls
Info: Mpls starting, please wait... OK!
Related Topics

mpls (interface view)

Function

The mpls command enables MPLS on an interface.

The undo mpls command disables MPLS on an interface.

By default, no interface is enabled with MPLS.

Format

mpls

undo mpls

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a network where MPLS services are deployed, after enabling MPLS on a node, enable MPLS on the interfaces of the node before performing other MPLS configurations.

Prerequisites

MPLS has been enabled globally using the mpls (system view) command.

Precautions

Running the undo mpls command in the interface view deletes all MPLS configurations on the interface.

Example

# Enable MPLS on the interface VLANIF100.
<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] interface vlanif 100 
[*HUAWEI-Vlanif100] mpls
# Enable MPLS on the interface 10GE1/0/1.
<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] interface 10ge 1/0/1 
[*HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls
Related Topics

mpls dynamic-label-number threshold-alarm

Function

The mpls dynamic-label-number threshold-alarm command sets alarm thresholds of dynamic label usage.

The undo mpls dynamic-label-number threshold-alarm command restores the default settings.

By default, the upper limit is 80%, and the lower limit is 70%.

Format

mpls dynamic-label-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls dynamic-label-number threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value Specifies the upper limit of dynamic label usage. The value is a percent integer ranging from 1 to 100. Using a value larger than 95 is not recommended. Using the default value 80 is recommended.
lower-limit lower-limit-value Specifies the lower limit of dynamic label usage. The value is a percent integer ranging from 1 to 100. The lower limit must be less than the upper limit. Using the default value 70 is recommended.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If dynamic labels run out but the system receives new dynamic label requests, the system fails to satisfy the requests because the dynamic labels are insufficient. As a result, the module that fails to be assigned labels works abnormally. The modules that apply for labels including MPLS LDP, BGP. To facilitate operation and maintenance, run mpls dynamic-label-number threshold-alarm command to set alarm thresholds of dynamic label usage. The system can alert users to the issue that dynamic labels will exhaust.

This command enables the system to generate an alarm in either of the following situations:

  • upper-limit-value: a percent indicating the upper limit of dynamic labels. If dynamic label usage reaches the upper limit, an alarm is generated.
  • lower-limit-value: a percent indicating the lower limit of dynamic labels. If dynamic label usage falls below the lower limit, a clear alarm can be generated.

Precautions

If the mpls dynamic-label-number threshold-alarm command is run more than once, the latest configuration overrides the previous one.

The mpls dynamic-label-number threshold-alarm command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsdynamiclabelthresholdexceed | hwmplsdynamiclabelthresholdexceedclear } command is run to enable the device to generate a dynamic label insufficiency alarm and its clear alarm.

Example

# Set the thresholds for triggering dynamic label alarms.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls dynamic-label-number threshold-alarm upper-limit 90 lower-limit 60

mpls remote-adjacency-number threshold-alarm

Function

The mpls remote-adjacency-number threshold-alarm command configures the conditions that trigger the threshold-reaching alarm and its clear alarm for remote LDP adjacencies.

The undo mpls remote-adjacency-number threshold-alarm command restores the default settings.

By default, the upper alarm threshold is 80%, and the lower alarm threshold is 75%.

Format

mpls remote-adjacency-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls remote-adjacency-number threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value

Sets the upper alarm threshold for the proportion of established remote LDP adjacencies to all supported ones.

The value is an integer ranging from 1 to 100, represented in percentage. Using a value larger than 95 is not recommended. Using the default value 80 is recommended.
lower-limit lower-limit-value

Sets the lower alarm threshold for the proportion of established remote LDP adjacencies to all supported ones.

The value is an integer ranging from 1 to 100, represented in percentage. The value must be smaller than the value of upper-limit-value. Using the default value 75 is recommended.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the number of remote LDP adjacencies reaches a specified upper limit, new remote LDP adjacencies cannot be configured due to insufficient resources. To alert the administrator in operation and maintenance, enable a device to generate an alarm when the proportion of established remote LDP adjacencies to all supported ones reaches a specified upper alarm threshold. The following parameters can be configured in the mpls remote-adjacency-number threshold-alarm command:

  • upper-limit-value: upper alarm threshold. If the proportion of established remote LDP adjacencies to all supported ones reaches the upper alarm threshold, an alarm can be generated.
  • lower-limit-value: lower alarm threshold. If the proportion of established remote LDP adjacencies to all supported ones falls below the lower alarm threshold, a clear alarm can be generated.

Precautions

  • If the mpls remote-adjacency-number threshold-alarm command is run more than once, the latest configuration overrides the previous one.

  • The mpls remote-adjacency-number threshold-alarm command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcethresholdexceed | hwmplsresourcethresholdexceedclear } command is run to enable the device to generate an MPLS resource insufficiency alarm and its clear alarm.

Example

# Configure conditions that trigger the threshold-reaching alarm and its clear alarm for remote LDP adjacencies.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls remote-adjacency-number threshold-alarm upper-limit 90 lower-limit 60

mpls ldp auto-config (IS-IS)

Function

The mpls ldp auto-config command enables all interfaces that can establish IS-IS neighbors in a specified IS-IS process to be automatically enabled with the MPLS LDP function.

The undo mpls ldp auto-config command disables all interfaces that can establish IS-IS neighbors in a specified IS-IS process to be automatically enabled with the MPLS LDP function.

By default, IS-IS interfaces are not automatically enabled with the MPLS LDP function.

Format

mpls ldp auto-config

undo mpls ldp auto-config

Parameters

None

Views

IS-IS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To enable the MPLS LDP function on IS-IS interfaces, you need to enable the MPLS LDP function globally first, and then enable the MPLS LDP function on interfaces. If too many interfaces need to be enabled with the function, the configuration method wastes too much time and energy, and cannot ensure the configuration accuracy. You can run the mpls ldp auto-config command to solve the problem. The command is configured in the IS-IS view, and enables all interfaces that can establish IS-IS neighbors to be automatically enabled with the MPLS LDP function. This simplifies the configuration and ensures correct configuration. You can run the undo mpls ldp auto-config command to disable the function as required.

Prerequisites

The MPLS LDP function has been enabled globally using the mpls ldp (system view) command.

Precautions

After the mpls ldp auto-config command is run, all interfaces that can establish IS-IS neighbors in an IS-IS process are automatically enabled with the MPLS LDP function. To disable LDP synchronization on some interfaces, run the isis mpls ldp auto-config disable command in the interface view to disable the MPLS LDP function.

Example

# Enable the MPLS LDP function on all interfaces that can establish IS-IS neighbors in IS-IS process 1.
<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls ldp
[*HUAWEI-mpls-ldp] quit
[*HUAWEI] isis 1
[*HUAWEI-isis-1] mpls ldp auto-config

mpls ldp auto-config (OSPF)

Function

The mpls ldp auto-config command enables all interfaces that can establish OSPF neighbors in a specified OSPF process to be automatically enabled with the MPLS LDP function.

The undo mpls ldp auto-config command disables all interfaces that can establish OSPF neighbors in a specified OSPF process to be automatically enabled with the MPLS LDP function.

By default, OSPF interfaces are not automatically enabled with the MPLS LDP function.

Format

mpls ldp auto-config

undo mpls ldp auto-config

Parameters

None

Views

OSPF view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

To enable the MPLS LDP function on OSPF interfaces, you need to enable the MPLS LDP function globally first, and then enable the MPLS LDP function on interfaces. If too many interfaces need to be enabled with the function, the configuration method wastes too much time and energy, and cannot ensure the configuration accuracy. You can run the mpls ldp auto-config command to solve the problem. The command is configured in the OSPF view, and enables all interfaces that can establish OSPF neighbors to be automatically enabled with the MPLS LDP function. This simplifies the configuration and ensures correct configuration. You can run the undo mpls ldp auto-config command to disable the function as required.

Prerequisites

The MPLS LDP function has been enabled globally using the mpls ldp (system view) command.

Precautions

After the mpls ldp auto-config command is run, all interfaces in an OSPF process are automatically enabled with the MPLS LDP function. To disable LDP synchronization on some interfaces, run the ospf mpls ldp auto-config disable command in the interface view to disable the MPLS LDP function.

Example

# Enable the MPLS LDP function on all interfaces in OSPF process 1.
<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls ldp
[*HUAWEI-mpls-ldp] quit
[*HUAWEI] ospf 1
[*HUAWEI-ospf-1] mpls ldp auto-config

mpls ldp (system view)

Function

The mpls ldp command enables LDP on the local node and displays the MPLS-LDP view.

The undo mpls ldp command deletes all LDP configurations.

By default, LDP is not enabled on a node.

Format

mpls ldp

undo mpls ldp

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a network where MPLS LDP needs to be deployed, run the mpls ldp command to enable MPLS LDP globally and create a public network instance running LDP.

Prerequisites

MPLS has been enabled globally using the mpls (system view) command.

Follow-up Procedure

You can perform other LDP configurations.

Precautions

Running the undo mpls ldp command in the system view deletes all MPLS LDP configurations in the system and interface views.

Example

# Enable LDP.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] quit
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] 
Related Topics

mpls ldp (interface view)

Function

The mpls ldp command enables MPLS LDP function on an interface.

The undo mpls ldp command disables MPLS LDP function on an interface.

By default, no interface is enabled with MPLS LDP function.

Format

mpls ldp

undo mpls ldp

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a network where MPLS LDP needs to be deployed, enable MPLS LDP function on an interface before configuring other LDP configurations.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

MPLS has been enabled on the interface using the mpls command in the interface view.

Follow-up Procedure

You can perform other MPLS LDP configurations.

Precautions

Running the undo mpls ldp command in the interface view deletes all MPLS LDP configurations on the interface.

Example

# Enable MPLS LDP function on VLANIF100.
<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] quit
[*HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls
[*HUAWEI-Vlanif100] mpls ldp
# Enable MPLS LDP function on 10GE1/0/1.
<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] quit
[*HUAWEI] interface 10ge 1/0/1
[*HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls
[*HUAWEI-10GE1/0/1] mpls ldp

mpls ldp remote-peer

Function

The mpls ldp remote-peer command creates a remote peer and displays the remote peer view.

The undo mpls ldp remote-peer command deletes a remote peer.

By default, no remote peer is created.

Format

mpls ldp remote-peer remote-peer-name

undo mpls ldp remote-peer remote-peer-name

Parameters

Parameter Description Value
remote-peer-name Specifies the name of a remote LDP peer. A string of 1 to 32 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A remote LDP session can be established between two indirectly connected LSRs or two directly connected LSRs.

Remote and local LDP sessions can both be configured and back up each other, ensuring connectivity of the LDP session.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp (system view) command.

Follow-up Procedure

An IP address can be assigned to the LDP remote peer.

Precautions

When configuring a remote LDP peer, run the mpls ldp remote-peer command on the local LDP and remote LDP peers.

Example

# Create a remote peer.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] quit
[*HUAWEI] mpls ldp remote-peer BJI
[*HUAWEI-mpls-ldp-remote-BJI]

mpls ldp timer hello-hold

Function

The mpls ldp timer hello-hold command sets the value of a Hello Hold timer.

The undo mpls ldp timer hello-hold command restores the default value.

By default, the link Hello Hold timer is 15 seconds and the target Hello Hold timer is 45 seconds.

Format

mpls ldp timer hello-hold interval

undo mpls ldp timer hello-hold

Parameters

Parameter Description Value
interval Specifies the value of a Hello Hold timer. The value is an integer ranging from 3 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view, remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Two LDP peers periodically exchange Hello messages to maintain the Hello adjacency. If no Hello message is received after the target Hello hold timer expires, the Hello adjacency is deleted.

The default value of the timer is recommended. On a network where the link status is unstable or a large number of packets are sent, increase the value of the timer to prevent the session flapping.

Hello hold timers are classified into the following types:
  • Link-Hello hold timer: maintains the local adjacency. The mpls ldp timer hello-hold command in the interface view sets a value of the timer.
  • Target-Hello hold timer: maintains the remote adjacency. The mpls ldp timer hello-hold command in the remote MPLS LDP peer view sets a value of the timer.

Prerequisites

The remote LDP peer has been configured or MPLS LDP has been enabled on the interface.

Precautions

The value of the timer that actually takes effect is the smaller one between the two Hello holder timers configured on both ends of an LDP session.

Example

# Set the value of the link Hello hold timer to 30 seconds.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls ldp
[*HUAWEI-Vlanif100] mpls ldp timer hello-hold 30
# Set the value of the link Hello hold timer to 30 seconds.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls ldp
[*HUAWEI-10GE1/0/1] mpls ldp timer hello-hold 30
# Set the value of the target Hello hold timer to 60 seconds.
<HUAWEI> system-view
[~HUAWEI] mpls ldp remote-peer bji
[*HUAWEI-mpls-ldp-remote-bji] mpls ldp timer hello-hold 60
Related Topics

mpls ldp timer hello-send

Function

The mpls ldp timer hello-send command sets the value of a Hello send timer.

The undo mpls ldp timer hello-send command restores the default setting.

By default, the value of a Hello send timer is one third the value of a Hello hold timer.

Format

mpls ldp timer hello-send interval

undo mpls ldp timer hello-send

Parameters

Parameter Description Value
interval Specifies the value of a Hello send timer. The value is an integer ranging from 1 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view, remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An LSR sends Hello messages to the neighboring LSR to advertise its presence on the network and sets up the Hello adjacency. The Hello messages are sent at an interval specified by the Hello send timer.

The default value of the Hello send timer is recommended. On a network with poor performance, you can reduce the value of the Hello send timer, enabling the network to recover from faults as soon as possible.

Hello send timers are classified into the following types:
  • Link-Hello send timer: maintains the local adjacency. The mpls ldp timer hello-send command in the interface view sets a value of the timer.
  • Target-Hello send timer: maintains the remote adjacency. The mpls ldp timer hello-send command in the remote MPLS LDP peer view sets a value of the timer.

Prerequisites

The remote LDP peer has been configured or MPLS LDP has been enabled on the interface.

Precautions

The value of the Hello send timer that takes effect is not necessarily the same as the set value. If the value of the Hello send timer is greater than one third of the value of the Hello hold timer, the value of the Hello send timer that takes effect is equal to one third of the value of the link-Hello hold timer. Run the mpls ldp timer hello-hold command to set the value for the Hello hold timer.

Example

# Set the value of the link Hello send timer to 10 seconds.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls ldp
[*HUAWEI-Vlanif100] mpls ldp timer hello-send 10
# Set the value of the link Hello send timer to 10 seconds.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls ldp
[*HUAWEI-10GE1/0/1] mpls ldp timer hello-send 10
# Set the value of the target Hello send timer to 20 seconds.
<HUAWEI> system-view
[~HUAWEI] mpls ldp remote-peer bji
[*HUAWEI-mpls-ldp-remote-bji] mpls ldp timer hello-send 20

mpls ldp timer igp-sync-delay

Function

The mpls ldp timer igp-sync-delay command sets the interval during which an LSP is being set up after an LDP session is created.

The undo mpls ldp timer igp-sync-delay command restores the default setting.

By default, the interval is 10 seconds.

Format

mpls ldp timer igp-sync-delay value

undo mpls ldp timer igp-sync-delay

Parameters

Parameter Description Value
value Specifies the interval, during which an LSP is being set up after an LDP session is created. The value is an integer ranging from 0 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

When an LDP session is reestablished on a faulty link, LDP starts the igp-sync-delay timer to wait for the establishment of an LSP.

After the igp-sync-delay timer times out, LDP notifies the IGP that synchronization is complete.

Example

# After the LDP session is established on VLANIF100, the interval is set to 15 seconds, during which the LSP is being set up.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls ldp
[*HUAWEI-Vlanif100] mpls ldp timer igp-sync-delay 15
# After the LDP session is established on 10GE1/0/1, the interval is set to 15 seconds, during which the LSP is being set up.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls ldp
[*HUAWEI-10GE1/0/1] mpls ldp timer igp-sync-delay 15

mpls ldp timer keepalive-hold

Function

The mpls ldp timer keepalive-hold command sets the value of a Keepalive hold timer.

The undo mpls ldp timer keepalive-hold command restores the default setting.

By default, the value of the Keepalive-hold timers of both local and remote sessions is 45 seconds.

Format

mpls ldp timer keepalive-hold interval

undo mpls ldp timer keepalive-hold

Parameters

Parameter Description Value
interval Specifies the timeout period of a Keepalive hold timer. The value is an integer ranging from 30 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view, remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

LDP peers exchange LDP PDUs over session connections to maintain LDP sessions. If a node does not receive any LDP PDU after the Keepalive hold timer expires, the node closes the connection to terminate the session.

The default value of the Keepalive hold timer is recommended. On a network with unstable links, increase the value of a Keepalive hold timer, preventing the session flapping.

Keepalive hold timers are classified into the following types:
  • Keepalive hold timer of the local session: maintains the local LDP session. The mpls ldp timer keepalive-hold command in the interface view sets a value of the timer.
  • Keepalive hold timer of the remote session: maintains the remote LDP session. The mpls ldp timer keepalive-hold command in the remote MPLS LDP peer view sets a value of the timer.

Prerequisites

The remote LDP peer has been configured or MPLS LDP has been enabled on the interface.

Configuration Impact

After the mpls ldp timer keepalive-hold command is run, the Keepalive hold timer value that takes effect is the smaller one of the Keepalive hold timer values configured on both ends of an LDP session.

Precautions

The same Keepalive Hold timer value must be set on each node between an LDP session established over more than one link. A Keepalive Hold time value inconsistency results in the unstable LDP sessions.

The Keepalive Hold timer of 9s takes effect even if two ends of an LDP session reach an agreement on a value less than 9s through negotiation.

The same Keepalive Hold timer value must be set on both ends of an LDP session established over multiple links or a local and remote coexistent LDP session. A Keepalive Hold time value inconsistency results in failures to establish LDP sessions.

Changing the value of the Keepalive hold timer causes the reestablishment of corresponding LDP sessions.

Example

# Set the value of the Keepalive hold timer for a local session to 60 seconds.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls ldp
[*HUAWEI-Vlanif100] mpls ldp timer keepalive-hold 60
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
# Set the value of the Keepalive hold timer for a local session to 60 seconds.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls ldp
[*HUAWEI-10GE1/0/1] mpls ldp timer keepalive-hold 60
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
# Set the value of the Keepalive hold timer for a remote session to 50 seconds.
<HUAWEI> system-view
[~HUAWEI] mpls ldp remote-peer bji
[*HUAWEI-mpls-ldp-remote-bji] mpls ldp timer keepalive-hold 50
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
Related Topics

mpls ldp timer keepalive-send

Function

The mpls ldp timer keepalive-send command sets the value of a Keepalive send timer.

The undo mpls ldp timer keepalive-send command restores the default setting.

By default, the value of a Keepalive send timer is one third the value of a Keepalive hold timer.

Format

mpls ldp timer keepalive-send interval

undo mpls ldp timer keepalive-send

Parameters

Parameter Description Value
interval Specifies the timeout period of a Keepalive send timer. The value is an integer ranging from 1 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view, remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After an LDP session is set up, LSRs on the two ends of the session periodically exchange Keepalive messages to maintain the LDP session.

The default value of the Keepalive send timer is recommended. On a network with poor performance, reduce the value of the Keepalive send timer, enabling the network to recover as soon as possible.

Keepalive send timers are classified into the following types:
  • Keepalive send timer of the local LDP session: controls the interval at which Keepalive messages are sent to the peer end of the local session. The mpls ldp timer keepalive-send command in the interface view sets a value of this timer.
  • Keepalive send timer of the remote LDP session: controls the interval at which Keepalive messages are sent to the peer end of the remote session. The mpls ldp timer keepalive-send command in the remote MPLS LDP peer view sets a value of the timer.

Prerequisites

The remote LDP peer has been configured or MPLS LDP has been enabled on the interface.

Precautions

The value of the Keepalive send timer that actually takes effect may be different from the configured one. If the value of the Keepalive send timer is greater than one third of the value of the Keepalive hold timer, the value of the Keepalive send timer that actually takes effect is equal to one third of the value of the Keepalive hold timer.

Example

# Set the value of the Keepalive send timer for setting up a local LDP session to 10 seconds.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls ldp
[*HUAWEI-Vlanif100] mpls ldp timer keepalive-send 10
# Set the value of the Keepalive send timer for setting up a local LDP session to 10 seconds.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls ldp
[*HUAWEI-10GE1/0/1] mpls ldp timer keepalive-send 10
# Set the value of the Keepalive send timer for setting up a remote LDP session to 20 seconds.
<HUAWEI> system-view
[~HUAWEI] mpls ldp remote-peer bji
[*HUAWEI-mpls-ldp-remote-bji] mpls ldp timer keepalive-send 20

mpls ldp transport-address

Function

The mpls ldp transport-address command configures an LDP transport address.

The undo mpls ldp transport-address command restores the default setting.

By default, the transport address for a node on a public network is the LSR ID of the node, and the transport address for a node on a private network is the primary IP address of an interface on the node.

Format

mpls ldp transport-address { interface-type interface-number | interface }

undo mpls ldp transport-address

Parameters

Parameter Description Value
interface-type interface-number Specifies the type and number of an interface. LDP uses the address of the interface as the TCP transport address. -
interface Indicates that LDP uses the IP address of the current interface as the TCP transport address. -

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Before two LSRs establish an LDP session, the two LSRs need to establish a TCP connection to exchange label messages. Run the mpls ldp transport-address command to set the address (the LDP transport address) for the TCP connection.

The transport address is used to establish a TCP connection between the local node and its peer. The peer must have a reachable route to this transport address. The default transport address is the loopback interface address (an LSR ID). When the address of the loopback interface is a public network address, configure different transport addresses for LSRs so that LSRs can set up connections with private network addresses.

You can run the mpls ldp transport-address command in the interface view to set the transport address for a TCP connection. When more than one link exists between two LSRs, and the links are bound to VPN instances, the default transport address is the IP address of an interface rather than the LSR ID of an LSR.

NOTE:
  • If LDP sessions are to be established over multiple links connecting two LSRs, LDP-enabled interfaces of either LSR must use the default transport address or the same transport address. If interfaces on either of the LSRs are assigned different transport addresses, a single transport address can be used and a single LDP session can be established.

  • When the LDP transport address changes, the session is not interrupted immediately. The session is interrupted after the Hello hold timer times out.

Prerequisites

MPLS LDP has been enabled on the interface using the mpls ldp (interface view) command.

Precautions

Changing an LDP transport address interrupts an LDP session. Exercise caution when running the mpls ldp transport-address command.

Example

# Set the transport address for link Hello messages to the current interface address.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls ldp
[*HUAWEI-Vlanif100] mpls ldp transport-address interface
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y
# Set the transport address for link Hello messages to the current interface address.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls ldp
[*HUAWEI-10GE1/0/1] mpls ldp transport-address interface
Warning: All the related sessions will be deleted if the operation is performed! Continue? [Y/N]:y

mpls ldp-lsp-number threshold-alarm

Function

The mpls ldp-lsp-number threshold-alarm command configures the alarm threshold for LDP LSP usage.

The undo mpls ldp-lsp-number threshold-alarm command restores the default settings.

By default, the upper limit of the alarm threshold for LDP LSP usage is 80%, the lower limit of the clear alarm threshold for LDP LSP usage is 75%.

Format

mpls ldp-lsp-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls ldp-lsp-number threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value Specifies the upper limit of the alarm threshold for LDP LSP usage. The value is an integer ranging from 1 to 100, represented in percentage. Using a value larger than 95 is not recommended. Using the default value 80 is recommended.
lower-limit lower-limit-value Specifies the lower limit of the clear alarm threshold for LDP LSP usage. The value is an integer ranging from 1 to 100, represented in percentage. The value must be smaller than the value of upper-limit-value. Using the default value 75 is recommended.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the number of LDP LSPs in the system reaches a specific limit, establishing additional LDP LSPs may fail because of insufficient resources. To facilitate user operation and maintenance, enable an alarm to be generated when the number of LDP LSPs reaches the specific limit. To configure the alarm threshold for LDP LSP usage, run the mpls ldp-lsp-number threshold-alarm command. The parameters in this command are described as follows:

  • upper-limit-value: upper alarm threshold. If the proportion of LDP LSP usage to all supported ones reaches the upper alarm threshold, an alarm can be generated.
  • lower-limit-value: lower alarm threshold. If the proportion of LDP LSP usage to all supported ones falls below the lower alarm threshold, a clear alarm can be generated.

Precautions

  • If the mpls ldp-lsp-number threshold-alarm command is run several times, the latest configuration overrides the previous one.

  • This command configures the alarm threshold for LDP LSP usage. The alarm that the number of LSPs exceeded the upper threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceed is configured, and the actual LDP LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of LSPs fell below the upper threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceedclear is configured, and the actual LDP LSP usage fells to the lower limit of the clear alarm threshold.

Example

# Configure the upper limit and the lower limit of the alarm threshold for LDP LSP usage.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls ldp-lsp-number threshold-alarm upper-limit 90 lower-limit 60

mpls lsr-id

Function

The mpls lsr-id command sets an LSR ID.

The undo mpls lsr-id command deletes an LSR ID.

By default, no LSR ID is set.

Format

mpls lsr-id lsr-id

undo mpls lsr-id

Parameters

Parameter Description Value
lsr-id Specifies the LSR ID of a device, which identifies the LSR. The value is in dotted decimal notation.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An LSR ID identifies an LSR on a network. On a network where MPLS services are deployed, you must configure the LSR IDs for devices.

An LSR does not have the default LSR ID, and you must configure an LSR ID for it. To enhance network reliability, you are advised to use the IP address of a loopback interface on the LSR as the LSR ID.

Follow-up Procedure

You can configure MPLS and associated services.

Precautions

  • If the LSR ID to be configured exists, the original LSR ID is deleted and the new IP address is configured as the LSR ID.

  • The undo mpls lsr-id command deletes existing LDP sessions and LSPs over the sessions. Execute caution when running this command.

  • If the LSR ID is configured and the LSR ID is the same as the primary IP address of a loopback interface, note that:
    • The loopback interface cannot be bound to a vpn instance.
    • The loopback interface cannot be deleted.
    • The primary IP address of the loopback interface cannot be deleted or modified.

Example

# Set the LSR ID to 1.1.1.1.

<HUAWEI> system-view
[~HUAWEI] mpls lsr-id 1.1.1.1
Related Topics

mpls mtu

Function

The mpls mtu command configures the MTU of MPLS packets on an interface.

The undo mpls mtu command restores the default setting.

By default, the MTU of MPLS packets is equal to the interface MTU.

Format

mpls mtu mtu

undo mpls mtu

Parameters

Parameter Description Value
mtu

Specifies the MPLS MTU of an interface.

The value range varies according to the interface type.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An MTU value determines the maximum number of bytes that can be sent each time. If the size of packets exceeds the MTU supported by a transit node or a receiver, the transit node or receiver fragments the packets or even discards them, increasing the network transmission load. MTU values must be correctly negotiated between LSRs to enable packets to successfully reach the receiver.

To calculate the MPLS MTU, an LSR on the path to a specified FEC compares all MTUs advertised by downstream devices with the interface MTU of its own, and adds the smaller MTU (the MPLS MTU) to the MTU TLV field in the Label Mapping message, and send the Label Mapping message upstream.

If an MTU value changes (for example when the local outbound interface or its configuration changes), an LSR recalculates the MTU value and sends a Label Mapping message carrying the new MTU value to all upstream devices.

The relationships between the MPLS MTU and the interface MTU are as follows:
  • If no MPLS MTU is configured on an interface, the interface MTU is used to control forwarding of MPLS packets.

  • If both an MPLS MTU and an interface MTU are configured on an interface, the smaller value between the two MTUs is used to control forwarding of MPLS packets.

Prerequisites

MPLS has been enabled on the interface using the mpls (interface view) command.

Precautions

After the mpls mtu command is run, LDP compares the MPLS MTU and the interface MTU, and uses the smaller value between the two MTUs.

Example

# Set the MPLS MTU to 1500 bytes on VLANIF100.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] mpls
[*HUAWEI-Vlanif100] mpls mtu 1500
# Set the MPLS MTU to 1500 bytes on 10GE1/0/1.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] mpls
[*HUAWEI-10GE1/0/1] mpls mtu 1500

mpls outsegment-number threshold-alarm

Function

The mpls outsegment-number threshold-alarm command configures the alarm threshold for LDP OutSegment number.

The undo mpls outsegment-number threshold-alarm command restores the default settings.

By default, the upper limit of the alarm threshold for LDP OutSegment number is 80%, the lower limit of the clear alarm threshold for LDP OutSegment number is 75%.

Format

mpls outsegment-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls outsegment-number threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value Specifies the upper limit of the alarm threshold for LDP OutSegment number. The value is an integer ranging from 1 to 100, represented in percentage. Using a value larger than 95 is not recommended. Using the default value 80 is recommended.
lower-limit lower-limit-value Specifies the lower limit of the clear alarm threshold for LDP OutSegment number. The value is an integer ranging from 1 to 100, represented in percentage. The value must be smaller than the value of upper-limit-value. Using the default value 75 is recommended.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the number of LDP OutSegments in the system reaches a specific limit, establishing additional LDP LSPs may fail because of insufficient resources. To facilitate user operation and maintenance, enable an alarm to be generated when the number of LDP OutSegments reaches the specific limit. To configure the alarm threshold for LDP OutSegment number, run the mpls outsegment-number threshold-alarm command. The parameters in this command are described as follows:

  • upper-limit-value specifies the upper limit of the alarm threshold for LDP OutSegment number. An alarm is generated when the number of LDP OutSegments reaches the upper limit.
  • lower-limit-value specifies the lower limit of the clear alarm threshold for LDP OutSegment number. A clear alarm is generated when the number of LDP OutSegments falls below the lower limit.

Precautions

  • If the mpls outsegment-number threshold-alarm command is run more than once, the latest configuration overrides the previous one.

  • This command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcethresholdexceed | hwmplsresourcethresholdexceedclear } command is run to enable the device to generate an MPLS resource insufficiency alarm and its clear alarm.

Example

# Configure the upper limit and the lower limit of the alarm threshold for LDP OutSegment number.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls outsegment-number threshold-alarm upper-limit 90 lower-limit 60

mtu-signalling apply-tlv

Function

The mtu-signalling apply-tlv command configures Label Mapping messages to carry an MTU TLV as defined in RFC 3988.

The undo mtu-signalling apply-tlv command configures Label Mapping messages to carry a Huawei private MTU TLV.

By default, the switch sends Label Mapping messages carrying the Huawei private MTU TLV.

Format

mtu-signalling apply-tlv

undo mtu-signalling apply-tlv

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An MPLS MTU value determines the maximum size of a Label Mapping message exchanged between two devices on a network. Before packet transmission, devices calculate the MPLS MTU value to prevent packet fragmentation during the transmission, relieving the load on the network. The MPLS MTU value advertised between devices is carried in the MTU TLV field of the Label Mapping message.

After the mpls ldp command is run, an MPLS LDP-enabled LSR by default sends a Huawei proprietary MTU TLV different from the MTU TLV defined in RFC3988.
  • The default MTU setting is recommended.
  • To ensure the communication with non-Huawei devices, run the mtu-signalling apply-tlv command to enable LSRs to send Label Mapping messages carrying the MTU TLV defined in RFC3988.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

  • The MPLS MTU is a parameter to be negotiated during the LDP LSP establishment. If a Huawei device is connected to a non-Huawei device, run the mtu-signalling apply-tlv command; otherwise, the user-defined MPLS MTU does not take effect.

  • The mtu-signalling command must be run before the mpls ldp command is run; otherwise, the number of network packets increases abruptly.

Example

# Enable LDP to send Label Mapping messages carrying the MTU TLV, as defined in RFC3988.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] mtu-signalling apply-tlv
Related Topics

mtu-signalling disable

Function

mtu-signalling disable command disables Label Mapping messages from carrying an MTU TLV.

undo mtu-signalling disablecommand enables Label Mapping messages from carrying an MTU TLV.

By default, the switch enables Label Mapping messages from carrying an MTU TLV.

Format

mtu-signalling disable

undo mtu-signalling disable

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

If the neighbor device cannot process MTU TLVs carried in received packets, run the mtu-signalling disable command to disable Label Mapping messages to carry MTU TLVs when being sent.

Example

# Disables Label Mapping messages from carrying an MTU TLV.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] mtu-signalling disable
Related Topics

no-renegotiate session-parameter-change graceful-restart

Function

The no-renegotiate session-parameter-change graceful-restart command disables a device from re-establishing existing LDP sessions when LDP GR is enabled or disabled, or the LDP GR timer value is changed.

The undo no-renegotiate session-parameter-change graceful-restart command restores the default configuration.

By default, a device re-establishes LDP sessions when LDP GR is enabled or disabled, or the LDP GR timer value is changed.

Format

no-renegotiate session-parameter-change graceful-restart

undo no-renegotiate session-parameter-change graceful-restart

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

To disable a device from re-establishing existing LDP sessions when LDP GR status or a GR parameter is changed, run the no-renegotiate session-parameter-change graceful-restart command.

After the no-renegotiate session-parameter-change graceful-restart command is run, running the following commands does not affect the existing LDP sessions.

Example

# Disable a device from re-establishing existing LDP sessions when LDP GR status or a GR parameter is changed.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[~HUAWEI-mpls-ldp] no-renegotiate session-parameter-change graceful-restart

ospf ldp-sync

Function

The ospf ldp-sync command enables synchronization between LDP and OSPF on an interface.

The undo ospf ldp-sync command disables synchronization between LDP and OSPF on an interface.

By default, synchronization between LDP and OSPF is disabled on an interface.

Format

ospf ldp-sync

undo ospf ldp-sync

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

The LDP convergence speed depends on the convergence speed of OSPF routes. To enable MPLS LDP on a network with the primary and backup links, the following problems may occur:
  • Upon a fault on the active link, OSPF routes and ISP are switched to the backup link using LDP FRR. When the primary link recovers, OSPF routes are switched back to the primary link earlier than LDP traffic because IGP route convergence is faster than LDP convergence. As a result, LSP traffic is lost.
  • If a fault occurs on the LDP session between nodes on the primary link where the OSPF routes are working properly, the OSPF routes still use the primary link and the LSP on the primary link is deleted. No OSPF route exists on the backup link; therefore, no LSP can be established on the backup link. LSP traffic is lost.

Run the ospf ldp-sync command to enable synchronization between LDP and OSPF to prevent traffic loss in the preceding problems. Run this command on the interfaces on both ends of the link between the node where the primary LSP and the backup LSP diverge from each other and its LDP peer on the primary LSP.

Example

# Enable synchronization between LDP and OSPF on VLANIF100.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] ospf ldp-sync
# Enable synchronization between LDP and OSPF on 10GE1/0/1.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] ospf ldp-sync

ospf ldp-sync block

Function

The ospf ldp-sync block command blocks synchronization between LDP and OSPF on an interface.

The undo ospf ldp-sync block command restores the default setting.

By default, synchronization between LDP and OSPF is not blocked on an interface.

Format

ospf ldp-sync block

undo ospf ldp-sync block

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

The ldp-sync enable command run in the OSPF area view to enable LDP and OSPF synchronization on the following interfaces:
  • Interfaces with OSPF neighbors in the Up state on a P2P network
  • DRs' and non-DR/BDR devices' interfaces with OSPF neighbors in the Up state on a broadcast network
If LDP and OSPF synchronization is enabled on an interface that transmits important services, ensure that the interface is not on a standby link. Synchronization between LDP and OSPF can be disabled on a specified interface of the switch.

You can block synchronization between LDP and OSPF on a specified interface of the switch.

Example

# Enable synchronization between LDP and OSPF on VLANIF100.

<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] ospf ldp-sync block

# Enable synchronization between LDP and OSPF on 10GE1/0/1.

<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] ospf ldp-sync block

ospf mpls ldp auto-config disable

Function

The ospf mpls ldp auto-config disable command disables OSPF interfaces to be automatically enabled with the MPLS LDP function.

The undo ospf mpls ldp auto-config disable command restores the default configuration of the MPLS LDP function on OSPF interfaces.

By default, if the mpls ldp auto-config command is run in an OSPF process, all interfaces that can establish OSPF neighbors are automatically enabled with the MPLS LDP function. Otherwise, the function is disabled.

Format

ospf mpls ldp auto-config disable

undo ospf mpls ldp auto-config disable

Parameters

None

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After the mpls ldp auto-config command is run, all interfaces that can establish OSPF neighbors in an OSPF process are automatically enabled with the MPLS LDP function. To disable the MPLS LDP function on some interfaces, run the ospf mpls ldp auto-config disable command in the interface view.

Precautions

If the mpls ldp auto-config command is not run in the OSPF view, the ospf mpls ldp auto-config disable command can be run normally, but does not take effect on interfaces.

If you run the ospf mpls ldp auto-config disable command and then run the mpls ldp auto-config command, the ospf mpls ldp auto-config disable command takes effect on interfaces.

Example

# Disable VLANIF10 to be automatically enabled with the MPLS LDP function.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 10
[*HUAWEI-Vlanif10] ospf mpls ldp auto-config disable
# Disable 10GE1/0/1 to be automatically enabled with the MPLS LDP function.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] ospf mpls ldp auto-config disable

ospf timer ldp-sync hold-down

Function

The ospf timer ldp-sync hold-down command sets the interval during which an interface waits for creating an LDP session before setting up the OSPF neighbor relationship.

The undo ospf timer ldp-sync hold-down command restores the default setting.

By default, the interval during which an interface waits for creating an LDP session before setting up the OSPF neighbor relationship is 10 seconds.

Format

ospf timer ldp-sync hold-down value

undo ospf timer ldp-sync hold-down

Parameters

Parameter Description Value
value Specifies the interval during which an interface waits for creating an LDP session before setting up the OSPF neighbor relationship. The value is an integer ranging from 0 to 65535, in seconds.

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After this command is configured, OSPF routes are not immediately switched to the primary link after the primary link is restored and before the LDP session is established. LSP traffic is transmitted through the backup link in a period of time specified by this command.

Prerequisites

LDP and OSPF synchronization has been enabled using the ospf ldp-sync command in the interface view.

Precautions

This command is circular in nature, and the latest configuration overrides the previous configurations.

Example

# Set the value of the Hold-down timer for VLANIF100 to 15 seconds, during which the interface waits for the establishment of an LDP session before setting up the OSPF neighbor relationship.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] ospf timer ldp-sync hold-down 15

ospf timer ldp-sync hold-max-cost

Function

The ospf timer ldp-sync hold-max-cost command sets the interval at which OSPF LSAs are sent to advertise the maximum metric on the local device.

The undo ospf timer ldp-sync hold-max-cost command restores the default setting.

By default, the local device running OSPF keeps advertising the maximum cost by sending LSAs.

Format

ospf timer ldp-sync hold-max-cost { value | infinite }

undo ospf timer ldp-sync hold-max-cost

Parameters

Parameter Description Value
value Specifies the interval for sending OSPF LSAs to advertise the maximum metric on the local device. The value is an integer ranging from 0 to 65535, in seconds.
infinite Indicates that OSPF always advertises the maximum metric in LSAs on the local device before an LDP session is reestablished. -

Views

GE interface view, 10GE interface view, 25GE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, Layer 3 sub-interface view, VLANIF interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When the primary LSP recovers from a fault, run the ospf timer ldp-sync hold-max-cost command to set the interval during which traffic is still transmitted along the backup LSP before the LDP session of the primary LSP is reestablished.

You can choose different parameters as required.
  • When OSPF carries only LDP services, to ensure that OSPF routing is always consistent with the LDP LSP, specify infinite.
  • When OSPF carries multiple services including LDP services, to ensure that OSPF route selection and other services still run properly in case the LDP session of the primary LSP fails, specify value.

Prerequisites

LDP and OSPF synchronization has been enabled using the ospf ldp-sync command in the interface view.

Precautions

This command is circular in nature, and the latest configuration overrides the previous configurations.

Example

# Set the interval at which OSPF LSAs are sent to advertise the maximum metric on the local device to 8 seconds.
<HUAWEI> system-view
[~HUAWEI] interface vlanif 100
[*HUAWEI-Vlanif100] ospf ldp-sync
[*HUAWEI-Vlanif100] ospf timer ldp-sync hold-max-cost 8
# Set the interval at which OSPF LSAs are sent to advertise the maximum metric on the local device to 8 seconds.
<HUAWEI> system-view
[~HUAWEI] interface 10ge 1/0/1
[~HUAWEI-10GE1/0/1] undo portswitch
[*HUAWEI-10GE1/0/1] ospf ldp-sync
[*HUAWEI-10GE1/0/1] ospf timer ldp-sync hold-max-cost 8

outbound peer bgp-label-route

Function

The outbound peer bgp-label-route command configures an outbound policy to send Label Mapping messages to a specified peer based on the specified BGP labeled route.

The undo outbound peer bgp-label-route command restores the default configuration.

By default, no outbound policy is configured.

Format

outbound peer { peer-id | peer-group peer-group-name | all } bgp-label-route { none | ip-prefix prefix-name }

undo outbound peer { peer-id | peer-group peer-group-name | all } bgp-label-route

Parameters

Parameter Description Value
peer-id Specifies the ID of an LDP peer. By default, the peer ID is specified by the mpls lsr-id command. If the lsr-id command has been configured, the peer ID is specified by the lsr-id command. The value is in dotted decimal notation.
peer-group peer-group-name Specifies the name of a peer group. The parameter is specified by the ip ip-prefix command. The value is an existing peer group name.
all Indicates all LDP peers. -
none Forbids Label Mapping messages for all FECs. After the parameter none is configured, the LSR does not send Label Mapping messages for labeled BGP routes to the specified peer. -
ip-prefix prefix-name Allows only Label Mapping messages for labeled BGP routes that are defined in the IP prefix list. After the parameter ip-prefix is configured on an LSR, the LSR sends only Label Mapping messages for labeled BGP routes that are defined in the IP prefix list to a specified peer. The parameter is specified by the ip ip-prefix command. The value is an existing IP prefix list name.

Views

MPLS-LDP-IPv4 view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An LSR sends Label Mapping messages to both upstream and downstream LDP peers by default, speeding up LDP LSP convergence. This leads to the establishment of a great number of unwanted LSPs, wasting resources. To reduce the number of LSPs and save memory resources, configure an outbound or inbound policy to filter out LDP LSPs not matching the policy.

To trigger the egress LSP using the BGP labeled route, run the outbound peer bgp-label-route command. You can specify the peer ID and FEC of the BGP labeled route in the command to configure the peer to receive only Label Mapping messages with specified BGP labeled routes, limiting the number of Label Mapping messages to be sent.

To apply a policy associated with a single FEC range to an LDP peer group or all LDP peers that send Label Mapping messages, configure either the peer-group peer-group-name or all parameter in the command.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

If multiple outbound policies are configured for a specified LDP peer, the first configured one takes effect. For example, the following two outbound policies are configured:
outbound peer 2.2.2.2 bgp-label-route ip-prefix prefix1
outbound peer peer-group group1 bgp-label-route none
As group1 also contains an LDP peer with peer-id of 2.2.2.2, the following outbound policy takes effect:
outbound peer 2.2.2.2 bgp-label-route ip-prefix prefix1
If two outbound policies are configured in sequence and the peer peer-id parameters in the two commands are the same, the second command overrides the first one. For example, the following two outbound policies are configured:
outbound peer 2.2.2.2 bgp-label-route ip-prefix prefix1
outbound peer 2.2.2.2 bgp-label-route none
The second configuration overrides the first one. This means that the following outbound policy takes effect on the LDP peer with peer-id of 2.2.2.2:
outbound peer 2.2.2.2 bgp-label-route none

Example

# Configure an LSR to send Label Mapping messages for labeled BGP routes defined in IP prefix list named prefix1 to all peers.

<HUAWEI> system-view
[~HUAWEI] ip ip-prefix prefix1 permit 2.2.2.2 24
[*HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] ipv4-family
[*HUAWEI-mpls-ldp-ipv4] outbound peer all bgp-label-route ip-prefix prefix1

outbound peer fec

Function

The outbound peer fec command configures an outbound policy to send Label Mapping messages to a specified peer based on the specified IGP route.

The undo outbound peer fec command restores the default configuration.

By default, no outbound policy is configured to allow label mapping messages carrying a specified IGP route to be sent to a specified peer.

Format

outbound peer { peer-id | peer-group peer-group-name | all } fec { none | host | ip-prefix prefix-name }

undo outbound peer { peer-id | peer-group peer-group-name | all } fec

Parameters

Parameter Description Value
peer-id Specifies the ID of an LDP peer. By default, the peer ID is specified by the mpls lsr-id command. If the lsr-id command has been configured, the peer ID is specified by the lsr-id command. The value is in dotted decimal notation.
peer-group peer-group-name Specifies the name of a peer group. The name is a string of 1 to 169 characters without spaces. It is case-sensitive. The peer-group-name must already exist.
all Indicates all LDP peers. -
none Prohibits Label Mapping messages carrying routes mapped to all FECs from passing the policy. After the parameter none is configured, no Label Mapping messages carrying IGP routes mapped to all FECs are sent to a specified peer. -
host Allows Label Mapping messages carrying the host routes mapped to FECs to pass the policy. After the parameter host is configured, Label Mapping messages carrying host routes mapped to all FECs are sent to a specified peer. -
ip-prefix prefix-name Allows Label Mapping messages carrying IGP routes that are defined in the IP prefix list and mapped to FECs to pass the policy. After the parameter ip-prefix is configured, Label Mapping messages carrying IGP routes that are defined in the IP prefix list and mapped to FECs are sent to a specified peer. The parameter is specified by the ip ip-prefix command. The name is a string of 1 to 169 characters without spaces. It is case-sensitive. The prefix-name must already exist.

Views

MPLS-LDP-IPv4 view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An LSR sends label mapping messages to both upstream and downstream LDP peers by default, speeding up LDP LSP convergence. This leads to the establishment of a great number of unwanted LSPs, wasting resources. To reduce the number of LSPs and save memory resources, configure an outbound or inbound policy to filter out LDP LSPs not matching the policy.

When running the outbound peer fec command to specify the peer ID and FEC of the IGP route, configure the peer to receive only label mapping messages for specified IGP routes. This setting helps reduce the number of Label Mapping messages to be sent.

To apply a policy associated with a single FEC range to an LDP peer group or all LDP peers that send Label Mapping messages, configure either the peer-group peer-group-name or all parameter in the command.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

If multiple outbound policies are configured for a specified LDP peer, the first configured one takes effect. For example, the following two outbound policies are configured:
outbound peer 2.2.2.2 fec host
outbound peer peer-group group1 fec none
As group1 also contains an LDP peer with peer-id of 2.2.2.2, the following outbound policy takes effect:
outbound peer 2.2.2.2 fec host
If two outbound policies are configured in sequence and the peer parameters in the two commands are the same, the second command overrides the first one. For example, the following two outbound policies are configured:
outbound peer 2.2.2.2 fec host
outbound peer 2.2.2.2 fec none
The second configuration overrides the first one. This means that the following outbound policy takes effect on the LDP peer with peer-id of 2.2.2.2:
outbound peer 2.2.2.2 fec none
NOTE:

To delete all outbound policies in batches, run the undo outbound peer all fec command.

Example

# Configure an LSR to send Label Mapping messages carrying host routes to all peers.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] ipv4-family
[*HUAWEI-mpls-ldp-ipv4] outbound peer all fec host

outbound peer split-horizon disable

Function

outbound peer split-horizon disable command disables LDP split horizon.

undo outbound peer split-horizon disable command restores the default configuration.

By default, LDP split horizon is enabled for all LDP peers so that LSRs allocate labels only to upstream LDP peers.

Format

outbound peer { peer-id | all } split-horizon disable

undo outbound peer { peer-id | all } split-horizon disable

Parameters

Parameter Description Value
peer-id Specifies the LSR ID of an LDP peer. The value is in dotted decimal notation.
all Indicates all LDP peers. -

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

An LSR usually distributes labels to both upstream and downstream LDP peers, speeding up LDP LSP convergence. On DSLAMs of low performance deployed on an MPLS network, LDP distributes labels to all LDP peers leads to the establishment of a large number of LSPs, which exposes a heavy burden on the DSLAMs. To help reduce the number of LSPs and save memory,by default, LDP split horizon is enabled for all LDP peers so that LSRs allocate labels only to upstream LDP peers. You can disable LDP split horizon to speed up LDP LSP convergence as needed.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Example

# Disable split horizon for all LDP peers.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] outbound peer all split-horizon disable

path-vectors

Function

The path-vectors command sets the maximum number of hops of the path vector that is used for LDP loop detection.

The undo path-vectors command restores the default setting.

By default, a maximum of 32 hops of the path vector are used for LDP loop detection.

Format

path-vectors integer

undo path-vectors

Parameters

Parameter Description Value
integer Specifies the path vector. The value is an integer ranging from 1 to 32.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

A scenario assumes that LDP loop detection is configured using the path vector, and the maximum number of hops of the path vector is n. The egress LSP triggered by local routes detects loop after n + 1 hops, whereas the egress LSP triggered by non-local routes (proxy egress) detects loops after n hops.

Prerequisites

The path-vectors command has been configured before LDP is enabled on all interfaces. The path-vectors command takes effect only after MPLS LDP is enabled in the related view.

Example

# Set the maximum value of the path vector to 3.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] path-vectors 3

ping lsp

Function

The ping lsp command checks the LSP connectivity and LSP forwarding status.

Format

ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v | -g ] * ip destination-host mask-length [ ip-address ] [ nexthop nexthop-address ]

ping lsp [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m interval | -r reply-mode | -s packet-size | -t time-out | -v | -g ] * bgp destination-host mask-length [ ip-address ]

Parameters

Parameter Description Value
-a source-ip Specifies the source IP address of MPLS Echo Request packets to be sent.

If the source IP address is not specified, the IP address of the outbound interface from which MPLS Echo Request packets are sent is used as the source IP address.

-
-c count Specifies the number of MPLS Echo Request packets to be sent.

In the case of poor network quality, you can set this parameter to a comparatively large value to check the network quality based on the packet loss rate.

The value is an integer that ranges from 1 to 4294967295. The default value is 5.
-exp exp-value Specifies the EXP value of MPLS Echo Request packets to be sent.
NOTE:

If DSCP priority has been configured by running the set priority dscp command, the exp-value parameter does not take effect.

The value is an integer that ranges from 0 to 7. The default value is 0.
-h ttl-value Specifies the value of the TTL. Each time the ping lsp command is run, an MPLS Echo Request packet carrying a sequence number is sent. The sequence number of the MPLS Echo Request packet starts from 1 and is increased by 1. By default, a maximum of five MPLS Echo Request packets are sent. You can set the number of MPLS Echo Request packets to be sent through the parameter ttl-value. If the destination is reachable, the source can receive five MPLS Echo Reply packets from the destination, with sequence numbers corresponding to those of MPLS Echo Request packets. If the TTL field is decreased to 0 during packet forwarding, the switch that the packet reaches sends an MPLS timeout packet to the source, indicating that the destination is unreachable. The value is an integer that ranges from 1 to 255. The default value is 64.
-m interval Specifies the time to wait before sending the next MPLS Echo Request packet.

Each time the source sends an MPLS Echo Request packet using the ping lsp command, the source waits a period of time (2000 ms by default) before sending the next MPLS Echo Request packet. You can set the time to wait before sending the next ICMP Echo Request message using the parameter interval. In the case of poor network condition, the value should be equal to or larger than 2000, in milliseconds.

The value is an integer that ranges from 1 to 10000, in milliseconds. The default value is 2000.
-r reply-mode Specifies the mode in which the peer returns MPLS Echo Reply packets.
The value is an integer that ranges from 1 to 2. The default value is 2.
  • 1: indicates that the peer does not return MPLS Echo Reply packets.
  • 2: indicates that the peer returns MPLS Echo Reply packets with IPv4/IPv6 UDP packets.
-s packet-size Indicates the length of the payload in a packet, excluding the IP header and UDP header.

The value is an integer that ranges from 65 to 9600, in bytes. The default value is 100. The configured value must be smaller than the MTU of the interface.

-t time-out Indicates the timeout period to wait for an MPLS Echo Reply packet after an MPLS Echo Request packet is sent. The value is an integer that ranges from 0 to 65535, in milliseconds. The default value is 2000.
-v Displays MPLS Echo Reply packets not for the local user. By default, only MPLS Echo Reply packets for the local user are displayed.
  • If -v is not specified, the system displays only the MPLS Echo Reply packets received by the local user.
  • If -v is specified, the system displays all received MPLS Echo Reply packets.
By default, the system displays only the MPLS Echo Reply packets received by the local user.
-g Performs the NQA test using MPLS fragments. -
ip Tests an LDP LSP. -
bgp Tests a BGP LSP.
NOTE:

CE6870EI does not support this parameter.

-
destination-host Indicates the domain name or IPv4 address of the destination host of the LSP. The destination-host must already exist.
mask-length Specifies the mask length of the LSP's destination host. The value is an integer ranging from 0 to 32.
ip-address Specifies the destination IP address carried in the IP header of an MPLS Echo Request packet.

The value is in dotted decimal notation.

By default, the destination IP address carried in the IP header of an MPLS Echo Request packet is 127.0.0.1.

nexthop nexthop-address Specifies the IP address of the next hop.

The value is in dotted decimal notation.

Views

All views

Default Level

0: Visit level

Usage Guidelines

Usage Scenario

On an MPLS network, you can run the ping lsp command to check LSP connectivity after an LSP is established.

The LSP ping can be used to monitor the following types of links:
  • LDP LSP Ping: Run the ping lsp ip destination-host mask-length command on the ingress node to ping the egress node to monitor the connectivity of the LDP LSP.

  • BGP LSP Ping: Run the ping lsp bgp destination-host mask-length command on the ingress node to ping the egress node to monitor the connectivity of the BGP LSP.

If the ping lsp command detects a fault on an LSP that packets transmitted along this LSP cannot reach the egress node, you can run the tracert lsp command to locate the fault.

Prerequisites

Before running the ping lsp command, ensure that the MPLS module is working properly.

Precautions

To prevent the egress node from forwarding the received MPLS Echo Request packet to other nodes, the destination address in the IP header of the Echo Request packet is set to 127.0.0.1/8 (the local loopback address), and the TTL value contained in the IP header is set to 1.

Example

# Ping 4.4.4.9/32 which is the destination of an LDP LSP by sending ten 200-byte MPLS Echo Request packets.
<HUAWEI> ping lsp -c 10 -s 200 ip 4.4.4.9 32  
  LSP PING FEC: IPV4 PREFIX 4.4.4.9/32/ : 200 data bytes, press CTRL_C to break
    Reply from 4.4.4.9: bytes=200 Sequence=1 time = 11 ms
    Reply from 4.4.4.9: bytes=200 Sequence=2 time = 6 ms
    Reply from 4.4.4.9: bytes=200 Sequence=3 time = 6 ms
    Reply from 4.4.4.9: bytes=200 Sequence=4 time = 6 ms
    Reply from 4.4.4.9: bytes=200 Sequence=5 time = 12 ms
    Reply from 4.4.4.9: bytes=200 Sequence=6 time = 9 ms
    Reply from 4.4.4.9: bytes=200 Sequence=7 time = 12 ms
    Reply from 4.4.4.9: bytes=200 Sequence=8 time = 9 ms
    Reply from 4.4.4.9: bytes=200 Sequence=9 time = 12 ms
    Reply from 4.4.4.9: bytes=200 Sequence=10 time = 12 ms

  --- FEC: IPV4 PREFIX 4.4.4.9/32 ping statistics ---
    10 packet(s) transmitted
    10 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 6/10/12 ms
# Ping 3.3.3.3/32 which is the destination of an LDP LSP and output detailed information.
<HUAWEI> ping lsp -v ip 3.3.3.3 32 
  LSP PING FEC: IPV4 PREFIX 3.3.3.3/32 : 100 data bytes, press CTRL_C to break
    Reply from 3.3.3.3: bytes=100 Sequence=1 time = 4 ms Return Code 3, Subcode 1
    Reply from 3.3.3.3: bytes=100 Sequence=2 time = 4 ms Return Code 3, Subcode 1
    Reply from 3.3.3.3: bytes=100 Sequence=3 time = 4 ms Return Code 3, Subcode 1
    Reply from 3.3.3.3: bytes=100 Sequence=4 time = 4 ms Return Code 3, Subcode 1
    Reply from 3.3.3.3: bytes=100 Sequence=5 time = 5 ms Return Code 3, Subcode 1
  --- FEC: IPV4 PREFIX 3.3.3.3/32 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 4/4/5 ms   
# Ping 1.1.1.1/32 which is the destination of a BGP LSP by sending MPLS Echo Request packets with 4.4.4.4 as the source IP address.
<HUAWEI> ping lsp -a 4.4.4.4 bgp 1.1.1.1 32
  LSP PING FEC: BGP LABELED IPV4 PREFIX 1.1.1.1/32/ : 100  data bytes, press CTRL_C to break
    Reply from 1.1.1.1: bytes=100 Sequence=1 time=26 ms
    Reply from 1.1.1.1: bytes=100 Sequence=2 time=9 ms
    Reply from 1.1.1.1: bytes=100 Sequence=3 time=8 ms
    Reply from 1.1.1.1: bytes=100 Sequence=4 time=7 ms
    Reply from 1.1.1.1: bytes=100 Sequence=5 time=5 ms

  --- FEC: BGP LABELED IPV4 PREFIX 1.1.1.1/32 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 5/11/26 ms
 
Table 11-36  Description of the ping lsp command output

Item

Description

Reply from

IP address in an Echo Reply packet.

bytes

Length of an Echo Reply packet.

Sequence

Serial number of an Echo Reply packet.

time

RTT of an Echo Reply packet.

Return Code

Return code. The meaning of each value is as follows:
  • 0: No return code is received.

  • 1: Incorrect request is received.

  • 2: An unknown TLV is received.

  • 3: There is the outbound interface of one LSP.

  • 4: No mapping between the request device and the replying device exists.

  • 5: The mapping does not match that on the downstream device.

  • 6: An unknown upstream interface exists.

  • 7: The return code is reserved.

  • 8: indicates label switching.

  • 9: indicates label switching without MPLS forwarding.

  • 10: indicates mapping without labels.

  • 11: indicates the entity without labels.

  • 12: No protocol is loaded on the interface.

  • 13: The ping operation is ended ahead of schedule because of shortened labels.

Subcode

Number of labels. Usually, the value is 1.

xxx ping statistics

Statistics collected after the ping test. The statistics include the following information:
  • packet(s) transmitted: indicates the number of sent ICMP Echo Request messages.

  • packet(s) received: indicates the number of received ICMP Echo Reply messages.

  • % packet loss: indicates the percentage of unresponded messages to total sent messages.

  • round-trip min/avg/max: indicates the minimum, average, and maximum RTTs. The unit is ms.

Related Topics

propagate mapping

Function

The propagate mapping for ip-prefix command allows the system to filter out the received routes using an IP prefix list. LDP uses routes that match the addresses in the prefix list to establish an LSP.

The undo propagate mapping command restores the default setting.

By default, when LDP establishes an LSP, LDP does not filter out received routes.

Format

propagate mapping for ip-prefix ip-prefix-name

undo propagate mapping

Parameters

Parameter Description Value
ip-prefix ip-prefix-name Specifies the name of an IP prefix list used to filter out routes. The value is an existing IP prefix list name.

Views

MPLS-LDP view, MPLS-LDP-IPv4 view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After MPLS LDP is enabled, LDP LSPs are automatically established, leading to a large number of LSPs and wasting resources. Run the propagate mapping command to configure a policy for establishing an LSP, allowing LDP to use routes that match the specified conditions to establish LSPs.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp (system view) command.

Precautions

The propagate mapping command takes effect in either the MPLS LDP view or MPLS-LDP-IPv4 view. If the command is configured in both views, only the latest configuration takes effect.

Example

# Allow routes that match the IP prefix list named policy1 to set up an LSP.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] propagate mapping for ip-prefix policy1

proxy-egress disable

Function

The proxy-egress disable command disables a device from establishing proxy egress LSPs.

The undo proxy-egress disable command enables a device to establish proxy egress LSPs.

By default, a device is enabled to establish proxy egress LSPs.

Format

proxy-egress disable

undo proxy-egress disable

Parameters

None

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If a policy allows a device to use all static and IGP routes to establish LSPs or use an IP address prefix list to establish LSPs, the policy also triggers proxy egress LSP establishment. However, the proxy egress LSPs may be unavailable, which wastes system resources. To prevent this problem, run the proxy-egress disable command to disable a device from establishing such proxy egress LSPs.

Prerequisites

MPLS has been enabled using the mpls (system view) command.

Example

# Disable a device from establishing proxy egress LSPs in the MPLS view.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] proxy-egress disable
Related Topics

remote-ip

Function

The remote-ip command allows you to assign an IP address to a remote LDP peer.

The undo remote-ip command deletes the configuration.

The remote-ip pwe3 command prevents an LSR from distributing labels to a specified remote peer.

The remote-ip pwe3 disable command allows the device to assign labels for a specified remote peer.

By default, the IP address of the remote LDP peer is not configured.

Format

remote-ip ip-address

undo remote-ip

remote-ip ip-address pwe3

remote-ip pwe3 disable

Parameters

Parameter Description Value
ip-address Specifies the IPv4 address of a remote peer.

The value is in decimal notation.

Views

Remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After a remote LDP peer is configured, to assign an IP address to the remote LDP peer, run the remote-ip command in the remote MPLS LDP peer view.

The IP address must be the LSR ID of the remote LDP peer. When the LDP LSR ID and the MPLS LSR ID are different, the LDP LSR ID takes effect.

The remote peer uses the LSR ID as the transport address to create a TCP connection.

PEs on both ends of an MPLS L2VPN that runs LDP signaling can establish a remote LDP session. The MPLS L2VPN can be a Martini VPLS network. The remote LDP session is expected to transmit Label Mapping messages carrying VC labels, not LDP labels. By default, the PE distributes LDP labels to its peer. To disable the PE from distributing LDP labels to its peer, run either of the following commands, which helps prevent LDP label wastes and minimize memory usage.
  • remote-ip ip-address pwe3 command: prevents the LSR from distributing labels to a specified remote peer.

  • remote-peer pwe3 command: prevents the LSR from distributing labels to all remote peers.

Prerequisites

Remote LDP peers have been configured.

Precautions

  • Modifying or deleting the configured IP address of a remote peer leads to the deletion of a remote LDP session.

  • After a remote peer IP address is specified using the remote-ip ip-address command, ip-address cannot be used as a local interface IP address. If it is used as a local interface IP address, the remote LDP session is interrupted.

Example

# Configure the address for a remote peer.

<HUAWEI> system-view
[~HUAWEI] mpls ldp remote-peer bji
[*HUAWEI-mpls-ldp-remote-bji] remote-ip 10.3.3.3
# Prohibit labels from being distributed to the remote peer at 10.1.1.1/32.
<HUAWEI> system-view
[~HUAWEI] mpls ldp remote-peer rtc
[*HUAWEI-mpls-ldp-remote-rtc] remote-ip 10.1.1.1 pwe3

remote-peer pwe3

Function

The remote-peer pwe3 command prevents public network labels from being distributed to all remote peers.

The undo remote-peer pwe3 command restores the default setting.

By default, an LSR is permitted to distribute public network labels to all remote peers.

Format

remote-peer pwe3

undo remote-peer pwe3

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

PEs on both ends of an MPLS L2VPN that runs LDP signaling can establish a remote LDP session. The MPLS L2VPN can be a Martini VLL network. The remote LDP session is expected to transmit Label Mapping messages carrying VC labels, not LDP labels.

By default, the PE distributes LDP labels to its peer. To disable the PE from distributing LDP labels to its peer, run either of the following commands, which helps prevent LDP label wastes and minimize memory usage.

  • The remote-peer pwe3 command prohibits an LSR from distributing labels to all remote peers.

  • The remote-ip ip-address pwe3 command in the remote MPLS LDP peer view prohibits an LSR from distributing labels to a specified remote peer.

When you create a remote LDP session, run the remote-peer pwe3 or remote-ip ip-address pwe3 command to prevent public network labels from being distributed to remote peers. If you do not run either of the preceding commands, the command configuration may affect system performance.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

The configuration will take effect on all remote LDP peers, including existing remote peers.

Example

# Prevent public network labels from being distributed to all remote peers.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] remote-peer pwe3
Warning: The modification has impact on all remote peers including the existing ones! Continue? [Y/N]:y

reset lspv statistics

Function

The reset lspv statistics command clears LSPV statistics.

Format

reset lspv statistics

Parameters

None

Views

User view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The display lspv statistics command can be used to display LSPV statistics of an LSP ping or trace test instance. LSPV statistics of multiple test instances are accumulated, which obsesses the analysis. The reset lspv statistics command can be used to clear LSPV statistics.

If the reset lspv statistics command is run before an LSP ping or trace test instance starts, the display lspv statistics command displays LSPV statistics of the current test instance.

The reset lspv statistics command can be used to clear the following LSPV statistics:

  • Number of sent MPLS Echo Request packets
  • Total number of MPLS Echo Reply packets
  • Number of received MPLS Echo Reply packets

Precautions

Statistics cannot be restored after being cleared. Therefore, exercise caution before running the reset lspv statistics command.

Example

# Clear LSPV statistics collected on the device.

<HUAWEI> reset lspv statistics

reset mpls ldp

Function

The reset mpls ldp command resets LDP instances of the public network.

The reset mpls ldp graceful command restarts a public network LDP instance, without service interruption. (In this case, it is required that the device be enabled with GR and set up a GR-enabled LDP session with a neighbor.)

The reset mpls ldp all command resets all LDP instances.

Format

reset mpls ldp [ peer peer-id ] [ graceful ]

reset mpls ldp all

Parameters

Parameter Description Value
peer peer-id Specifies the LSR ID of a peer. Expressed in dotted decimal notation
graceful Indicates graceful restart. -
all Specifies all LDP instances. -

Views

User view

Default Level

3: Management level

Usage Guidelines

Usage Scenario

When there is a new LDP configuration, to validate the configuration, you can run the reset mpls ldp command.

Run the reset mpls ldp peer command to reset sessions, and LSPs of a specified peer.

The reset mpls ldp graceful command restarts a public network LDP instance. For a GR-enabled device that sets up a GR-enabled LDP session with a neighbor, this command can ensure service continuity during the restart.

The reset mpls ldp peer command restarts the session, and LSP of a specified peer. If service continuity is required during the restart of a specified peer, you need to run the reset mpls ldp peer peer-id graceful command.

Precautions

The reset mpls ldp command cannot be run during GR.

If the parameter graceful is not configured, all services are deleted during the restart.

Example

# Reset the global LDP function.

<HUAWEI> reset mpls ldp

# Reset all LDP instances.

<HUAWEI> reset mpls ldp all

# Reset the peer.

<HUAWEI> reset mpls ldp peer 2.2.2.9
# Restart the peer with the LSR ID being 3.3.3.9 without service interruption.
<HUAWEI> reset mpls ldp peer 3.3.3.9 graceful

reset mpls ldp error packet

Function

The reset mpls ldp error packet command deletes information about LDP-related error messages.

Format

reset mpls ldp error packet { tcp | udp | all }

Parameters

Parameter Description Value
tcp Deletes information about TCP error messages. -
udp Deletes information about UDP error messages. -
all Deletes information about all LDP-related error messages. -

Views

User view

Default Level

3: Management level

Usage Guidelines

By default, the system records information about LDP-related error messages. To delete the information, run the reset mpls ldp error packet command.

Example

# Delete information about LDP-related TCP error messages.

<HUAWEI> reset mpls ldp error packet tcp

reset mpls ldp event adjacency-down

Function

The reset mpls ldp event adjacency-down command deletes the recorded events that LDP adjacencies go Down.

Format

reset mpls ldp event adjacency-down

Parameters

None

Views

User view

Default Level

3: Management level

Usage Guidelines

By default, the system records the events that LDP adjacencies go Down. To delete the recorded events, run the reset mpls ldp event adjacency-down command.

Example

# Delete the recorded events that LDP adjacencies go Down.

<HUAWEI> reset mpls ldp event adjacency-down

reset mpls ldp event session-down

Function

The reset mpls ldp event session-down command deletes the recorded events that LDP sessions go Down.

Format

reset mpls ldp event session-down

Parameters

None

Views

User view

Default Level

3: Management level

Usage Guidelines

By default, the system records events that LDP sessions go Down. To delete the recorded events, run the reset mpls ldp event session-down command.

Example

# Delete the recorded events that LDP sessions go Down.

<HUAWEI> reset mpls ldp event session-down

route recursive-lookup tunnel

Function

The route recursive-lookup tunnel command enables tunnel iteration.

The undo route recursive-lookup tunnel command disables tunnel iteration.

By default, tunnel iteration is disabled.

Format

route recursive-lookup tunnel [ ip-prefix ip-prefix-name ] [ tunnel-policy policy-name ]

undo route recursive-lookup tunnel

Parameters

Parameter Description Value
ip-prefix ip-prefix-name Specifies the name of an IP prefix list. The value is an existing IP prefix list name.
tunnel-policy policy-name Specifies the name of a tunnel policy. The value is an existing tunnel policy name.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, an unlabeled BGP route or a static route can only be iterated to the outbound interface and next hop, but not a tunnel. After tunnel iteration is enabled, this route is preferentially iterated to an LDP LSP/TE/SR-TE tunnel. If no LDP LSP/TE/SR-TE tunnel exists, the route can also be iterated to the outbound interface and next hop.

After ip-prefix ip-prefix-name is set, only the unlabeled BGP routes or static routes that match the specified IP prefix list are iterated to an LDP LSP/TE/SR-TE tunnel.

After tunnel-policy policy-name is set, the tunnel policy is used for tunnel iteration.

If the ip-prefix ip-prefix-name and tunnel-policy policy-name parameters are not set, all static routes and unlabeled BGP routes will be preferentially iterated to an LDP LSP tunnel.

Precautions

If the route recursive-lookup tunnel command is run for several times, the latest configuration overrides the previous one.

A static route preferentially recurs to an IP route. If a static route recurs to a BGP route, the static route no longer recurs to a tunnel. If a static route recurs to a non-BGP route, the static route finally recurs to a tunnel based on the tunnel policy. If the static route recurs to a network segment, not to a host route, the network segment address is used to subscribe to a tunnel. Therefore, a non-BGP route to the next hop of a static route must exist so that the static route recurs to a tunnel (public network tunnel).

Example

# Iterate the unlabeled routes of the public network to the LDP LSP tunnel.
<HUAWEI> system-view
[~HUAWEI] route recursive-lookup tunnel

session protection

Function

The session protection command enables LDP session protection on each end of an LDP session.

The undo session protection command disables LDP session protection.

LDP session protection is disabled by default.

Format

session protection [ peer-group peer-group-name ] [ duration { infinite | time-value } ]

undo session protection [ peer-group peer-group-name ] [ duration { infinite | time-value } ]

Parameters

Parameter Description Value
peer-group peer-group-name Specifies the name of an LDP peer group. The parameter is specified using the ip ip-prefix command. The name is a string of 1 to 169 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
duration Indicates the period of time, during which LDP session protection remains effective. -
infinite Indicates that LDP session protection remains effective permanently. -
time-value Specifies a period of time, during which LDP session protection remains effective. The value is an integer ranging from 30 to 2147483, in seconds. The default value is 86400.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the direct link of a local LDP session between two devices fails, an LDP adjacency for the LDP session is torn down. The LDP session and related labels are also deleted. After the direct link recovers, the LDP session can be reestablished with labels distributed so that an LDP LSP over the session can converge. During this process, LDP LSP traffic is dropped.

To speed up LDP LSP convergence and minimize traffic loss, LDP session protection can be configured using the session protection command. With LDP session protection, in the same scenario, the LDP session does not need to be reestablished, and labels do not need to be re-distributed, which speeds up LDP LSP convergence and minimizes traffic loss.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

If the LDP session holdtime is set to different values at two ends of a local LDP session, the shorter value takes effect if the link of the local LDP session fails.

If you want to manually configure LDP session protection, you are advised to set the LDP session holdtime at both ends of an LDP session to the same value.

Example

# Enable LDP session protection and set the LDP session holdtime to 40 seconds.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] session protection duration 40

snmp-agent trap enable feature-name ldp

Function

The snmp-agent trap enable feature-name ldp command enables the trap for the MPLS LDP module.

The undo snmp-agent trap enable feature-name ldp command disables the trap for the MPLS LDP module.

By default, the trap is disabled for the MPLS LDP module.

Format

snmp-agent trap enable feature-name ldp trap-name { hwmplsldpvirtualtunneldown | hwmplsldpvirtualtunnelup | session-down-mib | session-retry | session-up-mib }

undo snmp-agent trap enable feature-name ldp trap-name { hwmplsldpvirtualtunneldown | hwmplsldpvirtualtunnelup | session-down-mib | session-retry | session-up-mib }

Parameters

Parameter Description Value
trap-name Enables the trap of MPLS LDP events of a specified type. -
hwmplsldpvirtualtunneldown Enables the trap of the event that an LDP virtual tunnel goes Down. -
hwmplsldpvirtualtunnelup Enables the trap of the event that an LDP virtual tunnel goes Up. -
session-down-mib Enables the trap of the event that an LDP session goes Down in the MIB. -
session-retry Enables the trap of the event that an LDP session is reestablished. -
session-up-mib Enables the trap of the event that an LDP session goes Up in the MIB. -

Views

System view

Default Level

3: Management level

Usage Guidelines

Run the snmp-agent trap enable feature-name ldp command to enable the LDP session trap. Currently, all traps of the MPLS LDP module are non-excessive trap. The frequent LDP session status changes do not trigger a large number of traps.

Example

# Enable the trap of the event that an LDP session is reestablished.

<HUAWEI> system-view
[~HUAWEI] snmp-agent trap enable feature-name ldp trap-name session-retry

snmp-agent trap enable feature-name mpls_lspm

Function

The snmp-agent trap enable feature-name mpls_lspm command enables the trap for the MPLS LSPM module.

The undo snmp-agent trap enable feature-name mpls_lspm command disables the trap for the MPLS LSPM module.

By default, the trap is disabled for the MPLS LSPM module.

Format

snmp-agent trap enable feature-name mpls_lspm [ trap-name trapname ]

undo snmp-agent trap enable feature-name mpls_lspm [ trap-name trapname ]

Parameters

Parameter Description Value
trap-name trapname Enables the trap of MPLS events of a specified type.
  • hwmplslspthresholdexceed: Enables the function to generate an alarm if the number of LSPs exceeds the alarm threshold.
  • hwmplslspthresholdexceedclear: Enables the function to clear an alarm if the number of LSPs falls below the alarm threshold.
  • hwmplslsptotalcountexceed: Enables the function to generate an alarm if the number of LSPs exceeds the maximum limit.
  • hwmplslsptotalcountexceedclear: Enables the function to clear an alarm if the number of LSPs falls below the maximum limit.
  • hwmplsresourcethresholdexceed: Enables the function to generate an alarm if the number of used MPLS resources exceeds the alarm threshold.
  • hwmplsresourcethresholdexceedclear: Enables the function to clear an alarm if the number of used MPLS resources falls below the alarm threshold.
  • hwmplsresourcetotalcountexceed: Enables the function to generate an alarm if the number of used MPLS resources exceeds the maximum limit.
  • hwmplsresourcetotalcountexceedclear: Enables the function to clear an alarm if the number of used MPLS resources falls below the maximum limit.

Views

System view

Default Level

3: Management level

Usage Guidelines

Run the snmp-agent trap enable feature-name mpls_lspm command to enable the MPLS LSPM module trap.

Example

# Enables the trap for the MPLS LSPM module.

<HUAWEI> system-view
[~HUAWEI] snmp-agent trap enable feature-name mpls_lspm

timer ldp-sync hold-down

Function

The timer ldp-sync hold-down command sets the Hold-down time for all IS-IS interfaces within an IS-IS process so that these interfaces remain in the Hold-down state before LDP sessions are established.

The undo timer ldp-sync hold-down command restores the default Hold-down time.

The default Hold-down time is 10 seconds.

Format

timer ldp-sync hold-down value

undo timer ldp-sync hold-down

Parameters

Parameter Description Value
value Specifies the period of time during which all IS-IS interfaces within an IS-IS process remain in the Hold-down state before LDP sessions are established. The value is an integer ranging from 0 to 65535, in seconds.

Views

IS-IS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If an active link between two devices enabled with synchronization between LDP and IS-IS recovers from a fault, the IS-IS module enters the Hold-down state and starts a Hold-down timer. This timer allows the devices to create an LDP session and set up an IS-IS neighbor relationship at the same time. Traffic can be switched back to the active link over a reachable IS-IS route for an established LDP LSP.

To set the Hold-down time for all interfaces within an IS-IS process, run the timer ldp-sync hold-down command.

Precautions

If both the timer ldp-sync hold-down command and the isis timer ldp-sync hold-down command in the interface view are executed, the isis timer ldp-sync hold-down command takes effect.

Example

# Set the Hold-down time for all interfaces within IS-IS process 100 to 15 seconds.

<HUAWEI> system-view
[~HUAWEI] isis 100
[*HUAWEI-isis-100] timer ldp-sync hold-down 15

timer ldp-sync hold-max-cost

Function

The timer ldp-sync hold-max-cost command sets the time during which an interface in an IGP process waits to leave the LDP-IGP synchronization state.

The undo timer ldp-sync hold-max-cost command restores the default setting.

By default, IGP keeps advertising the maximum cost on a device before an LDP session is reestablished.

Format

timer ldp-sync hold-max-cost { infinite | interval }

undo timer ldp-sync hold-max-cost

Parameters

Parameter Description Value
infinite Indicates that IGP keeps advertising the maximum cost on a device before an LDP session is reestablished. -
interval Specifies the period during which IGP advertises the maximum cost on a device. The value is an integer ranging from 0 to 65535, in seconds.

Views

IS-IS view, OSPF area view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

LDP and IGP synchronization prevents traffic loss on a network with primary and backup link switched paths (LSPs). The timer ldp-sync hold-max-cost command is used in either of the following situations:
  • When the primary LSP is recovering, this command allows the backup LSP to transmit traffic before the primary LSP is established.
  • After an LDP session fails over the primary LSP, this command is used to enable the backup LSP to transmit traffic before the primary LSP recovers.
Select parameters based on networking requirements:
  • If an IGP carries only LDP services, configure the parameter infinite to ensure that a selected IGP route is kept consistent with the LDP LSP.
  • If an IGP carries multiple types of services including LDP services, set the value of the parameter interval to ensure that a teardown of LDP sessions does not affect IGP route selection or other services.

Precautions

If an LDP session cannot go Up, configuring infinite affects IGP route selection because the interface keeps advertising the maximum cost.

Example

# Configure IS-IS to keep advertising the maximum cost by sending Link State PDUs until the LSP is established.
<HUAWEI> system-view
[~HUAWEI] isis 100
[*HUAWEI-isis-100] timer ldp-sync hold-max-cost infinite
# Configure OSPF to keep advertising the maximum cost by sending Link State Advertisements until the LSP is established.
<HUAWEI> system-view
[~HUAWEI] ospf 100
[*HUAWEI-ospf-100] area 0
[*HUAWEI-ospf-100-area-0.0.0.0] timer ldp-sync hold-max-cost infinite

tracert lsp

Function

The tracert lsp command detects the gateways along the LSP from the source to the destination.

Format

tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out | -g ] * ip destination-host mask-length [ ip-address ] [ nexthop nexthop-address ] [ detail ]

tracert lsp [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -t time-out | -s size | -g ] * bgp destination-host mask-length [ ip-address ] [ detail ]

Parameters

Parameter Description Value
-a source-ip Specifies the source IP address of Echo Request packets to be sent. If no source IP address is specified, the IP address of the outbound interface through which Echo Request packets are sent is used as a source IP address. -
-exp exp-value Specifies the EXP value of Echo Request packets to be sent.

The EXP value represents the priority of Echo Request packets.

NOTE:

If DSCP priority has been configured by running the set priority dscp command, the exp-value parameter does not take effect.

An integer that ranges from 0 to 7. The default value is 0.
-h ttl-value Specifies the TTL value of MPLS Echo Request packets to be sent.

The TTL field indicates the lifetime of the MPLS Echo Request packet and specifies the maximum number of hops that the packet can pass through. The TTL value is set on the source and reduced by 1 each time the packet passes through a hop. When the TTL value is reduced to 0, the packet is discarded. At the same time, an ICMP Timeout message is sent to notify the source host.

An integer that ranges from 1 to 255. The default value is 30.
-r reply-mode Specifies the mode in which the peer returns MPLS Echo Reply packets.
An integer that ranges from 1 to 2. The default value is 2. The meaning of each value is as follows:
  • 1: No MPLS Echo Reply packet is returned.
  • 2: The MPLS Echo Reply packet is encapsulated into IPv4/IPv6 UDP packets.
If the value of reply-mode is 1, the initiator starts a unidirectional test. If the test succeeds, the initiator prompts that the test times out; if the test fails, the initiator prompts that the LSP does not exist.
-t time-out Specifies the period of time for waiting for an MPLS Echo Reply packet. An integer that ranges from 0 to 65535, in milliseconds. The default value is 2000.
-s size Specify a packet size. The value is an integer ranging from 100 to 1400. The default value is the length of the UDP data segment.
-g Performs the NQA test using MPLS fragments. -
ip Tests an LDP LSP. -
bgp Tests a BGP LSP.
NOTE:

CE6870EI does not support this parameter.

-
destination-host Indicates the domain name or IPv4 address of the destination host of the LSP. The value is a string of 1 to 255 case-sensitive characters with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. Alternatively, the value can be a valid IPv4 address in dotted decimal notation.
mask-length Specifies the mask length of the LSP's destination host. The value is an integer ranging from 0 to 32.
ip-address Specifies the destination IP address carried in the IP header of an MPLS Echo Request packet.

The value is in dotted decimal notation.

By default, the destination IP address carried in the IP header of an MPLS Echo Request packet is 127.0.0.1.

nexthop nexthop-address Specifies the next-hop address.

The value is in dotted decimal notation.

detail

Displays details carried in MPLS Echo Reply packets.

-

Views

All views

Default Level

0: Visit level

Usage Guidelines

Usage Scenario

When a fault occurs on the LSPs of an MPLS network, you can run the ping lsp command to check the LSP connectivity based on the reply packet, and then run the tracert lsp command to locate the fault.

Prerequisites

  • The UDP module of each node is working properly; otherwise, the tracert operation fails.
  • The MPLS module of each node is enabled and is working properly.
  • The ICMP module of each node is working properly; otherwise, three asterisks (* * *) are displayed.

Procedure

The execution process of the tracert lsp command is as follows:
  • The source sends an MPLS Echo Request packet with the TTL being 1. After the TTL times out, the first hop sends an MPLS Echo Reply packet to the source.
  • The source sends an MPLS Echo Request packet with the TTL being 2. After the TTL times out, the second hop sends an MPLS Echo Reply packet to the source.
  • The source sends an MPLS Echo Request packet with the TTL being 3. After the TTL times out, the third hop sends an MPLS Echo Reply packet to the source.
  • The preceding process proceeds until the MPLS Echo Request packet reaches the destination.

When the device on the destination hop receives the MPLS Echo Request packet, it returns an MPLS Echo Reply packet, indicating the end of the tracert. The purpose behind this is to record the source of each ICMP Timeout packet to provide a trace of the path the packet took to reach the destination.

Precautions

To prevent the egress node from forwarding the received MPLS Echo Request packet to other nodes, you can set the destination address in the IP header of the Echo Request packet to a loopback address with the prefix being 127.0.0.1/8.

Example

# Tracert the LDP LSP to 10.4.4.9/32.
<HUAWEI> tracert lsp ip 10.4.4.9 32
  LSP Trace Route FEC: IPV4 PREFIX 10.4.4.9/32 , press CTRL_C to break.
  TTL   Replier            Time    Type      Downstream
  0                                Ingress   10.1.2.2/[1028 ]
  1     10.1.2.2            94 ms   Transit  10.4.4.9/[3 ]
  2     10.4.4.9            94 ms   Egress
# Tracert the BGP LSP to 1.1.1.1/32 by sending Echo Request packets with 4.4.4.4 as the source IP address.
<HUAWEI> tracert lsp -a 4.4.4.4 bgp 1.1.1.1 32
  LSP Trace Route FEC: IPV4 PREFIX 1.1.1.1/32 , press CTRL_C to break.
  TTL    Replier            Time    Type      Downstream
  0                                 Ingress   10.205.0.1/[3 5199 ]
  1      10.205.0.1        15 ms   Transit    10.101.0.1/[814 ]
  2      1.1.1.1            7 ms    Egress    
Table 11-37  Description of the tracert lsp command output

Item

Description

TTL

Indicates the TTL value in an Echo Request packet. It represents the number of hops of the tunnel an Echo Request packet passes.

Replier

IP address of a switching node that returns an MPLS Echo Reply packet.

Time

RTT, in milliseconds.

Type

Type of a node. Available node types:
  • Ingress node
  • Transit node
  • Egress node

Downstream

Address and label of a downstream device.

Related Topics

ttl expiration pop disable

Function

The ttl expiration pop disable command enables a device to send ICMP response packets back along LSPs after the MPLS TTL expires.

The undo ttl expiration pop disable command disables this function. Therefore, ICMP response packets are forwarded along the local IP route.

By default, the LSR returns an ICMP packet using the local IP route if the received MPLS TTL-expired packet contains one label.

Format

ttl expiration pop disable

undo ttl expiration pop disable

Parameters

None

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On an MPLS network, when an LSR receives MPLS packets with the TTL value of 1, the LSR generates an ICMP TTL-expired message.

The LSR returns the TTL-expired message to the sender in the following ways:
  • If the LSR has a reachable route to the sender, it directly sends the TTL-expired message to the sender through the IP route.
  • If the LSR has no reachable route to the sender, it forwards the TTL-expired message along the LSP. The egress node forwards the TTL-expired message to the sender.

In most cases, the received MPLS packet contains only one label and the LSR responds to the sender with the TTL-expired message using the first method. If the MPLS packet contains multiple labels, the LSR uses the second method.

The MPLS VPN packets may contain only one label when they arrive at an autonomous system boundary router (ASBR) on the MPLS VPN. These devices have no IP routes to the sender, so they use the second method to reply to the TTL-expired messages.

Precautions

The undo mpls (system view) command deletes all configurations of the ttl expiration pop command.

Example

# Forward ICMP packets through an LSP after the MPLS TTL expires.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] ttl expiration pop disable

undo outbound peer all

Function

The undo outbound peer all command deletes all outbound policies.

Format

undo outbound peer all

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Before MPLS LDP is used, the outbound peer fec, and outbound peer split-horizon commands need to be executed to configure an outbound policy to control LDP LSP establishments. If multiple outbound policies have been configured, run the undo outbound peer all command to simultaneously delete all the outbound policies.

Prerequisites

MPLS LDP has been enabled globally using the mpls ldp command in the system view.

Precautions

Running the undo outbound peer all command deletes all outbound policies. Therefore, exercise caution when running this command.

Example

# Delete all outbound policies.

<HUAWEI> system-view
[~HUAWEI] mpls ldp
[*HUAWEI-mpls-ldp] undo outbound peer all
Translation
Download
Updated: 2019-03-21

Document ID: EDOC1000166501

Views: 44170

Downloads: 334

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