6 Replies Latest reply: Jan 6, 2013 3:11 AM by 885820 RSS

    Unable to ping scan-vip from remote machine

    885820
      After following the racattack tutorials, I have succesfully managed to install a working 11.2.0.0 cluster using vmware server runing OEL 5 Virtual clients on a windows host.

      One issue that I am having is connecting to the scan vip from a remote connection (windows 11.2 client - installed on the windows host machine)

      Contents of hosts file on the 'remote' machine are as follows:
      c:\windows\system32\drivers\etc\hosts >

      --------------------------------------------------------------------
      192.168.78.250 collab-scan.vm.ardentperf.com collab-scan
      192.168.78.61 collabn1-vip.vm.ardentperf.com collabn1-vip
      192.168.78.62 collabn2-vip.vm.ardentperf.com collabn2-vip
      192.168.78.51 collabn1.vm.ardentperf.com collabn1
      192.168.78.52 collabn2.vm.ardentperf.com collabn2
      --------------------------------------------------------------------


      I am not able to ping the scan vip remotley where as I can ping each node vip successfully from the remote machiine, however I AM able to ping the scan-vip from from each node of the cluster.

      Im puzzled

      Please see below..

      =====================================================================
      Remote connections -
      =====================================================================


      C:\instantclient_11_2>ping collabn1-vip

      Pinging collabn1-vip.vm.ardentperf.com [192.168.78.61] with 32 bytes of data:
      Reply from 192.168.78.61: bytes=32 time<1ms TTL=64
      Reply from 192.168.78.61: bytes=32 time<1ms TTL=64

      Ping statistics for 192.168.78.61:
      Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
      Control-C
      ^C
      C:\instantclient_11_2>ping collabn2-vip

      Pinging collabn2-vip.vm.ardentperf.com [192.168.78.62] with 32 bytes of data:
      Reply from 192.168.78.62: bytes=32 time<1ms TTL=64
      Reply from 192.168.78.62: bytes=32 time<1ms TTL=64

      Ping statistics for 192.168.78.62:
      Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
      Control-C
      ^C
      C:\instantclient_11_2>ping collabn1

      Pinging collabn1.vm.ardentperf.com [192.168.78.51] with 32 bytes of data:
      Reply from 192.168.78.51: bytes=32 time<1ms TTL=64
      Reply from 192.168.78.51: bytes=32 time<1ms TTL=64

      Ping statistics for 192.168.78.51:
      Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
      Control-C
      ^C
      C:\instantclient_11_2>ping collabn2

      Pinging collabn2.vm.ardentperf.com [192.168.78.52] with 32 bytes of data:
      Reply from 192.168.78.52: bytes=32 time<1ms TTL=64
      Reply from 192.168.78.52: bytes=32 time<1ms TTL=64

      Ping statistics for 192.168.78.52:
      Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
      Minimum = 0ms, Maximum = 0ms, Average = 0ms
      Control-C
      ^C
      C:\instantclient_11_2>ping collab-scan

      Pinging collab-scan.vm.ardentperf.com [92.168.78.250] with 32 bytes of data:
      Request timed out.
      Request timed out.
      Request timed out.

      Ping statistics for 92.168.78.250:
      Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),
      Control-C
      ^C
      C:\instantclient_11_2>


      =====================================================================
      From Node 1 of cluster -
      =====================================================================

      collabn1:/home/oracle[+ASM1]$ ping collab-scan
      PING collab-scan (192.168.78.250) 56(84) bytes of data.
      64 bytes from collab-scan (192.168.78.250): icmp_seq=1 ttl=64 time=0.036 ms
      64 bytes from collab-scan (192.168.78.250): icmp_seq=2 ttl=64 time=0.030 ms

      --- collab-scan ping statistics ---
      2 packets transmitted, 2 received, 0% packet loss, time 1000ms
      rtt min/avg/max/mdev = 0.030/0.033/0.036/0.003 ms

      =====================================================================
      From Node 2 of cluster -
      =====================================================================

      collabn2:/home/oracle[RAC2]$ ping collab-scan
      PING collab-scan (192.168.78.250) 56(84) bytes of data.
      64 bytes from collab-scan (192.168.78.250): icmp_seq=1 ttl=64 time=0.489 ms
      64 bytes from collab-scan (192.168.78.250): icmp_seq=2 ttl=64 time=0.238 ms

      --- collab-scan ping statistics ---
      2 packets transmitted, 2 received, 0% packet loss, time 1001ms
      rtt min/avg/max/mdev = 0.238/0.363/0.489/0.126 ms

      -------------------------------------------------------------------------

      Does anyone have any ideas why I can't ping the scan-vip remotley?

      Any help would be appriciated (let me know any additional information you require)

      Thanks