HBA Card

In computer hardware, a host controller, host adapter, or host bus adapter (HBA) connects a host system (the computer) to other network and storage devices.

A host bus adapter (HBA) is a circuit board and/or integrated circuit adapter that provides input/output (I/O) processing and physical connectivity between a server and a storage device. Because the HBA relieves the host microprocessor of both data storage and retrieval tasks, it can improve the server’s performance time. An HBA and its associated disk subsystems are sometimes referred to as a disk channel.

Single HBA Cards have two ports

Each HBA has a unique World Wide Name (WWN), which is similar to an Ethernet MAC address in that it uses an OUI assigned by the IEEE.

However, WWNs are longer (8 bytes).
There are two types of WWNs on a HBA;
a node WWN (WWNN), which is shared by all ports on a host bus adapter, and
a port WWN (WWPN), which is unique to each port.

There are HBA models of different speeds: 1Gbit/s, 2Gbit/s, 4Gbit/s, 8Gbit/s, 16Gbit/s, 10Gbit/s and 20Gbit/s.

SAN Storage Recommendations for Oracle RAC Installation

Sample configuration

SAN Storage having Dual Controller

HDD Size: 300Gb or +
No. of Hdd required : 4 + (1 optional for hot spare)
RAID Requirement : RAID 10
300Gb X 4 =~ 1200GB
Usable HDD Space after RAID 10 =~ 559 GB

SAS HDD 10k or max

front end connectivity for the storage

SAS Connectivity having 6 Gbps


FC Connectivity having 8/4 Gbps

Fibre Channel(FC) and Serial Attached SCSI (SAS) will continue to be the interfaces of choice on the SAN.

A PCI slot is used to add extension cards to a machine.

e.g. HBA Card

free PCI slots in each servers

choose the compatible HBA card with SERVER Configuration






Is crossover cable supported as an interconnect with RAC on any platform ?

Answer By: Oracle Metal ink Support
Is crossover cable supported as an interconnect with RAC on any platform ?
NO. CROSS OVER CABLES ARE NOT SUPPORTED. The requirement is to use a switch:

Detailed Reasons:

1) cross-cabling limits the expansion of RAC to two nodes

2) cross-cabling is unstable:

a) Some NIC cards do not work properly with it. They are not able to negotiate the DTE/DCE clocking, and will thus not function. These NICS were made cheaper by assuming that the switch was going to have the clock. Unfortunately there is no way to know which NICs do not have that clock.

b) Media sense behavior on various OS’s (most notably Windows) will bring a NIC down when a cable is disconnected. Either of these issues can lead to cluster instability and lead to ORA-29740 errors (node evictions).

Due to the benefits and stability provided by a switch, and their afforability ($200 for a simple 16 port GigE switch), and the expense and time related to dealing with issues when one does not exist, this is the only supported configuration.

From a purely technology point of view Oracle does not care if the customer uses cross over cable or router or switches to deliver a message. However, we know from experience that a lot of adapters misbehave when used in a crossover configuration and cause a lot of problems for RAC. Hence we have stated on certify that we do not support crossover cables to avoid false bugs and finger pointing amongst the various parties: Oracle, Hardware vendors, Os vendors etc…

Private Network Requirement for RAC Cluster heartbeat
 We require to /30 Network IPs (e.g. Private VLAN) to be setup between SERVER-1 and SERVER-2



Speed of NIC should be 1 Gbps or max.