My Oracle Support Banner

Oracle Linux: One of the Bond Interface Not Reachable after Reboot (Doc ID 2123387.1)

Last updated on JUNE 11, 2020

Applies to:

Oracle VM - Version 3.2.8 and later
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64

Symptoms

Network problem with one interface bond3 after rebooting on linux system . Cannot ping ip address of bond3 192.x.x.35. After ifdown/ifup bond3, route of bond3 showing and network of bond3 is up.

#cat ifcfg-bond3
MTU=1500
BONDING_OPTS='mode=active-backup use_carrier=1 miimon=250 downdelay=5000 updelay=5000'
NM_CONTROLLED=no
GATEWAY=192.x.x.1
NETMASK=255.255.255.0
IPADDR=192.x.x.35
BOOTPROTO=static
ONBOOT=yes
DEVICE=bond3
#route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.x.0.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
192.x.x.0 0.0.0.0 255.255.255.0 U 0 0 0 bond3
192.x.x.0 0.0.0.0 255.255.255.0 U 0 0 0 bond4
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond2
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond4
172.x.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond1
0.0.0.0 192.x.0.1 0.0.0.0 UG 0 0 0 bond0
#ifdown bond3
#ifup bond3
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.x.x.0 0.0.0.0 255.255.255.0 U 0 0 0 bond3
192.x.0.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
192.x.x.0 0.0.0.0 255.255.255.0 U 0 0 0 bond4
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond2
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond3
172.x.0.0 0.0.0.0 255.255.0.0 U 0 0 0 bond1
0.0.0.0 192.x.x.1 0.0.0.0 UG 0 0 0 bond3

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.