Oracle oda-x9-2l-ha checklist

EIS Installation Checklist for the
ORACLE® Database Appliance X9-2 High Availability (X9-2 HA) -

Bare Metal Platform
Customer:
TASK Number:
Technician:
Date:
This checklist is for the “Limited Software Install” service for the Oracle Database Appliance X9-2
HA – Bare Metal Platform.
• Be sure to check the EIS web page for the latest versions prior to commencing the
installation.
• The purpose of this checklist is to help the installer achieve a consistent, "good" installation.
• Installers must have attended the appropriate training classes.
◦ EIS checklists are NOT a replacement for proper training.
• Use of a laptop is required during the installation.
◦ Linux on that laptop would make life easier.
• Do NOT hand this checklist over to the customer.
• Feedback on issues with EIS content or product quality is welcome.
◦ Oracle staff should send email to EIS-SUPPORT_WW_GRP@oracle.com
◦ Partners should contact the PartnerHelp Portal for assistance and feedback.
System Type Top Level Identification (TLI)

Oracle Database Appliance X9-2 HA
In this document, we refer to the servers as Node 0 and Node 1. Node 0 is the bottom server (oak0
prompt) and Node 1 is the top server (oak1 prompt).
The hardware essentially is comprised of two Oracle Server X9-2L server nodes with an interconnect
and one or two DE3-24C storage shelves. The Top Level Identification (TLI) sticker which contains
the serial number is on the top of a server node or a storage shelf, on the left-hand side towards the
front.
NOTE: When multiple ODA systems are being installed, make sure that for each ODA system that
the TLI sticker shows the same serial number on both nodes (do not mix up the nodes!).
The original storage shelf and expansion shelf (if they have one) will also come with a TLI sticker to
match the nodes. Although it is preferred, it is not mandatory to match the storage TLI stickers with
the nodes.
Oracle Internal and Approved Partners Only Page 1 of 62 Version 2.0 – Created: 13 Jun 2023
ENGINEERED SYSTEMS ENTERPRISE SUPPORT TEAM EEST
If a Field Support Engineer (FSE) requires assistance while installing an Engineered System, a
streamlined method of engaging an Engineered Systems Enterprise Support Team (EEST) engineer
when the SR owner is not available is described below. The SR referred to is the installation SR.
An FSE would use this option if they are onsite and require immediate assistance from EEST. This
process is specifically for FSE Callbacks for hardware, installation and Field Change Order (FCOs)
support and should NOT be used by ACS or partners.
The complete process is described in MOS Document ID 1803744.1 EEST: Silent Menu Option :
GCSEXA (internal-only). Ensure that you understand the contents before going onsite.
If you encounter an issue during the installation, this may be documented in the ODA Current
Product Issues page: MOS Document ID 1538187.1 (internal-only). Refer to this document for a
possible workaround to any bug you may encounter during the installation.
For additional help with ODA deployment, you can send an email to the following mailing list:
global-field-oda-sme-assist_grp@oracle.com
This mailing list is intended for use by Installers/FEs to reach out to other Field resources, who have
been identified as ODA Subject Matter Experts, for help with ODA installs.
INSTALLATION OVERVIEW– EIS DELIVERABLES

For an overview of the activities carried out during the installation of this product via the EIS
Methodology, refer to the EIS-Deliverables page within the EIS website for the Oracle Database
Appliance ODA.
This EIS does not cover KVM configuration, and FEs are only tasked with creating the appliance, to
get the system on the customer network. After completing the EIS, if KVM is desired, then the
administrator of the ODA system can refer to Deploy KVM Database System in Oracle Database
Appliance Documentation .
MEMORY DIMM FAULT BEST PRACTICES
TSC are seeing many DIMMs being replaced in the field due to initial boot up and Memory DIMM
fault either due to Memory DIMM movement during shipping or improper seating during memory
upgrades.
If Memory DIMM faults are encountered during the installation or upgrade of any engineered
systems, please follow the "BEST PRACTICE" as supplied by the hardware team.
Best Practice for resolving DIMM Faults during Installation or upgrade:
1. We (the TSC) are recommending the re-seating of Memory DIMMs when seeing faults during
installation or memory upgrades, as a first step.
2. If we see these failures outside of upgrades or rack installs, we don't want to take the chance
and risk of a second visit if they're truly failed Memory DIMMs. So we recommend, in these
instances, to simply replace the Memory DIMM. If the replaced Memory DIMM experiences
Training errors, then it might be prudent to re-seat the Memory DIMM.
INFORMATION: EIS Checklist Steps & Estimated Timing

Item First Page Est. Duration
Preparation 6 4 hours
Unpacking 8 30 mins
Assembly / Cabling 9 45 mins
ILOM Service Processor Configuration 13 10 mins
Server Power On & POST 15 20 mins
Bare Metal (Non-Virtualized) ODA 105 (+60) mins
Verify Pre-Installed Version 19 10 mins
Re-imaging for the Bare Metal configuration
20 (60 mins)
(if necessary)
Bare Metal ODA Configuration 30 mins
Changing the ODA CPU Core Count 15 mins
Deploying the ODA Using the Oracle Appliance Manager
44 40 mins
Configuration
Post Validation 59 10 mins
Common Actions
Securing the ILOM Service Processors (SP) 61 10 mins
Handover 61 15 mins
Appendix A: Using the odacli Command to Monitor
10 mins
Deployment
AUTOMATIC SERVICE REQUEST (ASR) ACTIVITIES
If the ODA will not be configured to use ASR, go to the section entitled ODA
PREPARATION below.
While it is highly recommended to use an external ASR Manager with ODA it is supported to
use an internal ASR manager.
If the ASR Manager has not been previously installed AND the Customer requests that Oracle
install it, go to the documentation page for Oracle ASR and select the URL for the ASR
Manager installation and operations guide, quick install guide, security white paper. There
you will find the current Installation and Operations Guide. Follow the instructions to install
the ASRM based on the system you have been given to install it in.
Register the ASR manager with Oracle – follow the installation process through the point
where the ASR is registered to the backend.
This activity must be completed prior to installation of the ODA(s).
CHECKING A CUSTOMER'S EXISTING ASR MANAGER SERVER
If the Customer has a configured and operational ASR Manager system available, the
components within the ODA will be configured to use ASR. Ensure that the IP address &
root password of the ASR Manager host are available.
ODA PREPARATION
EIS Site-Audit Report complete? EISdoc V4:
The server nodes require 2RU each & each storage
shelf requires 4 RU hence an ODA with one storage
shelf requires a total of 8 RUs
EIS Installation Configuration Plan & Test EISdoc V4:
Procedures Plan complete? Use appropriate BUILD & TPP templates, inserted
into “Master” files (Chapter Servers):
EIS-BUILD-Server-ODA-X9HA.odt
EIS-TPP-Server-ODA-X9HA.odt
IMPORTANT: Review the network IP addresses are required for both the hosts & the
configuration information supplied by the Service Processors (at least two for each).
customer to ensure the correct data is The hostnames for the servers should be configured
recorded. Do this BEFORE going onsite. in the customer site network DNS servers as well.
The checklist information for the deployment using the configurator can be found in the
Oracle Database Appliance Documentation – Deployment Checklists
Refer to the Oracle Database Appliance documentation for more details, including a setup
poster that is included with the server delivery.
An Oracle Internal-only source of information is the FAQ for the Oracle Database Appliance
- Externally available documentation and information on all ODA products is available on the
Oracle Technical Network (OTN). Any additional questions should be referred to their sales
representative.
Terminology
Oracle Database Appliance patches and software consists the following components:
• ODA Bundle Patch
Contains patches to the following components: OS, Component Firmware and Oracle
Appliance Manager Modules, Grid Infrastructure and RDBMS, DCS components
• GI/RDBMS Clone files
Contains the latest Grid Infrastructure and RDBMS components, for deployment on an
Oracle Database Appliance in the "shipped from factory" state, or an Oracle Database
Appliance that has been re-imaged using the OS ISO Image.
• OS ISO Image
Used to restore the OS to the "shipped from factory" state. Use only when necessary.
• Bare Metal
Refers to the non-virtualized ODA configuration.
PREPARING THE DOWNLOADS
It is highly recommended that you always obtain the latest ODA software releases directly
from MOS. The Bare Metal software image is installed by the factory and is most likely not
the latest version available on MOS. At the time of this publication, the current software
version is 19.19.0.0.0. We recommend always installing the latest version.
The latest patches and ISO images can be found in MOS in the Patches and Updates tab.
In the Patch Search section, click on the Product or Family (Advanced) side tab, and next to
the Product field enter “Oracle Database Appliance Software”. Next to the Release field, in
the drop-down box, select “Oracle Database Appliance Software (ODA) 19.19.0.0.0”.
Click on Search button.
PATCHES NEEDED TO DEPLOY BARE METAL
Required Patches:
• 30403643 – ODA 19.19 ISO Bare Metal Restore file
p30403643_1919000_Linux-x86-64.zip 5.1 GB
• 35290009 – Server patch bundle

