Reconfiguring the vCenter Orchestrator principal (public) IP address (1010470)
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.
- Navigate to Start > All Programs > VMware > vCenter Orchestrator Web Configuration.
- Click Network in the left pane.
- Click the IP Address dropdown.
- Select the Principal (Public) IP address of the newly active server.
- Click Apply Changes.
- Restart the vCenter Orchestrator Server service.
vCenter Server Heartbeat 6.3.x and later
- Launch vCenter Server Heartbeat Console.
- Select Data: File Filters.
- Click Add Exclusion Filter.
- Browse to or enter the path $INSTALL_PATH_TO_ORCHESTRATOR/app-server/bin/boot.properties.
- Click OK.
- Perform a switchover so that the Secondary server becomes active.
- 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.
- Click Apply changes.
- If VMware Orchestrator Server is configured as a service:
- Launch the vCenter Orchestrator Web Configuration wizard, select Startup Options, and click Restart service.
- 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.