HP Enterprise Virtual Array Updating Product Software Guide (XCS 11001100) Abstract This guide describes how to upgrade controller software, disk drive firmware, and related EVA management software on HP EVA4400/6400/8400s and HP P63x0/P65x0 EVAs. General references to HP P6000 Command View can also refer to earlier versions of HP Command View EVA.
© Copyright 2012 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 1 Getting started...........................................................................................5 Upgrade overview....................................................................................................................5 Upgrade paths.........................................................................................................................5 Reference documentation....................................................................................................
Upgrading disk drive firmware in an HP P6000 Continuous Access environment........................39 Checking the disk grouping policy............................................................................................39 Saving array configuration data...............................................................................................40 3 Upgrading the Enterprise Virtual Array........................................................42 Task checklist........................................
1 Getting started This chapter provides information about required kits and reference documentation. Before you perform the upgrade procedures, ensure that your system meets the requirements. IMPORTANT: HP P6000 Command View (formerly HP StorageWorks Command View EVA) supports all HP P6000 Enterprise Virtual Arrays, EVA4000/6000/8000, EVA4100/6100/8100, EVA4400/6400/8400, and P63x0/P65x0 EVA storage systems.
Reference documentation Table 1 (page 6) identifies the documentation you should have available when upgrading the array.
Required kits Before you begin the upgrade, you must download the XCS 11001100 controller software from the following website: http://www.software.hp.com/ Under Product Category, click HP Storage. The Storage Software screen appears. At the top of the screen, with the Software Depot button selected (default), enter XCS 11001100 in the Search box and click the Search button . The Product Category result screen displays EVA 4400,6400,8400 XCS 11001100 and EVA P63x0, P65x0 XCS 11001100.
If you have questions or need assistance, go to http://welcome.hp.com/country/us/en/ wwcontact_us.html and select your country/region.
2 Preparing for the upgrade HP recommends that before starting the XCS upgrade, you perform tasks listed in Table 2 (page 9) to minimize the time required to complete the upgrade. The tasks you perform depend on your system configuration and the HP P6000 Command View implementation. These tasks focus on upgrading system components to ensure they meet the supported configuration for XCS 11001100. NOTE: Be sure to record the XCS controller software version you are using.
Table 2 Pre-upgrade task checklist (continued) Task Task complete When to perform: As close as possible to the upgrade “Managing an SVSP configuration for an online upgrade” (page 32) Time required: Varies When to perform: As close as possible to the upgrade “Backing up all array data” (page 32) Time required: Varies When to perform: As close as possible to the upgrade “Upgrading HP P6000 Command View” (page 32) Time required: 15–20 minutes When to perform: Anytime before the upgrade “Upgrading browsers a
Checking management software versions Estimated time to complete: 10–15 minutes When to perform: Anytime before the upgrade When upgrading the system software, you must upgrade related management software to the required version. Use Table 3 (page 11) to collect version information for your current software. NOTE: For details on array software compatibility, see Table 1.0, HP P6000 software solution compatibility and Table 2.
Checking the HP P6000 Command View version 1. Open HP P6000 Command View on the management server or the management module, if applicable. (This procedure is for server-based management.) The EVA Storage Network Properties window (Figure 1 (page 12)) opens. Figure 1 Storage Network Properties window 2. Click Help in the Session pane. The full version number is displayed at the top of the online help window (Figure 2 (page 12)).
a. Examine the Hardware folder in the navigation pane to see if there are any hardware caution or warning conditions. If there are any hardware caution or warning conditions, click the Hardware folder to expand it. The Hardware Folder Properties window opens (Figure 3 (page 13)). The Operational State field indicates if there is a hardware problem. Figure 3 Hardware Folder Properties window b. c. d. Select the array in the navigation pane and click Refresh to update the cache.
3. Replace any hardware components that have failed. NOTE: For information about replacing any components, see the user guide for your array model. See Table 1 (page 6) for links to these documents. TIP: If you see a yellow attention icon, you may still be able to perform the upgrade (for example, when leveling is occurring). If any unusual icons are visible, check with your HP-authorized service representative before doing the upgrade.
NOTE: The SAN Visibility version you are running may be a later version than what is shown in the examples that follow. SAN Visibility requires Java 2 Runtime Environment (JRE) 1.5.0 Update 1 or later. You can download the most current JRE version from the following website: http://www.java.com/ Installing SAN Visibility You typically install SAN Visibility on the management server running HP P6000 Command View. 1.
d. e. f. Select the fabric in the tree view. Enter a name in the Component Group Name box. You can use the default fabric name, but HP recommends that you change it to a name that is meaningful to you. This name is used when generating reports, so it should be one that is easily recognized as being associated with the fabric on which data collection will be done. (Mouse-over pop-ups provide detail on SAN settings.) Click Rename.
5. Select Host Settings and enter the following information: • Under Discover Host, select one of the following options: • IP Address: Enter the IP address of the host. • Subnet: To discover hosts for a range of IP addresses: 1. Enter the starting IP address in Start at IP Address. 2. Enter the limiting IP address in Stop at IP Address. • Enter the access information as required, to initiate host discovery. • Click Discover Hosts to discover the physical hosts and the associated virtual machines.
Creating a report automatically 1. Select Data Collection. 2. Select the fabric for which you want to create a report from the Select a switch group for data collection list. Select the Collect data for all switch groups check box to create reports for all fabrics. Clear the Capture performance data check box. To collect switch performance data, leave this option selected. Selecting this option will increase the amount of time required to collect the switch data.
3. 4. 5. 6. 7. 8. Clear the Capture performance data check box. To collect switch performance data, leave this option selected. Selecting this option will increase the amount of time required to collect the switch data. Select the Mask IP address check box if you do not want to send the IP address information (in the raw report) outside your network. Select a format for the report by selecting HTML Report, Microsoft Excel Report, or both. Under Data Collection, click Start.
4. In the navigation pane, click High Level Fabric Summary. The High Level Fabric Summary window opens (Figure 5 (page 19)). This report will identify the firmware and/or driver version that is currently running on your switches (including the HSV300–S embedded switch controller) and HBAs.
5. To review update recommendations for your switches and HBAs, select the applicable folder on the left side of the window. In Figure 5 (page 19), it is the folder called MySwitchGroup. Look for the group name you created in step 2 of “Using SAN Visibility” (page 15). The Best Practices and Recommendations window opens (Figure 6 (page 21)).
Evaluating your configuration Consider the following factors when determining if an online upgrade is appropriate for your environment: • Queuing host I/O—After the upgrade, the array performs a resynchronization. During the resynchronization, host I/O is queued to the host, which can create a backlog of requests for processing when the array is able to respond.
◦ Mirrorclones: For each mirrorclone, go to the Vdisk – General Properties window of the original virtual disk and record the value listed in the Requested capacity box. ◦ Containers: For each container, go to the Container properties window and record the value listed in the Capacity box. To ensure a resynchronization time of less than 60 seconds when performing an online upgrade, the total virtual mapped capacity should be less than 4750 TB.
Selecting a time to perform an online upgrade To ensure the success of an online upgrade, selecting the appropriate time is essential. The two factors that most affect this selection are: • Criticality of business applications—Do not select a time that could affect critical business applications. • I/O load—Select a period of low I/O activity to ensure that the upgrade is completed as quickly as possible, and to avoid disruptions to hosts and applications due to timeouts.
HP P6000 Performance Data Collector command options Use the following options with the HP P6000 Performance Data Collector commands: • -csv: Uses comma-separated output. This format is useful for importing large amounts of data into a spreadsheet for analysis. • -cont n: Runs the command continuously at an interval specified by n. The default interval is one second. • -dur n: Specifies the duration of a continuous mode session.
3. Identify instances where IOPS are at a minimum as periods to consider for performing the upgrade. The following configurations and performance levels have been validated by HP for online upgrade of controller software and disk drive firmware. All configurations include the use of HP P6000 Continuous Access.
3. When the command has finished executing, open the file in an ASCII editor. The virtual disk information will be similar to that shown in Figure 7 (page 27). Activity is reported for each controller accessing a virtual disk. The total activity for each virtual disk is the sum of the reported activity for each controller. A virtual disk can be a snapshot, snapclone, or DR group member. In the output, ID (identification) is used interchangeably with virtual disk.
Table 5 HP P6000 Performance Data Collector virtual disk statistics (continued) Counter Description Write Req/s The number of completed write requests per second to a virtual disk received from all hosts. Write requests may include transfers from a source array to this array for data replication and host data written to snapshot or snapclone volumes. Write MB/s The rate at which data is written to the virtual disk by all hosts; includes transfers from the source array to the destination array.
IBM AIX Checking or changing timeouts AIX requires the disk settings shown in Table 6 (page 29) for the native multipath drives. Table 6 IBM AIX timeout settings Setting Value Description PR_key_value not applicable 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.
Table 8 Emulex driver parameters Parameter Single path With Multipulse HPELXLPFC y — nodev_timeout 60 10 qdepth 30 16 discovery_threads 1 32 To check or set Linux parameters, use the set_parm executable located in the /opt/hp/ directory. When executed, the options to change timeout values are displayed. NOTE: • You must increase timeout values for Emulex single path (without multipath support) and QLogic single path used in this environment.
NOTE: OpenVMS tolerates the controller reboot that occurs at the end of the controller software upgrade process. Disks on the controller display the Mount Verify status during the controller reboot but return to Mounted status and resume I/O operations when the controller reboot is complete. You do not need to change any OpenVMS default settings when performing an online controller software upgrade.
NOTE: • You must increase timeout values for Emulex single path (without multipath support) and QLogic single path used in this environment. This is important for both online upgrades and general data integrity. • Online controller software upgrades are not supported with Xen Citrix boot devices. Managing application I/O timeouts for an online upgrade Applications are typically insulated from the online controller software upgrade by the operating system and HBA driver software.
HP P6000 Command View can be implemented in two ways: • Server-based management — HP P6000 Command View is installed on a management server connected to the array, providing management of multiple HP EVAs. All components of the software suite (HP P6000 Command View, HP P6000 Performance Data Collector, HP Storage System Scripting Utility, SMI-S EVA) are installed. Server-based management applies to all array models. • Array-based management — Beginning with HP P6000 Command View 8.
Command View Enterprise Virtual Array Performance Monitor and SMI-S CIMOM are selected by default. 9. Click Next. The Select Security Groups Configuration window opens. 10. Click Next. The installation summary window opens. 11. Review the pre-installation summary. Click Install. NOTE: The value for Required Disk Space shown in the Pre-Install Summary dialog represents the file size of files the installer will load; the size displayed in Add/Remove Programs is determined by Windows. 12.
1. Connect a server with a DVD drive to the management module port (1, Figure 8 (page 35)) on the controller enclosure. Figure 8 Management module 2. 3. Insert the installation DVD into the drive. Open a browser and navigate to the P6000 Control Panel: https://HP array IP address:2373 NOTE: • If you have not previously set the IP address for the management module, the default is 192.168.0.1.
Verifying installation on the management module To verify that the management module software was upgraded successfully: 1. On the P6000 Control Panel login window, log in as an HP EVA administrator (user name admin and the password). NOTE: 2. If set before the upgrade, the password is maintained during the upgrade process. The P6000 Control Panel GUI appears. Click View detailed system information and verify the operation state, XCS version, and management module software version.
proactive notification, but do not need proactive service delivery and integration with a management platform. • HP Insight Remote Support Advanced: This software provides comprehensive remote monitoring and proactive service support for nearly all HP servers, storage, network, and SAN environments, plus selected non-HP servers that have a support obligation with HP. It is integrated with HP Systems Insight Manager.
Figure 9 View Events window c. Select Controller Event Log. The Controller Events window (Figure 10 (page 38)) opens in a new browser window. Figure 10 Controller Events (Initialized system) window d. Check the Severity field to determine if any unexpected critical events have occurred. If critical events have occurred, click the More icon to see the corrective action and perform the steps outlined in the corrective action to correct the problems.
When upgrading an array in an HP P6000 Continuous Access environment, the following requirements must be met: • Perform the controller software upgrade using the local management server (the server running HP P6000 Command View that is local to the array being upgraded). • Before you upgrade the controller software, you must upgrade HP P6000 Command View (and layered applications) to the required version on both the source and destination arrays.
1. Verify the disk grouping policy setting: a. In the navigation pane, select the storage system being upgraded. b. Select System Options. c. Under Configuration, select Set system operation policies. d. Check the Device addition policy field: i. If field indicates manual, you can proceed with the upgrade. ii. If field indicates automatic, change it to manual and click Save. Continue with Step 2. 2. Restart Controller A: NOTE: a. b. c. d. e. f.
3. Enter SELECT SYSTEM system-name, where system-name is the name of the array. The array name is case sensitive. If there are spaces in the name, enclose the name in quotes. (For example, SELECT SYSTEM “Large EVA”.) 4. Enter CAPTURE CONFIGURATION, specifying the full paths and filenames of the output files for the configuration data. The configuration data is stored in a series of one to five files, which are scripts. The file names begin with the name you select, followed by the restore step.
3 Upgrading the Enterprise Virtual Array The procedures in this chapter guide you through the process of upgrading the system software. Follow them carefully and in the order specified. Table 9 (page 42) provides a checklist so you can track your progress. Make sure you have all the items indicated before starting the upgrade. NOTE: If you experience any problems when performing the XCS upgrade procedure, see “Troubleshooting” (page 62) for assistance.
a. Examine the Hardware folder in the navigation pane to see if there are any hardware caution or warning conditions. If there are any caution or warning conditions, click the Hardware folder to expand the navigation tree. The Hardware Folder Properties window (Figure 11 (page 43)) opens. The Operational State box indicates if there is a hardware problem. Figure 11 Hardware Folder Properties window b. c. d. Select the array in the navigation pane and click Refresh to update the cache.
TIP: If you see a yellow attention icon, you may still be able to perform the upgrade (for example, when leveling is occurring). If you are unsure about an icon, or if you are unable to resolve the error, contact your HP-authorized service representative for assistance. 4. Using HP P6000 Command View, examine the controller event log and check for any critical events. a. In the navigation pane, click the icon of the array you want to upgrade in the navigation pane. b. Click View Events.
To avoid generating unnecessary events and alerts during the upgrade, enable UISM in HP P6000 Command View. This will be used by HP Insight Remote Support to indicate the array is in service mode. 1. Open HP P6000 Command View and select the array for which you want to enable UISM. 2. Select System options. 3. Select Configure User-Initiated Service Mode (UISM) under the Service section. The Configuring User-Initiated Service Mode window opens. 4.
Step 5. Upgrading the controller software Estimated time to complete: 25–30 minutes CAUTION: • Stop all storage modification jobs (such as creation, deletion, shrinkage, expansion, and presentation) 30 minutes before starting the controller software upgrade. • Before upgrading the controller software, ensure that the array configuration is stable and is not being modified.
6. Click Continue to proceed or Cancel to exit the procedure. The Code Load Storage System – Page 1 window (Figure 16 (page 47)) opens. Check the box “I have completed the storage system and SAN checks outlined in the HP StorageWorks Enterprise Virtual Array Updating Product Software Guide for my storage system version.” and click Next Step (which is disabled if the box is not checked). 7. Figure 16 Code Load Storage System — Page 1 window 8.
Figure 17 Code Load Storage System — Page 2 Click Next step to perform automated readiness checks. The Performing storage system checks window opens. The Code Load Storage System — Page 3 window opens, confirming verification. 11. Click Next step to proceed with the upgrade. The Code Load Storage System — Page 4 window opens.
Figure 18 Code Load Storage System — Page 4 window 12. Click Browse to navigate to the controller software image file (created from the downloaded ISO image) (see “Required kits” (page 7)) and select the appropriate file (Table 10 (page 49)). Table 10 Controller software For this array: Select this file: P6000 \HSV340_360\11001100\340_360_11001100.SSS EVA4400 \HSV300\11001100\300_11001100.SSS EVA6400 \HSV400\11001100\400_11001100.SSS EVA8400 \HSV450\11001100\450_11001100.SSS 13.
Figure 20 Code Load Storage System — Page 5 window The new controller software is copied to the controllers and validated (Figure 21 (page 50)). Figure 21 Code load processing page The upgrade process begins and the Initiating firmware code load page opens (Figure 22 (page 51)). This page is displayed while the upgrade file components are processed.
Figure 22 Initiating firmware code load page CAUTION: If you are performing an upgrade on an EVA6400/8400 during heavy I/O load, processing of the System Data Collector file component could time out and one of the following error messages may appear: If either error message appears, click OK. Another message appears, indicating that the array is unresponsive; wait for communication to be re-established between HP P6000 Command View and the array.
15. A final Confirm System Code Load window opens (Figure 24 (page 52)). Enter YES (all uppercase) and click Code Load System to proceed. Figure 24 Final code load confirmation window 16. Select the array in the navigation pane and the Initialized Storage System Properties window appears (Figure 25 (page 52)). Verify the that the version of the controller software in the Attributes box is 11001100.
IMPORTANT: • After upgrading the controller software, consider the following: If the array is initialized after the upgrade, the default data replication protocol will be HP SCSI FC Compliant Data Replication Protocol, which is not currently supported in HP P6000 Continuous Access configurations with EVAx000 or EVAx100 arrays.
Figure 26 I/O tab of Disk Enclosure Properties window NOTE: The Firmware revision fields are different for EVAx400 and P6000 disk enclosures. If the fields Assembly serial number, Hardware revision, and Hardware type on the I/O tab of the Disk Enclosure Properties window are blank, you can optionally reset the I/O modules to clear the blank fields after the I/O module firmware upgrade has completed successfully. Note that blank fields do not affect the array's ability to process host I/O.
19. Determine whether the component blocking the upgrade is an I/O module or a disk drive: a. Refer to the list of I/O modules you recorded in Step 17. If the operational state display of the offending I/O module is something other than Good or Loading firmware or if the reported firmware version is the same as previously recorded in Step 17 indicating that the I/O module has not been upgraded, try resetting each I/O module as described in “Resetting the I/O module” (page 55).
To reset the I/O modules individually: • Remove and then reinsert the I/O module in each disk enclosure. See the HP Disk Enclosure I/O Module Replacement Instructions. See “Related information” (page 70) for the link to this document. • Insert a serial cable into the I/O module and issue the reset command using the serial line (requires HP Services). To power cycle the array: 1. Complete an orderly shutdown of both controllers from HP P6000 Command View. Then, power down the array: 2.
disk drive firmware complements the operation of the controller software and, for best results, the two should be used together. CAUTION: When upgrading the disk drive firmware: • Do not power off any components or perform controller resynchronization or reboot. • Upgrade the disk drive firmware after you upgrade the array software. • Perform the upgrade during a period of low I/O to minimize the time it takes to restore information to the drive after the upgrade.
Figure 28 Code Load Selection window – disk drives Choose Code Load Disk Drives On Line and click Select to proceed or Cancel to exit the procedure. A warning Confirm Disk Drive Code Load confirmation window opens Figure 29 (page 58). Figure 29 Confirm Disk Drive Code Load Warning Click Continue to proceed or Cancel to exit the procedure. The Code Load Disk Drive Online — Page 1window opens (Figure 30 (page 58)). In Step 1, Click Browse to select the bundled image zip file.
8. 9. Click Browse and navigate to the zip file, or manually enter the path to the zip file (Step 3). Click Next step. All disk drives are scanned for configuration information and upgrade eligibility. The results are displayed in the Code Load Disk Drives Online – Page 2 window. Figure 31 Code Load Disk Drives On Line – Page 2 window 10. Click Next step. The disk drive firmware upgrade begins. A status page opens, indicating the progress of the upgrade for each disk drive (Figure 32 (page 60)).
Figure 32 Code Load Disk Drives On Line – status window When all disk drives have been upgraded, the Code Load Disk Drives On Line – Page 3 window opens (Figure 33 (page 60)), indicating that the drives have been upgraded successfully. Figure 33 Code Load Disk Drives On Line – Page 3 window 11. Click Finish. Upgrading firmware on a single disk If you need to upgrade the firmware on a single disk, download the firmware and installation instructions from the following website: http://www.hp.
Upgrading firmware on a single disk can be performed online or offline, unless the disk is a member of a disk group that contains Vraid0 virtual disks. To upgrade disks that contain Vraid0 virtual disk data, halt all I/O to Vraid0 virtual disks (other Vraid virtual disks can continue to service host I/O). TIP: Earlier versions of HP P6000 Command View required you to either delete the Vraid0 virtual disks or ungroup the disks individually before upgrading disk drive firmware. Step 7.
4 Troubleshooting This chapter provides information to help you solve problems you may encounter with different parts of your array after completing your upgrade. HP P6000 Command View This section describes issues that can impact HP P6000 Command View and its ability to communicate with the array.
Resolution Click OK. Wait one to five minutes, depending on the size of the array, and retry the command generating this message. If you still cannot see the array, stop and restart HP P6000 Command View. HTTP status 404, not found or status 503, no service Symptom The content pane shows the message HTTP status 404, not found or HTTP status 503, no service. Cause These messages indicate that the server responded but could not find the requested page.
Cause HP P6000 Command View may have lost communication with the controllers. Two possible scenarios follow: • The management server HBA may have timed out commands to the controllers. See “Unknown storage system” (page 63). • The controllers are running a version of XCS that HP P6000 Command View does not recognize. See “Unknown storage system” (page 63).
Table 12 Possible causes and corrective actions when no array is found (continued) Possible cause the restart is complete, the array that lost communication will not be visible. Corrective action 3. Verify that switch zoning is correct. 4. Click Discover. An array may not be visible to HP P6000 Command Enter the WWID of your system. View because the controllers are waiting for you to enter the World Wide ID (WWID). This condition occurs if the arraywas uninitialized and the rack is power cycled.
Table 13 Disk drive firmware upgrade errors and workarounds Error Workaround Drive code load - Failed to write firmware to drive buffer Check the drive properties in HP P6000 Command View for problems. Resolve the problem and restart the disk drive firmware upgrade. Drive code load - The disk cannot be code loaded because Restart the disk drive firmware upgrade.
If the status icon for the array is not green, it indicates a problem that you must correct before proceeding. Expand the navigation tree to locate the problem. Figure 35 (page 67) illustrates an array with a disk enclosure problem. Figure 35 Status icon for an array in bad or questionable health Disabling DR group failsafe mode Issues with DR groups may occur with HP P6000 Continuous Access.
Bad image header (Status code 65) HP P6000 Command View transfers the XCS controller software to the controller in segments. As each segment is received, it is validated by the controller. HP P6000 Command View monitors each segment transfer and displays the transfer status information. If a problem occurs, the process stops and HP P6000 Command View displays the unsuccessful segment transfer.
If an event occurs that causes a second resynchronization while the upgrade resynchronization is still in progress, the controller will terminate with a code of 0b 08 01 00.
5 Support and other resources Contacting HP HP technical support Telephone numbers for worldwide technical support are listed on the HP support website: http://www.hp.
• HP Software Depot: http://www.software.hp.com • HP Single Point of Connectivity Knowledge (SPOCK): http://www.hp.com/storage/spock Typographic conventions Table 14 Document conventions Convention Element Medium blue text: Table 14 (page 71) Cross-reference links and email addresses Medium blue, underlined text: http:// www.hp.
Index A agent options using, 45 analyzing array I/O, 24 array checking for errors, 12, 42 XP P9000, 32 B backing up data, 32 Bad image header error, 68 browsers recommended versions, 36 C capacity virtual mapped, 22 checking hardware status, 12, 42 checklist pre-upgrade task, 9 upgrade task, 42 cluster symbol, 66 code load failure VMware, 31 Command View version verifying, 12 components failed, 12 configuration SAN, 14 configuration data collecting, 14 controller events checking log, 44 Controller Events
L T limits throughput, 26 LUNs Vraid0, 32 technical support HP, 70 throughput limits, 26 time estimate adding passwords, 61 clearing passwords, 45 disabling password access, 45 M management module, 34 software, 7 management server interaction with HP P6000 Command View, 63 O OCP, 35 adding passwords, 61 clearing passwords, 45 offline upgrade, 5 online upgrade, 5 configuration evaluation, 22 considerations, 22 managing host I/O timeouts, 28 selecting when to do, 24 success factors, 22 U UISM, 44 upgrad