MPLS OAM commands -- bfd discriminator

Use bfd discriminator to set local and remote discriminators for the BFD session used to verify PW connectivity.

Use undo bfd discriminator to restore the default.

Syntax

bfd discriminator local local-id remote remote-id

undo bfd discriminator

Default

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

Views

Cross-connect PW view

VSI static PW view

VSI LDP PW view

Cross-connect backup PW view

VSI static backup PW view

VSI LDP backup PW view

Predefined user roles

network-admin

mdc-admin

Parameters

local local-id: Specifies the local discriminator value for the BFD session. The value range varies by device model.

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

[Sysname] vsi ttt

[Sysname-vsi-ttt] pwsignaling ldp

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

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

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv bfd

vccv cc

MPLS OAM commands -- bfd ip-router-alert

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

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

Syntax

bfd ip-router-alert

undo bfd ip-router-alert

Default

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

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

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

Examples

# Remove the Router Alert option from BFD packets.

<Sysname> system-view

[Sysname] undo bfd ip-router-alert

MPLS OAM commands -- display l2vpn pw bfd

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

Syntax

display l2vpn pw bfd [ peer peer-ip pw-id pw-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

peer peer-ip pw-id pw-id: Specifies a PW. The peer-ip argument specifies the LSR ID for the peer PE of the PW. The pw-id argument specifies the PW ID in the range of 1 to 4294967295. If you do not specify a PW, this command displays BFD information for all PWs.

Examples

# Display BFD information for all PWs.

<Sysname> display l2vpn pw bfd

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

FEC Type: PW FEC-128

FEC Info:

Peer IP: 22.22.2.2

PW ID: 1

VSI Index: 0 Link ID: 8

Local Discr: 514 Remote Discr: 514

Source IP: 11.11.1.1 Destination IP: 127.0.0.2

Session State: Up Session Role: Active

Template Name: -

Table 1 Command output

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

Related commands

bfd discriminator

vccv bfd

vccv cc

MPLS OAM commands -- 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

mdc-admin

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

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

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

Table 2 Command output

Field | Description
Local Discr | Local discriminator of the BFD session.
Remote Discr | Remote discriminator of the BFD session.
Source IP | Source IP of the BFD session, which is the MPLS LSR ID of the local PE.
Destination IP | Destination IP address of the BFD session. 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.
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)

MPLS OAM commands -- 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 ] ] [ template template-name ]

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

Default

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

Views

System view

Predefined user roles

network-admin

mdc-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 varies by device model.

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

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

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.

A BFD session for LSP connectivity verification 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 enable BFD for MPLS and configure the mpls 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 bfd command is not needed on the remote PE. A dynamic BFD session verifies the connectivity of a unidirectional LSP from the local device to the remote device.

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

1. Configure an MPLS LSR ID for the local device.

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

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

display mpls bfd

mpls bfd enable

MPLS OAM commands -- mpls bfd (for TE tunnel)

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

Use undo mpls bfd to restore the default.

Syntax

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

undo mpls bfd

Default

BFD is not enabled on an MPLS TE tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

mdc-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 varies by device model.

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

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

Usage guidelines

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

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 enable BFD for MPLS and configure the mpls bfd command 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 enable BFD for MPLS 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 MPLS TE tunnel from the local device to the remote device.

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

1. Configure an MPLS LSR ID for the local device.

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

Examples

# Enable BFD 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 BFD 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

Related commands

display mpls bfd

mpls bfd enable

MPLS OAM commands -- 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

mdc-admin

Usage guidelines

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

Examples

# Enable BFD for MPLS.

<Sysname> system-view

[Sysname] mpls bfd enable

MPLS OAM commands -- 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

mpls periodic-tracert dest-addr mask-length [ -a source-ip | -exp exp-value | -h ttl-value | -m wait-time | -rtos tos-value | -t time-out | -u retry-attempt | fec-check ] *

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

mdc-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 for MPLS echo request packets. If you do not specify this option, the device uses the MPLS LSR ID as the source address for MPLS echo requests.

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

-h ttl-value: Specifies the maximum TTL value for 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 OAM commands -- 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 ] ] ]

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

-a source-ip: Specifies the source address for 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 for MPLS echo request packets, in the range of 0 to 7. The default is 0.

-h ttl-value: Specifies the TTL value for 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. 1 means "Do not reply." 2 means "Reply by using a UDP packet." 3 means "Reply by using a UDP packet that carries the Router Alert option." 4 means "Reply by using a VCCV packet." The default is 2. 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.

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 : 100 data bytes | 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.
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.

MPLS OAM commands -- ping mpls pw

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

Syntax

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * pw ip-address pw-id pw-id

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

-a source-ip: Specifies the source address for 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. The value range is 1 to 4294967295. The default is 5.

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

