< Previous  | TOC | Index | Next  >

Configuring private IP addresses for CRS

The CRS daemon requires a private IP address on each node to enable communications and heartbeating. After confirming the values, the installer adds a new section in the VCS configuration file (main.cf) for the PrivNIC resource in the CVM group.

 To add private IP addresses to /etc/hosts

1. Log in to each system as root
2. Add the following entries to the /etc/hosts file:

192.168.12.1 galaxy_priv

192.168.12.2 nebula_priv

 To configure private IP addresses for CRS

1. Access the SF Oracle RAC configuration program if you are not currently using it.

   See Using the SF Oracle RAC configuration program

2. Select Configure private IP addresses for CRS from the configuration menu.
3. Enter the private IP address information for each host.

   Enter the private IP for galaxy: [b] 192.168.12.1

   Checking 192.168.12.1 in /etc/hosts on galaxy..... exists

   Discovering NICs on galaxy ..... discovered qfe0 qfe1 qfe2

   Enter the NIC 1 for private network for galaxy (x if done): [b] qfe0

   Enter the NIC 2 for private network for galaxy (x if done): [b] qfe1

   Enter the NIC 3 for private network for galaxy (x if done): [b] x

   Enter the private IP for nebula: [b] 192.168.12.2

   Checking 192.168.12.2 in /etc/hosts on nebul ..... exists

   Discovering NICs on nebula ..... discovered qfe0 qfe1 qfe2

   Enter the NIC 1 for private network for nebula (x if done): [b] qfe0

   Enter the NIC 2 for private network for nebula (x if done): [b] qfe1

   Enter the NIC 3 for private network for nebula (x if done): [b] x

   Enter the netmask for private network: [b] 255.255.240.0

   ---

     Note   The private IP addresses of all nodes should be on the same physical network in the same IP subnet.

   ---

4. Confirm the private IP address information.
5. After the private IP address is configured, you can exit the installer by entering q or continue with your configuration.

 To verify the private NIC address configuration

1. Verify that the PrivNIC resource, ora_priv, shows up in VCS main.cf:

   PrivNIC ora_priv (

   Critical = 0

   Device @galaxy = { qfe0 = 0, qfe1 = 1 }

   Device @nebula = { qfe0 = 0, qfe1 = 1 }

   Address @galaxy = "192.168.12.1"

   Address @nebula = 2192.168.12.1"

   NetMask = "255.255.240.0"

   )

2. Verify that the "ora_priv" resource is online on all systems in the cluster:

   # hares -state ora_priv

   #Resource Attribute System Value

   ora_priv State galaxy ONLINE

   ora_priv State nebula ONLINE

3. On each system, check the output of "ifconfig"

   # ifconfig -a

4. From each system, ping the private IP addresses:

   # ping 192.168.12.2

   PING 192.168.12.2 (192.168.12.2): 56 data bytes

   64 bytes from 192.168.12.2: icmp_seq=0 ttl=255 time=0 ms

   64 bytes from 192.168.12.2: icmp_seq=1 ttl=255 time=0 ms

   # ping 192.168.12.1

   PING 192.168.12.1 (192.168.12.1): 56 data bytes

   64 bytes from 192.168.12.1: icmp_seq=0 ttl=255 time=0 ms

   64 bytes from 192.168.12.1: icmp_seq=1 ttl=255 time=0 ms