My Oracle Support Banner

Slave Bond Link Status Repeatedly Fails with "link status definitely down for interface"/"link status definitely up for interface" on BDA Server(s) (Doc ID 2251331.1)

Last updated on MARCH 30, 2020

Applies to:

Big Data Appliance X6-2 Hardware - Version All Versions and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

 

One or more hosts in a cluster show a slave bond link repeatedly failing.

 

Errors reported by bdachecknet-cluster and/or in /var/log/messages show behavior like below on each host experiencing the issue.

bondeth0: no route to arp_ip_target <IP_ADDRESS_ARP_TARGET> and arp_validate is set

In the case of a single client network see output like below (where eth8 and eth9 can be interchanged) showing a slave bond link repeatedly failing.

bondeth0: link status definitely down for interface eth8, disabling it
bondeth0: link status definitely down for interface eth9, disabling it
bondeth0: now running without any active interface!
bondeth0: link status definitely up for interface eth9
bondeth0: making interface eth9 the new active one
bondeth0: first active interface up!
bondeth0: link status definitely up for interface eth8
bondeth0: link status definitely down for interface eth9, disabling it
bondeth0: making interface eth8 the new active one
bondeth0: first active interface up!
...<repeated over and over>...

In the case of a second client network see output like below showing a slave bond link repeatedly failing. 

bondeth1: link status definitely down for interface eth11, disabling it
bondeth1: making interface eth10 the new active one.
bondeth1: link status definitely up for interface eth11.
bondeth1: making interface eth11 the new active one.
...<repeated over and over>...

2. Checking the bonding options in /etc/sysconfig/network-scripts/ifcfg-bondeth0 (for a single client network configuration) and in /etc/sysconfig/network-scripts/ifcfg-bondeth1 (for a two client network configuration) shows that arp monitoring is being used.

For example output is like:

Configuration - Single Client Network:
Where the interface will be eth8 or eth9 on alternating hosts like: 

 

 

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


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