6 Replies Latest reply: Nov 4, 2012 3:46 AM by Burasami RSS

    Could not find a suitable set of interfaces for VIPs

    Burasami
      Hi All,

      I have RAC environment which has 2 nodes. In which 1 node is down.. When i used the following command i found

      ERROR: Could not find a suitable set of interfaces for VIPs... Please help me out to fix the problem
      oracle@YYYYYYYY:~> cluvfy comp nodecon -n all -verbose
      
      Verifying node connectivity
      
      Checking node connectivity...
      
      
      Interface information for node "YYYYYYYY"
        Interface Name                  IP Address                      Subnet
        ------------------------------  ------------------------------  ----------------
        eth20                           10.20.2.111                     10.20.2.0
        eth2                            172.20.2.111                    172.20.2.0
        eth2                            172.20.2.114                    172.20.2.0
      
      
      Interface information for node "XXXXXXXX"
        Interface Name                  IP Address                      Subnet
        ------------------------------  ------------------------------  ----------------
        eth2                            172.20.2.110                    172.20.2.0
        eth2                            172.20.2.115                    172.20.2.0
        eth1                            10.20.2.110                     10.20.2.0
      
      
      Check: Node connectivity of subnet "10.20.2.0"
        Source                          Destination                     Connected?
        ------------------------------  ------------------------------  ----------------
        YYYYYYYY:eth20                XXXXXXXX:eth1                 yes
      Result: Node connectivity check passed for subnet "10.20.2.0" with node(s) YYYYYYYY,XXXXXXXX.
      
      Check: Node connectivity of subnet "172.20.2.0"
        Source                          Destination                     Connected?
        ------------------------------  ------------------------------  ----------------
        YYYYYYYY:eth2                 YYYYYYYY:eth2                 yes
        YYYYYYYY:eth2                 XXXXXXXX:eth2                 yes
        YYYYYYYY:eth2                 XXXXXXXX:eth2                 yes
        YYYYYYYY:eth2                 XXXXXXXX:eth2                 yes
        YYYYYYYY:eth2                 XXXXXXXX:eth2                 yes
        XXXXXXXX:eth2                 XXXXXXXX:eth2                 yes
      Result: Node connectivity check passed for subnet "172.20.2.0" with node(s) YYYYYYYY,XXXXXXXX.
      
      Suitable interfaces for the private interconnect on subnet "172.20.2.0":
      YYYYYYYY eth2:172.20.2.111 eth2:172.20.2.114
      XXXXXXXX eth2:172.20.2.110 eth2:172.20.2.115
      
      ERROR:
      Could not find a suitable set of interfaces for VIPs.
      
      Result: Node connectivity check failed.
      RAC Node on XXXXXXXX

      XXXXXXXX:~ # ifconfig -a
      eth1      Link encap:Ethernet  HWaddr 00:14:5E:77:E8:CD
                inet addr:10.20.2.110  Bcast:10.20.2.255  Mask:255.255.255.0
                inet6 addr: fe80::214:5eff:fe77:e8cd/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:18981 errors:0 dropped:0 overruns:0 frame:0
                TX packets:150734 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:3607660 (3.4 Mb)  TX bytes:50697085 (48.3 Mb)
      eth2      Link encap:Ethernet  HWaddr 00:14:5E:77:E8:CC
                inet addr:172.20.2.110  Bcast:172.20.2.255  Mask:255.255.255.0
                inet6 addr: fe80::214:5eff:fe77:e8cc/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:604644717 errors:0 dropped:2173 overruns:0 frame:0
                TX packets:100620702 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:771633621687 (735887.1 Mb)  TX bytes:73107535231 (69720.7 Mb)
      eth2:1    Link encap:Ethernet  HWaddr 00:14:5E:77:E8:CC
                inet addr:172.20.2.115  Bcast:172.20.2.255  Mask:255.255.255.0
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      eth3      Link encap:Ethernet  HWaddr 00:21:5E:B5:24:C0
                inet6 addr: fe80::221:5eff:feb5:24c0/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:13836 errors:0 dropped:0 overruns:0 frame:0
                TX packets:1788 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:2609189 (2.4 Mb)  TX bytes:177504 (173.3 Kb)
      lo        Link encap:Local Loopback
                inet addr:127.0.0.1  Mask:255.0.0.0
                inet6 addr: ::1/128 Scope:Host
                UP LOOPBACK RUNNING  MTU:16436  Metric:1
                RX packets:608969 errors:0 dropped:0 overruns:0 frame:0
                TX packets:608969 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:0
                RX bytes:113147556 (107.9 Mb)  TX bytes:113147556 (107.9 Mb)
      sit0      Link encap:IPv6-in-IPv4
                NOARP  MTU:1480  Metric:1
                RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:0
                RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
      RAC node YYYYYYYY:
      XXXXXXXX:~ # ifconfig -a
      eth1      Link encap:Ethernet  HWaddr 00:14:5E:77:E8:CD
                inet addr:10.20.2.110  Bcast:10.20.2.255  Mask:255.255.255.0
                inet6 addr: fe80::214:5eff:fe77:e8cd/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:18981 errors:0 dropped:0 overruns:0 frame:0
                TX packets:150734 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:3607660 (3.4 Mb)  TX bytes:50697085 (48.3 Mb)
      eth2      Link encap:Ethernet  HWaddr 00:14:5E:77:E8:CC
                inet addr:172.20.2.110  Bcast:172.20.2.255  Mask:255.255.255.0
                inet6 addr: fe80::214:5eff:fe77:e8cc/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:604644717 errors:0 dropped:2173 overruns:0 frame:0
                TX packets:100620702 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:771633621687 (735887.1 Mb)  TX bytes:73107535231 (69720.7 Mb)
      eth2:1    Link encap:Ethernet  HWaddr 00:14:5E:77:E8:CC
                inet addr:172.20.2.115  Bcast:172.20.2.255  Mask:255.255.255.0
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      eth3      Link encap:Ethernet  HWaddr 00:21:5E:B5:24:C0
                inet6 addr: fe80::221:5eff:feb5:24c0/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:13836 errors:0 dropped:0 overruns:0 frame:0
                TX packets:1788 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000
                RX bytes:2609189 (2.4 Mb)  TX bytes:177504 (173.3 Kb)
      lo        Link encap:Local Loopback
                inet addr:127.0.0.1  Mask:255.0.0.0
                inet6 addr: ::1/128 Scope:Host
                UP LOOPBACK RUNNING  MTU:16436  Metric:1
                RX packets:608969 errors:0 dropped:0 overruns:0 frame:0
                TX packets:608969 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:0
                RX bytes:113147556 (107.9 Mb)  TX bytes:113147556 (107.9 Mb)
      sit0      Link encap:IPv6-in-IPv4
                NOARP  MTU:1480  Metric:1
                RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:0
                RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
      Thanks
      Sami
        • 1. Re: Could not find a suitable set of interfaces for VIPs
          JohnWatson
          You didn't mention the release, but would it be 10.2.x? If so, this is not a problem. cluvfy reports those addresses as being unsuitable because according to the RFC that describes VIPs, a VIP must be routable. And 10.x.x.x addresses and 172.something addresses are not routable. But they work, no problem. The 11.x version of cluvfy does not rport this "error".
          • 2. Re: Could not find a suitable set of interfaces for VIPs
            Burasami
            Hi all,
            its an
            Connected to:
            Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
            With the Partitioning, Real Application Clusters, OLAP and Data Mining options
            Sorry I couldn't understand what your trying to say.. Because am new to RAC
            cluvfy reports those addresses as being unsuitable because according to the RFC that describes VIPs, a VIP must be routable. And 10.x.x.x addresses and 172.something addresses are not routable. But they work, no problem.
            Thanks
            Sami

            Edited by: Sami on Nov 1, 2012 3:00 PM
            • 3. Re: Could not find a suitable set of interfaces for VIPs
              phaeus
              Hello,
              the RFC says which IP Ranges are OK for private use and which IPs are used for Public use (like on the internet). The Check looks for the IP Masks and map them to the network classes. If it not found one Range in Private Class and one Range in Public class the error occurs. But you can still continue to build your rac as long your ip addresses are ok. In later version of oracle RAC this error is change to a info warning.

              regards
              Peter
              • 4. Re: Could not find a suitable set of interfaces for VIPs
                Burasami
                Hi,
                Thanks for your reply..
                 The Check looks for the IP Masks and map them to the network classes. If it not found one Range in Private Class and one Range in Public class the error occurs. But you can still continue to build your rac as long your ip addresses are ok. In later version of oracle RAC this error is change to a info warning.
                but still the node is not being up... so what cause the problem.

                Thanks & Regards
                Sami
                • 5. Re: Could not find a suitable set of interfaces for VIPs
                  JohnWatson
                  Sami wrote:
                  Hi,
                  Thanks for your reply..
                  The Check looks for the IP Masks and map them to the network classes. If it not found one Range in Private Class and one Range in Public class the error occurs. But you can still continue to build your rac as long your ip addresses are ok. In later version of oracle RAC this error is change to a info warning.
                  but still the node is not being up... so what cause the problem.

                  Thanks & Regards
                  Sami
                  Sami, so far you have described only one issue, which (as I explained) is not the problem.
                  You need to say what the problem is.
                  "the node is not being up" is not an ORacle error message.

                  Edited by: JohnWatson on Nov 2, 2012 9:24 AM
                  • 6. Re: Could not find a suitable set of interfaces for VIPs
                    Burasami
                    Hi All,

                    I have doubt that private ip address is configured at different Ethernet driver such as

                    RAC XXXXXXXX machine
                    eth20                           10.20.2.111                     10.20.2.0
                    RAC YYYYYYY machine
                    eth2                            172.20.2.110                    172.20.2.0
                    I suspect may be due to that. Please clarify me..

                    Thanks
                    Sami