cisco storage design fundamentals - · pdf filelab 3: configuring high-availability san...

Cisco Storage Design Fundamentals

Version 3.0

Lab Guide

Table of Contents Lab Guide................................................................................................................................................1 Lab 1: Initial Switch Configuration...........................................................................................................3 Lab 2: Accessing Fibre Channel-Attached Disks..................................................................................15 Lab 3: Configuring High-Availability SAN Extension.............................................................................37 Lab 4: Configuring IVR for SAN Extension ...........................................................................................47 Lab 5: Exploring Fabric Manager Tools ................................................................................................59 Lab 6: Implementing iSCSI ...................................................................................................................69

CSDF

Lab Guide

Overview This Lab Guide includes these exercises:

Lab 1: Initial Switch Configuration

Lab 2: Accessing Fibre Channel-Attached Disks

Lab 3: Configuring High-Availability SAN Extension

Lab 4: Configuring IVR for SAN Extension

Lab 5: Exploring Fabric Manager Tools

Lab 6: Implementing iSCSI

Scenario Your customer, ACME Corporation, has an existing SAN in their Long Island, NY datacenter that consists of Cisco MDS 9000 switches. ACME now wants to implement remote SANs in several of their national and international facilities, using FCIP to connect the remote sites to the NY data center. They also want to test iSCSI for their mid-range applications. They have asked you to set up a proof-of-concept demonstration of a scalable and highly available SAN.

ACME wants you to demonstrate the following functions:

Verify accessibility of Fibre-Channel attached disks

Create a redundant, high-availability FCIP connection to the data center

Use Inter-VSAN Routing (IVR) to further increase the reliability of the FCIP links

Demonstrate a basic iSCSI configuration using dynamic configuration features to simplify iSCSI deployment

Lab 1: Initial Switch Configuration Complete this lab activity to practice what you learned in the related lesson.

Activity Objective In this activity, you will configure a switch for out-of-band management as if powering the switch up for the first time. After completing this activity, you will be able to meet these objectives:

Complete the initial switch configuration process

Install Fabric Manager and Device Manager

Navigate through the switch CLI structure

Visual Objective The figure illustrates what you will accomplish in this activity.


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

Any MDS 9000 Series Fibre Channel switch

Command List The table describes the commands used in this activity.

Command Description

write erase Erases the switch’s startup configuration

reload Reboots the switch

show ? Displays all the permissible features for the show command for the current user

show running-config Shows the running configuration

show interface brief Displays an interface status summary

show vsan Displays VSAN configuration and status

show version Displays current code version

Copyright © 2006, Cisco Systems, Inc. Lab Guide 5

Task 1: Complete the Initial Switch Configuration Process In this task, you will complete the initial switch configuration process. Each pod will be separated into two teams. Team 1 will apply configurations to the MDS 1 switch and Team 2 will apply configurations to the MDS 2 switch. Both teams can work in parallel unless stated otherwise.

Activity Procedure Perform these steps on the MDS switch assigned to your team:

Step 1 Access the console of your assigned switch (MDS-1 or MDS-2) by clicking on the Console button on the main Labgear screen. Press the Enter key once to see a switch login prompt, then log in.

Switch login: admin

Password: 1234qwer

Step 2 Clear the current startup configuration:

# write erase

Warning: This command will erase the startup-configuration.

Do you wish to proceed anyway? [y/n] [N]

Type y to proceed.

Step 3 Reboot the switch:

# reload

This command will reboot the system. (y/n)?

Type y to proceed.

Step 4 After the switch reboots (in about 2 minutes), it will automatically launch the setup process. This is the state you would find the switch in when you power up an MDS for the first time.

Answer the questions according to the following example, replacing your pod number where appropriate:

---- System Admin Account Setup ----

Enter the password for "admin": 1234qwer

Confirm the password for "admin":1234qwer

--- Basic System Configuration Dialog ---

This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system.

Press Enter in case you want to skip any dialog. Use ctrl-c at anytime to skip away remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): y

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: Pxx-MDS-y (where xx is your pod number and y is the switch number; y=1 for left switch, y=2 for the switch on the right. For example: P01-MDS-1)

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: <Enter>

Mgmt0 IP address : <X.X.X.X> (Use the IP address of your switch from the Lab Reference Guide.)

Mgmt0 IP netmask : <X.X.X.X> (Use the Netmask of your switch from the Lab Reference Guide.)

Configure the default gateway? (yes/no) [y]: <Enter>

IP address of the default gateway : <X.X.X.X> (Use the default gateway IP address from the Lab Reference Guide.)

Configure advanced IP options? (yes/no) [n]: <Enter>

Enable the telnet service? (yes/no) [y]: <Enter>

Enable the ssh service? (yes/no) [n]: <Enter>

Configure the ntp server? (yes/no) [n]: <Enter>

Configure default switchport interface state (shut/noshut) [shut]: <Enter>

Configure default switchport trunk mode (on/off/auto) [on]: <Enter>

Configure default zone policy (permit/deny) [deny]: <Enter>

Enable full zoneset distribution (yes/no) [n]: <Enter>

Step 5 A summary of the configuration will be displayed.

The following configuration will be applied:

switchname P01-MDS-1

interface mgmt0

ip address 10.0.61.5 255.255.0.0

no shutdown

ip default-gateway 10.0.61.254

telnet server enable

no ssh server enable

system default switchport shutdown

system default switchport trunk mode on

no zone default-zone permit vsan 1-4093

no zoneset distribute full vsan 1-4093

Note The displayed running-config is from pod P01-MDS-1, port numbers, IP addresses and names may differ from your pod.


Step 6 Press Enter twice to save the configuration.

Would you like to edit the configuration? (yes/no) [n]: <Enter>

Use this configuration and save it? (yes/no) [y]: <Enter>

Step 7 After the configuration is saved, a login prompt appears. You should observe the switch name change at the prompt. Enter your username and password.

MDS Switch

P04-MDS-1 login: admin

Password: 1234qwer

Activity Verification You have completed this task successfully when you have logged in to your switch after completing the setup script.


Task 2: Exploring the MDS 9000 CLI In this task, you will briefly explore the MDS 9000 command-line interface (CLI) and various short cuts you can use to simplify its use.

Exercise Procedure Both teams complete these steps on both MDS switches:

Step 1 At the prompt, type ? to view current command options

# ?

Note Press Enter to scroll one line at a time or press the space bar to scroll through the list of commands a page at a time. Press the q key to return you to the prompt.

Step 2 Display the following commands that begin with s, sh, and show and observe the results.

# s?

# sh?

# show ?

# show ru <Tab> <Enter>

Note Note that the <?> key displays a list of available options. The Tab key completes a command if you have typed enough characters to uniquely identify it.

Step 3 Display the current running configuration:

# show running-config

Step 4 Display the current running configuration again using an abbreviated command:

# sh ru

Tip For most commands, abbreviate the syntax, then press the Tab key to complete each word. For example, type sh<tab> ru<tab> . Note that you do not have to press the Tab key to use abbreviations. Pressing the Tab key simply shows you the command that will be executed.


Step 5 Display the status of the switch interfaces.

# show interface brief (or abbreviate as: sh int br)

Display VSAN information.

# show vsan

Record the following information:

VSAN Name State Operational State

Note that two VSANs, 1 and 4094, are created by default. VSAN 1’s operational state is down since there are no operational members in the VSAN.

Step 6 Ping your default gateway.

# ping <X.X.X.X> (Use the default gateway IP address from the Lab Reference Guide.)

Step 7 Observe the response from the gateway. Press Ctrl-C to stop the ping command.

Step 8 Enter configuration mode. Observe the change in the prompt.

# config (abbr: con)

(config)#

Step 9 Attempt to invoke the show version command.

(config)# show version

Are you successful? _________ (Answer: no)

Step 10 Type a question mark to view Configuration Mode command options.

Do you see the show command? _____________________(Answer: no)

Step 11 While in configuration mode, you can invoke executive mode commands by preceding the command with “do”:

(config)# do show version

Tip You can use the arrow keys to scroll up and down the list of previously entered commands. For example, you could use the up arrow key to scroll to the last time you typed show version, then use the left arrow key to move to the beginning of the line and insert do.


Task 3: Install Fabric Manager and Device Manager In this task, you will install the Fabric Manager and Device Manager applications on your remote Windows PC.

Activity Procedure Complete these steps on your remote Windows PC:

Step 1 On the main Labgear page, click the Desktop button to establish a terminal service session. Team 1 should use W2K Server 1, and Team 2 should use W2K Server 2.

Step 2 Login with administrator and cisco for the username and password.

Step 3 Open Internet Explorer from the remote desktop and enter the IP address you configured for your switch in Lab 1. The following page should load. Click the “Cisco Fabric Manager” link in the middle left of the page.


Step 4 The Fabric Manager Installation process will begin. Under the options screen, choose eth 0 (or the interface starting with 10.0.x.x, not 10.1.x.x) as your local interface, and click the “Use Global Device Aliases” button. Then click the Finish button.

Step 5 You will observe your PC download and install both the Fabric Manager and Device Manager applications. Installation will be complete in about one minute when you see the following prompt:


Step 6 Click the Options button.

.

Step 7 Type 1234qwer in the Password field, ensure that Load from Database is unchecked and that the proper local interface is selected which will be 10.0.x.x (Not 10.1.x.x. Then click Open. You will see an icon of the switch you are working on in the main window.

Step 8 Open Device Manager by right-clicking the switch icon and selecting Device Manager from the pop-up menu.

Tip You can also open Device Manager by double-clicking this icon or by clicking the Device Manager icon on your desktop.


Activity Verification You have completed this task successfully when you have opened Fabric Manager and Device Manager.

Lab 2: Accessing Fibre Channel-Attached Disks Complete this lab activity to practice what you learned in the related lesson.

Activity Objective In this activity, you will configure a switch to allow a host to access a disk resource. After completing this activity, you will be able to meet these objectives:

Configure VSANs and FC interfaces

Configure FC aliases, zones, and zonesets

Create a file system on a Windows host

Observe traffic flow using Device Manager's monitoring tools



2 MDS 9000 Series Fibre Channel switches

2 Windows 2000 management servers with Fabric Manager and Device Manager installed and each with a QLogic Fibre Channel HBA

1 JBOD with at least two disks


Task 1: Configure VSANs and FC Interfaces In this task, you will configure VSANs and FC interfaces.

Activity Procedure Perform these steps on your assigned MDS switch:

Step 1 Log in to Device Manager.

Step 2 Select FC > VSANs.

Step 3 In the VSAN window, click Create.


Step 4 Type xy in the VSAN Id field, where x is your pod number and y is your switch number. For example, for Pod 4, Switch 1, use VSAN ID 41.

Step 5 Click the … button next to the Interface Members field.

Step 6 Click the buttons for interfaces Host1-P1 and JBOD-1 from the lab reference guide, and then click OK. (This is usually fc1/5 and fc1/6, but may vary with some topologies.)

Step 7 In the Create VSAN window, click Create, then Close.

Step 8 Click the Membership tab in the VSAN window to verify your work. Verify the ID of the VSAN you created and the interfaces you assigned to it. Click Close.


Step 9 In the Device Manager window, click and drag your mouse cursor over both interfaces Host1-P1 and JBOD-1 from the lab reference guide to select both interfaces (if fc1/5 and 1/6 since they are adjacent.) Otherwise place your cursor over each of the interfaces, right-click, and select Enable from the pop-up menu.

Activity Verification Complete these steps to verify your configuration:

Step 1 In Device Manager, click the FC > Name Server menu option.


Step 2 After Device Manager conducts its next poll you will also notice that interfaces Host1-P1 and JBOD-1 have F and FL designators for their port types. The fact that both your host and the disks in your JBOD now appear in the Name Server window indicates that those devices have logged into the fabric. Note that the VSAN Id is also displayed.

Tip You can click Refresh button to force Device Manager to poll the switch if you don’t see any devices.

Step 3 Click Close.

You have successfully completed this task when you observe your host and disks in the Name Server window and verify that all FC devices are assigned to the appropriate VSAN.


Task 2: Create FC Aliases, Zones, and Zonesets In this task, you will configure FC aliases, zones, and zonesets.

Activity Procedure Perform these steps on your assigned MDS switch:

Step 1 Log in to Fabric Manager.

Step 2 Click the Layout Map button, as shown in the following screen capture, to reposition the devices in the window.

Step 3 Right-click on the fabric loop icon and click Expand in the pop-up menu. This will display all the devices available in the JBOD.

Step 4 Click the Map Layout button again to clean up the display.


Step 5 In the upper-left corner of the window, click on the + next to the Fabric 10.0.x.y folder to expand that folder tree.

Step 6 Right-click on the VSAN you created in Lab 1 and select Edit Local Full Zone Database….

Step 7 In the Edit Local Full Zone Database window, right-click on Aliases and select Insert….


Step 8 Name the alias Hosty (where y is your switch number 1 or 2) and select the WWN for your host. Your host WWN will be the WWN that does not begin with “Seagate.”

Step 9 Click OK.

Step 10 Right-click on Aliases again and select Insert.

Step 11 This time, name the alias Disky (where y is again your switch number) and select a WWN from the list of available disks.

Caution Your JBOD is connected to both MDS switches in your pod, so the team working on the other MDS switch in your pod will see the same disks. Coordinate with the other team working on your pod and select a different disk than the one they are using! Note that the first octet of the disk WWN (21 in the example below) does not uniquely identify the disk—the other team will see the same WWNs preceded by 20.


Step 12 Right-click Zones and select Insert.

Step 13 Name the new zone z1. Click OK.

Step 14 Right-click on Zoneset and select Insert.


Step 15 Name the new zoneset zs1. Click OK.

Step 16 Drag and drop both of your newly created aliases Hosty and Disky into the zone you just created.

Step 17 Next, drag and drop the zone z1 into the zoneset zs1.

Step 18 Click Activate… to activate the zoneset.

Step 19 In the Save Configuration dialog, click Continue Activation.

Step 20 Allow a few moments for the configuration to be saved. When you see the “Success” message in the lower-left corner of the Edit Local Full Zone Database window, click Close.



Step 1 In the main Fabric Manager window, expand your VSANxy folder, then expand the zoneset zsy folder.

Step 2 Click the zone zy that you created in the previous steps. Observe in the map view that the zoned path is outlined in yellow.


Task 3: Create a File System on a Windows Host In this task, you will create a file system on your Windows server.

Activity Procedure Perform these steps on your assigned Windows PC:

Step 1 On your Windows server desktop, right-click on My Computer and select Manage.


Step 2 Click Disk Management, then right-click on the disk that is not labeled Disk0.

Caution Disk 0 is your local disk. Do not select Disk 0!

Note If your Windows Server can not see your disk yet, then right click on Disk Management and select Rescan Disks. If your host can still not see your disks, then on your Desktop, click the Start button, Shutdown, and Log Off Administrator. Then re-log into your server, right click on My Computer and select Manage. You should be able to see the disk you zoned at this time.


Step 3 Select Properties from the pop-up menu.


Step 4 Verify that this is a FC-attached disk. The Adapter Name field should show that the disk is attached to the Qlogic Fibre Channel Adapter.

Step 5 Click OK.


Step 6 In the Computer Management window, right-click in the area labeled Unallocated and select Create Partition…. If the disk does not have unallocated space, then right-click the existing partition and delete the partition first.


Step 7 The Create Partition Wizard will open. Take most of the default settings, but enter 5000MB for the partition size, and be sure to check the Quick Format box. At the end of the wizard click Finish. Note the drive letter assigned to the new partition.



Step 1 Because you are using Windows Terminal Services to access the remote PC, you need to log out and log in again before you can access the new disk volume.

From the Windows desktop, click Start > Shutdown, then select Log off administrator and click OK.

Step 2 On the Labgear webpage, click the Desktop button to reestablish the terminal service session. As usual, Team 1 should use W2K Server 1, and Team 2 should use W2K Server 2.

Step 3 Log in with administrator and cisco for the username and password.

Step 4 Open My Computer.

Step 5 Double-click on the volume with the drive letter that you assigned in the previous steps, and verify that the volume window is displayed.


Task 4: Observe Traffic Flow Using Device Manager In this task, you will observe traffic flow using Device Manager's monitoring tools.

Activity Procedure Complete these steps on your assigned Windows PC:

Step 1 In Device Manager, select Interface > Monitor > FC Enabled.

Step 2 In the Interval drop-down field, select 2s to set a 2-second update interval. Do not close this window since you will return to it in a moment.


Step 3 On your Windows desktop, right-click My Computer and select Explore.

Step 4 Drag and drop a large folder from your local C: drive into the new partition that you created earlier. Use something large like the Program Files folder.

Step 5 Return to the Device Manager FC Interface Monitor window. You should observe traffic running through both interfaces 1/5 and 1/6 as data is copied from your local disk to the disk you set up in the last task. You may also observe other statistics as well while the copy process is underway.


Answer Key: Accessing Disks via Fibre Channel When you complete this activity, your switch running-configuration file will be similar to the following, with differences that are specific to your device or workgroup.

Note The output from the show running-config command that is displayed below has been edited to show only the items that you configured in this lab.

P6-MDS-1# sh run

vsan database

vsan 61

vsan database

vsan 61 interface fc1/5

vsan 61 interface fc1/6


fcalias name Host1 vsan 61

member pwwn 21:00:00:e0:8e:0e:a8:12

fcalias name Disk1 vsan 61

member pwwn 21:00:00:04:cf:20:b7:3f

zone name z1 vsan 61

member fcalias Host1

member fcalias Disk1

zoneset name zs1 vsan 61

member z1

zoneset activate name zs1 vsan 61

interface fc1/5

no shutdown

interface fc1/6

no shutdown

Lab 3: Configuring High-Availability SAN Extension

Complete this lab activity to practice what you learned in the related lesson.

Activity Objective In this activity, you will configure FCIP tunnels for SAN extension. You will then configure the FCIP tunnels into a PortChannel to create a high-availability FCIP link. After completing this activity, you will be able to meet these objectives:

Configure FCIP tunnels for SAN extension

Configure a PortChannel with FCIP links




Two MDS 9000 Series Fibre Channel switches either with IPS modules or integrated Gigabit Ethernet ports.

Two Windows 2000 servers, each with a FC HBA. A JBOD with at least two disks

Confirm with your instructor whether you will be using the Firefly BB1, Firefly BB2 or Cisco Pod Configuration for the following lab exercise.

Consult the Lab Reference Guide document to determine the port mapping and addressing requirements of your particular pod configuration.

Caution Note the topology configuration requirements for Firefly BB1 pods. Teams will configure FCIP connectivity between odd and even numbered pods on Firefly BB1 pods only! On all other pod configurations teams will configure FCIP connectivity between the switches within the same pod.

Command List The table describes the commands used in this activity.

Command Description

show interface brief Displays status for all interfaces with less detail.

show port-channel database Display the PortChannel database


Task 1: Configure FCIP Tunnels In this task, you will configure FCIP tunnels for SAN extension.

Activity Procedure Both teams will create a single FCIP tunnel using the wizard:

Step 1 Open Fabric Manager and launch the FCIP Tunnel Wizard by clicking the button show in the following screen capture.

Step 2 Enter the Management IP address of the other switch in your pod (Switch 1 team enter the Management IP address of MDS-2, Switch 2 team enter the Management IP address of MDS-1)

Note Use the IP addresses specified for your pod topology in the Lab Reference Guide.

Step 3 Click Next.


Step 4 If you are working on switch 1, create an FCIP tunnel between GIG-1 and GIG-1of both switches. If you are working on switch 2 create an FCIP tunnel between GIG -2 and GIG -2 of both switches.

Note GIG-1 and GIG-2 refer to the ports specified for your topology in the Lab Reference Guide.

Step 5 Uncheck the checkbox labeled Use Large MTU Size.

Note The IP switches that connect the MDS switches in this lab do not support large MTU sizes.

Step 6 Click Next.

Step 7 Click Next to accept the default settings in step 3 of 4: Specify Tunnel Properties.


Step 8 In step 4 of 4: Create FCIP ISL, enter the IP addresses and subnet mask corresponding to your Gigabit Ethernet ports. Use the Lab Reference Guide to determine the IP addresses and subnet masks. Be sure to include the subnet mask by the /network bit notation, ie /16 or /24 depending on your topology.

Note You must enter the address and mask in the CIDR format (<IP Address>/<Mask>) or else you will receive a “Bad IP Address” error message.

Step 9 Click the Trunk button for Trunk Mode.

Step 10 Click Finish. The Wizard will inform you that FCIP has not been enabled yet and will ask you if you would like to enable it. Click Yes.


Activity Verification Complete these steps to verify your configuration:.

Step 1 Open a command-line interface (CLI) window by right-clicking on either switch and selecting Command Line Interface.

Step 2 Type the show interface brief | include fcip command. If the FCIP tunnels indicate “trunking” then they are operating properly.

P06-MDS-1# sh int br | include fcip

fcip2 1 auto on trunking TE 1 GigabitEthernet1/1 --

fcip3 1 auto on trunking TE 2 GigabitEthernet1/2 --

Note The include function can be used with many show commands to filter the output.

Step 3 In the Fabric Manager topology pane, click the Layout Map button

Step 4 Right-click the link between MDS-1 and MDS-2 and select Expand.

Step 5 Place your mouse over the dotted lines to confirm that both FCIP tunnels are displayed.


Task 2: Configure a PortChannel In this task, you will configure a PortChannel using the two FCIP links that you and your teammates created in Task 1.

Activity Procedure

Note Only one team should perform this task while the other team observes.

Perform these steps on one MDS switch in your pod:

Step 1 In Fabric Manager, click the Port Channel wizard button as shown in this screen capture.

Step 2 In step 1 of 3: Select Switch Pair, verify that both of your pod’s switches are selected and click Next.


Step 3 In step 2 of 3: Select ISLs, verify that both FCIP tunnels are in the Selected list.

Step 4 Uncheck the Dynamically form Port channel Group from selected ISLs checkbox.

Step 5 Click Next.

Step 6 In step 3 of 3: Create Port Channel, accept the default Channel Ids and Descriptions, accept the default 1 to 4093 in the VSAN List field, and ensure the trunk mode is set to trunk. Click Finish.


Step 7 When asked if you want to continue, click Yes.


Step 1 From the CLI, enter the show port-channel database command. Your display should resemble the following:

P04-MDS-1# sh port-c d

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, 2 ports up

Ports: fcip2 [up] *

fcip3 [up]

Step 2 In Fabric Manager, verify the PortChannel by placing your mouse cursor over the line between the switches. Your display should resemble the following.


Answer Key: Configuring High-Availability SAN Extension When you complete this activity, your switch running-configuration file will be similar to the following, with differences that are specific to your device or workgroup. The following is only a partial output that shows the changes you made to the configuration file during this task.

P6-MDS-1# sh run

fcip enable

fcip profile 1

ip address 10.1.66.11

fcip profile 2

ip address 10.1.66.12

interface port-channel 1

channel mode active

switchport description To P06-MDS-2

switchport mode E

interface fcip2

use-profile 1

peer-info ipaddr 10.1.66.21

switchport mode E

channel-group 1 force

no shutdown

interface fcip3

use-profile 2

peer-info ipaddr 10.1.66.22

switchport mode E

channel-group 1 force

no shutdown

interface GigabitEthernet1/1

ip address 10.1.66.11 255.255.0.0

no shutdown


ip address 10.1.66.12 255.255.0.0

no shutdown

Lab 4: Configuring IVR for SAN Extension Complete this lab activity to practice what you learned in the related lesson.

Activity Objective In this activity, you will configure Inter-VSAN Routing (IVR) for SAN extension. After completing this activity, you will be able to meet these objectives:

Create a transit VSAN

Convert dynamic domain IDs to static domain IDs to support IVR

Create an inter-VSAN route using the IVR Wizard




Two Windows 2000 servers, each with a FC HBA. A JBOD with at least two disks


Task 1: Create a Transit VSAN In this task, you will create a transit VSAN.

Activity Procedure Perform these steps on one MDS switch in your pod:

Note Only one team should complete this task.

Step 1 In Fabric Manager, right-click All VSANs in the Logical Domain pane in the upper-left corner of the Fabric Manager window.

Step 2 In the Create VSAN window, ensure that both switches are checked.

Step 3 In the VSAN Id field, type 99.

Step 4 Name the new VSAN Transit VSAN.

Step 5 Click Create.



Step 1 Click Transit_VSAN(99) in the Logical Domains window pane.

Step 2 Observe in the table to the right that the VSAN was created on both switches. Note that this VSAN does not contain any active interfaces yet.


Task 2: Set Unique Static Domain IDs In this task, you will convert dynamic domain IDs to static domain IDs to support IVR.

Activity Procedure Both teams should complete these steps on their assigned MDS switches:

Step 1 In Device Manager, select FC > Domain Manager.

Step 2 Click the Configuration tab.


Step 3 Enter the following settings:

The team working on MDS-1 should enter:

VSAN x1 Domain ID 11

VSAN 99 Domain ID 91

Type: Static

Restart Disruptive

The team working on MDS-2 should enter:

VSAN x2 Domain ID 22

VSAN 99 Domain ID 92

Type: Static

Restart Disruptive

Step 4 Click Apply.

Step 5 Click Yes to confirm the changes.


Activity Verification Click the Domains tab and verify that the Domain IDs have changed. You may need to click the Refresh button a few times to register all the changes.

Note that the Domain IDs are displayed in both decimal (e.g. 235) and hexadecimal (0xeb) format.


Task 3: Create an Inter-VSAN Route In this task, you will create an inter-VSAN route using the IVR Wizard.


Step 1 In Fabric Manager, click the IVR Zone Wizard button.

Step 2 In step 1 of 5: Select VSANs, select all the VSANs that will participate in IVR. In this lab, select all VSANs except VSAN 1. You can hold down the Shift key and click in the Available list to select multiple VSANs, then click the button to move them from the Available list to the Selected list. Click Next.


Step 3 In step 2 of 5: Select End Devices, select the devices that should be able to communicate:

Team 1 should select Host1 from the Available pane and click Add to move it to the Selected Pane.

Team 2 should select Host 2.

Both teams should then select a disk from the VSAN that was created on the other switch. That is, the team on MDS-1 should select a disk from VSAN x2 and the team on MDS-2 should select a disk from VSAN x1.

Both teams must coordinate with each other and select disks that have not and will not be part of any existing zone in the fabric. Use the table below to record your choices and coordinate with the other team in your pod.

Zone Last three hex numbers of WWN (xx:xx:xx)

Switch 1 Native Zone

Switch 2 Native Zone

Switch 1 IVR Zone

Switch 2 IVR Zone


Step 4 In step 3 of 5: Select Transition VSAN, select Transit_VSAN(99) as your Transit VSAN and click Next.

Step 5 In step 4 of 5: Select Zone, Team 1 should accept the default IVR Zone and Zoneset names. Team 2 should change the Zone name to IvrZone2 if this is not the default already.


Step 6 In step 5 of 5: Review Actions, verify the actions that will be performed to create the IVR topology and zones, and then click Finish.

Step 7 A dialog will appear to inform you that the IVR configuration you just created will be copied to other IVR-enabled switches. Click Continue Activation.


Step 8 Observe that all processes complete successfully and wait for the “Success” notice in the bottom left-hand corner of the window. Click Close.

Activity Verification In the Fabric Manager Logical Domains pane, click on each zone that you created in the lab thus far and observe the various paths from host to disk outlined in yellow.


Answer Key: Configuring IVR for SAN Extension When you complete this activity, your switch running-configuration file will be similar to the following, with differences that are specific to your device or workgroup. Only the commands that you affected in this last lab are shown.

P4-MDS-1# sh run

vsan 99 name "Transit_VSAN"

fcdomain fcid persistent vsan 1

fcdomain domain 11 static vsan 41


fcdomain domain 91 static vsan 99


ivr enable

ivr vsan-topology database

autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:1a:15:c0 vsan-ranges 1,41,99

autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:1a:18:c0 vsan-ranges 42,99

ivr vsan-topology activate

ivr zone name IvrZone1

member pwwn 21:00:00:e0:8e:0e:a4:82 vsan 41

member pwwn 22:00:00:20:37:e6:ea:50 vsan 42

ivr zone name IvrZone2

member pwwn 21:00:00:e0:8b:0e:a9:92 vsan 42

member pwwn 21:00:00:20:37:e6:eb:0a vsan 41

ivr zoneset name IvrZoneSet1

member IvrZone1

member IvrZone2

ivr zoneset activate name IvrZoneSet1 force

Lab 5: Exploring Fabric Manager Tools Complete this lab activity to practice what you learned in the related lesson.

Activity Objective In this activity, you will use Fabric Manager Tools to verify switch health, end to end connectivity and fabric configuration. After completing this activity, you will be able to meet these objectives:

Identify switch health conditions using the Switch Health Analysis tool

Verify that devices can communicate using the End to End Connectivity tool

Confirm fabric configuration consistency using the Fabric Configuration Analysis tool

Visual Objective The figure illustrates the topology you will use for this activity.



Two Windows 2000 servers, each with a FC HBA and Fabric Manager / Device Manager installed.

A JBOD with at least two disks


Task 1: Perform a Switch Health Analysis The Fabric Manager Switch Health analysis tool helps you to determine the status of the components of a specific switch. The Switch Health tool can identify problems such as exceeding environmental thresholds, high processor utilization, line card failures, port and port link failures, domain manager isolation, and name server rejects.

In this task, you will use the Switch Health tool to determine the status of your switch.

Activity Procedure Step 1 Select Switch Health from the Fabric Manager Tools menu.

Step 2 Click Start and observe the results. Note that the the Ignore Interface Link Failures checkbox is checked by default.

Step 3 Uncheck the Ignore Interface Link Failures checkbox.


Step 4 Launch Device Manager and enable an unused FC interface. Right click on interface fc1/11 and select enable.

Step 5 Return to the Switch Health Analysis window and click Start.

Observe the Interface Link Failures identified by the Switch Health Analysis tool.

Step 6 Select Close to exit the Switch Health Analysis window.

Step 7 Return to Device Manager and disable the ISL that you enabled in Step 4.


Task 2: Perform an End-to-End Connectivity Analysis You can use the Fabric Manager End-to-End Connectivity tool to determine connectivity and routes between devices in the switch fabric. The End-to-End Connectivity tool checks to see that every pair of end devices in an active zone can talk to each other, by using a ping test and by determining if they are in the same VSAN. This option uses versions of the ping and traceroute commands that have been modified for Fibre Channel networks.

The End-to-End Connectivity window displays the selected end points with the source and target ports on the switch to which each end point is attached.

The output shows all the requests which have failed. The possible descriptions are:

Ignoring empty zone—No requests are issued for this zone.

Ignoring zone with single member—No requests are issued for this zone.

Source/Target are unknown—No nameserver entries exist for the ports or no ports were found.

Both devices are on the same switch—The devices are not redundantly connected.

No paths exist.

Only one unique path exists.

VSAN does not have an active zone set.

Average time (micro secs)—The latency value was more than the threshold supplied.

In this task, you will use the End to End Connectivity tool to determine connectivity and routes between devices in your switch fabric.

Activity Procedure Step 1 Select End to End Connectivity from the Fabric Manager Tools menu.


Step 2 Select the VSAN that contains zone membership for your switch from the In VSAN field drop-down menu:

If you are working on MDS-1, select VSAN00x1 and zone z1.

If you are working on MDS-2, select VSAN00x2 and zone z2.

Step 3 Click Analyze.

Step 4 When polling completes, observe the All (2) requests succeeded message in the lower right corner of the window.


Step 5 In Device Manager, right-click interface fc1/5 and select Disable.

Step 6 Click Yes to confirm disabling interface fc1/5.

Step 7 Return to the Fabric Manager End to End Connectivity Analysis window and click Analyze again.

Step 8 Observe the message in the Issues > Description field that identifies why the connectivity check has failed.

Step 9 Click Clear to clear the issues table.

Step 10 In Device Manager, right-click interface fc1/5 and select Enable.

Step 11 Repeat Step 7 and confirm that the connectivity check succeeds with the message output All (2) requests succeeded.


Task 3: Perform a Fabric Configuration Analysis In this task, you will use the Fabric Manager Fabric Configuration analysis tool to analyze the configuration of a switch by comparing the current configuration to a specific switch or to a saved policy file.

Use a policy file to define the rules to be applied when running the Fabric Configuration analysis. You can create a policy file by saving a switch configuration to a file.The system saves the rules selected for the specified switch. You can then compare other switches against the configuration in the policy file.

Activity Procedure Step 1 Select Fabric Configuration from the Fabric Manager Tools menu.

Step 2 Select the other switch in your pod from the Policy Switch drop-down menu. If you are working on MDS-1, select MDS-2 as the policy switch; if you are working on MDS-2, select MDS-1 as the policy switch.

Step 3 Click Compare.


Step 4 Observe the discrepancies identified by the Fabric Configuration tool.

Note The missing and extra VSAN discrepancies are to be expected; in the previous lab you configured IVR to enable communication between selected devices in VSAN x1 and VSAN x2.

Step 5 Click Clear.

Step 6 Click Rules….

Step 7 Clear the check boxes for the VSAN and Syslog rules in the Fabric Rules window.

Step 8 Click OK.


Step 9 Return to the Fabric Configuration Analysis window.

Step 10 Click Compare again.

Step 11 Confirm that there are no longer any inconsistencies identified.

Step 12 Click Close.

Activity Verification You have successfully completed this exercise when you have used the Switch Health, End-to-End Connectivity, and Fabric Configuration tools to analyze the health, connectivity, and consistency of the switches in your topology.

Lab 6: Implementing iSCSI Complete this lab activity to practice what you learned in the related lesson.

Activity Objective In this activity, you will connect a host to a storage resource using iSCSI. After completing this activity, you will be able to meet these objectives:

Enable iSCSI features and iSCSI interfaces

Create an iSCSI zone using Fabric Manager

Log into an iSCSI target and mount the disk to a file system




Two Windows 2000 servers, each with the Microsoft iSCSI Initiator driver installed

A JBOD with at least two disks


Task 1: Complete the Initial Switch Configuration Process In this task, you will complete the initial switch configuration process to reset your switch to an unconfigured state. Team 1 will apply configurations to the MDS-1 switch and Team 2 will apply configurations to the MDS-2 switch. Both teams should work in parallel unless stated otherwise.


Step 1 Access the console of your assigned switch (MDS-1 or MDS-2) by clicking on the console button on the main Labgear screen. Press the Enter key once to see a switch login prompt, then log in.

Switch login: admin

Password: 1234qwer

Step 2 Clear the current startup configuration:

# write erase

Warning: This command will erase the startup-configuration.

Do you wish to proceed anyway? [y/n] [N]

Type y to proceed.

Step 3 Reboot the switch:

# reload

This command will reboot the system. (y/n)?

Type y to proceed.

Step 4 After the switch reboots (in about 2 minutes), it will automatically launch the setup process. This is the state you would find the switch in when you power up an MDS for the first time.

Answer the questions according to the following example, replacing your pod number where appropriate:

---- System Admin Account Setup ----

Enter the password for "admin": 1234qwer

Confirm the password for "admin":1234qwer

--- Basic System Configuration Dialog ---

This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system.

Press Enter in case you want to skip any dialog. Use ctrl-c at anytime to skip away remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): y

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: Pxx-MDS-x (where xx is your pod number and x is the switch number; for example: P01-MDS-1)

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: <Enter>

Mgmt0 IP address : <X.X.X.X> (Use the IP address of your switch from the Lab Reference Guide.)

Mgmt0 IP netmask : <X.X.X.X> (Use the Netmask of your switch from the Lab Reference Guide.)

Configure the default gateway? (yes/no) [y]: <Enter>

IP address of the default gateway : <X.X.X.X> (Use the default gateway IP address from the Lab Reference Guide.)

Configure advanced IP options? (yes/no) [n]: <Enter>

Enable the telnet service? (yes/no) [y]: <Enter>

Enable the ssh service? (yes/no) [n]: <Enter>

Configure the ntp server? (yes/no) [n]: <Enter>

Configure default switchport interface state (shut/noshut) [shut]: <Enter>

Configure default switchport trunk mode (on/off/auto) [on]: <Enter>

Configure default zone policy (permit/deny) [deny]: <Enter>

Enable full zoneset distribution (yes/no) [n]: <Enter>

Step 5 A summary of the configuration will be displayed:

The following configuration will be applied:


interface mgmt0

ip address 10.0.61.5 255.255.0.0

no shutdown

ip default-gateway 10.0.61.254

telnet server enable

no ssh server enable

system default switchport shutdown

system default switchport trunk mode on

no zone default-zone permit vsan 1-4093

no zoneset distribute full vsan 1-4093

