Note If you plan to use or already use Multiprotocol Label Switching (MPLS) TE FRR Link Protection before Cisco IOS Release 12.0(24)S, contact the Cisco Technical Assistance Center for important deployment and upgrade information.

Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

•Backup tunnel headend and tailend routers must implement FRR as described in this document.

•Backup tunnels are not protected. If an LSP is actively using a backup tunnel and the backup tunnel fails, the LSP is torn down.

•LSPs that are actively using backup tunnels are not considered for promotion. So, if an LSP is actively using a backup tunnel and a better backup tunnel becomes available, the active LSP is not switched to the better backup tunnel.

Fast ReRoute

Fast ReRoute (FRR) is a mechanism for protecting MPLS TE LSPs from link and node failures by locally repairing the LSPs at the point of failure, allowing data to continue to flow on them while their headend routers attempt to establish new end-to-end LSPs to replace them. FRR locally repairs the protected LSPs by rerouting them over backup tunnels that bypass failed links or nodes.

Link Protection

Backup tunnels that bypass only a single link of the LSP's path provide Link Protection. They protect LSPs if a link along their path fails by rerouting the LSP's traffic to the next hop (bypassing the failed link). These are referred to as next-hop (NHOP) backup tunnels because they terminate at the LSP's next hop beyond the point of failure. Figure 1 illustrates an NHOP backup tunnel.

Figure 1 NHOP Backup Tunnel

Node Protection

FRR provides Node Protection for LSPs. Backup tunnels that bypass next-hop nodes along LSP paths are called next-next-hop (NNHOP) backup tunnels because they terminate at the node following the next-hop node of the LSP paths, thereby bypassing the next-hop node. They protect LSPs if a node along their path fails by enabling the node upstream of the failure to reroute the LSPs and their traffic around the failed node to the next-next hop. FRR supports the use of RSVP Hellos to accelerate the detection of node failures. NNHOP backup tunnels also provide protection from link failures, because they bypass the failed link as well as the node.

If an LSP is using a backup tunnel and something changes so that the LSP is no longer appropriate for the backup tunnel, the LSP is torn down. Such changes include the following:

•Backup bandwidth of the backup tunnel is reduced.

•Backup bandwidth type of backup tunnel is changed to a type that is incompatible with the primary LSP.

•Primary LSP is modified so that FRR is disabled. (The no mpls traffic-eng fast-reroute command is entered.)

Bandwidth Protection

NHOP and NNHOP backup tunnels can be used to provide bandwidth protection for rerouted LSPs. This is referred to as backup bandwidth.You can associate backup bandwidth with NHOP or NNHOP backup tunnels. This informs the router of the amount of backup bandwidth a particular backup tunnel can protect. When a router maps LSPs to backup tunnels, bandwidth protection ensures that an LSP uses a given backup tunnel only if there is sufficient backup bandwidth. The router selects which LSPs use which backup tunnels in order to provide maximum bandwidth protection. That is, the router determines the best way to map LSPs onto backup tunnels in order to maximize the number of LSPs that can be protected. For information about mapping tunnels and assigning backup bandwidth, see the "Backup Tunnel Selection Procedure" section.

Fast Tunnel Interface Down Detection

If the headend router detects that a link on a label-switched path (LSP) has gone down, the Fast Tunnel Interface Down feature forces the interface's tunnel to go down immediately. Fast Tunnel Interface Down applies to generic tunnels.

If you do not configure this feature, there is a delay before the tunnel becomes unoperational and before the traffic uses an alternative path chosen by the headend/midpoint router to forward the traffic. This is fine for data traffic, but voice traffic expects the TE tunnel to go down as soon as the LSP goes down.

This feature is required if a fast switchover from an MPLS tunnel path to an IP path is desired upon an LSP failure. It is not required nor recommended if path protection is configured. This is because an LSP failure will trigger protection activation and traffic will be switched to the protection MPLS path, rather than switched to an IP path.

RSVP Hello

RSVP Hello Operation

RSVP Hello enables RSVP nodes to detect when a neighboring node is not reachable. This provides node-to-node failure detection. When such a failure is detected, it is handled in a similar manner as a link-layer communication failure.

RSVP Hello can be used by FRR when notification of link-layer failures is not available (for example, with Ethernet), or when the failure detection mechanisms provided by the link layer are not sufficient for the timely detection of node failures.

A node running Hello sends a Hello Request to a neighboring node every interval. If the receiving node is running Hello, it responds with Hello Ack. If four intervals pass and the sending node has not received an Ack or it receives a bad message, the sending node declares that the neighbor is down and notifies FRR.

•Number of acknowledgment messages that are missed before the sending node declares that the neighbor is down, by using the ip rsvp signalling hello refresh misses command

Note If a router's CPU utilization is high due to frequent RSVP Hello processing, there may be false failures due to Hello messages that are not transmitted.

Hello Instance

A Hello instance implements RSVP Hello for a given router interface address and remote IP address. A Hello instance is expensive because of the large number of Hello requests that are sent and the strains they put on the router resources. Therefore, create a Hello instance only when it is necessary and delete it when it is no longer needed.

If there is a Hello instance with no LSPs for an unreachable neighbor, do not delete the Hello instance. Convert the active Hello instance to a passive Hello instance because there may be an active instance on the neighboring router that is sending Hello requests to this instance.

Passive Hello Instances

Passive Hello instances respond to Hello Request messages (sending Ack messages), but do not initiate Hello Request messages and do not cause LSPs to be fast rerouted. A router with multiple interfaces can run multiple Hello instances to different neighbors or to the same neighbor.

A passive Hello instance is created when a Hello Request is received from a neighbor with a source IP address/destination IP address pair in the IP header for which a Hello instance does not exist.

Delete passive instances if no Hello messages are received for this instance within 10 minutes.

Backup tunnels that terminate at the next-next hop protect both the downstream link and node. This provides protection for link and node failures. For more detailed information, see the "Node Protection" section.

Multiple Backup Tunnels Can Protect the Same Interface

There is no limit (except memory limitations) to the number of backup tunnels that can protect a given interface. In many topologies, support for Node Protection requires supporting multiple backup tunnels per protected interface. These backup tunnels can terminate at the same destination or at different destinations. That is, for a given protected interface, you can configure multiple NHOP or NNHOP backup tunnels.This allows redundancy and load balancing.

In addition to being required for Node Protection, this feature provides the following benefits:

