HP StorageWorks 2000i HP StorageWorks MSA2000 G2 Firmware Release Notes (50884 - Page 11

• 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. • 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: Controller might need to be manually restarted after a firmware update. • Workaround: During a firmware update, the controller will sometimes need to be manually restarted. • 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. HP StorageWorks MSA2000 G2 Firmware Release Notes 11