HP StorageWorks Enterprise Virtual Array Release Notes (XCS )

Transcription

1 HP StorageWorks Enterprise Virtual Array Release Notes (XCS ) Abstract This document applies to the HP StorageWorks 4400 Enterprise Virtual Array, HP StorageWorks 6400 Enterprise Virtual Array, and HP StorageWorks 8400 Enterprise Virtual Array. HP Part Number: Published: January 2014 Edition: First

2 Copyright 2014 Hewlett-Packard Development Company, L.P.

3 Contents Description...4 Enhancements...4 Fixes (XCS )...5 Fixes (XCS )...7 Fixes (XCS )...8 Operating systems...11 Upgrade and downgrade paths...11 HP StorageWorks SmartStart EVA Storage Kit...12 SAN support...12 Supported Fibre Channel switches...12 Supported disks...12 Performance sizing...13 Workarounds...13 Hardware and controller software...13 Data Replication Protocol changes after controller software upgrade...13 Controller logs possibly retrieved incorrectly after upgrading to XCS on the EVA EVA4400 port does not log in to the embedded switch...14 DR log progress bar percentage appears incorrect...14 Connectivity...14 Emulex 8 Gb/s HBAs require Windows hotfix...14 Emulex HBAs require unique zoning...15 QLogic HBA speed setting...15 EVA6400/8400 host port negotiates to incorrect speed...15 Creating 16 TB or greater virtual disks in Windows Importing Windows dynamic disk volumes...15 Losing a path to a dynamic disk...15 VMware configuration details for raw device mapping...15 Microsoft Windows 2003 MSCS cluster installation...16 HP MPIO EVA DSM requirement...16 Array I/O can halt after a power cycle with an HP-UX host...16 Reboot can be required after EVA power cycle to resume access to LUNs...16 Contents 3

4 Version: Description XCS This document contains information specific to the release of XCS , which applies to the following array models: HP StorageWorks 4400 Enterprise Virtual Array (EVA4400), which includes the HSV300 controller enclosure or HSV300-S controller enclosure, and the M6412 and M6412A disk enclosures HP StorageWorks 6400 Enterprise Virtual Array (EVA6400), which includes the HSV400 controllers and the M6412A disk enclosure HP StorageWorks 8400 Enterprise Virtual Array (EVA8400), which includes the HSV450 controllers and the M6412A disk enclosure The information in this document is not provided elsewhere. HP recommends that you read this information thoroughly. Update recommendation Critical Enhancements 4 XCS contains the following functionality: EVA management software support HP Command View EVA 9.1 or later (both server-based management and array-based management) is supported with XCS However, HP strongly recommends that you use HP Command View EVA The array-based management version is only supported on the EVA4400, and is installed on the management module in the controller enclosure, which reduces the need for a management server. (A management server is still required for HP Continuous Access EVA support and certain other management tasks.) Without a management server in a direct connect environment, this allows for an additional Fibre Channel port, per controller, that you can use to directly connect to a Windows, HP-UX, or Linux application server. For more information, see the HP StorageWorks Command View EVA 9.2 release notes and HP StorageWorks Command View EVA release notes. Replication software support HP Replication Solutions Manager 5.0 or later is supported with XCS HP Replication Solutions Manager is an optional interface that offers enhanced management of local and remote replication and is offered at no charge. It includes the user interface for HP Business Copy EVA and HP Continuous Access EVA. For more information, see the HP StorageWorks Replication Solutions Manager 5.1 release notes. NOTE: HP Business Copy EVA and HP Continuous Access EVA are optional replication features. You must purchase a license to use these features. See the HP StorageWorks Enterprise Virtual Array Compatibility Reference for more information about local and remote replication support. Management module software support Versions and are supported with XCS The management module applies to the EVA4400 only. HP SCSI FC Compliant Data Replication Protocol This protocol supports Fibre Channel exchange-based routing in which all frames within a given exchange use the same path, but other exchanges can use other paths. This allows for improved performance. This protocol supports fabric switches that are configured for either exchange-based routing or in-order delivery. For optimum performance, HP recommends using exchange-based routing.

