ICSNS

Lab Guide
Overview
Use the exercises here to complete the labs for this course.

Outline
This Lab Guide includes these exercises:
               

Lab Exercise 1: Initial Switch Configuration Lab Exercise 2: Installing Fabric Manager and Device Manager Lab Exercise 3: Exploring Fabric Manager and Device Manager Lab Exercise 4: Configuring VSANs Lab Exercise 5: Configuring PortChannels Lab Exercise 6: Configuring Interfaces Lab Exercise 7: Configuring Zones Lab Exercise 8: IVR Lab Exercise 9: FCIP Basic Configuration Lab Exercise 10: FCIP Performance Tuning Lab Exercise 11: Cisco Fabric Services Lab Exercise 12: FC Analyzer Lab Exercise 13: Using the Port Analyzer Adapter and SPAN Lab Exercise 14: Performing Software Upgrades Lab Exercise 15: Challenge Lab SAN-OS 3.2 Addendum

Intro-2

Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

Lab Exercise 1: Initial Switch Configuration
Exercise Objective
In this exercise, you will configure MDS 9000 switches for out-of-band management and explore the MDS command-line interface (CLI). After completing this exercise, you will be able to meet these objectives:
      

Clear the current startup configuration and reboot the switch Start the interactive setup process on an MDS 9000 switch Configure an MDS 9000 switch for out-of-band management Navigate through the switch CLI structure Use command completion and help Save the running configuration Save the switch configuration to a TFTP server

Visual Objective
Figure 1 illustrates what you will accomplish in this exercise.

Figure 1. MDS Switches and TFTP Server

You will configure the out-of-band (OOB) mgmt0 Ethernet interfaces on your assigned MDS switch, and save and restore your configuration from a TFTP server.

Required Resources
These are the resources and equipment required to complete this exercise:
 

Two MDS 9000 Fibre Channel switches Access to TFTP server

Command List
A summary of CLI commands used in this exercise is described in the table here.
Command Description Erases the switch’s startup configuration Reboots the switch Displays all the permissible features for the show command for the current user Shows the running configation Displays an interface status summary Displays VSAN configuration and status Displays current code version Verifies that the system is ready to accept a supervisor switchover. Displays environment-related switch information, such as fan, power, and temperature status Enters configuration mode Executes an EXEC-mode command from config mode Enters configuration submode for FC port 3 on module 1 Exits one level in the menu structure. If you are in EXEC mode this command will log you off the system. Exits configuration mode to EXEC mode Disables an interface Enables an interface Saves the running configuration as the startup configuration Saves the running configuration to a TFTP server Displays the contents of the specified memory area Displays the contents of the specified file Deletes the specified file

write erase reload show ? show running-config show interface brief show vsan show version show system redundancy status show environment config term do command interface fc1/5 exit end shut no shut copy running-config startup-config copy running-config tftp://ip_address/path dir [volatile: | bootflash:] show file name del name

1-2

Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

One team will configure Px-MDS1 and the other team will configure Px-MDS2. Lab Guide 1-3 . Copyright © 2008. Note: You will be working in teams.Overview You will perform the initial configuration of MDS 9000 switches to enable out-of-band access and management. Skyline ATS. Inc.

re-connect and observe the console messages as the switch reboots. Enter and confirm 1234qwer (your keystrokes will not be echoed to the screen). as your switch has been previously configured. you will complete the initial configuration of the MDS 9000 switch for out-of-band management. it will prompt you for the administrator password. 1-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Note: At this point. Inc.Task 1: Initial Switch Configuration In this task. Step 4 After the switch reboots. but the startup configuration file will be missing. Answer the questions below according to the following example. . Switch login: admin Password: 1234qwer Step 2 On a new. Note: The ‘write erase’ command is a potentially dangerous command to run on a switch as it clears the startup configuration from persistent. you may be disconnected from the console. Do you wish to proceed anyway? [y/n] [n] Type y to proceed. Exercise Procedure Complete the following steps: Step 1 Access and login to the console of your assigned MDS 9000 switch.2 Copyright © 2008. The prompt you see will probably be for the form Px-MDS#. To simulate a fresh install you will clear the current startup configuration and reboot the switch as follows: switch# write erase The following message is displayed: Warning: This command will erase the startup-configuration. out of the box switch you will see a default switch prompt (switch#) indicating that the device has probably not been configured. Substitute numeric values for X and Y as provided by your instructor. If so. Skyline ATS. ---. The SAN-OS operating system should load automatically. memory (NVRAM). (y/n)? Type y to proceed.System Admin Account Setup ---Enter the password for “admin”: 1234qwer Confirm the password for “admin”: 1234qwer Read the message that is on the screen and then enter y to continue. Step 3 Reboot the switch as follows: switch# reload This command will reboot the system. or non-volatile.

Press Enter in case you want to skip any dialog.X. you can simply press Enter to accept the default response. Lab Guide 1-5 . MDS devices must be registered to receive entitled support services. Setup configures only enough connectivity for management of the system.0.Basic System Configuration Dialog --This setup utility will guide you through the basic configuration of the system. or 3 for the Px-MDS2) 255.255. Would you like to enter the basic configuration dialog (yes/no): Create another login account (yes/no) [n]: <enter> Configure read-only SNMP community string (yes/no) [n]: <enter> Configure read-write SNMP community string (yes/no) [n]: <enter> Enter the switch name: Px-MDS1 or Px-MDS2 (where X is your pod number) Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: <Enter> Mgmt0 IPv4 address: Mgmt0 IPv4 netmask : 10. Skyline ATS. Y is either 5 for the Px- MDS1.255. Use ctrl-c at anytime to skip away remaining dialogs. --.0 <Enter> Configure the default gateway? (yes/no) [y]: IPv4 address of the default gateway : number) 10.Note: Whenever you see the appropriate response in brackets [].Y y (X is your pod number. Failure to register may affect response times for initial service calls. Inc.254 (X is your pod Configure advanced IP options? (yes/no) [n] : <Enter> Enable the telnet service? (yes/no) [y]: Enable the ssh service? (yes/no) [n]: Configure clock? (yes/no) [n]: <Enter> Configure timezone? (yes/no) [n]: <Enter> Configure summertime? (yes/no) [n]: <Enter> Configure the ntp server? (yes/no) [n]: <Enter> <Enter> <Enter> Configure default switchport interface state (shut/noshut) [shut]: <Enter> Configure default switchport trunk mode (on/off/auto) [on]: <Enter> Configure default switchport port mode F? (yes/no) [n]: <Enter> Configure default zone policy (permit/deny) [deny]: Enable full zoneset distribution (yes/no) [n]: <Enter> <Enter> Configure default zone mode (basic/enhanced) [basic]: <Enter> Copyright © 2008.0. Please register Cisco 9000 Family devices promptly with your supplier.X.

. press Enter: The following configuration will be applied: switchname P4-MDS1 interface mgmt0 ip address 10.0.255. Skyline ATS.255.2 Copyright © 2008.0. press Enter to save the configuration to NVRAM: <Enter> Use this configuration and save it? (yes/no) [y]: Step 7 After the configuration is saved.4.4. Inc. press <Enter>: Did the switch prompt change to the name you configured? ___________ The switch prompt should now be of the form: MDS Switch P4-MDS1 login: • • 1-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3.254 telnet server enable no ssh server enable system default switchport shutdown system default switchport trunk mode on no system default zone default-zone permit no system default zone distribute full no system default zone mode enhanced Would you like to edit the configuration? (yes/no) [n]: <Enter> Step 6 Finally.5 255. If everything looks good.Step 5 At this point a summary of the configuration will be displayed.0 no shutdown ip default-gateway 10.

and show as follows: # s? # sh? # show ? Note: Notice that the first two commands have no space after the <?>. use them often. This will place you in what is known as EXEC Mode.  Note:Depending on the version of Java running on your local host the <tab> key may or may not work properly. type sh<tab> ru<tab> . a GBIC. <Space> to see the next screen. Exercise Procedure Complete these steps on one of the MDS 9000 switches in your pod: Step 1 Step 2 Login to your switch console using the login name admin and password 1234qwer that you configured in Task 1. sh.e. Copyright © 2008.prompt. Inc. Note also that <?> does not terminate the command line.Task 2: Exploring the MDS 9000 CLI and setting the clock In this task. or <q> to quit and return to the switch prompt. press <Enter> to see the next line.. i. then press the <tab> key to complete each word. Lab Guide 1-7 . Step 5 Display current running configuration that is stored in RAM: # show running-config Note: Abbreviate the syntax. it will work from a telnet or ssh connection. for example. Even if the <tab> key does not work from a console connection. after help is displayed you are returned to where you were. At the EXEC Mode prompt. Step 6 Display a brief status of the switch interfaces: # show interface brief (abbr: sh int br) • What is the status of the FC interfaces? _______________ Note: Sfp stands for Small Form Factor Pluggable. you will briefly explore the MDS 9000 command-line interface (CLI). Skyline ATS. The <tab> and <?> keys are your friends. type <?> to view commands available in the current mode: # ? Step 3 Step 4 At the --More-. Display all commands that begin with s. After this lab almost all CLI commands will be executed from a telnet or ssh connection so plan on using the <tab> feature in subsequent labs.

Step 7 Display VSAN information: # show vsan Record the following information: VSAN Name State Operational State Note: VSAN 4094 (the Isolated VSAN) will be discussed at length later in the course.254 (X is your pod #. simply note that both VSAN 1 and VSAN 4094 exist without any explicit configuration. Step 8 Display the installed version of SAN-OS by examining the kickstart and system variables in the output of the following command: # show version Step 9 Ping your default-gateway: # ping 10.2 Copyright © 2008.) Does the gateway respond? ___________ Step 10 Step 11 Press Ctrl-C to abort the ping command. Inc. Enter Configuration Mode as follows (observe the change in the prompt string): # config terminal (abbr: conf <Enter>) Step 12 Attempt to invoke the show version command. you can invoke EXEC Mode commands by preceding the command with “do”: (config)# do show version Step 15 Enter configuration mode for Fibre Channel port 5 on module 1. Here. Observe the change in the command prompt: (config)# interface fc1/5 (config-if)# Step 16 Type <?> to observe the commands available in the Interface Configuration SubMode: (config-if)# ? Step 17 Type <exit> to go back up one level and return to Config Mode: (config-if)# exit (config)# 1-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0. Also note that VSAN 4094 does not have a State or an Operational State. Skyline ATS. Do you see the show command? ____________ Step 14 While in Configuration Mode. Are you successful? _________ (config)# show version Step 13 Type a question mark to view commands available in Configuration Mode. .X.

Inc. Skyline ATS.Step 18 Type <end> or <Ctrl-Z> to back out all the way to EXEC mode: (config)# end (or type Ctrl-Z) Copyright © 2008. Lab Guide 1-9 .

you will set the system clock.Task 3: Setting the System Clock In this task. and daylight savings time from the CLI. Skyline ATS. timezone. In the U. the daylight saving time adjustment occurs on the second Sunday in March and ends on the first Sunday in November. For example: (config)# do clock set 16:48:00 2 February 2008 Sat Feb 2 16:48:00 PST 2008 Step 4 Enable the daylight saving time clock adjustment. . You can update the configuration of your switch to accommodate this change using the following command: (config)# clock summer-time PST 2 Sunday March 02:00 1 Sunday November 02:00 60 1-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Exercise Procedure Complete these steps on your assigned MDS 9000 switches: Step 1 From EXEC mode set the system clock: # clock set 16:40:00 2 February 2008 Sat Feb 2 16:40:00 UTC 2008 Step 2 From CONFIG mode set the timezone: # config terminal (config)# clock timezone PST -8 0 # do show clock Sat Feb 2 08:47:32 PST 2008 Step 3 Reset the clock to the current time.S. Inc.2 Copyright © 2008.

168.3 ms --.168. Lab Guide 1-11 . # copy tftp://192.0.0.10.198/podX/<fname. If the ping is not successful. MDS1# ping 192.198: icmp_seq=0 ttl=255 time=0. you will save and restore switch configurations.3/0. remember to abbreviate commands and/or use the <tab> key for command completion.3 m Note: Ping will continue until you abort it with Ctrl-C.cfg Note: Volatile is a RAM file system that is used as a temporary scratch area.0.198 PING 192.0. Step 7 The basic syntax of the copy command is “copy <source> <destination>”.0. 0% packet loss round-trip min/avg/max = 0. verify that your MDS 9000 has its mgmt0 interface and defaultgateway configured properly for your switch).198/podX/fname. where <source> and <destination> can be a number of locations. Skyline ATS.198: icmp_seq=1 ttl=255 time=0. Anything left in here will be lost when a switch reboots.198 (192.3/0.168. as well as remote file servers.cfg volatile:fname.168.2 ping statistics --2 packets transmitted.cfg> Note: To make your life easier. 2 packets received.168. Exercise Procedure Complete these steps on one of the MDS 9000 switches: Step 5 Copy your running configuration in RAM to the startup configuration in NVRAM: # copy running-config startup-config (abbr: copy run start) Step 6 Ping the TFTP server from your MDS switch console.Task 4: Saving the Switch Configuration In this task.0.168. Step 10 Copy the configuration you just saved back to the switch volatile file system.0. Inc.66.198): 56 data bytes 64 bytes from 192. investigate why and fix the problem (for example.3 ms 64 bytes from 192.0.168. Enter the following to determine valid copy source locations: # copy ? Step 8 Enter the following to determine valid copy destination locations: # copy run ? Step 9 Save your running configuration to the TFTP server as follows (where the IP address is the IP address of your TFTP server and fname is a unique filename that you will remember later): # copy running-config tftp://192. Copyright © 2008. including the running and startup configuration files.

Skyline ATS.2 Copyright © 2008. Step 13 Delete the file you just copied. # dir volatile: Step 12 Examine the contents of your configuration file: # show file volatile:fname.cfg Press q to terminate the display.cfg # dir volatile: Step 14 End your CLI session and log off: # exit That completes this lab exercise. . 1-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 11 Examine the contents of the volatile file system. Inc. and then confirm the result: # del volatile:fname.

Inc. P1-MDS1# show running-config version 3.1.254 switchname P1-MDS1 role name default-role description This is a system defined role and applies to all users rule 1 permit show feature system rule 2 permit show feature snmp rule 3 permit show feature module rule 4 permit show feature hardware rule 5 permit show feature environment username admin password 5 $1$8KaB5X5W$vZ3Ti5PuQxu7z2vs2ZUZ51 role network-admin boot kickstart bootflash:/9100-kickstart-3.0.2 boot system bootflash:/9100-system-3.0 kernel core limit 1 Copyright © 2008.2 kernel core target 0.Appendix A – Sample Lab Configuration File The following is a complete sample configuration file taken from P1-MDS1 in Pod 1.0.0(2) fcdomain fcid database vsan 1 wwn 21:00:00:e0:8b:03:d1:24 vsan 1 wwn 21:00:00:e0:8b:03:c3:24 vsan 1 wwn 20:09:00:0d:ec:06:4a:00 vsan 1 wwn 21:01:00:e0:8b:23:c3:24 vsan 1 wwn 21:01:00:e0:8b:23:d1:24 vsan 1 wwn 20:06:00:0d:ec:06:4a:00 clock timezone PST -8 0 clock summer-time PST 2 Sunday March interface fc1/1 interface fc1/2 interface fc1/3 interface fc1/4 interface fc1/5 interface fc1/6 interface fc1/7 interface fc1/8 interface fc1/9 interface fc1/10 interface fc1/11 interface fc1/12 interface fc1/13 interface fc1/14 interface fc1/15 interface fc1/16 interface fc1/17 interface fc1/18 interface fc1/19 interface fc1/20 fcid fcid fcid fcid fcid fcid 0x110000 0x110100 0x110300 0x110400 0x110500 0x110600 area area area area area area dynamic dynamic dynamic dynamic dynamic dynamic 02:00 1 Sunday November 02:00 60 tlport alpa-cache interface fc1/9 pwwn 21:00:00:e0:8b:03:c3:24 alpa 0x4 tlport alpa-cache interface fc1/9 pwwn 21:01:00:e0:8b:23:c3:24 alpa 0x1 tlport alpa-cache interface fc1/9 pwwn 21:01:00:e0:8b:23:d1:24 alpa 0x2 ip default-gateway 10.0.0. Skyline ATS. Lab Guide 1-13 .0.

Skyline ATS.snmp-server user admin network-admin auth md5 0x61d966bf0a20e07c3356e1c1817b0ce2 priv 0x61d966bf0a20e07c3356e1c1817b0ce2 localizedkey no snmp-server enable traps vrrp snmp-server enable traps license callhome interface fc1/1 interface fc1/2 interface fc1/3 interface fc1/4 interface fc1/5 interface fc1/6 interface fc1/7 interface fc1/8 interface fc1/9 interface fc1/10 interface fc1/11 interface fc1/12 interface fc1/13 interface fc1/14 interface fc1/15 interface fc1/16 interface fc1/17 interface fc1/18 interface fc1/19 interface fc1/20 interface mgmt0 switchport speed 100 ip address 10.255. Inc.0. .255.4.5 255.0 1-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008.

Appendix A provides instructions on how to download. and configure the Java Runtime Environment (JRE) and Java Web Start Visual Objective The figure illustrates what you will accomplish in this exercise. but for purposes of this lab the focus will continue to be on the out-of-band Ethernet network as illustrated above. After completing this exercise. install.Lab Exercise 2: Installing and Configuring the Fabric Manager and Device Manager Exercise Objective In this exercise. you will install and configure the Cisco MDS Fabric Manager (FM) and Device Manager (DM) applications. . Note: Subsequent lab exercises will focus on the Fibre Channel network. you will be able to meet these objectives:   Uninstall Cisco Fabric Manager and Device Manager Install Cisco Fabric Manager and Cisco Device Manager Additionally. You will install Fabric Manager and Device Manager on one of the Windows 2000 servers in your pod.

3. 2. Fabric Manager. The MDS 9000’s built-in web server presents the Fabric Manager & Device Manager installation page to the host.Required Resources These are the resources and equipment required to complete this exercise:   2 MDS 9000 Fibre Channel switches 2 Windows 2000 hosts with Java Runtime Environment (JRE) and Java Web Start installed Overview Before you can install the Cisco Fabric Manager or Device Manager. After Java is installed. the installation process for the Java components is outlined in the Appendix of this lab. the host must have the Java Runtime Environment (JRE) and Java Web Start installed. 2-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. you can reconnect to your MDS 9000 switch and install Fabric Manager Server. Skyline ATS. Selecting the link will connect to java. a warning message will appear with a Java Runtime Environment link. However. In this lab we will use Internet Explorer. 4.2 Copyright © 2008. the Java components are already installed. In the lab. Inc.sun. If your system does not have the correct version of Java Runtime Environment (JRE) installed.com to download JRE where you can then launch the installation executable that will install both Java Runtime Environment and Java Web Start. You do not need to reinstall the Java components. and Device Manager. . A user opens a web browser on the host and browses to the IP address of the MDS 9000 in that pod. The Windows 2000 installation process is as follows: 1.

Inc. use W2K2 if you have been assigned to MDS2. Skyline ATS. Lab Guide 2-3 . (Use W2K1 if you have been assigned to MDS1. Copyright © 2008.) Step 2 Click on the Microsoft Windows Remote Desktop Web Connection “Connect” button. Note.Task 1: Uninstalling Fabric Manager and Device Manager Step 1 Click your W2K server on the lab topology map. the server field should be left blank.

. proceed to the next task. From your Windows desktop. Skyline ATS. Inc. click Start | Programs | Cisco MDS9000 | Uninstall. Step 5 When prompted enter “a” to delete all files: 2-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 3 Log in to your W2K system. User name: administrator Password: Alexandra Step 4 Uninstall Fabric Manager and Device Manager: Launch the uninstall batch file.2 Copyright © 2008. Note: If this menu option is not available.

Lab Guide 2-5 . Skyline ATS. Inc.Step 6 When prompted enter “y” to remove PostgreSQL: Copyright © 2008.

htm document” 2-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Inc. Step 2 Double click the install_windows. Exercise Procedure Complete these steps: Step 1 Open the MDS9000-CD folder on your desktop. If you are working in teams.2 Copyright © 2008.Task 2: Installing Fabric Manager and Device Manager In this task. the team configuring Px-MDS1 will use W2K-Server-1 and the team configuring PxMDS2 will use W2K-Server-2. you will install Fabric Manager and Device Manager on one of the W2K servers in your pod. . Skyline ATS. Note: If you are working alone in your pod. you may use either W2K server.

Skyline ATS. Lab Guide 2-7 . Step 4 Click on the “Installing Fabric Manger” link: Copyright © 2008.Step 3 As shown below. Inc. click on the “here” link to go directly to the Fabric Manager installation page.

2-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Inc. Skyline ATS. .2 Copyright © 2008.Step 5 Read the notes regarding installing Fabric Manager. Click the “FM Installer” link: Step 6 Click “Yes” to allow ActiveX control on the page: Step 7 Wait while the management software loads.

2(3) window appears. Lab Guide 2-9 . click Next: Copyright © 2008.Step 8 When the Cisco Fabric Manager Installer 3. Skyline ATS. Inc.

accept the terms of the license agreement and click Next: 2-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. consulting with corporate attorneys. Inc.2 Copyright © 2008. and crossing your fingers. Skyline ATS.Step 9 After carefully reading the license agreement. .

Inc. Skyline ATS. Lab Guide 2-11 . Click Next: Copyright © 2008.Step 10 Ensure that Fabric Manager Standalone is selected and accept the default installation folder.

Step 11 Select Install PostgreSQL. Inc.2 Copyright © 2008. Skyline ATS. then enter and confirm the database password 1234qwer and click Next: 2-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. .

Then click Next. Copyright © 2008. Lab Guide 2-13 . Inc.Step 12 Enter and confirm 1234qwer as the Fabric Manager Server password. Skyline ATS.

Click Next.Step 13 Accept Local authentication mode. .2 Copyright © 2008. Inc. 2-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS.

Step 14 Ensure both check boxes shown below are unchecked and click Install. Copyright © 2008. Inc. Skyline ATS. Lab Guide 2-15 .

Click Finish to launch the Fabric Manager. .Step 15 After a few minutes the Fabric Manager installation will complete. 2-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Step 16 Enter the password 1234qwer in the FM Server Password field and click the Login button.2 Copyright © 2008. Skyline ATS. Inc.

X. Lab Guide 2-17 . Skyline ATS.0. Inc. If you are working on MDS1 the management port IP address is 10. X is your pod number.3.X.5. Copyright © 2008. If you are working on MDS2 the management port IP address is 10. Step 18 Select your switch and click Open.Step 17 Enter the IP address of the management port (mgmt0) of your assigned MDS switch.0. enter the switch password (1234qwer) and click the Discover button.

Step 19 At this point you should see a single-switch fabric topology. . Step 20 Double click your switch icon in the Fabric Manager topology map. Optionally. you have successfully installed Fabric Manager and Device Manager. Inc. This should launch Device Manager. Skyline ATS. The warning suggests that the switch is functioning but that there may be an issue requiring administrator intervention.2 Copyright © 2008. similar to the following: Note: You may see a Module Warning and an orange dashed X over your switch icon as shown above. or double-click the Device Manager shortcut icon on the Windows Desktop. In this case we will see that the warning is being caused because one of the switch power supplies is not in service. you can right-click the switch icon and select Device Manager. 2-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3. If you see the device manager graphic.

To verify select Physical -> Power Supplies. Note: In this case the power supply is not plugged in. Copyright © 2008. That concludes this lab exercise. Lab Guide 2-19 . It appears that Power Supply 2 is not currently receiving power.Step 21 The red thunderbolt in the lower left hand corner suggests a non-functional power supply. but please do not enable any interface at this time. Inc. Skyline ATS. Note: Feel free to explore Device Manager.

Double-click the install_windows. Skyline ATS. Step 1 Step 2 Locate and open the MDS9000-CD folder on your desktop.2 Copyright © 2008.5: 2-20 Implementing Cisco Storage Networking Solutions (ICSNS) v3.htm icon: Step 3 Hover your mouse cursor over Install Management Software and click on Java Runtime Environment 1. . Inc.Appendix A: Installing the JRE and Java Web Start Note: This section is for reference only since Java is already installed on the lab hosts. This appendix outlines the steps to install JRE and Java Web Start on a Windows 2000 system. Before you can run Fabric Manager or Device Manager.5 and Java Web Start installed. your system must have the Java Runtime Environment (JRE) 1.

Step 4 Click on the link JRE 1. Inc. Lab Guide 2-21 .5 for Windows: Step 5 When the File Download window appears click on Open: Copyright © 2008. Skyline ATS.

Inc. . This completes this lab. Skyline ATS.2 Copyright © 2008. You are now ready to install and run Fabric Manager. 2-22 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 6 Accept the Typical setup choice: Step 7 Select Save this program to disk and click OK.

This exercise is intended to help you become familiar with the graphical user interfaces of these applications. You will begin with a single-switch fabric and add your pod’s second switch as you and other pod administrators bring up ISLs between your two switches. After completing this exercise. you will be able to meet these objectives:   Navigate within the Fabric Manager and Device Manager interfaces Describe the basic capabilities of Fabric Manager and Device Manager Visual Objective The figure illustrates the topology that you will explore in this exercise. Required Resources These are the resources and equipment required to complete this exercise:   2 MDS 9000 Fibre Channel edge switches 2 Windows 2000 hosts with Java Runtime Environment (JRE) and Java Web Start installed . you will explore some basic features of Fabric Manager and Device Manager.Lab Exercise 3: Exploring Fabric Manager and Device Manager Exercise Objective In this exercise.

double-click the Cisco Fabric Manager SA shortcut icon on the Windows Desktop. Step 2 Select your fabric.3) and the Auth Password 1234qwer. Inc.Task 1: Enabling Interfaces Using FM and DM In this task you will launch Fabric Manager and use the GUI to enable FC interfaces. Enter the IP address of your MDS switch (10.5 or 10. . 3-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. Skyline ATS.0.X.X. and click Open.0. Exercise Procedure Complete these steps: Step 1 If the Fabric Manager is not already open. Click Open.

Lab Guide 3-3 . in Pod 4. Skyline ATS. Copyright © 2008. open the Switches folder and then the Interfaces folder and select FC Physical. For example.Step 3 At this point you should see a one-switch fabric in the topology map. P4-MDS1 should appear as follows: Step 4 In the Physical Attributes pane. Inc.

Step 5 In order to see your interfaces more clearly. The current labs are based on SAN-OS 3. Skyline ATS. What is the operational status of your interfaces? ___________ What is the FailureCause? __________________ Step 7 Note: FM and DM screens and menu options may change slightly from release to release. Inc. Select up to enable the interface. Click in the Admin field under the Status column. Step 6 See if you can grab the bar between the two windows and drag it upward and downward (this may be a bit tricky in the lab due to the emulation environment we are using). 3-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. locate the solid black triangle pointing downward and click it to temporarily hide the topology map window. Locate the Interfaces “Status Oper” column. This column refers to the operational status. . Now locate the corresponding black triangle pointing upward to restore the map view.2 Copyright © 2008.2.3 Step 8 Locate the row for your first ISL (int FC1/1).

The button below it is the Refresh Map button. click the Apply Changes button. Step 11 Observe the fabric topology map view. If your pod’s second switch does no appear select File -> Fabric Rediscover and wait for a minute. Note: Do not continue until the administrator of the other Cisco MDS switch in your pod has successfully brought up the ISL. Copyright © 2008. Together they can be useful in rearranging and cleaning up the display. Inc. Lab Guide 3-5 . Step 10 Return to the topology map window and click the Layout Map button.Step 9 Above the table. Do not proceed until both switches are visible in the Fabric Manager topology pane. Skyline ATS.

Skyline ATS. Inc. Step 12 Locate your switch in the topology map and double-click it to invoke Device Manager.Note: The view you see may be quite different than the one shown above. click on the Fabric Rediscovery button in the top left corner of the Fabric Manger window. Do not continue until interface fc1/1 is up on both switches in your pod and both switches appear in the topology map. . Step 13 Close Device Manager. If you believe ports fc1/1 is up on both of your pod switches. 3-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Please be sure it is the switch assigned to you.2 Copyright © 2008. but you do not see both switches in the topology map. Note: Please do not bring up other interfaces at this time. it will vary depending upon how far along your fellow pod administrators are in configuring their interface.

You are encouraged to explore beyond the features shown here if time permits. Inc. Task 3: Exploring the Fabric Manager Tree View In this task you will explore the Fabric Manager tree view. you might want to adjust the positions of the icons to clean up the display. Step 4 With your left mouse button. Fabric Manager automatically rearranges map when you click on the Layout Map button in the icon column to the left of the fabric map. when the topology changes. Skyline ATS. Step 2 Step 3 Experiment with the other buttons in the icon column. click and hold an object and drag it to a new position. Exercise Procedure Complete these steps: Copyright © 2008. and experiment with various features of Fabric Manager. Lab Guide 3-7 . then release. and experiment with various features of Fabric Manager. Hover your cursor over your MDS switch and observe the call-out that identifies the object. You are encouraged to explore beyond the few features we show here if time permits. Exercise Procedure Complete these steps: Step 1 Sometimes.Task 2: Exploring the Fabric Manager Map View In this task you will view your pod’s fabric in the Fabric Manager map view.

Click it again to sort the list in ascending order. Drag the margin to the right to expand the tree view.Step 1 With your left mouse button. Locate your switch. Skyline ATS.2 Copyright © 2008. Step 2 Click the VSAN0001 folder in the Logical Domains pane and observe the updated table above the Fabric map. and Storage tabs to view the information displayed. Note the Domain Id and Status Step 3 Click on the ISLs. click and hold the margin between the icon column and the Fabric tree on the left. 3-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Click the Name column to sort the list of switches in descending order. Hosts. Inc. .

Step 4 In the Physical Attributes pane. Copyright © 2008. versions. Temperature Sensors. and Power Supplies. serial numbers. sort by the Switch column and locate your pod’s switch. Skyline ATS. Click on the Switch column header to sort by switch name and locate your switch. Observe the table containing Inventory information for all the switches in the fabric. Note the components. In each table. Inc. etc. Lab Guide 3-9 . listed Step 5 Select the other tabs to view Card Module Status. open the Switches folder and click Hardware. modules.

Task 4: Exploring Device Manager In this task you will launch Device Manager from Fabric Manager and explore the Device Manager interface. Inc.2 Copyright © 2008. Exercise Procedure Complete these steps: Step 1 Step 2 Locate your switch in the Fabric Manager topology map window. Note: You can also double-click a switch icon to invoke DM. Step 4 Note the SAN-OS firmware version displayed in the upper right. mouse over a green LED and observe the status message. Step 3 In our classroom environment many of our switches only have a single power supply connected to a power source. Skyline ATS. . 3-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. If your switch does not display a red LED for the power supply. Right-click your switch and select Device Manager. You should see a status message indicating the second power supply is offline. Mouse over the red lightening bolt in the lower left. In such cases the one of the power LEDs will be red.

Copyright © 2008.Step 5 Click the black triangle in the lower right corner to display a port status legend. Lab Guide 3-11 . Step 6 You should see that ISL port is enabled as a TE ports. Inc. Double-click the port. Skyline ATS.

Click the Apply button at the bottom of the window. Inc. Step 11 Close the Inventory window. display the current interface status for your ISL port. # show interface fc1/1 Was the port description updated? ___________ Step 10 Select Inventory from the Physical menu item.2 Copyright © 2008. however this time it is for a single device. .Step 7 In the Description field. Login with the username admin and the password 1234qwer. and then click Close. Step 8 Step 9 Select Command Line Interface from the Device Manager Device menu. 3-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. type: Link to Px-MDSX (the name of the other switch in your pod). From your console command prompt. Skyline ATS. Note that the same information is displayed here as in Fabric Manager.

Notice how the subnet mask specified Step 13 Select the CDP Neighbors tab. Click Close. Inc. Lab Guide 3-13 .Step 12 Double-click the Mgmt interface to display settings for the mgmt0 interface. Copyright © 2008. our mgmt0 interface is attached to port 3/11 of a Catalyst 6503 in VLAN 101. In the example shown here. Skyline ATS. Click on the IP Address(es) button.

Is your local switch also the Principal switch? ___________ Step 17 Step 18 Close the Domain Manager window. Skyline ATS. Inc. Select the Domain Manager from the FC menu. Select the FC | Advanced | FSPF menu item. Step 15 Step 16 Close the VSAN window.Step 14 Select VSANs from the FC menu. Click the Membership tab. Note your Domain ID.2 Copyright © 2008. Verify that all ports are in the default VSAN number 1. . 3-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3. What is the default FSPF link Cost for fc1/1? ___________ Step 19 Close the FSPF window. Click on the Interfaces tab.

Step 22 Return to Fabric Manager.Step 20 Select the Summary tab in Device Manager. Make note of the default polling interval. Lab Guide 3-15 . Locate your switch in the topology map and doubleclick it to invoke Device Manager again. How much Flash memory is utilized? Step 21 Close Device Manager. Inc. Skyline ATS. Click No in the Save Configuration window. Copyright © 2008. How low can the interval be set? Note the % CPU and Memory utilization.

Step 24 Close the interface configuration window and minimize Device Manager. Still. 3-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3. . Inc. Skyline ATS.2 Copyright © 2008. changes made to the running-config will not be lost. By not saving your changes when closing Device Manager. did you lose the port Description you configured earlier? Note: Unless and until you reload the switch.Step 23 Right-click your ISL port (fc 1/1) and select Configure. it is always a good practice to copy the running config to the startup config after making modifications.

Lab Guide 3-17 . Note: If you are working alone in a pod. This interface will create an EISL link between your two switches. Step 4 Close Fabric Manager. Right-click and select Enable your second ISL port (fc1/2). Ensure that all other ports are disabled. you may proceed at this time. Skyline ATS. Note: If you see a Red X over port 2 as shown above. Inc. Step 1 Step 2 Open Device Manager for your switch. it probably means that the other switch in your pod has not yet enabled this port (you are not “seeing light” on the port). Step 3 Wait until both switches in your pod display a green box surrounding the label TE for both ISL ports. you must wait until both teams are ready to proceed. If two teams are sharing the pod.Task 5: Performing a Fabric Configuration Analysis In this task you will use Fabric Manager to purposely configure an interface parameter incorrectly and then use the Fabric Configuration Analysis tool to identify and resolve the resulting inconsistency. Click the Refresh Display button. Copyright © 2008.

Expand the Switches folder. . Skyline ATS. At this point you should see a simple two-switch fabric topology map similar to the following. the default Dead interval is 80 seconds. 3-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Notice that the default FSPF Hello interval is 20 seconds. Inc. then expand the Interfaces folder and click FC Physical. and the State is full.Step 5 Open Fabric Manager. taken from Pod 1: Step 6 Select the Physical Attributes tab in the tree view. Step 7 Click the FSPF tab.2 Copyright © 2008.

change the Dead interval for both your switch entries to 85. If you’re working on the Px-MDS2. If you’re working alone in your pod change all four. Lab Guide 3-19 . click Fabric Configuration Analysis.Step 8 If you’re working on the Px-MDS1. Inc. Click the Apply Changes button. Copyright © 2008. Step 11 Wait a few moments to see the inconsistencies appear. Skyline ATS. Step 9 From the Fabric Manager icon toolbar. Step 10 Select your switch from the Policy Switch from the pull-down menu. change the Hello interval for both your switch entries to 25. Click Compare.

Inc.2 Copyright © 2008. Skyline ATS. . Step 13 Click Yes to the question below. Click OK. and then click Resolve Issues. first select the Resolve box for each inconsistency on your switch. 3-20 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Click Close.Step 12 To view the recommended resolution. Step 14 The Fabric Checker Resolution Details window appears with recommended changes to resolve the issue.

Note: It may take a moment for the State to return to full. Lab Guide 3-21 . Inc. Step 16 Close Fabric Manager. Click No to the save configuration changes prompt. Feel free to explore more on your own with FM and DM. but please do not bring up other interfaces at this time.Step 15 Click the Refresh Values button in the FSPF window. Copyright © 2008. Verify that the Hello and Dead intervals for your switch are reset to their default values. That concludes this lab exercise. Skyline ATS.

Inc.2 Copyright © 2008. .3-22 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS.

Lab Exercise 4: Configuring VSANs Exercise Objective In this exercise. confirm the ports are up and operational. you will configure multiple VSANs on your switches. you will be able to meet these objectives:      Configure VSANs Verify the operational state of VSANs Implement redundant fabrics using VSANs Configure static Domain IDs for VSANs Configure the Principal switch within a VSAN Visual Objective Figure 1 illustrates the topology that you will implement in this exercise. VSAN Configuration . After completing this exercise. and change some per-VSAN parameters. Figure 1. add Fibre Channel ports to the VSANs.

Many SAN administrators still prefer to set static domain ID’s. These will be implemented using VSANs. In order to minimize the chance of disruptive fabric reconfiguration events and guarantee that FCIDs do not change you will configure statically assigned. Note: As noted in Figure 1 above. Skyline ATS. per-VSAN switch Domain IDs. in order to provide for the possibility of later implementing Inter-VSAN Routing (IVR). Displays status of all VSANs. you must configure the required VSANs. even though one VSAN on each switch will not have any ports assigned to it. 4-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. . including the “isolated” and default VSANs Displays the interface assignment for all the configured VSANs and the isolated and default VSAN Displays FC domain ID and principal switch information show interface show vsan show vsan membership show fcdomain Overview After performing the initial configuration of your switches and management workstations. Command Description Displays information about interfaces.1 globally unique Domain IDs are no longer required to implement IVR. Inc. for educational purposes we will be creating both VSANs on both switches. Each edge “pod” will represent a separate department with its own redundant SAN fabric topology.Required Resources These are the resources and equipment required to complete this exercise:   2 MDS 9000 Fibre Channel switches 2 Windows 2000 hosts with Fabric Manager and Device Manager installed Command List The commands used in this exercise are described in the following table. you will configure Domain IDs which are globally unique. Furthermore. Note: As of SAN-OS 2.2 Copyright © 2008. However. one would typically build a redundant fabric design by creating VSAN X1 only on one switch and VSAN X2 on the other. In our case it has been decided that VSAN 1 will be used strictly as a “Management VSAN” in order to provide a unified view of the entire physical SAN fabric.

However. If you are working on Px-MDS2 you will create VSAN X2 on both switches in your pod. Lab Guide 4-3 . Copyright © 2007. Exercise Procedure 1: Create VSANs Complete these steps on both switches in your pod: Step 1 Launch Fabric Manager and authenticate to your switch using the username admin and the password 1234qwer. you will configure multiple VSANs and add the interfaces of the MDS 9000 switches in your pod that connect to the JBOD and the Windows 2000 servers. for those of you who prefer to use the command line interface. For example. we will also include the relevant CLI commands. If you are working on Px-MDS1 you will create VSAN X1 on both switches in your pod (“X” refers to your pod number}. the view for Pod 1 should be similar to the following: Step 2 Step 3 From the Logical Domains pane select the All VSANs folder. Inc.Task 1: Creating and Verifying VSANs In this task. Verify that you see a simple two-switch fabric in the topology map window. Skyline ATS. Note: Our focus will be on using the graphical FM and DM.

DM or FM.2 Copyright © 2008. 4-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Note: VSANs can be created from the CLI. Skyline ATS. . A big advantage of using FM is that you can instantly and easily create a VSAN across multiple switches in the fabric. Inc.Step 4 Click the Create Row button.

enter the VsanId of X2 and Name VSAN_X2. Click the Create button. We will configure static domain IDs using a different utility later in this lab. Note: Do not include spaces in the Name field—use underscores instead of spaces. If you are working on Px-MDS1. If you are working on Px-MDS2. enter the VsanId of X1 and Name VSAN_X1 (where X is your pod number). Copyright © 2007. create both VSANs on both switches. Inc. Leave the defaults for everything else. Note: Staic Domain IDs could be configured from the Create VSAN form. Note: If you are working alone in your pod. Skyline ATS.Step 5 Both switches in your pod should be selected. pay attention to upper and lower case since SAN-OS is case sensitive. Also. Lab Guide 4-5 .

0(2) + vsan database + + vsan 41 name "VSAN_41" vsan 42 name "VSAN_42" 4-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Login with username admin and the password 1234qwer.2 Copyright © 2008. the TE interfaces are up for all VSANs that exist on both ends of the links. Because the EISL links between the two switches are trunking for all VSANs.7 **** --. P1-MDS1# show running-config diff *** Startup-config --.Step 6 Wait a moment. Step 7 Select your switch icon in the topology map window.12 ---version 3. Step 8 Enter the command “show running-config diff”. Skyline ATS. Right-click and select Command Line Interface. The output will compare the running-config to the startup-config and tell you what has changed. Verify that the Operational Status of the new VSANs has changed to up. . and then click the Refresh Values button. Inc.1.Running-config *************** *** 1. Note: A VSAN is considered operationally up if it has at least one functioning interface.

Enter the command “show interface brief”. Close the CLI window. It is also important to realize that the changes you make with the graphical tools are not automatically saved to NVRAM. To become proficient with MDS 9000 family switches you need to be able to understand and interpret the running config. Step 10 Enter the command “show vsan” and examine the output. Inc. Step 9 Enter the command “copy run start” so that your changes are saved and so you can do similar comparisons in the future. To create VSANs from the CLI you would simply enter these three lines. Lab Guide 4-7 . VSAN 1 ideally should be used as a management VSAN and also can be used for TE ports. Verify that you see four VSANs. Note: It is important to realize that most configuration changes done through the FM and DM are simply updating the running configuration. It compares lines 1-7 of the startup-config to lines 1-12 of the running config.Note: The above is a partial display of the output. only interfaces your first two EISLs (fc1/1 + fc1/2) should be enabled. Enter the command “show vsan membership”. Step 11 Step 12 Step 13 Note: At this point. Skyline ATS. Copyright © 2007. Three of them should be active and up. Note: Cisco recommends that end devices not be placed in VSAN 1. These are the trunking ports between the two switches in your pod. Verify that all interfaces are in the default VSAN number 1. This is another way to verify that all interfaces are still in the default VSAN number 1. The plus signs indicate the three lines added to the running config.

Step 2 Select the Membership tab. Select VSANs from the FC menu. In the following steps we will use the DM. you will add interfaces to your VSANs. Inc. Exercise Procedure 1: Adding Interfaces to VSANs Step 1 Double-click your switch icon to invoke Device Manager. Skyline ATS. Note: Interfaces can be added to VSANs using the FM. DM or CLI. click it to show the physical interface selection tool. 4-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. If you are working on Px-MDS1 double-click the FC field for VsanID X1 (where X is your pod number).2 Copyright © 2008. .Task 2: Adding Interfaces to VSANs In this task. For those of you who prefer to use the command line interface. If you are working on Px-MDS2 double-click the FC field for VsanID X2 A button with three dots appears. we will also include the relevant CLI commands.

these interfaces should still be in a shutdown state. At this point. Enter the command “show vsan membership”. Note: On both switches interface fc1/5 is attached to Windows 2000 server-1 and interface fc1/10 is attached to your Windows 2000 server-2. Step 5 Select Command Line Interface from the Device menu. so the interfaces are the same on both MDS 9000 switches in your pod. assigning interfaces to them is that simple). Step 7 Copyright © 2007.Step 3 Click your host interfaces (5 and 10). Login as username admin and password 1234qwer. Inc. and FC1/10 should all be in your VSAN. Skyline ATS. All devices are dual ported. Click OK. and to VSAN X2 on Px-MDS2. Interface fc1/6 is attached to the JBOD. and your storage interface (6). FC1/6. Lab Guide 4-9 . Step 4 Click Apply and then click Close (after VSANs have been created. Verify that the three interfaces have been added to VSAN X1 on Px-MDS1. Note: At this point FC1/5. Step 6 Enter the command “copy run start” so that your changes are saved and so you can do similar comparisons in the future.

one per line. P4-MDS1(config)# vsan database P4-MDS1(config-vsan-db)# vsan 99 name test P4-MDS1(config-vsan-db)# vsan 99 interface fc1/11-12. and assign it three interfaces as follows: P4-MDS1# config Enter configuration commands. Inc. Delete VSAN 99 and then check the VSAN membership again as follows: P4-MDS1(config-vsan-db)# no vsan 99 Do you want to continue? (y/n) y P4-MDS1(config-vsan-db)# do show vsan membership Step 3 What happened to the three interfaces? ___________________________ Note: The three interfaces should have been placed into the isolated VSAN number 4094. . Step 1 Enter global config mode.2 Copyright © 2008. Skyline ATS. Verify that the three interfaces have been placed in VSAN 99. you will see what happens when you delete a VSAN that has interfaces assigned. End with CNTL/Z. create a new VSAN. fc1/14 Step 2 Enter the command “do show vsan membership”. Step 4 Move the three interfaces back into VSAN 1 and then check the VSAN membership again as follows: P4-MDS1(config-vsan-db)# vsan 1 interface fc1/11-12. fc1/14 P4-MDS1(config-vsan-db)# do show vsan membership Step 5 Return to exec mode: P4-MDS1(config-vsan-db)# end 4-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Ports in this VSAN cannot communicate with any ports.Task 3: Exploring the Isolated VSAN In this task.

In this task. An MDS 9000 switch with more than one VSAN will have a multiple Domain IDs. Lab Guide 4-11 . By default. Inc. VSAN X1 and VSAN X2 (where X refers to your pod number). This will ensure that all Domain IDs are globally unique. and determine how to configure the principal switch. If so continue to follow the steps to make the assigned domain ID static. The principal switch is elected based on priority and switch WWN. Exercise Procedure 1: Configure Static Domain IDs The lead SAN architect has decided that switch Domain IDs will be statically assigned according to the following table. Skyline ATS. You will be configuring them using decimal. The Domain IDs are shown first in hexadecimal. one each for VSAN 1. Most SAN administrators consider it a best practice to statically assign switch Domain IDs.Task 4: Configuring Static Domain IDs Every switch in a fabric is assigned a unique Domain ID. Note: In some cases you may discover that your switch has already been assigned one of the domain IDs shown on the table. you will determine the Domain IDs of your switch. Step 1 Find your switch in the table and make note of your three Domain IDs. but they will often be visible in hexadecimal so you should make a note of both. DOMAIN ID TABLE – Hex (Decimal) SWITCH VSAN 1 VSAN X1 VSAN X2 P1-MDS1 0x11 (17) 0x12 (18) 0x13 (19) P1-MDS2 0x16 (22) 0x17 (23) 0x18 (24) P2-MDS1 0x21 (33) 0x22 (34) 0x23 (35) P2-MDS2 0x26 (38) 0x27 (39) 0x28 (40) P3-MDS1 0x31 (49) 0x32 (50) 0x33 (51) P3-MDS2 0x36 (54) 0x37 (55) 0x38 (56) P4-MDS1 0x41 (65) 0x42 (66) 0x43 (67) P4-MDS2 0x46 (70) 0x47 (71) 0x48 (72) POD Pod 1 Pod 2 Pod 3 Pod 4 Note: Each switch has three Domain IDs that need to be statically assigned. one for every VSAN that exists on that switch (with the exception of the isolated VSAN). followed by their decimal equivalent in parenthesis. determine which switch is the principal switch. manually configure the Domain ID of a switch. Domain IDs are assigned automatically by the principal switch. VSAN 1 __________ VSAN X1 __________ VSAN X2 __________ Copyright © 2007.

so the principal switch is elected based on switch WWN. open Fabric Manager. all switches have the same priority. in the Logical Domain pane expand the All Vsans folder and select Domain Manager. . Step 4 Minimize FM. determine the current Domain IDs for each VSAN as follows: P4-MDS1# show fcdomain domain-list VSAN 1 Number of domains: 2 Domain ID WWN ------------------------------0x65(41) 20:01:00:0d:ec:06:4a:01 [Local] [Principal] 0x70(46) 20:01:00:0d:ec:06:4e:c1 VSAN 41 Number of domains: 2 Domain ID WWN ------------------------------0x45(69) 20:0b:00:0d:ec:06:4a:01 [Local] [Principal] 0x42(66) 20:0b:00:0d:ec:06:4e:c1 VSAN 42 Number of domains: 2 Domain ID WWN ------------------------------0x43(67) 20:0c:00:0d:ec:06:4a:01 [Local] [Principal] 0x48(72) 20:0c:00:0d:ec:06:4e:c1 Note: The above example indicates that the local switch (P4-MDS1) is the principal switch. 4-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Step 3 To view the equivalent information for the entire fabric. Inc.2 Copyright © 2008. Skyline ATS. The lowest WWN in the VSAN becomes principal.Step 2 From the CLI. By default.

Step 6 Step 7 Click the Configuration tab. Enter the decimal Domain IDs from the table above. Click in the IdType field for all three VSANs and select static.Step 5 To view the equivalent information for just your switch. Skyline ATS. Copyright © 2007. Lab Guide 4-13 . Inc. Double-click in the DomainId field for VSAN 1. open Device Manager and select Domain Manager from the FC menu. VSAN X1 and VSAN X2 (where X is your pod number).

Step 9 Click Apply. Note: In some cases you can perform a non-disruptive Build Fabric (BF) event.2 Copyright © 2008. click Yes. click in the Restart field and select disruptive for all three VSANs. rather than a disruptive Reconfigure Fabric (RCF) event. If you see the following dialog. . Click Refresh. we don’t care because there is no data traffic flowing. so we choose to do a disruptive restart to ensure that Domain IDs are statically reassigned. In this case. Skyline ATS. Inc. Step 10 Click the Running tab. 4-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 8 On the far right.

P1-MDS1# show running-config diff | include static + fcdomain domain 41 static vsan 1 + fcdomain domain 45 static vsan 41 + fcdomain domain 43 static vsan 42 Step 15 Copyright © 2007. Verify that the appropriate Domain IDs have been assigned to your VSANs and that the state of each VSAN is “stable”. Note: If you are working alone.Step 11 If necessary. Verify that it matches what you saw in the DM/FM output above. Verify that the appropriate Domain IDs have been assigned to the VSANs on both your switches. wait a moment and click the Refresh button again. complete the above steps on the other switch in your pod. Click the Switch column to sort by switch name. Lab Guide 4-15 . Enter the command “show fcdomain domain-list”. Skyline ATS. Inc. Enter the command “show running-config diff” to see what has changed as a result of the above steps. Step 12 Open Fabric Manager. Step 13 Step 14 Open a CLI window to your switch. Click the Refresh button.

Skyline ATS. Inc. 4-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3. . Note: The command to perform a disruptive reconfigure fabric (RCF) event from the CLI is: (config)# fcdomain restart disruptive vsan n Step 16 Enter the command “copy run start” so that your changes are saved and so you can do similar comparisons in the future.2 Copyright © 2008.Note: The above is a partial display of the output that demonstrates the commands needed to configure static switch Domain IDs from the CLI.

In the following steps we will demonstrate how to configure the switch priority to ensure its selection as the principal switch. Inc.Task 5: Configuring the Principal Switch It is generally considered a best practice to configure priorities on specific switches (usually core switches) to ensure they will be selected as the principal switches. If you are not seeing this. you should see that either the local switch is the principal switch. select Domain Manager from the FC menu. Note: At this point. Copyright © 2007. Skyline ATS. just continue. If so. Lab Guide 4-17 . In our case we have not modified the default principal switch priority so the principal switch is determined by the switch with the lower switch WWN. Click the Domains tab and observe the output. Switch priorities are equal by default. it may be because there is another team working in your pod and they have already configured the switch priorities ahead of you. or that the local switch is not the principal switch (as seen above). Step 1 In Device Manager. Our goal will be to select MDS1 as the principal switch for VSAN X1 and MDS2 as the principal switch for VSAN X2 (where X is your pod number).

the lower the number. and set the priority for VSAN X2 to 250. Inc.Step 2 Click the Configuration tab. set the priority for VSAN X1 to 10. the higher the priority. Step 4 Click in the Restart field for VSAN X1 and X2. Click the Help button. Select disruptive. 4-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. The permissible values range from 1 to 254. Spend a few moments reading the context sensitive help. What does it mean to disable the Domain Manager? What is a “preferred” Domain ID? Step 3 Double-click in the Priority field for VSAN X1 and X2 (where X is your pod number). . and set the priority for VSAN X2 to 10. If you are working on PxMDS2. If you are working on PxMDS1. set the priority for VSAN X1 to 250. Skyline ATS. Click Apply.

Verify that Px-MDS1 is now the principal switch for VSAN X1 and that Px-MDS2 is the principal switch for VSAN X2.168.0. The IP address below is the IP address of your W2K server. Enter the command “show running-config diff” to see what has changed as a result of the above steps. Step 8 Step 9 Enter the command “copy run start” so that your changes are saved and so you can do similar comparisons in the future. Save your configuration to the TFTP server as follows (where fname is your first name. Copyright © 2007. Lab Guide 4-19 . Inc. Skyline ATS. Px-MDS1# sh run diff | include priority + fcdomain priority 10 vsan 11 + fcdomain priority 250 vsan 12 Note: The above is a partial display of the output that demonstrates the commands needed to configure FC Domain Manager priorities for determining principal switch selection. make sure it is unique). Wait a few moments and then click the Refresh button.198/podX/<fname.Step 5 Click the Domains tab. # copy run tftp://192. Step 6 Step 7 Open a CLI window.cfg> That completes this lab exercise.

Appendix A – Sample Lab Configuration File (partial) The following output has been edited to include the portions of the configuration file most relevant to this lab. Skyline ATS. This sample is taken from 9120-1 in Pod 1..2 Copyright © 2008. . vsan database vsan 41 name "VSAN_41" vsan 42 name "VSAN_42" fcdomain domain 17 static vsan 1 fcdomain priority 10 vsan 11 fcdomain domain 18 static vsan 11 fcdomain priority 250 vsan 12 fcdomain domain 19 static vsan 12 fcdomain fcid persistent global-enable fcdomain fcid persistent vsan 1 fcdomain fcid persistent vsan 61 fcdomain fcid persistent vsan 62 vsan database vsan 41 interface fc1/5 vsan 41 interface fc1/6 vsan 41 interface fc1/10 interface fc1/1 no shutdown interface fc1/2 no shutdown Note: All other interfaces should be shut down. Inc. Px-MDS1# show running-config Building Configuration .. except for mgmt0. 4-20 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

In this lab. you will configure PortChannels between your pod’s switches. After completing this exercise. . you will be able to meet these objectives:    Configure and operate a PortChannel Demonstrate the benefit of PortChannels with FSPF Demonstrate the benefit of Port Tracking Visual Objective The figure illustrates what you will accomplish in this exercise.Lab Exercise 5: Configuring PortChannels Exercise Objective In this exercise. you will configure PortChannels between the switches in your pod.

Required Resources These are the resources and equipment required to complete this exercise:   2 MDS 9000 Fibre Channel switches 2 Windows 2000 hosts with Fabric Manager and Device Manager installed Command List The commands used in this exercise are described in the table here. Inc. Displays the status for PortChannel x show interface fcx/y show interface brief show interface portchannel x Overview In this exercise. Skyline ATS. you will configure PortChannels between the two switches in your pod. 5-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Displays status for all interfaces with less detail.2 Copyright © 2008. . Command Description Displays status and statistics for the indicated interface.

Step 2 Mouse over the link between the two switches and observe the callout box that appears. Inc. similar to that shown here for Pod 1. Copyright © 2008. Step 3 Locate and click the Port Channel button in the icon toolbar. Skyline ATS.Task 1: Configuring Single Link PortChannels In this task. Lab Guide 5-3 . You should see a simple two-switch fabric displayed in the topology map. We will also show the CLI commands needed to create a PortChannel manually. Note: Because it is by far the simplest method. Exercise Procedure Complete these steps: Step 1 Launch Fabric Manager. you will configure a single link PortChannel between the MDS 9000 switches in your pod. we will create PortChannels using the Fabric Manager PortChannel Wizard.

even a single link. Inc. . In the following steps you will create a single link PortChannel. In our case. Skyline ATS. Note: The Port Channel Wizard will display all pairs of switches in the fabric that have an active ISL between them.Step 4 Click Next. 5-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. Note: Some SAN architects are of the opinion that all links. between two MDS 9000 family switches should be placed into a PortChannel because future links can be added to an existing PortChannel with minimal disruption. there should only be one pair displayed.

Click Next. Skyline ATS. Lab Guide 5-5 .Step 5 If you are working on Px-MDS1. ensure only your ISL ports appear in the Selected window (fc1/1-fc1/1). Caution: Copyright © 2008. Inc. Click the left arrow to move unwanted links out of the selected window. Do NOT check the “Dynamically form Port Channel Group” radio button. If you are working on Px-MDS2. ensure only your ISL ports appear in the Selected window (fc1/2-fc1/2).

If you are working on Px-MDS2. use Channel Id 1 for both. Click Yes. use Channel Id 2 for both. Step 7 Read the warning. 5-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. . Review the information and then click Finish.Step 6 If you are working on Px-MDS1. Inc.2 Copyright © 2008. Skyline ATS. repeat the above steps for the other link. Note: If you are working alone in your pod.

Skyline ATS. Step 10 Right-click the link and select Attributes. Copyright © 2008. Lab Guide 5-7 . Step 9 Mouse over the link and observe the callout box that appears. Inc.Step 8 If there is an X over the ISL. Compare this to the output displayed earlier. After refreshing the map it may take 10-20 seconds for the red X to disappear. click the Refresh Map button and verify that it goes away.

Inc. Skyline ATS. Notice that all VSANs are allowed. but that the only UpVsans are those existing on both ends of the PortChannels. What is the per-VSAN cost of the links? __________ 5-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. .2 Copyright © 2008.Step 11 Observe the information in the General tab window displayed above the topology map. and then click the Trunk Config tab. Step 12 Click the FSPF tab.

select one of the two ends of your port channel (channel 2). select one of the two ends of your port channel (channel 1). If you are working on Px-MDS2. Expand the ISLs folder and select Port Channels. Note: In the following steps you will delete your PortChannel. Lab Guide 5-9 . Copyright © 2008. Select the Physical Attributes pane under the tree window.Step 13 Return to Fabric Manager. Inc. Skyline ATS. Step 14 If you are working on Px-MDS1. Click the Delete Row button.

Step 16 Repeat for the other end of your port channel. you are essentially back to where you were at the beginning of the lab. After both PortChannels are deleted and the corresponding ports are re-enabled. Inc. Skyline ATS.2 Copyright © 2008.Step 15 Click Yes to confirm deletion.  Note: 5-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. .

# debug fspf flood Step 2 Step 3 Enter global config mode: # config Enter configuration commands. End with CNTL/Z. Enable debugging of FSPF flooding events. but can be invaluable for Cisco support engineers. (config-if)# no shutdown Note: Wait several seconds for the link to initialize. Inc. Skyline ATS. If you are working at a faster pace. you will configure a multi link PortChannel between the MDS 9000 switches in your pod and demonstrate the benefit of PortChannels for reducing FSPF overhead and FSPF update traffic on ISL links. If you are working on Px-MDS2. FSPF updates are flooded throughout the entire fabric. (config-if)# shutdown Note: You should immediately see several lines of debug output. Debug output is often fairly cryptic to the typical SAN administrator. Step 7 Ensure that all members in the pod are working together. Step 5 Shutdown the interface. Copyright © 2008. enter interface sub-config mode for interface fc1/1. Lab Guide 5-11 . Step 4 If you are working on Px-MDS1. and then re-enable the interface. please wait for the other pod members to catch up! Exercise Procedure Complete these steps: Step 1 If necessary.Task 2: Configuring Multi-Link PortChannels and Demonstrating the Benefits of PortChannels with FSPF In this task. You should see a large number of lines of debug output. enter interface sub-config mode for interface fc1/2. Please coordinate with other members using the same pod. Note: For most of this task you must work as a single team within your pod. open another Command Line Interface to your switch and login as username admin with password 1234qwer. Verify that ISL interfaces are up (fc1/1 + fc1/2) as TE ports on both switches. (config)# interface fc1/1 Note: The above example is MDS1. one per line. Step 6 Press Enter to display the switch prompt.

Follow the same steps as in Task 1 except this time add both links to the PortChannel. Skyline ATS. If you prefer. (config-if)# interface port-channel 100 Step 13 “Bounce” the entire PortChannel by disabling then re-enabling it. This leads to a much more resilient fabric and is the main reason why PortChannels are recommended as a best practice whenever more than one link exists between two MDS switches. Note: Step 9 Return to the Command Line Interface window. . Use Channel Id 100. first create a single link PortChannel as in Task 1. Step 12 Move to interface sub-config mode for the PortChannel interface. # no debug all 5-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. and then invoke the Port Channel Wizard again and select Edit Existing to add another link. (config-if)# end Step 15 Disable all debugging.Step 8 Designate one of the members in your pod to configure a two link PortChannel using the Fabric Manager Port Channel Wizard. If one link in a multi-link PortChannel goes down. (config-if)# do show debug Show Debug all FSPF Routing Protocol Application: FSPF flooding debug debugging is on Step 10 Step 11 “Bounce” the port by disabling then re-enabling it. Inc. You should still be in interface sub-config mode for one of the links in the PortChannel. (config-if)# shutdown (config-if)# no shutdown Note: If the entire PortChannel goes down. there is no impact from the FSPF perspective. Enter the command “do show debug” to verify that FSPF debugging is enabled. FSPF must re-calculate the topology database and flood updates throughout the fabric.2 Copyright © 2008. Step 14 Return to EXEC mode. (config-if)# shutdown (config-if)# no shutdown Note: You should not see any debug output.

therefore the link cost should be 250.Step 16 Verify that the PortChannel is trunking for VSANs 1. Inc.41-42) () () Step 17 Check the PortChannel database. where n is the number of Gbps in the link. Copyright © 2008. # show fcroute unicast D:direct R:remote P:permanent V:volatile A:active N:non-active # Next Protocol -------fspf fspf fspf VSAN ---1 41 42 FC ID/Mask -------. two 2 Gbps links gives us an aggregate bandwidth of 4 Gbps. Skyline ATS.-------0x110000 0xff0000 0x120000 0xff0000 0x130000 0xff0000 RCtl/Mask ---.41-42) Trunk vsans (up) Trunk vsans (isolated) Trunk vsans (initializing) (1. Lab Guide 5-13 . # show port-channel database port-channel 100 Administrative channel mode is on Operational channel mode is active Last membership update succeeded First operational port is fc1/1 2 ports in total. # show interface port-channel 100 port-channel 100 is trunking Port description is To Px-MDS2 Hardware is Fibre Channel Port WWN is 24:01:00:0d:ec:06:4e:c0 Admin port mode is E. X1 and X2 (where X is your pod number). This link cost will not change when one link goes down. In this case. 2 ports up Ports: fc1/1 fc1/2 [up] * [up] Step 18 Verify that the FSPF link cost reflects the aggregate bandwidth of the PortChannel by checking the FC routing table. trunk mode is on Port mode is TE Port vsan is 1 Speed is 4 Gbps Trunk vsans (admin allowed and active) (1.---0x00 0x00 0x00 0x00 0x00 0x00 Flags ----D P A D P A D P A Hops ---1 1 1 Cost ---250 250 250 Note: The basic formula for FSPF link cost is 1000 / n.

# show interface fc1/5 brief # show interface port-channel 100 brief Step 4 Disable interface PortChannel 100 #config (config)# interface port-channel 100 (config-if)# shutdown (config-if)# end 5-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. Step 1 Enable the port tracking feature.Task 3: Configure Port Tracking Activity Procedure Complete the following steps on both switches. . # config (config)# port-track enable Step 2 Track interface fc1/5 with interface port-channel 100 and enable interface fc1/5. Skyline ATS. Inc. (config)# interface fc1/5 (config-if)# port-track interface port-channel 100 (config-if)# no shutdown (config-if)# end Step 3 Verify that fc1/5 and Port-Channel 100 interfaces are up.

trunk mode is on Snmp traps are enabled Port vsan is 1 Linked to 1 port(s) Port linked to interface fc1/5 . Inc. Display ports linked to the PortChannel 100 interface # show interface port-channel 100 port-channel 128 is down (Administratively Down) Hardware is Fibre Channel Port WWN is xx:xx:xx:xx:xx:xx:xx:xx Admin port mode is E.. # config (config)# interface fc1/5 (config-if)# no port-track interface port-channel 100 That completes this lab exercise. Copyright © 2008. . . Skyline ATS. # config (config)# interface port-channel 100 (config-if)# no shutdown (config-if)# end Step 4 Display the status of interface fc1/5. # show interface fc1/5 fc1/5 is up . Lab Guide 5-15 . trunk mode is on Snmp traps are enabled Port vsan is 10 Receive data field size is 2112 Beacon is turned off Port tracked with interface port-channel 100 (down) Step 2 . SFP is short wave laser w/o OFC (SN) Port WWN is xx:xx:xx:xx:xx:xx:xx:xx Admin port mode is auto.. .Activity Verification Complete the following steps to verify your configuration. Step 5 Turn off port tracking. Step 3 Enable the PortChannel 100 interface on both switches. Step 1 Display the status of interface fc1/5 # show interface fc1/5 fc1/5 is down (All tracked ports down) Hardware is Fibre Channel. .

Appendix A – Sample Lab Configuration File (partial) The following output has been edited to include the portions of the configuration file most relevant to this lab.. Px-MDS1# show running-config Building Configuration . This sample is taken from MDS1 in Pod 1. Skyline ATS.2 Copyright © 2008. Inc.. . interface port-channel 100 switchport description To Px-MDS2 switchport mode E interface fc1/1 channel-group 100 force no shutdown interface fc1/2 channel-group 100 force no shutdown 5-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Lab Exercise 6: Configuring Interfaces Exercise Objective In this exercise. you will be able to meet these objectives:   Configure E_Ports and TE_Ports Configure F_Ports and FL_Ports Visual Objective Figure 1 illustrates the topology that you will use in this exercise. In this lab. you configured the VSAN membership for the VSAN X1 and X2 interfaces shown in the diagram. After completing this exercise. Figure 1. you will use configure Fibre Channel interfaces on MDS 9000 switches and verify that the interfaces are operational. you will configure the interfaces themselves. which are connected to the host and storage end devices. . Lab Pod Topology In the previous lab.

Required Resources These are the resources and equipment required to complete this exercise:     2 MDS 9000 Fibre Channel switches 2 Windows 2000 hosts with Fabric Manager and Device Manager installed 2 Windows 2000 hosts with dual Qlogic Fibre Channel HBAs 1 FC-AL JBOD with at least four disks Command List The commands used in this exercise are described in the table here. The default interface configuration will often allow the interfaces to operate correctly. Skyline ATS. Displays status for all interfaces with less detail. you may need to configure other interface parameters. Inc.2 Copyright © 2008. but best practices may require changing the default configuration. . show interface fcx/y show interface brief Overview After configuring VSANs and assigning ports to VSANs. Command Description Displays status and statistics for the indicated interface. 6-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Note: Our focus will be on using the graphical FM and DM. Step 2 Mouse over the link between the two switches and observe the pop-up window. for those of you who prefer to use the command line interface. we will also include the relevant CLI commands.Task 1: Configuring Interfaces In this task. you will configure the interfaces for host and storage connections. Copyright © 2008. as well as the interfaces for ISL connections between switches in your pod. Skyline ATS. Lab Guide 6-3 . Exercise Procedure Complete these steps on both switches in your pod: Step 1 Open a Fabric Manager connection to your switch. Step 3 Double-click your switch icon to launch Device Manager. and between your switches in your pod and the core. However. You should see a simple twoswitch fabric similar to the one shown here for Pod 4. Inc. At this point you should see that your ISL ports are up and operating as TE ports (fc1/1 + fc1/2).

Step 4 Single-click to select port 5. Click the Refresh Display button again. Step 5 Right-click inside any of the three yellow boxes and select Enable. Login with the username admin and the password 1234qwer. port 6 should come up as an FL port. Step 7 6-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Ports 5 and 10 should come up as F ports.2 Copyright © 2008. Step 6 Select Command Line Interface from the Device menu. Click the Refresh Display button and verify that all three ports have a yellow highlight box around them. Skyline ATS. Enter the command “copy run start” to save your changes and to enable similar comparisons later. hold down the Ctrl key and click to select port 6 and port 10. . Inc. Now. Note: Ports 5 and 10 each are connected to one of the two FC HBA ports in each of the two Windows 2000 servers. Port 6 is connected to a JBOD which contains four disks in a dual arbitrated loop configuration.

Inc. # show fcns database VSAN 41: -------------------------------------------------------------------------FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------0x2a0001 0x2a0002 0x2a01e2 0x2a01e4 0x2a01e8 0x2a01ef N N NL NL NL NL 21:00:00:e0:8e:0e:a8:12 (Qlogic) 21:01:00:e0:8e:2e:a5:5b (Qlogic) 21:00:00:04:cf:20:b7:3f (Seagate) 21:00:00:04:cf:3b:08:da (Seagate) 21:00:00:04:cf:3b:08:84 (Seagate) 21:00:00:04:cf:3b:08:e3 (Seagate) scsi-fcp:init scsi-fcp:init scsi-fcp: scsi-fcp: scsi-fcp: scsi-fcp: VSAN 42: -------------------------------------------------------------------------FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------0x2e0001 0x2e0002 0x2e01e2 0x2e01e4 0x2e01e8 0x2e01ef N N NL NL NL NL 21:01:00:e0:8e:2e:a8:12 (Qlogic) 21:00:00:e0:8e:0e:a5:5b (Qlogic) 22:00:00:04:cf:20:b7:3f (Seagate) 22:00:00:04:cf:3b:08:da (Seagate) 22:00:00:04:cf:3b:08:84 (Seagate) 22:00:00:04:cf:3b:08:e3 (Seagate) scsi-fcp:init scsi-fcp:init scsi-fcp: scsi-fcp: scsi-fcp: scsi-fcp: Copyright © 2008. # show flogi database --------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME --------------------------------------------------------------------------fc1/5 fc1/6 fc1/6 fc1/6 fc1/6 fc1/10 41 41 41 41 41 41 0x2a0001 0x2a01e2 0x2a01e4 0x2a01e8 0x2a01ef 0x2a0001 21:00:00:e0:8e:0e:a8:12 21:00:00:04:cf:20:b7:3f 21:00:00:04:cf:3b:08:da 21:00:00:04:cf:3b:08:84 21:00:00:04:cf:3b:08:e3 21:01:00:e0:8e:2e:a5:5b 20:00:00:e0:8e:0e:a8:12 20:00:00:04:cf:20:b7:3f 20:00:00:04:cf:3b:08:da 20:00:00:04:cf:3b:08:84 20:00:00:04:cf:3b:08:e3 20:01:00:e0:8e:2e:a5:5b Total number of flogi = 6. These are the four disks in the FC-AL JBOD. Note: FLOGI refers to the FC Extended Link Server Fabric Login process. Lab Guide 6-5 . Step 9 Check the FC Name Server database to see which devices are logged into all of the VSANs in the entire fabric. Note that there are four devices logged on to the same port. Skyline ATS.Step 8 Check the FLOGI database to see if any devices have logged into the switch.

and two Qlogic host icons. Return to Fabric Manager.Note: If the other switch has not yet configured their interfaces. Note: Experiment with other buttons on the icon bar. Skyline ATS. Observe the change in the topology map view. Click the Layout Map button. 6-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. each with two FC HBA connections to the switches in your pod. you will not see all of the devices in the distributed FC Name Server database. Inc. Right-click in the map and Expand Loops. and click to select the various VSAN folders in the tree. Verify that you see two FC-AL symbols. . Step 12 Select the Logical Domains pane in the tree view. Step 10 Step 11 Ensure both groups have completed the above steps before proceeding. each attached to four Seagate disks.

Step 14 Step 15 Return to Device Manager for your switch. Expand the End Devices folder and click Storage. Lab Guide 6-7 . Step 16 Verify that the information matches what you saw from the CLI above. Skyline ATS. Inc. Copyright © 2008.Step 13 Click the Physical Attributes pane. Select Name Server from the FC menu. Click Close.

2 Copyright © 2008. Verify that all ports have a Status of Operationally up and a FailureCause of none. Set the Admin Mode of fc1/6 to FL. Note: Some SAN administrators are of the opinion that. for higher security. Skyline ATS.Step 17 Select FC Enabled from the Interface menu. you should hard code the port mode rather letting ports auto configure. 6-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Click Refresh. . Inc. Step 18 Set the Admin Mode of fc1/5 and fc1/10 to F. This is easily done as follows. Step 19 Click Apply.

Step 22 Click OK to close the Error pop-up.Step 20 Select the Trunk Config tab. and then click Close to exit the FC Interfaces window. Lab Guide 6-9 . all VSANs are allowed on trunk interfaces (TE Ports). Note that by default. you may wish to restrict the VSANs allowed on EISLs. For security or traffic engineering reasons. Copyright © 2008.X2 (where X is your pod number). Step 21 Double-click in the AllowedVsans field for your EISLs (fc1/1 + fc1/2). Inc. you cannot make modifications to the individual interfaces.X1. Skyline ATS. Note: Because your ISL ports are now part of a PortChannel. Click Apply. Enter 1.

2 Copyright © 2008. Step 25 Step 26 Select the Trunk Config tab. Select FC Physical. In the Physical Attributes pane in the tree view expand the Interfaces folder. Click Close. Allowed and UpVsans for EISL interfaces (fc1/1 +fc1/2) on both switches in your pod. Skyline ATS. . Inc. 6-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Note the Oper. Note that all of the physical FC interfaces in the fabric can be configured from here. Warning The following steps will impact the PortChannel between the switches in your pod. Please coordinate with other pod members before performing these steps. Return to Fabric Manager.Step 23 Select Port Channels from the Interface menu. Step 24 Repeat steps 20-22 above to modify the VSAN allowed list on the PortChannel 100.

Inc. and then click the Refresh Values button. Step 28 Click in the Admin column and set the trunk mode to auto for both switches. What happened to the trunk operation and up VSANs list? ___________________ Copyright © 2008. Step 29 Click the Apply Changes button. Lab Guide 6-11 . Skyline ATS.Step 27 Click FC Logical in the tree view and select the Trunk Config. Wait a moment.

Select Save Configuration from the Admin menu. 6-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Click the Refresh Display button. Step 32 Step 33 Step 34 Click Yes to confirm. Verify that the port is trunking..2 Copyright © 2008. Step 30 Return to Device Manager. Verify that ports 1 and 2 are no longer Trunking E ports.Note: It is important to understand that trunk mode cannot be set to auto on both ends of a link that is meant to trunk. Step 31 Return to Fabric Manager and reconfigure the PortChannel to trunk on both ends of the link. At least one side must be set to trunk. Skyline ATS. Return to Device Manager. Wait for the Success message and then click Close. Inc. .

Set ServerAddress to the address of your TFTP server (192. Wait for the File transfer successful message. Step 37 Click Apply. Inc. Lab Guide 6-13 . That concludes this lab exercise. Click Close.198). Leave From set to startupConfig or select runningConfig (at this point they should be identical).Step 35 Step 36 Select Copy Configuration from the Admin menu.cfg (where fname is a unique filename that you will remember later if needed). Copyright © 2008. Skyline ATS. Leave To set to serverFile.0. Set FileName to fname. Leave Protocol set to tftp.168.

# show running-config Building Configuration . This sample is taken from MDS1 in Pod 4. Inc.. .Appendix A – Sample Lab Configuration File (partial) The following output has been edited to include the portions of the configuration file most relevant to this lab. Skyline ATS. interface port-channel 101 switchport description To P4-MDS1 switchport mode E switchport trunk allowed vsan 1 switchport trunk allowed vsan add 41-42 interface fc1/5 switchport mode F no shutdown interface fc1/10 switchport mode F no shutdown interface fc1/6 switchport mode FL no shutdown 6-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008..

you will configure zones within the redundant VSANs in order to allow each VSAN to serve as an alternate path for server applications. and zonesets Configure zoneset distribution Observe and troubleshoot a zone merge isolation event Visual Objective Figure 1 illustrates the topology that you will implement in this exercise. . zones. Figure 1. After completing this exercise. You will also explore zoneset distribution policies and perform a zone merge. you will configure zones and zonesets to isolate servers and their and storage devices the VSANs in your pod. Zoning Configuration for Pod “X” In this exercise.Lab Exercise 7: Configuring Zones Exercise Objective In this exercise. you will be able to meet these objectives:    Configure aliases.

such as database updates or zone merges. However. showing its name and the name of each active zone with all the members of all the zones listed. the zonesets and zones in the full zone database. In this lab you will create “single initiator” zones. 7-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Displays a list of all the ports that are logged in to the FC name server. Displays the active zoneset. at this point the servers cannot access their storage because no zoning has been established and the default zone policy is deny. so each of the two server HBAs must have a separate zone for the same disk. Command Description Displays all the zonesets that are configured on the switch Displays all the zones that are configured on the switch or in the specified VSAN Displays the status of the zones that are configured on the switch or in the VSAN. Skyline ATS. and verified that the servers and storage devices were logged into their fabrics. .2 Copyright © 2008. Inc. Displays the status of and statistics for interface fcx/y. and which zoneset (if any) is the active zone. so that each HBA port (the initiator) has exclusive access to its storage. Launches debugging for a specific zoning activity. Shows the default zone policy. you configured VSANs for redundant fabrics. The FC disks are dual-ported. enabled interfaces for servers and storage. show zoneset show zone [ vsan X ] show zone status [ vsan X ] show zoneset active [ vsan X ] show fcns database [ vsan X ] show interface fcx/y debug zone [ database | merge ] Overview In earlier labs.Required Resources These are the resources and equipment required to complete this exercise:     2 MDS 9000 Fibre Channel switches 2 Windows 2000 hosts with Fabric Manager and Device Manager installed 2 Windows 2000 hosts with dual Qlogic Fibre Channel HBAs 1 FC-AL JBOD with at least four disks Command List The commands used in this exercise are described in the table here.

will configure four zones. working on the other Px-MDS2.   On Px-MDS1. You will create zones using the Fabric Manager Zone Wizard. which is the approach we will take in this exercise. One team. Display the contents of the FLOGI database for the JBOD interface. However. we will also include the relevant commands at the end of the exercise. Lab Guide 7-3 . Skyline ATS. Exercise Procedure 1: Preparing to Create Zones and Zonesets Prior to configuring zones and zonesets you must have a very good idea of what you are trying to accomplish. you will configure zones and the zoneset for VSAN_X2 Note: It is generally considered easiest to configure zoning from the GUI.Task 1: Configuring Zones and Zone Sets In this task. Refer back to the Visual Objective on page 1. If the diagram and instructions are not clear. data corruption will ultimately ensue. for those of you who prefer the CLI. The disks are dual-ported. one for each disk in the JBOD. must coordinate to ensure they are using the appropriate and corresponding disks. Compare the output on Px-MDS1 with the output on Px-MDS2: Step 2 P4-MDS1# show flogi database interface fc1/6 --------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME --------------------------------------------------------------------------fc1/6 fc1/6 fc1/6 fc1/6 41 41 41 41 0x1c00e2 0x1c00e4 0x1c00e8 0x1c00ef 21:00:00:20:37:42:51:3c 21:00:00:04:cf:b5:ec:d4 21:00:00:04:cf:20:b7:e6 21:00:00:04:cf:3b:0f:3b 20:00:00:20:37:42:51:3c 20:00:00:04:cf:b5:ec:d4 20:00:00:04:cf:20:b7:e6 20:00:00:04:cf:3b:0f:3b P4-MDS2# show flogi database interface fc1/6 --------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME --------------------------------------------------------------------------fc1/6 fc1/6 fc1/6 fc1/6 42 42 42 42 0x4800e2 0x4800e4 0x4800e8 0x4800ef 22:00:00:20:37:42:51:3c 22:00:00:04:cf:b5:ec:d4 22:00:00:04:cf:20:b7:e6 22:00:00:04:cf:3b:0f:3b 20:00:00:20:37:42:51:3c 20:00:00:04:cf:b5:ec:d4 20:00:00:04:cf:20:b7:e6 20:00:00:04:cf:3b:0f:3b Copyright © 2008. you will configure zones and the zoneset for VSAN_X1 On Px-MDS2. Inc. Login with the username admin and the password 1234qwer. The other team. and SAN administrators’ heads will roll  Step 1 Open a Command Line Interface window to your switch. ask the instructor for an explanation. you will create zones and zonesets for the devices in VSAN X1 and X2 (where X is your pod number). Each server will have access to two disks. If you do not agree upon and select the correct disks and ports. working on one Px-MDS1.

2 Copyright © 2008. . Skyline ATS. Step 3 Reach agreement with the team working on the other MDS 9000 switch in your pod as to which PWWN represents disk1. disk3. and disk4. disk2. differing only in the first octet (hex 22 versus hex 21). Write down the last three octets of the PWWNs in the table: DISK Disk1 Disk2 Disk3 Disk4 PWWN 7-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Note: The Port WWNs of the corresponding disks are nearly identical. Inc.

Exercise Procedure 2: Creating Global Aliases and Enclosures
Note: The following procedure requires your entire pod to work as a single team. Select one pod team member to execute the following steps on the Px-MDS1 switch only.

Step 1 Step 2

Open a Fabric Manager connection to the Px-MDS1 switch. Select All VSANs from the Logical Domains pane and End Devices from the Physical Attributes pane.

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

7-5

Step 3

Next you will configure device alias names for all devices in your pod. It is important to choose the correct names in order for the rest of this lab to function smoothly. If you are unsure of the correct alias names ask your instructor to verify before you apply the changes. Fill in the Alias field, for all 12 devices (four dual ported disks and two dual ported hosts). All devices connected to the Px-MDS1 use port 0 and thus should end with a –p0. All devices connected to the PxMDS2 use port 1 and thus should end with a –p1. Review the diagram at the beginning of the lab to ensure that you choose the correct name and port for the server devices. SAN-OS is case sensitive, for consistency with future lab instructions use all lower case characters when setting device aliases.

Step 3

Ask your instructor to confirm your work before applying the changes.

7-6

Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

Step 4

In order to create Fabric Manager Topology Map enclosures that reflect the device alias naming convention (-p0 –p1) we need to add a regular expression to the fabric manager server.properties file. Open the server.properties files by clicking on Start -> Programs -> Cisco MDS9000 -> Server Properties When prompted open the file with Wordpad.

Step 5

Locate the fabric.aliasRE variable

Step 6

Prepend the following regular expression EXACTLY as written, including case: (.*)[_-]P.*,

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

7-7

Step 7

Save the server.properties file.

Step 8

When prompted, answer Yes to save in a text-only format.

Step 9

Stop and then restart Fabric Manager In order to apply your newly created device aliases to your Fabric Manager topology map you must create enclosures using the newly created regular expression. Select all twelve lines and click on the Alias->Enclosure button.

Step 10

7-8

Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

Inc. Copyright © 2008.Step 11 Verify that the regular expression you added above is the visible. Skyline ATS. Click on the Apply Changes on the End Devices table. Step 12 Step 13 Click Apply and then Close. Lab Guide 7-9 .

2 Copyright © 2008. You should see the Device Alias field already filled out. Skyline ATS. . Step 15 Open a Fabric Manager connection to the Px-MDS2 switch. End Devices from the Physical Attributes pane. Select all twelve lines from the data pane. Inc. 7-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Click on All VSANs from the Logical Domains pane.Step 14 Display the fabric topology map and verify that the Fabric Manager created enclosures using the aliases names that you entered. Click on Alias->Enclosure.

Copyright © 2008. The enclosure names should now be visible on W2K2 topology map. Inc. Step 18 On both switches save your running-configuration to your startup-configuration. Skyline ATS. Lab Guide 7-11 . Step 17 Click on the Apply Changes on the End Devices table.Step 16 When the regular expression list is presented click Apply and then Close.

Skyline ATS. . If you are configuring both switches you will need to perform the following steps in each switch in your pod. PxMDS2 has been assigned VSAN X2). Inc. Step 1 Step 2 Open a Fabric Manager connection to your switch. Right click on Zones and select Insert. From the Logical Domains pane right click and select Edit Local Full Zone Database on your assigned VSAN (Px-MDS1 has been assigned VSAN X1.Exercise Procedure 3: Creating Zones and Zonesets Both teams in your pod can begin working separately again. 7-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. Step 3 Ensure that your VSAN and Switch are selected.

Lab Guide 7-13 . Skyline ATS. ZoneS2D3. Step 5 Repeats steps 3 and 4 to create three additional zones: ZoneS1D2. Please check your spelling! Copyright © 2008.Step 4 Enter ZoneS1D1 (Server1 / Disk1) Note: The screen captures below are taken from MDS4 in Pod 1. Expand the Zones folder and verify that all four zones have successfully been created. Inc. the steps are essentially the same for MDS2 in all pods. Note: Zone and zoneset names are case sensitive. Zone S2D4. however.

Skyline ATS.2 Copyright © 2008. 7-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 6 Drag and Drop server1 and disk1 into ZoneS1D1 Drag and Drop server1 and disk2 into ZoneS1D2 Drag and Drop server2 and disk3 into ZoneS2D3 Drag and Drop server2 and disk4 into ZoneS2D4 Step 7 Verify that each of the four zones now contains two devices. . Inc.

Copyright © 2008. Lab Guide 7-15 . Step 9 If you are working on Px-MDS1 change the Zoneset name to ZoneSetX1 (where X is your pod number).Step 8 Right click on Zonesets and select Insert. Inc. Step 10 Drag and drop each of the four zones into your newly created zoneset. Skyline ATS. If you are working on Px-MDS2 change the Zoneset name to ZoneSetX2.

Note: If the above instructions are unclear. .2 Copyright © 2008. It is critical to properly configure zoning. 7-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 11 Activate your zoneset and save your changes when prompted. Skyline ATS. Inc. please ask the instructor for clarification.

Do the same for the VSAN_X2 and ZonesetX2 folders (where X is your pod number). Inc. ZonesetX1. Step 3 Copyright © 2008. Lab Guide 7-17 . Expand the VSAN_X1 and ZonesetX1 folders. Note the switch in the path. Note the server and disk icons highlighted in the topology map. Click on ZoneS1D1 for VSAN_X1. Skyline ATS.Exercise Procedure 3: Verifying Zones and Zonesets Step 1 Step 2 Select the Logical tab in the Fabric Manager tree view window.

.2 Copyright © 2008. Verify they are the same as above. Skyline ATS. Note the switch in the path. Note: If your verification fails. Note the server and disk icons highlighted in the topology map. Verify it is the other switch in your pod. you may need to delete or modify zones or zonesets and try again. ZonesetX2. Verify that each disk is used once in each VSAN.Step 4 Click on ZoneS1D1 for VSAN_X2. Inc. 7-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3. The procedure for modifying zones and zonesets will be covered in the next section. Verify that two zones are using one server and the other two zones are using the other server. Step 5 Repeat the above steps for the remaining three zones in each VSAN.

Copyright © 2008. however. Display the full zoneset for the other VSAN in your pod: P4-MDS1# show zoneset vsan 42 Step 11 What do you see? __________ Note: You should see nothing. this is not always the case. only the active zone database is propagated to other switches in the fabric. and the full zone database. Skyline ATS. they should contain the same information. each of which has two members (the example below is for Pod 1.Step 6 Step 7 Open a Command Line Interface window to your switch. Step 8 Repeat the above command. More on this later. displayed in the output of step 8. the full zone database is not. P4-MDS1# show zoneset vsan 41 Note: It is important to understand the difference between the active zone database. by default. as the next steps should demonstrate. In this case. displayed in the output of step 7. Lab Guide 7-19 . This is because. Inc. VSAN 12): P4-MDS1# show zoneset active vsan 42 Step 10 Verify that the output displayed is similar to the output of step 7 above. The PWWNs of the devices should be similar. Step 9 Display the active zoneset for the other VSAN in your pod (the command example below is for Pod 1. Verify that the active zoneset for your VSAN includes four zones. VSAN 11): P4-MDS1# show zoneset active vsan 41 zoneset name Zoneset41 vsan 41 zone name ZoneS1D1 vsan 41 * fcid 0x1c0100 [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x1c00e8 [pwwn 21:00:00:04:cf:20:b7:e6] [disk1-p0] zone name ZoneS1D2 vsan 41 * fcid 0x1c0100 [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x1c00ef [pwwn 21:00:00:04:cf:3b:0f:3b] [disk2-p0] zone name ZoneS2D3 vsan 41 * fcid 0x1c0200 [pwwn 21:01:00:e0:8b:25:4f:27] [server2-p0] * fcid 0x1c00e4 [pwwn 21:00:00:04:cf:b5:ec:d4] [disk3-p0] zone name ZoneS2D4 vsan 41 * fcid 0x1c0200 [pwwn 21:01:00:e0:8b:25:4f:27] [server2-p0] * fcid 0x1c00e2 [pwwn 21:00:00:20:37:42:51:3c] [disk4-p0] Note: The * fcid indicates the devices are logged in to the fabric and visible in the VSAN. except this time without the keyword active. but different.

but the full zone database did not. Once you have confirmed that the full zone databases are identical on both switches. Confirm that the active zoneset propagated to the other switch. Skyline ATS. It can also be enabled or disabled globally or on per-VSAN basis later. Confirm that the full zone database propagated to the other switch. Full zoneset distribution overwrites previously configured zonesets on the other switch. one to each of the two MDS 9000 switches in your pod. Exercise Procedure Complete these steps: Step 1 Open two Command Line Interface windows. if needed or desired. and so that zoning can be performed from any switch in the fabric. by default. The default is disabled.2 . As demonstrated earlier. Device Manager or the CLI In this task. you could recover the full zone database from the active zone database using the following command (although you would lose any configured FC Alias definitions): # zone copy active-zoneset full-zoneset vsan XY Step 6 Step 7 Repeat step 3. you will agree that zoning an MDS 9000 family switch can be a fairly simple process using the Fabric Manager. edit the global configuration so that future zoneset activations will always propagate the full zone database. Return to the CLI window for your primary switch. Perform a one-time full zoneset distribution for your VSAN: (X refers to your pod number. the active zoneset is propagated to other switches in the fabric. but the full zone database is not. # show zoneset active # show zoneset Step 2 Step 3 Enter the above two commands in both CLI windows. 7-20 Implementing Cisco Storage Networking Solutions (ICSNS) v3. removing the full zone database created earlier. or the wrong VSAN. you will implement and verify full zoneset distribution from the CLI. Full zoneset distribution is enabled or disabled globally for all VSANs during the initial switch configuration (refer to Lab Exercise 2). you may distribute an empty full zone database to the other switch. Review the following commands used in the verification steps from Task 1.Task 2: Configuring Full Zoneset Distribution Hopefully. Many SAN administrators consider it a best practice to distribute the full zone database during zoneset activation. Inc. If you choose the wrong switch. If this were to happen. so that all switches in the fabric will have a consistent view of the zoning database. Do this for your VSAN on both switches: Copyright © 2008. The configuration can be done using Fabric Manager. Y refers to 1 if you are responsible for Px-MDS1 or 2 if you are responsible for Px-MDS2.) # zoneset distribute vsan XY Step 4 Step 5 Warning Be careful. Exercise Procedure 3.

(config)# zoneset distribute full vsan XY Step 8 End with CNTL/Z. Return to EXEC mode and check the status of the zones for your VSAN: P4-MDS1# show zone status vsan 41 VSAN: 41 default-zone: deny distribute: full Interop: default mode: basic merge-control: allow session: none hard-zoning: enabled broadcast: disabled Default zone: qos: none broadcast: disabled ronly: disabled Full Zoning Database : DB size: 380 bytes Zonesets:1 Zones:4 Aliases: 0 Active Zoning Database : DB size: 196 bytes Name: Zoneset41 Zonesets:1 Zones:4 Status: Zoneset distribution completed at 06:45:38 UTC Feb 29 2008 Copyright © 2008. Inc.# config Enter configuration commands. one per line. Lab Guide 7-21 . Skyline ATS.

and reconcile the problem. you will purposely create a zoning conflict. In this task. You will then activate the zoneset and bring up the ISL to demonstrate a failed zone merge. Inc. fc1/1 and fc1/2 between your two switches. Enable debugging for zone merge events: # debug zone merge events Step 3 Step 4 Wait until both switches are ready to proceed. You will then demonstrate a failed zone merge. Scroll back in the output and look for one or more Merge success messages. If only one switch has an active zoneset. On one switch. you must do this task at the same time.Task 3: Troubleshooting Zone Merge Failures Bringing up an ISL between two switches will initiate a zone merge process. Note: If your pod is split into two teams. add a bogus zone member to one of the zones in VSAN_X1 (where X is your pod number): (config)# zone name ZoneS1D1 vsan X1 (config-zone)# member fcid 0x123456 7-22 Implementing Cisco Storage Networking Solutions (ICSNS) v3. one per line. please wait for them to catch up. indicating normal zone merges. # config Enter configuration commands. and then re-enable the interfaces: (config-if)# no shutdown Step 6 Wait a few moments for debug output to appear. the zonesets will attempt to merge. Please check in with the other team. Step 5 Briefly observe the debug output. and then work together in lock step. that zoneset will propagate to the other switch. (config)# interface fc1/1-2 (config-if)# shutdown End with CNTL/Z. Skyline ATS. Step 8 On Px-MDS1 only. disable the ISL interfaces. (config-if)# shutdown (config-if)# exit Step 7 Note: With the interfaces disabled. Exercise Procedure Complete these steps: Step 1 Step 2 Open a Command Line Interface window on your switch. . you will now create a zone conflict. If both switches have active zonesets that are different.2 Copyright © 2008. Disable the interfaces again. If your team is working faster than the other team.

check zone status Step 12 Verify that the zoneset is active and the bogus member is present: (config)# do show zoneset active zoneset name Zoneset41 vsan 41 zone name ZoneS1D1 vsan 41 * fcid 0x1c0100 [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x1c00e8 [pwwn 21:00:00:04:cf:20:b7:e6] [disk1-p0] fcid 0x123456 Note: At this point. you have configured a classic zone conflict situation. (config)# do show interface brief -------------------------------------------------------------Interface Vsan Admin Mode Admin Trunk Mode -------------------------------------------------------------fc1/1 fc1/2 fc1/3 fc1/4 1 1 1 1 E E auto auto on on on on down down down down swl swl swl swl ----Status FCOT Oper Mode Step 11 Activate the zoneset for your VSAN (X refers to your pod number. Bring up the ISL interfaces (fc1/1 and fc1/2) that were previously shut down. Inc. The two switches have active zonesets containing zones with the same name.(config-zone)# exit Step 9 On Px-MDS2 only. so that the zonesets will not be propagated to the other switch when activated. Lab Guide 7-23 . add a bogus zone member to one of the zones in VSAN_X2 (where X is your pod number): (config)# zone name ZoneS1D1 vsan X2 (config-zone)# member fcid 0xabcdef (config-zone)# exit Step 10 Make certain the Status of the ISL links between your switches is down or notConnected. (config)# interface fc1/1-2 (config-if)# no shutdown Copyright © 2008. Y refers to 1 for Px-MDS1. Step 13 Step 14 Wait until both teams have completed the above steps. or 2 for Px-MDS2) (config)# zoneset activate name ZonesetXY vsan XY Zoneset activation initiated. Skyline ATS. but with different members.

as illustrated here.41-42) Trunk vsans (up) (1) Trunk vsans (isolated) (41-42) Trunk vsans (initializing) () Note: It is important to understand that a trunking ISL (EISL) can be up for one or more VSANs and isolated for others. ZDB_MISMATCH. Skyline ATS. indicating failed zone merges. Inc. Return to EXEC mode and disable all debugging messages: (config-if)# end # no debug all Step 16 Step 17 Display the state of one of your ISL interfaces: P4-MDS1# show int fc1/1 fc1/1 is trunking (Not all VSANs UP on the trunk) Hardware is Fibre Channel. SFP is short wave laser w/o OFC (SN) Port WWN is 20:01:00:0d:ec:08:b4:80 Peer port WWN is 20:01:00:0d:ec:04:22:80 Admin port mode is auto. Scroll back in the output and look for one or more messages containing ISOLATE.2 Copyright © 2008. For example: # show interface fc1/1 trunk vsan 41-42 fc1/1 is trunking Vsan 41 is down (Isolation due to zone merge failure) Vsan 42 is down (Isolation due to zone merge failure) 7-24 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 15 Wait a few moments for debug output to appear. or ZS_MERGE_FAILED. . Step 18 Whenever you see isolation on an EISL. trunk mode is on snmp link state traps are enabled Port mode is TE Port vsan is 1 Speed is 2 Gbps Transmit B2B Credit is 255 Receive B2B Credit is 255 Receive data field Size is 2112 Beacon is turned off Trunk vsans (admin allowed and active) (1. it is a good idea to look more deeply into the problem.

Enter the VSAN ID for your VSAN. Step 21 Verify that the two switches in your pod are listed in the Switch 1 and Switch 2 fields. Lab Guide 7-25 . Click Clear. Skyline ATS. Click Close. Click the Analyze button. Click Analyze.Step 19 Step 20 Bring up a Fabric Manager connection to your switch. Step 22 Observe the output and verify the problem described is accurate based on the conflict you created above. Step 23 Step 24 Step 25 Copyright © 2008. Select Merge Analysis from the Zone menu. Inc. Change the VSAN ID to the other VSAN in your pod.

Skyline ATS. 7-26 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Step 29 Click Close.2 Copyright © 2008.0. . you should “import” the active zoneset to your switch. Note: The recovery method will depend upon which switch has the “problem” for that VSAN. to resolve the problem. Step 27 Leave the Import Active Zoneset radio button selected. Step 28 Wait for a Finished message to appear in the lower left corner of the window. Note: The problem for VSAN_X1 was created on Px-MDS1. Inc. Likewise the problem for VSAN_X2 was created in Px-MDS2.Step 26 Select Merge Fail Recovery from the Zone menu. Note: There is a bug in SAN-OS 3. as opposed to “export” the active zoneset from your switch. Select your VSAN in the Vsan field. Therefore. Click OK. Select your switch in the Switch field. Click on the … button and select the channel 100.2 that prevents the Zone Merge Recovery utility from working properly.

Step 30

Select the Physical tab in the tree view. Click Copy Configuration.

Step 31

Select only the checkbox for your switch. Click the Apply Changes button. Wait for the Success message.

That concludes this lab exercise.

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

7-27

Appendix A – Sample Lab Configuration File (partial)
The following output has been edited to include the portions of the configuration file most relevant to this lab. P4-MDS1# show running-config
Building Configuration ... device-alias database device-alias name disk1-p0 pwwn 22:00:00:04:cf:ac:7b:73 device-alias name disk1-p1 pwwn 21:00:00:04:cf:ac:7b:73 device-alias name disk2-p0 pwwn 22:00:00:04:cf:ac:e3:3b device-alias name disk2-p1 pwwn 21:00:00:04:cf:ac:e3:3b device-alias name disk3-p0 pwwn 22:00:00:04:cf:b5:ec:ec device-alias name disk3-p1 pwwn 21:00:00:04:cf:b5:ec:ec device-alias name disk4-p0 pwwn 22:00:00:04:cf:b5:ed:70 device-alias name disk4-p1 pwwn 21:00:00:04:cf:b5:ed:70 device-alias name server1-p0 pwwn 21:01:00:e0:8b:23:d1:24 device-alias name server1-p1 pwwn 21:00:00:e0:8b:03:d1:24 device-alias name server2-p0 pwwn 21:01:00:e0:8b:23:c3:24 device-alias name server2-p1 pwwn 21:00:00:e0:8b:03:c3:24 device-alias commit zoneset distribute full vsan 41 zone name ZoneS1D1 vsan 11 member pwwn 21:01:00:e0:8b:23:d1:24 member pwwn 22:00:00:04:cf:ac:7b:73

zone name ZoneS1D2 vsan 41 member pwwn 21:01:00:e0:8b:23:d1:24 member pwwn 22:00:00:04:cf:ac:e3:3b zone name ZoneS2D3 vsan 41 member pwwn 21:01:00:e0:8b:23:c3:24 member pwwn 22:00:00:04:cf:b5:ec:ec zone name ZoneS2D4 vsan 41 member pwwn 21:01:00:e0:8b:23:c3:24 member pwwn 22:00:00:04:cf:b5:ed:70 zone name ZoneS1D1 vsan 42 member pwwn 21:00:00:e0:8b:03:d1:24 member pwwn 21:00:00:04:cf:ac:7b:73 zone name ZoneS1D2 vsan 42 member pwwn 21:00:00:e0:8b:03:d1:24 member pwwn 21:00:00:04:cf:ac:e3:3b zone name ZoneS2D3 vsan 42 member pwwn 21:00:00:e0:8b:03:c3:24 member pwwn 21:00:00:04:cf:b5:ec:ec zone name ZoneS2D4 vsan 42 member pwwn 21:00:00:e0:8b:03:c3:24 member pwwn 21:00:00:04:cf:b5:ed:70 zoneset name Zoneset11 vsan 41 member ZoneS1D1
7-28 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008, Skyline ATS, Inc.

member ZoneS1D2 member ZoneS2D3 member ZoneS2D4 zoneset activate name Zoneset41 vsan 41 zoneset name Zoneset12 vsan 42 member ZoneS1D1 member ZoneS1D2 member ZoneS2D3 member ZoneS2D4 zoneset activate name Zoneset42 vsan 42

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

7-29

7-30

Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

you will be able to meet these objectives:  Implement a multi-switch IVR configuration with a transit VSAN using Fabric Manager Required Resources These are the resources and equipment required to complete this exercise:     Two MDS 9000 switches with at least one ISL between them Enterprise licenses installed on the two MDS 9000 switches At least one Fibre Channel-attached Windows 2000 server attached to both switches One FC-AL JBOD attached to both switches . you will implement. After completing this exercise. Exercise Objective In this exercise. and distribute IVR configurations. merge.Lab Exercise 8: Implementing IVR Complete this lab exercise to practice what you learned in the related lesson.

Skyline ATS. activate. and verify a multi-switch IVR topology. Management has asked you to selectively allow two servers to access disk located in different VSANs. However. Your company has grown and so has your SAN. you are using a direct Fibre Channel link between the two switches. Visual Objective The figure illustrates what you will accomplish in this task. the link forming the transit VSAN could just as easily be an FCIP tunnel. 8-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Note: In this lab.Task 1: Transit IVR Configuration In this task you will use the Fabric Manager IVR Wizard to configure. .2 Copyright © 2008. Inc.

41.42) Trunk vsans (up) Trunk vsans (isolated) Trunk vsans (initializing) (1.Exercise Procedure Caution: If you are working in teams. P4-MDS1# show interface fc1/1 | include vsans Trunk vsans (admin allowed and active) (1.41. Verify that you see two switches in the topology view. Copyright © 2008. Skyline ATS. Inc. Lab Guide 8-3 . X1 and X2 (here 41 and 42). make sure both teams are finished with the preceding tasks before going any further.42) () () Step 1 Step 2 Open the Fabric Manager. each connected to two servers and four disks. Verify that the EISL is still up and trunking for VSANs 1. Step 1 Step 2 Log in to the CLI using the username admin and the password 1234qwer.

In the VSAN Id column you should see six entries for VSAN X1. Observe the table in the Information pane. six entries for VSAN X2. If you are working in teams. Step 5 Click the IVR Zone Wizard button in the toolbar. 8-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. the team working on the MDS1 must finish using the wizard before the team working on MDS2 begins. Inc.2 Copyright © 2008.Step 3 Step 4 Choose the End Devices folder in the Physical Attributes pane. . Skyline ATS. This wizard must be used serially. you will invoke the wizard twice. Step 6 Click Yes to implement IVR in NAT mode. Caution: In the following steps you will configure IVR using the IVR Zone Wizard. If you are working alone.

Skyline ATS. X1. Inc. and X2 into the Selected window. Copyright © 2008. Lab Guide 8-5 .Step 7 Select your fabric and click Next. Step 8 Move VSAN’s 1. Click Next.

8-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. 1.2 Copyright © 2008. Inc. it must also traverse VSANs X2. 1. and X1. Similarly.Step 9 Observe the following diagram. and X1. Notice that for server1-p0 to reach disk2-p1. Skyline ATS. . it must traverse VSANs X2. for server2-p1 to reach disk1-p0.

Skyline ATS. Copyright © 2008. If you are working on the MDS2. Click Add to move them to the Selected window.   If you are working on the MDS1. Lab Guide 8-7 . choose server2-p1 and disk1-p0. Step 11 Ensure that both MDS1 and MDS2 are checked for IVR NAT. choose server1-p0 and disk2-p1. Then click Next. Inc.Step 10 Locate and choose the appropriate devices in the Available window based on their device alias names.

Click Next. Inc. set the zone name to IvrZoneMDS2.Step 12   Change the zone name: If you are working on the MDS1. set the zone name to IvrZoneMDS1. Review the action steps then click Finish. If you are working on the MDS2. 8-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. .2 Copyright © 2008. Step 13 Step 14 Accept the default zoneset name. Skyline ATS.

Step 17 Click Close. Inc.Step 15 Click Continue Activation. Skyline ATS. Copyright © 2008. Lab Guide 8-9 . Step 16 View the progress indicator and wait for Success to appear in the lower left.

Verify that the server1 and disk2 icons are highlighted in the topology view and that the correct names appear in the table in the Information pane. Step 18 Step 19 Repeat Step 2 for IvrZoneMDS2. Access the switch CLI using the username admin and the password 1234qwer.2 Copyright © 2008. Verify that the server1 -. . each having two members preceded by * pwwn. Click No when prompted to save changes. Verify that there is an IVR zoneset active with two zones. Step 20 Step 21 Step 22 P4-MDS1# show ivr zoneset active zoneset name IVR_Zoneset1 zone name IvrZoneMDS1 * pwwn 21:01:00:e0:8b:23:d3:24 * pwwn 22:00:00:04:cf:3b:0f:3b zone name IvrZoneMDS2 * pwwn 21:00:00:e0:8b:05:4f:27 * pwwn 21:00:00:04:cf:20:b7:e6 vsan 42 autonomous-fabric-id 1 vsan 41 autonomous-fabric-id 1 [server2-p1] [disk1-p0] vsan 41 autonomous-fabric-id 1 vsan 42 autonomous-fabric-id 1 [server1-p0] [disk2-p1] 8-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3.disk2 (IVRZoneMDS1) and server2 – disk 1 (IVRZoneMDS2) icons are highlighted in the topology view and that the correct names appear in the table in the Information pane. Close Fabric Manager. Step 1 Expand the SAN > Fabric > All VSANs > IVR > IvrZoneSet1 folders in the Logical Domains pane. Inc.Exercise Verification Complete these steps to verify that you have correctly configured IVR. Skyline ATS. Choose IvrZoneMDS1.

one in VSAN X1 and one in VSAN X2. each having two IVR zones with two members preceded by * fcid. Inc. Skyline ATS.Step 23 Verify that there are two ordinary zonesets active. P4-MDS1# show zoneset active zoneset name Zoneset41 vsan 41 zone name ZoneS1D1 vsan 41 * fcid 0x1c0100 [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x1c00e8 [pwwn 21:00:00:04:cf:20:b7:e6] [disk1-p0] zone name ZoneS1D2 vsan 41 * fcid 0x1c0100 [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x1c00ef [pwwn 21:00:00:04:cf:3b:0f:3b] [disk2-p0] zone name ZoneS2D3 vsan 41 * fcid 0x1c0200 [pwwn 21:01:00:e0:8b:25:4f:27] [server2-p0] * fcid 0x1c00e4 [pwwn 21:00:00:04:cf:b5:ec:d4] [disk3-p0] zone name ZoneS2D4 vsan 41 * fcid 0x1c0200 [pwwn 21:01:00:e0:8b:25:4f:27] [server2-p0] * fcid 0x1c00e2 [pwwn 21:00:00:20:37:42:51:3c] [disk4-p0] zone name IVRZ_IvrZoneMDS1 vsan 41 * fcid 0x1c0100 [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x273e39 [pwwn 22:00:00:04:cf:3b:0f:3b] [disk2-p1] zone name IVRZ_IvrZoneMDS2 vsan 41 * fcid 0x272965 [pwwn 21:00:00:e0:8b:05:4f:27] [server2-p1] * fcid 0x1c00e8 [pwwn 21:00:00:04:cf:20:b7:e6] [disk1-p0] zoneset name Zoneset42 vsan 42 zone name ZoneS1D1 vsan 42 * fcid 0x480200 [pwwn 21:00:00:e0:8b:03:d3:24] [server1-p1] * fcid 0x4800e8 [pwwn 22:00:00:04:cf:20:b7:e6] [disk1-p1] zone name ZoneS1D2 vsan 42 * fcid 0x480200 [pwwn 21:00:00:e0:8b:03:d3:24] [server1-p1] * fcid 0x4800ef [pwwn 22:00:00:04:cf:3b:0f:3b] [disk2-p1] Copyright © 2008. Lab Guide 8-11 .

2 Copyright © 2008. That concludes this lab exercise.zone name ZoneS2D3 vsan 42 * fcid 0x480100 [pwwn 21:00:00:e0:8b:05:4f:27] [server2-p1] * fcid 0x4800e4 [pwwn 22:00:00:04:cf:b5:ec:d4] [disk3-p1] zone name ZoneS2D4 vsan 42 * fcid 0x480100 [pwwn 21:00:00:e0:8b:05:4f:27] [server2-p1] * fcid 0x4800e2 [pwwn 22:00:00:20:37:42:51:3c] [disk4-p1] zone name IVRZ_IvrZoneMDS1 vsan 42 * fcid 0x10270a [pwwn 21:01:00:e0:8b:23:d3:24] [server1-p0] * fcid 0x4800ef [pwwn 22:00:00:04:cf:3b:0f:3b] [disk2-p1] zone name IVRZ_IvrZoneMDS2 vsan 42 * fcid 0x480100 [pwwn 21:00:00:e0:8b:05:4f:27] [server2-p1] * fcid 0x10e8b2 [pwwn 21:00:00:04:cf:20:b7:e6] [disk1-p0] You have successfully completed this lab exercise when you have configured and verified a multi-switch IVR configuration using a transit VSAN. . 8-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS. Inc.

Appendix A: Final Configuration The following is a partial output of the show run command from P4-MDS1 after completing the final task. Lab Guide 8-13 . Skyline ATS. P4-MDS1# show running-config ivr enable ivr distribute ivr nat ivr vsan-topology auto zoneset distribute full vsan 41 zone name ZoneS1D1 vsan 41 member pwwn 21:01:00:e0:8b:23:d1:24 member pwwn 22:00:00:04:cf:ac:7b:73 member fcid 0x123456 zone name ZoneS1D2 vsan 41 member pwwn 21:01:00:e0:8b:23:d1:24 member pwwn 22:00:00:04:cf:ac:e3:3b zone name ZoneS2D3 vsan 41 member pwwn 21:01:00:e0:8b:23:c3:24 member pwwn 22:00:00:04:cf:b5:ec:ec zone name ZoneS2D4 vsan 41 member pwwn 21:01:00:e0:8b:23:c3:24 member pwwn 22:00:00:04:cf:b5:ed:70 zone name ZoneSet41 vsan 41 zone name ZoneS1D1 vsan 42 member pwwn 21:00:00:e0:8b:03:d1:24 member pwwn 21:00:00:04:cf:ac:7b:73 zone name ZoneS1D2 vsan 42 member pwwn 21:00:00:e0:8b:03:d1:24 member pwwn 21:00:00:04:cf:ac:e3:3b zone name ZoneS2D3 vsan 42 member pwwn 21:00:00:e0:8b:03:c3:24 member pwwn 21:00:00:04:cf:b5:ec:ec zone name ZoneS2D4 vsan 42 member pwwn 21:00:00:e0:8b:03:c3:24 member pwwn 21:00:00:04:cf:b5:ed:70 zoneset name ZoneSet41 vsan 41 member ZoneS1D1 member ZoneS1D2 member ZoneS2D3 member ZoneS2D4 zoneset activate name ZoneSetMDS1 vsan 41 zoneset name ZoneSet42 vsan 42 member ZoneS1D1 member ZoneS1D2 member ZoneS2D3 member ZoneS2D4 zoneset activate name ZoneSet42 vsan 42 Copyright © 2008. Inc.

ivr zone name IvrZoneMDS1 member pwwn 21:01:00:e0:8b:23:d1:24 member pwwn 21:00:00:04:cf:ac:e3:3b ivr zone name IvrZoneMDS2 member pwwn 21:00:00:e0:8b:03:c3:24 member pwwn 22:00:00:04:cf:ac:7b:73 ivr zoneset name IvrZoneSet41 member IvrZoneMDS1 member IvrZoneMDS2 ivr zoneset activate name IvrZoneSet41 force ivr commit vsan 41 vsan 42 vsan 42 vsan 41 8-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Inc. Skyline ATS.2 Copyright © 2008. .

you will be able to configure Gigabit Ethernet interfaces. Scenario Your customer needs to provide SAN extension connectivity between two sites. you will configure an FCIP environment using the IP Services Module.Lab Exercise 9: Basic FCIP Configuration Exercise Objective In this exercise. Servers at one site will access storage at the other site. Visual Objective The figure illustrates what you will accomplish in this exercise. You must configure primary and failover tunnels. Required Resources These are the resources and equipment required to complete this exercise:   Two modular MDS 9000 family switches Two IPS-8 IP Services modules with GigE connectivity between them . FCIP Profiles and FCIP Tunnels between two MDS 9000 family switches with IP Services modules. After completing this exercise.

Refer to the following table. the team using Server 1 will configure FCIP tunnel a.2.2 Copyright © 2008.22 gig2/3 10. Core1 gig2/1 10. Exercise Procedure 1: Configure Gigabit Ethernet Interfaces Follow these steps to configure the Gigabit Ethernet interfaces to be used for the FCIP tunnels: Step 1 Login to a Windows 2000 server in your pod.2.11 gig2/4 10.1. If you are working in teams.4.11 gig2/6 10.21 gig2/8 10.21 gig2/4 10.1.12 gig2/5 10. and the team using Server 2 will configure FCIP tunnel b.1. Skyline ATS.12 gig2/7 10.1.1. one team will use Server 1 and the other team will use Server 2.21 gig2/6 10.4.2.3.Task 1: Configure Gigabit Ethernet Interfaces In this task.1.21 gig2/2 10.11 gig2/2 10.1. you will configure both FCIP tunnels a and b.3.3.1.4.1. use Server 1.11 gig2/8 10.22 gig2/7 10. You must configure the appropriate GigE interfaces on both MDS switches.1. If you are working in teams.1.3.1. .2.1.1. If you are working alone in a pod.12 gig2/3 10.1.12 Core2 gig2/1 10.22 FCIP Profile ID 1 2 3 4 5 6 7 8 Step 2 POD / TUNNEL Pod 1 FCIP a Pod 1 FCIP b Pod 2 FCIP a Pod 2 FCIP b Pod 3 FCIP a Pod 3 FCIP b Pod 4 FCIP a Pod 4 FCIP b Step 3 Locate the row for your tunnel. If you are working alone in a pod.1.22 gig2/5 10. Make certain you are confident which of the GigE ports are yours before proceeding. Step 4 9-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Inc.1. you will configure Gigabit Ethernet interfaces.1.1.1. Click on the Device Manager icon on your assigned W2K desktop.4.

Skyline ATS.196).0. Right-click and select Configure. Lab Guide 9-3 . Copyright © 2008.Step 5 Open a Device Manager connection to Core1 (192.168. Inc. Step 6 Locate your GigE port on line card 2.

Click the IP Address(es) button. Skyline ATS.Step 7 Enter a Description for your port. 9-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2 Copyright © 2008. Set the Admin mode to up. . Inc. Step 8 Step 9 Click Apply.

. Step 12 Verify that the correct ip address and net mask have been added. Inc. Lab Guide 9-5 . Login with the username admin and the password 1234qwer. using a 24-bit netmask. Step 13 Repeats steps 4-9 for Core2. The ports for each pod are assigned to their own VLAN. using a 24-bit netmask as shown. Select Command Line Interface from the Device menu of either switch. Note: The GigE ports are connected to a Catalyst 6500 Ethernet switch. Step 11 Enter the appropriate IP address for your Core1 GigE port from the table above. Step 14 Copyright © 2008.Click Create and then Close.Step 10 Click the Create button. Skyline ATS. Click Close. Be sure to enter the appropriate IP address for your Core2 GigE port from the table above.

3 packets received.3 ms 64 bytes from 10.static Default gateway is 192.3 ms --.0.10.Trans-Bridge.11/24 MTU 1500 bytes Port mode is IPS Speed is 1 Gbps .4 ms Note: In some earlier releases of SAN-OS. Inc.3 msec shown). Skyline ATS. FCIP and/or iSCSI must be explicitly enabled before a ping will succeed on the GigE interfaces.1.1.connected.4 ms 64 bytes from 10. 9-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0. .168.Switch.1.0da8 Internet address is 10.4.168.4. GigabitEthernet2/7 Step 17 View the CDP neighbor of your GigE interface. B .0/24 is directly connected.1.Source-Route-Bridge S .1. Make a mental note of the average round trip latency (0.3/0. address is 000e.Repeater Device ID FOX07310362(CAT_ Step 18 Local Intrfce Hldtme 95 Capability R B I r Platform WS-C6503 Port 2/7 Verify that you can ping the GigE port on the opposite switch. .21: icmp_seq=2 ttl=255 time=0.IGMP.254 C 192.38c6.4. 0% packet loss round-trip min/avg/max = 0.4.0/24 is directly connected.Step 15 Check the status of your GigE port.21 PING 10.1. Press Ctrl-c to terminate the ping. Core1# show cdp neighbors interface gigabitethernet 2/7 Capability Codes: R .4.21: icmp_seq=0 ttl=255 time=0. Verify that you see an entry for your GigE interfaces: Core1# show ip route Codes: C .1.3/0. r . Core1# ping 10.Host.1.4.4.21 ping statistics --3 packets transmitted. Verify that the interface is up and that the IP address is correct (pod 1 example shown): Core1# show interface gigabitethernet 2/7 GigabitEthernet2/7 is up Port description is GigE Port for FCIP Tunnel A Hardware is GigabitEthernet. I .4.4.21): 56 data bytes 64 bytes from 10. T . H .Router.21 (10.1.21: icmp_seq=1 ttl=255 time=0. Step 16 View the IP routing table. mgmt0 C 10. .2 Copyright © 2008. S .

Lab Guide 9-7 . Copyright © 2008. If the Status column for the FCIP feature indicates disabled (as shown below). Select enable in the Action field. If the FCIP feature is already enabled. Skyline ATS.197). skip ahead to the next step. Activity Procedure Each team should complete the following steps on both MDS CORE switches to configure their gigE2/x port for the FCIP profile.168.Task 2: Configure an FCIP Profile In this task you will configure an FCIP profile. Select Feature Control from the Admin menu. then you are the first team to reach this point.0. and then click Apply. Repeat the steps 1-3 for CORE2 (192. Step 1 Step 2 Return to the Device Manager for CORE1. Step 3 Step 4 Click Close. Inc.

Skyline ATS. click the Profiles tab. Inc. 9-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Step 6 In the FCIP dialog box.Step 5 From the CORE1 Device Manager select IP -> FCIP. . and then click Create.2 Copyright © 2008.

Step 7

In the Create FCIP Profiles dialog box, configure the following FCIP Profile parameters: Profile ID: (see chart in Task 1 for value) IP Address: (see chart in Task 1 for value) Leave all other settings at their default values. Click Create and then click Close..

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

9-9

Step 8

Your FCIP profile configuration should look similar to the following:

Step 9 Step 10 Step 11

Close the FCIP dialog Repeat steps 5-9 to configure an FCIP profile on CORE2. Display the details for your FCIP Profile. Be sure to use the Profile ID you recorded above. Verify that the correct GigE interface and IP address are displayed.

Core1# show fcip profile 1 FCIP Profile 7 Internet Address is 10.1.7.11 Listen Port is 3225 TCP parameters SACK is enabled PMTU discovery is enabled, reset timeout is 3600 sec Keep alive is 60 sec Minimum retransmission timeout is 200 ms Maximum number of re-transmissions is 4 Send buffer size is 0 KB Maximum allowed bandwidth is 1000000 kbps Minimum available bandwidth is 500000 kbps Estimated round trip time is 1000 usec Congestion window monitoring is enabled, burst size is 50 KB Auto jitter is enabled (interface GigabitEthernet2/7)

9-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

Step 12

Verify that the Status of the SAN Extension Over IP license is in use:

Lic Status Expiry Date Comments Count ------------------------------------------------------------------FM_SERVER_PKG Yes Unused never MAINFRAME_PKG No Unused ENTERPRISE_PKG Yes Unused never DMM_FOR_SSM_PKG No 0 Unused SAN_EXTN_OVER_IP Yes 1 Unused never PORT_ACTIVATION_PKG No 0 Unused SME_FOR_IPS_184_PKG No 0 Unused SAN_EXTN_OVER_IP_18_4 No 0 Unused SAN_EXTN_OVER_IP_IPS2 No 0 Unused SAN_EXTN_OVER_IP_IPS4 No 0 Unused 10G_PORT_ACTIVATION_PKG No 0 Unused STORAGE_SERVICES_ENABLER_PKG No 0 Unused -

Core1# show license usage Feature Ins

Activity Verification
You have completed this task when you attain these results:  FCIP profile parameters have been correctly configured

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

9-11

Task 3: Create an FCIP Tunnel
In this task, you will create an FCIP tunnel.

Activity Procedure
Each team should complete the following steps on Core1 to configure their FCIP tunnel.
Step 1

From the CLI, enter configuration mode and execute the following commands to create the FCIP interface, and associate it with the FCIP profile you have created.

# config (config)# interface fcip x (x is your fcip profile number) (config-if)# use-profile x (config-if)# peer-info ipaddr 10.1.x.y (see table in Task 1 for peer ip address) (config-if)# no shutdown (config-if)# end
Step 2 Step 3

Repeat Step 1 to configure the your FCIP interface on Core2. Display the status of the FCIP tunnel.

# show interface fcip 1 fcip1 is trunking Hardware is GigabitEthernet Port WWN is 20:42:00:0d:ec:20:6f:80 Peer port WWN is 20:42:00:0d:ec:0c:fb:40 Admin port mode is auto, trunk mode is on snmp traps are enabled Port mode is TE Port vsan is 1 Speed is 1 Gbps Trunk vsans (admin allowed and active) (1) Trunk vsans (up) Trunk vsans (isolated) Trunk vsans (initializing) Using Profile id 1 Peer Information Peer Internet address is 10.1.1.21 and port is 3225 Write acceleration mode is configured off Tape acceleration mode is configured off Tape Accelerator flow control buffer size is automatic Ficon Tape acceleration configured off for all vsans IP Compression is disabled (1) () ()

(interface GigabitEthernet2/1)

9-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

Slow start threshold: 112 KB Current Send Buffer Size: 33 KB.1.21:3225 2 Attempts for active connections. Requested Send Buffer Size: 0 KB CWM Burst Size: 50 KB 5 minutes input rate 0 bits/sec. 22960 bytes 0 Class 2/3 frames input.1.Special Frame is disabled Maximum number of TCP connections is 2 Time Stamp is disabled QOS control code point is 0 QOS data code point is 0 B-port mode disabled TCP Connection Information 2 Active TCP connections Control connection: Local 10. Remote 10. Scale: 5 Peer receive window: Current: 2047 KB.21:3225 Data connection: Local 10. Variance: 0 Jitter: 150 us Advertized window: Current: 33 KB. Scale: 5 Congestion window: Current: 14 KB. Maximum: 33 KB.1. 0 frames/sec 184 frames input. 0 bytes 0 Error frames Step 4 Check the default VSAN membership of the FCIP interfaces: Core1# show vsan membership vsan 1 interfaces: fc1/1 fc1/9 fcip1 fc1/2 fc1/10 fcip2 fc1/3 fc1/11 fc1/4 fc1/12 fc1/5 fc1/13 fc1/6 fc1/14 fc1/7 fc1/15 fc1/8 fc1/16 Copyright © 2008. 0 bytes/sec. Skyline ATS. 0 bytes/sec.11:65534. 22960 bytes 184 Class F frames input. Inc. 0 bytes 0 Reass frames 0 Error frames timestamp error 0 184 frames output.1.11:65532. 0 frames/sec 5 minutes output rate 0 bits/sec. Lab Guide 9-13 . 21844 bytes 0 Class 2/3 frames output. 0 close of connections TCP Parameters Path MTU 1500 bytes Current retransmission timeout is 200 ms Round trip time: Smoothed 0 ms. 21844 bytes 184 Class F frames output. Remote 10.1. Maximum: 2047 KB.1.1.1.

.2 Copyright © 2008. Skyline ATS. iSCSI) built upon them are members of VSANs.Note: Unlike Fibre Channel interfaces. however. Inc. 9-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3. the logical interfaces (FCIP. Gigabit Ethernet interfaces are not members of VSANs.

Task 4: Create an FCIP PortChannel
In this task, you will create a PortChannel that contains two FCIP tunnels.

Activity Procedure
Team up with the other students who created the other FCIP tunnel from your pod.
Step 5 Step 6

Open Fabric Manager and connect to CORE1. From the Fabric Manager tool bar, click the Port Channel icon to launch the Port Channel Wizard

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

9-15

Step 7

In the 1 of 3: Select Switch Pair dialog box, choose the CORE1 – CORE2 pair and click Next to continue. You should see (2 ISLs) next to the switch pair.

9-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

Step 8

In the 2 of 3: Select ISLs dialog box, verify both of your FCIP interface pairs are in the Selected pane.

Step 9

Click Next to continue.

Copyright © 2008, Skyline ATS, Inc.

Lab Guide

9-17

Step 10

In the 3 of 3: Create Port Channel dialog box, configure the following settings: • • • In the Trunk Mode field click the trunk radio button to enable trunk mode In the VSAN List field, accept the default value (1-4093) Leave the other parameters in this dialog box at their default values

Step 11 Step 12

Click Finish. A FC Port Channel Wizard warning dialog box appears, requesting confirmation to continue. Click Yes to create the PortChannel.

9-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3.2

Copyright © 2008, Skyline ATS, Inc.

0 bytes/sec.Activity Verification Complete the following steps to verify your configuration. trunk mode is on snmp traps are enabled Port mode is TE Port vsan is 1 Speed is 2 Gbps Trunk vsans (admin allowed and active) (1) Trunk vsans (up) (1) Trunk vsans (isolated) () Trunk vsans (initializing) () 5 minutes input rate 0 bits/sec. 27276 bytes 218 Class F frames input. Inc. 0 bytes 0 Reass frames 0 Error frames timestamp error 0 218 frames output. Your display should resemble the following: CORE1# show port-channel database port-channel 1 Administrative channel mode is active Operational channel mode is active Last membership update succeeded First operational port is fcip2 2 ports in total. Skyline ATS. 0 frames/sec 5 minutes output rate 0 bits/sec. 25508 bytes 218 Class F frames output. display the PortChannel interfaces to verify that the PortChannel is operational. 27276 bytes 0 Class 2/3 frames input. 0 bytes Display the PortChannel database information. CORE1# show interface port-channel 1 port-channel 1 is trunking Port description is To CORE2 Hardware is Fibre Channel Port WWN is 24:01:00:0d:ec:20:6f:80 Admin port mode is E. 0 bytes/sec. Lab Guide 9-19 . 0 frames/sec 218 frames input. Core1# copy run start Core2# copy run start That concludes this lab exercise Copyright © 2008. Step 13 From the CLI on both switches. 25508 bytes 0 Class 2/3 frames output. 2 ports up Ports: fcip7 [up] * Fcip8 [up] Step 15 Step 14 Save your configuration on both Core1 and Core2.

255.1.21 interface fcip2 no shutdown use-profile 2 peer-info ipaddr 10.1.1.255. Core1# show running-config Building Configuration .0 switchport description GigE Port for FCIP Tunnel A switchport mtu 1500 no shutdown interface GigabitEthernet2/2 ip address 10.1.Appendix A – Sample Lab Configuration File (partial) The following output has been edited to include the portions of the configuration file most relevant to this lab.0 switchport description GigE Port for FCIP Tunnel B switchport mtu 1500 no shutdown 9-20 Implementing Cisco Storage Networking Solutions (ICSNS) v3. fcip enable fcip profile 1 ip address 10. .12 tcp max-bandwidth-mbps 1000 min-available-bandwidth-mbps 1000 round-trip-time-ms 1 interface fcip1 no shutdown use-profile 1 peer-info ipaddr 10.. Inc.22 interface GigabitEthernet2/1 ip address 10.1.1.12 255.1.255.1.1.1.1.11 tcp max-bandwidth-mbps 1000 min-available-bandwidth-mbps 1000 round-trip-time-ms 1 fcip profile 2 ip address 10.11 255.1.255.. Skyline ATS. This sample is taken from Core1 after configuring two FCIP tunnels.2 Copyright © 2008.

Lab Exercise 10: Tuning FCIP Performance Exercise Objective In this exercise. Required Resources These are the resources and equipment required to complete this exercise:   Two modular MDS 9000 family switches Two IPS-8 IP Services modules with GigE connectivity between them . Servers at one site will access storage at the other site. Scenario Your customer needs to provide SAN extension connectivity between two sites. FCIP Profiles and FCIP Tunnels between two MDS 9000 family switches with IP Services modules. After completing this exercise. Visual Objective The figure illustrates what you will accomplish in this exercise. you will configure an FCIP environment using the IP Services Module. All students working an a pod will need to work together to complete this exercise. You must configure primary and failover tunnels. you will be able to configure Gigabit Ethernet interfaces.

Open the Fabric Manager from your Windows Desktop. Skyline ATS. 10-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. In the Physical Attributes pane select ISLs -> FCIP. . Inc.Task 1: Tune Down TCP Parameters on your FCIP Tunnels In this task. you will reconfigure your FCIP Tunnels using the Fabric manager. Exercise Procedure 1: Configure Gigabit Ethernet Interfaces Follow these steps to modify your FCIP tunnel configuration.2 Copyright © 2008. Step 1 Step 2 Step 3 Login to a Windows 2000 server in your pod. Click on the Profiles tab in the table window.

Inc. so enter 100000) Min Bandwidth 5Mb (The field is in Kb. Copyright © 2008. Lab Guide 10-3 . . the third octet corresponds to your pod number.Step 4 Your pod’s FCIP tunnel links can be identified by their IP address. For both ends of both links in the first link in your tunnel change the following parameters:    Max Bandwidth 100Mb (The field is in Kb. so enter 5000) Estimated RTT 200000 us Then click the Apply Changes button. Skyline ATS.

4. 10-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.x.364 ms): ____________ A microsecond (us) is 10-6 of a second.4.Activity Verification Complete the following steps to verify your configuration on both switches.340/0.21) 56(84) bytes of data. Inc.e.21 (10.21: icmp_seq=4 ttl=255 time=0.1.4. .1. .X.1. CORE1# show fcip profile ----------------------------------------------------------------ProfileId Ipaddr TcpPort ----------------------------------------------------------------7 10.21).364/0.10. 0% packet loss.4.036 ms Note: Note your average time (here 0.1. CORE1# show fcip profile 7 FCIP Profile 1 Internet Address is 10. Step 1 Display your first FCIP profile and determine the profile id that corresponds to your first FCIP tunnel (i.1.340 ms ms ms ms --.348 64 bytes from 10.1.1. (X is your pod number) CORE1# ping 10. time 4017ms rtt min/avg/max/mdev = 0. reset timeout is 3600 sec Keep alive is 60 sec Minimum retransmission timeout is 200 ms Maximum number of re-transmissions is 4 Send buffer size is 0 KB Maximum allowed bandwidth is 100000 kbps Minimum available bandwidth is 5000 kbps Estimated round trip time is 200000 usec .1.4.1.11 3225 8 10.4. the one that has an address 10.1.21: icmp_seq=3 ttl=255 time=0.1.4.11 (interface GigabitEthernet2/7) Tunnels Using this Profile: fcip2 Listen Port is 3225 TCP parameters SACK is enabled PMTU discovery is enabled..413 64 bytes from 10.4.12 3225 Step 2 Display the TCP parameters of the FCIP profile. 64 bytes from 10.1.11 or 10.21: icmp_seq=2 ttl=255 time=0. a millisecond is 10-3 of a second.21 PING 10.x.21: icmp_seq=5 ttl=255 time=0.413/0. .1.1.1. Skyline ATS.358 64 bytes from 10. 5 received. CORE1# show interface brief | include fcip on trunking TE 1 GigabitEthernet2/7 on trunking TE 2 GigabitEthernet2/8 Fcip7 Fcip8 1 1 E E port-channel 1 port-channel 1 Step 4 Ping the peer switch’s gigE interface and note the disparity between the actual and configured RTT. Step 3 Display the status of the FCIP tunnels and note the fcip interface numbers that correspond to your GigE ports.21 ping statistics --5 packets transmitted.2 Copyright © 2008.

3 12288 Jan 01 00:02:44 1980 lost+found/ 2590 May 13 22:54:39 2007 testfile Step 2 Step 3 Open the Device Manager for CORE2.2. # copy running-config bootflash:testfile CORE2# dir bootflash: 14651392 Jan 23 03:45:17 2007 9500-kickstart-3.2. Skyline ATS. Inc.3 66971845 Jan 23 03:44:02 2007 9500-system-3. Copyright © 2008.Task 2: Document Performance Measurements In this task you will generate workloads with SAN Extension Tuner and document performance measurements. From the CORE2 Device Manager select Interface > Monitor > FCIP. Step 1 Create a pattern file to use for SAN Extension Tuner testing. Lab Guide 10-5 . Activity Procedure Complete the following steps on CORE2.

Skyline ATS. Wait until they finish the application before proceeding. Select SAN Extension Tuner to launch the SAN Extension Tuner wizard. If another student is running SET. Note: Only one instance of the SAN Extension Tuner can run at a time. change the interval to 2s and the value to LastValue/sec.2 Copyright © 2008. Shutdown your pod’s second GigE interface on both CORE1 and CORE2 Pod1: GigE2/2 --. Step 5 Step 6 Leave the FCIP Monitor window open.Step 4 From the FCIP Monitor interface. Inc.GigE2/4 Pod3: GigE2/6 --.GigE2/2 Pod2: GigE2/4 --. . 10-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. right-click your Port Channel between CORE1 and CORE2.GigE2/6 Pod4: GigE2/8 --. you will get a warning message. Step 7 From the Fabric Manager topology pane.GigE2/8 Note: These disabled gigE ports will be used by the SAN Extension Tuner to simulate an attached iSCSI initiator and target.

GigE2/2 Pod2: GigE2/4 --. select your pod’s second gigE interface for CORE1 and CORE2 Pod1: GigE2/2 --. Lab Guide 10-7 .GigE2/6 Pod4: GigE2/8 --.Step 8 In the 1 of 3: Select Ethernet Port Pair dialog. Click Yes to create a zone for the SAN Extension Tuner virtual N ports. Skyline ATS.GigE2/8 Step 9 Step 10 Click Next. Inc. Copyright © 2008.GigE2/4 Pod3: GigE2/6 --.

Inc. continue to step 14. Step 14 Drag and Drop the SanExtTuner zone into ZoneSet1. right click the Zonesets placeholder and select Insert. Skyline ATS. create by clicking OK to accept the default Zoneset Name. Step 12 In the Edit Local Full Zone Database window for VSAN 1.2 Copyright © 2008. . Step 13 If a Zoneset does not exist.Step 11 Set a unique zonename and then click OK. If a Zoneset does exist. 10-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

then close the Edit Full Local Zone Database window. Skyline ATS. Step 17 Wait for the zoneset activation to complete.Step 15 Right-click ZoneSet1 and select Activate. Inc. Lab Guide 10-9 . Step 16 Click Continue Activation. Copyright © 2008.

2 Copyright © 2008. Inc.Step 18 Click Next on the SAN Extension Tuner Wizard screen 1 of 3. . Skyline ATS. 10-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Copyright © 2008. Read I/O. accept the default parameters for Transfer Size. Use the Pattern File pull-down menu to select the testfile you created in Task 1. Inc.Step 19 On screen 2 of 3. and Write I/O. Lab Guide 10-11 . Click Start on the 3 of 3: Results screen of the SAN Extension Tuner Wizard. Select the Use Pattern File check box. Step 20 Step 21 Step 22 Step 23 Click Next on screen 2 of 3 of the SAN Extension Tuner Wizard. Skyline ATS.

click Show. Step 26 After a minute or two. Note your average Read Response Time: __________ Note your average Write Response Time: __________ Note your Egress MBs/sec: __________ Note your Ingress MBs/sec: __________ 10-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS. . Inc. Step 25 Return to the SAN Extension Tuner Wizard 3 of 3: Results screen.Step 24 Return to the FCIP Monitor window and observe the Rx and Tx Bytes in the Data Traffic column.2 Copyright © 2008.

Lab Guide 10-13 . Skyline ATS. display the FLOGI database. # show fcns database VSAN 1: ----------------------------------------------------------------------FCID TYPE PWWN (VENDOR) FC4TYPE:FEATURE ----------------------------------------------------------------------0x0a0001 N 02:02:00:0d:ec:0c:fb:40 scsi-fcp 227 0x630004 N 02:02:00:0d:ec:20:6f:80 scsi-fcp 227 Total number of entries = 2 Step 29 On both switches. display the FCNS database. Copyright © 2008. display the active zoneset and the virtual N ports created by the SAN Extension Wizard. Inc. # show flogi database ------------------------------------------------------------------------------------------INTERFACE VSAN FCID PORT NAME NODE NAME ------------------------------------------------------------------------------------------iscsi2/8 1 0x630004 02:02:00:0d:ec:20:6f:80 00:00:00:0d:ec:20:6f:80 Total number of flogi = 1. Click Stop and then click Cancel. Step 28 On both switches.Activity Verification Complete the following steps to verify your configuration. # show zoneset active zoneset name ZoneSet1 vsan 1 zone name SanExtTuner-channel1-CORE1 vsan 1 * fcid 0x630001 [pwwn 02:02:00:0d:ec:20:6f:80] * fcid 0x0a0001 [pwwn 02:02:00:0d:ec:0c:fb:40] Step 30 Return to the SAN Extension Tuner Wizard. Step 27 On both switches.

(config)# interface fcip x (config-if)# shutdown (config-if)# no shutdown Step 3 From the Fabric Manager. Step 2 On both switches.2 Copyright © 2008. disable. you will tune TCP parameters and observe changes to performance measurements. Step 1 From the CLI configure the FCIP profile TCP parameters to optimize the FCIP tunnel:    Max Bandwidth: 1000 Mb Min Bandwidth: 1000 Mb Estimated RTT: 48 us (config)# fcip profile x (use the fcip profile number for your first GigE interface) (config-profile)# tcp max-bandwidth-mbps 1000 min-available-bandwidthmbps 1000 round-trip-time-us 48 (config-profile)# exit Note: Do not proceed until Step 1 has been completed on both switches. select Server > Purge Down Elements Step 4 Click Rediscover Current Fabric.Task 3: Tune TCP Parameters In this task. Activity Procedure Complete these steps on both switches. 10-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS. Inc. . and then enable the fcip x interface.

Inc.Step 5 Right-click your FCIP tunnel between CORE1 and CORE2. Note: Copyright © 2008. Step 6 Click SAN Extension Tuner. Wait until they finish the application before proceeding. Only one instance of the SAN Extension Tuner can run at a time. you will get a warning message. Lab Guide 10-15 . Skyline ATS. If another student is running SET.

Step 7 In the 1 of 3: Select Ethernet Port dialog. Pod3: x=6. . Inc. Skyline ATS.2 Copyright © 2008. Pod 2: x=4. 10-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3. select the gigE2/x interface for both CORE1 and CORE2. Pod 1: x=2. Pod4: x=8 Step 8 Click Next on the SAN Extension Tuner Wizard 1 of 3.

accept the default parameters of Transfer Size. Read IO.Step 9 On screen 2 of 3. Step 10 Step 11 Step 12 Click Next on screen 2 of 3 of the San Extension Tuner Wizard. and Write IO. Use the Pattern File pull-down menu to select the testfile you created in Task 1. Select the Use Pattern File check box. Copyright © 2008. Lab Guide 10-17 . Inc. Skyline ATS.

Step 14 Return to the FCIP Monitor window and observe the Rx and Tx Bytes in the Data Traffic column. Inc.Step 13 Click Start on the 3 of 3: Results screen of the San Extension Tuner Wizard. . 10-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS.2 Copyright © 2008.

Skyline ATS. The parameter values that you set in Task 3 were appropriate for a dedicated 1Gig link. Lab Guide 10-19 . Your results should document a dramatic performance improvement. Step 1 Compare these performance results with those recorded on page 11-. Note your average Read Response Time: __________ Note your average Write Response Time: __________ Note your Egress MBs/sec: __________ Note your Ingress MBs/sec: __________ Step 17 Return to the SAN Extension Tuner Wizard. Inc. This completes this lab.Step 15 Return to the San Extension Tuner Wizard 3 or 3: Results Screen. Click Stop and then click Cancel. Activity Verification Complete the following steps to verify your configuration. Step 16 Click Show. Copyright © 2008. The original TCP parameters were far from ideal.

Skyline ATS.2 Copyright © 2008.10-20 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Inc. .

you will configure MDS switches in your pod to access a peer network time protocol server Objective Your company recently added a Network Time Protocol server to ensure that all hosts and switches maintain consistent time. These are the resources and equipment required to complete this exercise:    Two MDS 9000 family switches with at least one ISL between them Two Fibre Channel-attached Windows 2000 servers connected to both switches One NTP server . You will enable NTP for CFS configuration and then configure both switches to use an NTP server.Lab Exercise 11: Using Cisco Fabric Services Exercise Objective  In this exercise.

CFS can be used to distribute and merge configurations for many SAN-OS applications. In this task you will configure NTP to use the CFS infrastructure. Exercise Procedure: Configure NTP Note: Administrators of MDS1 and MDS2 must work together to complete this exercise.Task 1: Configure NTP As of SAN-OS Release 2. Complete these steps: Step 1 Both teams login to your respective switches (MDS1 or MDS2) with the Device Manager. .0. Inc. Skyline ATS.2 Copyright © 2008. . On both MDS1 and MDS2: From the Device Manager choose Admin > CFS (Cisco Fabric Service) Step 2 11-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Copyright © 2008. Click Close.Step 3 On both MDS1 and MDS2: Observe the list of CFS-capable applications that are available. Notice that only the device-alias feature has a status of enabled by default. Step 4 On both MDS1 and MDS2: Select the enable command to configure Network Time Protocol (NTP) for CFS distribution. Inc. Additional CFS-capable applications are not listed because their services are not enabled on the switch. 11-3 . Skyline ATS. Click Apply.

2 Copyright © 2008. Skyline ATS. Step 7 On MDS1 only: Choose IP Address type of ipv4. Note: Most CFS applications require an explicit “commit” before configurations are applied. At this point the NTP entry is pending the commit. and Mode of peer.198.168. Click Create.Step 5 On MDS1 only: From the Device Manager select NTP from the Admin pull down menu.0. Step 6 One MDS1 only: Click the Create button. . Inc. Name or IP Address of 192. 11-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Copyright © 2008.Step 8 Verify that a lock has now been set on both MDS1 and MDS2. 11-5 . Skyline ATS. Enter the following command: # show cfs lock Step 9 On MDS2 only: Attempt to add a second NTP entry (steps 7-9) Step 10 When the administrator of MDS2 clicks on the Create button the following error is displayed: Step 11 On MDS1 only: Commit the NTP pending configuration by choosing Commit from the CFS drop down menu. Inc.

Inc. 11-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Write the filename down for future reference. Copy it into the podX directory.2 Copyright © 2008. . click Yes to save your changes.cfg Filename: ________________________________ Step 14 Close Device Manager.Step 12 From MDS2.0.198/podX/fname. When prompted. where X is your pod number. and then click Close to close the Save Configuration dialog. Skyline ATS. # copy run tftp://192. Step 13 On both MDS1 and MDS2: Save your running configuration to the TFTP server. That concludes this lab exercise. Use a unique filename so that it will not be overwritten by others. notice that the entry committed from MDS1 has been transferred to MDS2.168.

Appendix A: Final Configuration The following is a partial output of the show run command from P1-MDS1 after completing this lab exercise: P1-MDS1# show run ntp distribute ntp peer 192. 11-7 . Inc.0. Skyline ATS.198 ntp commit Copyright © 2008.168.

2 Copyright © 2008. . Skyline ATS. Inc.11-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Figure 1. MDS 9000 Switches and Management Hosts In this lab. you will use the fcanalyzer command to view supervisor control traffic locally from a command line interface. and then remotely from a Windows host running Ethereal. you will be able to meet these objectives:   Use the fcanalyzer local command to view control traffic locally Set filters for the fcanalyzer command display Visual Objective Figure 1 illustrates the topology that you will use in this exercise.Lab Exercise 12: Using FC Analyzer Exercise Objective In this exercise. After completing this exercise. . you will configure the fcanalyzer command to view control frames going to and from the MDS 9000 supervisor.

Capture and forward FC control traffic to the remote server with IP address ip_addr via mgmt0.10.it) – required for fcanalyzer remote Command List The commands used in this exercise are described in the table here. Skyline ATS.com) WinPcap version 3. . Capture and display FC control traffic on the local console.0 or higher (www.ethereal.Required Resources These are the resources and equipment required to complete this exercise:     2 MDS 9000 Fibre Channel switches 2 Windows 2000 hosts with Fabric Manager and Device Manager installed. Clear the list of configured fcanalyzer remote hosts. Inc.0 or higher (winpcap.polito. Ethereal version 0.2 Copyright © 2008. Command Description Capture and display FC control traffic on the local console Capture and write fcanalyzer output to the file sample_0000_<datetime> in the switch volatile memory. filtering the display using filter_conditions. fcanalyzer local [brief] [limit-captured-frames n] fcanalyzer local write volatile:sample fcanalyzer local displayfilter filter_conditions fcanalyzer remote ip_addr clear fcanalyzer 12-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

Exercise Procedure Complete these steps: Step 1 Step 2 Open a Device Manager connection to your switch. Capturing on eth2 Note: The above warning message is normal and should be ignored. If you do not see anything. Dst: 00:00:00:00:ee:00 Destination: 00:00:00:00:ee:00 (00:00:00:00:ee:00) Source: 00:00:00:00:00:0a (00:00:00:00:00:0a) Type: Unknown (0xfcfc) MDS Header(Unknown(0)/Unknown(0)) MDS Header Step 5 At this point you may or may not see output scrolling on the display screen. Frame 1 (160 bytes on wire. 160 bytes captured) Arrival Time: Sep 12. Inc.000000000 seconds Time since reference or first frame: 0.000000000 seconds Frame Number: 1 Packet Length: 160 bytes Capture Length: 160 bytes Ethernet II. 2004 05:48:34. You can change this behavior with the limit-captured-frames option. Note: By default FC Analyzer will run until you press Ctrl-C or until 100 frames are captured and displayed. Select Command Line Interface from the Device menu. Step 6 Press Ctrl-C to stop the fcanalyzer display. disable and then enable port 5 or port 10. Enter global configuration mode: # config Step 3 Step 4 Start the fcanalyzer in local display mode: (config)# fcanalyzer local Warning: Couldn't obtain netmask info (eth2: no IPv4 address assigned).Task 1: Viewing fcanalyzer Output Locally In this task you will use the fcanalyzer command to view supervisor control traffic on the local console. Skyline ATS. Login with the username admin and the password 1234qwer. Src: 00:00:00:00:00:0a.040374000 Time delta from previous packet: 0. Lab Guide 12-3 . Copyright © 2008. that is. return to Device Manager and “bounce” one of the F ports.

fa.02.fd -> ff.870021 189.574120 188.fc.fc.opcode Warning: Couldn't obtain netmask info (eth2: no IPv4 address assigned). enter the following: (config)# fcanalyzer local brief limit-captured-frames 20 Warning: Couldn't obtain netmask info (eth2: no IPv4 address assigned).ff.ff. ACK1 0x4dd2 0xffff SW_ILS HLO [Remainder of output deleted] Step 8 Direct the output of the fcanalyzer command to a file: (config)# fcanalyzer local write foo Note: Output will go both to the terminal and.18 ff.fd -> ff.574430 188.02.fd ff.02. 12-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3.ff.574434 188.ff.869646 189.870101 189.fd ff.2 Copyright © 2008.00 -> ff. Capturing on eth2 0.00 18.869353 10.00 18.ff.870312 189. Skyline ATS.18 -> 18.02.fe -> 18.02. .01 ff. by default..fc.01 -> ff.00 18.e.fc -> 18.Step 7 To see a protocol summary of one frame per line for 20 frames. Step 9 Limit the FC Analyzer output by setting a display filter that will only capture FC Extended Link Service frames: (config)# fcanalyzer local brief display-filter fcels.02. disable. for example.00 -> ff.02.18 -> 18.ff. to a file in the volatile file system (you can also specify slot0:. slot0:foo).574561 188. 00.18 -> 18.00 -> ff.00 18.02.fd 0xffff 0xffff FC Unknown frame 0x4d9f 0xffff SW_ILS HLO 0x4d9f 0x4dd1 FC Link Ctl.ff.00 -> ff.869893 ff.fd -> 18. The saved file name will be of the form volatile:foo_00001_<datetimestamp>. Inc.ff.575342 189.ff.18 ff.ethereal.871632 Note:The above command can be an invaluable tool for troubleshooting failed device logins.ff.fc.fc.fc.fe ff.869602 10. Step 10 Use Device Manage and bounce (i.02. That concludes this lab exercise.fc ff.ff.02. Observe the command line output.fd ff.00 -> ff.18 0xc770 0xffff FC ELS FLOGI 0xc770 0x4f1b FC ELS ACC (FLOGI) 0xc788 0xffff FC ELS PLOGI 0xc788 0x4f1c FC ELS ACC (PLOGI) 0xc7a0 0xffff FC ELS SCR 0xc7a0 0x4f1d FC ELS ACC (SCR) 0x4f41 0xffff FC ELS PLOGI 0x4f41 0xcab8 FC ELS ACC (PLOGI) 0x4f40 0xffff FC ELS PRLI 0x4f40 0xcad0 FC ELS ACC (PRLI) 0x4f42 0xffff FC ELS LOGO 0x4f42 0xcae8 FC ELS ACC (LOGO) 188.559659 188.00 -> ff.ff. and then enable) one of the F ports.fa.02.871490 189.00.fd -> ff.00 ff.00 18.000000 10.com. Capturing on eth2 Note: Procedures to specify display filters are documented at the Ethereal web site http://www.

Lab Exercise 13: Using SPAN and the Cisco Port Analyzer Adapter Exercise Objective In this exercise. you will use the MDS 9000 SPAN feature to capture FC data and control traffic and send it via a Cisco PAA to a Windows host running Ethereal. such as the PAA. You will use Ethereal to view and analyze the output. Note: Unlike FC Analyzer. you will configure a SPAN destination port and SPAN session to capture FC data and control traffic using the Cisco Port Analyzer Adapter (PAA). Figure 1. PAA and Windows Hosts with Ethereal In this lab. there is no PAA attached to MDS1. After completing this exercise. you will be able to meet these objectives:  Configure SPAN destination ports and SPAN sessions  Use Ethereal to capture and analyze frames from a PAA  Set display filters in Ethereal Visual Objective Figure 1 illustrates the topology that you will use in this exercise. As illustrated above. . MDS Switches. performing protocol analysis with SPAN requires additional hardware in the form of an external FC Analyzer.

2 Copyright © 2008.0 or higher Command List The commands used in this exercise are described in the table here. . Command Description Creates a SPAN session with ID x Sets the destination port for the current SPAN session Sets the source port for the current SPAN session Shows configured SPAN sessions span session x destination int fcx/y source int fcx/y show span session 13-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3.9.10 or higher  WinPcap version 3.Required Resources These are the resources and equipment required to complete this exercise:  1 MDS 9000 Fibre Channel switch with a PAA attached  2 Windows 2000 hosts with Fabric Manager and Device Manager installed  Ethereal version 0. Inc. Skyline ATS.

Inc. Complete these steps: Step 1 Open a Device Manager connection to your switch. one team can still perform the configuration of the SD Port and the SPAN session there. perform the following steps on MDS-2. Lab Guide 13-3 . although there is no PAA physically attached to MDS-1.Task 1: Configuring SPAN Ports In this task. If not. Copyright © 2008. Skyline ATS. Login with the username admin and the password 1234qwer. Exercise Procedure 1: Configuring a SPAN Port Using Device Manager Note: If you are working alone in your pod. you will configure a SPAN Destination port (SD_Port) using Device Manager.

Skyline ATS. The fc1/16 configuration window should open. Speed 1Gb and Status up. It must be set to 1 or 2 Gbps.Step 2 Step 3 Double-click port 16. . 13-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Note: The port speed on an SD Port cannot be set to auto. Enter SPAN Destination in the Description field. Select Mode SD. Click Close. Step 4 Click Apply. Inc.2 Copyright © 2008.

Lab Guide 13-5 . even if there is no fiber optic cable or FC analyzer attached. # config Enter configuration commands. Note:The output will show you the commands needed to configure an SD port from the CLI. Step 9 Repeat step 7 to verify the configuration. As long as there is a GBIC present. Inc. Step 10 Save the configuration to NVRAM # copy run start Copyright © 2008. it is a good idea to enable EISL encapsulation on the SD_Port (disabled by default). Step 6 Select Command Line Interface from the Device menu. This will allow you view EISL headers and to capture per-VSAN statistics with tools such as the Cisco Traffic Analyzer. (config)# interface fc1/16 (config-if)# switchport encap eisl (config-if)# end End with CNTL/Z. it will indicate SD.Step 5 Verify that port 16 now shows type SD. one per line. Login as username admin and password 1234qwer. Step 8 Enable EISL encapsulation on the SD port. Skyline ATS. Verify the configuration of the SD port as follows: # show run interface fc1/16 interface fc1/16 switchport description SPAN Destination switchport mode SD switchport speed 1000 no shutdown Step 7 Note:Because the SPAN Destination port is attached to a Cisco PAA. Note:The SD port is a passive port.

Task 2: Configuring a SPAN Session In this task. . Inc. click Create. Step 4 Click Close.2 Copyright © 2008. click Create. Select SPAN from the Interface menu. Step 3 With 1 in the SPAN Session Id field. you will use your configure a SPAN session using the Device Manager. Exercise Procedure 1: Configure a SPAN Session Using Device Manager Complete these steps: Step 1 Return to Device Manager. 13-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Step 2 In the Sessions tab. Skyline ATS.

Copyright © 2008. Click to select Session 1 and then click the Edit Interface List button. Note: The session Status should be Admin active. Click Apply. double-click in the Dest Interface field and enter the SPAN Destination port number fc1/16. Step 6 Step 7 Select the Sources tab.Step 5 In the SPAN dialog. Lab Guide 13-7 . Step 8 Click Create. Inc. meaning administratively active. but operationally inactive. Skyline ATS. but Oper inactive.

13-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3. the interface for one of your FC-attached hosts.2 Copyright © 2008. Inc.Step 9 Select the “…” button. Step 13 Click Close. Step 12 Click Create. Click OK. Step 10 Click port 5. . Click Close. Skyline ATS. Step 11 Click the transmit checkbox to select both receive and transmit.

Step 18 Save your configuration to NVRAM. if needed). Step 17 Determine the CLI commands needed to implement the SPAN session: # show run diff + span session 1 + destination interface fc1/16 + source interface fc1/5 rx + source interface fc1/5 tx Note: The above is a partial output of the display. Step 15 Step 16 Click Close. These four lines are equivalent to the 15 steps used in Device Manager to configure a SPAN session. Skyline ATS. Egress (tx) sources are fc1/5. Click Refresh. Lab Guide 13-9 .0. Verify that your session is now operationally active.cfg> Copyright © 2008.168. # copy run tftp://192. # copy run start Step 19 Save your configuration to the TFTP server as follows (where X is your pod number and fname is a unique filename that you will remember later. Inc.198/podX/<fname.Step 14 Select the Sessions tab. The plus signs indicate lines added to the running configuration. Open a Command Line Interface window and verify the status of the SPAN session: # show span session Session 1 (active) Destination is fc1/16 No session filters configured Ingress (rx) sources are fc1/5.

you will use the Ethereal protocol trace viewer to capture and analyze Fibre Channel Extended Link Service (FC_ELS) frames in a fabric login trace that includes the FLOGI. because the PAA simply does a MAC broadcast onto the Ethernet segment. The output will be generated using the previously created SPAN session.2 Copyright © 2008.X. 13-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Both servers are on the same network segment as the PAA. Exercise Procedure 1: Setting up Ethereal to Capture Frames Complete these steps: Step 1 Double-click the Ethereal shortcut on your Windows 2000 Server desktop. If it does not try one of the other adapters. Click OK.Task 3: Viewing FC Frames using Ethereal and the PAA In this task. Step 24 Note:Either Windows 2000 server will work fine for running Ethereal. Under Display Options select Update list of packets in real time and Automatic scrolling in live capture.X address. Verify that the IP Address field shows a 10.0. Skyline ATS. Inc. Step 20 Select Start from the Capture menu.0.X. and PRLI processes. Step 21 Select the Last adapter from the Interface pull down menu. PLOGI. Ensure that the IP address is of the form 10. . Step 22 Step 23 Clear the Capture Filter field.X before continueing.

Inc. select Save As from the File menu. Note: There are several protocols that were captured in addition to Fibre Channel. Skyline ATS. In the following steps we will create a filter to display only FC ELS frames. Step 26 Click Stop. so bouncing port 5 on that switch will not generate SPAN traffic. Scroll down until you see the FC ELS FLOGI frame.Step 25 With the following window open. Note: To save a copy of the packet capture to a local file so you can open it for later analysis. Note: Recall that there is not a PAA physically attached to MDS-1. Lab Guide 13-11 . open Device Manager for MDS2 and bounce port 5 (enable/disable fc1/5). Copyright © 2008. Note: If no Fibre Channel frames are visible return to step 3 and select the second adapter from the Interface pull down. Then repeat steps 4-8. Step 27 Click the Protocol column header to sort the frames by protocol type.

Step 30 Scroll down in the list.Step 28 Click the Filter button.2 Copyright © 2008. Step 31 Step 32 Click OK. 13-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Note: You should now only see FC ELS frames displayed. Click OK to apply the filter. Some of them may indicate “Malformed Packet”. . Inc. Step 29 Click the +Expression button. This is because the dip switches on the PAA are configured to truncate FC frames. Locate and select FC ELS. Skyline ATS.

Step 36 Copyright © 2008. Step 35 Locate and make a note of the Originator Exchange ID (OX_ID). Lab Guide 13-13 . Note the number of buffer-to-buffer credits advertised by the HBA. click the triangle next to Boardwalk to expand the EISL frame header. hence the source address is 00.00. the FC_ID of the HBA is not known. Skyline ATS. In the middle window. Step 34 Expand the Fibre Channel header. Note the VSAN number of the frame.00. At this point. Note the “well known” destination address for the fabric login server. ________ Expand the Common Svc Parameters. Note the Qlogic PWWN. Inc.Step 33 Select the FLOGI (fabric login) frame in the top window of the Ethereal display. Note: The FLOGI frame is coming from the server HBA port to the switch.

What is the well-known destination address of the frame? Select a PRLI (process login) frame. The destination address is the FC_ID assigned by the switch to the HBA port. Skyline ATS. click the ACC (Accept) frame sent in response to the FLOGI frame. .2 Copyright © 2008. is the OX_ID the same as the FLOGI frame above? ________ Note: Most FC extended link services use a two sequence exchange. Is this frame part of the same FC Exchange (in other words. What is the source address of the frame? Is this frame going from the HBA to the switch? Step 40 Step 41 Expand the PRLI FC ELS and Service Parameter Page 0. Step 38 Select a PLOGI (port login) frame: What is the well-known destination address of the frame? Is this frame part of the same FC Exchange as the FLOGI frame? What is the maximum number of concurrent sequences supported? ____________ _______ _______ ____________ ____________ _______ _______ Step 39 Select an SCR (state change registration) frame. What type of session is being established? 13-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.Step 37 In the top window of the Ethereal display. Inc.

(config)# span session 1 (config-span)# suspend (config-span)# end End with CNTL/Z.cfg> That concludes this lab exercise. When everyone in the pod is finished.Step 42 Select the ACC to the PRLI. Copyright © 2008. Step 45 Save your configuration to NVRAM. one per line. return to the switch CLI for MDS1 and MDS2 and suspend the SPAN session: # config Enter configuration commands. # copy run start Step 46 Save your configuration to the TFTP server as follows (where X is your pod number and fname is a unique filename that you will remember later. Skyline ATS.198/podX/<fname. if needed). # copy start tftp://192. Lab Guide 13-15 . Was the FCP Image Pair established? _______ Partial Listing of Well Known Fabric Addresses FF FC 01 – FF FC FE FF FF FA FF FF FC FF FF FD FF FF FE Reserved for Domain Controllers Management Server Directory Server Fabric Controller F_Port (Login Server) Step 43 Step 44 Close Ethereal.168.0. Inc.

Skyline ATS. P4-MDS2# show running-config Building Configuration . This sample is taken from MDS1 in Pod 1.2 Copyright © 2008. interface fc1/16 switchport description SPAN Destination switchport mode SD switchport speed 1000 switchport encap eisl no shutdown span session 1 destination interface fc1/16 source interface fc1/5 rx source interface fc1/5 tx 13-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3.. Inc.. .Appendix A – Sample Lab Configuration File (partial) The following output has been edited to include the portions of the configuration file most relevant to this lab.

you will be able to meet these objectives:      Determine the version of a software image file Download software images from a TFTP server to an MDS 9000 switch Perform a full software upgrade Install kickstart images from BIOS and/or the boot loader prompt Install system images from the kickstart image prompt Visual Objective Figure 1 illustrates what you will accomplish in this exercise. Figure 1.Lab Exercise 14: Upgrading Switch Software Exercise Objective In this exercise. After completing this exercise. you will upgrade MDS switch software and recover from several image-related problems. . and perform a software upgrade. MDS Switches and FTP/TFTP Server In this lab. You will also access the switch through the console port to troubleshoot problems loading software images. you will download system and kickstart images from the TFTP server to the switch bootflash.

Upgrades the system (non-disruptively if dual supervisors are p system and kickstart image files. Assigns the specified image file to the kickstart variable to be used at the next reboot. Copies the running configuration to the startup configuration. Displays details of the current installed images including the version number.2 Copyright © 2008. Assigns the specified image file to the system variable to be used at the next reboot. Copies the specified file from a TFTP server to the bootflash directory. Reboots the system. Erases the contents of the bootflash memory. Clears the current kickstart variable. Skyline ATS. . Clears the current system variable. use the image option to view version information of a specific image file. Displays the boot variables. Inc. Command Description Enters configuration mode/ Lists the files in the bootflash directory.Required Resources These are the resources and equipment required to complete this exercise:   2 MDS 9000 Fibre Channel switches Access to TFTP server with MDS 9000 software images Command List The commands used in this exercise are described in the table here. config term dir bootflash: show version [ image file ] show boot install all system file1 kickstart file2 no boot system no boot kickstart boot system bootflash:file boot kickstart bootflash:file init system copy running startup copy tftp://ip_addr/path/file bootflash:file reload 14-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3.

html and http://www.2(3) BIOS compile time: kickstart image file is: kickstart compile time: 12:22:23] system image file is: system compile time: 12:49:37] 10/24/03 bootflash:/9100-kickstart-3. The copyrights to certain works contained herein are owned by other third parties and are used and distributed under license. Exercise Procedure Complete these steps: Step 1 Open a Command Line Interface to your switch. this portion of the lab can be done from a Telnet or SSH connection as well.2(2) 3.2.2(3) 3. In particular.0 1.3 12/6/2007 10:00:00 [12/16/2007 bootflash:/9100-system-3. Cisco Systems. For this reason.Task 1: Downloading Software Images to the Switch In this task you will download software images to the switch and verify they arrived intact. Some parts of this software may be covered under the GNU Public License or the GNU Lesser General Public License.com/tac Copyright (c) 2002-2007.org/licenses/gpl. Device Manager or the CLI.1.html Software BIOS: loader: kickstart: system: version version version version 1. Note: Parts of this lab must be done from the switch console.org/licenses/lgpl.2. Login with the username admin and the password 1234qwer. Inc. Skyline ATS. in the following steps we will focus on the CLI method. A copy of each such license is available at http://www. Lab Guide 14-3 .gnu. Note: Image downloads and software upgrades can be performed using Fabric Manager. Inc. Cisco strongly recommends performing software upgrades from the CLI because it provides the most information and control. Step 2 Display details of the currently installed images.cisco.3 12/6/2007 10:00:00 [12/16/2007 Copyright © 2008.gnu. note the version of the kickstart and system software: # show version Cisco Storage Area Networking Operating System (SAN-OS) Software TAC support: http://www. however. All rights reserved.

Step 5 Verify that you can reach the TFTP server that holds the software images: # ping 192.198: icmp_seq=2 ttl=63 time=0.5 ms 64 bytes from 192.0.6 ms 64 bytes from 192. In lieu of TFTP. 14-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. you can copy images to and from the external compact flash. In addition. # dir bootflash: 14954496 67605711 Feb 12 21:17:33 2008 Feb 12 21:16:57 2008 9100-kickstart-3.168.168. verify the state of your mgmt0 interface and default gateway.0.168.Step 3 Display the value of the boot variables in the running config.198): 56 data bytes 64 bytes from 192.198: icmp_seq=3 ttl=63 time=0.0. You can do this with the following command: dir bootflash://sup-n (where n is 1 or 2 depending upon which supervisor is active. Inc.5 ms Step 6 If ping is not successful.0.168.2.2.168. As you can see.0. you can also use FTP. on an MDS 9500 series director.3 system variable = bootflash:/9100-system-3.168.3 Usage for bootflash://sup-local 96677888 bytes used 87881728 bytes free 184559616 bytes total Note: Pay particular attention to the free space. for example from the Cisco website. You must have sufficient space for the image downloads.168. Warning If you are upgrading an MDS 9500 series director. or SCP. # show boot kickstart variable = bootflash:/9100-kickstart-3. SFTP.2 Copyright © 2008.3 9100-system-3. Skyline ATS.2. slot0:. the kickstart and system images can consume over 70 MBytes. be sure to verify that there is sufficient free space in bootflash on the backup supervisor module.0.198: icmp_seq=1 ttl=63 time=2. If still unsuccessful.198 PING 192.0. .2. contact the instructor for help.198: icmp_seq=4 ttl=63 time=0. Note: The assumption is that you have previously downloaded the software images to the TFTP server.3 Step 4 Display the contents of the bootflash file system (note that you must include a colon character after the keyword bootflash).198 (192.4 ms 64 bytes from 192.

2.3 Usage for bootflash://sup-local 171897856 bytes used 14187520 bytes free 186085376 bytes total Step 10 Verify the software version for the new kickstart image file: # show version image bootflash:9100-kickstart-3.2(2) version 3. Lab Guide 14-5 .2.2.2. Copyright © 2008.Step 7 Download the new kickstart image from the TFTP server to bootflash: # copy tftp://192.168.2.0..bin loader: kickstart: compiled: version 1.168.3. This time.198 Enter username: student Password: mdslab Step 9 Display the contents of the bootflash file system: # dir bootflash: 14913536 14954496 67552289 67605711 Feb 14 21:17:33 2008 Feb 12 20:02:24 2008 Feb 14 21:16:57 2008 Feb 12 20:04:00 2008 9100-kickstart-3.2.2c Trying to connect to tftp server.2c bootflash:9100-kickstart-3.2. Inc.2.2c 9100-system-3. Skyline ATS..2c 9100-kickstart-3.2c. use the copy command interactively as follows: # copy ftp: bootflash: Enter the source filename: 9100-system-3.0.2. / TFTP get operation was successful Step 8 Copy the new system image from the FTP server to bootflash...2(2c) 11/16/2007 12:00:00 [11/17/2007 01:12:46] Note: The image name shown in the command output is the actual image name used by Cisco.2c image name: m9100-s1ek9-kickstart-mz..2c Enter hostname for the ftp server: 192.3 9100-system-3.198/9100-kickstart-3.

3. 14-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. # show version image bootflash:9100-system-3. . If new versions of the loader and BIOS are needed during a software upgrade process.bin bios: system: compiled: version v1.2 Copyright © 2008.0(10/24/03) version 3.2.Step 11 Repeat the above step for the new system image file. Skyline ATS.2.2c image name: m9100-s1ek9-mz. they will be extracted from these images.1.2c.2(2c) 11/16/2007 12:00:00 [11/17/2008 01:37:19] Note: Loader code is embedded in the kickstart image and the BIOS code is embedded in the system image. Inc.

2.2(2) Upg-Required -----------yes yes no no Do you want to continue with the installation (y/n)? [n] y Note: MDS 9500 series directors support a “hitless” upgrade.SUCCESS Verifying image bootflash:/9100-system-3. Exercise Procedure Complete these steps: Step 1 Verify that there are no incompatibilities with the earlier 3.1. will be disruptive.2(2c) 3.2c system bootflash:9100-system-3.2.2.2c for boot variable “system” [####################] 100% -. you will perform a software downgrade using the install all command.2.3 image to the earlier 3.SUCCESS [… deleted rest of output to save space …] Step 3 Observe the command output. Inc.1.2.2(3) 3.2c image. Verifying image bootflash:/9100-kickstart-3. the session will be lost during a switch reboot or during a director supervisor failover. bootable -------yes Impact -------------disruptive Install-type -----------reset Reason -----Reset due to single supervisor Compatibility check is done: Module -----1 Images will be upgraded according to following table: Module -----1 1 1 1 Image ---------system kickstart bios loader Running-Version -------------------3.2c for boot variable “kickstart” [####################] 100% -. however.Task 2: Downgrading Software Images In this task.2c Note: The above command can also be run from a Telnet or SSH session.2. such as the CSM.2(3) v1.2(2) New-Version -------------------3.0(10/24/03) 1.2. however upgrades to some services modules.2.2c No incompatible configurations Step 2 Access the switch console (not Telnet or SSH) and initiate the software upgrade: # install all kickstart bootflash:9100-kickstart-3. Copyright © 2008.2(2c) v1.2c image # show incompatibility system bootflash:9100-system-3.0(10/24/03) 1. Lab Guide 14-7 . You will be moving from 3. Skyline ATS. Pay particular attention to the Impact information. Enter y to proceed with the upgrade. meaning software upgrades will normally occur non-disruptively for the supervisor modules and FC line cards.

Step 5 Step 6 When the login prompt appears.2c system variable = bootflash:/9100-system-3. login to the switch. the supervisor that was previously active will reload with the new image and come up as the standby.2 Copyright © 2008.2(2c) Verify that the boot variables have been updated: # show boot kickstart variable = bootflash:/9100-kickstart-3. . Note: On an MDS 9500 series director. Skyline ATS. and then the switch will perform a hitless failover from the active to the standby supervisor.2. At that point.2(2) kickstart: version 3. Verify the kickstart and system software images have been updated: # show version Software BIOS: loader: version 1.2c 14-8 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 version 1. the standby supervisor will first reload with the new image. Inc.2.2(2c) system: Step 7 version 3. the configuration is saved to NVRAM and the switch resets to load the new image.1.Step 4 Continue to observe the console as the boot variables are updated.

bootable -------yes Impact -------------disruptive Install-type -----------reset Reason -----Reset due to single supervisor Compatibility check is done: Module -----1 Images will be upgraded according to following table: Module -----1 1 1 1 Image ---------system kickstart bios loader Running-Version -------------------3.2.3 system bootflash:9100-system-3. Lab Guide 14-9 . will be disruptive.2c image to the earlier 3.1.SUCCESS [… deleted rest of output to save space …] Step 2 Observe the command output.Task 3: Upgrading Software Images In this task.2(3) 3.2(2) New-Version -------------------3. however. Copyright © 2008. Pay particular attention to the Impact information. such as the CSM.3 for boot variable “kickstart” [####################] 100% -. the session will be lost during a switch reboot or during a director supervisor failover.2.2.3 image. Verifying image bootflash:/9100-kickstart-3.0(10/24/03) 1. You will be moving from 3. Inc.3 for boot variable “system” [####################] 100% -. you will perform a software upgrade using the install all command.1. Skyline ATS.2.2(2c) 3.2(3) v1. Exercise Procedure 1 Complete these steps: Step 1 Access the switch console (not Telnet or SSH) and initiate the software upgrade: # install all kickstart bootflash:9100-kickstart-3.SUCCESS Verifying image bootflash:/9100-system-3.2(2c) v1. meaning software upgrades will normally occur non-disruptively for the supervisor modules and FC line cards. however upgrades to some services modules.2.2.2(2) Upg-Required -----------yes yes no no Do you want to continue with the installation (y/n)? [n] y Note: MDS 9500 series directors support a “hitless” upgrade.0(10/24/03) 1. Enter y to proceed with the upgrade.3 Note: The above command can also be run from a Telnet or SSH session.

3 system variable = bootflash:/9100-system-3.3 14-10 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 version 1. At that point.2 Copyright © 2008.2(3) Verify that the boot variables have been updated: # show boot kickstart variable = bootflash:/9100-kickstart-3. login to the switch.2. Skyline ATS.Step 3 Continue to observe the console as the boot variables are updated. and then the switch will perform a hitless failover from the active to the standby supervisor. Inc.2(3) system: Step 6 version 3. the configuration is saved to NVRAM and the switch resets to load the new image. the supervisor that was previously active will reload with the new image and come up as the standby.2(2) kickstart: version 3. Note: On an MDS 9500 series director. Step 4 Step 5 When the login prompt appears.1. Verify the kickstart and system software images have been updated: # show version Software BIOS: loader: version 1.2. the standby supervisor will first reload with the new image. .

2.3 9100-kickstart-3.2.Exercise Procedure 2: Cleaning up Bootflash Complete these steps: Step 1 Verify the contents of bootflash # dir bootflash: 14913536 14954496 67552289 67605711 Feb 14 21:17:33 2008 Feb 12 20:02:24 2008 Feb 14 21:16:57 2008 Feb 12 20:04:00 2008 9100-kickstart-3.2.2.3 9100-system-3.3 Copyright © 2008.2c 9100-kickstart-3.2. Skyline ATS.3 image files. Inc.2c 9100-system-3. # dir bootflash: 14954496 67605711 Feb 12 20:02:24 2008 Feb 12 20:04:00 2008 9100-kickstart-3.2c Step 4 Verify that bootflash only contains the current 3.2. # delete bootflash:9100-kickstart-3.2.2.2c Step 3 Delete the old system image file to free up space on your bootflash. # delete bootflash:9100-system-3.2. Lab Guide 14-11 .3 Step 2 Delete the old kickstart image file to free up space on your bootflash.

0. switch(boot)# dir bootflash: 14954496 Feb 12 01:12:13 2008 9100-kickstart-3. Configure the default gateway and mgmt0 interface (X refers to your pod number. you can recover the missing system image from a TFTP server. (y/n)? [n] y Step 7 Observe the console as the switch resets and loads the kickstart image. Step 8 Verify that the required system image is missing from bootflash. Exercise Procedure 1: Restoring a Missing or Corrupted System Image File Complete these steps: Step 1 Step 5 Access the system console. However. . Eventually you should see the following switch prompt. Inc. To simulate a corrupted or missing system file.3 Step 6 Reload the switch. This prompt indicates that the kickstart image loaded successfully. # reload This command will reboot the system.X.2.2 Copyright © 2008. Step 10 Enter global config mode. 14-12 Implementing Cisco Storage Networking Solutions (ICSNS) v3. switch(boot)# Note: A small subset of switch commands is available in this mode.255.X. first check the state of the management 0 interface: switch(boot)# show interface mgmt 0 mgmt0 is down. or 3 for MDS2): switch(boot)# config terminal Enter configuration commands. there is no ping command. Y refers to 5 for MDS1.2. you will simulate and recover from various troubleshooting scenarios that can occur when loading software images. one per line.Task 4: Troubleshooting Software Image Loads In this task.0 switch(boot)(config-if)# no shut switch(boot)(config-if)# exit switch(boot)(config)# ip default-gateway 10.0.254 switch(boot)(config)# end End with CNTL/Z. Skyline ATS.Y 255. For example. delete the active system file: # delete bootflash:9100-system-3. switch(boot)(config)# interface mgmt 0 switch(boot)(config-if)# ip address 10.255. Type “?” to see the list of available EXEC mode commands. but the system image did not.3 Step 9 To resolve this problem.

Inc.2. next you’ll see how to recover from a missing kickstart image file. loader> Note: A small subset of commands is available in this mode.3 Step 15 Reload the switch.3 67605711 Feb 14 23:13:39 2008 9100-system-3.Step 11 Recover the system image from the FTP server: switch(boot)# copy ftp://192. Exercise Procedure 2: Restoring a Missing or Corrupt Kickstart Image File Complete these steps: Step 1 Step 14 Login to the console. Skyline ATS. # reload This command will reboot the system.2.3 Note: Boot variable kickstart is set to bootflash:/9100kickstart-3.2. Notice the switch prompt.2.168.2. Copyright © 2008.2.3 Enter username: student Password: mdslab Step 12 Verify the download was successful: switch(boot)# dir bootflash: 14954496 Feb 14 22:55:26 2008 9100-kickstart-3. This prompt indicates that the boot loader did not locate and load the kickstart image. Lab Guide 14-13 .3 Note: Now that you’ve recovered from a missing system image file.3 bootflash:9100-system-3. Type “?” to see the available commands.198/9100-system-3. delete the active kickstart file: # delete bootflash:9100-kickstart-3. To simulate a corrupted or missing kickstart file.2.3 Step 13 Load the system image from the kickstart image prompt: switch(boot)# load bootflash:9100-system-3.0. (y/n)? [n] y Step 16 Observe the console as the switch resets.

0 Server: 0.0.. Y refers to 5 for MDS1 or 3 for MDS2): loader> ip address 10. However.0 Step 19 Configure the default gateway (X refers to your pod number): loader> ip default-gateway 10. similar to above.0.0.2.255.X.0.X.3 Step 18 To resolve this problem.0. Configure the default gateway and mgmt0 interface (X refers to your pod number.198/9100-kickstart-3.X. 14-14 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 Gateway: 10.Step 17 Verify that the required kickstart image is missing from bootflash.3 Note: This boots. you must first configure the mgmt 0 interface IP address (X refers to your pod number. .0.0.0 switch(boot)(config-if)# no shut switch(boot)(config-if)# exit switch(boot)(config)# ip default-gateway 10. ROM address 0xc000 Probing.0.[Intel EtherExpressPro100 82559ER]Ethernet addr: 0:0D:BD:84:FD:F5 Address: 10.2 Copyright © 2008.5 Netmask: 255. but does not download. the kickstart image to the switch. switch(boot)(config)# interface mgmt 0 switch(boot)(config-if)# ip address 10. Step 21 Enter global config mode.255. loader> dir bootflash: 9100-system-3.255. one per line. you can boot the kickstart image from a TFTP server.168. Y refers to 5 for MDS1.254 Address: 10.Y 255.255. Inc.255.X.X. Skyline ATS.255.255..X.0 Gateway: 0.0.0.254 switch(boot)(config-if)# end switch(boot)# End with CNTL/Z.0 Found Intel EtherExpressPro100 82559ER at 0xe800.2.Y 255.X.0.5 Netmask: 255.0.0 Server: 0.254 Step 20 Boot the kickstart image from the TFTP server loader> boot tftp://192.0. or 3 for MDS2): switch(boot)# config terminal Enter configuration commands.0.255.

Note: Now you’ve seen how to recover from missing or corrupted system and kickstart files.168.2.3 9100-system-3. Copyright © 2008.0.2.2.198/9100-kickstart-3.3 Step 24 Load the system image from the switch(boot) prompt: switch(boot)# load bootflash:9100-system-3.2. Skyline ATS.3 bootflash:9100-kickstart-3. Note that the above problem of finding yourself at the loader> or switch(boot)# prompts can also occur simply because the boot variables are missing or mistyped in the configuration file.3 Enter username: student Password: mdslab Step 23 Verify the download was successful: switch(boot)# dir bootflash: 14954496 67605711 Feb 12 20:02:24 2008 Feb 12 20:04:00 2008 9100-kickstart-3. Inc.3 Step 25 Login to the console.2. Lab Guide 14-15 .Step 22 Recover the kickstart image from the TFTP server: switch(boot)# copy ftp://192.

immediately press Ctrl-C: 00000589K Low Memory Passed 00000000K Ext Memory Passed Hit ^C if you want to run SETUP. Inc. In the following steps you will begin the initial steps needed to perform such a recovery. Complete these steps: Step 1 Reload the switch. Step 2 This should take you to the System BIOS Setup screen.2 Copyright © 2008. # reload This command will reboot the system. Note: BIOS stands for Basic Input Output System. CMOS stands for Complementary Metal Oxide Semiconductor. however you will not complete the process. 14-16 Implementing Cisco Storage Networking Solutions (ICSNS) v3. in which case you will not even be able to get to the loader> prompt. (y/n)? Step 1 Pay close attention to the console as the system reboots. .Exercise Procedure 3: Recovering From a Corrupted Bootflash File System A more serious problem can occur if there is a damaged or corrupted bootflash file system. Skyline ATS. When you see the following message.

Skyline ATS. These step. Note: At this point. you could use the <tab> key to move the “>” cursor to various fields and enter information similar to that shown above to configure the switch to boot the kickstart image from a TFTP server. are covered in detail in the MDS Configuration Guide. Exit Without Saving Changes? (Y/N): That completes this lab exercise. including re-formatting the bootflash file system. Press “y” when prompted to exit without saving changes. The steps for completing the process are similar to the previous procedures. Inc. Lab Guide 14-17 . Step 4 Step 5 Step 6 Press <Esc> to exit the Basic CMOS Configuration screen. Press <Esc> to exit the System BIOS Setup screen.Step 3 Press <Enter> to go the Basic CMOS Configuration screen. Copyright © 2008.

Skyline ATS.14-18 Implementing Cisco Storage Networking Solutions (ICSNS) v3. . Inc.2 Copyright © 2008.

Visual Objective Figure 1 illustrates the topology that should be working when you have completed this lab. You are encouraged to use Fabric Manager. . The primary difference is that the VSANs are numbered 100 and 200 rather than X1 and X2 (where X is your pod number). Final Topology The above topology is nearly identical to the one that you have been building up to throughout the course. Figure 1. Device Manager and the CLI to perform the configuration procedures. Also note that the VSAN port assignments force traffic to cross switch ISLs.Lab Exercise 15: Challenge Lab In this lab you will use what you have learned in previous labs to build a SAN from the ground up.

After completing this exercise. you be given very little direction. Unlike previous labs.Required Resources These are the resources and equipment required to complete this exercise:  2 MDS 9000 family Fibre Channel switches  2 Windows 2000 hosts running Fabric Manager and Device Manager  2 Windows 2000 servers with dual attached FC HBAs  A FC-AL JBOD disk device with at least four disks Exercise Objective The overall goal of this exercise is to practice the skills you’ve learned throughout the course to put the fabric back in a working state.2 Copyright © 2008. . you will be able to:  Configure Port Channels  Configure Zoning  Configure Load Balancing  Configure Traffic Engineering  Configure Port Mode Security  Configure Port Security  Configure static domain-ids 15-2 Implementing Cisco Storage Networking Solutions (ICSNS) v3. in this exercise. Skyline ATS. Inc.

Administratively brings up the MDS switch port. Displays the local zoning database. show interface brief show interface fcx/y config t int fcx/y no shut show flogi database vsan x show fcns database vsan x show port-security database show interface portchannel x show zoneset vsan x show zoneset active vsan x fcping pwwn xx:xx:xx:xx:xx:xx:xx:xx vsan x fctrace pwwn xx:xx:xx:xx:xx:xx:xx:xx vsan x config terminal zoneset activate name name vsan x show user-account name show role name name Shows what nodes have logged into your switch. Lab Guide 15-3 . Inc. Skyline ATS. Displays the port-security database. CLI Command Description Displays a summary of all ports. FC ping a pwwn FC trace to a pwwn in the specified vsan Activate a zoneset Display the roles assigned to a user Displays the rules assigned to a role Copyright © 2008. Displays the local zoning database. Displays a detailed output of the status of the specified port.Job Aids The following are some CLI commands that may be helpful in performing this lab. Displays detailed information about a specific port-channel. Displays the FC Name Server database for the specified VSAN.

you will be asked if you want to perform the initial setup. There is more than problem. and then download a configuration file that will introduce one or more problems. You will then troubleshoot the fabric problems. 15-4 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Skyline ATS. Problem Statement Your fabric was working fine. Exercise Procedure 1: Loading the Configuration Complete these steps: Step 1 Step 2 Step 3 Step 4 Stop all Fabric Manager and Device Manager sessions you may have running.. Erase your current startup configuration: # write erase Warning: This command will erase the startup-configuration. Answer “yes” and perform a basic switch configuraiton.Task 1: Troubleshooting MDS 9000 Fabric Problems In this task you will erase your switch configuration. Inc.) Login to your switch console (not Telnet or SSH) with the username admin and the password 1234qwer. reload the switch. Completely uninstall the Fabric Manager (see lab 2 if you are unsure how to achieve this. .2 Copyright © 2008. Would you like to enter the basic configuration dialog (yes/no): yes Step 7 Login with the username admin and the password 1234qwer. Do you wish to proceed anyway? (y/n) [n] y Step 5 Reload your switch: # reload This command will reboot the system. You have been assigned the task of resolving the problem. one of the junior technical support staff got his hands on the administrative password. Then last night. and now the hosts cannot see their storage. (y/n)? [n] y Step 6 When the switch reloads. You can troubleshoot them in any order.

Inc. Step 9 Configure your switch to meet the following design requirements: • • • • • • • • Create VSANs 100. Skyline ATS.Step 8 Install the Fabric Manager on your W2K system. Lab Guide 15-5 . 200 Configure Flow-based load balancing (Src-Dst) on VSAN 200 Set unique static domain IDs Configure Exchange-based load balancing Src-Dst-OxID on VSAN 100 PortChannel Membership: create two single link portchannels on FC1/1 and FC1/2 Traffic Engineering: Ensure that VSAN 100 traffic favors ISL1 (fc1/1-fc1/1) Traffic Engineering: Ensure that VSAN 200 traffic favors ISL2 (fc1/2-fc1/2) Zone Configuration: configure the following zonesets and zones: ZoneSet_Eng_100 ZoneS1D1 Server1 Disk1 ZoneS1D2 Server1 Disk2 ZoneSet_Sales_200 ZoneS2D3 Server2 Disk3 ZoneS2D4 Server2 Disk4 Make sure all devices are properly logged into the fabric Use device aliases • Port Mode Security: Set port mode security on all active ports Copyright © 2008.

.That concludes this lab exercise.2 Copyright © 2008. 15-6 Implementing Cisco Storage Networking Solutions (ICSNS) v3. Inc. Skyline ATS.

Sign up to vote on this title
UsefulNot useful