•Increased backup capacity—If the protected interface is a high-capacity link and no single backup path exists with an equal capacity, multiple backup tunnels can protect that one high-capacity link. The LSPs using this link will fail over to different backup tunnels, allowing all of the LSPs to have adequate bandwidth protection during failure (rerouting). If bandwidth protection is not desired, the router spreads LSPs across all available backup tunnels (that is, there is load balancing across backup tunnels). For a more detailed explanation, see the "Backup Tunnel Selection Procedure" section.

A backup tunnel can protect multiple LSPs. Furthermore, a backup tunnel can protect multiple interfaces. This is called many-to-one (N:1) protection. N:1 protection has significant scalability advantages over one-to-one (1:1) protection, where a separate backup tunnel must be used for each LSP needing protection.

Example of 1:1 protection: When 5,000 backup tunnels protect 5,000 LSPs, each router along the backup path must maintain state for an additional 5,000 tunnels.

Example of N:1 protection: When one backup tunnel protects 5,000 LSPs, each router along the backup path maintains one additional tunnel.

Rerouted LSPs not only have their packets delivered during a failure, but the quality of service can also be maintained.

Bandwidth Pool Specifications for Backup Tunnels

You can restrict the types of LSPs that can use a given backup tunnel. Backup tunnels can be restricted so that only LSPs using sub pool bandwidth can use them or only LSPs that use global pool bandwidth can use them. This allows different backup tunnels to be used for voice and data. Example: The backup tunnel used for voice could provide bandwidth protection, and the backup tunnel used for data could (optionally) not provide bandwidth protection.

Semidynamic Backup Tunnel Paths

The path of a backup tunnel can be configured to be determined dynamically. This can be done by using the IP explicit address exclusion feature that was added in Release 12.0(14)ST. Using this feature, semidynamic NHOP backup tunnel paths can be specified simply by excluding the protected link; semidynamic NNHOP backup tunnel paths can be configured simply by excluding the protected node.

In case there are not enough NHOP or NNHOP backup tunnels or they do not have enough backup bandwidth to protect all LSPs, you can give an LSP priority in obtaining backup tunnels with bandwidth protection. This is especially useful if you want to give LSPs carrying voice a higher priority than those carrying data.

To activate this feature, enter the tunnel mpls traffic-eng fast-reroute bw-protect command to set the "bandwidth protection desired" bit. See the configuration task "Enabling Fast ReRoute on LSPs". The LSPs do not necessarily receive bandwidth protection. They have a higher chance of receiving bandwidth protection if they need it.

LSPs that do not have the bandwidth protection bit set can be demoted. Demotion is when one or more LSPs are removed from their assigned backup tunnel to provide backup to an LSP that has its bandwidth protection bit set. Demotion occurs only when there is a scarcity of backup bandwidth.

When an LSP is demoted, it becomes unprotected (that is, it no longer has a backup tunnel). During the next periodic promotion cycle, an attempt is made to find the best possible backup tunnels for all LSPs that do not currently have protection, including the LSP that was demoted. The LSP may get protection at the same level or a lower level, or it may get no protection.

RSVP Hello

RSVP Hello enables a router to detect when a neighboring node has gone down but its interface to that neighbor is still operational. This feature is useful when next-hop node failure is not detectable by link layer mechanisms, or when notification of link-layer failures is not available. This allows the router to switch LSPs onto its backup tunnels and avoid packet loss.

Fast ReRoute Activation

When a router's link or neighboring node fails, the router often detects this failure by an interface down notification. On a Packet over SONET (POS) interface, this notification is very fast. When a router notices that an interface has gone down, it switches LPSs going out that interface onto their respective backup tunnels (if any).

Unlike POS interfaces, Gigabit Ethernet does not have any alarms to detect link failures. If a link is down due to a cut cable or because the remote end shuts its laser, the optics module (GBIC or SFPs) on the Gigabit Ethernet card detects a loss of signal (LOS). The LOS is used as a mechanism to detect the failure and begin the switchover.

RSVP Hellos can also be used to trigger FRR. If RSVP Hellos are configured on an interface, messages are periodically sent to the neighboring router. If no response is received, Hellos declare that the neighbor is down. This causes any LSPs going out that interface to be switched to their respective backup tunnels.

Fast ReRoute also works over ATM interfaces.The interfaces must use RSVP Hello to detect failures.

Backup Tunnels Terminating at Different Destinations

Figure 3 illustrates an interface that has multiple backup tunnels terminating at different destinations and demonstrates why, in many topologies, support for Node Protection requires supporting multiple backup tunnels per protected interface.

Figure 3 Backup Tunnels that Terminate at Different Destinations

In this illustration, a single interface on R1 requires multiple backup tunnels. LSPs traverse the following routes:

•R1, R2, R3

•R1, R2, R4

To provide protection if node R2 fails, two NNHOP backup tunnels are required: one terminating at R3 and one terminating at R4.

Backup Tunnels Terminating at the Same Destination

Figure 4 shows how backup tunnels terminating at the same location can be used for redundancy and load balancing. Redundancy and load balancing work for both NHOP and NNHOP backup tunnels.

Figure 4 Backup Tunnels that Terminate at the Same Destination

In this illustration, there are three routers: R1, R2, and R3. At R1, there are two NNHOP backup tunnels (T1 and T2) that go from R1 to R3 without traversing R2.

With redundancy, if R2 fails or the link from R1 to R2 fails, either backup tunnel can be used. If one backup tunnel is down, the other can be used. LSPs are assigned to backup tunnels when the LSPs are first established. This is done before a failure.

With load balancing, if neither backup tunnel has enough bandwidth to back up all LSPs, both tunnels can be used. Some LSPs will use one backup tunnel, other LSPs will use the other backup tunnel. The router decides the best way to fit the LSPs onto the backup tunnels.

Backup Tunnel Selection Procedure

When an LSP is signaled, each node along the LSP path that provides FRR protection for the LSP selects a backup tunnel for the LSP to use if either of the following events occurs:

•The link to the next hop fails.

•The next hop fails.

By having the node select the backup tunnel for an LSP before a failure occurs, the LSP can be rerouted onto the backup tunnel quickly if there is a failure.

For an LSP to be mapped to a backup tunnel, all of the following conditions must exist:

•The LSP is protected by FRR; that is, the LSP is configured with the tunnel mpls traffic-eng fast-reroute command.

