Troubleshooting network disconnection in OpManager server
OpManager does a periodic self-ping to ensure that the OpManager-installed server is connected to the rest of the network. If this ping does not get a positive response, it is considered as a 'network disconnection' and data collection is temporarily suspended.
When that happens, an alert is raised as follows:
OpManager has detected that it has lost network connectivity and has suspended all monitoring. Monitoring will be automatically resumed once connectivity is established.
The data collection will be re-initiated once the self-ping is successful.
The possible causes for the network disconnection alert are as follows:
- The OpManager-installed server has been disconnected from the network
- IP Address/Hostname changes or any network-related changes have occurred for the OpManager server.
- Entries in the etc\hosts have been modified recently or some misconfiguration has occurred in the etc\hosts file.
How can I troubleshoot this network disconnection error?
- Get the network address we detected during startup.
- Ping local host server and obtain latest IP Address/hostname:
From the OpManager-installed server, run the "hostname" command on Command Prompt. Note down the hostname and try pinging it to make sure that it's resolving properly with the IP address.
- If it responds with the local loopback address (127.0.0.1), then you have to check the etc\hosts file. With proper consultation with your network administrator, check and update the etc\hosts file and check the behaviour again.
- If the response isn't as mentioned above, note down the IP address/hostname mentioned. Let's call this as Source 2.
- If Source 1 and 2 are the same, then it means that the network connection is fine now and data collection will be started automatically. You can safely close the pop up message.
- But if both are different, then some network change has occurred recently. If that is the case, we recommend you to restart OpManager service once to re-establish the network connection properly.
- Even after restarting if you keep getting the same alert, and Source 1 isn't the IP address/hostname of the OpManager-installed server:
- If there are issues even after trying all these, try restarting the OpManager service for one last time. If it's still not resolved, obtain the Support Information File (SIF) along with screenshots of the alerts and contact our support team to assist you with this issue.