Determining the operations performed along a service path/service chain

• US 10,153,951 B2
• Filed: 09/21/2017
• Issued: 12/11/2018
• Est. Priority Date: 06/07/2013
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Guichard, James, Pignataro, Carlos M., Ward, David, Quinn, Paul, Kumar, Surendra
• Primary Examiner(s): Mew, Kevin D
• Application Number:
  US15/711,625
• Publication Number:
  US 20180013638A1
• Time in Patent Office: 446 Days
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5077 wherein the managed service relates to simple transport services, i.e. providing only network infrastructure
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 43/50 Testing arrangements
• CPC Class Codes: H04L 43/55 Testing of service level quality, e.g. simulating service usage
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Presented herein are techniques performed in a network comprising a plurality of network nodes each configured to apply one or more service functions to traffic that passes the respective network nodes in a service path. At a network node, an indication is received of a failure or degradation of one or more service functions or applications applied to traffic at the network node. Data descriptive of the failure or degradation is generated. A previous service hop network node at which a service function or application was applied to traffic in the service path is determined. The data descriptive of the failure or degradation is communicated to the previous service hop network node.

Claims

1. A method comprising:

in a network comprising a plurality of network nodes each configured to apply one or more service functions to traffic that passes through the respective network nodes in a service path, receiving at a network node an indication of a failure or degradation of a service function or application applied to traffic at the network node;

generating data descriptive of the failure or degradation;

determining a previous service hop network node at which a service function or application was applied to traffic in the service path;

communicating the data descriptive of the failure or degradation to the previous service hop network node;

examining a service header of a received packet in which the received packet is encapsulated to detect a state of a particular bit in the service header allocated to indicate that the received packet is a synthetic packet injected into the service path for verification of packet forwarding through the service path;

determining whether the network node is a last service hop in the service path; and

when the network node is the last service hop in the service path, dropping the synthetic packet and sending to a destination a notification that the synthetic packet reached the last service hop in the service path.

2. The method of claim 1, further comprising injecting the synthetic packet into the service path on an on-demand or periodic basis.

3. The method of claim 1, wherein the destination to which the notification is sent comprises an off-board Operations and Management (OAM) manager.

4. The method of claim 1, wherein the synthetic packet is injected into the service path for verification of the one or more service functions in the service path.

5. The method of claim 4, wherein the verification of the one or more service functions comprises verification of the one or more service functions for one or more tenants of the network.

6. The method of claim 1, wherein generating the data descriptive of the failure or degradation comprises generating metadata for the failure or degradation and including the metadata within the service header.

7. The method of claim 1, wherein determining the previous service hop network node comprises examining a context header in the service header, the context header allocated to contain previous service hop location information and which is populated by each network node along the service path so that the context header contains information identifying the location of the previous service hop network node at any point along the service path.

8. An apparatus comprising:

a network interface unit configured to enable communications over a network, the network comprising a plurality of network nodes each configured to apply one or more service functions to traffic that passes through the respective network nodes in a service path;

a memory; and

a processor coupled to the network interface unit and the memory, wherein the processor is configured to;

receive at a network node an indication of a failure or degradation of a service function or application applied to traffic at the network node;

generate data descriptive of the failure or degradation;

determine a previous service hop network node at which a service function or application was applied to traffic in the service path;

communicate the data descriptive of the failure or degradation to the previous service hop network node;

examine a service header of a received packet in which the received packet is encapsulated to detect a state of a particular bit in the service header allocated to indicate that the received packet is a synthetic packet injected into the service path for verification of packet forwarding through the service path;

determine whether the network node is a last service hop in the service path; and

when the network node is the last service hop in the service path, drop the synthetic packet and send to a destination a notification that the synthetic packet reached the last service hop in the service path.

9. The apparatus of claim 8, wherein the processor is further configured to inject the synthetic packet into the service path on an on-demand or periodic basis.

10. The apparatus of claim 8, wherein the destination to which the notification is sent comprises an off-board Operations and Management (OAM) manager.

11. The apparatus of claim 8, wherein the synthetic packet is injected into the service path for verification of the one or more service functions in the service path.

12. The apparatus of claim 11, wherein the verification of the one or more service functions comprises verification of the one or more service functions for one or more tenants of the network.

13. The apparatus of claim 8, wherein the processor is configured to generate the data descriptive of the failure or degradation by generating metadata for the failure or degradation and including the metadata within the service header.

14. The apparatus of claim 8, wherein the processor is configured to determine the previous service hop network node by examining a context header in the service header, the context header allocated to contain previous service hop location information and which is populated by each network node along the service path so that the context header contains information identifying the location of the previous service hop network node at any point along the service path.

15. One or more non-transitory computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to:

receive at a network node configured to apply one or more service functions to traffic that passes the network node in a service path, an indication of a failure or degradation of a service function or application applied to traffic at the network node;

generate data descriptive of the failure or degradation;

determine a previous service hop network node at which a service function or application was applied to traffic in the service path;

communicate the data descriptive of the failure or degradation to the previous service hop network node;

examine a service header of a received packet in which the received packet is encapsulated to detect a state of a particular bit in the service header allocated to indicate that the received packet is a synthetic packet injected into the service path for verification of packet forwarding through the service path;

determine whether the network node is a last service hop in the service path; and

when the network node is the last service hop in the service path, drop the synthetic packet and send to a destination a notification that the synthetic packet reached the last service hop in the service path.

16. The non-transitory computer readable storage media of claim 15, further comprising instructions operable to inject the synthetic packet into the service path on an on-demand or periodic basis.

17. The non-transitory computer readable storage media of claim 15, wherein the destination to which the notification is sent comprises an off-board Operations and Management (OAM) manager.

18. The non-transitory computer readable storage media of claim 15, wherein the synthetic packet is injected into the service path for verification of the one or more service functions in the service path.

19. The non-transitory computer readable storage media of claim 15, further comprising instructions operable to generate metadata for the failure or degradation and including the metadata within the service header.

20. The non-transitory computer readable storage media of claim 15, further comprising instructions operable to determine the previous service hop network node by examining a context header in the service header, the context header allocated to contain previous service hop location information and which is populated by each network node along the service path so that the context header contains information identifying the location of the previous service hop network node at any point along the service path.