Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

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

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: changed distribution to partner

Applies to:

Goal

The purpose of this document is to outline the steps required to replace a Pilot Control Unit on a Pillar Axiom Storage System.

Solution

 DISPATCH INSTRUCTIONS
   WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?: Being able to identify and replace a Pilot Control Unit
   TIME ESTIMATE: 60 minutes
   TASK COMPLEXITY: 2

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS: Replace a Pilot Control Unit.
   PROBLEM OVERVIEW:
   WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?: The FRU can be Warning/Failed/Critical status
   WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE?:

Refer to the Pillar Axiom Service Guide about Pilot Control Unit replacement.

OBTAIN CUSTOMER ACCEPTANCE
   WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?: Replace Pilot Control Unit.

Please read this entire procedure in advance before attempting so you are familiar with the process and concepts. This action plan is to instruct you on how to remove and replace a Pilot Control Unit.

Identify a Pilot Control Unit (for R4 and below versions only)

1. Remove the Pilot bezel.
2. Click the Health icon in the top context pane.
3. Click the Pilot link in the left navigation pane.
4. For the target Pilot Control Unit (CU), click Identify.
   Note: The drive LED on the target CU will light solid for one minute.  If there is heavy drive activity on the Pilot CU, use both Identify and Reverse Identify to determine the correct CU.
   A very reliable method to identify the Pilot CU is to ping the unique address of each Pilot such as (10.0.0.3 and 10.0.0.4) and momentarily disconnect the management Ethernet connector out of the port make sure you replace the correct CU.  When the ping to the specific address stops, identify the correct Pilot CU.
   The IP addresses for CU 0 and CU 1 of the Pilot are available on the Global Settings Networking screen, which displays these IP addresses on the Modify Network Settings screen. If Call-Home is enabled, the Oracle Customer Support provides the IP address from the Call-Home logs.
5. Click Finish.

NOTE: For Axiom R5 versions you will have to identify the pilot CU based on the serial number, this can also be done on Axiom R4 (and below) versions. The serial number sticker is physically located behind the pilot, and can be compared with the serial number shown in the GUI for identification.

To find the serial number in the GUI for Axiom R5:
Log into the Axiom Storage Services Manager and navigate to "Monitor" tab -> under "Hardware" click on "Pilots", in the main screen you will find the serial number of each Pilot.

To find the serial number in the GUI for Axiom R4 and below versions:
Log into the GUI and navigate to "Health" tab -> under "Hardware" click on "Pilot", in the main screen you will find the serial number of each Pilot.

If there are any problems identifying a pilot CU, please contact Oracle Customer Support.

About Pilot Control Unit Removal

Before you remove a Pilot control unit (CU), label each cable that you detach
from the CU:

1. One power cord to the power supply.
2. One serial null-modem cable to the serial port. This cable supports the heartbeat between the two Pilot CUs.
3. Two Ethernet cables to the ETH 0 and ETH 1 ports. These cables support the private management network.
4. One Ethernet cable to the MGMT port. This cable supports the management console on the public LAN.

TIP: The label should note where the cable needs to be reattached on the replacement CU.

Remove a Pilot Control Unit (CU)
Important! Remove power only from the Pilot CU that you want to replace.

When removing power from an active Pilot control unit (CU), the GUI shows a Warning state for that CU and one of the Slammer CUs. The Slammer CU shows a Warning state because it lost its connection to the Pilot CU that was taken offline.  This is the expected state for the Slammer CU in that case. However, the Pilot CU must be brought back up as soon as possible to avoid any potential problems.

1. If you have not already done so, remove the Pilot bezel.
2. Use Guided Maintenance to identify the target Pilot CU. (For R4 and below versions only, for R5 identify the pilot based on serial number).
3. Detach the power cable from the target CU.
4. In the back of the target CU, detach the Ethernet cables from ports ETH 0, ETH 1, and MGMT.
5. In the back of the target CU, detach the serial null-modem cable from the serial port.
6. In the front of the CU, remove the two screws (one on each side) that secure the CU ears to the rack rails.
7. Grasp the bezel adapter flange and pull gently to extract the CU.
8. Set the Pilot CU aside on an anti-static surface.

About Pilot Control Unit Insertion

IMPORTANT!  Do NOT apply power to the new Pilot CU until the Pilot CU to CU Ethernet, the Serial Cable, and the External Management Ethernet cables are securely attached.  If you apply AC power, before all these cables are attached, the new Pilot CU will become pilot1 (CU0) and may attempt to take control of the Axiom--resulting in a System Down.  These cables are used to negotiate control of the Axiom, and if they are not attached when the Pilot CU is powered on, it will assume it is the only Pilot CU. 

When you replace a Pilot CU, the surviving Pilot CU updates the replacement CU with the following information:

• Linux operating system.
• Pillar Axiom software that includes current, previous, and staged software and firmware for all components.
• Pilot identity, pilot1 or pilot2 hostname
• Public and private IP configuration, including IP addresses and gateways.

Important! The above information update completes satisfactorily only if you have not powered on the replacement CU prior to cabling it to the serial link and the private management Ethernet and serial port of the surviving Pilot CU.

When you cable the Pilot CU replacement, refer to the labels on the Ethernet cables to guide you.

For complete information on how to cable a Pilot CU into the system, refer to the Pillar Axiom Cabling Reference Guide.

Insert a Pilot Control Unit (CU)
CAUTION:
Because a Pilot CU automatically powers on as soon as AC power is available, do not attach the AC power cord to the replacement CU until instructed to do so. If you power on the Pilot CU replacement before you perform these actions, the replacement CU will not be configured correctly. If this occurs, immediately unplug the AC power cord from the new Pilot and contact the Oracle Customer Support.

1. Place the Pilot CU into the empty set of Pilot rack rails.  Hold the Pilot CU horizontally to align and engage the support brackets on each side of the CU with the rack rails.
2. Slide the Pilot CU all the way in until the ears on the bezel adapter bracket seat against the rack rail ears.
3. Insert the two 10-32 screws into the holes in the bezel adapter ears (one on each side) and secure the CU to the rack rails.
4. In the back of the CU, attach the serial null-modem cable to the bottom serial port.
5. In the back of the Pilot CU replacement, attach the Ethernet cables to ports ETH 0, ETH 1, and MGMT.
6. Attach the AC power cable to the CU replacement.
7. On the front of the Pilot CU replacement, check whether the power LED is lit.
   If the power LED is lit, wait until the system disk LED blinks before continuing.
   Note: Contact the Oracle Customer Support if the system disk LED does not begin to blink within a few minutes.
   If the power LED is not lit, press and hold the power button on the front of the Pilot CU for two to five sec. Select one of the following options:
   
   
1. If the power LED lights, wait until the system disk LED blinks before continuing.
   NOTE: Contact the Oracle Customer Support if the system disk LED does not begin blinking within a few minutes.
2. If the power LED does not light, contact the Oracle Customer Support.
   Note: The front and back network activity LEDs and internal LEDs (on some Pilots) may blink even though the power is off.
   Note: It is normal for the Pilot CU to restart up to three times while the system attempts to accept it. The entire restart process can take up to half an hour. If the new Pilot CU does not display a green LED light and is not in normal state within an hour, or if you experience any data access disruption, contact the Oracle Customer Support for assistance.
8. Add the Pilot bezel.
   Note: Insert the USB cables into the front of each Pilot CU as marked. Ensure that the cable arm has no interference when attaching the bezel.
9. Log into the GUI, click the Support icon, and select Software Modules to verify that only one version of Pilot OS and Pilot Software displays.
   IMPORTANT! If you see two different software version numbers for either software component, contact the Oracle Customer Support for recovery assistance.

If applicable, reactivate ASR.

PARTS NOTE:

REFERENCE INFORMATION:

This solution has no attachment