VIP is Not Pingable But Started on Each Clusternode (Doc ID 555220.1)

Last updated on MARCH 18, 2008

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2 to 11.1
Microsoft Windows Server 2003

Symptoms

Oracle Clusterware was installed and setup correctly. The VIPs can not be pinged from any node except the local cluster-node.

For example:

on node3 (outside-cluster, but in the same subnet):
      ping clusternode1:           works
      ping clusternode2:           works
      ping clusternode1-vip:     timeout
      ping clusternode2-vip:     timeout


on clusternode1:
     ping clusternode1-vip:      works
     ping clusternode2:            works
     ping clusternode2-vip:      timeout


Similar behaviour on clusternode2

node3 (not in the cluster, but on the same subnet) shows this ARP cache after running the ping commands:

> arp -a
Interface: 138.1.185.226 --- 0x10005
Internet Address     Physical Address   Type
130.35.163.52        00-1a-ff-f3-ba-1   dynamic
138.1.185.148        01-18-f8-38-4f-62  dynamic  <== node1-vip
138.1.185.150        01-18-f8-38-4f-62  dynamic  <== node2-vip


==> Note the difference in the first two digits of the Physical Address (MAC Address) shown for the VIPs.


.

Changes

- During operating system setup a Network Load Balancer was installed on the public network card
- Installed Clusterware

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms