ViPR SRM 3.6 – SolutionPack for EMC® VMAX Summary Sheet

Overview

Learn how to install and configure the SolutionPack for EMC VMAX. The SolutionPack for EMC VMAX reports Input/Output Operations Per Second (IOPS) on Disks, directors, and devices to measure performance and assure service availability. Alerts are consolidated from EMC VMAX and shown on the All Alerts Console.

Technical specifications

Main reports

Storage Pool Capacity Planning: Trending and forecasting capacity for all arrays and pools, giving expected capacity based on trend
Thin Devices: Trending and forecasting capacity for all Thin Devices, giving bound devices capacity and the total Thin Devices consumed
Tiers: Trending and forecasting capacity for all arrays and tiers, giving expected capacity based on trend
All disks: Table listing information from all of the disks, including it's array, name, type, group RPM, director, IOPS, throughput and capacity
By DiskGroup: Table listing information from all of the disk groups, including it's array, disk group name, director, raw capacity, hyper capacity, free capacity and usage percentage
Masking views Summary: Capacity as seen by hosts in the masking view
Pool Capacity: Capacity information for all of the Pools available, including array, pool name, pool state and capacity used
Configured Usable: Trending and forecasting on the sum of all thick devices (including standard, BCV and R1 devices) plus the sum of all data devices (pool storage)
Hot Spares: Trending and forecasting on the sum of disks dedicated as hot spares
RAID overhead: Report on the array capacity used to support RAID protection overhead
Unconfigured: Report on all thick devices plus the sum of all data devices (pool storage)
Array ID: Overview of all VMAX main components, physical and logical
Arrays: Lists all the VMAX systems
Disks: Lists all disks and related key information, for all arrays
Directors: Lists all directors and related key information, for all arrays
Ports: Lists all ports and status for all arrays
Pools: Lists all pools and related key information, for all array.
Storage Groups: Lists all Storage Groups and related key information
Ports: Lists all ports and status for all arrays
Devices: Lists all devices and related key information, for all arrays
Storage Groups Summary: Performance and capacity of all storage groups for this array, including IO Density and Response Time
FE|BE|RDF Directors: Key performance metrics for all directors and ports

Supported collection interfaces

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

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.

Configuring the access credentials

M&R uses different accounts when running SolutionPacks.

VMAX Performance collection via EMC SMI-S Provider for VMAX:

Username - no default SMI-S Provider Username is provided during the deployment of SolutionPack for EMC VMAX but the EMC SMI-S Provider out-of-the-box username is admin
Password - no default SMI-S Provider Password is provided during the deployment of SolutionPack for EMC VMAX but the EMC SMI-S Provider out-of-the-box password is #1Password

VMAX Performance collection via Unisphere for VMAX:

Username - the default is smc
Password - the default is smc

Preparing EMC VMAX for discovery and data collection

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

ViPR SRM requires EMC Solutions Enabler to collect array topology details for VMAX arrays (VMAX3 arrays use SMI-S, not Solutions Enabler); optionally ViPR SRM requires Unisphere for VMAX and/or the EMC SMI-S Provider to collect array performance details. If both EMC Solutions Enabler and EMC SMI-S Provider are present, they must be on the same host. There are two supported scenarios for topology collection. The Solutions Enabler proxy scenario is recommended because the Collector and the Solutions Enabler are not competing for host resources.

The host running Unisphere for VMAX and the ViPR SRM collector host must have the same date and time and must be in same time zone; otherwise, performance collection will fail.

Solutions Enabler proxy scenario (recommended)

In this scenario, you install Solutions Enabler on the ViPR SRM Collector host designated to collect data from VMAX.

You configure Solutions Enabler to communicate over TCP/IP with a Solutions Enabler instance on the remote SYMAPI server (Array Provider).

You should add two additional gatekeepers to the host that is already monitoring the Symmetrix array.

To support collection using the SYMAPI Server, two additional gatekeepers will be required per array on the remote Solutions Enabler host. For example, if there are already six gatekeepers per array then you will need to add two more for a total of eight gatekeepers per array.

VMAX3 discovery scenario

VMAX3 discovery uses SMI-S Provider for collecting topology and Unisphere for VMAX for performance details. Installing SMI-S and Unisphere for VMAX locally on a ViPR SRM appliance will cause the Collector, Solutions Enabler, and Unisphere for VMAX to compete for host resources. Because of this, it is highly recommended that you use proxy mode. In proxy mode, SMI-S (along with SE) will be installed on a host connected to arrays to be discovered. The SMI-S connectivity to an array can be tested using the TestSmiProvider utility, as shown below. When using the utility, accept the default answers and then issue the dv command.

# cd /opt/emc/ECIM/ECOM/bin
#./TestSmiProvider  
Connection Type (ssl,no_ssl,native) [no_ssl]:
Host [localhost]:
Port [5988]:
Username [admin]:
Password [#1Password]:
Log output to console [y|n (default y)]:
Log output to file [y|n (default y)]:
Logfile path [Testsmiprovider.log]:
Connecting to localhost:5988
….
Namespace: root/emc
repeat count: 1
(localhost:5988) ? dv
++++ Display version information ++++
Solutions Enabler version: V8.x.y.z

Firmware version information:
(Local)  VMAX 000196700566 (VMAX200K) : 5977.477.457
(Local)  VMAX 000196700567 (VMAX200K) : 5977.477.457
(Local)  VMAX 000196700572 (VMAX200K) : 5977.477.457

While installing the SolutionPack, you can verify VMAX3 connectivity on the ViPR SRM Collector Appliance via Discovery Center using the Test button.

Local Solutions Enabler scenario

The Local Solutions Enabler scenario supports topology collection for VMAX arrays using a VMAX Solution Pack Collector which has been installed on the same host as the Solution Enabler software.

Implementing the Local Solutions Enabler scenario includes the advantages of reduced network calls and a more secure configuration. However, the Collector software will require additional Solutions Enabler host CPU and memory resources.
The Solutions Enabler (proxy) scenario is the preferred configuration since the Collector and Solutions Enabler are not competing for host resources.
The Local Solutions Enabler scenario requires that each VMAX array have at least 6 Gatekeeper Devices be created on the host.

If the Solutions Enabler was installed to a Virtual Machine then Raw Device Mappings must used when creating the Gatekeeper Devices
If the Local Solutions Enabler is desired and if VMAX LUN Performance details are required, then it is recommended that you install the EMC SMI-S Provider kit on your host since it includes the required Solutions Enabler components. This is in contrast to installing a standalone Solutions Enabler kit and then installing the SMI-S Provider over it which could potentially cause incompatibility issues if the Solutions Enabler versions are different. Refer to EMC SMI-S Provider documentation for installation details.

Solutions Enabler proxy scenario

The Solutions Enabler proxy scenario supports resource discovery and data collection for EMC VMAX.

In this scenario, no ViPR SRM software is installed on the SYMAPI server. Instead, a client host and server host proxy relationship is configured. This is the preferred configuration for monitoring VMAX arrays.

Client host - You install Solutions Enabler on the ViPR SRM Collector host designated to collect data from VMAX. The client host has no direct connectivity to the array.
Server host - Solutions Enabler already exists on the SYMAPI server with connectivity and gatekeeper access to the array.

The client host is then configured for proxy communicate with the server host over TCP/IP (port 2707, which is the default). In this scenario, map two additional gatekeeper devices to your SYMAPI server.

Configuring Solutions Enabler proxy support

Configure support for the Solutions Enabler proxy scenario.

Before you begin

Install a supported version of EMC Solutions Enabler on the ViPR SRM Collector host. Refer to the EMC ViPR SRM Support Matrix for supported versions used with ViPR SRM.
In a proxy configuration, you must maintain the same Solutions Enabler family version. A mixed 32-bit and 64-bit Solution Enabler is supported in a proxy configuration.
Map two additional gatekeeper devices for ViPR SRM and present them to your SYMAPI server.
Ensure the storsrvd daemon is running on the Server host. You can confirm this by issuing the stordaemon list command on the Server host.

This procedure is applicable for Solutions Enabler or the Solutions Enabler installed with the EMC SMI-S Provider.

Procedure

On the client host on which you installed Solutions Enabler, navigate to the netcnfg file.
On Linux, the file is located at: /var/symapi/config/netcnfg.
On Windows the file is located at: ..\Program Files\EMC\SYMAPI\config

Edit the file to add the remote host to which Solutions Enabler will communicate. Add a line similar to the last line in the following example:

# This is a sample config -- where WWW.XXX.YYY.ZZZ is a valid IP address.     #
# Please use this format for your host.                                       #
#                                                                             #
# <SYMAPI_SERVER>  -  TCPIP  node001  WWW.XXX.YYY.ZZZ  2707  -                  #
# SYMAPI_SECURE  -  TCPIP  node001  WWW.XXX.YYY.ZZZ  2707  SECURE             #
 
SYMAPI_SERVER - TCPIP hostname IP-address 2707 NONSECURE

Select NONSECURE when the server side is configured for NONSECURE, or ANY on the deamons_options file in the SECURITY_LEVEL section.

Set the following System environment variables on the client host:

SYMCLI_CONNECT=<SYMAPI_SERVER>

SYMCLI_CONNECT_TYPE=REMOTE

Option	Description
Windows	The environment variables are shown with the set command at the command prompt. To establish persistent variables use Computer > Properties > Advanced system settings. Select Environment Variables > New to create the two variables as shown above.
Linux	Use the env command to show the environment variables. To establish persistent variables use export to create the two variables as shown above.

Option

Description

Windows

The environment variables are shown with the set command at the command prompt.

To establish persistent variables use Computer > Properties > Advanced system settings. Select Environment Variables > New to create the two variables as shown above.

Linux

Use the env command to show the environment variables.

To establish persistent variables use export to create the two variables as shown above.

On the SYMAPI server host, ensure that the SERVER license key is registered by reviewing the symapi\config\symapi_licenses.dat file. If it is not there, use the symlmf utility to add the license key.
You can also control the Solutions Enabler licenses from the array.

Verifying the Solutions Enabler proxy configuration

Verify proxy configuration success and , if necessary, identify and resolve any configuration issues.

Procedure

From the SYMAPI server host, typesympd list to display a list of devices that are visible to the host. Note the results.
On the client host, type sympd list.
- If the results match, the configuration is complete.
- If the command issued from the client returns a message such as no devices found, continue to the next step.
To isolate the issue:
1. Verify that the same command works on the host with the FC connection to the Symmetrix array.
2. Verify that the environment variables for Solutions Enabler are set using the symcli -def command.
3. Verify that the netcfg file has been edited using the symcfg -services list command.
4. Verify the arrays you intend to monitor using the symcfg list command.
5. Verify that two additional gatekeepers are provisioned from each Symmetrix array using the sympd list command.

Local Solutions Enabler scenario

The local Solutions Enabler scenario supports resource discovery and data collection for EMC VMAX.

In this scenario, you install only the ViPR SRM Collector software directly on the existing SYMAPI Solutions Enabler server.

The Solutions Enabler proxy scenario is the preferred configuration.
Implementing this scenario includes the advantages of reduced network calls and a more secure configuration. However, the Collector software installed on the SYMAPI server will require processing cycles from that server.
This scenario requires two additional gatekeeper devices be mapped to your Collector host.

Configuring VMAX arrays for consolidation of availability alerts

Use this procedure to configure forwarding of availability alert traps (SNMP v1) from VMAX arrays to the suite.

VMAX performance alerts are collected using the discovery data collection configuration.

Procedure

Log into Solutions Enabler on the array provider host as an administrator.
Navigate to the daemon_options file in the C:\Program Files\EMC\SYMAPI\config\ directory.
In the parameter section SNMP_TRAP_CLIENT_REGISTRATION:
1. Uncomment the line storevntd:SNMP_TRAP_CLIENT_REGISTRATION
2. Add the ViPR SRM trap recipient IP to the trap filter. The trap recipient IP is the Backend host IP.
  The syntax is <IP>,<port>,<filter>,<state>, where <filter> is the filtering level for trap forwarding defined in the FCMGMT-MIB file.
  Example: 10.31.90.148, 2041,10,ACTIVE
In the parameter section LOG_EVENT_TARGETS, uncomment the line storevntd:LOG_EVENT_TARGETS = snmp file.
To identify the arrays from which traps should be forwarded to the suite, type symcfg list, and press Enter.
For each array that should forward alert traps to ViPR SRM:
1. Type symcfg list, and press Enter.
2. In the parameter section LOG_SYMMETRIX_EVENTS, specify the appropriate event categories in the format:
  sid=<SYM serial number>, <event category 1>, <event category 2>\
  Example: SID=000194900854, disk, device, device pool, director, srdf consistency group, srdfa session, srdf link, srdf system, service processor, environmental, diagnostic, checksum, status, events, array subsystem, groups, optimizer, thresh_critical=3, thresh_major=2, thresh_warning=1, thresh_info=0 ;\
To reload the changes to the daemon_options file, type stordaemon action storevntd -cmd reload, and press Enter.
Ensure that the storevntd Event Daemon is running on the provider host.
If you have multiple VMAX array provider hosts in your storage environment, repeat this procedure on each array provider host.

Installing the SolutionPack

Before you begin

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.
Managing Alert Consolidation explains how to configure alerts consolidation.

Data collection instances cannot collect data for both VMAX2/DMX and VMAX3 and arrays at the same time. You need to define separate instances if you plan to collect both VMAX2/DMX and VMAX3 data. It is recommended to include "vmax3" or "vmax2" in the name of the instance to easily select the right instance in the Discovery Center when adding serial numbers to collect.

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 a note about Alert Consolidation.
Click Next.
The window displays pre-configured alert details.
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.
Leave Enable alerting on data collected checked.
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.
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.
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.
From the Type of VMAX array collected drop-down menu, select the type of VMAX arrays collected with this data collection instance.
You cannot collect VMAX3 and VMAX2 arrays using the same instance.
If you are collecting data from VMAX2/DMX arrays, enter the following settings:
1. If Solutions Enabler was installed in the default location, leave the Solutions Enabler bin directory empty. If Solutions Enabler was installed in another location, type the path to the bin directory.
2. In Connection type, select Remote if you are using the Solutions Enabler proxy scenario or Local if you are using a local Solutions Enabler scenario. Refer to Preparing EMC VMAX for discovery and data collection.
3. In SYMAPI Connection name, type the connection name. This is the name of a SYMAPI service, which is configured in the netconfig file (netcnfg). This is not a host name. To view the name that is configured, use the symcfg list -services command.
4. Select a Performance collection type for all arrays and enter the required details.
  Use Do not collect performance if you do not want to collect any performance metrics.
  Use SMI to collect array LUN performance metrics via SMI-S.
  Use Unisphere for VMAX to collect array performance metrics other than LUN performance metrics via Unisphere for VMAX.
  Use SMI and Unisphere for VMAX to collect both array LUN performance metrics via SMI-S and additional metrics via Unisphere for VMAX
5. Select Use advanced settings to configure polling settings.
If you are collecting data from VMAX3 arrays, enter the following settings:
1. Select a Performance collection type for all arrays .
  Use Do not collect performance if you do not want to collect any performance metrics.
  Use SMI to collect array LUN performance metrics via SMI-S.
  Use Unisphere for VMAX to collect array performance metrics other than LUN performance metrics via Unisphere for VMAX.
  Use SMI and Unisphere for VMAX to collect both array LUN performance metrics via SMI-S and additional metrics via Unisphere for VMAX
2. Select Use advanced settings to configure polling settings.
Click Next.
The window displays reports settings.
Click Install.
Click Ok when the installation is complete.
Click Discovery Center > Devices Management.
Click VMAX.
Click Add new device.
In Server, select the server where the device will be dispatched.
In Instance, select the instance of the emc-vmax-collect where the device will be dispatched.
In Array Full Serial Number, type the Symmetrix SID from which data will be collected by Solutions Enabler or SMI-S.
Run the symcfg list command to view a list of arrays.

EMC recommends not to exceed six medium-sized (30K-40K devices) VMAX arrays for each VMAX collector.
Click Test to validate the credentials.
Click Ok.
Click Save.
Performance data will displayed in about an hour.
Discovery of large (> 20K devices) Symmetrix arrays may take long periods of time due to the number of volumes. To address this, discover the Symmetrix on its own instance. This will prevent the discovery from impacting the discovery of other arrays on the same symapi connection and allows the smaller arrays to complete during the polling schedule.

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

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

Configuring Solutions Enabler client access for VMAX

Symmetrix Authorization using symauth provides a secure host and user-based authorization solution. Use this procedure in environments in which Symmetrix Authorization is enabled.

Before you begin

Ensure that you have configured an appropriate Solutions Enabler scenario as described in Preparing EMC VMAX for discovery and data collection.

For more detailed information about Solutions Enabler, refer to the following documents:

EMC Solutions Enabler Symmetrix Array Management Product Guide
EMC Solutions Enabler Symmetrix Security Configuration Guide

The following configuration procedures are specific to a Solutions Enabler proxy configuration. However, you can also use these procedures for a local Solutions Enabler configuration in which the ViPR SRM Collector software is installed directly on the existing SYMAPI Solutions Enabler server. The term "client" refers to the host where the Collector software has been installed.

Procedure

Validate if Symmetrix Authorization is enabled by running the symauth list command on the host that has direct FC connectivity to the arrays to be managed.

Check the status displayed in the the Authorization Control section to determine the required action:

Option	Description
Disabled	Symmetrix Authorization is not configured. In this case, do nothing.
Enabled	Symmetrix Authorization is configured. In this case, you must configure the apg user and ViPR SRM hosts that will be issuing commands. Continue to step 3.

If Symmetrix Authorization is enabled, use the following procedures to complete the configuration:

Configuring host access

Enable the ViPR SRM apg account to access the local Solutions Enabler resources and logs.

This procedure provides an example of configuring access on a host using the Linux operating system.

Procedure

Log in to the Solutions Enabler client host.
Navigate to /var/symapi
Grant the apg user write access to the following Solutions Enabler directories and contents:
1. chown -R apg <SYMAPI_HOME>/config
2. chown -R apg <SYMAPI_HOME>/db
Repeat steps 1-3 for each VMAX Collector server.
Grant the apg user authorization for the Solutions Enabler storapid daemon by navigating to <SYMAPI_HOME>/config/daemon_users and adding the following line to the storapid[Base Daemon] section of the file:
apg storapid <all>
Save and exit the daemon_users file.
Set a password for the apg user.
Repeat steps 5-7 for each VMAX collector server.
Log out and log in as the apg user and run symauth show -username to determine the fully-qualified account name.
Make note of the value displayed in your current username. For example: H:system_name\apg
Repeat steps 9-11 for each VMAX Collector server.

Adding client hosts to existing SYMAUTH configuration

Enable the apg user with read-only monitoring access for VMAX arrays using Solutions Enabler User Authorization.

Before you begin

Complete the procedure described in Configuring host access.

You must be logged in as Root or Administrator.

Perform the following procedure for each VMAX you want to enable ViPR SRM to access.

Procedure

Run the symauth -sid <SID> list command to determine if User Authorization Control is enabled on the local client system.
- If User Authorization Control is disabled (Disabled) for the specific VMAX, proceed to Enabling client authorization.
- If User Authorization Control is enabled (Enabled) and in use (Enforced) for the specific VMAX, continue with this procedure.
Ensure that you are logged in with an existing privileged account (e.g., root or administrator).
Use the find / -name auth.txt command to find the auth.txt file.
Navigate to the folder with the auth.txt file.
Edit the file to include a line based on the results obtained from performing the procedure described in Configuring host access. For example:
assign user H:system_name\apg to role Admin;
Save the file.
Use the symauth -sid <SID> -f auth.txt command to commit changes to the User Authorization User-to-Role map.
Repeat this procedure for each VMAX array.

Enabling client authorization

Use this procedure when User Authorization Control is disabled (Disabled) for the specific VMAX and you want to restrict the apg user to a monitoring role without limiting other accounts in the environment.

Before you begin

You determined that User Authorization Control is disabled by performing the task described in Adding client hosts to existing SYMAUTH configuration.

You are logged in to the client host with local root or administrator credentials.

Procedure

Create an auth.txt file with the following contents:
assign user * to role Admin;
set enforcement enforce;
assign user H:system_name\apg to role Admin;
Repeat step 1 for each VMAX Collector server.
Use the symauth -sid <SID> -f auth.txt command to commit changes to the User Authorization User-to-Role map.
Repeat step 3 for each VMAX array.
Use the symauth -sid <SID> enable command to enable User Authorization Control for a specific VMAX array.
Repeat step 5 for each VMAX array.

Use the symauth list command to validate that User Authorization Control is enabled and enforced.

   S Y M M E T R I X   A U T H O R I Z A T I O N   S T A T U S

Symmetrix ID: 000195700363

  Authorization Control           : Enabled

  Time Enabled                    : Mon Aug  5 12:51:08 2013
  Time Disabled                   : Thu Aug  1 15:54:23 2013
  Time Updated                    : Mon Aug  5 12:51:08 2013

  Enforcement Mode                : Enforce
  Server Policy                   : Trust clients

Validating Symmetrix access controls

Validate that the Symmetrix Access Control (SymACL) security feature is enabled and in use on VMAX systems.

Before you begin

You are logged in to the client host with local root or administrator credentials.

Procedure

Run the symacl list command for each VMAX array. Status information is displayed.

   S Y M M E T R I X   A C C E S S   C O N T R O L   S T A T U S

Symmetrix ID: 000195700363

    Access    Session
    Control   Locked   Time Last Updated
    --------  -------  -------------------------
    N/A       N/A      N/A

Symmetrix ID: 000195700932

    Access    Session
    Control   Locked   Time Last Updated
    --------  -------  -------------------------
    N/A       N/A      N/A

If the Access Control field indicates N/A, SymACL is not enabled on this VMAX system. No action is necessary.
If the Access Control field indicates Enabled, continue this procedure to secure ViPR SRM client systems from a host system in the existing SymACL AdminGrp for each VMAX system.

Create a SymACL access group appropriate to contain the ViPR SRM client systems (e.g., SRMGRP)
Add each client system's unique identifier to the access group.
Repeat for each ViPR SRM client host system.
Grant BASE access rights to the access group just created for all devices (ALL_DEVS).
Repeat this procedure for each VMAX system monitored by ViPR SRM.

Limitation: some alerts not displayed

ViPR SRM fails to receive and display some alerts

If a trap is lost in the network communication, Solutions Enabler is not aware of the host and is not able to resend the lost information.

Confirming report creation

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

To view the reports:

Procedure

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

Results

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

Troubleshooting

Report display problems

What to do if data does not appear in any reports
What to do if data does not appear in some reports
Viewing collector errors in the Collector-Manager log files

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 Collecting > Collector-Manager::<instance name> > Log Files.

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 Collecting > Collector-Manager::<instance name> > Log Files.

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 Metrics.
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.
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> - <host_ID>
Expand Log Files and click the View File icon to review the configuration error messages.

ViPR SRM 3.6 – SolutionPack for EMC® VMAX Summary Sheet

Table of Contents

Main reports

Supported collection interfaces

Solutions Enabler proxy scenario (recommended)

VMAX3 discovery scenario

Local Solutions Enabler scenario

Before you begin

Procedure

Procedure

Procedure

Before you begin

Procedure

Procedure

Before you begin

Procedure

Procedure

Before you begin

Procedure

Before you begin

Procedure

Before you begin

Procedure

Procedure

Results

Report display problems

Procedure

Before you begin

Procedure

Procedure

Procedure

Procedure