HP P6000 Command View Software Suite

10.1 Release Notes

HP Part Number: T5494-96476

Published: June 2012
Edition: 1
© Copyright 2012 Hewlett-Packard Development Company, L.P.
Acknowledgments

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Java® is registered trademark of Oracle and/or its affiliates.

 Version
HP P6000 Command View Software Suite 10.1

Description
This document describes the HP P6000 Command View 10.1 release for array-based management
and server-based management.

IMPORTANT: General references to HP P6000 Command View can also refer to earlier versions
of HP Command View EVA.
The information in this document is specific to the following releases of HP management software:
• HP P6000 Command View 10.1
• HP P6000 Performance Advisor 10.1
• HP P6000 Performance Data Collector 10.1 (formerly HP Command View EVAPerf)
• HP P6000 SmartStart 4.1
• Storage Management Initiative Specification for Enterprise Virtual Array (HP SMI-S EVA) 10.1
• HP Storage System Scripting Utility (SSSU) 10.1
• HP Management Integration Framework (MIF) 1.5
To determine which versions of array controller software support HP P6000 Command View 10.1,
see Table 2.0, “HP P6000 Command View interoperability support,” in the HP P6000 Enterprise
Virtual Array Compatibility Reference. For the location of this document, see “Product websites
and documentation” (page 24).
For more information about HP XCS, see the release notes for the specific XCS version.
Update recommendation
HP recommends that you upgrade to HP P6000 Command View 10.1.

Description 3
HP P6000 Command View
This section contains information about the enhancements, fixes, licenses, compatibility and
interoperability, and workarounds and limitations for HP P6000 Command View 10.1.

Enhancements
• New storage system support. Support is added for HP P6550 and HP P6350 storage systems.
• New controller software support. Support is added for XCS 11001000.

NOTE: References to XCS 11000000 in the HP P6000 Command View online help apply
to XCS 11001000.

• Management Groups aggregate view. A new page shows all storage systems, management
servers and Management Groups that have been detected by Management Integration
Framework software.
• Create multiple virtual disks. You can now create more than one virtual disk in a single action.
• Cancel physical disk firmware load. A physical disk firmware load can now be cancelled
while the load is in progress.
• Enhanced resolution of disk group hardware failures. Improved resolution of disk group
hardware failures.
• Virtual disk presentation enhancements. You can now specify the target virtual disks to be
presented to a specified host. As in previous releases, you can select a virtual disk and specify
the target hosts that the virtual disk will be presented to. In both cases, selection of multiple
targets is now supported and simplified.
• Controller events enhancements. Controller events can now be sorted, filtered and written to
a text-based log file.
• SNMPv3 support for events. Support of SNMPv3 is added to event notifications.
• iSCSI host enhancements. You can now create ISCSI or FCOE hosts by manually adding the
corresponding server IQN or WWN in HP P6000 Command View, and then present LUNs.
Later, you can update the configuration, and then discover LUNs from the server:
◦ iSCSI—Discover and login to targets from the iSCSI initiator server

◦ FCoE—Set up zoning in the FCoE switch

• CHAP (Challenge Handshake Authentication Protocol) can now be enabled or disabled for
iSCSI hosts that you add in HP P6000 Command View. You can also set CHAP secret for
presented targets and iSCSI controller IP ports. (Use firmware version 3.2.2.7 for the CHAP
settings feature to work properly.)
• Support for four virtual port groups for Mez50 iSCSI hosts. This version supports four virtual
port groups enabled in Mez50 firmware version 3.2.2.7 or later and allows you to present
up to 1,024 LUNs.
• Automatic creation of UISM log. HP P6000 Command View automatically logs UISM events
during code load. You no longer need to use HP P6000 Command View to set the EVA to
maintenance mode before loading code.
• Add a host to multiple managed arrays. You can now can add a Fibre Channel host to multiple
EVAs in one action
• ABM USGv6 certification. The EVA array-based management interface is qualified as a host
device against the USGv6 1.0 specification.
• Improved online help. Clarified application name and version and added a link to the MIF
SPoG main help page.

4
 • Kerberos authentication on Linux platforms. You can now configure an XF machine to
authenticate from a Kerberos authentication server.
• CTP 1.5 certification for EVA SMI-S provider.
• ABM (CV) Processor/Memory improvement
• AIS software enhancements
• New language support. HP P6000 Command View Software 10.0 and later is now supported
on the Windows Server 2008 R2 English base Operating System with the Multilingual User
Interface (MUI) set to the German, French, Spanish, Italian, or Portuguese Language Pack.
The new language support is in addition to English and Japanese which is currently supported
by the P6000 Command View Software. The HP P6000 Command View Software continues
to be localized to English or Japanese only.
To install and utilize HP P6000 Command View Software 10.0 on a German, French, Spanish,
Italian, or Portuguese Windows Server 2008 R2 MUI Language Pack locale, the following
requirements must be met:
◦ The management server must be a Windows Server 2008 R2 English base Operating
System.
◦ The Administrators group and Administrator user account must be created using the
English locale spelling prior to installation.
◦ Using the Control Panel→Change display language, under the Keyboards and Languages
tab, ensure the keyboard input language is set to English (United States) – US.
◦ Install the HP P6000 Command View Software Suite.
HP P6000 Command View Software with the Japanese language is supported on either a
Windows Japanese or English (with Japanese Language Pack) base Operating System. The
keyboard input language can be set to either English (United States) – US or
Japanese.

Fixes
The following issues are fixed with this version of HP P6000 Command View.
• Username now appears in audit log—HP P6000 Command View 10.0 did not list the username
in the audit log.
• Unexpected behavior after loading a blank MLD—Earlier versions of the software resulted in
management problems with mirrorclones and virtual disks unless the configuration properties
were saved before a refresh was performed.
• MLD V2 section size errors—In earlier versions of the software insufficient space was allocated
to the MLD index section, leading to errors when trying write or read a MLD section.
• Unable to store object error—In earlier versions of the software, stale entries for disk drives
in the MLD diskIdx section built up over time causing errors and preventing P6000 Command
View to add newly installed drives to the diskIdx section.
• No email event notification sent after a thin provisioning allocation capacity alarm level was
reached
• HP P6000 Command View does not display failed power supply status at a high level—In
earlier versions of the software, an EVA controller enclosure a power supply failure did not
bubble up the GUI hardware tree unless you browsed to the controller enclosure to view the
power supply status.
• HP P6000 Command View does not respond to a presented virtual disk with data lost
condition—In earlier versions of the software, users were unable to retrieve properties for a
presented virtual disk that was in a failed data lost state.
HP P6000 Command View 5
Compatibility and interoperability
IPv6 information (array-based management only)
If both IPv4 and IPv6 are installed on a single system, HP P6000 Command View starts on the IPv4
address by default. To start HP P6000 Command View on a specific address, you must add the
address entry under the webserver section of the cveva.cfg file. For example, to start HP
P6000 Command View on IPv6, enter address 0::0 under the webserver section of
cveva.cfg.

