No local or remote discriminators are set for the BFD session used to verify PW connectivity. The system automatically assigns local and remote discriminators to the BFD session.

Views

Cross-connect PW view

VSI static PW view

VSI LDP PW view

Cross-connect backup PW view

VSI static backup PW view

VSI LDP backup PW view

Predefined user roles

network-admin

Parameters

local local-id: Specifies the local discriminator value for the BFD session, in the range of 1 to 32768.

remote remote-id: Specifies the remote discriminator value for the BFD session, in the range of 1 to 4294967295.

Usage guidelines

A BFD session for PW connectivity verification can be established in one of the following modes:

· Static mode—Specify the local and remote discriminator values by using the bfd discriminator command. You must specify the discriminators on both the local and remote PEs. Make sure the local discriminator and remote discriminator on the local PE are the same as the remote discriminator and local discriminator on the remote PE, respectively. Otherwise, the BFD session cannot be established for the PW.

· Dynamic mode—If you do not specify local and remote discriminators, the system automatically runs MPLS ping to negotiate the discriminator values.

Examples

# In VSI LDP PW view, set both the local and remote discriminator values to 1 for the BFD session used to verify PW connectivity.

<Sysname> system-view

[Sysname] vsi ttt

[Sysname-vsi-ttt] pwsignaling ldp

[Sysname-vsi-ttt-ldp] peer 22.22.2.2 pw-id 1 pw-class ttt

[Sysname-vsi-ttt-ldp-22.22.2.2-1] bfd discriminator local 1 remote 1

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv bfd

vccv cc

bfd ip-router-alert

Use bfd ip-router-alert to add the Router Alert option in BFD packets for LSP connectivity verification.

Use undo bfd ip-router-alert to remove the Router Alert option from BFD packets for LSP connectivity verification.

Syntax

bfd ip-router-alert

undo bfd ip-router-alert

Default

The device adds the Router Alert option in BFD packets for LSP connectivity verification.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Execute the undo bfd ip-router-alert command on the local device if the peer device cannot identify the Router Alert option in BFD packets.

This command takes effect only on BFD sessions that come up after this command is executed.

Examples

# Remove the Router Alert option from BFD packets.

<Sysname> system-view

[Sysname] undo bfd ip-router-alert

bfd static mpls-te

Use bfd static mpls-te to create a static BFD session for connectivity verification of an MPLS TE tunnel and enter its view, or enter the view of an existing static BFD session.

Use undo bfd static to delete a static BFD session and all the configurations for the session.

Syntax

bfd static session-name mpls-te interface interface-type interface-number [ te-lsp [ backup ] ] [ one-arm-echo ]

undo bfd static session-name

Default

No static BFD sessions exist.

Views

System view

Predefined user roles

network-admin

Parameters

session-name: Specifies the static BFD session name, a case-sensitive string of 1 to 64 characters.

interface interface-type interface-number: Specifies an MPLS TE tunnel interface to be detected by the static BFD session.

te-lsp: Performs BFD for LSPs of the TE tunnel. If you do not specify this keyword, the device performs BFD for the MPLS TE tunnel.

backup: Performs BFD for the backup LSPs of the TE tunnel. If you do not specify this keyword, the device performs BFD for the primary LSP of the MPLS TE tunnel.

one-arm-echo: Specifies the BFD mode of the static BFD session as one-arm-echo. If you do not specify this keyword, the BFD mode is the control packet mode.

Usage guidelines

Before you configure BFD for an MPLS TE tunnel, you must first configure the MPLS TE tunnel interface.

An MPLS TE tunnel can contain multiple LSPs. BFD can detect failures for the MPLS TE tunnel or for the primary and backup LSPs of the MPLS TE tunnel. If you use BFD to detect failure of the MPLS TE tunnel, the BFD session is set to down only when all the LSPs of tunnel failed.

You cannot repeat this command to modify a static BFD session. To modify a static BFD session, you must first delete the session and then create the session again with new settings.

Examples

# Create a static BFD session named abc for connectivity verification of MPLS TE tunnel 1 and enter the view of the BFD session.

<Sysname> system-view

[Sysname] bfd static abc mpls-te interface tunnel 1

[Sysname-bfd-static-session-abc]

bfd static pw

Use bfd static pw to create a static BFD session for PW connectivity verification and enter its view, or enter the view of an existing static BFD session.

Use undo bfd static to delete a static BFD session and all the configurations for the session.

Syntax

bfd static session-name pw interface interface-type interface-number [ remote-peer remote-ip-address ] [ backup ]

undo bfd static session-name

Default

No static BFD sessions exist.

Views

System view

Predefined user roles

network-admin

Parameters

session-name: Specifies the static BFD session name, a case-sensitive string of 1 to 64 characters.

interface interface-type interface-number: Specifies the interface associated with an MPLS L2VPN cross-connect. After you specify the interface, BFD performs single-hop detection for the PW associated with the cross connect.

remote-peer remote-ip-address: Specifies the peer PE address of the PW.

backup: Performs BFD for the backup PW. If you do not specify this keyword, the device performs BFD for the primary PW.

Usage guidelines

To configure a static BFD session for an MPLS TE tunnel, make sure the BFD session uses the asynchronous mode.

You need to configure a BFD session for the primary PW and another BFD session for the backup PW.

This command can verify the connectivity only for MPLS L2VPN PWs.

If the specified interface is a loopback interface, the static BFD session is created for the admin PW.

You cannot repeat this command to modify a static BFD session. To modify a static BFD session, you must first delete the session and then create the session again with new settings.

Examples

# Create a static BFD session named abc for PW connectivity verification and enter its view. Use the static BFD session to detect failure for the link that uses outgoing interface Ten-GigabitEthernet 3/1/1 and peer PE address 1.1.1.2.

<Sysname> system-view

[Sysname] bfd static abc pw interface ten-gigabitethernet 3/1/1 remote-peer 1.1.1.2

[Sysname-bfd-static-session-abc]

Related commands

discriminator (High Availability Command Reference)

display l2vpn pw bfd

Use display l2vpn pw bfd to display BFD information for PWs.

Syntax