5 For feature details and best practices, see the HP Continuous Access EVA Implementation Guide. NOTE: HP strongly recommends that you review these release notes and the HP StorageWorks Enterprise Virtual Array Updating Product Software Guide (XCS ) before upgrading the controller software and using this feature. VMware for HP Command View EVA support The controller software supports HP Command View EVA on a Windows guest operating system (running on a VMware server). This is supported on VMware ESX Server 3.5 and 4.0. See the HP Command View EVA Installation Guide for installation and configuration details. NOTE: When presenting EVA LUNs to a VMware server (where HP Command View EVA is installed), presentation is only supported on VMware ESX Server 3.5. Fixes (XCS ) The following issues have been fixed in XCS : Controller termination This section describes issues that can result in termination of controller operation. A single controller termination will result in a reduction of redundancy. A dual controller termination indicates a possibility of a data unavailable condition. A recursive termination will require manual intervention to address : Implemented a resource management scheme that monitors the use of volatile buffers during a heavy sequential workload or parity rebuild, which previously could result in a controller termination (termination code 0x ). This applies to the EVA4400 only , : Improved diagnostic capability to help define root cause in rare instances of the Logical Disk Capacity being set to zero (termination code 0x f) : Address an issue where diagnostic inquiry commands sent to a controller after a restart could lead to a termination, indicating Unit Stalled Too Long as the cause (termination code 0x f) : Fixed a recursive termination (termination code 0x04d3011f) that could occur during a resynchronization if a disk drive is removed while reconstruction processes are running : Fixed a recursive termination (termination code 0x04D3011f) that occurred during snapshot creation when the source virtual disk on the secondary controller : Fixed a controller termination that occurred when persistent reservation commands caused a DSI exception (termination code 0x04d3011f) : Fixed a possible recursive termination (termination code 0x f) that could occur after a controller software upgrade if the active storage system metadata volume fails / : Fixed a metadata map creation issue which could lead to a recursive termination (termination code 0x f) : Fixed a controller termination (termination code 0x070b0100) that occurred when attaching to an empty container that is part of a disk group under reconstruction : Fixed an issue which caused a controller termination (termination code 0x f) when a bad block reassign was sent to a disk drive with a failed port. Fixes (XCS ) 5

6 Disks (disk groups, virtual disks) This section describes issues affecting physical and virtual disks or disk groups, which can lead to a range of behaviors including a loss of redundancy, performance impact, or data unavailability , GR , , : Resolved an issue that resulted in a false metadata inoperative condition (Operator Control Panel message System Inoperative displayed) due to multiple missing drives , GR , : Improved diagnostic capability in rare instances of an incomplete storage cell metadata update (termination code 0x F) : Added diagnostic capability in rare instances of an unexpected metadata field change (termination code 0x ) : Added diagnostic capability to obtain more information about background redundant operations being completed prematurely or indicated as completed prematurely (termination code 0x F) : Enhanced disk group leveling to ensure all background redundant structures are equal (level) : Enhanced virtual disk expansion process to ensure allocation has completed before reporting the new capacity : Fixed an issue in which the array was declared inoperative due to a misdiagnosed metadata state : Fixed an issue during disk drive regeneration/ungrouping that could result in allocation that violates RAID selection criteria : Fixed an issue where erroneous reporting of misconfigured backend devices (event 0x031f9923) was occurring , : Addressed an issue where excessive reporting of unrecovered read medium errors from a disk drive led to a Unit Stalled Too Long event (event 0x b). Hardware (replaceable parts, device ports, resynchronization) This section describes issues affecting physical hardware, which can lead to incorrect condition handling, false condition reporting and similar events that may lead to incorrect device status reporting or replacement : Added a verification step to ensure that an accurate cache battery state is returned for HSV300 controllers to avoid falsely triggered cache policy changes : Added functionality to put cache in the Write Through state when the controller critical temperature threshold is exceeded : Fixed an issue caused by congestion within the Fibre Channel fabric, which led to controller host port freezing and lost connectivity : Fixed an issue that caused the reporting of false critical events even though the blower was operating normally : Fixed an issue which caused all disks within an enclosure to be bypassed by the midplane firmware when the enclosure was powered on. HP Continuous Access EVA This section describes issues affecting HP Continuous Access EVA implementations of remote replication, including data replication (DR) groups , , , : Resolved a recursive controller termination that could occur if, during a DR failover from one array to another, the failover array has only one active controller, resulting in cached information that is not copied to the 6

7 restarted partner controller. When the restarted controller became the master controller prior to the cached work being flushed, a recursive controller termination could occur (termination code 0x ) : Resolved a recursive controller termination that could result if a controller restart occurred during deletion of a DR group (termination code 0x f) : Enhanced the interlocking mechanism for the group online request in an HP Continuous Access EVA configuration to ensure that the group failover is allowed to occur on only one controller to prevent a controller termination (termination code 0x f) : Added a verification step to ensure that adequate space exists on the destination array prior to a LUN expansion to prevent a repeated controller termination : Fixed an issue that caused a controller termination when operations were prevented on unpresented copies (snapshots, snapclones, mirrorclones) and the parent virtual disk was a DR group member (termination code 0x04d3011f) , : Addressed an issue where an incomplete transition of a DR group between controllers led to a repeated termination : Fixed a controller termination that occurred when a snapshot was part of a DR group and there was a controller restart, resulting in the snapshot and its source being on a different controller than the DR group : Addressed an issue where an error indicator was incorrectly set in a DR group log leading to a controller termination (termination code 0x075b0104) : Fixed a controller termination that occurred when trying to delete a DR group member while the disk group is inoperative : Fixed a controller termination (termination code 0x f) that occurred during failover to the destination array during a controller software upgrade : Fixed an issue which could result in deletion of all DR group members due to an incomplete online state on the destination controller : Fixed a dual controller termination (termination code 0x ) that occurred due to multiple mastership transitions of DR groups. Operating system/solution support This section describes issues affecting EVA support of operating systems or solutions : Use of XCS with Veritas Storage Foundations and IO Fencing is now supported. Upgrades (controller software, I/O module firmware, disk drive firmware) This section describes issues affecting upgrades involving controller software, I/O module firmware, or disk drive firmware : Fixed an unexpected resynchronization between controllers, which occurred during the I/O module firmware upgrade : Fixed an issue which caused controllers to appear unresponsive after a controller software upgrade : Fixed an issue that prevented a replacement controller from downgrading the controller software version to the version running on the other controller. Fixes (XCS ) The following issue was fixed in XCS (available as a manufacturing release only) and is included in XCS : Fixes (XCS ) 7

8 HP Continuous Access EVA This section describes issues affecting HP Continuous Access EVA implementations of remote replication, including data replication (DR) groups : Fixed an issue where a DR group write history log expansion could result in performance issues, including potential data loss, in rare circumstances. Fixes (XCS ) The following issues have been fixed in XCS (available as a limited release only) and are included in XCS : Controller termination This section describes issues that can result in termination of controller operation. A single controller termination will result in a reduction of redundancy. A dual controller termination indicates a possibility of a data unavailable condition. A recursive termination will require manual intervention to address : Improperly processed SCSI commands (such as READ or Mode Sense commands) from some host applications to LUN 0 (which is designated as the Storage Array Controller Device (SACD)) on the EVA could cause controller terminations (termination code 0x04d3011f) : Improved code tracking capability to address the situation of both controllers terminating due to the host port update process. Corrected the following situations in which a controller termination could occur: , , : After the expansion of a virtual disk if a read request was sent to an unallocated space on the virtual disk before the expansion had completed (termination code 0x042011f or 0x ) : After a device port failure, causing a dual controller termination (termination code 0x a) : When a persistent LUN reservation was requested and a related metadata I/O failed as the result of a back-end issue (termination code 0x075b0100) / / : When upgrading an EVA4400 HSV300-S embedded switch controller (termination code 0x04d3011f) , , more: Due to the depletion of inter-controller resources (termination code 0x or 0x421c0101) : When a controller failover is interrupted (termination code 0x020a0104) : Due to a null pointer exception (termination code 04d3011f) : After a cache metadata corruption and cache failover does not occur when transitioning an inoperative virtual disk (termination code 0x020d0104) : After an occurrence of a TSDK ASSERT when the controller is unable to determine the link status from a back-end device during a host load (termination code 0x065a010e) : When medium errors were encountered during the processing of DR logs (termination code 0x075b0104) : Due to an interruption in the leveling of a disk group (termination code 0x f). 8

