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. General references to HP P6000 Command View may also refer to earlier versions of HP Command View EVA. This guide is intended for field personnel and customers who are experienced with these array models, storage area networks, HP P6000 Command View and associated software. This guide does not provide information about upgrading or replacing array hardware. The information in this guide is subject to change. Please check for the latest version before starting an upgrade.

HP Part Number: 5697-2423 Published: December 2012 Edition: 4

 Copyright 201 1 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. Warranty WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty Acknowledgments Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Java is a U.S. trademark of Oracle.

Contents
1 Getting started...........................................................................................5
Upgrade overview....................................................................................................................5 Upgrade paths.........................................................................................................................5 Reference documentation...........................................................................................................6 Required kits............................................................................................................................6

2 Preparing for the upgrade ..........................................................................8

Checking the controller software version......................................................................................8 Checking management software versions.....................................................................................8 Checking the array hardware...................................................................................................10 Checking and upgrading your SAN infrastructure.......................................................................11 Collecting SAN configuration data using SAN Visibility..........................................................12 Installing SAN Visibility..................................................................................................12 Using SAN Visibility......................................................................................................12 Obtaining a report from HP............................................................................................15 Creating a report automatically..................................................................................16 Creating a report manually........................................................................................17 Reading the report........................................................................................................18 Evaluating your configuration...................................................................................................19 XCS 10001000 upgrade considerations....................................................................................20 Selecting a time to perform an online upgrade...........................................................................22 Analyzing array I/O using HP Command View EVAPerf..........................................................22 Guidelines for using HP Command View EVAPerf..............................................................22 HP Command View EVAPerf command options.................................................................23 Running HP Command View EVAPerf...............................................................................23 Identifying virtual disk activity.........................................................................................24 Managing host I/O timeouts for an online upgrade....................................................................26 HP-UX...............................................................................................................................26 IBM AIX............................................................................................................................27 Linux Red Hat and SUSE.....................................................................................................27 Mac OS X........................................................................................................................28 Microsoft Windows............................................................................................................28 OpenVMS........................................................................................................................28 Solaris..............................................................................................................................29 VMware...........................................................................................................................29 Xen Citrix..........................................................................................................................29 Managing application I/O timeouts for an online upgrade..........................................................29 Managing external devices......................................................................................................30 Managing an SVSP configuration for an online upgrade.............................................................30 Backing up all array data........................................................................................................30 Upgrading HP P6000 Command View......................................................................................30 Upgrading on a management server....................................................................................31 Verifying installation on the management server.....................................................................32 Upgrading the management module.........................................................................................32 Verifying installation on the management module...................................................................33 Upgrading browsers and JRE...................................................................................................34 HP Insight Remote Support software..........................................................................................34 Upgrading HP P6000 Replication Solutions Manager (optional)...................................................35 Monitoring array stability.........................................................................................................35 Preparing the HP P6000 Continuous Access environment for an upgrade.......................................36 Upgrading disk drive firmware in an HP P6000 Continuous Access environment........................37 Checking the disk grouping policy............................................................................................37
Contents 3

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. Configure User-Initiated Service Mode (UISM).................................................................43 Step 3. Disabling array passwords............................................................................................44 Step 4. Halting all host access to the array for an offline upgrade ................................................44 Step 5. Upgrading the controller software .................................................................................45 Resetting the I/O module....................................................................................................54 Step 6. Upgrading the disk drive firmware.................................................................................55 Upgrading firmware on all disks..........................................................................................56 Upgrading firmware on a single disk....................................................................................60 Step 7. Entering array passwords..............................................................................................60 Enabling password access in HP P6000 Command View .......................................................61 Step 8. Resuming array operation.............................................................................................61 Task checklist.........................................................................................................................63

4 Troubleshooting........................................................................................64
HP P6000 Command View......................................................................................................64 HP P6000 Command View with a management server...........................................................64 HP P6000 Command View errors........................................................................................64 View is not set or view list is null......................................................................................64 HTTP status 404, not found or status 503, no service.........................................................65 Unknown storage system................................................................................................65 No storage systems found..............................................................................................66 Creating disk groups with double protection level ..................................................................67 Security credentials configuration ........................................................................................67 Upgrading the disk drive firmware ...........................................................................................67 Selecting an array .................................................................................................................68 Disabling DR group failsafe mode ............................................................................................69 Downloading the controller software file ...................................................................................69 Invalid firmware image file (Status code 21006).....................................................................69 Bad image header (Status code 65).....................................................................................70 Offline array .........................................................................................................................70 Multiple resynchronizations .....................................................................................................70

5 Support and other resources......................................................................72

Contacting HP........................................................................................................................72 HP technical support..........................................................................................................72 Subscription service............................................................................................................72 Documentation feedback....................................................................................................72 Related information.................................................................................................................72 Documents........................................................................................................................72 Websites..........................................................................................................................72 Typographic conventions.........................................................................................................73

Index.........................................................................................................74

Contents

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. General references to HP P6000 Command View may also refer to earlier versions of HP Command View EVA. P6000 is the new branding for the Enterprise Virtual Array product family.

Upgrade overview
Depending on the upgrade path for your configuration, you can perform an upgrade either online or offline.

Resynchronization
Resynchronization is the process of restarting the controllers at the end of a controller software upgrade to begin execution of the new controller software. In an online controller software upgrade, I/O processing is temporarily disrupted during resynchronization. Resynchronization is complete when the controller host ports come online and are ready to accept host commands. In an online upgrade, after resynchronization is complete, an additional delay may occur before host I/O processing resumes while hosts recover from the disruption. The recovery time is not solely dependent on the controllers and therefore is not specified by this document. Only the time required to complete resynchronization is specified. User knowledge of the external environment, including applications, is required to evaluate the overall impact of the I/O disruption that occurs during an online controller software upgrade.

Online upgrade
The controller software is upgraded while the controllers are processing I/O. The controllers resynchronize simultaneously while hosts and applications continue to run. Resynchronization during an online upgrade represents a single disruption of I/O, not the multiple disruptions seen with some upgrade types. However, you must consider host and application timeouts when performing an online upgrade.

Offline upgrade (shutdown upgrade)

All host I/O to the array must be stopped. All applications and hosts are shut down before you begin the controller upgrade and restarted when the upgrade is complete. An offline upgrade requires scheduling time with application managers and having staff available to shut down and restart applications and hosts. While actual upgrade time may be short, offline upgrades can require several hours to complete, from the time the first application shuts down until all hosts and applications have returned to service.

Upgrade paths
For details about supported upgrade and downgrade paths, see Table 3.1, Upgrade support for controller software versions, and Table 3.2, Downgrade support for controller software versions, respectively, in the HP P6000 Enterprise Virtual Array Compatibility Reference. See Table 1 (page 6) for the link to this document.

Upgrade overview

Reference documentation
Table 1 (page 6) identifies the documentation you should have available when upgrading the array. Table 1 Reference documentation
Document Required HP P6000 EVA documentation HP 4400 Enterprise Virtual Array User Guide HP 6400/8400 Enterprise Virtual Array User Guide HP P6300/6500 Enterprise Virtual Array User Guide HP P6000 Enterprise Virtual Array Release Notes HP P6000 Enterprise Virtual Array Compatibility Reference No No Yes Yes Yes HP P6000 Command View documentation HP P6000 Command View Release Notes HP P6000 Command View User Guide HP P6000 Command View Installation Guide HP P6000 Storage System Scripting Utility Reference No No Yes No http://www.hp.com/support/manuals Click Storage Software under storage, and then select HP P6000 Command View Software under Storage Device Management Software. http://www.hp.com/support/manuals Click Disk Storage Systems under storage, and then select HP 4400 Enterprise Virtual Array, or HP 6400/8400 Enterprise Virtual Array, or HP P6000 Enterprise Virtual Array Systems under P6000 EVA Disk Arrays. Location

HP P6000 replication software documentation HP P6000 Replication Solutions Manager Release Notes HP P6000 Replication Solutions Manager Installation Guide HP P6000 Replication Solutions Manager Administrator Guide HP P6000 Continuous Access Implementation Guide No Yes (if installed) No No SAN infrastructure documentation HP SAN Design Reference Guide Yes http://www.hp.com/support/manuals Click Storage Networking under storage, and then select HP SAN under HP SAN Solutions. http://www.hp.com/support/manuals Click Storage Software under storage, and then select HP P6000 Continuous Access Software under Storage Replication Software.

Required kits
Before you begin the upgrade, you must download the XCS 10001000 controller software from the following website: http://www.software.hp.com/ Under Product Category, click HP Storage. Click Storage Software. At the top of the screen, with the Software Depot button selected (default), enter XCS 10001000 in the Search box and click the Search button. The Product Category screen displays HP EVA 4400,6400,8400 XCS 10001000

Getting started

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. You will need them if you need to download the software again. IMPORTANT: HP P6000 Command View 9.4 or later is supported with XCS 10001000. For the latest HP P6000 Command View and XCS compatibility information, see Table 2.0, HP P6000 Command View interoperability support, in the HP P6000 Enterprise Virtual Array Compatibility Reference. See Table 1 (page 6) for the link to this document. The HP IT Resource Center (ITRC) has reached its end of life in June 201 1. The new HP Support Center will provide you a more personalized online support experience with access to information, tools and experts to keep your technology running in the Instant-On connected world. 1. Sign-in to the HP Support Center (http://www.hp.com/go/hpsc) with HP Passport (or register first for HP Passport if you have not already obtained one.) 2. Start your ITRC migration by clicking on the Profile Migration Feature in the home page on HP Support Center. 3. Provide your ITRC username and password. After the system verifies and confirms that you are the owner of the ITRC username and password, the migration will begin. You will get a confirmation from the system when the migration is complete. NOTE: If you used a single ITRC login (username and password) for multiple users, you will need separate HP Passport sign-ins for each individual on HP Support Center. An ITRC account can only be migrated once, and only to one HP Passport account on HP Support Center. We recommend that you discuss and identify within your team the individual you want to claim the ITRC account. This person will then need to create shares to enable others to obtain the important benefits of the linked entitlements. If you had a linked contract on ITRC which was shared with other ITRC users, these contracts are migrated to your HP Passport account and are now available to you on HP Support Center. Any members who shared the contract in ITRC will be part of the new share and will have access to the same services as on ITRC once they complete these same migration steps above. Note: It is not necessary that the owner of the share has to migrate first. Migration can be done in any order by the owner or any of the individuals who share the linked entitlement. 4. Start using HP Support Center or review your profile and contracts and warranties (including managing sharing).

If you have questions or need assistance, go to http://welcome.hp.com/country/us/en/ wwcontact_us.html and select your country/region.

Required kits

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.

Checking the controller software version

Estimated time to complete: About 5 minutes When to perform: Anytime before the upgrade To check your controller software version, follow these steps: 1. Open HP P6000 Command View. 2. In the navigation pane, select the array you plan to upgrade. The Initialized Storage System Properties window opens. The version field shows the current version.

Checking management software versions

Estimated time to complete: 1015 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 2 (page 8) 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.0, HP P6000 Command View interoperability support, in the HP P6000 Enterprise Virtual Array Compatibility Reference. See Reference documentation (page 6) for the link to this document. Table 2 Management software version worksheet
Software HP P6000 Command View (required) Current version Minimum required version 9.4 Locating version information1 Upgrade procedure

1. Open HP P6000 Command Upgrading HP P6000 Command View. View (page 30) 2. Click Help in the Session pane. The HP P6000 Command View Online Help window opens and the version is displayed. 1. Open or browse to HP P6000 Upgrading HP P6000 Replication Replication Solutions Solutions Manager (optional) (page Manager. 35) 2. Select HelpAbout from the menu bar. The version of HP Replication Solutions Manager server is displayed.

HP P6000 Replication Solutions Manager (if installed)

5.3

Preparing for the upgrade

Table 2 Management software version worksheet (continued)

Software JRE Current version Minimum required version 1.5.0_04 or later
2

Locating version information1 1. Open the Windows control panel. 2. Double-click the Java icon. 3. On the General tab, click About. The version of Java is displayed.

Upgrade procedure Upgrading browsers and JRE (page 34)

Web browser (required)

1 2

Internet Explorer 6.0 SP1 or later

From your browser, select Help > Upgrading browsers and JRE (page About Internet Explorer. 34)

You can also use Windows Add or Remove Programs to view the software version. For Windows servers. For clients running other operating systems, see Table 5.0, the Browser support table, in the HP P6000 Enterprise Virtual Array Compatibility Reference. See Table 1 (page 6) for the location of this document.

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 9)) opens. Figure 1 Storage Network Properties window

Checking management software versions

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: 1520 minutes When to perform: 12 weeks before the upgrade, and then daily until the upgrade is complete. NOTE: If you are running HP P6000 Command View 9.3 or later, HP P6000 Command View will complete this check automatically when you upgrade the controller software. Before upgrading your Enterprise Virtual Array, check the operation of the array hardware and replace any failed components to ensure that the array will be operating properly when the upgrade is performed. 1. Open HP P6000 Command View and click the icon of the array you want to upgrade. 2. Check for hardware errors. 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 10)). The Operational State field indicates if there is a hardware problem. Figure 3 Hardware Folder Properties window

b. c.

Select the array in the navigation pane and click Refresh to update the cache. 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.

10

Preparing for the upgrade

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. 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. If you cannot resolve the error, contact your HP-authorized service representative for assistance.

Checking and upgrading your SAN infrastructure

Estimated time to complete: Varies depending on the number of components that require an upgrade. When to perform: Any time before the upgrade Ensure that your SAN environment meets the configuration requirements of the XCS controller software. This includes HBA firmware, system drivers, and Fibre Channel switch firmware. The SAN Visibility tool assists you with this task by automating the collection of data and providing a full report. You can collect the data manually but this is more time consuming. To collect the data manually: Identify all host servers. Document all firmware versions. Go to the Single Point of Connectivity Knowledge (SPOCK) website (www.hp.com/storage/ spock) to ensure that the firmware and driver versions are supported with the XCS version you are upgrading to. You must log in to access SPOCK. If you do not already have an account, click Register to log in on the main page and follow the instructions. Once access is enabled, select View by Array/OS under Compatibility Tool in the left menu and then select the array 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
Checking and upgrading your SAN infrastructure 1 1

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. SAN Visibility collects configuration information from the Fibre Channel switches in your SAN, including any information provided by devices when they log into the fabric. The raw configuration data is collected and sent to HP, where it is formatted into a complete report and returned to you. You then use the report to determine if any of your SAN components are not supported by the latest controller software and must be upgraded or replaced. 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 Oracle website: http://www.oracle.com/

Installing SAN Visibility

You typically install SAN Visibility on the management server running HP P6000 Command View. 1. Download SAN Visibility and the SAN Visibility documentation from the following website: http://h18006.www1.hp.com/products/storageworks/san/index.html Click SAN Visibility under Networking Solutions and Download now!. 2. 3. Double-click the downloaded file to launch the installation. Follow the on-screen instructions to install the software.

Using SAN Visibility

Before running SAN Visibility for the first time, you will need the following information: The IP addresses of the switches in your SAN connected to the array being upgraded. You must have SNMP access to the switches to collect information from them. The name or IP address of your SMTP mail server to send reports automatically.

The following procedure describes the steps for using SAN Visibility. For complete information about using this tool, see the SAN Visibility online help. 1. Double-click the SAN Visibility icon on the desktop. The SAN Visibility window is displayed. 2. Click OK to view the SAN Settings window.

12

Preparing for the upgrade

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. 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.) f. Click Rename. Your new component group name (MyComponentGroup in this example) appears in the right panel of the SAN Visibility window.

Checking and upgrading your SAN infrastructure

13

g.

Click Yes to confirm the name change.

4.

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. This includes data for all devices connected to the switch. To include all switches, leave this option selected; to include subnet switches, also select Subnet. c. Enter the switch login and password, if required. You use the Read Community value to log in to the switch. d. If you have created more than one fabric, use the Select Component Group list to select the fabric to which you want to add this switch. e. Click Discover Switch to discover the switch and activate the login and password. The extended switch information with IP addresses appears in the right panel. f. Click Add to add the switch to the reporting configuration.

14

Preparing for the upgrade

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.

Obtaining a report from HP

Once you have configured SAN Visibility for data collection, you can obtain a report. There are two methods for obtaining a report: AutomaticallyAutomatically emails your data to HP when collection is complete. You will need to know the SMTP address of your mail server. Select the SMTP address from the list. Use this method if you have external e-mail access from your environment. ManuallyRequires that you send your data manually to HP to obtain a SAN Visibility report. Use this method if you do not have external email access.

Checking and upgrading your SAN infrastructure

15

Creating a report automatically 1. Select Data Collection.

2.

3.

4. 5. 6.

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. 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. On successful completion of data collection, a message is displayed in the message area. If you selected the option to collect switch performance data, it will take at least 10 additional minutes to collect the data. When data collection is complete, the raw data is sent to HP. (You can view the collected files that are sent to HP in the Raw Data screen that displays before the raw data is sent to HP.) The data is processed and the formatted report is returned to you within one business day. When you receive the formatted report, save it on a temporary location on the management server.

7.

16

Preparing for the upgrade

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. Select the Collect data for all switch groups check box to create reports for all fabrics. 3. 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. 4. 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. 5. Select a format for the report by selecting HTML Report, Microsoft Excel Report, or both. 6. Under Data Collection, click Start. If you selected the option to collect switch performance data, it will take 10 additional minutes to collect the data. 7. Select Default Mail Client in the Launch Mail Client panel. The location of the report is displayed in the message body of the default mail launched. 8. Manually attach the raw report created with the subject line: HP Essentials SAN Visibility Report Request. Send the report to the e-mail address: [email protected]. An automated email response is returned, confirming receipt of the raw data file. Click Close. The data is processed and the formatted report returned to you within one business day. 9. When you receive the formatted report, save it to a temporary location on the management server or any server on which SAN Visibility is installed. A sample report is shown in Figure 5 (page 18).

Checking and upgrading your SAN infrastructure

17

Figure 5 Sample SAN Visibility report

Reading the report

1. 2. 3. 4. 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. In the navigation pane, click High Level Fabric Summary. The High Level Fabric Summary window opens (Figure 5 (page 18)). This report will identify the firmware and/or driver version that is currently running on your switches (including the HSV300S embedded switch controller) and HBAs.

18

Preparing for the upgrade

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)). Figure 6 Sample SAN Recommendations

If the firmware or driver version recommended is later than what is currently running, ensure that you upgrade the appropriate switch or HBA. NOTE: After completing required upgrades, HP recommends that you create a new SAN Visibility report to verify that all upgrades were successful.

Evaluating your configuration

Consider the following factors when determining if an online upgrade is appropriate for your environment: Queuing host I/OAfter 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. The resynchronization may take less than a minute, but it may take time to clear the backlog of requests and some host I/O may experience timeouts. The HP recommended driver timeout value is 60 seconds. When an I/O timeout occurs, multipath drivers typically retry the I/O request on the same or an alternate path. These retry algorithms have operating system and HBA dependencies and may extend the time that host I/O will be allowed to complete successfully beyond the 60second timeout. Additionally, some applications may be more sensitive to I/O delays. Processing host I/O during the upgradeThe upgrade competes with host requests that have a higher priority, which can affect the upgrade outcome. To ensure that host I/O from business

Evaluating your configuration

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 ViewThe 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. An HP P6000 Command View discover operation may be required to re-establish communication with the array.

XCS 10001000 upgrade considerations

Before upgrading to XCS 10001000, consider the following: Check that the Device Addition Policy is set to manual. If it is set to automatic, you must change it to manual before you perform the controller software upgrade. See Checking the disk grouping policy (page 37) for more information. If the array contains solid state disk (SSD) drives, the upgrade must be done offline. XCS 10001000 requires more free space than earlier XCS versions. Before upgrading, verify the amount of free space available. For more information, see the following advisory: http://saw.cce.hp.com/km/saw/view.do?docld=emr_na-c02931 184 When upgrading from XCS 0953x000, an online upgrade is supported. When upgrading from XCS 09522000 or earlier, an online controller software upgrade is not supported on an array connected to a host in an environment or configuration using persistent reservations (for example, Windows Hyper-V with Cluster Shared Volumes, Windows 2008 SQL clusters, or Symantec Veritas Cluster Services with IO fencing). The EVA resynchronization time is affected by both the total virtual mapped capacity and the number of virtual disks. The number and capacity of all virtual disks, snapshots, snapclones, mirrorclones, containers, data replication log disks, and the number of DR groups contribute to the total virtual mapped capacity. To ensure a resynchronization time of less than 60 seconds when performing an online upgrade, the total virtual mapped capacity and the number of virtual disks that are configured on an EVA should be one of the following:

Less than 400 TB total virtual mapped capacity and less than 512 virtual disks Less than 350 TB total virtual mapped capacity and less than 1,024 virtual disks Less than 300 TB total virtual mapped capacity and less than 2,048 virtual disks

For the number of virtual disks, go to the Initialized Storage System Properties page and add the values in the 'Virtual Disks' total box and the DR groups total box. (Each DR group has a log disk, which is a protected vdisk used exclusively by the DR group.) Use the following formula to calculate the total virtual mapped capacity, where capacity is given in TB: Total virtual mapped capacity in TB = (total virtual disk capacity) + (13 * the capacity of DR group logs) + (0.5 TB * number of DR groups) To calculate the values for the formula, use HP P6000 Command View: To calculate (total virtual disk capacity), determine the capacity values for all virtual disks, snapshots, snapclones, mirrorclones, and containers and add them together:

Virtual disks: For each virtual disk, go to the Vdisk General Properties window and record the value listed in the Requested capacity box. Snapshots (demand allocated and fully allocated): For each snapshot, go to the Vdisk General Properties window of the original virtual disk and record the value listed in the Requested capacity box.

20

Preparing for the upgrade

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.

To calculate (13 * the capacity of DR group logs): For both the source and destination DR groups, go to the Log tab of the DR group properties window. Under Log Size, record the value in the Actual box. Add the log size values of both and multiply the result by 13. To calculate (0.5 TB * number of DR groups): On the Data Replication Folder Properties page, record the value in the Total DR groups box, and multiply the value by 0.5 TB. For example, given 100 virtual disks with total virtual disk capacity of 200 TB, 3 TB of DR group logs, and 30 DR groups, the total virtual mapped capacity is 200 + (13*3 TB) + (0.5 TB*30) or 200+39+15 or 254 TB. This configuration is supported for an online upgrade. A configuration with 400 virtual disks with total virtual disk capacity of 800 TB, 4 TB of DR group logs and 40 DR groups, has a total virtual mapped capacity of 800 + (13*4 TB) + (0.5 TB*40) or 800+52+20 or 872 TB. This configuration is not supported for an online upgrade. If the result is less than the total virtual mapped capacity values cited for the number of virtual disks you have, an online upgrade is supported. If it is more than the values cited, you must do an offline upgrade. For HP P6000 Continuous Access environments, see Preparing the HP P6000 Continuous Access environment for an upgrade (page 36). Stop all storage modification jobs (such as creation, deletion, shrinkage, expansion, and presentation) 30 minutes before starting the controller software upgrade. If you are upgrading from XCS 09522000 or earlier and if the configuration contains mirrorclones, you must delete, detach, or fracture the mirrorclones before starting the controller software upgrade. Do not change array components during the controller resynchronization process, which occurs after the controller software upgrade is complete. The controller software upgrade process maintains a copy of the metadata in controller memory instead of retrieving metadata from disks during a resynchronization. Component changes cause metadata to be retrieved from disks, making the resynchronization process take longer to complete, which may exceed host or application timeout values. When the controller software upgrade is complete (including upgrading the firmware on the disk enclosure I/O modules), it may take up to 20 minutes to stabilize device port operations. (The I/O module firmware upgrades are performed sequentially to ensure that host I/O continues during the upgrade.) HP recommends that you check the state of the I/O modules on each disk enclosure to ensure that the upgrade was completed successfully. To do this, confirm that the latest I/O module firmware version is displayed. In a few cases, it has been observed that certain fields on the I/O module tab of the Disk Enclosure Properties page (in HP P6000 Command View) appear blank, specifically, Hardware type, Hardware revision, and Assembly serial number. These blank fields do not affect I/O module operation and do not mean that the upgrade was unsuccessful. HP recommends that you wait 20 minutes to see if the fields become populated. If not, you can reset the I/O module; this is an optional step. However, if a disk enclosure reports a failed port or SPOF condition 20 minutes after the upgrade has completed, you must reset the I/O module. See Resetting the I/O module (page 54) for the steps to verify the I/O module firmware version and reset the I/O module.
XCS 10001000 upgrade considerations 21

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 applicationsDo not select a time that could affect critical business applications. I/O loadSelect 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.

While there are advantages to performing an online upgrade, there are circumstances when it is not advisable. Therefore, give careful consideration to your configuration and your application deployment before making an attempt to do an online upgrade. NOTE: When determining the appropriate time to do an online upgrade, ensure that no configuration-related replication tasks are in process (creating or deleting DR groups, snapshots, snapclones, or mirrorclones, or presenting to hosts).

Analyzing array I/O using HP Command View EVAPerf

Use the HP Command View EVAPerf tool included with HP P6000 Command View to gather and analyze statistics on array utilization. This section provides recommendations on using HP Command View EVAPerf to gather statistics to help identify periods of low array activity. For more information about HP Command View EVAPerf, see the chapter Monitoring array performance in the HP P6000 Command View User Guide. See Table 1 (page 6) for the link to this document. IMPORTANT: If you have an array-based management system, you can install and run HP Command View EVAPerf on a supported Windows host connected to the 4400, P6300 EVA or P6500 EVA.

Guidelines for using HP Command View EVAPerf

NOTE: Before using HP Command View EVAPerf, you may want to configure friendly names to simplify identifying your arrays, virtual disks, and hosts. See the HP P6000 Command View User Guide for more information about friendly names. Use the following guidelines to ensure that you select an appropriate period to perform an online upgrade of controller software: Identify a time period during which I/O load on the array will be low. During this time period, run HP Command View EVAPerf to gather I/O data. Run HP Command View EVAPerf to gather I/O data during the chosen time period. For example, if you suspect that I/O load may be low between midnight and 2 AM on Sunday morning, run HP Command View EVAPerf during this period. If the I/O load pattern is low, capture the data over the same time period several more times to ensure the low I/O load pattern is repeatable. After selecting a time period for the upgrade, perform the following tasks to ensure that I/O activity does not increase unexpectedly during the upgrade:

Alert all system users that they should minimize the load on the array during the time period selected for the upgrade. Identify any automated processes that may increase the I/O load during the upgrade period, including backup applications and scripts. Suspend these processes for the duration of the upgrade.

22

Preparing for the upgrade

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. For example, if you enter evaperf hps -cont 2 -dur 30, host port data is displayed at two-second intervals for a total of 30 seconds. -sz array: Limits data collection to the specified array(s). You must specify at least one array; use the array World Wide Name (WWN) or friendly name. -fo filename: Directs output to a specified file. Include the path information as necessary.

Running HP Command View EVAPerf

1. 2. Double-click the HP Command View EVAPerf icon on the desktop. The HP Command View EVAPerf command window opens. Enter the following command to capture and display the total IOPS (Req/s) and throughput (MB/s), where n is the interval in seconds and m is the duration in seconds: evaperf as -cont n dur m sz array -fo filename Specify an interval and duration that will enable you to view a period of low I/O activity. For example, collect data once every 10 minutes for a period of 6 hours when you plan to do the upgrade to familiarize yourself with characteristic I/O and throughput values. For example, the following command will capture data at 10minute intervals (60*10) for 6 hours (60*60*6) on an array named EVA1, and store the output in a file named EVA_upgrade: evaperf as cont 600 dur 21600 sz EVA1 -fo C:\EVA_upgrade You can store the data in a folder or drive of your choice. (To see your own friendly names, run HP Command View EVAPerf with the fnh command and list the names with the ls command.)

Selecting a time to perform an online upgrade

23

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. Table 3 Configurations validated by HP
Array Number of disks Disk groups Vraid type Total host workload EVA4400 96 10K RPM disks 2 disk groups of 48 disks each Vraid6 2950 IO/sec total host workload EVA6400 216 10K RPM disks EVA8400 324 10K RPM disks

2 disk groups of 108 disks 2 disk groups of 162 disks each each Vraid6 6640 IO/sec total host workload Vraid6 9958 IO/sec total host worklaod

NOTE: You can also use the HP TimeLine Visualizer (TLViz) tool to generate graphical representations of performance data. See Using the HP Command View EVAPerf TLViz formatter in the HP P6000 Command View User Guide for more information.

Identifying virtual disk activity

If you cannot identify a period that meets the necessary I/O load requirements, identify those applications that impose heavy I/O loads, and suspend them long enough to perform the upgrade. To do this, use HP Command View EVAPerf to view virtual disk activity. For example, after running HP Command View EVAPerf, you determine that all virtual disks on the array are nearly idle except for one virtual disk. To perform an online upgrade, halt the application that is imposing the load on the busy virtual disk. This will be far less disruptive to your environment than performing an offline upgrade. To view virtual disk activity: 1. Double-click the HP Command View EVAPerf icon on the desktop. The HP Command View EVAPerf command window opens. 2. Enter the following command: evaperf vd cont n dur m sz array -fo filename Select an appropriate interval and duration that will enable you to view a period during which you plan to perform the upgrade. For example, the following command will capture data at 10minute intervals for 2 hours on an array named EVA1, and store the output in a file named virtual_disks: evaperf vd -cont 600 -dur 7200 -sz EVA1 -fo C:\virtual_disks

24

Preparing for the upgrade

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. Virtual disks must be presented to a host to be seen by HP Command View EVAPerf. However, replication volumes on the replication system are visible without being presented. Because the array controllers are active/active, one controller is preferred (the owning controller) but requests can still be processed by the other controller (the proxy controller). In active/active controllers, all host requests are logged by the receiving controller only, whether owning or proxy. Thus, all request rate and data rate activity for a virtual disk is the total from both controllers. Table 4 (page 25) lists the statistics you can use to determine the virtual disk activity. 1. Check these values for requests: Read Hit (Req/s), Read Miss (Req/s), and Write (Req/s) (columns 2, 5 and 8). 2. Look for values in the hundreds. Values in the thousands or tens of thousands indicate a very active process, such as an active database, that should not be disrupted. If you see high values for requests during the time period you selected, look for another time period to perform the upgrade.

Figure 7 Sample virtual disk statistics display

Table 4 HP Command View EVAPerf virtual disk statistics

Counter Read Hit Req/s Description 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 a prefetch operation generated by a sequential read data stream. The rate at which data is read from the array cache memory because of read hit requests. The average time it takes to complete a read request (from initiation to information receipt) from the array cache memory. The number of read requests per second that failed to complete from the array cache memory and were completed from physical disks instead. The rate at which data is read from physical disks because the data is not present in the array cache memory. The average time it takes to complete a read request (from initiation to information receipt) from the physical disks.

Read Hit MB/s Read Hit Latency (ms) Read Miss Req/s Read Miss MB/s Read Miss Latency (ms)

Selecting a time to perform an online upgrade

25

Table 4 HP Command View EVAPerf virtual disk statistics (continued)

Counter Write Req/s Description 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. The rate at which data is written to the virtual disk by all hosts; includes transfers from the source array to the destination array. The average time it takes to complete a write request (from initiation to receipt of write completion). The rate at which data is written to a physical disk for the associated virtual disk. The sum of flush counters for all virtual disks on both controllers is the rate at which data is written to the physical drives, and is equal to the total host write data. Data written to the destination array is included. Host writes to snapshots and snapclones are included in the flush statistics, but data flow for internal snapshot and snapclone normalization and copy-before-write activity are not included. The rate at which data travels across the mirror port to complete read and write requests to a virtual disk. This data is not related to the physical disk mirroring for Vraid1 redundancy. Write data is always copied through the mirror port when cache mirroring is enabled for redundancy. In active/active controllers, this counter includes read data from the owning controller that must be returned to the requesting host through the proxy controller. Reported mirror traffic is always outbound from the referenced controller to the other controller. The rate at which data is read from the physical disk to cache in anticipation of subsequent reads when a sequential data stream is detected. A sequential data stream may be created by host I/O or other I/O activity that occurs because of a DR initial copy or DR full copy.

Write MB/s Write Latency (ms) Flush MB/s

Mirror MB/s

Prefetch MB/s

Managing host I/O timeouts for an online upgrade

The defaults for host operating parameters, such as LUN timeout and queue depth, ensure proper operation with the array. These values are appropriate for most array operations, including online controller software upgrades. In general, host LUN timeouts of 60 seconds or more are sufficient for an online upgrade. In most situations you will not need to change these settings to perform an online controller software upgrade. If any host timeout values have been changed to less than the default (typically 60 seconds), you must reset them to their original default. The following sections summarize the steps and commands for checking and changing timeout values for each supported operating system. See the operating system documentation for more information. IMPORTANT: Depending on your operating system, changing timeout values may require a reboot of your system. To minimize disruption of normal operations, schedule reboots one node at a time. In a cluster environment, plan your reboots one node at a time.

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.

Default timeout values

Sdisk timeout: 30 seconds (LVM) lvol timeout: 0 seconds (default=0, retries forever)

26

Preparing for the upgrade

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 PR_key_value Algorithm Value not applicable fail_over Description Sets the key value for persistent reservations. Persistent reservations are not supported. 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. Sets the path health-check feature to check each device every 60 seconds. Specifies the I/O paths monitored by the path health-check feature. The value nonactive checks all I/O paths for Failed status, and checks standby paths for Used/Opened devices. Sets the queue depth. Sets the reserve policy to standard SCSI-2 reservations. Sets the read/write timeout to 60 seconds.

hcheck_interval hcheck_mode

60 nonactive

queue_depth reserve_policy rw_timeout

8 single_path 60

Linux Red Hat and SUSE

NOTE: The RHEL 4/SLES 9 SCSI device has a default 30second timeout value with up to 5 retries. The RHEL 5/SLES 10 SCSI device has a default 60second timeout with up to 5 retries. In general, these timeout periods are sufficient for an online controller software upgrade. Native Linux Device-Mapper Multipath If you are using Native Linux Device-Mapper Multipath, see the Native Linux Device-Mapper Multipath for HP StorageWorks Disk Arrays reference guide for additional configuration details. The document is located on the Single Point of Connectivity Knowledge website: http://www.hp.com/storage/spock In the left navigation pane, select Solutions: Linux under Application Notes.

Configuration recommendations
Table 6 QLogic driver parameters
Parameter qdepth port_down_retry_count login_retry_count failover load_balancing excludemodel auto_restore Failover enabled 16 30 30 1 1 0x0 0xA0 Single path 16 64 30 0 1 0x0 0xA0

Managing host I/O timeouts for an online upgrade

27

Table 7 Emulex driver parameters

Parameter HPELXLPFC nodev_timeout qdepth discovery_threads Single path y 60 30 1 With Multipulse 10 16 32

To check or set Linux parameters, use the set_parm executable located in the
/opt/hp/<driver>

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. This is important for both online upgrades and general data integrity. Online controller software upgrades are supported with Linux boot devices.

Mac OS X
Online controller software upgrades are not supported for arrays connected to Mac OS X hosts. Controller software upgrades must be done offline for Mac OS X hosts.

Microsoft Windows
Guidelines for Microsoft Windows follow: Ensure that MPIO is installed and both paths are active and have access to the array. Array boot devices are supported with online controller software upgrades, but the page-file disk must not be on the array being upgraded during an online upgrade. See your Windows documentation for instructions on changing the location of the page-file disk. If the array being upgraded is used as a quorum disk in a Microsoft Windows cluster, an online controller software upgrade may cause the cluster to time out on the quorum disk and attempt to transition disks on that node to the surviving (secondary) node. The cluster may hang in this situation and require a cluster reboot to recover. A workaround is to transition all disks on the secondary node to the primary node, stop the cluster services, and shut down the secondary node before starting the controller software upgrade. Once the upgrade is complete, restart the cluster services and the secondary node to return it to the cluster. Shut down the secondary node to prevent automatic failover.

Checking timeout values

Ensure that the key timeout setting in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\TimeoutValue 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.

OpenVMS
The maximum LUN timeout value is 120 seconds.
28 Preparing for the upgrade

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. Online controller software upgrades are supported in OpenVMS cluster environments where the array is the cluster boot device.

Solaris
Solaris supports online controller software upgrades with the following driver timeouts: Sun drivers (qlc or emlxs): 60 seconds QLogic (qla2300): 60 seconds Emulex (lpfc): 60 seconds

Checking or changing timeouts

For Sun drivers, add the following lines to the /etc/system file:
set sd:sd_io_time=60 set ssd:ssd_io_time=60

For the QLogic driver, edit the /kernel/drv/qla2300.conf file and change the hbax-link-down-timeout value to 60: hba0-link-down-timeout=60; For the Emulex driver, edit the /kernel/drv/lpfc.conf file and change the linkdown-tmo value to 60: linkdown-tmo=60;

VMware
VMware ESX (Hypervisor) does not time I/O for a guest operating system. Therefore the SCSI timeouts on commands issued by each VMware guest (Linux, Windows, Solaris) are the timeouts set for these systems.

Xen Citrix
For Xen Citrix, (except for NFS SR timeouts because Citrix XenServer 5.0 mounts using software with nondefault timeout values) use the values described in Linux Red Hat and SUSE (page 27). To check or set Xen Citrix parameters, use the set_parm executable located in the
/opt/hp/<driver>

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. 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. Consequently, if the application is running on a properly configured operating system, the online controller software upgrade will complete successfully. Evaluate any
Managing application I/O timeouts for an online upgrade 29

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.

Managing external devices

If the array is being used as external storage (virtualized behind an HP P9000 XP array), perform the following resets before doing the upgrade (you will reset them after the upgrade is complete): IMPORTANT: Vraid0 LUNs on the XP array are not supported during an upgrade.

Enable System Option Mode 725 on the XP Set the I/O Timeout to 240 seconds on all applicable external paths Set the Path Blockade Watch Timer to 180 seconds on all applicable external paths

Once the upgrade is complete, reset these parameters to their original values.

Managing an SVSP configuration for an online upgrade

If the array is in an SVSP configuration with SVSP synchronous mirrors, see the HP SAN Virtualization Services Platform Best Practices Guide for more information before upgrading. This document is available at http://www.hp.com/support/manuals. Select Storage Software under storage and then select HP SAN Virtualization Services Platform under Storage Virtualization Software.

Backing up all array data

Estimated time to complete: Varies When to perform: As close as possible to the upgrade Before starting the upgrade, HP recommends that you perform a full verified backup of all array data. Although not required, it is a best practice to back up your data before performing major operations such as software upgrades. Schedule the backup as close to the upgrade as possible. For more information about establishing and implementing backup procedures for the array, contact your HP sales representative. TIP: If using server-based management, HP recommends that you also back up the management server before you begin the upgrade.

Upgrading HP P6000 Command View

Estimated time to complete: 1520 minutes or longer, depending on your configuration When to perform: Anytime before the upgrade 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. Server-based management applies to all array models. Array-based management Beginning with HP P6000 Command View 8.1, the EVA4400 is shipped with HP P6000 Command View preinstalled on the management module in the controller enclosure (9.4 for P6300/P6500 EVA). Only one component of the software suite (HP P6000 Command View) is installed. Array-based management applies only to the EVA4400, P6300 EVA, and P6500 EVA.

30

Preparing for the upgrade

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.1, HP P6000 Command View upgrade support, in the HP P6000 Enterprise Virtual Array Compatibility Reference. For more information on HP P6000 Command View and to download the HP P6000 Command View Installation Guide and the release notes, go to the website listed in Reference documentation (page 6).

Upgrading on a management server

This procedure is for a typical HP P6000 Command View installation on a management server. To use the custom installation procedure, which lets you select the components to install, see the HP P6000 Command View Installation Guide for instructions. To install the complete software suite: 1. Close all applications running on the management server. 2. Insert the installation DVD in the drive. 3. Browse to the installation DVD. 4. Double-click HP StorageWorks Command View EVA Software Suite.exe to start the installation. The InstallAnywhere Command View window opens. 5. Select the preferred language from the drop-down menu (English or Japanese). (On an English Windows system, the drop-down menu contains only English; on a Japanese Windows system, the drop-down menu contains both English and Japanese.) Click OK. The Introduction window opens. 6. 7. 8. Click Next. The CV EVA License Agreement window opens. Read and accept the terms of the license agreement. Click Next. The Choose Install Set window opens. 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. 1 1. 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.
Upgrading HP P6000 Command View 31

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: 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. In the navigation pane, click Hardware and verify that: New, uninitialized arrays appear as uninitialized arrays. Previously initialized arrays appear with their previous names and correct status. (Select each storage array to view the Properties window.) Previous disk groups, hosts, virtual disks, and other resources appear in the navigation pane.

If the information is not displayed properly, you may need to configure your browser settings. See the HP P6000 Command View Installation Guide for more information.

Upgrading the management module

Estimated time to complete: 25 minutes When to perform: Anytime before the upgrade If you have an EVA4400, P6300 EVA or P6500 EVA, follow the procedures in this section to: Upgrade HP P6000 Command View on the management module (for array-based management). Upgrade the management module software.

NOTE: Management module software is bundled with the array-based management version of HP P6000 Command View. Thus, when you upgrade HP P6000 Command View on the management module, you are also upgrading the management module software. Even if you are not using array-based management, you must complete the procedure in this section for the EVA4400, P6300 EVA, or P6500 EVA, to ensure that the array has the current management module software. To upgrade the management module: 1. Connect a server with a DVD drive to the management module port (1, Figure 8 (page 32)) 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

32

Preparing for the upgrade

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. 5. 6. 7. 8. 9. Log in as an HP EVA administrator (user name admin and the password). The P6000 Control Panel GUI appears. In the navigation pane, select Update management module firmware. The Update Management Module Firmware window opens. Click Browse and browse to the installation DVD. Select the ABM.pkg file and click Next step. Follow the online instructions and click Finish. A confirmation window opens. Click OK. The Management Module Restart in Progress window opens. The image files are loaded. This step can take several minutes. IMPORTANT: The management module will restart upon completion of the update. Allow up to 15 minutes to re-establish a browser connection. Do not reseat, restart, or reset the management module during this time if you are unable to reconnect from your browser. After the management module restarts, it may exhibit slow response time for about 5 to 10 minutes while gathering array information and completing background processes. Upon completion of the upgrade and restart, one of the following occurs: The P6000 Control Panel login window opens. Continue with Verifying installation on the management module (page 33). The P6000 Control Panel login window fails to open, which occurs if you are using the default IP address (192.168.0.1) for the management module. Continue with Step 10.

10. Press the reset button (2, Figure 8 (page 32)) on the management module to activate the IP address. Upon reset, the P6000 Control Panel login window opens. Continue with Verifying installation on the management module (page 33).

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.
Upgrading the management module 33

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. If it is incorrect, enter the correct time and save your changes.

Upgrading browsers and JRE

Estimated time to complete: 1020 minutes When to perform: Anytime before the upgrade Ensure that you are using a supported browser and JRE. HP P6000 Command View may not work correctly with an unsupported browser. The JRE is not used by HP P6000 Command View, but is required for HP P6000 Replication Solutions Manager, WEBES, and SAN Visibility. See Upgrading HP P6000 Replication Solutions Manager (optional) (page 35) for more information. For information on supported browsers, see Table 5.0, Browser support, in the HP P6000 Enterprise Virtual Array Compatibility Reference. See Reference documentation (page 6) for the link to this document. NOTE: If you need to update the browser on remote computers, do so after you have upgraded HP P6000 Command View.

HP Insight Remote Support software

HP strongly recommends that you install HP Insight Remote Support software to complete the installation or upgrade of your product and to enable enhanced delivery of your HP Warranty, HP Care Pack Service or HP contractual support agreement. HP Insight Remote Support supplements your monitoring, 24x7 to ensure maximum system availability by providing intelligent event diagnosis, and automatic, secure submission of hardware event notifications to HP, which will initiate a fast and accurate resolution, based on your products service level. Notifications may be 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. 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. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight Remote Support Advanced.

Details for both versions are available at: http://www.hp.com/go/insightremotesupport To download the software, go to Software Depot: http://www.software.hp.com
34 Preparing for the upgrade

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. Estimated time to complete: 1020 minutes When to perform: Anytime before the upgrade If HP P6000 Replication Solutions Manager is installed, you must upgrade it to the minimum required version (see Checking management software versions (page 8)). HP P6000 Replication Solutions Manager is an optional interface for HP P6000 Business Copy and HP P6000 Continuous Access. For installation information, see the HP P6000 Replication Solutions Manager Installation Guide. For general usage information, see the HP P6000 Replication Solutions Manager Administrator Guide. See Reference documentation (page 6) for links to these documents. When you purchase HP P6000 Replication Solutions Manager, you can choose to receive a software DVD or an E-Delivery kit. If you choose an E-Delivery kit, you will receive an email from HP with the download instructions. If you have a support contract with HP, you can download the software from the IT Resource Center (ITRC). For instructions, see Required kits (page 6). NOTE: For E-Delivery kits, be sure to save the HP email with the download instructions. You will need them if you need to download the software again.

Monitoring array stability

Estimated time to complete: 2530 minutes When to perform: 48 hours before the upgrade The array configuration should be stable for 48 hours before the upgrade. Check the status of the array to ensure that it is stable, and continue monitoring status until the upgrade begins. 1. Open HP P6000 Command View and click the icon of the array you want to upgrade. 2. 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. b. Click View Events. The View Events window opens (Figure 9 (page 35)). Figure 9 View Events window

c.

Select Controller Event Log. The Controller Events window (Figure 10 (page 36)) opens in a new browser window.

Upgrading HP P6000 Replication Solutions Manager (optional)

35

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. 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. NOTE: The leveling process does not impact the upgrade. Leveling is suspended during the upgrade and resumed when the upgrade is complete. Suspend any processes or applications that may change the array configuration, such as backups and snapshot creation or deletion. Stop any HP Storage System Scripting Utility scripts that are scheduled to run automatically.

Preparing the HP P6000 Continuous Access environment for an upgrade

NOTE: HP P6000 Continuous Access is currently available with server-based management only. Estimated time to complete: Varies depending on replication configuration When to perform: As close as possible to the upgrade 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. Before you upgrade an array in an HP P6000 Continuous Access environment, ensure that all arrays in the storage network are running the same version of controller software. This ensures that when you upgrade one array, the storage network will have only two versions of controller software. You cannot have more than two versions in an HP P6000 Continuous Access environment. For all DR groups, ensure that the failsafe state is Unlocked and the Failsafe on unavailable member mode is Disabled.

36

Preparing for the upgrade

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. Ensure that the previously described requirements are met on the second system. If you need to upgrade both VCS and XCS, complete the upgrade of one before upgrading the other. For example, upgrade all arrays running VCS before upgrading arrays running XCS. Ensure the connection between the arrays is not compromised or failed. 1. Click the Data Replication folder in the navigation pane. 2. Check the connection state in the Data Replication Folder Properties window. All EVA arrays must be running normally with fully functional controller pairs.

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). For all DR groups, ensure that the failsafe state is Unlocked and the Failsafe on unavailable member mode is Disabled. Do not perform HP P6000 Continuous Access copy/merge activities across sites, site failovers, cloning, or grouping/ungrouping of disks. Do not add or remove members from DR groups.

Checking the disk grouping policy

You must check the configuration of the EVA being upgraded to determine if the disk grouping policy is set to automatic. If it is set to automatic, you must change it to manual before continuing with the upgrade. NOTE: If you are running HP P6000 Command View 10.0 or later, a warning message may appear during the controller software upgrade if the Device Addition policy is set to automatic. To perform the upgrade: 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. HP P6000 Command View identifies the controllers as A and B.

In the navigation pane, select the storage system being upgraded. Select System Options.
Checking the disk grouping policy 37

c. d. e. f. 3.

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.

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. A pop-up warning will display; enter YES and click RESTART. f. Controller B will restart. Wait 3-5 minutes for the restart to complete. Verify the array is operational with both controllers active.

4.

Proceed with any remaining pre-upgrade tasks and then continue with the controller software upgrade. After the upgrade, you can change the Device addition policy to automatic, if preferred.

Saving array configuration data

Estimated time to complete: 1015 minutes When to perform: As close as possible to the upgrade 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. You can perform this procedure from the management server where HP P6000 Command View is installed, or from any host running the utility to communicate with HP P6000 Command View. NOTE: 1. 2. 3. You will need the IP address or name of your management server to run the utility.

Double-click the HP Storage System Scripting Utility desktop icon to open the utility. When prompted, enter the management server name or IP address, user name, and password. Enter LS SYSTEM to display the arrays managed by the management server. 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. For example, if you specify a file name of LargeEVA.txt, the configuration files would be named LargeEVA_Step1A.txt, LargeEVA_Step1B.txt, etc. Files that do not contain configuration information are not created and therefore cannot be restored. You can view the contents of the configuration files with a text editor.

5.

Enter exit.

NOTE: You cannot use the utility to restore a configuration that contains disk drives of different capacities. You must manually restore that type of configuration. See Restoring an array configuration with different disk sizes and types in the HP Storage System Scripting Utility Reference for more information.

38

Preparing for the upgrade

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. As a best practice, also use the following commands to collect configuration data: LS DISK_GROUP FULL LS HOST FULL LS VDISK FULL LS ISCSI_HOST FULL LS ISCSI_LUN FULL

If applicable, use the following commands as well:

For more information about using the utility or the CAPTURE commands, see the HP Storage System Scripting Utility Reference. See Reference documentation (page 6) for the link to this document.

Task checklist
Use the following checklist to track your progress and mark when a task is complete. Table 8 Pre-upgrade task checklist
Task Checking the controller software version (page 8) Time required: About 5 minutes When to perform: Anytime before the upgrade Checking management software versions (page 8) Time required: 1015 minutes When to perform: Anytime before the upgrade Checking the array hardware (page 10) Time required: 1520 minutes When to perform: 12 weeks before the upgrade, and then daily until the upgrade is complete. Provide enough time to order and replace any failed components. Checking and upgrading your SAN infrastructure (page 11) Time required: After collecting and evaluating your configuration data on over several weeks, you can determine when is an appropriate time to do the upgrade. When to perform: Anytime before the upgrade Evaluating your configuration (page 19) Time required: Varies When to perform: As close as possible to the upgrade Selecting a time to perform an online upgrade (page 22) Time required: Varies When to perform: As close as possible to the upgrade Managing host I/O timeouts for an online upgrade (page 26) Time required: Varies When to perform: As close as possible to the upgrade Task checklist 39 Task complete

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 to perform: As close as possible to the upgrade Upgrading HP P6000 Command View (page 30) Time required: 1520 minutes When to perform: Anytime before the upgrade Upgrading browsers and JRE (page 34) Time required: 1020 minutes When to perform: Anytime before the upgrade HP Insight Remote Support software (page 34) Time required: 1020 minutes When to perform: Anytime before the upgrade Upgrading HP P6000 Replication Solutions Manager (optional) (page 35) Time required: 1020 minutes When to perform: Anytime before the upgrade Monitoring array stability (page 35) Time required: 2535 minutes When to perform: 48 hours before upgrade Preparing the HP P6000 Continuous Access environment for an upgrade (page 36) Time required: Varies depending on the replication configuration When to perform: As close as possible to the upgrade Saving array configuration data (page 38) Time required: 1015 minutes When to perform: As close as possible to the upgrade Task complete

40

Preparing for the upgrade

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. If you are still unable to resolve the problem, contact your HP-authorized service representative. IMPORTANT: For upgrade paths, see Table 3.1, Upgrade support for controller software versions, in the HP P6000 Enterprise Virtual Array Compatibility Reference.

Step 1. Checking the health of the Enterprise Virtual Array

Estimated time to complete: 2030 minutes Before upgrading the array, perform a final check of the overall status of all components. The pre-upgrade checks will help ensure that the array is ready for upgrading, but you should check the array status again. NOTE: If you are running HP P6000 Command View 9.3 or later, HP P6000 Command View will complete this check automatically when you upgrade the controller software. 1. 2. Open HP P6000 Command View and click the icon of the array you want to upgrade. Check for hardware errors. 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 1 1 (page 41)) opens. The Operational State box indicates if there is a hardware problem. Figure 1 1 Hardware Folder Properties window

b. c. d.

Select the array in the navigation pane and click Refresh to update the cache. 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 Disk Enclosure Properties window (Figure 12 (page 42)). The Operational state field indicates if there is a hardware error. If the operational state is good, proceed with the upgrade.

Step 1. Checking the health of the Enterprise Virtual Array

41

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). 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. The View Events window opens. c. d. Click Controller Event Log. The Controller Events window (Figure 13 (page 43)) opens in a new browser window. Check the Severity field to determine if any unexpected Critical events in the last 48 hours. have occurred

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

42

Upgrading the Enterprise Virtual Array

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. 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 the upgrade. Use proactive event notification to alert you if a critical event occurs during the 48 hours before the upgrade. NOTE: The leveling process does not impact the upgrade. Leveling is suspended during the upgrade and resumed when the upgrade is complete. Suspend any processes or applications that may change the array configuration.

Step 2. Configure User-Initiated Service Mode (UISM)

Estimated time to complete: 1015 minutes To avoid generating unnecessary events and alerts during the upgrade, enable UISM in HP P6000 Command View (requires version 9.3 or later). 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. In the Reason box, enter text to indicate that you are updating controller software. NOTE: 5. 6. 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.

If you are running an earlier version of HP P6000 Command View, complete the following steps to disable Remote Support software:
Step 2. Configure User-Initiated Service Mode (UISM) 43

1. 2. 3.

On the management server, open a command window. Enter the following commands to stop Remote Support software: C:\>net stop desta_service Enter exit.

Step 3. Disabling array passwords

Estimated time to complete: 1015 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. To disable password access to an array in HP P6000 Command View: 1. Open HP P6000 Command View in your browser. 2. Click Server Options in the Session pane. The Management Server Options window opens. 3. 4. 5. 6. 7. Click Manage storage system password access. The Storage System Password Access window opens. Click Disable. The Disable Password Access to Storage System window opens. Select the array World Wide Node Name from the drop-down list. Click Disable Password. A confirmation box opens. Click Yes to disable the password.

Step 4. Halting all host access to the array for an offline upgrade
IMPORTANT: For information about upgrade paths, see Table 3.1, Upgrade support for controller software versions, in the HP P6000 Enterprise Virtual Array Compatibility Reference. If the array contains solid state disk (SSD) drives, the upgrade must be done offline. Estimated time to complete: Varies by host: (must be performed for each host accessing the array). For the offline upgrade, all host I/O to the array must be stopped. Stop all applications accessing the array and shut down hosts, if necessary.

44

Upgrading the Enterprise Virtual Array

Step 5. Upgrading the controller software

Estimated time to complete: 2530 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. If configuration changes are in progress, monitor them using HP P6000 Command View and wait until they are complete before proceeding with the upgrade. The XCS 10001000 controller software image contains an update to the System Data Collector for upgrades from XCS 09522000. If you perform the upgrade on an EVA6400/8400 during heavy I/O load, the upgrade process may exceed the expected upgrade interval, perhaps generating an error message indicating that the upgrade has failed. However, this does not affect host I/O to the array and the upgrade should complete as expected.

Procedure 1 1. 2. 3. 4. Open HP P6000 Command View in your browser. In the navigation pane, select the array you want to upgrade. The properties window for the selected array opens. Select the System options tab. Click Code load system. The Code Load Selection window opens (Figure 14 (page 45)). Figure 14 Code Load Selection window storage system

5.

Choose Code Load Storage System to continue the upgrade. Click Select to proceed or Cancel to exit the procedure. A warning confirmation window opens (Figure 15 (page 45)). Figure 15 First system code load confirmation window

Step 5. Upgrading the controller software

45

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.

If your drive-addition policy is set to Automatic, respond to the following message:

9.

If your drive-addition policy cannot be determined, respond to the following message:

10. The Code Load Storage System Page 2 window opens.

46

Upgrading the Enterprise Virtual Array

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.

1 1. 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. Upgrading the controller software

47

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: EVA4400 EVA6400 EVA8400 Select this file: \HSV300\10001000\300_10001000.SSS \HSV400\10001000\400_10001000.SSS \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 19 Second code load confirmation window

Enter YES (all uppercase) and click Continue. 14. The Code Load Storage System Page 5 window (Figure 20 (page 49)) opens. Read any pre-update application notes before proceeding. Click Finish to proceed or Cancel to exit the procedure.

48

Upgrading the Enterprise Virtual Array

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. Upgrading the controller software

49

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. When the array is available, the array appears as available in the navigation pane. Continue with Step 16 to verify that the upgrade completed successfully. After Figure 22 (page 50) appears, the controllers resynchronize and begin running the new controller software. Once resynchronization is complete, the controllers are ready for host 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 50)). Figure 23 Storage System Updating Firmware

50

Upgrading the Enterprise Virtual 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. Upgrading the controller software

51

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. To change the protocol default setting to HP FC Data Replication Protocol, complete the following steps in HP P6000 Command View: 1. In the navigation pane, select the Data Replication folder. The Data Replication Properties Folder window opens in the content pane. 2. 3. 4. 5. Select Data Replication Options. The Data Replication Options window opens. Select Set Data Replication Protocol. The Data Replication Protocol Options window opens. Select HP FC Data Replication Protocol. Select Save Changes, and click OK.

On the EVA4400, if the controller logs are not being retrieved correctly, see Controller logs possibly retrieved incorrectly after upgrading to XCS 10001000 on the EVA4400 in the HP P6000 Enterprise Virtual Array Release Notes (XCS 10001000).

17. After 30 minutes, verify the I/O module firmware version and the states of each I/O module in each disk enclosure: a. In HP P6000 Command View, go to the Hardware folder in the navigation pane and select a disk enclosure. The Disk Enclosure Properties window opens. b. c. d. Click the I/O tab. Record the firmware version and operational state of each I/O module (both I/O module A and B), and record any I/O modules that have blank fields. Verify that 0105 or higher appears in the Firmware revision field (for I/O modules A and B), and that the Operational state (for I/O modules A and B) is Good ( Figure 26 (page 53)) for every I/O module. If so, the upgrade was successful.

52

Upgrading the Enterprise Virtual Array

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. See Resetting the I/O module (page 54) for more information. e. Check the operational states that you recorded and proceed as follows: Good: No action Loading firmware: The I/O module firmware load is blocked. Corrective action is required somewhere on the array (but not on this I/O module). Continue with Step 18 Any state other than Good or Loading firmware: Corrective action is required on this I/O module. Continue with Step 18.

18. Check the event log for the code-load-blocked code (066df308, critical event). If you do not see this event, contact your HP-authorized service representative for assistance. If you see this event, continue with Step 19.

Step 5. Upgrading the controller software

53

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). Before you perform the reset, continue with Step 19.b to check for disk drive issues. b. Look at the disk enclosures in the navigation pane. For any disk enclosure with a yellow attention or red warning icon next to it, expand the navigation tree to locate the component with the problem. Record the enclosure and the affected side (A or B). If you found the blocked event, but you cannot isolate a component causing the problem, contact your HP-authorized service representative for assistance. 20. Correct any problems identified in Step 19. a. If there is an I/O module problem, follow the instructions in Resetting the I/O module (page 54) for the affected I/O module. After completing the reset, repeat Step 16. If the same problems are detected, reset the other I/O modules in the disk enclosures that were previously reset, following the instructions in Resetting the I/O module (page 54). After completing this second reset, repeat Step 17. If the same problems are detected, contact your HP-authorized service representative for assistance. If no further problems are detected, continue with Step 6. Upgrading the disk drive firmware (page 55). b. If there is a disk drive problem, determine which drive port (A or B) is causing the code-load-blocked condition. Refer to the list recorded in Step 19.b, and follow the instructions in Resetting the I/O module (page 54) for the I/O module associated with each affected drive port. The associated I/O module is in the same disk enclosure and on the same side as the affected port. After completing the reset, repeat Step 17. NOTE: Complete the I/O module resets before performing any other corrective action indicated by other service procedures.

Resetting the I/O module

NOTE: When resetting the I/O module, consider the following: You must reset one I/O module at a time. Before each I/O module reset, check the I/O tab of the Disk Enclosure Properties window to ensure that no exception conditions exist that may impact the reset. For example, if you want to reset I/O module B, verify that I/O module A is in an optimal (Good) state (and vice versa). Wait at least one minute between resets.

You can reset the I/O module in one of two ways: Reset each I/O module individuallyUse this method to reset up to five I/O modules or if an offline upgrade is not possible. I/O throughput is briefly reduced but does not stop host I/O so you can do an online controller software upgrade. Further, resetting a few I/O modules individually will not take long. Power cycle the arrayUse this method of you need to reset six or more I/O modules or if an offline upgrade is possible. Although power cycling an array will interrupt I/O and require an offline upgrade, it will take less time than resetting several I/O modules individually. If an offline upgrade is not possible, you can reset the I/O modules individually.

54

Upgrading the Enterprise Virtual Array

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: On the EVA4400, press and hold the enclosure power button on the rear of the controller for a minimum of 15 seconds. The power button and the green LED start to blink when held from 4 to 10 seconds. On the EVA6400/8400, press and release the power button on the rear of the controller. The power LED turns amber and the shutdown process is complete. To power down the shelf, ensure that the controllers have shut down, and then remove both power cables from all enclosures. Alternatively, you can power down the entire rack.

2.

Power on the array: a. Power on the circuit breakers on both array rack power distribution units. Verify that all disk enclosures are operating properly. The status indicator and the power indicator should be on (green). b. Power on each controller (EVA6400/8400) or the controller enclosure (EVA4400). Allow the array to fully start up. c. Start HP P6000 Command View and verify connection to the array. If the array is not visible, click EVA Storage Network in the navigation pane, and then click Discover in the content pane to allow HP P6000 Command View to discover the array. Verify the status of each host before enabling access.

d.

Step 6. Upgrading the 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 array. It can take from 30 seconds to 3.5 minutes per drive to upgrade the firmware. Review the following guidelines before proceeding with the upgrade: You can be using array-based or server-based management to upgrade the disk drive firmware. Check the disk group occupancy alarm setting before upgrading disk drive firmware. See the best practices configuration white paper for guidelines on how to configure this setting based on your capacity. Locate the white paper for your array model at: http://h18006.www1.hp.com/storage/arraywhitepapers.html When using HP P6000 Command View 9.2 or later, you can upgrade disks that contain Vraid0 virtual disk data by halting all I/O to Vraid0 virtual disks (other Vraid virtual disks can continue to service host I/O). When using HP P6000 Command View versions earlier than 9.2, you must either delete the Vraid0 virtual disks or ungroup the disks individually before upgrading disk drive firmware. For EVA4400 and EVA6400/8400, you must be running XCS 09522000 or later to upgrade disk drive firmware online. If you are running an XCS version earlier than 09522000, you must upgrade disk drive firmware offline. Although it is not required that the disk drive firmware be upgraded when the controller software is upgraded, it is strongly recommended that you perform these tasks together. The
Step 6. Upgrading the disk drive firmware 55

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. If an error occurs, the upgrade process stops. You must restart it to upgrade disks that have not yet been upgraded. Any disks that were upgraded before the error occurred do not have to be upgraded again. Check the logs to verify their status. When you restart the process, it begins with the next disk that needs to be upgraded.

Upgrading firmware on all disks

Upgrade the disk drive firmware after you upgrade the controller software. 1. Confirm that there is enough free space available to manage disk failures that might occur after the disk drive firmware upgrade. For more information, see the capacity management details in the best practices configuration white paper (for your array model), located at: http://h18006.www1.hp.com/storage/arraywhitepapers.html IMPORTANT: XCS 10001000 requires more free space than previous XCS versions. Before upgrading, verify the amount of free space available. For more information, see the following advisory: http://saw.cce.hp.com/km/saw/view.do?docId=emr_na-c02931 184 2. Reduce array maintenance overhead by setting the disk replacement delay to 5 minutes (see Figure 25 (page 51) for an example). Reset the value to the default (60 seconds/1 minute) after the upgrade is complete. The 5 minute setting prevents triggering unwanted migration and reversion processes as disks are upgraded. 3. If you have not already done so, download the HP Hard Disk Drive Bundle zip file from the following website: http://www.hp.com/support/evadiskfirmware Store the file in a local directory. 4. 5. 6. 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.

56

Upgrading the Enterprise Virtual Array

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

Step 6. Upgrading the disk drive firmware

57

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. A status page opens, indicating the progress of the upgrade for each disk drive (Figure 32 (page 59)).

58

Upgrading the Enterprise Virtual Array

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. If you start another disk drive upgrade, the status box on the status window displays NO for the 10 drives that have been upgraded, and the remaining 17 drives are not shown as upgraded. Proceed to upgrade the remaining drives. 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.

Step 6. Upgrading the disk drive firmware

59

Figure 33 Code Load Disk Drives On Line Page 3 window

1 1. 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.2 or later, you can upgrade disks that contain Vraid0 virtual disk data by halting all host I/O to the Vraid0 virtual disks (other Vraid virtual disks can continue to service host I/O). When using HP P6000 Command View versions earlier than 9.2, you must either delete the Vraid0 virtual disks or ungroup the disks individually before upgrading firmware.

Step 7. Entering array passwords

Estimated time to complete: 1015 minutes NOTE: This step is required only if you use password protection on the array. Set the array password by selecting Configure Administrator login options in the P6000 Control Panel (EVA4400) or using the OCP (EVA6400/8400). Long passwords (up to 16 characters) are supported. The password must meet the following requirements: Must be 8 to 16 characters Can include uppercase or lowercase letters Can include the numbers 0 to 9 Can include the following characters: ! # $ % & ( ) * + , - . / : ; < = > ? @ [ ] ^ _ ` { | } Cannot include the following characters: space ~ \

60

Upgrading the Enterprise Virtual Array

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. 4. Click Manage storage system password access. The Storage System Password Access window opens. Click Enable. The Enable Password Access to a Storage System window opens (Figure 34 (page 61)). Figure 34 Enable Password Access to an array window

5. 6. 7. 8.

Select the World Wide Node Name of the array for which you want to enable password access. Enter the password (exactly 8 or up to 16 characters, depending on the Password Mode) in the Enter password and Confirm password boxes. Click Enable Password. A message box opens. Click OK. HP P6000 Command View enables password access to the array.

Step 8. Resuming array operation

Estimated time to complete: Varies depending on your configuration. After the controller software and disk drive firmware have been upgraded successfully, return the array to normal operation: 1. Using HP P6000 Command View, check the overall status of the array to ensure that there are no problems. For instructions, see Step 1. Checking the health of the Enterprise Virtual Array (page 41).

Step 8. Resuming array operation

61

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. 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. If you are running Remote Support software, enable it as follows: a. Save and then clear the application event log file. b. On the management server, open a command window. c. Enter the following command to restart Remote Support software: C:\>net start desta_service d. Enter exit.

3.

4. 5.

6.

Update the MIB file after the upgrade to ensure that SNMP notifications are captured correctly. See Retrieving the Management Information Base in the HP P6000 Command View User Guide for instructions.

62

Upgrading the Enterprise Virtual Array

Task checklist
Use the following checklist to track your progress and mark when a task is completed. Table 10 Upgrade task checklist
Task Step 1. Checking the health of the Enterprise Virtual Array (page 41) Time required: 2030 minutes Step 2. Configure User-Initiated Service Mode (UISM) (page 43) Time required: 1015 minutes Step 3. Disabling array passwords (page 44) Time required: 1015 minutes Step 4. Halting all host access to the array for an offline upgrade (page 44) Time required: Varies by host; must be performed for each host accessing the array Step 5. Upgrading the controller software (page 45) Time required: 2530 minutes Step 6. Upgrading the disk drive firmware (page 55) Time required: Varies depending on the number of disk drives to be upgraded. It can take from 30 seconds to 3.5 minutes per drive. Step 7. Entering array passwords (page 60) Time required: 1015 minutes Step 8. Resuming array operation (page 61) Time required: Varies with your configuration. Task complete

Task checklist

63

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. To determine if there are problems with HP P6000 Command View, answer the following questions: Has an HBA failed? Has a controller failed? Have you set or reset the array password?

HP P6000 Command View with a management server

To isolate problems that can occur when using HP P6000 Command View with a management server: 1. To ensure that the version of HP P6000 Command View you are using is compatible with the XCS version, see the HP P6000 Command View interoperability support table in the HP P6000 Enterprise Virtual Array Compatibility Reference. See Reference documentation (page 6) for the link to this document. 2. Ensure that the server and the array are logged in to the fabric. 3. Use one of the following utilities to check the SAN Fibre Channel switch: 4. HBAnywhere (Emulex) SanSurfer (QLogic)

Clear the browser cache: a. On the General tab, under Temporary Internet files, click Settings. b. Click Every visit to the page under Check for newer versions of stored pages. c. On the General tab, under Temporary Internet files: i. Click Delete Cookies. ii. Click Delete Files. d. On the General Tab, under History, click Clear History. Ensure that the following folder exists:
<install_location>:\Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\

5.

For the Japanese version, check for the subfolder

<install_location>:\Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV\gui\pages\ja

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. Cause HP P6000 Command View cannot build the view of the array.

64

Troubleshooting

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. HTTP errors, including 404 and 503, originate from the web server or HTTP server. Even when HP P6000 Command View cannot respond, the web server continues to respond to HTTP requests from a browser. During normal interaction between HP P6000 Command View and the web server: 1. A browser requests an HP P6000 Command View page. 2. The web server passes the request for the page to HP P6000 Command View. 3. HP P6000 Command View sends the page to the web server. 4. The web server sends the page to the browser. HTTP errors 404 and 503 indicate a problem with this interaction. Table 1 1 (page 65) lists possible causes of these errors and corrective actions. Resolution Table 1 1 Possible causes and corrective actions for HTTP errors 404 and 503
Possible cause Corrective action

404 error: HP P6000 Command View may be initializing Retry the request by clicking the Refresh/Reload when a browser makes a request. The web server returns button on the browser. a 404 (Page Not Found) error because it cannot access the page. 404 error: A .frm (HTML) file may be missing in the HP Reinstall HP P6000 Command View. P6000 Command View directory structure. This can occur if the files were changed or if HP P6000 Command View was not installed successfully. 503 error: HP P6000 Command View may be down when Retry the request when HP P6000 Command View a browser makes a request. The web server returns a 503 is up. (No Service) error because it cannot access the page. Browser timeout: The server may be down or the web server may be unavailable when a browser makes a request to HP P6000 Command View. In this case, the browser will time out internally. Retry the request when the server and HP P6000 Command View are up.

Unknown storage system

Symptom HP P6000 Command View reports an unknown storage system error for an array that should be displayed.

HP P6000 Command View

65

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

Resolution Unknown storage system cause 1 If the array has a heavy I/O load, the HBA in the management server may time out commands to the controllers. If this occurs, the array appears in the Unknown state. Corrective action This scenario should correct itself in less than one minute. Alternatively, you can perform a Rediscover operation to initiate new commands to the controller. Unknown storage system cause 2 HP P6000 Command View can only manage controllers that are running supported XCS versions. Corrective action Ensure that you are running the HP P6000 Command View version that is compatible with XCS 10001000. See the HP P6000 Command View interoperability support table in the HP P6000 Enterprise Virtual Array Compatibility Reference to determine which version of HP P6000 Command View you should be running. Then, upgrade HP P6000 Command View to a compatible version. See Reference documentation (page 6) for the link to this document.

No storage systems found

Symptom HP P6000 Command View does not display any arrays, even though they are in the fabric. Cause Several conditions can cause this symptom. Table 12 (page 66) lists some possible causes and corrective actions. Resolution Table 12 Possible causes and corrective actions when no array is found
Possible cause The management server may not be able to communicate with either controller. Corrective action 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 communication with the server.

When HP P6000 Command View is first starting up, Enter the correct password in HP P6000 Command View or a password may be enabled on the controllers, but a disable the password on the controller. password has not been entered in HP P6000 Command View. The switches may not be zoned correctly, making an array invisible to HP P6000 Command View. Verify that the switches are zoned correctly.

HP P6000 Command View may have been restarted 1. Verify that the controllers are up and running properly. while there was a communication failure between HP 2. Check the cable connections between the management P6000 Command View and the controllers. When the server and the switch.

66

Troubleshooting

