Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ibm tivoli workload scheduler load leveler installation guide v3.5

1,024 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Ibm tivoli workload scheduler load leveler installation guide v3.5

  1. 1. Tivoli Workload Scheduler LoadLevelerInstallation GuideVersion 3 Release 5 GI10-0763-05
  2. 2. Tivoli Workload Scheduler LoadLevelerInstallation GuideVersion 3 Release 5 GI10-0763-05
  3. 3. Note! Before using this information and the product it supports, be sure to read the information in “Notices” on page 45.Sixth Edition (November 2008)This edition applies to version 3, release 5, modification 0 of IBM Tivoli Workload Scheduler LoadLeveler (productnumbers 5765-E69 and 5724-I23) and to all subsequent releases and modifications until otherwise indicated in neweditions. This edition replaces GI10-0763-04. Significant changes or additions to the text and illustrations areindicated by a vertical line (|) to the left of the change.IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, oryou can send your comments to the address: International Business Machines Corporation Department 58HA, Mail Station P181 2455 South Road Poughkeepsie, NY 12601-5400 United States of America FAX (United States & Canada): 1+845+432-9405 FAX (Other Countries): Your International Access Code +1+845+432-9405 IBMLink™ (United States customers only): IBMUSM10(MHVRCFS) Internet e-mail: mhvrcfs@us.ibm.comIf you want a reply, be sure to include your name, address, and telephone or FAX number.Make sure to include the following in your comment or note:v Title and order number of this publicationv Page number or topic related to your commentWhen you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.© Copyright International Business Machines Corporation 1986, 2008.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.
  4. 4. ContentsAbout this information . . . . . . . . v Change the TWS LoadLeveler for Linux user ID 26Who should read this information . . . . . . . v Install the TWS LoadLeveler for Linux RPMs . . . 26Conventions and terminology used in this Run the TWS LoadLeveler for Linux initializationinformation . . . . . . . . . . . . . . . v script llinit . . . . . . . . . . . . . . . 29Prerequisite and related information . . . . . . vi Make the TWS LoadLeveler for Linux graphical IBM System Blue Gene Solution documentation vi user interface resource file available (optional) . . . 30How to send your comments . . . . . . . . vii Update the TWS LoadLeveler for Linux PATH environment variable . . . . . . . . . . . 30Summary of changes . . . . . . . . . ix Make the TWS LoadLeveler for Linux man pages available (optional) . . . . . . . . . . . . 31 Repeat the appropriate steps for each TWSChapter 1. Introduction . . . . . . . . 1 LoadLeveler for Linux machine . . . . . . . . 31 Configure your TWS LoadLeveler for Linux system 32Chapter 2. Pre-installation planning . . . 3Installation overview . . . . . . . . . . . 3 Chapter 5. Installing submit-only TWS About the TWS LoadLeveler filesets and RPMs . . 3 LoadLeveler for AIX . . . . . . . . . 33 Configuration planning . . . . . . . . . . 5 Submit-only TWS LoadLeveler for AIX planning General installation considerations . . . . . . 6 considerations . . . . . . . . . . . . . 33Migration considerations . . . . . . . . . . 7 TWS LoadLeveler for AIX disk space TWS LoadLeveler migration considerations . . . 7 requirements . . . . . . . . . . . . . 33Hardware, software, and disk requirements . . . . 9 Set up the submit-only TWS LoadLeveler for AIX Hardware requirements . . . . . . . . . 10 user ID and group . . . . . . . . . . . . 33 Software requirements . . . . . . . . . . 10 Install the submit-only TWS LoadLeveler for AIX Disk space requirements . . . . . . . . . 13 image . . . . . . . . . . . . . . . . 34Configuration example . . . . . . . . . . 14 Update your submit-only TWS LoadLeveler for AIX configuration . . . . . . . . . . . . . . 34Chapter 3. Installing TWS LoadLeveler Update the submit-only TWS LoadLeveler for AIXfor AIX . . . . . . . . . . . . . . . 15 cluster configuration . . . . . . . . . . . 34Decide on directories for TWS LoadLeveler for AIX 15 Install submit-only TWS LoadLeveler for AIX onLog in as root on TWS LoadLeveler for AIX . . . 15 other machines in the pool . . . . . . . . . 36Create the TWS LoadLeveler for AIX loadl groupname . . . . . . . . . . . . . . . . 15 Chapter 6. Installing submit-only TWSCreate the TWS LoadLeveler for AIX loadl user ID 16 LoadLeveler for Linux . . . . . . . . 37 Change the TWS LoadLeveler for AIX user ID . . 17 Submit-only TWS LoadLeveler for Linux planningInstall the TWS LoadLeveler for AIX image. . . . 18 considerations . . . . . . . . . . . . . 37Run the TWS LoadLeveler for AIX initialization Submit-only TWS LoadLeveler for Linux diskscript llinit . . . . . . . . . . . . . . . 20 space requirements . . . . . . . . . . . 37Make the TWS LoadLeveler for AIX graphical user Set up the submit-only TWS LoadLeveler for Linuxinterface resource file available (optional) . . . . 21 user ID and group . . . . . . . . . . . . 37Update the TWS LoadLeveler for AIX PATH Install the submit-only TWS LoadLeveler for Linuxenvironment variable . . . . . . . . . . . 22 RPMs . . . . . . . . . . . . . . . . 38Make the TWS LoadLeveler for AIX man pages Update your submit-only TWS LoadLeveler foravailable (optional) . . . . . . . . . . . . 22 Linux configuration . . . . . . . . . . . 40Repeat the appropriate steps for each TWS Update the submit-only TWS LoadLeveler for LinuxLoadLeveler for AIX machine . . . . . . . . 22 cluster configuration . . . . . . . . . . . 40Configure your TWS LoadLeveler for AIX system 22 Install submit-only TWS LoadLeveler for Linux on other machines in the pool . . . . . . . . . 42Chapter 4. Installing TWS LoadLevelerfor Linux . . . . . . . . . . . . . . 25 Accessibility features for TWSDecide on directories for TWS LoadLeveler for LoadLeveler . . . . . . . . . . . . 43Linux . . . . . . . . . . . . . . . . 25 Accessibility features . . . . . . . . . . . 43Log in as root on TWS LoadLeveler for Linux . . . 25 Keyboard navigation . . . . . . . . . . . 43Create the TWS LoadLeveler for Linux loadl group IBM and accessibility . . . . . . . . . . . 43name . . . . . . . . . . . . . . . . 25Create the TWS LoadLeveler for Linux loadl user ID 25© Copyright IBM Corp. 1986, 2008 iii
  5. 5. Notices . . . . . . . . . . . . . . 45 Index . . . . . . . . . . . . . . . 53Trademarks . . . . . . . . . . . . . . 46Glossary . . . . . . . . . . . . . . 49iv TWS LoadLeveler: Installation Guide
  6. 6. About this information This information will help you install, configure, and migrate IBM® Tivoli® Workload Scheduler (TWS) LoadLeveler®. It includes concepts and instructions pertaining to:| v Installing and configuring TWS LoadLeveler for AIX® and Linux®| v Installing and configuring submit-only TWS LoadLeveler for AIX and Linux Who should read this information This information is intended for system administrators responsible for installing, configuring, and maintaining the TWS LoadLeveler system. It assumes the administrators have a working knowledge of the AIX and Linux operating systems. Conventions and terminology used in this information Throughout the TWS LoadLeveler product information: v TWS LoadLeveler for Linux Multiplatform includes:| – IBM System servers with Advanced Micro Devices (AMD) Opteron or Intel®| Extended Memory 64 Technology (EM64T) processors – IBM System x™ servers – IBM BladeCenter® Intel processor-based servers – IBM Cluster 1350™ Note: IBM Tivoli Workload Scheduler LoadLeveler is supported when running Linux on non-IBM Intel-based and AMD hardware servers. Supported hardware includes:| – Servers with Intel 32-bit and Intel EM64T| – Servers with AMD 64-bit technology v Note that in this information: – LoadLeveler is also referred to as Tivoli Workload Scheduler LoadLeveler and TWS LoadLeveler. – Switch_Network_Interface_For_HPS is also referred to as HPS or High Performance Switch. Table 1 describes the typographic conventions used in this information. Table 1. Summary of typographic conventions Typographic Usage Bold v Bold words or characters represent system elements that you must use literally, such as commands, flags, and path names. v Bold words also indicate the first use of a term included in the glossary. Italic v Italic words or characters represent variable values that you must supply. v Italics are also used for book titles and for general emphasis in text. Constant Examples and information that the system displays appear in constant width width typeface. [] Brackets enclose optional items in format and syntax descriptions. © Copyright IBM Corp. 1986, 2008 v
  7. 7. Table 1. Summary of typographic conventions (continued) Typographic Usage {} Braces enclose a list from which you must choose an item in format and syntax descriptions. | A vertical bar separates items in a list of choices. (In other words, it means “or.”) <> Angle brackets (less-than and greater-than) enclose the name of a key on the keyboard. For example, <Enter> refers to the key on your terminal or workstation that is labeled with the word Enter. ... An ellipsis indicates that you can repeat the preceding item one or more times. <Ctrl-x> The notation <Ctrl-x> indicates a control character sequence. For example, <Ctrl-c> means that you hold down the control key while pressing <c>. The continuation character is used in coding examples in this information for formatting purposes.Prerequisite and related information The Tivoli Workload Scheduler LoadLeveler publications are: v Installation Guide, GI10-0763 v Using and Administering, SA22-7881 v Diagnosis and Messages Guide, GA22-7882 To access all TWS LoadLeveler documentation, refer to the IBM Cluster Information Center, which contains the most recent TWS LoadLeveler documentation in PDF and HTML formats. This Web site is located at: http://publib.boulder.ibm.com/infocenter/clresctr/vxrx/index.jsp A TWS LoadLeveler Documentation Updates file also is maintained on this Web site. The TWS LoadLeveler Documentation Updates file contains updates to the TWS LoadLeveler documentation. These updates include documentation corrections and clarifications that were discovered after the TWS LoadLeveler books were published. Both the current TWS LoadLeveler books and earlier versions of the library are also available in PDF format from the IBM Publications Center Web site located at: http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss To easily locate a book in the IBM Publications Center, supply the book’s publication number. The publication number for each of the TWS LoadLeveler books is listed after the book title in the preceding list. IBM System Blue Gene Solution documentation Table 2 on page vii lists the IBM System Blue Gene® Solution publications that are available from the IBM Redbooks® Web site at the following URLs:vi TWS LoadLeveler: Installation Guide
  8. 8. Table 2. IBM System Blue Gene Solution documentationBlue GeneSystem Publication Name URL ® ™Blue Gene /P IBM System Blue Gene Solution: Blue Gene/P http://www.redbooks.ibm.com/abstracts/ System Administration sg247417.html IBM System Blue Gene Solution: Blue Gene/P http://www.redbooks.ibm.com/abstracts/ Safety Considerations redp4257.html IBM System Blue Gene Solution: Blue Gene/P http://www.redbooks.ibm.com/abstracts/ Application Development sg247287.html Evolution of the IBM System Blue Gene Solution http://www.redbooks.ibm.com/abstracts/ redp4247.htmlBlue Gene®/L™ IBM System Blue Gene Solution: System http://www.redbooks.ibm.com/abstracts/ Administration sg247417.html Blue Gene/L: Hardware Overview and Planning http://www.redbooks.ibm.com/abstracts/ redp4257.html IBM System Blue Gene Solution: Application http://www.redbooks.ibm.com/abstracts/ Development sg247287.html Unfolding the IBM eServer Blue Gene Solution http://www.redbooks.ibm.com/abstracts/ redp4247.htmlHow to send your comments Your feedback is important in helping us to produce accurate, high-quality information. If you have any comments about this book or any other TWS LoadLeveler documentation: v Send your comments by e-mail to: mhvrcfs@us.ibm.com Include the book title and order number, and, if applicable, the specific location of the information you have comments on (for example, a page number or a table number). v Fill out one of the forms at the back of this book and return it by mail, by fax, or by giving it to an IBM representative. To contact the IBM cluster development organization, send your comments by e-mail to: cluster@us.ibm.com About this information vii
  9. 9. viii TWS LoadLeveler: Installation Guide
  10. 10. Summary of changes The following sections summarize changes to the IBM Tivoli Workload Scheduler (TWS) LoadLeveler product and TWS LoadLeveler library for each new release or major service update for a given product version. Within each information unit in the library, a vertical line to the left of text and illustrations indicates technical changes or additions made to the previous edition of the information. Changes to TWS LoadLeveler for this release or update include: v New information: – Recurring reservation support: - The TWS LoadLeveler commands and APIs have been enhanced to support recurring reservation. - Accounting records have been enhanced to have recurring reservation entries. - The new recurring job command file keyword will allow a user to specify that the job can run in every occurrence of the recurring reservation to which it is bound. – Data staging support: - Jobs can request data files from a remote storage location before the job executes and back to remote storage after it finishes execution. - Schedules data staging at submit time or just in time for the application execution. – Multicluster scale-across scheduling support: - Allows a large job to span resources across more than one cluster v Scale-across scheduling is a way to schedule jobs in the multicluster environment to span resources across more than one cluster. This feature allows large jobs that request more resources than any single cluster can provide to combine the resources from more than one cluster and run large jobs on the combined resources, effectively spanning resources across more than one cluster. v Allows utilization of fragmented resources from more than one cluster – Fragmented resources occur when the resources available on a single cluster cannot satisfy any single job on that cluster. This feature allows any size job to take advantage of these resources by combining them from multiple clusters. – Enhanced WLM support: - Integrates TWS LoadLeveler with AIX Workload Manager (WLM) virtual memory and the large page resource limit support. - Enforces virtual memory and the large page limit usage of a job. - Reports statistics for virtual memory and the large page limit usage. - Dynamically changes virtual memory and the large page limit usage of a job. – Enhanced adapter striping (sn_all) support: - Submits jobs to nodes that have one or more networks in the failed (NOTREADY) state provided that all of the nodes assigned to the job have more than half of the networks in the READY state.© Copyright IBM Corp. 1986, 2008 ix
  11. 11. - A new striping_with_minimum_networks configuration keyword has been added to the class stanza to support striping with failed networks. – Enhanced affinity support: - Task affinity support has been enhanced on nodes that are booted in single threaded (ST) mode and on nodes that do not support simultaneous multithreading (SMT). – NetworkID64 for Mellanox adapters on Linux systems with InfiniBand support: - Generates unique NetworkID64 IDs for adapter ports that are connected to the same switch and have the same IP subnet address. This ensures that ports that are connected to the same switch, but are configured with different IP subnet addresses, will get different NeworkID64 values. v Changed information: – This is the last release that will provide the following functions: - The Motif-based graphical user interface xloadl. The function available in xloadl has been frozen since TWS LoadLeveler 3.3.2 and there are no plans to update this GUI with any new function added to TWS LoadLeveler after that level. - The IBM BladeCenter JS21 with a BladeCenter H chassis interconnected with the InfiniBand Host Channel Adapters connected to a Cisco InfiniBand SDR switch. - The IBM Power System 575 (Model 9118-575) and IBM Power System 550 (Model 9133-55A) interconnected with the InfiniBand Host Channel Adapter and Cisco switch. - The High Performance Switch. – If you have a mixed TWS LoadLeveler cluster and need to run your job on a specific operating system or architecture, you must define the requirements keyword statement in your job command file specifying the desired Arch or OpSys. For example: Requirements: (Arch == "RS6000") && (OpSys == "AIX53") v Deleted information: The following function is no longer supported and the information has been removed: – The scheduling of parallel jobs with the default scheduler (SCHEDULER_TYPE=LL_DEFAULT) – The min_processors and max_processors keywords – The RSET_CONSUMABLE_CPUS option for the rset_support configuration keyword and the rset job command file keyword – The API functions: - ll_get_nodes - ll_free_nodes - ll_get_jobs - ll_free_jobs - ll_start_job – Red Hat Enterprise Linux 3 – The llctl purgeschedd function has been replaced by the llmovespool function. – The lldbconvert function is no longer needed for migration and the lldbconvert command is not included in TWS LoadLeveler 3.5.x TWS LoadLeveler: Installation Guide
  12. 12. Chapter 1. Introduction Installation descriptions encompass a range of product and processor options. This topic describes how to install:| v IBM Tivoli Workload Scheduler (TWS) LoadLeveler for AIX (AIX 6.1 and AIX| 5.3), Version 3 Release 5 Modification 0, product number 5765-E69 or 5724-I23| v TWS LoadLeveler for Linux Version 3 Release 5.0, product number 5724-I23,| running on the following:| – Red Hat Enterprise Linux (RHEL) 4 and RHEL 5| – SUSE Linux Enterprise Server (SLES) 9 and SLES 10| Note: IBM Tivoli Workload Scheduler LoadLeveler is supported when running| Linux on non-IBM Intel-based and AMD hardware servers.| Supported hardware includes:| – Servers with Intel 32-bit and Intel EM64T| – Servers with AMD 64-bit technology| References to TWS LoadLeveler Version 3 Release 5 apply to the latest version of| TWS LoadLeveler, which is 3.5.0.x, where x represents the latest service update. At| the time this information unit was published, the current service update was| 3.5.0.1. To find out which release of TWS LoadLeveler you currently are running,| issue the llctl version command.| You can obtain AIX and Linux service updates by accessing the “IBM Tivoli| Workload Scheduler LoadLeveler Support and downloads for AIX and Linux” Web| site at:| http://www14.software.ibm.com/webapp/set2/sas/f/loadleveler/home.html © Copyright IBM Corp. 1986, 2008 1
  13. 13. 2 TWS LoadLeveler: Installation Guide
  14. 14. Chapter 2. Pre-installation planning Before installing TWS LoadLeveler, there are planning activities that you must first consider. This topic explains the things you should be aware of before you install TWS LoadLeveler. Installation overview Before installing TWS LoadLeveler, take these steps to make the necessary considerations and decisions. Complete the following steps to install TWS LoadLeveler: 1. Ensure prerequisites are installed. (See “Software requirements” on page 10.) 2. Make configuration decisions, including: v Decide which machine will act as the central manager, and decide which machines will be backup central managers v Decide on the locations of the home and local directories for the TWS LoadLeveler user ID v Decide which directories will be shared directories, and which will not be shared. 3. Set up the TWS LoadLeveler user ID and group ID for all of the machines in the TWS LoadLeveler cluster.| 4. Install the TWS LoadLeveler for AIX filesets or the TWS LoadLeveler for Linux| RPM packages and the mandatory PTF. 5. Run the initialization script. 6. Update the configuration files. 7. Repeat the installation process for each workstation in the TWS LoadLeveler cluster. About the TWS LoadLeveler filesets and RPMs Filesets comprise the TWS LoadLeveler for AIX product, while RPMs comprise the TWS LoadLeveler for Linux product. Table 3 shows the filesets that comprise the TWS LoadLeveler for AIX product. It also shows their associated AIX directories after installation. Note that lang refers to the abbreviated name for a language locale, such as en_US. Table 3. TWS LoadLeveler for AIX filesets and their associated directories Fileset Description Associated directory LoadL.full TWS LoadLeveler /usr/lpp/LoadL/full LoadL.so Submit-only TWS LoadLeveler /usr/lpp/LoadL/so LoadL.msg.lang Messages and man pages for the Various subdirectories under /usr supported languages LoadL.tguides Configuration tasks /usr/lpp/LoadL/codebase LoadL.loc.license Software License Agreement /usr/swlag/lang © Copyright IBM Corp. 1986, 2008 3
  15. 15. The TWS LoadLeveler for AIX product is available through the TWS LoadLeveler installation image on CD. At times, the TWS LoadLeveler installation image is also given as an AIX file. To view the filesets that are available to you, enter the following AIX command: installp -l -d device where device is: v /cdrom for a CD v The path name of the installation image for a file Table 4 shows the RPMs that comprise the TWS LoadLeveler for Linux product. It also shows their associated Linux directories after installation. Table 4. TWS LoadLeveler for Linux RPMs and their associated directories RPM Description Associated directory| LoadL-full-license-Linux_identifier.rpm TWS LoadLeveler license /opt/ibmll/LoadL/lap| acceptance /opt/ibmll/LoadL/sbin LoadL-full-Linux_identifier.rpm TWS LoadLeveler /opt/ibmll/LoadL/full /opt/ibmll/LoadL/READMES| LoadL-so-license-Linux_identifier.rpm Submit-only TWS LoadLeveler /opt/ibmll/LoadL/lap| license acceptance /opt/ibmll/LoadL/sbin LoadL-so-Linux_identifier.rpm Submit-only TWS LoadLeveler /opt/ibmll/LoadL/so /opt/ibmll/LoadL/READMES Table 5 shows the supported Linux identifiers:| Table 5. Linux platforms and associated identifiers| Platform Identifier| RHEL 4 on Intel IA-32 32-bit platforms RH4-X86-3.5.0.x-0.i386| RHEL 5 on Intel IA-32 32-bit platforms RH5-X86-3.5.0.x-0.i386| SLES 9 on Intel IA-32 32-bit platforms SLES9-X86-3.5.0.x-0.i386| SLES 10 on Intel IA-32 32-bit platforms SLES10-X86-3.5.0.x-0.i386| RHEL 4 on AMD Opteron or Intel EM64T 64-bit RH4-X86_64-3.5.0.x-0.x86_64| platforms| RHEL 5 on AMD Opteron or Intel EM64T 64-bit RH5-X86_64-3.5.0.x-0.x86_64| platforms| SLES 9 on AMD Opteron or Intel EM64T 64-bit SLES9-X86_64-3.5.0.x-0.x86_64| platforms| SLES 10 on AMD Opteron or Intel EM64T 64-bit SLES10-X86_64-3.5.0.x-0.x86_64| platforms| RHEL 4 on IBM Power systems RHEL4-PPC64-3.5.0.x-0.ppc64| RHEL 5 on IBM Power systems RHEL5-PPC64-3.5.0.x-0.ppc64| SLES 9 on IBM Power systems SLES9-PPC64-3.5.0.x-0.ppc64| SLES 10 on IBM Power systems SLES10-PPC64-3.5.0.x-0.ppc64| Note: x represents the latest service update version| Note to Blue Gene/L users An RPM may apply to your IBM System Blue Gene Solution. 4 TWS LoadLeveler: Installation Guide
  16. 16. | The following RPM is for the IBM System Blue Gene Solution and applies to SLES| 9 on IBM Power systems only:| v LoadL-full-lib-SLES9-PPC-3.5.0.x-0.ppc.rpm Note to Parallel Operating Environment (POE) users Parallel Operating Environment (POE) users may require a corresponding optional RPM.| If you plan to use POE with TWS LoadLeveler for Linux on a 64-bit platform such| as RHEL 4 on Opteron, RHEL 4 on IBM Power systems, SLES 9 or SLES 10 on| Opteron, or SLES 9 or SLES 10 on IBM Power systems, you must install the| corresponding optional RPM. For TWS LoadLeveler, version 3.5.0.0, the optional| RPMs would be:| v LoadL-full-lib-RH4-X86-3.5.0.0-0.i386.rpm| v LoadL-full-lib-RHEL4-PPC-3.5.0.0-0.ppc.rpm| v LoadL-full-lib-SLES9-X86-3.5.0.0-0.i386.rpm| v LoadL-full-lib-SLES9-PPC-3.5.0.0-0.ppc.rpm| v LoadL-full-lib-SLES10-X86-3.5.0.0-0.i386.rpm| v LoadL-full-lib-SLES10-PPC-3.5.0.0-0.ppc.rpm These RPMs contain the 32-bit TWS LoadLeveler libraries for the appropriate 64-bit platforms and are required for the proper operation of POE with TWS LoadLeveler. Installation of these RPMs is not needed if you do not plan to use POE with TWS LoadLeveler: v A 32-bit library RPM can only be installed if the corresponding 64-bit TWS LoadLeveler ″full product″ RPM is already installed. v The rpm -ivh command is used to install the library RPM.| v On SLES 9 IBM Power systems, if you have already installed| LoadL-full-lib-SLES9-PPC-3.5.0.x-0.ppc.rpm for Blue Gene/L use, there is no| need to reinstall it to enable the POE and TWS LoadLeveler interface. Note to SLES 9 SP3 users The installation of the glibc-Update for IBM Power systems (SLES 9 SP3) is mandatory. You must upgrade glibc to 2.3.3-98.66, or later compatible release. The glibc update is available at: http://www.novell.com Configuration planning An integral part of the installation of TWS LoadLeveler is to configure your nodes. TWS LoadLeveler: Using and Administering has full details regarding configuration. Table 6 shows TWS LoadLeveler configuration information. Table 6. TWS LoadLeveler configuration information and default values Configuration information Default value TWS LoadLeveler user ID and group ID loadl is the TWS LoadLeveler user ID and the TWS LoadLeveler group ID The configuration directory The home directory of loadl is the configuration directory The global configuration file LoadL_config is the name of the configuration file Chapter 2. Pre-installation planning 5
  17. 17. The keywords LOCAL_CONFIG and ADMIN_FILE in the global configuration file define the full path names of the local configuration and the administration files. The global configuration file specifies system attributes common to all nodes. The administration file specifies attributes specific to individual nodes. The information given in the local configuration file is specific to an individual node. It overrides the corresponding information given in the global configuration file. TWS LoadLeveler assumes a common name space. This means that you need the same user ID and group ID on all machines in a TWS LoadLeveler cluster. The term cluster refers to all machines mentioned in the TWS LoadLeveler configuration file. See TWS LoadLeveler: Using and Administering for planning considerations for defining machines. You can define your own TWS LoadLeveler user ID and group ID. Note, however, that if you use an ID other than loadl, you have to substitute this new ID into all appropriate installation instructions. Also, you must create a file called /etc/LoadL.cfg and place it in the local directory /etc of each of the nodes in your TWS LoadLeveler cluster. In the LoadL.cfg file, you specify the following three keywords: LoadLUserid Specifies the TWS LoadLeveler user ID LoadLGroupid Specifies the TWS LoadLeveler group ID LoadLConfig Specifies the full path name of the global configuration file For TWS LoadLeveler on AIX, see “Change the TWS LoadLeveler for AIX user ID” on page 17 for additional information. For TWS LoadLeveler on Linux, see “Change the TWS LoadLeveler for Linux user ID” on page 26. General installation considerations When planning your TWS LoadLeveler installation, there are specific activities that you must first consider. v Many of the steps for installing TWS LoadLeveler must be performed as root. Therefore, you need superuser authority on each machine in the cluster. v AIX and Linux commands are case sensitive. Therefore, you must enter commands, directory names, and so on exactly as they appear. v Many of the installation steps contain examples that assume you are using standard TWS LoadLeveler directories and names. If you do not use the standard names, you must modify the examples accordingly. This is especially true for the TWS LoadLeveler local and home directories. v The directory containing the configuration files must be readable by all users who will submit jobs. v To use the llctl start command to start remote machines in a cluster, all TWS LoadLeveler administrator user IDs must have rsh privileges on all machines in the cluster. Check the appropriate AIX or Linux documentation for more information on the files used by rsh, such as $HOME/.rhosts and /etc/hosts.equiv. If you use the LL_RSH_COMMAND keyword to specify using another executable instead of rsh, ensure all appropriate files and necessary permissions have been set up.6 TWS LoadLeveler: Installation Guide
  18. 18. | v The LoadL_master binary is installed as a setuid program with the owner set to| root. If the release directory will be shared among machines in the cluster using| NFS, you must allow all files to be world-readable (by default), or you must| export the file system with root permission to all hosts that will be running TWS| LoadLeveler. When mounting the file system, do not use the -nosuid flag. v TWS LoadLeveler log files should be stored locally at the nodes for best performance. v TWS LoadLeveler for AIX can be run with cluster security services. If you want to enable cluster security services, see TWS LoadLeveler: Using and Administering for details. v TWS LoadLeveler for Linux does not support cluster security services. Migration considerations Before migrating TWS LoadLeveler, consider the following specific migration-related activities.| This topic discusses considerations for migrating to TWS LoadLeveler for AIX 3.5| from a previous TWS LoadLeveler for AIX release and for migrating to TWS| LoadLeveler for Linux 3.5 from a previous TWS LoadLeveler for Linux release. Note: If you are running TWS LoadLeveler in a mixed cluster, refer to the appropriate level of documentation for each version of TWS LoadLeveler in the cluster. TWS LoadLeveler migration considerations Make these considerations before migrating to TWS LoadLeveler from a previous TWS LoadLeveler release. Use either of the following two methods to migrate TWS LoadLeveler: 1. Take down all of the machines and migrate the entire cluster at once. 2. Migrate your cluster gradually one machine or a group of machines at a time. This method requires that the first machine in the cluster to be migrated is the central manager. Whichever method you choose, you should make backup copies of the following files: v LoadL_admin, the TWS LoadLeveler administration file v LoadL_config, the TWS LoadLeveler global configuration file v LoadL_config.local, the TWS LoadLeveler local configuration file Note: If process tracking is set and the TWS LoadLeveler kernel extension is already loaded when migration occurs, you might need to reboot the nodes. The process tracking kernel extension is not unloaded. Therefore, if a mismatch in the version is found, the startd daemon will exit. A reboot of the node is needed to unload the currently loaded kernel extension. Migrating TWS LoadLeveler Follow either of these step-by-step instructions depicting common migration scenarios. Chapter 2. Pre-installation planning 7
  19. 19. “Scenario 1: Migrating an entire TWS LoadLeveler cluster” requires that all of the machines in the cluster be migrated together. “Scenario 2: Machine-by-machine TWS LoadLeveler migration” corresponds to a machine-by-machine migration strategy. Scenario 1: Migrating an entire TWS LoadLeveler cluster: This scenario requires that all of the machines in the cluster be migrated together. 1. Log in as a TWS LoadLeveler administrator. Issue the command llctl -g drain. This will drain all of the Schedd machines so that no new jobs can be submitted to TWS LoadLeveler. This will also drain all of the startd machines so that no jobs already submitted to TWS LoadLeveler can be started. Jobs that are currently running will continue to run. 2. After all of the running jobs have completed and only idle jobs remain in the job queues, issue the command llctl -g stop to stop TWS LoadLeveler on all of the machines in the cluster. 3. Run the llsummary command on the machines that run the Schedd daemons if accounting reports are required. Accounting reports are made by first running the llacctmrg command to create a global history file before running the llsummary command. 4. Perform a backup of all of the files in the TWS LoadLeveler spool directory on all machines that run a Schedd daemon. This step is not essential, but strongly suggested in case something goes wrong during the installation. 5. Install the new version of TWS LoadLeveler using the instructions described in Chapter 3, “Installing TWS LoadLeveler for AIX,” on page 15 or Chapter 4, “Installing TWS LoadLeveler for Linux,” on page 25. You will need root permission to perform this operation. Under normal circumstances, the files in the spool directories (job queues, history files, executables of batch jobs, and so on) are not affected by the installation of TWS LoadLeveler. If these files are accidentally deleted during the installation process, the saved files from the previous step can be used to perform the appropriate restore operations. 6. Issue the command llctl -g start to bring up the migrated machines. Scenario 2: Machine-by-machine TWS LoadLeveler migration: This scenario corresponds to a machine-by-machine migration strategy.| Being able to migrate one machine at a time implies that the new release of TWS| LoadLeveler can coexist with the preceding TWS LoadLeveler release. In other| words, it is possible to set up a TWS LoadLeveler cluster consisting of some| machines running TWS LoadLeveler 3.5 level of software while the rest of the| cluster remains at the TWS LoadLeveler 3.4 software level.| Note: If you run in this environment, it is possible that some TWS LoadLeveler| commands will display message 2539-433 referring to ** unknown| LL_Specification ** multiple times. This message can be ignored. The| message will not be displayed after all machines in the cluster are upgraded| to the new release. 1. Select the machines that you want to migrate. The central manager machine must be migrated before any other machines can be restarted with the new TWS LoadLeveler release. Log in as a TWS LoadLeveler administrator. Issue the command llctl -h machine_name drain. As a result of this action, no new 8 TWS LoadLeveler: Installation Guide
  20. 20. jobs can be submitted to this machine and no new jobs will be started on this machine. Jobs that are currently running will continue to run. Repeat this step for all of the machines to be migrated. 2. After all running jobs on the machines to be migrated have completed and only idle jobs remain in the queues of the Schedd daemons on the machines to be migrated, issue the command llctl -h machine_name stop to stop TWS LoadLeveler on the specified machine. Repeat this action for all of the machines to be migrated. 3. Perform a backup of all of the files in the TWS LoadLeveler spool directory on the machines to be migrated that run the Schedd daemon. This step is not essential, but strongly suggested in case something goes wrong in the next step. 4. Install TWS LoadLeveler on the machines to be migrated using the instructions described in Chapter 3, “Installing TWS LoadLeveler for AIX,” on page 15 or Chapter 4, “Installing TWS LoadLeveler for Linux,” on page 25. You will need root permission to perform this operation. Under normal circumstances, the files in the spool directories are not affected by the installation of TWS LoadLeveler. If these files are accidentally deleted during the installation process, the files saved in the previous step can be used to perform the appropriate restore operations.| 5. Issue the command llctl -h machine_name start to bring up TWS LoadLeveler| 3.5 on the specified machine. Repeat this action for all of the machines to be| migrated. At this point, the migrated machines should be running TWS| LoadLeveler 3.5 and any jobs carried over will run in the upgraded cluster.| New features in TWS LoadLeveler 3.5 cannot be used in a mixed cluster of TWS| LoadLeveler 3.4 and 3.5 machines. If you are running TWS LoadLeveler in a mixed| cluster, refer to the appropriate level of information for each version of TWS| LoadLeveler in the cluster. TWS LoadLeveler APIs: TWS LoadLeveler provides application programming interfaces (APIs) that allow application programs written by customers to use specific data or functions that are part of TWS LoadLeveler. These APIs are enabled in such a way that user programs linked dynamically to the library libllapi.a on AIX or libllapi.so on Linux do not have to be compiled and linked again when an installation migrates from one TWS LoadLeveler release to the next. Note that a user application compiled with an earlier TWS LoadLeveler version is limited to the information specific to that release. Thus, if you have an application using a TWS LoadLeveler API compiled in a previous TWS LoadLeveler release, you do not absolutely have to recompile to use it with latest version of TWS LoadLeveler. However, this application cannot access the new data and functions specific to the latest TWS LoadLeveler release. In order to do this, you may have to make enhancements to the source codes of your application and recompile this application on a TWS LoadLeveler machine using the new version of the llapi.h header file. Hardware, software, and disk requirements Planning for installation requires two main tasks: ensuring you have the correct software and hardware installed, and allocating the correct amount of disk space for directories. Chapter 2. Pre-installation planning 9
  21. 21. Note: You are responsible for licensing and installing these products and integrating them with TWS LoadLeveler. Hardware requirements Installation planning requires that you ensure that compatible hardware will be installed. The following topics list the TWS LoadLeveler hardware requirements. TWS LoadLeveler for AIX hardware requirements| TWS LoadLeveler for AIX 6.1 and AIX 5.3 are compatible with certain hardware| platforms.| TWS LoadLeveler for AIX 6.1 and AIX 5.3 runs on:| v IBM Power Systems (POWER6™, POWER5™, and POWER4™)| v IBM BladeCenter Power Architecture® servers v IBM Cluster 1600 TWS LoadLeveler for Linux Multiplatform hardware requirements TWS LoadLeveler for Linux Multiplatform supports certain hardware platforms. TWS LoadLeveler for Linux Multiplatform supports the following platforms: v IBM System servers with AMD Opteron or Intel EM64T processors v IBM System x servers v IBM BladeCenter Intel processor-based servers v IBM System Cluster 1350 Note: IBM Tivoli Workload Scheduler LoadLeveler is supported when running Linux on non-IBM Intel-based and AMD hardware servers. Supported hardware includes: v Servers with Intel 32-bit and Intel Extended Memory 64 Technology (EM64T) v Servers with Advanced Micro Devices (AMD) 64-bit technology TWS LoadLeveler for Linux Multiplatform requires: v A minimum of 1 GB of memory v 1 GB of swap space TWS LoadLeveler for Linux on POWER hardware requirements TWS LoadLeveler for Linux on POWER™ supports certain hardware platforms. TWS LoadLeveler for Linux on POWER supports the following platforms:| v IBM Power Systems (POWER6, POWER5, and POWER4)| v IBM BladeCenter Power Architecture servers v IBM OpenPower® TWS LoadLeveler for Linux on POWER requires: v A minimum of 1 GB of memory v 1 GB of swap space Software requirements Installation planning requires that you ensure that compatible software will be installed. 10 TWS LoadLeveler: Installation Guide
  22. 22. The following topics list the TWS LoadLeveler software requirements. TWS LoadLeveler for AIX software requirements| TWS LoadLeveler for AIX 6.1 and AIX 5.3 have certain software platform| requirements.| Table 7 lists the TWS LoadLeveler AIX 6.1 and AIX 5.3 software requirements.| Table 7. TWS LoadLeveler for AIX software requirements| To use: TWS LoadLeveler for AIX| AIX operating systems, including bos.cpr AIX 6.1, TL 6100–02| AIX 5.3, TL 5300–09| Mandatory TWS LoadLeveler Service APAR IZ31336| https://www14.software.ibm.com/webapp/set2/sas/f/| loadleveler/download/aix.html| If you want:| Parallel jobs Using:| POE Parallel Environment (PE) 5.1| MPICH| MPICH 1.2.6 or later| MPICH-GM| On AIX 5.3: MPICH 1.2.6..13 or later and GM 2.0.12 or| later| OpenSSL in a multicluster environment OpenSSL 0.9.7 or later| RDMA with InfiniBand adapters AIX 6.1: LAPI 3.1.1.0| AIX 5.3: LAPI 2.4.5.0| OpenMP thread binding XL C or C++ 9.0.0.1 or later| XL FORTRAN 11.1.0.1 or later| RSCT or the llextRPD command 2.5.2.0 or later| (See note 1.)| TWS LoadLeveler graphical user interface AIXWindows Environment| (xloadl)| Java™ Runtime Environment filesets| TaskGuide Runtime Environment fileset (sysmgt.sguide.rte)|| Notes on the TWS LoadLeveler for AIX software requirements: 1. If you plan to configure TWS LoadLeveler to support the cluster security services component of RSCT, ensure that for each machine in the TWS LoadLeveler cluster, that cluster security services and Host Based Authentication (HBA) are installed and configured. The cluster security services component of RSCT is installed as part of the base AIX installation. HBA should be configured as the cluster security services’ default and the HBA ctcasd daemon should be running. The Trusted Hosts List (THL) must be updated to include other machines that will need to be authenticated. Chapter 2. Pre-installation planning 11
  23. 23. TWS LoadLeveler for Linux software requirements TWS LoadLeveler for Linux has certain software platform requirements.| Table 8 lists the TWS LoadLeveler for Linux software requirements.| Table 8. TWS LoadLeveler for Linux Multiplatform and TWS LoadLeveler for Linux on POWER software requirements| To use: TWS LoadLeveler for Linux TWS LoadLeveler for Linux on POWER| Multiplatform| Linux operating systems RHEL 4 or RHEL 5| (requires libelf, libXm, and| libXp packages) SLES 9 or SLES 10| Mandatory TWS LoadLeveler RPMs for 3.5.0.1| Service| http://www14.software.ibm.com/webapp/set2/sas/f/loadleveler/home.html| If you want:| Process tracking RHEL 5, SLES 10:| You need to download, build, and install the process tracking kernel module. The| source files and installation instructions are available at:| http://www14.software.ibm.com/webapp/set2/sas/f/loadleveler/download/| kernels.html| afs RHEL 4 or RHEL 5: OpenAFS 1.4.1 or Not applicable| later| (See note 1.)| IBM System Blue Gene Not applicable SLES 9: Blue Gene/L Release 2 or later| Solution| Not applicable SLES 10: Blue Gene/P Release 2 or later| Parallel jobs Using:| POE Parallel Environment (PE) 5.1| MPICH| MPICH 1.2.6 or later| MPICH-GM| On AIX 5.3: MPICH 1.2.6..13 or later and GM 2.0.12 or later| MVAPICH| MVAPICH-0.9.7 or later| OpenSSL in a multicluster OpenSSL 0.9.7 or later| environment| RDMA with InfiniBand Not applicable SLES10: LAPI 3.1.1.0| adapters| OpenMP thread binding Not applicable XL C or C++ 9.0.0.1 or later| Not applicable XL FORTRAN 11.1.0.1 or later| RSCT or the llextRPD RSCT 2.4.5.0 2.5.0.0 or later| command| TWS LoadLeveler graphical IBMJava2-JRE-1.4.2-5| user interface (xloadl)|| Notes on the TWS LoadLeveler for Linux software requirements:| 1. OpenAFS 1.4.1 or later is supported on TWS LoadLeveler for Linux nodes. It| can be used for token passing and token refresh between Linux and AIX.| OpenAFS is not supported on TWS LoadLeveler for AIX nodes. 12 TWS LoadLeveler: Installation Guide
  24. 24. 2. If you plan to use scheduling affinity, SLES 10 SP2 is required. To use scheduling affinity on SLES 10 SP2, you must create a /dev/cpuset directory using the mkdir /dev/cpuset command. Then mount a cpuset file system to /dev/cpuset using the following command: mount -t cpuset none /dev/cpuset 3. If you plan to include a Blue Gene system in your cluster, ensure that all symbolic links have been created in /usr/lib64 as required in the Blue Gene installation procedure. See the Blue Gene Driver README available at the Blue Gene Software Delivery Web site for details on creating the required symbolic links in /usr/lib64. 4. You can download the Myrinet software from the following Web site: http://www.myri.com/scs/ Disk space requirements Certain directories require specific amounts of disk space. In order for your installation to be successful, ensure that your directories have adequate space available. Table 9 lists disk space requirements for TWS LoadLeveler for AIX facilities. Table 9. Information about TWS LoadLeveler for AIX facilities Directory Size Release directory (/usr/lpp/LoadL/full) 45 MB¹ Local directory 15 MB (minimum) Home directory No limits unless same as release or local directory Release directory for submit-only (/usr/lpp/LoadL/so) 35 MB Configuration tasks directory (usr/lpp/LoadL/codebase) 1 MB| ¹ If installing the LoadL.webui sample, add 40 MB for /usr/lpp/LoadL/ and 55 MB for /opt/IBM/ll/webui. For more| information about this sample, see the README file in samples/llwebui in the release directory. Table 10 shows disk space requirements for TWS LoadLeveler for Linux facilities. Table 10. Information about TWS LoadLeveler for Linux facilities Directory Size Release directory (/opt/ibmll/LoadL/full) 30 MB¹ Local directory 20 MB (minimum) Home directory No limits unless same as release or local directory Release directory for submit-only (/opt/ibmll/LoadL/so) 22 MB System directory (/usr/lib or /usr/lib64) 24 MB (additional)| ¹ If installing the LoadL-webui RPM, add 40 MB for /opt/ibmll/LoadL and 60 MB for /opt/IBM/ll/webui. For more| information about this sample, see the README file in samples/llwebui in the release directory. Chapter 2. Pre-installation planning 13
  25. 25. Configuration example This example shows a TWS LoadLeveler installation on a small pool of workstations connected by a network. Many other configurations are possible. Table 11 demonstrates one way to install TWS LoadLeveler.Table 11. TWS LoadLeveler configuration exampleTWS LoadLeveler element Example directory or location on Example directory or location on central manager machine first node in clusterMachine name mycenman mynode01Central manager mycenman mycenmanTWS LoadLeveler for AIX home /u/loadl (exported) /u/loadl (mounted)directoryTWS LoadLeveler for Linux home /home/loadl (exported) /home/loadl (mounted)directoryLocal directory /var/loadl/mycenman /var/loadl/mynode01TWS LoadLeveler for AIX release /usr/lpp/LoadL/full (exported) /usr/lpp/LoadL/full (mounted)directoryTWS LoadLeveler for Linux release /opt/ibmll/LoadL/full (exported) /opt/ibmll/LoadL/full (mounted)directoryGlobal configuration file LoadL_config (in home directory) LoadL_config (in home directory) One copy for all machines. One copy for all machines.Local configuration file LoadL_config.local LoadL_config.local (in local directory) One copy for each machine. One copy for each machine.Administration file LoadL_admin (in home directory) LoadL_admin (in home directory) One copy for all machines. One copy for all machines.log directory /var/loadl/mycenman/log (in /var/loadl/mynode01/log (in subdirectory of a local directory) subdirectory of a local directory)spool directory /var/loadl/mycenman/spool (in /var/loadl/mynode01/spool (in subdirectory of a local directory) subdirectory of a local directory)execute directory /var/loadl/mycenman/execute (in /var/loadl/mynode01/execute (in subdirectory of the local directory) subdirectory of the local directory) Entries in the TWS LoadLeveler for AIX LoadL_admin file and the LoadL_config file appear in Table 12. For TWS LoadLeveler for Linux on System x and TWS LoadLeveler for Linux on POWER, update RELEASEDIR to RELEASEDIR=/opt/ ibmll/LoadL/full in the LoadL_config or LoadL_config.local file.Table 12. Sample LoadL_admin and LoadL_config file entriesLoadL_admin file LoadL_config filemycenman: type=machine RELEASEDIR=/usr/lpp/LoadL/full central_manager=true LOCAL_CONFIG=$(tilde)/$(host)/LoadL_config.localmynode01: type=machine LOG=/var/loadl/$(host)/log central_manager=false SPOOL=/var/loadl/$(host)/spool EXECUTE=/var/loadl/$(host)/execute14 TWS LoadLeveler: Installation Guide
  26. 26. Chapter 3. Installing TWS LoadLeveler for AIX You can install TWS LoadLeveler for AIX from the product media. Use this information to configure your TWS LoadLeveler environment. The System Management Interface Tool (SMIT) is suggested for performing the installation, but you can also use the command line to install TWS LoadLeveler. These installation instructions assume that the TWS LoadLeveler user ID is loadl. See “Change the TWS LoadLeveler for AIX user ID” on page 17 for information on using a user ID other than loadl as the TWS LoadLeveler user ID.Decide on directories for TWS LoadLeveler for AIX Decide on and record the locations of your home and local directories. Use the information in “Installation overview” on page 3 to decide on the location of the home and local directories. Once you decide, write the locations in the “Actual Directory” column in Table 13. Table 13. TWS LoadLeveler for AIX directory location checklist TWS LoadLeveler element Example directory Actual directory Local directory /var/loadl Home directory /u/loadl Release directory /usr/lpp/LoadL/full /usr/lpp/LoadL/full Name of central manager mycenman machine Important: The local directory must be unique to each machine in the cluster and must not be shared by any other machines in the cluster. Also, each machine must have its own TWS LoadLeveler spool, execute, and log directories.Log in as root on TWS LoadLeveler for AIX Unless otherwise indicated, all of the steps performed during TWS LoadLeveler installation should be done from the root user ID.Create the TWS LoadLeveler for AIX loadl group name Create the group name for every node in the TWS LoadLeveler cluster. The procedure in Table 14 on page 16 creates the group name only for the node that you are currently logged into. It must be repeated for every node in the TWS LoadLeveler cluster.© Copyright IBM Corp. 1986, 2008 15
  27. 27. Table 14. Procedure for creating the loadl group nameIf using: Do this:SMIT TYPE smit SELECT Security and Users SELECT Groups SELECT Add a Group ENTER The appropriate information in each field. For example: Group name: loadl Administrative group: true The group name and ID must be the same on each machine in the cluster. PRESS Ok PRESS Done and then select System Management from the Return to: list. If using SMITTY, press F3 (cancel) until you return to the System Management window.mkgroup Enter the following command: mkgroup -a loadlCreate the TWS LoadLeveler for AIX loadl user ID Create the user ID for every node in the TWS LoadLeveler cluster. The procedure in Table 15 on page 17 creates the user ID only for the node that you are currently logged into. It must be repeated for every node in the TWS LoadLeveler cluster.16 TWS LoadLeveler: Installation Guide
  28. 28. Table 15. Procedure for creating the loadl user IDIf using: Do this:SMIT SELECT Security and Users SELECT Users SELECT Add a User ENTER The appropriate information in the Create User window. For example: User Name: loadl Primary group: loadl Group set: loadl Home directory: /u/loadl The user name and ID must be the same on each machine in the cluster. PRESS Ok PRESS Done and then select Exit SMIT from the Exit menu or press F12. If using SMITTY, on the AIX platform, press F10 to exit the program. When the installation is complete, exit SMIT.On the AIX platform: Enter the following command: mkuser pgrp=loadl groups=loadl home=/u/loadl loadlmkuser Change the TWS LoadLeveler for AIX user ID To change the ID you must create a file called /etc/LoadL.cfg and modify this file to point to the user ID. If you want to use a different user ID, for example, “joe”, as the TWS LoadLeveler user ID, you must create a file called /etc/LoadL.cfg and modify this file to point to the user ID. To create this file, follow these steps: 1. su - root 2. Copy the LoadL.cfg file from the samples directory to the /etc directory. For example, on AIX, issue: cp /usr/lpp/LoadL/full/samples/LoadL.cfg /etc chmod 644 /etc/LoadL.cfg 3. Edit the file by entering: vi /etc/LoadL.cfg 4. Edit the LoadLUserid line to indicate a user ID other than loadl. 5. Edit the LoadLGroupid line to indicate a group associated with the new user ID. 6. Edit the LoadLConfig line to indicate the directory where the LoadL_config file will be located. For example, if the user ID is “joe” with a home directory of /u/joe, then: LoadLConfig=/u/joe/LoadL_config 7. Enter exit. Chapter 3. Installing TWS LoadLeveler for AIX 17
  29. 29. Install the TWS LoadLeveler for AIX image Before proceeding, make sure that no other licensed programs are in the process of being installed. For example, if the following command returns nothing, no other installp programs are running. ps -ef | grep installp | grep -v grep 1. Set up your installation device: Insert the TWS LoadLeveler product CD into the CD drive and mount the CD using the following commands: Insert the TWS LoadLeveler product CD into the CD drive and mount the CD using the following commands: mkdir /cdrom mount -v cdrfs -p -r /dev/cd0 /cdrom then substitute /cdrom for device in Table 16 on page 19. Note that device can also refer to a directory containing the installp image. 2. Choose an installation method: You can use SMIT or the command line to install TWS LoadLeveler. Use the procedure in Table 16 on page 19 to install the TWS LoadLeveler for AIX image.18 TWS LoadLeveler: Installation Guide
  30. 30. Table 16. Procedure for installing the image If using: Do this:|| SMIT v Install the base image 3.5.0.0:| SELECT| Software Installation and Maintenance| SELECT| Install and Update Software| SELECT| Install Software| ENTER| The device or directory containing the installation images| ENTER| For ″Software to install,″ enter:| The appropriate information to specify options (or select PF4).| For the option ACCEPT new license argreements?, enter Yes.| PRESS Ok| PRESS Done and then select Exit SMIT from the Exit menu or press F12.| If using SMITTY, on the AIX platform, press F10 to exit the program.| If you install using SMIT and select the following default:| Include corresponding LANGUAGE filesets? Yes| and lang is one of the supported languages, the LoadL.msg.lang fileset that| matches your LANG environment variable is automatically installed. If| you set this option to No, no message filesets are installed.| v Install the PTFs:| SELECT| Software Installation and Maintenance| SELECT| Install and Update Software| SELECT| Install and Update from ALL Available Software| ENTER| The device or directory containing the installation updates| ENTER| For ″SOFTWARE to install,″ select PF4 to select options to update, and| press Enter.| PRESS Ok| PRESS Done and then select Exit SMIT from the Exit menu or press F12.| If using SMITTY, press F10 to exit.| Chapter 3. Installing TWS LoadLeveler for AIX 19
  31. 31. Table 16. Procedure for installing the image (continued) If using: Do this:| installp Use the following command or commands to install the desired TWS LoadLeveler| features:| v To install the entire TWS LoadLeveler product, issue:| installp -Y -X -d device all| installp -X -B -d device all| v To install the TWS LoadLeveler component, issue:| installp -Y -X -d device LoadL.full| installp -X -B -d device LoadL.full| v To install the submit-only component, issue:| installp -Y -X -d device LoadL.so| installp -X -B -d device LoadL.so| v To install the messages and man pages, issue:| installp -X -d device LoadL.msg.lang| installp -X -B -d device LoadL.msg.lang| where device in Table 16 on page 19 is: v /cdrom for a CD v The path name of the installation image for a file| v The path name of the directory containing the PTF updates, which you can| download from:| https://www14.software.ibm.com/webapp/set2/sas/f/loadleveler/download/| aix.html The installp command reports on the success or failure of this step. Ensure that the result column in the summary contains SUCCESS for each part of TWS LoadLeveler that you are installing (APPLYing). Do not continue until all of the parts you wish to install are successfully applied. Whether you are using SMIT or the command line, you can now unmount the CD. To unmount the CD, enter: unmount /cdrom Run the TWS LoadLeveler for AIX initialization script llinit This step must be run for each of the machines in the TWS LoadLeveler cluster. 1. You must perform this step using the TWS LoadLeveler user ID. These instructions use loadl as this ID. To switch to the loadl ID, enter the following: su - loadl 2. Ensure that your HOME environment variable is set to loadl’s home directory. 3. Change the current directory to the bin subdirectory in the release directory by entering: cd /usr/lpp/LoadL/full/bin 4. To run llinit, ensure that you have write privileges in the TWS LoadLeveler home, local, and /tmp directories. 20 TWS LoadLeveler: Installation Guide
  32. 32. 5. Enter the llinit command. For example, to run the llinit command with a local directory of /var/loadl, a release directory of /usr/lpp/LoadL/full, and a central manager machine with the host name mycenman, enter the following: ./llinit -local /var/loadl -release /usr/lpp/LoadL/full -cm mycenman Ensure that the local directory exists before running the preceding command. About llinit llinit does the following: v Copies the LoadL_admin and the LoadL_config files from the release directory (in the samples subdirectory) into the home directory of loadl. Note: These files are a common resource for all of the machines in the TWS LoadLeveler cluster and, therefore, must be made accessible to all members of the TWS LoadLeveler pool. v Creates the TWS LoadLeveler spool, execute, and log directories in the local directory with permissions set to 700, 1777, and 775, respectively. v Copies the LoadL_config.local file from the release directory (in the samples subdirectory) into the local directory. v Creates symbolic links from the loadl home directory to the spool, execute, and log subdirectories and the LoadL_config.local file in the local directory (if home and local directories are not identical). v Creates symbolic links from the home directory to the bin, lib, man, samples, and include subdirectories in the release directory. The preceding files are copied and directories and symbolic links are created only if they do not already exist. Note: You can change the locations of the spool, execute, and log directories by changing the associated paths in the global configuration file. The global configuration file must reside in loadl’s home directory or the location specified in /etc/LoadL.cfg. For example, if you want to move the spool, execute, and log directory from /var/loadl into /tmp/loadl, with appropriate permissions set, you can do so but you must create /tmp/loadl/spool, /tmp/loadl/execute, and /tmp/loadl/log in /tmp/loadl or TWS LoadLeveler will not start up. See TWS LoadLeveler: Using and Administering for more information on the llinit command.Make the TWS LoadLeveler for AIX graphical user interface resourcefile available (optional) You should perform this step if you want to use and customize xloadl, the graphical user interface, on this machine. After copying the resource file, you can update the resource values for this machine. Copy the TWS LoadLeveler GUI resource files from the lib directory to the standard locations for resource files, and set the permission for the Xloadl files to 644 (read/write for owner, read for group and others) by entering the following: cp /usr/lpp/LoadL/full/lib/Xloadl /usr/lib/X11/app-defaults chmod 644 /usr/lib/X11/app-defaults/Xloadl Chapter 3. Installing TWS LoadLeveler for AIX 21
  33. 33. If you installed a LoadL.msg.lang fileset in “Install the TWS LoadLeveler for AIX image” on page 18, copy the resource file for that lang. cp /usr/lpp/LoadL/full/lib/$LANG/Xloadl /usr/lib/X11/$LANG/app-defaults chmod 644 /usr/lib/X11/$LANG/app-defaults/Xloadl The resource file /usr/lib/X11/$LANG/app-defaults/Xloadl takes precedence over the file /usr/lib/X11/app-defaults/Xloadl.Update the TWS LoadLeveler for AIX PATH environment variable Add one of the following path statements to your PATH environment variable: /usr/lpp/LoadL/full/bin /u/loadl/bin You can specify /u/loadl/bin if you previously ran llinit.Make the TWS LoadLeveler for AIX man pages available (optional) If you do not want to make the man pages available to users, you can skip this step. Add the following path to your MANPATH: /usr/lpp/LoadL/full/man If you installed a LoadL.msg.lang fileset in “Install the TWS LoadLeveler for AIX image” on page 18, add the following, preceding /usr/lpp/LoadL/full/man: /usr/lpp/LoadL/full/man/$LANGRepeat the appropriate steps for each TWS LoadLeveler for AIXmachine Repeat only the necessary steps. If the release directory can be mounted with AFS® or NFS, you can mount the directory, skip “Install the TWS LoadLeveler for AIX image” on page 18 and continue with “Run the TWS LoadLeveler for AIX initialization script llinit” on page 20 for other machines in your configuration. When you do not run installp: v You must create symbolic links for the shared libraries. Enter the following commands: ln -s /usr/lpp/LoadL/full/lib/libllapi.a /usr/lib/libllapi.a v You should issue the errupdate command on each machine where you want to format error logging entries. As root, issue the following command: errupdate -f loadl_err.S The loadl_err.S file is located in the /usr/lpp/LoadL/full/include directory. Note that if the release directory is mounted as read-only, the errupdate will fail unless you copy the file loadl_err.S to another directory before you issue the command.Configure your TWS LoadLeveler for AIX system This consists of editing certain files to meet the needs of your installation.22 TWS LoadLeveler: Installation Guide
  34. 34. Configuring your TWS LoadLeveler system consists of editing the files,LoadL_config and LoadL_admin, and the local file, LoadL_config.local to meet theneeds of your installation. For detailed instructions on configuring the TWSLoadLeveler environment, see TWS LoadLeveler: Using and Administering.Once you configure your system, you can verify your configuration by startingTWS LoadLeveler. See post-installation considerations in TWS LoadLeveler: Usingand Administering for more information. Chapter 3. Installing TWS LoadLeveler for AIX 23
  35. 35. 24 TWS LoadLeveler: Installation Guide
  36. 36. Chapter 4. Installing TWS LoadLeveler for Linux You can install TWS LoadLeveler for Linux from the product media. These installation instructions assume that the TWS LoadLeveler user ID is loadl. See “Change the TWS LoadLeveler for Linux user ID” on page 26 for information on using a user ID other than loadl as the TWS LoadLeveler user ID.Decide on directories for TWS LoadLeveler for Linux Decide on and record the location of your home and local directories. Use the information in “Installation overview” on page 3 to decide on the location of the home and local directories. Once you decide, write the locations in the “Actual Directory” column in Table 17. Table 17. TWS LoadLeveler for Linux directory location checklist TWS LoadLeveler element Example directory Actual directory Local directory /var/loadl Home directory /home/loadl Release directory /opt/ibmll/LoadL/full /opt/ibmll/LoadL/full Name of central manager mycenman machine Important: The local directory must be unique to each machine in the cluster and must not be shared by any other machines in the cluster. Also, each machine must have its own TWS LoadLeveler spool, execute, and log directories.Log in as root on TWS LoadLeveler for Linux Unless otherwise indicated, all of the steps performed during TWS LoadLeveler installation should be done from the root user ID.Create the TWS LoadLeveler for Linux loadl group name Create the group name for every node in the TWS LoadLeveler cluster. This procedure creates the group name only for the node that you are currently logged into. It must be repeated for every node in the TWS LoadLeveler cluster. Enter the command: groupadd -g loadl_group_id loadlCreate the TWS LoadLeveler for Linux loadl user ID Create the user ID for every node in the TWS LoadLeveler cluster. This procedure creates the user ID only for the node that you are currently logged into. It must be repeated for every node in the TWS LoadLeveler cluster. Enter the command:© Copyright IBM Corp. 1986, 2008 25

×