Table of Contents

Related Documents

02-MPLS TE Configuration

Title	Size	Download
02-MPLS TE Configuration	651.12 KB

Contents

Configuring MPLS TE·········································································································································································· 1

MPLS TE overview······································································································································································ 1

Traffic engineering and MPLS TE································································································································· 1

Basic concepts··································································································································································· 2

MPLS TE implementation················································································································································· 2

CR-LSP·················································································································································································· 3

RSVP-TE················································································································································································ 4

Traffic forwarding····························································································································································· 8

CR-LSP backup·································································································································································· 9

FRR························································································································································································ 9

PS for an MPLS TE tunnel············································································································································· 11

DiffServ-aware TE·························································································································································· 11

Protocols and standards··············································································································································· 14

MPLS TE configuration task list············································································································································· 14

Configuring MPLS TE basic settings··································································································································· 14

Configuration prerequisites········································································································································· 14

Configuration procedure·············································································································································· 15

Configuring DiffServ-aware TE············································································································································ 15

Creating MPLS TE tunnel over static CR-LSP····················································································································· 16

Configuring MPLS TE tunnel with dynamic signaling protocol··················································································· 17

Configuring RSVP-TE advanced features·························································································································· 23

Tuning CR-LSP setup······························································································································································· 27

Tuning MPLS TE tunnel setup··············································································································································· 29

Configuration procedures············································································································································ 30

Configuring traffic forwarding············································································································································· 31

Configuring traffic forwarding tuning parameters········································································································· 33

Configuring CR-LSP backup················································································································································· 35

Configuring FRR······································································································································································· 36

Inspecting an MPLS TE tunnel·············································································································································· 39

Configuring MPLS LSP ping········································································································································ 39

Configuring MPLS LSP tracert····································································································································· 39

Configuring BFD for an MPLS TE tunnel·················································································································· 39

Configuring periodic LSP tracert································································································································ 41

Configuring protection switching········································································································································· 42

Displaying and maintaining MPLS TE······················································································································ 42

MPLS TE configuration examples········································································································································ 45

MPLS TE using static CR-LSP configuration example···························································································· 46

MPLS TE using RSVP-TE configuration example···································································································· 50

Configuration example of inter-AS MPLS TE tunnel using RSVP-TE·································································· 56

RSVP-TE GR configuration example·························································································································· 62

MPLS RSVP-TE and BFD cooperation configuration example············································································ 65

CR-LSP backup configuration example···················································································································· 67

FRR configuration example········································································································································· 70

MPLS TE in MPLS L3VPN configuration example································································································· 79

Troubleshooting MPLS TE······················································································································································ 87

No TE LSA generated··················································································································································· 87

Swicthback fails to occur when the main tunnel resumes··················································································· 87

Configuring MPLS TE

MPLS TE overview

Traffic engineering and MPLS TE

Network congestion is one of the major problems that can degrade your network backbone performance. It may occur either when network resources are inadequate or when load distribution is unbalanced. Traffic engineering (TE) is intended to avoid the latter situation where partial congestion may occur as the result of inefficient resource allocation.

TE can make best utilization of network resources and avoid non-even load distribution by real-time monitoring traffic and traffic load on each network elements to dynamically tune traffic management attributes, routing parameters and resources constraints.

The performance objectives for TE can be classified as either traffic-oriented or resource-oriented.

· Traffic–oriented performance objectives enhance Quality of Service (QoS) of traffic streams, such as minimization of packet loss, minimization of delay, maximization of throughput and enforcement of service level agreement (SLA).

· Resource–oriented performance objectives optimize resources utilization. Bandwidth is a crucial resource on networks. Efficiently managing it is one major task of TE.

To implement TE, you can use interior gateway protocols (IGPs) or Multiprotocol Label Switching (MPLS).

Because IGPs are topology-driven and consider only network connectivity, they fail to present some dynamic factors such as bandwidth and traffic characteristics.

This IGP disadvantage can be repaired by using an overlay model, such as IP over ATM or IP over FR. An overlay model provides a virtual topology above the physical network topology for a more scalable network design. It also provides better traffic and resources control support for implementing a variety of traffic engineering policies.

Despite all the benefits, overlay models are not suitable for implementing traffic engineering in large-sized backbones because of their inadequacy in extensibility. In this sense, MPLS TE is a better traffic engineering solution for its extensibility and ease of implementation.

MPLS is better than IGPs in implementing traffic engineering for the following reasons:

· MPLS supports explicit LSP routing.

· LSP routing is easy to manage and maintain compared with traditional packet-by-packet IP forwarding.

· MPLS TE uses less system resources compared with other traffic engineering implementations.

MPLS TE combines the MPLS technology and traffic engineering. It delivers the following benefits:

· Reserve resources by establishing LSP tunnels to specific destinations, which allows traffic to bypass congested nodes to achieve appropriate load distribution.

· When network resources are insufficient, MPLS TE allows bandwidth-hungry LSPs or critical user traffic to occupy the bandwidth for lower priority LSP tunnels.

· In case an LSP tunnel fails or congestion occurs on a network node, MPLS TE can provide route backup and Fast Reroute (FRR).

With MPLS TE, a network administrator can eliminate network congestion by creating some LSPs and congestion bypass nodes. Special offline tools are also available for the traffic analysis performed when the number of LSPs is large.

Basic concepts

LSP tunnel

On an LSP, after packets are labeled at the ingress node, the packets are forwarded based on label. The traffic is transparent to the transits nodes on the LSP. In this sense, an LSP can be regarded as a tunnel.

MPLS TE tunnel

Rerouting and transmission over multiple paths may involve multiple LSP tunnels. A set of such LSP tunnels is called a traffic engineered tunnel (TE tunnel).

MPLS TE implementation

MPLS TE mainly accomplishes the following functions:

· Static Constraint-based Routed LSP (CR-LSP) processing to create and remove static CR-LSPs. The bandwidth of a static CR-LSP must be configured manually.

· Dynamic CR-LSP processing to handle three types of CR-LSPs: basic CR-LSPs, backup CR-LSPs and fast rerouted CR-LSPs.

Static CR-LSP processing is simple, while dynamic CR-LSP processing involves four phrases: advertising TE attributes, calculating paths, establishing paths, and forwarding packets.

Advertising TE attributes

MPLS TE must be aware of dynamic TE attributes of each link on the network. This is achieved by extending link state-based IGPs such as OSPF and IS-IS.

OSPF and IS-IS extensions add to link states such TE attributes as link bandwidth, color, among which maximum reservable link bandwidth and non-reserved bandwidth with a particular priority are most important.

Each node collects the TE attributes of all links on all routers within the local area or at the same level to build up a TE database (TEDB).

Calculating paths

Link state-based routing protocols use Shortest Path First (SPF) to calculate the shortest path to each network node.

In MPLS TE, the Constraint-based Shortest Path First (CSPF) algorithm is used to calculate the shortest, TE compliant path to a node. It is derived from SPF and makes calculation based on the following conditions:

· Constraints on the LSP to be set up with respect to bandwidth, color, setup/holding priority, explicit path and other constraints. They are configured at the LSP ingress.

· TEDB

CSPF first prunes TE attribute incompliant links from the TEDB and then performs SPF calculation to identify the shortest path to an LSP egress.

Establishing paths

RSVP-TE is the signaling for setting up LSP tunnels. RSVP-TE can carry constraints such as LSP bandwidth, some explicit route information, and color.

RSVP-TE uses raw IP to establish LSPs. It is a well-established technology in terms of its architecture, protocol procedures and support to services.

Forwarding packets

Packets are forwarded over established tunnels.

CR-LSP

Unlike ordinary LSPs established based on routing information, CR-LSPs are established based on criteria such as bandwidth, selected path, and QoS parameters in addition to routing information.

The mechanism setting up and managing constraints is called Constraint-based Routing (CR).

CR-LSP involves the following concepts:

· Strict and loose explicit routes

· Traffic characteristics

· Preemption

· Route pinning

· Administrative group and affinity attribute

· Reoptimization

Strict and loose explicit routes

An LSP is called a strict explicit route if all LSRs along the LSP are specified.

An LSP is called a loose explicit route if the downstream LSR selection conditions rather than LSRs are defined.

Traffic characteristics

Traffic is described in terms of peak rate, committed rate, and service granularity.

The peak and committed rates describe the bandwidth constraints of a path while the service granularity specifies a constraint on the delay variation that the CR-LDP MPLS domain may introduce to a path's traffic.

Preemption

During establishment of a CR-LSP, if a path with sufficient resources cannot be found, the CR-LSP can be established by preempting the resources of a lower-priority CR-LSP. This is called path preemption.

Two priorities, setup priority and holding priority, are assigned to CR-LSPs for making preemption decision. Both setup and holding priorities range from 0 to 7, with a lower numerical number indicating a higher priority.

For a new path to preempt an existing path, the setup priority of the new path must be greater than the holding priority of the existing path. To initiate a preemption, the Resv message of RSVP-TE is sent.

To avoid flapping caused by improper preemptions between CR-LSPs, the setup priority of a CR-LSP must not be set higher than its holding priority.

Route pinning

Route pinning prevents an established CR-LSP from changing upon route changes.

If a network does not run IGP TE extension, the network administrator is unable to identify from which part of the network the required bandwidth will be obtained when setting up a CR-LSP. In this case, loose explicit route (ER-hop) with required resources is used. The established CR-LSP, however, may change when the route changes, for example, when a better next hop becomes available. If this is undesirable, the network administrator can set up the CR-LSP using route underpinning to make it a permanent path.

Administrative group and affinity attribute

Reoptimization

Traffic engineering is a process of allocating/reallocating network resources. You may configure it to meet desired QoS.

Normally, service providers use some mechanism to optimize CR-LSPs for best use of network resources. They can do this manually but CR-LSP measurement and tuning are required. Alternatively, they can use MPLS TE where CR-LSPs are dynamically optimized.

Dynamic CR-LSP optimization involves periodic calculation of paths that traffic trunks will traverse. If a better route is found for an existing CR-LSP, a new CR-LSP is established to replace the old one, and services are switched to the new CR-LSP.

RSVP-TE

Overview

Two QoS models are available: Integrated Service (IntServ) and Differentiated Service (DiffServ).

Resource Reservation Protocol (RSVP) is designed for IntServ. It reserves resources on each node along a path. RSVP operates at the transport layer but does not participate in data transmission. It is an Internet control protocol similar to ICMP.

The following are features of RSVP:

· Unidirectional

· Receiver oriented. The receiver initiates resource reservation requests and is responsible for maintaining the reservation information.

· Using soft state mechanism to maintain resource reservation information.

Extended RSVP can support MPLS label distribution and allow resource reservation information to be transmitted with label bindings. This extended RSVP is called RSVP-TE, which is operating as a signaling protocol for LSP tunnel setup in MPLS TE.

Basic concepts of RSVP-TE

· Soft state

Soft state is a mechanism used in RSVP-TE to periodically refresh the resource reservation state on a node. The resource reservation state includes the path state and the reservation state. The path state is generated and refreshed by the Path message, and the reservation state is generated and refreshed by the Resv message. A state is to be removed if no refresh messages are received for it in certain interval.

· Resource reservation style

Each LSP set up using RSVP-TE is assigned a resource reservation style. During an RSVP session, the receiver decides which reservation style can be used for this session and which LSPs can be used.

The following reservation styles are available:

¡ Fixed-filter style (FF) where resources are reserved for individual senders and cannot be shared among senders on the same session.

¡ Shared-explicit style (SE) where resources are reserved for senders on the same session and shared among them.

NOTE:

SE is only used for make-before-break because multiple LSPs cannot be present on the same session.

Make-before-break

Make-before-break is a mechanism to change MPLS TE tunnel attributes with minimum data loss and without extra bandwidth.

Figure 1 Diagram for make-before-break

Figure 1 presents a scenario where a path Router A → Router B → Router C → Router D is established with 30 Mbps reserved bandwidth between Router A and Router D. The remaining bandwidth is then 30 Mbps.

If 40 Mbps path bandwidth is requested, the remaining bandwidth of the Router A → Router B → Router C → Router D path is inadequate. The problem cannot be addressed by selecting another path, Router A → Router E → Router C → Router D, because the bandwidth of the Router C → Router D link is inadequate.

To address the problem, you may use the make-before-break mechanism. It allows the new path to share the bandwidth of the original path at the Router C → Router D link. Upon creation of the new path, traffic is switched to the new path and the previous path is torn down. This helps avoid traffic interruption effectively.

RSVP-TE messages

RSVP-TE uses RSVP messages with extensions. The following are RSVP messages:

· Path messages—Transmitted along the path of data transmission downstream by each RSVP sender to save path state information on each node along the path.

·Resv messages: sent by each receiver upstream towards senders to request resource reservation and to create and maintain reservation state on each node along the reverse of data transmission path.

· PathTear messages—Sent downstream immediately once created to remove the path state and related reservation state on each node along the path.

· ResvTear messages—Sent upstream immediately once created to remove the reservation state on each node along the path.

· PathErr messages—Sent upstream to report Path message processing errors to senders. They do not affect the state of the nodes along the path.

· ResvErr messages—Sent downstream to notify the downstream nodes that error occurs during Resv message processing or reservation error occurs as the result of preemption.

· ResvConf messages—Sent to receivers to confirm Resv messages.

· Hello messages—Sent between any two directly connected RSVP neighbors to set up and maintain the neighbor relationship that has local significance on the link.

The TE extension to RSVP adds new objects to the Path message and the Resv message. These objects carry not only label bindings but also routing constraints, supporting CR-LSP and FRR.

· New objects added to the Path message include LABEL_REQUEST, EXPLICIT_ROUTE, RECORD_ROUTE, and SESSION_ATTRIBUTE.

· New objects added to the Resv message include LABEL and RECORD_ROUTE

The LABEL_REQUEST object in the Path message requests the label bindings for an LSP. It is also saved in the path state block. The node receiving LABEL_REQUEST advertises the label binding using the LABEL object in the Resv message to the upstream node, accomplishing label advertisement and transmission.

Setting up an LSP tunnel

Figure 2 shows how to set up a LSP tunnel with RSVP:

Figure 2 Setting up an LSP tunnel

The following is a simplified procedure for setting up an LSP tunnel with RSVP:

1. The ingress LSR sends a Path message that carries the label request information, and then forwards the message along the path calculated by CSPF hop-by-hop towards the egress LSR.

2. After receiving the Path message, the egress generates a Resv message carrying the reservation information and label and then forwards the message towards the ingress along the reverse direction of the path along which the Path message travels. The LSRs that the Resv message traverses along the path reserve resources as required.

3. When the ingress LSR receives the Resv message, LSP is established.

As resources are reserved on the LSRs along the path for the LSP established using RSVP-TE, services transmitted on the LSP are guaranteed.

RSVP refresh mechanism

RSVP maintains path and reservation state by periodically retransmitting two types of messages: Path and Resv. These periodically retransmitted Path and Resv messages are called refresh messages. They are sent along the path that the last Path or Resv message travels to synchronize the state between RSVP neighbors and recover lost RSVP messages.

When many RSVP sessions are present, periodically sent refresh messages become a network burden. In addition, for some delay sensitive applications, the refreshing delay they must wait for recovering lost RSVP messages may be unbearable. As tuning refresh intervals is not adequate to address the two problems, the refreshing mechanism was extended in RFC 2961 RSVP Refresh Overhead Reduction Extensions to address the problems:

· Message_ID extension

RSVP itself uses Raw IP to send messages. The Message_ID extension mechanism defined in RFC 2961 adds objects that can be carried in RSVP messages. Of them, the Message_ID object and the Message_ID_ACK object are used to acknowledge RSVP messages, improving transmission reliability.

On an interface enabled with the Message_ID mechanism, you may configure RSVP message retransmission. If a node sends a message carrying the Message_ID object, and the ACK_Desired flag in the object is set, the node expects a response that carries the Message_ID_ACK object during the initial retransmission interval (Rf). If the node does not receive the response within the Rf interval, it resends the message and sets the retransmission interval to (1+Delta) × Rf. The node repeats such retransmissions until it receives the corresponding response within the retransmission time or the number of retransmission attempts reaches the limit.

· Summary refresh extension

Send summary refreshes (Srefreshes) rather than retransmit standard Path or Resv messages to refresh related RSVP state. This reduces refresh traffic and allows nodes to make faster processing.

To use summary refresh, you must use the Message_ID extension. Only states advertised using MESSAGE_ID included Path and Resv messages can be refreshed using summary refreshes.

PSB, RSB and BSB timeouts

To create an LSP tunnel, the sender sends a Path message with a LABEL_REQUEST object. After receiving this Path message, the receiver assigns a label for the path and puts the label binding in the LABEL object in the returned Resv message.

The LABEL_REQUEST object is stored in the path state block (PSB) on the upstream nodes, while the LABEL object is stored in the reservation state block (RSB) on the downstream nodes. The state stored in the PSB or RSB object times out and is removed after the number of consecutive non-refreshing times exceeds the PSB or RSB timeout keep-multiplier.

Sometimes, although a reservation request does not pass admission control on some node, you may want to store the resource reservation state for it while allowing other requests to use the resources reserved for the request. In this case, the node transits to the blockade state and a blockade state block (BSB) is created on each downstream node. When the number of non-refreshing times exceeds the blockade multiplier, the blockade state is removed.

RSVP-TE GR

RSVP-TE Graceful Restart (GR) preserves the soft state and label forwarding information when the signaling protocol or control plane fails, so that LSRs can still forward packets according to forwarding entries, ensuring continuous data transmission.

A device that participates in an RSVP-TE GR process plays either of the following two roles:

· GR restarter, the router that gracefully restarts due to a manually configured command or a fault. It must be GR-capable.

· GR helper, neighbor of the GR restarter. A GR helper maintains the neighbor relationship with the GR restarter and helps the GR restarter restore its LFIB information. A GR helper must be GR-capable.

The RSVP-TE GR function depends on the extended hello capability of RSVP-TE. A GR-capable device advertises its GR capability and relevant time parameters to its neighbors by extended RSVP hello packets. If a device and all its neighbors have the RSVP GR capability and have exchanged GR parameters, each of them can function as the GR helper of another device, allowing data to be forwarded without interruption when the GR restarter is rebooting.

A GR helper considers that a GR restarter is rebooting when it receives no Hello packets from the restarter in a specific period of time. When a GR restarter is rebooting, the GR helpers retain soft state information about the GR restarter and keep sending Hello packets periodically to the GR restarter until the restart timer expires.

If a GR helper and the GR restarter reestablish a Hello session before the restart timer expires, the recovery timer is started and signaling packet exchanging is triggered to restore the original soft state. Otherwise, all RSVP soft state information and forwarding entries relevant to the neighbor are removed. If the recovery timer expires, soft state information and forwarding entries that are not restored during the GR restarting process are removed.

NOTE:

· If configured with RSVP-TE GR, the switch can act as both a GR restarter and a GR helper at the same time.

· Without a backup main control board, the switch can act as only a GR helper when it is configured with RSVP-TE GR.

Traffic forwarding

For traffic to travel along an LSP tunnel, you need to make configuration after creating the MPLS TE tunnel. Otherwise, traffic is IP routed.

Even when an MPLS TE tunnel is available, traffic is IP routed if you do not configure it to travel the tunnel. For traffic to be routed along an MPLS TE tunnel, you can use static routing, policy routing, or automatic route advertisement.

Static routing

Static routing is the easiest way to route traffic along an MPLS TE tunnel. You only need to manually create a route that reaches the destination through the tunnel interface.

NOTE:

For more information about static routing, see Layer 3—IP Routing Configuration Guide.

Automatic route advertisement

You can use automatic route advertisement to advertise MPLS TE tunnel interface routes to IGPs, allowing traffic to be routed down MPLS TE tunnels.

Two approaches are available to automatic route advertisement: IGP shortcut and forwarding adjacency.

OSPF and IS-IS support both approaches where TE tunnels are considered point-to-point links and TE tunnel interfaces can be set as outgoing interfaces.

