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

S7700 and S9700 V200R011C10

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

Command Support

  • The SA series cards do not support the MPLS feature.

  • The FC/SC series cards do not support the MPLS OAM.

  • The EH1D2X48SEC0 card does not support MPLS OAM.

  • The XGE interface connected to ACU2 does not support MPLS TE or MPLS OAM and can provide other MPLS features.

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 10.1.1.1 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 10.1.1.1

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

  • MD5 authentication and keychain authentication cannot be configured together on one peer.

  • Configuring LDP keychain authentication leads to reestablishment of an LDP session and deletes the Label Switched Path (LSP) associated with the LDP session.

Example

# Configure LDP keychain authentication for the peer with an LSR ID of 10.1.1.1. 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 10.1.1.1 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 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.

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.

  • 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.

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 sha-256
[HUAWEI-keychain-kc1-keyid-1] key-string abcDEF-13579
[HUAWEI-keychain-kc1-keyid-1] send-time 14:30 2016-10-10 to 14:50 2016-10-10
[HUAWEI-keychain-kc1-keyid-1] receive-time 14:40 2016-10-10 to 14:50 2016-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 keychain has been configured using the keychain command.

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.

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

  • 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.

  • Before a peer group is referenced, create it. By default, a nonexistent peer group cannot be specified in this command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent peer group is specified in this command, a local device performs keychain authentication for each LDP session connected to each LDP peer.

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 sha-256
[HUAWEI-keychain-kc1-keyid-1] key-string abcDEF-13579
[HUAWEI-keychain-kc1-keyid-1] send-time 14:30 2016-10-10 to 14:50 2016-10-10
[HUAWEI-keychain-kc1-keyid-1] receive-time 14:40 2016-10-10 to 14:50 2016-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 10.1.1.1 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

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On an MPLS network with a backup link, if a link fault occurs, Interior Gateway Protocol (IGP) routes converge and routes related to the backup link become available. After IGP route convergence is complete, an LDP LSP over the backup link becomes available. During this process, traffic is interrupted. To prevent traffic interruption, you can configure LDP fast reroute (FRR). On the network enabled with LDP FRR, if an interface failure (detected by the interface itself or by an associated BFD session) or a primary LSP failure (detected by an associated BFD session) occurs, LDP FRR is notified of the failure and rapidly forwards traffic to a backup LSP, protecting traffic on the primary LSP. The traffic switchover is performed within 50 milliseconds, avoiding traffic interruption.

LDP FRR is classified into the following types:
  • LDP manual FRR: A backup LSP is configured manually by specifying an outbound interface or a next hop. The configuration is complex but flexible because a backup LSP can be configured manually. LDP manual FRR applies to simple networks.

  • Auto LDP FRR: A backup LSP is automatically created based on a specified policy. The configuration is simple and loop-free. Auto LDP FRR applies to complex and large networks.

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) 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

During LDP GR, changing the policy for triggering the setup of backup LSPs is not allowed.

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.

Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all backup routes trigger backup LDP LSP establishment.

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 cfg-name bind ldp-lsp peer-ip ip-address nexthop ip-address [ interface interface-type interface-number ]

undo bfd cfg-name

Parameters

Parameter Description Value
cfg-name Specifies the name of a BFD session. The value is a string of 1 to 15 case-insensitive characters, spaces not supported. 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 10.2.1.1, the next hop IP address being 10.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 10.2.1.1 nexthop 10.1.1.1 interface vlanif 100
[HUAWEI-bfd-lsp-session-1to4]

bfd bind static-lsp

Function

The bfd bind static-lsp command creates a BFD session to detect static LSPs.

The undo bfd command deletes a specified BFD session.

By default, no BFD session is created to detect static LSPs.

Format

bfd cfg-name bind static-lsp lsp-name

undo bfd cfg-name

Parameters

Parameter Description Value
cfg-name Specifies the BFD configuration name. The value is a string of 1 to 15 case-insensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
lsp-name Specifies the name of the static LSP bound to the BFD session. The value is an existing static LSP name.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can deploy MPLS services by manually configuring static LSPs on small networks with simple topology and stable performance. 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.

Prerequisites

BFD has been enabled globally using the bfd command in the system view.

Precautions

  • If the specified static LSP does not exist or the BFD configuration name exists, the BFD session cannot be created.

  • The commit command must be run to make the configured BFD parameters take effect before a BFD session is created.

  • When the status of the static LSP is Down, a BFD session cannot be created.

Example

# Create a BFD session to detect the static LSP named 1to4.

<HUAWEI> system-view
[HUAWEI] bfd bfd1to4 bind static-lsp 1to4
[HUAWEI-bfd-lsp-session-bfd1to4]

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
          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
          Capability-announcement        : Off
          mLDP MBB Capability            : Off
            Wait-ack timer(sec)          : 10
            Switch-delay timer(ms)       : 100
          mLDP P2MP Capability           : Off
          mLDP MP2MP Capability          : Off
          Label withdraw-delay           : Off
            Withdraw-delay timer(sec)    : 5
          Send LSP down reason           : Off
          Ingress LSP Load-balance Num   : 16
          Transit LSP Load-balance Num   : 16
          Smart-policy Ingress           : Off
          Smart-policy Auto-dod-request  : Off
 ----------------------------------------------------------
Table 9-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. You can set this value using the graceful-restart timer reconnect command.

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.

Label retention mode

LDP label retention modes include:
  • Liberal: free mode

  • Conservative: conservative mode.

The default label retention mode is liberal.

Label distribution mode

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

Label advertisement

LDP label advertisement modes include:
  • DU: downstream unsolicited mode.
  • DOD: downstream on demand mode.
The default label advertisement mode is DU. You can set the LDP label advertisement mode using the mpls ldp advertisement command.

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 and not supported currently.

Graceful delete timer(sec)

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

Capability-announcement

Dynamic capability announcement function. This function is disabled and not supported currently.

mLDP MBB Capability

Whether the mLDP make-before-break capability is enabled. The default value is "Off", indicating that mLDP make-before-break is disabled.

Wait-ack timer(sec)

Whether the multipoint extensions for LDP (mLDP) make-before-break capability is enabled. The default value is "Off", indicating that mLDP make-before-break is disabled.

Switch-delay timer(ms)

The default value of the time for waiting for an MBB ACK Notification message.

mLDP P2MP Capability

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

mLDP MP2MP Capability

Whether mLDP multipoint-to-multipoint (MP2MP) is enabled global. The default value is "Off", indicating that mLDP MP2MP is disabled globally.

Label withdraw-delay

Whether the label withdraw delay function is enabled. The default value is "Off", indicating that this function is disabled.

Withdraw-delay timer(sec)

Default value of the label withdraw delay timer (in seconds).

Send LSP down reason

Whether a node is enabled to report the fault location and cause to the ingress. The default value is "Off", indicating that the faulty node is disabled from reporting the fault cause to the ingress.

Ingress LSP Load-balance Num

Default maximum number of equal-cost LDP LSPs that can be established on the ingress.

Transit LSP Load-balance Num

Default maximum number of equal-cost LDP LSPs that can be established on a transit node.

Smart-policy Ingress

Whether the smart LDP ingress policy is enabled.

Smart-policy Auto-dod-request

Whether on-demand LDP request trigger is enabled.

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:
 --------------------------------------------------------------
          BFD detect-multiplier        : 3
          BFD min-tx-interval(ms)      : 1000
          BFD min-rx-interval(ms)      : 1000
          Label advertisement mode     : Implicit null
          LSP trigger mode             : Host
          LDP LSP number threshold-alarm upper limit  : 80
          LDP LSP number threshold-alarm lower limit  : 75 
          BGP LSP number threshold-alarm upper limit  : 80
          BGP LSP number threshold-alarm lower limit  : 75
          BGP V6 LSP number threshold-alarm upper limit  : 80
          BGP V6 LSP number threshold-alarm lower limit  : 75 
          Dynamic Label number threshold-alarm upper limit  : 80
          Dynamic Label number threshold-alarm lower limit  : 70
          RSVP LSP number threshold-alarm upper limit  : 80
          RSVP LSP number threshold-alarm lower limit  : 75
          Total LSP number threshold-alarm upper limit  : 80
          Total LSP number threshold-alarm lower limit  : 75
          Total CR LSP number threshold-alarm upper limit  : 80
          Total CR LSP number threshold-alarm lower limit  : 75  
          Ingress LDP LSP number threshold-alarm upper limit  : 80
          Ingress LDP LSP number threshold-alarm lower limit  : 75
          Transit LDP LSP number threshold-alarm upper limit  : 80
          Transit LDP LSP number threshold-alarm lower limit  : 75
          Egress LDP LSP number threshold-alarm upper limit  : 80
          Egress LDP LSP number threshold-alarm lower limit  : 75
          Ingress BGP LSP number threshold-alarm upper limit  : 80
          Ingress BGP LSP number threshold-alarm lower limit  : 75
          Egress BGP LSP number threshold-alarm upper limit  : 80
          Egress BGP LSP number threshold-alarm lower limit  : 75
          Egress BGP V6 LSP number threshold-alarm upper limit  : 80
          Egress BGP V6 LSP number threshold-alarm lower limit  : 75
          Ingress RSVP LSP number threshold-alarm upper limit  : 80
          Ingress RSVP LSP number threshold-alarm lower limit  : 75
          Transit RSVP LSP number threshold-alarm upper limit  : 80
          Transit RSVP LSP number threshold-alarm lower limit  : 75
          Egress RSVP LSP number threshold-alarm upper limit  : 80
          Egress RSVP LSP number threshold-alarm lower limit  : 75
          Total ingress LSP number threshold-alarm upper limit  : 80
          Total ingress LSP number threshold-alarm lower limit  : 75
          Total transit LSP number threshold-alarm upper limit  : 80
          Total transit LSP number threshold-alarm lower limit  : 75
          Total egress LSP number threshold-alarm upper limit  : 80
          Total egress LSP number threshold-alarm lower limit  : 75
          Total ingress CR LSP number threshold-alarm upper limit  : 80
          Total ingress CR LSP number threshold-alarm lower limit  : 75
          Total transit CR LSP number threshold-alarm upper limit  : 80
          Total transit CR LSP number threshold-alarm lower limit  : 75
          Total egress CR LSP number threshold-alarm upper limit  : 80
          Total egress CR LSP number threshold-alarm lower limit  : 75
          Auto bypass tunnel interface number threshold-alarm upper limit  : 80
          Auto bypass tunnel interface number threshold-alarm lower limit  : 75
          P2MP auto tunnel interface number threshold-alarm upper limit  : 80
          P2MP auto tunnel interface number threshold-alarm lower limit  : 75
          TE dynamic bfd number threshold-alarm upper limit  : 80
          TE dynamic bfd number threshold-alarm lower limit  : 75
          LDP dynamic bfd number threshold-alarm upper limit  : 80
          LDP dynamic bfd number threshold-alarm lower limit  : 75
          Total MLDP tree number threshold-alarm upper limit  : 80
          Total MLDP tree number threshold-alarm lower limit  : 75
          Total MLDP branch number threshold-alarm upper limit  : 80
          Total MLDP branch number threshold-alarm lower limit  : 75
          Total LDP remote adjacency number threshold-alarm upper limit  : 80
          Total LDP remote adjacency number threshold-alarm lower limit  : 75
          Total LDP local adjacency number threshold-alarm upper limit  : 80
          Total LDP local adjacency number threshold-alarm lower limit  : 75
          Total CSPF node number threshold-alarm upper limit  : 80
          Total CSPF node number threshold-alarm lower limit  : 75
          Total CSPF link number threshold-alarm upper limit  : 80
          Total CSPF link number threshold-alarm lower limit  : 75
          Total CSPF network-lsa number threshold-alarm upper limit  : 80
          Total CSPF network-lsa number threshold-alarm lower limit  : 75
          Total CSPF SRLG number threshold-alarm upper limit  : 80
          Total CSPF SRLG number threshold-alarm lower limit  : 75
          RSVP peer number threshold-alarm upper limit  : 80
          RSVP peer number threshold-alarm lower limit  : 75
 --------------------------------------------------------------
Table 9-2  Description of the display default-parameter mpls management command output

Item

Description

BFD detect-multiplier

BFD detection multiplier. The default value is 3. You can set this value using the mpls bfd command.

BFD min-tx-interval(ms)

Interval for sending BFD packets. You can set this value using the mpls bfd command.

BFD min-rx-interval(ms)

Interval for receiving BFD packets. You can set this value using the mpls bfd command.

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.

LDP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for LDP LSPs. You can set the LSP trigger mode using the mpls ldp-lsp-number threshold-alarm command.

LDP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for LDP LSPs. You can set the LSP trigger mode using the mpls ldp-lsp-number threshold-alarm command.

BGP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for BGP LSPs. You can set the LSP trigger mode using the mpls bgp-lsp-number threshold-alarm command.

BGP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for BGP LSPs. You can set the LSP trigger mode using the mpls bgp-lsp-number threshold-alarm command.

BGP V6 LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for BGP IPv6 LSPs. You can set the LSP trigger mode using the mpls bgpv6-lsp-number threshold-alarm command.

BGP V6 LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for BGP IPv6 LSPs. You can set the LSP trigger mode using the mpls bgpv6-lsp-number threshold-alarm command.

Dynamic Label number threshold-alarm upper limit

Upper limit of the alarm threshold for dynamic label usage. You can set the LSP trigger mode using the mpls dynamic-label-number threshold-alarm command.

Dynamic Label number threshold-alarm lower limit

Lower limit of the alarm threshold for dynamic label usage. You can set the LSP trigger mode using the mpls dynamic-label-number threshold-alarm command.

RSVP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for RSVP LSPs. You can set the LSP trigger mode using the mpls rsvp-lsp-number threshold-alarm command.

RSVP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for RSVP LSPs. You can set the LSP trigger mode using the mpls rsvp-lsp-number threshold-alarm command.

Total LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total LSPs. You can set the LSP trigger mode using the mpls total-lsp-number threshold-alarm command.

Total LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total LSPs. You can set the LSP trigger mode using the mpls total-lsp-number threshold-alarm command.

Total CR LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total CR-LSPs. You can set the LSP trigger mode using the mpls total-crlsp-number threshold-alarm command.

Total CR LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total CR-LSPs. You can set the LSP trigger mode using the mpls total-crlsp-number threshold-alarm command.

Ingress LDP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for ingress LDP LSP

Ingress LDP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for ingress LDP LSP

Transit LDP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for transit LDP LSP

Transit LDP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for transit LDP LSP

Egress LDP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for egress LDP LSP

Egress LDP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for egress LDP LSP

Ingress BGP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for ingress BGP LSP

Ingress BGP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for ingress BGP LSP

Egress BGP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for egress BGP LSP

Egress BGP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for egress BGP LSP

Egress BGP V6 LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for egress BGP V6 LSP

Egress BGP V6 LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for egress BGP V6 LSP

Ingress RSVP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for ingress RSVP LSP

Ingress RSVP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for ingress RSVP LSP

Transit RSVP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for transit RSVP LSP

Transit RSVP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for transit RSVP LSP

Egress RSVP LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for egress RSVP LSP

Egress RSVP LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for egress RSVP LSP

Total ingress LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total ingress LSP

Total ingress LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total ingress LSP

Total transit LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total transit LSP

Total transit LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total transit LSP

Total egress LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total egress LSP

Total egress LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total egress LSP

Total ingress CR LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total ingress CR-LSP

Total ingress CR LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total ingress CR-LSP

Total transit CR LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total transit CR-LSP

Total transit CR LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total transit CR-LSP

Total egress CR LSP number threshold-alarm upper limit

Upper limit of the alarm threshold for total egress CR-LSP

Total egress CR LSP number threshold-alarm lower limit

Lower limit of the alarm threshold for total egress CR-LSP

Auto bypass tunnel interface number threshold-alarm upper limit

Upper limit of the alarm threshold for auto bypass tunnel interface

Auto bypass tunnel interface number threshold-alarm lower limit

Lower limit of the alarm threshold for auto bypass tunnel interface

P2MP auto tunnel interface number threshold-alarm upper limit

Upper limit of the alarm threshold for P2MP auto tunnel interface

P2MP auto tunnel interface number threshold-alarm lower limit

Lower limit of the alarm threshold for P2MP auto tunnel interface

TE dynamic bfd number threshold-alarm upper limit

Upper limit of the alarm threshold for TE dynamic bfd

TE dynamic bfd number threshold-alarm lower limit

Lower limit of the alarm threshold for TE dynamic bfd

LDP dynamic bfd number threshold-alarm upper limit

Upper limit of the alarm threshold for LDP dynamic bfd

LDP dynamic bfd number threshold-alarm lower limit

Lower limit of the alarm threshold for LDP dynamic bfd

Total MLDP tree number threshold-alarm upper limit

Upper limit of the alarm threshold for total MLDP tree

Total MLDP tree number threshold-alarm lower limit

Lower limit of the alarm threshold for total MLDP tree

Total MLDP branch number threshold-alarm upper limit

Upper limit of the alarm threshold for total MLDP branch

Total MLDP branch number threshold-alarm lower limit

Lower limit of the alarm threshold for total MLDP branch

Total LDP remote adjacency number threshold-alarm upper limit

Upper limit of the alarm threshold for total LDP remote adjacency

Total LDP remote adjacency number threshold-alarm lower limit

Lower limit of the alarm threshold for total LDP remote adjacency

Total LDP local adjacency number threshold-alarm upper limit

Upper limit of the alarm threshold for total LDP local adjacency

Total LDP local adjacency number threshold-alarm lower limit

Lower limit of the alarm threshold for total LDP local adjacency

Total CSPF node number threshold-alarm upper limit

Upper limit of the alarm threshold for total CSPF node

Total CSPF node number threshold-alarm lower limit

Lower limit of the alarm threshold for total CSPF node

Total CSPF link number threshold-alarm upper limit

Upper limit of the alarm threshold for total CSPF link

Total CSPF link number threshold-alarm lower limit

Lower limit of the alarm threshold for total CSPF link

Total CSPF network-lsa number threshold-alarm upper limit

Upper limit of the alarm threshold for total CSPF network-lsa

Total CSPF network-lsa number threshold-alarm lower limit

Lower limit of the alarm threshold for total CSPF network-lsa

Total CSPF SRLG number threshold-alarm upper limit

Upper limit of the alarm threshold for total CSPF SRLG

Total CSPF SRLG number threshold-alarm lower limit

