update
Updates array firmware.
A PS Series array includes single or dual control modules, each with a compact flash card running the PS Series firmware. You should always run the latest 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:
- Update path. Usually, you can update an array directly to the latest firmware version. However, in some cases, you may need to update to an interim version before updating to the latest version. See the PS Series Release Notes for information about supported firmware update paths.
- Disallowed downgrades. If you have run the grpparams disallow-downgrade command in the group (see grpparams disallow-downgrades), you cannot return any group member to a PS Series firmware version prior to V3.2. Run this command to use the new features in the V3.2 release.
- Mixed firmware in a group. It is recommended that all PS Series group members run the same version of the array firmware. The Release Notes describe which firmware versions can co-exist in a group; however, only features and bug fixes common to all versions will be available. 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.
- Multi-member group updates. In a multi-member group, perform the update procedure on one member at a time. 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. For example, use the Group Manager GUI or CLI to ensure that all members and volumes are online. Also, be sure that iSCSI initiators reconnect to volumes, if applicable.
- Minimizing host disruption during updates. If an 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. In addition, regardless of the current running firmware, you must restart the array after the update procedure completes. When scheduling a firmware update, be sure to allot sufficient time to update and restart the entire group of arrays.
During an array restart, volumes with data on the array will be momentarily unavailable until the restart completes. While the volumes are unavailable, some iSCSI initiators may return errors to the operating system or applications.
The PS Series Release Notes provides examples of operating system and iSCSI initiator configurations that may be able to handle an array restart without disruption. In some cases, you may need to make modifications to the operating system. You should also ensure that the applications themselves can tolerate the restart. Other configurations may be able to tolerate an array restart without disruption. In all cases, you should first test them in a non-production environment.
If you do not have one of the identified configurations or if you are unsure of your application’s ability to tolerate the restart, you should consider planning for downtime when updating firmware. This can involve shutting down the hosts accessing the group before beginning the update procedure. After the update completes, you can restart the hosts. Planning for application downtime may be the best way to protect against unexpected disturbances.
- Backing up data. Regular backups should be a vital part of maintaining a storage environment. In addition, because upgrading infrastructure is a critical service procedure, it should be carefully planned and implemented at off-peak hours, if possible, and after a backup has occurred.
The following steps take you through the PS Series firmware update procedure:
- Gather network information and locate a host. The update procedure requires the following items for each array you are updating:
- The IP address assigned to a network interface on the array (for example, the IP address assigned to eth0). Do not use the group IP address.
- Host that has the ftp or scp utility available and network access to each array being updated. You can use the ping command to test network connectivity from an array’s IP address to a host.
- Obtain the firmware update kit and documentation. Follow these steps to obtain the update kit and documentation:
- On the host that has the FTP or SCP utility available, use a web browser to access support.dell.com/EqualLogic.
- In the Downloads area, select the archived update kit that is right for your operating system. The kit is approximately 15 MB in size.
- 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.
- 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:
- Use telnet or SSH to connect to an array through an IP address assigned to a network interface on the array (for example, eth0). Do not connect to the group IP address.
- Use the null modem cable (or cables) shipped with the array to connect Serial Port 0 on the active control module (LED labeled ACT is green) to a console or a computer running a terminal emulator. How you make a serial connection depends on the control module model. See Running Array Management Commands for more information.
Once connected, 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 restart command. When the array shuts down, the network connection closes.
- Copy the kit to the array. Use FTP or SCP 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. If using ftp, 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. Alternatively, you can use scp, which does not change file names and does not require you to log in to the array.
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 182.168.1.53.
The following example shows how to use scp to copy a firmware update kit named kit_12345678.tgz from a host to an array with the IP address 182.168.1.53:
- 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.
- 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.
- 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 array support provider.
- 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. Between updating members, wait for the SAN to stabilize before continuing with the update.
- Restart hosts. If you chose to shut down the hosts accessing the group volumes, you can restart them.
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.