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

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

Scenario................................................................................................................... 8 Objectives of Storage Management......................................................................... 9 ProShops 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 16 17 20 21 23 26 27 28

ControlCenter Planning Overview ......................................................................... Documenting the Environment .............................................................................. Verifying That Systems Meet All Prerequisites ...................................................... Listing the Required Software................................................................................ Planning for the ControlCenter Infrastructure ........................................................ Gathering ControlCenter Installation Information................................................... Choosing Logical Groups to Support Storage Allocation ....................................... Managing User Accounts....................................................................................... Chapter 3

Installing ControlCenter ............................................................... 29 30 33 36 43 48 51 52 53 57 60 64

ControlCenter Installation Overview ...................................................................... Creating a Shared Folder for ControlCenter Installation........................................ Installing ControlCenter Components on a Single Host......................................... Installing and Starting the Master Agents on Hosts ............................................... Installing and Starting the Console ........................................................................ Entering License Keys ........................................................................................... Creating User-Defined Groups .............................................................................. Installing Solutions Enabler and ControlCenter Agents ......................................... Validating Agent Installation and Startup ............................................................... Discovering the Storage Network .......................................................................... Validating All Managed Objects Are Discovered.................................................... Chapter 4

Configuring ControlCenter........................................................... 65 66 67 72 73 76 77

Configuration Overview ......................................................................................... Managing User Access to ControlCenter Features ............................................... Populating the User-Defined Groups ..................................................................... Setting Agent Data Collection Policies and Scheduling Reports ........................... Setting Data Retention Policies ............................................................................. Creating Zoning Policies........................................................................................ Chapter 5

Testing and Validating ControlCenter ......................................... 79

Validating Data Collection Policies......................................................................... 80 Validating the Complete Configuration................................................................... 81 Validating StorageScope Reports .......................................................................... 82


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 156 157 159 160 161 162 163 164 165 166 167 168 169

Latency ................................................................................................................ ControlCenter Infrastructure Components........................................................... Master Agent ....................................................................................................... Console................................................................................................................ StorageScope ...................................................................................................... Fibre Channel Connectivity Agent ....................................................................... Symmetrix SDM Agent ........................................................................................ Storage Agent for Symmetrix............................................................................... Storage Agent for CLARiiON ............................................................................... Storage Agent for NAS ........................................................................................ Storage Agent for HDS ........................................................................................ Database Agent for Oracle .................................................................................. Common Mapping Agent .....................................................................................

4


IntroductionThe 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 metfor 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 documentationstarting 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

6


1This 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:

Configuration and Control Challenges

Scenario ............................................................................................................................... 8 Objectives of Storage Management................................................................................. 9 ProShops 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

ScenarioThis 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 ProShops 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)

8



Objectives of Storage ManagementProShop needs to have the new e-commerce application up and running by the beginning of the next business quarter. ProShops 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 ProShops case specifically, these objectives apply to many small, medium, and even large data centers.

Objectives of Storage Management

9


ProShops Storage Allocation Workflow ChallengesProShop has a storage allocation workflow process in place that was implemented in an effort to streamline storage allocation. The challenges outlined earlier have limited ProShops 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 requirements for allocation

Select a storage array

Required storage available on array?*

Yes

Desired type of connection available?

Yes

Port available that meets requirements?**

No

*(Configured/ Unconfigured)

**Fan in, I/O, devices/ channel No No Yes

Select another array

Configured storage available?

Yes

Configure connection

Yes

Discover devices on host

No

Configure storage

Figure 1

ProShop Storage Allocation Workflow

10



Challenges of the Current Storage Allocation ProcessThe 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 ProShops 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 Oracle Database Brocade 3800 Baker Street Public IP Network Symmetrix DMX1000

Win2K Web Server

Win2K Web Server

HP UNIX CAD Celerra SE

Main Street Data Center

HP UNIX CAD IBM AIX Database

Baker Street

Win2K Transaction Engine

CLARiiON CX600 EMC DS16B HP Storage Works

IBM AIX Database