Note The displayed running-config is from pod P01-MDS-1, port numbers, IP addresses and names may differ from your pod.


Step 6 Press Enter twice to save the configuration.

Would you like to edit the configuration? (yes/no) [n]: <Enter>

Use this configuration and save it? (yes/no) [y]: <Enter>

Step 7 Answer Yes to save the running-configuration to startup-configuration

Would like to save the running-configuration to start- configuration? (yes/no)[n] Y <Enter>

Step 8 After the configuration is saved, a login prompt appears. You should observe the switch name change at the prompt. Enter in your username and password:

MDS Switch

P04-MDS-1 login: admin

Password: 1234qwer


Task 2: Enable iSCSI and Configure iSCSI Interfaces In this task, you will enable iSCSI features and configure iSCSI interfaces.

Activity Procedure Each team complete these steps on your respective switches:

Step 1 In Device Manager, click Admin > Feature Control.


Step 2 Enable iSCSI and iSCSI VSAN interface membership and click Apply. When the Status field for these features shows “enabled” and the Result field shows “success”, click Close. You can click the Refresh button to force Device Manager to update the display.

Step 3 Right-click on port GIG-1 and select Configure. (Refer to the Lab Reference Guide to locate the port named GIG-1.)


Step 4 On the gigEx/y tab, change the Admin mode to up, and enter the IP address for this interface from the Lab Reference Guide.

Step 5 Click the iSCSI tab.

Step 6 Change the admin mode to up, and select PortVSAN 1. Click Apply.


Note You will use VSAN 1 in this lab to simplify the procedure. However, Cisco recommends that you do not use VSAN 1 in production environments for security reasons.

Step 7 A dialog will indicate that I/O may be affected by your changes. Click Yes.

Step 8 Click Close to close the gigEx/y window.

Step 9 In Device Manager, select IP > iSCSI.

Step 10 Click the Globals tab and uncheck the chap box so that the switch will not require the host to authenticate. Click Apply.


Step 11 Click the Targets tab and check the Dynamically Import iSCSI targets box to allow the MDS to automatically create iSCSI configurations for all active Fibre Channel disk targets. Click Apply.

Step 12 In the main Device Manager window, right-click interface 1/6 and select Enable.


Task 3: Create iSCSI Zones In this task, you will create an iSCSI zone using Fabric Manager.

Activity Procedure Complete these steps:

Step 1 In Fabric Manager, click the iSCSI Setup button as shown in the following figure.

Step 2 In step 1 of 3: Configure Initiator, enter the IP address of your Windows PC’s iSCSI NIC from the Lab Reference Guide. Click Next.


Step 3 In step 2 of 3: Select Targets, select one of the disks in the Available list and click Add to move it to the Selected list. Click Next.