IPv6 not supported on Windows 2003 Server

Windows 2003 Server does not provide acceptable operation of HP P6000 Command View in
an IPv6 configuration. Consequently, HP P6000 Command View is not supported in IPv6
configurations on Windows 2003 Servers. IPv4 configurations continue to work reliably and are
still supported. If IPv6 is required, HP recommends installing HP P6000 Command View on Windows
2008 Server.

Clarifying HP P6000 array-based management support

HP P6000 Command View array-based management:
• Manages only one array.
• Cannot manage HP P6000 Continuous Access relationships (HP P6000 Command View can
only see one side of the DR group). High availability solutions that rely on HP P6000 Continuous
Access, such as HP Cluster Extension Software (CLX) and HP Metrocluster, cannot be managed
using HP P6000 Command View array-based management.
• Supports Insight Remote Support Standard (starting with HP Command View EVA 9.1) and
Insight Remote Support Advanced (starting with HP P6000 Command View 9.4).
• Does not support HP SMI-S EVA and HP P6000 Performance Data Collector natively. However,
both HP SMI-S EVA and HP P6000 Performance Data Collector support EVAs that are managed
by HP P6000 Command View array-based management. To do so, install the software on a
Windows server from the HP P6000 Command View installer. With the HP SMI-S EVA provider,
be sure to give the IP address and credentials of the array running HP P6000 Command View
to the provider. See the HP P6000 Command View Installation Guide for instructions.
• Supports hard disk drive firmware upgrades when running HP P6000 Command View 9.4
and XCS 10000000 or later.

Installation and upgrade requirements

For supported HP P6000 Command View upgrade paths, see Table 2.1, “HP P6000 Command
View upgrade support,” in the HP P6000 Enterprise Virtual Array Compatibility Reference.
For complete information on requirements and installation and upgrade procedures, see the HP
P6000 Command View Software Suite Installation Guide.

Browser support
Internet Explorer 8.0 or later or FireFox 4.0 or later are the supported browsers for accessing HP
P6000 software user interfaces. If you are using an earlier browser version, you must upgrade
your browser. When using HP Command View, HP Performance Advisor, or HP Management
Integration Framework, Adobe Flash Player 10 or later is required on the browser you are using.
To download the latest version of Adobe Flash Player:
1. Go to http://adobe.com and click Downloads.
2. Under Readers and Players, click Get Adobe Flash Player.
3. Click Download Now to install the Adobe Flash Player.

6
 NOTE: If you use Internet Explorer, HP recommends that you add HP P6000 Command View to
your list of trusted sites. See “HP P6000 Command View shutdown confirmation window” (page
7).

Installing HP P6000 Command View with HP Command View for Tape Libraries

IMPORTANT:
• HP P6000 Command View must be upgraded to version 10.1 before installing or upgrading
to HP Replication Solutions Manager Version 5.4 or HP Command View for Tape Libraries
Version 2.8, if all three products are installed on the same server.
• If HP Command View for Tape Libraries is installed, you must remove it before installing HP
P6000 Command View 10.1.
• HP recommends that you install HP Command View for Tape Libraries 2.8 before installing
HP P6000 Replication Solutions Manager to avoid Postgre SQL error messages.

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 accurately,
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, you must
use one of the following methods to set the system time 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.

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.

HP P6000 Command View shutdown confirmation window

If you use Internet Explorer, the HP P6000 shutdown option confirmation window can appear with
a transparent background, making it difficult to read because the information is superimposed
over the existing window. To avoid this condition, add HP P6000 Command View to your list of
trusted sites:
1. Open Internet Explorer and browse to the website you want to add as a trusted site.
2. Select Tools→Internet Options.
3. Click the Security tab.

HP P6000 Command View 7

 4. Under Select a zone to view or change security settings, click Trusted sites, and then click
Sites.
5. If the URL does not populate the Add this website to the zone box, enter
https://servername, or IP:2374, and then click Add.
6. Click Close, and then click OK.

Unable to write to log file

After a Nested group user installed HP P6000 Command View Software Suite, HP Performance
Advisor reports errors indicating an inability to write to the log file. However the events do appear
in the log file. These errors can be ignored.

Installation unsuccessful error

During an HP P6000 Command View Software Suite installation using HP P6000 SmartStart, if
the Command View installer displays a message indicating that the installation was unsuccessful
but HP P6000 SmartStart reports that the installation succeeded, reinstall HP P6000 Command
View.

Changing MEZ iSCSI controller management IP address

Changing the MEZ iSCSI controller management IP address requires a reboot of both iSCSIs
controllers to ensure proper peer communications.

NOTE: As a best practice, HP recommends that you not change the management IP address after
it is configured initially.

Virtual disk operation has failed error

A change in the iSCSI controller FC frame size can result in the following error message during a
virtual disk presentation in Mez50, Mez75, or MPX200 router:
The virtual disk operation has failed. Please make sure that FC target
connections are online.
If this occurs, use the Assign path option to select a different path for LUN presentation or return
the FC frame size to the default value of 2048.

Trace history disabled in HP P6000 Command View trace logs

In HP Command View EVA 9.2 or later on array-based management, the history of trace information
that accompanies a critical (level 1) error log in the cvevatrace*.log files is disabled by default.
To generate sufficient trace information when a critical error log is observed in the trace files,
change the configuration parameter backtrace=0 to backtrace=1 at the beginning of the file
ccbtrace.cfg. This file is located in the default HP P6000 Command View installation directory,
C:\Program Files\Hewlett-Packard\Sanworks\Element Manager for
StorageWorks HSV\. You must restart the management server
It is not necessary to restart the entire management host for this change to take effect. Restarting
the HP P6000 Command View service is all that is required.

CAUTION: Enabling trace history can adversely affect HP P6000 Command View performance.

