CLUVFY Fails With Error: Could not find a suitable set of interfaces for VIPs or Private Interconnect

Last updated on AUGUST 31, 2017

Applies to:

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.
========================

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

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

WARNING: Could not find a suitable set of interfaces for the private interconnect

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

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