06-MPLS Configuration Guide

HomeSupportResource CenterSwitchesS12500R SeriesS12500R SeriesTechnical DocumentsConfigure & DeployConfiguration GuidesH3C S12500R Switch Router Series Configuration Guides(R3606)-6W10006-MPLS Configuration Guide
11-MPLS OAM configuration
Title Size Download
11-MPLS OAM configuration 233.98 KB

Configuring MPLS OAM

About MPLS OAM

MPLS Operation, Administration, and Maintenance (OAM) provides fault management tools for the following purposes in an MPLS network:

·     MPLS data plane connectivity verification.

·     Data plane and control plane consistency verification.

·     Fault locating.

Fault management tools

The fault management tools include the following types:

·     On-demand tools—Tools that must be triggered manually, such as MPLS ping and MPLS tracert.

·     Proactive tools—Tools that are triggered by the system automatically, such as BFD for MPLS, and periodic MPLS tracert.

You can use these tools to detect and locate faults of LSPs, MPLS TE tunnels, and MPLS PWs.

MPLS ping

MPLS ping tests the connectivity of an LSP tunnel, an MPLS TE tunnel, or a PW. At the ingress node, MPLS ping adds the label associated with a tunnel into an MPLS echo request and sends it to the egress node over the tunnel. The egress node processes the request and returns an MPLS echo reply to the ingress node. An MPLS echo reply with a success notification indicates that the tunnel is available for data forwarding. An MPLS echo reply with an error code indicates that the tunnel has failed.

MPLS tracert

MPLS tracert displays the path that an MPLS LSP tunnel or an MPLS TE tunnel travels from the ingress to the egress to locate errors on the tunnel. MPLS tracert consecutively sends MPLS echo requests along the LSP tunnel, with the TTL increasing from 1 to a specific value. Each hop along the tunnel returns an MPLS echo reply to the ingress due to TTL timeout so the ingress can collect information about each hop along the tunnel. This information allows you to locate the failed node or access information for each hop, for example, the label allocated by each downstream hop.

BFD for MPLS

BFD for MPLS uses a BFD session to proactively verify the connectivity of an LSP tunnel, an MPLS TE tunnel, or a PW tunnel.

BFD for MPLS supports the following detection modes:

·     BFD—Detects primary path failure. 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 BFD detection mechanism fails.

BFD can also detect failures on the backup path of an MPLS TE tunnel or a PW.

·     Tunnel BFD—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 protection measure, such as MPLS L3VPN ECMP route based load balancing and FRR. This mode can minimize the traffic loss.

BFD can be implemented in control packet mode or echo packet mode. In echo packet mode, BFD for MPLS can verify the connectivity of only MPLS TE tunnels.

BFD control packet mode

In control packet mode, BFD for MPLS performs the following operations:

1.     Establishes a BFD session between the ingress and egress of the tunnel to be inspected.

2.     Adds the label associated with the tunnel into a BFD control packet at the ingress.

3.     Sends the packet to the egress node over the tunnel.

4.     Determines the tunnel status according to the BFD control packet returned by the egress.

When BFD detects a connectivity failure, it triggers the pre-configured action, such as FRR or path protection switching, to ensure uninterrupted traffic forwarding.

A BFD session for LSP, MPLS TE tunnel, or PW connectivity verification can be established in one of the following modes:

·     Static mode—On the ingress and egress nodes, manually specify the local and remote discriminators through command lines to establish the BFD session.

·     Dynamic mode—On the ingress node, manually specify the local and remote discriminators. On the egress node, you do not need to specify local and remote discriminators. After receiving an LSP ping request that carries a BFD TVL, the egress returns an LSP ping reply and establishes a passive mode BFD session.

In static mode, the egress node returns a BFD control packet to the ingress node through the reverse tunnel. If no reverse tunnel exists, the ingress node cannot receive the BFD control packet, resulting in a verification failure.

In dynamic mode, the egress node returns a BFD control packet to the ingress node through the reverse tunnel. If no reverse tunnel exists, the egress mode returns a BFD packet through IP routing.

Use the static mode to test the connectivity of a pair of LSPs or MPLS TE tunnels in opposite directions between two devices. Use the dynamic mode to test the connectivity of one LSP or MPLS TE tunnel from the local device to the remote device.

A PW is bidirectional. You will get the correct result using either the static or dynamic mode.

BFD Echo packet mode

In echo packet mode, BFD for MPLS performs the following operations:

1.     Establishes a BFD session at the ingress of the tunnel to be inspected.

2.     Adds the label associated with the tunnel into a BFD echo packet at the ingress.

3.     Sends the echo packet to the egress node over the tunnel.

4.     Without establishing a BFD session at the egress node, makes the egress node forward the echo packet back to the ingress node.

