After installing an ODA X9-2 HA with 19.29, we can check the configuration networks with the command odacli:
Use the odacli list-networks command to display the networks configured and managed by the ODA DCS (Database Configuration Service)
Check the list of networks
[root@wadhah-odax9-node02 ~]# odacli list-networks
ID Name NIC Interface Type Subnet Mask Gateway VLAN ID Node Networks
-------------------------------------- -------------------- ------------ --------------- ------------------ ------------------ -------- ---------------------------------------------------------------------------
35079bd7-b7c7-4ced-adeb-7ab6c81c1aa0 ASM-network privasm BRIDGE 255.255.255.128 [IP Address on node0: 192.168.17.2, IP Address on node1: 192.168.17.3]
cbefbd84-92d2-4863-b6fc-1b64f51e41da Public-network pubnet BRIDGE 255.255.255.0 172.16.1.1 [IP Address on node0: 172.16.1.2, IP Address on node1: 172.16.1.3]
2aa2b99b-328c-40b0-b341-6f1ed4c039c6 Private-network icbond0 INTERNAL 255.255.255.0 [IP Address on node0: 192.168.16.24, IP Address on node1: 192.168.16.25]
We have three networks:
- ASM-network
- Public-network
- Private-network
The ASM-network
Dedicated network for Oracle ASM communication. It is used by ASM clients and ASM instances and provides optimized storage-related communication
[root@wadhah-odax9-node02 ~]# odacli describe-network -n ASM-network
Network details
----------------------------------------------------------------
ID: 35079bd7-b7c7-4ced-adeb-7ab6c81c1aa0
Name: ASM-network
NIC: privasm
Interface Type: BRIDGE
Subnet Mask: 255.255.255.128
Gateway:
VLAN ID:
Type: ASM
Default: false
Created: June 2, 2026 11:33:52 AM WAT
Updated: June 2, 2026 11:33:52 AM WAT
Status: CONFIGURED
Node Networks: [IP Address on node0: 192.168.17.2, IP Address on node1: 192.168.17.3]
Scan Name:
Scan Ips:
Vips:
Associated Databases:
Listener Ports:
SCAN Ports:
[root@wadhah-odax9-node02 ~]#
The Public-network
Used for client connectivity, including database VIPs, SCAN listeners, and public node communication.
[root@wadhah-odax9-node02 ~]# odacli describe-network -n Public-network
Network details
----------------------------------------------------------------
ID: cbefbd84-92d2-4863-b6fc-1b64f51e41da
Name: Public-network
NIC: pubnet
Interface Type: BRIDGE
Subnet Mask: 255.255.255.0
Gateway: 172.16.1.1
VLAN ID:
Type: Public
Default: true
Created: June 2, 2026 11:33:52 AM WAT
Updated: June 2, 2026 11:33:52 AM WAT
Status: CONFIGURED
Node Networks: [IP Address on node0: 172.16.1.2, IP Address on node1: 172.16.1.3]
Scan Name: ga-aw-oda2-scan
Scan Ips: 172.16.1.6 172.16.1.7 172.16.1.8
Vips: [wadhah-odax9-node01-vip on node0: 172.16.1.4, wadhah-odax9-node02-vip on node1: 172.16.1.5]
Associated Databases: awdbmig
Listener Ports: 1521
SCAN Ports: 1521
The Private-network
Dedicated Oracle RAC private interconnect used for Cache Fusion, Cluster Synchronization Services (CSS), and inter-node communication. This network should be isolated from client traffic.
[root@wadhah-odax9-node02 ~]# odacli describe-network -n Private-network
Network details
----------------------------------------------------------------
ID: 2aa2b99b-328c-40b0-b341-6f1ed4c039c6
Name: Private-network
NIC: icbond0
Interface Type: INTERNAL
Subnet Mask: 255.255.255.0
Gateway:
VLAN ID:
Type: Private
Default: false
Created: June 2, 2026 11:33:52 AM WAT
Updated: June 2, 2026 11:33:52 AM WAT
Status: CONFIGURED
Node Networks: [IP Address on node0: 192.168.16.24, IP Address on node1: 192.168.16.25]
Scan Name:
Scan Ips:
Vips:
Associated Databases:
Listener Ports:
SCAN Ports:
[root@wadhah-odax9-node02 ~]#
Conclusion:
Running these commands confirms that the ODA configuration (DCS) and the operating system network configuration are consistent, which is particularly important after changing IP addresses, modifying network settings, or performing an appliance migration.
Google+
Facebook
