VIP Fails Over To Another NIC In the Same Node Instead Of To a Surviving Node (Doc ID 745104.1)

Last updated on JULY 12, 2012

Applies to:

Oracle Server - Enterprise Edition - Version 10.1.0.2 to 11.1.0.6 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.1 to 11.1
Information in this document applies to any Unix or Linux platform


Symptoms

When public network fails, VIP fails over to another NIC in the same node instead of failing over to another node.

The purpose of this is to allow the VIP to fail over to another NIC card in the same public subnet instead of failing to another node. This is intended behavior and provides more flexibility to the customer who wants to have the failover capability for VIP between two NIC cards on the same public subnet, but if incorrectly configured, the VIP can fail over to another NIC that is not on the same public subnet.

Although NIC bonding, IPMP, ether-channel, and other aggregation methods provided by OS give the same failover capability, the ability to define multiple NIC cards for VIP provides additional flexibility.

After VIP is failed over to another NIC card, "ifconfig -a" output shows that the VIP is running on a different NIC card.

If VIP is configured incorrectly with the private interconnect in the list of interfaces, VIP will fail over to the private interconnect. Having VIP running on the private interconnect can cause many problems including node eviction, instance eviction, and database performance problem.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms