Velocloud Azure Edge using accelerated networking, Tunnels do not come up to the VCG after upgrading from 5.4.0.0 to 5.4.0.1

Products

• VMWare SD-WAN
• VMware SD-WAN by VeloCloud

Issue/Introduction

When upgrading the Velocloud edge from 5.4.0.0 to 5.4.0.1, we notice that the tunnels towards the gateway do not come up, this article discusses the cause and how to resolve the issue.

Environment

In an Azure environment, when upgrading the edge to 5.4.0.1, we notice that the edge gateway services down message post upgrade.

Upon checking the events, we can see the below event which indicate that the edged services does not start causing the tunnels towards the Velocloud gateway to not establish.

Cause

Issue is caused by a bug under reference 143551 in the 5.4.0 release notes:

 

Issue 143551: A Virtual Edge deployed on Azure which uses Accelerated Networking may experience multiple Dataplane Service failures and be unable to pass traffic when it is upgraded to Release 5.4.0.1, and this state cannot be recovered.

Edge Release 5.4.0.1 does not properly implement support for Azure Accelerated Networking, and when an Azure Virtual Edge using Accelerated Networking is upgraded to this release, an exception is triggered and the Edge service fails, and then restarts three times in succession. After the third service failure, the Edge service stops entirely. A reboot does not recover the Edge as the issue will persist and restart the cycle of service failures/restarts all over again.

A customer with an Azure Virtual Edge that does not use Accelerated Networking is not at risk for this issue.

Note: This issue affects VMware SDWAN in Azure vWAN hub and Azure virtual edge instance. 

Resolution

Fix is to upgrade to 5.4.0.2 or upgrade to 5.4.0.1 hotfix image with fix for 143551.