Network Connectivity Issues with Multiple Client Networks in Exadata Environment
Last updated on DECEMBER 13, 2017
Applies to:Linux OS - Version Oracle Linux 5.0 and later
Note: IP Address range used here is for demonstration purpose only.
Consider an Exadata Client Network connectivity such as:
- Although most of the nodes in the additional network: "192.168.20.0/24", would access the DB node using the IP "192.168.20.25", it may also be expected that some nodes from this network accesses the DB node over the IP "192.168.10.25" (from client network).
- New TCP connections from a Node belonging to the Additional client network, to 192.168.10.25 would fail.
- For instance, When trying with ssh, tnsping, sqlplus from Node A at 192.168.20.100, to Exadata DB machine at 192.168.10.25, the connection is not getting established.
- A tcpdump command run on the interface "bondeth0", that filters the packets to/from network "192.168.20.0/24", would reveal that it receives all incoming TCP SYN packets and RESET packets but there is no reply sent over this interface.
- And upon further inspecting the packets on bondeth1 interface, it could be found that the TCP SYN ACKs for the previously seen packets, are sent over "bondeth1".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms