ViPR SRM 3.6 – SolutionPack for EMC® VNX Summary Sheet

Table of Contents

Overview

Learn how to install and configure the SolutionPack for EMC VNX. The SolutionPack for EMC VNX collects performance, topology, and capacity data from your VNX and VNXe systems and displays the data in easy-to-use reports within ViPR SRM.

With this SolutionPack, you can unify your view of multiple VNX and VNXe systems, including physical storage to virtual storage relationships. Capacity reports, such as Raw Capacity Usage, Usable Capacity, and File Systems Allocation, help you to improve the availability of business critical applications and services by ensuring that those applications have the storage resources they need to operate effectively.

SolutionPack for EMC VNX

SolutionPack for EMC VNX

Back to Top

Technical Specifications

Main reports

Summary
Overview dashboard
Array Summary
Reports the system type, serial number, system name, IP, model and OE.
Block, <SERIAL #>
Reports indicators such as Raw capacity, number of LUNs and if the element is in problem.
Raw Capacity
Reports the overall raw capacity in TB.
Block Usable Capacity
Reports the overall block usable capacity.
FileSystems Utilization
Reports free and used capacity across all FileSystems.
CPU (%)
Reports the overall CPU and DataMover usage throughout all of the systems.
Block Throughput (IOPS)
Reports the overall Block IOPS across all VNX/CLARiiON systems.
File Throughput (IOPS)
Reports the overall File IOPS across all VNX volumes.
Block Systems (All Reports)
Reports key indicators such as block usable capacity and processor utilization.
File Systems (All Reports)
Reports key indicators such as CIFS/NFS IOPS, deduplication, and the number of CIFS/NFS shares.
Integrated Unified Systems (All Reports)
Reports key indicators for VNXe systems such as the amount of IOPS and the overall health of the systems.
Management
Reports a summary of all systems including their model, serial number, system OE and number of metrics.

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

Preparing your VNX for discovery and data collection

Identify the information required to support resource discovery and data collection before installing the SolutionPack for EMC VNX and perform the necessary pre-configuration.

ViPR SRM uses Navisphere Secure CLI (NavisecCLI) installed on the suite Collector host to access the VNX arrays.

EMC recommends matching Naviseccli versions with Block Operating Environment versions of VNX systems configured in the Collector. For information on compatible Block OE and Naviseccli versions, refer to the VNX OE for Block Release Notes and the Unisphere Host Agent/CLI and Utilities Release Notes on EMC Online Support.

For block and unified data collection, you must enable statistics logging on the array. To enable statistics logging, refer to Unisphere documentation.

Back to Top

Configuring simple authentication

You can configure simple authentication with VNX arrays using the default ViPR SRM account.

In order to poll and collect performance statistics from a VNX array, administrator privileges are required for the user account used to access the arrays.

Note Image
The preferred method for secure polling and collection of data from VNX arrays is to configure authentication using a Unisphere security file. Refer to Unisphere security file authentication.

Procedure

  1. Configure the default ViPR SRM account (apg) with administrator privileges to access the VNX array as described in the Unisphere documentation.
  2. Validate access to the VNX array by running the following block command: naviseccli -h (host) -user username -password password -scope 0 getagent
Back to Top

Unisphere security file authentication

A Unisphere security file is the preferred method to provide secure polling and data collection from VNX arrays.

By default, the ViPR SRM Collector runs using the local system account which is a special Windows user with no environment. The preferred secure method is to create a Unisphere security file, an encrypted file stored on the Collector host.

When you create a security file, the username you use to log in to the current host is automatically stored in the security file, or you can specify an alternative username for the security file in the -AddUserSecurity request using the optional -user switch. If you omit the -user switch, the security file uses your current username. You can also target the security file at a specific storage system using the -ip option.

You can store the security file on the Collector host and edit parser XML files to include this path which will provide the required authentication to access the arrays.

Note the following:

  • By default, the security file is stored in your default home directory. With NavisecCLI, you can specify an alternative file path using the optional -secfilepath switch.
  • Once the security file exists, you can edit XML configuration files that are used to poll and collect data to use the path to the security file on the Collector host. The security file handles authentication.
  • For details on configuring a security file on a host, refer to the Unisphere documentation.
Back to Top

Configuring VNX arrays for file storage discovery

Learn how to configure VNX arrays for file storage discovery.