HP Insight Remote Support Advanced software supported with HP P6000 Command View
array-based management
In addition to server-based management, HP Insight Remote Support Advanced software is supported
with array-based management. To enable array-based management support, you must set identical
credentials for both the HP P6000 Command View host (where you used discoverer.bat to
set up the connection to array-based management) and the array management module.

8
Verifying HP P6000 Command View code
HP products deliver on the “trustworthy and reliable” brand promise. Creating and delivering an
electronic cryptographic "signature" for HP code (such as software, firmware, drivers, applications,
patches, and solutions) provides an industry-standard method to verify the integrity and authenticity
of the code you receive from HP before deployment. Digitally signed code helps you manage your
security vulnerability risk from using non-HP versions of the software and firmware, which may fail
to meet expectations and may contain malicious code (like a virus or worm).
To verify the HP P6000 Command View code before installing the software, contact your HP
representative for instructions.

Emulex HBA requires latest driver version

Servers that use an Emulex HBA with Storport drivers (earlier than version 5-2.00a12) may
experience a system hang that requires a reboot, or an Array Discovery issue in HP P6000
Command View. Ensure that the Storport driver version you have is 5-2.00a12 or later. To obtain
the drivers, go to the following HP website:
http://www.hp.com/support/downloads

NOTE: For Windows 2003 systems, the new driver (5-2.00a12) requires the Microsoft hotfix
KB932755. To obtain the hotfix, go to the following Windows website:
http://support.microsoft.com/KB/932755

Windows 2003 server requires a hotfix

If the management server is running Microsoft Windows 2003, HP P6000 Command View might
not display any arrays. To resolve this issue, you must install a Microsoft hotfix. Go to the following
link for details and the hotfix download:
http://support.microsoft.com/kb/945119/
If you are using the server for storage only, not as a management server, you do not need to install
this hotfix.

Antivirus software can degrade performance

To avoid HP P6000 Command View performance issues when antivirus software is installed on
the management server, HP recommends that you exclude from the antivirus software scan the
log-related files that change frequently, including the following:
• \Program Files\Hewlett-Packard\Sanworks\Element Manager for
StorageWorks HSV\cache
• \Program Files\Hewlett-Packard\Sanworks\Element Manager for
StorageWorks HSV\log
• \Program Files\Hewlett-Packard\Sanworks\Element Manager for
StorageWorks HSV\logs
• \Program Files\Hewlett-Packard\Sanworks\Element Manager for
StorageWorks HSV\trace
• \Program Files\Hewlett-Packard\XFROOT\log
If HP P6000 Performance Data Collector is installed:
• \Program Files\Hewlett-Packard\EVA Performance Monitor\logs
• \Program Files\Hewlett-Packard\EVA Performance Monitor\cache
If HP SMI-S EVA is installed:
• \Program Files\Hewlett-Packard\SMI-S\CXWSCimom\logs
• \Program Files\Hewlett-Packard\SMI-S\EVAProvider\logs

HP P6000 Command View 9

 If HP P6000 Performance Advisor is installed:
• \Program Files\Hewlett-Packard\EVAPA\EvapaTools\tomcat\32bit\
apache-tomcat-6.0.24\logs
• \Program Files\Hewlett-Packard\EVAPA\DataBase\Postgres\data\pg_log

NOTE: If HP P6000 Command View is installed on a 64-bit machine, the top level folder is
\Program Files (x86).

Windows 2008 and LUN shrink

LUN shrink on Windows 2008 systems is supported only on basic disks and dynamic simple
volumes that are spanned or are mirrors. Striped or RAID 5 dynamic disks are not supported with
LUN shrink.

Large LUN presentation requires Windows 2003 hotfixes

The presentation of large LUNs (larger than 2 TB) requires Windows hotfixes KB949001 and
KB919117. To obtain the hotfixes, go to the following Microsoft websites:
http://support.microsoft.com/KB/949001
http://support.microsoft.com/KB/919117

Array-based management proxy displays incorrectly

In an array-based management configuration, the managed proxy displayed will be different from
that of the web access point. When a layered application uses this information, it will see different
IP addresses in Managed Proxy and Launch URL. Although the management proxy displays
incorrectly, the URL for HP P6000 Command View launches the array-based management correctly.

Cannot access HP P6000 Command View from HP Systems Insight Manager or HP P6000
Replication Solutions Manager
To log on to HP P6000 Command View directly from HP Systems Insight Manager (HP SIM) or HP
P6000 Replication Solutions Manager, a trust relationship, referred to as Single Sign-on, must be
established between the applications. When the trust relationship is broken, HP P6000 Command
View cannot be run from HP SIM or HP P6000 Replication Solutions Manager. In this case, you
must re-establish the trust relationship. See “Single Sign-on from HP Systems Insight Manager” in
the HP P6000 Command View Software Suite User Guide.

Using HP P6000 Command View for Single Sign-on with HP SIM

Launching HP P6000 Command View 10.1 or later from HP SIM opens another browser window
with a login screen for HP P6000 Command View for Single Sign-on (automatic login) and requires
that you manually login to HP P6000 Command View.

Internet Explorer 8 language code change

In Japan, Microsoft Internet Explorer 8 (IE8) installs using the Japanese language code ja_JP by
default. This is a change from earlier and current English versions, which default to ja. To use HP
P6000 Command View with IE8 as a Japanese client, you must set the browser language preference
ja. To change the language preference, select Tools→Languages→Language→Add.

Setting the Network Time Protocol server time using array-based management
When setting the Network Time Protocol (NTP) server time using array-based management, the
system time is not updated immediately. The system time should update to match the NTP server
within 10 minutes.

10
Not able to log in to HP Replication Solutions Manager server
If the Windows TEMP environment variable is not set correctly, you may not be able to log in to
the HP Replication Solutions Manager server. Ensure that the TEMP environment variable is pointing
to an existing folder and the folder is accessible.

Write cache policy not maintained when migrating a virtual disk

When migrating the Vraid type and/or disk group of a virtual disk using the Online virtual disk
migration feature, the write cache policy is set to write-back. If the virtual disk had write cache
policy set to write-through, the policy is changed to write-back.

Multi-home Agent IP does not change for SNMP traps for different VLANs
Server-based HP P6000 Command View can be installed on a multi-homed server where multiple
IP addresses are configured. The array can be accessed from any of the IP addresses of the server
through HP P6000 Command View. Consider the following when using HP P6000 Command
View on a multi-homed server:
• If the network is not accessible through an IP address on the server, the array will remain
actively managed by HP P6000 Command View on that IP address. However, it may be
necessary to use an HP P6000 Command View instance on another IP address to take
management of the array away from the inaccessible HP P6000 Command View instance.
• When SNMP traps are configured from HP P6000 Command View, the SNMP agent IP
address that generates the trap will be the same, regardless of the destination IP address to
which the trap is to be sent. The agent IP address will be the IP address from which the array
is actively managed.

Online virtual disk migration limitation

HP P6000 Command View should not be restarted or management of the array transferred while
a migration is in progress. Doing so will cause HP P6000 Command View to abandon the migration
tasks, leaving behind temporary mirrorclones that must be deleted manually. This does not impact
host I/O directed at the original virtual disk.

Changing the management IP address of an iSCSI controller using the CLI

When the management IP address of the iSCSI controller is changed using the CLI, HP P6000
Command View loses connection with the iSCSI controller, resulting in a Not Available status
displayed in the iSCSI controller GUI pages. To correct this, use the HP P6000 Command View
GUI to delete the existing iSCSI controller, and then add the new IP address using the Add iSCSI
controller page.

Using an FCoE CNA-based server with MPX200 connectivity

When managing an EVA using an FCoE Converged Network Adapter-based server and through
MPX200 connectivity, unpresenting the last FCoE LUN from the MPX200 iSCSI controller may
cause HP P6000 Command View to lose communication with the array. To resolve this issue, use
the lunmask add wizard in the MPX200 CLI to present LUN 0 from each array target WWN to
each MPX200 FCoE port and to each management server FCoE-CNA port. To gather the necessary
information, use the show fc, show targets, and show initiators MPX200 CLI commands.
Then, use the lunmask add wizard.

iSCSI or iSCSI/FCoE module configuration file indicates zero bytes

When saving the iSCSI or iSCSI/FCoE module configuration (from the iSCSI Controller Configuration
page in HP P6000 Command View), HP P6000 Command View may indicate the file size is zero
bytes. If this occurs, you must restart the controller and then save the configuration again by
performing the following steps:
1. Select the applicable iSCSI controller in the navigation pane.

HP P6000 Command View 11

 2. Select Shutdown on the iSCSI Controller Properties window.
3. Select Restart on the iSCSI Controller Shutdown Properties window.
4. After the controller has restarted, select the iSCSI controller in the navigation pane.
5. Select Set Options.
6. Select Save/Restore Configuration.
7. Select Save Configuration.
If you attempt to restore the configuration from a zero byte file, the iSCSI or iSCSI/FCoE module
configuration will not be restored and it may cause the HP P6000 Command View content page
to hang.

iSCSI/FCoE controller inaccessible from HP P6000 Command View

If an iSCSI/FCoE controller is inaccessible from HP P6000 Command View, avoid performing any
management operations on that controller and any iSCSI/FCoE objects displayed in HP P6000
Command View.

Installer displays error that user does not have administrator privileges
Ensure that you add your user name to the local Administrators group before installing version
10.0 or later, or upgrading from an earlier version; otherwise, you may receive an error message
stating that you do not have administrator privileges.

Creating disk groups with double protection level

When creating a disk group with double protection level on an array running XCS 1000000 and
later, a minimum of 10 disk drives is required on the array. If the disk group contains fewer than
10 drives and double protection is requested, only single protection level will be used.
If all the physical disks in the disk group are of the same capacity, double protection level is
achieved by reserving capacity equal to four times the capacity of a single disk. If the physical
disks in the disk group are of different capacities, double protection is achieved by reserving
capacity equal to the sum of the four highest capacity disks.

Cannot connect to HP P6000 Command View from Firefox in an IPv6 environment

When using Firefox in an IPv6 environment, the browser cannot connect to HP P6000 Command
View because the required certificate is not trusted. In this situation, you must use Internet Explorer
to save the required certificate locally and then import it manually into Firefox. Use the appropriate
procedure to import the certificate. After the certificate is imported, the browser will be able to
connect to HP P6000 Command View.
• Internet Explorer 8. Browse to https://IP Address of CV Server:2374/domain.crt,
then click the link Continue to this Website (not recommended). A window opens with options
to save the file.
• Internet Explorer 9. Browse to https://IP Address of CV Server:2374/domain.crt.
A windows opens with options to save the file.

Downgrading from HP P6000 Command View 10.0 or later

Use the following instructions when downgrading from HP P6000 Command View 10.0 or later
to 9.4, 9.3, or 9.2:
• Array-based management system—After downgrading, reset the system using the reset button.
Failing to reset the system may result in the inability to open the MIF Security GUI and the MIF
Configuration GUI after loading HP P6000 Command View 9.4.
• Server-based management system—To downgrade, perform a complete uninstall of HP P6000
Command View 10.0 and then reinstall the earlier version.

12
LDAP security domain not supported in management group consisting of array-based management
only
Adding an LDAP security domain for authentication is only supported for machines in a management
group with a server-based management machine. It is not supported for machines in a management
group consisting of array-based management only.

Array code load fails in VMware Guest OS configuration

When using HP P6000 Command View on a Windows 2008 guest system on ESX 4.1, use one
of the following methods to upgrade the firmware to ensure a successful upgrade:
• Array-based management module
• Physical server-based HP P6000 Command View
• Direct Path I/O mapping from ESX (requires supported hardware on the ESX server)

Files not removed during uninstall of HP P6000 Command View

When uninistalling HP P6000 Command View, some files may not be removed. This may occur
because the file is locked by another application or has been marked for deletion by Windows.
The presence of these files does not impact the reinstallation of HP P6000 Command View.
However, when upgrading from HP Command View 9.3 to 10.0 or later, the presence of any
locked files causes the server to reboot automatically. After reboot, you must start the installation
of HP P6000 Command View 10.0 or later manually.

Attempting to login results in missing localization file or similar message

When attempting to login to HP P6000 Command View, HP P6000 Performance Advisor, or an
HP Management Integration Framework interface, the browser displays missing localization
file (or similar error message) and does not connect to the login page.
This can indicate that the browsers proxy settings are not correct. Consider turning off the proxy
settings, or changing them as required for your environment.

Data Migration license installation

When installing a Data Migration license, a warning is displayed that can be ignored. The license
will not be listed in the license key expiration status table, but it is included on the Storage tab of
the Initialized Storage System Properties window.

Security certificate does not install in Internet Explorer when logging in to HP P6000 Command
View.
If the security certificate on the login page does not install in Internet Explorer successfully, save
the certificate to your machine. Then double-click the saved certificate to import the certificate
manually into Internet Explorer.

