Downloads |
 Feedback
|
Table Of Contents
Prerequisites for RSVP Application ID Support
Restrictions for RSVP Application ID Support
Information About RSVP Application ID Support
Feature Overview of RSVP Application ID Support
Global and Per-Interface RSVP Policies
Benefits of RSVP Application ID Support
How to Configure RSVP Application ID Support
Configuring RSVP Application IDs and Local Policies for RSVP-Aware Software Programs
Configuring a Local Policy Globally
Configuring a Local Policy on an Interface
Configuring a Static Sender with an Application ID
Configuring a Static Receiver with an Application ID
Verifying the RSVP Application ID Support Configuration
Configuration Examples for RSVP Application ID Support
Configuring RSVP Application ID Support: Example
Configuring a Proxy Receiver on R4
Configuring an Application ID and a Global Local Policy on R3
Configuring an Application ID and Separate Bandwidth Pools on R2 for Per-Interface Local Policies
Configuring an Application ID and a Static Reservation from R1 to R4
Verifying RSVP Application ID Support: Example
Verifying the Application ID and the Global Local Policy on R3
Verifying the Application ID and the Per-Interface Local Policies on R2
Verifying the Application ID and the Reservation on R1
Feature Information for RSVP Application ID Support
RSVP Application ID Support
First Published: February 27, 2006Last Updated: February 19, 2007The RSVP Application ID Support feature introduces application-specific Resource Reservation Protocol (RSVP) reservations, which enhance the granularity for local policy match criteria so that you can manage quality of service (QoS) on the basis of application type.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for RSVP Application ID Support" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for RSVP Application ID Support
•
•
•
•
•
Prerequisites for RSVP Application ID Support
You must configure RSVP on one or more interfaces on at least two neighboring routers that share a link within the network.
Restrictions for RSVP Application ID Support
•
•
Information About RSVP Application ID Support
To use the RSVP Application ID Support feature, you should understand the following concepts:
•
•
Feature Overview of RSVP Application ID Support
This section provides the following information:
•
•
How RSVP Functions
Multiple applications such as voice and video need RSVP support. RSVP admits requests until the bandwidth limit is reached. RSVP does not differentiate between the requests and is not aware of the type of application for which the bandwidth is requested.
As a result, RSVP can exhaust the allowed bandwidth by admitting requests that represent just one type of application, causing all subsequent requests to be rejected because of unavailable bandwidth. For example, a few video calls could prevent all or most of the voice calls from being admitted because the video calls require a large amount of bandwidth and not enough bandwidth remains to accommodate the voice calls. With this limitation, you would probably not deploy RSVP for multiple applications especially if voice happens to be one of the applications for which RSVP is required.
The solution is to allow configuration of separate bandwidth limits for individual applications or classes of traffic. Limiting bandwidth per application requires configuring a bandwidth limit per application and having each reservation flag the application to which the reservation belongs so that it can be admitted against the appropriate bandwidth limit.
Application and Sub Application Identity Policy Element for Use with RSVP (IETF RFC 2872) allows for creation of separate bandwidth reservation pools. For example, an RSVP reservation pool can be created for voice traffic, and a separate RSVP reservation pool can be created for video traffic. This prevents video traffic from overwhelming voice traffic.
Note
Sample Solution
Figure 1 shows a sample solution in which application ID is used. In this example, bandwidth is allocated between the voice and video sessions that are being created by Cisco Unified Communications Manager. Video requires much more bandwidth than voice, and if you do not separate the reservations, the video traffic could overwhelm the voice traffic.
Cisco Unified Communications Manager has been enhanced to use the RSVP Application ID Support feature. In this example, when making the RSVP reservation, Cisco Unified Communications Manager has the ability to specify whether the reservation should be made against a video RSVP bandwidth pool or a voice RSVP bandwidth pool. If there is not enough bandwidth remaining in the requested pool, even though there is enough bandwidth in the total RSVP allocation, RSVP signals Cisco Unified Communications Manager that there is a problem with the reservation. Figure 1 shows some of the signaling and data traffic that is sent during the session setup.
Figure 1 Sample Solution Using RSVP Application ID Support
In this scenario, the IP phones and IP video devices do not directly support RSVP. In order to allow RSVP to reserve the bandwidth for these devices, the RSVP agent component in the Cisco IOS router creates the reservation. During the setup of the voice or video session, Cisco Unified Communications Manager communicates with the RSVP agent and sends the necessary parameters to reserve the appropriate bandwidth.
When a voice or video call is initiated on a device, the device signals Cisco Unified Communications Manager, which signals the RSVP agent, specifying the RSVP application ID that corresponds to the type of call (voice or video in this example). The RSVP agents establish the RSVP reservation across the network and notify Cisco Unified Communications Manager that the reservation is in place. Cisco Unified Communications Manager then completes session establishment and the Real-Time Transport Protocol (RTP) traffic streams flow between the devices. If the RSVP agents are unable to create the bandwidth reservations for the requested application ID, they communicate that information back to Cisco Unified Communications Manager, which signals this information back to the initiator.
Global and Per-Interface RSVP Policies
You can configure RSVP policies globally and on a per-interface basis. You can also configure multiple global policies and multiple policies per interface.
Global RSVP policies restrict how much RSVP bandwidth a router uses regardless of the number of interfaces. You should configure a global policy if your router has CPU restrictions, one interface, or multiple interfaces that do not require different bandwidth limits.
Per-interface RSVP policies allow you to configure separate bandwidth pools with varying limits so that no one application, such as video, can consume all the RSVP bandwidth on a specified interface at the expense of other applications, such as voice, which would be dropped. You should configure a per-interface policy when you need greater control of the available bandwidth.
How RSVP Policies Are Applied
RSVP searches for policies whenever an RSVP message is processed. The policy tells RSVP if any special handling is required for that message.
If your network configuration has global and per-interface RSVP policies, the per-interface policies are applied first meaning that RSVP looks for policy-match criteria in the order in which the policies were configured. RSVP searches for policy-match criteria in the following order:
•
•
•
•
If RSVP finds no policy-match criteria, it accepts all incoming messages. To change this decision from accept to reject, issue the ip rsvp policy default-reject command.
Preemption
Preemption happens when one reservation receives priority over another because there is insufficient bandwidth in an RSVP pool. There are two types of RSVP bandwidth pools: local policy pools and interface pools. Local policies can be global or interface-specific. RSVP performs admission control against these pools when a RESV message arrives.
If an incoming reservation request matches an RSVP local policy with an RSVP bandwidth limit that has been reached (as configured with the bandwidth group submode of the maximum (local policy) command), RSVP tries to preempt other lower-priority reservations admitted by that policy. When there are too few of these lower-priority reservations, then RSVP rejects the incoming reservation request. If there are enough lower-priority reservations that can be preempted to make room for the new call, then RSVP will next look at the interface bandwidth pool (configured with the ip rsvp bandwidth command). If that bandwidth limit has been reached, then RSVP tries to preempt other lower-priority reservations on that interface to accommodate the new reservation request. However, RSVP does not consider which local policies admitted the reservations—if there is not enough bandwidth on the interface bandwidth pool that can be preempted to make room for the new call, then RSVP rejects the new reservation even though the new reservation was able to obtain bandwidth from the local policy pool.
Preemption can also happen when you manually reconfigure an RSVP bandwidth pool of any type to a lower value such that the existing reservations using that pool no longer fit in the pool.
How Preemption Priorities Are Assigned and Signaled
If a received RSVP PATH or RESV message contains preemption priorities (signaled with an IETF RFC 3181 preemption priority policy element inside an IETF RFC 2750 POLICY_DATA object) and the priorities are higher than those contained in the matching local policy (if any), the message is rejected and a PATHERROR or RESVERROR message is sent in response. If the priorities are approved by the local policy, they are stored with the RSVP state in the router and forwarded to the router's neighbors.
If a received RSVP PATH or RESV message does not contain preemption priorities (as previously described), the ip rsvp policy preempt command is enabled globally, and the message matches a local policy that contains a preempt-priority command, then a POLICY_DATA object with a preemption priority element that contains the local policy's priorities is added to the message as part of the policy decision. These priorities are stored with the RSVP state in the router and forwarded to neighbors.
Controling Preemption
The ip rsvp policy preempt command controls whether or not a router preempts any reservations when required. When you issue this command, a RESV message that subsequently arrives on an interface can preempt the bandwidth of one or more reservations on that interface if the assigned setup priority of the new reservation is higher than the assigned hold priorities of the installed reservations.
Benefits of RSVP Application ID Support
The RSVP Application ID Support feature provides the following benefits:
•
•
•
How to Configure RSVP Application ID Support
You can configure application IDs and local policies for use with RSVP-aware software programs, such as Cisco Unified Communications Manager, or for use with non-RSVP-aware applications, such as static PATH and RESV messages.
This section contains the following procedures:
•
•
•
Configuring RSVP Application IDs and Local Policies for RSVP-Aware Software Programs
This section contains the following procedures:
•
Note
•
•
Configuring an Application ID
Perform this task to configure an application ID.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip rsvp policy identity alias policy-locator locatorExample:Router(config)# ip rsvp policy identity rsvp-voice policy-locator APP=VoiceDefines RSVP application IDs to use as match criteria for local policies.
•
Note
•
Step 4
Repeat Step 3 as needed to configure additional application IDs.
Defines additional application IDs.
Step 5
end
Example:Router(config)# endExits global configuration mode and returns to privileged EXEC mode.
What to Do Next
Configure a local policy globally, on an interface, or both.
Configuring a Local Policy Globally
Perform this task to configure a local policy globally.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip rsvp policy local {acl acl1 [acl2...acl8] | default | identity alias1 [alias2...alias4] | origin-as as1 [as2...as8]}Example:Router(config)# ip rsvp policy local identity rsvp-voiceCreates a local policy to determine how RSVP resources are used in a network and enters local policy configuration mode.
•
Step 4
(Optional) Configures additional local policies.
Step 5
{accept | forward [all | path | path-error | resv | resv-error] | default | exit | fast-reroute | local-override | maximum [bandwidth [group x] [single y] | senders n] | preempt-priority [traffic-eng x] setup-priority [hold-priority]}Example:Router(config-rsvp-policy-local)# forward all
(Optional) Defines the properties of the local policy that you are creating. (These are the submode commands.)
Note
See the ip rsvp policy local command for more detailed information on submode commands.
Step 6
(Optional) Configures additional submode commands.
Step 7
end
Example:Router(config-rsvp-policy-local)# end
Exits local policy configuration mode and returns to privileged EXEC mode.
Configuring a Local Policy on an Interface
Perform this task to configure a local policy on an interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface type number
Example:Router(config)# interface Ethernet0/0
Configures the interface type and number and enters interface configuration mode.
Step 4
Repeat Step 3 as needed to configure additional interfaces.
(Optional) Configures additional interfaces.
Step 5
ip rsvp bandwidth [interface-kbps] [single-flow-kbps]
Example:Router(config-if)# ip rsvp bandwidth 500 500
Enables RSVP on an interface.
•
Step 6
(Optional) Configures bandwidth for additional interfaces.
Step 7
ip rsvp policy local {acl acl1 [acl2...acl8] | default | identity alias1 [alias2...alias4] | origin-as as1 [as2...as8]}Example:Router(config-if)# ip rsvp policy local identity rsvp-voiceCreates a local policy to determine how RSVP resources are used in a network.
•
Step 8
(Optional) Configures additional local policies.
Step 9
{accept | forward [all | path | path-error | resv | resv-error] | default | exit | fast-reroute | local-override | maximum [bandwidth [group x] [single y] | senders n] | preempt-priority [traffic-eng x] setup-priority [hold-priority]}Example:Router(config-rsvp-policy-local)# forward all
(Optional) Defines the properties of the local policy that you are creating and enters local policy configuration mode. (These are the submode commands.)
Note
See the ip rsvp policy local command for more detailed information on submode commands.
Step 10
Repeat Step 9 as needed to configure additional submode commands.
(Optional) Configures additional submode commands.
Step 11
end
Example:Router(config-rsvp-policy-local)# end
Exits local policy configuration mode and returns to privileged EXEC mode.
Configuring RSVP Application IDs with Static Senders and Receivers for Non-RSVP-Aware Software Programs
This section contains the following procedures:
•
•
•
Configuring an Application ID
Perform this task to configure an application ID.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring a Static Sender with an Application ID
Perform this task to configure a static RSVP sender with an application ID to make the router proxy an RSVP PATH message containing an application ID on behalf of an RSVP-unaware sender application.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring a Static Receiver with an Application ID
Perform this task to configure a static RSVP receiver with an application ID to make the router proxy an RSVP RESV message containing an application ID on behalf of an RSVP-unaware receiver application.
Note
SUMMARY STEPS
1.
2.
3.
or
ip rsvp reservation session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port next-hop-ip-address next-hop-interface {ff | se | wf} {rate | load} bandwidth burst-size [identity alias]
Note
4.
DETAILED STEPS
Verifying the RSVP Application ID Support Configuration
Perform the following task to verify the configuration.
SUMMARY STEPS
1.
Note
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Step 1
enable
Example:Router> enable
(Optional) Enables privileged EXEC mode.
•
Note
Step 2
show ip rsvp host {senders | receivers} [group-name | group-address]Example:Router# show ip rsvp host sendersDisplays specific information for an RSVP host.
Note
Step 3
Displays selected RSVP identities in a router configuration.
•
Note
Step 4
Displays the local policies currently configured.
•
Step 5
Displays RSVP-related receiver information currently in the database.
•
Note
Cisco IOS Releases 12.0S and 12.2S only.Step 6
Displays RSVP PATH-related sender information currently in the database.
•
Note
Cisco IOS Releases 12.0 S and 12.2 S only.Step 7
exit
Example:Router# exit
Exits privileged EXEC mode and returns to user EXEC mode.
Configuration Examples for RSVP Application ID Support
This section provides configuration examples for the RSVP Application ID Support feature.
•
•
Configuring RSVP Application ID Support: Example
The four-router network in Figure 2 contains the following configurations:
•
•
•
•
Figure 2 Sample Network with Application Identities and Local Policies
Configuring a Proxy Receiver on R4
The following example configures R4 with a proxy receiver to create an RESV message to match the PATH message for the destination 10.0.0.7:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip rsvp listener 10.0.0.7 any any replyRouter(config)# endConfiguring an Application ID and a Global Local Policy on R3
The following example configures R3 with an application ID called video and a global local policy in which all RSVP messages are being accepted and forwarded:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip rsvp policy identity video policy-locator videoRouter(config)# ip rsvp policy local identity videoRouter(config-rsvp-policy-local)# forward allRouter(config-rsvp-policy-local)# endConfiguring an Application ID and Separate Bandwidth Pools on R2 for Per-Interface Local Policies
The following example configures R2 with an application ID called video, which is a wildcard regular expression to match any application ID that contains the substring video:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip rsvp policy identity video policy-locator .*Video.*Router(config-rsvp-id)# endThe following example configures R2 with a local policy on ingress Ethernet interface 0/0:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Ethernet0/0Router(config-if)# ip address 10.0.0.2 255.0.0.0Router(config-if)# no cdp enableRouter(config-if)# ip rsvp bandwidth 200Router(config-if)# ip rsvp policy local identity videoRouter(config-rsvp-policy-local)# maximum senders 10Router(config-rsvp-policy-local)# maximum bandwidth group 100Router(config-rsvp-policy-local)# maximum bandwidth single 10Router(config-rsvp-policy-local)# forward allRouter(config-rsvp-policy-local)# endThe following example configures R2 with a local policy on egress Ethernet interface 3/0:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Ethernet3/0Router(config-if)# ip address 10.0.0.3 255.0.0.0Router(config-if)# no cdp enableRouter(config-if)# ip rsvp bandwidth 200Router(config-if)# ip rsvp policy local identity videoRouter(config-rsvp-policy-local)# maximum senders 10Router(config-rsvp-policy-local)# maximum bandwidth group 100Router(config-rsvp-policy-local)# maximum bandwidth single 10Router(config-rsvp-policy-local)# forward allRouter(config-rsvp-policy-local)# end
Note
Configuring an Application ID and a Static Reservation from R1 to R4
The following example configures R1 with an application ID called video and initiates a host generating a PATH message with that application ID:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# ip rsvp policy identity video policy-locator "GUID=www.cisco.com, APP=Video, VER=1.0"Router(config)# ip rsvp sender-host 10.0.0.7 10.0.0.1 udp 1 1 10 10 identity videoRouter(config)# endVerifying RSVP Application ID Support: Example
This section contains the following verification examples:
•
•
•
Verifying the Application ID and the Global Local Policy on R3
The following example verifies that a global local policy has been configured on R3 with an application ID called Video:
Router# show ip rsvp policy local detailGlobal:Policy for ID(s): VideoPreemption Scope: Unrestricted.Local Override: Disabled.Fast ReRoute: Accept.Handle: 23000404.Accept ForwardPath: Yes YesResv: Yes YesPathError: Yes YesResvError: Yes YesSetup Priority Hold PriorityTE: N/A N/ANon-TE: N/A N/ACurrent LimitSenders: 1 N/AReceivers: 1 N/AConversations: 1 N/AGroup bandwidth (bps): 10K N/APer-flow b/w (bps): N/A N/AGeneric policy settings:Default policy: Accept allPreemption: DisabledVerifying the Application ID and the Per-Interface Local Policies on R2
The following example verifies that an application ID called Video has been created on R2:
Router# show ip rsvp policy identityAlias: VideoType: Application IDLocator: .*Video.*The following example verifies that per-interface local policies have been created on Ethernet interface 0/0 and Ethernet interface 3/0 on R2:
Router# show ip rsvp policy local detailEthernet0/0:Policy for ID(s): VideoPreemption Scope: Unrestricted.Local Override: Disabled.Fast ReRoute: Accept.Handle: 26000404.Accept ForwardPath: Yes YesResv: Yes YesPathError: Yes YesResvError: Yes YesSetup Priority Hold PriorityTE: N/A N/ANon-TE: N/A N/ACurrent LimitSenders: 1 10Receivers: 0 N/AConversations: 0 N/AGroup bandwidth (bps): 0 100KPer-flow b/w (bps): N/A 10KEthernet3/0:Policy for ID(s): VideoPreemption Scope: Unrestricted.Local Override: Disabled.Fast ReRoute: Accept.Handle: 5A00040A.Accept ForwardPath: Yes YesResv: Yes YesPathError: Yes YesResvError: Yes YesSetup Priority Hold PriorityTE: N/A N/ANon-TE: N/A N/ACurrent LimitSenders: 0 10Receivers: 1 N/AConversations: 1 N/AGroup bandwidth (bps): 10K 100KPer-flow b/w (bps): N/A 10KGeneric policy settings:Default policy: Accept allPreemption: Disabled
Note
Verifying the Application ID and the Reservation on R1
The following example verifies that a PATH message containing the application ID called Video has been created on R1:
Router# show ip rsvp sender detailPATH Session address: 10.0.0.7, port: 1. Protocol: UDPSender address: 10.0.0.1, port: 1Inbound from: 10.0.0.1 on interface:Traffic params - Rate: 10K bits/sec, Max. burst: 10K bytesMin Policed Unit: 0 bytes, Max Pkt Size 4294967295 bytesPath ID handle: 02000402.Incoming policy: Accepted. Policy source(s): DefaultApplication ID: 'GUID=www.cisco.com, APP=Video, VER=1.0'Status: ProxiedOutput on Ethernet0/0. Policy status: Forwarding. Handle: 01000403Policy source(s): Default
Note
The following example verifies that a reservation with the application ID called Video has been created on R1:
Router# show ip rsvp reservation detailRSVP Reservation. Destination is 10.0.0.7, Source is 10.0.0.1,Protocol is UDP, Destination port is 1, Source port is 1Next Hop is 10.0.0.2, Interface is Ethernet0/0Reservation Style is Fixed-Filter, QoS Service is Guaranteed-RateResv ID handle: 01000405.Created: 10:07:35 EST Thu Jan 12 2006Average Bitrate is 10K bits/sec, Maximum Burst is 10K bytesMin Policed Unit: 0 bytes, Max Pkt Size: 0 bytesStatus:Policy: Forwarding. Policy source(s): DefaultApplication ID: 'GUID=www.cisco.com, APP=Video, VER=1.0'Additional References
The following sections provide references related to the RSVP Application ID Support feature.
Related Documents
QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples
QoS configuration tasks
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4
Cisco CallManager and related features
Cisco Unified Communications Manager and Cisco IOS Interoperability Features Roadmap
Error messages
Regular expressions
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
Technical Assistance
Command Reference
This section documents only commands that are new or modified.
ip rsvp listener
To configure a Resource Reservation Protocol (RSVP) router to listen for PATH messages, use the ip rsvp listener command in global configuration mode. To disable listening, use the no form of this command.
ip rsvp listener dst {udp | tcp | any | number} {any | dst-port} {announce | reply | reject}
no ip rsvp listener dst {udp | tcp | any | number} {any | dst-port} {announce | reply | reject}
Syntax Description
Command Default
This command is disabled by default; therefore, no listeners are configured.
Command Modes
Global configuration
Command History
12.2(13)T
This command was introduced.
12.4(6)T
Support for RSVP application identity (ID) was added.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
Use the ip rsvp listener command to allow a router to send a matching RESV message when a PATH message arrives with the desired destination address, port, and protocol. This command copies the application ID and preemption priority value, if present, from the PATH message and includes them in the RESV message.
This command is similar to the ip rsvp reservation and ip rsvp reservation-host commands. However, they do not allow you to specify more than one port or protocol per command; so you may have to enter many commands to proxy for a set of ports and protocols. In contrast, the ip rsvp listener command allows you to use a wildcard for a set of ports and protocols by using just that one command.
You can use the debug ip rsvp api command to look for a matching PATH message, but no RESV message will be sent.
Examples
In the following example, the sender is requesting that the receiver reply with a RESV message for the flow if the PATH message destination is 192.168.2.1:
Router# configure terminalRouter(config)# ip rsvp listener 192.168.2.1 any any replyRelated Commands
ip rsvp policy identity
To define Resource Reservation Protocol (RSVP) application identities (IDs), use the ip rsvp policy identity command in global configuration mode. To delete RSVP application IDs, use the no form of this command.
ip rsvp policy identity alias policy-locator locator
no ip rsvp policy identity alias [policy-locator locator]
Syntax Description
Command Default
This command is disabled by default; therefore, no RSVP application identities are defined.
Command Modes
Global configuration
Command History
12.4(6)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
You can use RSVP identities as criteria for matching RSVP PATH and RESV messages to local policies. Identities can also be used to configure static senders and receivers. When you use an RSVP identity as the match criterion for a local policy, RSVP treats the policy locator string as a type of pattern-matching string known as a regular expression. Regular expressions allow you to configure a single identity for use with a local policy that can match multiple X.500 DNs. Regular expressions, by default, are not exact matches unless you add appropriate control characters to the expression to force it to be an exact match.
In Cisco IOS software, the locator is the primary piece of information that the router uses to find the correct policy to apply to RSVP messages that contain application IDs. This string assumes the format of an X.500 DN and includes the following attributes as recommended in RFC 2872:
•
•
•
•
Here are some examples:
•
•
You can create a maximum of 100 identities on a router. If you attempt to create more, the command fails and the following error message is generated: "RSVP error: maximum number of identities already created".
When you use the ip rsvp policy identity command, be aware of the following behavior:
•
•
•
•
•
Command Restrictions
•
•
Examples
Exact Application ID Match
The following example shows an application ID for RSVP messages containing a locator string whose contents are the exact string "APP=Voice":
Router# configure terminalRouter(config)# ip rsvp policy identity "rsvp-voice" policy-locator "^APP=Voice$"Router(config-rsvp-id)# endWildcard (or Partial) Application ID Match
The following example shows an application ID that is a partial match for RSVP messages containing a locator string with the substring "APP=Voice" anywhere in the signaled application ID:
Router# configure terminalRouter(config)# ip rsvp policy identity "rsvp-voice" policy-locator ".*APP=Voice.*"Router(config-rsvp-id)# endRelated Commands
ip rsvp policy local
To determine how to perform authorization on Resource Reservation Protocol (RSVP) requests and enter local policy configuration mode, use the ip rsvp policy local command in global configuration or interface configuration mode. To disable this feature, use the no form of this command.
ip rsvp policy local {acl acl1 [acl2...acl8] | default | identity alias1 [alias2...alias4] | origin-as as1 [as2...as8]}
no ip rsvp policy local {acl acl1 [acl2...acl8] | default | identity alias1 [alias2...alias4] | origin-as as1 [as2...as8]}
Syntax Description
Command Default
This command is disabled by default; therefore, no local policies are configured.
Command Modes
Global configuration
Interface configurationCommand History
Usage Guidelines
Use the ip rsvp policy local command to determine how to perform authorization on RSVP requests.
Note
You can use all types of match criteria with non-Traffic-Engineering (TE) reservations. You can use all types of match criteria except application ID with TE reservations because TE PATH and RESV messages sent by Cisco routers do not contain application IDs.
There are four types of local policies—one default local policy, one or more ACL-based policies, one or more autonomous-system-based policies, and one or more application-ID-based policies. The default policy is used when an RSVP message does not match any ACL-, autonomous-system-, or application-ID-based policies.
You can configure a mixture of local policy types including ACL, autonomous system, application ID, or default on the same interface or globally. Policies have the following priority (from highest to lowest):
•
•
•
•
Note
Policy-Match Criteria
Note
An ACL-based policy must have at least one ACL associated with it, but it can optionally have up to eight ACLs. The ACLs can be standard or extended IP ACLs. They are matched against source/destination addresses/ports based on RSVP objects inside RSVP signaling messages as described below.
•
•
•
•
•
•
Note
An autonomous-system-based policy must have at least one autonomous system associated with it, but it can optionally have up to eight autonomous systems. They are matched against the incoming interface/source IP address contained in RSVP objects inside RSVP signaling messages, not on the IP headers of the RSVP messages.
An application-ID-based policy must have at least one application ID associated with it, but it can optionally have up to four application IDs. They are matched against the incoming interface/source IP address contained in RSVP objects inside RSVP signaling messages, not on the IP headers of the RSVP messages.
Command Restrictions
•
•
CLI Submodes
Once you type the ip rsvp policy local command, you enter the local policy CLI submode where you define the properties of the local policy that you are creating.
Note
The submode commands are as follows:
•
accept {all | path | path-error | resv | resv-error}
–
–
–
–
The default bandwidth for a policy is unlimited. Therefore, if the policy has no configured bandwidth, a RESV message is always accepted by the local policy because any bandwidth request is less than or equal to unlimited. However, the RESV message may subsequently fail admission control if there is insufficient bandwidth in the RSVP pool on the input interface to which the RESV message applies. (See the ip rsvp bandwidth command for more information.) If the bandwidth requested by the RESV messages is too large, a RESVERROR message that is also subject to local policy is transmitted to the RESV sender.
–
•
•
•
•
forward {all | path | path-error | resv | resv-error}
–
–
–
–
–
•
•
–
Previously, the maximum bandwidth command applied only to PATH messages. However, as part of the application ID enhancement, this command now applies only to RESV messages. This change has the following benefits:
Allows the local policy bandwidth limit to be used by RSVP's admission control process for both shared and nonshared reservations. Previous releases that performed group bandwidth checks on PATH messages could not account for bandwidth sharing, and, as a result, you had to account for sharing by creating a larger maximum group bandwidth for the policy.
Allows a local policy to trigger preemption during the admission control function if there is insufficient policy bandwidth to meet the needs of an incoming RESV message.–
Note
•
•
The x value indicates the upper limit of the priority for TE reservations. The range of x values is
0 to 7 in which the smaller the number, the higher the reservation's priority. For non-TE reservations, the range of x values is 0 to 65535 in which the higher the number, the higher the reservation's priority.The setup-priority argument indicates the priority of a reservation when it is initially installed. The optional hold-priority argument indicates the priority of a reservation after it has been installed; if omitted, it defaults to the setup-priority. Values for the setup-priority and hold-priority arguments range from 0 to 7 where 0 is considered the highest priority.
If the incoming message has a preemption priority that requests a priority higher than the policy allows, the message is rejected. Use the tunnel mpls traffic-eng priority command to configure preemption priority for TE tunnels.
A single policy can contain a preempt-priority traffic-eng and a preempt-priority command, which may be useful if the policy is bound to an ACL that identifies a subnet containing a mix of TE and non-TE endpoints or midpoints.
Note
Per-Interface Local Policies
All the local policy submode commands are also supported on a per-interface basis. You simply enter Cisco IOS interface configuration mode for the selected interface and type in any number and mix of the submode commands.
Per-interface local policies take precedence over global local policies. However, if there is a default local policy configured for an interface, the router does not try to match any RSVP messages arriving on that interface to any of the global local policies. Policies have the following priority (from highest to lowest):
•
•
•
•
There are some important points to note about per-interface local policies:
•
•
Examples
ACL-, Default-, and Autonomous-System-Based Policies
In the following example, any RSVP nodes in the 192.168.101.0 subnet can initiate or respond to reservation requests, but all other nodes can respond to reservation requests only. This means that any 192.168.101.x node can send and receive PATH, PATHERROR, RESV, or RESVERROR messages. All other nodes can send only RESV or RESVERROR messages, and all reservations for autonomous system 1 are rejected.
Router# configure terminalRouter(config)# access-list 104 permit ip 192.168.101.0 0.0.0.255 anyRouter(config)# ip rsvp policy local acl 104Router(config-rsvp-policy-local)# forward allRouter(config-rsvp-policy-local)# exitRouter(config)# ip rsvp policy local defaultRouter(config-rsvp-policy-local)# forward resvRouter(config-rsvp-policy-local)# forward resverrorRouter(config-rsvp-policy-local)# exitRouter(config)# ip rsvp policy local origin-as 1Router(config-rsvp-policy-local)# endApplication-ID-Based Policy
RSVP matches incoming RSVP messages with IDs to configured IDs and policies. The following example displays a global RSVP local policy that limits voice calls to 200 kbps for the whole router regardless of which interface the RSVP signaling occurs on:
Router# configure terminalRouter(config)# ip rsvp policy identity rsvp-voice policy-locator "GUID=www.cisco.com, APP=Voice"Router(config)# ip rsvp policy local identity rsvp-voiceRouter(config-rsvp-local-policy)# forward allRouter(config-rsvp-local-policy)# maximum bandwidth group 200Router(config-rsvp-local-policy)# endPer-Interface Application ID-Based Policy
The following example displays a local policy that limits all RSVP voice calls on serial interface 2/0/0 to a total of 200 kbps:
Router# configure terminalRouter(config)# ip rsvp policy identity rsvp-voice policy-locator APP=VoiceRouter(config)# interface serial2/0/0Router(config-if)# ip rsvp policy local identity rsvp-voiceRouter(config-rsvp-local-policy)# forward allRouter(config-rsvp-local-policy)# maximum bandwidth group 200Router(config-rsvp-local-policy)# exitRouter(config-if)# ip rsvp policy local defaultRouter(config-rsvp-local-policy)# forward allRouter(config-rsvp-local-policy)# maximum bandwidth group 50Router(config-rsvp-local-policy)# endRelated Commands
ip rsvp reservation
To enable a router to simulate receiving Resource Reservation Protocol (RSVP) RESV messages from a downstream host, use the ip rsvp reservation command in global configuration mode. To disable this function, use the no form of this command.
ip rsvp reservation session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port next-hop-ip-address next-hop-interface {ff | se | wf} {rate | load} bandwidth burst-size [identity alias]
no ip rsvp reservation session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port next-hop-ip-address next-hop-interface {ff | se | wf} {rate | load} bandwidth burst-size [identity alias]
Syntax Description
Command Default
The router does not simulate receiving RSVP RESV messages.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip rsvp reservation command to make the router simulate receiving RSVP RESV messages from a downstream host and to proxy RSVP RESV messages for that host. By giving a local (loopback) next-hop address and next-hop interface, you can also use this command to proxy RSVP for the router that you are configuring or you can use the ip rsvp reservation-host command.
An alias must reference an RSVP identity that you created by using the ip rsvp identity command. The policy-locator string associated with this identity is signaled in the RESV message. This identity overrides any application ID that is contained in the matching PATH message.
If the matching PATH message has an application ID, but you have not specified an application ID using the ip rsvp reservation command, the RESV message will not contain an application ID. However, the RESV message proxied by the ip rsvp listener command does put the matching PATH message application ID into the proxied RESV message.
Examples
The following example specifies the use of a Shared Explicit style of reservation and the controlled load service, with token buckets of 100 or 150 kbps and 60 or 65 kbytes maximum queue depth:
Router(config)# ip rsvp reservation 239.250.0.2 172.16.1.1 udp 20 30 172.16.4.1 Ethernet1 se load 100 60Router(config)# ip rsvp reservation 239.250.0.2 172.16.2.1 tcp 20 30 172.16.4.1 Ethernet1 se load 150 65The following example specifies the use of a Wildcard Filter style of reservation and the guaranteed bit rate service, with token buckets of 300 or 350 kbps, 60 or 65 kbytes maximum queue depth, and an application ID:
Router(config)# ip rsvp reservation 239.250.0.3 0.0.0.0 udp 20 0 172.16.4.1 Ethernet1 wf rate 300 60 identity xyzRouter(config)# ip rsvp reservation 239.1.1.1 0.0.0.0 udp 20 0 172.16.4.1 Ethernet1 wf rate 350 65 identity xyzNote that the wildcard filter does not admit the specification of the sender; it accepts all senders. This action is denoted by setting the source address and port to zero. If, in any filter style, the destination port is specified to be zero, RSVP does not permit the source port to be anything else; it understands that such protocols do not use ports or that the specification applies to all ports.
Related Commands
ip rsvp reservation-host
To enable a router to simulate a host generating Resource Reservation Protocol (RSVP) RESV messages, use the ip rsvp reservation-host command in global configuration mode. To disable this function, use the no form of this command.
ip rsvp reservation-host session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port {ff | se | wf} {rate | load} bandwidth burst-size [identity alias]
no ip rsvp reservation-host session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port {ff | se | wf} {rate | load} bandwidth burst-size [identity alias]
Syntax Description
Command Default
The router does not simulate a host generating RSVP RESV messages.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip rsvp reservation-host command to make a router simulate a host generating its own RSVP RESV messages. This command is similar to the ip rsvp reservation command, which can cause a router to generate RESV messages on behalf of another host. The main differences between the ip rsvp reservation-host and ip rsvp reservation commands follow:
•
•
•
An alias must reference an RSVP identity that you created by using the ip rsvp identity command. The policy-locator string associated with this identity is signaled in the RESV message. This identity overrides any application ID that is contained in the matching PATH message.
If the matching PATH message has an application ID, but you have not specified an application ID using the ip rsvp reservation-host command, the RESV message does not contain an application ID. However, the RESV message proxied by the ip rsvp listener command does put the matching PATH message application ID into the proxied RESV message.
Examples
The following example specifies the use of a Shared Explicit style of reservation and the controlled load service, with token buckets of 100 or 150 kbps, 60 or 65 kbps maximum queue depth, and an application ID:
Router(config)# ip rsvp reservation-host 10.1.1.1 10.30.1.4 udp 20 30 se load 100 60 identity xyzRouter(config)# ip rsvp reservation-host 10.40.2.2 10.22.1.1 tcp 20 30 se load 150 65 identity xyzRelated Commands
ip rsvp sender
To enable a router to simulate receiving Resource Reservation Protocol (RSVP) PATH messages, use the ip rsvp sender command in global configuration mode. To disable this function, use the no form of this command.
ip rsvp sender session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port previous-hop-ip-address previous-hop-interface bandwidth burst-size
[identity alias]no ip rsvp sender session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port previous-hop-ip-address previous-hop-interface bandwidth burst-size
[identity alias]Syntax Description
Command Default
The router does not simulate receiving RSVP PATH messages.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip rsvp sender command to make the router simulate that it is receiving RSVP PATH messages from an upstream host and to proxy RSVP PATH messages from that host. By including a local (loopback) previous-hop address and previous-hop interface, you can also use this command to proxy RSVP for the router that you are configuring.
An alias must reference an RSVP identity that you created by using the ip rsvp identity command. The policy-locator string associated with this identity is supplied in the PATH message.
Examples
The following example sets up the router to act as though it is receiving RSVP PATH messages using UDP over loopback interface 1:
Router(config)# ip rsvp sender 239.250.0.1 172.16.2.1 udp 20 30 172.16.2.1 loopback 1 50 5 identity xyzRouter(config)# ip rsvp sender 239.250.0.2 172.16.2.1 udp 20 30 172.16.2.1 loopback 1 50 5 identity xyzRelated Commands
ip rsvp sender-host
To enable a router to simulate a host generating a Resource Reservation Protocol (RSVP) PATH message, use the ip rsvp sender-host command in global configuration mode. To disable this function, use the no form of this command.
ip rsvp sender-host session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port bandwidth burst-size [identity alias]
no ip rsvp sender-host session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-d-port sender-s-port bandwidth burst-size [identity alias]
Syntax Description
Command Default
The router does not simulate RSVP PATH message generation.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the ip rsvp sender-host command to make a router simulate a host generating its own RSVP PATH messages. This command is similar to the ip rsvp sender command, which can cause a router to generate RSVP PATH messages on behalf of another host. The main differences between the ip rsvp sender-host and ip rsvp sender commands follow:
•
•
•
An alias must reference an RSVP identity that you created by using the ip rsvp identity command. The policy-locator string associated with this identity is signaled in the RESV message. This identity overrides any application ID that is contained in the matching PATH message.
Examples
The following example sets up the router to act like a host that sends traffic to the given address:
Router(config)# ip rsvp sender-host 10.0.0.7 10.0.0.1 udp 1 1 10 10 identity xyzRelated Commands
maximum (local policy)
To set the limits for Resource Reservation Protocol (RSVP) resources, use the maximum command in local policy configuration mode. To delete the limits, use the no form of this command.
maximum [bandwidth [group x] [single y] | senders n]
no maximum [bandwidth [group x] [single y] | senders n]
Syntax Description
Command Default
No maximum bandwidth limit is set and no RSVP senders are configured.
Command Modes
Local policy configuration
Command History
12.0(29)S
This command was introduced.
12.4(6)T
This command was modified to apply to RESV messages.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
Previously, the maximum bandwidth command applied only to PATH messages. However, as part of the application ID enhancement, this command now applies only to RESV messages. This change has the following benefits:
•
•
Examples
The following example specifies the maximum bandwidth for a group of reservations and for a single reservation, respectively:
Router(config-rsvp-local-policy)# maximum bandwidth group 500Router(config-rsvp-local-policy)# maximum bandwidth single 50Related Commands
show ip rsvp host
To display specific information for a Resource Reservation Protocol (RSVP) host, use the show ip rsvp host command in user EXEC or privileged EXEC mode.
show ip rsvp host {senders | receivers} [group-name | group-address]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
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 sendersTo From Pro DPort Sport Prev Hop I/F BPS192.168.104.3 192.168.104.1 UDP 1 1 10KMode(s): Host CLITable 1 describes the significant fields shown in the display.
In the following example from the show ip rsvp host senders command, an RSVP identity is configured for the local sender and more information displays:
Router# show ip rsvp host sendersTo From Pro DPort Sport Prev Hop I/F BPS192.168.104.3 192.168.104.1 UDP 1 1 10KMode(s): Host CLIIdentity: voice100Locator: GUID=www.cisco.com,APP=voice,VER=100.0ID Type: ApplicationTable 2 describes the significant fields shown in the display.
Related Commands
ip rsvp sender-host
Enables a router to simulate a host generating an RSVP PATH message.
show ip rsvp policy identity
To display selected Resource Reservation Protocol (RSVP) identities in a router configuration, use the show ip rsvp policy identity command in user EXEC or privileged EXEC mode.
show ip rsvp policy identity [regular-expression]
Syntax Description
regular-expression
(Optional) String of text that allows pattern matching on the alias strings of the RSVP identities to be displayed.
Command Default
All configured RSVP identities are displayed.
Command Modes
User EXEC
Privileged EXECCommand History
12.4(6)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Usage Guidelines
Use the show ip rsvp policy identity command with the optional regular-expression argument to perform pattern matching on the alias strings of the RSVP identities to be displayed. Use this filtering capability to search for a small subset of RSVP identities in a configuration with a large number of identities.
Omit the regular-expression argument to display all the configured identities.
Examples
In the following example from the show ip rsvp policy identity command, all the configured identities are displayed:
Router# show ip rsvp policy identityAlias: voice1Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=1.0Alias: voice10Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=10.0Alias: voice100Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=100.0Alias: voice1000Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=1000.0Table 3 describes the significant fields shown in the display.
In the following example from the show ip rsvp policy identity command, all the identities whose aliases contain voice100 display:
Router# show ip rsvp policy identity voice100Alias: voice100Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=100.0Alias: voice1000Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=1000.0In the following example from the show ip rsvp policy identity command, all the identities whose aliases contain an exact match on voice100 are displayed:
Router# show ip rsvp policy identity ^voice100$Alias: voice100Type: Application IDLocator: GUID=www.cisco.com,APP=voice,VER=100.0Related Commands
show ip rsvp policy local
To display the local policies that are currently configured, use the show ip rsvp policy local command in user EXEC or privileged EXEC mode.
show ip rsvp policy local [detail] [interface type number] [default | acl acl | origin-as as | identity alias]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use the show ip rsvp policy local command to display information about the selected local policies that are currently configured. You can use the default keyword and/or the interface type number keyword and argument combination with one or more of the match criteria.
If you omit the acl acl, the origin-as as, or the identity alias keyword and argument combinations, all local policies currently configured appear.
If you use the ACL, the autonomous system, or the application-ID options as match criteria, you can specify only one. However, that parameter can be any ACL, autonomous system, or application ID of any local policy that you have created. If you have multiple local policies with a common match criteria, using that parameter displays all local policies that meet the match criteria. On the other hand, if you have created local policies each with multiple ACLs, autonomous systems, or application IDs as the match criteria, you cannot use that parameter to show only a specific policy. You must omit the match criteria and show all the local policies.
Examples
The following sample output from the show ip rsvp policy local command displays global and per-interface local policies based on RSVP identities (application IDs) that have been configured:
Router# show ip rsvp policy localA=Accept F=ForwardGlobal:Path:AF Resv:AF PathErr:AF ResvErr:AF ACL(s):101Path:AF Resv:AF PathErr:AF ResvErr:AF AS(es):3Path:AF Resv:AF PathErr:AF ResvErr:AF ID:voicePath:AF Resv:AF PathErr:AF ResvErr:AF ID:videoSerial2/0/0:Path:AF Resv:AF PathErr:AF ResvErr:AF ID:voicePath:AF Resv:AF PathErr:AF ResvErr:AF ID:videoSerial2/0/1:Path:AF Resv:AF PathErr:AF ResvErr:AF ID:conferencePath:AF Resv:AF PathErr:AF ResvErr:AF ID:iptvPath:-- Resv:-- PathErr:-- ResvErr:-- DefaultGeneric policy settings:Default policy: Accept allPreemption: DisabledTable 4 describes the significant fields shown in the display.
The following sample output from the show ip rsvp policy local detail command shows the location of the local policy (such as whether the policy is configured globally or for a specific interface, and the settings for preemption scope and maximum bandwidth. Preemption priorities and sender and receiver limits also appear even if they are set to their defaults.
Router# show ip rsvp policy local detailGlobal:Policy for ID: voicePreemption Scope: Unrestricted.Local Override: Disabled.Fast ReRoute: Accept.Handle: 02000409.Accept ForwardPath: Yes YesResv: Yes YesPathError: Yes YesResvError: Yes YesSetup Priority Hold PriorityTE: N/A N/ANon-TE: N/A N/ACurrent LimitSenders: 0 40Receivers: 0 N/AConversations: 0 N/AGroup bandwidth (bps): 0 200KPer-flow b/w (bps): N/A 10MPolicy for ID: videoPreemption Scope: Unrestricted.Local Override: Disabled.Fast ReRoute: Accept.Handle: 0200040A.Accept ForwardPath: Yes YesResv: Yes YesPathError: Yes YesResvError: Yes YesSetup Priority Hold PriorityTE: 2 2Non-TE: 5 4Current LimitSenders: 2 10Receivers: 2 10Conversations: 2 10Group bandwidth (bps): 100K 200KPer-flow b/w (bps): N/A 10MEthernet2/1:Policy for ID: voicePreemption Scope: Unrestricted.Local Override: Disabled.Fast ReRoute: Accept.Handle: 0200040B.Accept ForwardPath: Yes YesResv: Yes YesPathError: Yes YesResvError: Yes YesSetup Priority Hold PriorityTE: 2 2Non-TE: 5 4Current LimitSenders: 2 10Receivers: 2 10Conversations: 2 10Group bandwidth (bps): 100K 200KPer-flow b/w (bps): N/A 10MGeneric policy settings:Default policy: Accept allPreemption: DisabledTable 5 describes the significant fields shown in the display.
Related Commands
Feature Information for RSVP Application ID Support
Table 6 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Glossary
ACL—access control list. An ACL consists of individual filtering rules grouped together in a single list. It is generally used to provide security filtering, although it may be used to provide a generic packet classification facility.
admission control—The process in which an RSVP reservation is accepted or rejected on the basis of end-to-end available network resources.
application identity (ID)—A string that can be inserted in a policy element in a POLICY_DATA object of an RSVP message to identify the application and associate it with the RSVP reservation request, thus allowing routers along the path to make appropriate decisions based on the application information.
autonomous system—A collection of networks that share the same routing protocol and that are under the same system administration.
bandwidth—The difference between the highest and lowest frequencies available for network signals. The term also is used to describe the rated throughput capacity of a given network medium or protocol.
Cisco Unified Communications Manager—Formerly known as Cisco CallManager. The software-based, call-processing component of the Cisco IP telephony solution. The software extends enterprise telephony features and functions to packet telephony network devices such as IP phones, media processing devices, Voice-over-IP (VoIP) gateways, and multimedia applications.
DSCP—differentiated services code point. The six most significant bits of the 1-byte IP type of service (ToS) field. The per-hop behavior represented by a particular DSCP value is configurable. DSCP values range between 0 and 63.
policy—Any defined rule that determines the use of resources within the network. A policy can be based on a user, a device, a subnetwork, a network, or an application.
QoS—quality of service. A measure of performance for a transmission system that reflects its transmission quality and service availability.
RSVP—Resource Reservation Protocol. A protocol for reserving network resources to provide quality of service guarantees to application flows.
RSVP agent—Implements a Resource Reservation Protocol (RSVP) agent on Cisco IOS voice gateways that support Cisco CallManager 5.0.
RTP—Real-Time Transport Protocol. An Internet protocol for transmitting real-time data such as voice and video.
router—A network layer device that uses one or more metrics to determine the optimal path along which network traffic should be forwarded. Routers forward packets from one network to another on the basis of network layer information.
TE—traffic engineering. The techniques and processes used to cause routed traffic to travel through the network on a path other than the one that would have been chosen if standard routing methods had been used.
Note
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0612R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006, 2007 Cisco Systems, Inc. All rights reserved.
