SolutionPack for VMware vCenter 3.7 Summary Sheet – Service Assurance Suite 9.4.1

Table of Contents


The SolutionPack for VMware vCenter generates real-time and historical reports that help you understand VMware performance for VMware Hosts, Virtual Machines, virtual networks and DataStores.

Main reports

vCenter datacenter overview

Detailed datastore information

Detailed Virtual Machines, both running and offline

Back to Top

Technical specifications

SolutionPack version


Compatible EMC M&R versions


Supported VMware vCenter versions

Note Image
VMware vCenter Server and ESX(i) must be 4.1 or later, although 5.1 or later is recommended.

Back to Top

Configuring the SolutionPack to collect Powerpath data

This procedure is required to collect PowerPath data from ESX servers.

For monitoring PowerPath performance and path status, an RTools host is required. RTools is the remote CLI software for managing the PowerPath software on ESXi (or other) hosts. The Collector will use the Generic-RSC Collector to issue RTools command scripts to the RTools host to collect PowerPath data directly from the ESXi servers.


  1. Add the host name and credential of every ESXi host to the RTools default lockbox. Commands will fail if the lockbox is not populated.
    The first use of the command creates the lockbox if necessary.
  2. The RTools host has to be discovered by the Generic-RSC Collector. Discover it through the SolutionPack for Physical Hosts using the ESX Linux or the ESX Windows host type. Choose the Linux or Windows type appropriate for the RTools host so that the collector can issue the correct format scripts.
  3. Create the default lockbox on RTools Host and add ESXi hostname credentials:
    rpowermt setup add_host host= username= password=
  4. Turn on performance monitoring on ESXi host from Rtools (if needed):
    rpowermt set perfmon=on interval= host=
  5. For PASSWORD based discovery Suse Linux hosts from 3.0 RSC, it requires edits to the sshd_config file. Note this file is located under /etc/ssh directory on discovery hosts. You must enable "PasswordAuthentication" and restart sshd service on the host.

    lglah196:~/.ssh # grep Password /etc/ssh/sshd_config #PasswordAuthentication no #PermitEmptyPasswords no

    lglah196:~ # /etc/init.d/sshd restart Shutting down SSH daemon done Starting SSH daemon done

    lglah196:~ #

Back to Top

Installing this SolutionPack

Before you begin


  1. Click Administration .
  2. Click Centralized Management.
  3. Click SolutionPack Center.
  4. Select the SolutionPack in the Browse and Install SolutionPacks window.
  5. Click Install.
  6. Type the instance name.
  7. Assign a server for each component.
    In a typical four server deployment, the recommended servers are selected automatically.
  8. Click Next.
    The window displays a note about Alert Consolidation.
  9. Click Next.
    The window displays pre-configured alert details.
  10. To receive alerts, select Enable the Host PowerPath Alerts.
  11. In Recipient for email alerts, enter the email addresses in which to send the alerts.
  12. Click Next.
    The window displays data collection details.
  13. 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.
  14. From the Frontend Web service drop-down menu, select existing settings that have been specified for other components, or select Add a new Frontend Web service.
    If you select Add a new Frontend Web service, type information about the Frontend Web service.
  15. Leave Enable Topology Backend on data collected checked.
  16. From the Topology Service drop-down menu, select existing settings that have been specified for other components, or select Add a new Topology Service.
    If you select Add a new Topology service, provide information about the topology service and the web service. In Topology Service hostname or IP address, specify the Primary Backend.
    From the Web-Service Gateway drop-down menu, select existing settings that have been specified for other components, or select Add new gateway. If you select Add new gateway, provide information about the web-service gateway where the topology service resides.
  17. Optionally, select Do you want to configure advanced settings to configure the metric collection level, polling intervals, collection thread settings, and the re-synch interval.
    1. In Metric Collect Level, select the level of metrics you want the SolutionPack to collect per VMware collector block. The Metric Collect Level is an internal setting that tells the SolutionPack for VMware vCenter how much data to collect. This setting is not related to vCenter statistics levels.
      Collect-Level 1 collects the minimum required metrics related to capacity, topology, memory, and CPU.
      Collect-Level 2 collects all metrics supported by Collect-Level 1 and additionally all metrics related to disks and memory.
      Collect-Level 3 collects all supported metrics, which includes metrics collected under Collect-Level 1 and Collect-Level 2.
    2. In Polling interval for VMware vCenter collection, select a polling interval.
    3. In Polling interval for VM files only, select a polling interval.
    4. In Number of collecting threads, enter the number of collection threads.
    5. In Number of collecting threads for VM files, enter the number of collection threads.
    6. In Re-Sync interval, select an interval.
  18. Click Next.
  19. From Event database, select a database.
    If you select Add a new Event Database, add the Primary Backend host in the Database hostname or IP address field.
  20. Click Next.
    The window displays reports settings.
  21. Click Next.
  22. Select Collect performance metrics for PowerPath Bus to collect performance metrics for all the logical Bus managed by PowerPath agent.
  23. Select Collect performance metrics for PowerPath LUNs to collect performance metrics for all the logical devices managed by PowerPath agent.
  24. Select Collect PowerPath range-bound performance metrics to collect range-bound performance metrics. Selecting this option increases metric count significantly. Be sure to correctly size your application before enabling this option.
  25. Select Do you want to configure advanced settings to set the absolute path location of the sudo and pbrun binaries.
  26. Click Install.
  27. Click Ok. Monitor the installation logs to ensure that the installation completes successfully.
  28. Click Discovery Center > Devices Management.
  29. Click VMware vCenter (vmware-vcenter-collect <version>) for data collection and/or VMware vCenter (vmware-vcenter-events <version>) for vCenter events collection.
    These steps describe how to add VMware vCenter hosts individually. For information about using discovery groups to use the same credentials to discover multiple VMware vCenter hosts, see Adding devices to discovery groups.
  30. Click Add New Device.
  31. From Server, select the server where the device will be dispatched.
  32. From Instance, select the instance of the vmware-vcenter-collect where the device will be dispatched.
  33. In Hostname or IP address, type the vCenter service host. Enter the Username and Password used to poll vCenter.
  34. Click Ok.
  35. Click Save.
