installing emc controlcenter on a windows 2008 … · as a second store server and will also run...

INSTALLING EMC CONTROLCENTER ON A WINDOWS 2008 CLUSTER

Kevin AtkinLead Storage Engineer Operational Readiness Thomas Reuters

2014 EMC Proven Professional Knowledge Sharing 2

Table of Contents

1 Introduction ................................................................................................................. 4

1.1 Management Summary ....................................................................................... 4 1.2 Assumptions ........................................................................................................ 4

2 Section 1: Pre-Requisites and Access Requirements .............................................. 5

2.1 ECC User Accounts ............................................................................................. 5

3 Section 2: ECC Hardware and Software Requirements ............................................ 6

3.1 ECC Server Hardware Requirements .................................................................. 6 3.2 Install Windows 2008 SP2 Enterprise Edition ...................................................... 7 3.3 Install Windows 2008 SP2 Standard Edition ........................................................ 7 3.4 Create the Shared Storage on VMAX Array ......................................................... 7 3.5 Domain Controllers .............................................................................................. 8 3.6 Join the ECC servers to the Domain .................................................................... 8 3.7 Windows User Accounts ...................................................................................... 8 3.8 Create the Global ECC Administrators Group ...................................................... 9 3.9 Create the Cluster Admin Account ....................................................................... 9 3.10 Create the Windows 2008 Cluster ..................................................................... 10 3.11 Service LAN NIC Configuration .......................................................................... 13 3.12 Disable Unused NICs ........................................................................................ 14 3.13 Advanced Network Configuration ....................................................................... 15 3.14 Enable Required Services ................................................................................. 16 3.15 Enable Feature Failover-Clustering ................................................................... 16 3.16 Create the Cluster.............................................................................................. 16 3.17 Add the SAN Disks to the Cluster ...................................................................... 17 3.18 Configure the Quorum Disk ............................................................................... 19 3.19 Create the ECCRG Resource Group ................................................................. 21

4 Section 4: EMC ControlCenter (ECC) Installation ................................................... 29

4.1 Install Java on all Servers .................................................................................. 29 4.2 Prepare hosts for ControlCenter installation....................................................... 29 4.3 Install ControlCenter onto the First Cluster Node ............................................... 30 4.4 Prepare hosts for Storage Scope Repository installation ................................... 33 4.5 Install Store on xxxx.emccc03 ........................................................................... 35 4.6 Install the ControlCenter 6.1 Console ................................................................ 36 4.7 Solutions Enabler 7.5 ......................................................................................... 37 4.8 Backup and Restore Utility (4938 and 4990) ...................................................... 38 4.9 Oracle OCPU Patch 5011 ................................................................................. 39 4.10 Pre-update Bundle 14 Preparation .................................................................... 39 4.11 Update Bundle 14 (Patch 5013) ......................................................................... 39 4.12 Update Bundle 14 (Patch 5013) on Nodes (emccc02/03) .................................. 41 4.13 Add local ORA_DBA Group to each Cluster Node ............................................. 41 4.14 Edit ecc_server.ini File ....................................................................................... 41 4.15 Edit the Master Agent file ctg.ini ......................................................................... 42 4.16 Edit the ecc_store.ini file .................................................................................... 42 4.17 Upgrade the Console to 6.1.0.14.383 ................................................................ 42 4.18 Create the ECCRG Resources .......................................................................... 43 4.19 Post UB14 and OCPU Cluster Preparation ........................................................ 48 4.20 Install Agents ..................................................................................................... 49 4.21 Master Agent Configuration on the Cluster Nodes ............................................. 49 4.22 Install Control Center Licences .......................................................................... 49 4.23 Agent Patching .................................................................................................. 50 4.24 Add Gatekeepers to EMCCC02 and EMCCC03 Servers ................................... 51


4.25 Install Unisphere for VMAX on xxxx-EMCCC03 ................................................. 51 4.26 Install CLARiiON Agent and Naviseccli .............................................................. 51 4.27 Install UnisphereClient ....................................................................................... 51 4.28 Install the NAS Agent ......................................................................................... 51 4.29 Install the Integration Gateway Agent ................................................................ 52 4.30 Install the Master Agent on xxxx.emccc04/05. ................................................... 53 4.31 Disable ControlCenter status traps .................................................................... 53 4.32 Install the FCC Agent on xxxx.emccc04/05 ........................................................ 54 4.33 Discover Fabric on ECC console ....................................................................... 54 4.34 Enable ControlCenter Fabric Validation ............................................................. 56 4.35 Enable Alert Retention Policy ............................................................................ 57 4.36 References ........................................................................................................ 58 4.37 Glossary ............................................................................................................ 58

Disclaimer: The views, processes, or methodologies published in this article are those of the

author. They do not necessarily reflect EMC Corporation’s views, processes, or

methodologies.


1 Introduction

1.1 Management Summary

This article is an installation and configuration guide for new installations of EMC

ControlCenter® (ECC). It can also be used as a reference point when upgrading an existing

ECC instance.

This installation guide is divided into multiple sections:

Section 1 covers pre-requisites and access requirements.

Section 2 covers the hardware and software required to install ECC.

Section 3 covers the ECC configuration steps.

1.2 Assumptions

The reader is qualified to use EMC Management tools and/or Solutions Enabler CLI

The versions of ControlCenter patches that are referenced in this document were

correct in January 2013, so always check on EMC Powerlink for subsequent

updates. Either way, the methods described will be equally valid on newer patches,

as long as the accompanying readme is adhered to.


2 Section 1: Pre-Requisites and Access Requirements

2.1 ECC User Accounts

Once ECC has been configured as outlined in this document, all users of ECC will need to

have an Active Directory (AD) account created in the same Domain that ECC is a member.

AD users should then be added into the ECC Users folder and then moved into the ECC

Administrators folder as shown here:


3 Section 2: ECC Hardware and Software Requirements

The following sections outline the hardware requirements, LAN requirements and, the build

procedures for the Windows cluster and the installation of the ECC software and associated

patches.

3.1 ECC Server Hardware Requirements

The ECC Server hardware will be comprised of 6 x HPDL460 (or equivalent) Blade or physical servers.

All servers that participate in ECC will be built on Windows 2008 SP2 (note do not use R2 edition) from the SPT server. The HPDL460 Blade Servers will require Windows 2008 SP2 Enterprise Edition for the purposes of clustering; the remaining servers will be installed on Windows 2008 SP2 Standard Edition. Also, ensure that all the servers have the latest version of Firmware, Microsoft hoftfix, Store Port, and HBA drivers.

ControlCenter Infrastructure will be installed as a 2 Node Cluster (Active / Passive) in a distributed configuration. Install one of the two nodes of the cluster in two different HP chassis. The third Server will be used for Storage Scope, Performance Manager, Console, Symmetrix®, Gateway Agent, and WLA reporting. The fourth Server will act as a second Store Server and will also run EMC Unisphere® for VMAX® software. The remaining two servers will become Active Directory servers and will also host the FCC agents.

A reliable Windows Domain infrastructure and a Cluster Service Account that exists in the domain.

Three network LAN connections in each clustered server (emccc01a/1b), one to connect to the Service LAN, the remaining two connections for the Cluster Private LAN. The following IP addresses need to be made available to support all required resources:

1 x Server IP address per node 2 x Cluster Private IP addresses per Node (with separate VLAN for Each) 1 x Cluster IP address per cluster (Virtual) 1 x Virtual IP address for the ECCRG Cluster Resource Group

Remaining servers need one IP address each

Shared SAN storage that the clustered servers have access to which will be comprised of 1x 136GB Thin LUN and a 500MB Thin Quorum disk.

Shared and Non shared 136GB Thin LUNs will be assigned as follows:

1 x 136 GB Thin LUN assigned to the Cluster servers for Repository and the ControlCenter Server. This will be assigned the drive letter R and labeled SharedR.

1 x 136 GB Thin LUN assigned to the Storage Scope Repository on the third HPDL460 (*-emccc02) server. This will be assigned the drive letter S and labeled StorageScope.

1x 136 GB Thin LUN assigned to the Storage Scope Repository for Work Load Analyzer file storage. This will be assigned the drive letter T and labeled WLArchive. This is summarized in Table 1.


Q: SharedQ

Quorum (XXXX- EMCCC01)

R: SharedR

ECC Repository and Server (XXXX- EMCCC01)

S: StorageScope

Storage Scope Repository (XXXX- EMCCC02)

T: WLArchive WLA Archives (XXXX- EMCCC02)

Table 1

3.2 Install Windows 2008 SP2 Enterprise Edition

Install Windows 2008 SP2 Enterprise edition on the 2 ECC cluster nodes, namely:

site-emccc01a and site-emccc01b.

Apply the latest supported Emulex Storeport drivers to the HBA cards and install OneCommand management utility software.

Install Powerpath version EMCPower.X64.signed.5.5.SP1.b512 on both cluster nodes.

3.3 Install Windows 2008 SP2 Standard Edition

Install Windows 2008 SP2 Standard Edition on the remaining servers, namely: site-emccc02 site-emccc03 site-emccc04 site-emccc05 Apply the latest supported Emulex Storeport drivers to the HBA cards and install OneCommand management utility software on servers emccc02 and emccc03.

Install Powerpath version EMCPower.X64.signed.5.5.SP1.b512 on servers emccc02 and emccc03.

3.4 Create the Shared Storage on VMAX Array

Create an Initiator Group for each of the three servers that are to be accessing a SAN device, namely the two cluster nodes and the StorageScope servers: emccc01a, emccc01b, and emccc02.

Create a storage group for each of the servers and assign a TDEV of 136GB and 500MB to the cluster storage groups and a TDEV of 136GB to the StorageScope (emccc02) storage group. Assign the Storage Groups to a FAST policy.

Create a Masking View for EMCCC01A and EMCCC02 only at this point. Do not create a Masking view for EMCCC01B until after the cluster has been created.


Configuration Steps – Active Directory