5.     Determines the tunnel status according to whether the ingress node receives the BFD echo packet.

SBFD for MPLS

SBFD for MPLS uses an SBFD session to proactively verify the connectivity of an LSP or MPLS TE tunnel. After SBFD detects a connection failure, it notifies the device to take a protection measure, such as switching traffic to the backup tunnel.

SBFD performs unidirectional detection for a path. It is faster than BFD. If only one-end of a path requires path connectivity detection, you can deploy SBFD.

SBFD for MPLS operates as follows:

1.     Establishes an SBFD session between the ingress node and egress node of the tunnel to be verified. The ingress node is the session initiator, and the egress node is the reflector.

2.     The ingress node adds the label associated with the tunnel into an SBFD control packet and sends it to the egress node over the tunnel.

3.     The egress node gets the SBFD control packet, and returns an SBFD control packet reply to the ingress node.

4.     The ingress node determines the connectivity status of the tunnel according to the received reply packet.

The device supports establishing SBFD sessions for MPLS only in static mode. You must use a command to specify the remote discriminator to establish the SBFD session.

Periodic MPLS tracert

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 in system logs. You can check the logs to monitor LSP connectivity.

If both BFD and periodic MPLS tracert are configured for an LSP, and the periodic tracert feature detects a data plane and control plane inconsistency, the device performs the following tasks:

1.     Deletes the BFD session for the LSP.

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

Protocols and standards

·     RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures

·     RFC 5085, Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires

·     RFC 5885, Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)

Verifying LSP connectivity

About LSP connectivity verification

To verify LSP connectivity, you can use one of the following methods:

·     Use the ping mpls ipv4 command or the tracert mpls ipv4 command to trigger LSP connectivity verification as needed.

·     Configure BFD or periodic MPLS tracert for the system to automatically verify LSP connectivity.

Configuring MPLS ping for LSPs

Pinging the LSPs for an IPv4 prefix

To verify MPLS LSP connectivity for an IPv4 prefix, execute the following command in any view:

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

Pinging the LSPs of the specified outgoing labels

To verify MPLS LSP connectivity by specifying the outgoing labels, execute the following command in any view:

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 ] * out-labels out-label-value&<1-6> interface interface-type interface-number [ nexthop nexthop-address ]

Configuring MPLS tracert for LSPs

Tracing the path of the LSPs for an IPv4 prefix

To trace the path that the LSPs for an IPv4 prefix take from the ingress node to the egress node, execute the following command in any view:

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

Tracing the path of the LSPs of the specified outgoing labels

To trace the path that the LSPs of the specified outgoing labels take from the ingress node to the egress node, execute the following command in any view:

tracert mpls [ -a source-ip | -exp exp-value | -h ttl-value | -r reply-mode | -rtos tos-value | -t time-out | -v | fec-check ]* out-labels out-label-value&<1-6> interface interface-type interface-number [ nexthop nexthop-address ]

Configuring BFD for LSPs (control packet mode)

About this task

Perform this task to create a BFD session for LSPs to verify the LSP connectivity.

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.

Restrictions and guidelines

To configure BFD for an LSP, configure both the local and remote devices as described in Table 1.

Table 1 Configurations on the local and remote devices

BFD session establishment mode

Node type

Execute the "mpls bfd enable" command?

Execute the "mpls bfd" command?

Configure the discriminator keyword?

Static mode

Local

Yes

Yes

Yes

Remote

Yes

Yes

Yes

Dynamic mode

Local

Yes

Yes

No

Remote

Yes

No

N/A

 

Follow these guidelines to configure BFD for an LSP tunnel:

·     To establish a static BFD session, ensure that the local and remote discriminators configured locally are identical with the remote and local discriminators configured on the remote device, respectively.

·     On a BFD session established in static mode, the ingress node and egress node both operate in active mode. On a BFD session established in dynamic mode, the ingress node operates in passive mode and the egress node operates in active mode. Executing the bfd session init-mode command on the ingress or egress node does not change the node's operating mode.

Prerequisites

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:

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

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Enable dynamic establishment of passive mode BFD sessions.

mpls bfd passive enable

By default, device can dynamically establish passive mode BFD sessions.

This command is required only on the egress node to establish a dynamic BFD session.

4.     (Optional.) Remove the Router Alert option in BFD packets.

undo bfd ip-router-alert

By default, the Router Alert option is carried in BFD packets for LSP connectivity verification.

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

5.     Configure the BFD control packet mode to verify LSP connectivity for an FEC.

¡     In static mode:

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 ]

¡     In dynamic mode:

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

mpls bfd dest-addr mask-length [ ldp-fec ] [ template template-name ]

By default, the BFD control packet mode is not configured to verify LSP connectivity for an FEC.

If you specify the next hop of an LSP, the device creates a BFD session for the LSP. If you do not specify a next hop, the device creates BFD sessions for all LSPs destined for the FEC.

You cannot specify the next hop of an LSP when configuring nested LSP connectivity verification.

Configuring BFD for LSPs (echo packet mode)

Restrictions and guidelines

If both BFD and FRR are enabled for an LSP, set the BFD detection interval for LSP connectivity verification to be longer than that for FRR. Otherwise, the BFD session for LSP connectivity verification will be down during an FRR switchover.

Prerequisites

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

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

·     Configure the bfd echo-source-ip command on the local device to specify a source IP address for echo packets.

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Configure the BFD echo packet mode to verify LSP connectivity.

mpls bfd dest-addr mask-length nexthop nexthop-address echo [ template template-name ]

mpls bfd dest-addr mask-length echo [ template template-name ]

By default, the BFD echo packet mode is not configured to verify LSP connectivity.

Configuring tunnel BFD for LSPs

 

About this task

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

Restrictions and guidelines

To configure tunnel BFD for an LSP, configure both the local and remote devices as described in Table 2.

Table 2 Configurations on the local and remote devices

BFD session establishment mode

Node type

Execute the "mpls bfd enable" command?

Execute the "mpls tunnel-bfd" command?

Configure the discriminator keyword?

Static mode

Local

Yes

Yes

Yes

Remote

Yes

Yes

Yes

Dynamic mode

Local

Yes

Yes

No

Remote

Yes

No

N/A

 

Follow these guidelines to configure tunnel BFD for an LSP tunnel:

·     To establish a static BFD session, ensure that the local and remote discriminators configured locally are identical with the remote and local discriminators configured on the remote device, respectively.

·     On a BFD session established in static mode, the ingress node and egress node both operate in active mode. On a BFD session established in dynamic mode, the ingress node operates in passive mode and the egress node operates in active mode. Executing the bfd session init-mode command on the ingress or egress node does not change the node's operating mode.

Prerequisites

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

Configuring control packet mode tunnel BFD for LSPs

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Remove the Router Alert option in BFD packets.

undo bfd ip-router-alert

By default, the Router Alert option is carried in BFD packets for LSP connectivity verification.

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

4.     Configure control packet mode tunnel BFD to verify LSP connectivity for an FEC.

¡     To use a static BFD session:

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 ]

¡     To use a dynamic BFD session:

mpls tunnel-bfd dest-addr mask-length [ ldp-fec | nil-fec ] [ template template-name ]

By default, tunnel BFD is not configured to verify LSP connectivity for an FEC.

Configuring echo packet mode tunnel BFD for LSPs

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Remove the Router Alert option in BFD packets.

undo bfd ip-router-alert

By default, the Router Alert option is carried in BFD packets for LSP connectivity verification.

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

4.     Configure echo packet mode tunnel BFD to verify LSP connectivity for an FEC.

mpls tunnel-bfd dest-addr mask-length echo [ template template-name ]

By default, tunnel BFD is not configured to verify LSP connectivity for an FEC.

Configuring SBFD for LSPs

Restrictions and guidelines

Perform this task on the initiator of an SBFD session. On the reflector of the session, specify a local discriminator by using the sbfd local-discriminator command. For more information about the sbfd local-discriminator command, see BFD configuration in High Reliability Configuration Guide.

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

Prerequisites

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

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Configure SBFD to verify LSP connectivity for an FEC.

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

By default, SBFD is not configured to verify LSP connectivity for an FEC.

Configuring periodic MPLS tracert for LSPs

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Enable periodic LSP tracert for an FEC.

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

By default, periodic LSP tracert is disabled.

Verifying MPLS TE tunnel connectivity

About MPLS TE tunnel connectivity verification

To verify MPLS TE tunnel connectivity, you can use one of the following methods:

·     Use ping mpls te command or the tracert mpls te command to trigger MPLS TE tunnel connectivity verification as needed.

·     Configure BFD for the system to automatically verify MPLS TE tunnel connectivity.

Performing MPLS ping for MPLS TE tunnels

To use MPLS ping to verify MPLS TE tunnel connectivity, execute the following command in any view:

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

Performing MPLS tracert for MPLS TE tunnels

To use MPLS tracert to trace an MPLS TE tunnel, execute the following command in any view:

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

Configuring a static BFD session for an MPLS TE tunnel

About this task

An MPLS TE tunnel can contain multiple LSPs. BFD can detect failures for the MPLS TE tunnel or for the primary or backup LSP 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 the tunnel failed.

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Create a static BFD session for connectivity verification of an MPLS TE tunnel.

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

4.     Configure local and remote discriminators for the static BFD session.

discriminator { local local-id | remote remote-id }

Configuring BFD for MPLS TE tunnels (control packet mode)

About this task

This feature enables the device to create a BFD session for an 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.

Restrictions and guidelines

To run BFD on an MPLS TE tunnel, configure both the local and remote devices as described in Table 3.

Table 3 Configurations on the local and remote devices

BFD session establishment mode

Node type

Execute the "mpls bfd enable" command?

Execute the "mpls bfd" command?

Configure the discriminator keyword?

Static mode

Local

Yes

Yes

Yes

Remote

Yes

Yes

Yes

Dynamic mode

Local

Yes

Yes

No

Remote

Yes

No

N/A

 

Follow these guidelines to configure BFD for an MPLS TE tunnel:

·     To establish a static BFD session, ensure that the local and remote discriminators configured locally are identical with the remote and local discriminators configured on the remote device, respectively.

·     On a BFD session established in static mode, the ingress node and egress node both operate in active mode. On a BFD session established in dynamic mode, the ingress node operates in passive mode and the egress node operates in active mode. Executing the bfd session init-mode command on the ingress or egress node does not change the node's operating mode.

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

·     If both BFD and FRR are enabled for an MPLS TE tunnel, set the BFD detection interval for tunnel connectivity verification to be longer than that for FRR. Otherwise, the BFD session for MPLS TE tunnel connectivity verification will be down during an FRR switchover.

Prerequisites

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:

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

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Enable dynamic establishment of passive mode BFD sessions.

mpls bfd passive enable

By default, device can dynamically establish passive mode BFD sessions.

This command is required only on the egress node to establish a dynamic BFD session.

4.     (Optional.) Configure the capability of MPLS BFD to trigger tunnel-down.

a.     Enter MPLS TE view.

mpls te

b.     Enable MPLS BFD to trigger tunnel-down.

mpls bfd trigger tunnel-down enable

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

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.

c.     Return to system view.

quit

5.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

6.     (Optional.) Configure the control packet mode BFD parameters for verifying the MPLS TE tunnel's primary path connectivity.

¡     Set the BFD detection time multiplier for the primary path.

mpls bfd detect-multiplier value

By default, the BFD detection time multiplier is not set.

¡     Set the minimum interval for the primary path to receive BFD packets.

mpls bfd min-receive-interval interval

By default, the minimum receive interval is not set.

¡     Set the minimum interval for the primary path to transmit BFD packets.

mpls bfd min-transmit-interval interval

By default, the minimum transmit interval is not set.

7.     (Optional.) Configure the control packet mode BFD parameters for verifying the MPLS TE tunnel's backup path connectivity.

¡     Set the BFD detection time multiplier for the backup path.

mpls bfd backup detect-multiplier value

By default, the BFD detection time multiplier is not set.

¡     Set the minimum interval for the backup path to receive BFD packets.

mpls bfd backup min-receive-interval interval

By default, the minimum receive interval is not set.

¡     Set the minimum interval for the backup path to transmit BFD packets.

mpls bfd backup min-transmit-interval interval

By default, the minimum transmit interval is not set.

8.     (Optional.) Configure the capability of MPLS BFD to trigger tunnel-down.

mpls bfd trigger tunnel-down { disable | enable }

By default, the configuration for this feature in MPLS TE view applies.

9.     Configure the BFD control packet mode to verify MPLS TE tunnel connectivity.

¡     In static mode:

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

¡     In dynamic mode:

mpls bfd [ template template-name ] [ backup-path template template-name ]

By default, the BFD control packet mode is not configured to verify MPLS TE tunnel connectivity.

If you specify templates for both the primary and backup paths of a tunnel, specify greater interval settings for the template of the backup path than the primary path. This rule ensures that the BFD session for the new primary path is up after a primary/backup path switchover.

Configuring BFD for MPLS TE tunnels (echo packet mode)

Restrictions and guidelines

If both BFD and FRR are enabled for an MPLS TE tunnel, set the BFD detection interval for tunnel connectivity verification to be longer than that for FRR. Otherwise, the BFD session for MPLS TE tunnel connectivity verification will be down during an FRR switchover.

Prerequisites

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

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

·     Configure the bfd echo-source-ip command on the local device to specify a source IP address for echo packets.

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Configure the capability of MPLS BFD to trigger tunnel-down.

a.     Enter MPLS TE view.

mpls te

b.     Enable MPLS BFD to trigger tunnel-down.

mpls bfd trigger tunnel-down enable

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

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.

c.     Return to system view.

quit

4.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

5.     (Optional.) Configure the echo packet mode BFD parameters for verifying the MPLS TE tunnel's primary path connectivity.

¡     Set the BFD detection time multiplier for the primary path.

mpls bfd detect-multiplier value

By default, the BFD detection time multiplier is not set.

¡     Set the minimum interval for the primary path to receive BFD packets.

mpls bfd min-receive-interval interval

By default, the minimum receive interval is not set.

6.      (Optional.) Configure the echo packet mode BFD parameters for verifying the MPLS TE tunnel's backup path connectivity.

¡     Set the BFD detection time multiplier for the backup path.

mpls bfd backup detect-multiplier value

By default, the BFD detection time multiplier is not set.

¡     Set the minimum interval for the backup path to receive BFD packets.

mpls bfd backup min-receive-interval interval

By default, the minimum receive interval is not set.

7.     (Optional.) Configure the capability of MPLS BFD to trigger tunnel-down.

mpls bfd trigger tunnel-down { disable | enable }

By default, the configuration for this feature in MPLS TE view applies.

8.     Enable the BFD echo packet mode to verify MPLS TE tunnel connectivity.

mpls bfd echo [ template template-name ] [ backup-path template template-name ]

By default, the BFD echo packet mode is not configured to verify MPLS TE tunnel connectivity.

If you specify a template for each tunnel path, specify greater interval settings for the template of the backup path than the primary path. This rule ensures that the BFD session for the new primary path is up after a primary/backup path switchover.

Configuring tunnel BFD for MPLS TE tunnels

About this task

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.

Restrictions and guidelines

To run tunnel BFD on an MPLS TE tunnel, configure both the local and remote devices as described in Table 4.

Table 4 Configurations on the local and remote devices

BFD session establishment mode

Node type

Execute the "mpls bfd enable" command?

Execute the "mpls tunnel-bfd" command?

Configure the discriminator keyword?

Static mode

Local

Yes

Yes

Yes

Remote

Yes

Yes

Yes

Dynamic mode

Local

Yes

Yes

No

Remote

Yes

No

N/A

 

Follow these guidelines to configure tunnel BFD for an MPLS TE tunnel:

·     To establish a static BFD session, ensure that the local and remote discriminators configured locally are identical with the remote and local discriminators configured on the remote device, respectively.

·     On a BFD session established in static mode, the ingress node and egress node both operate in active mode. On a BFD session established in dynamic mode, the ingress node operates in passive mode and the egress node operates in active mode. Executing the bfd session init-mode command on the ingress or egress node does not change the node's operating mode.

Prerequisites

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:

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

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

Configuring control packet mode tunnel BFD for an MPLS TE tunnel

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Enable dynamic establishment of passive mode BFD sessions.

mpls bfd passive enable

By default, device can dynamically establish passive mode BFD sessions.

This command is required only on the egress node to establish a dynamic BFD session.

4.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

5.     (Optional.) Configure BFD session parameters for verifying the MPLS TE tunnel connectivity.

¡     Configure tunnel BFD detection timer multiplier.

mpls tunnel-bfd detect-multiplier value

By default, the tunnel BFD detection time multiplier

¡     Configure the minimum receive interval for tunnel BFD packets.

mpls tunnel-bfd min-receive-interval interval

By default, the minimum receive interval is not set.

¡     Configure the minimum transmit interval for tunnel BFD packets.

mpls tunnel-bfd min-transmit-interval interval

By default, the minimum transmit interval is not set.

6.     Configure control packet mode tunnel BFD to verify MPLS TE tunnel connectivity.

¡     To use a static BFD session:

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

¡     To use a dynamic BFD session:

mpls tunnel-bfd [ template template-name ]

By default, tunnel BFD is not configured to verify MPLS TE tunnel connectivity.

If you specify templates for both BFD and tunnel BFD, specify greater interval settings for the BFD template than the tunnel BFD template. This rule ensures that the tunnel BFD session for MPLS TE tunnel is up after a primary/backup LSP switchover.

command on the local device to specify a source IP address for BFD echo packets.

Configuring echo packet mode tunnel BFD for an MPLS TE tunnel

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     (Optional.) Enable dynamic establishment of passive mode BFD sessions.

mpls bfd passive enable

By default, device can dynamically establish passive mode BFD sessions.

This command is required only on the egress node to establish a dynamic BFD session.

4.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

5.     (Optional.) Configure BFD session parameters for verifying the MPLS TE tunnel connectivity.

¡     Configure tunnel BFD detection timer multiplier.

mpls tunnel-bfd detect-multiplier value

By default, the tunnel BFD detection time multiplier

¡     Configure the minimum receive interval for tunnel BFD packets.

mpls tunnel-bfd min-receive-interval interval

By default, the minimum receive interval is not set.

¡     Configure the minimum transmit interval for tunnel BFD packets.

mpls tunnel-bfd min-transmit-interval interval

By default, the minimum transmit interval is not set.

6.     Configure echo packet mode tunnel BFD to verify MPLS TE tunnel connectivity.

mpls tunnel-bfd echo [ template template-name ]

By default, tunnel BFD is not configured to verify MPLS TE tunnel connectivity.

If you specify templates for both BFD and tunnel BFD, specify greater interval settings for the BFD template than the tunnel BFD template. This rule ensures that the tunnel BFD session for MPLS TE tunnel is up after a primary/backup LSP switchover.

Configuring SBFD for MPLS TE tunnels

Restrictions and guidelines

Perform this task on the initiator of an SBFD session. On the reflector of the session, specify a local discriminator by using the sbfd local-discriminator command. For more information about the sbfd local-discriminator command, see BFD configuration in High Reliability Configuration Guide.

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

Prerequisites

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

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

4.     (Optional.) Configure SBFD session parameters for verifying the MPLS TE tunnel connectivity.

¡     Configure SBFD detection timer multiplier.

mpls bfd detect-multiplier value

By default, the SBFD detection time multiplier

¡     Configure the minimum receive interval for SBFD packets.

mpls bfd min-receive-interval interval

By default, the minimum receive interval is not set.

¡     Configure the minimum transmit interval for SBFD packets.

mpls bfd min-transmit-interval interval

By default, the minimum transmit interval is not set.

5.     Configure SBFD to verify MPLS TE tunnel connectivity.

mpls sbfd remote remote-id [ template template-name ] [ backup-path template template-name ]

By default, SBFD is not configured to verify MPLS TE tunnel connectivity.

Configuring tunnel SBFD for MPLS TE tunnels

About the task

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.

Restrictions and guidelines

Perform this task on the initiator of the SBFD session.

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.

Prerequisites

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.

Procedure

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

4.     (Optional.) Configure SBFD session parameters for verifying the MPLS TE tunnel connectivity.

¡     Configure tunnel SBFD detection timer multiplier.

mpls tunnel-bfd detect-multiplier value

By default, the SBFD detection time multiplier

¡     Configure the minimum receive interval for tunnel SBFD packets.

mpls tunnel-bfd min-receive-interval interval

By default, the minimum receive interval is not set.

¡     Configure the minimum transmit interval for tunnel SBFD packets.

mpls tunnel-bfd min-transmit-interval interval

By default, the minimum transmit interval is not set.

5.     Configure tunnel SBFD to verify MPLS TE tunnel connectivity.

mpls tunnel-sbfd [ remote remote-id ] [ template template-name ]

By default, tunnel SBFD is not configured to verify MPLS TE tunnel connectivity.

Verifying PW connectivity

About PW connectivity verification

Virtual Circuit Connectivity Verification (VCCV) is an L2VPN PW OAM feature to verify PW connectivity in data plane. VCCV can be implemented in the following modes:

·     On-demand mode—Execute the ping mpls pw command to trigger PW connectivity detection.

·     Proactive mode—Configure BFD for a PW to test PW connectivity.

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

A CC can be control word. This type of CC 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 "Configuring MPLS L2VPN."

Connectivity Verification (CV) tools include the following types:

·     MPLS ping—Uses MPLS ping to verify PW connectivity.

·     BFD—Uses BFD to verify PW connectivity. BFD packets use IP/UDP encapsulation (with IP/UDP headers).

Performing MPLS ping for a PW

Prerequisites

Before you configure MPLS ping for a PW, perform the following tasks:

1.     Create a PW class, and use the vccv cc command to configure the VCCV CC type in PW class view.

2.     Create the PW, and use the PW class created in the previous step for the PW.

Procedure

To use MPLS ping to verify the connectivity of a PW, execute the following command in any view:

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 [ remote remote-ip-address remote-pw-id ]

Configuring BFD for a PW

About this task

How BFD verifies PW connectivity depends on the configurations on both PEs:

·     If both PEs of the PW have configured BFD and use the same BFD packet encapsulation type, the PEs use the specified encapsulation type to verify PW connectivity. Otherwise, the PEs do not use BFD to verify PW connectivity.

·     If both PEs have specified the same VCCV CC type, the specified VCCV CC type is used. Otherwise, the PEs do not use any CC and they cannot establish a BFD session for the PW.

Creating a PW class

1.     Enter system view.

system-view

2.     Create a PW class and enter PW class view.

pw-class class-name

3.     Use BFD to verify PW connectivity.

vccv bfd [ template template-name ]

By default, BFD is not used to verify PW connectivity.

4.     Specify the VCCV CC type.

vccv cc control-word

By default, no VCCV CC type is specified.

You must specify the control-word keyword to use a static BFD session for PW connectivity verification.

Configuring static BFD for a PW

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Configure a PW, specify a PW class, and enter PW view. Choose one option as needed:

¡     Execute the following commands in sequence to enter cross-connect PW view:

xconnect-group group-name

connection connection-name

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] pw-class class-name [ tunnel-policy tunnel-policy-name ]

¡     Execute the following commands in sequence to enter VSI static PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling static

peer ip-address pw-id pw-id in-label label-value out-label label-value pw-class class-name [ hub | no-split-horizon | tunnel-policy tunnel-policy-name ] *

¡     Execute the following commands in sequence to enter VSI LDP PW view:

vsi vsi-name [ hub-spoke ]

pwsignaling ldp

peer ip-address pw-id pw-id pw-class class-name [ hub | no-split-horizon | tnl-policy tunnel-policy-name ] *

4.     Execute the following commands to return to system view:

quit

quit

5.     Create a static BFD session for PW connectivity verification, and enter static BFD session view.

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

6.     Configure local and remote discriminators for the static BFD session.

discriminator { local local-id | remote remote-id }

Configuring BFD for a static PW or an LDP PW of MPLS L2VPN

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Enter cross-connect group view.

xconnect-group group-name

4.     Enter cross-connect view.

connection connection-name

5.     Configure a PW, specify the created PW class for it, and enter PW view.

peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] pw-class class-name [ tunnel-policy tunnel-policy-name ]

By default, no PW is configured.

6.     (Optional.) Set the local and remote discriminators for the BFD session used to verify PW connectivity.

bfd discriminator local local-id remote remote-id

By default, no local and remote discriminators are set.

Make sure the local and remote PEs use the same local and remote discriminators.

7.     (Optional.) Configure a backup PW for BFD detection:

a.     Configure a backup PW, specify the PW class for the backup PW, and enter backup PW view.

backup-peer ip-address pw-id pw-id [ in-label label-value out-label label-value ] pw-class class-name [ tunnel-policy tunnel-policy-name ]

By default, no backup PW is configured.

b.     (Optional.) Set the local and remote discriminators for the BFD session used to verify the connectivity of the backup PW.

bfd discriminator local local-id remote remote-id

By default, no local and remote discriminators are configured.

Make sure the local and remote PEs use the same local and remote discriminators.

Configuring BFD for a VPLS static PW

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Enter VSI view.

vsi vsi-name [ hub-spoke ]

4.     Configure the VSI to establish static PWs, and enter VSI static view.

pwsignaling static

By default, no PW signaling protocol is specified for a VSI.

5.     Configure a VPLS PW, specify the created PW class for it, and enter VSI static PW view.

peer ip-address pw-id pw-id in-label label-value out-label label-value pw-class class-name [ hub | no-split-horizon | tunnel-policy tunnel-policy-name ] *

By default, no VPLS PW is configured.

6.     (Optional.) Set the local and remote discriminators for the BFD session used to verify PW connectivity.

bfd discriminator local local-id remote remote-id

By default, no local and remote discriminators are set.

Make sure the local and remote PEs use the same local and remote discriminators.

7.     (Optional.) Configure a static backup PW for BFD detection:

a.     Configure a static backup PW, specify the PW class for the backup PW, and enter VSI static backup PW view.

backup-peer ip-address pw-id pw-id in-label label-value out-label label-value pw-class class-name [ tunnel-policy tunnel-policy-name ]

By default, no backup VPLS PW is configured.

b.     Set the local and remote discriminators for the BFD session used to verify the connectivity of the backup PW.

bfd discriminator local local-id remote remote-id

By default, no local and remote discriminators are set.

Make sure the local and remote PEs use the same local and remote discriminators.

Configuring BFD for a VPLS LDP PW

1.     Enter system view.

system-view

2.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

3.     Enter VSI view.

vsi vsi-name [ hub-spoke ]

4.     Configure the VSI to establish PWs using LDP and enter VSI LDP view.

pwsignaling ldp

By default, no PW signaling protocol is specified for a VSI.

5.     Configure a VPLS PW, specify the created PW class for it, and enter VSI LDP PW view.

peer ip-address pw-id pw-id pw-class class-name [ hub | no-split-horizon | tnl-policy tunnel-policy-name ] *

By default, no VPLS PW is configured.

6.     (Optional.) Set the local and remote discriminators for the BFD session used to verify PW connectivity.

bfd discriminator local local-id remote remote-id

By default, no local and remote discriminators are set.

Make sure the local and remote PEs use the same local and remote discriminators.

7.     (Optional.) Configure an LDP backup PW for BFD detection:

a.     Configure an LDP backup PW, specify the PW class for the backup PW, and enter VSI LDP backup PW view.

backup-peer ip-address pw-id pw-id pw-class class-name [ tunnel-policy tunnel-policy-name ]

By default, no backup VPLS PW is configured.

b.     Set the local and remote discriminators for the BFD session used to verify the connectivity of the backup PW.

bfd discriminator local local-id remote remote-id

By default, no local and remote discriminators are set.

Make sure the local and remote PEs use the same local and remote discriminators.

Display and maintenance commands for MPLS OAM

Execute display commands in any view.

 

Task

Command

Display BFD information for LSP tunnels or MPLS TE tunnels.

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

Display BFD information for PWs.

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

 

MPLS OAM configuration examples

Example: Configuring BFD for LSP

Network configuration

Use LDP to establish an LSP from 1.1.1.9/32 to 3.3.3.9/32 and an LSP from 3.3.3.9/32 to 1.1.1.9/32. Use BFD to verify LSP connectivity.

Figure 1 Network diagram

Procedure

IMPORTANT

IMPORTANT:

By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.

1.     Configure IP addresses for interfaces. (Details not shown.)

2.     Configure OSPF to ensure IP connectivity between the routers:

# Configure Router A.

<RouterA> system-view

[RouterA] ospf

[RouterA-ospf-1] area 0

[RouterA-ospf-1-area-0.0.0.0] network 1.1.1.9 0.0.0.0

[RouterA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255

[RouterA-ospf-1-area-0.0.0.0] quit

[RouterA-ospf-1] quit

# Configure Router B.

<RouterB> system-view

[RouterB] ospf

[RouterB-ospf-1] area 0

[RouterB-ospf-1-area-0.0.0.0] network 2.2.2.9 0.0.0.0

[RouterB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255

[RouterB-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255

[RouterB-ospf-1-area-0.0.0.0] quit

[RouterB-ospf-1] quit

# Configure Router C.

<RouterC> system-view

[RouterC] ospf

[RouterC-ospf-1] area 0

[RouterC-ospf-1-area-0.0.0.0] network 3.3.3.9 0.0.0.0

[RouterC-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255

[RouterC-ospf-1-area-0.0.0.0] quit

[RouterC-ospf-1] quit

3.     Enable MPLS and LDP:

# Configure Router A.

[RouterA] mpls lsr-id 1.1.1.9

[RouterA] mpls ldp

[RouterA-ldp] quit

[RouterA] interface hundredgige 1/0/1

[RouterA-HundredGigE1/0/1] mpls enable

[RouterA-HundredGigE1/0/1] mpls ldp enable

[RouterA-HundredGigE1/0/1] quit

# Configure Router B.

[RouterB] mpls lsr-id 2.2.2.9

[RouterB] mpls ldp

[RouterB-ldp] quit

[RouterB] interface hundredgige 1/0/1

[RouterB-HundredGigE1/0/1] mpls enable

[RouterB-HundredGigE1/0/1] mpls ldp enable

[RouterB-HundredGigE1/0/1] quit

[RouterB] interface hundredgige 1/0/2

[RouterB-HundredGigE1/0/2] mpls enable

[RouterB-HundredGigE1/0/2] mpls ldp enable

[RouterB-HundredGigE1/0/2] quit

# Configure Router C.

[RouterC] mpls lsr-id 3.3.3.9

[RouterC] mpls ldp

[RouterC-ldp] quit

[RouterC] interface hundredgige 1/0/2

[RouterC-HundredGigE1/0/2] mpls enable

[RouterC-HundredGigE1/0/2] mpls ldp enable

[RouterC-HundredGigE1/0/2] quit

4.     Enable BFD for MPLS, and configure BFD to verify LSP connectivity:

# Configure Router A.

[RouterA] mpls bfd enable

[RouterA] mpls bfd 3.3.3.9 32

# Configure Router C.

[RouterC] mpls bfd enable

[RouterC] mpls bfd 1.1.1.9 32

Verifying the configuration

# Display BFD information for LSPs on Router A and Router C, for example, on Router A.

[RouterA] display mpls bfd

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

 

 FEC Type: LSP

 FEC Info:

   Destination: 1.1.1.9

   Mask Length: 32

 NHLFE ID: -

 Local Discr: 513                    Remote Discr: 513

 Source IP: 1.1.1.9                  Destination IP: 3.3.3.9

 Session State: Up                   Session Role: Active

 Template Name: -

 

 FEC Type: LSP

 FEC Info:

   Destination: 3.3.3.9

   Mask Length: 32

 NHLFE ID: 1042

 Local Discr: 514                    Remote Discr: 514

 Source IP: 1.1.1.9                  Destination IP: 127.0.0.1

 Session State: Up                   Session Role: Passive

 Template Name: -

The output shows that two BFD sessions have been established between Router A and Router C. One session verifies the connectivity of the LSP from 3.3.3.9/32 to 1.1.1.9/32, and the other session verifies the connectivity of the LSP from 1.1.1.9/32 to 3.3.3.9/32.

 

  • Cloud & AI
  • InterConnect
  • Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网