UpdatingFirmwareforDellEqualLogic PSSeriesStorageArrays

Copyright 2010 - 2012 Dell Inc. All rights reserved. Dell and EqualLogic are trademarks of Dell Inc. All trademarks and registered trademarks mentioned herein are the property of their respective owners. Information in this document is subject to change without notice. Reproduction in any manner whatsoever without written permission is strictly forbidden. Published: July 2012 Part Number: 110-0025-EN-R22

Table of Contents
Preface 1 Overview 2 Planning and Prerequisites
Review the Documentation SAN Planning Planning for Restart and Minimizing Host Disruption Host Software Requirements Browser Requirements Working With Multi-Member Groups Supported Upgrade Paths iv 1 2 2 2 3 3 4 4 5 8 8 8 8 9 9 9 9 10 10 11 12 15 15 15 16 18 19 20 20 23 23 25 25 26 26 27

3 Known Issues and Considerations

Windows Server 2008 R2-based Failover Cluster Collection Replications Should be Paused Before Updating Firmware GUI Firmware Update Does Not Work in an Environment Running Only IPV6 Firmware Downgrades Not Allowed in Some Cases Firmware Upgrade Wizard Does Not Distinguish Between Failed and Missing Control Modules Upgrading Firmware Not Allowed from GUI when FTP is Disabled Limits for Upgraded Release Not Available Until Disallow Downgrade Set

4 Updating the Firmware

Downloading Firmware Update Kit Updating the Firmware Using the GUI Updating the Firmware Using the CLI

5 Installing and Using Localized Versions of the GUI

Language File Considerations Available Languages Overview of Language Installation and Use Specifying Language Setting for System and Browser Specifying the System Language in Windows Specifying the Browser Language in Internet Explorer 8 Clearing the Java Cache and Browser Cache Changing to English GUI Using Localized Online Help

6 CLI Output Examples

Output Displayed When Firmware is Copied to an Array Using FTP Output Displayed When Firmware is Copied to an Array Using SCP Output Displayed When Update Command is Entered Output Displayed When Firmware Version is Confirmed

iii

Preface
Dell EqualLogic PS Series arrays optimize resources by automating capacity, performance, and network load balancing. Additionally, PS Series arrays offer all-inclusive array management software and firmware updates. Dell EqualLogic FS Series appliances, combined with PS Series arrays, offer a high-performance, highavailability, scalable NAS solution.

Audience
The information in this guide is intended for administrators who are responsible for updating firmware on the PS Series arrays.

Related Documentation
For detailed information about FS Series appliances, PS Series arrays, groups, volumes, array software, and host software, log in to the Documentation page at the customer support site.

Dell Online Services

You can learn about Dell products and services using this procedure: 1. Visit www.dell.com or the URL specified in any Dell product information. 2. Use the locale menu or click on the link that specifies your country or region.

Dell EqualLogic Storage Solutions

To learn more about Dell EqualLogic products and new releases being planned, visit Dell EqualLogic TechCenter. Here you can also see articles, demos, online discussions, and more details about the benefits of our product family.

Technical Support and Customer Service

Dell support service is available to answer your questions about FS Series arrays.

Contacting Dell
If you are a customer in the United States or Canada in need of technical support, call 1-800-945-3355. If you are outside of the United States or Canada, visit Dell EqualLogic Product Support. If you have an Express Service Code, have it ready. The code helps the Dell automated support telephone system direct your call more efficiently.

iv

Updating Firmware

Preface

1 Overview
This document describes the procedure for updating the firmware on Dell EqualLogic PS Series storage arrays.
Note: If you are applying a PS Series firmware patch, follow the instructions in the patch releases upgrade

document. Download patch releases from the Dell EqualLogic customer support website, located at support.dell.com/equallogic. A PS Series storage array includes single or dual control modules, each with a compact flash card or microSD card containing the PS Series firmware. To take advantage of new product features, enhancements, and bug fixes, use the latest PS Series storage array firmware. For instructions on updating Dell EqualLogic FS Series firmware for NAS controllers, see Updating Dell EqualLogic FS Series Firmware for NAS Controllers.

2 Planning and Prerequisites

Before performing a firmware update, review the information in this section.

Review the Documentation

Review the following documentation before updating the firmware on your PS Series storage arrays. These documents are available from the Dell EqualLogic support site at support.dell.com/equallogic. Release Notes and Fix List for the firmware version to which you are updating Release Notes for any FS Series appliances you are operating Current revision of Dell EqualLogic PS Series Storage Arrays iSCSI Initiators and Operating System Considerations

SAN Planning
In a SAN, hardware components (including arrays, switches, OS drivers, and NICs) interact with each other and with the operating system and applications. A disruption in the availability of one SAN component can have an impact on the entire infrastructure, leading to unplanned downtime. Before updating a SAN component, you must understand the impact of the update on the infrastructure and plan the update process carefully to avoid unplanned downtime. After updating any SAN component, test it to make sure it is functioning properly. Dell recommends that you perform firmware updates during scheduled maintenance periods to avoid disruption of service to the applications and servers that the storage group supports. If possible, perform the update after a backup. In rare cases, firmware updates might fail if attempted while the system is under heavy use. Dell also recommends that you keep initiators and drivers up-to-date. The Dell EqualLogic support website lists supported initiators. Apply the recommended modifications to your operating system and iSCSI initiators specified in Dell EqualLogic PS Series Storage Arrays iSCSI Initiator and Operating System Considerations. Consider the following when upgrading infrastructure: Does the upgrade procedure require a service disruption for the device you are upgrading? If so, what is the duration?

Updating Firmware

2 Planning and Prerequisites

Can the existing redundancy at the server, network, and storage level allow service to continue during the upgrade, despite the service disruption? Are the iSCSI initiators accessing group volumes configured to automatically retry during service disruptions? Will applications be able to resume processing without I/O errors, failures, or server reboots?

Some typical, but not universal, device timing issues are as follows: Network switches can take from 30 seconds to several minutes to reboot after a power cycle or firmware upgrade. Average storage array restart times range from 15 seconds to several minutes, depending on your specific configuration. For cluster configurations, Dell recommends that you place the cluster in maintenance mode during SAN infrastructure upgrades. After updating a SAN component (for example, an array or a switch), allow the SAN to stabilize before updating another component. Use the Group Manager GUI or CLI to make sure that all members and volumes are online. Make sure that iSCSI initiators reconnect to volumes, if applicable. Then, continue with the next step in the update process. Initiators must support error recovery and retry times of one minute or more to allow servers and applications to avoid disruptions that may occur during the upgrade.

Planning for Restart and Minimizing Host Disruption

The firmware update procedure requires an array restart. During the restart, volumes with data are temporarily unavailable. To make your infrastructure more tolerant of the array restart disruption, follow the guidelines in Dell EqualLogic PS Series Storage Arrays iSCSI Initiator and Operating System Considerations. This document provides examples of operating system and iSCSI initiator configurations that can handle an array restart without disruption. In some cases, you may need to modify your operating system settings, including initiator timeout settings, or modify your infrastructure settings, including enabling rapid spanning tree on end node ports. Make sure that applications using iSCSI volumes can support the restart. In all cases, test changes first in a nonproduction environment. If you do not have one of the configurations identified in Dell EqualLogic PS Series Storage Arrays iSCSI Initiator and Operating System Consideration, or if you are not sure of your applications ability to tolerate a restart, plan for downtime when updating firmware. As part of the downtime, you might have to shut down hosts accessing the group before and during the update procedure.

Host Software Requirements

The Dell EqualLogic customer support website at https://support.equallogic.com/compatibility lists the versions of Host Integration Tools and SAN HeadQuarters recommended for each firmware release.

Updating Firmware

2 Planning and Prerequisites

In some cases, you may be required to update your Host Integration Tools before updating the firmware.
Note: The minimum supported host software versions might not support all of the features provided by the

firmware version.

Browser Requirements
See the Release Notes for detailed browser support information.

Working With Multi-Member Groups

A PS Series group includes one or more PS Series storage arrays configured as group members. Dell recommends that all PS Series group members run the same version of the storage array firmware; in multiversion configurations, the group can support only functionality common to all versions.

Adding a New Array to an Existing Group

If you are adding a new array to an existing group, consider updating the group to the latest firmware before adding the new member to the group. In general, mixed firmware groups are supported only during the period of time during which you are updating all members. See Supported Upgrade Paths on page 5 for information about specific firmware releases.

Updating Across Multiple Releases

If you must update to an interim version, update all the members to the interim version, then update all the members to the final version. Between updating group members, wait for the SAN to stabilize before continuing with the update. Use the Group Manager GUI or CLI to make sure that all members and volumes are online. Also, make sure that iSCSI initiators reconnect to volumes (if applicable).

Updating Members Using Maintenance Pools

To avoid the brief interruption in I/O caused by the controller failover during the update process, you can perform firmware updates in multi-member groups by moving members into separate pools designated for maintenance purposes for the duration of the update. When you move a member from one pool to another, the volumes residing on it are moved to other members in the pool and their initiator connections are automatically redirected with no access disruption. To perform this type of update, first create a separate pool designated for maintenance purposes. Then, move a member into that pool and update its firmware. After the firmware update completes and the member restarts, you can move the member from the maintenance pool back to the pool in which it previously resided. Repeat the process, one member at a time, until the firmware for all members in the group is updated. After the update is complete, you can delete the empty maintenance pool.

Updating Firmware

2 Planning and Prerequisites

Alternately, you may also remove the member from the group entirely, update its firmware, and then add it back to the group, repeating the process for each group member.
Caution: When you move a member into a maintenance pool or remove a member from a group, it might take a

very long time for all the volumes on the member to move to other members in the pool. It is very important to wait until all volumes have been moved before updating the member. You can monitor the status of the move from the Status page in the Group Manager GUI. To perform updates using these techniques, there must be sufficient capacity on the other member(s) to temporarily hold the volumes of the member being updated. Also, changing members pool assignments or removing them from the group can be a long operation, depending on the amount of data the group must move to remaining pool members. See the Dell EqualLogic Group Manager Administrator's Manual and online help for information about changing a members pool membership or removing it from the group.

Supported Upgrade Paths

When updating array firmware, you must follow the supported upgrade path, as shown in Table 1 The first column lists starting firmware versions, and the second column lists the versions to which they can be updated.
Note: The notation used in the table refers to all releases of a given firmware revision. For example, 4.3.x

refers to versions 4.3.2, 4.3.4, 4.3.5, 4.3.6, 4.3.7, and 4.3.8, as well as all V4.3 patch releases.

Updating Firmware

2 Planning and Prerequisites

Table 1: Supported Firmware Upgrade Paths

Starting Version Supported Upgrades

5.2.x 5.1.x

5.0.x (excluding 5.0.0 and 5.0.1) 5.0.0 and 5.0.1 4.3.x

4.2.x

4.1.x

4.0.x 3.3.x

3.2.x

3.1.x

3.0.x

Later 5.2.x releases 6.0.x Later 5.1.x releases 5.2.x and 6.0.x Later V5.0.x releases 5.1.x 5.2.x 5.0.2 Later 4.3.x releases 5.0.x (excluding 5.0.0 and 5.0.1) Later 4.2.x releases 4.3.x 5.0.x (excluding 5.0.0 and 5.0.1) Later 4.1.x releases 4.2.x 4.3.x Later 4.0.x releases 4.1.x Later 3.3.x releases 4.0.x Later 3.2.x releases 3.3.x 4.0.x Later 3.1.x releases 3.2.x 3.3.x Later 3.0.x releases 3.1 .x

General Rules
Unless otherwise indicated in Table 1, or under Version-Specific Constraints on page 7, the following rules apply when upgrading array firmware: You can upgrade firmware to a later release within its own version. For example, you can upgrade version 5.0.2 to any subsequent version 5.0.X release. You can upgrade firmware to the next version. For example, you can upgrade any version 4.2.x release to a version 4.3.x release.

Updating Firmware

2 Planning and Prerequisites

If you are running older firmware versions, or upgrading across multiple releases, you may have to upgrade to one or more interim versions before upgrading to the latest firmware. For example, to upgrade a group from version 3.3.x to version 4.3.x, you must first upgrade to version 4.0.x, then to version 4.1.x, and finally to version 4.3.x.

Version-Specific Constraints
The following constraints apply when upgrading from specific firmware versions: For arrays running a PS Series firmware version prior to 2.2.3, you must use the restart command to restart the array before copying the update kit to the array. If you are running a firmware version earlier than version 3.0, contact your array support provider for supported upgrade paths. After updating a group to PS Series firmware version 4.0 or later, do not add new members running an earlier firmware release. You must update the member first before adding it to the group. Beginning with version 4.1.3, you can use the GUI to update the firmware. For earlier versions, you must use the CLI. When updating from version 4.1.x to version 4.x.x using the GUI, the GUI may return to the Update menu without restarting the array, making it look as though the update did not occur. However, the update has completed successfully; manually restarting the array through the GUI or the CLI will correct the issue. When updating version 4.x firmware to a higher version, the update procedure restarts the controllers individually, with the resumption of service occurring in approximately 15-30 seconds. In versions 5.0 and 6.0, firmware downgrades are not allowed. If you are upgrading from version 5.0.0 or version 5.0.1 to any subsequent version, you must first upgrade to version 5.0.2, following the instructions in the Release Notes for version 5.0.2 of the firmware. Do not follow the procedure listed under Updating the Firmware on page 10 of this document. If you use (or have previously used) RADIUS authentication for administrator accounts on groups running version 5.1.0 firmware, you must delete any duplicate administrator accounts prior to upgrading the firmware. Duplicate accounts include accounts that differ from one another only by capitalization of letters. You can delete the duplicate accounts using the Group Configuration Summary in the Group Manager GUI. If you are upgrading to version 5.1.0 or later of the PS Series Firmware and you plan to use Data Center Bridging (DCB) with your SAN, verify that all switches used in your SAN environment are running firmware versions that support DCB. Refer to your switch firmware documentation for more information.

3 Known Issues and Considerations

The following issues apply when updating firmware.

Windows Server 2008 R2-based Failover Cluster

If you are using Host Integration Tools (HIT) with Microsoft Windows Server 2008 R2-based failover clustering and are planning to upgrade to PS Series Array firmware version 5.2.0 or higher, Dell recommends that you upgrade the HIT on all cluster nodes to HIT V3.5.1 or later, before upgrading the firmware.

Collection Replications Should be Paused Before Updating Firmware

When planning an update, identify a time period when replication is not occurring. Check all the collection replication schedules. Dell recommends that you do not update a PS Series group member while collection replication outbound from the group is in progress; otherwise, the collection replication operation may fail or appear to hang. In addition, make sure that collection replication does not begin while you are upgrading member firmware. To make sure that no collection replication occurs during an update, disable all the collection replication schedules (if the group is running PS Series firmware version 3.0 or higher). Then, verify that all in-progress replication operations have completed before updating the member.

GUI Firmware Update Does Not Work in an Environment Running Only IPV6
The PS Series group must have IPV4 addresses to use the GUI update procedure. If your group uses an IPV6 address, follow the steps listed under Updating the Firmware Using the CLI on page 12.

Updating Firmware

3 Known Issues and Considerations

Firmware Downgrades Not Allowed in Some Cases

You cannot downgrade a group member to an earlier firmware version if: You have specifically disabled downgrades in the group, either through the GUI or by running the grpparams disallow-downgrade command. See the Dell EqualLogic Group Manager Administrator's Manual or the Dell EqualLogic Group Manager CLI Reference for more information. You have used any of the features of the currently installed firmware version that are not available in the previous version. The previous version does not support the control modules or other hardware in the group. You are running versions 5.0 or 6.0 of the firmware.

Firmware Upgrade Wizard Does Not Distinguish Between Failed and Missing Control Modules
The Firmware Upgrade Wizard in the Group Manager GUI displays the same error message, regardless of whether the array member being upgraded has a failed control module, or if it only has a single control module present: Single controller updates are not allowed from the GUI. Correct the problem or run the update from the CLI. In either case, the upgrade must be performed using the CLI.

Upgrading Firmware Not Allowed from GUI when FTP is Disabled

Firmware upgrades cannot be performed using the Group Manager GUI when FTP is disabled. To update array firmware for groups in which FTP has been disabled, use the CLI instead.

Limits for Upgraded Release Not Available Until Disallow Downgrade Set
When you upgrade your firmware from one version to another, the new limits for the new release might not take effect until you set the Disallow Downgrades function for the group. This issue does not apply to releases such as PS Series Firmware Version 6.0, in which the Disallow Downgrades option is set automatically when all members of the group are running that version.

4 Updating the Firmware

The following sections list the steps for downloading the firmware update kit and upgrading group member firmware using the Group Manager GUI or CLI. WARNING: If you are upgrading from version 5.0.0 or version 5.0.1, you must first upgrade to version 5.0.2. Follow the instructions in the Release Notes for version 5.0.2 of the firmware; do not follow the procedure listed below.

Downloading Firmware Update Kit

To download the update kit: 1. On a host that has the FTP utility available, use a Web browser to access the Dell EqualLogic customer support website (https://support.dell.com/equallogic). 2. Log in to your support account. If you do not have a support account, request an account from the Login page. 3. Click Support at the top of the page. 4. Click the Downloads tab, then click PS Series Firmware. 5. Select the PS Series firmware version you are downloading. 6. Download the firmware to a host that has network access to the array.
Note: Depending on the firmware version, the file may be 12 - 20 MB in size, and may be in .tgz, .tar, or

.zip format. 7. If you downloaded the firmware in a compressed format (.tar or .zip), decompress the file to a directory on the host.
Note: To use the Group Manager GUI in a language other than English, you must also download the appropriate

language kit from the support website. See Installing and Using Localized Versions of the GUI on page 15 for more information.

10

Updating Firmware

4 Updating the Firmware

Updating the Firmware Using the GUI

To perform a firmware update using the GUI, complete the following steps:
Note: You must perform the update from a host that has access to both control modules in the array and to the

switch ports to which they are connected. Use the ping command to test network connectivity to the IP address of Ethernet Port 0 on the array. 1. (Optional) Shut down the hosts accessing group volumes. See Planning for Restart and Minimizing Host Disruption on page 3 for more information. 2. On the computer where you downloaded the firmware kit, start the Group Manager GUI and log in using the grpadmin account.
Note: Only the grpadmin account can update group firmware.

3. Click Tools, then Update Firmware. 4. Enter the password for the default group administration account on the group (grpadmin), then click OK. 5. In the Select firmware update file dialog box, navigate to the location of the firmware kit you downloaded, then click Open. If this dialog box does not open automatically, click Browse in the Firmware Update dialog box to open it. The Firmware Update dialog box displays firmware for each group member. 6. Click Select all to update all members of the group, or click Update selected members to update only certain members of the group.
Note: In versions prior to 6.0, the Select all option is not available.

7. For each member you are updating, the Action column displays a different option depending on the firmware version you are applying and the version currently installed on the member: Update - Kit firmware is different from the member firmware. Upgrade - Kit firmware is a higher version than the member firmware. Downgrade - Kit firmware is a lower version than the member firmware. Reinstall - Kit firmware is the same version as the member firmware. Apply patch - Kit firmware is a patch.

8. Select an action to start the update process, which does the following: Step 1 of 3: FTP transfer (FTP the kit to the array) Step 2 of 3: Processing firmware update

Note: Step 3 of 3 involves restarting the member, as described in Step 9 of this procedure.

9. When the preparatory steps are complete, the Action column displays a link to restart the member. Click Restart and then click Yes in the confirmation dialog box.

11

Updating Firmware

4 Updating the Firmware

Notes: The firmware update is not complete until after the updated members restart.

You might briefly lose connectivity to the Group Manager GUI while the member restarts, but the connection will be restored automatically. During the interruption, the Firmware Update dialog box displays a status of Offline. In a single-member group, or on a member with a single control module, when the member goes offline during its update process, the status may not display correctly. A member that is offline cannot report its status. When the member restarts and is again online, the GUI displays the correct status. 10. Repeat Steps 8 and 9 for each additional group member.
Note: Between updating members, wait for the SAN to stabilize before continuing with the update. For

example, make sure all members and volumes are online. 11. When all group members have been updated to the same firmware version, click Close. 12. Close and restart the GUI after all members are updated to make sure the GUI is consistent with the new features in the updated firmware. 13. Verify the firmware update by selecting Members in the navigation panel, selecting the member(s) for which you have updated firmware, and then clicking the Controllers tab. 14. If you had shut down any hosts accessing group volumes prior to updating, restart them after the update is complete.

Updating the Firmware Using the CLI

This section provides the procedure to update the firmware using the CLI.

Constraints and Prerequisites for Using the CLI

If you are using a serial connection, make sure the connection has the following characteristics: 9600 baud One STOP bit No parity Eight data bits No hardware flow control On an array with dual control modules, the update command updates both control modules. On arrays with dual control modules, both of the control modules must be running the same firmware. If the FW Rev values for the two controllers do not match, contact Dell Technical Support. See CLI Output Examples on page 25 for examples of the screen output displayed during this process.

To update firmware using the CLI:

12

Updating Firmware

4 Updating the Firmware

1. (Optional) Shut down the hosts accessing group volumes. See Planning for Restart and Minimizing Host Disruption on page 3 for more information. 2. Use FTP to copy the firmware .tgz file to the array you are upgrading. See Output Displayed When Firmware is Copied to an Array Using FTP on page 25 for an example of screen output shown when you perform this step.
Note: From Linux systems, you can use the scp command to copy the firmware file to the array. If you want

to use scp, skip to Step3. a. Type ftp to open an FTP session. b. Type open, followed by the IP address of the array to establish a connection. For example: open 192.168.10.20 c. When prompted for an account and password, specify the grpadmin account and password. d. Enter binary to enable a binary mode transfer. e. Type put followed by the filename to transfer the file. For example: put kit_12345678.tgz. A Transfer complete status message appears, indicating that the file transfer was successful. Filenames are case-sensitive. f. Type close to close the session.

g. Type bye to close the FTP window. 3. If you did not use FTP to copy the file to the array as described in Step 4, use the Linux scp command to copy the firmware .tgz file to the array you are upgrading. (If you used FTP in Step 2 to copy the file, skip this step.) See Output Displayed When Firmware is Copied to an Array Using SCP on page 26 for an example of screen output shown when you perform this step. a. Type the scp command using the following syntax: $scp filename grpadmin@ ip_address_of_array: For example: $scp kit12345678.tgz grpadmin@192.168.10.20: Make sure to include the colon symbol (:) at the end of the IP address of the array.

13

Updating Firmware

4 Updating the Firmware

If you have not previously used SSH or scp with this group, the system displays a message indicating that the authenticity of the host cannot be established. If you receive this message, verify that you are connected to the correct system and enter yes. b. Enter the password for the grpadmin account. 4. Connect to the array using telnet, SSH, or a serial connection. Connect through an IP address assigned to a network interface on the array (for example, Ethernet Port 0). Do not connect to the group IP address. 5. Log in to the array using the grpadmin account. Only the grpadmin account can update group firmware. 6. At the Group Manager CLI prompt, enter the update command. See Output Displayed When Update Command is Entered on page 26 for sample screen output shown when you perform this step. 7. When prompted, enter Y to confirm that you want to update the arrays firmware. 8. Verify the firmware update by entering member select member_name show controllers, where member_ name is the name of the member you have updated. In the command output, note the SlotID value (which shows the control module) and FW Rev value (which shows the Firmware version). See Output Displayed When Firmware Version is Confirmed on page 27 for sample screen output shown when you perform this step. 9. Restart the array immediately after updating it. During the restart, iSCSI targets for the volumes with data on the array is unavailable.
Note: If you plan to shut down the array after a firmware update, Dell strongly recommends that you run the
restart command. down command.

After the group restarts, verify the group configuration before running the shut-

10. If necessary, restart the browser. After updating the firmware on a member, the link to reconnect to the Group Manager GUI might not respond when clicked. Restart the browser to log in to the GUI again. 11. If you shut down any hosts accessing group volumes prior to upgrading, restart them after the upgrade is complete. 12. Repeat this process for each additional group member.

14

5 Installing and Using Localized Versions of the GUI

Beginning with Version 6.0, you can install language files that allow you to interact with the Group Manager GUI in languages other than English. This section provides information about downloading, installing, and using the language files.

Language File Considerations

The language kit for a firmware release includes all the language files (one per language) available for use with that release. You must use the files in the language kit that corresponds to the firmware version currently running on your arrays. First install the firmware, and then install the corresponding language files you want to use. On earlier systems, the capacity of the boot flash device might limit the number of languages you can install, but installing a single language file is supported on all PS4000/5000/6000 series arrays. If you already have one or more language files installed and you are upgrading to a maintenance release (for example from version 6.0.x to version 6.0.y), do not reinstall the language files. The language files you are currently using are still available and valid after the upgrade. If you are upgrading to a new major release (for example, from version 6.0.x to version 6.1.x), your installed language file is not valid for the upgrade. New language kits are usually available within 90 days of the firmware release. If you can manage temporarily with English-only, you can upgrade the firmware and then install the corresponding language files when they are available.

Available Languages
The following language files are available as part of language kits on the Dell EqualLogic customer support website (https://support.dell.com/equallogic) with firmware releases beginning with version 6.0: French (fr) German (de) Japanese (ja) Korean (ko) Simplified Chinese (zh)

15

Updating Firmware

5 Installing and Using Localized Versions of the GUI

Spanish (es)

Overview of Language Installation and Use

To download, install, and use localized versions of the GUI: 1. Download the language kit from the Dell EqualLogic customer support website (https://support.dell.com/equallogic). 2. Install the file for the language(s) you want to use. 3. Specify the language settings for the operating system and browser. 4. Clear the Java cache and browser cache. Each of these steps is explained in the following sections.

Downloading the Language Kit and Localized Online Help

Download the language kit for a firmware release from the same place where you obtain the firmware: 1. On a host that has the FTP utility available, use a Web browser to access the Dell EqualLogic customer support website (https://support.dell.com/equallogic). 2. Log in to your support account. If you do not have a support account, request an account from the Login page. 3. Click Support at the top of the page. 4. Click the Downloads tab, then click PS Series Firmware. 5. Select the PS Series firmware version you are currently using. 6. Click on the link for the required languages. 7. Download the language kit .zip file. The files for all available languages are compressed into the same .zip file. 8. Unzip the files to a directory on the host.

Installing the Language Files

You can use the Group Manager GUI or CLI to install the required language kit, as described in the following sections.

16

Updating Firmware

5 Installing and Using Localized Versions of the GUI

Installing Language Files Using the GUI

1. On the computer where you have downloaded the language kit, start the Group Manager GUI and log in using the grpadmin account. 2. From the Group Manager GUI Tools menu, select Update firmware. 3. Enter the password for the default group administration account on the group (grpadmin), then click OK. 4. In the Select firmware update file dialog box, navigate to the location of the language files. 5. Select the language file that you downloaded for the language you want to use and click Open. 6. Click Select all to install the language on all members of the group, or click Update selected members to install the language on only certain members of the group. 7. Click Install under Action for the members where you want to install the language file. The language file is installed. 8. Repeat Steps 4 through 7 for each language file you want to install.
Note: There is no need to restart a member after performing an update to install a language file.

Installing the Language Files Using the CLI

The procedure for installing a language file using the Group Manager CLI is the same as the procedure for doing a firmware update.
Note: If you have more than one array in the group, you must install the language files on each array. Note: You can install more than one language file on each array, but you must install the files one at a time.

1. Use FTP to copy the firmware language file to the array. See Output Displayed When Firmware is Copied to an Array Using FTP on page 25 for an example of screen output shown when you perform this step.
Note: From Linux systems, you can use the scp command to copy the firmware file to the array. If you want

to use scp, skip to Step 2. a. Type ftp to open an FTP session. b. Type open, followed by the IP address of the array to open a connection. For example: open 192.168.10.20 c. When prompted for an account and password, specify the grpadmin account and password. d. Enter binary to enable a binary mode transfer. e. Type put followed by the filename to transfer the file. For example:

17

Updating Firmware

5 Installing and Using Localized Versions of the GUI

put kit_V6.0.0-T1_fr_1234567

A Transfer complete status message appears to indicate that the file transfer was successful. Filenames are case-sensitive. f. Type close to close the session.

g. Type bye to close the FTP window. 2. If you did not use FTP to copy the file to the array as described in Step 1, use the Linux scp command to copy the languare file to the array you are updating. See Output Displayed When Firmware is Copied to an Array Using SCP on page 26 for an example of screen output shown when you perform this step. a. Type the scp command using the following syntax: $scp filename grpadmin@ ip_address_of_array: For example: $scp kit_V6.0.0-T1_fr_1234567 grpadmin@192.168.10.20: Make sure to include the colon symbol (:) at the end of the IP address of the array. If you have not previously used SSH or scp with this group, the system displays a message indicating that the authenticity of the host cannot be established. If you receive this message, verify that you are connected to the correct system and enter yes. b. Enter the password for the grpadmin account. 3. Connect to the array using telnet, SSH, or a serial connection. Connect through an IP address assigned to a network interface on the array (for example, Ethernet Port 0). Do not connect to the group IP address. 4. Log in to the array using the grpadmin account. 5. At the Group Manager CLI prompt, enter the update command. See Output Displayed When Update Command is Entered on page 26 for sample screen output shown when you perform this step. 6. When prompted, enter Y to confirm that you want to update the firmware with the language file.
Note: There is no need to restart a member after performing an update to install a language file.

Specifying Language Setting for System and Browser

The language setting for your operating system must match the language setting for your browser. If the language settings do not match, the GUI displays English only.

18

Updating Firmware

5 Installing and Using Localized Versions of the GUI

The method for specifying the language settings varies based on the type of operating system and browser. This section describes how to specify the language settings for the Windows operating system and the Internet Explorer 8 browser.

Specifying the System Language in Windows

1. Open the Control Panel. 2. Select Region and Language. 3. From the dialog box, select the Formats tab. 4. From the Format drop-down box, shown in Figure 1, choose a setting for the language you want to use. 5. Click OK. Figure 1: Region and Language Formats Selection Box

19

Updating Firmware

5 Installing and Using Localized Versions of the GUI

Specifying the Browser Language in Internet Explorer 8

1. From the Tools menu, select Internet Options. 2. Click Languages at the bottom of the General tab. The currently selected language is displayed in the list box, as shown in Figure 2. 3. If the language you want to use is not displayed, click Add and then select the language you want to test. 4. Use the Move up button to move your selected language up until it is the first language in the list box. The first language in the list box is the configured language for the browser. 5. Click OK. Figure 2: Language Preference Screen

Clearing the Java Cache and Browser Cache For best results, after changing the language settings, clear the Java cache and the browser's cache on your system.
1. Log out and close any instances of the Group Manager GUI that are running on your system.

20

Updating Firmware

5 Installing and Using Localized Versions of the GUI

2. Clear the system's Java cache: a. Open the Control Panel. b. Select Java. c. Under Temporary Internet files, click Settings. The Temporary Files Settings screen (Figure 3) is displayed. d. Click Delete Files. e. Click OK until the Control Panel screens exit. Figure 3: Temporary Files Settings Screen

21

Updating Firmware

5 Installing and Using Localized Versions of the GUI

3. Clear your browser's cache: a. From the Tools menu, select Internet Options. b. In the Browsing History section, click Delete. The Delete Browsing History screen (Figure 4) is displayed. c. Make sure the Preserve Favorites website data is unchecked. d. Make sure the Temporary Internet files, Cookies, and History boxes are checked . e. Click Delete. f. Click OK. Figure 4: Delete Browsing History Screen

4. Log in to the Group Manager GUI.

22

Updating Firmware

5 Installing and Using Localized Versions of the GUI

Changing to English GUI

If you have installed one or more language kits, but would like to see the English language version of the Group Manager GUI, log in to the GUI using the Group Manager IP address with the string /english.html at the end, as in the following example:
http://10.127.1.1/english.html

This starts a completely new GUI session in English.

Using Localized Online Help

To use a localized version of the online help, follow the instructions in the readme file posted with the language files.

23

Updating Firmware

5 Installing and Using Localized Versions of the GUI

24

6 CLI Output Examples

The following sections provide examples of screen output displayed when you upgrade the firmware as described under Updating the Firmware Using the CLI on page 12

Output Displayed When Firmware is Copied to an Array Using FTP

The following example uses FTP to copy a firmware update kit named kit_12345678.tgz from a host to an array with the IP address 192.168.1.53.
Note: This is the output displayed during step 2 of the procedure in Updating the Firmware Using the CLI on

page 12
$ ftp ftp> open 192.168.1.53 Connected to psa1.site.com. 220 192.168.1.53 FTP server ready. Name: grpadmin 331 Password required for grpadmin. Password: xxxxxxx 230 User grpadmin logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> binary 200 Type set to I ftp> put kit_12345678.tgz local: kit_1234567.tgz remote: kit_1234567.tgz 229 Entering Extended Passive Mode (|||65534|) 150 Opening BINARY mode data connection for 'kit_12345678.tgz'. 100%|***********************| 13191 KB 81.26 KB/s 00:00 ETA 226 Transfer complete. 13508472 bytes sent in 02:42 (81.06 KB/s) ftp> close 221- Data traffic for this session was 13508472 bytes in 1 file. Total traffic for this session was 13509009 bytes in 1 transfer. 221 Thank you for using the FTP service on 192.168.1.53. ftp> bye

25

Updating Firmware

6 CLI Output Examples

Output Displayed When Firmware is Copied to an Array Using SCP

The following example uses the Linux scp command to copy a firmware update kit named kit_12345678.tgz from a host to an array with the IP address 192.168.1.53.
Note: This is the output shown during step 3 in the procedure in Updating the Firmware Using the CLI on page

12
$ scp kit_12345678.tgz grpadmin@192.168.1.53: The authenticity of host '192.168.1.53' can't be established. DSA key fingerprint is 93:30:25:e1:7f:f8:ce:78:06:a6:97:67:94:70:aa:e6. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.1.531' (DSA) to the list of known hosts. grpadmin@192.168.1.53's password: xxxxxxx kit_12345678.tgz 100% 26MB 4.4MB/s 00:06

Output Displayed When Update Command is Entered

The following example displays the screen output when you enter the update command. After you enter the command, the system prompts for confirmation.
Note: This is the output shown after you enter the command shown at step 6 in the procedure in Updating the

Firmware Using the CLI on page 12.

> update Updating from kit file "kit_V6.0.0-R242280_4075033671.tgz" This command will update the firmware on the array's flash card memory using the update kit file that was copied to the array. If you choose to proceed, you will be shown the current firmware version and the version to which you will update. You will then be given the choice to proceed again. Do you want to proceed (y/n) [y]: y Verifying kit integrity. Active and secondary controllers detected. Currently running version is: Storage Array Firmware V5.2.0 (R212916) You will be updating to version: Unreleased V6.0.0 (R242280) PLEASE NOTE: You are upgrading from firmware version V5.2.0 to version V6.0.0. You will NOT be able to downgrade back to V5.2.0 once the upgrade is finished. The firmware update will not take effect until you restart the array. Do you want to proceed (y/n) [n]: y Preparing to update active controller. Updating flash memory on active controller. This will take several minutes. Update of flash memory on active controller completed.

26

Updating Firmware
Updating flash memory on secondary controller. This will take several minutes. Preparing to update secondary controller. Update completed successfully. The firmware update will take effect when the array is restarted. To restart the array, enter the restart command at the CLI prompt. >

6 CLI Output Examples

Output Displayed When Firmware Version is Confirmed

The following example displays the screen output shown when you enter member select member_name show controllers to verify the firmware revision on the arrays Control Modules. The SlotID value shows the Control Module, and the FWRev. value shows the firmware revision running on the controller. In this scenario, the controllers are running firmware version 5.0.0.
Note: This is the output shown after you enter the command shown at step 8 in the procedure in Updating the

Firmware Using the CLI on page 12.

> member select memlab2 show controllers

_______________________Controller Information _______________________________ SlotID: 0 Status: active Model: 70-0011(TYPE 2) BatteryStatus: ok ProcessorTemperature: 55 ChipsetTemperature: 38 LastBootTime: 2010-06-03:13:31:46 SerialNumber: B027885 Manufactured: 2807 ECOLevel: C00 CM Rev.: R33 FW Rev.: Storage Array Firmware V5.0.0 NVRAM Battery: good (R124915) BootRomVersion: 3.3.1 BootRomVrsion: 2.3.3 EDT 2006 _____________________________________________________________________________ _____________________________________________________________________________ SlotID: 1 Status: active Model: 70-0011(TYPE 2) BatteryStatus: ok ProcessorTemperature: 55 ChipsetTemperature: 38 LastBootTime: 2010-06-03:13:31:73 SerialNumber: B027885 Manufactured: 2807 ECOLevel: C00 CM Rev.: R33 FW Rev.: Storage Array Firmware V5.0.0 NVRAM Battery: good (R124915) BootRomVersion: 3.3.1 BootRomBuilDate: Wed Sep 27 01:29:14 EDT 2006 _____________________________________________________________________________ _____________________Cache Information ______________________________________ CacheMode: write-back Controller-Safe: disabled Low-Battery-Safe: enabled

27