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

Known issues and workarounds
The following is a cumulative list of known issues and workarounds.
• Issue: DHCP address is not being set on the array.
• Workaround: Verify that there is a valid gateway being given by the DHCP server or set a manual IP address and
gateway.
• Issue: Citrix XenServer paths do not automatically appear after reinserting a SAS cable.
• Workaround: Do the following:
1. Login to the Citrix XenServer host, dom0.
2. Change directories to /etc/udev/rules.d/.
3. Open an editing tool and open the 40-multipath.rules file.
4. Append the following line to the end of the 40-multipath.rules file:
SUBSYSTEM=="block", ACTION=="add", RUN+="/bin/bash -c 'if [[ -h /dev/disk/mpInuse/
$env{ID_SERIAL} && -b /dev/mapper/$env{ID_SERIAL} ]]; then echo add path %k |
/sbin/multipathd -k > /dev /null; fi'"
5. Save the 40-multipath.rules file.
6. Restart the host.
• Issue: The default password for the ftp user is incorrectly documented in the MSA2000 G2 documentation as !flash.
• Workaround: The correct default password for the ftp user is flash.
• Issue: When the temporary license agreement checkbox is clicked, the confirmation pop-up is displayed. If the cancel
button is clicked on the confirmation pop-up, the checkbox is not cleared.
• Workaround: To clear the checkbox, click the checkbox again to remove the check and click the cancel button on the
confirmation pop-up.
• Issue: HP MSA70 enclosure single port drives connected to the MSA2000 G2 present a single point of failure.
• Workaround: If your configuration requires full data redundancy, HP highly recommends that you do NOT connect
MSA70 2.5“ single port drives to MSA2000 G2 configurations. If there is a MSA70 controller failure in this configuration,
all data on the MSA70 single port drives is lost.
• Issue: Changes to default Fibre Channel HBA driver parameters are required for proper controller failover.
• Workaround: The Fibre Channel HBA parameters were omitted from the MSA2000 G2 documentation. For controller
failover to function properly, change the default driver parameters as follows:
◦ QLogic — Port Down Retry Count = 60, Link Down Timeout = 60
◦ Emulex — LinkTimeOut = 60, NodeTimeOut = 60
• Issue: Storage Management Utility is slow or reports success when no action was taken.
• Workaround: When there are many volumes, vdisks, and disks in a configuration, the performance of the initial load
of the SMU can be slower than expected. You can navigate the interface for any information currently loaded. The
“barber pole” above the main information pane will be moving if the data is being updated. Additionally, there have
been instances in which the front and rear graphics do not fill in completely. If you use the tabular view in this scenario,
all tasks can be completed. If the SMU reports that an illegal action succeeds (for example, extending a vdisk with a
disk which is smaller than the smallest disk in the current vdisk), the action did not actually succeed. Be sure to verify
that all actions are completed as expected.
• Issue: RHEL 5.x failback issue after controller restart.
• Workaround: If a RHEL 5.x server is processing heavy I/O it might be possible for the I/O to not failback correctly
when an array controller is restarted. To avoid this situation, HP recommends performing tasks such as replacing failed
controllers or updating firmware during periods with light I/O profiles.
14 Known issues and workarounds