EMC Control Center permits administration/management of the entire infrastructure, from
host/server OS, to SAN and to Storage systems, as Hitachi, HP, IBM, etc.
By the use of wizards, Control Center
permits administrators to do
automated storage provisioning.
Timefinder allows to make copies of volumen inside the same symmetrix system. (local)
SRDF permits to replicate/copy sites between Symmetrix systems. (remote copy)
Symmetrix architecture (950 particular, as A & B cards are back end)
0 C LOOP
Each Hyper has a number, or symvol. This
D symmvol, is consecutive, so always is
better to allocate continuous hypers.
(EV ER YT IME A H OST S D
TRIES TO WR ITE , THE
0 WR ITE GOES TO THE
CACHE, A ND THEN IS
DEST AG ED TO DISK )
D The rule of 17, comes from older DMX or
C 8000 series. Always the directors
configuration is started from highest # to
the lowest (17-0) (16-1), etc.
Hyper types: STD, BCV.
STD: is the normal volume, and is able to
be under RAID1, 5, 6, unprotected, etc.
BCV: is used by Timefinder, normally
unprotected, but it can also have R5, 6, 1, etc.
For cloning, it can be done from STD to BCV, or from STD to STD volumes.
VDEV: Virtual devices used with Timefinder Snap.
VCMDB: Only exists one VCMDB per Symmetrix system, here resides all the masking
configuration of the symmetrix system. (hosts HBA WWN, switch port, symm port, etc) Can be
backedup in the Control Center Host. (Right click, backup VCMDB.)
META: Meta devices are simply several logical devices that are presented to a host as just one
larger device. Within the Console it appears in most views to be several devices, though the
partnered members are easy to identify. Meta devices can be concatenated (data addressed
linearly) or striped (data address shuffled among the members).
R1 & R2: SRDF Volumes, R1 is source, R2 is target device.
Gatekeeper (GK): utilized to send commands to Symmetrix system. This volumes must be
presented to any host in which the ECC / Solution Enabler will be installed. Recommended is to
have at least 4 GK Volumes allocated to the host via Fibre Channel. If not GK available, another
hyper can be allocated to host. It normally has 6 cylinders (2.88).
Storage processors in clariion have separated caches for read & writes, but not mirrored like in
X95 30 SFI
S EM E MG MGMT
TU T I V T
Y C T WR S
ST S A P R COM1
X95 30 SFI
U E E
V MG T CFI
T ST I
TA Y C WR E
S S A P R
To allocate disks from Clariion arrays, we must create RAID Groups, when creating a RAID
Group, we must choose the type of protection you desire, but it will depend also, on how many
disks you have selected for the group.
* In Clariion, instead of Timefinder, we have Snapview, and instead of SRDF, Mirrorview.
The SAN or Storage Area Network, is network of storage disks. In large enterprises, a SAN
connects multiple servers to a centralized pool of disk storage. Compared to managing hundreds
of servers, each with their own disks, SANs improve system administration. By treating all the
company's storage as a single resource, disk maintenance and routine backups are easier to
schedule and control. In some SANs, the disks themselves can copy data to other disks for
backup without any processing overhead at the host computers.
Storage Scope: is an independent Oracle database for the reports There is a process that gathers
information from ECC Database to the Storage Scope DB. (Extract, Transform and Load - ETL)
ControlCenter is made up of three layers. They can be easily thought of as data visualization,
data storage, and data collection, but are more formally called the User Interface Tier,
Infrastructure Tier, and Agents Tier.
The infrastructure is the tier responsible for data storage made up of three separate processes
(Server, Repository, and Store).
The console tier handles data presentation. The main presentation tool is the ControlCenter Java
Console, but other presentation tools are used for deeper analysis.
The agent tier is responsible for data gathering. Agents of different types monitor and manage
objects such as arrays, switches, and applications. This will be covered in more detail in the next
The Store, is the entity that writes all the agents information to the repository.
The Java console permits a complete management, but the web console is only to manage alerts.
ECC Server is the host from which all the commands are ran, and saved in to the repository.
The data collection policies maintain our repository continously updated.
The master agents are mandatory for the servers which you want to administer from control
center, they manage the other installed agents. (permit updates, patching and install/deinstall).
The host (or OS) agent, is the one that collects the host’s health and alerts and presents it to
ControlCenter. Passes information to ECC and Storage Scope.
In ESX servers, you must install master and vmware agents in order to view the LUNS mapped to
* And for every device you want to administer from ControlCenter, you will need to install an
specific set of agents (master+device specific agents) to be able to control/administer them.
(valid for switches, other storage arrays, etc.)
All the information you work with on ControlCenter, is taken from the repository, and not from
the final device. Every change made to the configuration here, is then later applied to the final
device (host, switch, storage, etc.)
** Authentication is made at OS level, an “eccadmin” account must be created for ControlCenter.
A key management server can be utilized for ControlCenter, for authentication using certificates.
If HA is desired, install ECC on
MS Cluster or SRDF/CE for
MSCS to provide redundancy
* The agents that have same
pre-requisites, can be installed
togheter, in same server.
The communication between Symmetrix and ECC is over FC, but for the rest of devices is over
Automatic Discovery: Many agents discover data objects automatically.
– Host Agents.
– Storage Agent for Symmetrix.
– Symmetrix SDM Agent.
Assisted Discovery: These agents must discover their objects by administrator action.
– Common Mapping Agent.
– Database Agent for Oracle.
– Fibre Channel Connectivity Agent.
– Storage Agents for CLARiiON, Centera, Invista, NAS, SMI, HP StorageWorks, HDS, and ESS.
– VMware Agent.
Use the Discover menu to perform Assisted Discovery.
You can use the Discover > Review Progress menu to see the results of the discovery process.
For ECC 6.1 and SAN Switches/Fabrics
with firmware 6.1 or above, the proxy
must be configured in order to allow
communications with the rest of the
Unidentified Ports in ControlCenter
ControlCenter matches WWNs to HBAs, and HBAs to switch ports automatically when:
- FCC Agent discovers switches, which report all connected WWN
- Host Agents discover HBA WWNs
This will not happen correctly when:
- Host does not have a Host Agent
- WWN from unsupported HBA, tape library, or other object is discovered
Result: Unidentified Ports in Tree Panel
- Difficult to allocate storage to host by WWN
- Difficult to report on storage utilization by WWN
Migration Manager Overview
You can use the Host Migration Manager
to manage unidentified ports in a large
SAN environment. It allows for the bulk
creation of host objects and the
association of WWNs to hosts. If you have
a list of hosts and WWNs, you can create
an input file to specify their relationships,
and then use the Migration Manager to
import all of them into ControlCenter. This
tool does not provide the same level of
detail as the manual addition of a host,
but it may be an easier option if you have
a large number of hosts to add.
*The SAN Manager license is required to use the Host Migration Manager.
To use the Host Migration Manager, prepare a file in the format shown here. A “name” and “id”
row is needed for each HBA entry. The world wide name of the HBA appears at the left of the
line before the first dot, and the related host name appears at the right after the equals sign. The
file must be named as shown here, but the utility will allow you to retrieve the file from any
folder on the Console host.
Once the file is created, launch the Host
Migration Manager from the ECC
Administration task menu. It will prompt
for the location of the file, and show a
preview of the associations it will create.
Use the preview to locate syntax errors.
You can find the hosts that it creates in
the Hosts tree. Drill down to find the HBAs
you ssociated with the hosts. Host objects
created this way have fewer details than
normal hosts of course, and they are
marked with a diamond icon to show that
they are not being actively discovered by
Menu bars, panels, and icons are used to manipulate the ControlCenter Console display. At the
top of the window is the menu bar that most window applications feature. Many of the
commands and views can be accessed from one of the menus available here.
Below the menu bar is the task bar. Clicking on any of the five tasks (Storage Management,
Monitoring, Performance Mgt, ECC Administration, Data Protection) alters the Console display to
present features tailored to that task. The menu selections on the menu bar change and quick
access icons appear on the Tool Bar to present features for that task. Pull down menus
associated with each task are used to change Target Panel views.
Alerts information is located on the far right of the task bar. The number and severity of the
current alerts is displayed here.
Clicking on the All Alerts button launches an Alerts view to display all current alerts.
The tool bar presents buttons for the six common views: Alerts, At A Glance, Properties,
Topology, Relationship, and Performance. Clicking on one of these buttons changes the Target
Panel view. Icons to the left of the view buttons can be used for printing, print preview,
exporting the Target Panel data to a file, and launching ControlCenter help. Quick access
icons to the right of the view buttons are used for common tasks.
At the bottom of the display are two text areas that display hints to guide a user through an
operation (“Right click for popup menu”) and status information about ControlCenter objects.
Also located on the bottom of the display are icons that launch the At A Glance View, the
Consoles (At A Glance) View, and the Agents view. Holding the mouse over each of these icons
provides a quick summary about the number of users logged in, number and severity of alerts,
and number of active agents.
The most common ways to manage the display of objects from the Tree Panel in Target Panel
- Drag the object from the Tree Panel to the desired view in the Target Panel. Large numbers of
objects can be added by dragging the folder that contains them. If an object cannot be
displayed in the view, an explanation will appear in the Hint Area.
- Check the box to the left of the object or folder in the Tree Panel. Un-checking the box
selectively deletes objects from the view.
- Right-click the object and use the Add to View menu option. Use the sub-menu to select one of
the current views to add the object. Other options on this menu such as Properties and Alerts
also add information about the object to an existing or new Target Panel view.
- The eraser icon at a view’s title bar can be used to remove all of the objects from that view.
Multiple Tree and Target Panels can be created using the horizontal and vertical split pane
buttons on the upper right of each panel. The delete pane button (“X”) next to them can be
used to delete an unwanted panel. At least one Target and Tree Panel must remain on the
Console display—the last one of each can not be deleted.
You can create groups of managed objects to simplify your ControlCenter monitoring and
management tasks. You can easily add the objects in the group to one of the views by just
selecting the group in the panel. This makes it easy to limit your views to a single department or
line of business.
These groups also appear in the StorageScope and Performance Manager tool. You can use these
groups to create storage allocation reports or performance graphs related to the objects in the
When a view is filtered, the filter icon at the top will be blue. If you are not seeing the objects
you expect, make sure the view is not being filtered.
A Properties view shows tabular information about objects. Different values are displayed for
different types of objects. The example above displays information regarding the entire
Symmetrix, its front end directors and its back end directors. By selecting individual arrays, you
can find such things as Symmetrix serial Number, Model number, configured capacity, un-
configured capacity, the amount of devices that are standard or BCV, and much more.
By selecting front end fibre ports you can see whether the ports are online or offline, how many
ports are managed by the processor, and how many devices are mapped to the director. The disc
Director properties is similar to the front end with the addition of not only how many physical
disks are mapped, but also how many hyper volumes reside on those disks.
The Last Discovered and the Last Modified columns are the last columns in the properties view
for many objects. The Last Modified column updates whenever information on the row changes.
For example, the Last Modified column time will change if the physical capacity of the array
changes or the alert severity changes. The Last Discovered column shows the time the object
was discovered by an agent within ControlCenter. There is a specific data collection policy for
each object type (i.e. Hosts, switches, and arrays) that runs and updates the Last Discovered
column. For example, the Configuration policy schedule causes the Storage Agent for Symmetrix
to read the configuration of the array at regular intervals.
Since the policies discover whole objects, the Last Discovered time is only available for top-level
objects like arrays, hosts, and switches. Symmetrix Fibre Channel Directors and Back End
Directors don’t have a Last Discovered column, for instance.
In short, by using the Properties view, you can gather basic information about any object within
a Symmetrix, all the way from a single device to the whole array.
Sub-objects are organized into different folders under the main object of the Tree Panel.
Symmetrix devices are divided into Mapped, Unmapped, and System folders. Within each folder
are subfolders that you can organize by type, name, or size. Open a folder to show the devices.
On the left, we can see Disk Directors (Disk-
Fibre) or Back end, and SRDF reserved ports,
with their corresponding devices.
On the right, you can see the devices types, such
as NP=unprotected, R5=RAID5, M1 & M2
But also, there is another way to recognize their
type: With shadow=BCV ; Pink=R5 ;
Another very good view for examining device characteristics is the TimeFinder view. This view,
opened by selecting TimeFinder under the Data Protection task drop down list, displays selected
devices based on their TimeFinder relationships to other devices. This view can be used for
performing research as part of architecting a TimeFinder solution as well as executing and
monitoring relationships in a production environment.
TimeFinder Architecting - Part of architecting TimeFinder solutions is identifying devices that are
available to be used. By selecting the BCV container of a Symmetrix and adding it to the
TimeFinder view window, you can very quickly identify those devices that are available by sorting
the BCV column and looking for devices that are not paired with a standard device. You can
easily populate device groups by dragging devices from the TimeFinder view into groups in the
tree panel. You can then confirm changes once the solution has been implemented by examining
Device group membership and standard-BCV partnering in the view window.
Execution and monitoring – Whether you use the Console or scripts to execute TimeFinder tasks,
the TimeFinder view can be an invaluable tool when managing these operations. From an
execution standpoint, you can quickly select, sort and identify those devices that you would like
to work with, perform pre-operation checks such as invalid track counts and pair states, and then
execute commands all from within the view window. From a monitoring perspective, you can
keep track of operation progress because the view is updated in real time. You can monitor
changes in state, track table merging processes, MB out of sync numbers, and even estimated
time to completion.
There is a similar SRDF view for remote replication monitoring.
ß Thse are physical disks, containing hypers.
ß Thse are physical disks, containing hypers.
ß Thse are physical disks, containing hypers.
The Visual Storage view is accessed from the Storage Allocation task pull-down.
The Visual Storage view shows a logical and physical configuration of Symmetrix, CLARiiON, HDS,
and HP StorageWorks storage arrays.
y The top panel of the view shows the logical arrangement of host-addressable devices. Each
host port is displayed with each of the devices mapped to the port and their LUNS (logical unit
numbers) and Symmetrix device numbers. In the illustration above, note that the #1 port of
each Symmetrix Fibre Adapter has the same devices mapped to them--two access paths to the
same devices might be used in a multi-pathed or clustered environment.
y The bottom panel of the view shows the physical arrangement of the devices. Each disk port is
displayed with the physical disks mapped to them; each disk displays the logical devices stored
on it. In the illustration, several Symmetrix Disk Adapters having two ports (C and D) are visible.
Only one physical disk is visible on each port without scrolling down, and the disks list many
y The very bottom of the view contains a mouse-over information box. Moving the mouse over
objects in the view changes this display.
In this example, the administrator has placed a Symmetrix into the Visual Storage view and then
selected a host. By selecting a host, all of the devices that that host can see are highlighted in
the view panel. This allows an administrator to very quickly identify device locations, and visually
identify resources that might be overly taxed at this time. An administrator can highlight devices
in the view panel by selecting hosts, databases, filesystem, device group, and many others.
The Performance View
within the ControlCenter
Console has the ability to
performance statistics as
well as 24 hours of
(extended to 7-days with
the Performance Manager
Here you can see the hypers on the disks, and the marked hypers in which disk are standing by.
500601=Clariion ; 500604=Symm
The Topology View displays the physical layout of the environment in a pictorial rendering of the
SAN. You can build this view by selecting objects in the tree panel with Topology view open and
active. Hosts, connectivity devices, storage containers, adapters, ports, links, fabrics, user-
defined objects, user-defined groups, zone members, and zone set members can be displayed in
the map. With Topology view open and in focus, tree-selected objects, plus the objects to which
they are connected, as well as the connectivity relationships among them, are displayed in the
The Path Details view shows which paths exist (the mapping, or I/O path) between a host device
and a storage logical volume across a storage area network. The information in the Path Details
correlates data received from host, SAN, and array agents. You can use this view to examine the
host device to logical volume mapping and resolve unmapped device paths. Only ports and
fabrics that have viable connectivity will appear in the Path Details view.
Path Details view has three panes. The top pane is a selection area used to filter the objects
Click on one (only) object from each of the drill down boxes that appear in the selection area and
then hit Show Devices to display the corresponding devices.
The Relationship view is one of the most powerful views available in ControlCenter. This view is a
visual display of the relationship between host storage structures (databases, file systems,
volume groups), and their logical and physical locations in the storage arrays. It can be used for
storage allocation planning by helping identify current storage layout, performance analysis by
identifying devices to graph, business continuance activities to help identify STD or R1 devices,
and a myriad of other administrative tasks.
A Relationship option appears on the context-sensitive menu that appears when a user right-
clicks on the object (objects that do not provide Relationship view information do not have this
option). Under the Relationship option are a number of choices which parallel the information on
the full Relationship view. Choosing one of the sub-choices brings up a properties-like dialog that
lists the related information.
Storage Device Masking functions as a component of the EMC ControlCenter storage
management suite of tools and controls the masking policies of hosts and host ports to volumes
in the SAN. It operates in Fibre Channel switched fabric or hub environments and has
compatibility with a broad array of hardware and software platforms using Fibre Channel host
The Masking view can be used to identify those devices that have been masked to a host. This
view can be launched from within the Storage Allocation list in the Task Bar. Select one or more
hosts in the Tree Panel to display in the view and then make these selections as numbered in the
1. Storage type: Choose the type of array storage to display. Currently only Symmetrix and
StorageWorks arrays are supported in this view. Storage from other array types are masked and
monitored from other views.
2. Storage array: Choose the array. Since you dragged one or more hosts to populate this view,
only the arrays that have storage masked to that host or hosts will be available.
3. Storage port: Choose the port. Again, only ports supporting devices masked to the hosts you
dragged will be available here.
4. Device Filter Options: Choose filters to limit the devices displayed. You can show devices for
which the host has or does not have access rights, devices masked to your selected hosts or to
all hosts on this port, or devices that are or are not reserved.
5. Click Show Devices to display the selection in the display pane at the bottom.
The devices displayed are the ones masked to your host or hosts that meet the options you
The device icons show the type of device and whether it is single (line to left below the device)
or multi-pathed (line to left nd right below the device). The background color shows that access
Data is updated in real-
time, and color-coded
according to perf alert
severity. The metrics
can be displayed in
table or chart form. It is
important to note that
this view is not intended
to be the primary tool
for perf troubleshooting.
Manager application is a
far more powerful tool
for detailed perf analysis
Host Support for ControlCenter
The following hosts are supported by ControlCenter
* Dedicated Host agents
– Microsoft Windows
– Hewlett-Packard HP-UX
– IBM AIX
– IBM MVS
– Sun Solaris
* Proxy management via Common Mapping Agent (CMA)
– Compaq Tru64, OpenVMS
– Fujitsu-Siemens BS2000
– IBM OS/400
– Windows, Solaris, AIX, Linux, and HP-UX host monitoring capability.
* Hosts supported through assisted discovery
– VMware ESX Servers
For specific OS levels see the ControlCenter Support Matrix.
A few other hosts can be managed by proxy using the Common Mapping Agent (CMA). The
Common Mapping Agent always resides on a different host and manages by proxy over the
The Common Mapping Agent can also manage several types of dedicated agent hosts by proxy.
This is sometimes useful because it allows management without installing agent software on the
However, only limited functionality is available and the Solutions Enabler component Symapi
Server must be running on the target host.
Server Virtualization Support
* VMware ESX Servers can be discovered and monitored using ControlCenter.
* VMware agent supported on physical Windows platforms.
* ControlCenter views show ESX and guest OS information.
– Path Details
– Free Space
* Storage is provisioned to ESX HBAs then to VM guests through the VMware ESX server user
Server virtualization is becoming widely adopted by businesses to cut costs on physical server
spending without compromising resources and performance. Many virtual machines can be
monitored from one simple user interface and resources can be proportioned out on a per OS
basis. As stated previously, ControlCenter provides server virtualization support for VMware ESX
Servers. They can be discovered and monitored using the ControlCenter console interface. The
VMware agent is supported only on Windows physical platforms. Once installed and running, the
VMware agent provides users and administrators with a number of views showing information
about ESX Servers and their guest VMs.
Properties – Hosts
In the example above, we can
see that by selecting whole
hosts, you can see inventory
type information such as host
name, operating system, OS
levels and version numbers, #
or CPUs amount of installed
RAM, and even the time zone
configured. Selecting devices
displays device naming, array
dev numbers, size, and
utilization information (and
more). You can even select
individual hardware components
like HBAs in order to determine
drive and firmware information.
Much can be found using this
view as a research aid.
Properties – Oracle Database
Database and Backup
Support for ControlCenter
The following databases are
supported by ControlCenter
* Dedicated database agent
* Proxy management via
Common Mapping Agent (CMA)
– SQL Server
* Dedicated backup agent
– EMC EDM
– IBM Tivoli
– Legato Networker
– Veritas Netbackup
For specific database versions see the ControlCenter Support Matrix
Although reporting of total database capacity is supported for all databases supported by the
Common Mapping Agent (CMA):
* Used capacity for Oracle databases is tablespace used capacity. For Sybase databases, used
capacity is used database capacity.
* For Sybase databases, the Common Mapping Agent collects total and used data and database
capacity. For all other supported database types, the Common Mapping Agent collects total data
and database capacity and assumes that used capacity is the same as the total.
Here we can see the relationship within hosts and storage devices, with all the media in between
Also, in the second image, we can see under visual storage, that, selecting a Disk Director, or a
Hyper in it, where it resides, in which physical disks, in the below portion of the image.
At a glance view (showing all)
Web Console – Login
Web Console Views
The Web Console has several views that contain the same information as their Java Console
counterparts, though it is displayed in a different way. You can see that the application removes
the normal browser’s menu bar and management buttons, so you have to use the tool’s own
links to do things like print and save. The Print button displays either the data from the tree or
the main panel in a browser page without the menus, allowing you to print the data easily. The
Export button saves the data from the tree or main panel in a file in HTML, JPG, or CSV format.
Properties View – Symmetrix Host Directors: Same as Java console.
Properties View – SAN ZoneSet: Same as Java console.
Performance View – Symmetrix: Same as Java console.
Relationship View – Host: Same as Java console.
Alerts View: The only in which can be modified data, asignin new alerts, alerts to users, etc.
Command History View – Symmetrix: System Auditory.
The ControlCenter Security Model
EMC ControlCenter’s security model is very simple and much like many others in the industry.
User accounts are created within the ControlCenter Console. Users are then placed into groups
for easier administration, monitoring, and reporting. Authorization rules are then created which
define a set of objects and the rights that this rule grants to those objects. Lastly, groups are
associated to the rules, effectively granting users within that group the permissions defined by
the Authorization rule.
* ControlCenter User account logins are validated using the data center’s underlying security
* eccadmin user must be a valid Local or LDAP user on the ControlCenter Server host. All other
users can be associated to one of three types of host user accounts:
– Local Windows user account created on the ControlCenter Server.
– Windows domain user account.
– User account in LDAP directory.
* ControlCenter login uses Secure Socket Layer (SSL) to encrypt login and password information
between the ControlCenter Console and Server.
When installing ControlCenter, you need to specify which method of user validation is to be used:
LDAP or Windows Domain authentication. This can be changed later, but you cannot use both
types at the same time.
It is important to note that all user and password information is encrypted using Secure Sockets
Layer (SSL) between Console and Server hosts in order to protect the security of that
ControlCenter Authorization Rules
* Rules grant permissions to a single user or groups of users.
* Permissions determine what actions a user or group may perform on a given object or user-
* The “Any User Rule” is applied to newly created ControlCenter users and allows monitoring only
* To make any management changes the user must be added to a group or an authorization rule
must be assigned to the individual.
* Only one Rule can be applied to a ControlCenter User or User Group.
* Users can be members of multiple Groups.
ControlCenter User Groups
“The symcli does not have special permissions, as to deny the chance to run symcli commands
with an unathorized user. One option would be to use Symmetrix ACL Flag to provide a group
with SRDF commands for example.”
– Controlling the administrators that configure the storage environment is a critical part of
automated networked storage security. Controlling administrators’ actions requires enforcing
general security rules:
. Each administrator should have an individual account; there should be no shared accounts.
. Strong password policies for administrators should be enforced; passwords should be complex
and regularly changed.
. Administrators should only be authorized to perform management actions that are required to
perform their job.
. Administrator actions should be audited.
– Groups should be designed to reflect a particular job description or task.
– Rules should be written most restrictively, to reflect the access rights required by the groups
that will be associated to it (e.g., Payroll Backup Group - TimeFinder).
To create a new authorization rule, right-click on Authorization Rules and choose New from the
Type a name for the rule at the top. If you are associating this rule with a group, it will make
your administration easier if you give the rule a similar name. Then choose the user or group to
associate the rule with from the top part of the dialog.
Choose the actions or privileges to associate with this rule in the bottom of the dialog. Start by
choosing to organize the actions by Groups/Instances or Types. Choosing Types (illustrated here)
lets you actions that will apply across all objects of that type. Choosing an action related to
Symmetrix arrays will give the users power over all arrays, for instance. Choose an object type
first, and then one or more of the available actions next. You can repeat this process to add any
number of actions to your rule.
Add New User
Add User to User Group
New Authorization Rule By Type
New Authorization Rule By Group/Instances
* Groups can exist only in ControlCenter, there is no need for groups to exist in Local or LDAP
Data Collection Policies (DCP)
* Formal set of statements used to manage the data collected by ControlCenter agents.
* Policies specify the data to collect and the frequency of collection.
* ControlCenter agents have predefined collection policies and collection policy templates.
– Policy Definitions
– Policy Templates
* Managing Data Collection Policies:
– Edit or Copy existing Data Collection Policies.
– Create new Data Collection Policies from the template.
– Delete Data Collection Policies.
– View Data Collection Policies that apply to various managed objects.
– Stagger start times to help distribute work load.
By default, many generic policies are configured, but they tend to be broad in their scope so as
to gather as much data as possible and populate the Repository so that ControlCenter can be
quickly incorporated into business processes. It may be necessary to create new policies in order
to set your discoveries based on priority. For example, say you have ten Windows 2000 servers.
Four of them are mission critical database servers that you want monitored every six hours and
six of them are corporate file servers that you only need updated once a day. Because the
default policy includes all Windows 2000 servers, it is necessary to edit the default policy as well
as add a second policy in order to cover the two separate business needs. Refer to the
ControlCenter Performance and Scalability Guidelines document (available on Powerlink) for
details of the recommended number of managed objects to be managed by a single Data
Collection Policy definition.
Data Collection Policies can be managed from within the AdministrationData Collection Policies
folder. There are two subfolders that are used depending on whether you are creating new
policies from scratch or managing existing policies.
DCP Policy Definitions/Policy Templates
Managing the Data Collection Policies consists of:
* Assigning Data Collection Policies —Each agent is assigned a set of pre-defined policies and a
set of policy templates. You can define new data collection policies from a pre-defined policy or
from a policy template.
* Editing Data Collection Policies—You can edit all settings for an existing data collection policy;
however, you can only edit the schedule and properties defined by the data collection policy
* Copying Data Collection Policies —Use the copy policy function when you want to have more
than one data collection policy with similar settings.
* Deleting Data Collection Policies —You can only delete policies in the Policies Definitions
branch of the Administration tree. Data collection policy templates cannot be deleted.
* Viewing Data Collection Policies —You can create a tabular view of specific data collection
policies and template settings.
Editing an Existing Data Collection Policy:
* Right-click to: – delete
– edit – add/remove object
– copy – disable/enable
Editing an Existing Data Collection Policy
Editing an Existing Data Collection Policy
You can use schedules to specify the times ControlCenter should evaluate alerts and run data
collection policies to collect statistics. The properties appear on two tabs: Properties and
Alerts/Policies (this tab appears only if the schedule is used by alerts or data collection policies).
Alert or data collection policy schedules define when ControlCenter should evaluate alerts and
collect statistics through a data collection policy. In a schedule, you can define the interval at
which an event occurs (every 10 seconds, minutes, hours, and so on), the days of the week, and
the days of the year.
ControlCenter provides several pre-defined schedules and you can define additional ones. Users
are no longer able to delete or edit existing default/pre-defined schedules. Users and
administrators must right click on the schedule and select Copy As. The copy of the default policy
must then be given a new name and when then editing is complete, the new policy name shows
up in the tree panel on the left.
Schedules – Continued
Creating a New
Policy from a
Creating a New
Policy from a
ControlCenter makes it very easy to monitor configured policies through the use of the Policies
View window. If you drag an object to this view, it will show all of the policies applied to it. You
can determine the frequency with which they discover information, the last time the policy
executed, the host that the managed agent is running on, among others.
To populate the Policy View, do the following:
* Click on the ECC Administration Taskbar and open the drop-down list.
* Select the Policies View (the active view window is now a Policies View).
* Next select the object whose policies you want to look at from the tree panel and add them to
the View window.
Beyond monitoring your policies, the Views window can also be used for numerous management
tasks such as enabling/disabling the policy, deleting, editing, and the like. The next time that the
agent is scheduled to poll, the source for data is displayed in the Next collection column. By
selecting refresh (shown here), the view is updated with the time and date of the next collection.
It is important to understand that though Policy Definitions are configured and maintained in the
Repository, a copy of the policy is pushed out to the Agent itself, and it is executed
independently at the host level.
* The “WLA” policies set are for perfomance gathering.
Data Collection Policy Considerations
When adding new hosts:
* Create Discovery DCPs for each one-hour time slot within the window.
* Distribute hosts evenly among the one-hour time slots.
* Mix large, medium, and small hosts (as defined by the number of Host Devices) in each time
Schedule daily collections during an off-peak window whenever possible; especially host
The Command History view shows all of the actions that users have taken through the
ControlCenter Console. You will see administrative tasks such as adding a new user, adding a
user to the Administrators group, or editing data collection policies. You will see object
management tasks also, such as editing a zone set, creating new array devices, or discovering a
Command History View
The Command History view shows all of the actions that users have taken through the
ControlCenter Console. You will see administrative tasks such as adding a new user, adding a
user to the Administrators group, or editing data collection policies. You will see object
management tasks also, such as editing a zone set, creating new array devices, or discovering a
The display shows the name of the action, the status the object it was executed on, the user who
executed it, and the time. If all of your users are logging in as different users—not using the
common eccadmin account—this will accurately show you every change that they make through
Command History Data Retention
Log Collection Wizard
* Log Collection Wizard collects log data about managed objects in the ControlCenter
* Two versions of the software allows for seamless collaboration between customers and
The Log Collection Wizard (LCW) is a graphical user interface that also collects log data about
managed objects in the ControlCenter environment. It is installed automatically on the
ControlCenter Server host. You can launch it using the desktop icon.
The version installed with your ControlCenter environment is a full-featured version that interacts
with your software. EMC customer service representatives have an internal version of the
software that can be run independently of any ControlCenter software. The internal version can
be used to demo the product to customers or to create instruction files that customers can load
in to their Log Collection Wizards.
Log Collection Wizard Communication
* Communicates with Master Agents in the environment to collect log files.
* Automatically installed with ControlCenter Server.
Log Collection Wizard User Interface
* Users create new or use existing instruction
xml files to filter log data based on log types, file
name, or host.
* Send zipped log file collection to EMC FTP
* Attach important files to zipped log file
collection results for additional troubleshooting
The Log Collection Wizard communicates with Master Agents in the environment to collect log
The Wizard is automatically installed on the host with the ControlCenter Server during the initial
ControlCenter implementation. The user operating the Wizard makes selections based on the
types of log data to be collected, the commands are sent to the Master Agents on the hosts that
contain the managed object agent, the logs are collected, and then zipped into a log file archive
on the ControlCenter Server host.
Symmetrix Configuration Overview
* Symmetrix configuration is a component of the ControlCenter Symmetrix Manager
* More than one tool can configure a Symmetrix:
– ControlCenter Console
– Solutions Enabler, or SYMCLI
– Symmetrix Management Console
. EMC ControlCenter Symmetrix Agent
. Solutions Enabler installed on agent host
. Symmetrix Manager License
– Solutions Enabler or Symmetrix Management Console
. Configuration capability has been available since Solutions Enabler 4.1
. Configuration Manager License
. Symmetrix Management Console License if using GUI
The Configuration changes allowed in the ControlCenter Console are listed above. Each of
these configuration changes is considered a Change Class. We will look at each of these change
classes in more detail during the course of this lesson.
* Logical Device – Create and Delete Symmetrix Devices.
* Meta Device Configuration – Create/Dissolve Symmetrix Meta Volumes.
* Device Mapping (SDR or Symmetrix Device Reallocation) – Map Symmetrix Devices to Front
* Device Type Definition – Convert device types: Standard, Business Continuance Volumes
(BCVs), or Dynamic Reallocation Volumes (DRVs).
* Device Attribute Definition – Give Symmetrix devices the Dynamic RDF or Double Checksum
* Device Protection Definition – Add a mirror to an unprotected device or drop a mirror from a 2-
way mirrored device.
* SRDF Device Definition – Create static SRDF Device pair definitions from existing Symmetrix
* Port Flag Settings - Modify SCSI or Fibre Channel front-end director flags.
* Symmetrix Attributes – Change global Symmetrix attributes such as maximum number of
hypers per disk, the RAID type to enable, SRDF settings, and others.
* Save Pool – Create and Populate Save Pools.
* SRDF/A Attributes – Change the SRDF/A checkpoint frequency, cache size, and other factors
The Command Line interface also allows the following configuration changes.
* Enable/Disable Dynamic RDF - If enabled the Dynamic RDF attribute can be set on non-RDF
* Enable/Disable FBA multi access cache - Must be enabled to create Celerra FBA devices.
* Restrict access to the VCMDB device - If enabled, you deny database access to all hosts except
those whose HBAs have been masked to the VCMDB device. Device masking could then be
performed only by those select hosts.
* Change device emulation - Change allowed between FBA emulations types only.
* Reserve physical disks as dynamic spares - Disks with no hypers must be available. Dynamic
spare is invoked against a failed disk.
Symmetrix Configuration Process
* Configuration change requests are sent from the ControlCenter Console to the primary Storage
Agent for Symmetrix.
* Symmetrix Agent sends the change requests to the Symmetrix via Solutions Enabler API over
the SCSI/FC interface.
* The steps in a configuration change session are as follows:
– Submit – Commit
– Validate – Database Refresh
* Configuration change sessions cannot be aborted via the ControlCenter Console.
Accessing Symmetrix Configuration Options
Symmetrix Configuration is part of the Storage Allocation task set in ControlCenter. Symmetrix
configuration options can be accessed one of three ways:
* Select Storage Allocation from the task bar. Highlight the Symmetrix which you intend to
reconfigure. From the menu bar choose Configure> Symmetrix.
* Select Storage Allocation from the task bar. Highlight the Symmetrix which you intend to
reconfigure. Short cut icons are available for SDR and Meta Device Configuration.
* Right-click on the Symmetrix which you intend to reconfigure. From the menu choose
Symmetrix Management Console Context Launch
Some ControlCenter Configuration Commands handled by SMC
You can group tasks (if
they are the same kind
of tasks) to improve
time, as things easy as
could take several
minutes if many.
Remember that at this
time, the symm will be
Symmetrix Configuration Considerations:
* Configuration changes should be performed by advanced users.
* Planning is key.
– Determine requirements.
– Understand the proposed reconfiguration prior to change.
– Ensure that critical data is safely preserved.
* If possible, stop I/O activity on all Symmetrix devices to be altered prior to commit.
* Determine if the configuration change requires devices to be unmapped.
* Ensure SCSI timeouts are set according to Host Connectivity Guide.
Solutions Enabler has a command that verifies that a configuration change can be performed
on the Symmetrix Unit:
* symconfigure verify –sid # > Command verifies that all requirements for the host and
Symmetrix are correct. Such a verification cannot be performed from the ControlCenter Console.
Configuration Log and Lock
SYMAPI Log: A record of all the SYMAPI calls (Issued via SYMCLI or via ControlCenter) is kept
in the SYMAPI Log files. The SYMAPI log file (symapi-yyyymmdd.log) is typically found in the
/var/symapi/log directory in a UNIX environment, or under C:Program FilesEMCSYMAPIlog in
a Windows environment. As indicated earlier configuration changes initiated via the
ControlCenter Console are directed to the Primary Symmetrix Agent which in turn initiates
SYMAPI (Solutions Enabler) calls. The configuration related SYMAPI calls are recorded in the
SYMAPI log file on the Host where the Primary Symmetrix is running. The information in the
SYMAPI log files is useful during troubleshooting. The primary Symmetrix Agent for a given array
is easily determined via the tabular Agents view.
Configuration Lock: The Symmetrix configuration lock is acquired and held for the duration of
a Configuration Session in order to prevent simultaneous configuration changes. The Symmetrix
Lock Number “15” is the Configuration Lock. A configuration change cannot be initiated if the
lock is unavailable. The Failure to acquire the lock will result in a popup error message in the
ControlCenter Console and is also recorded in the SYMAPI log file.
Using SYMCLI one can release the Configuration Lock via symcfg –lockn 15 release [-force].
This should be done with extreme caution. Please call the EMC Support for help in a such a
Symmetrix Optimizer uses the same configuration change mechanism to perform swaps of hyper
Symmetrix Optimizer needs to acquire the Configuration Lock as well when it is performing a
Swap operation. If a Swap operation is in progress, a configuration change cannot be initiated
and vice versa. While planning a configuration change ensure that there are no conflicts with
Symmetrix Optimizer. Symmetrix Optimizer can be disabled if necessary.
Identifying the Primary Agent
When changing the symm
configuration, there is no
versioning, so the only
way to recover it, would
be by hand.
Logical Device Configuration
* Select these parameters
– Number of devices
– Device emulation – FBA only (open systems)
– Device configuration (protection)
– SAVE Device?
– Free (unconfigured) space must be available on physical disks with less
than the maximum
allowed number of hyper volumes
– A Valid SSID (sub-system identifier) must be assigned to the new
devices if the Symmetrix
serves both open systems and mainframe
– Devices can be destroyed via ControlCenter only for DMX Symmetrix
To create new devices, launch the Logical Device Configuration dialog from the Configure menu.
ControlCenter tries to acquire the lock on the Symmetrix. Once the lock is acquired, a warning
message is displayed. In order to successfully create new devices, all the devices on the
Symmetrix (excluding Virtual Devices) must be in a Ready state. If a device in not in a Ready
state, chances are that there are some problems with the Symmetrix and thus a Configuration
Change will not be allowed. Click OK to continue with the Logical Device Configuration process.
The Logical Device Configuration input screen is displayed.
Viewing Unconfigured Space
The Logical Device Configuration input window allows you to build a list of devices that you
would like to configure.
Choose the number of volumes to create. ControlCenter only allows you to create FBA Devices.
You can specify the size in MB or Cylinders. The drop down list shows you the device sizes that
already exist on the Symmetrix. The recommendation is to choose the size from the drop down
list, but you can enter a different size.
Choose the Configuration (Protection Type) from the drop down list.
If the devices being configured are to be used as SAVE devices, select ‘Yes’ in the SAVE device
Type option. If the Symmetrix model doesn’t support SAVE devices then the SAVE device type
option is not shown on the dialog.
Click Add to create an entry in the Requested Configuration table. You can change the
parameters and click Add again to build a list of different device types. Click Execute to submit
the configuration change.
– Result à
New devices will be in the Unmapped Devices folder
The Configuration session initiated via the Console goes through a number of steps described
earlier in the lesson.
* Submit * Prepare
* Validate * Commit
After the Commit is finished, the Configuration Lock on the Symmetrix is released and then
ControlCenter initiates a Database refresh to update the ControlCenter Repository with the most
up-to-date information about the Symmetrix.
Meta Device Configuration. ControlCenter allows the following:
* Concatenated Meta Volumes: * Start removal from the tail member
– Create or Dissolve * Striped Meta Volumes:
– Add members – Create or Dissolve
– Remove members – Add member
* Must have an identical Meta-BCV available on the Symmetrix to successfully add a member to a
striped meta while preserving data.
* Only supported on certain microcode levels – Consult EMC in advance.
* EMC Recommends adding all members in the same session rather than adding more
– Remove members are Not allowed
– Stripe width:
* EMC recommends using a two (2) cylinder (960 KB) stripe width.
* In a DMX Symmetrix, the stripe width is preset at two (2) cylinder (960 KB).
You can remove members [dissolve] (always last member) of a concatenated meta. But you
must defrag it before, in order to be sure that the data is not standing on it.
When dealing with metas, always the meta ID is the meta head ID.
Meta Device Configuration – Considerations
* All member devices must have the same type of:
– Emulation (FBA only)
– Attribute (BCV or Standard)
* Devices must be unmapped before they can be formed as members of a meta.
* Changes to the attribute of a meta are done by changing the attribute of the meta head.
* Only the meta head is mapped to a front end port.
Meta Performance Considerations
– Largest capacity supported without RPQ – 1.1 TB.
– Largest capacity possible – 16 TB.
* Number of Members:
– Largest number possible – 255.
– Largest number tested by Performance Group – 48.
– EMC generally recommends creating smaller meta volumes rather than very large meta
* Meta volumes with four, eight and sixteen members are preferred.
* Choice of members:
– Member count even divisor or multiple of Disk Director count.
– Spread members evenly across DA ports and processors.
– Avoid members on the same physical disk.
– RAID-S/Parity RAID – Choose members from different RAID groups.
Display Disk Location of Unmapped Devices
Before creating a Meta device, it is a good idea to look at the back-end locations of the devices
that you intend to use as meta members. Ensure that the devices do not share the same physical
disks and that they are spread as evenly as possible across Disk Directors and ports. It is
especially important to make sure the devices do not share the same disk if you are creating a
striped Meta, since you will lose the effectiveness of striping the data to multiple physical drives.
The Visual storage view (Change the Target Panel to Visual Storage – Storage Allocation pull
down) of the unmapped devices show you the back-end locations as shown in the slide.
Creating Meta Volumes
Device Mapping (Symmetrix Device Reallocation)
* ControlCenter allows the following:
– Mapping and unmapping of open system devices to Fibre Channel (FA) or SCSI (SA) ports only.
– Move/Copy devices between front-end director ports.
– Modify/Specify SCSI Target ID/LUN assignments.
– Unprotected standard devices cannot be mapped.
* Unprotected BCVs can be mapped.
* Unprotected gatekeeper devices (smaller than 20 cylinders) can be mapped.
– Determine the front-end director port to which the host is attached.
* Devices should be mapped to more than one port in multipath and clustered environments.
– Ensure that the selected Target ID and LUN is appropriate for the host.
– Reconfigure the host to enable it to recognize the new device.
Remember that after adding devices to a port or changing their LUN numbers, you may also
need to execute some OS-specific commands to get the host to recognize the new devices.
Device Mapping via the Command Line interface provides these additional features as well:
* Open Systems or Mainframe (FBA and CKD)
* Specify Virtual bus (vbus) address if volume set addressing is used in HP-UX
* Specify CKD device number - OS/390 host
* Update VCMDB with WWN of HBA to allow access to device being mapped.
Determine Array Port
Copy Device to Another Port
You frequently want to map the same device to more than one array port to create redundant
Use the copy feature of the SDR dialog for this purpose. Locate the device under the Host
Directors part of the tree on the left panel—remember, it is already mapped to at least one port.
Then click the additional port you would like to copy the device to in the right panel and click
The same device can be copied to any number of ports by repeating this procedure.
Change Device Address
You should always check the device address, or LUN number, before committing your changes.
Many hosts have restrictions regarding these numbers. Gaps in the numbering is frequently
disallowed. You can find the automatically assigned address with the device itself in the right
panel under the Host Directors part of the tree. Just click the number to change it.
Execute SDR: Once you have made the changes in the dialog, click Continue to review. You
can make several changes to the mapping configuration and then commit them in one event. If
everything looks good, click Execute to begin the configuration change. Most changes do take
some time, as the popup alert shown here suggests. Newer arrays with faster processors
naturally take less time to execute changes.
The progress of the change is displayed in the lower part of the window.
Once the change is complete, you can use the Properties view to examine the characteristics of
the device. The detailed view shows all of the ports that the device has been mapped to.
Reconfigure Hosts After
– Solaris 2.6: disks; devlinks;
– Solaris 2.8: devfsadm
– Solaris 2.9
* HP Hosts: Execute the
following commands: ioscan
-fnC disk ; insf -e
* IBM AIX Hosts: Execute
the following command:
* Windows hosts: Add /
Hosts have to be reconfigured to recognize the new devices that are available for access.
Remember to perform LUN masking in a Fibre Channel switched environment. The commands to
reconfigure hosts are Operating System specific.
For Solaris 2.8 and higher, the devfsadm command can be used as well. In a Solaris
environment, the sd.conf file should be appropriately configured as well. A disk label might also
have to be applied with the format command. The update_drv command (available in Solaris 9
and higher) performs a dynamic reload operation on any loaded driver (such as the sd driver),
forcing it to reread the configuration file, an operation which normally would have required a
reboot in previous versions. It is very useful in a production environment where the host needs
more disks presented to it, but rebooting it is not an option.
In Topology view, you can see the hosts and their connections with Storage Systems.
Device Type and Device Attribute Definition
* Device type definition:
– Allows you to convert between Standard, BCV and DRV device definitions
* Device attribute definition:
– Allows you to give device the following attributes.
* Double Checksum
* Dynamic SRDF (R1 or R2 or Both)
* Ineligible devices will be filtered out by the Console
– Mapped devices
– System devices, Save devices, RAID-S, Parity RAID, SRDF, TDEV, VDEV, TDEV, COVD
– BCV or STD devices in a synchronized state, Meta members.
The Command Line interface allows the setting of the following additional attributes as well:
* WORM (Write Once Read Many)
* SCSI3 Persistent Reserve (For SUN Cluster 3.0 environments)
Device Type Definition
To change the device type
definition, go to the
configuration menu by any of the
methods discussed earlier and choose
Device Type Definition. After the
configuration lock is acquired, the
Device Type Definition dialog shown
above will appear. Just click on the
devices you want to change and click the BCV, DRV,
or STD buttons. Changing the device type definition
does not alter the protection of the device.
Clicking the Execute button starts the configuration
Note: To convert a device to a DRV, it must be
configured as Unprotected. A BCV cannot be
converted to a DRV directly, it must be converted to an STD first.
To change the device
attribute definition, use
the configuration menu
to launch the Device
dialog shown above.
To add or remove an
attribute, click in the
cells under the attribute
column. Light blue
colored cells indicate
Dynamic R1 and R2 can
both be assigned to the
same device if desired. If a device is capable of both
Dynamic R1 and R2, it can be either the source or target of remote synchronization. It can also
participate in an SRDF swap operation, or become a Cascaded SRDF R21 device.
* option only available to use with Oracle DBs.
Device Protection Definition
The Device Protection Definition dialog allows you to remove a mirror from a mirrored device, or
add a mirror to an unprotected device. No other protection types can be manipulated using this
When turning a mirrored device into an unprotected device, one of the mirror hypers is split off
as a new device. It has a new device number and appears in the Unmapped devices folder of
The original device type changes from 2-Way Mirror to Unprotected. The original device retaind
its data, but the new device does not.
When turning an unprotected device into a mirrored device, a new hyper is created and added as
a mirror. Enough unconfigured space must exist on the array to mirror the device. You do not
get to choose the disk to use for this, the Enginuity code determines the best location for the
hyper. You cannot just join two unprotected devices into a mirrored pair. The new mirror is
synchronized with the original device, preserving its data.
As with the other configuration commands, ineligible devices are filtered from the dialog to
prevent you from accidentally selecting the wrong thing.
Device Protection Definition Dialog
The example at the bottom of this illustration shows a BCV that has been unprotected. Each
mirror becomes an independent device, with a new device number being generated for the
Bring up the Device Protection Definition dialog to change the protection of a device. The
ControlCenter Console only shows devices on which the Device Protection changes can be made.
It filters out all RAID-5, RAID-6, and Mapped 2-Way Mirrored devices.
The pending changes are shown in blue italics. Click Execute to commit the configuration change.
SRDF Device Definition
The SRDF Device Definition configuration adds the R1 attribute to a local device and the R2
option to a remote device, making them a linked SRDF pair. This option creates static SRDF
Device pairs only.
As we have seen, the Dynamic SRDF attribute is enabled in the Device Attribute Definition dialog,
not the SRDF Device Definition dialog.
Only mirrored, RAID-5, RAID-6, or Unprotected devices can be made into static SRDF pairs. A
matched pair of eligible devices must exist on both of the arrays. Both devices match if they
have the same Meta configuration (if Metas), size, emulation (FBA or CKD), and protection. As
always, ineligible devices are filtered from the display. Additionally, the array must have SRDF
directors, be linked to the remote array, and SRDF RA groups must already have been created
(by command line).
A configuration lock has to be acquired for both arrays. You can not delete or edit a static SRDF
device pair relationship using ControlCenter.
Use any of the methods described previously to launch the SRDF Device Definition dialog. The
Select Symmetrix Screen will pop up first. Choose the Local and Remote Symmetrix from the
Drop down lists. Only those arrays in your environment that are physically connected by SRDF
links will appear here. Choose the RA Group Number from the list (cannot create a new RA
Group). Choose what SRDF type(R1 or R2) the local device will be.
-The Configuration Lock is acquired and the Warning message shown in Step 2 on the slide will
From the Select Local R1 Device Column select the device that becomes the R1. Before you pick
a device from the Select Local column, the Select Remote R2 Device column will be empty. Once
you select a device from the Select Local column, eligible devices are displayed on the Select
Remote R2 Device column. Pick a device from the Select Remote R2 Device column and click Add
to add this pairing into the Selected RDF pairs table.
When an SRDF Device Pair is created, the previously separate devices are synchronized with the
same set of data. You have the choice of invalidating (or losing) the data on either the local or
the remote device. The device that is being invalidated must be unmapped or in a Write Disabled
or Not Ready state.
Port Flag Settings
The Port Flag Settings dialog is used to change the communications protocol
settings on Symmetrix array ports.
* Change settings of SCSI or Fiber Channel Host Director ports
– Settings may have to be changed when adding hosts to existing switched configurations or for
preparing an unused port for host connectivity.
– EMC recommends that you temporarily suspend I/O activity to the affected ports when setting
front-end port attributes.
– Incorrectly changing the port flags can render your Symmetrix storage system inaccessible. Be
certain of the results of any change before resetting any of these flags.
Port Flags Settings – Host Policy
* Select the host from Host Policy list.
* Select the host director port to which the host must be added.
* Click on Add to add to the Selected list.
* Click Next.
This port flag attribute, is a bit to
change, that will allow better
communications with client
servers, like HP-UX, Windows
Cluster (MSCS), Solaris with
Veritas Volume Manager, and
other applications in operating
systems, or some specific
Another option is to use
“heterogeneous” bit setting.
When choose Port Flags Settings from the configuration menu, you see a Default Settings dialog
like the one above. You can use it to choose the standard settings for certain operating system
configurations. Just choose the policy and the port and click Add. If none of these settings suits
your needs, hit Next without making any changes here.
Port Flags Settings – Review/Manual Edit
The second part of the Port Flags Settings dialog gives you a chance to make detailed edits to
the flag settings. Every flag which is appropriate for the type of port can be edited here by
clicking in the box.
A bullet indicates the flag is set. An empty box means it is not set. Settings that can not be
edited are in gray. The two tabs choose the Fibre or SCSI flags for each port.
Delete Logical Devices
Use the Delete Logical Device configuration menu to delete one or more devices. This is one of
the few configuration menu dialogs that does not allow you to choose the devices within the
dialog. All of the devices selected on the console when the menu was launched will be deleted!
If you right-clicked on a single device to launch the dialog, only that device is deleted. If you
selected multiple devices and right-clicked, all of them are deleted. If you selected a Symmetrix
and right-clicked, all eligible devices on the array are deleted! Be especially careful with this
Set Symmetrix Attributes
Note: Different options are
available with different
versions of Enginuity.
Symmetrix Virtual Provisioning
* Increased Speed and Ease of Provisioning
* Improved Capacity Utilization
* Improved Performance
Symmetrix Virtual Provisioning allows administrators to allocate storage devices to hosts quickly
and easily. Virtual—or “thin”—devices are allocated from a common storage pool, making it easy
to provision for tiered service levels. Because the devices only consume storage when written to,
they greatly improve capacity utilization. You can initialize an application with a large amount of
virtual storage, and add more physical storage to the pool as the application grows.
Virtual provisioning can also improve the performance of applications, since the data is
automatically striped across all of the hardware in the pool.
Virtual provisioning was introduced in Enginuity 5773. Only DMX-4 or later arrays support
Virtual Provisioning Architecture
* Virtual (“thin”) Device:
– Must be bound to a Thin Pool.
– Presented to host with a fixed capacity.
– Initially, no disk storage allocated.
– Writes to virtual device stored in Thin Pool
* Data (“thin”) Pool:
– Collection of regular (non-virtual) devices.
– Virtual device writes striped across data Devices.
* Data Devices:
– Protection: RAID-1, RAID-5, RAID-6.
– All Data Devices in a pool must have the same protection.
Virtual Provisioning Storage Allocation Terminology
Managing the capacity utilization of thin devices and thin pools is an important task in
If a pool becomes completely utilized, the thin devices bound to it will not be able to allocate new
storage tracks. When this happens, writes that require new storage tracks will return a write
failure to the host. Other I/O operations will still succeed, however.
The free or available space in the pool represents all of the tracks that have not been allocated to
the thin devices. If your pool is over-subscribed, you will have to watch this measure carefully,
since you have promised more storage to the thin devices than the pool can provide.
Virtual Provisioning Devices Support:
Thin devices and data devices have a maximum size of 64 gigabytes—the same limit any devices
in a Symmetrix with this level of Enginuity have. Of course, EMC recommends a smaller, more
flexible device size. Thin devices can be mapped and masked, but data devices are never
mapped or masked to a host.
Thin devices are not protected—they depend on the protection of the devices in the data pool,
which can be RAID-1, RAID-5, or RAID-6.
Thin devices can be replicated to other thin or virtual devices, but never to a fully-provisioned
You can use TimeFinder/Snap to replicate a thin device to a Snap virtual device. You can make a
thin Clone of a thin device. Or you can use SRDF for remote replication if both the R1 and R2
devices are thin.
If a large thin device is needed, you can create a meta device of thin devices. Regular devices
and thin devices cannot be combined in the same meta.
Thin Pool Generic Alert:
A new alert has been added to
the Storage Agent for
Symmetrix to monitor the
used capacity of thin pools. It
is measuring the used capacity
against the total capacity of
the pool. The alert will trigger
at any of the thresholds
shown here, and display a
message showing the exact
utilization. Since the Solutions Enabler processes monitoring the arrays detect this event, the
alert should arrive in the Console within minutes of a change in the pool’s utilization. The alert is
enabled by default, and monitors all thin pools on the array.
Virtual Provisioning Properties Views
Thin pools are
displayed as a data
device in a blue
rectangle. Thin Pool
properties show the
capacity, and free
capacity of the pool.
capacity is labeled
Capacity Allocated” in
Virtual Provisioning Free Space View
summary graph now
showing the Thin
Pool Available, Thin
Pool Used, and pool
The sum of all of the
in this bar graph
except for the Over
of the array.
Thin Provisioning Implementation Steps
1. Create Data Devices (SMC)
2. Create Thin Pool, populate with Data Devices, enable Data Devices (SMC)
3. Create Thin Device, bind to Thin Pool (SMC)
4. Map, Mask Thin Device as normal (ControlCenter or SMC)
Create Data Devices
To create data devices, right-click on the array and
choose Device Configuration > Create Device
(SMC) from the menu.
This will launch the Symmetrix Management Console
dialog for creating devices.
Choose the Data Device tab
for thin pool devices.
The Save Device tab is for
TimeFinder/Snap or SRDF
Delta Set Extension devices.
Commit Configuration Changes
Device creation tasks require a configuration change. When you confirm a Symmetrix
Management Console operation that requires a configuration change, the task will just be added
to the My Active Tasks tab of the Config Session view. After adding one or more tasks, you will
need to switch to the Config Session view and commit your tasks. The Symmetrix Management
Console does not always switch to this view automatically, so you should get in the habit of
checking here for any uncommitted changes.
Create Thin Pool
To create a thin pool,
right-click on the array
and choose the Device
Pool Management >
Pool (SMC) menu. This
menu will launch the
Console dialog for
thin pools. The Save
options in this menu are
for TimeFinder/Snap or
SRDF Delta Set
management, so avoid them if you are looking for virtual provisioning tasks.
Creating a thin pool does not require a lengthy configuration change procedure. Clicking OK
will commit the change, and post a success or failure notification. You will not have to turn to the
Config Session view after leaving this dialog.
Enable Data Devices
After creating the thin pool, you might
like to view it before leaving Symmetrix
Locate the pool under the Pools folder
under the array in the left panel of the
Console. Click on it to show the general
properties, thin devices, and data
devices. You can click on an individual
data or thin device to view its
properties in the bottom of the dialog.
If you did not choose to automatically
enable the data devices in the Create
Device dialog or in the Create Pool
dialog, you will have to enable them
manually. Click the Data Devices tab of
the pool properties display
and select all of the
devices to be enabled.
Then right-click and
choose the Device Pool
Management > Enable
Create Thin Device,
Bind to Thin Pool à
To create thin devices, right-click on the array and choose Device Configuration > Create Device
(SMC) from the menu. This will launch the Symmetrix Management Console dialog for creating
devices. Choose the Thin Device tab for thin pool devices.
Creating a thin device is a configuration change, just like any device creation. Remember to use
the Config Session dialog of Symmetrix Management Console to commit your changes.
Verify Thin Device in SMC
* Use Logical Device Configuration dialog to create new Save devices.
* Use Save Pool dialog to create new Save Pools.
* Assign Snap Save Pools to Snap sessions with Create Snap Session dialog.
* Assign DSE Save Pools to RA Groups with Set SRDF/A Configuration dialog.
Save Pools are used to record data for two Symmetrix business continuity operations. Data is
stored for TimeFinder/Snap devices in a Save Pool when a track of data differs from the source
that the Snap is replicating. Many Snap devices can use the same pool to help share the storage
resources. SRDF/A can be configured to cache writes on the local array’s Save Pool disks. This
feature is known as Delta Set Extension and it helps recover from temporary bursts of writes or
link failures. Delta Set Extension was made available with Enginuity 5772. Each of these
technologies has its own type of Save Pool.
Active SNAP sessions can cause many writes to the associated Save Pool. You might want to
create separate Save Pools to prioritize the performance characteristics. You might assign many
low priority SNAP sessions to the default pool, but assign only a few high priority sessions to a
different pool. The devices in the high priority pool will have less contention for disk resources
because there are fewer sessions competing for them.
The down side of partitioning the Save devices into different pools is that a single session can not
borrow from another pool if the present pool runs out of space. You might end up wasting disk
space if you have more than one Save Pool.
ß Creating and Editing
Deleting Save Pools
and Devices à
SRDF/A transmits data in time-consistent sets called “cycles.” The data on the remote site is
consistent as of the last completed cycle. The Set SRDF/A Attributes dialog allows you to set the
minimum cycle time from 5 to 59 seconds. Under normal circumstances, the remote site should
be updated consistently at time periods equal to the Cycle Time. However, if too many writes
arrive at the local array to be transmitted to the remote in one cycle, the cycle time temporarily
elongates to accommodate the load. Cycle writes are kept in cache. If cache fills, SRDF/A
sessions begin to drop or terminate.
** Use the SRDF/A Group Priority to prioritize the RA groups. Groups with higher priorities drop
when cache fills.
Associating an SRDF/A Delta Set Extension Pool enables this feature for the RA Group. When a
large number of writes fills cache, additional writes are written to the pool. By writing to the pool
the session does not need to be dropped, but performance will be reduced as the writes now
have to be retrieved from disk.
If the Transmit Idle feature is enabled for the RA Group, the session will not drop when all the
links between the sites fail. Instead, the local array just elongates the cycle time as it does when
an overload of writes arrives. If a Delta Set Extension pool has been assigned, the writes are
stored in the pool.
Otherwise they fill cache. Either way, when the fixed amount of space is filled, the sessions
Delta Set Extension pools and the Transmit Idle feature are available on arrays having Enginuity
5772 or higher.
Since reserved devices are omitted from ControlCenter configuration dialogs, there is no direct
way to override a reservation. However, you can use the Console to release device reservations,
and then return to the configuration dialog to modify the device.
CLARiiON Configuration via ControlCenter
* Configuration changes supported via ControlCenter Console:
– Create, Defrag and Delete RAID Groups
– Bind and Un-Bind LUNs
– Create, Expand, Destroy and Modify MetaLUNs
– Create SnapView snapshots
– LUN Masking
* Create/Delete Storage Groups.
* Add/Remove LUNs to/from Storage Groups.
* Attach hosts to a Storage Group.
– Edit Storage Processor network settings.
Accessing CLARiiON Configuration Options
New RAID Group
Bus, Enclosure and Disk number are
part of the disk name.
New RAID Group
Defragment RAID Group
Fragmentation in a RAID
Group occurs as you
unbind and rebind LUNs
on a RAID Group
performance issues by
data to multiple regions
of disk. Defragment a
RAID Group to compress
these gaps and provide
more contiguous free
space across the disks.
De-fragmenting a RAID
Group does not affect the arrangement of data within the LUNs. It is not equivalent to de-
fragmenting a filesystem mounted on a CLARiiON LUN. If no deleted LUNs, no need to defrag.
Delete RAID Group
Before you can delete a
RAID Group, you must
unbind all the LUNs and
Private LUNs (part of a
MetaLUN) on it or you get
an error as shown in this
example. Just right-click
on the RAID Group, and
choose Delete RAID group
from the Configure menu.
A LUN is a host-
addressable storage unit
created from a RAID
Group. A RAID Group can
have many LUNs, but they
all share the same
protection type. You set
the protection type with
the first LUN you bind. All
additional LUNs must be of
the same protection.
This is the equivalent than
creating a Hyper(meta) in
Expand MetaLUN ->
ß Expand MetaLUN Properties.
a Properties View of some regular and
a MetaLUN in the Console. The
MetaLUN head along with its
associated Components and Private
LUNs (LUNs that are part of a
MetaLUN) are shown.
Note that the Size column shows the
total meta capacity and the capacity of
each private LUN, but the Actual User
Capacity column has N/A for the
private LUN size. The Actual User
Capacity only shows a value for the
MetaLUN head since it is the user-accessible device.
You can select the size you want to show to the OS.
Properties of LUNs:
Modify and Destroy
You can modify some of
the parameters of a
MetaLUN by using the
Modify MetaLUN option of
the Configure menu. It is
not possible to change
the Element Size
Multiplier or Alignment
Offset when modifying a
MetaLUN. You can also
delete the MetaLUN by
using the Destroy
MetaLUN option. When
deleting a MetaLUN all
the members are
from the RAID Group)
and the data will be
The final CLARiiON
that can be
By right clicking on the array in the Tree Panel and selecting Storage Agent >
CLARiiON > Explore one can perform a variety of tasks for SnapView Snapshots.
These tasks include:
•Editing Snapshot Cache Properties.
•Exploring Snapshot Sessions.
•Exploring LUNs that a Snap session can be executed against.
•Exploring a Snapshot.
•Creating New Snapshot session.
These are the possible Snapshot management tasks available in ControlCenter. Tasks such as
activating and terminating a Snapshot session cannot be done using ControlCenter.
SAN Management Overview
* SAN Management tasks are performed via SAN Manager
– Licensed ControlCenter application with comprehensive SAN Management capabilities
– Use the ControlCenter Console to:
*Discover and display an end-to-end topology view of the SAN
*Monitor the heath and performance of the SAN
*Manage zoning operations of the switched fabrics in the SAN
*Perform storage device masking operations on storage arrays in the SAN
– Please refer to the EMC ControlCenter Support Matrix for a comprehensive list of all the
switches and storage arrays supported by SAN Manager.
ß Switched Fabric