l A routing switch running MPLS has routing functions. The term “router” in this document refers to a router in a generic sense or a Layer 3 Ethernet switch running MPLS.

l For a S9500 Series routing switch, only line processor units (LPUs) with a suffix of C, CA or CB and VPLS service processor cards (SPCs) support MPLS. For S9500 Series routing switches to support MPLS VPN functions, you need to equip them with MPLS capable LPUs or VPLS SPCs. You can identify the suffix of an LPU by the silkscreen in the upper right corner of the LPU’s front panel. As an example, the silkscreen of an LSB1P4G8CA0 LPU is P4G8CA, and therefore the suffix of the LPU is CA.

When configuring multiprotocol path label switching traffic engineering (MPLS TE), go to these sections for information you are interested in:

l MPLS TE Overview

l MPLS TE Configuration Task List

l Displaying and Maintaining MPLS TE

l MPLS TE Configuration Example

l Troubleshooting MPLS TE

1.1 MPLS TE Overview

This section covers these topics:

l Traffic Engineering and MPLS TE

l Basic Concepts of MPLS TE

l MPLS TE Implementation

l CR-LSP

l CR-LDP

l RSVP-TE

l Traffic Forwarding

l CR-LSP Backup

l Fast Reroute

l Protocols and Standards

1.1.1 Traffic Engineering and MPLS TE

I. Traffic engineering

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 associated with TE can be either of the following:

l Traffic oriented. These are performance objectives that 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).

l Resource oriented. These are performance objectives that optimize resources utilization. Bandwidth is a crucial resource on networks. Efficiently managing it is one major task of TE.

1) TE solution

As existing interior gateway protocols (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.

II. MPLS TE

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

l MPLS supports explicit LSP routing.

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

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

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

l Reserve resources by establishing LSP tunnels to specific destinations. This allows traffic to bypass congested nodes to achieve appropriate load distribution.

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

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

1.1.2 Basic Concepts of MPLS TE

I. LSP tunnel

On an LSP, the nodes make forwarding decision for labeled packets based on label. The traffic thus is transparent to the transits nodes on the LSP. In this sense, an LSP can be regarded as a tunnel.

II. MPLS TE tunnel

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

1.1.3 MPLS TE Implementation

MPLS TE mainly accomplishes two functions:

l Static constraint-based routed LSP (CR-LSP) processing to create and remove static CR-LSPs. The bandwidth of LSPs must be configured manually.

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

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

II. 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. It is derived from SPF and makes calculation based on two conditions:

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

l TEDB

What CSPF does to identify the shortest path to an LSP egress is first pruning TE attribute incompliant links from the TEDB and then performing SPF calculation

III. Establishing paths

When setting up LSP tunnels, you may use two types of signaling: CR-LDP and RSVP-TE. Both can carry constraints such as LSP bandwidth, some explicit route information, and color and deliver the same function.

They are different in that CR-LDP establishes LSPs using TCP while RSVP-TE using raw IP.

RSVP is a well-established technology in terms of its architecture, protocol procedures and support to services; while CR-LDP is an emerging technology with better scalability.

& Note:

Currently, the device supports only RSVP-TE.

IV. Forwarding packets

Packets are forwarded over established tunnels.

1.1.4 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 these concepts:

l Strict and loose explicit routes

l Traffic characteristics

l Preemption

l Route pinning

l Administrative group and affinity attribute

l Reoptimization

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

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

III. Preemption

CR-LDP signals the resources required by a path on each hop of the route. If a route with sufficient resources cannot be found, existing paths may be rerouted to reallocate resources to the new path. This is called path preemption.

Two priorities, setup priority and holding priority, are assigned to paths 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 should not be set higher than its holding priority.

IV. 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 will be unable to identify from which part of the network the required bandwidth should be obtained when setting up a CR-LSP. In this case, loose explicit route (ER-hop) with required resources is used. The CR-LSP thus established 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.

V. Administrative group and affinity attribute

VI. 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 should traverse. If a better route is found for an existing CR-LSP, a new CR-LSP will be established to replace the old one, and services will be switched to the new CR-LSP.

1.1.5 CR-LDP

Constraint-based routed label distribution protocol (CR-LDP) is an extension to LDP. It is used in MPLS TE to create an explicit path with resource reservation between the ingress node and the egress node.

When initiating an LSP at the ingress, CR-LDP appends some constraints in the label request message.

& Note:

The S9500 series does not support CR-LDP.

1.1.6 RSVP-TE

This section covers these topics:

l Overview

l Basic concepts of RSVP-TE

l Make-before-break

l RSVP-TE messages

l Setting up an LSP tunnel

l RSVP refresh mechanism

l PSB, RSB and BSB timeouts

I. Overview

Currently, 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:

l Unidirectional

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

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

II. Basic concepts of RSVP-TE

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

2) 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 thus which LSPs can be used.

Currently, two reservation styles are available:

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

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

& Note:

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

III. Make-before-break

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

& Note:

Once you change the key attributes of an MPLS TE tunnel, such as the destination, priority, CT, and protocol, the device removes the MPLS TE tunnel and then re-establishes it, during which period the make-before-break mechanism does not take effect.

Figure 1-1 Diagram for make-before-break

Figure 1-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 will be 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.

IV. RSVP-TE messages

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

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

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

l PathTear messages: sent downstream immediately once created to remove the path state and related reservation state on each node along the path.

l ResvTear messages: sent upstream immediately once created to remove the reservation state on each node along the path.

l PathErr messages: sent upstream to report Path message processing errors to senders. They do not affect the state of the nodes along the path.

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

l ResvConf messages: sent to receivers to confirm Resv messages.

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

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

l 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 the object advertises the label binding using the LABEL object in the Resv message to the upstream node, thus accomplishing label advertisement and transmission.

V. Setting up an LSP tunnel

Figure 1-2 shows how to set up an LSP tunnel with RSVP:

Figure 1-2 Set 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 towards the egress LSR.

2) After receiving the Path message, the egress LSR sends back a Resv message towards the ingress LSR. 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.

VI. 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 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 as follows to address the problems:

1) 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, thus improving transmission reliability.

On an interface enabled with the Message_ID mechanism, you may configure RSVP message retransmission. After the interface sends an RSVP message, it waits for acknowledgement. If no ACK is received before the initial retransmission interval (Rf seconds for example) expires, the interface resends the message. After that, the interface resends the message at an exponentially increased retransmission interval equivalent to (1 + Delta) × Rf seconds.

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

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

You may sometimes want to store the resource reservation state for a reservation request that does not pass the admission control on some node. This however should not prevent the resources reserved for the request from being used by other requests. To handle this situation, 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 state in the BSB is removed.

1.1.7 Traffic Forwarding

For traffic to travel along an LSP tunnel, you need to make configuration after creating the MPLS TE tunnel. Otherwise, traffic will be 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 or automatic route advertisement.

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

II. 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 MPLS TE tunnels are considered point-to-point links and MPLS TE tunnel interfaces can be set as outgoing interfaces.

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

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

Figure 1-3 IGP shortcut and forwarding adjacency

As shown in Figure 1-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 known the presence of the TE tunnel and thus 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, consider the following:

l The tunnel destination address should be in the same area where the tunnel interface is located.

l The tunnel destination address should be reachable through intra-area routing.

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

Two approaches are available CR-LSP backup:

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

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

1.1.9 Fast Reroute

This section covers these topics:

I. Overview

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

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

II. Basic concepts

The following are concepts that FRR involves throughout this document:

l Primary LSP: The protected LSP.

l Bypass LSP: An LSP used to protect the primary LSP.

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

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

III. Protection

FRR provides link protection and node protection for an LSP as follows:

l 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 1-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 1-4 FRR link protection

l Node protection, where the PLR and the MP are connected through a router and the primary LSP traverses this device. When the device fails, traffic is switched to the bypass LSP. As shown in Figure 1-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 1-5 FRR node protection

IV. 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, you are recommended to use FRR for crucial interfaces or links only.

1.1.10 Protocols and Standards

l RFC 2702 Requirements for Traffic Engineering Over MPLS

l RFC 3212 Constraint-Based LSP Setup using LDP

l RFC 2205 Resource ReSerVation Protocol

l RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels

l RFC 2961 RSVP Refresh Overhead Reduction Extensions

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

1.2 MPLS TE Configuration Task List

Complete these tasks to configure MPLS TE:

Configuration task			Remarks
Configuring MPLS TE Basic Capabilities			Required
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 either approach
Configuring Traffic Forwarding		Forwarding traffic along MPLS TE tunnels through automatic route advertisement	Required Use either approach
Configuring Traffic Forwarding Tuning Parameters			Optional
Configuring CR-LSP Backup			Optional
Configuring FRR			Optional

1.3 Configuring MPLS TE Basic Capabilities

MPLS TE basic capabilities are essential to MPLS TE feature configurations. After configuring the basic capabilities, you need to make other configurations in order to use MPLS TE depending on the actual requirements.

1.3.1 Configuration Prerequisites

Before the configuration, do the following:

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

l Configure MPLS basic capabilities.

& Note:

For configuration information about MPLS basic capability, refer to MPLS Basics Configuration in MPLS VPN Volume.

1.3.2 Configuration procedure

Follow these steps to configure MPLS TE basic capabilities:

To do…	Use the command…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Enable global MPLS TE	mpls te	Required Disabled by default
Exit to system view	quit	––
Enter the interface view of an MPLS TE link	interface interface-type interface-number	––
Enable interface MPLS	mpls	Required
Enable interface MPLS TE	mpls te	Required Disabled by default
Exit to system view	quit	––
Create a tunnel interface and enter its view	interface tunnel tunnel-number	Required
Assign an IP address to the tunnel interface	ip address ip-address netmask	Required
Set the tunnel protocol to MPLS TE	tunnel-protocol mpls te	Required
Configure the destination address of the tunnel	destination ip-address	Required
Submit the current tunnel configuration	mpls te commit	Required

& Note:

Depending on the MPLS TE signaling protocol a tunnel uses, the basic capabilities you configured in this section may be inadequate for the tunnel to work and you may need to make extra configurations.

1.4 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. What you need to do is to 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 do not accept bandwidth constraints and cannot dynamically adapt to network changes.

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

1.4.1 Configuration Prerequisites

Before making the configuration, do the following:

l Configure static routing or an IGP protocol to make sure that all LSRs are reachable.

l Configure MPLS basic capabilities.

l Configure MPLS TE basic capabilities.

1.4.2 Configuration Procedure

Follow these steps to create an MPLS TE tunnel over a CR-LSP:

To do…		Use the command…	Remarks
Enter system view		system-view	––
Enter the interface view of an MPLS TE tunnel		interface tunnel tunnel-number	––
Configure the tunnel to use static CR-LSP		mpls te signal-protocol static	Required
Submit the current tunnel configuration		mpls te commit	Required
Exit to system view		quit	––
Create a static CR-LSP on your device depending on its location in the network	At the ingress	static-cr-lsp ingress tunnel-name destination dest-addr { nexthop next-hop-addr \| outgoing-interface interface-type interface-number } out-label out-label-value [ bandwidth [ bc0 \| bc1 ] bandwidth-value ]	Required Use any of the commands depending on the location of your device in the network.
	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 \| outgoing-interface interface-type interface-number } out-label out-label-value [ bandwidth [ bc0 \| bc1 ] bandwidth-value ]
	At the egress	static-cr-lsp egress tunnel-name incoming-interface interface-type interface-number in-label in-label-value

& Note:

l The tunnel-name argument specifies the name of the MPLS TE tunnel carried over the static CR-LSP.

l The tunnel-name argument in the static-cr-lsp ingress command is case sensitive. Suppose you create a tunnel interface with the interface tunnel 2/0/0 command. To specify it for the tunnel-name in the static-cr-lsp ingress command, you must input its name in the form of Tunnel2/0/0. Otherwise, your tunnel establishment attempt will fail. This restriction however does not apply to transit and egress nodes.

l The next hop address cannot be a local public address when configuring the static CR-LSP on the ingress or a transit node.

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

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

l Configure tunnel constraints.

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

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

1.5.1 Configuration Prerequisites

Before making the configuration, do the following:

l Configure static routing or an IGP protocol to make sure that all LSRs are reachable.

l Configure MPLS basic capabilities.

l Configure MPLS TE basic capabilities.

1.5.2 Configuration Procedure

Configuring an MPLS TE tunnel using a dynamic signaling protocol involves these tasks:

Configuration task	Remarks
Configuring MPLS TE properties for a link	Optional
Configuring OSPF TE	Optional
Configuring CSPF	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

I. Configuring MPLS TE properties for a link

Follow these steps to configure MPLS TE properties for a link:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
Configure maximum link bandwidth	mpls te max-link-bandwidth bandwidth-value [ bc1 bc1-bandwidth ]	Optional
Configure maximum reservable bandwidth of the MPLS TE link	mpls te max-reservable-bandwidth bandwidth-value [ bc1 bc1-bandwidth ]	Optional

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

Follow these steps to configure OSPF TE:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter OSPF view	ospf [ process-id ]	––
Enable the opaque LSA capability	opaque-capability enable	Required Disabled by default
Enter OSPF area view	area area-id	Required
Enable MPLS TE in the OSPF area	mpls-te enable	Required Disabled by default
Exit to OSPF view	quit	––

& Note:

For more information about OSPF opaque LSA, refer to OSPF Configuration in IP routing volume.

III. Configuring CSPF

Follow these steps to configure CSPF:

To do…	Use command to…	Remarks
Enter system view	system-view	—
Enter MPLS view	mpls	—
Enable CSPF on your device	mpls te cspf	Required Disabled by default

IV. 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, you need to configure the IS-IS wide metric style, which can be wide, compatible, or wide-compatible.

Follow these steps to configure IS-IS TE:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter IS-IS view	isis [ process-id ]	––
Configure the wide metric attribute of IS-IS	cost-style { narrow \| wide \| wide-compatible \| { compatible \| narrow-compatible } [ relax-spf-limit ] }	Required By default, IS-IS uses narrow metric style.
Enable IS-IS TE	traffic-eng [ level-1 \| level-2 \| level-1-2 ]	Required Disabled by default

& Note:

With the S9500 series, if you enable IS-IS TE on an interface configured with both primary and secondary IP addresses, IS-IS TE advertises only the primary IP address of the interface in the LSP’s IS reachability TLV (type 22).

V. 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 of the following:

l Strict: where the two nodes are directly connected.

l Loose: where 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.

Caution:

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

l 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 octets of LSP header and two octets of TLV header, cannot be less than 284 octets. If an LSP must also carry the authentication information, the minimum MTU needs to be recalculated according to the packet structure.

In a word, with the TE feature, the MTU of any interface with IS-IS enabled is recommended to be equal to or greater than 512 octets to guarantee that IS-IS LSPs can be flooded on the network.

Follow these steps to configure an MPLS TE explicit path:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Create an explicit path for MPLS TE tunneling and enter its view	explicit-path path-name [ enable \| disable ]	Required
Add a node to the explicit path	add hop ip-address1 [ include [ strict \| loose ] \| exclude ] { after \| before } ip-address2	Optional By default, the include keyword and the strict keyword apply. In other words, the explicit path traverses the specified node and the next node is a strict node.
Specify a next hop IP address on the explicit path	next hop ip-address [ include [ strict \| loose ] \| exclude ]	Required 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.
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. In other words, the explicit path traverses the specified node and the next node is a strict node.
Remove a node from the explicit path	delete hop ip-address	Optional
Display information about the specified or all nodes on the explicit path	list hop [ ip-address ]	Optional

VI. Configuring MPLS TE tunnel constraints

Follow these steps to configure MPLS TE tunnel constraints:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Assign bandwidth to the MPLS TE tunnel	mpls te bandwidth [ bc0 \| bc1 ] bandwidth	Optional No bandwidth is assigned by default.
Associate the tunnel with an explicit path	mpls te path explicit-path path-name	Required
Submit current tunnel configuration	mpls te commit	Required

VII. Establishing an MPLS TE tunnel with RSVP-TE

Follow these steps to establish an MPLS TE tunnel with RSVP-TE:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Enable RSVP-TE globally	mpls rsvp-te	Required Disabled by default
Exit to system view	quit	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
Enable RSVP-TE on the interface	mpls rsvp-te	Required Disabled by default
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
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.
Submit current tunnel configuration	mpls te commit	Required

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 interface for the tunnel to use.

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

1.6.1 Configuration Prerequisites

Before configuring RSVP-TE advanced features, do the following:

l Configure MPLS basic capabilities

l Configure MPLS TE basic capabilities

l Establish an MPLS TE tunnel with RSVP-TE

1.6.2 Configuration Procedure

Configuring RSVP-TE advanced features involves these tasks:

l Configuring RSVP reservation style

l Configuring RSVP state timers

l Configuring the RSVP refreshing mechanism

l Configuring the RSVP Hello extension

l Configuring RSVP-TE resource reservation confirmation

l Configuring RSVP authentication

I. Configuring RSVP reservation style

Currently, two reservation styles are available:

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

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

Follow these steps to configure RSVP reservation style:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Configure the resources reservation style for the tunnel	mpls te resv-style { ff \| se }	Optional The default resource reservation style is SE.
Submit current tunnel configuration	mpls te commit	Required

& Note:

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

II. Configuring RSVP state timers

Follow these steps to configure RSVP state timers:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
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.
Configure the keep multiplier for PSB and RSB	mpls rsvp-te keep-multiplier number	Optional The default is 3.
Configure the blockade timeout multiplier	mpls rsvp-te blockade-multiplier number	Optional The default blockade timeout multiplier is 4.
Submit current tunnel configuration	mpls te commit	Required

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

Follow these steps to configure RSVP refreshing mechanism:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
Enable the reliability mechanism of RSVP-TE	mpls rsvp-te reliability	Optional
Configure retransmission	mpls rsvp-te timer retransmission { increment-value [ increment-value ] \| retransmit-value [ retrans-timer-value ] } *	Optional Disabled by default
Enable summary refresh	mpls rsvp-te srefresh	Optional Disabled by default

IV. Configuring the RSVP Hello extension

Follow these steps to configure the RSVP hello extension:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Enable global RSVP hello extension	mpls rsvp-te hello	Required Disabled by default
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.
Configure the hello interval	mpls rsvp-te timer hello timevalue	Optional The default is 3 seconds.
Exit to system view	quit	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
Enable interface RSVP hello extension	mpls rsvp-te hello	Optional Disabled by default

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

V. Configuring RSVP-TE resource reservation confirmation

Follow these steps to configure RSVP-TE resource reservation confirmation:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Enable resource reservation confirmation	mpls rsvp-te resvconfirm	Required Disabled by default

& Note:

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

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

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

Follow these steps to configure RSVP authentication:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
Enable RSVP authentication	mpls rsvp-te authentication { cipher \| plain } auth-key	Required

& Note:

FRR and RSVP authentication cannot run at the same time.

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

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

1.7.2 Configuration Procedure

Tuning CR-LSP setup involves these tasks:

l Configuring the tie breaker in CSPF

l Configuring route pinning

l Configuring administrative group and affinity attribute

l Configuring CR-LSP reoptimization

I. 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 breakers include largest currently available bandwidth, least currently available bandwidth, or random selection.

Follow these steps to configure CSPF tie-breaking method:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Configure the tie breaker used when multiple paths are present in a CSPF calculation on the current node	mpls te tie-breaking { least-fill \| most-fill \| random }	Optional The random keyword applies by default.
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Configure the tie breaker used when multiple paths are present in a CSPF calculation for the current tunnel	mpls te tie-breaking { least-fill \| most-fill \| random }	Optional The random keyword applies by default.
Submit current tunnel configuration	mpls te commit	Required

& Note:

For a tunnel, the tie breaker configured in MPLS TE tunnel interface view is preferred to the one configured in MPLS view. If no tie breaker is configured in MPLS TE tunnel interface view, the one configured in MPLS view applies.

II. Configuring route pinning

Route pinning cannot be used together with reoptimization.

Follow these steps to configure route pinning:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Enable route pinning	mpls te route-pinning	Required Disabled by default
Submit current tunnel configuration	mpls te commit	Required.

III. 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 relationship between administrative groups and affinity attributes varies by vendor. To deploy devices from different vendors in the same network, acquaint yourself with the implementations of the vendors at first.

Follow these steps to configure the administrative group and affinity attribute:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
Assign the link to a link administrative group	mpls te link administrative group value	Optional The default is 0x00000000.
Exit to system view	quit	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
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.
Submit current tunnel configuration	mpls te commit	Required

IV. Configuring CR-LSP reoptimization

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

Follow these steps to configure CR-LSP reoptimization:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Configure reoptimization for the MPLS TE tunnel	mpls te reoptimization [ frequency seconds ]	Required Disabled by default
Submit current tunnel configuration	mpls te commit	Required
Exit to user view	return	––
Perform reoptimization on all MPLS TE tunnels with reoptimization enabled	mpls te reoptimization	Optional

1.8 Tuning MPLS TE Tunnel Setup

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

1.8.1 Configuration Prerequisites

The configurations described in this section need to be used together with the dynamic signaling protocol RSVP-TE.

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

1.8.2 Configuration Procedures

Tuning MPLS TE tunnel setup involves these tasks:

l Configuring loop detection

l Configuring route and label recording

l Configuring tunnel setup retry

l Assigning priorities to a tunnel

I. Configuring loop detection

Follow these steps to configure loop detection:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Enable the system to perform loop detection when setting up a tunnel	mpls te loop-detection	Required Disabled by default
Submit current tunnel configuration	mpls te commit	Required

II. Configuring route and label recording

Follow these steps to configure route and label recording:

To do…		Use command to…	Remarks
Enter system view		system-view	––
Enter MPLS TE tunnel interface view		interface tunnel tunnel-number	––
Enable the system to record routes or label bindings when setting up the tunnel	Record routes	mpls te record-route	Required Use either of the commands. Both route recording and label binding recording are disabled by default.
	Record routes and label bindings	mpls te record-route label
Submit current tunnel configuration		mpls te commit	Required

III. Configuring tunnel setup retry

With the tunnel setup retry interval and the maximum number of tunnel setup retries configured, the system will automatically try to set up the tunnel at the specified interval until the tunnel is setup or the specified maximum number of retries is reached.

Follow these steps to configure tunnel setup retry:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Configure the maximum number of tunnel setup retries	mpls te retry times	Optional The default is 5.
Configure the tunnel setup retry interval	mpls te timer retry seconds	Optional The default is 10 seconds.
Submit current tunnel configuration	mpls te commit	Required

IV. 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 should not be set higher than its holding priority.

Follow these steps to assign priorities to a tunnel:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Assign priorities to the tunnel	mpls te priority setup-priority [ hold-priority ]	Optional The default setup and holding priorities are 7.
Submit current tunnel configuration	mpls te commit	Required

1.9 Configuring Traffic Forwarding

1.9.1 Configuration Prerequisites

Before configuring traffic forwarding, do the following:

l Configure MPLS basic capabilities

l Configure MPLS TE basic capabilities

l Configure MPLS TE tunnels

1.9.2 Configuration Procedures

Configuring traffic forwarding involves these tasks:

l Forwarding traffic along MPLS TE tunnels using static routes

l Forwarding traffic along MPLS TE tunnels through automatic route advertisement

I. Forwarding traffic along MPLS TE tunnels using static routes

Follow these steps to create static routes for routing traffic along an MPLS TE tunnel:

To do…	Use command to…	Remarks
Enter system view	system-view	––
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 ]	Required

& 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, refer to Static Routing Commands in IP Routing Volume.

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

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.

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.

1) Configure IGP shortcut

Follow these steps to configure IGP shortcut:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
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 ]	Required 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 IS-IS by default.
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.
Submit current tunnel configuration	mpls te commit	Required
Exit to system view	quit	––
Enter IS-IS view	isis [ process-id ]	Configure one of the commands as needed.
Enter OSPF view	ospf [ process-id ]	Configure one of the commands as needed.
Enable the IGP shortcut function	enable traffic-adjustment	Required Disabled by default

2) Configure forwarding adjacency

Follow these steps to configure forwarding adjacency:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Enable IGP to advertise the route of the MPLS TE tunnel to IGP neighbors.	mpls te igp advertise [ hold-time value ]	Required Routes of MPLS TE tunnels are not advertised to IGP neighbors by default.
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.
Submit current tunnel configuration	mpls te commit	Required
Exit to system view	quit	––
Enter IS-IS view	isis [ process-id ]	Configure one of the commands as needed.
Enter OSPF view	ospf [ process-id ]	Configure one of the commands as needed.
Enable forwarding adjacency	enable traffic-adjustment advertise	Required Disabled by default

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

1.10.1 Configuration Prerequisites

The configurations described in this section are used in conjunction with CSPF and the dynamic signaling protocol RSVP-TE.

1.10.2 Configuration Procedure

Configuring traffic forwarding tuning parameters involves these tasks:

l Configuring the failed link timer

l Configuring flooding thresholds

l Configuring the link metric used for routing a tunnel

l Configuring the traffic flow type of a tunnel

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

Follow these steps to configure failed link timer:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Configure the CSPF failed link timer	mpls te cspf timer failed-link timer-interval	Optional The default is 10 seconds.

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

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

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

Follow these steps to configure flooding thresholds:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface interface-type interface-number	––
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.
Submit current tunnel configuration	mpls te commit	Required

III. Configuring the link metric used for routing a tunnel

For an MPLS TE link, you may assign it a TE metric. This TE metric or the IGP metric of the link is used for routing MPLS TE tunnels, depending on which metric type is specified.

Follow these steps to configure the link metric used for routing a tunnel:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Configure the link metric type used for routing TE tunnels without metric type	mpls te path metric-type { igp \| te }	Optional TE metrics of links are used by default.
Exit to system view	quit	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Configure the link metric type used for routing the tunnel	mpls te path metric-type { igp \| te }	Optional TE metric is used by default.
Submit current tunnel configuration	mpls te commit	Optional
Exit to system view	quit	––
Enter interface view of MPLS TE link	interface interface-type interface-number	––
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:

l The metric type configured in MPLS TE tunnel interface view takes priority over the one configured in MPLS view.

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

IV. Configuring the traffic flow type of a tunnel

Follow these steps to configure the traffic flow type of a tunnel:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
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.
Submit current tunnel configuration	mpls te commit	Required

1.11 Configuring CR-LSP Backup

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

1.11.1 Configuration Prerequisites

Before configuring CR-LSP backup, do the following:

l Configure MPLS basic capabilities

l Configure MPLS TE basic capabilities

l Configure MPLS TE tunnels

1.11.2 Configuration Procedure

Follow these steps to configure CR-LSP backup:

To do…	Use command to…	Remarks
Enter system view of the ingress node	system-view	––
Enter MPLS TE tunnel interface view	interface tunnel tunnel-number	––
Configure the backup mode used by the TE tunnel	mpls te backup { hot-standby \| ordinary }	Required Tunnel backup is disabled by default.
Submit current tunnel configuration	mpls te commit	Required

& Note:

CR-LSP backup should be configured at the ingress node of a tunnel. The system routes the primary LSP and backup LSP automatically. You do not need to configure them.

1.12 Configuring FRR

As mentioned earlier, fast reroute (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.

A bypass LSP can protect more than one physical interface other than its own outgoing interface. An interface can be protected by more than one bypass LSP. The number of bypass LSPs depends on the size of the system memory.

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 used 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 forward data traffic while protecting the primary tunnel, you need to ensure that bypass tunnels are available with adequate bandwidth.

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

1.12.1 Configuration Prerequisites

Before configuring FRR, do the following:

l Configure IGP, ensuring that all LSRs are reachable

l Configure MPLS basic capabilities

l Configure MPLS TE basic capabilities

l Establish an MPLS TE tunnel with RSVP-TE

l Set up primary LSPs

1.12.2 Configuration Procedure

Configuring FRR involves these tasks:

l Enabling FRR on the headend of a primary LSP

l Configuring a bypass tunnel on its PLR

l Configuring node protection

l Configuring the FRR polling timer

I. Enabling FRR on the headend of a primary LSP

Follow these steps to enable FRR on the headend of a primary LSP:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter tunnel interface view of the primary LSP	interface tunnel tunnel-number	––
Enable FRR	mpls te fast-reroute	Required Disabled by default
Submit current tunnel configuration	mpls te commit	Required

II. Configuring a bypass tunnel on its PLR

After a tunnel is specified to protect an interface, its corresponding LSP becomes a bypass LSP. Setting up a bypass LSP must be manually performed on its headend, also called point of local repair (PLR), which must be a part of the primary LSP but must not be the tail of the primary LSP.

Configuring a bypass LSP is the same as configuring a common LSP except that you cannot configure the FRR attribute on a bypass LSP. In other words, an LSP cannot be both primary and bypass. In addition, nested LSP protection is not allowed.

When specifying a bypass tunnel for an interface, make sure that:

l The bypass tunnel is up.

l The protected interface is not the outgoing interface on the next hop along the route.

Up to three bypass tunnels can be specified for a protected interface. The best-fit algorithm is used to determine which of them should be 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 specified value.

Follow these steps to configure a bypass tunnel on its PLR:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter interface view of the bypass tunnel	interface tunnel tunnel-number	––
Specify the destination of the bypass tunnel	destination ip-address	Required l To configure node protection, specify the LSR ID of the next hop of the PLR’s next hop as the destination. l To configure link protection, specify the LSR ID of the PLR’s next hop as the destination.
Configure the bandwidth and type of LSP that the bypass tunnel can protect	mpls te backup bandwidth { bandwidth \| { bc0 \| bc1 } { bandwidth \| un-limited } }	Required Bandwidth is not protected by default.
Submit current tunnel configuration	mpls te commit	Required
Exit to system view	quit	––
Enter interface view of the outgoing interface of the protected LSP	interface interface-type interface-number	––
Bind the bypass tunnel with the protected interface	mpls te fast-reroute bypass-tunnel tunnel tunnel-number	Required

Caution:

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

III. Configuring node protection

Perform these configurations on the PLR and the node to be protected only when you want to use FRR for node protection.

Follow these steps to configure node protection:

To do…	Use command to…	Remarks
Enter system view	system-view	––
Enter MPLS view	mpls	––
Enable RSVP hello extension on current node	mpls rsvp-te hello	Required Disabled by default
Exit to system view	quit	––
Enter the view of the interface directly connected to the protected node or PLR	interface interface-type interface-number	––
Enable RSVP hello extension on the interface	mpls rsvp-te hello	Required 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.

IV. Configuring the FRR polling timer

After an FRR protection switch, if the protected LSP comes back into service or a new LSP is established, the traffic will be switched back to the original LSP or the newly established LSP. Then, the PLR scans regularly for a bypass LSP. If it finds a bypass LSP, it will refresh the binding.

Follow these steps to configure the FRR polling timer:

To do…	Use command to…	Remarks
Enter system view of the PLR node	system-view	––
Enter MPLS view	mpls	––
Configure the FRR polling timer	mpls te timer fast-reroute [ second ]	Optional The FRR polling timer is 300 seconds by default.

1.13 Displaying and Maintaining MPLS TE

To do…	Use the command…	Remarks
Display information about explicit paths	display explicit-path [ pathname ]	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 ]	Available in any view
Display RSVP-TE configuration	display mpls rsvp-te [ interface [ interface-type interface-number ] [ \| { begin \| include \| exclude } regular-expression ] ]	Available in any view
Display global or interface RSVP-TE information	display mpls rsvp-te established [ interface interface-type interface-number ] [ \| { begin \| include \| exclude } regular-expression ]	Available in any view
Display RSVP-TE neighbors	display mpls rsvp-te peer [ interface interface-type interface-number ] [ \| { begin \| include \| exclude } regular-expression ]	Available in any view
Display information about RSVP requests	display mpls rsvp-te request [ interface interface-type interface-number ] [ \| { begin \| include \| exclude } regular-expression ]	Available in any view
Display information about RSVP resource reservation	display mpls rsvp-te reservation [ interface interface-type interface-number ] [ \| { begin \| include \| exclude } 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 \| include \| exclude } 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 \| include \| exclude } text ]	Available in any view
Display information about RSVP sender messages	display mpls rsvp-te sender [ interface interface-type interface-number ] [ \| { begin \| include \| exclude } regular-expression ]	Available in any view
Display statistics about RSVP-TE	display mpls rsvp-te statistics { global \| interface [ interface-type interface-number ] }	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 \| include \| exclude } 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 ]	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 ]	Available in any view
Display information bout 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 ]	Available in any view
Display the path attributes of MPLS TE tunnels on this node	display mpls te tunnel path [ tunnel-name tunnel-name ] [ lsp-id lsr-id lsp-id ]	Available in any view
Display tunnel statistics	display mpls te tunnel statistics	Available in any view
Display statistics about MPLS TE tunnels	display mpls te tunnel-interface	Available in any view
Display the information of the specified or all OSPF processes about traffic tuning.	display ospf [ process-id ] traffic-adjustment	Available in any view
Display information about OSPF TE	display ospf [ process-id ] mpls-te [ area area-id ] [ self-originated ]	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 ]	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 ]	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 ]	Available in any view
Display statistics about TE for IS-IS	display isis traffic-eng statistics [ process-id \| vpn-instance vpn-instance-name ]	Available in any view
Display information about tunnels	display tunnel-info { tunnel-id \| all \| statistics }	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

1.14 MPLS TE Configuration Example

1.14.1 MPLS TE Using Static CR-LSP Configuration Example

I. Network requirements

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

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

II. Network diagram

Figure 1-6 Set up MPLS TE tunnels using static CR-LSPs

III. Configuration procedure

1) Assign IP addresses and masks to interfaces (see Figure 1-6)

Omitted

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 1

[SwitchA-LoopBack1] isis enable 1

[SwitchA-LoopBack1] 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 1

[SwitchB-LoopBack1] isis enable 1

[SwitchB-LoopBack1] 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 1

[SwitchC-LoopBack1] isis enable 1

[SwitchC-LoopBack1] quit

Perform the display ip routing-table command on each switch. You can see that all nodes learnt 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 capabilities

# 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 3/0/0

[SwitchA-Tunnel3/0/0] ip address 6.1.1.1 255.255.255.0

[SwitchA-Tunnel3/0/0] tunnel-protocol mpls te

[SwitchA-Tunnel3/0/0] destination 3.3.3.3

[SwitchA-Tunnel3/0/0] mpls te signal-protocol static

[SwitchA-Tunnel3/0/0] mpls te commit

[SwitchA-Tunnel3/0/0] quit

5) Create a static CR-LSP

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

[SwitchA] static-cr-lsp ingress Tunnel3/0/0 destination 3.3.3.3 nexthop 2.1.1.2 out-label 20

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

[SwitchB] static-cr-lsp transit Tunnel3/0/0 incoming-interface Vlan-interface 1 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 Tunnel3/0/0 incoming-interface Vlan-interface 2 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

Tunnel3/0/0 current state : UP

Line protocol current state : UP

Description : Tunnel3/0/0 Interface

The Maximum Transmit Unit is 1500

Internet Address is 6.1.1.1/24 Primary

Encapsulation is TUNNEL, aggregation ID not set

Tunnel source unknown, destination 3.3.3.3

Tunnel protocol/transport CR_LSP

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 Tunnel3/0/0

[SwitchB] display mpls te tunnel

LSP-Id Destination In/Out-If Name

- - Vlan1/Vlan2 Tunnel3/0/0

[SwitchC] display mpls te tunnel

LSP-Id Destination In/Out-If Name

- - Vlan2/- Tunnel3/0/0

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 Vlan2/-

[SwitchA] display mpls static-cr-lsp

Name FEC I/O Label I/O If Stat

Tunnel3/0/0 3.3.3.3/32 NULL/20 -/Vlan1 Up

[SwitchB] display mpls static-cr-lsp

Name FEC I/O Label I/O If Stat

Tunnel3/0/0 -/- 20/30 Vlan1/Vlan2 Up

[SwitchC] display mpls static-cr-lsp

Name FEC I/O Label I/O If Stat

Tunnel3/0/0 -/- 30/NULL Vlan2/- Up

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.

1.14.2 MPLS TE Using RSVP-TE Configuration Example

I. Network requirements

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

l Use RSVP-TE to create a TE tunnel with 20 kbps of bandwidth from Switch A to Switch D, ensuring that the maximum bandwidth of each link that the tunnel traverses is 100 kbps and the maximum reservable bandwidth is 50 kbps.

II. Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loopback1	1.1.1.9/32	Switch D	Loopback1	4.4.4.9/32
	Vlan-int1	10.1.1.1/24		Vlan-int3	30.1.1.2/24
Switch B	Loopback1	2.2.2.9/32	Switch C	Loopback1	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

Figure 1-7 Set up MPLS TE tunnels using RSVP-TE

III. Configuration procedure

1) Assign IP addresses and masks to interfaces (see Figure 1-7)

Omitted

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 1

[SwitchA-LoopBack1] isis enable 1

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

[SwitchA-LoopBack1] 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 1

[SwitchB-LoopBack1] isis enable 1

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

[SwitchB-LoopBack1] 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 1

[SwitchC-LoopBack1] isis enable 1

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

[SwitchC-LoopBack1] 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 1

[SwitchD-LoopBack1] isis enable 1

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

[SwitchD-LoopBack1] quit

Perform the display ip routing-table command on each switch. You can see that all nodes learnt 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 capabilities, 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-interface1] 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-1-2

[SwitchA-isis-1] quit

# Configure Switch B.

[SwitchB] isis 1

[SwitchB-isis-1] cost-style wide

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

[SwitchB-isis-1] quit

# Configure Switch C.

[SwitchC] isis 1

[SwitchC-isis-1] cost-style wide

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

[SwitchC-isis-1] quit

# Configure Switch D.

[SwitchD] isis 1

[SwitchD-isis-1] cost-style wide

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

[SwitchD-isis-1] quit

5) Configure MPLS TE attributes of links

# Configure maximum link bandwidth and maximum reservable bandwidth on Switch A.

[SwitchA] interface vlan-interface 1

[SwitchA-Vlan-interface1] mpls te max-link-bandwidth 100

[SwitchA-Vlan-interface1] mpls te max-reservable-bandwidth 50

[SwitchA-Vlan-interface1] quit

# Configure maximum link bandwidth and maximum reservable bandwidth on Switch B.

[SwitchB] interface vlan-interface 1

[SwitchB-Vlan-interface1] mpls te max-link-bandwidth 100

[SwitchB-Vlan-interface1] mpls te max-reservable-bandwidth 50

[SwitchB-Vlan-interface1] quit

[SwitchB] interface vlan-interface 2

[SwitchB-Vlan-interface2] mpls te max-link-bandwidth 100

[SwitchB-Vlan-interface2] mpls te max-reservable-bandwidth 50

[SwitchB-Vlan-interface2] quit

# Configure maximum link bandwidth and maximum reservable bandwidth on Switch C.

[SwitchC] interface vlan-interface 3

[SwitchC-Vlan-interface3] mpls te max-link-bandwidth 100

[SwitchC-Vlan-interface3] mpls te max-reservable-bandwidth 50

[SwitchC-Vlan-interface3] quit

[SwitchC] interface vlan-interface 2

[SwitchC-Vlan-interface2] mpls te max-link-bandwidth 100

[SwitchC-Vlan-interface2] mpls te max-reservable-bandwidth 50

[SwitchC-Vlan-interface2] quit

# Configure maximum link bandwidth and maximum reservable bandwidth on Switch D.

[SwitchD] interface vlan-interface 3

[SwitchD-Vlan-interface3] mpls te max-link-bandwidth 100

[SwitchD-Vlan-interface3] mpls te max-reservable-bandwidth 50

[SwitchD-Vlan-interface3] quit

6) Create an MPLS TE tunnel

# Create an MPLS TE tunnel on Switch A.

[SwitchA] interface Tunnel 3/0/1

[SwitchA-Tunnel3/0/1] ip address 7.1.1.1 255.255.255.0

[SwitchA-Tunnel3/0/1] tunnel-protocol mpls te

[SwitchA-Tunnel3/0/1] destination 4.4.4.9

[SwitchA-Tunnel3/0/1] mpls te bandwidth 20

[SwitchA-Tunnel3/0/1] mpls te commit

[SwitchA-Tunnel3/0/1] quit

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

Tunnel3/0/1 current state: UP

Line protocol current state: UP

Description: Tunnel3/0/1 Interface

The Maximum Transmit Unit is 1500

Internet Address is 7.1.1.1/24 Primary

Encapsulation is TUNNEL, aggregation ID not set

Tunnel source unknown, destination 4.4.4.9

Tunnel protocol/transport CR_LSP

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 : Tunnel3/0/1

Tunnel Desc : Tunnel3/0/1 Interface

Tunnel State Desc : CR-LSP is Up

Tunnel Attributes :

LSP ID : 1.1.1.9:1

Session ID : 0

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 : CLASS 0 Tunnel BW : 20 kbps

Reserved BW : 20 kbps

Setup Priority : 7 Hold Priority: 7

Affinity Prop/Mask : 0x0/0x0

Explicit Path Name : -

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

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: 512 Maximum Link Supported: 2048

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

Id Router-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

1.14.3 CR-LSP Backup Configuration Example

I. Network requirements

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

II. Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loopback1	1.1.1.9/32	Switch D	Loopback1	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	Loopback1	2.2.2.9/32	Switch C	Loopback1	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

Figure 1-8 CR-LSP backup

III. Configuration procedure

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

Omitted

2) Configure the IGP protocol

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

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

3) Configure MPLS TE basic capabilities, 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

[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 3/0/1

[SwitchA-Tunnel3/0/1] ip address 7.1.1.1 255.255.255.0

[SwitchA-Tunnel3/0/1] tunnel-protocol mpls te

[SwitchA-Tunnel3/0/1] destination 3.3.3.9

# Enable hot LSP backup.

[SwitchA-Tunnel3/0/1] mpls te backup hot-standby

[SwitchA-Tunnel3/0/1] mpls te commit

[SwitchA-Tunnel3/0/1] quit

Perform the display interface tunnel command on Switch A. You can find that Tunnel 3/0/1 is up.

[SwitchA] display interface tunnel

Tunnel3/0/1 current state: UP

Line protocol current state: UP

Description: Tunnel3/0/1 Interface

The Maximum Transmit Unit is 1500

Internet Address is 9.1.1.1/24 Primary

Encapsulation is TUNNEL, aggregation ID not set

Tunnel source unknown, destination 3.3.3.9

Tunnel protocol/transport CR_LSP

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 find that two tunnels are present with the outgoing interfaces 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:1024 3.3.3.9 -/Vlan1 Tunnel3/0/1

1.1.1.9:2048 3.3.3.9 -/Vlan4 Tunnel3/0/1

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 : Tunnel3/0/1

Lsp ID : 1.1.1.9 :1024

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 : Tunnel3/0/1

Lsp ID : 1.1.1.9 :2048

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 Vlan2 on Switch B. Perform the tracert command on Switch A to draw the path to the tunnel destination. You can see 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 find 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:2048 3.3.3.9 -/vlan2 Tunnel3/0/1

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

1.14.4 FRR Configuration Example

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

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

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

II. Network diagram

Device	Interface	IP address	Device	Interface	IP address
Switch A	Loopback1	1.1.1.1/32	Switch E	Loopback1	5.5.5.5/32
	Vlan-int1	2.1.1.1/24		Vlan-int4	3.2.1.2/24
Switch B	Loopback1	2.2.2.2/32		Vlan-int5	3.3.1.1/24
	Vlan-int1	2.1.1.2/24	Switch C	Loopback1	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	Loopback1	4.4.4.4/32		Vlan-int5	3.3.1.2/24
	Vlan-int3	4.1.1.2/24

Figure 1-9 Link protection using the FRR approach

III. Configuration procedure

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

Omitted

2) Configure the IGP protocol

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

Perform the display ip routing-table command on each switch. You should see that all nodes learnt 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 capabilities, and enable RSVP-TE.

# Configure Switch A.

[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 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] 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 headend 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] quit

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

[SwitchA] interface Tunnel 3/0/4

[SwitchA-Tunnel3/0/4] ip address 10.1.1.1 255.255.255.0

[SwitchA-Tunnel3/0/4] tunnel-protocol mpls te

[SwitchA-Tunnel3/0/4] destination 4.4.4.4

[SwitchA-Tunnel3/0/4] mpls te path explicit-path pri-path

# Enable FRR.

[SwitchA-Tunnel3/0/4] mpls te fast-reroute

[SwitchA-Tunnel3/0/4] mpls te commit

[SwitchA-Tunnel3/0/4] quit

Perform the display interface tunnel command on Switch A. You can find that Tunnel 3/0/4 is up.

[SwitchA] display interface tunnel

Tunnel3/0/4 current state: UP

Line protocol current state: UP

Description: Tunnel3/0/4 Interface

The Maximum Transmit Unit is 1500

Internet Address is 10.1.1.1/24 Primary

Encapsulation is TUNNEL, aggregation ID not set

Tunnel source unknown, destination 4.4.4.4

Tunnel protocol/transport CR_LSP

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 : Tunnel3/0/4

Tunnel Desc : Tunnel3/0/4 Interface

Tunnel State Desc : CR-LSP is Up

Tunnel Attributes :

LSP ID : 1.1.1.1:1

Session ID : 0

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 : CLASS 0 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

Loop Detection : Disabled

Record Route : Enabled Record Label : Enabled

FRR Flag : Enabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 5 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

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

# Create the bypass tunnel.

[SwitchB] interface Tunnel 3/0/5

[SwitchB-Tunnel3/0/5] ip address 11.1.1.1 255.255.255.0

[SwitchB-Tunnel3/0/5] tunnel-protocol mpls te

[SwitchB-Tunnel3/0/5] destination 3.3.3.3

[SwitchB-Tunnel3/0/5] mpls te path explicit-path by-path

# Configure the bandwidth that the bypass tunnel protects.

[SwitchB-Tunnel3/0/5] mpls te backup bandwidth 10000

[SwitchB-Tunnel3/0/5] mpls te commit

[SwitchB-Tunnel3/0/5] quit

# Bind the bypass tunnel with the protected interface.

[SwitchB] interface Vlan-interface 2

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

[SwitchB-Vlan-interface2] quit

Perform the display interface tunnel command on Switch B. You can find that Tunnel 3/0/5 is up.

Perform the display mpls lsp command on each switch. You can find 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 -/Vlan4

[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 find 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 Tunnel3/0/4

[SwitchB] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 Vlan1/Vlan2 Tunnel3/0/4

2.2.2.2:1 3.3.3.3 -/Vlan4 Tunnel3/0/5

[SwitchC] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 Vlan2/Vlan3 Tunnel3/0/4

2.2.2.2:1 3.3.3.3 Vlan5/- Tunnel3/0/5

[SwitchD] display mpls te tunnel

LSP-Id Destination In/Out-If Name

1.1.1.1:1 4.4.4.4 Vlan3/- Tunnel3/0/4

[SwitchE] display mpls te tunnel

LSP-Id Destination In/Out-If Name

2.2.2.2:1 3.3.3.3 Vlan4/Vlan5 Tunnel3/0/5

Perform the display mpls lsp verbose command on Switch B. You can find 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 : Tunnel3/0/4

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

Token : 22001

LsrType : Transit

Bypass In Use : Not Used

BypassTunnel : Tunnel Index[Tunnel3/0/5], InnerLabel[1024]

Mpls-Mtu : 1500

No : 2

IngressLsrID : 2.2.2.2

LocalLspID : 1

Tunnel-Interface : Tunnel3/0/5

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

Token : 22002

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

%Mar 28 21:07:46:623 2007 SwitchB IFNET/4/LINK UPDOWN: Vlan-interface2: link status is DOWN

%Mar 28 21:07:46:735 2007 SwitchB IFNET/4/UPDOWN: Line protocol on the interface Vlan-interface2 is DOWN

Perform the display interface tunnel command on Switch A to identify the state of the primary LSP. You can find 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 : Tunnel3/0/4

Tunnel Desc : Tunnel3/0/4 Interface

Tunnel State Desc : Modifying CR-LSP is setting up

Tunnel Attributes :

LSP ID : 1.1.1.1:1

Session ID : 0

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 : CLASS 0 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

Loop Detection : Disabled

Record Route : Enabled Record Label : Enabled

FRR Flag : Enabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 5 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 Name : Tunnel3/0/4

Tunnel Desc : Tunnel3/0/4 Interface

Tunnel State Desc : Modifying CR-LSP is setting up

Tunnel Attributes :

LSP ID : 1.1.1.1:1025

Session ID : 0

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 : CLASS 0 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

Loop Detection : Disabled

Record Route : Enabled Record Label : Enabled

FRR Flag : Enabled BackUpBW Flag: Not Supported

BackUpBW Type : - BackUpBW : -

Route Pinning : Disabled

Retry Limit : 5 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

& 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. 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 find 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 : Tunnel3/0/4

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

Token : 22001

LsrType : Transit

Bypass In Use : In Use

BypassTunnel : Tunnel Index[Tunnel3/0/5], InnerLabel[1024]

Mpls-Mtu : 1500

No : 2

IngressLsrID : 2.2.2.2

LocalLspID : 1

Tunnel-Interface : Tunnel3/0/5

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

Token : 22002

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

%Mar 28 21:09:06:860 2007 SwitchB IFNET/4/LINK UPDOWN: Vlan-interface2: link status is UP

%Mar 28 21:09:06:966 2007 SwitchB IFNET/4/UPDOWN: Line protocol on the interface Vlan-interface2 is UP

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

About 5 seconds later, perform the display mpls lsp verbose command on Switch B. You can find that Tunnel 3/0/5 is still bound with interface Vlan-interface 2 and is unused.

1.14.5 MPLS TE in MPLS L3VPN Configuration Example

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

l Set up an MPLS TE tunnel to forward the VPN traffic from PE 1 to PE 2.

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

II. Network diagram

Figure 1-10 MPLS TE application in VPN

III. Configuration procedure

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

# Configure PE 1.

[PE1] interface loopback 1

[PE1-LoopBack1] ip address 2.2.2.2 255.255.255.255

[PE1-LoopBack1] quit

[PE1] interface pos 5/1

[PE1-POS5/1] ip address 10.0.0.1 255.255.255.0

[PE1-POS5/1] 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] interface loopback 1

[PE2-LoopBack1] ip address 3.3.3.3 255.255.255.255

[PE2-LoopBack1] 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 should be able to establish the OSPF neighborship. Perform the display ospf peer command; you should see that the neighborship state is FULL. Perform the display ip routing-table command; you should see that the PEs learnt the routes to the loopback interfaces of each other. Take PE 1 for example:

[PE1] display ospf peer

OSPF Process 1 with Router ID 2.2.2.2

Neighbor Brief Information

Area: 0.0.0.0

Router ID Address Pri Dead-Time Interface State

3.3.3.3 10.0.0.2 1 30 Vlan2 Full/DR

[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 MPLS basic capabilities and LDP.

# Configure PE 1.

[PE1] mpls lsr-id 2.2.2.2

[PE1] mpls

[PE1-mpls] lsp-trigger all

[PE1-mpls] quit

[PE1] mpls ldp

[PE1-mpls-ldp] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] mpls

[PE1-Vlan-interface2] mpls ldp

[PE1-Vlan-interface2] quit

# Configure PE 2.

[PE2] mpls lsr-id 3.3.3.3

[PE2] mpls

[PE2-mpls] lsp-trigger all

[PE2-mpls] quit

[PE2] mpls ldp

[PE2-mpls-ldp] quit

[PE2] interface vlan-interface 2

[PE2-Vlan-interface2] mpls

[PE2-Vlan-interface2] mpls ldp

[PE2-Vlan-interface2] quit

After you complete the configuration, PEs should be able to set up LDP sessions. Perform the display mpls ldp session command; you should see that the session state is operational. Take PE 1 for example:

[PE1] display mpls ldp session

LDP Session(s) in Public Network

Total number of sessions: 1

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

Peer-ID Status LAM SsnRole FT MD5 KA-Sent/Rcv

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

3.3.3.3:0 Operational DU Passive Off Off 2/2

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

LAM : Label Advertisement Mode FT : Fault Tolerance

3) Enable MPLS TE, CSPF and OSPF TE

# Configure PE 1.

[PE1] mpls

[PE1-mpls] mpls te

[PE1-mpls] mpls te cspf

[PE1-mpls] quit

[PE1] interface vlan-interface 2

[PE1-Vlan-interface2] mpls te

[PE1-Vlan-interface2] quit

[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] mpls

[PE2-mpls] mpls te

[PE2-mpls] mpls te cspf

[PE2-mpls] quit

[PE2] interface vlan-interface 2

[PE2-Vlan-interface2] mpls te

[PE2-Vlan-interface2] quit

[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 headend and PE 2 as the tail. The signaling protocol is RSVP-TE.

[PE1] interface tunnel 3/0/6

[PE1-Tunnel3/0/6] ip address 12.1.1.1 255.255.255.0

[PE1-Tunnel3/0/6] tunnel-protocol mpls te

[PE1-Tunnel3/0/6] destination 3.3.3.3

[PE1-Tunnel3/0/6] mpls te signal-protocol rsvp-te

[PE1-Tunnel3/0/6] mpls te commit

[PE1-Tunnel3/0/6] 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] 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] 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 : 2007/03/31 16:58:59

Up time : 0 days, 00 hours, 00 minutes and 35 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 loopback1

[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 EGBP 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 1

[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. You can see 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

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

[PE1-bgp] display bgp vpnv4 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

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

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. You can find an LSP with LspIndex 2050. This is the LSP, that is, the MPLS TE tunnel, established using RSVP-TE.

[PE1] display mpls lsp verbose

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

LSP Information: RSVP LSP

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

No : 1

IngressLsrID : 2.2.2.2

LocalLspID : 1

Tunnel-Interface : Tunnel3/0/6

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

Token : 22004

LsrType : Ingress

Bypass In Use : Not Exists

BypassTunnel : Tunnel Index[---]

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

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

Token : 0

LsrType : Egress

Outgoing token : 0

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

Token : 0

LsrType : Egress

Outgoing token : 0

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

Token : 22000

LsrType : Ingress

Outgoing token : 0

Label Operation : PUSH

1.15 Troubleshooting MPLS TE

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.

H3C S9500 Operation Manual-Release2132[V2.03]-05 MPLS VPN Volume

Chapter 1 MPLS TE Configuration

1.1 MPLS TE Overview

1.1.1 Traffic Engineering and MPLS TE

I. Traffic engineering

II. MPLS TE

1.1.2 Basic Concepts of MPLS TE

I. LSP tunnel

II. MPLS TE tunnel

1.1.3 MPLS TE Implementation

I. Advertising TE attributes

II. Calculating paths

III. Establishing paths

IV. Forwarding packets

1.1.4 CR-LSP

I. Strict and loose explicit routes

II. Traffic characteristics

III. Preemption

IV. Route pinning

V. Administrative group and affinity attribute

VI. Reoptimization

1.1.5 CR-LDP

1.1.6 RSVP-TE

I. Overview

II. Basic concepts of RSVP-TE

III. Make-before-break

IV. RSVP-TE messages

V. Setting up an LSP tunnel

VI. RSVP refresh mechanism

VII. PSB, RSB and BSB timeouts

1.1.7 Traffic Forwarding

I. Static routing

II. Automatic route advertisement

1.1.8 CR-LSP Backup

1.1.9 Fast Reroute

I. Overview

II. Basic concepts

III. Protection

IV. Deploying FRR

1.1.10 Protocols and Standards

1.2 MPLS TE Configuration Task List

1.3 Configuring MPLS TE Basic Capabilities

1.4 Creating MPLS TE Tunnel over Static CR-LSP

1.5 Configuring MPLS TE Tunnel with Dynamic Signaling Protocol

1.5.2 Configuration Procedure

I. Configuring MPLS TE properties for a link

II. Configuring OSPF TE

III. Configuring CSPF

V. Configuring an MPLS TE explicit path

VI. Configuring MPLS TE tunnel constraints

VII. Establishing an MPLS TE tunnel with RSVP-TE

1.6 Configuring RSVP-TE Advanced Features

I. Configuring RSVP reservation style

II. Configuring RSVP state timers

III. Configuring the RSVP refreshing mechanism

IV. Configuring the RSVP Hello extension

V. Configuring RSVP-TE resource reservation confirmation

VI. Configuring RSVP authentication

1.7 Tuning CR-LSP Setup

1.7.1 Configuration Prerequisites

I. Configuring the tie breaker in CSPF

II. Configuring route pinning

III. Configuring administrative group and affinity attribute

IV. Configuring CR-LSP reoptimization

1.8 Tuning MPLS TE Tunnel Setup

I. Configuring loop detection

II. Configuring route and label recording

III. Configuring tunnel setup retry

IV. Assigning priorities to a tunnel

1.9 Configuring Traffic Forwarding

1.9.1 Configuration Prerequisites

I. Forwarding traffic along MPLS TE tunnels using static routes

II. Forwarding traffic along MPLS TE tunnels through automatic route advertisement

1.10 Configuring Traffic Forwarding Tuning Parameters

I. Configuring the failed link timer

II. Configuring flooding thresholds

III. Configuring the link metric used for routing a tunnel

IV. Configuring the traffic flow type of a tunnel

1.11 Configuring CR-LSP Backup

1.12 Configuring FRR