Lower limit of the alarm threshold for total CSPF SRLG

RSVP peer number threshold-alarm upper limit

Upper limit of the alarm threshold for RSVP peer

RSVP peer number threshold-alarm lower limit

Lower limit of the alarm threshold for RSVP peer

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 | vpn-instance vpn-instance-name ] ldp-sync interface

Parameters

Parameter Description Value
process-id Specifies the IS-IS process ID. The value is an integer ranging from 1 to 65535.
vpn-instance vpn-instance-name Specifies the VPN instance name.

The value must be an existing VPN instance name.

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 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 9-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 10 seconds. 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:
  • Sync-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 configuration

Function

The display lspv configuration command displays the current configuration of LSPV tracert.

Format

display lspv configuration

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

You can run the display lspv configuration command to check the current LSPV configurations.

Example

# Display the current configuration of LSPV tracert.

<HUAWEI> display lspv configuration
lspv packet filter 2100
undo lspv mpls-lsp-ping echo enable
Table 9-4  Description of the display lspv configuration command output

Item

Description

lspv packet filter 2100

Filters the LSPV tracert packet with the specific source address according to ACL 2100.

To configure the filtering of the LSPV tracert packet with the specific source address, run the lspv packet-filter command.

undo lspv mpls-lsp-ping echo enable

Disables the response to MPLS Ping packets.

To configure a device to respond to MPLS Echo Request packets, run the lspv mpls-lsp-ping echo enable command.

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: 0 packet(s)
Total received: 0 packet(s)
MPLS echo request sent: 0 packet(s), received: 0 packet(s)
MPLS echo reply sent: 0 packet(s), received: 0 packet(s)
---------------------------------------------------------------------
Statistcs base on ReturnCode:
0 - No return code,1 - Malformed echo request received,2 - One or more
of the TLVs was not understood,3 - Replying router is an egress for
the FEC at stack-depth, 4 - Replying router has no mapping for the FEC
at stack-depth,5 - Downstream Mapping Mismatch, 6 - Upstream Interface
Index Unknown, 7 - Reserved, 8 - Label switched at stack-depth,9 -
Label switched but no MPLS forwarding at stack-depth,10 - Mapping for
this FEC is not the given label at stack-depth,11 - No label entry at
stack-depth,12 - Protocol not associated with interface at FEC
stack-epth,13 - Premature termination of ping due to label stack
hrinking to a single label.:
---------------------------------------------------------------------
Value      SendNum      RecvNum       Value      SendNum      RecvNum
    0            0            0           1            0            0
    2            0            0           3            0            0
    4            0            0           5            0            0
    6            0            0           7            0            0
    8            0            0           9            0            0
   10            0            0          11            0            0
   12            0            0          13            0            0
---------------------------------------------------------------------  
Table 9-5  Description of the display lspv statistics command output

Item

Description

Total sent

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

Total received

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

MPLS echo request sent, received

Number of sent and received MPLS Echo Request packets

MPLS echo reply sent, received

Number of sent and received MPLS Echo Reply packets

Statistcs base on ReturnCode

Statistcs base on ReturnCode:
  • 0: No return code
  • 1: Malformed echo request received
  • 2: One or more of the TLVs was not understood
  • 3: Replying router is an egress for the FEC at stack-depth
  • 4: Replying router has no mapping for the FEC at stack-depth
  • 5: Downstream Mapping Mismatch
  • 6: Upstream Interface Index Unknown
  • 7: Reserved
  • 8: Label switched at stack-depth
  • 9: Label switched but no MPLS forwarding at stack-depth
  • 10: Mapping for this FEC is not the given label at stack-depth
  • 11: No label entry at stack-depth
  • 12: Protocol not associated with interface at FEC stack-epth
  • 13: Premature termination of ping due to label stack hrinking to a single label

Value

The value of ReturnCode in sent or received LSP verification packets.

SendNum

Number of sent packets with this ReturnCode.

RecvNum

Number of received packets with this ReturnCode.

Related Topics

display mpls bfd session

Function

The display mpls bfd session command displays information about BFD sessions for MPLS.

Format

display mpls bfd session [ fec fec-address | monitor | nexthop ip-address | outgoing-interface interface-type interface-number | statistics | verbose ]

display mpls bfd session protocol ldp [ fec fec-address [ verbose ] ]

display mpls bfd session protocol { cr-static | rsvp-te } [ lsp-id ingress-lsr-id session-id lsp-id [ verbose ] ]

display mpls bfd session protocol bgp [ fec fec-address [ verbose ] ]

Parameters

Parameter Description Value
fec fec-address Displays information about the BFD session of a specified FEC. The value is in dotted decimal notation.
monitor Displays monitoring information of BFD sessions. -
nexthop ip-address Displays information about the BFD session of a specified next hop. The value is in dotted decimal notation.
outgoing-interface interface-type interface-number Displays information about the BFD session of the LSP with a specified outbound interface.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-
protocol Indicates the type of the protocol. -
cr-static Displays information about the BFD session for static CR-LSP. -
ldp Displays information about the BFD session for LDP. -
rsvp-te Displays information about the BFD session for RSVP-TE. -
statistics Displays statistics about BFD sessions such as the total number of BFD sessions. -
verbose Displays detailed information about BFD sessions. -
lsp-id ingress-lsr-id Specifies the LSR ID of the ingress. The value is in dotted decimal notation.
session-id Specifies the ID of a session. The value is an integer ranging from 0 to 65535.
lsp-id Specifies the LSP ID. The value is an integer ranging from 0 to 65535.
bgp Displays information about BFD sessions for BGP. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Run the display mpls bfd session command to view information about a BFD session and the LSP detected by BFD, including the destination address and outbound interface of the LSP, the local discriminator of the BFD session, and the status of an MPLS BFD session.

Example

# Display information about the BFD session.

<HUAWEI> display mpls bfd session
-------------------------------------------------------------------------------
                 BFD Information: LDP  LSP
-------------------------------------------------------------------------------
FEC            DISC  OUT-IF      NEXTHOP        TUNNEL         STATE
3.3.3.3        8     VLANIF100   10.1.1.2       Tunnel1        Up
Table 9-6  Description of the display mpls bfd session command output

Item

Description

FEC

Forwarding equivalence class.

DISC

Local discriminator of a BFD session.

OUT-IF

Outbound interface.

NEXTHOP

IP address of the next hop.

TUNNEL

Name of a tunnel.

STATE

Status of an MPLS BFD session.
  • Up
  • Down

# Display detailed information about a BFD session with the specified protocol type and LSP ID.

<HUAWEI> display mpls bfd session protocol rsvp-te lsp-id 3.3.3.3 3 1 verbose
--------------------------------------------------------------------- 
                 BFD Information: TE TUNNEL                                     
--------------------------------------------------------------------- 
  No                       :  1                                                 
  LspIndex                 :  6157                                              
  Protocol                 :  RSVP-TE                                           
  Tunnel-Interface         :  Tunnel1                                       
  Fec                      :  2.2.2.2                                           
  Nexthop                  :  10.2.3.2                                         
  Out-Interface            :  Vlanif100                              
  Bfd-Discriminator        :  8195                                              
  TEMIB Tunn Table Index   :  3                                                 
  SessionTunnelID          :  3                                                 
  LocalLspId               :  1                                                 
  PrevSessionTunnelID      :  -                                                 
  NextSessionTunnelID      :  12                                                
  ActTx                    :  2200                                              
  ActRx                    :  2200                                              
  ActMulti                 :  -                                                 
  Bfd-State                :  Down                                              
  Time                     :  2559 sec   
Table 9-7  Description of the display mpls bfd session protocol rsvp-te lsp-id 3.3.3.3 3 1 verbose command output

Item

Description

No

Serial number.

LspIndex

Index number of an LSP.

Protocol

Protocol type.

Tunnel-Interface

Name of a tunnel interface.

Fec

Forwarding equivalence class.

Nexthop

IP address of the next hop.

Out-Interface

Name of an outbound interface.

Bfd-Discriminator

Local discriminator of a BFD session.

TEMIB Tunn Table Index

Index of the tunnel entry to which an LSP corresponds.

SessionTunnelID

BFD session ID.

LocalLspId

ID of a local LSP.

PrevSessionTunnelID

Tunnel ID mapping the previous LSP to which a BFD session is bound.

NextSessionTunnelID

Tunnel ID mapping the next LSP to which a BFD session is bound.

ActTx

Actual interval for sending BFD packets, in milliseconds.

ActRx

Actual interval for receiving BFD packets, in milliseconds.

ActMulti

Actual local detection multiple of a BFD session.

Bfd-State

Status of the BFD session.
  • Up
  • Down

Time

Period from the time when the BFD session is created or updated till now, in seconds.

# Display BFD session statistics.

<HUAWEI> display mpls bfd session statistics
Lsp Type       sess num  Tx        Rx        Mult      Trig-type
LDP LSP        0         1000      1000      3         NONE
BGP LSP        0         1000      1000      3         NONE
STATIC CRLSP   0         1000      1000      3         -
RSVP           0         1000      1000      3         -
TOTAL          0
Table 9-8  Description of the display mpls bfd session statistics command output

Item

Description

Lsp Type

LSP type.

sess num

Number of BFD sessions monitoring the LSP.

Tx

Effective minimum interval (in ms) at which BFD packets are sent.

Rx

Effective minimum interval (in ms) at which BFD packets are received.

Mult

Effective BFD detection multiplier.

Trig-type

BFD session establishment policy:

  • HOST: BFD sessions are established using host addresses.

  • IP-PREFIX: BFD sessions are established using an IP address prefix list.

  • FEC-LIST: BFD sessions are established using a FEC list.

  • NONE: No policy for establishing BFD sessions is configured.

  • -: N/A

# Display BFD session monitoring information.

<HUAWEI> display mpls bfd session monitor

LDP BFD TRIGGER INFO:
  Trig-Type  : None
  OutIfIndex : Invalid
  NextHop    : Invalid

LDP BFD SCAN INFO:
  Cur BackGround Oper  : Off
  Cur Scan Index       : Invalid
  First Bfd Scan Index : Invalid
  Scan Again           : No
  License Lim Reached  : No
  License Lim Scn Agn  : No
  BackGround Status    : Suspended/Off
  Current Scan Node    : -

BGP BFD SCAN INFO:
  Cur BackGround Oper  : Off
  Cur Scan Index       : Invalid
  Scan Again           : No
  License Lim Reached  : No
  BackGround Status    : Suspended/Off

TE BFD SCAN INFO:
  Cur BackGround Oper  : Off
  Cur Scan Index       : 0
  First Bfd Scan Index : 0
  Scan Again           : No
  License Lim Reached  : No
  License Lim Scn Agn  : No
  BackGround Status    : Suspended/Off

CAPABILITY :
  Bfd Capability     : Disable
  Ldp Bfd Capability : Disable
  Bgp Bfd Capability : Disable
  Te Bfd Capability  : Disable
  Bfd Session Full   : Not-full
  Bfd Clearing       : No


BFD FOR LSP PAF LICENSE INFORMATION:
Lsp Type  Min-Val   Max-Val   Avail-Val Created
LDP LSP   0         1024      1024      0
BGP LSP   0         1024      1024      0
TE LSP    0         2048      256       0 + 0 (RSVP + CRSTATIC)
Table 9-9  Description of the display mpls bfd session monitor command output

Item

Description

Trig-Type

BFD session establishment policy:

  • HOST: BFD sessions are established using host addresses.

  • IP-PREFIX: BFD sessions are established using an IP address prefix list.

  • FEC-LIST: BFD sessions are established using a FEC list.

  • NONE: No policy for establishing BFD sessions is configured.

  • -: N/A

OutIfIndex

Index of a BFD session outbound interface.

NextHop

Next-hop IP address of a BFD session.

Cur BackGround Oper

Background operation:

  • Create

  • Delete

  • Update

  • Off

Cur Scan Index

Scanned BFD session index. "Invalid" indicates that no BFD session is established.

First Bfd Scan Index

First scanned BFD session index. "Invalid" indicates that no BFD session is established.

Scan Again

Whether a device scans BFD sessions again:

  • Yes

  • No

License Lim Reached

Whether the number of established BFD sessions reaches the upper limit specified in the license file:

  • Yes

  • No

License Lim Scn Agn

Whether the switch needs to check the threshold-crossing event about establishment BFD sessions:

  • Yes

  • No

BackGround Status

Background status:

  • Running

  • Suspended/Off

Current Scan Node

Name of a node that is being scanned.

Bfd Capability

Whether MPLS BFD is enabled:

  • Enable

  • Disable

Ldp Bfd Capability

Whether BFD for LDP is enabled:

  • Enable

  • Disable

Bgp Bfd Capability

Whether BFD for BGP tunnel is enabled:

  • Enable

  • Disable

Te Bfd Capability

Whether BFD for Traffic Engineering (TE) is enabled:

  • Enable

  • Disable

Bfd Session Full

Whether the number of created BFD sessions reaches the upper limit:

  • Full: The number of created BFD sessions reached the upper limit.

  • Not-full: The number of created BFD sessions is lower than the upper limit.

Bfd Clearing

Whether BFD is disabled globally:

  • Yes

  • No

Lsp Type

LSP type

Min-Val

Minimum number of supported LSPs specified in the license file.

Max-Val

Maximum number of supported LSPs specified in the license file.

Avail-Val

Average number of supported LSPs specified in the license file.

Created

Number of established LSPs.

display mpls graceful-restart

Function

The display mpls graceful-restart command displays graceful restart (GR) information about all protocols related to MPLS.

Format

display mpls graceful-restart

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

When MPLS is used together with other protocols, run the display mpls graceful-restart command to view GR information about protocols related to MPLS, including the GR status, GR start time, and GR type.

Example

# Display GR information related to all protocols.

<HUAWEI> display mpls graceful-restart
Protocol       GR state       GR start time            GR type
LDP            Normal         -                        -
CRLDP          Normal         -                        -
RSVP           Normal         -                        -
BGP            Normal         -                        -
L3VPN          Normal         -                        -
STATIC         Normal         -                        -
CRSTATIC       Normal         -                        -
BGP IPV6       Normal         -                        -
STATIC HA      Normal         -                        -
L3VPN IPV6     Normal         -                        -
STATIC TP      Normal         -                        -
Table 9-10  Description of the display mpls graceful-restart command output

Item

Description

Protocol

Protocol type:

LDP, CRLDP, RSVP, BGP, L3VPN, STATIC, CRSTATIC, BGP IPV6, STATIC HA, L3VPN IPV6, and STATIC TP.

GR state

GR status of a protocol:

  • Restarting: The protocol is in the GR process.
  • Normal: The protocol is not in the GR process.

GR start time

Time when the GR process starts

When the GR process does not start, a hyphen (-) is displayed.

GR type

GR type:

  • System restart: indicates the system GR.
  • Protocol restart: indicates the protocol GR.

When the GR process does not start, a hyphen (-) is displayed.

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 Specifies the type and number of an interface. -
verbose Displays detailed information about the interface enabled with MPLS. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

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

Example

# Display information about all MPLS-enabled interfaces.

<HUAWEI> display mpls interface
Interface             Status    TE Attr   LSP Count  CRLSP Count Effective MTU
Vlanif100               Up        Dis       2          0           1500
Table 9-11  Description of the display mpls interface command output

Item

Description

Interface

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 the interface.

  • En: MPLS TE is enabled on the interface.

LSP Count

Number of LSPs established on an interface.

CRLSP Count

Number of CR-LSPs established on an interface.

Effective MTU

MPLS 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.

To set the MPLS MTU, run the mpls mtu command.

To set the interface MTU, run the mtu (Interface view) command.

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

<HUAWEI> display mpls interface vlanif 100 verbose
No                    :  1
Interface             :  Vlanif100
Status                :  Up
TE Attribute          :  Disable 
Static LSPCount       :  0
Static CR-LSPCount    :  0
LDP LSPCount          :  0
RSVP LSPCount         :  0
MPLS MTU              :  -
Interface MTU         :  1500
Effective MTU         :  1500
TE FRR                :  Disable
Interface Index       :  0xd1  
Table 9-12  Description of the display mpls interface verbose command output

Item

Description

No

Serial number.

Interface

The interface enabled with MPLS.

Status

Interface status:
  • Up

  • Down

TE Attribute

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

  • Enable: MPLS TE is enabled on the interface.

Static LSPCount

Number of static LSPs established on the interface.

Static CR-LSPCount

Number of static CR-LSPs established on the interface.

LDP LSPCount

Number of LDP LSPs created on the interface.

RSVP LSPCount

Number of RSVP-TE LSPs established on the interface.

MPLS MTU

MPLS MTU value configured using the mpls mtu command.

When no MPLS MTU is set, a hyphen (-) is displayed.

Interface MTU

MTU value configured on an interface.

To set the interface MTU, run the mtu (Interface view) command.

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.

To set the MPLS MTU, run the mpls mtu command.

To set the interface MTU, run the mtu (Interface view) command.

TE FRR

Whether the TE FRR is enabled or disabled on the interface:
  • Disable: No bypass tunnel is set up in manual FRR mode to protect the interface.

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

Interface Index

Interface index value.

Related Topics

display mpls label static available

Function

The display mpls label static available command displays information about labels available for transmitting static services.

Format

display mpls label static available [ [ label-from label-index ] label-number label-number ]

Parameters

Parameter Description Value
label-from label-index Specifies the start label value. The value is an integer ranging from 16 to 1023.
label-number label-number Specifies the number of the required labels. The value is an integer ranging from 1 to 1008.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

By default, the system reserves separate label spaces for dynamic and static services, allowing labels for dynamic and static services to be stored in separate spaces.

Before specifying a label for static services, ensure that the specified label is available. You can run the display mpls label static available command to view labels for static services.

In the command output, a dash is used to specify a range. For example, labels 1000, 1001, and 1002 are displayed as 1000-1002.

Follow-up Procedure

Labels displayed in the command output can be allocated for static services.

Example

# Display information about labels available for transmitting static services.

<HUAWEI> display mpls label static available
16-1023

display mpls label-stack ilm inlabel

Function

The display mpls label-stack ilm inlabel command displays information about the label stack for packets with a specified incoming label.

Format

display mpls label-stack ilm inlabel in-label

Parameters

Parameter Description Value
in-label Specifies the incoming label for the packets about which label-stack information is to be displayed. The value is an integer ranging from 16 to 1048575.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

