My Oracle Support Banner

Oracle Linux: Bonding Device Based on Infiniband Does not Get Activated Even After All Secondary Are Activated (Doc ID 2181056.1)

Last updated on JUNE 07, 2021

Applies to:

Linux OS - Version Oracle Linux 6.7 with Unbreakable Enterprise Kernel [2.6.39] and later
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.


 A bonding device(ex. named "ibbond0") which has several Infiniband secondarys(ex. "ib0" and "ib1") does not get activated even after all secondarys has been activated by ifup, once after all secondarys was de-activated by ifdown.

 The typical scenario to reproduce this issue is:

  1. de-activate all secondarys of the bonding device(ex. ifdown ib0; ifdown ib1)
  2. re-activate them(ex. ifup ib0; ifup ib1)

 Then the bonding device ibbond0 does not get activated, all of the MII status in /proc/net/bond/ibbond0 show "down".

 This issue occurs only when all secondarys are deactivated by ifdown. If one or more secondary(s) remains as an active secondary of the bonding device, adding other secondarys by "ifup ib#" does not bring this issue, it is just added as an "up" interface.


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

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