SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent


SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent
Prev	Appendix I. SF Oracle RAC deployment scenarios	Next

This section illustrates the recommended configuration for the following scenario:

Deployment scenario

Oracle RAC with UDP IPC is configured to use a bonded NIC interface for distribution of Oracle database cache fusion traffic.

A second link is configured as a standby link.

Recommendation

Use the PrivNIC agent.

Sample main.cf configuration file

The following sample main.cf file describes the configuration:

/etc/VRTSvcs/conf/sample_rac/sfrac02_main.cf

Note:

You must replace the eth1 interface in the sample file with the bonded NIC interface you use in the scenario and eth2 in the sample file with the NIC3 interface in the scenario.

In the illustrated configuration:

A common IP address is used for Oracle Clusterware communication and Oracle database cache fusion that is distributed over two underlying physical links of the bonded NIC interface. The bonded NIC interface is configured as a single LLT link.
The CFS/CVM/VCS metadata also travels through the bonded link.
In the event of a bonded link failure, the PrivNIC agent fails over the private network IP address from the failed link to the available standby LLT link. When the link is restored, the IP address is failed back to the original link.

Figure: SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent illustrates the logical view of a two-node SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent.

Figure: SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent

Prev	Up	Next
SF Oracle RAC cluster with isolated Oracle traffic and MultiPrivNIC agent	Home	Configuration diagrams for setting up server-based I/O fencing