HP StorageWorks 2000fc HP StorageWorks MSA2000 G2 Firmware Release Notes (5088 - Page 12

Integrity Server ia64 Windows BFS must use Smart Setup 6.2 or later., Issue, Workaround

Get HP StorageWorks 2000fc - G2 Modular Smart Array PDF manuals and user guides View all HP StorageWorks 2000fc manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

• Issue: VMWare reports a retry (unit attn) in the log. • Workaround: VMWare reports a retry (unit attn) whether I/O is running or not. This issue does not affect data integrity, is being investigated, and is expected to be corrected in a future firmware update. • Issue: Disk channel errors reported by drives on an MSA70. • Workaround: When an MSA2000 G2 array is using MSA70s as expansion JBODs, disk channel errors might be reported. These errors do not affect data integrity and are being investigated for correction in a future update. • Issue: Inconsistent or unexpected behavior when the system is exposed to more than 64 host ports. • Workaround: When an MSA2000 G2 array is exposed to more than 64 hosts, the first discovered host on the list is removed without warning. This host can be added back in manually. There are a maximum of 64 hosts allowed in the host list at any time. You can also use fibre channel zoning to limit the number of exposed host ports to 64 or fewer. • Issue: In larger configurations the Windows DSM can have a slow failback time. • Workaround: Under very heavy load or large configurations the DSM can take many minutes to failback returning paths. This issue is being investigated by Microsoft for enhancement. • Issue: HP-UX possible path loss. • Workaround: Under very heavy load a path might unexpectedly disappear from the operating system. This is being investigated and will be mitigated in a future release. To avoid this situation, configure multiple paths to all volumes when possible. • Issue: Windows operating system performance can be negatively impacted if the recommended array configuration is not followed for BFS configurations. • Workaround: When designing a Windows BFS configuration, it is a best practice to have the operating system partitions on a separate vdisk than the data partitions. This helps spread the load to different disks and allows faster access to both data and operating system partitions concurrently. • Issue: Windows Clusters with Emulex HBAs have cluster failover issues. • Workaround: On Windows clusters with Emulex HBAs there have been instances in which a cluster resource was not moved to another node when an array controller was shut down. This issue is being investigated by all vendors involved and a resolution will be available as soon as possible. Qlogic cards have not exhibited this issue. Path loss does not trigger this issue. • Issue: Integrity Server ia64 Windows BFS must use Smart Setup 6.2 or later. • Workaround: Integrity BFS for Windows ia64 will install but then will not find the boot LUN on a reboot. To correct this issue, use Smart Setup 6.2. If this is not available from the support Web site, a call to customer support is required. • Issue: Command Line Interface cannot display locale-specific output correctly. • Workaround: Ensure that the telnet client is UTF8-compliant in order to display non-English character sets correctly. • Issue: Unable to set UDID on SCC device at LUN 0 on Open VMS. • Workaround: It is currently not possible to set the UDID on an SCC device at LUN 0. This is different than other HP products and is not currently supported. Avoid this issue by not using a LUN 0 for Open VMS. 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
•
Issue:
VMWare reports a retry (unit attn) in the log.
•
Workaround:
VMWare reports a retry (unit attn) whether I/O is running or not. This issue does not affect
data integrity, is being investigated, and is expected to be corrected in a future firmware update.
•
Issue:
Disk channel errors reported by drives on an MSA70.
•
Workaround:
When an MSA2000 G2 array is using MSA70s as expansion JBODs, disk channel errors
might be reported. These errors do not affect data integrity and are being investigated for correction in a
future update.
•
Issue:
Inconsistent or unexpected behavior when the system is exposed to more than 64 host ports.
•
Workaround:
When an MSA2000 G2 array is exposed to more than 64 hosts, the first discovered host
on the list is removed without warning. This host can be added back in manually. There are a maximum
of 64 hosts allowed in the host list at any time. You can also use fibre channel zoning to limit the number
of exposed host ports to 64 or fewer.
•
Issue:
In larger configurations the Windows DSM can have a slow failback time.
•
Workaround:
Under very heavy load or large configurations the DSM can take many minutes to failback
returning paths. This issue is being investigated by Microsoft for enhancement.
•
Issue:
HP-UX possible path loss.
•
Workaround:
Under very heavy load a path might unexpectedly disappear from the operating system.
This is being investigated and will be mitigated in a future release. To avoid this situation, configure multiple
paths to all volumes when possible.
•
Issue:
Windows operating system performance can be negatively impacted if the recommended array
configuration is not followed for BFS configurations.
•
Workaround:
When designing a Windows BFS configuration, it is a best practice to have the operating
system partitions on a separate vdisk than the data partitions. This helps spread the load to different disks
and allows faster access to both data and operating system partitions concurrently.
•
Issue:
Windows Clusters with Emulex HBAs have cluster failover issues.
•
Workaround:
On Windows clusters with Emulex HBAs there have been instances in which a cluster resource
was not moved to another node when an array controller was shut down. This issue is being investigated
by all vendors involved and a resolution will be available as soon as possible. Qlogic cards have not ex-
hibited this issue. Path loss does not trigger this issue.
•
Issue:
Integrity Server ia64 Windows BFS must use Smart Setup 6.2 or later.
•
Workaround:
Integrity BFS for Windows ia64 will install but then will not find the boot LUN on a reboot.
To correct this issue, use Smart Setup 6.2. If this is not available from the support Web site, a call to cus-
tomer support is required.
•
Issue:
Command Line Interface cannot display locale-specific output correctly.
•
Workaround:
Ensure that the telnet client is UTF8
–
compliant in order to display non-English character sets
correctly.
•
Issue:
Unable to set UDID on SCC device at LUN 0 on Open VMS.
•
Workaround:
It is currently not possible to set the UDID on an SCC device at LUN 0. This is different than
other HP products and is not currently supported. Avoid this issue by not using a LUN 0 for Open VMS.
12