Step 4 In step 3 of 3: Select Zone, accept the default zone and zoneset names and click Finish.


Step 5 Click Continue Activation.

Step 6 Observe the configuration processes complete and verify that a Success message is displayed in the lower left corner of the iSCSI wizard window. Click Close.



Step 1 In the Fabric Manager Logical Domains pane, expand VSAN0001 > ZoneSet1 and click ISCSI-Zone1.

Step 2 Verify that the ISCSI-Zone1 members appear in the details pane and on the topology map.


Task 4: Access an iSCSI-Attached Disk from a Windows Host In this task, you will log into an iSCSI target and mount the disk to a Windows file system.

Activity Procedure Complete these steps:

Step 1 Double click on the Microsoft iSCSI initiator icon on your desktop.

If you don’t have the MS iSCSI Initiator on your Desktop already then do the following:

Click the Start button then the Run button, enter \\bb-server\tftp then click OK.

Follow the path to software/Microsoft-iSCSI and drag and drop the Microsoft-iSCSI to your desktop. Open the folder, extract the driver, and install it.


Step 2 Click the Discovery tab.

Step 3 Click Add.

Step 4 Type the IP address of your iSCSI interface. Use the address you entered in Task 3: Create iSCSI Zones, Step 2, from the Lab Reference Guide. Click OK.


Step 5 Click the Targets tab.

Step 6 Click Log On….


Step 7 Accept the default IQN name and click OK.

Step 8 Verify that the Status field on the Targets tab changes to Connected for the disk to which you are connecting.


Step 1 In Fabric Manager, expand the VSAN folder in the Logical Domain window and click on the iSCSI zone that you created. The zoned path will be outlined in yellow.


Step 2 On your remote Windows desktop, right-click My Computer and select Manage.

Step 3 Click Disk Management.

Step 4 Right-click the Disk 1 label and select Properties. (Do not touch Disk 0.)

Step 5 Confirm that the Adapter Name for the disk is Microsoft iSCSI Initiator. If it is not, repeat for disks 2, 3, and so forth until you find the iSCSI-attached disk.


Answer Key: Implementing iSCSI When you complete this activity, your switch running-configuration file will be similar to the following, with differences that are specific to your device or workgroup.

P06-MDS-1# sh run

iscsi enable

iscsi interface vsan-membership

iscsi initiator ip-address 10.1.66.2

vsan 1

iscsi import target fc

iscsi authentication none

iscsi initiator ip-address 10.1.66.2

static nWWN 22:04:00:0d:ec:1a:15:82

