BlueCat Wednesday | Enterprise LiveAction Series Issue #11 Is Your SD-WAN Really Working as Expected?

The Policy May Be Correct. But What About the Actual Traffic?

The promise of SD-WAN is compelling: identify the application, select the best connection, route traffic along the right path, and switch to an alternative link when performance degrades.

But a correctly defined policy does not mean application traffic will always take the path you expect.

What matters is not seeing the configuration, but seeing the configuration's actual effect on traffic.

MPLS, Internet, LTE… Which One Is It Using?

Modern SD-WAN architectures can use multiple connections simultaneously, including MPLS, broadband internet, DIA, and LTE/5G. Policies select paths according to the application and link quality.

You may expect ERP traffic to use MPLS, Microsoft 365 traffic to go directly to the internet, and traffic to move to an alternative link when the primary circuit degrades. The critical operational question is: Is that what is actually happening?

Link Up Does Not Mean Good Performance

A link may remain active while latency increases, packet loss occurs, jitter rises, or application response time deteriorates.

LiveAction helps assess not only whether a link is up or down, but also the actual performance of different paths. This shifts the question from “Is the connection working?” to “Is this really the right connection for this application?”

Prove Path Selection

Teams need to see which WAN connection an application uses, when the path changes, and how that change affects performance.

• Did latency or packet loss increase on MPLS?

• Did the path change because a policy threshold was exceeded?

• Did SD-WAN fail over as expected?

• Was traffic sent down another path because of an incorrect policy?

A successful failover and an incorrect routing decision may look similar to the user. Only actual traffic and performance data can reveal the difference.

See the Cause and Outcome of Failover

Knowing that failover occurred is not enough. Teams must also understand which metric degraded beforehand, which connection received the traffic, and whether application performance improved after the transition.

When LiveAction brings network performance and traffic behavior into the same operational context, teams can verify both the cause and the outcome of failover.

Multiple Locations, One Reality

Manual investigation may be possible across ten branches; connecting to devices one by one is not sustainable across hundreds of locations.

Centralized visibility enables a holistic assessment of affected sites, degraded WAN links, application paths, and path changes. SD-WAN becomes an architecture that is not only centrally managed, but centrally verified.

Executive Note

The purpose of an SD-WAN investment is to protect performance and business continuity by carrying application traffic over the most appropriate path under all conditions.

By making path selection, link performance, and traffic behavior visible, LiveAction helps teams identify gaps between the designed architecture and actual network behavior more quickly.

Policy Shows Intent. Visibility Proves What Actually Happened.

BlueCat Wednesday | Enterprise LiveAction Series

Prepared by Zero Second

Helping organizations build resilient, observable and high-performing network infrastructures.