Brocade iSCSI Quick Start and Best Practices Guide v1 0(GA-BP-039-00)

STORAGE AREA NETWORK

Brocade iSCSI Quick Start and Best Practices Guide v1.0

August 27, 2007

© 2007 Brocade Communications Systems, Inc. All Rights Reserved. 08/07 GA-BP-039-00

Brocade, the Brocade B-weave logo, Fabric OS, File Lifecycle Manager, MyView, SilkWorm, and StorageX are registered trademarks and the Brocade B-wing symbol, SAN Health, and Tapestry are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered trademark of IBM Corporation in the U.S. and other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.

Notice: The information in this document is provided “AS IS,” without warranty of any kind, including, without limitation, any implied warranty of merchantability, noninfringement or fitness for a particular purpose. Disclosure of information in this material in no way grants a recipient any rights under Brocade's patents, copyrights, trade secrets or other intellectual property rights. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use.

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.

Notice: The product described by this document may contain “open source” software covered by the GNU General Public License or other open source license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

Export of technical data contained in this document may require an export license from the United States Government.

Document History

Document Title Summary of Changes Publication Date

Brocade iSCSI Quick Start and Best Practices Guide First Release August 27, 2007

http://www.brocade.com/support/oscd

Contents

About This Document ......................................................... 4 Introduction....................................................................... 12

iSCSI Concepts .......................................................................... 12 iSCSI Requirements................................................................... 13

iSCSI Overview ................................................................ 14 Supported iSCSI Topologies ...................................................... 14 How iSCSI Sessions are Translated .......................................... 14 iSCSI Features ........................................................................... 15 iSCSI Management Tools .......................................................... 16

iSCSI Installation .............................................................. 17 Overview of iSCSI Installation .................................................... 18 Enabling the iSCSI Service ........................................................ 18 Configuring iSCSI using the Launch Usability Wizard................ 19 FC4-16IP Port Numbering.......................................................... 21 Basic LUN mapping.................................................................... 24 Advanced LUN mapping ............................................................ 25 Controlling Access to the iSCSI Virtual Target (VT)................... 29 Switch-to-iSCSI Initiator Authentication...................................... 37

Microsoft iSCSI Initiator Setup ........................................ 39 Installing the Microsoft iSCSI Initiator......................................... 39 Configuring the Microsoft iSCSI Initiator .................................... 44

Best Practices .................................................................. 51 Connecting to the FC4-16IP....................................................... 51 Using the Easy Create Virtual Targets Wizard........................... 51 LUN Masking Considerations..................................................... 52 Hierarchical LUNs on FC Storage Devices ................................ 53 Configuring the IBM DS8000 for operation with the FC4-16IP... 56

Appendix A ....................................................................... 59 Naming Conventions for the IBM System Storage SAN B-type Switch family .............................................................................. 59

Brocade iSCSI Quick Start and Best Practices Guide 3

About This Document

This document is a guide written to assist individuals in configuring iSCSI on the FC4-16IP blade for the Brocade 48000 Director. This document is written with focus on the Brocade 48000 Director with Fabric OS v5.3.0 or later. The material in this guide is for the most part covered in the official Brocade User’s Manuals.

"About This Document" contains the following sections:

• How This Document Is Organized

• What's New in This Guide

• Document Conventions

• Additional Information

• Getting Technical Help

• Document Feedback

How This Document Is Organized This guide describes and provides procedures for the installation and management of the Brocade iSCSI features. This guide provides only concepts and capabilities and does not explain how the end user would implement management in their own environment. It is intended to provide step by step procedures to perform basic operating procedures that may be needed to verify or troubleshoot the iSCSI implementation on the Brocade 48000 Director using both WebTools and Fabric Manager Management tools. Refer to the Brocade Fabric OS Administrator’s Guide, the Brocade Fabric OS Command Reference Manual Guide, the Brocade Web Tools Administrator's Guide, and the Brocade Fabric Manager Administrator’s Guide for more in-depth information on managing Brocade Directors and using the iSCSI features.

The document contains the following components:

• The title page and "Table of Contents" provide the version number, date, and copyrighted information contained in the document; Brocade Communications, Inc., locations around the world; a document history table; and the topics covered in this particular document.

• "About This Document" provides information specific to this document: how it is organized, the typographic conventions and particular terminology that it uses, and where to go for further information on the topic.

• Chapter 1, “Introduction”, introduces the Brocade iSCSI products.

• Chapter 2, “iSCSI Overview”, explains the supported topologies, features and management tools used to manage the iSCSI product.

• Chapter 3, “iSCSI Installation”, explains the procedures to install and manage a Brocade Director for iSCSI.

• Chapter 4, “Microsoft iSCSI Initiator Setup”, explains the procedures to install and manage a Microsoft Windows Host for iSCSI.

• Chapter 4, “Best Practices”, introduces concepts the operator may need to know if their environment is not operative or in troubleshooting their iSCSI configuration.


What's New in This Guide This is the first release of this guide. This is meant to provide a basis for individuals to install a Brocade iSCSI installation.

The Brocade iSCSI Quick Start and Best Practices Guide describes the following Brocade iSCSI features:

• iSCSI for the FC4-16IP blade

• Microsoft Windows iSCSI initiator v2.04 installation

• Microsoft Windows iSCSI initiator v2.04 basic configuration

Brocade’s iSCSI implementation are documented in the following user’s manuals: the Brocade Fabric OS Administrator’s Guide, the Brocade Web Tools Administrator’s Guide (for procedures using Advanced Web Tools), and the Brocade Fabric Manager Administrator’s Guide (for procedures using Fabric Manager).

There are several other manuals that provide more detailed information on the CLI commands, SNMP, and the Diagnostics available in the Fabric Operating System. The Brocade Fabric OS Command Reference Manual covers command line descriptions, the Fabric OS MIB Reference Manual covers the SNMP agent supplied by the switch, and the Fabric OS System Error Message Reference Manual covers the switch diagnostic and system messages.


Document Conventions This section describes text formatting conventions, important notices formats, and terms as they are used in this document.

