Other network segments cannot be pinged after ScanIPrelocate/failover

After a single cluster node is restarted or manually srvctlrelocatescan_listener, the CIDR Block pingIP, VIP, and SCANIP of the cluster are normal, while pingSCANIP of other CIDR blocks cannot be connected. The reason is that the ARP table of the route does not follow the new SCANIP. Manual updates are required. Sbinarping-U-c3-IpublicNICforvipvipipaddressmyo

After a single cluster node is restarted or manually srvctl relocate scan_listener, the IP addresses, VIP addresses, and scan ip addresses of the Cluster's CIDR blocks are pinged, while those of other CIDR blocks cannot be pinged. The reason is that the ARP table of the route does not follow the new scan ip address. Manual updates are required. /Sbin/arping-U-c 3-I public NIC for vip ip address my o

After a single cluster node is restarted or manually srvctl relocate scan_listener, the IP addresses, VIP addresses, and scan ip addresses of the Cluster's CIDR blocks are pinged, while those of other CIDR blocks cannot be pinged. The reason is that the ARP table of the route does not follow the new scan ip address. Manual updates are required.

 /sbin/arping -U -c 3 -I 
  
   
  
 

My oracle support is described as follows:

Bug 13440962 Different subnet failed to connect to vip after restart vip

This note gives a brief overview of bug 13440962.
The content was last updated on: 01-FEB-2012
Click here for details of each of the sections below.

Affects:

Product (Component)	Oracle Server (PCW)
Range of versions believed to be affected	Versions> = 11.2.0.3 however BELOW 12.1
Versions confirmed as being affected	11.2.0.3
Platforms affected	Generic (all/most platforms affected)

It is believed to be a regression in default behaviour thus:

Regression introduced in 11.2.0.3

Fixed:

This issue is fixed in

12.1 (Future Release)

Symptoms:	Related:
(None Specified)	Cluster Ready Services/Parallel Server Management

Description

This is a regression fix for problem introduced by patch 11069846. the change in this patch (patch 13440962) fixes a problem with 4 extra bytes in the G)] ARP message and removes an extra unicast GARP packet to the router. rediscovery Notes: After upgrading to 11.2.0.3, after vip failover, the ip address is not pingable from a different subnet on Linux. (This problem is seen only on Linux) Workaround After vip failover, run command/sbin/arping-U-c 3-I
  
  
   
To update the ARP table of router.
  
 

Please note: The above is a summary description only. actual symptoms can vary. matching to any symptoms here does not confirm that you are encountering this problem. for questions about this bug please consult Oracle Support.