Auto Remediation for End Users

Musab Muhammad
16 steps
4 minutes

Opera Internet Browser

**Scenario for Auto-Remediation – User Connectivity Loss Due to Error-Disabled Switch Port** Users reported losing network access without any apparent changes or scheduled maintenance. Upon investigation, the affected switch port was found to be in an **err-disabled** state, preventing the end user from reconnecting. Issues like this often require manual device access, multiple CLI checks, and ad-hoc remediation — all of which increase resolution time and operational risk.\ \ In this automated remediation demonstration, our goal is to quickly diagnose the root cause of the err-disabled condition and safely restore end-user connectivity using NetBrain’s runbook-driven automation and Safe Change workflow. **Starting with Runbook-based automations to identify the root cause** We begin by running a NetBrain diagnostic runbook to automatically collect interface state, err-disable reasons, and related configuration data from the affected switch. This allows us to confirm why the port entered an err-disabled state and whether the issue is isolated or part of a broader pattern. **Executing a Pre-built Intent with Auto Remediation enabled** Once the root cause is identified, we run a pre-built intent that includes auto-remediation logic. This intent validates whether the condition meets predefined remediation criteria and confirms that it is safe to proceed with corrective action. **Opening a Change Runbook to apply the fix using NetBrain Safe Change** The remediation workflow launches a Change Runbook that applies the fix in a controlled manner, following NetBrain’s change philosophy. This includes benchmarking the current state, enforcing approval gates, and executing the change consistently across the affected interface. **Verifying recovery and end-user connectivity** After the change is applied, the runbook has built in automation to verify that the interface is operational and that end-user connectivity has been restored. Post-change checks confirm the issue is resolved and that no unintended side effects were introduced. **Generating automated documentation of the remediation event** We complete the workflow by exporting an automated documentation package summarizing the diagnosis, remediation steps taken, verification results, and final device state. This provides a complete audit trail suitable for ticketing, compliance, or operational review. This approach demonstrates how NetBrain can move teams from reactive troubleshooting to safe, repeatable, and automated remediation — reducing MTTR while maintaining full operational control.

We are going to start off by finding the affected device "US-NYC-SW1" in the **Search bar** and **Mapping** it out.

The best way to diagnose and automate our workflow is by using the **Runbook**. In the **Runbook** tab click on the **+** to add a new node.

We are going to start off by using the **Execute CLI Commands** node.

Here we are going to add two commands: "Show interface e1/1" and "Show port-security interface e1/1". Once we have **Added** both commands we will **Run** them live on our affected device.

Go through the output and identify both the err-disabled and Secure shutdown output from the CLI commands.

Next we **Add** the **Network Intent** node to the runbook so we can run diagnosis that will help us to auto remediate.

In the **Network Intent** node **Add Existing Intent** and choose **Standalone Intent.**

The intent we are looking for is the "Err-Disabled Interface Check - Auto Remediate".

**Run** the node and dig into results to reverify the interface that is shutdown.

Once we have the results we are looking for, we can go into intent options and chose to **Open Auto-remediation.** This pops open the auto remediation tab which will populate our change runbook for us.

The first step in any change is to go to the **Planning** tab and get approval. You can do that **externally** with a third party integration or directly with in NetBrain. Once you **Request Approval**, the approver must agree to the change before you are allowed to execute any change.

The change is defined in the **Change to Fix Error-disabled Interfaces** node. Here is where you double check the commands and can even add rollback if applicable.

The **Benchmark Before** tab give you the ability to benchmark your change devices before and then compare them after.

Part of this benchmark shows interface status for err-disabled ports. This is a quick and effective way to check before and after if the problem is resolved once the change has been executed.

The **Execute Change** tab is where you are able to **Execute** the change once approval has been attained. This is also where you are able to push any rollback if defined.

After the change has been executed, you are able to run a post change benchmark and compare. In this change you are also able to **Ping End Host to Verify** that the problem has been resolved.