Cisco IOS Quality of Service Solutions Command Reference

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

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

The table below describes the significant fields shown in the display.

Table 1. 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 nbr detail

To display detailed information about Resource Reservation Protocol (RSVP) traffic engineering (TE) client hellos for neighbors, use the show ip rsvp hello client nbr detail command in user EXEC or privileged EXEC mode.

show ip rsvp hello client nbr detail [ filter [ destination hostname ] ]

Syntax Description


filter	(Optional) Specifies filters to limit the display of output.
destination	(Optional) Displays the filters configured on the destination (tunnel tail).
`hostname`	(Optional) IP address or name of destination (tunnel tail).

Command Modes

User EXEC (>)
Privileged EXEC (#)

Command History


Release	Modification
12.0(33)S	This command was introduced.
12.2(33)SRC	This command was integrated in Cisco IOS Release 12.2(33)SRC.

Usage Guidelines

Use the show ip rsvp hello client nbr detail command to display information about the neighbors (nbr).

Examples

The following is sample output from the show ip rsvp hello client nbr detail command:


Router# show ip rsvp hello client nbr detail
Hello Client Neighbors
  Remote addr 10.0.0.1,  Local addr  10.0.0.3
    Nbr State: Normal    Type: Reroute
    Nbr Hello State: Up
    LSPs protecting: 1
    I/F: Et1/3
  Remote addr 172.16.1.1,  Local addr  192.168.1.1
    Nbr State: Normal    Type: Graceful Restart
    Nbr Hello State: Lost
    LSPs protecting: 1

The table below describes the fields shown in the display

Table 2. show ip rsvp hello client nbr 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 GR (graceful restart) is also lost. WAIT PathTear--PathTear message is delayed to allow traffic in the pipeline to be transmitted.
Type	Type of client: graceful restart (GR), reroute RR (hello state timer), or fast reroute (FRR).
Nbr Hello 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 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	Displays summary information about RSVP TE client hellos for neighbors.

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
Hello Client Neighbors
  Remote addr 10.0.0.1,  Local addr  10.0.0.3
    Nbr State: Normal    Type: Reroute
    Nbr Hello State: Up
    LSPs protecting: 1
    I/F: Et1/3
  Remote addr 172.16.1.1,  Local addr  192.168.1.1
    Nbr State: Normal    Type: Graceful Restart
    Nbr Hello State: Lost
    LSPs protecting: 1

The table below 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 3. 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

The table below describes the significant fields shown in the display.

Table 4. 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
  Refresh misses: 4
  DSCP: 0x30
  Advertised restart time: 30000 msecs
  Advertised recovery time: 120000 msecs
  Maximum wait for recovery: 3600000 msecs

The table below describes the significant fields shown in the display.

Table 5. 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)
    I/F:  Serial2/0
    State:   Up        (for 2d19h2d19h)
    Clients: ReRoute
    LSPs protecting: 1
    Missed acks: 4, IP DSCP: 0x30
    Refresh Interval (msec)
      Configured: 6000
      Statistics: (from 40722 samples)
        Min:      6000
        Max:      6064
        Average:  6000
        Waverage: 6000 (Weight = 0.8)
        Current:  6000
    Last sent Src_instance: 0xE617C847
    Last recv nbr's Src_instance: 0xFEC28E95
    Counters:
      Communication with neighbor lost:
        Num times:                    0
        Reasons:
          Missed acks:                0
          Bad Src_Inst received:      0
          Bad Dst_Inst received:      0
          I/F went down:              0
          Neighbor disabled Hello:    0
      Msgs Received:   55590
           Sent:       55854
           Suppressed: 521
  Neighbor 10.0.0.8 Source  10.0.0.7
    Type: Passive   (responding to requests)
    I/F:  Serial2/1
    Last sent Src_instance: 0xF7A80A52
    Last recv nbr's Src_instance: 0xD2F1B7F7
    Counters:
      Msgs Received:   199442
           Sent:       199442

The table below describes the significant fields shown in the display.

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

show ip rsvp hello instance summary

To display summary information about a hello instance, use the show ip rsvp hello instance summary command in user EXEC or privileged EXEC mode.

show ip rsvp hello instance summary

Syntax Description

This command has no arguments or keywords.

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, 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
Active Instances:
  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    
Passive Instances:
  Neighbor        I/F       
  10.0.0.1        Se2/1     
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

The table below describes the significant fields shown in the display.

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

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
 
Status: Enabled
  Packet arrival queue:
    Wait times (msec)
      Current:0
      Average:0
      Weighted Average:0 (weight = 0.8)
      Max:4
    Current length: 0 (max:500)
  Number of samples taken: 2398525

The table below describes the significant fields shown in the display.

