10-MPLS Configuration Guide

HomeSupportConfigure & DeployConfiguration GuidesH3C MSR810 2600 3600 Routers Configuration Guides(V7)-R0707-6W30110-MPLS Configuration Guide
11-MPLS OAM configuration
Title Size Download
11-MPLS OAM configuration 147.05 KB

Configuring MPLS OAM

About MPLS OAM

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

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

Support for the fault management tools varies by MPLS tunnel type.

·     LSP tunnels support all tools.

·     MPLS TE tunnels do not support periodic MPLS tracert.

·     MPLS PWs do not support MPLS tracert and periodic MPLS tracert.

MPLS ping

MPLS ping tests the connectivity of a tunnel. 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 a tunnel travels from the ingress to the egress to locate errors on the tunnel. MPLS tracert consecutively sends MPLS echo requests along the 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 a tunnel.

MPLS supported BFD modes include the control packet mode and the echo packet mode.

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 tunnel connectivity verification can be established in one of the following modes:

·     Static mode—You manually specify the local and remote discriminators through command lines to establish the BFD session.

·     Dynamic mode—The system automatically runs MPLS ping to negotiate the discriminators to establish the 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 tunnels in opposite directions between two devices. Use the dynamic mode to test the connectivity of one 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.

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)

Restrictions: Hardware compatibility with MPLS OAM

Hardware

MPLS OAM compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK: Yes

MSR810-LMS-EA: No

MSR810-LMS, MSR810-LUS

No

MSR2600-6-X1, MSR2600-10-X1

Yes

MSR 2630

Yes

MSR3600-28, MSR3600-51

Yes

MSR3600-28-SI, MSR3600-51-SI

No

MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP

Yes

MSR3610-I-DP, MSR3610-IE-DP

Yes

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC

Yes

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

Yes

MSR3610-G, MSR3620-G

Yes

 

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

To use MPLS ping 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 ] ] ]

Configuring MPLS tracert for LSPs

To use MPLS tracert to trace the LSPs for an IPv4 prefix, 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 ] * ipv4 ipv4-address mask-length [ destination start-address [ end-address [ address-increment ] ] ]

Configuring BFD control packet mode for LSPs

About configuring BFD control packet mode for LSPs

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

When FRR is configured on the device, you can perform this task to create a BFD session for the primary LSP and the backup LSP respectively. When the primary LSP fails, BFD can quickly detect the failure and notify the device to take an action, such as switching traffic to the backup LSP. If the primary LSP and the backup LSP both fail, the device cannot forward traffic over the LSPs.

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 egress node operates in active mode and the ingress node operates in passive 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:

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.

Procedure

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 BFD to verify LSP connectivity for an FEC.

mpls bfd dest-addr mask-length nexthop nexthop-address [ discriminator local local-id remote remote-id ] [ template template-name ]

mpls bfd dest-addr mask-length [ template template-name ] [ backup-path template template-name ]

By default, BFD 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.

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

Configuring BFD echo packet mode for LSPs

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:

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.

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 ] [ backup-path template template-name ]

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

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

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.

Configuring 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

Configuring 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 BFD control packet mode for MPLS TE tunnels

Restrictions and guidelines

To run BFD on an MPLS TE tunnel, 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 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 egress node operates in active mode and the ingress node operates in passive mode. Executing the bfd session init-mode command on the ingress or egress node does not change the node's operating mode.

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

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.     Configure BFD control packet mode to verify MPLS TE tunnel connectivity.

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

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

Configuring BFD echo packet mode for MPLS TE tunnels

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:

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.

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.     Enter the view of an MPLS TE tunnel interface.

interface tunnel number

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

mpls bfd echo

By default, the BFD echo packet mode 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 or raw-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).

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 "Configuring MPLS L2VPN."

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

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

·     Raw-BFDUses BFD to verify PW connectivity. BFD packets use PW-ACH encapsulation (without IP/UDP headers). Raw-BFD takes effect only when the CC type is control-word.

Configuring 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

Configuring BFD for a PW

Restrictions and guidelines for PW connectivity verification through BFD

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. If the PEs have specified different VCCV CC types, 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.     Enable BFD for MPLS.

mpls bfd enable

By default, BFD for MPLS is disabled.

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

pw-class class-name

4.     Use BFD to verify PW connectivity.

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

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

If you specify the raw-bfd keyword in this command, make sure you specify the VCCV CC type as control-word.

5.     Specify the VCCV CC type.

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

By default, no VCCV CC type is specified.

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

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

Display BFD information for LSP tunnels or MPLS TE tunnels.

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

 

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

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 gigabitethernet 1/0/1

[RouterA-GigabitEthernet1/0/1] mpls enable

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

[RouterA-GigabitEthernet1/0/1] quit

# Configure Router B.

[RouterB] mpls lsr-id 2.2.2.9

[RouterB] mpls ldp

[RouterB-ldp] quit

[RouterB] interface gigabitethernet 1/0/1

[RouterB-GigabitEthernet1/0/1] mpls enable

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

[RouterB-GigabitEthernet1/0/1] quit

[RouterB] interface gigabitethernet 1/0/2

[RouterB-GigabitEthernet1/0/2] mpls enable

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

[RouterB-GigabitEthernet1/0/2] quit

# Configure Router C.

[RouterC] mpls lsr-id 3.3.3.9

[RouterC] mpls ldp

[RouterC-ldp] quit

[RouterC] interface gigabitethernet 1/0/2

[RouterC-GigabitEthernet1/0/2] mpls enable

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

[RouterC-GigabitEthernet1/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
  • Intelligent 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
新华三官网