ControlUp supports monitoring and managing virtualization infrastructure based on VMware vSphere, Citrix XenServer, Nutanix AHV, Microsoft Hyper-V, or a combination of those. This means that besides gathering performance data and system information directly from your managed computers, you can also receive updates and perform actions on your managed computers using the underlying hypervisor servers. ControlUp visualizes the utilization of physical resources (such as the impact of VMs on the CPU, RAM, or storage of the host) and allows for performing actions such as turning VMs on and off.
To enable these features, you will need to supply ControlUp with credentials and connection details for your virtualization infrastructure. This operation is performed by creating a hypervisor connection in the Hypervisors folder, which is automatically created in the root of your organization tree. This is the location where all supported hypervisor connections and related objects can be created and monitored. You can manage and monitor any combination of supported hypervisors that you may have in your environment. To do so, you must create a hypervisor connection for each hypervisor instance (VMware vCenter, Nutanix AHV cluster, XenServer pool or standalone server, Hyper-V cluster, or standalone server) in your environment.
Note: There is no need to install XenCenter, vSphere client, or any other hypervisor client software in order to make connections to supported hypervisors in ControlUp.
Creating a hypervisor connection
To create a hypervisor connection, click the Add Hypervisor button on the Home ribbon of My Organization view, or right-click on the Hypervisors folder and choose Add -> Hypervisor.
If you are adding a vCenter server, enter the appropriate vCenter URL (in the format of https://<vCenter name or IP>/sdk) and create a meaningful name that you would like to see in the ControlUp console. Then, use the Credentials drop-down to select or create a set of Active Directory credentials for connecting to the vCenter.
Nutanix AHV Connection
To connect to a Nutanix AHV cluster, enter the cluster's virtual IP address in the format https://<cluster virtual IP>:9440 and provide a connection credential that has at least "Viewer" role permissions.
You can read more about adding a Nutanix connector in this article.
To connect to a XenServer server or pool, choose ‘XenServer’ as the hypervisor type, and then enter the appropriate URL for the server or pool master (in the format of http://<Pool Master name or IP>). The connection name will be automatically created from the name of the pool.
If your XenServer pool uses Active Directory for authentication, use the Credentials drop-down to select a set of Active Directory credentials for connecting to the pool. If the XenServer pool uses built-in Unix accounts (e.g. root), use the credentials drop-down to select or create a “Local Computer” credentials set.
In order to connect your Hyper-V-based virtualization infrastructure to ControlUp, you will need to add your Hyper-V hosts as managed computers to your organization tree. Use the Add Computers button on the Home ribbon to select and add your hosts and then proceed with the steps below. For more details on adding managed computers, please refer to the Add Computers page of the user guide.
Once your Hyper-V hosts are added as managed computers in the organization tree, performance data and system information is collected from those computers as generic Windows machines. In order to enable ControlUp to recognize those computers as virtualization hosts, click the Add Hypervisor button and select Hyper-V in the Type drop-down.
The Add Hypervisor Connection dialog will present you with a list of Hyper-V clusters and standalone hosts found in your ControlUp configuration. Select the cluster or host you would like to monitor and click OK to add the connection.
Configuring Credentials for a Hypervisor Connection
Note: Hyper-V hosts monitored by ControlUp do not require credentials to be explicitly configured. If your virtualization infrastructure is based on Hyper-V, you may skip the next paragraph.
If multiple colleagues are using ControlUp in your environment, please ensure each of them uses the same credentials for the hypervisor connection/s you create. Once a hypervisor connection is configured, ControlUp expects to find an identical set of credentials on all machines on which an instance of the Console or Monitor is used. This behavior is intended to ensure that only authorized users have access to hypervisor-related information and management actions. Therefore, it is recommended that you use a dedicated service account to connect ControlUp to your virtualization infrastructure.
Configuring Data Collection Agents
Note: Hyper-V hypervisor connections in ControlUp do not support dedicated data collectors. If your virtualization infrastructure is based on Hyper-V, you may skip the next paragraph.
The Connection Options dialog is to allow you to change the computer responsible for collecting hypervisor-related data on behalf of ControlUp. By default, any open console or running monitor will retrieve data directly from the connected hypervisors.
You may want to change the computer that collects data for some reason, such as performance issues due to the extra work involved in collecting the hypervisor data, connectivity limitations between the monitor/console and the hypervisor itself, or the desire to implement high availability for the data gathering component. In that case, use the Connections Options dialog to define one or more computers as designated data collector agents. Any active ControlUp agent is eligible to collect data from hypervisors.
Click ‘Add’ to open the list of active agents, and choose however many agents you would like to use. You can then test the connection of the agent to the hypervisor with the ‘Test Connection’ button. The connection is tested with the configuration information at the top of the Connection window. If there is an error, ControlUp will indicate any errors from the test.
Note: when a ControlUp Agent is designated for collecting hypervisor data, it will consume additional CPU and memory resources for connecting to the hypervisor infrastructure and retrieving performance data. Depending on the scale of your virtualization infrastructure, the resource footprint of the cuagent.exe process may grow significantly for those computers, so please keep this in mind when planning your deployment.
When ControlUp connects to a VMware vSphere connection, it will automatically retrieve a list of all datacenters, clusters, and hosts that your connection credentials have access to. For more information on how to restrict access to the vCenter objects, please refer to VMware’s documentation. XenServer connections will automatically retrieve the list of all XenServer hosts in the pool. Hyper-V connections will start monitoring any clustered and standalone hosts that exist in your ControlUp organization tree as managed computers.