Cisco IOS Software Releases 12.2 SR

Table Of Contents

RSVP Fast Local Repair

Contents

Prerequisites for RSVP FLR

Restrictions for RSVP FLR

Information About RSVP FLR

Feature Overview of RSVP FLR

Benefits of RSVP FLR

How to Configure RSVP FLR

Configuring the RSVP FLR Wait Time

Configuring the RSVP FLR Repair Rate

Configuring the RSVP FLR Notifications

Verifying the RSVP FLR Configuration

Configuration Examples for RSVP FLR

Configuring RSVP FLR: Example

Verifying the RSVP FLR Configuration: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

clear ip rsvp signalling fast-local-repair statistics

ip rsvp signalling fast-local-repair notifications

ip rsvp signalling fast-local-repair rate

ip rsvp signalling fast-local-repair wait-time

show ip rsvp

show ip rsvp interface

show ip rsvp sender

show ip rsvp signalling fast-local-repair

Feature Information for RSVP FLR

Glossary

RSVP Fast Local Repair

---

First Published: February 19, 2007

Last Updated: February 19, 2007

The RSVP Fast Local Repair feature provides quick adaptation to routing changes without the overhead of the refresh period to guarantee the quality of service (QoS) for data flows. With fast local repair (FLR), Resource Reservation Protocol (RSVP) speeds up its response to routing changes from 30 seconds to a few seconds.

Finding Feature Information in This Module

Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for RSVP FLR" section.

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.

Contents

•Prerequisites for RSVP FLR

•Restrictions for RSVP FLR

•Information About RSVP FLR

•How to Configure RSVP FLR

•Configuration Examples for RSVP FLR

•Additional References

•Command Reference

•show ip rsvp signalling fast-local-repair

•Glossary

Prerequisites for RSVP FLR

You must configure RSVP on one or more interfaces on at least two neighboring routers that share a link within the network.

Restrictions for RSVP FLR

•RSVP FLR applies only when RSVP is used to set up resource reservations for IPv4 unicast flows; IPv4 multicast flows are not supported.

•RSVP FLR does not apply to traffic engineering (TE) tunnels and, therefore, does not affect TE sessions.

•RSVP FLR does not support message bundling.

Information About RSVP FLR

To use the RSVP FLR feature, you should understand the following concepts:

•Feature Overview of RSVP FLR

•Benefits of RSVP FLR

Feature Overview of RSVP FLR

RSVP FLR provides for dynamic adaptation when routing changes occur. When a route changes, the next PATH and RESV message refreshes establish path and reservation states along the new route. Depending on the configured refresh interval, this reroute happens in tens of seconds. However, during this time, the QoS of flows is not guaranteed because congestion may occur while data packets travel over links where reservations are not yet in place.

In order to provide faster adaptation to routing changes, without the overhead of a refresh period, RSVP registers with the routing information base (RIB) and receives notifications when routes change, thereby triggering state refreshes for the affected destinations. These triggered refreshes use the new route information and, as a result, install reservations over the new path.

When routes change, RSVP has to reroute all affected paths and reservations. Without FLR, the reroute happens when refresh timers expire for the path states. With real time applications such as VoIP and VoD, the requirement changes and the reroute must happen quickly, within three seconds from the triggering event such as link down or link up.

Figure 1 illustrates the FLR process.

Figure 1 Overview of RSVP FLR

Initial RSVP states are installed for an IPv4 unicast flow over Routers A, B, C, D, and E. Router A is the source or headend, while Router E is the destination or tailend. The data packets are destined to an address of Router E. Assume that a route change occurs, and the new path taken by the data packets is from Router A to Router B to Router F to Router D to Router E; therefore, the old and new paths differ on the segments between Routers B and D. The Router B to Router C to Router D segment is the old segment, while the Router B to Router F to Router D segment is the new segment.

A route may change because of a link or node failure, or if a better path becomes available.

