Exadata X7-2 Hardware
 
Zero Data Loss Recovery Appliance X7 Hardware
 

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

How to Replace an Exadata X7-2 Compute Node Server SAS Disk Data Cable Assembly

Applies to:

Goal

How to Replace an Exadata X7-2 Compute Node Server Internal SAS Cable.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
Exadata X7-2 Training

TIME ESTIMATE: 45 minutes

TASK COMPLEXITY: 2

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS

PROBLEM OVERVIEW: An Exadata X7-2 Compute Node Server SAS Disk Data Cable Assembly needs replacement

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

IMPORTANT NOTE TO TSC ENGINEER: CUT & PASTE the “CUSTOMER ACTIVITY” sections of the Pre-Replacement and Post-Replacement steps into a SR Note and ensure the customer is aware to do these steps prior to the scheduled field engineer activity, and during and after the replacement activity.

CUSTOMER ACTIVITY:

Offlining the disk cache and shutdown of the database node is required prior to the part replacement.

1. Shutdown the database services:

   If running Linux or Solaris native - follow Steps 1 to 7 of MOS Note:
      How to shutdown the Exadata database nodes and storage cells in a rolling fashion so certain hardware tasks can be performed. (Doc ID 1539451.1)

   If running OVM - follow Steps 1 to 4 of MOS Note:
      How to Shutdown and Startup Exadata database nodes running OVM (Doc ID 2367609.1)

2. Revert all the RAID disk volumes to WriteThrough mode to ensure all data in the RAID cache memory is flushed to disk and not lost if disconnect of the SuperCap occurs. As 'root' user, set all logical volumes cache policy to WriteThrough cache mode:

3. Verify the current cache policy for all logical volumes is now WriteThrough:

In the volume table, the "Cache" column should report as "NRWTD" where WT indicates WriteThrough.

4. Once all disks are offline and inactive, the customer may shutdown the Cell using the following command:

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

Prepare the Server for Service

The customer should have already prepared the server and powered it off. If not, provide them the instructions in the previous section.

1. Extend the server to the maintenance position
2. Disconnect the power cords from the power supplies.
3. Attach an anti-static wrist strap to your wrist and to a metal area on the chassis or the rack.
4. Remove the server top cover. Use a Torx T10 screwdriver to unlock the release button latch.

Removing the SAS Disk Data Cable Assembly

1. Disconnect both SAS cables from the disk backplane by pressing the latch on the cable connector and then pulling out the connector.

2. If there is a NIC card in PCIe slot 3, disconnect and label any network cables.

3. Remove the PCIe riser from slots 3 and 4.

a. Open the green-tabbed latch located on the rear of the server's chassis next to the PCIe slot 3 to release the PCIe card holding bracket.
b. To release the riser from the motherboard connector, lift the riser's green-tabbed release lever to the open position.
c. Grasp the riser with both hands and remove it from the server carefully.

4. Press the SAS cable connector latch to disconnect the cable from the RAID HBA card in PCIe slot 4.

5. Carefully remove the SAS cables from the server.

Installing the SAS Disk Data Cable Assembly

1. Carefully guide SAS cables along the left-side cable trough.

2. Connect the SAS cables into the disk backplane connectors.

3. Connect the SAS cables to the RAID HBA card in PCIe slot 4 as per the note above.

4. Install the PCIe riser for slots 3 and 4 into the server:

a. Raise the green-tabbed release lever on the PCIe riser to the open (up) position, and then gently press the riser into the motherboard connector until it is seated.
b. Ensure that the rear bracket on the internal SAS HBA card in PCIe slot 4 is connected to the slot in the server's chassis side wall. If the bracket is not connected, remove the riser and re-position it so that the rear bracket connects to the side wall, then gently press the riser into the motherboard connector.
c. Ensure the SAS cables and the super capacitor cable are routed to the channel on the chassis side wall.
d. Press the green-tabbed release lever on the PCIe riser to the closed (down) position.
e. To secure the PCIe card's rear bracket to the server, close the green-tabbed latch on the rear of the server's chassis.

5. If there is a NIC card in PCIe Slot 3, re-connect any network cables that were disconnected.

Return the Server to Operation

1. Install the server top cover. Use a Torx T10 screwdriver to lock the release button latch.
2. Reconnect the power cords to the server power supply and connect any other cables to their original locations.
3. Return the server to the normal rack position.
4. Once the power cords have been re-attached and the ILOM has booted you will see a slow blink on the green LED for the server. Power on the
server by pressing the power button on the front of the unit.
5. Connect to the server console via the ILOM and monitor the boot.
   By default the ILOM serial console displays the primary console output.
   In the event of unexpected boot behavior, it is advisable to connect to both ILOM serial and ILOM graphics consoles at the same time and monitor.

 

OBTAIN CUSTOMER ACCEPTANCE

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

FIELD SERVICE ENGINEER and CUSTOMER ACTIVITY:

1. Verify all expected hardware is visible to the server and the fault is cleared. Assistance from the customer for server login access will be required.

2. Verify all the expected disk devices are present. For Compute Nodes, there should be a single disk volume:

3. Verify the status of the Super Capacitor is visible and 'Optimal':

4. Set all logical drives cache policy to WriteBack cache mode:

5. Verify all expected logical drives are present and state 'Optl' (Optimal). For Compute Nodes there should be a single RAID5 volume:

In the volume table, the "Cache" column should report as "NRWBD" where WB indicates WriteBack.

6. Verify there are no outstanding alerts in the DB Node:

7. Re-enable and restart the Database services:

If running Linux or Solaris native - follow Steps 11 to 14 of MOS Note:
How to shutdown the Exadata database nodes and storage cells in a rolling fashion so certain hardware tasks can be performed. (Doc ID 1539451.1)

If running OVM - follow Steps 2 to 5 of MOS Note:
How to Shutdown and Startup Exadata compute nodes running OVM (Doc ID 2367609.1)

PARTS NOTE:

7340897 [F] SAS-3 Data Cable Assembly
- 72-Pin SFF-8643 to 42-Pin SFF-8611, 725mm
- 72-Pin SFF-8643 tp 42-Pin SFF-8611, 545mm

REFERENCE INFORMATION:

Oracle Exadata Database Machine Maintenance Guide: https://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-database-servers.htm#DBMMN22020

Oracle Server X7-2 Documentation https://docs.oracle.com/cd/E72435_01/index.html

How to shutdown the Exadata database nodes and storage cells in a rolling fashion so certain hardware tasks can be performed. (Doc ID 1539451.1)

How to Shutdown and Startup Exadata compute nodes running OVM (Doc ID 2367609.1)

This solution has no attachment