10/25/2019 Document

Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

How to Replace an Exadata X7/X8 Storage Cell Server Motherboard (Doc ID 2375697.1)

In this Document

Goal
Solution
References

APPLIES TO:

Exadata X7-8 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X7-2 Hardware - Version All Versions to All Versions [Release All Releases]
Zero Data Loss Recovery Appliance X7 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster M8 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X8-2/X8M-2 Hardware - Version All Versions and later
x86_64

GOAL

How to Replace an Exadata X7-2/X8-2 Storage Cell Server Motherboard

SOLUTION

DISPATCH INSTRUCTIONS

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

TIME ESTIMATE: 120 Minutes

TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: An Exadata X7-2/X8-2 Storage Cell Server Motherboard 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 storage cell is required prior to the part replacement.

1. Complete Steps 1 to 5 of MOS Note ID 1188080.1 “Steps to shut down or reboot an Exadata storage cell without
affecting ASM”

Where noted, the SQL, CellCLI and commands under ‘root’ should be run by the Customers DBA, unless the Customer
provides login access to the Field Engineer.

These steps are also provided in the documentation:

https://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm#DBMMN21128

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 1/10
10/25/2019 Document

2. On Storage Cells with High Capacity disk drives, 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 RAID HBA occurs.

a. As 'root' user, set all logical volumes cache policy to WriteThrough cache mode:

# /opt/MegaRAID/storcli/storcli64 /c0/vall set wrcache=WT

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

# /opt/MegaRAID/storcli/storcli64 /c0/vall show

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

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

# shutdown -hP now

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. Log into the ILOM check the fruid container values and sync them if needed. To avoid mismatched fruid values causing
a failure after a motherboard replacement the fruid data should be confirmed to have matching data. The Motherboard is
the Backup1 container so the Primary (DBP) and Backup2 (PS0) must have valid values that are the same, in order for the
replacement motherboard's container to be updated to the correct values automatically.

Go into ILOM restricted mode and use the showpsnc command to check this:

-> set SESSION mode=restricted

WARNING: The "Restricted Shell" account is provided solely

to allow Services to perform diagnostic tasks.
[(restricted_shell) <HOSTNAME>-ilom:~]# showpsnc
Primary: fruid:///SYS/DBP
Backup 1: fruid:///SYS/MB
Backup 2: fruid:///SYS/PS0

Element | Primary | Backup1 | Backup2

------------------+-------------------+-------------------+-------------------
PPN 7338449 7338449 7338449
PSN XXXXNMXXXX XXXXNMXXXX XXXXNMXXXX
Profile 0x00010000 0x00010000 0x00010000
Product Name ORACLE SERVER X7-2L ORACLE SERVER X7-2L ORACLE SERVER X7-2L
RFID SN 341A583DE5800000000233C6 341A583DE5800000000233C6
341A583DE5800000000233C6
[(restricted_shell) <HOSTNAME>-ilom:~]#

The above example shows a system with all three containers properly in sync. If the output from the system does not
show all of the containers with matching values then you should reset the SP and then re-check the values again. An ILOM
reset will attempt to auto-populate the matching values if one container is out of sync.

-> reset /SP

Are you sure you want to reset /SP (y/n)? y
Performing reset on /SP

2. After an ILOM reset if the Primary and Backup2 containers match then proceed with the following steps to replace the
motherboard. If these two containers do not match then DO NOT proceed with the replacement yet. Contact TSC for
further assistance.

3. Backup the current ILOM configuration settings including fault data history to a XML file on an external laptop/system,
using one of the transfer protocols supported by ILOM 4.x:
https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 2/10
10/25/2019 Document

-> cd /SP/config
-> set include_faultdata=true
-> set passphrase=motherboard-replacement
-> set
dump_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/ilom_conf

For additional information, refer

to https://docs.oracle.com/cd/E81115_01/html/E86149/z40048b81489311.html#scrolltoc

4. Backup the current BIOS configuration parameters to a XML file on an external laptop/system using one of the transfer
protocols supported by ILOM 4.x:

-> cd /System/BIOS/Config
-> set
dump_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/bios_conf

For additional information, refer

to https://docs.oracle.com/cd/E81115_01/html/E86149/z40001541481533.html#scrolltoc

5. Extend the server to the maintenance position

6. Disconnect the power cords from the power supplies

7. Attach an anti-static wrist strap to your wrist and to a metal area on the chassis or the rack.

8. Remove the server top cover. Use a Torx T15 screwdriver to unlock the release button latch.