RSVP at Router B detects that the route change affects the RSVP flow and initiates the FLR procedure. The node that initiates an FLR repair procedure, Router B in Figure 1, is the point of local repair (PLR). The node where the new and old segments meet, Router D in Figure 1, is the merge point (MP). The interfaces at the PLR and the MP that are part of the old segment are the old interfaces, while the interfaces that are part of the new segment are the new interfaces.

If a route has changed because of a failure, the PLR may not be the node that detects the failure. For example, it is possible that the link from Router C to Router D fails, and although Router C detects the failure, the route change at Router B is the trigger for the FLR procedure. Router C, in this case, is also referred to as the node that detects the failure.

Benefits of RSVP FLR

Faster Response Time to Routing Changes

FLR reduces the time that it takes for RSVP to determine that a physical link has gone down and that the data packets have been rerouted. Without FLR, RSVP may not recognize the link failure for 30 seconds when all of the sessions are impacted by having too much traffic for the available bandwidth. With FLR, this time can be significantly reduced to a few seconds.

After detecting the failure, RSVP recomputes the admission control across the new link. If the rerouted traffic fits on the new link, RSVP reserves the bandwidth and guarantees the QoS of the new traffic.

If admission control fails on the new route, RSVP does not explictly tear down the flow, but instead sends a RESVERROR message towards the receiver. If a proxy receiver is running, then RSVP sends a PATHERROR message towards the headend, in response to the RESVERROR message, indicating the admission failure. In both cases, with and without a proxy receiver, the application tears down the failed session either at the headend or at the final destination.

Until this happens, the data packets belonging to this session still flow over the rerouted segment although admission has failed and QoS is affected.

How to Configure RSVP FLR

You can configure the RSVP FLR parameters in any order that you want.

This section contains the following procedures:

•Configuring the RSVP FLR Wait Time (required)

•Configuring the RSVP FLR Repair Rate (required)

•Configuring the RSVP FLR Notifications (required)

•Verifying the RSVP FLR Configuration (optional)

Configuring the RSVP FLR Wait Time

Perform this task to configure the RSVP FLR wait time.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ip rsvp bandwidth [interface-kbps] [single-flow-kbps]

5. ip rsvp signalling fast-local-repair wait-time interval

6. end

DETAILED STEPS

	Command or Action	Purpose
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	interface type number Example: Router(config)# interface Ethernet0/0	Configures the interface type and enters interface configuration mode.
Step 4	ip rsvp bandwidth [interface-kbps] [single-flow-kbps] Example: Router(config-if)# ip rsvp bandwidth 7500 7500	Enables RSVP on an interface. •The optional interface-kbps and single-flow-kbps arguments specify the amount of bandwidth that can be allocated by RSVP flows or to a single flow, respectively. Values are from 1 to 10000000. Note Repeat this command for each interface on which you want to enable RSVP.
Step 5	ip rsvp signalling fast-local-repair wait-time interval Example: Router(config-if)# ip rsvp signalling fast-local-repair wait-time 100	Configures the delay that RSVP uses before starting an FLR procedure. •Values for the interval argument are 0 to 5000 milliseconds (ms); the default is 0.
Step 6	end Example: Router(config-if)# end	(Optional) Returns to privileged EXEC mode.

Configuring the RSVP FLR Repair Rate

Perform this task to configure the RSVP FLR repair rate.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip rsvp signalling fast-local-repair rate rate

4. exit

DETAILED STEPS

	Command or Action	Purpose
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	ip rsvp signalling fast-local-repair rate rate Example: Router(config)# ip rsvp signalling fast-local-repair rate 100	Configures the repair rate that RSVP uses for an FLR procedure. •Values for the rate argument are 1 to 2500 messages per second; the default is 400. Note See the ip rsvp signalling fast-local-repair rate command for more information.
Step 4	exit Example: Router(config)# exit	(Optional) Returns to privileged EXEC mode.

Configuring the RSVP FLR Notifications

Perform this task to configure the number of RSVP FLR notifications.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip rsvp signalling fast-local-repair notifications number

4. exit

DETAILED STEPS

	Command or Action	Purpose
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	ip rsvp signalling fast-local-repair notifications number Example: Router(config)# ip rsvp signalling fast-local-repair notifications 100	Configures the number of path state blocks (PSBs) that RSVP processes before it suspends. •Values for the number argument are 10 to 10000; the default is 1000.
Step 4	exit Example: Router(config)# exit	(Optional) Returns to privileged EXEC mode.

Verifying the RSVP FLR Configuration

Perform this task to verify the configuration.

---

Note You can use the following show commands in user EXEC or privileged EXEC mode.

---

SUMMARY STEPS

1. enable

2. show ip rsvp signalling fast-local-repair [statistics [detail]]

3. show ip rsvp interface [detail] [interface-type interface-number]

4. show ip rsvp [atm-peak-rate-limit | counters | host | installed | interface | listeners | neighbor | policy | precedence | request | reservation | sbm | sender | signalling | tos]

5. show ip rsvp sender [detail] [filter [destination ip-addr | hostname] [source ip-addr | hostname] [dst-port port] [src-port port]]

6. exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	(Optional) Enables privileged EXEC mode. •Enter your password if prompted. Note Skip this step if you are using the show commands in user EXEC mode.
Step 2	show ip rsvp signalling fast-local-repair [statistics [detail]] Example: Router# show ip rsvp signalling fast-local-repair statistics detail	Displays FLR-specific information that RSVP maintains. •The optional statistics and detail keywords display additional information about the FLR parameters.
Step 3	show ip rsvp interface [detail] [interface-type interface-number] Example: Router# show ip rsvp interface ethernet 1/0	Displays RSVP-related information. •The optional detail keyword displays additional information including FLR parameters.
Step 4	show ip rsvp [atm-peak-rate-limit | counters | host | installed | interface | listeners | neighbor | policy | precedence | request | reservation | sbm | sender | signalling | tos] Example: Router# show ip rsvp	Displays specific information for RSVP categories.
Step 5	show ip rsvp sender [detail] [filter [destination ip-addr | hostname] [source ip-addr | hostname] [dst-port port] [src-port port]] Example: Router# show ip rsvp sender detail	Displays RSVP PATH-related sender information currently in the database. •The optional detail keyword displays additional output including the FLR parameters. Note The optional filter keyword is supported in Cisco IOS Releases 12.0S and 12.2S only.
Step 6	exit Example: Router# exit	(Optional) Exits privileged EXEC mode and returns to user EXEC mode.

Configuration Examples for RSVP FLR

This section provides configuration examples for the RSVP FLR feature.

•Configuring RSVP FLR: Example

•Verifying the RSVP FLR Configuration: Example

Configuring RSVP FLR: Example

The configuration options for RSVP FLR are the following:

•Wait time

•Number of notifications

•Repair rate

---

Note You can configure these options in any order.

---

Configuring the Wait Time

The following example configures Ethernet interface 1/0 with a bandwidth of 200 kbps and a wait time of 1000 msec:

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# interface ethernet1/0

Router(config-if)# ip rsvp bandwidth 200

Router(config-if)# ip rsvp signalling fast-local-repair wait-time 1000

Router(config-if)# end

Configuring the Number of Notifications

The following example configures the number of flows that are repaired before suspending to 100:

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# ip rsvp signalling fast-local-repair notifications 100

Router(config)# end

Configuring the Repair Rate

The following example configures a repair rate of 100 messages per second:

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# ip rsvp signalling fast-local-repair rate 100

Router(config)# end

Verifying the RSVP FLR Configuration: Example

This section contains the following examples:

•Verifying the Details for FLR Procedures

•Verifying Configuration Details for a Specific Interface

•Verifying Configuration Details Before, During, and After an FLR Procedure

Verifying the Details for FLR Procedures

The following example displays detailed information about FLR procedures:

Router# show ip rsvp signalling fast-local-repair statistics detail

Fast Local Repair: enabled

   Max repair rate (paths/sec): 1000

   Max processed   (paths/run): 1000

