HP StorageWorks Command View XP
							
                        Version 2.2B

                        January 2006

                   Part Number: B9357-96162
_____________________________________________________________


Contents
--------
1.  Overview
2.  Firmware Requirements
3.  New Features
4.  Defect Fixes and Enhancements
5.  Known Issues and Workarounds
6.  Command View XP Documentation
7.  Appendix



_____________________________________________________________

Chapter 1 : Overview
--------------------

HP StorageWorks Command View XP is a Web-based storage 
management platform that monitors and configures the HP 
StorageWorks XP Disk Array family of products. You can access 
Command View from remote locations using the Internet and a 
Web browser.

Firmware requirements are addressed in chapter 2.0 and new 
features are described in chapter 3.0. Defect fixes and 
ehancements are summarized in 4.0. Chapter 5.0 discusses 
known issues and workarounds, section 6.0 provides a list of 
documentation available for Command View. Section 7.0 is an 
appendix, providing corrected error messages received in the 
user partition windows in the Command View framework.

Unless otherwise noted in this readme, all new features are 
documented in the installation and user guides, which are 
provided on the Command View XP CD.


_____________________________________________________________

Chapter 2: Firmware Requirements
--------------------------------

Command View 2.2B requires that the managed disk arrays have
certain minimum firmware levels.

 o  For XP10000: Firmware version 50.04.31.00/00 is required. 
    (Firmware 50.04.41.00/00 or later is recommended.)

 o  For XP12000: Firmware version 50.04.31.00/00 is the 
    minimum required. (Firmware 50.04.41.00/00 or later is 
    recommended.)

 o  For XP1024/XP128: Firmware version 21.13.02-00/00 is the 
    minimum required. (Firmware 21.14.10.00/00 or later is 
    recommended.)

 o  For XP512/XP48: Firmware version 01.19.86.00/00 is 
    required. (Firmware version 01.19.91.00/00 or later is 
    recommended.)

 o  When using the MSA1000/1500 for Flex Copy on XP128 or 
    XP1024, use MSA1000 firmware version 4.32.

 o  When using the MSA1000/1500 for external storage or Flex 
    Copy XP on XP10000/12000, use MSA1000/1500 firmware 
    version 4.32.

		
_____________________________________________________________

Chapter 3: New Features
-----------------------

This section describes the new features in this release of 
Command View XP.

3.1 4 Gigabyte Fiber Channel Display 
------------------------------------
The Command View 2.2B Command Line Interface now displays 4GB 
Fiber Channel adapter information.


3.2 Parity Group Concatenation
------------------------------
The Command View modules, Command Line Interface & Path 
Connectivity, now display concatenated parity group related 
information. However, configuration of parity group 
concatenation can only be done through the SVP.


_____________________________________________________________

Chapter 4: Defect Fixes and Enhancements
----------------------------------------

This version of Command View fixes the following defects: 


4.1 Unable create host_group through Command View CLI when 
    LCP port is installed (XP128/XP1024/XP12000/XP10000)
----------------------------------------------------------
When trying to create host_group through the Command View 
Command Line Interface, the operation failed with the error 
message, “set operation failed, CL2-B: either the port 
security is not enabled or the number of host groups exceed 
maximum.”


4.2 Trap MIB definition files
-----------------------------
Trap MIB definition file for XP1024, XP128, XP10000 and 
XP12000 disk arrays have been created and is available 
through the “trap_integration.zip” in the Command View 
Support page.


4.3 HpssCVSubAgent service disabled by default
----------------------------------------------
The HpssCVSubAgent service has been disabled by default and   
can be enabled if required. 


4.4 Snapshot volume support in Path Connectivity
------------------------------------------------
LUNs of an array that were mapped to snapshot volumes, were 
not distinguished and its details were not displayed by Path 
Connectivity screens. 


4.5 WWN nickname allows only 8 when modifing 
--------------------------------------------
When modifying a WWN nickname the modified nickname could 
only be of 8 characters.


4.6 SVP reboot failure 
---------------------- 
The SVP reboot fails due to active CV connections. 

Workaround: 
To create the schedule, complete the following the steps: 
    1. Go to the CV installation DIR. 
       For example: C:\HPSS 
    2. Go to hpss\dm\tomcat\conf 
    3. Modify 'stop_time' and 'start_time' parameters in the 
       confile "scheduler.conf" according to the  
       scheduled SVP reboot time. 
    4. Run hpss\dm\tomcat\bin\schedule.bat file. 
    5. Restart the management server system. 

To modify the schedule, complete the following the steps: 
    1. Go to the CV installation DIR. 
       For example: C:\HPSS 
    2. Go to hpss\dm\tomcat\conf 
    3. Modify 'stop_time' and 'start_time' parameters in the 
       confile "scheduler.conf" according to the modified 
       scheduled SVP reboot time. 
    4. Run hpss\dm\tomcat\bin\modify_schedule.bat file. 
    
    
To delete the scheduled tasks, complete the following steps: 
    1. Go to the CV installation DIR. 
       For example: C:\HPSS\dm\tomcat\bin 
    2. Run delete_tasks.bat 

CAUTION: 
SVP reboot can fail even after installing this fix, in case: 
    o  SVP is in the modify mode 
    o  a user logs into Webconsole during the svp reboot time
    o  a floppy disk is inserted in the floppy drive



_____________________________________________________________ 

Chapter 5 :  Known Issues and Workarounds
-----------------------------------------

The issues addressed in this section are known to exist for 
Command View XP 2.2B.


5.1  General Limitations
------------------------
The following limitations exist for this release:

  o A dedicated management station is required
  o Coexistence with Performance Advisor 2.2 is supported;
    Versions of Performance Advisor older than 2.2 are NOT 
    supported
  o IP security feature removed from Command View CLI for
    XP128/XP1024/XP10000/XP12000
  o Device Administration CLI commands removed

The following is NOT supported:

  o Command View XP 2.0 or later for the XP256
  o AutoLUN support for the XP48/XP512
  o Host agent, CLI, or online help support for mainframe 
    systems
  o Netscape browsers on Microsoft Windows platforms
  o Windows NT management server
  o Auto LUN is supported with Business Copy XP on any XP
    disk array


5.2  Special FW Requirements for Command View 2.2B
--------------------------------------------------
Do NOT upgrade to Command View 2.2B on the Command View 
management station managing XP128/XP1024 arrays if you do not 
want to upgrade the firmware for these arrays.

The firmware version prior to 21.10.09 for XP128/XP1024 will 
only work with Command View 1.8B. If you want to manage an 
XP10000/XP12000 and still retain firmware versions prior to 
21.10.09 for your XP128/XP1024 arrays, you will need a 
separate Command View management station with Command View 
2.2B to manage the XP10000/XP12000.


5.3  Windows Server 2003 with Command View 2.2B
-----------------------------------------------
If you are using Windows Server 2003, you must perform the 
following operation in Internet Explorer before using Command 
View for the first time:

1. In Internet Explorer, select Tool > Internet Options. The 
   Internet Options dialog box is displayed.
2. Select the Advanced tab.
3. Clear the Do not save encrypted pages to disk check box.
4. Select OK to close the Internet Options dialog box.

Additionally, ensure that the "IIS Admin Service" is 
disabled.

1. Select Start > Settings > Control Panel > Administrative 
   Tools > Services.
2. Right-click "IIS Admin Service" and select "Properties".
3. Set the 'Startup Type' to "Disabled".
4. Click OK.


5.4  Installation of Command View 2.2B
--------------------------------------
All previous versions of Command View, with the exception of 
Command View 2.x, must be removed before installing Command 
View 2.2B. If the "IIS Admin Service" is available on the 
system, ensure that it is disabled. To do so, use the 
instructions given in section "5.3  Windows Server 2003 with 
Command View 2.2B".


5.5  Command View Web Client Session Times Out
----------------------------------------------
If the Command View framework session times out, attempts to 
log in again using the same browser will fail. Close the 
browser where Command View was running and restart Command 
View in a new browser.


5.6  Command View Management Station Software Does Not 
     Support Running on a Multiprocessor System