Text Formatting The following table describes the narrative-text formatting conventions that are used in this document.

Convention Purpose

bold text

• Identifies command names

• Identifies GUI elements

• Identifies keywords/operands

• Identifies text to enter at the GUI or CLI

italic text

• Provides emphasis

• Identifies variables

• Identifies paths and internet addresses

• Identifies document titles

code text • Identifies CLI output

• Identifies syntax examples

Notes, Cautions, and Warnings The following notices appear in this document.

Note

A note provides a tip, emphasizes important information, or provides a reference to related information.

Guideline Guidelines are recommendations for consideration. The adoption of these guidelines is a function of the user’s ability to interpret and correlate relevant SAN information and make decisions based upon their organization and SAN requirements.

Caution A caution alerts you to potential damage to hardware, firmware, software, or data. Cautions indicate that a particular action or type of connection is not recommended as it may cause failure of the switch or fabric.

Warning A warning alerts you to potential danger to personnel.


Additional Information This section lists additional Brocade, IBM and industry-specific documentation that one might find helpful.

Brocade Resources The following documentation is available on the Brocade Web site, through Brocade Connect:

Fabric OS • Brocade iSCSI Gateway Service Administrator’s Guide

• Brocade Fabric OS Administrator’s Guide

• Brocade Fabric OS Command Reference

• Brocade Fabric OS Message Reference

• Brocade Fabric OS MIB Reference

Fabric OS Management Features • Brocade Web Tools Administrator's Guide

• Brocade Fabric Watch Administrator's Guide

Fabric Management Software • Brocade Fabric Manager Administrator's Guide

Brocade SilkWorm Hardware Reference Manuals • Brocade 48000 Hardware Reference Manual

• Brocade 48000 QuickStart Guide

Additional Resource Information The following related iSCSI materials are provided on the Brocade Web site and are a resource for additional information.

Brocade FC4-16IP iSCSI Blade

http://www.brocade.com/products/switches/silkworm_fc416ip.jsp

Brocade FC4-16IP Data Sheet

http://www.brocade.com/san/pdf/datasheets/FC4-16IP_DS_01.pdf

Brocade FC4-16IP FAQ Document

http://www.brocade.com/products/extension/FAQ1.jsp


http://www.brocade.com/products/switches/silkworm_fc416ip.jsp

http://www.brocade.com/san/pdf/datasheets/FC4-16IP_DS_01.pdf

http://www.brocade.com/products/extension/FAQ1.jsp

For more information on how to use many of the other Brocade features in a SAN solution, refer to the documentation that can be found through the Brocade Connect Web site (you can register for free on the site if you are not already registered): Go to:

Brocade Connect > Technical Resource Center > Documentation Library > Product Manuals

http://www.brocadeconnect.com

Click on any of the links for Product Manuals, such as: - Software User’s Guides - Switch Reference Manuals

For additional Brocade documentation, visit Resources > SAN Info Center > SAN Resources:

http://www.brocade.com

Related publications are provided on the Brocade Partner site or the IBM TotalStorage SAN Switch Support Web site and are an excellent resource for additional information.

For practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through:

http://www.amazon.com

Release Notes are bundled with the Fabric OS software download.


http://www.brocadeconnect.com/

http://www.brocade.com/

http://www.amazon.com/

IBM Resources

The following related documentation is provided on the IBM TotalStorage SAN b-type Resource Library Web site, the IBM RedBook Web site and the IBM Education Web site.

IBM TotalStorage SAN b-type Resource Library Web Sites For additional resource information, on the complete range of Brocade switch products from IBM visit the IBM TotalStorage Web site. This Web site provides additional information on the IBM TotalStorage SAN b-type Family of products:

TotalStorage SAN b-type Resource Library Site:

http://www-03.ibm.com/servers/storage/san/b_type/library.html

IBM RedBooks Web Sites For additional IBM iSCSI resource information, visit the IBM RedBooks Web site and search for “iSCSI”:

http://www.redbooks.ibm.com

Some relevant titles are:

SAN Multiprotocol Routing: An Introduction and Implementation (SG24-7321-00)

IBM Education Web Sites For additional IBM Education resource information, visit the IBM Education Web site and search for “Brocade”:

http://www.ibm.com/products/finder/us/finders?pg=trfinder

IBM Support Web Site

If you have any questions or problems go to the following Help Center World Telephone Numbers URL:

http://www.ibm.com/planetwide

Other Industry Resources For additional resource information, visit the Technical Committee T11 Web site. This Web site provides interface standards for high-performance and mass storage applications for fibre channel, storage management, as well as other applications:

http://www.t11.org

For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web site:

http://www.fibrechannel.org


http://www-03.ibm.com/servers/storage/san/b_type/library.html

http://www.redbooks.ibm.com/

http://www.ibm.com/products/finder/us/finders?pg=trfinder

http://www.ibm.com/planetwide

http://www.t11.org/

http://www.fibrechannel.org/

Getting Technical Help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available:

1. General Information

• Technical Support contract number, if applicable

• Switch model

• Switch operating system version

• Error messages received

• supportsave command output

• Detailed description of the problem and specific questions

• Description of any troubleshooting steps already performed and results

2. Switch Serial Number

The switch serial number and corresponding bar code are provided on the serial number label, on the side of the unit:

Brocade Serial Number: FT00X0054E9

The serial number label is located as follows:

• Brocade 48000 Directors: Inside the front of the chassis, on the wall to the left of the ports

It can also be obtained:

o From a telnet session to the switch, use the “chassisshow” command it is located in the “Serial Num:” field.

o From a Web Tools session, Click on the “Info” tab it is located in the “Supplier Serial #” field. o From Fabric Manager, Click on the “Switches” tab it is located in a column titled “Supplier Serial

Number”.

3. License ID Information. (Required to obtain optional licenses)

• Brocade 48000 switches: Provide the license ID. Use the licenseidshow command to display the license ID.

It can be obtained:

o From a telnet session to the switch, use the “licenseidshow” command to display the license ID.

o From a Web Tools session, Click on the “Info” tab it is located in the “LicenseID” field.


Document Feedback Because quality is our first concern at Brocade, we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Provide the title and version number and as much detail as possible about your issue, including the topic heading and page number and your suggestions for improvement.


Chapter 1 Introduction

The Brocade iSCSI Design and Deployment Guide provides information to help you install and configure the Brocade iSCSI features and software. The following topics are covered:

• iSCSI Concepts • iSCSI Requirements

iSCSI Concepts iSCSI is an industry-standard. The iSCSI standard is a protocol that resides on top of TCP and is designed to transport SCSI commands and data across an IP network, most commonly across Ethernet. The iSCSI standard was developed by a working group under the Internet Engineering Task Force (IETF). The most current version is 1.0. From a software perspective, an iSCSI device appears as a locally attached SCSI drive. The SCSI commands are intercepted and directed to the iSCSI layer. They are encapsulated, then sent out as TCP packets. At the far end, the reverse happens so a SCSI command arrives at the device. There are many applications for iSCSI. It is especially useful for lower-cost connection of second and third-tier servers into existing Fibre Channel Storage Area Networks (SANs) for block access to storage. Many applications do not require the high level of performance that Fibre Channel provides, and iSCSI performance is often "good enough." These applications might include file services, DHCP services, mail services, or some development applications. The FC4-16IP SCSI Blade adds iSCSI-FC gateway functionality to the Brocade 48000 Director, translating iSCSI traffic to Fibre Channel traffic. Using the Brocade FC4-16IP Blade, an iSCSI initiator (server) can access a Fibre Channel storage device. The iSCSI initiators can either be directly connected to the Ethernet ports on the iSCSI Blade or across an IP network. The Fibre Channel targets can be connected directly to the Fibre Channel ports on the Brocade FC4-16IP Blade, to the Fibre Channel ports on the Brocade 48000 Director, or across the Fibre Channel fabric. For further information about the IBM specific iSCSI implementation, refer to the IBM Redbook, IBM System Storage : Implementing an IBM SAN. This covers the iSCSI implementation on the Brocade 48000 (IBM TotalStorage 2109-M48).


Chapter 1

iSCSI Requirements This section lists requirements to incorporate and manage iSCSI such as:

• Firmware

• Software

• Hardware

Firmware To incorporate and manage iSCSI on a Director or fabric, your system must have Fabric OS v5.2.0 or higher installed (For IBM fabrics Fabric OS 5.3.0 or later for the M48). For information on downloading Fabric OS firmware, refer to the Brocade Fabric OS Administrator’s Guide. iSCSI protocol is supported on the following Brocade models and Fabric OS releases:

• Brocade AP7420 Fabric OS v7.4.0 or later. • Brocade 48000, Fabric OS v5.2.0 or later and the 48000 iSCSI blade (FC4-16IP).

Software If you are implementing iSCSI solution, iSCSI is provided free of charge in Fabric OS versions 5.2 and higher. Only the proper hardware (the Brocade FC4-16IP Blade) is required. No additional Brocade licenses are required to enable the iSCSI feature. The following Brocade software products provide for iSCSI management:

• Fabric Manager. Refer to the Brocade Fabric Manager Administrator’s Guide. • Advanced Web Tools. Refer to the Brocade Web Tools Administrator’s Guide. • The Fabric OS CLI. Refer to the Brocade Fabric OS Administrator’s Guide and the Brocade

Fabric OS Command Reference Manual • SNMP. Refer to the Brocade Fabric OS MIB Reference Manual

Hardware From the network perspective, iSCSI traffic looks like another IP packet. Existing Ethernet switches and IP routers work transparently to bridge the iSCSI initiators into the FC4-16IP Blade.


Chapter 2 iSCSI Overview The following topics are covered in iSCSI Overview:

• Supported iSCSI Topologies • How iSCSI Sessions are Translated • iSCSI Features • iSCSI Management Tools

Supported iSCSI Topologies The FC4-16IP iSCSI gateway service is an intermediate device in the network, allowing iSCSI initiators in an IP SAN to access and utilize storage in a Fibre Channel (FC) SAN as shown in the figure below.

Figure 1. iSCSI gateway network

How iSCSI Sessions are Translated The iSCSI gateway enables applications on an IP network to use an iSCSI initiator to connect to FC targets. The iSCSI gateway translates iSCSI protocol to Fibre Channel Protocol (FCP), bridging the IP network and FC SAN. The following figure shows a basic implementation.

Figure 2. iSCSI gateway service basic implementation The Brocade FC4-16IP blade acts as an iSCSI gateway between FC-attached targets and iSCSI initiators. On the iSCSI initiator, iSCSI is mapped between the SCSI driver and the TCP/IP stack. At the iSCSI gateway port, the incoming iSCSI data is converted to FCP (SCSI on FC) by the iSCSI virtual initiator, and then forwarded to the FC target. This allows low-cost servers to leverage an existing FC infrastructure.


Chapter 2 iSCSI Features iSCSI Gateway service provides the following services to the iSCSI initiators:

• Access to the fabric using virtual FC devices (iSCSI virtual initiator)

• Supports target registration to an iSCSI Name Server (iSNS) for discovery

• Manages iSCSI initiator access control using discovery domains and a discovery domain set

• Session management, such as session tracking and performance monitoring

• Session authentication using CHAP

Note

The FC4-16IP iSCSI gateway service is not compatible with other iSCSI gateway platforms, including Brocade iSCSI Gateway or the Brocade Multiprotocol Router (AP7420).


Chapter 2

iSCSI Management Tools Brocade provides a variety of fabric management tools, including:

• Fabric Manager: a workstation-based graphical user interface (GUI) tool that can be used to manage a fabric that supports iSCSI and Fibre Channel Protocol (FCP) devices and traffic. This is the recommended GUI management tool for iSCSI environments. Refer to the Brocade Fabric Manager Administrator’s Guide for more information.

• Advanced Web Tools: a Web-based GUI tool that can be used to manage a fabric that supports iSCSI and FCP devices and traffic. Refer to the Brocade Web Tools Administrator’s Guide for more information.

• Fabric OS command line interface (CLI). Refer to the Brocade Fabric OS Administrator’s Guide and the Brocade Fabric OS Command Line Reference Manual for more information.

• MIBs: For more information, refer to the Brocade MIB Reference Manual.

Note

Fabric Manager is an optionally licensed software product that is not included with Fabric OS and must be installed on a workstation.


Chapter 3 iSCSI Installation

This chapter explains the procedures used to install Brocade iSCSI on a Director.

The following information is discussed:

• Overview of iSCSI Installation

• Enabling the iSCSI Service

• Configuring iSCSI using the Launch Usability Wizard

• FC4-16IP Port Numbering

• Basic LUN Mapping

• Advanced LUN Mapping

• Controlling Access to the iSCSI Virtual Target (VT)

• Switch-to-iSCSI Initiator Authentication


Chapter 3 Overview of iSCSI Installation Brocade Directors can be managed using many local and remote access methods. To install a Brocade iSCSI Director, you must have access to one of the following available management methods:

• Brocade Fabric Manager a stand alone JAVA application • Advanced Web Tools through a supported browser • Fabric OS Command Line Interface (CLI) through Telnet or Secure Shell (ssh)

Fabric Manager, Advanced Web Tools, Telnet and SNMP, require that the director be accessible using a network connection.

The following are the basic installation steps :

1. Enable the iSCSI service on the Brocade 48000

2. Configure iSCSI using the Launch Usability Wizard

3. Install the Microsoft iSCSI initiator v2.04

4. Configure the Microsoft iSCSI initiator v2.04

5. Connecting to iSCSI Targets presented by Brocade 48000 FC4-16IP iSCSI gateway

Enabling the iSCSI Service The default configuration of the iSCSI service is disabled. You can use the CLI or Advanced Web Tools to enable iSCSI. After launching Advanced Web Tools select the iSCSI button in the “Manage” pane on the left.

Figure 3. Enabling the iSCSI gateway service


Chapter 3 This will open the iSCSI Administration module. Notice the message “iSCSI is Disabled” and the top left button displays “Enable iSCSI”. Select the “Enable iSCSI” button.

Figure 4. Enabling iSCSI

Configuring iSCSI using the Launch Usability Wizard We have now enabled the iSCSI service and we can now continue with the configuration steps necessary to setup connectivity between an IP network and a Fibre Channel SAN. We will start the Launch Usability Wizard by selecting the “Launch Usability Wizard”. A new window “iSCSI Setup” should open.


Chapter 3

Figure 5. iSCSI setup

After reading the “Before you begin” recommendation select “Next”. A new window “Add IP interface” will open. There are eight GigE port on each FC4-16IP blade. In this example we have a FC4-16IP blade in slot 9.

Figure 6. Add an IP Interface to one of the Gigabit Ethernet Ports.


Chapter 3

FC4-16IP Port Numbering The FC4-16IP blade has both GbE ports and FC ports. Ports are addressed using slot number and port number notation (for example, 2/7). FC ports are numbered from 0 through 7; GbE ports are numbered from ge0 through ge7.

Note The FC4-16IP blade does not support FCIP functionality.

Figure 7. FC4-16IP ports


Chapter 3 Select the “Slot/port” for the FC4-16IP GigE iSCSI interface port to configure. Enter the appropriate IP address, and subnet mask for the selected GigE port that will be connected in your network. Do not configure any GigE ports that will not be connected to the IP network. If you have additional GigE ports to configure select the “Add” button.

When you have completed configuring your last GigE port select the “Add and Close” button. If you have selected "Add" button but do wish to configure additional GigE interfaces, select Cancel button.

This will close the “Add IP Interface” window and return to the Wizard. You should see the newly configured IP interfaces. In this example we have configured Slot 9, GigE port 0 and GigE port 1.

Figure 8. Configuring iSCSI Ports with an IP Interface.

When you have completed configuring the GigE iSCSI interfaces select the “Save” button. This will bring up the IP interface status report. This will display the results of the changes to the IP Interfaces. Then Select the “OK” button.


Chapter 3

Figure 9. IP Interface configuration status report.

Optionally you can configure Static Routes to reach the destination IP through a preferred gateway. The gateway must be on the same subnet as the GigE port. We are not configuring the optional static routes.

We now continue to step 4, the iSCSI initiator summary. If this is your initial configuration of the FC4-16IP iSCSI service you should not see any iSCSI initiators in the summary. If you have previously configured iSCSI you should see any iSCSI initiator which previously established an iSCSI session with a FC4-16IP iSCSI interface port.

Figure 10. Initiator Summary.

Select the “Next” Button to advance to “Configure Virtual Targets” step.


Chapter 3

Figure 10. iSCSI Setup – Configuring Virtual Targets.

The Fabric OS provides two methods to perform LUN mapping, Basic LUN mapping and Advanced LUN Mapping.

Basic LUN mapping Fabric OS provides a mechanism that maps LUNs to iSCSI Virtual Targets (VT)s, a one-to-one mapping with unique iSCSI Qualified Names (IQNs) for each target. It presents an iSCSI VT for each native FC target to the IP network and an iSCSI VI for each iSCSI port to the FC fabric. The following figure shows the result of using the iscsiCfg - -easycreate tgt command executed on an FC target with four LUNs.

Figure 11. iSCSI VT basic LUN mapping.


Chapter 3

Advanced LUN mapping SCSI VTs can be mapped to more than one physical FC target, and the LUNs can be mapped to different virtual LUNs. The following figure shows an advanced mapping scenario.

Figure 12 iSCSI VT advanced LUN mapping

In this example we select the “Use Auto Method” with “One to One LUN Mapping” and will use the default IBM iSCSI IQN prefix “iqn.1924-02.com.ibm:2109-m48port”. You can skip the Virtual Target creation step by selecting “Skip VT Create step” check box. Select the “Next” button.


Chapter 3

This will open a new window “Select FC Targets”.

Figure 13. Selecting FC Targets.

Select the Fibre Channel Target ports with LUNs to create Virtual iSCSI Targets. In this example we will select two of the four FC Targets by high lighting the FC Targets and selecting the “Add>” button. The two un-selected FC Targets will not have corresponding Virtual iSCSI Targets created.

When you have completed selecting the FC Targets, click on the OK button. The “Select FC Targets” window will close and you will return to the “Usability Wizard” step 6 to verify the parameter and Virtual iSCSI target that will be created.


Chapter 3

Figure 13. iSCSI Setup – Creating Virtual Targets : Auto Create.

Verify the virtual iSCSI target name and parameter then Click save.

Figure 14. Create iSCSI FC Zone.


Chapter 3 As stated in the wizard all physical FC Targets that have been mapped to iSCSI Virtual Target must be zoned with all Virtual iSCSI initiators.

Depending on whether you have an effective zone configuration enabled in the current fabric, you will be able to choose where to put the iSCSI FC zone. It can be either contained in a defined configuration or integrated into the effective configuration. If you would like to display the current zoning configuration you can select “Show Zone”

Select the “Save” button to move forward with the wizard. There will be another message notifying of the zone changes that will occur. Select the “Yes” button to continue.

Figure 15. Create iSCSI FC Zone warning message. This will open a new window “Add iSCSI FC Zones to Configs”. This allows you to add the required “iSCSI_FC_ZONE” to all of the defined zone configs or a select set of configs. If you select the current effective configuration it will re-enable the effective zoning configuration


Chapter 3

Figure 15. Add iSCSI FC Zones to Configs. After checking the appropriate zoning configuration to add the “iSCSI_FC_ZONE” select “OK”. The wizard will advance to the creation of Discovery Domains.

Controlling Access to the iSCSI Virtual Target (VT) You can limit access to iSCSI VTs using a discovery domain (DD), a group of the iSCSI initiators and iSCSI VTs. The iSCSI initiators can access only the iSCSI VTs that are in the same discovery domain. Discovery domains are grouped together in a discovery domain set (DDSet). The active discovery domain set enforces the fabric-wide iSCSI VT access. Only the DDs in the active DDSet are enforced. You can create multiple discovery domain sets but only one set can be active at a time. It is also possible to present a single iSCSI portal IP address to the iSCSI initiator when the default iSCSI port configuration is in effect, and connection redirection is disabled on the blade.

In an FC4-16IP iSCSI configuration DD are analogous to “zone” object in FC SAN zoning configuration and DDSet is analogous to “cfg” object in FC SAN zoning configuration.

The following figure shows a discovery domain set (DDSet 1), which contains two discovery domains (DD1 and DD2). When DDSet 1 is active, iSCSI initiator A can access only iSCSI VT 1 and iSCSI initiator B can access only VT 2 and VT 3.


Chapter 3

Figure 16. Discovery Domain Sets.

In this example we will configure configure two DDs (dd1 and dd2), each with one iSCSI initiator and one Virtual iSCSI target.

Figure 17. Configuring Discovery Domains.


Chapter 3

We will add a discovery domain (DD) in this example we will name it dd1. You will type the name of the DD in the box to the right of the “Add” button. Then select “Add”.

Figure 18. Adding Discovery Domains.

You should now see the newly add DD (dd1) in the right pane of the configure DDs window. Now we will add the iSCSI initiators and iSCSI virtual targets.

Highlight the desired virtual target to add to the “dd1” DD, and click the add button. Repeat for all the desired virtual targets and iSCSI initiator to be added to the “dd1”.


Chapter 3


To add additional DDs you must select “DDs” in the right pane of the Configure DDs window. This will change the update button form update to an add button. If you have a specific DD, in this example “dd1” the button will change from “Add” to “Update”

Repeat the steps for any additional DDs you would like to add. In this example we have added “dd1” and “dd2” with one iSCSI Virtual Target and one iSCSI initiator in each DD.


Chapter 3

Figure 20. Adding Discovery Domains. Once you have created all the DDs select the “Save” button. We can now create the DDSet in Step 9 of the wizard.



Chapter 3 In the field to the right of the “Add” button enter a user defined DDSet name. For our example we will use "ddset1". Then select “Add”.

Figure 20. Configuring Discovery Domains. In the DD Set pane we see the newly added DD Set, "ddset1". The DDset “ddset1” should be highlighted.


Chapter 3

Figure 21. Configuring Discovery Domains. In the left window “Available DDs” pane highlight the dd1 and dd2, then click “Add” button to add "dd1",and "dd2" to the "ddset1". After clicking the “Add” button you should be able to see that "dd1", "dd2" have been added to "ddset1”.


Chapter 3

Figure 21. Configuring Discovery Domains. Like zoning you can have multiple DDSets defined but only one effective at any one time. Only the DDs in the effective DDSet will be enforced.

Figure 22. Enabling Discovery Domains.


Chapter 3

In the “Enable DD Set” pull down menu select the DDset you would like to enable, in this example we select “ddset1”. Then click save.

This takes us to step 10, “Configure CHAP”.

Switch-to-iSCSI Initiator Authentication Authenticate iSCSI sessions using CHAP (Challenge Handshake Authentication Protocol). The iSCSI gateway service supports the following three strategies for CHAP authentication:

• One-way—Only the iSCSI VT authenticates the session.

• Mutual—Both the iSCSI initiator and the iSCSI VT authenticate the session

• Binding user names - Specific user names can be bound to an iSCSI VT. Only those user names

can be used for authentication during iSCSI logon.

Note iSCSI gateway service does not support IPSec.

For this example we will not be configuring CHAP. Click Finish.

Figure 23. Configuring CHAP.


Chapter 3 This completes all the steps for configuration using the “Usability Wizard”. But we still must “Apply” all our changes. Select the “Apply” button.

