update 6200 firmware

HP StorageWorks 4x00/6x00/8x00Enterprise Virtual Array updating productsoftware guide (XCS 6.200)This document applies to the EVA4000/6000/8000 and EVA4100/6100/8100 models only.

Part number: 5697-7368First edition: June 2008

Legal and notice information

© Copyright 2005, 2008 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 forthin the express warranty statements accompanying such products and services. Nothing herein should be construed as constitutingan additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Java is a US trademark of Sun Microsystems, Inc.

Contents

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . 7Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Product models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8HP websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . 11Upgrade paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Online versus offline upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Required kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Pre-upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . 13Checking current software versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Checking the HP Command View EVA version . . . . . . . . . . . . . . . . . . . . . . . 16Checking the storage system hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Checking and upgrading your SAN infrastructure . . . . . . . . . . . . . . . . . . . . . . . . 18

Collecting SAN configuration data using SAN Visibility . . . . . . . . . . . . . . . . . . . 18Installing SAN Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Using SAN Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Creating a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Reading the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Selecting an appropriate time to perform an online upgrade . . . . . . . . . . . . . . . . . . . 25Analyzing storage system I/O using HP Command View EVAPerf . . . . . . . . . . . . . . . 25

Tips for using HP Command View EVAPerf . . . . . . . . . . . . . . . . . . . . . . . 26HP Command View EVAPerf command options . . . . . . . . . . . . . . . . . . . . . 26Running HP Command View EVAPerf . . . . . . . . . . . . . . . . . . . . . . . . . 26Displaying EVA performance data using Windows Performance Monitor . . . . . . . . . . 29

Managing host I/O timeouts for an online upgrade . . . . . . . . . . . . . . . . . . . . . . . 29Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Checking timeout values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Default timeout values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Checking timeout values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Changing timeout values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Checking or changing timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Tru64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31OpenVMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Checking or changing timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Managing application I/O timeouts for an online upgrade . . . . . . . . . . . . . . . . . . . . 32Back up all storage system data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Upgrading HP Command View EVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Upgrading using the typical installation . . . . . . . . . . . . . . . . . . . . . . . . . . 33Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

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

HP StorageWorks 4x00/6x00/8x00 Enterprise Virtual Array updating product software guide (XCS 6.200) 3

Upgrading to WEBES 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Archiving and clearing the error log . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Upgrading WEBES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Upgrading HP Replication Solutions Manager (optional) . . . . . . . . . . . . . . . . . . . . . 36Monitoring storage system stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Preparing an HP Continuous Access EVA environment for upgrading . . . . . . . . . . . . . . . 37

Upgrading disk drive firmware in an HP Continuous Access EVA environment . . . . . . . . . . 38Saving storage system configuration information . . . . . . . . . . . . . . . . . . . . . . . . 38

3 Upgrading the Enterprise Virtual Array . . . . . . . . . . . . . . . . 41Upgrading remotely versus locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Solving upgrade problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Step 1. Checking the health of the Enterprise Virtual Array . . . . . . . . . . . . . . . . . . . . 42Step 2. Disabling ISEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Step 3. Clearing storage system passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Clearing the password on the Operator Control Panel (OCP) . . . . . . . . . . . . . . . . . 45Disabling password access in HP Command View EVA . . . . . . . . . . . . . . . . . . . 46

Step 4. Halting all host access to the storage system for an offline upgrade (optional) . . . . . . . . 46Step 5. Upgrading controller firmware to XCS 6.200 . . . . . . . . . . . . . . . . . . . . . . 46

Upgrading controller firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Step 6. Upgrading disk drive firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Upgrading the firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Upgrading firmware on an individual disk . . . . . . . . . . . . . . . . . . . . . . . . . 55

Step 7. Entering storage system passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Entering the password on the OCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Enabling password access in HP Command View EVA . . . . . . . . . . . . . . . . . . . 56

Step 8. Resuming storage system operation . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 Downgrading the Enterprise Virtual Array . . . . . . . . . . . . . . 59

5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 61Solving HP Command View EVA problems (Step 1) . . . . . . . . . . . . . . . . . . . . . . . 61

General HP Command View EVA troubleshooting tips . . . . . . . . . . . . . . . . . . . . 61Troubleshooting HP Command View EVA with the Storage Management Appliance (SMA) . . . . 61Troubleshooting HP Command View EVA with a management server . . . . . . . . . . . . . 62Troubleshooting specific HP Command View EVA errors . . . . . . . . . . . . . . . . . . . 62

View is not set or view list is null . . . . . . . . . . . . . . . . . . . . . . . . . . . 63HTTP status 404, not found or status 503, no service . . . . . . . . . . . . . . . . . . 63Unknown storage system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64No storage systems found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Solving security credentials configuration problems . . . . . . . . . . . . . . . . . . . . . 65Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Solving problems selecting a storage system (Step 2) . . . . . . . . . . . . . . . . . . . . . . 66Solving problems disabling DR group failsafe mode (Step 3) . . . . . . . . . . . . . . . . . . . 67Solving problems downloading the system software file (Step 6) . . . . . . . . . . . . . . . . . . 67

Invalid firmware image file (Status code 21006) . . . . . . . . . . . . . . . . . . . . . . 67Bad image header (Status code 65) . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Solving problems if the storage system does not come back online (Step 10) . . . . . . . . . . . . 68Solving problems with multiple resynchronizations (Step 10) . . . . . . . . . . . . . . . . . . . 69

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4

Figures1 HSV Storage Network Properties page . . . . . . . . . . . . . . . . . . . . . . . 16

2 HP Command View EVA Online Help . . . . . . . . . . . . . . . . . . . . . . . 17

3 Hardware Folder Properties window . . . . . . . . . . . . . . . . . . . . . . . . 17

4 Checking operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5 SAN Visibility management page . . . . . . . . . . . . . . . . . . . . . . . . . 20

6 Sample SAN Visibility report . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7 Sample virtual disk statistics display . . . . . . . . . . . . . . . . . . . . . . . . 28

8 Windows Performance Monitor display . . . . . . . . . . . . . . . . . . . . . . 29

9 Controller Events (Initialized system) window . . . . . . . . . . . . . . . . . . . . 37

10 Hardware Folder Properties window . . . . . . . . . . . . . . . . . . . . . . . . 43

11 Checking operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

12 Controller Events (Initialized system) page . . . . . . . . . . . . . . . . . . . . . 44

13 Code Load Storage System-Page 1 window . . . . . . . . . . . . . . . . . . . . . 47

14 Code Load Storage System-Page 2 window . . . . . . . . . . . . . . . . . . . . . 48

15 Validating code segments complete . . . . . . . . . . . . . . . . . . . . . . . . 49

16 Initializing firmware code load . . . . . . . . . . . . . . . . . . . . . . . . . . 50

17 Storage system updating firmware . . . . . . . . . . . . . . . . . . . . . . . . . 50

18 Verifying XCS version after upgrading . . . . . . . . . . . . . . . . . . . . . . . 51

19 Code Load Selection window — disk drives . . . . . . . . . . . . . . . . . . . . 5220 Code Load Disk Drives — Page 1 window . . . . . . . . . . . . . . . . . . . . . 53

21 Code Load Disk Drives — Page 2 window . . . . . . . . . . . . . . . . . . . . . 53

22 Code Load Disk Drives — status window . . . . . . . . . . . . . . . . . . . . . . 5423 Code Load Disk Drives — Page 3 window . . . . . . . . . . . . . . . . . . . . . 55

24 Enable Password Access to a Storage System window . . . . . . . . . . . . . . . . 57

25 Status icon for a good storage system . . . . . . . . . . . . . . . . . . . . . . . 66

26 Status icon for a bad storage system . . . . . . . . . . . . . . . . . . . . . . . . 67

27 Invalid firmware image file (Status code 21006) . . . . . . . . . . . . . . . . . . . 68

28 Bad image header (Status code 65) . . . . . . . . . . . . . . . . . . . . . . . . 68


Tables1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 XCS 6.200 Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 XCS 6.200 Pre-upgrade task checklist . . . . . . . . . . . . . . . . . . . . . . . 13

5 Management software version worksheet . . . . . . . . . . . . . . . . . . . . . . 15

6 HP Command View EVAPerf virtual disk statistics . . . . . . . . . . . . . . . . . . 287 IBM AIX timeout settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

8 HP Command View EVA upgrade paths . . . . . . . . . . . . . . . . . . . . . . 33

9 Upgrade task checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

10 System software code segment descriptions . . . . . . . . . . . . . . . . . . . . . 49

11 Possible causes and corrective actions for HTTP 404 and HTTP 503 errors . . . . . . . . 6312 Possible causes and corrective actions when no storage system found . . . . . . . . . . 65

6

About this guide

This guide provides information to help you:

• Upgrade the Enterprise Virtual Array controller firmware and disk drive firmware• Upgrade supporting components, such as HP Command View EVA and other management

software

This guide does not provide information about upgrading or changing the Enterprise Virtual Arrayhardware.

NOTE:The procedures in this guide are for upgrading from XCS 5.1xx, 6.000, 6.100 or 6.110 to XCS 6.200.

IMPORTANT:To upgrade from an HSV200-A or HSV210-A controller to an HSV200-B or HSV210-B controller, HPrequires that you also upgrade the I/O modules (A and B) to AD623C and AD624C on each shelf. Ifyou are upgrading to an EVA6100 (HSV200-B) or EVA8100 (HSV210-B) and you do not already havethe 30-10022-01 loop switches installed, you must also upgrade the loop switches to 30-10022-01. Seethe HP StorageWorks 4x00/6x00/8x00 Enterprise Virtual Array user guide for more information.

Intended audienceThis guide is intended for use by Enterprise Virtual Array customers involved in upgrading system softwareon EVA4x00/6x00/8x00 storage systems. You should have experience with the following:

• Enterprise Virtual Arrays• Storage area networks• HP Command View EVA• HP Command View EVAPerf (used for online upgrades)

Product modelsThis guide includes information for the following Enterprise Virtual Array products:

• EVA4000/6000/8000• EVA4100/6100/8100

These arrays are referenced as EVA4x00/6x00/8x00 throughout the document.


Document conventions and symbolsTable 1 Document conventions

Convention Element

Medium blue text: Requireddocumentation Cross-reference links and e-mail addresses

Medium blue, underlined text(http://www.hp.com) Website addresses

Bold font

• Key names• 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

Italic font Text emphasis

Monospace font

• File and directory names• System output• Code• Text typed at the command line

Monospace, italic font• Code variables• Command-line variables

Monospace, bold font Emphasis of file and directory names, system output, code, and texttyped at the command line

CAUTION:Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT:Provides clarifying information or specific instructions.

NOTE:Provides additional information.

TIP:Provides helpful hints and shortcuts.

HP technical supportTelephone numbers for worldwide technical support are listed on the HP support website:http://www.hp.com/support/.

Collect the following information before calling:

• Technical support registration number (if applicable)• Product serial numbers• Product model names and numbers• Error messages

8 About this guide

http://www.hp.com

http://www.hp.com/support/











• Operating system type and revision level• Detailed questions

For continuous quality improvement, calls may be recorded or monitored.

HP websitesFor additional information, see the following HP websites:

• http://www.hp.com• http://www.hp.com/go/storage• http://www.hp.com/service_locator• http://www.hp.com/support/manuals• http://h20293.www2.hp.com

Documentation feedbackHP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message to: . Allsubmissions become the property of HP.


http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com

http://www.hp.com/go/storage












http://www.hp.com/service_locator









http://www.hp.com/support/manuals












http://h20293.www2.hp.com






10 About this guide

1 Getting started

This chapter provides information about required kits and reference documentation. Ensure that youhave met the outlined requirements and possess all of the required materials before you begin theinstallation procedures described in this guide.

Upgrade pathsThe XCS 6.200 upgrade paths are shown in Table 2.

Table 2 XCS 6.200 Upgrade Paths

Current XCS Version Upgrade Path to XCS 6.200 Upgrade type

6.110 Upgrade directly to 6.200 Online or offline



5.110 Upgrade to 6.110 and then to 6.200 Online or offline

5.100 Upgrade to 6.110 and then to 6.200 Online or offline

5.0xx Contact HP Services for upgrade information if you are runningthese versions.

Online versus offline upgradesOnline upgrade to XCS 6.200 is supported from XCS 6.110, 6.100, and 6.000. An online upgrade doesnot require you to halt I/O or shut down the servers accessing the storage system. Because of the minimaldisruption to system operation, the online procedure is recommended. It will be necessary to identify thebest time to perform the upgrade to minimize the impact on hosts and applications.

If necessary, the upgrade can be performed offline. For an offline upgrade, you must stop all host I/O tothe storage system. Stop all applications accessing the storage system and shut down hosts, if necessary.

Reference documentationTable 3 identifies the documentation you should have available when upgrading the storage system.

Table 3 Reference documentation

Document Required? Location

HP StorageWorks EVA documentation

HP StorageWorks 4x00/6x00/8x00Enterprise Virtual Array user guide

HP StorageWorks 4x00/6x00/8x00Enterprise Virtual Array release notes Yes

HP StorageWorks 4x00/6x00/8x00Enterprise Virtual Array connectivity6.2A or later release notes. There is aseparate document for each supportedoperating system.

Yes


Click Disk Storage Systems under Storage, and thenselect either HP StorageWorks 4000/6000/8000Enterprise Virtual Arrays or HP StorageWorks4100/6100/8100 Enterprise Virtual Arrays underEVA Disk Arrays.



Document Required? Location

HP StorageWorks Enterprise VirtualArray compatibility reference Yes

HP Command View EVA documentation

HP StorageWorks Command View EVAuser guide

HP StorageWorks Command View EVAinstallation guide Yes

HP StorageWorks Storage SystemScripting Utility reference


Click Storage Software under Storage, and thenselect HP StorageWorks Command View EVASoftware under Storage Device ManagementSoftware.

HP StorageWorks EVA replication software documentation

HP StorageWorks Replication SolutionsManager installation guide

HP StorageWorks Replication SolutionsManager administrator guide

HP StorageWorks Continuous AccessEVA administrator guide

HP StorageWorks JREserver installationinstructions


Click Storage Software under Storage, and thenselect HP StorageWorks Continuous Access EVASoftware under Storage Replication Software.

SAN infrastructure documentation

HP StorageWorks SAN DesignReference Guide Yes


Click Storage Networking under Storage, andthen select HP StorageWorks SAN under HPStorageWorks SAN Solutions.

Required kitsBefore you begin the Enterprise Virtual Array upgrade, you must download the 6.2 controller software(XCS 6.200) from the following website:

http://h20293.www2.hp.com/

Click Storage and NAS under Product category, and then select the HP EVA XCS 6.200 ElectronicDownload.

NOTE:HP Command View EVA 8.0.1 is required with XCS 6.200.

12 Getting started












2 Pre-upgrade tasks

There are a number of necessary tasks that can be performed prior to beginning the upgrade. Performingthese tasks prior to, rather than during, the upgrade minimizes the time required to perform the XCSupgrade procedure.

The required tasks differ depending on your system configuration. They focus on upgrading componentsto ensure they meet the supported configuration for XCS 6.200. Table 4 provides a checklist so youcan track your progress as you perform these pre-upgrade tasks.

Table 4 XCS 6.200 Pre-upgrade task checklist

Checking current software versions, page 15Time required: 10–15 minutesWhen to perform: Any time prior to the upgrade– Check versions of all applicable installed management software.

Checking the storage system hardware, page 17Time required: 15–20 minutesWhen to perform: 1–2 weeks prior to the upgrade. Provide enough time to order and replace any failedcomponents.– Check hardware status using HP Command View EVA.– Check hardware components in the Unmappable Hardware folder.– Replace hardware as needed.

Checking and upgrading your SAN infrastructure, page 18Time required: Varies depending on how many hardware and software components require replacementor upgradeWhen to perform: Any time prior to the upgradeThings you will need:• Connectivity release notes. See “Required documentation” on page 11.• SAN Visibility tool. See “Collecting SAN configuration data using SAN Visibility” on page 18– Verify all host HBAs and drivers are supported.– Verify Fibre Channel switch firmware is supported.– Upgrade unsupported components as necessary.

Selecting an appropriate time to perform an online upgrade, page 25Time required: Varies depending on how long it will take to gather I/O dataWhen to perform: Any time prior to the upgrade– Run HP Command View EVAPerf to gather I/O data.– Analyze data to identify a time period that meets the I/O criteria.

Managing host I/O timeouts for an online upgrade, page 29Time required: Varies depending on number of hostsWhen to perform: Any time prior to the upgrade– Determine if any host LUN timeouts have been changed from their defaults.– Reset any changed LUN timeout parameters to a minimum of 60 seconds.

Managing application I/O timeouts for an online upgrade, page 32Time required: Varies depending on number of applicationsWhen to perform: Any time prior to the upgrade– Determine if any applications have timeouts set to more stringent values than the host LUN timeouts.– Change application timeout parameters to host LUN timeout values.


Upgrading HP Command View EVA, page 32Time required: 15–20 minutesWhen to perform: Any time prior to the upgradeThings you will need:• HP StorageWorks Command View EVA 8.0.1 installation media– Check the HP Command View EVA version.– Upgrade to version 8.0.1 if necessary.

Upgrading browser and Java Runtime Environment (JRE), page 34Time required: 10–20 minutesWhen to perform: Any time prior to the upgrade– Upgrade browser if necessary.– Upgrade JRE if necessary.

Upgrading to WEBES 5.2, page 34Time required: 10–20 minutesWhen to perform: Any time prior to the upgradeThings you will need:• WEBES 5.2 and upgrade documentation available from the following website:

http://h18023.www1.hp.com/support/svctools/webes/index.html– Upgrade to WEBES 5.2 if necessary

Upgrading HP Replication Solutions Manager (optional), page 36Time required: 10–20 minutesWhen to perform: Any time prior to the upgradeThings you will need:• HP StorageWorks Replication Solutions Manager 4.0.1• HP StorageWorks Replication Solutions Manager installation and administrator guide. See “Required

documentation” on page 11.– Upgrade to HP Replication Solutions Manager 4.0.1 if installed.

Monitoring storage system stability, page 36Time required: 25–35 minutesWhen to perform: 48 hours before the upgrade– Verify there are no critical events entered in the controller event log.– Ensure the storage system configuration is stable and no configuration changes are in progress.

Preparing an HP Continuous Access EVA environment for upgrading, page 37Time required: Varies depending on replication configurationWhen to perform: As close as possible to the upgrade– Disable failsafe mode on all DR groups.

Back up all storage system data, page 32Time required: VariesWhen to perform: As close as possible to the upgrade– Perform a full verified backup of all storage system data.

Saving storage system configuration information, page 38Time required: 10–15 minutesWhen to perform: As close as possible to the upgradeThings you will need:• HP Storage System Scripting Utility (called the utility). This is included with HP Command View EVA.• HP StorageWorks Storage System Scripting Utility reference. See “Required documentation” on page 11.– Capture configuration information using the utility.– Store configuration locally (not on storage system).

14 Pre-upgrade tasks

http://h18023.www1.hp.com/support/svctools/webes/index.html

Checking current software versionsEstimated time to complete: 10–15 minutes

When to perform: Any time prior to the upgrade

When upgrading the system software, you must upgrade related management software to the correctversion as required. Use Table 5 to collect version information for your current software. You mustupgrade any software that does not meet the required version.

NOTE:For complete details on EVA software compatibility, see the “EVA software solution compatibility” tableand the “HP Command View EVA interoperability support” table in the HP StorageWorks EnterpriseVirtual Array compatibility reference. See “Required documentation” on page 11 for the link to thisdocument.

Table 5 Management software version worksheet

Software Currentversion

Requiredversion

Locating versioninformation1

Upgrade procedure

HP Command ViewEVA (required) 8.0.1

1. Open HP CommandView EVA.

2. Click Help in theSession pane. The HPCommand View EVAOnline Help windowopens. The versiondisplays to the right ofthe dropdown list.

“Upgrading HP CommandView EVA” on page 32

HP ReplicationSolutions Manager(if installed)

4.0.1

1. Open or browse toHP StorageWorksReplication SolutionsManager.

2. Select Help in the menubar.

3. Select About. Theversion of HPReplication SolutionsManager server isdisplayed.

“Upgrading HP ReplicationSolutions Manager(optional)” on page 36

WEBES 5.2

1. Double-click the SystemEvent Analyzer icon onthe desktop.

2. Log in to the SystemEvent Analyzer.The WEBES versionis displayed in theSystem Event Analyzerwelcome page.

“Upgrading to WEBES5.2” on page 34

JRE 1.5.0_04 orlater2

1. OpenWindows controlpanel.

2. Double-click the Javaicon.

3. On the General tab,click About.The version of Java isdisplayed.

“Upgrading browser andJava Runtime Environment(JRE)” on page 34


Software Currentversion

Requiredversion

Locating versioninformation1

Upgrade procedure

Web browser(required)

InternetExplorer

6.0 SP1 orlater2

From your browser, selectHelp > About InternetExplorer.

“Upgrading browser andJava Runtime Environment(JRE)” on page 34

StorageManagementAppliance (requiredif the SMA is usedfor management)

2.1

1. From the SMA, clickHelp in the tool bar.

2. Check the defaultpage for the softwareversion.

See the StorageManagement Appliancedocumentation for upgradeinstructions.http://www.hp.com/support/manualsClick Storage Softwareunder Storage, and thenselect HP OpenViewStorage ManagementAppliance and Softwareunder Storage ResourceManagement Software.

1You can also use Windows Add or Remove Programs to view the software version.2For Windows servers. For clients running other operating systems, see the Browser and JRE support table in the HPStorageWorks Enterprise Virtual Array compatibility reference. See “Required documentation” on page 11 for the link tothis document.

Checking the HP Command View EVA versionTo check the HP Command View EVA version, perform the following steps:

1. Open HP Command View EVA on the management server.

The HSV Storage Network Properties window opens.

Figure 1 HSV Storage Network Properties page

2. Click Help in the Session pane.

The version is displayed. If the version listed is earlier than 8.0.1, it must be upgraded.




Figure 2 HP Command View EVA Online Help

Checking the storage system hardwareEstimated time to complete: 15–20 minutes

When to perform: 1–2 weeks prior to the upgrade. Provide enough time to order and replace anyfailed components.

Before upgrading your Enterprise Virtual Array, you should check the operation of the storage systemhardware and replace any failed components. This ensures the storage system will be operating properlywhen the upgrade is performed. This task should be performed far enough in advance to give you time toorder and replace any failed hardware components before beginning the upgrade.

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 Navigation pane. If there are any hardware caution orwarning 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 isa hardware problem.

Figure 3 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 field indicatesif there is a hardware error.


Figure 4 Checking operational states

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, whenthe I/O modules on a disk enclosure are not working, the controllers restart, or there is ahardware failure. If there are any hardware components listed under this folder, determine whythey are listed there and fix the problems.

3. Replace any hardware components that have failed.

NOTE:If you must replace any components, see the HP StorageWorks 4x00/6x00/8x00 Enterprise VirtualArray user guide for replacement instructions. See Table 3 on page 11 for the link to this guide.

Checking and upgrading your SAN infrastructureEstimated time to complete: Varies depending on the number of components that may requirereplacement.


It is important to ensure that your SAN environment meets the configuration requirements of XCS 6.200.This includes host HBAs and drivers, and Fibre Channel switch firmware.

Collecting SAN configuration data using SAN VisibilityHP 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. Anyinformation provided by devices when they log into the fabric is included. The raw configuration data iscollected, packaged, and sent to HP, where it is formatted into a complete report and returned to you.


The report can then be used to determine if any of your SAN components are not supported by XCS6.200 and must be replaced.

NOTE:Using SAN Visibility is optional.SAN Visibility requires Java Runtime Environment (JRE) 1.5.0 or later. You can download the most currentJRE version from Sun's website: http://www.sun.com/

Installing SAN VisibilitySAN Visibility is typically installed on the management server running HP Command View EVA.

1. Download SAN Visibility from the following website:

http://h18006.www1.hp.com/products/storageworks/san/index.html

Click SAN Visibility under Networking Solutions.

2. Double-click the downloaded file to launch the installation.

3. Follow the on-screen instructions to install the software.

Using SAN VisibilityBefore 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 usingthis tool, see the SAN Visibility online help.

1. Double-click the SAN Visibility icon on the desktop.

The SAN Visibility management page opens with the SAN Settings option selected.

2. Select Customer Details. See Figure 5.

3. Enter the customer data.

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 enterthe e-mail address where you typically receive e-mail.

c. Enter data in the remaining boxes as appropriate. This information is included in the reports,but is not required.


http://www.sun.com/

http://www.sun.com/

http://www.sun.com/

http://www.sun.com/

http://www.sun.com/

http://www.sun.com/

http://www.sun.com/

http://www.sun.com/



















Figure 5 SAN Visibility management page

4. 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 youchange 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 whichdata collection will be done.

b. Click Rename.

c. Click Yes to confirm the name change.

d. Select the fabric in the tree view.

e. Enter a name in Switch Group Name. You can use the default fabric name, but HP recommendsthat you change it to a name that is meaningful to you. This name is used when generatingreports, so it should be one that is easily recognized as being associated with the fabric onwhich data collection will be done.

f. Click Rename.

g. Click Yes to confirm the name change.


5. 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. Informationwill be collected for all devices connected to this switch.

b. Clear Discover cascaded switches. This option automatically detects all switches connected tothe switch identified by the IP address. Including all the cascaded switches increases the datacollected for the report to include all the devices connected to all the switches. If you want toinclude all the switches, leave this option selected.

c. Enter the switch login and password if required. The Read Community value is obtained fromthe switch.

d. If you have created more than one fabric, use the Select Switch Group drop-down list to selectthe fabric to which you want to add this switch.

e. Click Add to add the switch to the reporting configuration.

Creating a reportOnce you have configured SAN Visibility for data collection, you can create a report. There are twomethods for creating a report:

• Automatically—Automatically e-mails the data to HP when collection is complete. This requiresyou to know the SMTP address of your mail server. If you have external e-mail access fromyour environment, this is the preferred method.

• Manually—Requires you to manually send the data to HP. If you do not have external e-mailaccess, use this method.


Creating 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 datacollection. Check Collect data for all switch groups to create reports for all the fabrics.

3. Clear Capture Performance data for this switch. If you want to gather switch performance data,leave this option selected. Selecting this option will increase the amount of time required to collectthe switch data.

4. Click Start Data Collection. If you have selected the option to collect switch performance data, itwill 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 theformatted report returned to you within one business day.

5. When you receive the formatted report, save it to a temporary location on the management server.

Creating a report manually

The SMTP server IP address of the primary switch on the SAN is obtained by the e-mail address youentered on the Customer Details page. If SAN Visibility does not find the SMTP server or if you want tocreate 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. Click Start Data Collection. If you have selected the option to collect switch performance data, itwill take at least 10 minutes to collect the data.


4. Select Launch Default Mail Client. The location of the report is displayed.

5. Manually attach the raw report created and send the report to the following e-mail address:[email protected]

The report will be processed and the formatted report returned to you within one business day.

6. When you receive the formatted report, save it to a temporary location on the management server.

Reading the report1. Locate the returned report file and double-click on it. The contents are extracted and copied to

a local folder. If you used the default location during installation, this will be in the \ProgramFiles\Hewlett-Packard\HP SANVisibility\ExtractedProcessReports folder.

2. Select the report folder and double-click on the index.html file to open the report in your browser.

3. In the left navigation pane, click High Level Fabric Summary.

The High Level Fabric Summary window opens. See Figure 6.

4. For each switch, compare the indicated firmware (FW) version to the switch firmware supported byXCS 6.200. This information is included in Part II. Fabric infrastructure rules of the HP StorageWorksSAN design reference guide. See Table 3 on page 11 for the link to this document. If the firmware isnot at the indicated version or later, upgrade the firmware.

5. For each HBA, compare the indicated driver and firmware versions to the versions supported byXCS 6.200. This information is included in the appropriate HP StorageWorks 4x00/6x00/8x00Enterprise Virtual Array 6.2A or later connectivity release notes. See Table 3 on page 11 for the linkto these documents. If the firmware is not at the indicated version or later, upgrade the firmware.


Figure 6 Sample SAN Visibility report

Selecting an appropriate time to perform an online upgradeTo ensure the success of an online upgrade, selecting the appropriate time is essential. Because theonline firmware upgrade is performed while host I/Os are being serviced, the I/O load can impact theupgrade process. Selecting a period of low I/O activity will ensure the upgrade completes as quickly aspossible, and will avoid disruptions to host and applications due to timeouts.

When performing an online upgrade, select a time period that meets the following criteria:

• I/Os per second (IOPS) should be less than 7000• I/O throughput should be less than 70 MB/s

NOTE:The above values apply when upgrading the EVA4x00/6x00/8x00 storage systems. These values donot apply to EVA3000/5000 storage systems.

Analyzing storage system I/O using HP Command View EVAPerfThe HP Command View EVAPerf tool included with HP Command View EVA can be used to gather andanalyze statistics on storage system utilization. This section provides recommendations on using HPCommand View EVAPerf to gather statistics to help identify periods of low storage system activity.

If you are unfamiliar with HP Command View EVAPerf, see the “Monitoring array performance” chapterof the HP StorageWorks Command View EVA user guide for more information. See Table 3 for thelink to this guide.


Tips for using HP Command View EVAPerfUse HP Command View EVAPerf to identify periods of low I/O activity, during which you can safelyperform on online upgrade of the storage system firmware. Use the following tips to ensure that you selectan 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 simplifyidentifying your storage systems, virtual disks, and hosts. See the HP StorageWorks Command View EVAuser guide for more information about friendly names.

• Identify a period of time when you anticipate the I/O load on the storage system will be low. Thisis 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, ifyou suspect that I/O load may be low between midnight and 2 AM on Sunday morning, run HPCommand View EVAPerf during this period.

• If the I/O pattern is low, capture the data over the same time period several more times to ensurethe low I/O pattern is repeatable.

• When you have selected a potential time period for the upgrade, perform the following steps toensure 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 theduration of the upgrade.

HP Command View EVAPerf command optionsThe 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 datainto a spreadsheet for analysis.

• -cont n: Runs the command continuously at an interval specified by n. The default intervalis one second.

• -dur n: Specifies the duration of a continuous mode session. For example, if you enterevaperf hps -cont 2 -dur 30, host port data is displayed at two second intervals for atotal of 30 seconds.

• -sz array: Limits data collection to the specified array(s). You must enter at least one arrayand can use either the storage system WWN or friendly name.

• -fo filename: Directs output to a specified filename. Include the path information asnecessary.

Running HP Command View EVAPerf1. 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/Oactivity. For example, the following command will capture data at 15 second intervals for 2 hours onan array named EVA1 and store the output in a file named EVA_upgrade:

evaperf as –cont 15 –dur 7200 –sz EVA1 -fo C:\EVA_upgrade


3. When the command has completed, open the file in an ASCII editor. Identify any instances wherethe IOPS and throughput limits have been exceeded. If the limits have not been exceeded, thismay be a good period to perform the upgrade.

NOTE:Another option for displaying HP Command View EVAPerf data is to use the -csvcommand option, which saves the data as comma separated values for importing into aspreadsheet. 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 toidentify specific applications that are imposing heavy I/O loads, and suspend them long enough toperform 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 thestorage system are nearly idle with the exception of one virtual disk. To perform an online upgrade, itmay be desirable to halt the application that is imposing the load on the busy virtual disk. This will be farless 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 ViewEVAPerf 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 whichyou may want to perform the upgrade. For example, the following command will capture data at15 second intervals for 2 hours on an array named EVA1 and store the output in a file namedvirtual_disks:

evaperf vd -cont 15 -dur 7200 -sz EVA1 -fo C:\virtual_disks

3. When the command has completed, open the file in an ASCII editor. The virtual disk information willappear similar to that in Figure 7.

Activity is reported separately for each controller accessing a virtual disk. The total activity foreach virtual disk is the sum of the reported activity for each controller. A virtual disk may also bea snapshot, snapclone, or a DR group member. In the output, logical unit number (LUN) is usedinterchangeably 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 owningcontroller) but requests can still be processed by the other controller (the proxy controller). Inactive/active controllers, all host requests are logged by the receiving controller only, whether owningor proxy. Thus, all request rate and data rate activity for a virtual disk is the sum of both controllers.

The statistics you should use to determine the virtual disk activity are listed in Table 6.


Figure 7 Sample virtual disk statistics displayTable 6 HP Command View EVAPerf virtual disk statistics

Counter Description

Read Hit Req/sThe number of read requests per second completed from the array cachememory. Data may reside in the cache memory due to a previous cache miss orbecause 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 readhit requests.

Read Hit Latency The average time it takes to complete a read request (from initiation toinformation receipt) from the array cache memory.

Read Miss Req/s The number of read requests (per second) that failed to complete from the arraycache memory and were completed from physical disks instead.

Read Miss Data Rate The rate at which data is read from physical disks because the data was notpresent in the array cache memory.

Read Miss Latency The average time it takes to complete a read request (from initiation toinformation receipt) from the physical disks.

Write Req/s

The number of write requests per second completed to a virtual disk that werereceived from all hosts. Write requests may include transfers from a sourcearray to this array for data replication and host data written to snapshot orsnapclone volumes.

Write Data Rate The rate at which data is written to the virtual disk by all hosts and includestransfers from the source array to the destination array.

Write Latency This average time it takes to complete a write request (from initiation to receiptof write completion).

Flush Data Rate

The rate at which data is written to a physical disk for the associated virtualdisk. The sum of flush counters for all virtual disks on both controllers is the rateat which data is written to the physical drives and is equal to the total hostwrite data. Data written to the destination array is included. Host writes tosnapshots and snapclones are included in the flush statistics, but data flow forinternal snapshot and snapclone normalization and copy-before-write activityare not included.

Mirror Data Rate

The rate at which data travels across the mirror port to complete read and writerequests to a virtual disk. This data is not related to the physical disk mirroringfor Vraid1 redundancy. Write data is always copied through the mirror portwhen cache mirroring is enabled for redundancy. In active/active controllers,this counter includes read data from the owning controller that must be returnedto the requesting host through the proxy controller. Reported mirror traffic isalways 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 ofsubsequent reads when a sequential stream is detected. Note that a sequentialdata stream may be created by host I/O and other I/O activity that occursbecause of a DR initial copy or DR full copy.


Displaying EVA performance data using Windows Performance MonitorAn alternative for capturing and displaying EVA performance metrics is Windows Performance Monitor.This tools provides a graphical presentation that you may find more useful for analyzing EVA performancedata. See the HP StorageWorks Command View EVA user guide for more information about usingWindows Performance Monitor.

Figure 8 Windows Performance Monitor display

Managing host I/O timeouts for an online upgradeThe default values for host operating parameters such as LUN timeout and queue depth are typically setto values that ensure proper operation with the storage system. These values are appropriate for moststorage system operations, including online firmware upgrades. In general, host LUN timeouts of 60seconds or more are adequate to accommodate an online upgrade. In most situations it will not benecessary 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 resetthem to their original default value. The following section provide a summary of the steps and commandsinvolved in checking and changing timeout values for each supported operating system. See theoperating system documentation for more information.

NOTE:Unless otherwise noted, cluster testing with online controller firmware upgrades has not been completed.Cluster information will be added to this document when the testing is complete.

Microsoft Windows

NOTE:• 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.


Checking timeout values• The key timeout setting in the registry at HKEY_LOCAL_MACHINE/SYSTEM/

CurrentControlSet/Disk/TimeoutValue should be set to 3c (60 seconds)

HP-UX

CAUTION:Because HP-UX supports boot across Fibre Channel SAN, any change to default SCSI timeouts on theHP-UX host may cause corruption and make the system unrecoverable.

Default timeout values• Sdisk timeout: 30 seconds• (LVM) lvol timeout: 0 seconds

Checking timeout values• Device within a LVM volume group: pvdisplay /dev/dsk/cxtxdx• lvol physical volume with an LVM group: lvdisplay /dev/vgxx/lvolx

Changing timeout valuesPvchange -t (seconds) /dev/dsk/cxtxdx

LinuxThe 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 = 0xA6

QLogic Driver parameters (single path):

• qdepth = 16• port_down_retry_count = 64• login_retry_count = 30• failover = 1• load_balancing = 1• excludemodel = 0x0• auto_restore = 0xA6

Emulex Driver parameters (single path)

• HPELXLPFC=y• nodev_timeout=60• qdepth=30


• discovery_threads=1

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.

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 forgeneral data integrity.

• Online controller firmware upgrades are supported with Linux boot devices.

SolarisSolaris 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 timeoutsFor Sun drivers, add the following lines to /etc/system file:

set sd:sd_io_time = 60set ssd:ssd_io_time = 60

For QLogic, edit the /kernel/drv/qla2300.conf file and change the hbax-link-down-timeoutvalue 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 60as follows:

linkdown-tmo=60;

Tru64Tru64 has a 60 second timer for media command timeouts. In most cases, up to 5 retries can occur withinthe kernel's I/O stack, which results in a 5–6 minute window before I/O is returned to the file system. Nochanges should be made to any Tru64 settings when performing an online firmware upgrade.

Online controller firmware upgrades are supported in Trucluster 4–node environments where the EVA isthe cluster boot device.

OpenVMSThe limit for LUN timeout is 120 seconds.

NOTE:OpenVMS handles the controller reboot seen at the conclusion of the firmware update process. Disks onthe controller display a Mount Verify status during the controller reboot but regain Mounted status andresume I/O operations upon the completion of the controller reboot. No changes need to be made toany OpenVMS default settings when performing an online firmware upgrade.

Online controller firmware upgrades are supported in OpenVMS cluster environments where the EVA isthe cluster boot device.


IBM AIX

Checking or changing timeoutsAIX requires the disk settings shown in Table 7 for the native multipath drives.

Table 7 IBM AIX timeout settings

Setting Value Description

PR_key_value NA Sets the key value for persistent reservations. Persistent reservationsare not supported.

Algorithm fail_overSets the load balancing algorithm to fail_over. All I/O uses asingle path. The remaining paths are in standby mode. The valueround_robin is not supported.

hcheck_interval 60 Sets the path health feature to check each device every 60 seconds.

hcheck_mode nonactiveSpecifies the I/O paths monitored by the path health checkingfeature: nonactive—Checks all I/O paths for Failed status, andchecks standby paths for Used/Opened devices.

queue_depth 8 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.

Managing application I/O timeouts for an online upgradeApplications are typically insulated from the online controller firmware upgrade by the operating systemand HBA driver software. Consequently, if the application is running on a properly configured operatingsystem, the online controller upgrades will be performed successfully.

It may be necessary to determine if any applications have timeout requirements that are more stringentthan those of the operating system. Any applications with more stringent timeouts should be evaluatedto determine if the application timeouts will be exceeded by the resynchronization interval that occursduring the online upgrade.

Although an application may survive the online firmware upgrade successfully, there may be an impacton performance. To minimize the performance impact on users, the online upgrade should be performedduring a period of low user activity.

Back up all storage system dataEstimated 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 storagesystem data. Although not required, it is always good practice to back up your data before performingmajor operations such as software upgrades. The backup should be scheduled as close to the upgradeprocess as possible.

For more information about establishing and implementing good backup procedures for the EVA, contactyour HP sales representative.

Upgrading HP Command View EVAEstimated time to complete: 15–20 minutes



HP Command View EVA 8.0.1 is required with XCS 6.200. Check the current version and upgrade thesoftware if necessary.

Table 8 identifies the upgrade paths to HP Command View EVA 8.0.1.

Table 8 HP Command View EVA upgrade paths

Current HP Command ViewEVA Version Upgrade Path

HP Command View EVA 6.0

HP Command View EVA 6.0.1


HP Command View EVA 7.0


To upgrade your existing version of HP Command View EVA,complete the following steps:1. Uninstall the existing version of the HP Command View EVA.2. Install HP Command View EVA 8.0.3. Upgrade to HP Command View EVA 8.0.1.

HP Command View EVA 8.0 Upgrade to HP Command View EVA 8.0.1

For more information on HP Command View EVA, including the HP StorageWorks Command ViewEVA installation guide and the release notes, download documentation from the website listed in“Required documentation” on page 11.

Upgrading using the typical installationThis procedure is for the typical HP Command View EVA installation. To use the custom installationprocedure, which provides control over which components are installed, see the HP StorageWorksCommand 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 setup.exe to start the installation.

The InstallAnywhere Wizard Welcome window opens.

5. Follow the on-screen instructions to complete the installation.

NOTE:When SMI-S EVA is installed using the typical installation, a default account for the CIM administrator iscreated if an administrator account exists on the management server prior to installation. The defaultuser name and password is administrator. If an administrator account does not exist on the managementserver prior to installation, the default CIM administrator account is not created during installation. Youmust add at least one CIM administrator account to CIMOM after completing the installation. See“Managing users in SMI-S EVA” in the HP Command View EVA installation guide for more information.A trust relationship between HP Command View EVA and SMI-S EVA is established automatically whenyou install SMI-S EVA. As a result, HP Command View EVA accepts all SMI-S EVA queries.

Verifying the installationTo verify that the software was installed successfully:


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.If you installed the software suite on an SMA, the HP Command View EVA icon does not appearon the desktop.

• The software is available from the Start menu (for example, Start > Programs > HP CommandView EVA).If you installed the software suite on an SMA, the software is not available from the Start menu.

• 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, clickHardware 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 HPStorageWorks Command View EVA installation guide for more information.

Upgrading browsers and JREsEstimated time to complete: 10–20 minutes


Ensure that you are using a supported browser and JRE. HP Command View EVA may not work correctlywith an unsupported browser.

The JRE is not used by HP Command View EVA, but it is needed for HP Replica-tion Solutions Manager. It is also required for WEBES and SAN Visibility. See“Upgrading HP Replication Solutions Manager (optional)” on page 36 for more information.

For complete information on supported browsers and JREs, see the "Browsers and JREsupport" 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 to HPCommand View EVA 8.0.1.

Upgrading to WEBES 5.2Estimated time to complete: 10–20 minutes



WEBES is optional diagnostic monitoring software. If WEBES is currently installed, it must be upgradedto version 5.2, which is required with HP Command View EVA 8.0.1. To download the WEBES 5.2software kit, go to the following website:

http://h18023.www1.hp.com/support/svctools/webes/

Archiving and clearing the error logBefore upgrading WEBES, perform these steps to archive and clear the error log. If WEBES is installed andrunning when you clear the log, stop the Director process before proceeding. See the WEBES User Guidefor information on stopping the Director. Also, do not stop and restart any Windows system processes.

NOTE:You can upgrade WEBES without clearing the error log. However, the initial scan of event data maytake longer if the log is not cleared first.

1. Open the event viewer.

• Windows 2000: Select Start > Programs > Administrative Tools > Event Viewer.• Windows Server 2003: Select Start > Programs > Administrative Tools > Event Viewer.• Windows XP: Select Start > Control Panel > Performance and Maintenance > Administrative

Tools > Event Viewer.2. For events analyzed by the System Event Analyzer (SEA), follow step “a” on a Pentium server or step

“b” on an Integrity server.

a. Pentium: Clear the application event log:

Go to the Application Log. SEA does not process events from any other Windows event log.

Select Application in the left pane of the event viewer window.

b. Integrity: Clear the system event log:

Go the System Log. SEA does not process events from any other Windows event log.

Select System Log in the left pane of the event viewer window.

3. Clear all events by selecting Action > Clear all Events.

NOTE:Before the existing events are cleared, you are prompted to save them first. Be sure to selectYes to save these events to a file. You can analyze these saved events at a later time.

4. Close the event viewer.

Upgrading WEBESThis procedure applies when upgrading to WEBES 5.2 from an existing version of WEBES that is withintwo versions of 5.2. For example, WEBES 5.2 can be upgraded when either version 4.5 or 5.1 isinstalled, but not if version 4.4.3 or earlier is installed. If an upgrade is attempted on a version of WEBESthat is too old, you will be told to uninstall the existing version, and the upgrade will not proceed.

If WEBES is already uninstalled or was never installed, see the WEBES Installation Guide.

Upgrading lets you preserve your configuration and state data. Be aware that upgrading uninstalls theolder version of WEBES and installs the newer version. The upgrade does not patch or replace certainfiles, as was the case with WEBES Service Packs.

Whenever a version of WEBES is already installed that is capable of being upgraded, the WEBES kitinforms you that the older version was detected and prompts you about upgrading.



















1. Double-click the WEBES kit file to open the kit.

2. Click Yes to run the kit.

The kit does the following:

a. Saves configuration and state data to %SystemDrive%:\WebesBackup, where%SystemDrive% is the drive where Windows (not necessarily WEBES) was installed.

b. Uninstalls the existing installation.

c. Installs this version with the same components (SEA or CCAT) that were present before.

d. Restores the saved data.

e. Deletes the WebesBackup directory and all of its contents.

Upgrading HP Replication Solutions Manager (optional)Estimated time to complete: 10–20 minutes


If HP Replication Solutions Manager is installed, you must upgrade it to version 4.0.1. HP ReplicationSolutions 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 administratorguide. 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 4.0.1 requires JRE 1.5.0_04 and later. Go to the Sun website(www.sun.com) and download the required JRE.

Monitoring storage system stabilityEstimated time to complete: 25–30 minutes

When to perform: 48 hours before beginning the upgrade

The storage system configuration should be stable for 48 hours before beginning the upgrade. Check thestatus of the array to ensure it is stable and then continue monitoring status until the upgrade begins.

1. Open HP Command View EVA and click the icon of the storage system you want to upgrade.

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 9 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 tocorrect the problems. In some cases, it may be necessary to call your HP-authorized servicerepresentative to fix the problem.

3. Verify that no changes to the storage system configuration are in progress. For example, you shouldnot be in the process of creating a virtual disk. Configuration changes should not be made within 48hours before beginning the upgrade. Proactive event notification can be used to alert you if a criticalevent 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 resumedwhen the upgrade is complete.

• Ensure you suspend any processes or applications that may change the storage systemconfiguration, such as backups and snapshot creation or deletion. Stop any HP StorageSystem Scripting Utility scripts that are scheduled to run automatically.

Preparing an HP Continuous Access EVA environment forupgrading

Estimated time to complete: Varies depending on replication configuration


When upgrading an EVA in an HP Continuous Access EVA environment, the following requirements mustbe met. See HP StorageWorks Continuous Access EVA administrator guide for more information.


• Before you upgrade any storage system in an HP Continuous Access EVA relationship, ensure thatall 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 onlytwo versions of controller software. You cannot have more than two versions in an HP ContinuousAccess EVA environment.

• During the time that the HP Continuous Access EVA storage systems are running different controllersoftware 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 AccessEVA relationship within sixty 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 conditionsare met. If you attempt to upgrade the controllers before the following conditions are met, controlleroperation 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 one week before upgrading the second storage system. Ensure the preceding conditionsare met on the second system.

Upgrading disk drive firmware in an HP Continuous Access EVA environmentWhen upgrading disk drive firmware in an HP Continuous Access EVA environment, the followingrequirements must be met. See HP StorageWorks Continuous Access EVA implementation guide formore information.

• Verify that all DR groups are not failsafe mode enabled or in the failsafe locked state (DR groupfailsafe mode should be disabled).

• Suspend replication and disable the intersite link or modify zoning to isolate the source arrayfrom 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 informationEstimated time to complete: 10–15 minutes



Before beginning the upgrade, the current configuration information should be collected and saved. Thisinformation can be used to restore the existing configuration if necessary. The configuration data is savedto a series of files stored in a location other than on the storage system. HP Storage System ScriptingUtility (called the utility) is used to collect configuration information.

This procedure can be performed from the Storage Management Appliance (SMA) or managementserver where HP Command View EVA is installed, or from any host running the utility to communicatewith 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. Whenprompted, 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, quotesmust enclose the name. For example, SELECT SYSTEM “Large EVA”.

4. Enter CAPTURE CONFIGURATION, specifying the full path and filename of the output files forthe configuration data.

The configuration data is stored in a series of one to five files, which are scripts. The file namesbegin with the name you select, with the restore step appended. For example, if you specify a filename of LargeEVA.txt, the resultant configuration files would be LargeEVA_Step1A.txt,LargeEVA_Step1B, etc. Files which do not contain configuration information are not createdand therefore are not available to be restored.

The contents of the configuration files can be viewed with a text editor.

5. Enter exit.

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 withdifferent disk sizes and types” section in HP StorageWorks Storage System Scripting Utility referencefor more information.

You can run the CAPTURE VALIDATE command for each of the files generated by the CAPTURECONFIGURATION command to determine if the file has been modified since the initial capture.

For more information about using the utility or using the CAPTURE commands, see the HP StorageWorksStorage System Scripting Utility reference. See “Required documentation” on page 11 for the link to thisdocument.


3 Upgrading the Enterprise VirtualArray

The following steps guide you through the process of upgrading the system software. Ensure that youfollow them carefully and in the specified order. Table 9 on page 41 provides a checklist so you cantrack your progress as you perform the upgrade. Make sure you have all the items indicated beforebeginning the upgrade.

Table 9 Upgrade task checklistStep 1. Checking the health of the Enterprise Virtual Array, page 42Time required: 20–30 minutes− 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 48hours

Step 2. Disabling ISEE, page 45Time required: 10–15 minutes− Disable ISEE (if used).

Step 3. Clearing storage system passwords, page 45Time required: 10–15 minutes− Clear the OCP password.− Disable password access in HP Command View EVA.

Step 4. Halting all host access to the storage system for an offline upgrade (optional), page 46Time 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 firmware to XCS 6.200, page 46Time required: 25–30 minutesThings you will need:• HP StorageWorks EVA 4x00/6x00/8x00 6.2 controller software− Upgrade XCS firmware to version 6.200.

Step 6. Upgrading disk drive firmware, page 51Time required: Varies depending on the number of disk drives that must be upgraded. It can take 30 secondsto 3.5 minutes per drive.Things you will need:• Disk drive code bundled image file, which can be downloaded from the following website:

http://www.hp.com/support/evadiskfirmware− Download the disk drive firmware file.− Upgrade the disk drive firmware.


http://www.hp.com/support/evadiskfirmware

Step 7. Entering storage system passwords, page 55Time required: 10–15 minutes− Enter the OCP password.− Enable password access in HP Command View EVA.

Step 8. Resuming storage system operation, page 57Time 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 ISEE (if used).

Upgrading remotely versus locallyYou can perform the upgrade from a local server or from a remote server. Some advantages toperforming the upgrade locally include:

• Enables you to view the various status indicators on the storage system hardware to ensureeverything is working properly.

• Provides access to the controller operator control panel (OCP) to clear storage system passwordsand to monitor messages.

• Reduces the amount of time involved during file transfers. The shorter distance over the networkthe code files must travel, the faster the transfer will occur.

Solving upgrade problemsIf you experience any problems when performing the XCS upgrade procedure, see“Troubleshooting” on page 61 for assistance. If you are still unable to resolve the problem, contact yourHP-authorized service representative for assistance.

Step 1. Checking the health of the Enterprise Virtual ArrayEstimated time to complete: 20–30 minutes

Before upgrading your Enterprise Virtual Array, perform a final check of the overall status of allcomponents. The pre-upgrade checks should ensure that the storage system is ready for upgrading, butthe storage system status should be checked again.

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 Navigation pane. If there are any hardware caution orwarning 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 isa hardware problem.

42 Upgrading the Enterprise Virtual Array

Figure 10 Hardware Folder Properties window

c. If a problem is indicated, continue to expand the navigation tree under the Hardware folderuntil 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 indicatesif there is a hardware error.

Figure 11 Checking operational states

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, whenthe I/O modules on a disk enclosure are not working, the controllers restart, or there is ahardware failure. If there are any hardware components listed under this folder, determine whythey are listed there and fix the problems.


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 have occurred withinthe last 48 hours.

The most recent 400 events are displayed. If more than 400 events have occurred within the last48 hours, use the Display Range box to select the preceding events.

Figure 12 Controller Events (Initialized system) page

e. If Critical events have occurred within the last 48 hours, perform the steps outlined in thecorrective action codes to correct the problems. In some cases, it may be necessary to call yourHP-authorized service representative to fix the problem.

CAUTION:If any critical events have occurred within the last 48 hours, do not proceed with theupgrade until the situation has been resolved.


4. Verify that no changes to the storage system configuration are in progress. For example, you shouldnot be in the process of creating a virtual disk. Configuration changes should not be made within 48hours 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 resumedwhen the upgrade is complete.

• Make sure you suspend any processes or applications that may change the storagesystem configuration.

• Proactive event notification can be used to alert you if a critical event occurs during the48 hours before the upgrade.

Step 2. Disabling ISEEEstimated time to complete: 10–15 minutes

To avoid the generation of unnecessary events and alerts during the upgrade, you should disable ISEEwhile performing the upgrade. It is necessary to stop and restart WEBES so that it will not expect ISEE tobe running.

If you are running ISEE, disable it as follows to avoid generating unnecessary alerts during the upgrade:

1. On the management server, open a command window.

2. Enter the following command to stop ISEE:

C:\>DESTA ISEE OFF

3. Enter the following commands to stop and restart WEBES:

C:\>net stop desta_service

C:\>net start desta_service

4. Enter exit.

Step 3. Clearing storage system passwordsEstimated time to complete: 10–15 minutes

If you use passwords on the controllers, use the following procedure to clear them.

NOTE:When you clear a system password on the controller, you must also disable password access to thestorage system in HP Command View EVA. The two work in conjunction with one another.

Clearing the password on the Operator Control Panel (OCP)Clearing the password requires access to the storage system. The OCP is located on the front of eachcontroller.

Using the following procedure to clear the password on the storage system controllers. The passwordcan be cleared from either controller.

1. Press four times to scroll to the System Password menu.

2. Press to display Change Password?


3. Press to scroll to Clear Password.

4. Press to display Clear Password.

5. Press Enter to clear the password.

The Password cleared message will be displayed.

The password is cleared. The system automatically returns to the default display (WWID).

Disabling password access in HP Command View EVAEstimated time to complete: 10 minutes

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.

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.

NOTE:Make sure you select the storage system from which you cleared passwords using theOCP on the controller.

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 anoffline upgrade (optional)

Estimated time to complete: Varies. Must be performed for each host accessing the storage system.

Online upgrade is supported from XCS 6.110, 6.100 and 6.000. Because of the minimal disruption tosystem operation, the online procedure is recommended. If the upgrade will be performed offline, allhost I/O to the storage system must be stopped. Stop all applications accessing the storage system andshut down hosts, if necessary.

Step 5. Upgrading controller firmware to XCS 6.200Estimated time to complete: 25–30 minutes


CAUTION:Before upgrading the controller firmware, ensure that the storage system configuration is stable and isnot being changed in any way. If any configurations changes are in progress, monitor them using HPCommand View EVA and wait until they are completed before proceeding with the upgrade.

Upgrading controller firmware

IMPORTANT:If upgrading from XCS 5.1x0 to 6.200, all source and destination DR groups must be in synchronousmode before upgrading. Check each DR group to verify this setting before proceeding.

To upgrade the controller firmware:

1. Open HP Command View EVA in your browser.

2. In the Navigation pane, select the storage system you want to upgrade.

The properties window for the selected storage system opens.

3. Click Code load.

The Code Load Storage System-Page 1 window opens.

Figure 13 Code Load Storage System-Page 1 window

4. To download XCS 6.2 controller software from the web, go to the following website:http://h20293.www2.hp.com.

5. Select Storage and NAS under Product category, and then select HP EVA XCS 6.200 ElectronicDownload.

You will receive two .ISO images from which you can create CDs.

6. After creating a CD of the installation .ISO image, click Browse and select the file containingversion XCS 6.200 of the storage system software from the installation CD:

• EVA8000/8100 – Select either the \HSV210\6200\HSV210_6200.SSS or\HSV210\LATEST\HSV210_6200.SSS file (the files are identical).

• EVA4000/4100 or EVA 6000/6100 – Select either the\HSV200\6200\HSV200_6200.SSS or \HSV200\LATEST\HSV200_6200.SSS file(the files are identical).

7. Click Next Step.








The Code Load Storage System-Page 2 window opens listing any pre-update application notes.Read them before continuing.

Figure 14 Code Load Storage System-Page 2 window

8. Click Next Step.

The new storage system software is copied to the controllers and validated. A progress page opensand is updated as the code segments are validated. For a description of each code segment,see Table 10 on page 49.

When the code validation is complete, the Code Load Storage System-Page 3 window opens.


Figure 15 Validating code segments complete

Table 10 System software code segment descriptions

Segment Description

Before text Text file with information about the new code and upgrade requirements.Displayed by HP Command View EVA and not sent to the controller.

Information file File stored on the controller's card describing contents of this superfile.

OCP image Firmware for the Operator Controller Panel (LCD entry and display panel) PIC(8-bit) processor chip.

SDC image Firmware for System Data Center (Battery, Temperature and Blower manager) PIC(8-bit) processor chip.

Glue image Firmware for the GLUE chip FPGA, stored in EEPROM.

CBIC image Firmware for the CanBus Interface Chip (drive shelf out-of-band communicationschip) PIC (8-bit) processor chip.

Event text file File enabling HP Command View EVA to translate binary event data to text. Notsent to the controller.

EMU image Firmware for the Drive Shelf Environmental Monitoring Unit (EMU) module. Storedon the controllers program card and contains the image for the CTS I/O module.

Boot image Initial Firmware that the controller's main processor (PPC) runs after reset orpower-on.

Functional image EVA firmware that is upgraded and provides support for all EVA functions.

After textText file with information declaring that upgrade has completed and describingand post-upgrade requirements. Displayed by HP Command View EVA and notsent to the controller.


9. Click Finish.

The following confirmation message opens.

10. Click OK to upgrade the system software on the controllers. Click Cancel to stop the code loadprocess and return to the Storage System Properties window.

The upgrade process begins and the Initializing firmware code load page opens. See Figure 16.This page is displayed until the controller code load is complete and the controllers restart. Duringthis interval both controllers resync and begin operating on the new firmware code. Once the resyncis complete, the controllers begin processing host I/Os.

Next, code within the storage system is updated, which can take up to 10 minutes to complete. Thisincludes firmware on the EMU and I/O modules in the disk enclosures. During this interval, theStorage System Updating Firmware window opens. See Figure 17.

Figure 16 Initializing firmware code load

Figure 17 Storage system updating firmware

11. When the firmware upgrade is complete, the Initialized Storage System Properties window opens.Verify the version of the storage system software in the Version box. It should be 6200.


Figure 18 Verifying XCS version after upgrading

Step 6. Upgrading disk drive firmwareEstimated time to complete: Varies depending on the number of disk drives that require upgrading and theI/O load on the storage system. It can take 30 seconds to 3.5 minutes per drive to upgrade the firmware.

The firmware on all disk drives can be upgraded online.

Although it is not required that the disk drive firmware be upgraded at the same time as the systemsoftware, it is strongly recommended that you perform the two tasks together. The disk drive firmwaresupplied with the system software upgrade complements the operation of the controller firmware and forthe best results the two should be used together.

You will need the correct disk drive firmware bundled image file to update the drive firmware. The diskdrive firmware file can be downloaded from the following website:


Be sure to observe the following cautions when upgrading disk drive firmware.

CAUTION:• 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.














Upgrading the firmwareUpgrade the disk drive firmware after you upgrade the system software.

1. If you have not already done so, download the disk drive firmware file from the following website:


a. When you download the file from the web, the file is downloaded as a zip file. Store the fileto a local directory.

NOTE:It is recommended that you use the default directory of C:\ProgramFiles\Hewlett-Packard\Sanworks\CodeLoad. If you use a differentdirectory, you will have to enter the complete path when identifying the location ofthe firmware files.

b. Double-click the zip file to extract the bundled image file. When extracted, the file type isan executable.

2. Open HP Command View EVA.

3. In the Navigation pane, select the storage system being upgraded.

4. Click Code load.

The Code Load Selection window opens.

Figure 19 Code Load Selection window — disk drives

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

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














Figure 20 Code Load Disk Drives — Page 1 window

6. Enter the path to the folder containing the extracted bundled image files.

7. Click Next step.

The Code Load Disk Drives On Line - Page 2 window opens. The table indicates which disk drivesrequire firmware upgrades.


8. Click Next step.

The disk drive code load operation begins. A status page opens indicating the progress as eachdisk drive is upgraded.


The disk drives are upgraded sequentially. Depending upon the I/O load on the storage system, itcan take 30 seconds to 3.5 minutes per drive to upgrade the firmware. The status is updated at 45second 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 Statusbox on the Status window displays NO for the 10 drives that have been upgraded andthe remaining 17 drives are not upgraded.

Figure 22 Code Load Disk Drives — status window

9. When all the disk drives have been upgraded, the Code Load Disk Drives On Line - Page 3 windowopens indicating the drives that have been upgraded successfully. Click Finish.



Upgrading firmware on an individual diskIf it is necessary to upgrade the firmware on an individual disk, the firmware and installation instructionscan be downloaded from the following website:


NOTE:Online code load of disk drive firmware can also be done to individual disks by this method.

Step 7. Entering storage system passwordsEstimated time to complete: 10–15 minutes

NOTE:• This step is only required if you use password protection on the storage system.• When you add a system password to the controller, you must also enable password access in HP

Command View EVA. The two work in conjunction with one another.

XCS 6.000 and later supports long passwords of up to 16 characters. The password must meet thefollowing requirements:

• 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 ~ \

Entering the password on the OCPUsing the following procedure to enter the password on the storage system controllers. The passwordcan be entered from either controller.

1. With either of the default menus (Storage System Name or World Wide Name) displayed, pressthree times to display System Password.

2. Press to display Change Password?

3. Press Enter for yes.

The default password, AAAAAAAA~~~~~~~~, is displayed.

4. Press or to select the desired character.

5. Press to accept this character and select the next character.

6. Repeat the process to enter the remaining password characters.

7. Press Enter to enter the password and return to the default display.

Enabling password access in HP Command View EVAEstimated time to complete: 10 minutes

After entering a password on the OCP, you must enable password access in HP Command View EVA. Toenable 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 24 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 passwordaccess.

6. Enter the password in the Password and Confirm password fields.

NOTE:Make sure you use the same password you entered on the controller OCP.

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 operationEstimated time to complete: Varies.

After the storage system software and disk firmware have been successfully upgraded, the storage systemcan be returned to normal operation.

1. Using HP Command View EVA, check the overall status of the storage systemto ensure there are no problems. For instructions on checking the status, see“Step 1. Checking the health of the Enterprise Virtual Array” on page 42.

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 37.

4. If you changed any host LUN timeout values, reset them to their original values.


5. If you are running ISEE, 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 command to start ISEE:

C:\>DESTA ISEE ON

d. Enter the following commands to stop and restart WEBES:

C:\>net stop desta_service

C:\>net start desta_service


4 Downgrading the EnterpriseVirtual Array

Support for downgrading from XCS 6.200 depends on the minimum supported versions of your EVAcontroller hardware. Due to metadata changes in XCS 6.200, to downgrade it will be necessaryto reinitialize the storage system and restore all data. Before proceeding with a downgrade, youmust contact HP Services to determine if a downgrade is allowed in your configuration and, if so, toschedule the procedure.

IMPORTANT:If you are using a “-B” controller, you cannot downgrade to any version earlier than XCS 6.110. TheHSV200-B and HSV210-B controllers require a minimum version of XCS 6.110.


60 Downgrading the Enterprise Virtual Array

5 Troubleshooting

This chapter provides troubleshooting information should you encounter any problems when updatingthe system software. Each troubleshooting section is cross-referenced to the corresponding step in“Upgrading controller firmware” on page 47 where the problem is likely to occur.

Many of the common problems you may encounter are included. Contact your HP-authorized supportrepresentative for help if this information does not help your problem.

The following troubleshooting topics are covered:

• “HP Command View EVA problems” on page 61• “Troubleshooting HP Command View EVA with the StorageManagement Appliance (SMA)” on page 61• “Troubleshooting HP Command View EVA with a management server” on page 62• “Troubleshooting specific Command View EVA errors” on page 62

• “View is not set or view list is null” on page 63• “HTTP status 404, not found or status 503, no service” on page 63• “Unknown storage system” on page 64• “No storage systems found” on page 64

• “Solving security credentials configuration problems” on page 65• “Solving problems selecting a storage system (Step 2)” on page 66• “Solving problems disabling HP Continuous Access EVA DR group failsafe mode (Step 3)” on page 67• “Solving problems downloading the system software file (Step 6)” on page 67

• “Invalid firmware image file (Status code 21006)” on page 67• “Bad image header (Status code 65)” on page 68

• “Solving problems if the storage system does not come back online (Step 10)” on page 68• “Solving problems with multiple resyncs (Step 10)” on page 69

Solving HP Command View EVA problems (Step 1)There are a number of issues that may impact the operation of HP Command View EVA and its ability tocommunicate with the storage system.

General HP Command View EVA troubleshooting tipsUse 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 password?

Troubleshooting HP Command View EVA with the Storage ManagementAppliance (SMA)

Use the following steps to isolate problems that may occur when using HP Command View EVA with anSMA:


1. Check the HP StorageWorks Enterprise Virtual Array compatibility reference to ensure that theversion of HP Command View EVA you are using is compatible with the XCS version. Forcomplete details on EVA software compatibility, see the “HP Command View EVA interoperabilitysupport” table in the HP StorageWorks Enterprise Virtual Array compatibility reference. See“Required documentation” on page 11 for the link to this document.

2. Determine if HP Command View EVA has been restarted.

3. If you are using Emulex HBAs, ensure that the Emulex utility sees the EVA WWNs.

4. Ensure that the server and EVA is logged into the fabric and check the following:

a. Check the switch for zoning.

b. Ensure that each HBA has access to only half of the EVA ports.

5. 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.

6. Reboot the SMA.

Troubleshooting HP Command View EVA with a management serverUse the following steps to isolate problems that may occur when using HP Command View EVA witha management server:

1. Check the HP StorageWorks Enterprise Virtual Array compatibility reference to ensure that theversion of HP Command View EVA you are using is compatible with the XCS version. Forcomplete details on EVA software compatibility, see the "HP Command View EVA interoperabilitysupport" 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:

• HBAnywhere (Emulex)• SanSurfer (QLogic)

4. 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:

i. Click Delete Cookies.

ii. Click Delete Files.

d. 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 folders C:\Program Files\Compaq\SANworks\Element Manager forStorageWorks HSV\HSV200xx or HSV210 exist.

Troubleshooting specific HP Command View EVA errorsThis section describes specific Storage Management Appliance/HP Command View EVA errors:

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

62 Troubleshooting

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.

Resolution

Click OK. Wait one to five minutes, depending on the size of the storage system, and try the commandgenerating this message again. If you still cannot see the storage system, stop and restart HP CommandView 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 Servicemessage.

Cause

These messages indicate that the server responded, but it could not find the page being requested. HTTPerrors, including 404 and 503, originate from the web server, the HTTP server, or the appliance. Evenwhen HP Command View EVA cannot respond, the web server continues to respond to HTTP requestsfrom a browser.

During normal interaction between HP Command View EVA and the web server:

1. A browser requests an HP Command View EVA page.2. The web server passes the request for the page to HP Command View EVA.3. HP Command View EVA responds with the page.4. The web server sends it to the browser.

These errors indicate that a problem is occurring with this normal interaction. Table 11 lists some possiblecauses of these errors and their corrective actions.

Resolution

Table 11 Possible causes and corrective actions for HTTP 404 and HTTP 503 errors

Possible Cause Corrective Action

404 Error: HP Command View EVA may be initializingwhen 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 theRefresh/Reload button on the browser.

404 Error: A .frm (HTML) file may be missing in the HPCommand View EVA directory structure. This can occurif the files were changed or if the HP Command ViewEVA installation went amiss.

Reinstall HP Command View EVA.



503 Error: HP Command View EVA may be down whena 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 ViewEVA is up.

Browser timeout: The appliance may be down or theweb server may be unavailable when a browser makesa request to HP Command View EVA. In this case, thebrowser will time out internally.

Retry the request when the appliance andHP Command View EVA are up.

Unknown storage system

Symptom

HP Command View EVA reports an unknown storage system for a storage system that should bedisplayed.

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 system—cause 1” on page 64 below.

• The controllers are running a version of XCS that HP Command View EVA does not recognize.See “Unknown storage system—cause 2” on page 64.

Unknown storage system—cause 1

When the fabric is heavily loaded, the FC adapter in the management server may time out commands tothe controllers. If this occurs, the storage system appears in the Unknown state.

Corrective Action for Unknown Storage System—Cause 1

This scenario should correct itself in less than one minute. Alternately, you can perform a Rediscoveroperation to initiate new commands to the controller.

Unknown storage system—cause 2

HP Command View EVA can only manage controllers that are running supported XCS versions.

Corrective Action for Unknown Storage System—Cause 2

Ensure that you are running the HP Command View EVA version that is compatible with XCS6.200. See the "HP Command View EVA interoperability support" table in the HP StorageWorksEnterprise Virtual Array compatibility reference to determine which version of HP Command ViewEVA 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 12 lists some possible causes of these errors andtheir corrective actions.

64 Troubleshooting

Corrective action

Table 12 Possible causes and corrective actions when no storage system found


The management server may not be able tocommunicate with either controller.

Check the connection configuration between the management server andthe controller pair. The management server must have a communicationpath to both controllers in case one controller loses communicationswith the server.

When HP Command View EVA is firststarting up, a password may be enabled onthe controllers, but a password has not beenentered in HP Command View EVA.

Enter the correct password through HP Command View EVA or disablethe password on the controller.

The switches may not be correctly zoned,making a storage system invisible to HPCommand View EVA.

Verify that switches are zoned correctly.

HP Command View EVA may have beenrestarted while there was a communicationfailure between HP Command View EVA andthe controllers. When restart is completed,the storage system that lost communicationwill not be visible.

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.

A storage system may not be visible to HPCommand View EVA because the controllersare waiting for World Wide ID (WWID) tobe entered. This condition will occur if thestorage system has been uninitialized andthe cabinet is power cycled.This may also occur if backend problemsare preventing access to the quorum drives.Once communication is restored, the WWIDalong with the checksum can be re-entered.

Enter the WWID.

Solving security credentials configuration problemsThe 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 isrequired on the management server and must have at least one member (user account). Membershave view and manage capabilities.

• HP Storage Users. Members have view capability only. This group is required only when a groupwith extremely limited use of HP Command View EVA is required.

Access control1. 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 theView 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 userswith the View HP Storage privilege, access is denied.

Solving problems selecting a storage system (Step 2)When selecting a storage system, ensure the status icon displayed for the storage system is a green clustersymbol indicating good health. See Figure 25.

Figure 25 Status icon for a good storage system

If the status icon for the storage system is not a green cluster, it indicates a problem that must be correctedbefore proceeding. Expand the navigation tree to locate the problem. Figure 26 illustrates a storagesystem with a controller problem and a disk enclosure problem.

66 Troubleshooting

Figure 26 Status icon for a bad storage system

Solving problems disabling DR group failsafe mode (Step 3)There are a number of issues that may occur with HP Continuous Access EVA. The following websiteprovides 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 (Step6)

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 thelink and save it to a directory.

NOTE:The XCS firmware image file name has an extension of .sss. The file name contains the controllermodel (200 for EVA4x00, and EVA6x00 or 210 for EVA8x00) and the XCS version. For example,HSV210_6200.SSS is the name of the XCS 6.200 file for the HSV210 controller.

Invalid firmware image file (Status code 21006)If the XCS firmware image file is the wrong image, an Operation failed message is displayed. SeeFigure 27. Click OK to return to the Initialized Storage System Properties window.




































Figure 27 Invalid firmware image file (Status code 21006)

Bad image header (Status code 65)HP Command View EVA sends the XCS controller firmware to the controller in segments. As eachsegment is received, it is validated by the controller. HP Command View EVA monitors each segmenttransfer and displays the transfer status information.

If a problem occurs, the process stops and HP Command View EVA displays the segment transfer thatwas not successful. This is typically caused by a problem in the XCS controller firmware image file or theselection of the wrong firmware image file. See Figure 28. 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 code load sequence again.

3. Ensure that you select the correct firmware image file, and continue the process.

If the process fails again with the same message, download the firmware image file again and repeatthe process.

Figure 28 Bad image header (Status code 65)

Solving problems if the storage system does not come backonline (Step 10)

The system software upgrade should take approximately 10 minutes to complete. If the storage systemdoes not come back within 10 minutes, check the following:

• Determine if the problem is with HP Command View EVA by performing the troubleshooting stepsin “HP Command View EVA problems” on page 61.

• 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 navigationpane.

• Check the storage system event logs.

68 Troubleshooting

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 servicerepresentative for help.

Solving problems with multiple resynchronizations (Step 10)During the upgrade process, both controllers perform a resynchronization simultaneously. This invokes afast restart of the controllers — bypassing execution of lengthy hardware diagnostics. This fast restartallows the controllers to complete the resynchronization sequence before the host timeout period elapsesand the host becomes aware that the storage system is unavailable.

If an event occurs that causes a second resynchronization while the firmware upgrade resynchronizationis still in progress, the controller will terminate with a code of 0b 08 01 00. The following eventscause the controller to resysnchronize automatically:

• Initialization of the storage system• Setting debug flags through the command line interface or OCP• Occurrence of a disk group hardware problem on a Vraid1 virtual disk, or the return of a disk

during this condition• Bad Block Replacement (BBR) performed on a disk• Memory allocation failure or other errors

Every effort should be made to ensure none of these events occur during the upgrade process. Ifcontroller termination occurs due to multiple resynchronizations, contact your HP-authorized servicerepresentative for assistance.


70 Troubleshooting

Index

Aagent options, using, 46analyzing storage system I/O, 25application I/O timeouts, 32array, checking for errors, 17, 36, 42

Bbackup, 32Bad image header error, 68browsers

recommended versions, 34

Cchecking EVA health, time estimate, 17, 36, 42checking hardware status, 17, 42code load restrictions, 38Code Load Storage System-Page 1, 47Code Load Storage System-Page 2, 48collecting configuration data, 18Controller Event log, 36, 44Controller Events page, 36, 44controller events, checking log, 36, 44corrective action codes, 37, 44Critical event check, 36, 44

DDisable Password Access to Storage Systempage, 46disabling passwords, 46documentation

providing feedback, 9downgrading, 59

EEnable Password Access to a Storage Systempage, 56enabling passwords, 56EVA, health check, 17, 36, 42EVAPerf, 25

Hhardware errors, 17, 42help

obtaining, 8host I/O timeouts, managing, 29HP

technical support, 8

HP Command View EVAchecking hardware, 17, 42checking version, 16disabling passwords, 46enabling passwords, 56errors, troubleshooting, 62installing, 33web server, normal interaction, 63

HP Command View EVA, online help, 17HP Command View EVA, upgrading, 33

II/O timeouts

application, 32installation

typical, 33internet browsers

recommended versions, 34Invalid firmware image file error, 67

JJava Runtime Environment, recommendedversions, 34JRE, recommended versions, 34

Kkits, required, 12kits, software, 12

MManagement Agent Options page, 46Management Appliance

errors, troubleshooting, 62web server

normal interaction with HP CommandView EVA, 63

OOCP

adding passwords, 55clearing passwords, 45

online upgrademanaging host I/O timeouts, 29selecting appropriate time, 25

operating systems, and JREs, 34operating systems, recommended browsers, 34


Ppassword protection, 55password protection, removing, 45

Rrecommended browsers, 34Replication Solutions Manager, 36required kits, 12RSM

See Replication Solutions Manager

SSAN Visibility, 18selecting online upgrade time, 25software kits, 12status code

21006, 6765, 68

storage systemchecking hardware, 17, 42checking status, 17, 36, 42passwords, 56

Storage System Password Access page, 46

Ttechnical support

HP, 8service locator website, 9

time estimateadding passwords, 55checking EVA health, 17, 36, 42clearing passwords, 45disabling password access, 46enabling password access, 56

troubleshootingHP Command View EVA errors, 62management appliance errors, 62

Uunmappable hardware folder, 18, 43upgrade preparation, 17, 36, 42upgrading

Replication Solutions Manager, 36upgrading HP Command View EVA , 33

VVCS

minimum version before upgrade, 12verifying software version, 16View Events page, 36, 44

Wweb server, 63websites

HP , 9World Wide Node Name, using, 57WWN, 57

XXCS

downgrading, 59

72

update 6200 firmware

Documents