This section describes how to create the Active Directory where two of the ECC servers will

become Domain Controllers and the remainder of the ECC servers will join as member

servers. The cluster build is also discussed.

3.5 Domain Controllers

There will be two active directory domain controllers acting as backup to each other. They will be hosted by two of the ECC management servers, specifically emccc04 and emccc05 respectively.

3.6 Join the ECC servers to the Domain

Join the remaining servers to the Domain that was created in Sect 2.5 using the Domain account that was created during the AD creation.

3.7 Windows User Accounts

Create the Windows user accounts that are to manage ECC in the OPS Organisational Unit as shown below:


3.8 Create the Global ECC Administrators Group

Create a Domain Global Group named ECC_Administrators as shown below:

Add all the users that need to manage ECC into the ECC_Administrators group, then add the ECC_Administrators Global Group to the local Administrators Group on all of the ECC servers. This will give admin rights to all ECC users on each server.

3.9 Create the Cluster Admin Account

Create a domain user account in the AD and name it sclusteradmin. Place this account in the Accounts Organisational Unit as shown below.

Add this account to the local Administrators group on each cluster node.

Run the following command substituting the domain name that is applicable:

C:\>net localgroup administrators sanmgmtocmq\sclusteradmin /ADD


3.10 Create the Windows 2008 Cluster

Network connections that are to be used for Cluster Private Communications need to be renamed to:

Cluster Private LAN #1

Cluster Private LAN #2

Each of the Cluster Private LAN Connections must then be configured as below:

Open the Properties for each of the NICs:

Verify the Bindings are as follows:


Only “Internet Protocol (TCP/IP)” should be selected.

Note: depending on your server hardware, you may not have the “HP Network Configuration Utility ” element shown.

Select “Internet Protocol (TCP/IP)” and click the Properties button.

Ensure there is no Default Gateway specified.

Ensure there are no DNS Servers specified.

Click the Advanced… button, and choose the DNS tab.


Verify that the entry “DNS suffix for this connection:” is blank.

Ensure that the “Register this connection’s addresses in DNS” is NOT selected.

Select the WINS tab.


Ensure there are NO WINS servers listed.

Select “Disable NetBIOS over TCP/IP”.

Click OK, and click OK again.

Repeat this process for all NICs that are to be used for Cluster Private LAN connections.

3.11 Service LAN NIC Configuration

Rename the network connection to be used for Service LAN Communications to:

Service LAN

The Service LAN Connections must then be configured as below:

Open the Properties for each of the NICs:

Verify the Bindings are as follows:

Note: depending on your server hardware, you may not have the “HP Network Configuration Utility ” element shown.

Select “Internet Protocol (TCP/IP)” and click the Properties button.

Click the Advanced… button, and choose the DNS tab.


Verify that the “DNS suffix for this connection:” entry is correct.

Ensure that the “Register this connection’s addresses in DNS” is selected. Select the WINS tab. Verify that your WINS servers (if used) are correct.

Ensure that “Enable NetBIOS over TCP/IP” is selected.

Click OK, and click OK again. Repeat this process for all NICs that are to be used for Service LAN connections.

3.12 Disable Unused NICs


3.13 Advanced Network Configuration

In the Network Connections window, select the menu option Advanced and choose

Advanced Settings…

Ensure the network connections are listed in the Connections: list in the following order:

If you have more than one Service LAN connection, these should be highest in the list. Your

Cluster Private LAN connections should be next in the list. The [Remote Access

connections] should be last in the list.


3.14 Enable Required Services

Run the following commands in a CMD.EXE command prompt window:

SC CONFIG RemoteRegistry START= AUTO

SC CONFIG LanmanServer START= AUTO

SC CONFIG Browser START= AUTO

SC CONFIG ClusSvc START= AUTO

3.15 Enable Feature Failover-Clustering

Run the following commands on both nodes in a CMD.EXE command prompt window:

servermanagercmd -install Failover-Clustering

3.16 Create the Cluster

To create the cluster, you will need to supply the cluster name and its virtual IP address and

sub net mask. The cluster should be named as follows:

“SANMGMT<SITE><FUNCTION>”

Where SITE is the 3 letter abbreviation of the site and FUNCTION is either Prod (P) ,

NonProd (S), or Development (Q)

There will likely be an error when the cluster is first created. The following example shows

how to clear this:

C:\>cluster /cluster:SANMGMTOCMQ /create /nodes:"ocmq-emccc01a ocmq-emccc01b" /ipaddress:172.29.37.98/255.255.255.192 4% Initializing Cluster SANMGMTOCMQ. 9% Validating cluster state on node ocmq-emccc01a. This phase has failed for Cluster object 'ocmq-emccc01a' with an error status of 5065 (0x000013C9).


This phase has failed for Cluster object 'ocmq-emccc01a' with an error status of 5065 (0x000013C9). System error 5065 has occurred (0x000013c9). The cluster node is already a member of the cluster. From the above we can see that a failure has occurred. To resolve the issue, run the

forcecleanup command as follows:

C:\>cluster node ocmq-emccc01a /forcecleanup Attempting to clean up node 'ocmq-emccc01a' ... Clean up successfully completed. Repeat for the other cluster node. C:\>cluster node ocmq-emccc01b /forcecleanup Attempting to clean up node 'ocmq-emccc01b' ... Clean up successfully completed. Now, run the cluster create again: C:\>cluster /cluster:SANMGMTOCMQ /create /nodes:"ocmq-emccc01a ocmq-emccc01b" /ipaddress:172.29.37.99/255.255.255.192 4% Initializing Cluster SANMGMTOCMQ. 9% Validating cluster state on node ocmq-emccc01a. 13% Searching the domain for computer object SANMGMTOCMQ 18% Creating a new computer object for SANMGMTOCMQ in the domain 22% Configuring computer object SANMGMTOCMQ as cluster name object 27% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node ocmq-emccc01a.. 81% Creating Network Name resource 'SANMGMTOCMQ'. 86% Searching the domain for computer object SANMGMTOCMQ 90% Verifying computer object SANMGMTOCMQ in the domain 95% Configuring computer object SANMGMTOCMQ as cluster name object 100% Bringing resource group 'Cluster Group' online. Now that the cluster has created successfully, start creating the ECCRG resource.

3.17 Add the SAN Disks to the Cluster

Open the Failover Cluster Management tool which will display the recently created nodes.

Right click on Storage and select Add a disk.

Since you will not be able to add any storage to begin with if both nodes are showing, select

the emccc01b node and evict it from the cluster.


Add both disks that are presented. Click OK.


3.18 Configure the Quorum Disk

Right click on the cluster and select More Actions…Configure Cluster Quorum Settings….

Select Node and Disk Majority.

Ignore the warning that this is not recommended for the current number of nodes, as the

second node is yet to be added to the cluster.


Now create the Masking View on the VMAX for the second node and then add the node to

the cluster by selecting Nodes....Add Node...


3.19 Create the ECCRG Resource Group

Right click on the cluster and select More Actions....Create Empty Service or Application

Rename the new service or application to ECCRG


Click on Storage and Select the R drive Select More Actions..... Move this resource to another service or application


Select ECCRG and click OK

Right click on the ECCRG resource and select Add a resource Select Client Access Point


In the Address field, enter the Virtual IP of the ECC server.


Wait for the resource to complete, then bring it online.

Select the Properties page of the IP Address resource and rename the Resource Name to

xxxx-emccc01 (as shown in the example below) and add this name into DNS as an A

record. This name will then be used in the ECC Console when connecting to the ECC

Repository.


Next, click on Storage and select Cluster Disk 2 (the R drive) Then select More Actions....Move this resource to another service or application


Select ECCRG and click OK.


The ECCRG Summary page is shown here.

This completes the installation of the Windows cluster and the service application ECCRG

setup. The installation of ControlCenter can now take place.


4 Section 4: ControlCenter (ECC) Installation

This section concentrates on the initial setup of ECC and the associated patching

requirements.

4.1 Install Java on all Servers

Install Java jre-6u2-windows-i586-p.exe on each server. Run the executable and accept

the defaults.

4.2 Prepare hosts for ControlCenter installation

Ensure the following for hosts where infrastructure components (ECC Server,

Repository, and Store) are to reside:

The fully-qualified domain names (FQDNs) and hostnames do not contain

underscores.

No applications are currently running (to prevent interference with the installation

process, close any Windows Explorer windows and active command prompts).

Terminal Services is not disabled.

Disable Anti-Virus Software.

Stop and disable the DTC Service (Distributed Transaction Coordinator). This should

not be re enabled after ECC is installed.

Stop all HP Services and set to manual.

PowerPath® version 5.5 installs EMC PowerPath RSA Encryption Service 5.5.0. This

should be disabled during the ECC install.

Stop and disable COM+ servers. Note that the Cluster Service will fail to start if the

server is rebooted with COM+ disabled.

If Cisco Device Manager is installed, stop and set to Manual PostgreSQL service.

The ControlCenter Repository upgrade executable requires the use of two DLL’s;

libeay32.dll and ssleay32.dll. Other applications may also use these DLL’s which can

conflict with ControlCenter upgrade.

Make sure Cluster services is running and all resources are running on Node A.


4.3 Install ControlCenter onto the First Cluster Node

Download the latest A05 ECC 6.1 ISO images and patches from the EMC Powerlink

website. The most convenient way to install or upgrade ECC is to first copy all the ISO

images and patches to a shared network drive as shown below under the ECC Disks folder:

Once all the pre-requisites discussed in this and the EMC documentation have been fulfilled,

the installation of ECC is ready to proceed. Make sure that in the case of an upgrade that the

current ECC folder is backed up as per EMC documentation!

PAUSE the second node of the cluster by right-clicking on xxx-emccc01b and selecting

Pause Node.

On the first node of the cluster run setup.exe (as shown in the above screenshot) from the

shared location. You will see the Primary Network Name appear automatically if DNS is set

up correctly.


Select Next.

If prompted for a Secondary Network, Select None.


Change the installation path to R:\ECC and click Next.

Select Install When prompted to enable LDAP authentication: Select No to LDAP Authentication.

Follow the prompts to complete the install.

Be aware that as COM+ is currently disabled, it should be re-enabled so that the cluster

service is able to start up again.

Select

Yes I want to Restart my Computer now — then select Finish. This completes the initial (pre-patching) part of the upgrade of the Repository. When the Server has rebooted, check that the Cluster Service is running (the B Node should

still be Paused) so that the cluster R drive is made available.

Check that all EMC ControlCenter Services are able to Start. They will be set to Manual at

this point.


4.4 Prepare hosts for Storage Scope Repository installation

As in the installation of ECC on the cluster node, follow the same procedure on the STS

node prior to running the setup.exe program. Select the S drive as the install destination.

Run Setup.exe Select Network.

Select: Specify Existing ControlCenter Repository.


Enter ControlCenter Repository server name.

Select Storage Scope.

.

Type Use Name and Password for Storage Scope (eccadmin and default Password). Select Install EMC supplied Oracle Database. Select Yes, to the question, “Do you want to Install a Store?”

Select install

Performance Manager.

StorageScope

Un select ECCAPI


You will be prompted for a Storage Scope licence key. Enter License and Click install.

4.5 Install Store on xxxx.emccc03

Run Setup .exe on the fourth server, emccc03. Before running setup.exe file, follow the same steps followed for Control Centre install on Node A. Install Store.

From the Infrastructure Server (Node A), run ecc_getversion found on the R drive and ensure the correct version displays as follows:

R:\ECC\Repository\admin\Ramb_scripts>ecc_getversion.bat ECC_INSTALL_ROOT environment variable found is ==> R:\ECC return code = 0

ECC Repository Version -------------------------------------------------------------- ECC Repository version information

External Version : Version 6.1.0 Internal Version : 6.1.0.4.71 KitSpec : GA6 Build Label : ECC61040.16MAY2009.1146.224 Build Name : ECC61040.16MAY2009.1146.224 Release Date : Sat May 16 14:34:00 2009 Install Date : Thu Sep 24 10:59:16 2009


Run the emcsts_getversion.bat found on the S drive on the StorageScope server

and check the result is displayed as below:

S:\ECC\Repository\admin\emcsts_scripts>emcsts_getversion.bat

Value of userName got as input: sys

Initializing Lockbox in:S:\ECC\lockbox\WEB.lb

Value of UserName passed to SQL: sys

Success!

EMCSTS is open

Get Schema Version from Single-Site StorageScope Repository Database . . .

Value of userName got as input: emcsts

Initializing Lockbox in:S:\ECC\lockbox\WEB.lb

Value of UserName passed to SQL: emcsts

Success!

If the above commands do not return the correct version, DO NOT apply the

Update Bundle. Contact EMC for support.

Open the Services applet on Node A and verify that the Oracle database services have

started.

Make sure the following services are running (if not, start them)

EMC ControlCenter Key Management Server

EMC ControlCenter Repository

EMC ControlCenter Server

EMC ControlCenter Store

EMC ControlCenter Web Server

EMC ControlCenter API Server

EMC StorageScope Server

4.6 Install the ControlCenter 6.1 Console

Once ControlCenter has upgraded to version 6.1, install a Console. This is so that the

Master Agent can be upgraded as detailed in section 2.8 of this document. Install a Console

on all the ECC servers except for the cluster and Active Directory servers.

Open a browser and connect to the cluster node name. For example:

https://xxxx-emccc01:30002/webinstall

Install the Console 6.1.0 from the on-screen menu. When the Console has installed, enter the Cluster name in the Server Host Name as shown

here. Note that the Console shown here is a UB12 patched version.

https://xxxx-emccc01:30002/webinstall


Log into the ControlCenter Console. Use a Domain account that has previously been added to the ECC Users in ControlCenter. If

this were a new install, the only account available would be the local eccadmin account.

Make sure you are able to log in to ControlCenter. Now, close the Console window and proceed to the next steps.

4.7 Solutions Enabler 7.5

There are two variants of the Solutions Enabler software; 32-bit and 64-bit. It is important

that the correct one is installed on the correct server.

To ensure that the Symm Agent is able to start, install se7500-WINDOWS-x86.exe on the

EMCCC02 server. Follow the on-screen prompts and be prepared to stop any EMC services

in the Task Manager, if promted.

Install se7500-WINDOWS-x64.exe on the EMCCC03 server. This is to enable the correct

operation of the element manager, Unisphere for VMAX. Follow the on-screen prompts and

be prepared to stop any EMC services in the Task Manager, if prompted.


4.8 Backup and Restore Utility (4938 and 4990)

Before running either of these patches, check for the existence of the registry string

MA_ROOT on each of the above hosts found in:

HKEY_LOCAL_MACHINE\SOFTWARE\EMC CONTROL CENTER\6.1 This string contains the value used to specify the ControlCenter installation path of the

Master Agent. If the key is not present, add it.

Consult the Patch readme documentation. Take careful note of the following steps.

If the instance of ECC is already at patch UB12, install CC_4990 on all of the Infrastructure

servers. On the other hand, if the ECC instance is at patch level UB4 (native install), install

CC_4938.

Install the relevant backup utility—either CC_4938 or CC_4990—on all of the infrastructure

servers.

Run the backup.bat script that will be installed into either R:\ECC\HF4938 or

R:\ECC\HF4938 on the emccc01a server and S:\ECC\HF4938 on the emccc02 server.

Run the clustersave.bat file located in R:\ECC\Tools\Utils folder.

Reboot the server.

After rebooting, make a copy of the ECC folder to another location on all three servers. Example: R:\ECC copy to D:\Rollback-Pre-OCPU S:\ECC copy to D:\Rollback-Pre-OCPU


4.9 Oracle OCPU Patch 5011

Do NOT apply this OCPU on a UB14 instance of ControlCenter. This patch is for Oracle

10g whereas UB14 is an Oracle 11g install. Only apply 5011 whilst still at or below UB12

patch, as CC_4990 will not work with UB14.

This is an Oracle OCPU patch. Always check the EMC Powerlink site for the latest

version of this file as it is updated every quarter.

Fully read and understand the readme document that applies to a clustered environment

before applying this patch.

In addition to the Services listed by EMC that should be stopped and disabled, also stop

and disable all Tivoli instances. If you do not do this, the install will fail causing you to

rollback and start over.

Note this patch is installed using only one batch file, Postreboot.bat.

After the patch has successfully installed, restart all ECC services.

4.10 Pre-update Bundle 14 Preparation

Take careful note of the following steps.

If the instance of ECC is already at patch UB12, install CC_4990 on all of the Infrastructure

servers. On the other hand, if the ECC instance is at patch level UB4 (native install), install

CC_4938.

Install the relevant backup utility—either CC_4938 or CC_4990—on all of the Infrastructure

servers.

Run the backup.bat script that will be installed into either R:\ECC\HF4938 or

R:\ECC\HF4938 on the emccc01a server and S:\ECC\HF4938 on the emccc02 server.

Run the clustersave.bat file located in R:\ECC\Tools\Utils folder.

Pause the B node.

Reboot the A node.

After rebooting, make a copy of the ECC folder to another location on all three servers. Example: R:\ECC copy to D:\Rollback-Pre-UB14 S:\ECC copy to D:\Rollback-Pre-UB14 T:\ECC copy to D:\Rollback-Pre-UB14

4.11 Update Bundle 14 (Patch 5013)

Download patch 5013 (UB14 64 bit version) from EMC Powerlink site and follow the readme

documentation that comes with this patch. Once all pre-requisites are followed in the

readme, you will be ready to apply UB14.


Execute Patch61014383_5013.exe on the ECC Repository (A node) host first.

Click OK.

Click Next.

Click Install.

Follow the on-screen prompts. This will take time to complete as it replaces the current

Oracle services.

Before selecting “Yes, I want to restart my computer now” make sure that any Windows

services that were disabled are re-enabled. Otherwise, the computer may not come back up.

Select Finish.


4.12 Update Bundle 14 (Patch 5013) on Nodes (emccc02/03)

Execute Patch61014383_5013.exe on the StorageScope host emccc02, and when

completed, execute on the emccc03 host.

4.13 Add local ORA_DBA Group to each Cluster Node

Add a local Group called ORA_DBA to each node. This is a solution to a problem described

in EMC203001.

4.14 Edit ecc_server.ini File

After upgrading a cluster configuration, you must re-enter the IP aliases in the

ecc_server.ini file. Failure to do so results in communication problems between the

ControlCenter Console interfaces and the infrastructure. To enable correct name resolution

when logging into the ECC Console, perform the following to the ecc_server.ini file:

Locate the file on the xxx-emccc01a server and also on the servers xxx-emccc02 and xxx-

emccc03

<Install_Root>\ecc_inf\data\ecc_inf_hostname\data In this instance, the <Install_Root> is the R: drive. Open the ecc_server.ini file and search for the line that contains the string name server

aliases and add the physical IP addresses (not logical) of Node A and Node B respectively

as shown in the example below:

name server aliases = 172.19.234.73,172.19.234.74


4.15 Edit the Master Agent file ctg.ini

Locate the ctg.ini file in the R:\ECC\exec. Add the following entry: [Default] cluster = true

4.16 Edit the ecc_store.ini file

Locate the file where each Store is installed. For example, in S:\ECC\ecc_inf\data\ecc_inf_hostname\data, add the following entry: use fixed port = true

4.17 Upgrade the Console to 6.1.0.14.383

Connect a browser to //clustername:30002/webinstall. Click on the Console Patch 6.1.0.14.583 if the Console is already installed. Otherwise, start

at Console 6.1.0 and install that first.

Select to install the Console 6.1.0 followed by applying the Console patch.


4.18 Create the ECCRG Resources

This section outlines the procedure for adding the ECC Services as Generic Service

resources to the ECCRG Application. It should be noted that the Generic Services for ECC

are only created after installation of ECC and, also, the application of any patch such as as

an Update Bundle, or an OCPU have been successfully installed. If this were an upgrade of

an existing ECC build where a new Update Bundle is being installed, all of the ECC

resources under the ECCRG Application container would need to be deleted then recreated

once the patch had been applied.

Right click on the ECCRG and select Add a resource and choose option 4 – Generic

Service.


Select the OracleECCREP_HOMETNSListener service.

Click Next.


Click Next.

Click Finish.


Repeat the procedure for the remaining ECC services. You will end up with the following listing:

Next, right click on each of the resources and select Properties. Open the Dependancies tab and add the dependant resource as summarised in Table 2:

ECC Resource Dependancy

OracleECCREP_HOMETNSListener VIP Address of ECC

OracleServiceRAMBDB OracleECCREP_HOMETNSListener

EMC ControlCenter Repository OracleServiceRAMBDB

EMC ControlCenter Key Management Server EMC ControlCenter Repository

EMC ControlCenter Server EMC ControlCenter Key Management Server

EMC ControlCenter Web Server EMC ControlCenter Server

EMC ControlCenter Master Agent EMC ControlCenter Web Server

Table 2


Click OK. Next, bring the ECCRG online.


4.19 Post UB14 and OCPU Cluster Preparation

Refer to Primus Solution emc266055 to enable the ECCRG to failover to the B node. This is

summarised here for convenience:

On the A node (Active node), make sure that all the ECC resources are online.

Run clustersave.bat found in R:\ECC\Tools\Utils.

Take the ECC services offline, but make sure the R drive and IP are left online.

Move the ECCRG to the B node.

On the B node, run clusterupgrade.bat found in R:\ECC\Tools\Utils.

Reboot the B node.

On the A node, bring the ECC services back online.

When the B node has come back online, move the ECCRG back to the B node to

test that the ECC services are now running on the B node.

Move the ECCRG back to the A node.


4.20 Install Agents

Table 3 shows the agents that should be installed on each of the ECC servers. Note that all

the ECC servers should have the Host and Master Agents installed. The Master Agent will

be installed by default on the Infrastructure servers during the ECC and StorageScope

server installs.

AGENT ECC SERVER

Symmetrix Agent EMCCC02

SDM Agent EMCCC02

NAS Agent (if required) EMCCC02

Integration Gateway Agent EMCCC02

WLA Archiver EMCCC02

Clariion Agent (if applicable) EMCCC03

FCC Agent EMCCC04 and EMCCC05

Table 3

4.21 Master Agent Configuration on the Cluster Nodes

Check that the Master Agent on both Nodes of the Cluster are at the same version. You will

see that the Active node of the cluster will show the Master Agent as Active, but it will be

Inactive on the B Node. This is expected. If the Master Agent on the B Node has not

upgraded to 6.1 UB14, then do the following:

On the Node that is not active (the Master Agent is not active on that node), rename all files

with .COMFILE and .lck extensions found in the C:\Windows\ECC directory.

Failover the Cluster to restart the Master Agent on that node. The .COMFILE and .lck files

will be recreated by the Master Agent when it starts. The Master Agent should now be active

against that Node in the ControlCenter Console.

On the other Node (the Node that is now not active), rename all files with .COMFILE and .lck

extensions in the C:\Windows\ECC directory.

Failover the Cluster again back to the A node and the Master Agent will create the

.COMFILE and .lck files again. The Master Agent should now be at the same patch level on

both nodes.

4.22 Install Control Center Licences

Open the ECC Console, click on Administration>Install>Edit>ECC Licenses.

Add the license keys.


4.23 Agent Patching

Patch the Agents using the ControlCentre Console. The Master Agent must be patched first.

Open the ECC Console and select Agents view then select Show All from the menu bar.

Right click on each ECC host in turn starting with the ECC repository server EMCCC01A

and select Apply Patch.

Follow the prompts and run the patch install.

The Agents should upgrade to version 6.1.0.14.383.


4.24 Add Gatekeepers to EMCCC02 and EMCCC03 Servers

Allocate six Gatekeepers on a designated pair of FA directors on the VMAX array.

After Gatekeeper allocation is successfully completed and a disk rescan has been performed

on the host, EMC PowerPath will correctly display the presented devices as per the example

below.

4.25 Install Unisphere for VMAX on xxxx-EMCCC03

Download the Unisphere for VMAX from EMC Powerlink.

Stop all ECC Services running on the server. Run the UNIVMAX_V1.5.0.3_WINDOWS_X86_64.exe file on the emccc03 server. This

install needs to have Solutions Enabler 64-bit installed which was covered in Sect 5.10.

Restart all ECC Services.

4.26 Install CLARiiON Agent and Naviseccli

In sites where a VNX (or CLARiiON®) array is to be deployed, a CLARiiON Agent will need

to be installed. The CLARiiON Agent will need to be on a server that has naviseccli installed,

likely the xxxx-emccc03 server.

Run the NaviCLI-Win-32-x86-en_US-7.32.0.5.54-1.exe file and follow the prompts. You will

be prompted to create a security so you will need the logon credentials to the VNX or

CLARiiON array.

4.27 Install UnisphereClient

Download the UnisphereClient-Win-32-x86-loc-1.2.0.1.0556-7.exe from EMC Powerlink site.

Run the UnisphereClient-Win-32-x86-loc-1.2.0.1.0556-7.exe on the xxxx-emccc03 server.

4.28 Install the NAS Agent

If required, install the NAS Agent on the same server as the Storage Scope server; in this

instance, dtcp-emccc02


Once installed, navigate to the agent folder CNN610 and change the entry in the CNN.INI

file under the [SSH] heading from Version = 1 to version = 2

Re start the NAS Agent. Make sure the NAS is discovered using the Assisted Discovery wizard in ControlCenter. If

there are connection problems, you will need to use the emcplink.exe utility. This can be

found in the CNN610 Agent folder.

Next, run the following commands on xxxx-emccc02 emcplink -setpolicy +EMC_SSH_KEY_SECURITY_NONE Then, to discover a Celerra®, run the following substituting the correct password for –pw

variable.

emcplink -ssh -interactive -2 -pw passwd nasadmin@<IP Address of Control Stn> If discovering a NetApp Filer, substitute the correct user and IP for the Filer.This will set up a

ssh session with the Control Station or NetApp Filer and log in. Disconnect from the session.

Retry the Assisted Discovery. The Celerra or NetApp Filer should now discover.

4.29 Install the Integration Gateway Agent

Install the Integration Gateway Agent on the xxxx-emccc02 server.

When prompted, enter the IP of the Netprobe Server and click Next to complete the

installation.

This will then enable ECC Alerts to be sent via the Integration Gateway once a Management

Policy has been created and attached to Alerts under Administration\Alert Definitions,

discussed in the next section of this article.


4.30 Install the Master Agent on xxxx.emccc04/05.

4.31 Disable ControlCenter status traps

A number of selected alerts will be sent via a Management Policy (discussed in Section

5.38) to Webtop. As such, ControlCenter status traps need to be prevented from flooding the

Webtop interface. To do this, edit the following file:


Navigate to the \class directory, which is installed by default in the following location: R:\ECC\ecc_inf\data\<hostname>\class Open the SnmpEventPlugin.properties file in the \class directory and find the following

line:

enableStatusListener=true

Set the enableStatusListener value to "false" and save the SnmpEventPlugin.properties

file.

Restart the ControlCenter Server service to apply the change. 4.32 Install the FCC Agent on xxxx.emccc04/05

Install the FCC Agents on emcc04 and emcc05 servers.

4.33 Discover Fabric on ECC console

Before attempting the discovery of the switches into the ECC console view, perform the

tasks below on each switch:

Log in to Switch.

Go to Config mode and type the following command:

Snmp-server host 10.242.95.140 (IPaddres of emccc04) version 1 private udp-port 162

Snmp-server host 10.242.95.141 (IPaddres of emccc05) version 1 private udp-port 162

Copy Running-config startup config.

Exit.

Open ECC console Click Discover – Connectivity in the menu bar and select interface Cisco,

type switch name select SNMP V2, and type private – SNMP community and 162 – SNMP

Port.

Click Search Now.


Once all the fabrics have discovered, re-name as below:


4.34 Enable ControlCenter Fabric Validation

For the FCC agent to correctly import what is physically on the switch, ensure the Fabric Validation

DCP is setup as:


4.35 Enable Alert Retention Policy

Navigate to the Data Retention folder, right click on the ALERT, and select Edit Data Retention. Then

enter the settings shown:


4.36 References

Document SharePoint / Web URL

ControlCenter 6.1 Planning Guide

https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-006-387.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tDb250ZW50RXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwNDVjMDlmLGRvY3VtZW50VHlwZT1wZGYsbmF2ZU5vZGU9MGIwMTQwNjY4MDM1YWM5Yl9Hcmlk

UB14 Readme http://ftp.emc.com/action/storage;jsessionid=rmobcba1ksj71f5chbgefr61e

OCPU 5011 https://support.emc.com/downloads/5690_ControlCenter

emc266055 http://knowledgebase.emc.com/emcice/documentDisplay.do;jsessionid=587B1F3A8CC50ED161A3745020BE69C6?docType=1006&clusterName=DefaultCluster&resultType=5002&groupId=1&page=&docProp=$solution_id&docPropValue=emc266055&passedTitle=null

4.37 Glossary

Term Definition CLI Command Line Interface DNS Domain Name Server ECC EMC Ionix Control Centre LAN Local Area Network SE EMC Solutions Enabler SMC EMC Symmetrix Management Console SSH Secure Shell

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






http://knowledgebase.emc.com/emcice/documentDisplay.do;jsessionid=587B1F3A8CC50ED161A3745020BE69C6?docType=1006&clusterName=DefaultCluster&resultType=5002&groupId=1&page=&docProp=$solution_id&docPropValue=emc266055&passedTitle=null




installing emc controlcenter on a windows 2008 … · as a second store server and will also run...

Documents