Method and apparatus for communicating COPS protocol policies to non-COPS-enabled network devices

• US 7,991,907 B2
• Filed: 10/06/2004
• Issued: 08/02/2011
• Est. Priority Date: 01/14/2000
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: McCloghrie, Keith, Parnafes, Itzhak, Mohaban, Shai
• Primary Examiner(s): Vaughn, Jr.; William C
• Assistant Examiner(s): Cheema; Umar
• Application Number:
  US10/960,162
• Publication Number:
  US 20050060393A1
• Time in Patent Office: 2,491 Days
• Field of Search: 709/230, 709/232, 709/220, 709/228, 370/466, 370/467
• US Class Current: 709/232
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management

Abstract

A method and apparatus for communicating a COPS protocol policy to a non-COPS-enabled network device is provided. A COPS proxy is connected between a policy server and a non-COPS-enabled network device. The policy server is configured to communicate COPS protocol policies to the COPS proxy, which is, in turn, configured to translate the COPS protocol policy into a policy that is in accordance with a policy protocol that the non-COPS-enabled network device can receive and correctly interpret (“non-COPS protocol”). The translation of the policy utilizes a mapping database that delineates predetermined relationships between COPS protocol policies and the non-COPS protocol policies. More specifically, the mapping database can include relationships between COPS protocol policy information base variables, network device roles and characteristics, and non-COPS protocol parameters and associated values. Further, the COPS proxy can be configured to detect and reconcile policy conflicts for one or more network devices.

Claims

1. A method of communicating one or more quality of service roles that should be assigned to a non-COPS enabled network device but that cannot be communicated in accordance with a common open policy service (COPS) protocol to the non-COPS enabled network device, comprising:

receiving a first set of device data about the non-COPS enabled network device, wherein the first set of device data identifies one or more appropriate non-COPS protocols that are supported by the non-COPS enabled network device for communicating the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

receiving a set of COPS data that describes how the one or more quality of service roles should be assigned to the non-COPS enabled network device, wherein the set of COPS data is configured using the COPS protocol;

receiving a set of role data that describes the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

generating a policy, using the set of COPS data and the set of role data, for assigning the one or more quality of service roles to the non-COPS enabled network device;

if the one or more quality of service roles of the non-COPS enabled network device cause conflicts in generating the policy, resolving any conflicts arising from generating the policy using the set of COPS data and the set of role data; and

communicating the policy to the non-COPS enabled network device using one of the one or more appropriate non-COPS protocols that are supported by the non-COPS enabled network device for communicating the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

wherein after assigning the one or more quality of service roles to the non-COPS enabled network device, the non-COPS enabled network device becomes a backbone interface to a background of the network, a fast link device, or an Ethernet ring protection switching node while remaining the non-COPS enabled network device;

wherein the method is performed by one or more computer processors.

2. A method as recited in claim 1, wherein the first set of device data includes data that identifies the IOS version of the non-COPS enabled network device or interface features of the non-COPS enabled network device.

3. A method as recited in claim 1, wherein the step of generating the policy comprises generating the policy for use with the CLI protocol.

4. A method as recited in claim 1, wherein the step of generating the policy comprises generating the policy for use with the SNMP protocol.

5. A method as recited in claim 1, wherein the first set of device data comprises data that identifies at least one role to which the non-COPS enabled network device has been assigned.

6. A method as recited in claim 1, wherein the step of receiving the set of COPS data comprises receiving data that identifies at least two conflicting COPS policies, and wherein the step of generating the policy comprises the step of resolving the at least two conflicting COPS policies.

7. A non-transitory computer readable storage medium storing program instructions for communicating a common open policy service (COPS) protocol data to a non-COPS enabled network device, wherein when the computer readable medium is read by a computer system having a processor and memory, the program instructions are configured to be executed by the processor, the computer readable medium comprising:

program instructions for receiving a first set of device data about the non-COPS enabled network device, wherein the first set of device data identifies one or more appropriate non-COPS protocols that are supported by the non-COPS enabled network device for communicating one or more quality of service roles that should be assigned to the non-COPS enabled network device;

program instructions for receiving a set of COPS data that describe how the one or more quality of service roles should be assigned to the non-COPS enabled network device, wherein the set of COPS data is configured using the COPS protocol;

program instructions for receiving a set of role data that describe the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

program instructions for generating a policy by using the set of COPS data and the set of role data, wherein the set of role data assigns the one or more quality of service roles to the non-COPS enabled network device;

program instructions configured to determine if the one or more quality of service roles of the non-COPS enabled network device cause conflicts in generating the policy, resolving any conflicts arising from generating the policy using the set of COPS data and the set of role data; and

program instructions for communicating the policy to the non-COPS enabled network device using one of the one or more appropriate non-COPS protocols that are supported by the non-COPS enabled network device for communicating the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

wherein after assigning the one or more quality of service roles to the non-COPS enabled network device, the non-COPS enabled network device becomes a backbone interface to a background of the network, a fast link device, or an Ethernet ring protection switching node while remaining the non-COPS enabled network device.

8. A non-transitory computer readable storage medium as recited in claim 7, wherein the program instructions for the first set of device data comprises data that identifies the IOS version of the non-COPS enabled network device or interface features of the non-COPS enabled network device.

9. A non-transitory computer readable storage medium as recited in claim 7, wherein the program instructions for generating the policy include program instructions for generating the policy for use with the CLI protocol.

10. A non-transitory computer readable storage medium as recited in claim 7, wherein the program instructions for generating the policy include program instructions for generating the policy for use with the SNMP protocol.

11. A non-transitory computer readable storage medium as recited in claim 7, wherein the first set of device data comprises data that identifies at least one role to which the non-COPS enabled network device has been assigned.

12. A non-transitory computer readable storage medium as recited in claim 7, wherein the set of COPS data comprises data that identifies at least two conflicting COPS policies, and wherein the program instructions for generating the policy comprises program instructions for resolving the at least two conflicting COPS policies.

13. A system for communicating a common open policy service (COPS) protocol data to a non-COPS enabled network device, comprising:

one or more computer processors;

a communication receiver configured to receive a first set of device data about the non-COPS enabled network device from the non-COPS enabled network device and a set of COPS data from a policy server, wherein the first set of device data identifies one or more appropriate non-COPS protocols that are supported by the non-COPS enabled network device for communicating one or more quality of service roles that should be assigned to the non-COPS enabled network device, wherein the set of COPS data describes how the one or more quality of service roles should be assigned to the non-COPS enabled network device, wherein the set of COPS data is configured using the COPS protocol, wherein the communication receiver is configured to receive a set of role data that describes the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

a policy translator configured to translate the set of COPS data and the set of role data into a policy, and configured to resolve any conflicts arising from generating the policy using the set of COPS data and the set of role data if the one or more quality of service roles of the non-COPS enabled network device cause conflicts in generating the policy, wherein the policy is receivable and correctly interpretable by the non-COPS enabled network device; and

a communication transmitter configured to transmit the policy to the non-COPS enabled network device, wherein the policy is transmitted using the one of the one or more appropriate non-COPS protocols that are supported by the non-COPS enabled network device for communicating the one or more quality of service roles that should be assigned to the non-COPS enabled network device;

wherein after assigning the one or more quality of service roles to the non-COPS enabled network device, the non-COPS enabled network device becomes a backbone interface to a background of the network, a fast link device, or an Ethernet ring protection switching node while remaining the non-COPS enabled network device.

14. A system as recited in claim 13, wherein the policy translator comprises a mapping database, wherein the mapping database comprises data that identifies predetermined correlations between the policy, the set of COPS data, and the first set of device data.

15. A system as recited in claim 13, wherein the first set of device data comprises data that identifies one or more roles associated with the non-COPS enabled network device.

16. A system as recited in claim 13, wherein the first set of device data includes data that identifies the IOS version of the non-COPS enabled network device or interface features of the non-COPS enabled network device.

17. A system as recited in claim 13, wherein the policy is translated by policy translator for use with the CLI protocol.

18. A system as recited in claim 13, wherein the policy is translated by policy translator for use with the SNMP protocol.