Removing the Motherboard

Caution - These procedures require that you handle components that are sensitive to electrostatic discharge. This
sensitivity can cause the components to fail. To avoid damage, ensure that you follow anti-static practices.

1. Remove the following components and set them aside on an anti-static mat:

Caution - During the motherboard removal procedure, it is recommended to only pull the power supplies as far out as
necessary to disengage them from the motherboard, without removing them completely from the chassis slot they are
in. If they are removed completely from the chassis slot, it is critical to label the power supplies with the slot numbers
from which they were removed (PS0, PS1). The power supplies must be reinstalled into the chassis slots from which
they were removed because PS0 is a backup container for fruid data which will be used to verify and update the fruid
data on the replacement motherboard. If they are accidentally swapped, then manual re-programming of the fruid
data will be required. Contact TSC for further assistance with that.

Power supplies - disengage only, do not fully remove.

Fan modules.
Fan tray.
Air baffle.
IB HCA PCIe card in Slot 7 - Disconnect IB cables and completely remove the connector ends from the card. Set
them aside out of the way.
SAS HBA PCIe card in slot 11 (High Capacity model only) - Disconnect the SuperCap cable and 3 SAS data cables
while removing.
Flash PCIe cards - Label the Slot number as they are removed.

Caution - It is critical to label the flash cards with the PCIe Slot numbers from which they were removed. The
flash cards will actively contain data in active ASM diskgroups. If they are accidentally swapped to a different
slot, then the ASM diskgroups may not mount and may need manual intervention and/or restore from backup to
recover. Contact EEST for further assistance with that.

2. Remove the following cables from the motherboard:

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 3/10
10/25/2019 Document

a. Disconnect the external network cables from Net0 and ILOM Net.Mgt from the rear back panel, and set them out of
the way.

b. (High Capacity and XT models only) Remove the SAS cables from the cable trough and set them out of the way.

c. (High Capacity and XT models only) Detach the SuperCap tray by squeezing the plastic hings together and lifting
away from the midwall.

d. Disk Backplane power cable - unlatch from the motherboard connector, lift up and out of the cable trough and set out
of the way.

e. Disk Backplane data cable - unlatch from the motherboard connector, lift up and out of the cable trough and set out
of the way.

f. Front LED indicator module (FIM) ribbon cable - disconnect from the motherboard connector, lift up and out of the
cable trough and set out of the way.

g. Serial Management RJ-45 cable - carefully pull up on the cable and pry it up from the motherboard connector.
Disconnect the RJ45 connector latch and set the cable aside.

3. Remove the motherboard from the server chassis with all reusable components that populate the motherboard in place.

a. Using a Torx T25 screwdriver, loosen the two captive screws that secure the motherboard mid-wall to the chassis.
b. Carefully slide the motherboard forward, and while holding the motherboard mid-wall, lift it out of the chassis.
c. Place the motherboard assembly on an anti-static mat, and next to the replacement motherboard.

4. Remove the Coin Cell battery from the motherboard and re-install it on the replacement motherboard.

5. Remove the DDR4 DIMMs from the motherboard and re-install them onto the corresponding slots in the replacement
motherboard.

Note - Install the DDR4 DIMMs only in the slots (connectors) from which they were removed. Performing a one-to-one
replacement of DIMMs significantly reduces the possibility that DIMMs will be installed in the wrong slots. If you do not
reinstall the DIMMs in the same slots, server performance might be reduced and some DIMMs might not be used.

6. Remove the M.2 SSD Disk risers from the motherboard and re-install them into the corresponding slots in the
replacement motherboard.

Note - Install each M.2 SSD Disk riser into the same corresponding slot from which it was removed. If they are
accidentally swapped to a different slot, the OS disk volumes contained on the M.2 SSD Disks may be unable to boot.

7. Remove the CPUs from the failed motherboard.

8. Remove the CPU socket covers from the replacement motherboard and install the CPUs into the replacement
motherboard.

a. Grasp the CPU socket cover finger grips (labeled REMOVE) and lift the socket cover up and off the processor socket.
b. Install a CPU into the socket from which you removed the CPU socket cover. See MOS Doc ID 2360710.1 (How to
Replace an Exadata X7-2 Storage Cell Server CPU) for steps. A 12.0 in-lbs (inch-pounds) torque driver with a Torx T30 bit
is required for CPU installation.
c. Repeat Step 8.a and Step 8.b to remove the second CPU socket cover from the replacement motherboard and install
the second CPU processor.

