Importing Traffic to an SR-MPLS TE Tunnel

Using static routes is the simplest method for importing traffic to an SR-MPLS TE tunnel.

Procedure

Static routes in an SR-MPLS TE tunnel are similar to common static routes. You only need to configure a static route with an SR-MPLS TE tunnel interface as the outbound interface. For detailed instructions, see Configuring IPv4 Static Routes in the CloudEngine 12800 and 12800E Series Switches Configuration Guide - IP Unicast Routing.

A tunnel policy can be configured to import VPN traffic and unlabeled routes of the public network to an SR-MPLS TE tunnel.

Procedure

• Configure a tunnel policy to import VPN traffic to an SR-MPLS TE tunnel.

  Typically, VPN traffic is forwarded through an LSP tunnel but not an SR-MPLS TE tunnel. To import VPN traffic to the SR-MPLS TE tunnel, you need to configure a tunnel policy.

  1. Create a tunnel policy.

     You can configure either of the following types of tunnel policies according to service requirements:

     • Tunnel type prioritizing policy: This specifies the sequence in which different types of tunnels are selected by the VPN. For example, you can specify the VPN to select the SR-MPLS TE tunnel first.
     • Tunnel binding policy: This binds an SR-MPLS TE tunnel to a specified VPN by binding a specified destination address to the SR-MPLS TE tunnel to provide QoS guarantee.
  2. Apply the tunnel policy.

  For detailed instructions, see Configuring and Applying a Tunnel Policy in "BGP MPLS IP VPN Configuration" of the CloudEngine 12800 and 12800E Series Switches Configuration Guide - VPN.

• Configure a tunnel policy to iterate unlabeled routes of the public network to an SR-MPLS TE tunnel.

  By default, unlabeled routes of the public network can only be iterated to the outbound interface and the next hop, but not a tunnel.

  1. Run system-view

     The system view is displayed.

  2. Run tunnel-policy policy-name

     A tunnel policy is created, and tunnel policy view is displayed.

  3. (Optional) Run description description-information

     The description of the tunnel policy is configured.

  4. Run tunnel select-seq cr-lsp load-balance-number load-balance-number

     The sequence in which each type of tunnel is selected and the number of tunnels participating in load balancing are set.

  5. Run quit

     Return to the system view.

  6. Run route recursive-lookup tunnel [ ip-prefix ip-prefix-name ] [ tunnel-policy policy-name ]

     The unlabeled route of the public network is allowed to be iterated to the LSP to forward through MPLS.

     By default, the unlabeled route of the public network can be iterated only to the outbound interface and the next hop but not the LSP tunnel.

     If ip-prefix ip-prefix-name is not set, all static routes and unlabeled BGP routes will be preferentially iterated to LSP tunnels.

  7. Run commit

     The configuration is committed.

  After unlabeled routes of the public network are iterated to an SR-MPLS TE tunnel, you can run the display bgp routing-table network command to view route iteration information.

After you configure auto routes, SR-MPLS TE tunnels act as logical links to participate in IGP route calculation and tunnel interfaces are used as the outbound interfaces of packets. Devices on a network determine whether to advertise LSP information to neighboring nodes to instruct packet forwarding. You can configure automatic routes following Configuring IGP shortcut. The SR-MPLS TE tunnel is not advertised to neighbor nodes in this mode. Therefore, the SR-MPLS TE tunnel participates only in local route calculation and other nodes cannot use this tunnel.