You can run this command to query information about the outgoing label stack for packets based on the incoming label. The supported public network tunnels include static LSP tunnels, LDP LSPs, dynamic TE tunnels, and static TE tunnels. This command cannot be used in the following situations:

  • Tunnels overlap.
  • Tunnels load-balance traffic.
  • The primary and secondary SPE egresses are used.
  • Traffic is iterated to a ring network.
  • Layer 3 labels are used.

Example

# Display the outgoing label, outbound interface, and tunnel type in the packets with the incoming label value of 1028.

<HUAWEI> display mpls label-stack ilm inlabel 1028
Label-stack  : 1
Level        : 1
Type         : LDP
Label        : 1025
OutInterface : Vlanif111
Table 9-13  Description of the display mpls label-stack ilm inlabel command output

Item

Description

Label-stack

Number of label stacks

Level

Number of labels

Type

Tunnel type

Label

Value of the outgoing label

OutInterface

Outbound interface

display mpls last-info lsp-down

Function

The display mpls last-info lsp-down command displays information about LSPs in Down state.

Format

display mpls last-info lsp-down [ protocol ldp ] [ verbose ]

Parameters

Parameter Description Value
protocol ldp Displays information about LSPs in Down state. -
verbose Displays detailed information about LDP LSPs. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

If LSPs fail and enter the Down state, run the display mpls last-info lsp-down command to view the faults that cause the latest 64 LSPs to go Down.

Example

# Display brief information about LDP LSPs that just enter the Down state.

<HUAWEI> display mpls last-info lsp-down
-------------------------------------------------------------------------------
                 LDP LSP Information: Host Address
-------------------------------------------------------------------------------
FEC                In/Out Label  Out Interface       Down Reason
10.12.12.12/32     1029/3        vlanif10            route changed
10.12.12.12/32     NULL/3        vlanif10            route changed
10.11.11.11/32     1034/3        vlanif10            cannot recovery from GR
10.11.11.11/32     NULL/3        vlanif10            cannot recovery from GR
10.11.11.11/32     1033/3        vlanif10            DS lost
10.11.11.11/32     NULL/3        vlanif10            DS lost
Table 9-14  Description of the display mpls last-info lsp-down command output

Item

Description

FEC

Forwarding equivalence class.

In/Out Label

Values of the incoming and outgoing labels.

Out Interface

Outbound interface.

Down Reason

LSPs go Down due to the following causes:
  • route changed: A route was changed.

  • adjacency changed: An adjacency was changed.

  • cannot recovery from GR: The LDP LSP failed to be reestablished during GR.

  • recv release msg: A Release message was received.

  • recv withdraw msg: A Withdraw message was received.

  • US lost: The session with the upstream node went Down.

  • DS lost: The session with the downstream node went Down.

  • policy changed: The policy to establish LSPs was changed (Generally, configurations of the policy was changed).

  • reach paf limit: PAF resources are insufficient.

  • GR aging: The LSP aged after GR.

  • others

# Display detailed information about LDP LSPs that just enter the Down state.

<HUAWEI> display mpls last-info lsp-down protocol ldp verbose
-------------------------------------------------------------------------------
                 LDP LSP Information: Host Address
-------------------------------------------------------------------------------
  No                  :  1
  VrfIndex            :
  Fec                 :  10.1.1.1/32
  Nexthop             :  127.0.0.1
  In-Label            :  3
  Out-Label           :  NULL
  Out-Interface       :  vlanif13
  LspIndex            :  6144
  Token               :  0x0
  LsrType             :  Egress
  Outgoing token      :  0x0
  Label Operation     :  POP
  Down Time           :  2011/11/08 16:39:59+08:00
  Exist time          :  14sec
  Down Reason         :  policy changed

  No                  :  2
  VrfIndex            :
  Fec                 :  10.2.2.2/32
  Nexthop             :  10.1.2.2
  In-Label            :  NULL
  Out-Label           :  3
  Out-Interface       :  vlanif13
  LspIndex            :  6146
  Token               :  0x1
  LsrType             :  Ingress
  Outgoing token      :  0x0
  Label Operation     :  PUSH
  Down Time           :  2011/11/08 16:51:26+08:00
  Exist time          :  5sec
  Down Reason         :  route changed
Table 9-15  Description of the display mpls last-info lsp-down protocol ldp verbose command output

Item

Description

No

Record No.

VrfIndex

Index of a VRF instance.

Fec

Forwarding equivalence class.

Nexthop

Next hop IP address.

In-Label

Value of the incoming label.

Out-Label

Value of the outgoing label.

Out-Interface

Outbound interface.

LspIndex

Index of an LSP.

Token

Token value, in the hexadecimal format.

LsrType

Type of an LSR on an LSP, which can be ingress, transit, or egress.

Outgoing token

Outgoing token value, in the hexadecimal format.

Label Operation

Label operation, which can be PUSH, POP, SWAP, or SWAPPUSH.

Down Time

Time when an LSP goes Down.

Exist time

Existing period of an LDP LSP, in seconds.

Down Reason

LSPs go Down due to the following causes:
  • route changed: A route was changed.

  • adjacency changed: An adjacency was changed.

  • cannot recovery from GR: The LDP LSP failed to be reestablished during GR.

  • recv release msg: A Release message was received.

  • recv withdraw msg: A Withdraw message was received.

  • US lost: The session with the upstream node went Down.

  • DS lost: The session with the downstream node went Down.

  • policy changed: The policy to establish LSPs was changed (Generally, configurations of the policy was changed).

  • reach paf limit: PAF resources are insufficient.

  • GR aging: The LSP aged after GR.

  • others

display mpls ldp

Function

The display mpls ldp command displays global LDP configurations.

Format

display mpls ldp [ all ] [ verbose ]

Parameters

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

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

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.

Prerequisites

MPLS has been enabled globally using the mpls command, and MPLS LDP has been enabled globally using the mpls ldp command.

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
 Capability-Announcement : On             Longest-match         : Off
 mLDP P2MP Capability    : Off            mLDP MBB Capability   : Off  
 mLDP MP2MP Capability   : Off 
                           LDP Instance Information
 ------------------------------------------------------------------------------
 Instance ID             : 0              VPN-Instance          :
 Instance Status         : Active         LSR ID                : 10.1.1.1
 Loop Detection          : Off            Path Vector Limit     : 32
 Label Distribution Mode : Ordered
 Label Retention Mode    : Liberal(DU)/Conservative(DOD)
 Instance Deleting State : No             Instance Reseting State : No
 Graceful-Delete         : Off            Graceful-Delete Timer : 5 Sec
 ------------------------------------------------------------------------------
Table 9-16  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.

To set the timeout period of the GR Neighbor-liveness timer, run the graceful-restart timer neighbor-liveness command.

Graceful Restart

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

  • Off: GR is disabled.

To enable LDP GR, run the graceful-restart (MPLS-LDP view) command.

FT Reconnect Timer

Timeout period of the GR reconnect timer.

To set the timeout period of the GR reconnect timer, run the graceful-restart timer reconnect command.

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.

To set the MTU signaling, run the mtu-signalling command.

Recovery Timer

Timeout period of the GR Recovery timer.

To set the timeout period of the GR Recovery timer, run the graceful-restart timer recovery command.

Capability-Announcement

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

  • Off: LDP dynamic capability announcement is disabled.

NOTE:

The switch does not support this parameter.

Longest-match

Status of LDP extension for inter-area LSP:
  • On: LDP extension for inter-area LSP is enabled.

  • Off: LDP extension for inter-area LSP is disabled.

To set the status of LDP extension for inter-area LSP, run the longest-match command.

mLDP P2MP Capability

Whether mLDP P2MP is globally enabled:

  • On: mLDP P2MP is enabled globally.

  • Off: mLDP P2MP is disabled globally.

NOTE:

The switch does not support this parameter.

mLDP MBB Capability

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

  • On: mLDP make-before-break is enabled.

  • Off: mLDP make-before-break is disabled.

NOTE:

The switch does not support this parameter.

mLDP MP2MP Capability

Whether multipoint extensions for LDP (mLDP) multipoint-to-multipoint (MP2MP) is globally enabled:

  • On: mLDP MP2MP is enabled globally.

  • Off: mLDP MP2MP is disabled globally.

NOTE:

The switch does not support this parameter.

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.

The default name is null.

NOTE:

The switch does not support this parameter.

Instance Status

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

  • NotInService: The instance is in the NotInService state temporarily due to certain operations. For example, after the reset mpls ldp or graceful-restart command is used, the instance is unavailable temporarily.

  • 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.

Loop Detection

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

  • Off: Loop detection is disabled.

To set the status of the loop detection, run the loop-detect command.

Path Vector Limit

Path vector limit for loop detection.

To set the path vector limit for loop detection, run the path-vectors command.

Label Distribution Mode

Label distribution mode:
  • Ordered

  • Independent

Currently, the switch supports only the ordered mode.

Label Retention Mode

  • If label advertisement mode is DU, label retention mode will be Liberal.
  • If label advertisement mode is DOD, label retention mode will be Conservative.

Instance Deleting State

Deletion status of an instance:
  • Yes: The instance is being deleted.

  • No: The instance is not being deleted.

Instance Reseting State

Resetting status of an instance:
  • Yes: The instance is being reset.

  • No: The instance is not being reset.

Graceful-Delete

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

  • Off: disables graceful deletion.

NOTE:

The switch does not support this parameter.

Graceful-Delete Timer

Value of the Graceful-delete Timer, in seconds.

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 the 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 in Public Network
 Codes: R: Remote Adjacency, L: Local Adjacency
 A '*' before an adjacency means the adjacency is being deleted.
 ------------------------------------------------------------------------------
 SN   SourceAddr      PeerID          VrfID AdjAge(DDDD:HH:MM) RcvdHello Type
 ------------------------------------------------------------------------------
  1   10.1.2.2        2.2.2.2         0      0000:00:22        527       L
  2   10.2.3.3        3.3.3.3         0      0000:00:20        254       L
  3   3.3.3.3         3.3.3.3         0      0000:00:18        79        R
 ------------------------------------------------------------------------------
 TOTAL: 3 Record(s) found.  
Table 9-17  Description of the display mpls ldp adjacency command output

Item

Description

SN

Serial number.

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 in Public Network
 ------------------------------------------------------------------------------
                           LDP Peer ID : 3.3.3.3
                      VPNInstance name : -
                            CreateDate : 2005-07-27
                            CreateTime : 11:15:41+08:00
                         Adjacency Age : 0000:03:44
                         AdjacencyType : Remote Adjacency
                      Discovery-Source : -
                    UDP Source Address : 3.3.3.3
                         UDP Socket ID : 33
                          Sequence No. : 0
   Configuration Hello Hold Timer(sec) : 45
                    Hello Message Rcvd : 899
             Adjacency Deletion Status : No
 ------------------------------------------------------------------------------
 TOTAL: 1 Adjacency(s) found. 
Table 9-18  Description of the display mpls ldp adjacency remote peer command output

Item

Description

LDP Peer ID

LSR ID of an LDP peer.

VPNInstance name

Name of a VPN instance.

NOTE:

The switch does not support this parameter.

CreateDate

Creation date of an LDP adjacency.

CreateTime

Creation time of an LDP adjacency.

Adjacency Age

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

AdjacencyType

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 No

Serial number carried in the received Hello message.

The default value is 0.

Configuration Hello Hold Timer(sec)

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 Rcvd

Number of Hello messages received by an LDP adjacency.

Adjacency Deletion Status

Deletion status of an LDP adjacency:
  • Yes: The LDP adjacency is being deleted.
  • No: The LDP adjacency is not being deleted.
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 9-19  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 | udp | l2vpn } [ number ]

Parameters

Parameter Description Value
tcp Displays information about TCP error messages related to LDP sessions. -
udp Displays information about UDP error messages related to LDP sessions. -
l2vpn Displays information about L2VPN error messages related to LDP sessions. -
number Specifies the number of LDP-related error messages to be displayed. The value is an integer ranging from 1 to 100.

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 UDP packets related to LDP.

<HUAWEI> display mpls ldp error packet udp

  LDP Error UDP Packet  
  Total received error packet number: 58
  Record error packet number        : 10
  Max Record error packet number    : 10
------------------- Number 1 ----------------------  
  Date&Time         : 2011-11-08 16:39:59+08:00
  Error Reason      : unknown  
  Interface         : Vlanif100
  Instance ID       : 0  
  Message Type      : Hello
  Length            : 34
  Packet content    :
  01 64 00 14 00 00 00 32 04 00 00 04 00 0f 00 00
  04 01 00 04 01 01 01 01 00 00 00 00 00 00 00 00
  00 00
Table 9-20  Description of the display mpls ldp error packet command output

Item

Description

Total received error packet number

Number of received error messages related to LDP sessions.

Record error packet number

Number of recorded error messages related to LDP sessions.

Max Record error packet number

Maximum number of error messages that can be recorded.

Date&Time

Date and time when an error message was received.

Error Reason

Cause for an error.

Interface

An interface that receives the message.

Instance ID

ID of an LDP instance to which the error message belongs.

Message Type

Message type, which includes but is not limited to the following:

  • Address
  • Address Withdraw
  • Capability
  • Hello
  • Initialization
  • KeepAlive
  • Label Request
  • Label Mapping
  • Label Withdraw
  • Label Release
  • Label Abort Request
  • Notification
  • Unknown

Length

Length of the error message

Packet content

Contents of the error message in the binary format.

display mpls ldp error packet state

Function

The display mpls ldp error packet state command displays the record status of LDP-related error messages.

Format

display mpls ldp error packet state

Parameters

None

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 state command to view the record status of UDP, TCP, and L2VPN error messages related to LDP sessions.

Example

# Display the record status of LDP-related error messages.

<HUAWEI> display mpls ldp error packet state
--------------------------------------------
  Error UDP packet state            : ON
  Max UDP error packet number       : 100
  Current UDP error packet number   : 0
  Error TCP packet state            : ON
  Max TCP error packet number       : 100
  Current TCP error packet number   : 0
  Error L2VPN packet state          : ON
  Max L2VPN error packet number     : 100
  Current L2VPN error packet number : 0
-------------------------------------------- 
Table 9-21  Description of the display mpls ldp error packet state command output

Item

Description

Error UDP packet state

Whether or not UDP error messages can be detected and recorded:
  • ON: UDP error message detection is enabled.
  • OFF: UDP error message detection is disabled.

Max UDP error packet number

Maximum number of UDP error messages that can be recorded.

Current UDP error packet number

Number of recorded UDP error messages.

Error TCP packet state

Whether or not TCP error messages can be detected and recorded:
  • ON: TCP error message detection is enabled.
  • OFF: TCP error message detection is disabled.

Max TCP error packet number

Maximum number of TCP error messages that can be recorded.

Current TCP error packet number

Number of recorded TCP error messages.

Error L2VPN packet state

Whether or not L2VPN error messages can be detected and recorded:
  • ON: L2VPN error message detection is enabled.
  • OFF: L2VPN error message detection is disabled.

Max L2VPN error packet number

Maximum number of L2VPN error messages that can be recorded.

Current L2VPN error packet number

Number of recorded L2VPN error messages.

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
 ------------------------------------------------------------------------
 PeerID            Down       Down                   Duration      Reason
                   Date       Time                   Time
 ------------------------------------------------------------------------
 2.2.2.2:0         2012-04-24 17:08:59+08:00         0h44m54s      C            
 2.2.2.2:0         2012-04-26 15:43:54+08:00         46h34m54s     A            
 -----------------------------------------------------------------------------
 TOTAL: 2 Record(s) Found.
 A : The Adjacency is down because Hello Timer Expired.
 C : The administrator configuration to trigger.
 D : The Adjacency is down because delay-deleting timer expired.
 P : The Adjacency is down because the peer is being deleted.
 O : Other reason.
Table 9-22  Description of the display mpls ldp event adjacency-down command output
Item Description
PeerID LSR ID of an LDP peer.
Down Date Date when an LDP adjacency went Down.
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 Hello timer expires.
  • C: The configuration is changed.
  • D: The delay deleting timer expires.
  • P: The peer is deleted.
  • 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                                
 VrfID                                 : 0                                      
 DownDate                              : 2012-04-24
 DownTime                              : 17:08:59+08:00                           
 DurationTime                          : 0h44m54s                               
 MaxInterval(sec)                      : 5                                      
 Reason                                : configuration to trigger               
 Type                                  : Local Adjacency                        
 DiscoverySource                       : Vlanif60                              
 -------------------------------------------------------------------------------
 SN                                    : 2                                      
 PeerID                                : 2.2.2.2                                
 VrfID                                 : 0                                      
 DownDate                              : 2012-04-26
 DownTime                              : 15:43:54+08:00
 DurationTime                          : 46h34m54s                              
 MaxInterval(sec)                      : 6                                      
 Reason                                : Hello Timer Expired                    
 Type                                  : Local Adjacency                        
 DiscoverySource                       : Vlanif60
 -------------------------------------------------------------------------------
  TOTAL: 2 Record(s) Found. 
Table 9-23  Description of the display mpls ldp event adjacency-down verbose command output
Item Description

SN

Serial number.

PeerID

LSR ID of an LDP peer.

VrfID

ID of a VPN instance.

DownDate

Date when an LDP adjacency went Down.

DownTime

Time when an LDP adjacency went Down.

DurationTime

Time elapsed since an LDP adjacency established.

MaxInterval (sec)

Maximum interval for sending a Hello message.

Reason

Reason for the LDP adjacency Down event:
  • A: The Hello timer expires.
  • C: The configuration is changed.
  • D: The delay deleting timer expires.
  • P: The peer is deleted.
  • O: other causes.

Type

Adjacency type:
  • Local Adjacency: Directly connected adjacency.
  • Remote Adjacency: Indirectly connected adjacency.

DiscoverySource

Interface where an LDP peer is discovered.

display mpls ldp event gr-helper

Function

The display mpls ldp event gr-helper command displays GR Helper information.

Format

display mpls ldp event gr-helper [ all | peer-id ]

Parameters

Parameter Description Value
all Displays information about all GR Helpers. -
peer-id Displays information about a GR Helper on a specified LDP peer. The value is in dotted decimal notation.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

If GR Helpers are configured, run the display mpls ldp event gr-helper command to view GR Helper information.

Example

# Display GR Helper information.

