Asset ID: |
1-71-1463087.1 |
Update Date: | 2016-07-28 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1463087.1
:
Pillar Axiom: Private Interconnect Module Replacement Procedure:ATR:1463087.1:1
Related Items |
- Pillar Axiom 300 Storage System
- Pillar Axiom 600 Storage System
- Pillar Axiom 500 Storage System
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: DISK-CAP VCAP
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU
Applies to:
Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
PIM Replacement Procedure
Goal
The purpose of this document is to outline the steps required to replace the Private Interconnect Module using Guided Maintenance on a Pillar Axiom Storage System
Solution
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED: Ability to log into the Axiom system GUI.
TIME ESTIMATE: 30 minutes
TASK COMPLEXITY: 1
FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
PROBLEM OVERVIEW: How to replace the Private Interconnect Module in an Axiom system.
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE
RESOLUTION ACTIVITY?: The component could be in warning or normal. The slammer control unit could be in a failed status.
WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:
NOTE: Please refer to <Document 1535352.1> "Pillar Axiom: 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: If the FRU is in a Disable state shown in the GUI, before replacing the part please clear the failure history by following the instructions in <Document 1952081.1> - Pillar Axiom: How to run ClearFailureHist in R4 and R5
See action plan below.
Procedure on How to Replace a Private Interconnect Module
Tip: When removing the cables in this task, label the cables to show which cable connects to which port on the private interconnect module.
- Within Guided Maintenance, click Next in the Prepare System page.
- When Guided Maintenance prompts you, remove the power cords from both power supplies of the target Control Unit (CU).
Important! Do not remove the power cords from the partner CU. That CU is currently supporting all the user data paths for this Slammer.
- Disconnect all Ethernet cables from the ETH ports in the target CU.
- Disconnect all FC cables from the FC and FS ports in the target CU. Fibre Channel (FC) cables are color coded and labeled and should match the FC labels attached below the port socket connectors.
- For HSSDC2 connectors: Carefully grasp the cable connector and, while pushing the connector gently into the socket, press the latch on the top of the connector to unlatch it.
- For SFP connectors: Carefully grasp the cable connector and, while pushing the connector gently into the socket, press the latch on the bottom of the connector to unlatch it.
Then, gently pull the connector straight out to release the connector with the cable.
- Loosen and disengage the two screws that secure the private interconnect module ejectors to the Slammer chassis.
- Press both ejectors down firmly to disengage the private interconnect module from the chassis midplane.
- Slide the private interconnect module out of the chassis and set it aside.
- Slide the replacement private interconnect module into the Slammer chassis and push the module firmly into place.
- Lift both ejectors up and press firmly to engage the private interconnect module with the chassis midplane.
- Engage and tighten the two screws that lock the ejectors to the Slammer chassis.
- Reconnect all FC cables to the FC and FS ports in the target CU. Gently insert the cables straight into the socket and use gentle pressure to latch them in place.
- Reconnect all Ethernet cables to the ETH ports.
- Attach power cords to both power supplies of the target CU.
- In the Guided Maintenance page, click Next.
Important! Visually inspect the replaced part and all other private interconnect modules and RAID CUs in the system. For every port that has a cable, the port LED should be in one of the following states (if this is not the case, contact the Support Center:
Green, which means the FC port is online.
Amber, which means the FC port has faulted or has been disabled.
Flashing green, which means the FC port is initializing.
OBTAIN CUSTOMER ACCEPTANCE
WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
1. Finish Guided Maintenance in the GUI to return the slammer control unit to normal status.
2. If applies, reactivate ASR.
PARTS NOTE: Please return any used/unused parts.
REFERENCE INFORMATION: See documents listed below.
References
<NOTE:1447672.1> - Pillar Axiom: How to use Guided Maintenance in R4 and How to identify a FRU
<NOTE:1447965.1> - Pillar Axiom: How to use Guided Maintenance in R5 and How to identify a FRU
<NOTE:1952081.1> - Pillar Axiom: How to run ClearFailureHist in R4 and R5
Attachments
This solution has no attachment