Azure/AWS edges links BW measurement failing due to abnormal results
search cancel

Azure/AWS edges links BW measurement failing due to abnormal results

book

Article ID: 386844

calendar_today

Updated On: 02-12-2025

Products

VMware VeloCloud SD-WAN

Issue/Introduction

In some cases, Azure or AWS edges fails to measure the link BW and the paths are stuck in "WAITING_FOR_LINK_BW" or displaying wrong results.

Environment

Edges on Azure or AWS

Cause

In some cases due to the large BW provided by the cloud providers, the measure bandwidth is too high (1+ Gbps) which is not supported leading to restarting the BW measurement due to abnormal results and this keeps happening.

Resolution

It's recommended to set the BW manually if the BW exceeds 900 Mbps.

Additional Information

More information about Bandwidth Measurement Modes, Best Practices, and Limitations can be found in this KB