Some VCMP paths down when upgrading the Hub Edge to 5.2.x after Branch Edge

Products

• VMware VeloCloud SD-WAN

Issue/Introduction

In case of that Hub Edge is a high availability configuration, it is possible to see some VCMP paths down when upgrading the Hub Edge to 5.2.x after upgrading the Branch Edge to 5.2.x.

Environment

This issue occurs under the following condition.

• Hub Edge is a high availability configuration.
• First, Branch Edge is upgraded to 5.2.x version.
• Second, HUB Edge is upgraded to 5.2.x version.
• This issue occurs between the 5.2.x Branch Edge and the 5.2.x Hub Edge. Other Branch Edges are not affected.
• This issue also occurs to upgrade Branch Edge to newer 5.2.x version first. For example, HUB Edges and Branch Edges are version 5.2.2.0, and if you upgrade Branch Edges to 5.2.4.0 first, this issue occurs.

Resolution

The problem is seen because the HUB Edge doesn't delete the old tunnel information when the HUB Edge is upgraded.

Workaround:
The workaround is disconnecting a tunnel on Branch side (tunnel initiator). You can use Restart Service or Force HA failover on Diagnostics -> Remote Action.

Or once you have downgraded the Branch Edge and the HUB Edge to the previous version, and upgraded the HUB Edge first.