SolutionPack Installation Guide - Dell EMC · PDF fileConfiguring sudo for VIO Server and VIO Client host discovery.....161 ... EMC ViPR SRM 3.6.2 SolutionPack Installation Guide 11

EMC® ViPR SRMVersion 3.6.2

SolutionPack Installation GuideP/N 302-002-014

REV 01

Copyright © 2015 EMC Corporation. All rights reserved. Published in USA.

Published May, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC ViPR SRM 3.6.2 SolutionPack Installation Guide

11

13

Getting started 15

What are SolutionPacks?...............................................................................16Licenses........................................................................................................17Browse and install.........................................................................................17Reconfigure an installed SolutionPack.......................................................... 19Update SolutionPacks................................................................................... 21Where to find the latest SolutionPack software..............................................21ViPR SRM and SolutionPack privileges.......................................................... 21

SolutionPack for Brocade FC Switch 29

Overview....................................................................................................... 30Technical specifications................................................................................ 30Brocade switch and SMI agent configuration................................................. 31

Configuring Brocade SMI Agents...................................................... 31Configuring Brocade switches for alert consolidation....................... 32Configuring Brocade switches for SNMP........................................... 32

Installing the SolutionPack............................................................................33Passive host discovery configuration options................................................ 35

SolutionPack for Cisco MDS 37

Overview....................................................................................................... 38Technical specifications................................................................................ 38Performing pre-configuration tasks................................................................39

Known issue with user-defined roles................................................ 39Configuring switches for SNMPv1 and SNMPv2c............................................39Configuring switches for SNMPv3.................................................................. 40Configuring Cisco switches for alert consolidation.........................................41Installing the SolutionPack............................................................................41Enabling passive host discovery through Generic-SNMP................................42Enable and edit customized zone naming patterns........................................43Limitations....................................................................................................43

SolutionPack for Cisco UCS 45

Overview....................................................................................................... 46Technical specifications................................................................................ 46Configuring the UCS Manager........................................................................47Installing the SolutionPack............................................................................47Importing the new database schema.............................................................49

SolutionPack for Converged Infrastructure 51

Figures

Tables

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

EMC ViPR SRM 3.6.2 SolutionPack Installation Guide 3

Overview....................................................................................................... 52Technical specifications................................................................................ 52Preparing Converged Infrastructure............................................................... 53Installing the SolutionPack............................................................................53

SolutionPack for EMC Atmos 55

Overview....................................................................................................... 56Technical specifications................................................................................ 56Installing the SolutionPack............................................................................57Limitations....................................................................................................58

SolutionPack for EMC Centera 59

Overview....................................................................................................... 60Technical specifications................................................................................ 60Preparing EMC Centera for discovery and data collection...............................61Installing the SolutionPack............................................................................61Limitations....................................................................................................62

SolutionPack for EMC Data Domain 63

Overview....................................................................................................... 64Technical specifications................................................................................ 64Preparing EMC Data Domain for discovery and data collection.......................64Installing the SolutionPack ...........................................................................65Discover the SNMP Collector......................................................................... 66

SolutionPack for EMC Data Protection Advisor 67

Overview....................................................................................................... 68Technical specifications................................................................................ 68Installing the SolutionPack............................................................................69Troubleshooting alert collection errors.......................................................... 70Troubleshooting report generation errors...................................................... 70

SolutionPack for EMC Host Interface 73

Overview....................................................................................................... 74Technical specifications................................................................................ 74Installing the SolutionPack............................................................................75

SolutionPack for EMC Isilon 77

Overview....................................................................................................... 78Technical specifications................................................................................ 78Installing the SolutionPack............................................................................79Updating SolutionPack alert definitions........................................................ 80Limitations....................................................................................................81

SolutionPack for EMC M&R Health 83


Chapter 6

Chapter 7

Chapter 8

Chapter 9

Chapter 10

Chapter 11

Chapter 12

CONTENTS


SolutionPack for EMC Recoverpoint 87


SolutionPack for EMC ViPR 91

Overview....................................................................................................... 92Technical specifications................................................................................ 92Installing the SolutionPack............................................................................92Updating the SolutionPack............................................................................94

SolutionPack for EMC VMAX 97

Overview....................................................................................................... 98Technical specifications................................................................................ 98Configuring the access credentials................................................................ 99Preparing EMC VMAX for discovery and data collection ...............................100

Solutions Enabler proxy scenario .................................................. 101Local Solutions Enabler scenario....................................................103Configuring VMAX arrays for consolidation of availability alerts......104

Installing the SolutionPack..........................................................................105Updating SolutionPack alert definitions...................................................... 107Configuring Solutions Enabler client access for VMAX................................. 108

Configuring host access................................................................. 108Adding client hosts to existing SYMAUTH configuration..................109Enabling client authorization..........................................................110Validating Symmetrix access controls............................................ 110Limitation: some alerts not displayed.............................................111

SolutionPack for EMC VNX 113

Overview..................................................................................................... 114Technical Specifications..............................................................................114Preparing your VNX for discovery and data collection.................................. 115

Configuring simple authentication................................................. 115Unisphere security file authentication............................................ 116Configuring VNX arrays for file storage discovery............................ 116

Installing the SolutionPack..........................................................................117Updating SolutionPack alert definitions...................................................... 119Limitations..................................................................................................119

SolutionPack for EMC VPLEX 121

Overview..................................................................................................... 122Technical specifications.............................................................................. 122Installing the SolutionPack..........................................................................123Limitations..................................................................................................125

SolutionPack for EMC ScaleIO 127

Overview..................................................................................................... 128Technical Specifications..............................................................................128Installing the SolutionPack for EMC ScaleIO................................................ 129

Chapter 13

Chapter 14

Chapter 15

Chapter 16

Chapter 17

Chapter 18

CONTENTS


SolutionPack for EMC XtremIO 131

Overview..................................................................................................... 132Technical specifications.............................................................................. 132Installing the SolutionPack..........................................................................133

SolutionPack for Hitachi Device Manager 135

Overview..................................................................................................... 136Technical specifications.............................................................................. 136Preparing Hitachi Device Manager for discovery and data collection............137Installing the SolutionPack..........................................................................137Operational Issues...................................................................................... 139

SolutionPack for HP 3PAR Storeserv 141

Overview..................................................................................................... 142Technical Specifications..............................................................................142Preparing your system for discovery and data collection..............................143Installing the SolutionPack..........................................................................143

SolutionPack for HP EVA 145

Overview..................................................................................................... 146Technical Specifications..............................................................................146Preparing your HP EVA system for discovery and data collection..................147Installing the SolutionPack..........................................................................147

SolutionPack for HP Storageworks XP 149

Overview..................................................................................................... 150Technical Specifications..............................................................................150Installing the SolutionPack..........................................................................151

SolutionPack for IBM DS 155

Overview..................................................................................................... 156Technical Specifications..............................................................................156Preparing your IBM DS system for discovery and data collection..................157Installing the SolutionPack..........................................................................157

SolutionPack for IBM LPARS 159

Overview..................................................................................................... 160Technical Specifications..............................................................................160Configuring VIO for discovery...................................................................... 161

Configuring sudo for VIO Server and VIO Client host discovery........161Configuring PowerBroker for VIO Server and VIO Client discovery... 163Generating a public and private key pair........................................ 164Importing a private key into the Collector ...................................... 165

Verify adapter IDs in NPIV configuration...................................................... 165Installing the SolutionPack..........................................................................166Using Discovery Center to discover the VIO Servers and Clients................... 167Using Discovery Center to discover an HMC................................................. 167SolutionPack Reconfiguration..................................................................... 168

Chapter 19

Chapter 20

Chapter 21

Chapter 22

Chapter 23

Chapter 24

Chapter 25

CONTENTS


SolutionPack for IBM SAN Volume Controller/Storwize 169

Overview..................................................................................................... 170Technical Specifications..............................................................................170Preparing for discovery and data collection................................................. 171Installing the SolutionPack..........................................................................171Limitations..................................................................................................173

SolutionPack for IBM XIV 175

Overview..................................................................................................... 176Technical Specifications..............................................................................176Preparing your IBM XIV system for discovery and data collection................. 177Installing the SolutionPack..........................................................................177Limitations..................................................................................................178Known problems ........................................................................................ 179

SolutionPack for Microsoft Hyper-V 181

Overview..................................................................................................... 182Technical specifications.............................................................................. 182Configuring credentials for SolutionPack for Microsoft Hyper-V....................183Requirements for data collection.................................................................183Installing the SolutionPack..........................................................................183Using a test script to query WMI objects...................................................... 184

SolutionPack for Microsoft SQL Server 185

Overview..................................................................................................... 186Technical Specifications..............................................................................186Where to find the latest SolutionPack software............................................187Installing the SolutionPack..........................................................................187Confirming report creation...........................................................................188Troubleshooting ......................................................................................... 188

What to do if data does not appear in reports.................................188Running a scheduled task to import data into reports.....................189Viewing collector errors in the Collector-Manager log files.............. 190

SolutionPack for NetApp Filer 191

Overview..................................................................................................... 192Technical specifications.............................................................................. 192Configuring access credentials....................................................................193Preparing NetApp Filer for discovery and data collection..............................193Installing the SolutionPack..........................................................................193Supported use cases and limitations.......................................................... 195

SolutionPack for Oracle Database 197

Overview..................................................................................................... 198Technical specifications.............................................................................. 198Installing SolutionPack................................................................................199Configuring the SolutionPack with an unprivileged account.........................200

SolutionPack for Oracle MySQL Database 201

Chapter 26

Chapter 27

Chapter 28

Chapter 29

Chapter 30

Chapter 31

Chapter 32

CONTENTS


Overview..................................................................................................... 202Technical Specifications..............................................................................202Where to find the latest SolutionPack software............................................202Installing the SolutionPack .........................................................................203Confirming report creation...........................................................................203Troubleshooting ......................................................................................... 204

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

SolutionPack for Physical Hosts 207

Overview..................................................................................................... 208Technical Specifications..............................................................................208Preparing your hosts for discovery and data collection................................ 209

Guidelines for hostnames and IP addresses...................................209Guidelines for SNIA libraries and HBA drivers................................. 209Windows host configuration for discovery and data collection........209Unix host configuration for discovery and data collection...............221Configuring ESX hosts to collect PowerPath metrics....................... 226Configuring hosts to collect PowerPath metrics.............................. 226

Installing the SolutionPack..........................................................................227Adding hosts as part of groups in Discovery Center..................................... 228SolutionPack reconfiguration...................................................................... 229Limitations..................................................................................................230

SolutionPack for Storage Compliance 231

Overview..................................................................................................... 232Technical specifications.............................................................................. 232Where to find the latest SolutionPack software............................................233Installing the SolutionPack..........................................................................233

SolutionPack for VI VirtualWisdom 235

Overview..................................................................................................... 236Technical specifications.............................................................................. 236Preparing VI VirtualWisdom.........................................................................237

Connecting to multiple VirtualWisdom Portal Servers..................... 237Installing the SolutionPack..........................................................................238

SolutionPack for VMware vCenter 241

Overview..................................................................................................... 242Technical specifications.............................................................................. 242Configuring the SolutionPack to collect Powerpath data.............................. 242Installing this SolutionPack.........................................................................243Post-install requirements............................................................................ 245Limitations..................................................................................................246

Troubleshooting 247

Confirming report creation...........................................................................248Troubleshooting ......................................................................................... 248

What to do if data does not appear in any reports.......................... 248

Chapter 33

Chapter 34

Chapter 35

Chapter 36

Chapter 37

CONTENTS


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

CONTENTS


CONTENTS


SolutionPack for Brocade FC Switch .............................................................................. 30SolutionPack for Cisco MDS/Nexus................................................................................38SolutionPack for Cisco UCS............................................................................................46SolutionPack for Converged Infrastructure..................................................................... 52SolutionPack for EMC Atmos..........................................................................................56SolutionPack for EMC Centera........................................................................................60SolutionPack for EMC Data Domain................................................................................64SolutionPack for EMC Data Protection Advisor............................................................... 68SolutionPack for EMC Host Interface.............................................................................. 74SolutionPack for EMC Isilon........................................................................................... 78SolutionPack for EMC M&R Health................................................................................. 84SolutionPack for EMC RecoverPoint............................................................................... 88SolutionPack for EMC ViPR.............................................................................................92SolutionPack for EMC VMAX...........................................................................................98SolutionPack for EMC VNX........................................................................................... 114SolutionPack for EMC VPLEX........................................................................................ 122SolutionPack for EMC ScaleIO......................................................................................128SolutionPack for XtremIO.............................................................................................132SolutionPack for Hitachi Device Manager.....................................................................136SolutionPack for HP 3PAR StorServ.............................................................................. 142SolutionPack for HP EVA.............................................................................................. 146SolutionPack for HP StorageWorks P9000....................................................................150SolutionPack for IBM DS.............................................................................................. 156SolutionPack for IBM LPAR...........................................................................................160Sample sudoers file for Linux OS................................................................................. 163SolutionPack for IBM SAN Volume Controller/Storwize................................................ 170SolutionPack for IBM XIV............................................................................................. 176SolutionPack for Microsoft Hyper-V..............................................................................182SolutionPack for NetApp Filer...................................................................................... 192SolutionPack for Oracle Database................................................................................198SolutionPack for Physical Hosts...................................................................................208Verify that the host is ready for discovery with HTTP.....................................................215Set Negotiate authtype................................................................................................ 216Verify that the host is ready for discovery with HTTPS...................................................216Set Negotiate authtype................................................................................................ 217Set non-admin user..................................................................................................... 217Sample sudoers file for Linux OS................................................................................. 223SolutionPack for Storage Compliance.......................................................................... 232SolutionPack for VI VirtualWisdom...............................................................................236SolutionPack for VMware vCenter................................................................................ 242

12345678910111213141516171819202122232425262728293031323334353637383940

FIGURES


FIGURES


ViPR SRM and SolutionPack privilege levels...................................................................21Sample zone naming patterns....................................................................................... 36Sample output of show snmp user command................................................................ 41Sample zone naming patterns....................................................................................... 43Known problems..........................................................................................................179Supported use cases and limitations...........................................................................195Allowed discovery types.............................................................................................. 211Host Configuration utility command options................................................................ 214

12345678

TABLES


TABLES


CHAPTER 1

Getting started

l What are SolutionPacks?.......................................................................................16l Licenses................................................................................................................17l Browse and install.................................................................................................17l Reconfigure an installed SolutionPack...................................................................19l Update SolutionPacks........................................................................................... 21l Where to find the latest SolutionPack software......................................................21l ViPR SRM and SolutionPack privileges...................................................................21

Getting started 15

What are SolutionPacks?Understand the role of SolutionPacks in the ViPR SRM product and gain a high-levelunderstanding of how they are licensed, installed, reconfigured, and updated.

A SolutionPack is an installable application that provides data collection and reportingcapabilities for specific entities in your infrastructure. The SolutionPacks support EMCstorage systems along with many common third-party storage infrastructure components.

The SolutionPacks provide asset-specific support to an enterprise installation. Yourorganization purchases licenses to provide visibility into only those assets that exist inits installed infrastructure.

With a new installation, most SolutionPacks are initially available for you to try for 30days using a trial license. You can obtain a permanent license that enables any numberand combination of available SolutionPacks in your environment.

After a SolutionPack is installed, its reports are available in the Report Library node in theUser Interface report tree. Here are some possible nodes in the Report Library. Eachasset-specific node contains many pre-defined reports to support that asset type.

ViPR SRM discovers and collects data on hosts, hypervisors, and switches, as well asEMC and third-party storage devices. Global dashboards and reports roll up data from theSolutionPacks into holistic views and reports such as end-to-end topology views, pathdetails, capacity reports, and explore views. Global dashboards and reports include datafor EMC VMAX, VNX, VNXe3200, CLARiiON, Celerra, VPLEX, XtremIO, HDS, IBM XIV, HPStorageWorks P9000, and NetApp storage. ViPR SRM offers support for hosts,

Getting started


hypervisors, switches, and arrays using SolutionPacks that provide in-depth reporting forthe individual objects. Most of the available SolutionPack data is rolled up into the globalreports and dashboards, although not all are included. As EMC normalizes theSolutionPack data, EMC will continue to add data from those SolutionPacks to the globalreports and dashboard views.

LicensesYou must have a license to install SolutionPacks.

With the installation of ViPR SRM, all SolutionPacks are initially available for you to try for30 days using a trial license.

A permanent license can enable any number and combination of SolutionPacks for anenvironment.

To add SolutionPacks to an initial license, see your EMC Account representative. They canhelp issue temporary licenses for evaluation purposes or set up the sale of additionalSolutionPacks. New entitlements are added to the existing license. To obtain the updatedlicense, download it from the license portal.

Browse and installYou can browse SolutionPacks before installing them to learn more about what each onemonitors and the kinds of reports and dashboards that it provides.

Procedure

1. To browse SolutionPacks:

a. Log in to the Console and click Administration in the banner.

b. Click Centralized Management in the navigation tree (the left pane).

c. Click SOLUTIONPACK CENTER in the menu area at the top of the page.

A list of available SolutionPacks appears.

Getting started

Licenses 17

d. Click a SolutionPack name.

A page opens describing the SolutionPack and its reports. Notice the install buttonat the bottom of the page.

2. To prepare to install a new SolutionPack:

a. Make sure that you have a license.

b. Obtain the Summary Sheet for the SolutionPack from the EMC Community page at https://community.emc.com/.

Each Summary Sheet describes installation and configuration steps for integratinga particular SolutionPack into an installed ViPR SRM environment.

Getting started


https://community.emc.com/community/products/vipr

3. To install a new SolutionPack:

a. Navigate to the SolutionPack page as described in Step 1.

b. Click Install on the description page to start the installation.

c. Continue by following instructions in the Summary Sheet.

Reconfigure an installed SolutionPackYou can change the configuration options that are initially set during a SolutionPackinstallation.

To reconfigure a SolutionPack:

Procedure

1. Log in to the Console and click Administration in the banner.

2. Click Centralized Management in the navigation tree (the left pane).

A new browser tab opens.

3. Click SolutionPacks in the new navigation tree.

A list of installed SolutionPacks appears.

4. Click or select a SolutionPack name that you want to reconfigure.

A summary description of the SolutionPack opens, including a list of configuredcomponents associated with that SolutionPack.

Getting started

Reconfigure an installed SolutionPack 19

5. Click Edit (the pencil icon) next to a component to access its configuration screen.

6. Change any of the settings on the resulting screen.

7. Click Reconfigure, and then Ok.

Results

The SolutionPack is reconfigured to use the new settings.

Getting started


Update SolutionPacksYou can configure ViPR SRM to automatically download updates and enhancements toSolutionPacks.

The Online Update feature helps you to quickly take advantage of new capabilities asthey are provided in each SolutionPack. You can configure, enable, and disableautomatic downloads of SolutionPack updates. You can also see currently availabledownloads and download history.

To access the Online Update feature:

Procedure

1. Log in to the Console, and click Administration in the banner.

2. Click Centralized Management in the navigation tree (the left pane).

3. Click CONFIGURATION > ONLINE UPDATE in the banner.

4. For more information, see the ViPR SRM article "Automate the Download of Updates."

Where to find the latest SolutionPack softwareInstall the latest core software update for your product suite. SolutionPacks distributedwith core software have a 30-day free evaluation period. If you plan to use the softwarelonger 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 forupgraded installations. If you upgrade the core software and want to try a newSolutionPack, you must request a license for that SolutionPack by completing a SupportRequest (SR) form, which is available on the EMC Online Support website at http://support.emc.com.

ViPR SRM and SolutionPack privilegesThe following table provides the privilege levels that are required to install and operateSolutionPacks.

Table 1 ViPR SRM and SolutionPack privilege levels

SolutionPack Privilege level

SolutionPack for Brocade FC Switch SMI-S:

Getting started

Update SolutionPacks 21

http://support.emc.com


Table 1 ViPR SRM and SolutionPack privilege levels (continued)


l For SMI-S, any user having SAN System administratorprivileges and having access to all Fabrics.

SNMP:

l For SNMP v1/v2c, configure SNMP community string.

l For SNMP v3, configure an SNMP v3 user name.

SolutionPack for Cisco MDS/Nexus For SNMP v1/v2c, configure SNMP community string.

For SNMP v3, configure an SNMP v3 user name.

SolutionPack for Cisco UCS “Role-read-only” role is sufficient for the SolutionPack towork properly. We recommend to create a new dedicated“service account” for SolutionPack integration.

SolutionPack for ConvergedInfrastructure

Log in to UIM (using UIM credentials) from withinWatch4Net. The credentials will be re-used in the form ofa Ticket Granting Ticket (CAS TGT) until it expires. Thisexpiration interval is configurable on the UIM server bythe administrator. The default duration period is 2 hours.

One instance of UIM/P and one instance of UIM/O shouldbe used as a set. Add UIM/P to UIM/O as a data source.

If you use UIM’s default Self Signed SSL Certificates, thenthey must be installed or added to the exception in thebrowsers prior to using this Solution Pack. Otherwise, youcannot view reports from UIM.

SolutionPack for EMC Atmos Atmos System Management Console

l SysAdmin Level

l TenantAdmin on each Tenant that the user wants tocollect data.

Atmos Cloud Delivery Platform

l Admin level access to management nodes.

l Admin level access to authentication nodes.

SolutionPack for EMC Centera The minimum profile privileges needed for data collectionare:

l The only required roles are "Accesscontrol" and"Monitor".

l The "Granted Rights" only need to be set to "read" (r).

The installation of the Centera collection services on aWindows host requires Administrator privileges. But thereis a workaround described in KnowledgeBase article188584 that will allow the post-install running of theseservices as a non-Administrator user.

Getting started




SolutionPack for EMC Data Domain No user authentication required. ViPR SRM will extract thedata using SNMP "V2C" with the community string as"Public."

SolutionPack for EMC Data ProtectionAdvisor

DPA user needs a custom role with Manage ScheduledReports privileges enabled on DPA server.Enabling the Manage Scheduled Reports will also enableRun reports and View existing scheduled reports andschedules. These privileges are sufficient for the DPASolutionPack to pull data from DPA server.

SolutionPack for EMC Host Interface Privileges are controlled by the configuration of the hostagent. No special privileges are required for a host to bediscovered.

SolutionPack for EMC Isilon Collection will work with root/admin users who haveadministrative privileges. Collection also works for a non-admin user that is a member of the AuditAdmin role. Thisrole has mostly READ ONLY privileges.

SolutionPack for EMC RecoverPoint Under technical review.

SolutionPack for EMC VMAX For ViPR SRM to collect all masking views whenSymmetrix Access Control (symacl) is enabled, theSolutions Enabler host must be added to an AccessGroup which has Access Type "BASE" and "VLOGIX" to alldevices.

For ViPR SRM to collect all masking views whenSymmetrix Authorization (symauth) is enabled the userperforming the collection only needs the Monitor role.

IMPORTANT: symauth "Monitor" role only works toretrieve all masking views with latest Solutions Enabler7.6.2.25 (hotfix 1843/service alert 1708). Older versionsof Solutions Enabler 7.6.2 (ex. 7.6.2.8 which wasrequired in ViPR SRM 3.5 release) required "StorageAdmin" or "Admin" role in order to retrieve all maskingviews.

Windows-based collector host running VMAX SolutionPack and using "remote" SYMAPI Server:

l The Windows "System" account runs the Collectorservice which performs the VMAX collection

l The Windows "System" account therefore executesthe SYMCLI commands to get the masking view.

l In order for symauth to retrieve all masking views thecollector hosts's "System" user account must at leasthave the "Monitor" role authorized. Again, thisassumes Solutions Enabler 7.6.2.25 or higher isinstalled

Getting started

ViPR SRM and SolutionPack privileges 23



l Otherwise if an older 7.6.2 Solutions Enabler isinstalled then "Storage Admin" or "Admin" role wouldbe required.

Linux-based collector host running VMAX SolutionPack:

l The "apg" user account runs the Collector servicewhich performs the VMAX collection

l The "apg" user therefore executes the SYMCLIcommands to get the masking views

l In order for symauth to retrieve all masking views theSRM ViPR Linux collector hosts's "apg" user accountmust at least have the "Monitor" role authorized.Again, this assumes Solutions Enabler 7.6.2.25 orhigher is installed

l Otherwise, if an older 7.6.2 Solutions Enabler isinstalled, then "Storage Admin" or "Admin" rolewould be required.

SolutionPack for EMC VNX VNX Block -- User with Operator role or higher. NOTE: Ifthe user only has the Operator role and you run the status"Test" from Discovery Center, the "statistics logging" testwill always fail. To confirm Statistics Logging is enabled,you should login to Unisphere as a user withAdministrator privileges. Once Statistics Logging isenabled, the Operartor user will be able to collectperformance data from the array.

VNX File -- A local user for file with Operator role or higher.The "CLI access allowed" check box must be checked.

SolutionPack for EMC ViPR Set the following roles in the Virtual Data Center

l System Monitor - Retrieves metering and monitoringrecords for the Virtual Data Center.

l System Auditor - Retrieves audit logs for the VirtualData Center.

SolutionPack for EMC VPLEX Use the management CLI and the Linux shell account tonavigate on the management station. The service accountthat is used by default is both a Linux account and a CLIaccount.

From the perspective of the management CLI, the serviceuser is not read-only, because you can perform someprovisioning operations on the VPLEX, although it doesnot have full administrative capabilities.

From the perspective of the Linux shell, the serviceaccount is a regular user account so you cannot dooperations that require root privilege.

For a non-service account, follow these additional stepsonce the user has been created. This is assuming the

Getting started




SolutionPack is already installed using the serviceaccount. If it is being installed for the first time with anon-service user, you do not need this procedure.

1. Change the permission to the virt-volumes folder withfollowing command: chmod g+w virt-volumes // run under /var/log/Vplex/cli/w4

2. Reconfigure the VPLEX SolutionPack with thealternate account

SolutionPack for EMC M&R Health N/A

SolutionPack for EMC XtremIO Non-admin account with read-only privileges.

SolutionPack for Hitachi DeviceManager

Non-privileged account with rights to view all.

SolutionPack for HP 3PAR StoreServ Non-privileged account with rights to view all.

SolutionPack for HP EVA Admin rights are required.

SolutionPack for HP StorageWorksP9000

Non-privileged account with rights to view all.

SolutionPack for IBM DS Under technical review.

SolutionPack for IBM LPAR HMC credentials

l User role or Operator (recommended), or HMC Viewer(minimum).

l Refer to table 4 at http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=%2Fipha1%2Fhmctasksanduserroles.htm

VIO server

l SUDO user role with elevated (root) privileges toexecute commands to be run on the VIOS host.

l Note: The padmin role is not required for VIO Servers.

VIO Client/LPAR

l SUDO user role (or)

l SSH Keys (or)

l root user (optional)

SolutionPack for IBM SAN VolumeController/Storwize

All the performance, topology and capacity metrics aresupported for a user who is a member of "Administrator","SecurityAdmin" or "Monitor" user group. Performancedata such as CPU usage, Port traffic statistics of non-configuration nodes are not supported for a user who ismember of "Service" or CopyOperator" user group.

SolutionPack for IBM XIV Discovery works with Read Only, Storage Administrator,Application Administrator access.

Getting started


http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=%2Fipha1%2Fhmctasksanduserroles.htm





Read Only is the minimum required.

Note

Due to limitations with the IBM software, discovery usingthe LDAP users will not happen if there is no active IBMXIV GUI user session, either by the corresponding LDAPuser or a stroage administrator.

SolutionPack for Microsoft Hyper-V Admin rights are required in order to run unsignedPowerShell scripts.In order to do this, you must run the following commandas an administrative user:

PowerShell -C Set-ExecutionPolicyUnrestrictedOn Microsoft Windows Server 2008 R2 and MicrosoftWindows Server 2012 Hyper-V hosts, the domainadministrative user must use be member of domaingroup Domain Admins. In other words, is not enough tomake a domain user member of local groupAdministrators in Hyper-V hosts.

On Microsoft Windows Server 2008 R2 and MicrosoftWindows Server 2012 Hyper-V hosts, the WMI queries canbe performed only using the build-in Administrator localuser. Any other local administrative local user will beunable to perform the queries because the UAC controls.

On Microsoft Hyper-V Server 2012 and Microsoft WindowsServer 2012 Hyper-V hosts, is possible to collect datausing a non-administrative local or domain user. Thisuser must be member of local groups Hyper-VAdministrators and Performance Log Users groups.Unfortunately, this will not possible in Microsoft Hyper-VServer 2008 R2 and Microsoft Windows Server 2008 R2.

SolutionPack for Microsoft SQL Server l SQL authentication requires that the user be amember of the SYSADMIN group

l Windows user account requires the user be amember of the Guests group or the Domain Guestsgroup

l The default database must be the master

l Windows user account must be imported into theMicrosoft SQL Server with settings similar to these:

n Server roles of public

n Securable grants for Connect SQL, View anydefinitions, and View server state

SolutionPack for NetApp Filer SSH connection to the 7-Mode NetApp devices with thefollowing role:

Getting started




l login-ssh, cli-stats*, cli-snap*, cli-aggr*, cli-vol*, cli-disk*, cli-nfs*, cli-cifs*, cli-df, cli-sysconfig, cli-ifconfig, cli-qtree, cli-quota, cli-storage, cli-maxfiles,cli-echo, cli-lun, cli-fcp

SSH connection to the C-Mode NetApp devices with thefollowing role:

l Access level 'readonly' for the commands : volume,df, lun, storage, statistics, network, vserver, cluster,sleep

l Access level 'all' for the commands: set, system

SolutionPack for Oracle Database The Watch4net collector must connect to each instance ofOracle databases and perform SQL queries. You can useeither an administrator equivalent system account, orcreate a dedicated system account for the collector. If youwant to use the last option, ask the DBA administrator torun the query described in the SolutionPack for Oraclearticle.

This will create a "watch4net" account, which specificgrant for the Watch4net collector.

SolutionPack for Physical Hosts Windows user privileges

l Domain user in the local administrator's group(recommended), or

l Local administrator for the host.

UNIX user privileges

l Sudo user with read/execute permissions forcommands, or

l SSH public/private key pair with execute permissionfor commands.

Refer to the SolutionPack for Physical Hosts article formore information.

SolutionPack for Storage Compliance(The compliance rules support all thesupported Hosts, ESX, VMs, HDS, IBMXIV, EMC arrays (VMAX and VNX), andBrocade and Cisco fabrics.)

N/A

SolutionPack for VI VirtualWisdom Windows Administrator privileges are required to installthe VI proxy software.

SolutionPack for VMware vCenter Discovery works with read-only non-admin user.

Getting started


Getting started


CHAPTER 2

SolutionPack for Brocade FC Switch

l Overview............................................................................................................... 30l Technical specifications........................................................................................ 30l Brocade switch and SMI agent configuration......................................................... 31l Installing the SolutionPack....................................................................................33l Passive host discovery configuration options........................................................ 35

SolutionPack for Brocade FC Switch 29

OverviewLearn how to install and configure the SolutionPack for Brocade FC Switch. TheSolutionPack for Brocade FC Switch accesses performance data information that wasautomatically collected and interpreted (using resource grouping and mathematicalcalculations) from across multiple fabrics.

Figure 1 SolutionPack for Brocade FC Switch

Alerts are consolidated from Brocade FC Switches and shown on the All Alerts Console.

Technical specifications

Data collection methods

Note

Choose one of the options below. Do not use both options simultaneously.

SMI-S OnlyDiscover switch topology, performance and zoning details through SMI-S.

SNMP + SMI-S (Zoning only through SMI-S)Discover switch topology and performance metrics through SNMP. SNMP does notsupport zoning discovery. Restrict SMI-S discovery to zoning details only.

Main reports

FC Switches SummaryOverviews the FC switches, including key indicators such as name, IP addresses,firmware version, and operational status.



# FC Ports with ErrorsReports the FC ports with errors, such as invalid CRCs, signal losses, or link failures.

Fabrics Overall HealthReports the current operational status of the switch.

Inventory & PerformanceReports Inter-Switch-Link (ISL) trunking resource usage. ISL monitoring helpsadministrators determine the sources of traffic on ISLs and identify potential pointsof congestion in the SAN fabric.

Throughput by Switches (/s)Reports the Throughput by switches. Typically, this is the sum of throughput for allFC ports belonging to a switch.

Throughput by Port Type (/s)Reports the Throughput by port type. Typically, this is the sum of throughput of all FCports of each port type on the switches.

Traffic by Domains (/s)Reports the Throughput by domains. Typically, this is the sum of throughput for allFC ports belonging to switches regarding the domain id.

Situation To WatchHighlights risk situations such as FC ports errors.

Virtual FabricsReports the virtual Fabrics configured on all switches available in the environment

Recommendations on using SolutionPack for Brocade FC SwitchThe recommended discovery approach is to use SMI-S only data collection (in both freshdeployment of ViPR SRM 3.6 and upgrade from previous versions to 3.6).SNMP + SMI-S (Zoning only through SMI-S) data collection is supported for backwardcompatibility with previous versions and will be deprecated in a future release.

Supported collection interfacesFor information about supported collection interfaces, refer to the ViPR SRM SupportMatrix.

Brocade switch and SMI agent configurationYou must configure Brocade switches and SMI agents for discovery and alertconsolidation in ViPR SRM.

l Configuring Brocade SMI Agents on page 31

l Configuring Brocade switches for alert consolidation on page 32

l Configuring Brocade Switches for SNMP on page 32

Configuring Brocade SMI AgentsInstall and configure Brocade SMI agent for complete switch discovery (if you chooseSMI-S Only discovery option) or zoning discovery only (if you choose the SNMP+SMI-Sdiscovery option).

Procedure

1. Install Brocade SMI agent in one of the following modes:


Brocade switch and SMI agent configuration 31

Installation mode Description

Integrated Brocade SMIAgent

The Brocade SMI agent is integrated with CMCNE, BNA,CMDCE, DCFM and gets installed when you install anyof these products.

Brocade SMI Agent only(headless installation)

Headless installation (silent mode installation) doesnot need a license and installs the SMI agent only.

Refer to the CMCNE/CMDCE installation guide for more details on installation andconfiguration of Brocade SMI agent.

Configuring Brocade switches for alert consolidationUse the snmpConfig command to forward SNMP v1 traps from Brocade switches toViPR SRM.

Trap-based alerts for Brocade switches are supported through SNMP regardless of thediscovery option you choose. In other words, even if you choose the SMI-S Only discoveryapproach, configure the switches for SNMP trap forwarding.

Use the snmpConfig command to forward SNMP v1 traps from Brocade switches to ViPRSRM.

Procedure

1. Log into the Brocade FC switch as the administrator.

2. Type snmpConfig ––set snmpv1 , and press Enter.

3. Type the following details, when prompted:

Option Input

Community [public]

Trap recipient's IP address The ViPR SRM trap recipient IP which, in a single vAppinstallation is the ViPR SRM IP, and in a distributedenvironment, is the Backend server's IP.

Trap recipient severitylevel

(0..5)

Trap recipient port 2041, which is the ViPR SRM trap listening port.

4. If you have multiple Brocade FC switches in your storage environment, repeat thisprocedure on each switch.

Configuring Brocade switches for SNMP

Brocade switches have to be configured with SNMP v1/v2c/v3 credentials if you chooseSNMP+SMI-S (zoning only through SMI-S) discovery option.

Procedure

1. Launch a command line interface for the Brocade switch and log in with Administratorcredentials.

2. Perform the following steps to configure the switch for SNMPv1/v2c:



a. Type snmpConfig --show snmpv1The community strings will be listed.

b. If you wish to change a community string, type snmpConfig --set snmpv1c. Enter the new community string and proceed.

3. Perform the following steps to configure the switch for SNMPv3:

a. Type snmpConfig --show snmpv3.

The configuration parameters will be listed.

b. If you wish to change the parameters, type snmpConfig --set snmpv3c. Enter the parameters and proceed.

4. Repeat these steps for each Brocade switch in your storage environment.

Installing the SolutionPack

Before you begin

l To discover the switch topology (switch details and switch port details) and switchperformance using SNMP and zoning details through SMIS, you must be aware ofSNMP v1/v2 community strings and SNMP ports, or SNMP v3 user details and privacyand authentication details for the v3 username. In addition, the username, password,port number, and SSL enabled/status for the SMI-S provider are required to discoverthe zoning details

l To discover the switch topology, switch performance, and zoning details throughSMIS, the username, password, port number, and SSL enabled/status for the SMI-Sprovider are required

l Managing Alert Consolidation explains how to configure alerts consolidation.

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 selectedautomatically.

9. Click Next.

The window displays a note about Alert Consolidation.

10.Click Next.

The window displays pre-configured alert details.

11.From the Alerting on data collection drop-down menu, select existing settings thathave been specified for other components, or select Add a new alerting datacollection.


Installing the SolutionPack 33

http://community.emc.com/docs/DOC-36206

If you select Add a new alerting on data collection, choose an alerting web-serviceinstance.

12.Click Next.

The window displays data collection details.

13.From the Data collection drop-down menu, select existing settings that have beenspecified for other components, or select Add a new data collection.

If you select Add a new data collection, type information about the data collection. InHostname or IP address to send data to, use localhost on port 2020, which is theCollector host where the Load Balancer Connector is installed.

14.Leave Enable Topology Backend on data collected checked.

15.From the Topology Service drop-down menu, select existing settings that have beenspecified for other components, or select Add a new Topology Service.

If you select Add a new Topology service, provide information about the topologyservice and the web service. In Topology Service hostname or IP address, specify thePrimary Backend.

From the Web-Service Gateway drop-down menu, select existing settings that havebeen specified for other components, or select Add new gateway. If you select Addnew gateway, provide information about the web-service gateway where the topologyservice resides.

16.From the Frontend Web service drop-down menu, select existing settings that havebeen 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 FrontendWeb service.

17.(For SRM 3.5.1 and higher) From the SMI-S Discovery Configuration option drop-downmenu, select existing settings that have been specified for other components, or adda new configuration. If desired, select Restrict SMI-S to zoning discovery only.

If the option is selected, SMI-S will be used to discover zoning details only. Ifunselected, SMI-S will be used to discover switch and zoning details completely.

18.From the Passive Host Discovery Specific Configuration drop-down menu, selectexisting settings that have been specified for other components, or add a newconfiguration. If desired, select Enable Passive Host Discovery.

See Passive host discovery configuration options on page 35 for additional details.

19.Optionally, select Configure advanced settings to configure polling settings.

20.Click Next.

The window displays reports settings.

21.In Administration Web-Service Instance, select an existing instance or create acustom instance.

22.Click Next.

The window displays a note about SNMP masks.

23.Click Install.

24.Click Ok when the installation is complete.

25.Click Discovery Center > Devices Management.

26.Click Brocade SMI Provider.



27.Click Add new device.

28.Specify the details of the Brocade SMI Provider configuration.

a. In the Device location section, select the server and instance where you want tostore the configuration details for this device.

b. In the SMI Provider IP Address or Host Name field, type the Brocade SMI Providerhost.

c. Enter the access credentials.

d. If desired, select Enable Secure Connection (SSL).

e. Type the port number. The default ports are 5988 for non-SSL and 5989 for SSL.

29.Click Test to validate the credentials.

30.Click OK.

31.Click Save.

Passive host discovery configuration optionsEnable passive host discovery to see end-to-end topology from hosts to arrays, andidentify chargeback on SAN enabled hosts without active host discovery.

You can passively resolve hosts, discovered through the SolutionPack for Brocade FCSwitch, from zoning records.The default zone naming patterns in ViPR SRM are:

z_%h%

z_%h%_*

z_%h%_*_*

%h%_*

After you have enabled passive host discovery, there are two options for passive hostconfiguration.

l Enable DNS Resolution: This option, which is enabled by default, resolves the "IP"property by using the DNS lookup handler. You can un-check this option to avoidusing the DNS lookup feature.

l Customize zone naming patterns: This option allows you to customize the zonenaming pattern. By default, this option is disabled, and ViPR SRM uses the fourdefault zone naming patterns. You can enable this option to add, delete, or modifythe default zone naming patterns and host name positions in zones.

You can enable passive host discovery while installing the SolutionPack, or you canenable it by reconfiguring the SMI Data Collection component of an existing instance ofthe SolutionPack.

To enable and add/edit customized zone naming patterns:

Procedure

1. Select the Enable Passive Host Discovery checkbox.

2. Select the Customized zone naming patterns checkbox.

The system displays the four default zone naming templates.

3. Click the Add button (plus icon) to view the zone naming pattern and host position fora template. Edit the pattern or position if desired.

Only Java-based zone naming patterns are supported.


Passive host discovery configuration options 35

Only plain numbers can be used for the position. Special characters (like $) are notrequired.

Table 2 Sample zone naming patterns

Regex is ^(z_)([A-Z0-9a-z]+)$and hostname position is 2

Matches all the zone names that start with 'z_' and extracts thehostname from the rest of the string that follows 'z_'Example: For zone name z_lingz099, the hostname extracted islingz099.

Regex is ^([^z_][A-Z0-9a-z]+)_([A-Za-z0-9]+) andhostname position is 1

Matches all the zone names that doesn't start with 'z_' andextracts the hostname from zone name that is before the firstunderscore.Example: For lgloe111_1106, the hostname extracted islgloe111.

For more information on writing Java's regular expression refer to http://docs.oracle.com/javase/tutorial/essential/regex/



CHAPTER 3

SolutionPack for Cisco MDS

l Overview............................................................................................................... 38l Technical specifications........................................................................................ 38l Performing pre-configuration tasks........................................................................39l Configuring switches for SNMPv1 and SNMPv2c....................................................39l Configuring switches for SNMPv3.......................................................................... 40l Configuring Cisco switches for alert consolidation.................................................41l Installing the SolutionPack....................................................................................41l Enabling passive host discovery through Generic-SNMP........................................42l Enable and edit customized zone naming patterns................................................43l Limitations............................................................................................................43

SolutionPack for Cisco MDS 37

OverviewLearn how to install and configure SolutionPack for Cisco MDS/Nexus. The SolutionPackfor Cisco MDS/Nexus accesses performance data that was automatically collected andinterpreted (using resource grouping and mathematical calculations) across multipleMDS/Nexus fabrics.

Alerts are consolidated from Cisco MDS/Nexus Switches and shown on the All AlertsConsole.

Figure 2 SolutionPack for Cisco MDS/Nexus


Data collection methodsAccesses performance data information that was automatically collected and interpreted(using resource grouping and mathematical calculations) from across multiple fabrics.Uses SNMP to collect fabric information.

Main reports

Port UtilizationReport over Fibre channel ports and Port-Channel.

VSANVSAN utilization and relationship.

Overall ThroughputThe sum of throughput of all the interfaces of each switch

Switch PerformanceReport on the utilization, reachability, and uptime of the switch

Name ServerName Server Database information.

Environmental elementsPower Supply, temperature sensors.




Performing pre-configuration tasksBefore you discover a Cisco switch in ViPR SRM you need to perform the following checks.

All switches in the Cisco fabric must have SNMP credentials for use with ViPR SRM. Forexample, if SNMPv1/v2c is used, all Cisco switches in the fabric should have theSNMPv1/v2c community name set with a role of network-admin or network-operator. Forexample, if SNMPv3 is used, all Cisco switches in the fabric should have the SNMPv3user set with the role of network-admin or network-operator.

Procedure

1. Ensure all hardware and software is listed as supported in the EMC ViPR SRM SupportMatrix.

2. Verify the TCP/IP connectivity to the switches to be discovered. Test by issuing a pingcommand to these switches.

3. Determine if SNMP traps are enabled. Log in to the switch and run the command showsnmp trap.

4. Run the command snmp-server enable traps to enable SNMP traps.

SWDevCisco8-9216i# config terminalEnter configuration commands, one per line. End with CNTL/Z.

SWDevCisco8-9216i (config)# snmp-server enable traps5. Display the traps that are enabled. Execute the show snmp trap command. The values

in the Enabled column should be Yes.

Known issue with user-defined roles

If an SNMPv3 user or SNMPv1/v2c community string used for switch discovery isassigned to a role that has VSAN policy set to deny, there is a possibility of switch rebootand supervisor fail-over.

This is due to an issue in Cisco NX-OS 5.2(6) through 6.2(x).

The workaround is to execute the following commands in sequence:

linbge197#config tlinbge197#role name <name of the role>linbge197#no vsan policy denylinbge197#copy run startlinbge197#exit

Configuring switches for SNMPv1 and SNMPv2cYou have to configure Cisco switches for SNMPv1 or SNMPv2c to enable switch discovery,and alert consolidation for the switches. The SNMPv1 or SNMPv2c information youprovide when performing discovery is necessary for ViPR SRM to contact the switch toobtain information.

Before you begin

If SNMPv1/v2c is used, all Cisco switches in the fabric should have the SNMPv1/v2ccommunity name set with a role of network-admin/network-operator.


Performing pre-configuration tasks 39

ViPR SRM collects data from the switch using the SNMP community name. It uses theSNMP port for communication. The default port set is port 161.

Note

The Cisco documentation provides information on configuring Cisco switches for SNMPv1and SNMPv2c management.

Procedure

1. Log into the switch as an administrator.

2. To configure the snmp-server community string with read-only privileges, run thefollowing commands:

Cisco8-9216i# config terminalCisco8-9216i(config)# snmp-server community srmuser roEnter configuration commands, one per line.

3. To verify if the SNMPv1 community string exists, run the command show snmpcommunity.

A sample output of the command:

Community Group/Access

srmuser network-operator

Configuring switches for SNMPv3You have to configure Cisco switches for SNMPv3 to enable discovery and alertconsolidation for the switches. The SNMPv3 information you provide when performingdiscovery is necessary for ViPR SRM to contact the switch to obtain information.

ViPR SRM collects data from the switch using SNMPv3 secure credentials. ViPR SRMsupports SNMPv3 with all the combinations of Auth (MD5, SHA) and Priv (AES, DES,NONE).

Note

Create the SNMPv3 users with authentication and privacy passwords on all physicalswitches in the fabric. The Cisco documentation provides information on creatingSNMPv3 users on Cisco switches.

This procedure provides an example of creating an SNMPv3 user called srmuser with anetwork-operator role, SHA authorization, and AES128 authentication.

Procedure

1. Log into the switch as an administrator.

Cisco8-9216i# config terminalEnter configuration commands, one per line.

2. Run the snmp-server user commands as follows:

snmp-server user srmuser network-operator auth sha <SHA-password> priv aes-128 <AES-password>



3. To verify the new user creation run the command show snmp user.

Table 3 Sample output of show snmp user command

SNMP USERS

User Auth Priv(enforce) Groups

admin md5 no network-admin

srmuser sha aes-128(no) network-operator

NOTIFICATION TARGET USERS (configured for sending V3 Inform)

User Auth Priv

SWDevCisco8-9216i#

Configuring Cisco switches for alert consolidationUse the snmp-server command to forward SNMP v1 alert traps from Cisco FC switchesto ViPR SRM.

Procedure

1. Log into the Cisco FC switch as the administrator.

2. Type # config, and press Enter.

3. Type snmp-server host <trap recipient IP> traps <SNMP trap version><Community String> udp-port <trap listening port >, and press Enter.

In the command syntax:

Syntax element Input

<trap recipient IP> In a single vApp installation, this is the ViPR SRM IP, and in adistributed environment, is the Backend server's IP.

<SNMP trap version> version 1

<Community String> public

<trap listening port > 2041, which is the ViPR SRM trap listening port.

Example: snmp-server host 10.247.24.190 traps version 1 public udp-port 2041

4. If you have multiple Cisco FC switches in your storage environment, repeat thisprocedure on each switch.


Before you begin

l ViPR SRM core modules must be up-to-date in all servers because not all moduledependencies are validated during the SolutionPack installation or update process.


Configuring Cisco switches for alert consolidation 41


Procedure






6. Click Install.




9. Click Next.


10.Click Next.



If you select Add a new alerting on data collection, type information about the alertingconfiguration. In Alerting Backend hostname or IP address, specify the PrimaryBackend host.

12.Click Next.



14.Click Next.

The window displays a note about SNMP masks.

15.Click Install.


Enabling passive host discovery through Generic-SNMPIf you cannot access the active host, you cannot use active host discovery. In this case,you must enable passive host discovery if you want to see end-to-end topology fromhosts to array and identify chargeback on SAN enabled hosts.

To enable passive host discovery through the SolutionPack for Cisco MDS/Nexus, edit theGeneric-SNMP independent SolutionPack block instance, select the Enable Passive HostDiscovery checkbox, and click Reconfigure.

The default zone naming patterns supported in SolutionPack for Cisco MDS/Nexus are:

l z_%h%

l z_%h%_*




l z_%h%_*_*l %h%_*

After you have enabled passive host discovery, there are two options for passive hostconfiguration:

Enable DNS ResolutionThis option, which is enabled by default, resolves the "IP" property by using the DNSlookup handler. You can un-check this option to avoid using the DNS lookup feature.

Customize zone naming patternsThis option allows you to customize the zone naming pattern. By default, this optionis disabled, and ViPR SRM uses the four default zone naming patterns. You canenable this option to add, delete, or modify the default zone naming patterns andhost positions in zones.

Enable and edit customized zone naming patternsProcedure

1. Select the Enable Passive Host Discovery checkbox.

2. Select the Customized zone naming patterns checkbox.

The system displays the four default zone naming templates.

3. Click the Add button (plus icon) to view the zone naming pattern and host position fora template. Edit the pattern or position if desired.

Only Java-based zone naming patterns are supported.

Only plain numbers can be used for the position. Special characters (like $) shouldnot be prefixed.

Table 4 Sample zone naming patterns

Regex is ^(z_)([A-Z0-9a-z]+)$and hostname position is 2

Matches all the zone names that start with 'z_' and extracts thehostname from that matches the rest of the string that follows'z_'Example: For zone name z_lingz099, the hostname extracted islingz099.

Regex is ^([^z_][A-Z0-9a-z]+)_([A-Za-z0-9]+) andhostname position is 1

Matches all the zone names that doesn't start with 'z_' andextracts the hostname from zone name that is before the firstunderscore.Example: For lgloe111_1106, the hostname extracted islgloe111.

For more information on writing Java's regular expression refer to http://docs.oracle.com/javase/tutorial/essential/regex/

LimitationsMaintenance operations that cause a large number of changes in the SAN environment,such as zoning changes and migrations, might degrade APG database performance.These operations generate new active metrics to represent the new SAN environment,and previous metrics become inactive. If active plus inactive metrics exceed 1.5 millionentries, slower performance of the database is expected. If needed, you can clean the


Enable and edit customized zone naming patterns 43

database to remove inactive metrics, or split the database if active metrics are greaterthan 1.5 million entries.



CHAPTER 4

SolutionPack for Cisco UCS

l Overview............................................................................................................... 46l Technical specifications........................................................................................ 46l Configuring the UCS Manager................................................................................47l Installing the SolutionPack....................................................................................47l Importing the new database schema.....................................................................49

SolutionPack for Cisco UCS 45

OverviewLearn how to install and configure the SolutionPack for Cisco UCS. The SolutionPack forCisco UCS generates reports that encompass compute, network, and storage accesscomponents of the unified fabric.

The SolutionPack generates uptime reports for the UCS Managers and enables you to seeinto the solution as managed by the unified management domain. In addition, theSolutionPack for Cisco UCS obtains real-time and historical data through various reportsthat indicate events and faults in the system.

Figure 3 SolutionPack for Cisco UCS


Data collection methodsUCS XML API

Main reportsPower Consumption over Time

Fabric Interconnects

Chassis

System Statistics, Fans, PSU, Interfaces

Events




Configuring the UCS ManagerEnable XML API for the Cisco UCS Manager.

Before you begin

Procedure

1. Log in to the Cisco UCS Manager web console.

2. Navigate to Admin > Communication Management > Communication Services.

3. Verify that the HTTP & CIM XML services are enabled.

If the Redirect HTTP to HTTPS option is enabled, you will need to use securecommunication when configuring your SolutionPack block.

4. If you want to use secure communications between the collector and the UCSManager:

l Choose the secure communication option when adding the UCS Manager.

l Configure HTTPS on the Communication Services page of UCS Manager.

After you finish

EMC recommends that you create a new dedicated service account for SolutionPackintegration. Role-read-only role is sufficient for the SolutionPack to work properly.


Before you begin

ViPR SRM core modules must be up-to-date in all servers because not all moduledependencies are validated during the SolutionPack installation or update process.

Procedure






6. Click Install.




9. Click Next.




Configuring the UCS Manager 47


11.Click Next.






14.Select the Enable events collection checkbox.

15.In the Event server hostname or IP address field, select the Backend host where theevents server runs. The default port is 52007.

16.In the Even server port number field, enter a port number for events collection.

17.Select Configure advanced settings to configure polling settings.

18.Click Next.

The window displays event settings.

19.Select an Event database. If you select Add a new Events database, type informationfor the new events database. Type the database information for the events databasethat runs on the Primary Backend host. The default Database port is 53306. Thedefault Event server port number is 52007.

20.Click Next.



22.Click Install.



25.Click Cisco UCS.


27.Specify the details of the Cisco UCS configuration.

a. In the Device location section, select the server and instance where you want tostore the configuration details for this device.

b. In the UCS type field, select UCS Manager (Blade Chassis) or UCS C-Series (Server).

c. In Hostname or IP address type the UCS management host.

d. In the Username and Password fields, type the credentials for the managementserver.

e. Select Enable secure connection, if desired.



f. In the Communication port field, type the port number for the management server.


29.Click OK.

30.Click Save.

After you finish

If you want to discover the Cisco UCS Fabric Interconnects in your environment via SNMP,you must install the Cisco MDS /Nexus SolutionPack in your environment to provide fullSNMP masks and capabilities for the SNMP discovery.

Importing the new database schema

Before you begin

Starting with Watch4net 6.2u4, schema are preloaded. If you installed from an earlierversion, import the new database schema.

Procedure

1. Load the events block file Event-Processing/Generic-Live-Writer/cisco-ucs/ddl/my-ucs_live.sql.

2. Run mysql-client.sh (mysql-client.cmd on Windows).

3. Type username, database name, and password.

4. Copy the contents of the /my-ucs_live.sql file and paste it into the mysql clientat the mysql> prompt.

This creates the ucs_live table.

5. Start the event processing manager service.

6. To enable events reporting from the frontend:

a. Edit the Web-Application configuration file Web-Servers/Tomcat/Default/conf/Catalina/localhost/APG.xml.

b. If the cisco-ucs-events section is present, uncomment it.

c. If the cisco-ucs-events section is missing, add the following lines:

 <ResourceLink name="jdbc/FLOW-UCS-LIVE:{ mapping=FLOW-UCS.xml, table=ucs_live }" global="jdbc/FLOW-EVENTS" type="javax.sql.DataSource" />

7. Restart the tomcat service.


Importing the new database schema 49



CHAPTER 5

SolutionPack for Converged Infrastructure

l Overview............................................................................................................... 52l Technical specifications........................................................................................ 52l Preparing Converged Infrastructure....................................................................... 53l Installing the SolutionPack....................................................................................53

SolutionPack for Converged Infrastructure 51

OverviewLearn how to install and configure the SolutionPack for Converged Infrastructure. TheSolutionPack for Converged Infrastructure generates reports for hardware systemsummary, available capacity, hardware systems capacity by location, logical poolcapacity by type, and total capacity by service quality.

In addition, the SolutionPack obtains a topology view of the underlying system or serviceas discovered by the Unified Infrastructure Manager (UIM) view.

Figure 4 SolutionPack for Converged Infrastructure


Data collection methodsThe XML collector is the only collector used to collect the data. Client must have UnitedInfrastructure Manager/Provisioning (UIM/P) and Unified Infrastructure Manager/Operations (UIM/O) virtual appliances installed in his environment with appropriateconnectivity before deploying the SolutionPack for Converged Infrastructure.

Main reportsVblock/VSPEX Inventory

UIM Dashboard

Topology




Preparing Converged InfrastructureIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for Converged Infrastructure.

ViPR SRM communicates with Unified Infrastructure Manager using credentials withaccess to the UIM host.

Procedure

1. Identify the user account credentials used to access the UIM host.

2. Record this information for use when you install the SolutionPack.


Before you begin


Procedure






6. Click Install.




9. Click Next.

The windows displays topology collector details.



11.Leave Enable alerting on data collected checked.



13.In the UIM/P hostname or IP address field, type the UIM/P host.


Preparing Converged Infrastructure 53

14.In the Username and Password fields, type the required credentials for the UIM/Phost.

15.In the UIM/O hostname or IP address field, type the UIM/P host.

16.In the Username and Password fields, type the required credentials for the UIM/Ohost.

17.Select Use advanced settings to configure polling settings.

18.Click Next.


19.From the Web-Service Gateway drop-down menu, select existing settings that havebeen specified for other components, or select Add a new Web-Service Gateway.

If you select Add a new Web-Service Gateway, type information about the web-servicegateway.


21.Click Install.




CHAPTER 6

SolutionPack for EMC Atmos

l Overview............................................................................................................... 56l Technical specifications........................................................................................ 56l Installing the SolutionPack....................................................................................57l Limitations............................................................................................................58

SolutionPack for EMC Atmos 55

OverviewLearn how to install and configure the SolutionPack for EMC Atmos. The SolutionPackaccesses system summary reports for Resource Management Groups (RMGs), as well asfor the nodes being monitored within the RMGs. In addition, SolutionPack generatesreports summarizing key storage parameters for the entire Atmos multi-tenant system.

Figure 5 SolutionPack for EMC Atmos

Technical specificationsData collection methodsThe XML data collector is used to collect time series data. There are two sources of data:the Atmos System Management API and the Atmos Cloud Delivery Platform (ACDP).

Event Data from Atmos can be received using SNMP Traps. The M&R EPM server and theSNMP agent need to be configured in Atmos to send traps. Alternatively, the traps can besent to the SMARTS platform and the data can be populated using Smarts Listener.

Main reportsSystem Dashboard

RMG Dashboard

Tenant Summary

SubTenant Summary

Top-N Reports





Before you begin

l EMC ViPR SRM core modules must be up-to-date in all servers because not all moduledependencies are validated during the SolutionPack installation or update process.

l Data imported in the 2.0 version of this SolutionPack will not be compatible with the1.0 version of SolutionPack for EMC Atmos. Data continuity with previously importeddata will be broken.

Procedure






6. Click Install.




9. Click Next.







13.Make a selection in the EMC Atmos field. If you select Add a new EMC Atmos, enterthe Atmos configuration settings.

14.Configure polling settings.

15.Click Next.



17.Click Install.




LimitationsThe Atmos SMI interface reports capacity based on the storage available for objectcreation, while ViPR SRM reports combined object storage capacity along with thecapacity used to store the object's metadata. Therefore the ViPR SRM number will behigher than the number reported by the Atmos SMI console, the difference being thecapacity dedicated to metadata storage.



CHAPTER 7

SolutionPack for EMC Centera

l Overview............................................................................................................... 60l Technical specifications........................................................................................ 60l Preparing EMC Centera for discovery and data collection.......................................61l Installing the SolutionPack....................................................................................61l Limitations............................................................................................................62

SolutionPack for EMC Centera 59

OverviewLearn how to install and configure the SolutionPack for EMC Centera. The SolutionPackaccesses the inventory of the Centera storage system and generates reports on usagecapacity for pools and nodes, pool file counts, and c-clip counts.

Figure 6 SolutionPack for EMC Centera

Technical specificationsSupported systemsCentera Viewer CLI (v4.3)

Data collection methodsCLI

Main reportsCentera Cluster Summary

Pool usage details

Node detail

Utilization




Preparing EMC Centera for discovery and data collection

To enable discovery and data collection for EMC Centera, install a supported version ofCentera CLI software on the ViPR SRM Collector host.

Procedure

1. Identify the ViPR SRM Collector host where you will install the EMC Centera Viewer CLIsoftware.

2. Install a supported version of the EMC Centera Viewer CLI on the Collector host.

The EMC Centera Viewer CLI is currently supported on Microsoft Windows Server 2008R2 and Linux SLES11 SP3. EMC ViPR SRM Support Matrix provides the specific versionof Centera CLI software required and supported Collector host operating systems.

3. Identify the username (with monitor role enabled) and password.

4. Record this information. You need it to install the SolutionPack.

Results

As you install the SolutionPack for EMC Centera, the installation program will prompt youto provide the location of the CenteraViewer.jar file.


Before you begin

l Ensure that EMC Centera CLI is installed and configured on the Collector host. EMCCentera CLI is available on EMC Support Center (emc.support.com).

Note

Centera Collector-Manager is supported on Microsoft Windows Server 2008 R2 andLinux SLES11 SP3.

l Do a package synchronization after you register the Windows VM with the base vApp.From Centralized Management, click Package Management and thenSynchronization. Check retrieve the lastest package and click Ok.

l ViPR SRM core modules must be up-to-date in all servers because only some moduledependencies are validated during the SolutionPack installation or update process.

Procedure






6. Click Install.





Preparing EMC Centera for discovery and data collection 61

9. Click Next.




11.Leave Activate the FailOver-Filter checked.

12.Select an item in the EMC Centera specific configuration field. If you select Add a newEMC Centera specific configuration:

a. Provide Centera configuration information.

b. In the Path to the Centera Viewer jar file (CenteraViewer.jar) field, type the path tothe .jar file you configured as described in Preparing EMC Centera for discoveryand data collection on page 61.

c. Configure polling settings.

13.Click Next.



15.Click Install.


LimitationsIf a Centera system does not have its serial number configured, it will be reported in aseparate table. If there are two or more systems that do not have their serial numberconfigured, the Capacity information will be incorrect.



CHAPTER 8

SolutionPack for EMC Data Domain

l Overview............................................................................................................... 64l Technical specifications........................................................................................ 64l Preparing EMC Data Domain for discovery and data collection...............................64l Installing the SolutionPack ...................................................................................65l Discover the SNMP Collector................................................................................. 66

SolutionPack for EMC Data Domain 63

OverviewLearn how to install and configure the SolutionPack for EMC Data Domain. TheSolutionPack generates real-time and historical reports and accesses file system,compression, replication, and chassis inventory status details to gain insight into themanagement of a EMC Data Domain system.

Figure 7 SolutionPack for EMC Data Domain

Technical specificationsData collection methodSNMP

Main reportsOverview

File Systems

Compression

Replication


Preparing EMC Data Domain for discovery and data collectionEnable a supported version of SNMP on any Data Domain systems that you want ViPRSRM to poll.

The ViPR SRM Collector host communicates with EMC Data Domain using SNMP.



Note

For details on the supported versions of SNMP used with Data Domain, refer to the EMCViPR SRM Support Matrix.

Procedure

1. On the Data Domain system, use the following command to view the SNMPconfiguration: # snmp show config

2. Use the following command to add the ViPR SRM SNMP Collector host: # snmp addro-community public hosts collector_host


Before you begin

l Data Domain must be configured to allow the EMC M&R collector host tocommunicate to it via SNMP.

n Use the following command on the Data Domain system to view the SNMPconfiguration: # snmp show config

n Use the following command to add the EMC M&R host: # snmp add ro-community <public> hosts <emc m&r.collector.com> where<public> is the read-only community string


Procedure

1. Log in.






7. Click Install.




10.Click Next.







13.Click Next.

14.Click Install.


Discover the SNMP CollectorProcedure

1. Log in to EMC M&R.

Use http://<localhost>:58080/device-discovery/.

2. Go to Collector > New Collector.

This option collects configuration data from the SNMP Collector.

3. Click Save.

4. The Collector is listed with orange color in the STATE column.

5. Click Check reachability of the x selected collector(s) to verify that the collector isreachable, and if it is, click Send configurations to the x selected collector(s).

The Collector is listed with green color in STATE.

6. Select Devices and click New Device.

7. Fill in the details for the new device on all tabs.

8. Click Save.

If the STATE column is green for the device, no error occurred. If an error occurred,mouseover the STATE column for the device to display the error.

9. If STATE is green, click Execute Action. This will discover the device with thecapabilities that are selected.

10.Go to the Dashboard and send the configurations.

11.Go to the device and check that the Collector is listed.

After you finish

If all steps are successful, device details begin to appear in the ViPR SRM User Interface.

If you encounter any problems, use the Events Log to begin troubleshooting. For example,the log might point to problems with SNMP communications or configuration settings. Toopen the log, scroll to the bottom of the Device Discovery pane (http://<localhost>:58080/device-discovery/#/devices) and click Show EventsLog.



CHAPTER 9

SolutionPack for EMC Data Protection Advisor

l Overview............................................................................................................... 68l Technical specifications........................................................................................ 68l Installing the SolutionPack....................................................................................69l Troubleshooting alert collection errors.................................................................. 70l Troubleshooting report generation errors...............................................................70

SolutionPack for EMC Data Protection Advisor 67

OverviewLearn how to install and configure the SolutionPack for EMC Data Protection Advisor. ThisSolutionPack enables users to generate real-time and historical reports on replicationtechnologies, EMC Data Domain backup-to-disk platform, backup technologies forSymantec Netbackup, and EMC Avamar supported by Data Protection Advisor.

Figure 8 SolutionPack for EMC Data Protection Advisor

Technical specificationsData collection methodsXML Collector for Data Domain and RecoverPoint

Stream Collector using REST APIs for Netbackup and Avamar

Main reportsReplication: RPO Compliance, Alerts, Capacity

EMC Data Domain: Configuration, Performance, Replication

EMC Avamar: Inventory, BackupSummary, RestoreSummary

Symantec NetBackup: Inventory, BackupSummary, RestoreSummary





Before you begin


Procedure






6. Click Install.




9. Click Next.


10.Click Next.




12.From the Alert Consolidation drop-down menu, select existing settings that have beenspecified for other components, or select Add a new Alert consolidation.

If you select Add a new Alert consolidation, type information about the alertconfiguration. In Alerting HostName or IP address, use localhost on port 2020,which is the Collector host where the Load Balancer Connector is installed.

13.Select the backup technologies to monitor.

If you do not select any of these options, there will be no DPA reports to collect. If youselect all of these options, data will be collected for all DPA reports.

14.Select Do you want to configure advanced settings and enable Number of collectingthreads, if required.

15.Click Next.


16.Click Install.





19.Click EMC Data Protection Advisor.


21.In DPA appliance Host name or IP, type the host information for the DPA appliance.

22.Provide the access credentials for the DPA appliance.

23.Provide the protocol and DPA server port.


25.Click Ok.

26.Click Save.

DPA requires specific licenses to monitor replication technologies, backuptechnologies, and Data Domain. These licenses must be installed on DPA for ViPRSRM to monitor these technologies.

DPA reports may take up to one hour to populate. Some of the performance data/graphs take two collection cycles for the graphs to be plotted.

After installing the SolutionPack for EMC Data Protection Advisor, there may bescheduling related errors in the collector logs.

Troubleshooting alert collection errorsReconfigure the data collection options in the SolutionPack for EMC Data ProtectionAdvisor if alert collection is not occurring. This procedure applies to each DPA instancefor which alert collection is not occurring.

Procedure



3. Click Storage > EMC Data Protection Advisor .

4. Within the Instance column, click on the edit icon to reconfigure the options for theaffected DPAinstance that is affected by the problem.

5. Select the Enable alert collection from DPA.

6. Click Reconfigure.

Troubleshooting report generation errorsReconfigure the data collection options in the SolutionPack for EMC Data ProtectionAdvisor if reports are not being generated. This procedure applies to each DPA instancefor which reports are not being generated.

Procedure




4. Click EMC Data Protection Advisor.

5. Within the Instance column, click on the edit icon to reconfigure the Data Collectioncomponent.

6. Enable Do you want to configure advanced settings.



7. Select the technology you want to collect data from.



Troubleshooting report generation errors 71



CHAPTER 10

SolutionPack for EMC Host Interface

l Overview............................................................................................................... 74l Technical specifications........................................................................................ 74l Installing the SolutionPack....................................................................................75

SolutionPack for EMC Host Interface 73

OverviewLearn how to install and configure the SolutionPack for EMC Host Interface. ThisSolutionPack discovers physical servers through the EMC Host Interface, and provides aglobal view of hosts in a data center.

The SolutionPack provides the ability to drill down on host topology, capacity utilization,and performance measurements on hosts. In addition, the SolutionPack reports hostcapacity by summarizing storage LUNs mapped on host file systems and provides adetailed report on storage capacity.

Note

This SolutionPack does not contain reports. You should install the reports from theSolutionPack for Physical Hosts.

Figure 9 SolutionPack for EMC Host Interface


PrerequisitesInstall the EMC Host Interface as described in Install and Manage EMC Host InterfaceSoftware.

Main reportsHost Enterprise Dashboard

Host information and details

File systems summary report

Local and remote disk capacity reports

Service level for LUNs mapped to host file systems

Performance metrics such as CPU, memory, and disks for host devices





Note

The SolutionPack for EMC Host Interface supports alerts and uses the same alertingcomponent as the SolutionPack for Physical Hosts. To configure alerts for theSolutionPack for EMC Host Interface, install the alerting block from the SolutionPack forPhysical Hosts.

Procedure






6. Click Install.




9. Click Next.








13.Click Do you want to configure advanced settings to configure polling settings,specify the number of collecting threads, and specify the time to wait for data to bereceived.

14.Click Install.





17.Click Host Agent (EHI).

These steps describe how to add hosts individually. For information about usingdiscovery groups to use the same credentials to discover multiple hosts, refer to the"Adding new devices" topic in the online help.


19.Select the server and collector instance where you want to store the configurationdetails for this device, and then enter the hostname or IP address of the host, supplythe login credentials, and specify the appropriate configuration settings.


21.Click OK.

22.Click Save.



CHAPTER 11

SolutionPack for EMC Isilon

l Overview............................................................................................................... 78l Technical specifications........................................................................................ 78l Installing the SolutionPack....................................................................................79l Updating SolutionPack alert definitions................................................................ 80l Limitations............................................................................................................81

SolutionPack for EMC Isilon 77

OverviewLearn how to install and configure the SolutionPack for EMC Isilon. The SolutionPack forEMC Isilon optimizes service availability for the EMC Isilon scale-out NAS storage solutionand displays the data in easy-to-use reports within ViPR SRM.

This SolutionPack enables you to see and understand performance and utilization acrossEMC Isilon devices in real-time, to know which node is the bottleneck in a cluster, whatthe peak/busy hours are, and more.

Figure 10 SolutionPack for EMC Isilon

Technical specificationsMain reports

All cluster sizesHDD Free, HDD Used, SSD Free, SSD Used capacities for all clusters

Clusters CPU Usage (%)Average CPU utilization per cluster

Clusters ThroughputInbound and outbound file system throughput across all clusters

Cluster SizeHDD Free, HDD Used, SSD Free, SSD Used capacities

Cluster ThroughputInbound and outbound filesystem throughput

CPU Usage (%)Average CPU utilization

Connected Connection per Protocol/NodeMaximum connected connections for CIFS, FTP, HDFS, HTTP, iSCSI, NFS, PAPI, SIQ



Active Connection per Protocol/NodeMaximum active connections for CIFS, FTP, HDFS, HTTP, iSCSI, NFS, PAPI, SIQ

Node Pools & TiersFree, Used, Size, Time to full, Will reach 90% on, and Utilization for pools and tiers

OneFSFree, Used, Size, and Utilization (%)

Node DetailsNode Size, Node Throughput, Node CPU Usage (%), File Systems, Bays, Interfaces

Shares# NFS export, # CIFS share counts

More reportsSnapshot Summary, Quota Usage, Protocols performance


Installing the SolutionPackProcedure






6. Click Install.




9. Click Next.


10.Click Next.


11.Click Next.










15.In Alert Consolidation server hostname or IP address, enter the Primary Backend host.

16.In Alert Consolidation server port number, enter the port used for alert consolidation.

17.Select Use advanced settings to configure polling and alert settings.

18.Click Next.


19.Click Install.



22.Click EMC Isilon.


24.In the Cluster hostname or IP address field, type the hostname or IP address of theSmartConnect service, or of any node in the cluster.

25.Type the username (default is admin).

26.Type the password.


28.Click Ok.

29.Click Save.

Updating SolutionPack alert definitionsWhen you update a SolutionPack, any modified alert definitions supported in theupdated 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 > <SolutionPackName> definitions.

2. Highlight <SolutionPack Name> definitions, and click the Export icon to create abackup 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 > <SolutionPackName> in the tree.

5. In the table, click the Reconfigure icon in the Pre-configured alerts row.


7. In the Alerting Frontend, navigate to Local Manager > Alert definitions > <SolutionPackName> definitions to see the updated alert definitions.



LimitationsIsilon RestAPI has a limitation that it cannot get StoragePool information for OneFS 7.0.So the Isilon SolutionPack cannot show any StoragePool information on OneFS 7.0.StoragePool information is only available for OneFS 7.1 and above.


Limitations 81



CHAPTER 12

SolutionPack for EMC M&R Health


SolutionPack for EMC M&R Health 83

OverviewLearn how to install and configure the SolutionPack for EMC M&R Health. ThisSolutionPack monitors the health of your EMC M&R infrastructure. Take advantage of thisno-charge SolutionPack to keep the EMC M&R services performing optimally, so you haveinstant access to performance data and reports when you need it.

Figure 11 SolutionPack for EMC M&R Health

Technical specificationsSupported systemsEMC M&R 6.4 and later

Data collection methodsJMX

Main reportsModules Performance

Collecting Level Performance

Backend & Databases events and utilization

Server summary




Installing the SolutionPackInstall this SolutionPack on all core software hosts in your environment.

Before you begin


Procedure






6. Click Install.




9. Click Next.


10.Click Next.







14.Click Next.


15.Click Install.

16.Click Ok once installation is complete.

Performance data will displayed in about an hour.The following message might appear in the collection log during operation: WARNING-- [2014-04-25 05:26:38 EDT] -- f::a(): JVM IO ERROR 'No such process'. ID: '17032',NAME: 'lib/module-manager.jar exit'. You can ignore this message.





CHAPTER 13

SolutionPack for EMC Recoverpoint


SolutionPack for EMC Recoverpoint 87

OverviewLearn how to install and configure the SolutionPack for EMC RecoverPoint. TheSolutionPack for EMC RecoverPoint enables users to generate real-time and historicalreports on the performance of the mechanisms that replicate data from any supportedSAN-based arrays to other SAN-based arrays.

Summary reports for key components--such as RecoverPoint Appliance (RPA), Clusters,and Consistency Group Metrics, as well as I/O throughput analysis for SAN systemtraffic--provide a deeper understanding of replication schemes and the policies thatgovern them.Figure 12 SolutionPack for EMC RecoverPoint


System Traffic SANGlobal traffic view of the SAN

System Traffic Site-to-SiteGlobal traffic view between sites

RecoverPoint SummaryProvides key information about the RecoverPoint systems including information onClusters, Consistency Groups and Splitters




Installing the SolutionPackBefore you begin


l Ensure that the RecoverPoint appliance is reachable and that you can execute RESTAPI commands from the Collector host. The ports used by RecoverPoint and theCollector host should be unblocked.

Procedure






6. Click Install.




9. Click Next.







13.From the EMC RecoverPoint specific configuration drop-down, select Add a new EMCRecoverPoint specific configuration.

14.Type the RecoverPoint FQDN hostname, and type its username and password.


16.Click Next.







19.Click Install.




CHAPTER 14

SolutionPack for EMC ViPR

l Overview............................................................................................................... 92l Technical specifications........................................................................................ 92l Installing the SolutionPack....................................................................................92l Updating the SolutionPack....................................................................................94

SolutionPack for EMC ViPR 91

OverviewLearn how to install and configure the SolutionPack for EMC ViPR. The SolutionPackprovides a global view via the dashboard of the underlying EMC ViPR Controllerinfrastructure. It provides dashboard information to your tenant using the built-in multi-tenancy functionality of the EMC M&R portal.

Figure 13 SolutionPack for EMC ViPR

Technical specificationsMain reportsSummary Dashboard

Virtual Array Capacity

Virtual Pool Utilization

Utilization by Tenant/Project

ViPR Events






l Deploy the vApp as described in the article on installing ViPR SRM as a virtualappliance.

l You need to know the connection details for the instance of ViPR from which you wantto collect data. This includes:

n Virtual IPv4 address of the ViPR Controller

n Credentials for a ViPR account with the System Administrator role (ECS only),System Monitor, and System Auditor Role

n The core software and license must already be installed.

l The SolutionPack for EMC ViPR SolutionPack license must be uploaded.

l You need to know the frontend hostname and admin credentials for the core softwareinstance to which you are adding the SolutionPack.

Procedure






6. Click Install.




9. Click Next.


10.Click Next.















17.In Event server hostname or IP address, enter the Primary Backend host.

18.In Event server port number, enter the port for the Primary Backend host. The defaultport is 22000.

19.If ViPR is connected to an EMC ECS storage system, select Collect ViPR Data Fabric(*some features require additional SRM licenses).


21.Click Next.





24.Click Install.



27.Click ViPR.


29.From Server, select the ViPR Collector.

30.From Instance, select the ViPR instance.

31.Enter the public virtual IPv4 address and credentials for an account with the SystemAdministrator role for the ViPR Controller server from which you want to collect data.


33.Click Ok.

34.Click Save.

Discover ECS and HW nodes using the SolutionPack for Physical Hosts and private keyauthentication.

Updating the SolutionPackProcedure

1. After core modules are updated and the SolutionPack is ready for update, upload thelicense for ECS Add-on for EMC ViPR SolutionPack.



2. Update the SolutionPack blocks.

In case the SolutionPack is updated before uploading the license for ECS Add-on, youcan upload the license after SolutionPack update and then reconfigure the datacollection block of the SolutionPack for EMC ViPR.


Updating the SolutionPack 95



CHAPTER 15

SolutionPack for EMC VMAX

l Overview............................................................................................................... 98l Technical specifications........................................................................................ 98l Configuring the access credentials........................................................................ 99l Preparing EMC VMAX for discovery and data collection .......................................100l Installing the SolutionPack..................................................................................105l Updating SolutionPack alert definitions.............................................................. 107l Configuring Solutions Enabler client access for VMAX......................................... 108

SolutionPack for EMC VMAX 97

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

Figure 14 SolutionPack for EMC VMAX


Storage Pool Capacity PlanningTrending and forecasting capacity for all arrays and pools, giving expected capacitybased on trend

Thin DevicesTrending and forecasting capacity for all Thin Devices, giving bound devices capacityand the total Thin Devices consumed

TiersTrending and forecasting capacity for all arrays and tiers, giving expected capacitybased on trend

All disksTable listing information from all of the disks, including it's array, name, type, groupRPM, director, IOPS, throughput and capacity

By DiskGroupTable listing information from all of the disk groups, including it's array, disk groupname, director, raw capacity, hyper capacity, free capacity and usage percentage



Masking views SummaryCapacity as seen by hosts in the masking view

Pool CapacityCapacity information for all of the Pools available, including array, pool name, poolstate and capacity used

Configured UsableTrending and forecasting on the sum of all thick devices (including standard, BCVand R1 devices) plus the sum of all data devices (pool storage)

Hot SparesTrending and forecasting on the sum of disks dedicated as hot spares

RAID overheadReport on the array capacity used to support RAID protection overhead

UnconfiguredReport on all thick devices plus the sum of all data devices (pool storage)

Array IDOverview of all VMAX main components, physical and logical

ArraysLists all the VMAX systems

DisksLists all disks and related key information, for all arrays

DirectorsLists all directors and related key information, for all arrays

PortsLists all ports and status for all arrays

PoolsLists all pools and related key information, for all array.

Storage GroupsLists all Storage Groups and related key information

PortsLists all ports and status for all arrays

DevicesLists all devices and related key information, for all arrays

Storage Groups SummaryPerformance and capacity of all storage groups for this array, including IO Densityand Response Time

FE|BE|RDF DirectorsKey performance metrics for all directors and ports


Configuring the access credentialsM&R uses different accounts when running SolutionPacks.

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


Configuring the access credentials 99

l Username - no default SMI-S Provider Username is provided during the deployment ofSolutionPack for EMC VMAX but the EMC SMI-S Provider out-of-the-box username isadmin

l Password - no default SMI-S Provider Password is provided during the deployment ofSolutionPack for EMC VMAX but the EMC SMI-S Provider out-of-the-box password is#1Password

VMAX Performance collection via Unisphere for VMAX:

l Username - the default is smcl Password - the default is smc

Preparing EMC VMAX for discovery and data collectionIdentify the information required to support data collection before installing theSolutionPack for EMC VMAX and perform the necessary pre-configuration.

ViPR SRM requires EMC Solutions Enabler to collect array topology details for VMAXarrays (VMAX3 arrays use SMI-S, not Solutions Enabler); optionally ViPR SRM requiresUnisphere 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 thesame host. There are two supported scenarios for topology collection. The SolutionsEnabler proxy scenario is recommended because the Collector and the Solutions Enablerare not competing for host resources.

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

Solutions Enabler proxy scenario (recommended)In this scenario, you install Solutions Enabler on the ViPR SRM Collector host designatedto collect data from VMAX.

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

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

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

VMAX3 discovery scenarioVMAX3 discovery uses SMI-S Provider for collecting topology and Unisphere for VMAX forperformance details. Installing SMI-S and Unisphere for VMAX locally on a ViPR SRMappliance will cause the Collector, Solutions Enabler, and Unisphere for VMAX tocompete for host resources. Because of this, it is highly recommended that you use proxymode. In proxy mode, SMI-S (along with SE) will be installed on a host connected toarrays to be discovered. The SMI-S connectivity to an array can be tested using theTestSmiProvider utility, as shown below. When using the utility, accept the defaultanswers 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/emcrepeat 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 SRMCollector Appliance via Discovery Center using the Test button.

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

l Implementing the Local Solutions Enabler scenario includes the advantages ofreduced network calls and a more secure configuration. However, the Collectorsoftware will require additional Solutions Enabler host CPU and memory resources.

l The Solutions Enabler (proxy) scenario is the preferred configuration since theCollector and Solutions Enabler are not competing for host resources.

l The Local Solutions Enabler scenario requires that each VMAX array have at least 6Gatekeeper Devices be created on the host.

Note

If the Solutions Enabler was installed to a Virtual Machine then Raw Device Mappingsmust used when creating the Gatekeeper Devices

l If the Local Solutions Enabler is desired and if VMAX LUN Performance details arerequired, then it is recommended that you install the EMC SMI-S Provider kit on yourhost since it includes the required Solutions Enabler components. This is in contrastto installing a standalone Solutions Enabler kit and then installing the SMI-S Providerover it which could potentially cause incompatibility issues if the Solutions Enablerversions are different. Refer to EMC SMI-S Provider documentation for installationdetails.

Solutions Enabler proxy scenarioThe Solutions Enabler proxy scenario supports resource discovery and data collection forEMC VMAX.

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

l Client host - You install Solutions Enabler on the ViPR SRM Collector host designatedto collect data from VMAX. The client host has no direct connectivity to the array.

l Server host - Solutions Enabler already exists on the SYMAPI server with connectivityand gatekeeper access to the array.


Solutions Enabler proxy scenario 101

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 devicesto your SYMAPI server.

Configuring Solutions Enabler proxy supportConfigure support for the Solutions Enabler proxy scenario.

Before you begin

l 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.

l In a proxy configuration, you must maintain the same Solutions Enabler familyversion. A mixed 32-bit and 64-bit Solution Enabler is supported in a proxyconfiguration.

l Map two additional gatekeeper devices for ViPR SRM and present them to yourSYMAPI server.

l Ensure the storsrvd daemon is running on the Server host. You can confirm this byissuing the stordaemon list command on the Server host.

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

Procedure

1. On the client host on which you installed Solutions Enabler, navigate to the netcnfgfile.

On Linux, the file is located at: /var/symapi/config/netcnfg.

On Windows the file is located at: ..\Program Files\EMC\SYMAPI\config2. 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 thedeamons_options file in the SECURITY_LEVEL section.

3. Set the following System environment variables on the client host:

l SYMCLI_CONNECT=<SYMAPI_SERVER>l SYMCLI_CONNECT_TYPE=REMOTE

Option Description

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



Option Description

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

Linux Use the env command to show the environment variables.

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

4. On the SYMAPI server host, ensure that the SERVER license key is registered byreviewing the symapi\config\symapi_licenses.dat file. If it is not there, usethe symlmf utility to add the license key.

You can also control the Solutions Enabler licenses from the array.

Verifying the Solutions Enabler proxy configurationVerify proxy configuration success and , if necessary, identify and resolve anyconfiguration issues.

Procedure

1. From the SYMAPI server host, typesympd list to display a list of devices that arevisible to the host. Note the results.

2. On the client host, type sympd list.

l If the results match, the configuration is complete.

l If the command issued from the client returns a message such as no devicesfound, continue to the next step.

3. To isolate the issue:

a. Verify that the same command works on the host with the FC connection to theSymmetrix array.

b. Verify that the environment variables for Solutions Enabler are set using thesymcli -def command.

c. Verify that the netcfg file has been edited using the symcfg -services listcommand.

d. Verify the arrays you intend to monitor using the symcfg list command.

e. Verify that two additional gatekeepers are provisioned from each Symmetrix arrayusing the sympd list command.

Local Solutions Enabler scenarioThe local Solutions Enabler scenario supports resource discovery and data collection forEMC VMAX.

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

l The Solutions Enabler proxy scenario is the preferred configuration.

l Implementing this scenario includes the advantages of reduced network calls and amore secure configuration. However, the Collector software installed on the SYMAPIserver will require processing cycles from that server.


Local Solutions Enabler scenario 103

l This scenario requires two additional gatekeeper devices be mapped to yourCollector host.

Configuring VMAX arrays for consolidation of availability alertsUse this procedure to configure forwarding of availability alert traps (SNMP v1) fromVMAX arrays to the suite.

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

Procedure

1. Log into Solutions Enabler on the array provider host as an administrator.

2. Navigate to the daemon_options file in the C:\Program Files\EMC\SYMAPI\config\ directory.

3. In the parameter section SNMP_TRAP_CLIENT_REGISTRATION:

a. Uncomment the line storevntd:SNMP_TRAP_CLIENT_REGISTRATIONb. 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 filteringlevel for trap forwarding defined in the FCMGMT-MIB file.

Example: 10.31.90.148, 2041,10,ACTIVE4. In the parameter section LOG_EVENT_TARGETS, uncomment the line

storevntd:LOG_EVENT_TARGETS = snmp file.

5. To identify the arrays from which traps should be forwarded to the suite, type symcfglist, and press Enter.

6. For each array that should forward alert traps to ViPR SRM:

a. Type symcfg list, and press Enter.

b. In the parameter section LOG_SYMMETRIX_EVENTS, specify the appropriateevent categories in the format:

sid=<SYM serial number>, <event category 1>, <eventcategory 2>\

Example: SID=000194900854, disk, device, device pool,director, srdf consistency group, srdfa session, srdflink, 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 ;\

7. To reload the changes to the daemon_options file, type stordaemon actionstorevntd -cmd reload, and press Enter.

8. Ensure that the storevntd Event Daemon is running on the provider host.

9. If you have multiple VMAX array provider hosts in your storage environment, repeatthis procedure on each array provider host.






Note

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

Procedure






6. Click Install.




9. Click Next.


10.Click Next.


11.Click Next.















17.From the Type of VMAX array collected drop-down menu, select the type of VMAXarrays collected with this data collection instance.

You cannot collect VMAX3 and VMAX2 arrays using the same instance.

18.If you are collecting data from VMAX2/DMX arrays, enter the following settings:

a. If Solutions Enabler was installed in the default location, leave the SolutionsEnabler bin directory empty. If Solutions Enabler was installed in another location,type the path to the bin directory.

b. In Connection type, select Remote if you are using the Solutions Enabler proxyscenario or Local if you are using a local Solutions Enabler scenario. Refer to Preparing EMC VMAX for discovery and data collection on page 100.

c. In SYMAPI Connection name, type the connection name. This is the name of aSYMAPI service, which is configured in the netconfig file (netcnfg). This is not ahost name. To view the name that is configured, use the symcfg list -services command.

d. 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 performancemetrics.

Use SMI to collect array LUN performance metrics via SMI-S.

Use Unisphere for VMAX to collect array performance metrics other than LUNperformance metrics via Unisphere for VMAX.

Use SMI and Unisphere for VMAX to collect both array LUN performance metricsvia SMI-S and additional metrics via Unisphere for VMAX

e. Select Use advanced settings to configure polling settings.

19.If you are collecting data from VMAX3 arrays, enter the following settings:

a. Select a Performance collection type for all arrays .

Use Do not collect performance if you do not want to collect any performancemetrics.

Use SMI to collect array LUN performance metrics via SMI-S.

Use Unisphere for VMAX to collect array performance metrics other than LUNperformance metrics via Unisphere for VMAX.



Use SMI and Unisphere for VMAX to collect both array LUN performance metricsvia SMI-S and additional metrics via Unisphere for VMAX

b. Select Use advanced settings to configure polling settings.

20.Click Next.


21.Click Install.



24.Click VMAX.


26.In Server, select the server where the device will be dispatched.

27.In Instance, select the instance of the emc-vmax-collect where the device will bedispatched.

28.In Array Full Serial Number, type the Symmetrix SID from which data will be collectedby Solutions Enabler or SMI-S.

Run the symcfg list command to view a list of arrays.

Note

EMC recommends not to exceed six medium-sized (30K-40K devices) VMAX arrays foreach VMAX collector.


30.Click Ok.

31.Click Save.

Performance data will displayed in about an hour.

Discovery of large (> 20K devices) Symmetrix arrays may take long periods of time dueto the number of volumes. To address this, discover the Symmetrix on its owninstance. This will prevent the discovery from impacting the discovery of other arrayson the same symapi connection and allows the smaller arrays to complete during thepolling schedule.

Updating SolutionPack alert definitionsDuring SolutionPack update, any new alert definitions supported in the updated versiondo 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 VMAX in thetree.

2. In the table, click the pen icon button to the left of Pre-configured alerts.


4. In the Alerting Frontend, navigate to Local Mananger > Alert definitions > EMC VMAX tosee the newly added alert definitions.


Updating SolutionPack alert definitions 107

Configuring Solutions Enabler client access for VMAXSymmetrix Authorization using symauth provides a secure host and user-basedauthorization solution. Use this procedure in environments in which SymmetrixAuthorization is enabled.

Before you begin

Ensure that you have configured an appropriate Solutions Enabler scenario as describedin Preparing EMC VMAX for discovery and data collection on page 100.

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

l EMC Solutions Enabler Symmetrix Array Management Product Guide

l EMC Solutions Enabler Symmetrix Security Configuration Guide

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

Procedure

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

2. Check the status displayed in the the Authorization Control section todetermine 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 configurethe apg user and ViPR SRM hosts that will be issuing commands.Continue to step 3.

3. If Symmetrix Authorization is enabled, use the following procedures to complete theconfiguration:

a. Configuring host access on page 108

b. Adding client hosts to existing SYMAUTH configuration on page 109

c. Enabling client authorization on page 110

d. Validating Symmetrix access controls on page 110

Configuring host accessEnable the ViPR SRM apg account to access the local Solutions Enabler resources andlogs.

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

Procedure

1. Log in to the Solutions Enabler client host.

2. Navigate to /var/symapi



3. Grant the apg user write access to the following Solutions Enabler directories andcontents:

a. chown -R apg <SYMAPI_HOME>/config

b. chown -R apg <SYMAPI_HOME>/db4. Repeat steps 1-3 for each VMAX Collector server.

5. Grant the apg user authorization for the Solutions Enabler storapid daemon bynavigating to <SYMAPI_HOME>/config/daemon_users and adding the followingline to the storapid[Base Daemon] section of the file:

apg storapid <all>6. Save and exit the daemon_users file.

7. Set a password for the apg user.

8. Repeat steps 5-7 for each VMAX collector server.

9. Log out and log in as the apg user and run symauth show -username to determinethe fully-qualified account name.

10.Make note of the value displayed in your current username. For example:H:system_name\apg

11.Repeat steps 9-11 for each VMAX Collector server.

Adding client hosts to existing SYMAUTH configurationEnable the apg user with read-only monitoring access for VMAX arrays using SolutionsEnabler User Authorization.

Before you begin

Complete the procedure described in Configuring host access on page 108.

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

1. Run the symauth -sid <SID> list command to determine if User AuthorizationControl is enabled on the local client system.

l If User Authorization Control is disabled (Disabled) for the specific VMAX,proceed to Enabling client authorization on page 110.

l If User Authorization Control is enabled (Enabled) and in use (Enforced) for thespecific VMAX, continue with this procedure.

2. Ensure that you are logged in with an existing privileged account (e.g., root oradministrator).

3. Use the find / -name auth.txt command to find the auth.txt file.

4. Navigate to the folder with the auth.txt file.

5. Edit the file to include a line based on the results obtained from performing theprocedure described in Configuring host access on page 108. For example:

assign user H:system_name\apg to role Admin;6. Save the file.

7. Use the symauth -sid <SID> -f auth.txt command to commit changes to theUser Authorization User-to-Role map.


Adding client hosts to existing SYMAUTH configuration 109

8. Repeat this procedure for each VMAX array.

Enabling client authorizationUse this procedure when User Authorization Control is disabled (Disabled) for thespecific VMAX and you want to restrict the apg user to a monitoring role without limitingother accounts in the environment.

Before you begin

You determined that User Authorization Control is disabled by performing the taskdescribed in Adding client hosts to existing SYMAUTH configuration on page 109.

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

Procedure

1. 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;

2. Repeat step 1 for each VMAX Collector server.

3. Use the symauth -sid <SID> -f auth.txt command to commit changes to theUser Authorization User-to-Role map.

4. Repeat step 3 for each VMAX array.

5. Use the symauth -sid <SID> enable command to enable User AuthorizationControl for a specific VMAX array.

6. Repeat step 5 for each VMAX array.

7. Use the symauth list command to validate that User Authorization Control is enabledand 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 controlsValidate that the Symmetrix Access Control (SymACL) security feature is enabled and inuse on VMAX systems.

Before you begin

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



Procedure

1. Run the symacl list command for each VMAX array. Status information isdisplayed.

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


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


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

l If the Access Control field indicates N/A, SymACL is not enabled on this VMAXsystem. No action is necessary.

l If the Access Control field indicates Enabled, continue this procedure to secureViPR SRM client systems from a host system in the existing SymACL AdminGrpfor each VMAX system.

2. Create a SymACL access group appropriate to contain the ViPR SRM client systems(e.g., SRMGRP)

3. Add each client system's unique identifier to the access group.

4. Repeat for each ViPR SRM client host system.

5. Grant BASE access rights to the access group just created for all devices (ALL_DEVS).

6. Repeat this procedure for each VMAX system monitored by ViPR SRM.

Limitation: some alerts not displayedViPR SRM fails to receive and display some alerts

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


Limitation: some alerts not displayed 111



CHAPTER 16

SolutionPack for EMC VNX

l Overview............................................................................................................. 114l Technical Specifications......................................................................................114l Preparing your VNX for discovery and data collection.......................................... 115l Installing the SolutionPack..................................................................................117l Updating SolutionPack alert definitions.............................................................. 119l Limitations..........................................................................................................119

SolutionPack for EMC VNX 113

OverviewLearn how to install and configure the SolutionPack for EMC VNX. The SolutionPack forEMC VNX collects performance, topology, and capacity data from your VNX and VNXesystems 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 RawCapacity Usage, Usable Capacity, and File Systems Allocation, help you to improve theavailability of business critical applications and services by ensuring that thoseapplications have the storage resources they need to operate effectively.

Figure 15 SolutionPack for EMC VNX

Technical SpecificationsMain reports

SummaryOverview dashboard

Array SummaryReports 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 inproblem.

Raw CapacityReports the overall raw capacity in TB.

Block Usable CapacityReports the overall block usable capacity.



FileSystems UtilizationReports 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 ofCIFS/NFS shares.

Integrated Unified Systems (All Reports)Reports key indicators for VNXe systems such as the amount of IOPS and the overallhealth of the systems.

ManagementReports a summary of all systems including their model, serial number, system OEand number of metrics.


Preparing your VNX for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for EMC VNX and perform the necessary pre-configuration.

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

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

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

Configuring simple authenticationYou can configure simple authentication with VNX arrays using the default ViPR SRMaccount.

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

Note

The preferred method for secure polling and collection of data from VNX arrays is toconfigure authentication using a Unisphere security file. Refer to Unisphere security fileauthentication on page 116.


Preparing your VNX for discovery and data collection 115

Procedure

1. Configure the default ViPR SRM account (apg) with administrator privileges to accessthe 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 0getagent

Unisphere security file authenticationA Unisphere security file is the preferred method to provide secure polling and datacollection from VNX arrays.

By default, the ViPR SRM Collector runs using the local system account which is a specialWindows user with no environment. The preferred secure method is to create a Unispheresecurity 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 isautomatically stored in the security file, or you can specify an alternative username forthe security file in the -AddUserSecurity request using the optional -user switch. Ifyou omit the -user switch, the security file uses your current username. You can alsotarget 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 includethis path which will provide the required authentication to access the arrays.

Note the following:

l 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.

l Once the security file exists, you can edit XML configuration files that are used to polland collect data to use the path to the security file on the Collector host. The securityfile handles authentication.

l For details on configuring a security file on a host, refer to the Unispheredocumentation.

Configuring VNX arrays for file storage discoveryLearn 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 oneach VNX array.



Installing the SolutionPackAfter you log in as an administrator, you can install a SolutionPack from CentralizedManagement.

Before you begin

l Core modules must be up-to-date in all servers because not all module dependenciesare validated during the SolutionPack installation or update process.

l Managing Alert Consolidation explains how to configure alerts consolidation

Procedure






6. Click Install.




9. Click Next.


10.Click Next.


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 fromthe drop-down menu in the Alerting Web-Service Instance field.

12.Click Next.












16.In Event server hostname or IP address, select the Backend host on which the EventsListener 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 Backendhost.

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 areusing the default path.


23.Click Next.

24.From the Event database drop-down menu, select existing settings that have beenspecified for other components, or select Add a new Event database.

If you select Add a new Event database, type the information about the new eventdatabase.

25.Click Next.

26.In Administration Web-Service Instance, select the Frontend host.

27.Click Install.



30.Click VNX.


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 bedispatched.

34.In VNX type, select Block, File, Unified, or Integrated Unified.

If the following fields appear, enter the information specified:

a. In Unique friendly name for the VNX system, type the name.

b. In SP A IP, type the IP address of the SPA.

c. In SP B IP, type the IP address of the SPB.

d. In Use Naviseccli security file, select this checkbox if you are using the securityfile.

e. In User Scope, select LDAP, Global or Local.

f. In Naviseccli Username and Naviseccli Password, type the Naviseccli credentialsfor the block storage systems.

g. In Primary control station IP, type the IP address of the primary control station.

h. In Secondary control station IP, type the IP address of the secondary controlstation.



i. In VNX File username and VNX File password, type the credentials for the filestorage system.

j. In Management IP or hostname, type the IP address for the integrated unifiedsystem.

k. In Username, type the username for the integrated unified system.

l. In Password, type the password for the integrated unified system.


36.Click Ok.

37.Click Save.

38.In the tree, click SolutionPacks and navigate to the EMC VNX SolutionPack to verifythe installation.

After you finish

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

Updating SolutionPack alert definitionsWhen you update a SolutionPack, any modified alert definitions supported in theupdated 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 > <SolutionPackName> definitions.

2. Highlight <SolutionPack Name> definitions, and click the Export icon to create abackup 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 > <SolutionPackName> in the tree.

5. In the table, click the Reconfigure icon in the Pre-configured alerts row.


7. In the Alerting Frontend, navigate to Local Manager > Alert definitions > <SolutionPackName> definitions to see the updated alert definitions.

LimitationsVNX Free Raw Disk Capacity values are not the same as EMC Unisphere Free Raw Capacityvalues. 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 spaceavailable for user LUNs.

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


Updating SolutionPack alert definitions 119



CHAPTER 17

SolutionPack for EMC VPLEX

l Overview............................................................................................................. 122l Technical specifications...................................................................................... 122l Installing the SolutionPack..................................................................................123l Limitations..........................................................................................................125

SolutionPack for EMC VPLEX 121

OverviewLearn how to install and configure the SolutionPack for EMC VPLEX. The SolutionPack forEMC VPLEX collects performance, topology, and capacity data from your VPLEX systemsand displays the data in easy-to-use reports within ViPR SRM.

With this SolutionPack, you can unify your view of multiple VPLEX systems, includingphysical storage to virtual storage relationships. Capacity reports, such as Thick, Thin,Allocated and Not Allocated, help you to improve the availability of business criticalapplications and services by ensuring that those applications have the storage resourcesthey need to operate effectively.

Figure 16 SolutionPack for EMC VPLEX


SolutionPack / EMC VPLEXOverview dashboard

Back-end Throughput (IOPS)Reports the Back-end throughput (IOPS) for all VPLEX systems

Front-end Throughput (IOPS)Reports the Front-end throughput (IOPS) for all VPLEX systems

Front-end Bandwidth (KB/s)Reports the Front-end bandwidth (KB/s) for all VPLEX systems



Local Storage CapacityReports the overall storage capacity, including key indicators related to Capacity andVolumes

Distributed Storage CapacityReports the overall distributed storage capacity for all VPLEX systems

Shared Storage CapacityReports the overall shared storage capacity for all VPLEX systems

ClustersDrill-down report containing a summary of all clusters, including the cluster name,version, management IP, directors count, arrays count and virtual volumes count

Performance ReportsDrill-down report that reports Directors Processor (Global), Directors Processor (perCPU), and the Heap Used (%)

Capacity ReportsDrill-down report containing key indicators of Host to Physical Array End-To-EndView, Capacity per Array and Thick versus Thin

Port InventorySummarizes the ports on VPLEX systems

TopN Storage View ReportsDrill-down report containing key indicators of the TopN Storage Views per Capacity,IOPs and Throughput

Distributed StorageSummarizes the distributed storage devices on VPLEX systems

Inactive Device and Components reportsShows devices & sub-components which haven't been updated in more than 24hours



Before you begin

l Before installing confirm that the VPLEX model is supported.


l Identify the VPLEX type (Geo, Metro or Local), VPLEX Cluster IP/Hostname, VPLEXCluster Serial Number, and valid credentials.

l Check that a sink file is listed for each of the directors on the cluster.If the sink file is not listed for a director, check that the clusters and their associateddirectors are operating correctly. If the monitors are not created the SolutionPack canstill be installed, but the performance data will be missing for the correspondingdirectors. For instance, if cluster-2 is down then you could still install theSolutionPack but it will not collect any performance data for directors on that cluster.

l While adding a new device, ensure that the correct VPLEX type is selected. Do not adda Geo or Metro VPLEX System as two separate Local VPLEX Systems.

l While adding a new device, ensure that cluster 1 IP and serial number are notinterchanged with the cluster 2 IP and Serial Number.



Procedure






6. Click Install.




9. Click Next.


10.From the Alerting on data collection drop-down menu, select the Primary Backendhost.

11.Click Next.









16.Click Next.


17.Click Install.



20.Click VPLEX.


22.In the VPLEX section, provide the cluster host and authentication details for yourVPLEX system.



The default username for the VPLEX is service and the default password isMi@Dim7T.

It is important to enter the cluster information correctly, clusters are mapped to theircorrect number. Interchanging cluster IPs and SN results in a failure to collectperformance data.

Be sure to select the correct VPLEX type while adding the device. If you are adding aVPLEX Metro or VPLEX Geo, select the Geo/Metro VPLEX type from the drop-down andenter both VPLEX cluster details. If you are adding a VPLEX Local, select the LocalVPLEX type from the drop-down and enter the VPLEX cluster details. Do not add a Geoor Metro VPLEX System as two separate Local VPLEX Systems.


24.Click Ok.

25.Click Save.

It will take approximately take three hours for data to start appearing on reports.

After you finish

Check that SolutionPack for EMC VPLEX has been able to successfully create virtualvolume monitors:

1. To ensure that virtual volume performance monitors are created, you can run thefollowing command from the management server where these monitors were created:ll /monitoring/directors/*/*/*PERPETUAL*/*/fileThis command should list a file for each of the director (including directors on bothcluster-1 and cluster-2).

LimitationsThis SolutionPack does not support IBM DS arrays, HDS arrays, or HPXP arrays.

Only encapsulated virtual volumes are supported. LVM virtual volumes are notsupported.

Chargeback, path details, and end-to-end reports only support encapsulated virtualvolumes. Virtual Volumes created using logical volume management is not supported.

When an underlying virtual disk, on which the virtual volume is created, is alsocontributing to other virtual volumes, VPLEX and Host path details show incorrect valuesin the Storage View column for that particular virtual volume. Instead of listing only theStorage Views that it belongs to, it shows a pipe separated list of all the Storage Viewsthat the underlying virtual disk is contributing to.


Limitations 125



CHAPTER 18

SolutionPack for EMC ScaleIO

l Overview............................................................................................................. 128l Technical Specifications......................................................................................128l Installing the SolutionPack for EMC ScaleIO........................................................ 129

SolutionPack for EMC ScaleIO 127

OverviewLearn how to install and configure the SolutionPack for EMC ScaleIO. The SolutionPackfor EMC ScaleIO collects capacity, inventory, and performance data from ScaleIO RESTGateways and displays the data in easy-to-use reports within ViPR SRM.

Capacity reports provide details on free capacity, used capacity, and spare capacity atsystem level. Capacity reports per storage pools, per data servers, per drive, and perprotection domain levels provides details on free capacity and used capacity. Inventoryreports provide details on the data servers, data clients, storage pools, protectiondomains, and drive components. Performance reports provide detailed ScaleIOperformance metrics.

Figure 17 SolutionPack for EMC ScaleIO

Technical SpecificationsMain reports

All ScaleIO Systems CapacityFree Capacity, Hot Spare, Used Capacity

Raw Capacity UsageConfigured Usable, Hot Spare, RAID Overhead, Unconfigured, Unusable

Usable CapacityFree, Pool Free, Used For Block, Used For File, Used For Virtual Storage

Throughput per ScaleIO Systems

ScaleIO System Inventory

CapacityUsed Capacity by Purpose, All LUNs, Storage Pools




Installing the SolutionPack for EMC ScaleIOAfter you log in as an administrator, you can install a SolutionPack from CentralizedManagement.

Before you begin


Procedure






6. Click Install.




9. Click Next.




11.Select Do you want to configure advanced settings to configure polling settings.

12.Click Next.


13.Click Install.



16.Click EMC ScaleIO.


18.From ScaleIO version drop-down, select the ScaleIO version.

19.In ScaleIO REST Gateway IP or hostname, enter the IP Address, name, or FQDN of theScaleIO REST Gateway host to be configured.

20.Select Do you want to configure failover gateway to configure the failover settings.

21.In ScaleIO username, enter the username for the ScaleIO REST Gateway.

22.In ScaleIO password, enter the password to access the ScaleIO REST Gateway.



Installing the SolutionPack for EMC ScaleIO 129

24.Click Ok.

25.Click Save.



CHAPTER 19

SolutionPack for EMC XtremIO

l Overview............................................................................................................. 132l Technical specifications...................................................................................... 132l Installing the SolutionPack..................................................................................133

SolutionPack for EMC XtremIO 131

OverviewLearn how to install and configure SolutionPack for XtremIO. The SolutionPack forXtremIO generates real-time and historical reports and access capacity, performance, andinventory details. This gives insight into the management of your EMC XtremIO flashbased storage platform.

Figure 18 SolutionPack for XtremIO

Technical specificationsMain reportsXtremIO Information and details

XtremIO health

XtremIO Capacity dashboard, de-duplication and thin provisioning

XtremIO Performance metrics

XtremIO path details and connectivity

XtremIO Alerts





Before you begin


Procedure






6. Click Install.




9. Click Next.


10.Click Next.


11.Click Next.


12.From the Data collection drop-down, select existing settings that have been specifiedfor other components, or select Add a new data collection.

If you select Add a new data collection, type information about the data collection.

l FailOver-Filter must be enabled, which is the default.

l Hostname or the IP address to send data to must point to the host where thecollector is installed (localhost in a one-VM deployment and collector host in amulti-VM deployment).

l Network port to send data to must be set to the port to which the collected datawill sent. Specify your Arbiter port or legacy Backend data port. If you have chosena port other than 2020 for Arbiter, then the same port has to be configured in thisfield.




From the Web-Service Gateway drop-down menu, select existing settings that havebeen specified for other components, or select Add new gateway. If you select Add



new gateway, provide information about the web-service gateway where the topologyservice resides.

15.Select Enable Alert consolidation.

a. In Alert consolidation server hostname or IP address, select the Primary Backendhost.

b. In Alert consolidation server port number, select the port used for alertconsolidation.

16.Select Do you want to configure advanced settings to configure polling settings.

17.Click Next.


18.Click Install.



21.Click XtremIO.



24.From Instance, select the instance of the emc-xtremio-collect where the device will bedispatched.

25.In the section XtremIO configuration, enter the IP and credentials of the XtremIOarray’s Management IP address or hostname.

l In Management IP address or hostname, type the array management IP orhostname.

l Add the username and password of the XtremIO array

l Select the Timezone of the XtremIO system in UTC format


27.Click Ok.

28.Click Save.

29.In the tree, clickSolutionPacks and navigate to the EMC XtremIO SolutionPack to verifythe installation.

Performance data will displayed in about an hour.



CHAPTER 20

SolutionPack for Hitachi Device Manager

l Overview............................................................................................................. 136l Technical specifications...................................................................................... 136l Preparing Hitachi Device Manager for discovery and data collection....................137l Installing the SolutionPack..................................................................................137l Operational Issues.............................................................................................. 139

SolutionPack for Hitachi Device Manager 135

OverviewLearn how to install and configure SolutionPack for Hitachi Device Manager. TheSolutionPack for Hitachi Device Manager accesses performance data, configuration data,and capacity planning data pertaining to the Volumes, Disks, Ports, DynamicallyProvisioned Pools, and Parity Groups of Hitachi storage systems.

Figure 19 SolutionPack for Hitachi Device Manager


Main reports

Data center utilizationCapacity utilization across all Hitachi arrays

Disk utilizationCapacity utilization across various types of disks

Storage system -> Detailed InformationSummary report containing inventory information of all Hitachi devices:

l Parity groups

l Volumes

l Disks

l Frontend controllers

ResourcesContains various reports connected to the array

l Hosts

l Logical groups



Analytics

l Capacity Reports - Breaks down capacity across storage pool, tier, host for eachHDS array

l Performance collection troubleshooting - Helps troubleshooting performancedata collection


Preparing Hitachi Device Manager for discovery and datacollection

Identify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for Hitachi Device Manager

ViPR SRM communicates with the Hitachi Device Manager to poll information for HDSarrays.

Procedure

1. Identify read only account credentials with the ability to view all on the Hitachi DeviceManager system

2. Record the IP address/hostname for SSH and CIMOM communication


Before you begin


Procedure






6. Click Install.




9. Click Next.


10.Click Next.



Preparing Hitachi Device Manager for discovery and data collection 137



12.Click Next.













19.Select Enable Passive Host Discovery if you want the system to intelligently resolvehostnames from Hitachi Device Manager.


21.Click Next.



23.Click Install.





26.Click Hitachi Device Manager.


28.Select the server and collector instance where you want to store the configurationdetails for this device.

29.From the HDS type drop-down menu, select either Device Manager Collection orEmbedded Performance Collection depending on the type of collection you areconfiguring. Enter a unique friendly name such as the host or IP address.

30.Enter the hostname or IP address of the host, supply the login credentials, and specifythe appropriate configuration settings.


32.Click OK.

33.Click Save.

Operational IssuesThese are common problems and their workarounds, if possible.

LUNS not visible in Path details

LUNs from Hitachi AMS200 arrays do not appear in Path details and E2E reports. There isno workaround for this problem.


Operational Issues 139



CHAPTER 21

SolutionPack for HP 3PAR Storeserv

l Overview............................................................................................................. 142l Technical Specifications......................................................................................142l Preparing your system for discovery and data collection......................................143l Installing the SolutionPack..................................................................................143

SolutionPack for HP 3PAR Storeserv 141

OverviewLearn how to install and configure the SolutionPack for HP 3PAR StoreServ. ThisSolutionPack enables you to generate real-time and historical reports and accesscapacity, performance, and inventory details about your HP 3PAR StoreServ systems.

Figure 20 SolutionPack for HP 3PAR StorServ

Technical Specifications

Main reports

Back-end Throughput (IOPS)Reports the throughput (IOPS) for all HP 3PAR systems

Disk IOReports the overall disk IO activities (IOPS requests) for all HP 3PAR systems

Hits RatioReports the hits ratio distribution per subsystem as well as the hit ratio per array/controller for on all available subsystems

InventoryReports a summary containing the total count of all subsystems, controllers, powersupplies, ports, virtual volumes, logical drives, drive cages, and drives for allsubsystems

IOPS ReportsReports the total IOPS activities for the drives, LUNs, and ports on all availablesubsystems

Subsystems SummaryDrill-down report containing a summary of all subsystems, including key indicatorssuch as the subsystem name, version, IP address, drives, capacity, and model

TopN I/OReports the top 10 I/O activities for the drives, virtual volumes, and ports on allavailable subsystems



Usable CapacityReports the total array capacity available


Preparing your system for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for HP 3PAR StoreServ.

ViPR SRM communicates with the HP 3PAR StoreServ system using an account with read-only privileges on the system.

Procedure

1. Identify an account with read-only privileges for the HP 3PAR StoreServ system.

2. Ensure that the array can be accessed on port 22 using SSH.


Procedure






6. Click Install.




9. Click Next.

The windows displays alert details.



11.From the Alerting Web-Service Instance drop-down menu, select an existing instanceor create a custom instance.

12.Click Next.




Preparing your system for discovery and data collection 143









18.Click Next.





21.Click Install.



24.Click HP 3PAR.




28.Click OK.

29.Click Save.

After you finish

Depending on the numbers of Storage elements managed, you may need to edit theunix-services.properties file to increase the Heap Memory to a suitable level.The file is located at: /APG/Collecting/Collector-Manager/your_instance/conf/unix-services.properties.



CHAPTER 22

SolutionPack for HP EVA

l Overview............................................................................................................. 146l Technical Specifications......................................................................................146l Preparing your HP EVA system for discovery and data collection..........................147l Installing the SolutionPack..................................................................................147

SolutionPack for HP EVA 145

OverviewLearn how to install and configure the SolutionPack for HP EVA. The SolutionPack for HPEVA enables you to generate real-time and historical reports and access capacity,performance, and inventory details about your HP EVA systems.

Figure 21 SolutionPack for HP EVA


Main reports

Storage System dashboardGeneral information about the storage system

Dashboards for componentsHealth and performance information for storage system components

Forecast for Disk Group Utilization and Free CapacityReports disk group utilization and free capacity future trends

InventoryDashboard with aggregated information for all HP EVA storage systems




Preparing your HP EVA system for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for HP EVA.

ViPR SRM communicates with the HP EVA Element Manager to poll information for HP EVAsystems.

Procedure

1. Identify account credentials with administrator privileges on the HP EVA ElementManager system.

2. Ensure that SMIS is configured on each of the HP EVA Management Hosts.

3. Record the IP address/hostname for CIMOM communication.


Procedure






6. Click Install.




9. Click Next.









Preparing your HP EVA system for discovery and data collection 147

14.Click Next.





17.Click Install.



20.Click HP EVA.




24.Click OK.

25.Click Save.



CHAPTER 23

SolutionPack for HP Storageworks XP

l Overview............................................................................................................. 150l Technical Specifications......................................................................................150l Installing the SolutionPack..................................................................................151

SolutionPack for HP Storageworks XP 149

OverviewLearn how to install and configure the SolutionPack for HP StorageWorks P9000. TheSolutionPack for HP StorageWorks P9000 enables you to access performance,configuration data, and capacity planning data pertaining to the volumes, disks, ports,dynamically provisioned pools, and parity groups of arrays monitored by the HPStorageWorks P9000 XP software.

Figure 22 SolutionPack for HP StorageWorks P9000


Main reports

Data center utilizationCapacity utilization across all HP P9000 arrays

Disk utilizationCapacity utilization across various types of disks

Storage system -> Detailed InformationSummary report containing inventory information of all HP P9000 devices:

l Parity groups

l Volumes

l Disks

l Frontend controllers

ResourcesContains various reports connected to the array

l Hosts

l Logical groups



Analytics

l Capacity Reports - Breaks down capacity across storage pool, tier, host for eachHDS array

l Performance collection troubleshooting - Helps troubleshooting performancedata collection

Note

The Shared LUNs report does not report passive hosts. Hosts discovered via switches arereported.



Procedure






6. Click Install.




9. Click Next.


10.Click Next.




12.Click Next.















19.In the HP StorageWorks specific configurationsection, type the host information andaccess credentials.

a. Optionally, select the Enable Secure Connection (SSL) checkbox.

If you are using a secure connection, the default port is 5989. If you are using anon-secure connection, the default is 5988.

b. Click the plus (+) sign to add more systems.

20.Select Enable Alert consolidation.

a. In Alert consolidation server hostname or IP address, select the Primary Backendhost.

b. In Alert consolidation server port number, select the port used for alertconsolidation.

21.Select Enable Passive Host Discovery if you want to intelligently resolve hostnamesfrom your HP StorageWorks systems.


23.Click Next.



25.Click Install.





28.Click HP StorageWorks.




32.Click OK.

33.Click Save.





CHAPTER 24

SolutionPack for IBM DS

l Overview............................................................................................................. 156l Technical Specifications......................................................................................156l Preparing your IBM DS system for discovery and data collection..........................157l Installing the SolutionPack..................................................................................157

SolutionPack for IBM DS 155

OverviewLearn how to install and configure the SolutionPack for IBM DS. The SolutionPack for IBMDS enables you to generate real-time and historical reports and access capacity,performance, and inventory details about your IBM DS systems.

Figure 23 SolutionPack for IBM DS


Main reports

IOPSTotal read and write requests per system

Throughput (/s)Throughput of Read and Write operations for all systems

Subsystems SummaryDrill-down summary that contains key indicators such as the Controllers Ips, Drivecount, Logical Drive count, Array count, Raw Capacity, Configured Usable,Unconfigured, Free Capacity and Used Capacity for all Subsystems

InventoryTotal count of all Drives, Controllers, Logical Drives and Ports for all Subsystems

Arrays Utilization forecastKey indicators such as Parity Group Name, Capacity, Free Capacity and UsedCapacity




Preparing your IBM DS system for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for IBM DS.

ViPR SRM communicates with the IBM CIM/SMI-S provider that queries the storage array.

Procedure

1. Depending on your IBM DS model, do one of the following:

l IBM DS 3K/4K/5K models: Manually install and configure the IBM CIM/SMI-Sprovider on a management server.

l IBM DS 6K/8K models: The CIM/SMI-S provider is built into the HardwareManagement Console (HMC).

Note

Ensure that the CIM agent is enabled, as it was disabled by default in releasesprior to Release 4, Bundle 62.0.175.0.

2. Identify the CIM username and password used to access the array.



Procedure






6. Click Install.




9. Click Next.






Preparing your IBM DS system for discovery and data collection 157

12.Click Next.



14.Click Install.



17.Click IBM DS.




21.Click OK.

22.Click Save.



CHAPTER 25

SolutionPack for IBM LPARS

l Overview............................................................................................................. 160l Technical Specifications......................................................................................160l Configuring VIO for discovery.............................................................................. 161l Verify adapter IDs in NPIV configuration.............................................................. 165l Installing the SolutionPack..................................................................................166l Using Discovery Center to discover the VIO Servers and Clients........................... 167l Using Discovery Center to discover an HMC......................................................... 167l SolutionPack Reconfiguration............................................................................. 168

SolutionPack for IBM LPARS 159

OverviewLearn how to install and configure the SolutionPack for IBM LPAR. The SolutionPack forIBM LPAR collects Inventory details about IBM's Power-Servers managed by HardwareManagement Console (HMC) and displays the data in easy-to-use reports in ViPR SRM.

With this SolutionPack, you can generate reports to highlight key relationships in thevirtual environment such as:

l Power Systems managed by a HMC

l LPARs and VIOs residing on a Power System

l LPARs to the VIOs that provide the resource sharing capabilities for constituent LPARs

Capacity reports, such as File System Usage, help you to improve the availability ofbusiness critical applications and services by ensuring that applications have the storageresources they need to operate effectively.

Figure 24 SolutionPack for IBM LPAR

Technical SpecificationsMain reportsHMC Dashboard

LPAR/VIO Client Information and details

VIO Server basic details

Host Capacity Reports: Usable Capacity by FileSystem, Volume Manager Summary,Chargeable Capacity by Service Level, Disk Inventory

Topology end to end maps for VIOS/VIOC



Note

ViPR SRM Release 3.5 and earlier: Topology maps for VIOC will be reported only if therespective VIOS is discovered.

ViPR SRM Releases after 3.5: Topology maps for VIOC will be reported regardless of VIOSdiscovery.


Configuring VIO for discovery

The user credentials of VIO Server & VIO Clients should be configured in Discovery Center> Host Configuration.

ViPR SRM requires non-root user credentials or a SSH public/private key pair (keys can becreated for root / non-root users) to discover VIO Servers and VIO Clients.

When the VIOS Server is installed, the padmin user is automatically created and this userprovides restricted shell access. The ViPR SRM host data collection mechanism does notwork in the restricted shell environment, so you must create a non-root user andconfigure the non-root user via Sudo or PowerBroker to elevate the privileges to runcertain commands as root. Provide the non-root user credentials to ViPR SRM whilediscovering the VIO Server.

Note

ViPR SRM does not require padmin credentials to discover the VIO server.There are many tools available to elevate the privileges of a non-root user to runcommands as root, but ViPR SRM 3.6 supports only Sudo and Powerbroker.

Prepare VIO Server and VIO Client hosts for discoveryVIO Server and VIO Client hosts can be discovered in the following ways:

l Password based discovery using a root or non-root user. You can configure non-rootusers via sudo or PowerBrokerConfiguring sudo for VIO Server and VIO Client host discovery on page 161

Configuring PowerBroker for VIO Server and VIO Client discovery on page 163

l SSH public-private key pair based discoveryGenerating a public and private key pair for SSH key based authentication on page164

Configuring sudo for VIO Server and VIO Client host discoveryTo discover VIO Server/Client hosts and collect data from these hosts you have to elevateprivileges for the non-root user via sudo because some commands used in the datacollection require root privileges.

Before you begin

Supported sudo versionsLinux Fedora distribution: sudo-1.8.6 and above

Other operating systems: any version of sudo


Configuring VIO for discovery 161

Procedure

1. Include the path of sudo command in the environment variable $PATH for the sudouser.

The variable $PATH can be set either in /etc/environment or /etc/default/login or any other OS specific file.

2. Include the paths of OS commands in the environment variable $PATH for sudo user.

By default, most of the command files have the following location: /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

3. Verify that the $PATH is correct.

a. Log in as sudo user

b. Type which sudo.

4. Ensure that the sudoers file is available.

By default, the sudoers file is available in /etc or /opt/sfw/etc/ or /usr/local/etc/sudoers

5. Add the following line to the defaults section of the sudoers file:

Defaults !requiretty #for all usersor

Defaults : SRMADMIN !requiretty #for a specific user

6. For AIX hosts, if inq gives partial information, add the following line:

Defaults env_keep += "ODMDIR"7. Ensure that the sudo user has root privilege to run the following commands on a given

host.

Ensure the absolute path to the packages are provided in sudoers file.

It is recommended to use visudo to edit sudoers file.

Some packages are not installed by default.

AIXsar, inq, powermt, vxdisk, swap, kdb (kdb is only for VIO Clients)

Linuxsar, inq, powermt, vxdisk, dmidecode, lvdisplay, pvs, vgs, multipath



Figure 25 Sample sudoers file for Linux OS

Configuring PowerBroker for VIO Server and VIO Client discoveryPowerBroker for UNIX & Linux allows system administrators to delegate UNIX and Linuxprivileges and authorization without disclosing passwords for root or other accounts.Administrators can add specific commands in the configuration/policy files to enableViPR SRM to execute those commands and collect host information.

Procedure

1. Include the path of the pbrun command in the environment variable $PATH for thepowerbroker submit/run host.

2. Include the paths of the OS commands in the environment variable $PATH for thepbrun user. By default, most of the command files have the following location:

/usr/local/:sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin


a. Log in to the submit/run host.

4. Type "which pbrun".


Configuring PowerBroker for VIO Server and VIO Client discovery 163

5. The configuration/policy files exist on the master host and they must include thepbrun user name and the associated commands for host discovery. The followingscreenshot displays the policy files for a configuration in which the master/submit/run host is on the same host:

In this screenshot, the RootUsers variable includes "cmguser", which is the submituser (the ViPR SRM user used for discovering the host details) and the RootProgsvariable includes the various commands required by ViPR SRM to discover the host.Note that the commands mentioned in the section about configuring sudo apply hereas well.

Generating a public and private key pairFor the SSH key method of discovering UNIX hosts, you must generate a valid public andprivate key pair. You can choose any key generation tool to generate a valid public andprivate key pair.

Before you begin

Before you begin host discovery, you must have a public key present on all the UNIXhosts that are to be discovered using the private key. You can create SSH keys in any Unixenvironment and import them onto the ViPR SRM collector. EMC recommends that youcreate public-private SSH keys on ViPR SRM collectors (Linux VMs) where host discoverywill be initiated.

These steps describe the procedure to generate a public and private key pair for UNIXhosts using the ssh-keygen tool.

Note

The public key is to be added to the authorized_keys file on the target hosts intended fordiscovery and the private key is to be imported to the collector VMs where discovery istriggered.



Procedure

1. A Public-Private key can be generated using the following command:

ssh-keygen -t rsa -f <location_of_the_private_key/name_of_private_key_file> -N ""For example: ssh-keygen -t rsa -f /root/.ssh/id_rsa -N ””

2. Ensure that the public and private key pair that is generated has the followingpermissions:

l chmod 600 /root/.ssh/id_rsal chmod 644 /root/.ssh/id_rsa.pub

The private key file is id_rsa.

The public key file is id_rsa.pub.

3. To make the key pair functional, append the public key to <user's homedirectory>/.ssh/authorized_keys in the target UNIX host using the commandcat <location_of_the_public_key/name_of_public_key_file> >> /<user's homedirectory>/.ssh/authorized_keysFor example: cat /root/.ssh/id_rsa.pub >> /<user's homedirectory>/.ssh/authorized_keys

Next, import the private key to the Collector used for discovery.

Importing a private key into the Collector

Procedure

1. Place the generated private key in the RSC conf folder /opt/APG/Collecting/Remote-Shell-Collector/<instance_of_collector>/conf

2. Type chown apg:apg <private_key_file>

This command changes the owner.

The host is now ready for successful data collection.

Verify adapter IDs in NPIV configuration

In the NPIV configuration if a VFC Server Adapter is created on the VIOS and a VFC ClientAdapter on the VIOC, ensure correlation between the Physical HBA ports and the VirtualFC Client Adapter ports.

Procedure

1. On an HMC, go to the Virtual Adapters tab in the partition Properties of the VIOS/VIOCon which the VFC Server/Client Adapter are created.

2. Verify that a match exists between the Adapter ID of VFC Server Adapter and theAdapter ID of VFC Client Adapter.


Importing a private key into the Collector 165



Procedure






6. Click Install.




9. Click Next.




11.Click Do you want to configure advanced settings if you want to change the defaultHMC polling interval.

12.Click Next.



14.Click Install.



17.Click IBM LPAR.




21.Click OK.

22.Click Save.



Results

The SolutionPack for Physical Hosts will collect data from Physical Host/LPAR/VIOServers. You can configure script block from SolutionPack for Physical Hosts on multiplecollector VMs where you intend to discover hosts/LPAR/VIO server. Based on yourdeployment plan, you can distribute host discovery on multiple collector VMs.

Using Discovery Center to discover the VIO Servers and ClientsProcedure

1. From the User Interface, click Administration.

2. Click Discovery Center.

3. Under Device Type, click Host configuration.

4. Click Add new device.

5. In Server, select the collector VM where script block from SolutionPack for PhysicalHosts is installed.

6. Enter the VIO Server/Client configuration details and click Ok.

7. Add a new device for each VIO Server and Client that will be discovered.

8. Select the Authentication Type as:

Option Description

Password based Authenticates with password.

Public key base Authenticates with SSH public private key.

9. Provide username (root or sudo user):

a. Provide the password of the host for password based authentication

b. Provide the location of the private key for public key based authentication( /opt/APG/Collecting/Remote-Shell-Collector/ <instance-of-collector> /conf/ <name-of-private-key>)

10.Click Ok.

11.Select the device added and click Save.

12.Add a new device for each VIO Server and client that will be discovered.

Using Discovery Center to discover an HMCProcedure

1. From the User Interface, click Administration.

2. Click Discovery Center.

3. Under Device Type, click IBM LPAR configuration.

4. Click Add new device.

5. Enter the HMC hostname, username and password.

6. Click Ok.

7. Select the device added and click Save.


Using Discovery Center to discover the VIO Servers and Clients 167

8. Add a new device for each HMC that will be discovered.

SolutionPack ReconfigurationIf you wish to change the answers that were provided during SolutionPack installation thefirst time through, you could change them by reconfiguring the SolutionPack.

Procedure


2. Under Centralized Management.

a. Click SolutionPacks > Independent SolutionPackBlocks and select generic-rsc.

The SolutionPack Reconfiguration dialog box appears.

b. Click SolutionPacks > Infrastructure > IBM LPAR and select the instance for LPAR.

3. Change the configuration as desired.




CHAPTER 26

SolutionPack for IBM SAN Volume Controller/Storwize

l Overview............................................................................................................. 170l Technical Specifications......................................................................................170l Preparing for discovery and data collection......................................................... 171l Installing the SolutionPack..................................................................................171l Limitations..........................................................................................................173

SolutionPack for IBM SAN Volume Controller/Storwize 169

OverviewLearn how to install and configure the SolutionPack for IBM SAN Volume Controller/Storwize . The IBM System Storage SAN Volume Controller (SVC) is a member of the IBMStorwize family, which provides storage virtualization with a single point of control forstorage resources.

The SolutionPack for IBM SAN Volume Controller/Storwize enables you to generate real-time and historical reports and access capacity and performance details to gain insightinto the management of the underlying Storwize storage environment.

Figure 26 SolutionPack for IBM SAN Volume Controller/Storwize


Main reports

Virtual Storage DashboardDrill-down report that provides details about virtual storage information of the VirtualDisks such as Configured Usable, Virtual Disks Usable, Virtual Disks Unused, VirtualVolume Usable, Virtual Volume Used, and Virtual Volume Free.

ClustersDrill-down report that provides details about each cluster such as cluster nodes,virtual volumes, virtual disks, quorum disks, virtual pools, host association, pathdetails, and connectivity.

Performance ReportsDrill-down report that provides details about read and write requests, read and writethroughput on Virtual Disks, and Virtual Volumes for all SVC Clusters.



Capacity ReportsDrill-down report that provides a further breakdown of aggregated capacities such asConfigured Usable, Virtual Disks Usable, Virtual Disks Unused, Virtual VolumeUsable, Virtual Volume Used, Virtual Volume Free, and Usable Capacity by Pools.

Port InventoryDrill-down report that provides details of ports per cluster node such as portconnectivity, speed, and availability.

Inactive Devices and ComponentsDrill-down report that provides details of devices and components which have notbeen recently discovered.


Preparing for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for IBM SAN Volume Controller/Storwize .

Before you begin

l Confirm that the IBM SVC model and version are supported.

l ViPR SRM core modules must be up-to-date on all servers because not all moduledependencies are validated during the SolutionPack installation or update process.

l An SMI-S provider must be running on the IBM SVC server on port 5989.

Procedure

1. Record the IBM SVC/Storwize cluster IP address and hostname (for SSH and CIMOMcommunication).

2. Record the username and password for the cluster.

Note: All performance, topology, and capacity metrics are supported for users who aremembers of the "Administrator," "SecurityAdmin," or "Monitor" user group.Performance data (such as CPU usage and port traffic statistics of non-configurationnodes) are not supported for users who are members of the "Service" or"CopyOperator" user group.


Procedure






6. Click Install.



Preparing for discovery and data collection 171



9. Click Next.




11.Click Next.









16.Click Next.



18.Click Install.



21.Click IBM SAN Volume Controller/Storwize.



24.Leave Enable performance synchronization checked.

Enable performance synchronization allows ViPR SRM to collect and reportperformance statistics across all of the nodes. The performance statistics files arecopied from the non-config nodes to the config node, and the copied files are purged



after they are processed. None of the original performance statistics on any node arepurged. Disabling performance synchronization will allow collection and reportingonly on the config node.


26.Click OK.

27.Click Save.

Limitationsl Back end arrays IBM DS, IBM XIV, HDS, HPXP, and XtremeIO are not supported.

l Internal Storage is not supported in the Raw Capacity Usage and Configured Usablereports. Service Level and Chargeback is not supported for mdisks (virtual disks)based on internal storage.

l Replication is not supported.

l Hosts connected to IBM SVC discovered through EMC Host Interface are notsupported.


Limitations 173



CHAPTER 27

SolutionPack for IBM XIV

l Overview............................................................................................................. 176l Technical Specifications......................................................................................176l Preparing your IBM XIV system for discovery and data collection......................... 177l Installing the SolutionPack..................................................................................177l Limitations..........................................................................................................178l Known problems ................................................................................................ 179

SolutionPack for IBM XIV 175

OverviewLearn how to install and configure the SolutionPack for IBM XIV. The SolutionPack for IBMXIV enables you to monitor the status and performance of your IBM XIV disk storagesystem, and access performance and configuration data pertaining to the volumes, disks,pools and ports of IBM XIV systems.

Figure 27 SolutionPack for IBM XIV


Main reports

Volumes IOPSReports the read and write requests over time for all XIV systems

ReadRequestsReports the read requests over time for all XIV systems

WriteRequestsReports the write requests over time for all XIV systems

Volumes Throughput (/s)Reports the volumes read and write throughput over time for all XIV systems

ReadThroughputReports the volumes read throughput over time for all XIV systems

WriteThroughputReports the volumes write throughput over time for all XIV systems

Systems detailed per array capacity and performance reportsReports capacity and performance per array.




Preparing your IBM XIV system for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for IBM XIV.

ViPR SRM communicates with IBM XIV using the CIM agent.

Procedure

1. Ensure that the CIM agent is installed.

Starting with IBM XIV Storage System V10.1.0, the CIM agent is pre-installed on theadministrative module. The embedded CIM agent is automatically enabled andpreconfigured.

2. Identify the access credentials.



Procedure






6. Click Install.




9. Click Next.


10.Click Next.




12.Click Next.




Preparing your IBM XIV system for discovery and data collection 177









18.Click Next.



20.Click Install.



23.Click IBM XIV.




27.Click OK.

28.Click Save.

LimitationsDiscovery of LDAP users requires active GUI sessionDue to limitations in the IBM software, discovery using the LDAP users account will notsucceed unless there is an active IBM XIV GUI user session. The session must be activeeither for the corresponding LDAP user or for a storage administrator.

Max Storage Volume Response Time metric not collectedThe SolutionPack does not collect the Max Storage Volume Response Time (ms) metricneeded for the All > Explore > Hosts > [host] > Device Summary > [host] report.



No support for Used for File, LUN alias, and Replica 2 and Replica 3 details‘Used for File’ metrics are not supported. Therefore, the respective columns in thefollowing reports will be empty.

l All > Dashboards > Storage > Enterprise Capacity Dashboard > Usable Capacity by Pool

l All > Dashboards > Storage > Chargeback by Group

l All > Explore > Storage > More Reports > Storage Pools

‘LUN Alias’ column is empty in the following report:

l All > Explore > Storage > More Reports > More Storage Inventories > All LUNs

Remote replication data is not exposed through the SMI provider; therefore, Replica 2and Replica 3 columns details will be empty in the following report:

l All > Explore > Storage > More Reports > More Storage Inventories > Replication

Known problemsTable 5 Known problems

Issue number Problem description Workaround/Resolution

SRS-11244EMP-2943

After updating to 3.6, the Discovery Center is unable toimport the device details.

You can add a third column "friendly name" in theexported CSV file and give the serial number of XIVarray (for backward compatibility) as friendly name foreach instance of an XIV system. Then import themodified CSV file in to the updated Discovery Center.

SRS-11095(Doc)

In the report All->Explore->Storage->More Reports->Enterprise Capacity, the "Used for HDFS (GB)" and"Used For Object (GB)" columns have no capacity data.

There is no workaround at this time.

SRS-11530 Updating this SolutionPack to 3.6 requires alerts blocks("pre-configured alerts" and "alerts consolidation")installation at the 3.6 level.

You should deploy blocks related to ("pre-configuredalerts" and "alerts consolidation" from the userinterface.Go the "SolutionPacks" node, select "SolutionPackCenter," choose the IBM XIV SolutionPack, and deploythe alerts blocks for the existing instance.

SRS-9925 After updating from version 3.5 or earlier to version 3.6,if you provide a random user-friendly name for the XIVarray, historic data will not be displayed.

After the update, from the Discovery Center, update the"Unique friendly name for the XIV system" field with thearray's serial number. For example, if the IBM XIV arrayserial number is 9825369, change the "Unique friendlyname for the XIV system" field to "XIV 9825369."


Known problems 179



CHAPTER 28

SolutionPack for Microsoft Hyper-V

l Overview............................................................................................................. 182l Technical specifications...................................................................................... 182l Configuring credentials for SolutionPack for Microsoft Hyper-V............................183l Requirements for data collection.........................................................................183l Installing the SolutionPack..................................................................................183l Using a test script to query WMI objects.............................................................. 184

SolutionPack for Microsoft Hyper-V 181

OverviewLearn how to install and configure SolutionPack for Microsoft Hyper-V. The SolutionPackfor Microsoft Hyper-V generates real-time and historical reports so you understand Hyper-V performance through global and detailed status of Hyper-V hosts and underlying virtualmachines.

Figure 28 SolutionPack for Microsoft Hyper-V


Main reports

InventoryDisplays the inventory of devices, parts and metrics from Hypervisors and VirtualMachines

Virtual Disk Use AnalysisTool to analyze the utilization profile of Virtual Hard Disk images

All Hosts | All Virtual MachinesDisplays all available performance graphs for Hypervisors and Virtual Machines

Global StatusShows the global status of all hosts and running virtual machines in theenvironment, detailed by component type

SLA Detailled ViewShows the current and forecasted SLA values for Hypervisors and Virtual Machines

Virtual Machines Running On Snapshot DisksShows all virtual machines running on snapshot disks. They impact diskperformance and impact storage performance when it is time to commit changes onthe original virtual disk.




Configuring credentials for SolutionPack for Microsoft Hyper-Vl Hyper-V Collector Manager must have the right to query WMI objects from Hyper-V

hosts

l PowerShell must allow the execution of unassigned PowerShell scripts

Requirements for data collection

In order to collect data from Microsoft Hyper-V hosts, the environment needs to meet thefollowing requirements:

l The Collect SolutionPack Block must be installed in a server using Windows Server2008 R2 Service Pack 1 or later.

l The Collect SolutionPack Block must be able to query WMI objects in remoteMicrosoft Hyper-V hosts. For required privileges, refer to the manual EMC ViPR SRMSolutionPack Privileges.

l The Collect SolutionPack Block machine must allow the execution of unsignedPowerShell scripts. To provide this capability, run the following command as anadministrative user: PowerShell -C Set-ExecutionPolicy Unrestricted.


Before you begin


Procedure






6. Click Install.




9. Click Next.





Configuring credentials for SolutionPack for Microsoft Hyper-V 183

11.Click Next.



13.Click Install.



16.Click Microsoft Hyper-V.



Clicking the Test button results in a warning message that can be ignored.

19.Click OK.

20.Click Save.

Using a test script to query WMI objects

The Test feature located in the Discovery Center under the Centralized Management UI isnot supported for the SolutionPack for Microsoft Hyper-V. Instead, use the test methodpresented in this topic.The SolutionPack for Microsoft Hyper-V provides a script that can be used to check if ispossible to query all required WMI objects using the provided user. The script is in thefolder <APG_FOLDER>/Collecting/XML-Collector/<SolutionPack_instance_name>/conf/. You must execute the script from theCollect SolutionPack Block machine. Use the following syntax to run the script:

TestWMI.ps1 -Computer <ip-or-hostname> -Username <domain-or-machine\username> -Password <password> [-NoPing]

-ComputerRemote Hyper-V host IP address or hostname

-UsernameUsername used to perform remote WMI queries, in the format DOMAIN\username fordomain users or MACHINE\username for local users

-PasswordPassword of the user specified with the -Username parameter

-NoPing(optional) If the remote Hyper-V host is blocking ping requests, you must use thisparameter to skip connectivity tests



CHAPTER 29

SolutionPack for Microsoft SQL Server

l Overview............................................................................................................. 186l Technical Specifications......................................................................................186l Where to find the latest SolutionPack software....................................................187l Installing the SolutionPack..................................................................................187l Confirming report creation...................................................................................188l Troubleshooting ................................................................................................. 188

SolutionPack for Microsoft SQL Server 185

OverviewLearn how to install and configure the SolutionPack for Microsoft SQL Server. ThisSolutionPack provides the unified monitoring of Microsoft SQL databases using SQLqueries targeted at servers. It provides key information for database administrators, suchas server host performance, database availability, and deadlocks. Both ViPR SRM andService Assurance Suite use this SolutionPack.


SolutionPack version1.0

Compatible EMC M&R versions

Supported Microsoft SQL versionsSQL Server 2008R2

SQL Server 2012

Data collection methodSQL collector

SQL commandsThis SolutionPack uses these commands:

l SELECT

l CONNECT

l INSERT

l CREATE TABLE (creates temporary tables)

l EXEC (executes store procedure that lists disks and their available free space)

l DROP (removes temporary tables)

User privilege requirementsSQL authentication requires that the user be a member of the SYSADMIN group.

The Windows user account requires that the user be a member of the Guests group or theDomain Guests group.

The Windows user account must be imported into the Microsoft SQL Server with settingssimilar to these:

l Server roles of public

l Securable grants for Connect SQL, View any definitions, and View server state

The default database must be the master.

Main reportsHost Health (%), including the percentage of CPU and memory utilization of all hosts

Performance of SQL Server

Databases Overview

Performance Scorecard of storage usage, index contention, memory pressure, signalwaits, SQL server hosts performance, and user connections and logins



Situations to Watch, including memory exceptions, SQL server locks, I/O botllenecks,CPU bottleneck, data files out of space, and actual and forecasted SLA values

Inventory of servers, databases, data files, and objects




Before you begin

l Determine whether you need a SolutionPack license file by checking the featurenames and expiration dates listed in Centralized Management > LicenseManagement. If the license is not listed, obtain one by completing a Support Request(SR) form, which you can find on the EMC Online Support website at http://support.emc.com.

l Make sure the core modules, such as the Module-Manager, are up-to-date on allservers since not all module dependencies are validated during the SolutionPackinstallation. See the EMC M&R (Watch4net) Installation and Configuration Guideprovides for more information.

Procedure

1. Log in to Centralized Management.

2. Select SOLUTIONPACK CENTER.

3. Select the SolutionPack for Microsoft SQL Server in the Browse and InstallSolutionPacks screen.

4. Read the summary information and click Install.

5. In the Collector field of the Select the components to install window, select theCollector host.

6. In the Reports field, select the Frontend host.

7. Click Next.

8. Make a selection in the Data Collection field.

9. If you select Add a new Data collection, enter information for the new data collection.In the Hostname or IP address to send data field, type localhost.

10.Leave Enable alerting on data collected selected.

11.Make a selection in the Alerting on data collection field.

If you select Add a new Alerting on data collection, type information for the newalerting destination. In the Alerting Backend hostname or IP address field, select thePrimary Backend host.


Where to find the latest SolutionPack software 187





12.Type information to identify the SQL Server.

If you select Choose for Windows authentication instead of SQL Serverauthentication, type the Windows domain name.

13.Set these values:

l Fully qualified name of the SQL server

l Port

l Username

l Password


15.Click Next.

16.In the Administration Web-Service Instance field on the Reports window, select theFrontend host.

17.Select Centralized Management > SolutionPack to verify the installed SolutionPack.

Confirming report creationAfter 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.

Troubleshooting

Report display problems

l What to do if data does not appear in reports on page 188

l Running a scheduled task to import data into reports on page 189

l Viewing collector errors in the Collector-Manager log files on page 190

What to do if data does not appear in reports

Procedure

1. Do the following to check the Collector Manager logs:

a. View /opt/APG/Collecting/Collector-Manager/microsoft-sqlserver/logs/collecting-0-0.log.

b. Verify that the last message in the log states that a certain number of raw valueswere collected using 13 SQL queries. This message indicates the collector isworking.

For example: <instance_master> collect done: 2,735 new rawvalues collected in 0 seconds 527 ms using 13 SQL queries



c. Check for any Java exceptions and warning messages.

2. If collector errors exist, do the following:

a. Ping the Microsoft SQL Server using the fully qualified domain name (FQDN).

b. Replace the current user, which is the username and password set duringSolutionPack installation to retrieve data from the Microsoft SQL sever, with a userwith SYSADMIN rights.

c. Use telnet to check if the Microsoft SQL port is accessible from the SQL collectorserver.

d. Reconfigure the SolutionPack by navigating to Centralized Management >SolutionPacks > Microsoft SQL Server.

e. Under SolutionPackBlock, click the pencil next to Collector to reconfigure thesettings.

f. To edit advanced connection settings, you may need to manually edit the SQLcollector configuration file.

3. If no errors exist and the last message in the log indicates that 13 queries wereexecuted, do the following:

a. Wait a minimum of three polling cycles. By default, one polling cycle is fiveminutes.

b. Navigate to Centralized Management > Scheduled Tasks.

c. Under the Backend category, run backend/Default/import_variable_status.task.

d. Refresh the reports after five minutes.

4. Make sure the Frontend is attached to the database used by the SQL collector.

Running a scheduled task to import data into reportsAfter you push a new configuration into a collector, a scheduled task runs and populatesthe reports with new data. You can manually run the scheduled task to import the datamore quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure



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.


Running a scheduled task to import data into reports 189

Viewing collector errors in the Collector-Manager log filesReview the Collector-Manager log files to troubleshoot problems with data collection.

Procedure


2. Click Centralized Management > Logical Overview.

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 error messages.



CHAPTER 30

SolutionPack for NetApp Filer

l Overview............................................................................................................. 192l Technical specifications...................................................................................... 192l Configuring access credentials............................................................................193l Preparing NetApp Filer for discovery and data collection......................................193l Installing the SolutionPack..................................................................................193l Supported use cases and limitations...................................................................195

SolutionPack for NetApp Filer 191

OverviewLearn how to install and configure the SolutionPack for NetApp Filer. The SolutionPack forNetApp Filer enables users to get a deeper understanding of the performance and storagecapacity parameters of NetApp Filer devices through a unified monitoring of NetApp Filerdevices distributed in the network.

The SolutionPack generates reports regarding performance and capacity metrics.

Figure 29 SolutionPack for NetApp Filer


Main reports

Raw Capacity UsageProvides the raw capacity usage details such as Configured Usable, RAID Overhead,Unconfigured and Unusable capacity details

NAS File System UsageProvides details about the file system Free & Used capacity

CPU utilizationGlobal utilization of CPU per filer

CIFS Open SessionsLists open CIFS sessions

Storage Systems SummaryDrill-down report that provides key information regarding the NetApps storagesystems including IP addresses, NetApp release, aggregate capacity and total disksavailable

CapacityDrill-down report that provides a complete view of of Aggregate Utilization (Free/Used) Volumes, Deduplication,Disks and Maxfiles report



PerformanceDrill-down report that shows the utilization of CIFS, NFS, CPU, LUNs and Volumes,Network for all NetApp systems


Configuring access credentials

ViPR SRM communicates with NetApp Filer arrays using the NetApp CLI over SSH.

It requires following:

l SSH connection to the 7-Mode NetApp devices with the following roles: login-ssh, cli-stats*, cli-snap*, cli-aggr*,cli-vol*, cli-disk*, cli-nfs*,cli-cifs* ,cli-df,cli-sysconfig, cli-ifconfig, cli-qtree, cli-quota,cli-storage, cli-maxfiles, cli-echo, cli-lun,cli-fcp

l SSH connection to the C-Mode NetApp devices with the following roles: access level'readonly' for the commands volume, df, lun, storage, statistics, network, vserver,cluster, sleep and access level 'all' for the commands set, system

Verify that you are polling the real filer (not a vFiler).

Note

Ensure your host names are consistent.

Preparing NetApp Filer for discovery and data collectionIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for NetApp Filer.

ViPR SRM communicates with NetApp Filer arrays using the NetApp CLI over SSH.

Procedure

1. Identify the IP, username, password, SSH Port no (default is 22), and NetApp FilerMode (7-Mode or C-Mode).

2. Identify the Cluster management IP for C-Mode Filer discovery.



Before you begin


Procedure






Configuring access credentials 193


6. Click Install.




9. Click Next.


10.Click Next.


11.Click Next.









16.Click Next.



18.Click Install.



21.Click NetApp.




25.Click OK.



26.Click Save.

Supported use cases and limitationsTable 6 Supported use cases and limitations

Use case Support (7 mode) Support (C mode)

Discovery Yes Yes

Maps, Path and Connectivitydetails

Yes7 mode to external storage array(VNX & VNXe)

7 mode to VPLEX

7 mode to IBM SVC

YesC-mode topology

Not supported:

External storage array

Global Capacity reports YesNot supported:

"NAS Used by Purpose" -Local &Remote replica Used metric

YesNot supported:

"NAS Used by Purpose" -Local & Remote replica Usedmetric

Explore reports Yes Yes

Chargeback Yes Yes

Performance Yes Yes

Alerting Yes Yes

Compliance No No

Detailed reports for File andBlock at SP level

Yes Yes

Qtree and Quota Reports Yes Yes

Limitations in global reportsUsed capacity is the same as the total capacity for Ontap 7.x versions of the followingreports:

l Explore > Storage > More Reports > Service Level Capacity

l Explore > Storage > More Reports > More Storage Inventories > Array by Service Level

In Dashboards > Storage > Enterprise Capacity Dashboard > Usable Capacity > Used forBlock, the OnTap 7.x CLI does not provide LUN used capacity therefore the total capacityis used for computation.

The following global reports/metrics are not applicable:

l In Explore > Storage > More Reports > More Storage Inventories > NAS File Systems,Snapshot Total, Snapshot Used, and Snapshot Utilization are not applicable

l In Explore > Storage > More Reports > Storage Pools, Overhead Capacity is notapplicable in the File Systems/Flex Vols report and Pool Enabled and Pool Overheadare not applicable in the Subscriptions report

l Explore > Storage > More Reports > RAID/Parity Group

l Explore > Storage > More Reports > NAS Pools


Supported use cases and limitations 195

In Report Library > NetApp Filer > Storage Systems Summary > 7-Mode > Filer CPUUtilization, the "Uptime" and "System CPU(%)" columns will be empty for OnTap 8.1 orhigher versions that are configured as 7-Mode.

In Dashboards > Storage > Enterprise Capacity Dashboard > Used Capacity by Type andExplore > Storage > More Reports > Enterprise Capacity, the "Used for HDFS" and "Used forObject" metrics are blank for NetApp.

In Explore > Storage > More Reports > More Storage Inventories > NAS File Systems, forfilers running OnTap 8.2, the total capacity of a thin file system will be the same as itsused capacity.



CHAPTER 31

SolutionPack for Oracle Database

l Overview............................................................................................................. 198l Technical specifications...................................................................................... 198l Installing SolutionPack........................................................................................199l Configuring the SolutionPack with an unprivileged account.................................200

SolutionPack for Oracle Database 197

OverviewLearn how to install and configure the SolutionPack for Oracle Database. TheSolutionPack for Oracle Database monitors the status and performance of an Oracledatabase. The SolutionPack gives visibility into listeners, tablespaces, versions,connections, commits and rollbacks. You can survey the Oracle core process, such as theSGA, and verify the hit ratio about cache, dictionary cache, latch cache, library cache, sortand sessions.

Figure 30 SolutionPack for Oracle Database


Main reportsEntire Oracle database infrastructure summary

Detailed database size

Oracle RAC view

Instances availability

Cross server KPIs




Installing SolutionPack

Before you begin


Procedure






6. Click Install.




9. Click Next.





12.Optionally select the Enable property import for server enrichment checkbox.

13.In the Backend configuration section, type the host information and credentials forthe Primary Backend Host.

14.Select Configure collector advanced settings to configure polling settings.

15.Click Next.





18.Click Install.





Installing SolutionPack 199

22.Click Oracle Database.



25.Click OK.

26.Click Save.

Configuring the SolutionPack with an unprivileged account

The ViPR SRM collector must connect to each instance of Oracle databases and performSQL queries. You can use either an administrator equivalent system account, or create adedicated system account for the collector. If you want to use the last option, please askthe DBA administrator to run the following query against every instances/RAC cluster.This will create a watch4net account with specific grants for the ViPR SRM collector.

Procedure

1. Create the watch4net user:

create user watch4net identified by <securepassword> default tablespace users temporary tablespace temp;

2. Grant the necessary privileges to the watch4net user by running the following grants:

grant create session to watch4net;grant select on V_$SYSSTAT to watch4net;grant select on v_$filestat to watch4net;grant select on v_$database to watch4net;grant select on dba_data_files to watch4net;grant select on dba_extents to watch4net;grant select on dba_segments to watch4net;grant select on dba_free_space to watch4net;grant select on v_$parameter to watch4net;grant select on v_$sgainfo to watch4net;grant select on v_$rowcache to watch4net;grant select on v_$librarycache to watch4net;grant select on v_$latch to watch4net;grant select on v_$rollstat to watch4net;grant select on v_$dispatcher to watch4net;grant select on v_$instance to watch4net;grant select on v_$sesstat to watch4net;grant select on v_$statname to watch4net;grant select on v_$session to watch4net;grant select on v_$sess_io to watch4net;grant select on v_$asm_disk to watch4net;grant select on v_$asm_diskgroup to watch4net;grant select on v_$logfile to watch4net;grant select on v_$log to watch4net;grant select on sys.dba_tablespaces to watch4net;grant select on v$iostat_file to watch4net;grant select on dba_libraries to watch4net;

Results

Your dedicated account is configured.



CHAPTER 32

SolutionPack for Oracle MySQL Database

l Overview............................................................................................................. 202l Technical Specifications......................................................................................202l Where to find the latest SolutionPack software....................................................202l Installing the SolutionPack .................................................................................203l Confirming report creation...................................................................................203l Troubleshooting ................................................................................................. 204

SolutionPack for Oracle MySQL Database 201

OverviewLearn how to install and configure the SolutionPack for Oracle MySQL Database. ThisSolutionPack provides management capabilities typically found in database-centric toolsalong with management support from other technologies. You can measure client activityby reporting on data from your database tier alongside your business logic andpresentation tiers. Both ViPR SRM and Service Assurance Suite use this SolutionPack.


SolutionPack version1.0

Compatible EMC M&R versions

Supported Oracle MySQL versionsMySQL 5.1

MySQL 5.5

MySQL 5.6

User privilege requirementsThis SolutionPack requires MySQL database user login privileges to collect informationfrom MySQL database servers running remotely.

Data collection methodThe Oracle MySQL SolutionPack's sql-collector queries theinformation_schema.GLOBAL_STATUS table and theinformation_schema.SESSION_VARIABLES table.

Main reportsQuery Cache Volume among all MySQL Databases

Number of SQL queries among all MySQL Databases

Total Current Connection

Database Health and Performance

Connection Health

Memory Health

Slave's Health

Database Performance


This 30-day free evaluation only applies to new installations and is not available forupgraded installations. If you upgrade the core software and want to try a newSolutionPack, 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.


Before you begin

l Determine whether you need a SolutionPack license file by checking the featurenames and expiration dates listed in Centralized Management > LicenseManagement. If the license is not listed, obtain one by completing a Support Request(SR) form, which you can find on the EMC Online Support website at http://support.emc.com.

l Make sure the core modules, such as the Module-Manager, are up-to-date on allservers since not all module dependencies are validated during the SolutionPackinstallation. See the EMC M&R (Watch4net) Installation and Configuration Guideprovides for more information.

Procedure

1. Log in to Centralized Management.

2. Select SOLUTIONPACK CENTER.

3. Select the SolutionPack for MySQL Database in the Browse and Install SolutionPacksscreen.

4. Read the summary information and click Install.

5. Edit the default instance name, oracle-mysql-database, and click Next.

6. Set these values for the MySQL database server:

l Database hostname or IP address

l Database port

l Please select the credentials

7. If you have multiple instances of the Oracle MySQL database servers in yourconfiguration, click + to name each server and set the values shown in the previousstep.

8. Select Administration Web-Service Instance as the default and click Install.

9. When a checkmark appears next to the Collector and the Report, click OK.

10.Select Centralized Management > SolutionPack to verify the installed SolutionPack.



Procedure



Results








Troubleshooting


l What to do if data does not appear in any reports on page 204

l What to do if data does not appear in some reports on page 205


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 intothe reports.

2. On the Device Discovery Dashboard, verify that all icons are green.

3. To view the log files for errors, go to Centralized Management and click Collecting >Collector-Manager::<instance name> > Log Files.

4. Log in to your MySQL database and verify data is being written to the MySQL databaseserver. Look specifically at the data_property, data_variable, and all cachetables:

select * from data_property;select * from data_variable;select * from <cache-table-name>;

5. In the MySQL database, verify the user has the required login permissions to the localand remote MySQL servers being monitored by the SolutionPack. If not, follow thesesteps to create credentials for the user:

a. Navigate to bin/mysql/ -u root -p <rootUserPassword> -P<mysqlServerPort>

b. Type the following commands to create the credentials:

use mysql;CREATE USER 'testuser'@'%'IDENTIFIED BY 'watch4net';GRANT ALL ON *.* TO 'testuser'@'%';

c. Use these user credentials to log in to the local and remote MySQL databaseservers from the SolutionPack.


Before you begin


Procedure






4. Click Database.


6. Click Run Now.


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

Searching for metrics in the Oracle MySQL databaseYou can verify that a metric is being collected and used for reporting when you searchand find the metric in the database.

Procedure

1. Go to the Administration page.

2. Under Modules, click Management of Database Modules.

3. On the Metric Selection page, create the filter.

For example, to list the key_reads (the number of physical reads of a key block fromdisk to the MyISAM cache), type source=='MySQL-Collector'&&name=='key_reads' in the Filter field.

4. Click Query.

A list of the metric results appears. If nothing displays, the metric is not beingcollected.


Procedure








What to do if data does not appear in some reports 205



CHAPTER 33

SolutionPack for Physical Hosts

l Overview............................................................................................................. 208l Technical Specifications......................................................................................208l Preparing your hosts for discovery and data collection........................................ 209l Installing the SolutionPack..................................................................................227l Adding hosts as part of groups in Discovery Center............................................. 228l SolutionPack reconfiguration.............................................................................. 229l Limitations..........................................................................................................230

SolutionPack for Physical Hosts 207

OverviewLearn how to install and configure theSolutionPack for Physical Hosts. The SolutionPackfor Physical Hosts enables you to monitor and generate real-time and historical reportson the performance of physical hosts.

The SolutionPack gives better insight into parameters such as capacity and utilizationassociated with an inventory of File Systems, Volume Groups, and Disks (local andremote).

Figure 31 SolutionPack for Physical Hosts


Main reportsHost Information and details

File Systems, Volume Management summary report

Internal and SAN Disk Capacity Reports

Service level for LUNs mapped to host file systems

Performance metrics for host devices namely CPU, Memory, Disks

Native Multipathing and Powerpath reports




Preparing your hosts for discovery and data collectionYou need to configure your hosts to support resource discovery and data collection.

ViPR SRM uses the md5sum utility to verify the checksum of files on the target hosts andcompare them to the files on the collector before pushing scripts and binaries to thehost. The md5sum binary must be installed on the hosts, and the PATH environmentvariable must contain the location to the md5sum binary.

Refer to the following sections for additional details about configuring your hosts:

l Windows host configuration for discovery and data collection on page 209

l Unix host configuration for discovery and data collection on page 221

l Configuring ESX hosts to collect PowerPath metrics on page 226

Guidelines for hostnames and IP addressesYou have to follow these guidelines to ensure a successful host discovery and datacollection.

l The host names are in Domain Name Server (DNS) format with fully qualified domainname (FQDN).

l IP addresses are registered with the appropriate domain name servers and resolve fora reverse DNS lookup.

Guidelines for SNIA libraries and HBA driversIn order to discover SNIA-qualified HBA-related information for all the host platforms youshould ensure the right versions of SNIA library, drivers and firmware are in place.

l Ensure you have EMC-supported host bus adapter (HBA) drivers and firmware. EMCViPR SRM Support Matrix provides information for the supported SNIA compliantversion of the HBA driver.

l HBA Model and the compatible driver versions qualified by EMC can also be verifiedon https://support.emc.com > Product and Support Tools > Elab InteroperabilityNavigator. The vendor websites also list the EMC compatible drivers

l The vendor-specific SNIA libraries must be installed on the target host.

l The HBA model number and part number should be verified before updating thehosts with SNIA libraries for HBA.

l You can install the SNIA library as part of HBA driver installation package or install thelatest version of HBAnywhere (for Emulex installations) or SAN Surfer (for Qlogicinstallation).To discover an HP-UX host with a multi-port Fibre Channel card, the packageCommonIO bundle 0812(Dec 2008) or later should be present on the host to obtainthe updated FC-SNIA file set. INQ is dependent on binaries from CommonIO bundle.

Windows host configuration for discovery and data collection

Software to preinstall on hosts

l Install Powershell 2.0 or later on Windows hosts. Powershell can be downloaded from http://support.microsoft.com/kb/968929/en-us. User should have permissions toexecute powershell scripts. To provide permissions to execute scripts, type onpowershell terminal: Set-ExecutionPolicy RemoteSigned


Preparing your hosts for discovery and data collection 209

https://support.emc.com

HTTP://SUPPORT.MICROSOFT.COM/KB/968929/EN-US

Preinstall the following software on hosts using Windows 2003:

l Fcinfo is required to fetch HBA information. fcinfo.exe can be downloaded fromhttp://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17530. Use the latest version of fcinfo and the defaultinstall location recommended by Windows.

l INQ 7.6.2 needs to be made available on the host. Platform specific INQ can bedownloaded from: ftp://ftp.emc.com/pub/symm3000/inquiry/v7.6.2/The downloaded platform specific binary should be renamed to inq and placed in anyone of the below specified locations:

n C:\inq.exen C:\temp\inq.exen C:\windows\Temp\nl_dwd\inq.exeINQ binary should have executable permissions on the host.

User permissions required to be configured in ViPR SRMThe user credentials required for successful host discovery would be as follows:

l Local administrator

l Domain user who is part of administrator's group

l Non-admin user

A non-admin user is identified by ViPR SRM as a service account user or domain user whois neither a part of the Administrator group or domain Administrators group.Types of discovery allowed by different privilege levels on page 210

Configurations to be performed on the hostHosts should be pre-configured with certain WSMAN settings. These settings are requiredto prepare Windows hosts for ViPR SRM discovery of objects using WinRM services.

Configure one of the following listeners:

l WinRM HTTP listener with the following configuration:

n Negotiate authentication mode set to true.

n AllowUnencrypted be set to true

n Firewall exception added for port 5985

l WinRM HTTPS listener with following configuration:

n Negotiate authentication mode set to true

n A certificate needs to be generated and placed in personal store.Generating a .pfx certificate on page 219

n Firewall exception added for port 5986.

These changes can be accomplished via two methods:

l Host Configuration utility - To be run on each host.Using the HostConfiguration Utility on page 214

l Group policy configuration - To be run on domain servers.Generating a .pfx certificate on page 219

Types of discovery allowed by different privilege levels

In this topic, the term "non-admin user" is a service account user or domain user who isnot part of the Administrators group on a Windows host.

The following table applies to Windows 2003, 2008, and 2012:



Table 7 Allowed discovery types

Data in reports Non-Adminuser

Local Admin user

Discovery of hostnames, IP

Supported Supported

MPIO/Powerpath Notsupported

Supported

Device Details/Attributes

Supported Supported

HBA Details Supported Supported

End to endreports - Maps

Supported Supported

Path Details &Connectivity

Supported Supported

File Systems toDisks

Notsupported

Supported

SystemPerformance

Supported Supported

DisksPerformance

Supported Supported

FileSystemUsage

Supported Supported

VolumeGroups Supported Supported

Internal & SANDisks

Notsupported

Supported

Chargeback byPhysical host

Supported Supported

Chargeback reports for non-admin users is supported on VMAX, VNX, VNXe and XtremIOarray devices. Refer to the release notes for any limitations on third-party array LUNsmasked to Windows hosts.

Customizing a WinRM URL prefix

Before you begin

EMC supports use of a custom WinRM URL prefix. You can change the URL prefix from thedefault "wsman" to any other, by using following command on the target host.

Procedure

1. Type the following command:

For Use

Non-SSL communication winrm set winrm/config/listener?Address=*+Transport=HTTP @ {URLPrefix="EMC"}


Windows host configuration for discovery and data collection 211

For Use

SSL-based communication winrm set winrm/config/listener?Address=*+Transport=HTTPS @{URLPrefix="EMC"}

2. In the default installation path /opt/APG/Collecting/Collector-Manager/Generic-RSC/conf), add and commit the following line in module.properties:apg.remote.shell.winrm.path=<URL prefix>"/EMC" is an example of a user-defined WinRm URL prefix.

Prerequisites for discovering a Windows host using non-admin user credentials

To prepare Windows hosts for discovery, you can configure privileges in these ways:

l Provide the option -user nonadmin as an input to the Host Configuration utility

l Manually

The following checklist summarizes the configuration changes required on Windowshosts:

1. WinRM configuration settings:

a. Adding a non-admin user to a group on page 212

b. Retrieving the SID of a non-admin user on page 213

c. Adding a non-admin SID to root SDDL on page 213

2. Enabling WMI permissions for the non-admin user on page 213

3. Restarting WinRM and WMI services on page 214

If you decide to use Host Configuration utility, the script performs these operations on thehost.

l For Windows 2003 hosts the Host configuration utility sets the WinRM changes. Youmust manually configure the WMI permissions.Enabling WMI permissions for the non-admin user on page 213

l For Windows 2008 and Windows 2012, the Host Configuration utility sets bothWinRM and WMI configurations.

These procedures are only available in ViPR SRM 3.5.1.

Adding a non-admin user to a group

Before you begin

l On a Windows 2003 host, the non-admin user should be part of the following groups:

n TelnetClients

n Performance Monitor Users

n Performance Log Users

n Distributed COM Users

On a Windows 2008/2012 host a non-admin user should be part of the following groups:

l Performance Monitor Users

l Performance Log Users

l Add non-admin users to the group WinRMRemoteWMIUsers__ . If that group does notexist, add the user to Distributed COM Users group.



Procedure

1. Go to Start.

2. Right-click Computer name and click Manage.

3. On the Computer management window, click Local Users and Groups.

4. Right-click the non-admin user and select Properties.

5. Select the MemberOf tab.

6. Click the Add button and key in the group name.

7. Click Ok, then click Apply.

8. Repeat these steps to add Performance Monitor Users, Performance Log Users andTelnetClients.

9. click Ok

Retrieving the SID of a non-admin user

Procedure

1. Run the command wmic useraccount get name,sid at a command prompt.

2. From the output of the command, capture the SID of the non-admin user.

Adding a non-admin SID to root SDDL

Procedure

1. Open a command prompt.

2. Type the following command to add the SID.

winrm set winrm/config/service @{RootSDDL="O:NSG:BAD:P(A;;GA;;;BA)(A;;GA;;;<non-admin-sid>)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)"}

Replace <non-admin-sid> in this command with the SID you obtained.

Enabling WMI permissions for the non-admin user

Procedure

1. Go to Start.

2. Right click Computer name and click Manage.

3. On the Computer management window, expand Services and Applications.

4. Select WMI Control.

5. Right click WMI Control and select properties.

6. Click Security.

7. Select Root and click the Security button.

8. Add the non-admin user (hostname\non-admin-username) and click ok.

9. Select the check boxes for Enable Account, Read Security, and Remote Enable.

10.Click Advanced > edit on non-admin user > Apply onto > This namespace andsubnamespaces.

11.Click Ok, click Apply, and click Ok.



Restarting WinRM and WMI services

Procedure

1. Go to Start > Run.

2. Type the command services.msc.

3. Right click Windows Remote Management and click start.

In case the services are already running, click restart.

Using the HostConfiguration Utility

The host configuration utility is packaged along with SolutionPack for Physical Hosts. It isavailable <APG Home Directory/Collecting/Remote Shell Collector/Generic-RSC/scripts/windows>The script verifies and performs the following actions:

l Ensures that the WINRM service is running

l Creates a listener port for accepting WS-MAN requests

l Adds firewall exceptions to open port 5985 as non-SSL and 5986 as SSL

l Sets Basic or Negotiate authentication mode, based on input argument to script (-authType <Authentication_type>), to true.

l Sets AllowUnencrypted to true.

l Sets MaxTimeout value to 300000 ms.

l Checks whether fcinfo package is present on the host, if Windows 2003

l Verifies the presence of INQ on the host and checks its version, if Windows 2003

Usage./hostconfig-srm.ps1 <-verify | -set | -set -force> [-authType<authentication_type>] [-ssl [-thumbprint <thumbprint_value>][-CN <certificate_hostname>]] [-user <username>][-help]

Table 8 Host Configuration utility command options

Options Description

-help Displays the help menu of the script.

-verify Verifies current settings on the Windows host.

-set Configures settings on the Windows host.

-set -force Changes configuration settings without promptingthe user. The -force option must be used with the -set option.

-authType authentication-type Provide this option to set the authentication type forWS-MAN to Negotiate or Basic.

-ssl Configures and verifies the SSL certificate specificsettings on the host for WS-MAN discovery with SSL.

-thumbprint thumbprint_value Configures the SSL certificate with the specifiedthumbprint_value on the host. This option must beused only with the -ssl option.



Table 8 Host Configuration utility command options (continued)

Options Description

-certhostname certificate_hostname Configures the SSL certificate with the specifiedcertificate_hostname value on the host. This optionmust be used only with the -ssl option.

-user username Configures the host to enable discovery using thenon-admin username provided.

Example 1 Examples

The following screens show how to perform actions with the Host Configuration Utility.

l Verify whether host is ready for discovery with HTTP using Negotiate authtype onWindows 2003:

Figure 32 Verify that the host is ready for discovery with HTTP

l Set Negotiate authtype for a successful discovery with HTTP on Windows 2008:



Example 1 Examples (continued)

Figure 33 Set Negotiate authtype

l Verify whether the host is ready for a successful discovery with HTTPS on Windows2008:

Figure 34 Verify that the host is ready for discovery with HTTPS

l Set Basic authtype for a successful discovery with HTTPS on Windows 2008, withoutprompting the user:



Example 1 Examples (continued)

Figure 35 Set Negotiate authtype

l Set non-admin user on Windows 2008:Figure 36 Set non-admin user

Configuring group policyUse a group policy if you do not want to set the configuration on each and every host(either manually or using a script). The group policy lets you apply a set of configurationsacross a set of hosts. You have to configure the group policy so that it can be appliedacross hosts as required.

Procedure

1. Right-click Computer and select Manage.

2. Go to Features > Group Policy Management > Forest Domain name > Domains > DomainName > Default Domain Policy.

3. Right-click Default Domain Policy and select Edit.

The group policy editor appears.

4. Select Default Domain Policy > Computer Configuration > Policies > AdministrativeTemplates > Windows Components > Windows Remote Management.

5. Modify the following parameters as required:



l Enable Allow automatic configuration of listeners.

l Enable Allow Negotiate Authentication (for domain user).

l Enable AllowUnencrypted.

l Add Windows Firewall exception for Port 5985 - HTTP

l Add Windows Firewall exception for Port 5986 - HTTPS

Note

HTTPS listener configuration is not possible from Group Policy.

Configuring firewall port exception using group policyUsing group policy, you have to configure firewall port exception if you are not usingdefault ports.

Procedure

1. Click Computer.

2. Go to Computer Configurations > Policies > Windows Settings > Windows Firewall withAdvanced Security > Inbound Rules

3. Create a new inbound rule

This enables the WinRM communication.

Updating group policyIf you update the group policy on a domain controller, the changes are reflected on thecomputers that are part of the domain in approximately 90-120 minutes. Use thisprocedure to force update the group policy on the member computers.

Procedure

1. You can use any of the options for force update of group policy:

Option Comment

Run the command gpupdate/force on allthe member computers.

This command results in a fetch operationfor the group policy

This command has to be run on allthe hosts and hence maybecumbersome.

Change the Group Policy Refresh Interval inthe Group Policy Management editor underComputer Configuration > AdministrativeTemplates > System > Group Policy

Minimum possible time is 7 minutes.

Reducing refresh interval is notrecommended as it increases theload on the network.

Generating a certificateWinRM HTTPS requires a local computer server authentication certificate or self-signedcertificate with a CN name installed on the host. The certificates should not have expiredor been revoked.

Perform the following to create certificates:



Procedure

1. Generate a .pfx certificate on page 219

2. Exporting the .pfx certificate on page 219

3. Importing the .pfx certificate on page 220

4. Generate a .cer file on page 220

5. Import the .cer file on page 220

Generating a .pfx certificate

You can generate the required certificate using any certificate generator. This proceduredemonstrates generating a certificate using makecert.

Procedure

1. From the command prompt, run C:\>makecert.exe -ss MY -srLocalMachine -n "CN=<certificatename>" -sky exchange -pe -a sha1 -eku 1.3.6.1.5.5.7.3.1This creates a certificate under the personal store. Use the following steps to verify thecertificate created using makecert.

2. On a Windows host, click Start > Run.

3. Type mmc and click OK.

The Console window appears.

4. Click File > Add/Remove Snap-in.

5. Select Certificates under Available snap-ins and click Add.

6. Select Computer account.

7. Click Finish.

8. Click OK in the Add or Remove snap ins window.

9. On the left pane, double click Certificates (Local Computer) > Personal > Certificates.

10.On the right pane double click the certificate listed.

11.Navigate to Details tab. Select Subject to get the CN Name and Thumbprint to get theThumbprint of the certificate.

Note the CN Name and Thumbprint value, which will be used later while creating aWSMAN listener for HTTPS.

Exporting the .pfx certificate

To use the same certificate on multiple hosts, the generated certificate has to beimported on other hosts.

Procedure



3. In the Console window, click Certificates (local Computer) > Personal > Certificates.

4. Double-click Certificates.

5. Under Details, click Copy to File.

6. In the Certificate Export Wizard select Yes, export the private key. and click Next.



7. Select Include all certificates in the certification path if possible and click Next.

8. Type a password for the private key.

This password is used when you import this certificate on other hosts.

9. Type a filename and save the .pfx file.

Importing the .pfx certificate

You have to import the .pfx on other hosts if you want to use the same certificate onmultiple hosts.

Before you begin

The .pfx certificate must be copied on the host where it is to be imported.

Procedure



3. In the Console window, click Certificates (Local Computer) > Personal > Certificates

4. Right-click and select All Tasks > Import.

5. In the browse window, select the .pfx certificate and click OK.

Generating a .cer file

The .cer file is created from a .pfx certificate with only a public key, which is used alongwith the private key for a successful handshake between the client and server.

Procedure

1. Go to Start > Run > mmc > Certificates (Local Computer) > Personal > Certificates

2. Double-click Certificates.

3. Under Details, click Copy to File.

4. Select No, do not export the private keys.

5. Selecting the Encoding type as DER or Base-64, and click Next.

6. Type a file name and click Save.

Importing a .cer file

You have to import the .cer file on the collector host to enable a successful handshakebetween the server and the client.

Procedure

1. Copy the .cer file on the collector host.

2. Log in to the collector.

3. Run the command /opt/APG/Java/Sun-JRE/6.0u45/bin/keytool -import -file <Public_Certificate_File> -keystore /opt/APG/Java/Sun-JRE/6.0u45/lib/security/cacerts -alias <Name>

The command prompts for keystore’s password. The default password is changeit.

A sample output returned by the command:

Owner: CN=<CN Name>Issuer: CN=Root AgencySerial number: 522200243f029a894c741bcb83d58a5d



Valid from: Tue Dec 10 11:59:03 EST 2013 until: Sat Dec 3118:59:59 EST 2039Certificate fingerprints:MD5: 99:2A:6E:DC:CD:D7:7E:7D:07:C3:E2:8A:8F:E1:BB:DDSHA1:17:29:F4:45:99:AE:DC:C5:08:C6:73:D4:CF:A6:BE:7E:79:48:50:76Signature algorithm name: SHA1withRSAVersion: 3Extensions:#1: ObjectId: 2.5.29.1 Criticality=false#2: ObjectId: 2.5.29.37 Criticality=falseExtendedKeyUsages [serverAuth]Trust this certificate? [no]: yes

Unix host configuration for discovery and data collectionViPR SRM supports discovery of several Unix variants. Each Unix environment requiressome configuration for ViPR SRM to collect data consistently.

Software to preinstall on Unix hosts for discoveryThe following software must be installed on Unix hosts for successful ViPR SRMdiscovery:

l INQ binary (an EMC command line executable). You can acquire INQ in the followingways:

n The SolutionPack for Physical Hosts is packaged with the INQ binary for each OSvariant. Users can allow ViPR SRM to push INQ to the user's HOME directory duringdiscovery from ViPR SRM. No action is needed from the user.

n Pre-install INQ at a user-specified location on the host at a location provided toViPR SRM during SolutionPack installation.INQ 7.6.2 needs to be made available on the host. Platform specific INQ can bedownloaded from: ftp://ftp.emc.com/pub/symm3000/inquiry/v7.6.2/The downloaded platform-specific binary should be renamed to inq and placed inany user-defined location. The location where the INQ binary is placed must beprovided to ViPR SRM during installation of the SolutionPack for Physical Hosts.

Note: The INQ binary should have executable permissions on the host.

l System Activity Report (SAR)This tool is used by ViPR SRM to collect performance metrics from hosts. Identify thecompatible version of SAR (corresponding to the OS) and install the software onhosts required for discovery. The SolutionPack for Physical Hosts does not packagethe SAR utility.

Prepare Unix hosts for discoveryUnix hosts can be discovered in the following ways:

l Password based discovery using a root or non-root user. You can configure non-rootusers via sudo or PowerBrokerConfiguring sudo for host discovery on page 222

Configuring PowerBroker for host discovery on page 223

l SSH public-private key pair based discoveryGenerating a public and private key pair on page 164


Unix host configuration for discovery and data collection 221

Note: Generic RSC Windows VMs can discover Unix hosts. Credentials for Unix hostsshould be configured in the Discovery Center UI. See Installing the SolutionPack onpage 227 for details about configuring hosts in discovery center.

Configuring sudo for host discoveryDue to security constraints, ViPR SRM must be able to discover Linux and UNIX hosts in adata center even with non-root credentials. SUDO is a tool on UNIX hosts that cantemporarily elevate a user’s credentials. Administrators can add specific commands inthe sudoers file to enable ViPR SRM to execute those commands and collect hostinformation.

Before you begin

Supported sudo versionsLinux Fedora distribution: sudo-1.8.6 and above

Other operating systems: any version of sudo

Procedure

1. Include the path of sudo command in the environment variable $PATH for the sudouser.

The variable $PATH can be set either in /etc/environment or /etc/default/login or any other OS specific file.

2. Include the paths of OS commands in the environment variable $PATH for sudo user.

By default, most of the command files have the following location: /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin


a. Log in as sudo user

b. Type which sudo.

4. Ensure that the sudoers file is available.

By default, the sudoers file is available in /etc or /opt/sfw/etc/ or /usr/local/etc/sudoers

5. Add the following line to the defaults section of the sudoers file:

Defaults !requiretty #for all usersor

Defaults : SRMADMIN !requiretty #for a specific user

6. For AIX hosts, if inq gives partial information, add the following line:

Defaults env_keep += "ODMDIR"7. Ensure that the sudo user has root privilege to run the following commands on a given

host.

Ensure the absolute path to the packages are provided in sudoers file.

It is recommended to use visudo to edit sudoers file.

Some packages are not installed by default.



AIXsar, inq, powermt, vxdisk, swap, kdb (kdb is only for VIO Clients)

Linuxsar, inq, powermt, vxdisk, dmidecode, lvdisplay, pvs, vgs, multipath

HPUXsar, inq, powermt, vxdisk, /opt/sfm/bin/CIMUtil (CIMUtil is allowed only in ViPRSRM 3.5.1 or higher)

Solarissar, inq, powermt, vxdisk, mpstat

Figure 37 Sample sudoers file for Linux OS

Configuring PowerBroker for host discoveryPowerBroker for UNIX & Linux allows system administrators to delegate UNIX and Linuxprivileges and authorization without disclosing passwords for root or other accounts.Administrators can add specific commands in the configuration/policy files to enableViPR SRM to execute those commands and collect host information.

Procedure

1. Include the path of the pbrun command in the environment variable $PATH for thepowerbroker submit/run host.

2. Include the paths of the OS commands in the environment variable $PATH for thepbrun user. By default, most of the command files have the following location:



/usr/local/:sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin


a. Log in to the submit/run host.

4. Type "which pbrun".

5. The configuration/policy files exist on the master host and they must include thepbrun user name and the associated commands for host discovery. The followingscreenshot displays the policy files for a configuration in which the master/submit/run host is on the same host:

In this screenshot, the RootUsers variable includes "cmguser", which is the submituser (the ViPR SRM user used for discovering the host details) and the RootProgsvariable includes the various commands required by ViPR SRM to discover the host.Note that the commands mentioned in the section about configuring sudo apply hereas well.

Generating a public and private key pairFor the SSH key method of discovering UNIX hosts, you must generate a valid public andprivate key pair. You can choose any key generation tool to generate a valid public andprivate key pair.

Before you begin

Before you begin host discovery, you must have a public key present on all the UNIXhosts that are to be discovered using the private key. You can create SSH keys in any Unixenvironment and import them onto the ViPR SRM collector. EMC recommends that you



create public-private SSH keys on ViPR SRM collectors (Linux VMs) where host discoverywill be initiated.

These steps describe the procedure to generate a public and private key pair for UNIXhosts using the ssh-keygen tool.

Note

The public key is to be added to the authorized_keys file on the target hosts intended fordiscovery and the private key is to be imported to the collector VMs where discovery istriggered.

Procedure

1. A Public-Private key can be generated using the following command:

ssh-keygen -t rsa -f <location_of_the_private_key/name_of_private_key_file> -N ""For example: ssh-keygen -t rsa -f /root/.ssh/id_rsa -N ””

2. Ensure that the public and private key pair that is generated has the followingpermissions:

l chmod 600 /root/.ssh/id_rsal chmod 644 /root/.ssh/id_rsa.pub

The private key file is id_rsa.

The public key file is id_rsa.pub.

3. To make the key pair functional, append the public key to <user's homedirectory>/.ssh/authorized_keys in the target UNIX host using the commandcat <location_of_the_public_key/name_of_public_key_file> >> /<user's homedirectory>/.ssh/authorized_keysFor example: cat /root/.ssh/id_rsa.pub >> /<user's homedirectory>/.ssh/authorized_keys

Next, import the private key to the Collector used for discovery.

Importing a private key into the Collector

Procedure

1. Place the generated private key in the RSC conf folder /opt/APG/Collecting/Remote-Shell-Collector/<instance_of_collector>/conf

2. Type chown apg:apg <private_key_file>

This command changes the owner.

The host is now ready for successful data collection.



Configuring SSH authenticationModify the /etc/ssh/sshd_config file on SLES 11 SP3 to allow successful sshauthentication.

Procedure

1. Change the following value to yes:

#PasswordAuthentication no <--- original#PasswordAuthentication yes <--- modified

Tunneled clear text passwords are disabled.

Configuring ESX hosts to collect PowerPath metricsProvides information about configuring ESX host to collect PowerPath metrics.

Before you begin

l Ensure that PowerPath/VE remote CLI (rpowermt) is installed on the host and enableperformance collection by running the rpowermt set perfmon={on[interval=<#seconds>] | off} host=HOST_FQDN command.The EMC ViPR SRM Support Matrix provides more information on supported PowerPathversions.

l Register ESX and enable performance for reporting.Refer to the Powerpath /Ve or Rtools documentation about how to register an ESXserver and enable performance.

l Configure the host where RTOOLS resides in generic-RSC based on the operatingsystem type (ESX-LINUX or ESX-Windows).

To collect PowerPath metrics, do the following:

Procedure

1. Create a lockbox.

2. Update host username and password in the lockbox.

The PowerPath/VE for VMware vSphere Installation and Administration Guideprovides detailed description of performing the above steps.

PowerPath reports can also be accessed from Explore View > Host > StorageConnectivity.

PowerPath reports are available for the SolutionPack for IBM LPAR.

Configuring hosts to collect PowerPath metricsProvides information about configuring host to collect PowerPath metrics.

To collect PowerPath metrics, do the following:

Procedure

1. Install PowerPath CLI (powermt) on the host.

2. Enable performance collection by running the powermt set perfmon={on[interval=<#seconds>] | off} command.



Note

The EMC ViPR SRM Support Matrix provides more information on supported PowerPathversions.


Before you begin


l For non-admin users, the SolutionPack for Physical Hosts will report anauthentication error during discovery if the user is not part of the remote admin usersgroup. To avoid this issue, add non-admin users to the WinrMRemoteWMIUsers__group. If that group does not exist, add non-admin users to the DCOM group on theWindows host.

The steps below assume a typical four server deployment: Primary Backend, AdditionalBackend, Collector, and Front End.

Procedure






6. Click Install.




9. Click Next.


10.If desired, select Enable the Host PowerPath Alerts.

11.Click Next.



13.Click Next.

The window displays script settings.

14.Select the performance metrics that you want to collect. Click Use advanced settingsto configure the absolute paths of the binaries.

15.Click Install.





18.Click Host configuration.

These steps describe how to add hosts individually. For information about usingdiscovery groups to use the same credentials to discover multiple hosts, refer to the"Adding new devices" topic in the online help.


20.Select the server and collector instance where you want to store the configurationdetails for this device.

21.Enter the hostname and OS type.

22.From the Authentication Type drop-down menu, select:

l Password based if you are using password based authentication.

l Public key based if you are using key-based authentication.

23.Provide the username (root or sudo user).

24.If you are using password based authentication, provide the password for the host.

25.If you are using key-based authentication, provide the absolute location of the privatekey:

/opt/APG/Collecting/Remote-Shell-Collector/<instance_of_collector>/conf/<Name of private key>

26.Type the network port.


28.Click OK.

29.Click Save.

30.Add a new device for each host that will be discovered.

Adding hosts as part of groups in Discovery CenterLearn how to add hosts as part of groups in Discovery Center.

Procedure

1. From Centralized Management, click Discovery Center > Discovery Center Backends.

2. Select the Backend server.

3. Click Register.

4. Select the server you want to use for discovering the hosts.

5. Click OK.

6. Click Discovery Center > Devices Management.

7. Click Host Configuration.

8. Click the Discovery Groups tab.

9. Click Add new Discovery group.

10.Provide a name for the group and click OK.

11.Click the newly created group.

12.Under Credentials, click Add new entry.

13.Type the username.

14.Select the authentication type.



15.If you are using password authentication, provide the password and click OK.

16.If you are using key-based authentication, provide the absolute location of the privatekey and click OK.

17.Repeat the previous five steps to add as many username/password (or key)combinations as you would like.

18.Under Hostname or IP address, click Add new entry.

19.Provide the Hostname/IP Address of the host and Network Port and click OK.

20.Repeat the previous two steps to add as many hosts as you would like.

21.Click Save.

22.Click the Collected Devices tab.

23.Click Discover.

24.Select the Discovery group and Discovery Mode and click OK.

The progress bar is displayed above the Collected Devices tab.

25.When the progress bar is gone, click Discovery Results.

26.Click the group name that you added.

27.Under the group name, you can see the status of all the hosts that you added.

28.Click Import to Collected Devices.

29.Merge the devices if you want to retain older hosts that were added previously.

30.Click OK.

31.Select the action and click Continue.

32.Click Save.

All the hosts have been added to discovery

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

SolutionPack reconfiguration

If you want to change the answers that were provided during the SolutionPackinstallation, you can change them by reconfiguring the SolutionPack.

Procedure


2. Under Centralized Management, click SolutionPacks > IndependentSolutionPackBlocks and select the required instance.

The SolutionPack Reconfiguration dialog box appears.

3. Change the configuration as desired.



SolutionPack reconfiguration 229

LimitationsLearn about the limitations that apply to the SolutionPack for Physical Hosts.

l For non-admin users on Windows hosts, if the array connected to the host is notdiscovered, the report at All > Explore > Hosts > hostname > Device Summary > hostname> Path Details & Storage Connectivity > Path Details will show the name of the HBA inthe Host Device column.

l If the array and host are discovered, the report will show the name of the HBA in theHost Device column after initial discovery of the host. After 36 hours, the row showingthe HBA name for Host Device will not be shown in the report.

l After upgrading to ViPR SRM 3.6, each Windows host under the Physical Host reportsis listed twice (once in uppercase and once in lowercase). After 36 hours, only thelowercase name is listed. Historical trends for performance and capacity metrics ofthe host device reported with uppercase hostname will not be available after upgradeto 3.6.1. In addition, the metrics associated with the uppercase hostname willbecome inactive, and they will remain inactive in the database until it is cleaned upby the database scripts.

l This SolutionPack does not identify LUNs from the Hitachi AMS200 array.

l Due to the unavailability of WWN using in-band SCSI mechanisms accessible to thehosts, the software cannot match the LUNs associated with an array to the disks fromthe hosts.

l On a Linux host, when sudo is not configured properly for commands like"dmidecode," or "dmidecode" does not return proper output, the property keys andvalues fetched from the host by Remote Shell Collector are swapped and the PropertyStore is corrupted. Refer to Knowledgebase article 000198621 for complete details.



CHAPTER 34

SolutionPack for Storage Compliance

l Overview............................................................................................................. 232l Technical specifications...................................................................................... 232l Where to find the latest SolutionPack software....................................................233l Installing the SolutionPack..................................................................................233

SolutionPack for Storage Compliance 231

OverviewLearn how to install and configure the SolutionPack for Storage Compliance.

The SolutionPack for Storage Compliance allows users to manage compliance policiesand rules and perform ESM matching. It also generates breach, track configurationchanges, and policy reports. This enables the identification of any deviation fromconfiguration best practices, including items that do not comply with the EMC ViPR SRMRelease Notes. The compliance reports can be found under Operations > StorageCompliance. The Policy & Rule Management and ESM management screen can belaunched by clicking on the Storage Compliance link in the Administration screen.

Figure 38 SolutionPack for Storage Compliance


Main reportsBreach Report

Track Configuration Changes

View Policies







Before you begin

l EMC M&R will use SSH and a user account.


l If you are installing on a Windows host, stop the process jucheck.exe. This is aJava JRE update validator and uses the same port as the SolutionPack.

l Do not install multiple instances of the Storage Compliance Backend because thesame port would be used for each installation. This will lead to service startup failure.

l Alerting backend service should be available during installation; otherwise alertingdefinition will not be created. The SolutionPack for Storage Compliance createsalerting definition for notifying mentioned users with email alerts for breaches/violations.

l Though the Compliance service comes up immediately, do not run ESM rules as theSolutionPack installation also populates the database with ESM data, for ESM rulevalidation, which takes some time to get the database populated (approximately 3-5minutes).

Procedure






6. Click Install.




9. Click Next.

The window displays compliance notification details.

10.Select an item in Breach Notification Details. If you select Add a new BreachNotification Details, select an instance to receive breach notifications.


Where to find the latest SolutionPack software 233



11.Click Next.

12.From Frontend Web service, select the Frontend host details.

13.Select a Topology Service. To add a new gateway configuration, select Add a newTopology Service.

14.Select a configuration for Breach Notification Details.

Reuse the answers if another solution pack is using Alerting backend. Otherwisecreate a new configuration by selecting Add a new Breach Notification Details. In theAlerting Backend hostname or IP address, type the Primary Backend host. Type 2010as the port.

15.Select a configuration for Alert Consolidation Details.

Reuse the answers if another solution pack is using Alert Consolidation Details.Otherwise create a new configuration by selecting Add a new Alert ConsolidationDetails. In the Alert Consolidation hostname field, type the Primary Backend host.Type 2040 as the port.

If SOM RCA installation needs to be done, the alert consolidation configuration isrequired. For more details, refer to the "How to" article for SOM.

16.Click Next.

17.From Administration Web-Service Instance, select Default.

18.In Compliance Backend Host, for 4 VM installations, enter the Primary Backend host.

19.Click Next.

20.Click Install.

21.After Install of all the compliance components, click Ok.

After installation is complete, you need to restart the Tomcat for Compliance Frontendto point to the configured Backend. If the Web Service password is changed, then theCompliance Backend block needs to be reconfigured.



CHAPTER 35

SolutionPack for VI VirtualWisdom

l Overview............................................................................................................. 236l Technical specifications...................................................................................... 236l Preparing VI VirtualWisdom.................................................................................237l Installing the SolutionPack..................................................................................238

SolutionPack for VI VirtualWisdom 235

OverviewLearn how to install and configure the SolutionPack for VI VirtualWisdom. TheSolutionPack for VI VirtualWisdom accesses key performance and availability metrics,including individual transactional performance from host to LUN, host to LUN overview,link level aggregated metrics for throughput and errors, and a link level inventory forimpact assessment.

Figure 39 SolutionPack for VI VirtualWisdom


Main reports

PerformanceRead and write exchange completion time, number of completed reads and writes

HealthLink errors (LOS, LOSync, BadEOF, CVErrors, LinkResets, CRCErrors) SCSI Errors(Aborts, BadStatusFrames)

UtilisationAggregate storage link utilisation, individual initiator to LUN utilisation

Optional metricsRead and writes frame count, read and write payload sizes




Preparing VI VirtualWisdomIdentify the information required to support resource discovery and data collection beforeinstalling the SolutionPack for VI VirtualWisdom and perform any necessary pre-configuration.

ViPR SRMcollects VirtualWisdom data using proxy software installed on theVirtualWisdom Portal Server. Download and install the proxy software on theVirtualWisdom Portal Server

Procedure

1. Obtain the proxy installation package using Virtual Instruments customer credentialsfrom their SFDC portal, or from ftp.virtualinstruments.com. The package is located inthe CURRENT directory.

2. Copy the installation package to the VirtualWisdom server.

3. Unzip the package into a suitable temporary directory.

4. Stop the VirtualWisdom service.

5. Open a command prompt.

Note

You may need to run as Administrator to allow files to be copied.

6. Navigate to the temporary directory where the proxy is unzipped and run theinstall.bat script.

7. Enter the VirtualWisdom installation path.

8. Restart the VirtualWisdom service.

Results

You do not need to perform any addtional configuration of the proxy which runs as part ofthe standard VirtualWisdom.

After you finish

Create a VirtualWisdom user account dedicated for access by the SolutionPack for VIVirtualWisdom. When you install the SolutionPack, you will provide these credentialswhich are then stored on the Collector host in:APG/Collecting/XML-Collector/vi-virtualwisdom/conf/VI-proxyRequest.xml.

Connecting to multiple VirtualWisdom Portal ServersIf you have more than one VirtualWisdom Portal Server, you can combine data frommultiple Portal Servers. The data will populate the same reports.

Before you begin

Install and configure the proxy software on each VirtualWisdom Portal Server.

Use this configuration to collect the same metrics from all Portal Servers using the samefrequency (poll cycle) and credentials. Each host will be polled in the sequence youspecify in the configuration file.

Procedure

1. On the Collector host, navigate to APG/Collecting/XML-Collector/vi-virtualwisdom and open the VI-collector.xml file.


Preparing VI VirtualWisdom 237

2. Add one or more Portal Server hosts to the configuration file by typing the additionalhost IP addresses.

<input>http://(host):8080/Proxy</input>

<host>ip_address</host> <host>ip_address</host> <parameter name="connect-type"> <value>any</value> </parameter>

3. If the VirtualWisdom WebServices port numbers are different for each Portal Serverhost, you can remove the port number from the <input> line and append the uniqueport numbers to the host address. For example:

<input>http://(host)/Proxy</input>

<host>ip_address:port</host> <host>ip_address:port</host> <parameter name="connect-type"> <value>any</value> </parameter>

4. Restart the VirtualWisdom collector by restarting its Collector Manager. Use one of thefollowing methods:

l APG/bin/manage-modules service restart collector-manager<instance-name>

l Start/stop the collector manager from Centralised Management.


Before you begin


Procedure






6. Click Install.




9. Click Next.









13.In theServer Name field, type the VirtualWisdom Portal Server host.

14.In theServer Port field, type the port for the webservices proxy. The default is 8080.The value is configured in the virtualwisdom.properties file in theVirtualWisdom installation directory on the VirtualWisdom Portal Server.

15.In theUsername and Password fields, type the credentials used for authenticationwith the proxy.

16.Click Enable advanced settings to configure polling and collection settings.

17.Click Next.



19.Click Install.






CHAPTER 36

SolutionPack for VMware vCenter

l Overview............................................................................................................. 242l Technical specifications...................................................................................... 242l Configuring the SolutionPack to collect Powerpath data...................................... 242l Installing this SolutionPack.................................................................................243l Post-install requirements.................................................................................... 245l Limitations..........................................................................................................246

SolutionPack for VMware vCenter 241

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

The SolutionPack for VMware vCenter generates real-time and historical reports that helpyou understand VMware performance for VMware Hosts, Virtual Machines, virtualnetworks and DataStores.

Figure 40 SolutionPack for VMware vCenter

Technical specificationsMain reportsvCenter datacenter overview

Detailed datastore information

Detailed Virtual Machines, both running and offline


Configuring the SolutionPack to collect Powerpath dataThis 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 RToolscommand scripts to the RTools host to collect PowerPath data directly from the ESXiservers.



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 ifthe 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. Discoverit through the SolutionPack for Physical Hosts using the ESX Linux or the ESX Windowshost type. Choose the Linux or Windows type appropriate for the RTools host so thatthe 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 discoveryhosts. You must enable "PasswordAuthentication" and restart sshd service on thehost.

lglah196:~/.ssh # grep Password /etc/ssh/sshd_config#PasswordAuthentication no #PermitEmptyPasswords nolglah196:~ # /etc/init.d/sshd restart Shutting down SSHdaemon done Starting SSH daemon donelglah196:~ #

Installing this SolutionPack

Before you begin


Procedure






6. Click Install.




9. Click Next.


10.Click Next.



Installing this SolutionPack 243

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.













20.Optionally, select Do you want to configure advanced settings to configure the metriccollection level, polling intervals, collection thread settings, and the re-synch interval.

a. In Metric Collect Level, select the level of metrics you want the SolutionPack tocollect per VMware collector block. The Metric Collect Level is an internal ViPR SRMsetting 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 allmetrics related to disks and memory.

Collect-Level 3 collects all supported metrics, which includes metrics collectedunder Collect-Level 1 and Collect-Level 2.

b. In Polling interval for VMware vCenter collection, select a polling interval.

c. In Polling interval for VM files only, select a polling interval.



d. In Number of collecting threads, enter the number of collection threads.

e. In Number of collecting threads for VM files, enter the number of collectionthreads.

f. 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 theDatabase hostname or IP address field.

23.Click Next.


24.Click Next.

25.Select Collect performance metrics for PowerPath Bus to collect performance metricsfor all the logical Bus managed by PowerPath agent.

26.Select Collect performance metrics for PowerPath LUNs to collect performancemetrics for all the logical devices managed by PowerPath agent.

27.Select Collect PowerPath range-bound performance metrics to collect range-boundperformance metrics. Selecting this option increases metric count significantly. Besure to correctly size your application before enabling this option.

28.Select Do you want to configure advanced settings to set the absolute path locationof the sudo and pbrun binaries.

29.Click Install.



32.Click VMware vCenter.



35.From Instance, select the instance of the vmware-vcenter-collect where the device willbe dispatched.

36.In Hostname or IP address, type the vCenter service host. Enter the Username andPassword used to poll vCenter.

37.Click Ok.

38.Click Save.

Post-install requirementsPerform these operations after the installation is complete.

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

Procedure

1. In the LunMappingDetection.pl script, setwant_powerpath_lun_performance=1.

By default, this flag is set to zero.


Post-install requirements 245

2. To enable the PowerPath LUN or Path performance data collection on Windows:

a. Navigate to the C:\Program Files\APG\Collecting\Remote-Shell-Collector\<Instance Name>\scripts\windows directory.

b. In the LunMappingDetection.ps1 script, setpowerPathPerformanceCollection=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.

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



CHAPTER 37

Troubleshooting

l Confirming report creation...................................................................................248l Troubleshooting ................................................................................................. 248

Troubleshooting 247



Procedure



Results


Troubleshooting


l What to do if data does not appear in any reports on page 248

l What to do if data does not appear in some reports on page 205


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 intothe 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 thereports, continue to the next step.



Before you begin


Procedure




4. Click Database.


6. Click Run Now.


Troubleshooting


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 thereports, continue to step 2.

2. Search for the metric in the database.


Searching for metrics in the databaseYou can verify that a metric is being collected and used for reporting when you searchand 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 selectthe properties to display for the metric.

For example, to list up to 100 results of the Capacity metric with the properties ofdevice and IP, type name=='Capacity' in the Filter field, 100 in the Maximum resultsfield, 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 beingcollected.


Procedure







Troubleshooting

What to do if data does not appear in some reports 249

Troubleshooting

Documents

SolutionPack Installation Guide - Dell EMC · PDF fileConfiguring sudo for VIO Server and VIO Client host discovery.....161 ... EMC ViPR SRM 3.6.2 SolutionPack Installation Guide 11