1 2 Previous Next 21 Replies Latest reply: Apr 19, 2013 3:01 PM by user12140924 Go to original post RSS
      • 15. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
        Liron Amitzi
        Hi,
        First of all, you should not have iptables or any other firewall configured on the interconnect (MOS note 554781.1).
        Now, the last output you sent me, is it with or without iptables configuration?

        Regarding the DNS, you should deconfigure DNS on these servers, this error means that you have a DNS server which cannot be reached (so there is a timeout) - MOS note 1326997.1.

        Liron
        • 16. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
          895680
          Hi Liron,

          The last o/p sent to you is without IPtables firewall. Now I have disabled and all checks related to node connectivity passed.
          DNS check is still failing on both the nodes.
          Below is the o/p from runcluvfy.sh script:
          ***********************************************************************************************************************************

          Checking consistency of file "/etc/resolv.conf" across nodes

          Checking the file "/etc/resolv.conf" to make sure only one of domain and search entries is defined
          File "/etc/resolv.conf" does not have both domain and search entries defined
          Checking if domain entry in file "/etc/resolv.conf" is consistent across the nodes...
          domain entry in file "/etc/resolv.conf" is consistent across nodes
          Checking if search entry in file "/etc/resolv.conf" is consistent across the nodes...
          search entry in file "/etc/resolv.conf" is consistent across nodes
          Checking DNS response time for an unreachable node
          Node Name                             Status
          ------------------------------------  ------------------------
          rac2                                  failed
          rac1                                  failed
          PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes: rac2,rac1

          File "/etc/resolv.conf" is not consistent across nodes

          ***********************************************************************************************************************************

          *[root@rac1 grid]# cat /etc/resolv.conf*

          *[grid@rac2 grid]$ cat /etc/resolv.conf*


          Resolv.conf doesn't contain any entry on both the nodes. DNS server is not configured but still its checking for DNS response time.


          Regards,
          Purnima Johari

          Edited by: 892677 on Feb 10, 2012 2:47 AM
          • 17. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
            Liron Amitzi
            Hi Purnima,
            Please check nslookup:
            nslookup rac1
            nslookup rac2
            Also, please post the output of:
            cat /etc/nsswitch.conf
            Liron
            • 18. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
              user8830003
              Hi Liron,

              I was struggling with this issue on my build too.

              Thanks for posting the link to the iptables MOS Note 554781.1 which solved the below cluvfy ERROR for me

              I was encountering exactly the same issue "TCP connectivity check failed" per below o/p on my Oracle VM Server setup.

              Check: TCP connectivity of subnet "203.10.1.0"
              Source Destination Connected?
              ------------------------------ ------------------------------ ----------------
              racassur-ipfix01:203.10.1.3 racassur-ipfix02:203.10.1.4 failed

              ERROR:
              PRVF-7617 : Node connectivity between "racassur-ipfix01 : 203.10.1.3" and "racassur-ipfix02 : 203.10.1.4" failed
              Result: TCP connectivity check failed for subnet "203.10.1.0"

              After running these commands on my Linux nodes as root,

              [root@racassur-ipfix02 network-scripts]# chkconfig iptables off
              [root@racassur-ipfix02 network-scripts]# service iptables stop
              Flushing firewall rules: [  OK  ]
              Setting chains to policy ACCEPT: filter [  OK  ]
              Unloading iptables modules: [  OK  ]

              the cluvfy check of network was successful

              [grid@racassur-ipfix01 bin]$ +./cluvfy comp nodecon -i eth0 -n racassur-ipfix01,racassur-ipfix02 -verbose+
              • 19. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
                user13256058
                I just added iptables rules:

                -A INPUT -s the-other-node-ip-public/255.255.255.255 -j ACCEPT
                -A INPUT -s the-other-node-ip-vip/255.255.255.255 -j ACCEPT
                -A INPUT -s the-other-node-priv/255.255.255.255 -j ACCEPT
                -A INPUT -p igmp -j ACCEPT
                -A INPUT -m pkttype --pkt-type multicast -j ACCEPT

                and those checks passed even with iptables enabled.
                • 20. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
                  834915
                  I had no luck with the iptables rules, but disabling the service worked.

                  Also, for those who stumble across this thread in the future, I also received the error:
                  PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes

                  This is a known bug. See DocID: 1480242.1.
                  • 21. Re: TCP connectivity of subnet check failed, execuion of runcluvfy.sh,RAC
                    user12140924
                    hello, i am have problems installa oracle RAC 11.2.0.3 Helpppppppppppppppp

                    Here are the 2 Virtual machine details:
                    VM used: Oracle Virtual box 4.2.8
                    Cluster Version: 11g R2 (11.2.0.3)
                    Windows version: Windows 2008 Server R2
                    No of node: 2

                    Node details:
                    Node 1 hostname: w2008-112-rac1
                    Public ip (eth0): 192.168.0.151
                    Subnet mask: 255.255.255.0
                    Default gateway: 192.168.0.1
                    DNS: 192.168.0.4

                    Private ip (eth1): 192.168.1.151
                    Subnet mask: 255.255.255.0
                    Default gateway: none
                    DNS: none

                    Node 2 hostname: w2008-112-rac2
                    Public ip (eth0): 192.168.0.152
                    Subnet mask: 255.255.255.0
                    Default gateway: 192.168.0.1
                    DNS: 192.168.0.4

                    Private ip (eth1): 192.168.1.152
                    Subnet mask: 255.255.255.0
                    Default gateway: none
                    DNS: none

                    file hosts

                    127.0.0.1 localhost.localdomain localhost
                    # Public
                    192.168.0.151 w2008-112-rac1.localdomain w2008-112-rac1
                    192.168.0.152 w2008-112-rac2.localdomain w2008-112-rac2
                    #Private
                    192.168.1.151 w2008-112-rac1-priv.localdomain w2008-112-rac1-priv
                    192.168.1.152 w2008-112-rac2-priv.localdomain w2008-112-rac2-priv
                    #Virtual
                    192.168.0.153 w2008-112-rac1-vip.localdomain w2008-112-rac1-vip
                    192.168.0.154 w2008-112-rac2-vip.localdomain w2008-112-rac2-vip
                    #SCAN (192.168.0.155 - 192.168.0.157 in DNS)
                    192.168.0.155 w2008-112-scan.localdomain w2008-112-scan
                    192.168.0.156 w2008-112-scan.localdomain w2008-112-scan
                    192.168.0.157 w2008-112-scan.localdomain w2008-112-scan


                    Error **************

                    ERROR: PRVF-7617 : Node connectivity between "w2008-112-rac1: 192.168.0.151" and "w2008-112-rac2: 192.168.0.152" TCP connectivity check failed for subnet "192.168.0.0"


                    help Plis ......

                    Edited by: user12140924 on 19/04/2013 01:01 PM
                    1 2 Previous Next