Skip to main content

Configure the Microsoft Hyper-V integration

Use this procedure to configure the Microsoft Hyper-V integration in IO (Infrastructure Observability). Before you begin, ensure you have completed all tasks in Prepare the Windows environment for monitoring.

  1. On the Settings screen, click Integrations in the Probes and Integrations section.

    The Integrations screen opens.

  2. Click View for the Microsoft Hyper-V software integration.

    The Microsoft Hyper-V screen opens.

    For a description of the columns on this screen, see Microsoft Hyper-V inventory columns below.

    At the end of each row, click the down arrow to access shortcuts to Configure, Test Connection, Start Discovery, or Delete the integration in that row.

  3. Click New.

    The Discover New Integration screen opens.

  4. In the Name field, enter a name for the integration.

    The Name field is user-configurable. The Type, Frequency, and Time of Day fields are carried forward from the Integration Inventory page.

  5. Configure scheduled discovery:

    • To keep regularly scheduled discovery enabled (recommended), confirm that the Enable scheduled discovery checkbox is selected, then select a discovery frequency and time of day. The default is every day at 2:00 AM appliance time.

    • To disable regularly scheduled discovery, clear the Enable scheduled discovery checkbox.

  6. Add Hyper-V hosts using one of the following methods:

    • Add one host at a time: Click Add and continue with the next step.

    • Import multiple hosts from a CSV file: Click Import and skip to the Import multiple Hyper-V hosts step below.

  7. In the Add Host dialog, complete the following fields and click OK:

    Field

    Description

    Name

    User-defined name for the integration, typically the hostname. For example, HYPERV-SC01.

    Hostname

    IP address or fully qualified, DNS-resolvable hostname of the Hyper-V host. For example, hyperv-sc01.lab.company.local.

    Domain

    Domain of the user account used to poll data from the host.

    Username

    User account used to poll data from the host.

    Password

    Password for the user account.

    Metrics Polling Interval

    Frequency of metrics collection. The default is every 5 minutes.

    The host appears in the Hosts list on the Discover New Integration screen. Skip the next step and continue with Configure and subscribe hosts.

  8. Import multiple Hyper-V hosts

    Before clicking Import, prepare a CSV configuration file. The file must contain one line per host with no header row. Each line must use the following format:

    Name, Hostname/IP Address, AD Domain, Username, Password, Polling Interval

    Example:

    hyperv-host-01,10.10.56.12,hyperv.dev,vi-services,samplepassword,5min
    hyperv-host-02,10.10.56.13,hyperv.dev,vi-services,samplepassword,10min

    The following table describes each field in the CSV file:

    Field

    Description

    Name

    Display name for the host.

    Hostname/IP Address

    IP address or fully qualified, DNS-resolvable hostname of the Hyper-V host. For example, hyperv-sc01.lab.company.local.

    AD Domain

    Active Directory (AD) domain of the user account used to poll data from the host.

    Username

    User account used to poll data from the host.

    Password

    Password for the user account.

    Polling Interval

    Frequency at which the host is polled. Accepted values: 1min, 5min, 10min, 15min, 1hour.

    When your CSV file is ready, click Import.

  9. In the Import dialog, select one of the following import modes:

    • Replace: Removes all existing records and adds all records from the CSV file.

    • Merge: Updates existing records with values from the CSV file. Blank fields in the CSV file are ignored. New records from the file are added.

    • Add: Leaves existing records unchanged and adds only new records from the CSV file.

    Click Save to apply the import.

  10. Configure and subscribe hosts

    To update settings for multiple hosts at once, select the hosts from the Hosts list and click Configure.

    1. Select the fields you want to change and click Next.

    2. Enter the updated values in the Bulk Configuration dialog.

    3. Click OK to apply the changes.

  11. Optionally, click Test Connection to verify the hostname and credentials for all Hyper-V hosts.

    This process can take up to five minutes. A message appears indicating whether the configuration is correct or if there are errors to correct.

  12. In the Hosts list, select the hosts you want to subscribe to and click Subscribe.

    When you click Subscribe, IO also validates that sufficient licenses are available.

  13. Click Save to save your changes.

    The Discover dialog opens, asking whether you want discovery to start immediately. Virtana recommends starting discovery immediately, as no metrics are collected until discovery is complete.

  14. Click Yes to start discovery immediately.

    You return to the main integrations grid. The integration you added shows Discovering... in the Last Discovery column.

    While discovery is in progress, the integration is in read-only mode. You cannot make changes to the integration or host configuration until discovery is complete.

Microsoft Hyper-V inventory columns

The following table describes the columns on the Microsoft Hyper-V inventory screen.

Table 93. Microsoft Hyper-V inventory columns

Column

Description

Name

User-defined name for the integration, typically the integration IP address or type of integration. For example, Brocade_BNA_27 or seed_switch_1.

Subscription

Subscription status: Unsubscribed or Subscribed.

For Cisco SAN and Brocade SAN integrations, if subscribed, shows a ratio of subscribed switches to total configured switches. For example, 1/5 means one of five configured switches is subscribed.

Last Discovery

Date and time of the last discovery run. Other possible values are: Discovering (discovery in progress), No discovery, Discovery failed, or Warned.

For Discovery failed or Warned status, hover over the cell to see the error or warning as a tooltip.

Last Metrics Collection

Date and time of the last metrics collection. Other possible values are:

  • Collecting metrics: Metrics collection is in progress.

  • Metrics collection failed: Followed by a ratio of failed subscribed switches to total subscribed switches. To see failures, drill down into the switch grid.

  • No collection: No metrics collection has occurred.

  • Warned: Followed by a timestamp. To see warnings, drill down into the switch grid.

If an integration fails to collect metrics for two hours, you receive a Health Notification alert and an email notification.