Figure 24. Applying the configuration. We can verify the GigE iSCSI interface network connecting from any system on the same network as the newly configured FC4-16IP GigE port. You should be able to ping the IP interfaces. In this example we configure slot 9/GigE port 0 with an IP address of 192.168.70.2. From a remote host we use the ping command the IP address of the iSCSI interface. If there is network connectivity between the remote host and iSCSI interface we should see a reply from the iSCSI interface IP.

C:\>ping 192.168.70.2 Pinging 192.168.70.2 with 32 bytes of data: Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Ping statistics for 192.168.70.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

This completes the configuration of the FC4-16IP blade on the Brocade 48000.


Chapter 4

Microsoft iSCSI Initiator Setup This chapter explains the procedures used to install the Microsoft iSCSI initiator software v2.04.


• Installing the Microsoft iSCSI Initiator

• Configuring the Microsoft iSCSI Initiator

Installing the Microsoft iSCSI Initiator Now we will install and configure the Microsoft iSCSI Initiator v2.04.

To install the correct version of Microsoft iSCSI initiator right click “My computer” select “Properties” to determine if the computer is a x86, Intel, or AMD.

Figure 25. Microsoft iSCSI initiator configuration.


Chapter 4 In this example we have an “x86” system. Double click the appropriate Self-Extracting Cabinet exe file to begin the install.

Figure 26. Microsoft iSCSI initiator x86 driver installation.

This will start the “Software Update Installation Wizard” for the Microsoft iSCSI Initiator.

Figure 27. Microsoft iSCSI installation wizard.


Chapter 4 To continue with the install click “Next”.

Figure 27. Microsoft iSCSI initiator – MPIO Multipathing installation option.

If you wish to use “Microsoft MPIO Multipathing support for iSCSI” check the box. To continue select the “Next” button.


Chapter 4

Figure 28. Microsoft iSCSI initiator installation agreement.

Read the license agreement, if you agree select the “I agree” radio button and select “Next”. The Installation Wizard will now begin the installation of the Microsoft iSCSI initiator files.

Figure 29. Microsoft iSCSI initiator installation agreement.


Chapter 4

After all the files have been installed you will see the “successfully completed” message.

Figure 30. Microsoft iSCSI initiator installation success message.

If you wish to restart select the “Finish” button. If you wish to restart at a later time, select the “Do not restart now” check box.

Launch the “Computer Management” console. Select the “Disk Management”, looking at Disk manager we only have the local c: drive and cd rom 0 drive. We will revisit “Disk Management” after configuring the Microsoft iSCSI Initiator.


Chapter 4

Figure 31. Microsoft Disk Management.

Configuring the Microsoft iSCSI Initiator To start the Microsoft Initiator go to Start->programs->Microsoft iSCSI Initiator and select Microsoft iSCSI Initiator. This will launch the Microsoft iSCSI Initiator Properties configuration utility.


Chapter 4

Figure 32. Microsoft iSCSI Initiator “General” Properties. Enter the IP address of the configured GigE port on the iSCSI blade. In this example we will configure 192.168.70.2. Port 3260 is the default TCP listening port for iSCSI sessions.

Figure 33. Microsoft iSCSI Initiator “Add Target Portal” Properties. Select the Advanced button. For the local Adapter select Microsoft iSCSI Initiator, for Source IP select the desired IP interface. In this example 192.168.70.12. Select OK.


Chapter 4

Figure 34. Microsoft iSCSI Initiator “Advanced Settings” General. Source IP tab.


Chapter 4

Figure 35. Microsoft iSCSI Initiator “Discovery” Properties.


Chapter 4

Figure 36. Microsoft iSCSI Initiator “Targets” Properties.

If you receive an error or do not see any “Targets” in the “Targets” tab from this remote iSCSI initiator we use the ping command the IP address of the iSCSI interface. If there is network connectivity between the remote host and iSCSI interface we should see a reply from the iSCSI interface IP.

C:\>ping 192.168.70.2 Pinging 192.168.70.2 with 32 bytes of data: Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Reply from 192.168.70.2: bytes=32 time<10ms TTL=64 Ping statistics for 192.168.70.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

If you do see one or more iSCSI Targets (Virtual iSCSI targets) have been discovered note the status is “Inactive”. To connect to iSCSI Target high-light the Target and select "Log On" button.


Chapter 4

Figure 37. Microsoft iSCSI Initiator “Log On to Target”.

If you want to use Multipathing option check the “Enabled multi-path” box. Then select OK.

Figure 38. Microsoft iSCSI Initiator “Targets” Tab.


Chapter 4 You will return to the “Targets” tab. Notice the status of the iSCSI Target has changed to “Connected”.

If you closed Computer Management, launch it again.

Figure 39. Microsoft Computer Management.

After connecting to the iSCSI target disk manager shows our new disk, “Disk 1”.


Chapter 5

Best Practices This chapter explains some Best Practices as they apply to Brocade and IBM iSCSI solutions.


• Connecting to the FC4-16IP

• Using the Easy Create Virtual Targets Wizard

• LUN Masking Considerations

• Hierarchical LUNs on FC Storage Devices

• Configuring the IBM DS8000 for operation with the FC4-16IP

Connecting to the FC4-16IP The FC4-16IP blade GigE ports do not support 10 Mbits/sec or 100 Mbits/sec connections. Only 1000 Mbit/sec (GigE) connections are supported.

When connecting the FC4-16IP iSCSI GigE interfaces verify the Ethernet hub or switch is capable of and configured for 1000 Mbits/sec. Additionally the FC4-16IP blade is designed to have up to 64 iSCSI sessions (potentially up to 64 iSCSI initiators) per GigE port; do not connect your iSCSI initiator directly to the FC4-16IP GigE interface.

Using the Easy Create Virtual Targets Wizard When creating Virtual iSCSI targets using the Easy Create wizard reference your LUN documentation or Management application for your storage device. The Wizard does supply the switch Domain ID, port Number and the World Wide Port Name of the storage port, but the same Physical LUN could be presented out of multiple storage ports. The Easy Create Wizard only displays the LUN number and it can be difficult to determine if LUN 0 on one storage port is the same LUN 0 on a different storage port.


