FEEDBACK LOOP FOR SERVICE ENGINEERED PATHS

• US 20140003232A1
• Filed: 06/27/2012
• Published: 01/02/2014
• Est. Priority Date: 06/27/2012
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Guichard, James, Ward, David, Medved, Jan, Konstantynowicz, Maciek
• Granted Patent: US 9,143,557 B2
• Time in Patent Office: Days
• US Class Current: 370/230
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1025 Dynamic adaptation of the criteria on which the server selection is based
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

In general, techniques are described for providing feedback loops for service engineered paths. A service node comprising an interface and a control unit may implement the techniques. The interface receives traffic via a path configured within a network to direct the traffic from an ingress network device of the path to the service node. The control unit applies one or more services to the traffic received via the path and generates service-specific information related to the application of the one or more services to the traffic. The interface then sends the service-specific information to at least one network device configured to forward the traffic via the path so that the at least one network device configured to forward the traffic via the path is able to adapt the path based on the service-specific information.

Claims

1. A method comprising:

receiving, with a service node of a network, traffic via a path configured within the network to direct the traffic from an ingress network device of the path to the service node, wherein the path includes filters that control admission of the traffic at the ingress network device to the path;

applying, with the service node, one or more services to the traffic received via the path;

generating, with the service node, service-specific information related to the application of the one or more services to the traffic by the service node; and

sending, with the service node, the service-specific information to at least one network device configured to forward the traffic along the path so that the at least one network device configured to forward the traffic along the path adapts the path based on the service-specific information.

2. The method of claim 1, wherein sending the service-specific information comprises sending the service-specific information to the at least one network device configured to forward the traffic via the path using a field of one or more of an Intermediate System to Intermediate System (IS-IS) routing protocol, an Open Shortest Path First (OSPF) routing protocol a Border Gateway Protocol (BGP) and a simple network management protocol (SNMP).

3. The method of claim 1, wherein sending the service-specific information comprises sending the service-specific information to the at least one network device configured to forward the traffic via the path in a generic information type-length-value (GENINFO TLV) field specified in accordance with an Intermediate System to Intermediate System (IS-IS) routing protocol.

4. The method of claim 1, wherein the path comprises a path configured through the network in accordance with configuration data specified by an orchestrating device that computes and configures paths through the network and that does not forward any data through the network other than that used to compute and configure the paths through the network.

5. The method of claim 1, wherein sending the service-specific information comprises sending the service-specific information to the at least one network device configured to forward the traffic via a feedback loop mechanism so as to enable the at least one network device configured to forward the traffic via the path is able to adapt the path based on the service-specific information.

6. The method of claim 1,

wherein applying one or more services comprises applying one or more of a uniform resource locator (URL) filtering service, and

wherein generating, with the service node, service-specific information comprises generating service-specific information describing one or more of a filter by-pass state for the URL filtering service.

7. The method of claim 1,

wherein applying one or more services comprises applying the one or more services to flows associated with a set of one or more virtual private networks (VPNs),

wherein the method comprises determining that the set of one or more VPNs has changed such that one or more of the VPNs of the set of one or more VPNs is removed or one or more new VPNs are added to the set of one or more VPNs,

wherein generating, with the service node, service-specific information comprises generating service-specific information describing the change to the set of one or more VPNs.

8. The method of claim 1,

wherein generating, with the service node, service-specific information comprises generating service-specific information describing one or more of execution results of the applied one or more services and service state information between the at least one network device configured to forward the traffic along the path and the service node, and

wherein the service state information comprises one or more of a current load and performance between the at least one network device configured to forward the traffic along the path and the service node.

9. The method of claim 1,

wherein the service node includes a control plane, a forwarding plane and a service plane,

wherein applying the one or more services comprises applying, with one or more service modules of the service plane, the one or more services to the traffic received via the path,

wherein generating the service-specific information comprises:

