You must set up a number of IP addresses for various Sun Cluster components, depending on your cluster configuration. Each node 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 IP addresses assigned. Add these IP addresses to any naming services that are used. Also add these IP addresses to the local /etc/inet/hosts file on each cluster node after you install Solaris software.
For more information about IP addresses, see System Administration Guide, Volume 3 (Solaris 8) or System Administration Guide: IP Services (Solaris 9).
For more information about test IP addresses to support IP Network Multipathing, see IP Network Multipathing Administration Guide.
Component |
Number of IP Addresses Needed |
---|---|
1 per subnet |
|
|
|
Cluster nodes |
1 per node, per subnet |
1 per domain |
|
1 |
|
Logical addresses |
1 per logical host resource, per subnet |
You must have console access to all cluster nodes. If you install Cluster Control Panel software on your administrative console, you must provide the hostname of the console-access device that is used to communicate with the cluster nodes.
A terminal concentrator is used to communicate between the administrative console and the cluster node consoles.
A Sun Enterprise 10000 server uses a System Service Processor (SSP) instead of a terminal concentrator.
A Sun FireTM server uses a system controller instead of a terminal concentrator.
For more information about console access, see the Sun Cluster 3.1 10/03 Concepts Guide.
Each data-service resource group that uses a logical address must have a hostname specified for each public network from which the logical address can be accessed.
For more information, see the Sun Cluster 3.1 Data Service Planning and Administration Guide.
For additional information about data services and resources, also see the Sun Cluster 3.1 10/03 Concepts Guide.