FLR Statistics:

   FLR 1: DONE

     Start Time: 15:16:32 MET Wed Oct 25 2006

     Number of PSBs repaired:          2496

     Used Repair Rate (msgs/sec):      1000

     RIB notification processing time: 91(ms)

     Time of last PSB refresh:         3111(ms)

     Time of last Resv received:       4355(ms)

     Time of last Perr received:       0(us)

     Suspend count: 2

       Run  Number   Started              Duration

       ID   of ntf.  (time from Start)

       2    498      81(ms)               10(ms)

       1    998      49(ms)               21(ms)

       0    1000     0(us)                22(ms)

     FLR Pacing Unit: 1 msec

     Affected neighbors:

       Nbr Address           Relative Delay Values (msec)

       10.1.0.70             [500   ,..., 2995  ]

Verifying Configuration Details for a Specific Interface

The following example from the show ip rsvp interface detail command displays detailed information, including FLR, for the Ethernet 1/0 interface:

Router# show ip rsvp interface detail ethernet1/0

  Et1/0:

    RSVP: Enabled

    Interface State: Up

    Bandwidth:

      Curr allocated: 9K bits/sec

      Max. allowed (total): 300K bits/sec

      Max. allowed (per flow): 300K bits/sec

      Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec

      Set aside by policy (total): 0 bits/sec

    Traffic Control:

      RSVP Data Packet Classification is ON via CEF callbacks

    Signalling:

      DSCP value used in RSVP msgs: 0x30

      Number of refresh intervals to enforce blockade state: 4

    FLR Wait Time (IPv4 flows):

      Repair is delayed by 1000 msec.

    Authentication: disabled

      Key chain:   <none>

      Type:        md5

      Window size: 1

      Challenge:   disabled

    Hello Extension:

      State: Disabled

Verifying Configuration Details Before, During, and After an FLR Procedure

The following is sample output from the show ip rsvp sender detail command before an FLR procedure has occurred:

Router# show ip rsvp sender detail

PATH:

   Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1

   Sender address: 10.10.10.10, port: 1

   Path refreshes:

     arriving: from PHOP 172.3.31.34 on Et0/0 every 30000 msecs

   Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes

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

   Path ID handle: 01000401.

   Incoming policy: Accepted. Policy source(s): Default

   Status:

   Output on Ethernet1/0. Policy status: Forwarding. Handle: 02000400

     Policy source(s): Default

   Path FLR: Never repaired

The following is sample output from the show ip rsvp sender detail command at the PLR during an FLR procedure:

Router# show ip rsvp sender detail

PATH:

   Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1

   Sender address: 10.10.10.10, port: 1

   Path refreshes:

     arriving: from PHOP 172.16.31.34 on Et0/0 every 30000 msecs

   Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes

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

   Path ID handle: 01000401.

   Incoming policy: Accepted. Policy source(s): Default

   Status:

   Path FLR: PSB is currently being repaired...try later

   PLR - Old Segments: 1

    Output on Ethernet1/0, nhop 172.5.36.34

    Time before expiry: 2 refreshes

    Policy status: Forwarding. Handle: 02000400

       Policy source(s): Default

The following is sample output from the show ip rsvp sender detail command at the MP during an FLR procedure:

Router# show ip rsvp sender detail

PATH:

   Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1

   Sender address: 10.10.10.10, port: 1

   Path refreshes:

     arriving: from PHOP 172.16.37.35 on Et1/0 every 30000 msecs

Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes

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

   Path ID handle: 09000406.

   Incoming policy: Accepted. Policy source(s): Default

   Status: Proxy-terminated

   Path FLR: Never repaired

   MP - Old Segments: 1

    Input on Serial2/0, phop 172.16.36.35

    Time before expiry: 9 refreshes

The following is sample output from the show ip rsvp sender detail command at the PLR after an FLR procedure:

Router# show ip rsvp sender detail

PATH:

   Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1

   Sender address: 10.10.10.10, port: 1

   Path refreshes:

     arriving: from PHOP 172.16.31.34 on Et0/0 every 30000 msecs

   Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes

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

   Path ID handle: 05000401.

   Incoming policy: Accepted. Policy source(s): Default

   Status:

   Output on Serial3/0. Policy status: Forwarding. Handle: 3B000406

     Policy source(s): Default

   Path FLR: Started 12:56:16 EST Thu Nov 16 2006, PSB repaired 532(ms) after.

Resv/Perr: Received 992(ms) after.

Additional References

The following sections provide references related to the RSVP FLR feature.

Related Documents

Related Topic	Document Title
RSVP commands: complete command syntax, command mode, defaults, usage guidelines, and examples	Cisco IOS Quality of Service Solutions Command Reference, Release 12.2SR
QoS features including signaling, classification, and congestion management	Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4

Standards

Standard	Title
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.	—

MIBs

MIB	MIBs Link
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.	To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs

RFCs

RFC	Title
RFC 2205	Resource ReSerVation Protocol (RSVP)—Version 1 Functional Specification
RFC 2209	Resource ReSerVation Protocol (RSVP)—Version 1 Messaging Processing Rules

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.	http://www.cisco.com/techsupport

Command Reference

This section documents only commands that are new or modified.

New Commands

•clear ip rsvp signalling fast-local-repair statistics

•ip rsvp signalling fast-local-repair notifications

•ip rsvp signalling fast-local-repair rate

•ip rsvp signalling fast-local-repair wait-time

•show ip rsvp signalling fast-local-repair

Modified Commands

•show ip rsvp

•show ip rsvp interface

•show ip rsvp sender

clear ip rsvp signalling fast-local-repair statistics

To clear (set to zero) the Resource Reservation Protocol (RSVP) fast local repair (FLR) counters, use the clear ip rsvp signalling fast-local-repair statistics command in user EXEC or privileged EXEC mode.

clear ip rsvp signalling fast-local-repair statistics

Syntax Description

This command has no keywords or arguments.

Command Default

The default is to clear all the RSVP FLR counters.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
12.2(33)SRB	This command was introduced.

Usage Guidelines

Use the clear ip rsvp signalling fast-local-repair statistics command to set all the RSVP FLR counters to zero. The statistics include information about FLR procedures such as the current state, the start time, and the repair rate.

Examples

The following example clears all the RSVP FLR counters being maintained in the database:

Router# clear ip rsvp signalling fast-local-repair statistics

Related Commands

Command	Description
show ip rsvp signalling fast-local-repair	Displays FLR-related information.

ip rsvp signalling fast-local-repair notifications

To configure the number of per flow notifications that Resource Reservation Protocol (RSVP) processes during a fast local repair (FLR) procedure before suspending, use the ip rsvp signalling fast-local-repair notifications command in global configuration mode. To set the number of notifications to its default, use the no form of this command.

ip rsvp signalling fast-local-repair notifications number

no ip rsvp signalling fast-local-repair notifications

Syntax Description

number

Total number of notifications to be sent. The range is 10 to 10000. The default is 1000.

Command Default

There are always notifications sent by the routing information base (RIB) and processed by RSVP. If this command is not configured, RSVP processes 1000 notifications, suspends, then resumes processing of another 1000 notifications, and so on.

Command Modes

Global configuration

Command History

Release	Modification
12.2(33)SRB	This command was introduced.

Usage Guidelines

Upon a route change, RIB builds a list of notifications, one per affected flow, and notifies RSVP by sending an event including these notifications. Therefore, these events can contain thousands of elements depending on the number of path state blocks (PSBs) affected.

RSVP processes, by default, 1000 notifications at a time and then suspends if required, to prevent the CPU from being overwhelmed. However, you can configure this number using the ip rsvp signalling fast-local-repair notifications command.

Examples

The following example configures the number of flows that are repaired before RSVP suspends to 100:

Router(config)# ip rsvp signalling fast-local-repair notifications 100

Related Commands

Command	Description
ip rsvp signalling fast-local-repair rate	Configures the repair rate that RSVP uses for an FLR procedure.
ip rsvp signalling fast-local-repair wait-time	Configures the delay that RSVP uses to start an FLR procedure.
show ip rsvp signalling fast-local-repair	Displays FLR-specific information maintained by RSVP.

ip rsvp signalling fast-local-repair rate

To configure the repair rate that Resource Reservation Protocol (RSVP) uses for a fast local repair (FLR) procedure, use the ip rsvp signalling fast-local-repair rate command in global configuration mode. To set the repair rate to its default, use the no form of this command.

ip rsvp signalling fast-local-repair rate rate

no ip rsvp signalling fast-local-repair rate

Syntax Description

rate	FLR rate for PATH state refresh and repair, in messages per second (msg/sec). The range is 0 to 5000. The default is 400.

Command Default

If this command is not configured, the RSVP message pacing rate is used.

---

Note The RSVP message pacing rate is enabled by default in Cisco IOS Release 12.2 and later.

---

Command Modes

Global configuration

Command History

Release	Modification
12.2(33)SRB	This command was introduced.

Usage Guidelines

The default repair rate is based on the RSVP message pacing rate.

If you configure the FLR rate by using the ip rsvp signalling fast-local-repair rate command, and RSVP message pacing is enabled, the minimum between the FLR rate and the RSVP message pacing rate takes effect. If you disable the RSVP rate limit by using the no ip rsvp signalling rate-limit command, then the FLR rate is used. However, if you disable the RSVP rate limit and do not configure an FLR rate, then RSVP performs no message pacing and messages are sent back-to-back. This action is not recommended because the point of local repair (PLR) may flood the downstream node with PATH messages causing some of them to be dropped.

The repair rate is determined at notification time, and this same rate is used during the time of the repair even if you change either the RSVP message pacing rate or the FLR rate during this time.

Examples

The following example configures a repair rate of 100 messages per second:

Router(config)# ip rsvp signalling fast-local-repair rate 100

Related Commands

Command	Description
ip rsvp signalling fast-local-repair notifications	Configures the number of notifications that are processed before RSVP suspends.
ip rsvp signalling fast-local-repair wait-time	Configures the delay used to start an FLR procedure.
ip rsvp signalling rate-limit	Controls the transmission rate for RSVP messages sent to a neighboring router during a specified amount of time.

ip rsvp signalling fast-local-repair wait-time

To configure the delay that Resource Reservation Protocol (RSVP) uses before starting a fast local repair (FLR) procedure, use the ip rsvp signalling fast-local-repair wait-time command in interface configuration mode. To set the delay to its default, use the no form of this command.

ip rsvp signalling fast-local-repair wait-time interval

no ip rsvp signalling fast-local-repair wait-time

Syntax Description

interval

Amount of time before an FLR procedure begins, in milliseconds (ms). The range is 0 to 5000 ms. The default is 0.

Command Default

This command is disabled by default; therefore, no delay is configured.

Command Modes

Interface configuration

Command History

Release	Modification
12.2(33)SRB	This command was introduced.

Usage Guidelines

Use the ip rsvp signalling fast-local-repair wait-time command to configure the delay desired in starting an FLR procedure. If you do not configure a delay, then path refreshes are triggered immediately after RSVP receives a route change notification from the routing information base (RIB).

Examples

The following example configures a delay of 100 ms:

Router(config-if)# ip rsvp signalling fast-local-repair wait-time 100

Related Commands

Command	Description
ip rsvp signalling fast-local-repair notifications	Configures the number of notifications that are processed before RSVP suspends.
ip rsvp signalling fast-local-repair rate	Configures the repair rate that RSVP uses for an FLR procedure.

show ip rsvp

To display specific information for Resource Reservation Protocol (RSVP) categories, use the show ip rsvp command in user EXEC or privileged EXEC mode.

show ip rsvp [atm-peak-rate-limit | counters | host | installed | interface | listeners | neighbor | policy | precedence | request | reservation | sbm | sender | signalling | tos]

Syntax Description

atm-peak-rate-limit	(Optional) RSVP peak rate limit.
counters	(Optional) RSVP statistics.
host	(Optional) RSVP endpoint senders and receivers.
installed	(Optional) RSVP installed reservations.
interface	(Optional) RSVP interface information.
listeners	(Optional) RSVP listeners.
neighbor	(Optional) RSVP neighbor information.
policy	(Optional) RSVP policy information.
precedence	(Optional) RSVP precedence settings.
request	(Optional) RSVP reservations from upstream.
reservation	(Optional) RSVP reservation requests from downstream.
sbm	(Optional) RSVP subnet bandwidth manager (SBM) information.
sender	(Optional) RSVP path state information.
signalling	(Optional) RSVP signaling information.
tos	(Optional) RSVP type of service (TOS) settings.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
12.0(3)T	This command was introduced.
12.2(13)T	The listeners and policy keywords were added, and this command was modified to display RSVP global settings when no keywords or arguments are entered.
12.2(33)SRB	The command output was modified to display fast local repair (FLR) information.

Examples

The following example includes FLR information:

Router# show ip rsvp

RSVP: enabled (on 4 interface(s))

Signalling:

   Refresh interval (msec): 30000

   Refresh misses: 4

Rate Limiting: enabled

   Burst: 8

   Limit: 37

   Maxsize: 2000

   Period (msec): 20

   Max rate (msgs/sec): 400

Refresh Reduction: disabled

   ACK delay (msec): 250

   Initial retransmit delay (msec): 1000

   Local epoch: 0x7C11BE

   Message IDs: in use 0, total allocated 0, total freed 0

Neighbors: 2

   Raw IP encap: 2  UDP encap: 0  Raw IP, UDP encap: 0

Hello:

   Fast-Reroute/Reroute: Disabled

     Statistics: Disabled

   Graceful Restart: Disabled

Graceful Restart: Disabled

   Refresh interval: 10000 msecs

   Refresh misses: 4

   DSCP: 0x30

   Advertised restart time: 5 msecs

   Advertised recovery time: 0 msecs

   Maximum wait for recovery: 3600000 msecs

Fast-Reroute:

   PSBs w/ Local protection desired

     Yes: 0

     No:  0

Fast Local Repair: enabled

   Max repair rate (paths/sec): 400

   Max processed   (paths/run): 1000

Local policy:

COPS:

Generic policy settings:

     Default policy: Accept all

     Preemption:     Disabled

Table 1 describes the significant fields shown in the display.

Table 1 show ip rsvp Field Descriptions 