9 Disks (disk groups, virtual disks) This section describes issues affecting physical and virtual disks or disk groups, which can lead to a range of behaviors including a loss of redundancy, performance impact, or data unavailability : A data migration operation stalled after a disk drive error occurred : The one minute delay that occurred prior to a controller resynchronization (due to a RAID1 inoperative state) has been removed. Improved the storage of LUN world wide name IDs in persistent memory , , : Data and non-data exchange timeout processing has been changed to reduce erroneous Single Port on Fibre (SPOF) reporting during high workload conditions , : Improved the sequential disk leveling process : Corrected the ability to set the device ID on presented LUNs : Improved the ability to read from a mirrored pair when a data error bit is set on one of the one volumes : Changed the disk drive inquiry process to occur as soon as the disk drive is added to loop. Hardware (replaceable parts, device ports, resynchronization) This section describes issues affecting physical hardware, which can lead to incorrect condition handling, false condition reporting and similar events that may lead to incorrect device status reporting or replacement : A false Over Temperature condition could lead to a disk enclosure shutdown , : On the EVA4400, false reporting of the battery holdup time caused a change to the LUN cache policy : Excessive exchange timeouts (the cause of which has been corrected) led to device ports being disabled : Incorrectly formed Linux device mapper RAID (DM RAID) requests caused excessive server boot time due to timeouts : On the EVA8400, repeated cache battery failures due to a persistent load testing state were corrected : On the EVA4400, the time to establish mirror port communication (after a single controller resynchronization) has been improved : Corrected false failure indications on the controller's replaceable components that occurred after a controller resynchronization. HP Business Copy EVA This section describes issues affecting HP Business Copy EVA implementations of local replication, including snapshots, snapclones, and mirrorclones : Improvements were made to prevent a recursive controller termination that occurred when a mirrorclone was created and fractured in a different disk group than the source virtual disk and an inoperative condition occurred on the source : For multi-attach configurations, the timing requirements have been improved to satisfy the Microsoft Volume Snapshot Service (VSS) requirements. Fixes (XCS ) 9

10 HP Continuous Access EVA This section describes issues affecting HP Continuous Access EVA implementations of remote replication, including data replication (DR) groups : During a migration from an EVA3000/5000 running VCS 3.xxx to an EVA4400 or EVA6400/8400, a controller termination (termination code 0x f) occurred if the target EVAx4000 had existing DR groups with another EVA model communicating on the same Fibre Channel port. This problem has been corrected in this release : Addressed an issue where a heavy mirrored workload caused by DR operations led to a controller termination (termination code 0x f) : Improved preferred port settings to ensure paths are returned consistently to the desired controller in HP Continuous Access EVA configurations : In an HP Continuous Access EVA configuration, a correction was made to prevent a controller termination when commands are received out of sequence across mirror ports (termination code 0x0c0e0106) : Improved support for the creation of DR groups that have an initial log size greater than 100 GB : When setting the Failsafe on link-down/power-up feature, if the feature is supported on the source DR group but not on the destination DR group, the feature would be prevented from being used on the source DR group. The fix allows this feature to be set or cleared on the source DR group even if the destination DR group does not support it : The destination member s world wide LUN IDs were not being changed to unique world wide LUN IDs. If you recreate this DR group with the same source members, the destination members would have the same world wide LUN IDs of the existing volumes. The duplicate naming would prevent the LUNs from being presented on the destination array. Now, if you delete a DR group that still contains members, the world wide LUN IDs will be changed to new unique world wide LUN IDs : In HP Continuous Access EVA configurations, frame loss on the intersite link could result in a tunnel stuck timeout due to an error in the exchange retry code. This issue only applies to XCS or later : For an EVA controller pair running a DR consistency group, one of the destination controllers reboots, thus temporarily stopping the data mirroring relationship between the local controllers. Upon rebooting, the mirroring relationship of the controllers for the DR group is restored, but in the process, sometimes terminates with SCID_CA_BAD_PROXY_WRITE_STATE. The fix ensures that the write back cache is synchronized before writes are processed. Operating system/solution support This section describes issues affecting EVA support of operating systems or solutions : Corrected erroneous test failures that occurred during Microsoft Windows 2008 Cluster Validation Testing (CVT) : An issue of host port connectivity instability, which caused a Windows host to lose access from one path to a LUN, has been fixed. L3 GR , , : In a server-based management configuration, HP Command View EVA was unable to manage the EVA4400 because LUN 0 was not accessible (this did not affect host I/O). The fix ensures that LUN 0 remains accessible. 10

11 Upgrades (controller software, I/O module firmware, disk drive firmware) This section describes issues affecting upgrades involving controller software, I/O module firmware, or disk drive firmware , : Improved reconstruction of a disk drive that failed during a firmware download. Support for an online controller software upgrade to XCS for arrays connected to Solaris x86 and SPARC hosts is added : A correction was made so that the combination of a mirrorclone and a controller software upgrade does not cause the controller to hang : Improvements were made to the I/O module firmware upgrade process to ensure port status is reported consistently on both controllers : Corrected a timing issue so that when a disk drive had a firmware upgrade and a cache inconsistency occur simultaneously, the cache inconsistency is fixed and then the firmware upgrade occurs : After a controller software upgrade, a resynchronization for an Error Detection Code (EDC) invalid condition was falsely logged as a termination (termination code 0x f). The controller software was changed so the resynchronization does not occur for an EDC invalid condition. For information about issues fixed in previous 095xxxxx releases, see the HP StorageWorks Enterprise Virtual Array release notes (XCS ), which are available at: Select Disk Storage Systems under storage, and then select either HP StorageWorks 4400 Enterprise Virtual Array or HP StorageWorks 600/8400 Enterprise Virtual Array under EVA Disk Arrays. Operating systems For complete information about operating system specifications and supported configurations, see the Single Point of Connectivity Knowledge (SPOCK) at You must log in to access SPOCK. If you do not already have an account, select Register to log in on the main page and follow the instructions. Upgrade and downgrade paths For details about supported upgrade paths to XCS , see Table 3.1, Upgrade support for controller software versions, in the HP StorageWorks Enterprise Virtual Array Compatibility Reference. For supported downgrade paths from XCS , see Table 3.2, Downgrade support for controller software versions in the compatibility reference. For upgrade instructions, see the HP StorageWorks Enterprise Virtual Array Updating Product Software Guide (XCS ). You can download these documents from the following website: Under Storage, click Disk Storage Systems, and then select HP StorageWorks 4400 Enterprise Virtual Array or HP StorageWorks 6400/8400 Enterprise Virtual Array under EVA Disk Arrays. NOTE: A full restart of both controllers is required only one time after HP Command View EVA and the management module software is installed on the management module of the EVA4400. This is applicable when upgrading to XCS or later. Subsequent upgrades of controller software or management module software, or upgrading HP Command View EVA on the management module do not require another full restart. Operating systems 11

