Automatic application of implementation-specific configuration policies

• US 7,565,416 B1
• Filed: 04/14/2004
• Issued: 07/21/2009
• Est. Priority Date: 04/14/2004
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Enns, Robert P., Shafer, Philip A.
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): MADAMBA, GLENFORD J
• Application Number:
  US10/824,276
• Time in Patent Office: 1,924 Days
• Field of Search: 709/220
• US Class Current: 709/220
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0866 Checking the configuration
• 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

Techniques are described for application of implementation-specific configuration policies within a network device. For example, a device, such as a router, may comprise memory to store operational configuration data and candidate configuration data. The device further includes a control unit to apply changes to the candidate configuration data based on input from a client, and apply an implementation-specific configuration policy to a copy of the changed candidate configuration data. Based on a result of applying the implementation-specific configuration policy, the device selectively commits the changes made to the candidate configuration to the operational configuration. In the event an error occurs while applying the implementation-specific configuration policy, the device does not commit the changes to the operational configuration. In this manner, the device does not allow changes that violate the implementation-specific configuration policy to be committed to the operational configuration, thereby detecting misconfiguration that may otherwise be syntactically and semantically correct.

Claims

1. A method comprising:

applying, with a network device, changes to candidate configuration data of the network device;

applying an implementation-specific configuration policy to validate the changed candidate configuration data for compliance with specific operational requirements of the particular networks within which the network device operates, wherein the implementation-specific configuration policy comprises a set of user-defined rules representing the specific operational requirements; and

selectively committing the changed candidate configuration data to operational configuration data based on a result of the validation.

2. The method of claim 1, wherein applying an implementation-specific configuration policy comprises:

identifying an error within the changed candidate configuration data based on the implementation-specific configuration policy; and

correcting the error by automatically altering the changed candidate configuration data in response to the identified error.

3. The method of claim 1, wherein applying an implementation-specific configuration policy comprises:

identifying a warning condition within the changed candidate configuration data based on the implementation-specific configuration policy; and

correcting the warning condition by automatically altering the changed candidate configuration data.

4. The method of claim 1, wherein applying an implementation-specific configuration policy comprises:

receiving a commit command; and

automatically applying the implementation-specific configuration policy in response to receiving the commit command.

5. The method of claim 1, wherein selectively committing the changes includes committing the changes to the operational configuration when application of the implementation-specific configuration policy results in generation of a warning.

6. The method of claim 1, wherein selectively committing the changes includes automatically rejecting the changes when application of the implementation-specific configuration policy results in an error.

7. The method of claim 1, wherein applying an implementation-specific configuration policy comprises:

generating a copy of the candidate configuration data; and

applying the implementation-specific configuration policy to the copy of the candidate configuration.

8. The method of claim 7, wherein applying an implementation-specific configuration policy to the copy of the candidate configuration occurs via a Extensible Markup Language (XML) Application Program Interface (API).

9. The method of claim 7,

wherein generating a copy of the candidate configuration data comprises generating a version of the candidate configuration data that conforms to an Extensible Markup Language, and

wherein applying an implementation-specific configuration policy comprises applying an Extensible Style Language Transformation (XSLT) script to the copy of the candidate configuration data.

10. The method of claim 1, wherein the implementation-specific configuration policy comprises an Extensible Style Language Transformation (XSLT) script.

11. The method of claim 1, wherein the implementation-specific configuration policy is user-definable by a client, the method further comprising:

receiving input from the client; and

updating the implementation-specific configuration policy based on the input.

12. The method of claim 1, further comprising:

receiving the changes from a client associated with an authorization level; and

selecting the implementation-specific configuration policy from a plurality of implementation-specific configuration policies based on the determined authorization level.

13. The method of claim 12, further comprising:

receiving identification information from the client; and

determining the authorization level based on the identification information.

14. The method of claim 13, wherein identification information includes a password and a username.

41. The method of claim 1, wherein the specific operational requirements comprise one or more policies to allocate bandwidth to users based on Quality of Service (QoS) specifications of a service level agreement.

42. The method of claim 1, wherein the specific operational requirements comprise one or more policies to allocate bandwidth to users based on contracts between the users and a service provider.

15. A system comprising:

a memory to store operational configuration data and candidate configuration data; and

a control unit to apply an implementation-specific configuration policy to validate changes to the candidate configuration data for compliance with specific operational requirements of the particular networks within which the system operates, and selectively commit the changed candidate configuration data to the operational configuration data based on a result of the validation, wherein the implementation-specific configuration policy comprises a set of user-defined rules representing the specific operational requirements.

16. The system of claim 15, wherein the control unit applies an implementation-specific configuration policy by generating an error based on the implementation-specific configuration policy, and selectively correcting the error by altering the changed candidate configuration data based on the error.

17. The system of claim 15, wherein the control unit applies an implementation-specific configuration policy by identifying a warning condition based on the implementation-specific configuration policy, and altering the changed candidate configuration data based on the warning condition.

18. The system of claim 15,

wherein the control unit comprises a management interface to apply the implementation-specific configuration policy, and

