Page 1
HP Enterprise Virtual Array Updating Product Software Guide (XCS 10000000) Abstract This guide describes how to upgrade controller software, disk drive firmware, and related EVA management software on the HP EVA4400 and HP EVA6400/8400. HP P6300/P6500 EVAs are not included in this document because they are already running XCS 10000000 and do not need an upgrade.
Contents 1 Getting started...................5 Upgrade overview........................5 Upgrade paths.........................5 Reference documentation......................6 Required kits..........................6 2 Preparing for the upgrade ................9 Checking the controller software version..................9 Checking management software versions..................9 Checking the array hardware....................11 Checking and upgrading your SAN infrastructure...............12 Collecting SAN configuration data using SAN Visibility............13 Installing SAN Visibility....................13 Using SAN Visibility......................13 Obtaining a report from HP....................16...
Page 4
Saving array configuration data....................39 Task checklist.........................40 3 Upgrading the Enterprise Virtual Array............43 Step 1. Checking the health of the Enterprise Virtual Array............43 Step 2. Configure User-Initiated Service Mode (UISM)..............45 Step 3. Disabling array passwords....................46 Step 4. Halting all host access to the array for an offline upgrade ..........46 Step 5.
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 Array (EVA) models. General references to HP P6000 Command View may also refer to earlier versions of HP Command View EVA.
User Guide Click Disk Storage Systems under storage, and HP P6300/6500 Enterprise Virtual Array then select HP 4400 Enterprise Virtual Array, or User Guide HP 6400/8400 Enterprise Virtual Array, or HP P6300/P6500 Enterprise Virtual Array under HP P6000 Enterprise Virtual Array Release P6000 EVA Disk Arrays.
Page 7
You must also obtain a supported version of HP P6000 Command View. When you purchase HP P6000 Command View, you can choose to receive a software CD or an E-Delivery kit. If you choose an E-Delivery kit, you will receive an email from HP with download instructions. For E-Delivery kits, be sure to save the HP mail with the download instructions.
Page 8
1 1. Review the delivery address information for physical CD delivery or select the location for the image file to be stored, and click Submit. If you have questions or need assistance, go to http://welcome.hp.com/country/us/en/ wwcontact_us.html and select your country/region. Getting started...
2 Preparing for the upgrade Before starting the XCS upgrade, you should perform several tasks 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 10000000.
Page 10
Table 2 Management software version worksheet (continued) Software Current Required version Locating version information Upgrade procedure version (minimum) 1.5.0_04 or later Open the Windows control “Upgrading browsers and JRE” (page panel. Double-click the Java icon. On the General tab, click About.
Click Help in the Session pane. The full version number is displayed at the top of the online help window (Figure 2 (page 11)). If the version is earlier than the minimum supported version, it must be upgraded. Figure 2 HP P6000 Command View online help TIP: The full version number is also shown at the bottom of the login screen.
If a problem is indicated, expand the navigation tree under the Hardware folder until you see a hardware component icon with an attention or warning icon on it. Click the component icon to display the properties window (Figure 4 (page 12)).
and operating system combination that applies to your environment. Expand Host Bus Adapter (HBA) to view supported HBA details. Expand Fibre Channel Switch to view supported switches. To view details for a supported switch, navigate to Other Hardware in the left menu and select Switches.
Page 14
Select SAN Settings and enter the following information: Enter a name in the SAN Name box. 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 easily recognized as associated with the SAN for which you want a report.) Click Rename.
Page 15
Click Yes to confirm the name change. To detect switches, click Switch Settings and enter the following information: 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. Clear Discover connected switches .
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: Enter the starting IP address in Start at IP Address. Enter the limiting IP address in Stop at IP Address.
Creating a report automatically Select Data Collection. 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.
Creating a report manually To obtain the SMTP server for the e-mail address you entered in the Customer Details window, select the Automatically e-mail the collected raw data on completion checkbox. If SAN Visibility does not find the SMTP server or if you want to create a report manually, follow these steps: Click Data Collection.
Figure 5 Sample SAN Visibility report Reading the report Save the attached .hppr file to a preferred location. Do not change the file extension. Double-click the saved file to extract the processed report. The report is stored at: <Install_Dir>\ExtractedProcessReports\<SAN Name>\ Click on the .hppr file to open the report in your browser.
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”...
critical applications or operations is minimized during the upgrade, select a time when a host I/O disruption would minimize the impact to business operations. Communicating with HP P6000 Command View—The first steps of the upgrade have a lower priority than host I/O. The upgrade can extend beyond the timeout value expected by HP P6000 Command View, which may cause loss of management connectivity to the array.
Page 22
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 ◦...
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.
HP Command View EVAPerf command options Use the following options with the HP Command View EVAPerf 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.
When the command has finished, open the file in an ASCII editor. Identify and exclude instances where IOPS have been exceeded. Instances where limits have not been exceeded and where IOPS are at a minimum are 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.
Page 26
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 26). 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.
Table 4 HP Command View EVAPerf 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.
IBM AIX Checking or changing timeouts AIX requires the disk settings shown in Table 5 (page 28) for the native multipath drives. Table 5 IBM AIX timeout settings Setting Value Description PR_key_value not applicable Sets the key value for persistent reservations. Persistent reservations are not supported.
is set to 3c (60 seconds), the Microsoft Windows default. If the registry entry does not exist, you must create it. See your Windows documentation for instructions. If this registry entry is created or changed, reboot the Windows system for the new timeout value to take effect.
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 EVA arrays. All components of the software suite (HP P6000 Command View, HP Command View EVAPerf, HP Storage System Scripting Utility, SMI-S EVA) are installed.
Windows. 12. The installation summary window opens. Click Finish. All software components are installed in the directory <system drive>:\Program Files\Hewlett-Packard Verifying installation on the management server To verify that the software was installed successfully: Ensure that the software icons for HP P6000 Command View...
Page 34
Connect a server with a CD drive to the management module port (1, Figure 8 (page 34)) on the controller enclosure. Figure 8 Management module Insert the installation CD into the drive. Open a browser and navigate to the P6000 WOCP (Web-based Operator Control Panel): https://HP array IP address:2373 NOTE: If you are running a version of management module software earlier than 0001.1000...
10. Press the reset button (2, Figure 8 (page 34)) on the management module to activate the IP address. Upon reset, the WOCP login window opens. Continue with “Verifying installation on the management module” (page 35). Verifying installation on the management module To verify that the management module software was upgraded successfully: On the WOCP login window, log in as an HP EVA administrator (user name admin and the password).
sent to your authorized HP Channel Partner for on-site service, if configured and available in your country. The software is available in two variants: HP Insight Remote Support Standard: This software supports server and storage devices and is optimized for environments with 1-50 servers. Ideal for customers who can benefit from proactive notification, but do not need proactive service delivery and integration with a management platform.
Page 37
Click View Events. The View Events window opens (Figure 9 (page 37)). Figure 9 View Events window Select Controller Event Log. The Controller Events window (Figure 10 (page 37)) opens in a new browser window. Figure 10 Controller Events (Initialized system) window Check the Severity field to determine if any unexpected critical events have occurred.
Verify that there are no changes to the array configuration in progress (such as creation, deletion, shrinkage, expansion, and presentation). Do not make any configuration changes within 48 hours of beginning the upgrade. Use proactive event notification to alert you if a critical event occurs during the 48 hours before the upgrade.
Upgrading disk drive firmware in an HP P6000 Continuous Access environment When upgrading disk drive firmware in an HP P6000 Continuous Access environment, the following requirements must be met: Perform the disk drive firmware upgrade using the local management server (the server running HP P6000 Command View that is local to the array being upgraded).
Before starting the upgrade, collect and save your current configuration data. This data 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 array. HP Storage System Scripting Utility (called the utility) is used to collect configuration data.
Page 41
Table 6 Pre-upgrade task checklist Task Task complete “Checking the controller software version” (page 9) Time required: About 5 minutes When to perform: Anytime before the upgrade “Checking management software versions” (page 9) Time required: 10–15 minutes When to perform: Anytime before the upgrade “Checking the array hardware”...
Page 42
Table 6 Pre-upgrade task checklist (continued) Task Task complete “HP Insight Remote Support software” (page 35) Time required: 10–20 minutes When to perform: Anytime before the upgrade “Upgrading HP P6000 Replication Solutions Manager (optional)” (page 36) Time required: 10–20 minutes When to perform: Anytime before the upgrade “Monitoring array stability”...
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 8 (page 65) 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 44
Figure 12 Checking the operational state If you cannot resolve the error, contact your HP-authorized service representative for assistance. Replace any hardware components that have failed. NOTE: If you need to replace a component, see the replacement instructions for that component or the user guide for your array model.
Figure 13 Controller Events (Initialized system) page If critical events have occurred in the last 48 hours, perform the steps outlined in the corrective action codes to correct the problems. In some cases, you may need to call your HP-authorized service representative. CAUTION: If any critical events have occurred in the last 48 hours, do not proceed with the upgrade until the situation is resolved.
NOTE: This is a free form field. If desired, verify and change the amount of time you expect the array to remain in service mode. The default is 30 minutes. Select Start service mode to notify HP Insight Remote Support that the array will be in service mode.
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.
Page 48
Figure 15 First system code load confirmation window Click Continue to proceed or Cancel to exit the procedure. The Code Load Storage System – Page 1 window (Figure 16 (page 48)) opens. Figure 16 Code Load Storage System — Page 1 window 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.”...
Page 49
The Code Load Storage System — Page 3 window opens, confirming verification. 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 10.
Page 50
Figure 19 Second code load confirmation window Enter YES (all uppercase) and click Continue. 12. The Code Load Storage System — Page 5 window (Figure 20 (page 50)) opens. Read any pre-update application notes before proceeding. Click Finish to proceed or Cancel to exit the procedure.
Page 51
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...
Page 52
commands. I/O processing does not begin until the hosts complete recovery from the disruption of resynchronization. Other code in the array, such as I/O module firmware, is updated, which can take up to 10 minutes to complete. During this interval, the Storage System Updating Firmware page opens (Figure 23 (page 52)).
Page 53
Figure 25 Verifying XCS version after upgrading Step 5. Upgrading the controller software...
Page 54
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. If the data replication protocol is not compatible with the data replication protocol of the other array in the HP P6000 Continuous Access configuration, the data replication paths are disabled until a compatible data replication protocol is selected in HP P6000 Command View.
Page 55
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.
17. Determine whether the component blocking the upgrade is an I/O module or a disk drive: Refer to the list of I/O modules you recorded in Step 15. 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 15 indicating that...
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 74) 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).
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.
Page 59
Store the file in a local directory. Open and log in to HP P6000 Command View. In the navigation pane, select the array whose disk drive firmware you want to update. The Initialized Storage System Properties window opens. Select the System Options tab. The System Options window opens.
Page 60
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 60)). In Step 1, Click Browse to select the bundled image zip file. Figure 30 Code Load Disk Drives –...
Page 61
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 61)). The disk drives are upgraded sequentially.
When all disk drives have been upgraded, the Code Load Disk Drives On Line – Page 3 window opens (Figure 33 (page 62)), indicating that the drives have been upgraded successfully. Figure 33 Code Load Disk Drives On Line – Page 3 window 1 1.
Can include the following characters: ! “ # $ % & ‘ ( ) * + , - . / : ; < = > ? @ [ ] ^ _ ` { | } Cannot include the following characters: space ~ \ Enabling password access in HP P6000 Command View Estimated time to complete: 10 minutes You must enable password access in HP P6000 Command View.
Page 64
When running HP P6000 Continuous Access, set the Failsafe on unavailable member mode to Enabled on all DR groups if it was disabled before the upgrade. For instructions, see “Preparing the HP P6000 Continuous Access environment for an upgrade” (page 38).
Task checklist Use the following checklist to track your progress and mark when a task is completed. Table 8 Upgrade task checklist Task Task complete “Step 1. Checking the health of the Enterprise Virtual Array” (page 43) Time required: 20–30 minutes “Step 2.
Click Delete Cookies. Click Delete Files. On the General Tab, under History, click Clear History. Ensure that the following folder exists: <install_drive>:\Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\ HP P6000 Command View errors View is not set or view list is null Symptom The content pane shows an Operation Failed message with Details: View Is Not Set or View List Is Null.
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 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 67). The controllers are running a version of XCS that HP P6000 Command View does not recognize.
Table 10 Possible causes and corrective actions when no array is found (continued) Possible cause Corrective action restart is complete, the array that lost communication Verify that switch zoning is correct. will not be visible. Click Discover. An array may not be visible to HP P6000 Command Enter the WWID of your system.
Table 1 1 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.
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 36 (page 71) illustrates an array with a disk enclosure problem. Figure 36 Status icon for an array in bad 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.
Page 73
If an event occurs that causes a second resynchronization while the upgrade resynchronization is still in progress, the controller will terminate with a code of 0b 08 01 00. The following events cause the controller to resysnchronize automatically: Initialization of the array Debug flags set through the command line interface or WOCP Disk group hardware problem on a Vraid1 virtual disk, or attempted reconnection of a disk when there is a disk group hardware problem...
5 Support and other resources Contacting HP HP technical support Telephone numbers for worldwide technical support are listed on the HP support website: http://www.hp.com/support/ Collect the following information before calling: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level...
HP Software Depot: http://www.software.hp.com HP Single Point of Connectivity Knowledge (SPOCK): http://www.hp.com/storage/spock Typographic conventions Table 12 Document conventions Convention Element Medium blue text: Table 12 (page 75) Cross-reference links and email addresses Medium blue, underlined text: http:// Website addresses www.hp.com Bold text Keys that are pressed Text typed into a GUI element, such as into a box...