Procedure

  1. Log into Control Station as the root user.
  2. Open the nas_mcd.cfg configuration file in the /nas/sys/ directory.
  3. Enable the XML–API service by uncommenting the following entry:
    daemon "XML API Server"
            executable      "/nas/sbin/start_xml_api_server"
            optional        yes
            canexit         yes
            autorestart     yes
            ioaccess        no
    
  4. Type # service nas start, and press Enter to restart the XML-API service.
  5. If you have multiple VNX arrays in your storage environment, repeat this procedure on each VNX array.
Back to Top

Installing the SolutionPack

After you log in as an administrator, you can install a SolutionPack from Centralized Management.

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. Make a selection in the Alerting on data collection field.
    If you select Add a new Alerting on data collection, select the appropriate value from the drop-down menu in the Alerting Web-Service Instance field.
  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. 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.
  16. In Event server hostname or IP address, select the Backend host on which the Events Listener is installed.
  17. In Event server port number select the port number for the event server.
  18. Select Configure Alert consolidation.
  19. In Alert consolidation server hostname or IP address, select the Primary Backend host.
  20. In Alert consolidation server port number, select the port used for alert consolidation.
  21. In Naviseccli Path, type the path if using a non-default path, or leave blank if you are using the default path.
  22. Select Use advanced settings to configure polling and alert settings.
  23. Click Next.
  24. From the Event database drop-down menu, select existing settings that have been specified for other components, or select Add a new Event database.
    If you select Add a new Event database, type the information about the new event database.
  25. Click Next.
  26. In Administration Web-Service Instance, select the Frontend host.
  27. Click Install.
  28. Click Ok when the installation is complete.
  29. Click Discovery Center > Devices Management.
  30. Click VNX.
  31. Click Add new device.
  32. From Server, select the server where the device will be dispatched.
  33. From Instance, select the instance of the emc-vnx-collect where the device will be dispatched.
  34. In VNX type, select Block, File, Unified, or Integrated Unified.
    If the following fields appear, enter the information specified:
    1. In Unique friendly name for the VNX system, type the name.
    2. In SP A IP, type the IP address of the SPA.
    3. In SP B IP, type the IP address of the SPB.
    4. In Use Naviseccli security file, select this checkbox if you are using the security file.
    5. In User Scope, select LDAP, Global or Local.
    6. In Naviseccli Username and Naviseccli Password, type the Naviseccli credentials for the block storage systems.
    7. In Primary control station IP, type the IP address of the primary control station.
    8. In Secondary control station IP, type the IP address of the secondary control station.
    9. In VNX File username and VNX File password, type the credentials for the file storage system.
    10. In Management IP or hostname, type the IP address for the integrated unified system.
    11. In Username, type the username for the integrated unified system.
    12. In Password, type the password for the integrated unified system.
  35. Click Test to validate the credentials.
  36. Click Ok.
  37. Click Save.
  38. In the tree, click SolutionPacks and navigate to the EMC VNX SolutionPack to verify the installation.

After you finish

After installing or updating a SolutionPack, new data will not be available for three polling cycles. The data is available to the UI every hour with the Property Store task. This task can be run earlier, if desired, by selecting the Property Store task found on the Frontend host.

Back to Top

Updating SolutionPack alert definitions

When you update a SolutionPack, any modified alert definitions supported in the updated version are not updated by default. This is expected behavior.

To update all of the alerts:

Procedure

  1. In the Alerting Frontend, navigate to Local Manager > Alert definitions > <SolutionPack Name> definitions.
  2. Highlight <SolutionPack Name> definitions, and click the Export icon to create a backup of the old alerts.
  3. Delete all of the non-custom alerts below the <SolutionPack Name> definitions node.
  4. In Centralized Management, navigate to SolutionPacks > Storage > <SolutionPack Name> in the tree.
  5. In the table, click the Reconfigure icon in the Pre-configured alerts row.
  6. Click Reconfigure.
  7. In the Alerting Frontend, navigate to Local Manager > Alert definitions > <SolutionPack Name> definitions to see the updated alert definitions.
Back to Top

Limitations

VNX Free Raw Disk Capacity values are not the same as EMC Unisphere Free Raw Capacity values. Unisphere Free Raw Capacity counts both internal operation space (vault drives) and the space available for user LUNs. Free Raw Disk Capacity only counts the space available for user LUNs.

The displayed value for Quota Capacity is different from that of the CLI. The CLI returns values in KB with a greater level of precision than the Unisphere returns which are in GB and taken out to three levels of precision.

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