------------------------------------------------------
Command View management station software should run on a 
single-processor system. Running the Command View management 
server software on a multi-processor system is not formally 
supported. 


5.7  HP-UX Mozilla Web Client Support
-------------------------------------
Supported HP-UX Mozilla web clients include:

o For HP-UX 11.00, use Mozilla 1.7.3.02 with JRE/JPI 1.4.2.08
o For HP-UX 11.11, use Mozilla 1.7.3.02 with JRE/JPI 1.4.2.08
o For HP-UX 11.23, use Mozilla 1.7.3.02 with JRE/JPI 1.4.2.08
o For HP-UX 11.23 PI (HP-UX 11iv2 for PA-RISC and HP-UX 11iv2 
      for 1A-64), use Mozilla 1.7.3.02, JRE 1.4.2.08.


5.8  "hp StorageWorks command view xp" Shortcut
-----------------------------------------------
When Command View 1.8x is uninstalled, the shortcut "hp 
StorageWorks command view xp" remains on the management 
station's Start > Programs menu. When you install Command 
View 2.2B, a new shortcut, titled "HP StorageWorks", is 
added. Manually delete the old shortcut in the menu by 
right-clicking on the "hp StorageWorks command view xp" 
shortcut and selecting Delete; and use the new link 
titled "HP StorageWorks" to access the Command View 2.2B.


5.9  Session Timeout Values
---------------------------
User-defined changes to session timeout values, as described 
in the installation guide, will be ignored if the timeout is 
set to 10 minutes or less. If set in that range, CV will use 
the default of 60 minutes for session timeout. Make sure you 
set session timeout values to more than 10 minutes.

When the Command View browser session has timed out, you will 
need to close the browser and log in on a new browser 
session.

If Performance Advisor 2.0 is invoked from the Command View 
Web GUI and the Command View Web session times out, you must 
close all opened Performance Advisor browser sessions and 
Command View sessions and invoke a new browser session to log 
on to Command View again.


5.10  Adding Arrays to Command View with Device Panel
-----------------------------------------------------
Command View 2.2B will allow XP128 or XP1024 arrays running 
firmware version 21.10.08 to be added using the Device Admin 
panel, however those configurations are not supported. CV 1.X 
must be used to manage arrays with FW versions 21.10.08 and 
lower.

Workaround:
Confirm supported firmware version (see 2.0 Firmware 
Requirements for supported firmware version) before adding an 
array to Command View.


5.11  Viewing Online Help on HP-UX
----------------------------------
The Command View online help may not load properly on HP-UX 
operating systems using Netscape. If this occurs, reload the 
frame by right-clicking the grayed frame on the left hand 
side and clicking Reload Frame.


5.12  Multiple LAN Card Limitation
----------------------------------
If the Command View management station has two network cards 
installed, one card on an isolated LAN and another on a 
corporate LAN, the client may have trouble connecting to the 
management station if the primary card mapped to the local 
host is on a different LAN than the client.

Workaround:
To solve this issue, configure the first LAN card to 
communicate with the hosts and Command View API clients on 
the SAN. To set the LAN card as the first network card, 
modify the bindings order of the network adapters to bind 
that network card first. This procedure is explained in the 
installation guide.


5.13  The CV CLI "create host_group" Command Removes Spaces 
      in Host Group Name Input Parameters
------------------------------------------------------------
The "create host_group" command in CV CLI removes spaces in 
the host group name input parameters. 

Workaround:
When creating host group names ensure that there are no 
spaces.


5.14  Installing Multiple JRE Versions May Cause Command View 
      Applets to Crash Internet Explorer
