Public interfaces should be used to configure virtual

在OEL 5.8安装oracle clusterware 10.2.0.1，在最后一个node上运行root.sh最后出现以下错误：

The given interface(s), "eth0" is not public. Public interfaces should be used to configure virtual IPs.

以root身份，重新运行vipca配置IP地址解决

因为以下文档解释的问题，有时出错信息还有可能是：

[Error 0(Native: listNetInterfaces:[3])]

此时要参看这个文档：

10gR2 RAC Install issues on Oracle EL5 or RHEL5 or SLES10 (VIPCA / SRVCTL / OUI Failures) [ID 414163.1]

设定文档中提到的workground 2 和workground 3

查看了metlink：

VIPCA Fails Complaining That Interface Is Not Public (Doc ID 316583.1)

To Bottom

---

In this Document   Symptoms   Changes   Cause   Solution      Scalability RAC Community   References APPLIES TO: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.1 - Release: 10.2 to 10.2 Information in this document applies to any platform. Oracle Clusterware Checked for relevance on 05-Oct-20008 ***Checked for relevance on 12-Oct-2010*** SYMPTOMS During CRS install while running root.sh, The following messages are displayed 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. CHANGES You are running root.sh  In 10gR1 (VIPs are created when running root.sh from the database home after the RDBMS installation) In 10gR2 (VIPs are created when running root.sh from the CRS home on the last node) CAUSE When verifying the IP addresses, VIPCA tries to determine if a IP address is valid or not. In this case, VIPCA finds that the IPs are in the range generally reserved for Private networks. (For example IP addresses like 192.168.* and 10.10.*.) As per RFC 1918 networks in the following ranges are considered private. For more details please reviewhttp://tools.ietf.org/html/rfc1918 10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix 192.168.0.0 - 192.168.255.255 (192.168/16 prefix   While it is possible for these IPs to be used as VIP, it is usually reserved for Private interconnects. Therefore VIPCA errors out when running in silent mode as a warning to the user to double check the Virtual IPs. SOLUTION Run the command VIPCA (as root on Unix or as local administrator on windows) manually.  #<ORA_CRS_HOME>/bin/vipca This can be done immediately after the root.sh shows the errors on the screen. OR  the error can be ignored and the Virtual IPs added manually using the following srvctl commands #<ORA_CRS_HOME/bin/srvctl add nodeapps -n crmnode1 -o /ora/ora10 -A 1.2.3.4/255.255.255.0/lan0 The interface name specified in the srvctl command (lan0 in this example) should be same as the interface where the public IP resides. For details on the various attributes of add nodeapps please check the following documentation link. http://download-west.oracle.com/docs/cd/B19306_01/rac.102/b14197/srvctladmin.htm After adding the nodeapps, it can be started by executing the following command srvctl start nodeapps -n <nodename> Scalability RAC Community To discuss this topic further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Scalability RAC Community. REFERENCES NOTE:338924.1 - CLUVFY Fails With Error: Could not find a suitable set of interfaces for VIPs

VIPCA Fails Complaining That Interface Is Not Public (Doc ID 316583.1)

To Bottom

---

In this Document   Symptoms   Changes   Cause   Solution      Scalability RAC Community   References APPLIES TO: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.1 - Release: 10.2 to 10.2 Information in this document applies to any platform. Oracle Clusterware Checked for relevance on 05-Oct-20008 ***Checked for relevance on 12-Oct-2010*** SYMPTOMS During CRS install while running root.sh, The following messages are displayed 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. CHANGES You are running root.sh  In 10gR1 (VIPs are created when running root.sh from the database home after the RDBMS installation) In 10gR2 (VIPs are created when running root.sh from the CRS home on the last node) CAUSE When verifying the IP addresses, VIPCA tries to determine if a IP address is valid or not. In this case, VIPCA finds that the IPs are in the range generally reserved for Private networks. (For example IP addresses like 192.168.* and 10.10.*.) As per RFC 1918 networks in the following ranges are considered private. For more details please reviewhttp://tools.ietf.org/html/rfc1918 10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix 192.168.0.0 - 192.168.255.255 (192.168/16 prefix   While it is possible for these IPs to be used as VIP, it is usually reserved for Private interconnects. Therefore VIPCA errors out when running in silent mode as a warning to the user to double check the Virtual IPs. SOLUTION Run the command VIPCA (as root on Unix or as local administrator on windows) manually.  #<ORA_CRS_HOME>/bin/vipca This can be done immediately after the root.sh shows the errors on the screen. OR  the error can be ignored and the Virtual IPs added manually using the following srvctl commands #<ORA_CRS_HOME/bin/srvctl add nodeapps -n crmnode1 -o /ora/ora10 -A 1.2.3.4/255.255.255.0/lan0 The interface name specified in the srvctl command (lan0 in this example) should be same as the interface where the public IP resides. For details on the various attributes of add nodeapps please check the following documentation link. http://download-west.oracle.com/docs/cd/B19306_01/rac.102/b14197/srvctladmin.htm After adding the nodeapps, it can be started by executing the following command srvctl start nodeapps -n <nodename> Scalability RAC Community To discuss this topic further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Scalability RAC Community. REFERENCES NOTE:338924.1 - CLUVFY Fails With Error: Could not find a suitable set of interfaces for VIPs