Troubleshooting connectivity issues for virtualization monitors
Please follow the below steps when errors are faced related to connectivity for the respective type of Virtualization monitoring.
Citrix / Xen Hypervisor
Verify the host reachability. Try with both Host name and IP address.
Check the port accessibility if it is not blocked by firewall.
Open the Citrix/Xen Center console from the Applications Manager installed machine.
Check whether you can login with the console using the same user that is used for monitoring. If logged in successfully, then try to Add monitor in Applications Manager.
KVM Hypervisor
Verify the host reachability. Try with both Host name and IP address.
Check the SSH / Telnet port accessibility if it is not blocked by firewall.
Using PuTTY (or any CLI client), login to the target KVM host and check whether commands can be executed via SSH / Telnet. Try SSH or Telnet mode, which is tried in Applications Manager.
If any issues faced, please resolve that and try to Add monitor in Applications Manager.
VMware ESXi / vCenter
Verify the host reachability. Try with both Host name and IP address.
Check the port accessibility if it is not blocked by firewall.
Open the VMware ESXi / vCenter console from the Applications Manager installed machine.
Check whether you can login with the ESXi / vCenter console using the same user that is used for monitoring. If logged in successfully, then try to Add monitor in Applications Manager.
VMware Horizon View / Connection Broker
Verify the host reachability. Try with both Host Name and IP address.
Open the Horizon server management console from the Applications Manager installed machine.
Check whether you can login with the console using the same user that is used for monitoring. If logged in successfully, then try to Add monitor in Applications Manager.
Check whether the VMware PowerCLI power shell package is installed in Applications Manager running machine. Check here on how to install the Power CLI package and further configuration required for monitoring.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshoot URL connectivity using PowerShell script (CheckURL.ps1)
Purpose: Some customers may experience intermittent URL connectivity issues in monitors like IIS Server, Azure, AWS, etc., where the monitor Health/Availability fluctuates between up and down during consecutive polls. This often occurs due to minor ...Troubleshooting Basic WMI Connection
Troubleshoot Basic WMI connectivity If you're using Applications Manager version 15470 or above, navigate to Admin > Self Help Tools and select the monitor type to troubleshoot the issue. Click here for more details. If you encounter an error in the ...Troubleshooting Inconsistent .NET Core monitors Availability
Issue: Some applications are experiencing inconsistent availability status, where they appear to be active but are reported as "down." This issue can occur due to the nature of application monitoring and how the monitoring agent interacts with the ...How can I execute SybaseDebug.bat/SybaseDebug.sh?
This file is used to check if the connectivity and the Discovery of the Sybase Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the Sybase Server monitor. The ...