-------------------------------------------------------------
In Windows, installing an older or unsupported JRE after 
installing the supported JRE may cause the Command View web 
client running on that system to crash. First, verify the 
order you installed the JRE versions and if necessary, 
uninstall and re-install JRE 1.4.2. Complete the following 
assuming that JRE 1.3.1 is the supported JRE:

  1. Check the timestamps of the JRE installation folders. 
	   The JRE 1.3.1 installation folder path is 
     /JavaSoft/JRE/1.3.x. The JRE 
     1.4.2 installation folder path is  
     /Java/j2re1.4.2.
     If the JRE 1.3.x installation folder has a more recent 
     timestamp than the JRE 1.4.2 installation folder, 
     continue to the next step.
  
  2. If you are solving the problem on the management 
     station, stop all Command View or Performance Advisor 
     services.
  
  3. Uninstall JRE 1.4.2.
  
  4. Download and install JRE 1.4.2_06 from the Sun Web site.
  
  5. If you are solving the problem on the management 
     station, restart all Command View or Performance Advisor 
     services before using Command View or Performance 
     Advisor.


5.15  Flex Copy and External Storage Display Limitation
-------------------------------------------------------
LUNs and ports that are part of Flex Copy XP and External 
Storage XP will not be displayed under the CLI, APIs, SMI-S, 
or in the Path Connectivity Array Security pane.


5.16  Installing and Uninstalling License Keys
----------------------------------------------
If you are unable to install or uninstall license keys for 
the XP48 and XP512 disk arrays using the Licensing Management 
feature, contact your HP account support representative for 
assistance with installing the license key directly on the 
array.

If you are unable to install the emergency key over the 
permanent key for XP128, XP1024, XP12000 and XP10000 disk 
arrays using License Management, perform the operations 
through the Remote Web Console (RWC) GUI or contact your HP 
account support representative for assistance with installing
the key.


5.17  Auto LUN Cannot be Used to Migrate BC Volumes
---------------------------------------------------
In the Command View user guide, the Business Copy chapter 
incorrectly states that Auto LUN can be used to migrate BC 
volumes. This is currently not supported for any XP arrays.


5.18  Install Command View before Performance Advisor
-----------------------------------------------------
When installing both Command View and Performance Advisor, be 
sure to install Command View first.


5.19  Storage Domain Definition
-------------------------------
The introductory pages for the XP48/XP1024/XP12000 LUN 
Management documentation uses the term "storage domain" but 
it is not described well. A storage domain refers to a group 
of hosts within the same host group.


5.20  LUN Management (XP12000) Option Button
--------------------------------------------
Do not use the Option button on the LUN Management 
pane for the XP10000/12000.


5.21  Target ID at HostStorageMapping screen will be blank 
      for Solaris host
-----------------------------------------------------------
The HostStorageMapping screen displays target ID as blank 
when MPxIO's (Sun's Traffic Manager) is enabled on Solaris 
Host.


5.22  AIX and Red Hat Enterprise Linux Support Unclear in 
      Online Help for Host Software Installation Checklist
----------------------------------------------------------
Under System Requirements for the host software installation 
checklist for AIX and Linux hosts, note that the checklist 
does not include the most recent list of supported 
operating systems. See the HP StorageWorks Command View XP 
Installation Guide for a complete list of host agents 
supported for Command View 2.2B and for the settings on the 
host that enable deployment.


5.23  Unable to Connect to XP12000 through CLI and Path 
      Connectivity
--------------------------------------------------------
This may be encountered when the XP12000 is loaded with large 
configuration (for example, configured with numerous amount 
of disks/LDEVs). To resolve this issue, complete the 
following steps:

   1. Change the following properties to higher values at 
      \hpss\dm\tomcat\webapps\hpstmgmt\WEB-INF\cvapi\config\:

      # RMI_GETS_TIME_OUT time out value for Gets in seconds
      RMI_GETS_TIME_OUT= 300
      For example, change it to RMI_GETS_TIME_OUT= 600

      # RMI_TRAP_TIME_OUT time out value Trap Table for Gets 
      in seconds _TRAP_GETS_TIME_OUT=300
      For example, change it to RMI_TRAP_GETS_TIME_OUT= 600


   2. Change the "RMI time-out period {to higher values}. 
      For example, change the value from 1 minute to 
      5/10 minutes. To do so, follow these steps:
         
         a. Launch the Device Manager GUI.
         b. Click the Options icon, located at
            the top, right side of the window.
         c. Select the "Set Env." tab.
         d. Choose the required value from the dropdown 
            list for "RMI time-out period" property.
         f. Click Submit and exit from the control panel.

Note: This limitation is not applicable if you are accessing 
the application through the Device Manager GUI.


5.24  Recovery Testing Fails on the Management Station
------------------------------------------------------
When some Command View services are stopped on the Command 
View management station, the Command View window 
corresponding to that particular feature will show an error. 
The details for the error are in the format of code failure 
details (core-dump). On restarting the specific service, this 
window will not automatically refresh. 

Workaround:
To refresh the window, you need to navigate to another 
Command View window, and then return to the window you wanted 
to refresh.


5.25  SSL Configuration
-----------------------
Command View does not support SSL configuration with self-
signed certificates. If you plan to set up SSL configuration 
for communication between the Command View server and clients 
(browsers or CLI), use SSL certificates issued by a 
certifying authority only. If you are referring to the SSL 
white paper (Apache Web Server SSL Configuration for Command 
View Applications, Revision 10/8/2002), ignore sections of 
the document that refer to "self-signed" certificates.


5.26  Incorrect Wording in Error Messages in User 
      Partition Windows in the Command View Framework
-----------------------------------------------------
When using the Command View Device Manager GUI for the 
XP12000 disk array, you may receive some error messages (in 
the form of a popup dialog) that contain incorrect wording. 
These error messages are only found in the user partition 
assignments in the Command View framework. See “Chapter 7 :  
Appendix”, below, for the correct interpretation of the error 
messages.


5.27 Volume InitializeException or Install CV Exception
-------------------------------------------------------
In the CV CLI make volume operation, if the CU numbers that 
you intend to make the volumes, are not part of any other 
parity group, you will encounter the following error:

"Error Volume InitializeException (or) Install CV Exception 
occurred during set operation in CVS The Specified Sub-System 
ID already exists. Contact the HP Product Support."

Workaround
Complete the following steps to work around this problem:
1. Perform the make volume operation through Web Console GUI.

2. Create a custom volume for these CUs in any of the other 
parity groups as per the following conditions and then 
perform the make volume operation.

* If the CUs are a part of the parity group, perform the 
custom volume operation through CVCLI.

* If the CUs are a not part of the parity group, perform the 
custom volume operation through Web Console GUI.


5.28  Data Purge Functionality Remove Now Button Deletes 
      Older Data 
--------------------------------------------------------
In Path Connectivity, for the Data Purge functionality, the 
Remove Now button deletes older data (based on the Removal 
period) immediately. 

Clicking the "Remove Now" button will delete the older data,
which was not collected from past "Removal period" days.

For example:
    o Last data collected date: 12/20/2004(MM/DD/YYYY)
    o Removal Period :- 15 days

In this example, selecting the "Removal Now" button will 
delete any data not collected from 12/05/2004 (MM/DD/YYYY).

Once data purge is done, you need to add the hosts/switch 
again and perform the data collection to get the latest data.


5.29  Command View XP Path Connectivity Host Agent
      Support for HP-UX 11.23pi
--------------------------------------------------
Command View XP 2.2B only supports local installation for the 
HP-UX 11.23pi Path Connectivity host agent.

To install the HP-UX 11.23pi host agent:
1. From the Command View management station, click the 
   Support icon in the left pane.
2. In the right pane, click on the HP-UX 11.23pi link for the 
   preferred host agent.
3. Follow the instructions in the Command View XP 
   Installation Guide for installing Path Connectivity host 
   agents.

Note: To uninstall the HP-UX 11.23pi host agent, go to the 
depots directory, and run unix_local_uninstall.sh.


5.30  Path Connectivity Graphical Display
-----------------------------------------
The Path Connectivity Remote Deployment graphical display may 
not refresh when deploying a large number of hosts. The 
progress bar for the deployment status may freeze at a 
certain percentage.

Workaround:
Close and reopen the graphical display to get the actual  
status.


5.31  Broken Paths in the Path Connectivity - Connectivity 
      Health Screen Disappeared After Data Collection
----------------------------------------------------------
Beginning with Command View 1.8B, paths that have been broken 
(for example, due to the disconnection of an FC cable) will 
disappear after the next successful Path Connectivity data 
collection. If the paths become valid again, they will 
reappear after the next successful data collection. 

When a path is broken, an event will be sent out. You can use 
the Event Notification module to receive the events. To 
enable Event Notification: 

1. Click on Event Notification in the Command View main 
   window.

2. Click on Event under History in the left menu of Event 
   Notification pane. 

3. Select the category "Path Connectivity" and then select 
   the "Serious" checkbox and appropriate time in the right 
   side of the Event pane. 

4. A table containing events about the change in path health 
   will be displayed with Event description, Date, Status,
   HostIPAddress, Hostname, Hostportwwn, Portstate,
   ArraySerialNo, ArrayProductname, Arraymodel, 
   Arrayportname, Arrayportwwn.

5. To get e-mail notification for these events, see the user 
   guide or online help for Event Notification. 


5.32  Multiple Path Connectivity Instances in a SAN
---------------------------------------------------
When communicating with an XP48/XP512, if you have multiple 
Command View management stations configured in your SAN 
environment to manage the same SAN resources, Path 
Connectivity's "Data Collection Service" may conflict with 
each other. For instance, the Path Connectivity Diagnosis 
function either hangs or takes a very long time to complete.

Workaround:
Disable the Path Connectivity "Data Collection Service" on 
one of the management stations. To do this, go to the Windows 
Services, right-click "HpssDataCollectorService," and then 
click Stop.


5.33  Original Data in New Path Connectivity Database not 
      preserved
----------------------------------------------------------
If you are upgrading from Command View XP 1.40 or earlier, 
the installation process will not preserve the user-entered 
database data. The database content will be lost during the 
upgrade process.


5.34  Path Connectivity Event Log Pane Filter
---------------------------------------------
A defect in the Path Connectivity Event Log Pane occurs that 
allows a pop-up message stating that both hhmmss and 
hh:mm:ss formats are accepted.

The event filter function by date and time requires the time 
format to be hh:mm:ss where hh represents a two-digit hour, 
mm represents a two-digit minute and ss represents a two-
digit second in military time.


5.35  The Connectivity Health Screen Will Not Show Physical 
      Path Information for a Solaris Host with Sun's Traffic 
      Manager (MPxIO) Enabled
------------------------------------------------------------
The Connectivity Health screen provides a table of the paths 
and path connectivity health statuses between hosts and XP 
disk arrays. However, for a Solaris host with Sun's Traffic 
Manager (MPxIO) enabled, the Connectivity Health screen will 
show a pseudo HBA WWN and a logical path between this pseudo 
HBA port to the XP disk array.


5.36  Host Agent Deployment Tool
--------------------------------
The host agent deployment tool (remote install and update) 
will not work when trying to install Command View 2.2B or 
updateing the host agent from earlier versions of Command 
View.

Workaround:
Reinstall the host agent.


5.37  Path Connectivity Manual Data Collection May Show
      Successful Pop-up Message Upon a Failed Host Collection
-------------------------------------------------------------
The Path Connectivity Collect Data Now function may return a 
successful message for a host collection on existing hosts 
even though the collection may have failed. Ensure that there 
are no ERROR events shown in the Path Connectivity event log 
after a manual data collection.


5.38  A "No such object in table" Error May Occur While 
      Accessing the Administration Screens in Path 
      Connectivity
-------------------------------------------------------
A "No such object in table" error may occur while accessing 
the Administration panes in Path Connectivity. This error 
could occur when attempting to manually add a host on the 
Host Discovery - Host Management pane or other Path 
Connectivity Administration feature combined with a 
subsequent network delay or timeout during the requested 
operation.

To resolve this issue, you need to restart the HPSSE2ETomcat 
service. You can choose to either restart the Command View 
services through the Start menu:

Note: The following procedure stops and restarts ALL Command 
View services and will affect processes that are currently 
making changes to disk array configurations.

  o Click Start > Programs > HP StorageWorks Command View XP 
    > Restart Services.

OR

Restart the HPSSE2ETomcat service remotely:

  1. Become a member of the  
	   \Administrators group.
  2. From the Control Panel, click Administrator Tools > 
     Computer Management > Action > Connect to another 
     computer, and then connect to .
  3. From the Control Panel, click Administrator Tools > 
     Computer Management > Services and Applications > 
     Services.
  4. Stop and Start the HpssE2ETomcat service.

Or use the REXEC service:

  - rexec  [-l username] 
    [-n] "NET STOP HpssE2ETomcat"
  - rexec  [-l username]
    [-n] "NET START HpssE2ETomcat"


5.39  Connectivity Health Pane hyperlinks may not work
------------------------------------------------------
When you click on the Connectivity Health pane under Path 
Connectivity, some hypertext links in the diagnostics result 
report frame may not take you back to the main Connectivity 
Health screen. 

Workaround: 
Click the Connectivity Health button near the top of the 
frame to return to the main Connectivity Health screen.


5.40 Installing CV after PA makes the Username and Password 
     case sensitive
-----------------------------------------------------------
If Command View XP is installed on a management station 
which already has Performance Advisor installed on it, then 
the existing Performance Advisor users will have to ensure 
that they use the correct case for both the username and 
password characters while logging into the application.


5.41 No upgrade from CV XP2.2 to CV XP2.2B
------------------------------------------
An upgrade from CV XP 2.2 to CV XP 2.2B is not supported. 
If you are running CV XP 2.2 you must uninstall it, and then 
install CV XP 2.2B.


5.43 Restarting Command View XP services starts the  
     HpssCVSubAgent service 
---------------------------------------------------
The HpssCVSubAgent service is disabled by default at 
installation; but when Command View XP services are restarted 
[Start -> Programs -> HP StorageWorks -> Restart services] 
the HpssCVSubAgent service is enabled and starts 
automatically.
 
Workaround:
To disable the HpssCVSubAgent service, complete the following 
steps:
 o  Go to Control Panel -> Services 
 o  Select HpssCVSubAgent
 o  Right-click and select Properties 
 o  Change the Startup type to Automatic or Manual
 o  Click Stop to stop the service 
 o  Change the Startup type to Disabled
 o  Click Apply/OK 

The HpssCVSubAgent service is disabled.

 
5.44 Command View XP Path Connectivity Hostagent Remote 
     Installation Failure
-------------------------------------------------------
If the remote installation of Command View XP Path 
Connectivity 2.2B Host Agent fails, then install the CV XP 
Path Connectivity Host Agent locally. The instructions for 
installing Command View XP Path Connectivity Host Agents 
locally is descibed on page 42 of the CV XP Installation 
Guide.


_______________________________________________________

Chapter 6 : Command View XP Documentation
-----------------------------------------

The information contained within this appendix is information 
pertinent to Command View not covered elsewhere in the 
documentation.

6.1 Documentation Provided on the Command View CD-ROM
-----------------------------------------------------

  o HP StorageWorks Command View XP Installation Guide
  o HP StorageWorks Command View XP for XP Disk Arrays User 
    Guide
  o HP StorageWorks Command View XP Command Line Interface 
    (CLI) Reference Guide
  o HP StorageWorks Command View XP Path Connectivity User 
    Guide
  o HP StorageWorks Command View XP Path Connectivity Command 
    Line Interface (CLI) Reference Guide
  o HP StorageWorks Command View XP and Path Connectivity 
    online help
  o HP StorageWorks SMI-S XP Release Notes


_____________________________________________________________

Chapter 7 : Appendix
--------------------

The following are corrections for error messages received 
in the user partition assignments in the Command View 
framework:

[Current Message] There is no specifiable LDEV number. 
Probable causes and solutions are: -  The CU number that 
can be specified for the started SLPR is not assigned.
Contact the storage partition administrator. -  All LDEVs 
in the usable CU are already used. Check whether the 
LDEVs are used by another SLPR. Alternatively, contact 
the storage partition administrator.

[Can be read as] There is no specifiable LDEV number. 
Probable causes and solutions are: 1) The CU number that can 
be specified for the started SLPR is not assigned. 2) All 
LDEVs in the usable CU are already being used. Check to see 
if the LDEVs are being used by another SLPR, or contact 
your Command View administrator.

