Microsoft Hyper-V

The following entities will be discovered through an IP address, user name and password you provide. The attributes, tags and collections will be updated on Virtana' normal remodeling interval which defaults to every 12 hours.

Host CPUs

Host CPUs

Host HDDs

Cluster Shared Volumes (CSV)

Host Network Adapters

Virtual Machines

Virtual CPUs

Virtual HDDs

Virtual Network Adapters

Resource Pools

Virtual Switches

Note that all the discovered values for the attributes above are shown as of the last modeling time.

The following metrics will be collected every 5 minutes by default. The Average statistic is collected, and the graphed value is per second for anything that resembles a rate.

Hyper-V Server

Host CPU

Host HDD

Host Network Adapter

Resource Pool:

Virtual CPU:

Virtual machine

Virtual network adapter:

Virtual Switches:

You can use the custom command datasource in the HyperV ZenPack to create custom data points, graphs and thresholds.

from Products.ZenRRD.CommandParser import CommandParser
class test1(CommandParser):
    def processResults(self, cmd, result):
        result.events.append({'summary': 'test1 parser event', 'severity': 5, 'test1.detail': cmd.deviceConfig.name})

According to the following Hyper-V states this ZenPack will trigger events with an appropriate summary message.

You can optionally configure each monitored Hyper-V server to attempt to discover and monitor the guest operating systems running within each Hyper-V virtual machine. This requires that your Virtana system has the network and server access it needs to monitor the guest operating system.

When combined with the Virtana Service Dynamics product, this ZenPack adds built-in service impact capability for services running on Microsoft Hyper-V. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities.

Service Impact Relationships

Use the following steps to start monitoring Hyper-V with Basic Authentication using the web interface. Please check the Prerequisites section before adding device to ensure the Hyper-V target server has the correct WinRM setting.

When adding a device, please make sure that you choose a correct Windows version. Otherwise the device modeling and monitoring may result in an error.

Use the following steps to start monitoring Hyper-V with Kerberos Authentication using the web interface. Please check the Prerequisites section before adding device to ensure the Hyper-V target server has the correct WinRM setting.

HyperV and MicrosoftWindows ZenPacks share krb5.conf file as well as tools for sending/receiving data. Therefore if either HyperV or Windows device has a correct zWinKDC setting, it will be used for another device as well.

It is possible to have Hyper-V server in both /Server/Microsoft/HyperV and /Server/Microsoft/Windows. Navigate to the Infrastructure page and use Add a single device... from the add device button. Enter the Device Name, your Hyper-V server's IP address and select /Server/Microsoft/Windows device class. For more specific cases please read Microsoft Windows ZenPack documentation.

Use the following steps to configure Hyper-V device to use WinRM HTTPS using the web interface. Please check the Prerequisites section before adding device to ensure the Hyper-V target server has the correct WinRM setting.

Alternatively you can use zenbatchload to add Hyper-V servers from the command line. To do this, you must create a text file with hostname, username and password of all the servers you want to add. Multiple endpoints can be added under the same /Devices/Server/Microsoft/HyperV section. Here is an example:

'/Devices/Server/Microsoft/HyperV'  loader='hyperv', loader_arg_keys=['device_name', 'host', 'version', 'zWinRMUser', 'zWinRMPassword', 'zWinKDC','collector']
<HOST NAME> host='<HOST NAME or IP>', version='<WINDOWS VERSION>', zWinRMUser='<USER>', zWinRMPassword='<PASSWORD>', zWinKDC='<KDC>',collector='<COLLECTOR>', device_name='<HOST NAME>'

You can then load the Hyper-V servers into Zenoss Core or Virtana Service Dynamics as devices with the following command.

zenbatchload <filename>

Use the following steps to configure virtual machine guest device discovery. Guest device discovery must be configured individually for each Hyper-V server.

This ZenPack can be configured to use either the txwinrm Asynchronous Python WinRM Client or the .NET Core based zendotnet service which requires you to configure the Hyper-V server's hosting machine with the correct WinRM settings. In HyperV 2.0.0 or greater, all devices will use zendotnet by default. To use txwinrm, update zMicrosoftTxRx to txwinrm. Please refer to Microsoft Core documentation for more details. You can enable the WinRM service on the Hyper-V server's hosting machine by running Command Prompt as Administrator and executing the following commands.

This command configures the WinRM service, creates WinRM listener and enables firewall exception for WS-Management traffic. After executing the command below, make sure to type y and hit enter to approve the changes. (This step is required and must be run by an Administrator)

winrm quickconfig

This setting allows for the maximum concurrent operation and shells per user. (If you do not want to use the maximum settings, please see note below for more information)

winrm s winrm/config/winrs '@{MaxShellsPerUser="2147483647"}' 
winrm s winrm/config/service '@{MaxConcurrentOperationsPerUser="4294967295"}'

Set this setting if you plan on using Basic Authentication (WinRM default is Kerberos, please see note below for more information)

winrm s winrm/config/service/auth @{Basic="true"}

Set this setting if you plan on using HTTP with basic authentication. (WinRM default is HTTPS, please see note below for more information)

winrm s winrm/config/service @{AllowUnencrypted="true"}

The above instructions use the max values for MaxConcurrentOperationsPerUser and WinRS MaxShellsPerUser. If you do not want to set these to the max, then a value of 50 should be adequate. The default is 5 on both, which will cause problems because Virtana will open up concurrent requests for each WQL query and set of Perfmon counters.

If you choose to use Basic authentication it is highly recommended that you also configure HTTPS. If you do not use the HTTPS protocol your user name and password will be sent over in clear text. If you have challenges setting up HTTPS on the Windows clients and you don't mind sending the payload in clear text but require the user name and password to be encrypted then using the Kerberos authentication is the best option. HTTPS is not required for Kerberos but is recommended.

If you choose to take the WinRM default configurations you must supply Kerberos authentication settings in the zProperties. The Kerberos authentication process requires a ticket granting server. In the Microsoft Active Directory environment the AD Server is also the KDC. The zWinKDC value must be set to the IP address of the AD Server and the collector must be able to sent TCP/IP packets to this server. Once this is set your zWinRMUser must be a FQDN such as jsmith@Zenoss.com and the zWinRMPassword must be set correctly for this user account.

The HTTPS setup must be completed on each client. At this time we do not have notes on automating this task but are currently in the process of testing several options. To successfully encrypt your payload between the Virtana server and the Windows client you must install a Server Authentication certificate on tbe client machine. The process for requesting and installing the appropriate certificate can be found at the following URL. http://blogs.technet.com/b/meamcs/archive/2012/02/25/how-to-force-winrm-to-listen-interfaces-over-https.aspx Once the client has the correct certificate installed you only need to change the zWinScheme to HTTPS and zWinRMPort to 5986. If you are still having challenges setting up HTTPS on the client you can execute the following command on any AD server to verify the appropriate SPN record exists for Kerberos authentication.

setspn -l hostname1

If you do not see a record with HTTPS/ at the beginning of the hostname you will need to create the record. For example:

setspn -s HTTPS/hostname1.zenoss.com hostname1

If you want your guest devices to be discovered, the Integration Services should be installed on your virtual machines. By default, most Windows virtual machine has Integration Services already installed by default.

Follow the directions below, if your Windows virtual machine does not have Integration Services installed.

Follow the directions below, if your Linux virtual machine does not have Integration Services installed.