Knowledge Base

In a WAN environment after a switchover or failover, vCenter Orchestrator Server fails to connect as a result of failure to update the Principal (Public) IP address.

vCenter Server Heartbeat 5.5.x

To resolve this issue after a switchover or failure, manually reconfigure the newly active server's vCenter Orchestrator Server principal (public) IP address to the principal (public) IP address of the newly active server.

1. Navigate to Start > All Programs > VMware > vCenter Orchestrator Web Configuration.
2. Click Network in the left pane.
3. Click the IP Address dropdown.
4. Select the Principal (Public) IP address of the newly active server.
5. Click Apply Changes.
6. Restart the vCenter Orchestrator Server service.

vCenter Server Heartbeat 6.3.x and later

1. Launch vCenter Server Heartbeat Console.
2. Select Data: File Filters.
3. Click Add Exclusion Filter.
4. Browse to or enter the path $INSTALL_PATH_TO_ORCHESTRATOR/app-server/bin/boot.properties.
5. Click OK.
6. Perform a switchover so that the Secondary server becomes active.
7. Launch the vCenter Orchestrator Web Configuration wizard and select Network. In the IP address field select the principal (public) IP address of the Secondary server.
8. Click Apply changes.
9. If VMware Orchestrator Server is configured as a service:
1. Launch the vCenter Orchestrator Web Configuration wizard, select Startup Options, and click Restart service.
2. From vCenter Server Heartbeat Console, select Applications: Services. Verify that VMware vCenter Orchestrator Server service is included in the protected services. If not, manually run the Protected Service Discovery task from VMware vCenter Heartbeat Console > Applications > Tasks > VMware VirtualCenter - Protected Service Discovery.