HP Enterprise Virtual Array Updating Product Software Guide (XCS 10001000) Abstract This guide describes how to upgrade controller software, disk drive firmware, and related EVA management software on the HP 4400/6400/8400 Enterprise Virtual Arrays. HP P6300/P6500 EVAs are not included in this document because they are already running XCS 10001000 and do not need an upgrade. P6000, used throughout this document, is the new branding for the Enterprise Virtual Array product family.
© Copyright 2011 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....................................................................................................
Saving array configuration data...............................................................................................38 Task checklist.........................................................................................................................39 3 Upgrading the Enterprise Virtual Array........................................................41 Step 1. Checking the health of the Enterprise Virtual Array...........................................................41 Step 2.
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 and all previous EVA3000/5000, EVA4000/6000/8000, EVA4100/6100/8100, and EVA4400/6400/8400 arrays.
Reference documentation Table 1 (page 6) identifies the documentation you should have available when upgrading the array. Table 1 Reference documentation Document Required Location HP P6000 EVA documentation HP 4400 Enterprise Virtual Array User Guide No HP 6400/8400 Enterprise Virtual Array User Guide No HP P6300/6500 Enterprise Virtual Array User Guide Yes HP P6000 Enterprise Virtual Array Release Notes Yes HP P6000 Enterprise Virtual Array Compatibility Reference Yes http://www.hp.
and HP EVA P6300, P6500 XCS 10001000. Select your product and enter your information to download the ISO image. 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 DVD or an E-Delivery kit. TIP: 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.
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 10001000. Table 8 (page 39) provides a checklist so you can track your progress as you perform these pre-upgrade tasks.
Table 2 Management software version worksheet (continued) Software JRE Current version Minimum required version 1.5.0_04 or later 2 Locating version information1 Upgrade procedure 1. Open the Windows control panel. 2. Double-click the Java icon. 3. On the General tab, click About. “Upgrading browsers and JRE” (page 34) The version of Java is displayed. Web browser (required) Internet Explorer 6.
2. Click Help in the Session pane. The full version number is displayed at the top of the online help window (Figure 2 (page 10)). 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. Checking the array hardware Estimated time to complete: 15–20 minutes When to perform: 1–2 weeks before the upgrade, and then daily until the upgrade is complete.
d. Click the component icon to display the properties window (Figure 4 (page 11)). The Operational state field indicates if there is a hardware error. Figure 4 Checking operational state 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.
Switches. Then, to view specific support details, select the connectivity stream document for the switch model/series you are using. • Download the required HBA drivers, firmware and MPIO drivers. NOTE: Additionally, see the “P6000/EVA storage system rules” chapter in the HP SAN Design Reference Guide for general guidelines about managing Enterprise Virtual Arrays in a SAN. Collecting SAN configuration data using SAN Visibility IMPORTANT: SAN Visibility is available for server-based management only.
3. Select SAN Settings and enter the following information: a. 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.) b. Click Rename. c. Click Yes to confirm the name change. d. Select the fabric in the tree view. e. Enter a name in the Component Group Name box.
g. 4. 14 Click Yes to confirm the name change. To detect switches, click Switch Settings and enter the following information: a. Enter the IP address of the primary switch for the SAN for which you want a report. Information will be collected for all devices connected to this switch. b. Clear Discover connected switches . This option automatically detects all switches connected to the switch identified by the IP address. Including all connected switches increases the data collected for the report.
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.
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: 1. Click Data Collection. 2. Select the fabric for which you want to create a report from the Select a switch group for data collection.
Figure 5 Sample SAN Visibility report Reading the report 1. 2. 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: \ExtractedProcessReports\\ 3. 4. Click on the .hppr file to open the report in your browser. In the navigation pane, click High Level Fabric Summary. The High Level Fabric Summary window opens (Figure 5 (page 18)).
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 18), it is the folder called MySwitchGroup. Look for the group name you created in step 2 of “Using SAN Visibility” (page 12). The Best Practices and Recommendations window opens (Figure 6 (page 19)).
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.
◦ Snapclones: For each snapclone, go to the Vdisk – General Properties window of the original virtual disk and record the value listed in the Requested capacity box. ◦ 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.
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 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. • -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 25). 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 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. 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 5 (page 27) 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. 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 7 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.
applications that have more stringent timeout requirements than the operating system to help determine if the applications will tolerate the online upgrade. Although an application may survive the online controller software upgrade successfully, there may be an impact on performance. To minimize the performance impact on users, perform the online upgrade during a period of low user activity.
Follow the procedures in this section to upgrade HP P6000 Command View on the management server. If you are using array-based management, see “Upgrading the management module” (page 32) for upgrade instructions. NOTE: Before starting the upgrade, check the release notes for the version to which you are upgrading for any details on the upgrade process. TIP: To help ensure fast recovery from the upgrade, it may be useful to remove a disk from the management server. For supported upgrade paths, see Table 2.
12. The installation summary window opens. Click Finish. All software components are installed in the directory :\Program Files\Hewlett-Packard Verifying installation on the management server To verify that the software was installed successfully: 1. 2. 3. Ensure that the software icons for HP P6000 Command View , HP Command View EVAPerf , and/or HP System Scripting Utility appear on the desktop. Run HP P6000 Command View. Verify the display of array resources in the interface.
NOTE: • If you are running a version of management module software earlier than 0001.1000 (which corresponds to XCS 09004000 or earlier), use port 2372. • If you have not previously set the IP address for the management module, the default is 192.168.0.1. • If you have not previously completed the initial setup for the management module, see “Connecting to the management module (initial setup)” in the HP P6000 Control Panel User Guide. The P6000 Control Panel login window appears. 4.
To verify that HP P6000 Command View was upgraded successfully: 1. Open a browser and navigate to HP P6000 Command View: https://array IP address:2372 2. 3. Log in using the same user name and password that you use for the P6000 Control Panel login. Verify that the correct time is set: a. On the Initialized Storage System Properties window, select System Options. b. Select Set time options. c. Verify that the time displayed in the Current system time box is correct.
Select Insight Remote Support from the menu on the right. Upgrading HP P6000 Replication Solutions Manager (optional) NOTE: HP P6000 Replication Solutions Manager is currently supported with server-based management only. HP P6000 Replication Solutions Manager requires JRE 1.5.0_04 or later. Go to the Oracle website (http://www.oracle.com) to download the required JRE.
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. In some cases, it may be necessary to call your HP-authorized service representative to fix the problem. 3.
• If the HP P6000 Continuous Access arrays are running different controller software versions, you cannot make any configuration changes to the arrays (for example, do not add or delete DR groups or members of DR groups). • You must perform the upgrades to the arrays in the HP P6000 Continuous Access environment within 60 days (1,440 hours) so that all arrays are running the same controller software version. After upgrading the first array, wait at least three minutes before upgrading the second array.
c. d. e. f. Under Service, select Shut down system. Under Controller shutdown, select Restart Controller A. A pop-up warning will display; enter YES and click RESTART. Controller A will restart. Wait 3-5 minutes for the restart to complete. 3. Restart Controller B: a. In the navigation pane, select the storage system being upgraded. b. Select System Options. c. Under Service, select Shut down system. d. Under Controller shutdown, select Restart Controller B. e.
TIP: When capturing the HP P6000 Command View configuration, it is a best practice to specify the SAVE ALL option. This captures critical data such as the WWN, which is useful for rebuilding the array configuration. You can run the CAPTURE VALIDATE command for each file generated by the CAPTURE CONFIGURATION command to determine if the file has been modified since the initial capture.
Table 8 Pre-upgrade task checklist (continued) Task “Managing application I/O timeouts for an online upgrade” (page 29) Time required: Varies When to perform: As close as possible to the upgrade “Managing external devices” (page 30) Time required: Varies When to perform: As close as possible to the upgrade “Managing an SVSP configuration for an online upgrade” (page 30) Time required: Varies When to perform: As close as possible to the upgrade “Backing up all array data” (page 30) Time required: Varies When
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 10 (page 63) 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 64) for assistance.
Figure 12 Checking the operational state e. 3. 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. 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).
Figure 13 Controller Events (Initialized system) page e. 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. 5.
1. 2. On the management server, open a command window. Enter the following commands to stop Remote Support software: C:\>net stop desta_service 3. Enter exit. Step 3. Disabling array passwords Estimated time to complete: 10–15 minutes If you use passwords on the controllers, use the following procedure to disable or clear them. Disabling passwords in HP P6000 Command View NOTE: You must know the World Wide Name (WWN) of the array to disable password access.
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 46)) 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 Step 5.
12. Click Browse to navigate to the controller software image file (created from the downloaded .ISO image) (see “Required kits” (page 6)) and select the appropriate file (Table 9 (page 48)). Table 9 Controller software For this array: Select this file: EVA4400 \HSV300\10001000\300_10001000.SSS EVA6400 \HSV400\10001000\400_10001000.SSS EVA8400 \HSV450\10001000\450_10001000.SSS 13. Click Next Step to upload the appropriate controller software image file. A second code load confirmation window opens.
Figure 20 Code Load Storage System — Page 5 window The new controller software is copied to the controllers and validated (Figure 21 (page 49)). Figure 21 Code load processing page The upgrade process begins and the Initiating firmware code load page opens (Figure 22 (page 50)). This page is displayed while the upgrade file components are processed. Step 5.
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 51)). 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 51)). Verify the version of the controller software in the Version box. It should be 10001000. Figure 25 Verifying XCS version after upgrading Step 5.
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 54).
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 72) 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 27 System Options — Code load system 7. Click Code load system. The Code Load Selection window opens (Figure 28 (page 57)). 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 57). Figure 29 Confirm Disk Drive Code Load Warning Click Continue to proceed or Cancel to exit the procedure.
Figure 30 Code Load Disk Drives – Page 1 window 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.
The disk drives are upgraded sequentially. Depending on the I/O load on the array, it can take from 30 seconds to 3.5 minutes per drive to upgrade the firmware. The status is updated at 45-second intervals. CAUTION: Do not select an array to manage it during the disk drive upgrade. If you select an array in the navigation pane to manage it, the disk drive upgrade stops. For example, if the upgrade was completed on 10 of 27 drives when you selected the array, only those 10 drives have been upgraded.
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.com/support/evadiskfirmware IMPORTANT: 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. If so, when using HP P6000 Command View 9.
Enabling password access in HP P6000 Command View Estimated time to complete: 10 minutes You must enable password access in HP P6000 Command View. To enable password access to an array: 1. Open HP P6000 Command View in your browser. 2. Click Agent Options in the Session pane. The Management Agent Options window opens. 3. Click Manage storage system password access. The Storage System Password Access window opens. 4. Click Enable.
2. If you did an offline upgrade, perform the following steps: a. Restart any host servers that were shut down for the upgrade. b. Resume host I/O. 3. 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 36). If you changed any host LUN timeout values, reset them to their original values.
Task checklist Use the following checklist to track your progress and mark when a task is completed. Table 10 Upgrade task checklist Task Task complete “Step 1. Checking the health of the Enterprise Virtual Array” (page 41) Time required: 20–30 minutes “Step 2. Configure User-Initiated Service Mode (UISM)” (page 43) Time required: 10–15 minutes “Step 3. Disabling array passwords” (page 44) Time required: 10–15 minutes “Step 4.
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 65). • The controllers are running a version of XCS that HP P6000 Command View does not recognize. See “Unknown storage system” (page 65).
Table 12 Possible causes and corrective actions when no array is found (continued) Possible cause Corrective action restart is complete, the array that lost communication will not be visible. 3. Verify that switch zoning is correct. 4. Click Discover. An array may not be visible to HP P6000 Command 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. Enter the WWID of your system.
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 36 (page 69) 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.
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 73) Cross-reference links and email addresses Medium blue, underlined text: http:// www.hp.
Index A F advisory free space, 56 agent options using, 44 analyzing array I/O, 22 array checking for errors, 10, 41 passwords, 61 XP P9000, 30 fabric name, 13 failed hardware components, 10 firmware upgrading, 37, 56, 60 free space, 56 B backing up data, 30 Bad image header error, 70 browsers recommended versions, 34 C capacity virtual mapped, 20 checking hardware status, 10, 41 checklist pre-upgrade task, 39 upgrade task, 63 cluster symbol, 68 Command View version verifying, 9 components failed, 10 co
software, 6, 7 limits throughput, 24 LUNs Vraid0, 30 SPOCK website, 11 status code 21006, 69 65, 70 storage system passwords, 61 System Option Mode 725, 30 M T management module, 32 software, 7 management server interaction with HP P6000 Command View, 65 technical support HP, 72 throughput limits, 24 time estimate adding passwords, 60 clearing passwords, 44 disabling password access, 44 L O OCP adding passwords, 60 offline upgrade, 5 online upgrade, 5 configuration evaluation, 19 considerations, 20