static pWWN 22:03:00:0d:ec:1a:15:82


zone name ISCSI-Zone1 vsan 1

member pwwn 21:00:00:04:cf:3b:08:84

member pwwn 22:03:00:0d:ec:1a:15:82

zoneset name ZoneSet1 vsan 1

member ISCSI-Zone1

zoneset activate name ZoneSet1 vsan 1

interface mgmt0

ip address 10.0.66.5 255.255.0.0

interface iscsi1/1

no shutdown


ip address 10.1.66.11 255.255.0.0

no shutdown

interface fc1/6

no shutdown

Firefly BB1 Pod Configuration

Table 1: mgmt0 and Server IP Addresses

mgmt0 mgmt NIC iSCSI NIC

MDS-1 10.0.5x.5 Server 1 10.0.5x.1 10.1.5x.2

MDS-2 10.0.5x.3 Server 2 10.0.5x.2 10.1.5x.6

Default Gateway =Mask =

10.0.50.254 255.255.0.0

Table 2: VSAN Names and IDs

Y = x00 Name = VSANY_HR

Z = x01 Name = VSANZ_DEV Example for Pod-5:

VSAN500_HR, VSAN501_DEV

Table 3: MDS 9000 Port Map fc1/1 fc1/2 fc1/3 fc1/5 fc1/6 fc1/15 fc1/16 gig2/1 gig2/2 gig2/3 gig2/4

MDS-1 ISL-1 ISL-2 ISL-3 HOST1-P1 JBOD-1 HOST2-P2 SD-1 GIG-1 GIG-2 GIG-3 GIG-4

MDS-2 ISL-1 ISL-2 ISL-3 HOST2-P1 JBOD-2 HOST1-P2 na na na na na

Table 4: GigE Interfaces Mask = 255.255.0.0

Interface Site A Site B iSCSI

Primary gig2/1 10.1.5x.11 gig2/1 10.1.5x.11 iSCSI-1 gig2/3 10.1.5x.21

Secondary Pod X MDS-1 gig2/2 10.1.5x.12

Pod Y MDS-1 gig2/2 10.1.5x.12

MDS-1 iSCSI-2 gig2/4 10.1.5x.22

Table 5: IVR Domain IDs and Port VSAN Assignments VSAN 2 VSAN 3 VSAN 4 VSAN 5 VSAN 99

Domain ID 12 13 na na 95 MDS-1 Port assignment fc1/6 fc1/5 na na na Domain ID na na 14 15 92 MDS-2 Port assignment na na fc1/5 fc1/6 na

Firefly BB1 TFTP / RADIUS / TACACS+ / SMTP Server IP Address = 10.0.50.1

Firefly BB2 Pod Configuration

SSM

PAA

Px-MDS-1

Console

1/6 1/6

1/1, 1/2, 1/3

1/1, 1/2, 1/3

1/5 1/101/10 1/5

HBA 1 HBA 1 HBA 0

1/14

HBA 0

Px-MDS-2Px-BRCD

1/7 7JBOD 1 JBOD 2

1/4 4

HBAHBA

W2K Server 2

Desktop

ConsoleConsole

eth0 = 10.0.6x.2

10.0.6x.50

10.0.6x.510.0.6x.3

HBAHBA

W2K Server 1

Desktop

eth0 = 10.0.6x.1

eth1 = 10.1.6x.6eth1 = 10.1.6x.2

GigEFC



MDS-1 10.0.6x.5 Server 1 10.0.6x.1 10.1.6x.2

MDS-2 10.0.6 x.3 Server 2 10.0.6x.2 10.1.6x.6


10.0.50.254 255.255.0.0





Table 3: MDS 9000 Port Map fc1/1 fc1/2 fc1/3 fc1/5 fc1/6 fc1/10 fc1/14 gig1/1 gig1/2

MDS-1 ISL-1 ISL-2 ISL-3 HOST1-P1 JBOD-1 HOST2-P2 SD-1 GIG-1 GIG-2

MDS-2 ISL-1 ISL-2 ISL-3 HOST2-P1 JBOD-2 HOST1-P2 NA GIG-1 GIG-2

Table 4: GigE Interfaces Mask = 255.255.0.0 gig1/1 10.1.6x.11 gig

1/1 10.1.6x.21 iSCSI-1 gig1/1 10.1.6x.11 iSCSI-1

gig1/1 10.1.6x.21 MDS-1

gig1/2 10.1.6x.12

MDS-2 gig1/2 10.1.6x.22

MDS-1 iSCSI-2 gig1/2 10.1.6x.12

MDS-2 iSCSI-2 gig1/2 10.1.6x.22



Firefly BB2 TFTP / RADIUS / TACACS+ / SMTP Server IP Address = 10.0.50.1

Cisco Pod Configuration



MDS-1 10.0.x.5 Server 1 10.0.x.2 10.1.x.2

MDS-2 10.0.x.3 Server 2 10.0.x.6 10.1.x.6


10.0.x.254 255.255.255.0





Table 3: MDS 9000 Port Map fc1/7 fc1/8 fc1/9 fc1/5 fc1/6 fc1/10 fc1/16 gig2/1 gig2/2

MDS-1 ISL-1 ISL-2 ISL-3 HOST1-P1 JBOD-1 HOST2-P2 NA GIG-1 GIG-2

MDS-2 ISL-1 ISL-2 ISL-3 HOST1-P2 JBOD-2 HOST2-P1 SD-1 GIG-1 GIG-2

Table 4: GigE Interfaces Mask = 255.255.255.0

gig2/1 10.1.x.21 gig2/1 10.1.x.11 iSCSI-1 gig2/1 10.1.x.21 iSCSI-1 gig2/1 10.1.x.11MDS-1

gig2/2 10.1.x.22 MDS-2

gig2/2 10.1.x.12MDS-1

iSCSI-2 gig2/2 10.1.x.22MDS-2

iSCSI-2 gig2/2 10.1.x.12



Cisco TFTP / RADIUS / TACACS+ / SMTP Server IP Address = 10.0.0.198

cisco storage design fundamentals - · pdf filelab 3: configuring high-availability san...

Documents