executing a service monitoring module in the control plane of the service node that monitors the application of the one or more services by the one or more service modules; and

based on the monitoring of the application of the one or more services by the one or more service modules, generating, with the service monitoring module, the service specific information related to the application of the one or more services to the traffic by the service node, and

wherein sending the service-specific information comprises sending, with the forwarding plane of the service node, the service-specific information to at least one network device configured to forward the traffic along the path so that the at least one network device configured to forward the traffic along the path adapts the path based on the service-specific information.

10. The method of claim 1, wherein sending the service-specific information comprises sending the service-specific information to the at least one network device configured to forward the traffic via the path using a field of a link-state routing protocol.

11. A service node comprising:

at least one interface that receives traffic via a path configured within a network to direct the traffic from an ingress network device of the path to the service node, wherein the path includes filters that control admission of the traffic at the ingress network device to the path; and

a control unit that applies one or more services to the traffic received via the path and generates service-specific information related to the application of the one or more services to the traffic,

wherein the at least one interface sends the service-specific information to at least one network device configured to forward the traffic via the path so that the at least one network device configured to forward the traffic via the path is able to adapt the path based on the service-specific information.

12. The service node of claim 11, wherein the at least one interface sends the service-specific information to the at least one network device configured to forward the traffic via the path using a field of one or more of an Intermediate System to Intermediate System (IS-IS) routing protocol, an Open Shortest Path First (OSPF) routing protocol a Border Gateway Protocol (BGP) and a simple network management protocol (SNMP).

13. The service node of claim 11, wherein the at least one interface sends the service-specific information to the at least one network device configured to forward the traffic via the path in a generic information type-length-value (GENINFO TLV) field specified in accordance with an Intermediate System to Intermediate System (IS-IS) routing protocol.

14. The service node of claim 11, wherein the path comprises a path configured through the network in accordance with configuration data specified by an orchestrating device that computes and configures paths through the network and that does not forward any data through the network other than that used to compute and configure the paths through the network.

15. The service node of claim 11, wherein the at least one interface sends the service-specific information to the at least one network device configured to forward the traffic via a feedback loop mechanism so as to enable the at least one network device configured to forward the traffic via the path is able to adapt the path based on the service-specific information.

16. The service node of claim 11, wherein the control unit includes:

a service module that applies one or more of a uniform resource locator (URL) filtering service; and

a service monitoring module that generates service-specific information describing one or more of a filter by-pass state for the URL filtering service.

17. The service node of claim 11, wherein the control unit includes:

one or more service modules that apply the one or more services to flows associated with a set of one or more virtual private networks (VPNs); and

a service monitoring module that determines that the set of one or more VPNs has changed such that one or more of the VPNs of the set of one or more VPNs is removed or one or more new VPNs are added to the set of one or more VPNs and generates service-specific information describing the change to the set of one or more VPNs.

18. The service node of claim 11, wherein the control unit includes:

a service monitoring module that generates service-specific information describing one or more of execution results of the applied one or more services and service state information between the at least one network device configured to forward the traffic along the path and the service node, and

wherein the service state information comprises one or more of a current load and performance between the at least one network device configured to forward the traffic along the path and the service node.

19. The service node of claim 11,

wherein the control unit includes a control plane, a forwarding plane and a service plane,

wherein the service plane includes one or more service modules that apply the one or more services to the traffic received via the path,

wherein the control plane executes a service monitoring module that monitors the application of the one or more services by the one or more service modules and, based on the monitoring of the application of the one or more services by the one or more service modules, generates the service specific information related to the application of the one or more services to the traffic by the service node, and

wherein the forwarding plane includes the at least one interface that sends the service-specific information to at least one network device configured to forward the traffic along the path so that the at least one network device configured to forward the traffic along the path adapts the path based on the service-specific information.

20. The service node of claim 11, wherein the at least one interface sends the service-specific information to the at least one network device configured to forward the traffic via the path using a field of a link-state routing protocol.

21. A non-transitory computer-readable medium comprising instructions that, when executed, cause one or more processors of a service node of a network to:

receive traffic via a path configured within the network to direct the traffic from an ingress network device of the path to the service node, wherein the path includes filters that control admission of the traffic at the ingress network device to the path;

apply one or more services to the traffic received via the path;

generate service-specific information related to the application of the one or more services to the traffic; and

send the service-specific information to at least one network device configured to forward the traffic via the path so that the at least one network device configured to forward the traffic via the path is able to adapt the path based on the service-specific information.

22. A method comprising:

configuring a path in a control unit of a network device by which to forward traffic from an ingress network device to a service node based on configuration data specified by an orchestrating device that computes and configures paths through the network and that does not forward any traffic through the network other than that used to compute and configure the paths through the network;

forwarding the traffic along the path with the configured control unit to enable the service node to apply one or more services to the traffic;

receiving, with the network device, service-specific information related to the application of the one or more services by the service node to the traffic;

re-configuring the path in the control unit of the network device based on the received service-specific information.

23. The method of claim 22, wherein receiving the service-specific information comprises receiving the service-specific information via a field of one or more of an Intermediate System to Intermediate System (IS-IS) routing protocol, an Open Shortest Path First (OSPF) routing protocol, a Border Gateway Protocol (BGP) and a simple network management protocol (SNMP).

24. The method of claim 22, wherein receiving the service-specific information comprises receiving the service-specific information in a generic information type-length-value (GENINFO TLV) field specified in accordance with an Intermediate System to Intermediate System (IS-IS) routing protocol.

25. The method of claim 22,

wherein the network device comprises the ingress network device to the path,

wherein configuring the path comprises configuring the control unit of the network device to include one or more filters that control admission of traffic to the path,

wherein the service-specific information comprises service-specific information describing a filter by-pass state for a URL filtering service applied by the service node to the traffic, and

wherein re-configuring the path comprises re-configuring the filters that control admission of the traffic to the path based on the service-specific information describing the filter by-pass state for the URL filtering service.

26. The method of claim 22,

wherein the network device comprises the ingress network device to the path,

wherein configuring the path comprises configuring the control unit of the network device to include one or more filters that control admission of traffic to the path such that only traffic associated with a set of one or more virtual private networks (VPNs) is admitted to the path,

wherein the service-specific information comprises service-specific information describing a change to the set of the one or more VPNs, and

wherein re-configuring the path comprises re-configuring the filters that control admission of the traffic to the path based on the service-specific information describing the change to the set of one or more VPNs.

27. The method of claim 22,

wherein the network device comprises the ingress network device to the path,

wherein configuring the path comprises configuring the control unit of the network device to include one or more filters that control admission of traffic to the path,

wherein the service-specific information comprises service-specific information describing a firewall context for a firewall service applied by the service node to the traffic, and

wherein re-configuring the path comprises re-configuring the filters that control admission of the traffic to the path based on the service-specific information describing the firewall context for the VPN service.

28. The method of claim 22,

wherein the service-specific information comprises service-specific information describing one or more of execution results of the applied one or more services and service state information between the at least one network device configured to forward the traffic along the path and the service node, wherein the service state information comprises one or more of a current load and performance between the network device and the service node, and

wherein re-configuring the path comprises re-configuring the path to forward at least some of the traffic from the ingress network device to a different service node based on the service-specific information describing one or more of a current load and performance between the network device and the service node.

29. The method of claim 22, wherein receiving the service-specific information comprises receiving the service-specific information via a field of a link state routing protocol.

30. A network device comprising:

a control unit configured to forward traffic along a path from an ingress network device to a service node in accordance with configuration data specified by an orchestrating device that computes and configures paths through the network and that does not forward any traffic through the network other than that used to compute and configure the paths through the network; and

at least one interface that forwards the traffic along the path to enable the service node to apply one or more services to the traffic and receives service-specific information related to the application of the one or more services by the service node to the traffic,

