Sun StorEdge 3510 FC Array and Sun StorEdge 3511 SATA Array Controller Module Replacement Guide
|
819-2180-16 |
| Sun StorEdge 3510 FC Array and Sun StorEdge 3511 SATA Array Controller Module Replacement Guide
|
819-2180-16 |
These FRU components can be replaced by customers or by Sun-trained personnel.
To determine the firmware version of your I/O controller, check the model number. TABLE 1 shows the model numbers for FC and SATA I/O controllers.
|
4.11G FC controller [1] |
||
|
4.11G SATA controller * |
||
|
Note - Go to SunSolve Online at http://sunsolve.sun.com to see the latest available firmware upgrades. |
For information on version 4.1x controller firmware and 2.4 software, refer to the latest release notes. For upgrade instructions, refer to the patch README file for your product.
If you keep controller firmware version 3.27, be sure to upgrade the SES firmware to the latest version in the latest 3.27 patch:
Topics in this document include:
I/O 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.
In a dual-controller configuration, if the controller replacement FRU has a higher SES firmware version than the surviving controller, there will be an SES mismatch with alarms and an amber LED. You need to correct the SES mismatch and download the newer SES firmware. See SES Firmware Update Sometimes Required with I/O Controller Module Replacements.
In a single-controller configuration, you cannot restore the NVRAM configuration settings from disk if you replace a version 3.27 controller with a version 4.1x controller. See I/O Controller Replacement for a Single-Controller Array for single-controller replacement instructions.
Related documentation includes the following manuals on the product web site:
Before replacing a controller, 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."
A message informs you that NVRAM information has been successfully saved.
|
Do not restore a saved 3.27 NVRAM file onto a 4.1x controller FRU, or vice versa. |
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.27R on a single controller array, refer to Downgrading from Controller Firmware Version 4.1x to 3.27.
To replace an I/O controller module in a dual-controller configuration, perform the following steps.
|
1. Keep the array powered on and make sure that the connected hosts are inactive.
2. Write down the cabling configuration for the controller-to-host connections and expansion unit connections so that you can reconnect the cables correctly with the new I/O controller module.
3. Remove all cables and SFPs from the I/O controller module.
4. Turn the thumbscrews on the left and right sides of the I/O controller module counterclockwise until the thumbscrews are disengaged from the chassis.
5. Grasp the handle and carefully pull out the I/O controller module.
|
|
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. |
2. Gently slide the I/O controller module into the unit.
|
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 I/O 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. 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 FRU to match the firmware version of the other running controller. For example, if the running controller has firmware 4.13C and the new controller has 4.15, the new controller will be cross-loaded with the 4.13C firmware of the running controller. To monitor this process, see Monitoring the Automatic Firmware Update with a Recently Installed Controller FRU.
If you hear an audible alarm after the firmware cross-load, and you see a blinking amber Event light on the front of your array, the SCSI Enclosure Services (SES) firmware or its associated Programmable Logic Device (PLD) code in the new controller has a version that is different from the code in the other I/O controller in your array. To solve this mismatch, see SES Firmware Update Sometimes Required with I/O Controller Module Replacements.
The beep code that identifies an SES or PLD firmware mismatch is the repeating Morse code letter "R" (dot dash dot).
4. If you want the most current version of firmware on your controllers, download the latest firmware patch as described in the release notes for the array. See page 1 for current patch IDs and Downloading the Firmware Patch.
5. Reconnect the original cables to the new I/O controller module.
|
Caution - You must connect the hosts to the correct host channels on the I/O controller module or your configuration will not work correctly. |
To monitor the status of the automatic firmware update, use the Sun StorEdge CLI show redundancy-mode command. The Sun StorEdge CLI will display the progression of "Failed," "Scanning," "Detected," and "Enabled" states.
Located on http://sunsolve.sun.com, Sun StorEdge 3510 FC and Sun StorEdge 3511 SATA array patches contain the most current version of the controller, SES, and PLD firmware.
SunSolve has extensive search capabilities that can help you find the appropriate patch, as well as regular patch reports and alerts to let you know when firmware upgrades and related patches become available. In addition, SunSolve provides reports about bugs that have been fixed in patch updates.
Each patch includes an associated README text file that provides detailed instructions about how to download and install that patch. But, generally speaking, all firmware downloads follow the same steps:
Refer to the release notes for your array for the latest patch available for your array at the time of release.
If after replacing a controller module, you hear an audible alarm and see a blinking amber Event light on the front of the array/unit, the new I/O expansion module or controller module has a different version of SES firmware or PLD firmware than that of the other I/O module in the array/unit. To resolve this mismatch you must download new SES firmware. This can be done using the Sun StorEdge Command-Line Interface (CLI) for your array. (See "Invalid Cross-Reference Format"for non-reported mismatches.)
If you have not installed the Sun StorEdge CLI software, you must install it from the CD for your array, or from the Sun Download Center web site. For details, see the release notes for your array.
Use the Sun StorEdge CLI commands show ses-devices and show events to see what error condition is causing the alarms. If the error message indicates a PLD firmware mismatch, it might be because your SES firmware has not yet been upgraded. Upgrading your SES firmware usually resolves any apparent PLD mismatch. Refer to the Sun StorEdge 3000 Family CLI User's Guide or the sccli(1M) man pages for instructions on downloading SES firmware to the appropriate device.
SES firmware mismatches between RAID Controllers and expansion units are not reported by audible alarms or LEDs. You need to use the show ses devices CLI command as described below:
1. Verify the SES firmware version of all SES devices on the loop, including expansion units. Type the following command at the sccli> prompt:
Ch Id Chassis Vendor / Product ID Rev PLD WWNN
--------------------------------------------------------------------------------------------
2 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
2 60 0066AE SUN StorEdge 3511F D 0420 1100 204000C0FF000187
3 12 000187 SUN StorEdge 3510F A 1102 A000 204000C0FF000187
3 60 0066AE SUN StorEdge 3511F D 0420 1100 204000C0FF000187
2. Examine the SES firmware revision codes displayed in the "Rev" column. More than two lines will be displayed if a RAID enclosure has expansion chassis connected to it. The Product ID field will be "StorEdge 3510F A" for SES devices internal to the RAID array chassis, and "StorEdge 3510F D" for SES devices internal to the expansion chassis.
If all the lines contain the same revision code in the "Rev" field, then no SES firmware update is necessary. If they differ, upgrade them all to the same SES firmware version, following the instructions in the README.
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 completion of the crossload. When you power on the array, the automatic firmware cross-load will perform the correct operation but must be checked.
1. Power on the array and allow a few minutes to complete initialization.
2. Check that the correct firmware version is active on the array, by entering one of the following commands:
3. In a dual-controller configuration where both controllers have the same version number and two different letter identifiers (such as 4.14A and 4.14B), wait a minimum of 10 minutes for firmware cross-load to be completed.
4. In a dual-controller configuration where the controller modules have different firmware versions (such as 4.13 and 4.15), the 4.13 firmware will cross-load to the 4.15 controller.
5. Check that the secondary controller is active on the array by entering one of the following commands.
The Redundancy Status: Enabled indicates an initialized secondary redundant controller.
If you convert a dual-controller array into a single-controller array, the Sun StorEdge Configuration Service software does not automatically recognize the change and reports that the SES and battery board from the removed controller are failed or not present.
If you are running Sun StorEdge Configuration Service software and want to avoid this message, follow the steps in the chapter titled "Maintaining the Array," in the Sun StorEdge 3000 Family Configuration Service User's Guide. The section containing the instructions is titled, "To Convert a Dual Controller Array to a Single Controller Array."
|
FC and SATA single-controller arrays ship with a JBOD I/O module in 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 JBOD I/O module counterclockwise until the thumbscrews are disengaged from the chassis.
3. Grasp the handle and carefully pull out the JBOD I/O module.
4. Gently slide the I/O 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:
5. Turn the thumbscrews on the left and right sides of the I/O 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 FRU to match the firmware version of the other running controller. For example, if the running controller has firmware 4.13C and the new controller has 4.15, the new controller will be cross-loaded with the 4.13C firmware of the running controller. To monitor this process, see Monitoring the Automatic Firmware Update with a Recently Installed Controller FRU.
If you hear an audible alarm after the firmware cross-load and see a blinking amber Event light on the front of your array, the SCSI Enclosure Services (SES) firmware or its associated Programmable Logic Device (PLD) code in the new controller has a version that is different from the code in the other I/O controller in your array. To solve this mismatch, see to SES Firmware Update Sometimes Required with I/O Controller Module Replacements.
|
Note - The beep code that identifies an SES or PLD firmware mismatch is the repeating Morse code letter "R" (dot dash dot). |
6. 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.
7. Connect the cables to the new I/O controller module.
8. Set up the host channels for the new I/O controller module.
For cabling and 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 connect the hosts to the correct host channels on the I/O controller module or your configuration will not work correctly. |
To replace an I/O 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 choose "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>."
d. Write down the cabling configuration for the controller-to-host connections and expansion unit connections so that you can reconnect the cables correctly with the new I/O controller module.
a. Keep the array powered on and make sure that the connected hosts are inactive.
b. Remove all cables and SFPs from the I/O controller module.
c. Turn the thumbscrews on the left and right sides of the I/O controller module counterclockwise until the thumbscrews are disengaged from the chassis.
d. Grasp the handle and carefully pull out the I/O controller module.
3. Insert the replacement controller.
b. Gently slide the I/O controller module FRU into the slot, and push forward until you begin to feel resistance as the connecting pins engage.
c. 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.
|
Be sure that the module is properly inserted in the guide rails of the array and that you keep the power on. |
d. Turn the thumbscrews on the left and right sides of the I/O 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. Reconnect the original cables to the new I/O controller module.
|
Caution - You must connect the hosts to the correct host channels on the I/O controller module, or your configuration will not work correctly. |
5. From the RAID firmware Main Menu, select "system Functions Controller maintenance Restore NVRAM from disks," and choose Yes to confirm. Confirm that all configuration parameters are correctly set.
6. Confirm that the "Controller Unique Identifier" parameter is set to the value recorded in step 1c.
a. From the RAID firmware Main Menu, choose "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
b. If the "Controller Unique Identifier" is not set to the value recorded in step 1c, 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 choose Yes to confirm.
|
Do not downgrade from controller version 4.1x to 3.27 unless you are performing a FRU replacement or in an emergency with Technical Support assistance. If you upgrade an array to 4.1x controller firmware, change one or more parameters, and then downgrade back to 3.27, you can lose all data. You can lose or corrupt all data from all logical drives due to conflicting parameters between firmware versions, such as optimization and stripe size settings which have different NVRAM structures and different defaults. |
Earlier versions of the controller firmware work with the latest SES, 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.4 is compatible with controller version 3.27. CLI 1.6.2 can be used to downgrade to 3.27 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:
To downgrade from controller firmware 4.1x to 3.27 firmware, perform the following steps.
1. Change your working directory to the directory in which the patch was unpacked and confirm that the 3.27 controller firmware file is present using the ls command. The file must be one of the following:
2. Invoke sccli, and verify that you are running sccli version 1.6.2 or 2.x with the version command.
3. 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 411G or later, continue with Step 4.
4. Version 3.27 only supports 8 logical drives. To confirm that the array has no more than 8 logical drives, at the sccli> prompt, type:
|
Caution - If you have more than 8 logical drives, do not perform this downgrade. You will lose all data above the 8 logical drive limit. |
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.27 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.
Since the SSCS agent may interfere with firmware downloads, it is necessary to stop any SSCS agent that may be running on any host connected to the array controller. To stop the SSCS agent, log in as root on each host connected to the array and on which the SUNWsscs package has been installed, and issue the shell command /etc/init.d/ssagent stop.
If the SSCS agent is running on a Microsoft Windows system connected to the array, use the Services application (Start> Run> services.msc) to stop the SSCS Agent service.
StorADE, or any other application which monitors the status of the enclosure, may also interfere with controller or SAF-TE firmware downloads. Stop the StorADE agent software, or any other software that monitors the array, following the procedures described in the documentation for that application.
7. At the sccli> prompt, type:
where filename is SUN327R-3510.bin for the 3510 FC array or SUN327R-3511.bin for the 3511 SATA 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.
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 revision of the array. Type the following command.
Verify that the firmware revision is now reported as 327R for FC and SATA arrays.
12. Reconfigure your array to the desired configuration. If you saved a 3.27 configuration file to restore, type:
where filename is the name of the file that contains the configuration. Otherwise, configure the array using the CLI or the firmware application.
|
Caution - Do not restore a 4.1x configuration on a 3.27 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 following the procedures in the documentation for that software.
:
Removing an I/O Controller Module 
