53-1000603-01 19 October 2007 iSCSI Gateway Service Administrator’s Guide Supporting Fabric OS v6.0.
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.
Contents About This Document Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . vii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . viii Key terms. . . . .
Configuring the GbE interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Assigning an IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Adding static IP routes (optional) . . . . . . . . . . . . . . . . . . . . . . . . 16 Verifying the network connection . . . . . . . . . . . . . . . . . . . . . . . . 16 Adding ARP entries (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Chapter 3 Configuring iSCSI Virtual Targets In this chapter . . . . . .
Creating an iSCSI FC zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Creating a zoning configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Chapter 5 Administering the iSNS Client In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Overview of iSNS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Displaying iSNS service status . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi iSCSI Gateway Service Administrator’s Guide 53-1000603-01
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 v6.0.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.
Key terms For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia.org/education/dictionary. For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary. The following terms are used in this manual to describe the iSCSI gateway service and its components. discovery domain (DD) A group of iSCSI virtual targets and iSCSI initiators. Discovery domains are used for access control and authentication.
iSCSI portal group A set of iSCSI-enabled ports. The portal group allows the iSCSI initiator to access iSCSI virtual targets using any available port. An iSCSI session may have several connections to an iSCSI VT on any port in the group. Each FC4-16IP blade has eight GbE ports. The portal group name is the slot number of the blade. All online iSCSI-enabled GbE ports participate in the portal group. iSCSI virtual target (iSCSI VT) An iSCSI representation of LUNs from one or more FC targets.
Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade resources The most recent version of documentation is provided on the Brocade Web site, through Brocade Connect. NOTE Go to http://www.brocade.com and click Brocade Connect to register at no cost for a user ID and password.
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.
• Brocade 3800 and 3900— Nonport side of the chassis • Brocade 4100, 4900, 5000 7500, and 7600—On the switch ID pull-out tab located inside the chassis on the port side on the left • Brocade 12000, 24000, and 48000—Inside the chassis next to the power supply bays • Brocade Multiprotocol Router Model AP7420—On the bottom of the chassis and on the back of the chassis. 3.
xiv iSCSI Gateway Service Administrator’s Guide 53-1000603-01
Chapter Introduction to the iSCSI Gateway Service 1 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 • Supported iSCSI initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Overview of iSCSI gateway service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Overview of iSCSI gateway service Overview of iSCSI gateway service 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.
Overview of iSCSI gateway service 1 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.
1 Overview of iSCSI gateway service 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” • “Advanced LUN mapping” 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.
Overview of iSCSI gateway service 1 F C target 1 LUN 0 iS C S I virtual target 1 1 LUN 2 0 3 1 4 2 5 F C target 2 iS C S I virtual target 2 LUN 0 LUN 20 21 22 iS C S I virtual target 3 23 LUN 24 0 25 FIGURE 5 iSCSI VT advanced LUN mapping Identifying iSCSI components See Figure 2 for a basic implementation with an IP network. The Brocade iSCSI gateway service supports IQN only to identify the iSCSI components, such as the iSCSI initiator and iSCSI VT.
1 Overview of iSCSI gateway service 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.
Overview of iSCSI gateway service 1 DDS et 1 iS C S I virtual targets (V T s ) DD1 iS C S I initiator A VT 1 IP network VT 2 VT 3 iS C S I initiator B DD2 FIGURE 7 iS C S I gateway s ervic e Discovery domain set configuration example Switch-to-iSCSI initiator authentication Authenticate iSCSI sessions using CHAP (Challenge Handshake Authentication Protocol).
1 Checklist for configuring iSCSI 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.
Checklist for configuring iSCSI TABLE 2 1 Configuring the iSCSI target gateway (Continued) Step Command Procedure 14 Create the iSCSI FC zone. zoneCreate “”, “,,..." “Creating an iSCSI FC zone” on page 39 15 Add iSCSI FC zone to zone configuration. cfgAdd “cfgname”, “zone1, zone2” 16 Enable zone configuration.
1 10 Checklist for configuring iSCSI iSCSI Gateway Service Administrator’s Guide 53-1000603-01
Chapter 2 Configuring the FC4-16IP Blade 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 Enabling the GbE interface To enable the physical ports 1. Connect and log in to the switch. 2. Enter the portCfgShow command with the blade slot number and GbE port number parameters to display the Persistent Disable setting of the port. switch:admin> portcfgshow 10/ge0 Mode: ISCSI Persistent Disable: ON Ipif configuration: Interface IP Address NetMask MTU ---------------------------------------------------------0 30.0.130.100 255.255.0.
Configuring the GbE interface 2 Configuring the GbE interface Configure the FC4-16IP GbE interface (TCP/IP) network settings and static IP routes. Use the portCfg commands to perform the following tasks: • • • • “Assigning an IP address” “Adding static IP routes (optional)” “Verifying the network connection” on page 16 “Adding ARP entries (optional)” on page 17 NOTE You can set the TCP/IP parameters of a GbE port even when iSCSI gateway service is disabled.
2 Configuring the GbE interface Adding static IP routes (optional) Define static routes to reach the destination IP through a preferred gateway. The gateway must be on the same subnet as the GbE port. You can specify a maximum of 32 routes per GbE port. NOTE The GbE port number below is entered geX; where X is from 0 through 7. For example ge1 (see Figure 8 on page 12). To add a static route 1. Connect and log in to the switch. 2.
Configuring the GbE interface 2 Adding ARP entries (optional) ARP entries for the IP interfaces are created automatically when you verify the network connectivity using the ping command. This command configures additional address resolution protocol (ARP) entries. NOTE The GbE port number below is entered geX; where X is from 0 through 7. For example ge1 (see Figure 8 on page 12). To automatically add ARP entries 1. Connect and log in to the switch. 2.
2 18 Configuring the GbE interface iSCSI Gateway Service Administrator’s Guide 53-1000603-01
Chapter 3 Configuring iSCSI Virtual Targets 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Mapping FC targets to iSCSI VTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • 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 The following is an example. switch:admin> iscsicfg --easycreate tgt This will create iSCSI targets for ALL FC targets. 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.
3 Mapping FC targets to iSCSI VTs 4. 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: 16 22 Name: State/Status: iqn.2002-12.com.brocade:2e:1f:00:06:2b:0d:10:ba Online/Defined 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.
Mapping FC targets to iSCSI VTs 3 To generate an iSCSI VT for a specific FC target 1. Connect and log in to the switch. 2. Enter the iscsiCfg --easycreate tgt command with the -w option to create an iSCSI VT that contains only the storage attached to the specified WWN: The default value of iqn.2002-12.com.brocade, is used for the fixed prefix, and the port WWN is used as the user-defined portion of the IQN. The following is an example.
3 Mapping FC targets to iSCSI VTs To create an iSCSI VT 1. Connect and log in to the switch. 2. Enter the iscsiCfg --create tgt command with the -t option. The value is an iSCSI Qualified Name entered in the form type.date.naming authority:. The following is an example, using the Brocade default for the type.date.naming authority: prefix portion of the IQN, followed by a WWN as the user defined portion.
Mapping FC targets to iSCSI VTs 3 Target Pid: 120d9 Number of LUNs returned by query: 1 LUN ID: 0x00 Target Index: 3 Target Node WWN: 2f:ff:00:06:2b:0d:12:99 Target Port WWN: 2f:ff:00:06:2b:0d:12:99 Target Pid: 12300 Number of LUNs returned by query: 16 LUN ID: 0x00 LUN ID: 0x01 LUN ID: 0x02 LUN ID: 0x03 LUN ID: 0x04 LUN ID: 0x05 LUN ID: 0x06 LUN ID: 0x07 LUN ID: 0x08 LUN ID: 0x09 LUN ID: 0x0a LUN ID: 0x0b LUN ID: 0x0c LUN ID: 0x0d LUN ID: 0x0e LUN ID: 0x0f Adding LUNs to the iSCSI VT The iscsiCfg --add
3 Mapping FC targets to iSCSI VTs The following is an example. switch:admin> iscsicfg --show lun -t iqn.2006-10.com.example:disk001 Number of targets found: 1 Target: iqn.2006-10.com.example:disk001 Number of LUN Maps: 1 FC WWN Virtual LUN(s) 21:00:00:04:cf:e7:73:7e 0 Physical LUN(s) 0 Mapping LUNs on a specific port to an iSCSI VT The iscsiCfg --add lun command can be used to map LUNs attached to a specific port to an iSCSI VT. To map LUNs on a specific port to an iSCSI VT 1.
Displaying the iSCSI VT 3 Deleting LUNs from an existing iSCSI VT The iscsiCfg --delete lun command can be used to delete LUNs from an existing iSCSI VT. The command can be used to delete individual LUNs, a list or range of LUNs, or all LUNs associated with an iSCSI VT. To delete LUNs from an iSCSI VT 1. Connect to the switch and log in. 2. Enter the iscsiCfg --delete lun command with –t , –w , and –l options to delete a LUN or LUNs.
3 Configuring discovery domains 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.brocade:21:00:00:04:cf:e7:74:cf Number of LUN Maps: 1 FC WWN Virtual LUN(s) Physical LUN(s) 21:00:00:04:cf:e7:74:cf 0 0x0000000000000000 Displaying iSCSI VT state and status This section explains how to list all the iSCSI VTs on the fabric.
Configuring discovery domains 3 A discovery domain (DD) controls iSCSI initiator access to iSCSI VTs. A DD is a group of iSCSI initiators and iSCSI VTs identified by IQNs. The iSCSI initiators can access only the iSCSI VTs that are in the DD to which they are assigned. When there are no discovery domains, all iSCSI initiators can access all iSCSI VTs. NOTE All iSCSI components in a DD must be identified using IQNs, see “Identifying iSCSI components” on page 5.
3 Configuring discovery domain sets Configuring discovery domain sets You can create four discovery domain sets, but only one set can be enforced at a time. Discovery domain sets allow you to enable and disable fabric-wide iSCSI VT access with a single command.
Configuring iSCSI initiator-to-VT authentication 3 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 Displaying CHAP configurations You can display a list of the user names that have been set up on the fabric for iSCSI initiator authentication. To display iSCSI VT authentication 1. Connect and log in to the switch. 2.
3 Committing the iSCSI-related configuration Saving current transactions Use the iscsiCfg command to commit the iSCSI changes. The --commit all option triggers propagation of the database to all iSCSI-capable platforms in the fabric and commits the changes. Make all necessary changes to the database—VT creation, LUN additions, DD creation, DDSet creation, and so on—before issuing the iscsicfg --commit all command. To save the transactions 1. Connect to the switch and log in. 2.
Enabling/disabling connection redirection for load balancing 3 4. On the switch with the database you want to use fabric-wide, enter the iscsiCfg --commit all command with the -f option as follows: switch:admin> iscsicfg --commit all -f This will commit ALL database changes made to all iSCSI switches in fabric. This could be a long-running operation. Continue (yes, y, no, n) [n]: y The operation completed successfully. 5.
3 LUN masking considerations To display connection redirection status 1. Connect to the switch and log in. 2. Enter the iscsiswCfg - -showconn command with the -s all option to display the current status of connection redirection. The following is an example. switch:admin>iscsiswcfg --showconn -s all Number of records found: 2 Slot ICR Status 10 enabled 1 disabled switch:admin> LUN masking considerations The node WWN and port WWN of the local switch are used to query LUNs on the physical target.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 • Creating an iSCSI FC zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 4.
Creating an iSCSI FC zone 4 You should add all virtual initiators for each blade to the zone. (The nsShow command example continues on the following page.) (The nsShow example continued) N 012b00; 3;50:06:06:9e:00:15:63:18;50:06:06:9e:00:15:63:19; na FC4s: FCP PortSymb: [23] "iSCSI Virtual Initiator" NodeSymb: [51] "IPAddr: 30.0.127.
4 Creating an iSCSI FC zone 5. Save the WWN information, which you will use for the zoneCreate command. At this point you are ready to create the iSCSI gateway service zone with FC targets and initiators as members of the zone. To simplify the process of creating the zone, begin by creating a zone alias. A “zone alias” is a logical group of WWNs or ports, which eliminates the need for long lists of individual zone member names.
Creating a zoning configuration 4 3. Enter the cfgSave command to save the change to the defined configuration. The following example illustrates the creation of a zone by specifying the aliases for FC targets and iSCSI virtual initiators as members of the named zone. switch:admin> cfgsave You are about to save the Defined zoning configuration. This action will only save the changes on the Defined configuration. Any changes made on the Effective configuration will not take effect until it is re-enabled.
4 Creating a zoning configuration To enable a zoning configuration 1. Connect and log in to the switch as admin. 2. Enter the cfgEnable command. 3. Enter the cfgSave command to save the change to the defined configuration. switch:admin> cfgenable iscsi_cfg001 You are about to enable a new zoning configuration. This action will replace the old zoning configuration with the current configuration selected.
Chapter 5 Administering the iSNS Client 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 The following is an example. 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 3 lists scalability guidelines to consider when constructing iSCSI solutions on the FC4-16IP.
A 50 Scalability Guidelines iSCSI Gateway Service Administrator’s Guide 53-1000603-01
Appendix B Troubleshooting If you are having problems with iSCSI connectivity, use the following table to troubleshoot before calling your support provider. TABLE 4 Troubleshooting iSCSI connectivity Problem Cause Solution iSCSI host reports connection failed. Network connectivity is having problems.
B TABLE 4 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.
Index Numerics 48000, 13 A access control, 45 configuring, DD, 28 AD0, 20 address resolution protocol, 17 alias creating zone, 42 zone, 42 aliCreate, 42 all access zone setting, 38 ARP, 17 adding entries, 17 authentication, 19 Challenge Handshake Authentication Protocol, 7 CHAP, 7, 8 method, 28 mutual, 7 one-way, 7 B Binding user names to an iSCSI VT, 32 blade FC4-16IP, 1, 39 FC4-16IP, configuring, 11 Brocade 48000, 13 C cfgClear, 38 cfgCreate, 43 cfgDisable, 38 iSCSI Gateway Service Administrator’s Gu
D database iSCSI, 52 defZone, 51 device RAID, 51 devices zoning, 38 director SilkWorm 48000, 1 discovery domain configuration, 7 sets, 19 using to limit access, 6 discovery domains, 2, 19, 46 configuring, 28 displaying LUN, 24 LUN maps, 27 VT, state, 28 VT, status, 28 VTs, 27 WWNs, 39 E enabling zone configuration, 44 events notification of, 46 F FC target, 23 target LUN, 20 targets, 19 FC targets, 39 FC4-16IP, 39 FCIP tunneling service, 1, 11, 19, 45 fcLunQuery, 24, 51 Fibre Channel targets, 4 fosConfig
iSCSI, 2 components, 5 configuration checklist, 8 creating FC zones, 42 database, 52 enabling gateway service, 13 FC zone, 37 gateway, 45 Gateway Service, 2 gateway service, 38 gateway service, troubleshooting, 49, 51 initiator, 19 initiators, 46, 48 network, 46 translation, 3 virtual target, 25, 27 virtual target, creating, 24 virtual target, limiting access, 6 virtual targets, 4, 19, 20 VT, 19, 20, 23, 28 VT, user-defined, 26 VTs, 48 iSCSI gateway service enabling, 13 iSCSI Target Gateway LUN mapping, x i
portCfgShow, 14 portCmd, 16 ping, 16, 51 ports enabling, 14 GbE, enabling, 13 logical group, 42 portShow, 15, 16, 17 ipif, 51 iproute, 51 protocol address resolution, 17 R RAID device, 51 route static, 16 S SCN notification, 45 setting all access, 38 no access, 38 shared secret, 8 state VT, 28 status iSNS service, 46 VT, 28 T V virtual target limiting access to, 6 state, 28 status, 28 virtual targets, 39 creating, 23 VT displaying, 27 VTs, 25, 39 W WWN, 23 WWNs, 39 displaying information, 39 logical gr
