HP StorageWorks 4x00/6x00/8x00 Enterprise Virtual Array updating product software guide (XCS 6.200) This document applies to the EVA4000/6000/8000 and EVA4100/6100/8100 models only.
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 forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . Product models . . . . . . . . Document conventions and symbols HP technical support . . . . . . HP websites . . . . . . . . . . Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading to WEBES 5.2 . . . . . . . . . . . . . . . . . . . . . . . . Archiving and clearing the error log . . . . . . . . . . . . . . . . . Upgrading WEBES . . . . . . . . . . . . . . . . . . . . . . . . Upgrading HP Replication Solutions Manager (optional) . . . . . . . . . . . Monitoring storage system stability . . . . . . . . . . . . . . . . . . . . Preparing an HP Continuous Access EVA environment for upgrading . . . . .
Figures 1 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 . . . . . . . . . . . . . . . .
Tables 6 1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2 XCS 6.200 Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3 Reference documentation 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 XCS 6.200 Pre-upgrade task checklist . . . . . . . . . . . . . . . . . . . . . . . 13 5 Management software version worksheet . . . . . . . . . . . . . . . . . . . . . . 15 6 HP Command View EVAPerf virtual disk statistics . .
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 Array hardware. NOTE: The procedures in this guide are for upgrading from XCS 5.1xx, 6.000, 6.100 or 6.110 to XCS 6.200.
Document conventions and symbols Table 1 Document conventions Convention Element Medium blue text: Required documentation Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
• Operating system type and revision level • Detailed questions For continuous quality improvement, calls may be recorded or monitored. HP websites For 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 feedback HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to: .
About this guide
1 Getting started This chapter provides information about required kits and reference documentation. Ensure that you have met the outlined requirements and possess all of the required materials before you begin the installation procedures described in this guide. Upgrade paths The 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 6.100 Upgrade directly to 6.
Document Location Required? HP StorageWorks Enterprise Virtual Array compatibility reference Yes HP Command View EVA documentation HP StorageWorks Command View EVA user guide HP StorageWorks Command View EVA installation guide http://www.hp.com/support/manuals Yes HP StorageWorks Storage System Scripting Utility reference Click Storage Software under Storage, and then select HP StorageWorks Command View EVA Software under Storage Device Management Software.
2 Pre-upgrade tasks There are a number of necessary tasks that can be performed prior to beginning the upgrade. Performing these tasks prior to, rather than during, the upgrade minimizes the time required to perform the XCS upgrade procedure. The required tasks differ depending on your system configuration. They focus on upgrading components to ensure they meet the supported configuration for XCS 6.200. Table 4 provides a checklist so you can track your progress as you perform these pre-upgrade tasks.
Upgrading HP Command View EVA, page 32 Time required: 15–20 minutes When to perform: Any time prior to the upgrade Things 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 34 Time required: 10–20 minutes When to perform: Any time prior to the upgrade – Upgrade browser if necessary. – Upgrade JRE if necessary. Upgrading to WEBES 5.
Checking current software versions Estimated 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 correct version as required. Use Table 5 to collect version information for your current software. You must upgrade any software that does not meet the required version.
Software Current version Web browser (required) Required version Locating version information1 Upgrade procedure Internet Explorer 6.0 SP1 or later2 From your browser, select Help > About Internet Explorer. “Upgrading browser and Java Runtime Environment (JRE)” on page 34 Storage Management Appliance (required if the SMA is used for management) 1. 2.1 From the SMA, click Help in the tool bar. 2. Check the default page for the software version.
Figure 2 HP Command View EVA Online Help Checking the storage system hardware Estimated time to complete: 15–20 minutes When to perform: 1–2 weeks prior to the upgrade. Provide enough time to order and replace any failed components. Before upgrading your Enterprise Virtual Array, you should check the operation of the storage system hardware and replace any failed components. This ensures the storage system will be operating properly when the upgrade is performed.
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.
The report can then be used to determine if any of your SAN components are not supported by XCS 6.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 current JRE version from Sun's website: http://www.sun.com/ Installing SAN Visibility SAN Visibility is typically installed on the management server running HP Command View EVA. 1. Download SAN Visibility from the following website: http://h18006.
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 you change it to a name that is meaningful to you. This name is used when generating reports, so it should be one that is easily recognized as being associated with the SAN on which data collection will be done. 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.
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. Information will be collected for all devices connected to this switch. b. Clear Discover cascaded switches. This option automatically detects all switches connected to the switch identified by the IP address. Including all the cascaded switches increases the data collected for the report to include all the devices connected to all the switches.
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 data collection. 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 collect the switch data. 4. Click Start Data Collection.
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: SAN_Visibility@hp.com 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 report 1. Locate the returned report file and double-click on it.
Figure 6 Sample SAN Visibility report Selecting an appropriate time to perform an online upgrade To ensure the success of an online upgrade, selecting the appropriate time is essential. Because the online firmware upgrade is performed while host I/Os are being serviced, the I/O load can impact the upgrade process. Selecting a period of low I/O activity will ensure the upgrade completes as quickly as possible, and will avoid disruptions to host and applications due to timeouts.
Tips for using HP Command View EVAPerf Use HP Command View EVAPerf to identify periods of low I/O activity, during which you can safely perform on online upgrade of the storage system firmware. Use the following tips to ensure that you select an appropriate period during which I/O is low and remains low. NOTE: Before using HP Command View EVAPerf, you may want to configure friendly names to simplify identifying your storage systems, virtual disks, and hosts.
3. When the command has completed, open the file in an ASCII editor. Identify any instances where the IOPS and throughput limits have been exceeded. If the limits have not been exceeded, this may be a good period to perform the upgrade. NOTE: Another option for displaying HP Command View EVAPerf data is to use the -csv command option, which saves the data as comma separated values for importing into a spreadsheet. This may be useful for analyzing large amounts of data.
Figure 7 Sample virtual disk statistics display Table 6 HP Command View EVAPerf virtual disk statistics Counter Description Read Hit Req/s The number of read requests per second completed from the array cache memory. Data may reside in the cache memory due to a previous cache miss or because of a prefetch operation generated by a sequential read data stream. Read Hit MB/s The rate at which data is read from the array cache memory because of read hit requests.
Displaying EVA performance data using Windows Performance Monitor An 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 performance data. See the HP StorageWorks Command View EVA user guide for more information about using Windows Performance Monitor.
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 the HP-UX host may cause corruption and make the system unrecoverable.
• discovery_threads=1 To check or set Linux parameters, use the set_parm executable found in the /opt/hp/ directory. When executed, the options to change timeout values are displayed. NOTE: • The timeout values must be increased for Emulex single path (without multipath support) and QLogic single path being used in the environment. This is not only important for online upgrades but for general data integrity. • Online controller firmware upgrades are supported with Linux boot devices.
IBM AIX Checking or changing timeouts AIX 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 reservations are not supported. Algorithm fail_over Sets the load balancing algorithm to fail_over. All I/O uses a single path. The remaining paths are in standby mode. The value round_robin is not supported.
When to perform: Any time prior to the upgrade HP Command View EVA 8.0.1 is required with XCS 6.200. Check the current version and upgrade the software 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 View EVA Version HP Command View EVA 6.0 HP Command View EVA 6.0.1 HP Command View EVA 6.0.2 HP Command View EVA 7.0 HP Command View EVA 7.0.1 HP Command View EVA 8.
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 appear on the desktop. • The software is available from the Start menu (for example, Start > Programs > HP Command View EVA). If you installed the software suite on an SMA, the software is not available from the Start menu.
When to perform: Any time prior to the upgrade WEBES is optional diagnostic monitoring software. If WEBES is currently installed, it must be upgraded to version 5.2, which is required with HP Command View EVA 8.0.1. To download the WEBES 5.2 software kit, go to the following website: http://h18023.www1.hp.com/support/svctools/webes/ Archiving and clearing the error log Before upgrading WEBES, perform these steps to archive and clear the error log.
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.
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 to correct the problems. In some cases, it may be necessary to call your HP-authorized service representative to fix the problem. 3. Verify that no changes to the storage system configuration are in progress.
• Before you upgrade any storage system in an HP Continuous Access EVA relationship, ensure that all storage systems in the storage network are running the same version of controller software. This will ensure that when you upgrade one storage system, the storage network will have only two versions of controller software. You cannot have more than two versions in an HP Continuous Access EVA environment.
Before beginning the upgrade, the current configuration information should be collected and saved. This information can be used to restore the existing configuration if necessary. The configuration data is saved to a series of files stored in a location other than on the storage system. HP Storage System Scripting Utility (called the utility) is used to collect configuration information.
Pre-upgrade tasks
3 Upgrading the Enterprise Virtual Array The following steps guide you through the process of upgrading the system software. Ensure that you follow them carefully and in the specified order. Table 9 on page 41 provides a checklist so you can track your progress as you perform the upgrade. Make sure you have all the items indicated before beginning the upgrade. Table 9 Upgrade task checklist Step 1.
Step 7. Entering storage system passwords, page 55 Time required: 10–15 minutes − Enter the OCP password. − Enable password access in HP Command View EVA. Step 8. Resuming storage system operation, page 57 Time required: Varies − Restart applications accessing the storage system if an offline upgrade was performed. − When running HP Continuous Access EVA, enable failsafe mode on all DR groups. − If you changed any host LUN timeout values, reset them to their original values. − Enable ISEE (if used).
Figure 10 Hardware Folder Properties window c. If a problem is indicated, continue to expand the navigation tree under the Hardware folder until you see a hardware component icon with an attention or warning icon on it. d. Click the component icon to display the properties window. The Operational state box indicates if there is a hardware error. Figure 11 Checking operational states 2. Verify that there are no hardware components in the Unmappable Hardware folder. a.
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 the last 48 hours. have occurred within The most recent 400 events are displayed.
4. Verify that no changes to the storage system configuration are in progress. For example, you should not be in the process of creating a virtual disk. Configuration changes should not be made within 48 hours before beginning the upgrade. NOTE: • The leveling process does not impact the upgrade. If leveling is in progress, the upgrade can be performed. The leveling will be suspended during the upgrade and resumed when the upgrade is complete.
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).
CAUTION: Before upgrading the controller firmware, ensure that the storage system configuration is stable and is not being changed in any way. If any configurations changes are in progress, monitor them using HP Command 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 synchronous mode before upgrading.
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 opens and 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 Before text Information file Description Text file with information about the new code and upgrade requirements. Displayed by HP Command View EVA and not sent to the controller. 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.
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 load process 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. During this interval both controllers resync and begin operating on the new firmware code.
Figure 18 Verifying XCS version after upgrading Step 6. Upgrading disk drive firmware Estimated time to complete: Varies depending on the number of disk drives that require upgrading and the I/O load on the storage system. It can take 30 seconds to 3.5 minutes per drive to upgrade the firmware. The firmware on all disk drives can be upgraded online.
Upgrading the firmware Upgrade 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: http://www.hp.com/support/evadiskfirmware a. When you download the file from the web, the file is downloaded as a zip file. Store the file to a local directory. NOTE: It is recommended that you use the default directory of C:\Program Files\Hewlett-Packard\Sanworks\CodeLoad.
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 drives require firmware upgrades. Figure 21 Code Load Disk Drives — Page 2 window 8. Click Next step. The disk drive code load operation begins. A status page opens indicating the progress as each disk drive is upgraded.
The disk drives are upgraded sequentially. Depending upon the I/O load on the storage system, it can take 30 seconds to 3.5 minutes per drive to upgrade the firmware. The status is updated at 45 second intervals, so you must wait to see which disk drives are complete. CAUTION: If you select any array in the Navigation pane to manage it, the disk drive upgrade stops. For example, if 10 of 27 drives have completed the upgrade when you selected the array, only those 10 drives will be upgraded.
Figure 23 Code Load Disk Drives — Page 3 window Upgrading firmware on an individual disk If it is necessary to upgrade the firmware on an individual disk, the firmware and installation instructions can be downloaded from the following website: http://www.hp.com/support/evadiskfirmware NOTE: Online code load of disk drive firmware can also be done to individual disks by this method. Step 7.
• Can include numbers 0 - 9 • Can include the following characters: ! “ # $ % & ‘ ( ) * + , - . / : ; < = > ? @ [ ] ^ _ ‘ { | } • Cannot include the following characters: space ~ \ Entering the password on the OCP Using the following procedure to enter the password on the storage system controllers. The password can be entered from either controller. 1. With either of the default menus (Storage System Name or World Wide Name) displayed, press three times to display System Password. 2.
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 password access. 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 operation Estimated time to complete: Varies.
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.
4 Downgrading the Enterprise Virtual Array Support for downgrading from XCS 6.200 depends on the minimum supported versions of your EVA controller hardware. Due to metadata changes in XCS 6.200, to downgrade it will be necessary to reinitialize the storage system and restore all data. Before proceeding with a downgrade, you must contact HP Services to determine if a downgrade is allowed in your configuration and, if so, to schedule the procedure.
Downgrading the Enterprise Virtual Array
5 Troubleshooting This chapter provides troubleshooting information should you encounter any problems when updating the system software. Each troubleshooting section is cross-referenced to the corresponding step in “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 support representative for help if this information does not help your problem.
1. Check the HP StorageWorks Enterprise Virtual Array compatibility reference to ensure that the version of HP Command View EVA you are using is compatible with the XCS version. For complete details on EVA software compatibility, see the “HP Command View EVA interoperability support” table in the HP StorageWorks Enterprise Virtual Array compatibility reference. See “Required documentation” on page 11 for the link to this document. 2. Determine if HP Command View EVA has been restarted. 3.
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 command generating this message again. If you still cannot see the storage system, stop and restart HP Command View EVA.
Possible Cause Corrective Action 503 Error: HP Command View EVA may be down when a browser makes a request. The web server returns a 503 (No Service) error because it cannot access the page. Retry the request when HP Command View EVA is up. Browser timeout: The appliance may be down or the web server may be unavailable when a browser makes a request to HP Command View EVA. In this case, the browser will time out internally. Retry the request when the appliance and HP Command View EVA are up.
Corrective action Table 12 Possible causes and corrective actions when no storage system found Possible Cause Corrective Action The management server may not be able to communicate with either controller. Check the connection configuration between the management server and the controller pair. The management server must have a communication path to both controllers in case one controller loses communications with the server.
4. If the user belongs to the HP Storage Users group and the web pages does not allow access to users with the View HP Storage privilege, access is denied. 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 cluster symbol indicating good health. See Figure 25.
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 website provides access to information for troubleshooting problems with HP Continuous Access EVA: http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?&lang=en&cc=us& prodTypeId=18964&prodSeriesId=471572&lang=en&cc=us Click Troubleshoot a problem under Tasks for HP StorageWorks Continuous Access EVA Software.
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 each segment is received, it is validated by the controller. HP Command View EVA monitors each segment transfer and displays the transfer status information. If a problem occurs, the process stops and HP Command View EVA displays the segment transfer that was not successful.
1. Run HP Command View EVA and log in. 2. Select the storage system whose logs you want to view. 3. Click View events to view the event logs that can be displayed. If none of the above recommendations resolves the problem, contact your HP-authorized service representative for help. Solving problems with multiple resynchronizations (Step 10) During the upgrade process, both controllers perform a resynchronization simultaneously.
Troubleshooting
Index A agent options, using, 46 analyzing storage system I/O, 25 application I/O timeouts, 32 array, checking for errors, 17, 36, 42 B backup, 32 Bad image header error, 68 browsers recommended versions, 34 C checking EVA health, time estimate, 17, 36, 42 checking hardware status, 17, 42 code load restrictions, 38 Code Load Storage System-Page 1, 47 Code Load Storage System-Page 2, 48 collecting configuration data, 18 Controller Event log, 36, 44 Controller Events page, 36, 44 controller events, check
P password protection, 55 password protection, removing, 45 troubleshooting HP Command View EVA errors, 62 management appliance errors, 62 R U S V recommended browsers, 34 Replication Solutions Manager, 36 required kits, 12 RSM See Replication Solutions Manager SAN Visibility, 18 selecting online upgrade time, 25 software kits, 12 status code 21006, 67 65, 68 storage system checking hardware, 17, 42 checking status, 17, 36, 42 passwords, 56 Storage System Password Access page, 46 T technical suppo
