No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
CloudEngine 12800 V200R019C10 Configuration Guide - MPLS

This document describes the configurations of MPLS, including MPLS Basic, MPLS LDP, MPLS QoS, MPLS TE, and SR-MPLS TE.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuration Examples for SR-MPLS TE

Configuration Examples for SR-MPLS TE

This section only provides configuration examples for individual features. For details about multi-feature configuration examples, feature-specific configuration examples, interoperation examples, protocol or hardware replacement examples, and industry application examples, see the Typical Configuration Examples.

Example for Configuring an SR-MPLS TE Tunnel

Networking Requirements

On the network shown in Figure 5-33, a customer wants to establish a tunnel and an LSP from PE1 to PE2. The SR protocol is used for path generation and data forwarding. PE1, P1, and PE2 are the ingress, transit, and egress nodes, respectively. P1 is responsible for collecting network topology information and reporting collected information to the controller using Border Gateway Protocol-link state (BGP-LS). The controller calculates LSPs based on received topology information and delivers path information to PE1.

Figure 5-33 SR-MPLS TE tunnel networking

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure an IP address for each interface, and configure IS-IS on each node to ensure there are reachable routes between them.

  2. Enable MPLS, MPLS TE, and SR globally on each node and enable MPLS and MPLS TE on each interface to establish an SR-MPLS TE tunnel.

  3. Enable the IS-IS SR-MPLS TE capability on each node, so that TE information can be advertised to other nodes.

  4. Establish a BGP-LS peer relationship between P1 and the controller, so that P1 can report topology information to the controller using BGP-LS.

  5. Configure a tunnel interface on PE1, and specify a tunnel IP address, tunneling protocol, destination IP address, and tunnel bandwidth.

Data Plan

To complete the configuration, you need the following data:

  • Interface IP addresses for device interconnection, as shown in Figure 5-33

  • IS-IS process ID (1), IS-IS system ID of each node (converted from each node's loopback0 IP address), and IS-IS level (level-2)

  • BGP process ID (100) for establishing a BGP-LS peer relationship between the controller and P1, as shown in Figure 5-33

Procedure

  1. Assign IP addresses to the interfaces.

    Configure an IP address and a subnet mask for each interface. For details, see Configuration Files in this example.

  2. Configure IS-IS to advertise the route to each network segment of each interface and to advertise the host route to each loopback address (used as an LSR ID).

    Configure IS-IS on PE1, P1, and PE2 to ensure there are reachable routes between them. For details, see Configuration Files in this example.

  3. Configure basic MPLS functions and enable MPLS TE.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] mpls lsr-id 2.1.2.9
[*PE1] mpls
[*PE1-mpls] mpls te
[*PE1-mpls] quit
[*PE1] interface 10ge 1/0/1
[*PE1-10GE1/0/1] mpls
[*PE1-10GE1/0/1] mpls te
[*PE1-10GE1/0/1] quit
[*PE1] commit

  4. Enable the SR capability globally on each node.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] segment-routing
[*PE1-segment-routing] quit
[*PE1] commit

  5. Enable the IS-IS SR-MPLS TE capability on each node.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] isis 1
[~PE1-isis-1] cost-style wide
[*PE1-isis-1] traffic-eng level-2
[*PE1-isis-1] segment-routing mpls
[*PE1-isis-1] quit
[*PE1] commit

  6. Configure a BGP-LS peer relationship between the controller and the forwarder (P1).

    Configure a BGP-LS peer relationship between the controller and P1, so that P1 can report topology information to the controller using BGP-LS.

    # On P1, configure the IS-IS network topology advertisement to BGP.
    [~P1] isis 1
[~P1-isis-1] bgp-ls enable level-2
[*P1-isis-1] bgp-ls identifier 20
[*P1-isis-1] quit
[*P1] commit
    # On P1, configure the BGP-LS route advertisement capability.
    [~P1] bgp 100
[*P1-bgp] peer 7.1.2.9 as-number 100
[*P1-bgp] link-state-family unicast
[*P1-bgp-af-ls] peer 7.1.2.9 enable
[*P1-bgp-af-ls] quit
[*P1-bgp] quit
[*P1] commit

  7. Configure a tunnel interface on the ingress node.

    # Configure PE1.

    [~PE1] interface tunnel1
[*PE1-Tunnel1] ip address unnumbered interface loopback 0
[*PE1-Tunnel1] tunnel-protocol mpls te
[*PE1-Tunnel1] destination 4.1.2.9
[*PE1-Tunnel1] mpls te tunnel-id 1
[*PE1-Tunnel1] mpls te signal-protocol segment-routing
[*PE1-Tunnel1] mpls te pce delegate
[*PE1-Tunnel1] quit
[*PE1] commit

  8. Verify the configuration.

    # After the configurations are complete, run the display bgp link-state unicast peer command on P1. You can view information about the BGP-LS peer and its status.
    [~P1] display bgp link-state unicast peer
 BGP local router ID        : 11.1.1.2
 Local AS number            : 100
 Total number of peers      : 1
 Peers in established state : 1

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State  PrefRcv
  7.1.2.9         4         100       27       48     0 00:29:11 Established       17
    # Run the display interface tunnel command on PE1. You can view that the tunnel interface status is Up.
    [~PE1] display interface tunnel
Tunnel1 current state : UP (ifindex: 1554)
Line protocol current state : UP 
Last line protocol up time : 2017-04-06 14:20:51
Description: 
Route Port,The Maximum Transmit Unit is 1500
Internet Address is unnumbered, using address of LoopBack0(2.1.2.9/32)
Encapsulation is TUNNEL, loopback not set
Tunnel destination 4.1.2.9
Tunnel up/down statistics 1
Tunnel ct0 bandwidth is 0 Kbit/sec
Tunnel protocol/transport MPLS/MPLS, ILM is available
primary tunnel id is 0x6001, secondary tunnel id is 0x0
Current system time: 2017-04-06 15:41:50
    0 seconds output rate 0 bits/sec, 0 packets/sec
    0 seconds output rate 0 bits/sec, 0 packets/sec
    0 packets output,  0 bytes
    0 output error
    0 output drop
    Last 300 seconds input utility rate:  --
    Last 300 seconds output utility rate: --
    # Run the display mpls te tunnel command on PE1. You can view the information about SR-MPLS TE tunnel establishment.
    [~PE1] display mpls te tunnel -------------------------------------------------------------------------------
Ingress LsrId   Destination     LSPID In/OutLabel     R Tunnel-name
-------------------------------------------------------------------------------
2.1.2.9         4.1.2.9         7     -/33153         I Tunnel1 -------------------------------------------------------------------------------
R: Role, I: Ingress, T: Transit, E: Egress
    # Run the display mpls te tunnel path command on PE1. You can view path information of the SR-MPLS TE tunnel.
    [~PE1] display mpls te tunnel path
 Tunnel Interface Name : Tunnel1
 Lsp ID : 2.1.2.9 :1 :7
 Hop Information
  Hop 0    Link label 33153    NAI 10.1.23.3
  Hop 1    Link label 40001    NAI 20.1.34.4

Configuration Files

  • PE1 configuration file

    #
sysname PE1
#
mpls lsr-id 2.1.2.9
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.2222.2222.2222.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/1
 undo portswitch
 ip address 10.1.23.2 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0
 ip address 2.1.2.9 255.255.255.255
 isis enable 1
#
interface Tunnel1
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 4.1.2.9
 mpls te signal-protocol segment-routing
 mpls te tunnel-id 1
 mpls te pce delegate
#
return

  • P1 configuration file

    #
sysname P1
#
mpls lsr-id 3.1.2.9
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.1111.1111.1111.00
 traffic-eng level-2
 segment-routing mpls
 bgp-ls enable level-2
 bgp-ls identifier 20
#
interface 10GE1/0/1
 undo portswitch
 ip address 10.1.23.3 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/2
 undo portswitch
 ip address 20.1.34.3 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/3
 undo portswitch
 ip address 7.1.2.10 255.255.255.0
 isis enable 1
#
interface LoopBack0
 ip address 3.1.2.9 255.255.255.255
 isis enable 1
#
bgp 100
 peer 7.1.2.9 as-number 100
 #
 ipv4-family unicast
  peer 7.1.2.9 enable
 #
 link-state-family unicast
  peer 7.1.2.9 enable
#
return

  • PE2 configuration file

    #
sysname PE2
#
mpls lsr-id 4.1.2.9
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.3333.3333.3333.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/2
 undo portswitch
 ip address 20.1.34.4 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0 
 ip address 4.1.2.9 255.255.255.255
 isis enable 1
#
return

Example for Configuring Static BFD for SR-MPLS TE Tunnels

Networking Requirements

On the network shown in Figure 5-34, a customer wants to establish a tunnel and an LSP from PE1 to PE2. The SR protocol is used for path generation and data forwarding. PE1, P1, and PE2 are the ingress, transit, and egress nodes, respectively. P1 is responsible for collecting network topology information and reporting collected information to the controller using BGP-LS. The controller calculates LSPs based on received topology information and delivers path information to PE1.

Static BFD for SR-MPLS TE tunnels can be configured to quickly detect a tunnel fault and switch traffic accordingly.

If a Huawei device connects to a non-Huawei device that does not support BFD, configure one-arm BFD to detect the links.

Figure 5-34 Configuring static BFD for SR-MPLS TE tunnels

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure an IP address for each interface, and configure IS-IS on each node to ensure there are reachable routes between them.

  2. Enable MPLS, MPLS TE, and SR globally on each node and enable MPLS and MPLS TE on each interface to establish an SR-MPLS TE tunnel.

  3. Enable the IS-IS SR-MPLS TE capability on each node, so that TE information can be advertised to other nodes.

  4. Establish a BGP-LS peer relationship between P1 and the controller, so that P1 can report topology information to the controller using BGP-LS.

  5. Configure a tunnel interface on PE1, configure a reverse tunnel interface on PE2, and specify a tunnel IP address, tunneling protocol, destination IP address, and tunnel bandwidth.

  6. Configure a BFD session on PE1 and PE2 to monitor the SR-MPLS TE tunnel.

Data Plan

To complete the configuration, you need the following data:

  • Interface IP addresses for device interconnection, as shown in Figure 5-34

  • IS-IS process ID (1), IS-IS system ID of each node (converted from each node's loopback0 IP address), and IS-IS level (level-2)

  • BGP process ID (100) for establishing a BGP-LS peer relationship between the controller and P1, as shown in Figure 5-34

  • Name, local and remote discriminators of a BFD session

Procedure

  1. Assign IP addresses to the interfaces.

    Configure an IP address and a subnet mask for each interface. For details, see Configuration Files in this example.

  2. Configure IS-IS to advertise the route to each network segment of each interface and to advertise the host route to each loopback address (used as an LSR ID).

    Configure IS-IS on PE1, P1, and PE2 to ensure reachable routes between them. For details, see Configuration Files in this example.

  3. Configure basic MPLS functions and enable MPLS TE.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] mpls lsr-id 2.1.2.9
[*PE1] mpls
[*PE1-mpls] mpls te
[*PE1-mpls] quit
[*PE1] interface 10ge 1/0/1
[*PE1-10GE1/0/1] mpls
[*PE1-10GE1/0/1] mpls te
[*PE1-10GE1/0/1] quit
[*PE1] commit

  4. Enable the SR capability globally on each node.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] segment-routing
[*PE1-segment-routing] quit
[*PE1] commit

  5. Enable the IS-IS SR-MPLS TE capability on each node.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] isis 1
[~PE1-isis-1] cost-style wide
[*PE1-isis-1] traffic-eng level-2
[*PE1-isis-1] segment-routing mpls
[*PE1-isis-1] quit
[*PE1] commit

  6. Configure a BGP-LS peer relationship between the controller and the forwarder (P1).

    Configure a BGP-LS peer relationship between the controller and P1, so that P1 can report topology information to the controller using BGP-LS.

    # On P1, configure the IS-IS network topology advertisement to BGP.
    [~P1] isis 1
[~P1-isis-1] bgp-ls enable level-2
[*P1-isis-1] bgp-ls identifier 20
[*P1-isis-1] quit
[*P1] commit
    # On P1, configure the BGP-LS route advertisement capability.
    [~P1] bgp 100
[*P1-bgp] peer 7.1.2.9 as-number 100
[*P1-bgp] link-state-family unicast
[*P1-bgp-af-ls] peer 7.1.2.9 enable
[*P1-bgp-af-ls] quit
[*P1-bgp] quit
[*P1] commit

  7. Configure a tunnel interface on the ingress node and a reverse tunnel interface on the egress node.

    # Configure PE1.

    [~PE1] interface tunnel1
[*PE1-Tunnel1] ip address unnumbered interface loopback 0
[*PE1-Tunnel1] tunnel-protocol mpls te
[*PE1-Tunnel1] destination 4.1.2.9
[*PE1-Tunnel1] mpls te tunnel-id 1
[*PE1-Tunnel1] mpls te signal-protocol segment-routing
[*PE1-Tunnel1] mpls te pce delegate
[*PE1-Tunnel1] quit
[*PE1] commit

    # Configure PE2.

    [~PE2] interface tunnel1
[*PE2-Tunnel1] ip address unnumbered interface loopback 0
[*PE2-Tunnel1] tunnel-protocol mpls te
[*PE2-Tunnel1] destination 2.1.2.9
[*PE2-Tunnel1] mpls te tunnel-id 2
[*PE2-Tunnel1] mpls te signal-protocol segment-routing
[*PE2-Tunnel1] mpls te pce delegate
[*PE2-Tunnel1] quit
[*PE2] commit

  8. Verify the configuration.

    # After the configurations are complete, run the display bgp link-state unicast peer command on P1. You can view information about the BGP-LS peer and its status.
    [~P1] display bgp link-state unicast peer
 BGP local router ID        : 11.1.1.2
 Local AS number            : 100
 Total number of peers      : 1
 Peers in established state : 1

  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State  PrefRcv
  7.1.2.9         4         100       27       48     0 00:29:11 Established       17
    # Run the display interface tunnel command on PE1. You can view that the tunnel interface status is Up.
    [~PE1] display interface tunnel
Tunnel1 current state : UP (ifindex: 1554)
Line protocol current state : UP 
Last line protocol up time : 2017-04-06 14:20:51
Description: 
Route Port,The Maximum Transmit Unit is 1500
Internet Address is unnumbered, using address of LoopBack0(2.1.2.9/32)
Encapsulation is TUNNEL, loopback not set
Tunnel destination 4.1.2.9
Tunnel up/down statistics 1
Tunnel ct0 bandwidth is 0 Kbit/sec
Tunnel protocol/transport MPLS/MPLS, ILM is available
primary tunnel id is 0x6001, secondary tunnel id is 0x0
Current system time: 2017-04-06 15:41:50
    0 seconds output rate 0 bits/sec, 0 packets/sec
    0 seconds output rate 0 bits/sec, 0 packets/sec
    0 packets output,  0 bytes
    0 output error
    0 output drop
    Last 300 seconds input utility rate:  --
    Last 300 seconds output utility rate: --
    # Run the display mpls te tunnel command on PE1. You can view the information about SR-MPLS TE tunnel establishment.
    [~PE1] display mpls te tunnel -------------------------------------------------------------------------------
Ingress LsrId   Destination     LSPID In/OutLabel     R Tunnel-name
-------------------------------------------------------------------------------
2.1.2.9         4.1.2.9         7     -/33153         I Tunnel1 -------------------------------------------------------------------------------
R: Role, I: Ingress, T: Transit, E: Egress
    # Run the display mpls te tunnel path command on PE1. You can view path information of the SR-MPLS TE tunnel.
    [~PE1] display mpls te tunnel path
 Tunnel Interface Name : Tunnel1
 Lsp ID : 2.1.2.9 :1 :7
 Hop Information
  Hop 0    Link label 33153    NAI 10.1.23.3
  Hop 1    Link label 40001    NAI 20.1.34.4

  9. Configure BFD for SR-MPLS TE tunnels.

    # Configure a BFD session on PE1 to detect the SR-MPLS TE tunnel, and set the minimum intervals at which BFD packets are sent and received.

    [~PE1] bfd
[*PE1-bfd] quit
[*PE1] bfd pe1tope2 bind mpls-te interface tunnel1
[*PE1-bfd-lsp-session-pe1tope2] discriminator local 12
[*PE1-bfd-lsp-session-pe1tope2] discriminator remote 21
[*PE1-bfd-lsp-session-pe1tope2] commit

    # Configure a BFD session on PE2 to detect the reverse SR-MPLS TE tunnel, and set the minimum intervals at which BFD packets are sent and received.

    [~PE2] bfd
[*PE2-bfd] quit
[*PE2] bfd pe2tope1 bind mpls-te interface tunnel1
[*PE2-bfd-lsp-session-pe2tope1] discriminator local 21
[*PE1-bfd-lsp-session-pe1tope2] discriminator remote 12
[*PE2-bfd-lsp-session-pe2tope1] commit

    # After the configurations are complete, run the display bfd session mpls-te interface tunnel command on PE1 and PE2. You can view that the status of BFD sessions is Up.

Configuration Files

  • PE1 configuration file

    #
sysname PE1
#
bfd
#
mpls lsr-id 2.1.2.9
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.2222.2222.2222.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/1
 undo portswitch
 ip address 10.1.23.2 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0
 ip address 2.1.2.9 255.255.255.255
 isis enable 1
#
 interface Tunnel1
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 4.1.2.9
 mpls te signal-protocol segment-routing
 mpls te tunnel-id 1
 mpls te pce delegate
#
bfd pe1tope2 bind mpls-te interface Tunnel1
 discriminator local 12
 discriminator remote 21
#
return

  • P1 configuration file

    #
sysname P1
#
mpls lsr-id 3.1.2.9
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.1111.1111.1111.00
 traffic-eng level-2
 segment-routing mpls
 bgp-ls enable level-2
 bgp-ls identifier 20
#
interface 10GE1/0/1
 undo portswitch
 ip address 10.1.23.3 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/2
 undo portswitch
 ip address 20.1.34.3 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/3
 undo portswitch
 ip address 7.1.2.10 255.255.255.0
 isis enable 1
#
interface LoopBack0
 ip address 3.1.2.9 255.255.255.255
 isis enable 1
#
bgp 100
 peer 7.1.2.9 as-number 100
 #
 ipv4-family unicast
  peer 7.1.2.9 enable
 #
 link-state-family unicast
  peer 7.1.2.9 enable
#
return

  • PE2 configuration file

    #
sysname PE2
#
bfd
#
mpls lsr-id 4.1.2.9
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.3333.3333.3333.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/2
 undo portswitch
 ip address 20.1.34.4 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0 
 ip address 4.1.2.9 255.255.255.255
 isis enable 1
#
 interface Tunnel1
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 2.1.2.9
 mpls te signal-protocol segment-routing
 mpls te tunnel-id 1
 mpls te pce delegate
#
bfd pe2tope1 bind mpls-te interface Tunnel1
 discriminator local 21
 discriminator remote 12
#
return

Example for Configuring Dynamic BFD for SR-MPLS TE LSPs

Networking Requirements

On the network shown in Figure 5-35, a customer wants to establish a tunnel as well as primary and backup LSPs for the tunnel from PE1 to PE2. The SR protocol is used for path generation and data forwarding. PE1, P1, and PE2 are the ingress, transit, and egress nodes, respectively. PE2 is responsible for collecting network topology information and reporting collected information to the controller using BGP-LS. The controller calculates LSPs based on received topology information and delivers path information to PE1.

The tunnel works in hot standby mode. Dynamic BFD for SR-MPLS TE LSPs can be configured to quickly detect faults on SR-MPLS TE LSPs and protect traffic transmitted along the SR-MPLS TE LSPs. If the primary LSP fails, traffic is switched to the backup LSP. If the primary LSP recovers, traffic is switched back to it.

If a Huawei device connects to a non-Huawei device that does not support BFD, configure one-arm BFD to detect the links.

Figure 5-35 Configuring dynamic BFD for SR-MPLS TE LSPs

Configuration Roadmap

The configuration roadmap is as follows:

  1. Configure an IP address for each interface, and configure IS-IS on each node to ensure there are reachable routes between them.

  2. Enable MPLS, MPLS TE, and SR globally on each node and enable MPLS and MPLS TE on each interface to establish an SR-MPLS TE tunnel.

  3. Enable the IS-IS SR-MPLS TE capability on each node, so that TE information can be advertised to other nodes.

  4. Establish a BGP-LS peer relationship between PE2 and the controller, so that PE2 can report topology information to the controller using BGP-LS.

  5. Configure a tunnel interface on PE1, and specify a tunnel IP address, tunneling protocol, destination IP address, and tunnel bandwidth.

  6. On PE1, configure hot-standby CR-LSPs for the tunnel.

  7. On PE1, enable BFD and configure dynamic BFD for SR-MPLS TE LSPs, so that PE2 passively creates a BFD session.

Data Plan

To complete the configuration, you need the following data:

  • Interface IP addresses for device interconnection, as shown in Figure 5-35

  • IS-IS process ID (1), IS-IS system ID of each node (converted from each node's loopback0 IP address), and IS-IS level (level-2)

  • BGP process ID (100) for establishing a BGP-LS peer relationship between the controller and P1, as shown in Figure 5-35.

  • Name, local and remote discriminators of a BFD session

Procedure

  1. Assign IP addresses to the interfaces.

    Configure an IP address and a subnet mask for each interface. For details, see Configuration Files in this example.

  2. Configure IS-IS to advertise the route to each network segment of each interface and to advertise the host route to each loopback address (used as an LSR ID).

    Configure IS-IS on PE1, P1, and PE2 to ensure there are reachable routes between them. For details, see Configuration Files in this example.

  3. Configure basic MPLS functions and enable MPLS TE.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] mpls lsr-id 1.1.1.1
[*PE1] mpls
[*PE1-mpls] mpls te
[*PE1-mpls] quit
[*PE1] interface 10ge 1/0/1
[*PE1-10GE1/0/1] mpls
[*PE1-10GE1/0/1] mpls te
[*PE1-10GE1/0/1] quit
[*PE1] commit

  4. Enable the SR capability globally on each node.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] segment-routing
[*PE1-segment-routing] quit
[*PE1] commit

  5. Enable the IS-IS SR-MPLS TE capability on each node.

    # Configure PE1. The configurations of P1 and PE2 are similar to that of PE1, and are not mentioned here. For details, see Configuration Files in this example.

    [~PE1] isis 1
[~PE1-isis-1] cost-style wide
[*PE1-isis-1] traffic-eng level-2
[*PE1-isis-1] segment-routing mpls
[*PE1-isis-1] quit
[*PE1] commit

  6. Configure a BGP-LS peer relationship between the controller and the forwarder (PE2).

    Configure a BGP-LS peer relationship between the controller and PE2, so that PE2 can report topology information to the controller using BGP-LS.

    # On PE2, configure the IS-IS network topology advertisement to BGP.
    [~PE2] isis 1
[~PE2-isis-1] bgp-ls enable level-2
[*PE2-isis-1] bgp-ls identifier 20
[*PE2-isis-1] quit
[*PE2] commit
    # On PE2, configure the BGP-LS route advertisement capability.
    [~PE2] bgp 100
[*PE2-bgp] peer 10.2.1.2 as-number 100
[*PE2-bgp] link-state-family unicast
[*PE2-bgp-af-ls] peer 10.2.1.2 enable
[*PE2-bgp-af-ls] quit
[*PE2-bgp] quit
[*PE2] commit

  7. Configure a tunnel interface on the ingress node.

    # Configure PE1.

    [~PE1] interface tunnel1
[*PE1-Tunnel1] ip address unnumbered interface loopback 0
[*PE1-Tunnel1] tunnel-protocol mpls te
[*PE1-Tunnel1] destination 3.3.3.3
[*PE1-Tunnel1] mpls te tunnel-id 1
[*PE1-Tunnel1] mpls te signal-protocol segment-routing
[*PE1-Tunnel1] mpls te pce delegate
[*PE1-Tunnel1] mpls te backup hot-standby
[*PE1-Tunnel1] quit
[*PE1] commit

  8. Verify the configuration.

    # After the configurations are complete, run the display mpls te tunnel-interface command on PE1. You can view the information about the SR-MPLS TE tunnel interface.

    [~PE1] display mpls te tunnel-interface tunnel 1
    Tunnel Name       : Tunnel1
    Signalled Tunnel Name: -
    Tunnel State Desc : Primary CR-LSP Up and HotBackup CR-LSP Up
    Tunnel Attributes   :     
    Active LSP          : Primary LSP
    Traffic Switch      : - 
    Session ID          : 1
    Ingress LSR ID      : 1.1.1.1               Egress LSR ID: 3.3.3.3
    Admin State         : UP                    Oper State   : UP
    Signaling Protocol  : Segment-Routing
    FTid                : 32769
    Tie-Breaking Policy : None                  Metric Type  : None
    Bfd Cap             : None                  
    Reopt               : Disabled              Reopt Freq   : -              
    Auto BW             : Disabled              Threshold    : - 
    Current Collected BW: -                     Auto BW Freq : -
    Min BW              : -                     Max BW       : -
    Offload             : Disabled              Offload Freq : - 
    Low Value           : -                     High Value   : - 
    Readjust Value      : - 
    Offload Explicit Path Name: -
    Tunnel Group        : Primary
    Interfaces Protected: -
    Excluded IP Address : -
    Referred LSP Count  : 0
    Primary Tunnel      : -                     Pri Tunn Sum : -
    Backup Tunnel       : -
    Group Status        : Up                    Oam Status   : None
    IPTN InLabel        : -                     Tunnel BFD Status : -
    BackUp LSP Type     : Hot-Standby           BestEffort   : Disabled
    Secondary HopLimit  : -
    BestEffort HopLimit  : -
    Secondary Explicit Path Name: -
    Secondary Affinity Prop/Mask: 0x0/0x0
    BestEffort Affinity Prop/Mask: 0x0/0x0  
    IsConfigLspConstraint: -
    Hot-Standby Revertive Mode:  Revertive
    Hot-Standby Overlap-path:  Disabled
    Hot-Standby Switch State:  CLEAR
    Bit Error Detection:  Disabled
    Bit Error Detection Switch Threshold:  -
    Bit Error Detection Resume Threshold:  -
    Ip-Prefix Name    : -
    P2p-Template Name : -
    PCE Delegate      : Active                 LSP Control Status : PCE control
    Auto BW Remain Time   : -                     Reopt Remain Time     : -
                                      Primary LSP ID      : 1.1.1.1:21
    LSP State           : UP                    LSP Type     : Primary
    Setup Priority      : 7                     Hold Priority: 7
    IncludeAll          : 0x0
    IncludeAny          : 0x0
    ExcludeAny          : 0x0
    Affinity Prop/Mask  : 0x0/0x0               Resv Style   :  SE
    Configured Bandwidth Information:
    CT0 Bandwidth(Kbit/sec): 0               CT1 Bandwidth(Kbit/sec): 0
    CT2 Bandwidth(Kbit/sec): 0               CT3 Bandwidth(Kbit/sec): 0
    CT4 Bandwidth(Kbit/sec): 0               CT5 Bandwidth(Kbit/sec): 0
    CT6 Bandwidth(Kbit/sec): 0               CT7 Bandwidth(Kbit/sec): 0
    Actual Bandwidth Information:
    CT0 Bandwidth(Kbit/sec): 0               CT1 Bandwidth(Kbit/sec): 0
    CT2 Bandwidth(Kbit/sec): 0               CT3 Bandwidth(Kbit/sec): 0
    CT4 Bandwidth(Kbit/sec): 0               CT5 Bandwidth(Kbit/sec): 0
    CT6 Bandwidth(Kbit/sec): 0               CT7 Bandwidth(Kbit/sec): 0
    Explicit Path Name  : -                                Hop Limit: -
    Record Route        : Disabled              Record Label : Disabled
    Route Pinning       : Disabled
    FRR Flag            : Disabled
    IdleTime Remain     : -
    BFD Status          : -
    Soft Preemption     : Disabled
    Reroute Flag        : Enabled
    Pce Flag            : Normal
                     Backup LSP ID       : 1.1.1.1:26
    IsBestEffortPath    : No
    LSP State           : UP                    LSP Type     : Hot-Standby
    Setup Priority      : 7                     Hold Priority: 7
    IncludeAll          : 0x0
    IncludeAny          : 0x0
    ExcludeAny          : 0x0
    Affinity Prop/Mask  : 0x0/0x0               Resv Style   :  SE
    Configured Bandwidth Information:
    CT0 Bandwidth(Kbit/sec): 0               CT1 Bandwidth(Kbit/sec): 0
    CT2 Bandwidth(Kbit/sec): 0               CT3 Bandwidth(Kbit/sec): 0
    CT4 Bandwidth(Kbit/sec): 0               CT5 Bandwidth(Kbit/sec): 0
    CT6 Bandwidth(Kbit/sec): 0               CT7 Bandwidth(Kbit/sec): 0
    Actual Bandwidth Information:
    CT0 Bandwidth(Kbit/sec): 0               CT1 Bandwidth(Kbit/sec): 0
    CT2 Bandwidth(Kbit/sec): 0               CT3 Bandwidth(Kbit/sec): 0
    CT4 Bandwidth(Kbit/sec): 0               CT5 Bandwidth(Kbit/sec): 0
    CT6 Bandwidth(Kbit/sec): 0               CT7 Bandwidth(Kbit/sec): 0
    Explicit Path Name  : -                                Hop Limit: -
    Record Route        : Disabled              Record Label : Disabled
    Route Pinning       : Disabled
    FRR Flag            : Disabled
    IdleTime Remain     : -
    BFD Status          : -
    Soft Preemption     : Disabled
    Reroute Flag        : Enabled
    Pce Flag            : Normal

    # Run the display mpls te tunnel command on PE1. You can view the information about SR-MPLS TE tunnel establishment.

    [~PE1] display mpls te tunnel -------------------------------------------------------------------------------
Ingress LsrId   Destination     LSPID In/OutLabel     R Tunnel-name
-------------------------------------------------------------------------------
1.1.1.1         3.3.3.3         21    -/33200         I Tunnel1
1.1.1.1         3.3.3.3         26    -/33153         I Tunnel1 -------------------------------------------------------------------------------
R: Role, I: Ingress, T: Transit, E: Egress
    # Run the display mpls te tunnel path command on PE1. You can view path information of the SR-MPLS TE tunnel.
    [~PE1] display mpls te tunnel path
 Tunnel Interface Name : Tunnel1
 Lsp ID : 1.1.1.1 :1 :21
 Hop Information
  Hop 0    Link label 33200    NAI 10.1.1.2

 Tunnel Interface Name : Tunnel1
 Lsp ID : 1.1.1.1 :1 :26
 Hop Information
  Hop 0    Link label 33153    NAI 10.1.2.2
  Hop 1    Link label 40001    NAI 10.1.3.1

  9. On PE1, enable BFD and configure BFD for SR-MPLS TE LSPs.

    # On the tunnel interface of PE1, configure BFD for SR-MPLS TE LSPs, set the minimum intervals at which BFD packets are sent and received to 100 ms, and set the local detection multiplier to 3.

    [~PE1] bfd
[*PE1-bfd] quit
[*PE1] interface tunnel 1
[*PE1-Tunnel1] mpls te bfd enable
[*PE1-Tunenl1] quit
[*PE1] commit

  10. On PE2, enable passive BFD session creation.

    [~PE2] bfd
[*PE2-bfd] mpls-passive
[*PE2-bfd] quit
[*PE2] commit

    # After the configurations are complete, run the display bfd session mpls-te interface tunnel command on PE1 and run the display bfd session all command on PE2. You can view that the status of BFD sessions is Up.

    [~PE1] display bfd session mpls-te interface tunnel 1 te-lsp
S: Static session
D: Dynamic session
IP: IP session
IF: Single-hop session
PEER: Multi-hop session
LDP: LDP session
LSP: Label switched path
TE: Traffic Engineering
AUTO: Automatically negotiated session
VXLAN: VXLAN session
(w): State in WTR
(*): State is invalid
Total UP/DOWN Session Number : 2/0
--------------------------------------------------------------------------------
Local      Remote     PeerIpAddr      State     Type        InterfaceName 
--------------------------------------------------------------------------------
16385      16386      3.3.3.3         Up        D/TE-LSP     Tunnel1
16386      16387      3.3.3.3         Up        D/TE-LSP     Tunnel1
--------------------------------------------------------------------------------
    [~PE2] display bfd session all
S: Static session
D: Dynamic session
IP: IP session
IF: Single-hop session
PEER: Multi-hop session
LDP: LDP session
LSP: Label switched path
TE: Traffic Engineering
AUTO: Automatically negotiated session
VXLAN: VXLAN session
(w): State in WTR
(*): State is invalid
Total UP/DOWN Session Number : 2/0
--------------------------------------------------------------------------------
Local      Remote     PeerIpAddr      State     Type        InterfaceName 
--------------------------------------------------------------------------------
16386      16385      1.1.1.1         Up        E_Dynamic          -
16387      16386      1.1.1.1         Up        E_Dynamic          -
--------------------------------------------------------------------------------

Configuration Files

  • PE1 configuration file

    #
sysname PE1
#
bfd
#
mpls lsr-id 1.1.1.1
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.2222.2222.2222.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/1
 undo portswitch
 ip address 10.1.1.1 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/2
 undo portswitch
 ip address 10.1.2.1 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0
 ip address 1.1.1.1 255.255.255.255
 isis enable 1
#
 interface Tunnel1
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 3.3.3.3
 mpls te signal-protocol segment-routing
 mpls te backup hot-standby
 mpls te tunnel-id 1
 mpls te pce delegate
 mpls te bfd enable
#
return

  • P1 configuration file

    #
sysname P1
#
mpls lsr-id 2.2.2.2
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.1111.1111.1111.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/2
 undo portswitch
 ip address 10.1.2.2 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/3
 undo portswitch
 ip address 10.1.3.2 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0
 ip address 2.2.2.2 255.255.255.255
 isis enable 1
#
return

  • PE2 configuration file

    #
sysname PE2
#
bfd
 mpls-passive
#
mpls lsr-id 3.3.3.3
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.3333.3333.3333.00
 traffic-eng level-2
 segment-routing mpls
 bgp-ls enable level-2
 bgp-ls identifier 20
#
interface 10GE1/0/1
 undo portswitch
 ip address 10.1.1.2 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/2
 undo portswitch
 ip address 10.2.1.1 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/3
 undo portswitch
 ip address 10.1.3.1 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface LoopBack0 
 ip address 3.3.3.3 255.255.255.255
 isis enable 1
#
bgp 100
 peer 10.2.1.2 as-number 100
 #
 ipv4-family unicast
  peer 10.2.1.2 enable
 #
 link-state-family unicast
  peer 10.2.1.2 enable
#
return

Example for Configuring an SR-MPLS TE Group to Implement Differentiated Services

Networking Requirements

On the network shown in Figure 5-36, CE1 and CE2 connect to the SR-MPLS TE network through PE1 and PE2, respectively. Various types of service packets are transmitted between CE1 and CE2. Two service types are important, with peak traffic that can reach 10,000 kbit/s and 20,000 kbit/s. The other service types are common, each with total traffic of 50,000 kbit/s. Note that the peak traffic of all common services may exceed 50,000 kbit/s.

An SR-MPLS TE group can be configured to preferentially forward important services when the network bandwidth is insufficient.

Figure 5-36 SR-MPLS TE group for implementing differentiated services

In this example, CE1 and PE1 are connected through 10GE1/0/1; CE2 and PE2 are connected through 10GE1/0/1; PE1 and PE2 are connected through 10GE1/0/2; PE1 and PE2 connect to the controller through 10GE1/0/3.


Table 5-11 Interface IP addresses

Device

Interface

IP Address

CE1

10GE1/0/1

192.168.1.1/24

CE2

10GE1/0/1

192.168.2.1/24

PE1

10GE1/0/1

192.168.1.2/24

10GE1/0/2

20.1.1.1/24

10GE1/0/3

20.1.2.1/24

LoopBack0

1.1.1.1/32

PE2

10GE1/0/1

192.168.2.2/24

10GE1/0/2

20.1.1.2/24

10GE1/0/3

20.1.3.1/24

LoopBack0

2.2.2.2/32

Configuration Roadmap

The configuration roadmap is as follows:
  1. Create three SR-MPLS TE tunnels between PE1 and PE2 and assign bandwidths for them.
  2. On PE1, import service flows to the three SR-MPLS TE tunnels, which form an equal-cost multi-path routing (ECMP) group.
  3. On PE1, set the class of service (CoS) values for the three SR-MPLS TE tunnels.
  4. On PE1, set the CoS values for the service packets to permit two important services to pass through two SR-MPLS TE tunnels and all the other common services to pass through the last SR-MPLS TE tunnel.

Data Plan

To complete the configuration, you need the following data:

  • Interface IP addresses for device interconnection, as shown in Table 5-11
  • IDs of the three SR-MPLS TE tunnels: 1, 2, and 3
  • Bandwidths for SR-MPLS TE tunnels 1, 2, and 3: 10,000 kbit/s, 20,000 kbit/s, and 50,000Kbit/s
  • CoS values for SR-MPLS TE tunnels 1, 2, and 3: AF4, CS7, and default
  • CoS values for two important service packets: AF4 and CS7

Procedure

  1. Assign IP addresses to the interfaces.

    Configure an IP address and a subnet mask for each interface. For details, see Configuration Files in this example.

  2. Configure IS-IS to advertise the route to each network segment of each interface and to advertise the host route to each loopback address (used as an LSR ID).

    Configure IS-IS on PE1 and PE2 to ensure there are reachable routes between them. For details, see Configuration Files in this example.

  3. Configure an IS-IS neighbor relationship between the controller and PE2.

    Configure an IS-IS neighbor relationship between the controller and PE2, so that PE2 can flood network topology information to the controller using IS-IS. For details, see Configuration Files in this example.

  4. Configure basic SR-MPLS TE functions.
    1. Configure basic MPLS functions and enable MPLS TE.

      # Configure PE1. The configuration of PE2 is similar to that of PE1, and is not mentioned here. For details, see Configuration Files in this example.

      [~PE1] mpls lsr-id 1.1.1.1
[*PE1] mpls
[*PE1-mpls] mpls te
[*PE1-mpls] quit
[*PE1] interface 10ge 1/0/2
[*PE1-10GE1/0/2] mpls
[*PE1-10GE1/0/2] mpls te
[*PE1-10GE1/0/2] quit
[*PE1] commit

    2. Enable the SR capability globally on each node.

      # Configure PE1. The configuration of PE2 is similar to that of PE1, and is not mentioned here. For details, see Configuration Files in this example.

      [~PE1] segment-routing
[*PE1-segment-routing] quit
[*PE1] commit

    3. Enable the IS-IS SR-MPLS TE capability on each node.

      # Configure PE1. The configuration of PE2 is similar to that of PE1, and is not mentioned here. For details, see Configuration Files in this example.

      [~PE1] isis 1
[*PE1-isis-1] cost-style wide
[*PE1-isis-1] traffic-eng level-2
[*PE1-isis-1] segment-routing mpls
[*PE1-isis-1] quit
[*PE1] commit

    4. Configure tunnel interfaces on the ingress node.

      # Configure tunnel interfaces Tunnel1, Tunnel2, and Tunnel3 on PE1.

      [~PE1] interface tunnel 1
[*PE1-Tunnel1] ip address unnumbered interface loopback 0
[*PE1-Tunnel1] tunnel-protocol mpls te
[*PE1-Tunnel1] destination 2.2.2.2
[*PE1-Tunnel1] mpls te tunnel-id 1
[*PE1-Tunnel1] mpls te signal-protocol segment-routing
[*PE1-Tunnel1] mpls te pce delegate
[*PE1-Tunnel1] quit
[*PE1] interface tunnel 2
[*PE1-Tunnel2] ip address unnumbered interface loopback 0
[*PE1-Tunnel2] tunnel-protocol mpls te
[*PE1-Tunnel2] destination 2.2.2.2
[*PE1-Tunnel2] mpls te tunnel-id 2
[*PE1-Tunnel2] mpls te signal-protocol segment-routing
[*PE1-Tunnel2] mpls te pce delegate
[*PE1-Tunnel2] quit
[*PE1] interface tunnel 3
[*PE1-Tunnel3] ip address unnumbered interface loopback 0
[*PE1-Tunnel3] tunnel-protocol mpls te
[*PE1-Tunnel3] destination 2.2.2.2
[*PE1-Tunnel3] mpls te tunnel-id 3
[*PE1-Tunnel3] mpls te signal-protocol segment-routing
[*PE1-Tunnel3] mpls te pce delegate
[*PE1-Tunnel3] quit
[*PE1] commit

    5. Import traffic to the tunnels on the ingress node.

      # On PE1, configure three static routes to 5.5.5.0, with Tunnel1, Tunnel2, and Tunnel3 as the outbound tunnel interfaces to import traffic to the tunnels.

      [~PE1] ip route-static 5.5.5.0 255.255.255.0 tunnel1
[*PE1] ip route-static 5.5.5.0 255.255.255.0 tunnel2
[*PE1] ip route-static 5.5.5.0 255.255.255.0 tunnel3
[*PE1] commit

  5. Configure the tunnel bandwidths.

    # On PE1, set the required bandwidths of tunnels Tunnel1, Tunnel2, and Tunnel3 to 10,000 kbit/s, 20,000 kbit/s, and 50,000 kbit/s respectively, and enable traffic statistics collection for the tunnels.

    [~PE1] interface tunnel 1
[*PE1-Tunnel1] mpls te bandwidth ct0 10000
[*PE1-Tunnel1] statistic enable
[*PE1-Tunnel1] quit
[*PE1] interface tunnel 2
[*PE1-Tunnel2] mpls te bandwidth ct0 20000
[*PE1-Tunnel2] statistic enable
[*PE1-Tunnel2] quit
[*PE1] interface tunnel 3
[*PE1-Tunnel3] mpls te bandwidth ct0 50000
[*PE1-Tunnel3] statistic enable
[*PE1-Tunnel3] quit
[*PE1] commit

  6. Set the CoS values for the tunnels.

    # On PE1, set the CoS values for SR-MPLS TE tunnels Tunnel1, Tunnel2, and Tunnel3 to AF4, CS7, and default.

    [~PE1] interface tunnel 1
[*PE1-Tunnel1] mpls te service-class af4 cs7
[*PE1-Tunnel1] quit
[*PE1] interface tunnel 2
[*PE1-Tunnel2] mpls te service-class af4 cs7
[*PE1-Tunnel2] quit
[*PE1] interface tunnel 3
[*PE1-Tunnel3] mpls te service-class default
[*PE1-Tunnel3] quit
[*PE1] commit

  7. Set the CoS values for packets.
    1. Configure traffic classifiers.

      [~PE1] acl 3002
