HP 2000 G2 Modular Smart Array Controller Firmware M113R10 Release Notes (508849-014, February 2012)

• Issue: The Storage Management Utility Restore System Defaults function is not available.
• Workaround: The Restore System Defaults function is listed in the User Guide as an available feature. This function has
been removed from the SMU and is only available as an advanced option in the Command Line Interface (CLI).
• Issue: Linux Boot from Storage (BFS) configurations can become unresponsive on a controller failure due to incorrect
multipathing setup.
• Workaround: When configuring a Linux BFS setup, be sure to explicitly follow the documentation for the Linux release
and Device Mapper. The configuration should be tested for path and controller failure prior to being placed in a
production environment. A functioning operating system while all controllers/paths are up is not indicative of a fully
functional multipathed operating system drive.
• Issue: I/O timeouts reported by HP-UX 11.23 and PVLinks.
• Workaround: On HP-UX 11.23 with PVLinks, the operating system might report many I/O timeouts under heavy load.
These do not affect data integrity. The issue is being investigated.
• 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: 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.
Known issues and workarounds 15