HP StorageWorks C-Series iSCSI configuration guide Part number: AA-RW7PE-TE Fourth edition: December 2006
Legal and notice information © Copyright 2005 – 2006- Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration guide information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling iSCSI on the C-Series switch . . . . . . . . . . . . . . . Enabling the iSCSI interface . . . . . . . . . . . . . . . . . Configuring the Gigabit Ethernet interface . . . . . . . . . . . Testing connectivity . . . . . . . . . . . . . . . . . . . . . . Presenting iSCSI hosts as virtual Fibre Channel hosts . . . . . . . . Host side: iSCSI Initiator configuration . . . . . . . . . . . .
Figures 1 ..Typical IP/FC network structure . . . . . . . . . . . . . . . . . . . . . . 2 ..IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), 9216i switch map . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 ..Microsoft iSCSI Initiator icon . . . . . . . . . . . . . . . . . . . . . . . 4 ..iSCSI Initiator Properties window . . . . . . . . . . . . . . . . . . . . . 5 ..Add Target Portal window . . . . . . . . . . . . . . . . . . . . . . . . 6 ..
43 44 45 46 47 6 ..BBI main window . . . . . . . ..Switch Ports icon location . . . ..Disabling a port . . . . . . . ..Switch Ports Dashboard . . . . ..Assigning a static IP to a network . . . . . . . . . . . . . . . . interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1 ..C-Series iSCSI limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 .. iSCSI host limits for Windows 2003 . . . . . . . . . . . . . . . . . . . . . . .
About this guide This guide describes the basic setup and configuration for iSCSI using the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS 9216i Fibre Channel switch.
Using the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch in an iSCSI environment iSCSI protocol overview iSCSI is a SCSI transport protocol for mapping of block-oriented storage data over TCP/IP networks through iSCSI protocol data units (PDUs). The iSCSI protocol enables universal access to storage devices and storage area networks (SANs) over standard Ethernet-based TCP/IP networks.
well as helping to provide data security. An alternative is to use IPSec to secure the connection, although there will be a performance impact. Client, Host, or iSCSI Initiator has the ‘iSCSI Initiator’ loaded on it to enable Target Resource Recognition & Attachment. Storage Target Resources (LUNs) appear as if they are local drives attached directly to the system.
Figure 2 IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), and MDS 9216i switch map In conjunction with presenting Fibre Channel targets to iSCSI hosts, the IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i switch present each iSCSI host as a Fibre Channel host (in transparent mode), that is, as a host bus adapter (HBA) to the Fibre Channel storage device.
Fibre Channel switches The C-Series IP Storage Services Modules (IPS-4, IPS-8), and Multi–protocol Services Module (14/2) are supported with the following HP C-Series Product Line switches: • MDS 9216, MDS 9216A, MDS 9216i Multilayer Fabric Switches • MDS 9506, MDS 9509, MDS 9513 Multilayer Director Switches NOTE: The MDS 9216i switch contains two embedded IP ports. Operating system software and iSCSI Initiator support Refer to the HP StorageWorks C-Series iSCSI support tables located at: http://www.hp.
C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i configuration constraints C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2) and MDS 9216i constraints Table 1 C-Series iSCSI limits iSCSI component Maximum iSCSI host connections per port 200 Active LUNs per port 200 Number of Initiator/Targets (IT) Nexus per port 200 Number of active LUNs per IT Nexus 256 Number of IT Nexus/LUNs combinations per port 1
4. Zone the iSCSI initiator WWPN with Fibre Channel storage WWPN 5. Create an iSCSI host These procedures are described in the following sections. They enable you to quickly set up a basic connection between an iSCSI server and Fibre Channel storage. For advanced configuration parameters such as CHAP, VRRP, or VSANs, refer to the appropriate Cisco technical manuals and your iSCSI Initiator documentation. NOTE: This section uses Microsoft Windows in examples where host software is configured for iSCSI.
To configure IP for subsequent use by iSCSI initiators: 1. Enter configuration mode: switch# config terminal 2. Enter the interface configuration mode on the Gigabit Ethernet interface (slot 2, port 2): switch(config)# interface gigabitethernet 2/2 3. Enter the IP address (33.33.33.170) and subnet mask (255.255.255.0) for the Gigabit Ethernet interface: switch(config-if)# ip address 33.33.33.170 255.255.255.0 4.
During setup, the install procedure places a Microsoft iSCSI Initiator icon (Figure 3) on the server desktop as well as in the control panel. The Microsoft iSCSI Initiator also has a CLI. Refer to the user guide for more information. Figure 3 Microsoft iSCSI Initiator icon To install the Microsoft iSCSI Initiator: 1. Double-click the Microsoft iSCSI Initiator icon to open the iSCSI Initiator Properties window (Figure 4). Figure 4 iSCSI Initiator Properties window 2.
• Socket 4. Click OK. The IP address is added to the Available Portals list (Figure 6). The iSCSI Initiator connects to the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2),, or MDS 9216i switch. The C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2), or MDS 9216i switch generates a unique WWPN for the iSCSI initiator’s IP address.
• With the CLI: Enter the show iSCSI initiator command. Example: MDS9216i# show iscsi initiator iSCSI Node name is iqn.1991-05.com.microsoft:w2k3x03.sanbox.com Initiator ip addr (s): 33.33.33.
7. Select Admin > Save Configuration from the Device Manager tool bar. • With the CLI: 1. Enter the show iscsi initiator command to view the iSCSI initiators. Example: MDS9216i# show iscsi initiator iSCSI Node name is iqn.1991-05.com.microsoft:w2k3x03.sanbox.com Initiator ip addr (s): 33.33.33.
You can use either Fabric Manager or the switch CLI to create and modify SAN zones. As a best practice of SAN management, HP recommends that you create separate iSCSI zones that contain the iSCSI WWPNs and the storage WWPNs it will access. Refer to the Cisco configuration documentation to create, modify, or activate SAN zones.
The iSCSI Initiator rescans the connection to the storage port. Upon successful rescan, the iqn of the storage controller port appears under Name with a status of Inactive (Figure 10). Figure 10 Available targets—Inactive status 2. Select the storage controller Name and then click Log On. The Log On to Target window appears (Figure 11).
Figure 11 Log On to Target—Set persistent target 3. Select the Automatically restore this connection when the system boots check box to ensure that the controller port is enabled as a persistent target. 4. Click OK. The Available Target window shows the status for the storage controller iqn as Connected (Figure 12). Figure 12 Available targets window—Connected status 5. Click the Active Sessions tab to verify the connection to the EVA. The storage controller session Status appears as Connected (Figure 13).
Figure 13 Active Sessions tab—Connected status Installing the EVA CCL Drivers on the iSCSI initiator At this point, the Windows New Hardware Found Wizard may appear, because the EVA (Command Console LUN) CCL was discovered by the operating system. This Wizard requires the following two files: • The EVA CCL driver—HsgCCL.inf • The Windows security file—HsgCCL.cat These files are located on the Windows EVA Platform Kit CD.
Presenting EVA LUNs to the iSCSI initiator After the iSCSI Initiator connects to the EVA controller, the EVA recognizes the iSCSI Initiator WWPN that was mapped from the C-Series IP Storage Services Modules (IPS-4, IPS-8), Multi-protocol Services Module (14/2),, or MDS 9216i switch as if it were a Fibre Channel HBA. The EVA can use the iSCSI Initiator WWPN to create a host entry and present LUNs to the host entry. NOTE: This section describes configuring LUNs on an EVA.
Figure 15 Add a Host window 3. Enter information into the following boxes: • Host name • Port WW Name • Host OS 4. Click Add host. The new Port WW Name is added to the Port WW Name list. The host name appears in the Hosts folder (Figure 16). Figure 16 Hosts folder—Host Properties Creating LUNs for assignment to the new host To create LUNs: 1. Select the Storage Array icon and click on the Virtual Disks folder (Figure 17).
Figure 17 Virtual Disk—Folder Properties 2. Click Create Vdisk. The Create a Vdisk Family window appears (Figure 18). Figure 18 Create a Vdisk Family window, Page 1 NOTE: The example in Figure 18 shows an example of creating a 4 GB Raid, 5 LUN and presenting it to the EVA iSCSI Initiator Host Entry W2K3X03. 3.
4. Click Next step. The next Create a Vdisk Family window appears (Figure 19). Figure 19 Create a Vdisk Family window, Page 2 5. Enter a number in the Available LUN for this host box. The LUN is sent to the iSCSI host. 6. Click Finish. 7. Repeat the procedure to create additional LUNs as needed. The new LUNs are listed under the Virtual Disks folder (Figure 20). Figure 20 Vdisk Active Member Properties The new LUN is available to the iSCSI Initiator. To verify the availability of the LUN: 1.
NOTE: The EVA CCL appears as an Unavailable device. Figure 21 iSCSI Initiator Properties—Session Details Under Windows Disk Management, the LUNs appear as initialized partitions (Figure 22). You can configure the disk partition like any other disk partition available to the operating system. NOTE: The Microsoft iSCSI Initiator does not support dynamic partitions.
Configuring SANs with C-Series switches, iSCSI, and multi-path access to EVA4000/6000/8000 storage in a Windows environment To configure iSCSI in a Windows environment that includes multi-pathing and EVA storage: 1. 2. 3. 4. 5. 6. 7.
• All non-HP multi-pathing products except for Microsoft MPIO for Windows Installing the Microsoft iSCSI Initiator The IP host uses its NICs and the Microsoft iSCSI Initiator to enable iSCSI. The Microsoft iSCSI Initiator is configured with the GbE address of each iSCSI interface that the host will access. Setup Uninstall any installed version of the Microsoft Initiator before installing the current version. Download the iSCSI Initiator and User’s Guide (uguide.
The configuration and verification commands for the iSCSI feature are available when iSCSI is enabled on the switch. When you disable iSCSI, all associated configurations are automatically discarded. To use the CLI to enable iSCSI on a C-Series switch: 1. Enter configuration mode: switch # config terminal 2. Enable iSCSI on the switch: switch (config) # iscsi enable switch (config) # exit Enabling the iSCSI interface You must enable the iSCSI interface before traffic can flow on the GbE interface.
Testing connectivity To test connectivity, issue the ping command from the host (ping the C-Series Fibre Channel switches) and the switches (ping the server’s two IP addresses). If host and switches are able to ping each other’s respective IP addresses you can proceed with the final steps. Presenting iSCSI hosts as virtual Fibre Channel hosts After establishing IP connectivity, you must configure the host and switches for iSCSI discovery and login.
Figure 26 Add Target Portal window 3. Enter the IP address or DNS name of the first configured iSCSI GbE port. 4. Click OK. 5. Repeat steps 2 through 4 using the IP address or DNS name of the second configured iSCSI GbE port. The IP addresses are now added to the list of Target Portals (Figure 27). The iSCSI Initiator has connected to the iSCSI-enabled C-Series switch. The switch generates a unique virtual WWPN for the iSCSI Initiator’s IP address.
Figure 27 Both C-Series switches are target portals C-Series switch side: configuring transparent-mode static mapping The iSCSI-enabled C-Series switches have two modes of mapping IP addresses: • Transparent-mode dynamic mapping • Transparent-mode static mapping You must enable static mapping for each iSCSI Initiator for persistent LUN mapping from the Fibre Channel storage controller. 1. Using the Cisco Device Manager, select IP > iSCSI from the menu bar. The IP iSCSI window opens (Figure 28).
Figure 29 Discovery Dynamic check box 3. Select the Node Address Persistent check box (Figure 30). 4. Select the Node Address System Assigned check box (Figure 30). Figure 30 Node Address Persistent and Node Address System Assigned check boxes 5. 6. 7. 8. Click Apply. Close the IP iSCSI window. Select Admin > Save Configuration from the Device Manager menu bar. Configure transparent-mode static mapping on both iSCSI-enabled C-Series switches.
Figure 31 iSCSI Initiator zoned with an EVA storage port Virtual targeting Before the iSCSI Initiator can log in to the storage controller, you must create virtual targets on each C-Series Fibre Channel switch in the iSCSI window. 1. Using the Cisco Device Manager, select IP > iSCSI from the Device Manager menu bar. The IP iSCSI window opens (Figure 28). 2. Click the Targets tab (Figure 32). Figure 32 The Targets tab 3. Click Create. The Create iSCSI Targets window opens (Figure 33). 4. 5. 6. 7.
Figure 33 Create iSCSI Targets window 8. Click Create. 9. Select Admin > Save Configuration from the Device Manager menu bar. Repeat all of the above steps for the other C-Series switch. The iSCSI-enabled C-Series Fibre Channel switch setup is now complete. Creating an iSCSI host The host iSCSI Initiator must log in to the EVA storage controller before LUNs may be created.
Figure 34 Virtual targets defined for host 2. Select a target and click Log On…. The Log On to Target window opens (Figure 35). Figure 35 Log On to Target window 3. Select the Automatically restore this connection when the system boots and the Enable multi-path check boxes to ensure that the controller port is enabled as a persistent target and is able to utilize multi-pathing (Figure 35). 4. Click OK. 5. Repeat Steps 2 through 4 for all available virtual targets.
Installing the EVA CCL Driver on the iSCSI Initiator With the targets connected to the iSCSI host, Windows discovers the EVA Command Console LUN (CCL). The New Hardware Found Wizard opens and installs the driver. This Wizard requires the following two files: • sacd.inf – EVA CCL driver • sacd.cat – Windows Security File These files are located in the smart component file provided with any Fibre Channel HBA. Fibre Channel HBA smart component files are available on the HP web site.
Figure 37 Rescanning disks Setting MPIO load balancing policy You must specify how the iSCSI targets will manage and share network traffic for the host. For both targets: 1. Open the Microsoft iSCSI Initiator Properties window. 2. Click the Targets tab. 3. Select a target and click Details. A Target Properties window opens. 4. Click the Devices tab. 5. Select the appropriate device and click Advanced. A Device Details window opens. 6. Select a load balance policy from the list (Figure 38).
Figure 38 Selecting Load Balance Policy 7. Repeat steps 3 through 6 for the other target. 8. On the iSCSI-enabled C-Series Fibre Channel switch in the IP > iSCSI window, click the Session Initiators tab to verify C-Series iSCSI sessions (Figure 39). Figure 39 Verifying C-Series iSCSI sessions Configuring p-Class Blade servers in an iSCSI environment This section describes the procedures to prepare a p-Class Blade server for inclusion in an iSCSI environment.
Setup If you are not using DHCP, follow the setup instructions in the Cisco Gigabit Ethernet Switch Module for HP p-Class BladeSystem Software Configuration Guide, to assign the CGESM an IP address. Use a web browser to access the configuration management and operation features at http://10.10.10.168:80, where 80 is the default port number.. Use the web interface to disable the cross connection (XConnects) (ports 17 and 18) and to ensure all ports are in the same VLAN.
Figure 40 Switch web page 3. Click ’Port Settings’. 4. Disable port 17 and port 18 (Figure 41).
Figure 41 Disabling a port 5. Click Submit (Figure 41). Verifying VLAN settings After disabling the XConnects, verify that each port used in the iSCSI setup is enabled and is part of the same VLAN. To verify: 1. From Windows Start, select Run. 2. Enter “telnet” in the Run dialog box. 3. Log in to Interconnect A or B and run the command “show vlan” (Figure 42). NOTE: All ports are members of the same VLAN and are in VLAN 1 by default. Verify the VLAN settings for Interconnects A and B.
(XConnects) (ports 17 and 18) and to ensure all ports are in the same VLAN. For information on the BBI see the HP ProLiant BL p-Class GbE2 Interconnect Switch Browser-based Interface Reference Guide. Disabling the cross connection ports With XConnects between Interconnect A and Interconnect B, the multi-path solution may use loops established at the interconnect switching level. To avoid this disable the XConnects. Each interconnect model has different XConnect ports.
Figure 45 Disabling a port 6. Click Apply and then click Save. Verifying VLAN settings After disabling the XConnects, verify that each port used in the iSCSI setup is enabled and is part of the same VLAN. To do this, click DASHBOARD at the top of the BBI main window and navigate to Switch >> Switch Ports (Figure 46). Ports 1 to 12, 22, and 24 are operational and enabled. NOTE: All ports are members of the same VLAN (PVID 1). Verify the VLAN settings for Interconnects A and B.
Figure 46 Switch Ports Dashboard Configuring p-Class Blade server network settings Depending on the model, each p-Class Blade server has two or four network interfaces. These interfaces are split between Interconnect A and Interconnect B. To ensure proper multi-path setup, one interface from each interconnect is assigned a unique static IP address. In this example, 20.20.20.230 is the IP address for one network interface, and 20.20.21.230 is the IP address for the other network interface (Figure 47).
Figure 47 Assigning a static IP to a network interface C-Series iSCSI 49
