ViPR SRM 3.6 – SolutionPack for VMware vCenter Summary Sheet

Table of Contents

Overview

Learn how to install and configure the SolutionPack for VMware vCenter.

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.

SolutionPack for VMware vCenter

SolutionPack for VMware vCenter

Back to Top

Technical specifications

Main reports

vCenter datacenter overview

Detailed datastore information

Detailed Virtual Machines, both running and offline

Supported collection interfaces

For information about supported collection interfaces, refer to the ViPR SRM Support Matrix.

Back to Top

Where 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 by completing a Support Request (SR) form, which is available on the EMC Online Support website at http://support.emc.com.

Back to Top

Configuring the SolutionPack for VMware vCenter 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 ViPR SRM 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.

Procedure

  1. Add the host name and credential of every ESXi host to the RTools default lockbox. Since ViPR SRM does not know the ESXi credentials, ViPR SRM 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 ViPR SRM 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 SRM 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

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Click SolutionPacks.
  4. Click SolutionPack Center.
  5. Select the SolutionPack in the Browse and Install SolutionPacks window.
  6. Click Install.
  7. Type the instance name.
  8. Assign a server for each component.
    In a typical four server deployment, the recommended servers are selected automatically.
  9. Click Next.
    The window displays a note about Alert Consolidation.
  10. Click Next.
    The window displays pre-configured alert details.
  11. To receive alerts, select Enable the Host PowerPath Alerts.
  12. In Recipient for email alerts, enter the email addresses in which to send the alerts.
  13. Click Next.
    The window displays data collection details.
  14. 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.
  15. Leave Enable alerting on data collected checked.
  16. From the Alerting on data collection drop-down menu, select existing settings that have been specified for other components, or select Add a new alerting data collection.
    If you select Add a new alerting on data collection, type information about the alerting configuration. In Alerting Backend hostname or IP address, specify the Primary Backend host.
  17. 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.
  18. Leave Enable Topology Backend on data collected checked.
  19. 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.
  20. 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 ViPR SRM 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.
  21. Click Next.
  22. 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.
  23. Click Next.
    The window displays reports settings.
  24. Click Next.
  25. Select Collect performance metrics for PowerPath Bus to collect performance metrics for all the logical Bus managed by PowerPath agent.
  26. Select Collect performance metrics for PowerPath LUNs to collect performance metrics for all the logical devices managed by PowerPath agent.
  27. 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.
  28. Select Do you want to configure advanced settings to set the absolute path location of the sudo and pbrun binaries.
  29. Click Install.
  30. Click Ok when the installation is complete.
  31. Click Discovery Center > Devices Management.
  32. Click VMware vCenter.
  33. Click Add new device.
  34. From Server, select the server where the device will be dispatched.
  35. From Instance, select the instance of the vmware-vcenter-collect where the device will be dispatched.
  36. In Hostname or IP address, type the vCenter service host. Enter the Username and Password used to poll vCenter.
  37. Click Ok.
  38. 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.

Procedure

  1. In the LunMappingDetection.pl 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

Limitations

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

Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. 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.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

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

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

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

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Metrics.
  3. 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 Capacity metric with the properties of device and IP, type name=='Capacity' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top