<HUAWEI> display mpls ldp event gr-helper
  LDP GR-Helper Peer Info
 --------------------------------------------------------------------
 LDP InstanceId             : 0          Vpn Instance Name:
 Peer ID                    : 1.1.1.1
 Label Advertisement Mode   : Downstream Unsolicited
 Timer State                :
 Recovery Timer Left        : 229(s)
 Peer Gr Timer Configuration:
 Reconnect Timer            : 300(s)     Recovery Timer   : 300(s)
 Stale Lsp State            :
 USCB Counter               : 3          DSCB Counter     : 3
 --------------------------------------------------------------------
 Total GR Peer Counter: 1
Table 9-24  Description of the display mpls ldp event gr-helper command output

Item

Description

LDP InstanceId

LDP instance name.

Vpn Instance Name

VPN instance name.

NOTE:

The device does not support this parameter.

Peer ID

LSR ID of an LDP peer.

Label Advertisement Mode

Mode used by LDP to advertise labels.

To set the mode used by LDP to advertise labels, run the mpls ldp advertisement command.

Timer State

Status of the timer.

Recovery Timer Left

Remaining time before an LSP starts to be reestablished.

Peer Gr Timer Configuration

Confiugration of the GR timers.

Reconnect Timer

Value of the LDP session reconnection timer.

To set the value of the LDP session reconnection timer, run the graceful-restart timer reconnect command.

Recovery Timer

Value of the LSP recovery timer.

To set the value of the LSP recovery timer, run the graceful-restart timer recovery command.

Stale Lsp state

Status of the primary LSP.

USCB Counter

Number of upstream control blocks (USCBs).

DSCB Counter

Number of downstream control blocks (DSCBs).

Total GR Peer Counter

Number of GR Helper.

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

Parameters

None

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
------------------------------------------------------------------------------
PeerID      Down       Down             Duration   Flag Reason
            Date       Time             Time
------------------------------------------------------------------------------
10.1.2.9:0  2011-12-15 10:14:11+08:00   0h6m15s    L    Recv Noti(0x000a)

10.1.2.9:0  2011-12-15 10:14:26+08:00   0h6m34s    L    Recv Noti(0x000a)

-------------------------------------------------------------------------------
TOTAL: 2 Record(s) Found.
R: Remote peer.
L: Local peer.
B: Both of local and remote peer.
G: Graceful Restart Session.
Important notification message error code:
  0x0003: Bad PDU Length.
  0x0005: Bad Message Length.
  0x0007: Bad TLV Length.
  0x0009: Hello Hold Timer Expired.
  0x000a: Shutdown.
  0x0014: KeepAlive Timer Expired.
Table 9-25  Description of the display mpls ldp event session-down command output

Item

Description

PeerID

LSR ID of an LDP peer.

Down Date

Date when an LDP session went down.

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.

Important notification message error code

Important notification message error code.

Bad PDU Length

Incorrect PDU length.

Bad Message Length

Incorrect message length.

Bad TLV Length

Incorrect TLV length.

Hello Hold Timer Expired

Hello Hold timer expired.

Shutdown

The peer actively shuts down the session.

KeepAlive Timer Expired

Keepalive timer expired.

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
 Codes:LAM(Label Advertisement Mode), IFName(Interface name)
 A '*' before an interface means the entity is being deleted.
 ------------------------------------------------------------------------------
 IFName         Status       LAM   TransportAddress   HelloSent/Rcv
 ------------------------------------------------------------------------------
Vlanif100        Active       DU    10.1.1.1            29574/29539
 ------------------------------------------------------------------------------
Table 9-26  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.

To set the label advertisement mode, run the mpls ldp advertisement command.

TransportAddress

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

HelloSent/Rcv

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         : 10.1.1.1:0             Transport Address : 10.1.1.1
 Entity Status  : Active                Effective MTU : 1500

 Configured Hello Hold Timer     : 15 Sec
 Negotiated Hello Hold Timer     : 15 Sec
 Configured Hello Send Timer     : 2 Sec
 Configured Keepalive Hold Timer : 45 Sec
 Configured Keepalive Send Timer : 3 Sec
 Configured Delay Timer          : 10 Sec
 Label Advertisement Mode        : Downstream Unsolicited
 Hello Message Sent/Rcvd         : 29913/29878 (Message Count) 
 Entity Deletion Status          : No
 mLDP P2MP Capability            : Disable
 mLDP MP2MP Capability           : Disable
 ------------------------------------------------------------------------------
Table 9-27  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.

To set the timeout period of the Hello hold timer, run the mpls ldp timer hello-hold command.

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.

To set the timeout period of the Hello send timer, run the mpls ldp timer hello-send command.

Configured Keepalive Hold Timer

Timeout period of the configured Keepalive hold timer.

To set the timeout period of the Keepalive hold timer, run the mpls ldp timer keepalive-hold command.

Configured Keepalive Send Timer

Timeout period of the configured Keepalive send timer.

To set the timeout period of the Keepalive send timer, run the mpls ldp timer keepalive-send command.

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

To set the label advertisement mode, run the mpls ldp advertisement command.

Hello Message Sent/Rcvd

Number of sent and received Hello messages.

Entity Deletion Status

Deletion status of an instance:
  • Yes: The instance is being deleted.
  • No: The instance is not being deleted.

mLDP P2MP Capability

Whether mLDP P2MP is enabled:

  • Enable

  • Disable

NOTE:
The switch does not support this function.

mLDP MP2MP Capability

Whether mLDP MP2MP is enabled:

  • Enable

  • Disable

NOTE:
The switch does not support this function.

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        1023            1008
Dynamic            1024      163840          162817
Block            163841      180244           16404
NOTE:

The preceding information is an example. The allocation ranges of labels depend on the actual situation.

Table 9-28  Description of the display mpls label all summary command output

Item

Description

TableType

Label type.

  • Reserved: indicates reserved labels.
  • Static: indicates static labels, mainly for MPLS TE and BGP.
  • Dynamic: indicates dynamic labels, mainly for LDP, MPLS TE, and BGP.
  • Block: indicates block labels, mainly for BGP.

MinValue

Minimum label value.

MaxValue

Maximum label value.

AvailableNum

Number of labels that can be allocated.

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 ] [ peer peer-id ]

display mpls ldp lsp inbound-policy

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.
peer peer-id Specifies the peer ID. The value is in dotted decimal notation.
inbound-policy Displays information about the LSPs that have passed an inbound policy, in addition to information about the LSPs that are established without applying the inbound policy. -

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
 -------------------------------------------------------------------------------
 Flag after Out IF: (I) - LSP Is Only Iterated by RLFA
 -------------------------------------------------------------------------------
 DestAddress/Mask   In/OutLabel    UpstreamPeer    NextHop        OutInterface
 -------------------------------------------------------------------------------
 10.3.3.3/32        3/NULL         10.4.4.9        127.0.0.1       InLoop0
 10.3.3.9/32        3/NULL         10.4.4.9        127.0.0.1       InLoop0
*10.3.3.9/32        Liberal/1024                   DS/10.4.4.9
 10.4.4.9/32        NULL/3         -               172.16.1.2      Vlanif100
 10.4.4.9/32        1029/3         10.4.4.9        172.16.1.2      Vlanif100
 -------------------------------------------------------------------------------
 TOTAL: 4 Normal LSP(s) Found.
 TOTAL: 1 Liberal LSP(s) Found.
 TOTAL: 0 Frr LSP(s) Found.
 A '*' before an LSP means the LSP is not established
 A '*' before a Label means the USCB or DSCB is stale
 A '*' before a UpstreamPeer means the session is stale
 A '*' before a DS means the session is stale
 A '*' before a NextHop means the LSP is FRR LSP 
Table 9-29  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 a 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.

TOTAL: 4 Normal LSP(s) Found.

Total number of normal LSPs.

TOTAL: 1 Liberal LSP(s) Found.

Total number of liberal LSPs.

TOTAL: 0 Frr LSP(s) Found.

Total number of FRR LSPs.

Related Topics

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                                                 
 A '*' before a number means the LSP is for longest-match                       
 ------------------------------------------------------------------------------ 
 VPNInstanceName   Total   Ingress   Transit   Egress   Liberal  FRR            
 ------------------------------------------------------------------------------ 
 -                 14      4         4         3        3        0              
                   *0      *0        *0        *0       *-       *0             
 ------------------------------------------------------------------------------ 
Table 9-30  Description of the display mpls ldp lsp statistics command output

Item

Description

VPNInstanceName

Name of a VPN instance:

  • A hyphen (-) 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 [ [ all ] [ verbose ] | peer-id ]

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
 A '*' before a peer means the peer is being deleted.
 ------------------------------------------------------------------------------
 PeerID                TransportAddress   DiscoverySource
 ------------------------------------------------------------------------------
 2.2.2.2:0             2.2.2.2            Remote Peer : rtb
 3.3.3.3:0             3.3.3.3            Vlanif100
 ------------------------------------------------------------------------------
 TOTAL: 2 Peer(s) Found.
Table 9-31  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         : 2.2.2.2:0
 Peer Max PDU Length : 4096         Peer Transport Address   : 2.2.2.2
 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  
 Peer Discovery Source         : remote peer: rtb 
 Peer Deletion Status          : No
 Capability-Announcement       : Off 
 Peer mLDP P2MP Capability     : Off                                            
 Peer mLDP MBB Capability      : Off    
 ------------------------------------------------------------------------------
 Peer LDP ID         : 3.3.3.3:0
 Peer Max PDU Length : 4096         Peer Transport Address   : 3.3.3.3
 Peer Loop Detection : Off          Peer Path Vector Limit   : ----
 Peer FT Flag        : Off          Peer Keepalive Timer     : 45 Sec
 Recovery Timer      : ----         Reconnect Timer          : ----
 Peer Type           : Local
 Peer Label Advertisement Mode : Downstream Unsolicited 
 Peer Discovery Source         : Vlanif100 
 Peer Deletion Status          : No
 Capability-Announcement       : Off 
 Peer mLDP P2MP Capability     : Off                                            
 Peer mLDP MBB Capability      : Off   
 ------------------------------------------------------------------------------
Table 9-32  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.

To configure the loop detection function, run the loop-detect command.

Peer Path Vector Limit

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

To set the upper limit of the Path Vector for an LDP peer, run the path-vectors command.

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.

To set the value of the Keepalive timer, run the mpls ldp timer keepalive-hold command.

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.

To set the timeout period of the Recovery timer, run the graceful-restart timer recovery command.

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.

To set the timeout period of the Reconnect timer, run the graceful-restart timer reconnect command.

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.

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.

Peer Deletion Status

Deletion status of an LDP peer:
  • Yes: LDP peer is being deleted.
  • No: LDP peer is not being deleted.

Capability-Announcement

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

  • Off: LDP dynamic capability announcement is disabled.

NOTE:

The switch does not support this parameter.

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 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       1        1              2
 ---------------------------------------------------------
Table 9-33  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.

Run the display mpls ldp remote-peer command to view information about the configured remote LDP peer. Different from the display mpls ldp peer command, the display mpls ldp remote-peer command is used to view the remote LDP peer that is configured on the local device if the configuration takes effect. The display mpls ldp peer command is used to view the LDP peer discovered by the local device only when the LDP peers are configured on local and peer devices and the LDP peer relationship is set up.

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          : 10 Sec
 Hello Packet sent/received      : 61/59
 Label Advertisement Mode        : Downstream Unsolicited
 Remote Peer Deletion Status     : No
 Auto-config                     : ---
------------------------------------------------------------------------------
 TOTAL: 1 Peer(s) Found.
Table 9-34  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.

To set the label advertisement mode, run the mpls ldp advertisement command.

Remote Peer Deletion Status

Deletion status of an LDP peer:
  • Yes: The LDP peer is being deleted.
  • No: The LDP peer is not being deleted.

Auto-config

Source that triggers the creation of a remote peer:
  • ---: created using LDP configurations.

  • L2VPN: After an L2VPN is configured, the remote LDP peer is automatically configured. LDP configurations can also be involved.

  • RLFA: created using remote LFA.

  • Auto Accept: The remote LDP session is automatically established after a local device receives Targeted Hello messages.

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 ] ]

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

Usage Scenario

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.

Prerequisites

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

Precautions

If you run the display mpls ldp session command without specifying any parameter, information about all LDP sessions is displayed.

Example

# Display information about all LDP sessions.

<HUAWEI> display mpls ldp session
 LDP Session(s) in Public Network
 Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
 A '*' 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 9-35  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.

To set the label advertisement mode, run the mpls ldp advertisement command.

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      : 2.2.2.2:0            Local LDP ID    : 1.1.1.1:0
 TCP Connection   : 1.1.1.1 <- 2.2.2.2
 Session State    : Operational          Session Role    : Passive
 Session FT Flag  : Off                  MD5 Flag        : Off
 Reconnect Timer  : ---                  Recovery Timer  : ---
 Keychain Name    : kc1
 Authentication applied:---

 Negotiated Keepalive Hold Timer   : 45 Sec
 Configured Keepalive Send Timer   : 3 Sec
 Keepalive Message Sent/Rcvd       : 438/438 (Message Count)
 Label Advertisement Mode          : Downstream Unsolicited
 Label Resource Status(Peer/Local) : Available/Available
 Session Age                       : 0000:01:49 (DDDD:HH:MM)
 Session Deletion Status           : No

 Capability:
  Capability-Announcement           : On
  mLDP P2MP Capability              : Off 
  mLDP MP2MP Capability             : Off
  mLDP MBB Capability               : Off 

 Outbound&Inbound Policies applied : NULL 

 Addresses received from peer: (Count: 3)
 10.1.1.2            2.2.2.2             10.1.2.1
 ------------------------------------------------------------------------------
Table 9-36  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 Session 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 Session FT Flag field is On.

Keychain Name

Referenced keychain authentication name.

Authentication applied

Existing authentication mode:

  • Peer: single peer authentication

  • Peer-group PeerGroupName: peer-group authentication. PeerGroupName indicates a peer group name.

  • ALl: All authentication

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).

To set the label advertisement mode, run the mpls ldp advertisement command.

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.

Session Deletion Status

Deletion status of an LDP session:
  • Yes: The LDP session is being deleted.
  • No: The LDP session is not being deleted.

Capability

LDP capability.

Capability-Announcement

LDP dynamic capability announcement function:
  • On: LDP dynamic capability announcement is enabled.

  • Off: LDP dynamic capability announcement is disabled.

NOTE:

The switch does not support this parameter.

mLDP P2MP Capability

Whether mLDP P2MP is supported after a session is negotiated:

  • On: mLDP P2MP is supported.

  • Off: mLDP P2MP is not supported.

NOTE:

The switch does not support this parameter.

mLDP MP2MP Capability

Whether mLDP MP2MP is supported after a session is negotiated:

  • On: mLDP MP2MP is supported.

  • Off: mLDP MP2MP is not supported.

NOTE:

The switch does not support this parameter.

mLDP MBB Capability

Whether mLDP make-before-break is supported after a session is negotiated:

  • On: mLDP make-before-break is supported.

  • Off: mLDP make-before-break is not supported.

NOTE:

The switch does not support this parameter.

Outbound&Inbound Policies applied

Outbound and inbound policies on the local node.

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       1        1              2
 ------------------------------------------------------------
 SessionStatistics   0       1        1              2
 ------------------------------------------------------------
Table 9-37  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 lsp

Function

The display mpls lsp command displays information about LSPs.

The display mpls lsp lsp-id command displays information about CR-LSPs only.

Format

display mpls lsp lsp-id ingress-lsr-id session-id lsp-id [ verbose ]

display mpls lsp [ [ vpn-instance vpn-instance-name [ ipv4-family | ipv6-family ] ] [ protocol { bgp | bgp-ipv6 | rsvp-te | static | static-cr } ] | asbr ] [ { exclude | include } ip-address mask-length ] [ incoming-interface interface-type interface-number ] [ outgoing-interface interface-type interface-number ] [ in-label in-label-value ] [ out-label out-label-value ] [ nexthop ip-address ] [ lsr-role { egress | ingress | transit } ] [ verbose ]

display mpls lsp [ vpn-instance vpn-instance-name [ ipv4-family | ipv6-family ] ] protocol ldp [ { exclude | include } ip-address mask-length ] [ outgoing-interface interface-type interface-number ] [ in-label in-label-value ] [ out-label out-label-value ] [ nexthop ip-address ] [ lsr-role { egress | ingress | transit } ] [ verbose ]

display mpls lsp stale-incoming-interface interface-index [ outgoing-interface interface-type interface-number ] [ in-label in-label-value ] [ out-label out-label-value ] [ nexthop ip-address ] [ lsr-role { egress | ingress | transit } ] [ verbose ]

display mpls lsp stale-outgoing-interface interface-index [ in-label in-label-value ] [ out-label out-label-value ] [ nexthop ip-address ] [ lsr-role { egress | ingress | transit } ] [ verbose ]

Parameters

Parameter Description Value
lsp-id Specifies the LSP ID. The value is an integer ranging from 0 to 65535.
ingress-lsr-id Specifies the ID of the ingress LSR. The value is in dotted decimal notation.
session-id Specifies the ID of a session. The value is an integer ranging from 0 to 65535.
vpn-instance vpn-instance-name Displays detailed configurations of LSPs of a specified VPN instance.

The value must be an existing VPN instance name.

ipv4-family Indicates the IPv4 unicast address-family. -
ipv6-family Indicates the IPv6 unicast address-family. -
protocol Displays information about LSPs of a specified type. -
ldp Indicates LDP. -
bgp Indicates BGP. -
bgp-ipv6 Indicates BGP IPv6. -
rsvp-te Indicates RSVP-TE. -
static Indicates Static. -
static-cr Indicates Static-CR. -
asbr Displays information about LSPs of a specified ASBR. -
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 or a specified IPv6 address. The value is in dotted decimal notation.
mask-length Specifies the mask length of the specified IPv4 address or a specified IPv6 address. The value is an integer ranging from 0 to 32. Alternatively, it specifies the mask length of the specified IPv6 address. The value is an integer ranging from 0 to 128.
incoming-interface interface-type interface-number Specifies the type and number of an inbound interface. You can view the configuration of an LSP on a specified interface. -
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.
out-label out-label-value Displays information about LSPs of a specified outgoing label. The value is an integer ranging from 0 to 1048575.
nexthop ip-address Displays information about LSPs of a specified IPv4 or IPv6 next hop 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. -
stale-incoming-interface Displays information about the stale inbound interface of an LSP. -
stale-outgoing-interface Displays information about the stale outbound interface of an LSP. -
interface-index Specifies the index of a specified stale interface. The value is a hexadecimal integer ranging from 1 to FFFFFFFE.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

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

