SAN Management

(1)

Lab Guide

(2)

Copyright

Copyright © 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 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.

EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and where information lives, are registered trademarks or trademarks of EMC Corporation in the United States and other countries.

Revision Date: December 2013 Revision Number: 2.0

(3)

Document Revision History

Rev # Date Comments

1.0 March 2004 Original version 1.2 December 2004 Revised materials. New lab guide. 1.4 October 2005 Revised materials. Including emerging SAN protocols. 2.5 March 2007 Revised materials. 3.0 July 2007 Revised materials. Removed VisualSAN. Included SMC and ControlCenter 6.0 updates 3.0.1 May 2008 Revised format errors 4.0 May 2009 Revised materials and labs 5.0 October 2010 Revised materials and labs, added Virtual Fabrics 5.2.b February 2011 Migrated from SYMCLI to SMC, Fixed problems with Lab Guide 5.2.c March 2011 Fixed Enginuity code issue 5.4.b August 2011 Updated content for VNX, removed Control Center 5.5.c February 2012 Lab Remediation 6.0.4 April 2012 Revised Material and Labs. 1.0 February 2013 Course extended to 5 days, Asset code changed. Version restarted at 1.0 1.5 July 2013 Updated content according to Instructor Feedback Database entries 2.0 December 2013 Updated content, changed order of some labs, removed some lab tasks and added new ones.

(4)

(5)

Lab Exercise 1: B-Series Management

Purpose: The purpose of this lab is to provide the student with a working knowledge of the tools needed to explore the B‐ Series SAN environment. Tasks: Students perform the following tasks:  Verify proper switch installation using basic CLI commands  Check out the current state of the switch using Web Tools  Install CMCNE, and then use it to discover your switch, and check its current state. References: B‐Series Switch Tools Module

(8)

Lab 1: Part 1 – B-Series Basic CLI Commands

In this exercise you will telnet into your B-Series switch and use CLI commands to investigate the current switch status, firmware version, installed licenses, and other configured

parameters.

Step Action

1 From the Windows management host, open the Command Prompt and telnet to your Pod’s B‐Series switch.

Refer to your lab configuration guide for IP address information. telnet <switch IP Address>

2 Use admin as your user name and the password provided by your instructor in the Lab Configuration Guide.

3 Use the help command to view a list of CLI commands. Use the “| more” option to display only one page at a time. Use the space bar to advance one page. # help | more Type help in front of a command to see the help page. # help switchshow Notice that the help page is quite extensive. 4 Verify the current firmware version. # firmwareshow What do you learn from the information displayed? ____________________________ _______________________________________________________________________ 5 Verify the installed licenses. # licenseshow Which licenses are installed on your switch? ___________________________ ________________________________________________________________

(9)

Step Action 6 Display all the switch configuration parameters. # configshow | more What is the purpose of this command? ______________________________ _______________________________________________________________ 7 Verify the configured management network information. # ipaddrshow What is the current chassis IP address and subnet mask? ________________ ______________________________________________________________________ 8 Display port speed, trunking mode, state and other configuration for all the ports in the switch. # portcfgshow What speed are the first four ports set to? ___________________________ ______________________________________________________________ 9 Use the following command to view the switch name, interop mode, domain ID and other useful information. # switchshow Are there currently any devices logged into this switch? ________________ ______________________________________________________________

(10)

Step Action 10 Check the configured users. # userconfig --show When was the last time the password was changed for your user account? _______________________________________________________________ Does the password for this account have an expiration date? ______________________________________________________________ 11 Are there other switches in this fabric? _________ # fabricshow 12 Verify that the switch status is healthy. # switchstatusshow If the status is anything other than HEALTHY, notify your instructor. 13 Terminate the telnet session and close the Command Prompt. # exit

(11)

Lab 1: Part 2 – B-Series Management using Web Tools

In this lab exercise you will use Web Tools to check your switch’s operational state. Step Action 1 From your management Windows host, type your Pod’s B‐Series switch IP address in a browser and login using Web Tools. The username and password is the same as that used to login to your switch using Telnet. 2 On the Switch Events, Information pane, click the Switch Information tab. Verify that the following match what you saw using CLI commands: Fabric OS version Domain ID WWN Role Ethernet Configuration information 3 From the Manage section, click Switch Admin. 4 When the Switch Administration window opens, click the License tab and verify the installed licenses match what was displayed with the CLI. 5 Click the User tab and note the configured users. Does this display tell you the last time the password was set for your user account? __________________________________________________ Close the Switch Administration window.

(12)

Step Action 6 Analyze the switch status by clicking Status above the Switch View. You should see the same status as was displayed using CLI commands. Close the Switch Health Report window. You can also click on the Temp, Power, and Fan buttons to get additional information. 7 Click Port Admin from the Manage section. 8 Are any ports connected to hosts or storage arrays Persistently Disabled? __________________ If they are, persistently enable them. 9 Verify that the port type, speed, and status for the hosts and storage ports are what you expect them to be. Use the scroll bar, if necessary, to see all of the available columns. Click on a few ports in the FC Ports Explorer pane and note the information displayed.

10 Click on the Show Basic Mode button in the top right corner. Or if that button isn’t there, click on the Show Advanced Mode button.

What happens? _________________________________________________ _______________________________________________________________

11 Close the Port Admin window and close Web Tools. Click Logout.

(13)

Lab 1: Part 3 - Install CMCNE and Discover Fabric

In this lab exercise you will install CMCNE, discover your fabric, and display information from the most commonly used screens. Step Action 1 From the Windows management host, locate the CMCNE installation file. Open Windows Explorer and go the following folder: Local Disk (C:) software\Connectrix Manager and double‐click install1201. InstallAnywhere will begin. 2 Use the default options and click next on each screen until the installation completes. 3 On the Installation Complete screen, verify that CMCNE has been successfully installed. Check the box to Launch CMCNE Configuration if it is not already checked. Click on Done. 4 Next you will see the CMCNE Configuration Tool. Respond to each screen as shown below. Welcome Take a moment to look at all of the CMCNE configuration settings that you may configure with this program. Click Next. Copy Data and Settings from previous releases This is a new installation, so select: No, don’t copy any data and settings. Click Next. Package Select SAN with SMI Agent Click Next.

(14)

Step Action 5 Installation Type Choose CMCNE – 75 days Trial Select Next. FTP / SCP / SFTP Server Accept the defaults and click Next. Database Administrator Password (dcmadmin) Accept Default password and click Next. Server IP Configuration Use your management server name and IP address. Click Next Server Configuration Use the default server ports. Click Next. SMI Agent Configuration Accept the defaults and click Next. SAN Network Size Select Small (managing up to 2000 switch ports, 1‐20 domains) Click Next. Server Configuration Summary Verify all values are correct and click Next. Start Server Choose defaults and click Finish. 6 Launch CMCNE. Login with the default User ID and password: User ID: [supplied by instructor] Password: [supplied by instructor]

(15)

Step Action 7 CMCNE will come up displaying the dashboard. Since this is a new installation, no products have been discovered. In the SAN Status window, click on Discover. The Discover Fabrics dialog is displayed. Click Add. 8 Add Fabric Discovery SNMP configuration: Automatic Fabric Name: Podx (where x is the pod number) IP Address: (the IP address of your switch) User ID: [supplied by instructor]. Password: [supplied by instructor]. Click OK. 9 CMCNE should now discover your fabric. You should see your newly discovered fabric on the Discover Fabrics window. You may close this window and return to the main CMCNE window. Select the SAN tab. You should see your switch in the topology pane. 10 Take some time and get familiar with the menus available on the SAN tab.

(16)

(17)

Lab Exercise 2: B‐Series Configuration

Purpose: The purpose of this lab is to provide the student with a working knowledge of basic B‐Series switch configuration operations including changing the switch name, checking port status, displaying logins, enabling and disabling the switch, changing the Domain ID, and uploading and downloading switch configurations. Tasks: Students perform the following tasks:  Using CLI commands, perform the following tasks: o Change the switch name o Check port status o Display logged in devices o Enable and disable the switch o Change the Domain ID o Upload a switch configuration to the FTP server  Using Web Tools, complete the following tasks: o Disable the switch o Change the switch Domain ID o Download Config to switch o Specify port configuration parameters References: B‐Series Switch Tools Module.

(18)

Lab 2: Part 1 – B-Series Configuration Using CLI

In this lab you will use CLI commands to change the switch name, check port status, display logged in devices, disable the switch, change the switch Domain ID, and upload the current switch configuration to a file on the FTP server.

Step Action

1 From your Windows management host, log into your Pod’s B‐Series switch through telnet.

2 Configure the switch name as: pod#_switch model_switch# # switchname pod#_switchmodel_switch# Ex: # switchname pod1_dcx4s_1

3 Verify the switch name was changed. # switchname 4 Verify the hosts and storage ports are logged in the switch. # switchshow # nsshow 5 Set the speed to automatic for all the host ports. Automatic speed is equal to 0. Repeat this step for every host. # portcfgspeed <port #> 0 Use help to find a variation of this command to configure a range of ports. What command did you use to configure a range of ports? _____________________ Note: The hosts’ port assignments can be found using the command above or in the lab configuration guide. 6 Disable the switch. # switchdisable

(19)

Step Action

7 Set the switch domain ID to 1. Leave other parameters with their default values pressing CTRL + D or pressing ENTER key to accept the defaults.

# configure Configure...

Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [98] 1

CTRL + D

WARNING: The domain ID will be changed. The port level zoning may be affected

8 Enable the switch. # switchenable 9 Upload the configuration to your FTP server listed in the lab configuration guide, or ask your instructor for an available one (usually is the Linux server). Make sure the file uploads successfully. # configupload Protocol (scp, ftp, local) [ftp]: ftp

Server Name or IP Address [host]: <ftp server IP

Address>

User Name [user]: <ftp user-name> File Name [config.txt]:

<switchname>_yyyymmdd_config.txt

Section (all|chassis|FID# [all]): <ENTER> Password: <ftp password>

configUpload complete: All config parameters are uploaded

10 Logout of the switch.

(20)

Lab 2: Part 2 – B-Series Configuration Using Web Tools

In this lab you will use Web Tools to disable the switch, change the switch Domain ID, download a previously saved configuration to the switch, and specify port operational parameters. Step Action 1 From your Windows management host, type your Pod’s B‐Series switch IP address in a browser and login to Web Tools. 2 Click Switch Admin under the Manage section. 3 Select the Disable radio button under Switch Status. 4 Click Apply. 5 When prompted for confirmation, click Yes. 6 Under the Switch Name and Domain ID section, change the Domain ID to 10. 7 Click Apply. When prompted for confirmation, click Yes. 8 Click Show Advanced Mode at the top right corner of the Window. Note: If the button says Show Basic Mode, you are already in advanced mode. 9 Click the Configure tab. 10 Now click the Upload/Download tab, at the bottom of the window.

(21)

Step Action 11 Under Function, select Config Download to Switch. Set the following parameters: Host Name or IP: <ftp host IP address> User Name: <username> Password: <password> Protocol Type: File transfer Protocol (FTP) Configuration File Name: <switchname>_yyyymmdd_config.txt Note: The configuration file name must be the same as the uploaded in the last lab. 12 Click Apply. When prompted for confirmation, click Yes. 13 When the config has downloaded successfully, click the Switch tab. 14 Click Refresh. 15 Make sure the domain ID has been reverted to 1. 16 On the Switch Status section, click the Enable radio button. 17 Click Apply. When prompted for confirmation, click Yes. 18 Close the Switch Administration window. 19 On the Manage section click Port Admin. 20 From the Port Administration window, click the first storage port. The storage port assignment can be found in the lab configuration guide. 21 Click Edit Configuration. If prompted for confirmation click Yes.

(22)

Step Action 22 From the port configuration wizard, click Next in the Specify Port Parameters Step. 23 In the Specify FC Parameters set the speed to Auto and click Next. 24 Verify the configuration is correct and click Save. 25 Click close when the report is shown. 26 Repeat Step 22 to 27 for every storage port in the switch. 27 Close the Port Management window and the Port Administration window. 28 Click Switch Admin on the Manage section. 29 On the Report section, click View Report. 30 Analyze the report. Close the report, the Switch Administration window and Web Tools.

(23)

Lab Exercise 3: MDS-Series Management

Purpose: The purpose of this lab is to provide the student with a working knowledge of the tools needed to explore the MDS‐ Series SAN environment. Tasks: Students perform the following tasks:  Verify proper switch installation using basic CLI commands  Check out the current state of the switch using Device Manager  Install DCNM, and then use it to discover your switch, and check its current state. References: MDS‐Series Switch Tools Module.

(24)

Lab 3: Part 1 – MDS-Series Basic CLI Commands

In this exercise you will telnet into your MDS-Series switch and use CLI commands to

investigate the current switch status, firmware version, installed licenses, and other configured parameters. Step Action 1 From the Windows management host, telnet to your Pod’s MDS‐Series switch. 2 Use admin as your user name and the password provided in the lab configuration guide. 3 The initial prompt you are presented with after logging in is the exec mode prompt. To see a listing of all of the exec mode commands, type a ? at the prompt. # ?

When you see -- More -- use the space bar to display the next page of commands. 4 You can also find the options for a specific command. For example, to see all the variations of the show command, type: # show ? 5 To get to the config mode prompt type:config at the prompt. Notice how the prompt changes. 6 To see the commands available at the config mode prompt, type a ? at the prompt. Example: Switch(config)# ? Page through the displayed commands. 7 Type Exit to return to exec mode. # exit

(25)

Step Action 8 Type show version. What is the BIOS version? ______________ What is the kickstart version? ___________ What is the name of the kickstart image? What is the system version? ____________ What is the name of the system image? 9 To verify which licenses are installed and being used, type show license usage. Record the licenses installed on your switch. ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ ____________________________________________ Do any of your licenses have expiration dates? 10 Display the startup configuration. # show startup-config Page down through the configuration. NX‐OS also gives you the flexibility to partially type in commands, and it will figure out the full command. For example, for the previous command you can type: # sh start 11 Display the management port configuration. # show interface mgmt0

(26)

Step Action

12 View a brief description of the port status where your hosts are connected. # show interface brief

Which ports have a status of up?

__________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________

13 To find how many modules are installed, and their status, type: # show module 14 Verify the configured user accounts. # show user-account 15 Verify the switch status is healthy. # show system health # show environment

If you see any switch health issues, notify your instructor.

16 Terminate the telnet session and close the Command Prompt. # exit

(27)

Lab 3: Part 2 –Install DCNM and Discover Fabric

In this lab exercise, you will go through all of the steps of a DCNM installation on your Windows system and then verify the Cisco DCNM servers have started after the installation.

Step Action 1 Login to your assigned podx‐win1 system (where x is your pod number) 2 From the Windows management host, locate the DCNM installation file. Open Windows Explorer and go to the following folder: Local Disk (C:) software\Cisco and double‐click dcnm‐installer‐windows.6.1.1a. InstallAnywhere will start. 3 Introduction The introduction screen shows all the steps for installing DCNM. Click Next. Read the information on the Installation Help screen, and then click Next. 4 Choose Install Folder Accept the default and click Next. 5 Select the following Database Options RDBMS: Install PostgreSQL Inter the DCNM DB User: dcnmuser Enter the DCNM DB password: dcnmuser123 Confirm the DCNM DB password: dcnmuser123 Click Next.

(28)

Step Action 6 Configuration Options Select your podx‐win1 IP address as the server IP address. SAN WebServerPort: Leave at default LAN WebServerPort: Leave at default Click Next. If you get a message, saying that the ports are already in use, click on Advanced Settings. Then click on Resolve Port Conflicts. Click OK. Record the new port numbers: SAN WebServerPort: __________ LAN WebServerPort: __________ Click Next. 7 IP Multicast Addresses Configuration We will not be using this feature, so just click Next. 8 Choose Archive Folder for DCNM LAN Accept the default and click Next. 9 Local User Credentials Local Admin Username: admin Password: password Click Next. 10 Authentication Settings Select Local, and then click Next. 11 Create Shortcut Select On the Desktop, and then click Next. 12 Pre‐Installation Summary Review the information on this screen. Click Next.

(29)

Step Action 13 Installing DCNM Monitor the installation progress. This will take a few minutes. 14 Install Complete Check Start DCNM LAN and SAN Services. Click Next. Notice that your desktop now has icons for both DCNM SAN Client and Cisco Device Manager, as well as icons to start and stop the DCNM servers. Click Done. 15 When exiting the installation program, the DCNM Server service should start. This will take a few minutes. When the service starts, the service startup screen will go away. Verify the DCNM services have started by going to Start > Administrative Tools > Computer Management and expand Services and Applications. Click on Services. Verify that the Cisco DCNM LAN Server and Cisco DCNM SAN Server have started. 16 Close the Computer Management window.

(30)

Lab 3: Part 3 – MDS-Series Management using DCNM-SAN and

Device Manager.

In this lab you will get familiar with both DCNM-SAN and Device manager by using these tools to perform basic switch checks and save the switch system Startup configuration to your desktop.

Step Action 1 If you haven’t already done so, connect to your Windows management host. 2 On the desktop, open the DCNM SAN Client. 3 Log into DCNM using the following credentials: Username: admin Password: password 4 After you log into DCNM the Discover dialog opens. Enter the following parameters:  Seed Switch: Your Pod’s MDS‐Series switch IP Address  Use SNMPv3: Checked  Auth‐Privacy: MD5  User Name: admin  Password: Provided in your documentation 5 Click Discover. When you get the message that your fabric has been discovered, click OK. 6 Control Panel The switch should appear under the Open tab. Verify the switch user name on the Client Username field and the password in the Client Password/Community field. Click on the box to Select this switch, and then click Open. 7 Double‐click your switch in the topology view to launch Device Manager.

(31)

Step Action

8 From the Device Manager menu, click Admin > Licenses. Check the installed licenses, their status and expiration date. 9 Click Close to close the Licenses window. 10 Verify the hosts’ HBAs and storage for your pod are logged into the name server database. Click FC > Name Server. 11 Close the Name Server window. 12 Verify the Domain ID by clicking FC > Domain Manager. Notice the Domain ID is set on a per VSAN basis. 13 Close the Domain Manager window. 14 Verify the running config by clicking Admin > Show Startup/Running Config. 15 From the Show Startup/Running Config window, set the following parameters: Config File Type: Startup TCP Timeout: 30 File Name: Select the Desktop and label the file: pod#_mds_initial_config.txt 16 Click Start. 17 When the configuration download is Done click Close. 18 On your Windows host, uncompress the configuration file (if needed) and open it with Notepad. Analyze the file. 19 Close the configuration file. 20 From Device Manager click Physical > System. Verify the switch name, description, processor speed, and memory.

(32)

Step Action 21 Close the System window. 22 Right‐click each host and storage ports and select Enable. 23 Right‐click the management port (mgmt0) and select Configure. 24 From the Management Port window, click IP Address(es). 25 Verify the IP address is set and click Close. 26 Close the Management Port window and close Device Manager. Note: If prompted to Save the Configuration click Yes. When the configuration is saved successfully, click Close.

27 From DCNM expand Switches and then FC Interfaces in the Physical Attributes pane.

28 Click Physical and verify the port configuration. Notice the configuration, speed, operational status and, if present, the failure cause where your host and storage ports are connected.

29 From the Physical Attributes pane, expand End Devices and click Hosts. Verify the WWN, FCID, link status and HBA information available for the attached hosts.

30 From the Physical Attributes section, click Storage and verify the type of storage, PWWN, FCID and link status for your storage arrays. 31 Now move to the topology view and click the Refresh icon to refresh the map of attached devices. 32 Click the layout map icon to change the topology view. 33 Close DCNM.

(33)

Lab Exercise 4: MDS-Series Configuration

Purpose: The purpose of this lab is to provide the student with a working knowledge of basic MDS‐Series switch configuration operations including changing the switch name, displaying logins, configuring port parameters, enabling and disabling ports, changing the Domain ID, and saving configuration changes. Tasks: Students perform the following tasks:  Using CLI Commands: o Change the switch name o Display name server login information o Configure port parameters o Enable / Disable ports o Change Domain ID o Save changes and copy configuration to FTP server  Using DCNM‐SAN and Device Manager: o Change the switch name o Change the switch domain ID o Download previously saved configuration from the FTP server o Configure port parameters o Save changes References: MDS‐Series Switch Tools Module.

(34)

Lab 4: Part 1 – MDS-Series Configuration using CLI

Using CLI Commands change the switch name, display name server login information, configure port parameters, enable/disable ports, change Domain ID, save changes and copy the saved configuration to an FTP server

Step Action

1 From your Windows host, telnet to the MDS‐Series switch.

2 Move to the configuration mode. # config

3 Configure the switch name as: pod#‐switch‐model‐switch# #switchname <pod#-switchmodel-switch#>

Ex: #switchname pod1-mds9222-1

4 Exit configuration mode. # exit

5 Verify the switch name was changed. # show switchname

6 Verify the ports where hosts and storage are attached by running the command: # show flogi database

7 Move to the interface sub‐configuration mode. Configure all the host ports. The host port assignment can be found from the command in step 6 or in the lab configuration guide. # config # interface fc#/#, fc#/#, fc#/#, fc#/# Note: Replace the #/# with the host ports.

(35)

Step Action

8 Set the speed to automatic for all the host ports. # switchport speed auto

9 Enable the ports. # no shutdown 10 Exit the interface sub‐configuration mode. # exit 11 Move to the interface sub‐configuration mode. Select all the ISL ports between MDS switches. The ISL port assignment can be found in the lab configuration guide. # interface fc#/#, fc#/# Note: Replace the #/# with the ISL ports. 12 Enable trunking for the ISL ports.

# switchport trunk mode on

13 Verify the ISL ports remain shutdown. # shutdown

14 Exit the interface sub‐configuration mode. # exit

15 Configure the Domain ID of 1 on the default VSAN (1). # fcdomain domain 1 static vsan 1

16 Restart the VSAN for the Domain ID change to take effect. # fcdomain restart vsan 1

(36)

Step Action

17 Exit configuration mode. # exit

18 Verify the Domain ID is set to 1 for VSAN 1. # show fcdomain vsan 1

19 Save the configuration changes to the startup config. # copy running-config startup-config

20 Upload the configuration to your FTP server listed in the lab configuration guide. # copy running-config ftp://<IP Address>/

<switchname>_yyyymmdd_config.txt Enter username: <ftp username> Password: <ftp password>

21 Close the telnet session.

(37)

Lab 4: Part 2 – MDS-Series Configuration using DCNM and

Device Manager

Using DCNM‐SAN and Device Manager: change the switch name, change the switch domain ID, download the previously saved configuration from the FTP server, configure port parameters, and save changes. Step Action 1 From your Windows management host, open Data Center Network Manager ‐ DCNM. 2 Log into DCNM and open your switch fabric. 3 From the Logical Domains pane, click your Fabric. This shows your switch in the Information pane. 4 In the Information pane, double‐click your Switch’s logical name. 5 Change the name to pod#. 6 Click the Apply Changes icon. 7 Double‐click your switch in the Topology pane to launch Device Manager. 8 Click FC > Domain Manager. 9 Next, click the Configuration tab. 10 For VSAN 1, double click the Admin DomainId. 11 Change the Domain ID to 10. 12 Click the DomainId Type for VSAN 1. 13 Select preferred.

(38)

Step Action

14 Click Apply.

15 When prompted for confirmation click Yes.

16 Close the Domain Manager window.

17 Restore the backed up configuration. Steps 18a to 18d show how to restore using Device Manager; however, some versions of this GUI tool present a code bug, preventing the restore. If during the execution of steps 18a‐to‐18d you experience this issue, use steps 19a‐ to‐19c as a workaround. Follow steps 18a to 18d to restore a backup using Device Manager 18a Click Admin > Copy Configuration. 18b Now we will restore the backed up configuration. Set the following parameters: From: serverFile To: runningConfig Server Address: <FTP Server IP Address> File Name: /<switch name>_yyyymmdd_config.txt Protocol: FTP UserName: root Password: <host password> Note: The file name should be the same as the one used in the previous lab. 18c Click Apply. 18d When the File transfer success message appears, close the Copy Configuration window. Note: If the transfer experiences a time‐out verify the parameters and try again.

(39)

Step Action

This is a workaround to restore a backed up configuration using CLI. Go through

steps 19a‐to‐19c only in case the steps 18a‐to‐18d did not work.

19a From your Windows host, telnet to the MDS‐Series switch.

19b Download the configuration from your FTP server listed in the lab configuration guide. The file name should be the name as the one used in the previous lab. # copy ftp://<IPAddress>/<switchname>_yyyymmdd_config.txt running-config

Enter username: <ftp username> Password: <ftp password> 19c Verify the “Copy Complete” message appears and close the telnet session 20 Click FC > Domain Manager. 21 Click the Configuration tab and verify the DomainId has been reverted to the one configured in your last lab. 22 Close Domain Manager and Device Manager windows, if prompted to save configuration, click Yes. When the Success message appears click Close. 23 From the Physical Attributes pane of DCNM, expand Switches > FC Interfaces. 24 Click Physical. 25 Change the speed of all the storage ports in the Details pane by clicking Speed Admin for the port, and selecting auto. The storage port assignment can be found within: End Devices > Storage section of the Physical Attributes pane (Switch Interface column). 26 _{When you have finished configuring the ports, click the Apply Changes icon.}

(40)

Step Action

27 Close DCNM.

When prompted to copy running configuration to startup, click Yes.

(41)

Lab Exercise 5: Discover Host and Storage WWN

Purpose: The purpose of this lab is to provide the student with a working knowledge of how to discover hosts, storage ports and switch information using different tools and commands. Tasks: Students perform the following tasks:  Find port WWNs for HBAs on AIX, HP, Solaris, Linux, Windows, and ESXi hosts.  Discover Switch Name Server Information for your assigned B‐Series switch using Web Tools, and from your MDS‐Series switch using Device Manager.  Use the EMC E‐Lab Advisor WWN decoder tool to determine the array ports that have logged into your switches.  Create an environment map using the information gathered from above. References: SAN Management Module.

(42)

Lab 5: Part 1 – Locate and Record Initiator WWN’s

Use the following procedure to gather HBA WWN for this host. Record this information in the Lab Configuration Diagram at the end of this section.

AIX Host

Step Action 1 From your management host, telnet to your AIX host. 2 Gather OS version and model. # uname -a 3 Look for the HBA instances installed in the host # lsdev –Cc adapter | grep fcs

4 Gather useful information about each HBA such as part number, WWPN, and Firmware. Use the instance name gathered in Step 3. # lscfg –vl fcs# HBA 1 WWN: ____________________________________________ HBA 2 WWN: ____________________________________________ 5 Close the telnet session.

(43)

HP-UX Host

Step Action 1 From your management host, telnet to your HP‐UX host. 2 Gather OS version and model. # uname -a 3 Look for the HBA instances installed in the host, the following command looks for both types of HP drivers’ fcd and td. # ls /dev | egrep “fcd|td” 4 Gather useful data about each HBA; make sure to use the HBA instances discovered in the previous Step. # /opt/fcms/bin/fcmsutil /dev/<fcd#/td#> HBA 1 WWN: ____________________________________________ HBA 2 WWN: ____________________________________________ 5 Close the telnet session.

(44)

SOLARIS Host

Step Action 1 From your management host, telnet to your Solaris host. 2 Gather OS version and model. # uname -a 3 Show HBA model and firmware level for all the instances. # fcinfo hba-port HBA 1 WWN: ____________________________________________ HBA 2 WWN: ____________________________________________ 4 Close the telnet session.

(45)

LINUX Host

Step Action 1 From your management host, telnet to your Linux host. 2 Gather OS version and model. # uname -a 3 Verify the WWPN for both HBAs. # cd /sys/class/fc_host # ls # cd host# # cat port_name # cat node_name HBA 1 WWN: ____________________________________________ HBA 2 WWN: ____________________________________________ 4 Gather host FCIDs. # cat port_id 5 Gather FC port type, and FC topology. # cat port_type 6 Close the telnet session.

(46)

Use the following procedure to gather HBA WWN for this host. Record this information in the Lab

Configuration Diagram at the end of this section.

WINDOWS Host

Step Action

1 Connect to your Windows host.

2 To gather OS version, click Start > Run. Then type the following command: # winver Click OK to close About Windows 3 Open the Emulex OneCommand Manager from Start > All Programs > Emulex > OC Manager. 4 Expand the HBA and note the WWNs. HBA 1 WWN: ____________________________________________ HBA 2 WWN: ____________________________________________ 5 Close OneCommand.

(47)

Use the following procedure to gather the HBA WWNs for this host. Record this information in the Lab Configuration Diagram at the end of this section.

ESXi Host

Step Action 1 From your Windows management host, launch the VMware Infrastructure Client and log into the ESXi server. Note: If the VMware Infrastructure Client is not available, type the IP address of your Pod’s ESX host on a browser, download and install the client.

2 From within the Configuration tab. Click Storage Adapters on the Hardware sub menu and click the difference instances of HBAs. Notice the HBA model and WWN.

HBA 1 WWN: ____________________________________________ HBA 2 WWN: ____________________________________________ 3 Log out of your ESXi host.

(48)

Lab 5: Part 2 – Discover Switch Name Server Information

Use the following procedure to gather information on all the port WWNs that have logged into this switch. Record this information in the Lab Configuration Diagram at the end of this section.

B-SERIES SWITCHES

Step Action 1 Log into Web Tools by typing your Pod’s B‐Series switch IP address from a browser in your Windows management host. 2 Click Name Server from the Monitor section. 3 Right‐click a row in the name‐server table. Then select default >Export Table. 4 Save the name server on your Windows host desktop. Name it: <switch name>_nameserver.txt 5 Close the Name Server window and Log out of Web Tools.

(49)

Use the following procedure to gather information on all the port WWNs that have logged into this switch. Record this information in the Lab Configuration Diagram at the end of this section.

MDS-SERIES SWITCHES

Step Action 1 Open Device Manager from your Pod’s Windows management server and log into your MDS switch. 2 Click FC > Name Server. 3 From the General tab, click the Export to file… icon (Save icon). 4 Save the Name Server data to your desktop. Name it: <switch name>_nameserver.txt 5 Close the Name Server window and Device Manager.

(50)

Lab 5: Part 3 – Decode Storage Port WWN

You need to have a Powerlink account for this lab; if you don’t have one, use the student resource guide to manually decode the Storage Array WWNs. Step Action 1 Log in to E‐Lab Advisor by typing the following address in a web browser. https://elabadvisor.emc.com 2 Log in using your Powerlink Credentials. 3 Click on WWN Tool. 4 Copy the WWN for the storage array ports from your .txt file to the Decoder tool and click Decode. 5 The output should provide the director and port and storage array model; copy this information to your Lab Configuration Diagram found in Lab 5 Part 4.

6 Repeat Steps 4 and 5 for every storage array port that has logged into the name server on either your MDS‐Series or B‐Series switch.

7 Close the browser when finished.

(51)

Lab 5: Part 4 – Create a Map of the Lab Environment

In the last labs you gathered WWN information for the hosts and decoded the storage arrays’ WWNs. Match the information with the name servers for your switches and complete the Lab Configuration Diagram. Draw lines to connect the initiator and target WWN to the port in the switch where it’s connected. Host Name: ______________________ IP Address: ______________________ AIX HBA 2: HBA 1: Host Name: ______________________ IP Address: ______________________ HP‐UX HBA 2: HBA 1: Host Name: ______________________ IP Address: ______________________ Windows HBA 1: HBA 2: Switch Name: ___________ IP Address: ____________ Domain ID: ____________ B‐SERIES Port Number Switch Name: ___________ IP Address: ____________ Domain ID: ____________ MDS‐SERIES Port Number Storage Name:______________________ IP Address: _______________________ Serial Number: _____________________ VNX SP P WWN Storage Name:______________________ IP Address: _______________________ Serial Number: _____________________ DMX / VMAX FA P WWN Host Name: ______________________ IP Address: ______________________ LINUX HBA 2: HBA 1: Host Name: ______________________ IP Address: ______________________ Solaris HBA 1: HBA 2: Host Name: ______________________ IP Address: ______________________ VMware HBA 1: HBA 2:

(52)

(53)

Lab Exercise 6: SAN Management

Purpose: The purpose of this lab is to provide the student with a working knowledge of how to configure and manage virtual SANs as well as how to configure zoning on both B‐Series and MDS‐Series switches. You will use both CLI commands and each vendor’s GUI to perform the tasks in this lab exercise. Tasks: Students perform the following tasks:  B‐Series tasks: o Configure Virtual Fabrics using the CLI o Configure zones using the CLI o Configure zones using Web Tools o Configure zones using Connectrix Manager  MDS‐Series tasks: o Configure a VSAN using CLI o Configure zones using the CLI o Configure zones using DCNM‐SAN References: SAN Management Module

(54)

Lab 6: Part 1 – Configuring Virtual Fabrics Using the B-Series CLI

In this exercise you will use CLI commands to enable the Virtual Fabric feature on your assigned B-Series switch, and then create a logical switch, assign ports to it and verify your work. Step Action 1 From your Management host, telnet to your Pod’s B‐Series switch and login. 2 Verify the number of devices in the existing fabric # fabricshow 3 Enable Virtual Fabrics on the switch # fosconfig –-enable vf 4 Confirm the operation, the switch will reboot 5 Once the switch has rebooted, telnet to it. 6 Notice that the prompt has changed 7 Display the logical switches that are configured. # lscfg --show 8 How many switches are configured? What is special about switch 128? _____________________________________________________________________ 9 Create a new Logical Switch with FID 5 # lscfg --create 5 10 Verify FID 5 was created # lscfg --show 11 Verify port membership for the Default Switch # switchshow

(55)

Step Action 12 Log into logical switch 5. # setcontext 5 13 Turn off the default zoning. # defzone –-noaccess

You are about to set the Default Zone access to No Access Do you want to set the Default Zone access mode to No Access ? (yes, y, no, n):[no] y

14 Save the configuration. # cfgsave

You are about to save the Defined zoning configuration. This action will only save the changes on Defined

configuration.

Any changes made on the Effective configuration will not take effect until it is re-enabled.

Do you want to save Defined zoning configuration only?

(yes, y, no, n): [no] y

15 Move all your Host and Storage ports to the new Logical Switch. # lscfg –-config 5 –p #

This operation requires that the affected ports be disabled.

Would you like to continue [y/n]?:y Note: You can use a dash to modify a range of ports.

16 Verify port membership for the default switch. # fosexec –-fid 128 –cmd “switchshow” What ports are missing?

(56)

Step Action 17 Check the port membership. # lscfg –-show 18 Verify port membership for the new logical switch. # switchshow 19 Enable all your ports in logical switch 5. # portcfgpersistentenable # 20 Verify all ports are now enabled. # switchshow

(57)

Lab 6: Part 2 – B-Series CLI Zoning

In this exercise you will use CLI commands to create, save and enable a zone configuration for a virtual fabric. Step Action 1 If you closed your session, telnet to your B‐Series switch and login. 2 Log into logical switch 5 if you have not done so already. # setcontext 5 3 Verify your hosts and storage devices have logged into this logical fabric by checking the name server entries. # nsshow 4 Zone the Windows host to the VNX ports. Use the following format for the zone name: pod#_<hostname>_<hba####>_<storage array>_<port ####>

zonecreate “<zone name>”, “<HBA WWN>; <Storage Port WWN>”

Note: Make sure to use the right WWN from your Lab Configuration Guide. To avoid mistakes, copy and paste it from the name server database. Remember to follow single initiator zoning. 5 Repeat Step 4 to zone the Windows host HBAs to all the Symmetrix ports in your pod. 6 Verify the new zones. # zoneshow

(58)

Step Action

7 Create a new zone config (zone set) for the switch. Add one of the zones created in Step 4.

Use the following name for the zone config: b_series. # cfgcreate “<config name>”, “<zone name>”

Note: Zone Config Name “b_series” will be required when performing Fabric Configuration Lab

8 Add zones to the zone config.

# cfgadd “<config name>”, “<zone name>”

9 Repeat Step 8 for all the zones created in Step 4.

10 Verify the new config.

# cfgshow <config name>

11 Save the config. # cfgsave

You are about to save the Defined zoning configuration. This action will only save the changes on Defined

configuration.

Any changes made on the Effective configuration will not take effect until it is re-enabled.

Do you want to save Defined zoning configuration only? (yes, y, no, n): [no] y

12 Enable the config created in Step 7. # cfgenable “<config name>”

You are about to enable a new zoning configuration.

This action will replace the old zoning configuration with the current configuration selected. If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes

Do you want to enable 'b_series' configuration (yes, y, no, n): [no] y

(59)

Step Action 13 Verify the configuration is listed as the effective configuration. # cfgshow 14 Verify all the nodes included in the zones are logged in. # zone --validate Note: The zone member should not contain these characters next to them: ~ * # 15 Log off the switch. # exit

(60)

Lab 6: Part 3 – B-Series Web Tools Zoning

In this exercise you will use Web Tools to create, save, and enable a zone configuration for a virtual fabric. Step Action 1 From your management server, log into your Pod’s B‐Series switch by typing its IP Address on a browser. 2 Click Logical Switch drop down and select logical switch 5. 3 Click Zone Admin under the Manage section in the main GUI Window 4 Click the Zone tab on the upper left‐hand bar. 5 Zone the ESX host HBA to the VNX ports. Click New Zone. Use the following format for the zone name: pod#_<hostname>_<hba####>_<storage array>_<port ####> Note: Remember to follow single initiator zoning. 6 From the Member Selection List expand WWNs and select the WWNs which will be added to the newly created zone. Note: The devices shown are represented by their Node WWN. Expand the device which you want to zone and select its Port WWN. 7 Click Add Member. 8 Click the Zone Config tab. 9 Click on the Name drop down and select the zone config created in the last lab exercise (b_series). 10 Expand the Zone folder and select the ESX server zones. 11 Click Add Member.

(61)

Step Action 12 When the zones are in the Zone Config, click Save Config. 13 When prompted for confirmation click Yes. 14 When the commit process is complete, click Enable Config. 15 A window pops up asking you to select a config. Select the recently created config (b_series) from the drop‐down and click OK. 16 When prompted for confirmation, click Yes. 17 Make sure the changes are committed successfully. Close the Zone Administration window and Web Tools.

(62)

Lab 6: Part 4 – B-Series CMCNE Zoning

In this exercise you will use CMCNE to create, save and enable a zone configuration for a virtual fabric. Step Action 1 From your Windows management server, open Connectrix Manager Converged Network Edition (CMCNE) and login. 2 Click the SAN tab. 3 Click Discover > Fabrics. 4 In the Discover Fabrics window, click Add. 5 Set the following parameters in the IP Address tab:  SNMP Configuration: Automatic  Fabric Name: pod#_bseries  IP Address: <b‐series IP Address>  User ID: admin  Password: <switch password> 6 Click OK

7 An “Undiscovered Seed Switch” window pops up. Select your logical switch 5 as your seed switch. Click OK. 8 Click Close to Close the Discover Fabrics window. 9 On the left hand side, expand the fabric to verify the switch is discovered. 10 Click the Zoning icon. 11 Click the Zone DB tab. 12 Expand your switch in the Potential Members area. 13 Click New Zone.

(63)

Step Action 14 We will create zones between your UNIX and Linux hosts and Symmetrix storage. Let's start with the AIX host. Label the zone: pod#_<hostname>_<hba####>_<storage array>_<port ####> 15 Click on your newly created zone. 16 In the Potential Members area, select the WWN corresponding to the host in the zone and click the Add Member icon . 17 Select the WWN corresponding to the Symmetrix array port in the zone and click the Add Member icon . 18 Repeat Steps 14 to 17 until you zone all your Unix and Linux hosts to all the Symmetrix ports. 19 Under Zone Configurations, click on the active config. The active config is identified by the green mark. 20 Select all your new zones and click the Add Zone icon . 21 Click on the active config and then click Activate. 22 Verify the changes and click OK. 23 Click Yes to confirm. 24 Click OK to close the success message. 25 Click OK to close the Zoning window. 26 If prompted, click OK to save the zone database. 27 Close CMCNE.

(64)

Lab 6: Part 5 – Configure MDS-Series VSAN Using CLI

In this exercise you will use CLI commands to create a new VSAN on your assigned MDS-Series switch, and then assign interfaces to it and verify your work.

Step Action 1 From the Windows management host, telnet to your Pod’s MDS‐Series switch. 2 Move to the config menu. # config 3 Move to the VSAN database submenu. # vsan database 4 Create VSAN 5 and name it “Host‐to‐Storage”. # vsan 5 name Host-to-Storage

5 Add all your hosts ports as well as storage ports to VSAN 5. Use your Lab Configuration Diagram for port allocation information.

# vsan 5 interface fc#/#, fc#/#, fc#/#

Traffic on fc#/# may be impacted. Do you want to continue? (y/n) [n] y 6 Move back to exec mode. # end 7 Verify VSAN 5 was created. #show vsan 5 8 Verify the host ports and storage ports were added to VSAN 5. #show vsan 5 membership

(65)

Lab 6: Part 6 – MDS-Series CLI Zoning

In this exercise you will use CLI commands to create zones, add them to a Zoneset and activate the Zoneset for your new VSAN.

Step Action 1 If you closed the telnet session, telnet to your MDS‐Series switch. 2 Check the hosts and storage are logged in the name server. # show fcns database 3 Move to the config menu. # config

4 Zone the Windows and ESXi hosts to all the storage ports (VNX and Symmetrix).

Make a different zone for every initiator. Use the following format for the zone

name:

pod#_<hostname>_<hba####>_<storage array>_<port ####>

# zone name <zonename> vsan 5

5 Add the Windows/ESXi HBA and storage WWN to the zone. # member pwwn <host WWN> # member pwwn <storage WWN> #exit Note: To avoid mistyping, copy the member WWN from the name server output. 6 Repeat Steps 4 and 5 until all the Windows and ESXi HBAs are zoned to all the storage ports. 7 Move back to exec mode. #end 8 Verify the zones.

(66)

Step Action

9 Move to the config menu. # config

10 Create a zone set with the name mds_config. # zoneset name mds_config vsan 5

11 Add a zone you created in steps 4‐6 to the zone set. # member <zone name>

12 Repeat Step 11 for all the zones you created in steps 4‐6.

13 Move to exec mode. # end

14 Verify the zone set is correct before activating it. # show zoneset vsan 5

15 Move to the config menu. # config

16 Activate the zone set.

# zoneset activate name <zone set name> vsan 5 # exit

17 Verify the zone set has been enabled. #show zoneset active vsan 5

18 Logout of your switch.

(67)

Lab 6: Part 7 – MDS-Series DCNM Zoning

Using DCNM edit your full zone database for your VSAN, and add additional zones to it. Then activate the new Zoneset and save all changes.

Step Action

1 From your Windows management host, open Data Center Network Manager

DCNM and select your MDS‐Series switch.

2 In the Logical Domain pane, expand the Fabric.

3 Right‐click Host‐to‐Storage (VSAN 5) and select Edit Local Full Zone Database.

4 From the Edit Local Full Zone Database window, click Zones, then click the insert icon: 5 We will zone all the UNIX and Linux hosts with all the Symmetrix ports. Remember to use single initiator zoning. Start with your first UNIX host. Use the following format for the zone name: pod#_<hostname>_<hba####>_<storage array>_<port ####>. Make sure all the checkboxes are unchecked and click OK. 6 Expand the Zones folder and click on the recently created Zone. Select the host and storage port for the zone and click Add to Zone. 7 Repeat Steps 3 to 5 until all the Unix and Linux hosts are zoned to the Symmetrix.

8 Expand ZoneSets and select the zoneset created in the last lab exercise step 10. (mds_config) then click the insert icon:

9 The Select Zone window pops up. Select all the zones you created and click Add.

10 With the Zoneset selected, click Activate.

11 Click Yes to review the differences and verify the zones you created are included in this report. Click Close when finished.

(68)

Step Action 12 Make sure the Save Running to Startup Configuration checkbox is checked. Click Continue Activation. 13 If prompted for confirmation, click Yes. 14 Verify the activation is successful; close the Edit Local Full Zone Database window. 15 Close DCNM.

(69)

Lab Exercise 7: Volume Access

Purpose: The purpose of this lab is to provide the student with a working knowledge of how to use Unisphere to provision block storage volumes on VNX and VMAX storage arrays for various host operating systems. Tasks: Students perform the following tasks:  Use Unisphere to provision VNX storage volumes for access by Windows, Linux, ESXi, and UNIX hosts.  Use Unisphere for VMAX to provision storage volumes for access by Windows, Linux, ESXi, and UNIX hosts. References: SAN Management Module.

SAN Management - Lab Guide

SAN Management

Lab Guide

Copyright

Document Revision History

Table of Contents

Lab Exercise 1: B-Series Management

Lab 1: Part 1 – B-Series Basic CLI Commands

Lab 1: Part 2 – B-Series Management using Web Tools

Lab 1: Part 3 - Install CMCNE and Discover Fabric

Lab Exercise 2: B‐Series Configuration

Lab 2: Part 1 – B-Series Configuration Using CLI

Lab 2: Part 2 – B-Series Configuration Using Web Tools

Lab Exercise 3: MDS-Series Management

Lab 3: Part 1 – MDS-Series Basic CLI Commands

Lab 3: Part 2 –Install DCNM and Discover Fabric

Lab 3: Part 3 – MDS-Series Management using DCNM-SAN and

Device Manager.

Lab Exercise 4: MDS-Series Configuration

Lab 4: Part 1 – MDS-Series Configuration using CLI

Lab 4: Part 2 – MDS-Series Configuration using DCNM and

Device Manager

Lab Exercise 5: Discover Host and Storage WWN

Lab 5: Part 1 – Locate and Record Initiator WWN’s

AIX Host

HP-UX Host

SOLARIS Host

LINUX Host

WINDOWS Host

ESXi Host

Lab 5: Part 2 – Discover Switch Name Server Information

B-SERIES SWITCHES

MDS-SERIES SWITCHES

Lab 5: Part 3 – Decode Storage Port WWN

Lab 5: Part 4 – Create a Map of the Lab Environment

Lab Exercise 6: SAN Management

Lab 6: Part 1 – Configuring Virtual Fabrics Using the B-Series CLI

Lab 6: Part 2 – B-Series CLI Zoning

Lab 6: Part 3 – B-Series Web Tools Zoning

Lab 6: Part 4 – B-Series CMCNE Zoning

Lab 6: Part 5 – Configure MDS-Series VSAN Using CLI

Lab 6: Part 6 – MDS-Series CLI Zoning

Lab 6: Part 7 – MDS-Series DCNM Zoning

Lab Exercise 7: Volume Access

Note: Prior to beginning this lab exercise, all zoning must be complete and

active/enabled from the previous lab. If your zoning is not complete, finish that

before beginning this lab exercise.