SolutionPack for EMC VNX

Table of Contents

Back to Top

Overview

This article explains 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.

This article applies to EMC ViPR SRM version 3.5.1.

report screen

SolutionPack for EMC VNX

Back to Top

Technical Specifications

SolutionPack version

Compatible ViPR SRM version

Polled metrics

VNX:

VNXe:

Main reports

Summary
Overview dashboard
System 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.
File FileSystems Utilization
Reports free and used in MB.
CPU (%)
Reports the overall CPU usage throughout all of the systems.
Block IO/s
Reports the overall IO usage throughout all of the systems.
File Ops/s
Reports the overall OPs usage throughout all of the systems.
Block Systems (All Reports)
Reports key indicators such as block usable capacity and processor utilization.
File Systems (All Reports)
Reports key indicators such as NFS Ops/s, deduplication, and the number of shares.
Chargeback Reports
Reports key indicators such as top 10 applications by cost and cost distribution by business unit.
Management
Reports a summary of all systems including their model, serial number, system OE and number of metrics.

Comments
To collect performance data for VNX MetaLUNs with Operating Environment for Block (“FLARE”) 05.32, version 05.32.000.5.209 or higher must be used
CIFS Ops/s and Top 5 CIFS users reports are supported with Operating Environment for File 7.1 or later.
Navisphere CLI commands are used to communicate with the VNX. EMC recommends matching Navisphere CLI versions with the Block Operating Environment versions of VNX systems configured in the SolutionPack.
For example, if the firmware version of the Block side is 05.32.x, Navisphere CLI 7.32.x or higher should be used. For more information on compatible Block OE and Navisphere CLI versions, see the "VNX OE for Block Release Notes" and the "Unisphere Host Agent/CLI and Utilities Release Notes" located on EMC Online Support.
SSH access to VNX-File / Celerra with an "operator" user. SSH access is needed between VNX Collector host and Control Station to download files in /tmp/w4n_data via SFTP.

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 consolidation of file alerts

Configure forwarding of VNX file alerts to ViPR SRM.

Note Image
Consolidation of VNX block alerts does not require separate configuration.

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

  • Core modules must be up-to-date in all servers because not all module dependencies are validated during the SolutionPack installation or update process.
  • Managing Alert Consolidation explains how to configure alerts consolidation

Procedure

  1. Log in.
  2. Click Administration.
  3. Click Centralized Management.
  4. Click SolutionPacks.
  5. Select SolutionPack Center.
  6. Select the SolutionPack in the Browse and Install SolutionPacks screen.
  7. Click Install.
  8. Type the instance name.
  9. Assign a server for each component.
    In a typical four server deployment, the components are assigned as shown below:
    • Alert consolidation - Primary Backend
    • Pre-configured alerts - Primary Backend
    • Data collection - Collector
    • Events - Primary Backend
    • Reports - Front End
  10. Click Next.
  11. Click Next.
  12. In the Pre-configured alerts window, make a selection in the Alerting on data collection field.
    If you select Add a new Alerting on data collection, select the Primary Backend host in the > Alerting Web-Service Instance field.
  13. Click Next.
  14. In the Data collection window, select a value for Data Collection.
    If you select Add a new data collection, type information about the data collection. In > Hostname or IP address to send data, 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. 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.
  17. Select a value for Property Store configuration.
    If you select Add a new Property Store configuration, type information about the Property Store. Select the Frontend host.
  18. Leave Enable Topology Backend on data collected checked.
  19. Select a value for Topology Service.
    If you select Add a new Topology Service, select the Primary Backend host and type the information about topology queries.
    • Select a value for Web-Service Gateway.
    • If you select Add new gateway, type information about the gateway.
  20. In Event server hostname or IP address, select the Backend host on which the Events Listener is installed.
  21. In Event server port number select the port number for the event server.
  22. Select Configure Alert consolidation.
  23. In Alert consolidation server hostname or IP address, select the Primary Backend host.
  24. In Alert consolidation server port number, select the port used for alert consolidation.
  25. In Naviseccli Path, type the path if using a non-default path, or leave blank if you are using the default path.
  26. 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.
  27. Use the plus (+) icon to add more VNX arrays.
  28. Select Use advanced settings to configure polling settings.
  29. Click Next.
  30. Select a value for Event database.
    If you select Add a new Event database, select the Primary Backend host and type the information about the new event database.
  31. Click Next.
  32. In Administration Web-Service Instance, select the Frontend host.
  33. Click Install.
  34. After installation is complete, select Centralized Management > SolutionPack to verify the installed SolutionPack.

After you finish

To enable events reporting, edit your Web-Application configuration file (APG.xml), by uncommenting the emc-vnx section (uncomment the ResourceLink tag). You will then need to restart the Tomcat service in order to make the change effective.

The Tomcat Catalina APG.xml file is located in: /APG/Web-Servers/Tomcat/Default/conf/Catalina/localhost

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

During SolutionPack update, any new alert definitions supported in the updated version do not get updated by default. This is expected behavior.

To add newly introduced alert definitions after updating, follow the steps below.

Procedure

  1. In Centralized Management, navigate to SolutionPacks > Storage > EMC VNX in the tree.
  2. In the table, click the pen icon button to the left of Pre-configured alerts.
  3. Click Reconfigure.
  4. In the Alerting Frontend, navigate to Local Mananger > Alert definitions > EMC VNX to see the newly added alert definitions.