Run the display mpls stale-interface command without specifying a parameter to view the index of a stale interface.

Example

# Display information about all types of LSPs.

<HUAWEI> display mpls lsp
-------------------------------------------------------------------------------
                 LSP Information: RSVP LSP
-------------------------------------------------------------------------------
  FEC                In/Out Label  In/Out IF                      Vrf Name
  10.2.2.9/32        NULL/11264    -/Vlanif10

Flag after Out IF: (I) - LSP Is Only Iterated by RLFA
-------------------------------------------------------------------------------
                 LSP Information: LDP LSP
-------------------------------------------------------------------------------
  FEC                In/Out Label  In/Out IF                      Vrf Name

  10.2.2.9/32        NULL/3        -/Vlanif10
  10.2.2.9/32        1024/3        -/Vlanif10
  10.3.3.9/32        NULL/3        -/Vlanif20
  10.3.3.9/32        1025/3        -/Vlanif20

# Display information about all LSPs with the next hop of 192.168.1.1.

<HUAWEI> display mpls lsp nexthop 192.168.1.1

Flag after Out IF: (I) - LSP Is Only Iterated by RLFA
-------------------------------------------------------------------------------
            LSP Information: L3VPN Label-Per-Nexthop LSP                        
-------------------------------------------------------------------------------
IndirectID  NextHop            In/Out Label  In/Out IF      Vrf Name            
0x1         192.168.1.1        13312/13312   -/-            ASBR LSP            

# Display detailed information about all types of LSPs.

<HUAWEI> display mpls lsp verbose
-------------------------------------------------------------------------------
                 LSP Information: RSVP LSP
-------------------------------------------------------------------------------

  No                  :  1
  SessionID           :  300
  IngressLsrID        :  10.1.1.9
  LocalLspID          :  1
  Tunnel-Interface    :  Tunnel1
  Fec                 :  10.2.2.9/32
  TunnelTableIndex    :  0x1
  Nexthop             :  10.5.1.2
  In-Label            :  NULL
  Out-Label           :  11264
  In-Interface        :  ----------
  Out-Interface       :  Vlanif10
  LspIndex            :  3072
  Token               :  0x8002008
  LsrType             :  Ingress
  Mpls-Mtu            :  1500
  TimeStamp           :  1171sec
  Bfd-State           :  ---       
  CBfd-Event          :  0x0 
  Bed-State           :  ---
  Bed-LastNotifyValue :  ---
  Bed-LastNotifyLspId :  ---
  Flag after FEC: (I) - LSP Is Only Iterated by RLFA
-------------------------------------------------------------------------------
                 LSP Information: LDP LSP
-------------------------------------------------------------------------------
  No                  :  2
  VrfIndex            :
  Fec                 :  10.2.2.2/32
  Nexthop             :  10.1.1.2
  In-Label            :  NULL
  Out-Label           :  3
  In-Interface        :  ----------
  Out-Interface       :  Vlanif10
  LspIndex            :  9217
  Token               :  0x802009
  FrrToken            :  0x0
  LsrType             :  Ingress
  Outgoing token      :  0x0
  Label Operation     :  PUSH
  Mpls-Mtu            :  ------
  TimeStamp           :  21086sec
  Bfd-State           :  ---
  BGPKey              :  -----

  No                  :  3
  VrfIndex            :
  Fec                 :  10.2.2.2/32
  Nexthop             :  10.2.1.2
  In-Label            :  NULL
  Out-Label           :  3
  In-Interface        :  ----------
  Out-Interface       :  Vlanif20
  LspIndex            :  9218
  Token               :  0x80200a
  FrrToken            :  0x0
  LsrType             :  Ingress
  Outgoing token      :  0x0
  Label Operation     :  PUSH
  Mpls-Mtu            :  ------
  TimeStamp           :  19569sec
  Bfd-State           :  ---   
  BGPKey              :  -----
Table 9-38  Description of the display mpls lsp command output

Item

Description

LSP Information

LSP information:
  • STATIC LSP: manually created.

  • LDP LSP: created using LDP.

  • STATIC CR-LSP: a static MPLS TE tunnel created manually.

  • RSVP LSP: an MPLS TE tunnel created using RSVP-TE.

  • 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.

  • BGP IPV6 LSP: an LSP based on private-network IPv6 routes received by means of BGP.

  • L3VPN IPV6 LSP: an LSP based on IPv6 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.

IndirectID

Index of the next hop of a BGP route.

No

Serial number of an LSP.

SessionID

Session ID of a CR-LSP.

IngressLsrID

Ingress LSR ID of a CR-LSP.

LocalLspID

Local LSP ID of a CR-LSP.

Tunnel-Interface

Tunnel interface.

VrfIndex

Index of a VPN instance. This value is available for only non-CR-LSPs.

Nexthop

IP address of the next hop of an LSP.

TunnelTableIndex

Index of a tunnel table.

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.

LspIndex

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

Token

LSP token. It guides the packet forwarding.

FrrToken

Token of a standby LDP LSP. This value is available for only non-CR-LSPs.

LsrType

Role of an LSR on an LSP:

  • Ingress

  • Transit

  • Egress

Outgoing token

Token that guides the packet forwarding, which is available for only non-CR-LSPs.

Label Operation

Type of a label operation, which is available for only non-CR-LSPs:

  • PUSH

  • SWAP

  • POP

  • SWAPPUSH

Mpls-Mtu

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

TimeStamp

Time elapsed since an LSP was set up.

Bfd-State

BFD status.

CBfd-Event

Error code event that BFD reports to the RSVP LSP on the ingress node.

Bed-State

Error code status of an RSVP LSP on the ingress node.

Bed-LastNotifyValue

Error code association of which the RSVP LSP notifies BFD on the egress node.

Bed-LastNotifyLspId

ID of the reversed LSP that corresponds to the error code association event on the egress node. The association event is notified of BFD by the RSVP LSP.

BGPKey

Index of BGP.

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 and CR-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         3         0         1
RSVP CRLSP     0         0         0         0
BGP LSP        1         0         0         1
ASBR LSP       0         0         0         0
BGP IPV6 LSP   0         0         0         0
L3VPN IPV6 LSP 0         0         0         0
----------------------------------------------------------------------
LSP            5         3         0         2
CRLSP          0         0         0         0
----------------------------------------------------------------------
Lsp Type       IngressLspBypassState         TransitLspBypassState
               ExistNotUsed   InUse          ExistNotUsed   InUse
RSVP CRLSP     0              0              0              0
----------------------------------------------------------------------
Table 9-39  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.
  • 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.

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

State of the ingress LSP enabled with FRR:
  • ExistNotUsed: Bypass LSP that is bound to the primary LSP but has no traffic.
  • InUse: Traffic switched to the bypass LSP.

TransitLspBypassState

State of the Transit LSP enabled with FRR:
  • ExistNotUsed: Bypass LSP that is bound to the primary LSP but has no traffic.
  • InUse: Traffic switched to the bypass LSP.
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 [ vpn-instance vpn-instance-name ] [ { exclude | include } { idle | ready | settingup } * | destination-address mask-length ] [ verbose ]

Parameters

Parameter Description Value
vpn-instance vpn-instance-name Specifies the name of a VPN instance.

The value must be an existing VPN instance name.

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

Usage Scenario

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.

Precautions

Only routing states of the LSPs that are set up based on dynamic signaling protocols can be changed. Therefore, the display mpls route-state command displays only routing states of dynamic LSPs, but not routing information about static LSPs.

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)
--------------------------------------------------------------------------------
Dest/Mask         Next-Hop       Out-Interface        State    LSP   VRF Type
-------------------------------------------------------------------------------
10.21.21.21/32    10.22.22.21    Vlanif100            READY    2     0   I
     LspIndex: 30720     InLabel: NULL      OutLabel: 3
     LspIndex: 32728     InLabel: 1024      OutLabel: 3
10.0.0.6/32       10.21.22.21    Vlanif100            READY    1     0   I
     LspIndex: 33053     InLabel: NULL      OutLabel: 3338
Table 9-40  Description of the display mpls route-state verbose command output

Item

Description

Dest/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 mpls static-lsp

Function

The display mpls static-lsp command displays information about static LSPs.

Format

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

Parameters

Parameter Description Value
lsp-name Specifies the name of an LSP. The value is an existing static LSP name.
include Displays information about LSPs, including information about the specific FEC. -
exclude Displays information about LSPs, excluding information about the specific FEC. -
ip-address Specifies the destination IPv4 address. The value is in dotted decimal notation.
mask-length Specifies the length of an IPv4 mask. The value is an integer ranging from 0 to 32.
verbose Displays detailed information. -

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Static LSPs are configured locally, so you need to run the ping lsp command to check whether the static LSP can work normally. If the static LSP cannot work normally, run the display mpls static-lsp command to view information about static LSPs.

Example

# Display brief information about static LSPs.

<HUAWEI> display mpls static-lsp
TOTAL          : 1       STATIC LSP(S)
UP             : 1       STATIC LSP(S)
DOWN           : 0       STATIC LSP(S)
Name       FEC               I/O Label  I/O If                 Status
lsp1       3.3.3.9/32        NULL/100   -/Vlanif100            Up
Table 9-41  Description of the display mpls static-lsp command output

Item

Description

TOTAL

Total number of static LSPs.

UP

Number of static LSPs that are in the Up state.

DOWN

Number of static LSPs that are in the Down state.

Name

Name of an LSP.

FEC

Destination IP address and mask length of an LSP.

I/O Label

Incoming and outgoing labels.

I/O If

Incoming and outbound interfaces.

Status

Current status of an LSP:
  • Up
  • Down

# Display detailed information about static LSPs.

<HUAWEI> display mpls static-lsp verbose
No             : 1
LSP-Name       : lsp1
LSR-Type       : Ingress
FEC            : 3.3.3.9/32
In-Label       : NULL
Out-Label      : 100
In-Interface   : -
Out-Interface  : Vlanif100
NextHop        : 10.1.1.2
Static-Lsp Type: Normal
Lsp Status     : Up
Table 9-42  Description of the display mpls static-lsp verbose command output

Item

Description

No

Serial number.

LSP-Name

Name of an LSP.

LSR-Type

Role of the current LSR on a static LSP:
  • Ingress
  • Transit
  • Egress

FEC

Destination IP address and mask length of an LSP.

In-Label

Incoming label.

Out-Label

Outgoing label.

In-Interface

Inbound interface.

Out-Interface

Outbound interface.

NextHop

Next hop IP address.

Static-Lsp Type

Type of a static LSP.

Lsp Status

LSP status:
  • Up
  • Down
Related Topics

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 ldp-sync interface { all | interface-type interface-number }

Parameters

Parameter Description Value
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
 Interface Vlanif100 
 HoldDown Timer: 9         HoldMaxCost Timer: 50
 LDP State: Up             OSPF Sync State: Sync-Achieved
Table 9-43  Description of the display ospf ldp-sync interface command output

Item

Description

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.

To set the interval at which the interface waits to create an LDP session without creating the OSPF neighbor relationship, run the ospf timer ldp-sync hold-down command.

HoldMaxCost Timer

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

The default interval is 10 seconds.

To set the interval at which OSPF advertises the maximum metric in LSAs sent by the local device, run the ospf timer ldp-sync hold-max-cost command.

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

1: Monitoring 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 : 4
------------------------------------------------------------------------------
Trap name                     Default switch status      Current switch status
Session-Retry                 off                        on
Session-PVL                   off                        on
Session-Up-MIB                off                        on
Session-Down-MIB              off                        on
Table 9-44  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-PVL: PathVectorLimitMismatch event of an LDP session, which indicates that the maximal vector value in the received message is different from the one in the local setting.
  • Session-Up-MIB: An LDP session goes Up through the MIB.
  • Session-Down-MIB: An LDP session goes Down through the MIB.

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 all

Function

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

Format

display snmp-agent trap feature-name mpls all

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

Usage Scenario

After the trap function of a specified feature is enabled, you can run the display snmp-agent trap feature-name mpls all command to check the status of all traps of MPLS. You can use the snmp-agent trap enable feature-name mpls command to enable the trap function of MPLS.

Prerequisites

SNMP has been enabled. For details, see snmp-agent.

Example

# Display all the traps of the MPLS module.

<HUAWEI> display snmp-agent trap feature-name mpls all
------------------------------------------------------------------------------
Feature name: MPLS
Trap number : 3
------------------------------------------------------------------------------
Trap name                       Default switch status   Current switch status
hwBoardMplsPhpResLack           on                      on
hwBoardMplsFwdResLack           on                      on
hwBoardMplsFwdResLackResume     on                      on
Table 9-45  Description of the display snmp-agent trap feature-name mpls all command output

Item

Specification

Feature name

Name of the module that the trap belongs to.

Trap number

Number of traps.

Trap name

Trap name. Traps of the MPLS module include:

  • hwBoardMplsPhpResLack: MPLS PHP labels are insufficient.

    NOTE:

    This trap is only supported by EH1D2X48SEC0 card of S9700.

  • hwBoardMplsFwdResLack: The MPLS forwarding resources are insufficient.

  • hwBoardMplsFwdResLackResume: The alarm of MPLS forwarding resource insufficiency is cleared.

Default switch status

Default status of the trap function:
  • on: indicates that the trap function is enabled by default.

  • off: indicates that the trap function is disabled by default.

Current switch status

Status of the trap function:

  • on: indicates that the trap function is enabled.

  • off: indicates that 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

1: Monitoring 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 : 82                                                                
------------------------------------------------------------------------------  
Trap name                       Default switch status   Current switch status   
mplsXCUp                        off                     off                     
mplsXCDown                      off                     off                     
hwMplsStaticLspUp               off                     off                     
hwMplsStaticLspDown             off                     off                     
hwMplsLdpVirtualTunnelUp        off                     off                     
hwMplsLdpVirtualTunnelDown      off                     off                     
hwMplsLspThresholdExceed        off                     off                     
hwMplsLspThresholdExceedClear   off                     off                     
hwMplsLspTotalCountExceed       off                     off                     
hwMplsLspTotalCountExceedClear  off                     off                     
hwMplsDynamicLabelThresholdExceed                                               
                                off                     off                     
hwMplsDynamicLabelThresholdExceedClear                                          
                                off                     off                     
hwMplsDynamicLabelTotalCountExceed                                              
                                off                     off                     
hwMplsDynamicLabelTotalCountExceedClear                                         
                                off                     off
hwMplsResourceThresholdExceed   off                     off
hwMplsResourceThresholdExceedClear
                                off                     off
hwMplsResourceTotalCountExceed  off                     off
hwMplsResourceTotalCountExceedClear
                                off                     off
mplsTunnelUp                    off                     off                     
mplsTunnelDown                  off                     off                     
hwMplsStaticCRLspUp             off                     off                     
hwMplsStaticCRLspDown           off                     off                     
mplsTunnelReoptimized           off                     off                     
mplsTunnelRerouted              off                     off                     
hwMplsTeFrrSwitch               off                     off                     
hwMplsTeFrrResume               off                     off                     
hwMplsTunnelHSBSwitch           off                     off                     
hwMplsTunnelHSBResume           off                     off                     
hwMplsTunnelOBSwitch            off                     off                     
hwMplsTunnelOBResume            off                     off                     
hwMplsTeFrrProtAval             off                     off                     
hwMplsTeFrrProtNotAval          off                     off                     
hwmplsTunnelChangeBW            off                     off                     
hwMplsTunnelTpOamLossSD         off                     off                     
hwMplsOamLoss                   off                     off                     
hwMplsOamLossRecovery           off                     off                     
hwMplsOamAis                    off                     off                     
hwMplsOamAisRecovery            off                     off                     
hwMplsOamRdi                    off                     off                     
hwMplsOamRdiRecovery            off                     off                     
hwMplsOamMeg                    off                     off                     
hwMplsOamMegRecovery            off                     off                     
hwMplsOamMep                    off                     off                     
hwMplsOamMepRecovery            off                     off                     
hwMplsOamSF                     off                     off                     
hwMplsOamSFRecovery             off                     off                     
hwMplsOamPeriod                 off                     off                     
hwMplsOamPeriodRecovery         off                     off                     
hwMplsOamSDRecovery             off                     off                     
hwMplsOamLck                    off                     off                     
hwMplsOamLckRecovery            off                     off                     
hwMplsOamExcess                 off                     off                     
hwMplsOamExcessRecovery         off                     off                     
hwMplsOamMisMatch               off                     off                     
hwMplsOamMisMatchRecovery       off                     off                     
hwMplsOamMisMerge               off                     off                     
hwMplsOamMisMergeRecovery       off                     off                     
hwMplsOamUnknown                off                     off                     
hwMplsOamUnknownRecovery        off                     off                     
hwMplsOamBDI                    off                     off                     
hwMplsOamBDIRecovery            off                     off                     
hwMplsOamFail                   off                     off                     
hwMplsOamFailRecovery           off                     off                     
hwMplsTunnelPrimaryUp           off                     off                     
hwMplsTunnelPrimaryDown         off                     off                     
hwMplsTunnelHotstandbyUp        off                     off                     
hwMplsTunnelHotstandbyDown      off                     off                     
hwMplsTunnelOrdinaryUp          off                     off                     
hwMplsTunnelOrdinaryDown        off                     off                     
hwMplsTunnelBesteffortUp        off                     off                     
hwMplsTunnelBesteffortDown      off                     off                     
hwMplsTeAutoTunnelDownClear     off                     off                     
hwMplsTeAutoTunnelPrimaryDownClear                                              
                                off                     off                     
