VCF Upgrade Precheck Failure: PeerLRBgpNeighbourCheck Due to Stale BGP Neighbors

Products

• VMware NSX

Issue/Introduction

During a VMware Cloud Foundation (VCF) upgrade, the upgrade precheck phase fails consistently with the error PeerLRBgpNeighbourCheck. This error indicates that BGP neighbor connections on the Edge transport nodes are not in an established state for a non-existent destination RTEP (Remote Tunnel End Point).

Environment

VMware Cloud Foundation (VCF) upgrading from version 5.2.x to 9.1

VMware NSX

Cause

The root cause is the persistence of orphaned BgpNeighborInternalConfig entries within the NSX database. These stale records, which frequently refer to decommissioned RTEP IP addresses, were incorrectly retained during previous upgrades (notably from NSX 3.2.x). This creates a control-plane conflict where the system expects a BGP session that is no longer supported by the physical or logical network, thereby failing the PeerLRBgpNeighbourCheck validation logic.

Resolution

To resolve this issue, the stale database entries must be removed using an engineering-provided cleanup utility.

Obtain Cleanup Utility: Contact Broadcom Technical Support to request the librtep-bgp-neighbor-cleanup-lib.jar utility.
Execute Cleanup: Run the utility to identify and surgically remove the stale BgpNeighborInternalConfig entries from the NSX database.
Note: It is recommended to perform an initial run to confirm the count of stale entries before proceeding with the removal.
Perform a thorough audit of the BGP neighbor states via the NSX-T Manager UI or CLI to ensure all remaining sessions are current and established, then proceed with Upgrade: Once the database entries are cleared, the PeerLRBgpNeighbourCheck validation will pass, allowing the VCF upgrade orchestration to proceed.

Additional Information

The issue will be fixed in the later NSX version which used a periodic task that updates inter site neighborstor check if there are duplicate BGP neighbors and delete those.