Exadata - How to Change interconnect bonding interface on the compute nodes
(Doc ID 1468364.1)
Last updated on MARCH 02, 2017
Applies to:Exadata Database Machine V2 - Version All Versions and later
Information in this document applies to any platform.
***Checked for relevance on 09-Dec-2013***
As described in the Exadata Database Machine Owners guide, Chapter 8
Extending Oracle Exadata Database Machine, Configuring the New Hardware:
"Earlier releases of Oracle Exadata Database Machine X2-2 (with X4170 and X4275 servers) used bond0 and bond1 as the names for the bonded InfiniBand
and bonded Ethernet client networks, respectively. In the current release, bondib0 and bondeth0 are used for the bonded InfiniBand and bonded Ethernet
client networks. If you are adding new servers to an existing Oracle Exadata Database Machine X2-2 (with X4170 and X4275 servers), then ensure the
database servers use the same names for bonded configuration. You can either change the new database servers to match the existing server interface names,
or change the existing server interface names and Oracle Cluster Registry (OCR) configuration to match the new servers. Use the oifcfg utility to
change the OCR configuration. The interface names for Exadata Storage Servers do not have to be changed."
This document describes the steps to rename the bonding interface on the existing nodes of the cluster, primarly during the expansion of a cluster by adding another rack
Only Compute nodes running on servers SUN FIRE X4170 SERVER bonding interface defined as bond0
After the procedure, on the compute nodes, bonding interface will be identified by bondib0
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|