VNX Unified Storage Management - Lab Guide
VNX Unified Storage Management - Lab Guide
Management
Lab Guide
November 2015
LAB EXERCISE: VMWARE ESXI HOST ACCESS TO VNX BLOCK STORAGE ................. 97
LAB: PART 1 – CLONE PRIVATE LUNS AND ENABLE PROTECTED RESTORE ........................... 131
LAB: PART 2 – CREATE AND TEST A CLONE .................................................................... 132
LAB: PART 3 – PERFORM A CLONE CONSISTENT FRACTURE............................................... 139
LAB: PART 1 – CONFIGURE AND MANAGE A VNX FILE SYSTEM ......................................... 171
LAB: PART 1 – EXPORTING FILE SYSTEMS FOR NFS CLIENTS ............................................. 177
LAB: PART 2 – ASSIGNING ROOT PRIVILEGES ................................................................. 184
Important The following lab exercises provide the steps for setting up
Windows and Linux to interact with the VNX-series storage
system through Block and File connectivity.
A few important notes!
Note 1: Not all screen captures were made on the lab
equipment you will be using and therefore may differ slightly
from what you will see. Read each lab and step completely
before attempting it; do not simply follow the pictures!
Note 2: The names of the files used to install the VNX
software may differ slightly from one revision to the next. As
an example, the Unisphere Server Utility software for this OE
revision is presented with the following naming convention:
UnisphereServerUtil-Win-32-x86-en_US-1.3.8.1.0119-1.exe
Note 3: You will be sharing a VNX system with other students
to perform the lab exercises. This lab guide and a
corresponding Class Configuration Sheet are used together to
perform the lab exercises. It is important to follow the
naming convention for the objects you create by following
the lab guide and referring to your configuration sheet for the
unique names. In the lab guide objects or “items” specific to
each student are identified with Bold Italic text. The
corresponding “value” for the item is located on your specific
student Class Configuration Sheet. So when you see Bold
Italic text in the lab guide, you are required to use a value for
the item that is located on your Class Configuration Sheet.
Each lab exercise has a section labled “Preparing for the Lab”
and is designed as a tear-out sheet. It lists the objects or
“items” that will be identified with the Bold Italic text in the
lab guide. You may use this section to record the values for
each item from the Class Configuration Sheet. Refer to this
tear-out to input the values for the specified items.
This is a diagram of the lab equipment setup you will use for completing the exercises. The setup has
two halves; an A-side has odd-numbered equipment and a B-side that has even-numbered
equipment. Each student will be assigned to a Student Desktop system and will have access to a VNX
system and three other systems which will receive storage from the VNX; A Windows server, a Linux
server and an ESXi server. The setup also includes a Windows Active Directory environment for
Windows users to access CIFS storage from the VNX. It also includes a Linux LDAP environment for
users to access NFS storage from the VNX. The Windows AD and Linux LDAP user and group
environment are detailed in the lab guide Appendix. The setup includes multiple networks and
network services for the VNX to operate in.
Access to the lab setup is achieved through the EMC Virtual Data Center (VDC). The instructor will
provide each student with a unique VDC account credential to use for completing the lab exercises.
The specific VDC account is used to login to the VDC. The login will provide access to a user-specific
Student Desktop system.
Each student will be automatically redirected to the Metro view of their specific Student Desktop
Windows 8 system. Access the Desktop charm to get to the Desktop view. The Desktop view and its
Task bar have been pre-configured with all the needed application icons needed for the lab exercises.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
Note Your instructor will provide to you the information for connecting to the EMC
Virtual Data Center (VDC). The VDC connection information includes a Web
URL for the VDC and account credentials. The account provides you access to
your Student Desktop system. You will use your Student Desktop system to
access your VNX system and the other systems in the lab setup.
Ask your instructor for assistance if you are having any difficulty connecting to
the VDC or accessing your Student Desktop system.
From your Student Desktop, open a web browser and enter the VNX
Address in the URL address section.
4 Unisphere Login:
At the EMC Unisphere login screen, login using the following settings:
Name: sysadmin
Password: sysadmin
Use LDAP: unchecked
Scope: Global
Click Login
The Unisphere Interface is launched and the Home Page displayed with the
Dashboard screen.
5 The EMC Unisphere Title bar of the Unisphere interface has basic and
advanced object Search options, a General Tab with options to set interface
preferences, log and exit, and retrieve Unisphere Help.
The Top Navigation bar has Previous and Next Icons to allow navigation back
and forth, a Home Icon that shows the Dashboard screen, a System Drop-
down menu to switch between VNX storage systems registered to the
domain, and a context-Sensitive Menu Bar which varies depending on the
system been managed: VNX for File/Unified and VNX for Block.
Click the Customize button. The edit mode will open with the list of
panels that can be dragged to the Dashboard.
On the Alerts by Severity panel, click the X (close) button from the menu
on the top right corner of the panel.
Click on the top bar of the Overall Capacity panel and drag the window
to the top left of the Dashboard.
Click on Alerts by Severity icon on the top menu and drag the icon to the
right of the Overall Capacity panel.
Observe that the edit mode has closed and the Dashboard appearance has
returned to the default configuration.
From the top Navigation Menu click on the System List option
Observe that the systems that are part of the storage domain are listed here.
A list of managed domains is displayed, including the local domain and any
remote domains.
The systems that are part of this domain are displayed on the lower panel.
From the menu on the top right corner of the panel select the Tools icon,
and select the Columns option.
Uncheck the boxes for the Status, Software Revision, and Client Revision
columns, and click OK.
Observe that a description of the alert is displayed with the option to save it
to a text file on the client machine.
Select one Certificate and click the Properties button. Click Details.
Observe that the interface will launch the previous visited page (“Domains”).
Step Action
Note In this exercise you will perform basic tasks to become more familiar with
VNX for File operations using Unisphere. Some of the tasks can be completed
in more than one way.
Note: The same operation can be performed by clicking on the system link at
the Systems by Severity panel
Observe that the context-Sensitive Menu Bar on the Top Navigation has
changed based on the choice of object.
The Dashboard screen has also changed to display the information about the
chosen storage system: system alerts, system information, and storage
capacity.
On Top Navigation bar, click Systems > Hardware > Hardware for File.
Note: If you position the mouse over the menu option, and wait for 2
seconds, a sub-menu will open with the options for the choice.
The Hardware for File inventory is displayed with the list of components.
From the System Management Task Pane on the right of the screen
select the Control Station Properties link
Note: The screen above is displayed when the user log in using a global scope
authentication. If the user is authenticated to the VNX Control Station using
the local domain scope the screen below is presented.
On the top of screen, select Hardware from the page bread-crumb links.
On the top of screen, select System from the page bread-crumb links.
(Or click the System option from the Top Navigation bar).
On the top of screen, select Monitoring and Alerts from the page bread-
crumb links.
Select Background Tasks for File.
Read the logged information and click Cancel to close the window.
Step Action
Note In this exercise you will perform basic tasks to become more familiar with
Unisphere operations involving VNX for Block components. Some of the
tasks can be completed in more than one way.
1 Navigate to the Home Page displaying the All Systems Dashboard screen:
Click the Home Page icon or select All Systems from the drop-down list.
2 Open the System List page to view information about the VNX systems that are
part of the storage domain:
The page will display the list of systems with information about S/N, Model,
and Software Revision.
Select your assigned VNX system from the list and click Properties
Observe that the General tab will display information about the zoning
Unique ID, iSCSI IQN, and the IP address configuration of the storage
processors.
Explore the other tabs of the properties dialogue box. Observe that some
of the block configuration can be done on this dialogue box.
Click Cancel to close the properties dialogue box.
Observe that the context-Sensitive Menu Bar on the Top Navigation has
changed based on the choice of object.
The Dashboard screen has also changed to display the information about
the chosen storage system: system alerts, system information, and storage
capacity.
Click the column arrow that divides the main pane and the Task pane.
This will hide the Task Pane and expand the main pane – this will provide
a better visualization of the hardware component graphics.
Click and expand the different components and observe the changes on
the graphic on the main pane.
Expand the SPs > SP A component by clicking the + icon next to them.
Click on the SPA component
Click on the + next to the IO modules and select any Present State slot
Click on the Show Diagram button
A window will open with a description of the type of I/O module and status.
On the top of screen, select System from the page bread-crumb links.
(Or click the System option from the Top Navigation bar).
The Event Viewer dialogue box opens with the events for all periods and
categories. Observe that this view can be saved in a text file, printed or
filtered.
On the top of screen, select System from the page bread-crumb links.
Select Reports.
SP Summary
SP Port Details
I/O Module Information
Click Finish
The operation will capture the information and generate a report in a XML
format. The report can be automatically launched or the user can click the
View button to retrieve it.
Step Action
Note There may be events that require invoking a CLI command. This exercise
provides you with the ability to invoke a VNX OE for File CLI command via
Unisphere. The use of 3rd party applications for command line entry is also
acceptable. In order to illustrate a comparison you will view information via
Unisphere and then view the information via the command line output.
The next three steps illustrate how Unisphere and command line output
display similar information.
nas_server –list
Where:
From the Top Navigation Bar click Storage > Storage Configuration > File
Systems.
There should not be any file systems listed in the task page. This is expected.
nas_fs –list
You see many file systems listed in the task page. This is because Unisphere
does not display the root file systems but the CLI does.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
Note (If you are not already logged in to your “Student Desktop”) Connect to your “Student
Desktop” via your VDC connection.
Ask your instructor for assistance if you are having any difficulty
1 Unisphere login:
From your Student Desktop, open a web browser and enter the VNX address in
the URL address section.
At the EMC Unisphere login screen, login using the following settings:
Name: sysadmin
Password: sysadmin
Use LDAP: unchecked
Scope: Global
Click Login
From the Top Navigation bar in Unisphere, ensure that the All Systems option is
selected from the drop-down list.
Then click the Domains option.
3 Domain Configuration:
From the right-side Tasks Pane, in the Local Domain section, click the Select
Domain Master link.
4 Domain Master:
Step Action
From the navigation bar drop-down, select your assigned VNX system.
Click the Settings option on the navigation bar.
From the right-side Tasks pane in the More Setting section, select
Manage Licenses for File.
Verify that all the licenses are checked.
In this step, you will create a new administrative role with the privileges that
are described in your class configuration sheet.
Create a role with the information you recorded in “Preparing for the
Lab”:
Role Name: User-Defined Role Name
Description : User-Defined Role Description
Privileges : User-Defined Role Privileges
(Expand the Privileges Category in order to select the privilege object and
access level)
Look at the List of Roles – Observe that the role that was just created
appears under the Roles tab in the User Customization for File window.
From the User Customization for File window, select the Groups tab.
Click the Create button.
The newly created group should appear under the Groups tab in the User
Customization for File window as a Local Group type.
Navigate to Settings > Security > User Management > Global Users.
Click Add
The newly created user should appear under the Global User Management
window.
The modified user is displayed under the “User Customization for File”
window with the “Operator” and new assigned roles.
Logout from Unisphere and log back in as the Global User (case
sensitive) with the following settings:
Name: sysadmin
Password: sysadmin
Use LDAP: unchecked
Scope: Global
Click Login
Verify that the new user account is able to log into the system.
Observe that the role of the user does not have creation and modify rights
on tasks not related to the assigned role.
From the Dashboard view, select your VNX from the navigation bar drop-
down list.
Navigate to System > Monitoring and Alerts > Notifications for File.
Observe that the “Create” button is grayed out in each one of the tabs. The
account is not able to make any modifications to created events.
Purpose: In this lab, you will verify the VNX storage system SP (Storage
Processor) cache settings, networking and port configuration.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Select your VNX from the All Systems drop down menu
From the navigation bar select System. From the right-side Tasks pane
“System Management” section click the System Properties link.
Select the SP Cache tab
_______________________________
What would happen with Write cache is disabled?
_______________________________
End of Lab Exercise Part 1
Step Action
From then bar select Settings. From the right-side Tasks pane “Network
Settings” section click the Edit Network Settings – SPA link.
From the Virtual Port Properties window, verify that virtual port 0
displays the VNX Address (SPA).
Click on Virtual Port 0 and select Properties.
Verify that the settings are as follows:
From the navigation bar drop-down list, select All Systems. Click on the
navigation bar Domains option.
From the right-side Task pane Local Domain section, click the Configure
DNS link.
Verify the following DNS settings:
Step Action
Purpose: In this lab, you will verify and provision storage for a VNX
Unified system in preparation for configuring file systems and
attaching block hosts.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
You should see several LUNs starting with the word “File” in the list of
Selected LUNs. These LUNs have been added from the File storage pool.
These LUNs have also been discovered by the VNX OE for File, notice that
each LUN ends in a “d” and a number. These are the disk volumes that are
associated with each LUN.
Navigate to Storage > Storage Configuration > Storage Pools for File. The
page displays the mapped pool named File Pool. The storage space from
this pool will be used to create file systems with.
Step Action
Select the RAID Groups tab on the Storage Pools page to verify if there
are any RAID groups created
You should see two RAID groups created; RAID Group 5 made up of 5
disks and RAID Group 10 made up of 4 disks.
Step Action
Please verify you have created six (6) 5 GB LUNs with a LUN ID range starting
with the RG5 LUN ID. If the LUNs you created do not match the settings
specified, notify your instructor for assistance before proceeding any further.
Following lab exercises depend upon the LUNs created to be as specified.
Please verify you have created four (4) 5 GB LUNs with a LUN ID range
starting with the RG10 LUN ID. If the LUNs you created do not match the
settings specified, notify your instructor for assistance before proceeding any
further. Following lab exercises depend upon the LUNs created to be as
specified.
Step Action
Note: The Thin checkbox is unchecked so the LUNs you are creating will be
Thick LUNs.
Please verify you have created four (4) 5 GB Thick LUNs with a LUN ID range
starting with the Thick LUN ID. If the LUNs you created do not match the
settings specified, notify your instructor for assistance before proceeding any
further. Following lab exercises depend upon the LUNs created to be as
specified.
Please verify you have created four (4) 10 GB Thin LUNs with a LUN ID range
starting with the Thin LUN ID. If the LUNs you created do not match the
settings specified, notify your instructor for assistance before proceeding any
further. Following lab exercises depend upon the LUNs created to be as
specified.
3 LUN Properties:
Navigate to Storage > Storage Configuration > Storage Pools and select
the Pools tab.
Select the Block Pool and click the Properties button.
Select the General tab.
Select one of your Thick LUN Names and click the Properties button.
Record the details listed from the General tab in the LUN Capacity section.
________________________________________________________________
Record the details listed from the General tab in the LUN Capacity section.
_______________________________________________________________
Note: User Capacity is the size of the LUN that is presented to the host.
Consumed Capacity is user capacity to which the host has written data. Thin
LUN consumed capacity and rate of consumption can vary depending on the
attached host file system or application using the LUN. This is a normal
condition typical of most thin provisioning services.
Step Action
VNX systems use unused, or unbound, disks as hot spares. The table below
displays the number of unused disks that is recommended in order to
accommodate a hot spare.
SAS FLASH
NL-SAS
While still logged on to Unisphere, navigate to System > Hardware > Hot
Spare Policy
Here you will find a list of all the disk types available for your VNX system, and
the policy set for each disk type. A Recommended policy adheres to the EMC
best practices policy for that disk type/size. Custom policy gives the
administrator an option for their own ratio in the box in the Keep Unused per
Policy column. The No Hot Spares policy does not reserve any hot spares.
According to the number of disks in your VNX, how many unused disks are
recommended per disk type?
Close all open windows and application on your Student Desktop system.
Purpose: In this lab, you will verify host software already installed on
your Windows host and create a VNX storage group in order
to provide storage to your Windows host.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop system, launch the RDP Plus application that
is available from the Desktop view or its taskbar.
Click Connect.
powermt version
On your Windows host, open the Services tool which is available from
the Desktop view or its task bar.
Verify that the host agent and the iSCSI initiator services are up and
running. Look for “Navisphere_Agent”, which is the host agent service,
and the Microsoft iSCSI Initiator service.
You should see an iSCSI network connection in the Active Connection list.
Close the Network and Sharing Center.
Leave your RDP Plus session to your Windows host open on your Student
Desktop system. You will return to the session in a later part of the lab
exercise.
Step Action
From your Student Desktop system, open a browser and enter the VNX
Address (SPA) followed by </setup>. Example: 192.168.1.31/setup
To login, enter the sysadmin/sysadmin credentials and select the Scope:
Unisphere.
2 Verify Automanage:
In the Setup display scroll down until you find the Turn Automanage
On/Off button. Click it to enter the settings.
________________________________________________
Step Action
1 System Login:
Click OK.
Click Yes to the message “Do you wish to add LUNs or connect host”
Click the LUNs tab. From the Available LUNs window, expand your Pool
LUN Folder, locate the two Thick LUNs and the two Thin LUNs and add
them to your Windows Storage Group.
Click the Host tab, select your Windows host from the Available Hosts
pane and click the to move the hosts to the Hosts to be Connected
pane.
Click OK, Yes, OK.
Please verify you have selected and added the correct Thick LUNs and Thin
LUNs to your Windows Storage Group. If the LUNs added are not the correct
LUNs specified, notify your instructor for assistance before proceeding any
further. Following lab exercises depend upon the specified LUNs being given
to the host.
From theright-side task pane in the Host Management section, click the
Update All Hosts link.
Select your VNX Storage System and click Poll. Click Yes. After the Status
reads Success followed by the current date and time click Cancel.
From the Storage Group window select your Windows Storage Group.
From the Details section click the Hosts tab and verify that your
Windows host is connected.
From the Details section click the LUNs tab and verify that LUNs are
displayed.
Step Action
1 System Login:
On your Student Desktop system, return to your open RDP Plus session
to your Windows host.
Click the Server Manager icon on the taskbar of your Windows host.
From the Server Manager window, expand the File and Storage Services
container on the left-side panel and select Disks.
The DISKS pane in most cases will show four (4) DGC LUNZ disks. The VNX by
default presents LUNZ disks to the host when no LUNs are presented to the
host. This is to provide basic SCSI connectivity from the host to the array.
Now that LUNs are presented to the host, the host must rescan to see the
newly presented LUNs.
Click the TASKS drop down menu and select Rescan Storage.
The DISKS pane should show two 5.00 GB disks and two 10.0 GB disks with
Status Offline. These are the Thick LUNs and Thin LUNs that were added to
the Windows Storage Group.
Right-click each one of the offline disks and select the Bring Online
option. The disk status may not change immediately, you may need to
Refresh the disk table from the TASKS drop down menu.
You should now havefour (4) iSCSI disks that are Partitioned and have 0.00
GB in the Unallocated column. You may now close the Server Manager
window.
Purpose: In this lab, you will verify host software already installed on
your Linux host and create a VNX storage group in order to
provide access to the LUNs.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect
to your “Student Desktop” via your VDC connection.
From your Student Desktop system, launch the PuTTY application
that is available from the Desktop view or its taskbar.
powermt version
The Host agent status can also be verified with the following command:
ps -ef | grep hostagent
Step Action
1 System Login:
Click OK.
Click Yes to the message “Do you wish to add LUNs or connect host”
Click the LUNs tab. From the Available LUNs window, expand your RG5
LUN Folder, locate and add three RG5 LUNs to your Linux Storage Group.
In the Host LUN ID, enter “50” “51” “52” for the LUNs respectively. The
Host IDs are used by the Linux server to see the LUNs. If you leave them
blank, default values will be assigned.
Click the Host tab, select your Linux host from the Available Hosts pane
and click the to move the host to the Hosts to be Connected pane.
Click OK, Yes, OK.
Return to your PuTTY session to the Linux host and reboot the system by
running the following command:
reboot
A connection error message for you PuTTY session will be displayed.
Close it and the orphaned PuTTY session.
The Linux host will reboot in a moment. To verify its reboot, open a
Command Prompt on your Student desktop system and issue a ping
command to your Linux host. When the host replies to the ping, continue
to the next part of the lab.
Step Action
These commands will check and set the run levels for the iSCSI daemon to automatically
start at boot and to shut down when the server is brought down.
From your PuTTY session to your Linux host, run the following command:
powermt display dev=all
________________________________________________________________________
__
The fdisk command will be run next to create disk partitions for the host on the
assigned VNX LUNs. The command is menu drive. Run the following command and
follow the listed menu options:
fdisk /dev/emcpowera
Next, create a file system on the disk partition by running the following command:
mkfs.ext3 /dev/emcpowera1
Create a mount point for the new file system by running the following command:
mkdir /mntA1
Optional: You may repeat the same tasks listed here to partition the other two
pseudo-devices, emcpowerb and emcpowerc. Use /mntB1 and /mntC1 for the
mount points.
If you have partitioned the other two pseudo-devices, you also need to mount them.
Change directory to /mntA1 and write some data using the touch command
touch test
From your Student Desktop Unisphere session, navigate to Hosts and in the right side
Tasks pane Host Management section, select Connect Host.
Type in your Linux host Address in the Enter Host IP Address field. Click Go.
In the lower Volumes on Block Storage Systems section, verify that your mount
volumes are present.
Click OK to close the window.
Close your PuTTY session to your Linux host.
Purpose: In this lab, you will create a VNX storage group in order to
provide an ESXi server access to LUNs.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Click OK.
Click Yes to the message “Do you wish to add LUNs or connect host”
Click the LUNs tab. From the Available LUNs window, expand your Pool
LUN Folder, locate and add the Thick LUN and the Thin LUN to your ESXi
Storage Group.
Click the Host tab, select your ESXi host from the Available Hosts pane
and click the to move the hosts to the Hosts to be Connected pane.
Click OK, Yes, OK.
Step Action
1 System Login:
Password: emc2Local!
Click Login.
Next, select Storage Adapters from the Hardware table and right-click
iSCSI Software Adapter.
Select Rescan to make the LUNs visible to the ESXi server. Once the
Rescan is completed, the LUNs will appear in the Details pane.
Purpose: In this lab, you will perform VNX advanced LUN operations. It
will focus on LUN expansion and LUN Migration.
Tasks: In this lab exercise, you will perform the following tasks:
Expand a Pool-based Thick LUN
Expand a Pool-based Thin LUN
Expand a Classic LUN
Migrate a LUN
Please refer to your Class Configuration Sheet for this lab and record the values for each item
listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
From your Student Desktop system, launch the RDP Plus application that
is available from the Desktop view or its taskbar.
Click Connect.
Step Action
1 Renaming a LUN:
From the LUNs windows, right-click the Base LUN Name and select
Expand.
The Expand Storage Wizard will appear. Click Next.
From the Select Expansion Type window leave the default as Striping
and click Next.
From the Select Unused LUNs window select RG5 Stripe LUN and click
Next.
From the Specify new LUN Capacity window click the GB and Maximum
Capacity buttons and click Next.
From the Specify new LUN Settings window keep the defaults and click
Next
From the Summary window, review your configuration and click Finish
From the Results from the LUN Expansion Wizard window, once the
operation is shown as successful initiated, click Finish.
From the LUNs window, when the expansion completes, the Base LUN
Name LUN icon will change to represent a metaLUN.
From the LUNs window, right-click the Base LUN Name and select Show
Component LUNs.
Expand the Component 0 container.
Step Action
1 Navigate to LUNs:
LUN Migration moves data from a source LUN to a destination LUN of the
same size or larger within a single storage system. This migration is
accomplished without disruption to the applications running on the host.
LUNs can be the target or source of LUN migration operations. LUN
Migration can enhance performance or increase disk utilization for your
changing business needs and applications by allowing the user to change
LUN type and characteristics, such as RAID type or size, while their
Production volume remains online. LUNs can be moved between pools or to
a Classic LUN in another RAID group. This exercise will migrate a RAID Group
LUN to a Pool-based thin LUN.
2 Migrate a LUN:
Locate and select the Source LUN and click Properties. Note: to help
locate your LUN, in the Filter field input your Student number.
Fill in the following information:
o Unique ID (WWN): __________________
o RAID Type: ________________________
o RAID Group: _______________________
o User Capacity: _____________________
o Current Owner: ____________________
Click Cancel to close the properties window.
Locate and select the Destination LUN and click Properties. Note: to help
locate your LUN, in the Filter field input your Student number.
Fill in the following information:
o Unique ID (WWN): __________________
o RAID Type: ________________________
o Pool: _____________________________
o User Capacity: _____________________
o Current Owner: ____________________
Click Cancel to close the properties window.
Right-click the Source LUN and select Migrate. This will launch the Start
Migration window.
For a Migration Rate select Low.
From the Available Destination LUNs section, expand Thin_LUNs and
select the Destination LUN for the destination LUN. Click OK, Yes, Yes,
OK.
3 View Migration:
Select Source LUN and click Properties. Click the Migration tab to view
the migration progress.
Can the migration rate be changed while the migration is taking place?
_____________
Click Cancel.
Navigate to Storage > LUNs > LUN Folders. Under LUN Folders select the
Private LUNs folder.
Is the Destination LUN shown under details?
_______________________
o Note: If the migration has completed the LUN will not be shown.
4 Successful Migration:
Navigate to Storage > LUNs > Select Source LUN and click Properties.
Select the Migration tab. Set the migration rate to ASAP.
Wait until the migration completes.
Once completed, fill in the following information:
o Unique ID (WWN): __________________
o User Capacity: _____________________
o RAID Type: ________________________
o RAID Group: _______________________
o User Capacity: _____________________
o Current Owner: ____________________
Click Cancel.
Compare this information to the Source LUN information you wrote
down in step 2 of this exercise.
What
changed?____________________________________________________
__
In the LUNs window search for LUN Destination LUN.
Does LUN Destination LUN still exist?
________________________________________
Tasks: In this lab exercise, you will perform the following tasks:
Verify that SnapView is enabled on the VNX
Verify that the required LUNs and Storage Groups are
present on the VNX
Allocate LUNs to the Reserve LUN Pool
Create and Test a SnapView snapshot
Test Snapview session persistence
Rollback a SnapView session
Start and test a consistent Snapview session
Test the operation of the Reserved LUN Pool
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
SnapViewVol: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Navigate to Data Protection > Reserved LUN Pool and select the Free
LUNs tab.
The Reserved LUN Pool has already been configured. The LUNs free are
RLP_LUN_2010 through RLP_LUN_2041
Select one of the RLP LUNs and click Properties.
Click Ok once you have answered the question below.
Which LUN Folder contains the RLP LUNs? ________________
Step Action
In this step a LUN will be identified for use as a source LUN for the SnapView
Snapshot.
From your Student Desktop system, launch the RDP Plus application that
is available from the Desktop view or its taskbar.
Click Connect.
Click the Server Manager icon on the taskbar of your Windows host.
From the Server Manager window, expand the File and Storage Services
container on the left-side panel and select Disks.
Click on Tasks and select Rescan Storage.
Disks that were previously allocated to the host will still be present.
Your disk should appear as “Offline”. Right click on the drive and select
“Bring Online”.
A message will appear asking if you are sure you want to bring the disk
online on the server. Click Yes.
Verify that the drive is now “Online”.
4 Initialize Disk:
What is the drive letter for the new simple volume you just
created?_____________________
In this step data will be created on the source LUN to establish a data state
that will be captured using a SnapView Snapshot.
Open your SnapViewVol volume, right click the empty space and select
New > Folder.
Name the folder SnapView.
Open the SnapView folder.
Right click the empty space and select New > Text Document.
Name the file SnapView.txt.
Open SnapView.txt file and add some text into the file, such as your
student number, date and time and save it.
In this step a SnapView Snapshot is created for the source LUN. The snapshot
creates the framework for the SnapView Snapshot virtual LUN. It does not
define the point-in-time view of the data nor does it make the virtual LUN
visible to a host.
In this step a SnapView Snapshot Session is created. The session defines the
point-in-time data state that the SnapView Snapshot virtual LUN will capture.
In this step the SnapView Snapshot virtual LUN will be activated which makes
it available to be seen by a host. An inactive snapshot cannot be presented
to a host and thus its point-in-time data state cannot be viewed by a host.
Click the Snapshot LUNs tab and select SnapView Snap. Click Activate.
Select SnapView Session from the Available Snapshot Sessions pane and
click OK, Yes, OK.
Navigate to Data Protection > Reserved LUN Pool. Under the Allocated
LUNs tab expand RG10 LUN.
Click OK.
In this step the data on the source LUN will be changed to illustrate how the
SnapView Snapshot virtual LUN captures the point-in-time data state of the
source LUN.
In this step the SnapView Snapshot virtual LUN will be presented to a backup
host to view the point-in-time preserved data state of the source LUN.
In Unisphere, click Hosts > Storage Groups from the navigation bar.
From the Storage Groups window locate your Peer Storage Group.
If the Peer Storage Group is not present, click Create to create it.
Click Properties.
Select the LUNs tab on the Storage Group Properties dialog.
Expand the SnapView Snaps container, select SnapView Snap and click
Add. Then click OK, Yes, OK.
13 Navigate to the Server Manager menu on your peer (Secondary) Windows host
and verify Snapshot:
From your Student Desktop system, launch the RDP Plus application that
is available from the Desktop view or its taskbar.
Connect to your Peer Windows host according to the following
information:
Click Connect.
On the peer Windows Server, click on the Server Manager icon.
From the Server Manager window, select File and Storage Services >
Volumes > Disks.
Click on Tasks and select Rescan Storage.
Disks that were previously allocated to the host may still be present.
Your disk should appear as “Offline”. Right click on the drive and select
“Bring Online”.
A message will appear asking if you are sure you want to bring this disk
online on the server. Click Yes.
Verify that the drive is “Online”.
When the scan is complete, select your disk and verify that the drive
letter is present below in the volume section. If no, assign one.
Open the File Explorer and select the SnapViewVol drive. You should see
the SnapView.txt file you deleted on your primary Windows host.
Close Server Manager.
In this step the data state of the SnapView Snapshot virtual LUN will be
changed to illustrate how changes made to it do not affect the source LUN
data state.
From your Student Desktop system, access your existing RDP session to
your Windows host.
Open the File Explorer and select and open the SnapViewVol volume.
Verify that the text file that was created on the Snapshot is not present
on the source volume.
Step Action
1 Trespass LUNs:
In this step the source LUN of the SnapView Snapshot will be trespassed to
illustrate the persistence of the SnapView Snapshot Session. The peer SP will
own the trespassed source LUN and will also acquire ownership of the
associated reserved LUNs to maintain session persistence.
Click the refresh icon in the upper right hand corner of the pane.
Select the source LUN, and click the Properties button. The LUN has been
trespassed if the Current Owner and Default Owner are different SPs.
Click Cancel to close the dialog.
Click the Sessions tab and verify the state of SnapView Session.
Navigate to System > Monitoring and Alerts > SP Event Logs and select
Show SPA Event Log. Click Yes to dismiss any informational dialog that
appears.
Step Action
In this step the source LUN data state will be updated to illustrate the effect
of a SnapView Snapshot Session Rollback operation on the source LUN data.
From the existing RDP session to your Windows host, open File Explorer.
Open your SnapViewVol volume, right click the empty space and select
New > Folder.
Name the folder SnapView2.
Open the SnapView2 folder.
Right click the empty space and select New > Text Document.
Name the file SnapView2.txt.
Open SnapView2.txt and add some text into the file, such as your
student number, date and time and save it. Close the file and close File
Explorer.
3 Using Admsnap:
In this step the host will release the source LUN device to prepare the LUN
for the data state change of the session Rollback operation.
In this step the SnapView Snapshot Session point-in-time view data state of
the source LUN will be restored to the source LUN with the Rollback
operation.
From your Student Desktop, in the Unisphere session, click the Source
LUNs tab. Select SnapView Session and select Rollback.
In the Start Rollback dialog, under SnapView Recovery Session, check
the Start Session box and for Session Name type SnapView Session_R.
For the Rollback Rate select High. Click OK, Yes, Yes, OK.
In this step the host will reacquire the source LUN device so its new data
state can be seen.
From the existing RDP session to your Windows host, open a Command
Prompt.
Change to the directory that contains admsnap
Type the following command:
o admsnap_win2k12.exe clone_activate
The command should look something like this when finished:
From the Server Manager window on your Windows host, select File and
Storage Services > Volumes > Disks.
Click on Tasks and select Rescan Storage.
Disks that were previously allocated to the host may still be present.
Close Server Manager.
Open the File Explorer. Open the SnapViewVol volume. The file
SnapView2.txt should not be present.
Step Action
In this step a new SnapView Snapshot will be created for a new source LUN.
It will be used as one member of a SnapView Snapshot Consistent Session.
In this step another new SnapView Snapshot will be created for another new
source LUN. It will be used as a second member of a SnapView Snapshot
Consistent Session.
Right-click RG10 LUN CS2 and select SnapView > Create Snapshot.
Name the Snapshot SnapView CS2.
Do not assign the Snapshot to a Storage Group.
Click OK, Yes, OK.
In this step a new SnapView SnapShot Session will be created using the
Consistent option having two members. This results in the single session
capturing the data state of its two member source LUNs to the same point-
in-time.
Navigate to Data Protection > Snapshots > LUN Snapshots and click the
SnapView Snapshots tab, and then select the Source LUNs tab. Clear any
informational dialog by clicking OK.
Right-click RG10 LUN CS1 and select SnapView > Start SnapView Session.
Name the session Consistent Session and check the Consistent checkbox.
Expand containers SPA and SPB and select RG10 LUN CS2 and click Add.
Then click OK, Yes, OK.
This step will make the SnapView Snapshot virtual LUN available for viewing
by a host.
Click the Snapshot LUNs tab. Select SnapView CS1 and click Activate.
From the Available Sessions pane select Consistent Session and click OK,
Yes, OK.
This step will make the SnapView Snapshot virtual LUN available for viewing
by a host.
Click the Snapshot LUNs tab. Select SnapView CS2 and click Activate.
From the Available Sessions pane select Consistent Session and click OK,
Yes, OK.
7 Close applications:
Close all applications and open windows on the RDP sessions to your host
systems.
Disconnect your RDP sessions to your Windows host systems
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
2 Verify that Clone Private LUNs are configured on your VNX system:
In this step the presence of preconfigured Clone Private LUNs is verified. Also
verified is that the Protected Restore option is enabled. With Protected
Restore enabled, a Clone may not be updated with new I/O during a restore
operation.
Step Action
Navigate to Storage > LUNs and Click Create. Create three (3) LUNs in the
General tab with the following settings:
Click Apply, Yes and OK to complete the operation. Three Thin LUNs are
created having ascending IDs starting with the Thin LUN ID.
4 Clone Properties:
Click the Clone LUNs tab.
Select the Clone LUN 1 and click Properties.
Note the Clone ID ________________________
Click Cancel.
In this step the Data state of the source LUN will be established to illustrate
how the Clone LUN captures the source data state.
From your Student Desktop system, launch the RDP Plus application that
is available from the Desktop view or its taskbar.
Connect to your Windows host according to the following information:
Flush the Source LUN host buffers by typing the following command:
8 Fracture Clone:
In this step the Clone is fractured and is no longer synchronized to the source
LUN.
From your Student Desktop system Unisphere session, navigate to Data
Protection > Clones and select the Clone LUNs tab.
o Select the Clone LUN 1 and click Fracture, Yes, OK. The Clone
state will change to Consistent.
Select the Clone LUN 1 and click Properties.
What is displayed after “Is Fractured”? _____________________
Click Cancel
In this step the Clone LUN is made available to the peer host.
10 Make the Clone visible to the secondary host, and add a text file:
In this step the data state of the Clone LUN is modified to illustrate
operations to a fractured clone.
Launch the RDP Plus application and establish an RDP session to your
Peer Windows host according to the following information:
Flush the Source LUN host buffers by typing the following command:
Flush the Source LUN host buffers by typing the following command:
In this step the data state of the Clone is reverse synchronized to the source
LUN.
From the existing RDP session to your Windows host, open a Command
Prompt.
Change to the directory that contains admsnap
Type the following command:
admsnap_win2k12.exe clone_activate
C:\Program Files
<x86>\EMC\ServerUtility\admsnap_win2k12.exe
clone_activate
From your existing RDP session to your Windows host, access Server
Manager.
From the Server Manager window, select File and Storage Services >
Volumes > Disks.
Click on Tasks and select Rescan Storage.
Disks that were previously allocated to the host may still be present.
Your disk should appear as “Offline”. Right click on the drive and select
“Bring Online”.
A message will appear asking if you are sure you want to bring this disk
online on the server. Click Yes.
Verify that the drive is “Online”.
Step Action
In this step the data state of the second source LUN is established.
6 Add a Clone:
In this step a Clone LUN is selected for the second Clone Group.
Select Source LUN 2 and select Add Clone.
Expand the Thin LUNs container to view a list of available LUNs
(remember only LUNS of the same size are eligible).
Select Clone LUN 2 and apply the following parameters:
Check the Use Protected Restore checkbox.
Recovery Policy: Automatic
Synchronization Rate: High
Click Apply, Yes, OK, Cancel.
In this step both Clone LUNs will be fractured at the same time to illustrate a
consistent fracture time for each LUN preserving the point-in-time
restartable copy across the set of clones..
Tasks: In this lab exercise, you will perform the following tasks:
Verify that the VNX Snapshots feature is enabled on the
VNX
Verify that the required Pool and Pool LUNs are present
on the VNX
Create and Test a VNX Snapshot
Test the VNX Snapshot Restore feature
Start and test a VNX Snapshot Consistency Group
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
CG LUNs: __________________________________________________
CG Snapshot: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
This step creates a LUN to be used as a Primary LUN for VNX Snapshots to
replicate.
Navigate to Storage > LUNs and Click Create. Create a LUN in the General
tab with the following settings:
Click Apply, Yes and OK to complete the operation. One Thick LUN is created.
Step Action
In this and the following steps the new Primary LUN is made accessible as a
volume to the primary host.
From the Server Manager Disks pane, right click the new disk and select
Initialize.
A message will appear asking if you are sure that you want to continue. Click Yes.
This step establishes the data state of the Primary LUN to illustrate how VNX
Snapshots replicates the data.
In File Explorer open the volume, right click the empty space and select
New > Folder.
Name the folder Snapshot Folder.
Open the folder Snapshot Folder.
Right click the empty space and select New > Text Document.
Name the file Snapshot_file.txt.
Open Snapshot_file.txt and add some text into the file, such as your student
number, date and time and save it.
This step creates a VNX Snapshot which captures the point-in-time data state
of the Primary LUN.
Open an RDP session to your Peer Windows host. Verify that the mount point is
shown as an uninitialized disk in Server Manager.
In this step a copy of the VNX Snapshot is made and attached to the VNX
Snapshot Mount Point. The snapshot copy presents a point-in-time data
state of the Primary LUN to the secondary host.
The VNX Snapshot Copy should now show Yes under the Modified column, and
should also show that it is attached to your Peer Windows host.
10 Create a file on the VNX Snapshot from your Peer Window host:
This step creates data on the VNX Snapshot copy to illustrate how data
operations to it do not affect the Primary LUN data state.
Rescan disks on your Peer Windows host. You should now see a 10 GB
disk with the same data content as primary LUN (Thick LUN). It will have
a different drive letter.
Verify that the new file is not present on the primary LUN (on your Windows
host).
Step Action
1 Flush host buffers on your Peer Windows host, and detach the Snapshot:
This is a preparatory step for the Snapshot copy Restore operation. The host
buffers are flushed to ensure the data written to the snapshot copy is flushed to
disk. Then the snapshot copy is detached from the host.
From the RDP session to your Peer Windows host, flush the host buffers for the
snapshot.
Change to the directory where admsnap is found by typing the following:
cd c:\Program Files <x86>\EMC\Unisphere Server
Utility\
Flush the Source LUN host buffers by typing the following command:
2 Take the primary LUN offline, and restore VNX Snapshot copy:
This step prepares the Primary LUN for the Restore operation by first flushing the
primary host buffers to the Primary LUN and deactivating it. Then the Restore
operation from the Snapshot copy is performed to the Primary LUN. A restore
point snapshot of the Primary LUN is created to capture its data state prior to the
Restore operation.
Open a Command Prompt on your Windows host.
Change to the directory where admsnap is found by typing the following:
cd c:\Program Files <x86>\EMC\Unisphere Server
Utility\
Flush the Source LUN host buffers by typing the following command:
This step verifies the data state of the snapshot copy has been restored to the
Primary LUN.
Activate the primary LUN with admsnap:
admsnap_win2k12 clone_activate
Confirm that the primary LUN is visible to your Windows host. It will likely have
a different drive letter.
Verify that the primary LUN has the same files as the VNX Snapshot.
Why are files Snapshot_file.txt and Snapshot_file_new.txt both present on the source
LUN?
_______________________________________________________________________
Step Action
This step creates two new LUNs to be used as Primary LUNs for a Snapshot Consistency
Group.
Navigate to Storage > LUNs and Click Create. Create two LUNs in the General tab
with the following settings:
Click Apply, Yes and OK to complete the operation. Two Thick LUNs are created
with IDs in ascending order.
This and the next few steps creates access to the two LUNs by the Primary host as
volumes.
From the Server Manager Disks pane, right click the new disk and select Initialize.
A message will appear asking if you are sure that you want to continue. Click Yes.
This step creates a data state on each of the new Primary LUNs that are in the
Consistency Group.
Open File Explorer and create text files on each new volume.
This step creates a Snapshot Consistency Group with the two new Primary LUNs as
members.
In Unisphere, navigate to Data Protection > Snapshots > LUN Snapshots. From the
right side tree, in the Consistency Group section, click Create Snapshot Consistency
Group. Read the Welcome dialog, and click Next.
Name the Consistency Group Snap CG. Add a description if desired, and click Next.
Select the 2 CG LUNs created in the previous step. Click Next.
Read the Summary screen, verify that the information is correct, and click Finish.
Read the Results screen, and click Finish if the operation succeeded.
This step creates a Snapshot of the Primary LUNs in the Consistency Group. Both
Primary LUNs will have the same point-in-time captured for their data states.
Does the Snapshot have the Modified property set to Yes? Explain the current state of
the property.
_____________________________________________________________________
Were you able to successfully perform this operation? Explain why you see the result
shown.
________________________________________________________________________
This step creates the Snapshot Mount Point needed to attach the snapshots to the
secondary host.
Read the messages in the Results dialog (they should all show green check marks) and click
Finish.
Verify that CG Snapshot now has an entry under the Attached column.
12 Verify that the Peer Windows host can access the point in time copies:
Do the Snapshots have the same volume names as the primary LUNs?
____________________
Do the Snapshots have the same drive letters as the primary LUNs?
____________________
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
3 Configure a network interface for the physical network device on the Data
Mover:
Click OK.
The routing entry for the Data Mover default gateway has been preconfigured.
In this step you will confirm the address is correct.
From the Settings for File window, select the Routes tab.
Select the Data Mover from the “Show Network Routing for” drop-down
menu.
Locate the “0.0.0.0” Network Destination address.
Verify the entry is configured with the Gateway Address and the Routed
Interface.
Test the network interface by pinging the IP address of your DNS server.
From the right-side Task pane, under Network Settings, click the Ping –
Data Movers link.
From the Data Mover drop-down list, select your Data Mover.
Form the Interface drop-down list, select your Data Mover Address.
In the Destination: field input 192.168.1.50.
Click OK.
From the Settings > Network > Settings for File page, select the DNS tab.
From the “Show DNS Domains for:” drop-down menu, select Data
Mover.
The Data Mover DNS settings have already been configured on your VNX
system.
Confirm that the information from the DNS Settings table matches the
information below.
If the information above does not match what is displayed in Unisphere, ask
your instructor for assistance.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
VDM: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Click OK.
Review the information displayed in the “VDMs” tab for your VDM.
Confirm it is named correctly, is assigned to your Data Mover and its
status is “OK”.
If the information is incorrect, select your VDM and click Properties and
make the needed corrections. Ask your instructor if you need assistance.
Click OK.
Review the information displayed in the “File Systems” tab for your File
System. Confirm your VDM is shown as R/W in the “Data Mover”
column.
If the information is incorrect, select your File System and click Properties
and make the needed corrections. Ask your instructor if you need assistance.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Click OK.
The VNX volume manager, AVM, is used to construct the file system. AVM
first creates a stripe volume from five available disk volumes. It then makes
a slice volume from the stripe. A metavolume is created from the slice that
is used by the file system.
Record the meta volume that your file system resides on.
_________________________________________________________
_________________________________________________________
Record the disk volumes that AVM used to create your stripe volume.
_________________________________________________________
AVM extends the file system size by creating another slice volume from the
existing stripe volume. A new metavolume is created from the new slice. The
new metavolume is added to the existing metavolume that the file system is
constructed from.
Record the name of the new metavolume created.
_____________________________________
Record the name of the new slice volume that the new metavolume uses.
______________________________________
Close Unisphere
End of Lab Exercise
Purpose: In this lab exercise, you will export a file system and assign
root privileges to your Linux host.
NOTE: The screenshots used in this Lab Exercise are meant
to be used as examples. You may have different values/data
on your VNX system.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Step Action
1 Login to Unisphere:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Click OK.
The NFS Exports page displays the exported path of the file system.
From your Student Desktop, use PuTTY to open an SSH to the Linux Host
Address.
Log into the host with the following credentials:
From the terminal window, create a local directory to mount the file
system that you have exported via NFS. Type the following:
cd /
mkdir /fs1
cd /fs1
ls –al
Can you see the directories .etc and lost+found? (They should not
be visible)
NFS mount this directory to the exported file system on your Data
Mover. Type the following:
cd /
mount Data Mover Address:/File System 1 /fs1
df (confirm that the mount is listed)
cd /fs1
ls –al
Note: By default a new directory is empty. Therefore, when you created your
/fs1 directory on the client it was empty. However, after NFS mounting it to
your Data Mover, /fs1 is now being redirected to a file system showing
lost+found and .etc (hidden) directories.
Click OK.
cd /
mkdir /engdir (this directory will be used as a mountpoint)
mount Data Mover Address:/File System 1/engineering /engdir
df
ls –l | grep engdir
Notice that the permissions on the new directory engdir are the permissions
you setup earlier: 775 read, write, and execute for the owner and group. And
Read and execute for others.
Using PuTTY, open another SSH session to the Linux Host address and
login with the following credentials:
login as: swoo
password: emc2Admin!
Change directory to engdir. Create a new file and name it swoofile.
cd /engdir
touch swoofile
ls -l
Were you able to create a new file? _____________________
Were you able to obtain a listing? ___________________
You should not be able to create the new file because the user swoo is
neither the directory owner nor belongs to the engprop group. However,
swoo still can read and execute.
9 Lab cleanup:
Exit the SSH sessions to the Linux Host address for users: swoo, eplace,
and epallis by running the exit command. Leave the existing SSH session
for the root user open.
exit
From the SSH session for the root user, unmount and delete
mountpoints. Then exit the SSH session.
cd /
umount /fs1
umount /engdir
rmdir /fs1
rmdir /engdir
exit
Note: Deleting the file system removes its mountpoint and the associated
meta volumes, stripe and slice volumes. This space has been returned to the
Storage Pool for re-use.
Step Action
Click OK.
Navigate to Storage > Shared Folders > NFS and click Create.
Enter the following information:
cd /
mkdir /fs2
From the df output verify that the VNX File System 2 export is mounted on
the Linux host fs2 directory.
Change to the /fs2 directory and create a new directory called student.
cd /fs2
mkdir student
chmod 777 student
cd student
echo “THIS IS A TEST” > File
Go back to your Unisphere session and export the File System 2 file system at
the sub-directory level.
Navigate to Storage > Shared Folder > NFS and click Create. Define the
export as follows:
From your existing PuTTY session to Linux Host Address, create a new
directory and mount the NFS export.
cd /
mkdir /student
mount Data Mover Address:/File System 2/student /student
From your Student Desktop, open another PuTTY session to the Peer
Linux host (Peer Linux Host Address) and login with the Peer Linux Root
Credentials.
Create a new directory on the Peer Linux host named Student number.
cd /
mkdir /Student number
Mount the above directory to the file system that you exported in the
previous step.
cd /Student number
touch file
8 Unmount the directory and logout from the Peer Linux host:
Unmount /Student number and exit from the your PuTTY ssh session to the Peer
Linux host.
cd /
umount /Student number
rmdir /Student number
exit
9 Create a user file in the mounted directory in the primary Linux host:
From the PuTTY ssh session to the Linux Host Address create a user file in
the student directory.
cd /student
touch newfile
Do you have write permissions? _____________. You should be able to
create a new file because the file system has been export as read write to
this particular host.
10 Lab Cleanup:
Umount and delete mountpoints and exit from the PuTTY ssh session to
the Linux Host (Linux Host Address).
cd /
umount /student
rmdir /student
umount /fs2
rmdir /fs2
exit
From Unisphere delete the exports for File System 2 by navigating to Storage >
Shared Folders > NFS.
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
VDM: __________________________________________________
Step Action
1 System Login:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
In this lab you will implement CIFS into the lab Active Directory domain
hmarine.test. DNS is required for the AD environment and for VNX CIFS
Server operations. To prepare for the CIFS implementation, you will need to
verify and prepare both physical Data Movers in the VNX.
Click Cancel.
Repeat the verification for your Peer Data Mover.
Navigate to Setting > Network > Settings for File and select the
Interfaces tab.
Select your Data Mover Address and click Properties.
Modify the interface “Name:” to the CIFS interface. Leave all other
interface setting unchanged. Click OK.
Click OK.
Review the information for the newly created interface. Verify it has been
created with the correct information detailed above. If the information is
incorrect, select the interface and click Properties to make the needed
corrections. Ask your instructor if you need assistance.
End of Lab Exercise Part 1
Step Action
Navigate to Storage > Shared Folders > CIFS and select the CIFS Servers
tab.
Click Create to create a CIFS Server according to the following
information:
Click OK.
Review the information for the newly created CIFS Server. Verify it has been
created with the correct information detailed above. If the information is
incorrect, select the CIFS Server and click Properties to make the needed
corrections. Ask your instructor if you need assistance.
2 Verify CIFS Server Domain Join:
From the “CIFS Servers” tab select your CIFS Server and click Properties.
Note: You can use the “Filter” field on the page to help locate your CIFS
Server. Input your Student number into the field to display your CIFS
Server.
Review the information and verify the “Domain:” section displays the
(Domain joined) comment.
If the CIFS Server did not join the domain, you can retry the join operation
detailed in the previous step. Ask your instructor if you need assistance.
Click Cancel.
End of Lab Exercise Part 2
Step Action
Navigate to Storage > Shared Folders > CIFS and select the Shares tab.
Click Create to create a CIFS Share according to the following
information:
Click OK.
Click Connect.
In the Open: field input the path to your top level share. The format of
the path is:
\\<server>\<share>
Where <server> is your CIFS Server and <share> is Top$
Click OK.
The share opens to the .etc and lost+found folders. These folders are at the
top-level of all the VNX file systems and should not be disturbed. To prevent
inadvertent modifications to these folders by users, it is a best practice to
create a lower-level share in the file system for users to access.
From the left side tree, right-click Computer and select the Map network
drive option.
In the Folder: field, enter the path to the HMARINE_SHARE. The format
of the path is:
\\<server>\<share>
Where <server> is your CIFS Server and <share> is HMARINE_SHARE
Leave all other options on the page at their default settings and click
Finish.
The share opens and the test_data file create in a previous step is
present. Notice the absence of the .etc and lost+found folders that were
seen from the top-level share. This lower-level share demonstrates the
best practice of preventing users from access and disturbing the .etc and
lost+found folders.
Open the test_data file and verify its data is present. Add another line of
text to the file. Do not save or close the file, just leave the file open in
Notepad. The file will be left open for the last part of the lab exercise.
Also leave the Remote Desktop connection session open to your
Windows server. It will be used in the next part of the lab exercise.
End of Lab Exercise Part 3
Step Action
1 Verify Shares:
The page should display the two CIFS shares created, the top-level share
created with Unisphere and the lower-level share created with Microsoft’s
Computer Management tool. Note: Use the “Filter” field in Unisphere and
input your Student number to limit the display to your shares.
The Windows server is your CIFS client. In the previous part of this exercise,
the client established a CIFS session to your CIFS server. The client performed
a DNS lookup for your CIFS server and cached that lookup in its DNS cache.
When the VDM containing the CIFS server was moved, the CIFS server binds
to the interface of the Peer Data Mover and that interface has a different IP
address. Therefore to reconnect to the CIFS server, the client’s DNS cache
must be flushed so it can do a new DNS lookup for the CIFS server.
On your Windows server, open a Command window which is available
from the Desktop view or its task bar.
6 Access the CIFS data after the VDM move without flushing DNS:
Return to your existing Windows server Remote Desktop session.
Return to your open test_data.txt file in Notepad. Add some text to the
file and save the changes.
The results of this operation can vary depending on how much time has
passed since the new CIFS session was established in step 4 above. If enough
time has passed for the client DNS cache to expire though its default
timeout, the changes to the file will be saved normally. If the client DNS
cache has not expired, you will receive an error stating “The specific network
name is no longer available.”. The error can be cleared and access to the
share returned by flushing the client’s DNS cache or waiting for its normal
cache timeout to occur.
On your Windows server close all open applications.
Disconnect from the Remote Desktop by accessing the Logoff Session
icon which is available from the Windows server Desktop view or its
taskbar.
Purpose: In this lab, you will configure VNX SnapSure and observe
some of its functions. You will also perform a file recovery
and a file system restore.
Create Checkpoints
Please refer to your Class Configuration Sheet for this lab and record the values for each
item listed. You will use these values for the lab exercise.
VNX: __________________________________________________
Checkpoint 1: __________________________________________________
VDM: __________________________________________________
Checkpoint 2: __________________________________________________
Checkpoint 3: __________________________________________________
Checkpoint 4: __________________________________________________
Checkpoint 5: __________________________________________________
Step Action
1 Login to Unisphere:
(If you are not already logged in to your “Student Desktop”) Connect to
your “Student Desktop” via your VDC connection.
From your Student Desktop, open a browser and login to Unisphere on
your assigned VNX using the VNX Address and the user credentials:
sysadmin/sysadmin with Scope Global selected.
Create a new production file system using the available storage pool
3 Create an NFS export for the newly created production file system:
Create an NFS export from the file system created using the default path. Assign
root access to your Linux host.
From your Student Desktop, use PuTTY to open an SSH to the Linux Host.
Log into the host with the following credentials:
From the terminal window, create a local directory to mount the file
system that you have exported via NFS. Type the following:
cd /
mkdir /pfs1
NFS mount this directory to the exported file system on your Data
Mover. Type the following:
mount Data Mover Address:/File System 1 /pfs1
df (confirm that the mount is listed)
Create data on the file system by running the following commands:
cd /pfs1
dd if=/dev/zero of=Monday bs=256 count=10
Verify that you now have objects in the directory: one directory named
lost+found and five files, one for each weekday.
cd /pfs1/.ckpt
ls
Record the name of the File Fystem 1 checkpoint snapshot directory. You will
use the snapshot name later in the exercise.
__________________________________________________________
Note that the snapshot name assigned in Unisphere is not the same as this
directory name.
Create a new production file system using the available storage pool
From the left side tree, right-click Computer and select the Map network
drive option.
In the Folder: field, enter the path to the CIFS Share. The format of the
path is:
\\<server>\<share>
Where <server> is the CIFS Server and <share> is the CIFS Share.
Leave all other options on the page at their default settings and click
Finish.
In the mapped network drive create 12 new text files and name them for
the months of the year (January through December).
12 Create a Snapshot:
From the Windows server, launch File Explorer and expand the
Computer directory.
Right-click your share and select Properties.
Click on the Previous Versions tab (this is the VSS Client).
Do you see the snapshot you just created? What is the name of the File
System 2 checkpoint snapshot?
_______________________________________________________________
Step Action
On your Linux host, verify that the files created in the previous section of
the lab are still present in the mounted folder.
ls –l /pfs1
Remove and verify the removal of the Tuesday file from File System 1 by
running the following commands:
cd /pfs1
rm Tuesday
ls -l
ls
Recover the deleted file from the snapshot and verify the file recovery by
running the following commands:
cp Tuesday /pfs1
cd /pfs1
ls –l
You have just recovered an individual file from the point-in-time snapshot
using CVFS. This leaves all other copies of files as they are currently. If any
new files had been created after the snapshot, they are preserved.
3 Refresh a Snapshot:
ls /pfs1/.ckpt
_______________________________________________________
4 Verify that the new file has been preserved by the snapshot:
From the PuTTY SSH session to your Linux host, enter the following
command:
Create a new file in the /pfs1 directory named Sunday by running the
following command:
ls -l /pfs1/.ckpt
From the PuTTY SSH session to your Linux host, remove any two files
from the /pfs1 folder and confirm they have been successfully removed.
In Unisphere, select Checkpoint 3 and click Restore - when prompted,
enter the new snapshot name of Checkpoint 4.
When the operation is complete, from the PuTTY SSH session to your Linux
host, view the contents of the /pfs1 folder using the ls command.
You have just performed a restore of a point-in-time copy of the file system.
This operation reverts all files to a previous data state and erases any files
that were created after the snapshot (e.g., the Sunday file).
8 Lab cleanup:
From the PuTTY SSH session to your Linux host, unmount and delete the
/pfs1 directory.
From Unisphere, delete Checkpoint 5, Checkpoint 4, Checkpoint 3,
Checkpoint 1, File System 1 NFS export and the File System 1 file system.
Note: Leave the File System 2 and each one of the CIFS components to be
used on the next part of the lab.
Step Action
1 Snapshot verification:
From the RDP Plus session to your Windows Server, verify that the CIFS
share is still mapped and that there are 12 text files in the share named
after each month of the year.
In Unisphere, verify that there is a snapshot for File System 2 named
Checkpoint 2.
From your RDP Plus connection to your Windows Server, delete several
files from the CIFS Share.
From the Windows server, launch File Explorer and expand the
Computer directory.
Right-click your share and select Properties.
Click on the Previous Versions tab, select the snapshot, and click
Restore.
At the confirmation screen, click Restore once again.
Ignore the two permissions warning messages by clicking Skip. The error
relates to permissions on the .etc and lost+found directories and is
expected.
You have just restored a file system from a point-in-time copy using
Snapsure via the VSS Client. This will erase any files that were created after
the snapshot was created.
From the File Explorer window, open the mapped CIFS share folder
Delete January and February.
Right-click the CIFS share object on the left-pane and select Properties
Navigate to the Previous Versions tab.
Select the snapshot and click Open.
Select January and February and copy them back to the CIFS Share
folder.
You have just restored individual files from a point-in-time copy using VSS
Client. This allows all other files to remain in their current revision while
recovering previous versions of specific files.
6 Lab cleanup:
From the File Explorer window, expand Computer from the left pane.
Right-click the mapped network drive to your CIFS share and select
Disconnect.
In Unisphere, delete Checkpoint 2, the CIFS Share, and the File System 2.
Close your RDP session to the Windows server.
Hurricane Marine
Windows Users & Group Memberships
HMARINE.TEST Domain
Username Full Name Global Group
Administrator Domain Admins
EPallis Earl Pallis Propulsion Engineers, Managers
EPing Elvin Ping Propulsion Engineers
EPlace Etta Place Propulsion Engineers
EPope Eddie Pope Propulsion Engineers
EPratt Eldon Pratt Propulsion Engineers
EProh Elliot Proh Propulsion Engineers
EPutter Egan Putter Propulsion Engineers
ESazi Ed Sazi Structural Engineers
ESele Ellen Sele Structural Engineers
ESimons Eric Simons Structural Engineers
ESong Eva Song Structural Engineers
ESouth Edgar South Structural Engineers, Managers
ESwailz Evan Swailz Structural Engineers
ITallis Iggy Tallis IS, DOMAIN ADMINS
ITechi Ira Techi IS, DOMAIN ADMINS, Managers
ITei Isabella Tei IS, DOMAIN ADMINS
ITeribl Ivan Teribl IS, DOMAIN ADMINS
LMinacci Liza Minacci Director of Marketing, Managers
PTesca Perry Tesca President, Managers
SEammi Sal Eammi Eastcoast Sales
SEarly Sage Early Eastcoast Sales
SEcho Sam Echo Eastcoast Sales
SElton Santos Elton Eastcoast Sales
SEmm Sarah Emm Eastcoast Sales, Managers
SEpari Sadie Epari Eastcoast Sales
SEttol Saul Ettol Eastcoast Sales
SEwer Sean Ewer Eastcoast Sales
SExtra Sash Extra Eastcoast Sales
SWai Seymore Wai Westcoast Sales
SWall Sergio Wall Westcoast Sales
SWari Seve Wari Westcoast Sales, Managers
SWassi Seve Wassi Westcoast Sales
SWeir Seda Weir Westcoast Sales
SWelles Sema Welles Westcoast Sales
SWest Scott West Westcoast Sales
SWillet Selena Willet Westcoast Sales
SWitt Selma Witt Westcoast Sales
SWong Seiko Wong Westcoast Sales
SWoo Steve Woo Westcoast Sales