Duplicate VIP Address Introduced in the System May Cause an ARP Storm on Solaris 11
(Doc ID 2215247.1)
Last updated on FEBRUARY 11, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
1. Clusterware may introduce a duplicated VIP or SCAN VIP on another node in the cluster. Note that the SCAN and Node VIPs can run on any node, but must not be plumbed on more than one machine at a time.
2. On Solaris, when a duplicated IP is introduced on the system the OS log may report messages like:
note that the interface was left disabled, but ipadm or ifconfig may show the duplicated IP address:
ADDROBJ TYPE STATE ADDR
net0/v4b static duplicate <ip address>/21 <<<<<<<<<< It shows duplicate
3. On Solaris, the system may try to recover (enable) the interface and may produce an ARP strom. The nodes may report:
<node 1> ip: [ID 636139 kern.notice] NOTICE: recovered address ::ffff:<ip address> on pub0:3 (somehow got propagated to pub0 of both nodes.
<node 1> ip: [ID 195243 kern.warning] WARNING: proxy ARP problem? Node '<mac address>' is using <ip address> on pub0
<node 1> last message repeated 20495 times
<node 2> ip: [ID 195243 kern.warning] WARNING: proxy ARP problem? Node '<mac address>' is using <ip address> on pub0
<node 2> twsmwmapsdp03 last message repeated 1853064 times
No changes have been made to the system
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