p35290009_1919000_Linux-x86-64.zip 3.3 GB
Database Clone patches. With BM install, it is only required to install the
RDBMS
patch that is desired by the customer. Starting with 19.12, the ODA image
can only have one RDBMS patch installed before deploy. If a customer
wishes to use the RDBMS Software Clone for other versions than what
comes with the version being installed, they can install the RDBMS
Software Clone from a previous version of ODA 19.x. Oracle recommends
that a customer upgrade their RDBMS though. After deploy, additional
RDBMS Software Clone patches can be installed.
• 30403673 – Oracle 19.19.0.0.0 GI Clone file, a file needed for deployment when
installing database 19.18
p30403673_1919000_Linux-x86-64.zip 5.1GB
• 30403662 – Oracle 19.19.0.0.230418 Clone file for creating any new 19.19 database
homes.
p30403662_1919000_Linux-x86-64.zip 5.0 GB
NOTE: We recommend transferring the files directly to the server over a network
connection.
Alternatively, if you prefer, you can also use a USB drive to transfer the files. The
larger files (over 4GB) will not transfer to a FAT32 formatted USB drive due to
filesystem limitations. The USB drive must be formatted with “EXT4” (Linux) or
Windows NTFS filesystem.
UNPACKING Check
Delivery complete?
Collect the white Customer Information File away carefully!
Sheets (CIS).
Allow the system to acclimatize (power off) at Refer to EIS standard “Acclimatisation of Oracle
the customer site. Hardware products”.
Unpack outside data center to ensure no Collect packing material together for disposal.
contamination/dust is released inside
customer's controlled environment.
Verify all packing material has been removed, Fans & air vents must be free to operate.
i.e. nothing is blocked.
Gather excess parts, cables etc. in a box. • (2) Tool-less rack mount kits (Server nodes)
• (2) Cable Management Arms (Server nodes)
• (1) Fixed rack mount kit (Storage shelf)
• (2) 3 meter SFP28 passive copper cables (for
Interconnect)
• (4) 3 meter SAS cables (Storage server
Connectivity to Server nodes)
• Setup poster
Collect documentation together. Give to customer during handover.
Refer to the Oracle Database Appliance Owner's Guide for details on inserting the system into a rack.
An 8RU space is required for a one storage shelf configuration and a 12RU space is required for the
two storage shelf configuration.
Supported in any racks meeting the below criteria:
• Four-post rack (mounting at both front and rear), not supported in two-post racks.
• Rack should have a horizontal opening and unit vertical pitch conforming to ANSI/EIA 310-
D-1992 or IEC 60927 standards.
• Distance between front and rear mounting planes between approximately 24 and 36 inches
(610 mm and 915 mm).
• Minimum clearance depth (to front cabinet door) in front of front rack mounting plane: 1 inch
(25.4 mm).
• Minimum clearance depth (to rear cabinet door) behind front rack mounting plane: 35.43
inches (900 mm) with the cable management arm, or 800 mm (31.5 in) without the cable
management arm.
• Minimum clearance width (between structural supports and cable troughs) between front and
rear mounting planes: 18 inches (456 mm).
• Minimum clearance for front service access is 48.5 inches (123.2 cm).
• Minimum clearance for rear service access is 36 inches (91 cm).
• Always load equipment into a rack from the bottom upwards so that it will not become top-
heavy and tip over. Deploy the rack's anti-tilt bar to prevent the rack from tipping during
equipment installation.
ASSEMBLY/CABLING Check
Note the serial number. The TLI sticker which contains the serial number is on
the top of a server node or a storage shelf, on the left-
hand side towards the front.
Distribute systems across power-sequencers considering failure-safety.
Connect Ethernet cables for both SPs to the To the NET MGT port on each node.
administration network. Node 1 is the top server.
Node 0 is the bottom server.
Connect serial cables between the SPs and a terminal device or PC (used for the initial
configuration) to the SER MGT ports
PRIVATE INTERCONNECT
The ODA ships with two 1-meter SFP28 passive copper cables. Use these for the
interconnects.
Connect green cable Connect cable from PCIe slot 1, PORT2 on node0 to
PCIe slot 1, PORT2 on node1.
Connect yellow cable Connect cable from PCIe slot 1, PORT1 on node0 to
PCIe slot 1, PORT1 on node1.
These two private interfaces are named p1p1/p1p2, which in turn is icbond0.
CLIENT ACCESS CABLING
On each node, there is a network card installed in slot 6. Below is a picture of the cards if the
customer has chosen the dual 10/25gb Fiber card (btbond1). If the customer has chosen the
10gb Ethernet Fortpond card, the cards in slot 6 have four RJ45 ethernet ports (btbond1 and
btbond2). With ODA x9-2 hardware, the fiber card will be a Whitney+ 10/25GbPS card or a
Mellanox CX-5 10/25GbPS card.
With Fiber network cards in both computers, the upper connector is p6p1 of btbond1, and the
lower connector is p6p2 of btbond1. For a quad port card, the lowest RJ-45 connector is p6p1
of btbond1, the next connector up is p6p2 of btbond1, and the upper connections are
p6p3/p6p4 for btbond2.
CABLING THE STORAGE SHELF Check
Connect Node 0 to Storage shelf with dark Connect into dark blue port (SAS0) in PCIe slot 2 Node
blue cable. 0 to dark blue port in top IO Module (port 0) on the
Storage shelf.
Connect Node 0 to Storage shelf with light Connect into light blue port (SAS1) in PCIe slot 9 Node
blue cable. 0 to light blue port in bottom IO Module (port 0) on the
Storage shelf.
Connect Node 1 to Storage shelf with dark red Connect into dark red port (SAS1) in PCIe slot 2 Node
cable. 1 to dark red port in top IO Module (port 1) on the
Storage shelf.
Connect Node 1 to Storage shelf with light red Connect into light red port (SAS0) in PCIe slot 9 Node
cable. 1 to light red port in bottom IO Module (port 1) on the
Storage shelf.
CABLING THE EXPANSION STORAGE SHELF (OPTIONAL) Check
By default, the ODA X9-2 HA will have one storage shelf. An additional shelf is optional.
Connect Node 1 to Storage Expansion shelf Connect into dark blue port (SAS0) in PCIe slot 2 in
with dark blue cable. node 1 to dark blue port in top IO Module (port 0) on
Exp. Storage Shelf.
Connect Node 1 to Storage Expansion shelf Connect into light blue port (SAS1) in PCIe slot 9 in
with light blue cable. Node 1 to light blue port in bottom IO Module (port 0)
on Exp. Storage Shelf.
Connect Node 0 to Storage Expansion shelf Connect into dark red port (SAS1) in PCIe slot 2 in
with dark red cable. Node 0 to dark red port in top IO Module (port 1) on
Exp. Storage Shelf.
Connect Node 0 to Storage Expansion shelf Connect into light red port (SAS0) in PCIe slot 9 in
with light red cable. Node 0 to light red port in bottom IO Module (port 1)
on Exp. Storage Shelf.
COMPLETING THE CABLING

Label the cables clearly & use cable binders.
Perform initial power on by attaching the The SPs in the computers will boot and then will reduce
power cables. Both AC power connectors on the speed of the cooling fans. The Power/OK LEDs on
the front panel will flash (standby mode).
the back panel must be attached via grounded
AC power cords.
Confirm that the power switch of all shelf
PSUs are ON.
ILOM SERVICE PROCESSOR CONFIGURATION (CONT) Node
0 1
The hardware is essentially comprised of two nodes with an interconnect, plus one or two storage
shelves. Hence each node has a Service Processor that needs to be configured.
This checklist assumes IPv4 networking.
When the SP initially boots it will attempt to If a DHCP server is available, you can connect to the SP
obtain an IP address from a DHCP server. via network (ssh or https), otherwise you have to
connect to the SP via a serial line (see below) and
You must have a cable connected to the SP specify a static Ethernet configuration.
Serial Management port (SER MGT) and one
from the customer network connected to NET
MGT.
Obtain the Service Processor IP address and record the IP address for future reference. By
default, this IP address is assigned by the DHCP server.
To get the SP address that may have been assigned by a DHCP server, you can use one of the
following methods:
• Have the customer login to the DHCP server and determine what network address the
DHCP server assigned to the SP.
or
• Connect to SER MGT port of the SP via terminal device (such as a laptop). Log into
the SP via CLI and display the IP address.
User = root
Password = changeme
-> show /SP/network
CONFIGURING ILOM VIA CLI AND A SERIAL CONNECTION

To set a static IP address in the SP using the CLI using a serial line connection, perform the
steps below.
Enter the following commands to specify a The following are example values:
static Ethernet configuration. These -> set pendingipaddress=129.144.82.26
-> set pendingipnetmask=255.255.255.0
commands must be run after changing to -> set pendingipgateway=129.144.82.254
the /SP/Network directory. -> set pendingipdiscovery=static
Be sure to use the indicated spaces in the -> set commitpending=true
-> set state=enabled
command line structure. Note that the commitpending command requires
several seconds to complete.
→ cd /SP/network
Verify the changes. -> show /SP/network
Verify that the gateway can be reached:

-> set /SP/network/test ping=<IP of gateway>
ping of <IP of gateway> succeeded
After setting up the SP, exit. -> exit
ILOM SERVICE PROCESSOR CONFIGURATION (CONT) Node
0 1
CONFIGURING THE SP'S CLOCK PROPERTIES VIA CLI
Refer to the Oracle ILOM Administrator's Guide for Configuration and Maintenance Firmware
Release 5.0.x
To examine the current settings:
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Fri Aug 23 10:10:09 2013
timezone = GMT (GMT)
uptime = 1 day, 19:17:16
usentpserver = disabled
If required, the timezone can be changed from GMT (default) to EST or PST8PDT:
-> set /SP/clock timezone=EST5EDT
If connected by browser, available SP timezone values can be selected from a pull

down menu.
To manually set the ILOM clock property values:

-> set /SP/clock datetime=MMDDhhmmYYYY
Example:
-> set /SP/clock datetime=082310132013
Set 'datetime' to '082310132013'
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Fri Aug 23 10:13:04 2013
timezone = GMT (GMT)
uptime = 1 day, 19:17:16
usentpserver = disabled
To synchronize the SP's clock property values with an NTP server:

-> set /SP/clients/ntp/server/1 address=<ip_address>
-> set /SP/clock usentpserver=enabled
CHECK THE MOTHERBOARD REAL TIME CLOCK ON BOTH NODES

There have been several HA system installs where the system deploy repeatedly failed.
Troubleshooting found that the motherboard clock on one node was at a significantly different
time than that of the other.
The most direct way to check the motherboard clock is to enter the motherboard BIOS, the
clock is in the Main menu.
The other way is to check the clock after the OS boots using the “date” command.
To set the clock from within the OS, the date command uses this format:
date mmddhhmmyyyy
# date 011318362023
Fri Jan 13 18:36:00 MST 2023
SERVER POWER ON & POST Node
0 1
Confirm that all storage shelf/shelves PSUs power switches are already all “ON”.
Power on each Node. There are several ways to do this:
• Press the power-on button on the front panel of each server.
• Using the GUI on each SP, expand the Host Management menu on the left, select
Power Control. You will see Host is currently off – select Power On. Then press the
save button.
Using GUI: to gain console access to Server Start console redirection.
Node
The fans will speed up and after a few seconds The console will show the results of POST.
back down. Observe the POST results.
At the OS login prompt: User root with welcome1 as password.
VALIDATE STORAGE CABLING Node
0 1
Run the validate scripts to confirm that the cabling is correct:
[root@oak0 ~]# odacli validate-storagetopology

INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X8-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO : Check number of Controllers
SUCCESS : Number of ahci controller found : 1
SUCCESS : Number of External SCSI controllers found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : Internal LSI SAS controller :
SUCCESS : External LSI SAS controller 0 : 3b:00.0
SUCCESS : External LSI SAS controller 1 : e3:00.0
INFO : Check if JBOD powered on
SUCCESS : 1JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 2
INFO : Check for External Controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for controller 0
SUCCESS : Controller connected to correct EBOD number
SUCCESS : Controller port connected to correct EBOD port
SUCCESS : Overall Cable check for Controller 1
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
INFO : Check Node Identification status
SUCCESS : Node Identification
SUCCESS : Node name based on cable configuration found : NODE0
If there is a storage expansion unit attached, now is the time to power it on. Re-run the
storagetopology command on both nodes to make sure the cabling is correct:
[root@oak0 ~]# odacli validate-storagetopology

INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X8-2
INFO : Check for Environment(Bare Metal or Virtual Machine)
SUCCESS : Type of environment found : Bare Metal
INFO : Check number of Controllers
SUCCESS : Number of ahci controller found : 1
SUCCESS : Number of External SCSI controllers found : 2
INFO : Check for Controllers correct PCIe slot address
SUCCESS : Internal RAID controller :
SUCCESS : External LSI SAS controller 0 : 3b:00.0
SUCCESS : External LSI SAS controller 1 : 5e:00.0
INFO : Check if JBOD powered on
SUCCESS : 2JBOD : Powered-on
INFO : Check for correct number of EBODS(2 or 4)
SUCCESS : EBOD found : 4
SUCCESS : Cable check for port 0 on controller 0
INFO : Check for overall status of cable validation on Node0
SUCCESS : Overall Cable Validation on Node0
SUCCESS : JBOD0 Nickname set correctly
SUCCESS : JBOD1 Nickname set correctly
CHECK system_identifier FIELD Node
0 1
On both nodes display the system identifier:

# ipmitool sunoem getval /X/system_identifier
Target Value: Oracle Database Appliance X9-2 High Availability <serial #>
The output from both nodes should have the same system_identifier denoted with the same
serial number.
-> show /System
/System
Targets:
Open_Problems (0)
Processors
Memory
Power
Cooling
Storage
Networking
PCI_Devices
Firmware
BIOS
Log
Properties:
health = OK
health_details = -
open_problems_count = 0
type = Rack Mount
model = ORACLE SERVER X9-2L
qpart_id = Q13720
part_number = 7603375-18632
serial_number = 2138XL0008 <<< this is the serial # you want to use for system_identifier
rfid_serial_number = 341A583DE580000000074102
component_model = ORACLE SERVER X9-2L
component_part_number = 7603375-18632
component_serial_number = 2139XLF009
system_identifier = Oracle Database Appliance X9-2 High Availability
2138XL0008
system_fw_version = 5.1.0.23
primary_operating_system = Not Available
VALIDATE INTERCONNECT CABLING Node
0 1
# ethtool p1p1
Settings for p1p1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
10000baseT/Full
25000baseCR/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseT/Full
10000baseT/Full
25000baseCR/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 25000Mb/s <<<< Check the speed
Duplex: Full
Port: Direct Attach Copper
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes <<<< This should be "yes"
# ethtool p1p2
Settings for p1p2:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
10000baseT/Full
25000baseCR/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 1000baseT/Full
10000baseT/Full
25000baseCR/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 25000Mb/s <<<< Check the speed
Duplex: Full
Port: Direct Attach Copper
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: yes <<<< This should be "yes"
VERIFY PRE-INSTALLED VERSION
To verify the current ODA system version, run the following command on both nodes:
# odacli describe-component -v
System Version
---------------
19.19.0.0.0
System node Name

---------------
oak1
Local System Version

---------------
19.19.0.0.0
System node Name

---------------
oak1

---------------
19.19.0.0.0
If the version is the latest available on MOS, then you can proceed with the Bare Metal deployment.
If the version is older than what is available on MOS, you can re-image using the ISO file contained
in patch 30403643 (which was downloaded during the Preparation activities on page 6 of this
checklist) and continue to follow the instructions starting on the next page of this checklist.
NOTE REGARDING STORAGE SHELVES THAT PREVIOUSLY HAVE BEEN

IN PRODUCTION
If an ODA HA system disk shelf has been previously imaged (with even the same version),
the headers on the disks in the shelf must be cleared using cleanup.pl before deployment, or
the deploy with the new image version will fail when it configures storage.
In Troubleshooting Oracle Database Appliance, a full explanation for using cleanup.pl is
provided under “Uninstalling Oracle Database Appliance Components”.
If the storage array has had a previous image installed on it, the following command must be used
also before deploy:
cleanup.pl -erasedata
RE-IMAGING FOR THE BARE METAL CONFIGURATION Node
0 1
To re-image with a newer version, you will require the Bare Metal ISO image.
The file can be unzipped on a Linux or Windows environment using appropriate commands to unzip
the file. For example on Linux use:
# unzip p30403643_1919000_Linux-x86-64.zip
Archive: p30403643_1919000_Linux-x86-64.zip
inflating: oda_bm_19.19.0.0.0_230510.iso <<<<< this is the iso image file
Most actions here need to be carried out on both nodes.

The re-imaging can be performed in parallel on both nodes. There is no need to wait until one node is
complete before starting the other node.
Connect to ILOM from the Browser and login as root:
On successful login, the Browser will redirect to the Oracle Integrated Lights out Manager
home page. Click on the Launch button to continue:
Depending on the state of the system, there may be some message on the console. Click on
KVMS and then Storage as highlighted below:
Click on Add, then browser to choose the iso image as shown below:
Click on the file you've just selected and press Connect at the bottom of the screen.
After you have pressed Connect, if the Java window suddenly crashes or you are having issues
booting from the ISO image, perform the following steps:
• On the next reset, repeat the above steps
• But this time, uncheck the SSL Enabled box on this screen and mount the ISO image
again.
• Proceed only after the ISO image successfully mounts.
Now that the ISO image has successfully been mounted, return to the ILOM web GUI to set
the boot device to CDROM and press Save.
Now click on the Power Control tab as shown below and choose Power Cycle from the drop-
down list and press Save.
The Database Appliance Bare Metal install will start after reboot. This process will continue
for at least 60 minutes and then the following screen will be displayed:
NOTE: After the boot, the localhost login prompt will appear. Press enter after that for the
oak0/oak1 login (oak1/oak2 might also be the prompt), then login using user name root and
password welcome1. However, if this is ODA has two storage trays attached, the localhost
prompt will remain, this is normal, it will change after configure-firstnet.
Only proceed to the next section when the re-imaging on both nodes is complete.
CONFIGURING THE NETWORK INTERFACE Node
0 1
Run the command configure-firstnet on both nodes.
NOTE: If the command is only run on one node, the deployment will fail.
Respond to the prompts to configure the public network interface with the netmask and
gateway IP address info provided by the customer.
Example output below includes sample IP addresses for network, netmask and gateway. You
may get different options, other than btbond1/btbond3/btbond4, depending on what type of
network cards and how many network cards are installed. Starting with the X8-2 systems,
breaking the bond is not an option.
[root@oak0 ~]# odacli configure-firstnet
INFO: Using default bonding configuration
Select the Interface to configure the network on (btbond1 btbond3 btbond4)
[btbond1]:btbond1
Use LACP bonding on btbond1 (yes/no) [no]: <<<< new with 19.18
Configure DHCP on btbond1 (yes/no) [no]:
INFO: You have chosen Static configuration
Use VLAN on btbond1 (yes/no) [no]:
Enter the IP address to configure : 10.xxx.xxx.xx
Enter the Netmask address to configure : 255.255.248.0
Enter the Gateway address to configure [10.xxx.xxx.x] :
INFO: Restarting the network
[ 435.953556] mlx5_core 0000:17:00.0: Successfully unregistered panic
handler for port 1
[ 437.727069] mlx5_core 0000:17:00.0: Successfully registered panic handler
for port 1
[ 444.321556] mlx5_core 0000:17:00.0: Successfully unregistered panic
handler for port 1
[ 447.419374] mlx5_core 0000:17:00.0: Successfully registered panic handler
for port 1
INFO: Network has been setup successfully
Below is a table that shows the correlation between network cards and Linux interface names.
For a system with two storage trays, you will see this:
[root@localhost ~]# odacli configure-firstnet
Enter node number: 0 OR 1
0
Do you want to continue yes | no :
yes
User has entered node number=0

Initialize MySQL - Done
Created symlink from /etc/systemd/system/multi-user.target.wants/oda-mysql.service
to /etc/systemd/system/oda-mysql.service.
Starting MySQL for ODA - Done
mysql: [Warning] Using a password on the command line interface can be insecure.
Enable server-side auth_socket authentication plugin for MySQL root user - Done
Generating RSA private key, 2048 bit long modulus
....................................................................................
+++
........................................................+++
e is 65537 (0x10001)
Generating a 2048 bit RSA private key
........+++
...........................+++
writing new private key to 'server-key.pem'
-----
writing RSA key
Signature ok
subject=/CN=oak0
Getting CA Private Key
........+++
.......................+++
writing new private key to 'dcsagent-client-key.pem'
-----
writing RSA key
Signature ok
subject=/CN=dcsagent
.............+++
...................................................+++
writing new private key to 'rhp-client-key.pem'
-----
writing RSA key
Signature ok
subject=/CN=rhp user
All certificates : OK
Generate certificates for CA, MySQL Server and Clients (DCS Agent & RHP) - Done
Enable SSL and Restart MySQL - Done
Create database dcsagentdb - Done
Create user dcsagent - Done
Grant privileges to user dcsagent - Done
Create database GHSUSER21 - Done
Create user GHSUSER21 - Done
Grant privileges to user GHSUSER21 - Done
Create schemas, users for CS Agent & RHP - Done
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leapseconds' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/tzdata.zi' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping
it.
Load the timezone tables in mysql database - Done
MySQL installed version details :
/opt/oracle/dcs/mysql/bin/mysql Ver 8.0.22-commercial for Linux on x86_64 (MySQL
Enterprise Server - Commercial)
MySQL installation and configuration.....Completed
Resetting dcs-agent config file...
generating credentials for dcs-cli and dcs-agent
done generating credentials for dcs-cli and dcs-agent
Starting oda-zookeeper.service, oda-mysql.service and initdcs*.service services,
which can take 30 seconds
Created symlink from /etc/systemd/system/multi-user.target.wants/oda-
zookeeper.service to /etc/systemd/system/oda-zookeeper.service.
Created symlink from
/etc/systemd/system/multi-user.target.wants/initdcsadmin.service to
/etc/systemd/system/initdcsadmin.service.
/etc/systemd/system/multi-user.target.wants/initdcsagent.service to
/etc/systemd/system/initdcsagent.service.
/etc/systemd/system/multi-user.target.wants/initdcscontroller.service to
/etc/systemd/system/initdcscontroller.service.
Using bonding public interface (yes/no) [yes]:
Select the Interface to configure the network on (btbond1 btbond3 btbond4)
[btbond1]:
Use LACP bonding on btbond1 (yes/no) [no]: <<<< new with 19.18
Configure DHCP on btbond1 (yes/no) [no]:
INFO: You have chosen Static configuration
Use VLAN on btbond1 (yes/no) [no]:
Enter the IP address to configure : 10.xxx.xxx.xxx
Enter the Netmask address to configure : 255.255.252.0
Enter the Gateway address to configure[10.xxx.xxx.x] :
INFO: Restarting the network
INFO: Restarting TFA to configure the host name
Shutting down TFA
. . . . .
. . .
Successfully shutdown TFA..
Starting TFA..
Waiting up to 100 seconds for TFA to be started..
. . . . .
. . . . .
Successfully started TFA Process..
. . . . .
TFA Started and listening for commands
TFA has not synchronised across all nodes yet.

If an install or upgrade is in progress and the operation has not completed on all
nodes then please wait for completion and allow TFA 10 minutes to synchronize.
If no install or upgrade is in progress or you need TFA to synchronize now
Please run 'tfactl syncnodes' to generate and copy TFA Certificates.
UPLOADING PATCHES TO THE SERVER NODE Node
0
Patches only need to be installed on Node0 only. The patches and files will propagate to the
other node automatically.
Now that you have an active network interface, you can use scp/ftp/filezilla to transfer the
files to the server node, for example:
# cd /u01
# scp xx.xxx.xxx.xxx://<path>/p30403673_1919000_Linux-x86-64.zip .
**Important
Starting with 19.12, the file system layout has been changed, /opt has been
significantly reduced. Deploy with 1 RDBMS patch, then after deployment,
you can install additional RDBMS patches if needed. Also, you should copy
and install one patch at a time, then delete the compressed file that was
copied before copying the next patch, and the README.txt file as well.
This also means that for the entire process to work, upload only one patch,
unzip it, delete the just uploaded zip file and README.txt, then update the
repository with the decompressed zip file. This is to be done with each of
the files that are uploaded to the server.
If you're not able to have access to the client's network, then a good workaround is to configure em1 to
attach your laptop directly to the NET0 port.
To configure em1:
# ifconfig em1 10.10.10.1 netmask 255.255.255.0
# ifconfig em1
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255
ether 00:10:e0:eb:ec:4c txqueuelen 1000 (Ethernet)
RX packets 17352 bytes 1537513 (1.4 MiB)
RX errors 0 dropped 229 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x9ca00000-9cafffff
On your laptop, you will also need to configure the network port to 10.10.10.2
NOTE: em1 gets unconfigured during deployment, so your direct network connection will get
disconnected shortly after you hit submit.
Now, you can transfer the patches over using winscp, filezilla, etc..
UNPACK AND INSTALL THE GI PATCH
Unzip the GI patch.
extracting: odacli-dcs-19.19.0.0.0-230510-GI-19.19.0.0.zip
inflating: README.txt
Delete unneeded files to free up space:
# rm p30403673_1919000_Linux-x86-64.zip
rm: remove regular file ‘p30403673_1919000_Linux-x86-64.zip’? y
# rm README.txt
rm: remove regular file ‘README.txt’? y
Update the repository

# odacli update-repository -f /u01/odacli-dcs-19.19.0.0.0-230510-GI-
19.19.0.0.zip
{
"jobId" : "20d0e6ce-ec26-4bff-a3c2-fcf3566cd115",
"status" : "Created",
"message" : "/u01/odacli-dcs-19.19.0.0.0-230510-GI-19.19.0.0.zip",
"reports" : [ ],
"createTimestamp" : "June 05, 2023 22:41:13 PM UTC",
"resourceList" : [ ],
"description" : "Repository Update",
"updatedTime" : "June 05, 2023 22:41:13 PM UTC",
"jobType" : null
}
Confirm that the repository update has been successful.
# odacli describe-job -i "20d0e6ce-ec26-4bff-a3c2-fcf3566cd115"
Job details
----------------------------------------------------------------
ID: 20d0e6ce-ec26-4bff-a3c2-fcf3566cd115
Description: Repository Update
Status: Success
Created: June 5, 2023 10:41:13 PM UTC
Message: /u01/odacli-dcs-19.19.0.0.0-230510-GI-19.19.0.0.zip
Task Name Node Name Start Time

End Time Status
---------------------------------------- -------------------------
----------------------------------- -----------------------------------
----------
Check AvailableSpace oak2 June 5,
2023 10:41:25 PM UTC June 5, 2023 10:41:25 PM UTC Success
Setting up ssh equivalance oak1 June 5,
Copy BundleFile oak1 June 5,
Validating CopiedFile oak2 June 5,
Unzip bundle oak1 June 5,
Delete PatchBundles oak2 June 5,
UPLOAD, UNPACK, AND INSTALL THE SERVER/STORAGE PATCH

Upload the Server patch to the system:
Unzip the patch files:
AArchive: p35290009_1919000_Linux-x86-64.zip
extracting: oda-sm-19.19.0.0.0-230510-server.zip
Delete no longer needed files to free up space:
# rm p35290009_1919000_Linux-x86-64.zip
# unzip README.txt
Update the repository.
# odacli update-repository -f /u01/oda-sm-19.19.0.0.0-230510-server.zip
{
"jobId" : "cfbc9495-32e5-4a3c-9957-48f3865841dc",
"message" : "/u01/oda-sm-19.19.0.0.0-230510-server.zip",
"reports" : [ ],
"jobType" : null
}
Confirm the update was successful:
# odacli describe-job -i "cfbc9495-32e5-4a3c-9957-48f3865841dc"
Job details
----------------------------------------------------------------
ID: cfbc9495-32e5-4a3c-9957-48f3865841dc
Status: Success
Message: /u01/oda-sm-19.19.0.0.0-230510-server.zip
Task Name Node Name Start Time End Time Status

---------------------------------------- ------------------------- ----------------------------------- -----------------------------------
----------
Check AvailableSpace oak2 June 5, 2023 10:53:56 PM UTC June 5, 2023 10:53:56
PM UTC Success
Setting up ssh equivalance oak1 June 5, 2023 10:53:56 PM UTC June 5, 2023 10:53:58
PM UTC Success
Copy BundleFile oak1 June 5, 2023 10:53:58 PM UTC June 5, 2023 10:54:04 PM
UTC Success
Validating CopiedFile oak2 June 5, 2023 10:54:04 PM UTC June 5, 2023 10:54:10
PM UTC Success
Unzip bundle oak1 June 5, 2023 10:54:10 PM UTC June 5, 2023 10:54:35 PM
UTC Success
Unzip bundle oak2 June 5, 2023 10:54:35 PM UTC June 5, 2023 10:55:00 PM
UTC Success
Delete PatchBundles oak2 June 5, 2023 10:55:00 PM UTC June 5, 2023 10:55:01
PM UTC Success
UPLOAD, UNPACK, AND INSTALL AN RDBMS PATCH
Upload a RDBMS patch to the system:

Unzip the patch files:
extracting: odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip
Delete no longer needed files to free up space
# rm p30403662_1919000_Linux-x86-64.zip
# rm README.txt
Update the repository

# odacli update-repository -f /u01/odacli-dcs-19.19.0.0.0-230510-
DB-19.19.0.0.zip ##[K
{
"jobId" : "a5188ed6-3f7a-4cf0-8fa2-1e2c3d3f2714",
"message" : "/u01/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip",
"reports" : [ ],
"createTimestamp" : "June 06, 2023 00:49:10 AM UTC",
"updatedTime" : "June 06, 2023 00:49:10 AM UTC",
"jobType" : null
}
Confirm the update was successful:
# odacli describe-job -i "a5188ed6-3f7a-4cf0-8fa2-1e2c3d3f2714"
Job details
----------------------------------------------------------------
ID: a5188ed6-3f7a-4cf0-8fa2-1e2c3d3f2714
Status: Success
Created: June 6, 2023 12:49:10 AM UTC
Message: /u01/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip

End Time Status
---------------------------------------- -------------------------
----------------------------------- -----------------------------------
----------
Check AvailableSpace oak2 June 6,
2023 12:49:20 AM UTC June 6, 2023 12:49:20 AM UTC Success
Setting up ssh equivalance oak1 June 6,
Copy BundleFile oak1 June 6,
Validating CopiedFile oak2 June 6,
Delete PatchBundles oak2 June 6,
APPLYING THE SERVER UPDATE
It is a requirement to first run prepatchreport, before applying the server update.
# odacli create-prepatchreport -s -v 19.19.0.0.0
Job details
----------------------------------------------------------------
ID: 21017b6b-179c-4663-b63a-c29096c50e85
Description: Patch pre-checks for [OS, ILOM, SERVER]
Status: Created
Message: Use 'odacli describe-prepatchreport -i 21017b6b-179c-4663-
b63a-c29096c50e85' to check details of results
Task Name Start Time End Time

Status
---------------------------------------- -----------------------------------
----------------------------------- ----------
Confirm the prepatchreport has completed:

# odacli describe-job -i 21017b6b-179c-4663-b63a-c29096c50e85
Job details
----------------------------------------------------------------
ID: 21017b6b-179c-4663-b63a-c29096c50e85
Status: Success
Message: Use 'odacli describe-prepatchreport -i <ID>' to check
prepatch results

End Time Status
---------------------------------------------- -----------------------------------
Run patching pre-checks oak1 June 6, 2023
12:53:59 AM UTC June 6, 2023 12:54:57 AM UTC Success
Alternatively, you can use “odacli describe-prepatchreport -i 21017b6b-179c-4663-
b63a-c29096c50e85”
Apply the server patch. The iloms and nodes may reboot, be patient and do not interrupt the
process.
# odacli update-server -v 19.19.0.0.0
{
"jobId" : "c9b6e49e-bd3f-41b7-bded-cfcf38a050c2",
"message" : "Success of server update will trigger reboot of the node after 4-5
minutes. Please wait until the node reboots.",
"reports" : [ ],
"description" : "Server Patching",
"jobType" : null
}
Confirm the update was successful.
# odacli describe-job -i 21017b6b-179c-4663-b63a-c29096c50e85
Job details
----------------------------------------------------------------
ID: 21017b6b-179c-4663-b63a-c29096c50e85
Status: Success
Message: Use 'odacli describe-prepatchreport -i <ID>' to
check prepatch results

End Time Status
---------------------------------------- -------------------------
----------------------------------- -----------------------------------
----------
Run patching pre-checks oak1 June 6,
[root@oak1 ~]# odacli describe-job -i c9b6e49e-bd3f-41b7-bded-cfcf38a050c2
Job details
----------------------------------------------------------------
ID: c9b6e49e-bd3f-41b7-bded-cfcf38a050c2
Description: Server Patching
Status: Success
Message:

End Time Status
---------------------------------------- -------------------------
----------------------------------- -----------------------------------
----------
Validate ILOM server reachable oak1 June 6,
Validate ILOM server reachable oak2 June 6,
Stop DCS Admin oak2 June 6,
Stop DCS Admin oak1 June 6,
Generate mTLS certificates oak2 June 6,
Generate mTLS certificates oak1 June 6,
Exporting Public Keys oak2 June 6,
Exporting Public Keys oak1 June 6,
Copy Public Key to Remote node oak1 June 6,
Copy Public Key to Remote node oak2 June 6,
Creating Trust Store oak2 June 6,
Creating Trust Store oak1 June 6,
Update config files oak2 June 6,
Update config files oak1 June 6,
Restart DCS Admin oak2 June 6,
Restart DCS Admin oak1 June 6,
Creating repositories using yum oak2 June 6,
Updating YumPluginVersionLock rpm oak2 June 6,
Applying OS Patches oak2 June 6,
Creating repositories using yum oak2 June 6,
Applying HMP Patches oak2 June 6,
Patch location validation oak1 June 6,
Oda-hw-mgmt upgrade oak1 June 6,
Oda-hw-mgmt upgrade oak2 June 6,
Applying Firmware Disk Patches oak2 June 6,
Applying Firmware Controller Patches oak2 June 6,
Checking Ilom patch Version oak1 June 6,
Checking Ilom patch Version oak2 June 6,
Save password in Wallet oak2 June 6,
Disabling IPMI v2 oak2 June 6,
Apply Ilom patch oak1 June 6,
Apply Ilom patch oak2 June 6,
Copying Flash Bios to Temp location oak1 June 6,
Copying Flash Bios to Temp location oak2 June 6,
Update System version oak1 June 6,
Update System version oak2 June 6,
Cleanup JRE Home oak1 June 6,
Enable LKCE oak2 June 6,
Enable LKCE oak1 June 6,
Update lvm.conf file oak1 June 6,
Update lvm.conf file oak2 June 6,
Update previous workarounds oak1 June 6,
Update previous workarounds oak2 June 6,
Generating and saving BOM oak2 June 6,
Generating and saving BOM oak1 June 6,
PreRebootNode Actions oak1 June 6,
PreRebootNode Actions oak2 June 6,
Reboot Ilom oak1 June 6,
Reboot Ilom oak2 June 6,
APPLY THE STORAGE PATCH
Update storage components:
# odacli update-storage -v 19.19.0.0.0

{
"jobId" : "132d4f60-0330-40e1-ae8d-c00ebf18f708",
"message" : "Success of Storage Update may trigger reboot of node after 4-5
minutes. Please wait till node restart",
"reports" : [ ],
"description" : "Storage Firmware Patching",
"jobType" : null
}
Confirm the update was successful. The servers may reboot during this procedure, depending
on which component gets updated.
#odacli describe-job -i "132d4f60-0330-40e1-ae8d-c00ebf18f708"
Job details
----------------------------------------------------------------
ID: 132d4f60-0330-40e1-ae8d-c00ebf18f708
Description: Storage Firmware Patching
Status: Success
Message:

End Time Status
---------------------------------------- -------------------------
----------------------------------- ----------------------------------- ----------
Applying Firmware Disk Patches oak2 June 6, 2023
6:41:18 PM UTC June 6, 2023 6:41:25 PM UTC Success
Generating and saving BOM oak1 June 6, 2023
Generating and saving BOM oak2 June 6, 2023
PreRebootNode Actions oak1 June 6, 2023
PreRebootNode Actions oak2 June 6, 2023
Reboot Ilom oak1 June 6, 2023
Reboot Ilom oak2 June 6, 2023
Confirm that all firmware components are up-to-date.
# odacli describe-component
System Version
---------------
19.19.0.0.0
System node Name
---------------
odax9-2ha-h0

---------------
19.19.0.0.0
Component Installed Version Available

Version
---------------------------------------- --------------------
--------------------
OAK
19.19.0.0.0 up-to-date
GI
19.19.0.0.230418 up-to-date
DCSCONTROLLER
19.19.0.0.0 up-to-date
DCSCLI
19.19.0.0.0 up-to-date
DCSAGENT
19.19.0.0.0 up-to-date
DCSADMIN
19.19.0.0.0 up-to-date
OS
7.9 up-to-date
ILOM
5.1.1.21.r150524 up-to-date
BIOS
62080700 up-to-date
LOCAL CONTROLLER FIRMWARE {
[c3]
16.32.1010 up-to-date
[c4]
8000071E up-to-date
[c5]
8000C470 up-to-date
[c6]
214.2.271.9 up-to-date
}
SHARED CONTROLLER FIRMWARE
16.00.08.00 up-to-date
FIRMWAREEXPANDER
0310 up-to-date
LOCAL DISK FIRMWARE
XC311132 up-to-date
SHARED DISK FIRMWARE {
[c0d0,c0d1]
XC311132 up-to-date
[c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c2d0,
c2d1,c2d2,c2d3,c2d4,c2d5] RXA0 up-to-date
[c1d6,c1d7,c1d8,c1d9,c1d10,c1d11,c1d12,
c1d13,c1d14,c1d15,c1d16,c1d17,c1d18,
c1d19,c1d20,c1d21,c1d22,c1d23,c2d6,c2d7,
c2d8,c2d9,c2d10,c2d11,c2d12,c2d13,c2d14,
c2d15,c2d16,c2d17,c2d18,c2d19,c2d20,
c2d21,c2d22,c2d23] A670 up-to-date
}
HMP
2.4.8.9.605 up-to-date
System node Name
---------------
odax9-2ha-h1

---------------
19.19.0.0.0

Version
---------------------------------------- --------------------
--------------------
OAK
19.19.0.0.0 up-to-date
GI
19.19.0.0.230418 up-to-date
DCSCONTROLLER
19.19.0.0.0 up-to-date
DCSCLI
19.19.0.0.0 up-to-date
DCSAGENT
19.19.0.0.0 up-to-date
DCSADMIN
19.19.0.0.0 up-to-date
OS
7.9 up-to-date
ILOM
5.1.1.21.r150524 up-to-date
BIOS
62080700 up-to-date
[c3]
16.32.1010 up-to-date
[c4]
8000071E up-to-date
[c5]
8000C470 up-to-date
[c6]
214.2.271.9 up-to-date
}
16.00.08.00 up-to-date
FIRMWAREEXPANDER
0310 up-to-date
LOCAL DISK FIRMWARE
XC311132 up-to-date
[c0d0,c0d1]
XC311132 up-to-date
[c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c2d0,
[c1d6,c1d7,c1d8,c1d9,c1d10,c1d11,c1d12,
c1d13,c1d14,c1d15,c1d16,c1d17,c1d18,
c1d19,c1d20,c1d21,c1d22,c1d23,c2d6,c2d7,
c2d8,c2d9,c2d10,c2d11,c2d12,c2d13,c2d14,
c2d15,c2d16,c2d17,c2d18,c2d19,c2d20,
}
HMP
2.4.8.9.605 up-to-date
DEPLOYING THE ORACLE DATABASE APPLIANCE
You are now ready to deploy the Oracle Database Appliance. Monitor the progress by:
# tail -f /opt/oracle/dcs/log/dcs-agent.log
If you're not able to have access to the client's network, then a good workaround is to configure em1
to attach your laptop directly to the NET0 port.
To configure em1:
# ifconfig em1 10.10.10.1 netmask 255.255.255.0
# ifconfig em1
em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255
ether 00:10:e0:eb:ec:4c txqueuelen 1000 (Ethernet)
RX packets 17352 bytes 1537513 (1.4 MiB)
RX errors 0 dropped 229 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x9ca00000-9cafffff
On your laptop, you will also need to configure the network port to 10.10.10.2
• NOTE: em1 gets unconfigured during deployment, so your direct network connection will
get disconnected shortly after you hit submit.
Using the Chrome or IE browser, enter the following URL and log into the ODA:
• https://<ipaddress-node>:7093/mgmt/index.html
• The first screen you will see is a screen asking you to change the password.
• The password must contain at least two uppercase and two lowercase letters, two numbers (0-
9), and two special characters (#-_). Password must have a minimum of 9 characters and a
maximum of 30 characters.
Note: the “Enable Multi-User Access” box should not be set unless the customer knows
what it is used for.
Also: best practices is that the customer network DNS servers already include the ODA network
hostnames or the Create Appliance action will fail.
After the password has been changed, you will see the login screen. Login name is oda-admin
NOTE: If the login fails due to an authentication issue, make sure that network between the ODA
and the installer’s laptop has ports 7070 and 7093 open. Unless these ports are opened up, you will
continue to get authentication errors and will not be able to login until the customer opens up these
ports.
If opening up these ports is not an option, you can connect directly to the ODA by configuring em1 up
and using your laptop to connect directly.
On the first screen of a new system, you will see this, click on Create Appliance.
Starting with 19.17, the web page tool now uses tabs to configure different system parameters.
In each tab, mandatory fields have a *.

In the System information tab, the System name is the host name which...
• must begin with an alphabetic character
• can contain alphanumeric characters and dashes (-)
• cannot exceed 30 characters
• cannot start with a number or dash (-)
• cannot end with dash (-)
The next tab to the right is for network information. These are the hostnames that need to have been
configured in the customer network DNS servers, or deploying the server will fail.
Even if the ILOM network has been configured, it is good to also input the values here.
The next tab to the right is the section used to configure “Users & Groups”.
The default is “No” (no changes to the default User and Group information will be made), and with
“No”, this is what the tab shows:
In the “Users & Groups” tab, if you select “Yes”, the following settings can be changed:
The next tab is how an initial database can be created. The image shown here is with that set to No.
Creating an initial database is not mandatory for deployment (it is recommended that the FE does not
create the initial database), as this can be done later by the customer using the odacli create-
database command.
If an initial database is created, additional databases can be created with “odacli create-database.“
If you answer Yes to create a database, you will need to fill in the following fields. The database
name must begin with an alpha character and contain only alphanumeric characters. The database
name must NOT exceed 8 characters.
The “Diagnostics Information” tab is where to set redacted TFA collections, and is where ASR can
be configured. The default for both is No.
In order to use the External ASR Manager, the customer will need an existing ASR Manager IP.
While using an External ASR Manager is highly recommended, it is supported to use the internal
ASR manager.
If Yes, the ASR User Name and Password is required. Make sure this is the customer’s
username/password.
If Yes to HTTP Proxy, the Proxy Server Name and Proxy Port is required.
If Yes to HTTP Proxy Requires Authentication, Proxy User Name and Proxy Password is
required.
It is a good idea to first Save Configuration, so that you have it in case you need to redeploy.
Then press Submit.
Select Yes to confirm:
Starting with 19.18, after clicking Yes, the configuration web page will show a reminder that while
the appliance configuration checks are being made, system network connections (not SP) become
unreachable.
When the system deploy checks are completed, about 4min later, the configuration web page will
show a message similar to this:
MONITOR DEPLOYMENT PROGRESS
To monitor deployment progress, you can monitor the dcs-agent.log file:
# tail -f /opt/oracle/dcs/log/dcs-agent.log
If there is an error during deployment, we will see it in the dcs-agent.log file.

Furthermore, you can run the odacli command to monitor/check status.
To monitor the deployment progress using command-line, use the job ID identified for
“Provisioning service creation”.
To get the job ID:
[root@oak0 ~]# odacli list-jobs
ID Description
Created Status
----------------------------------------
---------------------------------------------------------------------------
----------------------------------- ----------
20d0e6ce-ec26-4bff-a3c2-fcf3566cd115 Repository Update
2023-06-05 22:41:13 GMT Success
cfbc9495-32e5-4a3c-9957-48f3865841dc Repository Update
2023-06-05 22:53:49 GMT Success
a5188ed6-3f7a-4cf0-8fa2-1e2c3d3f2714 Repository Update
2023-06-06 00:49:10 GMT Success
21017b6b-179c-4663-b63a-c29096c50e85 Patch pre-checks for [OS, ILOM,
SERVER] 2023-06-06 00:53:57 GMT
Success
06807d86-da96-40b4-b99d-47d4deeefb08 Auto purge job data
2023-06-06 04:00:00 GMT Success
c9b6e49e-bd3f-41b7-bded-cfcf38a050c2 Server Patching
2023-06-06 18:06:03 GMT Success
132d4f60-0330-40e1-ae8d-c00ebf18f708 Storage Firmware Patching
2023-06-06 18:41:02 GMT Success
d0637fa5-3afa-4266-b711-bc2f0b8c5e7a User creation(oda-admin)
2023-06-06 20:02:14 GMT Success
cd121793-ad7b-4c84-9fb2-8f791e3467ed Provisioning service creation
2023-06-06 20:40:19 GMT Running
To find status of deployment:
[root@oak0 ~]# odacli describe-job -i cd121793-ad7b-4c84-9fb2-8f791e3467ed
Job details
----------------------------------------------------------------
ID: cd121793-ad7b-4c84-9fb2-8f791e3467ed
Description: Provisioning service creation
Status: Success
Created: June 6, 2023 8:40:19 PM GMT
Message:
Task Name Node Name Start

Time End Time Status
---------------------------------------- -------------------------
----------------------------------- -----------------------------------
----------
Setting up Network odax9-2ha-brm06-a-h0 June 6,
2023 8:40:34 PM GMT June 6, 2023 8:40:34 PM GMT Success
Setting up Vlan odax9-2ha-brm06-a-h0 June 6,
Setting up Vlan odax9-2ha-brm06-a-h1 June 6,
Network update odax9-2ha-brm06-a-h0 June 6,
Updating network odax9-2ha-brm06-a-h0 June 6,
Network update odax9-2ha-brm06-a-h0 June 6,
Updating network odax9-2ha-brm06-a-h0 June 6,
OS usergroup 'asmdba' creation odax9-2ha-brm06-a-h0 June 6,
OS usergroup 'asmoper' creation odax9-2ha-brm06-a-h0 June 6,
OS usergroup 'asmadmin' creation odax9-2ha-brm06-a-h0 June 6,
OS usergroup 'dba' creation odax9-2ha-brm06-a-h0 June 6,
OS usergroup 'dbaoper' creation odax9-2ha-brm06-a-h0 June 6,
OS usergroup 'oinstall' creation odax9-2ha-brm06-a-h0 June 6,
OS user 'grid' creation odax9-2ha-brm06-a-h0 June 6,
OS user 'oracle' creation odax9-2ha-brm06-a-h0 June 6,
Default backup policy creation odax9-2ha-brm06-a-h0 June 6,
Backup config metadata persist odax9-2ha-brm06-a-h0 June 6,
Grant permission to RHP files odax9-2ha-brm06-a-h1 June 6,
Add SYSNAME in Env odax9-2ha-brm06-a-h1 June 6,
Install oracle-ahf odax9-2ha-brm06-a-h1 June 6,
Stop DCS Admin odax9-2ha-brm06-a-h1 June 6,
Stop DCS Admin odax9-2ha-brm06-a-h0 June 6,
Generate mTLS certificates odax9-2ha-brm06-a-h1 June 6,
Generate mTLS certificates odax9-2ha-brm06-a-h0 June 6,
Exporting Public Keys odax9-2ha-brm06-a-h1 June 6,
Exporting Public Keys odax9-2ha-brm06-a-h0 June 6,
Copy Public Key to Remote node odax9-2ha-brm06-a-h0 June 6,
Copy Public Key to Remote node odax9-2ha-brm06-a-h1 June 6,
Creating Trust Store odax9-2ha-brm06-a-h1 June 6,
Creating Trust Store odax9-2ha-brm06-a-h0 June 6,
Update config files odax9-2ha-brm06-a-h1 June 6,
Update config files odax9-2ha-brm06-a-h0 June 6,
Restart DCS Admin odax9-2ha-brm06-a-h0 June 6,
Restart DCS Admin odax9-2ha-brm06-a-h1 June 6,
Grid home creation odax9-2ha-brm06-a-h0 June 6,
Creating GI home directories odax9-2ha-brm06-a-h1 June 6,
Extract GI clone odax9-2ha-brm06-a-h0 June 6,
Extract GI clone odax9-2ha-brm06-a-h1 June 6,
Storage discovery odax9-2ha-brm06-a-h0 June 6,
Creating wallet for Root User odax9-2ha-brm06-a-h0 June 6,
Creating wallet for ASM Client odax9-2ha-brm06-a-h0 June 6,
Grid stack creation odax9-2ha-brm06-a-h0 June 6,
Provisioning GI with RHP odax9-2ha-brm06-a-h0 June 6,
Updating GIHome version odax9-2ha-brm06-a-h1 June 6,
Updating GIHome version odax9-2ha-brm06-a-h0 June 6,
Post cluster OAKD configuration odax9-2ha-brm06-a-h0 June 6,
Disk group 'RECO' creation odax9-2ha-brm06-a-h0 June 6,
Disk group 'FLASH' creation odax9-2ha-brm06-a-h0 June 6,
Setting ACL for disk groups odax9-2ha-brm06-a-h0 June 6,
Modify DB file attributes odax9-2ha-brm06-a-h0 June 6,
Register Scan and Vips to Public Network odax9-2ha-brm06-a-h1 June 6,
Configure export clones resource odax9-2ha-brm06-a-h0 June 6,
Volume 'commonstore' creation odax9-2ha-brm06-a-h0 June 6,
ACFS File system 'DATA' creation odax9-2ha-brm06-a-h0 June 6,
Delete public key odax9-2ha-brm06-a-h1 June 6,
Configure Zk Quorum TLS odax9-2ha-brm06-a-h1 June 6,
Create Trust Store odax9-2ha-brm06-a-h0 June 6,
Delete Trust Store odax9-2ha-brm06-a-h0 June 6,
Create Trust Store odax9-2ha-brm06-a-h1 June 6,
Provisioning service creation odax9-2ha-brm06-a-h0 June 6,
Persist new agent state entry odax9-2ha-brm06-a-h1 June 6,
Restart Zookeeper and DCS Agent odax9-2ha-brm06-a-h0 June 6,
Make sure all components are up-to-date (example below continues to the next page).
NOTE: If the installed version is higher than the available version, this is OK.
[root@oak0 u01]# odacli describe-component

System Version
---------------
19.19.0.0.0
System node Name

---------------
odax9-2ha-brm06-a-h0

---------------
19.19.0.0.0

Version
---------------------------------------- --------------------
--------------------
OAK
19.19.0.0.0 up-to-date
GI
19.19.0.0.230418 up-to-date
DCSCONTROLLER
19.19.0.0.0 up-to-date
DCSCLI
19.19.0.0.0 up-to-date
DCSAGENT
19.19.0.0.0 up-to-date
DCSADMIN
19.19.0.0.0 up-to-date
OS
7.9 up-to-date
ILOM
5.1.1.21.r150524 up-to-date
BIOS
62080700 up-to-date
[c3]
16.32.1010 up-to-date
[c4]
8000071E up-to-date
[c5]
8000C470 up-to-date
[c6]
214.2.271.9 up-to-date
}
16.00.08.00 up-to-date
FIRMWAREEXPANDER
0310 up-to-date
LOCAL DISK FIRMWARE
XC311132 up-to-date
[c0d0,c0d1]
XC311132 up-to-date
[c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c2d0,
[c1d6,c1d7,c1d8,c1d9,c1d10,c1d11,c1d12,
c1d13,c1d14,c1d15,c1d16,c1d17,c1d18,
c1d19,c1d20,c1d21,c1d22,c1d23,c2d6,c2d7,
c2d8,c2d9,c2d10,c2d11,c2d12,c2d13,c2d14,
c2d15,c2d16,c2d17,c2d18,c2d19,c2d20,
}
HMP
2.4.8.9.605 up-to-date
System node Name
---------------
odax9-2ha-brm06-a-h1

---------------
19.19.0.0.0

Version
---------------------------------------- --------------------
--------------------
OAK
19.19.0.0.0 up-to-date
GI
19.19.0.0.230418 up-to-date
DCSCONTROLLER
19.19.0.0.0 up-to-date
DCSCLI
19.19.0.0.0 up-to-date
DCSAGENT
19.19.0.0.0 up-to-date
DCSADMIN
19.19.0.0.0 up-to-date
OS
7.9 up-to-date
ILOM
5.1.1.21.r150524 up-to-date
BIOS
62080700 up-to-date
[c3]
16.32.1010 up-to-date
[c4]
8000071E up-to-date
[c5]
8000C470 up-to-date
[c6]
214.2.271.9 up-to-date
}
16.00.08.00 up-to-date
FIRMWAREEXPANDER
0310 up-to-date
LOCAL DISK FIRMWARE
XC311132 up-to-date
[c0d0,c0d1]
XC311132 up-to-date
[c1d0,c1d1,c1d2,c1d3,c1d4,c1d5,c2d0,
[c1d6,c1d7,c1d8,c1d9,c1d10,c1d11,c1d12,
c1d13,c1d14,c1d15,c1d16,c1d17,c1d18,
c1d19,c1d20,c1d21,c1d22,c1d23,c2d6,c2d7,
c2d8,c2d9,c2d10,c2d11,c2d12,c2d13,c2d14,
c2d15,c2d16,c2d17,c2d18,c2d19,c2d20,
}
HMP
2.4.8.9.605 up-to-date
CHANGING THE ODA CPU CORE COUNT
The ODA is delivered with all 32 cores on each server enabled. This section is only applicable of the
customer requires less than 36 cores.
Set the cores in multiples of 2 (e.g. 12):
NOTE: It is no longer necessary to generate a corekey on MOS. To reduce the number of
cores, use the following command on Node 0 only.
[root@oak0 u01]# odacli update-cpucore --cores 12
Modifying the enabled number of CPU requires a reboot of all nodes in the
ODA system. Are you sure you want to proceed with this operation? (Y/N): y
{
"jobId" : "7d3d8d96-e3ad-497d-a294-fca15dcad853",
"message" : null,
"reports" : [ ],
"createTimestamp" : "May 21, 2022 17:34:59 PM GMT",
"description" : "CPU cores service update",
"updatedTime" : "May 21, 2022 17:34:59 PM GMT"
}
WARNING: Reducing the number of enabled cores may set offline any of the
CPUs used by a CPU Pool. Thus, please review the status of all the CPU Pools
after this operation using the 'describe-cpupool' command. In case of any
CPU from a CPU Pool was offline please run 'remap-cpupools -f' to update the
list of CPUs and use only online CPUs.
WARNING: All the nodes in this ODA system will reboot after this operation
has completed.
After the node reboots, confirm on both nodes that the core count is correct.
Run the following command on both nodes.
# odacli describe-cpucore
Node Cores Modified Job Status

----- ------ ---------------------------------- ---------------
0 12 December 27, 2022 11:26:12 PM GMT CONFIGURED
POST VALIDATION
Verify the system has been successfully deployed by checking the new system version.
The results should look similar to the output below:
# odacli describe-system
Appliance Information
----------------------------------------------------------------
ID: 5dafcf2e-c51b-4428-90f5-06b4a053e6ea
Platform: X9-2-HA
Data Disk Count: 24
CPU Core Count: 32
Created: June 6, 2023 8:40:19 PM GMT
System Information
----------------------------------------------------------------
Name: odax9-2ha
Domain Name: us.oracle.com
Time Zone: GMT
DB Edition: EE
DNS Servers: 206.223.27.1 206.223.27.2
NTP Servers: 10.152.232.6 10.152.232.7
Disk Group Information

----------------------------------------------------------------
DG Name Redundancy Percentage
------------------------- ------------------------- ------------
DATA FLEX 80
RECO FLEX 20
FLASH FLEX 100
If there is an error during deployment, run the cleanup script on BOTH nodes with “-f” and
“-cleanDefNet”.
# /opt/oracle/oak/onecmd/cleanup.pl
INFO: Log file is
/opt/oracle/oak/log/odax9-2ha-xxxx-x-xx/cleanup/cleanup_2022-05-21_19-03-
42.log
INFO: Log file is

/opt/oracle/oak/log/odax9-2ha-xxxx-x-xx/cleanup/dcsemu_diag_precleanup_2022-
05-21_19-03-42.log
INFO: *******************************************************************
INFO: ** Starting process to cleanup provisioned host odax8-2ha-brm06-a-h0
**
INFO: *******************************************************************
INFO: Default mode being used to cleanup a provisioned system.
INFO: It will change all ASM disk status from MEMBER to FORMER
Do you want to continue (yes/no) : yes
INFO:
Running cleanup will delete Grid User - 'grid' and
INFO: DB user - 'oracle' and also the
INFO: groups 'oinstall,dba,asmadmin,asmoper,asmdba'
INFO: nodes will be rebooted
Do you want to continue (yes/no) : yes
INFO: /u01/app/19.17.0.0/grid/bin/crsctl.bin
INFO: /u01/app/19.17.0.0/grid/.patch_storage/33815596_Apr_6_2022_20_34_59/
files/bin/crsctl.bin
INFO: /u01/app/19.17.0.0/grid/.patch_storage/33987244_Apr_12_2022_06_11_26/
files/bin/crsctl.bin
INFO: *************************************
INFO: ** Checking for GI bits presence
INFO: *************************************
INFO: GI bits /u01/app/19.17.0.0/grid found on system under /u01/app
directory...
INFO: Setting up SSH equivalence from odax8-2ha-brm06-a-h0 to 192.168.16.25
root@192.168.16.25's password:
INFO: Successfully set SSH equivalence from odax8-2ha-brm06-a-h0 to
192.168.16.25
INFO: ** Disabling AFD filtering
SUCCESS: AFD filtering disabled on all devices
INFO: ** Saving disk partition info
INFO: *************************************
INFO: ** Executing Stop Clusterware commands
INFO: *************************************
INFO: *************************************
INFO: ** Remove Oracle Stack
INFO: *************************************
INFO: Stop clusterware
INFO: Oracle High Availability Services online
After reboot from a cleanup.pl script, the GI and RDBMS patch will need to be installed
again:
[root@oak1 u01]# odacli update-repository -f /u01/odacli-dcs-19.19.0.0.0-

230510-GI-19.19.0.0.zip, /u01/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip
All passwords will also revert back to the default “welcome1”.
The hostnames will revert back to oak1/oak2.
SECURING THE ILOM SERVICE PROCESSORS (SP)
Both ILOM SPs must be secured as part of the system's initial installation. Securing requires
the changing of the root password from ‘changeme’. By default connections are secure to the
ILOM either through ssh or https connection through the browser.
Do NOT change the default password until after you have completed software deployment on
the Oracle Appliance.
Change the root password. The password length must between 8-16 characters.
You can use the GUI or the CLI.
Examples below.
Changing the password using the GUI:
1. Pull down the ILOM Administration menu on the left.
2. Select User Management, select the User Accounts sub-tab.
3. Select root user & click on edit.
4. Change the root password.
Changing the password using the CLI:
# ssh -l root <SP-ipaddr>
# set /SP/users/root password=<new password>
Changing password for user /SP/users/root/password...
Enter new password again: *********
New password was successfully set for user /SP/users/root
For further information refer to the Oracle ILOM Administrator's Guide for Configuration and
Maintenance Firmware Release 5.0.x . E95138-06
HANDOVER
Perform Installation Assessment tests as EISdoc V4 – completed during preparation of
described in the EIS Test Procedures Plan. installation.
Complete documentation and hand over to EISdoc V4:

customer. File EIS-DOCS-Operational Handover-
Document.odt
Short briefing: the configuration.
For additional help with deployment, you can use global-field-oda-sme-assist_grp@oracle.com
This alias is intended for use is by FEs to reach out to Field resources for help with ODA installs.
Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that you always check the
web pages for the latest version.
Comments & RFEs welcome. Oracle staff should mail to EIS-SUPPORT_WW_GRP@oracle.com

Partners should contact the PartnerHelp Portal for assistance and feedback.

Oracle oda-x9-2l-ha checklist

Uploaded by

Copyright:

Available Formats

You might also like

Oracle oda-x9-2l-ha checklist

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle oda-x9-2l-ha checklist

Uploaded by

Copyright:

Available Formats

EIS Installation Checklist for the

ORACLE® Database Appliance X9-2 High Availability (X9-2 HA) -

System Type Top Level Identification (TLI)

INSTALLATION OVERVIEW– EIS DELIVERABLES

INFORMATION: EIS Checklist Steps & Estimated Timing

Click on Search button.

• 35290009 – Server patch bundle

COMPLETING THE CABLING

CONFIGURING ILOM VIA CLI AND A SERIAL CONNECTION

Verify the changes. -> show /SP/network

Verify that the gateway can be reached:

After setting up the SP, exit. -> exit

If connected by browser, available SP timezone values can be selected from a pull

To manually set the ILOM clock property values:

To synchronize the SP's clock property values with an NTP server:

CHECK THE MOTHERBOARD REAL TIME CLOCK ON BOTH NODES

VALIDATE STORAGE CABLING Node

Run the validate scripts to confirm that the cabling is correct:

[root@oak0 ~]# odacli validate-storagetopology

[root@oak0 ~]# odacli validate-storagetopology

On both nodes display the system identifier:

Link detected: yes <<<< This should be "yes"

Link detected: yes <<<< This should be "yes"

System node Name

Local System Version

System node Name

Local System Version

NOTE REGARDING STORAGE SHELVES THAT PREVIOUSLY HAVE BEEN

Most actions here need to be carried out on both nodes.

INFO: Network has been setup successfully

User has entered node number=0

TFA has not synchronised across all nodes yet.

Delete unneeded files to free up space:

Update the repository

# odacli describe-job -i "20d0e6ce-ec26-4bff-a3c2-fcf3566cd115"

Task Name Node Name Start Time

UPLOAD, UNPACK, AND INSTALL THE SERVER/STORAGE PATCH

Delete no longer needed files to free up space:

Task Name Node Name Start Time End Time Status

Upload a RDBMS patch to the system:

Delete no longer needed files to free up space

Update the repository

Task Name Node Name Start Time

Task Name Start Time End Time

Confirm the prepatchreport has completed:

Task Name Node Name Start Time

Task Name Node Name Start Time

[root@oak1 ~]# odacli describe-job -i c9b6e49e-bd3f-41b7-bded-cfcf38a050c2

Task Name Node Name Start Time

# odacli update-storage -v 19.19.0.0.0

Task Name Node Name Start Time

Confirm that all firmware components are up-to-date.

Local System Version

Component Installed Version Available

Local System Version

Component Installed Version Available

In each tab, mandatory fields have a *.

Then press Submit.

If there is an error during deployment, we will see it in the dcs-agent.log file.