13.1 Preinstallation Tasks

Note: Before attempting the following installation operations, back up all of the affected systems.

The tasks you must perform before installing the PSE software include the following:

Prepare for the PSE installation by checking the software distribution kit, reading the online release notes, login privileges, software requirements, and disk space requirements Section 13.1.1.
Identify the nodes you want to become PSE cluster members. PSE cluster members must meet the requirements listed in Section 13.1.2. If all nodes are not within the same IP subnet, you must customize your cluster (see Section 13.7 and Chapter 16).
Assemble the Cluster members' hardware, operating system, and network components as described in Chapter 11.
Set up the single system image required by the PSE software as described in Chapter 12.
Basic PSE cluster installation assigns IP port 57039 to the psefarm service. Make sure this port number and service name do not exist in the NIS services map, or in the /etc/services file on any of the nodes on which you want to install PSE. If IP service port 57039 is already being assigned to another service, and it is not possible to reassign this port number to the psefarm service, then follow the customization procedure to modify the psefarm service port (see Section 13.6).

13.1.1 Checking Installation Requirements

This section describes the documentation (online and hardcopy) that is available prior to installation. Licensing procedures, and activities such as checking system space and backing up your system are also discussed.

13.1.1.1 Checking the Software Distribution Kit

Use the bill of materials (BOM) to check the contents of your PSE software distribution kit.

In addition to this guide, the software distribution kit includes the following:

A CD-ROM optical disk for systems with optical disk drives
A CD-ROM booklet and CD-ROM cover letter

If your software distribution kit is damaged or incomplete, contact your Digital representative.

13.1.1.2 Reading the Online Cover Letter

The online cover letter often contains important information that may not be included in this guide or in the release notes. Read this letter before proceeding further. To read the online letter prior to the installation, use the following steps:

Physically mount the media on the appropriate disk drive.
Log in as superuser (root) to the system where you are installing the software.
Enter the following command to ensure that you are at the root directory:
```
# cd /
```
Specify the /mnt directory to be the mount point for the distribution file system on the drive. In the following example, substitute the correct device unit number for x :
```
# mount -rd /dev/rzxc /mnt
```

Use the more command to display the file:

# more /mnt/pse120/documentation/pse120_cover.txt

13.1.1.3 Reading the Online Release Notes

The PSE software provides both online and hardcopy versions of the release notes. Digital strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the software.

The release notes are included both in the installation media and in the PSE kit. From the installation media, you can read the release notes using the following procedure:

Physically mount the media on the appropriate disk drive.
Login as superuser (login name root) to the system where you are installing the software.
Enter the following command to ensure that you are in the root directory:
```
# cd /
```
Specify the /mnt directory to be the mount point for the distribution file system on the drive. In the following example, substitute the correct device unit number for x:
```
# mount -rd /dev/rzxc /mnt
```

Use the more command to display the file:

# more /mnt/pse120/documentation/pse120_relnotes.txt

After the installation, the release notes for the PSE software are in the following files:

/usr/opt/PSE120 /docs/pse120_ relnotes.txt - ASCII text version
/usr/opt/PSE120 /docs/pse120_ relnotes.ps - PostScript version

You can use the following command to read the release notes after the PSE software is installed:

# more /usr/opt/PSE120/docs/pse120_relnotes.txt

The PostScript version of the release notes can be printed on a PostScript printer or viewed using a PostScript previewer such as dxvdoc .

In addition to the cover letter and release notes, the distribution media includes the following documentation:

pse120_spd.txt and pse120_spd.ps - Software Product Description
pse120_iguide.txt and pse120_iguide.ps - Installation Guide

13.1.1.4 Checking Installation Procedure Requirements

This section discusses various requirements for installing the PSE software.

PSE installation takes approximately 30 to 60 minutes, depending on your type of media and the complexity of the system configuration.

13.1.1.4.1 Login Privileges

In order to install the PSE software, you need to become a superuser (root) on all PSE cluster members. Furthermore, if you want to run the pse-remote-install facility, you need to allow root from the source node to have remote access to root on all other hosts that will be PSE cluster members. This is achieved by adding the source node name to the /.rhosts file on all of these hosts. After the remote install is done, the root remote access is no longer required.

13.1.1.4.2 Checking Software Requirements

See the cover letter (included on the CD-ROM) or the online release notes to determine the minimum version of the operating system required.

The PSE software also requires the subsets of the Digital UNIX software shown in Table 13-1 to be loaded on the system:

Table 13-1 PSE Subset Requirements

PSE Subset Title	Requirement
PSE High Performance Fortran Support (PSEHPF120)	OSFCLINET, OSFRTDEV
PSE Parallel Programming Environment (PSEPPE120)	OSFCLINET, OSFRTDEV
PSE System Software (PSEWSF120)	OSFCLINET, OSFRTDEV, PSEHPF120
PSE Manual Pages (PSEMAN120)	OSFDCMT*
PSE Network Kernel Binaries (PSEKBIN300120)	OSFBIN300
PSE Network Kernel Binaries (PSEKBIN320120)	OSFBIN320
PSE Network Kernel Binaries (PSEKBIN350120)	OSFBIN350

To check the subsets that are loaded, follow these steps:

Log in to the system where you will install the PSE software.
Enter the following command (Replace " . . . " with additional required subsets you want to check):
```
# /usr/sbin/setld -i | egrep 'OSFCLINET*| . . . '
```

Check the displayed rows for the name of the relevant subset. The word installed appears in a row after the subset identifier when a subset is loaded. If the word "installed" does not appear (the second column in a row is blank), the subset is not loaded. In this case, you must load the missing Digital UNIX software before installing the PSE software. For information about loading the operating system software, see the Digital UNIX (DEC OSF/1) installation guide.

13.1.1.4.3 Determining Which Subsets to Load

You must choose the PSE subsets you want to load. The following two subsets are required for all PSE cluster members:

