Control Center Knowledge Share

6,307 views
6,175 views

Published on

ControlCenter Storage Allocation SRDF SAN Configuration TimeFinder Knowledge Share

Published in: Technology
3 Comments
5 Likes
Statistics
Notes
  • Awesome document. However, the images are not clear, could you please post the document with better resolution?. Thanks so much.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Excellent Control center knowledge share. I cannot see the pics in good resolution. can you please email me the pdf at white221g@gmail.com. thank you so much.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • what's this? EMC storage control center?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
6,307
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
250
Comments
3
Likes
5
Embeds 0
No embeds

No notes for slide

Control Center Knowledge Share

  1. 1. 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
  2. 2. 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)
  3. 3. 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.
  4. 4. 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.
  5. 5. 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.
  6. 6. 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.
  7. 7. 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.
  8. 8. 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.
  9. 9. 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, un- configured capacity, the amount of devices that are standard or BCV, and much more. By selecting front end fibre ports you can see whether the ports are online or offline, how many ports are managed by the 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.
  10. 10. 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
  11. 11. 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.
  12. 12. 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).
  13. 13. 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.
  14. 14. 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:
  15. 15. 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.
  16. 16. 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.
  17. 17. 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.
  18. 18. Pr int, Preview, Export and Launch
  19. 19. `
  20. 20. 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)
  21. 21. 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.
  22. 22. 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.
  23. 23. 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.
  24. 24. 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.
  25. 25. 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.
  26. 26. 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
  27. 27. 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.
  28. 28. Schedules – Continued Creating a New Policy from a Template Creating a New Policy from a Template - (Continued)
  29. 29. 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.
  30. 30. 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.
  31. 31. 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.
  32. 32. 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.
  33. 33. * 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.
  34. 34. 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.
  35. 35. 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.
  36. 36. 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.
  37. 37. 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).
  38. 38. 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.
  39. 39. 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.
  40. 40. * 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
  41. 41. 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.
  42. 42. 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.
  43. 43. * 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.
  44. 44. 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.
  45. 45. 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.
  46. 46. 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.
  47. 47. 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.
  48. 48. 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.
  49. 49. 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.
  50. 50. 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.
  51. 51. 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.
  52. 52. 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 à
  53. 53. 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.
  54. 54. ß Creating and Edit ing Save Pools Delet ing Save Pools and Dev ices à SRDF/A Attributes
  55. 55. 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.
  56. 56. 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.

×