1. Installing and Configuring an Oracle Solaris Cluster 4.4 Environment
  2. Planning the Oracle Solaris Cluster Configuration
  3. Planning the Oracle Solaris Cluster Environment
  4. Public-Network IP Addresses

Public-Network IP Addresses

For information about the use of public networks by the cluster, see Public Network Adapters in Concepts for Oracle Solaris Cluster 4.4.

You must set up a number of public-network IP addresses for various Oracle Solaris Cluster components. The number of addresses that you need depends on which components you include in your cluster configuration. Each Oracle Solaris host in the cluster configuration must have at least one public-network connection to the same set of public subnets.

The following table lists the components that need public-network IP addresses assigned. Add these IP addresses to the following locations:

  • Any naming services that are used

  • The local /etc/inet/hosts file on each global-cluster node, after you install Oracle Solaris software

  • The local /etc/inet/hosts file on any exclusive-IP non-global zone

Table 1-2 Oracle Solaris Cluster Components That Use Public-Network IP Addresses

Component Number of IP Addresses Needed

Administrative console

1 IP address per subnet

Global-cluster nodes

1 IP address per node, per subnet

Zone-cluster nodes

1 IP address per node, per subnet

Domain console network interface

1 IP address per domain

(Optional) Non-global zones

1 IP address per subnet

Console-access device

1 IP address

Logical addresses

1 IP address per logical host resource, per subnet

Disaster Recovery Framework

1 IP address per global cluster/zone cluster, where the framework runs

For more information about planning IP addresses, see Planning for Network Deployment in Oracle Solaris 11.4.