Microsoft Hyper-V

If you have a few Microsoft Hyper-V hosts in your environment, you can add them individually as Turbonomic targets. Also, if you have deployed the Hyper-V hosts in a clustered domain (for example as a failover cluster), you can specify one Hyper-V host as a target and Turbonomic automatically adds the other members of that cluster.

For large Hyper-V environments, it’s typical to manage the hosts via System Center Virtual Machine Manager (VMM). You can specify the VMM server as a target and Turbonomic will use it to discover and manage its child Hyper-V hosts. If you use VMM, you should not add individual Hyper-V hosts as targets. For information about adding VMM targets, see Adding Virtual Machine ManagerTargets.

Note:

Even if you manage Hyper-V using a VMM target, you must still configure remote management on each Hyper-V server. This Hyper-V topic includes instructions to configure remote management — see Enabling Windows Remote Management.

For accurate Server Message Block (SMB) storage calculations, Turbonomic requires a VMM target.

Prerequisites

  • Microsoft Hyper-V 2012 R2, 2016, 2019, or 2022

  • Create a service user account in Hyper-V

  • Configure remote management on each Hyper-V server

  • Sync the time on each Hyper-V host with the rest of the managed Hyper-V environment

  • Ensure that your Hyper-V environment does not use Server Message Block (SMB) storage

    To manage SMB storage, Turbonomic requires a VMM target, and that VMM instance must manage the Hyper-V hypervisors and the SMB storage that they use.

    Managing a Hyper-V plus SMB environment via Hyper-V targets will result in incorrect data collection for SMB storage.

Adding Hyper-V targets

Note:

This topic describes features that are available in the new design of the user interface. This new design is enabled by default. If you switched to the legacy design, click New Feature Toggle button in the navigation bar of the user interface and then turn on the toggle to re-enable the new design. For more information, see New Design for the User Interface.

Once you’ve enabled remote management, you can add your Hyper-V hosts as targets.

  1. Click Settings > Target Configuration.

  2. On the Target configuration page, click Add Target.

  3. On the Select target page, click Hyper-V.

  4. In the side panel, review the connection requirements and then click Connect Target.

  5. Configure the following settings:

    • Address

      Specify the fully qualified domain name of the Hyper-V host. If you are using the “Discover Host Cluster” option to add an entire cluster, enter the name of any one of the Hyper-V hosts in the cluster.

      Note:

      You can enter an IP address for the host, but you must first configure an SPN on the host. IBM recommends that you use the FQDN in this field.

    • Username

      Specify the username of the account Turbonomic uses to connect to the target. If you select "Discover Host Cluster”, use an account that is valid for all Hyper-V hosts in that cluster.

    • Fully qualified domain name

      Specify the fully qualified domain name of the cluster to which the host belongs.

    • Password

      Specify the password of the account Turbonomic uses to connect to the target.

    • Port number

      Specify the port number that Turbonomic uses to connect to remote management. By default, this is port 5985 for HTTP and port 5986 for HTTPS.

    • Discover host cluster

      If you select this option, Turbonomic discovers and adds all Hyper-V hosts in the named cluster. Each server must be configured to allow remote management.

      You may find it helpful to configure WinRM using a GPO so new servers are configured automatically (see Enabling WinRM Via a GPO).

    • Connect using HTTPS

      If you select this option, Turbonomic connects to the target servers using HTTPS. Make sure that the required certificate is configured for use on the host.

    • Use Kerberos message-level encryption over HTTP

      If this option is selected, Turbonomic uses Kerberos message-level encryption to discover the environment. This value is ignored if "Secure connection" is enabled.

Note:

If your Hyper-V hosts are running in a Nutanix environment, you must understand pinning a Nutanix Controller VM. For more information, see Pinning Controller VMs in Generic Hypervisor Mode.

Exporting Hyper-V virtual machines

In Hyper-V environments, you must be sure that all VMs have unique IDs.

Hyper-V supports the export of a VM, so that you can create exact copies of it by importing those exported files. The Copy import type creates a new unique ID for the imported VM. When importing VMs in your environment, you should always use the Copy import type.

Turbonomic uses the unique ID to discover and track a VM. If your environment includes multiple VMs with the same ID, then discovery assumes they are the same VM. As a result, the counts for VMs are incorrect.

Monitored resources

Turbonomic monitors the following resources:

  • Virtual Machine

    • Virtual memory (vMem)

      Virtual memory (vMem) is the measurement of memory that is in use.

    • Virtual CPU (vCPU)

      Virtual CPU is the measurement of CPU that is in use.

    • Virtual storage

      Virtual ssorage is the measurement of virtual storage capacity that is in use.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

    • Latency

      Latency is the measurement of storage latency.

  • Host

    • Memory (Mem)

      Memory is the measurement of memory that is reserved or in use.

    • CPU

      CPU is the measurement of CPU that is reserved or in use.

    • IO

      IO is the utilization of a host's IO adapters.

    • Net

      Net is the utilization of data through the host's network adapters.

    • Swap

      Swap is the measurement of a host's swap space that is in use.

  • Storage

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage provisioned

      Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

      Note:

      When it generates actions, Turbonomic does not consider IOPS throttling that it discovers on storage entities. Analysis uses the IOPS that it discovers on Logical Pool or Disk Array entities.

    • Latency

      Latency is the measurement of storage latency.

  • Datacenter

    Note:

    For datacenter entities, Turbonomic does not monitor resources directly from the datacenter, but from the hosts in the datacenter. See host monitored resources for details.

Actions

Turbonomic supports the following actions:

  • Virtual Machine

    • Start

    • Move

    • Suspend

    • Resize Up/Down

    • Terminate

      This action can only be executed outside Turbonomic.

    • Provision

      This action can only be executed outside Turbonomic.

    • Reconfigure

      This action can only be executed outside Turbonomic.

  • Host

    • Start

    • Suspend

    • Terminate

      This action can only be executed outside Turbonomic.

    • Provision

      This action can only be executed outside Turbonomic.

  • Storage

    • Provision

      This action can only be executed outside Turbonomic.