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-1529636.1
Update Date:2016-01-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  1529636.1 :   Mx-32 - How to Replace a Faulty Scalability Switch Board (SSB)  


Related Items
  • SPARC M5-32
  •  
  • SPARC M6-32
  •  
  • Oracle SuperCluster M6-32 Hardware
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
  •  




In this Document
Goal
Solution


Oracle Confidential INTERNAL - Do not distribute to customer (OracleConfidential).
Reason: FRU CAP

Applies to:

SPARC M5-32 - Version All Versions and later
SPARC M6-32 - Version All Versions and later
Oracle SuperCluster M6-32 Hardware - Version All Versions and later
Information in this document applies to any platform.

Goal

CAP PROBLEM OVERVIEW: Mx-32 -  Faulty Scalability Switch Board (SSB)


To report errors or request improvements on this procedure, please go to My Oracle Support, and put a comment on Doc ID: 1529636.1


 

ESD Caution:
  • Circuit boards and drives contain electronic components that are  extremely sensitive to static electricity. Ordinary amounts of static electricity from clothing or the work environment can destroy the components located on these boards. Do not touch the components along their connector edges.
  • Use a Antistatic Wrist strap. Attach one end of the strap to your wrist and the other end to the chassis, depending on what type of strap you use, with the adhesive end or the metal plug.
  • Use an Antistatic Mat. Place ESD-sensitive components such as motherboards, memory, and other PCBs on an antistatic mat.

 

Contamination Caution:
  • Dust particles of packaging material are number one cause of datacenter contamination. Make sure to remove all packaging material, up to the ESD safe packaging material, while still being outside the datacenter.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:  Mx-32 Product Training/Experience

TASK COMPLEXITY: 2

TIME ESTIMATE: 120 minutes HOT replacement

FIELD ENGINEER INSTRUCTIONS

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? : Blue Ready-to-Remove LED must be lit on the Scalability Switch Board (SSB).

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

1. Determine whether the SSB can be stopped without stopping Dynamic PDomains:
-> show /SYS/SSBx current_config_state
  /SYS/SSBx
     Properties:
            current_config_state = State

  • If state = Disabled, go to Step 5. You can remove the SSB without halting the PDomains.
  • If state = Enabled, go to Step 2. Dynamic PDomains might have to be halted.

2. Determine what types of PDomains are in the server:
   a. For each PDomain, determine whether it is an expandable PDomain:
   -> show /Servers/PDomains/PDomain_x/HOST/ expandable
      /Servers/PDomains/PDomain_x/HOST
         Properties:
               expandable = State

   The expandable property has two possible states, true or false.
   b. Repeat Step a for the remaining PDomains in the server.

3. Based on the results that you found:

  • If state = false for all PDomains, go to Step 5. You do not need to stop the PDomains.
  • If state = true for any one or more PDomains, go to Step 4. You must stop PDomains that are expandable


4. For any expandable PDomain that you identified in Step 3:
   a. Stop the expandable PDomain.
   -> stop /Servers/PDomains/PDomain_x/HOST
   Are you sure you want to stop
   /Servers/PDomains/PDomain_x/HOST/console (y/n) ? y
   Stopping /Servers/PDomains/PDomain_x/HOST

b. Repeat for any remaining expandable PDomains.


5. Light the blue Ready to Remove LED on the target SSB.
   a. Light the LED:
   b. Verify that the LED is lit:
   -> set /SYS/SSBx prepare_to_remove_action=true
   -> show /SYS/SSBx prepare_to_remove_status
          prepare_to_remove_status = Ready

Note – If you change your mind and decide not to remove this component, execute
the return_to_service_action command from the above path.

6. Use a grounding strap to protect the equipment from ESD damage.

7. SSB are at the front of the server.  Locate the lit blue Ready to Remove LED on the target SSB.

8. Remove the Faulty SSB:

  • Squeeze the locks on the extraction levers and open the extraction levers to the horizontal position.
  • Pull the SSB out of the cabinet.

7. Unpack the replacement SSB from its ESD safe packaging.

8. Pack the faulty SSB into its ESD safe packaging.

9. Install the replacement SSB:

  • Open the extraction levers fully.
  • Insert the replacement SSB until the extraction levers start to close.
  • Close the extraction levers to lock the SSB in the slot.

10. Restart PDomains to utilize the replaced SSB

If the SSB was found disabled in Step 1 all expandable PDomains must be stopped and then restarted to utilize the replace SSB.

All expandable PDomains were identified in Step 2.  Stop all expandable Pdomains (all most be stopped to reconfigure the 12 SSB).
-> stop /Servers/PDomains/PDomain_x/HOST
After all are stopped, you may proceed to restart them.  This will configure the replaced SSB into the running configuration.
-> start /Servers/PDomains/PDomain_x/HOST

NOTE: Alternatively, you may stop and start the full System (-> stop /System, -> start /System)

If the SSB was found enabled in Step 1 and PDomains were stopped in Step 3, restart the stopped PDomain.
For each of the expandable PDomain stopped in Step 3, restart the Pdomain.
-> start /Servers/PDomains/PDomain_x/HOST

11. Prepare the faulted SSB outside the datacenter for return to Oracle.

 

OBTAIN CUSTOMER ACCEPTANCE

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

Restart software applications per applicable administration guides to resume system operation.

 

======================== Other info =====================

REFERENCE INFORMATION:  Service Manual: https://www.oracle.com/technetwork/documentation/oracle-sparc-ent-servers-189996.html


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