Closed-Loop Automation

What is Closed-Loop Automation?

Automation helps finish a known task faster, for example, a blender that chops vegetables. Orchestration, on the other hand, ensures that the entire workflow is adopted as per known recipe. Closed Loop Automation is akin to tasting the dish and adjusting the recipe until you reach the perfect flavor and aroma.

By closing the loop, you ensure the system works as intended. This concept is also known as Intent Based Networking (IBN) or Intent-Driven Networking (IDN).

Anuta ATOM combines Assurance, Telemetry, Analytics, and Orchestration to deliver Closed-Loop Automation for multi-vendor network infrastructure.


Closed-Loop Automation Benefits:

  • Avoids human intervention for known troubleshooting steps
  • Improves the consistency and reliability of network infrastructure
  • Enhances the productivity of network operations teams
  • Reduces overall costs of managing the network infrastructure
Closed Loop Automation

Closed-Loop Automation with Anuta ATOM:

You can define the network intent using Anuta DSL. For example, you can define the KPIs and their baseline values along with remediation steps in case of deviations. Anuta ATOM configures the network policy based on the service model. It then collects streaming telemetry data. The ATOM correlation engine compares the metrics against the baseline behavior. So in case of any deviations, Anuta ATOM can automate the remediation steps.

Closed-Loop Automation Example:

Intent: In a stable state, BGP Neighbor flaps should not occur frequently. Frequent flaps indicate a problem with Circuit, Hardware, Software or Configuration.

The ATOM Collector subscribes to streaming telemetry (using model-driven telemetry) from the BGP peering routers. The collector specifies the metrics and frequency of various BGP Neighbor tables. The streaming data is decoded and stored in a time series database (TSDB).

The ATOM Correlation Engine compares the current behavior with baseline behavior. For example, if the Neighbor flaps two times in 60 mins, the system raises it as Trigger-1. However, if the Neighbor flaps 5 times in 10 mins, it can be considered as Trigger-2.

The ATOM Remediation Engine has various corrective actions based on the trigger conditions. For instance, in case of Trigger-1, the system could log the issue or raise the alarm. For Trigger-2, it can take more assertive action such as shutting down the interface, rerouting traffic or creating a severity-1 ticket for human intervention.

Anuta ATOM gives you the flexibility to define each step of this process with an easy to use interface.

For more, check out