wherein the control unit re-configures the path based on the received service-specific information.

31. The network device of claim 30, wherein the at least one interface receives the service-specific information via a field of one or more of an Intermediate System to Intermediate System (IS-IS) routing protocol, an Open Shortest Path First (OSPF) routing protocol, a Border Gateway Protocol (BGP) and a simple network management protocol (SNMP).

32. The network device of claim 30, wherein the at least one interface receives the service-specific information in a generic information type-length-value (GENINFO TLV) field specified in accordance with an Intermediate System to Intermediate System (IS-IS) routing protocol.

33. The network device of claim 30,

wherein the network device comprises the ingress network device to the path,

wherein the control unit configures one or more filters that control admission of traffic to the path when configuring the path,

wherein the service-specific information comprises service-specific information describing a filter by-pass state for a URL filtering service applied by the service node to the traffic, and

wherein the control unit re-configures the filters that control admission of the traffic to the path based on the service-specific information describing the filter by-pass state for the URL filtering service.

34. The network device of claim 30,

wherein the network device comprises the ingress network device to the path,

wherein the control unit one or more filters that control admission of traffic to the path such that only traffic associated with a set of one or more virtual private networks (VPNs) is admitted to the path when configuring the path,

wherein the service-specific information comprises service-specific information describing a change to the set of the one or more VPNs, and

wherein the control unit re-configures the filters that control admission of the traffic to the path based on the service-specific information describing the change to the set of one or more VPNs.

35. The network device of claim 30,

wherein the network device comprises the ingress network device to the path,

wherein the control unit configures one or more filters that control admission of traffic to the path when configuring the path,

wherein the service-specific information comprises service-specific information describing a firewall context for a firewall service applied by the service node to the traffic, and

wherein the control unit re-configures the filters that control admission of the traffic to the path based on the service-specific information describing the firewall context for the VPN service.

36. The network device of claim 30,

wherein the service-specific information comprises service-specific information describing one or more of execution results of the applied one or more services and service state information between the at least one network device configured to forward the traffic along the path and the service node, wherein the service state information comprises one or more of a current load and performance between the network device and the service node, and

wherein the control unit re-configures the path to forward at least some of the traffic from the ingress network device to a different service node based on the service-specific information describing one or more of a current load and performance between the network device and the service node.

37. The network device of claim 30, wherein the at least one interface receives the service-specific information via a field of a link state routing protocol.

38. A non-transitory computer-readable medium comprising instructions that, when executed, cause one or more processors of a network device to:

configure a path in a forwarding plane of the network device by which to forward traffic from an ingress network device to a service node based on configuration data specified by an orchestrating device that computes and configures paths through the network and that does not forward any traffic through the network other than that used to compute and configure the paths through the network;

forward the traffic along the path with the configured forwarding plane to enable the service node to apply one or more services to the traffic;

receive service-specific information related to the application of the one or more services by the service node to the traffic;

re-configure the path in the forwarding plane of the network device based on the received service-specific information.

39. A network system comprising:

a software-defined network; and

an orchestrating device that computes and configures paths through the software-defined network and that does not forward any traffic through the software-defined network other than that used to compute and configure the paths through the software-defined network,

wherein the software defined-network includes;

a service node; and

an ingress network device,

wherein the ingress network device comprises;

a control unit configured to forward traffic along a path from the ingress network device to the service node in accordance with configuration data specified by the orchestrating device; and

at least one interface that forwards the traffic along the path to enable the service node to apply one or more services to the traffic,

wherein the service node comprises;

at least one interface that receives the traffic via the path; and

a control unit that applies the one or more services to the traffic received via the path and generates service-specific information related to the application of the one or more services to the traffic,

wherein the at least one interface of the service node sends the service-specific information to at least one network device configured to forward the traffic via the path, and

wherein the control unit of the ingress network device unit re-configures the path based on the received service-specific information.