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


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

This section illustrates the recommended configuration for the following scenario:

Deployment scenario

A bonded NIC interface is used along with another NIC interface to distribute Oracle RAC 10g database cache fusion traffic using VCS IPC over LMX/LLT.

Recommendation

Use the PrivNIC agent.

Sample main.cf configuration file

The following sample main.cf file describes the configuration:

/etc/VRTSvcs/conf/sample_rac/sfrac01_main.cf

Note:

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

In the illustrated configuration:

Oracle uses VCS IPC over LMX/LLT for cache fusion.
One common private network IP address is used for Oracle database cache fusion and Oracle Clusterware communication that takes place over the bonded NIC interface, configured as an LLT link.
The Oracle Clusterware communication takes place over the other LLT private interconnect link.
The Oracle database cache fusion as well as the CFS/CVM/VCS metadata travels through LLT over the three physical links.
In the event of a bonded NIC interface failure, the PrivNIC agent fails over the private network IP address from the failed link to the other available 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, VCS IPC and PrivNIC agent (Oracle RAC 10g) illustrates the logical view of a two-node SF Oracle RAC cluster with NIC bonding, VCS IPC, and PrivNIC agent (Oracle RAC 10g).

Figure: SF Oracle RAC cluster with NIC bonding, VCS IPC and PrivNIC agent (Oracle RAC 10g)

Prev	Up	Next
SF Oracle RAC cluster with isolated Oracle traffic and MultiPrivNIC agent	Home	SF Oracle RAC cluster with NIC bonding, UDP IPC, and PrivNIC agent