IGP shortcut, also known as autoroute announce, considers a TE tunnel as a logical interface directly connected to the destination when computing IGP routes on the ingress of the TE tunnel.

IGP shortcut and forwarding adjacency are different in that in the forwarding adjacency approach, routes with TE tunnel interfaces as outgoing interfaces are advertised to neighboring devices but not in the IGP shortcut approach. Therefore, TE tunnels are visible to other devices in the forwarding adjacency approach but not in the IGP shortcut approach.

Figure 3 IGP shortcut and forwarding adjacency

As shown in Figure 3, a TE tunnel is present between Router D and Router C. With IGP shortcut enabled, the ingress node Router D can use this tunnel when calculating IGP routes. This tunnel, however, is invisible to Router A; therefore, Router A cannot use this tunnel to reach Router C. With forwarding adjacency enabled, Router A can know the presence of the TE tunnel and forward traffic to Router C to Router D though this tunnel.

The configuration of IGP shortcut and forwarding adjacency is broken down into tunnel configuration and IGP configuration. When making tunnel configuration on a TE tunnel interface, take the following issues into consideration:

· The tunnel destination address must be in the same area where the tunnel interface is located.

· The tunnel destination address must be reachable through intra-area routing.

CR-LSP backup

CR-LSP backup provides end-to-end path protection for the entire LSP without time limitation. This is different from Fast Reroute (FRR) which provides quick but temporary per-link or per-node protection on an LSP.

In the same TE tunnel, the LSP used to back up a primary LSP is called a secondary LSP. When the ingress of a TE tunnel detects that the primary LSP is unavailable, it switches traffic to the secondary LSP and after the primary LSP becomes available, switches traffic back. This is how LSP path protection is achieved.

The following approaches are available for CR-LSP backup:

· Hot backup where a secondary CR-LSP is created immediately after a primary CR-LSP is created. MPLS TE switches traffic to the secondary CR-LSP after the primary CR-LSP fails.

· Standard backup where a secondary CR-LSP is created to take over after the primary CR-LSP fails.

FRR

Overview

Fast Reroute (FRR) provides a quick per-link or per-node protection on an LSP.

In this approach, once a link or node fails on a path, FRR comes up to reroute the path to a new link or node to bypass the failed link or node. This can happen as fast as 50 milliseconds, thereby minimizing data loss.

Once a link or node on an LSP configured with FRR fails, traffic is switched to the protection link and the ingress node of the LSP starts attempting to set up a new LSP.

Basic concepts

The following are concepts that FRR involves throughout this document:

· Primary LSP—The protected LSP.

· Bypass LSP—An LSP used to protect the primary LSP.

· Point of local repair (PLR)—The ingress of the bypass LSP. It must be located on the primary LSP but must not be the egress.

· Merge point (MP)—The egress of the bypass LSP. It must be located on the primary LSP but must not be the ingress.

Protection

FRR provides link protection and node protection for an LSP.

· Link protection, where the PLR and the MP are connected through a direct link and the primary LSP traverses this link. When the link fails, traffic is switched to the bypass LSP. As shown in Figure 4, the primary LSP is Router A → Router B → Router C → Router D, and the bypass LSP is Router B → Router F → Router C.

Figure 4 FRR link protection

· Node protection, where the PLR and the MP are connected through a device and the primary LSP traverses this device. When the device fails, traffic is switched to the bypass LSP. As shown in Figure 5, the primary LSP is Router A → Router B → Router C → Router D → Router E, and the bypass LSP is Router B → Router F→ Router D. Router C is the protected device.

Figure 5 FRR node protection

Deploying FRR

When configuring the bypass LSP, make sure the protected link or node is not on the bypass LSP.

As bypass LSPs are pre-established, FRR requires extra bandwidth. When network bandwidth is insufficient, use FRR for crucial interfaces or links only.

PS for an MPLS TE tunnel

Protection switching (PS) refers to establishing one or more protection tunnels (backup tunnels) for a main tunnel. A main tunnel and its protection tunnels form a protection group. When the main tunnel fails, data is switched to a protection tunnel immediately, greatly improving the reliability of the network. When the main tunnel recovers, data can be switched back to the main tunnel.

The switch supports only 1:1 protection switching, where one protection tunnel is used to service one main tunnel. Two tunnels exist between the ingress and egress, one main and one backup. Normally, user data travels along the main tunnel. If the ingress finds a defect of the main tunnel by using a probing mechanism, it will switch data to the protection tunnel.

Protection switching may be command triggered or signal triggered.

Command switching refers to a PS triggered by an externally configured switching command, which can define the following switching actions (in the descending order of priority):

· clear—Clears all configured switching actions.

· lock (lockout of protection)—Always uses the main LSP to transfer data.

· force (forced switch)—Forces data to travel on the backup LSP.

· manual (manual switch)—Switches data from the main LSP to the backup LSP.

Signal switching (Signal Fail) refers to a PS automatically triggered by a signal fail declaration. Examples include a PS that occurs during BFD detection for MPLS-TE tunnels.

The following shows the priority of the externally configured switching actions and the signal fail switching, in the descending order:

· Clear

· Lockout of protection

· Signal fail of the backup LSP

· Forced switch

· Signal fail of the main LSP

· Signal clear

· Manual switch

DiffServ-aware TE

Overview

Diff-Serv is a model that provides differentiated QoS guarantees based on class of service.

MPLS TE is a traffic engineering solution that focuses on optimizing network resources allocation.

DiffServ-aware TE (DS-TE) combines them to optimize network resources allocation at a per-service class level. For traffic trunks which are distinguished by class of service, this means varied bandwidth constraints. Essentially, what DS-TE does is to map traffic trunks with LSPs, making each traffic trunk traverse the constraints-compliant path.

The switch supports two DS-TE modes:

· Prestandard mode—Implemented by using H3C proprietary mechanisms

· IETF mode—Implemented according to RFC 4124, RFC 4125, and RFC 4127.

Basic concepts

· Class Type (CT)—A set of traffic trunks crossing a link that is governed by a specific set of bandwidth constraints. DS-TE allocates link bandwidth, implements constraint-based routing, and performs admission control for a traffic trunk according to the traffic trunk’s CT. A given traffic trunk belongs to the same CT on all links.

· Bandwidth Constraint (BC)—Restricts the bandwidth for one or more class types.

· Bandwidth constraints model—Algorithm for implementing bandwidth constraints on different CTs. A BC model comprises two factors, the maximum number of Bandwidth Constraints (MaxBC) and the mappings between BCs and CTs. DS-TE supports two BC models, Russian Dolls Model (RDM) and Maximum Allocation Model (MAM).

· TE class—A pair consisting of a CT and a preemption priority for the CT. The setup priority or holding priority of an LSP transporting a traffic trunk from that CT must be the preemption priority for the CT.

NOTE:

· The prestandard mode supports two CTs (CT 0 and CT 1), eight priorities, and up to 16 TE classes. The IETF mode supports four CTs (CT 0 through CT 3), eight priorities, and up to eight TE classes.

· The prestandard mode supports only RDM, while the IETF mode supports both RDM and MAM.

· The prestandard mode is proprietary, and therefore a device working in prestandard mode cannot communicate with devices of some other vendors. The IETF mode is a standard mode implemented according to relative RFCs. A device working in IETF mode can communicate with devices of other vendors.

Working process

To establish MPLS TE tunnels according to CTs of traffic trunks, a device needs to:

1. Determine the CT of traffic flows.

A device classifies traffic flows according to your configuration.

¡ When configuring a dynamic MPLS TE tunnel, you can use the mpls te bandwidth command on the tunnel interface to specify a CT for the traffic flows to be forwarded by the tunnel.

¡ When configuring a static MPLS TE tunnel, you can use the bandwidth keyword to specify a CT for the traffic flows to be forwarded along the tunnel.

2. Check whether bandwidth is enough for the CT.

You can use the mpls te max-reservable-bandwidth command on an MPLS TE tunnel interface to configure the bandwidth constraints of the tunnel interface. The switch determines whether bandwidth is enough to establish an MPLS TE tunnel for a traffic trunk according to the traffic trunk’s CT and the tunnel interface’s BCs.

The relation between BCs and CTs varies in different BC models:

In RDM model, a BC constrains the total bandwidth of multiple CTs, as shown in Figure 6:

¡ BC 2 is for CT 2. The total bandwidth of the traffic of CT 2 cannot exceed BC 2.

¡ BC 1 is for CT 2 and CT 1. The total bandwidth of the traffic of CT 2 and CT 1 cannot exceed BC 1.

¡ BC 0 is for CT 2, CT 1, and CT 0. The total bandwidth of the traffic of CT 2, CT 1, and CT 0 cannot exceed BC 0. In this model, BC 0 equals the maximum reservable bandwidth of the tunnel.

In cooperation with priority preemption, the RDM model can also implement the isolation across CTs, ensuring each CT its share of bandwidth. RDM is suitable for networks where traffic is unstable and traffic bursts may occur.

Figure 6 RDM bandwidth constraints model

In MAM model, a BC constrains the bandwidth of only one CT on an interface. This ensures isolation across CTs no matter whether preemption is used or not. Compared with RDM, MAM is easy to understand and configure. MAM is suitable for networks where traffic of each CT is stable. Figure 7 shows an example:

¡ BC 0 is for CT 0. The bandwidth occupied by the traffic of CT 0 cannot exceed BC 0.

¡ BC 1 is for CT 1. The bandwidth occupied by the traffic of CT 1 cannot exceed BC 1.

¡ BC 2 is for CT 2. The bandwidth occupied by the traffic of CT 2 cannot exceed BC 2.

¡ The total bandwidth occupied by CT 0, CT 1, and CT 2 cannot exceed the maximum reservable bandwidth.

Figure 7 MAM bandwidth constraints model

3. Check whether the traffic trunk matches an existing TE class.

The switch checks whether the CT and the LSP setup/holding priority of the traffic trunk matches an existing TE class. An MPLS TE tunnel can be established for the traffic trunk only when the following conditions are satisfied:

¡ Every node along the tunnel has a TE class that matches the traffic trunk’s CT and the LSP setup priority.

¡ Every node along the tunnel has a TE class that matches the traffic trunk’s CT and the LSP holding priority.

NOTE:

The prestandard mode does not allow you to configure TE classes, while the IETF mode allows for TE class configuration.

Protocols and standards

· RFC 2702, Requirements for Traffic Engineering Over MPLS

· RFC 3212, Constraint-Based LSP Setup using LDP

· RFC 2205, Resource ReSerVation Protocol

· RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels

· RFC 2961, RSVP Refresh Overhead Reduction Extensions

· RFC 3564, Requirements for Support of Differentiated Service-aware MPLS Traffic Engineering

· ITU-T Recommendation Y.1720, Protection switching for MPLS networks

MPLS TE configuration task list

Complete the following tasks to configure MPLS TE:

Task			Remarks
Configuring MPLS TE basic settings.			Required
Configuring DiffServ-aware TE.			Optional
Configuring an MPLS TE tunnel..	Creating MPLS TE tunnel over static CR-LSP		Required Use either approach
Configuring an MPLS TE tunnel..	Configuring MPLS TE tunnel with dynamic signaling protocol		Required Use either approach
Configuring RSVP-TE advanced features.			Optional
Tuning CR-LSP setup.			Optional
Tuning MPLS TE tunnel setup.			Optional
Configuring traffic forwarding..		Forwarding traffic along MPLS TE tunnels using static routes	Required Use any approach
Configuring traffic forwarding..		Forwarding traffic along MPLS TE tunnels through automatic route advertisement	Required Use any approach
Configuring traffic forwarding tuning parameters.			Optional
Configuring CR-LSP backup.			Optional
Configuring FRR.			Optional
Inspecting an MPLS TE tunnel.			Optional
Configuring protection switching.			Optional

Configuring MPLS TE basic settings

This configuration task includes the basic settings required for all MPLS TE features.

Configuration prerequisites

Before you configure MPLS TE basic settings, complete the following tasks:

· Configure static routing or IGPs to make sure all LSRs are reachable.

· Configure basic MPLS.

NOTE:

For configuration information about MPLS basic settings, see the chapter “Configuring basic MPLS.”

Configuration procedure

To configure MPLS TE basic settings:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable global MPLS TE.	mpls te	Disabled by default
4. Return to system view.	quit	N/A
5. Enter the interface view of an MPLS TE link.	interface interface-type interface-number	N/A
6. Enable interface MPLS TE.	mpls te	Disabled by default
7. Return to system view.	quit	N/A
8. Create a tunnel interface and enter its view.	interface tunnel tunnel-number	N/A
9. Assign an IP address to the tunnel interface.	ip address ip-address netmask	N/A
10. Set the tunnel protocol to MPLS TE.	tunnel-protocol mpls te	N/A
11. Configure the destination address of the tunnel.	destination ip-address	N/A
12. Configure the tunnel ID of the tunnel.	mpls te tunnel-id tunnel-id	N/A
13. Submit the current tunnel configuration.	mpls te commit	N/A

NOTE:

For information about tunnel interfaces, see Layer 3—IP Services Configuration Guide.

Configuring DiffServ-aware TE

To configure DS-TE:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure the system working mode.	system working mode { { advance \| bridgee \| routee } hybrid }	To support the DiffServ-aware TE function, you must configure the system to work in advance hybrid, bridgee hybrid, or routee hybrid mode.
3. Enter MPLS view.	mpls	N/A
4. Configure the DS-TE mode as IETF.	mpls te ds-te mode ietf	Optional. By default, the DS-TE mode is prestandard.
5. Configure the BC model of IETF DS-TE as MAM.	mpls te ds-te ietf bc-mode mam	Optional. By default, the BC model of IETF DS-TE is RDM.
6. Configure the TE class mapping in IETF DS-TE mode, or, the TE class-CT-priority association.	mpls te ds-te ietf te-class te-class-index class-type class-type-number priority pri-number	Optional. By default, the TE class mappings in IETF mode are shown as Table 1.

NOTE:

Only base cards support DiffServ-aware TE.

Table 1 Default TE class mappings in IETF mode

TE Class	CT	Priority
0	0	7
1	1	7
2	2	7
3	3	7
4	0	0
5	1	0
6	2	0
7	3	0

Creating MPLS TE tunnel over static CR-LSP

Creating MPLS TE tunnels over static CR-LSPs does not involve configuration of tunnel constraints or the issue of IGP TE extension or CSPF. Create a static CR-LSP and a TE tunnel using static signaling and then associate them.

Despite its ease of configuration, the application of MPLS TE tunnels over static CR-LSPs is restricted because they cannot dynamically adapt to network changes.

Static CR-LSPs are special static LSPs. They share the same constraints and use the same label space.

Configuration prerequisites

Before you perform the configuration, complete the following tasks:

· Configure static routing or an IGP protocol to ensure all LSRs are reachable.

· Configure basic MPLS.

· Configure MPLS TE basic settings.

Configuration procedure

To create an MPLS TE tunnel over a CR-LSP:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter the interface view of an MPLS TE tunnel.	interface tunnel tunnel-number	N/A
3. Configure the tunnel to use static CR-LSP.	mpls te signal-protocol static	N/A
4. Submit the current tunnel configuration.	mpls te commit	N/A
5. Exit to system view.	quit	N/A
6. Create a static CR-LSP on the ingress node.	static-cr-lsp ingress tunnel-name destination dest-addr nexthop next-hop-addr out-label out-label-value [ bandwidth [ ct0 \| ct1 \| ct2 \| ct3 ] bandwidth-value ]	Use one of the commands according to the location of the switch in the network. The tunnel-name argument specifies the name of the MPLS TE tunnel interface that uses the static CR-LSP. For example, assume that you have created a tunnel interface by using the command interface tunnel 2. The tunnel interface name is Tunnel2.
7. Create a static CR-LSP on the transit node.	static-cr-lsp transit tunnel-name incoming-interface interface-type interface-number in-label in-label-value nexthop next-hop-addr out-label out-label-value [ bandwidth [ ct0 \| ct1 \| ct2 \| ct3 ] bandwidth-value ]
8. Create a static CR-LSP on the egress node.	static-cr-lsp egress tunnel-name incoming-interface interface-type interface-number in-label in-label-value [ bandwidth [ ct0 \| ct1 \| ct2 \| ct3 ] bandwidth-value ]

NOTE:

· The tunnel-name argument in the static-cr-lsp ingress command must be the same as the tunnel interface name, including the letter case. Assume you create a tunnel interface with the interface tunnel 2 command. The tunnel-name in the static-cr-lsp ingress command must be in the form of Tunnel2—not tunnel2 or TUNNEL2. Otherwise, the tunnel cannot be established on the ingress node. This restriction however does not apply to transit and egress nodes.

· Do not configure the next hop address as a local public address when configuring the static CR-LSP on the ingress or a transit node.

Configuring MPLS TE tunnel with dynamic signaling protocol

Dynamic signaling protocol can adapt the path of a TE tunnel to network changes and implement redundancy, FRR, and other advanced features.

The following describes how to create an MPLS TE tunnel with a dynamic signaling protocol:

· Configure MPLS TE properties for links and advertise them through IGP TE extension to form a TEDB.

· Configure tunnel constraints.

· Use the CSPF algorithm to calculate a preferred path based on the TEDB and tunnel constraints.

· Establish the path by using the signaling protocol RSVP-TE.

NOTE:

To form a TEDB, you must configure the IGP TE extension for the nodes on the network to send TE LSAs. If the IGP TE extension is not configured, the CR-LSP is created based on IGP routing rather than computed by CSPF.

Configuration prerequisites

Before you perform the configuration, complete the following tasks:

· Configure static routing or an IGP protocol to ensure all LSRs are reachable.

· Configure basic MPLS.

· Configure MPLS TE basic settings.

Configuration procedure

Complete the following tasks to configure an MPLS TE tunnel using a dynamic signaling protocol:

Task	Remarks
Configuring MPLS TE properties for a link.	Optional
Configuring CSPF.	Optional
Configuring OSPF TE.	Required when CSPF is configured. Choose one depending on the IGP protocol used.
Configuring IS-IS TE.
Configuring an MPLS TE explicit path.	Optional
Configuring MPLS TE tunnel constraints.	Optional
Establishing an MPLS TE tunnel with RSVP-TE.	Optional

Configuring MPLS TE properties for a link

To configure MPLS TE properties for a link:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
3. Configure maximum link bandwidth.	mpls te max-link-bandwidth bandwidth-value	Optional. 0 by default.
4. Configure BC 0 and BC 1 of the MPLS TE link in the RDM model of the prestandard DS-TE.	mpls te max-reservable-bandwidth bandwidth-value [ bc1 bc1-bandwidth ]	Optional. 0 for both BC 0 and BC 1 by default. In RDM model, BC 0 is the maximum reservable bandwidth of a link.
5. Configure maximum reservable bandwidth and BCs of the MPLS TE link in the MAM model of the IETF DS-TE.	mpls te max-reservable-bandwidth mam bandwidth-value { bc0 bc0-bandwidth \| bc1 bc1-bandwidth \| bc2 bc2-bandwidth \| bc3 bc3-bandwidth } *	Optional. By default, the maximum bandwidth, and BC 0 through BC 3 are all 0.
6. Configure the BCs of the MPLS TE link in the RDM model of the IETF DS-TE.	mpls te max-reservable-bandwidth rdm bandwidth-value [ bc1 bc1-bandwidth ] [ bc2 bc2-bandwidth ] [ bc3 bc3-bandwidth ]	Optional. 0 for BC 0 through BC 3 by default In RDM model, BC 0 is the maximum reservable bandwidth of a link.

NOTE:

Only base cards support configuring bandwidth reservation and maximum reservable bandwidth.

Configuring CSPF

With CSPF enabled, a node uses CSPF to calculate the shortest path that satisfies TE requirements.

To configure CSPF:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable CSPF on your device.	mpls te cspf	Disabled by default

Configuring OSPF TE

Configure OSPF TE if the routing protocol is OSPF and a dynamic signaling protocol is used for MPLS TE tunnel setup.

The OSPF TE extension uses Opaque Type 10 LSAs to carry TE attributes of links. Before configuring OSPF TE, you need to enable the opaque capability of OSPF. In addition, for TE LSAs to be generated, at least one neighbor must be in full state.

To configure OSPF TE:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter OSPF view.	ospf [ process-id ]	N/A
3. Enable the opaque LSA capability.	opaque-capability enable	Disabled by default
4. Enter OSPF area view.	area area-id	N/A
5. Enable MPLS TE in the OSPF area.	mpls-te enable	Disabled by default
6. Return to OSPF view.	quit	N/A

NOTE:

· For more information about OSPF opaque LSA, see Layer 3—IP routing Configuration Guide.

· MPLS TE cannot reserve resources and distribute labels on OSPF virtual links. MPLS TE cannot establish an LSP tunnel through an OSPF virtual link. Make sure no virtual links exist in the OSPF routing domain when configuring OSPF TE.

Configuring IS-IS TE

Configure IS-IS TE if the routing protocol is IS-IS and a dynamic signaling protocol is used for MPLS TE tunnel setup. In case both OSPF TE and IS-IS TE are available, OSPF TE takes priority.

The IS-IS TE extension uses the sub-TLV of IS reachability TLV (type 22) to carry TE attributes. Before configuring IS-IS TE, configure the IS-IS wide metric style, which can be wide, compatible, or wide-compatible.

NOTE:

· According to RFC 3784, the length of the IS reachability TLV (type 22) may reach the maximum of 255 bytes in some cases.

· For an IS-IS LSP to carry this type of TLV and to be flooded normally on all interfaces with IS-IS enabled, the MTU of any IS-IS enabled interface, including 27 bytes of LSP header and two bytes of TLV header, cannot be less than 284 bytes. If an LSP must also carry the authentication information, the minimum MTU needs to be recalculated according to the packet structure.

When TE is configured, H3C recommends that you set the MTU of any interface with IS-IS enabled be equal to or greater than 512 bytes to guarantee that IS-IS LSPs can be flooded on the network.

To configure IS-IS TE:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter IS-IS view.	isis [ process-id ]	N/A
3. Configure the wide metric attribute of IS-IS.	cost-style { narrow \| wide \| wide-compatible \| { compatible \| narrow-compatible } [ relax-spf-limit ] }	By default, IS-IS uses narrow metric style.
4. Enable IS-IS TE.	traffic-eng [ level-1 \| level-2 \| level-1-2 ]	By default, IS-IS TE is disabled.
5. Configure the TLV type of the sub-TLV carrying DS-TE parameters.	te-set-subtlv { bw-constraint value \| lo-multiplier value \| unreserved-bw-sub-pool value }	Optional. By default, the bw-constraint parameter is carried in sub-TLV 252; the lo-multiplier parameter in sub-TLV 253; and the unreserved-bw-sub-pool parameter in sub-TLV 251.

NOTE:

· For more information about IS-IS, see Layer 3—IP Routing Configuration Guide.

· IS-IS TE does not support secondary IP address advertisement. With IS-IS TE enabled on an interface configured with multiple IP addresses, IS-IS TE advertises only the primary IP address of the interface through the sub-TLV of IS reachability TLV (type 22). H3C does not recommend enabling IS-IS TE on an interface configured with secondary IP addresses.

Configuring an MPLS TE explicit path

An explicit path is a set of nodes. The relationship between any two neighboring nodes on an explicit path can be either strict or loose.

· Strict: The two nodes are directly connected.

· Loose: The two nodes have devices in between.

When inserting nodes to an explicit path or modifying nodes on it, you may configure the include keyword to have the established LSP traverse the specified nodes or the exclude keyword to have the established LSP bypass the specified nodes.

To configure an MPLS TE explicit path:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an explicit path for MPLS TE tunneling and enter its view.	explicit-path path-name [ disable \| enable ]	N/A
3. Add a node to the explicit path.	add hop ip-address1 [ include [ loose \| strict ] \| exclude ] { after \| before } ip-address2	Optional. By default, the include keyword and the strict keyword apply. The explicit path traverses the specified node and the next node is a strict node.
4. Specify a next hop IP address on the explicit path.	next hop ip-address [ include [ loose \| strict ] \| exclude ]	The next hop is a strict node by default. Repeat this step to define a sequential set of the hops that the explicit path traverses.
5. Modify the IP address of current node on the explicit path.	modify hop ip-address1 ip-address2 [ [ include [ loose \| strict ] \| exclude ]	Optional. By default, the include keyword and the strict keyword apply. The explicit path traverses the specified node and the next node is a strict node.
6. Remove a node from the explicit path.	delete hop ip-address	Optional.
7. Display information about the specified or all nodes on the explicit path.	list hop [ ip-address ]	Optional.

NOTE:

When establishing an MPLS TE tunnel between areas or Autonomous Systems (ASs), you must use a loose explicit route, specify the area border router (ABR) or autonomous system boundary router (ASBR) as the next hop of the route, and make sure that the tunnel’s ingress node and the ABR or ASBR are reachable to each other.

Configuring MPLS TE tunnel constraints

To configure MPLS TE tunnel constraints:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Assign bandwidth to the MPLS TE tunnel, and specify a CT for the tunnel’s traffic.	mpls te bandwidth [ ct0 \| ct1 \| ct2 \| ct3 ] bandwidth	Optional. By default, no bandwidth is assigned and traffic of the tunnel belongs to CT 0.
4. Specify a path for the tunnel to use and set the preference of the path.	mpls te path { dynamic \| explicit-path path-name } preference value	Optional. By default, a tunnel uses the dynamically calculated path.
5. Submit current tunnel configuration.	mpls te commit	N/A

Establishing an MPLS TE tunnel with RSVP-TE

To establish an MPLS TE tunnel with RSVP-TE:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable RSVP-TE on your device.	mpls rsvp-te	Disabled by default
4. Exit to system view.	quit	N/A
5. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
6. Enable RSVP-TE on the interface.	mpls rsvp-te	Disabled by default
7. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
8. Set the signaling protocol for setting up the MPLS TE tunnel to RSVP-TE.	mpls te signal-protocol rsvp-te	Optional. RSVP-TE applies by default.
9. Submit current tunnel configuration.	mpls te commit	N/A

CAUTION:

To use RSVP-TE as the signaling protocol for setting up the MPLS TE tunnel, you must enable both MPLS TE and RSVP-TE on the interfaces for the tunnel to use on each node along the tunnel.

Configuring RSVP-TE advanced features

RSVP-TE adds new objects in Path and Resv messages to support CR-LSP setup. RSVP-TE provides many configurable options with respect to reliability, network resources, and other advanced features of MPLS TE.

Before performing the configuration tasks in this section, be aware of each configuration objective and its impact on your network.

Configuration prerequisites

Before you configure RSVP-TE advanced features, complete the following tasks:

· Configure basic MPLS.

· Configure MPLS TE basic settings.

· Establish an MPLS TE tunnel with RSVP-TE.

Configuration procedure

Configuring RSVP reservation style

Each LSP set up using RSVP-TE is assigned a resource reservation style. During an RSVP session, the receiver decides which reservation style can be used for this session and thus which LSPs can be used.

Two reservation styles are available:

· Fixed-filter style (FF) where resources are reserved for individual senders and cannot be shared among senders on the same session.

· Shared-explicit style (SE) where resources are reserved for senders on the same session and shared among them.

To configure RSVP reservation style:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Configure the resources reservation style for the tunnel.	mpls te resv-style { ff \| se }	Optional. The default resource reservation style is SE.
4. Submit current tunnel configuration.	mpls te commit	N/A

NOTE:

In current MPLS TE applications, the SE style is mainly used for make-before-break, while the FF style is rarely used.

Configuring RSVP state timers

To configure RSVP state timers:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Configure the path/reservation state refresh interval of the node.	mpls rsvp-te timer refresh timevalue	Optional. The default path/reservation state refresh interval is 30 seconds.
4. Configure the keep multiplier for PSB and RSB.	mpls rsvp-te keep-multiplier number	Optional. The default is 3.
5. Configure the blockade timeout multiplier.	mpls rsvp-te blockade-multiplier number	Optional. The default blockade timeout multiplier is 4.

Configuring the RSVP refreshing mechanism

To enhance reliability of RSVP message transmission, the Message_ID extension mechanism is used to acknowledge RSVP messages. The Message_ID extension mechanism is also referred to as “the reliability mechanism” throughout this document.

After you enable RSVP message acknowledgement on an interface, you may enable retransmission.

To use summary refresh (Srefresh), you must use the Message_ID extension. Only states advertised using MESSAGE_ID included Path and Resv messages can be refreshed using summary refreshes.

To configure RSVP refreshing mechanism:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
3. Enable the reliability mechanism of RSVP-TE.	mpls rsvp-te reliability	Optional. Disabled by default.
4. Enable retransmission.	mpls rsvp-te timer retransmission { increment-value [ increment-value ] \| retransmit-value [ retrans-timer-value ] } *	Optional. Disabled by default.
5. Enable summary refresh.	mpls rsvp-te srefresh	Optional. Disabled by default.

Configuring the RSVP hello extension

To configure the RSVP hello extension:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable global RSVP hello extension.	mpls rsvp-te hello	Disabled by default.
4. Configure the maximum number of consecutive hellos that should be lost before the link is considered failed..	mpls rsvp-te hello-lost times	Optional. By default, the link is considered failed if three consecutive hellos are lost.
5. Configure the hello interval.	mpls rsvp-te timer hello timevalue	Optional. The default is 3 seconds.
6. Exit to system view.	quit	N/A
7. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
8. Enable interface RSVP hello extension.	mpls rsvp-te hello	Disabled by default.

NOTE:

RSVP hello extension detects the reachability of RSVP neighboring nodes. It is defined in RFC 3209.

Configuring RSVP-TE resource reservation confirmation

To configure RSVP-TE resource reservation confirmation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable resource reservation confirmation.	mpls rsvp-te resvconfirm	Disabled by default

NOTE:

· Reservation confirmation is initiated by the receiver, which sends the Resv message with an object requesting reservation confirmation.

· Receiving the ResvConf message does not mean resource reservation is established. It only indicates that resources are reserved on the farthest upstream node where the Resv message arrived and the resources can be preempted.

Configuring RSVP authentication

RSVP adopts hop-by-hop authentication to prevent fake resource reservation requests from occupying network resources.

It requires that the interfaces at the two ends of a link must share the same authentication key to exchange RSVP messages.

To configure RSVP authentication:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
3. Enable RSVP authentication.	mpls rsvp-te authentication { cipher \| plain } auth-key	Disabled by default

NOTE:

Do not configure both FRR and RSVP authentication on the same interface.

Configuring RSVP-TE GR

The RSVP-TE GR function depends on the extended hello capability of RSVP-TE. Be sure to enable the extended hello capability of RSVP-TE before configuring RSVP-TE GR.

To configure RSVP-TE GR on each device to act as the GR restarter or a GR helper:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable global RSVP hello extension.	mpls rsvp-te hello	Disabled by default
4. Enable MPLS RSVP-TE GR.	mpls rsvp-te graceful-restart	Disabled by default
5. Set the RSVP-TE GR restart timer.	mpls rsvp-te timer graceful-restart restart restart-time	Optional. 120 seconds by default
6. Set the RSVP-TE GR recovery timer.	mpls rsvp-te timer graceful-restart recovery recovery-time	Optional. 300 seconds by default
7. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
8. Enable RSVP hello extension for the interface.	mpls rsvp-te hello	Disabled by default

Configuring Cooperation of RSVP-TE and BFD

On an MPLS TE network, if a link between neighboring LSRs fails, the corresponding MPLS TE tunnel will fail to forward packets. MPLS TE itself cannot detect a link failure in time. To address this issue, you can enable Bidirectional Forwarding Detection (BFD) for RSVP-TE on the two peers of an RSVP-TE tunnel. Then, MPLS TE can be quickly aware of link failures between the peers, making sure that data can be switched from the main path to the backup path.

To configure BFD for an RSVP-TE-enabled interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter the view of an MPLS RSVP-TE enabled interface.	interface interface-type interface-number	N/A
3. Enable BFD on the RSVP-TE enabled interface.	mpls rsvp-te bfd enable	Disabled by default

Tuning CR-LSP setup

A CR-LSP is established through the signaling protocol based on the path calculated by CSPF using TEDB and constraints. MPLS TE can affect CSPF calculation in many ways to determine the path that a CR-LSP can traverse.

Configuration prerequisites

The configuration tasks described in this section are about CSPF of MPLS TE. They must be used in conjunction with CSPF and the dynamic signal protocol (RSVP-TE). Before performing them, be aware of each configuration objective and its impact on your system.

Configuration procedure

Configuring the tie breaker in CSPF

CSPF only calculates the shortest path to the end of a tunnel. If multiple paths are present with the same metric, only one of them is selected. Tie-breaking methods, in the descending order of selection priority, include: selecting a path with the lowest bandwidth usage ratio (the used bandwidth to the maximum reservable link bandwidth), selecting a path with the highest bandwidth usage ratio (the used bandwidth to the maximum reserved link bandwidth), and selecting a path randomly.

To configure the CSPF tie-breaking method:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Specify the tie breaker that a tunnel uses to select a path when multiple paths with the same metric are present on the current node.	mpls te tie-breaking { least-fill \| most-fill \| random }	Optional. The random keyword applies by default.
4. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
5. Specify the tie breaker for the current tunnel to select a path when multiple paths with the same metric are present.	mpls te tie-breaking { least-fill \| most-fill \| random }	Optional. By default, no tie breaker is specified for a specific tunnel and the tunnel uses the tie breaker specified in MPLS view.
6. Submit current tunnel configuration.	mpls te commit	N/A

NOTE:

· A tunnel prefers the tie breaker specified in the tunnel interface view. If no tie breaker is specified in tunnel interface view, the tunnel uses the tie breaker specified in MPLS view to select a path.

· The IETF DS-TE mode supports only random path selection.

Configuring route pinning

Route pinning cannot be used together with reoptimization.

To configure route pinning:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Enable route pinning.	mpls te route-pinning	Disabled by default
4. Submit current tunnel configuration.	mpls te commit	N/A

Configuring administrative group and affinity attribute

The affinity attribute of an MPLS TE tunnel identifies the properties of the links that the tunnel can use. Together with the link administrative group, it decides which links the MPLS TE tunnel can use. This is done by ANDing the 32-bit affinity attribute with the 32-bit link administrative group attribute. When doing that, a 32-bit mask is used. The affinity bits corresponding to the 1s in the mask are “do care” bits which must be considered while those corresponding to the 0s in the mask are “don’t care” bits.

For a link to be used by a TE tunnel, at least one considered affinity bit and its corresponding administrative group bit must be set to 1.

Suppose the affinity of an MPLS TE tunnel is 0xFFFFFFFF and the mask is 0x0000FFFF. For a link to be used by the tunnel, the leftmost 16 bits of its administrative group attribute can be 0s or 1s, but at least one of the rest bits must be 1.

The affinity of an MPLS TE tunnel is configured at the first node on the tunnel and then signaled to the rest nodes through RSVP-TE.

NOTE:

The associations between administrative groups and affinities may vary by vendor. To ensure the successful establishment of a tunnel between two devices from different vendors, correctly configure their respective administrative groups and affinities.

To configure the administrative group and affinity attribute:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
3. Assign the link to a link administrative group.	mpls te link administrative group value	Optional. The default is 0x00000000.
4. Exit to system view.	quit	N/A
5. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
6. Configure the affinity attribute of the MPLS TE tunnel.	mpls te affinity property properties [ mask mask-value ]	Optional. The default affinity attribute is 0x00000000, and the default mask is 0x00000000.
7. Submit current tunnel configuration.	mpls te commit	N/A

Configuring CR-LSP reoptimization

Dynamic CR-LSP optimization involves periodic calculation of paths that traffic trunks traverse. If a better route is found for an existing CR-LSP, a new CR-LSP is established to replace the old one, and services are switched to the new CR-LSP.

To configure CR-LSP reoptimization:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Enable reoptimization for the MPLS TE tunnel.	mpls te reoptimization [ frequency seconds ]	Disabled by default
4. Submit current tunnel configuration.	mpls te commit	N/A
5. Exit to user view.	return	N/A
6. Perform reoptimization on all MPLS TE tunnels with reoptimization enabled.	mpls te reoptimization	Optional.

Tuning MPLS TE tunnel setup

This section only covers the configuration tasks for tuning MPLS TE tunnel setup.

Configuration prerequisites

The configurations described in this section need to be used together with a dynamic signaling protocol (such as RSVP-TE).

Before performing them, be aware of each configuration objective and its impact on your system.

Configuration procedures

Configuring loop detection

To configure loop detection:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Enable the system to perform loop detection when setting up a tunnel.	mpls te loop-detection	Disabled by default
4. Submit current tunnel configuration.	mpls te commit	N/A

Configuring route and label recording

To configure route and label recording:

Step		Command	Remarks
1. Enter system view.		system-view	N/A
2. Enter MPLS TE tunnel interface view.		interface tunnel tunnel-number	N/A
3. Enable the system to record routes or label bindings when setting up the tunnel.	Record routes	mpls te record-route	Use either of the commands. Both route recording and label binding recording are disabled by default.
	Record routes and label bindings	4. mpls te record-route label.
5. Submit current tunnel configuration.		mpls te commit	N/A

Configuring tunnel setup retry

You may configure the system to attempt setting up a tunnel multiple times until it is established successfully or until the number of attempts reaches the upper limit.

To configure tunnel setup retry:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Configure maximum number of tunnel setup retries.	mpls te retry times	Optional. The default is 10.
4. Configure the tunnel setup retry interval.	mpls te timer retry seconds	Optional. The default is 2 seconds.
5. Submit current tunnel configuration.	mpls te commit	N/A

Assigning priorities to a tunnel

Two priorities, setup priority and holding priority, are assigned to paths for MPLS TE to make preemption decision. For a new path to preempt an existing path, the setup priority of the new path must be greater than the holding priority of the existing path.

To avoid flapping caused by improper preemptions between CR-LSPs, the setup priority of a CR-LSP must not be set higher than its holding priority.

To assign priorities to a tunnel:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Assign priorities to the tunnel.	mpls te priority setup-priority [ hold-priority ]	Optional. The default setup and holding priorities are 7.
4. Submit current tunnel configuration.	mpls te commit	N/A

Configuring traffic forwarding

Configuration prerequisites

Before you configure traffic forwarding, complete the following tasks:

· Configure basic MPLS.

· Configure MPLS TE basic settings.

· Configure MPLS TE tunnels.

Configuration procedures

Forwarding traffic along MPLS TE tunnels using static routes

To create static routes for routing traffic along an MPLS TE tunnel:

Step	Command
1. Enter system view.	system-view
2. Create a static route for forwarding traffic along an MPLS TE tunnel.	ip route-static dest-address { mask \| mask-length } interface-type interface-number [ gateway-address ] \| vpn-instance d-vpn-instance-name gateway-address } [ preference preference-value ] [ tag tag-value ] [ description description-text ]

NOTE:

· The interface-type argument in the ip route-static command must be tunnel. In addition, the preference value must be set.

· For more information about static routing, see Layer 3—IP Routing Configuration Guide.

Forwarding traffic along MPLS TE tunnels through automatic route advertisement

Two approaches, IGP shortcut and forwarding adjacency, are available to automatic route advertisement to advertise MPLS TE tunnel interface routes to IGPs, allowing traffic to be routed down MPLS TE tunnels.

In either approach, TE tunnels are considered point-to-point links and TE tunnel interfaces can be set as outgoing interfaces.

You may assign a metric, either absolute or relative, to TE tunnels for the purpose of path calculation in either approach. If it is absolute, the metric is directly used for path calculation. If it is relative, the cost of the corresponding IGP path must be added to the metric before it can be used for path calculation.

Enable OSPF or IS-IS on the tunnel interface of the MPLS TE tunnel before configuring automatic route advertisement.

1. Configure IGP shortcut

