Manual Workflow Transformation (Troubleshoot WAN Congestion)

Vivek Sharma
38 steps

Netbrain

Netbraintech

Newtab

Navigate to [https://class.netbraintech.com/desktop.html](https://class.netbraintech.com/desktop.html)

Navigate to Files > Public > Solution Lab Maps > Double-click to open map "Manual Workflow Transformation_WAN Congestion Troubleshooting_Boston Map

This map shows Boston site with CE routers connecting WAN to remote DC at London site.\ \ The issue is that the users are reporting WAN performance issues due to possible congestion.

Navigate to "Runbook" menu.\ We'll troubleshoot using NetBrain Runbook and experience transformation of manual troubleshooting workflow to automation.

Under Published Runbook Templates > Solution Series > select "WAN Congestion Troubleshooting"

Click "Create Runbook"

Run each individual Runbook node. Start with running "Overall Health View"

Observe the results overlaying all critical health parameters of mapped devices and links, right on the map.

Right click and do Data View > Clear All, to clear the current Data view

Switch to the next Ping Node, to check reachability to remote BGP peer IP.

Run "Ping" test

Observe the results showing reachability

Switch to next 'CLI node' to run a CLI command to check device logs on all map devices, with just one click

Click "Run"

"Compare" the current output with any previous version to quickly identify the difference and any possible critical log message.

Switch to tab Lab Tool and trigger event# 19 & 20 for inserting Voice and Video traffic.

Switch back to NetBrain and next, run the Intent node to check BGP Config and State for any issues

Observe the 'BGP Config Check' Golden Intent results to find that the BGP config is consistent with Baseline.

The BGP State Check results show that there are no recent neighbor adjacency issues that could have caused this WAN congestion.

Click "Show Result on Map"

Click "Build Dashboard"

Name it 'WAN Link Status', create new group named 'BGP Status' and save under "Solution Based Series"

Click "Open Dashboard"

You could also set the Dahsboard to Auto refresh

You could "Share Full Dashboard or Read-only Dashboard with Access Code set.

Switch to next Intent Node to check WAN interface for any issues

Here we get our first Red Flag, which shows Output packet drops on the WAN interface

Use "Build Dashboard" to add the results of this Intent also to the same Dashboard you built earlier.

Select the previously created Dashboard, create a New Chart ' WAN Int Status, then click "OK"

You get a unified Observability Dashboard to continuously monitor this WAN Link for any issues.

Now let's dig in deeper to find the root cause using Automation Insight node.

Filter with string 'qos' and Select 'QoS Drops Check_Video', 'QoS Drops Check_Voice' and 'QoS Configuration Check - Cisco IOS 1' Golden Intents to get an insight into suspected QoS packet drops in Voice & Video class as well as checking whether there are any discrepancies in QoS config.

Click "Run" to run all these automations in one go

The first alert shows that Class-map Video has exceeded 6204 packets

Second alert shows that Class-map Voice also has exceeded packets. This confirms the doubt that it is heavy Video and Voice traffic due to a recent Sowtware launch event, which triggered a lot of video and voice traffic, starving the other classes and congesting the overall link. So we just found the root cause in just a few minutes without even logging into any device.

QoS Configuration Check also shows that all the interface QoS config is consistent with the baseline, so no issues here. This could be fixed by a possible WAN bandwidth upgrade, or QoS policy update.

Now that we have found the root cause, we could use the Document node to automatically document the entire troubleshooting flow we followed and create an RCA document.

We could even summarise this document further, like for executive level, with a single click, using NetBrain AI.