Closed loop automation for intent-based networking

Patent metadata

Field	Value
Publication number	US-11539600-B2
Application number	US-202117516971-A
Country	US
Kind code	B2
Filing date	Nov 2, 2021
Priority date	Oct 4, 2019
Publication date	Dec 27, 2022
Grant date	Dec 27, 2022

Abstract

A method is performed at one or more entities configured to configure and provide assurance for a service enabled on a network. The service is configured as a collection of subservices on network devices of the network. A definition of the service is decomposed into a subservice dependency graph that indicates the subservices and dependencies between the subservices that collectively implement the service. Based on the subservice dependency graph, the subservices are configured to record and report subservice metrics indicative of subservice health states of the subservices. The subservice metrics are obtained from the subservices, and the subservice health states of the subservices are determined based on the subservice metrics. A health state of the service is determined based on the subservice health states. One or more of the subservices are reconfigured based on the health state of the service.

First claim

What is claimed is:

1. A method comprising:
decomposing, by a network service assurance orchestrator device, a definition of a service into a graph that identifies a plurality of subservices and dependencies between the subservices that collectively implement the service, wherein the subservices are each hosted on respective network devices;
obtaining subservice metrics indicative of subservice health states of the subservices;
determining the subservice health states of the subservices based on the subservice metrics;
determining a health state of the service based on the subservice health states;
reconfiguring one or more of the subservices based on the health state of the service and based on reconfiguration information;
if the health state of the service indicates a failing health state, identifying one or more of the subservices that are responsible for the failing health state;
using an identifier of the service and identifiers of the one or more of the subservices from the identifying, retrieving subservice configuration information for the one or more of the subservices from the definition of the service; and
generating the reconfiguration information for the one or more of the subservices from the subservice configuration information.

2. The method of claim 1 , wherein the reconfiguring the one or more of the subservices includes reconfiguring one or more of:
operations performed by the network devices;
communication behavior of interfaces of the network devices;
layer 1 (L1) network connectivity configured on the network devices, layer 2 (L2) network connectivity on the network devices, or layer 3 (L3) network connectivity on the network devices;
packet routing protocols on the network devices; or
logical network functions on the network devices.

3. The method of claim 1 , wherein the reconfiguring the one or more of the subservices includes one or more of:
rebooting the one or more of the subservices on the network devices;
performing traffic shaping on network traffic traversing the network devices to assure a desired level of traffic throughput;
adapting equal-cost multi-path (ECMP) routing on one or more of the network devices; or
repairing one or more of the network devices.

4. The method of claim 1 , wherein the reconfiguring the one or more of the subservices comprises repeating operations used to configure the one or more subservices.

5. The method of claim 1 , wherein the definition further includes a service type and a service instance, and the method further comprises:
generating from the service type and the service instance a service tag that is unique to the service so as to distinguish the service from other services on the network; and
applying the service tag to the subservice metrics to produce service-tagged subservice metrics,
wherein the determining the subservice health states includes determining the subservice health states based on the service-tagged subservice metrics.

6. The method of claim 1 , wherein:
the graph includes subservice nodes to represent the subservices and that are linked to each other in the graph; and
the determining the health state of the service includes populating the subservice nodes with data representing respective ones of the subservice health states; and
the method further includes searching the subservice nodes for ones of the subservice health states that indicate a failing subservice health state.

7. The method of claim 1 , further comprising:
if the health state of the service indicates a passing health state, not performing the reconfiguring.

8. The method of claim 1 , wherein:
each of the subservice health states respectively indicates a passing subservice health state or a failing subservice health state for a corresponding one of the subservices; and
the determining the health state of the service includes:
when one or more of the subservice health states indicate the failing subservice health state, setting the health state of the service to indicate a failing health state; and
when all of the subservice health states indicate a passing subservice health state, setting the health state of the service to indicate a passing health state.

9. The method of claim 8 , further comprising identifying the one or more of the subservices, wherein the identifying includes identifying the one or more of the subservices as the subservices having subservice health states that indicate the failing subservice health state.

10. The method of claim 1 , wherein:
each of the subservice health states respectively indicates a subservice health state within a range of possible subservice health states including a passing subservice health state, a failing subservice health state, and a degraded subservice health state that is neither the passing subservice health state nor the failing subservice health state; and
the determining the health state of the service includes determining the health state of the service to indicate the health state is within a range of possible health states including the passing subservice health state, the failing subservice health state, and a degraded subservice health state that is neither the passing subservice health state nor the failing subservice health state.

11. A system comprising:
one or more network interface units; and
one or more processors coupled to the one or more network interface units and configured to perform:
decomposing, by a network service assurance orchestrator device, a definition of a service into a graph that identifies a plurality of subservices and dependencies between the subservices that collectively implement the service, wherein the subservices are each hosted on respective network devices;
obtaining subservice metrics indicative of subservice health states of the subservices;
determining the subservice health states of the subservices based on the subservice metrics;
determining a health state of the service based on the subservice health states;
reconfiguring one or more of the subservices based on the health state of the service and based on reconfiguration information;
if the health state of the service indicates a failing health state, identifying one or more of the subservices that are responsible for the failing health state;
using an identifier of the service and identifiers of the one or more of the subservices from the identifying, retrieving subservice configuration information for the one or more of the subservices from the definition of the service; and
generating the reconfiguration information for the one or more of the subservices from the subservice configuration information.

12. The system of claim 11 , wherein the one or more processors are configured to perform the reconfiguring the one or more of the subservices by reconfiguring one or more of:
operations performed by the network devices;
communication behavior of interfaces of the network devices;
layer 1 (L1) network connectivity configured on the network devices, layer 2 (L2) network connectivity on the network devices, or layer 3 (L3) network connectivity on the network devices;
packet routing protocols on the network devices; or
logical network functions on the network devices.

13. The system of claim 11 , wherein the one or more processors are configured to perform the reconfiguring the one or more of the subservices by reconfiguring one or more of:
rebooting the one or more of the subservices on the network devices;
performing traffic shaping on network traffic traversing the network devices to assure a desired level of traffic throughput;
adapting equal-cost multi-path (ECMP) routing on one or m

Assignees

• Cisco Tech Inc

Inventors

• Claise Benoit
• Pignataro Carlos M
• Vyncke Eric
• Clarke Joseph M
• Jovanovic Mioljub
• Singh Harjinder

Classifications

• H04L41/5025

  by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade · CPC title

• H04L41/5009 Primary

  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 title

• H04L41/046

  comprising network management agents or mobile agents therefor · CPC title

• H04L41/5032

  Generating service level reports · CPC title