HP StorageWorks 2000fc - G2 Modular Smart Array Firmware Release Notes page 13

• Issue: Windows and Linux are limited to discovering fewer than the maximum number of LUN IDs that are
presentable from an MSA2000 G2 (512 LUNs)
• Workaround: Windows and Linux operating systems do not support enumerating all of the LUN IDs
presented from an MSA2000 G2 array. Windows supports the discovery of LUN IDs 0 - 254; Linux supports
the discovery of LUN IDs 0
To allow a single Windows or Linux host to discover more LUNs than the LUN ID limitation of 255 on
Windows and 256 on Linux, the array must be configured to present two different LUNs using the same
LUN ID. The array supports this configuration only if the LUN is presented on a subset of the host ports.
For example, present Volume Vol-001 as LUN ID 1 on ports A1 and B1 and present Volume Vol-300 as
LUN ID 1 on ports A2 and B2.
• Issue: Changing both IP addresses causes problems accessing Storage Management Utility.
• Workaround: Changing the IP address for both controllers concurrently can cause the controllers to become
unavailable. First, change the IP address on the controller that you are not logged into. Then, log in to that
controller to verify connectivity. After verifying connectivity, change the IP address on the original controller.
• Issue: Windows DiskPart utility clean command may hang.
• Workaround: When the VDS/VSS provider is loaded on a host, the clean function in DiskPart sometimes
hangs. Microsoft hotfix KB 968736 resolves this issue.
• Issue: The set network-parameters CLI command silently fails if the controller parameter is absent.
• Workaround: This parameter is not optional and must be specified to correctly set networking parameters.
The online help incorrectly states that this parameter is optional.
• Issue: Volumecopy operations can fail if a dual controller system is in a degraded state.
• Workaround: Resolve the degraded state issue.
• Issue: SunCluster using SCSI3 reservations are not supported with iSCSI and SAS environments.
• Workaround: This issue currently being investigated by HP. An alternative is to use 2 node clusters with
SCSI2 reservations in the MSA2000 G2 SAS and iSCSI protocol controllers. The Fibre Channel MSA2000
G2 has full SunCluster capabilities.
• Issue: In the SMU, recurring scheduled events may not occur.
• Workaround: Verify that the end schedule date and time are correct and later than the start schedule date
and time.
• Issue: Unable to create new schedule due to the error The schedule is expired.
• Workaround: Verify that the start time for a scheduled event is a valid time when submitting it.
• Issue: During rollback with modified data, snapshot volumes are inaccessible.
• Workaround: Plan rollback operations when access to snapshots are not required or unmount the snapshot
prior to rollback.
• Issue: After flashing firmware from the SMU, some fields may not display the updated information immedi-
ately.
• Workaround: Close all browser interfaces to the SMU after the firmware update has completed and then
re-establish the connections.
• Issue: While updating the firmware using the SMU, the browser may lose the connection.
• Workaround: Close all browser interfaces to the SMU and then re-establish the connections. If the problem
persists, restart the Management Controller from the CLI.
255. Note that SAS arrays do not support presenting a LUN on ID 0.
HP StorageWorks MSA2000 G2 Firmware Release Notes 13