Table Of Contents
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 statistics
show ip rsvp high-availability counters
show ip rsvp high-availability database
show ip rsvp high-availability summary
show ip rsvp host
show ip rsvp host vrf
show ip rsvp installed
show ip rsvp interface
show ip rsvp interface detail
show ip rsvp listeners
show ip rsvp neighbor
show ip rsvp policy
show ip rsvp policy cops
show ip rsvp policy identity
show ip rsvp policy local
show ip rsvp policy vrf
show ip rsvp precedence
show ip rsvp request
show ip rsvp reservation
show ip rsvp sbm
show ip rsvp sender
show ip rsvp signalling
show ip rsvp signalling blockade
show ip rsvp signalling fast-local-repair
show ip rsvp signalling rate-limit
show ip rsvp signalling refresh reduction
show ip rsvp tos
show ip rtp header-compression
show ip tcp header-compression
show ip vrf
show lane qos database
show ip rsvp hello client lsp summary
To display summary information about Resource Reservation Protocol (RSVP) traffic engineering (TE) client hellos for label-switched paths (LSPs), use the show ip rsvp hello client lsp summary command in user EXEC or privileged EXEC mode.
show ip rsvp hello client lsp summary
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SB
|
This command was introduced.
|
12.2(33)SRC
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
Use the show ip rsvp hello client lsp summary command to display information about the LSPs, including IP addresses and identification numbers.
Examples
The following is sample output from the show ip rsvp hello client lsp summary command:
Router# show ip rsvp hello client lsp summary
Local Remote tun_id lsp_id FLAGS
10.1.1.1 172.16.1.1 14 31 0x32
Table 76 describes the significant fields shown in the display.
Table 76 show ip rsvp hello client lsp summary Field Descriptions
Field
|
Description
|
Local
|
IP address of the tunnel sender.
|
Remote
|
IP address of the tunnel destination.
|
tun_id
|
Identification number of the tunnel.
|
lsp_id
|
Identification number of the LSP.
|
FLAGS
|
Database information.
|
Related Commands
Command
|
Description
|
show ip rsvp hello
|
Displays hello status and statistics for fast reroute, reroute (hello state timer), and graceful restart.
|
show ip rsvp hello client neighbor detail
To display detailed information about Resource Reservation Protocol (RSVP) traffic engineering (TE) client hellos for neighbors, use the show ip rsvp hello client neighbor detail command in user EXEC or privileged EXEC mode.
show ip rsvp hello client neighbor detail
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(29)S
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
Use the show ip rsvp hello client neighbor detail command to display information about the hello neighbors, including their state and type.
Examples
The following is sample output from the show ip rsvp hello client neighbor detail command:
Router# show ip rsvp hello client neighbor detail
Remote addr 10.0.0.1, Local addr 10.0.0.3
Nbr State: Normal Type: Reroute
Remote addr 172.16.1.1, Local addr 192.168.1.1
Nbr State: Normal Type: Graceful Restart
Table 77 describes the significant fields shown in the display. The fields provide information that uniquely identifies the neighbors. Clients can include graceful restart, reroute (hello state timer), and fast reroute.
Table 77 show ip rsvp hello client neighbor detail Field Descriptions
Field
|
Description
|
Remote addr
|
IP address of the remote neighbor. For graceful restart, this is the neighbor router's ID; for fast reroute and hello state timer (reroute), this is one of the neighbor's interface addresses.
|
Local addr
|
IP address of the local neighbor. For graceful restart, this is the neighbor router's ID; for fast reroute and hello state timer (reroute), this is one of the neighbor's interface addresses.
|
Nbr State
|
State of the neighbor; values can be the following:
• Normal = neighbor is functioning normally.
•Restarting = neighbor is restarting.
•Recover Nodal = neighbor is recovering from node failure.
•HST_GR_LOST = HST (hello state timer for reroute) is lost; waiting to see if graceful restart (GR) is also lost.
•WAIT PathTear = PathTear message is delayed to allow traffic in the pipeline to be transmitted.
|
Type
|
Type of client; graceful restart, Reroute (hello state timer), or Fast Reroute.
|
Nbr Hello State
|
State of hellos for the neighbor. Values are as follows:
•Up—Node is communicating with its neighbor.
•Lost—Communication has been lost.
•Init—Communication is being established.
|
LSPs protecting
|
Number of LSPs being protected.
|
I/F
|
Interface name and number associated with the hello instance.
|
Related Commands
Command
|
Description
|
show ip rsvp hello
|
Displays hello status and statistics for fast reroute, reroute (hello state timer), and graceful restart.
|
show ip rsvp hello client neighbor summary
To display summary information about Resource Reservation Protocol (RSVP) traffic engineering (TE) client hellos for neighbors, use the show ip rsvp hello client neighbor summary command in user EXEC or privileged EXEC mode.
show ip rsvp hello client neighbor summary
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(29)S
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
Use the show ip rsvp hello client neighbor summary command to display information about the neighbors, including state, type, and hello instance status.
Examples
The following is sample output from the show ip rsvp hello client neighbor summary command:
Router# show ip rsvp hello client neighbor summary
Local Remote Type NBR_STATE HI_STATE LSPs
10.0.0.1 10.0.0.3 RR Normal Up 1
172.16.1.1 192.168.1.1 GR Normal Lost 1
Table 78 describes the significant fields shown in the display.
Table 78 show ip rsvp hello client neighbor summary Field Descriptions
Field
|
Description
|
Local
|
IP address of the tunnel sender.
|
Remote
|
IP address of the tunnel destination.
|
Type
|
Type of client; graceful restart (GR), reroute (RR (hello state timer)), or fast reroute (FRR).
|
NBR_STATE
|
State of the neighbor; values can be the following:
•Normal—Neighbor is functioning normally.
•Restarting—Neighbor is restarting.
•Recover Nodal—Neighbor is recovering from node failure.
•HST_GR_LOST—HST (hello state timer for reroute) is lost; waiting to see if graceful restart (GR) is also lost.
•WAIT PathTear—PathTear message is delayed to allow traffic in the pipeline to be transmitted.
|
HI_STATE
|
State of hello instances for the neighbor. Values are as follows:
•Up—Node is communicating with its neighbor.
•Lost—Communication has been lost.
•Init—Communication is being established.
|
LSPs
|
Number of LSPs going to or coming from the neighbor.
|
Related Commands
Command
|
Description
|
show ip rsvp hello
|
Displays hello status and statistics for fast reroute, reroute (hello state timer), and graceful restart.
|
show ip rsvp hello graceful-restart
To display information about Resource Reservation Protocol (RSVP) traffic engineering (TE) graceful restart hellos, use the show ip rsvp hello graceful-restart command in user EXEC or privileged EXEC mode.
show ip rsvp hello graceful-restart
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(29)S
|
This command was introduced.
|
12.2(33)SRA
|
The command output was modified to show whether graceful restart is configured and full mode was added.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
Use the show ip rsvp hello graceful-restart command to display the status of graceful restart and related statistics.
Examples
The following is sample output from the show ip rsvp hello graceful-restart command:
Router# show ip rsvp hello graceful-restart
Graceful Restart: Enabled (full mode)
Refresh interval: 10000 msecs
Advertised restart time: 30000 msecs
Advertised recovery time: 120000 msecs
Maximum wait for recovery: 3600000 msecs
Table 79 describes the significant fields shown in the display.
Table 79 show ip rsvp hello graceful-restart Field Descriptions
Field
|
Description
|
Graceful Restart
|
Restart capability:
•Enabled—Restart capability is activated for a router (full mode) or its neighbor (help-neighbor).
•Disabled—Restart capability is not activated.
|
Refresh interval
|
Frequency in milliseconds (ms) with which a node sends a hello message to its neighbor.
|
Refresh misses
|
Number of missed hello messages that trigger a neighbor down event upon which stateful switchover (SSO) procedures are started.
|
DSCP
|
The differentiated services code point (DSCP) value in the IP header of the hello messages.
|
Advertised restart time
|
The time, in ms, that is required for the sender to restart the RSVP-TE component and exchange hello messages after a failure.
|
Advertised recovery time
|
The time, in ms, within which a recovering node wants its neighbor router to resynchronize the RSVP or Multiprotocol Label Switching (MPLS) forwarding state after SSO.
Note A zero value indicates that the RSVP or MPLS forwarding state is not preserved after SSO.
|
Maximum wait for recovery
|
The maximum amount of time, in ms, that the router waits for a neighbor to recover.
|
Related Commands
Command
|
Description
|
clear ip rsvp high-availability counters
|
Clears (sets to zero) the RSVP-TE HA counters that are being maintained by an RP.
|
ip rsvp signalling hello graceful-restart mode
|
Enables RSVP-TE graceful restart support capability on an RP.
|
ip rsvp signalling hello graceful-restart neighbor
|
Enables RSVP-TE graceful restart support capability on a neighboring router.
|
show ip rsvp hello
|
Displays hello status and statistics for fast reroute, reroute (hello state timer), and graceful restart.
|
show ip rsvp hello instance detail
To display detailed information about a hello instance, use the show ip rsvp hello instance detail command in user EXEC or privileged EXEC mode.
show ip rsvp hello instance detail [filter destination ip-address]
Syntax Description
filter destination ip-address
|
(Optional) IP address of the neighbor node.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.0(29)S
|
The command output was modified to include graceful restart, hello state timer (reroute), and fast reroute information.
|
12.2(18)SXD1
|
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
Use the show ip rsvp hello instance detail command to display information about the processes (clients) currently configured.
Examples
The following is sample output from the show ip rsvp hello instance detail command:
Router# show ip rsvp hello instance detail
Neighbor 10.0.0.3 Source 10.0.0.2
Type: Active (sending requests)
State: Up (for 2d19h2d19h)
Missed acks: 4, IP DSCP: 0x30
Statistics: (from 40722 samples)
Waverage: 6000 (Weight = 0.8)
Last sent Src_instance: 0xE617C847
Last recv nbr's Src_instance: 0xFEC28E95
Communication with neighbor lost:
Neighbor disabled Hello: 0
Neighbor 10.0.0.8 Source 10.0.0.7
Type: Passive (responding to requests)
Last sent Src_instance: 0xF7A80A52
Last recv nbr's Src_instance: 0xD2F1B7F7
Table 80 describes the significant fields shown in the display.
Table 80 show ip rsvp hello instance detail Field Descriptions
Field
|
Description
|
Neighbor
|
IP address of the adjacent node.
|
Source
|
IP address of the node that is sending the hello message.
|
Type
|
Values are Active (node is sending a request) and Passive (node is responding to a request).
|
I/F
|
Interface from which hellos are sent for this instance. Any means that the hellos can be sent out any interface.
|
State
|
Status of communication. Values are as follows:
•Up—Node is communicating with its neighbor.
•Lost—Communication has been lost.
•Init—Communication is being established.
|
Clients
|
Clients that created this hello instance; they include graceful restart, ReRoute (hello state timer), and Fast Reroute.
|
LSPs protecting
|
Number of LSPs that are being protected by this hello instance.
|
Missed acks
|
Number of times that communication was lost due to missed acknowledgments (ACKs).
|
IP DSCP
|
IP differentiated services code point (DSCP) value used in the hello IP header.
|
Refresh Interval (msec)
|
The frequency (in milliseconds) with which a node generates a hello message containing a Hello Request object for each neighbor whose status is being tracked.
|
Configured
|
Configured refresh interval.
|
Statistics
|
Refresh interval statistics from a specified number of samples (packets).
|
Min
|
Minimum refresh interval.
|
Max
|
Maximum refresh interval.
|
Average
|
Average refresh interval.
|
Waverage
|
Weighted average refresh interval.
|
Current
|
Current refresh interval.
|
Last sent Src_instance
|
The last source instance sent to a neighbor.
|
Last recv nbr's Src_instance
|
The last source instance field value received from a neighbor.
(0 means none received.)
|
Counters
|
Incremental information relating to communication with a neighbor.
|
Num times
|
Total number of times that communication with a neighbor was lost.
|
Reasons
|
Subsequent fields designate why communication with a neighbor was lost.
|
Missed acks
|
Number of times that communication was lost due to missed ACKs.
|
Bad Src_Inst received
|
Number of times that communication was lost due to bad source instance fields.
|
Bad Dst_Inst received
|
Number of times that communication was lost due to bad destination instance fields.
|
I/F went down
|
Number of times that the interface became unoperational.
|
Neighbor disabled Hello
|
Number of times that a neighbor disabled hello messages.
|
Msgs Received
|
Number of messages that were received.
|
Sent
|
Number of messages that were sent.
|
Suppressed
|
Number of messages that were suppressed due to optimization.
|
Related Commands
Command
|
Description
|
ip rsvp signalling hello (configuration)
|
Enables hello globally on the router.
|
ip rsvp signalling hello statistics
|
Enables hello statistics on the router.
|
show ip rsvp hello
|
Displays hello status and statistics for Fast reroute, reroute (hello state timer), and graceful restart.
|
show ip rsvp hello instance summary
|
Displays summary information about a hello instance.
|
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.0(29)S
|
The command output was modified to include graceful restart, reroute (hello state timer), and fast reroute information.
|
12.2(18)SXD1
|
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Examples
The following is sample output from the show ip rsvp hello instance summary command:
Router# show ip rsvp hello instance summary
Client Neighbor I/F State LostCnt LSPs Interval
RR 10.0.0.3 Se2/0 Up 0 1 6000
GR 10.1.1.1 Any Up 13 1 10000
GR 10.1.1.5 Any Lost 0 1 10000
GR 10.2.2.1 Any Init 1 0 5000
Active = Actively tracking neighbor state on behalf of clients:
RR = ReRoute, FRR = Fast ReRoute, or GR = Graceful Restart
Passive = Responding to hello requests from neighbor
Table 81 describes the significant fields shown in the display.
Table 81 show ip rsvp hello instance summary Field Descriptions
Field
|
Description
|
Active Instances
|
Active nodes that are sending hello requests.
|
Client
|
Clients on behalf of which hellos are sent; they include GR (graceful restart), RR (reroute = hello state timer), and FRR (Fast Reroute).
|
Neighbor
|
IP address of the adjacent node. For graceful restart, this is the neighbor router's ID; for Fast Reroute and hello state timer (reroute), this is one of the neighbor's interface addresses.
|
I/F
|
Interface from which hellos are sent for this instance. Any means that the hellos can be sent out any interface.
|
State
|
Status of communication. Values are as follows:
•Up—Node is communicating with its neighbor.
•Lost—Communication has been lost.
•Init—Communication is being established.
|
LostCnt
|
Number of times that communication was lost with the neighbor.
|
LSPs
|
Number of label-switched paths (LSPs) protected by this hello instance.
|
Interval
|
Hello refresh interval in milliseconds.
|
Passive Instances
|
Passive nodes that are responding to hello requests.
|
Neighbor
|
IP address of adjacent node. For graceful restart, this is the neighbor router's ID; for Fast Reroute and hello state timer (reroute), this is one of the neighbor's interface addresses.
|
I/F
|
Interface from which hellos are sent for this instance. Any means that the hellos can be sent out any interface.
|
Related Commands
Command
|
Description
|
ip rsvp signalling hello (configuration)
|
Enables hello globally on the router.
|
ip rsvp signalling hello statistics
|
Enables hello statistics on the router.
|
show ip rsvp hello
|
Displays hello status and statistics for fast reroute, reroute (hello state timer), and graceful restart.
|
show ip rsvp hello instance detail
|
Displays detailed information about a hello instance.
|
show ip rsvp hello statistics
To display how long hello packets have been in the hello input queue, use the show ip rsvp hello statistics command in user EXEC or privileged EXEC mode.
show ip rsvp hello statistics
Syntax Description
This command has no arguments or keywords.
Command Default
Information about how long hello packets have been in the hello input queue is not displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(18)SXD1
|
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T
|
Usage Guidelines
You can use this command to determine if the hello refresh interval is too small. If the interval is too small, communication may falsely be declared as lost.
Examples
The following is sample output from the show ip rsvp hello statistics command:
Router# show ip rsvp hello statistics
Weighted Average:0 (weight = 0.8)
Current length: 0 (max:500)
Number of samples taken: 2398525
Table 82 describes the significant fields shown in the display.
Table 82 show ip rsvp hello statistics Field Descriptions
Field
|
Description
|
Status
|
Indicator of whether Hello has been enabled globally on the router.
|
Current
|
Amount of time, in milliseconds, that the current hello packet has been in the Hello input queue.
|
Average
|
Average amount of time, in milliseconds, that hello packets are in the Hello input queue.
|
Max
|
Maximum amount of time, in milliseconds, that hello packets have been in the Hello input queue.
|
Current length
|
Current amount of time, in milliseconds, that hello packets have been in the Hello input queue.
|
Number of samples taken
|
Number of packets for which these statistics were compiled.
|
Related Commands
Command
|
Description
|
clear ip rsvp hello instance statistics
|
Clears hello statistics for an instance.
|
clear ip rsvp hello statistics
|
Clears hello statistics globally.
|
ip rsvp signalling hello refresh interval
|
Configures the hello request interval.
|
ip rsvp signalling hello statistics
|
Enables hello statistics on a router.
|
show ip rsvp high-availability counters
To display all Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) counters that are being maintained by a Route Processor (RP), use the show ip rsvp high-availability counters command in user EXEC or privileged EXEC mode.
show ip rsvp high-availability counters
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
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 show ip rsvp high-availability counters command to display the HA counters, which include state, ISSU, checkpoint messages, resource failures, and errors.
The command output differs depending on whether the RP is active or standby. (See the "Examples" section for more information.)
Use the clear ip rsvp high-availability counters command to clear all counters.
Examples
The following is sample output from the show ip rsvp high-availability counters command on the active RP:
Router# show ip rsvp high-availability counters
Checkpoint Messages (Items) Sent
Checkpoint Messages Transformed:
Table 83 describes the significant fields shown in the display.
Table 83 show ip rsvp high-availability counters—Active RP Field Descriptions
Field
|
Description
|
State
|
The RP state:
•Active—Active RP.
|
Bulk sync
|
The number of requests made by the standby RP to the active RP to resend all write database entries:
•Initiated—The number of bulk sync operations initiated by the standby RP since reboot.
|
Send timer
|
The write database timer.
|
Checkpoint Messages (Items) Sent
|
The details of the bundle messages or items sent since booting.
|
Succeeded
|
The number of bundle messages or items sent from the active RP to the standby RP since booting. Values are the following:
•Acks accepted—The number of bundle messages or items sent from the active RP to the standby RP.
•Acks ignored—The number of bundle messages or items sent by the active RP, but rejected by the standby RP.
•Nacks—The number of bundle messages or items given to the checkpointing facility (CF) on the active RP for transmitting to the standby RP, but failed to transmit.
|
Failed
|
The number of bundle messages or items the active RP attempted to send the standby RP when the send timer updated, but received an error back from CF.
|
Buffer alloc
|
Storage space allocated.
|
Buffer freed
|
Storage space available.
|
ISSU
|
In-Service Software Upgrade (ISSU) counters.
|
Checkpoint Messages Transformed
|
The details of the bundle messages or items transformed (upgraded or downgraded for compatibility) since booting so that the active RP and the standby RP can interoperate.
|
On Send
|
The number of messages sent by the active RP that succeeded, failed, or were transformations.
|
On Recv
|
The number of messages received by the active RP that succeeded, failed, or were transformations.
|
Negotiation
|
The number of times that the active RP and the standby RP have negotiated their interoperability parameters.
|
Started
|
The number of negotiations started.
|
Finished
|
The number of negotiations finished.
|
Failed to Start
|
The number of negotiations that failed to start.
|
Messages
|
The number of negotiation messages sent and received. These messages can be succeeded or failed.
•Send succeeded—Number of messages sent successfully.
•Send failed—Number of messages sent unsuccessfully.
•Buffer allocated—Storage space allowed.
•Buffer freed—Storage space available.
•Buffer alloc failed—No storage space available.
|
Init
|
The number of times the RSVP ISSU client has successfully and unsuccefully (failed) initialized.
|
Session Registration
|
The number of session registrations, succeeded and failed, performed by the active RP whenever the standby RP reboots.
|
Session Unregistration
|
The number of session unregistrations, succeeded and failed, before the standby RP resets.
|
Errors
|
The details of errors or caveats.
|
The following is sample output from the show ip rsvp high-availability counters command on the standby RP:
Router# show ip rsvp high-availability counters
Checkpoint Messages (Items) Received
Checkpoint Messages Transformed:
Table 84 describes the significant fields shown in the display.
Table 84 show ip rsvp high-availability counters—Standby RP Field Descriptions
Field
|
Description
|
State
|
The RP state:
•Standby—Standby (backup) RP.
|
Checkpoint Messages (Items) Received
|
The details of the messages or items received by the standby RP. Values are the following:
•Valid—The number of valid messages or items received by the standby RP.
•Invalid—The number of invalid messages or items received by the standby RP.
•Buffer freed—Amount of storage space available.
|
ISSU
|
ISSU counters.
Note For descriptions of the ISSU fields, see Table 83.
|
Errors
|
The details of errors or caveats.
|
Related Commands
Command
|
Description
|
clear ip rsvp high-availability counters
|
Clears (sets to zero) the RSVP-TE HA counters that are being maintained by an RP.
|
show ip rsvp high-availability database
|
Displays the contents of the RSVP-TE HA read and write databases used in TE SSO.
|
show ip rsvp high-availability summary
|
Displays summary information for an RSVP-TE HA RP.
|
show ip rsvp high-availability database
To display the contents of the Resource Reservation Protocol (RSVP) high availability (HA) read and write databases used in traffic engineering (TE), use the show ip rsvp high-availability database command in user EXEC or privileged EXEC mode.
show ip rsvp high-availability database {hello | link-management {interfaces [fixed | variable]
| system} | lsp [filter destination ip-address | filter lsp-id lsp-id | filter source ip-address |
filter tunnel-id tunnel-id] | lsp-head [filter number] | summary}
Syntax Description
hello
|
Displays information about the hello entries in the read and write databases.
|
link-management
|
Displays information about the link-management entries in the read and write databases.
|
interfaces
|
Displays information about the link-management interfaces in the read and write databases.
|
fixed
|
(Optional) Displays information about the link-management fixed interfaces in the read and write databases.
|
variable
|
(Optional) Displays information about the link-management variable interfaces in the read and write databases.
|
system
|
Displays information about the link-management system in the read and write databases.
|
lsp
|
Displays information about the label switched path (LSP) entries in the read and write databases.
|
filter destination ip-address
|
(Optional) Displays filtered information on the IP address of the destination (tunnel tail).
|
filter lsp-id lsp-id
|
(Optional) Displays filtered information on a specific LSP ID designated by a number from 0 to 65535.
|
filter source ip-address
|
(Optional) Displays filtered information on the IP address of the source (tunnel head).
|
filter tunnel-id tunnel-id
|
(Optional) Displays filtered information on a specific tunnel ID designated by a number from 0 to 65535.
|
lsp-head
|
Displays information about the LSP-headend entries in the read and write databases.
|
filter number
|
(Optional) Displays filtered information on a specific LSP-head router designated by a number from 0 to 65535.
|
summary
|
Displays cumulative information about the entries in the read and write databases.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SRA
|
This command was introduced.
|
12.2(33)SRB
|
The command output was modified to display the result of a loose hop expansion performed on the router.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.2(33)SRC
|
This command was integrated into Cisco IOS Release 12.2(33)SRC. The command output was modified to include path protection information if you specify the lsp-head keyword.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
Use the show ip rsvp high-availability database command to display information about the entries in the read and write databases.
Use the show ip rsvp high-availability database lsp command to display loose hop information. A loose hop expansion can be performed on a router when the router processes the explicit router object (ERO) for an incoming path message. After the router removes all local IP addresses from the incoming ERO, it finds the next hop. If the ERO specifies that the next hop is loose instead of strict, the router consults the TE topology database and routing to determine the next hop and output interface to forward the path message. The result of the calculation is a list of hops; that list is placed in the outgoing ERO and checkpointed with the LSP data as the loose hop information.
Use the show ip rsvp high-availability database lsp-head command on a headend router only. On other routers, this command gives no information.
Examples
Hello Example on Active RP
The following is sample output from the show ip rsvp high-availability database hello command on an active Route Processor (RP):
Router# show ip rsvp high-availability database hello
State: Checkpointed Action: Add
Last sent Src_instance: 0xDE435865
Table 85 describes the significant fields shown in the displays.
Table 85 show ip rsvp high-availability database hello—Active RP Field Descriptions
Field
|
Description
|
HELLO WRITE DB
|
Storage area for active RP hello data consisting of checkpointed RSVP-TE information that is sent to the standby RP when it becomes the active RP and needs to recover LSPs. This field is blank on a standby RP.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
•Ack-Pending—Entries have been sent, but not acknowledged.
•Checkpointed—Entries have been sent and acknowledged by the standby RP.
•Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
•Add—Adding an item to the standby RP.
•Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an acknowledgment (ack) of the delete operation.
•Modify—Modifying an item on the standby RP.
•Remove—Removing an item from the standby RP.
|
Seq #
|
Numbers used by the active and standby RPs to synchronize message acks and negative acknowledgments (nacks) to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information.
|
Last sent Src_instance
|
Last source instance identifier sent.
|
HELLO READ DB
|
Storage area for standby RP hello data. This field is blank on an active RP except when it is in recovery mode.
|
Hello Example on Standby RP
The following is sample output from the show ip rsvp high-availability database hello command on a standby RP:
Router# show ip rsvp high-availability database hello
State: Checkpointed Action: Add
Last sent Src_instance: 0xDE435865
These fields are the same as those for the active RP described in Table 85 except they are now in the read database for the standby RP.
Link-Management Interfaces Example on an Active RP
The following is sample output from the show ip rsvp high-availability database link-management interfaces command on an active RP:
Router# show ip rsvp high-availability database link-management interfaces
Flooding Protocol: ospf IGP Area ID: 0 Link ID: 0 (GigabitEthernet3/2)
State: Checkpointed Action: Add
Ifnumber: 5 Link Valid Flags: 0x193B
Link Subnet Type: Broadcast
Local Intfc ID: 0 Neighbor Intf ID: 0
Link IP Address: 172.16.3.1
Neighbor IGP System ID: 172.16.3.2 Neighbor IP Address: 10.0.0.0
IGP Metric: 1 TE Metric: 1
Physical Bandwidth: 1000000 kbits/sec
Res. Global BW: 3000 kbits/sec
Reservable Bandwidth[0]: 0 0 kbits/sec
Reservable Bandwidth[1]: 0 0 kbits/sec
Reservable Bandwidth[2]: 0 0 kbits/sec
Reservable Bandwidth[3]: 0 0 kbits/sec
Reservable Bandwidth[4]: 0 0 kbits/sec
Reservable Bandwidth[5]: 0 0 kbits/sec
Reservable Bandwidth[6]: 0 0 kbits/sec
Reservable Bandwidth[7]: 0 0 kbits/sec
Reservable Bandwidth[0]: 3000 0 kbits/sec
Reservable Bandwidth[1]: 3000 0 kbits/sec
Reservable Bandwidth[2]: 3000 0 kbits/sec
Reservable Bandwidth[3]: 3000 0 kbits/sec
Reservable Bandwidth[4]: 3000 0 kbits/sec
Reservable Bandwidth[5]: 3000 0 kbits/sec
Reservable Bandwidth[6]: 3000 0 kbits/sec
Reservable Bandwidth[7]: 2900 0 kbits/sec
Protection Type: Capability 0, Working Priority 0
Table 86 describes the significant fields shown in the display.
Table 86 show ip rsvp high-availability database link-management interfaces—Active RP Field Descriptions
Field
|
Description
|
TE LINK WRITE DB
|
Storage area for active TE RP link data. This field is blank on a standby RP.
|
Flooding Protocol
|
Protocol that is flooding information for this area. ospf = Open Shortest Path First.
|
IGP Area ID
|
Interior Gateway Protocol (IGP) identifier for the area being flooded.
|
Link ID
|
Link identifier and interface for the area being flooded.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
•Ack-Pending—Entries have been sent, but not acknowledged.
•Checkpointed—Entries have been sent and acknowledged by the standby RP.
•Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
•Add—Adding an item to the standby RP.
•Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete operation.
•Modify—Modifying an item on the standby RP.
•Remove—Removing an item from the standby RP.
|
Seq #
|
Numbers used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information.
|
Ifnumber
|
Interface number.
|
Link Valid Flags
|
Attributes used to identify or track links.
|
Link Subnet Type
|
Subnet type of the link. Values are as follows:
•Broadcast—Data for multiple recipients.
•Nonbroadcast Multiaccess—A network in which data is transmitted directly from one computer to another over a virtual circuit or across a switching fabric.
•Point-to-Multipoint—Unidirectional connection in which a single source end system (known as a root node) connects to multiple destination end systems (known as leaves).
•Point-to-Point—Unidirectional or bidirectional connection between two end systems.
•Unknown subnet type—Subnet type not identified.
|
Local Intfc ID
|
Local interface identifier.
|
Neighbor Intf ID
|
Neighbor's interface identifier.
|
Link IP Address
|
IP address of the link.
|
Neighbor IGP System ID
|
Neighbor system identifier configured using IGP.
|
Neighbor IP Address
|
Neighbor's IP address.
|
IGP Metric
|
Metric value for the TE link configured using IGP.
|
TE Metric
|
Metric value for the TE link configured using Multiprotocol Label Switching (MPLS) TE.
|
Physical Bandwidth
|
Link bandwidth capacity (in kilobits per second).
|
Res. Global BW
|
Amount of reservable global pool bandwidth (in kilobits per second) on this link.
|
Res. Sub BW
|
Amount of reservable subpool bandwidth (in kilobits per second) on this link.
|
Upstream
|
Header for the following section of bandwidth values.
|
Global Pool
|
Global pool bandwidth (in kilobits per second) on this link.
|
Sub Pool
|
Subpool bandwidth (in kilobits per second) on this link.
|
Reservable Bandwidth [1]
|
Amount of bandwidth (in kilobits per second) available for reservations in the global TE topology and subpools.
|
Downstream
|
Header for the following section of bandwidth values.
|
Affinity Bits
|
Link attributes required in tunnels.
|
Protection Type
|
LSPs protected by fast reroute (FRR). Capability = LSPs capable of using FRR. Working Priority = LSPs actually using FRR.
|
Number of TLVs
|
Number of type, length, values (TLVs).
|
The fields for a standby RP are the same as those described in Table 86 except they are now in the TE link read database instead of the TE link write database that is used by an active RP.
Link-Management System Example on an Active RP
The following is sample output from the show ip rsvp high-availability database link-management system command on an active RP:
Router# show ip rsvp high-availability database link-management system
Flooding Protocol: OSPF IGP Area ID: 0
State: Checkpointed Action: Modify
LSA Valid flags: 0x0 Node LSA flag: 0x0
IGP System ID: 172.16.3.1 MPLS TE Router ID: 10.0.0.3
Flooded links: 1 TLV length: 0 (bytes)
Table 87 describes the significant fields shown in the display.
Table 87 show ip rsvp high-availability database link-management system—Active RP Field Descriptions
Field
|
Description
|
TE SYSTEM WRITE DB
|
Storage area for active TE RP system data. This field is blank on a standby RP.
|
Flooding Protocol
|
Protocol that is flooding information for this area. OSPF = Open Shortest Path First.
|
IGP Area ID
|
IGP identifier for the area being flooded.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
•Ack-Pending—Entries have been sent, but not acknowledged.
•Checkpointed—Entries have been sent and acknowledged by the standby RP.
•Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
•Add—Adding an item to the standby RP.
•Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete operation.
•Modify—Modifying an item on the standby RP.
•Remove—Removing an item from the standby RP.
|
Seq #
|
Numbers used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information.
|
LM Flood Data
|
Link management (LM) flood data.
|
LSA Valid flags
|
Link-state advertisement (LSA) attributes.
|
Node LSA flag
|
LSA attributes used by a router.
|
IGP System ID
|
Identification (IP address) that IGP flooding uses in this area to identify this node.
|
MPLS TE Router ID
|
MPLS TE router identifier (IP address).
|
Flooded links
|
Number of flooded links.
|
TLV length
|
TLV length in bytes.
|
Fragment id
|
Fragment identifier for this link.
|
TE SYSTEM READ DB
|
Storage area for standby TE RP system data. This field is blank on a standby RP.
|
The fields for a standby RP are the same as those described in Table 87 except they are now in the TE system read database instead of the TE system write database that is used by an active RP.
LSP Example on an Active RP
The following is sample output from the show ip rsvp high-availability database lsp command on an active RP:
Router# show ip rsvp high-availability database lsp
Sender: 10.0.0.3 Ext. Tun ID: 10.0.0.3
State: Checkpointed Action: Add
10.0.0.2 10.10.2.2 10.10.2.3 10.1.1.1
Table 88 describes the significant fields shown in the display.
Table 88 show ip rsvp high-availability database lsp—Active RP Field Descriptions
Field
|
Description
|
LSP WRITE DB
|
Storage area for active RP LSP data. This field is blank on a standby RP.
|
Tun ID
|
Tunnel identifier.
|
LSP ID
|
LSP identifier.
|
Dest
|
Tunnel destination IP address.
|
Sender
|
Tunnel sender IP address.
|
Ext. Tun ID
|
Extended tunnel identifier; usually set to 0 or the sender's IP address.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
•Ack-Pending—Entries have been sent, but not acknowledged.
•Checkpointed—Entries have been sent and acknowledged by the standby RP.
•Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
•Add—Adding an item to the standby RP.
•Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete operation.
•Modify—Modifying an item on the standby RP.
•Remove—Removing an item from the standby RP.
|
Seq #
|
Numbers used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information.
|
InLabel
|
Incoming label identifier.
|
Out I/F
|
Outgoing interface.
|
Next-Hop
|
Next hop IP address.
|
OutLabel
|
Outgoing label identifier.
|
Loose hop info
|
Lists the loose hop expansions performed on the router, or specifies None.
|
LSP READ DB
|
Storage area for standby RP LSP data. This field is blank on an active RP.
|
The fields for a standby RP are the same as those described in Table 88 except they are now in the LSP read database instead of the LSP write database that is used by an active RP.
LSP-Head Example on an Active RP
The following is sample output from the show ip rsvp high-availability database lsp-head command on an active RP:
Router# show ip rsvp high-availability database lsp-head
State: Checkpointed Action: Add
lsp_id: 8, bandwidth: 100, thead_flags: 0x1, popt: 1
feature_flags: path protection active
output_if_num: 5, output_nhop: 172.16.3.2
Destination: 10.0.0.9, Id: 10.0.0.9 Router Node (ospf) flag:0x0
IGP: ospf, IGP area: 0, Number of hops: 5, metric: 2
Hop 0: 172.16.3.1, Id: 172.16.3.1 Router Node (ospf), flag:0x0
Hop 1: 172.16.3.2, Id: 10.0.0.7 Router Node (ospf), flag:0x0
Hop 2: 172.16.6.1, Id: 10.0.0.7 Router Node (ospf), flag:0x0
Hop 3: 172.16.6.2, Id: 10.0.0.9 Router Node (ospf), flag:0x0
Hop 4: 10.0.0.9, Id: 10.0.0.9 Router Node (ospf), flag:0x0
Table 89 describes the significant fields shown in the display.
Table 89 show ip rsvp high-availability database lsp-head—Active RP Field Descriptions
Field
|
Description
|
LSP_HEAD WRITE DB
|
Storage area for active RP LSP-head data. This field is blank on a standby RP.
|
Tun ID
|
Tunnel identifier.
|
Header
|
Header information.
|
State
|
Status of an entry. Values are as follows:
•Ack-Pending—Entries have been sent, but not acknowledged.
•Checkpointed—Entries have been sent and acknowledged by the standby RP.
•Send-Pending—Entries are waiting to be sent.
|
Action
|
Action taken. Values are as follows:
•Add—Adding an item to the standby RP.
•Delete—Deleting an item from the standby RP. This action appears temporarily while the active RP awaits an ack of the delete operation.
•Modify—Modifying an item on the standby RP.
•Remove—Removing an item from the standby RP.
|
Seq #
|
Numbers used by the active and standby RPs to synchronize message acks and nacks to messages sent.
|
Flags
|
Attribute used to identify or track data.
|
Data
|
Information.
|
lsp_id
|
LSP identifier.
|
bandwidth
|
Bandwidth on the LSP (in kilobits per second).
|
thead_flags
|
Tunnel head attribute used to identify or track data.
|
popt
|
Parsing option number.
|
feature_flags
|
Indicates whether the LSP being used to forward traffic is the secondary LSP using the path protection path-option. Valid values are as follows:
•none
•path protection active
|
output_if_num
|
Output interface number.
|
output_nhop
|
Output next hop IP address.
|
RRR path setup info
|
Routing with Resource Reservation (RRR) path information.
|
Destination
|
Destination IP address.
|
Id
|
IP address and protocol of the routing node. Values are the following:
•isis = Intermediate System-to-Intermediate System
•ospf = Open Shortest Path First
|
flag
|
Attribute used to track data.
|
IGP
|
Interior Gateway Protocol. ospf = Open Shortest Path First.
|
IGP area
|
IGP area identifier.
|
Number of hops
|
Number of connections or routers.
|
metric
|
Routing cost.
|
Hop
|
Hop's number and IP address.
|
Id
|
IP address and protocol of the routing node. Values are the following:
•isis = Intermediate System-to-Intermediate System
•ospf = Open Shortest Path First
|
flag
|
Attribute used to track data.
|
LSP_HEAD READ DB
|
Storage area for standby RP LSP-head data. This field is blank on an active RP.
|
The fields for a standby RP are the same as those described in Table 89 except they are now in the LSP_head read database instead of the LSP_head write database that is used by an active RP.
Summary Example on an Active RP
The following is sample output from the show ip rsvp high-availability database summary command on an active RP:
Router# show ip rsvp high-availability database summary
Table 90 describes the significant fields shown in the display.
Table 90 show ip rsvp high-availability database summary—Active RP Field Descriptions
Field
|
Description
|
Write DB
|
Storage area for active RP summary data. This field is blank on a standby RP.
|
Send-Pending
|
Entries are waiting to be sent.
|
Ack-Pending
|
Entries have been sent, but are waiting to be acknowledged.
|
Checkpointed
|
Entries have been sent and acknowledged.
|
Total
|
Total number of entries in the write database.
|
Total
|
Total number of entries in the read database.
|
Summary Example on a Standby RP
The following is sample output from the show ip rsvp high-availability database summary command on a standby RP:
Router# show ip rsvp high-availability database summary
Table 91 describes the significant fields shown in the display.
Table 91 show ip rsvp high-availability database summary—Standby RP Field Descriptions
Field
|
Description
|
Write DB
|
Storage area for active RP summary data.
|
Send-Pending
|
Entries are waiting to be sent.
|
Ack-Pending
|
Entries have been sent, but are waiting to be acknowledged.
|
Checkpointed
|
Entries have been sent and acknowledged.
|
Total
|
Total number of entries in the write DB.
|
Total
|
Total number of entries in the read DB.
|
Related Commands
Command
|
Description
|
show ip rsvp high-availability counters
|
Displays all RSVP HA counters that are being maintained by an RP.
|
show ip rsvp high-availability summary
|
Displays summary information for an RSVP HA RP.
|
show ip rsvp high-availability summary
To display summary information for a Resource Reservation Protocol (RSVP) traffic engineering (TE) high availability (HA) Route Processor (RP), use the show ip rsvp high-availability summary command in user EXEC or privileged EXEC mode.
show ip rsvp high-availability summary
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
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
Use the show ip rsvp high-availability summary command to display information about the HA parameters currently configured on an RP.
The command output differs depending on whether the RP is active or standby.
Examples
The following is sample output from the show ip rsvp high-availability summary command on an active RP:
Router# show ip rsvp high-availability summary
Graceful-Restart: Enabled, mode: full
Send timer: not running (Interval: 1000 msec)
Items sent per Interval: 200
CF buffer size used: 2000
Note On a standby RP, only the first three lines of the output are displayed. On an active RP, all lines are displayed.
Table 92 describes the significant fields shown in the display.
Table 92 show ip rsvp high-availability summary Field Descriptions
Field
|
Description
|
State
|
Status of graceful restart and HA.
|
Graceful Restart
|
Restart capability:
•Enabled—Restart capability is activated for a router (full mode) or its neighbor (help-neighbor).
•Disabled—Restart capability is not activated.
|
HA state
|
The RP state, which is the following:
•Active—Active RP.
•Standby—Standby (backup) RP.
•Recovering—The active RP is in recovery period.
|
Checkpointing
|
The function that copies state information (write database entries) from the active RP to the standby RP. Values are the following:
•Allowed—Functioning normally.
•Not Allowed—Checkpointing is not allowed. Reasons may be that the RP is not present or not ready.
|
Messages
|
The checkpointed messages that the active RP sends to the standby RP during a specified interval.
|
Send timer
|
The write database timer. Values are the following:
•running—Entries are in the write database in the send-pending state and checkpointing is allowed.
•not running—Checkpointing is not allowed or the write database is empty.
Note Entries in the write database can be in the following states:
•Send-Pending—The entry has not been sent to the standby RP yet.
•Ack-Pending—The entry was sent to the standby RP, but no acknowledgment was received from the standby RP yet.
•Checkpointed—The checkpointing facility (CF) message has been acknowledged by the standby RP, which notifies the active RP.
|
Interval
|
Time, in milliseconds (ms), when the active RP sends messages to the standby RP.
|
Items sent per Interval
|
The number of database entries (data that has been taken from the write database and packed into bundle message for transmitting to the standby RP), which the active RP sends to the standby RP each time the write database timer activates.
|
CF buffer size used
|
Amount of storage space, in bytes, used by the checkpointing facility.
|
In some cases, the checkpointing field displays Not Allowed. Here is an excerpt from sample output:
Checkpointing: Not Allowed
Note If checkpointing is allowed, the attributes displayed in the sample output do not appear. Refer to the show ip rsvp high-availability summary command output on an active RP for more details.
Table 93 describes the significant fields shown in the display.
Table 93 show ip rsvp high-availability summary—Checkpointing Field Descriptions
Field
|
Description
|
Peer RP Present : No
|
The active RP cannot communicate with any peer RP.
Note This can happen if the standby RP is removed, or if it is temporarily unavailable, such as during a restart.
|
RF Comm. Up : No
|
The redundant facility (RF) on the active RP is unable to communicate with the RF on the standby RP.
|
Flow Control On : No
|
The active RP cannot send Internet Protocol communications (IPC) messages (using checkpointing) to the standby RP because flow control is off.
|
CF Comm. Up : No
|
The TE CF client on the active RP is unable to communicate with the TE CF client on the standby RP.
|
RF Ready to Recv : No
|
The RF on the standby RP is not ready to receive checkpoint messages.
|
The following is sample output from the show ip rsvp high-availability summary command after a stateful switchover (SSO) has occurred.
Router# show ip rsvp high-availability summary
Graceful-Restart: Enabled
Last recorded: 75012 msec
Send timer: not running (Interval:1000)
Items sent per Interval: 200
Table 94 describes the significant fields shown in the display
.
Table 94 show ip rsvp high-availability summary—After an SSO Field Descriptions
Field
|
Description
|
Advertised
|
The advertised recovery time, in milliseconds.
|
Last recorded
|
The last recorded recovery time, in milliseconds.
|
Related Commands
Command
|
Description
|
clear ip rsvp high-availability counters
|
Clears (sets to zero) the RSVP-TE HA counters that are being maintained by an RP.
|
show ip rsvp high-availability counters
|
Displays the RSVP-TE HA counters that are being maintained by an RP.
|
show ip rsvp high-availability database
|
Displays the contents of the RSVP-TE HA read and write databases used in TE SSO.
|
show ip rsvp host
To display specific information for a Resource Reservation Protocol (RSVP) host, use the show ip rsvp host command in user EXEC or privileged EXEC mode.
show ip rsvp host {senders | receivers} [group-name | group-address]
Syntax Description
senders
|
RSVP-related sender information currently in the database.
|
receivers
|
RSVP-related receiver information currently in the database.
|
group-name
|
(Optional) Hostname of the source or destination.
|
group-address
|
(Optional) IP address of the source or destination.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
12.4(6)T
|
The command output was modified to display RSVP identity information when configured.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
Use the show ip rsvp host command to display static RSVP senders and receivers. If a router has any local host receivers or senders that have RSVP identities configured, the application IDs that they use are also displayed.
Examples
In the following example from the show ip rsvp host senders command, no RSVP identities are configured for the local sender:
Router# show ip rsvp host senders
To From Pro DPort Sport Prev Hop I/F BPS
192.168.104.3 192.168.104.1 UDP 1 1 10K
Table 95 describes the significant fields shown in the display.
Table 95 show ip rsvp host senders (No RSVP Identities Configured) Field Descriptions
Field
|
Description
|
To
|
IP address of the receiver.
|
From
|
IP address of the sender.
|
Pro
|
Protocol code. IP protocol such as TCP or UDP.
|
DPort
|
Destination port number. Code 1 indicates IP protocol such as TCP or UDP.
|
Sport
|
Source port number. Code 1 indicates IP protocol such as TCP or UDP.
|
Prev Hop
|
IP address of the previous hop. Blank means no previous hop.
|
I/F
|
Interface of the previous hop.
|
BPS
|
Reservation rate, in bits per second (bps).
|
Mode(s)
|
Any of the following strings:
•Host—The router is acting as the host system or RSVP endpoint for this reservation.
•LSP-Tunnel—The reservation is for a Traffic Engineering (TE) tunnel.
•MIB—The reservation was created via an SNMP SET directive from a remote management station.
•CLI—The reservation was created via a local RSVP CLI command.
•Host CLI—A combination of the host and CLI strings meaning that the static sender being displayed was created by the ip rsvp sender-host CLI command.
|
In the following example from the show ip rsvp host senders command, an RSVP identity is configured for the local sender and more information displays:
Router# show ip rsvp host senders
To From Pro DPort Sport Prev Hop I/F BPS
192.168.104.3 192.168.104.1 UDP 1 1 10K
Locator: GUID=www.cisco.com,APP=voice,VER=100.0
Table 96 describes the significant fields shown in the display.
Table 96 show ip rsvp host senders (RSVP Identity Configured) Field Descriptions
Field
|
Description
|
To
|
IP address of the receiver.
|
From
|
IP address of the sender.
|
Pro
|
Protocol code. IP protocol such as TCP or UDP.
|
DPort
|
Destination port number. Code 1 indicates IP protocol such as TCP or UDP.
|
Sport
|
Source port number. Code 1 indicates IP protocol such as TCP or UDP.
|
Prev Hop
|
IP address of the previous hop. Blank means no previous hop.
|
I/F
|
Interface of the previous hop.
|
BPS
|
Reservation rate in bits per second (bps).
|
Mode(s)
|
Any of the following strings:
•Host—The router is acting as the host system or RSVP endpoint for this reservation.
•LSP-Tunnel—The reservation is for a Traffic Engineering (TE) tunnel.
•MIB—The reservation was created via an SNMP SET directive from a remote management station.
•CLI—The reservation was created via a local RSVP CLI command.
•Host CLI—A combination of the host and CLI strings meaning that the static sender being displayed was created by the ip rsvp sender-host CLI command.
|
Identity
|
The alias string for the RSVP application ID.
|
Locator
|
The application ID that is being signaled in the RSVP PATH message for this statically-configured sender.
|
ID Type
|
Types of identities. RSVP defines two types: application IDs (Application) and user IDs (User). Cisco IOS software currently supports Application only.
|
Related Commands
Command
|
Description
|
ip rsvp sender-host
|
Enables a router to simulate a host generating an RSVP PATH message.
|
show ip rsvp host vrf
To display specific information for a Resource Reservation Protocol (RSVP) host configured with a virtual routing and forwarding (VRF) instance, use the show ip rsvp host vrf command in user EXEC or privileged EXEC mode.
show ip rsvp host vrf {* | vrf-name} {receivers | senders} [group-name | group-address]
Syntax Description
*
|
Displays all VRFs.
|
vrf-name
|
Name of a specified VRF.
|
receivers
|
Displays RSVP-related receiver information currently in the database.
|
senders
|
Displays RSVP-related sender information currently in the database.
|
group-name
|
(Optional) Hostname of the source or destination.
|
group-address
|
(Optional) IP address of the source or destination.
|
Command Modes
User EXEC (<)
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.0(1)M
|
This command was introduced.
|
Usage Guidelines
Use the show ip rsvp host vrf command to display VRFs and static RSVP senders and receivers.
Examples
In the following example from the show ip rsvp host vrf * senders command, VRFs are displayed for the local senders:
Router# show ip rsvp host vrf * senders
To From Pro DPort Sport Prev Hop I/F BPS
192.168.104.4 198.168.104.12 UDP 10 10 none none 10K
To From Pro DPort Sport Prev Hop I/F BPS
192.168.105.4 198.168.105.12 UDP 10 10 none none 10K
Table 97 describes the significant fields shown in the display.
Table 97 show ip rsvp host vrf * senders Field Descriptions
Field
|
Description
|
VRF
|
Name of the VRF.
|
To
|
IP address of the receiver.
|
From
|
IP address of the sender.
|
Pro
|
Protocol code. IP protocol such as TCP or UDP.
|
DPort
|
Destination port number. Code 1 indicates an IP protocol such as TCP or UDP.
|
Sport
|
Source port number. Code 1 indicates an IP protocol such as TCP or UDP.
|
Prev Hop
|
IP address of the previous hop. Blank means no previous hop.
|
I/F
|
Interface of the previous hop.
|
BPS
|
Reservation rate in bits per second (bps).
|
Mode(s)
|
Any of the following strings:
•Host—The router is acting as the host system or RSVP endpoint for this reservation.
•LSP-Tunnel—The reservation is for a Traffic Engineering (TE) tunnel.
•MIB—The reservation was created via an SNMP SET directive from a remote management station.
•CLI—The reservation was created via a local RSVP CLI command.
•Host CLI—A combination of the host and CLI strings meaning that the static sender being displayed was created by the ip rsvp sender-host CLI command.
|
Related Commands
Command
|
Description
|
show ip rsvp host
|
Displays specific information for an RSVP host.
|
show ip rsvp installed
To display Resource Reservation Protocol (RSVP)-related installed filters and corresponding bandwidth information, use the show ip rsvp installed command in user EXEC or privileged EXEC mode.
show ip rsvp installed [vrf {* | vrf-name}] [interface-type interface-number] [detail]
Syntax Description
vrf *
|
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances.
|
vrf vrf-name
|
(Optional) Name of a specified VRF.
|
interface-type
|
(Optional) Type of the interface.
|
interface-number
|
(Optional) Number of the interface.
|
detail
|
(Optional) Displays additional information about interfaces and their reservations.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(15)T
|
The command output was modified to display the resources required for a traffic control state block (TCSB) after compression has been taken into account.
|
12.2(18)SXF2
|
This command was integrated into Cisco IOS Release 12.2(18)SXF2.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SRC
|
The command output was modified to display RSVP aggregation information.
|
15.0(1)M
|
This command was modified. The vrf and * keywords and the vrf-name argument were added.
|
Usage Guidelines
The show ip rsvp installed command displays information about interfaces and their reservations. Enter the optional detail keyword for additional information, including the reservation's traffic parameters, downstream hop, compression, VRFs, and resources used by RSVP to ensure quality of service (QoS) for this reservation.
Examples
show ip rsvp installed Example
The following is sample output from the show ip rsvp installed command:
Router# show ip rsvp installed
RSVP: Ethernet1: has no installed reservations
kbps To From Protocol DPort Sport Weight Conversation
0 192.168.0.0 172.16.2.28 UDP 20 30 128 270
150 192.168.0.1 172.16.2.1 UDP 20 30 128 268
100 192.168.0.1 172.16.1.1 UDP 20 30 128 267
200 192.168.0.1 172.16.1.25 UDP 20 30 256 265
200 192.168.0.2 172.16.1.25 UDP 20 30 128 271
0 192.168.0.2 172.16.2.28 UDP 20 30 128 269
150 192.168.0.2 172.16.2.1 UDP 20 30 128 266
350 192.168.0.3 172.16.0.0 UDP 20 30 128 26
Table 98 describes the significant fields shown in the display.
Table 98 show ip rsvp installed Field Descriptions
Field
|
Description
|
kbps
|
Reserved rate in kilobits per second.
|
To
|
IP address of the source device.
|
From
|
IP address of the destination device.
|
Protocol
|
Protocol code. Code indicates IP protocol such as TCP or User Datagram Protocol (UDP).
|
DPort
|
Destination port number.
|
Sport
|
Source port number.
|
Weight
|
Weight used in Weighted Fair Queueing (WFQ).
|
Conversation
|
WFQ conversation number.
Note If WFQ is not configured on the interface, weight and conversation will be zero.
|
RSVP Compression Method Prediction Examples
The following sample output from the show ip rsvp installed detail command shows the compression parameters, including the compression method, the compression context ID, and the bytes saved per packet, on serial interface 3/0 in effect:
Router# show ip rsvp installed detail
RSVP:Ethernet2/1 has no installed reservations
RSVP:Serial3/0 has the following installed reservations
RSVP Reservation. Destination is 10.1.1.2. Source is 10.1.1.1,
Protocol is UDP, Destination port is 18054, Source port is 19156
Compression:(method rtp, context ID = 1, 37.98 bytes-saved/pkt avg)
Reserved bandwidth:65600 bits/sec, Maximum burst:328 bytes, Peak rate:80K bits/sec
Min Policed Unit:164 bytes, Max Pkt Size:164 bytes
Admitted flowspec (as required if compression were not applied):
Reserved bandwidth:80K bits/sec, Maximum burst:400 bytes, Peak rate:80K bits/sec
Min Policed Unit:200 bytes, Max Pkt Size:200 bytes
Resource provider for this flow:
WFQ on FR PVC dlci 101 on Se3/0: PRIORITY queue 24. Weight:0, BW 66 kbps
Conversation supports 1 reservations [0x1000405]
Data given reserved service:3963 packets (642085 bytes)
Data given best-effort service:0 packets (0 bytes)
Reserved traffic classified for 80 seconds
Long-term average bitrate (bits/sec):64901 reserved, 0 best-effort
Policy:INSTALL. Policy source(s):Default
The following sample output from the show ip rsvp installed detail command shows that compression is not predicted on the serial3/0 interface because no compression context IDs are available:
Router# show ip rsvp installed detail
RSVP:Ethernet2/1 has no installed reservations
RSVP:Serial3/0 has the following installed reservations
RSVP Reservation. Destination is 10.1.1.2. Source is 10.1.1.1,
Protocol is UDP, Destination port is 18116, Source port is 16594
Compression:(rtp compression not predicted:no contexts available)
Reserved bandwidth:80K bits/sec, Maximum burst:400 bytes, Peak rate:80K bits/sec
Min Policed Unit:200 bytes, Max Pkt Size:200 bytes
Resource provider for this flow:
WFQ on FR PVC dlci 101 on Se3/0: PRIORITY queue 24. Weight:0, BW 80 kbps
Conversation supports 1 reservations [0x2000420]
Data given reserved service:11306 packets (2261200 bytes)
Data given best-effort service:0 packets (0 bytes)
Reserved traffic classified for 226 seconds
Long-term average bitrate (bits/sec):79951 reserved, 0 best-effort
Policy:INSTALL. Policy source(s):Default
Note When no compression context IDs are available, use the ip rtp compression-connections number command to increase the pool of compression context IDs.
RSVP Aggregation Example
The following is sample output from the show ip rsvp installed command when RSVP aggregation is configured:
Router# show ip rsvp installed
RSVP: Ethernet0/0 has no installed reservations
BPS To From Protoc DPort Sport
300K 192.168.50.1 192.168.40.1 0 46 0
RSVP: RSVP 3175 AggResv 192.168.40.1->192.168.50.1_ef(46)
BPS To From Protoc DPort Sport
80K 192.168.5.1 192.168.2.1 TCP 222 222
80K 192.168.6.1 192.168.2.1 TCP 223 223
Table 99 describes the significant fields shown in the display.
Table 99 show ip rsvp installed Field Descriptions with RSVP Aggregation
Field
|
Description
|
RSVP
|
Reservation information for a specified interface.
|
BPS
|
Reserved rate in bits per second (BPS).
|
To
|
IP address of the source device.
|
From
|
IP address of the destination device.
|
Protoc
|
Protocol code.
•Code indicates IP protocol such as TCP or User Datagram Protocol (UDP) for end-to-end (E2E) reservations.
•Code is 0 for aggregate reservations.
|
DPort
|
Destination port number.
•Number indicates protocol destination port for E2E reservations.
•Number indicates differentiated services code point (DSCP) for aggregate reservations.
|
Sport
|
Source port number.
•Number indicates protocol source port for E2E reservations.
•Number is 0 for aggregate reservations.
|
RSVP
|
Individual E2E reservations mapped onto an aggregate. Information includes the following:
•IP address of the aggregate source.
•IP address of the aggregate destination.
•Differentiated services code point (DSCP) value.
|
Detailed RSVP Aggregation Example
The following is sample output from the show ip rsvp installed detail command when RSVP aggregation is configured and one E2E reservation that is mapped across an aggregate reservation as seen at the aggregator exists:
Router# show ip rsvp installed detail
RSVP: Ethernet0/0 has no installed reservations
RSVP: Serial1/0 has the following installed reservations
RSVP Reservation. Destination is 192.168.50.1. Source is 192.168.40.1,
Protocol is 0 , Destination port is 46, Source port is 0
Traffic Control ID handle: 35000403
Created: 20:27:14 EST Thu Nov 29 2007
Reserved bandwidth: 300K bits/sec, Maximum burst: 300K bytes, Peak rate: 300K bits/sec
Min Policed Unit: 20 bytes, Max Pkt Size: 0 bytes
Resource provider for this flow: None
Conversation supports 1 reservations [0x3000408]
Data given reserved service: 0 packets (0 bytes)
Data given best-effort service: 0 packets (0 bytes)
Reserved traffic classified for 24558 seconds
Long-term average bitrate (bits/sec): 0 reserved, 0 best-effort
Policy: INSTALL. Policy source(s): Default
RSVP: RSVP 3175 AggResv 192.168.40.1->192.168.50.1_ef(46) has the following installed
reservations
RSVP Reservation. Destination is 192.168.5.1. Source is 192.168.2.1,
Protocol is TCP, Destination port is 222, Source port is 222
Traffic Control ID handle: 0500040B
Created: 20:27:14 EST Thu Nov 29 2007
Reserved bandwidth: 80K bits/sec, Maximum burst: 5K bytes, Peak rate: 80K bits/sec
Min Policed Unit: 0 bytes, Max Pkt Size: 0 bytes
Resource provider for this flow:
Conversation supports 1 reservations [0x600040A]
Data given reserved service: 0 packets (0 bytes)
Data given best-effort service: 0 packets (0 bytes)
Reserved traffic classified for 24558 seconds
Long-term average bitrate (bits/sec): 0 reserved, 0 best-effort
Policy: INSTALL. Policy source(s):
Table 100 describes the significant fields shown in the display.
Table 100 show ip rsvp installed detail Field Descriptions with RSVP Aggregation
Field
|
Description
|
RSVP
|
Reservation information for a specified interface.
|
RSVP Reservation
|
Reservation information for the serial 1/0 interface that includes the following:
•Destination IP address.
–Deaggregator for aggregate reservations.
•Source IP address.
–Aggregator for aggregate reservations.
•Protocol used.
–0 for aggregate reservations.
–TCP/UDP or protocol for E2E reservations.
•Destination port.
–Differentiated services code (DSCP) for aggregate reservations.
–Protocol port number for E2E reservations.
•Source port.
–0 for aggregate reservations.
–Protocol port number for E2E reservations.
•Traffic control identifier assigned by RSVP for bookkeeping purposes.
•Creation date.
•Flowspec information that includes bandwidth, maximum burst, peak rate, policed unit size, and maximum packet size.
•Resource provider information.
–None for aggregate reservations.
–QoS bandwidth manager (BM) for E2E reservations.
•Type of service provided—reserved and best effort (always 0 packets in an RSVP/DiffServ node).
•Length of time traffic is classified.
–Bitrate (always 0 on an RSVP/DiffServ node)
•Policies.
|
RSVP
|
Aggregate information that includes the following:
•IP address of the aggregate source.
•IP address of the aggregate destination.
•DSCP.
Note The remaining fields describe the aggregate's E2E reservations with values explained in preceding fields.
|
VRF Example
The following is sample output when a specific VRF is configured:
Router# show ip rsvp installed vrf myvrf detail
RSVP: FastEthernet2/0 has the following installed reservations
RSVP Reservation. Destination is 10.10.10.10. Source is 10.10.10.12,
Protocol is UDP, Destination port is 10, Source port is 10
Traffic Control ID handle: C8000407
Created: 22:51:26 UTC Sun Feb 17 2008
Reserved bandwidth: 10K bits/sec, Maximum burst: 10K bytes, Peak rate: 10K bits/sec
Min Policed Unit: 0 bytes, Max Pkt Size: 0 bytes
Resource provider for this flow: None
Conversation supports 1 reservations [0xBF000406]
Data given reserved service: 0 packets (0 bytes)
Data given best-effort service: 0 packets (0 bytes)
Reserved traffic classified for 12783 seconds
Long-term average bitrate (bits/sec): 0 reserved, 0 best-effort
Policy: INSTALL. Policy source(s): Default
Table 101 describes the significant fields shown in the display.
Table 101 show ip rsvp installed detail Field Descriptions with VRFs
Field
|
Description
|
RSVP
|
Reservation information for a specified interface.
|
RSVP Reservation
|
Reservation information for the serial 1/0 interface that includes the following:
•Destination IP address.
–Deaggregator for aggregate reservations.
•Source IP address.
–Aggregator for aggregate reservations.
•Protocol used.
–0 for aggregate reservations.
–TCP/UDP or protocol for E2E reservations.
•Destination port.
–Differentiated services code (DSCP) for aggregate reservations.
–Protocol port number for E2E reservations.
•Source port.
–0 for aggregate reservations.
–Protocol port number for E2E reservations.
•Traffic control identifier assigned by RSVP for bookkeeping purposes.
•Creation date.
•Flowspec information that includes bandwidth, maximum burst, peak rate, policed unit size, and maximum packet size.
•Resource provider information.
–None for aggregate reservations.
–QoS bandwidth manager (BM) for E2E reservations.
•Type of service provided—reserved and best effort (always 0 packets in an RSVP/DiffServ node).
•Length of time traffic is classified.
–Bitrate (always 0 on an RSVP/DiffServ node)
•Policies.
|
RSVP
|
Aggregate information that includes the following:
•IP address of the aggregate source.
•IP address of the aggregate destination.
•DSCP.
Note The remaining fields describe the aggregate's E2E reservations with values explained in preceding fields.
|
VRF
|
Name of the VRF.
|
Related Commands
Command
|
Description
|
ip rtp compression-connections
|
Specifies the total number of RTP header compression connections that can exist on an interface.
|
show ip rsvp interface
|
Displays RSVP-related information.
|
show queueing interface
|
Displays interface queueing statistics for dataplane information.
|
show ip rsvp interface
To display information related to Resource Reservation Protocol (RSVP), use the show ip rsvp interface command in user EXEC or privileged EXEC mode.
show ip rsvp interface [vrf {* | vrf-name}] [detail] [interface-type interface-number]
Syntax Description
vrf *
|
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances.
|
vrf vrf-name
|
(Optional) Name of a specified VRF.
|
detail
|
(Optional) Displays additional information about interfaces.
|
interface-type
|
(Optional) Type of the interface.
|
interface-number
|
(Optional) Number of the interface.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(2)T
|
The optional detail keyword was added.
|
12.2(4)T
|
This command was implemented on the Cisco 7500 series and the ATM permanent virtual circuit (PVC) interface.
|
12.0(22)S
|
The command output was modified to display hello message information.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(13)T
|
The following modifications were made to this command:
•Rate-limiting and refresh-reduction information was added to the output display.
•RSVP global settings display when no keywords or arguments are entered.
|
12.2(15)T
|
The following modifications were made to this command:
•The effects of compression on admission control and the RSVP bandwidth limit counter were added to the display.
•Cryptographic authentication parameters were added to the display.
|
12.2(18)SFX2
|
This command was integrated into Cisco IOS Release 12.2(18)SFX2.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SRB
|
The command output was modified to display fast local repair (FLR) information.
|
12.2(33)SRC
|
The command output was modified to display RSVP aggregation information.
|
12.4(20)T
|
The command output was modified to display the RSVP source address configured on a specified interface.
|
15.0(1)M
|
This command was modified. The vrf and * keywords and the vrf-name argument were added.
|
Usage Guidelines
Use the show ip rsvp interface command to display information about interfaces on which RSVP is enabled, including the current allocation budget and maximum available bandwidth. Enter the optional detail keyword for additional information, including bandwidth and signaling parameters and blockade state.
Use the show ip rsvp interface detail command to display information about the RSVP parameters associated with an interface. These parameters include the following:
•Total RSVP bandwidth.
•RSVP bandwidth allocated to existing flows.
•Maximum RSVP bandwidth that can be allocated to a single flow.
•The type of admission control supported (header compression methods).
•The compression methods supported by RSVP compression prediction.
•RSVP aggregation.
•The RSVP source address.
•VRFs.
Examples
This section provides sample output from typical show ip rsvp interface commands. Depending upon the interface or platform in use and the options enabled, the output you see may vary slightly from the ones shown below.
•RSVP Interface Information Example
•RSVP Detailed Information Example
•RSVP Compression Method Prediction Example
•RSVP Cryptographic Authentication Example
•RSVP FLR Example
•RSVP Aggregation Example
•RSVP Source Address Example
•RSVP VRF Example
RSVP Interface Information Example
The following sample output from the show ip rsvp interface command shows information for each interface on which RSVP is enabled:
Router# show ip rsvp interface
interface allocated i/f max flow max sub max
Table 102 describes the fields shown in the display.
Table 102 show ip rsvp interface Field Descriptions
Field
|
Description
|
interface
|
Interface name.
|
allocated
|
Current allocation budget.
|
i/f max
|
Maximum allocatable bandwidth.
|
flow max
|
Largest single flow allocatable on this interface.
|
sub max
|
Largest subpool value allowed on this interface.
|
RSVP Detailed Information Example
The following sample output from the show ip rsvp interface detail command shows detailed RSVP information for each interface on which RSVP is enabled:
Router# show ip rsvp interface detail
Curr allocated:0 bits/sec
Max. allowed (total):200M bits/sec
Max. allowed (per flow):200M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/secMax. allowed for LSP tunnels using sub-pools:0
bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):200M bits/sec
Max. allowed (per flow):200M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Table 103 describes the significant fields shown in the detailed display for PO interface 0/0. The fields for the other interfaces are similar.
Table 103 show ip rsvp interface detail Field Descriptions—Detailed RSVP Information Example
Field
|
Description
|
PO0/0
|
Interface name.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for label switched path (LSP) tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Signalling
|
The RSVP signalling parameters in effect are as follows:
•DSCP value used in RSVP msgs—Differentiated services code point (DSCP) used in RSVP messages.
•Number of refresh intervals to enforce blockade state—How long, in milliseconds, before the blockade takes effect.
•Number of missed refresh messages—How many refresh messages until the router state expires.
•Refresh interval—How long, in milliseconds, until a refresh message is sent.
|
RSVP Compression Method Prediction Example
The following sample output from the show ip rsvp interface detail command shows the RSVP compression method prediction configuration for each interface on which RSVP is configured:
Router# show ip rsvp interface detail
Curr allocated:0 bits/sec
Max. allowed (total):1158K bits/sec
Max. allowed (per flow):128K bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
Header Compression methods supported:
rtp (36 bytes-saved), udp (20 bytes-saved)
Using IP encap:0. Using UDP encap:0
Refresh reduction:disabled
Curr allocated:0 bits/sec
Max. allowed (total):1158K bits/sec
Max. allowed (per flow):128K bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
Header Compression methods supported:
rtp (36 bytes-saved), udp (20 bytes-saved)
Using IP encap:1. Using UDP encap:0
Refresh reduction:disabled
Table 104 describes the significant fields shown in the display for Ethernet interface 2/1. The fields for serial interface 3/0 are similar.
Table 104 show ip rsvp interface detail Field Descriptions—RSVP Compression Method Prediction Example
Field
|
Description
|
Et2/1
|
Interface name and number.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for LSP tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Admission Control
|
The type of admission control in effect is as follows:
•Header Compression methods supported:
–Real-Time Transport Protocol (RTP) or User Data Protocol (UDP) compression schemes and the number of bytes saved per packet.
|
Neighbors
|
The number of neighbors using IP and UDP encapsulation.
|
Signalling
|
The type of signaling in effect; Refresh reduction is either enabled (active) or disabled (inactive).
|
Authentication
|
Authentication is either enabled (active) or disabled (inactive).
|
RSVP Cryptographic Authentication Example
The following sample output from the show ip rsvp interface detail command displays detailed information, including the cryptographic authentication parameters, for all RSVP-configured interfaces on the router:
Router# show ip rsvp interface detail
Curr allocated: 0 bits/sec
Max. allowed (total): 7500K bits/sec
Max. allowed (per flow): 7500K bits/sec
Max. allowed for LSP tunnels using sub-pools: 0 bits/sec
Set aside by policy (total):0 bits/sec
Using IP encap: 0. Using UDP encap: 0
Refresh reduction: disabled
Table 105 describes the significant fields shown in the display.
Table 105 show ip rsvp interface detail Field Descriptions—Cryptographic Authentication
Example
Field
|
Description
|
Et0/0
|
Interface name and number.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for LSP tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Neighbors
|
The number of neighbors using IP and UDP encapsulation.
|
Signalling
|
The type of signaling in effect; Refresh reduction is either enabled (active) or disabled (inactive).
|
Authentication
|
Authentication is either enabled (active) or disabled (inactive). The parameters are as follows:
•Key—The key (string) for the RSVP authentication algorithm displayed in clear text (for example, 11223344) or <encrypted>.
•Type—The algorithm to generate cryptographic signatures in RSVP messages; possible values are md5 and sha-1.
•Window size—Maximum number of RSVP authenticated messages that can be received out of order.
•Challenge—The challenge-response handshake performed with any new RSVP neighbors that are discovered on a network; possible values are enabled (active) or disabled (inactive).
|
RSVP FLR Example
The following sample output from the show ip rsvp interface detail command displays detailed information for the Ethernet 1/0 interface on which FLR is enabled:
Router# show ip rsvp interface detail ethernet1/0
Curr allocated: 9K bits/sec
Max. allowed (total): 300K bits/sec
Max. allowed (per flow): 300K bits/sec
Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec
Set aside by policy (total): 0 bits/sec
RSVP Data Packet Classification is ON via CEF callbacks
DSCP value used in RSVP msgs: 0x30
Number of refresh intervals to enforce blockade state: 4
FLR Wait Time (IPv4 flows):
Repair is delayed by 500 msec.
Table 106 describes the significant fields shown in the display.
Table 106 show ip rsvp interface detail Field Descriptions—FLR Example
Field
|
Description
|
Et1/0
|
Interface name and number.
|
RSVP
|
Enabled means active; disabled means inactive.
|
Interface State
|
Up means that the interface is configured; down means that the interface is not configured.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for LSP tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Traffic Control
|
RSVP Data Packet Classification is ON via CEF callbacks means that RSVP is not processing every packet; therefore, excess overhead is avoided and network performance is improved.
|
Signalling
|
The signaling parameters in effect are as follows:
•DSCP value used in RSVP msgs—Differentiated services code point (DSCP) value used in RSVP messages.
•Number of refresh intervals to enforce blockade state—How long, in milliseconds, before the blockade takes effect.
|
FLR Wait Time (IPv4 flows)
|
Repair is delayed by 500 msec represents the amount of time, in milliseconds, before the FLR procedure begins on the specified interface.
|
Authentication
|
Authentication is either enabled (active) or disabled (inactive). The parameters are as follows:
•Key chain—The key (string) for the RSVP authentication algorithm displayed in clear text (for example, 11223344) or <encrypted>.
•Type—The algorithm to generate cryptographic signatures in RSVP messages; possible values are md5 and sha-1.
•Window size—Maximum number of RSVP authenticated messages that can be received out of order.
•Challenge—The challenge-response handshake performed with any new RSVP neighbors that are discovered on a network; possible values are enabled (active) or disabled (inactive).
|
Hello Extension
|
Enables RSVP nodes to detect when a neighboring node is not reachable. The state is either enabled (active) or disabled (inactive).
|
RSVP Aggregation Example
The following sample output from the show ip rsvp interface detail command displays the aggregation parameters for each interface on which RSVP is configured:
Router# show ip rsvp interface detail
Curr allocated: 300K bits/sec
Max. allowed (total): 400K bits/sec
Max. allowed (per flow): 400K bits/sec
Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec
Set aside by policy (total): 0 bits/sec
RSVP Data Packet Classification is OFF
RSVP resource provider is: none
DSCP value used in RSVP msgs: 0x3F
Number of refresh intervals to enforce blockade state: 4
Backup Path: Not Configured
RFC 3175 Aggregation: Enabled
Table 107 describes the significant fields shown in the display.
Table 107 show ip rsvp interface detail Field Descriptions—RSVP Aggregation Example
Field
|
Description
|
Se1/0
|
Interface name and number.
|
RSVP
|
Enabled means active; disabled means inactive.
|
Interface State
|
Up means that the interface is configured; down means that the interface is not configured.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for LSP tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Traffic Control
|
RSVP Data Packet Classification Is OFF—Disabling data packet classification instructs RSVP not to process every packet, but to perform admission control only.
RSVP Resource Provider is None—Setting the resource provider to none instructs RSVP to not associate any resources, such as weighted fair queueing (WFQ) queues or bandwidth, with a reservation.
These settings are necessary because RSVP aggregation uses RSVP Scalability Enhancements for control plane aggregation only. Traffic control is performed by Class-Based Weighted Fair Queuing (CBWFQ).
|
Signalling
|
The signaling parameters in effect are as follows:
•DSCP value used in RSVP msgs—Differentiated services code point (DSCP) value used in RSVP messages IP headers.
•Number of refresh intervals to enforce blockade state—How long, in milliseconds, before the blockade takes effect.
|
Authentication
|
Authentication is either enabled (active) or disabled (inactive). The parameters are as follows:
•Key chain—The key (string) for the RSVP authentication algorithm displayed in clear text (for example, 11223344) or <encrypted>.
•Type—The algorithm to generate cryptographic signatures in RSVP messages; possible values are md5 and sha-1.
•Window size—Maximum number of RSVP authenticated messages that can be received out of order.
•Challenge—The challenge-response handshake performed with any new RSVP neighbors that are discovered on a network; possible values are enabled (active) or disabled (inactive).
|
FRR Extension
|
Fast Reroute backup path is configured or not configured.
|
BFD Extension
|
Bidirectional Forwarding Detection; values are the following:
•State—Enabled (active) or disabled (inactive).
•Interval—Configured with a value or Not Configured.
|
RSVP Hello Extension
|
Enables RSVP nodes to detect when a neighboring node is not reachable. The state is either enabled (active) or disabled (inactive).
|
RFC 3175 Aggregation
|
The state of aggregation as defined in RFC 3175, Aggregation of RSVP for IPv4 and IPv6 Reservations; values are the following:
•Enabled—Active.
•Disabled—Inactive.
Role
•Interior—Interface is facing an aggregation region.
•Exterior—Interface is facing a classic RSVP region.
|
RSVP Source Address Example
The following sample output from the show ip rsvp interface detail ethernet1/0 command displays the source address configured for that interface:
Router# show ip rsvp interface detail ethernet1/0
Curr allocated: 0 bits/sec
Max. allowed (total): 7500K bits/sec
Max. allowed (per flow): 7500K bits/sec
Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec
Set aside by policy (total): 0 bits/sec
RSVP Data Packet Classification is ON via CEF callbacks
DSCP value used in RSVP msgs: 0x3F
Number of refresh intervals to enforce blockade state: 4
Ip address used in RSVP objects: 10.1.3.13 <----------source address for Ethernet 0/1
Table 108 describes the significant fields shown in the display.
Table 108 show ip rsvp interface detail Field Descriptions—RSVP Source Address Example
Field
|
Description
|
Et1/0
|
Interface name and number.
|
RSVP
|
Enabled means active; disabled means inactive.
|
Interface State
|
Up means that the interface is configured; down means that the interface is not configured.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for LSP tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Traffic Control
|
RSVP Data Packet Classification is ON via CEF callbacks means that RSVP is not processing every packet; therefore, excess overhead is avoided and network performance is improved.
|
Signalling
|
The signaling parameters in effect are as follows:
•DSCP value used in RSVP msgs—Differentiated services code point (DSCP) value used in IP headers of RSVP messages.
•Number of refresh intervals to enforce blockade state—How long, in milliseconds, before the blockade takes effect.
•IP address used in RSVP objects—The RSVP source address for the specified interface.
|
Authentication
|
Authentication is either enabled (active) or disabled (inactive). The parameters are as follows:
•Key chain—The key (string) for the RSVP authentication algorithm displayed in clear text (for example, 11223344) or <encrypted>.
•Type—The algorithm to generate cryptographic signatures in RSVP messages; possible values are md5 and sha-1.
•Window size—Maximum number of RSVP authenticated messages that can be received out of order.
•Challenge—The challenge-response handshake performed with any new RSVP neighbors that are discovered on a network; possible values are enabled (active) or disabled (inactive).
|
Hello Extension
|
Enables RSVP nodes to detect when a neighboring node is not reachable. The state is either enabled (active) or disabled (inactive).
|
RSVP VRF Example
The following sample output from the show ip rsvp interface vrf myvrf detail command displays information for all the interfaces associated with the VRF named myvrf:
Router# show ip rsvp interface vrf myvrf detail
Curr allocated: 300K bits/sec
Max. allowed (total): 400K bits/sec
Max. allowed (per flow): 400K bits/sec
Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec
Set aside by policy (total): 0 bits/sec
RSVP Data Packet Classification is OFF
RSVP resource provider is: none
DSCP value used in RSVP msgs: 0x3F
Number of refresh intervals to enforce blockade state: 4
Backup Path: Not Configured
RFC 3175 Aggregation: Enabled
Table 109 describes the significant fields shown in the display.
Table 109 show ip rsvp interface detail Field Descriptions—RSVP VRF Example
Field
|
Description
|
Se1/0
|
Interface name and number.
|
RSVP
|
Enabled means active; disabled means inactive.
|
Interface State
|
Up means that the interface is configured; down means that the interface is not configured.
|
Bandwidth
|
The RSVP bandwidth parameters in effect are as follows:
•Curr allocated—Amount of bandwidth currently allocated, in bits per second.
•Max. allowed (total)—Maximum amount of bandwidth allowed, in bits per second.
•Max. allowed (per flow)—Maximum amount of bandwidth allowed per flow, in bits per second.
•Max. allowed for LSP tunnels using sub-pools—Maximum amount of bandwidth allowed for LSP tunnels, in bits per second.
•Set aside by policy (total)—The amount of bandwidth set aside by the local policy, in bits per second.
|
Traffic Control
|
RSVP Data Packet Classification Is OFF—Disabling data packet classification instructs RSVP not to process every packet, but to perform admission control only.
RSVP Resource Provider is None—Setting the resource provider to none instructs RSVP to not associate any resources, such as weighted fair queueing (WFQ) queues or bandwidth, with a reservation.
These settings are necessary because RSVP aggregation uses RSVP Scalability Enhancements for control plane aggregation only. Traffic control is performed by Class-Based Weighted Fair Queuing (CBWFQ).
|
Signalling
|
The signaling parameters in effect are as follows:
•DSCP value used in RSVP msgs—Differentiated services code point (DSCP) value used in RSVP messages IP headers.
•Number of refresh intervals to enforce blockade state—How long, in milliseconds, before the blockade takes effect.
|
Authentication
|
Authentication is either enabled (active) or disabled (inactive). The parameters are as follows:
•Key chain—The key (string) for the RSVP authentication algorithm displayed in clear text (for example, 11223344) or <encrypted>.
•Type—The algorithm to generate cryptographic signatures in RSVP messages; possible values are md5 and sha-1.
•Window size—Maximum number of RSVP authenticated messages that can be received out of order.
•Challenge—The challenge-response handshake performed with any new RSVP neighbors that are discovered on a network; possible values are enabled (active) or disabled (inactive).
|
FRR Extension
|
Fast Reroute backup path is configured or not configured.
|
BFD Extension
|
Bidirectional Forwarding Detection; values are the following:
•State—Enabled (active) or disabled (inactive).
•Interval—Configured with a value or Not Configured.
|
RSVP Hello Extension
|
Enables RSVP nodes to detect when a neighboring node is not reachable. The state is either enabled (active) or disabled (inactive).
|
RFC 3175 Aggregation
|
The state of aggregation as defined in RFC 3175, Aggregation of RSVP for IPv4 and IPv6 Reservations; values are the following:
•Enabled—Active.
•Disabled—Inactive.
Role
•Interior—Interface is facing an aggregation region.
•Exterior—Interface is facing a classic RSVP region.
|
VRF
|
Name of the VRF.
|
Related Commands
Command
|
Description
|
show ip rsvp installed
|
Displays RSVP-related installed filters and corresponding bandwidth information.
|
show ip rsvp neighbor
|
Displays current RSVP neighbors.
|
show ip rsvp interface detail
To display the interface configuration for hello, use the show ip rsvp interface detail command in user EXEC or privileged EXEC mode.
show ip rsvp interface detail [interface]
Syntax Description
interface
|
(Optional) Name of the Interface for which you want to show the hello configuration.
|
Command Default
The interface configuration for hello is not displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(18)SXD1
|
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.2(33)SRC
|
This command was integrated into Cisco IOS Release 12.2(33)SRC.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Examples
The following is sample output from the show ip rsvp interface detail command:
Router# show ip rsvp interface detail GigabitEthernet 9/47
Curr allocated: 0 bits/sec
Max. allowed (total): 0 bits/sec
Max. allowed (per flow): 0 bits/sec
Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec
Set aside by policy (total): 0 bits/sec
DSCP value used in RSVP msgs: 0x3F
Number of refresh intervals to enforce blockade state: 4
Backup Path: Configured (or "Not Configured")
Refresh Interval: FRR: 200 , Reroute: 2000
Missed Acks: FRR: 4 , Reroute: 4
DSCP in HELLOs: FRR: 0x30 , Reroute: 0x30
Table 110 describes the significant fields shown in the display.
Table 110 show ip rsvp interface detail Field Descriptions
Field
|
Description
|
RSVP
|
Status of the Resource Reservation Protocol (RSVP) protocol (Enabled or Disabled).
|
Interface State
|
Status of the interface (Up or Down).
|
Curr allocated
|
Amount of bandwidth (in bits per second [bps]) currently allocated.
|
Max. allowed (total)
|
Total maximum amount of bandwidth (in bps) allowed.
|
Max. allowed (per flow)
|
Maximum amount of bandwidth (in bps) allowed per flow.
|
Max. allowed for LSP tunnels using sub-pools
|
Maximum amount of bandwidth permitted for label-switched path (LSP) tunnels that obtain their bandwidth from subpools.
|
DSCP value used in RSVP msgs
|
The differentiated services code point (DSCP) value that is in RSVP messages.
|
BFD Extension State
|
State (Enabled or Disabled) of Bidirectional Forwarding Detection (BFD) extension.
|
RSVP Hello Extension State
|
State (Enabled or Disabled) of hello extension.
|
Missed Acks
|
Number of sequential acknowledgments that the node did not receive.
|
DSCP in HELLOs
|
The DSCP value that is in hello messages.
|
Related Commands
Command
|
Description
|
ip rsvp signalling hello (interface)
|
Enables hello on an interface where you need Fast Reroute protection.
|
ip rsvp signalling hello dscp
|
Sets the DSCP value that is in the IP header of the hello message sent out from an interface.
|
ip rsvp signalling hello refresh interval
|
Configures the hello request interval.
|
show ip rsvp listeners
To display the Resource Reservation Protocol (RSVP) listeners for a specified port or protocol, use the show ip rsvp listeners command in user EXEC or privileged mode.
show ip rsvp listeners [ip-address | any | vrf {* | vrf-name}] [udp | tcp | any | protocol] [dst-port
| any]
Syntax Description
ip-address
|
(Optional) A particular IP address for an RSVP message.
|
any
|
(Optional) Any IP address destination for an RSVP message.
|
vrf *
|
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances.
|
vrf vrf-name
|
(Optional) Name of a specified VRF.
|
udp
|
(Optional) User Datagram Protocol (UDP) to be used on the receiving interface and the UDP source port number.
|
tcp
|
(Optional) Transmission Control Protocol (TCP) to be used on the receiving interface and the TCP source port number.
|
any
|
(Optional) Any protocol to be used on the receiving interface and the UDP or TCP source port number.
|
protocol
|
(Optional) The protocol to be used on the receiving interface and the UDP or TCP source port number.
Note If you select protocol, the range is 0 to 255 and the protocol is IP.
|
dst-port
|
(Optional) A particular destination port from 0 to 65535 for an RSVP message.
|
any
|
(Optional) Any destination for an RSVP message.
|
Command Default
If you enter the show ip rsvp listeners command without a keyword or an argument, the command displays all the listeners that were sent and received for each interface on which RSVP is configured.
Command Modes
User EXEC (<)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
15.0(1)M
|
This command was modified. The vrf and * keywords and the vrf-name argument were added.
|
Usage Guidelines
Use the show ip rsvp listeners command to display the number of listeners that were sent and received for each interface on which RSVP is configured.
Examples
The following example shows the listeners for the VRF named myvrf1:
Router# show ip rsvp listeners vrf myvrf1
To Protocol DPort Description Action OutIf
10.0.2.1 any any RSVP Proxy reply
Table 111 describes the fields shown in the display.
Table 111 show ip rsvp listeners Command Field Descriptions
Field
|
Description
|
VRF
|
Name of the VRF for which the listeners are displayed.
|
To
|
IP address of the receiving interface.
|
Protocol
|
Protocol used.
|
DPort
|
Destination port on the receiving router.
|
Description
|
Cisco IOS component that requested RSVP to do the listening; for example, RSVP proxy and label-switched path (LSP) tunnel signaling.
|
Action
|
Action taken when a flow arrives at its destination. The choices include:
•Announce—The arrival of the flow is announced.
•Reply—After the flow arrives at its destination, the sender receives a reply.
|
OutIf
|
Outbound interface on the receiving router.
Note If this field is blank, it means that the listener was configured in global configuration mode and is not attached to any particular interface. If an interface name appears, then the listener was configured in interface configuration mode and is attached to that interface.
|
Related Commands
Command
|
Description
|
ip rsvp listener
|
Configures an RSVP router to listen for PATH messages.
|
show ip rsvp neighbor
To display current Resource Reservation Protocol (RSVP) neighbors, use the show ip rsvp neighbor command in user EXEC or privileged EXEC mode.
show ip rsvp neighbor [detail | inactive [detail] | vrf {* | vrf-name}]
Syntax Description
detail
|
(Optional) Displays additional information about RSVP neighbors.
|
inactive
|
(Optional) Displays RSVP neighbors that have had no activity for more than an hour.
|
detail
|
(Optional) Displays additional information about the inactive RSVP neighbors.
|
vrf *
|
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances.
|
vrf vrf-name
|
(Optional) Name of a specified VRF.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(13)T
|
The interface-type interface-number arguments were deleted. The detail keyword was added to the command, and rate-limiting and refresh-reduction information was added to the output.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
15.0(1)M
|
This command was modified. The vrf and * keywords and the vrf-name argument were added.
|
Usage Guidelines
Use the show ip rsvp neighbor command to show the IP addresses for the current RSVP neighbors. Enter the detail keyword to display rate-limiting, refresh-reduction, and VRF information for the RSVP neighbors.
Examples
RSVP Neighbors Example
The following command shows the current RSVP neighbors:
Router# show ip rsvp neighbor
Table 112 describes the fields shown in the display.
Table 112 show ip rsvp neighbor Field Descriptions
Field
|
Description
|
10.0.0.1
|
IP address of neighboring router.
|
RSVP
|
Type of encapsulation being used.
|
Rate-Limiting and Refresh-Reduction Parameters Example
The following command shows the rate-limiting and refresh-reduction parameters for the current RSVP neighbors:
Router# show ip rsvp neighbor detail
Highest rcvd message id:1059
Last rcvd message:00:00:04
Highest rcvd message id:945
Last rcvd message:00:00:05
Table 113 describes the fields shown in the display.
Table 113 show ip rsvp neighbor detail Field Descriptions
Field
|
Description
|
Neighbor
|
IP address of the neighboring router.
|
Encapsulation
|
Type of encapsulation being used.
Note Unknown displays if an RSVP message has been sent to an IP address, but no RSVP message has been received from that IP address. This is not an error condition; it simply means that the router does not yet know what RSVP encapsulation (IP or User Data Protocol (UDP)) is preferred and should be used to send RSVP messages.
|
Rate-Limiting
|
The rate-limiting parameters in effect are as follows:
•Dropped messages = number of messages dropped by the neighbor.
|
Refresh Reduction
|
The refresh-reduction parameters in effect are as follows:
•Remote epoch = the RSVP message number space identifier (ID); randomly generated whenever the node reboots or the RSVP process restarts.
•Out of order messages = messages that were dropped because they are out of sequential order.
•Retransmitted messages = number of messages retransmitted to the neighbor.
•Highest rcvd message id = highest message ID number sent by the neighbor.
•Last rcvd message= time delta in hours, minutes, and seconds when last message was received by the neighbor.
|
VRF Example
The following command shows the VRF named myvrf:
Router# show ip rsvp neighbor vrf myvrf
Neighbor Encapsulation Time since msg rcvd/sent
10.10.15.3 Raw IP 00:00:14 00:00:06
10.10.16.2 Raw IP 00:00:29 00:00:15
Table 114 describes the fields shown in the display.
Table 114 show ip rsvp neighbor vrf Field Descriptions
Field
|
Description
|
VRF
|
Name of the VRF.
|
Neighbor
|
IP address of neighboring router.
|
Encapsulation
|
Type of encapsulation being used.
|
Time since msg rcvd/sent
|
Time in hh:mm:ss since a message has been received by or sent to the neighbor.
|
Related Commands
Command
|
Description
|
show ip rsvp interface
|
Displays RSVP-related interface information.
|
show ip rsvp policy
To display the policies currently configured, use the show ip rsvp policy command in user EXEC or privileged mode.
show ip rsvp policy [cops | local [acl]]
Syntax Description
cops | local
|
(Optional) Displays either the configured Common Open Policy Service (COPS) servers or the local policies.
|
acl
|
(Optional) Displays the access control lists (ACLs) whose sessions are governed by COPS servers or the local policies.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.1(1)T
|
This command was introduced as show ip rsvp policy cops.
|
12.2(13)T
|
This command was modified to include the local keyword. This command replaces the show ip rsvp policy cops command.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Use the show ip rsvp policy command to display current local policies, configured COPS servers, default policies, and the preemption parameter (disabled or enabled).
Examples
The following is sample output from the show ip rsvp policy command:
Router# show ip rsvp policy
Path:-- Resv:-- PathErr:-- ResvErr:-- ACL:104
Path:-- Resv:-- PathErr:-- ResvErr:-- ACL:None [Default policy]
Default policy: Accept all
Table 115 describes the fields shown in the display.
Table 115 show ip rsvp policy Command Field Descriptions
Field
|
Description
|
Local policy
|
The local policy currently configured.
A = Accept the message.
F = Forward the message.
Blank (--) means messages of the specified type are neither accepted or forwarded.
|
COPS
|
The COPS servers currently in effect.
|
Generic policy settings
|
Policy settings that are not specific to COPS or the local policy.
Default policy: Accept all means all RSVP messages are accepted and forwarded. Reject all means all RSVP messages are rejected.
Preemption: Disabled means that RSVP should not implement any preemption decisions required by a particular local or remote policy. Enabled means that RSVP should implement any preemption decisions required by a particular local or remote policy.
|
Related Commands
Command
|
Description
|
ip rsvp signalling initial-retransmit-delay
|
Creates a local procedure that determines the use of RSVP resources in a network.
|
show ip rsvp policy cops
The show ip rsvp policy cops command is replaced by the show ip rsvp policy command. See the show ip rsvp policy command for more information.
show ip rsvp policy identity
To display selected Resource Reservation Protocol (RSVP) identities in a router configuration, use the show ip rsvp policy identity command in user EXEC or privileged EXEC mode.
show ip rsvp policy identity [regular-expression]
Syntax Description
regular-expression
|
(Optional) String of text that allows pattern matching on the alias strings of the RSVP identities to be displayed.
|
Command Default
All configured RSVP identities are displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.4(6)T
|
This command was introduced.
|
12.2(33)SRB
|
This command was integrated into Cisco IOS Release 12.2(33)SRB.
|
Usage Guidelines
Use the show ip rsvp policy identity command with the optional regular-expression argument to perform pattern matching on the alias strings of the RSVP identities to be displayed. Use this filtering capability to search for a small subset of RSVP identities in a configuration with a large number of identities.
Omit the regular-expression argument to display all the configured identities.
Examples
In the following example from the show ip rsvp policy identity command, all the configured identities are displayed:
Router# show ip rsvp policy identity
Locator: GUID=www.cisco.com,APP=voice,VER=1.0
Locator: GUID=www.cisco.com,APP=voice,VER=10.0
Locator: GUID=www.cisco.com,APP=voice,VER=100.0
Locator: GUID=www.cisco.com,APP=voice,VER=1000.0
Table 116 describes the significant fields shown in the display.
Table 116 show ip rsvp policy identity Field Descriptions
Field
|
Description
|
Alias
|
Name of the alias string. The string can have as many as 64 printable characters (in the range 0x20 to 0x7E).
The string has no maximum length and must contain printable characters (in the range 0x20 to 0x7E).
Note If you use the " " or ? characters as part of the string itself, you must type the CTRL/V key sequence before entering the embedded " " or ? characters. The alias is never transmitted to other routers.
|
Type
|
Types of identities. RSVP defines two types: application IDs and user IDs. Cisco IOS software currently supports application IDs only.
|
Locator
|
Information used by a router to find the correct policy to apply to RSVP messages that contain application IDs.
|
In the following example from the show ip rsvp policy identity command, all the identities whose aliases contain voice100 display:
Router# show ip rsvp policy identity voice100
Locator: GUID=www.cisco.com,APP=voice,VER=100.0
Locator: GUID=www.cisco.com,APP=voice,VER=1000.0
In the following example from the show ip rsvp policy identity command, all the identities whose aliases contain an exact match on voice100 are displayed:
Router# show ip rsvp policy identity ^voice100$
Locator: GUID=www.cisco.com,APP=voice,VER=100.0
Related Commands
Command
|
Description
|
ip rsvp listener
|
Configures an RSVP router to listen for PATH messages.
|
ip rsvp policy identity
|
Defines RSVP application IDs.
|
ip rsvp policy local
|
Determines how to perform authorization on RSVP requests.
|
ip rsvp reservation
|
Enables a router to simulate receiving RSVP RESV messages.
|
ip rsvp sender
|
Enables a router to simulate receiving RSVP PATH messages.
|
show ip rsvp policy local
To display the local policies that are currently configured, use the show ip rsvp policy local command in user EXEC or privileged EXEC mode.
show ip rsvp policy local [detail] [interface type number] [acl acl | dscp-ip value | default |
identity alias | origin-as as]
Syntax Description
detail
|
(Optional) Displays additional information about the configured local policies including preempt-priority and local-override.
|
interface type number
|
(Optional) Specifies an interface.
|
acl acl
|
(Optional) Specifies an access control list (ACL). Values are 1 to 199.
|
dscp-ip value
|
(Optional) Specifies a differentiated services code point (DSCP) for aggregate reservations. Values can be the following:
•0 to 63—Numerical DSCP values. The default value is 0.
•af11 to af43—Assured forwarding (AF) DSCP values.
•cs1 to cs7—Type of service (ToS) precedence values.
•default—Default DSCP value.
•ef—Expedited forwarding (EF) DSCP values.
|
default
|
(Optional) Displays information about the default policy.
|
identity alias
|
(Optional) Specifies an application identity (ID) alias.
|
origin-as as
|
(Optional) Specifies an autonomous system. Values are 1 to 65535.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
12.0(29)S
|
The origin-as as keyword and argument combination was added, and the acl argument became optional.
|
12.4(6)T
|
The identity alias and the interface type number keyword and argument combinations were added, and the output was modified to include application ID information.
|
12.2(33)SRB
|
This command was integrated into Cisco IOS Release 12.2(33)SRB.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
12.2(33)SRC
|
The dscp-ip value keyword and argument combination was added, and the output was modified to include RSVP aggregation information.
|
Usage Guidelines
Use the show ip rsvp policy local command to display information about the selected local policies that are currently configured. You can use the default keyword and/or the interface type number keyword and argument combination with one or more of the match criteria.
If you omit the acl acl, the origin-as as, the identity alias, or the dscp-ip value keyword and argument combinations, all local policies currently configured appear.
If you use the ACL, the autonomous system, the application-ID, or the DSCP options as match criteria, you can specify only one. However, that parameter can be any ACL, autonomous system, application ID, or DSCP of any local policy that you have created. If you have multiple local policies with a common match criteria, using that parameter displays all local policies that meet the match criteria. On the other hand, if you have created local policies each with multiple ACLs, autonomous systems, application IDs, or DSCPs as the match criteria, you cannot use that parameter to show only a specific policy. You must omit the match criteria and show all the local policies.
Examples
Application IDs Local Policy Example
The following sample output from the show ip rsvp policy local command displays global and per-interface local policies based on RSVP identities (application IDs) that have been configured:
Router# show ip rsvp policy local
Path:AF Resv:AF PathErr:AF ResvErr:AF ACL(s):101
Path:AF Resv:AF PathErr:AF ResvErr:AF AS(es):3
Path:AF Resv:AF PathErr:AF ResvErr:AF ID:voice
Path:AF Resv:AF PathErr:AF ResvErr:AF ID:video
Path:AF Resv:AF PathErr:AF ResvErr:AF ID:voice
Path:AF Resv:AF PathErr:AF ResvErr:AF ID:video
Path:AF Resv:AF PathErr:AF ResvErr:AF ID:conference
Path:AF Resv:AF PathErr:AF ResvErr:AF ID:iptv
Path:-- Resv:-- PathErr:-- ResvErr:-- Default
Default policy: Accept all
Table 117 describes the significant fields shown in the display.
Table 117 show ip rsvp policy local Field Descriptions
Field
|
Description
|
A=Accept
F=Forward
|
State of RSVP messages.
•Accept—Messages being accepted.
•Forward—Messages being forwarded.
|
Global
|
Location of the local policy. Global—Local policy configured for the entire router.
|
Path, Resv, PathErr, ResvErr, ACL(s), AS(es), ID, Default
|
Types of RSVP messages being accepted and forwarded and the match criteria for the local policies configured. Blank (--) means that messages of the specified type are neither accepted nor forwarded.
|
Interface
|
Location of the local policy. Serial2/0/0—Local policy configured for a specific interface on the router.
|
Path, Resv, PathErr, ResvErr, ACL(s), AS(es), ID
|
Types of RSVP messages being accepted and forwarded and the types of local policies configured. Blank (--) means that messages of the specified type are neither accepted nor forwarded.
|
Generic policy settings
|
Policy settings that are not specific to any local or remote policy.
•Default policy: Accept all means that all RSVP messages are accepted and forwarded. Reject all means that all RSVP messages are rejected.
•Preemption: Disabled means that RSVP should not implement any preemption decisions required by a particular local or remote policy. Enabled means that RSVP should implement any preemption decisions required by a particular local or remote policy.
|
DSCP-IP Local Policy Example
The following sample output from the show ip rsvp policy local command displays a global local policy based on a DSCP EF that has been configured:
Router# show ip rsvp policy local dscp-ip ef
Path:AF Resv:AF PathErr:AF ResvErr:AF DSCP(s): ef
Default policy: Accept all
See Table 118 for a description of the preceding fields.
show ip rsvp policy local detail Example
The following sample output from the show ip rsvp policy local detail command shows the location of the local policy (such as whether the policy is configured globally or for a specific interface, and the settings for preemption scope and maximum bandwidth. Preemption priorities and sender and receiver limits also appear even if they are set to their defaults.
Router# show ip rsvp policy local detail
Preemption Scope: Unrestricted.
Local Override: Disabled.
Setup Priority Hold Priority
Group bandwidth (bps): 0 200K
Per-flow b/w (bps): N/A 10M
Preemption Scope: Unrestricted.
Local Override: Disabled.
Setup Priority Hold Priority
Group bandwidth (bps): 100K 200K
Per-flow b/w (bps): N/A 10M
Preemption Scope: Unrestricted.
Local Override: Disabled.
Setup Priority Hold Priority
Group bandwidth (bps): 100K 200K
Per-flow b/w (bps): N/A 10M
Default policy: Accept all
Table 118 describes the significant fields shown in the display.
Table 118 show ip rsvp policy local detail Field Descriptions
Field
|
Description
|
Global
|
Location of the local policy. Global—Local policy configured for the entire router.
|
Policy for ID
|
A global local policy defined for an application ID alias named voice.
|
Preemption Scope
|
Describes which classes of RSVP quality of service (QoS) reservations can be preempted by other classes of RSVP QoS reservations on the same interface.
Unrestricted means that a reservation using an application ID such as voice can preempt any other class of reservation on the same interface as that reservation, even other nonvoice reservations.
|
Local Override
|
Overrides any remote policy by enforcing the local policy in effect.
•Disabled—Not active.
•Enabled—Active.
|
Fast ReRoute
|
State of Fast ReRoute for Multiprotocol Label Switching (MPLS)/Traffic Engineering (TE) label switched paths (LSPs).
•Accept—Messages being accepted.
•Do not accept—Messages requesting Fast Reroute service are not being accepted.
|
Handle
|
Internal database ID assigned to the security association by RSVP for bookkeeping purposes.
|
Accept, Forward
|
State of RSVP messages.
|
Path, Resv, PathError, ResvError
|
Types of RSVP messages being accepted and forwarded.
•Yes—Messages are being accepted and forwarded.
•No—Messages are not being accepted or forwarded.
|
Setup Priority, Hold Priority
|
Preemption priorities. Setup Priority indicates the priority of a reservation when it is initially installed. Hold Priority indicates the priority of a reservation after it has been installed.
N/A means preemption priorities are not configured.
|
TE
|
The preemption priority of TE reservations. Values for Setup Priority and Hold Priority range from 0 to 7 where 0 is considered the highest priority.
|
Non-TE
|
The preemption priority of non-TE reservations. Values for Setup Priority and Hold Priority range from 0 to 65535 where 65535 is considered the highest priority.
|
Current, Limit
|
The present number and the highest number of these parameters allowed.
|
Senders
|
The number of current PATH states accepted and/or approved by this policy.
|
Receivers
|
The number of current RESV states accepted by this policy.
|
Conversations
|
The number of active bandwidth requests approved by the local policy.
|
Group bandwidth (bps)
|
Amount of bandwidth configured for a class of reservations in bits per second (bps).
|
Per-flow b/w (bps)
|
Amount of bandwidth configured for each reservation in bits per second (bps).
|
Ethernet2/1
|
Local policy configured for a specific interface on the router.
|
Generic policy settings
|
Policy settings that are not specific to the local policy.
•Default policy: Accept all means that all RSVP messages are accepted and forwarded. Reject all means that all RSVP messages are rejected.
•Preemption: Disabled means that RSVP should not implement any preemption decisions required by a particular local or remote policy. Enabled means that RSVP should implement any preemption decisions required by a particular local or remote policy.
|
Related Commands
Command
|
Description
|
ip rsvp policy local
|
Determines how to perform authorization on RSVP requests.
|
show ip rsvp policy vrf
To display information for a Resource Reservation Protocol (RSVP) policy configured with a virtual routing and forwarding (VRF) instance, use the show ip rsvp policy vrf command in user EXEC or privileged EXEC mode.
show ip rsvp policy vrf {* | vrf-name} [identity [alias]] | local [acl acl | default | detail [acl acl |
default | identity alias | interface interface-type | origin-as as-number]]
Syntax Description
*
|
Displays all VRFs.
|
vrf-name
|
Name of a specified VRF.
|
identity
|
(Optional) Unique information that is conveyed in the POLICY-DATA object for RSVP messages.
|
alias
|
(Optional) Specifies a string used within the router to reference the identity in RSVP configuration commands and show displays. The string can have as many as 64 printable characters including quotes and regular expressions (in the range 0x20 to 0x7E).
Note If you use the " " or ? characters as part of the alias or locator string itself, you must type the CTRL/V key sequence before entering the embedded " " or ? characters. The alias is never transmitted to other routers.
|
local
|
(Optional) A local policy.
|
acl
|
(Optional) Access control list (ACL) for the local policy.
|
acl
|
(Optional) Specifies an ACL. Values for each ACL are 1 to 199.
|
default
|
(Optional) A default policy.
|
detail
|
(Optional) Detailed information for the VRF.
|
acl
|
(Optional) Access control list (ACL) for the local policy.
|
acl
|
(Optional) Specifies an ACL. Values for each ACL are 1 to 199.
|
default
|
(Optional) A default policy.
|
identity
|
(Optional) An application ID.
|
alias
|
(Optional) Specifies a string used within the router to reference the identity in RSVP configuration commands and show displays. The string can have as many as 64 printable characters including quotes and regular expressions (in the range 0x20 to 0x7E).
Note If you use the " " or ? characters as part of the alias or locator string itself, you must type the CTRL/V key sequence before entering the embedded " " or ? characters. The alias is never transmitted to other routers.
|
interface
|
(Optional) An interface for the VRF.
|
interface-type
|
(Optional) An interface name for the VRF.
|
origin-as
|
(Optional) An autonomous system (AS) for the VRF.
|
as-number
|
(Optional) An AS. Values for each autonomous system are 1 to 65535.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
15.0(1)M
|
This command was introduced.
|
Usage Guidelines
Use the show ip rsvp policy vrf command to display the policies configured for VRFs.
Examples
The following example shows an ACL local policy that is configured for a specified VRF:
Router# show ip rsvp policy vrf myVrf1 local acl 101
Path:AF Resv:AF PathErr:AF ResvErr:AF ACL(s): 101
Path:AF Resv:AF PathErr:AF ResvErr:AF ACL(s): 101
Default policy: Accept all
Table 119 describes the significant fields shown in the display.
Table 119 show ip rsvp policy vrf Field Descriptions
Field
|
Description
|
A=Accept
|
Accept the message.
|
F=Forward
|
Forward the message.
|
VRF
|
Name of the VRF.
Global: Global policies configured for the VRF.
Path: AF—Accept and forward these messages.
Resv: AF—Accept and forward these messages.
PathErr—Accept and forward these messages.
ResvErr—Accept and forward these messages.
ACL(s)—Access control list number.
Ethernet0/0—The interface configured for the VRF.
|
Generic policy settings
|
Policy settings that are not specific to COPS or the local policy.
Default policy: Accept all means all RSVP messages are accepted and forwarded. Reject all means all RSVP messages are rejected.
Preemption: Disabled means that RSVP should not implement any preemption decisions required by a particular local or remote policy. Enabled means that RSVP should implement any preemption decisions required by a particular local or remote policy.
|
Related Commands
Command
|
Description
|
ip rsvp policy vrf
|
Configures an RSVP policy for a VRF.
|
show ip rsvp precedence
To display IP precedence information about Resource Reservation Protocol (RSVP) interfaces, use the show ip rsvp precedence command in user EXEC or privileged EXEC mode.
show ip rsvp precedence [type number]
Syntax Description
type
|
(Optional) Type of interface.
|
number
|
(Optional) Number of the interface.
|
Command Modes
User EXEC(>)
Privileged EXEC(#)
Command History
Release
|
Modification
|
15.0(1)M
|
This command was introduced.
|
Usage Guidelines
To obtain IP precedence information about a specific interface configured to use RSVP, specify the interface name with the show ip rsvp precedence command. To obtain IP precedence information about all interfaces enabled for RSVP on the router, use the show ip rsvp precedence command without specifying an interface name.
Examples
The following example shows the IP precedence information for the interaces on which RSVP is enabled:
Router# show ip rsvp precedence ethernet 0/1
Interface name Precedence Precedence TOS TOS
conform exceed conform exceed
Table 120 describes the fields shown in the display.
Table 120 show ip rsvp precedence Field Descriptions
Field
|
Description
|
Interface name
|
Displays the interface details.
|
Precedence conform
|
Displays the IP precedence conform information for an interface.
Note The Precedence conform value specifies an IP precedence value in the range from 0 to 7 for traffic that conforms to the RSVP flowspec.
|
Precedence exceed
|
Displays the IP precedence exceed information for an interface.
Note The Precedence exceed value specifies an IP Precedence value in the range from 0 to 7 for traffic that exceeds the RSVP flowspec.
|
TOS conform
|
Displays the IP type of service (ToS) conform information for an interface.
Note The TOS conform value specifies a ToS value in the range from 0 to 31 for traffic that conforms to the RSVP flowspec.
|
TOS exceed
|
Displays the IP type of service (ToS) exceed information for an interface.
Note The TOS exceed value specifies a ToS value in the range from 0 to 31 for traffic that exceeds the RSVP flowspec.
|
Related Commands
Command
|
Description
|
show ip rsvp
|
Displays RSVP-related information.
|
show ip rsvp interface
|
Displays RSVP-related interface information.
|
show ip rsvp tos
|
Displays IP TOS information for RSVP enabled interfaces.
|
show ip rsvp request
To display Resource Reservation Protocol (RSVP)-related request information currently in the database, use the show ip rsvp request command in user EXEC or privileged EXEC mode.
show ip rsvp request [vrf {* | vrf-name}] [detail] [filter [destination ip-address | hostname]
[dst-port port-number] [source ip-address | hostname] [src-port port-number]]
Syntax Description
vrf *
|
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances.
|
vrf vrf-name
|
(Optional) Name of a specified VRF.
|
detail
|
(Optional) Displays additional receiver information.
|
filter
|
(Optional) Displays a subset of the receivers to display.
|
destination ip-address
|
(Optional) Specifies the destination IP address of the receiver.
|
hostname
|
(Optional) Specifies the hostname of the receiver.
|
dst-port port-number
|
(Optional) Specifies the destination port number. Valid destination port numbers can be in the range of 0 to 65535.
|
source ip-address
|
(Optional) Specifies the source IP address of the receiver.
|
hostname
|
(Optional) Specifies the hostname of the receiver.
|
src-port port-number
|
(Optional) Specifies the source port number. Valid source port numbers can be in the range of 0 to 65535.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2
|
This command was integrated into Cisco IOS Release 12.2. The detail keyword was added to display additional request information.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S. This command was enhanced to show Fast Reroute information when a link-state packet (LSP) is actively using a backup tunnel that terminates at this node (that is, when a node is the merge point [MP].) The command is supported on the Cisco 10000 series Edge Services Router (ESR).
|
12.2(18)SXD1
|
This command was integrated into Cisco IOS Release 12.2(18)SXD1.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.2(33)SRC
|
The command output was modified to display RSVP aggregation information.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
15.0(1)M
|
This command was modified. The vrf and * keywords and the vrf-name argument were added.
|
Usage Guidelines
Use the show ip rsvp request command to display the RSVP reservations currently being requested upstream for a specified interface or all interfaces. The received reservations may differ from requests because of aggregated or refused reservations. If desired, information for only a single tunnel or a subset of tunnels can be displayed.
Limiting the Display
When hundreds or thousands of tunnels exist and you are interested in only a few, you can display the output for only a single tunnel or a subset of tunnels. To request a limited display, enter the show ip rsvp request command with the appropriate keyword (called an output filter): destination, dst-port, source, and src-port. You can enter any or all of the output filters, and you can enter them whether or not you specify the detail keyword.
You can also limit the display to a particular VRF by using the show ip rsvp request vrf vrf-name command.
Examples
RSVP Aggregation Example 1
The following is sample output from the show ip rsvp request command when RSVP aggregation is configured:
Router# show ip rsvp request
To From Pro DPort Sport Next Hop I/F Fi Serv BPS
192.168.5.1 192.168.2.1 TCP 222 222 192.168.40.1 Se1/0 FF RATE 80K
192.168.50.1 192.168.40.1 0 46 0 10.10.10.4 Se1/0 FF LOAD 300K
Table 121 describes the significant fields shown in the display.
Table 121 show ip rsvp request Field Descriptions
Field
|
Description
|
To
|
IP address of the end-to-end (E2E) receiver or deaggregator.
|
From
|
IP address of the E2E sender or aggregator.
|
Pro
|
Protocol code.
•TCP indicates Transmission Control Protocol.
•Code 0 indicates an aggregate reservation.
|
DPort
|
Destination port number.
•DSCP for aggregate reservations.
|
Sport
|
Source port number.
•0 for aggregate reservations.
|
Next Hop
|
IP address of the next hop.
•Aggregator for E2E reservations mapped onto aggregates.
•Next hop RSVP node for aggregate or E2E reservations onto an interface.
|
I/F
|
Interface of the next hop.
|
Fi
|
Filter (Wildcard Filter, Shared Explicit, or Fixed Filter).
|
Serv
|
Service (value can be rate or load).
|
BPS
|
The rate, in bits per second, in the RSVP reservation request for a reservation.
Note In the example, the top one is the E2E reservation signaled at 80 bps and the corresponding aggregate request at 300 bps.
|
RSVP Aggregation Example 2
The following is sample output from the show ip rsvp request detail command when RSVP aggregation is configured:
Router# show ip rsvp request detail
RSVP Reservation. Destination is 192.168.5.1, Source is 192.168.2.1,
Protocol is TCP, Destination port is 222, Source port is 222
Prev Hop: 192.168.40.1 on Serial1/0
Reservation Style is Fixed-Filter, QoS Service is Guaranteed-Rate
Average Bitrate is 80K bits/sec, Maximum Burst is 5K bytes
Request ID handle: 0100040E.
Policy: Forwarding. Policy source(s): Default
Priorities - preempt: 0, defend: 0
PSB Handle List [1 elements]: [0x19000407]
RSB Handle List [1 elements]: [0x17000409]
3175 Aggregation: RSVP 3175 AggResv 192.168.40.1->192.168.50.1_ef(46)
RSVP Reservation. Destination is 192.168.50.1, Source is 192.168.40.1,
Protocol is 0 , Destination port is 46, Source port is 0
Prev Hop: 10.10.10.4 on Serial1/0
Reservation Style is Fixed-Filter, QoS Service is Controlled-Load
Average Bitrate is 300K bits/sec, Maximum Burst is 300K bytes
Request ID handle: 0100040B.
Policy: Forwarding. Policy source(s): Default
Priorities - preempt: 0, defend: 0
PSB Handle List [1 elements]: [0x9000408]
RSB Handle List [1 elements]: [0x100040A]
Table 122 describes the significant fields shown in the display.
Table 122 show ip rsvp request detail Field Descriptions
Field
|
Description
|
RSVP Reservation
|
Destination—Receiver's IP address of the E2E RESV message.
Source—Sender's IP address of the E2E RESV message.
|
Protocol
|
Protocol—IP protocol used; TCP—Transmission Control Protocol.
•0 for aggregate reservations.
|
Destination port
|
Receiver's port number.
•DSCP for aggregate reservations.
|
Source port
|
Sender's port number.
•0 for aggregate reservations.
|
Previous Hop
|
IP address of the previous hop on the specified interface.
Note This is the aggregator's IP address in the case of an E2E reservation mapped onto an aggregate as seen at the deaggregator.
|
Reservation Style
|
Multi-reservations sharing of bandwidth; values include Fixed-Filter, Shared-Explicit, and Wildcard-Filter.
|
QoS Service
|
Type of quality of service (QoS) configured; values include Guaranteed-Rate and Controlled-Load.
|
Average Bitrate
|
Average rate requested, in bits per second, for the data.
|
Maximum Burst
|
Largest amount of data allowed in kilobytes.
|
Request ID handle
|
Internal database ID assigned to the request by RSVP for bookkeeping purposes.
|
Policy
|
Policy status: Forwarding—RSVP RESV messages are being accepted and forwarded.
|
Policy source(s)
|
Type of local policy in effect; values include Default, Local, and MPLS/TE.
|
Priorities
|
RSVP preemption and hold priorities of the reservation; default is 0.
|
PSB Handle List
|
Path state block (PSB) internal database identifier assigned by RSVP for bookkeeping purposes.
|
RSB Handle List
|
Reservation state block (RSB) internal database identifier assigned by RSVP for bookkeeping purposes.
|
3175 Aggregation
|
RSVP aggregation as defined in RFC 3175, Aggregation of RSVP for IPv4 and IPv6 Reservations.
Note This E2E reservation is mapped onto an RSVP aggregate reservation with an aggregator (source) IP address of 192.168.40.1, a destination (deaggregator) IP address of 192.168.50.1, and a DSCP value of expedited forwarding (EF).
|
MP Example
The following is sample output from the show ip rsvp request detail command when the command is entered on the midpoint (MP) before and after a failure.
Figure 5 illustrates the network topology for the RSVP configuration example.
Figure 5 Network Topology for the RSVP Configuration Example
Example 1: The command is entered on the MP before a failure.
Router# show ip rsvp request detail
RSVP Reservation. Tun Dest: 10.2.2.1 Tun Sender: 10.2.2.0,
Next Hop is 10.1.1.5 on POS0/1
Reservation Style is Shared-Explicit, QoS Service is Controlled-Load
Average Bitrate is 0G bits/sec, Maximum Burst is 1K bytes
Example 2: The command is entered on the MP after a failure.
Router# show ip rsvp request detail
RSVP Reservation. Tun Dest: 10.2.2.1 Tun Sender: 10.2.2.0,
Next Hop is 10.1.1.5 on POS0/1
Reservation Style is Shared-Explicit, QoS Service is Controlled-Load
Average Bitrate is 0G bits/sec, Maximum Burst is 1K bytes
FRR is in progress (we are Merge Point)
RSVP Reservation. Tun Dest: 10.2.2.1 Tun Sender: 10.2.2.0,
Next Hop is 10.0.0.0 on POS0/1
Reservation Style is Shared-Explicit, QoS Service is Controlled-Load
Average Bitrate is 0G bits/sec, Maximum Burst is 1K bytes
FRR is in progress (we are Merge Point)
Notice that after the failure, there are two entries for the rerouted LSP.
The first entry continues to show the prefailure information (that is, RESV messages are being sent to 10.1.1.5 on POS0/1). This state is for the RESV being sent upstream before the failure, in response to path messages sent before the failure. This state may time out quickly, or it may continue to be refreshed for a few minutes if, for example, an upstream node is unaware of the failure.
The second entry shows the post-failure information (that is, RESV messages are being sent to 10.0.0.0 on POS0/1). This state is for the RESV messages being sent upstream after the failure (to the point of local repair [PLR]), and will remain and be refreshed as long as the LSP is rerouted.
In example 2, the MP is also the tail of the LSP. There is no record route object (RRO) information because there are no nodes downstream.
Related Commands
Command
|
Description
|
show ip rsvp reservation
|
Displays RSVP PATH-related receiver information currently in the database.
|
show ip rsvp sender
|
Displays RSVP RESV-related receiver information currently in the database.
|
show ip rsvp reservation
To display Resource Reservation Protocol (RSVP)-related receiver information currently in the database, use the show ip rsvp reservation command in user EXEC or privileged EXEC mode.
show ip rsvp reservation [detail | filter [destination ip-address |