•The backup tunnel is up.

•The backup tunnel is configured to have an IP address, typically a loopback address.

•The backup tunnel is configured to protect this LSP's outgoing interface; that is, the interface is configured with the mpls traffic-eng backup-path command.

•The backup tunnel does not traverse the LSP's protected interface.

•The backup tunnel terminates at the LSP's NHOP or NNHOP. If it is an NNHOP tunnel, it does not traverse the LSP's NHOP.

•The bandwidth protection requirements and constraints, if any, for the LSP and backup tunnel are met. For information about bandwidth protection considerations, see the "Bandwidth Protection" section.

Bandwidth Protection

A backup tunnel can be configured to protect two types of backup bandwidth:

•Limited backup bandwidth—A backup tunnel provides bandwidth protection. The sum of the bandwidth of all LSPs using this backup tunnel cannot exceed the backup tunnel's backup bandwidth. When assigning LSPs to this type of backup tunnel, sufficient backup bandwidth must exist.

•Unlimited backup bandwidth—The backup tunnel does not provide any bandwidth protection (that is, best-effort protection exists). There is no limit to the amount of bandwidth used by the LSPs that are mapped to this backup tunnel. LSPs that allocate zero bandwidth can only use backup tunnels that have unlimited backup bandwidth.

Load-balancing on Limited-bandwidth Backup Tunnels

There may be more than one backup tunnel that has sufficient backup bandwidth to protect a given LSP. In this case, the router chooses the one that has the least amount of backup bandwidth available. This algorithm limits fragmentation, maintaining the largest amount of backup bandwidth available.

Specifying limited backup bandwidth does not "guarantee" bandwidth protection if there is a link or node failure. For example, the set of NHOP and NNHOP backup tunnels that gets triggered when an interface fails may all share some link on the network topology, and this link may not have sufficient bandwidth to support all LSPs using this set of backup tunnels.

In Figure 5, both backup tunnels traverse the same links and hop. When the link between routers R1 and R4 fails, backup tunnels for primary tunnel 1 and primary tunnel 2 are triggered simultaneously. The two backup tunnels may share a link in the network.

Figure 5 Backup Tunnels Share a Link

In Figure 6, the backup tunnel for primary tunnel 1 may traverse routers R1-R2-R3-R4, and the backup tunnel for primary tunnel 2 may traverse routers R4-R2-R3-R1. In this case, the link R2-R3 may get overloaded if R1-R4 fails.

Figure 6 Overloaded Link

Load-balancing on Unlimited-bandwidth Backup Tunnels

More than one backup tunnel, each having unlimited backup bandwidth, can protect a given interface. In this case, when choosing a backup tunnel for a given LSP, the router chooses the backup tunnel that has the least amount of backup bandwidth in use. This algorithm evenly distributes the LSPs across backup tunnels based on LSP's bandwidth. If an LSP is requesting zero bandwidth, the router chooses the backup tunnel that is currently protecting the fewest LSPs.

Pool Type and Backup Tunnels

By default, a backup tunnel provides protection for LSPs that allocate from any pool (that is, global or sub pool). However, a backup tunnel can be configured to protect only LSPs that use global pool bandwidth, or only those that use sub pool bandwidth.

Tunnel Selection Priorities

More than one backup tunnel can protect a given LSP, where one backup tunnel terminates at the LSP's NNHOP, and the other terminates at the LSP's NHOP. In this case, the router chooses the backup tunnel that terminates at the NNHOP (that is, FRR prefers NNHOP over NHOP backup tunnels).

Table 1 lists the tunnel selection priorities. The first choice is an NNHOP backup tunnel that acquires its bandwidth from a sub pool or global pool, and has limited bandwidth. If there is no such backup tunnel, the next choice (2) is a next-next hop backup tunnel that acquires a limited amount of bandwidth from any pool. The preferences go from 1 (best) to 8 (worst), where choice 3 is for an NNHOP backup tunnel with an unlimited amount of sub pool or global pool bandwidth.

Table 1 Tunnel Selection Priorities

Preference

Backup Tunnel Destination

Bandwidth Pool

Bandwidth Amount

1 (Best)

NNHOP

Sub pool or global pool

Limited

2

NNHOP

Any

Limited

3

NNHOP

Sub pool or global pool

Unlimited

4

NNHOP

Any

Unlimited

5

NHOP

Sub pool or global pool

Limited

6

NHOP

Any

Limited

7

NHOP

Sub pool or global pool

Unlimited

8 (Worst)

NHOP

Any

Unlimited

Figure 7 shows an example of the backup tunnel selection procedure based on the designated amount of global pool and sub pool bandwidth currently available.

Note If NHOP and NNHOP backup tunnels do not have sufficient backup bandwidth, no consideration is given to the type of data that the LSP is carrying. For example, a voice LSP may not be protected unless it is signalled before a data LSP. To prioritize backup tunnel usage, see the "Backup Protection Preemption Algorithms" section.

Figure 7 Choosing from Among Multiple Backup Tunnels

In this example, an LSP requires 20 units (kilobits per second) of sub pool backup bandwidth. The best backup tunnel is selected as follows:

1. Backup tunnels T1 through T4 are considered first because they terminate at the NNHOP.

2. Tunnel T4 is eliminated because it only has 10 units of sub pool backup bandwidth.

3. Tunnel T1 is eliminated because it protects only LSPs using global pool bandwidth.

4. Tunnel T3 is chosen over T2 because, although both have sufficient backup bandwidth, T3 has the least backup bandwidth available (leaving the most backup bandwidth available on T2).

5. Tunnels T5 and T6 need not be considered because they terminate at an NHOP, and therefore are less desirable than T3, which terminates at an NNHOP.

Promotion

After a backup tunnel has been chosen for an LSP, conditions may change that will cause us to reevaluate this choice. This reevaluation, if successful, is called promotion. Such conditions may include:

1. A new backup tunnel comes up.

2. The currently chosen backup tunnel for this LSP goes down.

3. A backup tunnel's available backup bandwidth increases. For example, an LSP protected by the tunnel has been reoptimized by the headend to use another path.

4. A backup tunnel's available backup-bandwidth decreases.

For cases 1 and 2, the LSP's backup tunnel is evaluated immediately. Cases 3 and 4 are addressed by periodically reevaluating LSP-to-backup tunnel mappings. By default, background reevaluation is performed every 5 minutes. This interval is configurable via the mpls traffic-eng fast-reroute timers command.

The response to case 4 is as follows:

When the backup tunnel's bandwidth is reduced, promotion will not be run so long as the remaining bandwidth is greater than the sum of the bandwidths of all primary paths for which this tunnel is the backup. This policy prevents unnecessary disruption of protection of the primary paths.

When the backup tunnel's bandwidth does fall below the required bandwidth needed for it to substitute for all primary paths to which it has been assigned, promotion is run.

Backup Protection Preemption Algorithms

When you set the "bandwidth protection desired" bit for an LSP, the LSP has a higher right to select backup tunnels that provide bandwidth protection and it can preempt other LSPs that do not have that bit set.

If there is insufficient backup bandwidth on NNHOP backup tunnels but not on NHOP backup tunnels, the bandwidth-protected LSP does not preempt NNHOP LSPs; it uses NHOP protection.

If there are multiple LSPs using a given backup tunnel and one or more must be demoted to provide bandwidth, there are two user-configurable methods (algorithms) that the router can use to determine which LSPs are demoted.

•Minimize amount of bandwidth that is wasted.

•Minimize the number of LSPs that are demoted.

For example, If you need 10 units of backup bandwidth on a backup tunnel, you can demote one of the following:

•A single LSP using 100 units of bandwidth—Makes available more bandwidth than needed, but results in lots of waste

•Ten LSPs, each using one unit of bandwidth—Results in no wasted bandwidth, but affects more LSPs

The default algorithm minimizes the number of LSPs that are demoted. To change the algorithm to minimize the amount of bandwidth that is wasted, enter the mpls traffic-eng fast-reroute backup-prot-preemption optimize-bw command.

Bandwidth Protection Considerations

There are numerous ways in which bandwidth protection can be ensured. Table 2 describes the advantages and disadvantages of three methods.

Table 2 Bandwidth Protection Methods

Method

Advantages

Disadvantages

Reserve bandwidth for backup tunnels explicitly.

It is simple.

It is a challenge to allow bandwidth sharing of backup tunnels protecting against independent failures.

Use backup tunnels that are signaled with zero bandwidth.

It provides a way to share bandwidth used for protection against independent failures, so it ensures more economical bandwidth usage.

It may be complicated to determine the proper placement of zero bandwidth tunnels.

Backup bandwidth protection

Ensures bandwidth protection for voice traffic.

An LSP that does not have backup bandwidth protection can be demoted at any time if there is not enough backup bandwidth and an LSP that has backup bandwidth protection needs bandwidth.

Cisco implementation of FRR does not mandate a particular approach, and it provides the flexibility to use any of the above approaches. However, given a range of configuration choices, be sure that the choices are constant with a particular bandwidth protection strategy.

The following sections describe some important issues in choosing an appropriate configuration:

Using Backup Tunnels with Explicitly Signaled Bandwidth

There are two bandwidth parameters that must be set for a backup tunnel:

•actual signaled bandwidth

•backup-bandwidth

To signal bandwidth requirements of a backup tunnel, configure the bandwidth of the backup tunnel by using the tunnel mpls traffic-eng bandwidth command.

To configure the backup bandwidth of the backup tunnel, use the tunnel mpls traffic-eng backup-bw command.

The signaled bandwidth is used by the LSRs on the path of the backup tunnel to perform admission control and do appropriate bandwidth accounting.

The backup bandwidth is used by the PLR (the headend of the backup tunnel) to decide how much primary traffic can be rerouted to this backup tunnel if there is a failure.

Both parameters need to be set to ensure proper operation. The numerical value of the signaled bandwidth and the backup-bandwidth should be the same.

Protected Bandwidth Pools and the Bandwidth Pool from which the Backup Tunnel Reserves its Bandwidth

The tunnel mpls traffic-eng bandwidth command allows you to configure the following:

•Amount of bandwidth a backup tunnel reserves

•The DS-TE bandwidth pool from which the bandwidth needs to be reserved

Note Only one pool can be selected (that is, the backup tunnel can explicitly reserve bandwidth from either the global pool or the sub pool, but not both).

The tunnel mpls traffic-eng backup-bw command allows you to specify the bandwidth pool to which the traffic must belong for the traffic to use this backup tunnel. Multiple pools are allowed.

There is no direct correspondence between the bandwidth pool that is protected and the bandwidth pool from which the bandwidth of the backup tunnel draws its bandwidth.

Example: In this example, assume the following:

•Bandwidth protection is desired only for sub pool traffic, but the best-effort traffic using the global pool does not require bandwidth protection.

•Scheduling is configured so that sub pool traffic uses the priority queue, and global pool traffic is served at a lower priority.

Bandwidth protection for 10 Kbps of sub pool traffic on a given link can be achieved by any of the following combinations:

•tunnel mpls traffic-eng bandwidth sub-pool 10

tunnel mpls traffic-eng backup-bw sub-pool 10

•tunnel mpls traffic-eng bandwidth global-pool 10

tunnel mpls traffic-eng backup-bw sub-pool 10 global-pool unlimited

•tunnel mpls traffic-eng bandwidth global-pool 40

tunnel mpls traffic-eng backup-bw sub-pool 10 global-pool 30

Using Backup Tunnels Signaled with Zero Bandwidth

Frequently it is desirable to use backup tunnels with zero signaled bandwidth, even when bandwidth protection is required. It may seem that if no bandwidth is explicitly reserved, no bandwidth guarantees can be provided. However, that is not necessarily true.

In the following situation:

•Only link protection is desired.

•Bandwidth protection is desired only for sub pool traffic.

For each protected link AB with a max reservable sub pool value of S, there may be a path from node A to node B such that the difference between max reservable global and max reservable sub pool is at least S. If it is possible to find such paths for each link in the network, you can establish all the backup tunnels along such paths without any bandwidth reservations. If there is a single link failure, only one backup tunnel will use any link on its path. Because that path has at least S of available bandwidth (in the global pool), assuming that marking and scheduling is configured to classify the sub pool traffic into a priority queue, the sub pool bandwidth is guaranteed.

