RedundantInterconnectwithHighlyAvailableIP (HAIP)

Starting from 11.2.0.2, RedundantInterconnectwithHighlyAvailableIP (HAIP) is added to the Oracle cluster software GridInfrastructure (GI ).

Starting from 11.2.0.2, Redundant Interconnect with Highly Available IP (HAIP) is added to the cluster software Grid Infrastructure (GI) of Oracle.

Starting from 11.2.0.2, Redundant Interconnect with Highly Available IP (HAIP) was added to the cluster software Grid Infrastructure (GI) of Oracle to achieve high availability and load balancing for the private network of the cluster.

Before 11.2.0.2, Private Network redundancy is generally achieved through Nic binding on the OS (such as bonding and EtherChannel). With HAIP, you can achieve private network Nic redundancy without using Nic binding.

When installing GI, you can define multiple private network cards to achieve private network redundancy,

After installation, the HAIP address is automatically set to 169. 254. *. *. This address cannot be set manually. A haip can contain at least one IP address and a maximum of four IP addresses (one Nic and one HAIP address; two NICs, two HAIP addresses; three or more HAIP addresses; and four HAIP addresses ), evenly distributed on private network cards.

Case:
1. view the HAIP Resource Status
$ Crsctl stat res-t-init
NAME
Target state server STATE_DETAILS Cluster Resources
Bytes -------------------------------------------------------------------------------------------------
Ora. cluster_interconnect.haip
ONLINE node2 1

2. view the HAIP address and distribution.
# Ifconfig-
Eth1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 66
Inet addr: 192.168.254.32 Bcast: 192.168.254.255 Mask: 255.255.255.0
Inet6 addr: fe80: 20c: 29ff: fe4b: b766/64 Scope: Link
Up broadcast running multicast mtu: 1500 Metric: 1
......

Eth1: 1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 66
Inet addr: 169.254.31.199 Bcast: 169.254.127.255 Mask: 255.255.128.0 <=== HAIP address one.
Up broadcast running multicast mtu: 1500 Metric: 1
Interrupt: 193 Base address: 0x1800

Eth2 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 192.168.254.33 Bcast: 192.168.254.255 Mask: 255.255.255.0
Inet6 addr: fe80: 20c: 29ff: fe4b: b770/64 Scope: Link
Up broadcast running multicast mtu: 1500 Metric: 1
......

Eth2: 1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 169.254.185.222 Bcast: 169.254.255.255 Mask: 255.255.128.0 <=== HAIP address two.
Up broadcast running multicast mtu: 1500 Metric: 1
Interrupt: 169 Base address: 0x1880

The haip is evenly distributed on two private network cards.

3. After eth1 is disconnected.
Eth2 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 192.168.254.33 Bcast: 192.168.254.255 Mask: 255.255.255.0
Inet6 addr: fe80: 20c: 29ff: fe4b: b770/64 Scope: Link
Up broadcast running multicast mtu: 1500 Metric: 1
RX packets: 3206 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 3916 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 FIG: 1000
RX bytes: 1474658 (1.4 MiB) TX bytes: 2838774 (2.7 MiB)
Interrupt: 169 Base address: 0x1880

Eth2: 1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 169.254.185.222 Bcast: 169.254.255.255 Mask: 255.255.128.0 <=== HAIP address two.
Up broadcast running multicast mtu: 1500 Metric: 1
Interrupt: 169 Base address: 0x1880

Eth2: 2 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 169.254.31.199 Bcast: 169.254.127.255 Mask: 255.255.128.0 <=== HAIP address one.
Up broadcast running multicast mtu: 1500 Metric: 1
Interrupt: 169 Base address: 0x1880

HAIP one drifted to eth2.

4. After eth1 is restored.
Eth1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 66
Inet addr: 192.168.254.32 Bcast: 192.168.254.255 Mask: 255.255.255.0
Inet6 addr: fe80: 20c: 29ff: fe4b: b766/64 Scope: Link
Up broadcast running multicast mtu: 1500 Metric: 1
......

Eth1: 1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 66
Inet addr: 169.254.31.199 Bcast: 169.254.127.255 Mask: 255.255.128.0 <=== HAIP address one.
Up broadcast running multicast mtu: 1500 Metric: 1
Interrupt: 193 Base address: 0x1800

Eth2 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 192.168.254.33 Bcast: 192.168.254.255 Mask: 255.255.255.0
Inet6 addr: fe80: 20c: 29ff: fe4b: b770/64 Scope: Link
Up broadcast running multicast mtu: 1500 Metric: 1
......

Eth2: 1 Link encap: Ethernet HWaddr 00: 0C: 29: 4B: B7: 70
Inet addr: 169.254.185.222 Bcast: 169.254.255.255 Mask: 255.255.128.0 <=== HAIP address two.
Up broadcast running multicast mtu: 1500 Metric: 1
Interrupt: 169 Base address: 0x1880

HAIP one returns to eth1.

Note: failure of the HAIP address does not affect ocssd, that is, failure of the HAIP address does not cause node restart.

Impact of HAIP on databases and ASM

The database and the ASM instance use this HAIP as the cluster interconnect. The following is a snippet of alert. log.

Cluster communication is configured to use the following interface (s) for this instance
169.254.31.199
169.254.185.222
Cluster interconnect IPC version: Oracle UDP/IP (generic)
IPC Vendor 1 proto 2

Oracle databases and ASM instances can use HAIP to achieve high availability and load balancing for private network communication. Intranet traffic will achieve load balancing on these private network cards,
If a network card fails, the HAIP on it will automatically switch to another available private network card, so as not to affect the communication between the private network.

Note: HAIP cannot be manually stopped or disabled, unless it is not supported by some versions or platforms.

For more information about HAIP, see My Oracle Support Note 1210883.1.