Table 8. 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	Globally clears Hello statistics.
ip rsvp signalling hello refresh interval	Configures the Hello request interval.
ip rsvp signalling hello statistics	Enables Hello statistics on the 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.
15.0(1)S	This command was modified. The output was updated to display information for point-to-point (P2P) and point-to-multipoint traffic engineering (P2MP) counters.
15.2(2)S	This command was modified. The output was enhanced to show checkpoint information for MPLS traffic engineering autotunnel and automesh stateful switchover (SSO) tunnels.
Cisco IOS XE Release 3.6S	This command was modified. The output was enhanced to show checkpoint information for MPLS traffic engineering autotunnel and automesh stateful switchover (SSO) tunnels.

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

State: Active
P2P LSPs for which recovery:
  Attempted: 1
  Succeeded: 1
  Failed:    0
P2MP subLSPs for which recovery:
  Attempted: 2
  Succeeded: 2
  Failed:    0
Bulk sync
  initiated: 1
Send timer
  started: 2
Checkpoint Messages (Items) Sent
  Succeeded:      2  (8)
    Acks accepted:2  (8)
    Acks ignored:     (0)
    Nacks:        0  (0)
  Failed:         0  (0)
  Buffer alloc:   2
  Buffer freed:   4
ISSU:
  Checkpoint Messages Transformed:
    On Send:
      Succeeded:         2
      Failed:            0
      Transformations:   0
    On Recv:
      Succeeded:         2
      Failed:            0
      Transformations:   0
  Negotiation:
    Started:              2
    Finished:             2
    Failed to Start:      0
    Messages:
      Sent:
        Send succeeded:   14
        Send failed:      0
        Buffer allocated:        14
        Buffer freed:            0
        Buffer alloc failed:     0
      Received:
        Succeeded:        10
        Failed:           0
        Buffer freed:     10
  Init:
    Succeeded:            1
    Failed:               0
  Session Registration:
    Succeeded:            1
    Failed:               0
  Session Unregistration:
    Succeeded:            1
    Failed:               0
Errors:
  None
Historical: (When Active was Standby)
Checkpoint Messages (Items) Received
  Valid:        2  (11)
  Invalid:      0  (0)
Buffer freed: 2

The table below describes the significant fields shown in the display.

Table 9. 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 unsuccessfully (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

State: Standby
 
Checkpoint Messages (Items) Received
  Valid:        1  (2)
  Invalid:      0  (0)
  Buffer freed: 1
 
ISSU:
  Checkpoint Messages Transformed:
    On Send:
      Succeeded:         0
      Failed:            0
      Transformations:   0
    On Recv:
      Succeeded:         1
      Failed:            0
      Transformations:   0
 
  Negotiation:
    Started:              1
    Finished:             1
    Failed to Start:      0
    Messages:
      Sent:
        Send succeeded:   5
        Send failed:      0
        Buffer allocated:        5
        Buffer freed:            0
        Buffer alloc failed:     0
      Received:
        Succeeded:        7
        Failed:           0
        Buffer freed:     7
 
  Init:
    Succeeded:            1
    Failed:               0
 
  Session Registration:
    Succeeded:            0
    Failed:               0
 
  Session Unregistration:
    Succeeded:            0
    Failed:               0
          
Errors:
  None

The table below describes the significant fields shown in the display.

Table 10. 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 the table above.

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 contents of 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 | if-autotun | link-management { interfaces [ fixed | variable ] | system } | lsp [ filter [ destination ip-address ] | [ lsp-id lsp-id ] | [ source ip-address ] | [ tunnel-id tunnel-id ] ] | lsp-head [ filter number ] | summary }

Syntax Description


hello	Displays information about hello entries in read and write databases.
if-autotun	Displays information about TE HA autotunnel interface entries in read and write databases.
link-management	Displays information about link-management entries in the read and write databases.
interfaces	Displays information about link-management interfaces in the read and write databases.
fixed	(Optional) Displays information about link-management fixed interfaces in the read and write databases.
variable	(Optional) Displays information about 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 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 LSP-head 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 entries in 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 specified by the lsp-head keyword.
12.4(20)T	This command was integrated into Cisco IOS Release 12.4(20)T.
15.0(1)S	This command was integrated into Cisco IOS Release 15.0(1)S. The command output was modified to distinguish database-entry information for point-to-point (P2P) tunnels from that for point-to-multipoint (P2MP) tunnels and to display error database information.
12.2(50)SY	This command was integrated into Cisco IOS Release 12.2(50)SY.
Cisco IOS XE Release 3.5S	This command was integrated into Cisco IOS XE Release 3.5S.
15.2(2)S	This command was modified. The if-autotun keyword was added. The output for the show ip rsvp high-availability database lsp , the show ip rsvp high-availability database lsp-head , and the show ip rsvp high-availability database summary commands was enhanced to display checkpoint information for MPLS TE autotunnel and automesh stateful switchover (SSO) tunnels.
Cisco IOS XE Release 3.6S	This command was modified. The if-autotun keyword was added. The output for the show ip rsvp high-availability database lsp , the show ip rsvp high-availability database lsp-head , and the show ip rsvp high-availability database summary commands was enhanced to display checkpoint information for MPLS TE autotunnel and automesh stateful switchover (SSO) tunnels.

Usage Guidelines

Use the show ip rsvp high-availability database command to display information about 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; the list is placed in the outgoing ERO and checkpointed with the LSP data as the loose hop information.

In Cisco IOS Release 15.0(1)S and later releases, the show ip rsvp high-availability database lsp command displays sub-LSP information. If any sub-LSP, whether P2MP or P2P, fails to recover after a stateful switchover (SSO), the failure is noted in an error database for troubleshooting. You can use the show ip rsvp high-availability database lsp command to display error database entries.

You can use the show ip rsvp high-availability database lsp-head command only on a headend router; this command gives no information on other routers

Examples

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
 
HELLO WRITE DB
   Header:
     State: Checkpointed     Action: Add
     Seq #: 1                Flags: 0x0
   Data:
     Last sent Src_instance: 0xDE435865
HELLO READ DB

The table below describes the significant fields shown in the display.

Table 11. 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 is a temporary action that takes place 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 #	Number used by the active and standby RPs to synchronize message acknowledgments (acks) and negative acknowledgments (nacks) to sent messages.
Flags	Attribute used to identify or track data.
Data	Information about the last transmission.
Last sent Src_instance	Last sent source instance identifier.
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.

Examples

The following is sample output from the show ip rsvp high-availability database hello on a standby RP:


Router# show ip rsvp high-availability database hello
 
HELLO WRITE DB
HELLO READ DB
   Header:
     State: Checkpointed     Action: Add
     Seq #: 1                Flags: 0x0
   Data:
     Last sent Src_instance: 0xDE435865

These fields are the same as those for the active RP described in the table except they are now in the read database for the standby RP.

Examples

The following is sample output from the show ip rsvp high-availability database if-autotun command on an active RP.

Router# show ip rsvp high-availability database if-autotun
IF_AUTOTUN WRITE DB

  Header:
    State: Checkpointed     Action: Add
    Seq #: 1                Flags: 0x0
  Data:
    Tunnel ID: 1000 (if_handle: 85), prot_if_handle: 14
    template_unit: n/a, dest: 22.22.22.22, flags=0x0

  Header:
    State: Checkpointed     Action: Add
    Seq #: 61               Flags: 0x0
  Data:
    Tunnel ID: 2000 (if_handle: 86), prot_if_handle: 14
    template_unit: n/a, dest: 22.22.22.22, flags=0x1

  Header:
    State: Checkpointed     Action: Add
    Seq #: 1                Flags: 0x0
  Data:
    Tunnel ID: 3000 (if_handle: 87), prot_if_handle: 0
    template_unit: 1, dest: 22.22.22.22, flags=0x2

  Header:
    State: Checkpointed     Action: Add
    Seq #: 1                Flags: 0x0
  Data:
    Tunnel ID: 3001 (if_handle: 88), prot_if_handle: 0
    template_unit: 1, dest: 172.16.255.128, flags=0x2

  Header:
    State: Checkpointed     Action: Add
    Seq #: 1                Flags: 0x0
  Data:
    Tunnel ID: 3002 (if_handle: 89), prot_if_handle: 0
    template_unit: 1, dest: 200.0.0.0, flags=0x2


IF_AUTOTUN READ DB

The table below describes the significant fields shown in the display.

Table 12. show ip rsvp high-availability database if-autotun—Active RP Field Descriptions
Field	Description
IF_AUTOTUN WRITE DB	Storage area for active RP autotunnel interface information. 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 still 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 #	Number used by the active and standby RPs to synchronize message acks and nacks to sent messages.
Flags	Attributes used to identify or track data.
Data	Information about the last transmission.
Tunnel ID	Tunnel identifier.
if_handle	Internal number representing the autotunnel interface. For the same tunnel ID, this if_handle value should always be the same for the record in the Standby READ DB as in the Active WRITE DB.
prot_if_handle	For autotunnel mesh tunnels, this value should always be zero. For autotunnel primary tunnels, this is an internal number representing the egress interface of the autotunnel primary. For autotunnel backup tunnels, this is an internal number representing the interface that the backup is protecting. In all three cases, for the same tunnel ID, this value should always be the same for the record in the Standby READ DB as in the Active WRITE DB.
template_unit	For autotunnel mesh, this represents the auto-template interface number that the mesh tunnel was created from. For autotunnel primary and backup, this should be "n/a."
dest	Destination IP address of the autotunnel.
flags	Encodings have these values: 0 = autotunnel primary 1 = autotunnel backup 2 = autotunnel mesh
IF_AUTOTUN READ DB	Storage area for standby RP autotunnel interface information. This field is blank on an active RP.

The fields for a standby RP are the same as those described in the table except that they are now in the interface autotunnel read database instead of the interface autotunnel write database that is used by an active RP.

Examples

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
 
