ODA: IP not pingable across nodes though ibbond0

Asset ID:	1-72-2123676.1
Update Date:	2016-06-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2123676.1 : ODA: IP not pingable across nodes though ibbond0

Applies to:

Oracle Database Appliance X5-2 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

From Node 0 both 192.168.18.1 and 192.168.19.1 are pingable, whereas From Node 1 192.168.19.1 can be pinged but 192.168.18.1 ping throws Destination Host Unreachable

Node 0
=======

[root@node0 ~]# ping 192.168.18.1
PING 192.168.18.1 (192.168.18.1) 56(84) bytes of data.
64 bytes from 192.168.18.1: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 192.168.18.1: icmp_seq=2 ttl=64 time=0.021 ms
64 bytes from 192.168.18.1: icmp_seq=3 ttl=64 time=0.021 ms

[root@node0 ~]# ping 192.168.19.1
PING 192.168.19.1 (192.168.19.1) 56(84) bytes of data.
64 bytes from 192.168.19.1: icmp_seq=1 ttl=64 time=4.23 ms
64 bytes from 192.168.19.1: icmp_seq=2 ttl=64 time=0.208 ms

Node 1
=======

[root@node1 ~]# ping 192.168.19.1
PING 192.168.19.1 (192.168.19.1) 56(84) bytes of data.
64 bytes from 192.168.19.1: icmp_seq=1 ttl=64 time=0.020 ms
64 bytes from 192.168.19.1: icmp_seq=2 ttl=64 time=0.028 ms
64 bytes from 192.168.19.1: icmp_seq=3 ttl=64 time=0.026 ms

[root@node1 ~]# ping 192.168.18.1
PING 192.168.18.1 (192.168.18.1) 56(84) bytes of data.
From 192.168.16.25 icmp_seq=2 Destination Host Unreachable
From 192.168.16.25 icmp_seq=3 Destination Host Unreachable
From 192.168.16.25 icmp_seq=4 Destination Host Unreachable

Cause

node1 has additional parameter set in /etc/sysctl.conf file as listed below

net.ipv4.conf.all.arp_announce=2
net.ipv4.conf.all.arp_ignore=1
net.ipv4.conf.all.arp_filter=1

Also there are duplicated entries found

Solution

Remove the additional parameters as listed in the cause section from the file /etc/sysctl.conf and reboot the node

net.ipv4.conf.all.arp_announce=2
net.ipv4.conf.all.arp_ignore=1
net.ipv4.conf.all.arp_filter=1

Also remove the duplicated entries.

-- and / or --

No custom setting under /etc/sysctl.conf file is not recommended.

References

<BUG:20461930> - LNX64-121-CMT:REPO BECOME UNKNOWN AND HAVIP WAS OFFLINE AFTER RESTARTING CRS
<BUG:22985077> - ODA VBR1 CONNECTIVITY ISSUE ACROSS NODES THROUGH IBBONDO
<NOTE:1500235.1> - How To Collect an Sosreport on Oracle Linux

Attachments

This solution has no attachment