12 HP StorageWorks SmartStart EVA Storage Kit HP StorageWorks SmartStart EVA Storage is a CD-based wizard that you use on your Windows Server 2003 or 2008 system to install and configure HP Command View EVA. You can use HP Command View EVA to configure, manage, and monitor the HP StorageWorks Enterprise Virtual Array (EVA) storage system. NOTE: For the EVA4400, HP Command View EVA 9.2 is pre-installed on the controller enclosure management module (for array-based management). You can still use HP SmartStart EVA Storage to configure application servers. To bypass the HP SmartStart EVA Storage interface and manually run the HP Command View EVA installer, go to the \bin\installers\cv directory on the CD. HP SmartStart EVA Storage will install HP MPIO EVA DSM, which enables you to provision storage from the array; and DSM Manager, which enables you to change the default settings of HP MPIO EVA DSM. For more information about HP SmartStart EVA Storage, see the latest product release notes, which are available at: Under storage, select Storage Software. Then, select HP SmartStart for EVA Storage under Storage Device Management Software. SAN support The HSV300 controller in the EVA4400 supports 2/4 Gb Fibre Channel communication, but requires 4 Gb SFPs in the controller host ports. The HSV300-S supports up to 8 Gb communication through the embedded switch ports. The HSV400 controller in the EVA6400 and the HSV450 controller in the EVA8400 are enabled for 4 Gb/s on each Fibre Channel host path, but will also support 2 Gb/s Fibre Channel host paths and components for backward compatibility. NOTE: 1 Gb path and components have specific configuration requirements. For more information on configuration requirements and support for 2 Gb and 4 Gb EVAs, see the HP StorageWorks SAN Design Reference Guide, which can be downloaded from the following website: Click Storage Networking under Storage, and then select HP StorageWorks SAN under HP StorageWorks SAN Solutions. Supported Fibre Channel switches For complete information on which Fibre Channel switches are supported, see the Single Point of Connectivity Knowledge (SPOCK) at: You must log in to access SPOCK. If you do not already have an account, select Register to log in on the main page and follow the instructions. Supported disks For information about disk drive support, see HP StorageWorks Enterprise Virtual Array Disk Drive Firmware Support, available on the HP Manuals website: Under storage, click Disk Storage Systems, and then select the appropriate array model under EVA Disk Arrays. 12

13 Performance sizing To configure an EVA for the intended disk model(s) and host I/O workloads, please contact your HP account support representative for consulting services and instructions. For additional information on performance and solutions, see the following HP websites: Workarounds This section identifies important notes and workarounds for the EVA4400, EVA6400, and EVA8400. If you encounter difficulties with the workarounds, contact HP Services for assistance. Hardware and controller software Data Replication Protocol changes after controller software upgrade In an HP Continuous Access EVA configuration, the Data Replication Protocol may change to HP SCSI FC Compliant Data Replication Protocol when the array being upgraded to XCS : Is an EVA4400 that was initialized at a controller software version earlier than XCS Is an EVA6400 or EVA8400 that was upgraded from an EVA4400 (data in place upgrade) and was initialized at a controller software version earlier than XCS Symptoms of this issue are: Data replication stops after the upgrade. There are no visible paths to the destination array. To determine if there are visible paths, select the Data Replication folder in the HP Command View EVA navigation pane. When the Data Replication Properties Folder window opens in the content pane, select View remote connections. To resolve this issue, you must set the protocol to HP FC Data Replication Protocol in HP Command View EVA as follows: 1. Select the upgraded array in the EVA Storage Network Properties window. 2. Select the Data Replication folder in the navigation pane. The Data Replication Properties Folder window opens in the content pane. 3. Select Data Replication Options. The Data Replication Options window opens. 4. Select Set Data Replication Protocol. The Data Replication Protocol options window opens. 5. Select HP FC Data Replication Protocol. 6. Select Save Changes. Controller logs possibly retrieved incorrectly after upgrading to XCS on the EVA4400 After upgrading the EVA4400 to XCS , HP Command View EVA might not retrieve the controller logs correctly. This occurs if the controller event log sequence number is reset to zero during the upgrade. When the controller logs are not being retrieved, controller log-related entries will not be sent to the Windows application event log nor will the related WEBES callouts and SNMP traps be sent. To determine if this issue has occurred after the upgrade, access the HP Command View EVA GUI and select View events > Controller Event Log. Compare the most recent value in the Sequence # box in the GUI to the values in the \Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\cache\[EVA WWN]\[EVA Performance sizing 13

14 WWN].sceventstatefile.txt. The [EVA WWN].sceventstatefile.txt file stores the last sequence number retrieved from the controller event log in the second value. NOTE: [EVA WWN] is the worldwide name of the EVA storage system being managed. If the second value in the [EVA WWN].sceventstatefile.txt file is larger then the value shown in the GUI, apply the following workaround: NOTE: This workaround is not applicable for array-based management environments. Contact HP Services for assistance. 1. Stop the HP Command View EVA service. 2. Rename the \Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\cache\[EVA WWN] directory to...\[eva WWN]_OLD. 3. Start the HP Command View EVA service. HP Command View EVA will retrieve the controller log events that have occurred since the controller software upgrade. If the controller log events from prior to the upgrade are needed, you must retrieve them from the previous...\[eva WWN]_OLD directory. After applying the workaround, for those controller log-related events that have not been retrieved prior to the workaround, WEBES callouts and SNMP traps may be sent if the configured rules apply. Allow this to occur so you can be notified of any important events. For events older than one week, WEBES will roll all the related events into one callout. EVA4400 port does not log in to the embedded switch It has been observed that an EVA4400 host port will occasionally not log in to the embedded switch. If you encounter this issue, restart the controller to bring the port online. DR log progress bar percentage appears incorrect Connectivity Because the DR log can suddenly reach the full copy threshold, the percentage complete displayed by HP Command View EVA can appear to be inaccurate. This is caused by overhead (or metadata) that is applied to the file and is included in the percent complete, which reduces the amount of capacity available. This overhead is more significant for smaller log files than larger log files because some of the overhead is constant in size. For example, a 5 GB minimum log size can contain 35 percent overhead, while a 40 GB log file might only contain 10 percent overhead. This could cause the progress bar in HP Command View EVA to show a larger amount of progress than one would expect for the allocated log size. This section describes workarounds for HBA, switch, and operating system connectivity. For the latest support information about connectivity, see the Single Point of Connectivity Knowledge (SPOCK) at If you do not already have an account, select Register to log in on the main page and follow the instructions. Emulex 8 Gb/s HBAs require Windows hotfix If the management server is running Microsoft Windows 2003 and has Emulex 8 Gb/s HBAs (HP part numbers AJ762A and AJ763A) installed, HP Command View EVA may not display any arrays. To resolve this issue, you must install a Microsoft hotfix. Go to the following link for details and the hotfix download: If you are using the server for storage only, not as a management server, you do not need to install this hotfix. 14

15 Emulex HBAs require unique zoning When multiple Emulex HBAs are connected to the same EVA4400, each HBA requires unique zoning. QLogic HBA speed setting In a Linux direct connect environment with QLogic 4 Gb/s HBAs, auto speed negotiation is not supported. The QLogic HBA speed setting must be set to 4 Gb/s. EVA6400/8400 host port negotiates to incorrect speed The EVA6400/8400 might not correctly negotiate to 4 Gb/s when connected to an HP M-Series 4400, 4700, or 6140 switch with ports set to autonegotiate. The workaround is to set the switch port to 4 Gb/s. Creating 16 TB or greater virtual disks in Windows 2008 When creating a virtual disk that is 16 TB or greater in Windows 2008, ensure that the Allocation unit size field is set to something other than Default in the Windows New Simple Volume wizard. The recommended setting is 16K. If this field is set to Default, you will receive the following error message: The format operation did not complete because the cluster count is higher than expected. Importing Windows dynamic disk volumes If you create a snapshot, snapclone, or mirrorclone with a Windows 2003 RAID-spanned dynamic volume on the source virtual disk, and then try to import the copy to a Windows 2003 x64 (64-bit) system, it will import with Dynamic Foreign status. The following message displays in the DiskPart utility: The disk management services could not complete the operation. This error occurs because the 64-bit version of DiskPart fails to import dynamic RAID sets on a new server. To avoid this issue, use the 32-bit version of DiskPart instead of the 64-bit version. Copy DiskPart from a 32-bit x86 Windows system, located in C:\WINDOWS\system32. Place the DiskPart utility in a temporary folder on the 64-bit x64 Windows system. Losing a path to a dynamic disk If you are using Windows 2003 with dynamic disks and a path to the EVA virtual disk is temporarily lost, the Logical Disk Manager (LDM) will erroneously show a failed dynamic volume. For more information, see the following issue on the Microsoft knowledge base website: To resolve the issue, reboot the Windows 2003 server to restore the dynamic volume. VMware configuration details for raw device mapping Raw Device Mapping is not supported with Windows 2003 Virtual Machine Guest Operating System on versions earlier than ESX To avoid issues with RDM LUNs, complete the following changes for the applicable ESX version. For VMware ESX or Using the Virtual Infrastructure Client console, complete the following steps: 1. From the Configuration Tab, select Advanced Settings > Disk. 2. Add HSV3: HSV4 to the following setting: HSV1:HSV2:DGC:MSA_VOLUME:HSV3:HSV4 3. Click OK to apply the changes. Workarounds 15

