To display Resource Reservation Protocol (RSVP) PATH-related sender information currently in the database, use the showiprsvpsendercommand in user EXEC or privileged EXEC mode.
Syntax for Cisco IOS Release T, 12.2S, 12.2SB, 12.2(33)SRD, Cisco IOS XE Release 2.6 and, Earlier Releases
show
ip
rsvp
sender [
detail]
[
filter
[
destination
address
]
[
dst-port
port-number
]
[
source
address
]
[
src-port
port-number
]
]
[
vrf
{
* |
vrf-name
}
]
Syntax for Cisco IOS Release 12.2(33)SRE with Filtering Session Type all
show
ip
rsvp
sender [
detail]
[
filter
[
session-type
all
]
]
Syntax for Cisco IOS Release 12.2(33)SRE with Filtering Session Type 1
show
ip
rsvp
sender [
detail]
[
filter
[
session-type
session-type-number
]
]
[
destination
address
]
[
dst-port
port-number
]
[
source
address
]
[
src-port
port-number
]
Syntax for Cisco IOS Release 12.2(33)SRE with Filtering Session Type 7 or 13
show
ip
rsvp
sender [
detail]
[
filter
[
session-type
session-type-number
]
]
[
destination
address
]
[
lsp-id
lsp-id
]
[
sender
address
]
[
tunnel-id
tunnel-id
]
Syntax Description
detail |
(Optional) Specifies additional sender information. |
filter |
(Optional) Specifies a subset of the senders to display . |
destination address |
(Optional) Specifies the hostname of IP address of the destination of the sender. |
dst-port port-number |
(Optional) Specifies the destination port number. The range is from 0 to 65535. |
source address |
(Optional) Specifies the hostname or the IP address of the source of the sender. |
src-port port-number |
(Optional) Specifies the source port number. The range is from 0 to 65535. |
vrf * |
(Optional) Displays all the configured virtual routing and forwarding (VRF) instances. |
vrf-name |
(Optional) Name of a specified VRF. |
session-type session-type-number |
(Optional) Specifies the type of RSVP sessions to display. Valid values are:
-
1 for IPv4 sessions.
-
7 for IPv4 point-to-point (P2P) traffic engineering (TE) label switched path (LSP) tunnel sessions.
-
13 for IPv4 point-to-multipoint (P2MP) TE LSP tunnel sessions.
|
all |
(Optional) Specifies all types of RSVP sessions. |
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release |
Modification |
11.2 |
This command was introduced. |
12.0(22)S |
The command output was modified to display Fast Reroute information, and support was introduced for the Cisco 10000 series Edge Services Router (ESR). |
12.2(18)SXD1 |
This command was integrated into Cisco IOS Release 12.2(18)SXD1. |
12.4(4)T |
The command output was modified to display application ID information. |
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)SRB |
The command output was modified to display fast local repair (FLR) information. |
12.2(33)SRC |
The command output was modified to display tunnel-based admission control (TBAC) and RSVP aggregation information. |
15.0(1)M |
This command was modified. The vrfand*keywords and the vrf-name argument were added. |
12.2(33)SRE |
This command was modified. The session-type keyword was added to display specific types of tunnels. The output was modified to display MPLS TE P2MP information. |
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 vrfand * keywords and vrf-nameargument are not supported on ASR 1000 Series Aggregaton Services Routers.
|
Use the showiprsvpsender command to display the RSVP sender (PATH) information currently in the database for a specified interface or for all interfaces.
The showiprsvpsendercommandis useful for determining the state of RSVP signaling both before and after a label switched path (LSP) has been fast rerouted. The showiprsvpsendercommand is especially useful when used at the point of local repair (PLR) or at the merge point (MP).
Limiting the Display
When hundreds or thousands of tunnels exist and you are interested in only a few, you can display the output for only a single tunnel or a subset of tunnels. To request a limited display, enter the showiprsvpsender command with the appropriate keyword (called an output filter): destination, dst-port, source, and src-port. You can enter any or all of the output filters, and you can enter them whether or not you specify the detail keyword.
FLR Statistics
Use the showiprsvpsenderdetail command to display FLR statistics before, during, and after an FLR procedure. This command shows when a path state block (PSB) was repaired and can be used to determine when the cleanup began after the FLR procedure has finished. However, this command does not display old PLR or MP segments.
show ip rsvp sender Example
The following is sample output from the showiprsvpsender command:
Router# show ip rsvp sender
To From Pro DPort Sport Prev Hop I/F BPS
172.16.1.49 172.16.4.53 1 0 0 172.16.3.53 Et1 80K
172.16.2.51 172.16.5.54 1 0 0 172.16.3.54 Et1 80K
192.168.50.1 192.168.40.1 0 46 0 none none 17179868160
The tabel below describes the significant fields shown in the display.
Table 60 |
show ip rsvp sender Field Descriptions |
Field |
Description |
To |
IP address of the receiver. |
From |
IP address of the sender. |
Pro |
Protocol code.
-
Code 1 indicates an IP protocol such as TCP or User Datagram Protocol (UDP).
-
Code 0 indicates an aggregate reservation.
|
DPort |
Destination port number.
-
The Differentiated Services Code Point (DSCP) for an aggregate reservation.
|
Sport |
Source port number.
-
0 for an aggregate reservation.
|
Prev Hop |
IP address of the previous hop.
-
None if the node is an aggregator for this reservation.
|
I/F |
Interface of the previous hop.
-
None if the node is an aggregator for this reservation.
|
BPS |
As specified in the sender_tspec characteristics of the sender data flow--specified bit rate, in bits per second.
-
Always 17179868160 for an aggregate reservation.
|
Application ID Example
The following is sample output from the showiprsvpsenderdetailcommand with application IDs configured:
Router# show ip rsvp sender detail
PATH Session address: 192.168.104.3, port: 4444. Protocol: UDP
Sender address: 192.168.104.1, port: 4444
Inbound from: 192.168.104.1 on interface:
Traffic params - Rate: 5K bits/sec, Max. burst: 1K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytes
Path ID handle: 09000408.
Incoming policy: Accepted. Policy source(s): Default
Priorities - preempt: 5, defend: 2
Application ID: 'GUID=www.cisco.com, VER=10.1.1.2, APP=voice, SAPP=h323'
'/usr/local/bin/CallManager'
Status: Proxied
Output on ATM1/0.1. Policy status: Forwarding. Handle: 04000409
Policy source(s): Default
The table below describes the significant fields shown in the display.
Table 61 |
show ip rsvp sender detail Field Descriptions |
Field |
Descriptions |
PATH Session address |
Destination IP address of the PATH message.
-
port--Number of the destination port.
-
Protocol--IP protocol used.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Inbound from |
IP address of the sender and the interface name.
Note |
A blank interface field means that the PATH message originated at the router on which the show command is being executed (the headend router). A specified interface means that the PATH message originated at an upstream router. |
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values include Default, Local, and MPLS/TE. |
Priorities |
Preemption priorities in effect:
-
preempt--The startup priority; values are 0 to 7 for traffic engineering (TE) reservations with 0 being the highest. Values are 0 to 65535 for non-TE reservations with 0 being the lowest.
-
defend--The hold priority; values are the same as for preempt.
|
Application ID |
A quotable string that identifies the sender application and can be used to match on local policies. The string includes the policy locator in the X.500 Distinguished Name format and the application or filename of the sender application. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message has recently been received; therefore, the PSB enters the blockaded state.
|
Output on ATM1/0/1 |
Policy status (on the outbound interface):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Before FLR Example
The following is sample output from the showiprsvpsenderdetail command before FLR has occurred:
Router# show ip rsvp sender detail
PATH:
Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1
Sender address: 10.10.10.10, port: 1
Path refreshes:
arriving: from PHOP 172.16.31.34 on Et0/0 every 30000 msecs
Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 01000401.
Incoming policy: Accepted. Policy source(s): Default
Status:
Output on Ethernet1/0. Policy status: Forwarding. Handle: 02000400
Policy source(s): Default
Path FLR: Never repaired
The table below describes the significant fields shown in the display.
Table 62 |
show ip rsvp sender detail Field Descriptions--Before FLR |
Field |
Descriptions |
PATH |
PATH message information:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the path state block (PSB) enters the blockaded state.
Note |
A blank field means none of the above. |
|
Output on interface |
Policy status (on the outbound interface):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Path FLR |
Never repaired--Indicates that the node has never been a point of local repair (PLR) and, therefore, has never repaired the PSB. |
At the PLR During FLR Example
Note |
A node that initiates an FLR procedure is the point of local repair or PLR.
|
The following is sample output from the showiprsvpsenderdetail command at the PLR during an FLR procedure:
Router# show ip rsvp sender detail
PATH:
Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1
Sender address: 10.10.10.10, port: 1
Path refreshes:
arriving: from PHOP 172.16.31.34 on Et0/0 every 30000 msecs
Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 01000401.
Incoming policy: Accepted. Policy source(s): Default
Status:
Path FLR: PSB is currently being repaired...try later
PLR - Old Segments: 1
Output on Ethernet1/0, nhop 172.16.36.34
Time before expiry: 2 refreshes
Policy status: Forwarding. Handle: 02000400
Policy source(s): Default
The table below describes the significant fields shown in the display.
Table 63 |
show ip rsvp sender detail Field Descriptions--at the PLR During FLR |
Field |
Descriptions |
PATH |
PATH message information including the following:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the PSB enters the blockaded state.
Note |
A blank field means none of the above. |
|
Path FLR |
PSB is currently being repaired. FLR is in process. |
PLR - Old Segments |
The number of old segments or interfaces after the PLR initiated the FLR procedure. For each old segment, the following information displays:
-
Output on interface--Outbound interface after the FLR and the next-hop IP address.
-
Time before expiry--Number of PATH messages sent on a new segment before the old route (segment) expires.
-
Policy status (on the outbound interface):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
-
Policy source(s)--Type of local policy in effect; values are Default, Local, and MPLS/TE.
|
At the MP During an FLR Example
Note |
The node where the old and new paths (also called segments or interfaces) meet is the merge point (MP).
|
The following is sample output from the showiprsvpsenderdetail command at the MP during an FLR procedure:
Router# show ip rsvp sender detail
PATH:
Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1
Sender address: 10.10.10.10, port: 1
Path refreshes:
arriving: from PHOP 172.16.37.35 on Et1/0 every 30000 msecs
Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 09000406.
Incoming policy: Accepted. Policy source(s): Default
Status: Proxy-terminated
Path FLR: Never repaired
MP - Old Segments: 1
Input on Serial2/0, phop 172.16.36.35
Time before expiry: 9 refreshes
The table below describes the significant fields shown in the display.
Table 64 |
show ip rsvp sender detail Field Descriptions--at the MP During FLR |
Field |
Descriptions |
PATH |
PATH message information:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the PSB enters the blockaded state.
Note |
A blank field means none of the above. |
|
Path FLR |
Never repaired--Indicates that the node has never been a PLR and, therefore, has never repaired the PSB. |
MP - Old Segments |
The number of old segments or interfaces on the MP before the PLR initiated the FLR procedure. For each old segment,the following information displays:
-
Input on interface--Inbound interface and the previous-hop IP address.
-
Time before expiry--Number of PATH messages to be received on other segments before this segment expires.
|
At the PLR After an FLR Example
The following is sample output from the showiprsvpsenderdetail command at the PLR after an FLR procedure:
Router# show ip rsvp sender detail
PATH:
Destination 192.168.101.21, Protocol_Id 17, Don't Police , DstPort 1
Sender address: 10.10.10.10, port: 1
Path refreshes:
arriving: from PHOP 172.16.31.34 on Et0/0 every 30000 msecs
Traffic params - Rate: 9K bits/sec, Max. burst: 9K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 05000401.
Incoming policy: Accepted. Policy source(s): Default
Status:
Output on Serial3/0. Policy status: Forwarding. Handle: 3B000406
Policy source(s): Default
Path FLR: Started 12:56:16 EST Thu Nov 16 2006, PSB repaired 532(ms) after.
Resv/Perr: Received 992(ms) after.
The table below describes the significant fields shown in the display.
Table 65 |
show ip rsvp sender detail Field Descriptions--At the PLR After FLR |
Field |
Descriptions |
PATH |
PATH message information including the following:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information including the following:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
Path ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the PSB enters the blockaded state.
Note |
A blank field means none of the above. |
|
Output on Serial3/0 |
Policy status (on the outbound interface):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Path FLR |
FLR statistics that show when RSVP received the notification from RIB and how long thereafter the PATH message was sent. This delay can result when the interface on which the PATH message was sent had a wait time configured or when other PSBs were processed before this one or a combination of both. The statistics also show when an associated RESV or PATHERROR message was received.
Note |
This delay tells you the time when Quality of Service (QoS) was not honored for the specified flow. |
|
TBAC Example
The following is sample output from the showiprsvpsenderdetail command when TBAC is configured:
Router# show ip rsvp sender detail
PATH:
Destination 10.0.0.3, Protocol_Id 17, Don't Police , DstPort 2
Sender address: 10.0.0.1, port: 2
Path refreshes:
arriving: from PHOP 10.1.1.1 on Et0/0 every 30000 msecs. Timeout in 189 sec
Traffic params - Rate: 10K bits/sec, Max. burst: 10K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 02000412.
Incoming policy: Accepted. Policy source(s): Default
Status:
Output on Tunnel1, out of band. Policy status: Forwarding. Handle: 0800040E
Policy source(s): Default
Path FLR: Never repaired
The table below describes the significant fields shown in the display.
Table 66 |
show ip rsvp sender detail Field Descriptions--With TBAC |
Field |
Descriptions |
PATH |
PATH message information:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
Note |
A blank field means no refreshes have occurred. |
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the PSB enters the blockaded state.
Note |
A blank field means none of the above. |
|
Output on Tunnel1 |
Policy status (on the outbound tunnel with out-of-band signaling):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Path FLR |
Never repaired--Indicates that the node has never been a point of local repair (PLR) and, therefore, has never repaired the PSB. |
RSVP Aggregation Example
The following is sample output from the showiprsvpsenderdetail command when RSVP aggregation is configured:
Router# show ip rsvp sender detail
PATH:
Destination 10.10.10.21, Protocol_Id 17, Don't Police , DstPort 1
Sender address: 10.10.10.11, port: 1
Path refreshes:
arriving: from PHOP 10.10.10.34 on Et1/0 every 30000 msecs
Traffic params - Rate: 10K bits/sec, Max. burst: 10K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 0F000406.
Incoming policy: Accepted. Policy source(s): Default
Status:
3175 Aggregation: agg_info : AggResv 10.10.10.34->10.10.10.2_46
Output on Serial2/0. Policy status: Forwarding. Handle: 09000405
Policy source(s): Default
Path FLR: Never repaired
PATH:
Deaggregator 10.10.10.2, DSCP 46, Don't Police
Aggregator address: 10.10.10.34
Path refreshes:
arriving: from PHOP 192.168.34.36 on Et1/0 every 30000 msecs
Traffic params - Rate: 17179868160 bits/sec, Max. burst: 536870784 bytes
Min Policed Unit: 1 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 1500040A.
Incoming policy: Accepted. Policy source(s): Default
Status: Proxy-terminated
Path FLR: Never repaired
The table below describes the significant fields shown in the display.
Table 67 |
show ip rsvp sender detail Field Descriptions--With RSVP Aggregation |
Field |
Descriptions |
PATH |
PATH message information for E2E reservations:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
Note |
A blank field means no refreshes have occurred. |
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Always MAX rate possible for aggregate reservations.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Always MAX burst possible for aggregate reservations.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the PSB enters the blockaded state.
Note |
A blank field means none of the above. |
|
3175 Aggregation: agg_info |
IP address of the aggregated reservation on which this E2E reservation is mapped with specified source (aggregator) and destination (deaggregator) endpoints and DSCP. |
Output on Serial2/0 |
Policy status (on the outbound interface):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Path FLR |
Never repaired--Indicates that the node has never been a point of local repair (PLR) and, therefore, has never repaired the PSB. |
PATH |
PATH message information for aggregate reservations:
-
Deaggregator IP address.
-
Differentiated Services Code Point (DSCP) value.
-
Policing.
-
Aggregator IP address.
Note |
Remaining parameters are defined in the preceding fields. |
|
PLR and MP Examples
The following is sample output from the showiprsvpsenderdetail command under these circumstances:
-
The command is entered at the PLR before a failure (Example 1).
-
The command is entered at the PLR after a failure (Example 2).
-
The command is entered at the MP before a failure (Example 3).
-
The command is entered at the MP after a failure (Example 4).
-
The command output shows all senders (Example 5).
-
The command output shows only senders who have a specific destination (Example 6).
-
The command output shows more detail about a sender who has a specific destination (Example 7).
This figure illustrates the network topology for the RSVP configuration example.
Figure 15 |
Network Topology for the RSVP Configuration Example |
Example 1: The Command is entered at the PLR before a failure
The following is sample output from the showiprsvpsenderdetail command when it is entered at the PLR before a failure:
Router# show ip rsvp sender detail
PATH:
Tun Dest: 10.2.2.1 Tun ID: 1 Ext Tun ID: 10.2.2.0
Tun Sender: 10.2.2.0, LSP ID: 126
Path refreshes arriving on POS1/0 from PHOP 10.1.1.1
Path refreshes being sent to NHOP 10.1.1.4 on POS1/1
Session Attr::
Setup Prio: 0, Holding Prio: 0
Flags: Local Prot desired, Label Recording, SE Style
Session Name:tagsw4500-23_t1
ERO:
10.1.1.4 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.5 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.6 (Strict IPv4 Prefix, 8 bytes, /32)
10.2.2.1 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 0G bits/sec, Max. burst: 1K bytes
Fast-Reroute Backup info:
Inbound FRR: Not active
Outbound FRR: Ready -- backup tunnel selected
Backup Tunnel: Tu2 (label 0)
Bkup Sender Template:
Tun Sender: 10.0.0.0, LSP ID: 126
Bkup FilerSpec:
Tun Sender: 10.0.0.0, LSP ID 126
The table below describes the significant fields shown in the display.
Note |
The Flags field is important for Fast Reroute. For information about flags that must be set, see the Flags field description in the table.
|
Table 68 |
show ip rsvp sender detail Field Descriptions--On PLR Before Failure |
Field |
Description |
The first five fields provide information that uniquely identifies the LSP. The first three fields identify the LSP's session (that is, the contents of the SESSION object in arriving PATH messages). |
Tun Dest |
IP address of the destination of the tunnel. |
Tun ID |
Tunnel identification number. |
Ext Tun ID |
Extended tunnel identification number. |
The next two fields identify the LSP's sender (SENDER_TEMPLATE object of arriving PATH messages). |
Tun Sender |
Tunnel sender. |
LSP ID |
LSP identification number. |
The remaining fields indented under PATH provide additional information about this LSP. |
Session Attr --Session attributes. Refers to information included in the SESSION_ATTRIBUTE object of arriving PATH messages, such as the Setup and Holding Priorities, Flags, and the Session Name. |
Setup Prio |
Setup priority. |
Holding Prio |
Holding priority. |
Flags |
An LSP must have the "Local protection desired" flag of the SESSION_ATTRIBUTE object set for the LSP to use a backup tunnel (that is, in order to receive local protection). If this flag is not set, you have not enabled Fast Reroute for this tunnel at its headend (by entering the tunnelmplstraffic-engfast-reroute command). Next-next hop (NNHOP) backup tunnels rely on label recording, so LSPs should have the "label recording desired" flag set too. This flag is set if the tunnel was configured for Fast Reroute. |
ERO --Refers to the EXPLICIT_ROUTE Object (ERO) of the PATH messages. This field displays the contents of the ERO at this node. As a PATH message travels from the sender (headend) to the receiver (tailend), each node removes its own IP address from the ERO. The displayed value reflects the remainder of hops between this node and the tail. |
Fast-Reroute Backup info --Information that is relevant to Fast Reroute for this LSP. |
Inbound FRR |
If this node is downstream from a rerouted LSP (for example, at a merge point for this LSP), the state is Active. |
Outbound FRR |
If this node is a PLR for an LSP, there are three possible states:
-
Active--This LSP is actively using its backup tunnel, presumably because there has been a downstream failure.
-
No Backup--This LSP does not have local (Fast Reroute) protection. No backup tunnel has been selected for it to use in case of a failure.
-
Ready--This LSP is ready to use a backup tunnel in case of a downstream link or node failure. A backup tunnel has been selected for it to use.
|
Backup Tunnel |
If the Outbound FRR state is Ready or Active, this field indicates the following:
-
Which backup tunnel has been selected for this LSP to use in case of a failure.
-
The inbound label that will be prepended to the LSP's data packets for acceptance at the backup tunnel tail (the merge point).
|
Bkup Sender Template |
If the Outbound FRR state is Ready or Active, SENDER_TEMPLATE and FILTERSPEC objects are shown. These objects will be used in RSVP messages sent by the backup tunnel if the LSP starts actively using the backup tunnel. They differ from the original (prefailure) objects only in that the node (the PLR) substitutes its own IP address for that of the original sender. For example, PATH and PATHTEAR messages will contain the new SENDER_TEMPLATE. RESV and RESVTEAR messages will contain the new FILTERSPEC object. If this LSP begins actively using the backup tunnel, the display changes. |
Bkup FilerSpec |
If the Outbound FRR state is Ready or Active, SENDER_TEMPLATE and FILTERSPEC objects are shown. These objects will be used in RSVP messages sent by the backup tunnel if the LSP starts actively using the backup tunnel. They differ from the original (prefailure) objects only in that the node (the PLR) substitutes its own IP address for that of the original sender. For example, PATH and PATHTEAR messages will contain the new SENDER_TEMPLATE. RESV and RESVTEAR messages will contain the new FILTERSPEC object. If this LSP begins actively using the backup tunnel, the display changes as shown in Example 2. |
Example 2: The command is entered at the PLR after a failure
If the LSP begins actively using the backup tunnel and the command is entered at the PLR after a failure, the display changes as shown in the following output.
Router# show ip rsvp sender detail
PATH:
Tun Dest: 10.2.2.1 Tun ID: 1 Ext Tun ID: 10.2.2.0
Tun Sender: 10.2.2.0, LSP ID: 126
Path refreshes arriving on POS1/0 from PHOP 10.1.1.1
Path refreshes being sent to NHOP 10.2.2.1 on Tunnel2
Session Attr::
Setup Prio: 0, Holding Prio: 0
Flags: Local Prot desired, Label Recording, SE Style
Session Name:tagsw4500-23_t1
ERO:
10.2.2.1 (Strict IPv4 Prefix, 8 bytes, /32)
10.2.2.1 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 0G bits/sec, Max. burst: 1K bytes
Fast-Reroute Backup info:
Inbound FRR: Not active
Outbound FRR: Active -- using backup tunnel
Backup Tunnel: Tu2 (label 0)
Bkup Sender Template:
Tun Sender: 10.0.0.0, LSP ID: 126
Bkup FilerSpec:
Tun Sender: 10.0.0.0, LSP ID 126
Orig Output I/F: Et2
Orig Output ERO:
10.1.1.4 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.5 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.6 (Strict IPv4 Prefix, 8 bytes, /32)
10.2.2.1 (Strict IPv4 Prefix, 8 bytes, /32)
Once an LSP is actively using a backup tunnel, the following changes occur:
-
PATH refreshes are no longer sent to the original NHOP out the original interface. They are sent through the backup tunnel to the node that is the tail of the backup tunnel (NHOP or NNHOP).
-
The ERO is modified so that it will be acceptable upon arrival at the NHOP or NNHOP.
-
The display shows both the original ERO and the new one that is now being used.
-
The display shows the original output interface (that is, the interface from which PATH messages were sent for this LSP before the failure).
Example 3: The command is entered at the MP before a failure
If the same showiprsvpsender command is entered at the merge point (the backup tunnel tail), the display changes from before to after the failure. The following is sample output before a failure:
Router# show ip rsvp sender detail
PATH:
Tun Dest: 10.2.2.1 Tun ID: 1 Ext Tun ID: 10.2.2.0
Tun Sender: 10.2.2.0, LSP ID: 126
Path refreshes arriving on POS0/0 from PHOP 10.1.1.5
Session Attr::
Setup Prio: 0, Holding Prio: 0
Flags: Local Prot desired, Label Recording, SE Style
Session Name:tagsw4500-23_t1
Traffic params - Rate: 0G bits/sec, Max. burst: 1K bytes
Fast-Reroute Backup info:
Inbound FRR: Not active
Outbound FRR: No backup tunnel selected
Example 4: The command is entered at the MP after a failure
After a failure, the following changes occur:
-
The interface and previous hop (PHOP) from which PATH messages are received will change.
-
The inbound FRR becomes Active.
-
The original PHOP and the original input interface are displayed as shown in the following output.
The following is sample output after a failure:
Router# show ip rsvp sender detail
PATH:
Tun Dest: 10.2.2.1 Tun ID: 1 Ext Tun ID: 10.2.2.0
Tun Sender: 10.2.2.0, LSP ID: 126
Path refreshes arriving on POS0/1 from PHOP 10.0.0.0 on Loopback0
Session Attr::
Setup Prio: 0, Holding Prio: 0
Flags: Local Prot desired, Label Recording, SE Style
Session Name:tagsw4500-23_t1
Traffic params - Rate: 0G bits/sec, Max. burst: 1K bytes
Fast-Reroute Backup info:
Inbound FRR: Active
Orig Input I/F: POS0/0
Orig PHOP: 10.1.1.5
Now using Bkup Filterspec w/ sender: 10.0.0.0 LSP ID: 126
Outbound FRR: No backup tunnel selected
Notice the following changes:
-
After a failure, PATH refreshes arrive on a different interface and from a different PHOP.
-
The original PHOP and input interface are shown under Fast-Reroute Backup information, along with the FILTERSPEC object that will now be used when sending messages (such as RESV and RESVTEAR).
Example 5: The command output shows all senders
In the following example, information about all senders is displayed:
Router# show ip rsvp sender
To From Pro DPort Sport Prev Hop I/F BPS Bytes
10.2.2.1 10.2.2.0 1 1 59 10.1.1.1 Et1 0G 1K
10.2.2.1 172.31.255.255 1 2 9 0G 1K
10.2.2.1 10.2.2.0 1 3 12 10.1.1.1 Et1 0G 1K
10.2.2.1 172.31.255.255 1 3 20 0G 1K
172.16.0.0 172.31.255.255 1 0 23 0G 1K
172.16.0.0 172.31.255.255 1 1 22 0G 1K
172.16.0.0 172.31.255.255 1 1000 22 0G 1K
The table below describes the significant fields shown in the display.
Table 69 |
show ip rsvp sender Field Descriptions |
Field |
Description |
To |
IP address of the receiver. |
From |
IP address of the sender. |
Pro |
Protocol code. Code 1 indicates Internet Control Message Protocol (ICMP). |
DPort |
Destination port number. |
Sport |
Source port number. |
Prev Hop |
IP address of the previous hop. |
I/F |
Interface of the previous hop. |
BPS |
Reservation rate, in bits per second, that the application is advertising it might achieve. |
Bytes |
Bytes of burst size that the application is advertising it might achieve. |
Example 6: The command output shows only senders having a specific destination
To show only information about senders having a specific destination, specify the destination filter as shown in the following output. In this example, the destination is 172.16.0.0.
Router# show ip rsvp sender filter destination 172.16.0.0
To From Pro DPort Sport Prev Hop I/F BPS Bytes
172.16.0.0 172.31.255 1 0 23 0G 1K
172.16.0.0 172.31.255 1 1 22 0G 1K
172.16.0.0 172.31.255 1 1000 22 0G 1K
Example 7: Show more detail about a sender having a specific destination
To show more detail about the sender whose destination port is 1000 (as shown in Example 6), specify the command with the destination port filter:
Router# show ip rsvp sender filter detail dst-port 1000
PATH:
Tun Dest 172.16.0.0 Tun ID 1000 Ext Tun ID 172.31.255.255
Tun Sender: 172.31.255.255, LSP ID: 22
Path refreshes being sent to NHOP 10.1.1.4 on Ethernet2
Session Attr::
Setup Prio: 7, Holding Prio: 7
Flags: SE Style
Session Name:tagsw4500-25_t1000
ERO:
10.1.1.4 (Strict IPv4 Prefix, 8 bytes, /32)
172.16.0.0 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 0G bits/sec, Max. burst: 1K bytes
Fast-Reroute Backup info:
Inbound FRR: Not active
Outbound FRR: No backup tunnel selected
VRF Example
The following is sample output from the showiprsvpsendervrfmyvrfdetail command showing all the senders associated with the VRF named myvrf:
Router# show ip rsvp sender detail vrf myvrf
PATH:
Destination 10.10.10.21, Protocol_Id 17, Don't Police , DstPort 1
Sender address: 10.10.10.11, port: 1
Path refreshes:
Traffic params - Rate: 10K bits/sec, Max. burst: 10K bytes
Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
Path ID handle: 0F000406.
Incoming policy: Accepted. Policy source(s): Default
Status: Proxied
Output on Serial2/0. Policy status: Forwarding. Handle: 09000405
Policy source(s): Default
Path FLR: Never repaired
VRF: myvrf
The table below describes the significant fields shown in the display.
Table 70 |
show ip rsvp sender detail Field Descriptions--With VRF |
Field |
Descriptions |
PATH |
PATH message information for E2E reservations:
-
Destination IP address.
-
Protocol ID number.
-
Policing.
-
Destination port number.
|
Sender address |
Source IP address of the PATH message.
-
port--Number of the source port.
|
Path refreshes |
Refresh information:
-
IP address of the source (previous hop [PHOP]).
-
Interface name and number.
-
Frequency, in milliseconds (ms).
Note |
A blank field means no refreshes have occurred. |
|
Traffic params |
Traffic parameters in effect:
-
Rate--Speed, in kilobits per second.
-
Always MAX rate possible for aggregate reservations.
-
Max. burst--Largest amount of data allowed, in kilobytes.
-
Always MAX burst possible for aggregate reservations.
-
Min Policed Unit--Size, in bytes, of the smallest packet generated by the application, including the application data and all protocol headers at or above the IP level.
-
Max Pkt Size--Largest packet allowed, in bytes.
|
PATH ID handle |
Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes. |
Incoming policy |
State of the incoming policy:
-
Accepted--RSVP PATH messages are being accepted, but not forwarded.
-
Not Accepted--RSVP PATH messages are being rejected.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Status |
Status of the local policy:
-
Proxied--Head.
-
Proxy-terminated--Tail.
-
Blockaded--Tail or midpoint and an RESVERROR message have recently been received; therefore, the PSB enters the blockaded state.
Note |
A blank field means none of the above. |
|
Output on Serial2/0 |
Policy status (on the outbound interface):
-
Forwarding--Inbound PATH messages are being forwarded.
-
Not Forwarding--Outbound PATH messages are being rejected.
-
Handle--Internal database ID assigned to the PATH message by RSVP for bookkeeping purposes.
|
Policy source(s) |
Type of local policy in effect; values are Default, Local, and MPLS/TE. |
Path FLR |
Never repaired--Indicates that the node has never been a point of local repair (PLR) and, therefore, has never repaired the PSB. |
VRF |
Name of the VRF for which senders are displayed. |
MPLS Traffic Engineering Point-to-Multipoint Examples
The following is sample output from the showiprsvpsenderdetailcommand showing point-to-multipoint information:
Router# show ip rsvp sender detail
P2MP ID: 22 Tun ID: 22 Ext Tun ID: 10.1.1.201
Tun Sender: 10.1.1.201 LSP ID: 1 SubGroup Orig: 10.1.1.201
SubGroup ID: 1
S2L Destination : 10.1.1.203
Path refreshes:
sent: to NHOP 10.0.0.205 on Ethernet0/0
Session Attr:
Setup Prio: 7, Holding Prio: 7
Flags: (0xF) Local Prot desired, Label Recording, SE Style, Bandwidth Prot desired
Session Name: R201_t22
ERO: (incoming)
10.1.1.201 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.201 (Strict IPv4 Prefix, 8 bytes, /32)
10.0.0.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.202 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.202 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.203 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.203 (Strict IPv4 Prefix, 8 bytes, /32)
ERO: (outgoing)
10.0.0.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.205 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.202 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.202 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.0.203 (Strict IPv4 Prefix, 8 bytes, /32)
10.1.1.203 (Strict IPv4 Prefix, 8 bytes, /32)
Traffic params - Rate: 500K bits/sec, Max. burst: 1K bytes
Min Policed Unit: 1 bytes, Max Pkt Size 2147483647 bytes
Fast-Reroute Backup info:
Inbound FRR: Not active
Outbound FRR: Ready -- backup tunnel selected
Backup Tunnel: Tu666 (label 20)
Bkup Sender Template:
Tun Sender: 10.0.2.201 LSP ID: 1 SubGroup Orig: 10.1.1.201
SubGroup ID: 1
Bkup FilerSpec:
Tun Sender: 10.0.2.201, LSP ID: 1, SubGroup Orig: 10.1.1.201
SubGroup ID: 1
Path ID handle: 01000414.
Incoming policy: Accepted. Policy source(s): MPLS/TE
Status: Proxied
Output on Ethernet0/0. Policy status: Forwarding. Handle: 02000413
Policy source(s): MPLS/TE
The table below describes the significant fields shown in the display.
Table 71 |
show ip rsvp sender--MPLS TE P2MP Field Descriptions |
Field |
Description |
P2MP ID |
A 32-bit number that identifies the set of destinations of the P2MP tunnel. |
Tun ID |
Tunnel identification number. |
Ext Tun ID |
Extended tunnel identification number. |
Tun Sender |
IP address of the sender. |
LSP ID |
Label switched path identification number. |
SubGroup Orig |
LSP headend router ID address. |
SubGroup ID |
An incremental number assigned to each sub-LSP signaled from the headend router. |
S2L Destination |
LSP tailend router ID address. |
The following is sample output from the showiprsvpsenderfiltersession-type13command, which shows RSVP RESV requests for point-to-multipoint traffic:
Router# show ip rsvp sender filter session-type 13
Session Type 13 (te-p2mp-lsp)
Destination Tun Sender TunID LSPID P2MP-ID SubID I/F BPS
10.1.1.203 10.1.1.201 22 1 22 1 none 500K
10.1.1.206 10.1.1.201 22 1 22 2 none 500K
10.1.1.213 10.1.1.201 22 1 22 3 none 500K
10.1.1.214 10.1.1.201 22 1 22 4 none 500K
10.1.1.216 10.1.1.201 22 1 22 5 none 500K
10.1.1.217 10.1.1.201 22 1 22 6 none 500K
Related Commands
Command |
Description |
ip rsvp sender |
Enables a router to simulate RSVP PATH message reception from the sender. |
show ip rsvp reservation |
Displays RSVP PATH-related receiver information currently in the database. |