HP P6000 Command View 13

HP Management Integration Framework 1.5
Management Integration Framework 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 or
later does not complete successfully, all existing Command View files are removed. This includes
the MIF configuration data which is lost and must be re-created when the upgrade completes.

Clicking the arrow button does not alter the view of Management Integration
Framework Configuration
Some sections in the Management Integration Framework Configuration details page do not
expand/collapse when the arrow button is clicked.
If the General, Discovery, Security, or Tree Integrator sections do not expand or
collapse when you click the arrow button, perform the following:
1. Double-click the title of the browser window to expand the browser window to full screen.
2. Double-click the title of the browser window again to set the browser window back to the
default size.
The sections expand or collapse when the arrow buttons are pressed.

HP P6000 SmartStart 4.1

Enhancements
This release includes the ability to install Command View Software Suite components after the
initial installation. HP P6000 SmartStart now directs the install to the HP P6000 Command View
installer if HP P6000 Command View is found on the native server.
You can perform a customized installation of HP P6000 Command View Software Suite components
using the HP P6000 SmartStart Configuration Options page.
Under Management and Storage Configuration Options, select Configure HP P6000 EVA
management server using HP P6000 Command View Software.
You can then select the components you want to install.

Workarounds and limitations

Video tutorials
HP P6000 SmartStart for Windows contains video tutorials that describe HP P6000 SmartStart
concepts. The tutorials can be accessed from:
• Online help—Requires a Flash player and a 32-bit system (x86)
• GUI—Available to run on all systems

Running tutorials from online help

The tutorials are located in the HP P6000 SmartStart for Windows online help under
Contents→What’s new→Online help video tutorials.

Running tutorials from the GUI

You can view the tutorials from the HP P6000 SmartStart for Windows GUI by selecting Main
Menu→Tutorials.

14
Provisioning storage errors with Windows 2003 SP1
Windows 2003 SP1 has limited functionality for LUN provisioning. If you have issues provisioning
storage from HP P6000 SmartStart in a Fibre Channel configuration, upgrade your Windows
2003 server to SP2.
Alternately, you can provision storage directly from HP P6000 Command View and manually set
the new device as available to Windows.

Japanese virtual disk names

Virtual disk names cannot contain Japanese characters. If they do, errors occur while provisioning
storage for Fibre Channel and iSCSI application servers.

No administrator rights error for member of Administrators group

HP P6000 SmartStart reports an error indicating that although the current user is a member of the
Administrators group on the local machine, he does not have sufficient privileges to continue. For
example:
Your account does not have sufficient access to create the necessary
credentials. Please login as an administrator and try again.
This error occurs when the Microsoft User Account Control (UAC) security system seeks additional
confirmation before a task is performed. UAC can prevent unauthorized changes to your computer
by prompting you for permission when a task requires administrative rights, such as installing
software or changing settings that affect other users.
To resolve this issue:
1. Log off the system.
2. Do one of the following:
• Log in as an Administrator.
• Reset User Account Control:
1. Open User Accounts.
2. Click Turn User Account Control on or off.
3. If prompted, enter an administrator password or confirmation.
4. Select the Use User Account control (UAC) to help protect your computer box to turn
on UAC, or clear the box to turn off UAC.
5. Click OK.

IMPORTANT: HP recommends that you not turn UAC off permanently. If you do turn it off, you
must turn it back on as soon as possible.

Allow HP P6000 Command View time to gather information after a reboot

When HP P6000 SmartStart initiates a server reboot, HP P6000 Command View and HP P6000
SmartStart restart automatically. It is possible for you to advance through the HP P6000 SmartStart
application dialog boxes before all configuration information is available. Be sure to wait a minute
to allow HP P6000 Command View to gather the requisite storage array information before
proceeding. Otherwise, you might need to return to the main menu and restart HP P6000 SmartStart.

Running HP P6000 SmartStart from a network share

To run HP P6000 SmartStart from the Intranet or Internet network share, the Intranet zone security
level must be set to Full Trust. Otherwise, the operation fails and A .NET Security
Exception has occurred error message is displayed.
To change the zone security level:

HP P6000 SmartStart 4.1 15

 1. Select Control Panel→Administration Tools→Microsoft .NET 2.0 Framework Configuration to
run the .Net Framework Configuration utility (mscorcfg.msc).
A .NET configuration window opens.
NOTE:
This utility is not part of the .NET 2.0 redistributable package. It is part of the .NET Framework
Software Development Kit (SDK). You can download an SDK for your system from the Microsoft
Download Center website: http://www.microsoft.com/downloads/browse.aspx?
displaylang=en&productID=363FAD1D-FC68-461A-B459-BE5D41B521B2
2. Navigate to Console Root→.NET Framework 2.0 Configuration+Runtime Security Policy.
3. In the Tasks pane, click Adjust Zone Security.
A Security Adjustment Wizard window opens.
4. Select Make changes to this computer, and then click Next.
5. Select Local Intranet, move the trust level slider to Full Trust, and then click Next.
6. Click Finish to exit the utility.

Javascript error message

After using HP P6000 SmartStart to install HP P6000 Command View, a Javascript error message
may appear when you attempt to run HP P6000 Command View. This can occur if your browser
is not configured correctly.
To avoid these error messages, ensure that your browser is configured as described in the HP
P6000 Command View Software Suite Installation Guide.

Format prompt on Windows 2008

After creating a Windows 2008 storage volume with HP P6000 SmartStart, a popup window
appears, prompting you to format the drive associated with the storage volume.
However, HP P6000 SmartStart has already formatted the drive, therefore you can cancel this
prompt. If you choose to format the drive, the operating system will format it.

Creating a storage volume results in an error

HP P6000 SmartStart can appear to hang when creating a storage volume, and then displays the
following error:
Storage volume creation and mounting was not successful.
Reason: The storage volume you created has not been detected. (7007,
blm_storage_volume_not_found)
This error occurs when the host on which you attempted to create the storage volume cannot connect
to the array through the fabric. Other management operations succeed because they use connections
to HP P6000 Command View over Ethernet.
To resolve this situation, verify the zone configuration of the switch.

javaw.exe – Unable to locate component error

During HP P6000 Command View installation, the following error message can appear:
javaw.exe - Unable To Locate Component; This application has failed to
start because WINSPOOL.DRV was not found. Re-installing the application
may fix this problem.
This error occurs when the HP P6000 Command View installer attempts to create desktop icons
for the applications that it installed.
Because the error occurs after HP P6000 Command View installed all applications, you do not
need to reinstall the applications. To continue, click OK.

