High availability solutions for Oracle RAC private network
Table: High availability solutions for Oracle RAC private network lists the high availability solutions that you may adopt for your private network.
Related information
Table: High availability solutions for Oracle RAC private network
| Options | Description |
|---|---|
| Using link aggregation/ NIC bonding for Oracle Clusterware | Use a native NIC bonding solution to provide redundancy, in case of NIC failures. |
| Make sure that a link configured under a aggregated link or NIC bond is not configured as a | |
| separate LLT link. | |
| When LLT is configured over a bonded interface, do one of the following steps to prevent | |
| GAB from reporting jeopardy membership: | |
| - Configure an additional NIC under LLT in addition to the bonded NIC. | |
- Add the following line in the /etc/llttab file: lang=txt set-dbg-minlinks 2 |
|
| Using PrivNIC/MultiPrivNIC agents | Note: The PrivNIC and MultiPrivNIC agents are no longer supported in Oracle RAC 11.2.0.2 and later versions for managing cluster interconnects. For 11.2.0.2 and later versions, Veritas recommends the use of alternative solutions such as bonded NIC interfaces or Oracle HAIP. |
| Use the PrivNIC agent when operating | |
| system limitations prevent you from using NIC bonding to provide | |
| high availability using multiple network interfaces. | |
| Use the MultiPrivNIC agent when | |
| operating system limitations prevent you from using NIC bonding | |
| to provide high availability and increased bandwidth using | |
| multiple network interfaces. | |
| For more deployment scenarios that illustrate the use of PrivNIC/MultiPrivNIC deployments, see the appendix "SF Oracle RAC deployment scenarios" in this document. |