9. Install the CPU socket covers onto the CPU sockets of the faulty motherboard.

Caution - The CPU socket covers must be installed on the faulty motherboard; otherwise, damage might result to the
CPU sockets during handling and shipping, preventing motherboards from being repairable.

a. Align the CPU socket cover over the CPU socket alignment posts. Install the CPU socket cover by firmly pressing
down on all four corners (labeled INSTALL) on the socket cover.
You will hear an audible click when the CPU socket cover is securely attached to the CPU socket.
b. Repeat Step 9.a to install the second CPU socket cover on the faulty motherboard.

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 4/10
10/25/2019 Document

Installing the Motherboard

1. Attach an anti-static wrist strap to your wrist, and then to a metal area on the chassis.

2. Insert the motherboard into the server chassis.

a. While holding the motherboard mid-wall, tilt the motherboard to the right side to fit it under the power supply
assembly, then level the motherboard and place it into the server chassis. Be careful not to damage the rear Locate
Button/LED when placing the motherboard into the chassis.
b. Slide the motherboard to the rear of the server to engage the raised standoffs.
c. Ensure that the indicators, controls, and connectors on the rear of the motherboard fit correctly into the rear of the
server chassis.
d. Using a Torx T25 screwdriver, tighten the two captive screws to secure the motherboard mid-wall to the chassis.

3. Reinstall cables on to the motherboard.

a. Reconnect the RJ45 serial cable to the RJ45 connector and the motherboard connector.
b. Reconnect the FIM ribbon cable to the motherboard connector.
c. Reconnect the disk backplane data cable to the motherboard connector.
d. Reconnect the disk backplane power cable to the motherboard connector.
e. (High Capacity and XT models only) Re-attach the SuperCap tray by squeezing the plastic hinges together and
inserting the tray into the chassis. The cable should exit the tray to the PCIe Slot 11 area.
f. (High Capacity and XT models model only) Route the SAS data cables through the cable routing trough to the PCIe
Slot 11 area.
g. Reconnect the external network connections to the back panel ports - Net0 (Black) and ILOM Net.Mgt (Red).

4. Reinstall the following components:

Caution - The power supplies must be reinstalled into the chassis slots from which they were removed because PS0 is
a backup container for fruid data which will be used to verify and update the fruid data on the replacement
motherboard. If they are accidentally swapped, then manual re-programming of the fruid data will be required.
Contact TSC for further assistance with that.

Power supplies - ensure they are re-installed in the same slot they were removed from.
Fan modules.
Fan tray.
Air baffle.
Flash PCIe cards - ensure they are re-installed in the same slot they were removed from.

Caution - It is critical to label the flash cards with the PCIe Slot numbers from which they were removed. The
flash cards will actively contain data in active ASM diskgroups. If they are accidentally swapped to a different
slot, then the ASM diskgroups may not mount and may need manual intervention and/or restore from backup to
recover. Contact EEST for further assistance with that.

IB HCA PCIe card in Slot 7 - connect IB cables as labelled. Port 1 is the upper port, Port 2 is the lower port.
SAS HBA PCIe card in slot 11 (High Capacity model only) - Reconnect the SuperCap cable and the 3 SAS data
cables while installing. Plug each cable into its SAS connector until you hear an audible click. Ensure the cables are
installed in the correct HBA connector slots as they directly connect to the disk slots being connected through them:
- Cable 1 goes to disk slots 0-3
- Cable 2 goes to disk slots 4-7
- Cable 3 goes to disk slots 8-11
- Disk slots 12-15 connector should be empty.

Return the Server to Operation

1. Install the server top cover. Use a Torx T15 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.

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 5/10
10/25/2019 Document

Note: When connecting to ILOM via serial cable, the baud rate is 9600 for replacement boards. This will get changed
to the Exadata default which is 115200 when restoring ILOM settings and/or booting the Exadata OS image.

5. Login to the ILOM as root with default password 'changeme'. Power on the server to BIOS so that ILOM can access the
BIOS but the server OS does not boot:

-> set /HOST boot_device=bios

-> start /System

6. Install the Exadata ILOM profile required for UEFI secure boot. The update_entitlements.pkg package file is attached to
this Note 2375697.1. If this is not installed into ILOM, the system will not be able to boot the Exadata OS image. Load
the attached package from an external laptop/system using one of the transfer protocols supported by ILOM 4.x. After
installation, reset the BIOS properties to default.

-> set /SP system_contact='psnc profile|0x00010000'

