Symantec logo
Configuring private IP addresses for CRS

The CRS daemon requires a private IP address on each node to enable communications and heartbeating.

Determine a private NIC device for which LLT is configured. Look at the file /etc/llttab. For example, if lan0 is used as an LLT interconnect on one system, you can configure an available IP address for it. The private IP addresses of all nodes should be on the same physical network in the same IP subnet.

 To configure private IP addresses for CRS

  1. Select Configure private IP addresses for CRS if you want to specifically perform this task.
  2. Enter the private IP address for the system and interface for each host.

    Enter the private IP for galaxy: [b] 192.168.12.1

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

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

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

    Enter the private IP for nebula: [b] 196.168.12.2

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

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

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

  3. Enter the netmask for the cluster.

    Enter the netmask for private network: [b] 255.255.240.0

  4. Review and confirm the private IP address information for CRS.

    CRS private IP configuration information verification

    System Name: galaxy

    CRS IP address: 192.168.12.1

    Interfaces: lan1 lan2

    System Name: nebula

    CRS IP address: 192.168.12.2

    Interfaces: lan1 lan2

    Netmask: 255.255.240.0

    Is this information correct? [y,n,q,b] (y)

    After confirming the values, the utility adds a new section in the VCS configuration file (main.cf) for the PrivNIC resource in the CVM group. Here is a sample segment of an updated PrivNIC information in the main.cf:

    .

    .

    group cvm (

    SystemList = { galaxy = 0, nebula = 1 }

    AutoFailOver = 0

    Parallel = 1

    AutoStartList = { galaxy, nebula }

    )

    .

    .

    PrivNIC ora_priv (

    Critical = 0

    Device = { lan1 = 0, lan2 = 1}

    Address@galaxy = "192.168.12.1"

    Address@nebula = "192.168.12.2"

    NetMask = "255.255.240.0"

    )

    .

    .

    See About PrivNIC agent

  5. On each system, add the configured private IP addresses of all nodes to the /etc/hosts file, mapping them to symbolic names such as galaxy-priv.
  6. From each system, try pinging each of the other nodes, using the symbolic system name associated with the private NIC IP address.