Video Screencast Help

SFHA Solutions 6.0.1: Best practices for setting up your private network configuration for SF Oracle RAC

Created: 27 May 2013 • Updated: 27 May 2013
Blezy's picture

Oracle RAC private network configuration consists of a private interconnect that allows for cluster communications. The private cluster interconnect must be configured over multiple dedicated gigabit Ethernet links. A minimum of one private IP address is required on each node for Oracle Clusterware heartbeat. Additional private IP addresses are required for Oracle database Cache Fusion traffic. VCS uses LLT for communicating between cluster nodes over private interconnects while Oracle Clusterware/Grid Infrastructure uses private IP addresses configured over the private interconnects to communicate between the cluster nodes.

For more information, see:
Planning the private network configuration for Oracle RAC

Depending on the version of Oracle RAC you want to install, use one of the following options to configure the private network configuration for Oracle database Cache Fusion:

Oracle RAC 10g Use either Oracle UDP IPC or VCSIPC/LMX/LLT for the database cache fusion traffic. By default, the database Cache Fusion traffic is configured to use VCSIPC/LMX/LLT.
Oracle RAC 11g You must use UDP IPC for the database Cache Fusion traffic. Symantec recommends using multiple private interconnects for load balancing the cache fusion traffic.

The following practices provide a resilient private network setup:

  • Configure Oracle Clusterware interconnects over LLT links to prevent data corruption.

  • Protect Oracle Clusterware interconnects against NIC failures and link failures. For Oracle RAC 10g Release 2 and 11.2.0.1 versions, the PrivNIC or MultiPrivNIC agent can be used to protect against NIC failures and link failures, if multiple links are available.

    An alternative option is to configure the Oracle Clusterware interconnects over bonded NIC interfaces.

    For 11.2.0.2 and later versions, Symantec recommends the use of alternative solutions such as bonded NIC interfaces or Oracle High Availability IP (HAIP).

  • Configure Oracle Cache Fusion traffic to use the private network. Symantec also recommends that all UDP cache-fusion links be LLT links.

  • Use NIC bonding to provide redundancy for public networks so that Oracle can fail over virtual IP addresses if there is a public link failure.

Additional information can be found in the following documents:
Veritas Storage Foundation for Oracle RAC Administrator's Guide
Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide

Veritas Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.