Oracle 11g R2 and how to configure the network adapters

With very basic knowledge of Linux and NO Oracle RAC experience I am trying to install and configure Oracle 11g R2 RAC on WMware Server 2.0 running on Windows 7 for educational and testing purpose..

At the moment I have already done the following.
1. Created VMware Virtual Machine
2. Installed Oracle Enterpise Linux 5.5
3. Installed the VMware Tools (synced the host time)
4. Installed the pre-required rpm packages
5. Modified the Kernel parameters
6. Created the Oracle user and groups
7. Modified the /etc/security/limits.conf
8. Configured the Oracle .bash_profile
9. Added 5 independent persistance shared 12GB disks, configured  the vmware configuration so they are not locked and restarted the Linux guest.
10.Once guest was up again I discovered the disks and configured with fdisk.
11. Installed the oracleasm* packages matching my kernel
12. Successfully added the disks
# /usr/sbin/oracleasm listdisks
DISK1
DISK2
DISK3
DISK4
DISK5
13. copied grid and database setup packages to /u01/app so it is ready to be installed.

Now I think I am only missing one important configuration before going ahead with cloning my first node and going ahead with the Oracle grid and database setup which is the network adapter installation and configuration.

Searching the internet I see some people use 2 network adopters while others use 4 so I am a bit confused.

What I think I do know is that I am going to be asking our IT for 3 DNS entries for my RAC tests.
So I will define my SCAN address perhaps something like VMRAC-SCAN.ourdomain.com and get 3 ip addresses assigned to it.


Could someone now explain how to configure the network adapters, how many and how should they be configured on those two nodes. As detailed as possible would be extremely appreciated. And if something from the above lists is wrong or missing then let me know.

Thanks a lot in advance!
LVL 1
peturgretarsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Richard OlutolaConsultantCommented:
You need 2 NIC per node.

For each node,
1. define the public IP address on the first NIC, and define the host name in the hosts file or DNS
2. define the private (interconnect) IP address on the 2nd NIC. This can be an arbitrary IP address such as 192.168.0.1 (192.168.0.2 on node 2)

R.
peturgretarsAuthor Commented:
Would it be possible to get more detailed example? Unfortunately I am not too confident about the network configuration and I want to make sure I do it right the first time.

Let's say that the SCAN name I want is "VMRAC-SCAN.ourdomain.com"  and I get the following 3 IP addresses entered to our DNS server.

"VMRAC-SCAN.ourdomain.com"
192.168.2.100
192.168.2.101
192.168.2.102

Based on that how would you in details configure the vmnode1.ourdomain.com and  vmnode2.ourdomain.com network adapters and hosts files?
If some other network related configuration is needed could you please list?

VMNODE1.ourdomain.com
eth0:
eth1:

entries in hosts file would then be:

VMNODE1.ourdomain.com
eth0:
eth1:

entries in hosts file would then be:

Thanks!!
ptg.

Richard OlutolaConsultantCommented:
You would declare the SCAN address during the installation so don't worry about that. Just ensure it is defined on DNS.

regarding the other netword details, for each node you require a public address, a virtual address, and a private address.

Assign the public address to eth0 and private address to eth1
eg on Node1

192.168.2.5 vmnode1.ourdomain.com vmnode1 (eth0)
192.168.2.6 vmnode1-vip.ourdomain.com vmnode1-vip (this will be assigned to eth0 automatically by the installer)
192.168.1.1 vmnode1-priv.ourdomain.com vmnode1-priv (eth1)

private address can be anything you like as long as it can ping node 2. So node2 would have 192.168.1.2. Ideally the private IP should be connected to a dedicated gigabit switch for production.

Is this clear?

R.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

peturgretarsAuthor Commented:
Thanks for the answers and happy holidays!
I think I have got it but I would appreciate your comments please on the following scenario?

VMNODE1
eth0:
vmnode1.ourdomain.com 192.168.2.10 >> Added to DNS
vmnode1-vip.ourdomain.com 192.168.2.11 >> Added to DNS

eth1
vmnode1-priv.ourdomain.com 192.168.1.1 >> Enough to add to hosts?


VMNODE2

eth0
vmnode2.ourdomain.com 192.168.2.20 >> Added to DNS
vmnode2-vip.ourdomain.com 192.168.2.21 >> Added to DNS

eth1
vmnode2-priv.ourdomain.com 192.168.1.2 >> Enough to add to hosts?

Add to DNS:
VMRAC-SCAN.ourdomain.com 192.168.2.100
VMRAC-SCAN.ourdomain.com 192.168.2.101
VMRAC-SCAN.ourdomain.com 192.168.2.102

Thanks again!
ptg.
Richard OlutolaConsultantCommented:
That looks good to me.

As for the private IPs, yes it is enough to add to hosts file.

R.
peturgretarsAuthor Commented:
Thanks for taking time during Christmas holidays to answer!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.