Road map for a Typical installation of IBM Tivoli Monitoring, Version 5.1.0

Transcription

1 Road map for a Typical installation of IBM Tivoli Monitoring, Version Objective To use an installation wizard to deploy IBM Tivoli Monitoring and the Tivoli Management Framework in a typical Tivoli environment. Note: Installation of the Tivoli Management Framework has the following requirements: v Your IBM Tivoli Sales representative can provide CDs for the following software that is required in addition to the software for IBM Tivoli Monitoring, Version 5.1.0: Tivoli Management Framework CDs: Tivoli Management Framework, Version 3.7, Revision B; and Tivoli Management Framework, Upgrade from Version 3.7, Revision B to Version CDs for configuring Linux computers: Tivoli Framework Server, Gateway and Endpoint for LINUX, Version 3.7B (3KLK3T ) v If a previous installation of the Tivoli Management Framework exists on the computer, use the Tivoli command line interface or Tivoli desktop to install this product. See the Tivoli Enterprise Installation Guide that comes with the Tivoli Management Framework software for additional information. Who should use the Typical installation method? The installation wizard provides two deployment paths: Typical and Custom. Use the Typical installation path if: v You want to install the product on a server that has never had the Tivoli Management Framework installed on it. v You are a first-time Tivoli user. v Your environment matches the Typical installation described in What is a Typical installation on page 2. v You do not want to create Windows endpoints during the installation process. (You can create Windows endpoints during the Custom installation process as described in the IBM Tivoli Monitoring, Version 5.1.0: Deployment Supplement.) Note: For HP-UX operating systems, you must be running HP-UX Version 11.x to install this product. The required Java run-time environment, Version 1.3, is available only for HP-UX 11.x. You cannot run the installation wizard on previous versions of HP-UX. Use the Custom installation path if you have a more complex environment than the typical installation. IBM Tivoli Monitoring, Version 5.1.0: Deployment Supplement provides procedures for the custom installation process. Note: See the instructions for the Custom installation path in the IBM Tivoli Monitoring, Version 5.1.0: Deployment Supplement to learn how to create Windows managed nodes and endpoints during the Custom installation process. Copyright IBM Corp. 1

2 What is a Typical installation? During the Typical installation, Tivoli recommends that you create the following: v Mandatory: One Tivoli management region server to monitor endpoints. The Tivoli server runs the Tivoli Management Framework and IBM Tivoli Monitoring software. v A managed node, which is a computer system on which Tivoli Management Framework is installed. Each managed node you create increases performance in the Tivoli environment by reducing traffic on the Tivoli management region server. The IBM Tivoli Monitoring software also runs on a managed node. v Up to 50 endpoints for monitoring resources on your network. You distribute monitoring software to the endpoints. v One Health Console on a managed node or endpoint. The console shows the status and health of a server in a Web browser. You can create an unlimited number of Health Consoles. These consoles can display the status of resources for an unlimited number of Tivoli management regions. Disk space requirements The product installation requires the following amount of free disk space: v Tivoli Management Framework and IBM Tivoli Monitoring: 500 MB v The installation depot (temporary directory): 2.1 GB v Files that the installation wizard places in the temporary (/tmp or %temp%) directory that is defined for your operating system: approximately 10 MB v Web Health Console server: 130 to 200 MB, depending on the operating system of the target computer. Information required by the Typical installation Obtain the following information before you begin a Typical installation: v The directory path on the computer on which you want to install the product. Remember the directory must have 500 MB of free disk space. v A directory path that is accessible from the installation computer with 2.1 GB of disk space to store temporary files. (The installation wizard provides the option to automatically delete this directory after installation.) v The user password of the person who is installing the product. On UNIX, the user who installs the product must have root privileges. On Windows, the user who installs the product must have membership in the Administrators group. v The license key for Tivoli Management Framework software. Obtain the license key from the Tivoli Key Memo that comes with the Tivoli Management Framework software package. v The following values for all managed nodes and endpoints: The IP host name. A label to identify each endpoint. The label name can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). The names are case-sensitive. For example, the name EPName is different from epname. The type of the operating system used by the endpoint or managed node. The user ID and password for a user who has the required privileges on the computer you are configuring. On UNIX, the user must have root privileges. On Windows, the user must have membership in the Administrators group. Tivoli recommends that you log on as root on UNIX and Administrator on Windows. 2 Road map for a Typical installation: IBM Tivoli Monitoring

3 Additional Information: See Considerations for the Typical installation path: v General considerations on page 5: What to do if the installation process is interrupted temporarily. Messages that are displayed during installation. v UNIX considerations on page 5 Required fix packages and fonts for some versions of Solaris. v Windows considerations on page 6: How to create endpoints. Procedure On Windows, the installation wizard prompts you to restart your computer after it performs the following tasks: v Creates the user ID for the Tivoli Management Framework v Installs the Tivoli Management Framework software If you are installing the product in a language other than English, you must type single-byte characters (not double-byte characters) in the text boxes of the wizard panels. The strings that you type can include alphanumeric characters, underscores (_), hyphens (-), and periods (.). Step One Log on to the computer that you want to be the main Tivoli server. On UNIX, the user who installs the product must have root privileges. On Windows, the user who installs the product must have membership in the Administrators group. The installation wizard installs software for the Tivoli management region on this computer. Step Two Test that required software is running on the remote target computers that you configure during this installation. For example, in the environment recommended in What is a Typical installation on page 2 the required software must be running on any remote computers that you configure as managed nodes and endpoints: v For installation of managed nodes and endpoints on UNIX target computers, test the rexecd daemon: 1. Run a basic rexec command string against the target computer. For example, run the following command from a DOS prompt or xterm window: rexec <target_computer_name> echo test 2. Respond to the prompt for a user ID and password by typing the root ID and password. If the command is unsuccessful, you receive an error, for example, an authentication error, a notice that the server is down, or a notice that rexec failed to run. 3. Do not proceed with installation of this product until a system administrator can make the rexec daemon accessible on the target computer. Road map for a Typical installation of IBM Tivoli Monitoring, Version

4 v For installation of Windows managed nodes on target computers, test the Tivoli Remote Execution Service (TRIP) process: Note: Creation of Windows endpoints is not an option in the Typical installation path. If you want to use the installation wizard to create endpoints on Windows target computers, use the Custom installation path. 1. Run a basic rexec command string against the target system. For example, run the following command from a DOS prompt or xterm window: rexec <target_computer_name> cmd /c echo test 2. Respond to the prompt for a user ID and password by typing the Administrator ID and password. If the command is unsuccessful, you receive an error, for example, an authentication error, a notice that the server is down, or a notice that the process failed to run. 3. Do not proceed with installation of this product until you complete these steps: a. Log on to the target computer on which you want to confirm that the Tivoli Remote Execution Service exists. b. Access the Services user interface in the Windows control panel. c. Find the Tivoli Remote Execution Service in the Service list and perform one of the following actions: 1) If this service exists and the status is Stopped, click the Start button. 2) If this service exists and the status is Started, resolve firewall blocks or other network connectivity problems between this computer and the computer on which you are installing IBM Tivoli Monitoring. 3) If this service does not exist, run the setup.exe executable in the TRIP directory of the software installation CD for Tivoli Management Framework. Follow the instructions in the wizard panels. Step Three Run the setup executable in the root directory of the installation CD labeled IBM Tivoli Monitoring Tools V5.1. Additional Information: The executable launches the installation wizard. Select the executable that matches your operating system: v For Windows, setupwin32.exe v For Solaris, setupsolaris.bin v For AIX, setupaix.bin v For HP-UX, setuphpux11.bin (This executable is valid only for HP-UX, Version 11.x.) Step Four Follow the instructions in the wizard panels. The wizard prompts you to insert CDs for each software component that you need to install. The Objective on page 1 describes CDs that are required in addition to the CDs for IBM Tivoli Monitoring, Version CAUTION: You can click Cancel to temporarily suspend an installation and resume it only in the Step List panel of the wizard. This panel is displayed in the last stages of the installation. If you click the Cancel button in any other wizard panel and stop the installation, you cannot resume installation. Instead, you must begin installation again by running the setup executable on the installation CD. 4 Road map for a Typical installation: IBM Tivoli Monitoring

5 Considerations for the Typical installation path This section describes issues by category and describes workarounds for a Typical installation. The list might not be complete. Table 1. Considerations for the Typical installation path Consideration Workaround General considerations When you enter an invalid user ID or password for Perform the following steps: the installation of managed nodes or endpoints, the wizard panel accepts your settings, but later the wizard displays an error message in the Step Detail dialog box when it begins to install this software. 1. Click the Change buttoninthestep Detail dialog box to display the Change Value dialog box. 2. Enter the new value in the Change Value dialog box for user ID, password, and destination directory, as needed. At any time you can double-click this failed step in the Step List to perform this workaround. You can click Cancel to temporarily suspend an installation and resume it only in the Step List panel of the wizard. This panel is displayed in the last stages of an installation when installation of software actually begins. CAUTION: If you click the Cancel button in any other wizard panel and stop the installation, you cannot resume installation. Instead, you must begin installation again by running the setup executable on the installation CD. UNIX considerations A Solaris environment requires certain fix packages to enable installation of this product. If this operation fails, perform the following steps: 1. Click the Defer buttoninthestep Detail dialog box. 2. Allow the installation process to finish. 3. Manually perform any step that you defer. See the Tivoli Enterprise Installation Guide that comes with the Tivoli Management Framework software for information on manually installing managed nodes and endpoints. Suspend and resume an installation at the point where you cancel, preserving all previous settings: 1. Click the Stop buttoninthestep List panel of the installation wizard. 2. Allow the currently running process to finish. 3. Click Cancel to stop the installation and close the wizard. 4. When you want to resume the installation, run the installation executable that the wizard places in the installation depot (the temporary directory that the installation wizard places on your hard drive). Install these fix packages prior to installing the product. Fix packages for Solaris , , , , , , , , , , , , , , and Fix packages for Solaris , , , , , , , , , , , , , and SUNWi1 fonts package Note: You can obtain the fonts package on the Solaris installation CD. Fix packages for Solaris , , and Road map for a Typical installation of IBM Tivoli Monitoring, Version

6 Table 1. Considerations for the Typical installation path (continued) Consideration Workaround Installation of the product might hang at a specific stage in the HP-UX Version 11.x operating system. Specifically, in the Step List panel of the wizard the installation of the patch that enables Version of the Tivoli Management Framework completes successfully, but the process occasionally does not return control to the installation wizard. Windows considerations You cannot create Windows endpoints during the Typical installation for this product. This limitation exists because the Tivoli management region server requires a user ID and password on a pre-existing endpoint to obtain access to a Windows domain. This endpoint acts as a proxy endpoint through which you can configure other endpoints in the target domain. Without a proxy endpoint, the Tivoli server cannot create endpoints on other Windows servers in that domain. If the wizard step that installs this patch continues for over 15 minutes, inspect the Tivoli installation file, tivoli.cinstall, to confirm that it has not been updated for at least five minutes: 1. Run the following command to get the timestamp of the file: ls -l /tmp/tivoli.cinstall 2. Run the following command to get the timestamp of the computer: date 3. Respond as appropriate to the timestamp values: a. If the timestamps in Steps 1 and 2 differ by five or more minutes, the installation is hung. Go to Step 4. b. If the timestamps differ by less than five minutes, watch the installation wizard panel for signs that installation is continuing. 4. Run the following commands to kill the process corresponding to this step of the installation process: a. Get the ID of the process: ps -ef grep wpatch b. Kill the process: kill -9 <process_id> where <process_id> is the ID of the process. 5. Access the Tivoli command line interface as follows: v For the Bourne, Korn, or bash shell, run the following command:./etc/tivoli/setup_env.sh v For the C shell, run the following command: source /etc/tivoli/setup_env.csh 6. Run the following command to recycle the Tivoli oserv daemon: odadmin reexec all 7. Click the Run All buttoninthestep List wizard panel to resume installation. This action also changes the red x that indicates a problem with the step to a green check mark. Create Windows endpoints during the Custom installation. See IBM Tivoli Monitoring, Version 5.1.0: Deployment Supplement for information on creation of a proxy endpoint during a Custom installation. After you complete a Typical installation, manually configure a Windows endpoint in a Windows domain, as described in IBM Tivoli Monitoring, Version 5.1.0: Deployment Supplement. 6 Road map for a Typical installation: IBM Tivoli Monitoring

7 Copyright International Business Machines Corporation All rights reserved. IBM and Tivoli are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be the trademarks or service marks of other companies. U.S. Government Users Restricted Rights Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. GI Road map for a Typical installation of IBM Tivoli Monitoring, Version