update

Updates array firmware.

A PS Series storage array includes single or dual control modules, each with a compact flash card running the PS Series firmware. You should always run the latest storage array firmware to take advantage of new product features, enhancements, and fixes.

Note: It is recommended that you read the PS Series Release Notes before beginning the update.

When updating array firmware, keep in mind the following important issues:

The following steps take you through the PS Series firmware update procedure:

  1. Gather network information and locate a host. The update procedure requires the following items for each array you are updating:
  2. Obtain the firmware update kit and documentation. Follow these steps to obtain the update kit and documentation:
    1. On the host that has the FTP utility available, use a web browser to access the EqualLogic website (www.equallogic.com). Click Support and log in to a support account. Create an account if you do not have one.
    2. In the Downloads area, select the archived update kit that is right for your operating system. The kit is approximately 15 MB in size.
  3. Consider host implications. Shut down if necessary. See the PS Series Release Notes for information about specific configurations that should not be affected by the momentary disruption in volume availability resulting from an array restart. If your configuration does not meet the requirements in the Release Notes, you may want to consider shutting down the hosts accessing the group volumes. After the update, you can restart the hosts.
  4. Cleanly restart the array, if currently running firmware prior to V2.2.3. If the array is currently 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. To connect to the array, do one of the following:
  5. Copy the kit to the array. Use FTP to copy the update kit from the host in Step 2 to the array being updated. Specify the array IP address obtained in Step 1 as input to the open command. When prompted for an account and password, specify the grpadmin account and password. Be sure the transfer occurs in binary mode.

    Note that the update kit name must not be changed at any step in the copy process. If the name is changed, the update will fail. Because some versions of FTP convert file names to uppercase, specify the update kit name twice with the put command, as shown in the example below.

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

    ftp> open 192.168.1.53

    Connected to 192.168.1.53.

    220 192.168.1.53 FTP server ready.

    Name: grpadmin

    331 Password required for grpadmin.

    Password: 

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

        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

  7. Update the array firmware. Use a serial connection or use telnet or SSH to connect to an IP address assigned to a network interface on the array (for example, eth0). Do not connect to the group IP address.

    Once connected to an array, press the <Enter> key and log in to an administration account that has read-write permission (for example, the grpadmin account). At the CLI prompt, enter the update command. On a dual control module array, both control modules will be updated.
  8. Cleanly restart the array. When the update completes, at the CLI prompt, enter the restart command. You must restart the array to apply the new firmware. It is recommended that you restart the array as soon as possible.
  9. Verify the firmware. In the GUI, you can view control module information by expanding the members list in the leftmost panel, selecting a member name, and then clicking the Controllers tab. You can also use the following CLI command, specifying the member name:

    member select
    member_name show controllers

    On a dual control module array, the firmware on both control modules must be the same. If not, or if only one control module appears but two are installed, contact your support provider.
  10. Repeat the procedure on each group member. If you are updating firmware on a multi-member group, repeat Steps 4 to 8 on the remaining members.

    Note that between updating group members, wait for the SAN to stabilize before continuing with the update.
  11. Turn on hosts. If you chose to shut down the hosts accessing the group volumes, you can turn them back on.

Format

update

Example

The following example uses a serial connection to an array to which the firmware update kit has been copied, updates the firmware, and then restarts the array.

            EqualLogic, Inc. - Storage Arrays

 

login: grpadmin

Password:

 

             Welcome to Group Manager

        Copyright 2001 — 2006 EqualLogic, Inc.

update

This command will update the firmware on the array's flash card memory using the kit that is already loaded onto 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.

 

The firmware update will not take effect until the array is restarted.

Do you want to proceed (y/n) [y]: y

Active and secondary control modules detected.

 .

 .

 .

Update completed successfully.

The update will take effect after the next member restart. If you want to restart now, invoke the "restart" command.

> restart