Back to Top

Post-install requirements

Perform these operations after the installation is complete.

To enable PowerPath LUN or Path performance data collection on Linux, navigate to the APG/Collecting/Remote-Shell-Collector/<Instance Name>/scripts directory.


  1. In the script, set want_powerpath_lun_performance=1.
    By default, this flag is set to zero.
  2. To enable the PowerPath LUN or Path performance data collection on Windows:
    1. Navigate to the C:\Program Files\APG\Collecting\Remote-Shell-Collector\<Instance Name>\scripts\windows directory.
    2. In the LunMappingDetection.ps1 script, set powerPathPerformanceCollection=enabled.
      By default, this flag is set to disabled.
  3. To enable events reporting, open the Web-Application configuration file (APG.xml) and uncomment the vmware-vcenter section and the ResourceLink tag.
  4. Restart the Tomcat service to make the changes effective.
Back to Top

Adding devices to discovery groups

Discovery groups simplify the process of working with a large number of devices and their corresponding IP addresses/hostnames and discovery credentials. For example, if you have set of four user/password credentials used among twenty devices, using a discovery group allows you to enter each set of credentials and all of the IP addresses/hostnames, and the discovery group will match the correct credentials to each device.


  1. From Centralized Management, click Discovery Center > Discovery Center Backends.
  2. Select the Backend server.
  3. Click Register.
  4. Select the collector you want to use for discovering your SolutionPack objects.
  5. If you are collecting VMware vCenter events, select the primary backend you want to use for discovering the events.
  6. Click Register.
  7. Click Discovery Center > Devices Management.
  8. Click <Device Name>.
  9. Click the Discovery Groups tab.
  10. Click Add new Discovery group.
  11. Provide a name for the group and click Ok.
  12. Click the newly created group.
  13. Under Credentials, click Add new entry.
  14. Type the username.
  15. If required, select the authentication type.
  16. If you are using password authentication, provide the password and click Ok.
  17. If you are using key-based authentication, provide the absolute location of the private key and click Ok.
  18. Repeat the previous five steps to add as many username/password (or key) combinations as you would like.
  19. Under Hostname or IP address, click Add new entry.
  20. Provide the Hostname/IP Address of the device. If required, provide the Network Port. Click Ok.
  21. Repeat the previous two steps to add as many devices as you would like.
  22. Click Save.
  23. Click the Collected Devices tab.
  24. Click Discover.
  25. Select the Discovery group and Discovery Mode and click Ok.
    The progress bar is displayed above the Collected Devices tab.
  26. When the progress bar is gone, click theDiscovery Results tab.
  27. Click the group name that you added.
  28. Under the group name, you can see the status of all the devices that you added.
  29. Click Import to Collected Devices.
  30. Merge the devices if you want to retain older devices that were added previously.
  31. Click Ok.
  32. Select the action and click Continue.
  33. Click Save.

    All of the devices have been added to discovery

    Review your devices and credentials to avoid lockout of devices due to multiple attempts of incorrect credentials. EMC recommends that you create groups in such a way that devices have a minimal set of credentials to be tried against. EMC recommends using common public-private key pairs for multiple devices.

Back to Top


The Host Attributes report is missing the IP Address for VMware vCenter.

Back to Top