关于11g rhel6 11.2.0.3.0 rac VIP failover back ping不通的问题 ORA-12170

  关于11g rhel6 11.2.0.3.0 rac  VIP failover back ping不通的问题 1.主节点hosts配置  10.30.50.1      zrac0110.30.50.2      zrac0210.30.50.3      zrac01-vip10.30.50.4      zrac02-vip192.168.137.1   zrac01-priv192.168.137.2   zrac02-priv10.30.50.5      zrac-cluster-scan2.网卡配置public IP  网卡名 em1 VIP        网卡名 em1:1 em1       Link encap:Ethernet  HWaddr 54:9F:35:0A:6F:50            inet addr:10.30.50.1  Bcast:10.30.50.63  Mask:255.255.255.192          inet6 addr: fe80::569f:35ff:fe0a:6f50/64 Scope:Link          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          RX packets:23410 errors:0 dropped:0 overruns:0 frame:0          TX packets:17231 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:1000           RX bytes:2448649 (2.3 MiB)  TX bytes:1947974 (1.8 MiB)          Interrupt:35 em1:1     Link encap:Ethernet  HWaddr 54:9F:35:0A:6F:50            inet addr:10.30.50.3  Bcast:10.30.50.63  Mask:255.255.255.192          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          Interrupt:35 em2       Link encap:Ethernet  HWaddr 54:9F:35:0A:6F:51            inet addr:192.168.137.1  Bcast:192.168.137.255  Mask:255.255.255.0          inet6 addr: fe80::569f:35ff:fe0a:6f51/64 Scope:Link          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1          RX packets:557429 errors:0 dropped:0 overruns:0 frame:0          TX packets:312048 errors:0 dropped:0 overruns:0 carrier:0          collisions:0 txqueuelen:1000           RX bytes:611390963 (583.0 MiB)  TX bytes:262148220 (250.0 MiB)          Interrupt:38 3.客户端TNS配置客户端与数据库服务器不在同一子网网段GNNT1 =  (DESCRIPTION =    (FAILOVER=ON)    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.30.50.3)(PORT = 1521))    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.30.50.4)(PORT = 1521))    (CONNECT_DATA =      (SERVER = DEDICATED)      (SERVICE_NAME = gnnt)    (FAILOVER_MODE=(TYPE=select)(METHOD=basic)(BACKUP=zrac02))    )  )GNNT3 =  (DESCRIPTION =    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.30.50.3)(PORT = 1521))    (CONNECT_DATA =      (SERVER = DEDICATED)      (SERVICE_NAME = gnnt)    )  )                    问题描述:当主节点RAC01停止CRS集群后， zrac01-vip 10.30.50.3将漂移至第二个节点，关于VIP的migrate存在两种情况case1:如果客户端与数据库服务器不在同一子网网段，则VIP要漂移时要值得注意1.当停止RAC1节点CRS后，zrac01-vip 10.30.50.3漂移至节点RAC2，此时客户端通过ping  10.30.50.3是在超时状态2.当RAC1节点重新启动CRS后，zrac01-vip 10.30.50.3重新漂移至节点RAC1,但客户端仍旧无法通过TNS进行sqlplus连接实例1，客户端反馈为TNS超时case2:如果客户端与数据库服务器在同一子网网段，则不存在vip漂移后ping不通的问题与sqlplus连接问题测试状态:C:\Windows\System32>ping  10.30.50.3 -t正在 Ping 10.30.50.3 具有 32 字节的数据:请求超时。请求超时。请求超时。请求超时。导致此种情况，可以有两种方式解决1.此种情况是由于Oracle Duplicate list bug 13389756 bug 13396423 bug 13396684 bug 13357494 bug 13352041造成的，可以更新GI PSU至11.2.0.3.2以后解决2.手动更新主机的ARP CACHE导致VIP连接与ping超时情况的原因是arp cache机制与arp 自动响应的原因造成的，不通网段和平台arp cache列表的自动更新时间各不同通常–  思科设备  – 20 min至4 hours,–  Linux – default 60 seconds,–  Windows – up to 10 more than minutes.因此需要进行手动更新arp cache进行解决，当执行arping命令后，系统会为VIP提供新的MAC地址，更新各个网段的路由信息和arp cache #arping  -c2 -I em1  -U 10.30.50.3  ARP cache 手动更新完成后，客户端可以ping通VIP，sqplus可以正常连接 C:\Windows\System32>ping  10.30.50.3正在 Ping 10.30.50.3 具有 32 字节的数据:来自 10.30.50.3 的回复: 字节=32 时间<1ms TTL=63来自 10.30.50.3 的回复: 字节=32 时间<1ms TTL=63来自 10.30.50.3 的回复: 字节=32 时间<1ms TTL=63