[*PE1-acl4-advance-3002] rule permit ip destination 5.5.5.1 32
[*PE1-acl4-advance-3002] commit
[~PE1-acl4-advance-3002] quit
[~PE1] acl 3003
[*PE1-acl4-advance-3003] rule permit ip destination 5.5.5.2 32
[*PE1-acl4-advance-3003] commit
[~PE1-acl4-advance-3003] quit
[~PE1] traffic classifier c1
[*PE1-classifier-c1] if-match acl 3002
[*PE1-classifier-c1] quit
[*PE1] traffic classifier c2
[*PE1-classifier-c2] if-match acl 3003
[*PE1-classifier-c2] quit
[*PE1] commit

    2. Configure traffic behavior.

      [~PE1] traffic behavior b1
[*PE1-behavior-b1] remark local-precedence af4
[*PE1-behavior-b1] quit
[*PE1] traffic behavior b2
[*PE1-behavior-b2] remark local-precedence cs7
[*PE1-behavior-b2] quit
[*PE1] commit

    3. Configure a traffic policy.

      [~PE1] traffic policy p1
[*PE1-trafficpolicy-p1] classifier c1 behavior b1
[*PE1-trafficpolicy-p1] classifier c2 behavior b2
[*PE1-trafficpolicy-p1] quit
[*PE1] commit

    4. Apply the traffic policy.

      [~PE1] interface 10ge 1/0/1
[*PE1-10GE1/0/1] traffic-policy p1 inbound
[*PE1-10GE1/0/1] quit
[*PE1] commit

  8. Verify the configuration.

    After the configurations are complete, run the display mpls te tunnel command on PE1. You can view that three SR-MPLS TE tunnels are set up.

    [~PE1] display mpls te tunnel -------------------------------------------------------------------------------
Ingress LsrId   Destination     LSPID In/OutLabel     R Tunnel-name
-------------------------------------------------------------------------------
1.1.1.1         2.2.2.2         1     -/864256        I Tunnel1
1.1.1.1         2.2.2.2         2     -/864256        I Tunnel2
1.1.1.1         2.2.2.2         3     -/864256        I Tunnel3 -------------------------------------------------------------------------------
R: Role, I: Ingress, T: Transit, E: Egress
    Run the display ip routing-table command on PE1. You can view that the ECMP outbound interfaces are Tunnel1, Tunnel2, and Tunnel3.
    [~PE1] display ip routing-table 5.5.5.0
Proto: Protocol        Pre: Preference
Route Flags: R - relay, D - download to fib, T - to vpn-instance, B - black hole route
------------------------------------------------------------------------------
Routing Table : _public_
Summary Count : 1

Destination/Mask    Proto   Pre  Cost        Flags NextHop         Interface

      5.5.5.0/24    Static  60   0             D   1.1.1.1         Tunnel1  
                    Static  60   0             D   1.1.1.1         Tunnel2  
                    Static  60   0             D   1.1.1.1         Tunnel3

Configuration Files

  • PE1 configuration file

    #
sysname PE1
#
mpls lsr-id 1.1.1.1
#
mpls
 mpls te
#                                                                               
acl number 3002                                                                 
 rule 5 permit ip destination 5.5.5.1 32     
#                                                                               
acl number 3003                                                                 
 rule 5 permit ip destination 5.5.5.2 32    
#
traffic classifier c1 type or
 if-match acl 3002
#
traffic classifier c2 type or
 if-match acl 3003
#
traffic behavior b1
 remark local-precedence af4  
#
traffic behavior b2
 remark local-precedence cs7  
#
traffic policy p1
 classifier c1 behavior b1 precedence 5
 classifier c2 behavior b2 precedence 10
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.1111.1111.1111.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/1
 undo portswitch
 ip address 192.168.1.2 255.255.255.0
 traffic-policy p1 inbound 
#
interface 10GE1/0/2
 undo portswitch
 ip address 20.1.1.1 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/3
 undo portswitch
 ip address 20.1.2.1 255.255.255.0
 isis enable 1
#
interface LoopBack0
 ip address 1.1.1.1 255.255.255.255
 isis enable 1
#
interface Tunnel1
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 2.2.2.2
 mpls te signal-protocol segment-routing
 mpls te bandwidth ct0 10000
 statistic enable
 mpls te tunnel-id 1
 mpls te pce delegate
 mpls te service-class af4 cs7  
#
interface Tunnel2
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 2.2.2.2
 mpls te signal-protocol segment-routing
 mpls te bandwidth ct0 20000
 statistic enable
 mpls te tunnel-id 2
 mpls te pce delegate
 mpls te service-class af4 cs7  
#
interface Tunnel3
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 2.2.2.2
 mpls te signal-protocol segment-routing
 mpls te bandwidth ct0 50000
 statistic enable
 mpls te tunnel-id 3
 mpls te pce delegate
 mpls te service-class default
#
ip route-static 5.5.5.0 255.255.255.0 Tunnel1
ip route-static 5.5.5.0 255.255.255.0 Tunnel2
ip route-static 5.5.5.0 255.255.255.0 Tunnel3
#
return

  • PE2 configuration file

    #
sysname PE2
#
mpls lsr-id 2.2.2.2
#
mpls
 mpls te
#
segment-routing
#
isis 1
 is-level level-2
 cost-style wide
 network-entity 11.1111.1111.2222.00
 traffic-eng level-2
 segment-routing mpls
#
interface 10GE1/0/1
 undo portswitch
 ip address 192.168.2.2 255.255.255.0
#
interface 10GE1/0/2
 undo portswitch
 ip address 20.1.1.2 255.255.255.0
 isis enable 1
 mpls
 mpls te
#
interface 10GE1/0/3
 undo portswitch
 ip address 20.1.3.1 255.255.255.0
 isis enable 1
#
interface LoopBack0
 ip address 2.2.2.2 255.255.255.255
 isis enable 1
#
ip route-static 5.5.5.0 255.255.255.0 192.168.2.1
#
return

  • CE1 configuration file

    #
sysname CE1
#
interface 10GE1/0/1
 undo portswitch
 ip address 192.168.1.1 255.255.255.0
#
return

  • CE2 configuration file

    #
sysname CE2
#
interface 10GE1/0/1
 undo portswitch
 ip address 192.168.2.1 255.255.255.0
#
return
Translation
简体中文
Download
Updated: 2021-04-01

Document ID: EDOC1100138150

Views: 88454

Downloads: 118

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :