Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2067868.1
Update Date:2016-12-21
Keywords:

Solution Type  Technical Instruction Sure

Solution  2067868.1 :   MaxRep: How to Remove and Replace a Power Distribution Board in an Oracle MaxRep3 Engine  


Related Items
  • Pillar Axiom Replication Engine (MaxRep)
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: DISK-CAP VCAP
  •  


Instructions on how to replace a Power Distribution Board in an Oracle MaxRep3 Engine.

In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 3.0 and later
Information in this document applies to any platform.

Goal

This document outlines the steps to replace a Power Distribution Board (PDB) in an Oracle MaxRep3 Engine.

Solution

DISPATCH INSTRUCTIONS

- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:

Product knowledge, Oracle MaxRep

TIME ESTIMATE: 75 minutes

TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW:

What: A PDB in a MaxRep3 Engine has failed and needs to be replaced. 

Where: See "show /System/Open_Problems" output from ILOM. 

Why: A PDB in a MaxRep3 Engine has failed.

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?

Depending on the severity of the PDB failure, the MaxRep3 Engine with the PDB failure may just have a warning status because of incorrect temperatures being reported or it may have no power at all.  This procedure requires that the MaxRep3 Engine be powered off.

NOTE: Please review <Document 1942676.1> FS System: How to Disable Call Home to Prevent Automatic Service Request ASR Generation before proceeding with the procedure below. The steps contained therein are provided to allow an Administrator to de-activate a particular ASR enabled array while performing maintenance or troubleshooting. This will prevent any additional Service Requests from being created unnecessarily.

 

NOTE: The MaxRep3 Engine uses a quorum mechanism for Key Identity Properties (KIP). The quorum is comprised of the motherboard, disk backplane and power distribution board which are all encoded with the Product Serial Number (PSN) of the MaxRep3 Engine. At least two of these must agree on the correct PSN or the MaxRep3 Engine will NOT boot. So as to avoid this problem, this process has the user confirm the PSNs are in sync before attempting the replacement. NEVER replace one of these quorum devices if the PSNs are not in sync and NEVER replace two of these items at the same time.

