Oracle 11gR2 11.2.0.3 2-node RAC on Windows 2008 on VMware Workstation 9 – Part II

Time Required: 30 minutes

Class Materials:

  • None

Next we need to add additional networking components to allow our RAC nodes to communicate.

Oracle RAC requires two separate networks, one for public traffic and one for private cluster traffic. Both adapters must use static IP addresses.

VMware Workstation already installed a Bridged Adapter as part of the install process, and this adapter will provde internet access to our VM. But in most cases, the IP address of this adapter will change as DHCP leases expire, or in the case of a laptop, the machine moves from network to network.

Therefore, we need to add two additional NICs on virtual networks between the RAC nodes, one to be our public network and the other to be our private network.

In addition we will need static IP addresses for the virtual IPs of the cluster, and for the SCAN (Single Client Address Name) address. It is a good idea to have these ready before you start. In my example I am going to use the following:

Rodolfo Mimi
Public IP 10.10.1.30 10.10.1.40
Private IP 10.10.2.30 10.10.2.40
Virtual IP 10.10.1.31 10.10.1.41
SCAN IP 10.10.1.32 10.10.1.42

If you do not have virtual networks for the 10.10.1.x and 10.10.2.x subnets already set up, then you will need to do the following:

Use the VMware Workstation interface and select Edit->Virtual Network Editor.

This allows us to create new virtual networks that allow our guest VMs to talk amongst themselves, to the host computer and/or to the outside world.

For this example I am going to create VMnet2 and VMnet3.

VMnet2 will be a host-only network allowing communication to other VMs and the host, but not to the outside world. We will assign a Subnet IP of 10.10.1.0 to VMnet2, and a Subnet mask of 255.255.255.0

VMnet3 will also be a host-only network allowing communication to other VMs and the host, but not to the outside world. We will assign a Subnet IP of 10.10.2.0 to VMnet3, and a Subnet mask of 255.255.255.0

For both VMnet2 and VMnet3 DHCP is enabled.

Now we have our two networks created in VMware, we will add two new NICs to our VM. Shut down your new Windows VM and if you want, make a clone or snapshot backup.

Right click on the VM in the VMware Workstation menu, and select Settings. This will bring up the Virtual Machine Settings panel.

Now click Add

The Add Hardware Wizard allows us to select Network Adapter

On the Network Adapter Type menu, we will select the Custom: Specific virtual network radio button, and use the drop down to select VMnet2.

Now repeat the above steps to add another Network Adapter, this time using VMnet3.

Our final VM hardware configuration should look like this:

Restart the Windows VM and log in as Administrator.

Start a command prompt and type ncpa.cpl to access the Network Connections interface. You can also reach this interface by selecting:

Start->Control Panel->View network status and tasks->Change Adapter Settings

From this interface we can see three network adapters listed. In my example they are named:

  • Local Area Connection
  • Local Area Connection 2
  • Local Area Connection 3

The first Local Area Connection is the bridged adapter to the internet. We will not change this.

Local Area Connection 2 is the new NIC we added on VMnet2. This will be our public network. Right click on the adapter and select Rename.

Change the name of the adapter to Public.

Now right click on the newly named Public adapter and select Properties.

At the properties panel, highlight the Internet Protocol Version 4 (TCP/IPv4) option and select Properties.

When the properties window open, change the selection to Use the following IP address: and enter the IP address as 10.10.1.30 or whatever you have selected for your public IP address.

The Subnet mask should be 255.255.255.0.

Leave the Default gateway blank.

Select Use the following DNS server addresses: and then enter the Preferred DNS server as 127.0.0.1. This will point DNS requests back to the local machine. We will be installing a DNS server in an upcoming step.

If all looks good, click OK.

Now rename the Local Area Connection 3 adapter to Private.

Using the same procedure you used for the Public adapter, set the IP address to 10.10.2.30, remembering to set the subnet mask and DNS server entries as before.

Now using the same Network connections interface, press the ALT key to access the Advanced Menu. Then select Advanced Settings. You can also short cut this as ALT-S/ALT-N.

In the Advanced Settings menu, use the green arrow keys to the right to move the Public connection to the top of the bind order, with Private being second, and the Local Area Connection being third.

Next we are going to set our default network to a private network. This will avoid certain problems during the install.

Open a command prompt and enter the command:

control.exe /name Microsoft.NetworkandSharingCenter

 
This will open the Network and Sharing Center interface. Alternatively you can navigate here by selecting:

Start->Control Panel->Network and Internet->Network and Sharing Center

Look to where you see Network 3 listed and click on the “Public network” listed underneath.

Change the network type to “Work network” and then click Close.

Next we are going to set the IP address for our two nodes in the hosts file. A hosts file is a simple lookup table to resolve IP addresses.

Open a command prompt and edit the file:

%SystemRoot%\system32\drivers\etc\hosts

 
And add the following entries:

127.0.0.1       localhost.localdomain   localhost

# Public on VMnet2
10.10.1.30   rodolfo.hadesnet		rodolfo
10.10.1.40   mimi.hadesnet		mimi

# Virtual on VMnet2
10.10.1.31   rodolfo-vip.hadesnet	rodolfo-vip
10.10.1.41   mimi-vip.hadesnet		mimi-vip

# Private on VMnet3
10.10.2.30   rodolfo-priv.hadesnet	rodolfo-priv
10.10.2.40   mimi-priv.hadesnet		mimi-priv

 

Save the file and then test IP resolution by pinging the MIMI machine (which does not exist yet). You should see Windows trying the address 10.10.1.40 which it got from the hosts file you just edited.

C:\>ping mimi.hadesnet

Pinging mimi.hadesnet [10.10.1.40] with 32 bytes of data:
Control-C
^C
C:\>

 
You may note we did not add the SCAN addresses in the hosts file. SCAN addressess must resolve to more than one address and this is not possible in a hosts file. We will use a DNS server to achieve this is a later step.

Finally we are going to change the machine name and workgroup name.

Open a command prompt and type:

sysdm.cpl

 
This will open the System Properties menu. Alternatively you can select:

Start->Control Panel->System and Settings->System->Change Settings

Click the Change button and enter the machine as RODOLFO. Enter the workgroup name as LABOHEME.

CLick OK and Windows will wait a few moments before reporting Welcome to the LABOHEME workgroup. Click OK and you will be prompted to reboot your VM.

Alright, that is the networking taken care of, this might be a good time to shut down your VM and make a backup.

Article Quick Navigation
Previous Step Main Index Next Step
Advertisements

2 thoughts on “Oracle 11gR2 11.2.0.3 2-node RAC on Windows 2008 on VMware Workstation 9 – Part II

  1. Hi Gruff,

    this doc is very good to a lot of people.
    I have 1 question regarding the Vmnet2 which is used as the Public IP and Virtual IP.
    why is this vmnet2 is not communicated to the outside world?
    vmnet3 is OK with that due to the private IP.

    Thanks a lot
    John

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s