EMC Ionix ControlCenter · Symmetrix VMAX, TimeFinder, UltraFlex, ... Passing alert information to an autofix script ... EMC Ionix ControlCenter 6.1 Administrators Guide 13

EMC® Ionix™

ControlCenter®

6.1

Administrators GuideP/N 300-006-338REV 15

EMC Ionix ControlCenter 6.1 Administrators Guide2

Copyright © 2001 - 2012 EMC Corporation. All rights reserved. Published in the USA.

Published November, 2012

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

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

EMC2, EMC, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Connectrix, CopyCross, CopyPoint, CX, Dantz, Data Domain, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, OnAlert, OpenScale, PixTools, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, VMAX, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and the RSA logo, are registered trademarks or trademarks of EMC Corporation in the United States and other countries. Vblock is a trademark of EMC Corporation in the United States.

VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions.

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 the technical documentation and advisories section on the EMC online support website.

CONTENTS

Chapter 1 Working with Ionix ControlCenter Interfaces and Applications

Working in the Ionix ControlCenter Console.................................... 17Launching the Console application .......................................... 17Logging in to the Ionix ControlCenter Console .......................... 18Ionix ControlCenter Console and online help............................ 18

Working in the Web Console .......................................................... 19Accessing the Web Console ..................................................... 19Web Console tutorial and online help ...................................... 20

Working with StorageScope ........................................................... 21Launching StorageScope from the Ionix ControlCenter Console ................................................................................... 21Launching StorageScope from a web browser .......................... 23Launching StorageScope from the Start menu.......................... 23Configuring, Activating, Deactivating, or Modifying the default configuration of StorageScope Model Services Adapter (MSA) feature ............................................................. 23StorageScope online help........................................................ 25

Working with Performance Manager ............................................... 26Launching Performance Manager............................................. 26Accessing Performance Manager automated reports................ 28Performance Manager online help ........................................... 30

Chapter 2 Managing Ionix ControlCenter Users

Introduction to Ionix ControlCenter user access management......... 31Managing user access to Ionix ControlCenter ........................... 32Working with user groups ........................................................ 33Working with rules ................................................................... 34Assigning permissions............................................................. 36Understanding groups and inheritance .................................... 41Understanding the ChangeMembership permission................. 41

User access management procedures ............................................ 42 Creating Ionix ControlCenter users ................................................. 43

Creating a domain account for the ECC Server service .............. 45 Adding a user to Ionix ControlCenter .............................................. 46 Managing Ionix ControlCenter user groups ..................................... 47

Creating a new user group ....................................................... 48Adding a user to a group.......................................................... 48

EMC Ionix ControlCenter 6.1 Administrators Guide 3

Contents

Removing the eccadmin user from Ionix ControlCenter ................... 49 Creating and modifying rules for users and user groups ................. 50 Monitoring and contacting Console users ...................................... 52

Monitoring Console users ........................................................ 53Sending messages to Console users ........................................ 53

Chapter 3 Administering Ionix ControlCenter Data Collection Policies

Data collection overview................................................................ 55 Managing data collection policy definitions and templates ............ 56 Agent data collection policy reference............................................ 59

Chapter 4 Configuring and Managing Alerts and Notifications

Understanding alerts and notifications .......................................... 69Alert and notification life cycles ............................................... 71Understanding metric types ..................................................... 74

Setting up your alert and notification strategy................................ 74Controlling who creates and edits alerts and notifications ....... 75Deciding whether to define alerts or notifications .................... 75Defining the severity levels ...................................................... 76Establishing procedures for the resolution of alerts ................. 76Refining alert definitions.......................................................... 77Keeping alerts and notifications............................................... 78

Creating alerts and notifications .................................................... 78Tips for setting alerts and notifications .................................... 79Getting help............................................................................. 79Gathering information.............................................................. 80

Creating alert definitions ............................................................... 81Creating an alert definition from a template ............................. 81Creating alert definitions in the Edit Thresholds dialog............. 82Copying an alert definition....................................................... 82Testing an alert definition ........................................................ 83

Controlling alert spikes .................................................................. 84 Sending alerts in Email or to a management framework ................. 85 Automating alert responses with autofixes .................................... 86

Creating an autofix definition in the Console............................ 86Passing alert information to an autofix script ........................... 87Creating an autofix script on the host....................................... 89Attaching an autofix to an alert definition ................................ 89

Best practices for configuring and managing alerts ........................ 90Disable unnecessary or redundant alerts ................................. 90Set alert frequencies to minimize processing impact................ 91

4 EMC Ionix ControlCenter 6.1 Administrators Guide

Contents

Use notifications to reduce alert volume .................................. 91Create user-defined groups to organize your alerts .................. 91Use management policies to notify personnel.......................... 92Modify templates to facilitate alert creation ............................. 92

Troubleshooting alerts and autofixes ............................................. 92Too many alerts appear in the Console .................................... 92Cannot create or edit alerts or changes not saved .................... 93Cannot clear alerts................................................................... 94Alert does not trigger as expected............................................ 94Autofix does not run ................................................................ 94Alert count differs among users ............................................... 95Managed object has Warning Icon but no alerts....................... 95Alert created or modified date and time is incorrect ................. 96

Chapter 5 Maintaining the Repository

Automatic tasks............................................................................. 97Backing up the Ionix ControlCenter Repository......................... 97Backing up the Ionix ControlCenter Repository using Third-Party Tools...................................................................... 98Exporting the Repository backup.............................................. 99Analyzing tables .................................................................... 100Rebuilding the index.............................................................. 100Recompiling invalid objects ................................................... 101Monitoring tablespace growth ............................................... 101Monitoring the status of automated tasks.............................. 102Listing installed Ionix ControlCenter components .................. 102

Manual tasks............................................................................... 103Shutting down the Repository ................................................ 103Starting the Repository .......................................................... 103Scanning the Repository Alert Log.......................................... 104Cleaning trace files ................................................................ 104Determining Tablespace Fragmentation ................................. 104Determining which processes are currently running ............... 105Resetting the Repository ........................................................ 105Performing a media recovery.................................................. 105Restoring the Repository ........................................................ 105Importing the Repository database ........................................ 106Gathering data for remote diagnostics assistance.................. 108TCP/IP Service During Maintenance ....................................... 108

StorageScope Repository............................................................. 108


Contents

Chapter 6 Security

Changing Passwords on the Ionix ControlCenter Infrastructure ..... 109Change the Ionix ControlCenter Locksmith password ............. 110Change the Repository passwords ......................................... 110Change the LDAP bind password............................................ 110

Changing the Database Encryption Password............................... 111Procedure to reset the Repository Encryption Key................... 111

Changing StorageScope Passwords ............................................. 112 Steps to Regenerate Certificates for Ionix ControlCenter 6.1 ......... 112 File Authenticator Utility .............................................................. 121

Installation ............................................................................ 122Signing files........................................................................... 122

Trusted Entity Utility..................................................................... 123Updating Trusted Entity status ............................................... 124Exporting Trusted Entity records............................................. 125Deleting Trusted Entity records .............................................. 126

Trust Status Export Utility............................................................. 126 Untrusting Ionix ControlCenter Components................................. 127 Alternative Certificate Setup for SMC Link and Launch.................. 128

Ionix ControlCenter Setup ...................................................... 128SMC Setup............................................................................. 129

Chapter 7 Using Fully Automated Storage Tiers

Overview ..................................................................................... 131 Managing Service Levels.............................................................. 132

Managing service levels with FAST, Symmetrix Performance Analyzer, and Ionix ControlCenter .......................................... 132

Working with Service Levels......................................................... 133Creating a service level in StorageScope ................................ 133Importing a Symmetrix tier ..................................................... 135Applying service level definition changes to the LUNs in the StorageScope Repository....................................................... 135Modifying a service level........................................................ 135Deleting a service level .......................................................... 136Using custom queries ............................................................ 136

Appendix A Migrating the StorageScope Repository

Overview ..................................................................................... 138Prerequisites ......................................................................... 138

Export StorageScope Repository .................................................. 140 Uninstall StorageScope ............................................................... 141


Contents

Install StorageScope on the new host .......................................... 142 Import the StorageScope Repository dump file ............................ 143

Appendix B Configuring Email Notifications for Backup and Export Utilities

Overview ..................................................................................... 146 Adding email notifications to the utilities..................................... 147 Removing the email notifications................................................. 148 Troubleshooting .......................................................................... 149

Appendix C Launching Ionix ControlCenter Web Applications with Alternate Entities

Overview ..................................................................................... 152 Patching Ionix ControlCenter Web Server Services........................ 153 Importing Ionix ControlCenter Trust Certificate in browser............. 154


Contents


Title Page

FIGURES

1 StorageScope login page ............................................................................... 222 StorageScope Dashboard .............................................................................. 223 Rule providing a user with SDR permissions on a Symmetrix array ................. 334 Initial groups ................................................................................................. 345 Default authorization rules ............................................................................ 356 New User dialog box ...................................................................................... 447 New user definition........................................................................................ 468 Creating a new user group ............................................................................. 489 Adding a user to a group................................................................................ 4910 Creating a new rule ........................................................................................ 5111 Naming the new rule...................................................................................... 5212 Selecting a policy to modify ........................................................................... 5813 Policy definition dialog box............................................................................ 5914 Alerts view..................................................................................................... 7015 At A Glance Health and Performance views .................................................... 7016 Alert and notification life cycle....................................................................... 7217 trustedEntityUtil main menu ........................................................................ 12418 trustedEntityUtil input file ............................................................................ 12519 FAST Tiering ................................................................................................. 131


Figures


Title Page

TABLES

1 Tasks and permissions .................................................................................. 372 Backup agent DCPs........................................................................................ 603 Common agent DCPs ..................................................................................... 604 Connectivity agent DCPs ................................................................................ 615 Common Mapping Agent DCPs....................................................................... 616 Database agent DCPs .................................................................................... 627 Host agents for AIX, HP-UX, Linux, and Solaris DCPs....................................... 628 Host Agent for Windows DCPs........................................................................ 659 Physical agent DCPs ...................................................................................... 6510 EMC Invista Agent .......................................................................................... 6611 Storage agent DCPs ....................................................................................... 6612 VMware agent DCP......................................................................................... 6813 Alert and notification life cycle stages............................................................ 7314 Defining alert severity levels .......................................................................... 7615 Gathering information for file systems, directories, and files .......................... 8016 Autofix syntax requirements and examples.................................................... 8817 Reducing the number of alerts that display .................................................... 9318 Location of Keys and Files............................................................................ 12719 Pre-defined service levels ............................................................................ 13320 Service level definition ................................................................................ 134


Tableses


PREFACE

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features.

Contact your EMC representative if a product does not function properly or does not function as described in this document.

Note: This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document.

AudienceThis guide is part of the EMC Ionix ControlCenter documentation set, and is intended for use by system and data storage administrators.

Readers of this guide are expected to be familiar with the following:

◆ Storage array operation

◆ Host operating systems

◆ Storage array networks

Note: Detailed information about EMC products is available on the EMC online support website at: http://Powerlink.EMC.com.

Related documentationIonix ControlCenter documentation is available in the following locations:

◆ Your Ionix ControlCenter installation kit installs a documentation library as part of the software.

◆ You can install an independent documentation library by running ControlCenterLibrary.exe from the last CD.


Preface

◆ EMC online support (http://Powerlink.EMC.com) supplies updated versions of each document, as well as hosting the Doc Updater executable which can install a new documentation library independent of the software installation or refresh all existing documentation libraries on your host.

◆ After installation or updating, the Ionix ControlCenter Documentation Library is available from a desktop icon and the Ionix ControlCenter Console's help menu.

Conventions used in this documentEMC uses the following conventions for special notices:

CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

NOTICE is used to address practices not related to personal injury.

Note: A note presents information that is important, but not hazard-related.

IMPORTANT

An important notice contains information essential to software or hardware operation.


Preface

Typographical conventions

EMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and

menus• Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements,

keywords, clauses, environment variables, functions, and utilities• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys,

file systems, and notifications

Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages

Used in procedures for:• Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and

menus• What the user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis, for example, a new term• Variables

Courier Used for:• System output, such as an error message or script• URLs, complete paths, filenames, prompts, and syntax when shown outside of running text

Courier bold Used for specific user input, such as commands

Courier italic Used in procedures for:• Variables on the command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections — the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y or z

... Ellipses indicate nonessential information omitted from the example


Preface

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product information. For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to the EMC online support website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]


http://Powerlink.EMC.com

CHAPTER 1Working with Ionix ControlCenter Interfaces and Applications

This chapter provides instructions on how to access the Ionix ControlCenter Console and Web Console interfaces, as well as the StorageScope and Performance Manager applications after Ionix ControlCenter has been installed.

This chapter contains the following sections:

◆ Working in the Ionix ControlCenter Console ...................................................... 17◆ Working in the Web Console ............................................................................. 19◆ Working with StorageScope.............................................................................. 21◆ Working with Performance Manager ................................................................. 26

Working in the Ionix ControlCenter ConsoleThe Console is the primary Ionix ControlCenter user interface. System and storage administrators use the Console to view, manage, configure, and report on storage area network components (managed objects).

The Console is a Java-based application that allows you to monitor and control the storage infrastructure from a central point.

Launching the Console application

Follow these steps to launch the Ionix ControlCenter Console.

Windows

a. Click the Start ECC Console icon on the desktop, or from a command line, run:

<Console_install_directory>\bin\launch.bat

where C:\Program Files\ecc\console is the default <Console_install_directory> location.

The system displays the Ionix ControlCenter Launch Utility screen.

Working with Ionix ControlCenter Interfaces and Applications 17

Working with Ionix ControlCenter Interfaces and Applications

b. If not already entered, enter the following:

• ECC Server hostname, IP address, or fully qualified hostname• ECC Server host port number for Console communications (default is 10799)

c. Optionally select the Enable Console Logging checkbox to save extended debugging information from the Console (which can be useful in troubleshooting) to the following location:

%USERPROFILE%\ecc\data\<servername>\console.trc

where %USERPROFILE% is the root directory for Ionix ControlCenter Console logging information and <servername> is the ECC Server hostname, IP address, or fully qualified hostname (whichever you specified at logon).

Ionix ControlCenter always saves standard output from the Ionix ControlCenter Console to the consoleLaunch.log file in the same location (regardless of whether the Enable Console Logging checkbox is selected).

d. Click Submit.

The user logon screen is displayed.

Logging in to the Ionix ControlCenter Console

a. Enter your User Name. Use the following the first time you log in, until the Ionix ControlCenter Administrator adds other users through the Ionix ControlCenter Console.

• eccadmin (if using Windows authentication)

b. Enter your password.

c. Click OK. The Ionix ControlCenter Console user interface appears.

Ionix ControlCenter Console and online help

Ionix ControlCenterprovides a comprehensive Java-based Help system. You access Help from the toolbar by selecting Help > Topics. The Help Topic window appears.

Using the Help Contents tabClick the Contents tab in the Navigator window to display the table-of-contents tree.

Browse the tree by:



◆ Double-clicking a closed book to expand the next lower level of topics and books, or

◆ Selecting a book and choosing Expand, Expand All, Collapse, or Collapse All from the File menu.

Displaying a topic from the treeDisplay a topic from the tree in the Help Topic window by:

◆ Double-clicking a topic, or

◆ Selecting a topic, then clicking the Display icon located in the Help toolbar.

Note: To display a topic in a new window, select a topic, and then click the Display in New Window icon located in the Help toolbar.

Working in the Web ConsoleThe Ionix ControlCenter Web Console uses data stored in the Repository to monitor your storage-attached network and manage Ionix ControlCenter alerts remotely through a Web browser.

The Web Console provides access to the same Ionix ControlCenter Repository as the Ionix ControlCenter Console. However, the Web Console:

◆ Can be accessed without installation on the host.◆ Has an improved interface design for easy use, without creating a large learning

curve for users comfortable with the Ionix ControlCenter Console.

Note: The Web Console does not provide all of the administrative and management functions as the Ionix ControlCenter Console.

Accessing the Web Console

The following URL is the default for accessing the Web Console: https://<hostname>:30002/eccweb

where hostname is the name of the host running the Web Console server.

Working in the Web Console 19


If your network is configured with Secure Sockets Layer (SSL), you may be required to enter a different URL and port. Check with your system administrator for more information.

Accessing the Web Console with pop-up blockersIf pop-up blockers are installed on the host from which you are opening the Web Console, the Web Console may not open in your browser.

To open the Web Console with a pop-up blocker installed on the host, do one of the following:

◆ Disable the pop-up blocker program before you launch the Web Console.

◆ If available, use the pop-up blocker's unblocking feature while launching the Web Console. Refer to the pop-up blocker's documentation for instructions.

Note: Pop-up blockers may also prevent you from accessing the Web Console online help. Use the same procedures you used to enable access to the Web Console to access the Web Console help.

Web Console tutorial and online help

The Web Console is provided with a tutorial and help system.

Web Console tutorialAccess the Web Console tutorial after initial login to the Ionix ControlCenter Console through the Welcome screen or through the Console Documentation Library (Help>Doumentation Library).

The tutorial discusses how to access the Web Console, the differences between the Web Console and the Ionix ControlCenter Console, and when to use the Web Console.

Note: The Web Console tutorial requires the Flash plug-in for your browser.

Web Console helpThe help is a WebHelp system opened in your browser. It supports the Web navigation tools provided with your browser as well as providing Contents, Index, and Search panes for easy navigation.

Access the help within the Web Console as follows:



◆ Help menu > Contents, Index, and Search options to review general information about the Web Console or to access the help Contents, Index, Search, and Glossary.

◆ View title bar, click the question mark “?” to open a context-sensitive help topic that provides information about the open view.

◆ Alerts view, right-click an alert in the table, and select Alerts > Help. A context-sensitive help topic opens for the selected alert. The alert help topics describe how to respond to the alert in addition to other pertinent information about the selected alert.

◆ Dialog box, click the Help button to open a context-sensitive help topic for the dialog box. The dialog box help provides details about the options provided in the dialog box.

◆ How Do I... links within the help system to open another topic that provides needed information or explains how to perform a task. Click a link in the How Do I... column in a help topic.

Note: The “No Context-sensitive Help Available” topic opens if a context-sensitive help topic is missing or is linked incorrectly to the application. Please follow the steps described in the topic to get the information you need, or contact Customer Support about the issue.

Working with StorageScopeEMC Ionix ControlCenter StorageScope™ 6.1 provides a variety of features (snapshots, views, built-in and custom reports, database queries) to help you:

◆ Assess your current storage environment

◆ Determine future storage needs based on historical usage and trending reports

◆ Reclaim unused or under utilized storage resources

Launching StorageScope from the Ionix ControlCenter Console

To launch StorageScope from the Ionix ControlCenter Console:

1. Select ECC Administration from the Ionix ControlCenter task bar.

Working with StorageScope 21


2. Select Reports > Launch StorageScope. Your web browser will display the StorageScope login page (Figure 1 on page 22).

3. Enter your Ionix ControlCenter username and password to log in to StorageScope.

4. Click Login to log in to StorageScope. The Dashboard will appear (Figure 2 on page 22).

Figure 1 StorageScope login page

Figure 2 StorageScope Dashboard



Launching StorageScope from a web browser

To launch StorageScope from a web browser window:

1. Direct your web browser to the StorageScope server. The default URL is https://<servername>:30002/srm. Your web browser will display the StorageScope login page (Figure 1 on page 22).


3. Click Login to log in to StorageScope. The Dashboard will appear. (Figure 2 on page 22)

Launching StorageScope from the Start menu

To launch StorageScope from the Start menu on the StorageScope server:

Note: This procedure can be used only if you are logged into the Ionix ControlCenter/StorageScope application server. You cannot access StorageScope through the Start menu on a remote system.

1. Select Start > Programs > EMC > EMC ControlCenter > StorageScope. Your web browser will display the StorageScope login page (Figure 1 on page 22).


3. Click Login to log in to StorageScope. The Dashboard will appear (Figure 2 on page 22).

Configuring, Activating, Deactivating, or Modifying the default configuration of StorageScope Model Services Adapter (MSA) feature

By default, the StorageScope MSA is deactivated, after the Ionix ControlCenter 6.1 upgrade is done. It needs to be activated manually. Activate StorageScope MSA only if your current repository is a StorageScope Repository. You can use CAS Server application installed on any DCI host.

Configuring SSL and disabling the conflicting port on STS MSA host:

1. Log into the EMC Ionix ControlCenter host.

2. Navigate to <ECC_INSTALL_ROOT>\tomcat\conf directory.



3. Open the server.xml file and modify the following line:

8009 entries(AJP port entries)to



4. Configure the keystore and password for SSL mode, http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html provides information on configuring SSL. You can also use Ionix ControlCenter Tomcat's setting.

5. Search the xml tag Connector port="8443" pro…./ in <ECC_INSTALL_ROOT>\tomcat_stsmsa\conf \server.xml.

6. Copy the complete xml tag of port 30002 from <ECC_INSTALL_ROOT>\tomcat\conf \server.xml file and replace <Connector port="8443" pro…./> in <ECC_INSTALL_ROOT>\tomcat_stsmsa\conf \server.xml with <Connector port="30002 " pro…./> which is copied above.

7. Change the port number from 30002 to 8443 in <ECC_INSTALL_ROOT>\tomcat_stsmsa\conf \server.xml file.

8. Copy the keycert.ks and trust.ks files from <ECC_INSTALL_ROOT>\tomcat\conf directory to <ECC_INSTALL_ROOT>\tomcat_stsmsa\conf directory.

9. Restart the EMC ControlCenter Web Server and EMC ControlCenter STS MSA Web Server.

Follow these instructions to Activate the StorageScope MSA feature:

Activating STS MSATo activate the StorageScope MSAfrom the Start menu:

1. Select Start > Programs > EMC > EMC ControlCenter > StorageScope > Configure STS MSA. A command window is launched.

2. Enter your choice as 1 to activate the STS MSA. You will be prompted for a confirmation.

3. Enter Y to confirm. You will be prompted for a DCI hostname.

4. Enter a DCI fully qualified hostname for the settings to be configured. Wait for the successful activation and exit message to appear.

5. Press any key to exit the command window.

6. Reboot Ionix ControlCenter for the changes to take effect.



Deactivating STS MSATo deactivate the StorageScope MSAfrom the Start menu:


2. Enter your choice as 2 to deactivate the STS MSA. You will be prompted for a yes or no.

3. Enter Y to confirm. Wait for the successful deactivation and the exit message to appear.



Modifying the default configuration of StorageScope MSATo modify the default configuration of STS MSAfrom the Start menu:


2. Enter your choice as 3 to modify the default configuration of STS MSA. You will be prompted with the following suboptions:

1. Change STS MSA Tomcat port

2. Change STS MSA FQDN

3. Either enter 1 to change the STS MSA Tomcat port number or enter 2 to change the STS MSA fully qualified host name (FQDN).

4. Enter the Tomcat port number or the FQDN based on your choice and press the Enter key. Wait for the changes to to take effect.



StorageScope online help

StorageScope provides many ways to get additional information that can help you understand and use the application. Use the following steps to get help for different areas of the StorageScope Console:

◆ From the Help menu, select StorageScope Help to browse or navigate through the online help system.



◆ Click in the upper-right corner of a page to open a help topic describing the page or how to use it.

◆ Click in the upper-right corner of a dialog box to open a help topic describing the options in the dialog box.

◆ In the Query Builder Wizard, click the Help button at the bottom of the window to open a help topic about the current step in the wizard.

◆ In a table (for example, the SRM views or query results), position the cursor over a column header and view the tool tip for the column.

Working with Performance ManagerIonix ControlCenter Performance Manager allows you to collect, manage, view, and analyze historical performance data for a period of time or performance trends. Performance analysis is done using historical data collected from Symmetrix® storage arrays, CLARiiON® storage arrays, Hosts, Oracle databases, and Fibre Channel connectivity device ports.

Performance Manager documentation includes online help, a tutorial, and a metrics glossary available through the Performance Manager application or the Console Documentation Library.

Launching Performance Manager

Launching Performance Manager requires that you log in to establish yourself as an authorized Performance Manager user and to secure your Ionix ControlCenter environment.

◆ Use your Ionix ControlCenter username and password to log in to Performance Manager.

◆ Your Ionix ControlCenter username and password are case-sensitive.

◆ No log in authorization is required to work offline.

The following sections describe how to launch Performance Manager:

◆ “From the Start menu” on page 27◆ “From the Console” on page 27◆ “From the Start menu to work offline” on page 27



From the Start menu1. On the Performance Manager host, click Start > Programs > EMC > EMC

ControlCenter > Performance Manager. The Login dialog box appears.

2. From the Login dialog box:

• The Work Offline option remains unchecked.

• Select a Repository name from the menu. (Repository names are populated with WLA.ini alias names and are based on TNSNAMES.ora database entries.)

• Use your Ionix ControlCenter username and password to log in to Performance Manager.

• Click OK to launch Performance Manager. The Data Selection dialog box appears.

From the Console 1. Click File > Launch > Performance Manager. The Login dialog box appears.

Note: If Performance Manager is not installed, this option is grayed out.


• The Work Offline option remains unchecked.




From the Start menu to work offlineYou can use the Work Offline option in the Login dialog box to analyze local copies of ttp and btp datafile collections.

Note: This option offers fast access to local Performance Manager data. No log in authorization is required.

To launch Performance Manager from the Start menu to work offline:

Working with Performance Manager 27


1. On the Performance Manager host, click Start > Programs > EMC > EMC ControlCenter > Performance Manager. The Login dialog box appears.


• Select the Work Offline checkbox.




3. From the Data Selection dialog box:

• Select Specific File at the bottom of the Data Selection dialog box.

• Enter the location and name of the Private collection, or click the browse (...) button to locate and then open a local ttp or btp data file in a collection folder.

• Click OK.

Accessing Performance Manager automated reports

Automated reports are viewed by opening a web browser. Reports are managed by the automation jobs and accessed through the Ionix ControlCenter web server.

◆ Ionix ControlCenter username and password authorization is required.

◆ EMC ControlCenter Web Server service must be running on the host where the ECC Server is running.

◆ Supported browser versions include Microsoft Internet Explorer 5.5 and 6.0. If your browser version is not supported, a message appears advising you to update your browser. Refer to the EMC Ionix ControlCenter Support Matrix available on EMC online support website at http://Powerlink.EMC.com for more information about supported browser versions.

◆ Internet Explorer session cookies must be enabled. (Session cookies are enabled by default.) If your session cookies are not enabled, automated reports will not function properly.



◆ If you are viewing automated reports in Internet Explorer and you want to open additional automated reports in another browser, you must open the other reports through the Console or through Performance Manager. If you attempt to view the reports by opening a second browser window and copying the URL into the second browser, the reports will not function properly.

◆ When viewing automated reports from multiple browser windows on the same host, a graph is displayed in each report.

◆ If your automated reports browser session is inactive for more than 30 minutes, you must log in again.

The following sections describes how to access Performance Manager automated reports:

◆ “From Performance Manager” on page 29◆ “From the Console” on page 29◆ “From your web browser” on page 29

From Performance ManagerAfter using your Ionix ControlCenter username and password to log in to Performance Manager:

1. Select Reports > View Report.

2. Use your Ionix ControlCenter username and password to log in.

From the ConsoleAfter using your Ionix ControlCenter username and password to log in to the EMC Ionix ControlCenter Console:

1. Click Performance Mgt. and then select Reports > Performance Manager Reports.


OR1. Click ECC Administration and then select Reports > Performance Manager Reports.


From your web browserTo access Performance Manager automated reports from your web browser:

1. Enter the URL for your Performance Manager automated reports:

Working with Performance Manager 29


https://<hostname>:30002

Where <hostname> is the name of the host running EMC ControlCenter Web Server service, and 30002 is the default port address for Performance Manager to access the server.


Performance Manager online help

Online help is available for Performance Manager. The help includes detailed procedures, reference information, and a tutorial about this application.

To access Performance Manager help, click Help in the gray navigation bar at the top of the Performance Manager dialog.

The following options are available from the Help menu:

◆ Contents, Index, Search — This help system includes detailed procedures and reference information about Performance Manager. A Table of Contents is displayed in the left pane along with Index and Search tabs. The Index provides an alphabetized list of topics and keywords in the online help. The Search facility allows you to find topics that contain specific keywords.

◆ Tutorial — This help system describes how to use Performance Manager. A Table of Contents is displayed in the left pane. The Search facility allows you to find topics that contain specific keywords.

◆ Metrics Glossary — This help topic lists and defines available Performance Manager metrics.

◆ About Performance Manager — This dialog lists the version, copyright, and trademark information about Ionix ControlCenter Performance Manager.

Note: Help options open from a new window in your system browser. Help systems support the Web navigation tools provided with your browser as well as provide Contents, Index, and Search panes for easy navigation. How Do I... links within the help system open another topic that provides further information or explains how to perform a task.


CHAPTER 2Managing Ionix ControlCenter Users

This chapter provides an introduction to Ionix ControlCenter access management as well as procedures for setting up and managing user access to the Ionix ControlCenter application.


◆ Introduction to Ionix ControlCenter user access management ........................... 31◆ User access management procedures............................................................... 42◆ Creating Ionix ControlCenter users.................................................................... 43◆ Adding a user to Ionix ControlCenter................................................................. 46◆ Managing Ionix ControlCenter user groups........................................................ 47◆ Removing the eccadmin user from Ionix ControlCenter...................................... 49◆ Creating and modifying rules for users and user groups.................................... 50◆ Monitoring and contacting Console users ......................................................... 52

Introduction to Ionix ControlCenter user access management

This section provides an overview of the concepts behind Ionix ControlCenter access management. Refer to “User access management procedures” on page 42 for the procedures to administer user access.

Note: Detailed descriptions of Ionix ControlCenter user management procedures are provided in the online help under Administering ControlCenter Users.

This section contains the following topics:

◆ “Managing user access to Ionix ControlCenter” on page 32

◆ “Working with user groups” on page 33

◆ “Working with rules” on page 34

◆ “Assigning permissions” on page 36

◆ “Understanding groups and inheritance” on page 41

Managing Ionix ControlCenter Users 31

Managing Ionix ControlCenter Users

◆ “Understanding the ChangeMembership permission” on page 41

Managing user access to Ionix ControlCenter

Access to the Ionix ControlCenter application is controlled through rules that grant permissions to a single user and/or groups of users. The permissions determine what actions (commands) a user or group may perform on a given object or group of objects called a user-defined group.

Note: Users are not created through Ionix ControlCenter. Users are initially created on hosts through Windows Administrative Tools (refer to “Creating Ionix ControlCenter users” on page 43) or as LDAP users.

◆ A user group consists of a set of users to whom you want to grant the same permissions. A user inherits the permissions of the group in which the user is included.

◆ A user-defined group contains groups of objects (for example, all Symmetrix® arrays) that you want to provide access to for a specific group of users.

◆ A rule controls which users (or user groups) can access which objects (or user-defined groups) and what that user or user group is allowed to do with the user-defined group (permissions).

Note: The terms user-defined group and object group are both used to represent groups of managed objects in Ionix ControlCenter.

Figure 3 on page 33 shows the creation of a rule granting the SDR permission (authorizing the use of Symmetrix Dynamic Reallocation) to a single user (JSmyth) on a single Symmetrix array (S/N 000182402626). The complete procedure for creating a new rule for a user is provided in “Creating and modifying rules for users and user groups” on page 50.



Figure 3 Rule providing a user with SDR permissions on a Symmetrix array

Working with user groups

Ionix ControlCenter provides several default user groups that act as examples to help you begin to set up your authorization framework. You can modify or delete these groups (some exceptions apply to ECCAdministrators) to meet your needs.

Default user groupsIonix ControlCenter provides five initial user groups (Figure 4 on page 34):

◆ ECCAdministrators — Access to all objects. This group cannot be deleted or renamed. Members of this group can create users and groups and change permissions. This group initially contains one user, eccadmin, that you create during Ionix ControlCenter installation.

◆ SAN Manager™ — Access to EMC SAN Manager functions.

◆ Symmetrix Configuration Manager — Access to configuration functions.

◆ Symmetrix Data Protection Manager — Access to backup and recovery functions.

◆ Symmetrix Performance Manager — Access to tuning tools such as Optimizer and TimeFinder® SRDF®/QoS.

Introduction to Ionix ControlCenter user access management 33


Figure 4 Initial groups

Working with rules

Ionix ControlCenter provides initial authorization rules to help you set up your authorization framework. You can modify or delete these rules (some exceptions apply to ECCAdministrators) to meet your needs.

The basic principles for rule creation are:

◆ Each user or user group can have only one rule applied to it.

◆ A user may belong to multiple user groups.

◆ A rule may mention more than one user or user group.

◆ Once a rule is created for a user or a user group, no other rule may be created that applies to that specific user or user group. However, if a user is a member of a user group mentioned in a rule, it is still possible to create a rule for that specific user.

Note: A user can have a rule applied to it individually while at the same time having a rule applied to it as a member of a user group.



Rules are constructed using items under Administration, Security Management, Authorization Rules in the Ionix ControlCenter Console as shown in Figure 5 on this page.

Figure 5 Default authorization rules

Default authorization rulesEach entry represents a rule, depicted by a judge’s gavel and the rule’s name. Each rule may mention one or more users or user groups. The following rules are created by default:

Note: The authorization system maintains a privileged rule that is never displayed and cannot be edited. This rule grants members of the ECCAdministrators group full permissions over creating and changing users, user groups, user-defined groups, and authorization rules.

◆ ECCAdministrators Rule — Provides all access to all objects. ECCAdministrators can create users and groups and change permissions.

◆ SAN Manager Rule — Provides access to SAN management permissions.



◆ Symmetrix Configuration Manager Rule — Provides access to configuration permissions.

◆ Symmetrix Data Protection Manager Rule — Provides access to backup and recovery permissions.

◆ Symmetrix Performance Manager Rule — Provides access to tuning tools such as Optimizer and TimeFinder SRDF/QoS.

◆ Any User Rule — Provides access to permissions that you want to apply to all users. During installation, the StorageScope user permission is placed in the Any User rule by default.

Assigning permissions

Authorization involves creating rules that assign permissions to users. Permissions define what a user is allowed to do with a specified object or group of objects in a user-defined group. Users that require similar access permissions can be formed into user groups to simplify management.

The authorization GUI obeys the following principles:

◆ A specific user or user group can have only one rule assigned to it. However, a user may be a member of a user group that is mentioned in a rule and still have a rule applied to it that mentions that user specifically.

◆ A user may be a member of multiple user groups.

◆ A rule may mention more than one user or user group.

◆ Objects can be formed into user-defined groups so that rules can apply permissions to an entire group of objects at once.

Note: Descriptions of all Ionix ControlCenter permissions are provided in the Console online help under Administering ControlCenter Users, Working with authorization rules and permissions, ControlCenter permissions.



Table 1 on this page provides a list of the permissions required to accomplish common high-level Ionix ControlCenter tasks.

Table 1 Tasks and permissions

If you want to: You need to edit this kind of object: And give permission to perform at least this action:

Manage agents

Install, start, stop, and uninstall agents, view agent installation and uninstallation logs, and restart the master agent.

Ionix ControlCenter Agent Agent Management

Manage users, groups, rules, and objects

Create, edit, and delete authorized Ionix ControlCenter users and user groups.

User Account Manager Data UserAccountManager

Create, edit, and delete authorized Ionix ControlCenter users only.

User Account Manager Data ManageUsers

Create, edit, and delete user groups only.

User Account Manager Data ManageUserGroups

View User and group information only. User Account Manager Data Read

Create a new rule. Authorization Data Authorize (also provides Read privileges)

Read authorization rules. Authorization Data Read

Change membership of user-defined (object) groups

Change membership of user-defined group.

ObjectGroup ChangeMembership

Change permissions on managed objects

Change permissions on Ionix ControlCenter managed objects.

Various (refer to the online help for the specific object)

DatabaseUpdate

Manage the SAN

Discover and view topology. N/A No permissions required

Rename the fabric, enable or disable zoning operations, change default zoning, activate the zone set.

Fabric Fabric Management



Discover switches, rename a switch, change passwords, delete a switch, clear zone operations, import a zone set.

Switch Switch Management

Display zones and zone sets. N/A No permissions required

Create, activate, rename, delete, and/or clone zone sets, and remove zones.

ZoneSet Zoneset commands

Create, delete, rename and/or clone zones, and add or remove ports from zone.

Zone Zone commands

Manage both zones and zone sets. Zone/ZoneSet Zone Administration

Create, delete, modify, and rename zoning policies

Zoning Policy Zoning Policy Administration

Perform device masking operations on a storage array

Perform CLARiiON device masking operations.

CLARiiON CLARiiON Device Masking

Perform device masking on an HP-XP array.

HDS HDS Device Masking

Perform Symmetrix Storage Device Masking administration (set who can perform SDM operations).

Symmetrix SDM Administration

Perform Symmetrix storage device masking configuration operations including changing access rights, getting logs, carrying out SID lockdown, and so on.

Symmetrix SDM Configure

Perform operations on the SDM database including initialize, refresh, synchronize, restore, backup, and edit.

Symmetrix SDM Database

Perform StorageWorks device masking operations.

StorageWorks StorageWorks Device Masking

View or edit alert definitions

View and modify alert definitions. Alert Edit Alert Definitions

Table 1 Tasks and permissions (continued)




Assign an alert. Active Alert Assign Alert

Clear an alert. Active Alert Clear Alert

View or modify data collection policies (DCPs)

View and modify DCPs. Data Collection Policy Edit Data Collection Policy

Map devices, configure arrays, bind LUNs, and create RAID groups for various arrays

Map, unmap, move, and change the addresses of devices connected tofront-end ports on HP StorageWorks arrays.

StorageWorks HP StorageWorks Device Mapping

Expand devices on HP StorageWorks arrays.

StorageWorks HP StorageWorks Device Modification

Configure CLARiiON arrays. CLARiiON CLARiiON Array Configuration

Bind and unbind CLARiiON LUNs. CLARiiON CLARiiON LUN Management

Create or delete CLARiiON RAID groups. CLARiiON CLARiiON RAID Group

Create metaLUNs for CLARiiON arrays. CLARiiON FLARE® Fusion

Map, unmap, move, and change the addresses of devices connected to the front-end ports on an HP-XP array.

HDS HDS Device Mapping

Create logical unit size expansion (LUSE) volumes on an HP-XP array.

HDS HDS LUSE Management

Allocate or deallocate storage

Create, modify, or delete storage pools (groups of devices available for allocation) on a specified storage array(s).

SymmetrixCLARiiONStorageWorks

Allocation Administration

Perform storage allocation.You need permissions on both the host and the storage pool.

HostStorage Pool

Allocation Execution





Applying StorageScope permissionsStorageScope provides two permission types: user and administrator.

User Administrator When you install Ionix ControlCenter for the first time, an Any User authorization rule is created. StorageScope user (read-only) permissions are placed in this rule. Other permissions that the Ionix ControlCenter administrator wants all users to have can also be placed in this rule.

By default, the Any User Rule is automatically applied to a user when that user is added to Ionix ControlCenter. Therefore, all Ionix ControlCenter users have read-only access to StorageScope.

Note: The Any User Rule does not count as an assigned rule, so individual users can have the Any User Rule and one other rule assigned to them.

If you do not want all users to have this access, do the following:

1. Delete the StorageScope user permissions from the Any User Rule.

2. Create a group and add those users that you want to have StorageScope user permissions.

3. Select the group and create a rule with StorageScope user permissions.

Note: When you create the rule, select the Types radio button and select from the list of available object types. Then, select StorageScope user from the list of available actions.

Save and edit storage allocation tasks on the storage allocation task list.You need permissions on both the host and the storage pool.

HostStorage Pool

Allocation Reservation

Create a deallocation task.You need permissions on both the host and the array.

HostArray

Deallocation Reservation

Execute a deallocation task.You need permissions on both the host and the array.

HostArray

Deallocation Execution





StorageScope administrator permissions must be explicitly assigned to a user or group of users. You can create a StorageScope authorization rule and apply it to specific users or a group of users in the same way you would any other type of Ionix ControlCenter permissions.

Refer to earlier sections in this chapter for detailed information about and procedures for creating users, authorization rules, and user groups.

Understanding groups and inheritance

An Ionix ControlCenter user group is a group of users who share the same authorization characteristics. You can organize objects into user-defined groups to apply the same permissions to the entire group of objects at once.

One important consequence of user groups and object-defined groups is that permissions are inherited through the group structure. That is, groups may have subgroups, and permissions granted to a group also apply to users in a subgroup of that group. However, user-defined groups of objects have an additional permission that applies to the groups themselves (as opposed to the members) called the ChangeMembership permission. This permission restricts the ability to add and delete members from a user-defined group. “Understanding the ChangeMembership permission” on page 41 provides an overview of the ChangeMembership permission.

Note: Refer to the online help topic: "Administering ControlCenter users, User management concepts" for details about the differences in managing user groups and user-defined groups.

