Control Center Knowledge Share

EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. EMC Control Ce nter permits a dministration/management of the e ntire 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 s ymmetrix system. (local) SRDF permits to replicate/copy sites betwee n Symmetrix systems. (remote copy) Symmetr ix architecture (950 part icular, as A & B cards are back e nd) 16 17 0 C LOO P Each Hyper has a number, or symvol. This D 1 D D symmvol, is consecutive, so always is 0 1 C CA CH E C C better to allocate continuous hypers. D H YPE RS (E VER Y TIME A HOST S D ISKS / 0 TRIES TO W RITE, THE 0 WR ITE GOE S TO THE B C 1 LU N 000 1 CA CH E , AND THE N I S DE ST AG ED TO DIS K ) B D The rule of 17, comes from older DMX or 0 1 A A C 8000 series. Always the directors D configuration is started from highest # to the lowest (17-0) (16-1), etc. Hyper types: STD, BCV. LOO P STD: is the normal volume, and is able to 0 00 be under RAID1, 5, 6, unprotected, etc. 01 02 sy mm vo l BCV: is used by Timefinder, normall y unprotected, but it can also have R5, 6, 1, etc. For cloning, it can be done from STD to BCV, or from ST D to STD volumes. VDEV: Virtual devices used with Ti mefinder Snap. VCMDB: Only exists one VCMDB per Symmetrix system, here resides all the masking configuration of the symmetri x system. (hosts HBA WWN, switch port, symm port, etc) Can be backedup in the Contr ol Center Host. (Right click, backup VCMDB.) META: Meta devices are simply se veral 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 eas y to identify. Meta devices can be concatenated (data addressed linearly) or stripe d (data address shuffled among the mem bers). R1 & R2: SRDF V olumes, R1 is source, R2 is target device. Gatekee per (GK): utilized to send commands to S ymmetrix system. This volumes mus t be presented to any host in which the ECC / Solution Enabler will be installed. Recommended is to

have at least 4 GK Volumes alloca ted to the host via Fibre Channel. If not GK available, another hyper can be allocated to host. It normall y has 6 cylinders ( 2.88). CLARiiON architecture: Storage processors i n clariion have separa ted caches for read & writes, but not mirrored like in Symmetrix. WS 0 -X 953 ISF M GMT CONSOLE 1 M 00 0/1 T GM TUS STA SYS TE IV ACT EWR E M P RES T COM 1 C FI S ERVISOR UP WS 0 -X 953 ISF M GMT CONSOLE 1 M 00 0/1 T GM TUS STA SYS TE IV ACT EWR E M P RES T COM 1 C FI S ERVISOR UP To allocate disks from Clariio n arrays, we must create RAID Groups, when creating a RA ID Group, we must choose the type of protection you desire, but it will depend als o, on how many disks you have selected for the group. * In Clariio n, instead of Time finder, we have Snapview, and instead of SR DF, Mirror view. The SAN or Storage Area Networ k, is network of storage disks. In large enterprises, a SAN connects multiple servers to a centralize d pool of disk storage. Compared to managing hundreds of servers, eac h with their own disks, SANs improve system administration. By treating all the company's storage as a si ngle 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 wi thout 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. (Extrac t, Transform and Load - ETL)

ControlCenter is made up of three layers. T hey can be easily thought of as data visualization, data storage, a nd data collection, but are more formally called the User Interface Tier, Infrastructure Tier, and Agents Tier. The infrastructure is the tier res ponsible 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 anal ysis. The agent tier is responsible for data gathering. Agents of different types monitor and manage objects such as arra ys, switches, and applications. This will be covered in more de tail in the next lecture. The Store, is the entity that writes all the agents information to the repository. The Java console perm its a complete management, but the web console is only to manage aler ts. ECC Server is the host from which all the commands are ran, and sa ved in to the repository. The data collection policies maintain our reposi tory continously updated. The master agents are mandatory for the ser vers which you want to administer from control center, they manage the other i nstalled agents. (permit updates, patching and install/deinstall). The host (or OS) agent, is the one that collects the hos t’s health and aler ts 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 virtual hosts. * And for every device you want to administer from C ontrolCenter, you will need to install an specific se t of agents (master+device specific agents) to be able to contr ol/administer them. (valid for switches, other s torage arrays, etc.) All the information you wor k with on ControlCe nter, 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, e tc.) ** Authentication is made at OS level, an “eccadmin” account must be crea ted for ControlCenter.

A key management server can be utilized for ControlCenter, for a uthentication 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. IP ECC Server Symmetrix WIN SAN Clariion SUN AIX IBM/HP Storage The comm unication between Symmetrix and ECC is over FC, but for the rest of de vices is over IP.

Agent Discovery Automatic Discover y: Many agents discover data objects automatically. – Host Agents. – Storage Agent for Symmetrix. – Symmetrix S DM Agent. Assisted Discovery: These age nts must discover their objec ts by administrator action. – Common Mapping Age nt. – Database A gent for Oracle. – Fibre Cha nnel C onnectivity Agent. – Storage Agents for CLARiiON, Ce ntera, Invista, NAS, SMI, HP StorageW orks, 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 SA N Switches/ Fabr ics with fir mware 6.1 or above, the pro xy must be configured in order to allow communications with the rest of the SA N Switches. Unident ified Ports in ControlCenter ControlCenter ma tches WW Ns 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 w hen: - Host does not have a Host Agent - WWN from unsupported HBA, tape librar y, or other object is discovered Result: Unidentified Ports in Tree Panel - Difficult to alloca te storage to host by WW N - Difficult to report on storage utilization by WW N Migrat ion 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 WW Ns to hosts. If you have a list of hosts and WWNs, you can crea te an input file to specify their relationships, and then use the Migration Manager to import all of them into Co ntrolCe nter. This tool does not provide the same le vel 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 ad d. *The SAN Manager li cense is required to use the Host Migra tion Mana ger.

To use the Host Migra tion Mana ger, 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 a t 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 show n here, but the utility will all ow you to retrieve the file from a ny folder on the Co nsole host. Once the file is created, launch the Host Migration Manager from the ECC Administration tas k menu. It will prompt for the location of the file , and show a preview of the associa tions it will crea te. 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 wa y have fewer details than normal hosts of course, and they are marked wi th a diamond icon to show that they are not being actively discovered by an agent. Menu bars, panels, and icons are used to manipulate the Co ntrolCe nter 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 me nus a vailable here. Below the menu bar is the task bar. Clicking on any of the five tas ks (Stora ge Management, Monitoring, Performa nce Mgt, ECC Administration, Data Protection) alters the Console display to present features tailored to that tas k. T he menu selections on the menu bar c hange and quick access icons appear on the Tool Bar to present features for that tas k. Pull down menus associated with each task are used to change Target Panel views. Alerts informa tion is located on the far right of the task bar. T he number and se verity of the current aler ts 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 si x common views: Alerts, At A Glance, Properties, Topology, Relationship, and Performa nce. Clicking on one of these buttons changes the Target Panel view. Icons to the left of the view buttons can be used for printing, pri nt preview, expor ting 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 ControlCe nter o bjects. Also located on the bottom of the display are icons that launch the At A Glance View, the Consoles (A t A Glance) View, and the Age nts view. Holding the mouse over each of these icons provides a quick summar y 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 Views are: - Drag the object from the Tree Panel to the desired view in the Target Panel. Large numbers of objects can be added by dra gging the folder that contains them. If an objec t 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 a nd Aler ts 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 unwa nted 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 crea te groups of managed objects to simplify your ControlCenter monitoring and manageme nt 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 a ppear in the StorageScope and Performa nce Manager tool. You can use these groups to create storage allocation reports or performance graphs related to the objects in the group. When a view is filtered, the filter icon at the top will be blue. If you are not seei ng 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. T he example above displays information regarding the entire Symmetrix, its front end directors and its back end directors. By sele cting individual arrays, you can find such things as Symmetrix serial Number, Model number, configure d capacity, unconfigured 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 process or, 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 ma pped, 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 Las t Modified column updates whenever informa tion on the row changes. For example, the Las t Modified column time will change if the physical capacity of the arra y changes or the alert severity changes. The Last Discovere d 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 Las t Discovered column. For e xample, 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-le vel objects like arrays, hosts, and switches. Symmetrix Fibre Cha nnel Directors a nd Back End Directors don’t have a Las t Discovered column, for instance. In short, by using the Properties view, you ca n gather basic information about any object within a Symmetrix, all the wa y from a single device to the w hole array.

EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. Sub-objects are organized into different folders under the main object of the Tree Panel. Symmetrix de vices are divided into Mapped, Unmapped, and System folders. Within eac h folder are subfolders that you can organize by type, name, or size. Open a folder to show the devices. NP= unprotected On the left, we can see Disk Directors (Disk- Fibre) or Back end, and SRDF reser ved ports, with their corresponding devices. On the right, you ca n see the devices types, such as NP=unprotected, R5=RA ID5, M1 & M2 But also, there is another way to recognize their type: With shadow=BCV ; Pink=R5 ; Nothin=unprotected. R5= RAID5

Another very good view for examining device characteristics is the TimeFi nder view. This view, opened by selecting TimeFinder under the Data Protection tas k drop down list, displays selected devices based on their TimeFinder relationships to other de vices. T his view can be used for performing research as part of architecting a TimeFinder s olution 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 sel ecting the BCV c ontainer of a Symmetrix and adding it to the TimeFinder view window, you can very quickly identify those devices that are available by sor ting the BCV co lumn and looking for devices that are not paired with a standard device. You can easily populate device groups by dra gging devices from the TimeFinder view into gr oups in the tree panel. You can then confirm changes once the solution has been implemented by examining Device gr oup membership and standar d-BCV partnering in the view window. Execution and monitoring – Whether you use the Console or scripts to execute TimeFinder tasks, the TimeFi nder view can be an invaluable tool when managing these operations. From an execution standpoint, you can quickly sele ct, sort and identify those devices that you would like to work with, perform pre-opera tion checks such as invalid trac k counts a nd pair states, and then execute commands all from within the view wi ndow. 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 mergi ng processes, M B out of sync numbers, and even estimated time to completion. There is a similar SRDF view for remote replication monitoring. ß Thse are physica l dis ks, containing hypers. ß Thse are physica l dis ks, containing hypers. ß Thse are physica l dis ks, containing hypers.

The Visual Storage view is accessed from the Storage Alloca tion task pull-down. The Visual Storage view shows a logical and physical configuration of Symmetrix, CLARiiON, HDS, and HP StorageWor ks stora ge arrays. y The top panel of the view shows the logical arrangement of host-addressable devices. Each host port is displayed wi th each of the devices mapped to the port and their LUNS (logical unit numbers) and S ymmetrix device numbers. In the illus tration above, note that the #1 port of each Symmetrix Fibre Ada pter has the same devices mapped to them--two access paths to the same devices might be used in a multi-pathed or clustered envir onment. 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 Symmetri x 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 devices. 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 Vis ual Storage view and then selected a host. By sele cting a host, all of the devices that that host can see are highlighted in the view panel. This all ows 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 hos ts, databases, files ystem, device group, and many others. The Performa nce View within the ControlCenter Console has the ability to present real-time performance statistics as well as 24 hours of historical information (extended to 7-days with the Per formance Manager license key).

Here you can see the hypers on the disks, and the mar ked hypers in which disk are standing by. 500601=Clariion ; 500604=S ymm The Topology View displays the physical layout of the environment in a pictorial rendering of the SAN. You can build this view by sele cting objects in the tree panel with Topology view open and active. Hosts, connectivity devices, storage containers, adapters, por ts, links, fabrics, user- defined objec ts, user-defined groups, zone members, and zone se t members can be displayed in the ma p. 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 map.

The Path Details view shows which paths exist (the ma pping, or I/O path) between a host device and a storage logical volume across a s torage 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. T he top pane is a sele ction area used to filter the objects displayed. Click on one (only) object from ea ch 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 allo cation 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 a dministrative tas ks. A Relationship option appears on the context-sensitive menu that appears when a user ri ght- 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 bri ngs up a properties-like dialog that lists the related information. Storage Device Masking functions as a component of the EMC ControlCe nter storage manageme nt suite of tools and contr ols the masking policies of hosts and host ports to volumes in the SAN. It operates in Fibre Channel switched fabric or hub environments a nd has compatibility wi th a broad array of hardware and software platforms using Fibre C hannel host bus adapters. 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 Tas k Bar. Select one or more hosts in the Tree Panel to display in the view and then make these sele ctions as numbered in the selection pane:

1. Storage type: Choose the type of array storage to displa y. Currently only Symmetrix and StorageWorks arrays are supported in this view. Storage from other array types are mas ked and monitored from other views. 2. Storage array: Choose the arra y. Since you dragged one or more hosts to populate this view, only the arrays that have stora ge mas ked to that host or hosts will be available. 3. Storage port: Choose the port. Again, only ports supporting devices mas ked to the hosts you dragged will be available here. 4. Device Filter Options: C hoose filters to limit the devices displayed. You ca n 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 sele ction in the display pane a t the bottom. The devices dis played are the ones mas ked to your host or hosts that meet the options you chose. The device icons show the type of device and w hether 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 status. Data is updated in real- time, and color-coded according to perf aler t 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 troubles hooting. The Performa nce Manager application is a far more powerful tool for detailed perf analysis and tre nding.

Host Support for ControlCenter The followi ng hosts are supported by ControlCenter * Dedicated Host agents – Microsoft Windows – Hewlett-Packard HP-UX – IBM A IX – IBM MVS – Linux – Sun Solaris * Proxy management via C ommon Mapping Age nt (CMA) – Compaq Tru64, OpenVMS – Fujitsu-Siemens BS2000 – IBM OS/400 – Windows, Solaris, AIX, Linux, and HP-UX host monitoring capability. * Hosts supported through assiste d discover y – 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 alwa ys resides on a different host and manages by pro xy over the network. The Common Mapping Age nt can also manage several types of dedicated agent hosts by pro xy. This is sometimes use ful because it allows management without installing agent software o n the hosts. Howe ver, only limited functionality is available a nd the Solutions Enabler component Symapi Server must be running on the target host. Server Virtualizat ion Support * VMware ESX Servers can be discovered and monitored using ControlCe nter. * VMware agent supported on physical Windows platforms. * ControlCenter views s how ESX and guest OS information. – Properties – Relationship – Topology – Path Details – Free Space – Alerts – Agents * Storage is provisioned to ESX HBAs then to VM guests through the VMware ESX server user interface. Server virtualiza tion is becoming widely adopted by businesses to cut costs on physical ser ver spending wi thout compromising resources a nd performance. Many virtual machines can be monitored from one simple user interface a nd resources can be proportioned out on a per OS basis. As stated pre viously, ControlCenter provides ser ver vir tualiza tion support for VMware ESX Servers. They can be discovered and monitored using the ControlCenter console interface. T he 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 selec ting 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 selec t individual hardware c omponents 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 Bac kup Support for Contro lCenter The followi ng databases are supported by ControlCenter * Dedicated database agent – Oracle * Proxy management via Common Mapping Agent (CMA) – SQL Server – Sybase – Informix – DB2 * Dedicated backup agent – EMC EDM – IBM Tivoli – Legato Networker – Veritas Netbackup For specific database versions see the ControlCenter Support Matri x Although reporting of total database capaci ty is supported for all databases s upported by the Common Mapping Agent (CMA): * Used capaci ty for Oracle da tabases is tablespace used capacity. For Sybase databases, use d capacity is used database capacity. * For Sybase databases, the Common Mapping Agent collects total a nd used data and database capacity. For all other supported database types, the Common Mapping Agent collects total data and database capacity and ass umes that used capacity is the same as the total.

Pr int, Preview, Export and Launch

`

Here we ca n see the relationship within hosts and storage de vices, with all the media in between them. Also, in the sec ond image, we can see under visual storage, that, selecting a Disk Director, or a Hyper in it, w here it resides, in which physical disks, in the below portion of the image. At a glance v iew (showing all)

Web Console – Login Web Console V iews The Web Console has several views that contain the same i nformation as their Java Console counterparts, though it is displayed in a different wa y. You can see that the application removes the normal browser’s me nu bar and management buttons, so you have to use the tool’s own links to do things like print and sa ve. The Print button displays either the data from the tree or the mai n panel in a browser pa ge 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 HTM L, JPG, or CSV forma t. 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, aler ts to users, etc. Command History View – Symmetrix: System Auditory.

The ControlCenter Secur ity Model EMC ControlCe nter’s security model is very sim ple and much like many others in the industry. User accounts are created within the Contr olCenter Console. Users are then place d 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 r ules, effectively granting users within that group the permissions defined by the Authorization rule. ControlCenter Users: * ControlCenter User ac count logins are validated using the data center’s underl ying sec urity model. * eccadmin user must be a valid Local or LDAP user on the ControlCenter Server hos t. All other users can be associated to one of three types of host user accounts: – Local Windows user account crea ted on the ControlCenter Server. – Windows domai n user account. – User account in LDAP directory. * ControlCenter login uses Secure Socket Layer (SSL) to encrypt login and passw ord information between the ControlCenter Console and Server. When installing ControlCe nter, you need to speci fy which method of user validation is to be used: LDAP or W indows Domain authentication. This ca n be changed later, but you cannot use both types at the sa me time. It is important to note that all user and password information is encr ypted using Secure Sockets Layer (SSL) between Console and Server hos ts in order to protect the security of that information. ControlCenter Authorization Rules * Rules grant permissions to a single user or groups of users. * Permissions determine w hat actions a user or group may perform on a given object or user- defined group. * The “Any User Rule” is applied to newly crea ted ControlCe nter users and allows mo nitoring only permissions. * 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 Gro ups “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.” Security Considerations * Users: – Controlling the admi nistrators that configure the storage environment is a critical part of automated networked storage se curity. Controlling administrators’ actions requires enforcing general security rules: . Each administrator should have an individual account; there should be no shared ac counts. . Strong password policies for a dministrators s hould be enforced; passwords should be complex and regularly changed. . Administrators s hould only be authorized to perform management actions that are required to perform their job. . Administrator actions should be audited. * Group/Rules: – 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 a nd choose New from the menu. Type a name for the rule at the top. If you are associating this rule wi th a group, it will make your administration easier if you give the r ule 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 wi th this r ule in the bottom of the dialog. Start by choosing to organize the actions by Groups/Instances or T ypes. C hoosing T ypes (ill ustrated 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 objec t 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 Gro up New Authorization Rule By Type EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina.

New Authorization Rule By Group/ Instances * Groups can exist only in ControlCenter, there is no need for groups to exist in Local or LDAP Authentication. Data Collection Policies (DCP) * Formal set of stateme nts used to manage the data collected by Contr olCenter 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 fro m the template. – Delete Data Collection Policies. – View Data Collection Policies that apply to various managed objects. – Stagger s tart 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 Contr olCenter 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, sa y you have ten Windows 2000 ser vers. 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. Beca use the default policy includes all Wi ndows 2000 servers, it is necessary to edit the default polic y 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 recomme nded number of managed objects to be managed by a si ngle Data Collection Policy definition. Data Collection Policies can be managed from wi thin the AdministrationData Collection Policies folder. There are two subfolders that are used depending on whether you are crea ting new policies from scratch or managing existing policies.

DCP Policy Definitions/Policy Templates Managing the Data Collect ion Po licies cons ists 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 ca n edit all settings for a n existing data collection policy; however, you can only edit the sc hedule and properties defined by the data collection policy templates. * Copying Data Collection Policies — Use the copy policy function w hen you want to have more than one data collection policy wi th similar settings. * Deleting Data Collection Policies — You can only dele te policies in the Policies Definitions branch of the Administration tree. Data collection polic y templates cannot be deleted. * Viewing Data Collection Policies — You can create a tabular view of specific data collection policies and templa te 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 Schedules You can use schedules to specify the times ControlCe nter 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 aler ts or data collection policies). Alert or data collection policy schedules define when Contr olCenter should evaluate alerts a nd collect statistics through a data collection policy. In a schedule, you can define the inter val at which an event occurs (ever y 10 seconds, minutes, hours, and so on), the days of the wee k, 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 c omplete, the new policy name shows up in the tree panel on the left.

Schedules – Continued Creating a New Policy from a Template Creating a New Policy from a Template - (Continued)

ControlCenter ma kes it very eas y to monitor configure d policies through the use of the Policies View window. If you dra g 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 ma naged 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 wi ndow 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 e nabling/disabling the policy, dele ting, 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 Polic y Definitions are c onfigured 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. Policies V iew * The “WLA” policies set are for perfomance gathering. Data Collection Policy Considera tions When adding new hosts: * Create Discovery DCPs for each one-hour time slot within the wi ndow. * Distribute hosts evenly among the one-hour time slots. * Mix large, me dium, and small hosts (as defined by the number of Host Devices) in each time slot. Schedule daily collections during an off-peak window w henever possible; especial ly host “Discover y.” Monitoring ControlCenter The Command History view shows all of the actions that users have taken through the ControlCenter Console. You will see administrative tas ks such as a dding a new user, adding a user to the Administrators group, or editing data collection policies. You will see object manageme nt tasks also, such as editing a z one set, creating new array devices, or discoveri ng a new database.

Command History View The Command History view shows all of the actions that users have taken through the ControlCenter Console. You will see administrative tas ks such as a dding a new user, adding a user to the Administrators group, or editing data collection policies. You will see object manageme nt tasks also, such as editing a z one set, creating new array devices, or discoveri ng a new database. 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 acc urately show you e very change that they make through ControlCenter. Command History Data Retention Log Collect ion Wizard * Log Colle ction Wizard collects log data about ma naged objec ts in the ControlCenter environment. * Two versions of the sof tware allows for seamless collaboration between customers and support.

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 ca n launch it using the desktop icon. The versio n installed with your ControlCenter environment is a full-featured version that interacts with your software. EMC customer service representatives have an inter nal version of the software that can be run independently of any Contr olCenter software. T he 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 Collect ion Wizard Co mmunicat ion * Communicates with Master Agents in the environment to collect log files. * Automatically installed with ControlCe nter Server. Log Collect ion Wizard User Interface * Users create new or use e xisting instruction xml files to filter log data based on log types, file name, or host. * Send zipped log file collection to EMC FTP Server. * Attach important files to zipped log file collection results for additional troubleshooting information. The Log Collection Wizard communicates with Master A gents in the environment to collect log files. The Wizard is automatically installed on the host with the ControlCenter Server during the initial ControlCenter im plementation. The user operating the Wizard makes selections based on the types of log data to be collected, the commands are se nt to the Mas ter Agents on the hosts that contain the ma naged object agent, the logs are collected, and then zipped into a log file archive on the ControlCe nter Server host.

Symmetr ix Configuration Overview * Symmetrix configuration is a component of the Co ntrolCe nter Symmetrix Manager * More than one tool can configure a Symmetri x: – ControlCenter Console – Solutions Enabler, or SYMCLI – Symmetrix Management Console * Prerequisites: – ControlCenter . EMC ControlCe nter Symmetri x Agent . Solutions Enabler installed on agent host . Symmetrix Manager License – Solutions Enabler or Symmetrix Management Console . Configuration capability has bee n available since Solutions Enabler 4.1 . Configuration Manager License . Symmetrix Management Console License if using GUI The Configurat ion changes allowe d 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 Reallo cation) – Map Symmetri x Devices to Front End Ports. * Device Type Definition – Convert device types: Standard, Business Continuance Volumes (BCVs), or Dynamic Reallocation Volumes (DRVs). * Device Attribute Definition – Give S ymmetrix devices the Dynamic RDF or Double Checksum attribute. * Device Protection Definition – Add a mirror to an unprotected device or dr op a mirror from a 2- way mirrored device. * SRDF Device Definition – Crea te static SR DF Device pair definitions from existing Symmetrix devices. * Port Flag Settings - Modify SCSI or Fibre Channel front-end director flags. * Symmetrix Attributes – Change global Symmetrix attributes s uch as maximum number of hypers per disk, the RAID type to enable, SRDF se ttings, and others. * Save Pool – Crea te and Populate Save Pools. * SRDF/A Attributes – Change the SRDF/A che ckpoint frequency, cache size, and other factors The Command Line interfa ce also allows the following configuration changes. * Enable/Disa ble Dynamic RDF - If enabled the Dynamic RDF a ttribute can be set on non-RDF devices. * Enable/Disa ble FBA multi access cache - Must be enabled to create Celerra F BA devices. * Restrict access to the VC MDB device - If enabled, you deny database access to all hosts except those w hose HBAs have been masked to the VCM DB device. Device masking could then be performed only by those select hosts. * Change device emulation - Change allowe d 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. Symmetr ix Configuration Process * Configura tion change requests are sent from the ControlC enter Console to the primary Storage Agent for Symmetrix. * Symmetrix Agent sends the change requests to the S ymmetrix via Solutions Enabler API over the SCSI/FC i nterface.

* The steps in a configuration change session are as follows: – Submit – Commit – Validate – Database Refresh – Prepare * Configura tion change sessio ns cannot be aborted via the ControlCe nter Console. Accessing Sy mmetr ix Configurat ion Opt ions Symmetrix Configura tion is part of the Storage Allocation tas k set in ControlCe nter. Symmetri x configuration options can be accessed one of three ways: * Select Storage Allocation from the tas k bar. Highlight the Symmetrix which you intend to reconfigure. From the menu bar choose Co nfigure> Symmetrix. * Select Storage Allocation from the tas k bar. Highlight the Symmetrix which you intend to reconfigure. Short cut icons are available for SDR and Meta Device Configuration. * Right-cli ck on the Symmetri x which you intend to rec onfigure. From the menu choose Configure.

Symmetr ix Management Console Conte xt Launch Some ControlCenter C onfiguration Commands handled by SMC Tip: You can group tas ks (if they are the same kind of tas ks) to impro ve time, as things eas y as creating metadevices, could take several minutes if many. Remember that at this time, the symm will be locked. Symmetr ix Configuration Considerations: * Configura tion changes should be performed by advanced users. * Planning is key. – Determi ne requireme nts. – Understand the proposed reconfiguration prior to change. – Ensure that critical data is safely preserved. * If possible, s top I/O activity on all Symmetrix devices to be altered prior to commit. * Determi ne if the configura tion change requires de vices 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: * sy mconfigure verify –sid # > Command verifies that all requirements for the host and Symmetrix are correct. Such a verification cannot be performed from the ControlCe nter C onsole. Configuration Log and Lock SYMAPI Log: A record of all the S YMAPI calls ( Issue d via SYMCLI or via ControlCe nter) 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 Files EMCSYMAPIlog in a Windows e nvir onment. As indicated earlier configuration changes initiated via the ControlCenter Console are directed to the Primar y Symmetrix Agent which in turn initiates SYMAPI (Solutions Enabler) calls. T he configuration related SYMAPI calls are recorded in the SYMAPI log file on the Host where the Primary Symmetrix is r unning. 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 Loc k: The Symmetrix configuration lock is ac quired 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 i n the ControlCenter Console and is a lso 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 situation.

Symmetrix Optimizer uses the same co nfiguration change mechanism to perform swaps of hyper volumes. Symmetrix Optimizer needs to acquire the Configuration Lock as well w hen 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 necessar y. Identify ing the Primary Agent When changing the symm configuration, there is no versioning, so the only way to recover it, would be by hand. Logica l Dev ice Configuration * Select these parame ters – Number of devices – Device emulation – F BA only (open systems) – Device configuration (protection) – SAVE Device? * Considerations – 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 i f the Symmetrix serves both open systems and mainframe – Devices can be destroyed via ControlCenter only for DMX Symmetrix (5670+) Dev ice Configurat ion: 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 ac quired, a warning message is displayed. In order to successfully create new devices, all the devices on the Symmetrix (excluding Vir tual 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 wi th the Logical Device Configuration process. The Logical Device Configuration input screen is displayed.

Viewing Unconfigured Space Dev ice Configurat ion 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 i n MB or C ylinders. The drop down list shows you the device sizes that already exist on the Symmetri x. The recommendation is to choose the size from the drop down list, but you can enter a differe nt size. Choose the Configuration (Protection Type) from the drop down list. If the devices being configured are to be use d 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.

Dev ice Configurat ion Input à Dev ice Configurat ion – Result à New devices will be in the Unmapped Devices folder The Configuration sessi on initiated via the Console goes through a number of steps describe d earlier in the lesson. * Submit * Prepare * Valida te * Commit After the Commit is finished, the Configuration Lock on the Symmetrix is released and then ControlCenter i nitiates a Database refresh to update the Contr olCenter Repository with the mos t up-to-date information about the Symmetri x. Meta Dev ice Configuration. ControlCe nter allows the following: * Concatenated Meta Volumes: * Start removal from the tail member – Create or Dissol ve * Striped Meta Volumes: – Add members – Create or Dissol ve – Remove members – Add member * Must have an identical Meta-BCV a vailable 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 members later. – 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).

EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. You can rem ove 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 me ta ID is the meta head ID. Meta Dev ice Configuration – Considerations * All mem ber devices must have the same type of: – Protection – Emulation (FBA only) – Attri bute (BCV or Standard) * Devices mus t be unmapped before they can be formed as mem bers of a meta. * Changes to the attribute of a meta are done by changing the attribute of the me ta head. * Only the meta head is mapped to a front end port. Meta Perfor mance Considerations * Capaci ty: – Larges t capacity supported without RPQ – 1.1 TB. – Larges t capacity possible – 16 TB. * Number of Members: – Larges t number possible – 255. – Larges t number tested by Performance Group – 48. – EMC generall y recom mends creating smaller meta volumes rather than very lar ge meta volumes. * 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 e venly across DA ports and process ors. – Avoid members on the same physical disk. – RAID-S/Parity RAID – Choose members from different RAID groups.

Display Dis k Location of Unmapped Devices Before creating a Me ta 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 m ultiple 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 Dev ice Mapping (Symmetrix Dev ice 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. * Considerations: – Unprotected standard devices cannot be ma pped.

* Unprotected BCVs can be mapped. * Unprotected gatekee per devices (smaller than 20 cylinders) can be mapped. – Determi ne 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 sele cted Target ID and LUN is appropria te 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 ma y also need to e xecute some OS-specific c ommands 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 Mai nframe (F BA a nd CKD) * Specify Virtual bus (vbus) a ddress if volume set addressing is used in HP-UX * Specify CKD device number - OS/390 host * Update VCMDB wi th WW N of HBA to allow access to device being mapped. Deter mine A rray Port Map Dev ice

Copy Dev ice to Another Port You frequently wa nt to map the same device to more than one array port to create re dundant paths. Use the copy feature of the S DR 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 wo uld like to copy the device to in the right panel and click Copy. The same device can be copied to any number of ports by re peating this procedure. Change Dev ice Address You should always check the device address, or LUN number, before committing your changes. Many hosts have restric tions 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 par t of the tree. Just click the number to change it. Exec ute 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 wi ndow. 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.

Exec ute SDR Reconfigure Hosts A fter SDR Operation – Solaris 2.6: disks; devlinks; devalias – Solaris 2.8: devfsadm – Solaris 2.9 /usr/sbin/update_drv * HP Hosts: Execute the following commands: i oscan -fnC disk ; insf -e * IBM AIX Hosts: Execute the following command: cfgmgr -v * Windows hosts: Add / Remove Hardware. Hosts have to be reconfigured to recognize the new devices that are available for access. Remember to perf orm LUN masking in a Fibre C hannel switched environment. T he commands to reconfigure hosts are Operating System specific. For Solaris 2.8 and higher, the devfsa dm command can be used as well. In a Solaris environment, the sd.conf file should be appropriately configured as well. A disk label might als o have to be applied wi th the format command. The update_drv command (available in Solaris 9 and higher) performs a dynamic reload operation on any loaded driver (s uch as the sd driver), forcing it to reread the configuration file, an opera tion which normally would have require d a reboot in pre vious 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 c onnections with Storage S ystems. Dev ice Type and Device Attribute Def init ion * 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, T DEV, VDEV, T DEV, COV D – BCV or STD devices in a synchronize d state, Meta members. The Command Line interfa ce allows the se tting of the following additional attributes as well: * WORM (Write Once Read Many) * VCM DB * SCSI3 Persistent Reserve (For SUN Cluster 3.0 environments) Dev ice Type Def init ion 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. C hanging the device type definition does not alter the protection of the device. Clicking the Execute button starts the configuration session. Note: To convert a device to a DRV, it must be configured as Unprotected. A BCV ca nnot be converted to a DRV directly, it must be converted to an STD first. Dev ice Attribute Def inition To change the device attribute definition, use the configuration menu to launch the Device Attribute Definition dialog shown above. To add or remove an attribute, click in the cells under the attribute column. Light blue colored cells indicate pending changes. Dynamic R1 and R2 ca n both be assigned to the same device if desired. If a device is capable of both Dynamic R1 and R2, i t can be either the source or target of remote synchronization. It can also participate in an SRDF swap operation, or become a Cascade d SRDF R21 device. * opt ion only available to use with Oracle DBs.

Dev ice Protection Def inition 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 dialog. 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 array. The original device type changes from 2-Wa y 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 crea ted and added as a mirror. Enough unconfigured space must exist on the arra y 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. T he 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 acci dentally selecting the wrong thing. Dev ice Protection Def inition Dialog The example at the bottom of this illustration shows a BCV that has been unprotected. Each mirror becomes an indepe ndent device, with a new device number being genera ted for the additional mirror. Bring up the Device Protection Definition dialog to change the protection of a device. The ControlCenter Console only shows devices on which the Device Pr otection changes can be made. It filters out all RAID-5, RAID-6, a nd Mapped 2-Wa y Mirrored devices.

The pending changes are shown in blue italics. Clic k Execute to commit the configuration change. SRDF Dev ice Def init ion The SRDF Device Definition configuration adds the R1 attri bute to a local device and the R2 option to a remote device, making them a linked SRDF pair. This option creates static SR DF Device pairs only. As we have seen, the Dynamic SRDF attribute is enabled in the Device Attri bute Definition dialog, not the SRDF Device Definition dialog. Only mirrored, RAID-5, RA ID-6, or Unprotected devices can be made into static SR DF pairs. A matched pair of eligible devices must exist on both of the arrays. Both devices match if they have the sa me Meta configuration (if Metas), size, emulation (F BA or C KD), 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 bee n created (by command line). A configuration lock has to be acquired for both arrays. You can not delete or edit a static SR DF device pair relationship using Contr olCenter.

Use any of the me thods described previously to launch the SRDF Device Definition dialog. The Select Symmetrix Screen will pop up first. Choose the Local a nd 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 ac quired and the Warning messa ge shown in Step 2 on the sli de will pop up.- From the Selec t Local R1 Device Column select the device that becomes the R1. Before you pick a device from the Selec t 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 Selec t 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 crea ted, 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 Disable d or Not Rea dy state. Port Flag Settings The Port Fla g Settings dialog is used to change the communications protocol settings o n Symmetrix array ports. * Change settings of SCSI or Fiber Channel Host Director ports * Considerations: – Settings may have to be changed when adding hosts to existing switched configurations or for preparing an unused por t for host connectivity. – EMC recommends that you temporarily suspend I/O activity to the affected ports when setting front-end port attributes. – Incorrec tly changing the port flags can render your S ymmetrix storage s ystem 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 a pplications in operating systems, or some specific Platforms. Another option is to use “hetero geneous” bit setting. When choose Port Flags Settings from the configuration menu, you see a Default Settings dialog like the one above. You can use i t to choose the standard settings for cer tain 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 – Rev iew/ Manual Edit The second part of the Port Flags Settings dialog gives you a chance to make detailed edits to the flag settings. Ever y 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 mea ns it is not set. Settings that can not be edited are in gray. T he two tabs choose the Fibre or SCSI flags for each port. Delete Logica l Devices Use the Dele te Logical Device configuration menu to dele te one or more devices. This is one of the few configura tion menu dialogs that does not allow you to choose the devices within the dialog. All of the devices selec ted on the console w hen the menu was launched will be deleted! If you right-clic ked on a single device to launch the dialog, only that device is deleted. If you selected multiple devices and ri ght-clicked, all of them are deleted. If you selected a Symmetri x and right-clic ked, all eligible devices on the arra y are deleted! Be espec ially careful with this command.

Set Sy mmetr ix Attributes Note: Different options are available wi th different versions of Enginuity. Symmetr ix V irtual Prov is ioning * 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 alloca ted from a common storage pool, making it easy to provision for tiered ser vice levels. Because the de vices only consume storage w hen written to, they greatly improve capacity utilization. You can initialize an application with a large a mount of virtual storage, and add more physical storage to the pool as the application grows. Virtual provisioning can also im prove the performa nce 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 la ter arrays support virtual provisioning. Virtual Provis ioning Architecture * Virtual (“thin”) Device: – Must be bound to a Thin Pool. – Presented to host wi th 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, RA ID-5, RAID-6. – All Data Devices in a pool must have the same protection.

Virtual Provis ioning Storage A llocation Ter minology Managing the capacity utiliza tion of thin devices and thin pools is an important tas k in ControlCenter. If a pool becomes com pletely utilize d, the thin devices bound to it will not be able to allocate new storage trac ks. When this happens, writes that require new s torage tracks will return a write failure to the host. Other I/O operations will still succeed, however. The free or a vailable space in the pool represents all of the trac ks 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 promise d more s torage to the thin devices than the pool can provide. Virtual Provis ioning Dev ices Support: Thin devices and data devices have a maximum size of 64 gigabytes—the same li mit any devices in a Symmetrix wi th this level of Enginuity have. Of course, EMC recommends a smaller, more flexible device size. Thin devices can be mapped and mas ked, but data devices are never mapped or mas ked 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, RA ID-5, or RAID-6. Thin devices can be replica ted to other thin or virtual devices, but never to a fully-provisioned device. You can use TimeFinder/Snap to replicate a thin device to a Sna p vir tual 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 showi ng the exact utilization. Since the Solutions Enabler processes monitoring the arrays detect this e vent, 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 Provis ioning Properties V iews Thin pools are displayed as a data device in a blue rectangle. Thin Pool properties s how the total capacity, use d capacity, and free capacity of the pool. The subscribed capacity is la beled “Total Capacity Alloca ted” in this view. Virtual Provis ioning Free Space V iew The storage summary graph now includes measures showing the Thin Pool Available, T hin Pool Used, a nd pool Over Subscription. The sum of all of the components included in this bar graph except for the Over Subscription represents the configured storage of the array.

Thin Prov is ioning Imple mentation Steps 1. Create Data Devices (SMC) 2. Create Thin Pool, populate with Data Devices, enable Data Devices (SMC) 3. Create Thin Device, bind to T hin Pool (SMC) 4. Map, Mask Thin Device as normal (ControlCenter or SMC) Create Data Devices To create data devices, right-cl ick on the arra y and choose Device Configuration > Crea te Device (SMC) from the menu. This will launch the Symmetri x 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 crea tion tasks require a configura tion change. When you confirm a Symmetri x Management Console operation that requires a configuration change, the task will just be added to the My Active Tasks tab of the Co nfig 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 a ny uncommitted changes.

Create Thin Pool To create a thin pool, right-click on the array and choose the Device Pool Management > New Thin Pool (SMC) menu. T his menu will launch the Symmetrix Mana gement Console dialog for creating thin pools. The Save options in this menu are for TimeFinder/Snap or SRDF Delta Set Extension pool manageme nt, 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 commi t the change, and post a success or failure notification. You will not have to turn to the Config Session view after lea ving this dialog. Enable Data Devices After creating the thin pool, you might like to view it before lea ving Symmetrix Management Console. Locate the pool under the Pools folder under the arra y in the left panel of the Console. Clic k on it to show the general properties, thin devices, and data devices. You ca n click on an individual data or thin device to view its properties i n the bottom of the dial og. If you did not choose to automatically enable the data devices in the Crea te Device dialog or in the Crea te 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-clic k and choose the Device Pool Management > Enable Device menu. Create Thin Dev ice, 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. C hoose 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. EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. Verify Thin Device in SMC Save Pools * 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 fro m the source that the Snap is replicating. Many Snap devices can use the same pool to help s hare 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 reco ver from temporary bursts of writes or link failures. Delta Set Extension was ma de available wi th Enginuity 5772. Each of these technologies has its own type of Save Pool. Active S NAP sessions can cause many writes to the ass ociated Save Pool. You might want to create separate Save Pools to prioritize the performa nce 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 dis k 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 Edit ing Save Pools Delet ing Save Pools and Dev ices à SRDF/A Attributes

SRDF/A tra nsmits data in time-consistent sets called “cycles.” The data on the remote site is consistent as of the las t completed cycle. The Set SRDF/A Attributes dialog allows you to set the minimum cycle time from 5 to 59 seconds. Under normal circums tances, the remote site should be updated consistently at time periods e qual to the Cycle Time . Howe ver, 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 loa d. 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. Gr oups wi th higher priorities drop first when cache fills. Associating an SRDF/A Delta Set Extension Pool e nables 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 nee d to be dropped, but performance will be reduced as the writes now have to be retrie ved from disk. If the Tra nsmit Idle feature is enabled for the RA Group, the session will not dr op when all the links betwee n the sites fail. Instead, the local arra y just elongates the cycle time as it does whe n 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 fille d, the sessions drop. Delta Set Extension pools and the Transmit Idle feature are availa ble on arrays having Enginuity 5772 or higher. Releasing Reservations Since reserved devices are omitted from ControlCe nter c onfiguration dialogs, there is no direct way to override a reservation. Howe ver, you ca n use the Console to release device reservations, and then return to the configuration dialog to modify the device.

CLARiiON Configuration via ControlCenter * Configura tion changes supported via ControlCenter C onsole: – 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 Stora ge Group. – Edit Storage Processor network settings. Accessing CLARiiON Configurat ion Opt ions New RAID Gro up Bus, Enclosure a nd Disk number are part of the disk name.

New RAID Gro up Properties Defragment RAID Gro up Fragmentation in a RAID Group occurs as you unbind and rebind LUNs on a RAID Group creating gaps. Fragmentation causes performance issues by spreading contiguous data to m ultiple 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 files ystem mounted on a CLARiiON LUN. If no deleted LUNs, no nee d to defra g. Delete RA ID Gr oup Before you can delete a RAID Group, you must unbind all the LUNs and Private LUNs (par t of a MetaLUN) on it or you get an error as shown in this example. Just right-cli ck on the RAID Group, and choose Dele te RAID group from the Configure menu.

Bind LUNs A LUN is a host- addressable s torage unit created from a RAID Group. A RAID Group can have ma ny LUNs, but they all share the same protection type. You set the protection type wi th the firs t LUN you bind. All additional LUNs must be of the same protection. This is the equivalent than creating a Hyper(meta) in Symm Arrays. Expand MetaLUN -> ß Expand MetaLUN Pro perties. a Properties View of some regular and a MetaLUN in the Console. T he MetaLUN head along with its associated Components and Private LUNs (LUNs that are part of a MetaLUN) are shown. Note that the Size col umn shows the total meta capacity and the capacity of each private LUN, but the Ac tual User Capacity column has N/A for the private LUN size. T he Actual User Capacity only shows a value for the MetaLUN head since it is the user-accessi ble device. You can select the size you want to show to the OS.

Properties of LUNs: Modify and Destroy MetaLUN à You can modify some of the parameters of a MetaLUN by using the Modify MetaLUN option of the Configure me nu. It is not possible to change the Element Size Multiplier or Alignment Offset when modifying a MetaLUN. You ca n also delete the MetaLUN by using the Destroy MetaLUN option. When deleting a MetaLUN all the me mbers are unbound (dele ted from the RAID Group) and the data will be lost. SP Net wor k Settings and Managing SnapShots à The final CLARiiON configuration task that can be completed using ControlCenter is managing SnapView snapshots. 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 sessio n can be executed against. •Exploring a Snapshot. •Creating New Snapshot sessio n. These are the possible Snapshot management tas ks availa ble in ControlCenter. Tasks such as activating and terminating a Snapshot sessio n cannot be done using ControlCe nter. SA N Management Overv iew * SAN Management tasks are performe d via SAN Manager – Licensed ControlCenter a pplication 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 performa nce of the SAN *Manage zoning operations of the switched fabrics i n the SAN *Perform storage device mas king opera tions on storage arrays in the SAN – Please refer to the EMC ControlCe nter Support Matrix for a compre hensive list of all the switches a nd storage arrays supported by SAN Manager. SA N Manager Deploy ment – Example. ß Switched Fabric Def initions.

A single switch, or several physically connected switches, form a Fa bric. The swi tches in a single fabric can route data between any of the connected ports, no matter what switch they are on. A Zone can be created to isolate traffic between a Host Bus Adapter (HBA) and an Array Port. The switches in the Fa bric enforce isolation so that traffic from either e nd point can go only to the other e ndpoint and not the other swi tch ports. When an HBA initiates a connection, the only entity to reply is the z oned array port, which identifies the devices mapped to it. A Zone may not extend beyond the Fa bric. A set of Zones within a Fa bric is referred to as a Zone Set. In ControlCenter, a si ngle Zone Set defines all of the Zones in a Fabric—there is only one Zone Set active at any time. SA N Manager Zoning Operations * Create/Manage Zones and Zone Sets * Import Zone Set: – Active and Inactive Zone Sets can be imported fr om the switch * Activate Zone Set: – A planned Zone Set is pushed to the switch and activated * Reactivate Zoning: – Reactivate the active Zone Set from ControlCenter onto the fabric * Considerations: – As a best practice import Active Zone Set before modificat ion – SA N Manager retains co py of last active Zone Set for fa il-bac k. Connect ivity Area of the Tree Panel The Active Zone Set can be imported manually from the fabric, or you can use the Fabric Validation Data Collection Policy import it automatically. The Fabric Validation policy wil l periodicall y compare the active fabric zone set. If a difference is found between it and the Active Zone Set in ControlCenter, the policy can automatically re-import it, or it can send an alert to notify you that a difference was found. The Planned Zone Sets folder is used for editing zone sets. You can create new zone sets from scratch here, or make a copy of an existing zone set and make a few mi nor edits to it. When it is ready, you can make it active in the fabric. The Planned Zones folder is the place to store zones you might want to reuse in several zone sets. Create them once there, and then use them whenever needed. The Switches folder s hows the physical switches in the fabric, and the Unzoned Ports folder has the physical ports that have been discovere d that have not yet been zoned. It is a best practice to work on copies of active zo ne sets, in or der to modify them and then activate it, instead of modifying the or iginal one, that could not be done.

Import Active Zone Set Tas k Lists and Tas ks Create New Zoning Policy

Enable Defa ult Zoning Creating a New Zone Creating a New Zone Set

To create a new zone se t from scratch, drill down into a Fabric, right-click on the Planned Zones Folder and choose New > Zone Set. In the new dialog, type in a new Zone Set name, then pick the zones of interest from the Available Zones column. Click Add to add these zones to the Zones i n Zone Set column. Any zone in any Zone Set in the fabric or i n the Planned Zones folder can be sele cted. You can choose to activate the Zone Set immedia tely (use the check box). If the Activate Zone Set immedia tely box is unchecked, the new Planned Zone Set appears in the Planned Zone Sets folder. If the box is checked you are prompted to setup a task to activate this Zone Set. Right-clicking on an existing Zone Set allows you to edit the Zone Set to change the z ones which are members of the Zone Set. You can also right-click on an existing zone set and choose Create Zone Set As to create a copy. The copy is ma de in the Pla nned Zone Sets folder and has e xactly the same zones as the original. You then edit the planned zone set to make changes. The Zoning Policy dialog box is used to create and modify zoning policies. Zoning policies are used to set a standard for how z ones are named and configured. Users most often use Zoning policies to automa tically name their zones i n a wa y that indicates wha t the end points are. When creating a new zone the user can select the appropriate Zoning Policy or use the default Zoning Policy for that fabric. Zoning policies specify the following characteristics of new zones: * Zoning Type— Whether the new zo ne will use switch port zoning (Port zoning) or end port zoning (WWN zoning). You cannot create a zone with mixed zoning when a zoning policy is applied. * Maximum # of Host Ports—The maximum number of host ports (ports connected to host devices) that can be included in the new zone (end port zoning only). * Maximum # of Stora ge Ports—The ma ximum number of storage ports (ports connected to storage devices) that can be included in the new zone (end port zoning only). * Zone Name Format —An expression that determines the name of the new zone. To set the default zoning policy for a fabric, ri ght-click on the fabric and use the Zoning > Set Default Zoning Policy menu. ** When creating new zones, have in mind this Zoning Policies, as they give a big help, as naming convention is normall y Host+Hos tPort+Storage+StoragePor t (%H_%Hp_%A_%Ap) Adding a Zone to a Planned Zone Set

Activate Zone Set, Compare to Active Zone Set After creating a Planned Zone Set with the desired members, the next step is to activate the Zone Set to apply these changes to the switched fabric. Right-click on the planned zone set and choose Zoning > Activate Zone Set. The Zone Set is moved to the Active Zone Set Folder a nd Mar ked as Active. A copy of the zone se t remains in the Planned Zone Set Folder and mar ked a Copy of Active. The Zone Set that was active before is moved to the Planned Zone Set folder and marked as Last Active. If you need to undo these changes, you can activate this Last Active set again. As part of the activate process, you can compare the proposed Zone Set with the Active Zone Set. Use the Show drop down to show Changes Only, Zones A dded Only, Zones Removed Only, Zones Modified only or All Zones. A Green plus indicates an added zone, an Amber minus indicates a removed zone, the blue inequality icon represents a modified zone. Click Continue to continue with the Activate Zone Set process. Either of these methods pro mpts the user with the choice to Execute or Cancel. Clic k Execute to activate the Zone Set. This forces the user to create a task in a task list. The pr ogress of the task can be followed in the target panel. Compare A ctive Zone Set to Active Fabr ic This safety feature is useful in environments where some administrators mi ght be using other tools to change the fabric. Let’s use a scenario to illustrate the issue.

Reactivate Zone Set Use this feature when you know that the Active Zone Set in ControlCe nter is the correct one for your envir onment, but you suspect that someone has made an improper change to the fabric using another tool. It is especially useful if your Fabric Validation Data Collection Policy is se t to Compare but do not import. In this setting, the policy se nds aler ts when a difference is found in the fabric, but does not import it. After being alerted to the issue, you can carefully check the situation and manually reactivate the zo ne set if necessary. Cisco VSA N Support * ControlCenter has monitoring and management of Cisco Vir tual SANs – Creating, editing, renaming, or deleting a VSAN. – Move members between VSANs. – Distributing and committing a planned VSAN. – Zone editing within a VSAN. – Suspending a distributed and committed VSAN. VSAN 1 is the default VSAN and VSAN 4094 is reser ved for ports that have been isolated when their VSAN was deleted. These VSANs alwa ys exist and cannot be deleted. Only VSANs 2 through 4093 can be manipulated. Up to 256 VSANs can be configured in a switch. At install, all ports belong to VSAN 1. Ports can be added or removed to other VSANs non-disruptively. In a multi-vendor VSAN, using intero perabili ty mode 0 or 1, it is assumed that the mas ter switch is a Cisco MDS, and configured as the principal switch. Domain IDs must be set to static and persistent FCIDs must be set to dynamic. Fabrics containing Cisc o switches have a different folder la yout in the Co nsole Tree Panel. At the top level is a Switches folder to identify the physical hardware, and a VSANs folder that contains all of the active VSANs. You cannot edit the VSANs or their membership in this folder—it

represents the active state in the fabric. Use the Planned VSANs folder to create and edit copies of the active VSANs, and then make them active. VSA N Display in the Console Within a VSAN folder, you see familiar Zone Set and Zone folders that you can use to view the active state of the fabric and make changes. Fabric ma nagement within a VSAN is e xactly the same as without VSANs. Creating a VSA N Adding Ports to a New VSA N.

CISCO VSA N - Distr ibuting and committ ing * To distribute and commit a planned VSAN to a fabric: – Right-clic k a planned VSAN and select VSAN, Distribute and Commit. – Click Execute. Remember, this only commits the VSAN object and port membership information. To make zonin changes, drill down into the VSAN folder and make the changes using the Zone Set folders. SA N Manager – Storage Dev ice Mas king * Device mas king can be performed on: – Symmetrix: * VCM DB (Volume Configuration Management Database) Management * Search and Replace Masking (HBA change) * SID (Source ID) Lockdown – CLARiiON: * Manage Storage Groups – HP StorageW orks HS G arrays – HP XP arra ys Unlike an environment in which the host is directly connected to the storage and sees only the volumes to which it is directly connected, the SAN environment introduces new challenges. Multiple hosts can be connected to the same s torage array port, providing one host the ability to see, use, and potentially corrupt other hosts' storage areas. Storage Device Masking (S DM) addresses this problem by using a unique masking policy engine that resides on the storage itself, and management software that resides on the clie nt hosts. Storage device masking allows you to specify the storage array devices that a specific host and host port can access. The SAN Manager implementation of SDM enables you to perform device masking for four types of storage arrays in the SAN: * Symmetrix * CLARiiON * HP StorageWorks * HP XP CLARiiON masking is similar, but is handled through the creation of Storage Groups. Masking View: This view is applicable to Symmetrix and HP StorageWor ks arrays. Use i t to view or modify storage device masking configura tions. A user can right click on any device from this view and modify the masking configuration of that device.

Mas king View Symmetr ix Dev ice Mas king To modify mas king configurations for a host attached to a Symmetrix array, right-cli ck the Host and choose Masking > Modify Mas king Configurations from the menu, or highlight the host and choose Masking > Symmetrix> Modify Masking Configurations from the Storage Allocation menu. The Modify Masking Configuration window will open. To change the masking configuration, check the box to the left of the device name and choose the Grant or Remove button. T he change you requested appears in blue. ControlCenter fea tures include the ability to mas k the same lo gical device to multiple domains or groups using the same s torage port in HDS/HP XP third part arrays. In other words, you can make the same device available to multiple hosts that are zoned to the same port. This capability is available in the native arra y management tools and now ControlCe nter s upports it as well. Multiple lo gical devices can be mas ked to multiple domains or groups at a time. Multiple devices can also be unmas ked wi th just one operation. The Contr olCenter Storage Agent for HDS is required to per form device masking on these arrays.

HDS/ HP XP Dev ice Mas king Review Changes, Enable Dy namic LUN Addressing After ma king your mas king changes and clicking the Continue button, the Modify Masking Configuration dialog summarizes your changes. You can use the buttons on the ri ght to edit or delete any of the mas king changes you made in the previous page of the dial og. With Enginuity 5772, you can enable Dynamic LUN Addressing using the check box at the top of the dialog. Without this feature, the host addresses the device using the LUN assigned when the device was mapped to the array port. This turns out to be somew hat inflexible if more than one host is z oned to this port. You may have difficulty assigning additional storage to the port in a way that maintains a consecutive list of LUN addresses on each host. With Dynamic LUN Addressing enabled, you can override the LUN address chosen during mapping. This allows you to select LUN addresses that are appropriate for each host, even when several hosts are zo ned to the sa me array port. You can enable the feature independently for eac h HBA and array port pair. To set the LUN address, click the Set Dynamic LUN Address button at the top of the dialog. The dialog that appears shows the System LUN addresses—set during masking—and the Host LUN addresses. The Host LUN addresses are consecutively ordered by default, but you can click on values to manually change them. Once the device is masked howe ver, you cannot change the LUN address wi thout unmas king the device and starting over.

Symmetr ix V CMDB Management * Make Active: – Activates the configura tion for a selec ted storage array * Backup: – Backs up the current configuration to a file you select * Restore: – Restores the VC M database from a file you select * Initialize: – Initializes the VCM database and sa ves the current configuration to a file you select. Symmetrix Device mas king is performed by making changes to the Volume Configura tion Management Database (VCM DB) on the array. T he VCMDB is a file residing on a Symmetri x logical device that is used to store access configuration data used for masking logical devices from hosts. The VC M database exists on a special s ystem resource logical device, referred to as the VCMDB device. Information stored in the VCM database includes host and storage World W ide Names, S ID Lock and Volume Visibility settings, and native logical device data, such as the front-end directors and the director ports to which they are mapped. The VCMDB must be activated to ma ke changes to the masking configuration take effect. From the ControlCenter Console, you can backup, restore and initialize the VCMDB as well. The VCMDB must be initialize d before use, usually when the Symmetrix is first configure d. ControlCenter forces you to backup the VC MDB if you try to initialize it. Backups of the VCMDB are stored on the Co ntrolCe nter Server host. Symmetr ix V CMDB Commands To make a backup of the VC MDB, right-click on the Symmetrix array and choose Mas king > VCMDB Management >Backup or highlight the Symmetri x and choose Mas king > Symmetrix > VCMDB Management > Backup from the Storage Allocation menu. To restore the VCMDB, use the Console to locate the backup in the VCMDB Backups folder under the Symmetrix. Right-click, and choose Res tore from the menu. The VCMDB Backup will appear i n the VCMDB Backups folder on the Co ntrolCe nter Server. You can find it under a folder identified by the Symmetrix ID: <CC INSTALL ROOT>ecc_infdata<ECC Server Hostname>databackup<Symmetrix ID>

Symmetr ix Replace Mas king Replacing masking transfers access configurations from one host port or unidentified port to another. This is useful when replacing an existing host port with a new one. Swapping access is performe d on one host port pair at a time, and in one Symmetrix storage array at a time. The host port receiving new mas king configurations cannot have existing mas king configurations in the VCM database of the Symmetri x array in which access is being swapped. Right-click on an HBA or a Host and choose Mas king > Replace Masking from the menu, or highlight an HBA or a Host and choose Mas king>Symmetri x> Replace Mas king from the Storage Allocation menus. In the Replace Mas king dialog, choose the existing HBA from the panel on the left, and the storage array and the new HBA from the panels on the right. Click Add Action to ma ke this edit. Make some more edits if needed, and then Continue to approve of and execute the edits. You can not manually enter a WW N in this dialog, ControlCe nter m ust have discovered the HBA before you try to re place it. This works well if you install the new HBA in the host and then let the Host Agent discovery it before launching this dialog. The VCMDB can be activated as part of the Re place mas king operation, but the New HBA must be zoned separately via SAN Manager. Editing CLARiiON Storage Gro ups In a CLARiiON array AccessLogix must be enabled on the CLARiiON array and then device mas is done as follows: 1. Create a Storage Group 2. Add LUNS into the Storage Group 3. Connect a host to the Storage Group ControlCenter terminology is Bind/Unbind hosts) Highlight one or more LUNs, right-click, and choose Add to Storage Group from the menu to launch the Storage Group Configuration Wizard.

Storage Gro up Configuration Wizard The next step in the Storage Group Configuration Wizard is to add LUNs to the storage gro up. The LUNs you clicked on are already added, but you might want to choose a few more from the panel on the left. Once the LUNs are added you can Bind/Unbind hosts (Connect/Disconnect a Host from a Storage Group in Navisphere term inology). Note that the Bind process will be successf ul only if the Host is properly re gistered with the Storage Array. EMC Recommends that any ser ver attached to a CLARiiON array should run the Navisphere Host agent and a ControlCenter Host Agent. The last step is a re view. Click Execute or Execute Later. Setup the task and tas k list. Once the task is e xecuted success fully, the mas king process is complete. Properties of LUNs and Storage Groups In this example, once the MetaLUN has been added to the Storage Group the Pro perties view in the console shows the MetaLUN head belongs to the CLARiiON storage group WIN2-CX200. The second Properties view shows the LUNs in Component 0 of the Me taLUN, the Storage Group field is N/A as only the MetaLUN head is presented to the Storage Group.

CLARiiON – Remove LUNs fro m Storage Group Business Continuance – Sy mmetr ix * Symmetrix Manager license provides Business Continuance operations – Provides GUI support for: * TimeFinder/M irror * TimeFinder/Clone * TimeFinder/Snap opera tions * SRDF/S and SRDF/A – Use to: * Monitor SRDF, SRDF/A and TimeFinder activities * Manage device gr oups * Manually execute local and remote SRDF, SRDF/A and TimeFinder commands for ad- hoc replication requirements * Manipulate Quality of Service (QoS) settings for devices * Create/Delete Dynamic SRDF device pairs – Storage Agent for Symmetrix must be deployed. TimeFinder/Mirror Operations Ti meFinder Mi rror * Identify appropria te Standar d and BCV volumes Establish * Create Device Group: Split – Add Standard devices I/O – Associate BCVs 1) Establi sh 2) Split 10GB * Perform TimeFinder/ Mirror operations: 10GB 3) Restore – Establish A B A B I/O C – Split C STD BCV – Restore * Monitor s tatus in TimeFinder View. TimeFinder/Mirror operations in ControlCenter starts with identifying standard and Business Continuity Volumes (BCV) that can be used to replicate data. You can add the devices to a device group, and then perform synchronization opera tions on the devices. Finally, you can view the status of the synchronization in a TimeFinder view. TimeFinder/Mirror options can be found under the Data Protection Task. There are se veral wa ys the me nu can be accessed Right-clic k the array and choose Data Protection > TimeFinder. Select the arra y and switch to the Data Protection tas k. Then use the TimeFinder menu. You can also use the quick access icons on the Data Protection task.

Accessing TimeFinder/ Mirror Options Identify Relevant Volumes We need a si milarly configured BCV on the array to copy this filesystem. You ca n drag al l the host devices to the Proper ties view and examine the ones that are marked as BCV. To be eligible to replicate the files ystem, the BCV m ust be the same size, same emula tion (CKD, FBA), a nd if the standar d device is a meta, the BCV must also be a meta constructed the sa me way. So you should be searching for a BCV with these characteristics. A matching BCV is illustrated on this page. For safety, we might also drag the BCV to a TimeFinder view to verify that it does not already have a rela tionship wi th another s tandar d. If it does, the data on the BCV might be an important copy that someone is relying on. To identify the standard and BCV devices you have chosen, you should put them in a device group. You can easil y execute commands against all of the devices in the group, and it will help identify them as being In Use to the other users. Device gr oups can also be managed by Solutions Enabler a nd the Symmetri x Management Console.

To create a new group, Right-click on the host, an array, or the device and choose Data Protection > Device Groups > Create. Choose the Symmetrix from the drop-down list – this should be a utomatically selected because the wizard was launched from a right click context. Choose type of device that the non-BCVs of the group will be. You can choose Re gular (this example), or one of the SRDF types (R1, R2, or R21) Dev ice Gr oup Wizard In the second page of the dialog, choose the host name w here the group will be crea ted. Device groups in ControlCe nter ca n only be created on a host w hich has a Storage Agent for Symmetrix or Solutions Enabler installed and can access to the array. When you use this dialog to create a device group, it will interface with the Solutions Enabler so ftware to create the group on the host. Then choose a n existing or new group to edit, and click the Edit Members button to select the standard devices (only) to add to the group (which type depends on the type of group you created in the previous page). You can only add devices that match the group type you selected when you started.. If you right-clic ked on one or more devices to launch the dialog, those will already be selecte d. Dev ice Gr oup Wizard – Associate BCVs You can search in host devices, for the device you want to use for the mirror/clone operations. Select two devices of same size, source must be STD Volume, target can be STD or BCV.

The differe nt types of BCVs that appear in this dialog are actually BCVs in different locations. You can also choose other de vices in this part of the dialog: * BCV: This refers to local BCVs. i.e. BCVs in the sa me Symmetrix. You can choose a number of sets of local BCVs to create several copies of the standard data. * BRBCV: If the BCVs you chose in the BCV section are also R1 devices, then you can use this section to associate BCVs from the remo te array to your group. The remote BCVs will replicate the R2 volume on the remote arra y. This feature lets you manipulate copies of the data on both the local and remote array all from the same device group. * RBCV: This option is available only if the standards added to the group are R1 or R2 devices. The BCV se ts you are choosing here are actually on the remote array, and will replicate the remote SR DF device. * VDEV: Virtual devices used with TimeFinder/Snap. We will cover this la ter in the lesson. * Gatekeepers: For performance reasons, you may occasionally want to associated a gatekeeper device wi th a group. Commands issued to the group will use that gatekeeper device, lea ving any other gatekeepers on the host available to process other c ommands. TimeFinder/Mirror Establish Drag ging the BCV de vices from the group to a TimeFi nder view shows their status. Since the device (number 091 in this example) has never been synchronized with the standard, there is no information in the STD column. A few other de vices have bee n added to the view as e xamples— you can see that they have bee n synchronized at some time in the past. An Establish operation synchronizes the da ta on the standard devices to the BCV devices. A simple way to es tablish pairs is to right-cl ick on the device group and choose Data Protection > TimeFinder > Establish from the menu. Click the things you want to establish in the dialog (if you had clicked on multiple BCVs, you could now choose a subset of them), and the options. Host considerations prior to an Establish operation: * Establish is a non-disr uptive operation to the Standard device. I/O to Standard devices can proceed during establish. Applications need not be quies ced during the establish operation. * The Establish operation will set a Not Ready status on the BCV device. Hence all I/O to the BCV device must be stopped before the Establish operation is performed. A Full Establish is required the first time a BCV and a Standard device are established. Make sure the incremental box is unchecked. You can use the Incremental option on subsequent operations. With this option, only the changed data is copied. The Optimize option chooses the pairing of standards and BCVs according to optimum data flow within the Symmetrix. T he chief concern is to ensure that a standard and its paired BCV are o n separate Disk Directors. Exact Pairing pairs each standard with a BCV based on their label number i n the device group: DEV001 with BCV0 01, for example.

TimeFinder View You can see that the devices are i n a Sync in Progress state and that there are BCV Invalid tracks owed from the STD device to the BCV. The time left column estimates the time until complete synchronization based on the time take so far. When the synchronization is complete, the status will read Synchronized, and the invalid trac ks will be zero. The device group name is also shown along with information about Mirror Quality of ser vice settings, etc. TimeFinder/Mirror Split A Split opera tion suspends the mirroring between a standard and BCV, creating a point-in-time copy at the moment of the split. Right-click on the BCV or device group and choose Data > TimeFinder > Split from the menu. Click the objects you would like to split and the options. There are several things to consider if you wa nt an uncorrupted point-i n-time data copy. Data writes are typically buffered in the host’s memory at the application layer and the file system layer. Applications will return a write complete before data is actually written to disk. Host memor y buffers must be flushed to disk prior to splitting a BCV, to ensure that the data on the BCV is identical to that on the Standard at the time the split command was issued. Without a flush, buffered data is not available on the Standard and hence will not be available on the BCV. Ideally, you should stop the applications and offline the devices before performing the Split. Until the State has changed to Synchronized, it is not possible to Split the standard and BCV unless the Force option is used, in which case the validity of the data on the BCV is uncertai n.

TimeFinder/Mirror Restore A Restore operation synchronizes the BCV data to the standar d, and leaves the devices synchronized. There are several things to consider before performing a restore operation. Restore is a recover y operation. Data on the BCV will overwrite the data on the standar d device. All I/Os to the standard device should be stopped and the device must be taken offline prior to a restore operation. Although it has the source data, the BCV is still the device that goes to a Not-Rea dy status to its host. All I/Os to the BCV devices mus t be stopped a nd the devices must be offline before issuing the res tore command. Operations on the standard volumes ca n resume as soo n as the restore operation is initiated, while the synchronization of the sta ndards from the BCV is still in progress. Any reads from the standard that has not yet been copied will come from the good mirror—the BCV. The Restore operation can be increme ntal or full. Increme ntal restore is the default. TimeFinder/Snap Operations * Identify volumes of interest. * Identify appropria te VDEVs. * Create Dev ice Group: – Add Source devices – Associate VDEVs * Perfor m TimeFinder/Snap operat ions: – Create – Terminate – Activate – Restore

Using TimeFinder/Snap to perf orm virtual copying opera tions provides a s pace-saving method of creating instant, point-in- time copies of logical volumes. Snapping to a virtual device (VDEV) creates the appeara nce of copying volumes by sim ply copying the original data from changed tracks and the pointers to that data. The TimeFinder/SNAP operation uses two types of devices: VDEV and SAVE. A V DEV device contains pointers to the changed data, while a SAVE device holds the actual data that has been changed. Snapping to virtual devices uses a copy-on-firs t-write technique as a way to conser ve disk space when making copies. Only writes to tracks on the so urce device or target vir tual device cause a ny incremental storage to be consumed. The space sa vings using virtual devices can be significant when you consider that most applications change only a small percentage of data on a volume. Howe ver, you can expect perf ormance degradation that varies according to application characteristics and I/O profile. TimeFinder/Snap operations allow you to copy data from a si ngle source device to as many as fifteen target devices. T he targe t of a copy operation is a Symmetrix virtual device, and the copy operation (also referred to as a virtual s nap) performs a copy of those tracks identified by trac k pointers on a virtual device. Copying occurs only when there are writes to the source or targe t devices. T he snap pair state remains CopyOnWrite until you termi nate the copy session or all tracks have been wri tten to. Accessing TimeFinder/Snap Options: TimeFinder/Snap falls under the Data Protection Tas k. TimeFinder/Snap Options can be accessed by right-clicking on the array, and choosing Data Protection > Snap from the menu. Or you can sele ct the arra y, switch to the Data Protection tas k anduse the Snap menu. You can use the Snap view under the Data Protection tas k to monitor your TimeFi nder/Snap synchronization. Identify Relevant Volumes Let us illustrate TimeFinder/Snap by using another example. We wa nt to make a point in time copy of the file systems /istdata on the host DMX8 00IBM1. We use the Relationship view to determine that the filesystem resides on devices 026 and 027, and a Properties view to show the device proper ties.

Drag ging the host’s two virtual devices to the Proper ties view shows their properties also. Fortunately, they are the same size as the devices we need to copy. Even though they do not technically store the data, the virtual device must be configured as the same size as the device you want to replicate. The next step is to create a Device Group, add the so urce devices and associate the virtual devices. You have already seen the dialog for these actions, so this course will not show them again. While ControlCenter will allow you to perf orm TimeFinder/Snap operations on devices individually EMC recom mends that you create Device Groups and then perform TimeFinder/Snap actions on the Device Groups. TimeFinder/Snap Create Drag the new group containing the source and virtual devices into a Snap view. You can see from the Snap view that there is no Snap session for the devices in our group (035, 036), because the Pair State column is NotCreated. Despite being put in a device group, the Symmetrix does not recognize a pairing relationship betwee n the virtual devices and the so urces until a Snap sessio n is crea ted. A session for a Snap pair originates when you issue the Create command and ends when you issue the Terminate command. A device cannot par ticipate in two sessions simultaneously unless it is a source device that has multiple target devices. To pair a n existing target device with a different source device, you need to first terminate the tar get’s original session. To ensure that you do not copy over previously copied data, each snap opera tion res ults in putting a hold on the target device. You can see from the dialog that you can choose a different Snap save pool for every device pair. The Create procedure is a non-disruptive operation to the source device. I/O to source devices can proceed during the Create operation. Before the Crea te can be performed, the V DEV needs to be in its normal status of Not Ready, therefore all I/O to the V DEV needs to be stopped, a nd all previous Snap sessi ons to the VDEV need to be terminated before the Create opera tion is performed. The Create operation marks the VDEV as Held, preventing it from being used in another Snap session. The V DEV remains in the Not Ready state after the session is created.

TimeFinder/Snap A ctivate Now that the Snap sessio n has been created, the Pair State column of the Snap view is Created. The virtual devices are in the Held state, and can not be used in a different Snap session until this one is terminated. The Held state is indicated in the Parameters column of the device Properties view. To identify the point-i n-time copy, use the Activate command. Once activated, any writes to the source device cause the original data to be copied to the Save device to preserve the disk image as it was at the point of activation. Use the Activate option from the Snap menu to activate the session. The VDEV devices go to the Rea dy sta te after the Activate command. T he host can now read and write the virtual device. TimeFinder/Snap Restore With the Snap session activated, the Pair State changes to CopyOnWri te. The Source Protected Tracks column meas ures the number of Symme trix tracks on the source that have not yet changed. As post-activate writes are made to the source, this number will drop. The Status of the virtual devices shown in the Properties view changes from Not Ready to Ready to indicate that the VDEVs can now be accessed by the host.

You can use the Restore command to restore data from a virtual device to various locations: * An incremental restore to the original source device * An incremental restore to a BCV that is split from the original source device but which still has an increme ntal relationship with that source. * A full restore to any unrelated standard or BCV de vice The Restore operation can be increme ntal or full. Increme ntal restore is the default, In this example, we highlight device groups and from the Menu Bar choose Snap > Restore. Confirm that you want to perf orm a restore. After a TimeFinder/Snap Restore Because restoring back to a device replaces w hat is on that device with the data from the V DEV, there is always the risk you can lose data from the tar get device. To address this issue, the Snap Restore command creates two sessions. The two sessions have states of Copy-on-Write (Activated Snap session) and Restored (Snap Restored sessio n). TimeFinder/Snap Ter minate Terminating a copy session removes a ny hold on the tar get device and deletes pair information about the termi nated pair from the Symmetrix unit. The VDEV will return to the Not Ready state and be inaccessi ble to the host.

When you select a device pair session fr om the Console to Terminate, the two sessions, Activated Time Fin der C lone and Restored, will appear i n the Terminate dialog box. The restored sessio n must be terminated before the original session. Create Act ivat e 1) Create I /O 2) Activate 3 ) Termina te 10GB 1 0GB TimeFinder/Clone Operations A’’’ A’’ I /O B’ * Identify source volumes of interest B’’ C’ C STD STD / BCV * Identify appropriate target volume Backup Term ina e t The TimeFinder Clone feature allows you to make copies of data simultaneously on multiple target devices from a single source device. The data is available to a target’s host once the session is activated. You can copy data fr om a single source device to as many as sixteen target devices. A ny device can be either the source or the target in a Clone synchronization. They must be the same size, and be co nstructed the sa me if Meta devices. Unlike a BCV mirror copy, which must be completely synchronized with its s ource and then split to access the data, the Cl one copy activation makes data on the Cl one immediately accessible to its host, even while copying is occurring in the background. The followi ng TimeFi nder Clone commands are available in ControlCenter: * Create Clone Copy - Crea te the relationship between the source and target devices. * Activate Clone Copy - Activate the copy operations. * Terminate Clone Copy - End the rela tionship betwee n the so urce and targe t devices. Accessing TimeFinder/ Clone Options TimeFinder/Clone also falls under the Data Protection Task. The Options can be accessed by right-clic king on the array and choosing Data Protection > Clone from the menu. You can also select the array, choose the Data Protection task and use the Clone menu. In this example, we would like use TimeFinder/Clone to copy the data on two BCV de vices to a pair of R1 devices. All four of the devices are show n in the Proper ties view to verif y that they are the same size, and that the destination devices are not in the Held state. Before a Clone session can be executed, the source and targe t must be first identified and paired. The Create command is used for this purpose. Launch the Crea te dialog from the Clone menu. Select a source device from the Select Source Device panel and a corresponding device from the Select Target Device panel. Note that after you select a source device, all corresponding target devices of the same size and emulation type are displayed in the other window. Clic k Add to add your pair to the Pairs panel. When you finish adding pairs, cli ck Execute. You can choose three modes of copy when you create a Clone session. In No Copy mode, no additional copying is done. Data is copied to the Cl one on a first access basis only: the first time data is read from the Cl one, or the first time data is written to the Clone or source, the relevant

track is copied to the Clone. In Pre-Copy mode, all tracks of data are c opied from source to Clone when the pair is in Crea ted state. After Activation, the additional copying terminates, leaving only the copy on first access to synchronize the devices. In Copy mode, all tracks are copied from source to Clone after Activation. The copy on first access process is also used to address data that has not bee n copied yet. Once a Clone copy session has been crea ted, the target devices are in a Held state and no data is transferred until you activate the session. TimeFinder/Clone Create EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. TimeFinder/Clone Activate With the Cl one session created , the destination devices are marked as Held in the parameters column of the Proper ties view. The des tination devices are set to Not Ready. Dragging the devices to a Clone view (use the Data Protection task to get a Clone view) shows the paire d relationship. The Pair State column of the Clo ne view will be Created at this point. No data will be transferred until you activate the session. The Activate command is used for this purpose. To activate a Clone copy session, launch the Ac tivate dialog from the Clone menu. A list of unactivated Clone sessions is displayed. Check those sessions that you want to activate, and click Execute to activate the checked sessions.

If the No Copy option is sele cted when the pair is created, then activating them should change the state to Copy on Access, indicating that data is copied from the source to the clone on any first write or rea d of the destination, or on any first write to the source. If Copy had been chosen, the pair state reflects a status of CopyInProg while the contents are copied from the Clone Source to Target. Once all the data is copied the state changes to Copied. TimeFinder/Clone Ter minate You can see that the Pair State has changed to CopyOnAccess, indicating that the pairs are active. The destination devices are Ready (read/write) again, so the point-in-time copy can be accessed. As accesses force data to be copied from source to target, the Source Protected Tracks values will de crease, and the % Copied value will increase. To ensure that you do not copy over previously copied data, each Clone operation results in putting a hold on the target device. Terminating a copy session removes a ny hold on the targe t device and deletes pair information about the ter minated pair from the Symmetrix. The target host can no longer reference data on the source device through indirection (indirect target tracks that provide visibility to source tracks). When terminating a pair relationship, no conflicts exist if the pair is in the Created state or the Copied state. However, s topping a copy session for a pair w hose state is CopyOnAccess or CopyInProg may end the session prematurely if an application has not finished accessing data, or if writes to the source device are ongoing. Terminating a pair while CopyInProg requires the Symforce fla g. To terminate a Clone copy session, la unch the Terminate dialog from the Clone menu, check the boxes of the pairs you want to termi nate, and click the Execute button. After TimeFinder/Clone Ter minate

SRDF Operations * Identify SRDF volumes of interest – Restore * Create Device Group – Mode Change * Perform SRDF operations – Suspend Link – Failover – Resume Link – Update Source – Swap – Fail Back – Create Dynamic Pairs – Split – Delete Dynamic Pairs – Establish – Advanced SRDF crea tes and maintains a mirror image of one or more logical volumes on a remote Symmetrix array. Before you ca n use SRDF, the local and remote Symmetrix arrays must each be set up with at least two Remote Link Directors (RLD) through w hich the two arra ys are linked. The Symmetrix array being mirrored is designated as the source (R1); the Symmetrix array maintaining the remote mirror is designated as the target (R2). Data is transferred across the SRDF link from the source to the targe t array. By maintaining real-time copies of data in different physical locations, SRDF enables you to perf orm the following opera tions wi th minimal impact on normal business processing: * Disaster recovery * Recovery from planned outage * Remote backup * Data center mi gration Accessing SRDF Opt ions SRDF commands fall under the Data Protection Tas k. SRDF Options can be accessed by right- clicking the array and choosing Data Protection > SRDF from the menu. You can also select the array and the Data Protection task and use the SRDF me nu. Some of the quick access icons in the Data Protection task initiate SRDF dialogs.

You can monitor SRDF activity using an SRDF View, located in the Data Protection pull-down. This view displays: * Local and Remote Device Number a nd Symmetrix ID and Device Group name * Read and write state of the Devices * Pair State: Synchronized, Suspended, Split, Failed Over, etc. * SRDF Mode: Synchronous, Semi-Synchronous, Adaptive copy etc. * Domino : On or Off * Invalid track information * Quality of Service settings If a Symmetrix is dragged into the view , the status of every SRDF V olume in the arra y is shown. In this example, the SRDF view the same device group used in the pre vious example is shown. The screen is split three wa ys to show all the columns of information. SRDF V iew Identify Relevant Volumes Let us illustrate basic SRDF tasks with an example. The Relationship view shows us that our filesystem /istdata has been created on SR DF R1 volumes. W hen the SRDF pairs are synchronized, writes to the files ystem are being transferred to the paired devices on another Symmetrix. While ControlCenter allows you to perform SRDF operations on devices individuall y,

EMC recom mends that you create device groups and then perform SRDF ac tions on the device groups. You can see from the tree panel that a device group has been created for these devices previously. An SRDF Failover is invoked in the event of a disaster or in order to perform maintenance on the production site. A failover lea ds to a Write Disabled state on the Source side. If possible, ensure that a clean, consistent, cohere nt point in time copy which can be used with minimal or no reco very is available on the Targe t side. Ideally, you would stop all applications, unmount filesystems, and disable volume groups to be sure the source devices are not being written to. Failover ca n be invoked via ControlCenter from either the source or targe t side. In this e xample, the Failover is invoked from the a host attached to the Source si de Symmetrix. The device group resides on the source side host. Assuming that the host consi derations have bee n taken care of Failover is invoked by right-clic king on the device group and choosing Data Protection > SRDF > Failover from the menu. The Failover operation makes the R1 Devices Write Disabled and the R2 Devices Ready. The Pair State goes to Failed Over. SRDF Failover SRDF Fail Bac k

An SRDF Fail Back is invoked in order to move operations back to the primary site after a disaster or maintenance has been performed on the Source Symmetrix. The Fail Back process compares the track tables for eac h affected volume in each Symmetrix and proceed to update the Source volumes with the changed data that has occurred on the Targe t Symmetrix. After Fail Back is invoked, the Source volumes are re turned to a Rea dy state and the Target volumes to a Write Disable d state. Synchronization starts in the background. Production work can be resumed on the Source Symmetri x imme diately, any updated tracks on the Target volumes which haven’t bee n tra nsferred back to the Source volumes is rea d back across the SRDF link in the e vent that they are required by the res umed production applications. A performance over head will be incurred by this ‘read across the link’ operation. Until the s ynchronization has completed, the Targe t Symmetrix cannot provide disas ter recovery protection. Make sure that applications are properl y quiesced and volume groups deactivated before you Fail Back. Assuming the host considerations have been taken care of we will perform the Fail Back. In this example, the Fail Back is perfor m from the Source side by right-clicking on the device group and choosing Data Protection > SRDF >Fail Back. The R1 Devices become Ready and the R2 Devices become Write Disabled. SRDF Split, Establis h/Restore SRDF allows concurrent operations on the Source and Target devices simultaneously. T he SRDF Split operation will suspend the SRDF link and makes both the source and target devices Ready as well. After a spli t, you can either perform a n Establish to preserve source side changes or a Restore to preserve the tar get side changes. Both of these operations puts the pair back into regular Synchronized mode (after synchronization) with the source Ready and the tar get write disabled. SRDF Mode Control

Right-clicking on a group, device, or array and choosing Data Protection >SRDF>Mode Control from the menu bri ngs up the Mode Control dialog. Use this panel to change the way the devices are synchronized. Synchronous a nd As ynchronous are the main modes—the devices mus t be in one of these modes. Synchronous mode forces e very write to the R1 be sent to the R2 and acknowle dged before acknowle dging a s uccessful write to the host. Synchronous mode is the sa fest because a write is only committed when it has be en copied to two arrays. Howe ver, it is the slowest of all the modes because each write is held up while the remote copy is done. Domino Effect is an option with Synchronous mode. With Domino Effect enabled, and link failure or other reason that prevents writes from being copied to the R2 side force the R1 device to be Not Ready. T his prevents the host applications from writing any data that can not be copied to both the local and rem ote array. Adaptive Copy is more of a bulk load copy scheme. Writes are queued up at the R1 side and written to the R2 side whenever link availability allows. A daptive Copy Disk mode queues the writes on the physical disks, and marks them to be copied to the R2 side. When link availability allows, the entire disk track is read back into cache and copied. Adaptive Copy Write Pending mode queues the writes in cache as write pendings. When link availability allows, the smaller, individual writes are copied. This mode can require significant amounts of cache. The Adaptive Copy Skew is a per-device threshold to limi t the queue size. When the number of writes for a device hits the Skew, it reverts back to Synchronous mode, slowi ng the writes down. Create Dynamic SRDF Dev ice Pairs The Dynamic SRDF attribute can be selecte d when a device is first configured, or after it is configured using the Device Attribute Definition configuration dialog. Dynamic SRDF devices can be paired wi th similar devices on a remote array for replication. Unlike static SR DF definitions, the pairing rela tionship can be undone and changed without a configuration change. Dynamic SRDF must be enabled on the Symmetrix w hen the arra y is firs t configured, or it can be enabled using Solutions Enabler.

In the example, two devices on the local array have been chosen to be paired with two similarly- numbere d devices on the remote array. The Properties view Configuration column shows that they are currently not SRDF devices, but the Dynamic RDF Capability column shows that they can become either R 1s or R2s. To configure them for SRDF, launch the Create Dynamic Pair dialog by right-clicking on the Symmetrix and choosing Data Protection > SRDF >Create Dynamic Pair from the menu. Then choose the source and target arra y from the pull- down lists, and the RA group number. Also choose the type of local device. Clic k OK to assign individual pairs. Create Dynamic SRDF Dev ice Pairs In the ne xt page of the Create Dynamic Pair dialog, choose pairs of devices to become SRDF- capable. Choose a device in the local column and a list of eligible devices will appear in the remote column. Eligible devices are the same size as the local device, be the same configuration if a Meta device, are marked as being Dynamic SRDF capable, and not already a me mber of an SRDF pair. Click the remote device and click Add to defi ne the pair. Repeat for a ny other pairs you would like to create. Then choose the initial s ynchronization mode to place the devices in: Synchronous, Adaptive Copy, or Asynchronous. Also choose which device (R1 or R2) to invalidate and lose the data. After the changes have been made, the Proper ties view shows the Status of the R2s Write Disable d, the Configuration of all devices is an SRDF type, and the Parame ters column shows Dynamic SRDF.

SRDF/A synchronous SRDF/Asynchronous is a disas ter recovery solution that provides good application res ponse time while consis tently replicating data. Database disas ter recovery depends on consistent data: data that has been written to tablespaces and logs in order. Synchronous mode guarantees consistent replication, but cannot be used over long distances due to the performance penalty. The adaptive copy modes can be used over long distances, but writes might be transmitted in any order. SRDF/Asynchronous marks incoming writes as par t of a “delta se t:” for a fixed period of time, all writes received go into the curre nt delta set. Writes received after the time expires go into the next delta set. In this way, the writes in a particular set are known to be consistent as of the time that the set expired, even though the Symmetrix does not log the exact time that each write is received. In other w ords, the delta set that expired at 16:35:00 contains a group of writes; we cannot tell what order they arrived in, but we know that they represent the exact state of changes to the database as of 16:35:00. While set N is being built, the previous set (N-1) is being tra nsferred across the SRDF links. At the receiving site, the incoming writes are also marked as being part of set N-1. The writes may be transferred in any order that is efficient for the RDF directors. If a disaster occurs to stop se t N-1 from being completed, it must be discar ded since the writes wi thin the set are not ordere d. When the transferring N-1 set is finished transferring (the fixed cycle time expires), it is marked as a comple te set (N-2) and the tracks mar ked for destage. If a disaster occurs, se t N is completely lost and se t N-1 must be discarded since it is incomplete. Howe ver, set N-2 represents a consistent write set as of the time it expired, which was a t most two cycles in the past. Using the default cycle time of 30 seconds, this means that the R2 devices will have a consistent, rec overa ble database that is at most one minute out of date with respect to the source database.

SRDF/A infor mat ion in SRDF view SRDF/A pairs are managed much like other SRDF pairs. You can issue fail over, fail back, split, establish, and restore commands using the dialogs we have already seen. This e xample shows the status of some SRDF/A de vices in the SRDF View. You can see several indicators that these are SRDF/A pairs. The Columns relevant to SRDF/A are: * Pair State: Consistent or Inconsistent * Asynch. SRDF: Should be Yes for SRDF/A de vices * Consistency Protection: Enabled or not * R2 Consistent: Yes or No * Uncommitted trac ks * R1/R2 Time Log * Mode: Asynchronous indicates SRDF/A mo de. SRDF/A Disable

When performing SRDF/A Disable or Enable actions, it must be performed against all volumes in the assigned SR DF/A RA Group. This can be done by: * Creating a Device Group containing all of the SRDF/A de vices and then performing the SRDF/A Enable or Disable a ction. * Performing the SRDF/A Enable or Disable action against the SRDF/A RA Group. * Selecting all the SRDF/A volumes and then performing the Disable or Enable SRDF/A a ction. After performing an SR DF/A Disable action, the SRDF view shows that Consistency Protection is Disable d for the SRDF/A devices. The Pair State and R2 Co nsistent fields will also change as updates are perform ed against the R1 devices. Disabling SRDF/A reverts the volumes back to their normal Primar y mode of operation (S ynchronous or Adaptive Copy). Cascaded SRDF AS you can see in this e xample, you can cascade SRDF devices to have 2 replicated volumes besides original. This is a new feature, before it was done by the use of TimeFinder in the middle of tw o SRDF Sessions. Enginuity 5773 has introduced Cascade d SRDF synchronization. A Cascaded SRDF configura tion consists of a Primary Site (Site A) replicating to a Secondary Site (Site B) and then replicating the same data to a Tertiary Site (Site C). A single device at the Secondary Site has both R1 and R2 features to continuously pass data to the Tertiar y Site. The core benefit behind a “Cascaded” configuration is its inhere nt capability to continue replicating from the Secondary Site to the Tertiar y Site in the event that the Primary Site goes down. This enables a fas ter recover y at the Tertiary Site. Cascaded SRDF uses the dual role R21 device on the Secondary Site. This ca n help reduce the number of devices require d for a 3-site “No Data Loss” extended distance replication solution. Synchronous mode is not supported on both legs of a Casca ded SR DF configuration. Asynchronous or Adaptive Copy modes mus t be used for one or both of the legs. This table shows all of the supported Cascade d SRDF configurations. Creating Cascaded SRDF Relationships • Create one SRDF relationship and a normal device • Add SRDF Mirror to middle device to make it an R21

Although an R21 device is trea ted as a distinct de vice type, there is no command to create one. Instead, you will add an SRDF mirror to an existing SRDF device to create a cas caded relationship. This makes the middle device an R21. Start with an SR DF pair a nd a re gular device. Each device should be on one of the three Symmetrix arrays involved in the relationship. Then use the Add SRDF Mirror command to add the regular device as a mirror to the middle SRDF device. If the middle device is already and R2, you will add the regular device as an R2 mirror. If the middle device is an R1, you will add the regular device as an R1 mirror. Once the configuration is complete, the middle device will appear as an R21. In either configura tion, two of the devices are dynamica lly changing their SRDF type; the Regular device becomes an SRDF device, and the middle device has an additional SRDF relationship added. For this reason, the devices used to create Cascade d SRDF relationships must have the Dynamic SRDF R1 or R2 feature enabled. Configuring Casca ded SRDF Relat ionships In this example, we will configure a Cascaded SRDF relationship using the devices shown here. In this test environment, only two arrays are being use d. Device 33 will become the R21 device. In a realistic environment, you wo uld follow these same s teps with devices that are on three different arrays. Notice that all of the devices are Dynamic SRDF R1 and R2 ca pable. This is necessar y for the R21 device, si nce it cannot be configured as a static R21 device. The R1 and R2 devices only need to be Dynamic R1 or Dynamic R2 capable.

We will start by creating the SRDF relationship between device 22 and device 33. This ca n be done using the Create Dynamic Pair feature. The first step of the dialog prompts the user for the source and targe t arrays, and the RA group to use. The user will create the R1 device on the local array, and the R2 device on the remote array. Configuring Casca ded SRDF Relat ionships The next step of the dialog is to choose the R1 and R2 devices from the arrays, and the synchronization mode. Finally, the user will choose one of the two devices to invalidate, or overwrite during synchronization. The resulting SRDF View shows that the R1 and R2 devices are now paired in S ynchronous mode. Creating R21 Devices The next step is to add an SRDF mirror to one of the devices. In this case, the user has c hosen to add device 33 as a mirror to device 44. After selecting device 44 and choosing the Add RDF Mirror (SMC) option from the SRDF Configuration menu, the user is presented with a ControlCenter dialog displaying all of the Symmetrix Mana gement Console hosts that can perform the tas k on the array. The Storage Agents for Symmetrix have crea ted this list by quer ying the Solutions Enabler processes that support both ControlCenter and Symmetrix Management Console. The user will choose a host from the list, and if necessary, change the port used for secure web communications. Creating R21 Dev ices The next dialog is a Symmetrix Mana gement Console dialog. Using this dialog, the user will select the RDF group and device to be the mirror of device 44.

Device 44 is already selected as the target Device Range in the dialog. The user has chosen RDF Group six. Choosing a mirror type of R2 means that device 44 will be the R2 device and the remote device will be the R1. The user use d the dialog to select device 33 as the remote device. The RDF mode for this pair has been set to Asynchronous. Creating R21 Dev ices Returning to controlCenter, you can view the result of the S ymmetrix Management Console configuration. Device 44 has become an R2, and device 33 has become an R21. TimeFinder/SRDF Quality of Service Internal TimeFi nder or SRDF s ynchronization can have an impact on overall Symmetrix performance. Although priority is given to any immediately needed host I/O request, a large business continuity synchronization will still cause a lot of traffic at the back-end. This additional traffic, even if low priority, will consume resources needed by host applications. TimeFinder/SRDF Quality of Service utility helps reduce performance problems caused by business continuity synchronization. It does this by inserting delays in between eac h scheduled track copy for TimeFi nder or SRDF. T he delay causes the business continuity task to take much longer, but by slowing down the rate of additional traffic, resources are free d up. There are two configurable delays in Quality of Service: TimeFinder and SRDF. For a non-BCV, the TimeFi nder delay controls how much time is inser ted betwee n copying tracks from the source to tar get. Only the source volume setting is considered: for example, the se tting for the Standard is c onsidere d for an Establish, and the setting for the BCV is considered for a restore. For a BCV, the TimeFinder delay controls how much time is inserted between copying tracks from the BCV to its mirror after a split (if the BCV is mirrored).

The SRDF delay controls how much time is inserted between copying tracks using SRDF. A gain, the source volume’s settings are the ones observed. Non-SRDF devices can not have their SRDF setting changed. Host Management * Capability licensed by Automated Resource Manager * Management tasks on remote hosts can be performe d via ControlCenter – Explore Windows and UNIX hosts – Extend File Systems – Mount/Unmount File Systems – List all Files a nd Directories – Backup a UNIX File System using tar – Execute shell commands on UNIX hosts – Perform s torage related commands – Explore a nd manage users, groups, ser vices, regis tries, processes, a nd other non-storage entities – …. and many more tasks. Exec ute Command – UNIX Alerts - Overview * Why Alert? - Data availability – Monitor and report on events that could lead to application outages – Every ControlC enter agent can monitor a number of metrics * 34 agents and 700+ aler ts * Alert categories – Hea lth * Examples - Database instance up/down, Symmetrix service processor down, Connectivity device port status – Capacity * Examples - File System Space, File/ Directory Size Change – Performa nce * Examples – Symmetrix To tal Hit %, Host CPU Usage * Alert Matrix available on EMC Powerlink we bsite

Def ine an A lert Def ine A lert Instance The Alert Life Cycle refers to the sequence of typical e vents in an aler t’s life. It starts when an alert is defined with the configure d parame ters show n in this illustration. We will discuss these parameters in detail later, but a quick glance shows that the alert can be configured to detect when an event happens or a critical measure mee ts some thres hold. The condition of an event alert is either “True” or “False,” while the condition of a threshold alert is a numeric value that is compared a gainst a meas ure. In either case, you can configure up to five severity levels. You can also choose which Console Views display the alert information. Before a nd After settings can be specified to handle short spike aler ts. For most alerts, you can specify a schedule to control how frequently the objects are monitored. Some alerts are marked as “Agent Controlled.” The schedule is contr olled by the agent in that case. An optional management policy can be used to route the alert to certain Console users—the default is for all Console users to see the aler t. A management policy can also deliver an alert by email or SNMP. An optional autofix can be added to provide some kind of resolution. An autofix runs on the agent hos t when the alert first triggers. The Source and Apply To tabs of the aler t configuration are use d together to specify w hat objects the alert definition monitors. Alert Triggers Once an alert is defined, the agent will monitor the metric based on the schedule. When the event has occurred or the measure is found to be within one of the thresholds, the alert triggers or becomes active. Several things can happen when an alert first triggers. The Alerts View or At A Glance View might be updated to display the new aler t, if those options were selected in the alert definition. A management policy might restrict what Console users see this information. In the Alerts View, the “Created” column will be set to the date and time the alert triggered. If a management policy that specifies email or SNMP delivery is speci fied, the email or SNMP trap will be sent. If one or more autofix scripts are specified, they will r un on the agent host that detected the alert. If more than one agent can monitor the same o bject, the one currently designated as the “Primary” executes the autofix. Load balancing and failover might make any of the agents that can monitor the object a primar y agent. During the time the aler t is active, it can be actively managed by ControlCenter users. A user can acknowle dge the alert, assign ownership, attach a note, or perform other tasks to help document the resolution process.

Alert Updates At the next scheduled monitoring time, the agent checks the condition again. If the measure is still at one of the thresholds and it has c hanged value, the alert will be updated. Several things might happen duri ng an update. The record in the Alerts View or At A Glance View will be updated with new information—a new record is not created during an update. When the measured value changes, the “Las t Modified” column in the Aler ts View is updated with the current date and time. You can use the “Las t Modified” column to quickly tell how recently something has changed. But be war ned: the “Last Modified” time will also change when any property of the active alert changes, including when a user performs a management action. A manageme nt policy will e xecute again during an update. If a Console user is specified by the policy, this simply mea ns that the Alerts and At A Glance Views will be updated with any changed information. If email or SNMP is specified, a new message or trap will be se nt that carries the new measure value and se verity information. This helps keep users notified about the status of the measured value. An autofix is never run during an update. It is only run when the aler t is first triggered. Remember, an update happens when the measure changes. If the meas ure of a thres hold alert has not changed, the e vents on this page will not happen. Since “True/False” aler ts do not have measured values, a n update never happens for such aler ts. The Aler t Life Cycle of a True/False alert includes Trigger and Clear, but not Update. Alert Cleared An alert might self-clear during a monitoring period if the condition is no longer met. This typically happens with thres hold alerts when the meas ure is no longer within any of the thresholds, though not all thres hold aler ts self- clear. An alert can be manually cleared by a user also. Several things happen when an alert is cleared. The alert is removed from the Aler ts View and the At A Glance View. The alert is logged in the Alert History View. T he complete history of the alert is available in this view, including the first trigger time, times of severi ty changes, and time whe n cleared. Any notes a pplied during management are also viewable. Aler ts are retained in the Alert History View for a time period specified in the Alert Data Retention policy. By default, this policy re tains the history information indefinitely. Once the aler t has been cleared it is eligible to Trigger again, starting the alert lifecycle over. Threshold aler ts typically sel f-clear when the value is no longer wi thin a threshold, but True/False alerts do not typically self-clear. They remain active even when the e vent is no longer detected. Only by manually clearing these alerts will they become inactive.

Configuring A lerts * Alert Definitions – Defined alerts – State: enabled/disabled * Alert Templates – List of all possible metrics for which an alert can be define * Autofixes – Scripts that run automaticall when an alert triggers – Requires Automated Resour Manager or StorageScope li * Management Policies – Notify CC User – Send e-mail – Notify S NMP * Alert Data Retention Alert Definit ion * List of active alerts currently defined * Enabled alert – Red “Bell” * Disable d alert – Gray * Many aler ts for most agents are pre-defined and enabled when agent is installed. * Refer to EMC ControlCe nter Aler ts Matrix for a breakdown of all alerts. The Usage view of any defined alert shows i f a particular aler t is enabled in the Is Aler t Enabled? column. The Usage view is one of the c hoices under the ECC Administration pull down. A red bell indicates an enabled alert as well. The Properties view of a defined aler t shows if a Management Policy is associated with an aler t definition, when it was modified and who modified it. Both of these views can be exported into a CSV file which can then be imported into an spreadshee t like Microsoft Excel. Exporting these two views prior to making changes is extremely useful to record of the state of the alert definitions. To modify an existing alert definition, right click on the aler t and select Edit Aler t. The Aler t editor interface pop-ups. The interface has five tabs. * The Properties tab gives you information about the aler t. The information on the proper ties page cannot be edited. * Alert Type: The four types are Count, Interval, Rate and State. * Alert Category: Alerts could be Heal th, Ca pacity or Performance related from object types of Host, Storage, Connectivity etc. * Las t Modified: When was this alert definition last modified. * Who Modified: The ControlCenter Console user w ho last modified the aler t definition. * Description: Gives you a brief description of the alert. The online help will provide more information on the aler t.

Alert Definit ions – Usa ge and Propert ies Views Each alert definition has a unique descri ptor. T he unique descriptor is assigned automatically by ControlCenter, it star ts at 00 for the first definition of a specific alert, and is increme nted for new definitions of the same alert. The Director Status Alert is an example of a State Aler t. Editing an Alert Def init ion Source and Condit ions

Source Tab: The informa tion to be specified in the Source tab depends on the specific alert. For the Director Status Alert shown in this e xample, you can establish which objects should be monitored. The recommendation is to leave the Source tab at the default value of the asteris k wildcard. The Apply To tab (discussed in the next slide) allows a more granular filtering of the spe cific objects that one needs to monitor. Condit ions Tab: There are five levels of severity that can be configured for ea ch alert definition: (1) Fatal, (2) Critical, (3) War ning, (4) Minor, (5) Informational. Thresholds could be set up for eac h of the severity levels. For each severity level, the notifications can be se nt to the Aler ts View and the At A Glance View or, alter nately, to the At A Glance View only. If both the Alerts view and At A Glance view boxes are unchec ked, the alert does not trigger for that severity level. The Before and After values are used to control alert spikes—situations in which a resource temporaril y exceeds a trigger value, and then quickly falls within acceptable ranges a gain, or a resource briefl y goes offline, and then comes back online. Use these fields to pre vent being inundated with false aler ts. Before specifies how many consecutive times the alert conditions must be met before ControlCenter sends a notification or alert. After an alert or notification has triggered, ControlCenter uses the value in After to determine how many consecutive times the conditions must be false before ControlCenter removes the alert or notification. The aler t schedule determines how often ControlCenter evaluates the alert definition. Actions and Apply To Actions Tab: The Actions Tab is used to specify the alert schedule and optionally to assign a Management Policy and an Autofix. We will discuss Management Policies a nd Autofixes shortly. Some A lerts will not allow the specification of a schedule, the schedule for such aler ts is controlle d by the agent. The schedule is chosen via the drop down list. The list will show all the pre-defined schedules. Schedule definitions can be edited and new schedules can be created if necessary. The schedule determines hooften an agent monitors a specifi c metric for threshold violations.

Apply To Tab: This tab is used to specify the objects, s uch as hosts, storage arrays, or network components, to which the aler t definition applies. You can either select individual objects or al l valid objects monitored by the agent by checking the Apply this alert to all applicable. box. If the Apply this alert to all applicable box is che cked, then any new o bjects w hich are discovered in ControlCe nter inherit the alert definition automatically. Finally, before sa ving the new definition (OK button) to enable the aler t, make sure that the Alert Definition Enabled? box is checked. Creating Alert Def init ion from Template Alert Definitions are created from aler t templates. Right clic k and select the Alert Template Æ New option to create a new Aler t Definition. The new alert definition interface wi ndow will pop up. This interface is almos t identical to the edit alert interface. The only difference is that the Unique Descriptor is not shown. The Unique descriptor will be automatically generated by ControlCe nter a nd appended to the name of the new alert definition when it is saved. This example shows a Capaci ty Type alert template from the Database Agent for Oracle using the Free % of Tablespace Alert Definition Template. The Actions Tab: As previously shown, the Actions Tab is used to specify the aler t schedule and optionally to assign a Management Policy and an Autofix. We will discuss Management Policies and Autofixes shortly. Some Alerts will not allow the specification of a schedule, the schedule for such alerts is controlle d by the agent. The schedule is chosen via the drop down list. The list will s how all the pre-defined schedules. Schedule definitions can be edited and new schedules can be crea ted if necessary. The schedule determines how often an agent monitors a speci fic metric for thres hold violations.

Apply To Tab: This tab is used to specify the objects, s uch as hosts, database instances, storage arrays, or network components, to which the alert definition applies. You can either select individual objects or all valid objec ts monitored by the agent by checking the Apply this alert to all applicable. box. If the Apply this aler t to all applicable box is checked, then any new objects w hich are discovered in ControlCenter inherit the aler t definition automatically. Management Policies: * What should ControlCenter do when an alert triggers? * Possible actions: – Display alert in the Co nsole of a specific ControlCe nter user – Send an e-mail message – Notify a S NMP management framework – Set up loops – Set up wait inter vals * Create new or edit existing management policies * Same policy can apply to multiple aler ts Management Policies control the wa y alert notification is handled. If no Management Polic y is assigned to an alert notification to all Console Users Aler ts View or At A Glance View. Management Policies a llow alert notifications to specified Console users, to a Framewor k application via S NMP, or to an email address. You can also set up looping features to repeat the notifications a fixed number of times, and insert timed wait steps betwee n the notifications. To create a new Management Policy right-click the Management Policies F older under Administration > Alert Management and sel ect New.

Creating/Edit ing a Management Policy To edit the policy, drag action icons from the left of the dial og to the mai n display. If you are specifying a Console User or Email recipie nt, remember that you can only specify one name in an icon box. You ca n use “*” to mean all Console users, but otherwise avoid wildcards. For m ultiple recipients, drag multiple boxes. The SNMP icon does not have any configurable parameters. You can edit the SNMP receiver parameters in the Integration Gatewa y Agent’s c onfiguration file. A manageme nt policy may be use d by more than one alert. If you change a management policy, make sure your changes are appropriate for all the alerts to which the management policy is attached. ControlCenter e xecutes the management policy steps in the sequence they appear in this dialog box, from top to bottom. ControlCenter executes the management policy steps when the alert first triggers, and again whenever the value of a thres hold aler t changes. The use of the loop and wait functionality is not recomme nded as an escalation polic y. Once begun, the ma nagement policy executes all of the ste ps whether the alert is cleared or not. Keep the ma nagement policy sim ple; specify Console users, e-mail recipients and SNMP receivers only. Assigning Management Policy to Alerts Management polices can either be assigned with a right click on the alert folder from the tree panel or in the Actions tab of the alert definition. The Mana gement Policy is displayed in the properties view for the alert.

Management Policy – E- mail & SNMP Not ificat ion Autofixes * Types of autofixes – System defined – User defined * User defined autofix – Create the autofix definition within the Console – Create the autofix script on the host * Attach the autofix to the alert through the Edit Alert dialog box * Autofixes always run on the agent that detects the alert An autofix is a script or other program that the agent runs when the alert first triggers. A few System autofixes exist for Windows hos ts. Two of them manipulate the Wi ndows Event Log and are tied to the Host Agent for W indows Event Log alerts. The other System autofix restarts a Windows Service, a nd is related to the Service Failure aler t. Any other a utofixes have to be defined by the user. Do this by specifying the name of the executable and any parameters to pass and attaching it to the alerts. You must also install the executable on the agent host. The autofix will be e xecuted by the agent that detects the alert condition. If multiple agents monitor the same object, any one of the agents could be the primary at the time the event occurs. Remember to install the executable on all of them. An autofix can created by right-clicking the Autofixes f older and se lect ing New. Parameters can be passed from ControlCenter to the Autofix scripts. The parameters are: * &METRIC is the alert name. * &LEVEL is the se verity level of the alert, in string format: Fatal, Critical, Warning, Minor, and Information. * &KEY is the alert key (or managed object that the alert is acting on.) On UNIX and Windows, if the alert has more than one key, then append a number to &KEY for eac h key you want to pass, for example: &KEY1, &KEY2, and so on. * &VALUE is the value at which the alert triggered.

Creating a User Def ined Autofix EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. Attaching an Autofix to an a lert UNIX A utofix Example: * /usr/ecc/autofixes/vgextendfs &METRIC &LEVEL &KEY &VALUE #!/usr/bin/ksh TIME=`date` print "$TIME" >> /tmp/vgautofix.out print "Metric: $1 Filesystem Free Size: $4 %" >> /tmp/v gautofix.out if [ $2 = 'F ATAL' ] then print "Severity: $2 F ilesystem $3 has been increased by 4 M B" >> /tmp/vgautofix. out else print "Severity: $2 F ilesystem $3 has not been increased" >> /tmp/vgautofix.out fi * Output from vgautofix.out Thu Jan 17 14:1 3:23 EST 2006 Metric: MAR.FileSystem.Space.PctFreeSpace Filesystem Free Size: 10.032552 % Severity: MINOR Filesystem /istda ta has not been increased

Setting Thresholds You can also create aler t definitions using the Edit T hresholds dialog box. T he Edit T hresholds dialog box allows you to create or m odify multiple alert definitions at one time. In addition, the dialog box shows the category for each metric. T he category determines i n which At A Glance view chart a notification will display (for example, Storage System Performance or Host Capacity). To a ccess the Edit T hresholds dialog box, ri ght-click any object and select Alert Thresholds, Edit Thresholds. Using the edit threshold window will crea te a new alert in the tree panel for each unique alert level specified. In this example, the Total Hit% Metric for Symmetrix ‘156 is being se t. The Critical le vel has been changed to 20. Clicking OK results in the creation of a new aler t definition in the Alert Definition folder for the Storage Agent for Symmetrix. The resulting definition is shown in the next slide. The result of setting thresholds is the crea tion/alteration of the alert definition. In the previous slide, the Total Hit% threshold for Symmetrix ‘156 was c hanged. This sl ide shows the Alert Definition which was created as a result of setting the threshold.

Monitoring a nd Handling Alerts * Alerts View – Chart View – Acknowledge – Clearing – Assign * Alerts History View – Notes * At A Glance View – Filtering Active Alerts View This shows the Alerts View. From this view you can quickly see the cause of the alert, which object is affected, and what the level of the alert is. For alerts, this is the main functional view and most of the management functions can be started from this view. Alerts can be displayed in the Alerts View in a number of different ways, a few are lis ted below: * Clicking the All Alerts button in the top right hand corner. T he All Alerts button populates the Alerts View with all the active alerts. * Switch the target panel to Alert View by clicking the Alerts button in the taskbar. Then drag selected objects into the targe t panel from the tree panel. Dra gging selected objects into the target panel displays alerts that relate to those specific objects. This is one way to filter the number of alerts shown in the alerts view. * Right click any object that shows a s tatus ico n and choose Alerts. This populates the target panel with the active alerts that are specific to that object. Description of the Columns: * Alert State: Yellow Bell – New alert (Text will be in Bold font). Gray Bell – Acknowle dged or Assigned Aler t (Text is in normal font). Note: A paper clip icon is shown here if a note is assoc iated with this alert. * Autofix State: If an autofix is associated with the alert then this column will indicate the status of the autofix − Running – Wrench/Spanner icon − Success – Wrench/Spanner with green check − Failure – Wrench/Spanner with red X * Severity: Ranges from 1 to 5. 1 = Fatal, 2= Critical, 3 = Warning, 4 = Minor, 5 = Information * Object Name: Host, storage array, network component (such as a switch), or other ma naged object for which the alert triggered. * Message: A description of the condition that caused the alert. Look here for information about the specific resources affected.

Active Alerts View Active Alerts View Options Acknowledging an Alert

Assigning An Alert Adding Notes to Alerts Searching Alert Notes

Clear ing an Alert Alert History View Alert History of a Particular Alert Instance

Setting Alert Data Retention Disabling an Alert Def inition Alert Chart View

Filter ing Active Alerts At A Glance View At A Glance View – Hea lth Dr ill Down

At A Glance View – Capac ity Drill Down Alerts Disc ussion * There are over 700 alerts – Too few aler ts and problems will not be found – Too ma ny aler ts and they will be ignore d * We nee d to figure out which aler ts are bes t for each situation – There are no formulaic “best practices ” – Base d on the environment including, other monitoring products, which agents are installed and the organizational s tructure o f the gro up using ControlCenter * ControlCenter alerts are broadly divided into 3 areas – Hea lth – Performa nce – Capacity Hea lth Alerts Capac ity Alerts * Array * Array – Har dware – Symmetrix virtual provisioning thin pool – Software alert * SAN (Connectivity Objects) – CLARiiON Raid Group – Device/Port Status * Host – Zoning/Fabric – File system * Host – Volume Group/Disk Group – Process/Service failure – Swap Space – PowerPa th – Quota * Applications * Applications – Database Instance up/down – Database tablespace – Backup application errors – Backup data size c hange * ControlCenter Server alerts Which Alerts Should You Enable? * Finding the most useful alerts re quires understanding of – What problems have led to outages – How issues will appear from different perspectives – What alerts are a vailable

* Which alerts provide the most useful information? – Are all of them needed? – Are some redundant in this e nvironment? * Are other tools being used for alerting? – Opera ting Systems – Applications – Frameworks Fra mewor k Integration Architecture ControlCenter Framework Integration is SNMP based; C ontr olCenter is capable of forwarding alerts as SNMP version 1 traps to any S NMP Trap recipie nt. The standard S NMP Traps defined within the FibreAlliance MIB are used. The ControlCenter Integration Gatewa y agent is the interface between ControlCenter and the external framework application. It sends selecte d alerts as traps, a nd also responds to “get” requests for information. It can also be configured to write events to the Windows Application Event log. This feature is use d for Windows integration. Framework tools can be passive or active. Passive frameworks listen for traps from ControlCenter, and post them to an events display. Active framew orks typically listen for a nd post traps also, but they also query ControlCenter to show the status of every object. Active tools show the entire environment, while passive tools only show fault events. We discuss some of these topics in more de tail in the next few slides. Supported Fra mewor k Applications Integration Gateway Agent can send SNMP v1 traps to any receiver software, supported or not. BMC Patrol and Microsoft Operations Manager or System Center Operations Manager are the only framework applications currently supported. These applications have been tested with ControlCenter, and you can download integration packages that will seamlessly adapt these products to dis play the ControlCenter alerts. There are other a pplications that EMC supplies integration packages for, but are not supported. These files are provided without support to help guide administrators w hen integrating ControlCenter i nto their application. The packages should work well for the versions specified in the release notes. If you have a different version or an unusual configuration, you may have to start with the package files and then do some ma nual editing of the configuration. Any other s oftware not shown here s hould still be able to receive traps from the Integration Gatewa y Agent if it conforms to SNMP version 1. You will have to configure the appearance of such software manually, since no integration packages exist.

BMC Patrol is a supported framework application that can be modified by an integration package. Patrol is an active framework tool. This mea ns it can recei ve traps from the Integration Gatewa y and post them in an event wi ndow, and also query the Integration Gatewa y to retrie ve the status of all of the objects managed by ControlCenter. This gives Patrol the ability to display a dashboard of your entire ControlCenter environment—even the objects that currently have no faults. The Integration Package for Patrol installs and configures the ecc3pi knowledge module. Patrol uses this tool to interpret traps and retrie ve information from the Integration Gateway. This saves the Patrol administrator from having to investigate what information is returned by ControlCenter a nd then format it appropriately. The main map of BMC Patrol shows the ControlCe nter o bjects or ganized into groups. You will find default groups like “Storage,” “Connectivity,” and “Hosts.” Other groups match the user-defined

ControlCenter groups. Drill dow n into one of these groups to show a status dashboard for all of the objects. C olored icons show the current aler t status of object. These colors c orrespond directly to the alert status in Contr olCenter. Patrol also shows the individual tra ps received from the Gatewa y Agent in the Event Manager dialog. You can see the time, objec t name, and alert message for ever y trap sent. Microsoft Operat ions Manager Microsoft Operations Manager is another s upported framework application that can be modified by an integration package. Microsoft Operations Manager does not use S NMP to receive information; it monitors the Wi ndows Application Event Log. The Integration Gateway can be configured to write alerts to the log with an identifying tag. Operations Manager searches for events with the matching tag, and posts them in its interface. A similar architecture is used by Microso ft Systems Ce nter Operations Manager. You will have to manually conver t the AKM rules file supplied in the integration packages to the new XML format used in Systems Center Operations Manager, but otherwise the installation is the same. These tools are passive-only: they simply display the alerts sent from the Integration Gateway Agent. They never poll the agent to find the status of the other o bjects. Install Integrat ion Gateway Agent The Integration Gatewa y Agent is pushed to any host having a Mas ter Agent, just like any other ControlCenter a gent. A prompt as ks for the network name of the framework application. Traps will be sent to this address. If the framework application uses a dis tributed configuration, make

sure the address you enter here is of the tra p collector, not the central application server. Ask the framework application administrator for the correct address to se nd traps to. You will notice that there is no way to choose the port or community string. At installation, the agent is configured to respond to “get” requests using port 1273 and community string “public,” and to send traps using the default port of 162 and community string “public.” To change these defaults, you can edit the configuration file after installation. Greater customization of the parame ters of the Integration Gatewa y can be done by editing the CNG.ini file (CS G.ini if the Gatewa y is on a Solaris host). Entries in this file specify the port number a nd community used by the framework software when querying the Gatewa y. The default port value for this software is 1273, not the traditional S NMP default of 161. This allows the Gatewa y to be installed on the same host as the framework application without a port conflict. Make sure you use the correct port number w hen attempting to read information from the Gatewa y. You can configure the Gateway to write alerts to the Wi ndows Application Event log by replaci ng using a value of “EMC_Alarms” in the “NT_EventLog_Key” setting. This is a required step for integra tion with Microsoft framew ork applications.

The recipient address designated when the age nt was installed is recor ded in the “trap_client_registra tion” setting. The entire se tting shows the address of the recipient, the port (default 162), severity (default 10), and state (set to ACT IVE to enable sending of tra ps). If you need to change the recipie nt or port, simply edit those parameters in the file. To add additional receivers, just duplicate the line and edit the address. The severity se tting can be used to filter the forwarding of traps by se verity of the ControlCenter alert. Remember to use ControlCenter to restart the Integration Gatewa y after making changes to the initializa tion file. Tro ubleshooting: If your framewor k software does not show traps or ma naged objects as e xpected, there are several troubles hooting steps you can take. First, make sure the expected alerts appear in the ControlCenter Console. If the alert management policy includes at least one Console user, the event should be visible there. If it is not, then of course it will not be forwarded to the framework application. You might check the Integration Gateway Agent log files listed above for a ny software errors. Network errors and issues that pre vent proper startup will be captured there. Some of the integration packages include a program named “ecc3pi_test.exe” which will sim ulate several of the Integration Gatewa y traps. These traps are sent from the location of the Integration Package install (where the program is), not necessaril y from the Integration Gatewa y agent. So it is a good tes t of the framework’s ability to receive a trap, but may not completely test the network between the Integration Gatewa y and the framework. When an active framew ork recei ves the sim ulated Cold Start trap, it will try to discover the ControlCenter ma naged objec ts at that address. If the Integration Gatewa y is not present on that host, the application will discover a n “empty” ControlCenter environment. This might have to be deleted from the application view. You might edit the configuration file to cause the Integration Gateway to record the events in the Windows Event Log as an additional troubleshooting step. By rea ding the Event Log, you can see what alerts the agent processed. The Integration Gateway also records all of the events that it attempts to forward in a file named “events.xml.” Any event listed there should have been forwarded to the framework receiver—if it did not arrive, check the address and port settings, the network connectivity, or the framework software itself. The gatewa y INI file contains a parame ter that controls the maximum size of this file. When the maximum size is reached, older entries are deleted.

Integration Gateway Event Log: events.xml StorageScope Features • Reporting built around storage management use cases • On-demand views show stora ge pain points • Scheduled re ports delivered by File, Email, or Print • Different levels of customization • IT object (host, switch, storage) and file level data collections combined in one database This is a more detailed look at the StorageScope architecture and its relationship to the other ControlCenter c omponents. StorageScope is considered to be part of the Infrastr ucture tier, although it is shown on a separate host in this e xample. The StorageScope Repository is populated with data from the ControlCe nter Re pository by the Extraction, Translation, and Load (ET L) process. Configuration and storage information about all of the hosts, applications, storage, and switches in the environment that are monitore d by the

agents are passed from one database to another. Certain data is time stamped to enable long term trend reports. By using this already-collected data, StorageScope avoids placing additional processing demands on the agent hosts. The ETL process typically runs once a day. The FLR Arc hiver performs the ETL process and also handles data requests from the user. It uses the ControlCenter Web Server to publish the user interface as HTTP pages. If the FLR Archiver is installed on a separate host from the ControlCenter Server (which also uses the Web Server for HTTP publication), a separate We b Server ins tance is installed. The only data that is not collected from the ControlCenter Repository is file level data. File le vel data is collected by the Host Agents a nd se nt directly to the FLR Arc hiver. T he file level data is stored as temporar y files until the next ETL process. After ETL is run, the file level data is loaded into the StorageScope Repository and viewable in the views a nd reports. The StorageScope Repository must be an Oracle 10g Release 2 database, just like the main Repository. No other databases are supported with this release. It can be installed from the ControlCenter install CDs, or the customer can purchase a nd install their own Oracle ins tance. Installing Oracle from the ControlCenter CDs does not require any additional license or cost, but you will not have complete administrative control over the database. But even when using your own database to gain administrative control, be wary of per formance issues. StorageScope is a demanding data warehouse-type application that will have significant performance effects on any other application using the same Oracle server. In most small environments, the StorageScope Repository can be installed on the Infrastructure host. The Reposi tory and the StorageScope Repository instances share the same Oracle server i n this case. In larger environments where many thousands of managed objects are cataloged, the performance demands requires the StorageScope Repository to be on its own dedicated server. The EMC ControlCenter Performance and Scalability Guidelines have complete details on the StorageScope requireme nts. The FLR Arc hiver is automatically ins talled on the same host as the StorageScope Repository. If you purchase and install your own Repository, EMC impleme ntation engineers will initialize a new instance and install the F LR Archiver. Two licenses is required for full functionality of StorageScope. Most of the data collection and processing is available with the standar d StorageScope license, but not the file level reporting capabilities. Those become active with the StorageScope File Level Reporting license, which can only be entered after the StorageScope license. The StorageScope File Level Reporting license allows two data collection policies to be enabled: The File Level Collection polic y records file-by-file details of standard filesystems mounted on hosts. Any Host Agent can enable a File Level Collection policy to collect data about its file systems or mounted shares. The File Level Collection for UNC C onnection polic y records file-by-file details of UNC shares

accessed across a network. This policy only applies to the Host Agent for Wi ndows. The File Level Collection Data Collection Policy provides file s canning similar to the old StorageScope FLR and VisualSRM products. There are several scanning depth options available in the Source tab when creating the policy. T he Scope of Data Collection changes how much detail is rec orded in the Repository. An All Files and Folders sca n loads everything, going through all the files and folders o n a per file system basis. Alternatively, you could opt for only a summary file sca n. A Folders Only scan examines the folder contents to record the number of files, their storage utilization, type, ow ner, and other details. But it does not store the information for e very file, it only summarizes the data by folder. You can also choose “Exceptional Files and Folders,” such as the top N lar gest or the top N oldest. You can enter the N value in the next line of the dial og.

The demanding nature o f the file level collections are made clear in the Performance and Scalability Guidelines. It shows the circ umstances under which the StorageScope components ca n be installed wi th the other Infrastr ucture components a nd w hen they should be on a dedicated server. In most cases, environments classifie d as small and medium by the Performance and Scalability Guidelinesca n have the StorageScope database and server installed on the infrastructure. Large environments must use a dedicated server for StorageScope. When using a dedicated StorageScope ser ver, the limit of the number of medium filesystems that can be added to File Level Data Collection Policies is 2,000. These scalability guidelines assume that the highest level of collection detail is reser ved for the critical files ystems. Seventy-five percent of the ma ximum allowe d filesystems should be monitore d using a F olders Only scope settings with no sum mary file type collection. Twenty perce nt can have the Folders Only scope with summary type collection, and only five perce nt can have All Files and Folders and file type summary. When StorageScope is installed on the Infrastr ucture, the total number of filesystems allowed may be less than 2,000. Since the exact number depends on the power of the server a nd the size of the files ystems, make sure you ask the EMC team that installed ControlCe nter w hat your limits are. In practice, you should turn on the “Folders Only” collections for all of your files ystems for so me period to help identify the critical filesystems. Once you have studied the environment for a while, you can enable the higher details j ust on those filesystems that are in danger of running out of space. The file le vel data collection policies ca n optionally collect information on file types. To determine the file type, the agent compares the filename extension to a list of user-defined types. You ca n manage the types in the Edit File T ype Definitions option of the Reports menu in the ControlCenter Console. When adding extensions, separate them by commas and do not use a period—just enter the text that appears after the last period in the file name. You can use a star to mean any characters. There is only one type definition list for all users, so consult your ass ociates before changing an existing type. Since the type cataloging is done during a file level data collection polic y execution, any changes to the type list will show up in the views, queries, and reports a fter the next policy execution and ETL pr ocess.

The several reporting methods in Stora geScope can be arranged from Novice to Expert in terms of difficulty and level of effort. Users ca n use one method to quickly spot trouble, and use a more detailed method to further investigate the iss ue. The Das hboar d and SRM Views pages of the StorageScope interfa ce provide quick, high-level information about your objects, their utilization, and storage trends. Reports show more de tail about the same things, and can show file level data as well. Built-in queries are similar to reports, but tend towar d more tabular data. Custom queries are fully configurable database queries. You can filter data from any of the object tables, and sor t and summarize the output. The wizard interface gives you much of the power of a SQL query without having to actually know SQL. Use custom reports to query the StorageScope Repository and format the output to meet your specific needs. You need to use the Business Objects Crystal Reports editor to create custom reports (not supplied with ControlCe nter). Once you have a useful report, you can add it to the StorageScope report list for automatic scheduling. Good knowle dge of Crystal Reports is re quired for this option, and you may occasionall y need some SQL programm ing as well.

For the most complete reporting available, you can query the StorageScope Repository with any SQL-based reporting tool. You have the complete details of ever y table of data this way, but of course you have to write the reporting solution from scratch. You can go to the Snapshots page under the Utilities menu to view the built-in Snaps hots or add a custom Snapshot. Any one of the 16 built-in Snapshots can be copied, modified, and then saved as custom snapshots, or you can create your ow n from scra tch. The original built-in Sna pshots can not be modified or deleted. The Snapshot Settings dialog pictured at left prompts for a T ype (Table or Chart), organization Category, and a Title. The data source of the Snapshot is the SQL query, which you will have to enter by hand. If you are not familiar with SQL coding or the StorageScope Repository tables you might just make a slight change to the code of a copied Snapshot. Or you might capture the code from a Query you developed. If you are more familiar wi th SQL coding, you can use the EMC ControlCe nter StorageScope Refere nce Guide to look up the names of the tables and columns when writing your own query. The SRM Views pages provide high-level summar y information about all of the objects in the StorageScope Repository. The y show basic configuration summaries, high-level storage allocation, “Top 10” storage issues, and trend graphs. Use these pages as the firs t step in your inves tigation to spot problem areas.

The Array views contain information about the properties, capacity, and usa ge of your storage arrays. The views also identify storage device capacity that can be reclaimed and the hosts to which array storage is accessible. The Thin Pools View provides an enterprise summary about the number and usage of thin pools i n the environment. This view gives very sim ilar information as the Arrays View does regarding total, used, and subscribed capacity for individual thin pools and the arrays on which the reside. Trending for these metrics are als o displayed in the Enterprise Summar y View. The Host views contain information about the storage ca pacity (internal and external) accessible to your hosts, the database applications residing on those hosts, and host file-level details. The Connectivity views provide information about the properties and port usage of the Fibre channel switches in your environment. The NAS views provide information about your NAS file servers, data movers and NAS file systems. Except for the tre nd gra phs, all the data in the SRM Views is from the most recent Extrac tion, Translation, and Load process. Unlike most of the rest of the reporting features of StorageScope, the SRM Views are not customizable i n any wa y.

Other SRM V iews * Hosts • 10 Hosts Most – 10 Hosts with Most Accessible Storage Dorma nt|Aged|Media|Temp Cap – 10 Hosts Using Most Accessible Storage * Switches * Hosts Applications – 10 Switches with Most Used Ports – 10 Most Used Databases – 10 Switches with Most Free Por ts – 10 Least Use d Databases – Switches with No Free Ports in 6 Months – Databases Full in 6 Months * NAS File Servers * Hosts File Level Storage – 10 File Servers wi th Most Use d File – File Systems Systems • 10 Most|Least Used – 10 File Servers wi th Least Use d File • FS Full in 6 Months Systems • 10 Most Dorma nt|Aged|Media|Temp * NAS File Systems Cap – 10 Most Used File Systems – Folders/Directories – 10 Least Use d File Systems • 10 Most – File Systems Full in 6 Months Dorma nt|Aged|Media|Temp Cap * Thin Pools – Files – 10 Most Utilized a nd Subscribed Pools – 10 Least Utilized and Subscribed Pools

ControlCenter Real-t ime Perfor mance Monitoring EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina. * Statistics can be displayed for: * Symmetrix - Overall performance, Host Directors, Host Director Ports, Disk Directors, Devices, Disks * Switches - Switch ports . Performance statistics in approximately Real-Time . Historical chart of data can be kept for up to se ven da ys . Measures that exceed performance aler t thresholds color-c ode the display The performa nce data is updated every few mi nutes according to the schedule in a data collection polic y. This a pproximately real- time view is good for analyzing the current status of the components. As traffic ra tes change, you will quickly see the effects and might be able to pinpoint the source.

Console Perfor mance Monitor ing Console Perfor mance Data Collect ion Policies Overa ll Sy mmetrix Perfor mance – Table

Tabular performance numbers are either displayed in real-time or e xponential formats. Real- time values are sim ply the last number read from the agent. Display of real- time values is the most accurate view of the object’s performance, but the values may tend to change frequently. Exponential values are averaged with the previous few values displayed, wi th an exponentially decreasing weight on numbers further i n the past. The exponential display shows the overall trend of the measure but not the actual value read from the agent. Exponential values tend to be more stable. Overa ll Sy mmetrix Perfor mance – Chart Setting/Editing Thresholds You can view the performance of the Host Directors and their ports by selecting the Host Directors folder and all the sub folders. The user has c hosen to displa y meas ures across the whole array, and als o measures across sub-objects. T he Host Directors folder has been displayed, showing the sum of the measures across all the host directors. Some individual host directors have being displayed (named “Front End Directors” in the display) to show the breakdown across these objects. F inally, some host director ports are bei ng displayed to show the I/O on the ports.

Symmetr ix Fr ont-end Director/Port Statistics You might combine a view like this with a Relationship view. Use the Relationship view to show which ports and directors your host is connected to, and then drag the objects into a Performance view to show the workload. Symmetr ix Bac k-end Director/Dis k Statistics Switch Port Statist ics – Table

Switch Port Statist ics – Chart Histor ica l Chart ControlCenter Perfor mance Manager * Performa nce analysis tool useful for troubleshooting, tuning, and trend analysis of the enterprise storage environment * Data can be collected for Symmetrix, CLARiiON, HDS, NAS arrays, Fibre Channel Switches, Oracle Databases, and Hosts * Much more detailed meas ures than real-time Co nsole performance monitoring—most complete Symmetrix performa nce analysis a vailable * Archive viewing is strictly historical—all charts are static displays of past performa nce events * Two ways to view performance archives: – Performa nce Manager tool – Detailed performance arc hive viewing tool * Contains many default char ts showing most commonly used performa nce meas ures * Custom charts can be created to focus on a particular application or group of devices – Automated reports – Selected Performance Manager reports in HTM L forma t

Archive Types Created by the WLA Daily Policy * Interval – Raw WLA Daily data; number of data points per hour determined by the WLA Daily Policy * Daily – One data point per hour (24 hours per archive) averaged from Interval data * Weekly – One data point per hour (24 hours per archive) averaged from one wee k of Daily data * Monthly – One data point per hour (24 hours per archive) averaged from one month of Wee kly data A sample Wor kload Analyzer Daily collection policy is displayed above. As wi th most data collection policies, the Actions and Apply To tabs can be used to specify the frequency of the collection and the ma naged objec ts it pertains to. An administrator has the flexibility to set different collection schedules for different managed objects of the same type.

Data Collection Policy – Daily Collections Getting Revolv ing Collect ions An Analyst data collection policy is used to schedule a future A nalyst collection. Most of the se ttings are very similar to the other policies, but the method used to set the schedule is not immediately obvious. None of the timing features at the bottom of the Ac tions tab are directly editable, making it appear that only the frequency can be se t here.

Perfor mance Manager * Displays archives in grap hical format * Many useful graphs included as default views * Custom graphs can be created by combining any measures * Contains interfa ce for customizing automated HTM L repor ts * Can be launched directly from the Console if both are installed on the same host Perfor mance Manager Communication * Communicates directly with ControlCenter Repository to determine location of WLA Archiver Agents * Retrieves list of arc hives directly from Archiver * Loads chosen archive to the local system for viewing (temporar y copy only) * Archive can be sa ved locally if needed

Perfor mance Manager – Accessing Data Views Tab Creating New Data V iews

Graph Data View Metrics Tab Links V iew

Configuration Tab Groups in Perfor mance Manager Saving Data and Graphs

Automated HTML Reports * Created and stored automatically by the WLA Archiver Agent * Published by the EMC ControlCe nter Performance Manager Re ports ser vice on the W LA Archiver Agent host * Viewed with a normal web browser – Good for quick looks at comm on performance features – Publishes performance information to a wide audience wi thout re quiring widespread Performance Manager installs * Configura ble – Add, remove graphs – Set thres holds to color reports according to severity of performance issue – Thresholds can also be used to trigger the creation of a report Automat ion Jobs Automat ion Reports Login and Selection Page

Automat ion Jobs – Reports Storage Allocation Steps Storage provisioning can be a complex process. T here are many variables that come into pla y, and many steps that must be taken to successfully incorporate new stora ge into the manageme nt umbrella of an opera ting system, and made useable by a database or application. Before we start to analyze a planning tas k, we need to unders tand ever ything that is involved with allocating storage. The above image brea ks the provisioning steps down into their basic parts. Below we discuss w hat is happening at each phase: Array Manage ment * Configure new volumes – This stage can be quite complex and includes such steps as car ving off logical volumes from physical disks and combining multiple logical volumes into striped or concatenated meta volumes. The complexity does not lie in the steps, but in the thought process behind them, for example things like what device type and emulation, but also calc ulating the performance impact on cache, director and device resources. * Assign volumes to ports – The mai n considerations here include ensuring that the devices are assigned to a s ufficient number of ports to support performance requirements, confirming that the port flags are properly set according to the host that will use the devices, and ensuring that you do not excee d any LUN limits supported by the Director.

Storage Array Management * Allocate volumes to Host – If Symmetrix Device Mas king is being used, you will need to configure the VCM database to allow the Host HBA to have access to the mapped devices. * SAN Zoning – You must configure the SAN zoning to make sure that the Host HBAs have access to the arra y direc tor ports where the devices are mapped. This step could include editing or creating new zones, updating the zoneset and activating the zone set to apply those changes. Host Storage Management * Volume Management –This stage includes such tas ks as editing configuration files, rescanning buses for the device, incorporating the new device into PowerPath control a nd editing volume groups. * File System Management - This step involves enabling existing files ystems to rec ognize the new storage that is now available. * Database/Application Management – The las t step would be making the database or application capable of using the new filesystem space. The m ost common example here would be extending database tablespaces. Adding New Storage to a Server * You are tasked with adding storage for a new application to a ser ver in your environment. This implementation has the following requirements – This new a pplication requires a t least 3GB of storage – Storage must be striped across at least 8 array devices in order to support the expected performance demands – Storage must also be RAID-1 protected – The storage m ust be accessible via a t least two distinct data paths with full redundancy * As a storage administrator, wha t information must you gather during the planning phase of this rollout? * What planning must be done prior to the actual implementation? Imple menting Local Replica Solution * As part of a new backup plan, you have bee n asked to implement a local replication solution for an existing application server. A new server has been purchased in order to act as a centralized backup host for se veral applications. * As a storage administrator, wha t information must you gather during the planning phase of this implementation? * What planning must be done prior to the actual implementation? Manual Storage Allocation Storage provisioning can be a complex process. T here are many variables that come into pla y and many steps that must be taken to successfully incorporate new stora ge into the manageme nt umbrella of an opera ting system and made useable by an database or application. The above image brea ks the provisioning steps down into their basic parts. AutoPathing and Storage Prov is ioning Services

As we’ve seen, the provisioning of storage ca n be a constant challe nge for administrators in a storage area network (SAN) environment. Allocating storage, w hether it is for a new server or for an existing server, is often complex, time-consuming, and error-prone. Expert knowledge of multi-vendor storage arrays, SANs, and host system a dministration is required. Often, this expertise is lac king since skilled and trained personnel are in short supply. Even if skilled staff is available, a straightforward request for a dditional storage can take days to fulfill since stora ge, SAN, and host-specific expertise often crosses different organizational boundaries within a data center. ARM’s Storage Provisioning Services (SPS) provides a complete end-to-end solution by automating alloca tion actions from array to SAN and host management wi th a few mo use clicks. It automates the search for unallocated disks and the selection of the appropriate available capacity base d upon predefined policies. It then performs the complex tasks associated with storage provisioning in a heterogeneous SA N, including LUN masking, zoning, multipathing, and extension of file systems or volume groups. As a result, SPS enables users to provide “just-in- time” storage provisioning to mee t their Service Level Agreements. Not only does SPS expedite the entire storage pr ovisioning process, it also reduces errors as staff with a lower level of experience can allocate storage based on business policies and best prac tices. SAN Manager provides a utomation to perform Zoning and LUN Masking in one step using the AutoPathing wizard . Storage Prov is ioning Services Object ive * Challenges: – Respond quickly to end-user requirem ents for additional storage – Reduce administrative intervention for s torage-based alerts – Remove storage quickly * Automated Resource Manager – Quick and eas y policy-based storage allocation and deallocation – Automation based on your business rules and policies * SAN Manager – Quick and eas y zoning and LUN mas king using automation wizard * Meet time to provision, availability, and perf ormance goals. SPS allows a storage administrator to quickly meet the challenges of supporting a highly available storage environment. Using ControlCenter Automated Resource Manager, administrators can now quickly response to end-user s torage re quireme nts by using easy to manage policy based allocation tas ks.

It also allows you to reduce the overall administrative time and costs by automating the most common management processes through the use of pools, policies and wizar ds all base d on your business r ules, policies and processes. SA N Manager AutoPath * Automates the allocation of devices to hos ts – Creates required Zones – Creates required number of paths re quested – Activates updated Zone Set – Performs LUN Masking – Symmetrix – Devices must be mapped to front end ports – CLARiiON – Devices could be from the Mapped or Unmapped folders – Autopath can be used to allocate devices which have already been allocated to other hosts * Requires a SAN Manager license Starting AutoPath Wizard Launching the Autopath wizard is really very eas y. Simply select the mapped devices that you would like the host to have access to and the HBA that you would like to access those devices across. Next right click on one of the objects and from the dropdown list select Allocation Æ Autopath. At this point you need to comple te the wizard process presented on the following pages. Note: When zoning Symmetri x devices, you must select devices that are currently mapped to front end ports because Autopath will not perform S DR changes. Clariio n devices, however can be selected from the mapped or unmapped folders. Autopath requires a default zoning policy to be associa ted with each SAN Fabric that will affe cted by the Autopath actions. A warning as shown in step 3 will be shown if a default zoning policy does not exist for the affected fabrics.

AutoPath Wizard The review allo cation tas k scree n gives you your last chance to look over the changes before executing them. Using the Specifications tab you can review the objects that are to be effected. Here you confirm the devices and the HBAs that will be effected. The Path Details tab allows you to do one last re view of the paths between those objects that are to be defined. Once completed, you can choose to execute now or sa ve these changes in a task list to be executed later. SPS Overview * Enable “just in time” Stora ge Provisioning * Allocate storage based on business policies * Capture storage pro visioning best prac tices to enable less experienced perso nnel to allocate storage * Array support – CLARiiON, Symmetrix, HP StorageWorks (HS G80) * Host support - Reconfiguration – Windows, Solaris, HP-UX, IBM AIX, and VMware ESX Server 3.0.1

SPS Steps - Preparat ion 1. Determi ne strategy for pool design 2. Determi ne strategy for allocation policy definitions 3. Storage Pools must be created and populated 4. Allocation Policies must be defined 5. Users must be created and permissions assigned When planning and preparing for an SPS rollout you should follow the following steps. Determine strategy for pool design – This step is the sole objective that will be discussed in lesson 4, however the basic concept here is that you must decide how you want to split up your storage devices such that SPS tasks can pull storage and allocate it based on business processes. Determine strategy for alloca tion policy definitions – Like a pool strategy, you need to decide not only how your storage allocation policies will be crea ted, but how they will be used for different provisioning tas ks. Often these decisions are a direct result of the Pool design. For example, if the pools are designed by department, then the finance hosts will use allocation policies designed to pull devices from a pool reser ved for finance. If the pools are designed based on pr otection, then hosts who need mirrored protection would use allocation policies pulling from pools made up of mirrored devices. Storage Pools must be created and populated – Here, the administrator must go through the manual task of building and populating storage pools based on the design strategy defined and adopted in step 1. Allocation Policies m ust be defined – Again, here the administrator must go through the ma nual task of building the policies that will be used when creating storage allocation tas ks Users must be created and permissions assigned – The last step that must be perform ed is the assignment of permissions to those users who will have the right to create allocation tasks. Though this step may seem simple and perhaps obvious at firs t glance, this is w here SPS can truly change how businesses perform s torage allocation. Most application or database administrators currently request additional s torage via e-mail , phone calls or face to face discussions. If a storage admin decides to grant the storage request, they must then, from scratch, provision that stora ge. With SPS you can assign to those DBAs and Application administrators the right to create SPS tasks that request not only how much storage they want, but which devices and the paths that they will use. You can then have the storage administrator approve, deny or edit those tasks. SPS Steps - Execut ion 1. Launch SPS Allocation Wizard a. Select how much stora ge b. Which allocation policy c. Which host 2. Create Tasks and Task lists 3. Execute Task Lists When it is time to actually alloca te storage to a host or filesystem, the process is broken down as follows: Launch SPS wizard – Launching the wizard is as sim ple as right clicking on a host and drilling down to Storage Allocation. Once the wizard has launched you will need to provide it will information regarding how much storage you would like, which allocation policy you would like to use and which hosts to include (could be multiple hosts and might include backup hosts if BCVs are to be mapped as well)

Create Tasks and add to tas k lists – Once you have specified what you want allocated, you will finish by saving this request as a task and place it into a tas k list. Task lists allow you to create multiple changes ahead of time and then execute them later during predetermined off-peak hours or sc heduled down time. Execute task lists – Once you are rea dy to commit the changes, you sim ply need to execute the task lists and all the tasks within it will be run. Storage Pools Storage pools are groups of storage devices that SPS will search for a vailable storage. The first step to using SPS is for the administrator to categorize storage devices and create storage pools for each category. Storage pools can be based on device ownership, device per formance, device type, devices assigned to specific geographic locations or data centers, or any other lo gical grouping that a customer w ould need. Once the pools are created, the administrator populates the pools wi th the appropriate devices or other nested pools. Nes ted pools ca n be used to arrange the pools into any format that makes sense in the user environment. For example, a user may choose to use a forma t such as Data Center/Depar tments/Applications or Location/Application. The contents of the pool must be storage, but can be across arrays and array types. For e xample, an administrator can crea te a storage pool for a given business unit, such as Development. This particular business unit might only use HP StorageW orks storage. After stora ge pools are created, the adm inistrator can create all ocation policies that use these storage pools. Storage Pools - Rules • A device can belong to only one pool at a time. • A pool can contain either devices or other stora ge pools. • A storage device can be moved between pools. • A storage device remains in a pool, even after allocation. • A pool can contain devices across multiple arra ys and array types. • A pool can contain specific devices or entire arrays. To create a Storage Pool use the following steps: 1. Open the Storage Administration folder. 2. Right-clic k Storage Pools and select New >Stora ge Pool. 3. Rename the new storage pool folder to a descriptive pool name. 4. Add devices to the new pool by dragging and dropping the devices from the Console to the pool.

Storage Pools – Creation Allocat ion Po licies SPS simplifies the provisioning process by enabling customers to provision storage based on business r ules. These rules are specified within the ControlCenter alloca tion policies. Allocation policies contain all of the general criteria for storage allocation requests. For e xample, a allocation policy for an OLTP application that requires premium-level storage could be created. This might mean that the application is only alloca ted RAID 1 storage with four paths betwee n the host and array with remote replication support. Another allocation policy could be created for telemarketing file ser vers that require lower-level storage. This mi ght mean that these file servers would only be allocated RAID 5 storage with two paths between the host and array with no replication support. Regardless of how you choose to create your policies they all must be configured with the following information: • Replica class • Storage Pool • Type of storage • RAID Level • Number of paths Allocat ion Policies – Creation

Allocat ion Po licies – Policy Name a nd Options • Storage Pool —Select the group of storage devices within w hich SPS will search for devices for each of the replicas. • Storage Type —Select the type of storage to be selec ted from the specified storage pool. • RAID Level —Selec t array-based protection level for the LUN to be chosen. Options, such as RAID1 and RAID 5, vary depending on storage type selected. • Number o f Paths —Select the number of paths to be created between the ser ver and storage. For Symmetrix and CLARiiON systems, you can specify up to 32 paths. On HP StorageWorks arrays, specify one path since multipathing is not supported in this release. • Mapped Device Only (Symm only)—Selected when SPS should only searc h for devices that are already mapped to front-end array ports. This feature only applies to the Symmetrix system. • Zoned Storage Only —Selected when SPS should only search for devices on ports that are already zoned. This constraint is use d to force new devices to come from arrays that are already in use or arrays that are prepared for use by pre-zoning them to the host. • Disa ble Host Actions —Selected when SPS should not run host commands. This can be used when the Storage Administration and Host Administration are separate, and the host functions should not be done as automatically as par t of the automation process. Create New Storage Group (CLARiiON Only) – Selected when SPS should create a new storage group for Clariion device masking if a group does not currently exist. If this box is not selected the device will only be allocated if the tar get host iscurrently a member of an existing stora ge group.

• Add Storage to Host(s) —The host(s) selecte d in the navigation tree when the wizard was launched. Additional hosts can be added via drag and drop from the Console. If multiple hosts are in this field, the same s torage will be allocated to each of the hosts. • Storage Policy —Select the Allocation Policy that applies to the specified host(s) and/or application to run on the host based on business re quireme nts. The Alloca tion Policies editor/crea tor can also be launched from this dialog box by clicking Edit or New. The default Allocation Policy is show n. • Amount to Allocate — Indicate the am ount of storage nee ded. Available options are at most “x” GB, at least “y” GB, and a range. • Requested # of Devices: Range —Indicate a range for the number of devices that SPS should return for the allocation request. You can use these parame ters to specify a si ngle large volume (by specifying a range of 1 to 1) or a greater number of smaller volumes (by changing the “from” value to the number of volumes desired). Multiple devices might be selecte d if you plan to place the devices in a host logical volume group, for example. SPS searches for storage devices and paths that will satisfy the se lected Allocation Policy and additional criteria. SPS displays the results of the query in the Details of Proposed Path window.

If the policy being used for this allocation tas k specifies a local or remote replica, the dialog on the left will appear. Here you can choose to defi ne which host the BCV or R2 will be mapped to for recover y or backup purposes. It is important to note, however that this step is not mandatory. In the left window, select the local (or remote) replica. In the mi ddle window, sele ct the host that you would like the replica to be mapped to. Once you have made your selection, click on the add button and confirm that the Primary device host and repl ica device host are correct before clicking the Next button to move on. After selecting Replica Hosts click Next. The wizard will then begin searching for available devices and paths. If no suitable devices are found in the Storage Pool specified in the Alloca tion Policy selected then the dialog on the right will appear. T his dialog is useful in finding out why no suitable devices were found. In this example the: We as ked for at leas t 0.5 GB and enough BCV de vices were not available to give us 0.5 GB, but the log shows that one BCV of 449 MB was available. So we c ould step the SPS Wizard back to at for “A t Most” 0.5 GB. Dev ice Gr oup Selection If replicas were assigned using this task, you have the ability here to specify which device group you would like to make these devices a member of. If you are performing this provisioning tas ks for the purpose of increasing the storage for an existing application, simply add them to the device group that applications current de vices are a members of. If however you are alloca ting devices for a new application or files ystem, you might need to create a new device group prior to running the task wizard. The reason for this is that on this s creen you cannot create new device groups, only assign devices to existing ones.

Review Allocat ion Tas k Exec ute Tas k Later • Allows tasks to be ba tched • Multiple requests in a Task List get executed toge ther • Separate permissions to sa ve and execute With SPS, provisioning re quests are processed by creating storage allocation tasks. When you create a task, you save it as part of a task list. You can group se veral tasks together i n a task list. The advantage to this is seen duri ng execution of the tasks. SPS groups similar actions within the tasks; for e xample, all Symmetrix disk reallocation (SDR) actions (mapping volumes to Symmetrix front end ports) will be grouped together and executed at the same time for tasks within the same task list. In addition, junior staff members can genera te tas ks to be reviewed and approved/executed by more senior staff. Naming of the tas klists could be used effectively to organize wor k: wf_create Create all the tasks under this task lists wf_review Move the tasks to this task lists once the change contr ol board approves i t wf_readytoexecute Move the tasks to this tasklist when it is ready to execute wf_execute Move the tas ks to this task if they are executed Put the change control reques t ID in the task name. It will much easier to tie the requests and ControlCe nter tasks. Reserved Volumes Once provisioning tasks are sa ved, the volumes and their LUN IDs are reserved. This pre vents the same volumes from being selected by another SPS reques t. The sam e volumes are unreserved after the task is e xecuted. Vol umes are also unreserved if a task is deleted. To re view reserved volumes select the storage pools and select Show reserved volumes in the right-click menu. There are multiple wa ys to configure storage, including SPS and low-level commands within ControlCenter, array-specific tools, and SYMCLI. SPS is unaware of these changes until a task list is executed. Prior to execution a process is r un to verify that reserved devices have not become allocated by other tools. To determi ne if there is a problem with some reser ved volumes before your normal mai ntenance window, follow these steps: 1. Right-clic k the target task list. 2. Select Rebuild Task List from the me nu. 3. The Task List is rebuilt automatically. If there are problems, you will have time to edit the appropriate provisioning task in order to select a different storage volume.

Exec ute Tas k List To execute a task list , simply right click on the task list from within the tree panel and select Execute Tas k List. After confirming the command you can view the list of steps and status for each task within the list as it is executing. If an error occurs during execution of a task list, you can be notified by a ControlCenter alert or by viewing the properties of the Tasklist. If an existing Symmetrix configuration opera tion or Optimizer process has a current lock on the Symmetrix then the tasklist will fail. To check for locks on a Symmetrix use the following symcli command : symcfg –sid nn –lock –lockn ALL list You can then address the error (normall y by waiting for the other task to complete) and execute the task list again by right clic king on the tasklist and selecting Re-Try Tasklist. Deallo cation policies define the actions the Storage Provisioning Services wizard should perform when deallocating storage. Storage administrators can create different policies for stora ge with different nee ds or to control dealloca tion tas ks perf ormed by junior a dministrators. Use the Storage Provisioning Services wizard to deallocate storage from: Hosts ; Host devices ; Host adapters ; Host ports ; Unidentified por ts ; Storage ports ; Storage devices

Dea llocate Storage Extend a File System: In the situation where a host volume group has a dditional free space, ARM can automatically extend the file system using the storage that is alrea dy allocated to the host volume group. Alternately, this ma y also be done manually from the ControlC enter Console. In the situation where a host volume group has no additional space, SPS can increase the size o f the existing volume group by selecting additional LUNs and extending the file s ystem. Please check the Support Matrix for the supported OS Platforms, FileSystem types a nd Arra y Devices on which SPS will extend File Systems. SPS determines the attributes of the storage c urrently being used and, in the background, will propose a policy to be applied to the new storage for the file system extension Other SPS functions include: * Extend Volume Group * Extend Logical Vol ume

Storage Prov is ion Services CLI * Allows the administrator to integra te the Storage Provisioning Services functions with third party software s uch as a workflow s ystem. * Installed from ControlCe nter C Ds * SPS CLI examples: – SPS allocate –host seawin-01 –allocpolicy finance –tasklist wf_create –tas k payroll_project - atleast 100 – SPS extendfs –host losbe089 –fs /dev –atleast 10 – SPS extendvg –host losbe089 –vg vg00 –atleast 20 – SPS extendlv –host losbe089 –vg vg00 –lv lv00 –atleast 200 * Additional SPS CLI commands available to: – Manage tasks and tas klists – Research hosts, filesystems, volume groups and logical volumes * Refer to Storage Provisioning Services Command Line Interface Refere nce Guide for more details.

Storage Pool Des ign is Cr itica l * There are ma ny possible options * No one is necessarily better than another – It all depends on the customer environment and their needs y We will examine some pros a nd cons of just 5 options to illus trate the point: – Line-of-Business-based Storage Pools – Geographically-based Storage Pools – SAN-Fabric-base d Storage Pools – Array-based Storage Pools – Service-Level-based Storage Pools The next set of several slides attempt to show w hy the design of Storage Pools is critical for the successful implementation of the Storage Pro visioning Services ca pability of EMC ControlCe nter. First, there are many options from w hich to choose. Here we o nly list 5 possible ways to think about organizing and setting up Storage Pools. There are many others and the y could also be used in any number of combinations if so desired. So the first reason to focus on Storage Pool design is the large number of alternatives you can choose from. Second, each device can be placed in one, and only one, Storage Pool. The granularity of the Storage Pools that are chosen are going to impact the ease or difficulty with which this ca n be accomplished. If you have a Storage Pool that is to include every device in a specific storage array, it is eas y to drag and drop the array itself into the Pool and the setup is done. Howe ver, if the Storage Pools are intended to contain only some of the devices from only some of the stora ge arrays in your C ustomer environment, ea ch device or device range will have to separately be dragged and dropped into the chosen Storage Pool – clearl y more effort and more error-prone too. Third, changing from one Storage Pool design to another should be avoided. Moving the devices or arrays to a different pool organiza tion is likely to be time-consuming and also error-prone. It is much better to have thought about what is the ‘right’ or most appropriate Storage Pool strategy before the implementation so as to minimize the chances of this happening. Changing the Storage Pool design will also necessi tate changing the Alloca tion Policies too, adding even more administrative workload that could have bee n avoide d by good planning.

The designs presented here are not the only possible Storage Pool design philoso phies that are possible. T here are many others of which we have chosen just these 5 to share and discuss wi th you. Consider them as indicating some of the reasons that every Customer should spend time up- front identifying what might be relevant alternative Storage Pool designs and then determining the pros and cons for them in order to make the most informed and long-lasting se t of decisions about the Storage Pool that will be most appropriate to be deployed. This first design is based on setting up Storage Pools which are aligned with specific Lines of Business (LoB). Four fictitious examples are given for illustration. The intention of this design is to place into each Storage Pool only those storage array devices which a specific LoB is expected to nee d to be provisioned over whatever is the next planning period. For example, the Sales Storage Pool will contain the specific storage array devices the Sales LoB will need to use once its growth dema nds more than the existing allocation of storage de vices. This includes storage array devices of the right quantities a nd wi th the correct characteristics (e.g. STDs, BCVs and/or R1s for a Symmetrix array) to service the future pr ovisioning nee ds of the Sales LoB. Clearly this approach to Stora ge Pool design is most likely to appeal, at least initially, to a Customer that is focused on the differe nt LoBs that it has to service. The suggestion in the title of this slide is that this sce nario might be m ost appealing or rele vant for environments that have a single storage array or are restricted to a single geographic location – but in no way should that be considered as a hard and fast rule (it is more complex than that and the title is only trying to suggest an additional flavor concerned wi th the si mplicity of the storage environment we wish you to consider the pros and cons of with this design). Before you turn to the next page in the notes, please try to think of reasons why this design approach might be good and reasons why it might be bad, depending upon individual Cus tomer circumstances, of course. When you have done that, move on and re view the sam ple set of pros and cons we pro vide you wi th on the next slide.

This next desi gn is based on setting up Storage Pools which are aligned to specific storage arrays. Several examples are given for ill ustration. The intention of this design is to have just one array per Storage Pool and to place all storage devices from an array in its designated Storage Pool. The diagram a bove depicts several array pools sub-pools within an array type pool within a location Storage Pool. The Storage Pools wo uld contain all storage array devices with any technical characteristics (e.g. STDs, BCVs and/or R1s for a Symmetrix array) that reside in the designated array. If provisioning requires storage devices from a specific array it is easy to identify the correct Storage Pools and the relevant Storage Management Policies that would have to be setup to support this. Clearly this approach to Stora ge Pool design is most likely to appeal, at least initially, to a Customer that is focused on managing the arrays themselves. For this design, you have to decide in advance from w hich storage array you wish to provision the stora ge capacity. The suggestion in the title of this slide is that this sce nario might be m ost appealing or rele vant for environments that have to satisfy multiple ser vice levels across LoBs, locations and/or SANs –

but in no way should that be considered as a hard and fast rule (it is more complex than that and the title is only trying to suggest an additional flavor concerned wi th the si mplicity of the storage environment we wish you to consider the pros and cons of with this design). Before you turn to the next page in the notes, please try to think of reasons why this design approach might be good and reasons why it might be bad, depending upon individual Cus tomer circumstances, of course. When you have done that, move on and re view the sam ple set of pros and cons we pro vide you wi th on the next slide. This last design is an outgrowth of the previous array-based Storage Pool design. It takes the definition of a Storage Pool to a lower level i.e. based on different service level characteristics that can be provided from the different storage arrays and different stora ge array types. Six fictitious examples are given for illustration of lower le vel sub-Pools wi thin an array Storage Pool but they are likely only to represe nt a subset of any real Customer environment that used this type of Storage Pool design.

The intention of this design is to place into each Stora ge Pool only those storage array devices that have the same stated technical charac teristics e. g. for a Symmetrix: mirrored, high performance ST D devices or unprotected high perf ormance BCVs or stripe d meta STDs or striped BCV me tas or unprotected R1s. This m eans only storage devices with the appropriate technical characteristics have to be placed in the appropriate service-level-base d Storage Pool. Clearly this approach to Stora ge Pool design is most likely to appeal, at least initially, to a Customer that wants explicitly to provision storage devices with known and different ser vice level characteristics (performance, availability, security, etc.). Such Customers are likely already to ha ve a strong aware ness of and focus on the different service levels require d for the data their LoB applications need to access and to be orie nted to service management to meet agreed business needs for LoB application service levels. The suggestion in the title of this slide is that this sce nario might be m ost appealing or rele vant for environments that have a focus on provisioning storage that has different ser vice levels whether from one location or one array or not – but in no way should that be considered as a hard and fast rule (it is more complex than that and the title is only trying to sugges t an additional flavor concerned with the si mplicity of the storage environment we wish you to consider the pros and cons of with this design. Before you turn to the next page in the notes, please try to think of reasons why this design approach might be good and reasons why it might be bad, depending upon individual Cus tomer circumstances, of course. When you have done that, move on and re view the sam ple set of pros and cons we pro vide you wi th on the next slide. Symmetr ix Management Console (SMC) * Independent, light-weight, we b-based application – Simple and easy to use browser i nterface – Hosted on small Windows/ Linux server – Enables remote access and management from nearly any client * Enables access, configuration, and basic operation of Symmetrix arrays

– Supports all configuration capabilities of Sol utions Enabler/C LI * Supports multiple generations of Symmetri x – Enginuity version 5x68 and newer * Provides day-one support of new Symmetrix features when released * Adding full-fea ture ControlC enter does not re quire management data to be mi grated. SMC Funct ionality * Access Management – Manage users, permissions/roles – Symmetrix Access C ontrols * Configura tion Mana gement – Create devices, map and mas k devices, create device groups, set Symmetrix attributes * Replication Management – TF/Clone, TF/Mirror, TF/Snap, SRDF/S, SRDF/A, SRDF/DM, Open Replicator, Optimizer * Alerts and Monitoring – Monitor Device status, de vice attributes, operations status – Monitor array alerts

SMC Local User Accounts * The installation dialog includes the specification of the SMC Super User account – Default user "smc" with password "smc" * Password must be changed to avoid unauthorized access ! * Recommended to create other Administrators in place of Super User – Can specify different Super User name in installation dialog * The speci fied user mus t have a valid login to the SMC Server hos t * Authentication done by the SMC Server hos t OS * Menu: Administration > Local User Accounts – List existing usernames in a table – Add new user information (name and password) – Edit user information (enter a new password) – Delete selected user account(s)

Per miss ions and Roles * Menu: Administration > Permissions – List Symmetrix ID, User name, and Role entries – Add new permissi on entr y – Edit permissi on entr y (change role) – Delete permission entr y * Five Roles – Administrator, StorageAdmin and SecurityAdmin combined – StorageAdmin, full Symmetrix control – Monitor, view Symmetrix only, no manipulation of array – SecurityAdmin, add users and set permissions, no Symmetrix access – None, no access other than login (the default) * Super User – Created during installation – Only user with permission to set Symmetri x Preferences and LDAP-SSL – smc/smc username/password is a potential security hole if unchanged

EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina.

Let’s e xplore the creation of FBA Meta Devices. Right click on a S ymmetrix and choose FBA Meta Device Configuration, then choose Form Meta. In the e xample shown, the reservation filter is used to only show those devices reserved by the curre nt SMC user. Four devices are listed in the unmapped devices list. Add all moves the devices to the Meta member column. The meta head can then be specified. As with all configuration tas ks, click on the Add to Config Session list button. The ac tual commit of this action is done from ConfigSession view. When crea ting a meta, you can optionally use the “Auto Select” feature. The Auto select feature allows you to speci fy the number of metas, number of meta members per meta, and the meta heads only. The Symmetrix microcode automatically chooses the me ta members from the available pool of unmapped devices.

Dev ice Gr oups * SRDF and TimeFinder operations in SMC require Device Groups * All device groups in the default symapi_db.bin or GNS (if active) are a vailable in SMC * Device Groups can be created, deleted, renamed and devices can be added and remo ved as needed * SRDF and TimeFinder operations are i nvoked by selecting a device group and using the Replication option * Device Mas king opera tion can also be invoked by selecting a device group * Devices can belong to multiple Device Groups The Devices types supported in SMC are shown on the slide. The STD Devices can be Regular (non SRDF Devices), SRDF R1s, or SRDF R2. Devices can be added as Clo ne Target devices on the local or the remo te array, and rem ote Virtual devices can be added. The device group dialog displays only valid devices when choosing a device type. For instance, when adding remote Clone Target devices, only eligible devices configured on the remote array display in the dialog.

Dev ice Types in Dev ice Gr oups

SMC Device Group creation is a multi-step process, similar to creating SYMCLI device groups using symdg, symld, and symbcv. The wizard is launched by right clicking the Device Group Folder and choosing the Device Group Management >Create Device Group option. In this example, we crea te a Device Group of Type RDF1 and ass ociate local V DEVSs, local BCVs and remote clone tar gets. The first step is to choose a name for the Device Group (DemoDG in this e xample), then the Device Group Type (RDF1 in this example because we wa nt to add SRDF R1 STD devices). Click on STD in the Device Type Column and add the required R1 devices from the Available box to the Group Members box. The bottom of the wizar d gives a summary of the selections that have been made. In the next slide, the local BCVs, VDEVs and the remote C lone target selections are made.

SRDF Mode operations are shown in this slide. Right Click on an RDF device group and choose Replication >SRDF Settings . The dialog box shows the current mode and pair states. The mode can be changed by using the Set Mode pull down. The vari ous options are shown on the sli de. In this example the mode is being changed from S ynchronous to Asynchronous. SRDF Control operations are per formed by right clicking the RDF Device Gr oup and choosing Replication > SRDF Control. A failover operation is shown. The same dialog box can be used for the other actions like Failback, Split, Establish, etc. The complete list of actions is displayed on the slide. The SRDF C ontr ol window has 2 pages. On page 1 the action (failover for example) and the device pairs are chosen. Choose options that relate to a specific action and to execute the action via the Fi nish button.

SMC Device Group creation is a multi-step process, similar to creating SYMCLI device groups using symdg, symld, and symbcv. The wizard is launched by right clicking the Device Group Folder and choosing the Device Group Management >Create Device Group option. In this example, we crea te a Device Group of Type RDF1 and ass ociate local V DEVSs, local BCVs and remote clone tar gets. The first step is to choose a name for the Device Group (DemoDG in this e xample), then the Device Group Type (RDF1 in this example because we wa nt to add SRDF R1 STD devices). Click on STD in the Device Type Column and add the required R1 devices from the Available box to the Group Members box. The bottom of the wizard gives a summary of the selections that have been made. In the next slide, the local BCVs, VDEVs and the rem ote Clone target selections are made.

TimeFinder/Clone operations are performe d by right clicking a device group and choosing Replication >TimeFi nder/Clone. If clone pairs have not yet been created, the dialog box does not show any device pairings. The “Set exact pairs” option is not available for Clone operations. Device pairs have to be defined by using the Edit Pairs button, then the de vice pairs can be defined in the Add/Remove Clone pairs dialog. Once the device pairs are defined, the rest of the operations are similar to TimeFinder/Snap.

Click on “Find” tab a nd in the search box, type the string (LUN in this case) you are looking for.

Once found the “LUN” (it mostly will be a Hyper, as we are talking in Symmetrix language), we will be able to view its contents. In this particular case, we are loking at a Meta, with 3 Hypers: One is the Meta head, the other two are meta devices. Note the M, as Meta head is marked with (M) and accompanied with the number of meta devices in it. Also, have in mind that Hypers are normall y of two sizes (per standardization) 16.96 and 56.9966 Gygabytes. On the right hand, we ca n see the LUN proper ties. Listed is the Meta head, ID 087, 16.96GB, allocated, and within its total Meta device size, 50.87 (3 LUNS in total). Here the example is repeated, but wi th more LUNS or Hypers. Here we ca n see Meta head 5F4, with its 7 devices attached to it, making it a (M)7 of 135.64Gb total.

To see the diference, we have listed a LUN here. You can apprecia te that LUN B4A, has 5.62GB Size, and summarizes wi th the other LUNS, 11.24GB.

LUNs are not the common standard for Symmetrix, as they do not use the disk completely as Hypers. Hypers use the cylinders of the disks, using even the las test cylinder of the disks, avoiding to leave MBs in disuse as is usual in LUNs. That is why the 16.96 and 59.9966 sizes are so intrincanted. You may want to have a spreads heet were you have the free / unmapped Hypers, filtered by size, device, etc. Documentation is always a must, as it will guide us for future configurations, as for s ystems recovery. Select Hyper “729”, right click, go to configure and S DR Device Mapping. SDR Stands for “Symmetrix Data”. If you need to add more than one disk, select the dis ks with “ctrl” key and follow the same steps. In this case, ports 8C:1 & 9C:0, are the las t octets from BAC KUPSRV HBA por ts.

Select the device on the left and the HBA por ts on the right. Hold control to sele ct more than one. Alert messages will be displayed for each of the HBAs to which we are adding the device (hyper). To check availability of addresses into this ports, run: symcfg list -sid 1098 -fa 08c -p 1 -addresses -available symcfg list -sid 1098 -fa 09c -p 0 -addresses -available Here is a preview of how the devices (Hyper) wil l be presented (allocated) to the selecte d storage HBA port. You can change the Address presented to the host, for better a dministration. (some systems do not like hexa values.) Select the addresses with * from the lis t gathered before, from OS. Then, System will ask if you are sure to execute this.

To make the storage visible to the host, you must complete the LUN Masking steps. To do so, go to “Hosts” section in left pannel, right click on the desired host (hos t to which allocate the storage) a nd select “Masking > Modify Mas king Configurations”. This will take you to the following scree n. This can be also done from C LI, with the “symmaskdb” command. In this screen we will provide all the data needed to com plete the masking. • First select the ports (HBA ports) of the ser ver to which attach the devices. • Then, Select both HBA’s WWPN on upper left box, choose storae arra y, and select type of device as desired. Finally, select the storage port to be assigned to. • In bottom list, check the devices you will be adding, in pairs (as they are seen once per HBA port.) • The is the completed list of tasks. Once we have this, clic k on “Grant” to execute the tasks. At the end, Note the differences between the marked devices: This is telling us that the disks were previously assigned to another host/s, but they maybe still alloca ted or not. Please it is very important for you to validate that you are not assigning a device for seco nd time to the same or another host.

The thin line represents one previous assi gnment, the thick line represe nts more than one previous assignment. The disks you normally will be assigning/allocating, should not have this “underscore” mark on the devices list. This list is an example, as you ca n also see that there are some devices with granted permissions to a host. At last, Verify in the detail that all the operations have bee n completed as desired. Finally, Verif y on host wi th ioscan –fnC disk and insf –C disk, that the Hyper (or LUN) has been correctly assigned and visible to the Operating System. If this does not work, use iosca n as it, and the insf –C. For basic troubleshooting, use: symmaskdb -sid 1098 list assignment -dev 10E8 symdev -sid 1098 show 10E8 | more To show how the device is mapped to the host and were co uld be a communication loss.

Thanks for reading. ~ THE END ~ EMC Control Center Knowledge Share - July 17th 2009, Gaston Benetrix @ EMC Corporation, Argentina.

Control Center Knowledge Share

3 comments

Notes on slide 1

2 Favorites