The above approach allows sharing of the global pool bandwidth between backup tunnels protecting independent link failures. The backup tunnels are expected to be used for only a short period of time after a failure (until the headends of affected LSPs reroute those LSPs to other paths with available sub pool bandwidth). The probability of multiple unrelated link failures is very small (in the absence of node or SRLG failures, which result in multiple link failures). Therefore, it is reasonable to assume that link failures are in practice independent with high probability. This "independent failure assumption" in combination with backup tunnels signaled without explicit bandwidth reservation enables efficient bandwidth sharing that yields substantial bandwidth savings.

Backup tunnels protecting the sub pool traffic do now draw bandwidth from any pool. Primary traffic using the global pool can use the entire global pool, and primary traffic using the sub pool can use the entire sub pool. Yet, sub pool traffic has a complete bandwidth guarantee if there is a single link failure.

A similar approach can be used for node and SRLG protection. However, the decision of where to put the backup tunnels is more complicated because both node and SRLG failures effectively result in the simultaneous failure of several links. Therefore, the backup tunnels protecting traffic traversing all affected links cannot be computed independently of each other. The backup tunnels protecting groups of links corresponding to different failures can still be computed independently of each other, which results in similar bandwidth savings.

Signaled Bandwidth Versus Backup Bandwidth

Backup bandwidth is used locally (by the router that is the headend of the backup tunnel) to determine which, and how many, primary LSPs can be rerouted on a particular backup tunnel. The router ensures that the combined bandwidth requirement of these LSPs does not exceed the backup bandwidth.

Therefore, even when the backup tunnel is signaled with zero bandwidth, the backup bandwidth must be configured with the value corresponding to the actual bandwidth requirement of the traffic protected by this backup tunnel. Unlike the case when bandwidth requirements of the backup tunnels are explicitly signaled, the value of the signaled bandwidth (which is zero) is not the same value as the backup bandwidth.

How to Configure MPLS TE: Link and Node Protection, with RSVP Hellos Support (with Fast Tunnel Interface Down Detection)

This section assumes that you want to add FRR protection to a network in which MPLS TE LSPs are configured.

Before performing the configuration tasks, it is assumed that you have done the following tasks but you do not have to already have configured MPLS TE tunnels:

Creating a backup tunnel is basically no different from creating any other tunnel. None of the commands below is new.

Note When using the exclude-address command to specify the path for a backup tunnel, you must exclude an interface address to avoid a link (for creating an NHOP backup tunnel), or a router-ID address to avoid a node (for creating an NNHOP backup tunnel).

Enters the subcommand mode for IP explicit paths to create the named path.

Step 9

exclude-addressaddress

Example:

Router(cfg-ip-expl-path)# exclude-address 10.3.3.3

For Link Protection, specifies the IP address of the link to be protected. For Node Protection, specifies the router ID of the node to be protected.

Note Backup tunnel paths can be dynamic or explicit and they do not have to use exclude-address. Because backup tunnels must avoid the protected link or node, it is convenient to use an exclude-address.

Permits selected SONET alarms to be logged to the console for a POS interface.

Configuring an Interface for Fast Tunnel Interface Down

To configure interface for fast tunnel interface down, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. interfacetypeslot/port

4. tunnel mpls traffic-eng interface downdelaytime

DETAILED STEPS

Step 1

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interfacetypeslot/port

Example:

Router(config)# interface tunnel 1000

Configures an interface type and enters interface configuration mode.

Step 4

tunnel mpls traffic-eng interface down delaytime

Example:

Router(config-if)# tunnel mpls traffic-eng interface down delay 0

Forces a tunnel to go down as soon as the headend router detects that the label-switched path (LSP) is down.

Verifying That Fast ReRoute Is Operational

To verify that FRR can function, perform the following steps.

SUMMARY STEPS

Note To determine if FRR has been configured correctly, perform Steps 1 and 2.

Note If you created LSPs and performed the required configuration tasks but do not have operational backup tunnels (that is, the backup tunnels are not up or the LSPs are not associated with those backup tunnels), perform Step 3.

1. show mpls traffic-eng tunnels brief

2. show ip rsvp sender detail

3. show mpls traffic-eng fast-reroute database

4. show mpls traffic-eng tunnels backup

5. show mpls traffic-eng fast-reroute database

6. show ip rsvp reservation

DETAILED STEPS

Step 1 show mpls traffic-eng tunnels brief

Use this command to verify that backup tunnels are up.

Router# show mpls traffic-eng tunnels brief

Signalling Summary:

LSP Tunnels Process: running

RSVP Process: running

Forwarding: enabled

Periodic reoptimization: every 3600 seconds, next in 1706 seconds

TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROT

Router_t1 10.112.0.12 - PO4/0/1 up/up

Router_t2 10.112.0.12 - unknown up/down

Router_t3 10.112.0.12 - unknown admin-down

Router_t1000 10.110.0.10 - unknown up/down

Router_t2000 10.110.0.10 - PO4/0/1 up/up

Displayed 5 (of 5) heads, 0 (of 0) midpoints, 0 (of 0) tails

Step 2 show ip rsvp sender detail

Use this command to verify that LSPs are protected by the appropriate backup tunnels.

Following is sample output from the show ip rsvp sender detailcommand when the command is entered at the PLR before a failure.

If LDP is not enabled, separate prefix items are not shown because all prefixes then use a single rewrite. To confirm that a particular IP prefix is FRR protected, even though it is not shown in this display, enter it within the show mpls forwarding-tableip-addressdetailcommand. The final line of the display will tell whether that prefix is protected:

Router# show mpls forwarding-table 10.0.0.11 32 detail

Local Outgoing Prefix Bytes tag Outgoing Next Hop

tag tag or VC or Tunnel Id switched interface

Tun hd Untagged 10.0.0.11/32 48 pos5/0 point2point

MAC/Encaps=4/8, MTU=1520, Tag Stack{22}

48D18847 00016000

No output feature configured

Fast Reroute Protection via (Tu0, outgoing label 12304)

The following command output displays the LSPs that are protected when the FRR primary tunnel is over an ATM interface and the backup tunnel is over a POS interface. As shown in Figure 8, interface ATM4/0.100 is protected by backup tunnel 501.

Figure 8 Protected LSPs

Primary tunnel 500—Path is R1 via ATM4/0.100 to R2 to R3 to R4.

FRR backup tunnel 501—Path is R1 via POS2/0 to R2.

Interface ATM4/0.100—Protected by backup tunnel 501.

Router# show mpls traffic-eng fast-reroute database

Tunnel head end item frr information:

Protected tunnel In-label Out intf/label FRR intf/label Status

Tunnel500 Tun hd AT4/0.100:Untagg Tu501:20 ready

Prefix item frr information:

Prefix Tunnel In-label Out intf/label FRR intf/label Status

10.0.0.8/32 Tu500 18 AT4/0.100:Pop ta Tu501:20 ready

10.0.8.8/32 Tu500 19 AT4/0.100:Untagg Tu501:20 ready

10.8.9.0/24 Tu500 22 AT4/0.100:Untagg Tu501:20 ready

LSP midpoint item frr information:

LSP identifier In-label Out intf/label FRR intf/label Status

The following command output displays the LSPs that are protected when the FRR backup tunnel is over an ATM interface.

Router# show mpls traffic-eng fast-reroute database

Tunnel head end item frr information:

Protected tunnel In-label Out intf/label FRR intf/label Status

Tunnel500 Tun hd PO2/0:Untagged Tu501:20 ready

Prefix item frr information:

Prefix Tunnel In-label Out intf/label FRR intf/label Status

10.0.0.8/32 Tu500 18 PO2/0:Pop tag Tu501:20 ready

10.0.8.8/32 Tu500 19 PO2/0:Untagged Tu501:20 ready

10.8.9.0/24 Tu500 22 PO2/0:Untagged Tu501:20 ready

LSP midpoint item frr information:

LSP identifier In-label Out intf/label FRR intf/label Status

Step 4 show mpls traffic-eng tunnels backup

The following conditions must exist for backup tunnels to be operational:

•LSP is reroutable—At the headend of the LSP, enter the show run int tunneltunnel-number command.The output should include the tunnel mpls traffic-eng fast-reroute command. If it does not, enter this command for the tunnel.

On the router where the backup tunnels originate, enter the show mpls traffic-eng tunnels backup command. Following is sample command output.

Router# show mpls traffic-eng tunnels backup

Router_t578

LSP Head, Tunnel578, Admin: up, Oper: up

Src 10.55.55.55, Dest 10.88.88.88, Instance 1

Fast Reroute Backup Provided:

Protected i/fs: PO1/0, PO1/1, PO3/3

Protected lsps: 1

Backup BW: any pool unlimited; inuse: 100 kbps

Router_t5710

LSP Head, Tunnel5710, Admin: admin-down, Oper: down

Src 10.55.55.55, Dest 10.7.7.7, Instance 0

Fast Reroute Backup Provided:

Protected i/fs: PO1/1

Protected lsps: 0

Backup BW: any pool unlimited; inuse: 0 kbps

Router_t5711

LSP Head, Tunnel5711, Admin: up, Oper: up

Src 10.55.55.55, Dest 10.7.7.7, Instance 1

Fast Reroute Backup Provided:

Protected i/fs: PO1/0

Protected lsps: 2

Backup BW: any pool unlimited; inuse: 6010 kbps

The command output will allow you to verify the following:

•Backup tunnel exists—Verify that there is a backup tunnel that terminates at this LSP's NHOP or NNHOP. Look for the LSP's NHOP or NNHOP in the Dest field.

•Backup tunnel is up—To verify that the backup tunnel is up, look for "Up" in the State field.

•Backup tunnel is associated with LSP's I/F—Verify that the interface for the LSP is allowed to use this backup tunnel. Look for the LSP's output interface in the "protects" field list.

•Backup tunnel has sufficient bandwidth—If you restricted the amount of bandwidth a backup tunnel can hold, verify that the backup tunnel has sufficient bandwidth to hold the LSPs that would use this backup tunnel if there is a failure. The bandwidth of an LSP is defined by the line tunnel mpls traffic-eng bandwidth at the headend of the LSP. To determine the available bandwidth on a backup tunnel, look at the "cfg" and "inuse" fields. If there is insufficient backup bandwidth to accommodate the LSPs that would use this backup tunnel in the event of a failure, create an additional backup tunnel or increase the backup bandwidth of the existing tunnel by using the tunnel mpls traffic-eng bandwidth command.

Note To determine how much bandwidth is sufficient, offline capacity planning may be required.

•Backup tunnel has appropriate bandwidth type—If you restricted the type of LSPs (sub pool or global pool) that can use this backup tunnel, verify that the LSP is the appropriate type for the backup tunnel. The type of the LSP is defined by the line tunnel mpls traffic-eng bandwidthat the headend of this LSP. If this line contains the word "sub pool", then it uses sub pool bandwidth; otherwise, it uses global pool bandwidth. Verify that the type matches the type the backup tunnel can hold by looking in the output of the above command.

If none of the above actions works, enable debug by entering the debug ip rsvp fast-reroute command and the debug mpls traffic-eng fast-reroute command on the router that is the headend of the backup tunnel. Then do the following:

Note If LDP is not enabled, separate prefix items are not shown because all prefixes then use a single rewrite. To confirm that a particular IP prefix is FRR protected, even though it is not shown in this display, enter it within the show mpls forwarding-tableip_addressdetailcommand. The final line of the display will tell whether that prefix is protected:

Router# show mpls forwarding-table 10.0.0.11 32 detail

Local Outgoing Prefix Bytes tag Outgoing Next Hop

tag tag or VC or Tunnel Id switched interface

Tun hd Untagged 10.0.0.11/32 48 pos5/0 point2point

MAC/Encaps=4/8, MTU=1520, Tag Stack{22}

48D18847 00016000

No output feature configured

Fast Reroute Protection via (Tu0, outgoing label 12304)

Step 6 show ip rsvp reservation

Following is sample output from the show ip rsvp reservation command entered at the headend of a primary LSP. Entering the command at the head-end of the primary LSP shows, among other things, the status of FRR (that is, local protection) at each hop this LSP traverses. The per-hop information is collected in the Record Route Object (RRO) that travels with the Resv message from the tail to the head.

Router# show ip rsvp reservation detail

Reservation:

Tun Dest: 10.1.1.1 Tun ID: 1 Ext Tun ID: 10.1.1.1

Tun Sender: 10.1.1.1 LSP ID: 104

Next Hop: 10.1.1.2 on POS1/0

Label: 18 (outgoing)

Reservation Style is Shared-Explicit, QoS Service is Controlled-Load

Average Bitrate is 0 bits/sec, Maximum Burst is 1K bytes

Min Policed Unit: 0 bytes, Max Pkt Size: 0 bytes

RRO:

