Sei sulla pagina 1di 110

Lab Guide

Unisphere For VMAX 40K & 10K


Lab Guide

EMC Solutions Group


Abstract
This Lab Guide serves as a guide for a demonstration of Unisphere For VMAX. It provides an introduction to Unisphere for VMAX and a set of lab labs to demonstrate the solution to customers.

Copyright 2012 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All trademarks used herein are the property of their respective owners.

vLab Unisphere for VMAX 40K and 10K

Table of contents
Introduction to the VMAX Lab ................................................................................................................6 Welcome ...........................................................................................................................................6 An Overview of the VMAX Family...................................................................................................6 Connecting To The Lab ..........................................................................................................................8 Exercise 1: Introduction to Unisphere for VMAX ....................................................................................9 Introduction to Unisphere for VMAX ..................................................................................................9 Login to Unisphere for VMAX ........................................................................................................9 The Main Screen........................................................................................................................ 10 Enable Remote Connection Optimization................................................................................... 12 How to Navigate in Unisphere for VMAX..................................................................................... 12 Examine the Main Sections in Unisphere for VMAX .................................................................... 14 Examine the Hosts Sub-Sections ............................................................................................... 17 How to Register an Array in Performance Analyzer ..................................................................... 18 How to View an Array's Dashboard ............................................................................................ 20 How to Manage Alerts in Unisphere ........................................................................................... 22 Conclusion ................................................................................................................................ 23 Exercise 2: How to Provision Storage to an ESX Server ....................................................................... 25 How to Provision Storage to an ESX Server ..................................................................................... 25 Execute the Create a New Host Wizard ....................................................................................... 25 Expand the Host's Storage Group .............................................................................................. 33 Hide the Browser Window ......................................................................................................... 36 Login to vCenter Host ................................................................................................................ 36 Login to VMware vSphere Client ................................................................................................ 37 Discover Storage ....................................................................................................................... 38 Create a New Datastore ............................................................................................................. 40 Conclusion ................................................................................................................................ 47 Exercise 3: VMAX Integration with VMware ........................................................................................ 48 How to Use EMC's Virtual Storage Integrator Plugin in the vSphere Client....................................... 48 The vCenter Desktop ................................................................................................................. 48 Select the Virtual Storage Integrator (VSI) Plugin ....................................................................... 48 Explore the Storage Viewer Data for Datastores ......................................................................... 49 Rename the Datastore [Optional]............................................................................................... 50 Explore the Storage Viewer Data for LUNs .................................................................................. 51 Explore the Storage Viewer Data for Targets............................................................................... 52 Conclusion ................................................................................................................................ 53 How Unisphere for VMAX Integrates with VMware .......................................................................... 54 vLab Unisphere for VMAX 40K and 10K 3

Hide the vCenter Desktop .......................................................................................................... 54 Add a Virtual Server................................................................................................................... 55 Explore the Virtual Server's Details ............................................................................................ 55 Map Devices to a Virtual Machine.............................................................................................. 56 View the VM's Properties in the vSphere Client .......................................................................... 59 Conclusion ................................................................................................................................ 60 How to Provision Gatekeepers to a VM using Solutions Enabler (Optional Exercise) ....................... 61 How to Display the Authorized ESX Servers ............................................................................... 61 How to Display the VMs on an ESX Server .................................................................................. 61 How to Display the Gatekeeper Devices Provisioned to an ESX Server ....................................... 62 How to Display the Gatekeeper Devices Mapped to a VM .......................................................... 62 How to Map Gatekeeper Devices to a VM................................................................................... 62 Conclusion ................................................................................................................................ 63 Exercise 4: How to Configure Virtual Provisioning & FAST VP ............................................................. 64 How to Configure Virtual Provisioning & FAST VP ............................................................................ 64 Create the EFD_R1 Thin Pool ...................................................................................................... 66 Create the EFD_R1 Tier .............................................................................................................. 69 Navigate to the Tiers Page ......................................................................................................... 69 Modify the FC Tier ...................................................................................................................... 71 Create a FAST Policy .................................................................................................................. 73 Associate the GOLD Policy with a Storage Group ....................................................................... 74 Modify the DEFAULT Policy ........................................................................................................ 76 Define a Move Time Window...................................................................................................... 77 Modify the Initial Analysis Period .............................................................................................. 78 Enable FAST VP ......................................................................................................................... 79 Examine the FAST VP Compliance Reports ................................................................................. 81 View a Detailed Compliance Report for a Storage Group ............................................................ 81 Conclusion ................................................................................................................................ 82 Exercise 5: How to Configure Federated Tiered Storage (FTS) ............................................................. 83 How to Configure Federated Tiered Storage (FTS) ........................................................................... 83 How to View External Disk Groups ............................................................................................. 85 How to View the External Storage Presented to a VMAX ............................................................. 86 View the Control Ports ............................................................................................................... 86 View the External Ports .............................................................................................................. 87 View the External LUNs .............................................................................................................. 88 How to Import External LUNs ..................................................................................................... 88 How to View the FTS Components Created After Virtualizing External LUNs ................................ 90 View the Data Devices (TDAT) .................................................................................................... 92 View the Thin Devices (TDEV) .................................................................................................... 92 Conclusion ................................................................................................................................ 93 vLab Unisphere for VMAX 40K and 10K 4

How to Configure Federated Tiered Storage with SYMCLI (Optional Exercise) .................................. 94 How to Display External Disk Groups ......................................................................................... 94 How to Display the Control and External Ports ........................................................................... 94 How to Display the External LUNs .............................................................................................. 95 How to Virtualize External LUNs ................................................................................................. 95 How to Display eDisks added to an External Disk Group ............................................................ 96 How to Display the Details for a Spindle .................................................................................... 97 How to Display a Data Devices (TDAT) Details ............................................................................ 98 How to Display a Thin Devices (TDEV) Details ............................................................................ 98 Conclusion ................................................................................................................................ 99 Exercise 6: Using VP Snap ................................................................................................................ 100 Using VP Snap ............................................................................................................................. 100 Open a Command Prompt ....................................................................................................... 100 Navigate to the VPsnap Lab Directory ...................................................................................... 100 Display the Details for the Thin Pool FC_R1 .............................................................................. 101 Create a VP Snap Session........................................................................................................ 102 Query the VP Snap Session ..................................................................................................... 103 Re-examine the Allocated and Shared Tracks .......................................................................... 103 Create a Second VP Snap Session ........................................................................................... 104 Write Data to the Source Device 004A ..................................................................................... 105 Re-examine the Allocated and Shared Tracks .......................................................................... 105 Examine the Enabled Data Devices.......................................................................................... 106 Terminate the VP Snap Sessions ............................................................................................. 106 Create and Activate Two Clone -copy Sessions ........................................................................ 107 List the Clone Sessions ........................................................................................................... 108 Re-examine the Allocated and Shared Tracks .......................................................................... 109 Conclusion .............................................................................................................................. 109 Conclusion ....................................................................................................................................... 110 Three Things to Take Away ........................................................................................................... 110

vLab Unisphere for VMAX 40K and 10K

Introduction to the VMAX Lab


Welcome

Welcome to the Symmetrix Unisphere for VMAX lab. This series of exercises provides an introduction to the latest features of Enginuity 5876 using a virtual environment. This environment provides each lab user exclusive use of a Symmetrix VMAX, permitting a range of operations without interference to other labs. Virtual Enginuity has limitations and this is most obviously seen with small device sizes however all lab exercises have been tested and verified. It is still possible that operations outside exercise boundaries will cause errors. If this occurs, a user should email demoteam@emc.com to reset the environment. The following exercises are available for you to run through. Please note, exercises 2 and 3 are linked and should be executed in order. However, the remainder of the exercises may be executed in any order. 1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap
An Overview of the VMAX Family

VMAX 10K Most affordable multi-controller array purpose built for performance and efficiency to consolidate applications in virtual environments. VMAX 20K Purpose built for performance, consolidation and automation in demanding virtual data center environments. VMAX 40K Purpose built for Hybrid Cloud environments providing the industrys highest levels of consolidation, performance and scalability.

vLab Unisphere for VMAX 40K and 10K

vLab Unisphere for VMAX 40K and 10K

Connecting To The Lab


Click the drop down under Remote Access for UniVMAX Launchpad and select RDP

vLab Unisphere for VMAX 40K and 10K

Exercise 1: Introduction to Unisphere for VMAX


Introduction to Unisphere for VMAX

1. - Introduction to Unisphere for VMAX <<--- You are here 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap Unisphere for VMAX is a storage management product that provides a common look and feel using big button technology for simplicity and ease of use. In this exercise you will tour all of the main sections of Unisphere v1.1.0.5 that enable a user to manage a VMAX system.
Login to Unisphere for VMAX

Double click the Unisphere for VMAX icon on the desktop.

Click the link Continue to this website to bypass the certificate warning and launch Unisphere for VMAX.

vLab Unisphere for VMAX 40K and 10K

Enter smc in both the User and Password fields, then click Login.
The Main Screen

Make yourself familiar with Unisphere's Home Page:

Unisphere Controls - allows you to rediscover an Array, refresh the screen, export data, find help and exit the application

vLab Unisphere for VMAX 40K and 10K

10

Toolbar - provides links to different sections in Unisphere (Note, when an array is selected, the options available on the toolbar expand.) Navigation Path - allows quick navigation between sections in Unisphere The Dashboard - displays the objects or sections available to the user to manage Common Tasks - provide access to Wizards used to perform common administrative tasks

The Home page's dashboard displays all of the arrays managed by Unisphere and the following basic information about them:

The Symmetrix identification number - 000194900001 The indication this array is locally attached to the host running Unisphere - Local The array's model number - VMAX40K The Enginuity level running on the array - 5876.80.55 The number and severity of the Alerts - 6 The physical capacity indicator

Make yourself familiar with the bottom half of Unisphere's Home Page:
1. Capacity Indicator - available for every array managed by the Unisphere instance 2. Capacity Indicator Legend

vLab Unisphere for VMAX 40K and 10K

11

3. Alert Indicator - indicates the number of alerts Unisphere has received for all of the managed arrays 4. User/Role Indicator - indicates the user logged into Unisphere and their assigned role 5. Last Updated Indicator - displays the date and time Unisphere last refreshed it's information 6. Administration Link - clicking the Administration link will allow users to manage alerts, preferences, user roles and authentication options 7. Common Tasks - click the " >" to expand or collapse the Common Tasks window Enable Remote Connection Optimization

Click the Gear icon to display user Preferences.

Select Optimize for Remote Connection and click OK to minimize the graphic animations in Unisphere.
How to Navigate in Unisphere for VMAX

Unisphere for VMAX offers several options for navigating around the tool. The primary navigation method will be the big button options on the toolbar. To gain

vLab Unisphere for VMAX 40K and 10K

12

access to all of the options, you must set your context, which defines the array you want to work on. Click the Symmetrix ICON once to set your context to the VMAX ending in 0001. Note, double clicking will take you to the array's Dashboard view.

Notice that after setting your context new options including System, Storage, Hosts and Data Protection become available on the toolbar. In a multi array environment, clicking on the Symmetrix icon located on the far left of the toolbar, provides a drop down menu that enables you to change Unisphere's context. Clicking on the All Symmetrix option clears the context and returns you to the default view.

Click the Storage option on the toolbar to switch to the storage section.

The navigation path is displayed below the toolbar. As you navigate around Unisphere clicking on sections and sub-sections, links are automatically added to the navigation path to allow you to quickly return to a higher level. Click the serial number 000194900001 link to return to the Home page.

vLab Unisphere for VMAX 40K and 10K

13

Hovering the mouse over an option on the toolbar will display a drop down menu. Hover the mouse's cursor over the System option on the toolbar to display the System drop down menu. Notice that the drop down menu is divided into two sections
1. Sub-sections - these are the same sub-sections that become available when clicking on an option on the toolbar, but in a list format 2. Common Tasks - are links to wizards associated with the section

Hover the mouse's cursor over the other options on the toolbar.
Examine the Main Sections in Unisphere for VMAX

Click the System option on the toolbar.

vLab Unisphere for VMAX 40K and 10K

14

The System section contains four sub-sections.


Dashboard - a high level view of the arrays status; you will explore further in an upcoming step Alerts - any alerts that have been triggered for the array; you will explore further in an upcoming step Job List - allows the user to view and manage jobs that make changes to the array Settings - system wide settings for an array, including attributes and licensing

Click the Storage option on the toolbar.

vLab Unisphere for VMAX 40K and 10K

15

The Storage section contains six sub-sections.


Storage Groups - Storage groups are used for Auto Provisioning - masking and mapping devices - as well as with FAST VP FAST - dashboard to control and configure FAST and FAST VP components and settings Thin Pools - Virtual Provisioning pools Tiers - storage tiers for FAST and FAST VP Volumes - allows the user to create and mange volumes Storage Templates - allows the user to manage templates for creating new devices

Click the Hosts option on the toolbar.

vLab Unisphere for VMAX 40K and 10K

16

Examine the Hosts Sub-Sections

The Hosts section contains six sub-sections.


1. Initiators - the table shows the initiators (host HBAs) that are zoned to the array and which array port(s) they're zoned to 2. Masking Views - are the glue that tie Initiators, Port Groups and Storage Groups together to map and mask devices to a host 3. Initiator Groups - groups of initiators associated with a single host 4. Port Groups - groups of array ports 5. Host Cache Adapters - list the VFCache cards that are connected to the array 6. Virtual Servers - allow users to view and manage storage presented to virtual servers

Note, for those of you familiar with AutoProvisioning, Storage Groups are not in the Hosts section, they are in the Storage section.

Click Data Protection option on the toolbar.

vLab Unisphere for VMAX 40K and 10K

17

The Data Protection section contains six sub-sections.


1. Local Replication - allows the user to monitor and manage local TimeFinder replication sessions 3. Device Groups - are containers for managing devices used for the replication sessions above 4. Remote Replication - allows the user to manage and monitor SRDF sessions 5. Migration - allows the user to monitor and manage migration sessions (symmigrate) 6. Replication Groups & Pools - allows the user to monitor and manage TimeFinder Snap pools and SRDF groups 7. Open Replicator - allows the user to monitor and manage replication technologies including: Open Replicator, RecoverPoint and Federated Live Migration. How to Register an Array in Performance Analyzer

Performance Analyzer - also known as Symmetrix Performance Analyzer or simply SPA - is a performance monitoring tool for Symmetrix arrays. Beginning with the introduction of Unisphere for VMAX, Performance Analyzer is fully integrated into the Unisphere GUI management tool.

vLab Unisphere for VMAX 40K and 10K

18

Analyzing performance data with Performance Analyzer is beyond the scope of this lab, however the next few steps demonstrate how to register VMAX 0001 for analysis. The collection of performance data is handled by the storstpd daemon that is part of Solutions Enabler. In a Windows environment, the daemon runs as a service. To verify the storstpd daemon service is running, minimize the browser window and click services icon on the desktop.

Scroll down until the EMC storstpd daemon is visible, then verify it is Started.

Maximize the browser window to continue. Hover the mouse's cursor over the Performance option on the toolbar and then click the Settings link on the drop down menu.

vLab Unisphere for VMAX 40K and 10K

19

Click the System Registrations option on the Settings page.

Double click the Symmetrix ID ending in 0001 to view the detailed System Registration page.

Click the Real Time and Diagnostic check boxes to begin collecting both Real Time and Diagnostic data for the array. Click the Apply button to save the changes.

Click the Systems Registrations link in the navigation path to go back a level.

The green circles in the System Registrations table indicate that the Symmetrix ID ending in 0001 is registered to collect both Real Time and Diagnostic data.
How to View an Array's Dashboard

vLab Unisphere for VMAX 40K and 10K

20

Click the Home option on the toolbar.

Double click the Symmetrix icon on the Home page to view the array's Dashboard.

Examine the System Dashboard. Note that information about the array is divided into four sections:
1. Overview - An overview section, which includes the array's serial number, model number, the Enginuity level and an indication if the array is locally attached to the host running Unisphere

vLab Unisphere for VMAX 40K and 10K

21

2. Capacity - provides a quick summary of the physical and virtual capacity in the array 3. Hardware - includes links to drill down on the various director types in the array 4. Alerts - summary of the alerts for the array How to Manage Alerts in Unisphere

There are several options for navigating to the Alerts page in Unisphere for VMAX including: Clicking the Alerts link on the Dashboard, or the link next to the array on the Home page Clicking the System option on the toolbar, then the Alerts option Clicking the Alerts link at the bottom left of the Unisphere window Click Alerts link in the Common Tasks, which may not always be available Hovering over the System option on the toolbar, then selecting the Alerts option from the drop down menu (shown)

Using one of the methods above, navigate to the Alerts page.

Examine the Alerts table and select the one FATAL alert.

vLab Unisphere for VMAX 40K and 10K

22

Click the View Details button.

Use the scroll bars to examine the detailed information about the alert. In this case, the alert concerns the EXTERNAL data pool, which is also referred to as a thin pool. The EXTERNAL thin pool contains no data devices at the moment you'll add some in an upcoming exercise - so the alert is triggered. You can Acknowledge the alert, which will change its state and keep the record or you can Delete the alert.

Configuring thresholds and notification options for alerts are beyond the scope of this exercise, but if you'd like to view the available options, click the Administration link located in the lower right corner of the Home page.
Conclusion

This brief introduction to Unisphere for VMAX has armed you with the knowledge to: Navigate around inside the tool using the toolbar and the navigation path Introduced you to the different sections inside the tool and what options they contain

vLab Unisphere for VMAX 40K and 10K

23

Register an array in Performance Analyzer Manage the Alerts generated by the system

In the remaining exercises, you will have opportunities to configure Federated Tiered Storage, Virtual Provisioning and FAST VP.

vLab Unisphere for VMAX 40K and 10K

24

Exercise 2: How to Provision Storage to an ESX Server


How to Provision Storage to an ESX Server

1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server <<--- You are here 3. - VMAX Integration with VMware 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap In this exercise you'll provision storage to a new host and associate the storage with the DEFAULT FAST VP Policy. You'll learn more about FAST VP in an upcoming exercise.
Execute the Create a New Host Wizard

Click the Create a new host link in the Common Tasks pane.

Complete the top half of the Host Management - Create Host dialog using the following settings:
Symmetrix: 00194900001 Host: ESX

Scroll through the list of Initiators, select iqn.1998-01.vmw:esx from the list and click Add.
vLab Unisphere for VMAX 40K and 10K 25

iqn-1998-01.vmw:esx

Verify the initiator iqn.1998-01.vmw:esx is added to the list, then click the Finish button to continue. Completing this step creates an Initiator Group named ESX. As you may recall, an initiator group is a container for all of a host's initiator's - iSCSI or Fibre Channel - used to communicate with an array.

Click the link provision storage to this host to select the storage that will be presented to the host.

vLab Unisphere for VMAX 40K and 10K

26

Verify the default settings on the first page of the Provision Storage wizard match what's shown, then click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

27

On the second page of the Provision Storage wizard, select Manual Selection from the drop down menu, then click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

28

Complete the third page of the Provision Storage wizard as follows:


1. Select the volume 0040 and while holding down the shift key, select the volume 0041. 2. Click the Add to Group button. 3. Click the Next button to continue.

On the forth page of the Provision Storage wizard, notice that 2 volumes totaling 4 GB of capacity will be added to the Storage Group.

vLab Unisphere for VMAX 40K and 10K

29

Click the Next button to continue.

Click the Provision with this Storage Group link to continue.

Verify the default settings on the fifth page of the Provision Storage wizard match the screenshot. Notice that Unisphere automatically selects the front-end ports that the host's initiator is logged into.

Click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

30

Examine the final page of the Provision Storage wizard. The provisioning feature on the Symmetrix VMAX platform is called Auto Provisioning. Auto Provisioning is broken down into four components: The Host or Initiator Group contains a host's initiators, which may be iSCSI IQNs or the WWNs from Fibre Channel HBAs. The Port Group contains the array's front-end ports that the host's initiators are connected to via the network in the case of iSCSI or zoning in the case of Fibre Channel. The Storage Group contains the devices that need to be presented to the host or cluster. The final component, the Masking View ties the other three components together. Once created the devices in the Storage Group are masked to the initiators in the Initiator Group and mapped to the ports in the Port Group.

If additional devices need to be presented to a host, they only need to be added to the Storage Group in order for the masking and mapping to be automatically created, which you will do in a few steps.

Click the Finish button to complete the Storage Provisioning wizard.

Click the Associate Storage group 'ESX_SG' with FAST Policy link to continue.
vLab Unisphere for VMAX 40K and 10K 31

Click the DEFAULT policy from the Associate to FAST Policy dialog and click the OK button to continue. You will learn more about FAST VP in an upcoming exercise.

Click the Close button to continue.

vLab Unisphere for VMAX 40K and 10K

32

Expand the Host's Storage Group

In this next step, we will expand the host's storage group to include four Gatekeeper devices. Gatekeepers are used for inband communication between a host running Solutions Enabler and Unisphere management software and a Symmetrix VMAX array. Hover the mouse over the Storage button on the toolbar, then click the Storage Groups option from the drop down menu.

Select the ESX_SG storage group, then right click. Click the Expand option from the right-click menu.

On the first page of the Expand Storage Group wizard, select Manual Selection from the drop down menu.

vLab Unisphere for VMAX 40K and 10K

33

Click the Next button to continue.

On the second page of the Expand Storage Group wizard, click the Filter icon in the upper right corner.

Click the Volume Identifier filter.

Enter 0058 in the first Volume Range field and 005B in the second. Note, the leading zeros are required.

Click the OK button to complete the filter.

vLab Unisphere for VMAX 40K and 10K

34

Select the first volume in the list 0058 and while holding down the Shift key, select the last volume in the list 005B. Click the Add to Group button to continue.

Click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

35

On the third page of the Expand Storage Group wizard, note that four existing volumes will be added to the Storage Group.

Click the Finish button to complete the wizard.

Click the Close button to dismiss the Expand Storage Group pop-up window.
Hide the Browser Window

Minimize the browser window running EMC Unisphere for VMAX, by clicking the Minimize button located in the upper right hand corner.
Login to vCenter Host

In this step, you will open a Remote Desktop session to the vCenter host, which is running the vSphere Server that the ESX host is managed by.
vLab Unisphere for VMAX 40K and 10K 36

Click the Remote Desktop icon on the desktop.

Verify that the IP address 192.168.20.11 is selected in the Computer field, then click the Connect button to continue. Note, the user name and password are as follows if needed: User name: Administrator Password: V$A4vLab
Login to VMware vSphere Client

On the vCenter desktop, double click the VMware vSphere Client icon.

vLab Unisphere for VMAX 40K and 10K

37

Ensure that the IP address / Name field is localhost and that the Use Windows session credentials check box is selected, then click the Login button to launch the VMware vSphere Client.
Discover Storage

In the vSphere Client, select the ESX host 192.168.20.12, then click the Configuration tab.

vLab Unisphere for VMAX 40K and 10K

38

On the Configuration tab, click the Storage Adapters link.

In the Storage Adapters box, select the iSCSI Software Adapter vmhba33. In the Details box, notice that there are no Connected Targets or Devices. Click the Rescan All link to instruct the ESX Server to scan for new storage.

vLab Unisphere for VMAX 40K and 10K

39

Click the OK button on the Rescan pop-up window to continue.

Note in the Details box that the server is now connected to a target array, which is presenting six devices.
Create a New Datastore

On the Configuration tab, click the Storage link in the Hardware box. Then, click the Add Storage link to create a new Datastore.

vLab Unisphere for VMAX 40K and 10K

40

Click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

41

Select the first entry, then click the Next button on continue.

vLab Unisphere for VMAX 40K and 10K

42

Click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

43

Click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

44

Enter the name VMAX Datastore 1 for the new Datastore's name, then click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

45

Click the Next button to continue.

vLab Unisphere for VMAX 40K and 10K

46

Click the Finish button to continue.


Conclusion

In this exercise you provisioned storage to an ESXi server and created a new datastore.

vLab Unisphere for VMAX 40K and 10K

47

Exercise 3: VMAX Integration with VMware


How to Use EMC's Virtual Storage Integrator Plugin in the vSphere Client

1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware <<--- You are here 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap This exercise demonstrates how EMC's free plugin for vSphere - Virtual Storage Integrator (VSI) - can be used to view the details about the storage presented to an ESX Server. Before attempting this exercise, make sure you've completed exercise 2.
The vCenter Desktop

Verify the Remote Desktop window to the vCenter (192.168.20.11) host is active. If not, follow the instructions in the next step.

Maximize the Remote Desktop window to the vCenter by clicking the icon on the task bar.
Select the Virtual Storage Integrator (VSI) Plugin

In the vSphere client, select the EMC VSI tab. Note, it may be necessary to use the tab navigation arrows to scroll through the tabs depending on the size of your window.

vLab Unisphere for VMAX 40K and 10K

48

Explore the Storage Viewer Data for Datastores

Note the VSI plugin allows you to view information about:


Datastores and the details about the storage backing them up (Default View) LUNs or the devices presented to the server Targets or the arrays presenting the storage

In the Datastores view, select the Datastore VMAX Datastore 1.

In the Storage Details box, note all of the detailed information displayed about the device backing up the datastore.

vLab Unisphere for VMAX 40K and 10K

49

Rename the Datastore [Optional]

Right click the datastore VMAX Datastore 1, then select the Rename option from the menu. Rename the datastore to reflect the VMAX Array's serial number and the Device Name. For example vmax0001_vol0040.

Click the Storage Pools button to display information about the Virtual Provisioning pools that the thin device or TDEV is using in the array. In this example, the device 0040 is consuming physical storage from the FC_R1 thin pool. Use the scroll bar to see more information about the pool.

vLab Unisphere for VMAX 40K and 10K

50

Click the Paths button to display information about the storage paths the device is presented down and the type of multi-pathing policy in effect for the device. In this case, only one path is configured for the device, so a Fixed policy is in use.

Click the Performance button. From this display it is possible to start performance monitoring for the device that combines stats collected from vSphere Server with stats collected from Solutions Enabler. For more information about the Performance monitoring feature of the VSI Plugin, see PowerLink.
Explore the Storage Viewer Data for LUNs

Click the LUNs link to change views.

vLab Unisphere for VMAX 40K and 10K

51

Review the information about the LUNs or the individual devices presented to the ESX server. Use the Show filter to sort the devices and the scroll bar to view additional information about the devices.
Explore the Storage Viewer Data for Targets

Click the Targets link to change views.

vLab Unisphere for VMAX 40K and 10K

52

The Targets view is broken into the following sections.


1. Storage Adapters - these are the FC HBAs or iSCSI initiators in the ESX server that are connected to the EMC Storage. 2. EMC Targets - These are the front-end ports on the EMC arrays that the storage is presented down. 3. EMC LUNs - This box will only be populated when one of the EMC Targets are selected. In the example above, the target SE-7E 0 has been selected and the six EMC LUNs presented to the host from that port are displayed. Note, use the scroll bars to view all of the detailed information about the devices. 4. Note that the Export link may be used to export a comma separated file detailing the devices presented to the ESX server. Conclusion

In this section of the exercise you explored the information available from EMC's free VSI plugin. VSI is available from PowerLink.

vLab Unisphere for VMAX 40K and 10K

53

How Unisphere for VMAX Integrates with VMware

1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware <<--- You are here 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap This exercise demonstrates the integration points between Unisphere for VMAX and VMware. Before attempting this exercise, make sure you've completed exercise 2.
Hide the vCenter Desktop

If you're currently viewing the vCenter desktop, click the minimize button to hide the Remote Desktop session.

Maximize the browser window running Unisphere by clicking the Internet Explorer icon on the task bar.

vLab Unisphere for VMAX 40K and 10K

54

Add a Virtual Server

Hover over the Hosts button on the toolbar and select the Virtual Servers option from the drop down menu.
Explore the Virtual Server's Details

Double click the server 192.168.20.12 in the table to examine its details.

vLab Unisphere for VMAX 40K and 10K

55

symc Examine the server's properties.

Click the Volumes link to view the details of about the volumes presented to the server.

Explore the information in the Volumes table. Note that whatever you named the Datastore created on Volume 0040 in the previous lab is reflected in the Datastore Name column.
Map Devices to a Virtual Machine

Click the server's IP Address in the navigation path to return to the detailed page.

vLab Unisphere for VMAX 40K and 10K

56

Click the VMs link to view the virtual machines running on the server.

Double click the Win2K8 VM to view its details.

Click the Volumes link to view the volumes presented to the VM.

Note the VM currently has one volume presented, which is a Virtual disk located on datastore1. Note, you can tell that datastore1 is an internal drive, because there is not a Device ID or Array ID listed in the display.

Click the Add VM Storage button located on the bottom left of the screen.

vLab Unisphere for VMAX 40K and 10K

57

Complete the following steps at the top of the Add VM Storage dialog.
1. Select 000194900001 from the Symmetrix drop down menu. 2. Click the device 0058 and while holding down the Shift key, select the device 0059. 3. Click the Add to VM button.

Note Gatekeeper devices are very small, in this case 0.01GB in size. Gatekeeper's are used for inband communication with the array.

Verify that the correct devices are added to the bottom control box and then click the OK button to continue. Note the devices will be mapped to Win2K8 as Raw Device Mappings (RDMs).

vLab Unisphere for VMAX 40K and 10K

58

Click the Close button to acknowledge the Add VM Storage information window.

Note the addition of the two Gatekeeper devices 0058 and 0059.
View the VM's Properties in the vSphere Client

Return to the vCenter desktop, select the VM Win2K8 in the vSphere Client, then right click and select Edit Settings from the menu.

vLab Unisphere for VMAX 40K and 10K

59

Note two new hard disks are mapped to the VM using the Mapped Raw LUN option.
Conclusion

In this lab you used Unisphere for VMAX to map devices to Virtual Machines.

vLab Unisphere for VMAX 40K and 10K

60

How to Provision Gatekeepers to a VM using Solutions Enabler (Optional Exercise)

Note, this exercise is optional. It walks you through mapping Gatekeeper devices as Raw Device Mappings (RDMs) to the Win2K8 VM using the new symvm command. The command was introduced in Solutions Enabler 7.4 and works with both VMware's ESX and Microsoft's Hyper-V hypervisor platforms. Before attempting this exercise, make sure you've completed exercise 2. Gatekeeper devices allow for inband communication between a host running Solutions Enabler and the Symmetrix family of arrays.
How to Display the Authorized ESX Servers

Click the Command Prompt icon located on the UNIVMAX Desktop.

Execute the command below to list the ESX servers that have been registered on the UNIVMAX host. symcfg list authorization -vmware Note the IP address in the Hostname column. This address corresponds to the server's IP address.
How to Display the VMs on an ESX Server

Execute the command below to list the VMs running on the server: symvm -server 192.168.20.12 list -vm all We will provision GKs to the Win2K8 VM in an upcoming step.

vLab Unisphere for VMAX 40K and 10K

61

How to Display the Gatekeeper Devices Provisioned to an ESX Server

Execute the command below to list the GKs provisioned to the ESXi server: symvm -server 192.168.20.12 list -sid 01 -gk The option -mapped may be added to the command to list GKs that have already been mapped to VMs.
How to Display the Gatekeeper Devices Mapped to a VM

Recall that you mapped two Gatekeepers to the VM using Unisphere in a previous step. Execute the command below to list the GKs mapped to the VM Win2K8: symvm -server 192.168.20.12 list -sid 01 -gk -mapped -vm Win2K8 Note the value in the full Array ID column is 000194900001; you will need this value in the next step.
How to Map Gatekeeper Devices to a VM

Execute the command below to map the GKs 0056 - 005B to the VM Win2K8: symvm -server 192.168.20.12 map -vm Win2K8 -array_id 000194900001 -range 5a:5b Note all devices mapped to a VM with the symvm command are provisioned as Raw Device Mapping (RDMs) devices on an ESX server.

vLab Unisphere for VMAX 40K and 10K

62

Conclusion

In this simple exercise you used the new symvm command to manage GK devices in a virtualized environment. It should be noted that the symvm command works equally as well with regular volumes, however it is limited to presenting devices as Raw Device Mappings (RDMs). RDMs are not usually recommended for general purpose storage.

vLab Unisphere for VMAX 40K and 10K

63

Exercise 4: How to Configure Virtual Provisioning & FAST VP


How to Configure Virtual Provisioning & FAST VP

1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware 4. - Configuring Virtual Provisioning and FAST VP <<--- You are here 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap What is Virtual Provisioning? Virtual Provisioning is EMC's implementation of thin provisioning on the Symmetrix platform. Virtual Provisioning Components Virtual Pool A virtual pool - also referred to as a thin pool - is a shared, physical storage resource comprised of data devices of a single Raid protection and technology type. Data Device (TDAT) A data device - also referred to as a TDAT - is like a standard device in that it is created with a Raid protection type. However, it is considered a private device, because it cannot be directly mapped to a host. Instead data devices are added to a thin pool to provide shared physical storage. Thin Device (TDEV) A thin device - also referred to as a TDEV - is a cache only device that is created with a specific size. When created the device consumes no physical storage on disk. Once bound to a thin pool, extents are allocated from the data devices in the pool as the host writes to new areas of the device. Extent An extent is the Virtual Provisioning unit of storage allocation, which is 768KB in size. Extents are allocated in a round robin fashion across all of the enabled data devices in a pool. Binding Binding is an action performed on a thin device. When a thin device is bound to a pool, a single extent is allocated from a data device in the pool. As a host writes to new areas of the thin device, additional extents are allocated from the bound pool, up to the configured size of the thin device. What is FAST VP?

vLab Unisphere for VMAX 40K and 10K

64

FAST VP automates the identification of active or inactive application data for the purposes of reallocating that data across different performance/ capacity tiers within an array. FAST VP proactively monitors workloads at both the LUN level and sub-LUN level in order to identify busy data that would benefit from being moved to higher-performing drives, without existing performance being affected. This promotion activity is based on policies that associate a storage group to multiple drive technologies, or RAID protection schemes, via virtual pools, as well as the performance requirements of the application contained within the storage group. Data movement executed during this activity is performed nondisruptively, without affecting business continuity and data availability. FAST VP Components: VP Tier A VP Tier contains between one and four thin storage pools - each thin pool must contain data devices of the same RAID protection type, and be configured on the same drive technology. FAST Policy A FAST Policy groups between one and three VP Tiers and assigns an upper usage limit for each storage tier. The upper limit specifies the percentage of the configured, logical capacity of the associated storage group that can reside on each tier. Storage Group A storage group is a logical grouping of Symmetrix devices that are to be managed together. Association Storage groups are associated with a FAST Policy, thereby defining the VP Tiers that data in the storage group can be allocated on.

Exercise Overview

vLab Unisphere for VMAX 40K and 10K

65

In this exercise you will perform the steps required to place data under FAST VP control, including the following items:
Create Thin Pools Create VP Tiers Create FAST Policies Associate a FAST Policy with a Storage Group Modify a FAST Policy Examine the FAST Compliance Report

Note:
This lab is being run in a Virtual Appliance running Enginuity 5876. This Virtual Appliance has a fraction of the resources that the smallest Symmetrix array offers. Using 128 MB for the Volume Capacity will ensure that existing Data Devices (TDATs) are added to the pool, which will reduce the time it takes for you to complete the lab and will ensure the VM remains stable throughout the exercise. The Virtual Appliance only supports Raid 1 devices - denoted as 2-Way-Mir in Unisphere - so all of the TDATs used in the lab will have Raid 1 (2-Way-Mir) protection. Create the EFD_R1 Thin Pool

VMAX 10K vs. VMAX 20K & 40K Virtual Provisioning works the same on all three VMAX platforms, however the VMAX 10K is shipped with preconfigured Virtual Pools. One Virtual Pool per drive technology is configured by default, which reduces the time between powering on the array and allocating storage to your first host.

Click Storage icon on the Unisphere toolbar to navigate to the Storage page.

vLab Unisphere for VMAX 40K and 10K

66

A thin pool is a shared, physical storage resource of a single RAID protection and drive technology used for the purposes of Virtual Provisioning. Made up of multiple data devices (TDATs), each pool provides on-demand storage for host addressable thin devices (TDEVs). On the Storage page, click the Thin Pools big button.

Click the Create button in the bottom left hand corner of the Thin Pools page.

To create a thin pool, it is necessary to specify a pool name, the desired drive technology, the desired RAID protection, and emulation. The number of data devices, and their capacity, also needs to be specified. Complete the Create Thin Pool dialog as shown above. Be sure to change the Volume Capacity unit to MB before entering 128 for the actual capacity. Note, the protection type 2-way-mir is the same as Raid 1 protection, which is abbreviated as R1 in the pool and tier names throughout this lab.

vLab Unisphere for VMAX 40K and 10K

67

Verify that the 16 Existing Volumes will be added to the new thin pool. Select Run Now from the drop down to execute the create thin pool command.

Click the Close button to confirm the thin pool was created.

Verify that the new thin pool EFD_R1 is listed in the table. Double click on the name to view its details.

vLab Unisphere for VMAX 40K and 10K

68

Create the EFD_R1 Tier

VMAX 10K vs. VMAX 20K & 40K As with Virtual Provisioning, FAST VP works the same on all three VMAX platforms, however the VMAX 10K ships with preconfigured tiers and a default policy.

Click the Storage link in the navigation path to return to the Storage page.
Navigate to the Tiers Page

A FAST VP tier defines a set of resources of the same drive technology type combined with a given RAID protection type, and the same emulation. FAST VP tiers can contain between one and four thin pools. Each pool must contain data devices of the same RAID protection type, and be configured on the same drive technology. Click the Tiers big button to navigate to the Tiers page.

Click the Create button located at the bottom left of the screen.

vLab Unisphere for VMAX 40K and 10K

69

Complete the Create Tier dialog as indicated above.

Click the Close button on the Create Tier information pop up window to continue.

vLab Unisphere for VMAX 40K and 10K

70

Modify the FC Tier

Select the FC_R1 tier in the Tiers table.

Click the Edit button to continue.

vLab Unisphere for VMAX 40K and 10K

71

Complete the Edit Tier FC_R1 dialog as follows:


1. Click the check box next to the VPsnap pool 2. Click the OK button

FAST VP supports from one to four pools backed by data devices on the same technology, rotational speed and raid protection in a tier. EMC's best practice is to add data devices created on disks with significantly different capacities to separate pools, which may then be combined in a single tier.

vLab Unisphere for VMAX 40K and 10K

72

Click the Close button to dismiss the Edit Tier dialog.


Create a FAST Policy

Click the Storage link in the navigation path to return to the Storage page.

Click the FAST big button to navigate to the FAST page.

A FAST policy groups between one and three tiers and assigns an upper usage limit for each storage tier. The upper limit specifies the maximum amount of capacity from each storage group associated with the policy that can reside on that particular tier. Click the Mange Policies link to navigate to the FAST Polices page.

Click the Create button to continue.

vLab Unisphere for VMAX 40K and 10K

73

Complete the Create FAST Policy dialog as shown above. Click the OK button to continue.

Click the Close button to dismiss the Create FAST Policy information pop-up window.
Associate the GOLD Policy with a Storage Group

Select the GOLD policy in the FAST Policies table.

Associating a storage group to a policy allows data within the storage group to reside on up to three tiers. A storage group is considered to be compliant with the FAST policy it is associated with when all data in the storage group is

vLab Unisphere for VMAX 40K and 10K

74