hwMplsTunnelBBSwitch            off                     off                     
hwMplsTunnelBBResume            off                     off                     
hwMplsExtTunnelDown             off                     off                     
hwMplsExtTunnelDownClear        off                     off                     
hwMplsOamLocalLock              off                     off                     
hwMplsOamLocalLockRecovery      off                     off                     
hwMplsTunnelDelete              off                     off
hwMplsTunnelCommitLost          off                     on
hwMplsTunnelCommitLostClear     off                     on
Table 9-46  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:

  • mplsXCUp: The trap of the event that an LSP goes Up.
  • mplsXCDown: The trap of the event that an LSP goes Down.
  • hwMplsStaticLspUp: The private trap of the event that a static LSP goes Up.
  • hwMplsStaticLspDown: The private trap of the event that a static LSP goes Down.
  • hwMplsLdpVirtualTunnelUp: The trap of the event that an LDP virtual tunnel goes Up.
  • hwMplsLdpVirtualTunnelDown: The trap of the event that an LDP virtual tunnel goes Down.
  • hwMplsLspThresholdExceed: The function to generate an alarm if the number of LSPs exceeds the alarm threshold.
  • hwMplsLspThresholdExceedClear: The function to clear an alarm if the number of LSPs falls below the alarm threshold.
  • hwMplsLspTotalCountExceed: The function to generate an alarm if the number of LSPs exceeds the maximum limit.
  • hwMplsLspTotalCountExceedClear: The function to clear an alarm if the number of LSPs falls below the maximum limit.
  • hwMplsDynamicLabelThresholdExceed: Dynamic label usage reached the upper limit.
  • hwMplsDynamicLabelThresholdExceedClear: Dynamic label usage reached the lower limit.
  • hwMplsDynamicLabelTotalCountExceed: Dynamic label usage reached 100%.
  • hwMplsDynamicLabelTotalCountExceedClear: Dynamic label usage fell to 95%.
  • hwMplsResourceThresholdExceed: The function to generate an alarm if the number of used MPLS resources exceeds the alarm threshold.
  • hwMplsResourceThresholdExceedClear: The function to clear an alarm if the number of used MPLS resources falls below the alarm threshold.
  • hwMplsResourceTotalCountExceed: The function to generate an alarm if the number of used MPLS resources exceeds the maximum limit.
  • hwMplsResourceTotalCountExceedClear: The function to clear an alarm if the number of used MPLS resources falls below the maximum limit.
  • mplsTunnelUp: The trap of the event that a tunnel goes Up.
  • mplsTunnelDown: The trap of the event that a tunnel goes Down.
  • hwMplsStaticCRLspUp: The private trap of the event that a static CR-LSP goes Up.
  • hwMplsStaticCRLspDown: The private trap of the event that a static CR-LSP goes Down.
  • mplsTunnelReoptimized: The trap of the tunnel reoptimization event.
  • mplsTunnelRerouted: The trap of the tunnel reroute event.
  • hwMplsTeFrrSwitch: The private trap of the event of TE FRR protection switching.
  • hwMplsTeFrrResume: The private trap of the event of TE FRR fault recovery.
  • hwMplsTunnelHSBSwitch: The private trap of the event that traffic switches from the primary CR-LSP to the hot-standby CR-LSP.
  • hwMplsTunnelHSBResume: The private trap of the event that traffic switches from the hot-standby CR-LSP to the primary CR-LSP.
  • hwMplsTunnelOBSwitch: The private trap of the event that traffic switches from the primary CR-LSP to the ordinary backup CR-LSP.
  • hwMplsTunnelOBResume: The private trap of the event that traffic switches from the ordinary backup CR-LSP to the primary CR-LSP.
  • hwMplsTeFrrProtAval: The trap of the TE FRR bypass tunnel binding event.
  • hwMplsTeFrrProtNotAval: The trap of the TE FRR bypass tunnel unbinding event.
  • hwmplsTunnelChangeBW: The private trap of the event that the tunnel bandwidth changes.
  • hwMplsTunnelTpOamLossSD: The trap of the event that the loss of tunnel exceeds the threshold.
  • hwMplsOamLoss: The trap of the event that the tunnel receives a loss of continuity (LOC) alarm.
  • hwMplsOamLossRecovery: The trap of the event that the LOC alarm received by the tunnel is cleared.
  • hwMplsOamAis: The trap of the event that the tunnel receives an alarm indication signal (AIS) alarm.
  • hwMplsOamAisRecovery: The trap of the event that the AIS alarm received by the tunnel is cleared.
  • hwMplsOamRdi: The trap of the event that the tunnel receives a remote defect indication (RDI) alarm.
  • hwMplsOamRdiRecovery: The trap of the event that the RDI alarm received by the tunnel is cleared.
  • hwMplsOamMeg: The trap of the event that the tunnel receives an unexpected MEG alarm.
  • hwMplsOamMegRecovery: The trap of the event that the unexpected MEG alarm received by the tunnel is cleared.
  • hwMplsOamMep: The trap of the event that the tunnel receives an unexpected MEP alarm.
  • hwMplsOamMepRecovery: The trap of the event that the unexpected MEP alarm received by the tunnel is cleared.
  • hwMplsOamSF: The trap of the event that the tunnel receives a local signal deterioration threshold 2 alarm.
  • hwMplsOamSFRecovery: The trap of the event that the local signal deterioration threshold 2 alarm received by the tunnel is cleared.
  • hwMplsOamPeriod: The trap of the event that the tunnel receives an unexpected period alarm.
  • hwMplsOamPeriodRecovery: The trap of the event that the unexpected period alarm received by the tunnel is cleared.
  • hwMplsOamSDRecovery: The trap of the event that the local signal degrade threshold 1 alarm received by the tunnel is cleared.
  • hwMplsOamLck: The trap of the event that the tunnel receives an LCK alarm.
  • hwMplsOamLckRecovery: The trap of the event that the LCK alarm received by the tunnel is cleared.
  • hwMplsOamExcess: The trap of the event that the tunnel receives an Excess alarm.
  • hwMplsOamExcessRecovery: The trap of the event that the Excess alarm received by the tunnel is cleared.
  • hwMplsOamMisMatch: The trap of the event that the tunnel receives a MisMatch alarm.
  • hwMplsOamMisMatchRecovery: The trap of the event that the MisMatch alarm received by the tunnel is cleared.
  • hwMplsOamMisMerge: The trap of the event that the tunnel receives a MisMerge alarm.
  • hwMplsOamMisMergeRecovery: The trap of the event that the MisMerge alarm received by the tunnel is cleared.
  • hwMplsOamUnknown: The trap of the event that the tunnel receives an unknown alarm.
  • hwMplsOamUnknownRecovery: The trap of the event that the unknown alarm received by the tunnel is cleared.
  • hwMplsOamBDI: The trap of the event that the tunnel receives a backward defect indication (BDI) alarm.
  • hwMplsOamBDIRecovery: The trap of the event that the BDI alarm received by the tunnel is cleared.
  • hwMplsOamFail: The trap of the event that the tunnel receives an OAMFAIL alarm.
  • hwMplsOamFailRecovery: The trap of the event that the OAMFAIL alarm received by the tunnel is cleared.
  • hwMplsTunnelPrimaryUp: The trap of the event that the primary LSP of the tunnel changes to Up.
  • hwMplsTunnelPrimaryDown: The trap of the event that the primary LSP of the tunnel changes to Down.
  • hwMplsTunnelHotstandbyUp: The trap of the event that the hot-standby LSP of the tunnel changes to Up.
  • hwMplsTunnelHotstandbyDown: The trap of the event that the hot-standby LSP of the tunnel changes to Down.
  • hwMplsTunnelOrdinaryUp: The trap of the event that the ordinary LSP of the tunnel changes to Up.
  • hwMplsTunnelOrdinaryDown: The trap of the event that the ordinary LSP of the tunnel changes to Down.
  • hwMplsTunnelBesteffortUp: The trap of the event that the best-effort LSP of the tunnel changes to Up.
  • hwMplsTunnelBesteffortDown: The trap of the event that the best-effort LSP of the tunnel changes to Down.
  • hwMplsTeAutoTunnelDownClear: The trap of the event that the TE Auto tunnel Down alarm was cleared.
  • hwMplsTeAutoTunnelPrimaryDownClear: The trap of the event that the Down alarm about the primary LSP in the TE Auto tunnel was cleared.
  • hwMplsTunnelBBSwitch: The alarm for switchover from the primary LSP to the bypass LSP in common backup mode (BBK).
  • hwMplsTunnelBBResume: The trap of main LSP of tunnel resumes from backup LSP in BBK.
  • hwMplsExtTunnelDown: The trap of the event that the TE tunnel changes to Down.
  • hwMplsExtTunnelDownClear: The trap of the event that the TE tunnel Down alarm was cleared.
  • hwMplsOamLocalLock: The trap of the event that the tunnel receives a LOCK alarm.
  • hwMplsOamLocalLockRecovery: The trap of the event that the LOCK alarm received by the tunnel is cleared.
  • hwMplsTunnelDelete: The function to generate an alarm if an MPLS TE tunnel is deleted.
  • hwMplsTunnelCommitLost: The configuration of an MPLS TE tunnel was not committed.
  • hwMplsTunnelCommitLostClear: The configuration of all MPLS TE tunnel were committed.

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 vplsoam all

Function

The display snmp-agent trap feature-name vplsoam all command displays information about all traps of the VPLS OAM module.

Format

display snmp-agent trap feature-name vplsoam all

Parameters

None

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

The Simple Network Management Protocol (SNMP) is a standard network management protocol widely used on TCP/IP networks. It uses a central computer (a network management station) that runs network management software to manage network elements. The management agent on the network element automatically reports traps to the network management station. After that, the network administrator immediately takes measures to resolve the problem.

The display snmp-agent trap feature-name vplsoam all command displays whether all trap functions of the VPLS OAM module are enabled.

Example

# Display information about all traps of the VPLS OAM module.

<HUAWEI>display snmp-agent trap feature-name vplsoam all
------------------------------------------------------------------------------                                                      
Feature name: VPLSOAM                                                                                                               
Trap number : 3                                                                                                                     
------------------------------------------------------------------------------                                                      
Trap name                       Default switch status   Current switch status                                                       
hwLspvPingProbe                 off                     on                                                                          
hwLspvTraceProbe                off                     on                                                                          
hwLspPingIPv4VpnProbe           off                     on
Table 9-47  Description of the display snmp-agent trap feature-name vplsoam all command output

Item

Description

Feature name

Name of the module to which the traps belong

Trap number

Number of the traps

Trap name

Name of a trap. Traps of the VPLS OAM module include:

  • hwlsppingipv4vpnprobe: indicates the LSP ping IPv4 VPN test trap.
  • hwlspvpingprobe: indicates the ping test trap.
  • hwlspvtraceprobe: indicates the trace test trap.

Default switch status

Status of the trap function by default:
  • on: indicates that the trap function is enabled.
  • off: indicates that the trap function is disabled.

Current switch status

Current status of the trap function:
  • on: indicates that the trap function is enabled currently.
  • off: indicates that the trap function is disabled currently.

fec-list

Function

The fec-list command creates a FEC list used in dynamic BFD for LDP LSP.

The undo fec-list command deletes a FEC list.

By default, no FEC list is created.

Format

fec-list list-name

undo fec-list list-name

Parameters

Parameter Description Value
list-name Specifies the name of a FEC list. The value is a string of 1 to 31 case-sensitive characters without spaces. 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

When a BFD session is established based on the FEC list, run the fec-list command to create a FEC list. Run the fec-node command to specify a host route to trigger the establishment of BFD sessions.

Only a single FEC list can be configured globally.

Example

# Create FEC list 1.

<HUAWEI> system-view
[HUAWEI] fec-list 1

fec-node

Function

The fec-node command adds an FEC node.

The undo fec-node command deletes an FEC node.

By default, no FEC node is created.

Format

fec-node ip-address [ nexthop ip-address | outgoing-interface interface-type interface-number ]*

undo fec-node ip-address [ nexthop ip-address | outgoing-interface interface-type interface-number ]*

Parameters

Parameter Description Value
ip-address Specifies the FEC address. The value is in dotted decimal notation.
nexthop ip-address Specifies the next-hop address. The value is in dotted decimal notation.
outgoing-interface interface-type interface-number Specifies the outbound interface.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-

Views

FEC-list view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When the establishment of BFD sessions is triggered in FEC list mode, the system sets up BFD sessions for the added FEC nodes.

Prerequisites

An FEC list has been created by running the fec-list command.

Example

# Create FEC nodes in the FEC list.

<HUAWEI> system-view
[HUAWEI] fec-list 1
[HUAWEI-fec-list-1] fec-node 10.1.1.1 nexthop 10.2.1.1 outgoing-interface vlanif 100
Related Topics

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.

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.

LDP GR must be enabled on both the GR Restarter and Helper.

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 10.1.1.1 to 254 and 255.

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

inbound peer fec

Function

The inbound peer fec command configures an inbound policy, which allows the LSR to receive Label Mapping messages for IGP routes only from a specified peer.

The undo inbound peer fec command restores the default setting.

By default, no inbound policy is configured.

Format

inbound peer { peer-id | peer-group peer-group-name | all } fec { none | host | ip-prefix prefix-name }

undo inbound peer { peer-id | peer-group peer-group-name | all } fec

undo inbound peer all

Parameters

Parameter Description Value
peer-id Specifies the ID of an LDP peer. The value is in dotted decimal notation.
peer-group peer-group-name Specifies the name of a peer group. The value is an existing peer group name.
all Indicates all LDP peers. -
none Forbids all Label Mapping messages. After the parameter none is configured, the specified LSR does not receive Label Mapping messages for IGP routes from its peers. -
host Allows only Label Mapping messages for host routes. After the parameter host is configured, the specified LSR receives only Label Mapping messages for host routes from its peers. -
ip-prefix prefix-name Allows only Label Mapping messages for IGP routes that are defined in the IP prefix list. After the parameter ip-prefix is configured, the specified LSR receives Label Mapping messages only for IGP routes that are defined in the IP prefix list by its peers. The value is an existing IP prefix list name.

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

When running the inbound 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.

To apply a policy associated with the same FEC range to an LDP peer group or all LDP peers receiving Label Mapping messages, configure either peer-group peer-group-name or all in the command.

Prerequisites

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

Precautions

If multiple inbound policies are configured for a specified LDP peer, the earliest configuration takes effect. For example, the following two inbound policies are configured:
inbound peer 2.2.2.2 fec host
inbound peer peer-group group1 fec none
As group1 also contains an LDP peer with peer-id of 2.2.2.2, the following inbound policy takes effect:
inbound peer 2.2.2.2 fec host
If two inbound 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:
inbound peer 2.2.2.2 fec host
inbound peer 2.2.2.2 fec none
The second configuration overrides the first one. This means that the following inbound policy takes effect on the LDP peer with peer-id of 2.2.2.2:
inbound peer 2.2.2.2 fec none

Creating a peer group before it is referenced is recommended. By default, nonexistent peer groups cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent peer group is referenced using the current command, the current command applies to all LDP peers.

Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, the device receives Label Mapping messages of all LDP FECs from the specified peer.

Example

# Configure all LSRs to receive Label Mapping messages only for host routes from peers.

<HUAWEI> system-view
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] inbound peer all fec host

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

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 GE1/0/1.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] isis enable 1
[HUAWEI-GigabitEthernet1/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

Interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The ldp-sync enable command run in the IS-IS view on a device enables synchronization between LDP and IS-IS on all local IS-IS interfaces. On an IS-IS interface transmits importance services, LDP and IS-IS synchronization may affect service transmission. If the link is working properly and an LDP session over the link fails, IS-IS sends link state PDUs (LSPs) to advertise the maximum cost of the link. As a result, IS-IS does not select the route for the link, which affects important service transmission.

To prevent the preceding problem, run the isis ldp-sync block command to block synchronization between LDP and IS-IS on the IS-IS interface that transmits important services.

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 GE1/0/1.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] isis enable 1
[HUAWEI-GigabitEthernet1/0/1] isis ldp-sync block

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

Interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a network with both active and standby links, if the active link fails, traffic switches to a standby link. Therefore, the standby IS-IS route and backup LDP label switched path (LSP) along the standby link become reachable. After the active link recovers, its IS-IS route converges more rapidly than the LDP LSP. As a result, the IS-IS neighbor relationship is established earlier than the LDP session on the active link. Although traffic is directed over the IS-IS route to the active link, traffic fails to be forwarded because no LDP LSP is established.

To prevent the traffic forwarding failure, LDP and IS-IS synchronization can be configured. After the active link recovers from a physical fault, the IS-IS route for the active link is set to the Hold-down state, and the Hold-down timer starts. After an LDP session is established over the active link or the Hold-down timer expires, the IS-IS neighbor relationship starts to be established. This allows the LDP LSP and IS-IS route to go Up simultaneously. To set the Hold-down timer, run the isis timer ldp-sync hold-down command.

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
# Set the value of the Hold-down timer for GE1/0/1 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 gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] isis enable 1
[HUAWEI-GigabitEthernet1/0/1] 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 interval is 10 seconds.

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

Interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a network with active and standby links, when the IS-IS route of the active link is reachable and an LDP session between two nodes on the active link fails, traffic is transmitted over the IS-IS route of the active link, whereas the label switched path (LSP) on the active link fails. Although LSP traffic attempts to be switched to the backup LSP, the active IS-IS route is selected to direct traffic. As a result, traffic on the primary LSP is lost.

To prevent the traffic forwarding failure, LDP and IS-IS synchronization can be configured. If the LDP session over the active link fails, IS-IS advertises the maximum cost of the active link route. The IS-IS route for the standby link is selected, and the Hold-max-cost timer starts. After the LDP LSP over the standby link is established, and the IS-IS route for the standby link is reachable, traffic switches to the standby link. After the LDP session on the active link recovers or the Hold-max-cost timer expires, IS-IS advertises the actual cost of the active link route. To set the Hold-max-cost timer, run the isis timer ldp-sync hold-max-cost command.