Chapter 5

Figure 40. LUN Addition Dialog.

In an IBM SVC configuration you should reference the SVC LUN management application or documentation.

LUN Masking Considerations The node WWN and port WWN of the local switch are used to query LUNs on the physical target. If the physical target uses LUN masking to control access, these WWNs must be added to the LUN masking to ensure that the LUN query returns the LUNs to the switch.

You can obtain these WWNs in either of two ways.

• Enter the iscsiCfg --easycreate tgt command with the -s option. The -s option returns the node and port WWNs of the switch.

The following is an example. switch:admin> iscsicfg --easycreate tgt -s

The following WWNs will be used for any easycreate operation from this switch:

Node WWN: 10:00:00:60:69:80:04:4a

Port WWN: 21:fd:00:60:69:80:04:4a


Chapter 5 • Enter the fcLunQuery with the -s option. The -s option returns the node and port WWNs of the switch.

The following is an example.

switch:admin> fclunquery -s

The following WWNs will be used for any lun query from this switch:

Node WWN: 10:00:00:60:69:80:04:4a

Port WWN: 21:fd:00:60:69:80:04:4a

Hierarchical LUNs on FC Storage Devices Most systems use flat LUNs with single byte LUN IDs.

The following is an example of flat LUNs and the output of fclunquery command:

Target Index: 133 Target Node WWN: 50:05:07:68:01:00:29:7b Target Port WWN: 50:05:07:68:01:20:29:7b Target Pid: 350700 Number of LUNs returned by query: 4 LUN ID: 0x00 LUN ID: 0x01 LUN ID: 0x02 LUN ID: 0x03

<truncated output>

The Advanced Web Tools Virtual iSCSI wizard is able to display the single byte LUN ID correctly.


Chapter 5


AIX, HPUX, SVC, pSeries and zLinux use hierarchical LUNs defined with two bytes LUN IDs (multiple levels) .

The following is an example of hierarchical LUNs and the output of fclunquery command:

Target Index: 125 Target Node WWN: 50:05:07:63:03:ff:c8:55 Target Port WWN: 50:05:07:63:03:14:08:55 Target Pid: 270700 Number of LUNs returned by query: 16 LUN ID: 0x4001400a00000000 LUN ID: 0x4001400b00000000

When using hierarchical LUN you must use the Command Line Interface (CLI) to create Virtual iSCSI targets. The Advanced Web Tools (GUI) uses a single byte to display The LUN IDs.


Chapter 5



Chapter 5

Configuring the IBM DS8000 for operation with the FC4-16IP The following is an example of configuring the IBM DS8000 to provision LUNs to the Brocade FC4-16IP iSCSI blade. This environment has four iSCSI FC4-16IP ports that are active on slot 3, 3/ge0, 3/ge1, 3/ge2 and 3/ge3. The IBM DS8000 used in this example has eight Host Adapter Ports and they are zoned to see each of the GbE adapter interfaces since redirection is used on the Brocade FC4-16IP iSCSI Gateway.

Where to get iSCSI wwpn's for storage devices

On the Brocade Director which contains the Brocade iSCSI FC4-16IP blade we determine wwpn’s that need to be added to DS8000 using the “fclunquery” and “nsshow”commands. Bold text is used to identify the important information that will be necessary. switch:admin> fclunquery -s The following WWPNs will be used for any lun query from this switch: Node WWN: 10:00:00:60:69:e4:24:d8 Port WWN: 21:fd:00:60:69:e4:24:d8 switch:admin> nsshow N 142800; 3;50:06:06:9e:42:4d:83:00;50:06:06:9e:42:4d:83:01; na FC4s: FCP PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 9.11.192.15 Slot/Port: 3/ge0 Logical pn: 40" Fabric Port Name: 20:28:00:60:69:e4:24:d8 Permanent Port Name: 50:06:06:9e:42:4d:83:00 Port Index: 40 Share Area: No Device Shared in Other AD: No Redirect: No N 142900; 3;50:06:06:9e:42:4d:83:08;50:06:06:9e:42:4d:83:09; na FC4s: FCP PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 9.11.192.16 Slot/Port: 3/ge1 Logical pn: 41" Fabric Port Name: 20:29:00:60:69:e4:24:d8 Permanent Port Name: 50:06:06:9e:42:4d:83:08 Port Index: 41 Share Area: No Device Shared in Other AD: No Redirect: No N 142a00; 3;50:06:06:9e:42:4d:83:10;50:06:06:9e:42:4d:83:11; na FC4s: FCP PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 9.11.192.17 Slot/Port: 3/ge2 Logical pn: 42" Fabric Port Name: 20:2a:00:60:69:e4:24:d8 Permanent Port Name: 50:06:06:9e:42:4d:83:10 Port Index: 42


Chapter 5 Share Area: No Device Shared in Other AD: No Redirect: No N 142b00; 3;50:06:06:9e:42:4d:83:18;50:06:06:9e:42:4d:83:19; na FC4s: FCP PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 9.11.192.18 Slot/Port: 3/ge3 Logical pn: 43" Fabric Port Name: 20:2b:00:60:69:e4:24:d8 Permanent Port Name: 50:06:06:9e:42:4d:83:18 Port Index: 43 Share Area: No Device Shared in Other AD: No Redirect: No

IBM DS8000 Definitions for iSCSI In the following example the dscli is used to define hosts wwpn’s and luns for Brocade iSCSI gateway. dscli> mkvolgrp -type scsimap256 switch_iSCSI CMUC00030I mkvolgrp: Volume group V8 successfully created. dscli> mkfbvol -extpool p1 -cap 5 -name BE_iSCSI_#h -volgrp v8 0506-051f CMUC00025I mkfbvol: FB volume 0506 successfully created. CMUC00025I mkfbvol: FB volume 0507 successfully created. CMUC00025I mkfbvol: FB volume 0508 successfully created. CMUC00025I mkfbvol: FB volume 0509 successfully created. CMUC00025I mkfbvol: FB volume 050A successfully created. CMUC00025I mkfbvol: FB volume 050B successfully created. CMUC00025I mkfbvol: FB volume 050C successfully created. CMUC00025I mkfbvol: FB volume 050D successfully created. CMUC00025I mkfbvol: FB volume 050E successfully created. CMUC00025I mkfbvol: FB volume 050F successfully created. CMUC00025I mkfbvol: FB volume 0510 successfully created. CMUC00025I mkfbvol: FB volume 0511 successfully created. CMUC00025I mkfbvol: FB volume 0512 successfully created. CMUC00025I mkfbvol: FB volume 0513 successfully created. CMUC00025I mkfbvol: FB volume 0514 successfully created. CMUC00025I mkfbvol: FB volume 0515 successfully created. CMUC00025I mkfbvol: FB volume 0516 successfully created. CMUC00025I mkfbvol: FB volume 0517 successfully created. CMUC00025I mkfbvol: FB volume 0518 successfully created. CMUC00025I mkfbvol: FB volume 0519 successfully created. CMUC00025I mkfbvol: FB volume 051A successfully created. CMUC00025I mkfbvol: FB volume 051B successfully created. CMUC00025I mkfbvol: FB volume 051C successfully created. CMUC00025I mkfbvol: FB volume 051D successfully created. CMUC00025I mkfbvol: FB volume 051E successfully created. CMUC00025I mkfbvol: FB volume 051F successfully created. dscli> mkhostconnect -wwname 21fd006069e424d8 -hosttype Win2003 -volgrp v8 -ioport all switch_fclunquery


Chapter 5 CMUC00012I mkhostconnect: Host connection 000E successfully created. dscli> mkhostconnect -wwname 5006069e424d8300 -hosttype Win2003 -volgrp v8 -ioport all switch_3ge0 CMUC00012I mkhostconnect: Host connection 000F successfully created. dscli> mkhostconnect -wwname 5006069e424d8308 -hosttype Win2003 -volgrp v8 -ioport all switch_3ge1 CMUC00012I mkhostconnect: Host connection 0012 successfully created. dscli> mkhostconnect -wwname 5006069e424d8310 -hosttype Win2003 -volgrp v8 -ioport all switch_3ge2 CMUC00012I mkhostconnect: Host connection 004F successfully created. dscli> mkhostconnect -wwname 5006069e424d8318 -hosttype Win2003 -volgrp v8 -ioport all switch_3ge3 CMUC00012I mkhostconnect: Host connection 0050 successfully created.

Zoning examples for the DS8000 configuration

A zone was created in the Brocade fabric to connect the DS8000 ports with the Brocade FC4-16IP iSCSI gateway ports. Truncated output from cfgshow : zone: iSCSI_switch_DS8000_zone 50:05:07:63:03:01:00:6e; <----- DS8000 Port 50:05:07:63:03:03:00:6e; <----- DS8000 Port 50:05:07:63:03:04:00:6e; <----- DS8000 Port 50:05:07:63:03:04:c0:6e; <----- DS8000 Port 50:05:07:63:03:0b:00:6e; <----- DS8000 Port 50:05:07:63:03:11:40:6e; <----- DS8000 Port 50:05:07:63:03:19:40:6e; <----- DS8000 Port 50:05:07:63:03:1c:00:6e; <----- DS8000 Port 50:06:06:9e:42:4d:83:00; <----- Slot 3 GbE 0 50:06:06:9e:42:4d:83:08; <----- Slot 3 GbE 1 50:06:06:9e:42:4d:83:10; <----- Slot 3 GbE 2 50:06:06:9e:42:4d:83:18 <----- Slot 3 GbE 3


Appendix

Appendix A Naming Conventions for the IBM System Storage SAN B-type Switch family

IBM Name IBM Model Brocade Name1 Gbit Family 1 Gbit Family IBM TotalStorage SAN Managed Hub 3534-1RU Brocade 2010, (20X0) IBM TotalStorage SAN Switch S08 2109-S08 Brocade 2400 IBM TotalStorage SAN Switch S16 2109-S16 Brocade 2800 2 Gbit Family 2 Gbit Family IBM TotalStorage SAN Switch F08 3534-F08 Brocade 3200 IBM TotalStorage SAN Switch F16 2109-F16 Brocade 3800 IBM TotalStorage SAN Switch F32 2109-F32 Brocade 3900 IBM TotalStorage SAN Director M12 2109-M12 Brocade 12000 IBM TotalStorage SAN Switch H08 2005-H08 Brocade 3250 IBM TotalStorage SAN Switch H16 2005-H16 Brocade 3850 IBM TotalStorage SAN Director M14 2109-M14 Brocade 24000 Brocade SAN Switch Module for IBM BladeCenter (Entry and Enterprise models) 26K5601/90P0165 Brocade 3016 4 Gbit Family 4 Gbit Family IBM TotalStorage SAN16B-2 2005-B16 Brocade 200E IBM TotalStorage SAN32B-2 2005-B32 Brocade 4100 IBM System Storage SAN64B-2 2005-B64 Brocade 4900 IBM System Storage SAN32B-3 2005-B5K Brocade 5000 IBM TotalStorage SAN256B 2109-M48 Brocade 48000 16 Port Card FC3416 FC4-16 32 Port Card FC3432 FC4-32 48 Port Card FC3448 FC4-48 Multiprotocol Routing Blade FC3450 FR4-18i iSCSI Blade FC3460 FC4-16IP 10Gb Blade FC3470 FC10-6 Brocade 4Gb SAN Switch Module for IBM BladeCenter (10-port and 20-port models) 32R1813/32R1812 Brocade 4020 Multiprotocol Router Multiprotocol Router IBM System Storage SAN18B-R multiprotocol router 2005-R18 Brocade 7500 IBM TotalStorage SAN16B-R multiprotocol router 2109-A16

Brocade Multiprotocol Router AP7420


Appendix


Documents

Brocade iSCSI Quick Start and Best Practices Guide v1 0(GA-BP-039-00)