High Performance Fortran Support (PSEHPF120) - Run-time libraries for parallel HPF applications and the PSE system software utilities.
PSE System Software (PSEWSF120 - Cluster environment software which includes the farmd daemon and PSE utilities. This subset requires the PSEHPF120 subset.

The following subsets are optional, providing additional functionality to each PSE cluster member:

Parallel Programming Environment (PSEPPE120) - Parallel debugger, profiler, and profiling library
Parallel Software Environment Manual Pages (PSEMAN120 - Reference pages (manpages) for the PSE software
Networking Kernel Binaries (PSEKBIN300120, PSEKBIN320120, PSEKBIN350120) [Optional]-Kernel object files to support UDP_prime, an optimized implementation of UDP /IP for parallel HPF applications. This subset requires the presence of the Digital DEFTA, DEFEA, or DEFPA FDDI adapter. If this subset is installed, HPF applications transparently use UDP_ prime. Otherwise, the standard UDP/IP provided by the standard kernel is used. Although HPF applications run transparently in a mixed UDP/IP and UDP_prime environment, optimal performance is obtained when all PSE cluster members run UDP_prime. There are three versions of the Networking Kernel Binaries subset to support Digital UNIX V3.0, V3.2, and V3.2C. The setld installation procedure will automatically choose the appropriate subset to install. Digital UNIX V3.2D and V3.2E can safely use the PSEKBIN350120 subset.

13.1.1.4.4 Determining Disk Space Requirements

Table 13-2 lists the disk space requirements for loading the PSE software subsets. These requirements apply to the disks where you load the PSE subsets.

Table 13-2 PSE Subset Sizes (Kilobytes Required)

Subset Title	Subset Name	/usr	/var	/root
PSE High Performance Fortran Support	PSEHPF120	6,250
PSE Parallel Programming Environment	PSEPPE120	18,000
PSE System Software	PSEWSF120	1,400	50
PSE Manual Pages	PSEMAN120	2,600
PSE Network Kernel Binaries	PSEKBIN300120	800

Totals:		29,050	50	0

During the actual installation, the PSE software requires approximately 60 MB of free disk space on the /usr partition and 5-10 MB of free space in the /tmp directory. After the installation, the PSE software uses approximately 30 MB of /usr and /var partitions.

Using these disk space requirements, total the values for the subsets you are loading in each directory. Compare the space required for these subsets with the free space currently on the disks where the PSE software files will reside.

13.1.1.4.5 Listing the Files Installed by PSE

You can list the files created by the PSE software installation by looking at /mnt/pse120/kit/instctrl/PSE*120.inv .

For More Information:

See Appendix C.

13.1.1.4.6 Checking Current Disk Space

To check the current amount of free space for a directory path, log in to the system where you will install the PSE software. You can check which directories are mounted and where they are by viewing the /etc/fstab file. Use the command:

# more /etc/fstab

To check the total space and the free space for the directories where the PSE software will reside, enter the df command, as follows:

# df -k

This free space displayed by this command must accommodate the subset requirements listed in Table 13-2.

13.1.2 PSE Cluster Member Requirements

Any PSE cluster member should meet the following requirements:

All PSE cluster members must run Digital UNIX Version 3.0 or higher.
The network interface whose IP address is assigned to the member's hostname must be connected to the same network segment as all other PSE cluster members. If the members have multiple network interfaces, only one interface must satisfy this requirement.
If your cluster does not satisfy this requirement, then you must customize your PSE cluster. Only a customized PSE cluster is permitted to operate across multiple network segments.
The passwd , group , hosts , and services information must be consistent across all PSE cluster members. This can be conveniently done by distributing this information using Network Information Service (NIS) or DNS.
Files used by all PSE cluster applications (including the application image and, possibly, other data files) should be accessible by the same pathname from all PSE cluster members. Digital recommends setting up an Network File System (NFS) environment on all PSE cluster members with common directory mount points for user home directories and other directories that are used by PSE cluster applications. The automount daemon provides a convenient mechanism to manage these NFS mount points.
All PSE cluster users should have rsh access without password to any PSE cluster members they plan to use. This can be achieved by specifying the PSE cluster members' hostnames in the .rhosts file in your home directory.

For More Information:

On customizing your PSE cluster, see Section 13.7 and Chapter 16).

13.1.3 Additional Preinstallation Requirements for Customized PSE Clusters

If you will be customizing your PSE cluster, you must meet some additional requirements. Customized PSE clusters can be either file- based or DNS-based.

Section 13.1.3.1 lists the requirements for a file-based PSE cluster.
Section 13.1.3.2 lists the requirements for a DNS-based PSE cluster.

For More Information:

On file-based and DNS-based PSE clusters, see Section 16.1.
On customizing your PSE cluster, see Section 13.7 and Chapter 16.

13.1.3.1 Preinstallation for File-based PSE Clusters

If you wish to set up a file-based PSE cluster, you must choose a directory accessible to all members for the database file. This is most conveniently done by placing the database file in an NFS file system. File-based PSE cluster members do not have to be connected to the same network segment.

13.1.3.2 Preinstallation for DNS-based PSE Clusters

The requirements in this section apply if you wish to set up a DNS- based PSE cluster.

The PSE cluster configuration uses three DNS domains, as follows:

Host domain - Contains the PSE cluster members' hostname and Internet address mapping. On Digital UNIX DNS primary servers, this domain is stored in the /etc/namedb/hosts.db file.
in-addr.arpa domain - Contains the PSE cluster members' Internet address-to-hostname mapping. On Digital UNIX DNS primary servers, this domain is stored in the /etc/namedb/hosts.rev file.
PSE cluster domain - Contains information about the PSE cluster configuration. The PSE cluster domain is a subdomain of the host domain. For example, if the host domain is univ.edu and the PSE cluster name created by the PSE cluster is mycluster , the PSE cluster domain is mycluster.univ.edu .
Note
On Digital UNIX DNS primary servers, the host domain and the in-addr.arpa domain are automatically created by bindsetup from information in the primary server's /etc/hosts file. The PSE cluster domain is created when you customize the PSE cluster with the psedbedit utility. PSE cluster members' hostnames and Internet addresses continue to be part of the hosts and in-addr.arpa domains. The PSE cluster domain only maintains the PSE cluster configuration information.

To create the PSE cluster domain, you must perform the following procedures:

Choose a name for your PSE cluster; for example mycluster .
Designate one member to become the PSE cluster DNS server. The designated system must meet the PSE cluster member requirements.
If the PSE cluster DNS server is not configured to run DNS, or if it is already configured as a DNS client, use bindsetup to set it up as a caching server.
On all other PSE cluster members, use bindsetup to modify the BIND client configuration. Specify the PSE cluster DNS server host name/Internet address as the first name server listed in the /etc/resolv.conf file. Additional name servers, such as the host domain primary or secondary servers, can be specified after the PSE cluster DNS server.