-h ttl-value: Specifies the TTL value for 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. 1 means "Do not reply." 2 means "Reply by using a UDP packet." 3 means "Reply by using a UDP packet that carries the Router Alert option." 4 means "Reply by using a VCCV packet." 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.

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

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

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

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

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

Examples

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

<Sysname> ping mpls pw 3.3.3.9 pw-id 301

MPLS ping PW 3.3.3.9 301 with 100 bytes of data:

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

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

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

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

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

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

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

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

For the command output, see Table 3.

MPLS OAM commands -- ping mpls te

Use ping mpls te to verify MPLS TE tunnel connectivity.

Syntax

ping mpls [ -a source-ip | -c count | -exp exp-value | -h ttl-value | -m wait-time | -r reply-mode | -rtos tos-value | -s packet-size | -t time-out | -v ] * te tunnel interface-number

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameter

-a source-ip: Specifies the source address for 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, in the range of 1 to 4294967295. The default is 5.

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

-h ttl-value: Specifies the TTL value for 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. 1 means "Do not reply." 2 means "Reply by using a UDP packet." 3 means "Reply by using a UDP packet that carries the Router Alert option." 4 means "Reply by using a VCCV packet." The default is 2. 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.

MPLS OAM commands -- 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 | fec-check ] * ipv4 ipv4-address mask-length [ destination start-address [ end-address [ address-increment ] ] ]

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

-a source-ip: Specifies the source address for 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 for MPLS echo requests.

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

-h ttl-value: Specifies the maximum TTL value for 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.

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.

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 4 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 | Time used to receive the reply, in milliseconds.
Type | LSR type: Ingress, Transit, or Egress.
Downstream | Address of the downstream LSR and the label assigned by the downstream LSR.
ReturnCode | Return code. The number in parentheses represents a return subcode.

MPLS OAM commands -- 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

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v | fec-check ] * te tunnel interface-number

Views

Any view

Predefined user roles

network-admin

mdc-admin

Parameters

-a source-ip: Specifies the source address for 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 for MPLS echo requests.

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

-h ttl-value: Specifies the maximum TTL value for 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 4.

MPLS OAM commands -- vccv bfd

Use vccv bfd to configure BFD to verify PW connectivity.

Use undo vccv bfd to restore the default.

Syntax

vccv bfd [ raw-bfd ] [ template template-name ]

undo vccv bfd

Default

BFD is not used to verify PW connectivity.

Views

PW class view

Predefined user roles

network-admin

mdc-admin

Parameters

raw-bfd: Specifies the BFD packets to use PW-ACH encapsulation (without IP/UDP headers). This keyword takes effect only when the CC type is control word. If you do not specify this keyword, the BFD packets use IP/UDP encapsulation (with IP/UDP headers).

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

Usage guidelines

After you execute this command and specify the PW class for a PW, the PEs use the specified encapsulation type to verify PW connectivity when the following conditions are met:

· Both PEs of the PW have configured BFD for the PW.

· The PEs use the same encapsulation type for BFD packets.

If any of the previous conditions are not met, the PEs do not use BFD to verify PW connectivity.

To use BFD for PW connectivity verification, you must execute the vccv bfd and mpls bfd enable commands on both ends of the PW.

Examples

# Configure BFD to verify PW connectivity and specify the BFD session parameter template as aaa.

<Sysname> system-view

[Sysname] pw-class test

[Sysname-pw-test] vccv bfd template aaa

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv cc

MPLS OAM commands -- vccv cc

Use vccv cc to specify the VCCV control channel (CC) type.

Use undo vccv cc to restore the default.

Syntax

vccv cc { control-word | router-alert | ttl }

undo vccv cc

Default

No VCCV CC type is specified.

Views

PW class view

Predefined user roles

network-admin

mdc-admin

Parameters

control-word: Specifies the VCCV CC type as control word.

router-alert: Specifies the VCCV CC type as MPLS router alert label.

ttl: Specifies the VCCV CC type as TTL expiry (MPLS PW Label with TTL = 1).

Usage guidelines

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

CCs include the following types:

· Control word—Identifies VCCV packets through the control word (PW-ACH, PW Associated Channel Header). You can use this CC type only when the PW supports control word. For more information about control word, see MPLS Configuration Guide.

· MPLS router alert label—Identifies a VCCV packet by adding an MPLS router alert label before the PW label.

· TTL expiry—Identifies a VCCV packet by setting the TTL value of the PW label to 1.

After you execute this command and specify the PW class for a PW, the specified CC is used if both PEs have specified the same VCCV CC type. Otherwise, the PEs do not use any CC and they cannot establish a BFD session for the PW.

Examples

# Specify the VCCV CC type as MPLS router alert label.

<Sysname> system-view

[Sysname] pw-class test

[Sysname-pw-test] vccv cc router-alert

Related commands

display l2vpn pw bfd

mpls bfd enable

vccv bfd