After upgrading NSX, a stale Local Manager (LM) site name (prepended with NSX-) is introduced in the Global Manager (GM). When the stale entry is manually removed from the GM using API commands, cosmetic UI issues occur on the Local Manager:
The Location Manager is no longer present. A Federated Local Manager will add a Location Manager section under the System tab when it is onboarded to a Global Manager
RTEPs do not display in Edge Tunnels. The RTEPs configuration section is added to an Edge Node: System -> Fabric -> Edge -> Tunnels section when Local Manager is onboarded to a Global Manager in a Federated environment
The removed Site ID is still present when running GET https://localhost/policy/api/v1/infra/federation-config on the LM.
Data plane traffic for Virtual Machines (VMs) is not impacted.
VMware NSX 4.x
VMware NSX Federation
The Local Manager becomes out of sync when a stale site entry is removed from the Global Manager during post-upgrade cleanup, requiring a forced offboarding and onboarding of the site to restore the UI components.
If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.