[Current Message] Because the settings across the multiple 
SLPRs are contained, the authority has been shifted to the 
storage administrator from the storage partition 
administrator. To continue the operation, contact the storage 
administrator. To perform other operations, select a function 
button.

[Can be read as] Because the settings across the multiple 
SLPRs are contained, the authority has been shifted from 
Storage Administrator with partition access to Storage 
Administrator with full array access. To continue the 
operation, contact your Command View administrator. To 
perform other operations, click on one of the features icons 
in the left pane.

[Current Message] Some LUs are set across the multiple SLPRs.
If this operation is performed, the storage partition 
administrator will lose his function. Do you want to 
continue the operation?

[Can be read as]  Some LUs are set across the multiple SLPRs. 
If this operation is performed, the user having access to 
these SLPRs will lose access privileges. Do you want to 
continue? 

[Current Message] Storage partition administrator cannot 
disable the expiration lock, because the expiration lock is 
set to Enable by storage administrator.

[Can be read as]  Cannot disable the expiration lock because 
the expiration lock is enabled by the Command View 
Administrator.

[Current Message] The login information of the partition 
management function has been initialized due to detection 
of conflicting information. Contact the storage system 
administrator. (To the storage system administrator: Please 
reconfigure the login information.)

[Can be read as] The login information of the partition 
management function has been initialized due to detection 
of conflicting information. Please contact your 
administrator. To the administrator: Please reconfigure the 
login information.

[Current Message] The LUSE volume is set across plural SLPRs. 
If you perform this operation, the storage partition 
administrator will become unable to operate. Do you want to 
continue this operation?

[Can be read as]  The LUSE volume is set across multiple 
SLPRs. If you perform this operation, users having access to 
these SLPRs will lose their privileges. Do you want to 
continue?

[Current Message] The PFC group extends across multiple 
SLPRs. If this operation is performed, the storage partition 
administrator will lose his function. Do you want to 
continue?

[Can be read as]  The PFC group extends across multiple 
SLPRs. If this operation is performed, users assigned to the 
partitions will lose their privileges. Do you want to 
continue?

[Current Message] The P-VOL and the S-VOL belong to different 
SLPRs. If you perform this operation, the storage partition 
administrator will become unable to operate. Do you want to 
continue this operation?

[Can be read as]  The P-VOL and the S-VOL belong to different 
SLPRs. If you perform this operation, the users assigned to 
the SLPRs will lose their privileges. Do you want to 
continue?

[Current Message] The setting extends across multiple SLPRs.
If this operation is performed, the storage partition 
administrator will lose his function. Do you want to 
continue?

[Can be read as]  The setting extends across multiple SLPRs. 
If this operation is performed, users having access to these 
SLPRs will lose their privileges. Do you want to continue?

[Current Message] The S-VOL and the T-VOL belong to different 
SLPRs. If you perform this operation, the storage partition 
administrator will become unable to operate. Do you want to 
continue this operation?

[Can be read as]  The S-VOL and the T-VOL belong to different 
SLPRs. If you perform this operation, users having access to 
these SLPRs will lose their privileges. Do you want to 
continue?

[Current Message] This function cannot be used by the storage 
partition administrator.

[Can be read as]  You do not have account privileges to use 
this function.

[Current Message] This migration plan extends across 
multiple SLPRs. If you perform this operation, the storage 
partition administrator will become unable to operate. Do you 
want to continue this operation?

[Can be read as]  This migration plan extends across multiple 
SLPRs. If you perform this operation, users having access to 
these SLPRs will lose their privileges. Do you want to 
continue?

[Current Message] You are trying to combine volumes having 
different SLPR numbers into an LUSE volume. If you perform 
this operation,  the storage partition administrator will 
become unable to operate. Do you want to continue?

[Can be read as]  You are trying to combine volumes having 
different SLPR numbers into an LUSE volume. If you perform 
this operation, users having access to these SLPRs will 
lose their privileges. Do you want to continue?