Professional Documents
Culture Documents
Cluster Interconnect in Oracle 10g and 11gR1 RAC (Doc ID 787420.1)
Cluster Interconnect in Oracle 10g and 11gR1 RAC (Doc ID 787420.1)
Cluster Interconnect in Oracle 10g and 11gR1 RAC (Doc ID 787420.1)
Document 787420.1
Type: BULLETIN
In this Document
Purpose
Scope
Details
Physical Layout of the Private Interconnect
Why Do We Need a Private Interconnect ?
Interconnect Failure
Interconnect High Availability
Private Interconnect for Oracle Clusterware
Private Interconnect for RAC
Identification of the Private Interconnect for RAC
Private Interconnect for ASM
Different Interconnects for Clusterware and RAC
CLUSTER_INTERCONNECTS Parameter
Changing the Private Interconnect
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.7 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.1.0.2 to 11.1.0.7
Last Updated: 20-Feb-2012
***Checked for relevance on 20-Aug-2010***
PURPOSE
The purpose of this note is to make DBAs and System Administrators familiar with the concept of the cluster or
private interconnect and its usage in Oracle Clusterware and Oracle Real Application Clusters
SCOPE
The main audience is DBAs and System Administrators. This note applies to Oracle Clusterware and Oracle Real
Application Clusters releases 10.1, 10.2 and 11.1.
DETAILS
The term 'Private Interconnect' or 'Cluster Interconnect' is the private communication link between cluster nodes.
For Oracle Real Application Clusters and Oracle Clusterware we can differentiate between
1. Physical interface (including NIC, cables and switches)
2. Private Interconnect used by Oracle Clusterware
3. Private Interconnect used by Oracle Real Application Clusters (RAC)
1/4
12/20/2013
Document 787420.1
The basic requirements are described in the Installation Guide for each platform. Additional information about
certification can be found on Metalink Certify.
The interconnect as identified by both subnet number and interface name must be configured on all clustered
nodes.
A switch between the clustered nodes is an absolute requirement.
Interconnect Failure
The private interconnect is the critical communication link between nodes and instances. Network errors will
negatively impact Oracle Clusterware communication as well as RAC communication and performance.
Private interconnect failures are recognized by Oracle Clusterware and result in what is known as a 'split-brain' or
subdivided cluster.
A subdivided cluster can result in data corruption, consequently immediate action is taken to resolve this condition.
Interconnect failures, therefore, result in a node or subset of nodes in the cluster shutting down. In the case of two
equally sized sub clusters, it is basically random which sub cluster will survive, and a customer's architecture and
design should be based on this. At this time the Oracle Clusterware happens to use the node numbers to resolve
this, but this could change in the future.
RAC instances will wait for the end of cluster reconfiguration to start their own reconfiguration.
You may also check the private node name in the ocrdump output.
[SYSTEM.css.node_numbers.node1.privatename]
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_325&id=787420.1
2/4
12/20/2013
Document 787420.1
ORATEXT : node1-priv
Although the Oracle Universal Installer allows IP addresses when prompted for the private node name you should
always use the host names defined in the hosts file or DNS. This enables you to change the IP addresses when you
need to move the server to a different IP range. You would have to reinstall Oracle Clusterware when you used IPaddresses instead of host names and you are changing the server's IP adresses.
Note that there might be a difference to the interconnect defined in the OCR because
the value was overridden by setting the CLUSTER_INTERCONNECTS parameter or when
Oracle selected another interconnect because the one in the OCR was not available.
Protocol
Unix and Linux
cluster interconnect IPC version:Oracle UDP/IP (generic)
Windows:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_325&id=787420.1
3/4
12/20/2013
Document 787420.1
CLUSTER_INTERCONNECTS Parameter
This parameter overrides the value configured in the OCR. You may specify multiple IP addresses in
CLUSTER_INTERCONNECTS which will cause all defined interfaces to be used. Keep in mind that a failure of one of
those interfaces will cause the instance to fail. The failed instance can only be restarted when all the interfaces are
fixed or you start all the instances without the faulty interface.
REFERENCES
NOTE:283684.1 - How to Modify Private Network Information in Oracle Clusterware
NOTE:341788.1 - Recommendation for the Real Application Cluster Interconnect and Jumbo Frames
NOTE:368464.1 - How to Setup IPMP as Cluster Interconnect
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_325&id=787420.1
4/4