-
- Downstream Interface Configuration
- Upstream Interface Configuration
- DOCSIS Interface and Fiber Node Configuration
- DOCSIS Load Balancing Groups
- DOCSIS Load Balancing Movements
- DOCSIS 3.0 Downstream Bonding
- DOCSIS 2.0 A-TDMA Modulation Profiles
- Downstream Resiliency Bonding Group
- Downstream Channel ID Assignment
- Upstream Channel Bonding
- Spectrum Management and Advanced Spectrum Management
- Upstream Scheduler Mode
- Generic Routing Encapsulation
- Transparent LAN Service over Cable
- Downgrading Channel Bonding in Battery Backup Mode
- Energy Management Mode
- Upstream Bonding Support for D-PON
-
- IP Access Control Lists
- Creating an IP Access List and Applying It to an Interface
- Creating an IP Access List to Filter IP Options, TCP Flags, Noncontiguous Ports
- Refining an IP Access List
- IP Named Access Control Lists
- IPv4 ACL Chaining Support
- IPv6 ACL Chaining with a Common ACL
- Commented IP Access List Entries
- Standard IP Access List Logging
- IP Access List Entry Sequence Numbering
- ACL IP Options Selective Drop
- ACL Syslog Correlation
- IPv6 Access Control Lists
- IPv6 Template ACL
- IPv6 ACL Extensions for Hop by Hop Filtering
-
- Call Home
- SNMP Support over VPNs—Context-Based Access Control
- SNMP Cache Engine Enhancement
- Onboard Failure Logging
- Control Point Discovery
- IPDR Streaming Protocol
- Usage-Based Billing (SAMIS)
- Frequency Allocation Information for the Cisco CMTS Routers
- Flap List Troubleshooting
- Maximum CPE and Host Parameters
- SNMP Background Synchronization
- Online Offline Diagnostics
- Index
- Finding Feature Information
- Hardware Compatibility Matrix for Cisco cBR Series Routers
- Prerequisites for the COPS Engine on the Cisco CMTS Routers
- Restrictions for the COPS Engine on the Cisco CMTS
- Information About the COPS Engine on the Cisco CMTS
- How to Configure the COPS Engine on the Cisco CMTS
COPS Engine
Operation
This document describes the Common Open Policy Service (COPS) engine feature on the Cisco CMTS routers. The Cisco CMTS routers also support Access control lists (ACLs) with the COPS engine.
- Finding Feature Information
- Hardware Compatibility Matrix for Cisco cBR Series Routers
- Prerequisites for the COPS Engine on the Cisco CMTS Routers
- Restrictions for the COPS Engine on the Cisco CMTS
- Information About the COPS Engine on the Cisco CMTS
- How to Configure the COPS Engine on the Cisco CMTS
- COPS Engine Configuration Examples for Cable
- Additional References
- Feature Information for COPS Engine Operation
Finding Feature Information
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.
Hardware Compatibility Matrix for Cisco cBR Series Routers
Note | The hardware components introduced in a given Cisco IOS-XE Release are supported in all subsequent releases unless otherwise specified. |
Cisco CMTS Platform |
Processor Engine |
Interface Cards |
---|---|---|
Cisco cBR-8 Converged Broadband Router |
Cisco IOS-XE Release 3.15.0S and Later Releases Cisco cBR-8 Supervisor:
|
Cisco IOS-XE Release 3.15.0S and Later Releases Cisco cBR-8 CCAP Line Cards: Cisco cBR-8 Downstream PHY Modules: Cisco cBR-8 Upstream PHY Modules: |
Prerequisites for the COPS Engine on the Cisco CMTS Routers
Restrictions for the COPS Engine on the Cisco CMTS
Information About the COPS Engine on the Cisco CMTS
Common Open Policy Service (COPS) is a protocol for communicating network traffic policy information to network devices.
COPS works in correspondence with the Resource Reservation Protocol (RSVP), which 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. RSVP is not configured on the Cisco CMTS, but the Cisco CMTS presumes RSVP on the network for these configurations.
Refer to the Additional References for further information about COPS for RSVP.
How to Configure the COPS Engine on the Cisco CMTS
This section describes the tasks for configuring the COPS for RSVP feature on the Cisco CMTS.
To configure the COPS engine on the Cisco CMTS, perform the following tasks:
- Configuring COPS TCP and DSCP Marking
- Configuring COPS TCP Window Size
- Configuring Access Control List Support for COPS Engine
- Restricting RSVP Policy to Specific Access Control Lists
- Displaying and Verifying COPS Engine Configuration on the Cisco CMTS
- Show Commands for COPS Engine Information
Configuring COPS TCP and DSCP Marking
This feature allows you to change the Differentiated Services Code Point (DSCP) marking for COPS messages that are transmitted or received by the Cisco router. The cops ip dscp command changes the default IP parameters for connections between the Cisco router and COPS servers in the cable network.
DSCP values are used in Quality of Service (QoS) configurations on a Cisco router to summarize the relationship between DSCP and IP precedence. This command allows COPS to remark the packets for either incoming or outbound connections.
The default setting is 0 for outbound connections. On default incoming connections, the COPS engine takes the DSCP value from the COPS server initiating the TCP connection.
Note | This feature affects all TCP connections with all COPS servers. |
- For messages transmitted by the Cisco router, the default DSCP value is 0.
- For incoming connections to the Cisco router, the COPS engine takes the DSCP value used by the COPS server that initiates the TCP connection, by default.
- The cops ip dscp command allows the Cisco router to re-mark the COPS packets for either incoming or outbound connections.
- This command affects all TCP connections with all COPS servers.
- This command does not affect existing connections to COPS servers. Once you issue this command, this function is supported only for new connections after that point in time.
Perform the following steps to enable optional DSCP marking for COPS messages on the Cisco CMTS.
Configuring COPS TCP Window Size
This feature allows you to override the default TCP receive window size that is used by COPS processes. This setting can be used to prevent the COPS server from sending too much data at one time.
Perform the following steps to change the TCP Window size on the Cisco CMTS.
Configuring Access Control List Support for COPS Engine
Perform the following steps to configure COPS ACLs on the Cisco CMTS.
Command or Action | Purpose | |
---|---|---|
Step 1 | enable
Example: Router> enable |
Enables privileged EXEC mode. |
Step 2 | configure
terminal
Example: Router# configure terminal |
Enters global configuration mode. |
Step 3 | cops
listeners
access-list{
acl-num
|acl-name }
Example: Router# cops listeners access-list 40 |
Configures access control lists (ACLs) for inbound connections to all COPS listener applications on the Cisco CMTS. To remove this setting from the Cisco CMTS, us the no form of this command. |
Step 4 |
exit
Example: Router(config)# exit Router# |
Returns to privileged EXEC mode. |
Access lists can be displayed by using the show access-list command in privileged EXEC mode.
Restricting RSVP Policy to Specific Access Control Lists
Perform the following steps to restrict the RSVP policy to specific ACLs, as already configured on the Cisco CMTS.
For ACL configuration, refer to the Configuring Access Control List Support for COPS Engine.
Command or Action | Purpose | |
---|---|---|
Step 1 | enable
Example: Router> enable |
Enables privileged EXEC mode. Enter your password if prompted. |
Step 2 | configure
terminal
Example: Router# configure terminal |
Enters global configuration mode. |
Step 3 |
interface
cable (slot
/subslot
/port
}
Example: Router(config)#interface cable 8/0/1 Router(config-if)# |
Enters interface configuration mode. |
Step 4 | ip rsvp policy cops
ACL-1 ACL-2
servers
iP-addr1 IP-addr2
Example: Router(config-if)# 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 the specified ACLs, and specifies the COPS server or servers for those sessions. |
Step 5 | exit
Example: Router(config)# exit Router# |
Returns to privileged EXEC mode. |
Displaying and Verifying COPS Engine Configuration on the Cisco CMTS
Once COPS is enabled and configured on the Cisco CMTS, you can verify and track configuration by using one or all of the show commands in the following steps.
Command or Action | Purpose | |
---|---|---|
Step 1 | enable
Example: Router> enable |
Enables privileged EXEC mode. Enter your password if prompted. |
Step 2 | show
cops
servers
Example: Router# show cops servers |
Displays server addresses, port, state, keepalives, and policy client information. |
Step 3 | show
ip
rsvp
policy
cops
Example: Router# show ip rsvp policy cops |
Displays policy server addresses, ACL IDs, and client/server connection status. |
Step 4 | show
ip
rsvp
policy
Example: Router# show ip rsvp policy |
Displays ACL IDs and their connection status. |
Show Commands for COPS Engine Information
The following examples display three views of the COPS engine configuration on the Cisco router. These respective show commands verify the COPS engine configuration.
- Displaying COPS Servers on the Network
- Displaying COPS Policy Information on the Network
- Displaying Access Lists for COPS
Displaying COPS Servers on the Network
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.
Displaying COPS Policy Information on the Network
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
Displaying Access Lists for COPS
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.
COPS Engine Configuration Examples for Cable
The following sections provide COPS for RSVP configuration examples on the Cisco CMTS:
Example: COPS Server Specified
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
Example: COPS Server Display
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.
Additional References
Related Documents
Related Topic |
Document Title |
---|---|
Cisco CMTS Commands |
|
COPS for RSVP |
http://www.cisco.com/en/US/docs/ios-xml/ios/qos_rsvp/configuration/12-4t/cops_rsvp.html http://www.cisco.com/en/US/docs/ios/12_1t/12_1t1/feature/guide/CopsRSVP.html |
Standards
Standard |
Title |
---|---|
PKT-SP-ESP-I01-991229 |
PacketCable™ Electronic Surveillance Specification ( http://www.packetcable.com ) |
MIBs
MIB |
MIBs Link |
---|---|
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
RFC |
Title |
---|---|
General RFC Resources |
http://www.rfc-editor.org/rfcsearch.html
|
Technical Assistance
Description |
Link |
---|---|
The Cisco Technical Support & Documentation website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. |
Feature Information for COPS Engine Operation
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http://www.cisco.com/ is not required.
Note | The below table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature. |
Feature Name |
Releases |
Feature Information |
---|---|---|
COPS Engine Operation |
Cisco IOS-XE Release 3.15.0S |
This feature was introduced on the Cisco cBR Series Converged Broadband Routers. |