|A P P E N D I X A|
Migrating Controller Firmware on HP-UX and IBM AIX Operating Systems
When migrating from firmware version 3.xx to 4.15 or later on Solaris, Linux, and Microsoft Windows operating systems, you must use the s3kdlres script. The s3kdlres script cannot be used for firmware migrations on HP-UX and IBM AIX operating systems. Instead, follow the manual migration procedures provided in this appendix. Topics covered include:
Note - Before beginning the firmware migration procedures, contact Sun service personnel for assistance. Time and materials charges might apply if not currently covered under warranty/support contract.
Before installing controller firmware version 4.15 or later, make sure your environment supports the following prerequisites and requirements.
Caution - Failure to adhere to the system prerequisites and requirements can result in data loss. Refer to the latest Release Notes for your array for instructions about how and where to download the most recent controller firmware patch.
If you do not have these firmware versions installed, download patch 113722-09 from SunSolve online, and follow the instructions provided in the README for upgrading only the firmware versions mentioned above
If you do not have these firmware versions installed, download patch 113723-09 from SunSolve online and follow the instructions provided in the README for upgrading only the firmware versions mentioned above.
If you do not have these firmware versions installed, download patch 113724-03 from SunSolve online and follow the instructions provided in the README for upgrading only the firmware versions mentioned above.
If you do not have this package installed, or if you have an earlier version, download version 2.3 from the Sun Download Center, or install it from the optional Sun StorEdge Professional Manager CD. For software installation or upgrading instructions, refer to the Sun StorEdge 3000 Family Software Installation Guide.
You must have a serial connection during the migration process. Use a null modem serial cable to connect the COM port of the array to the serial port on a host workstation. Make sure the serial port setting is configured to 38400 baud, 8 bit, 1 stop bit, no parity. Refer to the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for information about connecting the RS-232 interface.
If you have logical drives or logical volumes with more than 32 partitions per logical drive or logical volume, make sure you delete all of these partitions. Create a configuration that contains less than 32 partitions per logical drive or logical volume, and then restore the data. Before beginning the firmware migration, contact authorized Sun service personnel for assistance. Time and materials charges might apply if not currently covered under warranty/support contract.
The migration procedure resets all configuration settings to the default settings of the firmware version to which you are migrating. See Creating a Configuration File for more information.
The migration procedure resets all configuration settings, including the following to the default settings of the firmware version to which you are migrating. You need to create a .txt file to record these settings so that you can refer to it to manually restore them after the firmware migration.
Type the following command to save the configuration settings in .txt format:
The command might take several minutes to complete and will save the file in the current working directory.
Note - Configuration setting output files are not transferable. That is, you cannot save a configuration file for a specific Sun StorEdge array and use it to perform the script upgrade on another Sun StorEdge array.
Use the RAID firmware application menus described in this section to view and record the following settings that are not restored. You need to provide this information when performing the migration. After nvram is reset, the only way to recover these settings is to re-enter them after the migration is complete. For information on accessing the RAID firmware application, refer to the Sun StorEdge 3000 Family RAID Firmware User's Guide.
This section provides the steps you need to take before you perform the firmware migration.
1. Make sure you understand and have followed steps provided in System Prerequisites and Requirements and Creating a Configuration File.
2. Read the latest Release Notes for your array for instructions about how and where to download the most recent controller firmware patch.
a. Download the patch.
b. Unpack the patch to any convenient directory that is easy to remember (for example, /var/tmp).
3. Change your working directory to the directory in which the patch was unpacked and confirm that the Sun binary file is present.
4. Invoke the CLI.
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
5. Verify that you are running version 2.3 or greater of sccli by typing:
6. Verify the product and version of the array by typing:
7. Examine the output.
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.
8. 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 migrate the controller firmware.
1. Make sure you have read and performed the steps provided in System Prerequisites and Requirements.
2. Make sure you have created a configuration file that enables you to restore configuration settings after the migration is complete.
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. Perform the firmware migration by typing:
8. The following messages are displayed:
The reset nvram command restores the original default settings, including all controller parameters, host, and drive parameters, etc. This command does not restore the controller IP address, instead it configures the network for DHCP. You may also lose LUN mappings on host channels.
You may need to have a serial connection to the controller available in order to be able to restore the previous configuration.
9. Wait until the sccli> prompt is displayed again, which can take 10 minutes or more, before proceeding.
10. To re-establish communication with the array, use the RAID firmware application through the serial connection to restore the IP address, netmask, and gateway recorded in Using the RAID Firmware Application to View Settings That Are Not Restored.
a. From the RAID firmware application Main Menu to restore the IP address, netmask, and gateway by choosing "view and edit Configuration parameters > communication Parameters > Internet Protocol (TCP/IP)."
b. To restore channel settings, from the Main menu, choose "view and edit channels."
c. To restore Host LUN mappings, from the Main menu, choose "view and edit Host luns."
11. Using the serial connection, manually restore the configuration settings that were recorded in the configuration file you created in Step 2.
12. Verify that the firmware migration succeeded by examining the firmware revision again by typing:
Verify that the firmware version reported is the one to which you have migrated.
13. Save the current array configuration settings in .txt format with the name after.txt.
This command might take several minutes to complete.
14. Compare after.txt to the filename.txt file referenced in Step 2 and to other recorded settings to verify that settings have been restored.
The firmware migration procedure requires extensive configuration because all factory defaults have been restored to the migrated version of the firmware.
15. 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.