Tuning the Cluster Interconnect - Expert Oracle RAC Performance Diagnostics and Tuning - page 450

The preceding output illustrates there are two interfaces currently configured on the node: bond0 and bond2 . Both
of these interfaces have used NIC bonding for high availability. Both of the interfaces are registered in the OCR. In
the preceding output, bond0 has the value Y in column Public ( PUB_KSXPIA ), indicating it's the public interface; and
bond2 is the private interface (identified by the value N ). If the correct IP addresses are not visible, it is an indication of
incorrect installation and configuration of the RAC environment.

■ Note Yet another method to validate the interconnect configuration is to use the oifcfg utility.

[oracle@ssky1l3p1 ~]$ oifcfg iflist -p -n
eth0 192.168.2.0 PRIVATE 255.255.255.0
eth1 10.2.4.0 PRIVATE 255.255.255.0
eth1 169.254.192.0 UNKNOWN 255.255.192.0
eth1 169.254.0.0 UNKNOWN 255.255.192.0
eth2 10.2.4.0 PRIVATE 255.255.255.0
eth2 169.254.64.0 UNKNOWN 255.255.192.0
eth3 10.2.4.0 PRIVATE 255.255.255.0
eth3 169.254.128.0 UNKNOWN 255.255.192.0

In Oracle Database 11g Release 2 (11.2.0.2), the configuration has changed. If the installation is a new install
using this version, Oracle assigns an HAIP for the private interconnect as well. If the RAC configuration is an upgrade
from 11.2.0.1 to 11.2.0.2, Oracle retains the existing configuration unless manually modified.
The private interconnect is no longer recorded in the OCR file; instead, Oracle keeps the information locally in
“GPnP” (Grid Plug and Play) profiles.
For every network available on the host servers, Oracle provides the list and allows for multiple networks to be
selected as the private network. During the grid infrastructure (GI) installation (Figure 14-2 ), these private networks
are all assigned IPs called HAIPs similar to the VIPs assigned to the public networks during the GI configuration.