Unable to proceed with NSXT upgrade due to BGP down alarms observed during NSX upgrade pre-check

Products

• VMware NSX
• VMware Telco Cloud Platform

Issue/Introduction

During NSX upgrade pre-check BGP down alarms were seen for most of the BGP neighbors as shown below, this prevents NSX upgrade from 4.2.1.2 to 4.2.1.4 

 

Environment

NSX 4.2.1.2 

TCP 3.0 

 

Cause

The BGP neighbors are configured between tier0 GW and Avi Service Engines which were down temporarily. So these BGP down alarms which are of high severity prevents NSX upgrades.

Resolution

In case of NSX upgrade pre-check failures due to BGP down alarms, one of the below workaround could be attempted 

1. Take a backup of all the BGP configs (note down the BGP peers) and remove it from the configuration. In this way even if any stale entries persists will also be removed and then proceed with upgrade pre-check 
2. The BGP down alarms could be suppressed for a user defined span or acknowledged indefinitely and the upgrade pre-check could be executed and proceed with upgrade. These alarms might appear again once if the underlying condition changes or suppress timeout exceeds.

Check upgrade pre-check status after performing one of the above actions and proceed with NSX upgrades if upgrade pre-check is successful

Additional Information

For successful NSX upgrade prechecks refer below documents

Run the NSX Upgrade Pre-check Bundle

NSX Pre-upgrade tasks