System and method for managing chained services in a network environment

• US 10,361,969 B2
• Filed: 08/30/2016
• Issued: 07/23/2019
• Est. Priority Date: 08/30/2016
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Bosch, Hendrikus G. P., Napper, Jeffrey, Kumar, Surendra M., Duminuco, Alessandro, Mullender, Sape Jurrien, La Roche, Humberto J., Samuel, Louis Gwyn, Brockners, Frank, Bhandari, Shwetha Subray
• Primary Examiner(s): Duong, Christine T
• Application Number:
  US15/252,028
• Publication Number:
  US 20180063018A1
• Time in Patent Office: 1,057 Days
• Field of Search: None
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 47/28 in relation to timing considerations
• CPC Class Codes: H04L 47/76 using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data

Abstract

An example method is provided in one example embodiment and may include configuring a measurement indication for a packet; forwarding the packet through a service chain comprising one or more service functions; recording measurement information for the packet as it is forwarded through the service chain; and managing capacity for the service chain based, at least in part, on the measurement information. In some cases, the method can include determining end-to-end measurement information for the service chain using the recorded measurement information. In some cases, managing capacity for the service chain can further include identifying a particular service function as a bottleneck service function for the service chain; and increasing capacity for the bottleneck service. In various instances, increasing capacity for the bottleneck service can include at least one of: instantiating additional instances of the bottleneck service; and instantiating additional instances of the service chain.

Claims

1. A method comprising:

setting, at a classifier node, a measurement indication within a header of a packet, wherein the measurement indication indicates to one or more service functions that the packet is a measurement and data packet;

forwarding the packet through a service chain comprising the one or more service functions;

upon determining that the measure indication within the header of the packet is set, recording measurement information for the packet as it is forwarded through the service chain;

after the packet is forwarded through the service chain, determining by evaluating the packet, that the packet failed to traverse a first service function of the service chain;

collecting the measurement information for the first service function; and

managing capacity for the service chain based, at least in part, on the measurement information.

2. The method of claim 1, further comprising:

determining end-to-end measurement information for the service chain using the recorded measurement information.

3. The method of claim 1, wherein managing capacity for the service chain further comprises:

identifying a particular service function as a bottleneck service function for the service chain; and

increasing capacity for the bottleneck service function.

4. The method of claim 3, wherein increasing capacity for the bottleneck service function includes at least one of:

instantiating additional instances of the bottleneck service function; and

instantiating additional instances of the service chain.

5. The method of claim 1, wherein managing capacity for the service chain further comprises:

identifying that a particular service function or the service chain is underutilized; and

decreasing capacity for the particular service function or the service chain.

6. The method of claim 5, wherein decreasing capacity for the particular service function or service chain includes:

cancelling the particular service function or service chain.

7. The method of claim 1, wherein configuring the measurement indication for the packet includes setting an Operations and Administration (OAM) bit within a Network Service Header that is encapsulated with the packet.

8. The method of claim 1, wherein the measurement information includes one or more of:

a time stamp associated with a time when the packet is received at an ingress interface associated with the service chain;

a time stamp associated with a time when the packet is received by a forwarding node associated with a particular service function of the service chain;

a time stamp associated with a time when the packet is placed in an output queue of a forwarding node to be sent to a particular service function of the service chain associated with the forwarding node;

a time stamp associated with a time when the packet is received from a particular service function by a forwarding node associated with the particular service function of the service chain; and

a time stamp associated with a time when the packet is added to an output queue for an egress interface associated with the service chain.

9. One or more non-transitory tangible media encoding logic that includes instructions for execution that when executed by a processor, is operable to perform operations comprising:

setting, at a classifier node, a measurement indication within a header of a packet, wherein the measurement indication indicates to one or more service functions that the packet is a measurement and data packet;

forwarding the packet through a service chain comprising the one or more service functions;

upon determining that the measure indication within the header of the packet is set, recording measurement information for the packet as it is forwarded through the service chain;

after the packet is forwarded through the service chain, determining by evaluating the packet, that the packet failed to traverse a first service function of the service chain;

collecting the measurement information for the first service function; and

managing capacity for the service chain based, at least in part, on the measurement information.

10. The media of claim 9, the operations further comprising:

determining end-to-end measurement information for the service chain using the recorded measurement information.

11. The media of claim 9, wherein managing capacity for the service chain further comprises:

identifying a particular service function as a bottleneck service function for the service chain; and

increasing capacity for the bottleneck service function.

12. The media of claim 11, wherein increasing capacity for the bottleneck service function includes at least one of:

instantiating additional instances of the bottleneck service function; and

instantiating additional instances of the service chain.

13. The media of claim 9, wherein managing capacity for the service chain further comprises:

identifying that a particular service function or the service chain is underutilized; and

decreasing capacity for the particular service function or the service chain.

14. The media of claim 9, wherein configuring the measurement indication for the packet includes setting an Operations and Administration (OAM) bit within a Network Service Header that is encapsulated with the packet.

15. A system comprising:

a compute node comprising at least one first memory element for storing first data and at least one first processor that executes instructions associated with the first data, wherein the compute node, when the at least one first processor executes the instructions, being configured to;

set, at a classifier node, a measurement indication within a header of a packet, wherein the measurement indication indicates to one or more service functions that the packet is a measurement and data packet;

forward the packet through a service chain comprising the one or more service functions; and

upon determining that the measure indication within the header of the packet is set, record measurement information for the packet as it is forwarded through the service chain;

after the packet is forwarded through the service chain, determining by evaluating the packet, that the packet failed to traverse a first service function of the service chain;

collecting the measurement information for the first service function; and

a service assurance system comprising at least one second memory element for storing second data and at least one second processor that executes instructions associated with the second data, wherein the service assurance system, when the at least one second processor executes the instructions, being configured to;

manage capacity for the service chain based, at least in part, on the measurement information.

16. The system of claim 15, wherein the service assurance system, when the at least one second processor executes the instructions, being configured to:

determine end-to-end measurement information for the service chain using the recorded measurement information.

17. The system of claim 15, wherein managing capacity for the service chain further comprises:

identifying a particular service function as a bottleneck service function for the service chain; and

increasing capacity for the bottleneck service function.

18. The system of claim 17, wherein increasing capacity for the bottleneck service function includes at least one of:

instantiating additional instances of the bottleneck service function; and

instantiating additional instances of the service chain.

19. The system of claim 17, wherein the measurement information includes one or more of:

a time stamp associated with a time when the packet is received at an ingress interface associated with the service chain;

a time stamp associated with a time when the packet is received by a forwarding node associated with a particular service function of the service chain;

a time stamp associated with a time when the packet is placed in an output queue of a forwarding node to be sent to a particular service function of the service chain associated with the forwarding node;

a time stamp associated with a time when the packet is received from a particular service function by a forwarding node associated with the particular service function of the service chain; and

a time stamp associated with a time when the packet is added to an output queue for an egress interface associated with the service chain.