wherein the management interface receives a commit command, and automatically applies the implementation-specific policy in response to receiving the commit command.

19. The system of claim 18, wherein the management interface selectively commits the changed candidate configuration data to the operational configuration when application of the implementation-specific configuration policy results in generation of a warning.

20. The system of claim 18, wherein the management interface automatically rejects the changes when application of the implementation-specific configuration policy results in an error.

21. The system of claim 15, wherein the control unit comprises a management interface to apply the implementation-specific configuration policy by generating a copy of the candidate configuration data and applying the implementation-specific configuration policy to the copy of the candidate configuration.

22. The system of claim 21, wherein the management interface comprises an Extensible Markup Language (XML) Application Program Interface (API) to apply the implementation-specific configuration policy to the copy of the candidate configuration.

23. The system of claim 21,

wherein the management interface comprises an Extensible Markup Language (XML) generator to generate the copy of the candidate configuration data, wherein the copy of the candidate configuration data includes a version of the candidate configuration data that conforms to the Extensible Markup Language, and

wherein the management interface applies an implementation-specific configuration policy comprising an Extensible Style Language Transformation (XSLT) script to the copy of the candidate configuration data.

24. The system of claim 15, wherein the implementation-specific configuration policy comprises an implementation-specific configuration policy defined by a client and wherein the control unit comprises a management interface to receive input from the client and update the implementation-specific configuration policy based on the input.

25. The system of claim 15, wherein the control unit comprises a management interface to receive the changes from a client associated with an authorization level and select the implementation-specific configuration policies based on the determined authorization level.

26. The system of claim 25, wherein the management interface comprises a command line interface to receive identification information from the client and a management module to determine the authorization level based on the identification information.

27. The system of claim 26, wherein identification information includes a password and a username.

43. The system of claim 15, wherein the specific operational requirements comprise one or more policies to allocate bandwidth to users based on Quality of Service (QoS) specifications of a service level agreement.

44. The system of claim 15, wherein the specific operational requirements comprise one or more policies to allocate bandwidth to users based on contracts between the users and a service provider.

28. A computer-readable medium comprising instructions to cause a processor to:

apply changes to candidate configuration data of a network device;

apply an implementation-specific configuration policy to validate the changed candidate configuration data for compliance with specific operational requirements of the particular networks within which the network device operates, wherein the implementation-specific configuration policy comprises a set of rules representing the specific operational requirements; and

selectively commit the changed candidate configuration data to the operational configuration data based on a result of the validation.

29. The computer-readable medium of claim 28, further comprising instructions to cause the processor to apply an implementation-specific configuration policy by generating an error based on the implementation-specific configuration policy, and selectively correcting the error by altering the changed candidate configuration data based on the error.

30. The computer-readable medium of claim 28, further comprising instructions to cause the processor to apply an implementation-specific configuration policy by generating an warning based on the implementation-specific configuration policy, and selectively correcting the warning by altering the changed candidate configuration data based on the warning.

31. The computer-readable medium of claim 28, further comprising instructions to cause the processor to:

receive a commit command; and

automatically apply the implementation-specific policy in response to receiving the commit command.

32. The computer-readable medium of claim 28, further comprising instructions to cause the processor to commit the changes to the operational configuration when application of the implementation-specific configuration policy results in generation of a warning.

33. The computer-readable medium of claim 28, further comprising instructions to cause the processor to automatically reject the changes when application of the implementation-specific configuration policy results in an error.

34. The computer-readable medium of claim 28, further comprising instructions to cause the processor to:

generate a copy of the candidate configuration data; and

apply the implementation-specific configuration policy to the copy of the candidate configuration.

35. The computer-readable medium of claim 34, further comprising instruction to cause the processor to apply an implementation-specific configuration policy to the copy of the candidate configuration via a Extensible Markup Language (XML) Application Program Interface (API).

36. The computer-readable medium of claim 34, further comprising instructions to cause the processor to generate a version of the candidate configuration data that conforms to an Extensible Markup Language.

37. The computer-readable medium of claim 36, wherein the implementation-specific configuration policy includes an Extensible Style Language Transformation script and further comprising instructions to cause the processor to apply the Extensible Style Language Transformation (XSLT) script to the copy of the candidate configuration data.

38. The computer-readable medium of claim 28, wherein the implementation-specific configuration policy comprises a user-definable implementation-specific configuration policy, and the computer-readable medium further comprises instructions to cause the processor to receive input from a client and update the implementation-specific configuration policy based on the input.

39. The computer-readable medium of claim 28, further comprising instructions to cause the processor to:

receive the changes from a client associated with an authorization level; and

select the implementation-specific configuration policy based on the determined authorization level.

40. The computer-readable medium of claim 39, further comprising instructions to cause the processor to:

receive identification information from the client; and

determine the authorization level based on the identification information.

45. The computer-readable medium of claim 28, wherein the specific operational requirements comprise one or more policies to allocate bandwidth to users based on Quality of Service (QoS) specifications of a service level agreement.

46. The computer-readable medium of claim 28, wherein the specific operational requirements comprise one or more policies to allocate bandwidth to users based on contracts between the users and a service provider.