ClusterPack V2.5 Release Note

Comprehensive Install Instructions

On the Management Server:

% /usr/sbin/swinstall -s <source_machine>: /mnt/dvdrom CPACK-MGR

• The ClusterPack DVD will be referenced again in the installation process.

Please leave it in the DVD drive until the "Run manager_config on the

Management Server" step has completed.

Step 10. Run manager_config on the Management Server

Background

This program is the main installation and configuration driver. It should be

executed on the Management Server.

Some of the steps are:

• Install the appropriate license files and start the licensing services.

• Assign DNS domain name and NIS domain name based on inputs provided.

• Select and configure the cluster LAN interface on the Management Server that

interfaces with the Compute Nodes.

• Specify how many Compute Nodes are in the cluster and the starting IP

address of the first Compute Node. This information is used to assign names

and IP addresses when the Compute Nodes are brought up. The first five

characters of the Management Server’s hostname are used for a base for the

Compute Nodes. For example, if the starting IP address is 10.1.1.1, and there

are 16 Compute Nodes, and the name of the Management Server is hpnode,

then the first Compute Node will be called hpnod001 with the address 10.1.1.1.

The next Compute Node will be called hpnod002 with the address 10.1.1.2, and

so on. (Compute Node names are limited to eight characters.) If the tool is

invoked with the -f option, the input file will be the source for this information.

• Set up the Management Server as NTP server, NIS server, NFS server,

Ignite-UX server, and Web server.

• Install all of the dependent software components from the ClusterPack DVD:

— This step looks for the source of the CPACK-MGR install and queries for an

alternate source, if the source is not found. A local depot is setup. All of the

agent components are copied. Other dependent software pieces in the

Management Server are validated and installed.

• Modify configuration files on the Management Server to enable auto-startup of

the Cluster Management Software components after reboots.