SolutionPack for Microsoft Hyper-V
Table of Contents
This article applies to EMC ViPR SRM version 3.5.1.Back to Top
Compatible ViPR SRM version
EMC ViPR SRM version: 3.5.1
- Displays the inventory of devices, parts and metrics from Hypervisors and Virtual Machines
- Virtual Disk Use Analysis
- Tool to analyze the utilization profile of Virtual Hard Disk images
- All Hosts | All Virtual Machines
- Displays all available performance graphs for Hypervisors and Virtual Machines
- Global Status
- Shows the global status of all hosts and running virtual machines in the environment, detailed by component type
- SLA Detailled View
- Shows the current and forecasted SLA values for Hypervisors and Virtual Machines
- Virtual Machines Running On Snapshot Disks
- Shows all virtual machines running on snapshot disks. They impact disk performance and impact storage performance when it is time to commit changes on the original virtual disk.
This SolutionPack can only be installed on a Windows collector host.
- Hyper-V Collector Manager must have the right to query WMI objects from Hyper-V hosts
- PowerShell must allow the execution of unassigned PowerShell scripts
In order to collect data from Microsoft Hyper-V hosts, the environment needs to meet the following requirements:
- The Collect SolutionPack Block must be installed in a server using Windows Server 2008 R2 Service Pack 1 or later.
- The Collect SolutionPack Block must be able to query WMI objects in remote Microsoft Hyper-V hosts. For required privileges, refer to the manual EMC ViPR SRM SolutionPack Privileges.
- The Collect SolutionPack Block machine must allow the execution of unsigned PowerShell scripts. To provide this capability, run the following command as an administrative user: PowerShell -C Set-ExecutionPolicy Unrestricted.
Before you begin
- EMC ViPR SRM core modules must be up-to-date in all servers because not all module dependencies are validated during the SolutionPack installation or update process.
- Log in.
- Click Administration.
- Click Centralized Management.
- Click SolutionPacks.
- Select SolutionPack Center.
- Select the SolutionPack for Microsoft Hyper-V in the Browse and Install SolutionPacks screen.
The steps below assume a typical four VM deployment.
- In the Data Collection field of the Select the components to install window, select the Collector host.
- In the Reports field, select the Frontend host.
- Click Next.
- In the
Data collection window, select a value for
If you select Add a new data collection, type information about the data collection.
- Failover-Filter must be enabled, which is the default.
- In the Hostname or IP address to send data field, type the Primary Backend host.
- Leave Enable alerting on data collected checked.
- Select a value for
Alerting on data collection.
If you select Add a new Alerting on data collection, type information about the alerting configuration.
- In Alerting Backend the hostname or IP address, select the Primary Backend host.
- Type the host information and access credentials to communicate with the Hyper-V.
- Click the plus (+) sign to add more Hyper-V hosts.
- Click Next.
- In the Reports window, in the Administration Web-Service Instance field, select the Frontend host.
The SolutionPack installation begins.
Ok once installation is complete.
Performance data will displayed in about an hour.
The Test feature located in the Discovery Center under the Centralized Management UI is not supported for the SolutionPack for Microsoft Hyper-V. Instead, use the test method presented in this topic.
The SolutionPack for Microsoft Hyper-V provides a script that can be used to check if is possible to query all required WMI objects using the provided user. The script is in the folder <APG_FOLDER>/Collecting/XML-Collector/<SolutionPack_instance_name>/conf/. You must execute the script from the Collect SolutionPack Block machine. Use the following syntax to run the script:
TestWMI.ps1 -Computer <ip-or-hostname> -Username <domain-or-machine\username> -Password <password> [-NoPing]
- Remote Hyper-V host IP address or hostname
- Username used to perform remote WMI queries, in the format DOMAIN\username for domain users or MACHINE\username for local users
- Password of the user specified with the -Username parameter
- (optional) If the remote Hyper-V host is blocking ping requests, you must use this parameter to skip connectivity tests