Sun Cluster 3.1 10/03 Software Installation Guide

Console-Access Devices

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 Fire™ 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.

Logical Addresses

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.

Sun Cluster Configurable Components

This section provides guidelines for the following Sun Cluster components that you configure during installation:

Cluster Name

Add this planning information to the Cluster and Node Names Worksheet.

Specify a name for the cluster during Sun Cluster installation. The cluster name should be unique throughout the enterprise.

Node Names

Add this planning information to the Cluster and Node Names Worksheet. Information for most other worksheets is grouped by node name.

The node name is the name that you assign to a machine when you install the Solaris operating environment. During Sun Cluster installation, you specify the names of all nodes that you are installing as a cluster. In single-node cluster installations, the default node name is the same as the cluster name.

Private Network

Add this planning information to the Cluster and Node Names Worksheet.

Note - You do not need to configure a private network for a single-node cluster.

Sun Cluster software uses the private network for internal communication between nodes. A Sun Cluster configuration requires at least two connections to the cluster interconnect on the private network. You specify the private network address and netmask when you install Sun Cluster software on the first node of the cluster. You can either accept the default private network address (172.16.0.0) and netmask (255.255.0.0) or type different choices if the default network address is already in use elsewhere in the enterprise.

Note - After you have successfully installed the node as a cluster member, you cannot change the private network address and netmask.

If you specify a private network address other than the default, the address must meet the following requirements:

Use zeroes for the last two octets of the address.
Follow the guidelines in RFC 1597 for network address assignments.

You can contact the InterNIC to obtain copies of RFCs. See "Planning Your TCP/IP Network" in System Administration Guide, Volume 3 (Solaris 8) or "Planning Your TCP/IP Network (Task)" in System Administration Guide: IP Services (Solaris 9) for instructions.

If you specify a netmask other than the default, the netmask must minimally mask all bits that are given in the private network address.

Private Hostnames

Add this planning information to the Cluster and Node Names Worksheet.

The private hostname is the name that is used for internode communication over the private-network interface. Private hostnames are automatically created during Sun Cluster installation. These private hostnames follow the naming convention clusternodenodeid-priv, where nodeid is the numeral of the internal node ID. During Sun Cluster installation, the node ID number is automatically assigned to each node when the node becomes a cluster member. After installation, you can rename private hostnames by using the scsetup(1M) utility.

Cluster Interconnect

Add this planning information to the Cluster Interconnect Worksheet.

Note - You do not need to configure a cluster interconnect for a single-node cluster. However, if you anticipate eventually adding nodes to a single-node cluster configuration, you might want to configure the cluster interconnect for future use.

The cluster interconnects provide the hardware pathways for private network communication between cluster nodes. Each interconnect consists of a cable that is connected in one of the following ways:

Between two transport adapters
Between a transport adapter and a transport junction
Between two transport junctions

During Sun Cluster installation, you specify the following configuration information for two cluster interconnects:

Transport adapters - For the transport adapters, such as ports on network interfaces, specify the transport adapter names and transport type. If your configuration is a two-node cluster, you also specify whether your interconnect is direct connected (adapter to adapter) or uses a transport junction. If your two-node cluster is direct connected, you can still specify a transport junction for the interconnect.

Tip - If you specify a transport junction, you can more easily add another node to the cluster in the future.

See the scconf_trans_adap_*(1M) family of man pages for information about a specific transport adapter.
Transport junctions - If you use transport junctions, such as a network switch, specify a transport junction name for each interconnect. You can use the default name switchN, where N is a number that is automatically assigned during installation, or create another name.

Also specify the junction port name or accept the default name. The default port name is the same as the internal node ID number of the node that hosts the adapter end of the cable. However, you cannot use the default port name for certain adapter types, such as SCI-PCI.


1. Planning the Sun Cluster Configuration Planning the Sun Cluster Environment IP Addresses


	Console-Access Devices 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 Fire™ 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. Logical Addresses 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. Sun Cluster Configurable Components This section provides guidelines for the following Sun Cluster components that you configure during installation: Cluster Name Node Names Private Network Private Hostnames Cluster Interconnect Public Networks Disk Device Groups IP Network Multipathing Groups Quorum Devices Cluster Name Add this planning information to the Cluster and Node Names Worksheet. Specify a name for the cluster during Sun Cluster installation. The cluster name should be unique throughout the enterprise. Node Names Add this planning information to the Cluster and Node Names Worksheet. Information for most other worksheets is grouped by node name. The node name is the name that you assign to a machine when you install the Solaris operating environment. During Sun Cluster installation, you specify the names of all nodes that you are installing as a cluster. In single-node cluster installations, the default node name is the same as the cluster name. Private Network Add this planning information to the Cluster and Node Names Worksheet. Note - You do not need to configure a private network for a single-node cluster. Sun Cluster software uses the private network for internal communication between nodes. A Sun Cluster configuration requires at least two connections to the cluster interconnect on the private network. You specify the private network address and netmask when you install Sun Cluster software on the first node of the cluster. You can either accept the default private network address (`172.16.0.0`) and netmask (`255.255.0.0`) or type different choices if the default network address is already in use elsewhere in the enterprise. Note - After you have successfully installed the node as a cluster member, you cannot change the private network address and netmask. If you specify a private network address other than the default, the address must meet the following requirements: Use zeroes for the last two octets of the address. Follow the guidelines in RFC 1597 for network address assignments. You can contact the InterNIC to obtain copies of RFCs. See "Planning Your TCP/IP Network" in System Administration Guide, Volume 3 (Solaris 8) or "Planning Your TCP/IP Network (Task)" in System Administration Guide: IP Services (Solaris 9) for instructions. If you specify a netmask other than the default, the netmask must minimally mask all bits that are given in the private network address. Private Hostnames Add this planning information to the Cluster and Node Names Worksheet. The private hostname is the name that is used for internode communication over the private-network interface. Private hostnames are automatically created during Sun Cluster installation. These private hostnames follow the naming convention `clusternodenodeid-priv`, where nodeid is the numeral of the internal node ID. During Sun Cluster installation, the node ID number is automatically assigned to each node when the node becomes a cluster member. After installation, you can rename private hostnames by using the `scsetup`(1M) utility. Cluster Interconnect Add this planning information to the Cluster Interconnect Worksheet. Note - You do not need to configure a cluster interconnect for a single-node cluster. However, if you anticipate eventually adding nodes to a single-node cluster configuration, you might want to configure the cluster interconnect for future use. The cluster interconnects provide the hardware pathways for private network communication between cluster nodes. Each interconnect consists of a cable that is connected in one of the following ways: Between two transport adapters Between a transport adapter and a transport junction Between two transport junctions During Sun Cluster installation, you specify the following configuration information for two cluster interconnects: Transport adapters - For the transport adapters, such as ports on network interfaces, specify the transport adapter names and transport type. If your configuration is a two-node cluster, you also specify whether your interconnect is direct connected (adapter to adapter) or uses a transport junction. If your two-node cluster is direct connected, you can still specify a transport junction for the interconnect. Tip - If you specify a transport junction, you can more easily add another node to the cluster in the future. See the `scconf_trans_adap_`(1M) family of man pages for information about a specific transport adapter. Transport junctions -* If you use transport junctions, such as a network switch, specify a transport junction name for each interconnect. You can use the default name `switchN`, where N is a number that is automatically assigned during installation, or create another name. Also specify the junction port name or accept the default name. The default port name is the same as the internal node ID number of the node that hosts the adapter end of the cable. However, you cannot use the default port name for certain adapter types, such as SCI-PCI.