Validating a routing function

• US 9,742,660 B2
• Filed: 01/28/2015
• Issued: 08/22/2017
• Est. Priority Date: 01/28/2015
• Status: Active Grant

• Current Assignee: Metaswitch Networks Limited (Microsoft Corporation)
• Original Assignee: Metaswitch Networks Limited (Microsoft Corporation)
• Inventors: Liljenstolpe, Christopher, Wingrove, Simon, Curtis, Michael, Denham, Tom, Tiplady, Paul, Pollitt, Alex
• Primary Examiner(s): Lazaro, David
• Application Number:
  US14/608,078
• Publication Number:
  US 20160218964A1
• Time in Patent Office: 937 Days
• Field of Search: 709220, 709238
• 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
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 45/14 Routing performance; Theoretical aspects
• CPC Class Codes: H04L 45/56 Routing software

Abstract

Certain examples described herein provide a system and method for validating a routing function for a network device. In one example, a network device has a run-time policy engine, wherein the run-time policy engine implements a routing configuration file and the routing configuration file defines a routing function for network traffic. A file editor is also provided that loads the routing configuration file. The file editor has an editor policy engine that duplicates a functionality of the run-time policy engine. In one example, the routing configuration file has at least one validation portion that has one or more route statements with definitions indicative of expected routing function behavior. The file editor parses the routing configuration file by implementing the routing configuration file using the editor policy engine. The editor policy engine applies the routing function defined by the routing configuration file to the one or more route statements and indicates where a result of the routing function does not conform to the definitions indicative of expected routing function behavior. These examples may help to reduce routing errors due to configuration errors in network devices.

Claims

1. A system for validating a routing function for a network device, the system comprising:

the network device, wherein the network devices comprises;

a network interface for receiving data packets from a network,

a run-time policy engine, and

a memory to store a routing configuration file,

wherein the run-time policy engine implements the routing configuration file to configure the network device to selectively forward data packets over the network via the network interface,

the routing configuration file comprising one or more subroutine statements that define a routing function for network traffic; and

a file editor arranged to load and edit the routing configuration file,

the file editor comprising an editor policy engine that duplicates a functionality of the run-time policy engine,

wherein the routing configuration file further comprises at least one validation portion, the validation portion comprising one or more route statements defining possible routes for data packets within the network, the one or more route statements having definitions indicative of expected routing function behavior for the one or more routes,

wherein, following an edit of the routing configuration file;

the file editor is arranged to parse the routing configuration file by implementing the routing configuration file using the editor policy engine, and

the editor policy engine is arranged to apply the routing function defined by the one or more subroutine statements of the routing configuration file to the one or more route statements and to indicate where a result of the routing function for the one or more routes does not conform to the definitions in the validation portion of the routing configuration file that are indicative of expected routing function behavior.

2. The system of claim 1, comprising:

a library of functions to implement the functionality of the run-time policy engine,

wherein the library of functions are callable from both the run-time policy engine and the editor policy engine.

3. The system of claim 1, wherein file editor is configured to implement the one or more route statements as respective route objects and the run-time policy engine and the editor policy engine are configured to implement the routing configuration file by converting at least a portion of the routing configuration file into the routing function, the routing function being arranged to receive a route object as a variable and to return an indication of whether the route object is accepted or rejected.

4. The system of claim 1, wherein the file editor comprises:

a tracing engine configured to output a result of applying one or more policy command statements in the routing configuration file to one or more routes.

5. The system of claim 4, wherein the tracing engine is activated using one or more trace statements in the routing configuration file, the one or more trace statements comprising one or more conditions to filter the routes that are traced.

6. The system of claim 5, wherein said one or more conditions comprise:

a configurable proportion of routes to be traced, said routes being sampled from a set of routes that are processed by the routing function according to the configurable proportion;

or

an initial number of routes to be traced, the tracing engine being configured to be deactivated after the initial number of routes have been traced.

7. A method for validating a routing function for a network device comprising:

loading a routing configuration file for a network device,

the routing configuration file comprising one or more subroutine statements that define a routing function,

the routing configuration file being implemented by a policy engine,

the policy engine being used by the network device to provide the routing function based on the routing configuration file and to configure the network device to selectively forward data packets over a network;

parsing at least one validation portion of the routing configuration file,

the validation portion comprising one or more route statements defining possible network routes for data packets, the one or more route statements having definitions indicative of expected routing function behavior for the one or more routes,

the parsing including;

implementing the one or more subroutine statements of the routing configuration file using the policy engine to apply the routing function to the one or more routes defined by the one or more route statements; and

indicating where a result of the routing function as applied to the one or more routes does not conform to the definitions in the validation portion of the routing configuration file that are indicative of expected routing function behavior.

8. The method of claim 7, wherein implementing the routing configuration file comprises:

loading the policy engine; and

passing the routing configuration file to the policy engine.

9. The method of claim 7, wherein indicating where a result of the routing function does not conform to the definitions comprises:

inserting error text into the routing configuration file where a result of the routing function does not conform to the definitions indicative of expected routing function behavior; and

displaying the routing configuration file including the error text on a display device.

10. The method of claim 7, wherein implementing the routing configuration file comprises:

parsing the routing configuration to implement the routing function;

parsing the one or more route statements;

converting the one or more route statements into respective route objects; and

applying the routing function to the each of the route objects to output the result of the routing function,

and wherein indicating where a result of the routing function does not conform to the definitions comprises;

comparing the result of the routing function to the definitions indicative of expected routing function behavior.

11. The method of claim 7, wherein the result of the routing function comprises a variable indicating whether a route object is accepted or rejected and the definitions indicative of expected routing function behavior comprise an indication of whether a route statement is to be accepted or rejected.

12. The method of claim 11, wherein the result of the routing function comprises an indication of one or more modifications to an accepted route object and the definitions indicative of expected routing function behavior comprise an indication of allowed modifications.

13. The method of claim 7, comprising:

implementing the routing configuration file on the network device.

14. The method of claim 13, wherein loading, parsing and indicating are performed by an editor policy engine of a file editor and implementing is performed by a run-time policy engine of the network device, the editor policy engine duplicating a functionality of the run-time policy engine.

15. The method of claim 7, comprising:

outputting a trace of a result of one or more sub-functions of the routing function when implementing the routing configuration file.

16. The method of claim 7, wherein

the routing configuration file comprises one or more changes to a routing configuration file in use by the network device,

the one or more route statements define network routes that are processed by the network device, and

the definitions indicative of expected routing function behavior comprise routing function behavior of the network device in operation.

17. The method of claim 7, wherein the routing configuration file comprises a modified routing configuration file and wherein indicating where a result of the routing function does not conform to the definitions indicative of expected routing function behavior comprises:

comparing the result of the routing function with an output generated by a routing function implemented by way of an original routing configuration file;

authorizing use of the modified routing configuration file in the network device based on the comparing.

18. The method of claim 7, comprising:

accessing a remote computer device to view an output indicating where a result of the routing function does not conform to the definitions indicative of expected routing function behavior,

wherein the remote computer device performs the loading, parsing and indicating and wherein the remote computer device is communicatively coupled to the network device.

19. The method of claim 7, wherein the routing configuration file implements a Border Gateway Protocol policy.

20. A non-transitory computer-readable storage medium comprising computer-executable instructions, which, when executed by a processor, cause a computing device to perform a method of validating a routing function, the method comprising:

loading a routing configuration file for a network device,

the routing configuration file comprising one or more subroutine statements that define a routing function,

the routing configuration file being implemented by a policy engine,

the policy engine being used by the network device to provide the routing function based on the routing configuration file and to configure the network device to selectively forward data packets over a network;

parsing at least one validation portion of the routing configuration file,

the validation portion comprising one or more route statements defining possible network routes for data packets, the one or more route statements having definitions indicative of expected routing function behavior for the one or more routes,

the parsing including;

implementing the one or more subroutine statements of the routing configuration file using the policy engine to apply the routing function to the one or more routes defined by the one or more route statements; and

indicating where a result of the routing function as applied to the one or more routes does not conform to the definitions in the validation portion of the routing configuration file that are indicative of expected routing function behavior.