To configure IGP shortcut:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Configure the IGP to take the MPLS TE tunnels in up state into account when performing enhanced SPF calculation.	mpls te igp shortcut [ isis \| ospf ]	MPLS TE tunnels are not considered in the enhanced SPF calculation of IGP. If no IGP type is specified, the configuration applies to both OSPF and ISIS by default.
4. Assign a metric to the MPLS TE tunnel.	mpls te igp metric { absolute \| relative } value	Optional. The metrics of TE tunnels equal the metrics of their corresponding IGP routes by default.
5. Submit current tunnel configuration.	mpls te commit	N/A
6. Exit to system view.	quit	N/A
7. Enter OSPF view.	ospf [ process-id ]	N/A
8. Enable the IGP shortcut function.	enable traffic-adjustment	Disabled by default.

2. Configure forwarding adjacency

You need to create a bi-directional MPLS TE tunnel and enable forwarding adjacency at both ends of the tunnel to make forwarding adjacency take effect.

To configure forwarding adjacency:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Enable IGP to advertise the route of the MPLS TE tunnel to IGP neighbors..	mpls te igp advertise [ hold-time value ]	Routes of MPLS TE tunnels are not advertised to IGP neighbors by default.
4. Assign a metric to the MPLS TE tunnel.	mpls te igp metric { absolute \| relative } value	Optional. The metrics of TE tunnels equal the metrics of their corresponding IGP routes by default.
5. Submit current tunnel configuration.	mpls te commit	N/A
6. Exit to system view.	quit	N/A
7. Enter OSPF view.	ospf [ process-id ]	N/A
8. Enable forwarding adjacency.	enable traffic-adjustment advertise	Disabled by default.

NOTE:

If you use automatic route advertisement, you must specify the destination address of the TE tunnel as the LSR ID of the peer and advertise the tunnel interface address to IGPs, such as OSPF and ISIS.

Configuring traffic forwarding tuning parameters

In MPLS TE, you may configure traffic forwarding tuning parameters such as the failed link timer and flooding thresholds to change paths that IP or MPLS traffic flows traverse or to define type of traffic that may travel down a TE tunnel.

Configuration prerequisites

The configurations described in this section are used in conjunction with CSPF and a dynamic signaling protocol, such as RSVP-TE.

Configuration procedure

Configuring the failed link timer

A CSPF failed link timer starts once a link goes down. If IGP removes or modifies the link before the timer expires, CSPF will update information about the link in TEDB and stops the timer. If IGP does not remove or modify the link before the timer expires, the state of the link in TEDB will change to up.

To configure failed link timer:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Configure the CSPF failed link timer.	mpls te cspf timer failed-link timer-interval	Optional. The default is 10 seconds.

Configuring flooding thresholds

After bandwidths of links regulated by MPLS TE change, CSPF may need to recalculate paths. This tends to be resource consuming as recalculation involves IGP flooding. To reduce recalculations and flood only significant changes, you may configure the following two IGP flooding thresholds in percentages:

· Up threshold. When the percentage of available-bandwidth increase to the maximum reservable bandwidth exceeds the threshold, the change is flooded.

· Down threshold. When the percentage of available-bandwidth decrease to the maximum reservable bandwidth exceeds the threshold, the change is flooded.

To configure flooding thresholds:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface interface-type interface-number	N/A
3. Configure the up/down thresholds for IGP to flood bandwidth changes.	mpls te bandwidth change thresholds { down \| up } percent	Optional. Both up and down flooding thresholds are 10 by default.

Specifying the link metric type for tunnel path calculation

To specify the metric type for tunnel path calculation:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Specify the metric type to use when no metric type is explicitly configured for a tunnel.	mpls te path metric-type { igp \| te }	Optional. TE metrics of links are used by default.
4. Return to system view.	quit	N/A
5. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
6. Specify the metric type to use for path calculation of the current tunnel.	mpls te path metric-type { igp \| te }	Optional. By default, no link metric type is specified and the one specified in MPLS view is used.
7. Submit current tunnel configuration.	mpls te commit	Optional.
8. Return to system view.	quit	N/A
9. Enter interface view of MPLS TE link.	interface interface-type interface-number	N/A
10. Assign a TE metric to the link.	mpls te metric value	Optional. If no TE metric is assigned to the link, IGP metric is used as the TE metric by default.

NOTE:

If you do not configure the mpls te path metric-type command in MPLS TE tunnel interface view, the configuration in MPLS view takes effect.

Configuring the traffic flow type of a tunnel

To configure the traffic flow type of a tunnel:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Configure the traffic flow type of the TE tunnel.	mpls te vpn-binding { acl acl-number \| vpn-instance vpn-instance-name }	Optional. Traffic flow types of TE tunnels are not restricted by default.
4. Submit current tunnel configuration.	mpls te commit	N/A

Configuring CR-LSP backup

CR-LSP backup provides end-to-end path protection to protect the entire LSP.

Configuration prerequisites

Before you configure CR-LSP backup, complete the following tasks:

· Configure basic MPLS.

· Configure MPLS TE basic settings.

· Configure MPLS TE tunnels.

Configuration procedure

To configure CR-LSP backup:

Step	Command	Remarks
1. Enter system view of the ingress node.	system-view	N/A
2. Enter MPLS TE tunnel interface view.	interface tunnel tunnel-number	N/A
3. Enable backup for the current tunnel and configure the backup mode.	mpls te backup { hot-standby \| ordinary }	Disabled by default.
4. Submit current tunnel configuration.	mpls te commit	N/A

NOTE:

Configure CR-LSP backup mode at the ingress node of a tunnel. The system automatically selects the primary LSP and backup LSP. You do not need to configure them.

Configuring FRR

NOTE:

Do not configure both FRR and RSVP authentication on the same interface.

As mentioned earlier, FRR provides quick but temporary per-link or per-node local protection on an LSP.

FRR uses bypass tunnels to protect primary tunnels. As bypass tunnels are pre-established, they require extra bandwidth and are usually used to protect crucial interfaces or links only.

You can define which type of LSP can use bypass LSPs, and whether a bypass LSP provides bandwidth protection as well as the sum of protected bandwidth.

The bandwidth of a bypass LSP is to protect its primary LSPs. To guarantee that a primary LSP can always bind with the bypass LSP successfully, make sure that the bandwidth assigned to the bypass LSP is not less than the total bandwidth needed by all protected LSPs.

Normally, bypass tunnels only forward data traffic when protected primary tunnels fail. To allow a bypass tunnel to forward data traffic while protecting the primary tunnel, you need to make sure that bypass tunnels are available with adequate bandwidth.

A bypass tunnel cannot be used for services like VPN at the same time.

Configuration prerequisites

Before you configure FRR, complete the following tasks:

· Configure an IGP, making sure that all LSRs are reachable.

· Configure basic MPLS.

· Configure MPLS TE basic settings.

· Establish an MPLS TE tunnel with RSVP-TE.

· Set up primary LSPs.

Configuration procedure

Enabling FRR on the ingress node of a primary LSP

To enable FRR on the ingress node of a primary LSP:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter tunnel interface view of the primary LSP.	interface tunnel tunnel-number	N/A
3. Enable FRR.	mpls te fast-reroute	Disabled by default
4. Submit current tunnel configuration.	mpls te commit	N/A

Configuring a bypass tunnel on its PLR

After a tunnel is specified to protect an interface, its corresponding LSP becomes a bypass LSP. The setup of a bypass LSP must be manually performed on the PLR. The configuration of a bypass LSP is similar to that of a common LSP, but a bypass LSP cannot act as a primary LSP to be protected by another LSP at the same time.

When specifying a bypass tunnel for an interface, ensure the following:

· The bypass tunnel is up.

· The protected interface is not the outgoing interface of the bypass tunnel.

Up to three bypass tunnels can be specified for a protected interface. The best-fit algorithm is used to determine which of them is used in case failure occurs.

Your device has restriction on links that use the same bypass tunnel so that their total bandwidth does not exceeds a specific value.

To configure a bypass tunnel on its PLR:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view of the bypass tunnel.	interface tunnel tunnel-number	N/A
3. Specify the destination address of the bypass tunnel.	destination ip-address	· For node protection, this is the LSR ID of the next hop router of PLR. · For link protection, this is the LSR ID of the next hop device of PLR.
4. Configure the bandwidth and type of LSP that the bypass tunnel can protect.	mpls te backup bandwidth { bandwidth \| { ct0 \| ct1 \| ct2 \| ct3 } { bandwidth \| un-limited } }	Bandwidth is not protected by default.
5. Submit current tunnel configuration.	mpls te commit	N/A
6. Exit to system view.	quit	N/A
7. Enter interface view of the outgoing interface of the protected LSP.	interface interface-type interface-number	N/A
8. Bind the bypass tunnel with the protected interface.	mpls te fast-reroute bypass-tunnel tunnel tunnel-number	N/A

CAUTION:

Bypass tunnels do not protect bandwidth by default. This can defeat your attempts to binding a primary LSP to a bypass tunnel. Therefore, when configuring a bypass tunnel, you must configure the bandwidth that it is intended to protect with the mpls te backup bandwidth command.

Configuring node protection

To use FRR for node protection, perform the tasks in this section on the PLR and the protected node. If you only need to protect links, skip this section.

To configure node protection:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Enable RSVP hello extension on current node.	mpls rsvp-te hello	Disabled by default.
4. Exit to system view.	quit	N/A
5. Enter the view of the interface directly connected to the protected node or PLR.	interface interface-type interface-number	N/A
6. Enable RSVP hello extension on the interface.	mpls rsvp-te hello	Disabled by default.

NOTE:

RSVP hello extension is configured to detect node failures caused by problems such as signaling error other than failures caused by link failures.

Configuring the FRR polling timer

The protection provided by FRR is temporary. Once a protected LSP becomes available again or a new LSP is established, traffic is switched to the protected or new LSP. After this switchover, the PLR polls available bypass tunnels for the best one at the regular interval specified by the FRR polling timer:

To configure the FRR polling timer:

Step	Command	Remarks
1. Enter system view of the PLR node.	system-view	N/A
2. Enter MPLS view.	mpls	N/A
3. Configure the FRR polling timer.	mpls te timer fast-reroute [ seconds ]	Optional. The FRR polling timer is 300 seconds by default.

Inspecting an MPLS TE tunnel

When an MPLS TE tunnel fails or affects data forwarding due to performance degradation, the control plane cannot detect the fault or cannot do so in time. This brings difficulty to network maintenance. To detect MPLS TE tunnel failures in time and locate the failed node, the switch provides the following mechanisms:

· MPLS LSP ping

· MPLS LSP tracert

· BFD for an MPLS TE tunnel

· Periodic tracert of an MPLS TE tunnel

Configuring MPLS LSP ping

MPLS LSP ping can be used to check the connectivity of an MPLS TE tunnel. At the ingress, it adds the label of the tunnel into an MPLS echo request, and sends it along the MPLS TE tunnel to the egress. The ingress determines whether the MPLS TE tunnel is normal according to whether it can receive a reply from the egress.

To check the connectivity of an MPLS TE tunnel:

Task	Command	Remarks
Use MPLS LSP ping to check the connectivity of an MPLS TE tunnel.	ping lsp [ -a source-ip \| -c count \| -exp exp-value \| -h ttl-value \| -m wait-time \| -r reply-mode \| -s packet-size \| -t time-out \| -v ] * te interface-type interface-number	Available in any view

Configuring MPLS LSP tracert

MPLS LSP tracert can be used to locate errors of an MPLS TE tunnel. It sends MPLS echo requests to the nodes along the MPLS TE tunnel to be inspected, with the TTL increasing from 1 to a specific value. Each node along the MPLS TE tunnel will return an MPLS echo reply to the ingress due to TTL timeout. Thus, the ingress can collect the information of each hop along the MPLS TE tunnel, so as to locate the failed node. You can also use MPLS LSP tracert to collect important information of each hop along the MPLS TE tunnel, such as the label allocated.

To locate errors of an MPLS TE tunnel:

Task	Command	Remarks
Use MPLS LSP tracert to locate errors of an MPLS TE tunnel.	tracert lsp [ -a source-ip \| -exp exp-value \| -h ttl-value \| -r reply-mode \|-t time-out ] * te interface-type interface-number	Available in any view

Configuring BFD for an MPLS TE tunnel

You can configure BFD for an MPLS TE tunnel to implement fast detection of the connectivity of the tunnel. After you configure BFD for an MPLS TE tunnel, a BFD session will be established between the ingress and egress of the tunnel, and the ingress will add the label for the tunnel into a BFD control packet, forward the BFD control packet along the tunnel, and determine the status of the tunnel according to the BFD control packet received from the egress. Upon detecting an MPLS TE tunnel failure, BFD triggers protection switching to switch traffic to another tunnel.

A BFD session for MPLS TE tunnel detection can be static or dynamic.

· Static: If you specify the local and remote discriminator values by using the discriminator keyword when configuring the mpls te bfd enable command, the BFD session will be established with the specified discriminator values. Such a BFD session can detect the connectivity of a pair of MPLS TE tunnels in opposite directions (one from local to remote, and the other from remote to local) between two devices.

· Dynamic: If you do not specify the local and remote discriminator values when configuring the mpls te bfd enable command, the MPLS LSP ping will be run automatically to negotiate the discriminator values and then the BFD session will be established based on the negotiated discriminator values. Such a BFD session can detect the connectivity of a unidirectional (from the local device to the remote device) MPLS TE tunnel between two devices.

After you enable BFD and configure the mpls te failure-action teardown command for an MPLS TE tunnel, once an RSVP-TE tunnel failure occurs, BFD can detect the failure, and if RSVP does not re-establish the tunnel within a specific period of time, MPLS TE will remove the failed RSVP-TE tunnel and then re-establish it.

Configuration guidelines

· You cannot establish both a static BFD session and a dynamic BFD session for the same MPLS TE tunnel.

· After establishing a static BFD session for an MPLS TE tunnel, you cannot modify the discriminator values of the BFD session.

· If you enable both FRR and BFD for an MPLS TE tunnel, to make sure that the BFD session will not be down during an FRR switching, you need to give the BFD detection interval a greater value than the FRR detection interval.

· In a BFD session for detecting an MPLS TE tunnel’s connectivity, the ingress node always works in active mode and the egress node always works in passive mode. The bfd session init-mode command does not take effect on the ingress and egress nodes of such a BFD session. Even if you configure the two nodes to both work in passive mode, the BFD session will still be established successfully.

Configuration prerequisites

· The source address of the BFD session is the MPLS LSR ID. Before configuring BFD to inspect an MPLS TE tunnel, make sure that there is a route on the peer device to the MPLS LSR ID. You can also configure the BFD session parameters on the tunnel interface as needed. For more information about BFD, see High Availability Configuration Guide.

· To establish a static BFD session to inspect an MPLS TE tunnel, make sure that there is already an LSP from the local device to the remote device and an LSP from the remote device to the local device.

Configuring BFD for an MPLS TE tunnel

To configure BFD for an MPLS TE tunnel:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable LSP verification and enter MPLS LSPV view.	mpls lspv	By default, LSP verification is disabled.
3. Return to system view.	quit	N/A
4. Enter the tunnel interface view of an MPLS TE tunnel.	interface tunnel tunnel-number	N/A
5. Configure BFD to check the connectivity of the MPLS TE tunnel.	mpls te bfd enable [ discriminator local local-id remote remote-id ]	By default, BFD is not configured to check connectivity of MPLS TE tunnels.
6. Configure MPLS TE to tear down a failed RSVP TE tunnel and reestablish it.	mpls te failure-action teardown	Optional. Not configured by default

NOTE:

For more information about the mpls lspv command, see MPLS Command Reference.

Configuring periodic LSP tracert

The periodic LSP tracert function for an MPLS TE tunnel is for locating faults of the MPLS TE tunnel periodically. It detects the consistency of the forwarding and control plane and records detection results into logs. You can know whether an MPLS TE tunnel has failed by checking the logs.

If you configure BFD as well as periodical tracert for an MPLS TE tunnel, once the periodical LSP tracert function detects a fault or inconsistency of the forwarding plane and control plane of the MPLS TE tunnel, the BFD session for the tunnel will be deleted and a new BFD session will be established according to the control plane.

After you configure periodic LSP tracert and the mpls te failure-action teardown command for an MPLS TE tunnel, once an RSVP-TE tunnel failure occurs, the periodic LSP tracert function can detect the failure, and if RSVP does not re-establish the RSVP-TE tunnel within a specific period of time, MPLS TE will remove the failed RSVP-TE tunnel and then re-establish it.

To configure periodic LSP tracert for an MPLS TE tunnel:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable LSP verification and enter MPLS LSPV view.	mpls lspv	By default, LSP verification is disabled.
3. Return to system view.	quit	N/A
4. Enter the tunnel interface view of an MPLS TE tunnel.	interface tunnel tunnel-number	N/A
5. Enable periodic LSP tracert for the MPLS TE tunnel.	mpls te periodic-tracert [ -a source-ip \| -exp exp-value \| -h ttl-value \| -m wait-time \| -t time-out \| -u retry-attempt ] *	By default, periodic LSP tracert is disabled for MPLS TE tunnels.
6. Configure MPLS TE to tear down a failed RSVP TE tunnel and reestablish it.	mpls te failure-action teardown	Optional. Not configured by default.

NOTE:

For more information about the mpls lspv command, see MPLS Command Reference.

Configuring protection switching

Configuration prerequisites

Before you configure protection switching, complete following tasks:

· Configure basic MPLS

· Enable MPLS TE and create an MPLS TE tunnel

· Configure BFD for the MPLS TE tunnel

Before you configure a protection tunnel, prepare the following data:

· Interface number of the main tunnel in the protection group

· ID of the protection tunnel in the protection group

Configuration procedure

To configure protection switching:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter tunnel interface view.	interface tunnel tunnel-number	N/A
3. Configure a protection tunnel for the main tunnel.	mpls te protection tunnel tunnel-id [ holdoff holdoff-time \| mode { non-revertive \| revertive [ wtr wtr-time ] } ] *	N/A
4. Configure an external protection switching action.	mpls te protect-switch { clear \| force \| lock \| manual }	Optional. By default, no switching action is configured.
5. Commit the current configuration of the tunnel.	mpls te commit	N/A

Displaying and maintaining MPLS TE

Task	Command	Remarks
Display information about explicit paths.	display explicit-path [ path-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about static CR-LSPs.	display mpls static-cr-lsp [ lsp-name lsp-name ] [ { include \| exclude } ip-address prefix-length ] [ verbose ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display RSVP-TE configuration.	display mpls rsvp-te [ interface [ interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ] ]	Available in any view
Display the RSVP-TE tunnel information.	display mpls rsvp-te established [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display RSVP-TE neighbors.	display mpls rsvp-te peer [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about RSVP requests.	display mpls rsvp-te request [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about RSVP resource reservation.	display mpls rsvp-te reservation [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about RSVP-TE PSB.	display mpls rsvp-te psb-content ingress-lsr-id lspid tunnel-id egress-lsr-id [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about RSVP-TE RSB.	display mpls rsvp-te rsb-content ingress-lsr-id Ispid tunnel-id egress-lsr-id nexthop-address [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about RSVP sender messages.	display mpls rsvp-te sender [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display statistics about RSVP-TE.	display mpls rsvp-te statistics { global \| interface [ interface-type interface-number ] } [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display criteria-compliant information about CSPF-based TEDB.	display mpls te cspf tedb { all \| area area-id \| interface ip-address \| network-lsa \| node [ mpls-lsr-id ] } [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about the CR-LSPs carried on the specified or all links.	display mpls te link-administration admission-control [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display bandwidths allocated to the specified or all MPLS TE-enabled interfaces.	display mpls te link-administration bandwidth-allocation [ interface interface-type interface-number ] [ \| { begin \| exclude \| include } regular-expression ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about MPLS TE tunnels.	display mpls te tunnel [ destination dest-addr ] [ lsp-id lsr-id lsp-id ] [ lsr-role { all \| egress \| ingress \| remote \| transit } ] [ name name ] [ { incoming-interface \| outgoing-interface \| interface } interface-type interface-number ] [ verbose ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the path attributes of MPLS TE tunnels on this node.	display mpls te tunnel path [ lsp-id lsr-id lsp-id \| tunnel-name tunnel-name ] [ \| { begin \| exclude \| include } regular-expression ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display statistics about MPLS TE tunnels.	display mpls te tunnel statistics [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about MPLS TE tunnel interfaces.	display mpls te tunnel-interface tunnel number [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the information of the specified or all OSPF processes about traffic tuning..	display ospf [ process-id ] traffic-adjustment [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about OSPF TE.	display ospf [ process-id ] mpls-te [ area area-id ] [ self-originated ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the latest TE information advertised by IS-IS TE.	display isis traffic-eng advertisements [ [ level-1 \| level-1-2 \| level-2 ] \| [ lsp-id lsp-id \| local ] ] * [ process-id \| vpn-instance vpn-instance-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about TE links for IS-IS.	display isis traffic-eng link [ [ level-1 \| level-1-2 \| level-2 ] \| verbose ] * [ process-id \| vpn-instance vpn-instance-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about TE networks for IS-IS.	display isis traffic-eng network [ level-1 \| level-1-2 \| level-2 ] [ process-id \| vpn-instance vpn-instance-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display statistics about TE for IS-IS.	display isis traffic-eng statistics [ process-id \| vpn-instance vpn-instance-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about sub-TLVs for the IS-IS TE extension.	display isis traffic-eng sub-tlvs [ process-id \| vpn-instance vpn-instance-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about tunnels.	display tunnel-info { tunnel-id \| all \| statistics } [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the BFD information for an MPLS TE tunnel.	display mpls lsp bfd [ te tunnel tunnel-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about the specified tunnels and their protection tunnels.	display mpls te protection tunnel { tunnel-id \| all } [ verbose ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display information about DS-TE.	display mpls te ds-te [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Clear the statistics about RSVP-TE.	reset mpls rsvp-te statistics { global \| interface [ interface-type interface-number ]	Available in user view

MPLS TE configuration examples

NOTE:

By default, Ethernet interfaces, VLAN interfaces, and aggregate interfaces are in DOWN state. To configure such an interface, first use the undo shutdown command to bring the interface up.

MPLS TE using static CR-LSP configuration example

Network requirements

Switch A, Switch B, and Switch C run IS-IS.

Establish a TE tunnel using a static CR-LSP between Switch A and Switch C.

Figure 8 Network diagram

Configuration procedure

1. Assign IP addresses and masks to interfaces (see Figure 8).

Details not shown

2. Enable IS-IS to advertise host routes with LSR IDs as destinations.

# Configure Switch A.

<SwitchA> system-view

[SwitchA] isis 1

[SwitchA-isis-1] network-entity 00.0005.0000.0000.0001.00

[SwitchA-isis-1] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] isis enable 1

[SwitchA-Vlan-interface1] quit

[SwitchA] interface loopback 0

[SwitchA-LoopBack0] isis enable 1

[SwitchA-LoopBack0] quit

# Configure Switch B.

<SwitchB> system-view

[SwitchB] isis 1

[SwitchB-isis-1] network-entity 00.0005.0000.0000.0002.00

[SwitchB-isis-1] quit

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] isis enable 1

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] isis enable 1

[SwitchB-Vlan-interface2] quit

[SwitchB] interface loopback 0

[SwitchB-LoopBack0] isis enable 1

[SwitchB-LoopBack0] quit

# Configure Switch C.

<SwitchC> system-view

[SwitchC] isis 1

[SwitchC-isis-1] network-entity 00.0005.0000.0000.0003.00

[SwitchC-isis-1] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] isis enable 1

[SwitchC-Vlan-interface2] quit

[SwitchC] interface loopback 0

[SwitchC-LoopBack0] isis enable 1

[SwitchC-LoopBack0] quit

Perform the display ip routing-table command on each switch. The output shows that all nodes have learned the host routes of other nodes with LSR IDs as destinations. Take Switch A for example:

[SwitchA] display ip routing-table

Routing Tables: Public

Destinations : 8 Routes : 8

Destination/Mask Proto Pre Cost NextHop Interface

1.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

2.1.1.0/24 Direct 0 0 2.1.1.1 Vlan1

2.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.2/32 ISIS 15 10 2.1.1.2 Vlan1

3.2.1.0/24 ISIS 15 20 2.1.1.2 Vlan1

3.3.3.3/32 ISIS 15 20 2.1.1.2 Vlan1

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

3. Configure MPLS TE basic settings.

# Configure Switch A.

[SwitchA] mpls lsr-id 1.1.1.1

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls

[SwitchA-Vlan-interface1] mpls te

[SwitchA-Vlan-interface1] quit

# Configure Switch B.

[SwitchB] mpls lsr-id 2.2.2.2

[SwitchB] mpls

[SwitchB-mpls] mpls te

[SwitchB-mpls] quit

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] mpls

[SwitchB-Vlan-interface1] mpls te

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] mpls

[SwitchB-Vlan-interface2] mpls te

[SwitchB-Vlan-interface2] quit

# Configure Switch C.

[SwitchC] mpls lsr-id 3.3.3.3

[SwitchC] mpls

[SwitchC-mpls] mpls te

[SwitchC-mpls] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] mpls

[SwitchC-Vlan-interface2] mpls te

[SwitchC-Vlan-interface2] quit

4. Configure an MPLS TE tunnel.

Configure an MPLS TE tunnel on Switch A.

[SwitchA] interface tunnel 0

[SwitchA-Tunnel0] ip address 6.1.1.1 255.255.255.0

[SwitchA-Tunnel0] tunnel-protocol mpls te

[SwitchA-Tunnel0] destination 3.3.3.3

[SwitchA-Tunnel0] mpls te tunnel-id 10

[SwitchA-Tunnel0] mpls te signal-protocol static

[SwitchA-Tunnel0] mpls te commit

[SwitchA-Tunnel0] quit

5. Create a static CR-LSP.

# Configure Switch A as the ingress node of the static CR-LSP.

[SwitchA] static-cr-lsp ingress Tunnel0 destination 3.3.3.3 nexthop 2.1.1.2 out-label 20

# Configure Switch B as the transit node of the static CR-LSP.

[SwitchB] static-cr-lsp transit tunnel0 incoming-interface Vlan-interface1 in-label 20 nexthop 3.2.1.2 out-label 30

# Configure Switch C as the egress node of the static CR-LSP.

[SwitchC] static-cr-lsp egress tunnel0 incoming-interface Vlan-interface2 in-label 30

6. Verify the configuration.

Perform the display interface tunnel command on Switch A. You can find that the tunnel interface is up.

[SwitchA] display interface tunnel

Tunnel0 current state: UP

Line protocol current state: UP

Description: Tunnel0 Interface

The Maximum Transmit Unit is 64000

Internet Address is 6.1.1.1/24 Primary

Encapsulation is TUNNEL, service-loopback-group ID not set

Tunnel source unknown, destination 3.3.3.3

Tunnel protocol/transport CR_LSP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Last 300 seconds input: 0 bytes/sec, 0 packets/sec

Last 300 seconds output: 0 bytes/sec, 0 packets/sec

0 packets input, 0 bytes

0 input error

0 packets output, 0 bytes

0 output error

Perform the display mpls te tunnel command on each switch to verify information about the MPLS TE tunnel.

[SwitchA] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 3.3.3.3 -/Vlan1 Tunnel0

[SwitchB] display mpls te tunnel

LSP-Id Destination In/Out-If Name

- - Vlan1/Vlan2 Tunnel0

[SwitchC] display mpls te tunnel

LSP-Id Destination In/Out-If Name

- - Vlan2/- Tunnel0

Perform the display mpls lsp command or the display mpls static-cr-lsp command on each switch to verify information about the static CR-LSP.

[SwitchA] display mpls lsp

-------------------------------------------------------------------

LSP Information: STATIC CRLSP

-------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

3.3.3.3/32 NULL/20 -/Vlan1

[SwitchB] display mpls lsp

------------------------------------------------------------------

LSP Information: STATIC CRLSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

-/- 20/30 Vlan1/Vlan2

[SwitchC] display mpls lsp

------------------------------------------------------------------

LSP Information: STATIC CRLSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

-/- 30/NULL Vlan1/-

[SwitchA] display mpls static-cr-lsp

total statics-cr-lsp : 1

Name FEC I/O Label I/O If State

Tunnel0 3.3.3.3/32 NULL/20 -/Vlan1 Up

[SwitchB] display mpls static-cr-lsp

total statics-cr-lsp : 1

Name FEC I/O Label I/O If State

Tunnel0 -/- 20/30 Vlan1/Vlan2 Up

[SwitchC] display mpls static-cr-lsp

total statics-cr-lsp : 1

Name FEC I/O Label I/O If State

Tunnel0 -/- 30/NULL Vlan2/- Up

NOTE:

On an MPLS TE tunnel configured using a static CR-LSP, traffic is forwarded directly based on label at the transit nodes and egress node. Therefore, it is normal that the FEC field in the sample output is empty on Switch B and Switch C.

7. Create a static route for routing MPLS TE tunnel traffic.

[SwitchA] ip route-static 3.2.1.2 24 tunnel 0 preference 1

Perform the display ip routing-table command on Switch A. You can see a static route entry with interface Tunnel 0 as the outgoing interface.

MPLS TE using RSVP-TE configuration example

Network requirements

Switch A, Switch B, Switch C, and Switch D are running IS-IS and all of them are Level-2 devices.

Use RSVP-TE to create a TE tunnel with 2000 kbps of bandwidth from Switch A to Switch D

Figure 9 Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loop0	1.1.1.9/32	Switch D	Loop0	4.4.4.9/32
	Vlan-int1	10.1.1.1/24		Vlan-int3	30.1.1.2/24
Switch B	Loop0	2.2.2.9/32	Switch C	Loop0	3.3.3.9/32
	Vlan-int1	10.1.1.2/24		Vlan-int3	30.1.1.1/24
	Vlan-int2	20.1.1.1/24		Vlan-int2	20.1.1.2/24

Configuration procedure

1. Assign IP addresses and masks to interfaces (see Figure 9).

Details not shown

2. Enable IS-IS to advertise host routes with LSR IDs as destinations.

# Configure Switch A.

<SwitchA> system-view

[SwitchA] isis 1

[SwitchA-isis-1] network-entity 00.0005.0000.0000.0001.00

[SwitchA-isis-1] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] isis enable 1

[SwitchA-Vlan-interface1] isis circuit-level level-2

[SwitchA-Vlan-interface1] quit

[SwitchA] interface loopback 0

[SwitchA-LoopBack0] isis enable 1

[SwitchA-LoopBack0] isis circuit-level level-2

[SwitchA-LoopBack0] quit

# Configure Switch B.

<SwitchB> system-view

[SwitchB] isis 1

[SwitchB-isis-1] network-entity 00.0005.0000.0000.0002.00

[SwitchB-isis-1] quit

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] isis enable 1

[SwitchB-Vlan-interface1] isis circuit-level level-2

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] isis enable 1

[SwitchB-Vlan-interface2] isis circuit-level level-2

[SwitchB-Vlan-interface2] quit

[SwitchB] interface loopback 0

[SwitchB-LoopBack0] isis enable 1

[SwitchB-LoopBack0] isis circuit-level level-2

[SwitchB-LoopBack0] quit

# Configure Switch C.

<SwitchC> system-view

[SwitchC] isis 1

[SwitchC-isis-1] network-entity 00.0005.0000.0000.0003.00

[SwitchC-isis-1] quit

[SwitchC] interface vlan-interface 3

[SwitchC-Vlan-interface3] isis enable 1

[SwitchC-Vlan-interface3] isis circuit-level level-2

[SwitchC-Vlan-interface3] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] isis enable 1

[SwitchC-Vlan-interface2] isis circuit-level level-2

[SwitchC-Vlan-interface2] quit

[SwitchC] interface loopback 0

[SwitchC-LoopBack0] isis enable 1

[SwitchC-LoopBack0] isis circuit-level level-2

[SwitchC-LoopBack0] quit

# Configure Switch D.

<SwitchD> system-view

[SwitchD] isis 1

[SwitchD-isis-1] network-entity 00.0005.0000.0000.0004.00

[SwitchD-isis-1] quit

[SwitchD] interface vlan-interface 3

[SwitchD-Vlan-interface3] isis enable 1

[SwitchD-Vlan-interface3] isis circuit-level level-2

[SwitchD-Vlan-interface3] quit

[SwitchD] interface loopback 0

[SwitchD-LoopBack0] isis enable 1

[SwitchD-LoopBack0] isis circuit-level level-2

[SwitchD-LoopBack0] quit

Perform the display ip routing-table command on each switch. The output shows that all nodes have learned the host routes of other nodes with LSR IDs as destinations. Take Switch A for example:

[SwitchA] display ip routing-table

Routing Tables: Public

Destinations : 10 Routes : 10

Destination/Mask Proto Pre Cost NextHop Interface

1.1.1.9/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.9/32 ISIS 15 10 10.1.1.2 Vlan1

3.3.3.9/32 ISIS 15 20 10.1.1.2 Vlan1

4.4.4.9/32 ISIS 15 30 10.1.1.2 Vlan1

10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan1

10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

20.1.1.0/24 ISIS 15 20 10.1.1.2 Vlan1

30.1.1.0/24 ISIS 15 30 10.1.1.2 Vlan1

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

3. Configure MPLS TE basic settings, and enable RSVP-TE and CSPF.

# Configure Switch A.

[SwitchA] mpls lsr-id 1.1.1.9

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] mpls rsvp-te

[SwitchA-mpls] mpls te cspf

[SwitchA-mpls] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls

[SwitchA-Vlan-interface1] mpls te

[SwitchA-Vlan-interface1] mpls rsvp-te

[SwitchA-Vlan-interface1] quit

# Configure Switch B.

[SwitchB] mpls lsr-id 2.2.2.9

[SwitchB] mpls

[SwitchB-mpls] mpls te

[SwitchB-mpls] mpls rsvp-te

[SwitchB-mpls] mpls te cspf

[SwitchB-mpls] quit

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] mpls

[SwitchB-Vlan-interface1] mpls te

[SwitchB-Vlan-interface1] mpls rsvp-te

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] mpls

[SwitchB-Vlan-interface2] mpls te

[SwitchB-Vlan-interface2] mpls rsvp-te

[SwitchB-Vlan-interface2] quit

# Configure Switch C.

[SwitchC] mpls lsr-id 3.3.3.9

[SwitchC] mpls

[SwitchC-mpls] mpls te

[SwitchC-mpls] mpls rsvp-te

[SwitchC-mpls] mpls te cspf

[SwitchC-mpls] quit

[SwitchC] interface vlan-interface 3

[SwitchC-Vlan-interface3] mpls

[SwitchC-Vlan-interface3] mpls te

[SwitchC-Vlan-interface3] mpls rsvp-te

[SwitchC-Vlan-interface3] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] mpls

[SwitchC-Vlan-interface2] mpls te

[SwitchC-Vlan-interface2] mpls rsvp-te

[SwitchC-Vlan-interface2] quit

# Configure Switch D.

[SwitchD] mpls lsr-id 4.4.4.9

[SwitchD] mpls

[SwitchD-mpls] mpls te

[SwitchD-mpls] mpls rsvp-te

[SwitchD-mpls] mpls te cspf

[SwitchD-mpls] quit

[SwitchD] interface vlan-interface 3

[SwitchD-Vlan-interface3] mpls

[SwitchD-Vlan-interface3] mpls te

[SwitchD-Vlan-interface3] mpls rsvp-te

[SwitchD-Vlan-interface3] quit

4. Configure IS-IS TE.

# Configure Switch A.

[SwitchA] isis 1

[SwitchA-isis-1] cost-style wide

[SwitchA-isis-1] traffic-eng level-2

[SwitchA-isis-1] quit

# Configure Switch B.

[SwitchB] isis 1

[SwitchB-isis-1] cost-style wide

[SwitchB-isis-1] traffic-eng level-2

[SwitchB-isis-1] quit

# Configure Switch C.

[SwitchC] isis 1

[SwitchC-isis-1] cost-style wide

[SwitchC-isis-1] traffic-eng level-2

[SwitchC-isis-1] quit

# Configure Switch D.

[SwitchD] isis 1

[SwitchD-isis-1] cost-style wide

[SwitchD-isis-1] traffic-eng level-2

[SwitchD-isis-1] quit

5. Create an MPLS TE tunnel.

Create an MPLS TE tunnel on Switch A.

[SwitchA] interface tunnel 1

[SwitchA-Tunnel1] ip address 7.1.1.1 255.255.255.0

[SwitchA-Tunnel1] tunnel-protocol mpls te

[SwitchA-Tunnel1] destination 4.4.4.9

[SwitchA-Tunnel1] mpls te tunnel-id 10

[SwitchA-Tunnel1] mpls te signal-protocol rsvp-te

[SwitchA-Tunnel1] mpls te commit

[SwitchA-Tunnel1] quit

6. Verify the configuration.

Perform the display interface tunnel command on Switch A. You can see that the tunnel interface is up.

[SwitchA] display interface tunnel

Tunnel1 current state: UP

Line protocol current state: UP

Description: Tunnel1 Interface

The Maximum Transmit Unit is 64000

Internet Address is 7.1.1.1/24 Primary

Encapsulation is TUNNEL, service-loopback-group ID not set

Tunnel source unknown, destination 4.4.4.9

Tunnel protocol/transport CR_LSP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Last 300 seconds input: 0 bytes/sec, 0 packets/sec

Last 300 seconds output: 0 bytes/sec, 0 packets/sec

0 packets input, 0 bytes

0 input error

0 packets output, 0 bytes

0 output error

Perform the display mpls te tunnel-interface command on Switch A to verify information about the MPLS TE tunnel.

[SwitchA] display mpls te tunnel-interface

Tunnel Name : Tunnel1

Tunnel Desc : Tunnel1 Interface

Tunnel State Desc : CR-LSP is Up

Tunnel Attributes :

LSP ID : 1.1.1.9:3

Session ID : 10

Admin State : UP Oper State : UP

Ingress LSR ID : 1.1.1.9 Egress LSR ID: 4.4.4.9

Signaling Prot : RSVP Resv Style : SE

Class Type : CT0 Tunnel BW : 0 kbps

Reserved BW : 0 kbps

Setup Priority : 7 Hold Priority: 7

Affinity Prop/Mask : 0x0/0x0

Explicit Path Name : -

Tie-Breaking Policy : None

Metric Type : None

Record Route : Disabled Record Label : Disabled

FRR Flag : Disabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 10 Retry Interval: 10 sec

Reopt : Disabled Reopt Freq : -

Back Up Type : None

Back Up LSPID : -

Auto BW : Disabled Auto BW Freq : -

Min BW : - Max BW : -

Current Collected BW: -

Interfaces Protected: -

VPN Bind Type : NONE

VPN Bind Value : -

Car Policy : Disabled

Tunnel Group : Primary

Primary Tunnel : -

Backup Tunnel : -

Group Status : -

Perform the display mpls te cspf tedb all command on Switch A to view information about links in TEDB.

[SwitchA] display mpls te cspf tedb all

Maximum Node Supported: 128 Maximum Link Supported: 256

Current Total Node Number: 4 Current Total Link Number: 6

Id MPLS LSR-Id IGP Process-Id Area Link-Count

1 3.3.3.9 ISIS 1 Level-2 2

2 2.2.2.9 ISIS 1 Level-2 2

3 4.4.4.9 ISIS 1 Level-2 1

4 1.1.1.9 ISIS 1 Level-2 1

7. Create a static route for routing MPLS TE tunnel traffic

[SwitchA] ip route-static 30.1.1.2 24 tunnel 1 preference 1

Perform the display ip routing-table command on Switch A. You can see a static route entry with interface Tunnel1 as the outgoing interface.

Configuration example of inter-AS MPLS TE tunnel using RSVP-TE

Network requirements

· Switch A and Switch B are in AS 100, and they run OSPF as the IGP.

· Switch C and Switch D are in AS 200, and they run OSPF as the IGP.

· Establish an EBGP connection between ASBRs Switch B and Switch C. Redistribute BGP routes into OSPF and OSPF routes into BGP, so that a route is available between AS 100 and AS 200.

· Establish an MPLS TE tunnel between Switch A and Switch D by using RSVP-TE.

Figure 10 Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loop0	1.1.1.9/32	Switch D	Loop0	4.4.4.9/32
	Vlan-int1	10.1.1.1/24		Vlan-int3	30.1.1.2/24
Switch B	Loop0	2.2.2.9/32	Switch C	Loop0	3.3.3.9/32
	Vlan-int1	10.1.1.2/24		Vlan-int3	30.1.1.1/24
	Vlan-int2	20.1.1.1/24		Vlan-int2	20.1.1.2/24

Configuration procedure

1. Assign IP addresses and masks to interfaces (see Figure 10).

2. Configure OSPF to advertise routes within the ASs.

# Configure OSPF on Switch A.

<SwitchA> system-view

[SwitchA] ospf

[SwitchA-ospf-1] area 0

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

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

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

[SwitchA-ospf-1] quit

# Configure OSPF on Switch B.

<SwitchB> system-view

[SwitchB] ospf

[SwitchB-ospf-1] import-route direct

[SwitchB-ospf-1] import-route bgp

[SwitchB-ospf-1] area 0

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

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

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

[SwitchB-ospf-1] quit

# Configure OSPF on Switch C.

<SwitchC> system-view

[SwitchC] ospf

[SwitchC-ospf-1] import-route direct

[SwitchC-ospf-1] import-route bgp

[SwitchC-ospf-1] area 0

[SwitchC-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255

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

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

[SwitchC-ospf-1] quit

# Configure OSPF on Switch D.

<SwitchD> system-view

[SwitchD] ospf

[SwitchD-ospf-1] area 0

[SwitchD-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255

[SwitchD-ospf-1-area-0.0.0.0] network 4.4.4.9 0.0.0.0

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

[SwitchD-ospf-1] quit

After the configurations, execute the display ip routing-table command on each device. The output shows that the switch in an AS has learned the route to the LSR ID of the other device in the AS. Take Switch A as an example:

[SwitchA] display ip routing-table

Routing Tables: Public

Destinations : 6 Routes : 6

Destination/Mask Proto Pre Cost NextHop Interface

1.1.1.9/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.9/32 OSPF 10 1 10.1.1.2 Vlan1

10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan1

10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

3. Configure BGP on Switch B and Switch C, ensuring the ASs can communicate with each other.

# Configure Switch B.

[SwitchB] bgp 100

[SwitchB-bgp] peer 20.1.1.2 as-number 200

[SwitchB-bgp] import-route ospf

[SwitchB-bgp] import-route direct

[SwitchB-bgp] quit

# Configure Switch C.

[SwitchC] bgp 200

[SwitchC-bgp] peer 20.1.1.1 as-number 100

[SwitchC-bgp] import-route ospf

[SwitchC-bgp] import-route direct

[SwitchC-bgp] quit

After the configuration, execute the display ip routing-table command on each device. The output shows that each device has learned the routes to the outside of the AS. Take Switch A as an example:

[SwitchA] display ip routing-table

Routing Tables: Public

Destinations : 10 Routes : 10

Destination/Mask Proto Pre Cost NextHop Interface

1.1.1.9/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.9/32 OSPF 10 1 10.1.1.2 Vlan1

3.3.3.9/32 O_ASE 150 1 10.1.1.2 Vlan1

4.4.4.9/32 O_ASE 150 1 10.1.1.2 Vlan1

10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan1

10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

20.1.1.0/24 O_ASE 150 1 10.1.1.2 Vlan1

30.1.1.0/24 O_ASE 150 1 10.1.1.2 Vlan1

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

4. Configure MPLS TE basic settings, and enable RSVP-TE and CSPF.

# Configure Switch A.

[SwitchA] mpls lsr-id 1.1.1.9

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] mpls rsvp-te

[SwitchA-mpls] mpls te cspf

[SwitchA-mpls] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls

[SwitchA-Vlan-interface1] mpls te

[SwitchA-Vlan-interface1] mpls rsvp-te

[SwitchA-Vlan-interface1] quit

# Configure Switch B.

[SwitchB] mpls lsr-id 2.2.2.9

[SwitchB] mpls

[SwitchB-mpls] mpls te

[SwitchB-mpls] mpls rsvp-te

[SwitchB-mpls] mpls te cspf

[SwitchB-mpls] quit

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] mpls

[SwitchB-Vlan-interface1] mpls te

[SwitchB-Vlan-interface1] mpls rsvp-te

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] mpls

[SwitchB-Vlan-interface2] mpls te

[SwitchB-Vlan-interface2] mpls rsvp-te

[SwitchB-Vlan-interface2] quit

# Configure Switch C.

[SwitchC] mpls lsr-id 3.3.3.9

[SwitchC] mpls

[SwitchC-mpls] mpls te

[SwitchC-mpls] mpls rsvp-te

[SwitchC-mpls] mpls te cspf

[SwitchC-mpls] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] mpls

[SwitchC-Vlan-interface2] mpls te

[SwitchC-Vlan-interface2] mpls rsvp-te

[SwitchC-Vlan-interface2] quit

[SwitchC] interface vlan-interface 3

[SwitchC-Vlan-interface3] mpls

[SwitchC-Vlan-interface3] mpls te

[SwitchC-Vlan-interface3] mpls rsvp-te

[SwitchC-Vlan-interface3] quit

# Configure Switch D.

[SwitchD] mpls lsr-id 4.4.4.9

[SwitchD] mpls

[SwitchD-mpls] mpls te

[SwitchD-mpls] mpls rsvp-te

[SwitchD-mpls] mpls te cspf

[SwitchD-mpls] quit

[SwitchD] interface vlan-interface 3

[SwitchD-Vlan-interface3] mpls

[SwitchD-Vlan-interface3] mpls te

[SwitchD-Vlan-interface3] mpls rsvp-te

[SwitchD-Vlan-interface3] quit

5. Configure OSPF TE.

# Configure Switch A.

[SwitchA] ospf

[SwitchA-ospf-1] opaque-capability enable

[SwitchA-ospf-1] area 0

[SwitchA-ospf-1-area-0.0.0.0] mpls-te enable

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

[SwitchA-ospf-1] quit

# Configure Switch B.

[SwitchB] ospf

[SwitchB-ospf-1] opaque-capability enable

[SwitchB-ospf-1] area 0

[SwitchB-ospf-1-area-0.0.0.0] mpls-te enable

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

[SwitchB-ospf-1] quit

# Configure Switch C.

[SwitchC] ospf

[SwitchC-ospf-1] opaque-capability enable

[SwitchC-ospf-1] area 0

[SwitchC-ospf-1-area-0.0.0.0] mpls-te enable

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

[SwitchC-ospf-1] quit

# Configure Switch D.

[SwitchD] ospf

[SwitchD-ospf-1] opaque-capability enable

[SwitchD-ospf-1] area 0

[SwitchD-ospf-1-area-0.0.0.0] mpls-te enable

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

[SwitchD-ospf-1] quit

6. Configure a loose explicit route.

Configure a loose explicit route on Switch A.

[SwitchA] explicit-path atod enable

[SwitchA-explicit-path-atod] next hop 10.1.1.2 include loose

[SwitchA-explicit-path-atod] next hop 20.1.1.2 include loose

[SwitchA-explicit-path-atod] next hop 30.1.1.2 include loose

[SwitchA-explicit-path-atod] quit

7. Create an MPLS TE tunnel.

# Create an MPLS TE tunnel on Switch A.

[SwitchA] interface tunnel 1

[SwitchA-Tunnel1] ip address 7.1.1.1 255.255.255.0

[SwitchA-Tunnel1] tunnel-protocol mpls te

[SwitchA-Tunnel1] destination 4.4.4.9

[SwitchA-Tunnel1] mpls te tunnel-id 10

[SwitchA-Tunnel1] mpls te signal-protocol rsvp-te

[SwitchA-Tunnel1] mpls te path explicit-path atod preference 5

[SwitchA-Tunnel1] mpls te commit

[SwitchA-Tunnel1] quit

8. Verify the configuration.

Perform the display interface tunnel command on Switch A. The output shows that the tunnel interface is up.

[SwitchA] display interface tunnel 1

Tunnel1 current state: UP

Line protocol current state: UP

Description: Tunnel1 Interface

The Maximum Transmit Unit is 64000

Internet Address is 7.1.1.1/24 Primary

Encapsulation is TUNNEL, service-loopback-group ID not set.

Tunnel source unknown, destination 4.4.4.9

Tunnel protocol/transport CR_LSP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Last clearing of counters: Never

Last 300 seconds input: 0 bytes/sec, 0 packets/sec

Last 300 seconds output: 0 bytes/sec, 0 packets/sec

0 packets input, 0 bytes

0 input error

0 packets output, 0 bytes

0 output error

Perform the display mpls te tunnel-interface command on Switch A to view the detailed information of the MPLS TE tunnel.

[SwitchA] display mpls te tunnel-interface

Tunnel Name : Tunnel1

Tunnel Desc : Tunnel1 Interface

Tunnel State Desc : CR-LSP is Up

Tunnel Attributes :

LSP ID : 1.1.1.9:2

Session ID : 10

Admin State : UP Oper State : UP

Ingress LSR ID : 1.1.1.9 Egress LSR ID: 4.4.4.9

Signaling Prot : RSVP Resv Style : SE

Class Type : CT0 Tunnel BW : 0 kbps

Reserved BW : 0 kbps

Setup Priority : 7 Hold Priority: 7

Affinity Prop/Mask : 0x0/0x0

Explicit Path Name : atod

Tie-Breaking Policy : None

Metric Type : None

Loop Detection : Disabled

Record Route : Disabled Record Label : Disabled

FRR Flag : Disabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 10 Retry Interval: 2 sec

Reopt : Disabled Reopt Freq : -

Back Up Type : None

Back Up LSPID : -

Auto BW : Disabled Auto BW Freq : -

Min BW : - Max BW : -

Current Collected BW: -

Interfaces Protected: -

VPN Bind Type : NONE

VPN Bind Value : -

Car Policy : Disabled

Tunnel Group : Primary

Primary Tunnel : -

Backup Tunnel : -

Group Status : -

Perform the display mpls te cspf tedb all command on Switch A to view information about links in TEDB.

[SwitchA] display mpls te cspf tedb all

Maximum Node Supported: 128 Maximum Link Supported: 256

Current Total Node Number: 2 Current Total Link Number: 2

Id MPLS LSR-Id IGP Process-Id Area Link-Count

1 1.1.1.9 OSPF 1 0 1

2 2.2.2.9 OSPF 1 0 1

9. Create a static route for routing MPLS TE tunnel traffic

[SwitchA] ip route-static 30.1.1.2 24 tunnel 1 preference 1

Perform the display ip routing-table command on Switch A. The output shows a static route entry with interface Tunnel 1 as the outgoing interface.

[SwitchA] display ip routing-table

Routing Tables: Public

Destinations : 14 Routes : 14

Destination/Mask Proto Pre Cost NextHop Interface

1.1.1.9/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.9/32 OSPF 10 1 10.1.1.2 Vlan1

3.3.3.9/32 O_ASE 150 1 10.1.1.2 Vlan1

4.4.4.9/32 O_ASE 150 1 10.1.1.2 Vlan1

7.1.1.0/24 Direct 0 0 7.1.1.1 Tun1

7.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan1

10.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

20.1.1.0/24 O_ASE 150 1 10.1.1.2 Vlan1

30.1.1.0/24 Static 1 0 7.1.1.1 Tun1

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

RSVP-TE GR configuration example

Network requirements

Switch A, Switch B and Switch C are running IS-IS. All of them are Level-2 devices and support RSVP hello extension.

Use RSVP-TE to create a TE tunnel from Switch A to Switch C.

Switch A, Switch B and Switch C are RSVP-TE neighbors. With GR capability, each of them can provide GR helper support when another is GR restarting.

Figure 11 Network diagram

Configuration procedure

1. Assign IP addresses and masks to interfaces (see Figure 11).

Details not shown

2. Enable IS-IS to advertise host routes with LSR IDs as destinations.

Details not shown

3. Configure MPLS TE basic settings, and enable RSVP-TE and RSVP hello extension.

# Configure Switch A.

<SwitchA> system-view

[SwitchA] mpls lsr-id 1.1.1.9

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] mpls rsvp-te

[SwitchA-mpls] mpls rsvp-te hello

[SwitchA-mpls] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls

[SwitchA-Vlan-interface1] mpls te

[SwitchA-Vlan-interface1] mpls rsvp-te

[SwitchA-Vlan-interface1] mpls rsvp-te hello

[SwitchA-Vlan-interface1] quit

# Configure Switch B.

<SwitchB> system-view

[SwitchB] mpls lsr-id 2.2.2.9

[SwitchB] mpls

[SwitchB-mpls] mpls te

[SwitchB-mpls] mpls rsvp-te

[SwitchB-mpls] mpls rsvp-te hello

[SwitchB-mpls] interface vlan-interface 1

[SwitchB-Vlan-interface1] mpls

[SwitchB-Vlan-interface1] mpls te

[SwitchB-Vlan-interface1] mpls rsvp-te

[SwitchB-Vlan-interface1] mpls rsvp-te hello

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] mpls

[SwitchB-Vlan-interface2] mpls te

[SwitchB-Vlan-interface2] mpls rsvp-te

[SwitchB-Vlan-interface2] mpls rsvp-te hello

[SwitchB-Vlan-interface2] quit

# Configure Switch C.

<SwitchC> system-view

[SwitchC] mpls lsr-id 3.3.3.9

[SwitchC] mpls

[SwitchC-mpls] mpls te

[SwitchC-mpls] mpls rsvp-te

[SwitchC-mpls] mpls rsvp-te hello

[SwitchC-mpls] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] mpls

[SwitchC-Vlan-interface2] mpls te

[SwitchC-Vlan-interface2] mpls rsvp-te

[SwitchC-Vlan-interface2] mpls rsvp-te hello

[SwitchC-Vlan-interface2] quit

4. Configure IS-IS TE.

Details not shown

5. Configure the MPLS TE tunnel.

Details not shown

6. Configure RSVP-TE GR.

# Configure Switch A.

<SwitchA> system-view

[SwitchA] mpls

[SwitchA-mpls] mpls rsvp-te graceful-restart

# Configure Switch B.

<SwitchB> system-view

[SwitchB] mpls

[SwitchB-mpls] mpls rsvp-te graceful-restart

# Configure Switch C.

<SwitchC> system-view

[SwitchC] mpls

[SwitchC-mpls] mpls rsvp-te graceful-restart

7. Verify the configuration.

After the configuration, a tunnel will be created between Switch A and Switch C. Issuing the following command, you will see that the neighbor’s GR status is Ready.

<SwitchA> display mpls rsvp-te peer

Interface Vlan-interface1

Neighbor Addr: 10.1.1.2

SrcInstance: 880 NbrSrcInstance: 5017

PSB Count: 0 RSB Count: 1

Hello Type Sent: REQ Neighbor Hello Extension: ENABLE

SRefresh Enable: NO

Graceful Restart State: Ready

Restart Time: 120 Sec Recovery Time: 300 Sec

MPLS RSVP-TE and BFD cooperation configuration example

Network requirements

Switch A and Switch B are connected directly. Enable MPLS RSVP-TE BFD on the VLAN interfaces connecting the two switches, and run OSPF on the switches to ensure reachability at the network layer.

If the link between Switch A and Switch B fails, BFD can detect the failure quickly and inform MPLS RSVP-TE of the failure.

Figure 12 Network diagram

Configuration procedure

1. Configure basic MPLS RSVP-TE.

# Configure Switch A.

<SwitchA> system-view

[SwitchA] mpls lsr-id 1.1.1.1

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] mpls rsvp-te

[SwitchA-mpls] quit

[SwitchA] interface vlan-interface 12

[SwitchA-Vlan-interface12] mpls

[SwitchA-Vlan-interface12] mpls te

[SwitchA-Vlan-interface12] mpls rsvp-te

[SwitchA-Vlan-interface12] mpls rsvp-te bfd enable

[SwitchA-Vlan-interface12] quit

# Configure Switch B.

<SwitchB> system-view

[SwitchB] mpls lsr-id 2.2.2.2

[SwitchB] mpls

[SwitchB-mpls] mpls te

[SwitchB-mpls] mpls rsvp-te

[SwitchB-mpls] quit

[SwitchB] interface vlan-interface 12

[SwitchB-Vlan-interface12] mpls

[SwitchB-Vlan-interface12] mpls te

[SwitchB-Vlan-interface12] mpls rsvp-te

[SwitchB-Vlan-interface12] mpls rsvp-te bfd enable

[SwitchB-Vlan-interface12] quit

2. Configure OSPF.

# Configure Switch A.

[SwitchA] ospf

[SwitchA-ospf-1] area 0

[SwitchA-ospf-1-area-0.0.0.0] network 12.12.12.1 0.0.0.255

[SwitchA-ospf-1-area-0.0.0.0] network 1.1.1.1 0.0.0.0

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

[SwitchA-ospf-1] quit

# Configure Switch B.

[SwitchB] ospf

[SwitchB-ospf-1] area 0

[SwitchB-ospf-1-area-0.0.0.0] network 12.12.12.2 0.0.0.255

[SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

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

[SwitchB-ospf-1] quit

3. Configure IP addresses for the interfaces.

# Configure Switch A.

[SwitchA] interface vlan-interface 12

[SwitchA-Vlan-interface12] ip address 12.12.12.1 24

[SwitchA-Vlan-interface12] quit

# Configure Switch B.

[SwitchB] interface vlan-interface 12

[SwitchB-Vlan-interface12] ip address 12.12.12.2 24

4. Configure the MPLS TE tunnel.

Configure an RSVP-TE tunnel between Switch A and Switch B.

[SwitchA] interface tunnel 1

[SwitchA-Tunnel1] ip address 10.10.10.1 24

[SwitchA-Tunnel1] tunnel-protocol mpls te

[SwitchA-Tunnel1] destination 2.2.2.2

[SwitchA-Tunnel1] mpls te tunnel-id 10

[SwitchA-Tunnel1] mpls te signal-protocol rsvp-te

[SwitchA-Tunnel1] mpls te commit

[SwitchA-Tunnel1] return

5. Verify the configuration.

On Switch A, display the detailed information about the BFD session between Switch A and Switch B.

<SwitchA> display bfd session verbose

Total Session Num: 1 Init Mode: Active

Session Working Under Ctrl Mode:

Local Discr: 21 Remote Discr: 20

Source IP: 12.12.12.1 Destination IP: 12.12.12.2

Session State: Up Interface: Vlan-interface12

Min Trans Inter: 400ms Act Trans Inter: 400ms

Min Recv Inter: 400ms Act Detect Inter: 2000ms

Running Up for: 00:00:01 Auth mode: None

Connect Type: Direct Board Num: 6

Protocol: RSVP

Diag Info: No Diagnostic

CR-LSP backup configuration example

Network requirements

Set up an MPLS TE tunnel from Switch A to Switch C. Use CR-LSP hot backup for it.

Figure 13 Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loop0	1.1.1.9/32	Switch D	Loop0	4.4.4.9/32
	Vlan-int1	10.1.1.1/24		Vlan-int4	30.1.1.2/24
	Vlan-int4	30.1.1.1/24		Vlan-int3	40.1.1.1/24
Switch B	Loop0	2.2.2.9/32	Switch C	Loop0	3.3.3.9/32
	Vlan-int1	10.1.1.2/24		Vlan-int2	20.1.1.2/24
	Vlan-int2	20.1.1.1/24		Vlan-int3	40.1.1.2/24

Configuration procedure

1. Assign IP addresses and masks to interfaces (see Figure 13).

Details not shown

2. Configure the IGP protocol.

# Enable IS-IS to advertise host routes with LSR IDs as destinations on each node. (Details not shown)

# Perform the display ip routing-table command on each switch. You can see that all nodes have learned the host routes of other nodes with LSR IDs as destinations.

3. Configure MPLS TE basic settings, and enable RSVP-TE and CSPF.

# Configure Switch A.

<SwitchA> system-view

[SwitchA] mpls lsr-id 1.1.1.9

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] mpls rsvp-te

[SwitchA-mpls] mpls te cspf

[SwitchA-mpls] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls

[SwitchA-Vlan-interface1] mpls te

[SwitchA-Vlan-interface1] mpls rsvp-te

[SwitchA-Vlan-interface1] quit

[SwitchA] interface vlan-interface 4

[SwitchA-Vlan-interface4] mpls

[SwitchA-Vlan-interface4] mpls te

[SwitchA-Vlan-interface4] mpls rsvp-te

[SwitchA-Vlan-interface4] quit

NOTE:

Follow the same steps to configure Switch B, Switch C, and Switch D.

4. Create an MPLS TE tunnel on Switch A.

# Configure the MPLS TE tunnel carried on the primary LSP.

[SwitchA] interface tunnel 1

[SwitchA-Tunnel1] ip address 9.1.1.1 24

[SwitchA-Tunnel1] tunnel-protocol mpls te

[SwitchA-Tunnel1] destination 3.3.3.9

[SwitchA-Tunnel1] mpls te tunnel-id 10

[SwitchA-Tunnel1] mpls te record-route

# Enable hot LSP backup.

[SwitchA-Tunnel1] mpls te backup hot-standby

[SwitchA-Tunnel1] mpls te commit

[SwitchA-Tunnel1] quit

Perform the display interface tunnel command on Switch A. You can see that Tunnel1 is up.

[SwitchA] display interface tunnel

Tunnel1 current state: UP

Line protocol current state: UP

Description: Tunnel1 Interface

The Maximum Transmit Unit is 64000

Internet Address is 9.1.1.1/24 Primary

Encapsulation is TUNNEL, service-loopback-group ID not set

Tunnel source unknown, destination 3.3.3.9

Tunnel protocol/transport CR_LSP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Last 300 seconds input: 0 bytes/sec, 0 packets/sec

Last 300 seconds output: 0 bytes/sec, 0 packets/sec

0 packets input, 0 bytes

0 input error

0 packets output, 0 bytes

0 output error

5. Verify the configuration.

Perform the display mpls te tunnel command on Switch A. You can see that two tunnels are present with the outgoing interface being VLAN-interface 1 and VLAN-interface 4 respectively. This indicates that a backup CR-LSP was created upon creation of the primary CR-LSP.

[SwitchA] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.9:6 3.3.3.9 -/Vlan1 Tunnel1

1.1.1.9:2054 3.3.3.9 -/Vlan4 Tunnel1

Perform the display mpls te tunnel path command on Switch A to identify the paths that the two tunnels traverse:

[SwitchA] display mpls te tunnel path

Tunnel Interface Name : Tunnel1

Lsp ID : 1.1.1.9 :6

Hop Information

Hop 0 10.1.1.1

Hop 1 10.1.1.2

Hop 2 2.2.2.9

Hop 3 20.1.1.1

Hop 4 20.1.1.2

Hop 5 3.3.3.9

Tunnel Interface Name : Tunnel1

Lsp ID : 1.1.1.9 :2054

Hop Information

Hop 0 30.1.1.1

Hop 1 30.1.1.2

Hop 2 4.4.4.9

Hop 3 40.1.1.1

Hop 4 40.1.1.2

Hop 5 3.3.3.9

Perform the tracert command to draw the picture of the path that a packet must travel to reach the tunnel destination.

[SwitchA] tracert –a 1.1.1.9 3.3.3.9

traceroute to 3.3.3.9(3.3.3.9) 30 hops max,40 bytes packet

1 10.1.1.2 25 ms 30.1.1.2 25 ms 10.1.1.2 25 ms

2 40.1.1.2 45 ms 20.1.1.2 29 ms 40.1.1.2 54 ms

The sample output shows that the current LSP traverses Switch B but not Switch D.

Shut down VLAN-interface 2 on Switch B. Perform the tracert command on Switch A to draw the path to the tunnel destination. The output shows that the LSP is re-routed to traverse Switch D:

[SwitchA] tracert –a 1.1.1.9 3.3.3.9

traceroute to 3.3.3.9(3.3.3.9) 30 hops max,40 bytes packet

1 30.1.1.2 28 ms 27 ms 23 ms

2 40.1.1.2 50 ms 50 ms 49 ms

Perform the display mpls te tunnel command on Switch A. You can see that only the tunnel traversing Switch D is present:

[SwitchA] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.9:2054 3.3.3.9 -/Vlan4 Tunnel1

NOTE:

Configuring ordinary CR-LSP backup is almost the same as configuring hot CR-LSP backup except that you need to replace the mpls te backup hot-standby command with the mpls te backup ordinary command. Unlike in hot CR-LSP backup where a secondary tunnel is created immediately upon creation of a primary tunnel, in ordinary CR-LSP backup, a secondary CR-LSP is created only after the primary LSP goes down.

6. Create a static route for routing MPLS TE tunnel traffic.

[SwitchA] ip route-static 20.1.1.2 24 tunnel 1 preference 1

Perform the display ip routing-table command on Switch A. You can see a static route entry with Tunnel1 as the outgoing interface.

FRR configuration example

Network requirements

On a primary LSP Switch A → Switch B → Switch C → Switch D, use FRR to protect the link Switch B → Switch C.

Do the following:

· Create a bypass LSP that traverses the path Switch B → Switch E → Switch C. Switch B is the PLR and Switch C is the MP.

· Explicitly route the primary TE tunnel and the bypass TE tunnel with the signaling protocol being RSVP-TE.

Figure 14 Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loop0	1.1.1.1/32	Switch E	Loop0	5.5.5.5/32
	Vlan-int1	2.1.1.1/24		Vlan-int4	3.2.1.2/24
Switch B	Loop0	2.2.2.2/32		Vlan-int5	3.3.1.1/24
	Vlan-int1	2.1.1.2/24	Switch C	Loop0	3.3.3.3/32
	Vlan-int2	3.1.1.1/24		Vlan-int3	4.1.1.1/24
	Vlan-int4	3.2.1.1/24		Vlan-int2	3.1.1.2/24
Switch D	Loop0	4.4.4.4/32		Vlan-int5	3.3.1.2/24
	Vlan-int3	4.1.1.2/24

Configuration procedure

1. Assign IP addresses and masks to interfaces (see Figure 14).

Details not shown

2. Configure the IGP protocol.

# Enable IS-IS to advertise host routes with LSR IDs as destinations on each node. (Details not shown)

# Perform the display ip routing-table command on each switch. You can see that all nodes have learned the host routes of other nodes with LSR IDs as destinations. Take Switch A for example:

<SwitchA> display ip routing-table

Routing Tables: Public

Destinations : 13 Routes : 13

Destination/Mask Proto Pre Cost NextHop Interface

1.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

2.1.1.0/24 Direct 0 0 2.1.1.1 Vlan1

2.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0

2.2.2.2/32 ISIS 15 10 2.1.1.2 Vlan1

3.1.1.0/24 ISIS 15 20 2.1.1.2 Vlan1

3.2.1.0/24 ISIS 15 20 2.1.1.2 Vlan1

3.3.1.0/24 ISIS 15 30 2.1.1.2 Vlan1

3.3.3.3/32 ISIS 15 20 2.1.1.2 Vlan1

4.1.1.0/24 ISIS 15 30 2.1.1.2 Vlan1

4.4.4.4/32 ISIS 15 30 2.1.1.2 Vlan1

5.5.5.5/32 ISIS 15 20 2.1.1.2 Vlan1

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

3. Configure MPLS TE basic settings, and enable RSVP-TE and CSPF.

# Configure Switch A.

[SwitchA] mpls lsr-id 1.1.1.1

[SwitchA] mpls

[SwitchA-mpls] mpls te

[SwitchA-mpls] mpls rsvp-te

[SwitchA-mpls] mpls te cspf

[SwitchA-mpls] quit

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls

[SwitchA-Vlan-interface1] mpls te

[SwitchA-Vlan-interface1] mpls rsvp-te

[SwitchA-Vlan-interface1] quit

# Configure Switch B.

[SwitchB] mpls lsr-id 2.2.2.2

[SwitchB] mpls

[SwitchB-mpls] mpls te

[SwitchB-mpls] mpls rsvp-te

[SwitchB-mpls] mpls te cspf

[SwitchB-mpls] quit

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] mpls

[SwitchB-Vlan-interface1] mpls te

[SwitchB-Vlan-interface1] mpls rsvp-te

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] mpls

[SwitchB-Vlan-interface2] mpls te

[SwitchB-Vlan-interface2] mpls rsvp-te

[SwitchB-Vlan-interface2] quit

[SwitchB] interface vlan-interface 4

[SwitchB-Vlan-interface4] mpls

[SwitchB-Vlan-interface4] mpls te

[SwitchB-Vlan-interface4] mpls rsvp-te

[SwitchB-Vlan-interface4] quit

NOTE:

Follow the same steps to configure Switch C, Switch D, and Switch E.

4. Create an MPLS TE tunnel on Switch A, the ingress node of the primary LSP.

# Create an explicit path for the primary LSP.

[SwitchA] explicit-path pri-path

[SwitchA-explicit-path-pri-path] next hop 2.1.1.2

[SwitchA-explicit-path-pri-path] next hop 3.1.1.2

[SwitchA-explicit-path-pri-path] next hop 4.1.1.2

[SwitchA-explicit-path-pri-path] next hop 4.4.4.4

[SwitchA-explicit-path-pri-path] quit

# Configure the MPLS TE tunnel carried on the primary LSP.

[SwitchA] interface tunnel 4

[SwitchA-Tunnel4] ip address 10.1.1.1 255.255.255.0

[SwitchA-Tunnel4] tunnel-protocol mpls te

[SwitchA-Tunnel4] destination 4.4.4.4

[SwitchA-Tunnel4] mpls te tunnel-id 10

[SwitchA-Tunnel4] mpls te path explicit-path pri-path preference 1

# Enable FRR.

[SwitchA-Tunnel4] mpls te fast-reroute

[SwitchA-Tunnel4] mpls te commit

[SwitchA-Tunnel4] quit

Perform the display interface tunnel command on Switch A. You can see that Tunnel4 is up.

[SwitchA] display interface tunnel

Tunnel4 current state: UP

Line protocol current state: UP

Description: Tunnel4 Interface

The Maximum Transmit Unit is 64000

Internet Address is 10.1.1.1/24 Primary

Encapsulation is TUNNEL, service-loopback-group ID not set

Tunnel source unknown, destination 4.4.4.4

Tunnel protocol/transport CR_LSP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Last 300 seconds input: 0 bytes/sec, 0 packets/sec

Last 300 seconds output: 0 bytes/sec, 0 packets/sec

0 packets input, 0 bytes

0 input error

0 packets output, 0 bytes

0 output error

Perform the display mpls te tunnel-interface command on Switch A to verify the configuration of the tunnel interface.

[SwitchA] display mpls te tunnel-interface

Tunnel Name : Tunnel4

Tunnel Desc : Tunnel4 Interface

Tunnel State Desc : CR-LSP is Up

Tunnel Attributes :

LSP ID : 1.1.1.1:1

Session ID : 10

Admin State : UP Oper State : UP

Ingress LSR ID : 1.1.1.1 Egress LSR ID: 4.4.4.4

Signaling Prot : RSVP Resv Style : SE

Class Type : CT0 Tunnel BW : 0 kbps

Reserved BW : 0 kbps

Setup Priority : 7 Hold Priority: 7

Affinity Prop/Mask : 0/0

Explicit Path Name : pri-path

Tie-Breaking Policy : None

Metric Type : None

Record Route : Enabled Record Label : Enabled

FRR Flag : Enabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 10 Retry Interval: 10 sec

Reopt : Disabled Reopt Freq : -

Back Up Type : None

Back Up LSPID : -

Auto BW : Disabled Auto BW Freq : -

Min BW : - Max BW : -

Current Collected BW: -

Interfaces Protected: -

VPN Bind Type : NONE

VPN Bind Value : -

Car Policy : Disabled

Tunnel Group : Primary

Primary Tunnel : -

Backup Tunnel : -

Group Status : -

5. Configure a bypass tunnel on Switch B (the PLR).

# Create an explicit path for the bypass LSP.

[SwitchB] explicit-path by-path

[SwitchB-explicit-path-by-path] next hop 3.2.1.2

[SwitchB-explicit-path-by-path] next hop 3.3.1.2

[SwitchB-explicit-path-by-path] next hop 3.3.3.3

[SwitchB-explicit-path-by-path] quit

# Create the bypass tunnel.

[SwitchB] interface tunnel 5

[SwitchB-Tunnel5] ip address 11.1.1.1 255.255.255.0

[SwitchB-Tunnel5] tunnel-protocol mpls te

[SwitchB-Tunnel5] destination 3.3.3.3

[SwitchB-Tunnel5] mpls te tunnel-id 15

[SwitchB-Tunnel5] mpls te path explicit-path by-path preference 1

# Configure the bandwidth that the bypass tunnel protects.

[SwitchB-Tunnel5] mpls te backup bandwidth 10000

[SwitchB-Tunnel5] mpls te commit

[SwitchB-Tunnel5] quit

# Bind the bypass tunnel with the protected interface.

[SwitchB] interface Vlan-interface 2

[SwitchB-Vlan-interface2] mpls te fast-reroute bypass-tunnel tunnel 5

[SwitchB-Vlan-interface2] quit

Perform the display interface tunnel command on Switch B. You can see that Tunnel5 is up.

Perform the display mpls lsp command on each switch. You can see that two LSPs are traversing Switch B and Switch C.

[SwitchA] display mpls lsp

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

4.4.4.4/32 NULL/1024 -/Vlan1

[SwitchB] display mpls lsp

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

4.4.4.4/32 1024/1024 Vlan1/Vlan2

3.3.3.3/32 NULL/1024 -/Vla4

[SwitchC] display mpls lsp

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

4.4.4.4/32 1024/3 Vlan2/Vlan3

3.3.3.3/32 3/NULL Vlan5/-

[SwitchD] display mpls lsp

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

4.4.4.4/32 3/NULL Vlan3/-

[SwitchE] display mpls lsp

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

FEC In/Out Label In/Out IF Vrf Name

3.3.3.3/32 1024/3 Vlan4/Vlan5

Perform the display mpls te tunnel command on each switch. You can see that two MPLS TE tunnels are traversing Switch B and Switch C.

[SwitchA] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 -/Vlan1 Tunnel4

[SwitchB] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 Vlan1/Vlan2 Tunnel4

2.2.2.2:1 3.3.3.3 -/Vlan4 Tunnel5

[SwitchC] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 Vlan2/Vlan3 Tunnel4

2.2.2.2:1 3.3.3.3 Vlan5/- Tunnel5

[SwitchD] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 Vlan3/- Tunnel4

[SwitchE] display mpls te tunnel

LSP-Id Destination In/Out-If Name

2.2.2.2:1 3.3.3.3 Vlan4/Vlan5 Tunnel5

Perform the display mpls lsp verbose command on Switch B. You can see that the bypass tunnel is bound with the protected interface VLAN-interface 2 and is currently unused.

[SwitchB] display mpls lsp verbose

-------------------------------------------------------------------

LSP Information: RSVP LSP

-------------------------------------------------------------------

No : 1

IngressLsrID : 1.1.1.1

LocalLspID : 1

Tunnel-Interface : Tunnel4

Fec : 4.4.4.4/32

Nexthop : 3.1.1.2

In-Label : 1024

Out-Label : 1024

In-Interface : Vlan-interface1

Out-Interface : Vlan-interface2

LspIndex : 4097

Tunnel ID : 0x22001

LsrType : Transit

Bypass In Use : Not Used

BypassTunnel : Tunnel Index[Tunnel5], InnerLabel[1024]

Mpls-Mtu : 1500

No : 2

IngressLsrID : 2.2.2.2

LocalLspID : 1

Tunnel-Interface : Tunnel5

Fec : 3.3.3.3/32

Nexthop : 3.2.1.2

In-Label : NULL

Out-Label : 1024

In-Interface : ----------

Out-Interface : Vlan-interface4

LspIndex : 4098

Tunnel ID : 0x22002

LsrType : Ingress

Bypass In Use : Not Exists

BypassTunnel : Tunnel Index[---]

Mpls-Mtu : 1500

6. Verify the FRR function.

# Shut down the protected outgoing interface on PLR.

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] shutdown

%Sep 7 08:53:34 2004 SwitchB IFNET/5/UPDOWN:Line protocol on the interface Vlan-interface2 turns into DOWN state

Perform the display interface tunnel 4 command on Switch A to identify the state of the primary LSP. You can see that the tunnel interface is still up.

Perform the display mpls te tunnel-interface command on Switch A to verify the configuration of the tunnel interface.

[SwitchA] display mpls te tunnel-interface

Tunnel Name : Tunnel4

Tunnel Desc : Tunnel4 Interface

Tunnel State Desc : Modifying CR-LSP is setting up

Tunnel Attributes :

LSP ID : 1.1.1.1:1

Session ID : 10

Admin State : UP Oper State : UP

Ingress LSR ID : 1.1.1.1 Egress LSR ID: 4.4.4.4

Signaling Prot : RSVP Resv Style : SE

Class Type : CT0 Tunnel BW : 0 kbps

Reserved BW : 0 kbps

Setup Priority : 7 Hold Priority: 7

Affinity Prop/Mask : 0x0/0x0

Explicit Path Name : pri-path

Tie-Breaking Policy : None

Metric Type : None

Record Route : Enabled Record Label : Enabled

FRR Flag : Enabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 10 Retry Interval: 10 sec

Reopt : Disabled Reopt Freq : -

Back Up Type : None

Back Up LSPID : -

Auto BW : Disabled Auto BW Freq : -

Min BW : - Max BW : -

Current Collected BW: -

Interfaces Protected: -

VPN Bind Type : NONE

VPN Bind Value : -

Car Policy : Disabled

Tunnel Group : Primary

Primary Tunnel : -

Backup Tunnel : -

Group Status : -

Tunnel Name : Tunnel4

Tunnel Desc : Tunnel4 Interface

Tunnel State Desc : Modifying CR-LSP is setting up

Tunnel Attributes :

LSP ID : 1.1.1.1:1025

Session ID : 10

Admin State : Oper State : Modified

Ingress LSR ID : 1.1.1.1 Egress LSR ID: 4.4.4.4

Signaling Prot : RSVP Resv Style : SE

Class Type : CT0 Tunnel BW : 0 kbps

Reserved BW : 0 kbps

Setup Priority : 7 Hold Priority: 7

Affinity Prop/Mask : 0x0/0x0

Explicit Path Name : pri-path

Tie-Breaking Policy : None

Metric Type : None

Record Route : Enabled Record Label : Enabled

FRR Flag : Enabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 10 Retry Interval: 10 sec

Reopt : Disabled Reopt Freq : -

Back Up Type : None

Back Up LSPID : -

Auto BW : Disabled Auto BW Freq : -

Min BW : - Max BW : -

Current Collected BW: -

Interfaces Protected: -

VPN Bind Type : NONE

VPN Bind Value : -

Car Policy : Disabled

Tunnel Group : Primary

Primary Tunnel : -

Backup Tunnel : -

Group Status : -

NOTE:

If you perform the display mpls te tunnel-interface command immediately after an FRR protection switch, you are likely to see two CR-LSPs in up state are present. This is normal because the make-before-break mechanism of FRR introduces a delay before removing the old LSP after a new LSP is created.

Perform the display mpls lsp verbose command on Switch B. You can see that the bypass tunnel is in use.

[SwitchB] display mpls lsp verbose

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

No : 1

IngressLsrID : 1.1.1.1

LocalLspID : 1

Tunnel-Interface : Tunnel4

Fec : 4.4.4.4/32

Nexthop : 3.1.1.2

In-Label : 1024

Out-Label : 1024

In-Interface : Vlan-interface1

Out-Interface : Vlan-interface2

LspIndex : 4097

Tunnel ID : 0x22001

LsrType : Transit

Bypass In Use : In Use

BypassTunnel : Tunnel Index[Tunnel5], InnerLabel[1024]

Mpls-Mtu : 1500

No : 2

IngressLsrID : 2.2.2.2

LocalLspID : 1

Tunnel-Interface : Tunnel5

Fec : 3.3.3.3/32

Nexthop : 3.2.1.2

In-Label : NULL

Out-Label : 1024

In-Interface : ----------

Out-Interface : Vlan-interface4

LspIndex : 4098

Tunnel ID : 0x22002

LsrType : Ingress

Bypass In Use : Not Exists

BypassTunnel : Tunnel Index[---]

Mpls-Mtu : 1500

# Set the FRR polling timer to five seconds on PLR.

[SwitchB] mpls

[SwitchB-mpls] mpls te timer fast-reroute 5

[SwitchB-mpls] quit

# Bring the protected outgoing interface up on PLR.

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] undo shutdown

%Sep 7 09:01:31 2004 SwitchB IFNET/5/UPDOWN:Line protocol on the interface Vlan-interface2 turns into UP state

Perform the display interface tunnel 4 command on Switch A to identify the state of the primary LSP. You can see that the tunnel interface is up.

About 5 seconds later, perform the display mpls lsp verbose command on Switch B. You can see that Tunnel5 is still bound with interface VLAN-interface 2 and is unused.

7. Create a static route for routing MPLS TE tunnel traffic.

[SwitchA] ip route-static 4.1.1.2 24 tunnel 4 preference 1

Perform the display ip routing-table command on Switch A. You can see a static route entry with Tunnel4 as the outgoing interface.

MPLS TE in MPLS L3VPN configuration example

Network requirements

CE 1 and CE 2 belong to VPN 1. They are connected to the MPLS backbone respectively through PE 1 and PE 2. The IGP protocol running on the MPLS backbone is OSPF.

Do the following:

· Set up an MPLS TE tunnel to forward traffic of VPN 1 from PE 1 to PE 2.

· To allow the MPLS L3VPN traffic to travel the TE tunnel, configure a tunneling policy to use a CR-LSP as the VPN tunnel when creating the VPN.

Figure 15 Network diagram

Configuration procedure

1. Configure OSPF, making sure that PE 1 and PE 2 can learn LSR-ID routes from each other.

# Configure PE 1.

<PE1> system-view

[PE1] interface loopback 0

[PE1-LoopBack0] ip address 2.2.2.2 255.255.255.255

[PE1-LoopBack0] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] ip address 10.0.0.1 255.255.255.0

[PE1-Vlan-interface2] quit

[PE1] ospf

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] network 10.0.0.0 0.0.0.255

[PE1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0

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

[PE1-ospf-1] quit

# Configure PE 2.

<PE2> system-view

[PE2] interface loopback 0

[PE2-LoopBack0] ip address 3.3.3.3 255.255.255.255

[PE2-LoopBack0] quit

[PE2] interface vlan-interface 2

[PE2-Vlan-interface2] ip address 10.0.0.2 255.255.255.0

[PE2-Vlan-interface2] quit

[PE2] ospf

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] network 10.0.0.0 0.0.0.255

[PE2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0

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

[PE2-ospf-1] quit

After you complete the configuration, the PEs will be able to establish the OSPF neighbor relationship. Perform the display ospf peer verbose command; you will see that the neighbor relationship state is FULL. Perform the display ip routing-table command; you will see that the PEs have learned the routes to the loopback interfaces of each other. Take PE 1 for example:

[PE1] display ospf peer verbose

OSPF Process 1 with Router ID 2.2.2.2

Neighbors

Area 0.0.0.0 interface 10.0.0.1(Vlan-interface2)'s neighbors

Router ID: 3.3.3.3 Address: 10.0.0.2 GR State: Normal

State: Full Mode:Nbr is Master Priority: 1

DR: None BDR: None

Dead timer due in 30 sec

Neighbor is up for 00:01:00

Authentication Sequence: [ 0 ]

[PE1] display ip routing-table

Routing Tables: Public

Destinations : 7 Routes : 7

Destination/Mask Proto Pre Cost NextHop Interface

2.2.2.2/32 Direct 0 0 127.0.0.1 InLoop0

3.3.3.3/32 OSPF 10 1563 10.0.0.2 Vlan2

10.0.0.0/24 Direct 0 0 10.0.0.1 Vlan2

10.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

10.0.0.2/32 Direct 0 0 10.0.0.2 Vlan2

127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0

127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0

2. Configure basic MPLS TE, enable RSVP-TE and CSPF.

# Configure PE 1.

[PE1] mpls lsr-id 2.2.2.2

[PE1] mpls

[PE1-mpls] lsp-trigger all

[PE1-mpls] mpls te

[PE1-mpls] mpls rsvp-te

[PE1-mpls] mpls te cspf

[PE1-mpls] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] mpls

[PE1-Vlan-interface2] mpls te

[PE1-Vlan-interface2] mpls rsvp-te

[PE1-Vlan-interface2] quit

# Configure PE 2.

[PE2] mpls lsr-id 3.3.3.3

[PE2] mpls

[PE2-mpls] lsp-trigger all

[PE2-mpls] mpls te

[PE2-mpls] mpls rsvp-te

[PE2-mpls] mpls te cspf

[PE2-mpls] quit

[PE2] interface vlan-interface 2

[PE2-Vlan-interface2] mpls

[PE2-Vlan-interface2] mpls te

[PE2-Vlan-interface2] mpls rsvp-te

[PE2-Vlan-interface2] quit

3. Enable OSPF TE.

# Configure PE 1.

[PE1] ospf

[PE1-ospf-1] opaque-capability enable

[PE1-ospf-1] area 0

[PE1-ospf-1-area-0.0.0.0] mpls-te enable

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

[PE1-ospf-1] quit

# Configure PE 2.

[PE2] ospf

[PE2-ospf-1] opaque-capability enable

[PE2-ospf-1] area 0

[PE2-ospf-1-area-0.0.0.0] mpls-te enable

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

[PE2-ospf-1] quit

4. Configure an MPLS TE tunnel.

# Create a TE tunnel with PE 1 as the ingress node and PE 2 as the egress node. The signaling protocol is RSVP-TE.

[PE1] interface tunnel 1

[PE1-Tunnel1] ip address 12.1.1.1 255.255.255.0

[PE1-Tunnel1] tunnel-protocol mpls te

[PE1-Tunnel1] destination 3.3.3.3

[PE1-Tunnel1] mpls te tunnel-id 10

[PE1-Tunnel1] mpls te signal-protocol rsvp-te

[PE1-Tunnel1] mpls te commit

[PE1-Tunnel1] quit

Perform the display interface tunnel command on PE 1. You can see that the tunnel interface is up.

5. Configure the VPN instance on each PE, and bind it to the interface connected to the CE.

# Configure on CE 1.

<CE1> system-view

[CE1] interface vlan-interface 1

[CE1-Vlan-interface1] ip address 192.168.1.2 255.255.255.0

[CE1-Vlan-interface1] quit

# Configure the VPN instance on PE 1, and use CR-LSP for VPN setup. Bind the VPN instance with the interface connected to CE 1.

[PE1] ip vpn-instance vpn1

[PE1-vpn-instance-vpn1] route-distinguisher 100:1

[PE1-vpn-instance-vpn1] vpn-target 100:1 both

[PE1-vpn-instance-vpn1] tnl-policy policy1

[PE1-vpn-instance-vpn1] quit

[PE1] tunnel-policy policy1

[PE1-tunnel-policy-policy1] tunnel select-seq cr-lsp load-balance-number 1

[PE1-tunnel-policy-policy1] quit

[PE1] interface vlan-interface 1

[PE1-Vlan-interface1] ip binding vpn-instance vpn1

[PE1-Vlan-interface1] ip address 192.168.1.1 255.255.255.0

[PE1-Vlan-interface1] quit

# Configure on CE 2.

<CE2> system-view

[CE2] interface vlan-interface 3

[CE2-Vlan-interface3] ip address 192.168.2.2 255.255.255.0

[CE2-Vlan-interface3] quit

# Configure the VPN instance on PE 2, and bind it with the interface connected to CE 2.

[PE2] ip vpn-instance vpn1

[PE2-vpn-instance-vpn1] route-distinguisher 100:2

[PE2-vpn-instance-vpn1] vpn-target 100:1 both

[PE2-vpn-instance-vpn1] quit

[PE2] interface vlan-interface 3

[PE2-Vlan-interface3] ip binding vpn-instance vpn1

[PE2-Vlan-interface3] ip address 192.168.2.1 255.255.255.0

[PE2-Vlan-interface3] quit

Perform the display ip vpn-instance command on the PEs to verify the configuration of the VPN instance. Take PE 1 for example:

[PE1] display ip vpn-instance instance-name vpn1

VPN-Instance Name and ID : vpn1, 1

Create time : 2006/09/27 15:10:29

Up time : 0 days, 00 hours, 03 minutes and 09 seconds

Route Distinguisher : 100:1

Export VPN Targets : 100:1

Import VPN Targets : 100:1

Tunnel Policy : policy1

Interfaces : Vlan-interface1

Ping connected CEs on PEs to test connectivity. For example, ping CE 1 on PE 1:

[PE1] ping -vpn-instance vpn1 192.168.1.2

PING 192.168.1.2: 56 data bytes, press CTRL_C to break

Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=47 ms

Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=255 time=26 ms

Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=255 time=26 ms

Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=255 time=26 ms

Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=255 time=26 ms

--- 192.168.1.2 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 26/30/47 ms

The sample output shows that PE 1 can reach CE 1.

6. Configure BGP.

# Configure CE 1.

[CE1] bgp 65001

[CE1-bgp] peer 192.168.1.1 as-number 100

[CE1-bgp] quit

# Configure PE 1 to establish the EBGP peer relationship with CE 1, and the IBGP peer relationship with PE 2.

[PE1] bgp 100

[PE1-bgp] ipv4-family vpn-instance vpn1

[PE1-bgp-vpn1] peer 192.168.1.2 as-number 65001

[PE1-bgp-vpn1] import-route direct

[PE1-bgp-vpn1] quit

[PE1-bgp] peer 3.3.3.3 as-number 100

[PE1-bgp] peer 3.3.3.3 connect-interface loopback 0

[PE1-bgp] ipv4-family vpnv4

[PE1-bgp-af-vpnv4] peer 3.3.3.3 enable

[PE1-bgp-af-vpnv4] quit

[PE1-bgp] quit

# Configure CE 2.

[CE2] bgp 65002

[CE2-bgp] peer 192.168.2.1 as-number 100

[CE2-bgp] quit

# Configure PE 2 to establish the EBGP peer relationship with CE 2 and the IBGP relationship with PE 1.

[PE2] bgp 100

[PE2-bgp] ipv4-family vpn-instance vpn1

[PE2-bgp-vpn1] peer 192.168.2.2 as-number 65002

[PE2-bgp-vpn1] import-route direct

[PE2-bgp-vpn1] quit

[PE2-bgp] peer 2.2.2.2 as-number 100

[PE2-bgp] peer 2.2.2.2 connect-interface loopback 0

[PE2-bgp] ipv4-family vpnv4

[PE2-bgp-af-vpnv4] peer 2.2.2.2 enable

[PE2-bgp-af-vpnv4] quit

[PE2-bgp] quit

Perform the display bgp peer command and the display bgp vpn-instance peer command on PEs. The output shows that the BGP peer relationships have been formed between PEs and between PEs and CEs and have reached the established state. Take PE 1 for example:

[PE1-bgp] display bgp peer

BGP local router ID : 2.2.2.2

Local AS number : 100

Total number of peers : 1 Peers in established state : 1

Peer V AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State PrefRcv

3.3.3.3 4 100 3 3 0 0 00:00:11 Established 0

[PE1-bgp] display bgp vpn-instance vpn1 peer

BGP local router ID : 2.2.2.2

Local AS number : 100

Total number of peers : 1 Peers in established state : 1

Peer V AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State PrefRcv

192.168.1.2 4 65001 4 5 0 0 00:02:13 Established 0

Ping CE 2 on CE 1 and vice versa to test connectivity.

[CE1] ping 192.168.2.2

PING 192.168.2.2: 56 data bytes, press CTRL_C to break

Reply from 192.168.2.2: bytes=56 Sequence=1 ttl=253 time=61 ms

Reply from 192.168.2.2: bytes=56 Sequence=2 ttl=253 time=54 ms

Reply from 192.168.2.2: bytes=56 Sequence=3 ttl=253 time=53 ms

Reply from 192.168.2.2: bytes=56 Sequence=4 ttl=253 time=57 ms

Reply from 192.168.2.2: bytes=56 Sequence=5 ttl=253 time=36 ms

--- 192.168.2.2 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 36/52/61 ms

[CE2] ping 192.168.1.2

PING 192.168.1.2: 56 data bytes, press CTRL_C to break

Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=253 time=38 ms

Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=253 time=61 ms

Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=253 time=74 ms

Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=253 time=36 ms

Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=253 time=35 ms

--- 192.168.1.2 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 35/48/74 ms

The sample output shows that CE 1 and CE 2 can reach each other.

7. Verify the configuration.

Perform the display mpls lsp verbose command on PE 1. The output shows that the LSP with LspIndex 2050 is established by using RSVP-TE. It is the MPLS TE tunnel.

[PE1] display mpls lsp verbose

------------------------------------------------------------------

LSP Information: RSVP LSP

------------------------------------------------------------------

No : 1

IngressLsrID : 2.2.2.2

LocalLspID : 1

Tunnel-Interface : Tunnel1

Fec : 3.3.3.3/32

Nexthop : 10.0.0.2

In-Label : NULL

Out-Label : 1024

In-Interface : ----------

Out-Interface : Vlan-interface2

LspIndex : 2050

Tunnel ID : 0x22004

LsrType : Ingress

Bypass In Use : Not Exists

BypassTunnel : Tunnel Index[---]

Mpls-Mtu : 1500

------------------------------------------------------------------

LSP Information: BGP LSP

------------------------------------------------------------------

No : 2

VrfIndex : vpn1

Fec : 192.168.1.0/24

Nexthop : 192.168.1.1

In-Label : 1024

Out-Label : NULL

In-Interface : ----------

Out-Interface : ----------

LspIndex : 8193

Tunnel ID : 0x0

LsrType : Egress

Outgoing Tunnel ID : 0x0

Label Operation : POP

------------------------------------------------------------------

LSP Information: LDP LSP

------------------------------------------------------------------

No : 3

VrfIndex :

Fec : 2.2.2.2/32

Nexthop : 127.0.0.1

In-Label : 3

Out-Label : NULL

In-Interface : Vlan-interface2

Out-Interface : ----------

LspIndex : 10241

Tunnel ID : 0x0

LsrType : Egress

Outgoing Tunnel ID : 0x0

Label Operation : POP

No : 4

VrfIndex :

Fec : 3.3.3.3/32

Nexthop : 10.0.0.2

In-Label : NULL

Out-Label : 3

In-Interface : ----------

Out-Interface : Vlan-interface2

LspIndex : 10242

Tunnel ID 0x22000

LsrType : Ingress

Outgoing Tunnel ID : 0x0

Label Operation : PUSH

Perform the display interface tunnel command on PE 1. The output shows that traffic is being forwarded along the CR-LSP of the TE tunnel.

[PE1] display interface tunnel 1

Tunnel1 current state: UP

Line protocol current state: UP

Description: Tunnel1 Interface

The Maximum Transmit Unit is 1500

Internet Address is 12.1.1.1/24 Primary

Encapsulation is TUNNEL, service-loopback-group ID not set

Tunnel source unknown, destination 3.3.3.3

Tunnel protocol/transport CR_LSP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Last 300 seconds input: 5 bytes/sec, 0 packets/sec

Last 300 seconds output: 5 bytes/sec, 0 packets/sec

34 packets input, 2856 bytes

0 input error

34 packets output, 2856 bytes

0 output error

Troubleshooting MPLS TE

No TE LSA generated

Symptom

OSPF TE is configured but no TE LSAs can be generated to describe MPLS TE attributes.

Analysis

For TE LSAs to be generated, at least one OSPF neighbor must reach the FULL state.

Solution

1. Perform the display current-configuration command to check that MPLS TE is configured on involved interfaces.

2. Perform the debugging ospf mpls-te command to observe whether OSPF can receive the TE LINK establishment message.

3. Perform the display ospf peer command to check that OSPF neighbors are established correctly.

Swicthback fails to occur when the main tunnel resumes

Symptom

When data is transmitted along the protection tunnel, the main tunnel becomes normal but data still travels along the protection tunnel. In the output of the display mpls te protection tunnel command, the Switch Result field has a value of Protect-tunnel and the Work-tunnel defect state field has a value of No-defect.

Analysis

Possible reasons include:

· The reverting mode is non-revertive.

· The reverting delay period is relatively long.

· A switching command with higher priority forces data to travel along the protection tunnel.

Solution

1. Execute the display mpls te protection tunnel command. If the Mode field in the output is Non-revertive, the configuration defines that reverting should not occur. If you expect that protection switching will be triggered when the main tunnel recovers, you can configure the mpls te protection tunnel command in the main tunnel interface view to set the reverting mode as revertive.

2. If the Mode field is revertive and the WTR field is a non-zero value, the reverting delay timer has expired. When the timer expires, if the main tunnel still has no defect, data will be switched back to the main tunnel. If you hope the switchover occurs immediately when the main tunnel recovers, you can use the mpls te protection tunnel command to change the reverting delay time to 0.

3. If your case is neither 1) nor 2), check the The current switch command field in the output of the display mpls te protection tunnel command. If its value is Force, a switching action with a higher priority than the signal switching is configured. If you expect that signaling can trigger switchover when the main tunnel recovers, you can use the mpls te protect-switch clear command to clear all configured switching actions.

