ping通ip mysql_ScanIPrelocate/failover后其他网段无法ping通

集群单节点在重启或者手动srvctl relocate scan_listener后，集群所在网段ping IP,VIP，SCAN IP正常，其他网段ping SCAN IP 不通。原因是路由的ARP表没有随之而跟新SCAN IP。需要手动更新。 /sbin/arping -U -c 3 -I public NIC for vip vip ip address my o

集群单节点在重启或者手动srvctl relocate scan_listener后，集群所在网段ping IP,VIP，SCAN IP正常，其他网段ping SCAN IP 不通。原因是路由的ARP表没有随之而跟新SCAN IP。需要手动更新。

/sbin/arping -U -c 3 -I

my oracle support说明如下：

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 but 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 To:

(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【本文来自鸿网互联 (http://www.68idc.cn)】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.

本文原创发布php中文网，转载请注明出处，感谢您的尊重！