The Standby Global Manager (GM) Sync status remains in a "In Progress" state in the NSX manager GUI as shown in the screenshot below:
The vmware/appl-proxy-rpc.log on the NSX manager reveals the following connection errors indicating an inability to route traffic to peer nodes on required synchronization ports:
YYYY-02-02T09:44:51.897Z DR-VX-NSXTG02.1link.pk NSX 2161 - [nsx@6876 comp="global-manager" subcomp="appl-proxy" s2comp="nsx-net" tid="2319" level="INFO"] StreamSocket[5030 Open f:61 i:-1258173070 ? -> ssl://X.X.X.X:1234] on_connect 113-No route to hostYYYY-02-02T09:44:51.897Z DR-VX-NSXTG02.1link.pk NSX 2161 - [nsx@6876 comp="global-manager" subcomp="appl-proxy" s2comp="nsx-net" tid="2319" level="WARNING"] StreamConnection[5030 Connecting to ssl://X.X.X.X:1234 sid:5030] Couldn't connect to 'ssl://X.X.X.X:1234' (error: 113-No route to host)YYYY-02-02T09:44:51.897Z DR-VX-NSXTG02.1link.pk NSX 2161 - [nsx@6876 comp="global-manager" subcomp="appl-proxy" s2comp="nsx-net" tid="2319" level="WARNING"] StreamConnection[5030 Error to ssl://X.X.X.X.:1234 sid:-1] Error 113-No route to host
VMware NSX
Network communication is failing between the Active Global Manager and the Standby Global Manager nodes.
Specifically, network port connections (such as 443, 1234, and 1235) are failing to establish for one or more target GM nodes, disrupting the synchronization sequence.
To resolve the issue:
Identify the specific IP addresses of the Standby GM nodes reporting the failure.
From the Active Global Manager, utilize the nc -zv command to test connectivity to the Standby GM nodes over required ports. Example: nc -zv <ip addresss> 1234
If the connection fails, engage the network administration team to ensure all required ports are open and forwarded between the NSX Managers in the environment.
Refer to the official VMware Ports and Protocols document to verify all required ports for NSX Manager and Global Manager communication: https://ports.broadcom.com/home/NSX