SCOM Integration for vnx & VMAX monitoring

Version: 1.0Date: 7/1/2014

Integration of VNX & VMAX with SCOM for Monitoring

Prepared for:PwC

Prepared by:

Anil Kumar BetaPwC | TCS Project Services - Infrastructure Engineering TeamOffice: +1 814 566 4595Email: anil.k.beta@us.pwc.comPricewaterhouseCoopers LLP4040 W Boy Scout Blvd, Tampa FL 33607http://www.pwc.com/us

July 1, 2014[SCOM Integration for vnx & VMAX monitoring]

July 1, 2014[SCOM Integration for vnx & VMAX monitoring

Page 2 of 13EMC ConfidentialEMC Global PS

Copyright

Document HistoryVersionDateAuthorSummary of Changes

1.07/1/2014Chandra Sekhar ReddyInitial release.

Contents1.Purpose of Document32.Details3

Purpose of Document

The document lists out the details of configuration and steps involved in integrating SCOM with VNX for monitoring.

Details Description:

EMC Symmetrix line of products as well as Clariion storage systems can be monitored by Microsoft System Center Family product called as System Center Operations Manager (read as SCOM).

EMC Storage Integrator suite (ESI) version 3.1 is available to manage storage systems.ESI for Windows Suite is a set of tools for Microsoft Windows. The suite includes: ESI for Windows, ESI PowerShell Toolkit, ESI Service, ESI Service PowerShell Toolkit, ESI Adapters and ESI SCOM Management Packs.

The ESI Service and the ESI SCOM Management Packs work in conjunction with Microsoft System Center Operations Manager for centralized discovery and monitoring of all supported EMC storage systems and storage-system components. The ESI Service and ESI SCOM Management Packs support the same VMAX family, VNX, and CX4 series of storage systems that are supported in ESI. The ESI SCOM Management Packs also support Symmetrix DMX-4 storage systems.

Getting Started:

ESI Service: is the communications link between ESI and the ESI SCOM Management Packs. You can use the ESI Service to view and report on all registered EMC storage systems and storage-system components connected to the ESI host system. ESI Service then pushes this data to SCOM. You can also use the ESI Service as a stand-alone tool without SCOM to collect, view, and report this same system data.

ESI SCOM Management Packs:

The ESI SCOM Management Packs enable you to manage EMC storage systems with SCOM by providing consolidated and simplified dashboard views of storage entities. These views enable you to: Discover and monitor the health status and events of your EMC storage systems and system components in SCOM. Receive alerts for any possible problems with disk drives, power supplies, storage pools, and other types of physical and logical components in SCOMEnvironment & System pre-requisites:

ESI system prerequisites:1. To have a windows server 2008 64 bit build VM.2. To have .NET Framework 3.5 on the ESI controller.3. To have Microsoft Management Console (MMC) 3.0.4. Enable firewall exceptions for vds.exe,vdsldr.exe and svchost.exe on the ESI controllers and ESI controlees .5. To have Microsoft PowerShell 3.0 or 2.0.6. To have latest version of EMC Power Path.7. To ensure that ESI is installed and runs in a domain user login session with administrative privileges for the controller host.Storage System pre-requisites:

Storage systemRequired software versions

Symmetrix VMAX storage seriesEnginuity release level 5876.159.102 and EMC Solutions Enabler 7.6.1.12 or later with EMC SMI-S Provider version 4.6.1.3 or later

VNX5100, VNX5200, VNX5300, VNX5400, VNX5500, VNX5600, VNX5700, VNX5800, VNX7500, VNX7600, and VNX8000Block 05.31, 05.32, or 05.33.000.5.015File 7.0.12.0, 7.1.55.3, or 8.1.0.15

CLARiiON CX4-120C, CLARiiON CX4-240C, CLARiiON CX4-480C, and CLARiiON CX4-960CFLARE 04.30

VNX Adapter prerequisite:The VNX Adapter uses a Secure Shell (SSH) network connection to communicate with VNX file storage systems. Confirm that the standard SSH port 22 is open on the ESI host. If it is not, the connection will fail.VMAX Adapter system prerequisites:

The ESI Symmetrix VMAX Adapter is installed by default with ESI. It enables storage administrators to create, provision, and manage VMAX storage with ESI. This VMAX Adapter is based on the Solutions Enabler Storage Management Initiative - Specification (SMI-S) provider. It supports all VMAX storage systems that are supported in ESI. Pre-requisite is to have the latest version of SMI-S installed and run on a management server that is separate from all ESI hosts and storage systems.

ESI Service and ESI SCOM Management Packs prerequisites:ESI Service must be installed and set up on the ESI host system. The ESI Service has the same prerequisites as the ESI host controller. SCOM Management Servers must have Microsoft SCOM 2012 R2, 2012 SP2, 2007 R2, or 2007 SP1 installed.

Setting up SMI-S:

After installing the latest version of EMC SMI-S Provider, use VMAX to create two or more gatekeeper devices and mask the gatekeepers to the SMI-S server that is hosting the SMI-S provider. Gatekeepers are required for accessing and issuing management commands.

Installation:ESI 3.1 suite is available in a zip folder on EMC Support site of size 123 MB with below contents:

Locate and double click the appropriate installer file as per the server build and complete the installation wizard. Some options, including the ESI Service and ESI Exchange HA Extension, are not selected by default. You can click Change to change the installable path to a drive other than the default drive.

Adding Storage Systems:

To add a storage system to ESI:

1. In the left pane of the ESI window, select EMC Storage Integrator or Storage Systems.2. In the Actions pane, click Add Storage System.3. Set the following details for the storage system:

FieldDescription

System TypeType of storage system to add

Friendly NameShort name for the storage system that is unique across different storage systems

For block storage systems, such as VNX-block:

FieldDescription

UsernameUsername for the storage system

PasswordPassword for the storage system

SPA's IP AddressIP address of SP A

SPB's IP AddressIP address of SP B

Port Number (VNX-Block or CX4)Control station port number. The default port is automatically selected. If the field is empty, you can leave it blank to use the default port.

For VNX storage systems with both block and file storage:

FieldDescription

BlockUsernameBlock username of the storage system

BlockPasswordBlock password of the storage system

SPAs IP addressIP address of SP A

SPBs IP addressIP address of SP B

Block Port NumberBlock port number

CIFSUsernameControl station username for the CIFS storage system

CIFSPasswordControl station password for the CIFS storage system

CIFS IP AddressIP address of the control station.

CIFS Port NumberControl station port number. The default port is automatically selected. If the field is empty, you can leave it blank to use the default port.

For VMAX storage systems:

FieldDescription

Array serial numberSerial number of the array

SMI provider hostHostname or IP address of the SMI-S provider

SMI provider portIP port of the SMI-S provider. Or you can accept the default port 5988 for HTTP or 5989 for HTTPS.

Use secured connectionUse a secure connection to the SMI-S provider

Use Windows AuthenticationUse Microsoft Windows authentication

Username and PasswordNot used and can be skippedOr type the username and password for the SMI-S provider

Connection timeout (seconds)Time limit for a connection to connect to the SMI-S provider

Operation timeout (seconds)Time limit for an operation to be completed

Ignore server certificate name validationBypass security certificate name validation

Ignore server certificate name validationBypass security certificate name validation

4. Click Test Connection to test the connection before adding it.5. Click Add. The storage system appears in the Available Systems list in the center pane.

ESI Service and ESI SCOM Management Packs:

Installing ESI Service:ESI is distributed as a Zip file that is available for download from EMC Online Support. During the ESI installation, you can choose to install the ESI Service on the same ESI host system. When you install the ESI Service, the ESI Service PowerShell Toolkit is also installed on the ESI host system.Installing and importing the ESI SCOM Management Packs:

The management packs must be installed on the SCOM Management Group that is connected to the ESI SCOM monitoring agents. To install and import the management packs:1. On the SCOM Management Group server that is connected to the ESI SCOM agents, download the ESI Zip file.2. In the ESI Zip file, locate and double-click the ESI SCOM ManagementPacks.*.Setup file3. The management pack files are installed by default to the C:\Program Files (x86)\EMC\Management Packs folder.4. Import each ESI management pack file in SCOM; however, if you have previously imported the management packs and are performing an update, do not import the EMC.SI.Customization.xml file.

After the ESI SCOM management packs have been imported, do the following:1. Confirm the connection between the SCOM agents and ESI Service:On the SCOM Agent computer, open this link: https://:/esi/console/graph/Entities?class=StorageSystem. Replace and with the applicable values.2. Confirm that the load time displayed at the bottom of the page is less than one second. Repeat this step a few times for consistent results.

Setting up the EMC SI Run As profiles:

Setting up the ESI SI Monitoring Account: For the EMC SI Monitoring Account Run As profile, create and set up the Run As profile for each SCOM agent that needs to connect to each ESI Service.To set up the EMC SI Monitoring Account Run As profile for each SCOM agent that is using Windows Authentication to connect to each ESI Service:1. Create a Windows Run As Account for the Windows account that is used in the Monitoring Role for the ESI Service.2. In the EMC SI Monitoring Account, assign the Windows Run As Account to the related SCOM agent that will connect to the ESI Service.Setting up the EMC SI Service Monitoring Account: Set up an EMC SI Service (ESI Service) Monitoring Account Run As profile to monitor the EMC SI Windows Service. The SCOM account that monitors the ESI Service must have the Allow log on locally enabled, be able to read the Application Event log, and use WMI (Windows Management Instrumentation) to query the status of the service.

Setting up the SCOM Agent Registry:

Before enabling the discovery of ESI Service, change the Value to Decimal 5120 in the following registry key for each SCOM agent that will monitor EMC storage systems:

Subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HealthService\ParametersType: REG_DWORDName: Persistence Version Store MaximumValue: Number of 16-kilobyte pages (change to Decimal 5120)Configure EMC Management PACK on SCOM SERVER:Setting up ESI Service discovery overrides:

Setting up the HTTP proxy: If the SCOM agent must connect to the ESI Service through a web proxy server, provide the following information for the Proxy Server and Bypass List overrides in the EMC SI Service Discovery for each related SCOM agent: Proxy server: proxy server string. For example:proxy_server:80 Bypass List: domain bypass list string. For example:the following represents that the discovery can bypass the proxy server when the host name ends with .emc.com:*.emc.com If the overrides above are not set, then the proxy settings are obtained from the registry. This assumes the proxy configuration tool, Proxycfg.exe has been run. If Proxycfg.exe has not been run, then the ESI Service can be accessed directly.

Changing the HTTPS to HTTP override:The SCOM agent will always try to connect to the ESI Service by using an HTTPS connection. By default, if the HTTPS connection fails, the SCOM agent cannot communicate with the ESI Service.If you want the ESI Service to connect with an HTTP connection instead of an HTTPS connection, you can set the HTTPS to HTTP Override to True for the ESI Service connection.

Note: If you set up the override, secure the SCOM agents. With this override, SCOM sends the username and password as text, which can be hijacked. This option is a data security risk.

To change the HTTPS to HTTP override:1. Open the SCOM Operations Console and connect to the SCOM Management Group.2. From the menu bar, select Go > Authoring.3. In the left pane, select Object Discoveries.4. Locate and double-click the EMC SI Service Discovery.5. Open the Overrides properties and select to Override > For a specific object of class: Windows Computer.6. In the Select Object dialog box, select the SCOM proxy agent that you want to connect to the ESI Service, and then click OK. The Override Properties page appears.7. Click the Override checkbox for the HTTPS to HTTP Fallback override to enable it.8. Change the value of the Override Value field to True and click OK.9. Click Close to save the change.

Setting up Setting up the ESI Service Host override:After changing the registry key value for each SCOM agent and setting up any applicable overrides, to set up the ESI Service Host override for each SCOM agent:1. Open the SCOM Operations Console and connect to the SCOM Management Group.2. From the menu bar, select Go > Authoring.3. In the left pane, select Object Discoveries.4. Locate and double-click EMC SI Service Discovery and the EMC SI Service Discovery Properties page appears.5. Open the Overrides properties and select Override > For a specific object of class: Windows Computer.

6. In the Select Object dialog box, select the SCOM proxy agent that you want to connect to the ESI Service from the list and click OK. The Override Properties page appears.7. Change the override value for the ESI Service Host parameter to the IP address of the computer hosting the ESI Service.8. If the default port number of 54500 or 54501 for the ESI Service has been changed, change the port parameter default value to the correct port number.9. In the Select destination management pack list box, select the EMC Storage Integrator Customizations management pack.10. Click Apply and confirm the changed values.11. Click OK.12. After completing this setup, export and save a copy of the EMC.SI.Customization.xml file as a backup of your customization values.

Enabling the ESI Service discovery:After setting up any applicable overrides and the ESI Service Host override, you must then enable the discovery of the ESI Service for each SCOM agent:1. Open the SCOM Operations Console and connect to the SCOM Management Group.2. From the menu bar, select Go > Authoring.3. In the left pane, select Object Discoveries.4. Locate and double-click EMC SI Service Discovery and the EMC SI Service Discovery Properties page appears.5. Open the Overrides properties and select to Override > For a specific object of class: Windows Computer.6. In the Select Object dialog box, select the SCOM proxy agent that you want to connect to the ESI Service from the list and click OK. The Override Properties page appears.7. Confirm the Enabled parameter name override is selected and that the override value is set to True.8. In the Select destination management pack list box, select the EMC Storage Integrator Customizations management pack.9. Click Apply and confirm the changed values.10. Click OK.11. After completing this setup, export and save a copy of the EMC.SI.Customization.xml file as a backup of your customization values.