Publication Number: 53-1000440-01 Publication Date: 15 June 2007 iSCSI Gateway Service Administrator’s Guide Supporting Fabric OS v5.3.
Copyright © 2007 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the Brocade B weave logo, Fabric OS, File Lifecycle Manager, MyView, Secure Fabric OS, SilkWorm, and StorageX are registered trademarks and the Brocade B wing logo 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.
About This Document This document is a procedural guide to help SAN administrators configure and manage the iSCSI gateway service on the FC4-16IP blade in a Brocade 48000 director. Supported hardware and software This document is specific to Fabric OS v5.3.0 or higher running on the Brocade 48000 director with an FC4-16IP blade installed.
Document conventions This section describes text formatting conventions and important notices formats.
discovery domain (DD) A group of iSCSI virtual targets and iSCSI initiators. Discovery domains are used for access control and authentication. Only the iSCSI initiators in the same discovery domain as the iSCSI virtual targets can connect to the FC targets. When there are no discovery domains, all iSCSI initiators can access all iSCSI virtual targets (and therefore all FC targets) on the gateway. discovery domain set (DDSet) A group of discovery domains that can be enabled or disabled.
iSCSI session The basic communication “pipe” from an iSCSI initiator to an iSCSI virtual target. A session is a group of TCP/IP connections that link an iSCSI initiator with an iSCSI virtual target. Connections can be added or removed from a session. Sessions are identified by a Session ID (SSID).
The following documentation is available for Brocade 48000 director and iSCSI blade: • Brocade 48000 Hardware Reference Manual • Brocade 48000 QuickStart Guide • FC4-16IP Hardware Reference Manual For practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through: http://www.amazon.
- Switch operating system version Error numbers and messages received supportSave command output Detailed description of the problem and specific questions Description of any troubleshooting steps already performed and results Serial console and telnet session logs syslog message logs 2. Switch Serial Number The switch serial number and corresponding bar code are provided on the serial number label, as illustrated below.
Contents About This Document Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . iii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . .iv Key terms. . . .
Configuring the GbE interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Assigning an IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Adding static IP routes (optional) . . . . . . . . . . . . . . . . . . . . . . . . 13 Verifying the network connection . . . . . . . . . . . . . . . . . . . . . . . . 14 Adding ARP entries (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Chapter 3 Configuring iSCSI Virtual Targets In this chapter . . . . . .
Creating an iSCSI FC zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Creating a zoning configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Chapter 5 Administering the iSNS Client In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Overview of iSNS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Displaying iSNS service status . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi iSCSI Gateway Service Administrator’s Guide Publication Number: 53-1000440-01
Chapter 1 Introduction to the iSCSI Gateway Service This chapter describes the FC4-16IP blade iSCSI gateway service. The iSCSI gateway service is supported only on the Brocade 48000 director running Fabric OS v5.2.0 or higher with one or more iSCSI-enabled FC4-16IP blades. In this chapter • Overview of iSCSI gateway service . . . . . . . . . . . . . . . 1 • Checklist for configuring iSCSI. . . . . . . . . . . . . . . . . . .
1 Overview of iSCSI gateway service 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.
Overview of iSCSI gateway service 1 PRESENTING FC TARGETS AS ISCSI VIRTUAL TARGETS Fabric OS provides the following two methods to map physical FC targets (LUNs) to iSCSI virtual targets (VTs): • “Basic LUN mapping” on page 3 • “Advanced LUN mapping” on page 4 Basic LUN mapping Fabric OS provides a mechanism that maps LUNs to iSCSI VTs, a one-to-one mapping with unique iSCSI Qualified Names (IQNs) for each target.
1 Overview of iSCSI gateway service 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.
Overview of iSCSI gateway service 1 The following figure shows an iSCSI gateway that has three iSCSI VTs and two iSCSI initiators. iS C S I initiator A iqn.2003-11.c om.mic ros oft: win2k-s n-192168101 iS C S I virtual targets (V T s ) VT 1 iqn.2002-12.c om.broc ade: 10: 00: 00: 05: 1e: aa: bb: c c IP Network VT 2 iqn.2002-12.c om.broc ade: 10: 00: 00: 05: 1e: c c : bb: aa VT 3 iqn.2002-12.c om.broc ade: 10: 00: 00: 05: 1e: bb: c c : aa iS C S I initiator B iiqn.2003-11.c om.
1 Overview of iSCSI gateway service 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.
Checklist for configuring iSCSI 1 Checklist for configuring iSCSI After you install the FC4-16IP blade in the Brocade 48000 director (see the Brocade FC4-16IP Hardware Reference Manual), you configure the iSCSI gateway service. The following table provides a high-level overview of the commands and links to the sections that detail the procedures. See the Fabric OS Command Reference for detailed information on the commands.
1 Checklist for configuring iSCSI TABLE 1 Configuring the iSCSI target gateway (Continued) Step Command Procedure 14 Create the iSCSI FC zone. zoneCreate “”, “,,..." “Creating an iSCSI FC zone” on page 35 15 Add iSCSI FC zone to zone configuration. cfgAdd “cfgname”, “zone1, zone2” 16 Enable zone configuration.
Chapter Configuring the FC4-16IP Blade 2 This chapter describes the initial setup required to deploy an iSCSI gateway solution. Install and configure the FC4-16IP blade in a Brocade 48000 as described in the Brocade FC4-16IP Hardware Reference Manual before performing these procedures. NOTE Only the Brocade 48000 with an iSCSI-enabled FC4-16IP blade running Fabric OS v5.2.0 or higher supports the iSCSI gateway service. In this chapter • • • • FC4-16IP port numbering. . . . . . . . . . . . . . . . . .
2 FC4-16IP port numbering 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. s c al e: 5/ 16" = 1" 56-0000590-01 Rev A ! ge7 ge7 ge6 ge5 ge4 G bE ports GE ge3 ge2 ge1 ge0 7 ge0 7 6 5 4 F C ports FC 3 2 1 0 0 FC4 16IP 40.
Enabling the iSCSI gateway service 2 Enabling the iSCSI gateway service The iSCSI gateway service translates and directs SCSI traffic between an iSCSI initiator and an FC target. This section explains how to enable the iSCSI gateway service on the Brocade 48000. To enable the iSCSI gateway service 1. Connect and log in to the switch. 2. Enter the following command to show the current Fabric OS configuration.
2 Configuring the GbE interface Arp configuration: IP Address Mac Address -----------------------------Iproute Configuration: IP Address Mask Gateway Metric -----------------------------------------------------switch:admin> 3. If Persistent Disable is set to ON, enter the portCfgPersistentEnable command with the slot number and GbE port number. switch:admin> portcfgpersistentenable 10/ge0 4.
Configuring the GbE interface 2 ASSIGNING AN IP ADDRESS Assign the IP address to the GbE port (iSCSI interface) using the portCfg command. NOTE The GbE port number below is entered geX; where X is from 0 through 7. For example ge1 (see Figure 8 on page 10). To assign the IP address and subnet mask 1. Connect and log in to the switch. 2.
2 Configuring the GbE interface VERIFYING THE NETWORK CONNECTION After you assign the IP address and (optionally) add static routes, use the portCmd command to ping a remote host. This ensures that data packets can be sent to the remote host over the (Ethernet) network. NOTE The GbE port number below is entered geX; where X is from 0 through 7. For example ge1 (see Figure 8 on page 10). To ping a remote location 1. Connect and log in to the switch. 2.
Chapter Configuring iSCSI Virtual Targets 3 This chapter explains how to create iSCSI virtual targets (VTs), discovery domains (DDs), discovery domain sets (DDSets), and how to configure iSCSI VT-iSCSI initiator authentication. In this chapter • • • • • • Changing and displaying the IQN Prefix . . . . . . . . . . . . . . . . . . . 15 Mapping FC targets to iSCSI VTs . . . . . . . . . . . . . . . . . . . . . . . . . 16 Configuring discovery domains . . . . . . . . . . . . . . . . . . . . . . . . .
3 Mapping FC targets to iSCSI VTs To display the IQN prefix 1. Connect and log in to the switch. 2. Enter the iscsiswCfg - -showgw command. The following is an example. iscsiSaturn1:root> iscsiswcfg --showgw Target name is: iqn.2007-12.com.brocade The operation completed successfully Mapping FC targets to iSCSI VTs You create iSCSI VTs using the LUN values of FC targets. The FC target must be accessible from the iSCSI gateway.
Mapping FC targets to iSCSI VTs 3 This could be a long-running operation. Continue [N]: y Index FC WWN iSCSI Name Status 9 2e:1f:00:06:2b:0d:10:ba iqn.2002-12.com.brocade:2e:1f:00:06:2b:0d:10:ba Operation Succeeded 10 2e:3f:00:06:2b:0d:10:ba iqn.2002-12.com.brocade:2e:3f:00:06:2b:0d:10:ba Operation Succeeded 11 2e:5f:00:06:2b:0d:10:ba iqn.2002-12.com.brocade:2e:5f:00:06:2b:0d:10:ba Operation Succeeded 12 2e:7f:00:06:2b:0d:10:ba iqn.2002-12.com.
3 Mapping FC targets to iSCSI VTs Name: State/Status: iqn.2002-12.com.brocade:2e:3f:00:06:2b:0d:10:ba Online/Defined Name: State/Status: iqn.2002-12.com.brocade:2e:5f:00:06:2b:0d:10:ba Online/Defined Name: State/Status: iqn.2002-12.com.brocade:2e:7f:00:06:2b:0d:10:ba Online/Defined Name: State/Status: iqn.2002-12.com.brocade:2e:9f:00:06:2b:0d:10:ba Online/Defined Name: State/Status: iqn.2002-12.com.brocade:2e:bf:00:06:2b:0d:10:ba Online/Defined Name: State/Status: iqn.2002-12.com.
Mapping FC targets to iSCSI VTs 3 Operation Succeeded 3. Enter the iscsicfg --show tgt command to display the status of the created iSCSI VTs: The following is an example. switch:admin> iscsicfg --show tgt Number of records found: 1 Name: iqn.2002-10.com.brocade:21:00:00:04:cf:e7:74:cf State/Status: Online/Defined Auth.
3 Mapping FC targets to iSCSI VTs CREATING ISCSI VTS MANUALLY Create iSCSI VTs manually when there are FC targets on the fabric that should not be mapped to an iSCSI VT and if you want to map more than one target to the same iSCSI VT or a LUN to an iSCSI VT.
Mapping FC targets to iSCSI VTs 3 Listing all available LUNs The fcLunQuery command displays a list of connected FC targets and shows the LUN configurations. To display LUN information 1. Connect and log in to the switch. 2. Enter the fcLunQuery command. The following is an example.
3 Mapping FC targets to iSCSI VTs Adding LUNs to the iSCSI VT The iscsiCfg --add lun command can be used to add the port WWN of the LUN to the iSCSI VT. Up to 256 LUNs can be mapped to an iSCSI VT. To add LUNs to an iSCSI VT 1. Connect to the switch and log in. 2. Enter the iscsiCfg --add lun command with –t , –w , and –l options to add an FC device to an existing iSCSI VT: where: -t Specifies the unique IQN name for the iSCSI VT in the format: iqn.2002-12.com.
Mapping FC targets to iSCSI VTs -l 3 Maps the physical FC LUNs to virtual iSCSI LUNs and is specified as a pair: LUNs:physical LUNs The following example maps two LUNs attached to port 2f:ff:00:06:2b:0d:12:99 to an iSCSI VT named iqn.2006-10.com.example:disk001: switch:admin> iscsicfg --add lun -t iqn.2006-10.com.example:disk001 \ -w 2f:ff:00:06:2b:0d:12:99 -l 1-2:0-1 The operation completed successfully. switch:admin> iscsicfg --show lun -t iqn.2006-10.com.
3 Displaying the iSCSI VT Displaying the iSCSI VT DISPLAYING LUN MAP CONFIGURATIONS This section shows how to display the iSCSI VT LUN maps. To display the iSCSI VT LUN map 1. Connect and log in to the switch. 2. Enter the iscsiCfg --show lun command as follows: switch:admin> iscsicfg --show lun Number of targets found: 2 Target: iqn.2006-10.com.example:disk001 Number of LUN Maps: 2 FC WWN Virtual LUN(s) 21:00:00:04:cf:e7:73:7e 0 2f:ff:00:06:2b:0d:12:99 1-2 Physical LUN(s) 0 0-1 Target: iqn.2002-10.com.
Configuring discovery domains 3 Configuring discovery domains This section explains how to configure access control between iSCSI initiators and iSCSI VTs manually using discovery domains and discovery domain sets configured on the fabric. If iSNS (internet storage name service) is enabled, then configure access control on the iSNS server; discovery domains and discovery domain sets configured in Fabric OS are not supported if the iSNS service is enabled on the fabric.
3 Configuring discovery domain sets 3. To verify enter the iscsiCfg --show dd command as follows: switch:admin> iscsicfg --show dd Number of records found: 1 Name: dd-host001 Status: Defined Num. Members: 2 iqn.1991-05.com.microsoft:host001.brocade.com iqn.2006-10.com.example:disk001 Configuring discovery domain sets You can create four discovery domain sets, but only one set can be enforced at a time.
Configuring iSCSI initiator-to-VT authentication 3 switch:admin> iscsicfg --enable ddset -n ddset-engineering This will enable the DDSet specified. Continue (yes, y, no, n) [n]: y The operation completed successfully. Configuring iSCSI initiator-to-VT authentication Fabric OS v5.2.0 or higher supports both one-way and mutual CHAP authentication for iSCSI initiator-to-iSCSI VT target sessions. The authentication method (CHAP or none) is set on a per-iSCSI VT basis.
3 Configuring iSCSI initiator-to-VT authentication BINDING USER NAMES TO AN ISCSI VT For additional security, you can bind specific user names to an already created iSCSI VT. When you do this, the specific user name and CHAP secret combination is required for authentication during the iSCSI login phase. The maximum number of user names that can be bound per iSCSI VT is 16. To bind a user name to an already created iSCSI VT 1. Connect and log in to the switch. 2.
Committing the iSCSI-related configuration 3 Committing the iSCSI-related configuration This section explains how to save iSCSI-related configuration parameters, including iSCSI VTs, discovery domains, discovery domain sets, and CHAP authentication, after they have been defined. Each set of changes, additions, and deletions is called a “transaction.” DISPLAYING CURRENT TRANSACTIONS Review the current transaction before committing the changes; once the changes are committed, they are enforced fabric-wide.
3 Committing the iSCSI-related configuration RESOLVING CONFLICTS When you merge two fabrics with different iSCSI configurations, a conflict will result. If there is a conflict, the database will not be merged and you must resolve the conflict. The iscsiCfg --show fabric command displays the “out of sync” state. The rest of the switches will function normally, however, since there is no segmentation of E_Ports as a result of discovery domain set database conflicts.
Enabling/disabling connection redirection for load balancing 3 Enabling/disabling connection redirection for load balancing Connection redirection allows iSCSI sessions to be evenly distributed across ports on the same blade. Before the maximum number of connections is reached for any given port, logins are redirected to the next available port, resulting in an even distribution of sessions. This distribution occurs only during the first login phase.
3 LUN masking considerations 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.
Chapter Creating the iSCSI FC Zone 4 This chapter describes how to create an iSCSI FC zone for discovery domains (DDs). NOTE If you do not have a zoning license or if zoning is not implemented, you do not need to create a zone for iSCSI target gateway service. In this chapter • Overview of iSCSI FC zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 • Creating an iSCSI FC zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 • Creating a zoning configuration. . . . . . . . . .
4 Overview of iSCSI FC zoning DD1 iS C S I virtual targets (V T s ) iS C S I G bE portal group FC T arget 1 iS C S I initiator A L UNs VT 1 IP network IP P ortal iS C S I virtual initiator IP P ortal iS C S I virtual initiator IP P ortal iS C S I virtual initiator IP P ortal iS C S I virtual initiator IP P ortal iS C S I virtual initiator L UNs VT 2 iS C S I initiator B DD2 VT 3 IP S AN FC T arget 3 L UNs FC iS C S I gateway s ervic e L UNs iS C S I zone FIGURE 9 FC T arget 2
Creating an iSCSI FC zone 4 Creating an iSCSI FC zone To create an iSCSI FC zone, you must include the following iSCSI elements in the zone: • The FC targets, used to create the virtual targets (VT) • The iSCSI virtual initiators (VIs): - If there is more than one FC4-16IP blade in the chassis, you must add all virtual initiators to the same zone. - If there is more than one FC4-16IP blade in the fabric, you must add all virtual initiators from all switches to the same zone.
4 Creating an iSCSI FC zone switch:admin> nsshow { Type Pid COS PortName NodeName TTL(sec) NL 0120d6; 3;21:00:00:04:cf:e7:74:cf;20:00:00:04:cf:e7:74:cf; na FC4s: FCP [SEAGATE ST336607FC 0004] Fabric Port Name: 20:20:00:60:69:e0:01:56 Permanent Port Name: 21:00:00:04:cf:e7:74:cf Port Index: 32 Share Area: No Device Shared in Other AD: No NL 0120d9; 3;21:00:00:04:cf:e7:73:7e;20:00:00:04:cf:e7:73:7e; na FC4s: FCP [SEAGATE ST336607FC 0004] Fabric Port Name: 20:20:00:60:69:e0:01:56 Permanent Port Name: 21:00:0
Creating an iSCSI FC zone 4 PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 30.0.127.33 Slot/Port: 3/ge3 Logical pn: 43" Fabric Port Name: 00:00:00:00:00:00:00:00 Permanent Port Name: 50:06:06:9e:00:15:63:18 Port Index: 43 Share Area: No Device Shared in Other AD: No N 012c00; 3;50:06:06:9e:00:15:63:20;50:06:06:9e:00:15:63:21; na FC4s: FCP PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 30.0.127.
4 Creating an iSCSI FC zone To create a zone alias 1. Connect and log in to the switch as admin. 2. Enter the aliCreate command. 3.
Creating a zoning configuration 4 You can create zones, add and remove members from a zone, and delete zones. These zone operations function the same way with iSCSI as without. To learn more about these operations, see “About Zones” in the Fabric OS Administrator’s Guide and the zoneCreate command in the Fabric OS Command Reference. Creating a zoning configuration After creating one or more zones, you can add them to the zoning configuration database and enable the zoning configuration.
4 40 Creating a zoning configuration iSCSI Gateway Service Administrator’s Guide Publication Number: 53-1000440-01
Chapter Administering the iSNS Client 5 This chapter explains how to enable the iSNS client on an iSCSI gateway and configure it with an iSNS server. The internet storage name service (iSNS) server facilitates the automatic discovery and manages access control of iSCSI VTs on a TCP/IP network. NOTE Fabric OS supports only Microsoft iSNS Server v3.0 and higher. In this chapter • • • • Overview of iSNS configuration . . . . . . . . . . . . . . . . . . . . . . . . . 42 Displaying iSNS service status. . .
5 Overview of iSNS configuration Overview of iSNS configuration iSNS clients initiate transactions with iSNS servers using the iSNS protocol, register available iSCSI VTs, download information about other registered clients (such as iSCSI initiators), and receive notification of events that occur in the DDs.
Enabling the iSNS client service 5 Enabling the iSNS client service This section explains how to enable the iSNS client service and configure the iSNS server IP address. Fabric OS supports one iSNS server connection. NOTE If DD and DDSets are configured on the fabric, clear the DD and DDSet configurations before enabling iSNS client services. To enable the iSNS client service 1. Connect to the switch and log in. 2.
5 Disabling the iSNS client service switch:admin> isnsccfg –set –m –s 10.33.56.105 iSNS client configuration updated: peering with iSNS server 10.33.56.105 on the management port. 5. Verify that the iSNS server has been configured correctly by entering the isnscCfg - -show command as follows: switch:admin> isnsccfg --show iSNS client is peering with iSNS server 10.33.56.105 on the management port. Operational Status: Connected to iSNS server. 6.
Appendix A Scalability Guidelines Table 2 lists scalability guidelines to consider when constructing iSCSI solutions on the FC4-16IP.
A 46 Scalability Guidelines iSCSI Gateway Service Administrator’s Guide Publication Number: 53-1000440-01
Appendix B Troubleshooting If you are having problems with iSCSI connectivity, use the following table to troubleshoot before calling your support provider. TABLE 3 Troubleshooting iSCSI connectivity Problem Cause Solution iSCSI host reports connection failed. Network connectivity is having problems.
B TABLE 3 Troubleshooting Troubleshooting iSCSI connectivity (Continued) Problem Cause Solution Changes made to the iSCSI database do not appear on iSCSI hosts. The DDSet has not been enabled or the database has not been committed. Check the currently enabled DD Set using: iscsiCfg - -show ddset Make sure it is reported as enabled and committed.
DRAFT: BROCADE CONFIDENTIAL Index Numerics 48000, 11 A access control, 41 configuring, DD, 25 AD0, 16 address resolution protocol, 14 alias creating zone, 38 zone, 37 aliCreate, 38 all access zone setting, 34 ARP, 14 adding entries, 14 authentication, 15 Challenge Handshake Authentication Protocol, 6 CHAP, 6, 7 method, 24 mutual, 6 one-way, 6 B Binding user names to an iSCSI VT, 28 blade FC4-16IP, 1, 35 FC4-16IP, configuring, 9 Brocade 48000, 11 C cfgClear, 34 cfgCreate, 39 cfgDisable, 34 iSCSI Gatewa
DRAFT: BROCADE CONFIDENTIAL D database iSCSI, 48 defZone, 47 device RAID, 47 devices zoning, 34 director SilkWorm 48000, 1 discovery domain configuration, 6 sets, 15 using to limit access, 5 discovery domains, 1, 15, 42 configuring, 25 displaying LUN, 21 LUN maps, 24 VT, state, 24 VT, status, 24 VTs, 24 WWNs, 35 E enabling zone configuration, 39 events notification of, 42 F FC target, 20 target LUN, 16 targets, 15 FC targets, 35 FC4-16IP, 35 FCIP tunneling service, 1, 9, 15, 41 fcLunQuery, 21, 47 Fibre C
DRAFT: BROCADE CONFIDENTIAL iSCSI, 1 components, 4 configuration checklist, 7 creating FC zones, 38 database, 48 enabling gateway service, 11 FC zone, 33 gateway, 41 Gateway Service, 1 gateway service, 34 gateway service, troubleshooting, 45, 47 initiator, 15 initiators, 42, 44 network, 42 translation, 2 virtual target, 22, 24 virtual target, creating, 20 virtual target, limiting access, 5 virtual targets, 3, 15, 16 VT, 15, 16, 20, 24 VT, user-defined, 22 VTs, 44 iSCSI gateway service enabling, 11 iSCSI Ta
DRAFT: BROCADE CONFIDENTIAL portCfgShow, 11, 12 portCmd, 14 ping, 14, 47 ports enabling, 11 GbE, enabling, 11 logical group, 37 portShow, 13, 14 ipif, 47 iproute, 47 protocol address resolution, 14 R RAID device, 47 route static, 13 S SCN notification, 41 setting all access, 34 no access, 34 shared secret, 7 state VT, 24 status iSNS service, 42 VT, 24 T V virtual target limiting access to, 5 state, 24 status, 24 virtual targets, 35 creating, 20 VT displaying, 24 VTs, 22, 35 W WWN, 18 WWNs, 35 displayi