Select one of the following parameters as required:
  • When IS-IS carries LDP services only, configure infinite to keep the IS-IS route and LSP over the same link.

  • If IS-IS carries multiple types of services including LDP services in the networking, configure value to ensure that interruption of an LDP session over the active link does not affect IS-IS routing and other services. The default is 10, in seconds, which is a recommended value.

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 gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] isis enable 1
[HUAWEI-GigabitEthernet1/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

MPLS transmits packets along label switched paths (LSPs). The egress at the last hop on the LSP removes MPLS labels from packets before forwarding the packets over IP links or using next layer labels. MPLS labels are useless at the last hop on an LSP. Therefore, penultimate hop popping (PHP) can be configured to enable the penultimate hop to remove labels, which improves forwarding efficiency.

By default, PHP is enabled, and the egress assigns implicit-null labels to the penultimate hop. To specify the type of label that the egress assigns to the penultimate hop, run the following commands:

  • In a bidirectional association LSP scenario, run the label advertise non-null command to enable the egress to assign a normal label to the penultimate hop.
  • In an MPLS QoS scenario, run the label advertise explicit-null command to enable the egress to assign an explicit null label to the penultimate hop.

Prerequisites

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

Precautions

After the label advertise command is run to specify a label, the egress on a newly established LDP LSP or constraint-based routed label switched path (CR-LSP) assigns the specified label to the penultimate hop. The label advertise command can take effect on existing LDP LSPs or CR-LSPs when one of the following conditions is met:

  • A master/slave main control board switchover is performed.

  • The reset mpls ldp command is run to reset an LDP public instance for an LDP LSP.

  • If a CR-LSP is established, the reset mpls rsvp-te command is run to reset Resource Reservation Protocol-Traffic Engineering (RSVP-TE), or the reset mpls te tunnel-interface tunnel command is run to restart a specified TE tunnel.

If the label advertise command is run more than once, the latest configuration overrides the previous one.

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

label-withdraw-delay

Function

The label-withdraw-delay command enables a node to delay sending Label Withdraw messages.

The undo label-withdraw-delay command disables a node from delaying sending Label Withdraw messages.

By default, the label withdraw delay function is disabled.

Format

label-withdraw-delay

undo label-withdraw-delay

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The label withdraw delay function prevents downstream LSP flapping from spreading to upstream nodes. For example, an LSP on a local node flaps because an LDP session between the node and its downstream peer flaps, a route flaps, or an LDP policy is modified. The local node repeatedly sends Label Withdraw and Label Mapping messages in sequence to upstream nodes. This causes the upstream nodes to repeatedly tear down and reestablish LSPs. As a result, the entire LDP LSP flaps. The label withdraw delay function can be enabled on each node of the LDP LSP to suppress the spread of LSP flapping.

Follow-up Procedure

Use the default delay time of 5s or run the label-withdraw-delay timer command to set the delay time.

Example

# Enable the label withdraw delay function.

<HUAWEI> system-view
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] label-withdraw-delay

label-withdraw-delay timer

Function

The label-withdraw-delay timer command sets the delay time before a node sends a Label Withdraw message.

The undo label-withdraw-delay timer command restores the default delay time.

The default delay time is 5 seconds.

Format

label-withdraw-delay timer time

undo label-withdraw-delay timer

Parameters

Parameter Description Value
time

Specifies the delay time before a Label Withdraw message can be sent.

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

The label withdraw delay function prevents downstream LSP flapping from spreading to upstream nodes. For example, an LSP on a local node flaps because an LDP session between the node and its downstream peer flaps, a route flaps, or an LDP policy is modified. The local node repeatedly sends Label Withdraw and Label Mapping messages in sequence to upstream nodes. This causes the upstream nodes to repeatedly tear down and reestablish LSPs. As a result, the entire LDP LSP flaps. To suppress the spread of LSP flapping, run the label-withdraw-delay command to enable the label withdraw delay function on each node and the label-withdraw-delay timer command to set the delay time before a node sends a Label Withdraw message to its upstream node.

Prerequisites

The label withdraw delay function has been enabled using the label-withdraw-delay command.

Example

# Enable the label withdraw delay function on the node and set the delay time to 10s.

<HUAWEI> system-view
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] label-withdraw-delay
[HUAWEI-mpls-ldp] label-withdraw-delay timer 10

ldp-sync enable

Function

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

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

By default, synchronization between LDP and IS-IS is disabled on all interfaces in an IS-IS process.

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. -

Views

IS-IS 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.

The ldp-sync enable command run in the IS-IS view can enable synchronization between LDP and IS-IS on all interfaces within a specified IS-IS process.

Follow-up Procedure

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

Precautions

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

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

longest-match

Function

The longest-match command configures inter-domain LDP extension capability and enable LDP to search for routes to establish LSPs based on the longest match rule.

The undo longest-match command restores the default setting.

By default, LDP searches for routes to establish LSPs based on the exact matching rule.

Format

longest-match

undo longest-match

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On a large network, multiple IGP areas need to be configured for flexible network deployment and fast route convergence. In this situation, when advertising routes between IGP areas, to prevent a large number of routes from consuming too many resources, an Area Border Router (ABR) needs to aggregate the routes in an area and then advertise the aggregated route to neighbor IGP areas. By default, when establishing LSPs, LDP searches the routing table for the route that exactly matches the forwarding equivalence class (FEC) carried in the received Label Mapping message. For aggregated routes, only liberal LDP LSPs, not inter-area LDP LSPs, can be set up.

In this case, run the longest-match command to enable LDP to search for routes or establishing inter-area LDP LSPs based on the longest match rule.

Precautions

Configuring this command is not allowed during LDP GR.

Example

# Enable LDP to search for routes for establishing LDP LSPs based on the longest match rule.

<HUAWEI> system-view
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] longest-match

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.

Precautions

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

Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all public-network labeled BGP routes trigger LDP LSP establishment.

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

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 polices 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 | ip-prefix ip-prefix-name } command can be used to establish proxy egress LSPs. The lsp-trigger host command, however, cannot be used to establish proxy egress LSPs.

  • Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all static and IGP routes trigger LDP LSP establishment.

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 mpls-lsp-ping echo enable

Function

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

The undo lspv mpls-lsp-ping echo enable command disables 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 enable

undo lspv mpls-lsp-ping echo enable

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 lspv mpls-lsp-ping echo enable command to enable a device to respond to MPLS Echo Request packets or run the undo lspv mpls-lsp-ping echo enable 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 recommended to run the undo lspv mpls-lsp-ping echo enable command to disable the device from responding to MPLS Echo Request packets to avoid occupation of system resources.

Precautions

If you run the undo lspv mpls-lsp-ping echo enable 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] undo lspv mpls-lsp-ping echo enable

lspv packet-filter

Function

The lspv packet-filter command enables the filtering of MPLS Echo Request packets based on source addresses. Filtering rules are defined in ACL configurations.

The undo lspv packet-filter command disables the filtering of MPLS Echo Request packets based on source addresses.

By default, the filtering of MPLS Echo Request packets based on source addresses is disabled.

Format

lspv packet-filter acl-number

undo lspv packet-filter

Parameters

Parameter Description Value
acl-number Specifies the number of an ACL. The ACL number is a decimal integer that ranges from 2000 to 3999.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

The lspv packet-filter command often runs on the destination device of the LSPV check. In the case that the filtering of MPLS Echo Request packets based on source addresses is enabled, upon receiving MPLS Echo Request packets, the device matches the source addresses of the packets with a specified ACL. The packets permitted by the ACL are processed; those denied by the ACL are discarded.

Example

# Enable the filtering of the MPLS Echo Request packets based on source addresses based on ACL 2100.

<HUAWEI> system-view
[HUAWEI] lspv packet-filter 2100

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 10.1.1.1.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] quit
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] lsr-id 10.1.1.1
Warning: All the related sessions will be deleted if the operation is performed!Continue? (y/n)y
Related Topics

maintain-session received-error-message

Function

The maintain-session received-error-message command enables LDP to maintain a session after receiving error TCP packets.

The undo maintain-session received-error-message command restores the default configuration.

By default, LDP tears down a session after receiving error TCP packets.

Format

maintain-session received-error-message

undo maintain-session received-error-message

Parameters

None

Views

MPLS-LDP view

Default Level

2: Configuration level

Usage Guidelines

According to RFC5036, LDP tears down a session after receiving error TCP packets. When a device from another vendor fails or a link fails, the LDP session alternates between Up and Down after processing in this way. If the LDP transmits L2VPN services, the L2VPN services will be interrupted. To prevent this problem, run the maintain-session received-error-message command to enable LDP to maintain a session after receiving error TCP packets. This prevents LDP session flapping and helps maintain upper-layer L2VPN services.

Example

# Enable LDP to maintain a session after receiving error TCP packets.

<HUAWEI> system-view
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] maintain-session received-error-message

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 [ plain | cipher ] 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 392 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.

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.

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 392 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.

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.

  • 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.

  • MD5 encryption algorithm cannot ensure security. Keychain authentication is recommended.

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.

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.

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 392 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.

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.

  • 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.

  • MD5 encryption algorithm cannot ensure security. Keychain authentication is recommended.

  • Before a peer group is referenced, create it. By default, a nonexistent peer group cannot be specified in this command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent peer group is specified in this command, a local device performs MD5 authentication for each LDP session connected to each LDP peer.

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.

Prerequisites

The LSR ID has been configured using the mpls lsr-id command.

Precautions

After the undo mpls command is run in the system view, MPLS services may be interrupted and all MPLS configurations in the system and interface views are deleted. To restore the MPLS services, reconfigure these commands.

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

Interface view

NOTE:

The mpls command does not take effect in the tunnel 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 GE1/0/1.
<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] quit
[HUAWEI] interface gigabitethernet 1/0/1 
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls
Related Topics

mpls bfd enable

Function

The mpls bfd enable command enables dynamic creation of BFD sessions on the ingress node of an LDP LSP.

The undo mpls bfd enable command disables the dynamic creation of BFD sessions on the ingress node of an LDP LSP.

By default, an ingress cannot dynamically create BFD sessions for monitoring LDP LSPs.

Format

mpls bfd enable

undo mpls bfd enable

Parameters

None

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

On an MPLS network, use LDP to dynamically create LSP tunnels. Upon a fault on the link, the convergence is slow. Configure BFD to detect LDP LSP connectivity to speed up convergence.

To dynamically establish a BFD session, run the mpls bfd enable command on the source end of the LDP LSP.

NOTE:

After the mpls bfd enable command is used, no BFD session is set up.

Prerequisites

BFD has been enabled globally using the bfd command.

Example

# Enable the dynamic creation of BFD sessions on the ingress node of an LDP LSP.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls bfd enable
Related Topics

mpls bfd

Function

The mpls bfd command sets the parameters of BFD sessions.

The undo mpls bfd command deletes the parameters of BFD sessions.

By default, no parameter of BFD sessions is set.

Format

mpls bfd { min-tx-interval tx-interval | min-rx-interval rx-interval | detect-multiplier multiplier } *

undo mpls bfd { min-tx-interval tx-interval | min-rx-interval rx-interval | detect-multiplier multiplier } *

undo mpls bfd { min-tx-interval | min-rx-interval | detect-multiplier } *

Parameters

Parameter Description Value
min-tx-interval tx-interval Specifies the interval at which BFD packets are sent.
The value is an integer, in milliseconds. If the MPU has the ES0D00FSUA00 card installed or the MPU is EH1D2SRUDC00/EH1D2SRUDC01, the value ranges from 3 to 1000. The default value is 10 ms. In other cases, the value ranges from 100 to 1000 and the default value is 1000 ms.
NOTE:

When the MPU is the EH1D2SRUDC00 or EH1D2SRUDC01, you need to first run the detect-engine enable command in the system view so that the value range is 3 to 1000. If the detect-engine enable command is not used first, the value range is 100 to 1000.

min-rx-interval rx-interval Specifies the interval at which BFD packets are received.
The value is an integer, in milliseconds. If the MPU has the ES0D00FSUA00 card installed or the MPU is EH1D2SRUDC00/EH1D2SRUDC01, the value ranges from 3 to 1000. The default value is 10 ms. In other cases, the value ranges from 100 to 1000 and the default value is 1000 ms.
NOTE:

When the MPU is the EH1D2SRUDC00 or EH1D2SRUDC01, you need to first run the detect-engine enable command in the system view so that the value range is 3 to 1000. If the detect-engine enable command is not used first, the value range is 100 to 1000.

detect-multiplier multiplier Specifies the local detection multiplier value of a BFD session. An integer ranging from 3 to 50. The value is 3 by default.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

On an MPLS network, use BFD to detect LSP connectivity to increase the link fault detection speed. Users can change the values of BFD parameters based on actual networking. On an unstable link, if the BFD parameters are set small, the BFD session may flap. You can increase the values of BFD parameters.

Actual interval for the local device to send BFD packets = max { interval for sending BFD packets on the local end, interval for receiving BFD packets on the peer end }; actual interval for the local device to receive BFD packets = max { interval for sending BFD packets on the peer end, interval for receiving BFD packets on the local end }; and local BFD detection time = actual interval for receiving BFD packets on the local end x BFD detection multiplier on the peer end.

If no BFD packet is received from the peer device within the detection time, the link is considered as faulty and the BFD session enters the Down state. To reduce the usage of system resources, when the BFD session is detected in Down state, the system adjusts the sending interval to a random value greater than 1000 ms. When the BFD session becomes Up, the configured interval is restored.

Example

# Set the interval at which BFD packets are sent to 200 ms.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls bfd min-tx-interval 200
Related Topics

mpls bfd-trigger

Function

The mpls bfd-trigger command configures a trigger policy for an LDP BFD session.

The undo mpls bfd-trigger command deletes a trigger policy for an LDP BFD session.

By default, no trigger policy for an LDP BFD session is configured.

Format

mpls bfd-trigger [ host [ nexthop next-hop-address | outgoing-interface interface-type interface-number ] * | fec-list list-name ]

undo mpls bfd-trigger [ host [ nexthop next-hop-address | outgoing-interface interface-type interface-number ] * | fec-list list-name ]

Parameters

Parameter Description Value
host Indicates that all host addresses are used to create LDP BFD sessions. -
nexthop next-hop-address Specifies the next hop address on an LSP. The value is in dotted decimal notation.
outgoing-interface interface-type interface-number Specifies the type and number of an outbound interface.
  • interface-type specifies the type of the interface.
  • interface-number specifies the number of the interface.
-
fec-list list-name Specifies the name of a FEC list, by which the creation of an LDP BFD session is triggered. The value is an existing FEC list name.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The trigger policy for LDP BFD has two types: the host address and FEC list.

If you want all host addresses to trigger the establishment of BFD sessions, use the host trigger mode. Specify the LSPs that can set up BFD sessions by specifying the next hop address and the outbound interface.

If you only want part of hosts to trigger the establishment of BFD sessions, use the FEC list trigger mode to specify the corresponding host addresses. Before specifying the FEC list triggering mode, run the fec-list and fec-node commands to configure a FEC list.

Prerequisites

BFD has been enabled globally using the bfd command.

Example

# Configure the host trigger policy of BFD sessions in the MPLS view.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls bfd enable
[HUAWEI-mpls] mpls bfd-trigger host

mpls bfd-ldp-number threshold-alarm

Function

The mpls bfd-ldp-number threshold-alarm command configures the conditions that trigger the threshold-reaching alarm and its clear alarm for dynamic BFD sessions for LDP. The conditions include the upper and lower alarm thresholds (percent) for the proportion of established dynamic BFD sessions for LDP to all supported ones.

The undo mpls bfd-ldp-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 bfd-ldp-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls bfd-ldp-number threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value

Sets the upper alarm threshold for the proportion of established dynamic BFD sessions for LDP 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 dynamic BFD sessions for LDP 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 dynamic BFD sessions for LDP reaches a specified upper limit, new dynamic BFD sessions for LDP 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 dynamic BFD sessions for LDP to all supported ones reaches a specified upper alarm threshold. The following parameters can be configured in the mpls bfd-ldp-number threshold-alarm command:

  • upper-limit-value: upper alarm threshold. If the proportion of established dynamic BFD sessions for LDP 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 dynamic BFD sessions for LDP to all supported ones falls below the lower alarm threshold, a clear alarm can be generated.

Precautions

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

  • The mpls bfd-ldp-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 dynamic BFD sessions for LDP.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls bfd-ldp-number threshold-alarm upper-limit 90 lower-limit 60

mpls bgp bfd

Function

The mpls bgp bfd command sets time parameters for BGP BFD sessions.

The undo mpls bgp bfd command restores default time parameters for BGP BFD sessions.

By default, the minimum interval for sending and receiving BFD packets is 10 ms when the MPU is equipped with the ES0D00FSUA00 or the MPU is EH1D2SRUDC00/EH1D2SRUDC01; otherwise, the minimum interval for sending and receiving BFD packets is 1000 ms. The local detection multiplier is 3.

Format

mpls bgp bfd { min-tx-interval interval | min-rx-interval interval | detect-multiplier multiplier } *

undo mpls bgp bfd { min-tx-interval | min-rx-interval | detect-multiplier } *

undo mpls bgp bfd { min-tx-interval interval | min-rx-interval interval | detect-multiplier multiplier } *

Parameters

Parameter Description Value
min-tx-interval interval Specifies the minimum interval at which BGP BFD packets are sent.
The value is an integer, in milliseconds. If the MPU is equipped with the ES0D00FSUA00 or the MPU is EH1D2SRUDC00/EH1D2SRUDC01, the value ranges from 3 to 1000. Otherwise, the value ranges from 100 to 1000.
NOTE:

When the MPU is the EH1D2SRUDC00 or EH1D2SRUDC01, you need to first run the detect-engine enable command in the system view so that the value range is 3 to 1000. If the detect-engine enable command is not used first, the value range is 100 to 1000.

min-rx-interval interval Specifies the minimum interval at which BGP BFD packets are received.
The value is an integer, in milliseconds. If the MPU is equipped with the ES0D00FSUA00 or the MPU is EH1D2SRUDC00/EH1D2SRUDC01, the value ranges from 3 to 1000. Otherwise, the value ranges from 100 to 1000.
NOTE:

When the MPU is the EH1D2SRUDC00 or EH1D2SRUDC01, you need to first run the detect-engine enable command in the system view so that the value range is 3 to 1000. If the detect-engine enable command is not used first, the value range is 100 to 1000.

detect-multiplier multiplier Specifies the local BGP BFD detection multiplier.

The value is an integer ranging from 3 to 50. The default value is 3.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

A BGP BFD session working in asynchronous mode monitor BGP label switched paths (LSPs) over BGP tunnels. The ingress and egress of E2E BGP LSPs exchange BFD packets periodically. If a node receives no BFD packet after the detection period elapses, the node considers the BGP LSP faulty.

Effective BFD time parameters are calculated using the following formulas:

  • Effective local interval at which BFD packets are sent = MAX { Locally configured minimum interval at which BFD packets are sent, Remotely configured minimum interval at which BFD packets are received }

  • Effective local interval at which BFD packets are received = MAX { Remotely configured minimum interval at which BFD packets are sent, Locally configured minimum interval at which BFD packets are received }

  • Local BFD detection period = Effective local interval at which BFD packets are received x Remotely configured BFD detection multiplier

Example

# Set the minimum interval at which BGP BFD packets are sent to 200 ms.

<HUAWEI> system-view
[HUAWEI] mpls lsr-id 10.1.1.1
[HUAWEI] mpls
[HUAWEI-mpls] mpls bgp bfd min-tx-interval 200

mpls bgp bfd enable

