CLUVFY Fails With Error: Could not find a suitable set of interfaces for VIPs [ID 338924.1]

CLUVFY Fails With Error: Could not find a suitable set of interfaces for VIPs [ID 338924.1]
		Modified 29-JUL-2010     Type PROBLEM     Status PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

---

 

 

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7 - Release: 10.2 to 11.1
Information in this document applies to any platform.

Symptoms

When running cluvfy to check network connectivity at various stages of the RAC/CRS installation process, cluvfy fails with errors similar to the following:

=========================
Suitable interfaces for the private interconnect on subnet "10.0.0.0":
node1 eth0:10.0.0.1
node2 eth0:10.0.0.2

Suitable interfaces for the private interconnect on subnet "192.168.1.0":
node1_internal eth1:192.168.1.2
node2_internal eth1:192.168.1.1

ERROR:
Could not find a suitable set of interfaces for VIPs.

Result: Node connectivity check failed.

========================

On Oracle 11g, you may still see a warning in some cases, such as:

========================

WARNING:
Could not find a suitable set of interfaces for VIPs.
========================

Output seen will be comparable to that noted above, but IP addresses and node_names may be different - i.e. the node names of 'node1','node2','node1_internal','node2_internal'  will be substituted with your actual Public and Private node names.

 

A second problem that will be encountered in this situation is that at the end of the CRS installation for 10gR2, VIPCA will be run automatically in silent mode, as one of the 'optional' configuration assistants.  In this scenario, the VIPCA will fail at the end of the CRS installation.   The InstallActions log will show output such as:

> />> Oracle CRS stack installed and running under init(1M)
> />> Running vipca(silent) for configuring nodeapps
> />> The given interface(s), "eth0" is not public. Public interfaces should
> />> be used to configure virtual IPs.

Cause

This issue occurs due to incorrect assumptions made in cluvfy and vipca based on an Internet Best Practice document - "RFC1918 - Address Allocation for Private Internets".  This Internet Best Practice RFC can be viewed here:

http://www.faqs.org/rfcs/rfc1918.html

From an Oracle perspective, this issue is tracked in BUG:4437727

Per BUG:4437727, cluvfy makes an incorrect assumption based on RFC 1918 that any IP address/subnet that begins with any of the following octets is private and hence may not be fit for use as a VIP:

172.16.x.x  through 172.31.x.x
192.168.x.x
10.x.x.x

However, this assumption does not take into account that it is possible to use these IPs as Public IP's on an internal network  (or intranet).   Therefore, it is very common to use IP addresses in these ranges as Public IP's and as Virtual IP(s), and this is a supported configuration.

Solution

The solution to the error above that is given when running 'cluvfy' is to simply ignore it if you intend to use an IP in one of the above ranges for your VIP. The installation and configuration can continue with no corrective action necessary.

One result of this, as noted in the problem section, is that the silent VIPCA will fail at the end of the 10gR2 CRS installation.   This is because VIPCA is running in silent mode and is trying to notify that the IPs that were provided may not be fit to be used as VIP(s). To correct this, you can manually execute the VIPCA GUI after the CRS installation is complete.  VIPCA needs to be executed from the CRS_HOME/bin directory as the 'root'  user  (on Unix/Linux)  or as a Local Administrator (on Windows):

$ cd $ORA_CRS_HOME/bin

$ ./vipca

Follow the prompts for VIPCA to select the appropriate interface for the public network, and assign the VIPs for each node when prompted.  Manually running VIPCA in the GUI mode, using the same IP addresses, should complete successfully.

Note that if you patch to 10.2.0.3 or above, VIPCA will run correctly in silent mode.  The command to re-run vipca silently can be found in CRS_HOME/cfgtoollogs  (or CRS_HOME/cfgtoollogs) in the file 'configToolAllCommands' or 'configToolFailedCommands'.  Thus, in the case of a new install, the silent mode VIPCA command will fail after the 10.2.0.1 base release install, but once the CRS Home is patched to 10.2.0.3 or above, vipca can be re-run silently, without the need to invoke the GUI tool

References

NOTE:316583.1 - VIPCA FAILS COMPLAINING THAT INTERFACE IS NOT PUBLIC

Related Products Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition Keywords INSTALLATION FAILS; INTERCONNECT; PRIVATE INTERCONNECT; PRIVATE NETWORKS Errors RFC-1918

Back to top

Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement