Exalogic: Reference Guide On Detailed Steps For Motherboard Replacement Of Exalogic Compute Node
(Doc ID 2631625.1)
Last updated on NOVEMBER 14, 2022
Applies to:
Oracle Exalogic Elastic Cloud Software - Version 2.0.3.0.0 and laterLinux x86-64
Oracle Virtual Server x86-64
This MOS Note applies to following Exalogic Versions.
Exalogic Linux Physical racks: 2.0.3.X.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.X, 2.0.6.4.X
Exalogic Linux Virtual racks: 2.0.6.0.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.X, 2.0.6.4.X
Exalogic Solaris Physical racks: 2.0.4.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.X
Purpose
This Note provides detailed steps involved when replacing the Motherboard of Exalogic Compute nodes.
Below are Main high level tasks involved in Exalogic Compute nodes motherboard replacement. You can find details on who is responsible for each of these tasks as well (whether it is Customer/Oracle Field Engineer responsibility)
☀ SECTION A: PRE-REQUISITE MANDATORY PREPARATION ACTIONS: Backups and Configuration Information Capture of Compute Node before Motherboard replacement (Customer Responsibility).
☀ SECTION B: PRE-WORK BEFORE MOTHERBOARD REPLACEMENT ACTIVITY: Prepare Compute Node for Motherboard Replacement (Customer Responsibility).
☀ SECTION C: MOTHER BOARD PHYSICAL REPLACEMENT: Physical Replacement of Motherboard (Oracle Field Engineer Responsibility).
☀ SECTION D: POST-WORK AFTER MOTHERBOARD REPLACEMENT ACTIVITY: Post Motherboard Replacement Steps For putting back the Compute Node into Service (Customer Responsibility).
Detailed steps are available for each of the above Sections in this MOS Note under Details section of this MOS Note.
Scope
Steps in this Note are applicable for use case of Motherboard replacement of Exalogic Compute Nodes.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| SECTION A: PRE-REQUISITE MANDATORY PREPARATION ACTIONS: Backups and Configuration Information Capture of Compute Node before Motherboard replacement (Customer Responsibility) |
| STEP A.1 - Take backup of Compute Node ILOM using Exabr on which Motherboard has to be replaced. |
| STEP A.2 - Take backup of Compute Node Host OS using Exabr. |
| STEP A.3 - Collect ILOM snapshot from the Compute Node for which Motherboard is being replaced. |
| STEP A.4 - Capture sosreport from Linux Compute Node for which Motherboard is being replaced (Applies to Only Linux Physical and Linux Virtual racks) |
| STEP A.5 - Capture Explorer data from Solaris Compute Node for which Motherboard is being replaced (Applies to Only Solaris Physical racks) |
| STEP A.6 - Take backup of Exalogic control stack using Exabr (Applies to only Exalogic Virtual racks) |
| STEP A.7 - Make a note of Serial Number of Compute Node for which MB is being replaced. |
| STEP A.8 - Make a note of the Rack Serial Number and Hardware model of Compute Node for which MB is being replaced. |
| STEP A.9 - Make a note of the ILOM firmware version of the Compute Node for which Motherboard is being replaced. |
| STEP A.10 - Make a note of the ILOM SP Network Settings of the Compute Node for which MB is being replaced. |
| STEP A.11 - Make a note of the Motherboard MAC address of the Compute Node for which Motherboard is being replaced. |
| STEP A.12 - Capture ifconfig output of Compute Node Host OS for which Motherboard is being replaced. |
| STEP A.13 - Take backup of BIOS settings of Compute Node for which Motherboard is being replaced. (Applies to only Exalogic Linux Physical and Virtual racks). |
| X2-2 Compute nodes |
| X3-2, X4-2, X5-2 & X6-2 Compute Nodes |
| _________________________________________________________________________________________________________________________________________________________ |
| SECTION B: PRE-WORK BEFORE MOTHERBOARD REPLACEMENT ACTIVITY: Prepare Compute Node for Motherboard Replacement (Customer Responsibility) |
| STEP B.1 - Bring Down the Applications/Guest vServers running on the Compute Node for which Motherboard is being replaced. |
| Exalogic Linux Physical & Solaris Physical Compute Node |
| Exalogic Virtual Dom0 OVS Compute Node |
| STEP B.2 - Remove Dom0 Compute Node from OVS Server Pool and from OVM Manager (Step applies to only Virtual Dom0 Compute Node) |
| a. Move the Dom0 OVS Compute Node to "Unassigned Servers' folder. |
| b. Check removed Dom0 Compute Node is not presented in Repository. |
| c. Check removed Dom0 Compute Node is not selected in "Generic Network File System" under Storage tab. |
| d. Delete the Dom0 Compute Node from "Unassigned Servers" |
| STEP B.3 - Remove the Dom0 Compute Node Asset from EMOC (Step applies to only Virtual Dom0 Compute Node) |
| _________________________________________________________________________________________________________________________________________________________ |
| SECTION C: MOTHER BOARD PHYSICAL REPLACEMENT: Physical Replacement of Motherboard (Oracle Field Engineer Responsibility) |
| _________________________________________________________________________________________________________________________________________________________ |
| SECTION D: POST-WORK AFTER MOTHERBOARD REPLACEMENT ACTIVITY: Post Motherboard Replacement Steps For putting back the Compute Node into Service (Customer Responsibility) |
| STEP D.1 - Verify the Firmware version of ILOM of Compute for which Motherboard is replaced to make sure it is same version as before Motherboard replacement. |
| STEP D.2 - Verify the ILOM SP Network Settings of Compute for which Motherboard is replaced to make sure they are same as before Motherboard replacement |
| STEP D.3 - Make a Note of the latest FRU MAC address which has to be used for Management Networks from ILOM of Compute Node for which MB has been replaced. |
| Exalogic Linux Physical Compute Node |
| Exalogic Virtual Dom0 Compute node. |
| STEP D.5 - Validate the BIOS Settings of Exalogic Compute Node for which Motherboard is replaced (Applies to only Exalogic Linux Physical and Virtual racks). |
| 2.0.6.4.X Exalogic Image version |
| 2.0.3.X.X, 2.0.6.0.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.X Exalogic Image Version |
| STEP D.6 - Exalogic Virtual Racks ONLY. Rediscover back the Dom0 Compute Node (for which Motherboard is replaced) into EMOC (Applies to Linux Virtual racks only) |
| STEP D.7 - Exalogic Virtual Racks ONLY. Rediscover back Dom0 Compute Node (for which Motherboard is replaced) in OVMM and add it OVS Server Pool. (Applies to Linux Virtual racks only) |
| a. Rediscover Dom0 Compute Node using IP Address. |
| b. Add the newly discovered Dom0 Compute node back to OVS Pool <<<< Skip this Step if CN is already part of OVS Pool >>>> |
| c. Refresh the Repository and check if Repository is presented to newly discovered Compute Node |
| d. Check newly discovered Dom0 Compute Node is selected in "Generic Network File System" under Storage tab |
| e. Check the newly discovered Compute Node is configured OK from OVM Manager BUI. |
| f. Validate all the OVS Services are UP and running on newly discovered Compute node. |
| STEP D.8 - START APPLICATIONS/VSERVERS (VM's) ON COMPUTE NODE: Bring UP Applications/vServers (VM's) back on the Compute Node which came back up after reboot on which firmware version was downgraded. |
| Exalogic Linux/Solaris Physical Compute Node (without Virtualization) |
| Exalogic Linux Virtual rack: |
| References |