09-MPLS Configuration Guide

Configuring MPLS TE

MPLS TE overview

Traffic engineering and MPLS TE

Basic concepts

LSP tunnel

MPLS TE tunnel

MPLS TE implementation

Advertising TE attributes

Calculating paths

Establishing paths

Forwarding packets

CR-LSP

Strict and loose explicit routes

Traffic characteristics

Preemption

Route pinning

Administrative group and affinity attribute

Reoptimization

RSVP-TE

Overview

Basic concepts of RSVP-TE

Make-before-break

RSVP-TE messages

Setting up an LSP tunnel

RSVP refresh mechanism

PSB, RSB and BSB timeouts

RSVP-TE GR

Static routing

Automatic route advertisement

CR-LSP backup

FRR

Overview

Basic concepts

Protection

Deploying FRR

PS for an MPLS TE tunnel

Overview

Basic concepts

Working process

Protocols and standards

MPLS TE configuration task list

Configuring MPLS TE basic settings

Creating MPLS TE tunnel over static CR-LSP

Configuring MPLS TE tunnel with dynamic signaling protocol

Configuration procedure

Configuring MPLS TE properties for a link

Configuring CSPF

Configuring IS-IS TE

Configuring an MPLS TE explicit path

Configuring MPLS TE tunnel constraints

Establishing an MPLS TE tunnel with RSVP-TE

Configuring RSVP-TE advanced features

Configuring RSVP reservation style

Configuring RSVP state timers

Configuring the RSVP refreshing mechanism

Configuring the RSVP hello extension

Configuring RSVP-TE resource reservation confirmation

Configuring RSVP authentication

Configuring RSVP-TE GR

Tuning CR-LSP setup

Configuration prerequisites

Configuring the tie breaker in CSPF

Configuring route pinning

Configuring administrative group and affinity attribute

Configuring CR-LSP reoptimization

Tuning MPLS TE tunnel setup

Configuring loop detection

Configuring route and label recording

Configuring tunnel setup retry

Assigning priorities to a tunnel

Configuring traffic forwarding

Configuration prerequisites

Forwarding traffic along MPLS TE tunnels using static routes

Forwarding traffic along MPLS TE tunnels through automatic route advertisement

Configuring traffic forwarding tuning parameters

Configuring the failed link timer

Configuring flooding thresholds

Specifying the link metric type for tunnel path calculation

Configuring the traffic flow type of a tunnel