allocated within the bounds of the upper usage limits for each tier contained with the policy. Click the Associate Storage Groups button.

Select the UNIVMAX storage group. Click the Show Advanced tab to display the Enable FAST VP RDF Coordination option. Click the OK button to continue. Click the Close button on the Add Storage Group(s) pop-up window to continue.

vLab Unisphere for VMAX 40K and 10K

75

Click the Close button to dismiss the Add Storage Group(s) pop-up.
Modify the DEFAULT Policy

Select the DEFAULT policy, then right click and select the View Details option on the Right Click menu.

Modify the Properties of the DEFAULT policy as follows:


1. Update the tiers as shown to add allow a small percentage of EFD space 2. Click the Apply button

Policy modifications take effect immediately.

vLab Unisphere for VMAX 40K and 10K

76

Click the Close button to dismiss the pop-up window.


Define a Move Time Window

Click the FAST link on the toolbar.

Click the Edit link for the Move Time Window in the FAST Status Report section.

Click the Show Advanced link on the FAST VP Movement Time Window dialog.

vLab Unisphere for VMAX 40K and 10K

77

Click the Manage button for the Open Time Windows (Inclusive) option.

Complete the Manage Open VP Movement Time Windows dialog as shown. Click the Close button to dismiss the pop-up window after hitting the Add button. Click OK.
Modify the Initial Analysis Period

vLab Unisphere for VMAX 40K and 10K

78

Modify the Time to sample before first analysis period to have FAST VP collect performance statistics for a full day before performing any data movement. Note, this value can also be reduced to as little as two hours. Then press the OK button to continue.

Click the Close button to dismiss the pop-up window.


Enable FAST VP

Click the Edit link to change the FAST VP Settings.

Click the Show Advanced settings link on the FAST VP Settings dialog.
vLab Unisphere for VMAX 40K and 10K 79

Complete the FAST VP Settings dialog as shown.

Click the Close button to dismiss the pop-up window.

vLab Unisphere for VMAX 40K and 10K

80

Note that FAST VP is now enabled and that both the Performance and Move Time Windows are open.
Examine the FAST VP Compliance Reports

Click the FAST link on the toolbar.

Click the Maximimize button on the Storage Groups under FAST control window, which is located on the bottom right of the FAST page, to display a table of the storage groups and their capacity distribution.
View a Detailed Compliance Report for a Storage Group

vLab Unisphere for VMAX 40K and 10K

81

Hover your mouse over the Storage section on the Toolbar. Click the Storage Groups option from the drop down menu.

Select the UNIVMAX storage group from the Storage Groups table. Click the View Details button at the bottom of the page to continue.

Examine the FAST Compliance Report for the Storage Group. Note the following information in the FAST Compliance Report: Max SG Demand (%) - the maximum capacity allowed in each tier based on the policy associated with the storage group. Limit (GB) - The capacity in GBs allowed in each tier based on the policy associated with the storage group. Fast SG Used (GB) - the amount of capacity currently allocated in each tier. Growth (GB) - (Not shown) the amount of capacity the storage group can still consume in each tier based on the policy. Note, a negative number would indicate the storage group is out of compliance.

Conclusion

In this exercise you've configured virtual provisioning pools, FAST VP Tiers and FAST VP Policies. You've also associated storage groups with the FAST VP policies and examined the compliance report.

vLab Unisphere for VMAX 40K and 10K

82

Exercise 5: How to Configure Federated Tiered Storage (FTS)


How to Configure Federated Tiered Storage (FTS)

1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) <<--- You are here 6. - Using VP Snap What is FTS? Federated Tiered Storage (FTS) allows LUNs that exist on external arrays to be used to provide physical storage for Symmetrix VMAX. The external LUNs can be used as raw storage space for the creation of Symmetrix devices in the same way internal Symmetrix physical drives are used. These devices are referred to as eDisks. Data on the external LUNs can also be preserved and accessed through Symmetrix devices. This allows the use of Symmetrix Enginuity functionality such as local replication, remote replication, storage tiering, data management, and data migration with data that resides on external arrays. New Enginuity components required by FTS FTS is implemented entirely in Enginuity and does not require any additional Symmetrix hardware. Connectivity with an external array will be established through the same fibre optic SLICs currently used for configuring FAs and RFs. Instead of running FA or RF emulation, however, the processors will run a new type of emulation. DX directors A new emulation, referred to as DX, (for DA eXternal) has been developed that adapts the traditional DA emulation model to act on external logical units as though they were physical drives. The fact that a DX is using external LUNs instead of a DA using internal LUNs is transparent to other director emulations and to the Enginuity infrastructure in general. With respect to most non-drivespecific Enginuity functions, a DX behaves the same as a DA. eDisks An eDisk is a logical representation of an external LUN when it is added into the VMAX configuration. The terms eDisk and external spindle both refer to this external LUN once it has been placed in an external disk group and a virtual RAID group. External disk group External disk groups are virtual disk groups that are created by the user to contain eDisks. Exclusive disk group numbers for external disk groups start at 512. External spindles and internal physical spindles cannot be mixed in a disk group.
vLab Unisphere for VMAX 40K and 10K 83

Virtual RAID group An unprotected, virtual RAID group gets created for each eDisk that gets added to the system. The RAID group is virtual because eDisks are not protected locally by the VMAX; they rely on the protection provided by the external array.

Virtualizing The process of adding an eDisk to a Symmetrix array is called virtualizing the eDisk. Virtualizing has two modes of operation: External Provisioning - Allows the user to access LUNs existing on external storage as raw capacity for new Symmetrix devices. These devices are called externally provisioned devices. Encapsulation - Allows the user to preserve existing data on external LUNs and access it through Symmetrix volumes. These devices are called encapsulated devices.

External provisioning When an eDisk is virtualized for external provisioning, Enginuity creates an external spindle and adds it to the specified external disk group. External disk groups are separate from disk groups containing internal physicals and start at disk group number 512. Because RAID protection is provided by the external array, eDisks are added to unprotected virtual RAID groups. Symmetrix devices can then be created from the external disk group to present to users.

vLab Unisphere for VMAX 40K and 10K

84

Encapsulation Encapsulation has two modes of operation: Encapsulation for disk group provisioning (DP encapsulation) - The external spindle is created and added to the specified external disk group and unprotected RAID group. Symmetrix devices are also created at the same time, allowing access to preserved data. Otherwise the Symm devices will be treated as any other VMAX volumes. Encapsulation for virtual provisioning (VP encapsulation ) - Just as with DP encapsulation, the external spindle is created and added to the specified external disk group and to an unprotected RAID group. Data devices (TDATs) are then created and added to a specified thin pool. Fully non-persistently allocated thin devices (TDEVs) are also created and bound to the pool. Extents are allocated to the external LUN through the TDAT.

Configuring FTS Virtual Provisioning Encapsulation In this lab, an external LUN will be encapsulated and configured for Virtual Provisioning. When the device is encapsulated and a thin pool is specified, a data device (TDAT) will be created, added to the pool, and enabled. A fully allocated thin device (TDEV) will be bound to the pool. The thin device would then available be presented to the host allowing it to access the preserved data on the external array through the VMAX. Because of the 1:1 relationship required between the data device and the thin device for VP Encapsulation, there are some differences between VP in an encapsulated environment and VP using non-encapsulated external or internal data devices. Pools with VP Encapsulated devices will have thin and data devices 100% allocated (as well as the pool itself). Operations like add device, unbind, balance, and reclaim are not applicable to encapsulated thin pools and devices.
How to View External Disk Groups

Click Storage on the Unisphere tool bar.

vLab Unisphere for VMAX 40K and 10K

85

Scroll down until the Disk Groups big button is available, then click on it to display the Disk Groups table.

Locate disk group # 512 and examine its attributes. All disk groups numbered 512 and above contain external disks only. External disks and internal disks cannot be mixed in any disk group.
How to View the External Storage Presented to a VMAX

Click Storage in the navigation path to return to the Storage Section.

Scroll down until the External Storage big button is available, then click on it to display the External Storage tables.
View the Control Ports

vLab Unisphere for VMAX 40K and 10K

86

Click the triangle next to the folder in the Control Ports table to display the DX ports. Use the scroll bar to view all of the details. DX directors are configured in dual initiator (DI) pairs like traditional DAs. They are fully redundant like DAs and a failing director will fail over when necessary to the other fully functioning director in the DI pair. DI pairs will always be configured on the same engine with the same processor number. For example, in a 2 engine VMAX, 7G and 8G would be a valid pair as would 9H and 10H. Both ports on a processor will be automatically configured as DX ports when the emulation is loaded and both must be cabled and part of the FTS configuration. EMC requires a minimum of 4 paths to external devices, meaning that at least 4 ports belonging to a single DX dual initiator pair must be configured. Notes: DX directors must be configured by EMC. Once the DX emulation has been loaded on the processors, FTS is completely user-configurable. If converting FAs to DXs, any previously assigned devices must be unmapped and unmasked and the FA ports must be removed from any port groups.
View the External Ports

Click the triangle next to the folder in the External Ports table to display the external ports. Use the scroll bar to view all of the details.

vLab Unisphere for VMAX 40K and 10K

87

View the External LUNs

Click the triangle next to the folder in the External LUNs table to display the external LUNs. Use the scroll bars to view all of the details.
How to Import External LUNs

Select the first External LUN WWN and while holding down the Shift key, select the third. These three devices correspond to Volumes 0100, 0101 and 0102 in the external array. Click the Virtualize button to start the process of adding the external LUNs as eDisks.

vLab Unisphere for VMAX 40K and 10K

88

Complete the Virtualize External LUNs Dialog as shown above.


1. 2. 3. 4. Import Method: Encapsulation - Virtual Provisioning Disk Group: 512 - EXTERNAL_DG Thin Pool: EXTERNAL Use the drop down menu to select Run Now

Note, when encapsulating a device for Virtual Provisioning, a thin pool name must be specified. If an appropriate thin pool does not already exist, one must be created. Adding the eDisk, choosing to encapsulate the data, and choosing a thin pool will cause the eDisk to be created along with the TDAT (DATA device) which will be added to the pool and the corresponding TDEV (thin device) which will be bound to the pool.

Read the Confirm Virtualizing External LUNs pop-up window. Note that with this option, the data on the external LUN will be preserved. Click OK to continue.

vLab Unisphere for VMAX 40K and 10K

89

PLEASE Note, executing the command may take up to five minutes to complete in the Virtual Symmetrix Environment.

Click the Close button to acknowledge the pop-up windows.


How to View the FTS Components Created After Virtualizing External LUNs

Hover the cursor over the Storage option on the toolbar, then click Thin Pools.

Examine the information in the Thin Pools table for the EXTERNAL thin pool. Note the pool's Configuration is Unprotected. With FTS, the VMAX relies on the external array to provide the raid protection.

vLab Unisphere for VMAX 40K and 10K

90

Double click the small icon next to EXTERNAL in the Name column to display the pool's detailed configuration.

Use the scroll bar to examine the EXTERNAL pool's properties. Note the following properties are unique to an external disk group: Raid Protection = Unprotected Technology = N/A

In the Related Objects section, notice that three DATA Volumes (TDAT) and three Bound Volumes (TDEV) exist in the pool. The TDAT and TDEV have a 1:1 relationship, so as soon as the TDEV is provisioned to a host, all of the data that exists on the external LUN will be visible to the host.

vLab Unisphere for VMAX 40K and 10K

91

View the Data Devices (TDAT)

Click the DATA Volumes link to display the volumes in the pool.

Examine the properties of the DATA Volume (TDEV) 0070 that was added during the virtualization step. Note that it's configuration is Unprotected, because with FTS, the external array provides an eDisk with its raid protection. [OPTIONAL] Double click on the Data Volume 0070 to see all of its details.

Click the EXTERNAL link in the navigation path to return to the pool's subsection.
View the Thin Devices (TDEV)

Click the Bound Volumes (TDEVs) link to display the volumes in the pool.

vLab Unisphere for VMAX 40K and 10K

92

These thin devices (TDEV) were automatically created and bound to the pool during the virtualization step. Use the scroll bar to examine TDEV 0073's properties. Note that the volume is 100% allocated from the EXTERNAL pool. As mentioned above, as soon as the volume is provisioned to a host, all of the data that exists on the external LUN will be visible to the host. Double click on the TDEV 0071 to see all of its details.
Conclusion

In this lesson you used Unisphere for VMAX to configure FTS.

vLab Unisphere for VMAX 40K and 10K

93

How to Configure Federated Tiered Storage with SYMCLI (Optional Exercise)

In this optional exercise, you will use Solutions Enabler (SYMCLI) to virtualize the two remaining external LUNs presented to the VMAX.
How to Display External Disk Groups

Click the Command Prompt icon located on the Desktop.

To list the Disk Groups in SYMCLI, open a command prompt and execute the following command: symdisk -sid 01 list -dskgrp_summary Locate disk group # 512 in the output and examine its attributes.
How to Display the Control and External Ports

If you wish to view the control ports and external ports in SYMCLI, open a command prompt and execute the following command:

vLab Unisphere for VMAX 40K and 10K

94

symsan -sid 01 list -sanports -dx all -p all Note the control ports are listed in the first column and the external port WWNs are listed in the last column of the output.
How to Display the External LUNs

To view the external LUNs visible to the first control port 7F:0, execute the following command: symsan -sid 01 list -dir 7F -p 0 -sanluns -wwn 50000972C0000558 Note, the WWN 50000972C0000558 at the end of the command line is the WWN of the remote port connected to the control port.
How to Virtualize External LUNs

vLab Unisphere for VMAX 40K and 10K

95

To prepare to virtualize the remaining external LUNs, execute the following commands in the Command Prompt: 1. Change to the FTS directory cd c:\Labs\FTS 2. Display the contents of the file fts_add_edisks.txt. type fts_add_edisks.txt Note the following about the file's contents: The WWNs after the wwn= match the WWNs of the two remaining external devices The disk_group=512 designates the disk group number the edisks will be added to The encapsulate _data=no option tells the system that this external LUN will be treated as a raw disk and the data it contains will not be preserved.

3. Execute the add disk commands in the fts_add_edisks.txt file: symconfigure -sid 01 -file fts_add_edisks.txt commit -noprompt Note, the -noprompt option in the command above may be abbreviated -nop as commit may be abbreviated com. This operation will take a few minutes to complete.
How to Display eDisks added to an External Disk Group

Execute the command below to list the eDisks added to the external disk group 512 during the virtualization step(s):
vLab Unisphere for VMAX 40K and 10K 96

symdisk -sid 01 list -disk_group 512 -spindle Note, if you skipped the optional SYMCLI step, only three spindles will be in the disk group.
How to Display the Details for a Spindle

Execute the command below to display spindle 1E00's details. symdisk -sid 01 show -spid 1E00 | more Note, the spindle's location is External.

Press the Space bar to display the rest of the command's output. Note that one hyper with Device id 0070 exists on the spindle. Also note that the device's Type is Ext-Data, which means it's a Data Device (TDAT) that exists on an external LUN.

vLab Unisphere for VMAX 40K and 10K

97

How to Display a Data Devices (TDAT) Details

Execute the command below to display device 0070's details. Use the scroll bar to display all of the fields. symdev -sid 01 show 0070 | more Note that device 0070 is an Encapsulated Device that is part of the thin pool EXTERNAL. Press the Space bar to display the rest of the device's details.
How to Display a Thin Devices (TDEV) Details

vLab Unisphere for VMAX 40K and 10K

98

Execute the command below to display device 0073's details. symdev -sid 01 show 0073 | more Note that the TDEV 0073 is an Encapsulated Device that is bound to the thin pool EXTERNAL. The fact that the device is bound to a pool indicates the device is a thin device (TDEV). Also note that like all thin devices, it doesn't have a RAID group and is locally unprotected.
Conclusion

In this lesson you used SYMCLI to configure FTS.

vLab Unisphere for VMAX 40K and 10K

99

Exercise 6: Using VP Snap


Using VP Snap

1. - Introduction to Unisphere for VMAX 2. - How to Provision Storage to an ESX Server 3. - VMAX Integration with VMware 4. - Configuring Virtual Provisioning and FAST VP 5. - Configuring Federated Tiered Storage (FTS) 6. - Using VP Snap <<--- You are here VP Snap leverages TimeFinder technology to create space-efficient snaps for thin devices by allowing multiple sessions to share allocations within a thin pool. In this lab, users will use Solutions Enabler v7.4 to create two VP Snap sessions using one source device. A virtual provisioning thin pool will be monitored throughout this exercise. After noting the space consumed by these sessions, you will create two regular TimeFinder/Clone -copy sessions and compare the space saving efficiencies that VP Snap offers. Note that this lab uses the Symmetrix Command Line interface (SYMCLI) exclusively.
Open a Command Prompt

Click the Command Prompt icon located on the Desktop.


Navigate to the VPsnap Lab Directory

Execute the command below to change to the VPsnap directory: cd \Labs\VPsnap

vLab Unisphere for VMAX 40K and 10K

100

Execute the command below to list the files that you'll use during the exercise: dir
Display the Details for the Thin Pool FC_R1

Execute the command below to display the detailed configuration of the FC_R1 pool: symcfg -sid 01 show -pool VPsnap -thin -detail | more Note the values of the two fields in the highlighted section, which we will be referencing throughout the lab to demonstrate the space savings efficiency of the VP Snap feature.

Press the space bar to advance the output to the Pool Bound Thin Devices section. Note, you can press Ctrl-C at any time to break the pipe to the more command and return to the command prompt. Note the following:

vLab Unisphere for VMAX 40K and 10K

101

Thin devices 0040 - 004F are bound to the FC_R1 pool The devices are all 32775 tracks in size Device 004A has 540 tracks allocated and 515 tracks written The total number of allocated tracks may vary from the screenshot depending on the order you execute the labs

As hosts write to new areas of a thin device, 12 tracks referred to as an Extent are allocated from an enabled Data Device in the pool. Extent allocations are performed in a round robin fashion across all of the enabled Data Devices with free space in the pool. Enginuity maintains a flag referred to as NWBH - Never Written By Host - for each track on every usable device. This flag indicates if a host write has ever been performed to the Logical Block Address (LBA) range that belongs to a track. This mechanism allows the VMAX family to take short cuts in certain situations.
Create a VP Snap Session

Execute the command below to display the contents of the file session1.txt: type session1.txt Note, that the first device on the line (04A) is the source device and the second device (04B) is the target device. Execute the command below to create a VPsnap session using the devices in the session1.txt file: symclone -sid 01 create -f session1.txt -vse -noprompt Note, the -nop option in the screenshot is an abbreviation for -noprompt.

vLab Unisphere for VMAX 40K and 10K

102

Execute the command below to activate the VP Snap session: symclone -sid 01 activate -f session1.txt -noprompt
Query the VP Snap Session

Execute the command below to list all of the VP Snap sessions: symclone list -vse Note the the Virtual Space Efficient (VSE) setting is active for the source and target pair 004A to 004B and also note the number of tracks of device 004A that are protected. Note, you may have to execute the command a number of times to allow the activation to complete.
Re-examine the Allocated and Shared Tracks

vLab Unisphere for VMAX 40K and 10K

103

Execute the command below to display the detailed configuration of the VPsnap pool. symcfg -sid 01 show -pool VPsnap -thin -detail | more Note the values of the two fields in the highlighted section haven't changed. The # of Shared Tracks will not increase until a second VP Snap session is activated for the same source device and new writes to the source device occur. When this happens, the target devices in any active VP Snap sessions begin sharing the original tracks. The source device allocates new extents from the free space in the pool to store updated data.
Create a Second VP Snap Session

Execute the command below to display the contents of the file session2.txt: type session2.txt Note, the first device on the line (04A) is the source device and the second device (04C) is the target device. Execute the command below to create a VPsnap session using the devices in the session2.txt file: symclone -sid 01 create -f session2.txt -vse -noprompt Note, the -nop option in the screenshot is an abbreviation for -noprompt. Execute the command below to activate the VP Snap session: symclone -sid 01 activate -f session2.txt -noprompt
vLab Unisphere for VMAX 40K and 10K 104

Write Data to the Source Device 004A

Execute the command below to list the devices presented to the host. syminq -winvol Notice that the \\PHYSICALDRIVE1 is the Source Device 004A and is mounted as drive E:. Execute the command below to copy the file VPsnaplab-test.log file to the E: drive. copy VPsnaplab-test.log E:\
Re-examine the Allocated and Shared Tracks

Execute the command below to display the detailed configuration of the VPsnap pool. symcfg -sid 01 show -pool VPsnap -thin -detail | more Note the values of the two fields in the highlighted section have changed. New extents of 12 tracks were allocated to accommodate the copy of the .log file. The

vLab Unisphere for VMAX 40K and 10K

105

two snap sessions are also sharing extents or multiples of 12 tracks to preserve the view of the source device before the .log file was copied.
Examine the Enabled Data Devices

Press the Space bar to advance the output. Notice Data Devices that contain shared tracks are indicated by the X in the FLG S column. Shared tracks are defined as tracks that have pointers to them from multiple thin devices sharing the pool.
Terminate the VP Snap Sessions

vLab Unisphere for VMAX 40K and 10K

106

In order to recognize the space savings that the VP Snap feature offers, we must compare the # of Allocated tracks from the previous step to the # of Allocated tracks after terminating the VP Snap sessions and creating regular Clone -copy sessions using the same device pairs. Execute the command below to terminate the VP Snap sessions: symclone -sid 01 terminate -f session1.txt -noprompt symclone -sid 01 terminate -f session2.txt -noprompt Note, the -noprompt option used in the commands above may be abbreviated nop. Execute the command below to verify there are no VP Snap sessions remaining: symclone list -vse
Create and Activate Two Clone -copy Sessions

Execute the command below to create a Clone -copy session using the same device pairs as the first VP Snap session: symclone -sid 01 create -f session1.txt -copy -noprompt
vLab Unisphere for VMAX 40K and 10K 107

Execute the command below to activate the Clone -copy session. symclone -sid 01 activate -f session1.txt -noprompt Execute the command below to create a Clone -copy session using the same device pairs as the second VP Snap session: symclone -sid 01 create -f session2.txt -copy -noprompt Execute the command below to activate the Clone -copy session. symclone -sid 01 activate -f session2.txt -noprompt Note, the -noprompt option used in the commands above may be abbreviated nop.
List the Clone Sessions

Execute the command below to list all of the clone sessions every 10 seconds. When the number of Protected Tracks for the two sessions reaches zero, press Ctrl-C to break the loop. symclone list -i 10 Without the VPsnap feature, both target devices consume the same amount of space in the pool as the source device.
vLab Unisphere for VMAX 40K and 10K 108

Re-examine the Allocated and Shared Tracks

Execute the command below to display the detailed configuration of the VPsnap pool. symcfg -sid 01 show -pool VPsnap -thin -detail | more Note the values of the two fields in the highlighted section have changed again. New extents of 12 tracks were allocated to accommodate the clones of the source device. Each clone is an independent and full copy of the source device. Therefore there are no longer any shared tracks in the pool.
Conclusion

In conclusion the new TimeFinder VP Snap feature offers space saving efficiencies by sharing data amongst multiple sessions.

vLab Unisphere for VMAX 40K and 10K

109

Conclusion
Three Things to Take Away

Thank you for taking the time to complete the VMAX lab! We hope you enjoyed the experience and learned a lot about the power and flexibility of the Symmetrix VMAX family of arrays. As you depart, we hope you'll take away the following:

Enginuity 5876 introduced many new features including Federated Tiered Storage, TimeFinder VP Snap and a new simplified management interface Unisphere for VMAX The VMAX family offers many integration points with VMware and is the best choice for hosting your virtualized environment Unisphere for VMAX makes managing the world's most powerful storage array easier than ever before

Thank you!

vLab Unisphere for VMAX 40K and 10K

110