TE LINK WRITE DB
Flooding Protocol: ospf  IGP Area ID: 0  Link ID: 0 (GigabitEthernet3/2)
  Header:
    State: Checkpointed     Action: Add
    Seq #: 4                Flags: 0x0
  Data:
        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
        Res. Sub BW: 0 kbits/sec
        Upstream::
                                 Global Pool   Sub Pool  
                                 -----------   ----------
        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
        Downstream::
                                 Global Pool   Sub Pool  
                                 -----------   ----------
        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
        Affinity Bits: 0x0
        Protection Type: Capability 0,  Working Priority 0
        Number of TLVs: 0

The table below describes the significant fields shown in the display.

Table 13. 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 #	Number used by the active and standby RPs to synchronize message acks and nacks to sent messages.
Flags	Attribute used to identify or track data.
Data	Information about the last transmission.
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 (kb/s).
Res. Global BW	Amount of reservable global pool bandwidth (in kb/s) on this link.
Res. Sub BW	Amount of reservable subpool bandwidth (in kb/s) on this link.
Upstream	Header for the following section of bandwidth values.
Global Pool	Global pool bandwidth (in kb/s) on this link.
Sub Pool	Subpool bandwidth (in kb/s) on this link.
Reservable Bandwidth [1]	Amount of bandwidth (in kb/s) 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 the table except that they are now in the TE link read database instead of the TE link write database that is used by an active RP.

Examples

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
 
TE SYSTEM WRITE DB
Flooding Protocol: OSPF  IGP Area ID: 0
  Header:
    State: Checkpointed     Action: Modify
    Seq #: 4                Flags: 0x0
  Data:
    LM Flood Data::
      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)
      Fragment id: 0
TE SYSTEM READ DB

The table below describes the significant fields shown in the display.

Table 14. 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 #	Number 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 about the last transmission.
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 the table except that they are now in the TE system read database instead of the TE system write database that is used by an active RP.

Examples

The following is sample output from the show ip rsvp high-availability database lsp command on an active RP for a P2P tunnel:


Router# show ip rsvp high-availability database lsp
 
Tun ID: 0   LSP ID: 10   (P2P)
  SubGrp ID:   -
  SubGrp Orig: -
  Dest:   10.3.0.1
  Sender: 10.1.0.1     Ext. Tun ID: 10.1.0.1
  Header:
    State: Checkpointed     Action: Add
    Seq #: 2                Flags: 0x0
  Data:
    PathSet ID: -
    Lspvif if_num: -
    InLabel: -
    Out I/F: Se2/0
    Next-Hop: 10.1.3.2
    OutLabel: 16
    Loose hop info: None (0)

Examples

The following is sample output from the show ip rsvp high-availability database lsp command on an active RP for a P2MP tunnel:


Router# show ip rsvp high-availability database lsp
 
Tun ID: 1   LSP ID: 127   (P2MP)
  SubGrp ID:   1
  SubGrp Orig: 10.1.0.1
  Dest:   10.2.0.1
  Sender: 10.1.0.1     Ext. Tun ID: 10.1.0.1
  Header:
    State: Checkpointed     Action: Add
    Seq #: 30               Flags: 0x0
  Data:
    PathSet ID: 0x1A000003
    Lspvif if_num: 35 (Lspvif0)
    InLabel: 19
    Out I/F: None
    Next-Hop: -
    OutLabel: -
    Loose hop info: None (0)

The table below describes the significant fields shown in the display.

Table 15. show ip rsvp high-availability database lsp—Active RP Field Descriptions
Field	Description
P2P/P2MP	Tunnel type.
Subgrp ID	Subgroup identifier (valid only for P2MP TE LSPs).
Subgrp Orig	Subgroup origin IP address (valid only for P2MP TE LSPs).
Lspvif if_num	Interface number of the LSPVIF (valid only for P2MP TE tailends).
PathSet ID	Path set identifier (valid only for P2MP TE LSPs)
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 #	Number 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 about the last transmission.
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 the table except that they are now in the LSP read database instead of the LSP write database that is used by an active RP.

Examples

The following is sample output from the show ip rsvp high-availability database lsp-head command on an active RP for a P2P tunnel:


Router# show ip rsvp high-availability database lsp-head
 
LSP_HEAD WRITE DB
  Tun ID: 0  (P2P)
  Header:
    State: Checkpointed     Action: Add
    Seq #: 2                Flags: 0x0
  Data:
    lsp_id: 10, bandwidth: 5, thead_flags: 0x1, popt: 1
    feature flags: none
    output_if_num: 11, output_nhop: 10.1.3.2
    RRR path setup info
      Destination: 10.3.0.1, Id: 10.3.0.1 Router Node (ospf) flag:0x0
      IGP: ospf, IGP area: 0, Number of hops: 3, metric: 128
      Hop 0: 10.1.3.2, Id: 10.2.0.1 Router Node (ospf), flag:0x0
      Hop 1: 10.2.3.3, Id: 10.3.0.1 Router Node (ospf), flag:0x0
      Hop 2: 10.3.0.1, Id: 10.3.0.1 Router Node (ospf), flag:0x0

Examples

The following is sample output from the show ip rsvp high-availability database lsp-head command on an active RP for a P2MP tunnel:


Router# show ip rsvp high-availability database lsp-head
 
LSP_HEAD WRITE DB
Tun ID: 1  (P2MP)
  Destination: 10.2.0.1
  Header:
    State: Checkpointed     Action: Add
    Seq #: 3                Flags: 0x0
  Data:
    lsp_id: 11, bandwidth: 100, thead_flags: 0x1, popt: 1
    Subgrp_id: 1
    feature flags: none
    output_if_num: 3, output_nhop: 10.1.2.2
    RRR path setup info
      Destination: 10.2.0.1, Id: 10.2.0.1 Router Node (ospf) flag:0x0
      IGP: ospf, IGP area: 0, Number of hops: 3, metric: 10
      Hop 0: 10.1.2.1, Id: 10.1.0.1 Router Node (ospf), flag:0x0
      Hop 1: 10.1.2.2, Id: 10.2.0.1 Router Node (ospf), flag:0x0
      Hop 2: 10.2.0.1, Id: 10.2.0.1 Router Node (ospf), flag:0x0

The table below describes the significant fields shown in the display.

Table 16. 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.
P2P/P2MP	Tunnel type.
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 is a temporary action that takes place 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 #	Number 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 about the last transmission.
lsp_id	LSP identifier.
bandwidth	Bandwidth on the LSP (in kb/s).
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 as follows: 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.
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 the table except that they are now in the LSP_head read database instead of the LSP_head write database that is used by an active RP.

Examples

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
 
Write DB:
  Send-Pending:     0
  Ack-Pending :     0
  Checkpointed:    10
  Total       :    10
Read DB:
  Total       :     0

The table below describes the significant fields shown in the display.

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

Examples

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
 
Write DB:
  Send-Pending:     0
  Ack-Pending :     0
  Checkpointed:     0
  Total       :     0
Read DB:
  Total       :    10

The table below describes the significant fields shown in the display.

Table 18. 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 database.
Total	Total number of entries in the read database.

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.
15.2(2)S	This command was modified. The output was enhanced to display checkpoint information for MPLS TE autotunnel and automesh stateful switchover (SSO) tunnels.
Cisco IOS XE Release 3.6S	This command was modified. The output was enhanced to display checkpoint information for MPLS TE autotunnel and automesh stateful switchover (SSO) tunnels.

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

State:
Graceful-Restart: Enabled, mode: full
HA state: Active
Checkpointing: Allowed
Messages:
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.

The table below describes the significant fields shown in the display.

Table 19. 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
Peer RP Present : No
RF Comm. Up : No
Flow Control On : No
CF Comm. Up : No
RF Ready to Recv: No

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.

The table below describes the significant fields shown in the display.

Table 20. 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
 
State:
 Graceful-Restart: Enabled
 HA state: active
Checkpointing: Allowed
Recovery Time (msec)
 Advertised:    120000 msec
 Last recorded: 75012 msec
Messages:
 Send timer: not running (Interval:1000)
 Items sent per Interval: 200

The table below describes the significant fields shown in the display

Table 21. 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 { receivers | senders } [ hostname | group-address ]

Syntax Description


senders	RSVP-related sender information currently in the database.
receivers	RSVP-related receiver information currently in the database.
`hostname`	(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	This command was modified. 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.
Cisco IOS XE Release 2.6	This command was integrated into Cisco IOS XE Release 2.6.

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
  Mode(s): Host CLI

The table below describes the significant fields shown in the display.

Table 22. 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 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 Simple Network Management Protocol (SNMP) SET directive from a remote management station. CLI--The reservation was created via a local RSVP command. Host CLI--A combination of the host and command line interface (CLI) strings meaning that the static sender being displayed was created by the ip rsvp sender-host command.

In the following example from the show ip rsvp host senders command, an RSVP identity is 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
  Mode(s): Host CLI
  Identity: voice100                                                        
    Locator: GUID=www.cisco.com,APP=voice,VER=100.0                          
    ID Type: Application

The table below describes the significant fields shown in the display.

Table 23. 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: CLI--The reservation was created via a local RSVP command. Host--The router is acting as the host system or RSVP endpoint for this reservation. 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 command. 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.
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 and Cisco IOS XE software support application IDs 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
VRF: vrf2
To                  From                 Pro DPort Sport Prev Hop      I/F      BPS
192.168.104.4       198.168.104.12       UDP 10    10    none          none     10K
  Mode(s): Host CLI
VRF: vrf1
To                  From                 Pro DPort Sport Prev Hop      I/F      BPS
192.168.105.4       198.168.105.12       UDP 10    10    none          none     10K
  Mode(s): Host CLI

The table below describes the significant fields shown in the display.

Table 24. 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 ingress

To display information about the Resource Reservation Protocol (RSVP) ingress bandwidth configured on interfaces, use the show ip rsvp ingress command in privileged EXEC mode.

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

Syntax Description


interface	Specifies the interface.
`type` `number`	(Optional) Interface type and interface or subinterface number.
detail	(Optional) Displays detailed information on the ingress bandwidth.

Command Modes

User EXEC (>)
Privileged EXEC (#)

Command History


Release	Modification
15.1(3)T	This command was introduced.
15.1(1)S	This command was integrated into Cisco IOS Release 15.1(1)S.
15.1(1)SY	This command was integrated into Cisco IOS Release 15.1(1)SY.

Usage Guidelines

Use the show ip rsvp ingress command to display information on the RSVP ingress bandwidth configured on a specific interface or all interfaces. If you do not specify the optional keyword or arguments, the command displays information about the RSVP ingress bandwidth configured on all interfaces. Use the detail keyword to display the detailed information on ingress bandwidth for a specific interface or for all interfaces.

Examples

The following is sample output from the show ip rsvp ingress detail ethernet 1/0 command:


Device# show ip rsvp ingress interface detail ethernet 1/0
interface    rsvp  in-allocated  in-i/f max  in-flow max  VRF 
Et1/0        ena   0             7500K       7500K        0

The table below describes the significant fields shown in the display.

Table 25. show ip rsvp ingress Field Descriptions

Field

Description

interface

Displays the interface on which the ingress bandwidth is configured.

rsvp

The state of RSVP. Values are enabled (activated) or disabled (deactivated).

Note

This field is disabled only if an internal error occurs when registering with Routing Information Base (RIB).

in-allocated

Amount of bandwidth, in bits per second, currently allocated.

in-i/f max

Ingress reservable bandwidth, in Kb/s.

in-flow max

Percentage of interface bandwidth configured as RSVP ingress bandwidth.

VRF

VRF name.

Related Commands


Command	Description
ip rsvp bandwidth	Enables RSVP for IP on an interface.
maximum bandwidth ingress	Configures the bandwidth parameters for the ingress policy pool.

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	This command was modified. 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	This command was modified. 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.
Cisco IOS XE Release 2.6	This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

Note

The syntax of the command depends on your platform and release. The vrf vrf-name keyword and argument combination is not supported on Cisco ASR 1000 series routers.

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

This section provides sample output from the show ip rsvp installed commands. Depending upon the interface or platform in use and the options enabled, the output that you see may vary slightly from the examples shown below:

Examples

The following is sample output from the show ip rsvp installed command:


Router# show ip rsvp installed
RSVP: Ethernet1: has no installed reservations
RSVP: Serial0:
     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

The table below describes the significant fields shown in the display.

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

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)
  Admitted flowspec:
    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)
  Admitted flowspec:
    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.

Examples

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
RSVP: Serial1/0
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

The table below describes the significant fields shown in the display.

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

Examples

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
  Admitted flowspec:
    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
  Admitted flowspec:
    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: 
    QBM
  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):

The table below describes the significant fields shown in the display.

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

Examples

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
  Admitted flowspec:
    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
VRF : myvrf

The table below describes the significant fields shown in the display.

Table 29. 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) Displays the 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	This command was modified. The detail keyword was added.
12.2(4)T	This command was modified. This command was implemented on the Cisco 7500 series and the ATM permanent virtual circuit (PVC) interface.
12.2(14)S	This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(13)T	This command was modified. The following changes 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	This command was modified. 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	This command was modified. The command output was enhanced to display fast local repair (FLR) information.
12.2(33)SRC	This command was modified. The command output was enhanced to display RSVP aggregation information.
12.4(20)T	This command was modified. The command output was enhanced 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.
Cisco IOS XE Release 2.6	This command was integrated into Cisco IOS XE Release 2.6.
15.1(3)S1	This command was modified. The show ip rsvp interface command output was enhanced to display the RSVP status configured on all the interfaces.

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 show ip rsvp interface commands. Depending upon the interface or platform in use and the options enabled, the output that you see may vary slightly from the examples shown below.

Examples

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    rsvp       allocated  i/f max  flow max sub max  VRF            
Et0/0        ena        300K       1M       1M       0   
Et0/1        ena        100K       1M       1M       0   
Et1/0        ena        200K       1M       1M       0   
Et1/1        ena        0          1M       1M       0   
Et1/2        ena        0          1M       1M       0

The table below describes the fields shown in the display.

Table 30. show ip rsvp interface Field Descriptions
Field	Description
interface	Interface name.
rsvp	Status of RSVP. Indicates if enabled or disabled.
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.

Examples

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
PO0/0:
   Bandwidth:
     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
   Signalling:
     DSCP value used in RSVP msgs:0x3F
     Number of refresh intervals to enforce blockade state:4
     Number of missed refresh messages:4
     Refresh interval:30
 PO1/0:
   Bandwidth:
     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
   Signalling:
     DSCP value used in RSVP msgs:0x3F
     Number of refresh intervals to enforce blockade state:4
     Number of missed refresh messages:4
     Refresh interval:30
