ViPR SRM 3.6 – SolutionPack for Microsoft Hyper-V Summary Sheet
Table of Contents
Overview
Learn how to install and configure SolutionPack for Microsoft Hyper-V. The SolutionPack for Microsoft Hyper-V generates real-time and historical reports so you understand Hyper-V performance through global and detailed status of Hyper-V hosts and underlying virtual machines.

SolutionPack for Microsoft Hyper-V
Technical specifications
Main reports
- Inventory
- 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.
Supported collection interfaces
For information about supported collection interfaces, refer to the ViPR SRM Support Matrix.
Back to TopWhere to find the latest SolutionPack software
Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.
This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack.
Back to TopConfiguring credentials for SolutionPack for Microsoft Hyper-V
- 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
Requirements for data collection
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.
Installing the SolutionPack
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.
Procedure
- Click Administration.
- Click Centralized Management.
- Click SolutionPacks.
- Click SolutionPack Center.
- Select the SolutionPack in the Browse and Install SolutionPacks window.
- Click Install.
- Type the instance name.
- Assign a server for each component.
In a typical four server deployment, the recommended servers are selected automatically.
- Click
Next.
The window displays data collection details.
- From the
Data collection drop-down menu, select existing settings that have been specified for other components, or select
Add a new data collection.
If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data to, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
- Click
Next.
The window displays reports settings.
- In Administration Web-Service Instance, select an existing instance or create a custom instance.
- Click Install.
- Click Ok when the installation is complete.
- Click .
- Click Microsoft Hyper-V.
- Click Add new device.
- Select the server and collector instance where you want to store the configuration details for this device, and then enter the hostname or IP address of the host, supply the login credentials, and specify the appropriate configuration settings.
Clicking the Test button results in a warning message that can be ignored.
- Click OK.
- Click Save.
Using a test script to query WMI objects
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]
- -Computer
- Remote Hyper-V host IP address or hostname
- -Username
- Username used to perform remote WMI queries, in the format DOMAIN\username for domain users or MACHINE\username for local users
- -Password
- Password of the user specified with the -Username parameter
- -NoPing
- (optional) If the remote Hyper-V host is blocking ping requests, you must use this parameter to skip connectivity tests
Confirming report creation
After you install a SolutionPack, you can view its reports.
To view the reports:
Procedure
- Go to .
- Click the SolutionPack to view its reports.
Results
Troubleshooting
Report display problems
What to do if data does not appear in any reports
Procedure
- After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
- Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
- To view the log files for errors, go to Centralized Management and click .
Running a scheduled task to import data into reports
After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.
Before you begin
Allow at least three polling cycles to pass before manually running the scheduled task.
Procedure
- Click Administration.
- Click Centralized Management.
- Expand Scheduled Tasks.
- Click Database.
- Select the import-properties-Default task.
- Click Run Now.
- Confirm success in running the task in the Last Result and Last Result Time columns.
What to do if data does not appear in some reports
Procedure
- Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
- Search for the metric in the database.
- To view the log files for errors, go to Centralized Management and click .
Searching for metrics in the database
You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.
Procedure
- Go to the Administration page.
- Under Modules, click Management of Database Modules.
- On the
Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
For example, to list up to 100 results of the SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
- Click
Query.A list of the metric results appears. If nothing displays, the metric is not being collected.
Viewing collector errors in the Collector-Manager log files
Review the Collector-Manager log files to troubleshoot problems with data collection.
Procedure
- Click Administration.
- Click Centralized Management.
- Expand Collecting.
- Click the Collector-Manager for your collector instance.
Collector-Manager::<Collector-Manager instance> - <physical_host_ID>
- Expand Log Files and click the View File icon to review the configuration error messages.