• Connecting to your Nutanix AHV hypervisor

    Introduction 

    ControlUp Console supports two hypervisors platforms running on Nutanix (AOS), VMware vSphere and Nutanix Acropolis Hypervisor (AHV). You can now also manage your Nutanix AHV clusters - live, with real-time metrics in the familiar ControlUp way.

    Along with many other new features, Nutanix AHV integration is being introduced starting with ControlUp Console v7.2

    Using the native Nutanix Prism API, all you need to do is provide your credentials in ControlUp in order to connect to your AHV cluster and see the live metrics in the ControlUp console. ControlUp  supports Nutanix AHV clusters running with AOS versions 5.5 & 5.6

    The default port that is configured by Nutanix is 9440 - adjustments will need to be implemented if there's a firewall in place. 

    Nutanix works with security protocol - TLS 1.2 which was released after .NET 3.5, which means that Nutanix data collector must be running .NET 4.5 and above.

    To verify your Nutanix cluster virtual IP address, in Prism, click the Gear Icon > Cluster Details > Cluster virtual IP address. This is the URL that you will need to enter when connecting your ControlUp Console to the Nutanix AHV hypervisor. 

    If the cluster virtual IP address is not configured in Prism - you can view your CVM IP in Prism via Hardware > Table > CVM IP. But keep in mind, if you decide to use one of the hosts CVM IP and it goes down, you won't be able to connect to the rest of the hosts, until that host becomes available. ControlUp best practice is to configure the hypervisor connection with a a Nutanix cluster virtual IP address and not an CVM IP that is configured on one of the hosts so you can view all hosts without depending on the availability of a specific host.

    Permissions

    ControlUp requires for the user\service account to have 'Viewer' only role for view only capabilities (the user that you connect your Console to the hypervisor with). If you want to perform VM power management & host maintenance actions, you'll need to grant the user\service account with the 'Cluster Admin' role.

    In order to use a dedicated user\service account that you already have configured in your environment - you'll need to add your organizational Active Directory to Nutanix by going into Prism, Click the Gear Icon> 'Authentication'. When you're finished with adding your AD - you can 'Test' the connection in ControlUp console and verify that it works. 

    If you don't want to connect your AD to your Nutanix cluster, you can create a local user in the Nutanix local management within Nutanix Prism. Click the Gear Icons > 'Local User Management' and add the user with the proper role required.

    Tip: You can use a user with 'Viewer' role and have your own user to perform special tasks like VM power management or performing hosts maintenance tasks - these actions will always prompt for credentials - so you can save your own credentials locally in your Console and not as 'Shared Credentials' 

    2018-06-12_15-41-55.jpg

     

     

  • Does ControlUp Supports vCenter 6.7?

    The answer is yes!

    In April 2018 VMware introduced to vCenter v6.7 and following that we adjusted and we are now supporting this version in our Console! 

    **This article is referring to Hybrid Cloud Consoles v7.1.1.162 and up.

    In order to integrate vCenter 6.7 with your ControlUp, you'll need to add the following regkey on the Data collector. 

     

    Data collector path:

    Path: HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Agent\ExclusionRules

    1. Value name - TLSSupport
    2. Value type - REG_DWORD
    3. Value data - 1 (decimal)

     

  • Setting permissions for ControlUp in VMware vCenter

    In order to connect your vCenter Server to ControlUp for monitoring purposes, it's highly recommended to create a special dedicated user (Service Account) in Active Directory and assign it with privileges in vCenter Server that will be used only for this purpose.  

    In this article we'll explain how and where to create the user and what permissions will be needed in order to preform tasks in the ControlUp Console. 

    First step is to create a user in your Active Directory. Example for username: CU_VMware

    **If you already have a service account that you want to use with CU it's also possible. You DO NOT have to create a special user just for ControlUp.

    2nd step - login to your vSphere Web Client and go to(>) clusters.jpgHosts and Clusters and select the root folder (vsphere.png) > Manage > Permissions > click on 2018-04-16_12-13-19.jpgand add the user we've created. (CU_VMware)

    **Make sure that the correct domain is selected when searching for CU_VMware.

     ** If you wish to exclude specific vSphere Clusters from ControlUp, you will need to change the permission on the root folder (vsphere.png) to -No Access- role and then on each Cluster that you DO want to see in ControlUp, highlight the Cluster > Manage > Permissions > add the CU_VMware with Read-Only role (or a custom vCenter role that you created) 

    There is two kinds of roles that you can assign the user. It can be either the built-in vCenter "Read-Only" role which will give you the ability to view ALL the virtual machines running on a specific vSphere cluster via ControlUp and the other role is a custom role that you create in vCenter Server and assign it with certain permissions to preform actions (as the image below)

     

    VM.jpg

     

    ** If you would like to know how to create a new custom vCenter role - click here

    vCenter Server privileges required to utilize the ControlUp Console actions under “VM Power Management” are located in Virtual Machine > Interaction > Power Off \ Power On \ Reset (attached image for example.)

    power.jpg

    3rd step - go to vms.jpgVMs and Templates > Manage > Permissions and add CU_VMware with No Access permissions. 

    At this point only Clusters that you've allowed the user to view should be in the ControlUp Console. 

    Note - if you're still not seeing VM's in your grid - confirm that "Show Agentless Managed VMs" is checked. 

    vms.jpg

  • Which Hypervisors are supported in ControlUp?
    • VMware ESXi 5.x. vCenter is required to enable VMware integration in ControlUp. Standalone ESXi are currently not supported.
      • We support all version past 5.x, VMware vSphere 6.x (including latest version 6.5 U1) is fully supported.
    • Citrix XenServer 6.5, including standalone XenServer hosts, and Citrix XenServer 7.x is fully supported.
    • Microsoft Hyper-V 2012 R2, Microsoft Hyper-V 2016 including standalone and clustered hosts. Please note that ControlUp Agent needs to be installed on the Hyper-V hosts to enable monitoring them as hypervisors (The console does not work on any version of Core, but the agent is fine as long as you have .Net 3.5.1 or .Net 4.6.2.).

    For more details regarding the configuration of ControlUp for monitoring your virtualization infrastructure, please refer to the Connect to Your Virtualization Infrastructure section of this guide.

     

  • Can I monitor multiple hypervisors from the same ControlUp console?

    Yes.

    ControlUp supports both VMware ESXi and Citrix XenServer hosts and they can be monitored and displayed in the same real-time view.

  • Do I need to install an agent on my VMware ESXi or Citrix XenServer hosts?

    No.

    ControlUp communicates with vCenter/XenServer via API calls to agentlessly collect real-time performance and configuration data on Hosts, VM’s and Datastores.

  • Do I need to install an agent on every VM?

    No.

    Our Hypervisor Integration feature provides a rich set of performance and configuration metrics on VM’s such as CPU, Memory, IO and Network. We recommend deploying the ControlUp agent to your Windows based VMs, which enables real-time performance monitoring of processes and sessions and allows for executing troubleshooting and remediation tasks.

  • What type of credentials are needed for the Hypervisor Connection?

    Read-only credentials are sufficient for displaying Hypervisor real-time performance data.

    If you plan to use the VM power management feature (i.e. force reset or shutdown) you would need to configure credentials with the appropriate power management rights on all relevant VM’s.

    Read more