16 For VMware ESX or (EVA4400 only) Using the ESX server console, add HSV3 to the following setting: echo "HSV1:HSV2:DGC:MSA_VOLUME:HSV3" > /proc/vmware/config/disk/sandeviceswithnonconstantsninpa Microsoft Windows 2003 MSCS cluster installation The MSCS cluster installation wizard on Windows 2003 can fail to find the shared quorum device and disk resources might not be auto-created by the cluster setup wizard. This is a known Windows Cluster Setup issue that has existed since Windows 2003 was released. There are two possible workarounds for this problem: Follow the workaround recommendation described in the Microsoft support article entitled Shared disks are missing or are marked as "Failed" when you create a server cluster in Windows Server 2003 (ID ), available for download on the Microsoft website: Use the MPIO DSM CLI to set the load balancing policy for each LUN to NLB. Microsoft is currently working on a resolution to address this issue. HP MPIO EVA DSM requirement HP recommends that you always install the latest version of HP MPIO EVA DSM. If you use HP SmartStart EVA Storage to install HP Command View EVA on your Windows 2003 or Windows 2008 management server, HP MPIO EVA DSM version and DSM Manager are installed automatically. You can always download the latest DSM Manager and HP MPIO EVA DSM from HP's website: 1. Under Storage, select Storage Software. 2. Under Storage Infrastructure Software, select Other Multi-Path Software-Windows. 3. Select Windows MPIO DSM for EVA. 4. Select the appropriate Windows operating system. 5. Do one of the following: For MPIO DSM, select HP MPIO Full Featured DSM for EVA4x00/6x00/8x00 and EVA4400 families of Disk Arrays. For DSM Manager, select HP MPIO DSM (Device Specific Module) Manager for Full Featured DSMs. See the release notes included with the download file for more information. Array I/O can halt after a power cycle with an HP-UX host I/O halts after power cycling an HSV300-S enclosure connected to an HP-UX host with HP-UX driver versions earlier than B To resolve this issue, either upgrade to version B , or reset the HBAs on any server affected after an HSV300-S is power cycled. Reboot can be required after EVA power cycle to resume access to LUNs If an EVA4400 experiences a power cycle while the management GUI for Windows MPIO DSM is open, the LUNs might not appear under Disk Management after they recover. This issue is seen when the MPIO DSM Manager snap-in is open at the time of a power cycle. To reduce the probability of this occurring, HP recommends that you close the GUI when you are not performing management actions. If this problem occurs, follow these steps: 1. Close the HP MPIO DSM Manager GUI. 16

17 2. Close Disk Management. 3. Stop and restart the Virtual Disk services. 4. Open Disk Management, and then rescan or Diskpart rescan to enumerate the LUNs. If these steps are not successful, reboot the server. Workarounds 17