DIGITAL Digital_Parallel_Software_Environment_______________ Installation Guide: PVM and MPI January 1999 This document describes the installation procedures for the DIGITAL Parallel Software Environment (PSE) software. It also describes the installation procedures for DIGITAL PVM (Parallel Virtual Machine) and DIGITAL MPI (Message Passing Interface) software. Revision/Update Information: January 1999 Operating System Versions: PVM: Digital UNIX V4.0a and higher MPI: Digital UNIX V4.0a and higher Software Versions: DIGITAL Parallel Software Environment Version 1.8 DIGITAL PVM Version 1.8 DIGITAL MPI Version 1.8 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ Revision January 1999 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1999. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: AdvantageCluster, Alpha AXP, AXP, Bookreader, DEC, DEC Fortran, DECconnector, DECmcc, DECnet, DECserver, DECstation, DECsystem, DECsupport, DECwindows, DELNI, DEMPR, Digital, GIGAswitch, POLYCENTER, ThinWire, TK, TURBOchannel, TruCluster, ULTRIX, VAX, VAX DOCUMENT, VAX FORTRAN, VMS, and the DIGITAL logo. Network File System and NFS are registered trademarks of Sun Microsystems, Inc. Motif is a registered trademark of Open Software Foundation, Inc., licensed by Digital; Open Software Foundation, OSF and OSF/1 are registered trademarks of Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. X Window System is a trademark of Massachusetts Institute of Technology. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents About This Manual......................................... vii 1 Introduction 2 PVM Installation (PVM only) 2.1 Preinstallation Tasks......................... 2-1 2.1.1 Checking Installation Requirements........ 2-1 2.1.1.1 Checking the Software Distribution Kit..................................... 2-2 2.1.1.2 Reading the Online Cover Letter......... 2-2 2.1.1.3 Reading the Online Release Notes........ 2-3 2.1.1.4 Checking Installation Procedure Requirements............................ 2-4 2.1.1.4.1 Login Privileges....................... 2-4 2.1.1.4.2 Checking Software Requirements......... 2-4 2.1.1.4.3 Determining Which Subsets to Load...... 2-5 2.1.1.4.4 Determining Disk Space Requirements.... 2-5 2.1.1.4.5 Listing the Files Installed by PVM..... 2-6 2.1.1.4.6 Checking Current Disk Space............ 2-6 2.1.2 PVM Cluster Member Requirements........... 2-6 2.2 Loading the PVM Software...................... 2-7 2.2.1 Deleting Existing PVM Software Subsets.... 2-7 2.2.1.1 PVM Installation Summary................ 2-7 2.2.2 Running the Installation Verification Procedure................................. 2-8 iii 3 MPI Installation (MPI only) 3.1 Preinstallation Tasks......................... 3-1 3.1.1 Checking Installation Requirements........ 3-1 3.1.1.1 Checking the Software Distribution Kit..................................... 3-2 3.1.1.2 Reading the Online Cover Letter......... 3-2 3.1.1.3 Reading the Online Release Notes........ 3-3 3.1.1.4 Checking Installation Procedure Requirements............................ 3-4 3.1.1.4.1 Login Privileges....................... 3-4 3.1.1.4.2 Checking Software Requirements......... 3-4 3.1.1.4.3 Determining Which Subsets to Load...... 3-5 3.1.1.4.4 Determining Disk Space Requirements.... 3-5 3.1.1.4.5 Listing the Files Installed by MPI..... 3-5 3.1.1.4.6 Checking Current Disk Space............ 3-6 3.1.2 MPI Cluster Member Requirements........... 3-6 3.2 Loading the MPI Software...................... 3-7 3.2.1 Deleting Existing MPI Software Subsets.... 3-7 3.2.1.1 MPI Installation Summary................ 3-7 3.2.2 Running the Installation Verification Procedure................................. 3-8 4 Installation Using setld 4.1 Using CD-ROM Consolidated Distribution Media......................................... 4-1 4.2 Using a RIS Distribution Area................. 4-2 4.3 Responding to Installation Procedure Prompts....................................... 4-3 4.3.1 Selecting Subsets......................... 4-3 4.3.2 Monitoring Displays During the Subset Loading Process........................... 4-4 4.4 Failures During Product Installation.......... 4-6 Index iv Examples 2-1 Sample PVM IVP Log........................ 2-9 3-1 Sample MPI IVP Log........................ 3-9 4-1 PSE Subsets Loaded from CD-ROM Media...... 4-5 Tables 2-1 PVM Subset Requirements................... 2-4 2-2 PVM Subset Sizes (Kilobytes Required)..... 2-5 3-1 MPI Subset Requirements................... 3-4 3-2 MPI Subset Sizes (Kilobytes Required)..... 3-5 v _________________________________________________________________ About This Manual This document describes how to install the DIGITAL Parallel Software Environment (PSE). The PSE kit contains the DIGITAL PVM and DIGITAL MPI software. Intended Audience This document is intended for anyone who must install DIGITAL PVM or DIGITAL MPI software. Related Documents The following DIGITAL documents provide more information about DIGITAL Parallel Software Environment administration and use: o DIGITAL PVM User Guide - Describes the DIGITAL PVM facility o DIGITAL MPI User Guide - Describes the DIGITAL MPI facility Conventions The following conventions are used in this manual. ___________________________________________________________ Convention_______Meaning___________________________________ % A percent sign represents the DIGITAL UNIX $ system prompt. A dollar sign represents the system prompt for OpenVMS VAX systems. % cat Boldface type in interactive examples indicates typed user input. vii ___________________________________________________________ Convention_______Meaning___________________________________ # A number sign represents the DIGITAL UNIX superuser prompt. file Italic (slanted) type indicates variable values, placeholders, and function argument names for DIGITAL UNIX commands and functions. OSF/1, DEC OSF All of these terms refer to the same /1, Digital operating system. UNIX cat DIGITAL UNIX command names are shown TYPE in a constant-width typeface. OpenVMS VAX commands are shown in all uppercase characters. cat(1) A cross-reference to a reference page includes the appropriate section number in parenthesis. For example, cat(1) indicates that you can find information on the cat command in Section 1 of the reference pages. Ctrl/x This symbol indicates that you press the X key while holding down the Ctrl key. ... In examples, a horizontal series of dots, or ellipsis, indicates that additional parameters, values, or other information can be entered. . In examples, a vertical series of dots, . or vertical ellipsis, indicates that a . portion of the actual code that would normally be present is omitted. [ ] In syntax descriptions and function definitions, brackets indicate that items are optional. In examples, a key name shown within a box indicates that you press a key on the keyboard. In text, a key name is not enclosed in a box but printed with an initial capital letter, like Return. viii ___________________________________________________________ Convention_______Meaning___________________________________ n A lowercase italic n indicates the generic use of a number. italicized text In examples, italicized text is used to denote parameters, values, or other information that changes either from session to session or user to user. In text, italicized words or phrases are used to add emphasis to important words, concepts, or titles of manuals. code examples This typeface is used to display program _________________coding_examples.__________________________ ix Sending DIGITAL Your Comments on This Manual DIGITAL welcomes your comments on this manual. You can send comments in the following ways: o Internet electronic mail: pse@hpc.pko.dec.com o Internet electronic mail: pvm@ilo.dec.com o Internet electronic mail: mpi@ilo.dec.com o FAX: 978-493-3628 ATTN: PSE Team o A Reader's Comment Card sent to the address on the form o A letter sent to the following address: Digital Equipment Corporation High Performance Computing Group 129 Parker Street PKO3-2/B12 Maynard, MA 01754-2195 o Online questionnaire form - Print or edit the questionnaire form provided near the end of the online release notes; send the form by Internet mail, FAX, or the postal service Getting Help from DIGITAL If you have a customer support contract and have comments or questions about DIGITAL Fortran software, you contact DIGITAL's Customer Support Center (CSC), preferably using electronic means such as DSNlink. In the United States, customers can call the CSC at 1-800-354-9000. x 1 _________________________________________________________________ Introduction This installation guide is for installing DIGITAL PVM and DIGITAL MPI software. These two facilities (PVM and MPI) are not integrated, and should be considered as two completely separate entities. Many installations will be interested in only one of the two. Some chapters are for only one of the facilities, and others are for both, as listed below: o This Introduction (PVM and MPI) o Chapter 2, PVM Installation (PVM only) o Chapter 3, MPI Installation (MPI only) o Chapter 4, Installation Using setld (PVM and MPI) Introduction 1-1 2 _________________________________________________________________ PVM Installation (PVM only) This chapter describes the installation of DIGITAL PVM. The following tasks are described: o Preinstallation tasks o Loading the software o Verifying the configuration For More Information: o On using PVM, see the DIGITAL PVM User Guide. 2.1 Preinstallation Tasks ________________________ Note ________________________ Before attempting the following installation operations, back up all of the affected systems. ______________________________________________________ Prepare for the PVM installation by checking the software distribution kit. Read the online release notes, and check login privileges, software requirements, and disk space requirements. 2.1.1 Checking Installation Requirements This section describes the documentation (online and hardcopy) that is available prior to installation. Activities such as checking system space and backing up your system are also discussed. PVM Installation (PVM only) 2-1 2.1.1.1 Checking the Software Distribution Kit Use the bill of materials (BOM) to check the contents of your software distribution kit. In addition to this guide, the software distribution kit includes the following: o A CD-ROM optical disk for systems with optical disk drives o A CD-ROM booklet and CD-ROM cover letter If your software distribution kit is damaged or incomplete, contact your DIGITAL representative. 2.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: 1. Physically mount the media on the appropriate disk drive. 2. Log in as superuser (root) to the system where you are installing the software. 3. Enter the following command to ensure that you are at the root directory: # cd / 4. 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 5. Use the more command to display the file: # more /mnt/pse180/documentation/pse180_cover.txt 2-2 PVM Installation (PVM only) 2.1.1.3 Reading the Online Release Notes Online release notes are provided. 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: o Physically mount the media on the appropriate disk drive. o Login as superuser (login name root) to the system where you are installing the software. o Enter the following command to ensure that you are in the root directory: # cd / o 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 o Use the more command to display the file: # more /mnt/pse180/documentation/pse180_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: o Software Product Description: pse180/documentation/pse180_spd.txt pse180/documentation/pse180_spd.ps o Installation Guide pse180/documentation/pse180_iguide.txt pse180/documentation/pse180_iguide.ps PVM Installation (PVM only) 2-3 2.1.1.4 Checking Installation Procedure Requirements This section discusses various requirements for installing the PVM software. PVM installation takes less than 10 minutes, depending on your type of media and the complexity of the system configuration. 2.1.1.4.1 Login Privileges In order to install the PVM software, you need to become a superuser (root) on all cluster members. 2.1.1.4.2 Checking Software Requirements The software requirements for DIGITAL PVM Version 1.8 are: o DIGITAL UNIX version 4.0a or higher In addition, if MEMORY CHANNEL[TM] support is needed, the following is required: o DIGITAL TruCluster software version 1.5 (requires DIGITAL UNIX V4.0d or higher) or higher (or TruCluster MEMORY CHANNEL[TM] Software Version 1.5 or higher). You may also be able to use an earlier TruCluster version with a special patch (for details, see the Release Notes). The PVM software also requires the subsets of the DIGITAL UNIX software shown in Table 2-1 to be loaded on the system: Table_2-1_PVM_Subset_Requirements________________________________ PVM_Subset_Title________Requirement______________________________ DIGITAL PVM V1.8 Base OSFBIN* (PVMBASE180) TCRCOMMON* (for MEMORY CHANNEL[TM] support) TCRMCA* (for MEMORY CHANNEL[TM] support) DIGITAL PVM V1.8 OSFDCMT* Supplementary Documentation (PVMSUPP180)_____________________________________________________ To check the subsets that are loaded, follow these steps: 2-4 PVM Installation (PVM only) 1. Log in to the system where you will install the PVM software. 2. 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 PVM software. For information about loading the operating system software, see the DIGITAL UNIX (DEC OSF /1) installation guide. 2.1.1.4.3 Determining Which Subsets to Load You must choose the PVM subsets you want to load. The following subset is required: o DIGITAL PVM Base (PVMBASE180) The following subset is optional: o DIGITAL PVM Manual Pages (PVMSUPP180) 2.1.1.4.4 Determining Disk Space Requirements Table 2-2 lists the disk space requirements for loading the PVM software subsets. These requirements apply to the disks where you load the PVM subsets. Table_2-2_PVM_Subset_Sizes_(Kilobytes_Required)____________ Subset_Title_______________Subset_Name___/usr___/var___/root DIGITAL PVM V1.8 Base PVMBASE180 7680 DIGITAL PVM V1.8 PVMSUPP180 1536 Supplementary Documentation Totals:__________________________________9216___0______0___ PVM Installation (PVM only) 2-5 2.1.1.4.5 Listing the Files Installed by PVM You can list the files created by the PVM software installation by looking at: /mnt/pse180/kit/instctrl/PVM*180.inv 2.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 PVM 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 PVM 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 2-2. 2.1.2 PVM Cluster Member Requirements Any PVM cluster member should meet the following requirements: o All PVM cluster members must run DIGITAL UNIX Version 4.0a or higher. o If MEMORY CHANNEL[TM] support is needed, all PVM cluster members must run either TruCluster software version 1.5 (requires DIGITAL UNIX V4.0d or higher), or MEMORY CHANNEL[TM] Software version 1.5. You may also be able to use an earlier TruCluster version with a special patch (for details, see the Release Notes). o The passwd, group, hosts, and services information must be consistent across all PVM cluster members. This can be conveniently done by distributing this information using Network Information Service (NIS) or DNS. o Files used by all PVM cluster applications (including the application image and, possibly, other data files) should be accessible by the same pathname from all PVM cluster members. Digital recommends setting up a Network File System (NFS) environment on all PVM cluster members with common directory mount points for user home 2-6 PVM Installation (PVM only) directories and other directories that are used by PVM cluster applications. The automount daemon provides a convenient mechanism to manage these NFS mount points. o All PVM cluster users should have rsh access without password to any PVM cluster members they plan to use. This can be achieved by specifying the PVM cluster members' hostnames in the .rhosts file in your home directory. 2.2 Loading the PVM Software This section describes how to load the PVM software onto each PVM cluster member. 2.2.1 Deleting Existing PVM Software Subsets Before loading a new version of the PVM software, any previous versions of the software must be deleted. If you are upgrading from a previous version of PVM, Digital recommends you follow the upgrading procedure detailed in the release notes. To delete PVM software, you must be superuser (username root). Make sure there are no PVM applications currently running. The command for deleting PVM software is: # cd / # setld -d PVMBASEnnn PVMSUPPnnn Replace nnn with the PVM version number (e.g. 080 for version 0.8). For More Information: o On upgrading from a previous version of PVM, see the instructions in the release notes. 2.2.1.1 PVM Installation Summary This section contains a brief summary of the PVM software installation procedure. The procedure is explained in detail in Chapter 4. PVM Installation (PVM only) 2-7 To load the PVM software kit onto a host, follow these steps: o For installation from a CD-ROM: 1. Log in as superuser (login name root). 2. Type the following commands (substitute your CD-ROM drive name for rzxxc. # cd / # mount -rd /dev/rzxxc /mnt # setld -l /mnt/pse180/kit 3. Refer to Section 2.1.1.4.3 to select the appropriate subsets. o For installation from an RIS (Remote Installation Service) server: 1. Log in as superuser (login name root). 2. Type the following commands (substitute your RIS server for nodename): # cd / # setld -l nodename: 3. Refer to Section 2.1.1.4.3 to select the appropriate subsets. For More Information: o On using setld to install the PVM software, see Chapter 4. o On setld, see the setld(8) manpage. 2.2.2 Running the Installation Verification Procedure ________________________ Note ________________________ The installation steps detailed in the preceding sections must successfully complete before attempting to execute the IVP for PVM. ______________________________________________________ 2-8 PVM Installation (PVM only) After installing PVM, you can run the (IVP) independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to be sure that users can access PVM. The PVM IVP verifies the installation as shown in Example 2-1. Example 2-1 Sample PVM IVP Log # setld -v PVMBASE180 Digital PVM V1.8 Base (Software Development) (PVMBASE180) Copyright (c) Digital Equipment Corporation, 1995, 1999. All Rights Reserved. Starting the verification of Digital PVM V1.8 Base (PVMBASE180) Compiling a PVM test program ... Done. Linking a test program with the Digital PVM library ... Link succeeded. *** The program however cannot be executed as root. *** To test that the compiled PVM program runs successfully *** (and prints an approximation of 'pi'), *** you may, as a non-privileged user: % dpvm dpvm> quit %/tmp/mb_pi.dpvm -numprocs 4 %dpvm dpvm> halt *** It should print the value of 'pi' to a few dozen places. PVMBASE180 IVP passed. # exit % dpvm Digital V1.0.9 dpvm> quit (continued on next page) PVM Installation (PVM only) 2-9 Example 2-1 (Cont.) Sample PVM IVP Log DPVM daemon still running. > /tmp/mb_pi.dpvm -numprocs 4 3.1415926535897932384626433832795028 > dpvm Digital V1.0.9 dpvm> halt > 2-10 PVM Installation (PVM only) 3 _________________________________________________________________ MPI Installation (MPI only) This chapter describes the installation of an MPI cluster. The following tasks are described in detail: o Preinstallation tasks o Loading the software o Verifying the configuration For More Information: o On using MPI, see the DIGITAL MPI User Guide. 3.1 Preinstallation Tasks ________________________ Note ________________________ Before attempting the following installation operations, back up all of the affected systems. ______________________________________________________ Prepare for the MPI installation by checking the software distribution kit. Read the online release notes, and check login privileges, software requirements, and disk space requirements. For More Information: o See Section 3.1.1 3.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. MPI Installation (MPI only) 3-1 3.1.1.1 Checking the Software Distribution Kit Use the bill of materials (BOM) to check the contents of your MPI software distribution kit. In addition to this guide, the software distribution kit includes the following: o A CD-ROM optical disk for systems with optical disk drives o A CD-ROM booklet and CD-ROM cover letter If your software distribution kit is damaged or incomplete, contact your DIGITAL representative. 3.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: 1. Physically mount the media on the appropriate disk drive. 2. Log in as superuser (root) to the system where you are installing the software. 3. Enter the following command to ensure that you are at the root directory: # cd / 4. 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 5. Use the more command to display the file: # more /mnt/pse180/documentation/pse180_cover.txt 3-2 MPI Installation (MPI only) 3.1.1.3 Reading the Online Release Notes Both online and hardcopy versions of the release notes are provided. 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 MPI kit. From the installation media, you can read the release notes using the following procedure: o Physically mount the media on the appropriate disk drive. o Login as superuser (login name root) to the system where you are installing the software. o Enter the following command to ensure that you are in the root directory: # cd / o 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 o Use the more command to display the file: # more /mnt/pse180/documentation/pse180_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: o Software Product Description: pse180/documentation/pse180_spd.txt pse180/documentation/pse180_spd.ps o Installation Guide: pse180/documentation/pse180_iguide.txt pse180/documentation/pse180_iguide.ps MPI Installation (MPI only) 3-3 3.1.1.4 Checking Installation Procedure Requirements This section discusses various requirements for installing the MPI software. MPI installation takes less than 30 minutes, depending on your type of media and the complexity of the system configuration. 3.1.1.4.1 Login Privileges In order to install the MPI software, you need to become a superuser (root) on all MPI cluster members. 3.1.1.4.2 Checking Software Requirements The software requirements for DIGITAL MPI Version 1.8 are: o DIGITAL UNIX version 4.0a or higher In addition, if MEMORY CHANNEL[TM] support is needed, the following is required: o DIGITAL TruCluster software version 1.5 (requires DIGITAL UNIX V4.0d or higher) (or TruCluster MEMORY CHANNEL[TM] Software Version 1.5) You may also be able to use an earlier TruCluster version with a special patch (for details, see the Release Notes). The MPI software also requires the subsets of the DIGITAL UNIX software shown in Table 3-1 to be loaded on the system: Table_3-1_MPI_Subset_Requirements________________________________ MPI_Subset_Title______Requirement________________________________ DIGITAL MPI V1.8 OSFDCMT* Binary TCRCOMMON* (for MEMORY CHANNEL[TM] support) (MPIBIN180)___________TCRMCA*_(for_MEMORY_CHANNEL[TM]_support)___ To check the subsets that are loaded, follow these steps: 1. Log in to the system where you will install the MPI software. 3-4 MPI Installation (MPI only) 2. 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 MPI software. For information about loading the operating system software, see the DIGITAL UNIX (DEC OSF /1) installation guide. 3.1.1.4.3 Determining Which Subsets to Load You must choose the subsets you want to load. The following subset is required for all MPI cluster members: o DIGITAL MPI Binary (MPIBIN180) 3.1.1.4.4 Determining Disk Space Requirements Table 3-2 lists the disk space requirements for loading the MPI software subsets. These requirements apply to the disks where you load the MPI subsets. Table_3-2_MPI_Subset_Sizes_(Kilobytes_Required)____________ Subset_Title_______________Subset_Name___/usr___/var___/root DIGITAL MPI Binary V1.8 MPIBIN180 6144 Totals:__________________________________6144______________ 3.1.1.4.5 Listing the Files Installed by MPI You can list the files created by the MPI software installation by looking at: /mnt/pse180/kit/instctrl/MPI*180.inv. MPI Installation (MPI only) 3-5 3.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 MPI 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 MPI 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 3-2. 3.1.2 MPI Cluster Member Requirements Any MPI cluster member should meet the following requirements: o All MPI cluster members must run DIGITAL UNIX Version 4.0a or higher. o If MEMORY CHANNEL[TM] support is needed, all MPI cluster members must run either TruCluster software version 1.5 (requires DIGITAL UNIX V4.0d or higher), or MEMORY CHANNEL[TM] Software version 1.5. You may be able to use an earlier TruCluster version with a special patch (for details, see the Release Notes). o The passwd, group, hosts, and services information must be consistent across all MPI cluster members. This can be conveniently done by distributing this information using Network Information Service (NIS) or DNS. o Files used by all MPI applications (including the application image and, possibly, other data files) should be accessible by the same pathname from all MPI cluster members. Digital recommends setting up an Network File System (NFS) environment on all MPI cluster members with common directory mount points for user home directories and other directories that are used by MPI cluster applications. The automount daemon provides a convenient mechanism to manage these NFS mount points. 3-6 MPI Installation (MPI only) o All cluster users should have rsh access without password to any cluster members they plan to use. This can be achieved by specifying the cluster members' hostnames in the .rhosts file in your home directory. For More Information: o See the DIGITAL MPI User Guide 3.2 Loading the MPI Software This section describes how to load the MPI software onto each MPI cluster member. 3.2.1 Deleting Existing MPI Software Subsets Before loading a new version of the MPI software, any previous versions of the software must be deleted. If you are upgrading from a previous version of MPI, Digital recommends you follow the upgrading procedure detailed in the release notes. To delete MPI software, you must be superuser (username root). Make sure there are no MPI applications currently running. The command for deleting MPI software is: # cd / # setld -d MPIBINnnn Replace nnn with the MPI version number (e.g. 080 for version 0.8). For More Information: o On upgrading from a previous version of MPI, see the instructions in the release notes. 3.2.1.1 MPI Installation Summary This section contains a brief summary of the MPI software installation procedure. The procedure is explained in detail in Chapter 4. To load the MPI software kit onto a host, follow these steps: o For installation from a CD-ROM: 1. Log in as superuser (login name root). MPI Installation (MPI only) 3-7 2. Type the following commands (substitute your CD-ROM drive name for rzxxc. # cd / # mount -rd /dev/rzxxc /mnt # setld -l /mnt/pse180/kit 3. Refer to Section 3.1.1.4.3 to select the appropriate subsets. o For installation from an RIS (Remote Installation Service) server: 1. Log in as superuser (login name root). 2. Type the following commands (substitute your RIS server for nodename): # cd / # setld -l nodename: 3. Refer to Section 3.1.1.4.3 to select the appropriate subsets. For More Information: o On using setld to install the MPI software, see Chapter 4. o On setld, see the setld(8) manpage. 3.2.2 Running the Installation Verification Procedure ________________________ Note ________________________ The installation steps detailed in the preceding sections must successfully complete before attempting to execute the IVP for MPI. ______________________________________________________ After installing MPI, you can run the (IVP) independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to be sure that users can access MPI. The MPI IVP verifies the installation as shown in Example 3-1. 3-8 MPI Installation (MPI only) Example 3-1 Sample MPI IVP Log # setld -v MPIBIN180 Digital MPI V1.8 Binary (MPIBIN180) Copyright (c) Digital Equipment Corporation, 1995, 1999. All Rights Reserved. Starting the verification of Digital MPI V1.8 (MPIBIN180) Compiling an MPI test program ... Done. Linking test program with the libmpi.a library ... Link succeeded. *** The program however cannot be executed as root. *** To test that the compiled MPI program runs successfully *** (and prints an approximation of 'pi'), *** you may, as a non-privileged user: > cd /tmp > dmpirun -np 4 /tmp/mb_pi.mpi > echo ok MPIBIN180 IVP passed. # exit > cd /tmp > dmpirun -np 4 /tmp/mb_pi.mpi 3.1415926535897932384626433832795028 MPI Installation (MPI only) 3-9 4 _________________________________________________________________ Installation Using setld This chapter describes the procedures for loading the PSE software using the setld(8) command. You can either install the PSE locally (using CD-ROM media) or from a Remote Installation Service (RIS) server. If you encounter any failures during installation, see Section 4.4. 4.1 Using CD-ROM Consolidated Distribution Media This procedure loads the PSE files onto the system where you perform the installation. Follow these steps to install the PSE software from CD-ROM media: 1. Mount the media on the appropriate disk drive. 2. Log in as superuser (login name root) to the system where you will install the PSE software. 3. Make sure that you are at the root (/) directory by entering the following command: # cd / 4. Specify the /mnt directory to be the mount point for the distribution file system on the drive. If your drive is rzxxc, enter the following command: # mount -rd /dev/rzxxc /mnt 5. Enter a setld command that requests the load function (-l) and identifies the directory in the mounted file system where the PSE subsets are located. Installation Using setld 4-1 For example, if the directory location for these subsets is /mnt/pse180/kit, enter the following command: # setld -l /mnt/pse180/kit The installation procedure now displays the names of the PSE subsets and asks you to specify the subsets you want to load. See Section 4.3 to continue the installation. 4.2 Using a RIS Distribution Area If you are installing the PSE subsets that reside in a RIS distribution area on a remote system, follow these steps: 1. Log in as superuser (login name root) to the system where you will install the PSE software. 2. Make sure you are at the root directory (/) by entering the following command: # cd / 3. Enter a setld command that requests the load function (-l option) and identifies the system where the PSE subsets are located. For example, if you are loading the PSE subsets from a RIS distribution area on node orion, enter the following: # setld -l orion: Remote Installation Services now displays a menu that lists all the software subsets available to you and asks you to specify the subsets you want to load. See Section 4.3 to continue the installation. 4-2 Installation Using setld 4.3 Responding to Installation Procedure Prompts This section explains the installation procedure prompts and displays. 4.3.1 Selecting Subsets You must specify which of the PSE subsets you want to load. There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. ________________________ Note ________________________ If you are installing from a RIS distribution area, the number of subsets can vary depending on what products are available in the RIS area and how many subsets they have. ______________________________________________________ For example: The subsets listed below are optional: 1) Digital PVM V1.80 Base 2) Digital PVM V1.80 Supplementary Documentation 3) MPI Version 1.80 Binary Or you may choose one of the following options: 4) ALL of the above 5) CANCEL selections and redisplay menus 6) EXIT without installing any subsets Press RETURN to display the next screen: Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 4 To specify more than one number at the prompt, separate each number with a space, not a comma. Installation Using setld 4-3 Next, the script lets you verify your choice. For example, if you enter 1-3 in response to the previous prompt, the following is displayed: You are installing the following optional subsets: Digital PVM V1.80 Base Digital PVM V1.80 Supplementary Documentation MPI Version 1.80 Binary Is this correct? (y/n): If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu again displays and you can correct your choice of optional subsets. If the displayed subsets are the ones you want to load, enter y. 4.3.2 Monitoring Displays During the Subset Loading Process The installation procedure loads and verifies the selected PSE subsets. When you see the "Verifying" message during the subset installation, the installation procedure is checking to see that the files are copied correctly; it is not an Installation Verification Procedure (IVP) message. During the installation, if you get errors from the setld facility, see the Diagnostics section of the setld(8) reference page for an explanation of the errors and the appropriate actions to take. Digital recommends running an IVP (Installation Verification Procedure) after installation. For instructions on running the IVP, refer to the appropriate section(s): o PVM: Section 2.2.2 o MPI: Section 3.2.2 In Example 4-1, all the PSE subsets are loaded from CD- ROM. 4-4 Installation Using setld Example 4-1 PSE Subsets Loaded from CD-ROM Media Checking file system space required to install selected subsets: File system space checked OK. 3 subset(s) will be installed. Loading 1 of 3 subsets(s).... Copyright (c) Digital Equipment Corporation, 1997. All Rights Reserved. Starting installation at Tue Nov 24 12:40:06 EST 1998. Digital PVM V1.80 Base Copying from . (disk) Verifying Loading 2 of 3 subsets(s).... Digital PVM V1.80 Supplementary Documentation Copying from . (disk) Verifying Loading 3 of 3 subsets(s).... Copyright (c) Digital Equipment Corporation, 1997. All Rights Reserved. Digital MPI T1.80 MPIBIN180 Starting installation at Tue Nov 24 12:40:24 EST 1998. MPI Version 1.80 Binary Copying from . (disk) Working....Tue Nov 24 12:40:34 EST 1998 Verifying 3 of 3 subset(s) installed successfully. Configuring "Digital PVM V1.80 Base" (PVMBASE180) Installation of Digital PVM V1.80 Base (PVMBASE180) is complete. Before using the tools in this subset, please read the README file located in the /usr/opt/PVM180 directory for details on the kit contents and release information. Configuring "Digital PVM V1.80 Supplementary Documentation" (PVMSUPP180) Configuring "MPI Version 1.80 Binary" (MPIBIN180) (continued on next page) Installation Using setld 4-5 Example 4-1 (Cont.) PSE Subsets Loaded from CD-ROM Media Installation of Digital MPI T1.80 (MPIBIN180) is complete. Before using the libraries and tools in this subset, please read the README file located in the /usr/opt/MPI180 directory for details on the kit contents and release information. # ^D script done on tue Nov 24 12:41:55 1998 4.4 Failures During Product Installation If errors occur during the installation, the system displays failure messages. For example, if the installation fails due to insufficient disk space, the following message appears: There is not enough space for subset xxxxxx xxxxxx will not be loaded. Errors can occur during the installation if any of the following conditions exist: o Operating system version is incorrect o Prerequisite software version is incorrect o Disk space is insufficient o System parameter values for successful installation are insufficient For descriptions of error messages generated by these conditions, see the DIGITAL UNIX documentation on system messages, recovery procedures, and DIGITAL UNIX software installation. For More Information: o On system software requirements for DIGITAL PVM, see Section 2.1.1.4.2 o On system software requirements for DIGITAL MPI, see Section 3.1.1.4.2 4-6 Installation Using setld _________________________________________________________________ Index C______________________________ I______________________________ CD-ROM Installation Verification installation media, 2-2, 3-2 Procedures, 2-9, 3-8 mount point, 4-1 IVP using to load software, 4-1 Cover letter, 2-2, 3-2 See Installation Verification Procedures D______________________________ DIGITAL Fortran L______________________________ Installation, 2-1, 3-1 Login privileges DIGITAL MPI Support subset, during installation, 2-4, 3-5 3-4 DIGITAL PVM Support subset, 2-5 M______________________________ DIGITAL UNIX operating system MPI clusters software requirements, 2-4, preinstallation requirements, 3-4 3-6 Disk space checking, 2-6, 3-6 O requirements _______________________________ MPI, 3-5 Online documentation, 2-3, 3-3 PVM, 2-5 Operating system software requirements, 2-4, H______________________________ 3-4 High Performance Fortran P Support subset _______________________________ specifying, 4-3 Parallel Programming Environment subset specifying, 4-3 Preinstallation requirements MPI, 3-6 PVM, 2-6 Index-1 PSE System Software subset Software installation (cont'd) specifying, 4-3 software requirements, 2-4, PVM clusters 3-4 preinstallation requirements, specifying subsets, 4-3 2-6 subsets, 2-5, 3-5 PVM Manual Pages subset, 2-5 time, 2-4, 3-4 using setld, 4-1, 4-2 R______________________________ Subsets Release notes, 2-3, 3-3 specifying during Remote Installation Services installation, 4-3 loading software, 4-2 Superuser privileges RIS during installation, 2-4, See Remote Installation 3-4 Services Root privileges during installation, 2-4, 3-4 S______________________________ setld command, 4-1, 4-2 Software installation checking disk space, 2-6, 3-6 checking the kit, 2-2, 3-2 cover letter, 2-2, 3-2 disk space requirements MPI, 3-5 PVM, 2-5 error messages, 4-1, 4-4 installation displays, 4-4 loading from CD-ROM, 4-1 loading from RIS, 4-2 login privileges, 2-4, 3-4 Message Passing Interface Support subset, 3-5 operating system requirements , 2-4, 3-4 Parallel Virtual Machine Support subset, 2-5 PVM Manual Pages subset, 2-5 release notes, 2-3, 3-3 requirements, 2-4, 3-4 running the IVPs, 2-9, 3-8 Index-2