Table 12 Possible causes and corrective actions when no array is found (continued)
Possible cause restart is complete, the array that lost communication will not be visible. 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. This can also occur if back-end problems are preventing access to the quorum drives. Once communication is restored, you can re-enter the WWID and the checksum. Corrective action 3. Verify that switch zoning is correct. 4. Click Discover. Enter the WWID of your system.

Creating disk groups with double protection level

When creating a disk group with double protection level on an array running XCS 10001000, a minimum of 10 disks is required on the array. If the disk group contains fewer than 10 drives and double protection is requested, only single protection level will be used. If all the physical disks in the disk group are of the same capacity, double protection level is achieved by reserving capacity equal to more than four times the capacity of a single disk. If the physical disks in the disk group are of different capacities, double protection is achieved by reserving capacity equal to more than the sum of the four highest capacity disks.

Security credentials configuration

The following Windows-based security groups are required on the management server: HP Storage Admins This security group is required on the management server to enable access to all features of HP P6000 Command View and must have at least one member (user account). Members have view and manage capabilities. NOTE: Group names are case sensitive.

HP Storage UsersMembers have view capability only. This security group is required only when a group with extremely limited use of HP P6000 Command View is needed.

Access control
Access authentication proceeds as follows: 1. The user's security group is checked to control access to various functions and web pages used with HP P6000 Command View. 2. If the user belongs to the HP Storage Admins group, access is granted. 3. If the user belongs to the HP Storage Users group and the web page allows access to users with the View HP Storage privilege, access is granted. 4. If the user belongs to the HP Storage Users group and the web page does not allow access to users with the View HP Storage privilege, access is denied.

Upgrading the disk drive firmware

Table 13 (page 68) lists errors you may encounter when upgrading the disk drive firmware, and provides workarounds.

Upgrading the disk drive firmware

67

Table 13 Disk drive firmware upgrade errors and workarounds

Error Drive code load - Failed to write firmware to drive buffer Workaround 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. it is part of a group Drive code load - The disk group containing the physical store has background reconstructing or reverting in progress Reduce the I/O using the I/O analysis (see Analyzing array I/O using HP Command View EVAPerf (page 22)) for the online disk drive firmware upgrade, and restart the upgrade.

Drive code load - Unable to determine the condition of the Check the drive properties in HP P6000 Command View volume for problems. Resolve the problem and restart the disk drive firmware upgrade. Media Not Available This error message may appear if the code load occurs when the array is experiencing a heavy I/O load. Restart the disk drive firmware upgrade.

Drive code load - Unable to determine the condition of the Check the drive properties in HP P6000 Command View physical store for problems. Resolve the drive problems and restart the disk drive firmware upgrade. Unable to process command at this time. Retry the command or check all connections Failed - Successful Status Object not found in View Check for any connection issues between HP P6000 Command View and the array, and restart the disk drive firmware upgrade. Restart the disk drive firmware upgrade. Check for any connection issues between HP P6000 Command View and the array, and restart the disk drive firmware upgrade. Restart the disk drive firmware upgrade. Check the drive properties in HP P6000 Command View for problems. Resolve the problem and restart the disk drive firmware upgrade. Restart HP P6000 Command View and retry the disk drive firmware upgrade.

Drive code load - The Storage Cell is in device discovery, and the requested operation cannot be served Invalid Target Handle

Not a supported version

The disk cannot be code loaded because disk is part of a Remove disks that contain RAID0 (Vraid0) data from the RAID0 group group and restart the disk drive firmware upgrade.

Selecting an array
When selecting an array, ensure that the status icon is a green cluster symbol indicating good health (Figure 35 (page 68)). Figure 35 Status icon for an array in good health

68

Troubleshooting

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. The following website provides access to information for troubleshooting problems with HP P6000 Continuous Access, including disabling DR groups when necessary: 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 P6000 Continuous Access Software.

Downloading the controller software file

If you cannot download the controller software file from Software Depot, right-click the link and save it to your desktop. Then, double-click the saved file, which opens a window with the link to the file. Click the link and save the file to a directory. Create your own DVD from the downloaded file. NOTE: The XCS image filename has an extension of .sss. The file name contains the controller model and the XCS version. For example, 300_10001000.SSS is the name of the XCS 10001000 file for the HSV300 and HSV300S controllers. See Table 9 (page 48) for details.

Invalid firmware image file (Status code 21006)

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

Disabling DR group failsafe mode

69

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. This can be caused by a problem in the XCS controller software image file or by selecting the wrong image file (Figure 38 (page 70)). If this occurs, do the following: 1. Click OK to return to the Initialized Storage System Properties window. 2. Click Code load to restart the controller software upgrade. 3. Select the correct image file and continue the process. If the process fails again with the same message, download the image file again and repeat the process. Verify that the correct name was selected. For the list of current image files, see Table 9 (page 48). Figure 38 Bad image header (Status code 65)

Offline array
The controller software upgrade should take approximately 10 minutes to complete. If the array does not come back online within 10 minutes, check the following: Determine if the problem is with HP P6000 Command View by answering the basic questions at the start of this chapter. Check any Insight Remote Support messages: Check the array event logs: 1. Open HP P6000 Command View in your browser. 2. Select the array whose logs you want to view. 3. Click View Events to view the event logs that can be displayed.

If these actions do not resolve the problem, contact your HP-authorized service representative for assistance.

Multiple resynchronizations
During the upgrade process, both controllers perform a resynchronization simultaneously. This invokes a fast restart of the controllers, bypassing execution of lengthy hardware diagnostics. The fast restart allows controllers to complete the resynchronization sequence before the host timeout period elapses and the host becomes aware that the array is unavailable.

70

Troubleshooting

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 P6000 Control Panel Disk group hardware problem on a Vraid1 virtual disk, or attempted reconnection of a disk when there is a disk group hardware problem Bad Block Replacement (BBR) performed on a disk

Every effort should be made to ensure that these events do not occur during the upgrade process. If controller termination occurs due to multiple resynchronizations, contact your HP-authorized service representative for assistance.

Multiple resynchronizations

71

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 Detailed questions

Subscription service
HP recommends that you register your product at the Subscriber's choice for business website: http://www.hp.com/go/wwalerts After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources.

Documentation feedback
HP welcomes your feedback. To make comments and suggestions about product documentation, please send a message to [email protected]. All submissions become the property of HP.

Related information
Documents
For documents referenced in this guide, see the Manuals page on the Business Support Center website: http://www.hp.com/support/manuals In the Storage section, click Disk Storage Systems or Storage Software, and then select your product.

Websites
HP: http://www.hp.com HP Storage: http://www.hp.com/go/storage HP Partner Locator: http://www.hp.com/service_locator HP Software Downloads: http://www.hp.com/support/downloads
72 Support and other resources

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 Medium blue text: Table 14 (page 73) Medium blue, underlined text: http:// www.hp.com Bold text Element Cross-reference links and email addresses Website addresses Keys that are pressed Text typed into a GUI element, such as into a box GUI elements that are clicked or selected, such as menu and list items, buttons, and check boxes Italic text Monospace text Text emphasis File and directory names System output Code Commands, their arguments, and argument values Monospace, italic text Code variables Command variables Monospace, bold text . . . WARNING! CAUTION: An alert that calls attention to important information that if not understood or followed can result in personal injury. An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information. An alert that calls attention to additional or supplementary information. An alert that calls attention to helpful hints and shortcuts. Emphasized monospace text Indication that the example continues.

IMPORTANT: NOTE: TIP:

Typographic conventions

73

Index
A
advisory free space, 56 agent options using, 44 analyzing array I/O, 22 array checking for errors, 10, 41 passwords, 61 XP P9000, 30

F
fabric name, 13 failed hardware components, 10 firmware upgrading, 37, 56, 60 free space, 56

H
hardware check, 10 errors, 10 hardware errors, 41 health check, 10 help obtaining, 72 host I/O timeouts AIX, 27 HP-UX, 26 IBM AIX, 27 Linux, 27 Mac OS X, 28 managing, 26 OpenVMS, 29 Red Hat, 27 Solaris, 29 SUSE, 27 VMware, 29 Xen Citrix, 29 HP Command View installing, 31 HP P6000 Command View checking hardware, 10, 41 disabling passwords, 44 online help, 10 web server interaction, 65 HP technical support, 72

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 configuration SAN, 12 configuration data collecting, 12 controller events checking log, 42 Controller Events page, 35, 42 corrective action codes, 36, 43 critical event check, 42 events, 36

I
I/O module resetting, 54 I/O timeout external device, 30 Insight Remote Support, 34 installation typical, 31 Invalid firmware image file error, 69 IOPS, 24

D
data backup, 30 Device-Mapper Multipath, 27 documentation providing feedback, 72

E
Emulex, 27 EVAPerf, 22 external device I/O timeout, 30

J
JRE recommended version, 35

K
kits required, 6, 7

74

Index

software, 6, 7

L
limits throughput, 24 LUNs Vraid0, 30

SPOCK website, 1 1 status code 21006, 69 65, 70 storage system passwords, 61 System Option Mode 725, 30

M
management module, 32 software, 7 management server interaction with HP P6000 Command View, 65

T
technical support HP, 72 throughput limits, 24 time estimate adding passwords, 60 clearing passwords, 44 disabling password access, 44

O
OCP adding passwords, 60 offline upgrade, 5 online upgrade, 5 configuration evaluation, 19 considerations, 20 managing host I/O timeouts, 26 selecting when to do, 22 success factors, 19

U
UISM, 43 upgrade offline, 5 online, 5 shutdown, 5 upgrade preparation, 10, 41 upgrade task checklist, 63 upgrading firmware, 56, 60 Replication Solutions Manager, 35

P
P6000 Control Panel, 33 adding passwords, 60 clearing passwords, 44 P9000 XP array, 30 Password Mode, 61 password protection, 60 passwords array, 61 disabling, 44 Path Blockade Watch Timer, 30 pre-upgrade task checklist, 39

V
VCS minimum version before upgrade, 7 verifying software version, 9 View Events page, 35, 42 virtual disk activity viewing, 24 virtual mapped capacity, 20 Vraid0 LUNS, 30

Q
QLogic, 27

W
warning conditions, 10 Watch Timer Path Blockade, 30 web server, 65 WWN, 23, 39, 44 WWNN, 61

R
remote support, 34 resetting I/O module, 54 resynchronization, 5 RSM, 35

S
SAN configuration, 12 report, 15 Visibility, 12 selecting when to do online upgrade, 22 shutdown upgrade, 5 software, 7 kits, 6 space free, 56

X
XP array, 30

75