ControlCenter Configuration and Control - Manage What You Have 5.2 A05

Copyright © 2003, 2004, 2005 EMC Corporation. All rights reserved.
Printed June 2005
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.
Trademark Information
Part Number 300-000-948

Revision A05
2 ControlCenter Configuration and Control: Manage What You Have

Contents
Introduction ............................................................................................................... 5
Chapter 1 Configuration and Control Challenges ......................................... 7

Scenario................................................................................................................... 8
Objectives of Storage Management......................................................................... 9
ProShop’s Storage Allocation Workflow Challenges.............................................. 10
Challenges of the Current Storage Allocation Process.......................................... 11
Achieving Storage Allocation Management Objectives With ControlCenter.......... 12
Getting Started ....................................................................................................... 13
Chapter 2 Planning the ControlCenter Implementation .............................. 15

ControlCenter Planning Overview ......................................................................... 16
Documenting the Environment .............................................................................. 17
Verifying That Systems Meet All Prerequisites ...................................................... 20
Listing the Required Software................................................................................ 21
Planning for the ControlCenter Infrastructure ........................................................ 23
Gathering ControlCenter Installation Information................................................... 26
Choosing Logical Groups to Support Storage Allocation ....................................... 27
Managing User Accounts....................................................................................... 28
Chapter 3 Installing ControlCenter ............................................................... 29

ControlCenter Installation Overview ...................................................................... 30
Creating a Shared Folder for ControlCenter Installation........................................ 33
Installing ControlCenter Components on a Single Host......................................... 36
Installing and Starting the Master Agents on Hosts ............................................... 43
Installing and Starting the Console ........................................................................ 48
Entering License Keys ........................................................................................... 51
Creating User-Defined Groups .............................................................................. 52
Installing Solutions Enabler and ControlCenter Agents ......................................... 53
Validating Agent Installation and Startup ............................................................... 57
Discovering the Storage Network .......................................................................... 60
Validating All Managed Objects Are Discovered.................................................... 64
Chapter 4 Configuring ControlCenter........................................................... 65

Configuration Overview ......................................................................................... 66
Managing User Access to ControlCenter Features ............................................... 67
Populating the User-Defined Groups ..................................................................... 72
Setting Agent Data Collection Policies and Scheduling Reports ........................... 73
Setting Data Retention Policies ............................................................................. 76
Creating Zoning Policies........................................................................................ 77
Chapter 5 Testing and Validating ControlCenter ......................................... 79

Validating Data Collection Policies......................................................................... 80
Validating the Complete Configuration................................................................... 81
Validating StorageScope Reports .......................................................................... 82
ControlCenter Configuration and Control: Manage What You Have 3

Contents
Chapter 6 Configuration and Control Solutions .......................................... 83

Overview................................................................................................................ 84
Validating and Optimizing a SAN Configuration..................................................... 85
Allocating Storage to a Host from a Symmetrix Array............................................ 96
Allocating CLARiiON Devices (LUNs) to a Host .................................................. 115
Adding Devices to a CLARiiON MetaLUN for a Host........................................... 121
Adding HP XP LUSEs to a Host .......................................................................... 126
Adding Symmetrix Devices to a Host Using Storage Provisioning Services ....... 132
Deallocating Storage from a Host ........................................................................ 138
Allocating Storage Using AutoPath...................................................................... 145
What To Do Next.................................................................................................. 153
Appendix A Installation Notes ........................................................................ 155

Latency ................................................................................................................ 156
ControlCenter Infrastructure Components........................................................... 157
Master Agent ....................................................................................................... 159
Console................................................................................................................ 160
StorageScope ...................................................................................................... 161
Fibre Channel Connectivity Agent ....................................................................... 162
Symmetrix SDM Agent ........................................................................................ 163
Storage Agent for Symmetrix............................................................................... 164
Storage Agent for CLARiiON ............................................................................... 165
Storage Agent for NAS ........................................................................................ 166
Storage Agent for HDS ........................................................................................ 167
Database Agent for Oracle .................................................................................. 168
Common Mapping Agent ..................................................................................... 169

Introduction
The Challenge
Today, many businesses face an ever-increasing challenge of managing their storage
resources. How is storage being utilized? How much free space is available and where is
it? How do you add new servers, applications, and storage to your business
environment? All of these processes, using tools unique to each operating system and
storage array, can be extremely complex and labor-intensive.
The EMC ControlCenter 5.2 family of storage management software provides an
end-to-end solution for multivendor storage reporting, monitoring, configuration, and
control. With ControlCenter, you can see the elements of your IT infrastructure (both
hardware and software), know how your infrastructure is performing, and do what's
necessary to ensure that service levels are met—for better performance, improved
productivity, and reduced costs.
Implementation Case Studies
EMC provides a set of Implementation Case Studies to supplement the user
documentation. Unlike a product guide, which covers the full spectrum of features and
capabilities, each case study focuses on a particular aspect of storage management.
Today, there are three case studies in the set:
◆ Reporting: Know What You Have
◆ Configuration and Control: Manage What You Have
◆ Monitoring: Respond to Issues
The case studies can be used alone or together according to your business needs.
Business Model
Each Implementation Case Study looks at the business and operational needs of a data
storage environment and demonstrates a ControlCenter solution.
Case Study Model
Each Implementation Case Study describes an example customer and their data center
configuration. We then walk through the processes of planning, installing, configuring,
and testing, giving the steps we followed in the data center to implement the
ControlCenter components required for each solution. The data center setup of our
example customer simulates a small-to-medium customer environment, with multiple
arrays, switches, databases, and hosts. However, it has none of the complexity
associated with clustering, multiple networks, or firewalls that you might have
implemented in your data center. Your configuration will be different.
Who Should Use This Case Study?
Before implementing ControlCenter in a production environment, you need to consider
the size and complexity of your configuration/implementation.
If you are installing ControlCenter in a small environment similar to our example
customer, use the procedures in this Implementation Case Study in conjunction with the
ControlCenter user documentation—starting with the EMC ControlCenter Planning and
Installation Guide, Volume 1 — to plan, install, and configure your environment.
If you have a medium to large environment, this case study serves as a model for using
ControlCenter to improve your business and operational processes, and provides a
sense of the ControlCenter planning, installation, and configuration process. EMC
recommends that you contact EMC Professional Services for assistance with all your
planning, installation, and implementation needs.
Introduction 5
Introduction

1
Configuration
and Control
Challenges
This chapter describes the business scenario that provides the context for this case
study. Using the scenario, this case study identifies the key challenges businesses face in
allocating and managing their storage resources.
The rest of this case study provides detailed procedures for installing, configuring, and
using ControlCenter 5.2 to meet the configuration and control challenges outlined in
this chapter.
This chapter contains the following sections:
◆ Scenario ............................................................................................................................... 8
◆ Objectives of Storage Management................................................................................. 9
◆ ProShop’s Storage Allocation Workflow Challenges ................................................. 10
◆ Challenges of the Current Storage Allocation Process................................................11
◆ Achieving Storage Allocation Management Objectives With ControlCenter......... 12
◆ Getting Started ................................................................................................................. 13
Configuration and Control Challenges 7

Chapter 1, Configuration and Control Challenges
Scenario
This case study uses the story of ProShop, a company that manufactures and sells golf
equipment, to examine a key challenge facing small to medium-size companies:
allocating and managing storage resources.
ProShop is expanding into Internet sales to reach a broader market and has purchased
an e-commerce application. The e-commerce site needs to be operational by the
beginning of the next business quarter in order to meet sales goals.
ProShop Profile Here is some background information on ProShop’s goals, challenges, and IT structure.
Revenue goal:
◆ Increase from $100M to $200M in two years.
Business initiatives to meet revenue goal:

◆ Acquire a golf club manufacturer to begin selling its own equipment. (ProShop
previously was only a reseller.)
◆ Develop an Internet store to reach a broader market.
IT challenges:
◆ With the acquisition of the club manufacturer, ProShop now has two data centers
resulting in an increased amount and variety of equipment to manage, such as
Windows, Solaris, AIX, and HP-UX servers, several fabrics, a Celerra® Network
Server, and Symmetrix®, CLARiiON®, and HP XP arrays.
◆ To control staffing costs, the company merged the IT staffs from the two data
centers. Each individual brought different specialized skills to the merger.
◆ ProShop needs to increase its IT assets to support growing applications without
adding “head count” to the IT staff.
◆ The growth of the business will significantly increase the number of storage
allocations.
◆ ProShop has an existing workflow process for allocating storage and an increased
need to make the process highly available to support their changing business/IT
environment. ProShop will be unable to meet its business objectives with the current
tools and staff.
◆ Although each data center implemented storage area networks (SANs), ProShop has
not capitalized on the benefits of efficiently allocating their storage resources.
IT staff:
◆ Chief Technology Officer (CTO)
◆ Operations manager
◆ Two UNIX system administrators (one acting as an Oracle DBA and one specializing
in storage and networking)
◆ Two Windows system administrators (one specializes in Microsoft SQL Server and
one specializing in storage and networking)
◆ Database administrator (specializing in Oracle and Microsoft SQL Server)

Objectives of Storage Management

ProShop needs to have the new e-commerce application up and running by the
beginning of the next business quarter.
ProShop’s storage management needs are categorized under the following primary
objectives:
◆ Meet business needs for storage allocations and leverage existing staff by
cross-training.
◆ Use resources more efficiently, including staff, hardware (use storage resources more
efficiently), software, and training.
◆ Implement a tool that simplifies and streamlines its storage allocation processes to
decrease time to allocate storage.
◆ Use a highly available process.
◆ Identify and configure storage for new applications.
◆ Eliminate the use of multiple vendor-specific management tools and instead use a
tool that allows management of both data centers from a single location.
Although the case study focuses on ProShop’s case specifically, these objectives apply to
many small, medium, and even large data centers.
Objectives of Storage Management 9

ProShop’s Storage Allocation Workflow Challenges

ProShop has a storage allocation workflow process in place that was implemented in an
effort to streamline storage allocation. The challenges outlined earlier have limited
ProShop’s successful implementation of the workflow process. The company expects
EMC ControlCenter® to provide the integrated tools to simplify and streamline this
process and to improve the efficiency of the IT staff.
The ProShop storage allocation workflow is shown in Figure 1.
Collect storage
Select a storage
requirements for
array
allocation
Required Desired type of Port available

storage available Yes connection Yes that meets
on array?* available? requirements?**
**Fan in, I/O,

*(Configured/
devices/
No Unconfigured)
channel
Select another
No
array
No
Yes
Configured storage Configure Discover devices

Yes Yes
available? connection on host
No
Configure storage
Figure 1 ProShop Storage Allocation Workflow

Challenges of the Current Storage Allocation Process

The current storage allocation process has several challenges associated with it,
including:
◆ ProShop uses numerous tools to achieve storage allocation.
◆ Staff has specialized skills, requiring a large staff to be involved with each allocation.
This leads to increased time for storage allocation and an inefficient use of
personnel.
◆ The current process is error-prone and cannot scale.
In ProShop’s case, the process is further complicated by the merger of two businesses
and the addition of the new e-commerce application with the requirement for additional
storage.
Sun Solaris
Symmetrix
Oracle DMX1000
Database
Brocade
3800
Baker Street Public IP Network
Win2K
Web
Server
Win2K HP UNIX
Web CAD
Server
Celerra SE Main Street Data Center
HP UNIX
CAD
IBM AIX
Database
Win2K
Baker Street
Transaction
Engine
IBM AIX
CLARiiON
CX600
Database
EMC Win2K
DS16B
Transaction
Win2K/ Engine
SQL2K
HP Storage EMC
Works Symmetrix
Transaction DS16B 4.0
Engine
Sun Solaris
Oracle
Win2K/ Database
SQL2K
Figure 2 ProShop’s Method of “Spreadsheet Storage Management”
Challenges of the Current Storage Allocation Process 11

Achieving Storage Allocation Management Objectives With ControlCenter

Using EMC® ControlCenter’s configuration and control features, ProShop can better
achieve its storage allocation objectives.
The IT staff can efficiently find and allocate storage resources from a single interface as
shown in Figure 3.
Figure 3 ControlCenter Configuration and Control Solutions
The benefits of a single interface result in:

◆ Common training and cross-functional staff, which equals efficiency of staff, and
storage allocations, and a highly available process.
◆ One-stop-shopping ability to configure storage, manage fabrics, and allocate
storage.
The benefits of data in one location result in:
◆ Time saved in collection of standardized and accurate data.
◆ A common picture of the environment.
◆ Efficient use of assets.

Getting Started
ControlCenter provides many powerful features for monitoring and reporting on the
storage environment, but this case study focuses on ControlCenter’s configuration and
control capabilities. The case study continues to follow the story of ProShop to
demonstrate the implementation steps in detail.
Chapter 2, Planning the ControlCenter Implementation
Discusses decisions ProShop must make and information it must gather before
installing ControlCenter.
Chapter 3, Installing ControlCenter
Follows the step-by-step procedures ProShop uses to install the ControlCenter
components.
Chapter 4, Configuring ControlCenter
Looks at how ProShop configures ControlCenter to meet its storage allocation
management needs.
Chapter 5, Testing and Validating ControlCenter
Describes how ProShop validates that ControlCenter was installed and configured
properly.
Chapter 6, Configuration and Control Solutions
Shows the steps ProShop uses to find and allocate storage to support business decisions.
Getting Started 13

2
Planning the
ControlCenter
Implementation
Chapter 1, Configuration and Control Challenges, discussed the business challenges facing
ProShop, such as determining how much storage is available in the merged data
centers, allocating new storage, and managing the fabric.
In this chapter, the administrator plans the ControlCenter 5.2 implementation and
collects the information that is needed to install and set up ControlCenter. Proper
planning at this stage is vital to a successful ControlCenter implementation.
◆ ControlCenter Planning Overview ............................................................................... 16
◆ Documenting the Environment ..................................................................................... 17
◆ Verifying That Systems Meet All Prerequisites ........................................................... 20
◆ Listing the Required Software ....................................................................................... 21
◆ Planning for the ControlCenter Infrastructure............................................................ 23
◆ Gathering ControlCenter Installation Information..................................................... 26
◆ Choosing Logical Groups to Support Storage Allocation ......................................... 27
◆ Managing User Accounts ............................................................................................... 28
Planning the ControlCenter Implementation 15

ControlCenter Planning Overview

ProShop’s operations manager assigns the senior UNIX administrator to lead the
planning and installation of ControlCenter. The UNIX administrator calls on the rest of
the IT staff as necessary for assistance.
The administrator does extensive planning to determine how to install and configure
ControlCenter 5.2 for ProShop’s storage environment.
Planning Planning the installation of ControlCenter components includes these steps:

ControlCenter ❑ Documenting the storage network — The administrator documents the storage
Installation environment by collecting detailed information about host operating systems,
HBAs, drivers, switches, storage arrays, and so on. This information is required to
ensure that all components are supported by ControlCenter.
❑ Verifying that all systems meet EMC ControlCenter prerequisites — The
administrator uses the EMC ControlCenter Release Notes, as well as the
interoperability support documents and tools available on the EMC Powerlink™
website (http://powerlink.emc.com under Interoperability Matrices), to ensure
that all hardware and software components are compatible with ControlCenter 5.2:
• EMC ControlCenter Support Matrix — Describes which ControlCenter
components run on which host platforms, what functionality is supported on
each platform, and with which specific managed objects (arrays, hosts, file
systems, volume managers, databases, and so on).
• E-Lab™ Navigator — Searchable, Web-based application that provides access to
EMC interoperability support matrices.
• EMC Support Matrix — Contains the latest information about which open
systems hosts and related operating systems EMC has qualified to attach to
Symmetrix systems.
• EMC ControlCenter Performance and Scalability Guidelines — Provides an
easy-to-reference list of guidelines for implementing ControlCenter for
maximum performance and scalability.
❑ Listing the software to install — The administrator ensures that the required
software is available.
❑ Planning for the ControlCenter Infrastructure — The administrator determines the
requirements for the ControlCenter infrastructure host to support the environment.
❑ Gathering ControlCenter installation information — The administrator creates
installation notes containing the information required for ControlCenter
installation. The completed ProShop installation notes are provided in Appendix A,
Installation Notes.
Planning Planning the configuration of ControlCenter includes the following steps:

ControlCenter ❑ Create logical groups of resources — To help assess the impact of issues on the
Configuration business, the administrator organizes the environment into logical groups based on
applications, departments, and administrator responsibilities.
❑ Determine ControlCenter users and user access — The administrator uses
ControlCenter administrative permissions to control which systems administrators
can manage and allocate storage.

Documenting the Environment

ControlCenter collects information from objects such as hosts, switches, databases, and
storage arrays through agents loaded on designated hosts in the environment. The
environment must be documented during the planning process.
Decisions about which ControlCenter components are required and where to put them
are mainly based on:
◆ Business requirements — The administrator needs to manage and allocate storage
resources throughout the storage network
◆ Size of the environment — Based on number and size of hosts, fabrics, arrays, and
databases
◆ Type and location of equipment — Requires detailed list of assets
The administrator uses a network diagram tool to diagram the storage network. The
ProShop environment is shown in Figure 4.
Mainstreet_3800
"l82ar122"
Windows 2000
Web Server
Brocade Symmetrix
"l82ar123" 3800 DMX1000
Windows 2000 "182ar155"
Web Server Sun Solaris
Oracle
Database
"l82ar134"
Baker Street Data Center
IBM AIX
SPA SPB Financial "pshpcad1"
Applications HP UX
CLARiiON
CX600 CAD
"l82ar136"
IBM AIX
Main Street Data Center

Financial
Applications "pshpcad2" Celerra
HP XP 512 EMC IP
DS16B HP UX
"l82at124"
CAD
Windows 2000
SQL Server
Transaction "pswapp01"
Engine
"csebach" Windows 2000
Windows 2000 "l82at125" Transaction
HP XP Engine
CommandView Windows 2000
Server SQL Server
Transaction "pswapp02"
Engine
Windows 2000
Transaction
Engine
EMC Symmetrix
DS16B 4.0
"psssun01"
Sun Solaris
Oracle
Database
"psssun02"
Legend Sun Solaris
Oracle
Database
Fibre Channel
Production LAN 1 "pswexch01" "cawti"

Windows 2000 Windows 2000
Production LAN 2
Exchange Web Server
Server
Public IP Network
Figure 4 ProShop Network Diagram Showing Equipment Configuration and Types
Documenting the Environment 17

The list of components in the environment includes details such as operating systems
and versions, patch levels, Fibre Channel HBAs, and HBA driver versions. As the
administrator and staff plan the ControlCenter implementation, they use this list to
determine which ControlCenter components are required and whether a particular
host, operating system, HBA, and so on, is supported by this version of ControlCenter.
The administrator uses the EMC ControlCenter Support Matrix as well as the E-Lab
Navigator and the EMC Support Matrix on the EMC Powerlink website to determine
whether a host is compatible with ControlCenter.
Examples of the information collected by the administrator to verify compatibility with
ControlCenter are shown in Tables 1 through 3.
Table 1 ProShop Host Preimplementation Notes
Hostname IP Address Host Purpose Server Make OS and Patch Level Fibre Channel HBA
and Model Version HBA Driver
cawti 168.159.90.60 Web Server Compaq Windows 2000 SP3 ------------------- ---------------
csebacha 172.23.172.121 HP XP Compaq Windows 2000 SP3 ------------------ --------------

CommandView
Server
l82ar122 172.23.172.122 Web Server Compaq Windows 2000 SP3 ------------------ --------------
l82ar123 172.23.172.123 Web Server Compaq Windows 2000 SP3 ------------------ --------------
l82at124b 172.23.174.124 Transaction Compaq Windows 2000 SP3 Emulex LP8000 2.13
Engine
l82at125c 172.23.174.125 Transaction Compaq Windows 2000 SP3 Emulex LP8000 2.13
Engine
l82ar134 172.23.172.134 Financial IBM F80 AIX 4.4.3 10 6227 --------------

Applications
l82ar136 172.23.172.136 Financial IBM 6150-F50 AIX 4.4.3 10 6227 --------------

Applications
l82ar154d 172.23.172.154 Infrastructure Compaq Windows 2000 SP3 Emulex LP8000 2.13
Host
l82ar155 172.23.172.155 Oracle Database Sun 220R Solaris 8 108528-17 Emulex LP8000 5.01b
l82ar156e 172.23.172.156 Oracle Database Sun 220R Solaris 8 108528-17 Emulex LP8000 5.01b
pshpcad1 10.15.64.23 CAD HP HP-UX 11 ------------------- ------------------ --------------
pshpcad2 10.15.64.24 CAD HP HP-UX 11 ------------------- ------------------ --------------
psssun01 10.15.64.21 Oracle Database Sun 220R Solaris 8 108528-08 Emulex LP8000 5.01b
psssun02 10.15.64.22 Oracle Database Sun 220R Solaris 8 108528-08 Emulex LP8000 5.01b
pswapp01 10.15.64.18 Transaction Dell Windows 2000 SP3 Emulex LP8000 2.13
Engine
pswapp02 10.15.64.19 Transaction Dell Windows 2000 SP3 Emulex LP8000 2.13
Engine
pswexch01 10.15.64.20 Exchange Server Dell Windows 2000 SP3 Emulex LP8000 2.13
a. This host also has the HP XP CommandView Server and appropriate HP XP licenses installed.
b. This host also has EMC ControlCenter Navisphere® CLI installed.
c. This host also has the HP XP CommandView CLI installed.
d. The ControlCenter infrastructure host does not yet exist in the ProShop environment. It is included here for planning purposes.
e. l82ar156 will be added to the ProShop environment later in the case study. It is included here for planning purposes.

Table 2 ProShop Switch Preimplementation Notes
Switch Switch Type IP Address Firmware Revision
3800_209 Brocade 3800 172.23.172.209 3.0.2m_rc4
Clubmftg_DS16B EMC DS16B 172.23.174.170 2.6.0d
sb2_16b_2 EMC DS16B 10.15.64.25 2.6.0d
Table 3 ProShop Storage Array Preimplementation Notes
Storage Serial Number Storage Type IP Address Array Management Software
WRE00022201023 CLARiiON CX600 172.23.174.182 Navisphere CLI 6.06

172.23.174.183 MetaLUN support JRE 1.4.2
30471 HP XP 512 None CommandView 1.8
000182504200 Symmetrix 4.0 None Solutions Enabler 5.4
000187400075 Symmetrix DMX1000 None Solutions Enabler 5.4
psnasCS0 Celerra Network Server 10.15.64.27 NAS OS 4.0
Documenting the Environment 19

Verifying That Systems Meet All Prerequisites

The administrator needs to ensure that the systems documented in the previous section
have the correct hardware and software and that the network meets ControlCenter
latency requirements.
Qualifying the Environment

The administrator compiled a qualifier list of hosts with OS versions, patch levels, and
HBA drivers in a previous section (refer to Documenting the Environment on page 17).
The administrator compares this list to the support matrices in the EMC ControlCenter
Support Matrix and to the EMC Support Matrix on the EMC Powerlink website to ensure
that all components and software meet ControlCenter requirements.
As an alternative to using the various support matrices, the administrator uses EMC
ControlCenter SAN Advisor™ to design the Main Street_3800 configuration, which
currently consists of a new Symmetrix DMX™ system connected through a Brocade
switch to a Solaris host. As the new e-commerce application comes online, additional
hosts will periodically be added. An example of ProShop’s use of SAN Advisor is
provided in Chapter 6, Configuration and Control Solutions.
Over time, the administrator will use SAN Advisor to verify proposed configuration
changes throughout the environment, before implementing them in the data center.
SAN Advisor is a stand-alone web-based solution that is provided as part of the
ControlCenter SRM Planning and Provisioning package or purchased separately. The
administrator uses it to design or verify an environment as a part of the
pre-ControlCenter installation process.
Testing for Latency The EMC ControlCenter Planning and Installation Guide, Volume 1, provides guidelines for
the maximum allowable latency between ControlCenter components. The guidelines
for ControlCenter components are:
◆ Agent-to-infrastructure latency of less than 200 ms.
◆ Console-to-infrastructure latency of less than 8 ms.
The administrator uses the PING command to obtain the average latency between
components within each data center and between data centers.
The ProShop latency calculations are shown in Appendix A, Installation Notes. All
timing measurements between agent hosts and the infrastructure host were under
10 ms and easily met the under-200 ms requirement.
The ControlCenter Console will be installed on the same host as the infrastructure so
latency is not an issue; however, if the administrator and staff install Consoles on other
hosts at a later date, they will have to ensure the latency between Console and
infrastructure hosts is less than 8 ms.

Listing the Required Software

The administrator now determines which portions of the ControlCenter family of
products it needs based on the storage management objectives outlined in previous
sections. In general, the administrator and staff expect ControlCenter to allow them to:
◆ Manage the SAN by allowing it to discover, monitor, and manage the various
objects in the environment (such as hosts, switches, arrays, and so on).
◆ Determine the availability of host- and array-based storage.
◆ Allocate storage to hosts.
The administrator works with an EMC sales representative to determine the required
ControlCenter applications. These licensed applications and agents as well as associated
software requirements are listed in the following sections.
Required ControlCenter Licenses

The basic ControlCenter infrastructure (ECC Server, Repository, Store) is provided in a
package called Open Integration Components (OIC) that also contains the user interfaces,
host agents, database agents, and the Common Mapping Agent.
ProShop purchases the following ControlCenter licensed applications to meet their
specific business needs:
Planning and Provisioning
◆ SAN Manager™ — SAN discovery, monitoring, and configuration functions.
◆ SAN Advisor — Design the fabric topology and verify the interoperability of the
components in ProShop’s storage area network.
◆ Automated Resource Manager™ — Storage Provisioning Services (SPS), control,
and in-depth monitoring of host and host storage resources. SPS requires SAN
Manager to function. For SPS, if the customer has a Symmetrix array, Symmetrix
Manager is required; in the case of CLARiiON arrays, the Storage Agent for
CLARiiON is needed.
Monitoring and Reporting

◆ StorageScopeTM — Reports on storage utilization and provides asset management
for multivendor arrays, SAN, and host storage resources. StorageScope is used in
the context of this case study to determine how much storage is available for
configuration.
Storage Device Management

◆ Symmetrix Manager — Symmetrix discovery, monitoring, and array configuration
functions, as well as SRDF® and TimeFinder® monitoring and control functions.
◆ CLARiiON Agent — CLARiiON discovery, monitoring, and array configuration
functions.
◆ Celerra Agent — Celerra discovery and monitoring functions.
ProShop added the Celerra Agent license so they could discover the Celerra array in
their topology. It is not required for this scenario.
Listing the Required Software 21

Required EMC ControlCenter Agents

ControlCenter agents are loaded on hosts based on the type of information that needs to
be collected about the fabric, the host, an application running on the host, or about the
storage array connected to it.
Table 4 lists the agents that the administrator will install.
Table 4 Agents Needed in the ProShop Environment
Agent Purpose ProShop Agent Installation

Locations
Master Agent Manages all the agents on a One on each host where one or
host. more agents are installed.
Host Agents Monitor and collect statistics One on each Windows, Solaris,
about hosts. HP-UX, and AIX host.
Storage Agents Monitor and collect data about One storage agent per
storage arrays. Symmetrix, CLARiiON, NAS
(Celerra), and HP XP array on
designated hosts in the
environment.
Database Agent for Oracle Collects information about and One on each host on which
monitors Oracle instances. Oracle instances reside.
Common Mapping Agent Collects information about One on a selected host in the
databases other than Oracle. environment (in ProShop’s case,
SQL Server).
Fibre Channel Connectivity Agent Collects data about the SAN One on a selected host in the
from switches. environment.
Symmetrix SDM Agent Enables agents to collect LUN One on each host where a
masking information from Storage Agent for Symmetrix is
Volume Configuration Manager installed.
(VCM) database on a Symmetrix
array.
Required Applications
The administrator needs to ensure that the correct version of array management
software is installed for each array by checking the support matrices in the EMC
ControlCenter Support Matrix as well as the EMC Support Matrix available on the EMC
Powerlink website. The administrator ensures that the correct versions of the following
array management software is installed:
◆ HP XP array — HP CommandView CLI installed on the target host (the host with
the Storage Agent for HDS), and able to communicate with the HP CommandView
Server host. The CommandView Server host must have the appropriate HP licenses
installed.
◆ EMC CLARiiON array — EMC ControlCenter Navisphere CLI.
◆ Symmetrix arrays — EMC Solutions Enabler. The latest version is provided with
EMC ControlCenter and can be installed during or after ControlCenter installation.
The administrator installs Solutions Enabler on the following hosts:
• Hosts with the Storage Agents for Symmetrix
• Hosts with file systems or databases (such as SQL Server) that need to be
discovered with the Common Mapping Agent
• Hosts with Symmetrix device groups that need to be discovered

Planning for the ControlCenter Infrastructure

Every ControlCenter installation requires infrastructure components called the ECC
Server, Repository, and Store. The size, complexity, and growth rate of a customer
environment dictate whether the ControlCenter infrastructure can be installed on a
single host or must be distributed across multiple hosts.
Choosing a Host for the ControlCenter Infrastructure Components

ProShop’s goal is to manage both data centers from a single management infrastructure,
as well as to install several ControlCenter agents on the same host. The administrator
must collect the following information to determine if this is possible and, if so, to
determine the requirements of the infrastructure host:
◆ Classify managed objects as small, medium, or large
◆ Count the number of managed objects of each size
◆ Determine the installation size
Classify Managed Objects as Small, Medium, or Large

The administrator determines the size of the managed objects in the environment based
on the following table from the Planning Guidelines for the Infrastructure section of the
EMC ControlCenter Performance and Scalability Guidelines.
Table 5 Managed Object Sizes
Managed Object Resource Small Medium Large
Symmetrix Logical volumes 1-800 801-2000 2001-8192
Front-end mappings Up to 1600 Up to 4000 Up to 16000
CLARiiON Logical devices 1-32 33-256 257-1024
NAS Logical devices 1-150 151-500 501-1200
Data Movers 2 4 10
Switch Ports 1-16 17-64 65-256
Oracle database Sum of data files and tablespaces 1-800 801-1600 1601-2048
SQL Server or Sybase Sum of databases, data files, log 1-100 101-200 201-400
files, file groups
MVS LPAR DASD devices 1-600 601-1500 1501-3000
DB2 Sum of data files and tablespaces 1-800 801-1600 1601-2048
Agent host Host devices 1-16 17-128 129-512
Logical volumes 1-16 17-64 65-128
File systems (NTFS, UFS, VXFX) 1-16 17-64 65-128
Redundant paths 1-2 3-4 5-32
Planning for the ControlCenter Infrastructure 23

Determine the Installation Size

The administrator adds up the number of managed objects of each size in the data
center and determines the installation size based on the infrastructure sizing tables from
the EMC ControlCenter Performance and Scalability Guidelines. The following excerpt
shows the requirements for a small single-host configuration:
Table 6 Infrastructure Sizing: Infrastructure and Agent Configuration
Host Configuration Max. # Supported Medium-Managed Objects
#
Installation Configuration # Min. Min. Disk Software Storage # Oracle Switches
Size Type CPUs Speed Memory Space Components Arrays # Hosts DBs or (Ports)
Configuration #1: 2 GB RAM Host
Small Single-Host 2 1.0 GHz 2 GB 36 GB ECC Server, Store, & 5 30 10 8

(256)
Repository
StorageScope
Small Single-Host 2 2.4 GHz 2 GB 36 GB Master/Host Agents 10 75 20 16
(512)
WLA Archiver
FCC Agent
Small Single-Host 2 3.0 GHz 2 GB 36 GB 12 90 25 24
Common Mapping Agent (512)
ProShop’s environment easily meets the requirements for a single-host infrastructure.

This means that the ControlCenter infrastructure (Repository, ECC Server, and Store)
can all be installed on the same host.
Determine the Infrastructure Host Requirements

ProShop’s minimum requirements for a single-infrastructure host with additional
agents running on the host are:
◆ Dual 1 GHz processors (Pentium III or above)
◆ 2 GB of RAM (if no agents are loaded on the host, this requirement is 1 GB)
◆ Windows 2000 Advanced Server with Service Pack 2 (English version)
Because the administrator plans to install agents on the infrastructure host in addition
to the infrastructure components, the ProShop infrastructure host must have 2 GB of
RAM to accommodate the additional agents (refer to Figure 4 on page 17 for a list of
agents).
In addition, 72 GB (RAID 1) of available hard disk space will be configured as ProShop's
G and H drives (each drive is 36 GB) on this host. The administrator places the
ControlCenter backup directory on a different physical drive to ensure availability in
case of disk failure.
In choosing where to install agents, the administrator considers the size and number of
objects the agents will manage. For example, if ProShop has a storage array with a large
number of logical volumes, as defined in the EMC ControlCenter Support Matrix, then the
administrator must ensure that the agent host for the array meets the requirements for
managing a large storage array.

Deciding Where to Install Consoles

In addition to the infrastructure, the administrator will install the ControlCenter
Console (the user interface for ControlCenter) on one or more systems. The
administrator, in this initial implementation, chose to limit access to ControlCenter to
one location, and is installing a single Console on the infrastructure server. The
administrator can easily install additional Consoles if necessary.
Table 7 lists the minimum hardware requirements for a client host to run a single
instance of the Console, as described in the Console Guidelines section of the EMC
ControlCenter Performance and Scalability Guidelines.
Table 7 Minimum Hardware Requirements for Running the ControlCenter Console
Operating Number of Minimum Minimum Disk Space with

Systema Processors Speed Memory Console Logging
Windows 1 500 MHz 512 MB 550 MB
Solarisb 1 360 MHz 512 MB 550 MB
a. Refer to the EMC ControlCenter Support Matrix for supported operating system versions for
Console installation.
b. Although ProShop is initially installing the Console on a Windows platform, the requirements for a
Solaris platform are also provided.
Planning for the ControlCenter Infrastructure 25

Gathering ControlCenter Installation Information

The administrator created installation notes that contain specific information about each
component to install. The notes allow the administrator and staff to quickly access the
exact information they need when installing and configuring the ControlCenter
infrastructure and agents.
The administrator recorded some of this information when they listed the assets in the
environment (refer to Documenting the Environment on page 17). Additional host, storage
array, database instance, etc., information is also required.
Figure 5 shows the ProShop environment with the locations of the various
ControlCenter components. The completed ProShop installation notes are provided in
Appendix A, Installation Notes.
Infrastructure Host
ControlCenter:
Console
Agents: "l82ar122" ECC Server "182ar155"
Repository Agents:
Master Sun Solaris Master
Host Windows 2000 Store
StorageScope Host
Oracle Oracle
Web Server Solutions Enabler Database
"l82ar154" Brocade Symmetrix
Agents: "l82ar123" 3800 DMX1000
Windows 2000
Master "182ar156"
Host Agents: Agents:
Windows 2000 Sun Solaris Master
Master
Web Server Host Host
Oracle Oracle
FCC Database
Symmetrix
SDM
Agents: "l82ar134"
Baker Street Data Center
Master IBM AIX

SPA SPB Host Financial "pshpcad1" Agents:
Applications HP-UX Master
CLARiiON Host
CX600 CAD
"l82ar136"
Agents:
Master IBM AIX
Main Street Data Center

Host Financial
Applications "pshpcad2" Agents: Celerra
HP XP EMC IP
DS16B HP-UX Master
Agents: "l82at124" Host
Master CAD
Windows 2000
Host SQL Server
CLARiiON
Transaction Agents:
"pswapp01" Master
Solutions Enabler Engine
Windows 2000 Host
Navisphere CLI
Transaction SDM
Engine Symmetrix
"csebach" Agents: "l82at125" Solutions Enabler
Windows 2000 Master Windows 2000
Host SQL Server Agents:
HP XP HDS Transaction "pswapp02" Master
CommandView Mapping Engine Windows 2000 Host
Server NAS
Solutions Enabler Transaction SDM
CommandView CLI Engine Symmetrix
Solutions Enabler EMC Symmetrix
DS16B 4.0
"psssun01"
Sun Solaris Agents:
Master
Oracle Host
Database Oracle
"psssun02"
Legend Agents: Agents:
Sun Solaris
Master Master
Oracle Host Host
Fibre Channel Database Oracle
Production LAN 1 "cawti"

"pswexch01"
Agents: Windows 2000
Production LAN 2 Windows 2000 Master
Exchange Host Web Server
Public IP Network Server
Figure 5 ControlCenter Infrastructure and Agent Locations in the ProShop Environment

Choosing Logical Groups to Support Storage Allocation

Before implementing a ControlCenter solution, a key task is deciding how to group
ProShop’s resources. These logical groups appear in the Console views and can reflect
the business (as well as physical) structure of the environment.
Businesses may create:
◆ Functional groups such as Test and Production
◆ Geographical groups such as New York and New Jersey
◆ Organizational groups such as Finance and Development
The administrator decided to create groups based on three primary objectives: tracking
and managing assets, knowing how storage resources are allocated, and using storage
more efficiently. The following table lists the groups the administrator has chosen and
how the groups support ProShop’s objectives.
Table 8 ProShop’s User-Defined Groups
Groups Subgroups Purpose
Management e-commerce Application Contains the hosts, database, and switch ports that are part of Manufacturing’s
critical e-commerce application, which is also a major storage consumer. The
group allows management to monitor configuration changes.
Manufacturing Contain the assets (hosts, databases, file systems, switch ports, and storage
Sales devices) that belong to these departments.
Allow management to see how much storage is allocated to and used by these
groups.
Allow the CTO to attribute the costs of storage use.
Allow planners to track storage use over time and forecast the needs of these
groups.
UNIX Admin Databases Allow the IT staff to track the systems for which they are responsible.
Windows Admin Hosts Administrators can even include file systems or database instances that reside
DBA File Systems on the same server in different logical groups.
Switch Ports
Storage Devices
Baker Street Datacenter Databases Allow management and the IT staff to track the physical location of IT assets.
Main Street Datacenter Hosts
Fibre Channel Switches
Storage Arrays
Main Street_3800 Databases Identify the new Symmetrix DMX storage array that has just been installed and
Hosts that will be used with the new e-commerce application.
Fibre Channel Switch
Storage Array
Chapter 4, Configuring ControlCenter, shows the detailed steps the administrator uses to
create these groups in ControlCenter. As the business grows and changes, ProShop can
create new groups and modify existing ones as needed.
Choosing Logical Groups to Support Storage Allocation 27

Managing User Accounts

Access to ControlCenter features is provided through a system of rules and
permissions. Users can be placed into groups that limit their access to specific user-
defined groups of objects. ControlCenter creates several user groups by default, but
additional groups can be created based on business and security needs.
The administrator will use the following ControlCenter groups that are created by
default during installation:
◆ ECCAdministrators — The ProShop Operations Manager is placed in a
ControlCenter default user group called ECCAdministrators that provides all
permissions to all objects.
◆ Symmetrix Configuration Manager Group — This is a ControlCenter default group
that gives members permission to carry out Symmetrix configuration. ProShop’s
System Administrators are placed in this group.
◆ SAN Manager Group — This is a ControlCenter default group that gives members
permission to carry out SAN management tasks. ProShop’s System Administrators
are placed in this group.
The administrator creates new groups to manage the HP XP array and to administer
StorageScope reports:
◆ HP XP Group — The rules for this group will allow members to do storage device
masking and LUSE management on the HP XP array. ProShop’s System
Administrators are placed in this group.
◆ StorageScope Administrator Group — The administrator and staff will use
StorageScope reports to determine the availability of configured space on an array.
ProShop places the System Administrators in this group so they have permission to
change the times at which information for the reports is gathered.
Once StorageScope is installed, all users, by default, have access to view
StorageScope reports.
What’s Next After thoroughly planning out the ControlCenter implementation, the administrator is
now ready to perform the ControlCenter installation as outlined in Chapter 3, Installing
ControlCenter.

3
Installing
ControlCenter
In Chapter 2, Planning the ControlCenter Implementation, ProShop planned the

ControlCenter 5.2 implementation and completed the installation notes required for
installation. In this chapter, they install EMC ControlCenter infrastructure and
components.
◆ ControlCenter Installation Overview ........................................................................... 30
◆ Creating a Shared Folder for ControlCenter Installation........................................... 33
◆ Installing ControlCenter Components on a Single Host ........................................... 36
◆ Installing and Starting the Master Agents on Hosts................................................... 43
◆ Installing and Starting the Console............................................................................... 48
◆ Entering License Keys..................................................................................................... 51
◆ Creating User-Defined Groups...................................................................................... 52
◆ Installing Solutions Enabler and ControlCenter Agents ........................................... 53
◆ Validating Agent Installation and Startup ................................................................... 57
◆ Discovering the Storage Network ................................................................................. 60
◆ Validating All Managed Objects Are Discovered ....................................................... 64
Installing ControlCenter 29
ControlCenter Installation Overview

ProShop is installing ControlCenter into an environment that, based on EMC
guidelines, allows them to place all of the ControlCenter infrastructure components
(Repository, ECC Server, and Store) on one Windows host.
More complex, larger data centers might require that the ControlCenter infrastructure
components be distributed across multiple hosts for load balancing and data storage
(storage of data generated by the ControlCenter agents running on various hosts).
Installation Before beginning installation, make sure the following prerequisites are met:
Prerequisites ❑ Completed the applicable installation notes.
❑ Verified that the site’s hardware, network, and operating systems meet the
requirements listed in the EMC ControlCenter Support Matrix.
❑ Used the EMC ControlCenter Performance and Scalability Guidelines to determine the
minimum memory, processing power, and disk space requirements for the
infrastructure host.
❑ Logged in as administrator or as a user with administrative privileges to the
Windows host on which to install the ControlCenter infrastructure.
❑ Checked that antivirus software is not running.
❑ Ensured that hosts do not have network interface cards (NICs) that are configured
for DHCP.
❑ Verified that the Distributed Transaction Coordinator Service is stopped on the
infrastructure host.
❑ Ensured that all of the correct ports are open based on Appendix B in the EMC
ControlCenter Planning and Installation Guide, Volume 1.
❑ Verified that DNS is properly configured and active.
❑ Ensured that Terminal Services is not running.
❑ Ensured that the infrastructure host has active connections to all network resources
that ControlCenter is to monitor.

Installation Checklist Overview

The administrator completed installation notes that detail the current state of the
customer environment in a previous section of this case study. The notes allow the
administrator to tailor the ControlCenter installation. The completed ProShop notes are
provided in Appendix A, Installation Notes.
ProShop focuses on its storage allocation needs and installs a portion of the available
ControlCenter components. As the business grows or as storage management needs
change, the administrator can install additional components.
The administrator completes the following tasks to install ControlCenter:
❑ Creates a shared folder containing the ControlCenter installation CDs and EMC
Solutions Enabler.
❑ Installs ControlCenter components on the infrastructure host:
❑ Creates a new user, eccadmin, on the ECC Server host — this login account is
required to initially access ControlCenter and create new users.
❑ Maps to the shared drive containing the installation CDs.
❑ Transfers the Install Tools and starts the Installation Wizard.
❑ Installs the following components:
– Repository
– ECC Server
– Store
– Master Agent
– StorageScope
❑ Copies Solutions Enabler onto the host to make it available for remote
installation on designated hosts.
❑ Transfers the Installation Tools and installs a Master Agent on each host that will
have ControlCenter agents.
❑ Installs and starts the ControlCenter Console.
❑ Enters the license keys for ControlCenter components.
❑ Creates logical groups of managed objects (user-defined groups).
❑ Installs EMC Solutions Enabler on designated hosts.
❑ Installs the ControlCenter application agents that collect data, monitor, and control
the customer environment.
❑ Validates that the agents are installed and started.
❑ Discovers objects in the storage network.
❑ Validates that all managed objects were discovered.
During planning, the administrator determined where to install application agents
based on the information they need to collect about the various hosts, switches, storage
arrays, and database instances. Table 9 on page 32 shows the agents that will be
installed on each host.
The administrator transfers the Installation Tools and installs a Master Agent on a host
before installing any application agents.
ControlCenter Installation Overview 31

Table 9 ProShop ControlCenter Agent Installation
Hostname IP Address Host OS
Enabler Required?
Database Agent
Mapping Agent
Storage Agent
Master Agent
Host Agent
SDM Agent
FCC Agent
for Oracle
Solutions
Common
cawti 168.159.90.60 Windows 2000 ✔ ✔
csebach 172.23.172.21 Windows 2000 ✔ ✔
l82ar122 172.23.172.122 Windows 2000 ✔ ✔
l82ar123 172.23.172.123 Windows 2000 ✔ ✔
l82at124 172.23.174.124 Windows 2000 ✔ ✔ ✔a ✔
l82at125 172.23.174.125 Windows 2000 ✔ ✔ ✔b ✔ ✔
l82ar134 172.23.172.134 AIX 4.4.3 ✔ ✔
l82ar136 172.23.172.136 AIX 4.4.3 ✔ ✔
l82ar154 172.23.172.154 Windows 2000 ✔ ✔ ✔c ✔ ✔ ✔
l82ar155 172.23.172.155 Solaris 8 ✔ ✔ ✔
pshpcad1 10.15.64.23 HP-UX 11 ✔ ✔
pshpcad2 10.15.64.24 HP-UX 11 ✔ ✔
psssun01 10.15.64.21 Solaris 8 ✔ ✔ ✔
psssun02 10.15.64.22 Solaris 8 ✔ ✔ ✔
pswapp01 10.15.64.18 Windows 2000 ✔ ✔ ✔c ✔ ✔
pswapp02 10.15.64.19 Windows 2000 ✔ ✔ ✔c,d ✔ ✔
pswexch01 10.15.64.20 Windows 2000 ✔ ✔
a. Storage Agent for CLARiiON

b. Storage Agent for HDS to manage HP XP Array
c. Storage Agent for Symmetrix
d. Storage Agent for NAS

Creating a Shared Folder for ControlCenter Installation

ControlCenter components can be installed either locally from the installation CDs or
from a shared drive. ProShop’s standard business practice is to install all applications
from a shared drive. This allows it to install components from the shared folder to a
remote host without having to move the installation CDs manually from host to host.
This is especially helpful when installing a ControlCenter Master Agent on each host.
The drive on which the shared folder resides must have at least 2.4 GB free space
available for the ControlCenter installation CDs and approximately 520 MB available
for the Solutions Enabler 5.4.x CD.
Creating the Shared Folder

The administrator creates the shared folder as follows:
1. Creates a folder called ECC_VirtualCD that will contain the contents of all
ControlCenter installation CDs. In this case, the administrator creates the folder in
the shared_files file system on host csebach.
2. Shares the folder ECC_VirtualCD.
Transferring ControlCenter Installation Tools

The administrator must transfer the ControlCenter Installation Tools from CD #1 to the
host. The Installation Tools contain the copy utility required to upload the installation
CDs onto the shared drive. The administrator transfers the Installation Tools as follows:
1. Logs in to the host as a user that is part of the local administrators group.
2. Stops the Distributed Transaction Coordinator Service through Windows Services.
the administrator can restart the service after installation is complete.
3. Inserts CD #1 in the host’s CD-ROM drive.
• If autorun is enabled, the Installation utility launches automatically.
• If autorun is not enabled, the administrator launches <cd_drive>:\ecc.exe
The installation wizard displays the following options:
• Ensuring Installation Success Tutorial — View a quick tutorial about planning
and installing ControlCenter.
• Begin Installing — Proceed with installation.
• Support Information — View latest EMC contact information.
• Exit — Discontinue the installation.
4. After viewing the Ensuring Installation Success Tutorial, clicks Begin Installing.
The installation prerequisites appear.
5. Verifies that the installation prerequisites are met and clicks Next.
The EMC ControlCenter copyright and terms of use appear.
6. Clicks Accept.
A dialog box appears asking the administrator to ensure that any antivirus software
running on the host is disabled before continuing.
7. Disables the antivirus software through Windows Services and clicks OK. The
service can be restarted after installation is complete.
A message appears indicating that the installation wizard is loading.
Creating a Shared Folder for ControlCenter Installation 33

The installation wizard displays a screen requesting the installation directory. The
installation directory will contain the Installation Tools and any ControlCenter
components loaded on this host. This drive must be sized to support the planned
implementation and allow for additional component installations in the future.
8. Enters the installation directory information and clicks Next.
The installation wizard launches when the tools installation is complete.
The Start ECC Install icon also appears on the desktop.
9. Clicks Exit to stop the installation wizard, and then clicks Yes to confirm the
selection. If the administrator intended to install directly from the CDs onto this
host, they would continue using the installation wizard and followed the procedure
in Installing ControlCenter Components on a Single Host on page 36.
The Installation Tools are installed and the administrator can now copy the
ControlCenter Installation CDs to the shared drive.
Copying the ControlCenter Installation CDs to the Shared Drive

To copy the ControlCenter installation CDs to the shared drive, the administrator uses
the provided CD copy utility as follows:
1. Maps the ECC_VirtualCD shared folder that will contain the ControlCenter
installation CDs to a network drive on the host. The administrator maps to
\\csebach\shared_files\ECC_VirtualCD.
2. Opens the directory where the ControlCenter Installation Tools are installed. The
default directory is C:\ECC.
3. Opens the folders tools, utils, and then double-clicks copy_cds_to_disk.bat to
launch the CD copy utility.
The CD copy utility prompts for the drive letter of the CD-ROM drive.
4. Enters the drive letter of the CD-ROM drive and presses Enter.
The CD copy utility prompts for the destination shared folder.
5. Enters the drive letter of the shared folder (ECC_VirtualCD) mapped in step 1, and
then presses Enter.
The CD copy utility prompts the administrator to insert the first CD.
6. Inserts CD #1 into the CD-ROM drive and presses Enter.
The utility begins copying the first install CD.
If CD #1 is not in the CD-ROM drive, the CD-ROM drive ejects and the CD Copy
Utility screen appears. If autorun is enabled, the ControlCenter Main Menu appears.
Clicking Exit closes the menu.
After a CD has been copied, the script prompts for the next CD and the
administrator enters the next CD to copy.
After all CDs have been copied to the shared folder, the CD copy utility prompts the
administrator to configure the host to point to the shared folder instead of the
CD-ROM drive for any products the administrator wants to install on this host in
the future.
7. Enters Y for yes, and then presses Enter so that the next time a ControlCenter
product needs to be installed on this host, the installation program will look for the
required files in the shared directory (instead of the installation CDs).
The shared folder now contains the ControlCenter installation CDs.

Copying Solutions Enabler to the Shared Drive

The administrator also places EMC Solutions Enabler in the shared folder (refer to
Making Solutions Enabler Available for Remote Installation on page 40). The ControlCenter
CD copy utility (copy_cds_to_disk.bat) cannot copy the Solutions Enabler source
files to the shared location. Instead, the administrator copies the Solutions Enabler CD
to the shared folder as follows:
1. Inserts the Solutions Enabler CD in the CD-ROM drive.
2. Uses Windows Explorer to copy all the files from the root directory on the CD
(include all files in all subdirectories) to the shared folder (ECC_VirtualCD).
The ControlCenter Installation CDs and EMC Solutions Enabler are now available for
installation from a shared folder. The administrator can begin installation of the
ControlCenter infrastructure.
Creating a Shared Folder for ControlCenter Installation 35

Installing ControlCenter Components on a Single Host

ProShop installs the ControlCenter infrastructure (Repository, ECC Server, and Store) as
well as a Master Agent on a single Windows 2000 host (l82ar154). The administrator
completes the following tasks on this host:
◆ Creates the eccadmin account.
◆ Maps to the shared drive containing the ControlCenter installation package.
◆ Transfers ControlCenter Installation Tools.
◆ Installs the ControlCenter infrastructure.
◆ Makes Solutions Enabler available for remote installation.
◆ Installs and starts the Master Agent.
The following sections describe each of these tasks.
Creating the eccadmin Account

A user account named eccadmin must exist on the Windows 2000 infrastructure host in
order to install and start ControlCenter. eccadmin is the default administrative user in
ControlCenter that enables additional users to be created. After installing ControlCenter
and adding ControlCenter users, the administrator can disable eccadmin for security
purposes.
To create the eccadmin user account, the administrator:
2. Clicks the Windows Start button and selects Settings, Control Panel.
The Control Panel window appears.
3. Opens Administrative Tools, and then opens Computer Management.
The Computer Management dialog box appears.
4. In the tree, expands System Tools, and then expands Local Users and Groups.
5. Under Local Users and Groups, selects Users.
6. On the Action menu, selects New User.
The New User dialog box appears.
7. Enters the following information into the New User dialog box:
User name: eccadmin
Full Name: <Administrator name>
Description: <Administrator description>
Password: <password>
Confirm Password: <re-enter password>
8. Clears the User Must Change Password at Next Logon checkbox.
EMC recommends selecting Password Never Expires for the eccadmin account. If
this option is not selected and the password expires, the user will not be able to log
in and will see the error message, User <username> authentication failed,
your password has expired.
9. Clicks Create to create the account, and then clicks Close to close the dialog box.
10. Clicks OK to exit any open dialog boxes.

Mapping to the Shared Drive

The administrator is installing ControlCenter from a shared drive. If they were
installing directly from the ControlCenter CDs, they would simply insert CD #1 to begin
transferring ControlCenter Installation Tools.
To map the shared drive, the administrator:
1. Maps to the ECC_VirtualCD shared folder on host cawti that contains the
ControlCenter installation package. The administrator maps down to the top level
of the shared folder using the IP address or hostname as shown in the following
example:
\\cawti\shared_files\ECC_VirtualCD
This is the first time the administrator has installed ControlCenter. If ControlCenter
was already installed on the host, the administrator would need to run a
ControlCenter utility to ensure that the installation source is the shared drive. (Refer
to Changing the Media Source for the ControlCenter Installation on page 38.)
2. Opens Windows Explorer, and selects the drive letter of the network drive mapped
in the previous step.
The administrator is ready to transfer the ControlCenter Installation Tools to this
host.
Transferring ControlCenter Installation Tools

The administrator must transfer the ControlCenter Installation Tools to a host before
installing ControlCenter components on that host. An installation wizard, that controls
the installation order of ControlCenter components, launches once the tools installation
completes.
The administrator is installing ControlCenter from a shared drive; if they were installing
directly from the ControlCenter CDs, they would simply insert CD #1 at this point.
To transfer the Installation Tools to a host, the administrator:
2. Stops the Distributed Transaction Coordinator Service through Windows Services.
The administrator can restart the service after installation is complete.
3. Double-clicks ECC.exe in the ECC_VirtualCD folder on the mapped drive.
• Ensuring Installation Success Tutorial — View a quick tutorial about planning
and installing ControlCenter.
• Begin Installing — Proceed with installation.
• Support Information — View latest EMC contact information.
• Exit — Discontinue the installation.
4. After viewing the Ensuring Installation Success Tutorial, clicks Begin Installing.
The EMC ControlCenter copyright and terms of use appear.
6. Clicks Accept.
Installing ControlCenter Components on a Single Host 37

A message appears indicating that the installation is loading.
When the loading completes, the installation wizard displays a screen requesting
the installation directory. The installation directory will contain all of the
ControlCenter infrastructure components. This drive must be sufficiently sized to
support ProShop’s planned implementation, as well as allow for additional
component installations in the future.
8. Enters the installation directory information from the infrastructure installation
notes (Table 10) and clicks Next.
The default is C:\ECC but the administrator chose to install the infrastructure on a
drive that meets the planned size requirements.
Table 10 ProShop Infrastructure Installation Notes
Installation Directory (default is C:\ECC) G:\ECC
If not enough disk space is available to install all of the available ControlCenter
components, the program displays a dialog box indicating the amount of disk space
required by each component. The administrator could then click Back to return to
the previous menu or click Continue to change a subset of the available components
if the drive contains enough space.
When the infrastructure installation is complete, directory G:\ECC will contain
ProShop’s ControlCenter infrastructure.
9. Clicks Next.
The installation wizard launches when the tools installation is complete.
The Start ECC Install icon also appears on the desktop.
Changing the Media Source for the ControlCenter Installation

The Installation Tools program on the host does not know the location of the shared
drive. The administrator sets the media source location as follows:
1. Opens the directory where the ControlCenter Installation Tools are installed. The
default directory is C:\ECC. ProShop’s directory is located on G:\ECC.
2. Opens the folders tools, utils, and then double-clicks configure_install_source.bat.
The program displays a command window with a message indicating the current
drive for reading ControlCenter install media and a prompt to change the
installation source.
3. Answers Y to change the installation source. When prompted, enters the letter of the
mapped network drive and presses Enter.
The program changes the source to the newly specified location. The administrator
is now ready to install ControlCenter components and products from the new
location.

Installing the ControlCenter Infrastructure

The administrator now installs the ControlCenter infrastructure components
(Repository, ECC Server, and Store) on the infrastructure host.
Installing the Repository

The Repository uses an Oracle database to hold the data it collects from the various
agents. Only one Repository exists within a ControlCenter implementation.
As the administrator installs the infrastructure components, the installation wizard
provides prompts to enter information necessary to communicate with the Repository.
To install the Repository, the administrator:
1. Removes any previously existing Oracle products from the host.
2. Double-clicks the Start ECC Install desktop icon to start the installation wizard, if
it’s not already displayed, on the infrastructure host.
• Install ECCRepository
• Specify existing ECCRepository
3. Since this is a new installation, selects Install ECCRepository in the wizard to install
the Repository on the host and clicks Next.
The Repository Data Entry screen appears.
4. Enters the backup directory location from the Repository installation notes (Table
11) and clicks Next to begin the installation.
The administrator places the backup directory on a different mounted file system
and physical drive from the Repository. ProShop backs up this drive daily to an
external media (tape) because these files are overwritten every day during
ControlCenter automated scheduled jobs. This ensures protection of the Repository
hot backup and export files in the event that the physical drive or mounted file
system that the Repository is on has a problem.
Table 11 ProShop Repository Installation Notes
Backup Directory H:\eccbackup
Company Name ProShop
Enable ECC Repository Access via a No

Firewall. (Default is No)
SMTP Mail Server Name mail.proshop.com
The installation wizard displays a message indicating that Oracle is installing on the
host.
There can be extended delays while the Repository is installing.
Once the installation completes, the wizard prompts to install more products on the
host.
5. Clicks Yes to continue installing components.

Installing the ECC The administrator now installs the ECC Server. The ECC Server contains a main
Server program and a Media Repository component, which configures the WebApplications,
WebConsole, API Servers, and SupportTools (ELU). It also contains installation media
for ControlCenter agents, the ControlCenter Console, and the Integration Packages
application. Only one ECC Server exists within a ControlCenter implementation.
To install the ECC Server, the administrator:
1. Selects ECCServer in the Available Components list.
2. Clicks Add to add the ECC Server to the Selected Components list, and then clicks
Next to begin the ECC Server Media Repository installation.
3. Enters the information from the ECC Server installation notes (Table 12) and clicks
Next.
During this step, the wizard asks if the administrator wants to enable LDAP for
ControlCenter user authorization. If ProShop was using LDAP, they would select
Yes and answer a series of questions about their LDAP implementation. The
administrator selects No (default).
Table 12 ProShop ECC Server Installation Notes
ECC Server port number 5799 (default)
Enable LDAP User Authorization? No (default)
The ECC Server installation completes and the installation wizard asks if the
administrator wants to make Solutions Enabler available for remote installation.
Making Solutions Enabler Available for Remote Installation

After installing the ECC Server, a message from the installation wizard appears asking if
the user wants to make Solutions Enabler available for remote installation. This allows
the administrator to install Solutions Enabler on remote hosts from the Console instead
of loading it locally on each host.
Later in the installation, the administrator will install Solutions Enabler on:
◆ Hosts that are to run Storage Agent for Symmetrix.
◆ Hosts with databases to be discovered with the Common Mapping Agent.
◆ Hosts with Symmetrix device groups to be discovered.
The Solutions Enabler CD-ROMs are provided with ControlCenter, and in this scenario
are already loaded on the shared drive; otherwise, the administrator would need
Solutions Enabler CD #1 to complete this task.
To make Solutions Enabler available, the administrator:
1. Clicks Yes at the Would you like to make Solutions Enabler available for
remote install? prompt.
A message appears prompting the user to have Solutions Enabler available.

If the administrator chose not to create the Solutions Enabler remote install package
at this time, they can create it any time afterward by clicking the Start ECC Install
desktop icon and selecting Solutions Enabler.
2. Clicks Yes: I have Solutions Enabler.
The system starts copying the source files from the shared directory to the Media
Repository so Solutions Enabler will be available for remote installation through the
ControlCenter Console.

Once the Solutions Enabler remote install package is created, the wizard prompts to
install more products on the host.
The next step in the installation process is to install the Store.
Installing a Store The administrator installs a single Store based on the sizing requirements determined
during planning.
One or more Stores can exist within a ControlCenter implementation. However, only
one Store can exist on a single host.
To install the Store, the administrator:
1. Selects ECCStore in the Available Components list.
2. Clicks Add to add the ECC Store to the Selected Components list, and then clicks
Next to begin the installation.
Once the installation has completed, the wizard prompts to install more products on
the host.
The administrator now installs a Master Agent on this host.
Installing the Master Agent on the Infrastructure Host

The Master Agent controls all of the agents on a host, starts and stops the agents, and
facilitates remote installation and upgrades. Using the same installation wizard they
used for installing the Repository, ECC Server, and Store, the administrator loads a
Master Agent on its infrastructure host because the company will be installing several
agents on this host.
Installing agents on the infrastructure host is not a ControlCenter requirement, but is
recommended for monitoring purposes.
To install the Master Agent, the administrator:
1. Selects MasterAgent in the Available Components list.
2. Clicks Add to add the Master Agent to the Selected Components list, and then
clicks Next.
3. Enters the information from the Master Agent installation notes (Table 13).
Table 13 ProShop Master Agent Installation Notes
Master Agent port number 5798 (default)
4. Clicks Next to begin the installation.

host.
The next step is to install StorageScope.

Installing StorageScope on the Infrastructure Host

StorageScope generates storage resource utilization reports based on the data that the
various ControlCenter agents collect and send to the Repository. The administrator
installs StorageScope on the infrastructure host.
To install StorageScope, the administrator:
1. Under Available Components, selects StorageScope.
2. Clicks Add to add StorageScope to the Selected Components list, and then clicks
Next.
3. Enters the information from the StorageScope installation notes (Table 14).
Table 14 ProShop StorageScope Installation Notes
StorageScope Server Port Number 8080 (Default)
StorageScope Key The StorageScope key provided with ControlCenter.
4. Clicks Next to begin the installation.

host.
5. Clicks No to finish installing components.
6. Clicks Exit to close the wizard.
Rebooting the Host after Installing the Infrastructure

The administrator reboots the host to enable all of the ControlCenter automatic
database jobs.
A reboot at this time is necessary to start the various ControlCenter services on the host.
The services start automatically on reboot.
The administrator now installs and starts Master Agents on hosts.

Installing and Starting the Master Agents on Hosts

The Master Agents control all of the agents on a host, start and stop the agents, and
facilitate remote installation and upgrades. The administrator needs to install and start a
Master Agent on each host that will have an agent running on it (such as a host agent or
storage agent) before installing the agents on the hosts.
The administrator will load Master Agents on the following hosts:
◆ Windows
◆ Solaris
◆ HP-UX
◆ AIX
The administrator uses the following methods to install Master Agents on the various
hosts (based on the host’s operating system):
◆ Remote installation of Master Agent from a shared drive
◆ Local installation on Solaris, HP-UX, and AIX hosts using shell scripts
Installing Master Agents on Windows Hosts Using the Shared Directory

Before installing Master Agents on each Windows host from the ControlCenter shared
folder (ECC_VirtualCD), which contains the ControlCenter installation CDs, the
administrator first maps the hosts to the shared drive, and then runs the Installation
Wizard that installs the Installation Tools component on the host.
Mapping the Shared To map the shared drive and install the ControlCenter Installation Tools on the host, the
Drive administrator:
1. Maps the shared folder ECC_VirtualCD to a network drive on the Windows hosts
on which the administrator intends to install agents.
The administrator maps to the ECC_VirtualCD shared folder on host cawti. The
administrator maps down to the top level of the shared folder using the IP address
or hostname as shown in the following example:
\\cawti\shared_files\ECC_VirtualCD
This is the first time the administrator has installed ControlCenter. If ControlCenter
was already installed on the host, the administrator would need to run a
ControlCenter utility to ensure that the installation source is the shared drive. (Refer
to Changing the Media Source for the ControlCenter Installation on page 38.)
2. Opens Windows Explorer, and selects the drive letter of the network drive mapped
in the previous step.
3. Double-clicks ECC.exe.
The installation wizard main menu appears.
4. Clicks Begin Installing.
6. Clicks Accept to agree to the licensing terms.
Installing and Starting the Master Agents on Hosts 43

A message appears indicating that the installation is loading. When the loading
completes, the installation wizard displays a screen requesting the installation
directory.
8. Selects the directory in which to install the ControlCenter components on this host
and clicks Next. The default directory is C:\ECC.
Once the ControlCenter Install Tools component has installed, the administrator
then installs the Master Agents, either from the shared folder or the CDs.
Installing the Master Agents on Windows Hosts Using the Shared Drive
To install the Master Agent on a Windows host, the administrator:
1. Double-clicks the Start ECC Install desktop icon to start the installation wizard, if
the wizard is not already running.
2. Selects Specify existing ECCRepository.
3. Enters the Repository hostname and port number from the completed Repository
installation notes (Table 15) and clicks Next.
Repository Hostname l82ar154
Repository Port Number 1521
4. Selects MasterAgent from the Available Components list, clicks Add to add the
Master Agent to the Selected Components list, and then clicks Next.
5. Enters the port number from the completed Master Agent installation notes (Table
16), and clicks Next to start the installation.
Master Agent port number 5798 (default)
Once the installation completes, the wizard prompts to install more products.
6. Clicks No to finish installing components, and then clicks Exit.
7. Clicks Yes in the Question dialog box to confirm the selection to exit the wizard.
Starting the Master Agent on Windows Hosts

Even though the Master Agent service is set to Automatic for Startup Type at reboot, the
administrator must manually start this service after the initial install, or reboot the host.
To manually start the Master Agent, the administrator:
2. Opens Administrative Tools, and then opens Services.
The Services window appears.
3. In the right panel, right-clicks the EMC ControlCenter Master Agent service and
selects Start.
The Master Agent is now running on the host.

Ensuring That the Master Agent has the Required Rights

When a Master Agent is installed on a host, the Master Agent service (EMC
ControlCenter Master Agent) inherits the security settings of the account that is used to
start the service. In turn, all ControlCenter agents that run on that host inherit the
security settings from the Master Agent. Some of the functions performed by those
agents require administrative privileges.
The administrator ensures that the Master Agent starts with administrative privileges as
follows:
2. Opens Administrative Tools, and then opens Services.
The Services window appears.
3. Right-clicks the Master Agent service and selects Properties.
The Master Agent Properties window appears.
4. Clicks the Log On tab and selects This Account.
5. Enters the username and password required to grant the Master Agent
administrative privileges.
6. Stops and restarts the Master Agent (and all other agents running on this host if
there are any) to activate the new settings.
7. Opens Administrative Tools, Security Policy Settings and views the Local Security
Settings to ensure that the account has the privileges: Act as part of the operating
system and Back up files and directories.
Installing Master Agents on AIX, HP-UX, and Solaris Hosts

The administrator installs the Master Agents on the AIX, HP-UX, and Solaris hosts
locally using the installation CDs, although they could perform the installation from a
shared folder as long as the shared location was an NFS-mountable disk.
This procedure uses installation CD #1.
To install and start the Master Agent on AIX, HP-UX, or Solaris hosts, the administrator
does the following based on the operating system:
Invoking the (The procedures are organized by operating system.)

Installation
To invoke the installation on each platform, the administrator:
AIX
1. Creates the mount point:
mkdir /cdrom
2. Inserts CD #1 into the CD-ROM drive.

3. Mounts the CD-ROM using the following command:
mount -v cdrfs -p -r <device_name> <mount_point>
For example: mount -v cdrfs -p -r /dev/cd0 /cdrom

4. Proceeds to Invoking the Installation Script on page 46.

HP-UX
The RockRidge format is not supported by the standard mount and unmount on
HP-UX. The administrator uses the portable file system (PFS) to create the mount point.
To read the CD-ROM in the correct format under HP-UX, the administrator uses the
Portable File System (PFS) as follows:
1. Creates the following file:
/etc/pfs_fstab
2. Enters the following line in the pfs_fstab file and replaces the X, Y, and Z with the
controller, target, and LUN of the CD-ROM device:
/dev/dsk/cXtYdZ /cdrom pfs-rrip xlat=unix,soft 0 0
3. Starts the following daemons:

pfs_mountd &
pfsd &
If not in a path, the administrator can look in /usr/sbin.
4. Creates the mount point:
mkdir /cdrom
5. Inserts CD #1 into the CD_ROM drive.

6. Mounts the CD-ROM:
pfs_mount /cdrom
7. Proceeds to the next section, Invoking the Installation Script.
Solaris
The CD is automounted if the vold daemon is running.
The administrator proceeds to the next section, Invoking the Installation Script.
Invoking the The administrator now invokes the install script on CD #1 to start installing the Master
Installation Script Agent on each host.
As root, the administrator runs the following command:
install_master.sh <mount_point>
For example:
./install_master.sh /dev/cdrom/cdrom0
The EMC ControlCenter Tools installation script starts.
Completing the The administrator now completes the Master Agent installation using the information
Installation from the ProShop Master Agent installation notes (Table 17).
ECC Server Hostname l82ar154
ECC Server IP Address 172.23.172.154
ECC Server Port 5799 (default)
Master Agent’s Listening Port 5798 (default)

To complete the installation, the administrator:

1. Enters the root ControlCenter installation directory when prompted and presses
Enter. This is the directory where the administrator installs all ControlCenter agents.
The default is /usr/ecc.
The program prompts the administrator to create native installable images.
2. Types N to continue the installation without creating the images.
3. Enters the requested system data:
ECC Server's Hostname or IP address[]:
If the administrator enters the ECC Server IP address (not the hostname), the
installation prompts for the ECC Server's hostname.
ECC Server's Hostname[]:
4. Accepts the default values for the following prompts:
ECC Server Port [5799]:
Master Agent's listening port [5798]:
The program displays the following message:
Are these values acceptable [Y|N|Q]:
5. Types Y to accept the values, if they are correct.
The installation extracts files and writes configuration files with the information the
administrator entered.
The installation prompts the administrator to make the Master Agent restart on
reboot (this is not supported on AIX).
Do you want EMC ControlCenter Master Agent to start on reboot [Y|N]:
6. Enters Y.
The installation of the Master Agent is complete and the installation exits.
Starting the Master Agent on AIX, HP-UX, and Solaris

The administrator (logged on to an account with root privileges) starts the Master
Agent from:
<Install_Root>/exec/start_master.csh
and repeats the steps in Completing the Installation on page 46 for each AIX, HP-UX, and
Solaris host that requires a Master Agent.
The next step in the installation process is to install the ControlCenter Console. Each
host with an installed and running Master Agent will now appear in the Console.

Installing and Starting the Console

Installing and starting the Console involves:
◆ Installing the Console application by downloading it from the ECC Server to the
Console host.
◆ Launching the Console on a client.
◆ Logging in to the Console.
Installing the Console Application

The Console is downloaded from the ECC Server. Before installing the Console, the
ControlCenter infrastructure must be installed and running.
To download the Console application, the administrator:
1. Verifies that the WebApplications Server service is running on the infrastructure
host.
2. Opens a Web browser and enters the URL of the ECC Server host using either the IP
address or the hostname in the format
http://<ECCServerHostname-OR-IPAddress>:30000 as follows:
http://l82ar154:30000
The EMC ControlCenter Home Page appears.

3. Clicks Installation, and then clicks Console 5.2.
Since this is the first time the administrator is installing the Console on this client,
the Security Warning dialog box appears.
4. Clicks Yes to continue.
The Console installation application downloads to the host. When the download is
complete, the EMC ControlCenter Console installation wizard appears
automatically.
5. Clicks Next in the wizard.
If the Welcome screen does not open, the administrator can minimize open windows
and wait for the screen to appear.
6. Selects the destination directory to install the Console application, obtained from the
completed Console installation notes (Table 18), and clicks Next to start the
installation.
Table 18 ProShop Console Installation Notes
Console Installation Directory Name C:\Program Files\ecc\console (default)
The Installation Summary message appears indicating the installation was

successful.
7. Clicks Finish to exit the wizard and closes unneeded Web browser windows.
The ControlCenter Console is now installed. The next step in the installation process is
to launch the Console.

Launching the Console

To launch the Console application, the administrator:
1. Clicks the Start ECC Console icon on the desktop.
The EMC ControlCenter Launch Utility appears.
2. Enters the ECC Server hostname (l82ar154) and port number (5799).
3. Selects Enable Console Logging to automatically save extended debugging
information from the Console (used for troubleshooting) to the following location:
%USERPROFILE%\ecc\data\<servername>\console.trc
ProShop’s console.trc for this host is located at:

C:\Documents and Settings\<username>\ecc\data\l82ar154
ControlCenter always saves the standard output from the Console to a file named
consoleLaunch.log (in the same location as console.trc), regardless of whether
the Enable Console Logging checkbox is selected.
For complete information about Console log files, refer to the EMC ControlCenter
Troubleshooting Guidelines.
4. Clicks Submit.
The ControlCenter Console Logon screen appears. The next step in the installation
process is to log on to the Console.
Installing and Starting the Console 49

Logging on to the Console

Since this is the first logon, the administrator must use eccadmin as the username and
password. The administrator continues to use eccadmin until more users are added to
the Console. Chapter 4, Configuring ControlCenter, explains how to how to create and
add users to the Console.
To log on to the ControlCenter Console, the administrator:
1. Enters the username eccadmin.
2. Enters the password.
3. Clicks OK.
The ControlCenter Welcome screen and Console user interface appear as shown in
Figure 6. The hosts with installed and running Master Agents will appear under the
Hosts folder in the tree panel on the left side of the Console.
The Welcome screen provides easy access to valuable information for learning the basics
about the ControlCenter Console. the administrator and staff will use these resources to
become familiar with the Console. This information is always accessible through the
Help button in the Console Menu bar.
Title Bar
Menu Bar
Taskbar
Toolbar
Information
Panel
Tree Panel Welcome Screen Target Panel Displaying At A Glance View
Figure 6 ControlCenter Console
Next, the administrator adds the ControlCenter product license keys.

Entering License Keys

ControlCenter provides license keys for the various ControlCenter products ProShop
purchased to meet their business requirements. In this case, ProShop needs to install the
following license keys:
◆ Automated Resource Manager
◆ CLARiiON Agent
◆ StorageScope
◆ SAN Manager
◆ Symmetrix Manager
Other features are available depending on the products purchased. For example,
ProShop also added the Celerra Agent license so they could discover the Celerra
Network Server in their topology. However, the Celerra Agent license is not required for
the scenarios described in this case study.
To enter the license keys, the administrator:
1. Clicks the blue Administration button on the taskbar. The menu bar changes.
2. Clicks the Install menu and selects Edit Licenses.
The Edit Licenses dialog box appears.
3. Enters the appropriate license keys from the license key card (shipped separately
from the ControlCenter kit) into the text fields and clicks OK.
4. Exits the Console.
5. Restarts the Console to enable the licenses.
This is required from only one Console per ControlCenter infrastructure. The licenses
are already enabled when other hosts (to this infrastructure) launch the Console.
Entering License Keys 51

Creating User-Defined Groups

Containers called user-defined groups are used in ControlCenter to hold objects that need
to be treated as groups rather than individually. For example, the administrator creates
a group containing all UNIX hosts, and another group containing all Windows hosts, so
management access to these objects can be easily controlled.
The administrator will use these groups not just to meet business needs later on, but
also to install ControlCenter agents on the various hosts in a quick, efficient manner.
Planning the Groups Based on initial planning (refer to Choosing Logical Groups to Support Storage Allocation on
page 27), the administrator needs to create the following groups of objects:
Table 19 User-Defined Groups of Objects within ProShop
Group Name Objects in Group
DBA SQL and Oracle database instances and hosts.
Main Street Databases, hosts, storage arrays, and Fibre Channel switches at the Main Street location.
Baker Street Databases, hosts, storage arrays, and Fibre Channel switches at the Baker Street location.
Management Other user groups as well as subgroups containing all database instances, all hosts, all storage, and all Fibre
Channel switches.
Manufacturing Databases, hosts, storage arrays, Fibre Channel switches, and file systems used by the manufacturing division.
Sales Databases, hosts, storage arrays, Fibre Channel switches, and file systems used by the sales division.
Unix Admins UNIX hosts.
Windows Admins Windows hosts.
Main Street_3800 Databases, hosts, arrays, Fibre Channel switches, and file systems used by the new e-commerce application.
Creating a User-Defined Group

The administrator creates user-defined groups as follows:
1. Right-clicks in the white space in the tree panel.
A menu appears.
2. Selects New, Group.
A new item appears on the tree called New Group.
3. Types a name for the new user-defined group.
4. Populates the new group by dragging members (objects) into it.
At this time, the administrator can create groups, but can only populate the groups
with hosts. ControlCenter has not yet discovered the other managed objects in the
environment, such as databases, arrays, switches, and so on. The administrator is
creating the groups at this time to facilitate the installation of ControlCenter agents.
The administrator can create subcategories by right-clicking the top-level group and
selecting New, Group.

Installing Solutions Enabler and ControlCenter Agents

After installing and starting the Master Agents, the administrator loads Solutions
Enabler and the ControlCenter agents on the appropriate hosts.
Installing EMC Solutions Enabler on Hosts

When upgrading from a previous version of Solutions Enabler, all application processes
that use the Solutions Enabler libraries and binaries must be stopped before starting the
install. The EMC Solutions Enabler Release Notes contain important installation
requirements.
The administrator now loads the correct version of Solutions Enabler (version 5.4.0 or
higher) on all hosts where they plan to install the Storage Agents for Symmetrix, hosts
with databases that need to be discovered with the Common Mapping Agent (such as
SQL Server), and hosts with Symmetrix device groups that need to be discovered.
The administrator uploaded the Solutions Enabler package during the ControlCenter
infrastructure installation so it is available for remote installation.
To install Solutions Enabler on a host, the administrator:
1. Right-clicks the Host folder in the Console tree and selects Agents, Install.
The Agent Administration Wizard starts and displays the Platform Types page.
2. Selects the platform type (the administrator needs to install Solutions Enabler on
several Windows hosts) and clicks Next.
The Host Selection page appears.
3. Selects the appropriate hosts based on Table 9 on page 32 and clicks Next.
The Agent Selection page appears.
4. Selects Solutions Enabler 5.4.x and clicks Next.
The Prerequisites Checks page appears. The wizard checks each host to ensure that
Solutions Enabler can be installed successfully.
5. Clicks Next when the preinstallation checking is complete.
The Install Path page appears. The default location is C:\Program Files\EMC.
6. Clicks Next.
The Review Install Agent Task page appears.
7. Clicks Finish to install Solutions Enabler on the selected hosts.
A message appears warning that installing Solutions Enabler can negatively impact
existing SYMCLI-based customized scripts.
8. Clicks Yes to proceed because ProShop does not have any SYMCLI-based scripts.
The Execute Now dialog box appears. This allows a user to create a new task list or
append this task to an existing one. The task list also allows the administrator to
view the progress of the agent installation.
9. Enters a task list name and clicks OK.
The task runs and is updated in the task list viewer displayed on the Console.
After installing Solutions Enabler, the administrator is now ready to install
ControlCenter agents.
Installing Solutions Enabler and ControlCenter Agents 53

Installing ControlCenter Agents

The administrator now installs ControlCenter agents on hosts using the Agent
Administration Wizard. The wizard is accessed by right-clicking on any object in the
tree and selecting Agents, Install.
The administrator will install agents on the following platforms:
◆ Windows 2000
◆ Solaris 8
◆ HP-UX B.11.00
◆ AIX 4.4.3
The wizard gives the administrator the flexibility to install agents on the various hosts
based on platform and agent type. But, the wizard also allows the administrator to
install agents based on the logical groups of hosts that were created in the previous
section.
For example:
◆ The administrator can use a platforms-based approach to load the host agents on all
of the Windows, Solaris, AIX, and HP-UX platforms.
◆ The administrator can also use the logical groups of hosts created in the previous
section to load specific agents on subsets of hosts. For example, the administrator
can select a group containing just hosts collecting information about Oracle
databases or just hosts collecting data about the Symmetrix storage arrays, and load
only those hosts with the required agents.
Installing Host The administrator installs host agents on each host in the environment (refer to Table 9
Agents on page 32).
To install agents on a host, the administrator:
1. Right-clicks the Host folder in the Console tree and selects Agents, Install.
The Agent Administration Wizard starts and displays the Platform Types page.
2. Selects the platform type (the administrator starts with the Windows hosts) and
clicks Next.
The Host Selection page appears, and displays the status, OS version, and level of
the available Windows hosts.
3. Selects the appropriate available hosts based on Table 9 on page 32 and clicks Next.
In this case, the administrator is installing the Host Agent for Windows on all of the
Windows hosts.
If the agent the administrator wants to install does not appear on this list, the agent
may already be installed, or the host may not be compatible with the type of agent
they are installing.
4. Selects Host Agent for Windows and clicks Next.
The Prerequisites Checks page appears. The Agent Application Wizard checks each
host to ensure that the Host Agent for Windows can be installed successfully.
6. Clicks Finish to install the Host Agent for Windows on the selected hosts.

8. Repeats these steps to install host agents on the Solaris, HP-UX, and AIX platforms.
After each host agent is successfully installed, it automatically starts and initiates a
discovery process. The Console tree is updated with the new host data.
Installing Application Agents

In a previous section, the administrator placed managed objects into groups based on
both business needs and the physical structure of the environment.
The administrator uses this logical grouping to install agents on subsets of hosts. For
example, they created a folder called DBA that contains all of the database instances and
hosts. The administrator uses this group to install the Database Agent for Oracle on
each host with an Oracle instance as follows:
1. In the Console tree, right-clicks the ProShop DBA folder.
2. Selects Agents, Install.
The Agent Administration Wizard starts and displays the Platform Types page. This
page lists only those platform types that are in the DBA group.
3. Selects the platform type (the administrator selects the Solaris platform) and clicks
Next.
The Host Selection page appears, and displays the status and OS version and level
of the available Solaris hosts.
4. Selects the appropriate available hosts based on Table 9 on page 32 and clicks Next.
In this case, the administrator is installing the Database Agent for Oracle on all of
the Solaris hosts in the DBA group.
If the agent the administrator wants to install does not appear on this list, the agent
may already be installed, or the host may not be compatible with the type of agent
they are installing.
5. Selects Database Agent for Oracle, and clicks Next.
The Prerequisites Checks page appears. The Agent Application Wizard checks each
host to ensure that the Database Agent for Oracle can be installed successfully.
7. Clicks Finish to install the Database Agent for Oracle on the selected hosts.
Installing Solutions Enabler and ControlCenter Agents 55

The administrator now installs the remaining ControlCenter agents using the
procedures just described (installing the agents based on logical groupings of hosts,
platform type, or specific agent types):
◆ Storage Agent for CLARiiON — on the host gathering CLARiiON array data
◆ Storage Agent for HDS — on the host gathering HP XP array data
◆ Storage Agent for NAS — on the host gathering Celerra data
◆ Storage Agent for Symmetrix — on hosts gathering Symmetrix array data
◆ Common Mapping Agent — on a single host in the environment
◆ Symmetrix SDM Agent — on hosts with a direct connection to the VCM databases
on each Symmetrix array to gather LUN masking data
◆ Fibre Channel Connectivity Agent — one agent per ControlCenter infrastructure

Validating Agent Installation and Startup

The administrator wants to ensure that their agents installed correctly and are running.
They check the installation log to verify that each agent is installed, and then use the
Agents view to check that the agents are running.
Examining the Installation Logs

To check the installation log, the administrator:
1. In the Console tree, right-clicks the Hosts folder (if viewing the install logs for all of
the hosts), or expands the hosts folder and right-clicks a specific host.
2. Selects Agents, View Install Logs.
The Install Logs report appears (Figure 7).
3. Verifies that each agent has a status of Installed.
Figure 7 Install Logs
Using the Agents View

To verify agent status using the Agents view, the administrator:
1. On the task bar, clicks the down arrow next to the blue ECC Administration button
and selects Agents.
The Agents view appears. This view can display in either table or map format
(Figure 8 on page 58).
2. In the Console tree, clicks the checkbox next to a host with an agent running on it to
ensure that the agents on that host are active.
If the agent has not started or has stopped, a warning status icon appears on top of
the agent icon. Figure 8 on page 58 illustrates a warning status for a Storage Agent
for Symmetrix in the Agents view.
Validating Agent Installation and Startup 57

Figure 8 Agents View with Warning on the Symmetrix Agent for pswapp01
Another way the administrator and staff can verify successful agent installation is to
view the list of installed agents. In the tree, they expand Hosts, the host they are
checking, and System Information. Then they right-click ECC Agents and select
Properties. A view appears displaying a list of the installed agents for all of the
hosts and their status.
Starting and Stopping Agents

When the administrator installs an agent, the agent should start automatically.
However, ProShop may have to start or stop agents manually at times, for example, to
perform maintenance on a host or the agent, or to start an agent that was installed
without the prerequisite support software on the host (once the prerequisites are met,
the agent can be started).
Starting Agents To start agent(s) from the Console tree, the administrator:
1. Right-clicks the hosts folder and selects Agents, Start.
The Start Agents dialog box appears with a list of available hosts.
2. Selects the hosts with agents that need to be started and clicks Next.
The Agent selection dialog box appears with a list of inactive and new (never
started) agents.
3. In the Start Agents dialog box, selects the agent(s) to start, and then clicks OK.
The Review Start Agent Task dialog box appears with a list of the inactive and new
agents that will be started.
4. Clicks Finish to accept the review list.
The Execute Now dialog box appears.
The Start Agents task runs and is updated in the task list viewer displayed on the
Console.

Stopping Agents To stop an agent in the Agents view, the administrator:

1. Right-clicks the hosts folder and selects Agents, Stop.
The Stop Agents dialog box appears with a list of available hosts.
2. Selects the hosts with agents that need to be stopped, and clicks Next.
The Agent selection dialog box appears with a list of active agents.
3. In the Stop Agents dialog box, selects the agent(s) to stop, and then clicks Next.
The Shutdown Type Selection Dialog box appears. The administrator must select the
method with which to shut down the agents. A normal shutdown allows an agent to
complete the work in progress before stopping; an immediate shutdown causes an
agent to shut down as soon as possible, which may leave some agent tasks
unfinished.
4. Selects either Normal or Immediate depending on the reasons for stopping the
agent(s).
The Review Start Agent Task dialog box appears with a list of the active agents that
will be stopped and the stop option (Immediate or Normal).
5. Clicks Finish to accept the review list.
The Stop Agents task runs and is updated in the task list viewer displayed on the
Console.
After starting or stopping an agent, the administrator can use the Agents view to verify
that the agent started or stopped. In the Agents view map, the warning icon appears if
the agent is stopped.
In the Agents view table, the status column indicates whether the agent is active or
inactive. To access the table view, the administrator clicks the Table button on the
Agents view title bar.
Validating Agent Installation and Startup 59

Discovering the Storage Network

ControlCenter discovers most objects (such as hosts and Symmetrix arrays) through an
automatic discovery process that is initiated when an agent’s Discovery data collection
policy runs. However, ControlCenter does not automatically discover switches, some
storage arrays, and databases objects.
To completely discover all objects in the storage network, the administrator must
perform the following two procedures:
◆ Assisted Discovery — Discovers the storage arrays, database instances, and the
NAS Server.
◆ User-Initiated Connectivity Discovery — Discovers the three switches in the
environment using their IP addresses.
Using Assisted The administrator uses the assisted discovery method to discover the following:
Discovery ◆ CLARiiON storage array
◆ HP XP array
◆ Celerra Network Server
◆ SQL Server database
◆ Oracle database instances
The administrator uses the Storage Agent for CLARiiON, NAS, and HP XP installation
notes, as well as the Database Agent for Oracle and Common Mapping Agent
installation notes to complete this section. The installation notes are provided in
Appendix A, Installation Notes.
To discover objects using assisted discovery, the administrator:
1. Ensures that all agents to receive a command through assisted discovery are
running. Refer to Installing Solutions Enabler and ControlCenter Agents on page 53.
2. Clicks the blue Monitoring button on the taskbar. The menu bar changes.
3. Clicks the Discover menu and selects Assisted.
The Discover Other Objects dialog box appears.
4. Selects an object type to discover in the Discover Type panel:
• CLARiiON — Discovers CLARiiON storage arrays
• Database — Uses the Common Mapping Agent to discover SQL Server
instances, and the Database Agent for Oracle to discover the Oracle database
instances
• Host — Discovers hosts based on a list of hostnames
• NAS Container — Discovers Celerra Network Servers or NetApp filers
• HDS — Discovers HP XP arrays
The Discovery Settings panel displays the access information fields relevant to the
object type selected.
5. Enters the access information for the objects to discover into the fields in the
Discovery Settings panel. The administrator obtains this information from the
installation notes in Appendix A.
In Figure 9, the administrator has entered the discovery settings for the Celerra
Network Server based on the ProShop installation notes.

Figure 9 Discover Other Objects Dialog Box
6. Selects an agent from the Send To drop-down list, or uses the default setting all
relevant agents, through which to discover the object.
The administrator uses the default settings.
7. Clicks Apply to initiate the discovery.
The Access Info Confirmation window appears.
8. Checks that the confirmation information is correct and clicks OK.
The command is sent to the ECC Server. When an object is discovered, it appears
under the appropriate folder in the Console tree.
9. Repeats these steps for each object the administrator needs to discover.
10. Clicks Cancel to close the Discover Other Objects dialog box once all objects are
discovered.
Discovering the Storage Network 61

User-initiated Connectivity Device Discovery

During the planning phase, the administrator listed all of the IT assets in the storage
network (refer to Documenting the Environment on page 17). The list included three
switches in the network that the administrators need to discover. The administrators
use the IP addresses of the switches to complete this task.
To discover the switches, the administrator:
1. On the taskbar, clicks the blue Monitoring button. The menu bar changes.
2. On the menu bar, clicks the Discover menu and selects Connectivity.
The Search for Connectivity Devices dialog box opens (Figure 10).
Figure 10 Searching for Connectivity Devices through the Console
3. Under Search for IP Address or DNS Name, types the name of one of the switches
and clicks Search Now.
ControlCenter discovers the fabric and topology of the switch. When the discovery
has completed, the switch appears in the Console tree under the Connectivity folder.
4. Repeats this process for each switch until all connectivity devices are discovered and
appear in the Console tree.

Reviewing Discovery Results

After discovering all of the objects in its storage network, the administrator reviews the
results to ensure that all of the objects are correctly identified.
Some objects in ProShop's environment will not be fully discovered until the relevant
agent data collection policies (DCPs) are set. The administrator needs to configure the
Oracle Agent DCP and the Common Mapping Agent SQL Server DCP in order to fully
discover the Oracle and SQL Server databases. Refer to Setting Agent Data Collection
Policies and Scheduling Reports on page 73 for more information.
To review the results of assisted discovery process, the administrator:
1. Clicks the blue Monitoring button on the task bar. The menu bar changes.
2. Clicks the Discover menu and selects Review Progress. The Review Discovery
Results dialog box appears.
3. Selects a command row in the Result Summaries table.
The command details appear under Assistance Result Details.
The administrator cannot delete rows in the Results Summaries tables for
commands sent by the Console. The administrator can delete rows for stored access
data if there are no managed objects associated with that access data (if the Object #
column has a zero).
Figure 11 shows the results table for ProShop’s Celerra Network Server. The Celerra
Network Server did not appear in the Console tree when the administrator attempted to
discover the object.
A review of the Results Summaries table showed that the Celerra agent was not active.
In this instance, the administrator had not installed the agent on the host. Once the
agent was installed and started, the administrator rediscovered the Celerra Network
Server using assisted discovery.
Figure 11 Review Discovery Results for NAS Container
Discovering the Storage Network 63

Validating All Managed Objects Are Discovered

After all the agents have started and all host, arrays, and switches are discovered, the
administrator verifies that all expected managed objects were discovered by examining
the objects in the Console tree. A small diamond on the object indicates that either:
◆ Discovery has not finished
or
◆ The object is not being managed and has been discovered through another managed
object.
Figure 12 illustrates the diamond on a managed object (two Symmetrix systems with
serial numbers ending in 0088 and 0266, respectively). To correct this situation, an agent
needs to be started on a host to manage these objects.
Diamonds Showing
Unmanaged Objects
Figure 12 Unmanaged Symmetrix Systems
What’s Next Now that the ControlCenter agents and infrastructure are installed, and the installation
has been verified as successful, the administrator can begin configuring ControlCenter
as outlined in Chapter 4, Configuring ControlCenter.

4
Configuring
ControlCenter
In Chapter 3, Installing ControlCenter, ProShop installed the ControlCenter infrastructure

and agents in the ProShop environment. This chapter describes how the administrator
configures ControlCenter.
◆ Configuration Overview................................................................................................. 66
◆ Managing User Access to ControlCenter Features ..................................................... 67
◆ Populating the User-Defined Groups ........................................................................... 72
◆ Setting Agent Data Collection Policies and Scheduling Reports.............................. 73
◆ Setting Data Retention Policies...................................................................................... 76
◆ Creating Zoning Policies ................................................................................................ 77
Configuring ControlCenter 65
Configuration Overview
After installing and starting the ControlCenter infrastructure, the administrator needs
to complete the configuration as follows:
❑ Set up user access — Add users to ControlCenter and provide them with varying
degrees of access based on security and business requirements
❑ Configure data collection policies — Set how often they need to collect data about
their databases, hosts, and storage arrays
❑ Populate user-defined groups — Populate the user-defined groups in the Console
tree that the administrator created during installation
❑ Set data retention policies — Set policies that dictate how long historical data is
retained in the ControlCenter Repository
❑ Create zoning policies — Create a default zoning policy to ensure that all new zones
created within a fabric obey the same ProShop standards such as type of zoning,
number of ports allowed in a zone, and zone naming conventions

Managing User Access to ControlCenter Features

The administrator sets up user access to ControlCenter as follows:
◆ Create users on the Windows host (if they do not already exist)
◆ Add the users to ControlCenter
◆ Set up user access to ControlCenter features by placing users into predefined or
newly created user groups
Creating ControlCenter Users

ControlCenter users must exist as Windows users on the ECC Server host or be added
through Windows 2000 Administrative Tools on the host before the administrator can
add them as new ControlCenter users.
The eccadmin user logon and password that the administrator created during
installation should only be used until ProShop creates their own users with
administrator permissions. After the administrator creates these users, they can remove
eccadmin from the Console to prevent unauthorized access to ControlCenter.
Create Users To create users on the ECC Server host, the administrator:
2. Opens Administrative Tools, and then opens Computer Management.
The Computer Management dialog box appears.
3. In the tree, expands System Tools, and then expands Local Users and Groups.
4. Under Local Users and Groups, selects the Users folder.
5. On the Action menu, selects New User.
The New User dialog box appears.
6. Enters the required information in each field of the New User dialog box.
EMC strongly recommends that all user accounts assigned as EMC ControlCenter
users be given unique passwords that cannot be easily guessed.
7. Clears the User Must Change Password at Next Logon checkbox.
8. Clicks Create.
9. Repeats this procedure for each user requiring access to ControlCenter.
Managing User Access to ControlCenter Features 67

Adding a User to ControlCenter

After the administrator has created new users through Windows 2000 Administrative
Tools on the ECC Server host, they can add them to ControlCenter.
To add new users to ControlCenter, the administrator:
1. Expands the Administration, Security Management folder in the Console tree
panel.
2. Right-clicks ECC Users and selects New from the pop-up menu.
The User Definition (New) dialog box appears.
3. In the Login ID field, enters the username for a local user or domain\username for a
domain login ID (the ECC Server must be a part of the domain).
The ControlCenter user ID in the Login ID field is the same name the administrator
entered in the Username field when creating a new user with the Windows 2000
Administrative Tools.
4. Adds a description of the login ID if desired, and clicks OK to add the user.
If the administrator wants to change the ControlCenter login ID for a user, they
must first change the username on the ECC Server host through Windows
Administrative Tools. After the username is changed on the ECC Server host, they
can change the login ID through ControlCenter.
The administrator added users (previously created on the Windows host) to
ControlCenter as shown in Figure 13.
Figure 13 ProShop ControlCenter Users

Creating ControlCenter User Groups

Based on the planning completed in Managing User Accounts on page 28, the
administrator creates two new groups: StorageScope Administrator group and HP XP
Manager group, and then populates the groups with users.
The administrator creates new user groups as follows:
1. Right-clicks ECC User Groups under Administration, Security Management, and
selects New.
The User Group Definition (New) dialog box appears.
2. Types the name of the new group and a description, and clicks OK.
The new group appears under ECC User Groups.
3. Populates the user groups by clicking and dragging users from ECC Users to the
new group.
Figure 14 shows the new StorageScope Administrator and HP XP Manager groups
appearing in the tree with the ControlCenter default user groups.
Figure 14 ProShop’s User Groups
Creating Rules for Users and User Groups

Rules control what a user or user group can do to specified objects. The administrator
needs to create rules for the new groups as follows:
◆ StorageScope Administrator Group — to schedule reports, modify report retention
policies, run real-time reports, and view report history.
◆ HP XP Manager Group — to carry out device masking on the HP XP array.

The administrator creates the rule for the StorageScope Administrator group with the
following steps:
1. In the Console tree, expands the folders Administration, Security, Management,
ECC User Groups.
2. Right-clicks the group and selects Authorization, New Rule. If the user or user
group is already mentioned in a rule, this option does not appear.
The Rule Definition dialog box appears (Figure 15).
3. Enters a name for the rule.
The administrator names the rule StorageScope Admin Rule.
4. Under Choose Objects, selects Types.
The administrator is creating this rule for a type of object (StorageScope Report).
If a group of objects, object instance, or object type is selected, the available
permissions appear under the middle panel (Available actions).
5. Selects StorageScope Admin permission and clicks > to place it in the rule.
The administrator used the EMC ControlCenter Administration/User Guide and the
ControlCenter Console online Help to determine which permissions give them the
required authorization control.
6. Clicks OK to write the new rule to the database.
Figure 15 Creating the StorageScope Admin Rule

The administrator also creates a rule for the HP XP Manager Group that allows
members of the group to carry out device mapping and masking, and LUSE
management on the HP XP array as shown in Figure 16.
Figure 16 Creating the HP XP Manager Rule

Populating the User-Defined Groups

ProShop created several user-defined groups during ControlCenter installation. These
groups were used to facilitate ControlCenter agent installation on the various hosts, but
their larger purpose is to support ProShop’s storage allocation processes.
Now that all of the managed objects such as hosts, storage arrays, switches, databases,
and so on, have been discovered and appear in the Console tree, the administrator can
populate the groups by simply dragging managed objects into the appropriate group.
The administrator populates the groups based on the information in Table 20.
Table 20 User-Defined Groups of Objects Within ProShop
Group Objects
DBA SQL and Oracle database instances and hosts.
Main Street Databases, hosts, storage arrays, and Fibre Channel switches at the Main Street location.
Baker Street Databases, hosts, storage arrays, and Fibre Channel switches at the Baker Street location.
Management Other user groups as well as subgroups containing all database instances, all hosts, all storage, and all Fibre
Channel switches.
Manufacturing Databases, hosts, storage arrays, Fibre Channel switches, and file systems used by the manufacturing division.
Sales Databases, hosts, storage arrays, Fibre Channel switches, and file systems used by the sales division.
Unix Admins UNIX hosts.
Windows Admins Windows hosts.
Main Street_3800 Databases, hosts, arrays, Fibre Channel switches, and file systems used by the new e-commerce application.

Setting Agent Data Collection Policies and Scheduling Reports

ControlCenter application agents have data collection policies (DCPs) that control when
data is collected from the agent. Most DCPs are enabled when an agent is installed and
started. Other DCPs must be defined and scheduled for a specific agent.
Setting Data Collection Policies

The DCPs for ControlCenter are set according to the specifications decided upon during
the planning phase (refer to Listing the Required Software on page 21).
ProShop’s storage allocation and management data collection needs require a level of
data collection that is met by the default ControlCenter DCP schedule settings, (Table
21).
The administrator sets the DCPs as follows:
1. In the Console tree, expands Administration, Data Collection Policies, Policy
Definitions.
A list of agents appears.
2. Expands the agent folder, and then right-clicks the specific policy to manage.
The Policy Definition dialog box appears.
In some cases, the required DCP does not appear in the agent folder. This means
that it was not defined by default for the agent during installation.
If the policy does not appear, the administrator finds the DCP in the Policy
Templates folder; right-clicks it, and selects New. The Policy Definition dialog box
appears; the only additional step the administrator needs to do is to give the policy a
unique descriptor.
3. Sets the Actions (Schedule) and Apply To parameters. The administrator selects
Apply to all applicable objects for all DCPs in this scenario.
The configuration and control solution for ProShop requires configuration of the
following DCPs:
Table 21 ProShop Data Collection Policy Settings
ControlCenter Agent Data Collection Initial Location (Policy DCP Setting Schedule
Policy Definitions/Policy
Templates Folder)*
Common Mapping Agent SQLServer Policy Templates Day_01_0000 (default) Once per day at 12 a.m.
Database Agent for Oracle Oracle Agent Data Policy Templates Hour_01_0600 (default) Once per day at 6 a.m.
Collection
Fibre Channel Connectivity Discovery Scan Policy Templates Minute_30 (default) Every 30 minutes
Agent
Fabric validation Policy Definitions Hour_01 (default) Every hour
Device Validation Policy Definitions Hour_01 (default) Every hour
Host Agent for AIX Discovery Policy Definitions Day_01_0400 (default) Once per day at 4 a.m.
Host Agent for HP-UX Discovery Policy Definitions Day_01_0400 (default) Once per day at 4 a.m.
Host Agent for Solaris Discovery Policy Definitions Day_01_0200 (default) Once per day at 2 a.m.
Host Agent for Windows Discovery Policy Definitions Day_01_0000 (default) Once per day at 12 a.m.
Storage Agent for NAS Discovery Policy Definitions Day_01_0000 (default) Once per day at 12 a.m.
Setting Agent Data Collection Policies and Scheduling Reports 73

Table 21 ProShop Data Collection Policy Settings (continued)
ControlCenter Agent Data Collection Initial Location (Policy DCP Setting Schedule
Policy Definitions/Policy
Templates Folder)*
Storage Agent for CLARiiON Discovery Policy Definitions Day_01_0000 (default) Once per day at 12 a.m.
Storage Agent for HDS Discovery Policy Definitions Day_01_0000 (default) Once per day at 12 a.m.
Storage Agent for Symmetrix Alert Polling Policy Definitions Minute_02 (default) Every 2 minutes
Configuration Policy Definitions Minute_10 (default) Every 10 minutes
Local Discovery Policy Definitions Day_01_0000 (default) Once per day at 12 a.m.
Symmetrix SDM Agent Discovery Policy Definitions Hour_12 (default) Every 12 hours
* Basic DCPs that are turned on by default when the agent is started are found in the Policy Definitions folder. If a DCP is not in the
Policy Definitions folder, it has not yet been defined for this agent and is located in the Policy Templates folder.

Scheduling Reports The administrator needs to schedule the time at which StorageScope captures a
snapshot of the data in the Repository. StorageScope then saves the information into
XML files, which are used when the administrator or staff requests a report.
To set up the schedule for the reports, the administrator (Figure 17):
1. Accesses StorageScope (from the taskbar on the ControlCenter Console, clicks ECC
Administration and selects Reports, Launch StorageScope).
2. Clicks the Administration tab and selects Retention and Scheduling.
3. Selects the time of day for reports to run. The time of day is based on GMT. Local
time is displayed under the time fields. By default, reports run at 4:00 a.m. local
time, but for this scenario, the administrator chooses to run the StorageScope reports
at 5 a.m. to ensure that all other data collection finishes first.
4. Clicks Save before exiting the screen.
StorageScope Report Retention

To set up the retention for the reports, the administrator:
1. Accesses StorageScope (from the taskbar on the ControlCenter Console, clicks ECC
Administration and selects Reports, Launch StorageScope).
2. Clicks the Administration tab and select Retention and Scheduling.
3. Under Retention, selects Keep all reports indefinitely.
4. Clicks Save before exiting the screen.
Figure 17 Scheduling Report Retention
Setting Agent Data Collection Policies and Scheduling Reports 75

Setting Data Retention Policies

Data retention policies define how long and how much historical alert, allocation, log,
and snap data to retain in the Repository. These policies are not enabled by default. If
they are not enabled, the data will be retained indefinitely.
ProShop retains the historical data as follows:
Table 22 Data Retention Policies
Data Retention Description ProShop Retention

Policy Period
Alerts Alerts that have been resolved or cleared from the 1 week
Alert views.
Allocation Information that grows or changes such as file system 90 days

size.
Control Defines how long records of past commands are kept 1 month
in the Command History view.
Log Log files about ControlCenter installation or when the 2 months

Repository was reset.
Snap Containers that hold snapshots of configuration 45 days

information. A new snapshot is created each time the
configuration changes.
The administrator defines a data retention policy as follows:

1. Selects the type of data. From the tree panel, expands Administration, Data
Retention, and then selects the data type.
2. Right-clicks the data type, and then selects Edit Retention.
3. In Retention Period, enters the number of days, weeks, or months worth of
historical data to retain, and then selects Days, Weeks, or Months.
4. In Job Frequency, selects how often the data retention policy will run: Hourly,
Daily, Weekly, or Monthly.
5. In Starting, selects the date and time that ControlCenter should perform the scan
and delete operations. After the starting date, the policy will run according to the
frequency specified and at the time specified.
6. Selects Enabled and clicks OK. The data retention policy will begin to retain the
data from the date entered in the Starting field.
Figure 18 shows the ProShop Alert Data Retention Policy.
Figure 18 Alert Data Retention Policy

Creating Zoning Policies

ProShop creates a default zoning policy to use when creating new zones that specifies
the zoning type, maximum # of host and storage ports, and the zone naming format.
The administrator creates the zoning policy as follows:
1. From the tree panel, expands Storage Administration, right-clicks Zoning Policy,
and selects New, Zoning Policy.
The Zoning Policy Editor - New Policy screen appears (Figure 19).
Figure 19 Create the Zoning Policy
2. Names the new policy Standard ProShop Zoning Policy.

3. Selects the zoning type (WWN Zoning) and Maximum # of Host ports (1).
4. Sets the zone name format using a zone naming convention of <hostname>_<host
port name>_<last three characters of the array name>_<array port name> that uses the
elements %H_%Hp_%Ae3_%Ap.
5. Clicks OK to save the zoning policy.
6. Right-clicks the fabric in the tree and selects Zoning, Set Default Zoning Policy.
The Set Default Zoning Policy for this Fabric dialog box appears (Figure 20).
Figure 20 Set Default Zoning Policy
7. Ensures that the correct zoning policy is selected and clicks OK.
Creating Zoning Policies 77

What’s Next After configuring all of the ControlCenter components, the administrator is now ready
to test the configuration for any problems as outlined in Chapter 5, Testing and Validating
ControlCenter.

5
Testing and
Validating
ControlCenter
This chapter describes how to test and validate the configuration using EMC
ControlCenter to ensure that the data that is being collected is correct.
This chapter includes the following sections:
◆ Validating Data Collection Policies ............................................................................... 80
◆ Validating the Complete Configuration ....................................................................... 81
◆ Validating StorageScope Reports .................................................................................. 82
Testing and Validating ControlCenter 79

Validating Data Collection Policies

The administrator uses the ControlCenter Policies view to ensure that the data
collection policies are running correctly.
To display a Policies view, the administrator:
1. In the Console on the taskbar, clicks the pull-down menu on the blue ECC
Administration button, and selects Policies.
The Policies view appears in the target panel (Figure 21).
2. In the Console tree, selects a managed object.
All started data collection policies appear in the target panel.
Figure 21 illustrates the Policies view for the agents on ProShop’s infrastructure host
(l82ar154). The administrator compares this view to the list of data collection policies
developed in Setting Agent Data Collection Policies and Scheduling Reports on page 73 to
ensure that all data collection policies were set and started correctly.
This view also allows the administrator to make changes to the policies by right-clicking
and choosing a function from the menu.
Figure 21 Policies View

Validating the Complete Configuration

The Topology view allows the administrator to quickly validate that objects were
discovered. The view shows the physical connections between hosts, switches, and
storage arrays. If a known connection does not appear in the view, then the
administrator knows that some aspect of the installation is not configured properly.
To open the Topology view, the administrator:
1. Clicks Topology on the toolbar.
2. In the tree, selects one or more storage arrays, hosts, switches, or user-defined
groups.
Figure 22 shows ProShop’s e-commerce Application group in the Topology view,
including hosts, switch connections, and storage array information.
To diagnose a problem, the administrator can split the Topology view and drag the
problematic objects to other views that were demonstrated in earlier validation
procedures. For example, the administrator can drag a host to the Agents view to see
whether the necessary agents are running, or drag a host into the Policies view to
determine whether the required data collection policies are enabled.
Figure 22 Topology View
Validating the Complete Configuration 81

Validating StorageScope Reports

StorageScope reports are normally run once a day at a set time period. To test and
validate StorageScope, the administrator must run the reports manually.
To run a StorageScope report, the administrator:
1. In the Console on the taskbar, clicks the blue ECC Administration task button.
The menu bar changes.
2. On the menu bar, clicks the Reports menu and selects Launch StorageScope.
The StorageScope Web page appears.
3. Logs in to StorageScope.
4. Clicks the Administration tab, and then clicks the Run reports now button.
After several minutes, StorageScope finishes generating the reports.
5. Clicks the History link and ensures that all reports ran correctly.
6. Clicks the Reports tab, and then, under Combined Reports, selects All.
A combined report of objects in ProShop’s environment appears.
7. Compares the results of the report to what appears in the ControlCenter Console.
Figure 23 shows the host portion of ProShop’s combined report.
Figure 23 ProShop StorageScope Combined Report
What’s Next Now that the administrator has tested the entire ControlCenter implementation to
ensure that everything is working correctly, ProShop is ready to begin storage allocation
as outlined in Chapter 6, Configuration and Control Solutions.

6
Configuration
and Control
Solutions
ProShop has completed installing, configuring, and testing ControlCenter in its data
centers and is now ready to use it to address its storage allocation challenges. This
chapter shows the step-by-step procedures that the staff use to meet the challenges
using ControlCenter’s configuration and control features.
The chapter is divided into the following sections:
◆ Overview........................................................................................................................... 84
◆ Validating and Optimizing a SAN Configuration ...................................................... 85
◆ Allocating Storage to a Host from a Symmetrix Array .............................................. 96
◆ Allocating CLARiiON Devices (LUNs) to a Host......................................................115
◆ Adding Devices to a CLARiiON MetaLUN for a Host............................................ 121
◆ Adding HP XP LUSEs to a Host.................................................................................. 126
◆ Adding Symmetrix Devices to a Host Using Storage Provisioning Services ....... 132
◆ Deallocating Storage from a Host ............................................................................... 138
◆ Allocating Storage Using AutoPath............................................................................ 145
◆ What To Do Next ........................................................................................................... 153
Configuration and Control Solutions 83

Overview
As outlined in Chapter 1, Configuration and Control Challenges, ProShop has the
following issues with their existing storage allocation tools and methods:
◆ ProShop uses numerous tools to achieve storage allocation.
◆ Staff has specialized skills, requiring a large staff for each allocation. This leads to
increased time for storage allocation and an inefficient use of personnel.
◆ The current process is error-prone and cannot scale.
ProShop is implementing ControlCenter to resolve these problems. Using
ControlCenter, they can more efficiently meet objectives.
This chapter covers how ProShop uses ControlCenter to implement their storage
allocation workflow (Figure 24).
Collect storage
Select a storage
requirements for
array
allocation
Required Desired type of Port available

storage available Yes connection Yes that meets
on array?* available? requirements?**
**Fan in, I/O,

*(Configured/
devices/
No Unconfigured)
channel
Select another
No
array
No
Yes
Configured storage Configure Discover devices

Yes Yes
available? connection on host
No
Configure storage
Figure 24 ProShop’s Storage Allocation Workflow

Validating and Optimizing a SAN Configuration

ProShop uses EMC ControlCenter SAN Advisor to model and validate the existing SAN
in the Main Street_3800 environment for interoperability, high availability, configuration
rules, and best practices.
ProShop’s administrator performs the following tasks:
◆ Validates the existing SAN environment
◆ Models proposed SAN changes for interoperability, availability, and performance
◆ Builds an action plan for change implementation
◆ Implements the changes
◆ Verifies correct plan information
This configuration consists of a new Symmetrix DMX 1000 connected through a Brocade
switch to a single Solaris host. As the e-commerce operation comes online and grows,
additional hosts will be added (refer to Allocating Storage to a Host from a Symmetrix
Array on page 96).
After building the existing environment in SAN Advisor, the administrator will add
new hosts to the design to verify the interoperability of new configurations.
Logging in to SAN Advisor

The administrator logs in to SAN Advisor as follows:
1. Accesses SAN Advisor by selecting Start, Programs, EMC, SAN Advisor.
The SAN Advisor login screen appears.
2. Enters the username and password and clicks Login.
The SAN Advisor Home Page appears (Figure 25).
Figure 25 SAN Advisor Home Page
Validating an Existing SAN Environment

SAN Advisor takes snapshots of ControlCenter-managed environments. These
snapshots help accelerate SAN design and change management by allowing you to
model and validate environment changes before implementing them.
Validating and Optimizing a SAN Configuration 85

The administrator takes a snapshot of the existing SAN environment from the
ControlCenter Repository and directly from servers running SNMP as follows. (For
information on supported server and agent details, refer to the SAN Advisor online
Help.)
1. Enters the name of the new snapshot definition and clicks Go.
The ControlCenter Server page appears (Figure 26).
Figure 26 SAN Advisor ControlCenter Server Page
2. Enters the ControlCenter server name or IP address, username, and password. To

use SNMP for server data collection, selects the Use SNMP box, and enters the
SNMP community strings and port number.
When finished, clicks Next.
The Select Members page appears, showing all ControlCenter-managed physical
fabrics and systems (Figure 27).
Figure 27 SAN Advisor Select Members Page

3. Selects the appropriate checkbox to choose the fabrics to include in the snapshot.
Additional devices are accessible by clicking the Individual Systems link.
EMC recommends taking snapshots of either an individual fabric or two fabrics that
mirror each other. Because SAN Advisor uses high-availability rules, it is important
to take snapshots of mirrored fabrics for these rules to execute. If fabrics are not
mirrored, EMC recommends creating a separate definition for each fabric.
When finished, clicks Next.
The Map Systems page appears (Figure 28).
Figure 28 SAN Advisor Map Systems Page
4. Maps any items that are not associated with EMC Support Matrix components.
Mapping associates a collected snapshot value with an EMC Support Matrix
component and allows SAN Advisor to validate components’ interoperability based
on EMC Support Matrix information.
a. Expands the items in the Display Name column to see all system names.
b. Selects the Show “To Do” items only checkbox to display all items that
require mapping.
c. To map an item, the administrator clicks its link in the Mapped To column
and navigates the menus to select the correct description as shown in Figure
29.
Figure 29 Mapping Snapshot Values to EMC Support Matrix Components

d. When finished, clicks Next. The Take Snapshot page appears (Figure 30).
Figure 30 SAN Advisor Take Snapshot Page
5. Clicks Start Snapshot Now to begin the snapshot process. SAN Advisor confirms
when the snapshot is complete.
Note: You can use the Schedule Snapshots page to define how often SAN Advisor takes an
environment snapshot. You can use the Report page to define who receives snapshot
reports. SAN Advisor sends reports via e-mail after a scheduled snapshot is finished.
The completed snapshot appears on the SAN Advisor home page in the Snapshot
Definitions section as shown in Figure 31.
Figure 31 Completed Snapshot Appears on SAN Advisor Home Page
6. Views the snapshot. All error, warning, or informational messages asociated with
the SAN environment are displayed in the Overview report. The Overview report
contains design messages, diagrams, and tables that contain component details.
Clicks the snapshot name, and then clicks the View Report button to view the
Overview report.
7. Edits the snapshot to model changes or resolve problems, if necessary. Clicks the
snapshot name, and then clicks the Make Copy and Edit button. The snapshot is
copied to the My Designs section so that it can be edited.

Modeling Proposed San Changes

The SAN snapshot captured in Validating an Existing SAN Environment on page 85
provides a baseline against which SAN changes can be modeled.
ProShop’s Overview report shows that an availability problem exists on the 182ar122
server. Two connections to the same switch in the fabric are discovered (Figure 32).
Figure 32 ProShop Overview Report: Availability Problem
The administrator performs the following steps to resolve the availability problem:
1. Edits the appropriate snapshot from the SAN Advisor Home Page.
2. Selects Tools, Connections from the top navigation bar. The Connections page
appears showing the two connections to the same switch in the fabric (Figure 33).
Figure 33 Availability Problem: Two Connections to the Same Switch
3. Disconnects one of the Mesh 1 connections and reconnects it to another switch

(Mesh A/BRCD24K_02) (Figure 34).
Figure 34 Correcting the Availability Problem
ProShop’s Overview report also shows that an interoperability problem exists on the
cawti server (Figure 35). Two HBAs from different vendors are present. EMC
recommends that both HBAs be from the same vendor.
Figure 35 ProShop Overview Report: Driver/Firmware Qualification Issues

The administrator performs the following steps to resolve the interoperability problem:
1. Clicks the Server Information tab to view the HBA driver and firmware
combination that is incorrect (Figure 36). SAN Advisor displays an icon to show
components that do not interoperate with each other.
Figure 36 Server Information Page Showing Incompatible Components
2. Clicks the trashcan icon on the right side of the screen to delete the QLogic HBA.
3. Selects the correct firmware for the Emulex HBA from the menu (Figure 37).
Figure 37 Selecting the Correct HBA Firmware
4. Clicks the Add HBA button to replace the deleted QLogic HBA with another
Emulex HBA (Figure 38 on page 91).
This ensures that HBAs are from the same vendor. Now the HBA driver and
firmware for both HBAs are of a qualified combination.

Figure 38 Qualified HBA Combination
By detailing the existing configuration, the administrator can easily add individual or
multiple components and test their interoperability as shown next in Adding Components
to the Existing Configuration.
Adding Components to the Existing Configuration

The ProShop administrator wants to add a new server to the existing configuration.
Using the baseline established in Validating an Existing SAN Environment on page 85, the
administrator can now model the new components.
After the existing configuration has been validated, the administrator adds a new
storage requirement and server as follows:
1. Copies and edits the appropriate snapshot from the SAN Advisor Home Page. The
Server page appears showing the Storage Requirements fields.
2. Selects New, Server or clicks the Add Another Server button and enters the new
storage requirement information, which includes new server name, requirement
name, target platform, protection, and capacity (Figure 39).
Figure 39 Defining a New Storage Requirement
3. When finished, clicks the Server Information tab. The Server Information fields
appear.

4. Enters the new server information, which includes server model, operating system,
and HBAs (Figure 40).
Figure 40 Defining a New Server
For detailed information on the fields in the Server Information page, click the SAN
Advisor online help icon in the top-right corner of the page.
As you add and define components, SAN Advisor continuously checks their
interoperability against the latest EMC Support Matrix data and indicates any
incompatibility issues. If an incompatibility is found, an icon appears to warn of an
invalid configuration.
When finished, clicks Submit. The new server is now added.
5. Selects Tools, Connections. The Connections page appears (Figure 41). A red flag
next to the new server name indicates that the server is not yet connected.
Figure 41 SAN Advisor Connections Page

6. To connect the new server’s HBA ports to the fabric, expands the new server on the
left and expands the switch on the right. Clicks either end to make the connection. A
connection is shown in Figure 42.
Figure 42 Connecting the New Server’s HBA Port
When finished, clicks Submit.

The new server is now connected as shown in Figure 43.
Figure 43 The New Server is Connected
The administrator can now compare the snapshots and verify whether the new
server was added correctly as shown next in Building an Action Plan on page 94.

Building an Action Plan

Building an action plan consists of comparing snapshots and correcting any problems
found. The administrator compares the original snapshot with the new design as
follows:
1. Navigates to the SAN Advisor Home Page.
2. In the Compare column, checks the original design snapshot and the new design
snapshot (Figure 44).
Figure 44 Selecting Snapshots for Comparison
3. Clicks Compare Designs. The newly added server should be the only difference
seen in these designs (Figure 45).
Figure 45 Compare Report Showing Newly Added Server

Implementing Changes
Using SAN Advisor’s Compare Report as a guide to install, connect, and configure the
new server and storage requirement, the administrator should verify that:
◆ The server contains all required software, HBAs, and drivers.
◆ The server can connect to the storage array where its storage requirement resides.
◆ The storage requirement is protected by the appropriate RAID level.
◆ The storage requirement has the required local and remote replicas.
Verifying Correct Plan Information

To verify that the changes are correct, the administrator:
1. Takes a second snapshot of the ControlCenter environment where the server was
added, as described in Validating an Existing SAN Environment on page 85.
2. Checks the appropriate snapshots for comparison, and clicks Compare Designs, as
described in Building an Action Plan on page 94.
3. Compares the snapshot to the design containing the recently modeled changes. If
the new server was implemented correctly, the Compare Report will not contain any
differences (Figure 46).
Figure 46 Comparing Snapshots

Allocating Storage to a Host from a Symmetrix Array

In this scenario, a new Sun Solaris database host (l82ar156) is added to the ProShop
environment. The administrator needs to add additional storage to the database host
based on the storage allocation workflow outlined in previous sections.
Based on growth and performance estimates, the ProShop Oracle DBA requested 40 GB
of RAID 1 storage with local replica for the new host. The system administrators
determine they need to find and allocate a total of 120 GB of space (40 GB for the
standard devices, 40 GB for the mirror devices, and 40 GB for the BCV devices) to meet
ProShop’s RAID protection and local replica business requirements.
The host and the Symmetrix array are physically connected to the same fabric as shown
in Figure 47.
ProShop installed, configured, and tested ControlCenter on this host using the
procedures outlined in previous chapters of this case study.
Figure 47 New Database Host L82AR156 Added to ProShop Environment
Determining if There is Enough Storage on the Symmetrix Array

A total of 120 GB of storage must to be found and allocated for the new database host.
The administrator generates a StorageScope Array Configuration report to determine
Required
the amount of configured, allocated, and unconfigured storage available on this array.
storage available ProShop uses the most up-to-date data for generating the StorageScope reports used in
on array?*
this section. Otherwise, the administrator could be basing device allocation on old data
that is no longer valid for this configuration.
The administrator determines the amount of storage available on the array by accessing
an array configuration report through the Console.
To do this, the administrator:
1. In the Console tree, expands the folders Storage Systems, Symmetrix.
The Symmetrix arrays appear.
2. Right-clicks the array (00187400075) and selects Reports.
The Select Report dialog box appears.
3. Ensures that Array Configuration is highlighted, and then clicks OK.
The Array Configuration report for this array is generated (Figure 48 on page 97).

Figure 48 StorageScope Report Showing Unconfigured Capacity
The report shows that there is 2635.24 GB configured, 2575.61 GB allocated, and 331.64
GB unconfigured storage available. Since ProShop needs 120 GB of storage for the new
host, there is enough additional storage on this array to meet their requirements.
Determining if Type of Connection Is Available

ProShop uses the Topology view in the ControlCenter Console to verify that Fibre
Channel connections to the array exist.
Desired type of To do this, the administrator:

connection
available?
1. Clicks the Topology button on the Console toolbar.
2. In the Console tree, expands the folders Storage Systems, Symmetrix. The
Symmetrix arrays appear.
3. Drags the array (00187400075) into the Topology view (Figure 49).
The administrator turned on Show Links to see the cabling that is in place for this
fabric. ProShop is using WWN zoning and will need to create a zone and add it to
the zone configuration for the Mainstreet_3800 fabric.
Figure 49 Determining if Desired Type of Connection is Available
The Topology view shows that Fibre Channel connectivity to the host exists.
Allocating Storage to a Host from a Symmetrix Array 97

Determining if Ports That Meet Requirements Are Available

The administrator needs to determine if ports are available on the array, and if the
available ports meet requirements such as fan-in ratio, I/O, devices per channel, and so
on. The administrator uses the EMC Support Matrix available on the EMC Powerlink
Port available
that meets website to determine if the current configuration can support the new host.
requirements?**
To complete this task, the administrator:
◆ Verifies port settings.
◆ Verifies fan-in ratio.
◆ Determines devices per channel.
◆ Determines port throughput.
Verifying Port Settings Port flag settings on the Symmetrix array control how the array communicates with
each host type. The administrator needs to select a port based on the port flag settings to
ensure that the port can communicate with the HBA in the new Sun host.
Port available The administrator generates a StorageScope report that shows all of the ports and their
that meets associated port flag settings.
requirements?**
1. On the Console task bar, clicks the blue ECC Administration button.
The menu bar changes.
2. Clicks the Reports menu and selects Launch StorageScope.
The StorageScope home page appears.
3. On the StorageScope home page, clicks All Arrays. The Arrays — Usable Summary
report appears.
4. Selects the appropriate array (000187400075) from the summary table. The Array
Configuration - General - Basic report appears.
5. Clicks the Ports tab.
6. Creates a customized layout by clicking the Layout drop-down menu and selecting
Create New Layout.
The Create Custom Layout wizard starts.
7. Enters the layout name: 0075 Port Settings.
8. Clicks Next.
The Select Columns screen appears (Figure 50 on page 99).

Figure 50 Select Columns Screen
9. Under Columns Available selects FC Flags - Fibre Port and clicks Add > to add a
Port Flags column to the new report.
10. Clicks Next.
The Filter screen appears (Figure 51).
11. In the first Select a Column field, selects Array.
12. Under Operator, selects contains.
13. Under Value, enters the last few characters of the array name: 0075.
14. Clicks Finish.
Figure 51 Set Filter
The report appears, displaying the port flag settings for each device in the array (Figure
52).

Figure 52 StorageScope Report Showing Port Flag Settings for Each Device on the Array
15. Based on the EMC Host Support Matrix, uses the StorageScope report to select a port
that has the correct port flag settings for the new Sun host.
The administrator selects FA-3D Port 0 for further consideration, but many of the
ports have the appropriate port flag settings for this implementation.
The WWN of FA-3D Port 0 (5006048acadfe2d2) is recorded for use later in the
procedure.
Manually Confirming Port Flag Settings

The administrator now manually confirms the port flag settings for FA-3D Port 0
through the ControlCenter Console. The most up-to-date information for port flag
settings can be found in the EMC Support Matrix on the EMC Powerlink website.
Port available
that meets To do this, the administrator:
requirements?**
2. Expands the array (00187400075) and the folder Host Directors.
3. Right-clicks FA-3D and selects Configure, Port Flag Settings.
The Port Flag Default Settings dialog box appears (Figure 53 on page 100).
Figure 53 Port Flag Default Settings Dialog Box
4. Selects Manual Mode and verifies the flag settings for the host operating system
against the EMC Host Support Matrix (Figure 54).

Figure 54 Manual Flag Setting Dialog Box
5. Clicks Help to display the online Help that describes the flag settings.
6. Clicks Cancel to close the dialog box once the port flag settings are confirmed.
The administrator has now verified that FA-3D Port 0 and the new host HBA are
compatible.
Verifying Fan-in Ratio The administrator uses Path Details view to determine the number of HBAs connected
to the selected Symmetrix port to ensure that the fan-in ratio stays within EMC
guidelines based on the EMC Support Matrix on the EMC Powerlink website.
Port available To do this, the administrator:

that meets
requirements?**
1. On the Console toolbar, clicks the pull-down menu of the blue Storage Allocation
button and selects Path Details.
2. In the Console tree, expands the Symmetrix array down to the director (Storage
Systems, Symmetrix Arrays, 000187400075, Host Directors, FA-3D), and then drags
Port 0 into the target panel.
A table showing the path details for this host appears if there are HBAs zoned to this
port, or, if not (as in this case), the target panel displays the message: There are no
paths to display in this view.
Determining Devices Per Channel

The administrator uses Properties view to determine the number of devices on the
selected port to ensure that the configuration stays within EMC guidelines based on the
EMC Support Matrix on the EMC Powerlink website.
Port available
that meets To do this, the administrator:
requirements?**
1. On the Console toolbar, clicks the Properties view button.
2. In the Console tree, expands the Symmetrix array down to the director (Storage
Systems, Symmetrix Arrays, 000187400075, Host Directors, FA-3D), and then drags
Port 0 into the Properties view.
The number of devices connected to the port are displayed in the # Devices column
(Figure 55).
3. Compares the number of devices on the channel to the EMC Support Matrix and
determines that this configuration falls within the guidelines.

Figure 55 Using Properties View to Determine the Number of Devices on FA-3D Port 0
Determining Port Throughput

FA-3D Port 0 is not a member of the active zone set. This means that it is an unused port
on the Symmetrix array and has no throughput.
Port available In situations where throughput might be an issue, the administrator can use EMC
that meets ControlCenter Performance Manager (which is not installed in this scenario) to check
requirements?**
port throughput.
Figure 56 provides an example of how a port with no throughput appears in
Performance Manager.
A description of ProShop’s Performance Manager implementation is provided in the
ControlCenter Reporting: Know What You Have Implementation Guide.
Figure 56 Using Performance View to Determine the Throughput on FA-3D Port 0
Determining if Configured Storage is Available

The administrator uses Free Space view and Properties view to determine if configured
storage is available on the Symmetrix array.
Configured storage
available? 1. On the taskbar, clicks the pull-down menu on the blue Storage Allocation button
and selects Free Space.
2. In the Console tree, expands the folders Storage Systems, Symmetrix, and selects
the checkbox beside Symmetrix array 000187400075.

Figure 57 Free Space View Showing Available Unmapped Storage
The Free Space view shows that there is not enough available unmapped storage. The
administrator will configure additional storage on this array to meet their requirements.
The administrator now splits the target panel horizontally using Alt-Shift-h, clicks the
Properties view button, and drags the array into the Properties view to confirm that
unconfigured storage is available on the array (Figure 58). There is 331.64 GB of
unconfigured storage available.
Figure 58 Properties View Showing Unconfigured Storage
Configuring Unconfigured Storage

For this project, the storage for the database needs to be at least 40 GB (mirrored). Since
the Symmetrix array uses 8.46 GB standards, The administrator needs to create five 8.46
Configure storage GB drives, and five 8.46 GB unprotected devices that will be converted to BCVs.
The Symmetrix arrays appear.
2. Right-clicks the Symmetrix array and selects Configure, Logical Device
Configuration.
The Logical Device Configuration dialog box opens.

3. Creates five standard volumes and five unprotected volumes, each containing
18,484 cylinders (equivalent to 8.46 GB) as follows:
Adds five standard devices to the configuration as follows:
a. In the No. Volumes to create field, enters 5.
b. For the size, enters 18484 Cylinders (which is equivalent to 8.46 GB size).
c. For configuration, selects Mirror-2 devices.
d. Clicks Add to add the configuration to the Requested Configuration table. At the
bottom of the Requested Configuration table, the Configuration Total shows how
much space will be used to create the configuration.
Adds five unprotected devices to the configuration (for use as BCVs) as follows:
a. In the No. Volumes to create field, enters 5.
b. For the size, enters 18484 Cylinders (which is equivalent to 8.46 GB size).
c. For configuration, selects UNPROTECTED.
d. Clicks Add to add the configuration to the Requested Configuration table. At the
bottom of the Requested Configuration table, the Configuration Total shows how
much space will be used to create the configuration.
Figure 59 Logical Device Configuration
4. Clicks Execute to run the proposed configuration.

It takes several minutes to create the devices. When the execution steps finish, the
administrator is prompted to close the window.
5. In the Console tree, expands the Symmetrix array and expands the folders
Unmapped Devices, Standard Devices.
The 10 devices that were just created appear at the bottom of the list.
6. Selects the devices and drags them into the Properties view to verify that there are
five two-way mirrored and five unprotected devices.
Figure 60 on page 105 shows the 10 devices: five two-way mirrored devices and five
unprotected devices.

Figure 60 Symmetrix Devices
Creating BCVs The administrator now creates BCVs from the unprotected devices they just created.
Configure storage 1. Selects the five unprotected devices from the Properties view.
2. Right-clicks the selected device and selects Configure, Device Type Definition.
The Device Type Definition dialog box appears (Figure 61).
3. Selects the devices and clicks the BCV button.
The devices type changes to BCV and is highlighted in blue (Figure 61).
Figure 61 Define BCVs
4. Clicks Execute to start the device type conversion.

5. Closes the window when the device type conversion is complete.
6. Uses the Properties view to ensure that the devices were changed to BCVs.
Now that the BCVs have been created, the administrator can map the new standard
devices to the FA port.

Configuring the Connection

The administrator configures the connection to the Symmetrix storage array by:
Configure ◆ Mapping devices to the FA port.
connection
◆ Zoning the Symmetrix to the host.
◆ Masking the devices.
Mapping Devices to a FA Port

In previous sections, the administrator found an available port (FA-3D Port 0) on the
Configure Symmetrix array and confirmed that it is suitable for this configuration. Now, the
connection administrator uses Symmetrix Device Reallocation (SDR) to map the new standard and
BCV devices to the FA port.
Gatekeeper devices may also need to be added to the host depending on what kind of
information needs to be collected from the Symmetrix array. For example, the
administrator placed the Storage Agent for Symmetrix on the new host and mapped
two gatekeeper devices to the host as outlined in Appendix A, Installation Notes.
1. In the Console tree, right-clicks the Symmetrix array (000187400075) and selects
Configure, SDR.
The SDR dialog box appears.
2. Under Selected Devices, expands Unmapped Devices, and selects the standard
devices (created in the previous sections) and gatekeeper devices (if required) to
map to the FA port.
3. Under Select a Port, expands Host Directors and selects the director and port:
FA-3D Port 0.
4. Selects Port 0 to highlight it, and clicks the Copy button.
The devices move from the left panel to the right panel under the selected port.
5. Repeats this procedure to add the new BCVs. The administrator selects FA-3C Port
0.
6. Clicks Continue to commit the changes.
The dialog box displays the proposed changes.
7. Clicks Execute to perform the changes.
The screen is updated as the changes are made.
When the execution steps finish, the administrator is prompted to close the window.

Zoning the Symmetrix to Host

The host needs to be zoned to the FA port where the new devices are mapped. The
Configure administrator needs to create a new zone that contains the HBA and the FA port on the
connection Symmetrix.
1. On the toolbar, clicks the Topology button to display the Topology view.
2. Drags host l82ar156 into the view.
The Topology view shows that the host and storage are in the fabric called
Mainstreet_3800.
3. Expands the host and the storage to display the HBAs and the storage Fibre Channel
adapters.
Figure 62 Mainstreet Topology View
4. In the Console tree, expands the folders Connectivity, Fabrics, Mainstreet_3800.

5. Right-clicks the folder Planned Zones and selects Zoning, Manage Zone.
The Zoning wizard appears (Figure 63 on page 108).
6. Enters a new zone name using the same naming convention as the existing zones.
7. Under Available Members, selects the Mainstreet_3800 fabric.
8. Selects the Host Ports filter to view only the HBAs
9. Selects the HBA for l82ar156 and clicks Add.
10. Filters by Storage Ports, selects FA-3D, and then clicks Add.
The two selected members will be listed in the Member in Zone section.
11. Clicks Apply, and then OK.

Figure 63 Adding a Zone
The new zone appears under the folder Planned Zones.

12. In the Console tree, expands the folders Connectivity, Fabrics, Mainstreet_3800
fabric.
13. Right-clicks the folder Planned Zone Sets and selects Zoning, Manage Zone Set.
The Manage Zone Set dialog box appears (Figure 64 on page 109).
14. Selects Existing Zone Set, and then selects Playbooks_3800 Zone Set from the
pull-down menu.
15. Selects the new zone from the available zone list, and then clicks Add to add it to the
zone set.
16. Selects Activate Zone Set Immediately.
Selecting this box sends the new zone set to the switch and makes it active on the
switch.
17. Clicks OK.
Activating a new zone set can have serious consequences. The wizard will prompt,
Are you sure you want to activate zone set Playbooks_3800 to fabric
Mainstreet_3800.
18. Clicks Execute and enters a task name for the task lists.
The new zone set is sent from ControlCenter out to the switch. ControlCenter makes
a copy of the previous active zone set, places it in the Planned Zone Sets folder, and
marks it as Last Active. The Active Zone Sets folder is updated with the new active
zone set.

Figure 64 Activating a New Zone Set
The Connectivity tree view is updated to display the new active zone set and the copy
of the previous active zone set.
Figure 65 Tree View Showing New Active Zone Set

Masking Devices The host l82ar156 cannot access the new devices until the masking privileges have been
granted. The administrator needs to mask the devices to grant the host access to the
Configure devices.
connection
1. In the Console tree, right-clicks the host (l82ar156) and selects Masking, Modify
Masking Configurations.
The Device Masking Wizard appears (Figure 66).
Figure 66 Device Masking Wizard
Devices are granted specifically to the HBA, not the host itself.
2. Selects the HBA on which to grant device access by toggling the checkbox.
3. Selects the particular FA through which the host will access the devices: FA-3D.
The FA port is also part of the access record for device masking.
4. Selects Show Devices.
This creates a table for every device available behind the selected adapter (FA-3D).
5. Selects the checkboxes for devices 1F4 through 1F8, and then clicks Grant.
The masking column now shows Granted for those devices.
6. Clicks Continue.

The Modify Masking Configuration Results window now lists the details of the
masking operation the administrator created (Figure 67).
The administrator reviews the list to ensure that the correct devices were selected.
7. Selects the option to Activate the VCMDB.
This ensures that the Fibre Channel adapters on the Symmetrix array are updated
automatically when the masking operation completes. Otherwise, the administrator
can update the Symmetrix array after the operation completes by right-clicking the
array in the Console tree and selecting Masking, VCMDB Management, Make
Active.
Figure 67 Modify Masking Configuration Results
8. Clicks Execute.
The Execute Now Task List appears.
9. Selects the task list defaults or types a new name like Device Masking.
10. Clicks OK to begin the task.
This task will appear in the Console tree under the folders Storage Administration,
Task Lists.
Once the task completes, the host can now access the new devices 1F4 through 1F8.
The sd.conf file must have been modified with the appropriate target entries, and
the system must be rebooted before the devices can be recognized.
11. Right-clicks the host and selects Host, Rescan Disks.
This rescans the host bus so the host can detect the new devices.
Creating Device The administrator creates a device group containing the standards and BCVs to simplify
Groups the process of establishing devices. Placing both standards and BCVs in the same device
group allows the administrator to establish all devices at once instead of individually.
2. Expands the Symmetrix array (000187400075), the folder Mapped Devices, and then
Standard Devices.
3. Selects the standard devices for the host: 1F4 through 1F8.

4. Right-clicks the highlighted hosts and selects Data Protection, Device Groups,
Create.
The Device Group Wizard appears.
5. Chooses the type of device group to create. The administrator selects Regular, and
then clicks Next.
The Create Group Wizard - Create screen appears (Figure 68).
6. Selects the host in which the device group will be created: l82ar156.
7. Under Device Group Name, clicks Add Members to a New Device Group.
8. Enters the name for the new device group: databasedg.
Figure 68 Creating a Device Group
If the administrator needs to add or remove members from the device group, they
can click the Edit Members button.
9. Clicks Next when finished with the selections.
10. Selects the Associate BCV checkbox.
11. Enters the number of BCV sets and clicks Next.
The administrator enters 1, for one copy of the database.
The wizard chooses the BCVs and enters them in the Final Devices column.
12. Removes the BCV devices selected the wizard and replaces them with the BCV
devices created earlier (1F9 through 1FD).
The administrator can make changes by highlighting a device and clicking Add or
Remove.

13. Clicks Next.

The administrator is prompted to confirm the configuration before creating the
device groups.
14. Clicks Finish to confirm the configuration.
A pop-up box confirms that the device group was created.
15. Clicks Finish to complete the task.
16. Verifies that the device group was created by expanding the host in the Console tree
and then the folder Device Groups.
The device group appears (Figure 69).
Figure 69 List of ProShop Device Groups
Establishing BCVs with Standards

The administrator establishes the BCVs with the standards.
1. In the Console tree, expands the folder Hosts, the host l82ar156, and the folder
Device Groups.
2. Right-clicks device group databasedg and selects Data Protection, TimeFinder,
Establish.
The TimeFinder Establish dialog box appears.
3. Clears the Incremental checkbox, and then clicks Execute.
The BCV will be established to the standard.
4. Selects the TimeFinder view, and then selects the device group to watch the
progress of the establish.
Once the device groups have established, the devices can be updated on the host
system.

Discovering Devices on the Host

The administrator has completed storage allocation and now updates the disk
Discover devices information on the host after the configuration change.
on host
1. In the Console tree, right-clicks host l82ar156 and selects Host, Rescan Disks.
A login dialog box appears the first time during the session that an attempt is made
to perform a command that requires user authentication on this host.
2. Enters the Username and Password that provide the necessary privileges to
complete the rescan task on this host.
3. Once the rescan completes, right-clicks host l82ar156 and selects Rediscover.
The Discover data collection policy runs, and the host information in the Console is
updated (Figure 70).
Figure 70 New Devices are Visible to the Host

Allocating CLARiiON Devices (LUNs) to a Host

The administrator needs to add 10 GB of RAID 5 storage to l82ar136, one of two IBM
AIX application servers using the CLARiiON CX600 array.
The administrator completes the following tasks to allocate storage from the CLARiiON
array:
◆ Ensures the CLARiiON storage is accessible from the host
◆ Finds the available storage
◆ Creates new LUNs if necessary
◆ Adds LUNs to an existing storage group (or create a new one) so the host sees the
LUNs
Determining if Storage is Available on the CLARiiON Array

The administrator determines if there is available storage on the CLARiiON array
through a StorageScope Array Configuration report.
Required To do this, the administrator:
storage available
on array?* 1. In the Console tree, expands the folders Storage Systems, CLARiiON.
2. Right-clicks the array (WRE00022201023) and selects Reports.
The Select Report dialog box appears.
3. Ensures that Array Configuration is highlighted and clicks OK.
The Array Configuration report for this array is generated (Figure 71).
Figure 71 StorageScope Array Configuration Report for ProShop’s CLARiiON Array
The administrator determines that there is 3,744.13 GB of unconfigured space, 1,514.66

GB of configured space, and 1,351.12 GB of allocated space on this array.
Allocating CLARiiON Devices (LUNs) to a Host 115

Determining if Type of Connection is Available

The administrator intends to add new storage to host l82ar136 and checks to ensure that
the array is accessible.

connection
available?
1. On the Console toolbar, clicks the pull-down menu of the blue Storage Allocation
button and selects Path Details.
2. In the Console tree, expands the folder Hosts, and then drags host cl82ar136 into the
target panel.
A table showing the path details by HBA for this host appears.
3. Clicks any HBA in the table.
The Path details for the host appear as shown in Figure 72.
Figure 72 Path Details for Host l82ar136
Figure 72 shows that there is connectivity between the host and the CLARiiON array
(serial number WRE00022201023).
Port available Because the path already exists, the administrator does not need to determine if ports
that meets are available, and can skip that portion of the workflow.
requirements?**
Determining if Configured Storage is Available

The administrator determines if there is available configured storage on the CLARiiON
array through the StorageScope Array Configuration report generated in Determining if
Storage is Available on the CLARiiON Array on page 115. The StorageScope Array
Configured storage Configuration report is shown in Figure 73 on page 117.
available?

Figure 73 StorageScope Report Showing Available Configured Storage
The administrator determines that there is over 150 GB of available configured

unallocated storage.
The administrator also needs to ensure that the available storage is the correct
protection type (RAID 5).
1. On the Console toolbar, clicks the Properties view button.
2. In the Console tree, expands the CLARiiON array.
3. Drags the unmapped LUNs into the Properties view.
4. Sorts on the configuration column (by clicking the column heading).
This shows the RAID-level protection of the LUNs.

The administrator determined in the previous section that LUNs are available for
Configure allocation. If ProShop did not have LUNs available for allocation, the administrator
connection could create the LUNs using EMC ControlCenter Navisphere Manager.
The administrator allocates the existing LUNs as follows:
◆ Determines if a storage group exist
◆ Finds available LUNs
◆ Adds LUNs to the storage group
Determining if Storage Group Exists

The LUNs will be placed in a storage group for the host. Only one storage group can
Configure exist per host. The administrator determines that a storage group already exists by
connection selecting the host in the Console tree, and selecting Storage Allocation, Path Details in
the toolbar. Figure 74 shows that the existing Storage Group is named l82ar136_AIX.
If this host did not have a storage group, the administrator could have created a new
one by right-clicking Storage Groups under the CLARiiON array in the Console tree
and selecting New. This displays the Storage Group Configuration Wizard.

Figure 74 Storage Group
Finding Available The administrator finds the available (unmapped) LUNs on the array by right-clicking
LUNs Unmapped LUNs under the CLARiiON array in the Console tree and selecting
Properties.
Configure
connection ProShop requires 10 GB of RAID 5 storage. LUNs 62 through 71 will meet ProShop’s
needs as shown in Figure 75.
Figure 75 Available Unmapped LUNs
The administrator adds the LUNs to storage group l82ar136_AIX through the Storage
Group Configuration Wizard.
1. In the Console tree, expands the folders Storage Systems, CLARiiON, Storage
Groups.
2. Right-clicks storage group l82ar136_AIX and selects Edit.
The Storage Group Configuration Wizard appears displaying the storage group the
administrator intends to edit.
3. Clicks Next.
The Add/Remove LUNs screen appears (Figure 76 on page 119).

Figure 76 Adding LUNs to the Storage Group
4. Finds the appropriate LUNs on the left side of the wizard screen and clicks Add to
add them to the Storage Group. The administrator adds LUNs 62 through 71.
5. Clicks Finish. The proposed changes are displayed.
6. Reviews the proposed changes and clicks Execute.
A task list appears.
7. Fills in the task list name and task name to easily view the execution progress and
status. The administrator names the task l82ar136 (after the host).
8. Confirms that the LUNs were successfully placed in the Storage Group by clicking
the Properties button on the toolbar, and then expanding the following in the
Console tree: Storage Administration, Tasklist, SAN Tasklists, l82ar136.
The table shows a status of Succeeded.
Figure 77 Storage Group Configuration Task Succeeded

Discovering LUNs on Host

on host
updated.
Figure 78 shows the new LUNs appearing in the storage group for l82ar136 in the
Console tree. The server sees the devices after rediscovery is complete. ProShop’s IT
team has completed the allocation of LUNs to the application server.
Figure 78 LUNs are Now Available to the Application Server

Adding Devices to a CLARiiON MetaLUN for a Host

ProShop uses metaLUNs on the CLARiiON CX600 array as a way of managing groups
of devices based on the type and amount of storage required by various business
applications. metaLUNs are groups of striped or concatenated LUNs that can be easily
created or expanded using the ControlCenter Expand Storage Wizard.
In this scenario, the administrator received a ControlCenter Free Space alert that a
logical volume on an AIX host has reached a critical space threshold with only five
percent capacity remaining.
Note: Refer to the ControlCenter Monitoring: Respond to Issues Implementation Case Study, for details
on how to configure and respond to Free Space alerts.
After acknowledging the alert, the administrator determines that all of the allocated
RAID 5 storage (80 GB) for host l82ar134 is utilized and that an additional 80 GB of
RAID 5 storage must be allocated.
The following steps are required to allocate additional storage to the host:
◆ Determine if Storage is Available
◆ Start the Expand Storage Wizard
◆ Select LUNs to add to metaLUN (or create metaLUN)
◆ Review and Execute the Expansion
◆ Confirm the Allocation
Determining if Storage is Available

The administrator determines the array and the LUNs accessible to the host by dragging
the host from the Console tree into the Relationship view. Figure 79 shows that host
l82ar134 is connected to the CLARiiON CX600 array and an existing metaLUN named
LUN 15 META. The administrator will add more storage to the host by adding LUNs to
the existing metaLUN using the Expand Storage Wizard.
Figure 79 Relationships View
Adding Devices to a CLARiiON MetaLUN for a Host 121

Starting the Expand Storage Wizard

The administrator starts the wizard as follows:
1. In the tree panel, expands the Storage Systems folder.
2. Expands the CLARiiON array containing the metaLUN for host l82ar134.
3. Expands the Mapped LUNs folder to display the LUNs (and metaLUNs) on the
array.
4. Right-clicks the metaLUN (LUN 15 Meta) and selects Configure, Expand LUN.
The Expand Storage wizard appears, showing the current state of the metaLUN. In
this case, the wizard shows that all of the 80 GB of RAID 5 storage is utilized (Figure
80).
5. Clicks Next to begin selecting the LUNs to add to the metaLUN.
Figure 80 Expand Storage Wizard
Selecting the LUNs

The first Select LUNs screen displays all of the available LUNs. The administrator
selects LUNs as follows:
1. Scrolls through the Available LUNs panel to find 80 GB of RAID 5 storage.
2. Selects the appropriate RAID group and clicks Add to add the RAID group to the
right-hand panel. The new maximum capacity (160 GB) appears.

Figure 81 Selected RAID Group Showing New User Capacity
3. Clicks OK after determining that enough storage is selected. The wizard displays
the new metaLUN components and the new maximum capacity (Figure 82).
Figure 82 RAID Groups and LUNs by Component

Reviewing and Executing the Expansion

The administrator verifies the metaLUN properties as follows:
1. Clicks Next and verifies (the administrator makes no changes) the final metaLUN
Properties information, and then clicks Next again to review the metaLUN
configuration.
Figure 83 shows the new devices that will be added to the metaLUN.
Figure 83 Review MetaLUN Configuration
2. After reviewing the details for the metaLUN expansion, the administrator clicks
Execute to complete the task.

Confirming the Allocation

The administrator confirms the allocation of additional storage to the host by dragging
the host from the Console tree into Relationship view (Figure 84). The new RAID group,
containing LUNs 24, 25, 26, and 27, is now part of the expanded metaLUN and
accessible to the host.
Figure 84 Relationship View Showing New LUNs in MetaLUN

on host
updated.

Adding HP XP LUSEs to a Host

The administrator is adding a new website and requires an additional 20 GB of RAID 5
storage for the Web server. The Web server (l82ar122) is an existing host that is already
cabled and zoned to an HP XP array.
During the initial setup and configuration of the HP XP array and this host, the
administrator used ControlCenter to complete the following tasks:
◆ Enabled LUN security on the array port (otherwise, all LUNs mapped to this port
will be accessible to the connected host.)
◆ Set the host mode on the array ports to specify which hosts (based on OS) can access
the LUNs on the array.
◆ Zoned the host and array ports
◆ Registered the host port (HBA WWN) with the storage port.
Once the array ports are set up correctly, the administrator adds storage to the Web
Server as follows:
◆ Determines the array port
◆ Determines if storage is available
◆ Creates LUSEs (logical unit size expansion volumes)
◆ Masks devices to the array port
◆ Discovers devices on host
Determining the Array Port

The administrator uses the Relationship view to determine which port on the array has
connectivity to the host.
1. On the Console toolbar, clicks the Relationship button to display the Relationship
view.
2. In the Console tree expands the folders Windows Hosts, and drags host l82ar122
into the Relationships view (Figure 85).
The Relationship view shows that host l82ar122 is connected to the HP XP array
30471 through Director CHA-2X, Port CL2-K.
Figure 85 Use Relationship View to See Host to Array Port Connectivity

Determining if Storage is Available on the HP XP Array

The administrator uses the Properties view to see if there is any available storage.
Required
storage available 1. On the Console toolbar, clicks the Properties button to display the Properties view.
on array?*
2. In the Console tree, expands the folders Storage Systems, HP XP Arrays (if not
already expanded).
3. Drags the HP XP array and the Unmapped Devices into the target panel.
The Array Properties appear (Figure 86).
Figure 86 Use Properties View to Determine if There is Enough Unallocated Capacity
The administrator uses the Size and RAID Level columns from the Properties view to
determine that there is enough unallocated capacity of the appropriate size and RAID
level for allocation to the Web server.
Creating LUSEs
Logical unit size expansion (LUSE) volumes combine two or more HP XP devices
(LDEVs) to function as one large device, much like a metadevice on a Symmetrix array.
The LUSE appears as a single large device instead of several smaller ones to the host.
The Properties view showed that there were enough unmapped 2.29 GB devices with
RAID 5 protection available to provide the 20 GB of new storage for the host. The
devices are located on control units (CU) 1 and 2.
Because these devices are not all on the same control unit (CU), the administrator
creates two LUSEs (a LUSE cannot contain devices with different CUs).
The administrator creates the LUSEs as follows:
1. In the Console tree, expands the folders Storage Systems, HP XP Arrays (if not
already expanded).
2. Right-clicks the StorageWorks XP array (30471), and selects Configure, New LUSE.
The New LUSEs dialog box appears (Figure 87).
3. Under Select Devices, selects either All to view all of the devices and their CUs or
selects the specific Control Unit (1) to view the devices it owns. The devices appear
in the table under the menu.
Adding HP XP LUSEs to a Host 127

4. In the devices table, holds the Ctrl key down and selects the devices to add to the
LUSE volume. The lowest number ID number will become the meta head (top
device) of the LUSE volume (1:98 in this case).
5. Under Select Ports, selects the port to map the LUSE volume. The administrator
maps to CL2-K.
6. Checks Select Lun Address Automatically to have the next available LUN ID
applied to the LUSE volume when it's mapped.
7. Clicks Create to establish the LUSE volume.
8. Selects Control Unit 2 from the menu and repeats steps 4 through 7.
Figure 87 Create the LUSEs
9. Clicks Continue to display the preview panel.

10. Reviews the details of the proposed LUSE volumes, and then clicks Execute to
create them.
The two LUSEs, consisting of nine 2.29 GB RAID 5 devices are now mapped to the
correct array port and ready to be masked to the host. The LUSEs are identified by the
lowest numbered device in each LUSE. In this case, the LUSEs are 1:98 and 2:36.

Assigning (Masking) the LUSEs to the Host Port

The administrator assigns (masks) the two LUSEs to the host port.
Configure To do this, the administrator:
connection
1. On the taskbar, clicks the pull-down menu on the blue Storage Allocation button
and selects Masking to display the Masking view.
2. In the Console tree, expands the folders Storage Systems, HP XP Arrays.
3. Selects the appropriate array (30471), and expands Controllers, (CHA-2X), and the
storage port (CL2-K).
4. Selects Registered host ports in a WWN folder.
The Masking view opens with filter area and a table. The HP XP 512 is displayed in
the Select Storage Type drop-down list (Figure 88).
Figure 88 Masking the LUSEs to the Host Port
5. Selects the storage array (30471) displayed in the list box below the Select Storage
Array drop-down list.
6. Selects the storage port (CL2-K) in the Select Storage Port drop-down list.
7. Selects the WWN (host port) from the Select WWN Group/WWN tree window. The
Related Tree Selection panel populates with the WWN (host port) selection.

8. Clicks Show Devices. The Masking view table populates with all the LUNs mapped
to the storage port selected in the Select Storage Port field.
This table can be filtered based on the type of devices that the administrator
requires. In this case they used the default setting to show All Devices.
9. Selects the two LUSEs based on the names of the lowest numbered devices in each
group, 1:98 and 2:36.
10. Right-clicks the highlighted LUSEs and selects Grant Access Rights to add host
access to the selected LUSEs for the host port (HBA WWN) selected in the
ControlCenter tree panel.
The Masking review dialog box appears listing the masking actions created in the
current Masking view session.
11. Clicks Execute.
The masking actions are sent to the ECC Server for execution. When the masking
actions finish, the changes appear in the Console and a popup message indicates the
operation completed successfully.

Discovering Devices on Host

The administrator has completed allocation of storage to the Web server and now
Discover devices updates the disk information on the host.
on host
updated.
4. On the Console toolbar, clicks the Properties button to display the Properties view.
5. In the Console tree, expands host l82ar122 and the folder Host Devices.
6. Drags the Host Devices folder into the Properties view to view the details.
Figure 89 shows the new host devices totaling 20.62 GB.
Figure 89 Devices are Now Available to the Web Server

Adding Symmetrix Devices to a Host Using Storage Provisioning Services

In this example, ProShop uses ControlCenter Automated Resource Manager (ARM)
Storage Provisioning Services to allocate storage to a database host instead of using the
“manual” method described in Allocating Storage to a Host from a Symmetrix Array on
page 96.
In this scenario, a new Sun Solaris database host (l82ar156) is added to the ProShop
environment. The administrator needs to add additional storage to the database host
based on the storage allocation workflow outlined in previous sections.
Based on growth and performance estimates, the ProShop Oracle DBA requested 40 GB
of RAID 1 storage with local replica for Oracle for the new host. The system
administrators determine they need to find and allocate a total of 120 GB of space (40
GB for the standard devices, 40 GB for the mirror devices, and 40 GB for the BCV
devices) to meet ProShop’s RAID protection and local replica business requirements.
The host and the Symmetrix array are physically connected to the same fabric as shown
in Figure 47 on page 96.
The administrator installed, configured, and tested ControlCenter on this host using the
procedures outlined in previous chapters of this case study.
ProShop needs the ControlCenter Automated Resource Manager license for this scenario.
Using Storage Provisioning Services to Allocate Storage

The complex series of tasks required to allocate storage can be simplified and
automated through the use of a ControlCenter feature called Storage Provisioning
Services (SPS), licensed under Automated Resource Manager. SPS takes into account
ProShop’s business practices for allocating storage and automates many of the steps
required to fulfill those allocation requests. It finds devices that meet ProShop’s criteria
and performs the necessary operations, such as SDR, LUN masking, and zoning.
SPS automates the storage allocation process, but the administrator needs to create
devices, find free space, and set up storage pools and policies before using SPS.
The administrator completes the following tasks to allocate storage in this scenario:
◆ Determines available storage
◆ Creates storage pools and storage policies
◆ Allocates storage using SPS
◆ Reviews and executes the task lists
Determining Available Storage

Prior to allocating storage, the administrator needs a clear picture of how much unused
space is currently available to the host.
1. On the taskbar, clicks the pull-down menu on the blue Storage Allocation button
and selects Free Space.
2. In the Console tree, expands the folders Storage Systems, Symmetrix, and selects
the checkbox beside Symmetrix array 000187400075.

Figure 90 Free Space View Showing Available Storage
Creating Storage Pools and Policies

SPS uses storage pools and storage policies as a way of grouping devices and
controlling device allocation. The administrator creates a storage pool of devices and a
storage policy for device allocation before using SPS.
Creating Storage Storage pools are groups of devices that are logically placed together and used for
Pools allocations. The grouping can be done in any way that meets the customer's needs,
based on geography, performance, department, and so on. SPS uses the devices in these
storage pools for allocation. The administrator needs to create the storage pools.
To create storage pools, the administrator:
1. In the Console tree, expands the folder Storage Administration.
2. Right-clicks the folder Storage Pools and selects New, Storage Pool.
A New Storage Pool folder appears.
3. Names the storage pool: Main Street Datacenter Sandbox.
4. Creates daughter pools named Primary and Local Replica under the Main Street
Datacenter Sandbox storage pool using the same technique.
5. Populates the new storage pool with the standard and BCV devices created earlier
as follows:
a. In the Console tree, expands the following: Storage Systems, Symmetrix,
000187400075, Unmapped Devices.
b. Right-clicks Standard Devices and selects Properties.
The target panel is populated with the properties for those devices.
c. Sorts on the Configuration column by clicking the column heading.
d. Shift-selects all of the 2-Way Mir devices.
e. Drags the selection to the Primary storage pool under the Main Street
Datacenter Sandbox storage pool.
f. Clears the view.
g. Shift-selects all of the BCV devices in the tree.
h. Drags the selection to the Local Replica storage pool under the Main Street
Datacenter Sandbox storage pool.
Adding Symmetrix Devices to a Host Using Storage Provisioning Services 133

Creating Storage Prior to using SPS, ProShop’s senior-level system administrators translated their
Policies business rules into storage policies. Storage policies contain information such as the
level and type of protection, the type of storage used for an allocation, whether zoning
operations should be performed, and whether host actions should be performed.
To create storage policies, the administrator:
1. In the Console tree, expands the folder Storage Administration.
2. Right-clicks the Storage Policy folder and selects New.
The Storage Policy Editor - New Policy window appears.
3. In the Policy Name field, enters Main Street Datacenter.
4. Selects Use this Policy as default to set the default storage policy.
5. Leaves Replica Class as Primary + Local.
6. Under Storage Element's Attributes, selects the storage pool for each storage
element:
a. For Primary Device, selects Primary Storage Pool.
b. For Local Replica, selects Local Replica Storage Pool.
7. Leaves the Storage Type as Symmetrix.
8. Selects the RAID level for each storage element:
a. For Primary Device, leaves it as RAID_1.
b. For Local Replica, selects RAID_0.
9. Leaves Port Balancing as Host Based.
10. Leaves # Paths as 1.
11. Clears Mapped Device Only for both Primary Device and Local Replica.
12. Clears Zoned Storage for both Primary Device and Local Replica.
13. Leaves Zoning Type as WWN Zoning.
14. Selects Disable Host Actions for both Primary Device and Local Replica.
15. Clicks Save.
The storage policies are now created.
Creating an Allocation Request with SPS

Once the storage policies are created, ProShop’s systems administrator allocates storage
based on the new policies.
1. In the Console tree, expands the folder Hosts.
2. Right-clicks host l82ar156 and selects Allocation, Storage Provisioning Services.
The Storage Provisioning Services Wizard appears.
3. Verifies that host l82ar156 appears in the Add Storage to Host(s) field.
4. Verifies that the storage policy is correct. The administrator selects Main Street
Datacenter as the default policy, so it automatically appears in the Storage Policy
field.
5. Clicks More Options and sets the Amount to Allocate to At Least 40 GB.

6. Enters the number of devices for Requested # of Devices: Range.
Figure 91 Creating an Allocation Request through the SPS Wizard
7. Clicks Next.
The Select Replica Host screen appears.
8. Under Select Replicas, selects Local Replica.
9. Under Select Hosts, selects the host to which the local replica is allocated.
The administrator allocates the local replica to l82ar155 to ensure that the local
replica and standard devices are not allocated to the same host.
10. Clicks Add and verifies that the host appears under Selected Hosts per Replica,
Local Replica.
11. Clicks Next.
SPS now performs a query for devices that meet the criteria. The details of Proposed
Path screen appear.
12. Verifies that there are two entries:
• Row 1 for Primary Device
• Row 1S for Local Replica
13. Clicks Next.
The Device Group Selection screen appears because the storage policy required
devices to be added to a device group.

14. Selects the hostname (l82ar156) where the device group resides (the device group
must already exist).
15. Selects the device group: prim_local.
16. Clicks Next. The Review Allocation Task screen appears.
17. Clicks the tabs Replica Host, Specification, Path Details, and Device Group to
verify the information.
18. Clicks Execute Later.
The Execute Later window appears.
19. Enters a new task list name: l82ar156 new db storage.
20. Enters task name l82ar156.
21. Clicks OK.
Reviewing and Executing Task Lists

Prior to executing requests, storage administrators can review the requests. Then they
can either modify the requests or execute them. The execution runs in the background,
but can be monitored through Properties view.
To review the task list, the administrator:
1. On the toolbar, clicks the Properties button to display the Properties view.
2. In the Console tree, expands the folders Storage Administration, Task Lists,
Allocation Task Lists.
3. Place a check next to task list l82ar156 new db storage so it appears in the Properties
view.
4. In the Properties view, double-clicks the task name l82ar156.
Actions for the task appear.
5. Right-clicks the task list and selects Execute Task List.
A Verification window appears.
6. Clicks Yes to execute.
The Properties view for the task list automatically updates as the execution goes
through each action.

Figure 92 Task Execution Succeeded
Discovering Devices on Host

ProShop’s IT team has completed the allocation of storage devices to the new host. The
host has been rescanned and rediscovered, and the devices are visible as shown in the
Console tree (Figure 93).
Figure 93 New Devices are Visible to the Host

Deallocating Storage from a Host

The administrator allocated too much storage to Windows host l82at124 and now
deallocates 40 GB of storage using the ControlCenter Deallocation Wizard.
The Deallocation Wizard allows the administrator to remove the relationship between
the host and specified storage devices to which it has access (as long as the objects are
connected through Fibre Channel paths).
The administrator completes the following steps to deallocate storage:
◆ Determine the Amount of Free Space on the Host
◆ Determine the Host Devices to be Deallocated
◆ Start the Deallocation Wizard
◆ Create Deallocation Policies
◆ Select the Host
◆ Confirm the Objects and Select a Policy
◆ Select the Deallocation Paths
◆ Review and Execute the Task
Determine Amount of Free Apace Available on Host

The administrator uses Free Space view to determine the amount of free space on host
l82at124. Figure 94 shows that this host has a little over 48 GB of free space. The
administrator decides to deallocate 40 GB from this host.
Figure 94 Free Space View of Host l82at124

Starting the Deallocation Wizard

The administrator starts the wizard as follows:
1. In the Console tree expands Hosts, l82at124, Host Devices, and highlights devices
c6t9d10 and c6t8d11.
In this case, the administrator had already determined which devices to deallocate,
however, they could have simply selected host l82ar124 and used the wizard to
determine which devices were not in use and could be safely deallocated.
2. Right-clicks the devices and selects Allocation, Deallocate.
The Deallocation Wizard starts (Figure 95).
The dialog box shows the host devices that were previously selected as well as any
available deallocation policies.
The administrator can add objects by dragging them from the tree or remove them
by selecting the device and pressing Delete.
3. Clicks New to create a new policy.
The administrator could have used or edited the policy provided by ControlCenter
as a default, or used or edited an existing policy available through the drop-down
menu.
Figure 95 Starting Deallocation Wizard
Deallocating Storage from a Host 139

Editing (or Creating) the Deallocation Policy

Deallocation policies define the actions to be performed during the deallocation task,
such as rediscovering a host, unmapping devices from the front end of a storage array,
and dissolving metadevices.
A default Deallocation Policy is provided but the Administrator creates a new policy
using the Deallocation Policy Editor (Figure 96).
The administrator creates the new policy as follows:
1. Names the policy CLARIION_FREE_DEVICES, and ensures that Use this policy as
system default is cleared.
This is a policy unique to CLARiiON array deallocations and will not be the
standard policy that the administrator uses to deallocate storage for every array.
2. Ensures that Disable Host Actions is cleared, and selects Before Executing Tasks,
Rediscover host and fail on error.
This means that the wizard checks which devices are currently in use, and will fail
the deallocation task if storage is still in use by the host.
3. Selects After Executing Tasks, Rediscover Hosts.
This tells ControlCenter to rediscover the host after the deallocation and update the
Repository so all users will see accurate data about the host.
4. Selects Array Actions, Delete device.
This deletes any deallocated devices that are no longer part of any path.
5. Clicks Save to save the new policy and return to the Allocation -- Deallocate dialog
box.
6. Ensures that the (CLARIION_FREE_DEVICES) deallocation policy is selected and
clicks Next.
Figure 96 Create a New Deallocation Policy

Selecting Allocation Paths

The Paths to Deallocate dialog box displays the available paths to be deallocated based
on the objects that were selected in the previous screen. In this case, a total of four paths
to host devices c6t9d10 and c6t8d11 will be deallocated (Figure 97).
Figure 97 Paths to be Deallocated
The administrator confirms that the paths are correct and clicks Next.
The Review Deallocation Task dialog box appears.

Reviewing and Executing the Deallocation Task

The Review Deallocation Task dialog box provides summaries of the Deallocation
Policy and the Paths to Deallocate (Figure 98).
Figure 98 Review Deallocation Task
The administrator completes the deallocation task as follows:

1. Reviews the summaries and clicks Execute.
2. Creates a Task List name, selects View progress/status of tasks, and clicks OK. The
deallocation begins.

3. Follows the progress of the deallocation in the Properties - Task List Viewer.
Figure 99 shows the completed task.
Figure 99 Deallocation Succeeded

The administrator verifies that the deallocation was successful by comparing the initial
Free Space View to Free Space View of the host after the deallocation. Figure 100 shows
that the Host Device free space is now 8.52 GB as opposed to 48.51 GB before the
deallocation (Figure 94 on page 138). 40 GB was successfully deallocated.
Figure 100 Free Space View Showing Successful Deallocation

Allocating Storage Using AutoPath

In a previous scenario, the administrator added storage to a host connected to a
CLARiiON array using the standard workflow outlined in the Overview on page 84. In
this scenario, the administrator intends to allocate storage that is already mapped to a
port on the CLARiiON array, but uses a ControlCenter wizard called AutoPath to
streamline the zoning and LUN masking portion of the storage allocation process.
The administrator completes the following tasks to allocate storage from the CLARiiON
array using AutoPath:
◆ Determines if storage is available on the CLARiiON array
◆ Ensures the CLARiiON is accessible from the host
◆ Uses the AutoPath Wizard to establish the path between host and array by setting
up zoning and LUN masking
◆ Adds LUNs to an existing storage group (or creates one) so the host sees the LUNs
Determining if Storage is Available on the CLARiiON Array

The administrator uses Properties view to determine if mapped storage is available on
the CLARiiON array.
1. In the Console tree, expands the folders Storage Systems, CLARiiON.
2. Right-clicks the array and selects Properties.
The CLARiiON properties appear in Properties view (Figure 101). This view shows
that there is over 3000 GB of locally unallocated capacity available.
Figure 101 CLARiiON Array Properties
3. In the Console tree, expands the CLARiiON array.

4. Drags the mapped LUNs into the Properties view.
Allocating Storage Using AutoPath 145

5. Sorts on the configuration column by clicking the column heading to show the
RAID-level protection of the LUNs (Figure 102).
Figure 102 CLARiiON LUN Properties
Determining if Type of Connection is Available

The administrator uses the Topology view in the ControlCenter Console to verify that
Fibre Channel connections to the array exist.

connection
available?
1. Clicks the Topology button on the Console toolbar.
2. In the Console tree, expands the folders Storage Systems, CLARiiON.
3. Drags array WRE00022201023 into the Topology view.
The Topology view for the CLARiiON array appears (Figure 103).
The administrator turned on Show Links to ensure that the cabling is in place
between host l82ar136 and the CLARiiON array in this fabric.
Figure 103 Verify that a Fibre Channel Connection Exists Using Topology View


The administrator determined in the previous section that mapped LUNs are available
for allocation. Now the administrator checks to see if a zoned path exists between the
host and array. If the path does not exist, they will use AutoPath to create one.
Checking for Existing Path Between Host and Array

The administrator checks for an existing path as follows:
1. On the Console toolbar, clicks Storage Allocation and selects Path Details from the
drop-down menu.
2. Drags the host into the Path Details view (Figure 104).
There are no paths associated with this host.
3. Clicks the Relationship view button.
4. Drags the host into the Relationship view.
There is no path between the host and the array.
Figure 104 Path Details Showing no Zoned Paths between Host and Target Array

Starting the AutoPath Wizard

There are no paths between the host and array, meaning that even though there is a
physical connection between the host and array (as determined by checking the
Topology), the two objects are not zoned together, nor are there any LUNs masked for
this host.
The administrator uses AutoPath to zone the host and array and mask the required
LUNs as follows:
1. Splits the tree panel into two sections so there is access to the array devices in one
screen and access to the host in the other.
2. Selects the logical device(s) and Control-clicks on the host or adapter (ProShop has
only one HBA in this host, so there is no issue with port selection) so that both the
host and the device(s) are selected.
3. After the pair is selected, uses the right-click menu to select Allocation, AutoPath
(Figure 105).
Figure 105 Starting the AutoPath Wizard
The Storage Provisioning Services AutoPath wizard starts and displays the name of the
host adapter and the device (Figure 106 on page 149).
4. Enters the number of Paths (1).
Port balancing is not important in this case since there is only one port available on
the host.
5. Clears Zoned Path Only since the administrator has already determined that no
zoned paths exist between the host and the array.

Figure 106 Using AutoPath to Zone the Host and Array Port
6. Clicks Next.
The wizard provides the details of the proposed path (Figure 107).

Figure 107 Proposed Path Details
7. Ensures that the box beside the proposed path is selected and clicks Next.
The administrator created a default zoning policy for the fabric during
ControlCenter configuration (refer to Creating Zoning Policies on page 77). If a zoning
policy does not exist, an error message appears and the user is instructed to create a
zoning policy before continuing.
The Review Allocation Task dialog box appears (Figure 108 on page 151).
8. Reviews the task, and clicks Execute.

Figure 108 Review the Allocation Task
The Execute Now dialog box appears (Figure 109).

9. The administrator names the task, ensures that View progress/status of Tasks is
selected and clicks OK.
Figure 109 Execute Task
The Properties - Task List Viewer shows the progress of the task (Figure 110).

Figure 110 Properties - Task List Viewer
Confirming Storage Allocation

Once the task succeeds, the administrator uses Properties view on the CLARiiON array
to confirm that additional storage was allocated (Figure 111).
Figure 111 Properties View Showing New Storage Allocated to Host

on host
updated.

What To Do Next
This chapter demonstrated how ProShop used ControlCenter to achieve its storage
allocation objectives. To find out how ControlCenter can help your organization meet its
objectives, explore the product and documentation.
The EMC ControlCenter Open Integration Components (OIC) kit provides the
following information resources for installing and using each of the ControlCenter
products described in this book:
◆ Hard-copy product documentation.
◆ Product documentation PDFs, tutorials, and help systems on the
Documentation/Help CD.
◆ Product documentation PDFs, tutorials, and help systems accessed through the
ControlCenter application.
Figure 112 illustrates each of the information resources.
Figure 112 ControlCenter Documentation Resources
What To Do Next 153


A
Installation
Notes
This appendix contains the completed notes that the ProShop administrator and staff
created during installation. These notes were based on the guidelines provided in the
EMC ControlCenter Planning and Installation Guide, Volume 1 and from the Console online
Help. You can use these notes as an example of what types of information need to be
collected for a ControlCenter implementation.
ProShop completed the following notes based on their business requirements:
◆ Latency ............................................................................................................................ 156
◆ ControlCenter Infrastructure Components................................................................ 157
◆ Master Agent .................................................................................................................. 159
◆ Console............................................................................................................................ 160
◆ StorageScope .................................................................................................................. 161
◆ Fibre Channel Connectivity Agent.............................................................................. 162
◆ Symmetrix SDM Agent................................................................................................. 163
◆ Storage Agent for Symmetrix ...................................................................................... 164
◆ Storage Agent for CLARiiON ...................................................................................... 165
◆ Storage Agent for NAS ................................................................................................. 166
◆ Storage Agent for HDS ................................................................................................. 167
◆ Database Agent for Oracle ........................................................................................... 168
◆ Common Mapping Agent ............................................................................................ 169
Installation Notes 155

Appendix A, Installation Notes
Latency
The EMC ControlCenter Planning and Installation Guide, Volume 1, provides guidelines for
the maximum allowable latency between ControlCenter components. The guidelines
for ControlCenter components are:
◆ Agent-to-infrastructure latency of less than 200 ms.
◆ Console-to-infrastructure latency of less than 15 ms (optimally less than 8 ms).
The administrator used the ping command to test for latency between the infrastructure
host and the agent hosts. The ProShop results were all less than 10 ms, well under the
200 ms maximum recommended by EMC.
ProShop’s Console is on the infrastructure host, so Console-to-infrastructure latency is
not currently an issue.
Table 23 ProShop Agent-To-Infrastructure Latency Measurements
Site/Location Originating Host IP Address To Console
Main Street cawti 168.159.90.60 <10 ms
Main Street csebach 172.23.172.121 <10 ms
Main Street l82at124 172.23.174.124 <10 ms
Main Street l82at125 172.23.174.125 <10 ms
Main Street l82ar122 172.23.172.122 <10 ms
Sandbox l82ar155 172.23.172.155 <10 ms
Sandbox l82ar156 172.23.172.156 <10 ms
Main Street pshpcad1 10.15.64.23 <10 ms
Main Street pshpcad2 10.15.64.24 <10 ms
Main Street psssun01 10.15.64.21 <10 ms
Main Street psssun02 10.15.64.22 <10 ms
Main Street pswapp01 10.15.64.18 <10 ms
Main Street pswapp02 10.15.64.19 <10 ms
Main Street pswexch01 10.15.64.20 <10 ms

ControlCenter Infrastructure Components

The installation notes in this section provide the information required to install
ControlCenter infrastructure components in the ProShop environment.
Installation Directory The size of the infrastructure installation directory is based on which ControlCenter
components will be installed during this initial installation as well as which components
the administrator might install in the future on this host.
The administrator is installing all of the infrastructure components (Repository ECC
Server, and Store), as well as several agents and StorageScope on a single host
(l82ar154). The administrator used the EMC ControlCenter Performance and Scalability
Guidelines and EMC ControlCenter Support Matrix (both available on the EMC Powerlink
website) to determine the drive requirements.
These notes contain the installation directory information used to install ControlCenter
infrastructure components on host l82ar154.
Table 24 ProShop Infrastructure Installation Notes
Item ProShop Notes Definition
Installation directory G:\ECC The directory where the install tools will be
installed. The default directory is C:\ECC.
At the completion of installation, this
directory will contain the ControlCenter
infrastructure.
Repository These notes provide information for installing the ControlCenter Repository on host
l82ar154.
Database Backup H:\ECCBACKUP The directory that holds the Repository hot backup and
Directory export files. Space requirements are the same to
backup and export the Repository as for the Repository
itself. Back up this directory daily to external media such
as tape. These files are overwritten everyday with the
automated scheduled jobs which run, by default, from
2:00 a.m. to 6:00 a.m. (for hot backup) and 10:00 p.m.
to 11 p.m. (for export). Run the backup commands
manually when needed.
The backup directory should be on a different mounted
file system and physical drive from the Repository to
ensure protection of the Repository data in the event
that the physical drive or mounted file system that the
Repository is on has a problem.
Company name ProShop Your company's name.
Enable ECC No Selecting this option fixes the Repository port number at
Repository Access via 1521, disallowing later dynamic port assignment by the
Firewall (Yes/No) network, allowing the Repository to be configured for
later access through a firewall. The default is No.
SMTP Mail Server mail.proshop.co The name of the SMTP Mail Server to use to send
Name m ControlCenter-generated e-mail. E-mail can include
alert notifications, reports, and so on.
ControlCenter Infrastructure Components 157

ECC Server These notes help the administrator install the ControlCenter infrastructure server on
host l82ar154. Only one ECC Server exists for a ControlCenter implementation.
Table 26 ProShop ECC Server Installation Notes
ECC Server Port 5799 The port number associated with the ECC Server. The
Number default is 5799.

Master Agent
These notes help the administrator install the Master Agent on each host.
Hostname Master Agent System Type Physical Location Logical Name IP Address
Port Number
cawti 5798 Windows 2000 Main Street cawti.aselab.proshop.com 168.159.90.60
csebach 5798 Windows 2000 Baker Street csebach.lss.proshop.com 172.23.172.121
l82ar122 5798 Windows 2000 Baker Street l82ar122 172.23.172.122
l82ar123 5798 Windows 2000 Baker Street l82ar123 172.23.172.123
l82at124 5798 Windows 2000 Baker Street l82at124.mgmnt.proshop.com 172.23.174.124
l82at125 5798 Windows 2000 Baker Street l82at125.lss.proshop.com 172.23.174.125
l82ar134 5798 AIX 4.3.3 Baker Street l82ar134.lss.proshop.com 172.23.172.134
l82ar136 5798 AIX 4.3.3 Baker Street l82ar136.lss.proshop.com 172.23.172.136
l82ar154 5798 Windows 2000 Main Street CSE-NT-4.lss.proshop.com 172.23.172.154
l82ar155 5798 Solaris 8 Mainstreet_3800 l82ar155.lss.proshop.com 172.23.172.155
l82ar156 5798 Solaris 8 Mainstreet_3800 l82ar156.lss.proshop.com 172.23.172.156
pshpcad1 5798 HP-UX B.11.00 Main Street tornado 10.15.64.23
pshpcad2 5798 HP-UX B.11.00 Main Street cyclone 10.15.64.24
psssun01 5798 Solaris 8 Main Street psssun01 10.15.64.21
psssun02 5798 Solaris 8 Main Street psssun02 10.15.64.22
pswapp01 5798 Windows 2000 Main Street pswapp01.prosports.com 10.15.64.18
psswap02 5798 Windows 2000 Main Street pswapp02.prosports.com 10.15.64.19
pswexch01 5798 Windows 2000 Main Street pswexch01.prosports.com 10.15.64.20
Master Agent 159

Console
These notes help the administrator install the ControlCenter Console. One or more
Consoles can exist for a ControlCenter implementation.
Table 28 ProShop Console Installation Notes
Console Installation C:\Program The directory where the Console will be

Directory Files\ecc\Console installed. The default is:
C:\Program Files\ecc\Console.

StorageScope
These notes help the administrator install the StorageScope component on host
l82ar154.
Table 29 ProShop StorageScope Installation Notes
Repository hostname l82ar154.lss.proshop.com The host system where the Repository resides.
(logical name)
StorageScope server l82ar154.lss.proshop.com Name of the host where the StorageScope server
primary network name resides.
(logical name)
StorageScope Server 8080 The StorageScope server listening port number.

port number The default is 8080.
ECC Server hostname l82ar154 Name or IP address of the host where the ECC
or IP address 172.23.172.154 Server resides.
StorageScope license xx-xxx-xxx-xxxx The license key provided with StorageScope.

key
StorageScope 161
Fibre Channel Connectivity Agent

These notes help the administrator install the Fibre Channel Connectivity Agent on host
l82ar154. The administrator also records the IP addresses of the switches in the
environment for use during ControlCenter connectivity discovery.
Table 30 ProShop Fibre Channel Connectivity Agent Installation Notes
Host l82ar154 The name of the host on which you are

installing the agent. Only compatible hosts will
be available. If the agent is already installed
on a host, it will not be available for selection.
IP Address(es) of Switch Name IP Address IP addresses of the Fibre Channel switches

the Switch(es) for which topology and fabric information is to
3800_209 172.23.172.209 be gathered.
Clubmftg_DS16B 172.23.174.170
sb2_16b_2 10.15.64.25
Additional Installation Considerations

Before Installing the Fibre Channel Connectivity Agent, the administrator considers the
following:
◆ By default, ControlCenter uses the default SNMP community string public. To
enable connectivity device discovery for switches and service processors:
• If necessary, changes the ControlCenter community string to match the string for
Brocade and McDATA switches and service processors.
• Uses the Cisco CLI to update Cisco switches to specify the same community
string (for example, one with write privileges such as private.)
◆ The FCC Agent has exclusive access to port 162 (the default), where it listens for
SNMP traps from the devices it manages. If other processes (such as Storage Agent
for NAS or Microsoft SNMP Trap Service) use port 162, they can prevent FCC agent
from receiving traps and subsequently sending ControlCenter alerts.
◆ To discover and monitor connectivity devices, Fibre Channel switches, and fabrics,
the FCC Agent must be active on the Console.
◆ Ensures that SNMP V1 is enabled on all switches.
◆ Ensures that the CNT Enterprise Manager API license key (required to perform a
full discovery, for CNT Enterprise Manager Version 3.2.1 and higher) is enabled.
◆ Fibre Channel connections to switches should use the Source ID (SID) lockdown
feature in SAN Manager to fix ports to specific World Wide Names (WWNs). This
feature creates an association among the SID of a switch port, the HBA attached to
the port, and the WWN of the HBA. SID lockdown prevents a WWN from changing
ports, thus foiling most attempts to spoof. For more information on how to use the
SID lockdown feature through ControlCenter, refer to the Console Online Help.

Symmetrix SDM Agent

These notes provide the information for installing the Symmetrix SDM agent on the
hosts connected to the VCM database on each Symmetrix array to collect LUN masking
information.
Table 31 ProShop Symmetrix SDM Agent Installation Notes
Hostname System Type Physical Location IP Address
l82ar154 Windows 2000 Main Street 172.23.172.154
pswapp01 Windows 2000 Main Street 10.15.64.18

Before installing the Symmetrix SDM Agent, the administrator ensures:
◆ A Fibre Channel connection exists on the target host.
◆ EMC Solutions Enabler is installed on each host through which a Symmetrix VCM
database is to be monitored (usually, the host running the Symmetrix Agent for
SDM).
◆ A connection to a VCM-enabled Symmetrix system is configured on the target host.
◆ A Fibre Channel HBA exists on the target host. EMC strongly recommends an HBA
with the appropriate driver/firmware to support the Storage Networking Industry
Association (SNIA) API (the agent will still communicate and offer SDM capabilities
without an SNIA-qualified HBA). Refer to the EMC ControlCenter 5.2 Support Matrix
for the specific drivers.
After installing the Symmetrix SDM Agent, change the default discovery policy to run
once daily.
Symmetrix SDM Agent 163

Storage Agent for Symmetrix

These notes help the administrator install the Storage Agent for Symmetrix on the hosts
collecting information about their Symmetrix systems.
Table 32 ProShop Storage Agent for Symmetrix Installation Notes
Hostname System Type Physical Location IP Address
l82ar154 Windows 2000 Main Street 172.23.172.154

Before installing the Storage Agent for Symmetrix, the administrator ensures:
◆ The host has Solutions Enabler 5.4.x installed. Solutions Enabler can be remotely
installed through the Console.
◆ The following minimum gatekeeper recommendations are met for each Symmetrix
system connected to a host:
• Two gatekeepers are required when the Storage Agent for Symmetrix is installed
on the host.
• An additional two (total of four) gatekeepers are required if the administrator
intends to use Symmetrix Configure commands to manage the Symmetrix
system.

Storage Agent for CLARiiON

These notes help the administrator install the Storage Agent for CLARiiON. This agent
is supported by Assisted Discovery.
Table 33 ProShop Storage Agent for CLARiiON Installation Notes
FC4700/CX600 To discover the CLARiiON FC4700/CX600 arrays you need to specify the network
name of storage processors (SPs) A and B of the CLARiiON array you want to
discover through the agent.
SP A Hostname 172.23.174.182 The hostname of each of the SP pairs for which this
agent is to gather data.The first field for A and B is
SP B Hostname 172.23.174.183 required.

Before installing the Storage Agent for CLARiiON, the administrator ensures:
◆ To enable metaLUN support, JAVA Runtime Environment (JRE) 1.4.2_01 (required
by NaviCLI) is installed on the target host. If installed on UNIX, the JRE location
must be in the PATH.
◆ The target host has Navisphere CLI software installed and enabled, and the
CLARiiON unit serial numbers are set to Array in Navisphere. If installed on UNIX,
the Navisphere CLI directory must be added to the PATH.
◆ The service processor host has Navisphere Service Processor (SP) Agent and Access
Logix™ software installed and running.
Storage Agent for CLARiiON 165

Storage Agent for NAS

These notes help the administrator install the Storage Agent for NAS on the host
collecting information about their Celerra Network Server(s).
Table 34 ProShop Storage Agent for NAS Installation Notes
Host pswapp01 The name of the host on which to install the agent. Only
compatible hosts will be available. If the agent is already
installed on a host, it will not be available for selection.
IP address 10.15.64.27 The IP address of the NAS container to discover.
Port 8000 The port of the NAS container the agent is monitoring.
The default is 8000 for Celerra Network Servers.
Username nasadmin NAS container login name.
Password ******* NAS container password.
Type Celerra Choose from Celerra or NetApp.

Storage Agent for HDS

These notes help the administrator install the Storage Agent for HDS that is required to
manage the HP XP array. This agent is supported by Assisted Discovery.
ProShop has a network connection between the host and the storage array. If ProShop
had a serial connection, they would need to collect information about the serial port,
baud rate, and parity to enter in the Assisted Discovery fields.
Table 35 ProShop Storage Agent for HDS Installation Notes
Assisted Discovery Requirements (Network Connection)
Server Type csbach IP address or hostname of the ESS Specialist Server.

172.23.172.121
User ID ********** The CommandView user ID (active commands require

administrator access, but discovery requires user-level
access only).
Password ******* The CommandView password.
Command View CLI C:\HPSS\cvcli.bat Command View CLI Path. The path and filename for
Path CommandView command line interface file, on the host
where the Storage Agent for HDS is running. For
example: C:\HPSS\cvcli.bat

Before installing the Storage Agent for HDS, the administrator ensures that:
◆ The host meets the system requirements provided in the EMC ControlCenter Support
Matrix available on the EMC Powerlink website.
◆ CommandView CLI is installed on the target host and can communicate with the
CommandView Server. However, the Storage Agent for HDS should not be on the
same host as the CommandView Server.
◆ The required HP XP licenses are on the CommandView Server. The administrator
will be performing configuration changes using active commands on the array, so
they also need to install the following HP licenses:
• LUN Security Manager XP
• LUN Configuration Manager XP
Storage Agent for HDS 167

Database Agent for Oracle

These notes provide the information for installing the Database Agent for Oracle on
each host. After installing the agent, the administrator used the Assisted Discovery
utility in the Console to identify Oracle databases to ControlCenter.
If there is a host agent installed on the same host as the Database Agent for Oracle, allow
the host agent’s Discovery data collection policy to complete before starting the
Database Agent for Oracle’s data collection policy.
Table 36 provides the information required for the administrator to install the Database
Agent for Oracle on hosts l82ar155, l82ar156, psssun01, and psssun02.
Table 36 ProShop Database Agent for Oracle Installation Notes
Hostname l82ar155 l82ar156 psssun01 psssun02 The name of the host on which to install the
agent.
Database kind Oracle Oracle Oracle Oracle Database type.
Oracle base /erm /oracle/OraHome /oracle/OraHome /oracle/OraHome If Oracle base is an environment variable
specified when the Oracle database was
installed, you must specify the variable here.
ORACLE_BASE is a top-level directory.
Oracle home /erm /oracle/OraHome /oracle/OraHome /oracle/OraHome Oracle home of the Oracle database to be
monitored. The Oracle home directory is
located directly under ORACLE_BASE.
Directory where Oracle is installed. Consult
with your Database Administrator.
Oracle SID sale testsale mainmfg mainplan Oracle instance name of the Oracle database
to be monitored.
Listener port 1521 1521 1521 1521 The listener port number where the Oracle
number Listener is listening for client connections.
Sys user password ****** ****** ****** ****** The password of the Oracle database sys
user.
Oracle Agent oraagent oraagent oraagent oraagent The database user will be used by Database
username Agent for Oracle to connect to the database.
Oracle Agent user oraagent oraagent oraagent oraagent The password of the Oracle agent user.
password

Common Mapping Agent

These notes help the administrator install the Common Mapping Agent to monitor their
SQL Server database.
This agent is supported by Assisted Discovery.
Table 37 ProShop Common Mapping Agent Installation Notes
Host l82at125 The name of the host on which to install the agent.
Only compatible hosts will be available. If the agent is
already installed on a host, it will not be available for
selection.
Hostname #1 l82at124 Hostname of the database to be monitored.
Host IP 172.23.174.125 The IP address of the system where the agent resides.
Host port 2707 (default) The host port number used by the SYMAPI server.
DB instance #1 l82at124 Instance name of the database to be monitored.
Database user #1 sa User's database login name.
Database password #1 ********* User's database password.
Database type #1 SQL Server Type of database to be monitored. Choose from SQL
Server, Sybase, Informix, or DB2 Universal Database.

Before installing the Common Mapping Agent, the administrator ensures that:
◆ The host has Solutions Enabler 5.4.x installed. Solutions Enabler can be remotely
installed through the Console.
◆ The Discovery DCP for the host agent and the Host DCP for the Common Mapping
Agent are not both enabled.
The Common Mapping Agent has a data collection policy (Host DCP) that can
collect some information about the host. This DCP is usually used only when a host
agent is not installed on the host. The data collected by the Host DCP can conflict
with the data being collected by the Discovery DCP running under the host agent,
so both policies cannot be running at the same time.
For example, ProShop’s host l82ar125 has both a Host Agent for Windows and the
Common Mapping Agent on it. The administrator cannot have the Host DCP for the
Common Mapping Agent enabled if the Discovery DCP for the Host Agent for
Windows is running.
Common Mapping Agent 169


ControlCenter Configuration and Control - Manage What You Have 5.2 A05

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ControlCenter Configuration and Control - Manage What You Have 5.2 A05

Uploaded by

Copyright:

Available Formats

Copyright © 2003, 2004, 2005 EMC Corporation. All rights reserved.

Printed June 2005

Part Number 300-000-948

2 ControlCenter Configuration and Control: Manage What You Have

Chapter 1 Configuration and Control Challenges ......................................... 7

Chapter 2 Planning the ControlCenter Implementation .............................. 15

Chapter 3 Installing ControlCenter ............................................................... 29

Chapter 4 Configuring ControlCenter........................................................... 65

Chapter 5 Testing and Validating ControlCenter ......................................... 79

ControlCenter Configuration and Control: Manage What You Have 3

Chapter 6 Configuration and Control Solutions .......................................... 83

Appendix A Installation Notes ........................................................................ 155

4 ControlCenter Configuration and Control: Manage What You Have

6 ControlCenter Configuration and Control: Manage What You Have

Configuration and Control Challenges 7

Business initiatives to meet revenue goal:

8 ControlCenter Configuration and Control: Manage What You Have

Objectives of Storage Management

Objectives of Storage Management 9

ProShop’s Storage Allocation Workflow Challenges

Required Desired type of Port available

**Fan in, I/O,

Configured storage Configure Discover devices

Figure 1 ProShop Storage Allocation Workflow

10 ControlCenter Configuration and Control: Manage What You Have

Challenges of the Current Storage Allocation Process

Figure 2 ProShop’s Method of “Spreadsheet Storage Management”

Challenges of the Current Storage Allocation Process 11

Achieving Storage Allocation Management Objectives With ControlCenter

Figure 3 ControlCenter Configuration and Control Solutions

The benefits of a single interface result in:

12 ControlCenter Configuration and Control: Manage What You Have

14 ControlCenter Configuration and Control: Manage What You Have

Planning the ControlCenter Implementation 15

ControlCenter Planning Overview

Planning Planning the installation of ControlCenter components includes these steps:

Planning Planning the configuration of ControlCenter includes the following steps:

16 ControlCenter Configuration and Control: Manage What You Have

Documenting the Environment

Main Street Data Center

Production LAN 1 "pswexch01" "cawti"

Figure 4 ProShop Network Diagram Showing Equipment Configuration and Types

Documenting the Environment 17

Table 1 ProShop Host Preimplementation Notes

csebacha 172.23.172.121 HP XP Compaq Windows 2000 SP3 ------------------ --------------

l82ar134 172.23.172.134 Financial IBM F80 AIX 4.4.3 10 6227 --------------

l82ar136 172.23.172.136 Financial IBM 6150-F50 AIX 4.4.3 10 6227 --------------

pshpcad1 10.15.64.23 CAD HP HP-UX 11 ------------------- ------------------ --------------

pshpcad2 10.15.64.24 CAD HP HP-UX 11 ------------------- ------------------ --------------

18 ControlCenter Configuration and Control: Manage What You Have

Table 2 ProShop Switch Preimplementation Notes

Switch Switch Type IP Address Firmware Revision

3800_209 Brocade 3800 172.23.172.209 3.0.2m_rc4

Clubmftg_DS16B EMC DS16B 172.23.174.170 2.6.0d

sb2_16b_2 EMC DS16B 10.15.64.25 2.6.0d

Table 3 ProShop Storage Array Preimplementation Notes

Storage Serial Number Storage Type IP Address Array Management Software

WRE00022201023 CLARiiON CX600 172.23.174.182 Navisphere CLI 6.06

30471 HP XP 512 None CommandView 1.8

000182504200 Symmetrix 4.0 None Solutions Enabler 5.4

000187400075 Symmetrix DMX1000 None Solutions Enabler 5.4

psnasCS0 Celerra Network Server 10.15.64.27 NAS OS 4.0

Documenting the Environment 19