Table Of Contents
show ip nbar port-map
show ip nbar protocol-discovery
show ip rsvp
show ip rsvp atm-peak-rate-limit
show ip rsvp counters
show ip rsvp installed
show ip rsvp interface
show ip rsvp listeners
show ip rsvp neighbor
show ip rsvp policy
show ip rsvp policy cops
show ip rsvp policy local
show ip rsvp request
show ip rsvp reservation
show ip rsvp sbm
show ip rsvp sender
show ip rsvp signalling
show ip rsvp signalling blockade
show ip rsvp signalling rate-limit
show ip rsvp signalling refresh reduction
show ip rtp header-compression
show policy-map
show policy-map class
show policy-map interface
show qdm status
show ip nbar port-map
To display the current protocol-to-port mappings in use by network-based application recognition (NBAR), use the show ip nbar port-map command in privileged EXEC mode.
show ip nbar port-map [protocol-name]
Syntax Description
protocol-name
|
(Optional) Limits the command display to the specified protocol.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)XE2
|
This command was introduced.
|
12.1(1)E
|
This command was integrated into Cisco IOS Release 12.1(1)E.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
12.1(13)E
|
This command was implemented on Catalyst 6000 family switches without FlexWAN modules.
|
Usage Guidelines
The show ip nbar port-map command displays port assignments for NBAR protocols.
This command is used to display the current protocol-to-port mappings in use by NBAR. When the ip nbar port-map command has been used, the show ip nbar port-map command displays the ports assigned by the user to the protocol. If no ip nbar port-map command has been used, the show ip nbar port-map command displays the default ports. The protocol-name argument can also be used to limit the display to a specific protocol.
Examples
The following is sample output from the show ip nbar port-map command:
Router# show ip nbar port-map
port-map cuseeme udp 7648 7649
port-map cuseeme tcp 7648 7649
Related Commands
Command
|
Description
|
ip nbar-port-map
|
Configures NBAR to search for a protocol or protocol name using a port number other than the well-known port.
|
show ip nbar protocol-discovery
To display the statistics gathered by the network-based application recognition (NBAR) Protocol Discovery feature, use the show ip nbar protocol-discovery command in privileged EXEC mode.
show ip nbar protocol-discovery [interface interface-spec] [stats {byte-count | bit-rate
| packet-count}] [{protocol protocol-name | top-n number}]
Syntax Description
interface
|
(Optional) Specifies that Protocol Discovery statistics for the interface are to be displayed.
|
interface-spec
|
(Optional) Specifies an interface to display.
|
stats
|
(Optional) Specifies that the byte count, byte rate, or packet count is to be displayed.
|
byte-count
|
(Optional) Specifies that the byte count is to be displayed.
|
bit-rate
|
(Optional) Specifies that the bit rate is to be displayed.
|
packet-count
|
(Optional) Specifies that the packet count is to be displayed.
|
protocol
|
(Optional) Specifies that statistics for a specific protocol are to be displayed.
|
protocol-name
|
(Optional) User-specified protocol name for which the statistics are to be displayed.
|
top-n
|
(Optional) Specifies that a top-n is to be displayed. A top-n is the number of most active NBAR-supported protocols, where n is the number of protocols to be displayed. For instance, if top-n 3 is entered, the three most active NBAR-supported protocols will be displayed.
|
number
|
(Optional) Specifies the number of most active NBAR-supported protocols to be displayed.
|
Defaults
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(5)XE2
|
This command was introduced.
|
12.1(1)E
|
This command was integrated into Cisco IOS Release 12.1(1)E.
|
12.1(5)T
|
This command was integrated into Cisco IOS Release 12.1(5)T.
|
12.1(13)E
|
This command was implemented on Catalyst 6000 family switches without FlexWAN modules.
|
Usage Guidelines
Statistics for all interfaces on which the Protocol Discovery feature is enabled are displayed.
Use the show ip nbar protocol-discovery command to display statistics gathered by the NBAR Protocol Discovery feature. This command, by default, displays statistics for all interfaces on which protocol discovery is currently enabled. The default output of this command includes, in the following order, input bit rate (in bits per second), input byte count, input packet count, and protocol name.
Protocol discovery can be used to monitor both input and output traffic and may be applied with or without a service policy enabled. NBAR protocol discovery gathers statistics for packets switched to output interfaces. These statistics are not necessarily for packets that exited the router on the output interfaces, because packets may have been dropped after switching for various reasons, including policing at the output interface, access lists, or queue drops.
Examples
The following example displays partial output of the show ip nbar protocol-discovery command for an Ethernet interface:
Router# show ip nbar protocol-discovery interface Fastethernet 6/0
Protocol Packet Count Packet Count
5 minute bit rate (bps) 5 minute bit rate (bps)
------------------------ ------------------------ ------------------------
Related Commands
Command
|
Description
|
ip nbar protocol-discovery
|
Configures NBAR to discover traffic for all protocols known to NBAR on a particular interface.
|
show ip rsvp
To display specific information for Resource Reservation Protocol (RSVP) categories, use the show ip rsvp command in EXEC mode.
show ip rsvp [atm-peak-rate-limit | counters | host | installed | interface | listeners | neighbor |
policy | precedence | request | reservation | sbm | sender | signalling | tos]
Syntax Description
atm-peak-rate-limit
|
(Optional) RSVP peak rate limit.
|
counters
|
(Optional) RSVP statistics.
|
host
|
(Optional) RSVP endpoint senders and receivers.
|
installed
|
(Optional) RSVP installed reservations.
|
interface
|
(Optional) RSVP interface information.
|
listeners
|
(Optional) RSVP listeners.
|
neighbor
|
(Optional) RSVP neighbor information.
|
policy
|
(Optional) RSVP policy information.
|
precedence
|
(Optional) RSVP precedence settings.
|
request
|
(Optional) RSVP reservations upstream.
|
reservation
|
(Optional) RSVP reservation requests from downstream.
|
sender
|
(Optional) RSVP path state information.
|
sbm
|
(Optional) RSVP subnet bandwidth manager (SBM) information.
|
signalling
|
(Optional) RSVP signalling information.
|
tos
|
(Optional) RSVP type of service (TOS) settings.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
12.2(13)T
|
The listeners and policy keywords were added, and this command was modified to display RSVP global settings when no keywords or arguments are entered.
|
Examples
The following command shows RSVP rate-limiting, refresh-reduction, and neighbor information:
Interval length (msec):20
Refresh Reduction:enabled
Initial retransmit delay (msec):1000
Message IDs:in use 580, total allocated 3018, total freed 2438
RSVP encap:1 UDP encap:0 RSVP and UDP encap:0
Default policy:Accept all
Table 26 describes the fields shown in the display.
Table 26 show ip rsvp Command Field Descriptions
Field
|
Description
|
Rate Limiting: enabled (active) or disabled (not active)
|
The RSVP rate-limiting parameters in effect including the following:
• Max msgs per interval = number of messages allowed to be sent per interval (timeframe).
• Interval length (msecs) = interval (timeframe) length in milliseconds.
• Max queue size = maximum size of the message queue in bytes.
• Max msgs per second = maximum number of messages allowed to be sent per second.
|
Refresh Reduction: enabled (active) or disabled (not active)
|
The RSVP refresh-reduction parameters in effect including the following:
• ACK delay (msec) = how long in milliseconds before the receiving router sends an acknowledgment (ACK).
• Initial retransmit delay (msec) = how long in milliseconds before the router retransmits a message.
• Local epoch = the RSVP message identifier (ID) number space identifier; randomly generated each time a node reboots or the RSVP process restarts.
• Message IDs = the number of message IDs in use, the total number allocated, and the total number available (freed).
|
Neighbors
|
The total number of neighbors and the types of encapsulation in use including RSVP and User Datagram Protocol (UDP).
|
Local policy
|
The local policy currently configured.
|
COPS
|
The Common Open Policy Service (COPS) currently in effect.
|
Generic policy settings
|
Policy settings that are not specific to COPS or the local policy.
Default policy: Accept all means all RSVP messages are accepted and forwarded. Reject all means all RSVP messages are rejected.
Preemption: Disabled means RSVP is not prioritizing reservations and allocating bandwidth accordingly. Enabled means RSVP is prioritizing reservations and allocating more bandwidth to those with the highest priority.
|
Related Commands
Command
|
Description
|
debug ip rsvp
|
Displays debug messages for RSVP categories.
|
show ip rsvp atm-peak-rate-limit
To display the current peak rate limit set for an interface or for all interfaces, if any, use the show ip rsvp atm-peak-rate-limit command in EXEC mode.
show ip rsvp atm-peak-rate-limit [interface-id]
Syntax Description
interface-id
|
(Optional) Specifies the interface for which current peak rate limit statistics should displayed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
Usage Guidelines
The show ip rsvp atm-peak-rate-limit command displays the configured peak rate using the following notations for brevity:
•
Kilobytes is shown as K bytes; for example, 1200 kilobytes is displayed as 1200K bytes.
•
1000 kilobytes is displayed as 1M bytes.
If no interface name is specified, configured peak rates for all Resource Reservation Protocol (RSVP)-enabled interfaces are displayed.
Examples
The following example depicts results of the show ip rsvp atm-peak-rate-limit command, presuming that the ATM subinterface 2/0/0.1 was configured with a reservation peak rate limit of 100 KB using the ip rsvp atm-peak-rate-limit command.
The following is sample output from the show ip rsvp atm-peak-rate-limit command using the interface-id argument:
Router# show ip rsvp atm-peak-rate-limit atm2/0/0.1
RSVP: Peak rate limit for ATM2/0/0.1 is 100K bytes
The following samples show output from the show ip rsvp atm-peak-rate-limit command when no interface name is given:
Router# show ip rsvp atm-peak-rate-limit
Interface name Peak rate limit
Router# show ip rsvp atm-peak-rate-limit
Interface name Peak rate limit
Related Commands
Command
|
Description
|
ip rsvp atm-peak-rate-limit
|
Sets a limit on the peak cell rate of reservations for all newly created RSVP SVCs established on the current interface or any of its subinterfaces.
|
show ip rsvp counters
To display the number of Resource Reservation Protocol (RSVP) messages that were sent and received on each interface, use the show ip rsvp counters command in EXEC mode.
show ip rsvp counters [interface interface_unit | summary | neighbor]
Syntax Description
interface interface_unit
|
(Optional) Number of RSVP messages sent and received for the specified interface name.
|
summary
|
(Optional) Cumulative number of RSVP messages sent and received by the router over all interfaces.
|
neighbor
|
(Optional) Number of RSVP messages sent and received by the specified neighbor.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(14)ST
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T, and the neighbor keyword was added.
|
12.2(15)T
|
The following modifications were made to this command:
• The neighbor keyword was added.
• The output was modified to show the errors counter incrementing. This occurs whenever an RSVP message, on which the authentication checks have failed, is received on an interface that has RSVP authentication enabled.
|
Usage Guidelines
Use the show ip rsvp counters command to display the number of RSVP messages that were sent and received for each interface on which RSVP is configured.
If you enter the show ip rsvp counters command without a keyword, the command displays the number of RSVP messages that were sent and received for each interface on which RSVP is configured.
Examples
The following command shows the values for the number of RSVP messages of each type that were sent and received by the router over all interfaces:
Router# show ip rsvp counters summary
All Interfaces Recv Xmit Recv Xmit
Path 23284 0 Resv 0 23258
PathError 0 0 ResvError 0 0
PathTear 6 0 ResvTear 0 6
ResvConf 0 0 RTearConf 0 0
Ack 186 86 Srefresh 85 93
DSBM_WILLING 0 0 I_AM_DSBM 0 0
Table 27 describes the fields shown in the display.
Table 27 show ip rsvp counters summary Command Field Descriptions
Field
|
Description
|
All Interfaces
|
Types of messages displayed for all interfaces.
|
Recv
|
Number of messages received on the specified interface or on all interfaces.
|
Xmit
|
Number of messages transmitted from the specified interface or from all interfaces.
|
Related Commands
Command
|
Description
|
clear ip rsvp counters
|
Clears (sets to zero) all IP RSVP counters that are being maintained by the router.
|
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 EXEC mode.
show ip rsvp installed [interface-type interface-number] [detail]
Syntax Description
detail
|
(Optional) Specifies additional information about interfaces and their reservations.
|
interface-type
|
(Optional) Specifies the type of the interface.
|
interface-number
|
(Optional) Specifies the number of the interface.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(15)T
|
The command output was modified to display the resources required for a traffic control state block (TCSB) after compression has been taken into account.
|
Usage Guidelines
The show ip rsvp installed command displays information about interfaces and their reservations. Enter the optional detail keyword for additional information, including the reservation's traffic parameters, downstream hop, compression, and resources used by RSVP to ensure quality of service (QoS) for this reservation.
Examples
The following is sample output from the show ip rsvp installed command:
Router# show ip rsvp installed
RSVP: Ethernet1: has no installed reservations
kbps To From Protocol DPort Sport Weight Conversation
0 224.250.250.1 132.240.2.28 UDP 20 30 128 270
150 224.250.250.1 132.240.2.1 UDP 20 30 128 268
100 224.250.250.1 132.240.1.1 UDP 20 30 128 267
200 224.250.250.1 132.240.1.25 UDP 20 30 256 265
200 224.250.250.2 132.240.1.25 UDP 20 30 128 271
0 224.250.250.2 132.240.2.28 UDP 20 30 128 269
150 224.250.250.2 132.240.2.1 UDP 20 30 128 266
350 224.250.250.3 0.0.0.0 UDP 20 0 128 26
Table 28 describes the significant fields shown in the display.
Table 28 show ip rsvp installed Field Descriptions
Field
|
Description
|
kbps
|
Reserved rate.
|
To
|
IP address of the source device.
|
From
|
IP address of the destination device.
|
Protocol
|
Protocol User Datagram Protocol (UDP)/TCP type.
|
DPort
|
Destination UDP/TCP port
|
Sport
|
Source UDP/TCP port.
|
Weight
|
Weight used in weighted fair queueing (WFQ).
|
Conversation
|
WFQ conversation number. If the WFQ is not configured on the interface, weight and conversation will be zero.
|
RSVP Compression Method Prediction Example
The following example of 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 the serial3/0 interface in effect:
Router# show ip rsvp installed detail
RSVP:Ethernet2/1 has no installed reservations
RSVP:Serial3/0 has the following installed reservations
RSVP Reservation. Destination is 10.1.1.2. Source is 10.1.1.1,
Protocol is UDP, Destination port is 18054, Source port is 19156
Compression:(method rtp, context ID = 1, 37.98 bytes-saved/pkt avg)
Reserved bandwidth:65600 bits/sec, Maximum burst:328 bytes, Peak rate:80K bits/sec
Min Policed Unit:164 bytes, Max Pkt Size:164 bytes
Admitted flowspec (as required if compression were not applied):
Reserved bandwidth:80K bits/sec, Maximum burst:400 bytes, Peak rate:80K bits/sec
Min Policed Unit:200 bytes, Max Pkt Size:200 bytes
Resource provider for this flow:
WFQ on FR PVC dlci 101 on Se3/0: PRIORITY queue 24. Weight:0, BW 66 kbps
Conversation supports 1 reservations [0x1000405]
Data given reserved service:3963 packets (642085 bytes)
Data given best-effort service:0 packets (0 bytes)
Reserved traffic classified for 80 seconds
Long-term average bitrate (bits/sec):64901 reserved, 0 best-effort
Policy:INSTALL. Policy source(s):Default
The following example of the show ip rsvp installed detail command shows that compression is not predicted on the serial3/0 interface because no compression context IDs are available:
Router# show ip rsvp installed detail
RSVP:Ethernet2/1 has no installed reservations
RSVP:Serial3/0 has the following installed reservations
RSVP Reservation. Destination is 10.1.1.2. Source is 10.1.1.1,
Protocol is UDP, Destination port is 18116, Source port is 16594
Compression:(rtp compression not predicted:no contexts available)
Reserved bandwidth:80K bits/sec, Maximum burst:400 bytes, Peak rate:80K bits/sec
Min Policed Unit:200 bytes, Max Pkt Size:200 bytes
Resource provider for this flow:
WFQ on FR PVC dlci 101 on Se3/0: PRIORITY queue 24. Weight:0, BW 80 kbps
Conversation supports 1 reservations [0x2000420]
Data given reserved service:11306 packets (2261200 bytes)
Data given best-effort service:0 packets (0 bytes)
Reserved traffic classified for 226 seconds
Long-term average bitrate (bits/sec):79951 reserved, 0 best-effort
Policy:INSTALL. Policy source(s):Default
Note
When no compression context IDs are available, use the ip rtp compression-connections number command to increase the pool of compression context IDs.
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 ip rsvp interface
To display Resource Reservation Protocol (RSVP)-related information, use the show ip rsvp interface command in EXEC mode.
show ip rsvp interface [interface-type interface-number] [detail]
Syntax Description
interface-type
|
(Optional) Type of the interface.
|
interface-number
|
(Optional) Number of the interface.
|
detail
|
(Optional) Additional information about interfaces.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(2)T
|
The detail keyword was added.
|
12.2(4)T
|
This command was implemented on the Cisco 7500 series and the ATM-permanent virtual circuit (PVC) interface.
|
12.2(13)T
|
The following modifications were made to this command:
• Rate-limiting and refresh-reduction information were added to the output display.
• This command was modified to display RSVP global settings when no keywords or arguments are entered.
|
12.2(15)T
|
The following modifications were made to this command:
• The command output was modified to display the effects of compression on admission control and the RSVP bandwidth limit counter.
• Cryptographic authentication parameters were added to the display.
|
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
Examples
The following command shows information for each interface on which RSVP is enabled:
Router# show ip rsvp interface
interface allocated i/f max flow max sub max
Table 29 describes the fields shown in the display.
Table 29 show ip rsvp interface Field Descriptions
Field
|
Description
|
interface
|
Interface name.
|
allocated
|
Current allocation budget.
|
i/f max
|
Maximum allocatable bandwidth.
|
flow max
|
Largest single flow allocatable on this interface.
|
sub max
|
Largest sub-pool value allowed on this interface.
|
Detailed RSVP Information Example
The following command shows detailed RSVP information for each interface on which RSVP is enabled:
Router# show ip rsvp interface detail
Curr allocated:0 bits/sec
Max. allowed (total):200M bits/sec
Max. allowed (per flow):200M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/secMax. allowed for LSP tunnels using sub-pools:0
bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):50M bits/sec
Max. allowed (per flow):50M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Curr allocated:0 bits/sec
Max. allowed (total):200M bits/sec
Max. allowed (per flow):200M bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
DSCP value used in RSVP msgs:0x3F
Number of refresh intervals to enforce blockade state:4
Number of missed refresh messages:4
Table 30 describes the significant fields shown in the detailed display for interface PO0/0. The fields for the other interfaces are similar.
Table 30 show ip rsvp interface detail Field Descriptions -Detailed RSVP Information Example
Field
|
Description
|
PO0/0
|
Interface name.
|
Bandwidth
|
The RSVP bandwidth parameters in effect including the following:
• 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 including the following:
• DSCP value used in RSVP msgs = differentiated services code point (DSCP) used in RSVP messages.
• Number of refresh intervals to enforce blockade state = how long in milliseconds before the blockade takes effect.
• Number of missed refresh messages = how many refresh messages until the router state expires.
• Refresh interval = how long in milliseconds until a refresh message is sent.
|
RSVP Compression Method Prediction Example
The following example from the show ip rsvp interface detail command shows the RSVP compression method prediction configuration for each interface on which RSVP is configured:
Router# show ip rsvp interface detail
Curr allocated:0 bits/sec
Max. allowed (total):1158K bits/sec
Max. allowed (per flow):128K bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
Header Compression methods supported:
rtp (36 bytes-saved), udp (20 bytes-saved)
Using IP encap:0. Using UDP encap:0
Refresh reduction:disabled
Curr allocated:0 bits/sec
Max. allowed (total):1158K bits/sec
Max. allowed (per flow):128K bits/sec
Max. allowed for LSP tunnels using sub-pools:0 bits/sec
Set aside by policy (total):0 bits/sec
Header Compression methods supported:
rtp (36 bytes-saved), udp (20 bytes-saved)
Using IP encap:1. Using UDP encap:0
Refresh reduction:disabled
Table 31 describes the significant fields shown in the display for interface Ethernet2/1. The fields for interface Serial3/0 are similar.
Table 31 show ip rsvp interface detail Field Descriptions—RSVP Compression Method Prediction Example
Field
|
Description
|
Et2/1: Se3/0
|
Interface name.
|
Bandwidth
|
The RSVP bandwidth parameters in effect including the following:
• 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 including the following:
• 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).
|
Cryptographic Authentication Example
The following example of the show ip rsvp interface detail command displays detailed information, including the cryptographic authentication parameters, for all RSVP-configured interfaces on the router:
Router# show ip rsvp interface detail
Curr allocated: 0 bits/sec
Max. allowed (total): 7500K bits/sec
Max. allowed (per flow): 7500K bits/sec
Max. allowed for LSP tunnels using sub-pools: 0 bits/sec
Set aside by policy (total):0 bits/sec
Using IP encap: 0. Using UDP encap: 0
Refresh reduction: disabled
Table 32 describes the significant fields shown in the display.
Table 32 show ip rsvp interface detail Field Descriptions—Cryptograhic
Authentication Example
Field
|
Description
|
Et0/0
|
Interface name.
|
Bandwidth
|
The RSVP bandwidth parameters in effect including the following:
• 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 include the following:
• Key = The key (string) for the RSVP authentication algorithm displayed in clear text (for example, 11223344) or encrypted <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).
|
Related Commands
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 EXEC mode.
show ip rsvp listeners [dst | any] [udp | tcp | any | protocol] [dst-port | any]
Syntax Description
dst | any
|
(Optional) A particular destination or any destination for an RSVP message.
|
udp | tcp | any | protocol
|
(Optional) User Datagram Protocol (UDP), TCP, or any protocol to be used on the receiving interface and the UDP or TCP source port number.
Note If you select protocol, the range is 0 to 255 and the protocol is IP.
|
dst-port | any
|
(Optional) A particular destination port from 0 to 65535 or any destination for an RSVP message.
|
Defaults
If you enter 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
EXEC
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
Usage Guidelines
Use the show ip rsvp listeners command to display the number of listeners that were sent and received for each interface on which RSVP is configured.
Examples
The following command shows the current listeners:
Router# show ip rsvp listeners
To Protocol DPort Description Action
145.10.2.1 any any RSVP Proxy reply
Table 33 describes the fields shown in the display.
Table 33 show ip rsvp listeners Command Field Descriptions
Field
|
Description
|
To
|
IP address of the receiving interface.
|
Protocol
|
Protocol used.
|
DPort
|
Destination port on the receiving router.
|
Description
|
Cisco IOS component that requested RSVP to do the listening; for example, RSVP proxy and label-switched path (LSP) tunnel signaling.
|
Action
|
Action taken when a flow arrives at its destination. The choices include:
• Announce—The arrival of the flow is announced.
• Reply—After the flow arrives at its destination, the sender receives a reply.
|
Related Commands
Command
|
Description
|
ip rsvp listener
|
Configures an RSVP router to listen for Path messages.
|
show ip rsvp neighbor
To display current Resource Reservation Protocol (RSVP) neighbors, use the show ip rsvp neighbor command in EXEC mode.
show ip rsvp neighbor [detail]
Syntax Description
detail
|
(Optional) Additional information about RSVP neighbors.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(13)T
|
The interface-type interface-number arguments were deleted. The detail keyword was added to the command, and rate-limiting and refresh-reduction information was added to the output.
|
Usage Guidelines
Use the show ip rsvp neighbor command to show the IP addresses for the current RSVP neighbors. Enter the detail keyword to display rate-limiting and refresh-reduction parameters for the RSVP neighbors.
Examples
The following command shows the current RSVP neighbors:
Router# show ip rsvp neighbor
Table 34 describes the fields shown in the display.
Table 34 show ip rsvp neighbor Command Field Descriptions
Field
|
Description
|
21.0.0.1
|
IP address of neighboring router.
|
RSVP
|
Type of encapsulation being used.
|
The following command shows the rate-limiting and refresh-reduction parameters for the current RSVP neighbors:
Router# show ip rsvp neighbor detail
Highest rcvd message id:1059
Last rcvd message:00:00:04