VIP Does not Failover when nic Goes down in Clusterware Running on OVM
(Doc ID 2014567.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
2-Node RAC cluster using GI running in Guest vm on oda:
On the physical servers (dom0), we have 4 NICs and we do couple every 2 of them to build up 2 bonded interfaces bond0 and bond1. 2 XEN bridges were created using these bonded interfaces: xenbr0 and xenbr1. The guests (RAC nodes) get two virtual NICs eth0 and eth1, mapped to the xenbr's. GI installed and configured inside the guests uses 1 NIC for public network and one for interconnect.
In a situation if we lose both NICs behind the same bond in dom0 (i.e. the whole bond becomes disfunctional), this is processed normally by GI in the guest if it's the bond behind the interconnect.
It's not detected by GI if the bond exists behind the guest's public interface so GI does not initiate an VIP-failover, thus compromising client access to the cluster.
The nic attached to public or private inrterconnect goes down.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!