RSVP Infrastructure Commands on Cisco IOS XR Software
Available Languages
Table Of Contents
RSVP Infrastructure Commands on
Cisco IOS XR Softwareclear rsvp counters authentication
clear rsvp counters prefix filtering
show rsvp counters prefix filtering
show rsvp hello instance interface-based
signalling graceful-restart restart-time
signalling hello graceful-restart interface-based
signalling hello graceful-restart refresh interval
signalling hello graceful-restart refresh misses
signalling prefix-filtering access-list
signalling prefix-filtering default-deny-action
signalling refresh reduction bundle-max-size
signalling refresh reduction disable
signalling refresh reduction reliable
signalling refresh reduction summary
RSVP Infrastructure Commands on
Cisco IOS XR Software
This chapter describes the commands that you will use to configure and use Resource Reservation Protocol (RSVP). RSVP is a signaling protocol used to set up, maintain, and control end-to-end quality-of-service (QoS) reservations over IP. RSVP is specified in Internet Engineering Task Force (IETF) RFC 2205 (ftp://ftp.isi.edu/in-notes/rfc2205.txt).
The protocol has been extended to signal Multiprotocol Label Switching traffic engineering (MPLS-TE) tunnels, as specified in the IETF RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels and Optical UNI tunnels, as specified in the Optical Internetworking Forum (OIF) document OIF2000.125.7, User Network Interface (UNI) 1.0, Signalling Specification. The RSVP implementation also supports fault handling as specified in IETF RFC 3473, Generalized Multiprotocol Label Switching (GMPLS) Signaling RSVP-TE extensions.
RFC2747, RSVP Cryptographic Authentication is also supported.
For detailed information about MPLS concepts, configuration tasks, and examples, refer to the
Cisco IOS XR MPLS Configuration Guide.authentication (RSVP)
To enter RSVP authentication submode, use the authentication command in global configuration mode, RSVP interface configuration mode, or RSVP neighbor configuration mode. To remove authentication parameters in the applicable submode, use the no form of this command.
authentication
no authentication
Syntax Description
This command has no arguments or keywords.
Defaults
The default value is no authentication, which means that the feature is disabled.
Command Modes
Global configuration
RSVP interface configuration
RSVP neighbor configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the authentication command to enter RSVP authentication configuration mode.
Task ID
Examples
The following example shows how to enter RSVP authentication configuration mode from global configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp authenticationRP/0/RP0/CPU0:router(config-rsvp-auth)#The following example shows how to activate the RSVP on an interface and enter RSVP authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/2/1/0RP/0/RP0/CPU0:router(config-rsvp-if)# authenticationRP/0/RP0/CPU0:router(config-rsvp-if-auth)#The following example shows how to configure the RSVP neighbor with IP address 1.1.1.1 and enter neighbor authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp neighbor 1.1.1.1RP/0/RP0/CPU0:router(config-rsvp-nbor)# authenticationRP/0/RP0/CPU0:router(config-rsvp-nbor-auth)#Related Commands
bandwidth (RSVP)
To configure RSVP bandwidth on an interface using prestandard DS-TE mode, use the bandwidth command in RSVP interface configuration mode. To reset the RSVP bandwidth on that interface to its default value, use the no form of this command.
bandwidth [total reservable bandwidth] [bc0 bandwidth] [global-pool bandwidth] [sub-pool reservable-bw]
no bandwidth [total reservable bandwidth] [bc0 bandwidth] [global-pool bandwidth] [sub-pool reservable-bw]
Syntax Description
Defaults
sub-pool-bw: 0
Note
If the command is entered without the optional arguments, the total bandwidth is set to 75 percent of the intrinsic bandwidth of the interface. (If the interface has zero intrinsic bandwidth, none are reserved.)
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
RSVP is enabled either using the rsvp interface command or when MPLS is configured on the interface. In addition, there are other instances in which RSVP is enabled automatically; for example, when an RSVP message is received on an interface that is not configured under RSVP or MPLS (such as out-of-band signaling for an Optical User Network Interface application).
If RSVP reservation messages are received on an interface different from the one through which the corresponding Path message was sent out, the interfaces are adjusted such that all resource reservations, such as bandwidth, are done on the outgoing interface of the Path message.
Prestandard DS-TE uses the Cisco proprietary mechanisms for RSVP signaling and IGP advertisements. This DS-TE mode does not interoperate with third-party vendor equipment. Note that prestandard DS-TE is enabled only after configuring the sub-pool bandwidth values on MPLS-enabled interfaces.
Note
Task ID
Examples
The following example shows how to limit the total of all RSVP reservations on POS interface 0/3/0/0 to 5000 Kbps:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp)# bandwidth 5000Related Commands
bandwidth mam (RSVP)
To configure RSVP bandwidth on an interface using the Maximum Allocation Model (MAM) bandwidth constraints model, use the bandwidth mam command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
bandwidth mam {total reservable bandwidth | max-reservable-bw maximum-reservable-bw} bc0 reservable bandwidth
no bandwidth mam {total reservable bandwidth | max-reservable-bw maximum-reservable-bw} bc0 reservable bandwidth
Syntax Description
Defaults
If the command is entered without the optional arguments, the RSVP total bandwidth is set to 75 percent of the intrinsic bandwidth of the interface. If the interface has no (0) intrinsic bandwidth, then no bandwidth is reserved for RSVP.
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Both the MAM and RDM models can be configured on a single interface to allow switching between each model.
Note
Task ID
Examples
The following example shows how to limit the total of all RSVP reservations on POS interface 0/3/0/0 to 7500 kbps:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# bandwidth mam 7500Related Commands
Configures RSVP bandwidth on an interface using prestandard DS-TE mode.
Configures RSVP bandwidth on an interface using the Russian Doll Model (RDM) bandwidth constraints model.
bandwidth rdm (RSVP)
To configure RSVP bandwidth on an interface using the Russian Doll Model (RDM) bandwidth constraints model, use the bandwidth rdm command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
bandwidth rdm {total-reservable-bw | bc0 | global-pool} {sub-pool | bc1 reservable-bw}
no bandwidth rdm {total-reservable-bw | bc0 | global-pool} {sub-pool | bc1 reservable-bw}
Syntax Description
Defaults
sub-pool-bw: 0
global-pool and bc0: default value expressed in Kbps
Note
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Both the MAM and RDM bandwidth constraint models support up two bandwidth pools.
Cisco IOS XR software provides global configuration when switching between bandwidth constraint models. Both models are configured on a single interface to allow switching between models.
Note
The global pool and sub-pool keywords are included in this command for backward compatibility with prestandard DS-TE. The global pool keyword is equivalent to the bc0 keyword. The sub-pool keyword is equivalent to the bc1 keyword.
RDM is the default bandwidth constraint model used in both pre-standard and IETF mode.
Task ID
Examples
The following example shows how to limit the total of all RSVP reservations on POS interface 0/3/0/0 to 7500 kbps, and allows each single flow to reserve no more than 1000 kbps:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# bandwidth rdm 7500 1000Related Commands
clear rsvp authentication
To eliminate RSVP security association (SA) before the lifetime expires, use the clear rsvp authentication command in EXEC mode.
clear rsvp authentication [type interface-id] [destination IP address] [source IP address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear rsvp authentication command for the following reasons:
•
•
•
You can delete all RSVP security associations if you do not enter an optional filter (interface, source, or destination IP address).
If you delete a security association, it is recreated as needed.
Task ID
Examples
The following example shows how to clear each SA:
RP/0/RP0/CPU0:router# clear rsvp authenticationThe following example shows how to clear each SA with the destination address 1.1.1.1:
RP/0/RP0/CPU0:router# clear rsvp authentication destination 1.1.1.1The following example shows how to clear each SA with the source address 2.2.2.2:
RP/0/RP0/CPU0:router# clear rsvp authentication source 2.2.2.2The following example shows how to clear each SA with the POS interface 0/2/1/0:
RP/0/RP0/CPU0:router# clear rsvp authentication POS 0/2/1/0The following example shows how to clear each SA on the POS interface 0/2/1/0, destination address 1.1.1.1, and source address 2.2.2.2:
RP/0/RP0/CPU0:router# clear rsvp authentication POS 0/2/1/0 destination 1.1.1.1 source 2.2.2.2Related Commands
Controls how long RSVP maintains idle security associations with other trusted RSVP neighbors.
clear rsvp counters authentication
To eliminate RSVP counters for each security association (SA), use the clear rsvp counters authentication command in EXEC mode.
clear rsvp counters authentication [type interface-id] [destination IP address] [source IP address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear authentication counters for each SA:
RP/0/RP0/CPU0:router# clear rsvp counters authenticationThe following example shows how to clear authentication counters for each SA with the destination address 1.1.1.1:
RP/0/RP0/CPU0:router# clear rsvp counters authentication destination 1.1.1.1The following example shows how to clear authentication counters for each SA with the source address 2.2.2.2:
RP/0/RP0/CPU0:router# clear rsvp counters authentication source 2.2.2.2The following example shows how to clear authentication counters for each SA with the POS interface 0/2/1/0:
RP/0/RP0/CPU0:router# clear rsvp counters authentication POS 0/2/1/0The following example shows how to clear authentication counters for each SA on the POS interface 0/2/1/0, destination address 1.1.1.1, and source address 2.2.2.2:
RP/0/RP0/CPU0:router# clear rsvp counters authentication POS 0/2/1/0 destination 1.1.1.1 source 2.2.2.2clear rsvp counters all
To clear (set to zero) all RSVP message and event counters that are being maintained by the router, use the clear rsvp counters all command in EXEC mode.
clear rsvp counters all type interface-id
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear all message and event counters:
RP/0/RP0/CPU0:router# clear rsvp counters allRelated Commands
clear rsvp counters chkpt
To clear RSVP checkpoint counters, use the clear rsvp counters chkpt command in EXEC mode.
clear rsvp counters chkpt
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear all message and event counters:
RP/0/RP0/CPU0:router# clear rsvp counters chkptRelated Commands
clear rsvp counters events
To clear (set to zero) all RSVP event counters that are being maintained by the router, use the clear rsvp counters events command in EXEC mode.
clear rsvp counters events [type interface-id]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear rsvp counters events command to set all RSVP event counters to zero.
Task ID
Examples
The following example shows how to clear all event counters:
RP/0/RP0/CPU0:router# clear rsvp counters eventsRelated Commands
Clears all RSVP message counters that are being maintained by the router.
Shows RSVP event counters that are being maintained by the router when the events option is specified.
clear rsvp counters messages
To clear (set to zero) all RSVP message counters that are being maintained by the router, use the clear rsvp counters messages command in EXEC mode.
clear rsvp counters messages [type interface-id]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear rsvp counters messages command to set all RSVP message counters to zero.
Task ID
Examples
The following example shows how to set all RSVP message counters for POS interface 0/3/0/2 to zero:
RP/0/RP0/CPU0:router# clear rsvp counters messages pos0/3/0/2Related Commands
clear rsvp counters oor
To clear internal RSVP counters on out of resources (OOR) events, use the clear rsvp counters oor command in EXEC mode.
clear rsvp counters oor [type interface-id]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear rsvp counters oor command to set RSVP OOR counters to zero.
Task ID
Examples
The following example show how to clear all RSVP message counters for POS interface 0/3/0/2 to zero:
RP/0/RP0/CPU0:router# clear rsvp counters oor pos0/3/0/2Related Commands
clear rsvp counters prefix filtering
To clear internal prefix-filtering related RSVP counters, use the clear rsvp counters prefix-filtering command in EXEC mode.
clear rsvp counters prefix-filtering {interface [type interface-id] | access-list [aclname]}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear rsvp counters prefix-filtering command to set RSVP prefix-filtering related RSVP counters to zero.
Task ID
Examples
The following example shows how to set all RSVP message counters for POS interface 0/3/0/2 to zero:
RP/0/RP0/CPU0:router# clear rsvp counters prefix-filtering interface pos0/3/0/2The following example shows how to set all RSVP prefix-filtering counters for access-list banks to zero:
RP/0/RP0/CPU0:router# clear rsvp counters prefix-filtering access-list banksRelated Commands
key-source key-chain (RSVP)
To specify the source of the key information to authenticate RSVP messages, use the key-source key-chain command in the appropriate RSVP authentication configuration mode. To remove the key source from the appropriate RSVP authentication configuration mode, use the no form of this command.
key-source key-chain key-chain-name
no key-source key-chain key-chain-name
Syntax Description
Defaults
The default value is none, which means that the key source is not specified.
Command Modes
RSVP authentication configuration
RSVP interface authentication configuration
RSVP neighbor authentication configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
•
•
•
Note
Task ID
Examples
The following example shows that the source of the key information is specified for the keychain mpls-keys in RSVP authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp authenticationRP/0/RP0/CPU0:router(config-rsvp-auth)# key-source key-chain mpls-keysThe following example shows that the source of the key information is specified for the keychain mpls-keys for a POS interface in RSVP authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface POS 0/2/1/0RP/0/RP0/CPU0:router(config-rsvp-if)# authenticationRP/0/RP0/CPU0:router(config-rsvp-if-auth)# key-source key-chain mpls-keysThe following example shows that the source of the key information is specified for the keychain mpls-keys in RSVP neighbor authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp neighbor 1.1.1.1 authenticationRP/0/RP0/CPU0:router(config-rsvp-nbor-auth)# key-source key-chain mpls-keysRelated Commands
Controls how long RSVP maintains idle security associations with other trusted RSVP neighbors.
Specifies the tolerance to accept out-of-sequence messages.
life-time (RSVP)
To control how long RSVP maintains idle security associations with other trusted RSVP neighbors, use the life-time command in the appropriate RSVP authentication configuration mode. To disable the lifetime setting, use the no form of this command.
life-time seconds
no life-time seconds
Syntax Description
seconds
Length of time (in seconds) that RSVP maintains security associations with other trusted RSVP neighbors. Range is 30 to 86400.
Defaults
seconds: 1800 seconds (30 minutes)
Command Modes
RSVP authentication configuration
RSVP interface authentication configuration
RSVP neighbor authentication configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For inheritance procedures, see the Cisco IOS XR MPLS Configuration Guide.
Use the life-time (RSVP) command to indicate when to end idle security associations with RSVP trusted neighbors.
By setting a larger lifetime, the router remembers the state for a long period time, which provides better protection against a replay attack.
Use the clear rsvp authentication command to free security associations before their lifetimes expire.
Task ID
Examples
The following example shows how to configure a lifetime of 2000 seconds for each SA in RSVP authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp authenticationRP/0/RP0/CPU0:router(config-rsvp-auth)# life-time 2000The following example shows how to configure a lifetime of 2000 seconds for each SA in RSVP neighbor authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp neighbor 1.1.1.1 authenticationRP/0/RP0/CPU0:router(config-rsvp-nbor-auth)# life-time 2000The following example shows how to configure a lifetime of 2000 seconds for each SA in RSVP interface authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface POS 0/2/1/0RP/0/RP0/CPU0:router(config-rsvp-if)# authenticationRP/0/RP0/CPU0:router(config-rsvp-if-auth)# life-time 2000Related Commands
rsvp interface
To configure RSVP on an interface, use the rsvp interface command in global configuration mode. To disable RSVP on that interface, use the no form of this command.
rsvp interface type interface-id}
no rsvp interface type interface-id
Syntax Description
Defaults
RSVP is enabled by default on an interface under the following conditions. (Enabling RSVP on an interface means that interface can be used by RSVP to send and receive RSVP messages).
•
•
•
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When RSVP is enabled on an interface by any of the three methods mentioned in the above section, the default bandwidth is 0. Use the bandwidth command in RSVP interface configuration mode to configure the bandwidth on an interface.
If the interface bandwidth is 0, RSVP can be used only to signal flows that do not require bandwidth on this interface. In the case of O-UNI, 0 bandwidth is not an issue, because O-UNI does not use bandwidth as a resource.
The rsvp interface command enables the RSVP interface configuration submode.
Task ID
Examples
The following example shows how to enable the RSVP interface configuration submode and to enable RSVP on this interface with 0 bandwidth:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0Related Commands
rsvp neighbor
To specify an RSVP neighbor, use the rsvp neighbor command in global configuration mode. To deactivate authentication for a neighbor, use the no form of this command.
rsvp neighbor IP address authentication
no rsvp neighbor IP address authentication
Syntax Description
Defaults
No default values or behaviors
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Use the rsvp neighbor command to enter RSVP neighbor authentication configuration mode.
Task ID
Examples
The following example shows how to enter RSVP neighbor authentication configuration mode for IP address 1.1.1.1:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp neighbor 1.1.1.1 authenticationP/0/RP0/CPU0:router(config-rsvp-nbor-auth)#Related Commands
show rsvp authentication
To display the database for the security association that RSVP has established with other RSVP neighbors, use the show rsvp authentication command in EXEC mode.
show rsvp authentication [type interface-id] [destination IP address] [detail] [mode {receive | send}] [neighbor IP address] [source IP address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following sample output displays information for RSVP authentication:
RP/0/RP0/CPU0:router# show rsvp authenticationCodes: S - static, G - global, N - neighbor, I -interface, C - chainSource Address Dest Address Interface Mode Key-Source Key-ID Code3.0.0.1 3.0.0.2 PO0/7/0/2 Send mpls-keys 1 SGC3.0.0.2 3.0.0.1 PO0/7/0/2 Recv mpls-keys 1 SGCTable 49 describes the significant fields shown in the display.
The following sample output shows detailed information about a Send mode SA that is followed by a Receive mode SA:
RP/0/RP0/CPU0:router# show rsvp authentication detailRSVP Authentication Information:Source Address: 3.0.0.1Destination Address: 3.0.0.2Neighbour Address: 3.0.0.2Interface: POS0/7/0/2Direction: SendLifeTime: 1800 (sec)LifeTime left: 1305 (sec)KeyType: Static Global KeyChainKey Source: foobarKey Status: No errorKeyID: 1Digest: HMAC MD5 (16)Challenge: Not supportedTX Sequence: 5023969459702858020 (0x45b8b99b00000124)Messages successfully authenticated: 245Messages failed authentication: 0Receive Errors:Incomplete security association: 0Missing INTEGRITY object: 0Incorrect digest: 0Digest type mismatch: 0Duplicate sequence number: 0Out-of-range sequence number: 0Invalid message format: 0Table 50 describes the significant fields shown in the display.
show rsvp counters
To display internal RSVP counters, use the show rsvp counters command in EXEC mode.
show rsvp counters [messages type interface-id] [events | database]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
In message counters, bundle messages are counted as single bundle messages. The component messages are not counted separately.
Task ID
Examples
The following is sample output from the show rsvp counters messages command for POS0/3/0/0:
RP/0/RP0/CPU0:router# show rsvp counters messages POS 0/3/0/0POS0/3/0/0 Recv Xmit Recv XmitPath 24 1 Resv 0 0PathError 0 0 ResvError 0 0PathTear 5 1 ResvTear 0 0ResvConfirm 0 0 Ack 34 0Bundle 0 Hello 0 0SRefresh 10118 0 OutOfOrder 0Retransmit 0 Rate Limited 0Table 51 describes the significant fields shown in the display.
The following is sample output from the show rsvp counters events command:
RP/0/RP0/CPU0:router# show rsvp counters eventsEthernet0/0/0/0 tunnel1Expired Path states 0 Expired Path states 0Expired Resv states 0 Expired Resv states 0NACKs received 0 NACKs received 0POS0/3/0/1 POS0/3/0/2Expired Path states 0 Expired Path states 0Expired Resv states 0 Expired Resv states 0NACKs received 0 NACKs received 0POS0/3/0/3 All RSVP InterfacesExpired Path states 0 Expired Path states 0Expired Resv states 0 Expired Resv states 0NACKs received 0 NACKs received 0Table 52 describes the significant fields shown in the display.
The following is sample output from the show rsvp counters database command:
RP/0/RP0/CPU0:router# show rsvp counters databaseSessions: 0Locally created and incoming paths: 0Outgoing paths: 0Locally created and incoming Reservations: 0Outgoing Reservations: 0Interfaces: 4Table 53 describes the significant fields shown in the display.
show rsvp counters oor
To display internal RSVP counters on out of resources (OOR) events, use the show rsvp counters oor command in EXEC mode.
show rsvp counters oor [type interface-id | summary]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show rsvp counters oor command:
RP/0/RP0/CPU0:router# show rsvp counters oorPOS 0/3/0/0 RejectedPath 24POS 0/3/0/2 RejectedPath 31All RSVP Interfaces RejectedPath 55Table 54 describes the significant fields shown in the display.
Table 54 show rsvp counters oor Field Descriptions
Path
Number of Path messages received on the interface that were rejected due to oor conditions.
show rsvp counters prefix filtering
To display internal prefix-filtering related RSVP counters, use the show rsvp counters prefix-filtering command in EXEC mode.
show rsvp counters prefix-filtering {interface [type interface-id | summary]} {access-list [aclname]}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following is sample output from the show rsvp counters prefix filtering command:
RP/0/RP0/CPU0:router# show rsvp counters prefix-filtering interfaceRouted Fwd Local Drop Def-Drop Def-Proc TotalPath 4 4PathTear 0 0ResvConfirm 0 0Total 4 4POS0/5/0/1 Fwd Local Drop Def-Drop Def-Proc TotalPath 1 0 219 2 222PathTear 0 0 31 0 31ResvConfirm 0 0 0 0 0Total 1 0 219 2 253POS0/5/0/2 Fwd Local Drop Def-Drop Def-Proc TotalPath 0 0 0 1 1PathTear 0 0 0 0 0ResvConfirm 0 0 0 0 0Total 0 0 0 1 1ALL RSVPInterfaces Fwd Local Drop Def-Drop Def-Proc TotalPath 4 1 0 219 3 227PathTear 0 0 0 31 0 31ResvConfirm 0 0 0 0 0 0Total 4 1 0 250 3 258The following is sample output from the show rsvp counters prefix filtering interface type interface-id command:
RP/0/RP0/CPU0:router# show rsvp counters prefix-filtering interface POS 0/5/0/1POS0/5/0/1 Fwd Local Drop Def-Drop Def-Proc TotalPath 1 0 219 2 222PathTear 0 0 31 0 31ResvConfirm 0 0 0 0 0Total 1 0 250 2 253The following is sample output from the show rsvp counters prefix filtering summary command:
RP/0/RP0/CPU0:router# show rsvp counters prefix-filtering interface summaryALL RSVPInterfaces Fwd Local Drop Def-Drop Def-Proc TotalPath 4 1 0 219 3 227PathTear 0 0 0 31 0 31ResvConfirm 0 0 0 0 0 0Total 4 1 0 250 3 258RP/0/RP0/CPU0:router# show rsvp counters prefix-filtering access-listACL: banks Forward Local Drop TotalPath 0 0 0 0PathTear 0 0 0 0ResvConfirm 0 0 0 0Total 0 0 0 0RP/0/RP0/CPU0:router# show rsvp counters prefix-filtering access-list banksACL: banks Forward Local Drop TotalPath 0 0 0 0PathTear 0 0 0 0ResvConfirm 0 0 0 0Total 0 0 0 0Table 55 describes the significant fields shown in the display.
show rsvp fast-reroute
To display RSVP Fast-Reroute (FRR) information, use the show rsvp counters fast-reroute command in EXEC mode.
show rsvp fast-reroute [destination A.B.C.D. | dst-port destination port | source A.B.C.D. | src-port source port | summary]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show rsvp fast-reroute command:
RP/0/RP0/CPU0:router# show rsvp fast-rerouteType Destination TunID Source PSBs RSBs-------- --------------- ----------- ------------ --------- -------LSP4 70.70.70.70 1 50.50.50.50 Ready ReadyTable 56 describes the significant fields shown in the display.
Table 56 show rsvp fast-reroute Field Descriptions
Type
Type of session.
Destination
Destination address of session.
TunID
Tunnel ID number.
Source
Source address of session.
PSBs
PSB FRR1 state.
RSBs
RSB FRR state.
1 Fast reroute
The following is sample output from the show rsvp fast-reroute summary command:
RP/0/RP0/CPU0:router# show rsvp fast-reroute summaryStates Total Ready Act-Wait ActivePSBs 1 1 0 0RSBs 1 1 0 0Table 57 describes the significant fields shown in the display.
Table 57 show rsvp fast-reroute summary Field Descriptions
States
FRR1 state.
Total
Total number of path and reservation states.
Ready
Number of states in FRR ready state. No FRR processing has been done on these states.
Act-Wait
Number of states in "Active Wait" FRR state.
•
•
Active
Number of states in "Active" FRR state.
•
•
1 Fast reroute
show rsvp graceful-restart
To display the local graceful-restart information for RSVP, use the show rsvp graceful-restart command in EXEC mode.
show rsvp graceful-restart [neighbors A.B.C.D. | detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Graceful-restart neighbors are displayed in ascending order of neighbor IP address.
Task ID
Examples
The following is sample output from the show rsvp graceful-restart command:
RP/0/RP0/CPU0:router# show rsvp graceful-restartGraceful restart: enabled Number of global neighbors: 1Local MPLS router id: 192.168.55.55Restart time: 60 seconds Recovery time: 120 secondsRecovery timer: Not runningHello interval: 5000 milliseconds Maximum Hello miss-count: 4Table 58 describes the significant fields shown in the display.
The following is sample output from the show rsvp graceful-restart neighbors command, which displays information about graceful restart neighbors in the router:
RP/0/RP0/CPU0:router# show rsvp graceful-restart neighborsNeighbor App State Recovery Reason Since LostCnt--------------- ----- ------ -------- ------------ -------------------- --------192.168.77.77 MPLS UP DONE N/A 19/12/2002 17:02:25 0Table 59 describes the significant fields shown in the display.
The following is sample output from the show rsvp graceful-restart neighbors detail command, which displays detailed information about all graceful restart neighbors:
RP/0/RP0/CPU0:router# show rsvp graceful-restart neighbors detailNeighbor: 192.168.77.77 Source: 192.168.55.55 (MPLS)Hello instance for application MPLSHello State: UP (for 00:20:52)Number of times communications with neighbor lost: 0Reason: N/ARecovery State: DONENumber of Interface neighbors: 1address: 192.168.55.0Restart time: 120 seconds Recovery time: 120 secondsRestart timer: Not runningRecovery timer: Not runningHello interval: 5000 milliseconds Maximum allowed missed Hello messages: 4Table 60 describes the significant fields shown in the display.
show rsvp hello instance
To display the RSVP hello instances, use the show rsvp hello instance command in EXEC mode.
show rsvp hello instance [Hostname or A.B.C.D. | detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Hello instances are displayed in ascending order of neighbor IP address.
Task ID
Examples
The following is sample output from the show rsvp hello instance command, which displays brief information about all hello instances in the router:
RP/0/RP0/CPU0:router# show rsvp hello instanceNeighbor Type State Interface LostCnt---------------- ------ -------- ------------ --------192.168.77.77 ACTIVE UP None 0Table 61 describes the significant fields shown in the display.
Table 61 show rsvp hello instance Field Descriptions
Neighbor
Router ID of a global neighbor hosting the hello instance.
Type
Hello instance type (active or passive). active type indicates that a node is sending hello requests and passive indicates that a node is sending hello acknowledgements.
State
State of the hello session to a global neighbor (up, down, or init).
Interface
Interface for interface bound hello's used for FRR1 . Hello instances bound to a global neighbor show Interface as None. Hello's used for FRR are currently not supported.
LostCnt
Number of times hello communication has been lost with a global neighbor.
1 Fast reroute
The following is sample output from the show rsvp hello instance command, which displays detailed information about all hello instances in the router:
RP/0/RP0/CPU0:router# show rsvp hello instance detailNeighbor: 192.168.77.77 Source: 192.168.55.55 (MPLS)State: UP (for 00:07:14)Type: ACTIVE (sending requests)I/F: NoneHello interval (msec) (used when ACTIVE)Configured: 5000Src_instance 0x484b01, Dst_instance 0x4d4247Counters:Communication with neighbor lost:Num of times: 0 Reasons:Missed acks: 0New Src_Inst received: 0New Dst_Inst received: 0I/f went down: 0Neighbor disabled Hello: 0Msgs Received: 93Sent: 92Suppressed: 87Table 62 describes the significant fields shown in the display.
show rsvp hello instance interface-based
To display the RSVP hello instances on a specific interface, use the show rsvp hello instance interface-based command in EXEC mode.
show rsvp hello instance interface-based [A.B.C.D. | detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Hello instances are displayed in ascending order of neighbor IP address.
Task ID
Examples
The following is sample output from the show rsvp hello instance interface-based command, which displays detailed information about hello instances on a specific interface:
RP/0/RP0/CPU0:router# show rsvp hello instance interface-based 10.10.10.10Neighbor Type State Interface LostCnt---------------- ------ -------- ------------ --------10.10.10.10 ACTIVE UP None 0Table 63 describes the significant fields shown in the display.
Table 63 show rsvp hello instance Field Descriptions
Neighbor
Router ID of a global neighbor hosting the hello instance.
Type
Hello instance type (active or passive). active type indicates that a node is sending hello requests and passive indicates that a node is sending hello acknowledgements.
State
State of the hello session to a global neighbor (up, down, or init).
Interface
Interface for interface bound hello's used for FRR1 . Hello instances bound to a global neighbor show Interface as None. Hello's used for FRR are currently not supported.
LostCnt
Number of times hello communication has been lost with a global neighbor.
1 Fast reroute
show rsvp interface
To display information about all interfaces with RSVP enabled, use the show rsvp interface command in EXEC mode.
show rsvp interface type interface-id [detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show rsvp interface command to display various configuration settings such as the list of neighbors and their refresh reduction capabilities.
Task ID
Examples
The following is sample output from the show rsvp interface command, which displays brief information about RSVP-configured interfaces running in prestandard DS-TE mode:
RP/0/RP0/CPU0:router# show rsvp interfaceInterface MaxBW MaxFlow Allocated MaxSub---------- -------- -------- --------------- -------tu2000 0 0 0 ( 0%) 0PO0/3/0/0 1000M 1000M 200K( 0%) 0This following is sample output from the show rsvp interfaces detail command running in standard DS-TE mode:
RP/0/RP0/CPU0:router# show rsvp interface detailINTERFACE: tunnel-te10 (ifh=0x1000480).BW (bits/sec): Max=0. MaxFlow=0.Allocated=0 (0%).BC0=0. BC1=0.INTERFACE: POS0/3/0/0 (ifh=0x4000300).BW (bits/sec): Max=0. MaxFlow=0.Allocated=0 (0%).BC0=0. BC1=0.INTERFACE: POS0/3/0/3 (ifh=0x4000C00).BW (bits/sec): Max=0. MaxFlow=0.Allocated=0 (0%).BC0=0. BC1=0.Table 64 describes the significant fields shown in the display.
Related Commands
show rsvp neighbor
To display information about RSVP neighbors, use the show rsvp neighbor command in EXEC mode.
show rsvp neighbor [detail]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show rsvp interface command to display various configuration settings such as the list of neighbors and their refresh reduction capabilities.
Task ID
Examples
The following is sample output from the show rsvp neighbor command using the detail keyword:
RP/0/RP0/CPU0:router# show rsvp neighbor detailGlobal Neighbor: 40.40.40.40Interface Neighbor: 1.1.1.1Interface: POS0/0/0/0Refresh Reduction: "Enabled" or "Disabled".Remote epoch: 0xXXXXXXXXOut of order messages: 0Retransmitted messages: 0Interface Neighbor: 2.2.2.2Interface: POS0/1/0/0Refresh Reduction: "Enabled" or "Disabled".Remote epoch: 0xXXXXXXXXOut of order messages: 0Retransmitted messages: 0show rsvp request
To list all the requests that RSVP knows about on a router, use the show rsvp request command in EXEC mode.
show rsvp request [detail] [destination A.B.C.D. | dst-port port-num | source A.B.C.D. | src-port port-num]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This command displays information about upstream reservations only; that is, reservations being sent to upstream hops. Information about downstream reservations (that is, incoming or locally created reservations) is available using the show rsvp reservation command.
Reservations are displayed in ascending order of destination IP address, destination port, source IP address, and source port.
Task ID
Examples
The following is sample output from the show rsvp request command:
RP/0/RP0/CPU0:router# show rsvp requestDest Addr DPort Source Addr SPort Pro OutputIF Sty Serv Rate Burst---------------- ----- ---------------- ----- --- ---------- --- ---- ---- -----192.168.40.40 2001 192.168.67.68 2 0 PO0/7/0/1 SE LOAD 0 1KThe following is sample output from the show rsvp request detail command, which displays detailed information about all requests in the router. Requests are reservation states for the reservation messages sent upstream:
RP/0/RP0/CPU0:router# show rsvp request detailREQ: IPv4-LSP Session addr: 192.168.40.40. TunID: 2001. LSPId: 2.Source addr: 192.168.67.68. ExtID: 192.168.67.68.Output interface: POS0/7/0/1. Next hop: 192.168.67.68 (lih: 0x19700001).Flags: Local Receiver.Style: Shared-Explicit. Service: Controlled-Load.Rate: 0 bits/sec. Burst: 1K bytes. Peak: 0 bits/sec.MTU min: 0, max: 500 bytes.Policy: Forwarding. Policy source(s): MPLS/TE.Number of supporting PSBs: 1Destination Add DPort Source Add SPort Pro Input IF Rate Burst Prot192.168.40.40 2001 192.168.67.68 2 0 PO0/7/0/1 0 1K OffNumber of supporting RSBs: 1Destination Add DPort Source Add SPort Pro Input IF Sty Serv Rate Burst192.168.40.40 2001 65.66.67.68 2 0 None SE LOAD 0 1KTable 65 describes the significant fields shown in the display.
Related Commands
show rsvp reservation
To list all reservations that RSVP knows about on a router, use the show rsvp reservation command in EXEC mode.
show rsvp reservation [detail] [destination A.B.C.D. | dst-port port-num | source A.B.C.D. | src-port port-num]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show rsvp reservation command displays information about downstream reservations only (that is, reservations received on this device or created by application program interface (API) calls). Upstream reservations or requests are displayed using the show rsvp request command.
Task ID
Examples
The following is sample output from the show rsvp reservation command:
cRP/0/RP0/CPU0:router# show rsvp reservationDest Addr DPort Source Addr SPort Pro Input IF Sty Serv Rate Burst---------------- ----- ---------------- ----- --- ---------- --- ---- ---- -----192.168.40.40 2001 192.168.67.68 2 0 None SE LOAD 0 1K192.168.67.68 2000 10.40.40.40 15 0 PO0/7/0/1 SE LOAD 0 1KThe following example displays detailed information about all reservations in the router:
RP/0/RP0/CPU0:router# show rsvp reservation detailRESV: IPv4-LSP Session addr: 192.168.40.40. TunID: 2001. LSPId: 2.Source addr: 192.168.67.68. ExtID: 192.168.67.68.Input adjusted interface: None. Input physical interface: None.Next hop: 0.0.0.0 (lih: 0x0).Style: Shared-Explicit. Service: Controlled-Load.Rate: 0 bits/sec. Burst: 1K bytes. Peak: 0 bits/sec.MTU min: 40, max: 500 bytes.Flags: Local Receiver.State expires in 0.000 sec.Policy: Accepted. Policy source(s): MPLS/TE.Header info: RSVP TTL=255. IP TTL=255. Flags: 0x0. TOS=0xff.Resource:Labels: Local downstream: 3.RESV: IPv4-LSP Session addr: 192.168.67.68. TunID: 2000. LSPId: 15.Source addr: 192.168.40.40. ExtID: 10.10.40.40.Input adjusted interface: PO0/7/0/1. Input physical interface: PO0/7/0/1.Next hop: 10.66.67.68 (lih: 0x8DE00002).Style: Shared-Explicit. Service: Controlled-Load.Rate: 0 bits/sec. Burst: 1K bytes. Peak: 0 bits/sec.MTU min: 0, max: 500 bytes.Flags: None.State expires in 361.184 sec.Policy: Accepted. Policy source(s): MPLS/TE.Header info: RSVP TTL=254. IP TTL=254. Flags: 0x1. TOS=0xff.Resource:Labels: Outgoing downstream: 3.Table 66 describes the significant fields shown in the display.
Table 66 show rsvp reservation detail Field Descriptions
Input adjusted interface
Interface to reflect the path's outgoing interface.
Input physical interface
Interface where the reservation was received.
Next hop
Address of the downstream node that sent the reservation to this node.
Lih
Logical interface handle sent in the hop object of path returned to us in the reservation to figure out what interface the path was sent on.
Flags
Indicates path state, including as Local Repair, Local Sender (LSP1 ingress node), and others.
Policy
Admission control status.
Policy source
Entity performing the admission control on the LSP.
Header info
RSVP header information as described in RFC 2205.
1 Link-state packet
Related Commands
show rsvp sender
To list all path states that RSVP knows about on this router, use the show rsvp sender command in EXEC mode.
show rsvp sender [detail] [destination A.B.C.D. | dst-port port-num | source A.B.C.D. | src-port port-num]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show rsvp sender command displays information about path states.
Task ID
Examples
The following is sample output from the show rsvp sender command:
RP/0/RP0/CPU0:router# show rsvp senderDest Addr DPort Source Addr SPort Pro Input IF Rate Burst Prot---------------- ----- ---------------- ----- --- ------------ ---- ----- ----10.40.40.40 2001 10.66.67.68 2 0 PO0/7/0/1 0 1K Off10.66.67.68 2000 10.40.40.40 15 0 None 0 1K OffTable 67 describes the significant fields shown in the display.
Table 67 show rsvp sender Field Descriptions
DProt
Destination port number and tunnel-id.
Dest Address
Destination and session address of LSP1 .
SPort
Source port and LSP ID.
Source Addr
Address of the ingress node of the LSP.
Input IF
Interface on which the Path message was received.
1 Link-state packet
The following example displays detailed information about all paths in the system:
RP/0/RP0/CPU0:router# show rsvp sender detailPATH: IPv4-LSP Session addr: 65.66.67.68. TunID: 1. LSPId: 25.Source addr: 40.40.40.40. ExtID: 40.40.40.40.Prot: Off. Backup tunnel: None.Setup Priority: 7, Reservation Priority: 0Rate: 0 bits/sec. Burst: 1K bytes. Peak: 0 bits/sec.Min unit: 40 bytes, Max unit: 500 bytesFlags: Bidirectional.State expires in 370.154 sec.Policy: Accepted. Policy source(s): Default.Header info: RSVP TTL=254. IP TTL=254. Flags: 0x1. TOS=0xc0.Input interface: PO0/3/0/0. Previous hop: 40.40.40.40 (lih: 0x40600001).Resource:Labels: Outgoing upstream: 3.Class-Type: None.Explicit Route (Incoming):Strict, 65.66.67.68(interface-id 5)Strict, 65.66.67.68/32Table 68 describes the significant fields shown in the display.
Table 68 show rsvp sender detail Field Descriptions
Prot
Specifies if the LSP is configured as a protected tunnel.
Backup tunnel
Name of the backup tunnel assigned to protect this LSP1 .
Flags
Path state, including as local repair, local sender (LSP ingress node), and others.
Policy
Admission control status for Path message in the incoming direction.
Policy source
Entity doing the admission control, such as COPS or MPLS-TE2 .
Header info
RSVP header information as described in RFC 2205.
Input interface
Interface on which the path was received. At ingress mode, it is None.
Previous hop
Address of the upstream peer who sent us the Path message. May be the interface address or node-id depending on LSP (packet or optical).
Lih
Logical interface handle received in the hop object of the path.
Output interface
Interface on which the path was forwarded to the downstream neighbor
Policy
Admission control status for the path in the outgoing direction.
Explicit route
Explicit route specified in the explicit-route object of the Path message.
1 Link-state packet
2 MPLS-Traffic Engineering
show rsvp session
To list all sessions that RSVP knows about on this router, use the show rsvp session command in EXEC mode.
show rsvp session [detail] [destination A.B.C.D. | dst-port port-num | tunnel-name tunnel-name]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Sessions are displayed in ascending order of destination IP address, destination port, and source IP address.
Task ID
Examples
The following is sample output from the show rsvp session command:
RP/0/RP0/CPU0:router# show rsvp sessionType Session Addr Port Proto/ExtTunID PSBs RSBs Reqs---- --------------- ----- --------------- ----- ----- -----LSP4 10.40.40.40 2001 10.66.67.68 1 1 1LSP4 10.66.67.68 2000 10.40.40.40 1 1 0Table 69 describes the significant fields shown in the display.
The following is sample output for the show rsvp session detail command:
RP/0/RP0/CPU0:router# show rsvp session detailSESSION: IPv4-LSP Addr: 65.66.67.68, TunID: 1, ExtID: 40.40.40.40PSBs: 1, RSBs: 1, Requests: 0LSPId: 1Tunnel Name: newhead_t1RSVP Path Info:InLabel: No intf, No labelIncoming Address: UnknownExplicit Route:Strict, 65.66.67.68(interface-id 5)Strict, 65.66.67.68/32Record Route: NoneTspec: avg rate=0, burst=1K, peak rate=0RSVP Resv Info:OutLabel: POS0/7/0/1, 5FRR OutLabel: No intf, No labelRecord Route:Node-id 65.66.67.68, interface index 5Fspec: avg rate=0, burst=1K, peak rate=0Table 70 describes the significant fields shown in the display.
Table 70 show rsvp session detail Field Descriptions
TunID
Tunnel identifier and the destination port of the LSP1 .
ExtID
Ingress node address of LSP.
Tunnel Instance
Source port of the LSP (with the ExtId forming the source parameters).
Tunnel Name
Name of the tunnel and LSP.
InLabel
Incoming interface and label info for the LSP in the upstream direction. At the egress node, using penultimate hop popping at the egress node, (implicit-null) appears as No Label.
Incoming Address
Address of the ingress interface.
Explicit Route
Explicit route specified in the explicit-route object of the Path message.
Record Route
Record route object in either the path or reservation message.
Tspec
Traffic parameters.
OutLabel
Outgoing interface and label sent downstream.
FRR OutLabel
For FRR2 , displays the backup tunnel and Merge-point label.
Fspec
Flow spec parameters for specified QoS.
1 Link-state packet
2 Fast reroute
signalling dscp (RSVP)
To give all RSVP signaling packets sent out on a specific interface higher priority in the network by marking them with a particular Differentiated Service Code Point (DSCP), use the signalling dscp command in RSVP interface configuration submode. To return to the default behavior, use the no form of this command.
signalling dscp dscp
no signalling dscp
Syntax Description
Defaults
No default behavior or values
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
DSCP marking improves signaling setup and teardown times.
Ordinarily, when a router receives Path messages for a particular state marked with a DSCP value, it sends out Path messages for that state marked with the same DSCP value. This command overrides that DSCP persistence and ensures that all messages sent out a particular interface are marked with a specified DSCP.
Though this command controls RSVP signaling packets, it has no effect on ordinary IP or MPLS data packets traveling along the path created or reserved by this RSVP session.
DSCP persistence operates on a per-state basis, but this command operates on a per-interface basis. So, if some incoming message (for example, multicast Path) with DSCP 10 causes two outgoing messages on interfaces A and B, ordinarily both are sent with DSCP 10. If signalling dscp 5 is configured for RSVP on interface A, the Path messages being sent out interface A is marked with DSCP 5, but the Path messages being sent out interface B are marked with DSCP 10.
There is a difference between the signalling dscp 0 and no signalling dscp commands. The first command instructs RSVP to explicitly set to 0 the DSCP on all packets sent out this interface. The second command removes any override on the packets being sent out this interface, and allows the DSCP of received packets that created this state to persist on packets forwarded out this interface.
The RFC specifies a standard mapping from the eight IP precedence values to eight values in the 64-value DSCP space. You can use those special DSCP values to specify IP precedence bits only.
Task ID
Examples
The following example shows how to mark all RSVP packets going out on POS interface 0/1/0/1 as DSCP 20:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/1/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# signalling dscp 20The following example shows how to disable DSCP marking of signaling packets going out POS interface 0/1/0/1:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/1/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# interface pos 0/1/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling dscpsignalling graceful-restart
To enable or disable RSVP signaling graceful restart, use the signalling graceful-restart command in RSVP configuration mode. To return to the default behavior, use the no form of this command.
signalling graceful-restart
no signalling graceful-restart
Syntax Description
This command has no arguments or keywords.
Defaults
RSVP signaling graceful restart is disabled.
Command Modes
RSVP configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The signalling graceful-restart command provides a mechanism that helps minimize the negative effects on MPLS and Optical User Network Interface (O-UNI) traffic for the following types of faults. This is an implementation of the fault handling section of the IETF standard RFC 3473:
•
•
The signalling graceful-restart command instigates the exchange of RSVP hello messages between the router and its neighbor nodes. After the hello messages are established with a given neighbor, RSVP can detect these types of faults when they occur.
Task ID
Examples
The following example shows how to enable RSVP signalling graceful restart:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# signalling graceful-restartRelated Commands
Configures the restart time that is advertised in the Restart Cap object in hello messages.
signalling graceful-restart restart-time
To configure the restart time that is advertised in the Restart Cap object in hello messages, use the signalling graceful-restart restart-time command in RSVP configuration mode. To return to the default behavior, use the no form of this command.
signalling graceful-restart restart-time time
no signalling graceful-restart restart-time
Syntax Description
time
Time after a control-plane restart that RSVP can start exchanging hello messages. Range is 60 to 3600 seconds. Default is 120 seconds.
Defaults
restart-time: 120 seconds
Command Modes
RSVP configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If no hello messages are received from a neighbor within a certain number of hello intervals, a node assumes that communication with the neighbor has been lost. The node waits the amount of time advertised by the last restart time communicated by the neighbor, before invoking procedures for recovery from communication loss.
The configured restart time is important in case of recovery from failure. The configured value should accurately reflect the amount of time within which, after a control-plane restart, RSVP can start exchanging hello messages.
Task ID
Examples
The following example shows how to set the restart time:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# signalling graceful-restart restart-time 200The following example shows how to reset the restart time to the default of 120 seconds:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# no signalling graceful-restart restart-timeRelated Commands
signalling hello graceful-restart interface-based
To enable RSVP to accept interface-based hello requests from the neighbor on an interface and send a Hello Ack to it, use the rsvp hello graceful-restart interface-based command in RSVP configuration mode. To return to the default behavior, use the no form of this command.
signalling hello graceful-restart interface-based
no signalling hello graceful-restart interface-based
Syntax Description
This command has no arguments or keywords.
Defaults
.No default behavior or values
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to enable interface-based graceful restart:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 66RP/0/RP0/CPU0:router(config-rsvp-if)# signalling hello graceful-restart interface basedsignalling hello graceful-restart refresh interval
To configure the interval at which RSVP graceful-restart hello messages are sent to each neighbor, use the signalling hello graceful-restart refresh interval command in global configuration mode. To return to the default behavior, use the no form of this command.
signalling hello graceful-restart refresh interval refresh-interval
no signalling hello graceful-restart refresh interval
Syntax Description
refresh-interval
Interval at which RSVP graceful-restart hello messages are sent to each neighbor. Range is 3000 to 30000 milliseconds.
Defaults
refresh interval: 5000 milliseconds
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The signalling hello graceful-restart refresh interval command determines how often hello messages are sent to each neighbor. If the interval is made short, the hello messages are sent more frequently. Although a short interval may help detect failures quickly, it also results in increased network traffic. Optimizations in the RSVP hello mechanism exist to reduce the number of hello messages traveling over the network.
When an RSVP hello message is received, the receiving node acknowledges the hello and restarts its hello timer to the neighbor. By doing this, a hello is transmitted to the neighbor only if a hello is not received before the hello refresh interval has expired.
If two neighboring nodes do not have the same hello interval, the node with the larger hello interval has to acknowledge its neighbor's (more frequent) hellos. For instance, if node A has a hello interval of 5 seconds, and node B has a hello interval of 10 seconds, node B still has to send hello messages every 5 seconds.
The hello backoff mechanism is an optimization that is tailored to minimize the number of hello messages from a neighbor that either does not have graceful restart enabled, or that fails to come back up during the restart interval. The restart interval is provided by the neighbor in the restart cap object.
Task ID
Examples
The following example sets the hello graceful-restart refresh interval to 4000 msecs:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# signalling hello graceful-restart refresh interval 4000Related Commands
Configures the number of consecutive missed RSVP hello messages before a neighbor is declared down or unreachable.
signalling hello graceful-restart refresh misses
To configure the number of consecutive missed RSVP hello messages before a neighbor is declared down or unreachable, use the signalling hello graceful-restart refresh misses command in RSVP configuration mode. To return to the default behavior, use the no form of this command.
signalling hello graceful-restart refresh misses refresh-misses
no signalling hello graceful-restart refresh misses
Syntax Description
refresh-misses
The number of misses for hello messages before a neighbor is declared down or unreachable. Range is 1 to 10. Default is 3.
Defaults
refresh-misses: 3
Command Modes
RSVP configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If no hello messages (request or ACK) are received from a neighbor within the configured number of refresh misses, the node assumes that communication with the neighbor has been lost.
Task ID
Examples
The following example shows how to set hello graceful-restart refresh misses to 4:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# signalling hello graceful-restart refresh misses 4Related Commands
Configures the interval at which RSVP graceful restart hello messages are sent per neighbor.
signalling prefix-filtering access-list
To specify the extended access control list to use for prefix filtering of RSVP Router Alert messages, use the signalling prefix-filtering access-list command in RSVP configuration mode. To return to the default behavior, use the no form of this command.
signalling prefix-filtering access-list access list name
no signalling prefix-filtering access-list access list name
Syntax Description
Defaults
No default behavior or values
Command Modes
RSVP configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to configure the access control list name banks for prefix-filtering of RSVP Router Alert messages:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# signalling prefix-filtering access-list banksThe following example shows how to disable RSVP prefix-filtering of RSVP Router Alert messages:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# no signalling prefix-filtering access-list banksRelated Commands
Configures RSVP to drop messages when an access control list match yields an implicit deny.
signalling prefix-filtering default-deny-action
To configure RSVP to drop RSVP Router Alert messages when an access control list match returns an implicit deny, use the signalling prefix-filtering default-deny-action command in RSVP configuration mode. To return to the default behavior, use the no form of this command.
signalling prefix-filtering default-deny-action drop
no signalling prefix-filtering default-deny-action drop
Syntax Description
Defaults
Performs normal RSVP processing of Path, Path Tear, and ResvConfirm message packets.
Command Modes
RSVP configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure RSVP Router Alert messages when an access control list match returns an implicit deny:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvpRP/0/RP0/CPU0:router(config-rsvp)# signalling prefix-filtering default-deny-action dropRelated Commands
Configures extended access control lists for prefix-filtering of an RSVP Router Alert messages.
signalling rate-limit
To limit the rate of RSVP signaling messages being sent out a particular interface, use the signalling rate-limit command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
signalling rate-limit [rate messages] [interval interval-length]
no signalling rate-limit [rate messages] [interval interval-length]
Syntax Description
Defaults
messages: 100
interval-length: 1 second
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the rate-limiting feature with caution. Limiting the rate of RSVP signaling has the advantage of avoiding an overload of the next hop router's input queue, because such overloads would cause the next hop router to drop RSVP messages. However, reliable messaging and rapid retransmit usually enable the router to recover very rapidly from message drops; so rate limiting might not be necessary.
If the rate is set too low, it causes slower convergence times. This command limits all RSVP messages except acknowledgments (ACK) and SRefresh messages. The command does not let you make a router generate messages faster than its inherent limit. (That limit differs among router models.)
Task ID
Examples
The following example shows how to enable rate-limiting:
RP/0/RP0/CPU0:router# configure terminalRP/0/RP0/CPU0:router(config)# rsvp interface POS0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# signalling rate-limitThe following example shows how to limit the rate to 50 messages per second:
RP/0/RP0/CPU0:router# configure terminalRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# signalling rate-limit rate 50The following example shows how to set a limit at 40 messages for every 250 milliseconds:
RP/0/RP0/CPU0:router# configure terminalRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# signalling rate-limit rate 40 interval 250The following example shows how to restore the rate to the default of 100 messages per second:
RP/0/RP0/CPU0:router# configure terminalRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling rate-limit rateThe following example shows how to disable rate-limiting:
RP/0/RP0/CPU0:router# configure terminalRP/0/RP0/CPU0:router(config)# rsvp interface pos 0/3/0/0RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling rate-limitRelated Commands
Specifies the maximum bundle size of maximum size of single RSVP bundle message.
signalling refresh interval
To change the frequency with which a router updates the network about the RSVP state of a particular interface, use the signalling refresh interval command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
signalling refresh interval seconds
no signalling refresh interval
Syntax Description
seconds
Number of seconds the router waits to update the network about the RSVP state of an interface (specified in seconds). Range is 10 to 180 seconds. Default is 45 seconds.
Defaults
seconds: 45
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
RSVP relies on a soft-state mechanism to maintain state consistency in the face of network losses. That mechanism is based on continuous refresh messages to keep a state current. Each RSVP router is responsible for sending periodic refresh messages to its neighbors.
The router attempts to randomize network traffic and reduce metronomic burstiness by jittering the actual interval between refreshes by as much as 50 percent. As a result, refreshes may not be sent at exactly the interval specified. However, the average rate of refreshes are within the specified refresh interval.
Lengthening the interval reduces the refresh load of RSVP on the network but causes downstream nodes to hold state longer. This reduces the responsiveness of the network to failure scenarios. Shortening the interval improves network responsiveness but expands the messaging load on the network.
The reliable messaging extension, implemented through the signalling refresh reduction reliable command, may cause new or changed messages to be temporarily refreshed at a more rapid rate than specified, in order to improve network responsiveness.
The use of reliable messaging with rapid retransmit substantially improves network responsiveness in case of transient message loss; if the refresh interval is changed when using the reliable messaging feature, it is more useful to lengthen the interval than to shorten it.
The summary refresh extension, implemented through the signalling refresh reduction summary command, provides a lower-cost mechanism to refresh RSVP state. The router uses the same refresh interval between successive refreshes of a single state when using summary refresh and when using ordinary message-based refresh.
Task ID
Examples
The following example shows how to specify a refresh interval of 30 seconds:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh interval 30The following example shows how to restore the refresh interval to the default value of 45 seconds:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh intervalRelated Commands
signalling refresh missed
To specify the number of successive refresh messages that can be missed before the RSVP deems a state to be expired (resulting in the state to be torn down), use the signalling refresh missed command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
signalling refresh missed number
no signalling refresh missed
Syntax Description
Defaults
number: 4
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Decreasing the missed-message number improves RSVP responsiveness to major failures like router failure or link faults, but decreases the resilience of RSVP resulting in packet drops or temporary network congestion. The latter condition makes RSVP too sensitive.
Increasing the missed-message number increases the resilience of RSVP to such transient packet loss, but decreases the RSVP responsiveness to more intransient network failures such as router failure or link fault.
The default value of 4 provides a balance of resilience and responsiveness factors.
Task ID
Examples
The following example shows how to specify a missed refresh limit of six (6) messages:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh missed 6The following example shows how to return the missed refresh limit to the default value of four (4):
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh missedRelated Commands
signalling refresh reduction bundle-max-size
To configure the maximum size of a single RSVP bundle message, use the signalling refresh reduction bundle-max-size command in RSVP interface configuration mode.
signalling refresh reduction bundle-max-size size
Syntax Description
Defaults
size: 4096 bytes
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to set the maximum bundle size of a single RSVP bundle message to 4000:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction bundle-max-size 4000Related Commands
signalling refresh reduction disable
To disable RSVP refresh reduction on an interface, use the signalling refresh reduction disable command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
signalling refresh reduction disable
no signalling refresh reduction disable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The following features of the IETF refresh reduction standard RFC 2961 are enabled with this command:
•
•
•
•
Because refresh reduction relies on cooperation of the neighbor, the neighbor must also support the standard. If the router detects that a neighbor is not supporting the refresh reduction standard (either through observing the refresh-reduction-enabled bit in messages received from the next hop, or by sending a Message-ID object to the next hop and receiving an error), refresh reduction is not used on this link. That information is obtained through use of the show rsvp interface detail command.
Task ID
Examples
The following example shows how to disable RSVP refresh reduction on an interface:
RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction disableRP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2The following example shows how to enable RSVP refresh reduction on the interface:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh reduction disableRelated Commands
signalling refresh reduction reliable
To configure the parameters of reliable messaging, use the signalling refresh reduction reliable command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
signalling refresh reduction reliable [ack-max-size bytes | ack-hold-time milliseconds | retransmit-time milliseconds | summary-refresh]
no signalling refresh reduction reliable [ack-max-size bytes | ack-hold-time milliseconds | retransmit-time milliseconds | summary-refresh]
Syntax Description
Defaults
ack-max-size bytes: 4096
ack-hold-time milliseconds: 400 (0.4 seconds)
retransmit-time milliseconds: 900 (0.9 seconds)
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For reliable messaging to work properly, configure the retransmit time on the send router (A) and acknowledgment hold time on the peer router (B). (Vice versa for messages in reverse direction.)
The retransmit time must be greater than the acknowledgment hold time, so that the acknowledgment message has time to get back to the sender before the message retransmits. We recommend that the retransmit-time interval be at least twice the acknowledgment hold-time interval. If the retransmit-time value is smaller than the acknowledgment hold-time value, then router A retransmits the message even though router B may have received the message and is waiting for an acknowledgment hold time to time out to send the acknowledgment. This causes unnecessary network traffic.
Reducing the value of ack-max-size causes more acknowledgment messages to be issued, with fewer acknowledgments contained within each acknowledgment message. However, reducing the acknowledgment-max-size does not speed up the rate at which acknowledgment messages are issued, because their frequency is still controlled by the time values (acknowledgment hold time and retransmit time).
To use reliable messaging for summary refresh messages, use the rsvp interface interface-name signalling refresh reduction summary command.
Task ID
Examples
The following example shows how to set the maximum acknowledgment message size to 4096 bytes on POS interface 0/4/0/1:
RP/0/RP0/CPU0:router(config)# rsvp interface pos 0/4/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction reliable ack-max-size 4096The following example shows how to return the maximum acknowledgment message size to the default of 1000 bytes on POS interface 0/4/0/1:
RP/0/RP0/CPU0:router(config)# rsvp interface pos 0/4/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# no rsvp signalling refresh reduction reliableThe following example shows how to set the acknowledgment hold time to 1 second:
RP/0/RP0/CPU0:router(config)# rsvp interface pos 0/4/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction reliable ack-hold-time 1000The following example shows how to return the acknowledgment hold time to the default of 0.4 second:
RP/0/RP0/CPU0:router(config)# rsvp interface pos 0/4/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh reduction reliable ack-hold-timeThe following example shows how to set the retransmit timer to 2 seconds:
RP/0/RP0/CPU0:router(config)# rsvp interface pos 0/4/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction reliable retransmit-time 2000The following example shows how to return the retransmit timer to the default of 0.9 seconds:
RP/0/RP0/CPU0:router(config)# rsvp interface pos 0/4/0/1RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh reduction reliableThe following example shows how to enable the use of reliable transmission for RSVP summary refresh messages:
RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction reliable summary-refreshThe following example shows how to disable the use of reliable transmission for RSVP summary refresh messages:
RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh reduction reliable summary-refreshRelated Commands
signalling refresh reduction summary
To configure RSVP summary refresh message size on an interface, use the signalling refresh reduction summary command in RSVP interface configuration mode. To return to the default behavior, use the no form of this command.
signalling refresh reduction summary [max-size bytes]
no signalling refresh reduction summary [max-size bytes]
Syntax Description
max-size bytes
(Optional) Specifies the maximum size in bytes of a single RSVP summary refresh message. Range is 20 to 65000 bytes.
Defaults
bytes: 4096
Command Modes
RSVP interface configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the signalling refresh reduction summary command to specify the maximum size of the summary refresh messages sent. Message size is verified using the show rsvp interface detail command.
Task ID
Examples
The following example shows how to change the summary message maximum size on an interface:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# signalling refresh reduction summary max-size 6000The following example shows how to return the summary message maximum size to the default value on an interface:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# config rsvp interface tunnel-te 2RP/0/RP0/CPU0:router(config-rsvp-if)# no signalling refresh reduction summary max-size 6000Related Commands
Displays information about all interfaces with RSVP enabled.
Changes the frequency with which a router updates the network about the RSVP state of an interface.
window-size (RSVP)
To specify the maximum number of RSVP authenticated messages that can be received out of sequence, use the window-size command in RSVP authentication configuration mode, RSVP interface authentication configuration mode, or RSVP neighbor authentication configuration mode. To disable the window size, use the no form of this command.
window-size {N}
no window-size
Syntax Description
N
Size of the window to restrict out-of-sequence messages. Range is 1 to 64. Default is 1. All out-of-sequence messages are dropped.
Defaults
N: 1
Command Modes
RSVP authentication configuration
RSVP interface authentication configuration
RSVP neighbor authentication configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the window-size command to specify the maximum number of authenticated messages that are received out of sequence. All RSVP authenticated messages include a sequence number that is used to prevent replays of RSVP messages.
With a default window size of one message, RSVP rejects any out-of-order or out-of-sequence authenticated messages, because they are assumed to be replay attacks. However, sometimes bursts of RSVP messages become reordered between RSVP neighbors. If this occurs on a regular basis, and you can verify that the node sending the burst of messages is trusted, you can use the window-size option to adjust the burst size such that RSVP does not discard such reordered bursts. RSVP checks for duplicate messages within these bursts.
Task ID
Examples
The following example shows how to configure the size of the window to 33 in RSVP neighbor authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp neighbor 1.1.1.1 authenticationRP/0/RP0/CPU0:router(config-rsvp-nbor-auth)# window-size 33The following example shows how to configure the size of the window to 33 in RSVP authentication configuration mode:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp authenticationRP/0/RP0/CPU0:router(config-rsvp-auth)# window-size 33The following example shows how to configure the size of the window to 33 in RSVP interface authentication configuration mode by using the rsvp interface command:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# rsvp interface POS 0/2/1/0RP/0/RP0/CPU0:router(config-rsvp-if)# authenticationRP/0/RP0/CPU0:router(config-rsvp-if-auth)# window-size 33Related Commands
Specifies the source of the key information to authenticate RSVP signaling messages.
Controls how long RSVP maintains idle security associations with other trusted RSVP neighbors.
Feedback