Network Remediation
NI has a Follow-up Remediation function to facilitate auto-remediation directly from the observability dashboard. This provides an alternative to using Intent’s webhook call to initiate remediation with Ansible. The Follow-up Remediation is a subsequent action that can be defined in Network Intent, allowing users to start remediation with a CM task.
Main Use Cases and Use Flow
#1: For Troubleshooting
When users check the network operation status in the network intent and discover an exception, they need identify the root cause and determine the required config change commands and CM template to resolve the issue.
After the NI execution, users will be prompted to determine if the follow-up remediation is needed. If users agree, the corresponding change task is generated based on the device, config change commands, and the CM template calculated in NI. This allows users to execute the change task and quickly resolve the network problem. For example:
- If an IP is detected as rogue IP address, auto-remediate by shutting down the connected switch port.
- If a port is in error-disabled mode, auto-remediate by performing a shutdown followed by a no shutdown.
- If an interface is shown as flapping (up and down), auto-remediate with a shutdown.
- For performance tuning, if an application slowness is detected, then execute a pre-defined QoS config to make sure the communication quality of the critical applications.
The complete use flow for the above scenario is:
#2: For Golden Config Check
When users check the latest golden config check result for a specified device in the network intent (template) and find a golden rule violation, a corresponding config change task is generated. This allows users to immediately execute the corresponding change to solve the network config rule violation.
A single device corresponds to one golden config rule, but there may be multiple config instances. Some of the check results may show violations, while others may be compliant. Only the config instance with an alert in the golden config check result needs to be auto-remediated.
The complete use flow for the above scenario is: