HP P6000 Command View 10.0 Release Notes (T5494-96528, March 2012)

Table Of Contents
MIF configuration data lost if an upgrade fails
If an upgrade from HP P6000 Command View 9.3 or 9.4 to HP P6000 Command View 10.0 does
not complete successfully, all existing Command View files will be removed. This includes the MIF
configuration data which is lost and will have to be recreated when the 10.0 upgrade is completed.
Set server to the current time before installing HP P6000 Command View
Before starting HP P6000 Command View installation, make sure the time on the server (array-based
management or server-based management) is properly set. If the system time is not set properly, the
certificate generated during installation may be invalid and you will not be able to login to HP P6000
Command View, MIF Security GUI, or the MIF Configuration GUI. If this occurs, it will be necessary
to use one of the following methods to set the system time properly and regenerate a valid certificate.
For array-based management
1. Change the time on the server from which the browser is launched to match the time on the
array-based management machine.
2. Login to the MIF Security GUI.
3. Run HP P6000 Command View and change the time on the array-based management machine
using the set time options.
4. Generate the certificate again by moving the array-based management machine to a new
management group.
For server-based management
1. Change the time on the server from which the browser is launched to match the time on the
server-based management machine.
2. Log in to the MIF Security GUI.
3. Correct the server date and time on the server-based management machine.
4. Generate the certificate again by moving the server-based management machine to a new
management group.
Custom component setup from HP P6000 Command View Software Suite limited from HP P6000
SmartStart after Command View is installed
With this release of HP P6000 SmartStart, you will use the HP P6000 Command View installer to
perform a custom installation of the software suite; however, after HP P6000 Command View has
been installed and resides on the server, HP P6000 SmartStart will no longer start the HP P6000
Command View installer, and you will not be able to perform custom installations of other applications
from HP P6000 SmartStart.
If you want to perform a custom installation of other applications in the HP P6000 Command View
Suite after HP P6000 Command View has been installed, you will need to launch the HP P6000
Command View installer directly, using the P6000SmartStart.exe pop-up window or by double
clicking bin\installers\CV\HP P6000 Command View Software Suite.exe.
NOTE: See the HP P6000 Command View Installation Guide for additional information.
Workarounds and limitations
Most of the issues described in this section have a workaround and include a resolution. Some,
however, are limitations and should be noted for reference.
P6000 disk enclosures not powering up automatically
P6000 disk enclosures should power up automatically. If this does not happen, you many need to
power them on manually. For the correct procedure on powering up the disk enclosures, see
“Documentation updates (page 27)
HP P6000 Command View 7