Not receiving updates within Foglight. Current status not shown for a specific vCenter
Alarm:
Host Port: 443, Host URL: sdk, Host Name: <FglAMHost> One or more attempts to connect to the VirtualCenter have timed out or failed. Please review the Host Name and Host Port in the agent configuration. If these are correct there may be issues in your network preventing the connection to the Virtual Center.
Foglight log file:
,
YYYY-MM-DD HH:MM:SS.DDD ECHO <VMwarePerformance/5.6.2/VMwarePerformance/<FglAMHost>-agent> FATAL [Quartz-20394] com.quest.agent.esx.task.RelationsTask - One or more attempts to connect to the VirtualCenter have timed out or failed. Please review the Host Name and Host Port in the agent configuration. If these are correct there may be issues in your network preventing the connection to the Virtual Center.
YYYY-MM-DD HH:MM:SS.DDD ECHO <VMwarePerformance/5.6.2/VMwarePerformance/<FglAMHost>-agent> ERROR [Quartz-20394] com.quest.agent.esx.task.RelationsTask - Error during execution: ERROR: VI SDK invoke exception:java.net.ConnectException: Connection timed out: connect
java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection timed out: connect
at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:181)
at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:123)
at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1449)
at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:85)
at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:69)
at com.quest.vmware.api.connection.VIService.connect(Unknown Source)
at com.quest.vmware.api.connection.VIService.login(Unknown Source)
at com.quest.agent.esx.task.ESXAgentTask.connect(Unknown Source)
at com.quest.agent.esx.task.ESXAgentTask.run(Unknown Source)
at com
There is a connectivity issue.
1: Verify that there is connectivity between the Agent Manager system (FglAM) and the vCenter. Use ping (or other appropriate tools) as a method to verify that name resolves and can connect.
2: If IP of vCenter has changed recently, clear the DNS cache of the operating system.
Windows: ipconfig /flushdns
Linux: /etc/rc.d/init.d/nscd restart
(Linux command may be different depending on distro, consult your documentation)
3: Stop, wait for it to end, and restart the Agent Manager (FglAM). If using the embedded Agent Manager, you will need to stop the FMS, wait for it to stop, and restart it. Do not use the 'restart' service or daemon as that may not allow for enough time for the service/daemon to stop completely.
If the above do not resolve the issue, there may be a different problem.
