HP P2000 Release Note page 16

Workaround: Delete the replication set from the source system (the system where the external view volume resides.)
Issue: On rare occasions, deleting a vdisk when volumes are in the process of rolling back may cause communications
issues between the management controller and the storage controller.
Workaround: Cycle power on the array to resolve the issue. To avoid this situation, allow the rollbacks to complete or
delete the volumes before deleting the vdisk.
Issue: Scheduled tasks are not occurring, and there is no indication of a problem in the schedules or the tasks.
Workaround: Restart both management controllers (MC) of the array(s) involved in the tasks.
Issue: Cannot schedule volume copy operations, or scheduled volume copy operations for snapshots and standard volumes
do not occur.
Workaround: Perform the volume copy manually. Scheduled volume copies of master volumes should complete successfully,
if the schedule permits completion of the volume copy before the next occurrence.
Issue: A P2000 G3 iSCSI MSA System LUN which has been newly added to a Citrix XenServer 5.6 pool may not return
to an active Storage Repository (SR) state following removal or replacement of an array controller.
Workaround: To recover to an active Storage Repository state, restart the iSCSI session by executing the following command:
/etc/init.d/open-iscsi restart
Issue: Debug logs are incomplete.
Workaround: Determine if the logs are incomplete by unzipping the log file retrieved from the array and examining the
last line of the store_YYYY_MM_DD__HH_MM_SS.logs file for the lines: End of Data ]]></LOG_CONTENT></
RESPONSE>. If the file contains these two lines at the end of the file, it is complete and you can forward it to your service
support organization for analysis. If the file does not contain these two lines at the end, it is incomplete and may not be
useful. In this case, repeat the log collection process after a 5 minute delay. Should the second collection contain the above
specified lines at the end of the file, send it to your service support organization for analysis along with the first set of logs.
However, if the second file does not contain the above specified lines at the end of the file, reboot the system and try once
more to collect the logs. Be sure to send all of the collected logs back to your service support organization with a brief note
explaining the actions you took and the result.
Issue: In a dual controller system, log in to one of the controllers fails, but log in to the other controller succeeds.
Workaround: Log in to the other controller and restart the inaccessible management controller using the CLI restart mc
command or the SMU Tools > Shut Down or Restart Controller page.
Issue: IOPs and Bytes per second may be lower or higher than expected for the workload.
Workaround: This is reporting issue and not a performance issue. The correct values can be calculated by using the change
in the Number of Reads and Number of Writes over time to determine IOPs, and the change in Data Read and Data
Written over time to determine Bytes per second.
Issue: During firmware upgrade, FTP is aborted from a Windows client after starting the upgrade.
Workaround: This is a client side FTP application issue. If this issue persists try updating from the SMU, use another client,
or use another FTP application.
Issue: Upgrading firmware failed with the error, "Unwritable cache data present".
Workaround: The controller is not in a state which can reliably perform upgrade without losing data currently in cache.
Resolve the unwritable cache issue and retry the upgrade.
Issue: While updating the array firmware via the Storage Management Utility, if the array must reboot the management
controller the web page may not automatically log the user out completely resulting in a blank page.
Workaround: Refresh the browser window; if the login page is not displayed, close the browser and restart it to access
the login page and complete the firmware update.
Issue: While performing a firmware update using the Storage Management Utility (SMU) to multiple arrays, the window
showing the status of the upgrade may appear as a blank window.
Workaround: Updating multiple arrays at the same time can cause this issue. Perform one firmware update from one client
at a time. Updating one array at a time from a client allows the window to refresh more accurately.
16 Known issues and workarounds