StorageTek Virtual Storage Manager System 6 (VSM6)
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Internal Field process

Applies to:

Goal

 How to Replace a SPARC T4-2 Motherboard on VSM6 server

Solution

DISPATCH INSTRUCTIONS
   WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?: VSM6 trained, T4 server, Solaris 11
   TIME ESTIMATE:180 minutes

• May be 120-180 minutes

   TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
   PROBLEM OVERVIEW: How to Replace a SPARC T4-2 Motherboard on VSM6 server
  
   WHAT SKILLS DOES THE ENGINEER NEED:(IS A SITE ENGINEER AVAILABLE?) SPARC T4-2 Server product training and VSM6 product training. (Have documents listed in Reference Information section available)

   WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?:
   
       Prepare affected VSM6 server for servicing:

         Check with customer to verify whether any RTDs attached to the node being replaced are dual pathed to the other node.  If any are NOT, those RTD paths attached to the failed node must be taken offline.
       
        1. Login to the server as vsmadm on the functioning node that will NOT be stopped (motherboard replaced).
        2. Enter one of the following commands to stop VSM processes, put the failed node into maintenance mode, and shutdown the server:

           WARNING********WARNING********WARNING********WARNING********WARNING!!!
           Verify you enter or copy/paste the correct command string below for the node you need to shutdown and work on!!!

           Enter only one of the following commands – do NOT enter both commands:

            If the motherboard on NODE 1 is being replaced, enter:
            sudo /opt/vsm/bin/vsm_cli_client -c "shutdown node -maint -node 1"

            If the motherboard on NODE 2 is being replaced, enter::
            sudo /opt/vsm/bin/vsm_cli_client -c "shutdown node -maint -node 2"

            Note - In image release 6.0.6 documentation, the -force optional parameter was used but in 6.0.7 documentation was removed.

            Do not use the -force parameter unless instructed by TSC or engineering.

                
        3. Attach an antistatic wrist strap and verify the node has completely shutdown.
        4. Unplug power cords from the power supplies.
        5. Extend the server to maintenance position.
            Note: Be careful when pulling out server, as cables in CMA may bind
        6. Remove the top cover.

   WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE?:

        Removing the MotherBoard:

1. Remove the System Configuration PROM from the motherboard so you can reinstall it on the new Motherboard.
2. Remove all memory risers and filler panels.
3. Remove the System Remind button assembly (air divider) by lifting it up and away from the power supplies.
4. Disconnect all cables connected to the motherboard by completing the following tasks.
    a. Disconnect two cables that connect the motherboard to the hard disk drive backplane.
    b. Disconnect three cables from the motherboard.
    c. Disconnect the fan board power cable and the ribbon cable from the motherboard.
5. Remove the Phillips screw on the cable cover, lift and remove the cover, and disconnect the two exposed cables from the motherboard.
6. Remove the four bus bar screws securing the motherboard to the power supply backplane.
7. Remove all PCIe cards from the server.
8. Position the HDD end of the cables off to the side using the tab on the top of the plastic power supply cover.
9. Remove the motherboard by completing the following tasks.
    a. Loosen the captive screw in the corner near the fans that secures the motherboard to the chassis.
    b. Grasp the handle on the motherboard and slide it toward the front of the chassis.
    c. Lift the motherboard out of the chassis.
10. Remove the service processor from the motherboard so you can reinstall it on the new motherboard

Installing the Motherboard

1. Unpack the replacement motherboard and place it on an antistatic mat.
2. On the replacement motherboard, install the service processor that you removed from the old motherboard.
3. Grasping the motherboard by the handle, place it into the chassis.
4. Hold the cables off to the side while grasping the handle on the motherboard and sliding it toward the back of the chassis.
5. Reinsert and tighten the four bus bar screws that secure the motherboard to the power supply backplane.

Note: Using a No. 2 screwdriver, tighten the bus bar screws until the power supply backplane and the motherboard securely fasten to the bus bars.

6. Reinstall the System Remind button assembly (air divider) by sliding it into the chassis.

Caution: After replacing the motherboard, inspect the dividing wall gasket, and then install the plastic dividing wall securely. This dividing wall maintains a pressurized seal between the server cooling zones. Without this pressurized seal, the power supply fans will not be able to draw enough air to cool the drives properly.
7. Reinstall all memory risers.
8. Reinstall the cable cover.
9. Reconnect all cables from the power supply backplane, hard disk drive backplane, and fan board to their original locations on the motherboard.
10. Reinstall all PCIe cards.
11. Tighten the captive screw in the corner near the fans that secures the motherboard to the chassis.
12. On the replacement motherboard, install the System Configuration PROM that you removed from the old motherboard.
13. Install the top cover.
14. Return the server to the normal rack position.
15. Reinstall the power cords to the power supplies.
16. Prior to powering on the server, connect a terminal or a terminal emulator (PC or workstation) to the service processor SER MGT port.

If the service processor detects the host firmware on the replacement motherboard is not compatible with the existing service processor firmware, further action will be suspended and the following message will be displayed:

    Unrecognized Chassis: This module is installed in an unknown or
    unsupported chassis. You must upgrade the firmware to a newer
    version that supports this chassis.

If you see the preceding message, continue to Step 17. Otherwise, skip to Step 18.

17. Download the system firmware.
     a. If necessary, configure the service processor NET MGT port so that it can access the network.
     b. Log in to the service processor through the NET MGT port.
     c. Download the system firmware and unzip the file.

Note - You will select the .pkg that was unzipped.

Follow the firmware download instructions in the Oracle ILOM documentation.

If ILOM GUI is not working for FW upgrade use following process : http://docs.oracle.com/cd/E23075_01/html/E23076/z400056c1296389.html

NOTE: You can load any supported system firmware version, including the firmware version that had been installed prior to replacing the motherboard.


18. Power on the server.

OBTAIN CUSTOMER ACCEPTANCE:

WHAT ACTION DOES THE FE/CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?:

Boot system and monitor boot sequence for errors. Verify you are logging your ssh session should some abnormality occur while booting.

Test functionality of system:
1. Run the Solaris "sudo fmadm faulty" and SP/ILOM "show faulty" command (if only ALOM is supported run "showfaults -v" command) to verify that the fault has been cleared.
2. Perform one of the following tasks based on your verification results:
* If the previous steps did not clear the fault, refer to doc 1004229.1 for information about the tools and methods you can use to diagnose and clear
component faults.
* If the previous steps indicate that no faults have been detected, the component has been replaced successfully. No further action is required
3. From the previously failed node, reboot the VSM6 Node (to get out of maint mode) with command: (Note: the uadmin 2 1 command only boots the node logged into.)
    $ sudo uadmin 2 1
4. Check that the node came up correctly in cluster with command:
    $ /usr/cluster/bin/scstat -g

5. If the node that had the MB replaced appears to not be coming up into the cluster and online, you can open a separate ssh session and perform the following to monitor the messages file in addition to running the scstat -g. 

    $ tail -f /var/adm/messages

6. Once the node is completely up and the output of step 4 above (/usr/cluster/bin/scstat -g) looks good run the health check script:

    sudo /opt/vsm/bin/vsm_HealthCheck

    Examine the output of the health check script (especially the Summary area) and verify that no unexpected WARNING or FAILURE messages are reported.
    If FAILURE or WARNING messages are found then investigate and/or repair as appropriate.
   

PARTS NOTE:
https://support.us.oracle.com/handbook_internal/Systems/VSM6/components.html#SystemBoard

REFERENCE INFORMATION:

   SPARC T4-2 Service Manual
   http://docs.oracle.com/cd/E23075_01/pdf/E23078.pdf

   Oracle Integrated Lights Out Manager (ILOM) 3.0 Maintenance and Diagnostics - CLI and Web Guide
   http://download.oracle.com/docs/cd/E19860-01/E21449/E21449.pdf
   See also Oracle Integrated Lights Out Manager (ILOM) 3.0 Daily Management - CLI Procedures Guide
   http://download.oracle.com/docs/cd/E19860-01/E21446/E21446.pdf

   VSM6 Install, Configuration and Service Guide
   https://mosemp.us.oracle.com/handbook_internal/Systems/VSM6/docs.html

References

This solution has no attachment