Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2
Configuring COPS for RSVP
Downloads: This chapterpdf (PDF - 141.0KB) | Feedback

Configuring COPS for RSVP

Table Of Contents

Configuring COPS for RSVP

COPS for RSVP Configuration Task List

Specifying COPS Servers and Enabling COPS for RSVP

Restricting RSVP Policy to Specific Access Control Lists

Rejecting Unmatched RSVP Messages

Confining Policy to PATH and RESV Messages

Retaining RSVP Information After Losing Connection with the COPS Server

Reporting the Results of Outsourcing and Configuration Decisions

Verifying the Configuration

COPS for RSVP Configuration Examples

COPS Server Specified Example

RSVP Behavior Customized Example

Verification of the COPS for RSVP Configuration Example


Configuring COPS for RSVP


This chapter describes the tasks for configuring the COPS for RSVP feature. Common Open Policy Service (COPS) is a protocol for communicating network traffic policy information to network devices. Resource Reservation Protocol (RSVP) is a means for reserving network resources—primarily bandwidth—to guarantee that applications sending end-to-end across the Internet will perform at the desired speed and quality.

For complete conceptual information, see the section "COPS for RSVP" in the chapter "Signalling Overview" in this book.

For a complete description of the COPS for RSVP commands in this chapter, refer to the Cisco IOS Quality of Service Solutions Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index, or search online.

To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Supported Platforms" section in the "Using Cisco IOS Software" chapter in this book.

COPS for RSVP Configuration Task List

To configure COPS for RSVP, perform the tasks described in the following sections. The tasks in the first two sections are required; the tasks in the remaining sections are optional.

Specifying COPS Servers and Enabling COPS for RSVP (Required)

Restricting RSVP Policy to Specific Access Control Lists (Optional)

Rejecting Unmatched RSVP Messages (Optional)

Confining Policy to PATH and RESV Messages (Optional)

Retaining RSVP Information After Losing Connection with the COPS Server (Optional)

Reporting the Results of Outsourcing and Configuration Decisions (Optional)

Verifying the Configuration (Optional)

See the end of this chapter for the section "COPS for RSVP Configuration Examples."

Specifying COPS Servers and Enabling COPS for RSVP

To specify COPS servers and enable COPS for RSVP, use the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# configure terminal

Enters global configuration mode.

Step 2 

Router(config)# ip rsvp policy cops servers 161.44.130.168 161.44.129.6

Tells the router to request RSVP policy decisions from the first server listed, and if that fails to connect, from the next server listed. Also enables a COPS-RSVP client on the router.

Restricting RSVP Policy to Specific Access Control Lists

To restrict RSVP policy to specific access control lists (ACLs), use the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# configure terminal

Enters global configuration mode.

Step 2 

Router(config)# ip rsvp policy cops 40 160 servers 161.44.130.164 161.44.129.2

Tells the router to apply RSVP policy to messages that match ACLs 40 and 160, and specifies the servers for those sessions.

Rejecting Unmatched RSVP Messages

To reject unmatched RSVP messages, use the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# configure terminal

Enters global configuration mode.

Step 2 

Router(config)# ip rsvp policy default-reject

Tells the router to reject unmatched PATH and RESV messages, instead of just letting them pass through unadjudicated.

Confining Policy to PATH and RESV Messages

To confine policy to PATH and RESV messages, use the following commands beginning in interface configuration mode:

:

 
Command
Purpose

Step 1 

Router(config-if)# configure terminal

Enters global configuration mode.

Step 2 

Router(config)# ip rsvp policy cops minimal

Tells the router to adjudicate only PATH and RESV messages, and to accept and pass onward PATH ERROR, RESV ERROR, and RESV CONFIRM messages.

Retaining RSVP Information After Losing Connection with the COPS Server

To retain RSVP information after losing connection with the COPS server, use the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# configure terminal

Enters global configuration mode.

Step 2 

Router(config)# ip rsvp policy cops timeout 600

Tells the router to hold policy information for 10 minutes (600 seconds) while attempting to reconnect to a COPS server.

Reporting the Results of Outsourcing and Configuration Decisions

To report the results of outsourcing and configuration decisions, use the following commands beginning in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# configure terminal

Enters global configuration mode.

Step 2 

Router(config)# ip rsvp policy cops report-all

Tells the router to report to the Policy Decision Point (PDP) the success or failure of outsourcing and configuration decisions.

Verifying the Configuration

To verify the COPS for RSVP configuration, use the following commands in EXEC mode, as needed:

Command
Purpose

Router# show cops servers

Displays server addresses, port, state, keepalives, and policy client information.

Router# show ip rsvp policy cops

Displays policy server addresses, ACL IDs, and client/server connection status.

Router# show ip rsvp policy

Displays ACL IDs and their connection status.


COPS for RSVP Configuration Examples

The following sections provide COPS for RSVP configuration examples:

COPS Server Specified Example

RSVP Behavior Customized Example

Verification of the COPS for RSVP Configuration Example

For information about configuring COPS for RSVP, see the section "COPS for RSVP Configuration Task List" in this chapter.

COPS Server Specified Example

The following example specifies the COPS server and enables COPS for RSVP on the server. Both of these functions are accomplished by using the ip rsvp policy cops command. By implication, the default settings for all remaining COPS for RSVP commands are accepted.

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# ip rsvp policy cops servers 161.44.130.168 161.44.129.6
Router(config)# exit

RSVP Behavior Customized Example

Once the COPS server has been specified and COPS for RSVP has been enabled, the remaining COPS for RSVP commands can be used to customize the COPS for RSVP behavior of the router. The following example uses the remaining COPS for RSVP commands to customize the RSVP behavior of the router:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# ip rsvp policy cops 40 160 servers 161.44.130.168 161.44.129.6
Router(config)# ip rsvp policy default-reject
Router(config)# ip rsvp policy cops minimal
Router(config)# ip rsvp policy cops timeout 600
Router(config)# ip rsvp policy cops report-all
Router(config)# exit

Verification of the COPS for RSVP Configuration Example

The following examples display three views of the COPS for RSVP configuration on the router, which can be used to verify the COPS for RSVP configuration.

This example displays the policy server address, state, keepalives, and policy client information:

Router# show cops servers

COPS SERVER: Address: 161.44.135.172. Port: 3288. State: 0. Keepalive: 120 sec
Number of clients: 1. Number of sessions: 1. 
    COPS CLIENT: Client type: 1.  State: 0.

This example displays the policy server address, the ACL ID, and the client/server connection status:

Router# show ip rsvp policy cops

COPS/RSVP entry. ACLs: 40 60 
PDPs: 161.44.135.172 
Current state: Connected
Currently connected to PDP 161.44.135.172, port 0

This example displays the ACL ID numbers and the status for each ACL ID:

Router# show ip rsvp policy

Local policy: Currently unsupported
COPS: 
ACLs: 40 60 . State: CONNECTED. 
ACLs: 40 160 . State: CONNECTING.