Understanding the ChangeMembership permission

The ChangeMembership permission applies to the user-defined group itself, rather than to the objects that are members of the group. This permission controls who is allowed to add or delete objects from the user-defined group.

Note: It is important that you control who can change the membership of user-defined groups used in authorization rules.



ChangeMembership permission inheritanceThe ChangeMembership permission is inherited through the home of the group. The home of the group is the group in which it was created or a group into which it was moved.

There is a distinction between linking a group to another group, moving a group to another group, and copying a group.

◆ Linking a group to another group (select the group, press CTRL and SHIFT, and drag the group to another group) merely links the group to the new group so that any additions or deletions of objects from the original group are reflected in the new group.

This operation requires ChangeMembership permission on the destination group.

◆ Copying the group (select the group, press CTRL, and drag the group to another group) creates a new group with the same members as the old group.

This operation requires ChangeMembership permission on the destination group.

◆ Moving a group (by dragging the group from one group to another) changes the home of the group.

This operation requires ChangeMembership permission on both the old and new group.

User access management proceduresThis section provides procedures for setting up and maintaining access management at the user level with Ionix ControlCenter. Refer to “Introduction to Ionix ControlCenter user access management” on page 31 for an overview of Ionix ControlCenter access management concepts.

In general, the following tasks are required to set up user access management:

◆ Create eccadmin. You created this user on the ECC Server host through Windows Administrative Tools as a local or domain user or as an LDAP user before installing Ionix ControlCenter. Refer to the EMC Ionix ControlCenter 6.1 Planning and Installation Guide, Volume 1 for details.

◆ Choose existing LDAP users, or local or domain users on Windows hosts, or create users through LDAP or Windows Administrative Tools (refer to “Creating Ionix ControlCenter users” on page 43).



◆ Add users to Ionix ControlCenter from the LDAP users or from Windows users (refer to “Adding a user to Ionix ControlCenter” on page 46).

◆ Create groups of users for efficient user management (refer to “Managing Ionix ControlCenter user groups” on page 47).

◆ Create or modify the rules that govern the permissions granted to users (or user groups) on specified objects (or user-defined groups).

Creating Ionix ControlCenter usersIonix ControlCenter users in general do not require any special privileges. However, users must exist as LDAP users or as local or domain users on a Windows host. The Ionix ControlCenter Server (ECC Server) must be a member of the domain or have an established trust relationship with the domain of the host on which the users were created.

Note: LDAP is supported for user authentication purposes only. LDAP does not control Ionix ControlCenter user permissions.

Creating the Ionix ControlCenter eccadmin userDuring Ionix ControlCenter planning and installation, you created a user named eccadmin through Windows Administrative Tools on the ECC Server host or as an LDAP user. When the ECC Server starts for the first time, eccadmin is added to the Ionix ControlCenter Repository as a member of the ECCAdministrators User Group. This user has the authorization to add new users, create and edit user groups, and create and edit authorization rules. Refer to EMC Ionix ControlCenter 6.1 Planning and Installation Guide, Volume 1 or EMC Ionix ControlCenter 6.1 Planning and Installation Guide, Volume 2 (MVS Agents) for more details.

The eccadmin account is an anonymous account. Anyone logging into it can perform any function without giving away their identity in log files. For this reason, it is desirable (but not necessary) to limit or eliminate eccadmin as an Ionix ControlCenter login account. Refer to “Managing Ionix ControlCenter user groups” on page 47.

Creating Ionix ControlCenter users 43


Creating Ionix ControlCenter users through Windows Administrative ToolsYou can use current Windows users (Windows 2000 or Windows Server 2003) or LDAP users or you must create new users before you can add them as users to Ionix ControlCenter. Create new Windows users as follows:

1. From the Start menu, select Settings, Control Panel.

2. Open Administrative Tools, and then open Computer Management.

3. From the Systems Tools folder on the Computer Management dialog box, open the Local Users and Groups folder. A view appears displaying the Users and Groups folders.

4. Open the Users folder. The local users appear.

5. From the Action menu, select New User. The New User dialog box appears.

Figure 6 New User dialog box

6. In the New User dialog box, enter the required information (username, full name, description, password, confirm password).



EMC strongly recommends that all user accounts assigned as Ionix ControlCenter users be given unique, hard-to-guess passwords.

7. Clear (uncheck) the User Must Change Password at Next Logon checkbox.

8. Click Create.

9. Repeat this procedure for each user requiring access to Ionix ControlCenter.

Creating a domain account for the ECC Server service

In some situations you will be unable to add domain users to Ionix ControlCenter because the ECC Server service is not a qualified domain user.

If you are unable to add domain users to Ionix ControlCenter, ask your Windows Domain Administrator to complete the following steps to create a new domain account for the ECC Server service:

1. On the domain controller, create or select an existing domain account.

Note: This account will be used exclusively as a service account for the ECC Server service.

2. On the ECC Server host, grant this account the Act as part of operating system user right.

3. On the ECC Server host, add this account to the local Administrators group.

Note: If steps 2 and 3 are not completed, you will not be able to connect to the server from the Ionix ControlCenter Console.

4. Make this account the service account for the ECC Server service.

5. Stop the EMC Web Applications Server, Store, and ECC Server services (in that order).

6. Start the services in the reverse order (ECC Server, Store, Web Applications Server).

7. Bring up the Ionix ControlCenter console and add the domain users you want to have access to Ionix ControlCenter (refer to “Adding a user to Ionix ControlCenter” on page 46).

Creating Ionix ControlCenter users 45


Adding a user to Ionix ControlCenterOnce users exist on a Windows host or as LDAP users, you can add them to Ionix ControlCenter. Adding a user to Ionix ControlCenter allows that user to log on to the Ionix ControlCenter application.

Add a user as follows:

1. From the Console tree, right-click ECC Users under Administration, Security Management, and select New. The User Definition (New) dialog box appears (refer to Figure 7 on this page).

2. Fill in the Login ID field in the form username for a local user or domain\username for a domain login ID (the Ionix ControlCenter Server must be a member of the domain or have an established trust relationship with the domain).

Note: The Ionix ControlCenter user ID in the Login ID field is the same as the name you entered in the Username field in Windows Administrative Tools shown in Figure 6 on page 44 or as the LDAP user.

3. Add a description of the login ID if desired.

Figure 7 New user definition

Note: You can change the Ionix ControlCenter login ID for a user, but it must have already been changed in the Username field in Windows Administrative Tools or through LDAP. Once the username is changed on the host or through LDAP, you can change the login ID through Ionix ControlCenter.

Once a user is added as a Ionix ControlCenter user, you set permissions for rules that control the user’s access to monitoring, managing, and controlling objects in the Ionix ControlCenter environment. Rules may apply to either individual users or groups of users as explained in the “Managing Ionix ControlCenter user groups” on page 47.



Managing Ionix ControlCenter user groupsUser groups save administrative time and effort by allowing you to manage rules for groups of users instead of for individuals. This section provides procedures for:

◆ “Creating a new user group” on page 48

◆ “Adding a user to a group” on page 48

Note: Refer to the online help topic: "Administering ControlCenter users, Working with user groups" for detailed procedures about managing user groups.

Managing Ionix ControlCenter user groups 47


Creating a new user group

Create a new user group as follows:

1. From the Console tree, right-click ECC User Groups under Administration, Security Management, and select New. The User Group Definition (New) dialog box appears.

Figure 8 Creating a new user group

2. Type the name of the new group and a description, and click OK. The new group appears under ECC User Groups.

3. Populate the user group by clicking and dragging users from ECC Users to the new group.

4. You can also create a user group from within the rule creation dialog box by right-clicking ECC User Group and proceeding with steps 1 through 3.

Adding a user to a group

A user may be added to an ECC user group by using the mouse to drag the user from the ECC Users folder to the group.

In the following example, a user named JSmyth was added to the Symmetrix Configuration Manager Group.



Figure 9 Adding a user to a group

Removing the eccadmin user from Ionix ControlCenterThe eccadmin account must be used to initially log on to Ionix ControlCenter because no other Ionix ControlCenter users exist at that point. However, eccadmin is an anonymous account, which means that anyone logging into it can perform any function without revealing their identity in log files.

Note: It is desirable (but not necessary) to limit or eliminate eccadmin as a Ionix ControlCenter login account.

The eccadmin user cannot be removed from the ECCAdministrators group until another user is added to the group (the group cannot be deleted and must always have at least one member). Once you add another user to the ECCAdministrators group, the eccadmin account is no longer required and may be removed as follows:

Note: The new Ionix ControlCenter user must already be a valid account on a Windows host or as an LDAP user.

1. Add a user to the ECCAdministrators group as outlined in “Managing Ionix ControlCenter user groups” on page 47.

Removing the eccadmin user from Ionix ControlCenter 49


2. Log out of the Console and log back in as the user you just added to the ECCAdministrators group.

3. From the Console tree, expand Administration, Security Management, ECC Users.

4. Right-click eccadmin and select Delete.

A message appears asking if you really want to delete the user eccadmin.

5. Click Yes.

The eccadmin account is deleted from Ionix ControlCenter.

The corresponding user account for eccadmin that exists on the ECC Server host (or as an LDAP user) may be left in place in case there is ever a need to add the eccadmin user back into Ionix ControlCenter for maintenance purposes.

Creating and modifying rules for users and user groupsRules allow you to control what a user or user group can do to specified objects. A user or user group can only have one rule applied to it. You can modify a rule by editing (adding or deleting) the permissions, renaming the rule, or deleting the rule.

Note: Refer to the online help topic: "Administering ControlCenter users, Working with authorization rules and permissions" for detailed procedures.

You can create a new rule with the following steps:

1. From the Console tree, expand Administration, Security Management.

2. Right-click the user or user group for which no rule exists, and select Authorization, New Rule.



Figure 10 Creating a new rule

Note: If the user or user group is already mentioned in a rule, this option does not appear.

The Rule Definition for User Group (or User, depending on whether you are creating a rule for a user or user group) dialog box appears, as shown in Figure 11 on page 52.

Creating and modifying rules for users and user groups 51


Figure 11 Naming the new rule

3. Enter a name for the rule.

4. Under Choose Objects (located above the left panel), select either Groups/Instances or Types depending on the kind of objects you are creating.

If a group of objects, object instance, or object type is selected, the available permissions appear under the middle panel (Available actions).

5. Select one or more of the permissions and click > to place them in the rule.

6. Click OK to write the new rule to the database.

Note: Once a rule is created containing a user or user group, no additional rules may be created for it. However, existing rules may be edited to remove permissions or grant additional ones.

Monitoring and contacting Console usersIonix ControlCenter allows members of the ECCAdministrators group to monitor Console use as well as to send messages to Console users.



Note: Only members of the ECCAdministrators group can monitor Console use or send messages to other Console users. Refer to “Adding a user to a group” on page 48 for the steps required to add a user to a group.

Monitoring Console users

Ionix ControlCenter allows members of the ECCAdministrators group to monitor Console use through the At A Glance view. Ionix ControlCenter displays the user IDs that are currently logged on, the name and IP address of the host, and the time they logged on.

You access the status of Ionix ControlCenter users as follows:

1. Click the At A Glance button in the toolbar to display the At A Glance view, and then click Show All to display all of the At A Glance charts.

2. In the ECC Status chart, click the Consoles bar.

3. On the Drill Down By toolbar, click Consoles. The Consoles view with the current Ionix ControlCenter users appears.

Sending messages to Console users

Ionix ControlCenter allows members of the ECCAdministrators group to send messages to other console users. You can broadcast a message to a specific user or group of users before performing actions that could be disruptive to other users, such as placing a configuration lock on a Symmetrix or stopping a Ionix ControlCenter agent.

The message appears immediately in the Consoles of those users, on top of all other windows. They cannot reply to it, nor is it logged.

To send an immediate notification to a user:

1. From the Consoles view (that you accessed in the previous steps), right-click the user to whom you want to send the notification and select Consoles, Send Message. The Send ECC Console Message dialog box appears.

2. Type the message and click OK. The message cannot exceed 200 characters.

Monitoring and contacting Console users 53



CHAPTER 3Administering Ionix ControlCenter Data Collection Policies

This chapter provides a brief overview of the tasks involved in administering data collection policies, and consists of the following sections:

◆ Data collection overview .................................................................................. 55◆ Managing data collection policy definitions and templates............................... 56◆ Agent data collection policy reference .............................................................. 59

Data collection overviewData collection policies (DCPs) are a formal set of statements used to manage the data collected by most Ionix ControlCenter agents. The policies specify the data to collect and the frequency of collection. Each agent has associated predefined collection policies and collection policy templates, which can be managed through Ionix ControlCenter Administration.

Data collection policy definitionsPredefined data collection policies are provided automatically with each agent. You can edit, copy, or delete predefined collection policies.

Data collection policy templatesData collection policy templates provide default values for the creation of new collection policies. Ionix ControlCenter provides at least one template for each policy. You can define your own policies by modifying the collection policy templates.

Enabling data collection policiesAgent data collection is performed differently for each agent. Some agents:

◆ Start data collection automatically upon startup.

◆ Require manual configuration to collect data.

◆ Require that data collection policies are defined, assigned, and enabled to manage how and when the data is collected.

Administering Ionix ControlCenter Data Collection Policies 55

Administering Ionix ControlCenter Data Collection Policies

Scheduling data collection policiesYou can optimize the scheduling of data collection to avoid overtaxing the ECC Server with too much data at one time by using the Schedule Discovery Utility.

Understanding the Schedule Discovery Utility

The Schedule Discovery Utility generates a report of recommended times to schedule when discovery of the Host Agents for AIX (MAR), HP-UX (MHR), Linux (MLR), Solaris (MSR), and Windows (MNR), and the Common Mapping Agent (EGZ) should take place to avoid performance issues. Processing too many discovery policies at the same time causes performance issues for the ECC Server. This version of the scheduling utility works for EMC Ionix ControlCenter 6.x.

The report generated by this utility helps you decide how to configure the Discovery data collection policies (DCPs) for the various agents.

The Schedule Discovery Utility is installed automatically as part of the infrastructure installation and is installed on the Server host in the <ECC_INSTALL_ROOT>\tools\utils\DCPScheduler\ directory, where <ECC_INSTALL_ROOT> is the location where Ionix ControlCenter is installed.

On EMC online support website, download the EMC Ionix ControlCenter 6.1 Schedule Discovery Utility Technical Notes. This document contains instructions on how to run the Schedule Discovery Utility.

Managing data collection policy definitions and templatesYou can define a new data collection policy based upon a predefined policy or policy template, and edit, copy or delete existing collection policies. You can also edit a policy template. Once the policy settings are defined or modified, you can apply the policy to specific managed objects.

Note the following additional resources:

◆ Refer to the Console online help for detailed step-by-step procedures for all data collection policy procedures.

◆ For environments with many hosts and arrays, refer to the EMC Ionix ControlCenter Planning and Installation Guide, Volume 1, or EMC Ionix ControlCenter Planning and Installation Guide, Volume 2 (MVS Agents).



Policy management optionsManaging the data collection policies consists of:

◆ Assigning Data Collection Policies — Each agent is assigned a set of predefined policies and a set of policy templates. You can define new data collection policies from a predefined policy or from a policy template.

◆ Editing Data Collection Policies — You can edit all settings for an existing data collection policy; however, you can only edit the schedule and properties defined by the data collection policy templates.

◆ Copying Data Collection Policies — You can use the copy policy function when you want to have more than one data collection policy with similar settings.

◆ Deleting Data Collection Policies — You can only delete policies in the Policies Definitions branch of the Administration tree. Data collection policy templates cannot be deleted.

◆ Viewing Data Collection Policies — You can create a tabular view of specific data collection policies and template settings.

Accessing data collection templates and policiesIn general, collection policies for a specific agent are accessed as follows:

1. From the Console tree panel, expand Administration, Data Collection Policies, Policy Definitions, and the specific agent folder. An example follows:

Managing data collection policy definitions and templates 57


Figure 12 Selecting a policy to modify

Note: If the agent folder does not contain the policy you want to assign, expand the Policy Templates folder under Administration, Data Collection Policies, and then expand the agent folder to find the appropriate policy template. Use this policy template to create the DCP. Refer to the online help topic "Creating new policies from a template" for instructions.

2. Right-click the policy you are modifying or assigning and select Edit Data Collection Policy.... The Policy Definition dialog box appears (Figure 13 on page 59).



Figure 13 Policy definition dialog box

3. Click the Actions tab and then the Edit button to edit, for example, the schedule for this DCP.

4. Click OK when you complete your edits to the DCP.

Agent data collection policy referenceThe following tables list agents and their data collection policies (DCPs). If an agent is not listed, it means that data collection is managed using another process. Refer to the specific agent overview topic in the online help for detailed information.

Agent data collection policy reference 59


Note: Basic DCPs that are created by default when the agent is started are found in the Policy Definition folder. If a DCP is not in the Policy Definition folder, then it has not yet been defined for the agent and can be created using the apropriate template located in the Policy Templates folder. Refer to “Accessing data collection templates and policies” on page 57 for more information.

Table 2 Backup agent DCPs

AgentsDCP templates available

Default DCP available Y/N

Enabled by default Y/N Default schedule

AIX Backup Agent for NetBackupAIX Backup Agent for NetWorker™AIX Backup Agent for TSMHP-UX Backup Agent for NetBackupHP-UX Backup Agent for NetWorkerHP-UX Backup Agent for TSMSolaris Backup Agent for NetBackupSolaris Backup Agent for NetWorkerSolaris Backup Agent for TSMWindows NT Backup Agent for NetBackupWindows NT Backup Agent for NetWorkerWindows NT Backup Agent for TSM

Discovery Y Y Every day at 4 a.m.

Table 3 Common agent DCPs

AgentDCP templates available



Workload Analyzer Archiver WLA Retention Y Y Agent controlled



Table 4 Connectivity agent DCPs

Agents DCP templates available



Symmetrix SDM Agent Discovery Y Y Every 12 hours

Masking Configuration Y Y Every 6 hours

Fibre Channel Connectivity Agent

Device Validation Y Y Every hour

Fabric Validation Y Y Every hour

Historical Data Y N Every day at 12 a.m.

WLA Daily Y N Every 15 minutes

WLA Revolving Y N Every 15 minutes

Discovery Scan N N Every 30 minutes

Performance Statistics N N Every 15 minutes

WLA Analyst N N Every 15 minutes

Table 5 Common Mapping Agent DCPs

Agent DCP templates available



Common Mapping Agent DB2Hosta, b

InformixSqlServerSybase

N N Every day at 12 a.m.

a. If you want to perform only monitoring functions on hosts, consider using the Common Mapping Agent and enabling the Host DCP instead of running a host agent on each host. Use of Common Mapping Agent improves host performance and reduces overhead, but keep in mind that Common Mapping Agent does not support active commands, real-time explore, or alerts.

b. You can have either the Discovery data collection policy for a given host agent enabled or you can have the Host DCP for the Common Mapping Agent enabled, but you cannot have both enabled on the same host at the same time. Note that the Host agent Discovery DCP starts by default when the Host Agent is installed and started.



Table 6 Database agent DCPs




Database Agent for Oraclea WLA Analyst Y N Every 15 minutes


WLA Revolving N N Every 15 minutes

Oracle Agent Data Collection N N Once per day at 6 a.m.

a. The database agent for Oracle has two additional default settings that must be turned on for the Oracle database instance to be fully discovered. From within the Policy Definition dialog box, click the Source tab and set Collect Configuration and Collect Allocation to Yes.

Table 7 Host agents for AIX, HP-UX, Linux, and Solaris DCPs




Host Agent for AIX Discovery Y Y Every day at 4 a.m.

File Level Collection N N Every day at 2 a.m.

Watermarks for File Systems Y Y Every 15 minutes

Watermarks for Logical Volumes

Y Y Every 15 minutes

Watermarks for Volume Groups




WLA Analyst N N Every minute



Host Agent for HP-UX Discovery Y Y Every day at 4 a.m.










Host Agent for Linux Discovery Y Y Every day at 2 a.m.










Table 7 Host agents for AIX, HP-UX, Linux, and Solaris DCPs (continued)






Host Agent for Solaris Discovery Y Y Every day at 2 a.m.










Table 7 Host agents for AIX, HP-UX, Linux, and Solaris DCPs (continued)






Table 8 Host Agent for Windows DCPs




Host Agent for Windows Discovery Y Y Every day at 12 a.m.

Discover UNC Y Y Every day at 2 a.m.

File Level Collection N Every day at 2 a.m.

File Level Collection for UNC Connections

N N Every day at 2 a.m.




Watermarks for Volume Groups Y Y Every 15 minutes




Table 9 Physical agent DCPs




Physical Agent for MVS MMP Data Collection Y Y Every day at 2 a.m.






Table 10 EMC Invista Agent




EMC Invista™ Agent Discovery Y Y Every day at 12 a.m.

Table 11 Storage agent DCPs




Storage Agent for Centera™ Discovery Y Y Every day at 12 a.m.

Storage Agent for CLARiiON Discovery Y Y Every day at 12 a.m.




Storage Agent for HDS Discovery Y Y Every day at 12 a.m.




Storage Agent for HP StorageWorks

Discovery Y Y Every day at 12 a.m.

Storage Agent for ESS Discovery Y Y Every day at 4 a.m.

Storage Agent for NAS Discovery Y Y Every day at 12 a.m.






Storage Agent for SMI Discovery for CLARiiON Y Y Every 8 hours

Discovery for ESS Y Y Every 8 hours

Discovery for HDS Y Y Every 8 hours

Discovery for StorageArray Y Y Every 8 hours

Discovery for StorageWorks Y Y Every 8 hours

Discovery for Symmetrix Y Y Every 8 hours

Discovery for TapeLibrary Y Y Every 8 hours




Storage Agent for Symmetrix Alert Polling Y Y Every 2 minutes

BCV/RDF Status Y Y Every 5 minutes

CLI Generator Y Y Every day at 12 a.m.

Configuration Y Y Every 10 minutes

Historical Data Y Y Every day at 12 a.m.

Local Discovery Y Y Every day at 12 a.m.

Performance Statistics Y Y Every 2 minutes

Real-time BCV/RDF Status Y Y Every minute



Proxy Discovery N N Every day at 12 a.m.


Table 11 Storage agent DCPs (continued)






Table 12 VMware agent DCP




VMware ESX Discovery Y Y Every day at 12 a.m.

Initial Discovery Y Y Every 5 minutes

CheckVCForServers Y Y Every hour


CHAPTER 4Configuring and Managing Alerts and Notifications

This chapter provides an introduction to alerts and monitoring for the Ionix Ionix ControlCenter administrator. Administrative tasks involve the mechanics of setting alerts and notifications, directing them to specific personnel, configuring automated responses (autofixes), and troubleshooting alerts that do not trigger as expected. The chapter also describes best practices so that alerts processing provides the maximum benefit without redundancy or system impact.

For user information on how to view and respond to alerts and how to apply alerts to host resources, refer to the "Monitoring Alerts and Notifications" online help topic.


◆ Understanding alerts and notifications............................................................. 69◆ Setting up your alert and notification strategy .................................................. 74◆ Creating alerts and notifications....................................................................... 78◆ Creating alert definitions .................................................................................. 81◆ Controlling alert spikes .................................................................................... 84◆ Sending alerts in Email or to a management framework.................................... 85◆ Automating alert responses with autofixes ....................................................... 86◆ Best practices for configuring and managing alerts........................................... 90◆ Troubleshooting alerts and autofixes................................................................ 92

Understanding alerts and notificationsIonix ControlCenter allows you to monitor hundreds of metrics about your storage environment—one example is the I/O rate of a Symmetrix director. For each metric, you can set values at which you want Ionix ControlCenter to notify you—for example, when the I/O rate exceeds 15,000 operations per second. The EMC Ionix ControlCenter Alerts Matrix lists all of the metrics.

You have several options for how Ionix ControlCenter notifies you. The most significant choice is whether you want to receive a notification or both an alert and a notification.

Configuring and Managing Alerts and Notifications 69

Configuring and Managing Alerts and Notifications

Alerts and notifications appear in different parts of the Console; alerts appear in the Alerts view, as shown in Figure 14 on this page; notifications populate the At A Glance views, as shown in Figure 15 on page 70.

Figure 14 Alerts view

The Alerts view provides a very detailed look at issues in your environment and offers many tools for tracking the issues to resolution.

Figure 15 At A Glance Health and Performance views



The At A Glance views provide a higher-level perspective by dividing your environment into categories such as storage array performance or host capacity. For the At A Glance views, Ionix ControlCenter consolidates related alerts and notifications into charts that indicate the status of the various categories.

Alert and notification life cycles

Figure 16 demonstrates the alert and notification life cycles using a file-size metric. This section also introduces important terminology.

Understanding alerts and notifications 71


Figure 16 Alert and notification life cycle

Stage 4

Metric

Example:File Size

Alert Definition 1

MyImportantFile.txtFatal alert >= 100 MBCritical alert >= 80 MB

Warning alert >= 60 MB

Alert Definition 2

MyOtherFile.txtMinor notification >= 50 MB

Information notification >= 30 MB

Alert History View

Alert and notificationappear at last severity levels

MyImportantFilereaches 61 MB

MyOtherFilereaches 31 MB

File reaches 83 MB: alert changes to Critical: management policy and

autofixes run again

MyImportantFilereaches 54 MB

MyOtherFilereaches 25 MB

Alert data retention period ends and alert andnotification are cleared from view and

ControlCenter Repository

Stage 1

Stage 2

Stage 3

Stage 5

Stage 6

Stage 7CC-000140

Alerts View

Warning alertappears

At A Glance View

Information notificationcontributes to Host

Capacity chart

Alert Template

Metric + defaulttrigger values,

management policy,and schedule

Management policy steps execute (including e-mail and SNMP notifications) and autofixes run



Note: Table 13 on page 73 describes the stages in Figure 16 on page 72.

Table 13 Alert and notification life cycle stages

Stage 1

Ionix ControlCenter can monitor hundreds of metrics about your storage environment, such as file size, the I/O rate of a Symmetrix Director, or the status of a daily backup operation. The online help and the EMC Ionix ControlCenter Alerts Matrix provide complete descriptions of each metric.

Stage 2

In the Console, the Administration, Alert Management branch of the tree provides alert templates for each metric that Ionix ControlCenter can monitor. The templates are organized by agent.The templates provide default values at which alerts and notifications will trigger. The template also specifies a schedule that determines how often Ionix ControlCenter will evaluate alerts and notifications. There is one template for each metric, and you can edit the default values.In addition to trigger values and a schedule, you can specify a management policy, which indicates who should be notified when an alert or notification triggers, and autofix, which is a script that runs automatically the first time an alert triggers. The autofix will not run again until the alert is cleared.

Stage 3

You can create multiple alert definitions from a template. An alert definition specifies which object to monitor (for example, the filename for a file-size alert) and on which hosts or storage systems. In the alert definition, you specify whether Ionix ControlCenter should send a notification only, or both an alert and a notification when the monitored object exceeds the trigger values.For the trigger values, schedule, and management policy, you can use the template values or modify them as necessary.

Stage 4

When a monitored resource exceeds a trigger value, Ionix ControlCenter triggers the alerts and notifications that you have turned on. Alerts are sent to the Alerts view. Notifications are sent to the At A Glance views. In addition, Ionix ControlCenter executes the management policy steps (such as sending an alert to an Email address or SNMP framework) and runs any autofixes attached to the alert.

Stage 5

If the resource exceeds the next trigger value, Ionix ControlCenter updates the display of that alert or notification in the view (for example, changing the color and icon of an alert in the Alerts view, or adding length to the critical bar in an At A Glance view chart and removing length from the warning bar).In addition, the management policy steps and autofixes run again.

Stage 6

When the resource falls back under the trigger values you defined, Ionix ControlCenter removes the associated alerts and notifications from the Alerts and At A Glance views. You also can clear alerts and notifications manually from the views. Some alerts and notifications must be cleared manually.After an alert is cleared, it appears in the Alert History view. The alerts appear at the severity level at which they were cleared. For example, if an alert was critical when it was cleared, then it appears as a critical alert in the Alert History view. In the Alerts or Alert History view, right-click the alert and select Alerts, History to view all the changes to the alert, such as severity changes, assignments, and the creation of notes.

Stage 7Alerts remain in the Alert History view for the period defined in the alert data retention policy. By default, the policy is disabled and alerts remain indefinitely.

Understanding alerts and notifications 73


Understanding metric types

There are two primary types of metrics: state metrics and count metrics. State metrics measure whether a condition is true or false (for example, whether a backup completed successfully). Count metrics measure whether a monitored condition has met a specific numeric value (for example, whether a file system has exceeded a specific size or the rate of a device has fallen below some value).

Within the three primary metric categories (health, capacity, and performance), health metrics are typically state metrics and capacity and performance metrics are count metrics.

After you install and enable an agent, the health metrics for that agent are typically enabled by default and the capacity and performance metrics are disabled.

In addition to state and count metric types, Ionix ControlCenter has interval and rate metrics. Interval metrics monitor the number of times an event occurs within a specified time range. For example, if an alert definition has a schedule of 15 minutes and 10 as the trigger value, then the condition must occur 10 times within 15 minutes for an alert to trigger. Rate metrics monitor the number of times a condition occurs every second. For example, if an alert definition specifies 100 as the trigger value, the condition must occur 100 times per second for an alert to trigger. The Alert Definition dialog box indicates the type of each metric.

For more explanation of metric types, refer to the topic "Understanding alert types" in the online help.

Setting up your alert and notification strategyDevelop a strategy for how you want to use alerts and notifications in your data center. Create standards for the configuration and resolution of alerts and communicate them to all Ionix ControlCenter users.

Consider the following issues:

◆ “Controlling who creates and edits alerts and notifications” on page 75

◆ “Deciding whether to define alerts or notifications” on page 75

◆ “Defining the severity levels” on page 76

◆ “Establishing procedures for the resolution of alerts” on page 76

◆ “Refining alert definitions” on page 77



◆ “Keeping alerts and notifications” on page 78

Controlling who creates and edits alerts and notifications

Decide whether you want all users to be able to create and edit alert definitions or whether a single or group of administrators will create and edit all alert definitions.

To create alert definitions, a user must have the Edit Alert Definition permission for the Alert object type. To edit a specific alert definition, the user must have the Edit Alert Definition permission for that alert definition or for the Alert object type. Grant this permission to users who you want to be able to create and edit alert definitions. Allow users to edit alert definitions for which they are responsible, but not other alert definitions.

To clear an alert from the Alerts or Notifications views, a user must have the Clear Alerts permission for the Active Alert object type.

You can also control access to management policies, autofixes, and schedules.

Refer to “User access management procedures” on page 42 for specific procedures for assigning permissions.

Deciding whether to define alerts or notifications

You can define a metric to appear as a notification only or as both a notification and an alert.

Define an alert if you anticipate tracking an issue to resolution. Define a metric as a notification only if you want a metric to contribute to an overall picture of your environment, but you do not want to track the issue to resolution.

Or, you can configure the metric to appear as both an alert and notification under certain conditions and as a notification only for less severe conditions.

Setting up your alert and notification strategy 75


Defining the severity levels

For each metric, you can specify five unique trigger values, with each assigned a different severity level. Create standards in your data center for the types of conditions that correspond to the different severity levels. Table 14 provides recommendations.

Establishing procedures for the resolution of alerts

Ionix ControlCenter provides several tools in the Alerts view to help track alert resolution. Decide whether and how you will use these tools and communicate alert resolution procedures to all users.

Table 14 Defining alert severity levels

Icon in Alerts view

Severity level Possible meaning Examples

Fatal A resource critical to the daily operation of your organization has failed or cannot perform at an acceptable level. The alert requires immediate attention.

A critical volume or file system is out of space.A critical process has failed.

Critical A critical resource is failing or its performance is severely degrading. The alert requires immediate attention to ensure the resource can continue to perform or does not fail.

A high disk queue is affecting the performance of a critical application.The memory performance of a critical server is poor.

Warning The performance or availability of a resource is nearing an unacceptable range. Monitor the resource carefully and possibly take action.

The free space in a database tablespace is below an acceptable threshold.A Symmetrix subsystem raised an environmental alarm.

Minor An abnormal event occurred. The event may indicate current or future problems.

The daily backup of a nonessential file system did not occur.A Symmetrix subsystem issued an error message.

Information Use this severity level for informational messages.

The backup of a critical resource completed successfully.A device mapping changed.



Acknowledging alertsUsers can acknowledge a new alert to indicate that someone is working on resolving the alert. In the Alerts view, the alert text changes from bold to plain text and the new alert count in the upper-right corner of the Console decreases. In addition, the name of the user who acknowledged the alert is recorded in the Acknowledged By column of the Alerts view.

Decide who should acknowledge alerts: the Ionix ControlCenter or alert administrator, team leaders who assign the alerts to other users, or any user.

If you do not want to use the acknowledge-alert feature, you can hide this column in the Alerts view.

Assigning alertsEstablish whether you will assign alerts to individual users or user groups and who will assign the alerts (an administrator, team leader, and so on). The name of the user or group appears in the Assigned To column of the Alerts view.

You can change the user or group after you initially assign the alert. One strategy is to assign alerts to a user group and then have the team leader of the group reassign the alert to a team member.

Users can sort or filter the Alerts view by the Assigned To column.

If you do not want to use the alert-assignment feature, you can hide this column in the Alerts view.

Recording alert notesCreate standards for how you will use alert notes. You can add a note to an alert when you acknowledge, assign, or clear it or at any other time.

If you use notes to document how you resolve alerts, you can later search the notes to help resolve new alerts of the same type.

Refining alert definitions

Creating alert definitions is an iterative process. After an alert triggers, review the alert history to ensure you have defined the alert effectively. This is especially important after you create an alert definition.

Look for the following opportunities to optimize the alert definition:

Setting up your alert and notification strategy 77


◆ Determine whether trigger values and severity levels are set appropriately. For example, ensure that the trigger values are not set too low, causing the alert to trigger too frequently.

◆ Determine whether you can configure some alerts to appear as notifications instead of alerts, thereby reducing the number of alerts that appear in the Alerts view.

◆ Notice whether the alert is spiking (frequently exceeding a trigger value and then returning to normal levels). If so, adjust the trigger values or set spike-controlling values that prevent the alert from triggering until it exceeds a trigger value for several consecutive intervals.

◆ Notice how quickly users respond to an alert. Determine whether the alert schedule is appropriate considering the user response. For example, if users typically respond to an alert after several days, then a schedule that evaluates the alert every hour may not be necessary.

Keeping alerts and notifications

After you clear an alert from the Alerts view or a Notification from the Notifications view, Ionix ControlCenter keeps it in the Alert History view. The length of time Ionix ControlCenter keeps the alert or notification in the Alert History view depends on the Alert data retention policy. By default, the Alert data retention policy is disabled, and Ionix ControlCenter keeps resolved alerts indefinitely.

Refer to the topic "Defining data retention policies" in the online help for specific procedures on defining data retention policies.

Creating alerts and notificationsAfter you gather the necessary information, set alerts and notifications in the Administration branch of the selection tree. Review the EMC Ionix ControlCenter Alerts Matrix, which lists all the metrics provided by Ionix ControlCenter, to determine which metrics you want to monitor.

In addition, determine if any existing schedules and management policies meet the needs of the resources you want to monitor. If they do, you can attach the given schedule and management policy to the alert definition you create. If not, you can create a custom schedule, management policy, or both.



Tips for setting alerts and notifications

Use the following tips to set alerts and notifications:

◆ Set more than one alert of a given type.

◆ Monitor similar resources together using the same alert, which will have the same schedule and management policy.

◆ For resources managed by different teams or individuals, create separate alerts with different management policies.

◆ Use separate alerts for resources of different levels of importance.

◆ For critical resources, use a more frequent schedule.

◆ Use wildcards to restrict alert processing to limited sets of resources. For example, do not set an alert to monitor the size of all files on a system.

Getting help

When you are creating or modifying an alert definition in the Alert Definition dialog box, click Help to find out more about the alert.

Descriptions of all alerts are also available through the online help table of contents. To access the Help:

1. Select EMC ControlCenter Help from the Help menu.

2. On the Contents pane of the Help Navigator dialog box, expand Alert Descriptions and then expand the node for the desired agent.

After an alert triggers, you can right-click the alert in the Alerts view or Alert History view and select Alerts, Help to get help on responding to some specific alerts.

Creating alerts and notifications 79


Gathering information

Table 15 describes the information you need to gather to set alerts for file systems, directories, and files. See the online help for detailed requirements for individual alerts. The EMC Ionix ControlCenter Alerts Matrix lists all the alerts that Ionix ControlCenter provides.

Table 15 Gathering information for file systems, directories, and files

Information needed Description Instructions Notes

Hosts Hosts that need to be monitored

List the hosts you want to monitor.

Other types of alerts may check multiple hosts, but file-system and file alerts are best reserved for a single host.

Source Resources to be monitored

List the file systems, directories, files, and disks you want to monitor on each host.

Explore hosts for their file systems, directories, important files, and disks.

Conditions Trigger values and alert severities

For each resource, determine the values that should trigger alerts. • File systems and disks:

Determine the threshold free space and percentage free space.

• Files and folders: Determine triggers for size, change in size, and percent change in size.

Consider multiple thresholds for alerts of increasing severity: warning, critical, and fatal.

To help you determine trigger values, use recent data for resource free space and size. Also, consult the user of the resource.



Creating alert definitionsYou can use one of the following procedures to create an alert definition:

◆ “Creating an alert definition from a template” on page 81

◆ “Creating alert definitions in the Edit Thresholds dialog” on page 82

◆ “Copying an alert definition” on page 82

Once you create an alert definition, be sure to test it using the procedure outlined in “Testing an alert definition” on page 83.

As described in “Controlling who creates and edits alerts and notifications” on page 75, you must have the Edit Alert Definition permission for the Alert object type or for specific alerts to create alert definitions.

Creating an alert definition from a template

To create an alert definition:

Schedule Frequency that the alert conditions are evaluated

For each resource, determine:• How often the alert condition

should be checked.• The days of the week on which

the alert condition should be checked.

Critical or faster-growing resources should be checked more often (every 5 to 60 minutes). Others should be checked less often to decrease alert processing (every 60 to 360 minutes).

Management policy

Names and Email addresses of personnel to notify

Determine whom an alert should notify automatically:• In the Console.• By Email.• By page.• In a framework product.

You can limit the display of alerts to the Consoles of administrators with responsibility for the affected systems or applications. You can configure alerts to send Email to key personnel at appropriate times.

Autofix Automated responses to alerts, including predefined or user-defined commands and scripts

Determine an automated action that would help resolve the alert. Assemble any scripts or commands that the alert could issue when triggered.

Table 15 Gathering information for file systems, directories, and files

Information needed Description Instructions Notes

Creating alert definitions 81


1. In the selection tree, expand Administration, Alert Management, and Alert Templates.

The alert templates appear, organized by agent or component.

2. Expand the tree to view the templates for the agent that supplies the metric you want to use.

3. Continue expanding the tree until you reach the alert template.

4. Right-click the template, and then click New.

The Alert Definition dialog box appears.

5. On the Source tab, specify which resource you want to monitor (for example, a file or a tablespace and table in a database). You must complete all fields, and you can include wildcards. Click Help for field definitions. (Some alerts have no fields on this tab.)

6. On the Conditions tab, select levels and values at which you want Ionix ControlCenter to issue alerts and notifications.

7. On the Actions tab, specify the schedule and, optionally, a management policy and autofixes.

8. On the Apply To tab, select the objects Ionix ControlCenter should monitor, such as a particular storage system, host, file system, or device.

Creating alert definitions in the Edit Thresholds dialog

You can also create alert definitions using the Edit Thresholds dialog box. The Edit Thresholds dialog box allows you to create or modify multiple alert definitions at one time. In addition, the dialog box shows the category for each metric. The category determines in which At A Glance view chart a notification will display (for example, Storage System Performance or Host Capacity).

To access the Edit Thresholds dialog box, right-click any object and select Alert Thresholds, Edit Thresholds.

Copying an alert definition

If similarly managed objects have slightly different monitoring needs, you can copy an alert definition and modify the settings as necessary. This prevents having to create a second alert definition from scratch.

To create an alert definition by copying an existing alert definition:



1. In the selection tree, expand Administration, Alert Management, and Alert Definitions.

2. Expand the folder for the agent for which you want to create the alert definition.

3. Locate the alert definition you want to copy by expanding the subfolders.

4. Right-click the alert definition and select Copy As.

The Alert Definition dialog box appears.

5. Modify the definition as necessary.

Testing an alert definition

After you create an alert definition, test it to ensure that it triggers correctly for the desired resources.

To test an alert definition:

1. In the upper-right portion of the Console, view the current number of active alerts.

2. Edit the alert you want to test. The Alert Definition dialog box appears.

3. On the Conditions tab, select Information.

4. Specify a trigger value that is guaranteed to trigger the alert. For example, specify a free space percentage of less than 99, or a file size greater than 1.

5. In the Actions tab, select a schedule of Minute_05. This will cause Ionix ControlCenter to check the condition within 5 minutes of editing it. Click OK.

Note the following:

• Ionix ControlCenter checks alert conditions immediately when you create an alert, but when you edit an alert, it checks conditions at the end of the schedule interval.

• Some alerts require two iterations of the schedule before they can be evaluated, such as alerts that measure growth over time. You will have to wait longer for these alerts to fire when testing.

6. In the upper-right portion of the Console, click All Alerts. Within a few minutes, the alert should trigger and the number of active alerts should increase.

7. Locate the new alert. In the Alerts view, click the time and date column headings to sort the alert to the top.

Creating alert definitions 83


8. Verify the following:

• The resource that triggered the alert is one that is monitored by the alert you set.

• The trigger value and severity matches those of the alert you set.

Controlling alert spikesIonix ControlCenter provides a way for you to prevent alerts from triggering when a resource temporarily exceeds a trigger value, called an alert spike. For example, if a user creates a temporary file that causes the free space on a volume to drop below a trigger value, you may want to know about the condition only if the free space remains low for several hours and not when it temporarily dips. You can control these spikes using the Before and After fields in the Alert Definition dialog box and the schedule attached to the alert.

To prevent an alert from triggering when spikes occur:

1. In the selection tree, expand Administration, Alert Management, and Alerts.

2. Expand the folder for the agent to which the alert you want to edit belongs.

3. Expand the subfolders to locate the alert.

4. Right-click the alert and select Edit. The Alert Definition dialog box appears.

5. Click Conditions.

6. In the Before boxes, specify the number of consecutive times that the alert conditions must exist before Ionix ControlCenter triggers the alert.

7. In the After boxes, specify how many times, after an alert has triggered, that the alert must evaluate to false before Ionix ControlCenter removes the alert.

8. Click Actions.

9. From the Schedule list box, select a schedule to indicate how often Ionix ControlCenter should evaluate the alert.

Note that you also can access the Alert Definition dialog box from the Alerts view. Right-click the alert that is spiking and select Edit Definition. Then modify the Before and After values.



Sending alerts in Email or to a management frameworkOften, alerts trigger when you are not at the Ionix ControlCenter Console. To ensure you receive notification of critical alerts in a timely manner, set up Ionix ControlCenter to send alert messages by Email or to a management framework like HP OpenView Network Node Manager or Computer Associates Unicenter TNG.

To set up Ionix ControlCenter to send events to a management framework or Email:

1. To send Email, the Ionix ControlCenter administrator must configure Ionix ControlCenter for SMTP notification. This is typically done during installation of the ECC Server.

To send an event to a management framework, the Ionix ControlCenter administrator must configure Ionix ControlCenter to send SNMP traps to a management framework during installation and configuration of the ECC Server.

2. Create a management policy.

In the Management Policy Definition dialog box, drag the Email icon or SNMP icon into the management policy (and for Email, specify the address).

3. Specify the Email address.

When an Email management policy is set for an alert and the alert is triggered or moves from one severity to another, Ionix ControlCenter sends an Email notification. To receive the Email notification on a specific Email address, modify the value of the flag email from in the ecc_server.ini file located in the %ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\data folder.If you do not specify the Email address, the default value, EMC_Control_Center@<SMTP Host Name> is used. The value for <SMTP Host Name> is configured in the ecc_server.ini file.

4. Attach the management policy to an alert.

Each time the alert triggers or moves from one severity to another, Ionix ControlCenter sends the Email or SNMP trap.

For complete instructions on configuring Ionix ControlCenter to work with a third-party framework application, refer to the EMC Ionix ControlCenter Integration Packages Product Guide.

Sending alerts in Email or to a management framework 85


Automating alert responses with autofixesThrough autofixes, Ionix ControlCenter allows you to specify commands or scripts that should run when an alert triggers.

Note: To execute an autofix on a host in response to an alert, the agent issuing the alert must be running on the host.

Autofixes consist of a unique name, a descriptive name, and the text of the command or script Ionix ControlCenter sends to the host when an alert triggers. Ionix ControlCenter provides some autofixes; you can also create autofixes from new or existing scripts, batch files, or executables.

Configuring an autofix consists of three primary steps:

1. Creating the autofix definition in the Console.

2. Creating the autofix script on the host.

3. Attaching the autofix to an alert.

You must be a member of the ECCAdministrators user group to create autofix definitions in the Console.

Creating an autofix definition in the Console

To create an autofix definition:

1. In the selection tree, expand Administration, Alert Management, and Autofixes.

2. Right-click User and select New. The Autofix Definition dialog box appears.

3. Type a brief but unique name in Internal Name. This name cannot contain spaces.

4. Type a brief description in Display Name. This field can contain spaces but should not be too long as it appears in many tables throughout the interface.

5. In Command, type the syntax of the command or the name of a script or batch file.

When an alert triggers, the host agent uses the text exactly as it appears in this field. You can also pass alert information to your autofix commands. Refer to “Autofix syntax” on page 88 for complete information.



Ionix ControlCenter executes an autofix the first time an alert or notification to which the autofix is attached triggers or moves from one severity to another, whether the alert or notification increases or decreases in severity. The autofix will not execute again until the alert is cleared.

Passing alert information to an autofix script

Ionix ControlCenter allows you to pass the following information with your autofix command:

◆ Metric name

◆ Alert severity level

◆ Value that caused the alert to trigger

◆ Key values related to the alert, such as the name of the resource for which the alert triggered

Use the following syntax to pass this information with your autofix command:

your_autofix_command &METRIC &LEVEL &KEY &VALUE

&METRIC is the metric name.

&LEVEL is the severity level of the alert, in string format: Fatal, Critical, Warning, Minor, or Information.

&KEY is a value, such as a subsystem ID or filename, that Ionix ControlCenter passes when the alert triggers. These are the same values that appear in the alert message in the Alerts view. On UNIX and Windows, if the alert has more than one key, then append a number within brackets to &KEY for each key you want to pass, for example: &KEY[1], &KEY[2], and so on. On MVS, Ionix ControlCenter passes the first key only.

&VALUE is the value at which the alert triggered.

The EMC Ionix ControlCenter Alerts Matrix lists the metric names and the messages that Ionix ControlCenter issues when alerts trigger. This document is available on the Ionix ControlCenter documentation CD-ROM.

Automating alert responses with autofixes 87


Autofix syntaxTable 16 on page 88 provides requirements and examples for specifying autofixes for UNIX, Windows, and MVS hosts.

Table 16 Autofix syntax requirements and examples

Platform Requirements and examples

UNIX Specify the file path and the name of a shell command, shell script, or executable.Ensure that files or programs referenced in a script are in the same directory as the script, or specify the complete path in the script.Examples/admin/tools/backup/backup.sh &KEY &VALUE /utility/cleanup/fixit.pl

Windows

Specify the name of a command, script, batch file, or executable.Include cmd.exe /c or cmd /c in front of the autofix string.If the script, batch file, or executable is not included in the Windows path, then specify the full path in the autofix command.Ensure that files or programs referenced in a script are in the same directory as the script, or specify the complete path in the script.Do not launch another GUI application from an autofix command. Doing so may cause the autofix to fail.Examples cmd.exe /c C:\utilities\cleanup.bat &METRIC &LEVEL &KEY[1] &KEY[2] &VALUE cmd /c C:\backup\delete.wsh cmd /c cp &KEY[1] C:\backup

MVS Specify the fully-qualified dataset name of the REXX executable or CLIST.Enclose the autofix within quotes. (Ionix ControlCenter submits autofixes as TSO commands.)Place the alert value substitutions outside of the quotes.Separate multiple commands with semicolons. Examples “system.utility.cleanup” &METRIC &VALUE &KEY “test.batch.restart(rexxfix)”



Creating an autofix script on the host

Use Perl, Javascript, or another scripting tool to create your autofix script on the host. Place the script in the directory that you specified when you created the autofix command in the Console.

If you plan to use the autofix on multiple hosts, you must place it in the same directory on each host, or create separate autofixes for each host. Before propagating the autofix to multiple hosts, create and test it on one host to make sure it works how you want.

Following is an example of a simple batch file autofix for a Windows host. The autofix accepts four parameters (%1 through %4) and writes them to a log file called alertinfo.txt.

@echo METRIC NAME: %1 >> alertinfo.txt@echo LEVEL: %2 >> alertinfo.txt@echo KEY 1: %3 >> alertinfo.txt@echo VALUE: %4 >> alertinfo.txt

In Ionix ControlCenter, the corresponding autofix command might look like this:

cmd /c C:\Autofixes\TestAutofix.bat &METRIC &LEVEL &KEY[1] &VALUE

After an alert to which the autofix is attached triggers, the alertinfo.txt log file would contain content like this:

METRIC NAME: MNR.FileSize.File.SizeLEVEL: FATAL KEY 1: MyMonitoredFile.txt VALUE: 100000

Use a simple autofix such as this to test your autofix scripts before copying them to multiple hosts. Simple scripts are also helpful in parsing the output returned by Ionix ControlCenter.

Attaching an autofix to an alert definition

To have an autofix run when an alert triggers, attach the autofix to the alert definition. The autofix runs when the alert first triggers. The alert must be cleared before the autofix will run again.

To attach an autofix to an alert:

Automating alert responses with autofixes 89


1. In the selection tree, expand Administration, Alert Management, and Alert Definitions.

2. Expand the folder for the agent that contains the alert to which you want to attach the autofix.

3. Expand the subfolders to locate the alert. Right-click the alert and select Edit Alert.

4. Click Actions.

5. Select the autofix in Available Autofixes.

6. Click Add.

7. Click Apply To.

8. Verify that you want the autofix to run on all the selected hosts or for the selected storage systems. The script, executable, or batch file specified in the autofix must exist in the same place on all hosts.

Best practices for configuring and managing alertsUse the following tips to configure and manage a system of alerts and notifications:

◆ Disable unnecessary or redundant alerts.

◆ Set alert frequencies to minimize processing impact.

◆ Use notifications to reduce the volume of alerts.

◆ Create user-defined groups to organize your alerts.

◆ Use management policies to notify personnel.

◆ Modify templates to facilitate alert creation.

Disable unnecessary or redundant alerts

When you install a new Ionix ControlCenter agent, a set of alerts and notifications for that agent are enabled by default. Review those alerts and notifications to ensure they are appropriate for your environment. Disable alerts and notifications for metrics that you do not want to monitor, or remove the managed object from the alert definition.



Set alert frequencies to minimize processing impact

Each alert definition has an associated schedule that determines how often Ionix ControlCenter checks the status of an object. Use the following techniques to minimize the impact of alert and data collection policy processing on the host CPU:

◆ Do not configure schedules to run more often than every 5 minutes.

◆ Do not assign the same schedule to too many alerts on the same host. As you increase the number of objects an agent is monitoring, extend the schedule to minimize processing impact.

◆ Disable alerts that you do not need.

◆ Configure schedules to run only on days and during hours when you need notification. For example, configure the schedule to run only during normal business hours.

Consult the EMC Ionix ControlCenter Planning and Installation Guide, Volume 1 or Volume 2 (MVS Agents) for duration and CPU usage statistics for data collection policies and alerts.

Use notifications to reduce alert volume

For any metric, you can enable both notifications and alerts. Notifications populate the At A Glance view, which uses charts to summarize the status of your environment or a subset of your environment, based on your selection. You can then drill down through the charts to identify specific problems. Alerts appear in the Alerts view, which lists problems in a table format.

Often, the number of active alerts in the Alerts view can seem overwhelming. Configure as notifications those metrics that do not require action. Use alerts for more critical problems that require immediate attention. For example, define the Information, Minor, and Warning levels as notifications and the Critical and Fatal levels as both notifications and alerts.

Create user-defined groups to organize your alerts

User-defined groups allow you to organize objects (such as hosts and storage systems) into logical groups based, for example, on geographic region, business units, or personnel assignments. In views such as Alerts and At A Glance, you can then show the alerts for a specific group.

Best practices for configuring and managing alerts 91


Use management policies to notify personnel

If you do not attach a management policy to an alert definition, the associated alerts and notifications appear for all Ionix ControlCenter users. Create management policies that send alerts and notifications to the people who need to see them.

Modify templates to facilitate alert creation

Each metric has an associated template that defines default parameters for new alert definitions. Edit the templates to specify the trigger values, management policy, and schedule that all alert definitions created from that template will have by default. You can then modify the alert definitions as necessary.

Troubleshooting alerts and autofixesThis section provides tips for troubleshooting the following alert and autofix problems:

◆ Too many alerts appear in Console

◆ Cannot create or edit alerts or changes not saved

◆ Cannot clear alerts

◆ Alert does not trigger as expected

◆ Autofix does not run

◆ Alert count differs among users

◆ Managed object has warning icon but no alerts

◆ Alert created/modified date and time is incorrect

Too many alerts appear in the Console

If too many alerts appear in your Alerts view, there are several steps you can take to reduce the display, such as applying management policies and disabling alerts that are not important to you.



Table 17 provides suggestions for reducing the number of alerts that display.

Cannot create or edit alerts or changes not saved

If you cannot create an alert, edit an alert, or save changes to an alert, check with the Ionix ControlCenter administrator to ensure your user ID has been assigned the necessary permissions.

Table 17 Reducing the number of alerts that display

Action Description

Disable all alert definitions, and then enable only those critical to you.

Many alert definitions are enabled by default when you install Ionix ControlCenter components. Although we identified these alerts as important, they may not be significant in your environment or for every system. Or, the default settings may not be appropriate.Refer to Enabling or disabling multiple alert definitions in the online help.

Disable unnecessary or redundant alerts.

Instead of disabling all alerts, review all enabled alerts and disable those that are not appropriate for your storage environment.Refer to the description on page 90 for more information.

Assign management policies. If you do not assign a management policy to an alert definition, the alert displays for all users when it triggers. Use management policies to direct alerts to appropriate personnel. For example, assign all of the ECC Server alerts to the Ionix ControlCenter administrator.Many alert definitions are preconfigured when you install Ionix ControlCenter components. However, these alert definitions do not have management policies attached. Make sure you assign management policies to them.

Clear resolved alerts. After you address a triggered alert, you can remove it from the Alerts view by clearing it for all users.For a specific procedure, refer to the topic "Clearing an alert whose condition has been resolved" in the online help.

Use notifications to reduce the volume of alerts.

Refer to the description on page 91 for more information.

Filter the Alerts view. Filter the view to show a subset of alerts, such as alerts created within the last day or of a specific type, such as Host Performance alerts. Click Filter on the view title bar to set the filter criteria.

View alerts by object or user-defined group.

View the alerts for a specific storage array, host, or other object or group of objects, such as an application group. Refer to the online help topic "Reducing the number of alerts that display" for more information.

Troubleshooting alerts and autofixes 93


Cannot clear alerts

To clear alerts from the Alerts view and notifications from the Notifications view, you must have the Clear Alert permission for the Active Alert object type. See the Ionix ControlCenter administrator to ensure your user ID has the necessary permissions.

Alert does not trigger as expected

Ensure that:

◆ You used correct syntax to specify the alert key (or source). For syntax rules, see the specific alert description in the online help.

◆ You attached a schedule to the alert.

◆ Enough time passed for Ionix ControlCenter to evaluate the alert. (For example, if you attached a schedule that causes Ionix ControlCenter to evaluate the alert every hour, wait for an hour to pass.)

◆ The alert is enabled and you selected at least one alert severity level.

◆ The alert's management policy is set up to notify your Console.

◆ The alert's spike controlling values are configured properly. The Before field in the alert definition indicates how many consecutive times an alert must evaluate to true before Ionix ControlCenter triggers the alert.

◆ Another user has not cleared or removed the alert (you can review the alert history to find out).

◆ There are no additional requirements for the alert. See the alert description in the online help for requirements.

Autofix does not run

If your autofix command does not run when the alert it is attached to triggers, ensure that:

◆ You have used the proper syntax to specify the autofix command.

◆ Files or programs referenced in a script are in the same directory as the script or have their complete path specified in the script.

◆ On Windows, you have included cmd.exe /c in front of the command and you have specified an executable.



Alert count differs among users

The All Alerts button in the upper-right corner of the Console displays:

◆ Total number of alerts.

◆ Total number of new alerts (new alerts are alerts that have not been assigned to a user or cleared from the Alerts view).

◆ Severity of the alert with the highest severity and the number of alerts at that severity.

These totals may differ among users if:

◆ The management policy attached to an alert definition specifies that an alert be sent to one user but not another.

◆ The management policy attached to an alert definition has changed since a user logged on to the Console. In this case, Ionix ControlCenter applies the management policy and updates the alert count accordingly the next time the user restarts the Console.

◆ If a user is running multiple Consoles, the alert count can differ in those Consoles depending on any management policy changes and the last time each Console was restarted.

Managed object has Warning Icon but no alerts

If a storage array, host, or other managed object has a Warning icon but no alerts appear for that object in the Alerts or At A Glance views, then the object may have had alerts previously, but the Console has not updated the object's icon. In this case, clear the Warning icon by right-clicking the object and selecting Refresh Alert Status to update the alert status.

If, after refreshing the alert status, the problem remains, verify that the managed object does not have alerts for which your user ID is excluded from the management policy.

Make sure that you are included in the list if the management policy specifies that an alert be sent to specific users. If you are not included, you will not see the alerts in your Alerts and At A Glance views even though a Warning icon appears on managed objects for which the alert triggers (This is the designed behavior).

Troubleshooting alerts and autofixes 95


Alert created or modified date and time is incorrect

When an alert is created (or updated) in the Alerts view on the Console, the time shown in the Alerts view for the creation (or update) of the alert is the local system time for the host running the agent for the managed object of the alert. If the local system time is incorrect, the time shown in the Alerts view will be incorrect. Maintain the correct date and time on your hosts to prevent this problem.


CHAPTER 5Maintaining the Repository

The Repository is a relational database that holds the current and historical data of both the storage environment and Ionix ControlCenter itself. This data includes configuration details about storage arrays, hosts, databases, statistical data for capacity planning, alerts, and detailed status information about any given device.


◆ Automatic tasks ............................................................................................... 97◆ Manual tasks ................................................................................................. 103◆ StorageScope Repository ............................................................................... 108

Automatic tasksThe following tasks are scheduled to run automatically at a specific time. The tasks can also be run manually at any time using the procedures provided in each section.

Note: After you complete installation of components on the Repository host, you must reboot the Repository host to enable automatic tasks.

Backing up the Ionix ControlCenter Repository

Backup is a database job that runs at 2:00 a.m. for hot backup, which you can expect to complete by 4:00 a.m., everyday. However, you can backup the Repository at any time as follows:

From the Start menu, select: Programs, EMC, EMC Control Center, Repository Maintenance, BackUp Database.

Note: The hot backup requires that the RAMBBACKUPDIR environment variable be defined to a directory with enough free space. The variable is defined during install to whatever value is supplied. This can be changed at a later date, if needed.

Maintaining the Repository 97

Maintaining the Repository

Historical information is purged automatically after 15 days. If you want to keep more data for any trend analysis or other statistics, you can change it from the Console. Make a copy of the backup on a daily basis onto tape or offsite storage to help with recovery, as it is overwritten the next day. Please note that the backup space requirements are approximately the same as the Repository.

Refer to “Restoring the Repository” on page 105 for information about restoring the repository in the event the database becomes corrupted.

Backing up the Ionix ControlCenter Repository using Third-Party Tools

If you have a requirement to backup the Ionix ControlCenter infrastructure server using third-party software, such as NetBackup, EDM, etc., the following should be considered.

Backups should be scheduled around the following automatic tasks:

◆ Hotbackup database job that runs daily at 2:00 a.m.

◆ Export Backup that runs daily at 10:00 p.m. (ramdb_export_db.bat)

◆ Backups from both of these jobs are stored in the RAMBBACKUPDIR environment variable directory.

For example, scheduling third-party backup after 3:00 a.m. or 11:00 p.m. (after the automatic tasks end) allows backup of the latest files from RAMBBACKUPDIR. You can determine the exact completion time of hot backup or export backup by looking at the timestamps of %RAMBOH%\admin\Ramb_Scripts\ramb_hotback.log and %RAMBBACKUPDIR%\exp\rambdb_exp.log.

When backing up the database components, the following open files need to be excluded from the backup process:

%RAMBOH%\oradata\rambdb\*.CTL

%RAMBOH%\oradata\rambdb\*.LOG

%RAMBOH%\oradata\rambdb\*.DBF

This also applies to any third-party monitoring tools, such as BMC Patrol, as the external locks that this tool places on files are intrusive to Oracle (refer to the Oracle website, www.oracle.com, for additional information).



For recovery purposes, when backing up the database components, the following files need to be included in the backup process:

%RAMBBACKUPDIR%\hot\*.*

%RAMBBACKUPDIR%\exp\*.*

%RAMBOH%\oradata\rambdb\archive\*.*

%RAMBOH%\database\PWD*.*

%RAMBOH%\database\SP*.*

%RAMBOH%\admin\rambdb\bdump\*.*

%RAMBOH%\admin\rambdb\udump\*.*

%RAMBOH%\admin\rambdb\pfile\*.*

Note: For details regarding backing up the StorageScope Repository using third-party tools, see Backing up the StorageScope Repository using Third-Party Tools in the StorageScope API and Repository Reference Guide.

Exporting the Repository backup

Export backup is a database job that runs at 10:00 p.m. every day. However, you can export the repository database any time as follows:

From the Start menu, select: Programs > EMC > EMC Control Center > Repository Maintenance > Export Database.

Note: In order for the Export Backup to work, the RAMBBACKUPDIR environment variable needs to be defined to a local directory which has sufficient free space. This variable is defined during the install to whatever value is supplied. This can be changed at a later date, if needed.

Two zip files are created when you run ramdb_export_db.bat:

rambdb_exp_dmp.zip which contains:ecc_getversion.logrambdb_exp.dmprambdb_exp.logREPOSITORY.lb (lockbox file)

Automatic tasks 99


rambdb_exp_notedmp.zip which contains:ecc_getversion.logrambdb_exp_notde.dmprambdb_exp_notde.log

The lockbox file named REPOSITORY.lb is used for Ionix ControlCenter secure access management. You will need to specify the location of all of these files if you ever need to import the database.

You can import this data back into the Repository in the event you need to restore the Repository to a previous point in time (all existing data in the Repository will be overwritten). Refer to “Importing the Repository database” on page 106 for more information.

Analyzing tables

This process is a scheduled database job to run at 11:00 p.m., every day. However, you can run Analyze Tables anytime with the following batch process:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_analyze_table.bat

Error files end in .err and complete output is listed in .log. The files are created in <Install_Root>\Repository\admin\Ramb_scripts.

When you run:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_analyze_table.bat

it creates the following files:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_analyze_table.log <Install_Root>\Repository\admin\Ramb_scripts\ramb_analyze_table.err

Rebuilding the index

This process is a scheduled database job that runs at 12:05 a.m., every Saturday. However, you can run Rebuilding Index anytime with the following batch process:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_rebuild_index.bat


When you run:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_rebuild_index.bat




<Install_Root>\Repository\admin\Ramb_scripts\ramb_rebuild_index.log <Install_Root>\Repository\admin\Ramb_scripts\ramb_rebuild_index.err

Recompiling invalid objects

This process is a scheduled database job that runs at 9:30 a.m., every Sunday. However, you can run Recompiling invalid objects at any time with the following batch process:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_recomp_invalid.bat


When you run:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_recomp_invalid.bat


<Install_Root>\Repository\admin\Ramb_scripts\ramb_recomp_invalid.log <Install_Root>\Repository\admin\Ramb_scripts\ramb_recomp_invalid.err

Monitoring tablespace growth

This process is a database job scheduled to run at 9:00 p.m., every day. However, you can run Tablespace Growth Monitoring at any time with the following batch process:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_freespace.bat


When you run:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_freespace.bat


<Install_Root>\Repository\admin\Ramb_scripts\ramb_freespace.log <Install_Root>\Repository\admin\Ramb_scripts\ramb_freespace.err

Automatic tasks 101


Monitoring the status of automated tasks

Ionix ControlCenter runs a batch process at 8:30 a.m. every day that creates a log file with the status of every automated Repository job (not jobs you ran manually) based on the current information that Oracle has for jobs. The ramb_jobstatus.log file provides the name of each job, how many times it has failed (if any), the last successful run time, the next scheduled run time, as well as if the job is not active.

Check the status of the automated Repository jobs at any time by running the following batch file and then viewing the log file:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_jobstatus.bat

Note: Opening the .log file in Wordpad provides the best format for viewing. This is applicable to all .log files.

Listing installed Ionix ControlCenter components

Ionix ControlCenter runs three automated tasks each morning to create report files containing lists of installed Ionix ControlCenter components. The report files are identical, except in the way that the lists are ordered.

The report files are:

◆ InstalledECCCompByComp.log — Display Ionix ControlCenter components based on components. Runs at 7 a.m. every day.

◆ InstalledECCCompByVer.log — Display Ionix ControlCenter components based on version. Runs at 7:10 a.m. every day.

◆ InstalledECCCompByHost.log — Display Ionix ControlCenter components based on host. Runs at 7:20 a.m. every day.

You can run these tasks anytime with one of the following batch processes:

<Install_Root>\Repository\admin\Ramb_scripts\InstalledECCCompByComp.bat

<Install_Root>\Repository\admin\Ramb_scripts\InstalledECCCompByVer.bat

<Install_Root>\Repository\admin\Ramb_scripts\InstalledECCCompByHost.bat



Manual tasksThe following tasks can be performed manually and should not be run without contacting your service representative:

◆ “Shutting down the Repository” on page 103

◆ “Starting the Repository” on page 103

◆ “Scanning the Repository Alert Log” on page 104

◆ “Cleaning trace files” on page 104

◆ “Determining Tablespace Fragmentation” on page 104

◆ “Determining which processes are currently running” on page 105

◆ “Resetting the Repository” on page 105

◆ “Performing a media recovery” on page 105

◆ “Restoring the Repository” on page 105

◆ “Importing the Repository database” on page 106

◆ “Gathering data for remote diagnostics assistance” on page 108

◆ “TCP/IP Service During Maintenance” on page 108

The scripts used to perform these tasks are located in the Ionix ControlCenter install root directory:

<ECC_Install_Root>\repository\admin\Ramb_Scripts\

Shutting down the Repository

You can shut down the Repository by completing either of the following methods:

◆ Run:

<ECC_Install_Root>\Repository\admin\Ramb_scripts\ramb_shutdown_db.bat

◆ On Windows, from the Start menu, select Programs, Administrative Tools, Services, OracleServiceRAMBDB, Stop.

Starting the Repository

If you shut down the Repository as described in the previous section, you can start the Repository through either one of the following methods:

Manual tasks 103


Note: During the Ionix ControlCenter installation, the Repository starts automatically.

◆ Run:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_start_db.bat

◆ On Windows, from the Start menu, select Programs > Administrative tools > Services > OracleServiceRAMBDB > Start.

Scanning the Repository Alert Log

To scan the Repository Alert Log, run the following:

findstr /I "ORA-" <Install Root>:\Repository\Admin\Rambdb\bdump\Alert_Rambdb.log

Note: If this file does not yet exist, a new file is created. If this file already exists, then the information is appended to the existing file each time the scan is run. EMC recommends that you rename and archive this file when it starts to grow large.

Cleaning trace files

To clean trace files, complete the following procedure:

Note: Be sure to rename the alert_ramdb.log file (located in the bdump directory) and save it to another location in case you need to check the log files.

1. Delete the old trace files from the following directories:

<Install_Root>\Repository\admin\ramdb\bdump<Install_Root>\Repository\admin\ramdb\udump

2. Delete any archive log files that are older than two days from:

<Install_Root>\Repository\oradata\ramdb\archive

Determining Tablespace Fragmentation

Execute the following to run the Tablespace Fragmentation task:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_tbspfrag.bat



Determining which processes are currently running

You can generate a log file listing the status of the processes running on the Ionix ControlCenter Repository database with the following task:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_process_info.bat

Resetting the Repository

Resetting the Repository will erase all data from the Repository! Contact EMC Customer Support for assistance.

Performing a media recovery

If the ECC Server cannot connect to the Repository and if you see ORA-01113 toward the end of the <Install_Root>\Repository\admin\rambdb\bdump\alert_rambdb.log, run the following script to perform a media recovery on the Repository.

Note: The script will not run properly from Terminal Services Client. Run this batch file on the Repository host itself.

<Install_Root>\Repository\admin\Ramb_scripts\ramb_mediarecovery.bat

If this procedure fails, proceed to the next section to restore the Repository.

Restoring the Repository

Use this procedure to restore a corrupted Repository database. You can restore the database to any point in time for which you have the hot backup copy and archive log files (refer to “Backing up the Ionix ControlCenter Repository” on page 97).

A two-step process is used to restore the database:

◆ Perform a Media Recovery — Usually the Repository can be repaired by running a media recovery script as outlined in the previous section.

◆ Restore the Database — If the media recovery is unsuccessful, then you can run a Repository restore script as detailed in this section.

Manual tasks 105


Note: The script will not run properly from Terminal Services Client. Run this batch file on the Repository host itself.

If you attempted to perform a media recovery and failed, use the steps in this section to restore the Repository.

This procedure requires a hot backup copy and archive log files to restore the database to a specified point in time.

1. Copy the following files into a new folder (for example Before_Restore_Files) in case the restore is unsuccessful and you require EMC Support:

<Install_Root>\Repository\oradata\rambdb\*.DBF <Install_Root>\Repository\oradata\rambdb\*.CTL <Install_Root>\Repository\oradata\rambdb\redo*.LOG

2. Copy your good hot backup *.dbf file to:

<Install_Root>\Repository\oradata\rambdb

3. Run the following script:

<Install_Root>\Repository\admin\Ramb_scripts\ramb_restore.bat

The script walks you through the restore procedure.

If this procedure does not work, contact Customer Support.

Importing the Repository database

In some situations, you may want to import data from a previously exported database (refer to “Exporting the Repository backup” on page 99). The Repository must be functioning properly to import a database. This is not a solution for resolving a corrupted database; use this procedure when you need to restore your Repository to a previously exported point in time.

Importing the Repository database will replace the existing database (including managed objects) with the previously exported database and its managed objects. Be sure to export and/or backup your existing database before attempting this procedure.

Import the Repository database as follows:



Note: In order for the Import to work, the RAMBBACKUPDIR environment variable needs to be defined to a local directory. This variable is defined during the install to whatever value is supplied. This can be changed at a later date, if needed.

1. Export and/or back up the existing Repository database using the procedures outlined in “Exporting the Repository backup” on page 99, and “Backing up the Ionix ControlCenter Repository” on page 97.

The exported files include the dump file as well as a lockbox file used as part of Ionix ControlCenter security.

2. Run the following script to import a previously exported Repository database:

<Install_Root>\Repository\admin\Ramb_scripts\ecc_import.bat

3. ecc_import.bat requires you to set parameters depending on whether or not you are importing the database back into the same or to a different database as follows:

• If importing the dump file back into the same database:

ecc_import.bat [Dump file folder location] [Dump File Name]

Example: ecc_import.bat c:\ecc ecc_export.dmp

• If importing the dump file into a different database, a third parameter is required to provide the location for the REPOSITORY.lb that is in the rambdb_exp_dmp.zip

ecc_import.bat [Dump file folder location] [Dump File Name] [lockbox folder location]

Example :

ecc_import.bat c:\ecc ecc_export.dmp c:\lockbox

Note: ecc_import.bat will import the full database dump with tables with encryption_password. The dump file will be rambdb_exp.dmp.

The script walks you through the import procedure.

Manual tasks 107


Gathering data for remote diagnostics assistance

EMC may require system and database log files to troubleshoot a remote customer’s Ionix ControlCenter issue. In this situation, EMC will request that you run the following job, which gathers system and database log information, and then creates a zip file:

<Install_Root>\Repository\admin\Ramb_Scripts\Ramb_RDA.bat

This creates a zip file named RDA.RDA_hostname.zip in the \Repository\rda\output folder.

TCP/IP Service During Maintenance

The TCP/IP service should be running during maintenance period.

If TCP/IP service is stopped as part of maintenance, then the MVS agents should also be stopped.

StorageScope RepositoryFor information about maintaining and troubleshooting the StorageScope Repository, refer to the EMC Ionix ControlCenter 6.1 StorageScope API and Repository Reference Guide.


CHAPTER 6Security

The EMC Ionix ControlCenter 6.1 Security Configuration Guide provides a brief overview of the security settings available in Ionix Ionix ControlCenter to ensure a secure operation of the product. This document provides specific security procedures.


◆ Changing Passwords on the Ionix ControlCenter Infrastructure........................ 109◆ Changing the Database Encryption Password ................................................. 111◆ Changing StorageScope Passwords................................................................ 112◆ Steps to Regenerate Certificates for Ionix ControlCenter 6.1............................ 112◆ File Authenticator Utility ................................................................................. 121◆ Trusted Entity Utility ....................................................................................... 123◆ Untrusting Ionix ControlCenter Components ................................................... 127◆ Alternative Certificate Setup for SMC Link and Launch .................................... 128

Changing Passwords on the Ionix ControlCenter Infrastructure

In order to change all Ionix ControlCenter infrastructure passwords, you need to:

1. Change the Ionix ControlCenter locksmith password using the PasswordChangeUtility.bat

This utility resides on the ControlCenter Server host in the following directory:%ECC_INSTALL_ROOT%\tools\utils\lspwdutils

2. Change the Repository passwords using passwd.exe

This utility resides on the ControlCenter Repository host in the following directory:%ECC_INSTALL_ROOT%\Repository\admin\Ramb_Scripts

3. Change the LDAP bind password (only if you are using LDAP authentication).

Security 109

Security

Change the Ionix ControlCenter Locksmith password

Change the Ionix ControlCenter Locksmith password as follows:

1. Open a DOS Window.

2. Change directory to:

%ECC_INSTALL_ROOT%\tools\utils\lspwdutils

3. Type: PasswordChangeUtility.bat -locksmith

Note: For more information about changing StorageScope passwords, refer to the EMC Ionix ControlCenter StorageScope API and Repository Reference Guide

Change the Repository passwords

Change the Repository passwords as follows:



%ECC_INSTALL_ROOT%\Repository\admin\Ramb_Scripts

3. Type: passwd.exe ECCALL

4. Restart all Ionix ControlCenter component services (or continue to the next step to change the LDAP bind password if you are using LDAP authentication).

Change the LDAP bind password

If you are using LDAP Authentication do the following to change the LDAP bind password:

Note: An updated PasswordChangeUtility.bat is available as a Patch through EMC online support. You must apply this Patch before updating the Ionix ControlCenter LDAP bind password.



%ECC_INSTALL_ROOT%\tools\utils\lspwdutils


Security

3. Type: PasswordChangeUtility.bat -ldap <password>

4. Restart all Ionix ControlCenter component services.

Changing the Database Encryption PasswordResetting the Ionix ControlCenter Repository Encryption Key should only be done when you believe the encryption key wallet may have been tampered with. If you are not sure, please contact your EMC service representative before proceeding.

This section describes how to use the ramb_passwd_encryption.bat utility to reset the Ionix ControlCenter Repository encryption key.

Make sure you run a complete database backup immediately after you run the ramb_passwd_encryption.bat utility (both ramb_export_db.bat and ramb_hotbackup.bat) to ensure you have a backup that matches the new encryption key.

Procedure to reset the Repository Encryption Key

Note: All batch files mentioned in this section are found in %ECC_INSTALL_ROOT%\Repository\admin\Ramb_scripts.

1. Stop all ECC component services except for:

• OracleECCREP_HOMETNSListener• OracleServiceRAMBDB

2. Open a Command Prompt.

3. Run ramb_passwd_encryption.bat ENCRYPTION.

4. Immediately run ramb_export_db.bat and ramb_hotback.bat.

5. Close the Command Prompt.

6. Start all Ionix ControlCenter component services stopped in Step 1.

Changing the Database Encryption Password 111

Security

Changing StorageScope Passwords For more information about changing StorageScope passwords, refer to the EMC Ionix ControlCenter StorageScope API and Repository Reference Guide.

Steps to Regenerate Certificates for Ionix ControlCenter 6.1

You MUST read this entire section BEFORE you begin following the procedures herein! The procedures in this section will IMPACT your Ionix ControlCenter environment SIGNIFICANTLY!

Regenerating Certificates for Ionix ControlCenter 6.1 should not be done without good cause. If you have ANY QUESTIONS or are NOT SURE you should regenerate certificates, please contact your EMC Service Representative BEFORE proceeding!

If you need to change the Ionix ControlCenter root trust certificate and redistribute it to all Ionix ControlCenter components, then follow the steps as presented in this section.

The general process for regenerating and redistributing certificates is as follows:

1. Stop the services.

Stop all the EMC services before implementing the steps and let the repository service be up till the passwords are reset.

• EMC ControlCenter API Server

• EMC ControlCenter Server

• EMC ControlCenter Store


• EMC ControlCenter Performance Manager Reports

• EMC StorageScope server

• EMC ControlCenter Repository

• EMC ControlCenter Web Server

• EMC ControlCenter WebApplications Server


Security

• EMC ControlCenter WebConsole Server

• EMC ControlCenter Key Management Server

• EMC ControlCenter Master Agent

• EMCSymmetrixVssProvider

2. Stop the component.

3. Delete the certificate files.

4. Start the component.

5. Be sure that component is Trusted.

Before you begin following the procedures in this section to Regenerate Certificates, backup Ionix ControlCenter.

For complete Backup Steps, refer to the EMC Control Center 6.1 Planning and Installation Guide, Volume 1.

DO NOT PROCEED if you have not completely reviewed this entire section "Steps to Regenerate Certificates for ControlCenter 6.1" and fully understand the implications of doing so!If you have any questions or are not sure, please contact yourEMC Service Representative BEFORE proceeding.

Turn the trust_all Flag On

With Ionix ControlCenter 6.1 all components are installed as trusted, by default. During the installation process, it is recommended that the trust_all flag be turned off, refer to the EMC Ionix ControlCenter Planning and Installation Guide, Volume 1 for more information.

To perform the steps necessary to regenerate certificates, it is recommended that the trust_all flag be turned back on.

To turn the trust_all flag on do the following:

1. Modify the ECCSecurityConfig.Properties file located at:

Steps to Regenerate Certificates for Ionix ControlCenter 6.1 113

Security

%ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\class

2. Add trust_all to the Global.TrustedHostFilter field.

3. Save the file.

4. Restart the Ionix ControlCenter Server.

Ionix ControlCenter Repository Host

To run the Ionix ControlCenter Password Reset Utility:


2. Change directory to: %ECC_INSTALL_ROOT%\Repository\admin\Ramb_Scripts

3. Type: reset_lsmith_passwd.bat RESET

StorageScope Server Host


5. Change directory to: %ECC_INSTALL_ROOT%\Tomcat\webapps\srm\conf\

6. Type:emcsts_reset_password.bat embedded

(This depends on which type of Repository you have installed.)

Once you perform Steps 7 -13 below, you will loose all control over the managed objects in your Ionix ControlCenter environment including all Hosts, Switches, and Storage Arrays. You will also loose all Alerting and WLA Data Collections. These capabilities will remain unavailable until you perform Steps 66-69 later in this section on EVERY HOST in your environment!

Ionix ControlCenter Server Host

7. Stop the ControlCenter Server service. From the Windows Start menu, select Settings, Control Panel, Administrative Tools, Services.

8. In the Services window, ensure that the Status of the EMC ControlCenter Server service is Stopped. If necessary, right-click the service name and select Stop.


Security

9. Delete the server lockbox files, server.*These files are located at: %ECC_INSTALL_ROOT%\ecc\lockbox


11. Change directory to: %ECC_INSTALL_ROOT%\tools\utils\lspwdutils

12. Type: PasswordChangeUtility.bat -locksmith

13. Delete trust.ks file located at:

%ECC_INSTALL_ROOT%\ecc\ecc_inf\data\ECC_inf_Hostname\safe

Ionix ControlCenter Services

14. Stop the following Ionix ControlCenter services. From the Windows Start menu, select Settings, Control Panel, Administrative Tools, Services.

15. In the Services window, ensure the Status of the following services is Stopped. If necessary, right-click each service and select Stop.






• EMC StorageScope Server


• OracleServiceRAMBDB

• OracleECCREP_HOMETNSListener

• OracleServiceEMCSTSDB


Note: The services should be stopped on all hosts they are running on.


Security

ControlCenter KMSServer/ControlCenter Repository Host

16. Delete all files located at:%ECC_INSTALL_ROOT%\ecc\dbSafe

DO NOT delete the%ECC_INSTALL_ROOT%\ecc\dbSafe\TDE folder.

17. Delete the kmsserver.* files located at: %ECC_INSTALL_ROOT%\ecc\lockbox

18. Run the Key Management utility.

a. Open a DOS Window.

b. Change Directory to: %ECC_INSTALL_ROOT%\ecc\tools\utils\keymgmt

c. At a Command Prompt enter:keymanagementutility.bat

d. Type:keymanagementutility -generate -trust -override -silent

19. Start the Ionix ControlCenter Repository and KMS Server services:





Note: In case of a server lockbox corruption or a case where the server certificate has to be regenerated, run the KeyManagementUtility using the -resetServerTrust option.


20. Start the ECC Server service: EMC ControlCenter Server


Security

Ionix ControlCenter Store Host

21. Delete the store.* files located at: %ECC_INSTALL_ROOT%\ecc\lockbox

22. Delete the trust.ks file located at:

%ECC_INSTALL_ROOT%\ecc\ecc_inf\data\ECC_inf_Hostname\safe

Note: If the Ionix ControlCenter Server and Store are on the same host, you already deleted the trust.ks file in “Ionix ControlCenter Server Host”.

23. Start the Ionix ControlCenter Store service: EMC ControlCenter Store

ECCAPI Server Host

24. Delete the apiserver.* files located at: %ECC_INSTALL_ROOT%\ecc\lockbox

25. Delete the trust.ks file located at: %ECC_INSTALL_ROOT%\ECCAPIServer\safe

26. Start the Ionix ControlCenter API Server service: EMC ControlCenter API Server

Ionix ControlCenter Console

27. Delete the console.* files located at:

%USERPROFILE%\ecc\data\<hostname>\lockbox

Where %USERPROFILE% is the user’s working environment, and <hostname> is any Ionix ControlCenter Server host name that you connect to.

28. Delete the trust.ks file located at:

%USERPROFILE%\ecc\data\<hostname>\safe

Where %USERPROFILE% is the user’s working environment, and <hostname> is any Ionix ControlCenter Server host name that you connect to.

29. Restart the Console. This is required for every machine you have a Console installed on.


Security

StorageScope Repository Host

Note: If the StorageScope Repository resides on the same host as the Ionix ControlCenter Repository, skip steps 30-33, they were already performed in “ControlCenter KMSServer/ControlCenter Repository Host” on page 116.


31. Open a DOS prompt.

32. Change directory to: %ECC_INSTALL_ROOT%\tools\utils\webkeymgt

33. Type:WalletGenerationUtility.bat DSS

34. Start the following services:



StorageScope Server Host

Note: If the StorageScope Server resides on the same host as the Ionix ControlCenter Repository or the StorageScope Repository, skip steps 35-38, they were already performed in previous steps.


36. Open a DOS prompt.

37. Change directory to: %ECC_INSTALL_ROOT%\tools\utils\webkeymgt

38. Type:WalletGenerationUtility.bat STS

39. Delete the WEB.lb files located at: %ECC_INSTALL_ROOT%\lockbox

40. Perform the step “Ionix ControlCenter Web Server (Tomcat)” on page 119 on the StorageScope Repository host.

41. Change directory to:Tomcat\webapps\srm\conf\


Security

42. Type:emcsts_changepassword.bat embedded | external

(this depends on which type of StorageScope Repository you have installed.)

43. Restart EMC ControlCenter Web Server.

44. Start EMC ControlCenter StorageScope Server.

Ionix ControlCenter Web Server (Tomcat)

The Ionix ControlCenter Web Server exists on the Ionix ControlCenter Server, StorageScope, and ECCAPI Server host(s).

45. Delete the trust.ks file in the following locations: %ECC_INSTALL_ROOT%\Tomcat\conf %ECC_INSTALL_ROOT%\Tomcat\shared

46. Delete the keycert.ks file located at: %ECC_INSTALL_ROOT%\Tomcat\conf

47. Delete the TOM.lb.* files located at: %ECC_INSTALL_ROOT%\lockbox

Note: If Tomcat is not installed on the same host as StorageScope, then you should delete the WEB.lb files located at %ECC_INSTALL_ROOT%\lockbox. Otherwise skip this, as this action was performed in “StorageScope Server Host” on page 118

48. Start the Web Server.

StorageScope MSA

49. Start the EMC ControlCenter STS MSA Web Server.

Web Console (ECCAPI Client)

50. Delete the <hostname>_ApIClient_keystore.ks file located at: %ECC_INSTALL_ROOT%\lockbox

51. Delete the <hostname>_ApIClient_trust.ks file located at: %ECC_INSTALL_ROOT%\lockbox

52. Login into the Web Console.This process will regenerate these files again.


Security

EACLI

53. Delete the <hostname>_EaCli_keystore.ks file located at: %ECC_INSTALL_ROOT%\lockbox

54. Delete the <hostname>_EaCli_trust.ks file located at: %ECC_INSTALL_ROOT%\lockbox

55. Login into the EACLI.This process will regenerate these files again.


It is assumed that all agents are not trusted until their authenticity is verified by the Ionix ControlCenter security administrator. Therefore, it is recommended that the trust_all flag be turned off when working with agents.

To turn the trust_all flag off do the following:

56. Modify the ECCSecurityConfig.Properties file located at:

%ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\class

57. Remove trust_all from the Global.TrustedHostFilter field.

58. Save the file.

59. Restart the Ionix ControlCenter Server.

Ionix ControlCenter Agents

60. Stop the Master agent and all Ionix ControlCenter agents on the host.

As an example on a Windows platform, do the following:


62. Change directory to a specific agent: %ECC_INSTALL_ROOT%\exec\<agent directory>

Note: Reference the Port Usage Appendix located in the EMC Ionix ControlCenter 6.1 Planning and Installation Guide, Volume 1 for a complete list of agentType acronyms.

63. Delete the following files:

• agent.pem• sdk.clb• sdk.clb.bak


Security

• TrustCert.pem• sdk.clb.FCD (found in agent version 6.1.0.0.179 or higher)• sdk.clb.bak.FCD (found in agent version 6.1.0.0.179 or higher)

Note: Repeat this step for all agents on the host including the Master agent.

64. Restart the Master Agentwhich starts all the other agents on the host.

65. Repeat steps 60-64 on ALL Agent Hosts.

Performance Manager Client

Note: If the Performance Manager Client is installed on the same host as the Ionix ControlCenter Repository, StorageScope Repository, or the StorageScope Server, you do not have to delete the wallet files, skip steps 66-69.


Do not delete the%ECC_INSTALL_ROOT%\ecc\dbSafe\TDE folder.


68. Change directory to:%ECC_INSTALL_ROOT%\tools\utils\webkeymgt

69. Type:WalletGenerationUtility.bat PMC

Note: Please note that the Performance Manager Client should not be launched until “Ionix ControlCenter Agents” on page 120 has been performed as there is a correlation between Performance Manager and the Master Agent.

File Authenticator UtilityThe File Authenticator Utility is a digital signing utility. Use this utility if an install or zip file in the Media Repository is unsigned.

File Authenticator Utility 121

Security

Installation

The File Authenticator Utility is installed automatically on the Ionix ControlCenter Server host in the <ECC_INSTALL_ROOT>\tools\utils\fileauth directory. <ECC_INSTALL_ROOT> is where the Ionix ControlCenter is installed.

Signing files

To sign files in the Media Repository:

1. Open a cmd window on the ECC Server host.

2. Change the directory to:<ECC_INSTALL_ROOT>\tools\utils\fileauth

3. Run the following command:

FileAuthenticatorUtility.bat -sign <Media Repository file>

The File Authenticator digitally signs the file followed by -sign option. If the -sign option is followed by a directory name then the File Authenticator signs all files in the directory filtered by extensions. For example,

FileAuthenticatorUtility -sign <File/Dir Full Name> [ -r ][ -filter <Extension Extension ...> ]

If the -r parameter follows the -sign <Dir Full Name> option then it recursively signs all files in the directory and its subdirectories filtered by extensions.

Examples The following are File Authenticator Utility command samples:

FileAuthenticatorUtility -sign < ECC INSTALL ROOT>\media_rep\remoteinstall\MNR520\MNR520.zipsigns MNR520.zip file

FileAuthenticatorUtility -sign < ECC INSTALL ROOT>\media_rep\remoteinstall\MNR520 -filter pl zipsigns all ".pl" and ".zip" files in MNR520 folder

FileAuthenticatorUtility -sign < ECC INSTALL ROOT>\media_rep\remoteinstall -r -filter pl zip xmit txtsigns all ".pl" ,".zip", "xmit", "txt" files in remote install folder and its subfolders recursively.


Security

Trusted Entity UtilityThe Trusted Entity Utility performs trust management. Use this utility as an alternative to the Ionix ControlCenter Console Trust Manager GUI interface or if the GUI interface is not available.

The Trusted Entity Utility allows a user to create, update, or delete the trust status of host and agent entities. A host or agent entity’s trust status can be set to Trusted, Untrusted, or Neutral.

Note: The trust status of the Ionix ControlCenter Server host cannot be modified. This is always trusted by default. All components that reside on the Server host will be trusted as well.

The Trusted Entity Utility is located in the Ionix ControlCenter root install directory on the Repository host.

C:\%ECC_INSTALL_ROOT%\tools\utils\TrustedEntityUtil\trustedEntityUtil.bat

Note: The Global.TrustedHostFilter setting in the Ionix ControlCenter ECCSecurityConfig.properties file is set to trust_all by default. This allows for easy installation of Ionix ControlCenter components. To run Ionix ControlCenter in its most secure mode and to allow the Trusted Entity Utility trust status settings to take affect and persist to the Ionix ControlCenter Respository, the trust_all value of the Global.TrustedHostFilter setting in the Ionix ControlCenter ECCSecurityConfig.properties file must be deleted.

Turn off the trust_all flag:

1. Modify the ECCSecurityConfig.properties file located in:%ECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\class

2. Delete trust_all from the Global.TrustedHostFilter setting.

3. Save the ECCSecurityConfig.properties file.

To run the Trusted Entity Utility, follow these steps:

1. Open a DOS command prompt on the Server host.

2. Migrate to the following directory:\%ECC_INSTALL_ROOT%\tools\utils\TrustedEntityUtil

3. Enter the following command:

Trusted Entity Utility 123

Security

trustedentityutilThe menu in Figure 17 appears:

Figure 17 trustedEntityUtil main menu

4. Follow the instructions in the following sections to manage your trust relationships.

5. Restart the Ionix ControlCenter Server service after running this utility.

Updating Trusted Entity status

To execute an update operation choose option 1. When prompted, specify the complete path name of a file with entities to be updated, such as C:\ECC\ecc_inf\data\ecc_inf_hostname\data\entities.txt.

The entities in the file should be listed one per row. Each row defines 5 parameters of the entity. Each parameter is separated by a single comma. The following shows the format of an entity record in the trustedEntityUtil input file:

<Hostname>,<IPaddress>,<entityType>,<agentType>,<trustStatus>

In this format:

◆ hostname is the host name of the entity to be updated.

◆ IPaddress is the IP Address of host. The Trusted Entity Utility supports IPv4 and IPv6 formats.

Note: If the hosts/agents you are making changes to are already known to Ionix ControlCenter, the IP address is not needed. In this case, it is recommended to perform an export first, and then simply import the same file after making any desired

Use the following table to select the option that best reflects your needs:

1. Update hosts' status in Database2. Export records from Host and TrustedEntity tables

into a file.3. Delete TrustedEntity objects from Database.

Please, make a choice (default is 1):


Security

changes. If the hosts/agents you are making changes to are not currently known to Ionix ControlCenter, then the IP address is required so that Ionix ControlCenter can properly handle those entries."

◆ entityType is Host or Agent.

◆ agentType is a 3-letter acronym of the entity. agentType is not used for the Host entity

type. For a complete list of valid acronyms, refer to "Appendix A - Port Usage and Firewall

Configuration" of the EMC ControlCenter Planning and Installation Guide, Volume 1.

◆ trustStatus is Trusted, Untrusted, or Neutral. See the Ionix ControlCenter online help for a description of these three settings.

If you do not specify the IPaddress or agentType in an entity record, use double-commas between parameters to signify an empty parameter as follows:

<hostname>,,<entityType>,,<trustStatus>

Example EntityInput file

Figure 18 shows an example entity input file:

Figure 18 trustedEntityUtil input file

Exporting Trusted Entity records

To export TrustedEntity records from the Ionix ControlCenter Repository to a text file, specify the trustedEntityUtil command without parameters.

trustedEntityUtil

The generated file will reside in the current directory, and have the name trustedEntityExport.txt.

You can use this generated file as a template to add other entities before performing an update or delete operation.

Host1,168.159.0.1,Host,,TrustedHost2,168.159.0.2,Agent,STS,TrustedHost2,168.159.0.2,Agent,PMR,TrustedHost2,168.159.0.2,Agent,EGN,Neutral

Trusted Entity Utility 125

Security

Deleting Trusted Entity records

To delete TrustedEntity objects from the Ionix ControlCenter Repository, choose option 3. When prompted, specify the complete path name of a file with entities to be deleted, such as C:\ECC\ecc_inf\data\ecc_inf_hostname\data\entities.txt.

The format of the input file for a delete operation is identical to the file format for an update operation. See “Exporting Trusted Entity records” on page 125 for information on the input file format.

Trust Status Export UtilityThe Trust Status Export Utility provides an audit trail of trust status modifications made to host or agent entities using the Trust Manager GUI interface, the Trusted Entity Utility, or the Ionix ControlCenter Server.

The Trust Status Export Utility is located in the Ionix ControlCenter root install directory on the Repository host.

C:\%ECC_INSTALL_ROOT%\tools\utils\TrustStatusExportThe Trust Status Export Utility creates a .csv file called TrustStatus_Report.csv containing every trust status modification made to host or agent entities in the Ionix ControlCenter Repository using the Trust Manager GUI interface, the Trusted Entity Utility, or the Ionix ControlCenter Server.

The Trust Status Export Utility also creates a .txt file called TrustStatusExp_Debug_Log.txt. The debug log can be analyzed in the event of a problem creating the TrustStatus_Report.csv.

Both files are created when you run the TrustStatusExport.bat batch file and are stored in the same directory as the utility.

Note: The TrustStatus_Report.csv and the TrustStatusExp_Debug_Log.txt files are over-written each time you run the batch file. If you want to save the contents of a particular run of the batch file, be sure to rename the TrustStatus_Report.csv and the TrustStatusExp_Debug_Log.txt files right after you run the batch file.


Security

Untrusting Ionix ControlCenter ComponentsIf you change the status of a Ionix ControlCenter component from trusted to untrusted in the Trust Manager dialog box, you also have to delete the trust certificate and the signed certificate for each component.

Refer to Table 18, “Location of Keys and Files,”for more information.

If the ContorlCenter Repository resides on the same machine with any of the following:

◆ StorageScope Server

◆ StorageScope Repository

◆ Performance Manager Client

do not change the trust status of these components. If any of these components reside together on another machine then the trust status, by default, is the same for these components. You cannot have different trust status settings for these components on the same machine.

Table 18 Location of Keys and Files

Component Location of Keys Filename(s)

Console %USERPROFILE%\ecc\data\hostname\lockbox%USERPROFILE%\ecc\data\hostname\safe

CONSOLE.*Trust.ks

Store %ECC_INSTALL_ROOT%\lockboxECC_INSTALL_ROOT%\ecc_inf\data\ecc_inf_hostname\safe

STORE.*Trust.ks

API Server %ECC_INSTALL_ROOT%\lockbox%ECC_INSTALL_ROOT%\ECCAPIServer\safe

APISERVER.*Trust.ks

Agents C:\ECC\exec\<agent dir> agent.pemTrustCert.pem

Performance Manager Desktop Client

%ECC_INSTALL_ROOT%\dbSafe All files, except TDE directory

API Client %ECC_INSTALL_ROOT%\lockbox <host>_ApiClient_keystore.ks<host>_ApiClient_trust.ks

API CLI %ECC_INSTALL_ROOT%\lockbox <host>_EaCli_keystore.ks <host>_EaCli_trust.ks

Untrusting Ionix ControlCenter Components 127

Security

Alternative Certificate Setup for SMC Link and LaunchTwo scripts allow you to generate and use your own security certificate for ControlCenter/SMC communication if you do not want to use the security mechanism provided at install time.

Ionix ControlCenter Setup


2. Change directory to:C:\Program Files\ecc\console\WSLaunch

3. Type:genkey -generate -alias <alias> -password <password> -userKeystore <filename.keystore> -file <filename.cer> -defStorePath <path>

Where: alias=the alias for new private/public key pair.password=password for generating new private key.userKeystore=name to be given to generated user keystore.file=name to be given to generated certificate which will contain the new public key.defStorepath=path to directory containing default (existing) keystore and truststore files, for example:

%USERPROFILE%\Admin\ecc\data\<SERVER>\safe\

StorageScope Repository

%ECC_INSTALL_ROOT%\dbSafe All files, except TDE directory

Tomcat %ECC_INSTALL_ROOT%\Tomcat\conf

%ECC_INSTALL_ROOT%\Tomcat\shared

Trust.ksKeycert.ks

Trust.ks

Web Applications

%ECC_INSTALL_ROOT%\Tomcat\shared Trust.ks

Table 18 Location of Keys and Files (continued)

Component Location of Keys Filename(s)


Security

Expected output

User keystore has been created.

One certificate has been created.

One key has been added to the default Store.

4. Copy the generated certificate to the SMC Server host. This is the host location where the SMC Application has been installed. Please refer to your SMC documenttion for more information.

SMC Setup

The following directory is recommended as the destination for the certificate generated on the Ionix ControlCenter Console host:

C:\Program Files\EMC\SMC\Litewave\webapps\sem\etc


2. Change directory to:C:\Program Files\EMC\SMC\litewave\tomcat\bin\

3. Type:keystore.bat -import -alias <alias> -file <file_path>/filename.cer

Where:alias=the alias for new private/public key pair. Must match the alias used to generate the certificate on the Ionix ControlCenter Console host.file=path and name of generated certificate.

Expected output

One certificate has been added to the trust store.

4. Restart the SMC Server host.

Alternative Certificate Setup for SMC Link and Launch 129

Security


CHAPTER 7Using Fully Automated Storage Tiers

Fully Automated Storage Tiering (FAST) is a policy-based system that automatically moves data across tiers to achieve performance service levels and cost targets.


◆ Overview........................................................................................................ 131◆ Managing Service Levels ................................................................................ 132◆ Working with Service Levels ........................................................................... 133

OverviewIonix ControlCenter introduces tiered storage management to simplify capacity reporting and analysis across FAST and heterogeneous storage environments. Ionix ControlCenter now automates the discovery and classification of storage into tiers.

Ionix ControlCenter reports on the cost of service delivery by storage group to enhance policy analysis and asset management.

FAST analyzes volume activity and optimizes both performance and cost. It moves very busy data onto Enterprise Flash Disks and puts data that is mostly idle onto SATA drives (FAST Tiering 131).

Figure 19 FAST Tiering

Using Fully Automated Storage Tiers 131

Using Fully Automated Storage Tiers

Symmetrix Management Console (SMC) provides the ability to create tiers, policies and storage groups.

Managing Service Levels

Managing service levels with FAST, Symmetrix Performance Analyzer, and Ionix ControlCenter

Consider a scenario where FAST is used to optimize an Oracle database across storage that consists of Enterprise Flash Drives, Fibre Channel, and SATA. Ionix ControlCenter and Symmetrix Performance Analyzer (SPA) provide the tools necessary to manage and monitor this environment effectively. For example:

◆ Oracle Database on FAST Storage Group starts with all data on fibre channel.

◆ Ionix ControlCenter shows allocated and unallocated capacity within each storage type.

◆ Ionix ControlCenter also shows service delivery costs for FAST storage groups.

◆ Oracle application generates high transaction requests on LUNs storing index and log files.

◆ Symmetrix Performance Analyzer (SPA) displays high read response time on backend LUNS.

◆ FAST detects high transaction activity on these LUNS and moves data to EFD storage class.

◆ SPA shows reduced read response times and higher transaction per second indicating storage service levels have improved and are now meeting expectations.

◆ FAST detects low transaction activity on Old Transactions and moves data to SATA storage class.

◆ SPA shows low pending transaction requests indicating service levels are still being be met.

◆ Ionix ControlCenter reports that the cost of service delivery has been reduced while service levels have increased using FAST.



Working with Service LevelsIonix ControlCenter has four pre-defined service levels - Platinum, Gold, Silver, and Bronze. You can use these service levels, edit them, or create your own. Ionix ControlCenter then analyzes each volume and maps it to the appropriate service level.

Note: Service levels created in SMC are visible in the Ionix ControlCenter tree and should not be confused with user-defined service levels in StorageScope. The user-defined service levels created in StorageScope cannot be pushed down to Symmetrix.

Creating a service level in StorageScope

To set up service levels, complete the following procedure:

1. Select Utilities > Settings > Service Levels.

Note: This is only available to users with Administrator level privileges.

The Service Levels page is displayed. Each row contains a service level and the list is ordered by Priority. You can change the priority of a service level manually by selecting it and using the directional arrows at the side.

If a LUN matches criteria from multiple service levels, it will be mapped to the service level with the highest priority.

2. To create a new service level click New.

The Service Level Definition page is displayed.

Table 19 Pre-defined service levels

Service Level Name Description

Platinum Enterprise Flash Drive, any RAID level

Gold Fibre Channel, RAID 1

Silver Fibre Channel, RAID 5

Bronze SATA, any RAID level

Working with Service Levels 133


3. Select and add storage class attributes. Service levels may have single or multiple criteria added to their definition. Specify the following details:

4. Click Add.

This adds the service level criteria to the table containing the criteria definitions for that service level.

5. After defining the criteria for a service level, select OK to save the changes.

6. To setup service level reporting, enable LUN Scanning. By default, this is disabled.

You need to apply the changes made to the service level, refer to “Applying service level definition changes to the LUNs in the StorageScope Repository” on page 135.

Table 20 Service level definition

Field Name Description

Service Level Name

Specify a unique name. It can only contain characters from A-Z, a-z, 0-9, - (hyphen), _ (underscore), . (period) and : (colon).

Array Type Specify the array platform you wish to use for the service level. For example, Symmetrix is Gold and CLARiiON is Silver. The options available for Disk Technology, Disk Size and Protection Level depend on the Array Type.

Disk Technology

Select one of the following. • For CLARiiON: Fibre Channel, ATA, SATA, SATA II, SAS,

Enterprise Flash Drive• For Symmetrix: Fibre Channel (all speeds), FC 15K, FC 10K,

SATA, Enterprise Flash Drive

Disk Size Select one of the following. The values are in GB.• For CLARiiON: 0-200, 200-500, 500+• For Symmetrix: 0-200, 200-500, 500+

Protection Level

Select one of the following.• For CLARiiON: RAID 6, RAID 5, RAID 0, RAID 3, RAID 1, RAID

10• For Symmetrix: RAID 5 3+1, RAID 5 7+1, RAID 1, RAID 5,

RAID 6, RAID 6 6+2, RAID 6 14+2, RAID 10• For ESS: RAID 10, RAID 5• For HDS: RAID 0, RAID 0+1, RAID 10, RAID 5, RAID 6, RAID 1• For HPXP: RAID 0+1, RAID 1, RAID 10, RAID 5, RAID 6, RAID

0• For StorageWorks: RAID 5, RAID 10, RAID 1, RAID 0



Importing a Symmetrix tier

You can import the tier definitions you have already created on your Symmetrix arrays and use them as part of your service level definition.


2. Click New.


3. Click Import Tier.

The Import Tier dialog box is displayed that lists the available Symmetrix tiers.

4. Choose a tier by selecting it through the radio button and click Add Criteria.

This adds the tier to the service level criteria.

5. Click OK to save your changes.

You need to apply the changes made to the service level, refer to “Applying service level definition changes to the LUNs in the StorageScope Repository” on page 135.

Applying service level definition changes to the LUNs in the StorageScope Repository

After making service level definition changes, apply the changes by clicking Apply Changes. An information message is displayed. This message is displayed until the page is refreshed.

If you make changes to the service level definitions and do not run the LUN scan then it will run after the next scheduled ETL run (that is, if LUN scanning is enabled).

The Apply Changes button is grayed out unless there are changes to apply.

Modifying a service level

To modify a service level, complete the following procedure:


The existing service levels are listed.

2. Select the service level you wish to modify and click Modify.


Working with Service Levels 135


3. Make the necessary modifications and click OK.

Deleting a service level

To delete a service level, complete the following procedure:


The existing service levels are listed.

2. Select the service level you wish to delete and click Delete.

Using custom queries

Custom query reports are available to address the FAST functionality. For more information refer to the StorageScope online help.


APPENDIX AMigrating the StorageScope Repository

This appendix provides instructions for migrating the StorageScope Repository from one system to another.

◆ Overview........................................................................................................ 138◆ Export StorageScope Repository..................................................................... 140◆ Uninstall StorageScope .................................................................................. 141◆ Install StorageScope on the new host............................................................. 142◆ Import the StorageScope Repository dump file ............................................... 143

Migrating the StorageScope Repository 137

Migrating the StorageScope Repository

OverviewThis appendix provides instructions for migrating the StorageScope server and Repository from one system to another. It assumes that in the initial setup, all Ionix ControlCenter infrastructure systems reside on one system. In the new setup, post-migration, the StorageScope Server and Repository will reside on their own system, with the other Ionix ControlCenter infrastrutcture components residing on a different system.

Note: This procedure also assumes that you will be using an embedded StorageScope Repository stup, not a stand-alone installation with the StorageScope Repository residing on a pre-existing Oracle installation in your enterprise.

Prerequisites

Before migrating the StorageScope setup, the following prerequisites must be met.

System access

◆ You must have administrator privilieges on all Ionix ControlCenter infrastructure systems.

◆ All procedures must be performed while directly logged into the systems; do not access the Ionix ControlCenter infrastructure systems via Terminal Services or a VNC client.

Verify that StorageScope is running properly

1. Log into StorageScope.

2. On the navigation menu, select Utilities, Event log to open the Event log.

3. Verify that there are no error alerts in the log.

4. On the Utilities menu, select Settings, ETL Scheduler to open the ETL Scheduler page.

5. Click Run Now to run ETL.

6. Wait for ETL to complete before proceeding.



Backup the StorageScope server

1. Log into the StorageScope Server host using an administrator account.

2. Backup the Ionix ControlCenter installation folder.

Note: In the default installation, the installation folder is C:\ECC.

Create a cold backup of the StorageScope Repository

1. Log into the StorageScope Repository host using an administrator account.

2. Open the Command Prompt.

3. Navigate to:

<ECC Install Root>\repository\admin\emcsts_scripts

4. Run emcsts_coldback.bat to generate a cold backup of the Repository. When the utility returns a “Database cold backup is successful” message, the backup has successfully completed.

Refer to the StorageScope API & Repository Reference Guide for more information about using the emcsts_coldback.bat utility.

Overview 139


Export StorageScope RepositoryFollow the steps below to backup the StorageScope Repository and create an export of it to migrate from the old Repository host to the new system.


2. Open the Command Prompt.

3. Navigate to:


4. Run emcsts_export_db.bat to generate an export of the Repository. When the utility returns a “Export terminated successfully without warnings” message, the export has successfully completed.

Note: Refer to the StorageScope API & Repository Reference Guide for more information about using the emcsts_export_db.bat utility.

5. Extract the emcstsdb_exp.dmp from the zip file and save it to another location.

Note: Remember the location and dump file name. You will need this information when importing the StorageScope Repository to the new system.



Uninstall StorageScopeAfter exporting and backing up the StorageScope infrastructure components, perform the following tasks to remove the StorageScope installation from the old host:

1. Uninstall the StorageScope Repository and Server as described in the EMC Ionix ControlCenter Planning & Installation Guide, Vol. I.

2. After the uninstallation is complete, restart the Ionix ControlCenter infrastructure host.

3. Log into the system and verify that the following Ionix ControlCenter and Oracle services are still installed and running:






• EMC Control Center Web Console



4. Make a backup of the ControlCenter installation folder on the infrastructure host.

Uninstall StorageScope 141


Install StorageScope on the new host After uninstalling StorageScope, reinstall it on the second host as follows:

1. Install the StorageScope Server as described in the EMC Ionix ControlCenter Planning & Installation Guide, Vol. I.

You may install StorageScope using all default options except for the following required steps that must be performed in the Ionix ControlCenter installation wizard:

• In the Ionix ControlCenter Repository Options step, select the Specify Existing ControlCenter Repository option and click Next. When prompted, enter the hostname and port number used by the Ionix ControlCenter Repository.

• In the StorageScope Repository step, select Yes to install the StorageScope Repository and click Next. You will be prompted with a warning that EMC recommends against installing multiple Ionix ControlCenter infrastructure components on the same host. Click OK to continue with the StorageScope Repository installation.

• Note the StorageScope username and password that you create in the StorageScope Repository User Creation step; you will need this information for importing the StorageScope Repository export to the new system.

2. After the Ionix ControlCenter installation wizard has completed and the StorageScope Server and Repository have been installed, restart the host.

3. Log into the host using an administrator account and verify that the following Ionix ControlCenter and Oracle services are installed and running on the host:



• EMC ControlCenter StorageScope Server



4. Make a backup of the ControlCenter installation folder on the StorageScope host.



Import the StorageScope Repository dump fileTo import the StorageScope Repository export file to the new host:

1. Log into the StorageScope infrastructure host with an administrator account.

2. Stop all Ionix ControlCenter services on the host.

Do not stop the Oracle services.

3. Repeat the previous steps on the other Ionix ControlCenter infrastructure host(s).

4. Import the StorageScope Repository export created under “Export StorageScope Repository” on page 140.


2. Open the Comand Prompt.

3. Navigate to:


4. Run the Repository import utility by entering the following:

emcsts_import_db.bat <STS user> <dump file>

where:

– <STS User> is the user-defined user account for the StorageScope Repository created under “Install StorageScope on the new host” on page 142 (e.g. sts).

– <dump file> is the path and file name of the export dump file created under “Export StorageScope Repository” on page 140 (e.g. c:\temp\emcstsdb_exp.

Note: The EMC Ionix ControlCenter StorageScope API & Repository Reference Guide provides detailed usage instructions for the emcsts_import_db.bat utility.

5. After the import has completed, review the log file, located at


to verify that the import was successful.

Import the StorageScope Repository dump file 143


5. Stop the Oracle services on the StorageScope infrastructure host.

6. Start all stopped Ionix ControlCenter services on the Ionix ControlCenter infrastructure host.

7. Start all stopped Oracle and Ionix ControlCenter services on the StorageScope infrastructure host.

8. Log into StorageScope and run ETL to verify that StorageScope is working properly.

9. Backup all Ionix ControlCenter and StorageScope infrastructure systems.


APPENDIX BConfiguring Email Notifications for Backup and Export Utilities

This appendix describes the procedure to add email notifications to the Ionix ControlCenter and StorageScope repository backup and export utilities.

This appendix contains the following topics:

◆ Overview........................................................................................................ 146◆ Adding email notifications to the utilities ....................................................... 147◆ Removing the email notifications ................................................................... 148◆ Troubleshooting ............................................................................................. 149

Configuring Email Notifications for Backup and Export Utilities 145

Configuring Email Notifications for Backup and Export Utilities

OverviewYou can add email notification to the Ionix ControlCenter and StorageScope repository backup and export utilities. These emails are sent when the backup and export utilities are completed successfully or have failed. This saves you the trouble of going to the database hosts and checking the log files to find the status.

Note: Email notification is an optional functionality and you need to follow the procedures mentioned in this Appendix only if you wish to use it.

To facilitate email notification, you need Blat, which is an open source software.



Adding email notifications to the utilitiesTo add email notifications to the utilities:

1. Ensure that blat is installed.

Blat installation is located in the %ECC_INSTALL_ROOT%\tools\utils folder.

2. Set the system environmental variables.

To set the system environmental variables, select My Computer > Properties > Advanced > Environmental Variables.

You need to specify values for three system environmental variables:

• SMTPSERVER=<SMTP server name>

• COMPUTERNAME=<Server name (without domain name) where the

ControlCenter repository is installed>

Usually, COMPUTERNAME is already set. Check and ensure that it contains the desired value.

• TOADDRESS=<Recipient email address>

• FROMADDRESS=<Sender email address>

If this variable is not set, %toaddress% is used by default.

For example:

SMTPSERVER=Mailhub.lss.emc.comCOMPUTERNAME=losal163toaddress=somebody@emc.com

[email protected]

Note: When you change the environment variables, you need to delete the following files:ControlCenter: %ramboh%\check_bit.txt StorageScope: %emcstsoh%\check_bit.txt

Adding email notifications to the utilities 147


Removing the email notificationsTo remove email notifications, do one of the following:

◆ Set the system environmental variables to "dummy". For example:

SMTPSERVER=dummyCOMPUTERNAME=dummytoaddress=dummyfromaddress=dummy

◆ Remove the system environmental variables.

Note: If you are using COMPUTERNAME for other purposes, retain the value for this variable.

Note: When you change the environment variables, you need to delete the following files:ControlCenter: %ramboh%\check_bit.txt StorageScope: %emcstsoh%\check_bit.txt



Troubleshooting◆ I do not see any email notifications in my mailbox, why is that?

Check both your Inbox and Junk Email box. Email notification might be treated as spam and sent to the Junk Email box.

◆ I have set the SMTPSERVER and toaddress environment variables, but I still do not receive any emails.

Check and make sure that the spelling and case-sensitivity of the SMTPSERVER is accurate.

◆ I have made changes to the SMTPSERVER, fromaddress, and toaddress environment variables, but these changes are not reflected in the emails.

Blat creates a file when it first runs installation, the file is %ramboh%\check_bit.txt for Ionix ControlCenter repository and %emcstsoh%\check_bit.txt for StorageScope repository.

Delete these files if you have made any change to the environment variables. Blat -install will run again to take the new values of the environment variables.

◆ Why does my antivirus software block the blat email notification?

You may see a message similar to:

Blocked by port blocking rule C:\ECC\tools\utils\blat262\full\blat.exe Anti-virus Standard Protection:Prevent mass mailing worms from sending mail

If you are using McAfee, it means that your McAfee version may be too old. Update McAfee and it should allow the blat email.

Troubleshooting 149



APPENDIX CLaunching Ionix ControlCenter Web Applications with Alternate Entities

This appendix describes the procedure to launch Ionix ControlCenter web applications using FQDN or multiple IPs without getting the secutiry certificate error in the browser.

Note: This feature is available only from Ionix ControlCenter 6.1 UB8 onwards.

This appendix contains the following topics:

◆ Overview........................................................................................................ 152◆ Patching Ionix ControlCenter Web Server Services .......................................... 153◆ Importing Ionix ControlCenter Trust Certificate in browser ............................... 154

Launching Ionix ControlCenter Web Applications with Alternate Entities 151

Launching Ionix ControlCenter Web Applications with Alternate Entities

OverviewIf you tried to launch a Ionix ControlCenter web application, such as the Ionix ControlCenter Web Console or StorageScope Console using the FQDN or multiple IPs in the address, you used to get a security certificate error. You could only use the hostname.

With Ionix ControlCenter 6.1 UB8, in addition to hostname, you can use FQDN or multiple IPs in the address without getting this error. To achieve this, you need to generate the Tomcat lockbox, keystore, and trust store with new certificate extension "Subject Alternative Names".

Note: To use this feature, install Ionix ControlCenter 6.1 UB8.



Patching Ionix ControlCenter Web Server ServicesComplete this procedure on all hosts that have the Ionix ControlCenter Web Server service.

1. Backup and delete the following files from your Tomcat Server host:

• tom.lb from %ECC_INSTALL_ROOT%\lockbox

• keycert.ks from %ECC_INSTALL_ROOT%\Tomcat\conf

• trust.ks from %ECC_INSTALL_ROOT%\Tomcat\conf

2. Edit tomcat_kmsclient.ini located in the %ECC_INSTALL_ROOT%\Tomcat\conf folder.

Add the Multiple DNS property under Global Section. Add FQDN, IPs and domain name as comma separated list to "Multiple DNS" property, for example:

[[Global Section]]server host = INENJAINS15L1CServer Init Port = 30721Server User Port = 30721ecc root = .Component name = ..Component type = TOMMultiple DNS = inenjains15l1c.corp.emc.com, 10.30.71.37, 10.30.26.118, localhost

3. Stop and start the EMC ControlCenter Web Server service to regenerate the files you deleted in the step 1 .

Patching Ionix ControlCenter Web Server Services 153


Importing Ionix ControlCenter Trust Certificate in browser1. Open the browser and point it to a Ionix ControlCenter web applications, such as

StorageScope, Web Console, Web Install, Performance Manager, and Documentation Library.

• https://hostname:30002/srm

• https://hostname:30002/webinstall

• https://hostname:30002/eccweb

• https://hostname:30002/wla/login.do

2. Import the certificates in the browser.

• For Internet Explorer version 6.0:

1. The security warning is displayed as:

"The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority".

Click View Certificate.

2. Select the Certification Path tab.

3. Select ControlCenter - ROOT and click View Certificate.

4. Select the General tab, and click Install Certificate to open the Import Certificate wizard.

5. Click Next on the first screen.

6. Select Place all certificates in the following store and click Browse.

7. Select Trusted Root Certification Authorities.

8. Click Next and Finish.

9. Restart the web browser.

• For Internet Explorer version 7.0 and higher:

1. The security warning is displayed as:

"The security certificate presented by this website was not issued by a trusted certificate authority. The security certificate presented by this website was issued for a different website's address. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server".



Click Continue to this website (not recommended).

2. A red icon that shows Certificate Error is displayed at the top of the page. Click Certificate Error.

3. Click View Certificates.

4. Select the Certification Path tab.

5. Select ControlCenter - ROOT and click View Certificate.

6. Select the General tab, and click Install Certificate to open the Import Certificate wizard.

7. Click Next on the first screen.

8. Select Place all certificates in the following store and click Browse.

9. Select Trusted Root Certification Authorities.

10.Click Next and Finish.

11.Restart the web browser.

Note: Importing Ionix ControlCenter Trust Certificate needs to be performed on all hosts from where Ionix ControlCenter web applications are accessed. In order to access multiple Ionix ControlCenter deployment's web applications from the same browser, the certificate regeneration procedure must be executed for each Ionix ControlCenter web application deployments.

Importing Ionix ControlCenter Trust Certificate in browser 155



INDEX

AAlert Log, scanning 104alerts 69

assigning 77autofixes 86best practices 90creating 78resolution 76send to Email and pager 85severity level 76spikes 84templates 81testing 83troubleshooting 92

Any User rule 36At A Glance view 71authorization rules

Any User rule 36ECCAdministrators rule 35SAN Manager rule 35Symmetrix Configuration Manager rule 36Symmetrix Data Protection Manager rule 36Symmetrix Performance Manager rule 36

autofix 81creating definition 86troubleshooting 92

automated alert responses 81

Bbacking up the Repository 97

CChangeMembership permission 41collection policies

accessing 57managing 57

combination agent data collection policy 61common agent data collection policy 60connectivity agent data collection policy 61ControlCenter Console

logging in 18

Ddata collection

policy templates 55predefined policy 55

data collection policiesaccessing 57combination agent 61common agent 60connectivity agent 61database agent 62host agent 62, 65, 68managing 57physical agent 65storage agent 66

database agent data collection policy 62definitions, creating 81documentation, related 13

Eeccadmin 43ECCAdministrators 33ECCAdministrators rule 35Email, alert notification 81EMC online support website 13

Ffrequency, alert checking 81

Ggroups and inheritance 41

Hhelp 18host agent data collection policy 62, 65, 68


Index

Iinheritance

ChangeMembership 42

Mmanagement

policy 81user access 42

Nnew user, creation 44

Oonline help 18

Ppermissions

assigning 36ChangeMembership 41tasks 37

physical agent data collection policy 65

Rrecompiling invalid objects in Repository 101Repository

analyzing tables 100backing up 97cleaning trace files 104export backup 99monitoring tablespace growth 101overview 97, 131recompiling invalid objects 101scanning alert logs 104shutting down 103starting 103tablespace fragmentation 104

rule, create new 50

SSAN Manager 33SAN Manager rule 35schedules, alert 81starting the Repository 103storage agent data collection policy 66

SymmetrixConfiguration Manager 33Configuration Manager rule 36Data Protection Manager 33Data Protection Manager rule 36Performance Manager 33

Symmetrix Performance Manager rule 36

Ttablespace

fragmentation in Repository 104growth monitoring 101

threshold, alert 80thresholds 69trace files, cleaning 104trigger values, alert 80, 83

Uuser

access management overview 42change ID 46create new 44

user groupsadd user 48create new 48default 33ECCAdministrators 33inheritance

of permissions 41SAN Manager 33Symmetrix Configuration Manager 33Symmetrix Data Protection Manager 33Symmetrix Performance Manager 33

Vviews

At A Glance 71

Wwildcards, using with alerts 79Windows 2000 users 44

Documents

EMC Ionix ControlCenter · Symmetrix VMAX, TimeFinder, UltraFlex, ... Passing alert information to an autofix script ... EMC Ionix ControlCenter 6.1 Administrators Guide 13