-> load -script -source

transfer_method://username:password@ipaddress_or_hostname/directorypath/update_entitlement

-> set /System/BIOS reset_to_defaults=factory

For additional information on the ILOM load command, refer

to: https://docs.oracle.com/cd/E81115_01/html/E86149/z400371a1482689.html#scrolltoc

7. Check and set the system serial number/fruid data:

a. Enter the ILOM restricted shell to check the psnc values. Follow the example below to enter restricted shell and use
the showpsnc command:

-> set SESSION mode=restricted

WARNING: The "Restricted Shell" account is provided solely

to allow Services to perform diagnostic tasks.

[(restricted_shell) <HOSTNAME>-ilom:~]# showpsnc

Primary: fruid:///SYS/DBP
Backup 1: fruid:///SYS/MB
Backup 2: fruid:///SYS/PS0

Element | Primary | Backup1 | Backup2

------------------+-------------------+-------------------+-------------------
PPN 7338449 7338449 7338449
PSN XXXXNMXXXX 0000000000 XXXXNMXXXX
Profile 0x00010000 0x00010000 0x00010000
Product Name ORACLE SERVER X7-2L ORACLE SERVER X7-2L ORACLE SERVER X7-2L
RFID SN 341A583DE5800000000233C6 341A583DE5800000000233C6
341A583DE5800000000233C6
[(restricted_shell) <HOSTNAME>-ilom:~]#

b. The above example shows a system with the Backup1 container not in sync after MB replacement. If the output from
the system does not show all of the containers with matching values then you should reset the SP and then re-check the
values again. An ILOM reset will attempt to auto-populate the matching values if one container is out of sync.

-> reset /SP

Are you sure you want to reset /SP (y/n)? y
Performing reset on /SP

If after the ILOM reset the containers still don't match then contact the TSC for further assistance. (if all three entries
match this step is done).

8. Restore the ILOM configuration using the backup XML file made earlier, using one of the transfer protocols supported
by ILOM 4.x:

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 6/10
10/25/2019 Document

-> cd /SP/config
/SP/config
-> set include_faultdata=true
-> set passphrase=motherboard-replacement
-> set
load_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/ilom_conf

For additional information, refer to https://docs.oracle.com/cd/E81115_01/html/E86149/z40048b81489452.html#scrolltoc

9. Restore the BIOS configuration using the backup XML file made earlier.

-> cd /System/BIOS/Config
-> set
load_uri=transfer_method://username:password@ipaddress_or_hostname/directorypath/bios_conf

For additional information, refer to https://docs.oracle.com/cd/E81115_01/html/E86149/z40001541481574.html#scrolltoc

Note - In the event the ILOM or BIOS configuration could not be backed up due to the faulty motherboard, manually
set at least the following settings, using a working node ILOM or BIOS as the reference for values:

Serial Baud rate is 115200 for external and host

/SP system_identifier contains the Rack type and serial number
/SP hostname
/SP/network settings
/SP/clock and /SP/clients/ntp settings
/SP/clients/dns settings
/SP/alertmgmt rules
/SP/users/root account password
BIOS boot order

Note - Also be aware that if the new motherboard firmware does not match the previous boards firmware version, this
may cause the restore of ILOM or BIOS backup to fail. If this happens you may need to manually update the firmware
via the ILOM BUI to the same version before the motherboard was replaced before restoring the ILOM or BIOS
backup.

10. Reset the ILOM to apply the configuration changes:

-> reset /SP

11. Reset the host power and connect to the server console via the ILOM and monitor the boot.

-> reset /System

-> start /HOST/console

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.

12. During boot, the image will re-flash the ILOM/BIOS to the correct minimum level contained in the image, if it is a lower
version.

Note - Before power up it is necessary to configure the ILOM network settings, obtain the ILOM network values
from the customer or the previously saved SP.config file ( See Steps #8 & #9 above
). If one of these steps are
not performed the ILOM will fail to re-flash.

a. Power up system using front button or from ILOM "-> start /SYS".
b. During the boot validation phase, CheckHWnFWProfile will run and determine the ILOM version, and give a

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 7/10
10/25/2019 Document

WARNING if it is not correct, it will then attempt to reflash, which will result in a reboot. After the reboot, the boot
validation phase should return "SUCCESS".

If you see the following warning then the firmware update has failed:

[WARNING] Firmware updates were already tried once and likely failed.
[WARNING] To retry the firmware update reboot or try to update the firmware manually.

then please delete /opt/oracle.cellos/TRIED_FW_UPDATE_ONCE and re-run

/opt/oracle.SupportTools/CheckHWnFWProfile -U /opt/oracle.cellos/iso/cellbits

If this happens, then manually update the firmware by logging in as root to the node after it is booted, and run the
following:

# /opt/oracle.SupportTools/CheckHWnFWProfile -U /opt/oracle.cellos/iso/cellbits

NOTE - The above command will do a similar update to the Cell automatic update method. The server will be powered off
during this, ILOM will reset, and after 10 minutes of being off to allow ILOM reset and BIOS flash update, the server host
will be automatically powered back on. See Example output below:-

[root@<HOSTNAME> cellbits]# /opt/oracle.SupportTools/CheckHWnFWProfile -U

/opt/oracle.cellos/iso/cellbits

Now updating the ILOM and the BIOS ...

[INFO] Start ILOM firmware upgrade to version 3.1.2.10 r74387. Attempt 1 of 2.
Connected. Use ^D to exit.
...
Waiting for upgrade to start..
Broadcast message from root (Thu Dec 9 00:57:48 2010):
The system is going down for system halt NOW!
..Connection to 10.X.X.XX closed by remote host.
Connection to 10.X.X.XX closed.

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.

-> show /SYS/MB

/SYS/MB
Targets:
BIOS
CPLD
FM0
FM1
FM2
FM3
M2R0
M2R1
NET0
P0
P1
PCIE4
PCIE5

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 8/10
10/25/2019 Document
PCIE6
PCIE7
PCIE10
PCIE11
T_IN_ZONE0
T_IN_ZONE1
T_IN_ZONE2
T_IN_ZONE3
T_OUT_ZONE0
T_OUT_ZONE1
T_OUT_ZONE2
T_OUT_ZONE3

Properties:
type = Motherboard
ipmi_name = MB
fru_description = ASM, MB MECH, X7-2L
fru_manufacturer = Oracle Corporation
fru_part_number = 7335280
fru_rev_level = 06
fru_serial_number = 465136N+XXXXNMXXXX
fru_macaddress = XX:XX:XX:XX:XX:XX
fault_state = OK
clear_fault_action = (none)

Commands:
cd
set
show

->

2. Verify there are no outstanding faults in ILOM:

# ipmitool sunoem cli 'show faulty'

Connected. Use ^D to exit.
-> show faulty
Target | Property | Value
-------------------+-----------------------+-----------------------------------
-> Session closed
Disconnected
#

If there are faults still outstanding that did not auto-clear in ILOM after replacement, refer to the post-repair procedures
section of Doc ID 1155200.1 to clear the fault.

3. (High Capacity and XT models only) Verify the status of the Super Capacitor is visible and 'Optimal':

# /opt/MegaRAID/storcli/storcli64 /c0/cv show status

4. (High Capacity and XT models only) Set all logical drives cache policy to WriteBack cache mode:

# /opt/MegaRAID/storcli/storcli64 /c0/vall set wrcache=WB

5. (High Capacity and XT models only) Verify all expected logical drives are present and state 'Optl' (Optimal). For 1/8th
rack Storage Cells there will be 6 disks, for all others there will be 12 disks:

# /opt/MegaRAID/storcli/storcli64 /c0/vall show

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

6. Verify there are no outstanding alerts in the Cell:

# cellcli -e list alerthistory

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 9/10
10/25/2019 Document

7. Re-activate the Storage Cell grid disks. Follow Steps 7 to 10 of Note ID 1188080.1 “Steps to shut down or reboot an
Exadata storage cell without affecting ASM”.

These steps are also provided in the documentation:

https://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm#DBMMN21128

8. If the customer has dcli setup for password-less SSH, then they will need to update and push new SSH keys for the new
mac address. The customer should be able to do this using the documentation:

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-storage-server-
dcli.html#GUID-472C6AA1-BF36-4885-825D-281FC2CEFBC3

PARTS NOTE:

7335280 [F] System Board Assembly [X7-2]

7360978 [F] System Board Assembly [X8-2]

REFERENCE INFORMATION:

Oracle Exadata Database Machine Maintenance Guide: https://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-

exadata-storage-servers.htm#DBMMN21128

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

Oracle Server X8-2L Documentation: https://docs.oracle.com/cd/E93361_01/

Steps to shut down or reboot an Exadata storage cell without affecting ASM (Doc ID 1188080.1)

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_adf.ctrl-state=sprfppqyx_4 10/10