12 Managing Networks
View the public and private networks that are configured on your Oracle Database Appliance.
- About Network Infrastructure and VLANs on Oracle Database Appliance
Learn about networks and virtual local area networks (VLANs) on the appliance. - About Oracle Database Appliance X11 Network Interfaces
Learn about onboard network interfaces for Oracle Database Appliance. - Viewing Configured Networks and Network Interfaces
Use the Browser User Interface to display a list of configured networks, network details, and interfaces. - Creating a Network
Understand how you can use the Browser User Interface to create a network for the appliance. - Creating a Physical Network
Understand how you can use the Browser User Interface to create a physical network on the unused network interface. - Updating a Network
Understand how you can use the Browser User Interface to update a network and revise the IP address, subnet mask, gateway, or type of network. - Modifying Public Network Configurations
Understand how you can modify public network on Oracle Database Appliance using ODACLI commands and JSON file. - Adding a Network Interface
Understand how you can add a configured network interface. - Deleting a Network Interface
Understand how you can delete a configured network interface. - Deleting a Network Interface Using Browser User Interface
Understand how you can delete a configured network interface using the Browser User Interface. - Deleting a Network Using the Browser User Interface
Understand how you can delete a configured network using the Browser User Interface.
About Network Infrastructure and VLANs on Oracle Database Appliance
Learn about networks and virtual local area networks (VLANs) on the appliance.
Oracle Database Appliance has two dual-port public network interfaces (either copper
or fiber), which are bonded. For dual-port networks cards, the bonded network interface
used for primary public network is always btbond1. You can, optionally,
configure upto six bonded interfaces, btbond1 to
btbond6. If you use network cards with four ports, then you can
select either btbond1 or btbond2 as the public network
interface.
You can use the Browser User Interface to display all physical and virtual networks. You can use ODACLI commands or the Browser User Interface to create, update, and deleted networks.
Virtual Local Area Networks (VLANs)
Oracle Database Appliance supports multiple virtual local area networks (VLANs) on the same network port or bond. VLANs are multiple logical networks that are created from a single physical network switch port, providing network security isolation for multiple workloads that share a common network. For example, application, backup, and management networks. Each VLAN acts as an independent logical network operating with other VLANs over the same physical connection. The VLAN tag associated with the data packet and network define the network. You can create a collection of isolated networks to enhance network security and bandwidth and keep data packets separated.
The network interfaces differ, depending on your Oracle Database Appliance hardware.
The VLAN is created on btbond0 in single-node and high-availability
platforms. In all cases, connections to user domains are through the selected
interfaces. A switch that supports tagged VLANs uses VLAN IDs to identify the
packet, including to which network the packet belongs.
Note:
To use VLANs with Oracle Database Appliance, you must configure the VLANs before you deploy the appliance.
The Browser User Interface enables you to create, list, and delete VLANs on the appliance. For high-availability systems, you can use the Browser User Interface to create a VLAN on both nodes of the appliance. To create a VLAN on a specific node, use the command-line interface.
For a bare metal deployment, use the Browser User Interface or
odacli commands to manage the following types of VLANs:
- Data Guard: For Oracle Data Guard.
- Database: For Oracle Database.
-
Backup: For backup operations.
-
Management: For management traffic.
-
Other: For usage defined by the customer. For example, for applications.
The public VLAN is setup when you configure the first network using the command
odacli configure-firstnet. You can set up only
one public VLAN. Use the command-line interface to create other VLANs. For
high-availability systems, the IP addresses for Node 0 and Node 1 cannot be the
same. Oracle Database Appliance does not support Dynamic Host Configuration Protocol
(DHCP) to provide IP addresses, subnet mask and default gateway.
Parent topic: Managing Networks
About Oracle Database Appliance X11 Network Interfaces
Learn about onboard network interfaces for Oracle Database Appliance.
The network interfaces differ, depending on your Oracle Database Appliance hardware. In all cases, connections to user domains are through the selected interfaces. Two ports inside a network card are used to create an active-backup mode bonding interface.
Table 12-1 Network Interfaces for Oracle Database Appliance X11-HA Bare Metal Deployment
| PCIe Network Card Slot | PCIe Network Port | Network Interfaces | Network Bonds | IP Addresses |
|---|---|---|---|---|
| PCIe Slot 1 (Interconnect) | 2 x 10/25GbE SFP28 ports | p1p1, p1p2 | icbond0 |
Node 0: 192.168.16.24 Node 1: 192.168.16.25 |
| PCIe Slot 5 (required - first NIC) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p5p1, p5p2 (p5p3, p5p4) | btbond1 (btbond2) | Can be assigned during provisioning or post deployment. |
| PCIe Slot 4 (optional - second NIC) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p4p1, p4p2 (p4p3, p4p4) | btbond3 (btbond4) | Can be assigned during provisioning or post deployment. |
| PCIe Slot 8 (optional - third NIC) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p8p1, p8p2 (p8p3, p8p4) | btbond5 (btbond6) | Can be assigned during provisioning or post deployment. |
| On-board | 1GBase-T | em1 | Not applicable | Assigned post deployment |
Table 12-2 Network Interfaces for Oracle Database Appliance X11-S and X11-L Bare Metal Deployment
| PCIe Network Card Slot | PCIe Network Port | Network Interfaces | Network Bonds | IP Addresses |
|---|---|---|---|---|
| PCIe Slot 5 (required - first NIC) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p5p1, p5p2 (p5p3, p5p4) | btbond1 (btbond2) | btbond1 and btbond2 can be assigned during deployment. |
| PCIe Slot 4 (optional - second NIC for Oracle Database Appliance X11-L) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p4p1, p4p2 (p4p3, p4p4) | btbond3 (btbond4) | Can be assigned during deployment. If not assigned during deployment, then it can be assigned post deployment. |
| PCIe Slot 9 (optional - second NIC for Oracle Database Appliance X11-S) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p9p1, p9p2 (p9p3, p9p4) | btbond3 (btbond4) | Can be assigned during deployment. If not assigned during deployment, then it can be assigned post deployment. |
| PCIe Slot 8 (optional - third NIC) | 4 x 10GBase-T ports or 2 x 10/25GbE SFP28 ports | p8p1, p8p2 (p8p3, p8p4) | btbond5 (btbond6) | Can be assigned during deployment. If not assigned during deployment, then it can be assigned post deployment. |
| On-board | 1GBase-T | em1 | Not applicable | Assigned post deployment |
Parent topic: Managing Networks
Viewing Configured Networks and Network Interfaces
Use the Browser User Interface to display a list of configured networks, network details, and interfaces.
Parent topic: Managing Networks
Creating a Network
Understand how you can use the Browser User Interface to create a network for the appliance.
Parent topic: Managing Networks
Creating a Physical Network
Understand how you can use the Browser User Interface to create a physical network on the unused network interface.
- Click the Appliance tab in the Browser User Interface.
- Click the Network tab in the left navigation to display a list of configured networks.
- If the appliance is a single-node system, then click Create
Network in the upper right corner. If the appliance is a
high-availability system, then go to Step 4.
- Enter the network information in the required fields. The Interface field has a drop-down menu with available choices. The Subnet Mask field has a drop-down menu with available choices and a search box. Optionally, enter a Gateway IP address and select an option from the Network Type list. The network type helps to identify if the network is for backup, database, dataguard, management, private, or other.
- Click Create.
- If the appliance is a high-availability system, then the Browser User Interface
helps you create the network for both nodes at the same time. Click
Create Network in the upper right corner.
- Enter the network information in the required fields. The Interface field has a drop-down menu with available choices. The Subnet Mask field has a drop-down menu with available choices and a search box. Optionally, enter a Gateway IP address and select an option from the Network Type list. The network type helps to identify if the network is for backup, database, dataguard, management, private, or other.
- Click Create.
Parent topic: Managing Networks
Updating a Network
Understand how you can use the Browser User Interface to update a network and revise the IP address, subnet mask, gateway, or type of network.
Parent topic: Managing Networks
Modifying Public Network Configurations
Understand how you can modify public network on Oracle Database Appliance using ODACLI commands and JSON file.
- About Modifying Network Configuration
Understand the configuration settings you can modify on the appliance. - Prerequisites
Learn about prerequisites for network changes. - About JSON File Attributes for Network Modification
Learn about the attributes in the JSON file for network changes. - About Networking Impact Report
Learn about the networking impact report. - Modifying Network Configuration
Use ODACLI commands to modify public network settings, DNS, and NTP configurations, as well as to generate and manage public Networking Impact Reports.
Parent topic: Managing Networks
About Modifying Network Configuration
Understand the configuration settings you can modify on the appliance.
- Node public IP addresses
- Subnet mask
- Gateway IP address
- Domain name
- SCAN name and SCAN IP addresses
- Node VIP names and VIP addresses
- DNS server IP addresses
- NTP server IP addresses or hostnames
- VLAN ID for an existing VLAN-configured network or vNetwork
odacli
create-networking-impact-report and odacli
modify-networking commands. The odacli
create-networking-impact-report command runs readiness checks, validates
the requested change, and shows what will be affected. It does not change the system.
The odacli modify-networking command applies the requested network
change after the required prerequisites are complete and the impact report passes
readiness checks. The operation does not rename hostnames. The short hostname remains
the same. If a new domain name is provided in the JSON file, only the domain portion of
the fully qualified hostname is changed. Before running the odacli
modify-networking command, DNS must already resolve the existing hostnames
to the new IP addresses. The command does not update external DNS records. For
same-subnet changes, the JSON file can include only the components that need to be
changed. For different-subnet changes, the JSON file must include the full target
network configuration for the bare metal system and all affected DB systems. This is
required so that all systems using the affected network can be updated together. The
feature also supports DNS-only and NTP-only changes. The all section in
the JSON file can be used only for DNS and NTP updates that apply to the bare metal
system and all DB systems.
Parent topic: Modifying Public Network Configurations
Prerequisites
Learn about prerequisites for network changes.
Before running the odacli create-networking-impact-report or
odacli modify-networking command, complete the applicable
prerequisites for the planned network change. These prerequisites are required because
some network settings are outside the scope of Oracle Database Appliance automation and
must be prepared before the network modification starts.
Prerequisites for DNS
Before running odacli modify-networking, update DNS with the new
hostname-to-IP mappings for all hostnames that will be changed. The DNS entries must
be updated for the applicable components: Bare metal system node host names, bare
metal system node VIP names, bare metal system SCAN name. DB system node host names,
DB system node VIP names, DB system SCAN name.
The existing host names must resolve to the new IP addresses before the network modification starts. The host names themselves do not change as part of this operation. Only the IP addresses and related network settings are updated. If a new domain name is provided in the request payload, only the domain portion of the fully qualified host name is changed. The short host name remains unchanged. For high-availability systems, ensure that the SCAN name resolves to the new SCAN IP addresses. For single-node systems, ensure that the node host name, VIP name, and SCAN-related entries, where applicable, resolve to the correct new address. After DNS is updated, verify name resolution from the relevant network location before proceeding.
nslookup node-hostname
nslookup node-vip-name
nslookup scan-nameDo not proceed with odacli modify-networking until DNS
resolves the target host names to the new IP addresses.
Prerequisites for Oracle ILOM
For different-subnet migration or datacenter migration, reconfigure
Oracle ILOM before changing the bare metal system public network. This is required
because the bare metal system host may become unreachable through the old public
network after the machine is moved to the new subnet. Oracle ILOM provides the
recovery and access path needed to open the host serial console and run ODACLI
commands. Oracle ILOM configuration is not modified by odacli
modify-networking.
Update the following Oracle ILOM network settings as required: ILOM IP address ILOM subnet mask ILOM gateway For same-subnet changes, Oracle ILOM reconfiguration is optional unless the ILOM address or management network is also being changed.
For different-subnet changes, complete the Oracle ILOM update first, then verify that Oracle ILOM is reachable using the new address. After that, use the Oracle ILOM console to access the bare metal system host and run the networking impact report and network modification commands.
set /SP/network pendingipdiscovery=static
set /SP/network pendingipaddress=new-ilom-ip
set /SP/network pendingipgateway=new-ilom-gateway-ip
set /SP/network pendingipnetmask=new-ilom-netmask
set /SP/network commitpending=true After committing the pending settings, verify Oracle ILOM connectivity using the new ILOM IP address.
Prerequisites for Oracle ASR
odacli
modify-networking. Oracle ASR reconfiguration is not performed
automatically as part of odacli modify-networking. Oracle ASR
delete and configure workflow requires actions that cannot be completed in the same
running networking job. Before running odacli modify-networking,
delete the existing Oracle ASR configuration:
odacli delete-asr odacli modify-networking completes successfully,
configure Oracle ASR again: odacli configure-asrThe networking impact report includes an Oracle ASR readiness check.
Prerequisites for Oracle Data Guard
If Oracle Data Guard is configured, review the networking impact report
before running odacli modify-networking. If the database role is
primary on the system where the public network is being modified, perform a planned
switchover before the network change when application availability must be
preserved.
After odacli modify-networking completes, run
odacli modify-dataguard --transport-ips for each impacted
Oracle Data Guard configuration listed in the networking impact report. Run the
command from the system that currently hosts the primary database for that Oracle
Data Guard configuration.
Oracle Data Guard must be configured in MAXIMUM_PERFORMANCE protection mode before running the network change.
Prerequisites for Oracle Key Vault
If Oracle Key Vault-enabled databases are present, review the networking
impact report before the network change. After odacli
modify-networking completes, run odacli
update-okvendpoint for impacted Oracle Key Vault databases before
starting or using those databases. Oracle Key Vault-based databases remain stopped
after the network modification until the Oracle Key Vault endpoint is updated.
Prerequisites for Other Dependencies
- Client-side tnsnames.ora files outside Oracle Database Appliance
- NFS server export rules
Oracle Database Appliance updates only the configuration it manages locally. It does not update external client systems
Prerequisites for Application KVMs
If application KVMs use the affected public network or vNetwork, review the impact report before proceeding. Oracle Database Appliance modifies the host-side network configuration, but it does not manage the network configuration inside application KVMs.
Prerequisites for HANFS and HAVIP
Oracle Database Appliance tooling does not manage the lifecycle of HANFS and HAVIP network changes. Update the affected export and HAVIP configuration manually.
Readiness Report
odacli create-networking-impact-report -r json_pathReview the report output and fix any failed readiness checks before
running odacli modify-networking -r json_path.
Parent topic: Modifying Public Network Configurations
About JSON File Attributes for Network Modification
Learn about the attributes in the JSON file for network changes.
odacli modify-networking and odacli
create-networking-impact-report commands use the same JSON payload format.
The payload describes the target network configuration that you want the system to
validate or apply. When the payload is used with odacli
create-networking-impact-report, the command validates the requested change
and reports the expected impact. When the same payload is used with odacli
modify-networking, the command applies the requested network configuration
changes. The payload can include one or more of the following top-level sections:
- bareMetal: Defines network changes for the bare metal system.
- dbSystems: Defines network changes for one or more DB systems. Each DB system is identified by its DB System name.
- all: Defines DNS and NTP changes that apply to the bare metal system and all DB systems. This section is supported only for DNS and NTP address updates.
Use the payload to specify the new target values for the network configuration. Depending on the change, the payload can include public network details, SCAN configuration, node IP addresses, VIP addresses, gateway, subnet mask, domain name, VLAN ID, DNS servers, and NTP servers.
For same-subnet changes, the payload can include only the components that require modification. For example, you can include only the bare metal system, only selected DB systems, or only DNS and NTP settings.
For different-subnet changes, the payload must include the complete new network configuration for the bare metal system and all affected DB systems that use the network being modified. This is required so that all affected systems are updated consistently and remain reachable after the change.
all section is used only when DNS or NTP settings must be updated
for the bare metal system and all DB systems. Do not use the all section for public IP,
SCAN, VIP, gateway, subnet, domain, network name, vNetwork name, or VLAN ID changes.
- networkName: Name of the existing network to modify, such as Public-network.
- vnetworkName: Name of the existing vNetwork to modify. Use this when the change applies to a vNetwork.
- domainName: Domain name to use for the fully qualified hostnames. The short hostnames are not changed.
- netmask: Subnet mask for the target network configuration.
- vlanId: VLAN ID for an existing VLAN-configured network or vNetwork. This can be used only to change an existing VLAN ID. It cannot convert a non-VLAN network to a VLAN network.
- scanName: SCAN name for the cluster.
- scan.ipAddresses: SCAN IP addresses for the cluster.
- number: Node number.
- name: Hostname of the node. The short hostname is not changed by this operation.
- ipAddress: Target public IP address for the node.
- gateway: Gateway IP address for the target network.
- vipName: VIP hostname for the node.
- vipAddress: Target VIP address for the node.
- networkServices.dnsServers: DNS server IP addresses to configure.
- networkServices.ntpServers: NTP server IP addresses or hostnames to configure.
- all.dnsServers: DNS server IP addresses to apply to the Bare Metal system and all DB Systems.
- all.ntpServers: NTP server IP addresses or hostnames to apply to the bare metal system and all DB systems.
Before running the odacli modify-networking command, update DNS so that
the existing hostnames resolve to the new IP addresses. The new hostname-to-IP mappings
must be available in DNS before the network modification starts.
Use the odacli create-networking-impact-report command with the request
payload before running the odacli modify-networking command. Review the
readiness checks and impacted resources, fix any reported issues, and proceed with the
network change once all readiness checks pass.
Parent topic: Modifying Public Network Configurations
About Networking Impact Report
Learn about the networking impact report.
odacli create-networking-impact-report command to
check whether the system is ready for a planned network change and to see which
components will be affected. The command analyzes the request JSON and generates a
report. The command is available only on the bare metal system. This command does not
make any changes to the system. It only analyzes the request and provides details about:
system readiness for the network change components that will be affected by the change
The command performs the following actions:
- Runs readiness checks on the target system
- Verifies that the environment is ready for the requested network change
- Generates an impact report that lists the affected components
The readiness checks validate that required services, configuration files, and dependent components are in a valid state before the network change is attempted. The checks cover areas such as host network configuration, Oracle Clusterware database status, DB system status, DNS configuration, NTP configuration, and Oracle ASR state, when applicable
The command first runs readiness checks. If one or more readiness checks fail, the command does not generate the networking impact report. Instead, it shows the failed checks, their status, the reason for failure, and the recommended action. Fix the reported issues and run the command again.
odacli
describe-networking-impact-report command displays the failed check details
in the report output, including the check name, status, message, and recommended action.
Review the failure message and follow the suggested action before proceeding. When all
readiness checks pass, odacli describe-networking-impact-report
displays a summary message instead of listing each individual check. The report shows
that all readiness checks passed and provides the command to view the detailed readiness
check results in JSON format. To see the full list of checks performed, run the
odacli describe-networking-impact-report --job-id id --json
command.# odacli describe-networking-impact-report --job-id b09fd718-eafa-4d34-86ee-3434a6fa94be
================================================================================
Networking Impact Report
================================================================================
Report Description:
-------------------
Bare Metal:
Changing public network to the same subnet.
Impacted Interface Name(s):
---------------------------
Bare Metal: pubnet
================================================================================
Networking Readiness Assessment
================================================================================
Bare Metal
------------------------------------------------------------------------------------------------------------------------
Node: odan2
------------------------------------------------------------------------------------------------------------------------
Check Name Status Message Action
---------------------------------------- ---------- ----------------------------------- --------------------------------
DB System status (odadb2) SUCCESS DB system 'odadb2' is None
running
DB System status in metadata SUCCESS DB system 'odadb2' status None
is CONFIGURED
System provisioned SUCCESS System is provisioned None
Network cable and switch port SUCCESS Link detected: yes None
System network configuration file exists SUCCESS System network configuration file None
exists
Network interface configuration file SUCCESS Configuration file exists for None
interface 'pubnet'
Local hosts file exists SUCCESS Local hosts file exists None
ASR exists SUCCESS ASR does not exists None
DNS configuration file exists SUCCESS DNS configuration file exists None
NTP configuration file exists SUCCESS NTP configuration file exists None
Chronyd service exists SUCCESS Chronyd service is present None
Cluster network resource exists SUCCESS Network resource ora.net1.network None
exists
Listener configuration exists SUCCESS Listener configuration file exists None
Clusterware status FAILED Clusterware is not running Start the Clusterware and check
the status using crsctl check
cluster -all
Database status in metadata SUCCESS Database 'Rac2DB' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'RrVTKks4' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'Rac1DB' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvsi' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'odacn' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'ok' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvracdb' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'Rac2DB' is None
running
Database status in metadata SUCCESS Database 'tst' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvrc1' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'Rac1DB' is None
running
Database instance status SUCCESS Database instance 'noeha' is None
running
Database status in metadata SUCCESS Database 'okvvv' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'odacn' is None
running
Database instance status SUCCESS Database instance 'tst' is running None
Database status in metadata SUCCESS Database 'noeha' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'ok' is running None
Database instance status SUCCESS Database instance 'RrVTKks4' is None
running
------------------------------------------------------------------------------------------------------------------------
Node: odan1
------------------------------------------------------------------------------------------------------------------------
Check Name Status Message Action
---------------------------------------- ---------- ----------------------------------- --------------------------------
DB System status (odadb2) SUCCESS DB system 'odab2' is None
running
DB System status in metadata SUCCESS DB system 'odab2' status None
is CONFIGURED
DNS configuration file exists SUCCESS DNS configuration file exists None
Cluster network resource exists SUCCESS Network resource ora.net1.network None
exists
Listener configuration exists SUCCESS Listener configuration file exists None
Clusterware status SUCCESS Clusterware is running on all nodes None
ASR exists SUCCESS ASR does not exists None
System provisioned SUCCESS System is provisioned None
Network cable and switch port SUCCESS Link detected: yes None
System network configuration file exists SUCCESS System network configuration file None
exists
Local hosts file exists SUCCESS Local hosts file exists None
Network interface configuration file SUCCESS Configuration file exists for None
interface 'pubnet'
Chronyd service exists SUCCESS Chronyd service is present None
NTP configuration file exists SUCCESS NTP configuration file exists None
Database status in metadata SUCCESS Database 'noeha' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvvv' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'RrVTKks4' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'noeha' is None
running
Database status in metadata SUCCESS Database 'Rac1DB' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvracdb' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'Rac2DB' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'ok' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvsi' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'okvrc1' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'tst' is running None
Database status in metadata SUCCESS Database 'tst' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'RrVTKks4' is None
running
Database instance status SUCCESS Database instance 'Rac2DB' is None
running
Database instance status SUCCESS Database instance 'Rac1DB' is None
running
Database status in metadata SUCCESS Database 'odacn' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'odacn' is None
running
Database instance status SUCCESS Database instance 'ok' is running None
------------------------------------------------------------------------------------------------------------------------
DB System: odadb2
------------------------------------------------------------------------------------------------------------------------
Node: odanode2
------------------------------------------------------------------------------------------------------------------------
Check Name Status Message Action
---------------------------------------- ---------- ----------------------------------- --------------------------------
System network configuration file exists SUCCESS System network configuration file None
exists
Network interface configuration file SUCCESS Configuration file exists for None
interface 'enp0s3'
System provisioned SUCCESS System is provisioned None
Local hosts file exists SUCCESS Local hosts file exists None
DNS configuration file exists SUCCESS DNS configuration file exists None
Database instance status SUCCESS Database instance 'db3u' is running None
Database status in metadata SUCCESS Database 'db3u' status is None
'CONFIGURED'
Database status in metadata SUCCESS Database 'utst' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'utst' is running None
NTP configuration file exists FAILED NTP configuration file Investigate the reason why the
(/etc/chrony.conf) is missing. configuration file is missing
and restore /etc/chrony.conf
Chronyd service exists SUCCESS Chronyd service is present None
ASR exists SUCCESS ASR does not exists None
Clusterware status SUCCESS Clusterware is running on all nodes None
Cluster network resource exists SUCCESS Network resource ora.net1.network None
exists
Listener configuration exists SUCCESS Listener configuration file exists None
------------------------------------------------------------------------------------------------------------------------
Node: odan12
------------------------------------------------------------------------------------------------------------------------
Check Name Status Message Action
---------------------------------------- ---------- ----------------------------------- --------------------------------
DNS configuration file exists SUCCESS DNS configuration file exists None
ASR exists SUCCESS ASR does not exists None
Clusterware status SUCCESS Clusterware is running on all nodes None
Cluster network resource exists SUCCESS Network resource ora.net1.network None
exists
Listener configuration exists SUCCESS Listener configuration file exists None
Local hosts file exists SUCCESS Local hosts file exists None
System network configuration file exists SUCCESS System network configuration file None
exists
System provisioned SUCCESS System is provisioned None
Network interface configuration file SUCCESS Configuration file exists for None
interface 'enp0s3'
Chronyd service exists SUCCESS Chronyd service is present None
NTP configuration file exists SUCCESS NTP configuration file exists None
Database status in metadata SUCCESS Database 'utst' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'db3u' is running None
Database status in metadata SUCCESS Database 'db3u' status is None
'CONFIGURED'
Database instance status SUCCESS Database instance 'utst' is running None
------------------------------------------------------------------------------------------------------------------------If all readiness checks pass, the command generates the networking impact report. The report describes the components that will be affected by the requested network change and the expected impact on those components during the network change. If all readiness checks pass, the report includes a report description, the impacted interface name or names, a readiness assessment summary, and the list of impacted resources When all readiness checks pass, the readiness assessment section shows a summary message.
# odacli describe-networking-impact-report -i 4ea7d000-b022-4bde-92dd-4139a28118de
================================================================================
Networking Impact Report
================================================================================
Report Description:
-------------------
Bare Metal:
Changing public network to the same subnet. Impacted components are: Dataguards, Databases, Grid,
Objectstore backup, TFA service, SSH equivalence, Application KVMs, DNS and NTP
DB System odadb1:
Changing
public network to the same subnet. Impacted components are: Network interface, Databases, Grid, Objectstore backup,
TFA service, SSH equivalence, DNS and NTP
Impacted Interface Name(s):
---------------------------
Bare Metal: pubnet, DB System scaoda11ha20c2: enp0s3
================================================================================
Networking Readiness Assessment
================================================================================
- All readiness checks passed.
- To view a detailed list of the checks performed, execute:
odacli describe-networking-impact-report --job-id <id> --json
================================================================================
Networking Impacted Resources
================================================================================
Bare Metal
------------------------------------------------------------------------------------------------------------------------
Node: odan1
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Rac1DB RACOne database Database instance (Rac1DB_1) stops before the network change and
starts again after the network change completes.
Database services restart to re-register with the newly configured
listeners.
- Rac1DB_racone
Connection attempts using service names fail during network
modification.
Rac2DB RACOne database Database services restart to re-register with the newly configured
listeners.
- Rac2DB_racone
Connection attempts using service names fail during network
modification.
Database instance (Rac2DB_1) stops before the network change and
starts again after the network change completes.
noeha SI database Database instance (noeha) remains running during the network change
while database listener configuration is updated and database
services are re-registered with the new listeners. Local database
access remains available, but existing remote client connections
disconnect during listener restart.
odacn RAC database Database instances (odacn1, odacn2) remain running during the
network change while database listener configuration is updated and
database services are re-registered with the new listeners. Local
database access remains available, but existing remote client
connections disconnect during listener restart.
ok SI database Database instance (ok) stops before the network change and starts
again after the network change completes. Database listener
configuration is updated and database services are re-registered
with the new listeners. Local database connections resume after the
database starts, and existing remote client connections disconnect
during listener restart.
Database services restart to re-register with the newly configured
listeners.
- ok_ro
- ok_rw
- POK_ro
- POK_rw
Connection attempts using service names fail during network
modification.
dg-ok Data Guard Data Guard reconfiguration requires following sequence:
1. First switch over to standby to maintain application
availability while the primary network is under modification
2. Submit 'odacli modify-networking' to assign new network
configurations
3. Execute 'odacli modify-dataguard --transport-ips' to restore
redo transport
4. Optionally, switch back to the original primary role.
srvapp01 ODA Application KVMs Application KVM 'srvapp01' is unreachable during network
modification. Host network changes affects Application KVM
connectivity. ODA does not manage network configuration inside the
guest.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_SCAN2.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.qosmserver Oracle QoS Management The QoS Management service restarts to apply the new network
configuration. Automated performance policies and cluster
monitoring are suspended until the service restart completes.
ora.scan2.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.odan1.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
Impacted databases are: ok, odacn, RrVTKks4
------------------------------------------------------------------------------------------------------------------------
Node: odan2
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
RrVTKks4 SI database Database instance (RrVTKks4) stops before the network change and
starts again after the network change completes. Database listener
configuration is updated and database services are re-registered
with the new listeners. Local database connections resume after the
database starts, and existing remote client connections disconnect
during listener restart.
odacn RAC database Database instances (odacn1, odacn2) remain running during the
network change while database listener configuration is updated and
database services are re-registered with the new listeners. Local
database access remains available, but existing remote client
connections disconnect during listener restart.
tst SI database Database instance (tst) stops before the network change and starts
again after the network change completes. Database listener
configuration is updated and database services are re-registered
with the new listeners. Local database connections resume after the
database starts, and existing remote client connections disconnect
during listener restart.
srvapp01 ODA Application KVMs Application KVM 'srvapp01' is unreachable during network
modification. Host network changes affects Application KVM
connectivity. ODA does not manage network configuration inside the
guest.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_SCAN1.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.scan1.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.scaoda11ha20c1n2.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
ora.souravhavip.havip Oracle HA VIP resource This resource is not managed by ODA tooling. The network change
impacts this resource.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
Impacted databases are: ok, odacn, RrVTKks4
------------------------------------------------------------------------------------------------------------------------
DB System: odadb1
------------------------------------------------------------------------------------------------------------------------
Node: odan1
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Bridge network interface Bridge network interface Network interface 'enp0s3' restarts to apply configuration changes.
db3u RAC database Database instances (db31, db32) remain running during the network
change while database listener configuration is updated and
database services are re-registered with the new listeners. Local
database access remains available, but existing remote client
connections disconnect during listener restart.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_SCAN1.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.LISTENER_SCAN2.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.scan1.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.scan2.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.odan1.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
------------------------------------------------------------------------------------------------------------------------
Node: odan2
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Bridge network interface Bridge network interface Network interface 'enp0s3' restarts to apply configuration changes.
db3u RAC database Database instances (db31, db32) remain running during the network
change while database listener configuration is updated and
database services are re-registered with the new listeners. Local
database access remains available, but existing remote client
connections disconnect during listener restart.
utst SI database Database services restart to re-register with the newly configured
listeners.
- ok_ro
- ok_rw
- POK_ro
- POK_rw
Connection attempts using service names fail during network
modification.
Database instance (utst) stops before the network change and starts
again after the network change completes. Database listener
configuration is updated and database services are re-registered
with the new listeners. Local database connections resume after the
database starts, and existing remote client connections disconnect
during listener restart.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.qosmserver Oracle QoS Management The QoS Management service restarts to apply the new network
configuration. Automated performance policies and cluster
monitoring are suspended until the service restart completes.
ora.odan2.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
------------------------------------------------------------------------------------------------------------------------odacli describe-networking-impact-report --job-id
job_id command generates the networking impact report. The report
contains two section - Readiness checks and Impact description on the components.
- Networking Readiness Assessment: Performs readiness checks for all impacted targets identified in the JSON file, including bare metal system and each impacted DB system, across their corresponding nodes.
- Networking Impacted Resources: Lists the resources affected by the networking change and describes the expected impact on each resource.
To view the complete list of checks that were performed, run the
odacli describe-networking-impact-report --job-id job_id
--json. If any readiness check fails, the output displays the failed check
details directly in the report output, including the check name, status message, and
recommended action.
Network changes can affect multiple components, including databases,
listeners, Oracle Clusterware resources, DB systems, DNS, NTP, and Oracle Data
Guard-related configuration. Run the impact report before you run the odacli
modify-networking command so that you can confirm the system is ready and
understand the expected impact before making the change. Proceed with the network change
only after all readiness checks pass.
After readiness checks, the command identifies all components that will be affected by the network change. This includes databases, database services, Oracle Data Guard configurations, Oracle Clusterware resources such as SCAN, VIP, network, DNS and NTP services, DB systems, Oracle TFA and other system services, application KVMs, HANFS and HAVIP, Oracle ASR, and SSH equivalence.
For each impacted resource, the report describes what will happen during the
change and whether resource will restart. A detailed view of all checks can be obtained
using the --json option.
Networking Readiness Checks
The networking readiness checks validate whether the environment is prepared for the requested networking change. These checks are performed before running the network modification operation to identify issues that could block the operation or cause it to fail. If a check fails, review the message and complete the recommended action before proceeding. The checks are grouped by component for easy identification of the affected area, such as the host, database, DB system, Oracle Grid infrastructure, NTP, or DNS.
Host Checks:
These checks validate that the host has the required network configuration files and physical network connectivity needed for the operation.
Table 12-3 Host Checks
| Readiness Check | Error Message | Action |
|---|---|---|
| Network interface configuration file exists | The network interface configuration file
/etc/sysconfig/network-script/ifcfg-pubnet is
missing.
|
Investigate the reason why the configuration file is missing and
restore
/etc/sysconfig/network-script/ifcfg-pubnet.
|
| Local hosts file exists | The local hosts file /etc/hosts is
missing.
|
Investigate the reason why the configuration file is missing and
restore /etc/hosts.
|
| System network configuration file exists | The system network configuration file
/etc/sysconfig/network is missing.
|
Investigate the reason why the configuration file is missing and
restore /etc/sysconfig/network.
|
| Network cable and switch port connectivity | The network interface does not detect a physical network connection. | Verify that the network cable is connected to the switch port.
Run the ethtool interfacename command and
confirm that it reports Link detected: yes.
|
Database Checks:
These checks validate that the database is in a valid state and accessible so that network-related updates can be applied successfully. Database instance status check is only applicable for non-Oracle Key Vault databases.
Table 12-4 Database Checks
| Readiness Check | Error Message | Action |
|---|---|---|
| Database status | The database status is NOT CONFIGURED in metadata and the operation cannot proceed. | Investigate why the database is in the NOT CONFIGURED state. Or, if the database is not required, delete the database. |
| Database instance status | Cannot connect to the instance to update the network configuration. | Start the database instance. |
DB System Checks:
These checks validate that the DB system is available and correctly configured in metadata before network changes are applied.
Table 12-5 DB System Checks
| Readiness Check | Error Message | Action |
|---|---|---|
| DB system status | The DB system must be running to perform network configuration changes. | Start the DB system. |
| DB system metadata status | The DB system status is not CONFIGURED in metadata and the operation cannot proceed. | Investigate why the DB system status is NOT CONFIGURED. Resolve the issue. If the DB system is not required, delete the DB system. |
Oracle Grid Infrastructure Checks:
These checks validate that the Oracle Grid Infrastructure components are available and correctly configured in metadata before network changes are applied.
Table 12-6 Oracle Grid Infrastructure Checks
| Readiness Check | Error Message | Action |
|---|---|---|
| Oracle Clusterware status | Oracle Clusterware is not running | Start Oracle Clusterware and check the status using the command
crsctl check cluster -all.
|
| Listener configuration exists | Listener configuration file
/u01/app/grid_version/grid/network/admin/listener.ora
is missing.
|
Investigate why the listener configuration file is missing and restore the file. |
| SCAN listener entries exists | SCAN listener entries are missing from the
listener.ora file.
|
Investigate the Oracle Grid Infrastructure listener configuration and restore the missing SCAN listener entries. |
| Cluster network resource exists | Oracle Clusterware network resource
ora.net1.network is missing.
|
Investigate why the network resource is missing and restore the network resource |
NTP Checks:
These checks validate that NTP services and configuration files are available so time synchronization settings can be updated if needed.
Table 12-7 NTP Checks
| Readiness Check | Error Message | Action |
|---|---|---|
| chronyd service exists | The chronyd service is not present on the system, and NTP configuration cannot be modified. | Investigate why the chronyd service is missing and restore it. Or, remove the NTP configuration from the request payload. |
| NTP configuration file exists | NTP configuration file /etc/chrony.conf is
missing.
|
Investigate the reason why the configuration file is missing and
restore the /etc/chrony.conf file.
|
DNS Checks:
These checks validate that the DNS configuration required for hostname resolution is present before the network change is applied.
Table 12-8 DNS Checks
| Readiness Check | Error Message | Action |
|---|---|---|
| DNS configuration file exists | The DNS configuration file /etc/resolv.conf is
missing.
|
Investigate the reason why the configuration file is missing and
restore /etc/resolv.conf.
|
Parent topic: Modifying Public Network Configurations
Modifying Network Configuration
Use ODACLI commands to modify public network settings, DNS, and NTP configurations, as well as to generate and manage public Networking Impact Reports.
Creating and viewing networking impact report and modifying network
# odacli create-networking-impact-report -r json_file_path# odacli create-networking-impact-report --requestjson path/to/input.json
Job details
----------------------------------------------------------------
ID: e3f902cd-8ce1-4c75-90d2-1fa639db734b
Description: Networking Impact Report
Status: Created
Created: May 13, 2026 13:13:05 UTC
Message: Use 'odacli describe-networking-impact-report --job-id e3f902cd-8ce1-4c75-90d2-1fa639db734b' to check detailed report
Task Name Start Time End Time Status
------------------ -------------------- ----------------------------------------
# odacli describe-networking-impact-report --job-id e3f902cd-8ce1-4c75-90d2-1fa639db734b
Job details
----------------------------------------------------------------
ID: e3f902cd-8ce1-4c75-90d2-1fa639db734b
Description: Networking Impact Report
Status: Success
Created: May 13, 2026 13:13:05 UTC
Message:
Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- ----------------
Execute networking readiness checks oda_bmha1 May 13, 2026 13:13:14 UTC May 13, 2026 13:13:27 UTC Success
Collect Data Guard information oda_bmha1 May 13, 2026 13:13:27 UTC May 13, 2026 13:13:28 UTC Success
Collect network interface information oda_bmha1 May 13, 2026 13:13:27 UTC May 13, 2026 13:13:27 UTC Success
Validate readiness report oda_bmha1 May 13, 2026 13:13:27 UTC May 13, 2026 13:13:27 UTC Success
Collect database information oda_bmha1 May 13, 2026 13:13:28 UTC May 13, 2026 13:13:52 UTC Success
Collect Clusterware resource information oda_bmha1 May 13, 2026 13:13:52 UTC May 13, 2026 13:14:26 UTC Success
Collect ASR information oda_bmha1 May 13, 2026 13:14:27 UTC May 13, 2026 13:14:27 UTC Success
Collect Application VM information oda_bmha1 May 13, 2026 13:14:27 UTC May 13, 2026 13:14:27 UTC Success
Collect DNS information oda_bmha1 May 13, 2026 13:14:27 UTC May 13, 2026 13:14:27 UTC Success
Collect SSH equivalence information oda_bmha1 May 13, 2026 13:14:27 UTC May 13, 2026 13:14:27 UTC Success
Collect TFA information oda_bmha1 May 13, 2026 13:14:27 UTC May 13, 2026 13:14:27 UTC Success
Collect database backup configuration oda_bmha1 May 13, 2026 13:14:27 UTC May 13, 2026 13:14:27 UTC Success
Collect NTP information oda_bmha1 May 13, 2026 13:14:28 UTC May 13, 2026 13:14:28 UTC Success# odacli describe-networking-impact-report# odacli describe-networking-impact-report -i dd855efc-87bf-4e5d-9727-aa3094bee611
================================================================================
Networking Impact Report
================================================================================
Report Description:
-------------------
Bare Metal:
Changing public network to the same subnet. Impacted components are: Network interface, Dataguards,
Databases, Grid, Objectstore backup, TFA service, SSH equivalence, Application KVMs, DNS and NTP
DB System
oda_dbsystem1:
Changing public network to the same subnet. Impacted components are: Network interface, Databases,
Grid, Objectstore backup, TFA service, SSH equivalence, DNS and NTP
Impacted Interface Name(s):
---------------------------
Bare Metal: pubnet, DB System dbsystem1: enp0s3
================================================================================
Networking Readiness Assessment
================================================================================
- All readiness checks passed.
- To view a detailed list of the checks performed, execute:
odacli describe-networking-impact-report --job-id <id> --json
================================================================================
Networking Impacted Resources
================================================================================
Bare Metal
------------------------------------------------------------------------------------------------------------------------
Node: oda_bm_1
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Bridge network interface Bridge network interface Network interface 'pubnet' restarts to apply configuration changes.
Rac1DB RACOne database Database services restart to re-register with the newly configured
listeners.
- Rac1DB_racone
Connection attempts using service names fail during network
modification.
Database instance (Rac1DB_1) stops before the network change and
starts again after the network change completes.
Rac2DB RACOne database Database instance (Rac2DB_1) stops before the network change and
starts again after the network change completes.
Database services restart to re-register with the newly configured
listeners.
- Rac2DB_racone
Connection attempts using service names fail during network
modification.
noeha SI database Database instance (noeha) remains running during the network change
while database listener configuration changes and database services
re-register with the new listeners. Local connections on the
database host remain available. Existing remote client connections
disconnect during listener restart.
odacn RAC database Database services restart to re-register with the newly configured
listeners.
- sauravapp.us.oracle.com
- souravtst.us.oracle.com
Connection attempts using service names fail during network
modification.
Database instances (odacn1, odacn2) remain running during the
network change while database listener configuration changes and
database services re-register with the new listeners. Local
connections on the database host remain available. Existing remote
client connections disconnect during listener restart.
ok SI database Database instance (ok) stops before the network change and starts
again after the network change completes. Database listener
configuration changes and database services re-register with the
new listeners. Local connections on the database host resume after
the database starts. Existing remote client connections disconnect
during listener restart.
Database services restart to re-register with the newly configured
listeners.
- ok_ro
- ok_rw
- POK_ro
- POK_rw
Connection attempts using service names fail during network
modification.
okvracdb RAC database Database instance (okvracdb1, okvracdb2) stops before the network
change and remains stopped after the network change completes. Run
'odacli update-okvendpoints' after 'odacli modify-networking' to
update database endpoints and restore Oracle Key Vault
connectivity. Start the database after 'odacli update-okvendpoints'
completes.
okvrc1 RACOne database Database services restart to re-register with the newly configured
listeners.
- okvrc1_racone
Connection attempts using service names fail during network
modification.
Database instance (okvrc1_1) stops before the network change and
remains stopped after the network change completes. Run 'odacli
update-okvendpoints' after 'odacli modify-networking' to update
database endpoints and restore Oracle Key Vault connectivity. Start
the database after 'odacli update-okvendpoints' completes.
okvsi SI database Database instance (okvsi) stops before the network change and
remains stopped after the network change completes. Run 'odacli
update-okvendpoints' after 'odacli modify-networking' to update
database endpoints and restore Oracle Key Vault connectivity. Start
the database after 'odacli update-okvendpoints' completes.
okvvv RAC database Database services restart to re-register with the newly configured
listeners.
- okvvv_app_svc.us.oracle.com
Connection attempts using service names fail during network
modification.
Database instance (okvvv1, okvvv2) stops before the network change
and remains stopped after the network change completes. Run 'odacli
update-okvendpoints' after 'odacli modify-networking' to update
database endpoints and restore Oracle Key Vault connectivity. Start
the database after 'odacli update-okvendpoints' completes.
dg-ok Data Guard Data Guard reconfiguration requires following sequence:
1. First switch over to standby to maintain application
availability while the primary network is under modification
2. Submit 'odacli modify-networking' to assign new network
configurations
3. Execute 'odacli modify-dataguard --transport-ips' to restore
redo transport
4. Optionally, switch back to the original primary role.
srvapp01 ODA Application KVMs Application KVM 'srvapp01' is unreachable during network
modification. Host network changes affects Application KVM
connectivity. ODA does not manage network configuration inside the
guest.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_NET1_APP.lsn Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_SCAN2.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.qosmserver Oracle QoS Management The QoS Management service restarts to apply the new network
configuration. Automated performance policies and cluster
monitoring are suspended until the service restart completes.
ora.scan2.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.odanode1.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
Impacted databases are: ok, odacn, RrVTKks4
------------------------------------------------------------------------------------------------------------------------
Node: oda_bm_2
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Bridge network interface Bridge network interface Network interface 'pubnet' restarts to apply configuration changes.
RrVTKks4 SI database Database instance (RrVTKks4) stops before the network change and
starts again after the network change completes. Database listener
configuration changes and database services re-register with the
new listeners. Local connections on the database host resume after
the database starts. Existing remote client connections disconnect
during listener restart.
odacn RAC database Database services restart to re-register with the newly configured
listeners.
- sauravapp.us.oracle.com
- souravtst.us.oracle.com
Connection attempts using service names fail during network
modification.
Database instances (odacn1, odacn2) remain running during the
network change while database listener configuration changes and
database services re-register with the new listeners. Local
connections on the database host remain available. Existing remote
client connections disconnect during listener restart.
okvracdb RAC database Database instance (okvracdb1, okvracdb2) stops before the network
change and remains stopped after the network change completes. Run
'odacli update-okvendpoints' after 'odacli modify-networking' to
update database endpoints and restore Oracle Key Vault
connectivity. Start the database after 'odacli update-okvendpoints'
completes.
okvvv RAC database Database services restart to re-register with the newly configured
listeners.
- okvvv_app_svc.us.oracle.com
Connection attempts using service names fail during network
modification.
Database instance (okvvv1, okvvv2) stops before the network change
and remains stopped after the network change completes. Run 'odacli
update-okvendpoints' after 'odacli modify-networking' to update
database endpoints and restore Oracle Key Vault connectivity. Start
the database after 'odacli update-okvendpoints' completes.
tst SI database Database instance (tst) stops before the network change and starts
again after the network change completes. Database listener
configuration changes and database services re-register with the
new listeners. Local connections on the database host resume after
the database starts. Existing remote client connections disconnect
during listener restart.
srvapp01 ODA Application KVMs Application KVM 'srvapp01' is unreachable during network
modification. Host network changes affects Application KVM
connectivity. ODA does not manage network configuration inside the
guest.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_NET1_APP.lsn Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_SCAN1.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.scan1.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.odan2.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
ora.havip.havip Oracle HA VIP resource This resource is not managed by ODA tooling. The network change
impacts this resource.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
Impacted databases are: ok, odacn, RrVTKks4
------------------------------------------------------------------------------------------------------------------------
DB System: oda_dbsystem1
------------------------------------------------------------------------------------------------------------------------
Node: oda_dbsystem1_node1
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Bridge network interface Bridge network interface Network interface 'enp0s3' restarts to apply configuration changes.
db3u RAC database Database instances (db31, db32) remain running during the network
change while database listener configuration changes and database
services re-register with the new listeners. Local connections on
the database host remain available. Existing remote client
connections disconnect during listener restart.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.LISTENER_SCAN1.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.LISTENER_SCAN2.lsnr Oracle SCAN listener The SCAN listener restarts to apply the new network configuration.
Existing remote connections using SCAN are disconnected. New remote
connection attempts using SCAN fail until the restart completes.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.scan1.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.scan2.vip Oracle SCAN VIP resource The SCAN restarts with the new SCAN IP addresses. Existing remote
connections using SCAN are disconnected. New remote connection
attempts using SCAN fail until the restart completes.
ora.node1.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
------------------------------------------------------------------------------------------------------------------------
Node: oda_dbsystem1_node2
------------------------------------------------------------------------------------------------------------------------
Resource Name Resource Description Impact Description
------------------------- ------------------------- --------------------------------------------------------------------
Bridge network interface Bridge network interface Network interface 'enp0s3' restarts to apply configuration changes.
db3u RAC database Database instances (db31, db32) remain running during the network
change while database listener configuration changes and database
services re-register with the new listeners. Local connections on
the database host remain available. Existing remote client
connections disconnect during listener restart.
utst SI database Database services restart to re-register with the newly configured
listeners.
- ok_ro
- ok_rw
- POK_ro
- POK_rw
Connection attempts using service names fail during network
modification.
Database instance (utst) stops before the network change and starts
again after the network change completes. Database listener
configuration changes and database services re-register with the
new listeners. Local connections on the database host resume after
the database starts. Existing remote client connections disconnect
during listener restart.
SSH Equivalence Passwordless SSH The existing SSH equivalence will be cleaned up as part of the
modify-networking execution.
ora.LISTENER.lsnr Oracle Listener resource The listener restarts with the new VIP address and SCAN addresses
Existing remote connections are disconnected, and new remote
connection attempts fail until the listener restart completes with
the new VIP and SCAN addresses.
ora.net1.network Oracle Network resource Network resource restarts to apply the new network configuration.
Updated attributes include subnet mask, gateway, and subnet ID.
ora.ons Oracle ONS resource ONS restarts to bind to the new network configuration. Event
notification delivery is interrupted until the service becomes
available again.
ora.qosmserver Oracle QoS Management The QoS Management service restarts to apply the new network
configuration. Automated performance policies and cluster
monitoring are suspended until the service restart completes.
ora.odan2.vip Oracle VIP resource The VIP is unreachable during the network change. Existing remote
database sessions are terminated, and new remote connection
attempts fail.
NTP Service NTP service synchronizes The system assigns new NTP server addresses. The chronyd service
restarts to synchronize with the new time sources.
DNS Service Provides hostname-to-IP The system assigns new DNS server addresses. Hostname-to-IP
resolution (nslookup) is unavailable during DNS modification.
Trace File Analyzer Oracle TFA service The TFA service restarts to apply the new public IP addresses.
Diagnostics collection is unavailable during the restart.
myconfig Object Store backup During the 'odacli modify-networking' execution, scheduled backups
for 'myconfig' cannot be performed. Following a successful
completion of the operation, backup jobs will resume normally.
------------------------------------------------------------------------------------------------------------------------# odacli list-networking-impact-reports# odacli list-networking-impact-reports
ID Description Created Status
---------------------------------------- --------------------------------------------------------------------------- ----------------------------------- ----------------
a16df2c6-7f4f-4cad-bb8c-803a53da4140 Networking Impact Report 2026-04-16 18:18:22 UTC Success
dd855efc-87bf-4e5d-9727-aa3094bee611 Networking Impact Report 2026-04-20 16:41:50 UTC Success
6dbcda9b-c185-43ea-b49d-eee820c7cc4d Networking Impact Report 2026-05-07 13:09:49 UTC SuccessUse the odacli delete-networking-impact-report command
to delete a previously generated networking impact report. Specify the report job ID to
remove the report from the system. The delete-networking-impact-report operation does not
submit a DCS job. Therefore, no new job ID is generated and there is no job to view using
odacli describe-job. The command waits for the networking impact report
deletion to complete and exits after the report is deleted.
# odacli delete-networking-impact-report# odacli delete-networking-impact-report -i 521e4e22-aaf5-4945-b214-309c7d855fe5# odacli modify-networking -r json_file_path# odacli modify-networking --requestjson path/to/input.json
Job details
----------------------------------------------------------------
ID: cd4be2f9-83a0-41b6-aeea-8dd0c4d2f74e
Description: Modify Networking Request
Status: Created
Created: May 13, 2026 13:13:56 UTC
Message:
# odacli describe-job -i cd4be2f9-83a0-41b6-aeea-8dd0c4d2f74e
odacli describe-job -i cd4be2f9-83a0-41b6-aeea-8dd0c4d2f74e
Job details
----------------------------------------------------------------
ID: cd4be2f9-83a0-41b6-aeea-8dd0c4d2f74e
Description: Modify Networking Request
Status: Success
Created: May 13, 2026 13:13:56 UTC
Message:
Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- ----------------
Execute networking readiness checks oda_bm2 May 13, 2026 13:14:10 UTC May 13, 2026 13:14:18 UTC Success
Stop database 'kkUIxBYc' oda_bm1 May 13, 2026 13:14:18 UTC May 13, 2026 13:14:38 UTC Success
Stop database 'upJHXf6' oda_bm1 May 13, 2026 13:14:18 UTC May 13, 2026 13:14:46 UTC Success
Modify VLAN configuration oda_bm1 May 13, 2026 13:14:46 UTC May 13, 2026 13:14:58 UTC Success
Modify network interface 'pubnet' oda_bm1 May 13, 2026 13:14:58 UTC May 13, 2026 13:14:58 UTC Success
configuration
Start network interface 'pubnet' oda_bm1 May 13, 2026 13:14:59 UTC May 13, 2026 13:15:05 UTC Success
Stop network interface 'pubnet' oda_bm1 May 13, 2026 13:14:59 UTC May 13, 2026 13:14:59 UTC Success
Add entries to /etc/hosts oda_bm2 May 13, 2026 13:15:05 UTC May 13, 2026 13:15:05 UTC Success
Modify DNS configuration oda_bm2 May 13, 2026 13:15:05 UTC May 13, 2026 13:15:06 UTC Success
Modify gateway IP address oda_bm1 May 13, 2026 13:15:05 UTC May 13, 2026 13:15:05 UTC Success
Modify host domain name oda_bm1 May 13, 2026 13:15:05 UTC May 13, 2026 13:15:05 UTC Success
Validate availability of 'pubnet' oda_bm1 May 13, 2026 13:15:05 UTC May 13, 2026 13:15:05 UTC Success
Restart Name Service Cache Daemon oda_bm2 May 13, 2026 13:15:06 UTC May 13, 2026 13:15:06 UTC Success
Modify Chrony configuration oda_bm2 May 13, 2026 13:15:07 UTC May 13, 2026 13:15:08 UTC Success
Modify Clusterware public network oda_bm1 May 13, 2026 13:15:08 UTC May 13, 2026 13:15:23 UTC Success
configuration
Validate CRS resource oda_bm1 May 13, 2026 13:15:23 UTC May 13, 2026 13:17:39 UTC Success
'ora.net1.network' is ONLINE
Modify SCAN configuration oda_bm1 May 13, 2026 13:17:39 UTC May 13, 2026 13:18:05 UTC Success
Start SCAN VIP ora.scan1.vip oda_bm1 May 13, 2026 13:18:05 UTC May 13, 2026 13:18:06 UTC Success
Start SCAN listener oda_bm1 May 13, 2026 13:18:06 UTC May 13, 2026 13:18:06 UTC Success
ora.SCANLSNR_SCAN1.lsnr
Validate CRS resource 'ora.scan1.vip' oda_bm1 May 13, 2026 13:18:06 UTC May 13, 2026 13:18:07 UTC Success
is ONLINE
Validate CRS resource oda_bm1 May 13, 2026 13:18:07 UTC May 13, 2026 13:18:53 UTC Success
'ora.LISTENER_SCAN1.lsnr' is ONLINE
Start SCAN VIP ora.scan2.vip oda_bm1 May 13, 2026 13:18:53 UTC May 13, 2026 13:18:53 UTC Success
Start SCAN listener oda_bm1 May 13, 2026 13:18:53 UTC May 13, 2026 13:18:54 UTC Success
ora.SCANLSNR_SCAN2.lsnr
Modify node VIP configuration oda_bm1 May 13, 2026 13:18:54 UTC May 13, 2026 13:18:58 UTC Success
Validate CRS resource oda_bm1 May 13, 2026 13:18:54 UTC May 13, 2026 13:18:54 UTC Success
'ora.LISTENER_SCAN2.lsnr' is ONLINE
Validate CRS resource 'ora.scan2.vip' oda_bm1 May 13, 2026 13:18:54 UTC May 13, 2026 13:18:54 UTC Success
is ONLINE
Modify CRS configuration parameter file oda_bm2 May 13, 2026 13:18:58 UTC May 13, 2026 13:18:59 UTC Success
Start node VIP oda_bm1 May 13, 2026 13:18:58 UTC May 13, 2026 13:18:58 UTC Success
ora.oda_bm1.vip
Validate CRS resource oda_bm1 May 13, 2026 13:18:58 UTC May 13, 2026 13:18:58 UTC Success
'ora.oda_bm1.vip' is ONLINE
Restart listener oda_bm1 May 13, 2026 13:18:59 UTC May 13, 2026 13:19:01 UTC Success
Remove entries from /etc/hosts oda_bm2 May 13, 2026 13:19:01 UTC May 13, 2026 13:19:01 UTC Success
Add entries to /etc/hosts oda_bm2 May 13, 2026 13:19:02 UTC May 13, 2026 13:19:02 UTC Success
Persist SysInstance metadata oda_bm2 May 13, 2026 13:19:02 UTC May 13, 2026 13:19:02 UTC Success
Persist vNetwork metadata 'pubnet' oda_bm1 May 13, 2026 13:19:03 UTC May 13, 2026 13:19:03 UTC Success
Discover and persist ILOM metadata oda_bm1 May 13, 2026 13:19:04 UTC May 13, 2026 13:19:06 UTC Success
Modify VLAN configuration oda_bm2 May 13, 2026 13:19:06 UTC May 13, 2026 13:19:18 UTC Success
Modify network interface 'pubnet' oda_bm2 May 13, 2026 13:19:18 UTC May 13, 2026 13:19:18 UTC Success
configuration
Stop network interface 'pubnet' oda_bm2 May 13, 2026 13:19:18 UTC May 13, 2026 13:19:19 UTC Success
Start network interface 'pubnet' oda_bm2 May 13, 2026 13:19:19 UTC May 13, 2026 13:19:24 UTC Success
Modify host domain name oda_bm2 May 13, 2026 13:19:24 UTC May 13, 2026 13:19:25 UTC Success
Validate availability of 'pubnet' oda_bm2 May 13, 2026 13:19:24 UTC May 13, 2026 13:19:24 UTC Success
Add entries to /etc/hosts oda_bm2 May 13, 2026 13:19:25 UTC May 13, 2026 13:19:25 UTC Success
Modify DNS configuration oda_bm2 May 13, 2026 13:19:25 UTC May 13, 2026 13:19:25 UTC Success
Modify gateway IP address oda_bm2 May 13, 2026 13:19:25 UTC May 13, 2026 13:19:25 UTC Success
Restart Name Service Cache Daemon oda_bm2 May 13, 2026 13:19:26 UTC May 13, 2026 13:19:26 UTC Success
Modify Chrony configuration oda_bm2 May 13, 2026 13:19:27 UTC May 13, 2026 13:19:27 UTC Success
Validate CRS resource oda_bm2 May 13, 2026 13:19:27 UTC May 13, 2026 13:20:13 UTC Success
'ora.net1.network' is ONLINE
Modify node VIP configuration oda_bm2 May 13, 2026 13:20:13 UTC May 13, 2026 13:20:16 UTC Success
Start node VIP oda_bm2 May 13, 2026 13:20:16 UTC May 13, 2026 13:20:17 UTC Success
ora.oda_bm2.vip
Modify Oracle Interface Configuration oda_bm2 May 13, 2026 13:20:17 UTC May 13, 2026 13:20:19 UTC Success
(OIFCFG)
Validate CRS resource oda_bm2 May 13, 2026 13:20:17 UTC May 13, 2026 13:20:17 UTC Success
'ora.oda_bm2.vip' is ONLINE
Modify CRS configuration parameter file oda_bm2 May 13, 2026 13:20:19 UTC May 13, 2026 13:20:19 UTC Success
Restart listener oda_bm2 May 13, 2026 13:20:19 UTC May 13, 2026 13:20:23 UTC Success
Remove entries from /etc/hosts oda_bm2 May 13, 2026 13:20:23 UTC May 13, 2026 13:20:23 UTC Success
Add entries to /etc/hosts oda_bm2 May 13, 2026 13:20:24 UTC May 13, 2026 13:20:24 UTC Success
Delete SSH equivalence for user odaadmin oda_bm2 May 13, 2026 13:20:24 UTC May 13, 2026 13:20:25 UTC Success
Delete SSH equivalence for user yoracle oda_bm2 May 13, 2026 13:20:24 UTC May 13, 2026 13:20:24 UTC Success
Delete SSH equivalence for user oda_bm2 May 13, 2026 13:20:25 UTC May 13, 2026 13:20:25 UTC Success
qaemrqorljojr0zw
Delete SSH equivalence for user root oda_bm2 May 13, 2026 13:20:25 UTC May 13, 2026 13:20:25 UTC Success
Restart Trace File Analyzer oda_bm2 May 13, 2026 13:20:25 UTC May 13, 2026 13:21:21 UTC Success
Start database 'kkUIxBYc' in NOMOUNT oda_bm1 May 13, 2026 13:21:53 UTC May 13, 2026 13:22:07 UTC Success
mode
Start database 'upJHXf6' in NOMOUNT mode oda_bm1 May 13, 2026 13:21:53 UTC May 13, 2026 13:22:07 UTC Success
Remove old DB network config 'kkUIxBYc' oda_bm2 May 13, 2026 13:22:10 UTC May 13, 2026 13:22:11 UTC Success
Apply new DB network config 'kkUIxBYc' oda_bm2 May 13, 2026 13:22:15 UTC May 13, 2026 13:22:16 UTC Success
Remove old DB network config 'upJHXf6' oda_bm2 May 13, 2026 13:22:19 UTC May 13, 2026 13:22:20 UTC Success
Apply new DB network config 'upJHXf6' oda_bm2 May 13, 2026 13:22:24 UTC May 13, 2026 13:22:24 UTC Success
Remove old DB network config 'JlwmAuIU' oda_bm2 May 13, 2026 13:22:27 UTC May 13, 2026 13:22:28 UTC Success
Apply new DB network config 'JlwmAuIU' oda_bm2 May 13, 2026 13:22:32 UTC May 13, 2026 13:22:33 UTC Success
Stop database 'kkUIxBYc' oda_bm1 May 13, 2026 13:22:33 UTC May 13, 2026 13:22:52 UTC Success
Stop database 'upJHXf6' oda_bm1 May 13, 2026 13:22:33 UTC May 13, 2026 13:22:51 UTC Success
Start database 'kkUIxBYc' oda_bm1 May 13, 2026 13:22:52 UTC May 13, 2026 13:23:14 UTC Success
Start database 'upJHXf6' oda_bm1 May 13, 2026 13:22:52 UTC May 13, 2026 13:23:14 UTC Success
Modify tnsnames.ora files oda_bm2 May 13, 2026 13:23:14 UTC May 13, 2026 13:23:14 UTC Success
Persist SysInstance metadata oda_bm2 May 13, 2026 13:23:15 UTC May 13, 2026 13:23:15 UTC Success
Discover and persist ILOM metadata oda_bm2 May 13, 2026 13:23:16 UTC May 13, 2026 13:23:18 UTC Success
Persist vNetwork metadata 'pubnet' oda_bm2 May 13, 2026 13:23:16 UTC May 13, 2026 13:23:16 UTC Success
Modify networking for DB system oda_bm1 May 13, 2026 13:23:18 UTC May 13, 2026 13:27:02 UTC Success
'vlan_23262'.Modifying Oracle Data Guard Network
If Oracle Database Appliance bare metal system or DB system have Oracle Data
Guard configured, use the odacli modify-dataguard --transport-ips command
after running the odacli modify-networking command to complete Oracle Data
Guard network update. After the public network is changed, Oracle Data Guard configuration
still contains the old network information for the database listeners. Because of this,
communication between the primary and standby databases is not restored automatically after
the network change.
The odacli modify-dataguard --transport-ips command updates Oracle Data
Guard configuration with the new network information so that redo transport can resume. The
networking impact report lists all Oracle Data Guard configurations that require this post
update step. Run this command for each Oracle Data Guard configuration shown in the report.
You must run this command from the system that currently hosts the primary database for Oracle Data Guard configuration. When the command runs, it prompts for the number of standby databases. Enter the number of standby databases configured for Oracle Data Guard setup. It then prompts for the standby site address for each standby database. This is required because the standby systems may now be reachable using different addresses after the network change.
# odacli modify-dataguard -i 18d6464f-dad5-416e-a445-b240321fbf46 -tips utst:odan1.test=ipv4_address,odan2.test=ipv4_address
Number of standby databases (enter 1 or 2 | default: 1):
Standby 1 site address: xx.xx.xx.xx
Username for Standby site xx.xx.xx.xx. If Multi-user Access/Multi-user Access Passwordless is not enabled on Standby site xx.xx.xx.xx, enter 'oda-admin'; otherwise, enter the name of the user who has irestored the Standby database (default: oda-admin):
Password for the user 'oda-admin' for Standby site xx.xx.xx.xx:
Password for root user on Standby site xx.xx.xx.xx:
{
"jobId" : "279329e1-dfa2-4205-9844-0ca8a7b33472",
"status" : "Created",
"message" : "",
"reports" : [ ],
"createTimestamp" : "May 12, 2026 04:59:25 UTC",
"resourceList" : [ ],
"description" : "Dataguard transport-IP modification for DG Config - '18d6464f-dad5-416e-a445-b240321fbf46'",
"updatedTime" : "May 12, 2026 04:59:25 UTC",
"jobType" : null,
"cpsMetadata" : null,
"ecJobId" : null
}
[root@odan1 ~]# odacli describe-job -i 279329e1-dfa2-4205-9844-0ca8a7b33472
Job details
----------------------------------------------------------------
ID: 279329e1-dfa2-4205-9844-0ca8a7b33472
Description: Dataguard transport-IP modification for DG Config - '18d6464f-dad5-416e-a445-b240321fbf46'
Status: Success
Created: May 12, 2026 04:59:25 UTC
Message:
Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- ----------------
Modify DG - Transport IPs odan1 May 12, 2026 04:59:25 UTC May 12, 2026 04:59:32 UTC Success
ipv4_address (Host: host_IP_address/Job
ID:
6ba3868f-0dc2-41a2-af7f-40a036eb619a)
Modify DG Metadata - utst odan2 May 12, 2026 04:59:33 UTC May 12, 2026 04:59:33 UTC Success
Modify Local DNS file - utst odan2 May 12, 2026 04:59:33 UTC May 12, 2026 04:59:33 UTC Success
Modify TNS configuration file - utst odan2 May 12, 2026 04:59:33 UTC May 12, 2026 04:59:33 UTC Success[root@odan1 ~]# odacli describe-job -i 6ba3868f-0dc2-41a2-af7f-40a036eb619a
Job details
----------------------------------------------------------------
ID: 6ba3868f-0dc2-41a2-af7f-40a036eb619a
Description: Dataguard transport-IP modification for DG Config - '18d6464f-dad5-416e-a445-b240321fbf46'
Status: Success
Created: May 12, 2026 04:59:27 UTC
Message:
Task Name Node Name Start Time End Time Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- ----------------
Modify TNS configuration file - utst odan2 May 12, 2026 04:59:27 UTC May 12, 2026 04:59:28 UTC Success
Modify DG Metadata - utst odan2 May 12, 2026 04:59:28 UTC May 12, 2026 04:59:28 UTC Success
Modify Local DNS file - utst odan2 May 12, 2026 04:59:28 UTC May 12, 2026 04:59:28 UTC SuccessUse case for modifying the network on both bare metal system and DB system
This is required when migrating to a different subnet and the DB systems use the network or bridge being modified on the bare metal system. In this case, the payload must include the complete target network configuration for the bare metal system and all affected DB systems. This format can also be used for same-subnet changes when you want to update both the Bare Metal system and selected DB systems in a single request.
- Migrating the bare metal system and associated DB systems to a different subnet.
- Updating both bare metal system and DB system public network configuration within the same subnet.
- Updating DNS or NTP settings along with public network changes.
- Updating an existing VLAN-configured network or vNetwork.
Modifying the network on the bare metal system and DB system using public-network:
{
"bareMetal": {
"networkName": "<public-network-name>",
"domainName": "<domain-name>",
"netmask": "<public-network-netmask>",
"scan": {
"scanName": "<scan-short-name>",
"ipAddresses": [
"<scan-ipv4-1>",
"<scan-ipv4-2>"
]
},
"nodes": [
{
"number": 0,
"name": "<node-1-short-name>",
"ipAddress": "<node-1-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<node-1-vip-short-name>",
"vipAddress": "<node-1-vip-ipv4>"
},
{
"number": 1,
"name": "<node-2-short-name>",
"ipAddress": "<node-2-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<node-2-vip-short-name>",
"vipAddress": "<node-2-vip-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
},
"dbSystems": {
"<db-system-1-name>": {
"networkName": "<public-network-name>",
"domainName": "<domain-name>",
"netmask": "<public-network-netmask>",
"scan": {
"scanName": "<db-system-1-scan-short-name>",
"ipAddresses": [
"<db-system-1-scan-ipv4-1>",
"<db-system-1-scan-ipv4-2>"
]
},
"nodes": [
{
"number": 0,
"name": "<db-system-1-node-1-short-name>",
"ipAddress": "<db-system-1-node-1-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-1-node-1-vip-short-name>",
"vipAddress": "<db-system-1-node-1-vip-ipv4>"
},
{
"number": 1,
"name": "<db-system-1-node-2-short-name>",
"ipAddress": "<db-system-1-node-2-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-1-node-2-vip-short-name>",
"vipAddress": "<db-system-1-node-2-vip-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
},
"<db-system-2-name>": {
"networkName": "<public-network-name>",
"domainName": "<domain-name>",
"netmask": "<public-network-netmask>",
"scan": {
"scanName": "<db-system-2-scan-short-name>",
"ipAddresses": [
"<db-system-2-scan-ipv4-1>",
"<db-system-2-scan-ipv4-2>"
]
},
"nodes": [
{
"number": 0,
"name": "<db-system-2-node-1-short-name>",
"ipAddress": "<db-system-2-node-1-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-2-node-1-vip-short-name>",
"vipAddress": "<db-system-2-node-1-vip-ipv4>"
},
{
"number": 1,
"name": "<db-system-2-node-2-short-name>",
"ipAddress": "<db-system-2-node-2-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-2-node-2-vip-short-name>",
"vipAddress": "<db-system-2-node-2-vip-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
}
}
}DB system using custom-public-vnetwork
This sample updates an existing VLAN-configured vnetwork on the bare metal system and the
public network configuration for an associated DB system. The bare metal section uses
vnetworkName and vlanId because the change applies to an
existing vnetwork. The DB system section uses networkName because the DB
system public network is being updated.
vNetwork and the network change also affects one or more DB systems. The
vlanId field can be used only for an existing VLAN-configured network or
vNetwork. It supports modifying the VLAN ID from one value to another. It does not support
converting a non-VLAN network into a VLAN
network.{
"bareMetal": {
"vnetworkName": "<vnetwork-name>",
"domainName": "<domain-name>",
"netmask": "<vnetwork-netmask>",
"vlanId": <vlan-id>,
"nodes": [
{
"number": 0,
"name": "<node-1-short-name>",
"ipAddress": "<node-1-vlan-ipv4>",
"gateway": "<vlan-network-gateway-ipv4>"
},
{
"number": 1,
"name": "<node-2-short-name>",
"ipAddress": "<node-2-vlan-ipv4>",
"gateway": "<vlan-network-gateway-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
},
"dbSystems": {
"<db-system-1-name>": {
"networkName": "<public-network-name>",
"domainName": "<domain-name>",
"netmask": "<public-network-netmask>",
"scan": {
"scanName": "<db-system-1-scan-short-name>",
"ipAddresses": [
"<db-system-1-scan-ipv4-1>",
"<db-system-1-scan-ipv4-2>"
]
},
"nodes": [
{
"number": 0,
"name": "<db-system-1-node-1-short-name>",
"ipAddress": "<db-system-1-node-1-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-1-node-1-vip-short-name>",
"vipAddress": "<db-system-1-node-1-vip-ipv4>"
},
{
"number": 1,
"name": "<db-system-1-node-2-short-name>",
"ipAddress": "<db-system-1-node-2-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-1-node-2-vip-short-name>",
"vipAddress": "<db-system-1-node-2-vip-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
}
}
}Use case for modifying the network on the bare metal system only
- When there are no DB systems on the appliance.
- Modification to the bare metal system public network is within the same subnet, then modification to the DB system public network configuration is optional.
- When the NTP or DNS of only the bare metal system must be modified.
{
"bareMetal": {
"networkName": "<public-network-name>",
"domainName": "<domain-name>",
"netmask": "<public-network-netmask>",
"scan": {
"scanName": "<scan-short-name>",
"ipAddresses": [
"<scan-ipv4-1>",
"<scan-ipv4-2>"
]
},
"nodes": [
{
"number": 0,
"name": "<node-1-short-name>",
"ipAddress": "<node-1-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<node-1-vip-short-name>",
"vipAddress": "<node-1-vip-ipv4>"
},
{
"number": 1,
"name": "<node-2-short-name>",
"ipAddress": "<node-2-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<node-2-vip-short-name>",
"vipAddress": "<node-2-vip-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
}
}Use case for modifying the network on the DB system only
- Public network configuration change for DB system within the same subnet. Modification to the bare metal system system public network configuration is not required.
{
"dbSystems": {
"<db-system-1-name>": {
"networkName": "<public-network-name>",
"domainName": "<domain-name>",
"netmask": "<public-network-netmask>",
"scan": {
"scanName": "<db-system-1-scan-short-name>",
"ipAddresses": [
"<db-system-1-scan-ipv4-1>",
"<db-system-1-scan-ipv4-2>"
]
},
"nodes": [
{
"number": 0,
"name": "<db-system-1-node-1-short-name>",
"ipAddress": "<db-system-1-node-1-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-1-node-1-vip-short-name>",
"vipAddress": "<db-system-1-node-1-vip-ipv4>"
},
{
"number": 1,
"name": "<db-system-1-node-2-short-name>",
"ipAddress": "<db-system-1-node-2-public-ipv4>",
"gateway": "<public-network-gateway-ipv4>",
"vipName": "<db-system-1-node-2-vip-short-name>",
"vipAddress": "<db-system-1-node-2-vip-ipv4>"
}
],
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
}
}
}Use cases to change the DNS and NTP
You can also modify the DNS and NTP configuration on the bare metal system and the DB system. You can choose to modify these setting on the bare metal system and one or all the DB systems at the same time.
Use networkServices.dnsServers and
networkServices.ntpServers when updating selected bare metal or DB system
sections. Use all.dnsServers and all.ntpServers when the
same DNS and NTP settings must be applied to the bare metal system and all DB systems.
{
"bareMetal": {
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
}
}{
"dbSystems": {
"<db-system-1-name>": {
"networkServices": {
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
],
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>",
"<ntp-server-3>"
]
}
},
"<db-system-2-name>": {
"networkServices": {
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
],
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>",
"<ntp-server-3>"
]
}
}
}
}{
"bareMetal": {
"networkServices": {
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>"
],
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
]
}
},
"dbSystems": {
"<db-system-1-name>": {
"networkServices": {
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
],
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>",
"<ntp-server-3>"
]
}
},
"<db-system-2-name>": {
"networkServices": {
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>"
],
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>",
"<ntp-server-3>"
]
}
}
}
}{
"all": {
"dnsServers": [
"<dns-server-ipv4-1>",
"<dns-server-ipv4-2>",
"<dns-server-ipv4-3>"
],
"ntpServers": [
"<ntp-server-1>",
"<ntp-server-2>",
"<ntp-server-3>"
]
}
}Parent topic: Modifying Public Network Configurations
Adding a Network Interface
Understand how you can add a configured network interface.
- Power off the appliance.
- Add the network interface card.
- Power on the appliance.
- The network configuration files are automatically updated for network bonding and configuration changes.
Parent topic: Managing Networks
Deleting a Network Interface
Understand how you can delete a configured network interface.
btbond1 and btbond2
networks.
Parent topic: Managing Networks
Deleting a Network Interface Using Browser User Interface
Understand how you can delete a configured network interface using the Browser User Interface.
- Click the Appliance tab in the Browser User Interface.
- Click the Network tab in the left navigation to display a list of configured networks.
- Click the Show Interfaces tab in the right navigation to display a list of configured network interfaces.
- Expand the Actions menu, then click Delete for the network interface that you want to delete.
- Confirm the action when prompted.
Parent topic: Managing Networks
Deleting a Network Using the Browser User Interface
Understand how you can delete a configured network using the Browser User Interface.
Parent topic: Managing Networks