Professional Documents
Culture Documents
Backing Up Data
Regular backups are 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.
Page 1
The following example is of running the kit_V10.0_DriveFw_ drive firmware update script.
seal1grp> update
12:01:40 Updating from kit file "kit_V10.0_DriveFw_2480353603.tgz"
This command will install 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.
-----------------------------------------------
The process will now update the 44 drives that qualify for a firmware upgrade.
If you proceed, please do not power off or restart the array, or remove
any drives until the update process completes.
-----------------------------------------------
Do you want to continue at this time (Y/N)? y
Page 2
If the script detects that either all drives are running the correct firmware version, or that the update is not
applicable to any drives on the array, the following dialog is displayed:
seal1grp> update
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.
Troubleshooting
This section describes possible alternate outcomes of the drive firmware update.
Update Failed
If the script cannot update the firmware on one or more drives, the following message is displayed:
Page 3
Array Firmware Too Old
If the firmware running on the member is not at the minimum required version, the following message is displayed:
ERROR: The minimum supported version for this procedure is 6.0.0. You are running
V4.3.5
Entering cleanup phase... Please Wait...
Please contact technical support.
If this problem occurs, fix the error indicated by the RAID status field and retry the drive firmware update
procedure.
Page 4
Uploading the Kit to the Array Using FTP
The computer must have network access to each group member whose drives you are updating. You can use the
pingcommand to test network connectivity between computers and group members.
Follow these steps to put the drive firmware update kit on the array:
1. Use FTP to copy the kit from the host to the array being updated.
a. To start an ftp session, type: ftp
b. To connect to an array, type: open <IP address of the array> (for example:
open 192.168.10.20 )
c. When prompted for an account and password, specify the grpadmin account and password.
d. To enable a binary mode transfer, type: binary
e. To transfer a file, type: put <file name that you want to transfer> (for example:
put kit_V10.0_DriveFw_2480353603.tgz)
f. To close the session, type: close
g. To end the ftp session, type: bye
The following example uses FTP to copy a firmware update kit named
kit_V10.0_DriveFw_2480353603.tgz from a host to an array with the IP address 192.168.1.53.
Note: Because some versions of FTP convert file names to uppercase, specify the file name twice with
the put command.
$ 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_V10.0_DriveFw_2480353603.tgz kit_V10.0_DriveFw_2480353603.tgz Note the file
name is entered twice.
local: kit_V10.0_DriveFw_2480353603.tgz remote: kit_V10.0_DriveFw_2480353603.tgz
229 Entering Extended Passive Mode (|||65534|)
150 Opening BINARY mode data connection for kit_V10.0_DriveFw_2480353603.tgz
100%|***********************| 13191 KB 81.26 KB/s 00:00 ETA
226 Transfer complete.
441803 bytes sent in 02:42 (81.06 KB/s)
ftp> close
221- Data traffic for this session was 441803 bytes in 1 file.
Total traffic for this session was 441803 bytes in 1 transfer.
221 Thank you for using the FTP service on
192.168.1.53. ftp> bye
Page 5
2. Connect to the array.
You can use a serial connection that is right for your control module model or use telnet or SSH to
connect to an array. 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.
If you are using a serial connection, the following characteristics are required for CLI access:
• 9600 baud
• 1 STOP bit
• No parity
• 8 data bits
• No flow control
When the module is connected to the array, press the Enter key and log in to an administration
account that has read-write permission (for example, the grpadmin account).
Page 6
Appendix
This document applies to the following drive and array models:
Page 7
Drive Existing Drive New Drive
Drive Model Update Script
Type Firmware Version Firmware Version
EC03
MK1001TRKB SAS kit_V10.0_DriveFw_2480353603.tgz EC04
EC02
EC03
MK2001TRKB SAS kit_V10.0_DriveFw_2480353603.tgz EC04
EC02
Page 8
Drive Existing Drive New Drive Firmware
Drive Model Update Script
Type Firmware Version Version
PE08
ST500NM0001 SAS PN04 kit_V10.0_DriveFw_2480353603.tgz PE0E
PN03
PE08
ST1000NM0001 SAS PN04 kit_V10.0_DriveFw_2480353603.tgz PE0E
PN03
PE08
ST2000NM0001 SAS PN04 kit_V10.0_DriveFw_2480353603.tgz PE0E
PN03
SAS
ST900MM0036 LEF5, LEF6 kit_V10.0_DriveFw_2480353603.tgz LEF7
SED
Page 9
Drive Existing Drive New Drive Firmware
Drive Model Update Script
Type Firmware Version Version
ST1000NM0023 SAS GE09, GE0A kit_V10.0_DriveFw_2480353603.tgz GE0F
ST2000NM0023 SAS GE09, GE0A kit_V10.0_DriveFw_2480353603.tgz GE0F
ST3000NM0023 SAS GE09, GE0A kit_V10.0_DriveFw_2480353603.tgz GE0F
ST4000NM0023 SAS GE09, GE0A kit_V10.0_DriveFw_2480353603.tgz GE0F
ST3000NM0063 SAS GEF3 kit_V10.0_DriveFw_2480353603.tgz GEFA
ST4000NM0063
SAS GEF3 kit_V10.0_DriveFw_2480353603.tgz GEFA
Page 10
10