QRC for this procedure:
MaxRep3 PDB QRC

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

  1. Confirm Product Serial Number Containers (PSNCs) are currently synchronized.
    1.  ssh to the ILOM of the MaxRep3 Engine.
    2. Enter restricted session mode and run the showpsnc command.

      -> set SESSION mode=restricted

      WARNING: The "Restricted Shell" account is provided solely
      to allow Services to perform diagnostic tasks.

      [(restricted_shell) ORACLESP-1312FMxxxx:~]# showpsnc
      Primary: fruid:///SYS/DBP
      Backup 1: fruid:///SYS/MB
      Backup 2: fruid:///SYS/PDB

      Element           | Primary           | Backup1           | Backup2
      ------------------+-------------------+-------------------+-------------------
      PPN                 70893370            70893370            70893370
      PSN                 1312FMxxxx          1312FMxxxx          1312FMxxxx  <=== Product Serial Numbers must match
      Product Name        Sun Netra X4270 M3  Sun Netra X4270 M3  Sun Netra X4270 M3
      [(restricted_shell) ORACLESP-1312FMxxxx:~]#
       


    3. If all 3 PSNs match, type exit twice to close the ssh session and proceed to step 2.
    4. If the Disk BackPlane 0 (DBP0) and Motherboard (MB) are the same but Power Distribution Board (PDB) is different, it is safe to proceed to step 2 since the PDB will be replaced.
    5. If any other condition exists, STOP!! and re-engage Oracle Support for steps to correct before proceeding to replace the failed PDB.

  2. Prepare the MaxRep3 Engine for Service Procedure.
    1. Using the ILOM interface, confirm the failed part and location:
      • Browser: point a browser at the ILOM IP address and select Open Problems in the navigation tree on the left.
      • CLI: ssh to ILOM IP address and execute "show /System/Open_Problems"
    2. Disable Call-Home to prevent spurious alerts (see <Document 1942676.1> FS System: How to disable Call Home to prevent Automatic Service Request ASR Generation).
    3. Shutdown the MaxRep3 Engine (see <Document 2066803.1> MaxRep: How to Perform a Graceful Shutdown of the Oracle MaxRep3 Engine).
    4. Use ESD precautions.

  3. Access the failed PDB.
    1. Deploy the anti-tip legs in the front of the rack.
    2. Slide the MaxRep3 Engine into the service position.
    3. Unplug both power cords.
    4. Loosen the two captive screws in the rear of the top cover.
    5. Slide the top cover back and remove.
    6. Unseat both power supplies.

      NOTE: It is recommended to only unseat both power supplies rather than completely remove them.
       
    7. Lift Drive Compartment into service position.
      1. Unplug the cables connected to the Drive Compartment - suggest that they be labeled to make reconnections easier.
      2. Loosen the four captive screws that secure the Drive Compartment to the MaxRep3 Engine chassis and tilt it up into the service position.
    8. Remove air duct.
    9. Remove fan tray.
      1. Remove all 5 fan modules.
      2. Remove fan tray.
    10. Remove risers.
      1. Loosen 2 captive screws in each riser.
      2. Lift the riser up and clear of the MaxRep3 Engine chassis.

      NOTE: it is not necessary to remove the PCIe cards from the risers nor is it required to unplug any cables connected to the PCIe cards in those risers.

    11. Remove motherboard.
      1. Loosen the single captive screw that secures the PDB duct to the MaxRep3 Engine chassis and lift it free.  Be sure to guide the USB cable out of the slot in the PDB duct.
      2. Remove the 4 screws that secure the PDB GND and +12V buses to the motherboard.
      3. Loosen the single captive screw at the front of the motherboard.
      4. Using the two green plastic handles, gently push the motherboard towards the rear until it is free of the chassis (only needs to move about 1/2 an inch).


      NOTE: Removal of CPUs, Heatsinks, DIMMs, or other cables from the motherboard is not necessary since it is not being replaced.
        

  4. Remove the failed PDB.
    1. Unplug the ribbon cable from the PDB.
    2. Remove the 2 screws that secure the PDB to the chassis.
    3. Using the green plastic handles, lift the motherboard up so that you can slide the GND and +12V buses from under the motherboard.

  5. Install the replacement PDB.
    1. Slide the two bus arms under the motherboard and into their fabricated locations.  If necessary use the green plastic handles on the motherboard to lift it up slightly and out of the way.
    2. Tighten the 2 screws that secure the PDB to the chassis.
    3. Plug in the ribbon cable to the PDB.

  6. Reassemble MaxRep3 Engine components.
    1. Reinstall the motherboard
      1. Using the 2 green plastic handles, slide the motherboard forward to its original position.  Take care to align the four holes that connect it to the PDB as well as the alignment tabs in the rear.
      2. Secure motherboard by tightening captive screw in the front of the motherboard.
      3. Secure the PDB buses to the motherboard using the 4 screws previously removed.
      4. Install the PDB duct in place and secure to chassis with captive screw.  Be sure to route the USB cable through the slot on the top.
    2. Reinstall the risers.
      1. Each riser has 1 alignment hole, 2 screws and a PCIe connector.  Align the PCIe connector to the motherboard first and then adjust for the others before pushing the PCIe connector into the PCIe slot.
      2. Secure in place using the two captive screws.
    3. Reinstall fan tray and Fans.  Be sure to properly route the alarm and and power cables (left side) and the PDB cable (right side).
    4. Reinstall the air duct
    5. Return Drive compartment to its normal position.
      1. Tilt the Drive Compartment back into its normal position, being careful not to pinch any cables.
      2. Secure in place using the 4 captive screws.
      3. Reconnect (left to right) the power cable from the motherboard and the SAS cables from the internal SAS HBA.
    6. Reseat both power supplies.
    7. Close the top cover.
    8. Tighten the two captive screws in the rear of the top cover.

  7. Return the MaxRep3 Engine to operation.
    1. Plug in both power cords.
    2. Return the MaxRep3 Engine to the rack position.
    3. Return the anti-tip legs to their normal position.
    4. Once the MaxRep3 Engine ILOM has completed its reboot, repeat step 1 to verify that PSN of the replacement PDB is synchronized with the other two quorum devices.

  8. After 4-5 minutes, the MaxRep3 Engine should have completed its boot sequence. Access the User Interface and resync any Protection Plans that require it (see <Document 2066803.1> MaxRep: How to Perform a Graceful Shutdown of the Oracle MaxRep3 Engine).
  9. When finished, re-enable Call-Home.


OBTAIN CUSTOMER ACCEPTANCE


WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

Confirm that the replacement PDB was successful. The Warning under Status Summary in the Oracle FS System Manager GUI associated with it and the Open Problem in the ILOM both should be gone.

REFERENCE INFORMATION:

 From the Oracle Help Center: http://docs.oracle.com/en/storage/#fla select the Oracle MaxRep for SAN Documentation Library for more information.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback