| Sun StorEdge 3000 Family FRU Installation Guide |    
|
| Sun StorEdge 3000 Family FRU Installation Guide |
|
| C H A P T E R 6 |
|
Sun StorEdge 3510 FC and Sun StorEdge 3511 SATA Controller FRUs |
This chapter provides instructions for removing and installing controller module FRUs in Sun StorEdge 3510 FC and Sun StorEdge 3511 SATA arrays.
Topics covered in this chapter are:
Be sure to follow the Section 1.2, Static Electricity Precautions.
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 must correct the SES mismatch and download the newer SES firmware. For details, see Section 6.3.4, 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 Section 6.6, I/O Controller Replacement for a Single-Controller Array for single controller replacement instructions.
|
Caution - For single-controller FRU replacements, be sure to follow the instructions in Section 6.6, I/O Controller Replacement for a Single-Controller Array and where necessary, downgrade to firmware version 3.27. See Section 6.6.1, Downgrading from Controller Firmware Version 4.1x to 3.27 for downgrade instructions. |
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.
|
Caution - Do not restore the 3.27 NVRAM settings from disk onto a 4.1x controller FRU, or vice versa. The NVRAM structures are incompatible. |
To determine the firmware version of your I/O controller, check the model number. TABLE 6-1 shows the model numbers for FC and SATA I/O controllers.
It is a recommended practice to always check the SunSolve Download Center located on http://sunsolve.sun.com for the latest available firmware upgrades.
If you keep the controller firmware 3.27 version, be sure to upgrade the SES firmware to the latest version in the latest 3.27 patch:
To replace a 4.1x I/O controller module with a 3.27 I/O controller module, see Section A.1, Replacing a 4.1x Controller with a 3.27 Controller (FC and SATA Only). For all other dual-controller configurations, perform the following steps.
|
Caution - Cross-loading does not work when you replace a 4.1x I/O controller with a 3.27 I/O controller in a dual-controller chassis. If you replace a 4.1x controller with a 3.27 controller in this configuration without upgrading the 3.27 controller, the replacement controller will not be recognized. See Section A.1, Replacing a 4.1x Controller with a 3.27 Controller (FC and SATA Only). |
1. Keep the array powered on and make sure that the connected hosts are inactive.
|
Note - Most users who have multiple host connections between the two controllers use multipathing software to manage them. If multipathing software and connectivity are not possible, one alternative is to power off the array and discontinue all host I/O until the replacement is completed and the array is powered on. See Section 1.4, Powering Off the Array for important instructions about powering off an array. |
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.
2. 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. If you power off and then replace the module, you will have to continue with additional steps. See Section 6.3.5, 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.
|
Note - 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 Section 6.3.3, 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 Section 6.3.4, 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). |
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 your array.
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.
Periodically, firmware upgrades are made available as patches that you can download from SunSolve
Online, located at:
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 you hear an audible alarm after replacing a controller module 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 CLI for your array.
If you have not installed the Sun StorEdge CLI software, you must install it from the product CD for your array, or from the Sun Download Center website. 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.
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 cross-load. 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.
View Peripheral Device Status."
The Redundant Controller: Enabled status indicates an initialized secondary redundant controller.
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."
|
Note - 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.
|
Note - 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 Section 6.3.3, 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 Section 6.3.4, 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. |
The 4.1x firmware upgrade requires Sun StorEdge CLI 2.x which is available on the Sun Download Center.
|
Note - The 4.11G controller firmware must be replaced with a released firmware version in a single-controller configuration. |
In a single-controller chassis with 4.11G firmware, you need to perform one of the following downgrades or upgrades.
For 3.27 downgrade instructions, refer to Section 6.6.1, Downgrading from Controller Firmware Version 4.1x to 3.27.
For 4.1x upgrade instructions, refer to the README file in the 4.1x patch.
|
Note - For information on the version 4.1x upgrade and new 2.x software, refer to the latest release notes. |
To determine the firmware version of your I/O controller, check the model number. TABLE 6-2 shows the model numbers for FC and SATA I/O controllers.
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.
Use the show configuration CLI command to output the configuration settings to a file.
where filename.txt is a text file, or
where filename.xml is an xml file.
2. From the RAID firmware Main Menu, choose "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
Record the Controller Unique Identifier which combines the serial number and MAC address for each chassis and is used for network connections and worldwide names.
3. Save NVRAM configuration settings to disk.
Controller maintenance Save nvram to disks," and choose Yes to save the contents of NVRAM to disk.
4. 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.
6. Insert the replacement controller.
a. Keep the array powered on and gently slide the controller module into the unit.
|
Caution - Be sure that the module is properly inserted into the guide rails of the array. |
b. Insert the controller 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.
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.
|
Note - To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter turn. |
7. 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. |
8. If the old controller and the new controller have the 4.1x firmware and you had saved a 4.1x NVRAM file, from the RAID firmware Main Menu, choose "system Functions Controller maintenance Restore NVRAM from disks," and choose Yes to confirm.
9. If you have a 4.11G replacement controller which requires an upgrade or a downgrade, or want to downgrade to 3.27 firmware, download the desired firmware into the replacement controller.
You must upgrade or downgrade a 4.11G controller.
If you have a 4.11I or later replacement controller module, you can downgrade it to 3.27 firmware.
10. If the old controller and the new controller have the 4.11I or later firmware and you had saved a 4.1x NVRAM file, from the RAID firmware Main Menu, choose "system Functions Controller maintenance Restore NVRAM from disks," and choose Yes to confirm. Confirm that all configuration parameters are correctly set.
11. Confirm that the "Controller Unique Identifier" parameter is set to the value recorded in Step 2.
From the RAID firmware Main Menu, choose "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
12. If the "Controller Unique Identifier" is not set to the value recorded in Step 2, 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.
13. To implement the revised configuration settings, choose "system Functions Reset controller" from the RAID firmware Main Menu, then choose Yes to confirm.
If you have a 4.11G replacement controller module for a single-controller configuration (see TABLE 6-2 for part numbers), you must downgrade the controller firmware to the released 3.27 firmware version or upgrade to a released 4.1x firmware version.
If you have a 4.1x replacement controller module and need to downgrade to 3.27 firmware, follow these procedures as well.
Earlier versions of the controller firmware work with the latest SES, PLD, SAF-TE, 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.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 the Sun StorEdge CLI.
3. Verify that you are running CLI version 1.6.2 or 2.x with the version command.
4. Verify the product and revision of the array by typing the following 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 5.
5. 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. |
6. If feasible, save the configuration in a separate location.
If you are unable to restore the 3.27 configuration, you can reference this file.
where filename.txt is a text file, or
where filename.xml is an xml file.
7. 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 Sun StorEdge Configuration Service agent may interfere with firmware downloads, it is necessary to stop any agent that may be running on any host connected to the array controller. To stop the Sun StorEdge Configuration Service agent, log in as root on each host connected to the array and on which the SUNWsscs package has been installed, and issue the following shell command:
If the Sun StorEdge Configuration Service agent is running on a Microsoft Windows system connected to the array, use the Services application to stop the 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.
8. 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 download controller-firmware 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 before proceeding. This might take 10 minutes or more.
9. To re-establish communication with the array, use the serial connection to restore the IP address, netmask, and gateway.
10. To complete the downgrade, access the CLI and enter the following commands:
11. To re-establish communication with the array, use the serial connection to restore the IP address, netmask, and gateway.
12. To verify the revision of the array, type the following command:
Confirm that the firmware revision is now reported as 327R for FC and SATA arrays.
13. Reconfigure your array to the desired configuration.
a. If you saved a 3.27 configuration file to restore, type:
where filename is the name of the file that contains the 3.27 configuration.
b. 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. |
14. Confirm that the Controller Unique Identifier parameter value is correct.
From the RAID firmware Main Menu, choose "view and edit Configuration parameters Controller Parameters Controller Unique Identifier <hex>."
15. If the "Controller Unique Identifier" is not set, 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.
16. To implement the revised configuration settings, choose "system Functions Reset controller" from the RAID firmware Main Menu, then choose Yes to confirm.
Periodically, firmware upgrades are made available as patches that you can download from SunSolve Online, located at:
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.
| Sun StorEdge 3000 Family FRU Installation Guide | 816-7326-23 |
|
Copyright © 2007, Dot Hill Systems Corporation. All rights reserved.
