Exalogic Physical: IB Networks Not Working On Compute Nodes When One Of the Slaves Is Made Active Slave
(Doc ID 2256764.1)
Last updated on OCTOBER 22, 2018
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.0 and later
In Exalogic Physical racks, only one of the two slaves configured for IB network bonded interface is observed to be functional. IB networks do not work when making other slave interface as active slave.
For e.g. if we have Compute Node with EoIB network bond1 with two slaves ethX and ethY slaves with ethX slave pinned to GW01 and ethY slave pinned GW02. Bond1 works when ethX is active slave which corresponds to GW01. Same bond1 does not work when ethY is active slave which corresponds to GW02.
For flipping active slave for bond we can run below command.
This behavior can be observed for EoIB or IPoIB networks or both.
There are no error messages in the logs of Compute Nodes or IB Switches when IB network does not work, In this example when ethY is active slave for bond1. Also ifconfig -a output shows network and its slaves as UP when the issue is happening. "ibstat" command shows that both the ports are UP.
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