Field	Description
RSVP: enabled or disabled	The state of RSVP. Note This field is disabled only if an internal error occurred when registering with RIB.
Signalling	The RSVP signaling parameters in effect are as follows: •Refresh interval—Time, in milliseconds (ms), between sending refreshes for each RSVP state. •Refresh misses—Number of successive refresh messages that can be missed before RSVP considers the state expired and tears it down.
Rate Limiting: enabled or disabled	The RSVP rate-limiting parameters in effect are as follows: •Burst—Maximum number of RSVP messages allowed to be sent to a neighboring router during an interval. •Limit—Maximum number of RSVP messages to send per queue interval. •Maxsize—Maximum size of the message queue, in bytes. •Period—Length of an interval (timeframe), in milliseconds (msec). •Max rate—Maximum number of messages allowed to be sent per second.
Refresh Reduction: enabled or disabled	The RSVP refresh-reduction parameters in effect are as follows: •ACK delay (msec)—How long, in milliseconds, before the receiving router sends an acknowledgment (ACK). •Initial retransmit delay (msec)—How long, in milliseconds, before the router retransmits a message. •Local epoch—The RSVP message identifier (ID); randomly generated each time a node reboots or the RSVP process restarts. •Message IDs—The number of message IDs in use, the total number allocated, and the total number available (freed).
Neighbors	The total number of neighbors and the types of encapsulation in use including RSVP and User Datagram Protocol (UDP).
Hello	Subsequent fields describe the processes for which hello is enabled or disabled. Choices are Fast Reroute, reroute (hello for state timer), and Graceful restart for a node with restart capability.
Statistics	Status of hello statistics. Valid values are as follows: •Enabled—Statistics are configured. Hello packets are time-stamped when they arrive in the hello input queue for the purpose of recording the time it takes until they are processed. •Disabled—Hello statistics are not configured. •Shutdown—Hello statistics are configured, but not operational. The input queue is too long (that is, more than 10,000 packets are queued).
Graceful Restart: enabled or disabled	The RSVP Graceful Restart parameters in effect are as follows: •Refresh interval—Frequency, in milliseconds (msecs), with which a node sends a hello message to its neighbor. •Refresh misses—Number of missed hello messages that trigger a neighbor-down event upon which stateful switchover (SSO) procedures are started. •DSCP—Differentiated services code point (DSCP) value in the IP header of a hello message. •Advertised restart time—Time, in milliseconds (msecs), required for the sender to restart the RSVP-Traffic Engineering (TE) component and exchange hello messages after a failure. •Advertised recovery time—Time, in milliseconds (msecs), within which a recovering node wants its neighbor router to resynchronize the RSVP or Multiprotocol Label Switching (MPLS) forwarding state after SSO. A zero value indicates that the RSVP or MPLS forwarding state is not preserved after SSO. •Maximum wait for recovery—Maximum amount of time, in milliseconds (msecs), that a router waits for a neighbor to recover.
Fast-Reroute	The Fast Reroute parameters in effect are as follows: •PSBs w/ Local protection desired—Yes means that path state blocks (PSBs) are rerouted when a tunnel goes down and packet flow is not interrupted; No means that PSBs are not rerouted.
Fast Local Repair: enabled or disabled	The Fast Local Repair parameters in effect are as follows: •Max repair rate (paths/sec)—Maximum repair rate, in paths per second. •Max processed (paths/run)—Maximum notification elements processed, in paths per run.
Local policy	The local policy currently configured.
COPS	The Common Open Policy Service (COPS) currently in effect.
Generic policy settings	Policy settings that are not specific to COPS or the local policy. •Default policy: Accept all means that all RSVP messages are accepted and forwarded. Reject all means all RSVP messages are rejected. •Preemption: Disabled means that RSVP is not prioritizing reservations and allocating bandwidth accordingly. Enabled means that RSVP is prioritizing reservations and allocating more bandwidth to those with the highest priority.

Related Commands

Command	Description
debug ip rsvp	Displays debug messages for RSVP categories.

show ip rsvp interface

To display Resource Reservation Protocol (RSVP)-related information, use the show ip rsvp interface command in user EXEC or privileged EXEC mode.

show ip rsvp interface [interface-type interface-number] [detail]

Syntax Description

interface-type	(Optional) Type of the interface.
interface-number	(Optional) Number of the interface.
detail	(Optional) Displays additional information about interfaces.

Command Modes

User EXEC
Privileged EXEC

Command History

Release	Modification
11.2	This command was introduced.
12.2(2)T	The optional detail keyword was added.
12.2(4)T	This command was implemented on the Cisco 7500 series and the ATM permanent virtual circuit (PVC) interface.
12.0(22)S	The command output was modified to display hello message information.
12.2(14)S	This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(13)T	The following modifications were made to this command: •Rate-limiting and refresh-reduction information was added to the output display. •RSVP global settings display when no keywords or arguments are entered.
12.2(15)T	The following modifications were made to this command: •The effects of compression on admission control and the RSVP bandwidth limit counter were added to the display. •Cryptographic authentication parameters were added to the display.
12.2(18)SFX2	This command was integrated into Cisco IOS Release 12.2(18)SFX2.
12.2(28)SB	This command was integrated into Cisco IOS Release 12.2(28)SB.
12.2(33)SRA	This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SRB	The command output was modified to display fast local repair (FLR) information.

Usage Guidelines

<