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]

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 1 Command output

Field	Description
BFD Info: Tunnel BFD	Indicates that the LSP or tunnel was detected by tunnel BFD.
FEC Type	Type of FEC detected by BFD: · LSP · TE Tunnel · Nil FEC · SR Prefix SID · SR Adjacency SID
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 or MPLS TE tunnels.

Syntax

display mpls sbfd [ 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 SBFD information for all LSP tunnels and all MPLS TE 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 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: -

Table 2 Command output

Field	Description
BFD Info	BFD information. This field can only be Tunnel SBFD is the current software version.
FEC Type	Type of the FEC detected by SBFD, which can be LSP or TE Tunnel.
FEC Info	Information of the FEC detected by SBFD. For an LSP, the FEC information includes the FEC destination address of mask length. For a TE tunnel, the FEC information includes the tunnel source and destination addresses, tunnel ID, and LSP ID.
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 [ 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 [ 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. The value range for the local-id argument is 1 to 32768.

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

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.

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 parameters configured in system view, and BFD echo packet mode uses the system default BFD session parameters.

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.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

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 is the MPLS LSR ID of the local device. Before configuring BFD 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.

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 type of LSPs to be verified, BFD detects the LSPs in the order of static LSP, LDP LSP, OSPF SRLSP, and IS-IS SRLSP. 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 ] [ 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. The value range for the local-id argument is 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. If you do not specify this keyword, the command enables the BFD control packet mode.

backup-path template template-name: Specifies a BFD session parameter template for the MPLS TE backup path. The template-name argument indicates the template 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 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.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

Usage guidelines

After you execute the mpls bfd enable and mpls bfd commands, the device creates a BFD session for the MPLS TE tunnel. When the 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.

If you specify templates for both the primary and backup CRLSPs of a tunnel, 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.

The source address of the BFD session is the MPLS LSR ID of the local device. Before configuring BFD for an MPLS TE tunnel, 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.

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.

If a tunnel interface is configured with CRLSP backup, the static mode creates a BFD session only for the primary CRLSP. The dynamic mode creates a BFD session for the primary CRLSP and the backup CRLSP, separately. If the two CRLSPs both fail, the device puts the MPLS TE tunnel to down state so the tunnel does not receive traffic.

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.

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

[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

[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

[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 the backup path of an MPLS TE 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 the backup path of 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 3 to 50.

Usage guidelines

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

· If the mpls bfd backup detect-multiplier command and the mpls bfd command with the backup-path template keyword are both executed in the tunnel interface view, the mpls 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.

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

· If the mpls bfd backup detect-multiplier command and the mpls bfd command with the backup-path template keyword are both executed in the tunnel interface view, the mpls bfd command 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 backup path of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1

[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 the backup path of an MPLS TE tunnel to receive BFD packets.

Use undo mpls bfd 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 the backup path of 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 for this argument is 10 to 10000.

Usage guidelines

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

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

· If the mpls bfd backup min-receive-interval command and the mpls bfd command with the backup-path template keyword are both executed in the tunnel interface view, the mpls 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.

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 path of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1

[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 the backup path of an MPLS TE 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 the backup path of 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 for this argument is 10 to 10000.

Usage guidelines

Use this command to prevent the BFD packet transmit rate from exceeding the packet receive rate of the peer end.

The actual BFD packet transmit 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 command and the mpls bfd command with the backup-path template keyword are both executed in the tunnel interface view, the mpls 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.

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 transmit interval to 450 milliseconds for the backup path of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1

[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 and SBFD detection time multiplier for the primary path of an MPLS TE 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 and SBFD detection time multiplier is not set for the primary path of 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

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

· If the mpls bfd detect-multiplier command and the mpls bfd command with the template keyword are both executed in the tunnel interface view, the mpls 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.

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

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

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

In SBFD for an MPLS TE tunnel:

· If the mpls bfd detect-multiplier command and the mpls sbfd command with the template keyword are both executed in the tunnel interface view, the mpls 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 BFD and SBFD detection time multiplier to 3 for the primary path of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1

[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

display mpls sbfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls sbfd (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 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 receive interval for BFD and SBFD on the primary path of an MPLS TE tunnel.

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 receiving interval is not set for BFD and SBFD on the primary path of 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 for this argument is 10 to 10000.

Usage guidelines

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

· If the mpls bfd min-receive-interval command and the mpls bfd command with the template keyword are both executed in the tunnel interface view, the mpls 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.

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

· If the mpls bfd min-receive-interval command and the mpls bfd command with the template keyword are both executed in the tunnel interface view, the mpls bfd command 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.

For SBFD on an MPLS TE tunnel:

· If the mpls bfd min-receive-interval command and the mpls sbfd command with the template keyword are both executed in the tunnel interface view, the mpls 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 BFD and SBFD on the primary path of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1

[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

display mpls sbfd

mpls bfd (for TE tunnel)

mpls bfd enable

mpls sbfd (for TE tunnel)

mpls bfd min-transmit-interval

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

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 transmit interval is not set for BFD and SBFD on the primary path of 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 for this argument is 10 to 10000.

Usage guidelines

Use this command to prevent the BFD packet transmit rate from exceeding the packet receive rate of the peer end.

The actual BFD packet transmit 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 command and the mpls bfd command with the template keyword are both executed in the tunnel interface view, the mpls 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.

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

For SBFD on an MPLS TE tunnel:

· If the mpls bfd min-transmit-interval command and the mpls sbfd command with the template keyword are both executed in the tunnel interface view, the mpls 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 transmit interval to 450 milliseconds for BFD and SBFD on the primary path of MPLS TE tunnel 1.

<Sysname> system-view

[Sysname] mpls bfd enable

[Sysname] interface tunnel 1

[Sysname-Tunnel1] mpls 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 (for TE tunnel)

mpls bfd enable

mpls sbfd (for TE tunnel)

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 for this feature in MPLS TE view applies.

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. The BFD sessions for normal paths might go down if a large number of MPLS TE tunnel interfaces exist and they perform primary/backup switchovers concurrently. This results in unexpected 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. The BFD sessions for normal paths might go down if a large number of MPLS TE tunnel interfaces exist and they perform primary/backup switchovers concurrently. This results in unexpected 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 parameters 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.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

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

Use undo mpls sbfd to restore the default.

Syntax

mpls sbfd [ remote remote-id ] [ template template-name ] [ backup-path template template-name ] [ source-ip ipv4-address ]

undo mpls sbfd

Default

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

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 SBFD session settings configured in tunnel interface view.

backup-path template template-name: Specifies an SBFD session parameter template for the MPLS TE backup path. The template-name argument indicates the template 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 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 SBFD session. If you do not specify this option, the device uses the MPLS LSR ID as the source address of the SBFD session.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

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.

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 source address of the SBFD session is the MPLS LSR ID of the local device. Before configuring SBFD for an MPLS TE tunnel, 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

# 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

[Sysname-Tunnel1] mpls sbfd remote 1 template test

Related commands

display mpls bfd

mpls bfd enable

sbfd local-discriminator (High Availability Command Reference)

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. The value range for the local-id argument is 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.

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.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

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 is the MPLS LSR ID of the local device. Before configuring tunnel BFD 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.

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 type of LSPs to be verified, BFD detects the LSPs in the order of static LSP, LDP LSP, BGP LSP, OSPF SRLSP, and IS-IS SRLSP. The BFD session is up as long as one LSP is operating correctly. The BFD session goes down when all LSPs fail.

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.

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 ] [ template template-name ] [ source-ip ipv4-address ]

undo mpls tunnel-bfd

Default

Tunnel BFD is not used to verify MPLS TE 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. The value range for the local-id argument is 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. If you do not specify this keyword, the command enables the BFD control 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.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

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 is the MPLS LSR ID of the local device. Before configuring tunnel BFD for an MPLS TE tunnel, 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.

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.

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

[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

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

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

[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 10 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

[Sysname-Tunnel1] mpls 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 [ remote remote-id ] [ 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.

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.

NOTE:

The source-ip keyword is supported only in F3607P02 and later.

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.

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 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 is the MPLS LSR ID of the local device. Before configuring tunnel SBFD for an MPLS TE tunnel, 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

# 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

[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 [ destination start-address [ end-address [ address-increment ] ] ] [ fec-type { generic | isis | ldp | ospf } ]

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.

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.

generic: Represents LSPs of any FEC type.

is-is: Represents IS-IS signaled SRLSPs.

ldp: Represents LDP signaled LSPs.

ospf: Represents OSPF signaled SRLSPs.

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 3 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-6>: Specifies a space-separated list of up to six 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

# In an LDP network, verify the connectivity of the LSP with outgoing label 2173, outgoing interface HundredGigE 1/0/1, and next hop IP address 10.1.1.2/32.

<Sysname> ping mpls out-labels 2173 interface hundredgige 1/0/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: 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.

# In an MPLS SR to LDP interworking network, configure the source node to verify the LSP with outgoing label 17030, outgoing interface HundredGigE 1/0/2, and next hop 100.1.1.2/32.

<Sysname> ping mpls out-labels 17030 interface hundredgige 1/0/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: 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 4 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 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.

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

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

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 [ destination start-address [ end-address [ address-increment ] ] ] [ fec-type { generic | isis | ldp | ospf } ]

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 1, 2, or 3. 1 means "Do not reply," 2 means "Reply by using a UDP packet," and 3 means "reply by using a UDP packet that carries the Router Alert option." The default is 2.

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

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.

generic: Represents LSPs of any FEC type.

is-is: Represents IS-IS signaled SRLSPs.

ldp: Represents LDP signaled LSPs.

ospf: Represents OSPF signaled SRLSPs.

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

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 or 3. The default is 2.

· 2—Reply by using a UDP packet.

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

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

# In an LDP network, trace the path of the LSP with outgoing label 2173, outgoing interface HundredGigE 1/0/1, and next hop IP address 10.1.1.2/32.

<Sysname> tracert mpls out-labels 2173 interface hundredgige 1/0/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 MPLS SR to LDP interworking network, trace the LSP with outgoing label 17030, outgoing interface HundredGigE 1/0/2, and next hop 100.1.1.2/32 on the source node.

<Sysname> tracert mpls out-labels 17030 interface hundredgige 1/0/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 6 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.

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.

-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 or 3. 2 means "Reply by using a UDP packet," and 3 means "reply by using a UDP packet that carries the Router Alert option." The default is 2.

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

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

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

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

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.

Usage guidelines

The packets used to verify PW connectivity are collectively referred to as VCCV packets. A PE transfers VCCV packets through a CC.

The CC type can be control word, which 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.

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

<Sysname> system-view

[Sysname] pw-class test

[Sysname-pw-test] vccv cc control-word

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv bfd

06-MPLS Command Reference

MPLS OAM commands

bfd ip-router-alert

mpls bfd (for LSP)

mpls bfd enable

mpls tunnel-bfd detect-multiplier

ping mpls out-labels

ping mpls te

tracert mpls te

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us