My Oracle Support Banner

AIX: ARP Cache Not Updated After HAIP Failover (Doc ID 2831749.1)

Last updated on AUGUST 25, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
IBM AIX on POWER Systems (64-bit)

Symptoms

NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

On 19C GI environment on IBM platform, if there are multiple private networks and one of the network interface is down and then up, communication problems can happen on HAIP layer, ASM & DB instances may hang or crash, the issue can cause around 20 minutes outage.

Main Symptoms:

In ohasd agent trace of node 2 , HAIP [169.254.xxx.236] failed over from [en3] to [en4] at [08:45:03], and then failed back from [en4] to [en3] 5 seconds later at [08:45:08], ARP cache was also cleaned up successfully, everything looks fine.

In the ARP table of node 1, [169.254.xxx.236] changed from [1a:16:xx:xx:14:17] to [1a:16:xx:xx:14:18] at [08:45:29], this is expected as the HAIP failed over from [en3] to [en4], however, until 20 minutes later at [09:06:02], it changed back to [1a:16:xx:xx:14:17]. HAIP couldn't work during this time, which caused ASM & DB communication problems.

Changes

 No changes.

Cause

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
Symptoms
Changes
Cause
Solution
References


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