16
 If the desktop shortcuts do not appear, you can create them manually. Common executable files
and shortcuts are located as follows:

HP Storage System Scripting Utility C:\Program Files\Hewlett-Packard\Sanworks\Element Manager

for StorageWorks HSV\sssu.exe

HP P6000 Command View https://localhost:2374

HP P6000 Performance Data C:\Program Files\Hewlett-Packard\EVA Performance Monitor\

Collector evaperf.exe

Related documentation
Documentation for HP P6000 SmartStart for Windows is located on the HP P6000 Command View
SW Suite CV/SmartStart/SSSU/Docs Version 10.1 DVD. in the documentation folder.
Documentation for HP P6000 SmartStart for Linux is located on the HP P6000 SmartStart SW for
Linux CD.
You can also access all the documentation referenced in this document from the Manuals page of
the HP Business Support Center website http://www.hp.com/support/manuals. In the Storage
section, click Storage Software, and then select your product. For array-specific documents, click
Disk Storage Systems, and then select your array model.

Starting HP P6000 SmartStart for Linux

To start HP P6000 SmartStart for Linux:
1. Insert the HP P6000 SmartStart SW for Linux CD in the CD drive of the server you want to
configure.
2. Create a mount folder for the disk.
For example, mkdir /mnt/cdrom.
3. Mount the disk.
For example, mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom.
4. Change the current directory to the application directory.
For example, cd /mnt/cdrom/app.
5. Run the HP P6000 SmartStart executable script as follows: ./P6000SmartStart

SELinux prevents HP P6000 SmartStart from running on Red Hat Enterprise Server 5.3
With Red Hat Enterprise Server 5.3, you might need to disable SELinux temporarily while using
HP P6000 SmartStart. If you attempt to run HP P6000 SmartStart, and the application is unresponsive
(for 5 minutes after clicking Next, for example), SELinux may be preventing the execution of some
modules because of unsigned system libraries. Another symptom is a crash reported by SELinux
or the Red Hat Enterprise Server.
If this occurs, temporarily disable SELinux, and then run HP P6000 SmartStart. When you are
finished using HP P6000 SmartStart, you can enable SELinux.

Screen does not display result information

A task can fail to display requested information due to CD load time or a .NET load issue of XSL
file.
If a task does not display requested information, for example, a request for HBA information
displays ... Checking HBA information ..., but the HBA information does not appear,
click Cancel, and then without quitting HP P6000 SmartStart Storage, restart the task.

HP P6000 SmartStart 4.1 17

Install HBA API request
After installing the HBA API, rebooting, and starting HP P6000 SmartStart, you see an instruction
to install the HBA API. This is due to an incomplete installation of an fcinfo package.
If this occurs:
1. Insert the HP P6000 Command View SW Suite CV/SmartStart/SSSU/Docs Version 10.1
DVD.
2. Under \bin\installers\fcinfo, run the fcinfo for your architecture (note the
architecture x86, amd64, or ia64 in the filename).
3. When the installer starts, select Repair, then reboot the system.

Fibre Channel over Ethernet is not supported

This version of HP P6000 SmartStart for Linux and HP P6000/EVA support with Linux does not
support FCoE. Do not install FCoE Linux packages.
If you have issues running HP P6000 SmartStart for Linux or if HP P6000 SmartStart for Linux
crashes, ensure that no FCoE packages are installed.

P6000 SmartStart does not discover new HBA in application or management server
When a new HBA is installed in the application or management server, the driver for that HBA
may not already be installed in the operating system. Make sure to use the Proliant Support Pack
to reinstall the HBA drivers, or follow your vendor's guidelines. This is applicable for both Windows
and Linux.

P6000 SmartStart does not discover the LAN IP address of a SLES Linux host
P6000 SmartStart relies on the /etc/hosts file to discover the IP address of the Linux host. On
most installations of SLES, this file is not enabled by default.
To enable the /etc/hosts file on a SUSE Enterprise Linux 10 host:
1. Run YaST.
2. Select Network Devices.
3. Select Network Card.
4. Click Next.
5. Select NIC and click Edit.
6. Click [Hostname and Name Server].
7. Click [Accept].
8. Enable [Write Hostname to /etc/hosts].
To enable the /etc/hosts file on a SUSE Enterprise Linux 11 host:
1. Run YaST.
2. Select Network Devices.
3. Select Network Settings.
4. Select NIC and click Edit.
5. Click [Hostname/DNS].
6. Enable [Write Hostname to /etc/hosts].

Adobe Flash Player v11 required with Internet Explorer 64-bit

Attempting to launch HP P6000 Command View from the HP P6000 SmartStart page on a system
running Adobe Flash v10 and Internet Explorer 64-bit will fail with a message indicating that
Adobe Flash V11 is required with the 64-bit browser. In this situation, you should install version
11 of the Adobe Flash Player. If HP P6000 Command View is installed on the same server, the
desktop shortcut created during installation can be used to launch HP P6000 Command View
successfully.

18
 Alternatively, you can manually start the 32-bit version Internet Explorer browser. From the C:\
Program Files (x86)\Internet Explorer folder, double click on iexplore.exe to
launch the browser. Enter https://<CV server IP or hostname>:2374 in the browser
address bar to launch HP P6000 Command View.

HP P6000 Performance Advisor 10.1

Enhancements
Customize data duration window for viewing performance data. You can specify any 24 hour
period in the device history to view performance data for Key Metrics, Dashboard–Overview, Host
Port Connections and Key Performance Indicators.
• Support for XCOPY and WSAME metrics. P6000 EVA supports VMware Vsphere 5.0. HP
Performance Advisor displays XCOPY and WSAME performance metrics for EVA controllers.
• Enhanced reporting features.
◦ You can generate customized reports manually.

◦ You can generate scheduled reports and download them as needed for analysis.

◦ You can email the reports that you generate.

◦ Additional DRM performance counters are tracked.

• Load balancing view. HP Performance Advisor navigation trees now have a Load Balancing
view which allows you to ensure that your EVA is running at optimum performance. The load
distribution views help you to identify whether the I/O load across certain objects of the
storage system is balanced. This information can be used to troubleshoot array performance
issues.

Fixes
• The Refresh button in the Content pane is accessable—In earlier versions of HP P6000
Performance Advisor, the Refresh button in the Content pane became inaccessible and the
content could not be manually refreshed. You can now perform a refresh from the Content
pane.
• Storage systems display correctly —In earlier versions of HP P6000 Performance Advisor,
during an attempt to add a storage system, the controller were reported to be unknown,
resulting in the inability of HP P6000 Performance Advisor to monitor the array.

Workarounds and limitations

Restarting the HP P6000 Performance Advisor Server service
Do not restart the HP P6000 Performance Advisor Server service. Instead, stop and then start the
service, only after a confirmation that the service has completely stopped.

Aggregate live data samples not available

Aggregate or average live data samples collected across both the controllers is not available even
if one of the controllers in the storage system is inaccessible.

Performance monitoring for physical disks not supported

Performance monitoring for physical disks listed under Disk Groups→Ungrouped Disks is not
supported.

HP P6000 Performance Advisor 10.1 19

Displaying Advanced Statistics
When you click the Advanced Statistics link in the Key Performance Indicators pane under the
Dashboard→Overview tab, the statistics for the last selected view type appears under the Key
Performance Indicators tab.
Workaround: Based on the statistics that you want to view, select either Basic or Advanced from
the View list under the Key Performance Indicators tab.

Controller inaccessible when adding a storage system

When one of the controllers that you want to add is inaccessible, the Event Log displays the
following message:
Unable to add the object instances for monitoring, as the storage system
could not be monitored: Storage System Name: <name>, Storage System
WWN: <WWN>...
This indicates that the storage system cannot be added for monitoring in HP P6000 Performance
Advisor.
Workaround: Follow the steps provided in the HP P6000 EVA Command View User Guide to
ensure that both the controllers are accessible. Then, retry adding the storage system for monitoring
in HP P6000 Performance Advisor by navigating to the P6000 Monitoring tab (Settings→HP P6000
Performance Advisor Instance→Configuration) in the Content pane and clicking Add.

Live chart not shown when one controller is down

When one controller is down or inaccessible, the live chart is not shown if you choose to view live
data samples aggregated across both the controllers.

State monitoring for data replication groups leads to multiple logging of the event
Enabling state monitoring for data replication groups in HP P6000 Performance Advisor leads to
multiple logging of the event that is generated for the first data replication group undergoing the
state change.
Workaround/Solution: Manually update the state data for a data replication group whenever
required. Select the storage system under the Monitoring tab and click Update Object Status in HP
P6000 Performance Advisor.

HP P6000 Performance Data Collector 10.1

Enhancements
Support for Vstorage API for Array Integration (VAAI). P6000 EVA supports VMware Vsphere 5.0.
HP Performance data collector now displays VAAI performance counters for EVA controllers. For
XCS 10000000 and later, the following performance counters are displayed in HP Performance
Data Collectordrg command output.
• Writes in Cache: A point-in-time count of the number of outstanding per-group DRM source
host writes for which status has been returned to the host, but not yet been replicated to
destination. For this firmware provides detached_write_count.
• NAK Writes - Not Acknowledged Writes: A point-in-time count of the number host writes
per-group currently on the waiters list but not yet acknowledged back to the host. For this,
firmware provides detached_wait_count.

Workarounds and limitations

This section describes workarounds for HP P6000 Performance Data Collector 10.1.

20
HP P6000 Performance Data Collector drg command limitation
Deleting a DR group while running the HP Performance Data Collector drg –cont 2 command
can produce an unexpected result in the command output. More DR groups can be removed from
the command output that the DR group that you deleted.
For example, consider a system that has three DR groups (DR1, DR2, and DR3). If DR3 is deleted
while drg is running, DR2 or DR1 entries can also be deleted from the command output.

Domain names not supported in hostname parameter of fnh command

If the host name you specify in the fnh command is a full domain name (for example,
nt12345.asiapacific.xyzcompany.net
<mailto:xyz@asiapacific.xyzcompany.net>), the friendly names host file is not created.
Use localhost or the host name without the domain when running the fnh command. Examples
of supported entries follow:
evaperf fnh localhost hpadmin@localhost
evaperf fnh nt12345 xyz@asiapacific.xyzcompany.net

Windows Performance Monitor limitations

When using Windows Performance Monitor to view HP P6000 Performance Data Collector
performance data on a management server running Windows 2003 Enterprise Edition, Windows
Performance Monitor may hang when the number of counters exceeds 900 (for example, a virtual
disk object that exceeds 100 instances, with 9 counters per instance).

evaperf nall command fails to execute

The evaperf nall command fails to execute in continuous mode on a Windows 2008 server
in both local mode and remote mode. Use the evaperf all command instead.

hist command limitation

When used with the object type state_diskgroup, the hist command does not display data
for the EVA4400/6400/8400.

HP SMI-S EVA 10.1

HP SMI-S EVA 10.1 is shipped with the HP P6000 Command View software suite. HP SMI-S EVA
enables Common Information Model (CIM)-capable management software to manage EVA storage
systems. HP SMI-S EVA 10.1 is based on the Managed Object Format (MOF) 2.23 and is SMI-S
1.5 compliant.

NOTE: If a version of HP SMI-S EVA earlier than 8.0.x is installed, you must remove it before
installing HP SMI-S EVA 10.1.

Compatibility and interoperability

Supported main profiles and subprofiles
The HP SMI-S EVA 10.1 supports the following main profiles and subprofiles:
• Main profiles—Array and Server
• Subprofiles—Software, Masking and Mapping Subprofile, Copy Services, Block Services,
Disk Drive Lite, FC Target Ports, FC Initiator Ports, Job Control, Access Points, Physical Package,
Multiple Computer System, SAS Initiator port, thin provisioning, and Profiles Registration

HP SMI-S EVA 10.1 21

SSL certificates
For information about Secure Sockets Layer (SSL) certificates for HP P6000 Command View, see
the HP P6000 Command View Software Suite Installation Guide.

HP SMI-S EVA initial cache building may take longer with array-based management
If you are using the HP SMI-S EVA Provider with array-based management, allow several minutes
after the IP address is added to the Discoverer tool or after the HP SMI-S EVA Provider host is
rebooted, to build the cache. Applications using HP SMI-S EVA do not have access to the array
details until cache building is complete. To determine the status of cache building, use the
getarrayrefreshstatus.bat file.

Multiple array-based management systems per HP SMI-S EVA Provider

HP recommends a maximum of 12 HP P6000 Command View array-based management systems
configured for the HP SMI-S EVA Provider.

Fixes
The following issues are fixed in this version of SMI-S:
• Storage Essentials now collects physical disk performance data from EVA storage systems.
Previously, after a disk replacement, Performance Data Collector updated the CRT (Counter
Reset Time) for that disk as expected. However, the SMI-S StartStatisticTime for all disks changed
for each collection interval.
• Alert notification is now working correctly. Previously, Storage Essentials stopped receiving
event notification after an HP P6000 Command View server reboot.
• The DR group state is now displayed accurately after a normalization completes. In earlier
versions of SMI-S, after normalizing, an incorrect DR group state was reported.
• SMI-S GetArrayRefreshStatus discovers the array through the array-based management
module.

Workarounds and limitations

Data Protector backup fails with error Failed to create target volume
When performing a Data Protector backup of a snapshot created from the HP P6000 Command
View GUI, the backup may fail with the error Failed to create target volume. To avoid
this situation, after creating a snapshot using the HP P6000 Command View GUI, wait for the next
incremental SAL refresh (or force a refresh) before running a Data Protector job on the snapshot.

HP Storage System Scripting Utility 10.1

This section describes important information about HP SSSU 10.1.

Enhancement
SSSU now supports RHEL 6.1.

Fixes
This version of SSSU fixed an issue in which a move vdisk command fails if the virtual disk has
the same name as the folder.

22
Limitations and workarounds
• If you use the CODELOAD DISK command to upgrade firmware on multiple disk drives, no
error is displayed for disks configured with Vraid0.
• For HSV340/HSV360 controllers, when you enter the ADD SYSTEM or ADD DISK_GROUP
command, you must specify DISKGROUP_TYPE=enhanced. Otherwise, SSSU will return an
invalid parameter error.
Syntax example
ADD SYSTEM system_name DISKGROUP_TYPE=enhanced DEVICE_COUNT=16
SPARE_POLICY=single

Unable to write to log file

After a Nested group user installed HP P6000 Command View Software Suite, SSSU reports errors
indicating an inability to write to the log file. However the events do appear in the log file. These
errors can be ignored.

Syntax error when capturing configuration of array in DR relationship

When using HP SSSU to capture the configuration of an array that is in a DR relationship, the
resulting configuration file contains a syntax error that renders the file unusable when restoring the
configuration.
The capture configuration incorrectly captures two properties at a time for the SET DR_GROUP
command:
SET DR_GROUP "\Data Replication\DR Group 001" LINK_DOWN_AUTOSUSPEND=DISABLE
SET DR_GROUP "\Data Replication\DR Group 001" LINK_DOWN_AUTOSUSPEND=DISABLE
FULLCOPY_AUTOSUSPEND=ENABLE
Attempting a restore using a file with this syntax error will fail because HP SSSU attempts to set
two properties at a time.
After capturing the configuration, edit the SET DR_GROUP command in the configuration file as
follows:
SET DR_GROUP "\Data Replication\DR Group 001" LINK_DOWN_AUTOSUSPEND=DISABLE
SET DR_GROUP "\Data Replication\DR Group 001" FULLCOPY_AUTOSUSPEND=ENABLE
Editing the file before it is needed enables you to restore the configuration successfully, if necessary.

Running HP SSSU in OpenVMS

There are two options for running HP SSSU in OpenVMS:
• Change to the directory where HP SSSU is installed and run the application from there.
• To run HP SSSU from any directory, set an environment variable to the HP SSSU executable
file name and path. For example: Env_Var_Name :== [Path]
file_name_of_executable

HP SSSU does not create an FCoE host with HP-UX

The HP P6000 Command View GUI enables you to create an FCoE host with operating system
type as HPUX. However, HP SSSU does not support this operation.

HP SSSU might hang when using long commands on Solaris

When using long commands on Solaris, the HP SSSU process can hang. This is a result of how
Solaris handles long commands.

HP Storage System Scripting Utility 10.1 23

Accessing the HP Storage System Scripting Utility
The latest version of HP SSSU is on the HP P6000 Command View SW Suite
CV/SmartStart/SSSU/Docs Version 10.1 DVD.

Installing the HP Storage System Scripting Utility

For installation instructions, see the HP P6000 Command View Software Suite Installation Guide.

Documentation updates
The following updates apply to the HP P6000 Command View documentation:
• Page 8 of the HP P6000 Command View Software Suite Installation Guide states that:
VMDirectPath (PCI pass-through) is supported on HP P6000 Command View 9.3 or later...
and after referring to a technical note states Although this technical note indicates that the
VMDirectPath configuration is experimental, HP and VMware have an agreement that this
configuration is supported.
This last statement is incorrect. The VMDirectPath solution is no longer experimental. For
up-to-date support information, see http://kb.vmware.com/kb/1025641.
• In chapter 10 of the HP P6000 Command View User Guide, Objects and counters section,
under HP EVA virtual disk, the terms “Read Miss Data Rate” and “Write Data Rate” are used
incorrectly. The correct terms are “Read Miss MB/s” and “Write MB/s.”
• In the HP P6000 Command View online help, all references to XCS 11000000 should be
XCS 11001000.

Product websites and documentation

All documentation associated with this release is available on the Web. You can find the documents
on the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
In the Storage section, click Storage Software, and then under Storage Device Management
Software, select HP P6000 Command View Software.
Table 1 HP storage websites
Item HP website

EVA4400 http://www.hp.com/go/eva4400

EVA6400/EVA8400 http://www.hp.com/go/eva6484

EVA4000/4100 http://h18006.www1.hp.com/storage/disk_storage/eva_diskarrays/eva_arrays/index.html
EVA6000/6100
EVA8000/8100

P6300/P6500
nl
http://www.hp.com/go/p6000
P6350/P6550

HP P6000 Command http://h18006.www1.hp.com/products/storage/software/cmdvieweva/index.html

View

HP P6000 Performance http://h18006.www1.hp.com/storage/software/p6000/pas/index.html

Advisor

HP P6000 Business Copy http://h18006.www1.hp.com/products/storage/software/bizcopyeva/index.html

HP P6000 Continuous http://h18006.www1.hp.com/products/storage/software/conaccesseva/index.html

Access

HP P6000 Replication http://h18006.www1.hp.com/products/storage/software/repsolmgr/index.html

Solutions Manager

24
 An HP P6000 Performance Data Collector white paper is available from the following HP website:
http://h18006.www1.hp.com/storage/softwhitepapers.html

Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
(docsfeedback@hp.com). Include the document title and part number, version number, or the URL
when submitting your feedback.

Product websites and documentation 25