| Sun StorEdge 3000 Family RAID Controller Firmware Migration Guide |    
|
| Sun StorEdge 3000 Family RAID Controller Firmware Migration Guide |
|
| C H A P T E R 2 |
|
Using the Firmware Migration Script (s3kdlres) |
This chapter provides steps you need to follow before you run the s3kdlres script and the steps to run the script. Topics covered include:
This section provides the steps you need to follow before you run the s3kdlres script.
1. Make sure you understand and have followed the steps provided in System Prerequisites and Requirements and Script Behavior and Limitations.
2. Make sure you have created a configuration file that enables you to verify that any custom settings have been restored after the script has been run.
See Creating a Configuration File for more information.
3. Read the latest Release Notes for your array for instructions about how and where to download the most recent controller firmware patch.
b. Unpack the patch to any convenient directory that is easy to remember (for example, /var/tmp).
4. Change your working directory to the directory in which the patch was unpacked, and confirm that the Sun binary file is present.
The firmware migration procedures require you to invoke sccli using the appropriate syntax for the type of connection used to manage the array.
If the array to be upgraded is a RAID subsystem attached to a Fibre Channel HBA installed on the local host, type the sccli command with no arguments:
If more than one array is connected to local Fibre Channel, sccli displays a list from which the appropriate device can be selected.
If the array has an IP address configured, it can be managed remotely using a network (or out-of-band) connection. To specify this mode, type:
where password is the password assigned to the controller and hostname | ip is the host name or IP address of the array. If no controller password is set, omit the
-w option and password option
|
Note - Use single quote characters to quote the password if it contains any characters that are interpreted specially by the shell. |
6. Verify that you are running version 2.3 or greater of sccli by typing:
7. Verify the product and version of the array by typing:
|
Note - For an out-of-band sccli connection, "Device Type" is not displayed for a JBOD chassis. |
For the Sun StorEdge 3310 SCSI array, refer to "SAF-TE Firmware Update" found in the README included in the patch you downloaded for your array.
For the Sun StorEdge 3510 FC or 3511 SATA array, refer to "SES Firmware Update" found in the README included in the patch you downloaded for your array.
9. Verify single or dual controller by typing:
The dual controller array is healthy if the redundancy mode is "Active-Active" and the status is "Enabled."
The single controller array is healthy if the redundancy mode is "Active-Active" and the status is "Scanning."
If the array does not show a healthy status, correct the problem before proceeding.
Perform the following steps to run the s3kdlres script.
|
Note - If you are upgrading more than one array, note the time it takes to upgrade the first array so that you can schedule the amount of time needed to upgrade the other arrays. |
|
Note - Step-by-step interactions that take place when the upgrade script runs are logged to a file called s3kdlres.log, which can be found in the same directory where the script was run. If an upgrade fails, resulting in an indeterminate or incomplete status, contact authorized service personnel and make your log files (s3kdlres.log, <filename>.xml, and <filename>.txt)available to them. (See Creating a Configuration File for information about creating <filename>.txt.) Also see Script Troubleshooting for a list of possible error messages and resolutions. |
1. Make sure you have read and performed the steps provided in System Prerequisites and Requirements, Script Behavior and Limitations, and Before Running the s3kdlres Script.
2. Make sure you have created a configuration file that enables you to verify that any custom settings have been restored after the script has been run.
See Creating a Configuration File for more information.
3. Stop all I/O activity and unmount any file systems or volumes mounted by a volume manager from the array.
4. Stop any Sun StorEdge Configuration Service agent that might be running on a host connected to the array controller.
To stop the agent, issue the shell command as "root" user:
If the agent is running on a Microsoft Windows system connected to the array, use the Services application to stop the agent service by choosing Start > Run > Services.msc.
5. Because other applications might interfere with controller firmware downloads, stop any other software that monitors the array.
Refer to the documentation for the specific application for information on stopping the agent software.
6. If you haven't already done so, set up a serial connection to the controller.
See System Prerequisites and Requirements for more information.
7. Run the script to migrate the controller firmware.
For Solaris and Linux operating systems, change the directory to:
where xml filename is a name specified for the file in which the array configuration output is saved.
where device or IP is either the device name for in-band or the IP address of the array for out-of-band.
where controller password is an optional password that only needs to be specified if a password for this controller has been previously set.
Example for in-band migration with no password:
Example for out-of-band migration with no password:
For Microsoft Windows, choose Start > Run.
To launch a command prompt, type:
where xml filename is a name specified for the file where the array configuration output is saved.
where device or IP is either the device name for in-band or the IP address of the array for out-of-band.
where controller password is an optional password that only needs to be specified if a password for this controller has been previously set.
Example for in-band migration with no password:
Example for out-of-band migration with no password:
8. When the script prompts you for the firmware file, specify the full path name where the firmware patch was extracted from and the firmware file name.
Solaris operating system example:
The script performs several steps that are output to the screen, which takes several minutes, after which the following prompt is displayed:
9. Using the RAID firmware application through the serial connection, restore the IP address, netmask, and gateway settings as recorded in the instructions in Using the RAID Firmware Application to View Settings That Are Not Restored.
From the Main Menu, choose "view and edit Configuration parameters > communication Parameters > Internet Protocol (TCP/IP)."
10. If you are using in-band communication, using the RAID firmware application through the serial connection, also restore channel settings (ID) and LUN mappings to ensure that the upgrade script is able to continue to access the array.
To restore channel settings, from the Main Menu, choose "view and edit channels."
To restore LUN mappings, from the Main Menu, choose "view and edit Host luns."
11. Reset the controller and wait for the controller to come back online.
12. Only after the controller comes back online, type yes to the prompt shown in Step 8.
13. Verify that the firmware upgrade succeeded by examining the firmware revision again by typing:
Verify that the firmware version reported is the one to which you have migrated.
14. Manually restore all other configuration settings not already specified in Step 9 and Step 10 that are listed in Configuration Settings That Are Not Restored.
Refer to the Sun StorEdge 3000 Family RAID Firmware User's Guide for more information about restoring these settings.
15. Save the current array configuration settings in .txt format with the name after.txt.
This command might take several minutes to complete.
16. Compare after.txt to the filename.txt file referenced in Step 2 and to other recorded settings to verify that settings have been restored.
17. When the migration process is finished, continue with the "SAF-TE Firmware Upgrade" or "SES Firmware Upgrade" procedure as described in the README included in the patch you downloaded for your array.
If you are connecting a Sun StorEdge 3511 expansion unit to a Sun StorEdge 3510 FC controller, continue with the section "Mixed 3510 and 3511 Upgrades" found in the README included in the patch you downloaded for your array.
| Sun StorEdge 3000 Family RAID Controller Firmware Migration Guide | 819-6573-11 |
|
Copyright © 2007, Dot Hill Systems Corporation. All rights reserved.