display l2vpn pw bfd [ peer peer-ip { pw-id pw-id | remote-service-id remote-service-id } ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

peer peer-ip: Specifies the LSR ID of the peer PE for a PW. If you do not specify a PW, this command displays BFD information for all PWs.

pw-id pw-id: Specifies the PW ID, in the range of 1 to 4294967295.

remote-service-id remote-service-id: Specifies the remote service ID of the EVPN PW, in the range of 1 to 16777215. For more information about EVPN PW, see EVPN VPWS in EVPN Configuration Guide.

Examples

# Display BFD information for all PWs.

<Sysname> display l2vpn pw bfd

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: PW FEC-128

FEC Info:

Peer IP: 22.22.2.2

PW ID: 1

VSI Index: 0 Link ID: 8

Local Discr: 514 Remote Discr: 514

Source IP: 11.11.1.1 Destination IP: 127.0.0.2

Session State: Up Session Role: Active

Template Name: -

# Display BFD information for the EVPN PW whose remote PE LSR ID is 1.1.1.1 and remote service ID is 100.

<Sysname> display l2vpn pw bfd peer 1.1.1.1 remote-service-id 100

Total number of sessions: 1, 1 up, 0 down, 0 init

BFD Info: Tunnel BFD

FEC Type: EVPN PW

FEC Info:

Peer IP: 1.1.1.1

Remote Service ID: 100

Connection ID: 2147483651 Link ID: 0

Local Discr: 33283 Remote Discr: 33285

Source IP: 4.4.4.4 Destination IP: 127.0.0.3

Session State: Up Session Role: Active

Template Name: -

Table 1 Command output

Field	Description
BFD Info: Tunnel BFD	Indicates that the PW was detected by tunnel BFD.
FEC type	Type of the FEC detected by BFD: PW FEC-128 or EVPN PW.
Peer IP	LSR ID of the peer PE.
VSI Index	Index of the VSI to which the PW belongs. This field is displayed when the PW is a VPLS PW.
Connection ID	ID of the cross-connect to which the PW belongs. This field is displayed when the PW is an MPLS L2VPN PW.
Link ID	Link ID of the PW.
Local Discr	Local discriminator of the BFD session.
Remote Discr	Remote discriminator of the BFD session.
Source IP	Source IP of the BFD session, which is the MPLS LSR ID of the local PE.
Destination IP	Destination IP address of the BFD session, which is on subnet 127.0.0.0/8.
Session State	BFD session state: · Init—BFD session is in initialization state. · Up—BFD session is up. · Down—BFD session is down.
Session Role	Role of the local PE in the BFD session: · Active—Sender of the BFD session. · Passive—Receiver of the BFD session.
Template Name	Name of the BFD session parameter template.

‌

Related commands

bfd discriminator

vccv bfd

vccv cc

display mpls bfd

Use display mpls bfd to display BFD information for LSP tunnels or MPLS TE tunnels.

Syntax

display mpls bfd [ ipv4 ipv4-address mask-length | te tunnel tunnel-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv4 ipv4-address mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

te tunnel tunnel-number: Specifies an existing MPLS TE tunnel by the tunnel interface number.

Usage guidelines

If you do not specify any parameters, this command displays BFD information for all LSP tunnels and all MPLS TE tunnels.

Examples

# Display BFD information for the LSPs to destination 22.22.2.2/32. In this example, BFD control packet mode is used.

<Sysname> display mpls bfd ipv4 22.22.2.2 32

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: LSP

FEC Info:

Destination: 22.22.2.2

Mask Length: 32

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up Session Role: Passive

Template Name: -

# Display BFD information for the LSPs to destination 22.22.2.2/32. In this example, tunnel BFD control packet mode is used.

<Sysname> display mpls bfd ipv4 22.22.2.2 32

Total number of sessions: 1, 1 up, 0 down, 0 init

BFD Info: Tunnel BFD

FEC Type: LSP

FEC Info:

Destination: 22.22.2.2

Mask Length: 32

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up Session Role: Passive

Template Name: -

# Display BFD information for MPLS TE tunnel interface Tunnel 1. In this example, BFD control packet mode is used.

<Sysname> display mpls bfd te tunnel 1

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: TE Tunnel

FEC Info:

Source : 100.1.1.1

Destination: 200.1.1.1

Tunnel ID : 1

LSP ID : 100

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up Session Role: Passive

Template Name: -

# Display BFD information for MPLS TE tunnel interface Tunnel 1. In this example, tunnel BFD control packet mode is used.

<Sysname> display mpls bfd te tunnel 1

Total number of sessions: 1, 1 up, 0 down, 0 init

BFD Info: Tunnel BFD

FEC Type: TE Tunnel

FEC Info:

Source : 100.1.1.1

Destination: 200.1.1.1

Tunnel ID : 1

LSP ID : 100

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up Session Role: Passive

Template Name: -

# Display BFD information for MPLS TE tunnel interface Tunnel 1. In this example, BFD echo packet mode is used.

<Sysname> display mpls bfd te tunnel 1

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: TE Tunnel

FEC Info:

Source : 100.1.1.1

Destination: 200.1.1.1

Tunnel ID : 1

LSP ID : 100

NHLFE ID: 1025

Local Discr: 513

Source IP: 11.11.1.1 Destination IP: 200.1.1.1

Session State: Up

Template Name: -

# Display BFD information for MPLS TE tunnel interface Tunnel 1. In this example, tunnel BFD echo packet mode is used.

<Sysname> display mpls bfd te tunnel 1

Total number of sessions: 1, 1 up, 0 down, 0 init

BFD Info: Tunnel BFD

FEC Type: TE Tunnel

FEC Info:

Source : 100.1.1.1

Destination: 200.1.1.1

Tunnel ID : 1

LSP ID : 100

NHLFE ID: 1025

Local Discr: 513

Source IP: 11.11.1.1 Destination IP: 200.1.1.1

Session State: Up

Template Name: -

Table 2 Command output

Field	Description
BFD Info: Tunnel BFD	Indicates that the LSP or tunnel was detected by tunnel BFD.
Local Discr	Local discriminator of the BFD session.
Remote Discr	Remote discriminator of the BFD session.
Source IP	Source IP of the BFD session, which is the MPLS LSR ID of the local PE.
Destination IP	If BFD control packet mode is used, this field displays the destination IP address of the BFD session. At the ingress node, it is an address on subnet 127.0.0.0/8. At the egress node, it is the MPLS LSR ID of the ingress node. If BFD echo packet mode is used, this field displays the destination IP address of the tunnel to be inspected.
Session State	BFD session state: · Init—BFD session is in initialization state. · Up—BFD session is up. · Down—BFD session is down.
Session Role	Role of the local PE in the BFD session: · Active—Initiator of the BFD session. · Passive—Responder of the BFD session.
Template Name	Name of the BFD session parameter template.

‌

Related commands

mpls bfd (for LSP)

mpls bfd (for TE tunnel)

display mpls sbfd

Use display mpls sbfd to display SBFD information for LSP tunnels, MPLS TE tunnels, Flex-Algo LSP tunnels, or SR-MPLS TE policy tunnels.

Syntax

display mpls sbfd [ ipv4 ipv4-address mask-length | flex-algo-lsp [ ipv4 ipv4-address mask-length [ algorithm flex-algo-id-begin [ to flex-algo-id-end ] ] ] | sr-policy [ name sr-policy-name | end-point ipv4 ip-address color color-value ] | te tunnel tunnel-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipv4 ipv4-address mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

flex-algo-lsp [ ipv4 ipv4-address mask-length [ algorithm flex-algo-id-begin [ to flex-algo-id-end ] ] ]: Displays SBFD information for Flex-Algo LSPs.

· ipv4 ipv4-address mask-length: Specifies the destination IPv4 address of a Flex-Algo LSP. The mask-length argument specifies the mask length of destination IPv4 address, in the range of 0 to 32. If you do not specify this option, the command displays SBFD information for all Flex-Algo LSPs.

· algorithm flex-algo-id-begin [ to flex-algo-id-end ]: Specifies the Flex-Algos used to calculate the LSPs. The flex-algo-id-begin argument represents the start Flex-Algo ID. The flex-algo-id-end argument represents the end Flex-Algo ID. If you do not specify this option, the command displays SBFD information for all Flex-Algo LSPs with the specified destination address.

sr-policy: Displays SBFD information for SR-MPLS TE policy tunnels.

name sr-policy-name: Specifies an SR-MPLS TE policy by its name, a case-sensitive string of 1 to 59 characters.

end-point ipv4 ip-address color color-value: Specifies an SR-MPLS TE policy by its endpoint IPv4 address and color attribute. The value range for the color-value argument is 0 to 4294967295.

te tunnel tunnel-number: Specifies an existing MPLS TE tunnel by the tunnel interface number.

Usage guidelines

If you do not specify any parameters, this command displays SBFD information for all LSP tunnels, MPLS TE tunnels, and SR-MPLS TE policy tunnels.

If you specify the sr-policy keyword but do not specify the name sr-policy-name or end-point ipv4 ip-address color color-value option, this command displays SBFD information for all SR-MPLS TE policy tunnels.

Examples

# Display SBFD information for the LSPs to destination 22.22.2.2/32.

<Sysname> display mpls sbfd ipv4 22.22.2.2 32

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: LSP

FEC Info:

Destination: 22.22.2.2

Mask Length: 32

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up

Template Name: -

# Display SBFD information for MPLS TE tunnel interface Tunnel 1.

<Sysname> display mpls sbfd te tunnel 1

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: TE Tunnel

FEC Info:

Source : 100.1.1.1

Destination: 200.1.1.1

Tunnel ID : 1

LSP ID : 100

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up

Template Name: -

# Display SBFD information for SR-MPLS TE policy policy100.

<Sysname> display mpls sbfd sr-policy policy100

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: SR-TE policy

FEC Info:

Name : policy100

Color : 100

Endpoint: 5.5.5.5

NHLFE ID: 1025

Local Discr : 513 Remote Discr : 513

Source IP : 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up

Template Name: -

# Display tunnel SBFD information for MPLS TE tunnel interface Tunnel 1.

<Sysname> display mpls sbfd te tunnel 1

Total number of sessions: 1, 1 up, 0 down, 0 init

BFD Info: Tunnel SBFD

FEC Type: TE Tunnel

FEC Info:

Source : 100.1.1.1

Destination: 200.1.1.1

Tunnel ID : 1

LSP ID : 100

NHLFE ID: 1025

Local Discr: 513 Remote Discr: 513

Source IP: 11.11.1.1 Destination IP: 127.0.0.1

Session State: Up

Template Name: -

# Display SBFD information for the LSP destination for 1.1.1.9 and calculated by Flex-Algo 130.

<Sysname> display mpls sbfd flex-algo ipv4 1.1.1.9 32 130

Total number of sessions: 1, 1 up, 0 down, 0 init

FEC Type: Flex-Algo LSP

FEC Info:

Destination: 1.1.1.9

Mask Length: 32

Flex-Algo ID: 130

NHLFE ID: 3

Local Discr: 32769 Remote Discr: 16843017

Source IP: 2.2.2.9 Destination IP: 127.0.0.1

Session State: Up

Template Name: -

Table 3 Command output

Field	Description
BFD Info	BFD information. This field can only be Tunnel SBFD in the current software version.
FEC Type	Type of the FEC detected by SBFD: · LSP. · TE Tunnel. · SR-TE policy. · Flex-Algo LSP
FEC Info	Information of the FEC detected by SBFD. For an LSP, the FEC information includes the FEC destination address and mask length. For a TE tunnel, the FEC information includes the tunnel source and destination addresses, tunnel ID, and LSP ID. For an SR-MPLS TE policy tunnel, the FEC information includes the name, color attribute, and endpoint IP address of the SR-MPLS TE policy. For a Flex-Algo LSP, the FEC information includes the destination address and mask length, and the Flex-Algo ID used to calculate the LSP.
NHLFE ID	NHLFE entry index.
Local Discr	Local discriminator of the SBFD session.
Remote Discr	Remote discriminator of the SBFD session.
Source IP	Source IP of the SBFD session, which is the MPLS LSR ID of the local device.
Destination IP	Destination IP address of the SBFD session, which is an address on subnet 127.0.0.0/8.
Session State	SBFD session state: · Init—The SBFD session is in initialization state. · Up—The SBFD session is up. · Down—The SBFD session is down.
Template Name	Name of the SBFD session parameter template.

‌

Related commands

mpls sbfd (for LSP)

mpls sbfd (for TE tunnel)

mpls bfd (for LSP)

Use mpls bfd to enable BFD for LSPs associated with an FEC.

Use undo mpls bfd to disable BFD for LSPs associated with an FEC.

Syntax

mpls bfd dest-addr mask-length nexthop nexthop-address discriminator local local-id remote remote-id [ bgp-lsp | isis-srlsp | ldp-lsp | ospf-srlsp | static-lsp ] [ template template-name ]

undo mpls bfd dest-addr mask-length nexthop nexthop-address

mpls bfd dest-addr mask-length nexthop nexthop-address [ echo | ldp-fec | nil-fec ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls bfd dest-addr mask-length nexthop nexthop-address

mpls bfd dest-addr mask-length [ echo | ldp-fec ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls bfd dest-addr mask-length

Default

BFD is not used to verify LSP connectivity for an FEC.

Views

System view

Predefined user roles

network-admin

Parameters

dest-addr mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

nexthop nexthop-address: Specifies the next hop address of the FEC. If you specify the FEC next hop, BFD verifies the specified LSP. If you do not specify a next hop, BFD verifies all LSPs for the FEC.

discriminator: Specifies discriminator values for the BFD session.

local local-id: Specifies the local discriminator value for the BFD session, in the range of 1 to 32768.

remote remote-id: Specifies the remote discriminator value for the BFD session, in the range of 1 to 4294967295.

bgp-lsp: Specifies BGP LSP.

isis-srlsp: Specifies IS-IS SRLSP.

ldp-lsp: Specifies LDP LSP.

ospf-srlsp: Specifies OSPF SRLSP.

static-lsp: Specifies static LSP.

echo: Specifies the BFD echo packet mode. If you do not specify this keyword, the BFD control packet mode is used to verify LSP connectivity.

ldp-fec: Encapsulates the LDP IPv4 Prefix FEC in MPLS echo request packets when BFD control packet mode is used to detect LSPs. If you do not specify this keyword, the type of the FEC carried in MPLS echo request packets is IPv4 IGP-Prefix Segment ID. The egress node of an LSP might support only the LDP IPv4 Prefix FEC. If the ingress node sends MPLS echo request packets that carry the IPv4 IGP-Prefix Segment ID type of FEC, the egress node cannot recognize this FEC type. The FEC validation on the egress node will fail and the BFD session will go down. To resolve this issue, specify the ldp-fec keyword to enable the ingress node to encapsulate the LDP IPv4 Prefix FEC in MPLS echo request packets. Then, FEC validation on the egress node can be successful.

nil-fec: Encapsulates the Nil FEC in MPLS echo request packets when BFD control packet mode is used to detect LSPs. In LDP to SR interworking mode, the ingress node (source node) cannot determine whether the LDP LSP is connected to the SRLSP. When the ingress node uses MPLS BFD to detect LSPs, it encapsulates LDP FEC in MPLS echo request packets, which will fail the FEC type verification on the egress node (endpoint node). Then, the BFD session will go down. To resolve this issue, specify the nil-fec keyword to enable the ingress node to encapsulate the Nil FEC in MPLS echo request packets. The egress node will not check the FEC type of packets encapsulated with the Nil FEC.

template template-name: Specifies a BFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a template, BFD control packet mode uses the multihop BFD session settings configured in system view, and BFD echo packet mode uses the system default BFD session settings.

source-ip ipv4-address: Specifies the source IP address of the BFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the BFD session.

Usage guidelines

After you enable BFD for MPLS and execute the mpls bfd command, the device creates a BFD session for each LSP associated with the specified FEC. When an LSP fails, BFD can quickly detect the failure and notify the device to take an action, such as switching traffic to the backup LSP.

The source address of the BFD session can be specified manually, or if not specified, is the MPLS LSR ID of the local device. Before configuring BFD for an LSP tunnel, make sure a route is available on the remote device to reach the source address of the BFD session.

When BFD control packet mode is used to verify LSP connectivity, a BFD session can be established in one of the following modes:

· Static mode—Specify the local and remote discriminator values by using the discriminator keyword in the mpls bfd command. You must execute the mpls bfd enable and mpls bfd commands on both the local and remote devices. Make sure the discriminators configured on the local device match those configured on the remote device. A static BFD session verifies connectivity of a pair of LSPs in opposite directions between two devices.

· Dynamic mode—If you do not specify local and remote discriminators, the system automatically runs MPLS ping to negotiate the discriminator values. You must execute the mpls bfd enable command on both the local and remote devices, but the mpls bfd command is not needed on the remote device. A dynamic BFD session verifies the connectivity of a unidirectional LSP from the local device to the remote device.

To enable the BFD echo packet mode, you must first execute the bfd echo-source-ip command on the local device to specify a source IP address for BFD echo packets.

You must specify the same BFD mode (BFD control or echo packet mode) for the LSPs (specified by next hop addresses) of the same FEC.

If you do not specify the bgp-lsp, isis-srlsp, ldp-lsp, ospf-srlsp, or static-lsp keyword when executing the mpls bfd command, BFD detects the LSPs in the following sequence:

1. Static LSP.

2. LDP LSP.

3. OSPF SRLSP.

4. IS-IS SRLSP.

5. BGP LSP.

The BFD session is up as long as one LSP is operating correctly. The BFD session goes down when all LSPs fail.

Examples

# Use BFD to verify the connectivity of the LSPs to destination 22.22.2.2/32.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls bfd 22.22.2.2 32

# Use BFD to verify the connectivity of the LSP with destination 22.22.2.2/32 and next hop 12.0.0.2.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls bfd 22.22.2.2 32 nexthop 12.0.0.2

# Use BFD to verify the connectivity of the LSP with destination 22.22.2.2/32 and next hop 12.0.0.2. Set both the local and remote discriminators to 1, and use BFD session parameter template test.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls bfd 22.22.2.2 32 nexthop 12.0.0.2 discriminator local 1 remote 1 template test

Related commands

bfd echo-source-ip (High Availability Command Reference)

display mpls bfd

mpls bfd enable

mpls bfd (for TE tunnel)

Use mpls bfd to enable BFD on an MPLS TE tunnel interface.

Use undo mpls bfd to restore the default.

Syntax

mpls bfd discriminator local local-id remote remote-id [ template template-name ]

mpls bfd [ echo | reverse-lsp binding-sid label label-value ] [ template template-name ] [ backup-path [ template template-name ] ] [ source-ip ipv4-address ]

undo mpls bfd

Default

BFD is not enabled on an MPLS TE tunnel interface to verify the tunnel connectivity.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

discriminator: Specifies discriminator values for the BFD session.

local local-id: Specifies the local discriminator value for the BFD session, in the range of 1 to 32768.

remote remote-id: Specifies the remote discriminator value for the BFD session, in the range of 1 to 4294967295.

echo: Enables the BFD echo packet mode.

reverse-lsp binding-sid label label-value: Enables the BFD echo packet mode and specifies the associated reverse SRLSP. The label-value argument specifies the BSID of the tunnel that uses the reverse SRLSP, in the range of 16 to 1048575. Use this option only when bidirectional tunnel is not configured on the MPLS TE tunnel interface on the ingress node. This is to ensure that reply packets from the egress node can be sent to the ingress node over the reverse SRLSP.

template template-name: Specifies a BFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a template:

· For BFD sessions in control packet mode, the device uses the BFD session parameter settings configured on the tunnel interface by using the mpls bfd min-receive-interval, mpls bfd min-transmit-interval, and mpls bfd detect-multiplier commands. If those commands are not configured on the tunnel interface, the device uses the multihop BFD session parameter settings configured in system view.

· For BFD sessions in echo packet mode, the device uses the BFD session parameter settings configured on the tunnel interface by using the mpls bfd min-receive-interval command. If that command is not configured on the tunnel interface, the device uses the system default BFD session parameter settings.

backup-path [ template template-name ]: Creates a BFD session for the MPLS TE backup tunnel, and specifies the BFD session parameter template. The template-name argument indicates the template name, a case-sensitive string of 1 to 63 characters. If you do not specify the backup-path option, the device does not establish a BFD session for the backup tunnel. If you specify the backup-path keyword without specifying the template template-name option, the device establishes a BFD session for the backup tunnel as follows:

· In BFD control packet mode, the device uses the BFD session parameter settings configured on the tunnel interface by using the mpls bfd backup min-receive-interval, mpls bfd backup min-transmit-interval, and mpls bfd backup detect-multiplier commands. If those commands are not configured on the tunnel interface, the device uses the multihop BFD session parameter settings configured in system view.

· In BFD echo packet mode, the device uses the BFD session parameter settings configured on the tunnel interface by using the mpls bfd backup min-receive-interval command. If that command is not configured on the tunnel interface, the device uses the system default BFD session parameter settings.

source-ip ipv4-address: Specifies the source IP address of the BFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the BFD session.

Usage guidelines

After you enable BFD for MPLS and execute the mpls bfd command, the device creates BFD sessions to monitor MPLS TE tunnels. When an MPLS TE tunnel fails, BFD can quickly detect the failure and notify the device to take an action, such as switching traffic to the backup MPLS TE tunnel.

The source address of the BFD session can be specified manually, or if not specified, is the MPLS LSR ID of the local device. Before configuring BFD for an MPLS TE tunnel, make sure a route is available on the remote device to reach the source address of the BFD session.

When BFD control packet mode is used, a BFD session can be established in one of the following modes:

· Static mode—Specify the local and remote discriminators by using the discriminator keyword in the mpls bfd command. You must execute the mpls bfd enable and mpls bfd commands on both the local and remote devices. Make sure the local discriminator and remote discriminator on the local device are the same as the remote discriminator and local discriminator on the remote device, respectively. A static BFD session verifies the connectivity of a pair of MPLS TE tunnels in opposite directions between two devices.

In static BFD session establishment mode, this feature creates a BFD session only for the primary CRLSP on the tunnel interface. In dynamic BFD session establishment mode, this feature creates a BFD session for the primary and backup CRLSPs respectively on the tunnel interface. If the primary and backup CRLSPs fail at the same time, the device puts the MPLS TE tunnel to down state so the tunnel does not receive traffic. If you specify templates for both the primary and backup CRLSPs, specify greater interval settings for the template of the backup CRLSP than the primary CRLSP. This rule ensures that the BFD session for the new working CRLSP is up after a primary/backup CRLSP switchover.

To enable the BFD echo packet mode, you must first execute the bfd echo-source-ip command on the local device to specify a source IP address for BFD echo packets.

If you do not specify the echo or reverse-lsp keyword, this command enables the BFD control packet mode to verify the MPLS TE tunnel connectivity.

Examples

# Enable the BFD control packet mode for MPLS TE tunnel interface Tunnel 1, and use the BFD session parameter template test.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd template test

# Enable the BFD control packet mode for MPLS TE tunnel interface Tunnel 1, and set the local and remote discriminators both to 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd discriminator local 1 remote 1

# Enable the BFD echo packet mode for MPLS TE tunnel interface Tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd echo

Related commands

bfd echo-source-ip (High Availability Command Reference)

display mpls bfd

mpls bfd enable

mpls bfd backup detect-multiplier

Use mpls bfd backup detect-multiplier to set the BFD detection time multiplier for an MPLS TE backup tunnel.

Use undo mpls bfd backup detect-multiplier to restore the default.

Syntax

mpls bfd backup detect-multiplier value

undo mpls backup bfd detect-multiplier

Default

The BFD detection time multiplier is not set for an MPLS TE backup tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

In control packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd backup detect-multiplier and mpls bfd backup-path template commands are both executed in the tunnel interface view, the mpls bfd backup-path template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop detect-multiplier command's configuration is used.

In echo packet mode of BFD for an MPLS TE tunnel:

· If that two commands are both not executed in the tunnel interface view, the bfd detect-multiplier command's configuration is used.

Examples

# Set the BFD detection time multiplier to 3 for the backup tunnel of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd backup detect-multiplier 3

Related commands

bfd detect-multiplier (High Availability Command Reference)

bfd multi-hop detect-multiplier (High Availability Command Reference)

display mpls bfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls bfd backup min-receive-interval

Use mpls bfd backup min-receive-interval to set the minimum interval for an MPLS TE backup tunnel to receive BFD packets.

Use undo mpls bfd backup min-receive-interval to restore the default.

Syntax

mpls bfd backup min-receive-interval interval

undo mpls bfd backup min-receive-interval

Default

The minimum interval for receiving BFD packets is not set for an MPLS TE backup tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the packet sending rate of the peer end from exceeding the packet receiving rate of the local end. If the receiving rate is exceeded, the peer end dynamically adjusts the BFD packet sending interval to the minimum receiving interval of the local end.

In control packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd backup min-receive-interval and mpls bfd backup-path template commands are both executed in the tunnel interface view, the mpls bfd backup-path template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-receive-interval command's configuration is used.

In echo packet mode of BFD for an MPLS TE tunnel:

· If that two commands are both not executed in the tunnel interface view, the bfd min-echo-receive-interval command's configuration is used.

Examples

# Set the minimum BFD packet receiving interval to 550 milliseconds for the backup tunnel of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd backup min-receive-interval 550

Related commands

bfd min-echo-receive-interval (High Availability Command Reference)

bfd multi-hop min-receive-interval (High Availability Command Reference)

display mpls bfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls bfd backup min-transmit-interval

Use mpls bfd backup min-transmit-interval to set the minimum interval for an MPLS TE backup tunnel to transmit BFD packets.

Use undo mpls bfd backup min-transmit-interval to restore the default.

Syntax

mpls bfd backup min-transmit-interval interval

undo mpls bfd backup min-transmit-interval

Default

The minimum interval for transmitting BFD packets is not set for an MPLS TE backup tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

In control packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd backup min-transmit-interval and mpls bfd backup-path template commands are both executed in the tunnel interface view, the mpls bfd backup-path template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-transmit-interval command's configuration is used.

In echo packet mode of BFD for an MPLS TE tunnel, the mpls bfd backup min-transmit-interval command does not take effect.

Examples

# Set the minimum BFD packet transmitting interval to 450 milliseconds for the backup tunnel of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd backup min-transmit-interval 450

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

display mpls bfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls bfd detect-multiplier

Use mpls bfd detect-multiplier to set the BFD detection time multiplier for an MPLS TE primary tunnel.

Use undo mpls bfd detect-multiplier to restore the default.

Syntax

mpls bfd detect-multiplier value

undo mpls bfd detect-multiplier

Default

The BFD detection time multiplier is not set for an MPLS TE primary tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

In control packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd detect-multiplier and mpls bfd template commands are both executed in the tunnel interface view, the mpls bfd backup-path template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop detect-multiplier command's configuration is used.

In echo packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd detect-multiplier and mpls bfd template commands are both executed in the tunnel interface view, the mpls bfd template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd detect-multiplier command's configuration is used.

Examples

# Set the BFD detection time multiplier to 3 for the primary tunnel of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd detect-multiplier 3

Related commands

bfd detect-multiplier (High Availability Command Reference)

bfd multi-hop detect-multiplier (High Availability Command Reference)

display mpls bfd

mpls bfd (for TE tunnel)

mpls bfd enable

Use mpls bfd enable to enable BFD for MPLS.

Use undo mpls bfd enable to disable BFD for MPLS.

Syntax

mpls bfd enable

undo mpls bfd enable

Default

BFD for MPLS is disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To use BFD to verify LSP, PW, or TE tunnel connectivity, you must use the mpls bfd enable command to enable BFD for MPLS. Otherwise, the BFD session cannot be established after you execute the following commands:

· vccv bfd.

· mpls bfd (for LSP).

· mpls bfd (for TE tunnel).

· mpls sbfd (for LSP).

· mpls sbfd (for TE tunnel).

· mpls tunnel-bfd (for LSP).

· mpls tunnel-bfd (for TE tunnel).

Examples

# Enable BFD for MPLS.

<Sysname> system-view

[Sysname] mpls bfd enable

mpls bfd min-receive-interval

Use mpls bfd min-receive-interval to set the minimum interval for an MPLS TE primary tunnel to receive BFD packets.

Use undo mpls bfd min-receive-interval to restore the default.

Syntax

mpls bfd min-receive-interval interval

undo mpls bfd min-receive-interval

Default

The minimum interval for receiving BFD packets is not set for an MPLS TE primary tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

In control packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd min-receive-interval and mpls bfd template commands are both executed in the tunnel interface view, the mpls bfd template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-receive-interval command's configuration is used.

In echo packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd min-receive-interval and mpls bfd template commands are both executed in the tunnel interface view, the mpls bfd template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd min-echo-receive-interval command's configuration is used.

Examples

# Set the minimum BFD packet receiving interval to 550 milliseconds for the primary tunnel of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd min-receive-interval 550

Related commands

bfd min-echo-receive-interval (High Availability Command Reference)

bfd multi-hop min-receive-interval (High Availability Command Reference)

display mpls bfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls bfd min-transmit-interval

Use mpls bfd min-transmit-interval to set the minimum interval for an MPLS TE primary tunnel to transmit BFD packets.

Use undo mpls bfd min-transmit-interval to restore the default.

Syntax

mpls bfd min-transmit-interval interval

undo mpls bfd min-transmit-interval

Default

The minimum interval for transmitting BFD packets is not set for an MPLS TE primary tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

In control packet mode of BFD for an MPLS TE tunnel:

· If the mpls bfd min-transmit-interval and mpls bfd template commands are both executed in the tunnel interface view, the mpls bfd template command's configuration takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-transmit-interval command's configuration is used.

In echo packet mode of BFD for an MPLS TE tunnel, the mpls bfd min-transmit-interval command does not take effect.

Examples

# Set the minimum BFD packet transmitting interval to 450 milliseconds for the primary tunnel of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd min-transmit-interval 450

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

display mpls bfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls bfd passive enable

Use mpls bfd passive enable to enable dynamic establishment of passive mode BFD sessions.

Use undo mpls bfd passive enable to disable dynamic establishment of passive mode BFD sessions.

Syntax

mpls bfd passive enable

undo mpls bfd passive enable

Default

The device can dynamically establish passive mode BFD sessions.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Before you execute this command, enable BFD for MPLS by using the mpls bfd enable command.

To configure the control packet mode of BFD for an MPLS TE tunnel, you must execute the mpls bfd passive enable command on the tunnel egress.

Examples

# Enable dynamic establishment of passive mode BFD sessions.

<Sysname> system-view

[Sysname] mpls bfd passive enable

Related commands

mpls bfd enable

mpls bfd trigger tunnel-down

Use mpls bfd trigger tunnel-down to configure the capability of MPLS BFD to trigger tunnel-down.

Use undo mpls bfd trigger tunnel-down to restore the default.

Syntax

mpls bfd trigger tunnel-down { disable | enable }

undo mpls bfd trigger tunnel-down { disable | enable }

Default

The configuration in MPLS TE view is used.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

disable: Disables MPLS BFD from triggering tunnel-down.

enable: Enables MPLS BFD to trigger tunnel-down.

Usage guidelines

If you configure static MPLS BFD in a primary/backup scenario, the device creates a BFD session for only the primary path. During a primary/backup switchover, the BFD session of the primary path might go down if a large number of MPLS TE tunnel interfaces exist, which results in traffic interruption. To resolve this issue, execute the mpls bfd trigger tunnel-down disable command to disable MPLS BFD from triggering tunnel-down. Then, the tunnel interface state remains unchanged when the BFD session of the MPLS TE tunnel interface goes down.

As a best practice, execute the mpls tunnel-bfd command to enable tunnel BFD on an MPLS TE tunnel interface after you disable MPLS BFD from triggering tunnel-down on the interface.

You can execute the mpls bfd trigger tunnel-down command in both MPLS TE view and MPLS TE tunnel interface view. The configuration in MPLS TE view takes effect on all MPLS TE tunnel interfaces. The configuration in MPLS TE tunnel interface view takes effect on only the current MPLS TE tunnel interface. For an MPLS TE tunnel interface, the configuration in MPLS TE tunnel interface view takes precedence over the configuration in MPLS TE view.

Examples

# Enable MPLS BFD to trigger tunnel-down on interface Tunnel 1.

<Sysname> system-view

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls bfd trigger tunnel-down enable

Related commands

mpls bfd trigger tunnel-down enable

Use mpls bfd trigger tunnel-down enable to enable MPLS BFD to trigger tunnel-down.

Use undo mpls bfd trigger tunnel-down enable to disable MPLS BFD from triggering tunnel-down.

Syntax

mpls bfd trigger tunnel-down enable

undo mpls bfd trigger tunnel-down enable

Default

MPLS BFD is able to trigger tunnel-down. An MPLS TE tunnel interface goes down when its BFD session goes down.

Views

MPLS TE view

Predefined user roles

network-admin

Usage guidelines

If you configure static MPLS BFD in a primary/backup scenario, the device creates a BFD session for only the primary path. During a primary/backup switchover, the BFD session of the primary path might go down if a large number of MPLS TE tunnel interfaces exist, which results in traffic interruption. To resolve this issue, execute the undo mpls bfd trigger tunnel-down enable command to disable MPLS BFD from triggering tunnel-down. Then, the tunnel interface state remains unchanged when the BFD session of the MPLS TE tunnel interface goes down.

As a best practice, execute the mpls tunnel-bfd command to enable tunnel BFD on an MPLS TE tunnel interface after you disable MPLS BFD from triggering tunnel-down on the interface.

You can execute the mpls bfd trigger tunnel-down enable command in both MPLS TE view and MPLS TE tunnel interface view. The configuration in MPLS TE view takes effect on all MPLS TE tunnel interfaces. The configuration in MPLS TE tunnel interface view takes effect on only the current MPLS TE tunnel interface. For an MPLS TE tunnel interface, the configuration in MPLS TE tunnel interface view takes precedence over the configuration in MPLS TE view.

Examples

# Enable MPLS BFD to trigger tunnel-down.

<Sysname> system-view

[Sysname] mpls te

[Sysname-te] mpls bfd trigger tunnel-down enable

Related commands

mpls bfd trigger tunnel-down

mpls periodic-tracert (for LSP)

Use mpls periodic-tracert to enable periodic tracert of LSPs for an FEC.

Use undo mpls periodic-tracert to disable periodic tracert of LSPs for an FEC.

Syntax

undo mpls periodic-tracert dest-addr mask-length

Default

Periodic tracert of LSPs for an FEC is disabled.

Views

System view

Predefined user roles

network-admin

Parameters

dest-addr mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

-a source-ip: Specifies the source address of MPLS echo request packets. If you do not specify this option, the device uses the MPLS LSR ID as the source address of MPLS echo requests.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the maximum TTL value of MPLS echo request packets (the maximum number of hops to be inspected). The value range for the ttl-value argument is 1 to 255, and the default is 30.

-m wait-time: Specifies the interval at which tracert is performed. The value range is 15 to 120 minutes. The default is 60 minutes.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-u retry-attempt: Specifies the maximum number of retransmissions of an MPLS echo request if no reply is received. The value range is 1 to 9, and the default value is 3.

fec-check: Checks the FEC stack at transit nodes.

Usage guidelines

The periodic MPLS tracert feature automatically traces an LSP tunnel at intervals. It locates errors on the LSP tunnel, verifies the consistency of the data plane and control plane, and records the detected errors into system logs. You can check the logs to monitor LSP connectivity.

If both BFD and periodic MPLS tracert are configured for an LSP, both feature take effect. When periodic MPLS tracert detects a data plane failure or an inconsistency between data plane and control plane, the device performs the following operations:

1. Deletes the BFD session for the LSP.

2. Re-establishes the BFD session based on the control plane.

Before you execute this command, execute the mpls bfd enable command.

Examples

# Enable periodic tracert for LSPs to destination 11.11.1.1/32.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls periodic-tracert 11.11.1.1 32

Related commands

mpls bfd enable

mpls bfd (for LSP)

mpls sbfd (for LSP)

Use mpls sbfd to enable SBFD for LSPs associated with an FEC.

Use undo mpls sbfd to disable SBFD for LSPs associated with an FEC.

Syntax

mpls sbfd dest-addr mask-length [ nexthop nexthop-address ] [ remote remote-id ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls sbfd dest-addr mask-length [ nexthop nexthop-address ]

Default

SBFD is not used to verify LSP connectivity for an FEC.

Views

System view

Predefined user roles

network-admin

Parameters

dest-addr mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

nexthop nexthop-address: Specifies the next hop address of the FEC. If you specify the FEC next hop, SBFD verifies the specified LSP. If you do not specify a next hop, SBFD verifies all LSPs for the FEC.

remote remote-id: Specifies the remote discriminator of the SBFD session, in the range of 1 to 4294967295. If you do not specify this option, the SBFD session uses the FEC destination address as the remote discriminator.

template template-name: Specifies an SBFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a template, SBFD uses the multihop SBFD session settings configured in system view.

source-ip ipv4-address: Specifies the source IP address of the SBFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the SBFD session.

Usage guidelines

Execute this command on the initiator of an SBFD session.

After you enable BFD for MPLS and execute the mpls sbfd command, the device creates an SBFD session for each LSP associated with the specified FEC. When the primary LSP fails, SBFD can quickly detect the failure and notify the device to take an action, such as switching traffic to the backup LSP.

An SBFD session can be established in static mode.

· If you specify a remote discriminator in the mpls sbfd command, the device uses the specified remote discriminator to establish a static SBFD session.

· If you do not specify a remote discriminator in the mpls sbfd command, the device uses the FEC destination address as the remote discriminator to establish a static SBFD session.

The remote discriminator specified by the mpls sbfd command on the initiator must be the same as the local discriminator specified by the sbfd local-discriminator command on the reflector. Otherwise, the reflector will not respond to the initiator.

The source address of the SBFD session can be specified manually, or if not specified, is the MPLS LSR ID of the initiator. Before configuring SBFD for an LSP tunnel, make sure a route is available on the reflector to reach the source address of the SBFD session.

Examples

# Use SBFD to verify the connectivity of the LSPs to destination 22.22.2.2/32.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls sbfd 22.22.2.2 32 remote 1

# Use BFD to verify the connectivity of the LSP with destination 22.22.2.2/32 and next hop 12.0.0.2. Set the remote discriminator to 1, and use SBFD session parameter template test.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls sbfd 22.22.2.2 32 nexthop 12.0.0.2 remote 1 template test

Related commands

display mpls bfd

mpls bfd enable

sbfd local-discriminator (High Availability Command Reference)

mpls sbfd (for TE tunnel)

Use mpls sbfd to enable SBFD on an MPLS TE tunnel interface.

Use undo mpls sbfd to restore the default.

Syntax

mpls sbfd [ echo | remote remote-id | reverse-lsp binding-sid label label-value ] [ template template-name ] [ backup-path [ template template-name ] ] [ source-ip ipv4-address ]

undo mpls sbfd

Default

SBFD is not used to verify tunnel connectivity on an MPLS TE tunnel interface.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

remote remote-id: Specifies the remote discriminator of the SBFD session, in the range of 1 to 4294967295. If you do not specify this option, the SBFD session uses the tunnel's remote IP address as the remote discriminator.

echo: Enables the SBFD echo packet mode to verify the connectivity of a bidirectional MPLS TE tunnel.

reverse-lsp binding-sid label label-value: Enables the SBFD echo packet mode and specifies the associated reverse SRLSP. The label-value argument specifies the BSID of the tunnel that uses the reverse SRLSP, in the range of 16 to 1048575. Use this option only when bidirectional tunnel is not configured on the MPLS TE tunnel interface on the ingress node. This is to ensure that reply packets from the egress node can be sent to the ingress node over the reverse SRLSP.

template template-name: Specifies an SBFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a template:

· For SBFD sessions in control packet mode, the device uses the SBFD session parameter settings configured on the tunnel interface by using the mpls bfd min-receive-interval, mpls bfd min-transmit-interval, and mpls bfd detect-multiplier commands. If those commands are not configured on the tunnel interface, the device uses the SBFD session parameter settings configured in system view.

· For SBFD sessions in echo packet mode, the device uses the SBFD session parameter settings configured on the tunnel interface by using the mpls bfd min-receive-interval command. If that command is not configured on the tunnel interface, the device uses the system default SBFD session parameter settings.

backup-path [ template template-name ]: Creates an SBFD session for the MPLS TE backup tunnel, and specifies the SBFD session parameter template. The template-name argument indicates the template name, a case-sensitive string of 1 to 63 characters. If you do not specify the backup-path option, the device does not establish an SBFD session for the backup tunnel. If you specify the backup-path keyword without specifying the template template-name option, the device establishes an SBFD session for the backup tunnel as follows:

· For SBFD sessions in control packet mode, the device uses the SBFD session parameter settings configured on the tunnel interface by using the mpls bfd backup min-receive-interval, mpls bfd backup min-transmit-interval, and mpls bfd backup detect-multiplier commands. If those commands are not configured on the tunnel interface, the device uses the multihop SBFD session parameter settings configured in system view.

· For SBFD sessions in echo packet mode, the device uses the SBFD session parameter settings configured on the tunnel interface by using the mpls bfd backup min-receive-interval command. If that command is not configured on the tunnel interface, the device uses the system default SBFD session settings.

source-ip ipv4-address: Specifies the source IP address of the SBFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the SBFD session.

Usage guidelines

Execute this command on the initiator of an SBFD session.

After you enable BFD for MPLS and execute the mpls sbfd command, the device creates an SBFD session for the MPLS TE tunnel. When the MPLS TE tunnel fails, SBFD can quickly detect the failure and notify the device to take an action, such as switching traffic to the backup tunnel.

If you do not specify the echo or reverse-lsp keyword, this command enables the SBFD control packet mode to verify the MPLS TE tunnel connectivity.

When SBFD control packet mode is used, an SBFD session can be established in static mode.

· If you specify a remote discriminator in the mpls sbfd command, the device uses the specified remote discriminator to establish a static SBFD session.

· If you do not specify a remote discriminator in the mpls sbfd command, the device uses the tunnel's remote IP address as the remote discriminator to establish a static SBFD session.

The SBFD echo packet mode supports verifying connectivity only for bidirectional MPLS TE tunnels.

The source address of the SBFD session can be specified manually, or if not specified, is the MPLS LSR ID of the initiator. Before configuring SBFD for an MPLS TE tunnel, make sure a route is available on the reflector to reach the source address of the SBFD session.

Examples

# Enable SBFD to verify tunnel connectivity on MPLS TE tunnel interface Tunnel 1, set the remote discriminator to 1, and use SBFD session parameter template test.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls sbfd remote 1 template test

Related commands

display mpls bfd

mpls bfd enable

sbfd local-discriminator (High Availability Command Reference)

mpls sbfd flex-algo-lsp

Use mpls sbfd flex-algo-lsp to enable SBFD for Flex-Algo LSPs.

Use undo mpls sbfd flex-alg-lsp to disable SBFD for SBFD for Flex-Algo LSPs.

Syntax

mpls sbfd flex-algo-lsp dest-address mask-length algorithm flex-algo-id-begin [ to flex-algo-id-end ] [ template template-name ]

undo mpls sbfd flex-algo-lsp dest-address mask-length algorithm flex-algo-id-begin [ to flex-algo-id-end ]

Default

SBFD is not used to verify the Flex-Algo LSP connectivity.

Views

System view

Predefined user roles

network-admin

Parameters

dest-addr: Destination address of an Flex-Algo LSP.

mask-length: Mask length of the destination address, in the range of 0 to 32.

algorithm flex-algo-id-begin [ to flex-algo-id-end ]: Specifies the Flex-Algos used to calculate LSPs. The flex-algo-id-begin argument represents the start Flex-Algo ID. The flex-algo-id-end argument represents the end Flex-Algo ID.

Usage guidelines

Execute this command on the initiator of an SBFD session.

After you execute the mpls bfd enable command and then the mpls sbfd flex-algo-lsp command, the device creates an SBFD session for the LSP destined for the specified address and calculated by the specified Flex-Algos. When the LSP fails, SBFD can quickly detect the failure and notify the device to take an action, such as switching traffic to the backup LSP.

An SBFD session can be established in static mode. The device uses the Flex-Algo LSP's destination address as the remote discriminator to establish a static SBFD session.

The destination address specified by the mpls sbfd flex-algo-lsp command on the initiator must be the same as the local discriminator specified by the sbfd local-discriminator command on the reflector. Otherwise, the reflector will not respond to the initiator.

The source address of the SBFD session is the MPLS LSR ID of the local device. Before configuring SBFD for LSPs, perform the following tasks:

· Configure an MPLS LSR ID for the local device.

· Make sure a route is available on the remote device to reach the MPLS LSR ID.

Examples

# Use SBFD to verify the connectivity of the LSP destined for 22.22.2.2/32 and calculated by Flex-Algo 128.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls sbfd flex-algo-lsp 22.22.2.2 32 algorithm 128

Related commands

display mpls sbfd

mpls bfd enable

sbfd local-discriminator (High Availability Command Reference)

mpls te bfd detect-multiplier

Use mpls te bfd detect-multiplier to set the BFD detection time multiplier for PCE-initiated tunnels.

Use undo mpls te bfd detect-multiplier to restore the default.

Syntax

mpls te bfd detect-multiplier value

undo mpls te bfd detect-multiplier

Default

The BFD detection time multiplier is not set for PCE-initiated tunnels. The BFD detection time multiplier set by the bfd multi-hop detect-multiplier command applies.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

The device sends BFD packets to a peer periodically. If the device does not receive BFD packets from the peer within the actual detection interval, it determines that the session is down. The actual detection interval of the sender is the detection time multiplier of the receiver × the actual sending interval of the receiver.

This command takes effect only on BFD sessions created by the mpls te bfd enable pce-initiated-lsp command.

Examples

# Set the BFD detection time multiplier to 3 for PCE-initiated tunnels.

<Sysname> system-view

[Sysname] mpls te bfd detect-multiplier 3

Related commands

bfd multi-hop detect-multiplier (High Availability Command Reference)

mpls te bfd enable pce-initiated-lsp

Use mpls te bfd enable pce-initiated-lsp to enable BFD for PCE-initiated tunnels.

Use undo mpls te bfd enable pce-initiated-lsp to disable BFD for PCE-initiated tunnels.

Syntax

mpls te bfd enable pce-initiated-lsp { rsvp | segment-routing }

undo mpls te bfd enable pce-initiated-lsp { rsvp | segment-routing }

Default

BFD for PCE-initiated tunnels is not enabled.

Views

System view

Predefined user roles

network-admin

Parameters

rsvp: Specifies the PCE-initiated RSVP-TE tunnels.

segment-routing: Specifies the PCE-initiated SR tunnels.

Usage guidelines

This command enables the device to create a BFD session for each PCE-initiated primary RSVP-TE or SR tunnel to detect the primary tunnel connectivity.

When a primary RSVP-TE or SR tunnel fails, BFD can quickly detect the failure and switches traffic to the backup tunnel to reduce packet loss.

If you execute both the mpls te bfd enable pce-initiated-lsp command and the mpls bfd command for a PCE-initiated tunnel, the mpls bfd command takes effect on the tunnel.

Examples

# Enable BFD for PCE-initiated RSVP-TE tunnels.

<Sysname> system-view

[Sysname] mpls te bfd enable pce-initiated-lsp rsvp

Related commands

mpls bfd (for TE Tunnel)

mpls te bfd min-receive-interval

Use mpls te bfd min-receive-interval to set the minimum interval for PCE-initiated tunnels to receive BFD packets.

Use undo mpls te bfd min-receive-interval to restore the default.

Syntax

mpls te bfd min-receive-interval interval

undo mpls te bfd min-receive-interval

Default

The minimum interval for receiving BFD packets is not set for PCE-initiated tunnels. The interval set by the bfd multi-hop min-receive-interval command applies.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the packet sending rate of the peer end from exceeding the packet receiving rate of the local end. If the receiving rate is exceeded, the peer end dynamically adjusts the BFD packet transmitting interval to the minimum receiving interval of the local end.

This command takes effect only on BFD sessions created by the mpls te bfd enable pce-initiated-lsp command.

Examples

# Set the minimum BFD packet receiving interval of PCE-initiated tunnels to 30 milliseconds.

<Sysname> system-view

[Sysname] mpls te bfd min-receive-interval 30

Related commands

bfd multi-hop min-receive-interval (High Availability Command Reference)

mpls te bfd enable pce-initiated-lsp

mpls te bfd min-transmit-interval

Use mpls te bfd min-transmit-interval to set the minimum interval for PCE-initiated tunnels to transmit BFD packets.

Use undo mpls te bfd min-transmit-interval to restore the default.

Syntax

mpls te bfd min-transmit-interval interval

undo mpls te bfd min-transmit-interval

Default

The minimum interval for transmitting BFD packets is not set for PCE-initiated tunnels. The interval set by the bfd multi-hop min-transmit-interval command applies.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

This command takes effect only on BFD sessions created by the mpls te bfd enable pce-initiated-lsp command.

Examples

# Set the minimum BFD packet transmitting interval of PCE-initiated tunnels to 30 milliseconds.

<Sysname> system-view

[Sysname] mpls te bfd min-transmit-interval 30

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

mpls te bfd enable pce-initiated-lsp

mpls te tunnel-bfd detect-multiplier

Use mpls te tunnel-bfd detect-multiplier to set the tunnel BFD detection time multiplier for PCE-initiated tunnels.

Use undo mpls te tunnel-bfd detect-multiplier to restore the default.

Syntax

mpls te tunnel-bfd detect-multiplier value

undo mpls te tunnel-bfd detect-multiplier

Default

The tunnel BFD detection time multiplier is not set for PCE-initiated tunnels. The multiplier set by the bfd multi-hop detect-multiplier command applies.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

This command takes effect only on BFD sessions created by the mpls te tunnel-bfd enable command.

Examples

# Set the tunnel BFD detection time multiplier to 3 for PCE-initiated tunnels.

<Sysname> system-view

[Sysname] mpls te tunnel-bfd detect-multiplier 3

Related commands

bfd multi-hop detect-multiplier (High Availability Command Reference)

mpls te tunnel-bfd enable

Use mpls te tunnel-bfd enable pce-initiated-lsp to enable tunnel BFD for PCE-initiated tunnels.

Use undo mpls te tunnel-bfd enable pce-initiated-lsp to disable tunnel BFD for PCE-initiated tunnels.

Syntax

mpls te tunnel-bfd enable pce-initiated-lsp { rsvp | segment-routing }

undo mpls te tunnel-bfd enable pce-initiated-lsp { rsvp | segment-routing }

Default

Tunnel BFD for PCE-initiated tunnels is not enabled.

Views

System view

Predefined user roles

network-admin

Parameters

rsvp: Specifies the PCE-initiated RSVP-TE tunnels.

segment-routing: Specifies the PCE-initiated SR tunnels.

Usage guidelines

This command enables the device to create a tunnel BFD session for each PCE-initiated RSVP-TE or SR tunnel to detect the tunnel connectivity.

A tunnel BFD session detects the primary path and all its backup paths of a PCE-initiated RSVP-TE or SR tunnel. The BFD session remains in up state as long as one of the paths is available. When all the primary and backup paths fail, the BFD session is placed to down state. BFD can quickly detect the failure and trigger another protection measure (such as MPLS L3VPN FRR) to switch traffic to an available forwarding path.

If you execute both the mpls te tunnel-bfd enable command and the mpls tunnel-bfd command for a PCE-initiated tunnel, the mpls tunnel-bfd command takes effect on the tunnel.

Examples

# Enable tunnel BFD for PCE-initiated RSVP-TE tunnels.

<Sysname> system-view

[Sysname] mpls te tunnel-bfd enable pce-initiated-lsp rsvp

Related commands

mpls tunnel-bfd (for TE Tunnel)

mpls te tunnel-bfd min-receive-interval

Use mpls te tunnel-bfd min-receive-interval to set the tunnel BFD minimum receiving interval for PCE-initiated tunnels.

Use undo mpls te tunnel-bfd min-receive-interval to restore the default.

Syntax

mpls te tunnel-bfd min-receive-interval interval

undo mpls te tunnel-bfd min-receive-interval

Default

The tunnel BFD minimum receiving interval is not set for PCE-initiated tunnels. The interval set by the bfd multi-hop min-receive-interval command applies.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the packet sending rate of the peer end from exceeding the packet receiving rate of the local end. If the receiving rate is exceeded, the peer end dynamically adjusts the BFD packet transmitting interval to the minimum receiving interval of the local end.

This command takes effect only on BFD sessions created by the mpls te tunnel-bfd enable command.

Examples

# Set the tunnel BFD minimum receiving interval to 30 milliseconds for PCE-initiated tunnels.

<Sysname> system-view

[Sysname] mpls te tunnel-bfd min-receive-interval 30

Related commands

bfd multi-hop min-receive-interval (High Availability Command Reference)

mpls te tunnel-bfd enable

mpls te tunnel-bfd min-transmit-interval

Use mpls te tunnel-bfd min-transmit-interval to set the tunnel BFD minimum transmitting interval for PCE-initiated tunnels.

Use undo mpls te tunnel-bfd min-transmit-interval to restore the default.

Syntax

mpls te tunnel-bfd min-transmit-interval interval

undo mpls te tunnel-bfd min-transmit-interval

Default

The tunnel BFD minimum transmitting interval is not set for PCE-initiated tunnels. The interval set by the bfd multi-hop min-transmit-interval command applies.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

This command takes effect only on BFD sessions created by the mpls te bfd enable pce-initiated-lsp command.

Examples

# Set the minimum BFD packet transmitting interval of PCE-initiated tunnels to 30 milliseconds.

<Sysname> system-view

[Sysname] mpls te bfd min-transmit-interval 30

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

mpls te tunnel-bfd enable

mpls tunnel-bfd (for LSP)

Use mpls tunnel-bfd to enable tunnel BFD for LSPs associated with an FEC.

Use undo mpls tunnel-bfd to disable tunnel BFD for LSPs associated with an FEC.

Syntax

mpls tunnel-bfd dest-addr mask-length discriminator local local-id remote remote-id [ bgp-lsp | isis-srlsp | ldp-lsp | ospf-srlsp | static-lsp ] [ template template-name ]

mpls tunnel-bfd dest-addr mask-length [ echo | ldp-fec | nil-fec ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls tunnel-bfd dest-addr mask-length

Default

Tunnel BFD is not used to verify LSP connectivity for an FEC.

Views

System view

Predefined user roles

network-admin

Parameters

dest-addr mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

discriminator: Specifies discriminator values for the BFD session.

local local-id: Specifies the local discriminator value for the BFD session, in the value range of 1 to 32768.

remote remote-id: Specifies the remote discriminator value for the BFD session, in the range of 1 to 4294967295.

bgp-lsp: Specifies BGP LSP.

isis-srlsp: Specifies IS-IS SRLSP.

ldp-lsp: Specifies LDP LSP.

ospf-srlsp: Specifies OSPF SRLSP.

static-lsp: Specifies static LSP.

echo: Specifies the BFD echo packet mode. If you do not specify this keyword, the BFD control packet mode is used to verify LSP connectivity.

nil-fec: Encapsulates the Nil FEC in MPLS echo request packets when BFD control packet mode is used to detect LSPs. In LDP to SR interworking mode, the ingress node (source node) cannot determine whether the LDP LSP is connected to the SRLSP. When the ingress node uses MPLS BFD to detect LSPs, it encapsulates LDP FEC in MPLS echo request packets, which will fail the FEC type verification on the egress node (end-point node). Then, the BFD session will go down. To resolve this issue, specify the nil-fec keyword to enable the ingress node to encapsulate the Nil FEC in MPLS echo request packets. The egress node will not check the FEC type of packets encapsulated with the Nil FEC.

source-ip ipv4-address: Specifies the source IP address of the BFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the BFD session.

Usage guidelines

The mpls bfd command can detect only the primary LSP failure. When the primary LSP fails, BFD can quickly detect the failure and notify the device to switch traffic to the backup LSP. When both the primary and backup LSPs fail, the BFD detection mechanism fails. Traffic is lost until another mechanism detects the failures and triggers a traffic protection measure (such as MPLS L3VPN ECMP route based load balancing and FRR) to take effect.

To resolve this issue, you can execute the mpls tunnel-bfd command to configure tunnel BFD, which detects failures on the primary LSP and all the backup LSPs. When both the primary LSP and current backup LSP fail, tunnel BFD can quickly detect the failures and trigger a traffic protection measure to switch traffic to an available backup LSP.

The source address of the BFD session can be specified manually, or if not specified, is the MPLS LSR ID of the local device. Before configuring tunnel BFD for an LSP tunnel, make sure a route is available on the remote device to reach the source address of the BFD session.

When BFD control packet mode is used to verify LSP connectivity, a BFD session can be established in one of the following modes:

· Static mode—Specify the local and remote discriminator values by using the discriminator keyword in the mpls tunnel-bfd command. You must enable BFD for MPLS and execute the mpls tunnel-bfd command on both the local and remote devices. Make sure the discriminators configured on the local device match those configured on the remote device. A static BFD session verifies connectivity of a pair of LSPs in opposite directions between two devices.

· Dynamic mode—If you do not specify local and remote discriminators, the system automatically runs MPLS ping to negotiate the discriminator values. You must enable BFD for MPLS on both the local and remote devices, but the mpls tunnel-bfd command is not needed on the remote device. A dynamic BFD session verifies the connectivity of a unidirectional LSP from the local device to the remote device.

To enable the BFD echo packet mode, you must first execute the bfd echo-source-ip command on the local device to specify a source IP address for BFD echo packets.

If you do not specify the bgp-lsp, isis-srlsp, ldp-lsp, ospf-srlsp, or static-lsp keyword, BFD detects LSPs in static LSP, LDP LSP, BGP LSP, OSPF SRLSP, and IS-IS SRLSP order. The BFD session is up as long as one LSP is operating correctly. The BFD session goes down when all LSPs fail.

When a primary LSP and its backup LSP are of different types, if the LSP type specified for BFD is the type of the backup LSP, BFD detects only the backup LSP.

Examples

# Use tunnel BFD to verify the connectivity of the LSPs to destination 22.22.2.2/32.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] mpls bfd 22.22.2.2 32

Related commands

display mpls bfd

mpls bfd enable

mpls tunnel-bfd (for TE tunnel)

Use mpls tunnel-bfd to enable tunnel BFD on an MPLS TE tunnel interface.

Use undo mpls tunnel-bfd to restore the default.

Syntax

mpls tunnel-bfd discriminator local local-id remote remote-id [ template template-name ]

mpls tunnel-bfd [ echo | reverse-lsp binding-sid label label-value ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls tunnel-bfd

Default

Tunnel BFD is not used to verify MPLS TE tunnel connectivity on a tunnel interface.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

discriminator: Specifies discriminator values for the BFD session.

local local-id: Specifies the local discriminator value for the BFD session, in the range of 1 to 32768.

remote remote-id: Specifies the remote discriminator value for the BFD session, in the range of 1 to 4294967295.

echo: Enables the BFD echo packet mode.

source-ip ipv4-address: Specifies the source IP address of the BFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the BFD session.

Usage guidelines

In an MPLS TE CRLSP backup scenario, you can use the mpls bfd command to create a BFD session for the primary and backup CRLSPs, respectively. When the primary CRLSP fails, BFD can quickly detect the failure and notify the device to switch traffic to the backup CRLSP. When both the primary and backup CRLSPs fail, the BFD detection mechanism fails. Traffic is lost until another mechanism detects the failure and triggers a traffic protection measure (such as MPLS L3VPN ECMP route based load balancing and FRR) to take effect.

To resolve this issue, you can execute the mpls tunnel-bfd command to configure tunnel BFD, which detects failures on the primary CRLSP and all the backup CRLSPs. When both the primary CRLSP and the current backup CRLSP fail, tunnel BFD can quickly detect the failures and trigger a traffic protection measure to switch traffic to an available backup CRLSP.

The source address of the BFD session can be specified manually, or if not specified, is the MPLS LSR ID of the local device. Before configuring tunnel BFD for an MPLS TE tunnel, make sure a route is available on the remote device to reach the source address of the BFD session.

If you do not specify the echo or reverse-lsp keyword, this command enables the BFD control packet mode to verify the MPLS TE tunnel connectivity.

When BFD control packet mode is used, a BFD session can be established in one of the following modes:

· Static mode—Specify the local and remote discriminators by using the discriminator keyword in the mpls tunnel-bfd command. You must execute the mpls bfd enable and mpls tunnel-bfd commands on both the local and remote devices. Make sure the local discriminator and remote discriminator on the local device are the same as the remote discriminator and local discriminator on the remote device, respectively. A static BFD session verifies the connectivity of a pair of MPLS TE tunnels in opposite directions between two devices.

· Dynamic mode—If you do not specify local and remote discriminators, the system automatically runs MPLS ping to negotiate the discriminator values. You must execute the mpls bfd enable command on both the local and remote devices, but the mpls tunnel-bfd command is not needed on the remote device. A dynamic BFD session verifies the connectivity of a unidirectional MPLS TE tunnel from the local device to the remote device.

To enable the BFD echo packet mode, you must first execute the bfd echo-source-ip command on the local device to specify a source IP address for BFD echo packets.

After you execute the mpls tunnel-bfd command, use one of the following commands to disable MPLS BFD from triggering tunnel-down to avoid tunnel flapping:

· mpls bfd trigger tunnel-down disable (in tunnel interface view)

· undo mpls bfd trigger tunnel-down enable (in MPLS TE view)

Examples

# Enable tunnel BFD to verify tunnel connectivity on MPLS TE tunnel interface Tunnel 1, and use the BFD session parameter template test.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls tunnel-bfd template test

Related commands

display mpls bfd

mpls bfd enable

mpls tunnel-bfd detect-multiplier

Use mpls tunnel-bfd detect-multiplier to set the tunnel BFD and tunnel SBFD detection time multiplier for an MPLS TE tunnel.

Use undo mpls tunnel-bfd detect-multiplier to restore the default.

Syntax

mpls tunnel-bfd detect-multiplier value

undo mpls tunnel-bfd detect-multiplier

Default

The tunnel BFD and tunnel SBFD detection time multiplier is not set for an MPLS TE tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

For tunnel BFD on an MPLS TE tunnel:

· If the mpls tunnel-bfd detect-multiplier command and the mpls tunnel-bfd command with the template keyword are both executed in the tunnel interface view, the mpls tunnel-bfd command takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop detect-multiplier command's configuration is used.

For tunnel SBFD on an MPLS TE tunnel:

· If the mpls bfd detect-multiplier command and the mpls tunnel-sbfd command with the template keyword are both executed in the tunnel interface view, the mpls tunnel-sbfd command takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop detect-multiplier command's configuration is used.

Examples

# Set the tunnel BFD and tunnel SBFD detection time multiplier to 3 for MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls tunnel-bfd detect-multiplier 3

Related commands

bfd detect-multiplier (High Availability Command Reference)

bfd multi-hop detect-multiplier (High Availability Command Reference)

display mpls bfd

display mpls sbfd

mpls bfd enable

mpls tunnel-bfd (for TE tunnel)

mpls tunnel-sbfd (for TE tunnel)

mpls tunnel-bfd min-receive-interval

Use mpls tunnel-bfd min-receive-interval to set the minimum receiving interval for tunnel BFD and tunnel SBFD on an MPLS TE tunnel.

Use undo mpls tunnel-bfd min-receive-interval to restore the default.

Syntax

mpls tunnel-bfd min-receive-interval interval

undo mpls tunnel-bfd min-receive-interval

Default

The minimum receiving interval is not set for tunnel BFD and tunnel SBFD on an MPLS TE tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

For tunnel BFD on an MPLS TE tunnel:

· If the mpls tunnel-bfd min-receive-interval command and the mpls tunnel-bfd command with the template keyword are both executed in the tunnel interface view, the mpls tunnel-bfd command takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-receive-interval command's configuration is used.

For tunnel SBFD on an MPLS TE tunnel:

· If the mpls tunnel-bfd min-receive-interval command and the mpls tunnel-sbfd command with the template keyword are both executed in the tunnel interface view, the mpls tunnel-sbfd command takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-receive-interval command's configuration is used.

Examples

# Set the minimum BFD packet receiving interval to 550 milliseconds for tunnel BFD and tunnel SBFD on MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls tunnel-bfd min-receive-interval 550

Related commands

bfd min-echo-receive-interval (High Availability Command Reference)

bfd multi-hop min-receive-interval (High Availability Command Reference)

display mpls bfd

display mpls sbfd

mpls bfd enable

mpls tunnel-bfd (for TE tunnel)

mpls tunnel-sbfd (for TE tunnel)

mpls tunnel-bfd min-transmit-interval

Use mpls tunnel-bfd min-transmit-interval to set the minimum transmit interval for tunnel BFD and tunnel SBFD on an MPLS TE tunnel.

Use undo mpls tunnel-bfd min-transmit-interval to restore the default.

Syntax

mpls tunnel-bfd min-transmit-interval interval

undo mpls tunnel-bfd min-transmit-interval

Default

The minimum transmit interval is not set for tunnel BFD and tunnel SBFD on an MPLS TE tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

For tunnel BFD on an MPLS TE tunnel:

· If the mpls tunnel-bfd min-transmit-interval command and the mpls tunnel-bfd command with the template keyword are both executed in the tunnel interface view, the mpls tunnel-bfd command takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-transmit-interval command's configuration is used.

For tunnel SBFD on an MPLS TE tunnel:

· If the mpls tunnel-bfd min-transmit-interval command and the mpls tunnel-sbfd command with the template keyword are both executed in the tunnel interface view, the mpls tunnel-sbfd command takes effect.

· If that two commands are both not executed in the tunnel interface view, the bfd multi-hop min-transmit-interval command's configuration is used.

Examples

# Set the minimum BFD packet transmitting interval to 450 milliseconds for tunnel BFD and tunnel SBFD on MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls tunnel-bfd min-transmit-interval 450

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

display mpls bfd

display mpls sbfd

mpls bfd enable

mpls tunnel-bfd (for TE tunnel)

mpls tunnel-sbfd (for TE tunnel)

Use mpls tunnel-bfd to enable tunnel SBFD on an MPLS TE tunnel.

Use undo mpls tunnel-bfd to restore the default.

Syntax

mpls tunnel-sbfd [ echo | remote remote-id | reverse-lsp binding-sid label label-value ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls tunnel-sbfd

Default

Tunnel SBFD is not used to verify MPLS TE tunnel connectivity.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

remote remote-id: Specifies the remote discriminator value for the SBFD session, in the range of 1 to 4294967295. If you do not specify this option, the SBFD session uses the tunnel's remote IP address as the remote discriminator.

echo: Enables the SBFD echo packet mode to verify the connectivity of a bidirectional MPLS TE tunnel.

template template-name: Specifies an SBFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a template, the SBFD session uses the SBFD session settings configured in tunnel interface view.

source-ip ipv4-address: Specifies the source IP address of the SBFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the SBFD session.

Usage guidelines

In an MPLS TE network, you can use the mpls sbfd command to create an SBFD session for the primary and backup paths of the MPLS TE tunnel, respectively. When the primary path fails, BFD can quickly detect the failure and notify the device to switch traffic to the backup path. When both the primary and backup paths fail, the SBFD detection mechanism fails. Traffic is lost until another mechanism detects the failure and triggers a traffic protection measure (such as MPLS L3VPN ECMP route based load balancing and FRR) to take effect.

To resolve this issue, you can execute the mpls tunnel-sbfd command to configure tunnel SBFD, which detects failures on the primary path and all the backup paths. When both the primary path and the current backup path fail, tunnel BFD can quickly detect the failures and trigger a traffic protection measure to switch traffic to an available backup path.

Execute the mpls tunnel-sbfd command on the initiator of the SBFD session. Before executing the mpls tunnel-sbfd command, you must first enable BFD for MPLS on the initiator by using the mpls bfd enable command.

If you do not specify the echo or reverse-lsp keyword, this command enables the BFD control packet mode to verify the MPLS TE tunnel connectivity.

When BFD control packet mode is used, an SBFD session can be established in static mode.

· If you specify a remote discriminator in the mpls tunnel-sbfd command, the device uses the specified remote discriminator to establish a static SBFD session.

· If you do not specify a remote discriminator in the mpls tunnel-sbfd command, the device uses the tunnel's remote IP address as the remote discriminator to establish a static SBFD session.

The SBFD echo packet mode supports verifying connectivity only for bidirectional MPLS TE tunnels.

The remote discriminator specified by the mpls tunnel-sbfd command on the initiator must be the same as the local discriminator specified by the sbfd local-discriminator command on the reflector. Otherwise, the reflector will not respond to the initiator.

The source address of the SBFD session can be specified manually, or if not specified, is the MPLS LSR ID of the initiator. Before configuring tunnel SBFD for an MPLS TE tunnel, make sure a route is available on the reflector to reach the source address of the SBFD session.

After you execute the mpls tunnel-sbfd command, use one of the following commands to disable MPLS BFD from triggering tunnel-down to avoid tunnel flapping:

· mpls bfd trigger tunnel-down disable (in tunnel interface view)

· undo mpls bfd trigger tunnel-down enable (in MPLS TE view)

Examples

# Enable tunnel SBFD to verify tunnel connectivity on MPLS TE tunnel interface Tunnel 1, and use the BFD session parameter template test.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls tunnel-sbfd remote 1 template test

Related commands

display mpls sbfd

mpls bfd enable

mpls tunnel-bfd detect-multiplier

mpls tunnel-bfd min-receive-interval

mpls tunnel-bfd min-transmit-interval

sbfd local-discriminator (High Availability Command Reference)

ping mpls ipv4

Use ping mpls ipv4 to verify MPLS LSP connectivity for an IPv4 prefix.

Syntax

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * ipv4 ipv4-address mask-length [ nexthop nexthop-address ] [ destination start-address [ end-address [ address-increment ] ] ] [ fec-type { bgp | generic | isis | ldp | ospf } ] [ remote-fec { ldp remote-ip-addr remote-mask-len | nil } ]

Views

Any view

Predefined user roles

network-admin

Parameters

-a source-ip: Specifies the source address of MPLS echo request packets. If you do not specify this option, the device uses the primary IP address of the outgoing interface as the source address for MPLS echo requests.

-c count: Specifies the number of MPLS echo request packets to be sent with the same destination address in the IP header. The value range is 1 to 4294967295. The default is 5.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the TTL value of MPLS echo request packets, in the range of 1 to 255. The default is 255.

-m wait-time: Specifies the interval for sending MPLS echo request packets, in the range of 1 to 10000 milliseconds. The default is 200 milliseconds.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 1, 2, 3, or 4. The default is 2.

· 1—Do not reply.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet. The reply mode 4 is not available for MPLS LSP connectivity verification. If the reply mode 4 is specified, the remote end does not reply.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-s packet-size: Specifies the length (excluding the IP header and UDP header) of an MPLS echo request packet. The value for the packet-size argument is 65 to 8100 bytes, and the default is 100 bytes.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

ipv4-address mask-length: Specifies an FEC by a destination IP address and mask length. The mask length is in the range of 0 to 32.

nexthop nexthop-address: Specifies the next hop IP address. If an FEC has multiple next hops, you can use this option to specify a next hop for the ping operation.

destination: Specifies the destination address in the IP header of MPLS echo requests. The default is 127.0.0.1.

start-address: Specifies the destination address or the start destination address. This address must be an address on subnet 127.0.0.0/8—a local loopback address. If you specify the start-address argument without the end-address argument, the start-address is the destination address in the IP header. The number of MPLS echo requests to be sent is determined by the -c count keyword. If you specify both start-address and end-address, you specify a range of destination addresses. The destination address increments by the value specified for the address-increment argument, starting from the start-address to the end-address. The number of MPLS echo requests to be sent with each of the destination addresses is determined by the -c count keyword.

end-address: Specifies the end destination address. This address must be an address on subnet 127.0.0.0/8—a local loopback address.

address-increment: Specifies the increment value by which the destination address in the IP header increases in turn. The value range is 1 to 16777215 and the default value is 1.

fec-type: Specifies the FEC type of the MPLS LSPs to be verified. If you do not specify this keyword, the FEC type is the protocol type of the specified FEC in the routing table.

bgp: Represents BGP signaled LSPs.

generic: Represents LSPs of any FEC type.

is-is: Represents IS-IS signaled SRLSPs.

ldp: Represents LDP signaled LSPs.

ospf: Represents OSPF signaled SRLSPs.

remote-fec: Specifies the remote FEC type. To test the complete path of an LSP that belongs to different FEC types, you need to specify the FEC type used in the remote network.

ldp remote-ip-addr remote-mask-len: Specifies the IP address and mask length of the remote LDP FEC. The value range for the mask length is 0 to 32. This option is used in SR to LDP interworking scenarios. For more information about SR to LDP interworking, see the SR-MPLS configuration in MPLS Configuration Guide.

nil: Specifies the Nil FEC. If the remote FEC type is unknown, specify this keyword in to avoid LSP ping failure caused by FEC type verification failure on the egress node.

Examples

# Verify the connectivity of LSPs to destination 3.3.3.9/32.

<Sysname> ping mpls ipv4 3.3.3.9 32

MPLS ping FEC 3.3.3.9/32 with 100 bytes of data:

100 bytes from 100.1.2.1: Sequence=1 time=49 ms

100 bytes from 100.1.2.1: Sequence=2 time=44 ms

100 bytes from 100.1.2.1: Sequence=3 time=60 ms

100 bytes from 100.1.2.1: Sequence=4 time=60 ms

100 bytes from 100.1.2.1: Sequence=5 time=76 ms

--- Ping statistics for FEC 3.3.3.9/32 ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 44/57/76 ms

# Verify the connectivity of LSPs to destination 3.3.3.9/32, and specify the following parameters:

· Set the number of MPLS echo requests to be sent with the same destination address to 3.

· Display detailed reply information.

· Specify the range of destination addresses in IP headers as 127.0.0.1 to 127.0.0.3, and set the destination address increment value to 2. With these settings, the destination addresses are 127.0.0.1 and 127.0.0.3.

<Sysname> ping mpls –c 3 –v ipv4 3.3.3.9 32 destination 127.0.0.1 127.0.0.3 2

MPLS ping FEC 3.3.3.9/32 with 100 bytes of data:

Destination address 127.0.0.1

100 bytes from 100.1.2.1: Sequence=1 time=49 ms Return Code=3(1)

Destination address 127.0.0.3

100 bytes from 100.1.2.1: Sequence=2 time=44 ms Return Code=3(1)

Destination address 127.0.0.1

100 bytes from 100.1.2.1: Sequence=3 time=60 ms Return Code=3(1)

Destination address 127.0.0.3

100 bytes from 100.1.2.1: Sequence=4 time=60 ms Return Code=3(1)

Destination address 127.0.0.1

100 bytes from 100.1.2.1: Sequence=5 time=76 ms Return Code=3(1)

Destination address 127.0.0.3

100 bytes from 100.1.2.1: Sequence=6 time=57 ms Return Code=3(1)

--- Ping statistics for FEC 3.3.3.9/32 ---

6 packets transmitted, 6 packets received, 0.0% packet loss

Round-trip min/avg/max = 44/57/76 ms

Table 4 Command output

Field	Description
MPLS Ping FEC: 3.3.3.9/32 with 100 bytes of data	Verify LSP connectivity for FEC 3.3.3.9/32 by sending 100-byte MPLS echo requests.
Destination address	Destination IP address in the IP header.
100 bytes from 100.1.2.1	Received a 100-byte reply from 100.1.2.1.
Sequence	Sequence number of the reply, for determination of packet loss, disorder, or duplicate.
time	Packet round-trip delay.
Return Code	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.
Ping statistics for FEC 3.3.3.9/32	LSP verification statistics.
packets transmitted	Number of MPLS echo requests sent.
packets received	Number of MPLS echo replies received.
packet loss	Percentage of unreplied packets to total request packets.
Round-trip min/avg/max	Minimum, average, and maximum round-trip delay.

‌

ping mpls out-labels

Use ping mpls out-labels to verify the MPLS LSP of the specified outgoing labels.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

-c count: Specifies the number of MPLS echo request packets to be sent with the same destination address in the IP header. The value range is 1 to 4294967295. The default is 5.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the TTL value of MPLS echo request packets, in the range of 1 to 255. The default is 255.

-m wait-time: Specifies the interval for sending MPLS echo request packets, in the range of 1 to 10000 milliseconds. The default is 200 milliseconds.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 1, 2, 3, or 4. The default is 2.

· 1—Do not reply.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet. The reply mode 4 is not available for MPLS LSP connectivity verification. If the reply mode 4 is specified, the remote end does not reply.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-s packet-size: Specifies the length (excluding the IP header and UDP header) of an MPLS echo request packet. The value for the packet-size argument is 65 to 8100 bytes, and the default is 100 bytes.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

out-labels out-label-value&<1-15>: Specifies a space-separated list of up to 15 outgoing labels, corresponding to the labels from top to bottom in the label stack. The value range for the out-label-value argument is 0, 3, and 16 to 1048575.

interface interface-type interface-number: Specifies the outgoing interface by the interface type and number.

nexthop nexthop-address: Specifies the next hop IP address.

Usage guidelines

To verify connectivity of a specific LSP, first execute the display mpls lsp command to identify the outgoing interface and next hop for the outgoing labels to be specified.

Examples

# Verify the connectivity of the LSP with outgoing label 2173, outgoing interface Ten-GigabitEthernet 3/1/1, and next hop IP address 10.1.1.2/32 in an LDP network.

<Sysname> ping mpls out-labels 2173 interface ten-gigabitethernet 3/1/1 nexthop 10.1.1.2

MPLS ping out-labels 2173 with 100 bytes of data:

100 bytes from 20.1.1.2: Sequence=1 time=1 ms

100 bytes from 20.1.1.2: Sequence=2 time=1 ms

100 bytes from 20.1.1.2: Sequence=3 time=1 ms

100 bytes from 20.1.1.2: Sequence=4 time=1 ms

100 bytes from 20.1.1.2: Sequence=5 time=1 ms

--- Ping statistics for out-labels 2173 ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 1/1/1 ms

<Sysname>%Oct 11 09:26:52:882 2018 Sysname LSPV/6/LSPV_PING_STATIS_INFO: -MDC=1; Ping statistics for out-labels 2173: 5 packets transmitted, 5 packets received, 0.0% packets loss, round-trip min/avg/max = 1/1/1 ms.

# Configure the source node to verify the LSP with outgoing label 17030, outgoing interface Ten-GigabitEthernet 3/1/2, and next hop 100.1.1.2/32 in an SR-MPLS to LDP interworking network.

<Sysname> ping mpls out-labels 17030 interface ten-gigabitethernet 3/1/2 nexthop 100.1.1.2

MPLS ping out-labels 17030 with 100 bytes of data:

100 bytes from 20.1.1.2: Sequence=1 time=3 ms

100 bytes from 20.1.1.2: Sequence=2 time=2 ms

100 bytes from 20.1.1.2: Sequence=3 time=2 ms

100 bytes from 20.1.1.2: Sequence=4 time=2 ms

100 bytes from 20.1.1.2: Sequence=5 time=1 ms

--- Ping statistics for out-labels 17030 ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 1/2/3 ms

<Sysname>%Oct 11 10:12:45:434 2018 Sysname LSPV/6/LSPV_PING_STATIS_INFO: -MDC=1; Ping statistics for out-labels 17030: 5 packets transmitted, 5 packets received, 0.0% packets loss, round-trip min/avg/max = 1/2/3 ms.

Table 5 Command output

Field	Description
MPLS ping out-labels out-label-value with 100 bytes of data	Verify LSP connectivity for the specified outgoing labels (out-label-value) by sending 100-byte MPLS echo requests.
100 bytes from 20.1.1.2	Received a 100-byte reply from 20.1.1.2.
Sequence	Sequence number of the reply, for determination of packet loss, disorder, or duplicate.
time	Packet round-trip delay.
Return Code	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.
Ping statistics for out-labels	LSP verification statistics.
packets transmitted	Number of MPLS echo requests sent.
packets received	Number of MPLS echo replies received.
packet loss	Percentage of unreplied packets to total request packets.
Round-trip min/avg/max	Minimum, average, and maximum round-trip delay.

‌

ping mpls pw

Use ping mpls pw to verify LDP PW or static PW connectivity.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

-a source-ip: Specifies the source address of MPLS echo request packets. If you do not specify this option, the device uses its MPLS LSR ID as the source address of MPLS echo requests.

-c count: Specifies the number of MPLS echo request packets to be sent. The value range is 1 to 4294967295. The default is 5.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the TTL value of MPLS echo request packets, in the range of 1 to 255. The default is 255.

-m wait-time: Specifies the interval for sending MPLS echo request packets, in the range of 1 to 10000 milliseconds. The default is 200 milliseconds.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 1, 2, 3, or 4. The default is 2.

· 1—Do not reply.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-s packet-size: Specifies the length (excluding the IP header and UDP header) of an MPLS echo request packet. The value for the packet-size argument is 65 to 8100 bytes, and the default is 100 bytes.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

ip-address: Specifies the IP address of the peer PE.

pw-id pw-id: Specifies the ID of the PW to the peer PE, in the range of 1 to 4294967295.

remote remote-ip-address remote-pw-id: Specifies a multisegment PW. The remote-ip-address argument represents the IP address of the egress node of the multisegment PW. The remote-pw-id argument represents the ID of the last segment PW, in the range of 1 to 4294967295. This option is required only when the egress node of a multisegment PW supports verifying the Target FEC Stack TLV in an MPLS echo request. The device does not support the verification in the current software version.

Usage guidelines

To use this command to verify the connectivity of an LDP PW or a static PW, the PW must be created by using a PW class that specifies the VCCV CC type.

If you execute this command for a down PW, the ping operation might fail because of negotiation issues at the two ends of the PW. In this case, the device prompts not support for PW ping.

Examples

# Verify the connectivity of PW 301 to peer PE 3.3.3.9.

<Sysname> ping mpls pw 3.3.3.9 pw-id 301

MPLS ping PW 3.3.3.9 301 with 100 bytes of data:

100 bytes from 100.1.2.1: Sequence=1 time=49 ms

100 bytes from 100.1.2.1: Sequence=2 time=44 ms

100 bytes from 100.1.2.1: Sequence=3 time=60 ms

100 bytes from 100.1.2.1: Sequence=4 time=60 ms

100 bytes from 100.1.2.1: Sequence=5 time=76 ms

--- Ping statistics for PW 3.3.3.9 301 ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 44/57/76 ms

For the command output, see Table 4.

ping mpls sr-policy

Use ping mpls sr-policy to verify SR-MPLS TE policy connectivity.

Syntax

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * sr-policy { policy-name sr-policy-name | end-point ipv4 ip-address color color-value | binding-sid bsid }

Views

Any view

Predefined user roles

network-admin

Parameters

-a source-ip: Specifies the source address of SR-MPLS TE policy echo request packets. If you do not specify this option, the device uses the primary IP address of the outgoing interface as the source address of SR-MPLS TE policy echo requests.

-c count: Specifies the number of SR-MPLS TE policy echo request packets to be sent. The value range is 1 to 4294967295. The default is 5.

-exp exp-value: Specifies the EXP value of SR-MPLS TE policy echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the TTL value of SR-MPLS TE policy echo request packets, in the range of 1 to 255. The default is 255.

-m wait-time: Specifies the interval for sending SR-MPLS TE policy echo request packets, in the range of 1 to 10000 milliseconds. The default is 200 milliseconds.

-r reply-mode: Specifies the reply mode of the receiver in response to SR-MPLS TE policy echo request packets. The reply-mode argument can be 1, 2, 3, or 4. The default is 2.

· 1—Do not reply.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an SR-MPLS TE policy echo reply packet. The value range is 0 to 7, and the default value is 6.

-s packet-size: Specifies the length (excluding the IP header and UDP header) of an SR-MPLS TE policy echo request packet. The value for the packet-size argument is 65 to 8100 bytes, and the default is 100 bytes.

-t time-out: Specifies the timeout interval for the reply to an SR-MPLS TE policy echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

policy-name sr-policy-name: Specifies an SR-MPLS TE policy by its name, a case-sensitive string of 1 to 59 characters.

end-point ipv4 ip-address color color-value: Specifies an SR-MPLS TE policy by its endpoint IPv4 address and color attribute. The value range for the color-value argument is 0 to 4294967295.

binding-sid bsid: Specifies an SR-MPLS TE policy by its BSID value, which is an MPLS label value in the range of 16 to 1010152.

Usage guidelines

If the SR-MPLS TE policy contains multiple SID lists, the command verifies the connectivity to all SID lists.

Examples

# Verify the tunnel connectivity of SR-MPLS TE policy policy1.

<Sysname> ping mpls sr-policy policy-name policy1

SR-TE policy ping policy1 with 100 bytes of data:

Segment list ID: 1

Preference=10, Path type=main, Protocol origin=Local

100 bytes from 100.1.2.1: Sequence=1 time=49 ms

100 bytes from 100.1.2.1: Sequence=2 time=44 ms

100 bytes from 100.1.2.1: Sequence=3 time=60 ms

100 bytes from 100.1.2.1: Sequence=4 time=60 ms

100 bytes from 100.1.2.1: Sequence=5 time=76 ms

--- Ping statistics for SR-TE policy ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 44/57/76 ms

Segment list ID: 2

Preference=10, Path type=main, Protocol origin=Local

100 bytes from 101.1.2.1: Sequence=1 time=3 ms

100 bytes from 101.1.2.1: Sequence=2 time=2 ms

100 bytes from 101.1.2.1: Sequence=3 time=2 ms

100 bytes from 101.1.2.1: Sequence=4 time=6 ms

100 bytes from 101.1.2.1: Sequence=5 time=3 ms

--- Ping statistics for SR-TE policy ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 2/3/6 ms

Segment list ID: 3

Preference=5, Path type=backup, Protocol origin=Local

100 bytes from 102.1.2.1: Sequence=1 time=3 ms

100 bytes from 102.1.2.1: Sequence=2 time=2 ms

100 bytes from 102.1.2.1: Sequence=3 time=2 ms

100 bytes from 102.1.2.1: Sequence=4 time=6 ms

100 bytes from 102.1.2.1: Sequence=5 time=3 ms

--- Ping statistics for SR-TE policy ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 2/3/6 ms

# Verify the tunnel connectivity of SR-MPLS TE policy policy1 and configure the following settings:

· Send three SR-MPLS TE policy echo request packets.

· Display detailed reply information.

<Sysname> ping mpls –c 3 –v sr-policy policy-name policy1

SR-TE policy ping policy1 with 100 bytes of data:

Segment list ID: 1

Preference: 10; Path Type: main; Protocol-Origin: Local

100 bytes from 100.1.2.1: Sequence=1 time=49 ms Return Code=3(1)

100 bytes from 100.1.2.1: Sequence=2 time=44 ms Return Code=3(1)

100 bytes from 100.1.2.1: Sequence=3 time=60 ms Return Code=3(1)

100 bytes from 100.1.2.1: Sequence=4 time=60 ms Return Code=3(1)

100 bytes from 100.1.2.1: Sequence=5 time=76 ms Return Code=3(1)

100 bytes from 100.1.2.1: Sequence=6 time=57 ms Return Code=3(1)

--- Ping statistics for SR-TE policy ---

6 packets transmitted, 6 packets received, 0.0% packet loss

Round-trip min/avg/max = 44/57/76 ms

Table 6 Command output

Field	Description
SR-TE policy ping policy1 with 100 bytes of data	Verify connectivity to SR-MPLS TE policy policy1 by sending 100-byte SR-MPLS TE policy echo requests.
Segment list·ID	SID list ID.
Preference	Path priority.
Path type	Path type: · Main—Primary path. · Backup—Backup path.
Protocol origin	Protocol that obtains the SR TE policy: · PCEP. (This option is not supported in the current software version.) · BGP. · Local. · Unknown.
100 bytes from 100.1.2.1	Received a 100-byte reply from 100.1.2.1.
Sequence	Sequence number of the reply, for determination of packet loss, disorder, or duplicate.
time	Packet round-trip delay in milliseconds.
Return Code	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.
Ping statistics for SR-TE policy	SR-MPLS TE policy verification statistics.
packets transmitted	Number of SR-MPLS TE policy echo requests sent.
packets received	Number of SR-MPLS TE policy echo replies received.
packet loss	Percentage of unreplied packets to total request packets.
Round-trip min/avg/max	Minimum, average, and maximum round-trip delay in milliseconds.

‌

ping mpls te

Use ping mpls te to verify MPLS TE tunnel connectivity.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameter

-c count: Specifies the number of MPLS echo request packets to be sent, in the range of 1 to 4294967295. The default is 5.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the TTL value of MPLS echo request packets, in the range of 1 to 255. The default is 255.

-m wait-time: Specifies the interval for sending MPLS echo request packets, in the range of 1 to 10000 milliseconds. The default is 200 milliseconds.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 1, 2, 3, or 4. The default is 2.

· 1—Do not reply.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet. The reply mode 4 is not available for MPLS TE tunnel connectivity verification. If the mode is specified, the remote end does not reply.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default is 6.

-s packet-size: Specifies the length (excluding the IP header and UDP header) of an MPLS echo request packet. The value range for the packet-size argument is 65 to 8100 bytes, and the default is 100 bytes.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

fec-check: Checks the FEC type at transit nodes. If you do not specify this keyword, transit nodes do not check the FEC type.

segment-routing: For verification of the tunnels signaled by using Segment Routing, if you specify this keyword, MPLS echo request packets use the IGP Prefix/Adj FEC. If you do not specify this keyword, MPLS echo request packets use the IPv4 LSP FEC. This keyword does not affect MPLS TE tunnels signaled by using other protocols.

tunnel interface-number: Specifies an MPLS TE tunnel interface by the interface number. The specified MPLS TE tunnel interface must have already been created.

nil: Specifies the Nil FEC, so that the egress node will not check the FEC type. If you do not specify this keyword, the egress node will check the FEC type.

hot-standby: Verifies the connectivity of the hot-standby backup LSP created for the specified MPLS TE tunnel. To verify the specified MPLS TE tunnel, do not specify this keyword.

nil-fec: Specifies the Nil FEC, so that the egress node will not check the FEC type. If you do not specify this keyword, the egress node will check the FEC type.

Examples

# Verify the connectivity of the MPLS TE tunnel for Tunnel 1.

<Sysname> ping mpls te tunnel 1

MPLS ping TE tunnel Tunnel1 with 100 bytes of data:

100 bytes from 100.1.2.1: Sequence=1 time=49 ms

100 bytes from 100.1.2.1: Sequence=2 time=44 ms

100 bytes from 100.1.2.1: Sequence=3 time=60 ms

100 bytes from 100.1.2.1: Sequence=4 time=60 ms

100 bytes from 100.1.2.1: Sequence=5 time=76 ms

--- Ping statistics for TE tunnel Tunnel1 ---

5 packets transmitted, 5 packets received, 0.0% packet loss

Round-trip min/avg/max = 44/57/76 ms

For the command output, see Table 4.

tracert mpls ipv4

Use tracert mpls ipv4 to trace MPLS LSPs from the ingress node to the egress node for an IPv4 prefix. You can locate the error node according to the reply information.

Syntax

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v | ddmap | fec-check ] * ipv4 ipv4-address mask-length [ nexthop nexthop-address ] [ destination start-address [ end-address [ address-increment ] ] ] [ fec-type { bgp | generic | isis | ldp | ospf } ] [ remote-fec { ldp remote-ip-addr remote-mask-len | nil } ]

Views

Any view

Predefined user roles

network-admin

Parameters

-a source-ip: Specifies the source address of MPLS echo request packets. If you do not specify this option, the command uses the primary IP address of the outgoing interface as the source address of MPLS echo requests.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the maximum TTL value of MPLS echo request packets (the maximum number of hops to be inspected). The value range for the ttl-value argument is 1 to 255, and the default is 30.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 2, 3, or 4. The default is 2.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

ddmap: Encapsulates the Downstream Detailed Mapping (DDMAP) TLV in MPLS echo reply and MPLS echo request packets. If you do not specify this keyword, Downstream Mapping TLV (DSMAP) will be encapsulated in these packets. DDMAP TLV and DSMAP TLV carry the downstream information of the current node, including the next hop address and outgoing label. When you perform MPLS tracert operations, the device will verify the next hop address and outgoing label in the DDMAP TLV and DSMAP TLV. If both the address and label are correct, the device sends a normal MPLS echo reply to the ingress node. If the address or label is incorrect, the device sends an MPLS echo reply with an error code to the ingress node.

fec-check: Checks the FEC stack at transit nodes.

ipv4-address mask-length: Specifies an FEC by an IPv4 destination address and a mask length. The value range for the mask-length argument is 0 to 32.

nexthop nexthop-address: Specifies the next hop IP address. If an FEC has multiple next hops, you can use this option to specify a next hop for the tracert operation.

destination: Specifies the destination address in the IP header of MPLS echo requests. The default is 127.0.0.1.

start-address: Specifies the destination address or the start destination address. This address must be an address on subnet 127.0.0.0/8—a local loopback address. If you specify the start-address argument without the end-address argument, the start-address is the destination address in the IP header. If you specify both start-address and end-address, you specify a range of destination addresses. The destination address increments by the value specified for the address-increment argument, starting from the start-address to the end-address. The command performs a tracert for each of the destination addresses.

end-address: Specifies the end destination address. This address must be an address on subnet 127.0.0.0/8—a local loopback address.

address-increment: Specifies the increment value by which the destination address in the IP header increases in turn. The value range is 1 to 16777215 and the default value is 1.

fec-type: Specifies the FEC type to be carried in an MPLS echo request packet. If you do not specify this keyword, the FEC type is the protocol type of the specified FEC in the routing table.

bgp: Represents BGP signaled LSPs.

generic: Represents LSPs of any FEC type.

is-is: Represents IS-IS signaled SRLSPs.

ldp: Represents LDP signaled LSPs.

ospf: Represents OSPF signaled SRLSPs.

remote-fec: Specifies the remote FEC type. To trace the complete path of an LSP that belongs to different FEC types, you need to specify the FEC type used in the remote network.

nil: Specifies the Nil FEC. If the remote FEC type is unknown, specify this keyword in to avoid LSP tracert failure caused by FEC type verification failure on the egress node.

Usage guidelines

In the MPLS trace route result, no downstream information is displayed for some nodes if the MPLS LSP contains ECMP paths on a transit node that uses per-packet load sharing. This is because different MPLS echo requests will select different paths on the transit node, resulting in downstream mapping verification failure on some nodes of the MPLS LSP.

To use this feature, make sure the mpls ttl expiration enable command is configured on all the devices in the MPLS network.

Examples

# Trace the path that the LSP (for FEC 5.5.5.9/32) traverses from the ingress node to the egress node. Specify the IP header destination address range as 127.1.1.1 to 127.1.1.2 and set the address increment value to 1. With these settings, the device performs a tracert for 127.1.1.1 and 127.1.1.2.

<Sysname> tracert mpls ipv4 5.5.5.9 32 destination 127.1.1.1 127.1.1.2 1

MPLS trace route FEC 5.5.5.9/32

Destination address 127.1.1.1

TTL Replier Time Type Downstream

0 Ingress 100.1.2.1/[1025]

1 100.1.2.1 1 ms Transit 100.2.4.1/[1024]

2 100.2.4.1 63 ms Transit 100.4.5.1/[3]

3 100.4.5.1 129 ms Egress

Destination address 127.1.1.2

TTL Replier Time Type Downstream

0 Ingress 100.1.3.1/[1030]

1 100.1.3.1 1 ms Transit 100.3.4.1/[1024]

2 100.3.4.1 51 ms Transit 100.4.5.1/[3]

3 100.4.5.1 80 ms Egress

# Trace the path that the LSP (for FEC 5.5.5.9/32) traverses from the ingress node to the egress node. Display detailed reply information, specify the IP header destination address range as 127.1.1.1 to 127.1.1.2, and set the address increment value to 1. With these settings, the device performs a tracert for 127.1.1.1 and 127.1.1.2.

<Sysname> tracert mpls –v ipv4 5.5.5.9 32 destination 127.1.1.1 127.1.1.2 1

MPLS trace route FEC 5.5.5.9/32

Destination address 127.1.1.1

TTL Replier Time Type Downstream

0 Ingress 100.1.2.1/[1025]

1 100.1.2.1 1 ms Transit 100.2.4.1/[1024] ReturnCode 8(1)

2 100.2.4.1 63 ms Transit 100.4.5.1/[3] ReturnCode 8(1)

3 100.4.5.1 129 ms Egress ReturnCode 3(1)

Destination address 127.1.1.2

TTL Replier Time Type Downstream

0 Ingress 100.1.3.1/[1030]

1 100.1.3.1 1 ms Transit 100.3.4.1/[1024] ReturnCode 8(1)

2 100.3.4.1 51 ms Transit 100.4.5.1/[3] ReturnCode 8(1)

3 100.4.5.1 80 ms Egress ReturnCode 3(1)

Table 7 Command output

Field	Description
MPLS trace route FEC	Trace the LSPs for the specified FEC.
Destination address	Destination IP address in the IP header.
TTL	Number of hops.
Replier	Address of the LSR that replied the request.
Time	Packet round-trip delay, in milliseconds.
Type	LSR type: Ingress, Transit, or Egress.
Downstream	Address of the downstream LSR and the outgoing label (label assigned by the downstream LSR).
ReturnCode	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.

‌

Related commands

mpls ttl expiration enable

tracert mpls out-labels

Use tracert mpls out-labels to trace MPLS LSPs of the specified outgoing labels from the ingress node to the egress node of the LSPs. You can locate the error node according to the reply information.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the maximum TTL value of MPLS echo request packets (the maximum number of hops to be inspected). The value range for the ttl-value argument is 1 to 255, and the default is 30.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 2, 3, or 4. The default is 2.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

interface interface-type interface-number: Specifies the outgoing interface by the interface type and number.

nexthop nexthop-address: Specifies the next hop IP address.

Usage guidelines

To use this feature, make sure the mpls ttl expiration enable command is configured on all the devices in the MPLS network.

To trace a specific LSP, first execute the display mpls lsp command to identify the outgoing interface and next hop for the outgoing labels to be specified.

Examples

# Trace the path of the LSP with outgoing label 2173, outgoing interface Ten-GigabitEthernet 3/1/1, and next hop IP address 10.1.1.2/32 in an LDP network.

<Sysname> tracert mpls out-labels 2173 interface ten-gigabitethernet 3/1/1 nexthop 10.1.1.2

MPLS trace route out-labels 2173

TTL Replier Time Type Downstream

0 Ingress 10.1.1.2/[2173]

1 10.1.1.2 1 ms Transit 20.1.1.2/[1040127]

2 20.1.1.2 1 ms Egress

# In an SR-MPLS to LDP interworking network, trace the LSP with outgoing label 17030, outgoing interface Ten-GigabitEthernet 3/1/2, and next hop 100.1.1.2/32 on the source node.

<Sysname> tracert mpls out-labels 17030 interface ten-gigabitethernet 3/1/2 nexthop 100.1.1.2

MPLS trace route out-labels 17030

TTL Replier Time Type Downstream

0 Ingress 100.1.1.2/[17030]

1 100.1.1.2 1 ms Transit 10.1.1.2/[2173]

2 10.1.1.2 2 ms Transit 20.1.1.2/[1040127]

3 20.1.1.2 1 ms Egress

Table 8 Command output

Field	Description
MPLS trace route out-labels out-label-value	Trace the LSPs for the specified outgoing labels.
TTL	Number of hops.
Replier	IP address of the LSR that replied the request.
Time	Packet round-trip delay, in milliseconds.
Type	LSR type: Ingress, Transit, or Egress.
Downstream	Address of the downstream LSR and the outgoing label (label assigned by the downstream LSR).
Return Code	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.

‌

Related commands

mpls ttl expiration enable

tracert mpls pw

Use tracert mpls pw to trace the path of an LDP PW or a static PW and locate the error node according to the reply information.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

-a source-ip: Specifies the source address of MPLS echo request packets. If you do not specify this option, the device uses its MPLS LSR ID as the source address of MPLS echo requests.

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the maximum TTL value of MPLS echo request packets (the maximum number of hops to be inspected). The value range for the ttl-value argument is 1 to 255, and the default is 255.

-m wait-time: Specifies the interval for sending MPLS echo request packets, in the range of 1 to 10000 milliseconds. The default is 200 milliseconds.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 2, 3, or 4. The default is 2.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

ip-address: Specifies the IP address of the peer PE.

pw-id pw-id: Specifies the ID of the PW to the peer PE, in the range of 1 to 4294967295.

full-lsp-path: Displays the full LSP path between the local PE and the remote PE. If you do not specify this keyword, the command displays only the path information returned by the egress node.

Usage guidelines

To use this command to trace the path of an LDP PW or a static PW, the PW must be created by using a PW class that specifies the VCCV CC type.

Examples

# Display the path of the PW with remote IP address 3.3.3.9 and PW ID 301.

<Sysname> tracert mpls pw 3.3.3.9 pw-id 301

MPLS tracert PW 3.3.3.9 301

TTL Replier Time Type Downstream

0 Ingress 10.4.5.1/[1025]

1 10.4.5.1 1 ms Transit 100.3.4.1/[1024]

2 100.3.4.1 63 ms Transit 100.1.2.1/[3]

3 100.1.2.1 129 ms Egress

Table 9 Command output

Field	Description
MPLS tracert PW 3.3.3.9 301	Tracert the PW with remote IP address 3.3.3.9 and PW ID 301.
TTL	Number of hops.
Replier	IP address of the LSR that replied the request.
Time	Packet round-trip delay, in milliseconds.
Type	LSR type: Ingress, Transit, or Egress.
Downstream	Address of the downstream LSR and the outgoing label (label assigned by the downstream LSR).
ReturnCode	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.

‌

tracert mpls sr-policy

Use tracert mpls sr-policy to trace the path of an SR-MPLS TE policy and locate the error node according to the reply information.

Syntax

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v ] * sr-policy { policy-name sr-policy-name | end-point ipv4 ip-address color color-value | binding-sid bsid }

Views

Any view

Predefined user roles

network-admin

Parameters

-exp exp-value: Specifies the EXP value of SR-MPLS TE policy echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the maximum TTL value of SR-MPLS TE policy echo request packets (the maximum number of hops to be inspected). The value range for the ttl-value argument is 1 to 255, and the default is 30.

-r reply-mode: Specifies the reply mode of the receiver in response to SR-MPLS TE policy echo request packets. The reply-mode argument can be 2, 3, or 4. The default is 2.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an SR-MPLS TE policy echo reply packet. The value range is 0 to 7, and the default value is 6.

-t time-out: Specifies the timeout interval for the reply to an SR-MPLS TE policy echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

policy-name sr-policy-name: Specifies an SR-MPLS TE policy by its name, a case-sensitive string of 1 to 59 characters.

end-point ipv4 ip-address color color-value: Specifies an SR-MPLS TE policy by its endpoint IPv4 address and color attribute. The value range for the color-value argument is 0 to 4294967295.

binding-sid bsid: Specifies an SR-MPLS TE policy by its BSID value, which is an MPLS label value in the range of 16 to 1010152.

Usage guidelines

Examples

# Trace the path of SR-MPLS TE policy policy1.

<Sysname> tracert mpls sr-policy policy-name policy1

SR-TE Policy trace route policy1

Segment list ID: 1

Preference=10, Path type=main, Protocol origin=Local

TTL Replier Time Type Downstream

0 Ingress 100.1.2.1/[16000]

1 100.1.2.1 1 ms Transit 100.2.4.1/[16000]

2 100.2.4.1 63 ms Transit 100.4.5.1/[3]

3 100.4.5.1 129 ms Egress

Segment list ID: 2

Preference=10, Path type=main, Protocol origin=Local

TTL Replier Time Type Downstream

0 Ingress 100.1.3.1/[15000]

1 100.1.3.1 1 ms Transit 100.3.4.1/[15001]

2 100.3.4.1 51 ms Transit 100.4.5.1/[15002]

3 100.4.5.1 80 ms Egress

# Trace the path of SR-MPLS TE policy policy1 and display detailed reply information.

<Sysname> tracert mpls –v sr-policy policy-name policy1

SR-TE Policy trace route policy1

Segment list ID: 1

Preference=10, Path type=main, Protocol origin=Local

TTL Replier Time Type Downstream

0 Ingress 100.1.2.1/[1025]

1 100.1.2.1 1 ms Transit 100.2.4.1/[1024] ReturnCode 8(1)

2 100.2.4.1 63 ms Transit 100.4.5.1/[3] ReturnCode 8(1)

3 100.4.5.1 129 ms Egress ReturnCode 3(1)

Segment list ID: 2

Preference=10, Path type=main, Protocol origin=Local

TTL Replier Time Type Downstream

0 Ingress 100.1.3.1/[1030]

1 100.1.3.1 1 ms Transit 100.3.4.1/[1024] ReturnCode 8(1)

2 100.3.4.1 51 ms Transit 100.4.5.1/[3] ReturnCode 8(1)

3 100.4.5.1 80 ms Egress ReturnCode 3(1)

Table 10 Command output

Field	Description
SR-TE Policy trace route policy1	Trace the LSPs for the specified SR TE Policy.
Segment list·ID	SID list ID.
Preference	Path priority.
Path type	Path type: · Main—Primary path. · Backup—Backup path.
Protocol origin	Protocol that obtains the SR TE policy: · PCEP. (This option is not supported in the current software version.) · BGP. · Local. · Unknown.
TTL	Number of hops.
Replier	IP address of the LSR that replied the request.
Time	Packet round-trip delay, in milliseconds.
Type	LSR type: Ingress, Transit, or Egress.
Downstream	Address of the downstream LSR and the outgoing label (label assigned by the downstream LSR).
ReturnCode	Return code. The number in parentheses represents a return subcode. · 1—The received MPLS echo request packet has content errors. · 2—The packet contains an unsupported TLV. · 3—Reply from the egress node. · 5—Unmatching downstream mapping. · 6—The upstream did not provide the outgoing interface. · 8—Reply from the label switching node. · 10—The outgoing label for the FEC is inconsistent with that in the packet label stack. · 11—The label in the packet label stack does not have a matching forwarding entry. · 12—The protocol type of the FEC is inconsistent with that in the label forwarding table for the packet.

‌

tracert mpls te

Use tracert mpls te to trace an MPLS TE tunnel from the ingress node to the egress node. You can locate the error node according to the reply information.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

-exp exp-value: Specifies the EXP value of MPLS echo request packets, in the range of 0 to 7. The default is 0.

fec-check: Checks the FEC type at transit nodes. If you do not specify this keyword, transit nodes do not check the FEC type.

-h ttl-value: Specifies the maximum TTL value of MPLS echo request packets (the maximum number of hops to be inspected). The value range for the ttl-value argument is 1 to 255, and the default is 30.

-r reply-mode: Specifies the reply mode of the receiver in response to MPLS echo request packets. The reply-mode argument can be 2, 3, or 4. The default is 2.

· 2—Reply by using a UDP packet.

· 3—Reply by using a UDP packet that carries the Router Alert option.

· 4—Reply by using a VCCV packet.

-rtos tos-value: Specifies the ToS value in the IP header of an MPLS echo reply packet. The value range is 0 to 7, and the default value is 6.

-t time-out: Specifies the timeout interval for the reply to an MPLS echo request. The value range is 0 to 65535 milliseconds, and the default is 2000 milliseconds.

-v: Displays detailed reply information. If you do not specify this keyword, the command displays brief reply information.

fec-check: Checks the FEC stack at transit nodes.

segment-routing: For tracert of the tunnels signaled by using Segment Routing, if you specify this keyword, MPLS echo request packets use the IGP Prefix/Adj FEC. If you do not specify this keyword, MPLS echo request packets use the IPv4 LSP FEC. This keyword does not affect MPLS TE tunnels signaled by using other protocols.

tunnel interface-number: Specifies an existing MPLS TE tunnel interface by the interface number.

nil: Specifies the Nil FEC, so that the egress node will not check the FEC type. If you do not specify this keyword, the egress node will check the FEC type.

hot-standby: Tracerts the hot-standby backup LSP created for the specified MPLS TE tunnel. To tracert the specified MPLS TE tunnel, do not specify this keyword.

nil-fec: Specifies the Nil FEC, so that the egress node will not check the FEC type. If you do not specify this keyword, the egress node will check the FEC type.

Usage guidelines

To use this feature, make sure the mpls ttl expiration enable command is configured on all the devices in the MPLS network.

Examples

# Trace the path that MPLS TE tunnel 1 traverses from the ingress node to the egress node.

<Sysname> tracert mpls te tunnel 1

MPLS trace route TE tunnel Tunnel1

TTL Replier Time Type Downstream

0 Ingress 10.4.5.1/[1025]

1 10.4.5.1 1 ms Transit 100.3.4.1/[1024]

2 100.3.4.1 63 ms Transit 100.1.2.1/[3]

3 100.1.2.1 129 ms Egress

For the command output, see Table 7.

Related commands

mpls ttl expiration enable

vccv bfd

Use vccv bfd to configure BFD to verify PW connectivity.

Use undo vccv bfd to restore the default.

Syntax

vccv bfd [ template template-name ]

undo vccv bfd

Default

BFD is not used to verify PW connectivity.

Views

PW class view

Predefined user roles

network-admin

Parameters

template template-name: Specifies a BFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a template, BFD uses the multihop BFD session settings configured in system view.

Usage guidelines

After you execute this command and specify the PW class for a PW, the PEs use the specified encapsulation type to verify PW connectivity when the following conditions are met:

· Both PEs of the PW have configured BFD for the PW.

· The PEs use the same encapsulation type for BFD packets.

If any of the previous conditions are not met, the PEs do not use BFD to verify PW connectivity.

To use BFD for PW connectivity verification, you must execute the vccv bfd and mpls bfd enable commands on both ends of the PW.

Examples

# Configure BFD to verify PW connectivity and specify the BFD session parameter template as aaa.

<Sysname> system-view

[Sysname] pw-class test

[Sysname-pw-test] vccv bfd template aaa

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv cc

Use vccv cc to specify the VCCV control channel (CC) type.

Use undo vccv cc to restore the default.

Syntax

vccv cc { control-word | router-alert }

undo vccv cc

Default

No VCCV CC type is specified.

Views

PW class view

Predefined user roles

network-admin

Parameters

control-word: Specifies the VCCV CC type as control word.

router-alert: Specifies the VCCV CC type as MPLS router alert label.

Usage guidelines

The packets used to verify PW connectivity are collectively referred to as VCCV packets. A PE transfers VCCV packets through a CC.

CCs include the following types:

· Control word—Identifies VCCV packets through the control word (PW-ACH, PW Associated Channel Header). You can use this CC type only when the PW supports control word. For more information about control word, see MPLS Configuration Guide.

· MPLS router alert label—Identifies a VCCV packet by adding an MPLS router alert label before the PW label.

After you execute this command and specify the PW class for a PW, the specified CC is used if both PEs have specified the same VCCV CC type. Otherwise, the PEs do not use any CC and they cannot establish a BFD session for the PW.

Examples

# Specify the VCCV CC type as MPLS router alert label.

<Sysname> system-view

[Sysname] pw-class test

[Sysname-pw-test] vccv cc router-alert

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv bfd

10-MPLS Command Reference

MPLS OAM commands

bfd ip-router-alert

bfd static pw

mpls bfd (for LSP)

mpls bfd enable

mpls sbfd flex-algo-lsp

mpls te bfd enable pce-initiated-lsp

mpls tunnel-bfd min-receive-interval

ping mpls out-labels

tracert mpls te

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us