C H A P T E R  5

2U FC Module FRUs

This chapter provides instructions for removing and installing field-replaceable units (FRUs) in Sun StorEdge 3510 FC arrays.

Topics covered in this chapter are:


5.1 Replacing an I/O Controller Module

Be sure to follow the Static Electricity Precautions. The I/O controller modules are hot-serviceable. Hot-serviceable means that the module can be replaced while the array and hosts are powered on but the connected hosts must be inactive.



caution icon

Caution - Connected hosts must be inactive during this replacement procedure.



5.1.1 Saving the Configuration Settings to NVRAM

Before replacing a controller module, save the configuration settings to NVRAM. If power is removed before you replace an I/O controller module, the settings can be restored from NVRAM.



caution icon

Caution - If you power off the array and replace a controller module, the replacement controller could become the primary controller and overwrite any configuration settings previously set.





Note - It is also important to save the configuration settings to NVRAM after replacing a failed drive.



1. From the firmware application Main Menu, choose "system Functions." Use the arrow keys to scroll down, and choose "controller maintenance."

2. Choose "save NVRAM to disks" and press Return. Select Yes to confirm. A message informs you that NVRAM information has been successfully saved.

5.1.2 Removing an I/O Controller Module

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 multi-pathing software to manage them. If multi-pathing 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.



2. Write down the cabling configuration for the controller-to-host connection and expansion unit connections so that you can reconnect the cables correctly with the new I/O controller module. See FIGURE 5-1.

3. Remove all cables 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. Hold the thumbscrews, and pull out the I/O controller module.

 FIGURE 5-1 Hardware Connections on the Back of a Dual-Controller FC Array

Figure shows the back panel of a dual-controller FC array with the hardware connections identified.

Management is in-band through fibre host connections and out-of-band through the serial port and Ethernet port on the back of each controller.

5.1.3 Installing an I/O Controller Module

1. Keep the array powered on. Gently slide the I/O controller module into the unit until it clicks and is seated in the backplane.



caution icon

Caution - Be sure that the module is properly inserted into 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. Refer to I/O Controller Replacement for a Single-Controller or Powered-Off Array.



2. 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.



caution icon

Caution - Wait a minimum of 10 minutes for the firmware synchronization process to be completed. If the newly installed controller is removed for ANY reason during the period when the status LED is AMBER (for 10 minutes or more), the controller can be rendered inoperable and must be returned for repair.



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 is required for proper redundant controller operation.

The redundant controller process automatically synchronizes 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 3.27N and the new controller has 3.27Q, the new controller will be synchronized to have the 3.27N firmware of the running controller. To monitor this process, refer to Monitoring the Automatic Firmware Update with a Recently Installed Controller FRU.

3. If you hear an audible alarm and see a blinking amber Event light on the front of your array, the SES firmware or its associated PLD code in the new controller has version that is different from the code in the other I/O controller in your array.

To solve this mismatch, refer to SES Firmware Update Sometimes Required with I/O Controller Module Replacements.

4. If you wish to have the most current version of firmware on your controllers, download the latest firmware patch as described the Release Notes for the array.



caution icon

Caution - Follow the upgrade instructions in the patch README file with great care, to download and install firmware correctly. If the wrong firmware is installed, or the firmware is installed on the wrong device, your controller may be rendered inoperable.



5. Reconnect the original cables to the new I/O controller module.



caution icon

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.1.4 Monitoring the Automatic Firmware Update with a Recently Installed Controller FRU

To monitor the status of the automatic firmware update, use the CLI show redundancy command. The CLI will display the progression of "Failed," "Scanning," "Detected" and "Enabled" states.



Note - If you have not installed the CLI software, you need to install it from the CD that was packaged with your array.



5.1.5 SES Firmware Update Sometimes Required with I/O Controller Module Replacements

Periodically, firmware upgrades are made available as patches that you can download from SunSolvetrademark Online, located at:

http://sunsolve.sun.com

The Sun StorEdge 3510 FC array patch contains the most current version of the controller, SES, and PLD firmware.

SunSolve has extensive search capabilities that can help you find this 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.

When you power on the expansion unit or array, if 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 from that of the other I/O module in the unit/array. To resolve this issue you need to download new SES firmware. This can be done using Sun StorEdge Configuration Service software or the command line interface (CLI) for your array.

If you have not installed this software, you need to install it from the CD that was packaged with your array.

Use the CLI commands show ses and show events to see what error condition is causing the alarms. If the error message indicates a PLD firmware mismatch, it may 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 Configuration Service User's Guide for your array to see instructions for "flashing" the upgraded firmware to the appropriate device, or refer to the sccli(1M) man page for instructions on performing the same operation using the CLI.



caution icon

Caution - Follow the upgrade instructions in the patch README file with great care, to download and install firmware correctly. If the wrong firmware is installed, or the firmware is installed on the wrong device, your controller may be rendered inoperable. Always be sure to upgrade your SES firmware first before trying to determine if you need a PLD upgrade.



5.1.6 Converting a Dual-Controller Array to a Single Controller Array

If you convert a dual-controller unit into a single-controller unit, the SSCS 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 SSCS 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 for the Sun StoreEdge 3510 FC array. The section containing the instructions is entitled, "Converting a Dual Controller Array to a Single Controller Array."

5.1.7 I/O Controller Replacement for a Single-Controller or Powered-Off Array

If the array was powered off during the controller replacement or if you replaced a controller in a single-controller configuration, perform the following important steps.

1. Restore configuration settings from NVRAM if the new controller replaced an old controller:

a. From the Main Menu, choose "system Functions," choose "Controller maintenance," and press Return.

b. Choose "Restore NVRAM from disks" and press Return. Select Yes to confirm.

2. Set the parameter called the "Controller Unique Identifier" to the correct value:

a. From the firmware Main Menu, choose "view and edit Configuration parameters," then choose "Controller Parameters" and press Return.

b. From the Controller Parameters menu, choose "Controller Unique Identifier <hex>" and press Return. 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 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.

3. To implement the revised configuration settings from step 1 or step 2, choose "system Functions" from the Main Menu, choose "Reset controller" and press Return.


5.2 Replacing I/O Expansion Modules

Be sure to follow Static Electricity Precautions.

All I/O expansion modules are hot-serviceable. Hot-serviceable means that the module can be replaced while the array and hosts are powered on but the connected hosts must be inactive.



caution icon

Caution - When you replace an I/O expansion module, the connected hosts must be inactive during the replacement procedure.



5.2.1 Removing the I/O Expansion Module

1. Keep the array powered on, and be sure that the connected hosts are inactive during this procedure.

2. Turn the thumbscrews on the left and right sides of an I/O expansion module counterclockwise until the thumbscrews are disengaged from the chassis.

3. Hold the thumbscrews and pull out the I/O expansion module.

5.2.2 Installing the I/O Expansion Module

1. Keep the array powered on, and be sure that the connected hosts are inactive during this procedure.

2. Slide the I/O expansion module into the chassis until the module is firmly seated in the backplane, and the module's front panel is flush with the chassis.



caution icon

Caution - Be sure that the I/O expansion module is properly inserted into the guide rails of the array.



3. Turn the thumbscrews on the left and right sides of the I/O expansion module clockwise until the thumbscrews are finger-tight to secure the module.



Note - To ensure that a thumbscrew is finger-tight, tighten it with a screwdriver and then loosen the thumbscrew counterclockwise a quarter-turn.



When you power on your array, if you hear an audible alarm and see a blinking amber Event light on the front of your array, the SES firmware or its associated PLD code in the new controller has version that is different from the code in the other I/O controller in your array. To solve this mismatch, refer 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.




5.3 Installing Small Form-Factor Pluggable Transceivers

Fibre Channel arrays use small form-factor (SFP) transceivers to attach the array to hosts and expansion units.

Each Fibre Channel I/O controller module has six SFP ports, as shown in the lower row of ports in FIGURE 5-2. These ports are labeled FC0 through FC5.

 FIGURE 5-2 Six SFP Ports on an I/O Controller Module

Figure shows SFP-Pluggable Ports on a Single Controller.

Each Fibre Channel I/O expansion module has two SFP ports. These ports are labeled Loop A or Loop B.

1. Slide the SFP into the SFP port so that the gold pins connect firmly with the chassis.

 FIGURE 5-3 Typical SFP Used to Connect Cables to SFP Ports

Figure shows typical SFP used to connect cables to array chassis ports.

2. Plug one end of a Fibre Channel cable into the duplex jack at the end of the SFP, as shown in FIGURE 5-4.

3. Plug the other end into a server or into an FC expansion unit.

 FIGURE 5-4 Duplex Jack at the End of an SFP

Figure shows a duplex jack at the end of an SFP.


Note - To remove an SFP, make sure that no cable is connected to it and then slide it out from the port.




5.4 Installing a RAID/Expansion Chassis FRU

The chassis (box) FRU for the Sun StorEdge 3510 FC array includes a chassis, its drive midplane, and its backplane. This product is ordered to replace a box that has been damaged or whose midplane or backplane has been damaged.

To make a fully functional array, you need to add the following parts from the replaced array:

To install the individual modules, use the replacement instructions provided in this guide.

To configure the array, refer to the installation manual for your array, located on your Sun StorEdge 3000 Family Documentation CD or on the product websites.

To replace the chassis frame of an existing RAID array or expansion unit, perform the following steps.

1. Connect to the firmware application via the serial interface (tip for Solaris/Linux) or via telnet.



caution icon

Caution - Connected hosts must be inactive during this replacement procedure.



2. If the defective array is a RAID array:

a. From the Main Menu, choose "view and edit Configuration parameters," then choose "Controller Parameters."

b. Write down the Controller Unique Identifier (hex) - value.

3. Power off both power supply modules on the defective array.

4. Ensure all FC cables attached to the I/O controller module are labeled clearly.

5. Write down the defective array's cabling configuration.

6. Remove all FC cables attached to the I/O controller module.

7. If the defective array is a RAID array, remove all serial and Ethernet cables connected to the I/O controller modules.

8. Label each disk drive with its disk slot position in the array.

9. Remove the I/O controller module(s), power supply modules, and disk drives from the defective array.

10. Remove the defective chassis.

11. Obtain the replacement chassis.

12. Reinstall all previously removed FRUs in their original positions into the replacement chassis.

13. Reinstall all FC, serial, Ethernet, and power cables in their original positions.

14. Power on both power supply modules on the replacement chassis.

15. If the replacement chassis is an expansion unit or JBOD, refer to your installation manual to configure it.

16. If the replacement chassis is a RAID array, proceed with the following steps:

a. Connect to the array console menu interface via the serial interface (tip for Solaris/Linux) or via telnet.

b. From the Main Menu, choose "view and edit Configuration parameters," then "Controller Parameters."

c. Select "Controller Unique Identifier (hex)."

17. If this array is being used by clustered hosts, or for any other reason its attached hosts require that their Device IDs remaining consistent, perform these steps:

a. Set Controller Unique Identifier (hex) to the value you wrote down in step 2.

b. Reset the RAID Controllers: From the Main Menu, choose "system Functions," then "Reset controller." Confirm Yes when prompted.

c. This procedure is now complete. Proceed with step 19.

18. If this array is NOT being used by clustered hosts, perform these steps:

a. On the firmware main menu, choose "view and edit Configuration parameters," then choose "Controller Parameters," and press Return.

 Screen capture showing main menu with view and edit Configuration parameters selected and sub menu with Controller Parameters selected.

b. From the Controller Parameters menu, choose "Controller Unique Identifier <hex>" and press Return.

c. Type in the value 0 (to automatically read the chassis serial number from the midplane).

The value 0 is immediately replaced with the hex value of the chassis serial number.

 Screen capture showing a sub menu with Controller Unique Identifier <hex> displayed.

d. To implement the revised parameter value, choose "system Functions" on the Main Menu, choose "Reset Controller" and press Return.

19. Connect the array to hosts according to the configuration identified in steps 4
and 5. The chassis replacement is now complete.


5.5 Converting an FC JBOD to an FC RAID Array

You can convert an FC JBOD (or expansion unit) to a single- or dual-controller FC RAID array by performing the following procedure.

Components required for this conversion are:



Note - If you do not have the required cables, consult your sales representative to obtain them.



1. If you have data on the JBOD drives, be sure to back up the data onto the network or onto another array prior to the conversion of the JBOD to a RAID array.



caution icon

Caution - The data on the drives of a JBOD will not be accessible after the JBOD is converted to a RAID array. Therefore, it is essential that you back up the JBOD data onto another storage device prior to converting the JBOD to a RAID array.





Note - You must use a tool within Solaris, or an external software package to perform the data backup function. The firmware, software and CLI provided with the Sun StorEdge 3510 FC array do not have backup functions for data.



2. If you use Sun StorEdge Configuration Service (SSCS) to monitor your arrays and JBODs, stop the sscs daemon and close the console.



Note - When you disconnect the JBOD from the host, the JBOD drives will appear as failed drives in SSCS. To remove the failed drive entries, you need to stop the daemon, remove the JBOD, and restart the daemon.



3. To convert the JBOD to a RAID array, power off the JBOD.

4. Remove all cables connected to the JBOD I/O expansion module(s) which will be replaced by I/O controller module(s).

5. Remove the top I/O expansion module with the following steps.

a. Turn the thumbscrews on the left and right sides of an I/O expansion module counterclockwise until the thumbscrews are disengaged from the chassis.

b. Hold the thumbscrews and pull out the I/O expansion module.

c. To remove an SFP, make sure no cable is connected to it and then slide it out from the port.

Each I/O expansion module has one SFP which can be re-used and inserted into the new I/O controller module.

6. Insert the SFP from step 5c into the new I/O controller module.

Slide the single-end of the SFP into an empty port so that it connects firmly with the chassis.

See FIGURE 5-5 and FIGURE 5-6 for recommended SFP locations in I/O controller modules.



Note - I/O controller module FRUs do not have any SFPs; the SFPs must be ordered separately. The I/O controller module X-Option includes two SFPs, an Ethernet cable, and a serial cable.



In a dual-controller array, the recommended configuration is SFPs plugged into the following ports, namely into one port out of two ports in each pair of host and drive ports:

This configuration provides connections to all four host channels as well as to both drive channels, and prevents a single point-of-failure.

 FIGURE 5-5 Recommended Dual-Controller SFP Placement

Figure shows the default dual-controller SFP placement.

In a single-controller array, SFPs are usually plugged into FC0, FC1, FC4, and FC5. No SFPs are plugged into the drive channels. This configuration is appropriate for connecting to up to four hosts or fibre switches, with no connection to expansion units.

 FIGURE 5-6 Single-Controller SFP Placement

Figure shows the default single-controller SFP placement.

7. Insert additional SFPs into the new I/O controller module as needed.

8. Install an I/O controller module into the top slot with the following steps.

a. Gently slide the I/O controller module into the unit until it clicks and is seated in the backplane.



caution icon

Caution - Be sure that the module is properly inserted into the guide rails of the array.



b. 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.



9. Repeat steps 4 and 5 to remove the I/O module in the lower slot and repeat step 6 to install a second I/O controller module if you want to create a dual-controller RAID array.

10. Power on the array.

11. Print or locate chapters 4 and 5 of the Sun StorEdge Installation, Operation and Service Manual for the array, to use for the remainder of this procedure.

12. Connect the new RAID array to a terminal emulation program or workstation through its serial port.

For information on how to connect to the serial port, refer to section 4.7, Configuring a COM Port to Connect to a RAID Array, in the installation manual.

On a Solaris system, use the tip command to access the array locally.

# tip -38400 /dev/ttyn

where n is the COM port identifier. For instance, if you have connected the array to the COM port identified as ttyb, use this command:

# tip -38400 /dev/ttyb

Refresh your screen by holding down the Control key on your keyboard and pressing the letter L key on your keyboard.

13. Set up an IP address for the chassis.

Refer to section 4.8, Setting an IP Address, in the installation manual.



Note - You can access the firmware application program directly through the serial port, or over Ethernet after you have set up the IP address.



14. To telnet to the chassis and access the firmware application, refer to section 4.9, Setting Up Out-of-Band Management Over Ethernet, in the installation manual.

15. The Controller Unique Identifier for each I/O controller module must be set to 0 so that it adopts the chassis serial number with the Reset controller command.

The Controller Unique Identifier is used to create Ethernet addresses and worldwide names.

Perform the following steps to ensure that the Controller Unique Identifier is set to zero.

a. On the firmware main menu, choose "view and edit Configuration parameters," then choose "Controller Parameters," and press Return.

 Screen capture showing a sub menu with Controller Parameters selected.

b. From the Controller Parameters menu, choose "Controller Unique Identifier <hex>" and press Return.

c. Type in the value 0 (to automatically read the chassis serial number from the midplane).

The value 0 is immediately replaced with the hex value of the chassis serial number.

 Screen capture showing a sub menu with Controller Unique Identifier <hex> displayed.

d. To implement the revised parameter value, choose "system Functions" on the Main Menu, choose "Reset Controller" and press Return.

16. On the firmware main menu, choose "view system Information," and record the serial number of the array. You will use this number later.

 Screen capture showing the serial number displayed.

17. If you plan to use SSCS to manage and monitor the RAID array, perform the following additional steps.

a. Restart the SSCS agent and the console.

b. From the SSCS main window in the console, click View right arrow Agent Options Management, and uncheck the box labeled Enable JBOD support.

You need to disable the JBOD support temporarily in order to remove the old JBOD drive assignments.

c. Click View right arrow View Server.

d. Double-click on the server which had the JBOD connected to it. Click the Probe button.

The JBOD connections are removed now.

e. Click Array Administration right arrow Controller Assignment.

The Assign Server to Manage a RAID Controller window is displayed.

f. Check that the RAID array serial number recorded in step 16 is displayed.

If the serial number is not displayed, check the operating system information in the Sun StorEdge Operation, Installation, and Service Manual and your operating system documentation to complete the configuration. You will need to stop and restart the SSCS agent and console to see the revised configuration.

g. Select a server from the "Server to manage this controller" list and click Apply.

This enables the selected server to manage an array controller. It also disables all other servers listed from managing the same array.

h. To provide monitoring of other JBODs, click View right arrow Agent Options Management, and check the box labeled Enable JBOD support.

Your initial configuration of the RAID array is now complete. Refer to the Sun StorEdge Configuration Service User's Guide for additional information.

18. If you are creating a dual-controller RAID array, perform the following steps with the firmware application, to ensure compatibility.

a. To check the controller firmware version of each module, perform these steps:

Remove one I/O controller module so that only one I/O controller module remains in the array.

Maintain a serial port connection to a terminal or workstation as described in step 10.

In the firmware application, choose "view system Information" and record the Firmware Version.

Insert the second I/O controller module, remove the first module, and choose "view system Information" to record the Firmware Version of the second module.

 Screen capture showing the firmware version displayed.

To check that you have the latest firmware, go to:

http://sunsolve.sun.com

and select Patch Portal, and then browse in the Sun Alert Patch Report, or check the Sun StorEdge 3510 FC Release Notes for firmware patch information.

b. Check the number on each I/O controller module faceplate where there is a four-digit number such as 03/50 or 04/50.

Both I/O controller modules must have the same first two digits which represent a SES/PLD firmware level in the module. If the two modules have two different numbers, for example 03 and 04, you must upgrade one I/O controller module to the higher level or both modules to the latest SES/PLD level. For more information, refer to SES Firmware Update Sometimes Required with I/O Controller Module Replacements.

c. If the firmware versions of the two I/O controller modules do not match, download the latest firmware to each I/O controller module to ensure that they have the latest firmware and the same firmware.

To download new versions of controller firmware, disk drive firmware, or SES/PLD firmware, use one of the following tools and check the Sun StorEdge 3510 Release Notes or Sun Solve for the latest firmware patch:

19. The new RAID array requires new cabling and first-time configuration.

For cabling and configuration instructions, refer to Chapters 4 and 5 in the installation manual.



Note - Each operating system has additional procedures or requirements for seeing a new device. For instructions related to each operating system, refer to the appropriate appendix in the Sun StorEdge Installation, Operation, and Service Manual for your array.





Note - In some operating systems, you will also have obsolete files or paths associated with the removed JBOD unit; for example in Solaris operating systems, ses files are created for each JBOD drive under /dev/es. Consult your operating system documentation for information on how to remove or modify appropriate files and paths.



20. After you create RAID logical drives on the new RAID array, restore the data onto the drives.



Note - You must use a tool within Solaris, or an external software package to perform the data restore function. The firmware, software and CLI provided with the Sun StorEdge 3510 FC array do not have restore functions for data.