3310 SCSI array controller module ships with controller firmware version 3.66 which is only available in SCSI FRUs and which provides the following functions:
To provide maximum usability, the Sun StorEdge 3310 SCSI array controller module ships with controller firmware version 3.66 which is only available in SCSI FRUs and which provides the following functions:
for the single-controller FRU configurations are:
To upgrade the 3.66 firmware to 4.1x firmware for a single-controller configuration, refer to the patch README instructions.
To downgrade the 3.66 firmware to 3.25 firmware for a single-controller configuration, refer to Downgrading the Controller Firmware from 3.66 to 3.25 in a Single-Controller Array.
|
Note - Always check the SunSolve Download Center located at http://sunsolve.sun.com for the latest available firmware upgrades. |
To determine the firmware version of your SCSI controller, check the model number. TABLE 1 shows the model numbers for SCSI controllers.
Topics in this document include:
|
Caution - In a single-controller configuration, you cannot restore the NVRAM configuration settings from disk if you replace a version 3.25 controller with a version 3.66 controller. See SCSI Controller Replacement for a Single-Controller Array for single-controller replacement instructions. |
|
Note - Be sure to check and update SAF-TE firmware in all configurations to provide the best performance. The latest SAF-TE firmware is included in each controller firmware patch. |
The patch README files provide detailed instructions for firmware upgrades. Other related documentation includes the following documents on the product web site:
SCSI controller modules are hot-swappable. In the event that it is impossible or impractical to halt I/O from hosts to the array, a controller can be replaced while the surviving controller is active and servicing I/O.
However, if your configuration enables you to halt I/O during the controller replacement procedure without disruption, it is a good idea to do so. With write-back cache enabled under heavy I/O, cache synchronization can take three hours or more to complete. During this time, your controller will display "preparing failback" status and the LED remains amber.
It is also possible that hardware errors or configuration errors may be present but undetected, resulting in an unserviceable condition that will only be revealed when the hot-swap is underway. For instance, it is possible that a hardware module might be improperly seated.
It is good practice before replacing a controller FRU to try to verify your system's health. Do not replace a working controller on a channel that is offline.
When a controller fails in a dual-controller configuration, the remaining controller automatically becomes the primary controller, if it is not already. If you replace a controller that has not failed, force-fail the controller to be replaced via one of the following methods.
Set Peripheral Device Entry Redundant Controller - Primary force Primary controller failure".
Set Peripheral Device Entry Redundant Controller - Primary force Secondary controller failure".
For details on the fail, show redundancy, and show events commands, refer to the Sun StorEdge 3000 Family CLI User's Guide.
When a controller is replaced in a dual-controller configuration, the controller firmware of the remaining functional controller automatically overwrites the firmware of the new replacement controller to maintain compatibility. This is referred to as cross-loading. Cross-loading uses the NVRAM configuration settings to synchronize the firmware version of the newly installed controller to match the firmware version of the running controller.
|
Caution - In a single-controller chassis, the FRU firmware 3.66 cannot be used by itself and must have a released version of 3.25 or 4.1x firmware downloaded to the controller FRU. Be sure to follow the instructions in SCSI Controller Replacement for a Single-Controller Array, and Downgrading the Controller Firmware from 3.66 to 3.25 in a Single-Controller Array when applicable. |
Before replacing a controller module, save the NVRAM configuration settings to disk. The saved NVRAM file can be used to restore configuration settings only if the replacement controller has the same firmware version as the defective controller.
1. From the RAID firmware Main Menu, choose "system Functions controller maintenance save NVRAM to disks."
2. Select Yes to confirm. A message informs you that NVRAM information has been successfully saved.
1. Go to http://sunsolve.sun.com.
3. Use Patch Finder to locate the patch ID by entering the patch ID into the search field and clicking the Find Patch button.
4. Select the link for the format that you want, either HTTP or FTP next to Download Patch, or HTTP or FTP next to Download Signed Patch.
5. In the dialog box that is displayed, indicate the destination directory for the patch and proceed to download the file to that location.
6. To install the latest firmware, follow the instructions in the patch README file. To downgrade to 3.25W on a single controller array, refer to Downgrading the Controller Firmware from 3.66 to 3.25 in a Single-Controller Array.
To replace a SCSI controller module in a dual-controller configuration, perform the following steps.
|
2. Turn the thumbscrews on the left and right sides of the controller module counterclockwise until the thumbscrews are disengaged from the chassis.
3. Hold the thumbscrews, and carefully pull out the controller module.
|
|
Caution - DO NOT POWER OFF the chassis when you replace a controller module. Multiple problems can occur. If you power off the array and replace a controller module in a dual-controller configuration, the replacement controller could become the primary controller and overwrite any configuration settings previously set. Additionally, if the array is powered off incorrectly, data that is written to cache and that has not been completely written to the disks will be lost. If you powered off the array during replacement, see Restoring the Configuration Settings of a Powered-Off Array. |
2. Gently slide the controller module into the array.
|
Caution - Be sure that the module is properly inserted in the guide rails of the array and that you keep the power on. If you power off and then replace the module, you will have to continue with additional steps. See Restoring the Configuration Settings of a Powered-Off Array. |
a. Insert the controller FRU into the slot, and push forward until you begin to feel resistance as the connecting pins engage.
b. Push the controller FRU until the connecting pins are fully seated and the RAID controller fits flush against the back plate of the RAID array.
Failure to insert the controller carefully as described above can cause one of the following problems:
3. Turn the thumbscrews on the left and right sides of the controller module clockwise until they are finger-tight, to secure the module and to make the module's front panel flush with the chassis.
To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter turn.
The new controller automatically becomes the secondary controller.
In a redundant controller configuration where a new controller FRU is installed, the controller status LED will remain amber until the controllers complete the redundant controller process, which can take more than 10 minutes. Identical firmware versions on both controllers are required for proper redundant controller operation.
The redundant controller process automatically cross-loads the firmware version of the newly installed controller FRU to match the firmware version of the other running controller. For example, if the running controller has firmware 3.25W and the new controller has 3.66, the new controller will be cross-loaded with the 3.25W firmware of the running controller. To monitor this process, see Monitoring the Firmware Update for a Recently Installed Controller FRU.
4. If you want to have the most current version of firmware on your controllers, download the latest firmware patch to the controllers. See page 1 for current patch IDs and Downloading the Firmware Patch.
|
Caution - You must connect the hosts to the correct host channels on the controller module or your configuration will not work correctly. |
To monitor the status of the firmware update, use the Sun StorEdge CLI show redundancy command. The Sun StorEdge CLI will display the progression of "Failed," "Scanning," "Detected" and "Enabled" states.
If the array was inadvertently powered off during the controller replacement in a dual-controller configuration, you must perform the following steps to ensure successful operation of your array.
1. In a dual-controller configuration where both controllers have the same version number (such as 3.25S and 3.25W if you are using an older controller FRU), power on the array and wait a minimum of 10 minutes for firmware cross-load to occur.
The controller with the higher serial number becomes the primary controller.
2. In a dual-controller configuration where the controller modules have different firmware versions (namely, 3.25 and 3.66), perform the following steps:
d. Remove the 3.66 controller module. See Removing a SCSI Controller Module.
e. Power up the array with the 3.25 controller module still in the array and allow a few minutes to complete the initialization.
f. Confirm that controller version 3.25 is active by entering one of the following commands.
The firmware version is the Revision number.
g. Re-insert the 3.66 controller module. See Installing a SCSI Controller Module.
h. Wait a minimum of 10 minutes for the firmware cross-load to be completed.
3. Check that the secondary controller is active on the array by entering one of the following commands.
The Redundant Controller: Enabled status indicates an initialized secondary redundant controller.
The Redundancy Status: Enabled indicates an initialized secondary redundant controller.
If one controller fails in a dual-controller configuration, you might want to run a single controller for an extended period of time so that the array does not display as degraded.
For instructions on converting a dual-controller configuration to a single-controller configuration, refer to the section titled "To Convert a Dual Controller Array to a Single Controller Array" in the Sun StorEdge 3000 Family Configuration Service User's Guide.
|
Note - SCSI single-controller arrays ship with a blanking panel covering the secondary controller slot. This must be removed in order to install a secondary controller. |
1. Keep the array powered on and make sure that the connected hosts are inactive.
2. Turn the thumbscrews on the left and right sides of the blanking panel and remove it.
3. Gently slide the new controller module into the array.
|
Caution - Be sure that the module is properly inserted in the guide rails of the array and that you keep the power on. |
a. Insert the controller FRU into the slot, and push forward until you begin to feel resistance as the connecting pins engage.
b. Push the controller FRU until the connecting pins are fully seated and the RAID controller fits flush against the back plate of the RAID array.
Failure to insert the controller carefully as described above can cause one of the following problems:
4. Turn the thumbscrews on the left and right sides of the controller module clockwise until they are finger-tight to secure the module and to make the module's front panel flush with the chassis.
To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter turn.
The new controller automatically becomes the secondary controller.
When the new controller FRU is installed, the controller status LED will remain amber until the controllers complete the redundant controller process, which can take more than 10 minutes. The same firmware versions must be installed on both controllers for proper redundant-controller operation.
The redundant-controller process automatically cross-loads the firmware version of the newly installed controller FRU to match the firmware version of the other running controller. For example, if the running controller has firmware 4.12B and the new controller has 4.15, the new controller will be cross-loaded with the 4.12B firmware of the running controller. To monitor this process, see Monitoring the Firmware Update for a Recently Installed Controller FRU.
5. If you want the most current version of firmware on your controllers, download the latest firmware patch as described in the release notes for your array.
6. Set up the host channels for the new controller module.
For host channel set up information, refer to the "Connecting Your Array" chapter in the Sun StorEdge 3000 Family Installation, Operation, and Service Manual for your array.
|
Caution - You must set the hosts to the correct host channels on the controller module or your configuration will not work correctly. |
To replace a SCSI controller module in a single-controller configuration, perform the following steps.
1. If possible, make a record of the firmware version and configuration settings before replacing the controller.
a. Use the show configuration CLI command to output the configuration settings to a file. Refer to the Sun StorEdge 3000 Family CLI User's Guide for more information.
b. Save NVRAM configuration settings to disk.
From the RAID firmware Main Menu select "system Functions Controller maintenance Save nvram to disks," and choose Yes to save the contents of NVRAM to disk.
c. Record the Unique Controller Identifier which combines the serial number and MAC address for each chassis and is used for network connections.
From the RAID firmware Main Menu, select "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
a. Keep the array powered on and make sure that the connected hosts are inactive.
b. Turn the thumbscrews on the left and right sides of the controller module counterclockwise until the thumbscrews are disengaged from the chassis.
c. Grasp the handle and carefully pull out the controller module.
3. Insert the replacement controller.
b. Gently slide the controller module FRU into the slot, and push forward until you begin to feel resistance as the connecting pins engage.
c. Slowly push the controller FRU the rest of the way until the connecting pins are fully seated and the RAID controller fits flush against the back plate of the RAID array.
|
Caution - Be sure that the module is properly inserted into the guide rails of the array. |
d. Turn the thumbscrews on the left and right sides of the controller module clockwise until they are finger-tight, to secure the module and to make the module's front panel flush with the chassis.
To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter turn.
4. Download the desired firmware version from SunSolve.
a. To downgrade the firmware, carefully follow the instructions in Downgrading the Controller Firmware from 3.66 to 3.25 in a Single-Controller Array.
b. To upgrade the firmware to version 4.1x, refer to the patch README file supplied with the firmware.
5. Confirm that the "Controller Unique Identifier" parameter is set to the value recorded in step 1c.
a. From the RAID firmware Main Menu, select "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
b. Type the value 0 (to automatically read the chassis serial number from the midplane) or type the hex value for the original serial number of the chassis (used when the midplane has been replaced).
The Controller Unique Identifier is used to create Ethernet MAC addresses and worldwide names. The value 0 is immediately replaced with the hex value of the chassis serial number. A nonzero value should be specified only if the chassis has been replaced, but the original chassis serial number must be retained; this feature is especially important in a Sun Cluster environment, to maintain the same disk device names in a cluster.
c. To implement the revised configuration settings, choose "system Functions Reset controller" from the RAID firmware Main Menu, then select Yes to confirm.
6. If the SSCS agent was stopped, restart it. On Solaris and other UNIX systems, use the command "/etc/init.d/ssagent start." On Microsoft Windows, use the "Services" utility (Start > Run > services.msc).
If other software such as StorADE was stopped, restart it folllowing the procedures in the documentation for that software.
If you have a 3.66 SCSI replacement controller module for a single-controller configuration (see page 1 for controller module part numbers), you must downgrade the controller firmware to the released 3.25 firmware version or upgrade to a released 4.1x firmware version.
The 3.25 firmware works with the latest SAF-TE, PLD, and software versions. There is no need to downgrade any of these components if you downgrade the controller version. For instance, CLI version 2.3 is compatible with controller version 3.27. CLI 1.6.2 can be used to downgrade to 3.xx controller firmware but cannot be used to upgrade to 4.1x controller firmware.
The CLI download controller-firmware command restores factory defaults with downgrades and does not restore:
1. Change your working directory to the directory in which the patch was unpacked and confirm that the SUN325W-3310.bin file is present using the ls command.
3. Verify that you are running sccli version 1.6.2 or 2.x with the version command.
4. Verify the product and revision of the array. Type the command:
Confirm that the correct product name is displayed. Otherwise, this patch does not apply. Select a different device or discontinue installation of this patch. If the firmware version reported is 3.66, continue with step 5.
5. If you are downgrading due to an emergency and if feasible, save the configuration in a separate location. If you are unable to restore the 3.25 configuration, you can reference this file. At the sccli> command prompt, type the following commands:
6. Stop all I/O to the array before beginning the controller firmware downgrade, and unmount any filesystems or volumes mounted from the array.
7. At the sccli> prompt, type:
where filename is SUN325W-3310.bin for the Sun StorEdge 3310 SCSI array.
|
Note - Disregard the CLI message that a script is available to automate the download; the script is only for upgrades. |
The sccli command will display messages indicating that it is downloading the firmware, programming the controller's flash memory, and "engaging" the new firmware. Wait until the sccli> prompt appears again, which may take 10 minutes or more, before proceeding.
|
Caution - DO NOT POWER OFF the array or remove a controller FRU within 10 minutes of performing a controller firmware upgrade, or the controller may be rendered inoperable. |
8. To re-establish communication with the array, use the serial connection to restore the IP address, netmask, and gateway.
9. To complete the downgrade, access the CLI and enter two more commands. Type:
10. To re-establish communication with the array, use the serial connection to restore the IP address, netmask, and gateway.
11. Verify the firmware revision of the array. Type the following command.
Verify that the firmware revision is now reported as 325W for the SCSI array.
12. Reconfigure your array to the desired configuration. If you saved a 3.25 configuration file to restore, type:
where filename is the name of the file that contains the configuration.
Otherwise, configure the array using CLI or the firmware application.
|
Caution - Do not restore a 4.1x configuration on a 3.xx controller. This may cause data loss. |
13. Confirm that the Controller Unique Identifier parameter value is correct.
a. From the RAID firmware Main Menu, select "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
b. Type the value 0 (to automatically read the chassis serial number from the midplane) or type the hex value for the original serial number of the chassis (used when the midplane has been replaced).
The Controller Unique Identifier is used to create Ethernet MAC addresses and worldwide names. The value 0 is immediately replaced with the hex value of the chassis serial number. A nonzero value should be specified only if the chassis has been replaced, but the original chassis serial number must be retained; this feature is especially important in a Sun Cluster environment, to maintain the same disk device names in a cluster.
c. To implement the revised configuration settings, choose "system Functions Reset controller" from the RAID firmware Main Menu, then select Yes to confirm.
14. If the SSCS agent was stopped, restart it. On Solaris and other UNIX systems, use the command "/etc/init.d/ssagent start." On Microsoft Windows, use the "Services" utility (Start > Run > services.msc).
If other software such as StorADE was stopped, restart it folllowing the procedures in the documentation for that software.
Copyright © 2006, Dot Hill Systems Corporation and others. All rights reserved.
Removing a SCSI Controller Module 