Function

The mpls bgp bfd enable command enables the MPLS ability to dynamically create BGP BFD sessions.

The undo mpls bgp bfd enable command disables the MPLS ability to dynamically create BGP BFD sessions.

By default, the MPLS ability to dynamically create BGP BFD sessions is disabled.

Format

mpls bgp bfd enable

undo mpls bgp bfd enable

Parameters

None

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

BFD for BGP tunnel rapidly detects faults in E2E BGP tunnels. Before a BGP BFD session is established, run the mpls bgp bfd enable command on the ingress of a BGP tunnel to enable the MPLS ability to dynamically create a BGP BFD session.

Prerequisites

BFD has been globally enabled using the bfd command.

Follow-up Procedure

Run the mpls bgp bfd-trigger-tunnel command to establish a BGP BFD session.

Example

# Enable the MPLS ability to dynamically create a BGP BFD session on the ingress of a BGP tunnel.

<HUAWEI> system-view
[HUAWEI] bfd
[HUAWEI-bfd] quit
[HUAWEI] mpls lsr-id 10.1.1.1
[HUAWEI] mpls
[HUAWEI-mpls] mpls bgp bfd enable

mpls bgp bfd-trigger-tunnel

Function

The mpls bgp bfd-trigger-tunnel command specifies a policy to establish BGP BFD sessions.

The undo mpls bgp bfd-trigger-tunnel command deletes a policy to establish BGP BFD sessions.

By default, no trigger policy is configured.

Format

mpls bgp bfd-trigger-tunnel { host | ip-prefix ip-prefix-name }

undo mpls bgp bfd-trigger-tunnel

Parameters

Parameter Description Value
host Allows a device to use host addresses to establish BGP BFD sessions. -
ip-prefix ip-prefix-name Allows a device to use an IP address prefix list with a specified name to establish BGP BFD sessions.

The value is an existing IP address prefix list.

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

BFD for BGP tunnel rapidly detects faults in E2E BGP tunnels. Before a BGP BFD session is established, the mpls bgp bfd enable command must be run to enable the MPLS ability to dynamically establish BGP BFD sessions on the ingress of a BGP tunnel. Then to specify the policy for dynamically establish BGP BFD sessions, run the mpls bgp bfd-trigger-tunnel command.

Either of the following trigger policies can be used:

  • Host address-based policy: used when all host addresses are available to trigger the creation of BGP BFD sessions.

  • IP address prefix list-based policy: used when only some host addresses can be used to establish BFD sessions.

Prerequisites

BFD has been globally enabled using the bfd command.

Precautions

If the mpls bgp bfd-trigger-tunnel command is run more than once, the latest configuration overrides the previous one.

Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all host addresses trigger BGP BFD session establishment.

Example

# Allow a device to use host addresses to dynamically establish BGP BFD sessions.

<HUAWEI> system-view
[HUAWEI] bfd
[HUAWEI-bfd] quit
[HUAWEI] mpls lsr-id 10.1.1.1
[HUAWEI] mpls
[HUAWEI-mpls] mpls bgp bfd enable
[HUAWEI-mpls] mpls bgp bfd-trigger-tunnel host

mpls bgp-lsp-number threshold-alarm

Function

The mpls bgp-lsp-number threshold-alarm command configures the alarm threshold for BGP LSP usage.

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

The default upper limit of the alarm threshold for BGP LSP usage is 80%. The default lower limit of the clear alarm threshold for BGP LSP usage is 75%.

Format

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

mpls bgp-lsp-number { ingress | egress } threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls bgp-lsp-number threshold-alarm

undo mpls bgp-lsp-number { ingress | egress } threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value Specifies the upper limit of the alarm threshold for BGP 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 BGP 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.
ingress

Specifies the alarm threshold for ingress BGP LSPs.

-
egress

Specifies the alarm threshold for egress BGP LSPs.

-

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

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

  • upper-limit-value: upper alarm threshold. If the proportion of BGP 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 BGP LSP usage to all supported ones falls below the lower alarm threshold, a clear alarm can be generated.

If you want to set the alarm threshold for ingress BGP LSPs or egress BGP LSPs, run mpls bgp-lsp-number { ingress | egress } threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value.

Precautions

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

  • This command configures the alarm threshold for BGP 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 BGP 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 BGP LSP usage falls below the lower limit of the clear alarm threshold.

Example

# Configure the upper limit and the lower limit of the alarm threshold for BGP LSP usage.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls bgp-lsp-number threshold-alarm upper-limit 90 lower-limit 60

mpls bgpv6-lsp-number threshold-alarm

Function

The mpls bgpv6-lsp-number threshold-alarm command configures the alarm threshold for BGP IPv6 LSP usage.

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

The default upper limit of the alarm threshold for BGP IPv6 LSP usage is 80%. The default lower limit of the clear alarm threshold for BGP IPv6 LSP usage is 75%.

Format

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

mpls bgpv6-lsp-number egress threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls bgpv6-lsp-number threshold-alarm

undo mpls bgpv6-lsp-number egress threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value Specifies the upper limit of the alarm threshold for BGP IPv6 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 BGP IPv6 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.
egress

Specifies the alarm threshold for egress BGP IPv6 LSPs.

-

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

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

  • upper-limit-value: upper alarm threshold. If the proportion of BGP IPv6 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 BGP IPv6 LSP usage to all supported ones falls below the lower alarm threshold, a clear alarm can be generated.

If you want to set the alarm threshold for egress BGP IPv6 LSPs, run mpls bgpv6-lsp-number egress threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value.

Precautions

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

  • This command configures the alarm threshold for BGP IPv6 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 BGP IPv6 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 BGP IPv6 LSP usage falls below the lower limit of the clear alarm threshold.

Example

# Configure the upper limit and the lower limit of the alarm threshold for BGP IPv6 LSP usage.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls bgpv6-lsp-number threshold-alarm upper-limit 90 lower-limit 60

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 TE, MPLS LDP, BGP, L3VPN and L2VPN. 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 forward-resource threshold-alarm

Function

The mpls forward-resource threshold-alarm command configures the conditions that trigger the threshold-reaching alarm and its clear alarm for MPLS forwarding resources.

The undo mpls forward-resource threshold-alarm command restores the default settings.

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

Format

mpls forward-resource threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls forward-resource threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value

Sets the upper alarm threshold.

The value is an integer ranging from 2 to 100, represented in percentage.
lower-limit lower-limit-value

Sets the lower alarm threshold.

The value is an integer ranging from 1 to (upper-limit-value-1), represented in percentage.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

If the number of MPLS forwarding resources reaches a specified upper limit, new MPLS forwarding entries 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 MPLS forwarding resources reaches a specified upper alarm threshold. The following parameters can be configured in the mpls forward-resource threshold-alarm command:

  • upper-limit-value: upper alarm threshold. If the proportion of MPLS forwarding resources reaches the upper alarm threshold, an alarm can be generated.
  • lower-limit-value: lower alarm threshold. If the proportion of MPLS forwarding resources falls below the lower alarm threshold, a clear alarm can be generated.

Precautions

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

  • The mpls forward-resource 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 trap-name { hwboardmplsfwdreslack | hwboardmplsfwdreslackresume } command is run to enable the device to generate MPLS forwarding resources insufficiency alarm and its clear alarm.

Example

# Configure conditions that trigger the threshold-reaching alarm and its clear alarm for MPLS forwarding resources.

<HUAWEI> system-view
[HUAWEI] mpls forward-resource 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 advertisement

Function

The mpls ldp advertisement command configures the label advertisement mode.

The undo mpls ldp advertisement command restores the default setting.

By default, the label advertisement mode is downstream unsolicited (DU).

Format

mpls ldp advertisement { dod | du }

undo mpls ldp advertisement

Parameters

Parameter Description Value
dod Indicates the downstream on demand (DoD) mode. After the upstream requests the downstream for a label, the downstream sends a Label Mapping message to the upstream. -
du Indicates the DU mode. Without a request, the downstream voluntarily sends a Label Mapping message to the upstream. -

Views

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

By default, downstream LSRs unsolicitedly send Label Mapping messages to upstream LSRs. Establishing a large number of LSPs burdens an LSR such as a DSLAM (a low-performance access device) deployed on an MPLS network. On a large network, run the mpls ldp advertisement dod command. This setting allows a DSLAM to send Label Mapping messages to upstream LSRs only after receiving requests for labels. This setting helps minimize the number of unwanted MPLS forwarding entries forwarded by the DSLAM.

Prerequisites

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

Precautions

  • When multiple links exist between neighbors, all interfaces must use the same label advertisement mode.

  • Modifying the label advertisement mode causes reestablishment of LDP sessions.

  • LDP DoD does not support NSR. That is the mpls ldp advertisement dod command and the switchover mode nonstop-routing command cannot be configured together.

Example

# Set the label advertisement mode to DoD.
<HUAWEI> system-view
[HUAWEI] interface vlanif 100
[HUAWEI-Vlanif100] mpls
[HUAWEI-Vlanif100] mpls ldp
[HUAWEI-Vlanif100] mpls ldp advertisement dod
Warning: All the related sessions will be deleted if the operation is performed!Continue? (y/n)y
# Set the label advertisement mode to DoD.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls
[HUAWEI-GigabitEthernet1/0/1] mpls ldp
[HUAWEI-GigabitEthernet1/0/1] mpls ldp advertisement dod
Warning: All the related sessions will be deleted if the operation is performed!Continue? (y/n)y

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

After the undo mpls ldp command is run in the system view, MPLS LDP services may be interrupted and all MPLS LDP configurations in the system and interface views are deleted. To restore the MPLS LDP services, reconfigure these commands.

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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk 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 GE1/0/1.
<HUAWEI> system-view
[HUAWEI] mpls ldp
[HUAWEI-mpls-ldp] quit
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls
[HUAWEI-GigabitEthernet1/0/1] mpls ldp

mpls ldp frr nexthop

Function

The mpls ldp frr nexthop command enables LDP FRR on an interface.

The undo mpls ldp frr command disables LDP FRR on an interface.

By default, no interface is enabled with LDP FRR.

Format

mpls ldp frr nexthop nexthop-address [ ip-prefix ip-prefix-name ] [ priority priority ]

undo mpls ldp frr [ nexthop nexthop-address ] [ ip-prefix ip-prefix-name ] [ priority priority ]

Parameters

Parameter Description Value
nexthop-address Specifies the next hop address on a backup LSP. The value is in dotted decimal notation.
ip-prefix ip-prefix-name Specifies the IP prefix name. Only the FEC that matches the specified IP prefix can trigger the generation of a backup LSP. The value is an existing IP prefix name.
priority priority Specifies the priority of a backup LSP. The greater the value is, the lower priority the backup LSP has. The value is an integer ranging from 1 to 65535. By default, the value is 50.

Views

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The traditional IP FRR technology cannot effectively protect the traffic on an MPLS network. The device provides the LDP FRR function and the solution to port protection.

In the manual LDP FRR mode, you need to configure a backup LSP by specifying the outbound interfaces or the next hops. This mode applies to simple-structured networks.

When running the mpls ldp frr nexthop command to configure the next hop IP address, note that:

  • You can configure multiple next hops on one interface. This allows you to configure multiple backup LSPs with different outbound interfaces for the primary LSP.

  • You can configure different prefix lists for the same next hop on one interface.

    • If no prefix list is specified, LDP FRR tries to establish backup LSPs along the path specified by nexthop-address for all primary LSPs on the interface.

    • If only the DENY item is in a specified prefix list, no backup LSP is allowed to set up along the path specified by nexthop-address for the primary LSP mapping to the FEC denied by the interface.

    • If only PERMIT item is in the specified prefix list, backup LSPs are allowed to set up along the path specified by nexthop-address only for the primary LSPs mapping to the FEC permitted by the interface.

    • If both PERMIT and DENY items are in the prefix list, only the PERMIT item is effective. That is, backup LSPs are allowed to set up along the path specified by nexthop-address only for the primary LSPs mapping to the FEC permitted by the interface.

  • A single interface supports LDP FRR with a maximum of 10 priorities. Only a single backup LSP is generated.

Prerequisites

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

Precautions

  • If the undo mpls ldp command is run in the system view or the undo mpls ldp command is run in the interface view to disable LDP functions, the LDP FRR configuration in the interface remains but does not take effect. During the LDP FRR configuration, the LSP that functions as the backup LSP must be in the liberal state. For a backup LSP, the routing status of the backup LSP from the ingress node to the egress node must be Inactive Adv.

  • LDP FRR cannot be enabled or disabled during LDP GR.

  • When both LDP FRR and IP FRR are enabled, IP FRR takes effect.

  • Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, backup LSPs are established for all LDP LSPs on the local interface along the path to the specified next-hop IP address.

Example

# Enable LDP FRR on VLANIF100, and set the next hop IP address of the backup LSP to 10.1.1.2.
<HUAWEI> system-view
[HUAWEI] interface vlanif 100
[HUAWEI-Vlanif100] mpls
[HUAWEI-Vlanif100] mpls ldp frr nexthop 10.1.1.2
# Enable LDP FRR on GE1/0/1, and set the next hop IP address of the backup LSP to 10.1.1.2.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls
[HUAWEI-GigabitEthernet1/0/1] mpls ldp frr nexthop 10.1.1.2

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-insensitive 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 is used to allocate inner L2VPN labels.If a Martini VLL or VPLS connection is to be established between two LSRs, the remote LDP session must be established between the LSRs to allocate inner labels.

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

A local and a remote LDP session can be established together between two LSRs.

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. Value 65535 indicates that the timer never expires.

Views

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk 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. If the value is smaller than 9, the Hello hold timer is 9.

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 gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls ldp
[HUAWEI-GigabitEthernet1/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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk 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 gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls ldp
[HUAWEI-GigabitEthernet1/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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view, remote MPLS LDP peer view

Default Level

2: Configuration level

Usage Guidelines

LDP-Interior Gateway Protocol (IGP) synchronization-enabled devices complete to establish an LDP session earlier than an LSP. The mpls ldp timer igp-sync-delay command can be used to switch traffic to the established LSP after a specified period of time. This setting prevents traffic loss that occurs if the LDP session in the Up state attempts to switch traffic to the LSP that has not been established. Using the default delay value is recommended.

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 GE1/0/1, the interval is set to 15 seconds, during which the LSP is being set up.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1]  mpls ldp
[HUAWEI-GigabitEthernet1/0/1]  mpls ldp timer igp-sync-delay 15
# After the LDP session is established in the remote MPLS LDP peer view, the interval is set to 15 seconds, during which the LSP is being set up.
<HUAWEI> system-view
[HUAWEI] mpls ldp remote-peer rta
[HUAWEI-mpls-ldp-remote-rta] 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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 100GE interface view, 40GE interface view, Eth-trunk 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.

Precautions

  • The value of the Keepalive hold timer that takes effect is the smaller one between the two Keepalive hold timers configured on both ends of an LDP session.

  • If more than one LDP link exists between two LSRs, the values of the Keepalive hold timers set for the links must be the same; otherwise, the LDP sessions may be unstable.

  • Changing the value of a Keepalive hold timer causes the reestablishment of related 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 gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls ldp
[HUAWEI-GigabitEthernet1/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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk 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 gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls ldp
[HUAWEI-GigabitEthernet1/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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk 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.

An IP address must be assigned to the specified interface. If no IP address is assigned, 0.0.0.0 is used as a transport address, causing a failure to establish an LDP session.

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
# Set the transport address for link Hello messages to the current interface address.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls ldp
[HUAWEI-GigabitEthernet1/0/1] mpls ldp transport-address interface

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

mpls ldp-lsp-number { ingress | transit | egress } threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls ldp-lsp-number threshold-alarm

undo mpls ldp-lsp-number { ingress | transit | egress } 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.
ingress

Specifies the alarm threshold for ingress LDP LSPs.

-
transit

Specifies the alarm threshold for transit LDP LSPs.

-
egress

Specifies the alarm threshold for egress LDP LSPs.

-

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.

If you want to set the alarm threshold for ingress LDP LSPs, transit LDP LSPs or egress LDP LSPs, run mpls ldp-lsp-number { ingress | transit | egress } threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value.

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 local-adjacency-number threshold-alarm

Function

The mpls local-adjacency-number threshold-alarm command configures the conditions that trigger the threshold-reaching alarm and its clear alarm for local LDP adjacencies. The conditions include the upper and lower alarm thresholds (percent) for the proportion of established local LDP adjacencies to all supported ones.

The undo mpls local-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 local-adjacency-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls local-adjacency-number threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value

Sets the upper alarm threshold for the proportion of established local 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 local 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 local LDP adjacencies reaches a specified upper limit, new local 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 local LDP adjacencies to all supported ones reaches a specified upper alarm threshold. The following parameters can be configured in the mpls local-adjacency-number threshold-alarm command:

  • upper-limit-value: upper alarm threshold. If the proportion of established local 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 local LDP adjacencies to all supported ones falls below the lower alarm threshold, a clear alarm can be generated.

Precautions

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

  • The mpls local-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 local LDP adjacencies.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls local-adjacency-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

Before changing or deleting a configured LSR ID, you must run the undo mpls command in the system view to delete all MPLS configurations. Exercise caution when you run the undo mpls command.

Running the undo mpls command deletes all MPLS configurations (including established LDP sessions and LSPs).

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

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, 100GE interface view, Eth-trunk interface view

NOTE:

The mpls mtu command does not take effect in the tunnel 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 changing the MTU using the mpls mtu or mtu command on an interface, you need to restart the interface to make the new MTU take effect. To restart the interface, run the shutdown command and then the undo shutdown command, or run the restart command in the interface view.

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 GE1/0/1.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls
[HUAWEI-GigabitEthernet1/0/1] mpls mtu 1500

mpls total-lsp-number threshold-alarm

Function

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

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

The default upper limit of the alarm threshold for total LSP usage is 80%. The default lower limit of the clear alarm threshold for total LSP usage is 75%.

Format

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

mpls total-lsp-number { ingress | transit | egress } threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value

undo mpls total-lsp-number threshold-alarm

undo mpls total-lsp-number { ingress | transit | egress } threshold-alarm

Parameters

Parameter Description Value
upper-limit upper-limit-value Specifies the upper limit of the alarm threshold for total 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 total 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.
ingress

Specifies the alarm threshold for total ingress LSPs.

-
transit

Specifies the alarm threshold for total transit LSPs.

-