10.1.1.1/32, Flags:0x1 (Local Prot Avail/to NHOP)

Label subobject: Flags 0x1, C-Type 1, Label 18

10.1.1.1/32, Flags:0x0 (Local Prot Avail/In Use/Has BW/to NHOP)

Label subobject: Flags 0x1, C-Type 1, Label 16

10.1.1.2/32, Flags:0x0 (No Local Protection)

Label subobject: Flags 0x1, C-Type 1, Label 0

Resv ID handle: CD000404.

Policy: Accepted. Policy source(s): MPLS/TE

Notice the following about the primary LSP:

•It has protection that uses a NHOP backup tunnel at its first hop.

•It has protection and is actively using an NHOP backup tunnel at its second hop.

•It has no local protection at its third hop.

The RRO display shows the following information for each hop:

•Whether local protection is available (that is, whether the LSP has selected a backup tunnel)

•Whether local protection is in use (that is, whether the LSP is currently using its selected backup tunnel)

•Whether the selected backup tunnel is an NHOP or NNHOP backup tunnel

•Whether the backup tunnel used at this hop provides bandwidth protection

At a PLR, LSPs transition from Ready to Active if one of the following events occurs:

•Primary interface goes down—If the primary interface (LSP's outbound interface) goes down and the LSP is ready to use a backup tunnel, the LSP will transition to the active state causing its data to flow over the backup tunnel. On some platforms and interface types (for example, GSR POS interfaces), fast interface-down logic has been added to detect this event very quickly. On other platforms where this logic does not exist, detection time is slower. On such platforms, it may be desirable to enable RSVP Hello (see the next bulleted item, "Hellos detect next hop is down").

•Hellos detect next hop is down—If Hellos are enabled on the primary interface (LSP's outbound interface), and the LSP's next hop is no longer reachable, the next hop is declared down. This event will cause the LSP to begin actively using its backup tunnel. Notice that a next hop will be declared down even if the primary interface does not go down. For example, if the next hop stops responding due to a reboot or software/hardware problem, Hellos will trigger the LSPs using this next hop to switch to their backup tunnels. Hellos can also help trigger FRR on interfaces such as Gigabit Ethernet where the interface remains up but is unusable (due to lack of link-layer liveness detection mechanisms).

Primary Tunnel Does Not Select Backup Tunnel That Is Up

If a backup tunnel is up, but it is not selected as a backup tunnel by the primary tunnel (LSP), enter the following commands for the backup tunnel:

•shutdown

•no shutdown

Note If you change the status of a backup tunnel, the backup tunnel selection algorithm is rerun for the backup tunnel. LSPs that have currently selected (that is, are ready to use) that backup tunnel will be disassociated from it, and then reassociated with that backup tunnel or another backup tunnel. This is generally harmless and usually results in mapping the same LSPs to that backup tunnel. However, if any LSPs are actively using that backup tunnel, shutting down the backup tunnel will tear down those LSPs.

Enhanced RSVP Commands

The following RSVP commands have been enhanced to display information that can be helpful when examining FRR state or when troubleshooting FRR:

These commands show control plane state; they do not show data state. That is, they show information about RSVP messages (Path and Resv) used to signal LSPs. For information about the data packets being forwarded along LSPs, use the show mpls forwarding command.

RSVP Hello

The RSVP Hello feature enables RSVP nodes to detect when a neighboring node is not reachable. Use this feature when notification of link-layer failures is not available and unnumbered links are not used, or when the failure detection mechanisms provided by the link layer are not sufficient for timely node failure detection. Hello must be configured both globally on the router and on the specific interface to be operational.

Hello Instances Have Not Been Created

If Hello instances have not been created, do the following:

•Determine if RSVP Hello has been enabled globally on the router. Enter the ip rsvp signalling hello (configuration) command.

•Determine if RSVP Hello has been enabled on an interface that the LSPs traverse. Enter the ip rsvp signalling hello (interface) command.

•Verify that at least one LSP has a backup tunnel by viewing the output of the show ip rsvp sender command. A value of "Ready" indicates that a backup tunnel has been selected.

No entry at index (error may self-correct, RRO may not yet have propagated from downstream node of interest)" Error Message Is Printed at the Point of Local Repair

FRR relies on a Record Route Object (RRO) in Resv messages arriving from downstream. Routers receiving Path messages with the SESSION_ATTRIBUTE bit indicating that the LSP is fast-reroutable should include an RRO in the corresponding Resv messages.

If an LSP is configured for FRR, but the Resv arriving from a downstream router contains an incomplete RRO, the "No entry at index (error may self-correct, RRO may not yet have propagated from downstream node of interest)" message is printed. An incomplete RRO is one in which the NHOP or the NNHOP did not include an entry in the RRO.

This error typically means that backup tunnels to the NHOP or the NNHOP cannot be selected for this LSP because there is insufficient information about the NHOP or NNHOP due to the lack of an RRO entry.

Occasionally there are valid circumstances in which this situation occurs temporarily and the problem is self-corrected. If subsequent Resv messages arrive with a complete RRO, ignore the error message.

To determine whether the error has been corrected, view the RRO in Resv messages by entering the clear ip rsvp hello instance counters command. Use an output filter keyword to view only the LSP of interest.

Couldn't get rsbs (error may self-correct when Resv arrives)" Error Message Is Printed at the Point of Local Repair

The PLR cannot select a backup tunnel for an LSP until a Resv message has arrived from downstream.

When this error occurs, it typically means that something is truly wrong. For example, no reservation exists for this LSP. You can troubleshoot this problem by using the debug ip rsvp reservation command to enable debug.

Occasionally there are valid circumstances in which this error message occurs and there is no need for concern. One such circumstance is when an LSP experiences a change before any Resv message has arrived from downstream. Changes can cause a PLR to try to select a backup tunnel for an LSP, and the selection will fail (causing this error message) if no Resv message has arrived for this LSP.

Enabling Fast ReRoute for all Tunnels: Example

On router R1, enter interface configuration mode for each tunnel to be protected (Tunnel 1000 and Tunnel 2000). Enable these tunnels to use a backup tunnel in case of a link or node failure along their paths.

Tunnel 1000 will use 10 units of bandwidth from the sub pool.

Tunnel 2000 will use 5 units of bandwidth from the global pool. The "bandwidth protection desired" bit and the "node protection desired bit" have been set by specifying bw-prot and node-prot, respectively, in the tunnel mpls traffic-eng fast-reroute command.

Backup tunnel 1 is to be used only by LSPs that take their bandwidth from the global pool. It does not provide bandwidth protection. Backup tunnel 2 is to be used only by LSPs that take their bandwidth from the sub pool. Backup tunnel 2 provides bandwidth protection for up to 1000 units.

Configuring Backup Bandwidth Protection: Example

In the following example, backup bandwidth protection is configured.

Note This global configuration is required only to change the backup protection preemption algorithm from minimize the number of LSPs that are demoted to minimize the amount of bandwidth that is wasted.

RFCs

RFCs

Title

RFC 4090

Fast Reroute Extensions for RSVP-TE for LSP Tunnels

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register on Cisco.com.

Command Reference

tunnel mpls traffic-eng interface down delay

To force a tunnel to go down as soon as the headend router detects that the label-switched path (LSP) is down, use the tunnel mpls traffic-eng interface down delay command in interface configuration mode. To disable this feature, use the no form of this command.

tunnel mpls traffic-eng interface down delaytime

no tunnel mpls traffic-eng interface down delaytime

Syntax Description

time

Time, in minutes. The only valid value is 0.

Defaults

There is a delay before the tunnel goes down.

Command Modes

Interface configuration

Command History

Release

Modification

12.0(30)S

This command was introduced.

12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SRB.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

Usage Guidelines

You cannot specify both the tunnel mpls traffic-eng interface down delay command and the tunnel mpls traffic-eng forwarding-adjacency command. The first command that you enter would prevent the implementation of the other command and would cause the system to display error messages.

Examples

In the following example, if the headend router detects that a link has goes down on tunnel 1000, the tunnel goes down immediately.

Glossary

backup tunnel—An MPLS TE tunnel used to protect other (primary) tunnels' traffic when a link or node failure occurs.

bandwidth—The available traffic capacity of a link.

Cisco Express Forwarding—A means for accelerating the forwarding of packets within a router, by storing route lookup.

enterprise network—A large and diverse network connecting most major points in a company or other organization.

Fast ReRoute—Procedures that enable temporary routing around a failed link or node while a new LSP is being established at the head end.

Gigabit Ethernet—Standard for a high-speed Ethernet, approved by the IEEE (Institute of Electrical and Electronics Engineers) 802.3z standards committee in 1996.

global pool—The total bandwidth allocated to an MPLS Traffic Engineering link or node.

headend—The router that originates and maintains a given LSP. This is the first router in the LSP's path.

hop—Passage of a data packet between two network nodes (for example, between two routers).

instance—A Hello instance implements the RSVP Hello extensions for a given router interface address and remote IP address. Active Hello instances periodically send Hello Request messages, expecting Hello ACK messages in response. If the expected Ack message is not received, the active Hello instance declares that the neighbor (remote IP address) is unreachable (that is, it is lost). This can cause LSPs crossing this neighbor to be fast rerouted.

interface—A network connection.

Intermediate System-to-Intermediate System—IS-IS. Link-state hierarchical routing protocol that calls for intermediate system (IS) routers to exchange routing information based on a single metric to determine network topology.

link—A point-to-point connection between adjacent nodes. There can be more than one link between adjacent nodes. A network communications channel consisting of a circuit or transmission path and all related equipment between a sender and a receiver. Sometimes referred to as a line or a transmission link.

load balancing—A configuration technique that shifts traffic to an alternative link if a certain threshold is exceeded on the primary link. Load balancing is similar to redundancy in that if an event causes traffic to shift directions, alternative equipment must be present in the configuration. In load balancing, the alternative equipment is not necessarily redundant equipment that only operates in the event of a failure.

LSP—label-switched path. A configured connection between two routers, in which label switching is used to carry the packets. The purpose of an LSP is to carry data packets.

merge point—The backup tunnel's tail.

MPLS—Multiprotocol Label Switching. Packet-forwarding technology, used in the network core, that applies data link layer labels to tell switching nodes how to forward data, resulting in faster and more scalable forwarding than network layer routing normally can do.

MPLS global label allocation—There is one label space for all interfaces in the router. For example, label 100 coming in one interface is treated the same as label 100 coming in a different interface.

NHOP—next hop. The next downstream node along an LSP's path.

NHOP backup tunnel—next-hop backup tunnel. Backup tunnel terminating at the LSP's next hop beyond the point of failure, and originating at the hop immediately upstream of the point of failure. It bypasses a failed link, and is used to protect primary LSPs that were using this link before the failure.

NNHOP—next-next hop. The node after the next downstream node along an LSP's path.

NNHOP backup tunnel—next-next-hop backup tunnel. Backup tunnel terminating at the LSP's next-next hop beyond the point of failure, and originating at the hop immediately upstream of the point of failure. It bypasses a failed link and/or node, and is used to protect primary LSPs that were using this link or node before the failure.

node—Endpoint of a network connection or a junction common to two or more lines in a network. Nodes can be interconnected by links, and serve as control points in the network. Computers on a network, or any endpoint or a junction common to two or more lines in a network. Nodes can be processors, controllers, or workstations.

primary LSP—The last LSP originally signaled over the protected interface before the failure. The LSP before the failure.

primary tunnel—Tunnel whose LSP may be fast rerouted if there is a failure. Backup tunnels cannot be primary tunnels.

promotion—Conditions, such as a new backup tunnel comes up, cause a reevaluation of a backup tunnel that was chosen for an LSP. If the reevaluation is successful, it is called a promotion.

protected interface—An interface that has one or more backup tunnels associated with it.

redundancy—The duplication of devices, services, or connections so that, in the event of a failure, the redundant devices, services, or connections can perform the work of those that failed.

RSVP—Resource Reservation Protocol. An IETF protocol used for signaling requests (setting up reservations) for Internet services by a customer before that customer is permitted to transmit data over that portion of the network.

scalability—An indicator showing how quickly some measure of resource usage increases as a network gets larger.

state—Information that a router must maintain about each LSP. The information is used for rerouting tunnels.

sub pool—The more restrictive bandwidth in an MPLS Traffic Engineering link or node. The sub pool is a portion of the link or node's overall global pool bandwidth.

tailend—The router upon which an LSP is terminated. This is the last router in the LSP's path.

topology—The physical arrangement of network nodes and media within an enterprise networking structure.

tunnel—Secure communications path between two peers, such as two routers.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.