PO1/1:
   Bandwidth:
     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
   Signalling:
     DSCP value used in RSVP msgs:0x3F
     Number of refresh intervals to enforce blockade state:4
     Number of missed refresh messages:4
     Refresh interval:30
 PO1/2:
   Bandwidth:
     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
   Signalling:
     DSCP value used in RSVP msgs:0x3F
     Number of refresh intervals to enforce blockade state:4
     Number of missed refresh messages:4
     Refresh interval:30
 PO1/3:
   Bandwidth:
     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
   Signalling:
     DSCP value used in RSVP msgs:0x3F
     Number of refresh intervals to enforce blockade state:4
     Number of missed refresh messages:4
     Refresh interval:30
 Lo0:
   Bandwidth:
     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
   Signalling:
     DSCP value used in RSVP msgs:0x3F
     Number of refresh intervals to enforce blockade state:4
     Number of missed refresh messages:4
     Refresh interval:30

The table below describes the significant fields shown in the detailed display for PO interface 0/0. The fields for the other interfaces are similar.

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

Examples

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
 Et2/1:
   Bandwidth:
     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
   Admission Control:
     Header Compression methods supported:
       rtp (36 bytes-saved), udp (20 bytes-saved)
   Neighbors:
     Using IP encap:0.  Using UDP encap:0
   Signalling:
     Refresh reduction:disabled
   Authentication:disabled 
 Se3/0:
   Bandwidth:
     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
   Admission Control:
     Header Compression methods supported:
       rtp (36 bytes-saved), udp (20 bytes-saved)
   Neighbors:
     Using IP encap:1.  Using UDP encap:0
   Signalling:
     Refresh reduction:disabled
   Authentication:disabled

The table below describes the significant fields shown in the display for Ethernet interface 2/1. The fields for serial interface 3/0 are similar.

Table 32. 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).

Examples

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
 Et0/0:
   Bandwidth:
    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
   Neighbors:
    Using IP encap: 0.  Using UDP encap: 0
   Signalling:
    Refresh reduction: disabled
   Authentication: enabled
    Key:           11223344
    Type:          sha-1
    Window size:   2
    Challenge:     enabled

The table below describes the significant fields shown in the display.

Table 33. 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).

Examples

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
  Et1/0:
    RSVP: Enabled
    Interface State: Up
    Bandwidth:
      Curr allocated: 9K bits/sec
      Max. allowed (total): 300K bits/sec
      Max. allowed (per flow): 300K bits/sec
      Max. allowed for LSP tunnels using sub-pools (pool 1): 0 bits/sec
      Set aside by policy (total): 0 bits/sec
    Traffic Control:
      RSVP Data Packet Classification is ON via CEF callbacks
    Signalling:
      DSCP value used in RSVP msgs: 0x30
      Number of refresh intervals to enforce blockade state: 4
    FLR Wait Time (IPv4 flows):
      Repair is delayed by 500 msec.
    Authentication: disabled
      Key chain:   <none>
      Type:        md5
      Window size: 1
      Challenge:   disabled
    Hello Extension:
      State: Disabled

The table below describes the significant fields shown in the display.

Table 34. 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).

Examples

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
Se1/0:
   RSVP: Enabled
   Interface State: Up
   Bandwidth:
     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
   Traffic Control:
     RSVP Data Packet Classification is OFF
     RSVP resource provider is: none
   Signalling:
     DSCP value used in RSVP msgs: 0x3F
     Number of refresh intervals to enforce blockade state: 4
   Authentication: disabled
     Key chain:   <none>
     Type:        md5
     Window size: 1
     Challenge:   disabled 
   FRR Extension:
     Backup Path: Not Configured
   BFD Extension:
     State: Disabled
     Interval: Not Configured
   RSVP Hello Extension:
     State: Disabled
   RFC 3175 Aggregation: Enabled
     Role: interior

The table below describes the significant fields shown in the display.

Table 35. 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, `AggregationofRSVPforIPv4andIPv6Reservations` ; values are the following: Enabled--Active. Disabled--Inactive. Role Interior--Interface is facing an aggregation region. Exterior--Interface is facing a classic RSVP region.

Examples

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
 Et1/0:
   RSVP: Enabled
   Interface State: Up
   Bandwidth:
     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
   Traffic Control:
     RSVP Data Packet Classification is ON via CEF callbacks
   Signalling:
     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
   Authentication: disabled
     Key chain:   <none>
     Type:        md5
     Window size: 1
     Challenge:   disabled 
   Hello Extension:
     State: Disabled

The table below describes the significant fields shown in the display.

Table 36. 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).

Examples

The following sample output from the show ip rsvp interface vrf my vrf detail command displays information for all the interfaces associated with the VRF named myvrf:


Router# show ip rsvp interface vrf myvrf detail
Se1/0:
   RSVP: Enabled
   Interface State: Up
   Bandwidth:
     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
   Traffic Control:
     RSVP Data Packet Classification is OFF
     RSVP resource provider is: none
   Signalling:
     DSCP value used in RSVP msgs: 0x3F
     Number of refresh intervals to enforce blockade state: 4
   Authentication: disabled
     Key chain:   <none>
     Type:        md5
     Window size: 1
     Challenge:   disabled 
   FRR Extension:
     Backup Path: Not Configured
   BFD Extension:
     State: Disabled
     Interval: Not Configured
   RSVP Hello Extension:
     State: Disabled
   RFC 3175 Aggregation: Enabled
     Role: interior
   VRF: myvrf

The table below describes the significant fields shown in the display.

Table 37. 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, `AggregationofRSVPforIPv4andIPv6Reservations` ; 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 hello configuration for all interface types, use the show ip rsvp interface detail command in user EXEC or privileged EXEC mode.

show ip rsvp interface detail [ type number ]

Syntax Description


`type` `number`	(Optional) The type and number of the interface for which you want to display the hello configuration.

Command Default

The hello configuration for all interfaces is 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.
12.2(33)SRE	This command was modified. The output was updated to display the source address used in the PHOP address field.
15.1(2)T	This command was modified. The output was updated to display the overhead percent.
15.1(1)S	This command was integrated into Cisco IOS Release 15.1(1)S.
15.2(2)SNG	This command was implemented on the Cisco ASR 901 Series Aggregation Services Routers.
15.1(1)SY	This command was integrated into Cisco IOS Release 15.1(1)SY.

Usage Guidelines

To display the hello configuration for a specific interface, use the show ip rsvp interface detail command with the type and number arguments.

Examples

The following is sample output from the show ip rsvp interface detail command:


Router# show ip rsvp interface detail GigabitEthernet 9/47 
Tu0:
   RSVP: Enabled
   Interface State: Up
   Bandwidth:
     Curr allocated: 10K bits/sec
     Max. allowed (total): 75K bits/sec
     Max. allowed (per flow): 75K bits/sec
     Max. allowed for LSP tunnels using sub-pools: 0 bits/sec
     Set aside by policy (total): 0 bits/sec
   Admission Control:
     Header Compression methods supported:
       rtp (36 bytes-saved), udp (20 bytes-saved)
     Tunnel IP Overhead percent:
       4
     Tunnel Bandwidth considered:
       Yes
   Traffic Control:
     RSVP Data Packet Classification is ON via CEF callbacks
   Signalling:
     DSCP value used in RSVP msgs: 0x3F
     Number of refresh intervals to enforce blockade state: 4
   Authentication: disabled
     Key chain:   <none>
     Type:        md5
     Window size: 1
     Challenge:   disabled 
   Hello Extension:
     State: Disabled

The table below describes the significant fields shown in the display.

Table 38. show ip rsvp interface detail Field Descriptions
Field	Description
RSVP	Status of the Resource Reservation Protocol (RSVP) (Enabled or Disabled).
Interface State	Status of the interface (Up or Down).
Curr allocated	Amount of bandwidth (in bits per second [b/s]) currently allocated.
Max. allowed (total)	Total maximum amount of bandwidth (in b/s) allowed.
Max. allowed (per flow)	Maximum amount of bandwidth (in b/s) allowed per flow.
Max. allowed for LSP tunnels using sub-pools	Maximum amount of bandwidth permitted for the label switched path (LSP) tunnels that obtain their bandwidth from subpools.
Tunnel IP Overhead percent	Overhead percent to override the RSVP bandwidth manually.
Tunnel Bandwidth considered	Indicates if the tunnel bandwidth is considered.
DSCP value used in RSVP msgs	Differentiated services code point (DSCP) value in the RSVP messages.

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 EXEC 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) Displays information about a specified VRF.

udp

(Optional) User Datagram Protocol (UDP) to be used on the receiving interface and the UDP source port number.

tcp

(Optional) 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 the protocol argument, the range is from 0 to 255 and the protocol used 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.
Cisco IOS XE Release 2.6	This command was integrated into Cisco IOS XE Release 2.6.

Usage Guidelines

Note

The syntax of the command depends on your platform and release. The vrf and * keywords and vrf-name argument are not supported on ASR 1000 Series Aggregation Services Routers.

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
VRF : myvrf1

To Protocol DPort Description Action OutIf

10.0.2.1 any any RSVP Proxy reply

The table below describes the significant fields shown in the display.

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

Results

Chapter: show ip rsvp hello client lsp summary through show lane qos database

show ip rsvp hello client lsp summary through show lane qos database

show ip rsvp hello client lsp summary

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp hello client nbr detail

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp hello client neighbor detail

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp hello client neighbor summary

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp hello graceful-restart

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp hello instance detail

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp hello instance summary

Syntax Description

Command Modes

Command History

Examples

Related Commands

show ip rsvp hello statistics

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp high-availability counters

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

show ip rsvp high-availability database

Syntax Description

Command Modes

Command History

Usage Guidelines

Examples

Examples

Examples

Examples

Examples

Examples

Examples

Examples