Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IOS Software Releases 12.2 SX

NSF/SSO--MPLS TE and RSVP Graceful Restart

Downloads

Table Of Contents

NSF/SSO—MPLS TE and RSVP Graceful Restart

Content

Prerequisites for NSF/SSO—MPLS TE and RSVP Graceful Restart

Restrictions for NSF/SSO—MPLS TE and RSVP Graceful Restart

Information About NSF/SSO—MPLS TE and RSVP Graceful Restart

Overview of MPLS TE and RSVP Graceful Restart

Benefits of MPLS TE and RSVP Graceful Restart

How to Configure NSF/SSO—MPLS TE and RSVP Graceful Restart

Enabling RSVP Graceful Restart Globally

Enabling RSVP Graceful Restart on an Interface

Setting a DSCP Value

Setting a Value to Control the Hello Refresh Interval

Setting a Value to Control the Missed Refresh Limit

Verifying the RSVP Graceful Restart Configuration

Configuration Examples for NSF/SSO—MPLS TE and RSVP Graceful Restart

Configuring NSF/SSO—MPLS TE and RSVP Graceful Restart: Example

Verifying the NSF/SSO—MPLS TE and RSVP Graceful Restart Configuration: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

clear ip rsvp high-availability counters

debug ip rsvp high-availability

debug ip rsvp sso

debug mpls traffic-eng ha sso

ip rsvp signalling hello graceful-restart dscp

ip rsvp signalling hello graceful-restart mode

ip rsvp signalling hello graceful-restart mode help-neighbor

ip rsvp signalling hello graceful-restart neighbor

ip rsvp signalling hello graceful-restart refresh interval

ip rsvp signalling hello graceful-restart refresh misses

show ip rsvp counters

show ip rsvp counters state teardown

show ip rsvp hello

show ip rsvp hello client lsp detail

show ip rsvp hello client lsp summary

show ip rsvp hello client neighbor detail

show ip rsvp hello client neighbor summary

show ip rsvp hello graceful-restart

show ip rsvp hello instance detail

show ip rsvp hello instance summary

show ip rsvp high-availability counters

show ip rsvp high-availability database

show ip rsvp high-availability summary

Feature Information for NSF/SSO—MPLS TE and RSVP Graceful Restart

Glossary


NSF/SSO—MPLS TE and RSVP Graceful Restart

First Published: August 2, 2004
Last Updated: June 29, 2007

The NSF/SSO—MPLS TE and RSVP Graceful Restart feature allows a Route Processor (RP) to recover from disruption in control plane service without losing its Multiprotocol Label Switching (MPLS) forwarding state.

Cisco nonstop forwarding (NSF) with stateful switchover (SSO) provides continuous packet forwarding, even during a network processor hardware or software failure. In a redundant system, the secondary processor recovers control plane service during a critical failure in the primary processor. SSO synchronizes the network state information between the primary and the secondary processor.

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 NSF/SSO—MPLS TE and RSVP Graceful Restart" 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.

Content

•Prerequisites for NSF/SSO—MPLS TE and RSVP Graceful Restart

•Restrictions for NSF/SSO—MPLS TE and RSVP Graceful Restart

•Information About NSF/SSO—MPLS TE and RSVP Graceful Restart

•How to Configure NSF/SSO—MPLS TE and RSVP Graceful Restart

•Configuration Examples for NSF/SSO—MPLS TE and RSVP Graceful Restart

•Additional References

•Command Reference

•Feature Information for NSF/SSO—MPLS TE and RSVP Graceful Restart

•Glossary

Prerequisites for NSF/SSO—MPLS TE and RSVP Graceful Restart

•Configure Resource Reservation Protocol (RSVP) graceful restart in full mode.

•Configure RSVP graceful restart on all interfaces of the neighbor that you want to be restart-capable.

•Configure the redundancy mode as SSO. See the Stateful Switchover feature module for more information.

•Enable NSF on the routing protocols running among the provider routers (P), provider edge (PE) routers, and customer edge (CE) routers. The routing protocols are as follows:

–Border Gateway Protocol (BGP)

–Open Shortest Path First (OSPF)

–Intermediate System-to-Intermediate System (IS-IS)

See the Cisco Nonstop Forwarding feature module for more information.

•Enable MPLS.

•Configure traffic engineering (TE).

Restrictions for NSF/SSO—MPLS TE and RSVP Graceful Restart

•RSVP graceful restart supports node failure only.

•Unnumbered interfaces are not supported.

•You cannot enable RSVP fast reroute (FRR) hello messages and RSVP graceful restart on the same router.

•Configure this feature on Cisco 7600 series routers with dual RPs only.

•You cannot enable primary one-hop autotunnels, backup autotunnels, or autotunnel mesh groups on a router that is also configured with SSO and Route Processor Redundancy Plus (RPR+). This restriction does not prevent an MPLS TE tunnel that is automatically configured by TE autotunnel from being successfully recovered if any midpoint router along the label-switched path (LSP) of the router experiences an SSO.

•MPLS TE LSPs that are fast reroutable cannot be successfully recovered if the LSPs are FRR active and the Point of Local Repair (PLR) router experiences an SSO.

•When you configure RSVP graceful restart, you must use the neighbor's interface IP address.

Information About NSF/SSO—MPLS TE and RSVP Graceful Restart

To configure the NSF/SSO—MPLS TE and RSVP Graceful Restart feature, you should understand the following concepts:

•Overview of MPLS TE and RSVP Graceful Restart

•Benefits of MPLS TE and RSVP Graceful Restart

Overview of MPLS TE and RSVP Graceful Restart

RSVP graceful restart allows RSVP TE-enabled nodes to recover gracefully following a node failure in the network such that the RSVP state after the failure is restored as quickly as possible. The node failure may be completely transparent to other nodes in the network.

RSVP graceful restart preserves the label values and forwarding information and works with third-party or Cisco routers seamlessly.

RSVP graceful restart depends on RSVP hello messages to detect that a neighbor went down. Hello messages include Hello Request or Hello Acknowledgment (ACK) objects between two neighbors.

As shown in Figure 1, the RSVP graceful restart extension to these messages adds an object called Hello Restart_Cap, which tells neighbors that a node may be capable of recovering if a failure occurs.

Figure 1 How RSVP Graceful Restart Works

The Hello Restart_Cap object has two values: the restart time, which is the sender's time to restart the RSVP_TE component and exchange hello messages after a failure; and the recovery time, which is the desired time that the sender wants the receiver to synchronize the RSVP and MPLS databases.

In Figure 1, RSVP graceful restart help neighbor support is enabled on Routers 1 and 3 so that they can help a neighbor recover after a failure, but they cannot perform self recovery. Router 2 has full SSO help support enabled, meaning it can perform self recovery after a failure or help its neighbor to recover. Router 2 has two RPs, one that is active and one that is standby (backup). A TE LSP is signaled from Router 1 to Router 4.

Router 2 performs checkpointing; that is, it copies state information from the active RP to the standby RP, thereby ensuring that the standby RP has the latest information. If an active RP fails, the standby RP can take over.

Routers 2 and 3 exchange periodic graceful restart hello messages every 10,000 milliseconds (ms) (10 seconds), and so do Routers 2 and 1 and Routers 3 and 4. Assume that Router 2 advertises its restart time = 60,000 ms (60 seconds) and its recovery time = 60,000 ms (60 seconds) as shown in the following example: 

23:33:36: Outgoing Hello:

23:33:36:   version:1 flags:0000 cksum:883C ttl:255 reserved:0 length:32

23:33:36:  HELLO                type HELLO REQUEST length 12:

23:33:36:   Src_Instance: 0x6EDA8BD7, Dst_Instance: 0x00000000

23:33:36:  RESTART_CAP          type 1 length 12:

23:33:36:   Restart_Time: 0x0000EA60, Recovery_Time: 0x0000EA60

Router 3 records this into its database. Also, both neighbors maintain the neighbor status as UP. However, Router 3's control plane fails at some point (for example, a primary RP failure). As a result, RSVP and TE lose their signaling information and states although data packets continue to be forwarded by the line cards.

When Router 3 declares communication with Router 2 lost, Router 3 starts the restart time to wait for the duration advertised in Router 2's restart time previously recorded (60 seconds). Routers 1 and 2 suppress all RSVP messages to Router 3 except hellos. Router 3 keeps sending the RSVP PATH and RESV refresh messages to Routers 4 and 5 so that they do not expire the state for the LSP; however, Routers 1 and 3 suppress these messages for Router 2.

When Routers 1 and 3 receive the hello message from Router 2, Routers 1 and 3 check the recovery time value in the message. If the recovery time is 0, Router 3 knows that Router 2 was not able to preserve its forwarding information, and Routers 1 and 3 delete all RSVP state that they had with Router 2.

If the recovery time is greater than 0, Router 1 sends Router 2 PATH messages for each LSP that it had previously sent through Router 2. If these messages were previously refreshed in summary messages, they are sent individually during the recovery time. Each of these PATH messages includes a Recovery_Label object containing the label value received from Router 2 before the failure.

When Router 3 receives a PATH message from Router 2, Router 3 sends a RESV message upstream. However, Router 3 suppresses the RESV message until it receives a PATH message. When Router 2 receives the RESV message, it installs the RSVP state and reprograms the forwarding entry for the LSP.

Benefits of MPLS TE and RSVP Graceful Restart

State Information Recovery

RSVP graceful restart allows a node to perform self recovery or to help its neighbor recover state information when there is an RP failure or the device has undergone an SSO.

Session Information Recovery

RSVP graceful restart allows session information recovery with minimal disruption to the network.

Increased Availability of Network Services

A node can perform a graceful restart to help itself or a neighbor recover its state by keeping the label bindings and state information, thereby providing a faster recovery of the failed node and not affecting currently forwarded traffic.

How to Configure NSF/SSO—MPLS TE and RSVP Graceful Restart

This section contains the following procedures:

•Enabling RSVP Graceful Restart Globally (required)

•Enabling RSVP Graceful Restart on an Interface (required)

•Setting a DSCP Value (optional)

•Setting a Value to Control the Hello Refresh Interval (optional)

•Setting a Value to Control the Missed Refresh Limit (optional)

•Verifying the RSVP Graceful Restart Configuration (optional)

Enabling RSVP Graceful Restart Globally

Perform this task to enable RSVP graceful restart globally.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip rsvp signalling hello graceful-restart mode {help-neighbor | full}

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 hello graceful-restart mode (help-neighbor | full)

Example:

Router(config)# ip rsvp signalling hello graceful-restart mode full

Enables RSVP TE graceful restart capability on an RP.

•Enter the help-neighbor keyword to enable a neighboring router to restart after a failure.

•Enter the full keyword to enable a router to perform self recovery or to help a neighbor recover after a failure.

Step 4 

exit

Example:

Router(config)# exit

(Optional) Returns to privileged EXEC mode.

Enabling RSVP Graceful Restart on an Interface

Perform this task to enable RSVP graceful restart on an interface.

Note You must repeat this procedure for each of the neighbor router's interfaces.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. Repeat Step 3 as needed to configure additional interfaces.

5. ip rsvp signalling hello graceful-restart neighbor ip-address

6. Repeat Step 5 as needed to configure additional IP addresses on a neighbor router's interfaces.

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

interface type number

Example:

Router(config)# interface POS 1/0/0

Configures the interface type and number and enters interface configuration mode.

Step 4 

Repeat Step 3 as needed to configure additional interfaces.

(Optional) Configures additional interfaces.

Step 5 

ip rsvp signalling hello graceful-restart neighbor ip-address

Example:

Router(config-if)# ip rsvp signalling hello graceful-restart neighbor 10.0.0.0

Enables support for RSVP graceful restart on routers helping their neighbors recover TE tunnels following SSO.

Note The IP address must be that of the neighbor's interface.

Step 6 

Repeat Step 5 as needed to configure additional IP addresses on a neighbor router's interfaces.

(Optional) Configures additional IP addresses on a neighbor router's interfaces.

Step 7 

exit

Example:

Router(config-if)# exit

(Optional) Returns to privileged EXEC mode.

Setting a DSCP Value

Perform this task to set a differentiated services code point (DSCP) value.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip rsvp signalling hello graceful-restart dscp num

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 hello graceful-restart dscp num

Example:

Router(config)# ip rsvp signalling hello graceful-restart dscp 30

Sets a DSCP value on a router with RSVP graceful restart enabled.

Step 4 

exit

Example:

Router(config)# exit

(Optional) Returns to privileged EXEC mode.

Setting a Value to Control the Hello Refresh Interval

Perform this task to set a value to control the hello refresh interval.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip rsvp signalling hello graceful-restart refresh interval interval-value

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 hello graceful-restart refresh interval interval-value

Example:

Router(config)# ip rsvp signalling hello graceful-restart refresh interval 5000

Sets the value to control the request interval in graceful restart hello messages. This interval represents the frequency at which RSVP hello messages are sent to a neighbor; for example, one hello message is sent per each interval.

Note If you change the default value for this command and you also changed the RSVP refresh interval using the ip rsvp signalling refresh interval command, ensure that the value for the ip rsvp signalling hello graceful-restart refresh interval command is less than the value for the ip rsvp signalling hello refresh interval command. Otherwise, some or all of the label-switched paths (LSPs) may not be recovered after an SSO has occurred.

Step 4 

exit

Example:

Router(config)# exit

(Optional) Returns to privileged EXEC mode.

Setting a Value to Control the Missed Refresh Limit

Perform this task to set a value to control the missed refresh limit.

SUMMARY STEPS

1. enable

2. configure terminal

3. ip rsvp signalling hello graceful-restart refresh misses msg-count

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 hello graceful-restart refresh misses msg-count

Example:

Router(config)# ip rsvp signalling hello graceful-restart refresh misses 5

Specifies how many sequential RSVP TE graceful restart hello acknowledgments (ACKs) a node can miss before the node considers communication with its neighbor lost.

Note If you change the default value for this command and you are also using the ip rsvp signalling hello refresh misses command, ensure that the value for the ip rsvp signalling hello graceful-restart refresh misses command is less than the value for the ip rsvp signalling hello refresh misses command. Otherwise, some or all of the LSPs may not be recovered after an SSO has occurred.

Step 4 

exit

Example:

Router(config)# exit

(Optional) Returns to privileged EXEC mode.

Verifying the RSVP Graceful Restart Configuration

Perform this task to verify the RSVP graceful restart configuration.

SUMMARY STEPS

1. enable

2. show ip rsvp hello graceful-restart

3. exit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

(Optional) Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

show ip rsvp hello graceful-restart

Example:

Router# show ip rsvp hello graceful-restart

Displays information about the status of RSVP graceful restart and related parameters.

Step 3 

exit

Example:

Router# exit

(Optional) Returns to user EXEC mode.

Configuration Examples for NSF/SSO—MPLS TE and RSVP Graceful Restart

This section provides the following configuration examples:

•Configuring NSF/SSO—MPLS TE and RSVP Graceful Restart: Example

•Verifying the NSF/SSO—MPLS TE and RSVP Graceful Restart Configuration: Example

Configuring NSF/SSO—MPLS TE and RSVP Graceful Restart: Example

In the following example, RSVP graceful restart is enabled globally and on a neighbor router's interfaces as shown in Figure 2. Related parameters, including a DSCP value, a refresh interval, and a missed refresh limit are set.

Figure 2 Sample Network Configuration

enable

configure terminal

ip rsvp signalling hello graceful-restart mode full

interface POS 1/0/0

 ip rsvp signalling hello graceful-restart neighbor 10.0.0.1 

 ip rsvp signalling hello graceful-restart neighbor 10.0.0.2 

 exit

ip rsvp signalling hello graceful-restart dscp 30

ip rsvp signalling hello graceful-restart refresh interval 50000

ip rsvp signalling hello graceful-restart refresh misses 5 

exit

Verifying the NSF/SSO—MPLS TE and RSVP Graceful Restart Configuration: Example

The following example verifies the status of RSVP graceful restart and the configured parameters: 

Router# show ip rsvp hello graceful-restart


Graceful Restart: Enabled (full mode)

  Refresh interval: 10000 msecs

  Refresh misses: 4

  DSCP:0x30

  Advertised restart time: 30000 msecs

  Advertised recovery time: 120000 msecs

  Maximum wait for recovery: 3600000 msecs

Additional References

The following sections provide references related to the NSF/SSO—MPLS TE and RSVP Graceful Restart 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.2SX

Quality of service (QoS) features including signaling, classification, and congestion management

Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4

Stateful switchover

Stateful Switchover feature module

Cisco nonstop forwarding

Cisco Nonstop Forwarding feature module

Information on stateful switchover, Cisco nonstop forwarding, graceful restart

NSF/SSO - MPLS LDP and LDP Graceful Restart feature module

Hello messages for state timeout

MPLS Traffic Engineering—RSVP Hello State Timer feature module


Standards

Standards
Title

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

—


MIBs

MIBs
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

RFCs
Title

RFC 3209

RSVP-TE: Extensions to RSVP for LSP Tunnels

RFC 3473

Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions

RFC 4558

Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement


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.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport


Command Reference

This section documents only commands that are new or modified.

•clear ip rsvp high-availability counters

•debug ip rsvp high-availability

•debug ip rsvp sso

•debug mpls traffic-eng ha sso

•ip rsvp signalling hello graceful-restart dscp

•ip rsvp signalling hello graceful-restart mode

•ip rsvp signalling hello graceful-restart mode help-neighbor

•ip rsvp signalling hello graceful-restart neighbor

•ip rsvp signalling hello graceful-restart refresh interval

•ip rsvp signalling hello graceful-restart refresh misses

•show ip rsvp counters

•show ip rsvp counters state teardown

•show ip rsvp hello

•show ip rsvp hello client lsp detail

•show ip rsvp hello client lsp summary

•show ip rsvp hello client neighbor detail

•show ip rsvp hello client neighbor summary

•show ip rsvp hello graceful-restart

•show ip rsvp hello instance detail

•show ip rsvp hello instance summary

•show ip rsvp high-availability counters

•show ip rsvp high-availability database

•show ip rsvp high-availability summary

clear ip rsvp high-availability counters

To clear (set to zero) the Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) counters that are being maintained by a Route Processor (RP), use the clear ip rsvp high-availability counters command in privileged EXEC mode.

clear ip rsvp high-availability counters

Syntax Description

This command has no arguments or keywords.

Command Default

No counters are cleared until you issue the command.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(33)SRA

This command was introduced.

12.2(33)SRB

Support for In-Service Software Upgrade (ISSU) was added.

12.2(33)SXH

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


Usage Guidelines

Use the clear ip rsvp high-availability counters command to clear (set to zero) the HA counters, which include state, ISSU, resource failures, and historical information.

Examples

The following example clears all the HA information currently being maintained by the RP:

Router# clear ip rsvp high-availability counters

Related Commands

Command
Description

show ip rsvp high-availability counters

Displays the RSVP-TE HA counters that are being maintained by an RP.


debug ip rsvp high-availability

To display debugging output for Resource Reservation Protocol traffic engineering (RSVP-TE) high availability (HA) activities that improve the accessibility of network resources, use the debug ip rsvp high-availability command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug ip rsvp high-availability {all | database | errors | events | fsm | issu | messages}

no debug ip rsvp high-availability {all | database | errors | events | fsm | issu | messages}

Syntax Description

all

Displays debugging output for all RSVP-TE HA categories except for the dumping of messages.

database

Displays information about read and write operations to and from the checkpointed database during the RSVP-TE HA activities.

errors

Displays errors encountered by RSVP-TE during HA activities.

events

Displays significant RSVP-TE stateful switchover (SSO) events during RSVP-TE HA activities, such as:

•RSVP-TE process events

•RSVP-TE Route Processor (RP) state (active, standby, and recovery) changes

•Recovery period beginning and end

•Redundant Facility (RF) events handled by RSVP-TE

fsm

Displays significant events for the RSVP-TE checkpointed database finite state machine (fsm) during the RSVP-TE HA activities.

issu

Displays information about RSVP-TE In-Service Software Upgrade (ISSU) activity.

messages

Displays information about Checkpointing Facility (CF) messages sent by RSVP-TE between the active RP and the standby RP.


Command Default

Debugging is not enabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(33)SRA

This command was introduced.

12.2(33)SRB

Support for ISSU was added.

12.2(33)SXH

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


Usage Guidelines

This command displays information about RSVP-TE activities, before and after SSO, that improve the availability of network resources and services.

Examples

The following example is sample output from the debug ip rsvp high-availability all command, which turns on debugging for IP RSVP-TE HA events, messages, database, errors, fsm, and ISSU: 

Router# debug ip rsvp high-availability all


RSVP HA all debugging is on 


Router# show debug        <---- This command displays the debugging that is enabled.


IP RSVP HA debugging is on for: 

   events

   messages

   database

   errors

   fsm

   issu

This sample debugging output is displayed as an SSO recovery begins on the standby router in the process of the standby router becoming active.

Note The prefix in the debug output is composed of label switched path (LSP) 5-tuples in the following format: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]. The 10.0.0.3 represents the source address, the 61 represents the LSP ID, the 10.0.0.9 represents the tunnel destination (tunnel tail), the10 represents the tunnel ID, and the [10.0.0.3] represents the extended tunnel ID. 

*May 12 19:46:14.267: RSVP-HA: session 
65.39.97.4_18698[0.0.0.0]:rsvp_ha_read_lsp_head_info: Read LSP Head info: tun_id: 10

*May 12 19:46:14.267: RSVP-HA: session 10.0.0.1_10[0.0.0.0]: rsvp_ha_db_entry_find: 
lsp_head entry found

*May 12 19:46:14.267: rsvp_ha_read_lsp_head_info: entry found

*May 12 19:46:14.267: RSVP-HA:rsvp_ha_read_lsp_head_info: Read LSP Head info: tun_id: 10

*May 12 19:46:14.267: RSVP-HA: session 10.221.123.48_10[0.0.0.0]: rsvp_ha_db_entry_find: 
lsp_head entry found

*May 12 19:46:14.267: rsvp_ha_read_lsp_head_info: entry found

*May 12 19:46:15.995: %SYS-5-CONFIG_I: Configured from console by console

*May 12 19:46:20.803: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: rsvp_ha_db_entry_find: 
lsp entry found

*May 12 19:46:20.803: rsvp_ha_read_generic_info: lsp entry found

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]:rsvp_ha_write_generic_info: 
Writing lsp_head info

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]: rsvp_ha_db_entry_find: 
lsp_head entry not found

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]: 
rsvp_ha_handle_wr_entry_not_found: 

entry not found, type =lsp_head, action: Add

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]: rsvp_ha_db_entry_create: 
Created lsp_head entry

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]:rsvp_ha_set_entry_state: None 
-> Send-Pending

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]: rsvp_ha_db_wavl_entry_insert: 
Inserted entry into lsp_head Write DB, Send_Pending tree

*May 12 19:46:20.807: RSVP-HA: session 
10.0.0.9_10[0.0.0.0]:rsvp_ha_fsm_wr_event_add_entry: add lsp_head entry to Write DB

*May 12 19:46:20.807: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_write_generic_info: Writing lsp info

*May 12 19:46:20.807: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: rsvp_ha_db_entry_find: 
lsp entry not found

*May 12 19:46:20.807: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_handle_wr_entry_not_found: entry not found, type =lsp, action: Add

*May 12 19:46:20.807: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_db_entry_create: Created lsp entry

*May 12 19:46:20.807: RSVP-HA:10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_set_entry_state: None -> Send-Pending

*May 12 19:46:20.807: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_db_wavl_entry_insert: Inserted entry into lsp Write DB, Send_Pending tree

*May 12 19:46:20.807: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_fsm_wr_event_add_entry: add lsp entry to Write DB

*May 12 19:46:20.807: rsvp_ha_rd_remove_lsp_head_info: Event RD: remove lsp_head_info

*May 12 19:46:20.807: RSVP-HA: session 10.27.90.140_10[0.0.0.0]:  
rsvp_ha_db_entry_find: lsp_head entry found

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]: rsvp_ha_db_wavl_entry_remove: 
Removed entry from lsp_head Read DB, Checkpointed tree

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]: rsvp_ha_db_entry_free: 
Freeing lsp_head entry

*May 12 19:46:20.807: RSVP-HA: session 10.0.0.9_10[0.0.0.0]:rsvp_ha_set_entry_state: 
Checkpointed -> None

.

.

.

The following example shows how to turn debugging off for this command: 

Router# no debug ip rsvp high-availability all


RSVP HA all debugging is off

Related Commands

Command
Description

debug ip rsvp sso

Displays debugging output for RSVP signalling when the graceful restart feature is configured.

debug mpls traffic-eng ha sso

Displays debugging output for MPLS traffic engineering HA activities during the graceful switchover from an active RP to a redundant standby RP.


debug ip rsvp sso

To display debugging output for Resource Reservation Protocol (RSVP) signaling when the graceful restart feature is configured, use the debug ip rsvp sso command in privileged EXEC mode. To disable debugging, use the no form of this command.

debug ip rsvp sso

no debug ip rsvp sso

Syntax Description

This command has no arguments or keywords.

Command Default

Debugging is disabled.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(33)SRA

This command was introduced.

12.2(33)SXH

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


Usage Guidelines

This command displays debugging output from RSVP signaling during and after the Route Processor (RP) stateful switchover when system control and routing protocol execution is transferred from the active RP to the redundant standby RP. The SSO process occurs when the active router becomes unavailable, so that no interruption of network services occurs. The command displays information about the activities that RSVP performs when you configure a graceful restart, such as:

•Writing checkpointing information into the write database when a new traffic engineering (TE) label switched path (LSP) is signaled on the active RP

•Recovering the LSP checkpointed information from the read database after SSO

•Displaying information about LSPs not recovered

Examples

The following is sample output from the debug ip rsvp sso command that was displayed during a successful SSO on the standby router as it became active: 

Router# debug ip rsvp sso


RSVP sso debugging is on 


Router#

Note The prefix in the debug output is composed of LSP 5-tuples in the following format: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]. The 10.0.0.3 represents the source address, the 61 represents the LSP ID, the 10.0.0.9 represents the tunnel destination (tunnel tail), the10 represents the tunnel ID, and the [10.0.0.3] represents the extended tunnel ID. 

*May 12 20:12:38.175: RSVP-HA: begin recovery, send msg to RSVP

*May 12 20:12:38.175: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: event: new Path received 
during RSVP or IGP recovery period

*May 12 20:12:38.175: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_sb_event_new_path_received: lsp_info found, attempt to recover lsp

*May 12 20:12:38.175: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: set psb_is_recovering flag

*May 12 20:12:38.179: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]:rsvp_ha_sb_set_path_info: 
Recovering: Set next_hop and next_idb in psb

*May 12 20:12:38.179: RSVP: 
10.0.0.3_61->10.0.0.9_10[10.0.0.3]:rsvp_ha_mark_lsp_if_recoverable: LSP is recoverable 
(ERO expansion. not needed)

*May 12 20:12:38.179: RSVP-HA: rsvp_ha_sb_handle_recovery_start: Recovery period start: 
set GR recovery time.

*May 12 20:12:38.179: RSVP_HA: checkpoint hello_globals_info

*May 12 20:12:38.179: RSVP-HELLO: rsvp_ha_update_all_gr_hi: Updating all GR HIs with new 
src_instance

*May 12 20:12:38.183: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: prevent populating output; 
LSP is recovering

*May 12 20:12:38.187: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: prevent populating output; 
LSP is recovering

*May 12 20:12:38.939: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_sb_event_new_resv_received: event: Resv for LSP received during recovery period

*May 12 20:12:38.943: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_event_lsp_create_head: psb found

*May 12 20:12:38.943: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_event_lsp_create_head: event: LSP created at head-end, try to checkpoint it

*May 12 20:12:38.943: RSVP: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: LSP was checkpointed

*May 12 20:12:38.943: RSVP-HA: 10.0.0.3_61->10.0.0.9_10[10.0.0.3]: 
rsvp_ha_sb_event_lsp_head_recovered: event: LSP head was recovered

*May 12 20:12:38.943: RSVP-HA: recovery period over, send msg to RSVP

*May 12 20:12:38.947: RSVP-HA: rsvp_ha_sb_handle_recovery_end: Deleting state for LSPs not 
recovered

Router#

The following example shows how to turn debugging off for this command: 

Router# no debug ip rsvp sso


RSVP sso debugging is off

Related Commands

Command
Description

debug ip rsvp high-availability

Displays debugging output for RSVP-TE HA activities that improve the accessibility of network resources.

debug mpls traffic-eng ha sso

Displays debugging output for MPLS traffic engineering HA activities during the graceful switchover from an active RP to a redundant standby RP.


debug mpls traffic-eng ha sso

To display debugging output for Multiprotocol Label Switching (MPLS) traffic engineering high availability (HA) activities during the graceful switchover from an active Route Processor (RP) to a redundant standby RP, use the debug mpls traffic-eng ha sso command in privileged EXEC mode. To disable debugging output, use the no form of this command.

debug mpls traffic-eng ha sso {auto-tunnel | errors | link-management {events | standby | recovery | checkpoint} | tunnel {events | standby | recovery}}

no debug mpls traffic-eng ha sso {auto-tunnel | errors | link-management {events | standby | recovery | checkpoint} | tunnel {events | standby | recovery}}

Syntax Description

auto-tunnel

Displays information about autotunnel activity during the MPLS traffic engineering stateful switchover (SSO) process.

errors

Displays errors encountered during the MPLS traffic engineering SSO process.

link-management

Displays information about link management activity during the MPLS traffic engineering SSO process.

events

Displays significant events that occur during the MPLS traffic engineering SSO process.

standby

Displays information about the standby behavior during the MPLS traffic engineering SSO process.

recovery

Displays information about recovery activity during the MPLS traffic engineering SSO process.

checkpoint

Display information about checkpointing activities during the MPLS traffic engineering SSO process. Checkpointing occurs when a message is sent and acknowledged.

tunnel

Displays information about tunnel activity during the MPLS traffic engineering SSO process.


Command Default

Debugging is disabled until you issue this command with one or more keywords.

Command Modes

Privileged EXEC

Command History

Release
Modification

12.2(33)SRA

This command was introduced.

12.2(33)SXH

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


Usage Guidelines

This command displays debugging output about the SSO process for MPLS traffic engineering tunnels, autotunnels, and link management systems. The SSO process occurs when the active router becomes unavailable and system control and routing protocol execution is transferred from the now inactive RP to the redundant standby RP, thus providing uninterrupted network services.

Examples

The following is sample output from the debug mpls traffic-eng ha sso command when you enabled debugging keywords to monitor the SSO process for tunnels and link management systems as the standby router becomes active: 

Router# debug mpls traffic-eng ha sso link-management events


MPLS traffic-eng SSO link management events debugging is on


Router# debug mpls traffic-eng ha sso link-management recovery


MPLS traffic-eng SSO link management recovery debugging is on


Router# debug mpls traffic-eng ha sso link-management standby


MPLS traffic-eng SSO link management standby behavior debugging is on


Router# debug mpls traffic-eng ha sso link-management checkpoint


MPLS traffic-eng SSO link management checkpointed info debugging is on


Router# debug mpls traffic-eng ha sso tunnel standby


MPLS traffic-eng SSO tunnel standby behavior debugging is on


Router# debug mpls traffic-eng ha sso tunnel recovery


MPLS traffic-eng SSO tunnel head recovery debugging is on


Router# debug mpls traffic-eng ha sso tunnel events 


MPLS traffic-eng SSO events for tunnel heads debugging is on


Router# debug mpls traffic-eng ha sso errors


MPLS traffic-eng SSO errors debugging is on


Router# show debug      <-----This command displays the debugging that is enabled.


MPLS TE:

  MPLS traffic-eng SSO link management events debugging is on

  MPLS traffic-eng SSO link management recovery debugging is on

  MPLS traffic-eng SSO link management standby behavior debugging is on

  MPLS traffic-eng SSO link management checkpointed info debugging is on

  MPLS traffic-eng SSO tunnel standby behavior debugging is on

  MPLS traffic-eng SSO tunnel head recovery debugging is on

  MPLS traffic-eng SSO events for tunnel heads debugging is on

  MPLS traffic-eng SSO errors debugging is on

Router#


Standby-Router#

Following is the sample debugging output displayed during a successful SSO recovery on the standby router as it becomes active: 

*May 12 20:03:15.303: RRR_HA_STATE: Told to wait for IGP convergence

*May 12 20:03:14.807: %FABRIC-SP-STDBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in 
slot 5 became active.

*May 12 20:03:15.763: RRR_HA_REC: Attempting to recover last flooded info; protocol: OSPF, 
area: 0

*May 12 20:03:15.763: RRR_HA_REC: recovered ospf area 0 instance 0x48FFF240

*May 12 20:03:15.763: RRR_HA_REC: recovered system info

*May 12 20:03:15.763: RRR_HA_REC: recovered link[0] info

*May 12 20:03:15.763: RRR_HA: Recovered last flooded info for igp: OSPF, area: 0

*May 12 20:03:15.763: Pre announce tunnel 10

*May 12 20:03:15.763: TSPVIF_HA_EVENT: added Router_t10 to dest list

*May 12 20:03:15.763: TSPVIF_HA_EVENT: Completed announcement of 1 tunnel heads to IGP

*May 12 20:03:15.763: TSPVIF_HA_REC: Attempting to recover Tunnel10 after SSO

*May 12 20:03:15.763: LSP-TUNNEL-REOPT: Tunnel10 [61] set to recover

*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered number hops = 5

*May 12 20:03:15.763: TSPVIF_HA_REC: recovered ospf area 0 instance 0x48FFF240

*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 0: 10.0.3.1, Id: 10.0.0.3 Router Node 
(ospf) flag:0x0

*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 1: 10.0.3.2, Id: 10.0.0.7 Router Node 
(ospf) flag:0x0

*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 2: 10.0.6.1, Id: 10.0.0.7 Router Node 
(ospf) flag:0x0

*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 3: 10.0.6.2, Id: 10.0.0.9 Router Node 
(ospf) flag:0x0

*May 12 20:03:15.763: TSPVIF_HA_REC: Recovered Hop 4: 10.0.0.9, Id: 10.0.0.9 Router Node 
(ospf) flag:0x0

*May 12 20:03:15.763: TSPVIF_HA_REC: signalling recovered setup for Tunnel10: popt 1

[61], weight 2

*May 12 20:03:15.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query

*May 12 20:03:15.891: TSPVIF_HA_REC:     output_idb: GigabitEthernet3/2, output_nhop: 
180.0.3.2

Standby-Router#

Router#

*May 12 20:03:25.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query

*May 12 20:03:25.891: TSPVIF_HA_REC:     output_idb: GigabitEthernet3/2, output_nhop: 
10.0.3.2

*May 12 20:03:35.891: TSPVIF_HA_REC: recovered Tu10 forwarding info needed by query

*May 12 20:03:35.891: TSPVIF_HA_REC:     output_idb: GigabitEthernet3/2, output_nhop: 
10.0.3.2

*May 12 20:03:35.895: RRR_HA_STATE: IGP flood prevented during IGP recovery

*May 12 20:03:38.079: LSP-TUNNEL-REOPT: Tunnel10 [61] received RESV for recovered setup

*May 12 20:03:38.079: LSP-TUNNEL-REOPT: Tunnel10 [61] removed as recovery

*May 12 20:03:38.079: TSPVIF_HA_EVENT: notifying RSVP HA to add lsp_info using key 
10.0.0.3->10.0.0.9 Tu10 [61] 10.0.0.3

*May 12 20:03:38.079: TSPVIF_HA_EVENT: updated 7600-1_t10 state; action = add; result = 
success

*May 12 20:03:38.079: