emc eccoa 52 ug

Portfolio Capability Engineering - Storage

Capability User Guide On Alert

EMC OnAlert User Guide for Managed Storage Services (MSS)

Enterprise Solution Template (EST)

Template Control: Capability User Guide Template Version 1.1 -- Approval Date 15 October, 2004 Saved 23 March, 2005 EDS is an equal opportunity employer and values the diversity of its people. Page 1 of 9 Copyright 2004, Electronic Data Systems Corporation. All rights reserved. EDS is a registered mark and the EDS logo is a trademark of Electronic Data Systems Corporation. D:\MyDocuments\EIT\MSS\MSS20042\WorkingDocs\EMC ECCOA 52 UG.doc

Portfolio Capability Engineering - StorageCapability User Guide OnAlert

Table of Contents

1 Document Control.......................................................................................3 1.1 Purpose and Audience ................................................................................................. 3 1.2 Distribution List ............................................................................................................. 3 1.3 Reviewers ..................................................................................................................... 3 1.4 Amendment Record...................................................................................................... 3 1.5 Terminology.................................................................................................................. 3 1.6 Related Documentation ................................................................................................ 4 1.7 References ................................................................................................................... 4

2 Roles and Responsibilities.........................................................................5

3 User Procedures .........................................................................................5 3.1 OnAlert Implementation................................................................................................ 5

3.1.1 General............................................................................................................. 5 3.1.2 Solutions and Restrictions................................................................................ 6 3.1.3 Examples.......................................................................................................... 8

Saved 23 March, 2005 Copyright 2004, Electronic Data Systems Corporation. All rights reserved. Page 2 of 9 D:\MyDocuments\EIT\MSS\MSS20042\WorkingDocs\EMC ECCOA 52 UG.doc


1 Document Control

1.1 Purpose and Audience The Capability User Guide for EMC OnAlert, including CLARalert, is intended to demonstrate typical implementations, with a focus on the limitations of OnAlert interactions with the various elements of the OnAlert family. In general, though, each unique OnAlert application is not able to co-exist on a host PC with another OnAlert or CLARalert instance. At a minimum, this will require each site or implementation to provide separate host PCs for each platform-specific copy of OnAlert or CLARalert that is to be installed.

This document is intended to address configuration limitations only, and is not intended to address installation information. For installation and other related information, refer to the pertinent EMC OnAlert or EMC CLARalert installation guide.

1.2 Distribution List Name Role Representing

Tim Bowers Project Leader Infrastructure Portfolio Michelle Rasteiro Support US Delivery Peter Koster Support EMEA Delivery Ken Mclean Support AP Delivery Alan Shockley Director Portfolio Capability Engineering

1.3 Reviewers Name Representing Date Status

Joel Motzny EDS PCE Storage Concur Michelle Rastiero EDS Service Delivery Concur Mark Cornell EDS Service Delivery Concur Ted McGavin EMC Support Concur Ray Wright EDS GATA Concur

1.4 Amendment Record Version Date Status Author Comment

2004.2.1 03/23/2005 Delivery Ready

Jeffry A. Smith Initial release of On Alert User Guide

1.5 Terminology Term Definition

BCV Business Continuance Volume

CBU Centralized Backup Utility

CLI Command Line Interface

ECC EMC Control Center



Term Definition

ESN Enterprise Storage Network

MSS Managed Storage Services

NSM Unicenter Network and Systems Management

SDR Symmetrix Disk Reallocation

SGR Symmetrix Manager

SPS Storage Provisioning Services

STM SRDF/TimeFinder Manager

STS StorageScope

TNG CA Unicenter TNG (prior name, replaced by NSM)

UDF User Defined Field

WLA Work Load Analyzer

SDR Symmetrix Disk Reallocation

1.6 Related Documentation KnowledgeCentre Capability Designs Repository - This document is one of several that make up the Released Capability Designs for this capability. For a complete list of documentation, see the Capability Designs KnowledgeCentre site located at: https://knowledgecentre.eds.com/sites/kc6/default.aspx

1.7 References Document Author Status Version

EMC SAN Design Guide EDS Final 2004.1.0 Managed Storage Services Architecture Definition

EDS Final 2003.1.0

Managed Storage Services Reference Guide EDS Pending EMC ControlCenter Message Guide EDS Final 2004.2.1 EMC ControlCenter Deployment Guide EDS Final 2004.2.1 EMC ControlCenter Operations Guide EDS Final 2004.2.1 EMC SAN Manager Operations Guide EDS Final 2004.2.1 ECC StorageScope User Guide EDS Final 2004.2.1 ECC Performance Manager User Guide EDS Final 2004.2.1 EMC ControlCenter Implementation Guide EMC Final 2004.2.1

Document Author Status Version OnAlert Product Guide EMC 2.2 OnAlert Release Notes EMC 2.2 OnAlert Refresh Letter EMC 2.2


https://knowledgecentre.eds.com/sites/kc6/default.aspx


2 Roles and Responsibilities For Roles and Responsibilities, refer to the ECC Deployment Guide.

3 User Procedures When installing OnAlert or CLARalert, the user must be mindful of the limitations placed on the product by EMC. The following chart summarizes the most typical of these limitations. Users should refer to the EMC Support Matrix at installation time in order to obtain the most current information on product limitations.

3.1 OnAlert Implementation

3.1.1 General

OnAlert is the generalized EMC tool used for phone home and remote support for much (but not all) of the EMC storage platforms. Each variation of OnAlert is a unique product, and typically cannot co-exist on the same host platform that is hosting another version of the OnAlert or CLARalert products.



3.1.2 Solutions and Restrictions

EMC Remote Support and Alerting Solutions

Platform Communication Software Notes

Symmetrix Modem Self Contained No Dependencies

Connectrix Modem Connectrix Manager

No Dependencies

(do not install Terminal Services. PCAnywhere on Ctx SP if using SymmRemote/EMCRemote)

Celerra Modem Self Contained No Dependencies

Platform Host Communication Software Notes

CLARiiON Workstation Modem

CLARalert Cannot run with other alerting or remote control software including Terminal Services. *,a,b,c,e,f,g,h

Centera Workstation Modem On Alert Cannot run with other alerting or remote control software including Terminal Services. *,a,d,e,k

Cisco MDS Workstation Modem On Alert Cannot run with other alerting or remote control software including Terminal Services. * ,a,d,e,g,j

Centera (light) N/A N/A eMail Uses IP connection for eMail alerts. k



Table 1 Configuration Limitations

The above summary of configurations are for enabling EMC product support to be alerted of faulty conditions on EMC monitored products, and remotely access these products when necessary for break/fix analysis.

* Assumes Dial EMC and EMC Remote components are used. When EMC Remote is not in use, then remote software such as Terminal Services can be utilized.

(a) CLARalert is not compatible with On Alert, and should run on a separate workstation. If using todays version of CLARAlert OnAlert is superceded. (This is where lexicon and function cross-paths.) The OnAlert suite of tools includes an older version of ClarAlert that at one time was used to support Clariion in a centralized environment.

(b) The latest version of CLARiiON supports ClarAlert not OnAlert. ClarAlert includes Navisphere, DialEMC and EMCRemote.)

(c) The Clariion CX uses CLARAlert in a centralized environment. In a distributed environment the Clariion array can use SMTP for connecthome (Clarion array to EMC). Remote support (EMC to CLARiiON array) via WebEx or an EMCRemote session (via an EMCRemote workstation) is supported.

(d) On Alert installations are intended to manage one product type. For example, an instance of On Alert for Cisco should not run on the same workstation as an instance of On Alert for Centera.

(e) These remote management workstations are for EMC use only and do NOT support any additional management function. Additional workstations or servers must be in place for Navisphere, ControlCenter or other storage management products utilized.

(f) CLARAlert includes Navisphere, DialEMC and EMCRemote. All can co-exist on the same server/workstation (caveats as stated above on Terminal Services, single product support etc).

(g) Outside of remote support tools - Navisphere and ControlCenter cannot reside peacefully on the same machine.

(h) ControlCenter uses a CLARiiON Agent to discover the CLARiiON arrays. The CLARiiON Agent needs the Navi CLI it does not need to have the Navisphere host Agent and it does not need to have access to any CLARiiON LUNs. It just needs IP connectivity to the arrays and the ControlCenter Server. If the ControlCenter CLARiiON Agent is running on a ControlCenter infrastructure host, it wont have any conflict with OnAlert. There is no reason why the CLARiiON Agent could not run on the same host as CLARAlert.

(j) For Cisco MDS ControlCenter is the interface between the switch and OnAlert (DialEMC).. If 'dial-home' support (ControlCenter for the switch to EMC), by ControlCenter, for the MDS, Brocade or McData switches is required, then OnAlert (the dial-home portion of OnAlert) must reside on the same server as CC. Unless dial-in support (EMC to the CC server) is required, SymmRemote does not need to be installed on the CC server. SymmRemote can not co-exist with Terminal Services or other remote desk-top services.

(k) For Centera (light or standard) if the customer allows SMTP connecthome (Centera to EMC) and a PPP connection to the Centera frame (EMC to Centera) the OnAlert workstation/server is not needed. Centera CE may have other restrictions.

Note: Modems are provided with many of the storage platforms listed above, refer to template BOM information for additional details.



3.1.3 Examples

Copyright EDS 2004 9

Combined View Typical MSS Implementation Combined View Typical MSS Implementation

Cisco MDS 9000Switches

Modem

WinTel ServerECC Infrastructure

(OnAlert-Cisco)

CLARiiON

ModemWinTel Server

(OnAlert-CLARiiON)

Symmetrix

Modem

IPNetwork

Figure 1 OnAlert Example

In addition to the recommended configuration, and limitations stated above, additional information is required for those cases where the ECC Infrastructure Server hosting OnAlert is configured in a cluster for high availability.

3.1.3.1 OnAlert Cluster Configuration Note:

Information pertaining to specifics of OnAlert in a cluster configuration are included here to assist the user when faced with managing the product in a cluster environment.

The following information pertaining to a clustered instance of OnAlert was prepared for EDS by EMC.

This setup has been submitted to EMC Engineering for approval via RPQ # 36313 on January 6, 2005

Prerequisites: Microsoft Windows 2003 Enterprise Server 2-Node Cluster (Active-Passive) Modem installed on each node and fully tested. Modems should be OnAlert recommended modems. Modems can share a single phone line EMC ControlCenter 5.2, SP1 with Server service installed in a designated Cluster Resource group




General Environment: The OnAlert software for ControlCenter is composed of three components (EventHandler, DialEMC, and Symmremote). Symmremote is not qualified for use on Windows 2003. Since the primary purpose of the OnAlert for ControlCenter installation is the reporting of errors to EMC Support for the Cisco MDS switches and not dial-in access, the Symmremote software is not required.

OnAlert will be installed to the default system disks for each node. OnAlert will not be installed to any shared environment. OnAlert will be configured to monitor the EMC ControlCenter shared directory.

The EventHandler service will run continually on both nodes. Even though the EventHandler is running on both nodes, only one instance of EventHandler will actually be able to access the shared disk resource where ControlCenter creates the devstatus.err file for alert conditions. There does not seem to be any issues with EventHandler running and not being able to access a drive that is not currently available to the passive node. This will mean that only one node will attempt to activate DialEMC and phone support. An added advantage of this configuration is that each node will have its own log and event directories and so determination of issues can be traced back to a specific node.

Installation Notes:

Start with Active Cluster Node where ControlCenter 5.x Server component has already been installed. Install OnAlert for ControlCenter (DialEMC and EventHandler components only) to non-shared default drive (C:\). Specify the Shared Directory for ControlCenter that is monitored during the installation procedure. Ex. E:\ECC\ecc_inf\data\\data Restart Node to complete installation (note this will failover the active node). Wait for second node to be fully operational. Install OnAlert as on the first node. Restart second node to complete installation. Configure OnAlert for monitored devices on both nodes. (Standard OnAlert configuration)

If OnAlert must be uninstalled, this will be straightforward since the files are located on non-shared resources. This makes support easy if a new revision on OnAlert was required to be installed. Each node will have its own logs for OnAlert, so any problem during operation can be traced to the specific node in the cluster.

Testing: This configuration was tested in the EMC Global Integration Group lab on a clustered EMC ControlCenter environment. Forced errors from a switch caused the EventHandler to activate the DialEMC component only on the current active node. The cluster resource group was moved to the inactive node and a forced error was again created. The second node correctly detected the condition and activated DialEMC. The EventHandler on the inactive node continues to run without error. Moving the ControlCenter resource group back to the first node and simulating an error showed that EventHandler immediately detected the error condition.

Document ControlPurpose and AudienceReviewersAmendment RecordTerminologyRelated Documentation

Roles and ResponsibilitiesUser ProceduresOnAlert ImplementationGeneralSolutions and RestrictionsExamplesOnAlert Cluster Configuration Note: