Zero Data Loss Recovery Appliance X6 Hardware
 
Exadata X5-2 Eighth Rack
 
Exadata X5-2 Hardware
 
Exadata X5-2 Full Rack
 
Exadata X6-2 Hardware
 
Exadata X5-2 Quarter Rack
 
Exadata X5-2 Half Rack
 
Zero Data Loss Recovery Appliance X5 Hardware
 

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

In this Document

Goal

Solution

References

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

Applies to:

Goal

 How to Replace a Faulty RAID HBA on Exadata successfully in Exadata X5-2/X6-2 Compute Node

Solution

 DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?: Exadata Trained

TIME ESTIMATE: 90 Minutes
TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
PROBLEM OVERVIEW: A faulty RAID HBA in an Exadata X5-2/X6-2 Compute node has been diagnosed as needing replacement

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

- The server that contains the faulty HBA should have its services offline and system powered off.

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

The instructions below assume the customer DBA is available and working with the field engineer onsite to manage the host OS and
DB/ASM services. They are provided here to allow the FE to have all the available steps needed when onsite, and can be done by the
FE if the customer DBA wants or allows or needs help with their steps.

Step A. Pre-Steps to shutdown the node for servicing:

1. For Extended information on this section, check MOS Note:
ID 1093890.1 Steps To Shutdown/Startup The Exadata & RDBMS Services and Cell/Compute Nodes On An Exadata Configuration.

For a documentation reference, in the Exadata Maintenance Guide, use the section of chapter 1 "General Maintenance Information"

titled "Non-Emergency Power Procedures" section "Powering Off Oracle Exadata Rack" sub-section "Powering off Database Servers" available on the customer's cell
server image in the /opt/oracle/cell/doc directory, or internal to Oracle here:
http://amomv0115.us.oracle.com/archive/cd_ns/E50790_01/doc/doc.121/e51951/general.htm#DBMMN21014

It is highly recommended to make and verify a backup of all disk partitions prior to RAID HBA replacement.

if running OVM then go to section "For Compute Node running OVM" - for non-OVM proceed as follows:

 
Shutdown crs


i. As root user do the following to stop crs and disable autostart of crs on reboot:

where GI_HOME environment variable is typically set to “/u01/app/11.2.0/grid” but will depend on the customer's environment.

In the above output the “1” of “+ASM1” refers to the DB node number. For example, Db node #3 the value would be +ASM3.

ii. Validate CRS is down cleanly. There should be no processes running.
  

For Compute Node running OVM proceed as follows:

If there are any concerns engage EEST engineer.

The customer should perform the following:

(a) See what user domains are running (record result )

Connect to the management domain (domain zero, or dom0).

  This is an example with just two domains and the management domain Domain-0

connect to each domain  using the command

where domainname would be dm01db01vm01 or dm01db01vm02 if using the above examples.

Shut down any instances of crs ,refer to the example above in previous section "shutdown crs" in all user domains

Press CTRL+] to disconnect from the console.

(b)Shutdown all user domains from dom0

(c) See what user domains are running (should be only Domain-0)

(d) Disable user domains from auto starting during dom0 boot after HBA has been replaced. 

3. 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
when replacement of the HBA occurs. Set all logical volumes cache policy to WriteThrough cache mode:

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

4. The customer can now shutdown the server operating system:

5. The field engineer can now slide out the server for maintenance. Do not remove any cables prior to sliding the server forward, or the
loose cable ends will jam in the cable management arms (CMA). Ensure all customer-added data network cables are properly dressed
into the CMA Take care to ensure the cables and CMA is moving properly.
Remember to disconnect the power cords before opening the top of the server.

Step B. Physical RAID Card replacement

Reference links for Service Manual:
X5-2 DB’s: ( http://docs.oracle.com/cd/E41059_01/html/E48312/napsm.html#scrolltoc )

Remove the old HBA PCI Card

1. Remove the IB cables from the IB card in slot 3 above the HBA making a note of which port each cable goes into so
they can go back into the same port.

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

(a) Open the green-tabbed latch located on the rear of the server chassis next to
PCIe slot 3 to release the rear bracket on the PCIe card

(b) To release the riser from the motherboard connector, lift the green-tabbed release
lever on the PCIe riser to the open position.

(c) Slide the plastic PCIe card retainer, which is mounted on the side of the chassis,
toward the front of the server to release the card(s) installed in the riser .

(d) Grasp the riser with both hands and remove it from the server.

(e) Disconnect the SAS storage drive (HDD) cables from the internal HBA card
installed in PCIe slot 4 .
(f) Disconnect the super capacitor cable from the internal HBA card in slot 4

(g) Disconnect the rear bracket attached to the PCIe card from the rear of the
PCIe riser.

Install the new HBA PCI Card

Reverse the removal instructions, taking care to get the cables re-connected to the same ports they were removed from. If reversed,
this may affect disk slot mappings.
Take care  to also put the IB cables back into the original ports, as well, in the correct orientation. IB cables are factory
labeled with the port identification where port 2 is the port nearest the PCI connector, and port 1 is the port near the top side of the
card. The cables should be inserted with the latch release tab on the down side, so they fully seat and latch. If inserted upside down,
they will not fully seat or latch.

Power on :
1. Once the power cords have been re-attached, slide the server back into the rack.
2. Once 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.

Server Services Startup Validation:

DB Node Startup:

1. As the system boots the hardware/firmware profile will be checked, and either a green "Passed" will be displayed, or a red "Warning"
that the check does not match if the firmware on the HBA is different from what the image expects.
If the check passes, then the firmware is correct, continue to step 2.

If the check fails, then an attempt will be made to automatically update the firmware ,  a subsequent reboot will occur. Monitor to ensure this occurs properly.

If the check or update still fail, then:
a) Login as root at the OS login prompt.
b) Run the following to update the RAID HBA to the correct supported firmware for the image:

c) After the firmware updates, the server will reboot again. The disk volumes should remain intact and boot up to the OS again.

2. After the OS is up, login as root and validate the physical and logical volumes are seen properly from the new RAID HBA in the OS,
for the configuration that it should be for the DB node and that the supercap is seen:

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

Verify the current cache policy for all logical drives is now using WriteBack cache mode:

4. CRS services should now be started.

"DB Node Startup Verification" - for compute node NOT running OVM ,for OVM refer to next section.

Startup CRS and re-enable autostart of crs. After the OS is up, the Customer DBA should validate that CRS is running. As root execute:

where GI_HOME environment variable is typically set to “/u01/app/11.2.0/grid” but will depend on the customer's environment.
In the above output the “1” of “+ASM1” refers to the DB node number. For example, Db node #3 the value would be +ASM3.
Example output when all is online is:

2. Validate that instances are running:

It should return a record for the ASM instance and a record for each database.

For Compute Node running OVM

If the customer requires assistance please ask them to contact EEST engineer or parent case owner.

Once the compute node has booted ,re-enable user domains to autostart during Domain-0 boot.

Startup all user domains that are marked for auto start

See what user domains are running (compare against result from previously collected data)

if any not auto-started then Startup a single user domain

 Check that crs has started in user domains ,refer to previous section "DB Node Startup Verification"

4. Verify also the InfiniBand links are up at 40Gbps as the cables were disconnected:

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

- Verify that HW Components and SW Components are returned to properly functioning state with server up and database services
operating on DB Servers

PARTS NOTE:

REFERENCE INFORMATION:

1093890.1 Steps To Shutdown/Startup The Exadata & RDBMS Services and Cell/Compute Nodes On An Exadata Configuration.

Service Manual's:
X5-2 DB’s: ( Service Manual's:
X5-2 DB’s: ( http://docs.oracle.com/cd/E41059_01/html/E48312/napsm.html#scrolltoc )

This solution has no attachment