Win2K Win2K/ SQL2K Transaction Engine Win2K/ SQL2K Transaction Engine EMC DS16B Sun Solaris Oracle Database Symmetrix 4.0

Figure 2

ProShops Method of Spreadsheet Storage Management

Challenges of the Current Storage Allocation Process

11


Achieving Storage Allocation Management Objectives With ControlCenterUsing EMC ControlCenters 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. Time saved in collection of standardized and accurate data. A common picture of the environment. Efficient use of assets.

The benefits of data in one location result in:

12



Getting StartedControlCenter provides many powerful features for monitoring and reporting on the storage environment, but this case study focuses on ControlCenters 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


14


2Chapter 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. This chapter contains the following sections:

Planning the 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

Chapter 2, Planning the ControlCenter Implementation

ControlCenter Planning OverviewProShops 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 ProShops storage environment.

Planning ControlCenter Installation

Planning the installation of ControlCenter components includes these steps: Documenting the storage network The administrator documents the storage 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 ControlCenter Configuration

Planning the configuration of ControlCenter includes the following steps: Create logical groups of resources To help assess the impact of issues on the 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.

16



Documenting the EnvironmentControlCenter 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 3800 "182ar155" Sun Solaris Oracle Database Symmetrix DMX1000

"l82ar123" Windows 2000 Web Server

"l82ar134"

Baker Street Data Center

SPA

SPB

CLARiiON CX600

IBM AIX Financial Applications

"pshpcad1" HP UX CAD

"l82ar136" IBM AIX Financial Applications "l82at124" Windows 2000 SQL Server Transaction Engine "l82at125" Windows 2000 SQL Server Transaction Engine


HP XP 512

EMC DS16B

IP

"pshpcad2" HP UX CAD

Celerra

"csebach" Windows 2000 HP XP CommandView Server

"pswapp01" Windows 2000 Transaction Engine "pswapp02" Windows 2000 Transaction Engine EMC DS16B "psssun01" Sun Solaris Oracle Database "psssun02" Symmetrix 4.0

Legend

Sun Solaris Oracle Database Fibre Channel Production LAN 1 Production LAN 2 Public IP Network "pswexch01" Windows 2000 Exchange Server "cawti" Windows 2000 Web Server

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 Hostname cawti csebacha IP Address 168.159.90.60 172.23.172.121 ProShop Host Preimplementation Notes Host Purpose Web Server HP XP CommandView Server Web Server Web Server Transaction Engine Transaction Engine Financial Applications Financial Applications Infrastructure Host Oracle Database Oracle Database CAD CAD Oracle Database Oracle Database Transaction Engine Transaction Engine Exchange Server Server Make and Model Compaq Compaq OS and Version Windows 2000 Windows 2000 Patch Level SP3 SP3 Fibre Channel HBA -----------------------------------HBA Driver ----------------------------

l82ar122 l82ar123 l82at124b l82at125c l82ar134 l82ar136 l82ar154d l82ar155 l82ar156e pshpcad1 pshpcad2 psssun01 psssun02 pswapp01 pswapp02 pswexch01

172.23.172.122 172.23.172.123 172.23.174.124 172.23.174.125 172.23.172.134 172.23.172.136 172.23.172.154 172.23.172.155 172.23.172.156 10.15.64.23 10.15.64.24 10.15.64.21 10.15.64.22 10.15.64.18 10.15.64.19 10.15.64.20

Compaq Compaq Compaq Compaq IBM F80 IBM 6150-F50 Compaq Sun 220R Sun 220R HP HP Sun 220R Sun 220R Dell Dell Dell

Windows 2000 Windows 2000 Windows 2000 Windows 2000 AIX 4.4.3 AIX 4.4.3 Windows 2000 Solaris 8 Solaris 8 HP-UX 11 HP-UX 11 Solaris 8 Solaris 8 Windows 2000 Windows 2000 Windows 2000

SP3 SP3 SP3 SP3 10 10 SP3 108528-17 108528-17 ------------------------------------108528-08 108528-08 SP3 SP3 SP3

----------------------------------Emulex LP8000 Emulex LP8000 6227 6227 Emulex LP8000 Emulex LP8000 Emulex LP8000 ----------------------------------Emulex LP8000 Emulex LP8000 Emulex LP8000 Emulex LP8000 Emulex LP8000

--------------------------2.13 2.13 --------------------------2.13 5.01b 5.01b --------------------------5.01b 5.01b 2.13 2.13 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.

18



Table 2 Switch 3800_209 Clubmftg_DS16B sb2_16b_2

ProShop Switch Preimplementation Notes Switch Type Brocade 3800 EMC DS16B EMC DS16B IP Address 172.23.172.209 172.23.174.170 10.15.64.25 Firmware Revision 3.0.2m_rc4 2.6.0d 2.6.0d

Table 3 Storage Serial Number WRE00022201023

ProShop Storage Array Preimplementation Notes Storage Type CLARiiON CX600 IP Address 172.23.174.182 172.23.174.183 None None None 10.15.64.27 Array Management Software Navisphere CLI 6.06 MetaLUN support JRE 1.4.2 CommandView 1.8 Solutions Enabler 5.4 Solutions Enabler 5.4 NAS OS 4.0

30471 000182504200 000187400075 psnasCS0

HP XP 512 Symmetrix 4.0 Symmetrix DMX1000 Celerra Network Server

Documenting the Environment

19


Verifying That Systems Meet All PrerequisitesThe 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 EnvironmentThe 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 ProShops 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.

20



Listing the Required SoftwareThe 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 ProShops 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 Master Agent Host Agents Storage Agents Purpose Manages all the agents on a host. Monitor and collect statistics about hosts. Monitor and collect data about storage arrays. ProShop Agent Installation Locations One on each host where one or more agents are installed. One on each Windows, Solaris, HP-UX, and AIX host. One storage agent per Symmetrix, CLARiiON, NAS (Celerra), and HP XP array on designated hosts in the environment. One on each host on which Oracle instances reside. One on a selected host in the environment (in ProShops case, SQL Server). One on a selected host in the environment. One on each host where a Storage Agent for Symmetrix is installed.

Database Agent for Oracle Common Mapping Agent

Collects information about and monitors Oracle instances. Collects information about databases other than Oracle. Collects data about the SAN from switches. Enables agents to collect LUN masking information from Volume Configuration Manager (VCM) database on a Symmetrix array.

Fibre Channel Connectivity Agent Symmetrix SDM Agent

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

22



Planning for the ControlCenter InfrastructureEvery 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 ComponentsProShops 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 Symmetrix Resource Logical volumes Front-end mappings CLARiiON NAS Logical devices Logical devices Data Movers Switch Oracle database SQL Server or Sybase MVS LPAR DB2 Agent host Ports Sum of data files and tablespaces Sum of databases, data files, log files, file groups DASD devices Sum of data files and tablespaces Host devices Logical volumes File systems (NTFS, UFS, VXFX) Redundant paths Small 1-800 Up to 1600 1-32 1-150 2 1-16 1-800 1-100 1-600 1-800 1-16 1-16 1-16 1-2 Medium 801-2000 Up to 4000 33-256 151-500 4 17-64 801-1600 101-200 601-1500 801-1600 17-128 17-64 17-64 3-4 Large 2001-8192 Up to 16000 257-1024 501-1200 10 65-256 1601-2048 201-400 1501-3000 1601-2048 129-512 65-128 65-128 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 Installation Size Configuration Type # CPUs Min. Speed Min. Memory Disk Space Software ComponentsMax. # Supported Medium-Managed Objects

Storage Arrays

# Hosts

# Oracle DBs

# Switches or (Ports)

Configuration #1: 2 GB RAM HostSmall Single-Host 2 1.0 GHz 2 GB 36 GB ECC Server, Store, & Repository StorageScope Master/Host Agents WLA Archiver FCC Agent Common Mapping Agent 5 30 10 8 (256) 16 (512) 24 (512)

Small Small

Single-Host Single-Host

2 2

2.4 GHz 3.0 GHz

2 GB 2 GB

36 GB 36 GB

10 12

75 90

20 25

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

24



Deciding Where to Install ConsolesIn 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 Systema Windows Solarisb Number of Processors 1 1 Minimum Speed 500 MHz 360 MHz Minimum Memory 512 MB 512 MB Disk Space with Console Logging 550 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 InformationThe 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 ECC Server Repository Store StorageScope Solutions Enabler"l82ar154" Windows 2000

Agents: Master Host

"l82ar122" Windows 2000 Web Server "l82ar123" Windows 2000 Web Server

"182ar155" Sun Solaris Oracle Database

Agents: Master Host Oracle Brocade 3800 Symmetrix DMX1000

Agents: Master Host

Agents: Master Host FCC Symmetrix SDM

"182ar156" Sun Solaris Oracle Database

Agents: Master Host Oracle

Baker Street Data Center

SPA

SPB

Agents: Master Host

CLARiiON CX600 Agents: Master Host HP XP EMC DS16B

"l82ar134" IBM AIX Financial Applications

"pshpcad1" HP-UX CAD

Agents: Master Host

"l82ar136" IBM AIX Financial Applications


IP

"pshpcad2" HP-UX CAD

"l82at124" Windows 2000 SQL Server Transaction Engine Solutions Enabler Navisphere CLI Agents: Master Host CLARiiON Agents: Master Host HDS Mapping Solutions Enabler CommandView CLI "l82at125" Windows 2000 SQL Server Transaction Engine

Agents: Master Host

Celerra

"pswapp01" Windows 2000 Transaction Engine "pswapp02"

"csebach" Windows 2000 HP XP CommandView Server

Agents: Master Host SDM Symmetrix Solutions Enabler

Agents: Master Host Windows 2000 NAS Transaction SDM Engine Symmetrix Solutions Enabler "psssun01" Sun Solaris Oracle Database "psssun02" Sun Solaris Agents: Master Host Oracle

EMC DS16B

Symmetrix 4.0

Legend

Fibre Channel Production LAN 1 Production LAN 2 Public IP Network

Oracle Database "pswexch01" Windows 2000 Exchange Server

Agents: Master Host Oracle

Agents: Master Host

"cawti" Agents: Master Host Windows 2000 Web Server

Figure 5

ControlCenter Infrastructure and Agent Locations in the ProShop Environment

26



Choosing Logical Groups to Support Storage AllocationBefore implementing a ControlCenter solution, a key task is deciding how to group ProShops 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 ProShops objectives.Table 8 Groups Management ProShops User-Defined Groups Subgroups e-commerce Application Purpose Contains the hosts, database, and switch ports that are part of Manufacturings critical e-commerce application, which is also a major storage consumer. The group allows management to monitor configuration changes. Contain the assets (hosts, databases, file systems, switch ports, and storage 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. Allow the IT staff to track the systems for which they are responsible. Administrators can even include file systems or database instances that reside on the same server in different logical groups.

Manufacturing Sales

UNIX Admin Windows Admin DBA

Databases Hosts File Systems Switch Ports Storage Devices Databases Hosts Fibre Channel Switches Storage Arrays Databases Hosts Fibre Channel Switch Storage Array

Baker Street Datacenter Main Street Datacenter

Allow management and the IT staff to track the physical location of IT assets.

Main Street_3800

Identify the new Symmetrix DMX storage array that has just been installed and that will be used with the new e-commerce application.

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 AccountsAccess to ControlCenter features is provided through a system of rules and permissions. Users can be placed into groups that limit their access to specific userdefined 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. ProShops 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. ProShops 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. ProShops 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.

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

28


3In 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. This chapter contains the following sections:

Installing ControlCenter

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

Chapter 3, Installing ControlCenter

ControlCenter Installation OverviewProShop 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 Prerequisites

Before beginning installation, make sure the following prerequisites are met: Completed the applicable installation notes. Verified that the sites 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.

30



Installation Checklist OverviewThe 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 Hostname

ProShop ControlCenter Agent Installation Solutions Enabler Required? IP Address Host OS Database Agent for Oracle Common Mapping Agent Storage Agent Master Agent

cawti csebach l82ar122 l82ar123 l82at124 l82at125 l82ar134 l82ar136 l82ar154 l82ar155 pshpcad1 pshpcad2 psssun01 psssun02 pswapp01 pswapp02 pswexch01

168.159.90.60 172.23.172.21 172.23.172.122 172.23.172.123 172.23.174.124 172.23.174.125 172.23.172.134 172.23.172.136 172.23.172.154 172.23.172.155 10.15.64.23 10.15.64.24 10.15.64.21 10.15.64.22 10.15.64.18 10.15.64.19 10.15.64.20

Windows 2000 Windows 2000 Windows 2000 Windows 2000 Windows 2000 Windows 2000 AIX 4.4.3 AIX 4.4.3 Windows 2000 Solaris 8 HP-UX 11 HP-UX 11 Solaris 8 Solaris 8 Windows 2000 Windows 2000 Windows 2000

c c,d c a b

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

32


SDM Agent

Host Agent

FCC Agent


Creating a Shared Folder for ControlCenter InstallationControlCenter components can be installed either locally from the installation CDs or from a shared drive. ProShops 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 FolderThe 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 ToolsThe 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 hosts CD-ROM drive. If autorun is enabled, the Installation utility launches automatically. If autorun is not enabled, the administrator launches :\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.34 ControlCenter Configuration and Control: Manage What You Have


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 HostProShop 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 AccountA 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: 1. Logs in to the host as a user that is part of the local administrators group. 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: Description: Password: Confirm 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 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.

36



Mapping to the Shared DriveThe 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 ToolsThe 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: 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. Double-clicks ECC.exe in the ECC_VirtualCD folder on the mapped drive. 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.

Installing ControlCenter Components on a Single Host

37


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

38



Installing the ControlCenter InfrastructureThe 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 its not already displayed, on the infrastructure host. The installation wizard displays the following options: 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 Company Name Enable ECC Repository Access via a Firewall. (Default is No) SMTP Mail Server Name

H:\eccbackupProShop No

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.


39


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 Enable LDAP User Authorization? 5799 (default) 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.

40



Once the Solutions Enabler remote install package is created, the wizard prompts to install more products on the host. 3. Clicks Yes to continue installing components. 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. 3. Clicks Yes to continue installing components. The administrator now installs a Master Agent on this host.

Installing the Master Agent on the Infrastructure HostThe 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. Once the installation completes, the wizard prompts to install more products on the host. 5. Clicks Yes to continue installing components. The next step is to install StorageScope.


41


Installing StorageScope on the Infrastructure HostStorageScope 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 StorageScope Key 8080 (Default) The StorageScope key provided with ControlCenter.

4. Clicks Next to begin the installation. Once the installation completes, the wizard prompts to install more products on the host. 5. Clicks No to finish installing components. 6. Clicks Exit to close the wizard.

Rebooting the Host after Installing the InfrastructureThe 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.

42



Installing and Starting the Master Agents on HostsThe 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 hosts 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 DirectoryBefore 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. The installation prerequisites appear. 5. Verifies that the installation prerequisites are met and clicks Next. 6. Clicks Accept to agree to the licensing terms. A dialog box appears asking the administrator to ensure that any antivirus software running on the host is disabled before continuing.

Installing and Starting the Master Agents on Hosts

43


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 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.Table 15 ProShop Repository Installation Notes Repository Hostname Repository Port Number l82ar154 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.Table 16 ProShop Master Agent Installation Notes 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: 1. Clicks the Windows Start button and selects Settings, Control Panel. The Control Panel window appears. 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.

44



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: 1. Clicks the Windows Start button and selects Settings, Control Panel. The Control Panel window appears. 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 HostsThe 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 co

ControlCenter Configuration and Control - Manage What You Have 5.2 A05

Documents

Transcript of ControlCenter Configuration and Control - Manage What You Have 5.2 A05