TECHNICAL NOTES

EMC Ionix
ControlCenter
Installing Ionix ControlCenter in a VMware Environment
Technical Notes
P/N 300-006-787
REV A05

December, 2011

This document provides an overview of the steps required to plan for and install Ionix
ControlCenter 6.x components (including infrastructure components) in a VMware virtual
environment. Installing Ionix ControlCenter components in VMware may be accomplished
via a direct install (new components) or via a migration from physical to virtual (converting
existing components). Topics include:
Overview................................................................................................................... 1
Sizing your VMware Configuration ............................................................................. 2
Planning for Ionix ControlCenter Migration............................................................... 10
Migrating a Physical Host to a Virtual Machine or Guest........................................... 12
Discovery of ESX Servers in Ionix ControlCenter ....................................................... 13
Moving Guests from one ESX Server to another ....................................................... 14
Creating the New Discovery_CC_ESX Data Collection Policy ..................................... 14
Refreshing Ionix ControlCenter after Moving a Virtual Guest..................................... 17

Overview
Ionix ControlCenter 6.x components, including infrastructure components, are supported
on VMware ESX Server 3.0.x, 3.5.x, 4.0.x, and ESXi 5.0 server Virtual Machines (VMs) also
referred to as guests. The terms Virtual Machine, VM, guest, and Virtual guest are used
interchangeably in this document.
The VMware Systems Compatibility Guide for ESX Server 3.x , VMware Systems
Compatibility Guide for ESX Server 4.x, and VMware Systems Compatibility Guide for ESXi
server 5.0 available at www.vmware.com, provides an up-to-date list of ESX Server 3.x,
4.x, and ESXi 5.0 supported guest Operating Systems.
Sizing your VMware Configuration

The current version of the EMC Ionix ControlCenter Support Matrix, also available on EMC
online support, provides an up-to-date list of supported Ionix ControlCenter components
and versions.

Physical to Virtual Migration

You use VMware Converter 2.0.x, installed on a stand-alone Windows host, to migrate a
physical host to a VMware ESX Server Virtual Machine or guest. The entire image of the
physical host is migrated onto the Virtual Machine. The process can take anywhere from
15 minutes to several hours based on the size of the host.
Physical to Virtual Migration is a one-way process. Physical hosts can be Migrated to
Virtual Machines but Virtual Machines cannot be Migrated to physical hosts. Several
Virtual Machines or guests can exist on a single ESX Server.
It is not necessary to dedicate an ESX Server solely to Ionix ControlCenter component
guests. However, any ESX Server containing Ionix ControlCenter component guests must
provide the necessary system resources for those guests and the Ionix ControlCenter
components must be installed based on the guidelines provided in Sizing your VMware
Configuration on page 2.
The benefits of dedicating an ESX Server solely to Ionix ControlCenter component guests
are that you avoid the potential of unpredictable resource demand created by other
applications running on the same ESX Server. If the demand for system resources from
other guests has high peaks, the performance and scalability of Ionix ControlCenter
components may be negatively impacted.
The negative side of dedicating an ESX Server solely to Ionix ControlCenter component
guests, aside from the fact that it may be against your companys policy to do so, is the
loss of the standardized configuration and management of an ESX Farm along with the
higher flexibility the ESX Farm provides for advanced VMware technology like VMotion.

Note: When creating VMware guests intended to serve as host platforms for Ionix
ControlCenter components you should carefully consider the configuration. If the disk
size, CPU, and RAM of the guest conform to the host specifications presented in this
document, you can expect that performance and scalability of the Ionix ControlCenter
components is comparable to single-core hardware, which is described in the current
version of the EMC Ionix ControlCenter Performance and Scalability Guidelines.

Virtual to Virtual Migration

Using VMotion, a utility of VirtualCenter 2.0.x , 4.x, and 5.0 and accessible using a Virtual
Infrastructure (VI) Client, you can migrate a guest that is currently being used (hot) or not
being used (cold) from one ESX Server to another ESX Server. In this document:
Migrating a hot guest is referred to as VMotioning.
Migrating a cold guest is referred to as Migrating.

Sizing your VMware Configuration

This section identifies the count of guests needed to support a Ionix ControlCenter
deployment.

2 Installing Ionix ControlCenter 6.x in a VMware Environment

 Sizing your VMware Configuration

Planning for Ionix ControlCenter Infrastructure Guests

Follow these steps to determine the count of Ionix ControlCenter infrastructure guests:
a. Refer to to Table 3, Configuration#1: Single-core infrastructure host and Table 4
Configuration #1: Single-core host with infrastructure and agents in the EMC Ionix
ControlCenter Performance and Scalability Guidelines. Select the row that best
matches the configuration to be virtualized.
b. Refer to Tables 1 through 5 in this document. Select the table that corresponds to
the deployment on physical host. Tables include:
If the count of managed object is similar to the numbers presented in Table 4,
Configuration #1, of the EMC Ionix ControlCenter Performance and Scalability Guidelines,
then refer to Table 8, Ionix ControlCenter component location example, on page 15 for
deployment planning.

Planning for Ionix ControlCenter agents

The count of Ionix ControlCenter agent guests needed for a particular deployment
depends on the size and count of various managed objects like Symmetrix, CLARiiON,
databases etc. The scalability of a Ionix ControlCenter agents deployed on a guest is
equivalent to one deployed on single-core physical hosts described in the Agents
guideline section in EMC Ionix ControlCenter Performance and Scalability Guidelines.
Table 6, Infrastructure with Agents Deployment on VMware, on page 10 provides the
configuration of agent guests.

Note: System resources needed to support an agent guest are independent of the
installation size of deployment. For example, system resource consumption of a guest
installed with Storage Agent for Symmetrix and Symmetrix SDM Agent is the same if the
Ionix ControlCenter infrastructure is on physical or virtual server or if the installation size is
small or large.

Planning for StorageScope

Table 7, Ionix ControlCenter StorageScope Deployment on VMware, on page 10 provides
planning information about StorageScope component deployment on VMware. This
configuration supports File Level Reporter (FLR) processing of maximum of 2000 file
systems.

About these tables

Physical-to-virtual migration on the following pages are for illustration purpose only.

Installing Ionix ControlCenter 6.x in a VMware Environment 3

Sizing your VMware Configuration

Extra Large Configuration

Table 1 Extra Large Infrastructure Deployment on VMware

Infrastructure guests resource utilization for an extra large configuration

175 Arrays 2,050 Hosts 75 ESXs 1200 Databases 132 Switches

System
System System Resources
Resources Resources Consumed on
Components on VM Provisioned Consumed at Peak Average Comments

ECC Server CPU: 1 vCPU CPU: 80% (2400 CPU: 30% (900 Peak usage is during nightly discovery DCP
Repository (3000 MHz) MHz) MHz) processing time. For large configuration
Store Memory: 2 Memory: 65% Memory: 45% the duration could be up to 5 hours.
GB Disk: 8000 KBps Disk: 6000 KBps
Disk: 90 GB Network: 700 KBps Network: 300 KBps

Store CPU: 1 vCPU CPU: 30% (900 MHz) CPU: 10% (300 Peak usage is during nightly discovery DCP
(3000 MHz) Memory: 20% MHz) processing time. For large configuration
Memory: 2 Disk: 120 KBps Memory: 10% the duration could be up to 5 hours.
GB Network: 750 KBps Disk: 25 KBps
Disk: 10 GB Network: 100 KBps

Store CPU: 1 vCPU CPU: 30% (900 MHz) CPU: 10% (300 Peak usage is during nightly discovery DCP
(3000 MHz) Memory: 20% MHz) processing time. For large configuration
Memory: 2 Disk: 120 KBps Memory: 10% the duration could be up to 5 hours.
GB Network: 750 KBps Disk: 25 KBps
Disk: 10 GB Network: 100 KBps

4 Installing Ionix ControlCenter 6.x in a VMware Environment

 Sizing your VMware Configuration

Large Configuration
Table 2 Large Infrastructure Deployment on VMware

Infrastructure guests resource utilization for a large configuration

120 Arrays 1,400 Hosts 50 ESXs 750 Databases 88 Switches

System
System System Resources
Resources Resources Consumed on
Components on VM Provisioned Consumed at Peak Average Comments

ECC Server CPU: 1 vCPU CPU: 75% (2250 CPU: 25% (750 Peak usage is during nightly discovery DCP
Repository (3000 MHz) MHz) MHz) processing time. For large configuration the
Store Memory: 2 Memory: 55% Memory: 45% duration could be up to 5 hours.
GB Disk: 6000 KBps Disk: 4500 KBps
Disk: 80 GB Network: 500 KBps Network: 300 KBps

Store CPU: 1 vCPU CPU: 30% (900 MHz) CPU: 10% (300 Peak usage is during nightly discovery DCP
(3000 MHz) Memory: 20% MHz) processing time. For large configuration the
Memory: 2 Disk: 120 KBps Memory: 10% duration could be up to 5 hours.
GB Network: 750 KBps Disk: 25 KBps
Disk: 10 GB Network: 100 KBps

Installing Ionix ControlCenter 6.x in a VMware Environment 5

Sizing your VMware Configuration

LARGE - Physical Host Environment LARGE - Virtual Environment

ECC Server ESX Server 1

Store #1
Repository WLA Archiver #1
WLA Archiver #1
Master Agent ECC Server CLARiiON Agent #1 Symmetrix Agent #1
Symmetrix Agent #1
Host Agent Repository HDS Agent #1 SDM Agent #1
SDM Agent #1
Store #1 NAS Agent #1 Master Agent
Master Agent
Master Agent Master Agent Host Agent
HOST 1 Host Agent
Host Agent Host Agent
HOST 2

Guest A Guest B Guest C

FCC Agent #1
CLARiiON Agent #1 STS Server
Centera Agent #1 STS Repository
Master Agent
ESX Server 2
Master Agent
WLA Archiver #2
Host Agent Host Agent
Store #2 CLARiiON Agent #2 Symmetrix Agent #2
HOST 3 Master Agent HDS Agent #2 SDM Agent #2
HOST 4 Host Agent NAS Agent #2 Master Agent
Master Agent Host Agent
Store #2 Host Agent
FCC Agent #2
WLA Archiver #2
CLARiiON Agent #2
Symmetrix Agent #2 Guest D Guest E Guest F
HDS Agent #1
SDM Agent #2
Master Agent
Master Agent
Host Agent
Host Agent ESX Server 3
HOST 5 WLA Archiver #3
HOST 6
STS Server CLARiiON Agent #3 Master Agent
STS Repository FCC Agent #1 Host Agent
CLARiiON Agent #3
Store #3 Master Agent Centera Agent #1
NAS Agent #1
WLA Archiver #3 Host Agent Master Agent
Centera Agent #2
Symmetrix Agent #3 Host Agent
Master Agent
SDM Agent #3
Host Agent
Master Agent Guest G Guest H Guest I

HOST 7 Host Agent

HOST 8

ESX Server 4
FCC Agent #3
NAS Agent #2
CLARiiON Agent #4
Centera Agent #3 Symmetrix Agent #3 Symmetrix Agent #4
HDS Agent #2
Symmetrix Agent #4 SDM Agent #3 SDM Agent #4
Master Agent
SDM Agent #4 Master Agent Master Agent
Host Agent
Master Agent Host Agent Host Agent
HOST 9 Host Agent
HOST 10
Guest J Guest K

FCC Agent #2 CLARiiON Agent #4

Centera Agent #2 FCC Agent #3
Master Agent Centera Agent #3
Host Agent Master Agent
Windows Host running
Host Agent
VMware Converter 2.0.1

Guest L Guest M

Note: In this example only two stores are migrated from the physical environment
to the virtual environment because the physical is using Dual Processors and
the virtual is using Dual Core.

Figure 1 Large Ionix ControlCenter 6.x Physical to Virtual Migration Example

6 Installing Ionix ControlCenter 6.x in a VMware Environment

 Sizing your VMware Configuration

Medium Configuration
Table 3 Medium Infrastructure Deployment on VMware

Infrastructure guests resource utilization for a medium configuration

60 Arrays 680 Hosts 35 ESXs 380 Databases 44 Switches

Table 1:
System
System System Resources
Resources Resources Consumed on
Components on VM Provisioned Consumed at Peak Average Comments

ECC Server CPU: 1 vCPU CPU: 75% (2250 CPU: 20% (600 Peak usage is during nightly discovery DCP
Repository (3000 MHz) MHz) MHz) processing time. For large configuration the
Store Memory: 2 GB Memory: 55% Memory: 45% duration could be up to 5 hours.
Disk: 70 GB Disk: 6000 KBps Disk: 4500 KBps
Network: 500 KBps Network: 300 KBps

Table 4 Medium Infrastructure Deployment on VMware

Infrastructure guests resource utilization for a medium configuration

45 Arrays 550 Hosts 25 ESXs 280 Databases 28 Switches

Table 2:
System
System System Resources
Resources Resources Consumed on
Components on VM Provisioned Consumed at Peak Average Comments

ECC Server CPU: 1 vCPU CPU: 75% (2200 CPU: 20% (600 Peak usage is during nightly discovery DCP
Repository (3000 MHz) MHz) MHz) processing time. For large configuration
Store Memory: 2 GB Memory: 55% Memory: 30% the duration could be up to 4 hours.
Disk: 60 GB Disk: 7000 KBps Disk: 4500 KBps
Network: 1500 KBps Network: 500 KBps

Installing Ionix ControlCenter 6.x in a VMware Environment 7

Sizing your VMware Configuration

MEDIUM - Physical Host Environment MEDIUM - Virtual Environment

ECC Server ESX Server 1

Store #1
Repository
WLA Archiver #1
Master Agent ECC Server Symmetrix Agent #1 Symmetrix Agent #2
Symmetrix Agent #1
Host Agent Repository SDM Agent #1 SDM Agent #2
SDM Agent #1
Store #1 Master Agent Master Agent
Master Agent
Master Agent Host Agent Host Agent
HOST 1 Host Agent
HOST 2 Host Agent

Guest A Guest B Guest C

WLA Archiver #2
Symmetrix Agent #2 CLARiiON Agent #1

ESX Server 2
SDM Agent #2 FCC Agent #1

Master Agent HDS Agent #1

Centera Agent 1 WLA Archiver #1 WLA Archiver #2
Host Agent
Master Agent STS Server CLARiiON Agent #1 CLARiiON Agent #2

HOST 3 Host Agent STS Repository FCC Agent #1 FCC Agent #2

HOST 4 Master Agent HDS Agent #1 HDS Agent #2
Host Agent Centera Agent #1 Centera Agent #2
CLARiiON Agent #2 Master Agent Master Agent
STS Server
FCC Agent #2 Host Agent Host Agent
STS Repository
HDS Agent #2 Guest D Guest E Guest F
Master Agent
Centera Agent #2
Host Agent
Master Agent
Host Agent
HOST 5
HOST 6

Windows Host running

VMware Converter 2.0.1

Figure 2 Medium ControlCenter 6.x Physical to Virtual Migration Example

8 Installing Ionix ControlCenter 6.x in a VMware Environment

 Sizing your VMware Configuration

Small Configuration
Table 5 Infrastructure with Agents Deployment on VMware

Infrastructure guests resource utilization for a small configuration

30 Arrays 330 Hosts 25 ESXs 180 Databases 24 Switches

System System System

Resources Resources Resources
Components on VM Provisioned Consumed at Peak Consumed on Average Comments

ECC Server CPU: 2 vCPU CPU: 99% (5972 CPU: 55% (3200 MHz) Peak utilization is during ETL processing
Repository (6000 MHz) MHz) Memory: 35% time. The CPU% stays at 99% for about
Store Memory: 3 GB Memory: 55% Disk: 14000 KBps 30 minutes when ETL is running. For
Disk: 80 GB Disk: 51630 KBps deployment planning purposes, go with
Performance Manager Network: 500 KBps average resources consumed.
ControlCenter Console Network: 1000 KBps
CLARiiON Agent
Workload Analyzer
Archiver
FCC Agent
VMware Agent
Oracle Agent
StorageScope Server
(no FLR)

SMALL- Physical Host Environment SMALL- Virtual Environment

ECC Server ESX Server 1

Repository WLA Archiver
ECC Server
Store Symmetrix Agent #2
Repository Symmetrix Agent #1 Symmetrix Agent #2
STS Server SDM Agent #2 Guest A
Store SDM Agent #1 SDM Agent #2
STS Repository Master Agent
STS Server Master Agent Master Agent
Symmetrix Agent #1 Host Agent
STS Repository Host Agent Host Agent
SDM Agent #1
Performance Manager
CLARiiON Agent HOST 2
ControlCenter Console
FCC Agent
CLARiiON Agent Guest B Guest C
Master Agent
Workload Analyzer Agent
Host Agent
FCC Agent
HOST 1 Master Agent
Host Agent

Windows Host running

VMware Converter 2.0.1

Figure 3 Small ControlCenter 6.x Physical to Virtual Migration Example

Installing Ionix ControlCenter 6.x in a VMware Environment 9

Planning for Ionix ControlCenter Migration

Ionix ControlCenter Agent Guests

Table 6 Infrastructure with Agents Deployment on VMware

System System System

Resources Resources Resources
Components on VM Provisioned Consumed at Peak Consumed on Average Comments

Symmetrix Agent CPU: 1 vCPU CPU: 98% (2900 CPU: 26% (770 MHz) Peak utilization happens in bursts
Symmetrix SDM Agent (3000 MHz) MHz) Memory: 32% synchronized with DCP processing. The
Memory: 2 GB Memory: 41% Disk: 160 KBps 99% CPU doesnt stay for more than half
Disk: 10 GB Disk: 900 KBps a minute. For deployment planning
Network: 10 KPbs purposes, go with average resources
Network: 300 KBps consumed.

CLARiiON Agent CPU: 1 vCPU CPU: 99% (3000 CPU: 58% (1730 MHz) Overlap of discovery and WLA DCPs
HDS Agent (3000 MHz) MHz) Memory: 15% causes the peak demand for resource
NAS Agent Memory: 2 GB Memory: 15% Disk: 540 KBps usage. The CPU% stays 99% in regular
Disk: 50 GB Disk: 1357 KBps intervals for about 25 minutes during
FCC Agent Network: 109 KBps every hour. For deployment planning
Workload Analyzer Network: 406 KBps purposes, go with average resources
Archiver consumed.
VMware Agent Workload Analyzer Archiver contributes
to 70% of the CPU consumption.

Ionix ControlCenter StorageScope Deployment

Table 7 Ionix ControlCenter StorageScope Deployment on VMware

System System System

Resources Resources Resources
Components on VM Provisioned Consumed at Peak Consumed on Average Comments

StorageScope Server CPU: 2 vCPU CPU: 50% (3000 CPU: 5% (300 MHz) Peak usage is during FLR DCP and ETL
StorageScope (6000 MHz) MHz) Memory: 10% processing time of 2000 filesystems.
Repository Memory: 2 GB Memory: 40% Disk: 5000 KBps PLEASE RUN ETL WITH SSL DISABLED.
Disk: 200 GB Disk: 5000 KBps Refer to the Enabling/Disabling SSL
Network: 100 KPbs Technical Notes for more information on
Network: 4500 KBps disabling the required components.
Refer to the EMC Ionix ControlCenter
Performance and Scalability Guidelines,
Guideline P3 Allocate disk space for the
StorageScope host, for more information
on computing disk space for a VM.

Planning for Ionix ControlCenter Migration

You can either install Ionix ControlCenter 6.x components directly onto VMware guests as
a new installation, or migrate existing physical Ionix ControlCenter 6.x components onto
VMware guests. The number of guests that can be installed on an ESX depends on its
available capacity. Test ESX server had three Ionix ControlCenter guests. A larger ESX
server with sufficient available system resources can accommodate more Ionix

10 Installing Ionix ControlCenter 6.x in a VMware Environment

 Planning for Ionix ControlCenter Migration

ControlCenter guests. When an ESX server satisfies the system resource requirements of
Ionix ControlCenter guests, similar end-user deployment experience occurs on physical
hosts.
Ionix ControlCenter components that are not supported in VMware must be un-installed
from the physical host before migrating that host to a Virtual Machine (guest).

Note: Pre-6.x versions of Ionix ControlCenter must first be upgraded to Ionix ControlCenter
6.x before migrating to VMware guests.

Migration Pre-Requisites

Software
The following software requirements have been qualified and documented by EMC:
Ionix ControlCenter 6.x
ESX Server 3.0.x, 3.5.x, 4.0.x
ESXi Server 5.0
VMware Converter 2.0.x
VirtualCenter 2.0.x, 4.x, and 5.0
Virtual Infrastructure Client (VI Client)
Virtual Infrastructure Server (VI Server)

Note: For a list of Ionix ControlCenter components that are supported on an ESX Server
guest, refer to the current version of the EMC Ionix ControlCenter Support Matrix.

Hardware
ESX servers built on multi-core (dual-core or quad-core) processors should be used for
Ionix ControlCenter deployment. Please ensure that the ESX server meets SPEC CINT2000
Rate (baseline) score of 123 or SPEC CINT2006 Rate (baseline) score of 61. Test ESX server
had the following specifications. It is ok use FSB with higher than 1000 MHz speed:
Base Unit Processor: Dual-core Intel Xeon 5160 3.0 GHz processor, 4 MB cache, 1333
MHz FSB
Second Processor: Dual-core Intel Xeon 5160 3.0 GHz processor, 4 MB cache, 1333
MHz FSB
Memory: 8 GB, 4 GB PC2-5300/667MHz DDR2 FB-DIMM (2 DIMMs)
Hard Drive: 146 GB, SAS, 3.5", 10K RPM
Hard Drive Controller: Dell PERC 5/i Integrated RAID Controller
NIC: Broadcom BCM5708C NetXtreme II GigE (2 internal, built-in),
plus Intel Corporation 82540EM GigE (4port) (1 unit)
CD-ROM or DVD-ROM Drive: 24x IDE CR-RW/DVR ROM Drive
Additional Storage Products: 146 GB, SAS, 3.5", 10K RPM

Note: Best Practice for NICs: 1 NIC dedicated to Console OS (10/100 or GigE), 1 NIC
dedicated to VMotion (GigE), and 1 or more NICs for VMs (10/100 or GigE).

Installing Ionix ControlCenter 6.x in a VMware Environment 11

Migrating a Physical Host to a Virtual Machine or Guest

Note: Best Practice for HBAs: Assign two HBAs to each ESX Server for redundancy and to
provide load balancing. Make sure both HBAs can access both Storage Processors if using
CLARiiON storage.

Note: On ESX Server 3.5.x, 4.0.x, and ESXi Server 5.0 NPIV enabled is supported by Ionix
ControlCenter.

Other Considerations
Do not super size the Ionix ControlCenter VMware guests. Configure the guests such
that resources provisioned and utilized remain within reasonable limits. This is
especially important if you are planning to use VMotion and associated technologies.
For example, you may find it difficult to VMotion a guest requiring 3 GB of RAM
compared to the same Ionix ControlCenter components split between two guests with
1.5 GB RAM each. Smaller guest sizes make it easier to find an ESX Server with the
available resources.
Deploy components on the guest that do not have synchronized resource demands.
For example Ionix ControlCenter and StorageScope Repositories on the same guest
will create a resource consumption hot spot, because both Ionix ControlCenter
components are most active between midnight and early morning (simultaneously)
performing scheduled rediscovery of managed objects and FLR processing.
Combine components that complement the cost of virtualization. Having the
StorageScope Server and StorageScope Repository on the same guest reduces
virtualization overhead compared to those on separate guests on the same or
different ESX Servers.
For optimum user experience, ESX Servers should not consume more than 80% of CPU
resources during peak usage time. Refer to Sizing your VMware Configuration on
page 2 for estimates of resource consumption by various guests installed with
supported Ionix ControlCenter components.
Provisioning of more than 2 vCPUs (e.g. 4 vCPUs) to guests installed with Ionix
ControlCenter components may negatively impact guest performance.

Migrating a Physical Host to a Virtual Machine or Guest

Physical to Virtual Migration
1. Upgrade the existing physical Ionix ControlCenter environment to Ionix ControlCenter
6.x if it isn't already at this version.
2. Review the current version of the EMC Ionix ControlCenter Support Matrix to determine
which Ionix ControlCenter components are supported on a VMware guest.
3. Review the information provided in Sizing your VMware Configuration on page 2 to
determine the system resources required to implement various Ionix ControlCenter
configurations in a virtual environment.
4. Check the destination ESX server(s) to verify they provide connectivity to the same
subnet that the existing physical server is connected to.

12 Installing Ionix ControlCenter 6.x in a VMware Environment

 Discovery of ESX Servers in Ionix ControlCenter

5. Plan the deployment of your Ionix ControlCenter components in the new virtual
environment, referring to step 2 and step 3 above to determine how many ESX
Servers and how many guests will be used, where each guest will be deployed, and
which specific Ionix ControlCenter components will be installed on each guest.
6. Ready your physical hosts for migration to their new virtual guests. Remember,
VMware Converter 2.0.x will migrate the entire image of the physical host to the new
virtual guest and not all Ionix ControlCenter components are supported in VMware.
Therefore, each physical host should either be configured with the Ionix ControlCenter
components you want it to have when it is migrated to its new virtual guest, or at least
make sure any unsupported components are uninstalled from the physical host prior
to using VMware Converter to migrate it.

Note: If you migrate a physical host containing a Storage Agent for Symmetrix and/or
Symmetrix SDM Agent, the destination ESX Server must be able to see the same
Symmetrix Array that the physical host can see. All devices visible to the physical host
being migrated, including all Gatekeeper devices, will need to be re-created on the
destination ESX Server and made visible to the new guest via Raw Device Mapping (RDM).

7. Implement the plan by migrating each physical host to its new ESX Server virtual guest
using VMware Converter 2.0.x.
8. Shut Down the old physical Ionix ControlCenter 6.x host and keep it cold as a
fall-back.
9. Configure each new Ionix ControlCenter guests resources (memory, CPU, disk space,
etc.) based on the information provided in Sizing your VMware Configuration on
page 2.
10. Start Up the new Ionix ControlCenter 6.x guests and components and check
connectivity from Web browsers, Ionix ControlCenter Consoles and Ionix ControlCenter
agents.

Discovery of ESX Servers in Ionix ControlCenter

All ESX Servers are discovered by an Ionix ControlCenter VMware Agent.
In order for Ionix ControlCenter to coordinate and stay synchronized with VMware ESX
Servers and their guests, and especially to enable the use of VMotion and other VMware
technologies, it is essential that all ESX Servers be discovered by an Ionix ControlCenter
VMware Agent.

Note: The VMware Agent must be installed on a Windows host. A VMware Agent discovers
ESX Servers directly or by using a VMware VirtualCenter.

If an ESX Server contains guests with Ionix ControlCenter components installed on them,
Ionix ControlCenter needs to be aware of all ESX Servers and all guests within the
environment.
By default, the Ionix ControlCenter VMware Agent Discovery_00 Data Collection Policy
(DCP) will discover all ESX Servers in the environment once per day at midnight. This
refreshes the Ionix ControlCenter Repository and Console with the current ESX Server and
guest information.

Installing Ionix ControlCenter 6.x in a VMware Environment 13

Moving Guests from one ESX Server to another

Moving Guests from one ESX Server to another

Virtual to Virtual Migration
Using VMotion you can VMotion or migrate a guest that is currently being used (hot) or
not being used (cold) from one ESX Server to another ESX Server.
Migrating a hot guest is referred to as VMotioning.
Migrating a cold guest is referred to as Migrating.
If you are VMotioning or migrating a guest that does not contain any Ionix ControlCenter
components, then the default VMware agent Discovery_00 DCP will take care of refreshing
the Ionix ControlCenter Repository and Console.
If you are VMotioning or migrating a guest that does contain a Ionix ControlCenter
component, then a new VMware agent Discovery DCP is required.
This new DCP will be run automatically every day at midnight or manually via a pop-up
menu in Ionix ControlCenter following the VMotion or Migration of a Ionix ControlCenter
component guest from one ESX Server to another.
This new VMware agent Discovery DCP provides a mechanism for Discovering ONLY ESX
Servers with Ionix ControlCenter component guests on them. By specifying in the DCP
definition that it applies only to those specific ESX Servers listed, it speeds up the
re-discovery process following the move of a guest from one server to another.

Note: If you VMotion a hot guest or migrate a cold guest containing a Storage Agent for
Symmetrix and/or Symmetrix SDM Agent, the destination ESX Server must be able to see
the same Symmetrix Array that the guest can see. For all devices visible to the guest being
VMotioned or migrated, including all Gatekeeper devices, the destination ESX server
needs to access the same array devices that the guest is using on the source ESX server.
Make all devices visible to the guest via Raw Device Mapping (RDM).

Creating the New Discovery_CC_ESX Data Collection Policy

In the example screen shots that follow, there are 3 ESX Servers depicted:
ESX Server losak121
ESX Server losao224
ESX Server losao225
ESX Server losak121 does not contain any guests with installed Ionix ControlCenter
components, it is excluded from the new Discovery_CC_ESX DCP.

14 Installing Ionix ControlCenter 6.x in a VMware Environment

 Creating the New Discovery_CC_ESX Data Collection Policy

ESX Server losao224 and ESX Server losao225 both contain guests with installed Ionix
ControlCenter components, they are both included in the new Discovery_CC_ESX DCP.

Table 8 Ionix ControlCenter component location example

ESX Server -- losak121 ESX Server -- losao224 ESX Server -- losao225

Guest LOSAO104 Guest LOSAO105

Repository STS Repository
ECC Server STS Server
Guest LOSAO112 Guest LOSAO115
Store CLARiiON Agent

Steps to Create the Discovery_CC_ESX Data Collection Policy

In the Ionix ControlCenter Console:
1. Navigate to Administration > Data Collection Policies > Policy Templates > VMware
agent > Discovery
2. Right-Click the Discovery Template.
3. Select New.
4. Select the Properties Tab.
5. Enter CC_ESX in the Unique Descriptor Text Box.
6. Select the Apply To Tab.
7. Un-Check Apply this policy to all applicable Host objects
8. Check losao224 and losao225 in the Selected Hosts List.
9. Click OK.

Installing Ionix ControlCenter 6.x in a VMware Environment 15

Creating the New Discovery_CC_ESX Data Collection Policy

Figure 4 Discovery_CC_ESX Properties tab

Figure 5 Discovery_CC_ESX Source tab

16 Installing Ionix ControlCenter 6.x in a VMware Environment

 Refreshing Ionix ControlCenter after Moving a Virtual Guest

Figure 6 Discovery_CC_ESX Actions tab

Figure 7 Discovery_CC_ESX Apply To tab

Refreshing Ionix ControlCenter after Moving a Virtual Guest

After moving a Ionix ControlCenter component guest from one ESX Server to another,
either by migrating a cold guest or VMotioning a hot guest, The Ionix ControlCenter
Repository and Console need to be refreshed with the results of the move.

Installing Ionix ControlCenter 6.x in a VMware Environment 17

Refreshing Ionix ControlCenter after Moving a Virtual Guest

In this discussion:
The Source ESX Server = the ESX Server where the guest was moved FROM.
The Destination ESX Server = the ESX Server where the guest was moved TO.

Note: If the Destination ESX Server does not contain any guests with Ionix ControlCenter
components prior to the move, dont forget to add the ESX Server to the list of Selected
Hosts in the Discovery_CC_ESX DCP or it will not be included in the re-discovery following
the move, and Ionix ControlCenter will not be refreshed with the results of the move.

After moving the guest, in the Ionix ControlCenter Console:

Select a Policy View of the Destination ESX Server
Right-click on the VMware agent DCP Discovery_CC_ESX
Click Start DCP in the Pop-up Menu
The above steps manually kick-off the VMware agent Discovery_CC_ESX Data Collection
Policy (DCP).
The DCP will discover all ESX Servers listed in the policy definition. Since the number of
ESX Servers is limited to ONLY those with Ionix ControlCenter component guests, the
re-discovery process runs very quickly.
Note that when running the Dicovery_CC_ESX DCP, you cannot control the order of the ESX
Server discoveries. You are still only discovering ESX Servers with Ionix ControlCenter
components on them, but you cannot control the order in which those ESX Servers are
discovered.
If the Destination ESX Server is discovered first, then both the Source and Destination ESX
Servers will be refreshed in the Ionix ControlCenter Console and you will have completed
the refresh of Ionix ControlCenter.
If however the Source ESX Server is discovered first, then only the Destination ESX Server
will be refreshed in the Ionix ControlCenter Console and the Source ESX Server will contain
stale inaccurate information.
The way to correct this is to run the Discovery_CC_ESX DCP a second time, and all will be
refreshed.
The quick way to tell if you need to run the DCP a second time is to check the Last
Discovered column in the Policy View after you first run the Discovery_CC_ESX DCP.
If both the Source and Destination ESX Servers show an updated Time Stamp, then they
both refreshed with one run of the DCP.
If however ONLY the Destination ESX Server Last Discovered column shows an updated
Time Stamp, then you will need to run the DCP a second time to update the Source ESX
Server.

18 Installing Ionix ControlCenter 6.x in a VMware Environment

 Refreshing Ionix ControlCenter after Moving a Virtual Guest

Copyright 2008 - 2011 EMC Corporation. All rights reserved. Published in the USA.

Published August 2011

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

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

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

VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories
section on the EMC online support website.

Installing Ionix ControlCenter 6.x in a VMware Environment 19