Eva Upgrade

HP StorageWorks Enterprise Virtual Array
updating product software guide (XCS

09522000)
Abstract
This guide describes how to upgrade controller software, disk drive firmware, and related EVA management
software on HP StorageWorks 4400 Enterprise Virtual Array and HP StorageWorks 6400/8400 Enterprise
Virtual Array models. This guide is intended for field personnel and customers who are experienced with Enterprise
Virtual Arrays, storage area networks, and HP StorageWorks Command View EVA.
This guide does not provide information about upgrading or changing the Enterprise Virtual Array hardware.
Part Number: 576287-003

First edition: October 2009
Legal and notice information

Copyright 2009 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set
forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
Java is a US trademark of Sun Microsystems, Inc.
Warranty
WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website:
http://www.hp.com/go/storagewarranty
Contents
1 Getting started .................................................................................. 9
Upgrade overview ...................................................................................................................... 9
Evaluate your configuration .......................................................................................................... 9
XCS 09522000 upgrade considerations ...................................................................................... 10
Upgrade paths ......................................................................................................................... 11
Reference documentation ........................................................................................................... 11
Required kits ............................................................................................................................ 12
2 Pre-upgrade tasks ............................................................................ 15

Checking current controller software version .................................................................................
Checking current software versions ..............................................................................................
Checking the HP Command View EVA version .......................................................................
Checking the storage system hardware ........................................................................................
Checking and upgrading your SAN infrastructure .........................................................................
Collecting SAN configuration data using SAN Visibility ..........................................................
Installing SAN Visibility ................................................................................................
Using SAN Visibility .....................................................................................................
Obtaining a report from HP ..........................................................................................
Reading the report .......................................................................................................
Selecting an appropriate time to perform an online upgrade ..........................................................
Analyzing storage system I/O using HP Command View EVAPerf .............................................
Tips for using HP Command View EVAPerf ......................................................................
HP Command View EVAPerf command options ................................................................
Running HP Command View EVAPerf ..............................................................................
Managing host I/O timeouts for an online upgrade ......................................................................
HP-UX ...............................................................................................................................
Default timeout values ..................................................................................................
IBM AIX ............................................................................................................................
Checking or changing timeouts .....................................................................................
Linux .................................................................................................................................
Mac OS X .........................................................................................................................
Microsoft Windows ............................................................................................................
Checking timeout values ...............................................................................................
NetWare ..........................................................................................................................
OpenVMS .........................................................................................................................
Solaris ..............................................................................................................................
Checking or changing timeouts .....................................................................................
VMware ............................................................................................................................
Xen Citrix ..........................................................................................................................
Back up all storage system data ..................................................................................................
Upgrading HP Command View EVA ............................................................................................
Upgrading on a management server ....................................................................................
Verifying the installation on the management server ................................................................
Upgrading the management module ...........................................................................................
Verifying the installation on the management module ..............................................................
HP StorageWorks Enterprise Virtual Array updating product software guide (XCS 09522000)
15
15
16
17
19
19
20
20
23
26
27
27
27
28
28
31
32
32
32
32
33
34
34
34
34
35
35
35
35
36
36
36
37
38
39
41
Upgrading browsers and JREs ....................................................................................................

HP Insight Remote Support Software ............................................................................................
Upgrading HP Replication Solutions Manager (optional) ................................................................
Monitoring storage system stability ..............................................................................................
Preparing an HP Continuous Access EVA environment for upgrading ...............................................
Upgrading disk drive firmware in an HP Continuous Access EVA environment ............................
Saving storage system configuration information ...........................................................................
Task checklist ...........................................................................................................................
42
42
43
43
45
46
46
48
3 Upgrading the Enterprise Virtual Array ................................................ 51

Solving upgrade problems .........................................................................................................
Step 1. Checking the health of the Enterprise Virtual Array .............................................................
Step 2. Disabling Remote Support Software ..................................................................................
Step 3. Clearing storage system passwords ..................................................................................
Disabling password access in HP Command View EVA ...........................................................
Step 4. Halting all host access to the storage system for an offline upgrade .....................................
Step 5. Upgrading controller software to XCS 09522000 ..............................................................
Upgrading controller software ..............................................................................................
Verifying and resetting the I/O module .................................................................................
Step 6. Upgrading disk drive firmware ........................................................................................
Upgrading firmware on all disks ..........................................................................................
Upgrading firmware on an individual disk .............................................................................
Step 7. Entering storage system passwords ...................................................................................
Enabling password access in HP Command View EVA ............................................................
Step 8. Resuming storage system operation ..................................................................................
Task checklist ...........................................................................................................................
51
51
54
54
54
55
55
55
59
61
62
66
66
67
67
68
4 Troubleshooting ............................................................................... 71
Solving HP Command View EVA problems ...................................................................................
General HP Command View EVA troubleshooting tips .............................................................
Troubleshooting HP Command View EVA with a management server ........................................
Troubleshooting specific HP Command View EVA errors ..........................................................
View is not set or view list is null ....................................................................................
HTTP status 404, not found or status 503, no service ........................................................
Unknown storage system ...............................................................................................
No storage systems found .............................................................................................
Solving security credentials configuration problems .................................................................
Access control .............................................................................................................
Troubleshooting disk drive firmware upgrade ................................................................................
Solving problems selecting a storage system ................................................................................
Solving problems disabling DR group failsafe mode .....................................................................
Solving problems downloading the system software file .................................................................
Invalid image file (Status code 21006) .................................................................................
Bad image header (Status code 65) .....................................................................................
Solving problems if the storage system does not come back online .................................................
Solving problems with multiple resynchronizations ........................................................................
71
71
72
72
72
73
74
74
75
76
76
77
78
78
78
79
79
80
5 Support and other resources .............................................................. 81

Contacting HP ..........................................................................................................................
HP technical support ...........................................................................................................
Subscription service ............................................................................................................
Documentation feedback .....................................................................................................
Related information ...................................................................................................................
81
81
81
81
81
Documents ........................................................................................................................ 81
Websites ........................................................................................................................... 82
Typographic conventions ........................................................................................................... 82
Index ................................................................................................. 85
Figures
1 EVA Storage Network Properties window ................................................................... 17
2 HP Command View EVA online help ......................................................................... 17
3 Hardware Folder Properties window .......................................................................... 18
4 Checking operational state ....................................................................................... 18
5 Sample SAN Visibility report .................................................................................... 26
6 Sample virtual disk statistics display .......................................................................... 30
7 Management module .............................................................................................. 40
8 Controller Events (Initialized system) window ............................................................... 44
9 Hardware Folder Properties window .......................................................................... 52
10 Checking operational state ....................................................................................... 52
11 Controller Events (Initialized system) page .................................................................. 53
12 Code Load Selection window storage system ........................................................... 56
13 Code Load Storage System-Page 1 window ................................................................ 56
14 First code load confirmation screen ........................................................................... 57
15 Second code load confirmation screen ...................................................................... 57
16 Initializing software code load .................................................................................. 58
17 Storage system updating software ............................................................................. 58
18 Verifying XCS version after upgrading ....................................................................... 59
19 I/O tab of Disk Enclosure Properties window .............................................................. 60
20 Blank fields on I/O tab ............................................................................................ 61
21 Code Load Selection window disk drives ............................................................... 63
22 Code Load Disk Drives Page 1 window ................................................................. 63
23 Code Load Disk Drives Page 2 window ................................................................... 64
24 Code Load Disk Drives status window .................................................................... 65
25 Code Load Disk Drives Page 3 window ................................................................... 66
26 Enable Password Access to a Storage System window ................................................. 67
27 Status icon for a good storage system ....................................................................... 77
28 Status icon for a bad storage system .......................................................................... 78
29 Invalid image file (Status code 21006) ...................................................................... 79
30 Bad image header (Status code 65) .......................................................................... 79
Tables
1 Reference documentation ......................................................................................... 11
2 Management software version worksheet ................................................................... 16
3 HP Command View EVAPerf virtual disk statistics ......................................................... 30
4 IBM AIX timeout settings .......................................................................................... 32
5 HP Command View EVA upgrade paths ..................................................................... 37
6 Pre-upgrade task checklist ........................................................................................ 48
7 Controller software .................................................................................................. 56
8 Upgrade task checklist ............................................................................................. 68
9 Possible causes and corrective actions for HTTP 404 and HTTP 503 errors ...................... 73
10 Possible causes and corrective actions when no storage system found ............................ 75
11 Disk drive firmware upgrade errors and workarounds .................................................. 76
12 Document conventions ............................................................................................. 82
1 Getting started
This chapter provides information about required kits and reference documentation. Check that you
have met the requirements and have all the required materials before you begin the upgrade procedures
described in this guide.
HP Command View EVA can be implemented in two ways:
Server-based management HP Command View EVA is installed on a management server connected to the EVA, providing management of multiple HP EVA storage systems. All components
of the software suite (HP Command View EVA, HP Command View EVAPerf, HP Storage System
Scripting Utility, SMI-S EVA) are installed. Server-based management applies to all EVA models.
Array-based management Beginning with HP Command View EVA 8.1, the EVA4400 is
shipped with HP Command View EVA pre-installed on the management module within the controller
enclosure. Only one component of the software suite (HP Command View EVA) is installed. Arraybased management applies only to the EVA4400.
Upgrade overview
Depending on the upgrade path for your configuration, an upgrade can be done either online or
offline.
During an online upgrade, EVA controller software is upgraded while the controllers are receiving
I/O; the controllers resynchronize simultaneously, and both hosts and applications continue to
run. The resynchronization during an online upgrade represents a single disruption of I/O, not
the multiple disruptions seen with some upgrade types. However, you must consider host and application timeouts when doing an online upgrade.
During an offline upgrade (shutdown upgrade), all host I/O to the storage system must be stopped.
All applications and hosts are shut down before the controller upgrade is done, and restarted
when the upgrade is complete.
An offline upgrade requires scheduling time with application managers, and having staff on hand
to shut down and restart applications and hosts. While actual upgrade time may be short, offline
upgrades can require several hours to complete from the start of the first application shutdown
until all hosts and applications have returned to service.
Evaluate your configuration

The following factors can affect the success of an online upgrade. Consider these factors when
determining if an online upgrade is appropriate for your environment.
Queuing host I/OAfter the upgrade, the array performs a resynchronization. During the resynchronization, host I/O is queued to the host, which can create a backlog of requests for processing
when the array is able to respond. The resynchronization may take less than a minute, but the
backlog of requests may take time to clear and some host I/O may experience timeouts. The HP
recommended driver timeout values are 60 seconds. When an I/O timeout occurs, multipath
drivers will typically retry the I/O request on the same path or an alternate path. There are operating system and HBA dependencies on these algorithms. The retry algorithms may extend the
total amount of time that a host I/O will be allowed to complete successfully beyond the 60 second
timeout values. Note that some applications may be more sensitive to I/O delays.
Processing host I/O during the upgrade The upgrade competes with host requests that have a
higher priority, which can affect the upgrade outcome. To ensure that host I/O from business
critical applications or operations is minimized during the upgrade, select a time when a host I/O
disruption would minimize the impact to the business operations.
Communicating with HP Command View EVA The first steps of the upgrade have a lower priority
than host I/O. The upgrade can extend beyond the timeout values expected by HP Command
View EVA, which may result in losing management connectivity to the EVA. A HP Command View
EVA discover operation may be required to re-establish communication with the EVA.
XCS 09522000 upgrade considerations

Before upgrading to XCS 09522000, consider the following:
The EVA resynchronization time is affected by both mapped virtual disk capacity and the number
of virtual disks. Mapped virtual disk capacity is the total of all virtual disks, snapshots, snapclones,
mirrorclones, containers, and data replication log disks. When upgrading from XCS 0950xxxx
or 0952x000 to 09522000, to ensure a resynchronization time of less than 60 seconds, the total
mapped virtual disk capacity and number of virtual disks configured on an EVA should be one of
the following:
less than 400 TB mapped capacity and less than 512 virtual disks created
NOTE:
Multiply the capacity of each data replication log disk by 15 to calculate the total capacity of the
data replication log disks. Add the total capacity of the data replication log disks to your total
virtual disk capacity (all virtual disks, snapshots, snapclones, containers, and mirrorclones); if it
is less that the total mapped virtual disk capacity for the number of virtual disks you have, an
online upgrade is supported.
Stop all storage modification jobs (such as creation, deletion, presentation) 30 minutes before
beginning the controller software upgrade.
If the configuration contains mirrorclones, you must delete, detach, or fracture the mirrorclones
before starting the controller software upgrade.
Do not change any array components during the controller resynchronization process, which occurs
after the controller software upgrade has completed. The controller software upgrade process
maintains a copy of the metadata within the controller memory instead of retrieving metadata from
disks during a resynchronization. Component changes will cause metadata to be retrieved from
disks, making the resynchronization process take longer to complete, which may be beyond host
or application timeout values.
After the controller software upgrade has completed (which includes upgrading the firmware on
the disk enclosure I/O modules), it may take up to 20 minutes to stabilize device port operations.
(The I/O module firmware upgrades are performed sequentially to ensure host I/O continues
during the upgrade.) HP recommends that you check the state of the I/O modules on each disk
enclosure to ensure the upgrade completed successfully, which you can verify by checking that
the latest I/O module firmware version displays.
In a few cases, it has been observed that some fields on the I/O module tab of the Disk Enclosure
Properties page (in HP Command View EVA) appear blank, specifically Hardware type, Hardware
10
Getting started
revision, and Assembly serial number. These blank fields do not affect I/O module operation and
do not mean the upgrade was unsuccessful. HP recommends that you wait 20 minutes to see the
fields become populated. If not, you can reset the I/O module; this is an optional step. However,
if a disk enclosure reports a failed port or SPOF condition 20 minutes after the upgrade has
completed, this will require an I/O module reset.
See Verifying and resetting the I/O module on page 59 for steps to verify the I/O module
firmware version and reset the I/O module.
Upgrade paths
For more information about supported upgrade and downgrade paths, see Table 3.1, Upgrade
support for controller software versions, and Table 3.2, Downgrade support for controller software
versions, respectively, in the HP StorageWorks Enterprise Virtual Array compatibility reference. See
Table 1 for document location.
Reference documentation
Table 1 identifies the documentation you should have available when upgrading the storage system.
Table 1 Reference documentation
Document
Required
Location
HP StorageWorks EVA documentation

HP StorageWorks 4400 Enterprise
Virtual Array user guide
http://www.hp.com/support/manuals
HP StorageWorks 6400/8400
Enterprise Virtual Array user guide
HP StorageWorks 4400 Enterprise
Virtual Array release notes
Yes
HP StorageWorks Enterprise Virtual

Array compatibility reference
Yes
Click Disk Storage Systems under Storage,

and then select HP StorageWorks 4400
Enterprise Virtual Array or HP StorageWorks
6400/8400 Enterprise Virtual Arrays under
EVA Disk Arrays.
HP Command View EVA documentation

HP StorageWorks Command View
EVA user guide
HP StorageWorks Command View
EVA installation guide
HP StorageWorks Storage System
Scripting Utility reference
Yes
Click Storage Software under Storage, and

then select HP StorageWorks Command
View EVA Software under Storage Device
Management Software.
HP StorageWorks EVA replication software documentation

HP StorageWorks Replication
Solutions Manager installation
guide
HP StorageWorks Replication
Solutions Manager administrator
guide
Click Storage Software under Storage, and
then select HP StorageWorks Continuous
Access EVA Software under Storage
Replication Software.
11
Document
Required
Location
HP StorageWorks Continuous Access EVA implementation guide

HP StorageWorks JREserver installation instructions
SAN infrastructure documentation
HP StorageWorks SAN Design
Reference Guide
Yes
Click Storage Networking under Storage,

and then select HP StorageWorks SAN under
HP StorageWorks SAN Solutions.
Required kits
Before you begin the Enterprise Virtual Array upgrade, you must download the XCS 09522000
controller software from the following website:
http://www.software.hp.com
Click Storage and NAS under Product category, scroll down to HP EVA4400/6400/8400 XCS
09522000 and click Receive for Free. Follow the instructions to enter your information and download
the .ISO image.
Before you begin the Enterprise Virtual Array upgrade, you must also download HP Command View
EVA 9.1 software from the IT Resource Center (ITRC) using the following procedure:
1.
To obtain a user ID, register with the ITRC at http://www.itrc.hp.com and click Register at the
top of the page. Perform this step once for each user.
2.
Link your support agreement(s) to your ITRC user ID at http://www.itrc.hp.com/service/

entitlements/linkSupportAgreement.do.
Enter the System Handle or SAID (Service Agreement Identifier), specified on your support
agreement. Perform this step once per support agreement and click link. If you have not logged
into the ITRC, you will be prompted to enter your ITRC User ID and password.
3.
To manage the software updates for your linked support agreements, go to http://
www.itrc.hp.com/service/sum/home.do and click Software Update Manager.
4.
To receive physical media, click Request Updates; to request a download of the .ISO image to
create a CD yourself, click Download Updates.
5.
Select the appropriate Support Agreements or select All Support Agreements.
6.
Under How would you like to view the updates?, select By release and click Next.
7.
Select HP CV EVA 9.1 Rep Sol Mgr 5.0 Media Kit by checking the appropriate box and click
Next.
8.
Review the Delivery address information for physical CD delivery or select the location for the
image file to be stored and click Submit.
If you have questions or require additional assistance go to: http://welcome.hp.com/country/us/en/

wwcontact_us.html and select your country/region.
12
Getting started
IMPORTANT:
Either HP Command View EVA 9.0.1 or 9.1 can be used with XCS 09522000.
13
14
Getting started
2 Pre-upgrade tasks
You should perform several tasks before starting the upgrade to minimize the time required to complete
the XCS upgrade procedure. The required tasks differ depending on your system configuration and
HP Command View EVA implementation. They focus on upgrading components to ensure they meet
the supported configuration for XCS 09522000. Table 6 provides a checklist so you can track your
progress as you perform these pre-upgrade tasks.
Checking current controller software version

Estimated time to complete: About 5 minutes
When to perform: Any time prior to the upgrade
To check your controller software, follow these steps:
1.
2.
Open HP Command View EVA.

In the navigation pane, select the array you plan to upgrade.
The Initialized Storage System Properties window opens. The version field shows the current
version.
Checking current software versions

Estimated time to complete: 1015 minutes
When upgrading the system software, you must upgrade related management software to the correct
version as required. Use Table 2 to collect version information for your current software. You must
upgrade any software that does not meet the required version.
15
NOTE:
For complete details on EVA software compatibility, see the EVA software version compatibility table
and the HP Command View EVA interoperability support table in the HP StorageWorks Enterprise
Virtual Array compatibility reference. See Required documentation on page 11 for the link to this
document.
Table 2 Management software version worksheet
Required
version
Locating version information1
Upgrade procedure
HP
Command
View EVA
(required)
9.0.1 or
9.1
1.
Open HP Command View

EVA.
Upgrading HP Command View

EVA, page 36
2.
Click Help in the Session pane.

The HP Command View EVA
Online Help window opens
and the version is displayed.
HP
Replication
Solutions
Manager
(if installed)
5.0
1.
Open or browse to HP StorageWorks Replication Solutions

Manager.
2.
Select Help > About in the

menu bar. The version of HP
Replication Solutions Manager
server is displayed.
JRE
1.5.0_04
and later 2
1.
Open Windows control panel.
2.
Double-click the Java icon.
3.
On the General tab, click

About.
Software
Current
version
Upgrading HP Replication
Solutions Manager
(optional) on page 43
Upgrading browser and Java

Runtime Environment
(JRE) on page 42
The version of Java is displayed.

Web
browser
(required)
Internet
Explorer
6.0 SP1 or
later
From your browser, select Help >

About Internet Explorer.
Upgrading browser and Java

Runtime Environment
(JRE) on page 42
You can also use Windows Add or Remove Programs to view the software version.
For Windows servers. For clients running other operating systems, see the Browser and JRE support table in the HP StorageWorks
Virtual Array compatibility reference. See Table 1, page 11 for the link to this document.
Checking the HP Command View EVA version

To check the HP Command View EVA version, perform the following steps:
16
Pre-upgrade tasks
1.
Open HP Command View EVA on the management server or the management module, if
applicable. The screen captures in this section reflect server-based management.
The EVA Storage Network Properties window opens.
Figure 1 EVA Storage Network Properties window

.
2.
Click Help in the Session pane.
The full version number is displayed at the top of the online help window. If the version listed is
earlier than 9.0.1 or 9.1, it must be upgraded.
Figure 2 HP Command View EVA online help

.
TIP:
The full version number is also shown at the bottom of the login screen.
Checking the storage system hardware

When to perform: 12 weeks prior to the upgrade, and then daily until the upgrade is completed.
Provide enough time to order and replace any failed components.
Before upgrading your Enterprise Virtual Array, you should check the operation of the storage system
hardware and replace any failed components. This ensures the storage system will be operating
properly when the upgrade is performed. This task should be performed far enough in advance to
give you time to order and replace any failed hardware components before beginning the upgrade.
17
1.
Open HP Command View EVA and click the icon of the storage system you want to upgrade.
Check for hardware errors.
a.
Check the Hardware folder in the Storage Systems navigation pane. If there are any hardware
caution or warning conditions, HP Command View EVA displays the appropriate icon over
the folder.
b.
Click the Hardware folder to expand the navigation tree.

The Hardware Folder Properties window opens. The Operational State field indicates if there
is a hardware problem.
Figure 3 Hardware Folder Properties window

.
c.
Select the applicable array and click Refresh to update the cache.
d.
If a problem is indicated, continue to expand the navigation tree under the Hardware folder,
until you see a hardware component icon with an attention or warning icon on it.
e.
Click the component icon to display the properties window. The Operational state field
indicates if there is a hardware error.
Figure 4 Checking operational state

.
2.
Verify that there are no hardware components in the Unmappable Hardware folder.
a.
Expand the navigation tree under the Hardware folder in the navigation pane.
b.
Click the Unmappable Hardware folder.

Hardware components can be placed in the Unmappable Hardware folder for several
reasons. For example, hardware components can be placed in the Unmappable Hardware
folder, when the I/O modules on a disk enclosure are not working, the controllers restart,
or there is a hardware failure. If there are any hardware components listed under this folder,
determine why they are listed there and fix the problems.
3.
18
Replace any hardware components that have failed.
Pre-upgrade tasks
TIP:
If there is an attention icon, you may still be able to do the upgrade, for example, when leveling is
occurring. If any unusual icons are visible, check with HP before doing the upgrade.
NOTE:
If you must replace any components, see the user guide for your array model for information about
replacement. See Table 1 on page 11 for links to these guides.
Checking and upgrading your SAN infrastructure

Estimated time to complete: Varies depending on the number of components that may require upgrade.
It is important to ensure that your SAN environment meets the configuration requirements of the XCS
controller software. This includes HBA firmware, system drivers, and Fibre Channel switch firmware.
The SAN Visibility tool can assist you in this task because it automates the collection of this data and
provides you with a full report. You can collect the data manually, without using SAN Visibility, but
the manual process is more time consuming. To collect the data manually, complete the following
tasks:
Identify all host servers
Document all firmware versions
Download the required HBA drivers, firmware and MPIO drivers
Collecting SAN configuration data using SAN Visibility

IMPORTANT:
SAN Visibility is only available for server-based management.
HP provides the SAN Visibility tool to automate the process of collecting SAN configuration data.
SAN Visibility collects configuration information from the Fibre Channel switches on your SAN. Any
information provided by devices when they log into the fabric is included. The raw configuration data
is collected, packaged, and sent to HP, where it is formatted into a complete report and returned to
you. You can then use the report to determine if any of your SAN components are not supported by
the latest controller software and must be upgraded or replaced.
NOTE:
The version of SAN Visibility you are running may be a later version that what is shown below.
SAN Visibility requires Java 2 Runtime Environment (JRE) 1.5.0 Update 1 or higher. You can download
the most current JRE version from Sun's website:
http://www.sun.com/
19
Installing SAN Visibility

SAN Visibility is typically installed on the management server running HP Command View EVA.
1.
Download SAN Visibility and SAN Visibility documentation from the following website:
http://h18006.www1.hp.com/products/storageworks/san/index.html
Click SAN Visibility under Networking Solutions and Download Now.
2.
Double-click the downloaded file to launch the installation.
3.
Follow the on-screen instructions to install the software.
Using SAN Visibility

Before running SAN Visibility for the first time, you will need the following information:
The IP addresses of the switches in your SAN connected to the storage system being upgraded.
You must have SNMP access to the switches to collect information from them.
The name or IP address of your SMTP mail server to send reports automatically.
The following steps provide an overview of using SAN Visibility. For complete information about using
this tool, see the SAN Visibility online help.
1.
Double-click the SAN Visibility icon on the desktop.

The SAN Visibility welcome screen is displayed.
2.
20
Click OK to view the SAN Settings window.
Pre-upgrade tasks
3.
Select SAN Settings and enter the following information:
a.
Enter a name in SAN Name. You can use the default SAN Name, but HP recommends that
you change it to a name that is meaningful to you. This name is used when generating
reports, so it should be one that is easily recognized as being associated with the SAN on
which data collection will be done. (If you see a Server Authentication error in the Messages
panel (bottom of screen), this is just notification of lack of a specific service; you can ignore
it.)
b.
Click Rename.
c.
Click Yes to confirm the name change.
d.
Enter a name in Switch Group Name. You can use the default fabric name, but HP
recommends that you change it to a name that is meaningful to you. This name is used when
generating reports, so it should be one that is easily recognized as being associated with
the fabric on which data collection will be done. (Mouse-over pop-ups provide useful
information.)
e.
Click Rename.
Your new switch group name (MySwitchGroup in this example) appears in the right panel
of the SAN Visibility window.
f.
Click Yes to confirm the name change.
21
4.
22
Click Switch Settings and enter the following information:
a.
Enter the IP Address of the primary switch for the SAN for which you want a report.
Information will be collected for all devices connected to this switch.
b.
Clear Discover connected switches. This option automatically detects all switches connected
to the switch identified by the IP address. Including all the cascaded switches increases the
data collected for the report to include all the devices connected to all the switches. If you
want to include all the switches, leave this option selected; to include discovery of subnet
switches, also select Subnet.
c.
Enter the switch login and password if required. The Read Community value is obtained
from the switch.
d.
If you have created more than one switch group, use the Select Switch Group drop-down list
to select the fabric to which you want to add this switch.
e.
Click Discover Switch to discover the switch and activate the login and password. You should
see the extended switch information with IP addresses in the right-most panel.
f.
Click Add to add the switch to the reporting configuration.
Pre-upgrade tasks
5.
Select Customer Details and enter the following information:
a.
Enter your name in Name. This information is required.
b.
Enter your e-mail address in E-Mail to receive the completed report. This information is
required. It is not necessary to have an e-mail address connected to the EVA controller. You
should enter the e-mail address where you typically receive e-mail. To enter multiple email
addresses in E-Mail, separate entries with a semicolon (;).
c.
Enter data in the remaining boxes as appropriate. This information is included in the reports,
but is not required.
d.
To send your raw data to HP automatically when creating a report, select Automatically
e-mail the collected raw data on completion.
e.
Click Next to save and proceed.
NOTE:
For information on using Advanced Settings, see the SAN Visibility user guide.
Obtaining a report from HP

Once you have configured SAN Visibility for data collection, you can obtain a report. There are two
methods for obtaining a report:
AutomaticallyAutomatically e-mails your data to HP when collection is complete. This requires
you to know the SMTP address of your mail server. Select the appropriate SMTP address from the
23
dropdown list. If you have external e-mail access from your environment, this is the preferred
method.
ManuallyRequires you to send your data manually to HP to obtain a SAN Visibility report. If
you do not have external e-mail access, use this method.
Obtaining a report automatically
1. Click Data Collection.
2.
Select the fabric for which you want to create a report from the Choose switch group for data
collection. Check Collect data for all switch groups to create reports for all the fabrics.
3.
Clear Capture Performance data. If you want to gather switch performance data, leave this option
selected. Selecting this option will increase the amount of time required to collect the switch data.
4.
Select Mask IP Address check box if you do not want to send the IP address information (in the
raw report) outside your network.
5.
Select a format for your report by selecting either HTML Report or Microsoft Excel Report, or both.
6.
In the Data Collection sub-box, click Start. A message is displayed in the message area on
successful completion of data collection. If you have selected the option to collect switch
performance data, it will take at least 10 minutes to collect the data.
When data collection is complete, the raw data is sent to HP. The report is processed and the
formatted report returned to you within one business day.
7.
24
When you receive the formatted report, save it to a temporary location on the management
server.
Pre-upgrade tasks
Obtaining a report manually

The SMTP server IP address of the primary switch on the SAN is obtained by the e-mail address you
entered on the Customer Details page. If SAN Visibility does not find the SMTP server or if you want
to create a report manually, follow the procedure below:
1.
Click Data Collection.
2.
Select the fabric for which you want to create a report from Choose switch group for data
collection. Check Collect data for all switch groups to create reports for all the fabrics.
3.
Clear Capture Performance data. If you want to gather switch performance data, leave this option
selected. Selecting this option will increase the amount of time required to collect the switch data.
4.
Select the Mask IP Address check box if you do not want to send the IP address information (in
the raw report) outside your network.
5.
Select a format for the report by selecting HTML Report, Microsoft Excel Report.
6.
In the Data Collection sub-box, click Start. If you have selected the option to collect switch
performance data, it will take at least 10 minutes to collect the data.
7.
Select Launch in the Launch Mail Client panel. The location of the report is displayed.
8.
Manually attach the raw report created with subject line: HP StorageWorks Essentials SAN
Visibility Report Request. Send the report to the following e-mail address: SAN_Visibility@hp.com.
An automated email response is mailed back confirming the receipt of the raw data file. Click
Close.
The report will be processed and the formatted report returned to you within one business day.
9.
When you receive the formatted report, save it to a temporary location on the management server
or another server. A sample report is shown in Figure 5.
25
Figure 5 Sample SAN Visibility report

.
Reading the report

1.
Save the attached file (.hppr file) to a preferred location. Do not change the file extension.
2.
Double-click the saved file to extract the processed report. The processed report is extracted and
stored at: <Install_Dir>\ExtractedProcessReports\<SAN Name>\.
3.
Navigate to the saved location and double-click the index.html file to open the report in your
browser.
4.
In the left navigation pane, click High Level Fabric Summary.

The High Level Fabric Summary window opens. See Figure 5.
5.
For each switch, compare the indicated firmware (FW) version to the switch firmware supported
by XCS 09522000.
This information is listed on the Single Point of Connectivity Knowledge (SPOCK) website (http:/
/www.hp.com/storage/spock). You must sign up for an HP Passport to enable access. Once
access is enabled, select Compatibility Tool in the left menu and then select Fibre Channel Switch.
You can refine your search by the switch brand. If the switch firmware is not at the indicated
version or later, upgrade the firmware. For more information about how to use SPOCK, see the
Getting Started Guide (http://h20272.www2.hp.com/Pages/spock_overview/introduction.html).
6.
For each HBA, compare the indicated driver and firmware versions to the versions supported by
XCS 09522000.
This information is listed on the Single Point of Connectivity Knowledge (SPOCK) website (http:/
/www.hp.com/storage/spock). You must sign up for an HP Passport to enable access. Once
access is enabled, select Compatibility Tool in the left menu and then select Host Bus Adapters.
You can refine your search by the HBA brand. If the HBA firmware is not at the indicated version
or later, upgrade the firmware.
26
Pre-upgrade tasks
NOTE:
After completing required upgrades, HP recommends that you create a new SAN Visibility report to
verify that all upgrades are were successful.
Selecting an appropriate time to perform an online upgrade

To ensure the success of an online upgrade, selecting the appropriate time is essential. Because the
online firmware upgrade is performed while host I/Os are being serviced, the I/O load can impact
the upgrade process. Selecting a period of low I/O activity will ensure the upgrade completes as
quickly as possible, and will avoid disruptions to host and applications due to timeouts.
While there are advantages to performing an online upgrade, there are circumstances when it is not
advisable. Therefore, give careful consideration to the circumstances of your configuration and your
application deployment before making an attempt to do an online upgrade.
NOTE:
When determining an appropriate time to do an online upgrade, ensure that no configuration-related
replication tasks (creating or deleting DR groups, snapshots, snapclones, containers, mirrorclones or
presenting to hosts) are being performed.
Analyzing storage system I/O using HP Command View EVAPerf

The HP Command View EVAPerf tool included with HP Command View EVA can be used to gather
and analyze statistics on storage system utilization. This section provides recommendations on using
HP Command View EVAPerf to gather statistics to help identify periods of low storage system activity.
For more information about HP Command View EVAPerf, see the Monitoring array performance
chapter of the HP StorageWorks Command View EVA user guide for more information. See Table 1
for the link to this guide.
IMPORTANT:
If you have an array-based management system, you can install and run HP Command View EVAPerf
on a supported Windows host connected to the EVA4400.
Tips for using HP Command View EVAPerf

Use HP Command View EVAPerf to identify periods of low I/O activity, during which you can safely
perform on online upgrade of the storage system firmware. Use the following tips to ensure that you
select an appropriate period during which I/O is low and remains low.
NOTE:
Before using HP Command View EVAPerf, you may want to configure friendly names to simplify
identifying your storage systems, virtual disks, and hosts. See the HP StorageWorks Command View
EVA user guide for more information about friendly names.
27
Identify a period of time when you anticipate the I/O load on the storage system will be low. This
is the window to focus on when running HP Command View EVAPerf to gather I/O data.
Run HP Command View EVAPerf to gather I/O data during the chosen window. For example, if
you suspect that I/O load may be low between midnight and 2 AM on Sunday morning, run HP
Command View EVAPerf during this period.
If the I/O pattern is low, capture the data over the same time period several more times to ensure
the low I/O pattern is repeatable.
When you have selected a potential time period for the upgrade, perform the following steps to
ensure I/O activity does not increase unexpectedly during the upgrade:
Alert all system users of the need to minimize the load on the storage system during the time
period you have selected for the upgrade.
Identify any automated processes that may increase I/O load during the upgrade period, including backup applications and scripts. Ensure these processes are suspended for the duration
of the upgrade.
HP Command View EVAPerf command options

The following options are used with the HP Command View EVAPerf commands:
-csv: Use comma separated output. This format is useful for importing large amounts of data into
a spreadsheet for analysis.
-cont n: Runs the command continuously at an interval specified by n. The default interval is
one second.
-dur n: Specifies the duration of a continuous mode session. For example, if you enter evaperf
hps -cont 2 -dur 30, host port data is displayed at two second intervals for a total of 30
seconds.
-sz array: Limits data collection to the specified array(s). You must enter at least one array and
can use either the storage system WWN or friendly name.
-fo filename: Directs output to a specified filename. Include the path information as necessary.
Running HP Command View EVAPerf

1.
Double-click the HP Command View EVAPerf icon on the desktop. The HP Command View EVAPerf
command window opens.
2.
Enter the following command to capture and display the total IOPS (Req/s) and throughput
(MB/s):
evaperf as -cont
n dur n sz array -fo filename
Select an interval and duration that will enable you to view a period that may include a low I/O
activity. For example, collect data once every 10 minutes for a period of 6 hours around the time
of day you plan to do the upgrade. This is to familiarize yourself with characteristic IOPS and
throughput values. For example, the following command will capture data at 10 minute intervals
for 6 hours on an array named EVA1 and store the output in a file named EVA_upgrade:
evaperf as cont 600 dur 51600 sz EVA1 -fo C:\EVA_upgrade
To see your own friendly names, run HP Command View EVAPerf with the fnh command and
list the names with the EVAPerf ls command.
28
Pre-upgrade tasks
3.
When the command has completed, open the file in an ASCII editor. Identify any instances where
the IOPS and throughput limits have been exceeded. If the limits have not been exceeded, this
may be a good period to perform the upgrade. For example, as a guideline, values should be
less than 7000 IOPS and less than 70 MB/s.
NOTE:
Another option for displaying HP Command View EVAPerf data is to use the -csv command
option, which saves the data as comma-separated values for importing into a spreadsheet.
This may be useful for analyzing large amounts of data.
Identifying virtual disk activity

If you cannot locate a period that meets the necessary I/O load requirements, it may be possible to
identify specific applications that are imposing heavy I/O loads, and suspend them long enough to
perform the upgrade. This can be done by using HP Command View EVAPerf to view virtual disk
activity.
For example, after running HP Command View EVAPerf, you determine that all the virtual disks on
the storage system are nearly idle with the exception of one virtual disk. To perform an online upgrade,
it may be desirable to halt the application that is imposing the load on the busy virtual disk. This will
be far less disruptive to your environment than performing an offline upgrade.
To view virtual disk activity:
1.
Double-click the HP Command View EVAPerf program icon on the desktop. The HP Command
View EVAPerf command window opens.
2.
Enter the following command to display virtual disk activity:

evaperf vd cont
n dur n sz array -fo filename
Select an appropriate interval and duration that will enable you to view a period during which
you may want to perform the upgrade. For example, the following command will capture data
at 10 minute intervals for 2 hours on an array named EVA1 and store the output in a file named
virtual_disks:
evaperf vd -cont 600 -dur 7200 -sz EVA1 -fo C:\virtual_disks
29
3.
When the command has completed, open the file in an ASCII editor. The virtual disk information
will appear similar to that in Figure 6.
Activity is reported separately for each controller accessing a virtual disk. The total activity for
each virtual disk is the sum of the reported activity for each controller. A virtual disk may also be
a snapshot, snapclone, or a DR group member. In the output, logical unit number (LUN) is used
interchangeably with virtual disk.
Virtual disks must be presented to a host to be seen by HP Command View EVAPerf. However,
replication volumes on the replication system are visible without being presented.
Because the storage system controllers are active/active, one controller is preferred (the owning
controller) but requests can still be processed by the other controller (the proxy controller). In
active/active controllers, all host requests are logged by the receiving controller only, whether
owning or proxy. Thus, all request rate and data rate activity for a virtual disk is the sum of both
controllers.
The statistics you can use to determine the virtual disk activity are listed in Table 3, in order of
the columns on the screen, left to right.
1.
Check the values for requests: Read Hit Request (Req/s), Read Miss Request (Req/s), and
Write Requests (Req/s).
2.
Look for values in the hundreds. When the values are in the thousands or tens of thousands,
they indicate a very active process such as an active database that you should not disrupt.
If you see high values for request during the period you are checking, look for another time
period to perform the upgrade.
Figure 6 Sample virtual disk statistics display

.
Table 3 HP Command View EVAPerf virtual disk statistics

Counter
Description
Read Hit Req/s
The number of read requests per second completed from the array cache
memory. Data may reside in the cache memory due to a previous cache miss
or because of a prefetch operation generated by a sequential read data stream.
Read Hit MB/s
The rate at which data is read from the array cache memory because of read
hit requests.
Read Hit Latency
The average time it takes to complete a read request (from initiation to information receipt) from the array cache memory.
Read Miss Req/s
The number of read requests (per second) that failed to complete from the array
cache memory and were completed from physical disks instead.
30
Pre-upgrade tasks
Counter
Description
Read Miss Data Rate
The rate at which data is read from physical disks because the data was not
present in the array cache memory.
Read Miss Latency
The average time it takes to complete a read request (from initiation to information receipt) from the physical disks.
Write Req/s
The number of write requests per second completed to a virtual disk that were
received from all hosts. Write requests may include transfers from a source array
to this array for data replication and host data written to snapshot or snapclone
volumes.
Write Data Rate
The rate at which data is written to the virtual disk by all hosts and includes
transfers from the source array to the destination array.
Write Latency
This average time it takes to complete a write request (from initiation to receipt
of write completion).
Flush Data Rate
The rate at which data is written to a physical disk for the associated virtual
disk. The sum of flush counters for all virtual disks on both controllers is the rate
at which data is written to the physical drives and is equal to the total host write
data. Data written to the destination array is included. Host writes to snapshots
and snapclones are included in the flush statistics, but data flow for internal
snapshot and snapclone normalization and copy-before-write activity are not
included.
Mirror Data Rate
The rate at which data travels across the mirror port to complete read and write
requests to a virtual disk. This data is not related to the physical disk mirroring
for Vraid1 redundancy. Write data is always copied through the mirror port
when cache mirroring is enabled for redundancy. In active/active controllers,
this counter includes read data from the owning controller that must be returned
to the requesting host through the proxy controller. Reported mirror traffic is always outbound from the referenced controller to the other controller.
Prefetch Data Rate
The rate at which data is read from the physical disk to cache in anticipation
of subsequent reads when a sequential stream is detected. Note that a sequential
data stream may be created by host I/O and other I/O activity that occurs because of a DR initial copy or DR full copy.
Managing host I/O timeouts for an online upgrade

The default values for host operating parameters such as LUN timeout and queue depth are typically
set to values that ensure proper operation with the storage system. These values are appropriate for
most storage system operations, including online firmware upgrades. In general, host LUN timeouts
of 60 seconds or more are adequate to accommodate an online upgrade. In most situations it will
not be necessary to alter these settings to perform an online firmware upgrade.
If any host timeout values have been decreased to less than 60 seconds, it will be necessary to reset
them to their original default value. The following section provide a summary of the steps and commands
involved in checking and changing timeout values for each supported operating system. See the
operating system documentation for more information.
31
IMPORTANT:
Depending on your operating system, changing timeout values may require a reboot of your system.
To minimize disruption of normal operations, schedule reboots one node at a time. In a cluster
environment, plan your reboots one node at a time and shut down the passive node to avoid unwanted
automatic failover.
HP-UX
CAUTION:
Because HP-UX supports boot across Fibre Channel SAN, any change to default SCSI timeouts on
the HP-UX host may cause corruption and make the system unrecoverable.
Default timeout values

Sdisk timeout: 30 seconds
(LVM) lvol timeout: 0 seconds (default=0, retries forever)
IBM AIX
Checking or changing timeouts
AIX requires the disk settings shown in Table 4 for the native multipath drives.
Table 4 IBM AIX timeout settings
Setting
Value
Description
PR_key_value
NA
Sets the key value for persistent reservations. Persistent reservations

are not supported.
Algorithm
fail_over
Sets the load balancing algorithm to fail_over. All I/O uses a single
path. The remaining paths are in standby mode. The value round_robin
is not supported.
hcheck_interval
60
Sets the path health feature to check each device every 60 seconds.
hcheck_mode
nonactive
Specifies the I/O paths monitored by the path health checking feature:
nonactiveChecks all I/O paths for Failed status, and checks standby
paths for Used/Opened devices.
queue_depth
Sets the queue depth.
reserve_policy
Single path
Sets the reserve policy to standard SCSI-2 reservations.
rw_timeout
60
Sets the read/write timeout to 60 seconds.
32
Pre-upgrade tasks
Linux
NOTE:
RHEL4/SLES9 SCSI device has a default 30 second timeout value and up to 5 retries can occur.
RHEL5/SLES10 SCSI device has a default 60 second timeout and also up to 5 retries can occur. In
general, these timeout periods are adequate to accommodate an EVA online firmware upgrade.
The following configuration recommendations apply to both RedHat and SuSE.
QLogic Driver parameters (failover enabled):
qdepth = 16
port_down_retry_count = 30
login_retry_count = 30
failover = 1
load_balancing = 1
excludemodel = 0x0
auto_restore = 0xA0
QLogic Driver parameters (single path):
qdepth = 16
port_down_retry_count = 64
login_retry_count = 30
failover = 0
load_balancing = 1
excludemodel = 0x0
auto_restore = 0xA0
Emulex Driver parameters (single path)
HPELXLPFC=y
nodev_timeout=60
qdepth=30
discovery_threads=1
Emulex Driver parameters (with Multipulse)

nodev_timeout=10
qdepth=16
discovery_threads=32
To check or set Linux parameters, use the set_parm executable found in the /opt/hp/
<driver-specific> directory. When executed, the options to change timeout values are displayed.
33
NOTE:
The timeout values must be increased for Emulex single path (without multipath support) and
QLogic single path being used in the environment. This is not only important for online upgrades
but for general data integrity.
Online controller firmware upgrades are supported with Linux boot devices.
Mac OS X
Online firmware upgrade is not supported for Mac OS X. All firmware upgrades must be done offline
for Mac OS X servers.
Microsoft Windows
For Microsoft Windows, consider the following guidelines:
Ensure that MPIO is installed and both paths are active and have access to the array.
Boot devices are supported with online controller firmware upgrades, but the page-file disk should
not be on the boot device during an online upgrade.
If the array being upgraded is used as a quorum disk in a Microsoft Windows cluster, an online
controller software upgrade may cause the cluster to time out on the quorum disk and attempt to
transition disks on that node to the surviving node. The cluster may hang in this situation and require
a cluster reboot to recover. A work-around is to transition all disks on the secondary node to the
primary node, stop the cluster services, and shut down the secondary node before starting the
controller software upgrade. Once the upgrade is complete, restart the cluster services and restart
the secondary node to return it to the cluster.
You cannot boot from SAN in this environment.
Checking timeout values

The key timeout setting in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\Disk\TimeoutValue should be set to 3c (60 seconds), which is the Microsoft Windows
default.
NetWare
NOTE:
When NetWare is used with the EVA4400, it is not supported in an HP Continuous Access EVA
environment.
No changes are needed for NetWare operating system timeouts. The default values from HBA are:
Login retry count: 8
Port down retry count: 16
Link down timeout: 8
34
Pre-upgrade tasks
OpenVMS
The limit for LUN timeout is 120 seconds.
NOTE:
OpenVMS handles the controller reboot seen at the conclusion of the firmware update process. Disks
on the controller display a Mount Verify status during the controller reboot but regain Mounted status
and resume I/O operations upon the completion of the controller reboot. No changes need to be
made to any OpenVMS default settings when performing an online firmware upgrade.
Online controller firmware upgrades are supported in OpenVMS cluster environments where the EVA
is the cluster boot device.
Solaris
Solaris supports online controller upgrades with the following driver timeouts:
Sun Drivers (qlc or emlxs): 60 seconds
QLogic (qla2300): 60 seconds
Emulex (lpfc): 60 seconds
Checking or changing timeouts

For Sun drivers, add the following lines to /etc/system file:
set sd:sd_io_time = 60
set ssd:ssd_io_time = 60
For QLogic, edit the /kernel/drv/qla2300.conf file and change the

hbax-link-down-timeout value to 60 as follows:
hba0-link-down-timeout=60;
For Emulex, edit the /kernel/drv/lpfc.conf file and change the linkdown-tmo value to 60
as follows:
linkdown-tmo=60;
VMware
VMware ESX (Hypervisor) does not time I/O for a guest operating system. Thus the SCSI timeouts on
commands issued by each VMware guest (Linux, Windows, Solaris) are those provided for these
systems.
35
NOTE:
For Microsoft Windows guests: set the windows SCSI timeout registry to 60secs, as follows:
1.
In the windows registry, find HKEY_LOCAL_MACHINE\System\CurrentControlSet\

Services\Disk\TimeOutValue
2.
Set this value to 60 decimal (3Ch).
The ESX layer (VMFS, the VMware filesystem) controls timeouts of VMFS I/O. These values may vary
from ESX release to release.
Xen Citrix
For Xen Citrix, except for NFS SR timeouts, because Citrix XenServer 5.0 mounts using software with
non-default timeout values, use the values described in the Linux section Linux, page 33.
To check or set Xen Citrix parameters, use the set_parm executable found in the /opt/hp/
<driver-specific> directory. When executed, the options to change timeout values are displayed.
NOTE:
The timeout values must be increased for Emulex single path (without multipath support) and
QLogic single path being used in the environment. This is not only important for online upgrades
but for general data integrity.
Online controller firmware upgrades are supported with Xen Citrix boot devices.
Back up all storage system data

Estimated time to complete: Varies
When to perform: As close as possible to the upgrade
Before beginning the upgrade, it is recommended that you perform a full verified backup of all storage
system data. Although not required, it is always good practice to back up your data before performing
major operations such as software upgrades. The backup should be scheduled as close to the upgrade
process as possible.
For more information about establishing and implementing good backup procedures for the EVA,
contact your HP sales representative.
TIP:
If using server-based management, HP recommends that you also back up the management server
before you begin the upgrade.
Upgrading HP Command View EVA

Follow the procedures in this section to upgrade HP Command View EVA on the management server.
If you have an EVA4400 and are using array-based management, see Upgrading the management
module for upgrade instructions.
36
Pre-upgrade tasks
NOTE:
Before starting the upgrade, check the release notes for the version to which you are upgrading for
any details on the upgrade process.
Estimated time to complete: 1520 minutes or longer, depending on your configuration.
HP Command View EVA 9.0.1 or 9.1 is required with XCS 09522000. Check the current version
and upgrade the software if necessary.
TIP:
To help ensure fast recovery from the upgrade, it may be useful to remove a disk from the management
server.
Table 5 identifies the upgrade paths for HP Command View EVA 9.1.
Table 5 HP Command View EVA upgrade paths
Current HP Command View EVA Version
Upgrade Path
HP Command View EVA 8.x
Upgrade to HP Command View EVA 9.0.1
HP Command View EVA 9.0.1
Upgrade to HP Command View EVA 9.1 (optional)
For more information on HP Command View EVA, including the HP StorageWorks Command View
EVA installation guide and the release notes, download documentation from the website listed in
Required documentation on page 11.
Upgrading on a management server

This procedure is for the typical HP Command View EVA installation on a management server. To
use the custom installation procedure, which provides control over which components are installed,
see the HP StorageWorks Command View EVA installation guide for instructions.
To install the complete software suite:
1.
Close all applications running on the management server.
2.
Insert the installation CD into the drive.
3.
Browse to the installation CD.
4.
Double-click HP StorageWorks Command View EVA Software Suite.exe to start the

installation.
The InstallAnywhere StorageWorks Command View EVA window opens.
5.
Select the preferred language from the drop-down menu (English or Japanese). (On an English
Windows system, the drop-down menu contains only English; on a Japanese Windows system,
the drop-down menu contains both English and Japanese.)
Click OK.
The Introduction window opens.
37
6.
Click Next.
The CV EVA License Agreement window opens.
7.
Read and accept the terms of the license agreement.
8.
Click Next.
The Choose Install Set window opens.
Command View Enterprise Virtual Array Performance Monitor and SMI-S CIMOM are selected
by default.
9.
Click Next.
The Select Security Groups Configuration window opens.
10. Click Next.

The installation summary window opens.
11. Verify the pre-installation summary. Click Install.
NOTE:
The value for Required Disk Space shown in the Pre-Install Summary Dialog represents the
size of files the installer will load; the size displayed in Add/Remove Programs is determined
by Windows.
12. The installation summary window opens. Click Finish.
All the software components are installed to <system drive>:\Program Files\
Hewlett-Packard.
NOTE:
When SMI-S EVA is installed using the typical installation, a default account for the CIM administrator
is created if an administrator account exists on the management server prior to installation. The default
user name and password is administrator. If an administrator account does not exist on the
management server prior to installation, the default CIM administrator account is not created during
installation. You must add at least one CIM administrator account to CIMOM after completing the
installation. See Managing users in SMI-S EVA in the HP StorageWorks Command View EVA
installation guide for more information.
A trust relationship between HP Command View EVA and SMI-S EVA is established automatically
when you install SMI-S EVA. As a result, HP Command View EVA accepts all SMI-S EVA queries.
Verifying the installation on the management server

To verify that the software was installed successfully:
38
Pre-upgrade tasks
1.
Ensure that:
The software icons for HP Command View EVA , HP Command View EVAPerf , and/or
HP Storage System Scripting Utility appear on the desktop.
The software is available from the Start menu (for example, Start > Programs > HP Command
View EVA).
Go to Add/Remove Programs and make sure the applicable software components are listed:
HP StorageWorks Command View EVA software suite
HP StorageWorks Command View EVA
HP StorageWorks Command View EVA Performance Monitor
HP StorageWorks SMI-S EVA
HP StorageWorks SMI-S CIMOM
NOTE:
HP Storage System Scripting Utility is not listed in Add/Remove Programs.
2.
Run HP Command View EVA.
3.
Verify the display of storage system resources in the interface. In the Navigation pane, click
Hardware and verify the following:
New, uninitialized arrays appear as uninitialized storage systems.
Previously initialized arrays appear with their previous names and correct status. (Select each
storage array to view the Properties window.)
Previous disk groups, hosts, virtual disks, and other resources appear in the Navigation pane.
If information is not displayed properly, it may be necessary to configure your browser settings. See
HP StorageWorks Command View EVA installation guide for more information.
Upgrading the management module

If you have an EVA4400, follow the procedures in this section to:
Upgrade HP Command View EVA on the management module (for array-based management)
Upgrade the management module software
NOTE:
Management module software is bundled with the array-based management version of HP Command
View EVA. Thus, when you upgrade HP Command View EVA on the management module, you are
also upgrading the management module software.
Even if you are not using array-based management, you must complete the procedure in this section
for the EVA4400 to ensure the management module software is current.
When to perform: Any time prior to the upgrade.
To upgrade the management module:
39
1.
Connect a server with a CD drive to the management module port (1, Figure 7) on the controller
enclosure.
Figure 7 Management module

.
2.
Insert the installation CD into the drive.
3.
Open a browser and browse to the WOCP (Web-based Operator Control Panel):
https://HP EVA storage system IP address:2373
NOTE:
If you are running a version of management module software earlier than 0001.1000
(which corresponds to XCS 09004000 or earlier), use port 2372.
If you have not previously set the IP address for the management module, the default is
192.168.0.1.
If you have not previously completed the initial setup for the management module, see
Connecting to the management module (initial setup) in the Web-based operator
panel user guide.
The WOCP login window appears.

4.
Log in as an HP EVA administrator (user name admin and the password).

The WOCP GUI appears.
5.
In the navigation pane, select Update management module firmware.

The Update Management Module Firmware window opens.
6.
Click Browse and browse to the installation CD.
7.
Select the ABM.pkg file and then click Next step.
8.
Follow the online instructions and then click Finish. A confirmation window opens.
40
Pre-upgrade tasks
9.
Click OK.
The Management Module Restart in Progress window opens. The image files are loaded. This
step can take several minutes.
IMPORTANT:
The management module will restart on completion of this update. Allow up to 15 minutes
to re-establish a browser connection. Do not reseat, restart, or reset the management module
during this time if you are unable to reconnect from your browser.
After the management module restarts, it may exhibit slow response time for about 5 to 10
minutes while gathering array information and completing background processes.
Upon completion of the upgrade and restart, one of the following occurs:
The WOCP login window opens. Continue with Verifying the installation on the management
module.
The WOCP login window fails to open, which occurs if you are using the default IP address
(192.168.0.1) for the management module. Continue with Step 10.
10. Press the reset button (2, Figure 7) on the management module to activate the IP address.
Upon reset, the WOCP login window opens. Continue with Verifying the installation on the
management module.
Verifying the installation on the management module

To verify that the management module software was upgraded successfully:
1. On the WOCP login window, log in as an HP EVA administrator (username admin and the
password).
NOTE:
The password, if set before the upgrade, is maintained during the upgrade.
2.
The WOCP GUI appears.

Click View detailed system information and verify the Operation state, XCS version, and the
management module software version.
To verify that HP Command View EVA was upgraded successfully:

1.
Open a browser and browse to HP Command View EVA:

https://EVA storage system IP address:2372
(for example: https://15.154.58.19:2372)
2.
Log in using the same username and password that you use for the WOCP login.
3.
Verify that the correct time is set:

a.
On the Initialized Storage System Properties window, select System Options.
b.
Select Set time options.
c.
Verify that the time displayed in the Current system time box is correct. If it is incorrect, enter
the correct time and save your changes. If it is incorrect, enter the correct time and save your
changes.
41
Upgrading browsers and JREs

Ensure that you are using a supported browser and JRE. HP Command View EVA may not work
correctly with an unsupported browser.
The JRE is not used by HP Command View EVA, but it is needed for HP Replication Solutions Manager.
It is also required for WEBES and SAN Visibility. See Upgrading HP Replication Solutions Manager
(optional) on page 43 for more information.
For complete information on supported browsers and JREs, see the "Browsers and JRE support" table
in the HP StorageWorks Enterprise Virtual Array compatibility reference. See Required
documentation on page 11 for the link to this document.
NOTE:
If you need to update the browser version on remote computers, do so after you have upgraded HP
Command View EVA.
HP Insight Remote Support Software

HP strongly recommends that you install HP Insight Remote Support software to complete the installation
or upgrade of your product and to enable enhanced delivery of your HP Warranty, HP Care Pack
Service or HP contractual support agreement. HP Insight Remote Support supplements your monitoring,
24x7 to ensure maximum system availability by providing intelligent event diagnosis, and automatic,
secure submission of hardware event notifications to HP, which will initiate a fast and accurate
resolution, based on your products service level. Notifications may be sent to your authorized HP
Channel Partner for on-site service, if configured and available in your country. The software is
available in two variants:
HP Insight Remote Support Standard: This software supports server and storage devices and is
optimized for environments with 1-50 servers. Ideal for customers who can benefit from proactive
notification, but do not need proactive service delivery and integration with a management platform.
HP Insight Remote Support Advanced: This software provides comprehensive remote monitoring
and proactive service support for nearly all HP servers, storage, network, and SAN environments,
plus selected non-HP servers that have a support obligation with HP. It is integrated with HP Systems
Insight Manager. A dedicated server is recommended to host both HP Systems Insight Manager
and HP Insight Remote Support Advanced.
Details for both versions are available at:
http://www.hp.com/go/insightremotesupport
To download the software, go to Software Depot:
http://www.software.hp.com).
Select Insight Remote Support from the menu on the right.
42
Pre-upgrade tasks
Upgrading HP Replication Solutions Manager (optional)

NOTE:
HP Replication Solutions Manager is currently supported with server-based management only.
If HP Replication Solutions Manager is installed, you must upgrade it to version 5.0. HP Replication
Solutions Manager is an optional interface for HP Business Copy EVA and HP Continuous Access
EVA.
For installation information, see the HP StorageWorks Replication Solutions Manager installation
guide. For general usage information, see the HP StorageWorks Replication Solutions Manager
administrator guide. See Required documentation on page 11.
HP Replication Solutions Manager can be downloaded from the following website:
http://h18006.www1.hp.com/products/storage/software/bizcopyeva/index.html
Click Software & drivers.
NOTE:
HP Replication Solutions Manager 5.0 requires JRE 1.5.0_04 and later. Go to the Sun website
(www.sun.com) and download the required JRE.
Monitoring storage system stability

When to perform: 48 hours before beginning the upgrade
The storage system configuration should be stable for 48 hours before beginning the upgrade. Check
the status of the array to ensure it is stable and then continue monitoring status until the upgrade
begins.
1.
43
2.
Using HP Command View EVA, examine the controller event log and check for any critical events.
a.
Select the icon of the storage system you want to upgrade in the Navigation pane.
b.
Click View Events.

The View Events window opens.
c.
Click Controller Event Log.

The Controller Events window opens in a new browser window.
Figure 8 Controller Events (Initialized system) window

.
d.
Check the Severity field to determine if any unexpected Critical events
have occurred.
If Critical events have occurred, perform the steps outlined in the corrective action codes to
correct the problems. In some cases, it may be necessary to call your HP-authorized service
representative to fix the problem.
3.
Verify that no changes to the storage system configuration are in progress. For example, you
should not be in the process of creating a virtual disk. Configuration changes should not be made
within 48 hours before beginning the upgrade. Proactive event notification can be used to alert
you if a critical event occurs during the 48 hours before the upgrade.
NOTE:
The leveling process does not impact the upgrade. If leveling is in progress, the upgrade
can be performed. The leveling will be suspended during the upgrade and resumed
Ensure you suspend any processes or applications that may change the storage system
configuration, such as backups and snapshot creation or deletion. Stop any HP Storage
System Scripting Utility scripts that are scheduled to run automatically.
44
Pre-upgrade tasks
Preparing an HP Continuous Access EVA environment for

upgrading
NOTE:
HP Continuous Access EVA is currently available with server-based management only.
Estimated time to complete: Varies depending on replication configuration
When upgrading an EVA in an HP Continuous Access EVA environment, the following requirements
must be met. See HP StorageWorks Continuous Access EVA implementation guide for more information.
Before you upgrade the controller software, you must upgrade HP Command View EVA (and
layered applications) to the required version on both the source and destination storage systems.
Before you upgrade any storage system in an HP Continuous Access EVA relationship, ensure that
all storage systems in the storage network are running the same version of controller software.
This will ensure that when you upgrade one storage system, the storage network will have only
two versions of controller software. You cannot have more than two versions in an HP Continuous
Access EVA environment.
During the time that the HP Continuous Access EVA storage systems are running different controller
software versions, you cannot make any configuration changes to your storage systems.
You must perform the necessary upgrades to the storage systems in the HP Continuous Access
EVA relationship within 60 days (1440 hours) to make all controller software versions the same.
CAUTION:
In an HP Continuous Access EVA environment, do not begin the upgrade until the following conditions
are met. If you attempt to upgrade the controllers before the following conditions are met, controller
operation will fail.
Ensure that no DR group is logging, merging, or copying. Furthermore, none of the DR groups
can be in a failsafe locked state.
1. Click the DR group icon in the Navigation pane.
2. Check the Log state in the DR Group Properties window.
Ensure the connection between the storage systems is not compromised or failed.
1. Click the Data Replication folder in the Navigation pane.
2. Check the Connection State in the Data Replication Folder Properties window.
All EVA storage systems must be running normally with fully functional controller pairs.
After upgrading the first storage system (for example, the source), wait at least three minutes and
no more than 60 days before upgrading the second storage system. Ensure the preceding conditions
are met on the second system.
45
Upgrading disk drive firmware in an HP Continuous Access EVA environment

When upgrading disk drive firmware in an HP Continuous Access EVA environment, the following
requirements must be met. See HP StorageWorks Continuous Access EVA implementation guide for
more information.
Verify that all DR groups are not failsafe mode enabled or in the failsafe locked state (DR group
failsafe mode should be disabled).
Suspend replication and disable the intersite link or modify zoning to isolate the source array from
the destination array.
Upgrade the disk drive firmware on the destination array
Re-establish intersite link communication between the arrays and resume replication, allowing the
DR group merges to complete.
Perform site failover.
Suspend replication and disable the intersite link or modify zoning to isolate the source array from
the destination array.
Upgrade the disk drive firmware on the new destination array (before site failover, this was the
source array).
Re-establish intersite link communication between the arrays and resume replication, allowing the
DR group merges to complete.
Perform site failback.
Saving storage system configuration information

Before starting the upgrade, collect and save your current configuration information. This information
can be used to restore the existing configuration if necessary. The configuration data is saved to a
series of files stored in a location other than on the storage system. HP Storage System Scripting Utility
(called the utility) is used to collect configuration information.
This procedure can be performed from the management server where HP Command View EVA is
installed, or from any host running the utility to communicate with the HP Command View EVA.
NOTE:
You will need the IP address or name of your management server to run the utility.
1.
Double-click the HP Storage Systems Scripting Utility desktop icon to open the utility. When
prompted, enter Manager (management server name or IP address), User name, and Password.
2.
Enter LS SYSTEM to display the arrays managed by the management server.
3.
Enter SELECT SYSTEM system name, where system name is the name of the storage system.
The storage system name is case sensitive. If there are spaces between the letters in the name,
quotes must enclose the name. For example, SELECT SYSTEM Large EVA.
46
Pre-upgrade tasks
4.
Enter CAPTURE CONFIGURATION, specifying the full path and filename of the output files for
the configuration data.
The configuration data is stored in a series of one to five files, which are scripts. The file names
begin with the name you select, with the restore step appended. For example, if you specify a
file name of LargeEVA.txt, the resultant configuration files would be LargeEVA_Step1A.txt,
LargeEVA_Step1B, etc. Files which do not contain configuration information are not created
and therefore are not available to be restored.
The contents of the configuration files can be viewed with a text editor.
5.
Enter exit.
TIP:
When capturing the HP Command View EVA configuration, it is a best practice to specify the SAVE
ALL option. This helps to capture critical data such as the WWN, useful for rebuilding the array
configuration.
NOTE:
You cannot use the utility to restore a configuration that contains disk drives of different capacities.
You must manually restore that type of configuration. See the Restoring an array configuration with
different disk sizes and types section in HP StorageWorks Storage System Scripting Utility reference
for more information.
You can run the CAPTURE VALIDATE command for each of the files generated by the CAPTURE
CONFIGURATION command to determine if the file has been modified since the initial capture.
As a best practice, also use the following commands to collect configuration data:
LS DISK_GROUP FULL
LS HOST FULL
LS VDISK FULL
If applicable, use the following commands as well:
LS ISCSI_HOST FULL
LS ISCSI_LUN FULL
For more information about using the utility or using the CAPTURE commands, see the HP StorageWorks
Storage System Scripting Utility reference. See Required documentation on page 11 for the link to
this document.
47
Task checklist
Use the following checklist to track your progress and mark when a task has been completed. You
can initial and timestamp task completion if you like.
Table 6 Pre-upgrade task checklist
Task
Task complete
Checking current controller software version, page 15

Time required: About 5 minutes
When to perform: Any time before the upgrade.
Checking current software versions, page 15
Time required: 1015 minutes
When to perform: Any time before the upgrade
Checking the storage system hardware, page 17
When to perform: 12 weeks before the upgrade, and then daily until the upgrade is
completed. Provide enough time to order and replace any failed components.
Checking and upgrading your SAN infrastructure, page 19
Time required: After collecting and evaluating data on your configuration over several
weeks, you can determine when is an appropriate time to do the upgrade.
Back up all storage system data, page 36
Time required: Varies
Upgrading HP Command View EVA, page 36
Upgrading browser and Java Runtime Environment (JRE), page 42
Installing Remote Support Software, page 42
Upgrading HP Replication Solutions Manager (optional), page 43
Monitoring storage system stability, page 43
When to perform: 48 hours before upgrade
48
Pre-upgrade tasks
Task
Task complete
Preparing an HP Continuous Access EVA environment for upgrading, page 45

Time required: Varies depending on replication configuration
Saving storage system configuration information, page 46
49
50
Pre-upgrade tasks
3 Upgrading the Enterprise Virtual Array

The following steps guide you through the process of upgrading the system software. Ensure that you
follow them carefully and in the specified order. Table 8 on page 68 provides a checklist so you can
track your progress as you perform the upgrade. Make sure you have all the items indicated before
beginning the upgrade.
Solving upgrade problems

If you experience any problems when performing the XCS upgrade procedure, see
Troubleshooting on page 71 for assistance. If you are still unable to resolve the problem, contact
your HP-authorized service representative for assistance.
Step 1. Checking the health of the Enterprise Virtual Array

Before upgrading your Enterprise Virtual Array, perform a final check of the overall status of all
components. The pre-upgrade checks should ensure that the storage system is ready for upgrading,
but the storage system status should be checked again.
51
1.
Check for hardware errors.
a.
Check the Hardware folder in the Navigation pane. If there are any hardware caution or
warning conditions, HP Command View EVA displays the appropriate icon over the folder.
b.
Click the Hardware folder to expand the navigation tree.

The Hardware Folder Properties window opens. The Operational State box indicates if there
is a hardware problem.
Figure 9 Hardware Folder Properties window

.
c.
If a problem is indicated, continue to expand the navigation tree under the Hardware folder
until you see a hardware component icon with an attention or warning icon on it.
d.
Click the component icon to display the properties window. The Operational state box
indicates if there is a hardware error.
Figure 10 Checking operational state

.
2.
Verify that there are no hardware components in the Unmappable Hardware folder.
a.
Expand the navigation tree under the Hardware folder in the Navigation pane.
b.
Click the Unmappable Hardware folder.

Hardware components can be placed in the Unmappable Hardware folder for several
reasons. For example, hardware components can be placed in the Unmappable Hardware
folder, when the I/O modules on a disk enclosure are not working, the controllers restart,
or there is a hardware failure. If there are any hardware components listed under this folder,
determine why they are listed there and fix the problems.
52
Upgrading the Enterprise Virtual Array
3.
Using HP Command View EVA, examine the controller event log and check for any critical events.
a.
Select the icon of the storage system you want to upgrade in the Navigation pane.
b.
Click View Events.

The View Events page opens.
c.
Click Controller Event Log.

The Controller Events page opens in a new browser window.
d.
Check the Severity field to determine if any unexpected Critical events

within the last 48 hours.
have occurred
The most recent 400 events are displayed. If more than 400 events have occurred within
the last 48 hours, use the Display Range box to select the preceding events.
Figure 11 Controller Events (Initialized system) page

.
e.
If Critical events have occurred within the last 48 hours, perform the steps outlined in the
corrective action codes to correct the problems. In some cases, it may be necessary to call
your HP-authorized service representative to fix the problem.
CAUTION:
If any critical events have occurred within the last 48 hours, do not proceed with the upgrade
until the situation has been resolved.
53
4.
Verify that no changes to the storage system configuration are in progress. For example, you
should not be in the process of creating a virtual disk. Configuration changes should not be made
within 48 hours before beginning the upgrade.
NOTE:
The leveling process does not impact the upgrade. If leveling is in progress, the upgrade
can be performed. The leveling will be suspended during the upgrade and resumed
Make sure you suspend any processes or applications that may change the storage
system configuration.
Proactive event notification can be used to alert you if a critical event occurs during the
48 hours before the upgrade.
Step 2. Disabling Remote Support Software

To avoid generating unnecessary events and alerts during the upgrade, disable Remote Support
Software while performing the upgrade as follows:
1.
On the HP Command View EVA management server, open a command window.
2.
Enter the following commands to stop Remote Support Software:

C:\>net stop desta_service
3.
Enter exit.
Step 3. Clearing storage system passwords

If you use passwords on the controllers, use the following procedure to clear them.
Disabling password access in HP Command View EVA

To disable password access to a storage system in HP Command View EVA:
NOTE:
You will need to know the World Wide Name (WWN) of the storage system to disable password
access.
1.
Start HP Command View EVA in your browser.
2.
Click Server Options in the Session pane.

The Management Server Options window opens.
3.
Click Storage system password access.

The Storage System Password Access window opens.
54
4.
Click Disable.
The Disable Password Access to Storage System window opens.
5.
Select the storage system World Wide Node Name from the drop-down list.
6.
Click Disable Password.

A confirmation box opens.
7.
Click Yes to disable the password.
Step 4. Halting all host access to the storage system for an

offline upgrade
IMPORTANT:
If you are upgrading from XCS 0950xxxx or 0952x000, an offline upgrade is optional. If you are
upgrading from an XCS version earlier than 0950xxxx, an offline upgrade is required.
Estimated time to complete: Varies. Must be performed for each host accessing the storage system.
For the offline upgrade, all host I/O to the storage system must be stopped. Stop all applications
accessing the storage system and shut down hosts, if necessary.
Step 5. Upgrading controller software to XCS 09522000

CAUTION:
Stop all storage modification jobs (such as creation, deletion, presentation) 30 minutes before
beginning the controller software upgrade.
Before upgrading the controller software, ensure that the storage system configuration is stable
and is not being changed in any way. If any configuration changes are in progress, monitor them
using HP Command View EVA and wait until they are completed before proceeding with the upgrade.
Upgrading controller software

1.
Open HP Command View EVA in your browser.
2.
In the Storage Systems navigation pane, select the storage system you want to upgrade.
The properties window for the selected storage system opens.
55
3.
Click Code load.

The Code Load Selection window opens.
Figure 12 Code Load Selection window storage system

.
4.
Select Code Load Storage System and click Select.
5.
The Code Load Storage System Page 1 window opens.
Figure 13 Code Load Storage System-Page 1 window

.
6.
Click Browse, navigate to the installation CD (that was created from the download .ISO image.)
and select the appropriate file as shown in the following table.
Table 7 Controller software
56
For this array
Select
EVA4400
\HSV300\09522000\300_09522000.SSS
EVA6400
\HSV400\09522000\400_09522000.SSS
EVA8400
\HSV450\09522000\450_09522000.SSS
7.
Click Next Step.

The Code Load Storage System-Page 2 window opens listing any pre-update application notes.
Read them before continuing. Two confirmation screens appear. Respond to both by entering
YES (all uppercase) to proceed.
Figure 14 First code load confirmation screen

.
Figure 15 Second code load confirmation screen

.
8.
Click Next Step.

The new storage system software is copied to the controllers and validated.
57
9.
The upgrade process begins and the Initializing firmware code load page opens (see Figure 16).
This page is displayed until the upgrade is complete and the controllers restart. During this interval
both controllers resynchronize and begin operating on the new controller software. Once the
resynchronization is complete, the controllers begin processing host I/Os.
Figure 16 Initializing software code load

.
Next, additional code within the storage system is updated, which can take up to 10 minutes to
complete. This includes firmware on the I/O modules in the disk enclosures. During this interval,
the Storage System Updating Firmware window opens (see Figure 17).
Figure 17 Storage system updating software

.
IMPORTANT:
If you are doing an offline upgrade, the I/O modules must be reset after being upgraded.
Allow 30 minutes for the I/O module firmware upgrade to complete. Then, continue with
step 10. If you are doing an online upgrade, continue with step 12.
If you are doing an online upgrade, allow up to 20 minutes for the I/O modules to stabilize
device port operations. If there are any issues, see Verifying and resetting the I/O
module on page 59 for more information.
10. This step only applies for an offline upgrade. After 30 minutes, you must complete a power-off
reset of the storage system including all disk enclosures. You can either issue a power off from
HP Command View EVA or from the controller as follows:
a.
On the EVA4400, push and hold the enclosure power button on the rear of the controller
for a minimum of 4 seconds. The power button and the green LED start to blink when held
from 4 to 10 seconds.
On the EVA4400, while the power LED is blinking, release the power button. The button
continues to blink and the shutdown process completes.
If the EVA4400 does not perform a controlled shutdown, press and hold the power button
for 15 seconds. The power button turns amber when the array has shut down.
58
b.
On the EVA6400/8400, press and release the power button at the rear of the controller.
The power LED turns amber and the shut down process is complete.
c.
Press the power button on a disk enclosure and wait for it to shut down. Repeat this step for
each disk enclosure.
11. This step only applies for an offline upgrade. Power on the storage system:
a.
Power on the circuit breakers on both EVA rack power distribution units. Verify that all disk
enclosures are operating properly. The status indicator and the power indicator should be
on (green).
b.
Power on each controller (EVA6400/8400) or the controller enclosure (EVA4400).
c.
Allow the array to start up completely.
d.
Start HP Command View EVA and verify connection to the storage system. If the storage
system is not visible, click EVA Storage Network in the Navigation pane, and then click
Discover in the Content pane to allow HP Command View EVA to discover the array.
Verify the status of each host before enabling access.
12. On the Initialized Storage System Properties window, verify the version of the storage system
software in the Version box. It should be 09522000.
Figure 18 Verifying XCS version after upgrading

.
Verifying and resetting the I/O module

After the controller software upgrade completes (which includes upgrading I/O module firmware),
HP recommends that you verify the I/O module firmware upgrade was successful. To complete the
verification:
59
1.
In HP Command View EVA, go to the Hardware folder in the Navigation pane and select a disk
enclosure.
The Disk Enclosure Properties window opens.
2.
Select the I/O tab.
3.
Verify that 0073 displays in the Firmware revision field (for both I/O module A and B). See
Figure 19. If so, the upgrade was successful. If not, resetting the I/O module is recommended.
Figure 19 I/O tab of Disk Enclosure Properties window

.
In a few cases, it has been observed that some fields on the I/O tab of the Disk Enclosure Properties
window appear blank, specifically Hardware revision, Hardware type, and Assembly serial number
(see Figure 20). These blank fields do not affect I/O module operation and do not indicate that the
upgrade was unsuccessful. HP recommends that you wait 20 minutes to see if the situation corrects
itself. If not, you can reset the I/O module to populate these fields (optional).
60
Figure 20 Blank fields on I/O tab

.
To reset the I/O module:

You must reset one I/O module at a time.
Before each I/O module reset, check the I/O tab of the Disk Enclosure Properties window to ensure
there are no other exception conditions that may conflict with the reset. For example, if you want
to reset I/O module B, check that I/O module A is in an optimal state (and vice versa).
Wait at least one minute between resets.
There are two ways to reset the I/O module:
Remove and then re-insert the I/O module in each disk enclosure. See HP StorageWorks disk
enclosure I/O module replacement instructions for instructions. See Related information on page 81 for document location.
Insert a serial cable into the I/O module and issue the reset command via the serial line (requires
HP Services).
Step 6. Upgrading disk drive firmware

Estimated time to complete: Varies depending on the number of disk drives that require upgrading
and the I/O load on the storage system. It can take 30 seconds to 3.5 minutes per drive to upgrade
the firmware.
Review the following guidelines and tips before proceeding with the upgrade:
To verify disk drive firmware support with controller software, see HP StorageWorks disk drive
firmware support. See Related information on page 81 for document location.
Server-based management is required to upgrade the disk drive firmware.
Disks with Vraid0 cannot be upgraded online.
Although it is not required that the disk drive firmware be upgraded when the controller software
is upgraded, it is strongly recommended that you perform these tasks together. The disk drive
61
firmware complements the operation of the controller software and, for best results, the two should
be used together.
When upgrading many (more than about 20) disk drives online, a loop may fail; to reduce the
chance of such a loop failure, upgrade about 15 or 20 drives, then pause the activity for several
minutes by navigating away from the upgrade. Continue after a few minutes. To proceed after
such a pause, review the controller logs to establish where you are in the upgrade process and
relaunch the online upgrade. The upgrade will start where it left off.
CAUTION:
Observe the following cautions when upgrading disk drive firmware:
Do not power off any components or perform controller resynchs or reboots during an upgrade.
Do not perform HP Continuous Access EVA copy/merge activities across sites, site failovers,
cloning, or grouping or ungrouping of disks during an upgrade.
Do not add to or remove members from DR groups during upgrade.
Ensure that you upgrade the disk drive firmware after you upgrade the storage system software.
Perform your upgrade during times of low I/O to minimize the time it takes to revert information
back onto the drive after the upgrade.
If an error occurs during the upgrade, the process stops and must be restarted to upgrade disks
that have not yet been upgraded. Any disks that were upgraded before the error occurred do not
have to be upgraded again. Check the logs to verify status. When you restart the process, it starts
at the next disk that needs the upgrade.
Upgrading firmware on all disks

Upgrade the disk drive firmware after you upgrade the controller software.
1.
Validate that adequate free space is available to manage disk failures that might occur after the
disk firmware upgrade.
2.
Reduce EVA maintenance overhead by setting the disk replacement timer to five minutes. Reset
the value to the default (60 seconds) once the upgrade process is complete. The longer setting
prevents triggering migration and revert processes as disks are upgraded.
3.
If you have not already done so, download the HP StorageWorks EVA Hard Disk Drive Bundle
zip file from the following website:
http://www.hp.com/support/evadiskfirmware.
a.
Store the file to a known local directory. If you are running HP Command View EVA 9.x or
later, continue with step 4.
NOTE:
HP recommends that you use the default directory of C:\Program Files\
Hewlett-Packard\Sanworks\codeload. If you use a different directory, you
must enter the complete path when identifying the location of the firmware file.
b.
If you are running HP Command View EVA 8.x or earlier, unzip the bundled image file and
place the files in a directory where HP Command View EVA resides (HP recommends that
you use the default directory noted in Step 3a.)
Continue with step 4.
62
4.
Open and log into HP Command View EVA.
5.
In the Navigation pane, select the array for which you want to update hard disk drive firmware.
The Initialized Storage Systems Properties window opens.
6.
Click Code load.

The Code Load Selection window opens.
Figure 21 Code Load Selection window disk drives

.
7.
Select Code Load Disk Drives On Line and click Select.

The Code Load Disk Drives On Line - Page 1 window opens.
Figure 22 Code Load Disk Drives Page 1 window

.
8.
Do one of the following:

a.
If you are running HP Command View EVA 9.x or later, click Browse and navigate to the
zip file or manually enter the path to the zip file (from Step 3.a).
b.
If you are running HP Command View EVA 8.x or earlier, enter the path to the folder where
you extracted the bundled image files (from Step 3.b).
63
9.
Click Next step.

All disk drives are scanned for configuration information and upgrade eligibility. The results are
displayed in a table when the Online Disk Drive Code Load - Page 2 window opens.

.
64
10. Click Next step.

The disk drive firmware upgrade begins. A status page opens indicating the progress as each
disk drive is upgraded.
The disk drives are upgraded sequentially. Depending upon the I/O load on the storage system,
it can take 30 seconds to 3.5 minutes per drive to upgrade the firmware. The status is updated
at 45 second intervals, so you must wait to see which disk drives are complete.
CAUTION:
If you select any array in the Navigation pane to manage it, the disk drive upgrade stops.
For example, if 10 of 27 drives have completed the upgrade when you selected the array,
only those 10 drives will be upgraded. If you run a second disk drive upgrade, the Status
box on the Status window displays NO for the 10 drives that have been upgraded and the
remaining 17 drives are not upgraded.
Figure 24 Code Load Disk Drives status window

.
When all the disk drives have been upgraded, the Code Load Disk Drives On Line Page 3
window opens indicating the drives that have been upgraded successfully.
65

.
11. Click Finish.
Upgrading firmware on an individual disk

If it is necessary to upgrade the firmware on an individual disk, the firmware and installation instructions
can be downloaded from the following website:
http://www.hp.com/support/evadiskfirmware
IMPORTANT:
Upgrading disk drive firmware on an individual disk can be performed online or offline, unless the
disk is a member of a disk group that contains Vraid0 virtual disks. If so, the disk must be ungrouped
before the disk drive firmware can be upgraded.
Step 7. Entering storage system passwords

NOTE:
This step is required only if you use password protection on the storage system. Set the storage system
password by selecting Configure Administrator login options in the WOCP (EVA4400) or use the
OCP (EVA6400/8400).
Long passwords (up to 16 characters) are supported. The password must meet the following
requirements:
66
8 to 16 characters in length
Can include upper or lower case letters
Can include numbers 0 - 9
Can include the following characters: ! # $ % & ( ) * + , - . / : ; < = > ? @ [ ] ^ _ ` { | }
Cannot include the following characters: space ~ \
Enabling password access in HP Command View EVA

You must enable password access in HP Command View EVA. To enable password access to a
storage system, perform the following steps:
1.
Start HP Command View EVA in your browser.
2.
Click Agent Options in the Session pane.

The Management Agent Options window opens.
3.
Click Storage system password access.

The Storage System Password Access window opens.
4.
Click Enable.
The Enable Password Access to a Storage System window opens.
Figure 26 Enable Password Access to a Storage System window

.
5.
Select the World Wide Node Name of the storage system for which you want to enable password
access.
6.
Enter the password in the Password and Confirm password fields.
7.
Click Enable Password.

A message box opens.
8.
Click OK.
HP Command View EVA enables password access to the storage system.
Step 8. Resuming storage system operation

Estimated time to complete: Varies.
67
After the storage system software and disk firmware have been successfully upgraded, the storage
system can be returned to normal operation.
1.
Using HP Command View EVA, check the overall status of the storage system to ensure there are
no problems. For instructions on checking the status, see Step 1. Checking the health of the
Enterprise Virtual Array on page 51.
2.
If you did on offline upgrade, perform the following steps:

a.
Restart any host servers that were shutdown for the upgrade.
b.
Resume host I/Os.
3.
When running HP Continuous Access EVA, enable the failsafe mode on all data replication
groups. See Preparing an HP Continuous Access EVA environment for upgrading on page 45.
4.
If you changed any host LUN timeout values, reset them to their original values.
5.
If you are running Remote Support Software, enable it as follows:

a.
Save and clean the application eventlog file.
b.
On the HP Command View EVA management server, open a command window.
c.
Enter the following commands to restart Remote Support Software:

C:\>net start desta_service
d.
6.
Enter exit.
Update the MIB file after the upgrade to ensure SNMP notifications are captured correctly. See
Retrieving the Management Information Base in the HP StorageWorks Command View EVA
user guide for detailed instructions.
Task checklist
Use the following checklist to track your progress and mark when a task has been completed. You
can initial and timestamp task completion if you like.
Table 8 Upgrade task checklist
Task
Task complete
Step 1. Checking the health of the Enterprise Virtual Array, page 51

HP Command View EVA indicates no hardware problems
No hardware components in the Unmappable Hardware folder
No critical events entered in the controller event log within the last 48 hours
Storage system configuration is stable and no configuration changes have been made
within the last 48 hours
Step 2. Disabling Remote Support Software, page 54
Step 3. Clearing storage system passwords, page 54
68
Task
Task complete
Step 4. Halting all host access to the storage system for an offline upgrade, page 55
Time required: Varies by host. Must be performed for each host accessing the storage system
Halt all applications accessing the storage system.
Stop all I/O to the storage system.
Step 5. Upgrading controller software, page 55
Things you will need:
HP StorageWorks 09522000 controller software
Step 6. Upgrading disk drive firmware, page 61
Time required: Varies depending on the number of disk drives that must be upgraded. It
can take 30 seconds to 3.5 minutes per drive.
Step 7. Entering storage system passwords, page 66
Step 8. Resuming storage system operation, page 67
Time required: Varies
Restart applications accessing the storage system if an offline upgrade was performed.
When running HP Continuous Access EVA, enable failsafe mode on all DR groups.
If you changed any host LUN timeout values, reset them to their original values.
Enable Remote Support Software (if used).
69
70
4 Troubleshooting
This chapter provides troubleshooting information should you encounter any problems when updating
the system software. Each troubleshooting section is cross-referenced to the corresponding step in
Step 5. Upgrading controller software on page 55 where the problem is likely to occur.
Many of the common problems you may encounter are included. Contact your HP-authorized support
representative for help if this information does not help your problem.
The following troubleshooting topics are covered:
HP Command View EVA problems on page 71
Troubleshooting HP Command View EVA with a management server on page 72
Troubleshooting specific Command View EVA errors on page 72
View is not set or view list is null on page 72

HTTP status 404, not found or status 503, no service on page 73
Unknown storage system on page 74
No storage systems found on page 74
Solving security credentials configuration problems on page 75

Solving problems selecting a storage system (Step 2) on page 77
Solving problems disabling HP Continuous Access EVA DR group failsafe mode (Step
3) on page 78
Solving problems downloading the system software file (Step 6) on page 78
Invalid firmware image file (Status code 21006) on page 78
Bad image header (Status code 65) on page 79
Solving problems if the storage system does not come back online (Step 10) on page 79
Solving problems with multiple resyncs (Step 10) on page 80
Solving HP Command View EVA problems

There are a number of issues that may impact the operation of HP Command View EVA and its ability
to communicate with the storage system.
General HP Command View EVA troubleshooting tips

Use the following checklist to determine if there are problems with HP Command View EVA:
Has an HBA failed?
Has an EVA controller failed?
Have you set or reset the storage system password?
71
Troubleshooting HP Command View EVA with a management server

Use the following steps to isolate problems that may occur when using HP Command View EVA with
a management server:
1.
Check the EVA compatibility reference to ensure that the version of HP Command View EVA you
are using is compatible with the XCS version. For complete details on EVA software compatibility,
see the HP Command View EVA interoperability support table in the HP StorageWorks Enterprise
Virtual Array compatibility reference. See Required documentation on page 11 for the link to
this document.
2.
Ensure that the server and EVA is logged into the fabric.
3.
Select one of the following utilities to check the SAN Fibre Channel switch:
4.
HBAnywhere (Emulex)
SanSurfer (QLogic)
Clear the browser cache as follows.
a.
On the General tab under Temporary Internet files, click Settings.
b.
Click Every visit to the page under Check for newer versions of stored pages.
c.
On the General tab, under Temporary Internet files:
d.
i.
Click Delete Cookies.
ii.
Click Delete Files.
On the General Tab, under History, click Clear History.
5.
Ensure that HP Command View EVA is installed on the C:\ drive.
6.
Ensure that the folder C:\Program Files\Compaq\SANworks\Element Manager for

StorageWorks HSV\HSV300 exists.
Troubleshooting specific HP Command View EVA errors

This section describes specific Storage Management Appliance/HP Command View EVA errors:
View is not set or view list is null, page 72

HTTP status 404, not found or status 503, no service, page 73
Unknown storage system, page 74
No storage systems found, page 74
View is not set or view list is null

Symptom
The HP Command View EVA content pane shows an Operation Failed message with Details:
View Is Not Set or View List Is Null.
Cause
HP Command View EVA cannot build the view of the storage system.
72
Troubleshooting
Resolution
Click OK. Wait one to five minutes, depending on the size of the storage system, and try the command
generating this message again. If you still cannot see the storage system, stop and restart HP Command
View EVA.
HTTP status 404, not found or status 503, no service

Symptom
The content pane shows an HTTP Status 404, Not Found or HTTP Status 503, No
Service message.
Cause
These messages indicate that the server responded, but it could not find the page being requested.
HTTP errors, including 404 and 503, originate from the web server, the HTTP server, or the appliance.
Even when HP Command View EVA cannot respond, the web server continues to respond to HTTP
requests from a browser.
During normal interaction between HP Command View EVA and the web server:
1.
2.
3.
4.
A browser requests an HP Command View EVA page.

The web server passes the request for the page to HP Command View EVA.
HP Command View EVA responds with the page.
The web server sends it to the browser.
These errors indicate that a problem is occurring with this normal interaction. Table 9 lists some
possible causes of these errors and their corrective actions.
Resolution
Table 9 Possible causes and corrective actions for HTTP 404 and HTTP 503 errors
Possible Cause
Corrective Action
404 Error: HP Command View EVA may be initializing

when a browser makes a request. The web returns a 404
(Page Not Found) error because it cannot get the page.
Retry the request by clicking the Refresh/Reload button on the browser.
404 Error: A .frm (HTML) file may be missing in the HP

Command View EVA directory structure. This can occur
if the files were changed or if the HP Command View
EVA installation went amiss.
Reinstall HP Command View EVA.
503 Error: HP Command View EVA may be down when

a browser makes a request. The web server returns a 503
(No Service) error because it cannot access the page.
Retry the request when HP Command View

EVA is up.
Browser timeout: The appliance may be down or the web

server may be unavailable when a browser makes a request to HP Command View EVA. In this case, the browser
will time out internally.
Retry the request when the appliance and HP

Command View EVA are up.
73
Unknown storage system

Symptom
HP Command View EVA reports an unknown storage system for a storage system that should be
displayed.
Cause of the error
HP Command View EVA may have lost communication with the controllers. Two possible scenarios
are:
The HBA in the management server may have timed out commands to the controllers. See Unknown
storage systemcause 1 on page 74 below.
The controllers are running a version of XCS that HP Command View EVA does not recognize.
See Unknown storage systemcause 2 on page 74.
Unknown storage systemcause 1
When the fabric is heavily loaded, the FC adapter in the management server may time out commands
to the controllers. If this occurs, the storage system appears in the Unknown state.
Corrective Action for Unknown Storage SystemCause 1
This scenario should correct itself in less than one minute. Alternately, you can perform a Rediscover
operation to initiate new commands to the controller.
Unknown storage systemcause 2
HP Command View EVA can only manage controllers that are running supported XCS versions.
Corrective Action for Unknown Storage SystemCause 2
Ensure that you are running the HP Command View EVA version that is compatible with XCS
09522000. See the HP Command View EVA interoperability support table in the HP StorageWorks
Enterprise Virtual Array compatibility reference to determine which version of HP Command View
EVA you should be running. Then, upgrade HP Command View EVA to a compatible version. See
Required documentation on page 11 for the link to this document.
No storage systems found

Symptom
HP Command View EVA does not display any storage systems, even though they are on the fabric.
Cause of the error
Several conditions can cause this symptom. Table 10 lists some possible causes of these errors and
their corrective actions.
74
Troubleshooting
Corrective action
Table 10 Possible causes and corrective actions when no storage system found
Possible Cause
Corrective Action
The management server may not be able to

communicate with either controller.
Check the connection configuration between the management server and

the controller pair. The management server must have a communication
path to both controllers in case one controller loses communications with
the server.
When HP Command View EVA is first starting

up, a password may be enabled on the controllers, but a password has not been entered
in HP Command View EVA.
Enter the correct password through HP Command View EVA or disable

the password on the controller.
The switches may not be correctly zoned,

making a storage system invisible to HP
Command View EVA.
Verify that switches are zoned correctly.
HP Command View EVA may have been restarted while there was a communication
failure between HP Command View EVA and
the controllers. When restart is completed,
the storage system that lost communication
will not be visible.
A storage system may not be visible to HP
Command View EVA because the controllers
are waiting for World Wide ID (WWID) to
be entered. This condition will occur if the
storage system has been uninitialized and
the cabinet is power cycled.
1.
Verify that the controllers are up and functioning properly.
2.
Check the cable connections between the management server and

the switch.
3.
Verify that switch zoning is correct.
4.
Click Discover.
Enter the WWID.
This may also occur if backend problems are

preventing access to the quorum drives. Once
communication is restored, the WWID along
with the checksum can be re-entered.
Solving security credentials configuration problems

The following Windows-based security groups are required on the management server:
NOTE:
Group names are case sensitive.
HP Storage Admins. To access all the features of HP Command View EVA, this security group is
required on the management server and must have at least one member (user account). Members
have view and manage capabilities.
HP Storage Users. Members have view capability only. This group is required only when a group
with extremely limited use of HP Command View EVA is required.
75
Access control
1.
The user's security group is checked to control access to various functions and web pages with
HP Command View EVA.
2.
If the user belongs to the HP Storage Admins group, access is granted.
3.
If the user belongs to the HP Storage Users group and the web page allows access to users with
the View HP Storage privilege, access is granted.
4.
If the user belongs to the HP Storage Users group and the web pages does not allow access to
users with the View HP Storage privilege, access is denied.
Troubleshooting disk drive firmware upgrade

Table 11 on page 76 lists the errors you may encounter when upgrading the disk drive firmware and
provides workarounds.
Table 11 Disk drive firmware upgrade errors and workarounds
Error
Workarounds
Drive code load - Failed to write firmware to drive buffer
Check the drive properties in the HP Command View

EVA GUI for problems. Resolve the problem and restart
the disk drive firmware upgrade.
Drive code load - The disk cannot be

code loaded because it is part of a
group
Restart the disk drive firmware upgrade.
Drive code load - The disk group containing the physical store has background
reconstructing or reverting in progress
Reduce the I/O as per the I/O recommendation given

for the online disk drive firmware upgrades and restart
Drive code load - Unable to determine

the condition of the volume

Media Not Available
This error may appear if the code load occurs while

the array is experiencing a heavy I/O load. Restart
Drive code load - Unable to determine

the condition of the physical store

EVA GUI to see if the drive has any problems. Resolve
the drive problems and restart the disk drive firmware
upgrade.
Unable to process command at this time.

Retry the command or check all connections
Check for any possible connection issues between HP

Command View EVA software and the EVA, and restart the disk drive firmware upgrade.
Failed - Successful Status
Object not found in View
Check for any possible connection issues between HP

Command View EVA software and the EVA, and restart the disk drive firmware upgrade.
76
Troubleshooting
Drive code load - The StorageCell is in

device discovery, and the requested operation cannot be served
Invalid Target Handle

Not a supported version
Restart the HP Command View EVA service and retry

The disk cannot be code loaded because

disk is part of a RAID0 group.
Remove disks that contain RAID0 data from the group

and restart the disk drive firmware upgrade.
Solving problems selecting a storage system

When selecting a storage system, ensure the status icon displayed for the storage system is a green
cluster symbol indicating good health. See Figure 27.
Figure 27 Status icon for a good storage system

.
If the status icon for the storage system is not green, it indicates a problem that must be corrected
before proceeding. Expand the navigation tree to locate the problem. Figure 28 illustrates a storage
system with a disk enclosure problem.
77
Figure 28 Status icon for a bad storage system

.
Solving problems disabling DR group failsafe mode

There are a number of issues that may occur with HP Continuous Access EVA. The following website
provides access to information for troubleshooting problems with HP Continuous Access EVA:
http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?&lang=en&cc=us&
prodTypeId=18964&prodSeriesId=471572&lang=en&cc=us
Click Troubleshoot a problem under Tasks for HP StorageWorks Continuous Access EVA Software.
Solving problems downloading the system software file

If you cannot download the system software file, right-click the link and save it to your desktop. Then
double-click the saved file on the desktop, which opens a window with the link to the file. Click the
link and save it to a directory.
NOTE:
The XCS image filename has an extension of .sss. The file name contains the controller model and
the XCS version. For example, 300_09522000.SSS is the name of the XCS 09522000 file for the
HSV300 and HSV300S controllers. See Table 7 for details.
Invalid image file (Status code 21006)

If the XCS image file is the wrong image, an Operation failed message is displayed. See Figure 29.
Click OK to return to the Initialized Storage System Properties window.
78
Troubleshooting
Figure 29 Invalid image file (Status code 21006)

.
Bad image header (Status code 65)

HP Command View EVA sends the XCS controller software to the controller in segments. As each
segment is received, it is validated by the controller. HP Command View EVA monitors each segment
transfer and displays the transfer status information.
If a problem occurs, the process stops and HP Command View EVA displays the segment transfer that
was not successful. This is typically caused by a problem in the XCS controller software image file or
selection of the wrong image file. See Figure 30. If this error occurs, do the following:
1.
Click OK to return to the Initialized Storage System Properties window.
2.
Click Code load to begin the controller software upgrade again.
3.
Ensure that you select the correct image file, and continue the process.
If the process fails again with the same message, download the image file again and repeat the
process.
Verify that the correct name was selected. For the list of current image files, see Table 7.
Figure 30 Bad image header (Status code 65)

.
Solving problems if the storage system does not come back

online
The controller software upgrade should take approximately 10 minutes to complete. If the storage
system does not come back within 10 minutes, check the following:
Determine if the problem is with HP Command View EVA by performing the troubleshooting steps
in HP Command View EVA problems on page 71.
79
Check any WEBES messages.

1. Double click on the System Event Analyzer icon on the management server to run WEBES.
2.
Click Full View under either System Log or the appropriate storage system in the left navigation
pane.
Check the storage system event logs.

1. Run HP Command View EVA and log in.
2.
Select the storage system whose logs you want to view.
3.
Click View events to view the event logs that can be displayed.
If none of the above recommendations resolves the problem, contact your HP-authorized service
representative for help.
Solving problems with multiple resynchronizations

During the upgrade process, both controllers perform a resynchronization simultaneously. This invokes
a fast restart of the controllers bypassing execution of lengthy hardware diagnostics. This fast restart
allows the controllers to complete the resynchronization sequence before the host timeout period
elapses and the host becomes aware that the storage system is unavailable.
If an event occurs that causes a second resynchronization while the upgrade resynchronization is still
in progress, the controller will terminate with a code of 0b 08 01 00. The following events cause
the controller to resysnchronize automatically:
Initialization of the storage system
Setting debug flags through the command line interface or WOCP
Disk group hardware problem on a Vraid1 virtual disk, or attempted re-connection of a disk when
there is a disk group hardware problem
Bad Block Replacement (BBR) performed on a disk
Memory allocation failure or other errors
Every effort should be made to ensure that none of these events occur during the upgrade process. If
controller termination occurs due to multiple resynchronizations, contact your HP-authorized service
representative for assistance.
80
Troubleshooting
5 Support and other resources

Contacting HP
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support website:
http://www.hp.com/support/
Collect the following information before calling:
Product model names and numbers
Technical support registration number (if applicable)

Product serial numbers
Error messages
Operating system type and revision level
Detailed questions
Subscription service
HP recommends that you register your product at the Subscriber's choice for business website:
http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, please send a message to:
storagedocsfeedback@hp.com. All submissions become the property of HP.
Related information
Documents
For documents referenced in this guide, see the Manuals page on the Business Support Center website:
In the Storage section, click Disk Storage Systems or Storage Software, and then select your product.
81
Websites
HP:
http://www.hp.com
HP Storage:
http://www.hp.com/go/storage
HP Partner Locator:
http://www.hp.com/service_locator
HP Software Downloads:
http://www.hp.com/support/downloads
HP Software Depot:
http://www.software.hp.com
HP Single Point of Connectivity Knowledge (SPOCK):
http://www.hp.com/storage/spock
Typographic conventions
Table 12 Document conventions
Convention
Element
Medium blue text: Table 12
Cross-reference links and email addresses
Medium blue, underlined text: http://

www.hp.com
Website addresses
Keys that are pressed
Bold text
Italic text
Text typed into a GUI element, such as into a box

GUI elements that are clicked or selected, such as menu and list items,
buttons, and check boxes
Text emphasis
File and directory names
Monospace text
System output
Code
Commands, their arguments, and argument values
Monospace, italic text

Monospace, bold text
Code variables
Command variables
Emphasized monospace text
.
.
Indication that the example continues.
WARNING!
82
Support and other resources
An alert that calls attention to important information that if not understood

or followed can result in personal injury.
Convention
Element
CAUTION:
An alert that calls attention to important information that if not understood

or followed can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT:
An alert that calls attention to essential information.
NOTE:
An alert that calls attention to additional or supplementary information.
TIP:
An alert that calls attention to helpful hints and shortcuts.
83
84
Support and other resources
Index
A
agent options, using, 54
analyzing storage system I/O, 27
array
checking for errors, 17, 51
B
backup, 36
Bad image header error, 79
browsers
recommended versions, 42
HP Command View EVA

checking hardware, 18, 52
disabling passwords, 54
installing, 37
online help, 17
upgrading, 37
web server interaction, 73
HP technical support, 81
I
installation
typical, 37
Invalid firmware image file error, 78
checking
hardware status, 18, 52
cluster symbol, 77
code load restrictions, 45
collecting configuration data, 19
controller events
checking log, 53
Controller Events page, 44, 53
corrective action codes, 44, 53
critical event check, 53
Management Agent Options page, 54

management appliance
interaction with HP Command View EVA, 73
troubleshooting errors, 72
management module software, 12
Disable Password Access to Storage System

page, 55
documentation
providing feedback, 81
E
EVA health check, 18
EVAPerf, 27
H
hardware errors, 18, 52
help
obtaining, 81
host I/O timeouts, managing, 31
JRE, recommended versions, 42
K
kits
required, 12
software, 12
O
OCP
adding passwords, 66
clearing passwords, 54
online upgrade
managing host I/O timeouts, 31
P
password protection, 66
85
R
Replication Solutions Manager, 43
RSM
See Replication Solutions Manager
S
SAN Visibility, 19
selecting online upgrade time, 27
software, 12
status code
21006, 78
65, 79
storage system
passwords, 67
T
technical support
HP, 81
time estimate
adding passwords, 66
clearing passwords, 54
disabling password access, 54
troubleshooting
HP Command View EVA errors, 72
management appliance errors, 72
U
unmappable hardware folder, 18, 52
upgrade preparation, 18, 51
upgrading
HP Command View EVA, 37
Replication Solutions Manager, 43
V
VCS
minimum version before upgrade, 12
verifying software version, 16
View Events page, 44, 53
W
web server, 73
World Wide Node Name, 67
WWN, 67
86

Eva Upgrade

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Eva Upgrade

Cargado por

Copyright:

Formatos disponibles

HP StorageWorks Enterprise Virtual Array

updating product software guide (XCS

Part Number: 576287-003

Legal and notice information

2 Pre-upgrade tasks ............................................................................ 15

Upgrading browsers and JREs ....................................................................................................

3 Upgrading the Enterprise Virtual Array ................................................ 51

5 Support and other resources .............................................................. 81

Evaluate your configuration

XCS 09522000 upgrade considerations

HP StorageWorks EVA documentation

HP StorageWorks Enterprise Virtual

Click Disk Storage Systems under Storage,

HP Command View EVA documentation

Click Storage Software under Storage, and

HP StorageWorks EVA replication software documentation

HP StorageWorks Continuous Access EVA implementation guide

Click Storage Networking under Storage,

Link your support agreement(s) to your ITRC user ID at http://www.itrc.hp.com/service/

Select the appropriate Support Agreements or select All Support Agreements.

If you have questions or require additional assistance go to: http://welcome.hp.com/country/us/en/

Checking current controller software version

Open HP Command View EVA.

Checking current software versions

Locating version information1

Open HP Command View

Upgrading HP Command View

Click Help in the Session pane.

Open or browse to HP StorageWorks Replication Solutions

Select Help > About in the

Open Windows control panel.

Double-click the Java icon.

On the General tab, click

Upgrading browser and Java

The version of Java is displayed.

From your browser, select Help >

Upgrading browser and Java

Checking the HP Command View EVA version

Figure 1 EVA Storage Network Properties window

Click Help in the Session pane.

Figure 2 HP Command View EVA online help

Checking the storage system hardware

Click the Hardware folder to expand the navigation tree.

Figure 3 Hardware Folder Properties window

Figure 4 Checking operational state

Click the Unmappable Hardware folder.

Replace any hardware components that have failed.

Checking and upgrading your SAN infrastructure

Collecting SAN configuration data using SAN Visibility

Installing SAN Visibility

Double-click the downloaded file to launch the installation.

Follow the on-screen instructions to install the software.

Using SAN Visibility

Double-click the SAN Visibility icon on the desktop.

Click OK to view the SAN Settings window.

Select SAN Settings and enter the following information:

Click Yes to confirm the name change.

Click Yes to confirm the name change.

Click Switch Settings and enter the following information:

Click Add to add the switch to the reporting configuration.

Select Customer Details and enter the following information:

Enter your name in Name. This information is required.

Click Next to save and proceed.

Obtaining a report from HP