HP StorageWorks EVA4400 iscsi Connectivity Option (mpx100b) 5.0. Release Notes

Transcription

1 HP StorageWorks EVA4400 iscsi Connectivity Option (mpx100b) 5.0 Release Notes Part Number: Ninth edition: June 2010

2 Legal and notice information Copyright Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Apple, Mac OS, and Macintosh are registered trademarks of Apple, Inc. Linux is a registered trademark of Linus Torvalds. Microsoft, Windows, and Windows XP are U.S. registered trademarks of Microsoft Corporation. QLogic is a trademark of QLogic Corporation. Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries. Sun and Solaris are registered trademarks of Sun Microsystems, Inc. SUSE is a registered trademark of Novell, Inc. in the United States and other countries.

3 Description The EVA4400 iscsi Connectivity Option (mpx100b) provides iscsi connectivity to the HP StorageWorks 4400 Enterprise Virtual Array (EVA4400) Fibre Channel storage systems. You can order: AJ713A with an EVA4400 storage system or to upgrade an existing EVA4400 storage system. This option includes one mpx100b hardware unit and the components needed for installation in any EVA cabinet. AJ714A with the AJ713A Connectivity Option and an EVA4400 storage system with iscsi connectivity to provide high-availability multipath connectivity or to upgrade an existing EVA4400 storage system for multipathing. This option includes a redundant mpx100b hardware unit for customers who require high availability. T5471A (optional) HP StorageWorks EVA4400 iscsi Connectivity 32 Initiator Upgrade License (LTU) for use with the EVA4400 and mpx100b only. Install one upgrade license to increase the number of iscsi initiators from 16 to 48. Install a second upgrade license to increase the number of iscsi initiators from 48 up to the maximum supported limit of 150. Purpose of the update The mpx100b firmware version for this release is This release includes the following fixes and updates: mpx100b iscsi ports hang when properties are modified Failure to connect to the mpx100b using Telnet or the serial port. Added support for disabling ftp access. The default setting is enabled. Product models The following EVA4400 iscsi Connectivity Option (mpx100b) product models are available: HP StorageWorks EVA4400 iscsi Connectivity Option (AJ713A) HP StorageWorks EVA4400 iscsi Upgrade Option (AJ714A) The following options: Two 4-Gb copper cables (AG311A) 4-Gb shortwave single SFP transceivers (A7446B) HP StorageWorks EVA4400 iscsi Connectivity 32 Initiator Upgrade License (LTU) (T5471A) Products supported For the latest product support information, see the Single Point of Connectivity Knowledge (SPOCK) on the HP website: You must sign up for an HP Passport to access the website. Operating systems The EVA4400 iscsi Connectivity Option (mpx100b) is available for the following operating systems: EVA4400 iscsi Connectivity Option (mpx100b) 5.0 3

4 Apple Mac OS X (Power Mac G5, Xserve, Mac Pro) Linux Red Hat (32/64-bit, IA64) Linux SUSE (x86 32/64-bit, IA64) Microsoft Windows Sun Solaris VMware ESX For the latest product support information, see SPOCK on the HP website: You must sign up for an HP Passport to access the website. Prerequisites The following are prerequisites for installing the EVA4400 iscsi Connectivity Option (mpx100b): EVA4400 HP StorageWorks Command View EVA Installation instructions For information about installing these products, see the HP StorageWorks EVA iscsi connectivity quick start instructions for Windows and the HP StorageWorks EVA iscsi connectivity user guide, available on the HP website: index.html. Important information This section contains important notes and workarounds for installation and use. Using MPIO with Windows 2003 For Windows 2003 with raw disk device access, when using Microsoft Initiator version 2.07, MPIO load balance policy must be set to Failover Only. For file system disk access or when using Microsoft Initiator version 2.08, all MPIO load balance policies are supported. ECC error fix console message An ECC error fix message similar to the following may be displayed on the mpx100b console. The ECC management software displays this message when it performs a NAND flash memory check or correction. ecc error fix performed on chunk 46349:0 This message indicates that an error correction has occurred. No user action is required. 4

5 isns IP address and IPv4, IPv6 When the IP address for the isns server is changed from an IPv4 address to an IPv6 address, or from an IPv6 address to an IPv4 address, the command completes successfully but the change does not take place. Disable isns for the existing address before setting the new address. Sequence out-of-range errors Microsoft initiator The CmdSN out of range error messages may be logged as Critical. You can view them by issuing a show logs command to the mpx100b. Despite the message, this is not a critical issue; it is displayed only when using the Microsoft initiator. The commands are reissued and completed to the target. Incorrect function error during isns registration You may see the incorrect function error during the Microsoft iscsi initiator's initial isns target discovery. To complete the isns target discovery, click the Refresh button on the Target tab in the iscsi initiator GUI. OS-type change ineffective If you attempt to change the OS type on a pair of redundant mpx100b's using the GUI or the command line interface (CLI), HP Command View EVA may not display the change properly due to a mismatch between the mpx pair. Sun Solaris server does not support EVA LUN 0 By default, LUN 0 is assigned to an iscsi initiator when the initiator logs in to the mpx100b iscsi target and when HP Command View EVA presents a virtual disk to an iscsi host. Because the Solaris iscsi initiator does not recognize LUN 0 as the EVA controller console LUN, the initiator tries to bring LUN 0 online, resulting in the following warning: Mar 21 08:04:09 hdxs8j: [ID kern.warning] WARNING: iscsi driver unable to online iqn com.hp:fcgw.mpx100b:hdxh05 m fe1500aef fe1500aef68 LUN 0 To prevent LUN 0 from being sent to the Solaris iscsi initiator, disable the Controller Lun AutoMap parameter with the mpx100b system settings. This also prevents LUN 0 from being presented to any host entry in HP Command View EVA 8.0 with any iscsi host mode setting of Solaris. LUN 0 is the HSV controller device. By default, the HSV is not included in the /kernel/drv/ scsi_vhci.conf file and is treated as an asymmetrical device for LUN access. EVA4400 iscsi Connectivity Option (mpx100b) 5.0 5

6 If the following lines are added to the /kernel/drv/scsi_vhci.conf file with LUN 0 present, any mpathadm command will panic the server after reboot: device-type-scsi-options-list = HP HSV, symmetric-option ; symmetric-option = 0x ; 1 During the initial Solaris iscsi initiator setup, LUN 0 must be disabled from the mpx100b. To disable the Controller Lun AutoMap parameter using the mpx100b CLI: 1. Use Telnet to connect to the mpx100b management port, or connect to the serial port using the connector supplied by HP. NOTE: The mpx100b management port default IP address is / The mpx100b serial port default setting is /8/n/1. 2. Log in using the following: User name: guest Password: password 3. Enable administrator privileges by entering the following: admin start config 4. Enter the set system command and follow the prompts to disable the Controller Lun AutoMap parameter: mpx100b (admin) #> set system A list of attributes with formatting and current values will follow. Enter a new value or simply press the ENTER key to accept the current value. If you wish to terminate this process before reaching the end of the list press 'q' or 'Q' and the ENTER key to do so. WARNING: If enabled by operator, the Symbolic Name can be embedded as part of the IQN. Only valid iscsi name characters will be accepted. Valid characters include alphabetical (a-z, A-Z), numerical (0-9), colon, hyphen, and period. Changes to the Settings below will be effective after a reboot. System Symbolic Name (Max = 64 characters) [mpx ] Embed Symbolic Name (0=Enable,1=Disable) [Enabled ] Controller Lun AutoMap (0=Enable, 1=Disable) [Enabled ] 1 System Log Level (Min = 0, Max = 3) [0 ] Please reboot the system for these changes to take effect. mpx100b (admin) #> 2 If LUN 0 is presented to the Solaris iscsi initiator: 6

7 1. Use Telnet to connect to the mpx100b management port, or connect to the mpx100b serial port using the connector supplied by HP. NOTE: The mpx100b management port default IP address is / The mpx100b serial port default setting is /8/n/1. 2. Log in using the following: User name: guest Password: password 3. Enable administrator privileges by entering the following: admin start config EVA4400 iscsi Connectivity Option (mpx100b) 5.0 7

8 4. Issue the lunmask rm command and follow the prompts to remove the Solaris iscsi initiator from each iscsi-presented target. For example: > telnet login: guest password: password >admin start password: config mpx100b (admin) #> lunmask rm Index (WWNN,WWPN/iSCSI Name) 50:00:1f:e1:50:00:2f:70,50:00:1f:e1:50:00:2f:7e Please select a Target from the list above ('q' to quit): 0 LUN Vendor 0 HP 1 HP 2 HP 3 HP 4 HP... Please select a LUN from the list above ('q' to quit): 0 Index Initiator 0 iqn com:sanlabmac-s01 1 iqn com.sun:rack81-s16 2 iqn com.microsoft:rack77-s16.sanbox.com 3 iqn com.microsoft:rack77-s14.sanbox.com 4 iqn de.suse:bl7-04.sanbox.com 5 iqn de.suse:bl7-03.sanbox.com 6 iqn de.suse:bl7-02.sanbox.com... Please select an Initiator to remove ('a' to remove all, 'q' to quit): 1 All attribute values that have been changed will now be saved. mpx100b (admin) #> Configuring the Symbolic Name You can use the Symbolic Name to determine mpx100b availability. To modify the Symbolic Name attribute, use the HP StorageWorks mpx100 Manager GUI or the mpx100b CLI. A Symbolic Name is optional, and the default attribute is blank. Typically, the iscsi port iscsi Qualified Name (IQN) target name is presented as follows: iqn com.hp:fcgw.mpx100b: fe150002f fe150002f7f Where: 8

9 qn com.hp:fcgw.mpx100 is the standard IQN for all mpx100s. 1 is the iscsi part number fe150002f fe150002f7f is the presented EVA port. If you enter a name in the Symbolic Name attribute, the iscsi port IQN target name presented to iscsi initiators and isns servers shows the Symbolic Name. For example, the following iscsi port IQN target name has the Symbolic Name blg2-lab embedded in it: iqn com.hp:fcgw.mpx100b:blg2-lab fe150002f fe150002f7f Where: iqn com.hp:fcgw.mpx100 is the standard IQN for all mpx100s. blg2 lab is the Symbolic Name. 1 is the iscsi port number fe150002f fe150002f7f is the presented EVA port. For details about modifying the Symbolic Name, see the HP StorageWorks EVA iscsi connectivity user guide. NOTE: HP recommends adding a Symbolic Name to the iscsi port IQN target name when presenting the target to an isns server. Mac iscsi initiator may lose iscsi connectivity to LUNs if the Mac server has Sleep mode enabled The ATTO iscsi initiator does not support the Mac server Sleep mode. If the Mac goes to sleep because the server Sleep mode is enabled, it may lose the iscsi connections to its EVA LUNs. Disable Mac server Sleep mode if the ATTO iscsi initiator is installed. DHCP-assigned IP address of mpx100b's management port may confuse HP Command View EVA When an mpx100b management port IP address is configured using Dynamic Host Configuration Protocol (DHCP), HP Command View EVA initially discovers the mpx100b. However, HP Command View EVA does not rediscover the management port IP address of the mpx100b when a new IP address is assigned by DHCP. When you configure an mpx100b management port, select only the static IP address option. mpx100b and CHAP security with Linux The Challenge Handshake Authentication Protocol (CHAP) setup with the Linux iscsi initiator is not supported with the mpx100b. The Linux iscsi driver omits CHAP security negotiations at login. EVA4400 iscsi Connectivity Option (mpx100b) 5.0 9

10 The CHAP setup issue will be resolved in a future release of the Linux initiator. Windows drops the IP connection Certain I/O workloads can result in LUN removal because Windows has dropped the IP connection. The connection can be restored by rebooting the system. To avoid dropped connections, do one of the following: Reduce the I/O workload Use a smaller application transfer size HP StorageWorks High-Availability Fabric Manager (HAFM) for M-series Fibre Channel switches does not recognize the mpx100b The M-series Zoning Manager does not recognize the world wide port names (WWPNs) of the mpx100b as Fibre Channel HBAs. Instead, the M-series Zoning Manager sees the WWPNs as switches, so they do not appear as devices to zone. Use one of the following M-series applications to configure zones that include the mpx100b WWPNs: For versions earlier than HAFM 8, use Embedded Web Server (EWS). For HAFM 8 and later versions, use HAFM Basic. NOTE: After configuring the zones, you must update HAFM to include these changes. iscsi initiator no longer logs in to the target after changing the initiator IQN The iscsi name structure is fairly rigid and contains two parts: a type designator followed by a unique name. Table 1 displays the type designators for iscsi. Table 1 Type designators for iscsi Type designator iscsi qualified name IEEE EUI-64 identifier in ASCII-encoded hexadecimal Unique name iqn eui The following example shows an iqn string: iqn com.microsoft:imthe.firstone.net 10

11 The type designator consists of the following parameters: The string iqn followed by a dot (.) A date code, in yyyy-mm format, followed by another dot (.) A reverse domain name (Optional) A string followed by a colon (:) If you are using only ASCII characters (U+0000 to U+007F), the following characters are allowed: ASCII dash character ( - = U+002d) ASCII dot character (. = U+002e) ASCII colon character ( : = U+003a) ASCII lowercase characters ( a.. z = U U+007a) ASCII numeric characters ( = U U+0039) NOTE: See section of Request for Comments (RFC) 3720 (iscsi) for a description of the iscsi name string profile. You can access RFC 3720 at ftp://ftp.rfc-editor.org/in-notes/ rfc3720.txt. Use the correct IQN syntax, as described in section of RFC 3720: For Windows In the initiator GUI, click Reset under Change in the General tab to reset the IQN to the original name that was created when you installed the initiator. For Linux Edit the InitiatorName setting in the initiatorname.iscsi file using the correct syntax. For Linux and Windows Reinstall the initiator to create a valid IQN. iscsi initiator LUNs disappear after changing the initiator IQN The mpx100b maintains a database of targets, initiators, and LUNs, and the corresponding links between them. When HP Command View EVA presents or removes a LUN from an iscsi initiator, it updates the mpx100b database. When a new IQN logs in to the mpx100b, it is considered a new initiator and no LUNs are assigned to it. All LUN assignments to the old IQN are maintained. Using HP Command View EVA, unpresent the LUN from the old initiator IQN and present it to the new initiator IQN. Remove the old initiator from the mpx100b database with either the mpx100b Manager GUI or the CLI. EVA4400 iscsi Connectivity Option (mpx100b)

12 Windows iscsi initiators must add Tcp1323Opts to registry CAUTION: Using the Registry Editor incorrectly can cause serious problems that may require reinstallation of the operating system. Back up the registry before making any changes. Use the Registry Editor at your own risk. Timestamps enable TCP to measure the round-trip time (RTT) accurately to adjust retransmission timeouts. The Timestamps option provides two timestamp fields of 4 bytes each in the TCP header: one to record the time of the initial transmission, and one to record the time on the remote host. To enable timestamps, the Tcp1323Opts entry must be set to REG_DWORD = 2 under HKLM\ SYSTEM\CurrentControlSet\Services\Tcpip\Parameters. IMPORTANT: Installing the Windows iscsi initiator from the HP StorageWorks iscsi Connectivity Option for Enterprise Virtual Array Windows software kit automatically adds the registry setting. Make the change to the registry or cut and paste the following lines to a text file named tcp1323opts.reg: tcp1323opts.reg. : REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\Current- ControlSet\Services\Tcpip\Parameters] "Tcp1323Opts"=dword: Double-click the file to add changes to the registry for the iscsi initiator. HP Command View EVA refresh The HP Command View EVA refresh interval can affect controller property field information. To ensure that you retain iscsi controller property field information in HP Command View EVA, take one of the following actions: Enter a portion of the data between page refreshes, and then click Save to store the information. Enter the rest of the data and then click Save. Change the refresh interval for the entire GUI to a larger value in Agent Options > User Interface. (The default value for the content pane is 60 seconds.) 12

13 Ordered tagged commands Ordered delivery of iscsi commands is not guaranteed for applications running on iscsi initiators that use ordered tagged commands. HP is investigating a fix for a future release of mpx100b firmware. Private iscsi network for mpx100b GbE ports To ensure adequate performance and data security, HP recommends using a private Gigabit Ethernet (GbE) network between the iscsi initiators and the mpx100b in any iscsi configuration. The iscsi technology is low cost and uses standardized network adapters and topology hardware. However, existing networks must be evaluated for their capacity to support iscsi storage. If you are not using dedicated switches, consider using separate virtual LANs (VLANs). Resolving an IP conflict on an mpx100b if the IP port does not clear the LED indication on the mpx100b When the mpx100b recognizes an IP conflict with its management ports, its fault LED blinks four times, once per second, and then off for two seconds. The following error message is displayed: checkduplicateip: Detected Error MAC address The management port is still enabled and uses its IP address. To clear the LED, turn the mpx100b beacon light off using either the mpx Manager or the CLI beacon off command. Supersedes history This version supersedes firmware version Effective date June 2010 EVA4400 iscsi Connectivity Option (mpx100b)

14 14