HP StorageWorks P2000 G3 FC and FC/iSCSI MSA Controller Firmware Release Notes (631269-005, February 2011)

Issue: A replication set was deleted, but is later shown with the primary volume status of “Offline” and the
status-reason is record-missing.
Workaround: This generally occurs when the secondary volume is detached and its vdisk stopped when the
replication set was deleted, and then the vdisk of the secondary volume restarted. To correct this issue, reattach
the secondary volume, set it as the primary volume, and delete the replication set.
Issue: Attempting to delete a replication set returns the error message: “The volume was not found on this
system.”
Workaround: This may occur when deleting a replication set is attempted before the information for the volumes
that constitute the set has been retrieved. Wait for the information to be retrieved and try the operation again.
Issue: While setting up a replication set involving two systems, there is a possibility that the CLI and SMU will
not respond.
Workaround: This condition will clear itself after 15 minutes. You should still have access to the system via the
other management controller. When this situation occurs, a partial replication set may be created, where only
the primary volume is included. To correct this situation, remove the replication set and any secondary volumes
created, and retry the operation.
Issue: An error message indicating “controller busy” occurs while creating a replication set.
Workaround: Creating a replication set immediately following another replication set creation may result in
"Controller Busy". This is expected behavior. Wait and try the operation again at a later time.
Issue: In the SMU, the Vdisk > Provisioning > Create Multiple Snapshots task allows a secondary volume to
be selected, but fails the operation.
Workaround: User initiated snapshots are not allowed on secondary volumes. Do not select a secondary
volume.
Issue: A scheduled replication is missing or replications are queued, but don’t complete.
Workaround: A best practice is to schedule no more than four volumes to start replicating at the same time
and for those replications to recur no less than 30 minutes apart. If you schedule more replications to start at
the same time or schedule replications to start more frequently, some scheduled replications may not have
time to complete.
Issue: Unable to perform a local replication (a replication where the external view volume and the destination
volume reside on the same system) with a single vdisk.
Workaround: Create a second vdisk for the destination volume.
Issue: Deleting the replication-set from the destination system fails.
Workaround: Delete the replication set from the source system (the system where the external view volume
resides.)
Issue: A replication set is missing the external view volume, and the replication set cannot be deleted.
Workaround: Set the external view volume to the remaining volume in the set. You should then be able to
delete the replication set.
Issue: A flurry of old events from the array are sent via email or SNMP, even though they have previously
been sent.
Workaround: Check the events on the system to determine if any action is necessary. The flurry itself is innocuous
and can safely be ignored. If this continues, consider clearing the events on the array, which would alleviate
the number of events sent.
Issue: Logging into the CLI with the credentials of a user other than a built-in user (that is, a user that has been
added to the array), generates the error message: login: can't chdir to home directory ''
Workaround: Logout, wait a few seconds, and try again. If this continues, login as the manage user, restart
the MC, and try again as the added user.
18