Professional Documents
Culture Documents
Version 3.3
This document is published by the BMC Software, Inc., Technical Publications Department. Copyright [19961999] BMC Software, Inc. All rights reserved. BMC Software, the BMC Software logos, and all other product or service names are trademarks or registered trademarks of BMC Software, Inc., in the USA and in other select countries. The and indicate USA trademark or USA registration. *IBM, Acrobat, CA, Sequent, and Sun are registered trademarks or trademarks of, respectively, International Machines Corp.; Adobe Systems, Inc.; and Sun Microsystems, Inc. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corp. PATROL Technology--US Patent No. 5,655,081 PATROL SCRIPT LANGUAGE IS PROPRIETARY AND CONFIDENTIAL TO BMC SOFTWARE, INC. All other third-party logos and product/trade names are trademarks or registered trademarks of their respective companies. RESTRICTED RIGHTS LEGEND Use, distribution, or disclosure by the Government is subject to restrictions set forth in subparagraph (c)(1)(ii) of Rights in Technical Data and Computer Software clause in DFARS 252.227-7013. BMC Software, Inc. 2101 CityWest Blvd. Houston, TX 77042-2827 USA
International
Outside the USA and Canada, you can contact a BMC Software international support center: Africa, Europe, Latin America, and the Middle East Asia/Pacific BMC Software, Inc. BMC Software (Australia) Pty. Ltd. 2101 CityWest Blvd. 3rd Floor Houston, TX 77042-2827 290 Burwood Road USA Hawthorn Victoria Telephone: 713 918 8800 Australia Fax: 713 918 1303 Telephone: (61) 3 9810 2010 Fax: (61) 3 9810 2030 You can also call the BMC Software office in your country, if applicable. For a complete list of all BMC Software offices and subsidiaries anywhere in the world, see the BMC Software home page at http://www.bmc.com.
Contents
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Chapter 1 PATROL Installation Introduction
PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Installation and Operation Requirements . . . . . . . . . . . . . . . . . . . . . 1-4 Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 CPU and Operating System Requirements . . . . . . . . . . . . . . . . . 1-6 PATROL Console Memory Requirements . . . . . . . . . . . . . . . . . 1-7 PATROL Console Display Requirements . . . . . . . . . . . . . . . . . . 1-7 Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 PATROL Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 GNU Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Upgrading to a New Version of PATROL . . . . . . . . . . . . . . . . . . . . . 1-9 Methods for Installing PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Installing a Patch for PATROL Products . . . . . . . . . . . . . . . . . . . . . . 1-10 Overview of Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Installation Program Record Files . . . . . . . . . . . . . . . . . . . . . . . 1-13 Navigating Within the Installation Program . . . . . . . . . . . . . . . . 1-14 Password Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 Saving Product and Host Files . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Quitting the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Starting the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 Preparing to Install PATROL Products . . . . . . . . . . . . . . . . . . . . 1-18 Starting the Installation Program with CD1 for Unix . . . . . . . . . 1-23 Starting the Installation Program with CD2 for Unix . . . . . . . . . 1-31
Contents
iii
Chapter 2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 Installing PATROL Agents and Consoles . . . . . . . . . . . . . . . . . . . . .2-3 Installing PATROL Agents and Consoles . . . . . . . . . . . . . . . . . .2-4 Installing PATROL KMs to Agent and Console Computers . . . . . . .2-22 Installing PATROL KMs to Agent and Console Computers . . . .2-23
Chapter 3 Installing the PATROL KMDS and PATROL KMs
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Installation of the PATROL Knowledge Module Deployment Server 3-3 Installing the PATROL KMDS . . . . . . . . . . . . . . . . . . . . . . . . . .3-4 Installation of the PATROL KMs to the PATROL KMDS Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20 Installation of PATROL KMs to the PATROL KMDS . . . . . . . .3-21
Chapter 4 Replicating and Uninstalling PATROL Products
Replicating PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Creating the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3 Replicating PATROL Products to Remote Computers . . . . . . . .4-7 Uninstalling PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22 Uninstalling PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . .4-23
Chapter 5 Configuring, Starting, and Licensing PATROL
Running the Configuration Script . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2 Configuring PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . .5-3 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4 Starting PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5 Starting a PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6 Starting the PATROL Consoles . . . . . . . . . . . . . . . . . . . . . . . . . .5-7 Starting the PATROL Event Manager . . . . . . . . . . . . . . . . . . . . .5-10 Setting PATROL Environment Variables . . . . . . . . . . . . . . . . . .5-11 Supplying License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12 To Supply License Information . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
Chapter 6 Upgrading from a Prior Version of PATROL
Upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2 PATROL Knowledge Module Deployment Server . . . . . . . . . . .6-2 Compatibility Between Versions . . . . . . . . . . . . . . . . . . . . . . . . .6-2 Migrating KM Customizations to a New Version of PATROL . .6-2 PATROL KMDS histool Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
BMC Software, Inc., Confidential and Proprietary Information
iv
Installing the PATROL Help Browser . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Setting the Required Environment Variables . . . . . . . . . . . . . . . . . . 7-3 LANG Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 PATH Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 PATROL_BROWSER Variable . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Additional Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Installing the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Chapter 8 Installing PATROL Using the Text-Based Installation Program
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 CPU and Operating System Requirements for the Text-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Using the Text-Based Installation Program to Install or Uninstall PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Starting the Text-Based Installation Program . . . . . . . . . . . . . . . 8-5 Installing the PATROL Agent with the Text-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . 8-8 Installing PATROL Knowledge Modules with the Text-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21 Uninstalling PATROL Products with the Text-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . 8-31 Using a Batch File to Install or Uninstall PATROL Products . . . . . . 8-38 Building the Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39 Running the Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
Appendix A The PATROL Products Files and Directories on the Disk Drive
PATROL Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Files Used by the PATROL Console . . . . . . . . . . . . . . . . . . . . . A-4 Files Used by the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . A-5 $PATROL_HOME Directory Structure . . . . . . . . . . . . . . . . . . . . . . A-6 $PATROL_HOME/log/history Parameter History Directory . . A-6 $PATROL_HOME/log/PEM_<hostname>_<portnumber>.log and .archive Permanent Event Log Files . . . . . . . . . . . . . . . . . . . A-7 $PATROL_HOME/log/PatrolAgent-<hostname>_ <portnumber>.errs.~<iter>~ Files . . . . . . . . . . . . . . . . . . . . . A-8 $HOME/patrol Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . A-8
BMC Software, Inc., Confidential and Proprietary Information
Contents
$HOME/patrol/chart, desktop Directories . . . . . . . . . . . . . . . . . A-9 $HOME/patrol/psl User-written PSL Scripts Directory . . . . . . A-9 $HOME/patrol/knowledge/session-<id> Session Information Files A-10 $HOME/patrol/tmp/Patrol-<id>.errs.~<iter>~ Log Files . . . . . A-10 /tmp/patrol Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 /tmp/patrol/PEM_<hostname>_<portnumber>.log.lock Temporary Lock Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 PATROL3.3KMDS Directory Structure . . . . . . . . . . . . . . . . . . . . . A-12 PATROL3.3KMDS\tbldata . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12 PATROL3.3KMDS\lib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13 PATROL3.3KMDS\<Unix operating system> . . . . . . . . . . . . . A-13
Appendix B Using PATROL with Firewalls
Types of Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Agent/Console Communication Basics . . . . . . . . . . . . . . Reliable UDP-Based Transport . . . . . . . . . . . . . . . . . . . . . . . . . TCP-Based Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL KMDS Communication Basics . . . . . . . . . . . . . . . . . . . .
Appendix C Appendix D Using Installation Program Command Line Options Installation Troubleshooting
Overview of Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reviewing the logfile<pid> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnosing Specific Issues with FTP . . . . . . . . . . . . . . . . . . . . . . . . Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index
vi
Figures
Figures
Figure 1-1 Figure 1-2 Figure 1-3 Figure 1-4 Figure 1-5 Figure 1-6 Figure 1-7 Figure 1-8 Figure 1-9 Figure 1-10 Figure 1-11 Figure 1-12 Figure 1-13 Figure 1-14 Figure 1-15 Figure 1-16 Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 2-9 Figure 2-10 Abort Install Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 Abort Install Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 PATROL product set selection Text . . . . . . . . . . . . . . . . . . . . . . 1-24 Set the DISPLAY environment variable Text . . . . . . . . . . . . . . . 1-25 Populate hostlist with nslookup Text . . . . . . . . . . . . . . . . . . . . . 1-25 PATROL products path selection Text . . . . . . . . . . . . . . . . . . . . 1-26 PATROL Installation log file path selection Text . . . . . . . . . . . . 1-27 Starting PATROL Installation with the following pathnames Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27 PATROL Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . 1-29 Installation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29 Set the DISPLAY environment variable Text . . . . . . . . . . . . . . . 1-32 Populate hostlist with nslookup Text . . . . . . . . . . . . . . . . . . . . . 1-33 PATROL products path selection Text . . . . . . . . . . . . . . . . . . . . 1-34 PATROL Installation log file path selection Text . . . . . . . . . . . . 1-34 Starting PATROL Installation with the following path names Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35 Installation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36 PATROL products path selection Text . . . . . . . . . . . . . . . . . . . . 2-5 Installation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 Installation Operations Dialog Box . . . . . . . . . . . . . . . . . . . . . . 2-7 PATROL Products Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Advanced Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Select Hosts Dialog Box (Remote Installation Only) . . . . . . . . . 2-10 User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Destination Location Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 2-12 Destination Directory Matrix Dialog Box . . . . . . . . . . . . . . . . . 2-13 Account Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Figures
vii
Figure 2-11 Figure 2-12 Figure 2-13 Figure 2-14 Figure 2-15 Figure 2-16 Figure 2-17 Figure 2-18 Figure 2-19 Figure 2-20 Figure 2-21 Figure 2-22 Figure 2-23 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 3-6 Figure 3-7 Figure 3-8 Figure 3-9 Figure 3-10 Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 Figure 3-15 Figure 3-16 Figure 3-17 Figure 3-18 Figure 3-19 Figure 3-20 Figure 3-21 Figure 4-1 Figure 4-2 Figure 4-3 Figure 4-4 Figure 4-5 Figure 4-6
PATROL Username/Password Matrix Dialog Box . . . . . . . . . . .2-14 Root Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . .2-15 PATROL Root Password Matrix Dialog Box . . . . . . . . . . . . . . .2-16 Agent Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .2-17 Save Installation Files Dialog Box . . . . . . . . . . . . . . . . . . . . . . .2-18 User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .2-18 Operation Progress Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .2-19 Operation Status Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20 Next Steps Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-21 Knowledge Module Installation Destination Dialog Box . . . . . .2-25 Knowledge Module Destination Instructions Dialog Box . . . . .2-26 PATROL Products Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .2-26 Next Steps Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-32 PATROL products path selection Text . . . . . . . . . . . . . . . . . . . .3-6 PATROL Installation Instructions Dialog Box . . . . . . . . . . . . . .3-6 Installation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7 Installation Operations Dialog Box . . . . . . . . . . . . . . . . . . . . . . .3-8 PATROL Products Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .3-9 Advanced Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .3-10 Select Hosts Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11 User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .3-12 Destination Location Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .3-13 Destination Directory Matrix Dialog Box . . . . . . . . . . . . . . . . . .3-14 Account Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .3-14 PATROL Username/Password Matrix Dialog Box . . . . . . . . . . .3-15 Save Installation Files Dialog Box . . . . . . . . . . . . . . . . . . . . . . .3-16 User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .3-16 Operation Progress Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .3-17 Operation Status Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18 Next Steps Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19 Knowledge Module Installation Destination Dialog Box . . . . . .3-23 Knowledge Module Destination Instructions Dialog Box . . . . .3-24 PATROL Products Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .3-24 Next Steps Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30 The PATROL Products Dialog Box . . . . . . . . . . . . . . . . . . . . . . .4-3 The Advanced Options-Operating Systems Dialog Box . . . . . . .4-4 The PATROL Products Dialog Box . . . . . . . . . . . . . . . . . . . . . . .4-5 PATROL Product set selection Text . . . . . . . . . . . . . . . . . . . . . .4-8 Installation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9 Installation Operations Dialog Box . . . . . . . . . . . . . . . . . . . . . . .4-9
BMC Software, Inc., Confidential and Proprietary Information
viii
Figure 4-7 Figure 4-8 Figure 4-9 Figure 4-10 Figure 4-11 Figure 4-12 Figure 4-13 Figure 4-14 Figure 4-15 Figure 4-16 Figure 4-17 Figure 4-18 Figure 4-19 Figure 4-20 Figure 4-21 Figure 4-22 Figure 4-23 Figure 4-24 Figure 4-25 Figure 4-26 Figure 4-27 Figure 4-28 Figure 4-29 Figure 4-30 Figure 4-31 Figure 4-32 Figure 4-33 Figure 5-1 Figure 5-2 Figure 8-1 Figure 8-2 Figure 8-3 Figure 8-4 Figure 8-5 Figure 8-6 Figure 8-7 Figure 8-8 Figure 8-9 Figure 8-10
The Select Hosts Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 4-11 The Replicate Path Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 The Destination Location Dialog Box . . . . . . . . . . . . . . . . . . . . 4-13 Destination Directory Matrix Dialog Box . . . . . . . . . . . . . . . . . 4-14 The Account Information Dialog Box . . . . . . . . . . . . . . . . . . . . 4-14 PATROL Username/Password Matrix Dialog Box . . . . . . . . . . . 4-15 Root Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15 PATROL Root Password Matrix Dialog Box . . . . . . . . . . . . . . . 4-16 Agent Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 The Save Installation Files Dialog Box . . . . . . . . . . . . . . . . . . . 4-18 The User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . 4-18 The Operation Progress Dialog Box . . . . . . . . . . . . . . . . . . . . . . 4-19 The Operation Status Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 4-20 Next Steps Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21 PATROL Product set selection Text . . . . . . . . . . . . . . . . . . . . . . 4-24 The Installation Setup Dialog Box . . . . . . . . . . . . . . . . . . . . . . . 4-25 The Installation Operations Dialog Box . . . . . . . . . . . . . . . . . . . 4-26 The Select Hosts Dialog Box (Remote Installation Only) . . . . . 4-27 User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 4-28 The Destination Location Dialog Box . . . . . . . . . . . . . . . . . . . . 4-29 The Account Information Dialog Box . . . . . . . . . . . . . . . . . . . . 4-30 The PATROL Username/Password Matrix Dialog Box . . . . . . . 4-31 The Save Installation Files Dialog Box . . . . . . . . . . . . . . . . . . . 4-31 The User Encryption Key Dialog Box . . . . . . . . . . . . . . . . . . . . 4-32 The Operation Progress Dialog Box . . . . . . . . . . . . . . . . . . . . . . 4-33 The Operation Status Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 4-34 PATROL Identification Dialog Box . . . . . . . . . . . . . . . . . . . . . . 5-8 PATROL License Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 Starting PATROL Installation with the following pathnames Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Accept License Terms Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6 Installation Operations Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 Product Selection Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9 Main Product List Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10 PATROL Agent Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10 Main Product List Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 Product Selection Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 Override OS Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13 Destination Directory Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Figures
ix
Figure 8-11 Figure 8-12 Figure 8-13 Figure 8-14 Figure 8-15 Figure 8-16 Figure 8-17 Figure 8-18 Figure 8-19 Figure 8-20 Figure 8-21 Figure 8-22 Figure 8-23 Figure 8-24 Figure 8-25 Figure 8-26 Figure 8-27 Figure 8-28 Figure 8-29 Figure 8-30 Figure 8-31 Figure 8-32 Figure 8-33 Figure 8-34 Figure 8-35 Figure 8-36 Figure 8-37 Figure 8-38 Figure 8-39 Figure 8-40 Figure A-1 Figure A-2 Figure A-3 Figure A-4
Destination Directory Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-15 Account Information Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-15 Account Information Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-16 Root Password Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-16 Root Password Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-17 Agent Startup Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-18 Port Override Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-18 Optional Command File Selection Text . . . . . . . . . . . . . . . . . . .8-19 Install Status Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-19 Product Selection Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-22 Main Product List Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-23 PATROL Knowledge Module Text . . . . . . . . . . . . . . . . . . . . . . .8-23 Product Selection Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-24 Override OS Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-25 Destination Directory Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-26 Destination Directory Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-27 Account Information Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-27 Account Information Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-28 Root Password Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-29 Optional Command File Selection Text . . . . . . . . . . . . . . . . . . .8-30 Install Status Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-30 Destination Directory Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-32 Destination Directory Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-33 Account Information Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-34 Root Password Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-35 Port Override Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-35 Optional Command File Selection Text . . . . . . . . . . . . . . . . . . .8-36 Install Status Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-36 Command File Selection Text . . . . . . . . . . . . . . . . . . . . . . . . . . .8-40 Install Status Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-40 $PATROL_HOME Directories and Files . . . . . . . . . . . . . . . . . A-6 $HOME/patrol Directories and Files . . . . . . . . . . . . . . . . . . . . . A-9 /tmp/patrol Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 PATROL3.3KMDS Directory Structure . . . . . . . . . . . . . . . . . . A-12
Tables
Tables
Table 1-1 Table 5-1 Table 5-2 Table 6-1 Table A-1 Table A-2 Table A-3 Table C-1 Table C-2 Table D-1 Table D-2 CPU and Operating System Version Requirements (Part 1 of 2) 1-6 Tasks for Setting Up PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 PATROL License Dialog Box Entry Fields . . . . . . . . . . . . . . . . 5-14 histool Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . 6-3 Summary of PATROL Main Directories . . . . . . . . . . . . . . . . . . A-3 PATROL Console File Usage (Part 1 of 2) . . . . . . . . . . . . . . . A-4 PATROL Agent File Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Command Line Options for the Graphics-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2 Command Line Options forText-Based Installation Program C-4 Requirements and Troubleshooting Tips for the Installation Program D-4 Sample logfile<pid> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
Tables
xi
xii
About . . .
This book assumes that you are familiar with your host operating system. You should know how to perform basic actions in a window environment, such as choosing menu commands and dragging and dropping icons.
xiii
xiv
Chapter/ Appendix 1 2
Title
PATROL Installation Introduction Installing the PATROL Agent, PATROL Console, and PATROL KMs Installing the PATROL KMDS and PATROL KMs Replicating and Uninstalling PATROL Products Configuring, Starting, and Licensing PATROL Upgrading from a Prior Version of PATROL Installing the Documentation and the Help System Installing PATROL Using the Text-Based Installation Program The PATROL Products Files and Directories on the Disk Drive Using PATROL with Firewalls
Description
identifies issues you should consider before beginning the PATROL installation. presents instructions that allow you to install the PATROL for Unix core products (PATROL Agent, Console and PATROL KMDS). presents instructions that allow you to install the PATROL OS and application KMs to the PATROL Agent, Console and PATROL KMDS. presents instructions for uninstalling and replicating PATROL products. presents instructions for starting and setting up the PATROL Agent, PATROL Console for Unix, and PATROL KM for Unix. PATROL license information is also provided. presents information on upgrading PATROL from a previous version. presents information on installing PATROL help system products. presents information on installing PATROL using the text based installation script. provides information for system administrators to use periodically for managing the PATROL files.
discusses some approaches a system administrator might take to implement PATROL in an environment that uses firewall security.
xv
Chapter/ Appendix C
Title
Using Installation Program Command Line Options Installation Troubleshooting
Description
provides information about command line options you can use when starting the installation program. presents information on the most common error messages and suggests solutions for problem resolution.
Related Documentation
BMC Software products offer several types of documentation: online and printed books release notes
You can access online books from the documentation compact disc (CD) that accompanies your product or from the World Wide Web.
xvi
Online books are formatted as Portable Document Format (PDF) files. You can view them, print them, or copy them to your computer by using Acrobat Reader 3.0 or later.
Note
In some cases, installation of Acrobat Reader and downloading the online books is an optional part of the product-installation process. For information about downloading the free reader from the Web, go to the Adobe Systems site at http://www.adobe.com. For information about installing the reader from the documentation CD, see the readme.txt file on the CD.
Accessing Books on the Web
To access any online book that BMC Software offers, visit the support page of the BMC Software Web site at http://www.bmc.com/support.html.
Note
To use the support page, you must be a registered user or have a temporary user name and a password. If you are a registered user, proceed as follows: 1. Click Log in to Support. 2. Enter your user name and password. 3. To view books for a particular product, click the product name in the Product Directory. 4. Select the book that you want to view.
xvii
If you are not a registered user, choose one of the following options: To register, click Request UserID, complete the form, and click Send
Request.
To request a temporary user name and a password, contact your BMC Software sales representative.
BMC Software provides a core set of printed books with your product order. To request additional books, go to http://www.bmc.com/support.html.
Release Notes
Printed release notes accompany each BMC Software product. Release notes provide up-to-date information such as updates to the installation instructions last-minute product information
The latest versions of the release notes are also available on the Web at http://www.bmc.com/support.html.
Conventions
The following conventions are used in this book: This book includes special elements called notes:
Note
xviii
All syntax, operating system terms, and literal examples are presented in this typeface. In instructions, boldface type highlights information that you enter. File names, directories, and Web addresses also appear in boldface type. The symbol => connects items in a menu sequence. For example, Actions => Create Test instructs you to choose the Create Test command from the Actions menu. The symbol
In syntax, path names, or system messages, italic text represents a variable, as shown in the following examples: The table table_name is not available.
system/instance/file_name
In syntax, the following additional conventions apply: A vertical bar ( | ) separating items indicates that you must choose one item. In the following example, you would choose a, b, or c: a | b | c An ellipsis ( ) indicates that you can repeat the preceding item or items as many times as necessary. Square brackets ( [ ] ) around an item indicate that the item is optional.
xix
The following table shows equivalent mouse buttons for Unix users and Windows NT users:
Unix Button
MB1
Windows NT Button
left mouse button
Description
Click this button on an icon or menu command to select that icon or command. Click MB1 on a command button to initiate action. Double-click an icon to open its container. Click this button on an icon to display the InfoBox for the icon. To simulate MB2 on a two-button mouse, simultaneously press the two buttons (MB1 and MB3). Click this button on an icon to display its pop-up menu.
MB2
not applicable
MB3
Note
If you have a one-button mouse (such as an Apple Macintosh mouse), assign MB1 to that button. You should also define a user-selectable combination of option and arrow keys to simulate MB2 and MB3. For details, refer to the documentation for your emulation software.
xx
1
1 1
This chapter presents information you need for planning the installation of the PATROL products in your environment and for starting the installation program. It contains the following topics. PATROL Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Installation and Operation Requirements . . . . . . . . . . . . . . . . . . . . . . 1-4 Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 CPU and Operating System Requirements . . . . . . . . . . . . . . . . . 1-6 PATROL Console Memory Requirements. . . . . . . . . . . . . . . . . . 1-7 PATROL Console Display Requirements . . . . . . . . . . . . . . . . . . 1-7 Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 PATROL Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 GNU Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 Upgrading to a New Version of PATROL . . . . . . . . . . . . . . . . . . . . . 1-9 Methods for Installing PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 Installing a Patch for PATROL Products . . . . . . . . . . . . . . . . . . . . . . 1-10 Overview of Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 Installation Program Record Files . . . . . . . . . . . . . . . . . . . . . . . . 1-13 Navigating Within the Installation Program . . . . . . . . . . . . . . . . 1-14 Password Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 Saving Product and Host Files. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Quitting the Installation Program. . . . . . . . . . . . . . . . . . . . . . . . . 1-15 Starting the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 Preparing to Install PATROL Products . . . . . . . . . . . . . . . . . . . . 1-18
BMC Software, Inc., Confidential and Proprietary Information
1-1
Starting the Installation Program with CD1 for Unix . . . . . . . . .1-23 Starting the Installation Program with CD2 for Unix . . . . . . . . .1-31
1-2
PATROL Architecture
PATROL is a tool for monitoring and managing computer systems and applications. It provides an object-oriented graphical workspace where you can view the status of vital resources in the distributed environment that you are managing. PATROL can be installed on multiple computers. Before you can begin planning the PATROL installation, you must understand the PATROL components; then you can decide where to install them. Not all components can be installed on all platforms. PATROL consists of the following components: PATROL Agent PATROL Console PATROL Knowledge Modules (KMs) PATROL Knowledge Module Deployment Server (KMDS) PATROL Event Manager (PEM)
A brief description of each component follows. For detailed information about the PATROL components and their activities, see the user guides and reference manuals for each. A PATROL Agent must be installed on every computer that you want to monitor, whether you want to monitor the computer itself or an application running on the computer. The PATROL Console is the interface that you use to communicate with the PATROL Agent and to monitor the information provided by the agents. The console can be installed only on a computer that uses Windows NT or certain versions of Unix as its operating system. The PATROL Knowledge Modules provide the specific information that the PATROL Agents and Consoles use to monitor computer systems and applications. The PATROL Agent must have PATROL KMs for the operating system of the computer that it is installed on and for each application that it is monitoring on that computer. The PATROL Console must have the same PATROL KMs loaded as each PATROL Agent that it is monitoring.
BMC Software, Inc., Confidential and Proprietary Information
PATROL Architecture
1-3
The PATROL KMDS serves as a central repository for PATROL Knowledge Module (KM) version control and migration and as a point from which you can manage PATROL KMs loaded on Unix and Windows NT computers. The PATROL KMDS can be installed only on a computer that uses Windows NT or certain versions of Unix as the operating system. The PATROL Event Manager (PEM) can work by itself or with a PATROL Console to display event information, generate event statistics, and otherwise manage events. The PATROL Event Manager can be installed only on a computer that uses Windows NT or certain versions of Unix as the operating system. For more detailed information about the PATROL components and the functions of each, see the PATROL Agent Reference Manual, the PATROL for Unix User Guide, the PATROL for Windows NT User Guide, and the PATROL Knowledge Module Deployment Server Manager User Guide.
1-4
PATROL configuration requires privileges usually reserved by the system administrator. These privileges include access to a root account on the hardware where PATROL will reside. During the installation process, you will be asked for account names and passwords for the hardware that you want to install PATROL on.
Note
Do not use the root account as either the account you use to perform the installation nor the PATROL user account.
Note
The computers you want to install PATROL on must have ftp and telnet enabled. If your environment uses a firewall system for security, consult Appendix B, Using PATROL with Firewalls, for more information.
Platform Requirements
Although the PATROL Consoles and Agents can operate on a variety of platforms including Unix, OS/2, OS/390, OpenVMS, and Windows NT, the installation programs are platformspecific. This means that you must use the Windows NT installation program to install PATROL Consoles, Agents, and KMs on Windows NT hardware. You must use the Unix installation program to install PATROL Consoles, Agents, and KMs on Unix hardware. The PATROL KMDS can be installed on either a Unix or Windows NT platform.
1-5
Each PATROL Console requires about 20 MB of disk space. The Console also requires an additional 31 MB of disk space for the supporting files including online help files. Each PATROL Agent requires from 20 to 30 MB of disk space, depending on the platform it is installed on. Each PATROL Event Manager (PEM) Console requires about 5 MB of disk space. If the PEM Console is installed independently of the PATROL Console, then an additional 24 MB of disk space is required for the supporting files. The PATROL KMDS requires approximately 20 MB of disk space. PATROL Knowledge Module space requirements vary. They range in size from about 250 KB to over 5 MB. If you use the PATROL KMDS, the KMs installed into the PATROL KMDS require the same amount of disk space as the KMs installed on agent and console computers.
Hardware CPU
DEC Alpha DEC Alpha HP 9000/700 HP 9000/800
Operating System
DEC UNIX DEC UNIX HP-UX HP-UX
Supported Versions
3.0 4.0 10.20 10.20
Comments
1-6
Table 1-1
Hardware CPU
HP 9000/700 HP 9000/800 IBM RS/6000 IBM RS/6000 Sun SPARC Siemens Nixdorf
Operating System
HP-UX HP-UX AIX AIX Solaris2 SINIX
Supported Versions
11.0 11.0 4.1, 4.2, 4.3 4.3 2.5.1, 2.6, 7 5.4.2, 5.4.3 64 bit 64 bit
Comments
1-7
32 MB minimum system RAM; 48 MB are recommended if you are running other X applications or Windows applications simultaneously with the PATROL Console.
Note
The PATROL for Windows NT Installation Guide describes the requirements for the PATROL for Windows NT Console and Agent products.
Network Requirements
PATROL requires TCP/IP network communications. In addition, ftp and telnet must be enabled on the computers you want to install PATROL on for both local and remote installations. BMC Software recommends that you install PATROL on local partitions, not NFS-mounted partitions. If you do install PATROL on NFS-mounted partitions, the root account must have been granted root access privileges on the NFS server.
PATROL Licensing
The PATROL products are installed with a 30-day demonstration license. In order to use the PATROL Agent or Console after 30 days, you must either extend the demonstration license or install a permanent license. See Supplying License Information on page 5-12.
GNU Notification
The distribution CD-ROMs contain compiled binaries for GNU gzip and df. Source for these programs is available from the GNU archive (prep.ai.mit.edu or www.gnu.ai.mit.edu) or one of its mirrors.
1-8
If you have an existing PATROL environment that you have customized, please refer to the PATROL Migration Tools User Guide for important information on steps you should take before you install the newest version of PATROL.
1-9
An installation program with a graphical user interface. This installation program is available for the Unix systems listed in Table 1-1, CPU and Operating System Version Requirements, on page 1-6. The PATROL Console, PATROL KMDS, and PATROL Agent are supported on these systems. Most of the chapters in this book discuss this installation program. Except in Chapter 8, the term installation program refers to the installation program with a graphical user interface. An installation program with a text user interface. The text-based installation program is available for the Unix operating systems listed in CPU and Operating System Requirements for the Text-Based Installation Program on page 8-2. The PATROL Agent is supported on these systems, but the PATROL Console and PATROL KMDS are not. See Chapter 8, Installing PATROL Using the Text-Based Installation Program, for more information on using the text-based installation program.The term text-based installation program refers to this installation program. In Chapter 8, the term installation program refers to the text-based installation program.
1-10
You must install the PATROL products in the following order. If you do not want to install the PATROL Knowledge Module Deployment Server, skip Steps 3 and 4. 1. PATROL Agents and Consoles from CD1 for Unix. See Chapter 2, Installing the PATROL Agent, PATROL Console, and PATROL KMs for more information. 2. PATROL KMs to Agents and Consoles from CD2 for Unix. See Chapter 2, Installing the PATROL Agent, PATROL Console, and PATROL KMs for more information. 3. PATROL KMDS from CD1 for Unix. See Chapter 3, Installing the PATROL KMDS and PATROL KMs for more information. 4. PATROL KMs to the PATROL KMDS from CD2 for Unix. Chapter 3, Installing the PATROL KMDS and PATROL KMs for more information. You can use the installation program to install the PATROL products on your local computer as well as on remote computers. You can also install PATROL products in one location, customize the installed products, and then replicate the customized products to remote computers. The installation program can be used to move files from the distribution media load the agent KMs configure agents
1-11
start the agents replicate an existing PATROL installation uninstall PATROL products
Before you can monitor applications and systems with PATROL, you must start a PATROL Console and perform a number of other steps. Basic information about these steps is available in Chapter 5, Configuring, Starting, and Licensing PATROL. More complete information about these procedures is available in the PATROL for Unix Getting Started manual and the PATROL for Unix User Guide. You can use the installation program to perform either a local installation, on the computer you are currently logged in on, or a network installation, on computers that are connected to your local computer by a network. The installation program allows you to install the products on multiple computers all at one time, including your local computer. The installation program can save the list of hosts you install to and lists of specific products you install. You can use these lists in subsequent installation operations to select to the same hosts or the same products. The network installation is very similar to the local installation, so the instructions for both are included in most of the procedures in this manual. Whenever different steps are required for a local or network computer, the instructions explain which steps are applicable. In some cases, the installation steps are different enough that there is a separate procedure for a local installation and a network installation. The PATROL products have different executable files for different operating systems. The installation program automatically detects the operating system present on the computers you are installing to. The installation program selects and installs the correct files for that system. If you want, you can override the automatic selection and specify which executable files will be installed on the computers.
1-12
The prodlists subdirectory contains files listing the PATROL products installed during one pass through the installation program. See Saving Product and Host Files on page 1-15 for more information. The hostlists subdirectory contains files listing the hosts that the installation program installed PATROL products on during one pass through the installation program. See Saving Product and Host Files on page 1-15 for more information. The batchfiles subdirectory contains files used by the installation program.
1-13
Password Encryption
From time to time, the installation program may ask you for an account password or for the root password. When you type this information, the installation program immediately encrypts it so the correct characters of the password are never displayed in clear text on the screen.
1-14
1-15
Figure 1-1
If you click OK the installation program exits without installing any PATROL products. If you click Cancel in the Abort Install dialog box, the installation program returns to the dialog box you were in. If you are in the Operation Progress dialog box and you click Cancel, the program displays a different Abort Install dialog box, shown in Figure 1-2.
Figure 1-2 Abort Install Dialog Box
If you click OK in this dialog box, the installation program exits immediately without installing any more PATROL products. If you abort during an installation process, the installation may be left in an unknown state. Usually, restarting the installation program and allowing it to run to completion is enough for any needed cleanup and for a successful installation. If you click Cancel in this dialog box, the installation program returns to the Operation Progress dialog box and continues the installation.
1-16
1-17
Log on
No
Yes
You must know which PATROL products can be installed at your site before you begin to install PATROL. This information is in your licensing agreement. To prepare to install PATROL products, you must Mount the CD Create a PATROL user account Set the umask setting
BMC Software, Inc., Confidential and Proprietary Information
1-18
BMC Software recommends that the account you use to install the PATROL products meet the following conditions: The preferred login shell is a Bourne shell. A Korn shell or a C shell is acceptable, but other shells may cause problems in the installation. The account .profile and .cshrc files should contain as little user customization as possible. Specifically, there should be no aliases, the prompt should be set to the default, and there should be no command in these files to change the umask setting. Do not use root to install PATROL products. Be sure the account has permission to create directories in the directory where you will install PATROL products.
In this procedure, the CD-ROMs root directory is called /cdrom. This directory might be different for your computer, depending on how your system administrator has configured the device. If you have a question about the location or setup of your CD-ROM, please contact your system administrator.
Step 1 Step 2 Step 3
Log on as root. Insert the CD-ROM into the CD-ROM drive. Use the mount command appropriate to your platform to mount the CD-ROM drive.
1-19
Platform
AIX Digital UNIX HPUX-PA1.0 Version 10.20 or higher SINIX Solaris IRIX Sequent SCO 5.0
Mount Command
mount -r -v cdrfs /dev/cd0 /cdrom mount -r -t cdfs -o rrip,noversion,nodefperm /dev/rz4c /cdrom mount -F cdfs -o ro /dev/dsk/<drive for cdrom>/cdrom or mount -F cdfs -o ro,cdcase /dev/dsk/<drive for cdrom>/cdrom mount -F cdfs -o ro /dev/ios0/rsdisk00650 Volume Manager (/usr/sbin/vold) automatically mounts. Otherwise, mount -r -F hsfs /dev/sr0 /cdrom Volume Manager automatically mounts mount_cdfs /dev/dsk/cd1 mount -f RCKRDG /dev/cd1 /cdrom
If a problem occurs, consult your system administrator or read the man page for mount.
Step 4
Log off.
You must have exported the CD-ROM file system so that it can be mounted by NFS clients. Almost all platforms use the exportfs command to export a local file system, including a CD-ROM file system. Solaris computers use the share command.
Step 1 Step 2
Logon as root. Create a directory on your local computer (for example, /mnt/cdrom or /mnt/cdrom/cdrom0 for Solaris) as the mount point for the CD-ROM on the remote host computer.
Step 3
Mount the CD-ROM using the command appropriate for your platform.
1-20
Mount Command
mount <host>:/cdrom /mnt/cdrom mount <host>:/cdrom/cdrom0 /mnt/cdrom/cdrom0 mount -F nfs <host>:/cdrom /mnt/cdrom
If a problem occurs, consult your system administrator or read the man page for mount if the command does not work.
Step 4
Logoff.
Logon as the account that will perform the installation. Create a user account for PATROL. (BMC Software recommends the user account be named patrol.)
To Finalize the Preparations Step 1
Set the umask setting to 022 for the account performing the PATROL installation. The umask command is used to specify read-write permissions to be turned off. Type the following command:
BMC Software recommends only using 022 as the umask value. Other umask settings such as 027 may introduce problems when executing PATROL from other accounts in the PATROL group.
Step 2
Insert the appropriate CD-ROM into the CD-ROM drive and do one of the following:
1-21
If the product CD-ROM is in a CD-ROM drive your computer can access, go to Step 3 on page 1-22. Telnet to a host with the mounted PATROL product CD-ROM.
Note
If you telnet to another system, you will have to reset the umask value on the system described in Step 1 on page 1-21.
Step 3
Change your working directory to the root of the CD-ROM. For example, type the following command and press Enter:
cd /cdrom
See...
Starting the Installation Program with CD1 for Unix on page 1-23 Starting the Text-Based Installation Program on page 8-5
1-22
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. For a local installation, you must use the PATROL user account to perform the installation.
To Start the Installation Program with CD1 for Unix Step 1
Refer to the following table for the more common startup command line options. See Appendix C, Using Installation Program Command Line Options, for more information about these and other command line options.
1-23
Warning For AIX Users: On certain versions of the AIX operating system, the
nslookup operation has a security issue. To avoid this problem, use the -nonslookup command line option or see the IBM Global Services Emergency response service number ERS-SVA-E01-1997:008.1 for information about a patch. The installation program prompts you for the products you want to install. See Figure 1-3.
Figure 1-3 PATROL product set selection Text
Step 2 Step 3
Type the number for the products you are installing and press Enter. Perform the step that applies to you. If the DISPLAY environment variable has been set for your system, go to Step 4 on page 1-25. If the DISPLAY environment variable is not set on your system, the installation program prompts you for the value to use. See Figure 1-4.
BMC Software, Inc., Confidential and Proprietary Information
1-24
Figure 1-4
Do one of the following: To accept the default, press Enter. To specify a different value for the DISPLAY variable, type the new value and press Enter.
Step 4
Perform the step that applies to you. If you specified either -nslookup or -nonslookup in the command line, go to Step 5 on page 1-26. If you did not specify either -nslookup or -nonslookup in the command line, the installation program asks you whether you want to run nslookup to find the hosts on your system. See Figure 1-5.
Populate hostlist with nslookup Text
Figure 1-5
1-25
If you do not want the installation program to run nslookup, type 1 and press Enter. If you choose this option, the installation program will not determine the hosts available on your system. If you want to perform a remote installation, at a later step you will have to specify the host names to install to rather than select them from a list. The installation program starts faster if you choose 1. If you want the installation program to run nslookup, type 2 and press Enter. If you choose this option, the installation program will determine the hosts available on your system. If you want to perform a remote installation, at a later step the installation program will present a list of available hosts so you can select the hosts to install to. Depending on the size of your system, there may be a delay in starting the installation program if you choose 2.
The installation program asks you to specify the path name of the location of the PATROL products you want to install. The path to CD1 is given as the default. See Figure 1-6.
Figure 1-6 PATROL products path selection Text
Step 5
Do one of the following: To accept the default, press Enter. To specify a different directory, type the complete path to the directory you want and press Enter.
1-26
The installation program asks you to specify the path name of the location where you want the program to store log files and list files. The default is the patrolinstall directory within the home directory of the installation account. See Figure 1-7. The specified directory will be created if it does not exist.
Figure 1-7 PATROL Installation log file path selection Text
Step 6
Do one of the following: To accept the default, press Enter. To specify a different directory, type the complete path to the directory you want and press Enter.
The installation program displays the specified path names. See Figure 1-8 on page 1-27.
Figure 1-8 Starting PATROL Installation with the following pathnames Text
Step 7
Do one of the following: If the path names are not correct, press any key except Enter. The installation program returns to Step 5 on page 1-26. If the path names are correct, press Enter.
1-27
The Welcome dialog box appears. After the Welcome dialog box, you will see the Installation Initialization dialog box. When the installation program has finished initializing, the PATROL License Agreement dialog box appears.
Step 8
Read the agreement and click Accept to accept the License Agreement. The PATROL Installation dialog box appears.
Step 9
Click Continue to continue the installation. The PATROL Installation Instructions dialog box appears to describe the steps involved in installing PATROL 3.3. The appearance of the PATROL Installation Instructions dialog box depends on the products you are installing (your response to Step 2 on page 1-24). Figure 1-9 shows the dialog box when you are installing PATROL Agents, Consoles, and associated products.
Note
Be sure to pay special attention to the order in which you must install each component. This is very important in ensuring that PATROL will function properly when you start it.
1-28
Figure 1-9
Step 10
Review the steps involved in installing PATROL products, then click Next to continue. The Installation Setup dialog box appears as shown in Figure 1-10.
Figure 1-10 Installation Setup Dialog Box
1-29
See...
Installing PATROL Agents and Consoles on page 2-4 Installing the PATROL KMDS on page 3-4 Uninstalling PATROL Products on page 4-23 Replicating PATROL Products to Remote Computers on page 4-7
1-30
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. For a local installation, you must use the PATROL user account to perform the installation.
To Start the Installation Program with CD2 for Unix Step 1
Refer to the following table for the more common startup command line options. See Appendix C, Using Installation Program Command Line Options, for more information about these and other command line options.
1-31
Then Type...
-nonslookup -nslookup -wingeometry override or
-wingeometry 500x300+10+10 Warning For AIX Users: On certain versions of the AIX operating system, the
nslookup operation has a security issue. To avoid this problem, use the -nonslookup command line option or see the IBM Global Services Emergency response service number ERS-SVA-E01-1997:008.1 for information about a patch.
Step 2
Perform the step that applies to you. If the DISPLAY environment variable has been set for your system, go to Step 3 on page 1-33. If the DISPLAY environment variable is not set on your system, the installation program prompts you for the value to use. See Figure 1-11.
Do one of the following: To accept the default, press Enter. To specify a different value for the DISPLAY variable, type the new value and press Enter.
1-32
Step 3
Perform the step that applies to you. If you specified either -nslookup or -nonslookup in the command line, go to Step 4 on page 1-34. If you did not specify either -nslookup or -nonslookup in the command line, the installation program asks you whether you want to run nslookup to find the hosts on your system. See Figure 1-12.
Do one of the following: If you do not want the installation program to run nslookup, type 1 and press Enter. If you choose this option, the installation program will not determine the hosts available on your system. If you want to perform a remote installation, at a later step you will have to specify the host names to install to rather than select them from a list. The installation program starts faster if you choose 1. If you want the installation program to run nslookup, type 2 and press Enter. If you choose this option, the installation program will determine the hosts available on your system. If you want to perform a remote installation, at a later step the installation program will present a list of available hosts so you can select the hosts to install to. Depending on the size of your system, there may be a delay in starting the installation program if you choose 2.
1-33
The installation program asks you to specify the path name of the location of the PATROL products you want to install. The path to CD2 is given as the default. See Figure 1-13.
Figure 1-13 PATROL products path selection Text
Step 4
Do one of the following: To accept the default, press Enter. To specify a different directory, type the complete path to the directory you want and press Enter.
The installation program asks you to specify the path name of the location where you want the program to store log files and list files. The default is the patrolinstall directory within the home directory of the installation account. See Figure 1-14 on page 1-34.
Figure 1-14 PATROL Installation log file path selection Text
Step 5
Do one of the following: To accept the default, press Enter. To specify a different directory, type the complete path to the directory you want and press Enter.
BMC Software, Inc., Confidential and Proprietary Information
1-34
The installation program displays the specified path names. See Figure 1-15.
Figure 1-15 Starting PATROL Installation with the following path names Text
Step 6
Do one of the following: If the path names are not correct, press any key except Enter. The installation program returns to Step 5 on page 1-26. If the path names are correct, press Enter.
The Welcome dialog box appears. After the Welcome dialog box, you will see the Installation Initialization dialog box. When the installation program has finished initializing, the PATROL License Agreement dialog box appears.
Step 7
Read the agreement and click Accept to accept the License Agreement. The Installation Setup dialog box appears as shown in Figure 1-16.
1-35
See...
Installing PATROL KMs to Agent and Console Computers on page 2-23 Installation of PATROL KMs to the PATROL KMDS on page 3-21
1-36
2-1
Overview
This chapter describes the installation of the PATROL Agent, PATROL Console, and PATROL KMs for the agent and console computers. You use PATROL for Unix CD1 and CD2 to complete this operation. The installation program takes you through each step of the installation, whether you are making a local or a remote installation. A local installation occurs when you install the PATROL products on the computer you are currently logged on. A remote installation is when you install the PATROL products on computers that are accessible to your local computer. (Your local computer is the computer you are currently logged on.) The installation program allows you to specify the products that you want to install and the remote computers you want to install on at one time. The remote installation is very similar to the local installation. The procedures in this chapter cover both remote and local installations. When a particular step applies only to one type of install, it is clearly marked.
Note
If you choose to use the PATROL KMDS in your environment, you must complete the installation procedures in this chapter, then proceed to Chapter 3, Installing the PATROL KMDS and PATROL KMs to complete the installation.
2-2
2-3
Yes
a remote installation?
Yes
Choose the files to save the product list and the host list Yes
No
2-4
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You must have completed the procedures described in Starting the Installation Program with CD1 for Unix on page 1-23. You should be familiar with the information in Navigating Within the Installation Program on page 1-14. The computers you want to install PATROL on must have ftp and telnet enabled. Be sure you are using CD1 for Unix to do this procedure. If you are installing a patch, you must stop any PATROL processes that are running on the computers you want to install the patch on.
Follow the instructions in Starting the Installation Program with CD1 for Unix on page 1-23. When the installation program prompts you for the products you want to install, type 1 and press Enter. See Figure 2-1.
Figure 2-1 PATROL products path selection Text
Step 2
Continue the steps as described in the Starting the Installation Program with CD1 for Unix procedure.
2-5
When you have completed the procedure, the Installation Setup dialog box appears as shown in Figure 2-2.
Figure 2-2 Installation Setup Dialog Box
Step 3
Do one of the following: Select Local to install PATROL to the computer you are currently using and click Next. Select Remote to install PATROL to specified remote computers in your environment and click Next. You may also install PATROL to your local computer at the same time.
2-6
Figure 2-3
The options available on the Installation Operations dialog box depend on whether you chose Local or Remote in the Installation Setup dialog box. Replicate PATROL and Distribute PATROL are only displayed if you chose Remote on the Installation Setup dialog box.
Note
Distribute PATROL is used with the PATROL KMDS. For more information on this option, consult the PATROL Knowledge Module Deployment Server Manager User Guide.
Step 4
Select Install PATROL and click Next. The PATROL Products dialog box appears as shown in Figure 2-4 on page 2-8.
2-7
Figure 2-4
Step 5
Select the products you want to install by clicking on the box or double clicking on the product category to expand each product list and then selecting the check box by the product name. As you select products, the installation program updates the Estimated space required field. This field shows approximately how much space is required to install the products you have selected. To use a saved list of products from a previous installation, click Load and select the file that contains the list you want to use. Ordinarily, the installation program automatically selects the appropriate version of the program files to install, based on the operating system of the computers you want to install to. Click Advanced to override the installation programs automatic selection. Specify the operating system or systems from the Advanced Options dialog box and click OK to close the dialog box.
2-8
Figure 2-5
When you have selected all the products you want to install, click Next. The dialog box you see next depends on whether you are doing a local or remote installation. For a local installation, the Destination Location dialog box appears as shown in Figure 2-8 on page 2-12. For a remote installation, the Select Hosts dialog box appears as shown in Figure 2-6 on page 2-10. If you used the -nslookup option when you started the installation program, the Host Choices pane contains a list of host computers on your system. See Starting the Installation Program with CD1 for Unix on page 1-23 for more information about -nslookup. There may be a short delay while the host list loads.
2-9
Figure 2-6
Step 7
Perform the step that applies to you. For a local installation, proceed to Step 10 on page 2-12. For a remote installation, proceed to Step 8 on page 2-10.
Step 8
For a remote installation, select the host computers you want to install PATROL on from the Select Hosts dialog box, using one of the methods below. Click the computer name in the Host Choices pane. This method is available only if you used the -nslookup option when you started the installation program. Click Add Host and type the host name of the computer in the addhost dialog box, then click OK to close the dialog box. If you want to use a list of computers saved during a previous installation, click Load and select the file. After you select the file, the User Encryption Key dialog box appears as shown in Figure 2-7 on page 2-11. Type and verify the decryption key for the host file. Then click OK.
2-10
Figure 2-7
If you do not type the key that was used to encrypt the file, you cannot open the file. Whichever method you use to select the hosts, the computers you select are listed in the Hosts Selected pane of the Select Hosts dialog box.
Note
If you select a computer in error, click its name in the Hosts Selected pane. The installation program removes it from the list of selected hosts.
Step 9
When you are finished selecting computers, click Next. The Destination Location dialog box appears as shown in Figure 2-8 on page 2-12.
2-11
Figure 2-8
Step 10
Use one of the following methods to choose the directory for PATROL products. To accept the default directory as PATROL3.3, click Next. Type the directory name in this dialog box and click Next. If you are performing a remote installation and want to enter destination directory locations for multiple hosts, click Advanced to display the PATROL Destination Directory Matrix as shown in Figure 2-9. Enter the path name for each directory next to the name of the host, then click OK in the PATROL Destination Matrix dialog box. Click Next in the Destination Location dialog box when you are finished.
2-12
Figure 2-9
Step 11
Use one of the following methods for entering user names and passwords.
2-13
Type the information on the PATROL user account in each entry box, then click Next. Use this method for local installations and for remote installations where the account names and passwords are the same for all host computers.
Note
For a local installation, the user name and password must be the same as the account that you used to start the installation program. If you are doing a remote installation and the user names and passwords are different for each host, click Advanced to display the PATROL Username/Password Matrix dialog box as shown in Figure 2-11. Type the user name and password for each host, then click OK to close the PATROL Username/Password Matrix dialog box. Click Next in the Account Information dialog box.
The Root Information dialog box appears as shown in Figure 2-12. The installation program uses the root password to configure the PATROL Console and Agents.
2-14
Step 12
Perform the step that applies to you. If you want the installation program to configure PATROL, you must type the root password in the entry box and click Next. If you want the installation program to configure PATROL, you are installing PATROL to remote hosts, and if the root accounts on the remote hosts have different passwords, click Advanced. The PATROL Root Password Matrix dialog box appears as shown in Figure 2-13 on page 2-16. The default password for the listed hosts is the password you specified on the Root Information dialog box.
2-15
In the PATROL Root Password Matrix dialog box, type the root password for each host that has a different password. The characters you type are encrypted immediately. Click OK in the PATROL Root Password Matrix dialog box, and click Next in the Root Information dialog box. If you want to manually configure PATROL using the configure.sh script, click Next without typing the root password. After the installation is finished and before you can use PATROL, you must log on as root to each remote system where you installed PATROL Agents and configure the PATROL Agents using the configure.sh script. If the products you are installing do not need to be configured, click Next without typing the root password.
Step 13
Determine what to do based on your action in the Root Information dialog box. If you typed the root password, the Agent Information dialog box, shown in Figure 2-14 on page 2-17, appears. Go to Step 14 on page 2-17. If you did not type the root password, the Save Installation Files dialog box, shown in Figure 2-15 on page 2-18, appears. Go to Step 15 on page 2-18.
2-16
Step 14
On the Agent Information dialog box, shown in Figure 2-14, do one of the following: If you typed the root password and you want the installation program to start the PATROL Agent, select Yes and type the number of the port you want the Agent to use. Then click Next. Valid port numbers are four-digit or five-digit integers greater than 1024. The default port is 1987. Check your /etc/services file or NIS for ports already in use by system services. Always choose a port number that is not already in use. If you typed the root password and if you do not want the installation program to start the PATROL Agent, select No and click Next.
The Save Installation Files dialog box appears as shown in Figure 2-15 on page 2-18.
2-17
Step 15
Type the host list file name and the products file name in their respective entry fields or click Browse to choose the path and file names you want. Click Next when you are finished. The installation program saves the names of the products that you selected to install and the hosts you selected to install them on. These files can be used in later installations to specify the same list of products or host computers. The User Encryption Key dialog box appears as shown in Figure 2-16 on page 2-18.
Figure 2-16 User Encryption Key Dialog Box
2-18
Step 16
Do one of the following: If you want to save the product and host file information for this installation, type and verify a key for the installation program to use to encrypt the password information. Then click OK. The key can be up to 20 characters and can contain any printable ASCII characters. The case of any letters is significant. That is, the key AbC is different from the key abc. If you use the hosts file from the current installation session in another installation session, the installation program will ask you for the key you enter here. You must enter the exact combination of characters for the key, or the installation program will not load the file. If you do not want to save the product and host file information, click Continue without saving files.
The installation program starts the installation process and the Operation Progress dialog box appears as shown in Figure 2-17 on page 2-19. It may be a few seconds before the status bars start to show progress.
Figure 2-17 Operation Progress Dialog Box
2-19
At this point, the following actions occur: The installation program copies the program files to the appropriate directories on the destination computers, copying the files to one computer at a time. If you supplied the root password and selected Yes on the PATROL Agent Information dialog box, the installation program also configures and starts the PATROL Agents. When the installation is complete on all the specified computers, the Operation Status dialog box appears as shown in Figure 2-18 on page 2-20.
Step 17
If you want to see details of the installation operations, click View Log. The installation program displays the contents of the log file. The log file is saved in the logs subdirectory of the patrolinstall directory you specified when you started the installation program. (See Starting the Installation Program with CD1 for Unix on page 1-23.) Click Exit to complete this portion of the installation program.
Step 18
2-20
If you have successfully finished installing the PATROL Agents and Consoles, you will see the dialog box as shown in Figure 2-19 on page 2-21.
If you were not successful in installing the PATROL Agents and Consoles, refer to the log file for information on what errors were reported during the installation.
You must now install PATROL KMs to both PATROL Agents and Consoles so that PATROL will function properly. See Installing PATROL KMs to Agent and Console Computers on page 2-23.
2-21
2-22
Yes
a remote installation? No
Choose the files to save the product list and the host list Yes
No
2-23
You should be familiar with the information in Navigating Within the Installation Program on page 1-14. You must have already installed the PATROL Consoles and Agents as described in Installing PATROL Agents and Consoles on page 2-4. The computers you want to install PATROL on must have ftp and telnet enabled. Be sure to use CD2 for Unix for this procedure. If you are installing a patch, you must stop any PATROL processes that are running on the computers you want to install the patch on.
Note
The installation program uses many of the same dialog boxes to install the KMs as to install agents and consoles. Many of the dialog boxes that were illustrated in the first part of the chapter are not illustrated again in this part.
Follow the instructions in Starting the Installation Program with CD2 for Unix on page 1-31. When you have completed the procedure, the Installation Setup dialog box appears.
Step 2
Do one of the following: Select Local to install PATROL to the computer you are currently using and click Next. Select Remote to install PATROL to specified remote computers in your environment and click Next. You may also install PATROL to your local computer at the same time.
BMC Software, Inc., Confidential and Proprietary Information
2-24
Select Install PATROL, then click Next. The Knowledge Module Installation Destination dialog box appears as shown in Figure 2-20.
Figure 2-20 Knowledge Module Installation Destination Dialog Box
Step 4
Select Install to Agents/Consoles and click Next. The Knowledge Module Destination Instructions dialog box appears as shown in Figure 2-21 on page 2-26.
2-25
Step 5
Review the installation instructions, noting that Step 2 is highlighted. Click Next to continue the installation program. The PATROL Products dialog box appears as shown in Figure 2-22.
Figure 2-22 PATROL Products Dialog Box
2-26
Step 6
You only need to select Agent KMs for PATROL Agents and Console KMs for PATROL Consoles. If you are concerned about conserving disk space, you may prefer to not select both KM types for both Agents and Consoles. Select the KMs you want to install by expanding the product tree and clicking beside the name of each KM you want to install. As you select products, the installation program updates the Estimated space required field. This field shows approximately how much space is required to install the products you have selected. If you have saved a list of products from a previous installation, you can use that list to specify the products you want to install. Click Load and select the file that contains the list you want to use on the Load Products List dialog box. After you select the file, the User Encryption Key dialog box appears. Type and verify the decryption key for the host file. Then click OK. Ordinarily, the installation program automatically selects the appropriate version of the program files to install, based on the operating system of the computers you want to install to. Click Advanced to override the installation programs automatic selection. Specify the operating system from the Advanced Options dialog box and click OK to close the dialog box. You return to the PATROL Products dialog box.
Step 7
When you have selected all the products you want to install, click Next. The dialog box you see next depends on whether you are doing a local or remote installation. For a local installation, the Destination Location dialog box appears.
2-27
For a remote installation, the Select Hosts dialog box appears. If you used the -nslookup option when you started the installation program, the Host Choices pane contains a list of host computers on your system. See Starting the Installation Program with CD2 for Unix on page 1-31 for more information about -nslookup. There may be a short delay while the host list loads.
Step 8
Perform the step that applies to you For a local installation, proceed to Step 11 on page 2-29. For a remote installation, proceed to Step 9.
Step 9
For a remote installation, select the host computers you want to install PATROL on from the Select Hosts dialog box, using one of the methods below.
Note
If you select a computer in error, click its name in the Hosts Selected pane. The installation program removes it from the list of selected hosts. Click the computer name in the Host Choices pane. This method is available only if you used the -nslookup option when you started the installation program. Click Add Host and type the host name of the computer in the addhost dialog box, then click OK to close the dialog box. If you want to use a list of computers saved during a previous installation, click Load and select the file. After you select the file, the User Encryption Key dialog box appears. Type and verify the decryption key for the host file. If you do not type the key that was used to encrypt the file, you cannot open the file. Whichever method you use to select the hosts, the computers you select are listed in the Hosts Selected pane of the Select Hosts dialog box.
2-28
Step 10
When you are finished selecting computers, click Next. The Destination Location dialog box appears. Use one of the following methods to choose the directory for PATROL products. You must install the KMs into the same directory as you installed the PATROL Consoles and Agents. To accept the default directory as PATROL3.3, click Next. To use a different directory, type the directory name in this dialog box and click Next. If you are performing a remote installation and want to enter destination directory locations for multiple hosts, click Advanced to display the PATROL Destination Directory Matrix. Enter the path name for each directory next to the name of the host, then click OK in the PATROL Destination Matrix dialog box. Click Next in the Destination Location dialog box when you are finished.
Step 11
Use one of the following methods for entering user names and passwords. Type the information on the PATROL user account in each entry box, then click Next. Use this method for local installations and for remote installations where the account names and passwords are the same for all host computers.
Note
For a local installation, the user name and password must be the same as the account that you used to start the installation program. If you are doing a remote installation and the user names and passwords are different for each host, click Advanced to display the PATROL Username/Password Matrix dialog box. Type the user name and password for each host, then click OK to close the PATROL Username/Password Matrix dialog box. Click Next in the Account Information dialog box.
2-29
Step 13
Perform the step that applies to you. If the Save Installation Files dialog box appears, proceed to Step 15 on page 2-30. If the Root Information dialog box appears, the installation program requires root access to install one or more of the KMs you selected. Proceed to Step 14.
Step 14
Perform the step that applies to you. If the root accounts for all the hosts you are installing KMs to have the same password, type the root password in the entry box and click Next. If you are installing PATROL KMs to remote hosts, and if the root accounts on the remote hosts have different passwords, click Advanced. The PATROL Root Password Matrix dialog box appears. The default password for the listed hosts is the password you specified on the Root Information dialog box. In the PATROL Root Password Matrix dialog box, type the root password for each host that has a different password. The characters you type are encrypted immediately. Click OK in the PATROL Root Password Matrix dialog box, and click Next in the Root Information dialog box. The Save Installation Files dialog box appears.
Step 15
Type the host list file name and the products file name in their respective entry fields or click Browse to choose the path and file names you want. Click Next when you are finished. The installation program saves the names of the products that you selected to install and the hosts you selected to install them on. These files can be used in later installations to specify the same list of products or host computers.
2-30
Do one of the following: If you want to save the product and host file information for this installation, type and verify a key for the installation program to use to encrypt the password information. Then click OK. The key can be up to 20 characters and can contain any printable ASCII characters. The case of any letters is significant. That is, the key AbC is different from the key abc. If you use the hosts file from the current installation session in another installation session, the installation program will ask you for the key. You must enter the exact combination of characters for the key, or the installation program will not load the file. If you do not want to save the product and host file information, click Continue without saving files.
The installation program starts the installation process and the Operation Progress dialog box appears. It may be a few seconds before the status bars start to show progress. At this point, the following actions occur: The installation program copies the program files to the appropriate directories on the destination computers, copying the files to one computer at a time. When the installation is complete on all the specified computers, the Operation Status dialog box appears.
Step 17
If you want to see details of the installation operations, click View Log. The installation program displays the contents of the log file. The log file is saved in the logs subdirectory of the patrolinstall directory you specified when you started the installation program. (See Starting the Installation Program with CD2 for Unix on page 1-31.) Click Exit to complete this portion of the installation program.
Step 18
2-31
If you have successfully finished installing KMs to the PATROL Agents and Consoles, you will see the dialog box as shown in Figure 2-23 on page 2-32.
If you were not successful in installing the PATROL Agents and Consoles, refer to the log file for information on what errors were reported during the installation.
If you have not elected to use the PATROL KMDS, your installation of PATROL is complete. If you want to use the PATROL KMDS in your environment, continue with the installation as described in Chapter 3, Installing the PATROL KMDS and PATROL KMs.
2-32
This chapter describes how to use the installation program to install the PATROL Knowledge Modules Deployment Server (PATROL KMDS) and PATROL KMs to the PATROL KMDS on computers using the Unix operating system. This chapter contains the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Installation of the PATROL Knowledge Module Deployment Server3-3 Installing the PATROL KMDS . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Installation of the PATROL KMs to the PATROL KMDS Computers3-20 Installation of PATROL KMs to the PATROL KMDS . . . . . . . . 3-21
3-1
Overview
This chapter describes the installation of the PATROL KMDS, and KMs to the PATROL KMDS. You will use CD1 for Unix and CD2 for Unix to complete this operation. The installation program takes you through each step of the installation, whether you are making a local or a networked installation. A local installation occurs when you install the PATROL products on the computer you are currently logged on. A remote installation is when you install the PATROL products on computers that are accessible to your local computer. (Your local computer is the computer you are currently logged on.) The installation program allows you to specify the products that you want to install and the remote computers you want to install on at one time. The remote installation is very similar to the local installation. The procedures in this chapter cover both remote and local installations. When a particular step applies only to one type of install, it is clearly marked.
Note
Before you can install the PATROL KMDS and KMs to the PATROL KMDS, you must have installed the PATROL Agents and Consoles and KMs as shown in Chapter 2, Installing the PATROL Agent, PATROL Console, and PATROL KMs.
3-2
3-3
Yes
a remote installation?
Choose the files to save the product list and the host list Yes
No
3-4
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You must have completed the procedures described in Starting the Installation Program with CD1 for Unix on page 1-23 You should be familiar with the information in Navigating Within the Installation Program on page 1-14. You must have already installed the PATROL Agents and Consoles as described in Installing PATROL Agents and Consoles on page 2-4 and have already installed the PATROL KMs into the Agents and Consoles as described in Installing PATROL KMs to Agent and Console Computers on page 2-23. The computers you want to install PATROL on must have ftp and telnet enabled. Be sure to use CD1 for Unix for this procedure. If you are installing a patch, you must stop any PATROL processes that are running on the computers you want to install the patch on.
Note
Follow the instructions in Starting the Installation Program with CD1 for Unix on page 1-23. When the installation program prompts you for the products you want to install, type 2 and press Enter. See Figure 3-1.
3-5
Figure 3-1
Step 2
Continue the steps as described in the Starting the Installation Program with CD1 for Unix procedure. When the PATROL Installation Instructions dialog box appears, it highlights that you are currently on step 3 of the installation as shown in Figure 3-2.
Figure 3-2 PATROL Installation Instructions Dialog Box
When you have completed the procedure, the Installation Setup dialog box appears as shown in Figure 3-3.
3-6
Figure 3-3
Step 3
Do one of the following: Select Local to install PATROL to the computer you are currently using and click Next. Select Remote to install PATROL to specified remote computers in your environment and click Next. You may also install PATROL to your local computer at the same time.
3-7
Figure 3-4
The options available on the Installation Operations dialog box depends on whether you chose Local or Remote in the Installation Setup dialog box. Replicate PATROL and Distribute PATROL are only displayed if you chose Remote on the Installation Setup dialog box.
Note
Distribute PATROL is used with the PATROL KMDS. For more information on this option, consult the PATROL Knowledge Module Deployment Server Manager User Guide. The PATROL Products dialog box appears as shown in Figure 3-5 on page 3-9.
3-8
Figure 3-5
Step 4
Select the products you want to install by clicking on the box or double clicking on the product category to expand each product list and then selecting the check box by the product name. As you select products, the installation program updates the Estimated space required field. This field shows approximately how much space is required to install the products you have selected. To use a saved a list of products from a previous installation, click Load and select the file that contains the list you want to use. Ordinarily, the installation program automatically selects the appropriate version of the program files to install, based on the operating system of the computers you want to install to. Click Advanced to override the installation programs automatic selection. Specify the operating system from the Advanced Options dialog box and click OK to close the dialog box.
3-9
Figure 3-6
When you have selected all the products you want to install, click Next. If you are doing a local installation, the Destination Location dialog box appears as shown in Figure 3-9 on page 3-13. If you are doing a remote installation, the Select Hosts dialog box appears as shown in Figure 3-7. If you used the -nslookup option when you started the installation program, the Host Choices pane contains a list of host computers on your system. See Starting the Installation Program with CD1 for Unix on page 1-23 for more information about -nslookup. There may be a short delay while the host list loads.
3-10
Figure 3-7
Step 6
Perform the step that applies to you: For a local installation, proceed to Step 9 on page 3-13. For a remote installation, proceed to Step 7.
Step 7
For a remote installation, select the host computers you want to install PATROL on from the Select Hosts dialog box, using one of the methods below.
Note
If you select a computer in error, click its name in the Hosts Selected pane. The installation program removes it from the list of selected hosts. Click the computer name in the Host Choices pane. This method is available only if you used the -nslookup option when you started the installation program. Click Add Host and type the host name of the computer in the addhost dialog box, then click OK to close the dialog box. If you want to use a list of computers saved during a previous installation, click Load and select the file.
3-11
After you select the file, the User Encryption Key dialog box appears as shown in Figure 3-8. Type and verify the decryption key for the host file.
Figure 3-8 User Encryption Key Dialog Box
If you do not type the key that was used to encrypt the file, you cannot open the file. Whichever method you use to select the hosts, the computers you select are listed in the Hosts Selected pane of the Select Hosts dialog box.
Step 8
When you are finished selecting computers, click Next. The Destination Location dialog box appears as shown in Figure 3-9 on page 3-13.
3-12
Figure 3-9
Step 9
Use one of the following methods to choose the directory for PATROL products. You must install the PATROL KMDS to a different directory than the directory where you installed the PATROL Agents and Consoles. Failure to do so will result in the PATROL KMDS not functioning properly. To accept the default directory as PATROL3.3KMDS, click Next. To use a different directory, type the directory name in this dialog box and click Next. If you are performing a remote installation and want to enter destination directory locations for multiple hosts, click Advanced to display the PATROL Destination Directory Matrix as shown in Figure 3-10. Enter the path name for each directory next to the name of the host, then click OK in the PATROL Destination Matrix dialog box. Click Next in the Destination Location dialog box when you are finished.
3-13
Step 10
Use one of the following methods for entering user names and passwords.
3-14
Type the information on the PATROL user account in each entry box, then click Next. Use this method for local installations and for remote installations where the account names and passwords are the same for all host computers.
Note
For a local installation, the user name and password must be the same as the account that you used to start the installation program. If you are doing a remote installation and the user names and passwords are different for each host, click Advanced to display the PATROL Username/Password Matrix dialog box as shown in Figure 3-12 on page 3-15. Type the user name and password for each host, then click OK to close the PATROL Username/Password Matrix dialog box. Click Next in the Account Information dialog box.
The Save Installation Files dialog box appears as shown in Figure 3-13 on page 3-16.
3-15
Step 11
Type the host list file name and the products file name in their respective entry fields or click Browse to choose the path and file names you want. Click Next when you are finished. The installation program saves the names of the products that you selected to install and the hosts you selected to install them on. These files can be used in later installations to specify the same list of products or host computers. The User Encryption Key dialog box appears as shown in Figure 3-14 on page 3-16.
Figure 3-14 User Encryption Key Dialog Box
3-16
Step 12
Do one of the following: If you want to save the product and host file information for this installation, type and verify a key for the installation program to use to encrypt the password information. Then click OK. The key can be up to 20 characters and can contain any printable ASCII characters. The case of any letters is significant. That is, the key AbC is different from the key abc. If you use the hosts file from the current installation session in another installation session, the installation program will ask you for the key. You must enter the exact combination of characters for the key, or the installation program will not load the file. If you do not want to save the product and host file information, click Continue without saving files.
The installation program starts the installation process and the Operation Progress dialog box appears as shown in Figure 3-15 on page 3-17. It may be a few seconds before the status bars start to show progress.
Figure 3-15 Operation Progress Dialog Box
3-17
At this point, the following actions occur: The installation program copies the program files to the appropriate directories on the destination computers, copying the files to one computer at a time. When the installation is complete on all the specified computers, the Operation Status dialog box appears as shown in Figure 3-16 on page 3-18.
Step 13
If you want to see details of the installation operations, click View Log. The installation program displays the contents of the log file. The log file is saved in the logs subdirectory of the patrolinstall directory you specified when you started the installation program. (See Starting the Installation Program with CD1 for Unix on page 1-23.) Click Exit to complete this portion of the installation program. If you have successfully finished installing the PATROL KMDS, you will see the dialog box as shown in Figure 3-17 on page 3-19.
Step 14
3-18
If you were not successful in installing the PATROL KMDS, refer to the log file for information on what errors were reported during the installation.
You must now install KMs to the PATROL KMDS. See Installation of PATROL KMs to the PATROL KMDS on page 3-21.
3-19
3-20
Yes
a remote installation? No
Choose the files to save the product list and the host list Yes
No
You should be familiar with the information in Navigating Within the Installation Program on page 1-14.
BMC Software, Inc., Confidential and Proprietary Information
3-21
You must have already installed the PATROL Agents and Consoles as described in Installing PATROL Agents and Consoles on page 2-4. the PATROL KMs into the Agents and Consoles as described in Installing PATROL KMs to Agent and Console Computers on page 2-23. the PATROL KMDS as described in Installing the PATROL KMDS on page 3-4.
If you are installing a patch, you must stop any PATROL processes that are running on the computers you want to install the patch on.
Note
The installation program uses many of the same dialog boxes to install the KMs as to install the PATROL KMDS. Many of the dialog boxes that were illustrated in the first part of the chapter are not illustrated again in this part. The computers you want to install PATROL on must have ftp and telnet enabled. Be sure to use CD2 for Unix for this procedure.
To Install PATROL KMs to a PATROL KMDS Step 1
Follow the instructions in Starting the Installation Program with CD2 for Unix on page 1-31. When you have completed the procedure, the Installation Setup dialog box appears.
Step 2
Do one of the following: Select Local to install PATROL to the computer you are currently using and click Next.
3-22
Select Remote to install PATROL to specified remote computers in your environment and click Next. You may also install PATROL to your local computer at the same time.
Select Install PATROL, then click Next. The Knowledge Module Installation Destination dialog box appears as shown in Figure 3-18.
Figure 3-18 Knowledge Module Installation Destination Dialog Box
Step 4
Select Install to KMDS and click Next. The Knowledge Module Destination Instructions dialog box appears as shown in Figure 3-19 on page 3-24.
3-23
Step 5
Review the installation instructions, noting that Step 4 is highlighted. Click Next to continue the installation program. The PATROL Products dialog box appears as shown in Figure 3-20 on page 3-24.
Figure 3-20 PATROL Products Dialog Box
Step 6
3-24
Select the KMs you want to install by clicking on the box or double clicking on the product category to expand the product tree and clicking beside the name of each KM you want to install. As you select products, the installation program updates the Estimated space required field. This field shows approximately how much space is required to install the products you have selected.
If you have saved a list of products from a previous installation, you can use that list to specify the products you want to install. Click Load and select the file that contains the list you want to use on the Load Products List dialog box. Click OK. Ordinarily, the installation program automatically selects the appropriate version of the program files to install based on the operating system of the computers you want to install to. Click Advanced to override the installation programs automatic selection. Specify the operating system from the Advanced Options dialog box and click OK to close the dialog box. You return to the PATROL Products dialog box.
Note
You must install both Agent KMs and Console KMs to the PATROL KMDS to ensure that all necessary files are present in the PATROL KMDS.
Step 7
When you have selected all the products you want to install, click Next. The dialog box you see next depends on whether you are doing a local or remote installation. For a local installation, the Destination Location dialog box appears. For a remote installation, the Select Hosts dialog box appears. If you used the -nslookup option when you started the installation program, the Host Choices pane contains a list of host computers on your system. See Starting the Installation Program with CD2 for Unix on page 1-31 for more information about -nslookup. There may be a short delay while the host list loads.
3-25
Step 8
Perform the step that applies to you: For a local installation, proceed to Step 11 on page 3-26. For a remote installation, proceed to Step 9 on page 3-26.
Step 9
For a remote installation, select the host computers you want to install PATROL on from the Select Hosts dialog box, using one of the methods below.
Note
If you select a computer in error, click its name in the Hosts Selected pane. The installation program removes it from the list of selected hosts. Click the computer name in the Host Choices pane, on the left. This method is available only if you used the -nslookup option when you started the installation program. Click Add Host and type the host name of the computer in the addhost dialog box, then click OK to close the dialog box. If you want to use a list of computers saved during a previous installation, click Load and select the file. After you select the file, the User Encryption Key dialog box appears. Type and verify the decryption key for the host file. If you do not type the key that was used to encrypt the file, you cannot open the file. Whichever method you use to select the hosts, the computers you select are listed in the Hosts Selected pane of the Select Hosts dialog box.
Step 10
When you are finished selecting computers, click Next. The Destination Location dialog box appears. Use one of the following methods to choose the directory for PATROL products. To accept the default directory as PATROL3.3KMDS, click Next. Type the directory name in this dialog box and click Next.
BMC Software, Inc., Confidential and Proprietary Information
Step 11
3-26
If you are performing a remote installation and want to enter destination directory locations for multiple hosts, click Advanced to display the PATROL Destination Directory Matrix. Enter the path name for each directory next to the name of the host, then click OK in the PATROL Destination Matrix dialog box. Click Next in the Destination Location dialog box when you are finished.
You must install the KMs into the same directory as you installed the PATROL KMDS. The Account Information dialog box appears.
Step 12
Use one of the following methods for entering user names and passwords. Type the information on the PATROL user account in each entry box, then click Next. Use this method for local installations and for remote installations where the account names and passwords are the same for all host computers.
Note
For a local installation, the user name and password must be the same as the account that you used to start the installation program. If you are doing a remote installation and the user names and passwords are different for each host, click Advanced to display the PATROL Username/Password Matrix dialog box. Type the user name and password for each host, then click OK to close the PATROL Username/Password Matrix dialog box. Click Next in the Account Information dialog box.
Step 13
Perform the step that applies to you. If the Save Installation Files dialog box appears, proceed to Step 15 on page 3-28. If the Root Information dialog box appears, the installation program requires root access to install one or more of the KMs you selected. Proceed to Step 14.
3-27
Step 14
Perform the step that applies to you. If the root accounts for all the hosts you are installing KMs to have the same password, type the root password in the entry box and click Next. If you are installing PATROL KMs to remote hosts, and if the root accounts on the remote hosts have different passwords, click Advanced. The PATROL Root Password Matrix dialog box appears. The default password for the listed hosts is the password you specified on the Root Information dialog box. In the PATROL Root Password Matrix dialog box, type the root password for each host that has a different password. The characters you type are encrypted immediately. Click OK in the PATROL Root Password Matrix dialog box, and click Next in the Root Information dialog box. The Save Installation Files dialog box appears.
Step 15
Type the host list file name and the products file name in their respective entry fields or click Browse to choose the path and file names you want. Click Next when you are finished. The installation program saves the names of the products that you selected to install and the hosts you selected to install them on. These files can be used in later installations to specify the same list of products or host computers. The User Encryption Key dialog box appears.
Step 16
Do one of the following: If you want to save the product and host file information for this installation, type and verify a key for the installation program to use to encrypt the password information. Then click OK.
3-28
The key can be up to 20 characters and can contain any printable ASCII characters. The case of any letters is significant. That is, the key AbC is different from the key abc. If you use the hosts file from the current installation session in another installation session, the installation program will ask you for the key. You must enter the exact combination of characters for the key that you enter here, or the installation program will not load the file. If you do not want to save the product and host file information, click Continue without saving files.
The installation program starts the installation process and the Operation Progress dialog box appears. It may be a few seconds before the status bars start to show progress. At this point, the following actions occur: The installation program copies the program files to the appropriate directories on the destination computers, copying the files to one computer at a time. When the installation is complete on all the specified computers, the Operation Status dialog box appears.
Step 17
If you want to see details of the installation operations, click View Log. The installation program displays the contents of the log file. The log file is saved in the logs subdirectory of the patrolinstall directory you specified when you started the installation program. (See Starting the Installation Program with CD2 for Unix on page 1-31.) Click Exit to complete this portion of the installation program. If you have successfully installed KMs to the PATROL KMDS, you will see the dialog box as shown in Figure 3-21 on page 3-30.
Step 18
3-29
If you were not successful in installing KMs to the PATROL KMDS, refer to the log file for information on what errors were reported during the installation.
You now have a complete PATROL installation using the PATROL KMDS. If you have successfully completed the installing PATROL, proceed to Chapter 5, Configuring, Starting, and Licensing PATROL, which describes starting and configuring the PATROL Console and PATROL Knowledge Modules. It also describes replacing your demonstration license with a permanent license. The chapter tells you how to perform these tasks or directs you to other PATROL documentation with the information you need.
3-30
4-1
BMC Software, Inc., recommends that you do not attempt to replicate an installation of the PATROL KMDS. You should directly install the PATROL KMDS on each machine that you want the PATROL KMDS to be on. You should install the KMs for each PATROL KMDS directly into the PATROL KMDS. If you do replicate the PATROL KMDS installation, the replicated PATROL KMDS will not work correctly. There are two tasks you must perform to complete a replicated installation. They are: 1. Creating the Repository on page 4-3. This task creates the PATROL installation that you want to replicate to other computers. 2. Replicating PATROL Products to Remote Computers on page 4-7. This task copies the repository installation to the other computers.
4-2
Use the procedure described in Installing PATROL Agents and Consoles on page 2-4 to install the agents and consoles you want to replicate. On the PATROL Products dialog box, shown in Figure 4-1, select the products you want to install. Then click Advanced.
Figure 4-1 The PATROL Products Dialog Box
Step 2
The installation program displays the Advanced Options-Operating Systems dialog box, as shown in Figure 4-2 on page 4-4.
BMC Software, Inc., Confidential and Proprietary Information
4-3
Figure 4-2
The different types of Unix operating systems require slightly different versions of the PATROL software. When you install to a local or remote host, the installation program automatically determines the Unix operating system appropriate for each computer and installs the correct version on each. This means that when you do a local installation, the installation program only installs the version of PATROL for that computer. The remote computers where you want to install PATROL may have different types of Unix. For example, the local computer may be Hewlett Packard, while the remote hosts might be a combination of Siemens and DIGITAL computers. To ensure that you replicate the correct versions of PATROL on the remote systems, you must specify the operating systems as part of the preliminary installation.
Step 3
Select the operating systems used by each of the remote computers you want to replicate PATROL on, then click OK. The installation program displays the PATROL Products dialog box again.
Step 4
Click Next.
4-4
The installation program installs all the products you specify in the versions for each of the operating systems you specify, if they are available.
Note
Not all the PATROL products are available for all the Unix operating systems. If you specify an operating system that is not available for the products you have specified, the installation program will write an error message in the installation log file.
Step 5
Use the procedure described in Installing PATROL KMs to Agent and Console Computers on page 2-23 to install the PATROL Knowledge Modules you want to replicate. On the PATROL Products dialog box, shown in Figure 4-3, select the products you want to install. Then click Advanced.
Figure 4-3 The PATROL Products Dialog Box
Step 6
The installation program displays the Advanced Options-Operating Systems dialog box.
4-5
Step 7
Select the operating systems used by each of the remote computers you want to replicate PATROL on, then click OK. The installation program displays the PATROL Products dialog box again.
Step 8
Continue with the installation. The installation program installs all the products you specify in the versions for each of the operating systems you specify, if they are available. Customize the products to meet your specific needs. This may include customizing parameters, menu commands, classes, or others. See the PATROL for Unix User Guide for details on how to customize PATROL.
Step 9
To continue the process of a replicated installation, perform the task Replicating PATROL Products to Remote Computers on page 4-7.
4-6
Select Remote
Yes
No
Choose the files to save the product list and the host list
No
Yes
4-7
Before you can replicate the customized PATROL products to other remote computers, you must have completed the following tasks: You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You should be familiar with the information in Navigating Within the Installation Program on page 1-14. You must have completed the preliminary installation as described in Creating the Repository on page 4-3.
The computers you want to install PATROL on must have ftp and telnet enabled. Be sure you are using CD1 for Unix to do this procedure.
To Replicate PATROL Products to Remote Computers Step 1
Follow the instructions in Starting the Installation Program with CD1 for Unix on page 1-23. When the installation program prompts you for the products you want to install, type 1 and press Enter. See Figure 4-4.
Figure 4-4 PATROL Product set selection Text
When you have completed the procedure, the Installation Setup dialog box appears as shown in Figure 4-5.
4-8
Figure 4-5
Step 2
Select Remote and click Next. The installation program displays the Installation Operations dialog box, as shown in Figure 4-6.
Figure 4-6 Installation Operations Dialog Box
4-9
Step 3
Distribute PATROL is used with the PATROL KMDS. For more information on this option, consult the PATROL KMDS Manager User Guide. The installation program displays the Select Hosts dialog box, as shown in Figure 4-7. If you used the -nslookup option when you started the installation program, the Host Choices pane contains a list of host computers on your system. See Starting the Installation Program with CD1 for Unix on page 1-23 for more information about -nslookup. There may be a short delay while the host list loads.
Figure 4-7 The Select Hosts Dialog Box
Step 4
Select the host computers you want to install PATROL on from the Select Hosts dialog box, using one of the methods below.
Note
If you select a computer in error, click its name in the Hosts Selected pane. The installation program removes it from the list of selected hosts.
BMC Software, Inc., Confidential and Proprietary Information
4-10
Click the computer name in the Host Choices pane. This method is available only if you used the -nslookup option when you started the installation program. Click Add Host and type the host name of the computer in the addhost dialog box, then click OK to close the dialog box. If you want to use a list of computers saved during a previous installation, click Load and select the file. After you select the file, the User Encryption Key dialog box appears as shown in Figure 4-8. Type and verify the decryption key for the host file.
Figure 4-8
If you do not type the key that was used to encrypt the file, you cannot open the file. Whichever method you use to select the hosts, the computers you select are listed in the Hosts Selected pane of the Select Hosts dialog box.
Step 5
When you are finished selecting computers, click Next. The installation program displays the Replication Path dialog box, shown in Figure 4-9.
4-11
Figure 4-9
Step 6
Type the full path name of the directory that contains the preliminary installed version of PATROL and click Next. The installation program will replicate the entire contents of this directory to all the selected hosts. The installation program displays the Destination Location dialog box, as shown in Figure 4-10 on page 4-13.
4-12
Step 7
Use one of the following methods to choose the directory for PATROL products on all the computers to which you are replicating the installation of PATROL products. To accept the default directory as PATROL3.3, click Next. To use a different directory, type the directory name in this dialog box and click Next. To enter destination directory locations for multiple hosts, click Advanced to display the PATROL Destination Directory Matrix as shown in Figure 4-11. Enter the path name for each directory next to the name of the host, then click OK in the PATROL Destination Matrix dialog box. Click Next in the Destination Location dialog box when you are finished.
4-13
Step 8
Use one of the following methods for entering user names and passwords. Type the information on the PATROL user account in each entry box, then click Next. Use this method for remote installations where the account names and passwords are the same for all host computers.
4-14
If the user names and passwords are different for each host, click Advanced to display the PATROL Username/Password Matrix dialog box as shown in Figure 4-13. Type the user name and password for each host, then click OK to close the PATROL Username/Password Matrix dialog box. Click Next in the Account Information dialog box.
Step 9
If you want the installation program to configure PATROL, you must type the root password in the entry box and click Next. If you want the installation program to configure PATROL and if the root accounts on the remote hosts have different passwords, click Advanced. The PATROL Root Password Matrix dialog box appears as shown in Figure 4-15 on page 4-16.
In the PATROL Root Password Matrix dialog box, type the root password for each host. The characters you type are encrypted immediately. Click OK in the PATROL Root Password Matrix dialog box and click Next in the Root Information dialog box. If you want to manually configure PATROL using the configure.sh script, click Next in the Root Information dialog box without typing the root password. After the installation is finished and before you can use PATROL, you must log on as root to each remote system where you installed PATROL Agents, and configure the PATROL Agents using the configure.sh script.
Step 10
Determine what to do based on your action in the Root Information dialog box. If you typed the root password, go to Step 11 on page 4-17. If you did not type the root password go to Step 12 on page 4-18.
BMC Software, Inc., Confidential and Proprietary Information
4-16
Step 11
On the Agent Information dialog box, shown in Figure 4-16, do one of the following: If you typed the root password and you want the installation program to start the PATROL Agent, select Yes and type the number of the port you want the agent to use. (The default is 1987.) Then click Next. Valid port numbers are four-digit or five-digit integers greater than 1024. The default port is 1987. Check your /etc/services file or NIS for ports already in use by system services. Choose a port number that is not already in use. If you typed the root password and if you do not want the installation program to start the PATROL Agent, select No and click Next.
The Save Installation Files dialog box appears as shown in Figure 4-17 on page 4-18.
4-17
Step 12
Type the host list file name and the products file name in their respective entry fields or click Browse to choose the path and file names you want. Click Next when you are finished. The installation program saves the names of the products that you selected to install and the hosts you selected to install them on. These files can be used in later installations to specify the same list of products or host computers. The User Encryption Key dialog box appears as shown in Figure 4-18 on page 4-18.
Figure 4-18 The User Encryption Key Dialog Box
4-18
Step 13
Do one of the following: If you want to save the host file information, type a key for the installation program to use to encrypt the password information. Type the key a second time to verify it. Then click OK. The key can be up to 20 characters and can contain any printable ASCII characters. The case of any letters is significant. That is, the key AbC is different from the key abc. If you load the hosts file to use in another installation session, the installation program will ask you for the key. You must enter the exact combination of characters for the key that you enter here, or the installation program will not load the file. If you do not want to save the host file information, click Continue without saving files.
The installation program starts the installation process and displays the Operation Progress dialog box, shown in Figure 4-19 on page 4-19. It may be a few seconds before the status bars start to show progress.
Figure 4-19 The Operation Progress Dialog Box
4-19
At this point, the following actions occur: The installation program copies the program files to the appropriate directories on the destination computers, copying the files to one computer at a time. If you supplied the root password and selected Yes on the PATROL Agent Information dialog box, the installation program also configures and starts the PATROL Agents. When the installation is complete on all the specified computers, the Operation Status dialog box appears as shown in Figure 4-20 on page 4-20.
Step 14
If you want to see details of the installation operations, click View Log. The installation program displays the contents of the log file. The log file is saved in the logs subdirectory of the patrolinstall directory you specified when you started the installation program. (See Starting the Installation Program with CD1 for Unix on page 1-23.) Click Exit to complete this portion of the installation program.
Step 15
4-20
If you have just successfully finished installing the PATROL Agents and Consoles, you will see the dialog box as shown in Figure 4-21 on page 4-21.
If you were not successful in installing the PATROL Agents and Consoles, refer to the log file for information on any errors that were reported during the installation.
Chapter 5, Configuring, Starting, and Licensing PATROL, describes starting and configuring the PATROL Console and PATROL Knowledge Modules. It also describes replacing your demonstration license with a permanent license. The chapter tells you how to perform these tasks or directs you to other PATROL documentation with the information you need.
4-21
4-22
No
Yes
4-23
Before you can uninstall PATROL products, you must have completed the following tasks: You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You should be familiar with the information in Navigating Within the Installation Program on page 1-14. You must stop any PATROL processes that are running on the computers where you want to uninstall PATROL. See the PATROL for Unix Getting Started Guide, the PATROL Agent Reference Manual, and the PATROL Knowledge Module Deployment Server Manager User Guide for information on stopping PATROL processes. The computers you want to uninstall PATROL from must have ftp and telnet enabled.
Follow the instructions in Starting the Installation Program with CD1 for Unix on page 1-23. When the installation program prompts you for the products to install, as shown in Figure 4-22, if you are uninstalling agents and consoles, type 1 and press Enter. if you are uninstalling the PATROL KMDS, type 2 and press Enter.
4-24
Step 2
Continue the steps as described in the Starting the Installation Program with CD1 for Unix procedure. When you have completed the procedure, the Installation Setup dialog box appears as shown in Figure 4-23.
Figure 4-23 The Installation Setup Dialog Box
Step 3
Do one of the following: Select Local to uninstall PATROL from the computer you are currently using and click Next. Select Remote to uninstall PATROL from specified remote computers in your environment and click Next. You may also uninstall PATROL from your local computer at the same time.
The installation program displays the Installation Operations dialog box, as shown in Figure 4-24 on page 4-26.
4-25
The options available on the Installation Operations dialog box depend on whether you chose Local or Remote in the Installation Setup dialog box. Replicate PATROL and Distribute PATROL are only displayed if you chose Remote on the Installation Setup dialog box.
Note
Distribute PATROL is used with the PATROL KMDS. For more information on this option, consult the PATROL Knowledge Module Deployment Server Manager User Guide.
Step 4 Step 5
Select Uninstall PATROL, and then click Next. When you have selected all the products you want to install, click Next. The dialog box you see next depends on whether you are doing a local or remote uninstall. For a local uninstall, the Destination Location dialog box appears as shown in Figure 4-27 on page 4-29.
4-26
Fora remote uninstall, the Select Hosts dialog box appears as shown in Figure 4-25 on page 4-27. If you used the -nslookup option when you started the installation program, the Host Choices pane contains a list of host computers on your system. See Starting the Installation Program with CD1 for Unix on page 1-23 for more information about -nslookup. There may be a short delay while the host list loads.
Figure 4-25 The Select Hosts Dialog Box (Remote Installation Only)
Step 6
Perform the step that applies to you. For a local uninstall, proceed to Step 9 on page 4-29. For a remote uninstall, proceed to Step 7 on page 4-27.
Step 7
For a remote uninstall, select the host computers you want to remove PATROL from using one of the methods below. Click the computer name in the Host Choices pane. This method is available only if you used the -nslookup option when you started the installation program. Click Add Host and type the host name of the computer in the addhost dialog box, then click OK to close the dialog box.
4-27
If you want to use a list of computers saved during a previous installation, click Load and select the file. After you select the file, the User Encryption Key dialog box appears as shown in Figure 4-26. Type and verify the decryption key for the host file.
If you do not type the key that was used to encrypt the file, you cannot open the file. Whichever method you use to select the hosts, the computers you select are listed in the Hosts Selected pane of the Select Hosts dialog box.
Note
If you select a computer in error, click its name in the Hosts Selected pane. The installation program removes it from the list of selected hosts.
Step 8
When you are finished selecting computers, click Next. The installation program displays the Destination Location dialog box, as shown in Figure 4-27 on page 4-29.
4-28
Step 9
Do one of the following: To specify the same directory on each computer that contains the PATROL products you want to uninstall, type the name of the directory in the entry box and click Next. To specify a different directory on each computer that contains the PATROL products you want to uninstall, click Advanced to display the PATROL Destination Directory Matrix. Enter the path name for each directory next to the name of the host, then click OK in the PATROL Destination Matrix dialog box. Click Next in the Destination Location dialog box when you are finished. To specify the $HOME directory of the user account on each computer, leave the entry box empty and click Next. The installation program will uninstall the PATROL products from the $HOME directory of the user account on each computer.
The installation program displays the Account Information dialog box, as shown in Figure 4-28 on page 4-30.
4-29
Step 10
Use one of the following methods for entering user names and passwords. The password is required so that the installation program can turn off the agent and console before they are uninstalled. Type the information on the PATROL user account in each entry box, then click Next. Use this method for local installations and for remote installations where the account names and passwords are the same for all host computers.
Note
For a local installation, the user name and password must be the same as the account that you used to start the installation program. If you are doing a remote installation and the user names and passwords are different for each host, click Advanced to display the PATROL Username/Password Matrix dialog box as shown in Figure 4-29 on page 4-31. Type the user name and password for each host, then click OK to close the PATROL Username/Password Matrix dialog box. Click Next in the Account Information dialog box.
4-30
The Save Installation Files dialog box appears as shown in Figure 4-30.
Figure 4-30 The Save Installation Files Dialog Box
Step 11
Type the Hostlist file name or click Browse to choose the path and file name you want. Click Next.
4-31
The installation program saves the name of the computers you selected to uninstall from. This file can be used in later installs to specify the same computers.
Note
The Products file entry box is not used in the uninstall PATROL process. The installation program displays the User Encryption Key dialog box, as shown in Figure 4-31.
Figure 4-31 The User Encryption Key Dialog Box
Step 12
Do one of the following: If you want to save the host file information, type and verify a key for the installation program to use to encrypt the password information. Then click OK. The key can be up to 20 characters and can contain any printable ASCII characters. The case of any letters is significant. That is, the key AbC is different from the key abc. If you use the hosts file from the current installation session in another installation session, the installation program will ask you for the key you enter here. You must enter the exact combination of characters for the key, or the installation program will not load the file. If you do not want to save the host file information, click Continue without saving files.
BMC Software, Inc., Confidential and Proprietary Information
4-32
The installation program begins uninstalling products and displays the Operation Progress dialog box, shown in Figure 4-32 on page 4-33. It may be a few seconds before the status bars show progress.
Figure 4-32 The Operation Progress Dialog Box
When the uninstall is complete, the installation program displays the Operation Status dialog box, shown in Figure 4-33 on page 4-34.
4-33
Step 13
If you want to see details of the installation operations, click View Log. The installation program displays the contents of the log file. The log file is saved in the logs subdirectory of the patrolinstall directory you specified when you started the installation program. (See Starting the Installation Program with CD1 for Unix on page 1-23.) Click Exit to stop the installation program.
Note
Step 14
There are files that will remain after the uninstall is complete. To clean the directory, execute the rm -rf command in $PATROL_HOME to remove all remaining files.
4-34
5-1
This procedure is applicable only for PATROL Consoles, PATROL Agents, and PATROL Event Managers installed on computers running under a Unix operating system.
5-2
To complete this procedure, you must know the root password for each computer that has PATROL products that you want to configure.
Restriction
You cannot execute the configuration script from an NFS-mounted directory if the root account has not been granted root access privileges on the NFS server. You must run the configuration script on each computer that you want to configure PATROL products on.
To Run the Configuration Script Step 1
Type the following command and press Return to log on as the root user:
% su
Type the password for root and press Return. Use the cd command to change the current directory to the directory where the PATROL products were installed. (For example, cd /users/patrol/PATROL3.3.)
5-3
Step 4
#./configure.sh
The configure script sets the user ID to root for the PATROL Console, PATROL Agent, and PATROL Event Manager Console executables as applicable.
See...
Starting a PATROL Agent on page 5-6 Starting the PATROL Consoles on page 5-7 Starting the PATROL Event Manager on page 5-10 To Supply License Information on page 5-13 The PATROL Knowledge Module Deployment Server Manager User Guide Setting PATROL Environment Variables on page 5-11
5-4
5-5
Change directories (cd) to the PATROL installation directory. Type the following command at the operating system prompt:
% ./PatrolAgent -p <portNo>
A message notifies you that the PATROL Agent is bound to the port you specified during installation. The port number allows you to specify the same UDP and TCP port number on which the PATROL Agent will accept communications from PATROL Consoles.
Note
In PATROL Version 3.1 and above, the PATROL Console can communicate with each of its managed agents on different port numbers. This capability eliminates the need to start all PATROL Agents with the same port number, as required in PATROL Version 2.x.x. In PATROL Version 3.1 and above, the PATROL Agent binds to both the UDP port and TCP port specified by portNo. In PATROL Version 3.0, the PATROL Agent was bound only to the UDP port. You can set the PATROL Agent port number for all future sessions by using xpconfig or pconfig, the Agent configuration utilities described in the PATROL Agent Reference Manual.
5-6
If you are logged on as root, type exit and press Return. If your system requires you to use a session identifier, you must know the identifier before you perform this procedure. The identifier is an alphanumeric string that has been assigned by your PATROL administrator.
To Start a PATROL Console Step 1
Perform one of the following actions: cd to the PATROL installation directory to type the command in Step 2. Type the full path to the PATROL installation directory when you type the command in Step 2.
Step 2
Perform one of the following actions: To start the PATROL Developer Console, type the following command:
./Patrol -dev [-id <n>] [-p <portNo>] n represents the session identifier that has been assigned by your PATROL administrator and portNo is the UDP or TCP port number to add PATROL Agent hosts to the PATROL Console. The default is 1987.
You must be licensed for the Developer Console for the computer you want to start it on.
5-7
See the PATROL for Unix Getting Started manual for information about other startup options you can use. PATROL displays its identification dialog box.
Figure 5-1 PATROL Identification Dialog Box
Step 3 Step 4
Type the PATROL user name and password for the console. Click on OK to log in to PATROL.
5-8
Once PATROL is installed and configured and the PATROL Console is started, several tasks must be completed. Some tasks must be completed before you can use PATROL; other tasks must be completed only if you need to change your agent or PATROL Knowledge Module configuration.
Table 5-1 Tasks for Setting Up PATROL
5-9
Change directories (cd) to the PATROL installation directory. Type the following command at the operating system prompt and press Return:
% ./emcons
Information for using the PATROL Event Manager is provided in the PATROL Event Manager Console for Unix User Guide.
5-10
Change directories (cd) to the $PATROL_HOME directory. Follow the appropriate procedure. For Korn or Bourne shells, type the command below and press Enter.
. ./patrolrc.sh
5-11
Do not reset your system clock. This will cause the following message to be displayed: Error in license... Clock set back PATROL does not run in the demonstration mode if the system clock has been set back.
5-12
If the PATROL License dialog box is not already displayed, choose View => License in the PATROL Console main window. The PATROL License dialog box appears as shown in Figure 5-2.
Figure 5-2 PATROL License Dialog Box
When you agree to purchase a permanent PATROL license, BMC Software Contracts Administration can provide permanent license information to you by telephone or by fax.
Note
The password is a hexadecimal string. If a character looks like the letter O it is the numeral 0, if it looks like a lower case l, it is the numeral 1, and an upper case S is the numeral 5.
5-13
Step 2
Type the following information into the fields of the PATROL License dialog box to activate a permanent license.
Table 5-2 PATROL License Dialog Box Entry Fields What You Type . . .
company name leave blank for a permanent license number of PATROL Consoles stated by BMC Software Contracts Administration number of PATROL Agents stated by BMC Software Contracts Administration password provided by BMC Software Contracts Administration
Password
Step 3
When you have entered this information, click OK. Your permanent license will be activated.
Note
Your temporary or permanent product license password is generated and validated on the basis of the exact information in the applicable fields in the License dialog box. If you do not supply this information correctly, you will receive an error message.
Note
PATROL Developer Consoles, PATROL Operator Consoles, and PATROL Agents have different licenses and passwords. You may be required to use View=>License multiple times to enter the license information for the different products. Enter the information for the developer consoles first. See PATROL for Unix Getting Started for more information.
Step 4
Distribute the license.<hostname> file from a computer with a PATROL Console to each computer with a PATROL Agent. You can use ftp or the xpconfig utility to distribute the license. See the PATROL Agent Reference Manual for more information.
BMC Software, Inc., Confidential and Proprietary Information
5-14
Each license in the same file must be registered to the same name or company, and that name must correspond to the recognized password. Subsequent names entered for licenses in the same system are ignored. When you enter a new license in the dialog box, no new name is requested if any valid license exists.
Note
If no valid license exists on a system, a dialog box appears and asks for a license to be entered. If the name of the license file is simply license, it can be shared by more than one machine. If the name of the file is license.<hostname>, it belongs only to that host machine.
5-15
5-16
There are special considerations when you want to upgrade from one version of the PATROL products to another. This chapter describes these issues and provides suggestions for how to address them. It covers the following topics: Upgrade Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 PATROL Knowledge Module Deployment Server . . . . . . . . . . . 6-2 Compatibility Between Versions . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Migrating KM Customizations to a New Version of PATROL . . 6-2 PATROL KMDS histool Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 PATROL Cache Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 PATROL_CACHE Environment Variable . . . . . . . . . . . . . . . . . . 6-4
6-1
Upgrade Considerations
If you are upgrading to a new version of PATROL, there are several issues that you must keep in mind. The issues are addressed in very general terms in this guide.
6-2
Command
-help -allfile -allprod -config -prod <prod_name> -file <file_path> -base <dir_path> -v
What it Does...
Generates a list of commands and their results Displays all installed files Displays all installed products Displays configuration information Displays files included in the specified product Displays products installed referencing the specified file Required argument that specifies the location of the PATROL installation Displays the histool version and exits
6-3
6-4
This environment variable is useful when PATROL users share the same login account. If each user sets PATROL_CACHE to a different directory before starting the PATROL Developers Console, their changes will not affect anyone else. However, using the Commit menu command may affect other users changes if they are modifying the same KM files.
6-5
6-6
7-1
Place the CD labeled Browser for PATROL Help in the CD-ROM drive. Use the appropriate commands for your platform to mount the CD-ROM drive. Change directory (cd) to the appropriate language directory. The CD contains five subdirectories, each for a different language. For example, change to the En_us directory for English. Change to the Unix directory. Print and read the readme.txt file. Be careful. The readme.txt file can be confusing. For example, the readme.txt implies the files are in gzip format, but they are not. Change to the directory appropriate for your operating system. Copy the file or files in the directory to your system. Extract the Netscape files with the tar command and options appropriate for your operating system.
Step 2
Step 3
Step 4 Step 5
7-2
Step 9
Set environment variables as appropriate. See Setting the Required Environment Variables on page 7-3 for more information about environment variables.
LANG Variable
On some platforms, the Unix LANG environment variable must be set to C so that Netscape Navigator will work properly. Otherwise, you might experience unexpected product failures. Set your user or system .profile for Bourne or Korn shells as follows: LANG=C export LANG For C shell users, issue the following: setenv LANG C
PATH Variable
The PATROL user account PATH variable must contain the location of the directory containing the Netscape files. If the directory containing the Netscape files is not on the path, add the directory to the PATROL user account path.
7-3
This requirement applies only to the PATROL user account on the same computer as the PATROL Console.
PATROL_BROWSER Variable
When PATROL starts the help browser, it uses the command in the PATROL_BROWSER environment variable. As a default, the PATROL_BROWSER environment variable contains the following command: netscape -display SDISPLAY -install -iconic To use different arguments, set the value of PATROL_BROWSER to the appropriate string. For example,
export PATROL_BROWSER=/usr/local/bin/netscape -raise
Additional Considerations
When you select Help from the PATROL Console for Unix, it may take a few seconds for the help browser to launch. Two windows will appear. First the Netscape Navigator window appears as an icon, and then a help browser window that the help. In addition, you must be aware of the following restrictions: Netscape Navigator displays warning messages when it is invoked multiple times within the same user account because of its file-locking mechanism. It will, however, continue functioning.
7-4
By default, when Netscape Navigator starts, it uses a private color map. As a result, you might experience color flashing on your workstation. If so, you can set the value of PATROL_BROWSER so that the colormap option is not specified. Some subsequent color requests, however, might fail and the on-line help will be improperly displayed. The eXceed for Windows NT X Window Server product by Hummingbird Communication Ltd. may not always display the help files properly.
Consult your Netscape Navigator documentation and PATROL Release Notes for specific platform requirements and restrictions.
Additional Considerations
7-5
If you already have an Acrobat reader, ensure that your version is compatible with the PDFs on the PATROL documentation CD (currently version 3.0 or later).
7-6
This chapter presents information on how to install the PATROL products using the text-based installation program. The chapter consists of the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 CPU and Operating System Requirements for the Text-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Using the Text-Based Installation Program to Install or Uninstall PATROL Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Starting the Text-Based Installation Program . . . . . . . . . . . . . . . 8-5 Installing the PATROL Agent with the Text-Based Installation Program 8-8 Installing PATROL Knowledge Modules with the Text-Based Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21 UninstallingPATROL Productswith theText-Based Installation Program 8-31 Using a Batch File to Install or Uninstall PATROL Products . . . . . . 8-38 Building the Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39 Running the Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
8-1
Overview
The PATROL installation program with a graphical user interface is available only for those operating systems on which the PATROL Console is available. These systems are listed in Table 1-1, CPU and Operating System Version Requirements, on page 1-6. The text-based installation program is available to install PATROL products on the other Unix operating systems that PATROL supports. These systems are listed in CPU and Operating System Requirements for the Text-Based Installation Program on page 8-2. The PATROL Agent and some PATROL Knowledge Modules are available on these systems. The two installation programs differ in several areas, including their specific capabilities. The text-based installation program is available only for local installations. That is, you must be logged on to the computer where you want to use the text-based installation program to install PATROL products. You can use the text-based installation program to create a batch file for the installation and then run the batch file later to perform the installation at a more convenient time. In this chapter, the term installation program means the text-based installation program.
CPU and Operating System Requirements for the Text-Based Installation Program
Use the text-based installation program to install PATROL to the following systems. DG/UX DRS 6000 DRS NX Open Server Unixware
BMC Software, Inc., Confidential and Proprietary Information
8-2
Solaris-Intel M-RAS Reliant Unix Dynix/PTX IRIX Nonstop Unix Unisys Linux
Consult the current PATROL Console and PATROL Agent Release Notes for specific information regarding the supported versions of these operating systems. The PATROL Console and PATROL KMDS are not supported on these systems.
8-3
You can use the installation program to uninstall PATROL products on a local Unix workstation. The uninstall process removes most of the PATROL files. However, it leaves the directory structure intact, and it does not remove the history files and any other PATROL files that have been customized. If you want to remove the entire directory structure and all the files, including the files you have customized, use an appropriate Unix command. The installation program displays selection lists for you to specify the products you want to install. The items included on the selection lists are based on the contents on the installation CD. The selection lists you see as you use the text-based installation program may not match the lists on the examples included in this chapter. In addition, not all products are available on all platforms, so the selection lists may include products that are not available for the particular platform you want to install PATROL products on. This section contains the following procedures: Starting the Text-Based Installation Program on page 8-5 Installing the PATROL Agent with the Text-Based Installation Program on page 8-8 Installing PATROL Knowledge Modules with the Text-Based Installation Program on page 8-21 Uninstalling PATROL Products with the Text-Based Installation Program on page 8-31
8-4
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You can use command line options with the text-based installation program. See Using Installation Program Command Line Options on page C-1 for more information about the available options. If you are installing a patch, you must stop any PATROL processes that are running on the computers you want to install the patch on.
To Start the Text-Based Installation Program Step 1
Perform the step that applies to you. If you want to install the PATROL Agent or a patch for the PATROL Agent, insert and mount CD1. If you want to uninstall PATROL, insert and mount CD1. If you want to install PATROL KMs, insert and mount CD2.
Step 2
The installation program asks you to verify the path name of the location of the PATROL products you want to install and the path name of the location where you want the program to store log files. The path to the CD you mounted is given as the default for the source location. The default location for the log files is the patrolinstall directory within the home directory of the installation account. (See Figure 8-1.)
8-5
Figure 8-1
Step 3
Do one of the following: To accept the default paths, press Enter. The program displays the first part of the License Agreement. To specify different paths, type c and press Enter. The program displays the PATROL products path selection text and then the PATROL installation logfile path selection text. Press Enter to accept the current path or type a new path and press Enter. The program displays the first part of the License Agreement.
Step 4
Read the displayed portion of the agreement and press Enter. Continue to read and press Enter until you have read all of the License Agreement. The installation program displays the Accept License Terms text. See Figure 8-2.
Figure 8-2 Accept License Terms Text
8-6
Step 5
Type A to accept the agreement and press Enter. The installation program displays the Installation Operations text as shown in Figure 8-3.
Figure 8-3 Installation Operations Text
See...
Installing the PATROL Agent with the Text-Based Installation Program on page 8-8 Installing PATROL Knowledge Modules with the Text-Based Installation Program on page 8-21 Uninstalling PATROL Products with the Text-Based Installation Program on page 8-31 the PATROL Migration Tools User Guide Using a Batch File to Install or Uninstall PATROL Products on page 8-38
8-7
Installing the PATROL Agent with the Text-Based Installation Program Summary:
This task describes how to install the PATROL Agent on a Unix computer using the text-based installation program.
Yes
No
Type 2
Type 1
Unmount the CD
8-8
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You must have completed the procedures described in Starting the Text-Based Installation Program on page 8-5. You will begin this procedure with the Installations Operations text. Be sure you are using CD1 for Unix.
To Install the PATROL Agent with the Text-Based Installation Program Step 1
On the Installations Operations text, type 1 (Install PATROL) and press Enter. The installation program displays the Product Selection text, shown in Figure 8-4.
Figure 8-4 Product Selection Text
Step 2
Type 1 and press Enter. The installation program displays the Main Product List text. The contents of this text may vary depending on the installation CD you are using. An example text is shown in Figure 8-5.
8-9
Figure 8-5
Step 3
Type the number for the PATROL Agent (3 in the example figure) and press Enter.
Note
The order of the product list shown in Figure 8-5 may differ from the product list that you are currently viewing. The installation program displays the PATROL Agent text as shown in Figure 8-6.
Figure 8-6 PATROL Agent Text
Step 4
Type the number of the PATROL Agent for Unix (1 in the example figure) and press Enter. The installation program redisplays the PATROL Agent text with an asterisk by Agent for UNIX and with an estimate of the space required to install the agent you have selected.
BMC Software, Inc., Confidential and Proprietary Information
8-10
Step 5
Type B and press Enter. The installation program redisplays the Main Product List text showing how many products are selected. See Figure 8-7.
Figure 8-7 Main Product List Text
Step 6
The order of the product list shown in Figure 8-7 may differ from the product list that you are currently viewing. The installation program returns to the Product Selection text and shows how many products have been selected as shown in Figure 8-8.
Figure 8-8 Product Selection Text
Step 7
8-11
Ordinarily, the installation program automatically selects the appropriate version of the program files to install, based on the operating system of the computer you want to install to. To accept the automatic selection of operating system, type N and press Enter. The installation program displays the Destination Directory text as shown in Figure 8-10 on page 8-14. Go to Step 11 on page 8-14. To override the installation programs automatic selection, type A and press Enter. The installation program displays the Override OS text as shown in Figure 8-9. Go to Step 8 on page 8-12. The list of available operating systems depends on the contents of the CD you are using to install. It may be longer than can in your window. Press Enter or type N and press Enter to scroll forward through the list of operating systems. Type B and press Enter to scroll backwards through the list of operating systems.
Step 8
On the part of the Override OS text has the Select Desired Operation prompt, type the number of the operating system version of the program files you want to install and press Enter.
8-12
Figure 8-9
Override OS Text
The installation program displays the Override OS text again with the operating system marked with an asterisk.
Step 9
Type B on the Override OS text and press Enter. The installation program returns to the Product Selection text.
Step 10
Type N and press Enter to continue to the next step. The installation program displays the Destination Directory text as shown in Figure 8-10.
8-13
The destination directory is the directory where the PATROL products will be installed.
Step 11
Perform the step that applies to you. To accept the default directory, type N and press Enter. The installation program displays the Account Information text as shown in Figure 8-12 on page 8-15. Go to Step 14 on page 8-16. To change the destination directory, type C and press Enter. The installation program redisplays the Destination Directory text with a prompt for you to type the name of the directory you want to use, as shown in Figure 8-11. Go to Step 12 on page 8-15.
8-14
Step 12
Type the name of the directory you want to use to install the PATROL products and press Enter. The installation program redisplays the Destination Directory text with the new directory shown as the current selection.
Step 13
Type N and press Enter. The installation program displays the Account Information text as shown in Figure 8-12.
Figure 8-12 Account Information Text
8-15
Step 14
Type 1 and press Enter. The installation program displays a revised Account Information text that prompts you to type the username and the password and then to verify the password by typing it again. See Figure 8-13.
Figure 8-13 Account Information Text
Step 15
Type the username and password in response to the prompts and press Enter after each entry. The installation program displays the Root Password text as shown in Figure 8-14. The installation program uses the root password to configure and start the PATROL Agent.
Figure 8-14 Root Password Text
Step 16
8-16
If you want to manually configure PATROL using the configure.sh script, type N and press Enter. After the installation is finished and before you can use PATROL, you must log on as root and configure the PATROL Agent using the configure.sh script. To have the installation program configure the Agent, type 1 and press Enter.
Step 17
Determine what to do based on your action for the Root Password text. If you typed N, the installation program displays the Optional Command File Selection text shown in Figure 8-18 on page 8-19. Go to Step 21 on page 8-19. If you typed 1, the installation program displays a revised Root Password text that prompts you to type the root password and then to verify the password by typing it again as shown in Figure 8-15. Go to Step 18 on page 8-17.
Step 18
Type the password in response to the prompts and press Enter after each entry. The installation program displays the Agent Startup text as shown in Figure 8-16.
8-17
Step 19
Perform the step that applies to you. If you do not want the installation program to start the Agent, type N and press Enter. If you want the installation program to start the Agent, type Y and press Enter. Whether you type N or Y, the installation program displays the Port Override text as shown in Figure 8-17. The port you select on this text is the default port number the agent uses to communicate with the console.
Figure 8-17 Port Override Text
Valid port numbers are four-digit or five-digit integers greater than 1024. The default port is 1987. Check your /etc/services file or NIS (Network Information Service) for ports already in use by system services. Always choose a port number that is not already in use.
Step 20
Press Enter to accept the default agent port number (1987) or type the new agent port number and press Enter to change the agent port number.
BMC Software, Inc., Confidential and Proprietary Information
8-18
The installation program displays the Optional Command File Selection text as shown in Figure 8-18.
Figure 8-18 Optional Command File Selection Text
Step 21
Perform the step that applies to you. To install the PATROL Agent now, type 1 and press Enter. The installation begins and displays status messages as shown in Figure 8-19. The specific messages depend on the details of your installation and system. When the installation is complete, the installation program tells you the next steps so you can install the PATROL Knowledge Modules.
Figure 8-19 Install Status Text
To save a batch file to install the agent later, type 2 and press Enter.
8-19
The installation program displays the Command File Selection text. Go to Building the Batch File on page 8-39 for instructions for saving and using batch files.
Step 22
See...
Installing PATROL Knowledge Modules with the Text-Based Installation Program on page 8-21 Running the Batch File on page 8-42
8-20
Installing PATROL Knowledge Modules with the Text-Based Installation Program Summary:
This task describes how to install PATROL KMs on Unix computers using the text-based installation program.
Yes
No
Type 2
Type 1
Unmount the CD
8-21
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You must have installed the PATROL Agent as described in Installing the PATROL Agent with the Text-Based Installation Program on page 8-8. You must have completed the procedures described in Starting the Text-Based Installation Program on page 8-5. You will begin this procedure with the Installations Operations text. Be sure you are using CD2 for Unix.
To Install the PATROL Knowledge Modules with the Text-Based Installation Program Step 1
On the Installations Operations text, type 1 (Install PATROL) and press Enter. The installation program displays the Product Selection text, shown in Figure 8-20.
Figure 8-20 Product Selection Text
Step 2
Type 1 and press Enter. The installation program displays the Main Product List text, shown in Figure 8-21.
8-22
Step 3
Type the number for PATROL Knowledge Modules (1 in the example figure) and press Enter. The installation program displays the PATROL Knowledge Modules text. The list of available PATROL Knowledge Modules depends on the contents of the CD you are using to install. There may be more KMs than can be shown in your window. Figure 8-22 shows one part of a PATROL Knowledge Modules list.
Figure 8-22 PATROL Knowledge Module Text
You can type N and press Enter or type P and press Enter to scroll forward and backwards through the list of PATROL Knowledge Modules.Type B and press Enter to return to the Main Product List text.
BMC Software, Inc., Confidential and Proprietary Information
8-23
Step 4
Type the number for the PATROL Knowledge Module you want to install and press Enter. The installation program redisplays the PATROL Knowledge Module text with an asterisk by the KM you selected and with an estimate of the space required to install all the KMs you have selected.
Step 5 Step 6
Continue to select all the KMs that you want to install. Type B and press Enter to return to the Main Product List text. The installation program redisplays the Main Product List text showing the number of KMs you have selected.
Step 7
Type B and press Enter. The installation program returns to the Product Selection text and shows how many products have been selected as shown in Figure 8-23.
Figure 8-23 Product Selection Text
Step 8
Perform the step that applies to you. By default, the installation program automatically selects the appropriate version of the program files to install, based on the operating system of the computer you want to install to. To accept the automatic selection of operating system, type N and press Enter. The installation program displays the Destination Directory text as shown in Figure 8-25 on page 8-26. Go to Step 12 on page 8-26.
BMC Software, Inc., Confidential and Proprietary Information
8-24
To override the installation programs automatic selection, type A and press Enter. The installation program displays the Override OS text as shown in Figure 8-24. Go to Step 9 on page 8-25. The list of available operating systems depends on the contents of the CD you are using to install. It may be longer than can be shown in your window. Press Enter or type N and press Enter to scroll forward through the list of the operating systems. Type B and press Enter to scroll backwards through the list of the operating systems.
Step 9
On the part of the Override OS text has the Select Desired Operation prompt, type the number of the operating system version of the program files you want to install and press Enter.
Figure 8-24 Override OS Text
The installation program displays the Override OS text again with the operating system marked with an asterisk.
Step 10
Type B on the Override OS text and press Enter. The installation program returns to the Product Selection text.
Step 11
The installation program displays the Destination Directory text as shown in Figure 8-25.
Figure 8-25 Destination Directory Text
The destination directory is the directory where the PATROL products will be installed.
Step 12
Perform the step that applies to you. To accept the default directory, type N and press Enter. The installation program displays the Account Information text as shown in Figure 8-27 on page 8-27. Go to Step 15 on page 8-28. To change the destination directory, type C and press Enter. The installation program redisplays the Destination Directory text with a prompt for you to type the name of the directory you want to use, as shown in Figure 8-26. Go to Step 13 on page 8-27.
8-26
Step 13
Type the name of the directory you want to use to install the PATROL products and press Enter. The installation program redisplays the Destination Directory text with the new directory shown as the current selection.
Step 14
Type N and press Enter. The installation program displays the Account Information text as shown in Figure 8-27.
Figure 8-27 Account Information Text
8-27
Step 15
Type 1 and press Enter. The installation program displays a revised Account Information text that prompts you to type the username and the password and then to verify the password by typing it again. See Figure 8-28.
Figure 8-28 Account Information Text
Step 16
Type the username and password in response to the prompts and press Enter after each entry. The text that the installation program displays depends on the products you selected. If the products you selected require the root password for proper configuration, the installation program displays the Root Password text as shown in Figure 8-29. Go to Step 17 on page 8-29. If the products you selected do not require the root password for proper configuration, the installation program displays the Optional Command File Selection Text as shown in Figure 8-30. Go to Step 18 on page 8-30.
8-28
Step 17
Perform the step that applies to you. If the products you selected require the root password for proper configuration and you want to manually configure PATROL using the configure.sh script, type N and press Enter. After the installation is finished and before you can use PATROL, you must log on as root and configure the PATROL products using the configure.sh script. The installation program displays the Optional Command File Selection text shown in Figure 8-30 on page 8-30. Go to Step 18 on page 8-30. If the products you selected require the root password for proper configuration and you want the installation program configure the products, type 1 and press Enter. The installation program displays a revised Root Password text that prompts you to type the root password and then to verify the password by typing it again. The installation program displays the Optional Command File Selection text as shown in Figure 8-30.
8-29
Step 18
Perform the step that applies to you. To install the PATROL KMs now, type 1 and press Enter. The installation begins and displays status messages as shown in Figure 8-31. The specific messages depend on the details of your installation and system.
Figure 8-31 Install Status Text
To build a batch file to install the KMs later, type 2 and press Enter. The installation program displays the Command File Selection text. Go to Building the Batch File on page 8-39 for instructions for saving and using batch files.
Step 19
8-30
Yes
Type 1
Unmount the CD
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18.
8-31
You must stop any PATROL processes that are running on the computers where you want to uninstall PATROL. See the PATROL for Unix Getting Started Guide, the PATROL Agent Reference Manual, and the PATROL Knowledge Module Deployment Server Manager User Guide for information on stopping PATROL processes. Be sure you are using CD1 for Unix.
Follow the instructions in Starting the Text-Based Installation Program on page 8-5. When you have completed the procedure, the Installation Operations text appears.
Step 1
On the Installations Operations text, type 2 (Uninstall PATROL) and press Enter. The installation program displays the Destination Directory text as shown in Figure 8-32. The destination directory is the directory where the PATROL products that you want to uninstall are located.
Figure 8-32 Destination Directory Text
8-32
Step 2
Perform the step that applies to you. To accept the default directory, type N and press Enter. The installation program displays the Account Information text as shown in Figure 8-34 on page 8-34. Go to Step 5 on page 8-34. To change the destination directory, type C and press Enter. The installation program redisplays the Destination Directory text with a prompt for you to type the name of the directory you want to use, as shown in Figure 8-33. Go to Step 3 on page 8-33.
Figure 8-33 Destination Directory Text
Step 3
Type the name of the directory you want to uninstall the PATROL products from and press Enter. The installation program redisplays the Destination Directory text with the new directory shown as the current selection.
Step 4
Type N and press Enter. The installation program displays the Account Information text as shown in Figure 8-34.
8-33
Step 5
Type 1 on the Account Information text and press Enter. The installation program displays revised Account Information text that prompts you to type the username and the password and then to verify the password by typing it again.
Note
The user name and password must be the same as the account that you used to start the installation program.
Step 6
Type the username and password in response to the prompts and press Enter after each entry. The installation program displays the Root Password text as shown in Figure 8-35. The installation program uses the root password to stop any running PATROL processes. If you do not supply the password, the program may not be able to uninstall the PATROL products that are running.
8-34
Step 7
Perform the step that applies to you. To continue without the root password, type N and press Enter. The installation program displays the Optional Command File Selection text shown in Figure 8-37 on page 8-36. Go to Step 9 on page 8-36. To supply the password so the installation program can stop any PATROL processes, type 1 and press Enter. The installation program displays a revised Root Password text that prompts you to type the root password and then to verify the password by typing it again. The installation program displays the Port Override text as shown in Figure 8-36.
Figure 8-36 Port Override Text
8-35
Step 8
Press Enter to accept the default agent port number (1987) or type the new agent port number and press Enter to change the agent port number. The installation program displays the Optional Command File Selection text as shown in Figure 8-37.
Figure 8-37 Optional Command File Selection Text
Step 9
Perform the step that applies to you. To uninstall the PATROL products now, type 1 and press Enter. The installation begins and displays status messages as shown in Figure 8-38. The specific messages depend on the details of your installation and system.
Figure 8-38 Install Status Text
To build a batch file to uninstall the PATROL products later, type 2 and press Enter.
8-36
The installation program displays the Command File Selection text. Go to Building the Batch File on page 8-39 for instructions for saving and using batch files.
Step 10
8-37
8-38
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You must have completed the procedures described in Starting the Text-Based Installation Program on page 8-5.
Step 2
When the installation program displays the Optional Command File Selection text, type 2 (Save command file) and press Enter. The installation program displays the Command File Selection text, shown in Figure 8-39.
8-39
Step 3
Perform the step that applies to you. To change the name of the command file, type C and press Enter, then type the new name for the command file and press Enter again. The installation program redisplays the Select the name of the command file text with the new name. To accept the name of the command file, type N and press Enter. The installation program creates the batch file in the directory you specified as the logfile directory and displays the Install Status text. The messages on this text depend on the type of installation you want to perform and on the specific details of your system. An example of Install Status text is shown in Figure 8-40.
Figure 8-40 Install Status Text
8-40
For more information on using the batch file, see Running the Batch File on page 8-42.
8-41
You must have completed the procedures described in Preparing to Install PATROL Products on page 1-18. You must have completed the procedures described in Building the Batch File on page 8-39. You can use either PATROL for Unix CD1 or CD2 for running the batch file. The batch file operation does not require user input, so you can execute the batch file as an unattended process. If the batch file will install a patch, you must stop any PATROL processes that are running on the computers you want to install the patch on.
The variable file_name represents the name of the batch file you created in the procedure Building the Batch File on page 8-39. The variable operation_type represents the type of installation the batch file will perform. Valid operation types are install and uninstall. You can use uppercase or lowercase letters for the operation type. The installation program performs the installation operation defined by the batch file.
BMC Software, Inc., Confidential and Proprietary Information
8-42
Step 2
8-43
8-44
A
A
The PATROL Console and PATROL Agent create several files on the PATROL hosts disk drive. These files are automatically generated at run time and range from temporary files used for error logging to permanent files that store historical information. This appendix provides information for system administrators to use in periodically managing the PATROL files. Note which files are required and which can be removed safely. PATROL Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Files Used by the PATROL Console . . . . . . . . . . . . . . . . . . . . . A-4 Files Used by the PATROL Agent . . . . . . . . . . . . . . . . . . . . . . . A-5 $PATROL_HOME Directory Structure . . . . . . . . . . . . . . . . . . . . . . A-6 $PATROL_HOME/log/history Parameter History Directory . . A-6 $PATROL_HOME/log/PEM_<hostname>_<portnumber>.log and .archive Permanent Event Log Files. . . . . . . . . . . . . . . . . . . . A-7 $PATROL_HOME/log/PatrolAgent-<hostname>_ <portnumber>.errs.~<iter>~ Files . . . . . . . . . . . . . . . . . . . . . A-8 $HOME/patrol Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . A-8 $HOME/patrol/chart, desktop Directories . . . . . . . . . . . . . . . . . A-9 $HOME/patrol/psl User-written PSL Scripts Directory . . . . . . A-9 $HOME/patrol/knowledge/session-<id> Session Information Files A-10 $HOME/patrol/tmp/Patrol-<id>.errs.~<iter>~ Log Files . . . . . A-10 /tmp/patrol Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 /tmp/patrol/PEM_<hostname>_<portnumber>.log.lock Temporary Lock Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
BMC Software, Inc., Confidential and Proprietary Information
A-1
A-2
PATROL Directories
PATROL uses four main directories to store information. Table A-1 summarizes those directories.
Table A-1 Summary of PATROL Main Directories
Directory Name
$PATROL_HOME
General Content
A sub directory of the installation directorybinaries, knowledge, sounds, images, application defaults, help, utilities, and parameter histories The actual name of the $PATROL_HOME directory depends on the type of installation. For example, the name for an installation of PATROL 3.3 on an HP Unix computer would be /patrol/PATROL3.3/HPUX-PA1.0-V10
$HOME/patrol
Console error logs, custom PSL scripts, custom knowledge, customized charts, console swap files, console desktop layout files, and custom Standard Event Catalog The actual name of the $HOME/patrol directory depends on the specific installation. A typical name of the $HOME/patrol directory is /usr/patrol/<userid>
/tmp/patrol
Event Manager lock files for all PATROL Agents running on a host
PATROL Directories
A-3
File Name
$PATROL_HOME/bin $PATROL_HOME/lib/app-defaults/help $PATROL_HOME/lib/app-defaults/Patrol $PATROL_HOME/lib/app-defaults/XKeysymDB $PATROL_HOME/lib/images $PATROL_HOME/lib/sounds $PATROL_HOME/lib/knowledge/StdEvents.ctg $PATROL_HOME/lib/psl
Description
Binary directory Directory of help files File of Consoles X Windows resources File of Consoles keyboard binding Directory of icons and background pixmaps Directory of sounds and phrases in different languages PATROL Event Manager Standard Event Catalog Directory for BMC supplied PSL and OS scripts (and other user-defined command types) Directory for BMC supplied versions of KMs Directory for the Charting Server Directory for the Agent configuration changes Directory to store the Console desktop Directory for user-written/modified PSL and OS scripts (and other user-defined command types) Directory for user-written/modified KMs File that is your default list of KMs loaded by the Console File of user preferences Layout files for a particular Console ID Lock on a particular Console ID Files caching events for the PATROL Event Manager
BMC Software, Inc., Confidential and Proprietary Information
A-4
Table A-2
File Name
$HOME/patrol/tmp/Patrol-<id>.errs.~<iter>~ /tmp/patrol/evcache.log-<iter>.lock
Description
Files containing Console error messages Lock on Event Manager log file
File Name
$PATROL_HOME/bin $PATROL_HOME/lib/config.default
Description
Binary directory Agent startup default configuration file Standard Events Catalog Directory of message catalogs Directory for shipped PSL and OS (and other KM-defined command types) scripts Directory for shipped KMs and Standard Events Catalog File created temporarily during a Commit operation Agent configuration files History file and indices Files containing all events for the PATROL Event Manager Lock on an Event Manager file File containing Agent error messages, etc.
$PATROL_HOME/lib/knowledge
$PATROL_HOME/lib/commit.lock
PATROL Directories
A-5
$PATROL_HOME bin
A-6
The recommended procedure is to use the PATROL History Loader Knowledge Module to transfer and store the parameter history in a database, such as Oracle or Sybase, for permanent storage and utilization. You can override the location of the parameter history directory by setting the PATROL_HISTORY environment variable. You can also modify the history retention period through the User Preferences dialog box. Refer to the PATROL for Unix User Guide for more information.
A-7
A-8
Figure A-2
chart desktop
psl
knowledge tmp
The following topics, presented alphabetically by path name, describe the $HOME/patrol files and subdirectories.
A-9
When searching for a PSL script, the PATROL Console checks this directory first. You can change the location of user-written PSL scripts and knowledge modules by setting the PATROL_LOCAL_PSL_APPS environment variable. Refer to the PATROL for Unix User Guide for more information. If you have not committed these files to your agents, do not delete them unless you want to delete any modifications or additions to the standard PATROL Knowledge Modules you are using.
Selecting the Save option from the file menu creates these files. If you remove these files, the next time you start the PATROL Console, it reverts to the default values supplied on the distribution medium.
A-10
The value of <id> specifies different Console sessions that you started with the -id option. For example, console log file names can be as follows:
$HOME/patrol/tmp/Patrol-1.errs.~1~ $HOME/patrol/tmp/Patrol-2.errs.~1~
The value of <iter> increases in increments for successive runs that are using the same <id> value. These files can be safely deleted from time to time after you have resolved any problems described in the logs.
/tmp/patrol Directories
/
tmp patrol
A-11
PATROL3.3KMDS annotate cache checkin checkout download install lib tbldata xpm <Unix operating system>
bin app-defaults help nls
PATROL3.3KMDS\tbldata
The PATROL3.3KMDS\tbldata directory contains .tab files.
A-12
PATROL3.3KMDS\lib
The PATROL3.3KMDS\lib directory contains three subdirectories. They are:
app-defaults help nls
A-13
A-14
This appendix describes how to use PATROL in environments that have a firewall between the PATROL Consoles and PATROL Agents or between the PATROL KMDS and other PATROL components. It is intended for system administrators who can tailor their site environment to make effective use of PATROL products. Depending on your type of firewall and the location of your PATROL Consoles, Agents, and PATROL KMDS relative to your firewall, you might need to modify your firewall protection to use PATROL. This chapter presents the following topics: Types of Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2 PATROL Agent/Console Communication Basics . . . . . . . . . . . . . . .B-2 Reliable UDP-Based Transport . . . . . . . . . . . . . . . . . . . . . . . . . .B-3 TCP-Based Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4 PATROL KMDS Communication Basics. . . . . . . . . . . . . . . . . . . . . .B-5
B-1
Types of Firewalls
The first level of defense in a network firewall comes from a filtering router. These routers filter incoming and outgoing traffic according to the filters protocol and source and destination addresses (IP address plus port number). As a second level of defense, many companies introduce a firewall computer that sits directly behind the filtering router and acts as the single point of exit from and entry into the companys network. The firewall computer runs special proxy servers, and users connect to services outside of the company using these servers. The filtering router is configured to block outgoing traffic that does not originate from the firewall computers IP address and to block incoming traffic that is not addressed to the firewall computers IP address. PATROL can be used with both types of firewalls; however, if you use a firewall computer, you must allow communications among PATROL Consoles and PATROL Agents across the firewall. The extent to which you need to modify your firewall protection is determined by the transport protocol you use between the PATROL Consoles and PATROL Agents and the location of your PATROL Consoles and PATROL Agents relative to the firewall.
B-2
UDP port 1988 will be used by the PATROL Console process, and UDP port 1989 will be used by the PATROL Agent configuration process. The router must have one additional filter defined on each of its two interfaces to allow the PATROL Consoles and PATROL Agents to communicate through the firewall. Your router filter tables might look like those shown in the paragraphs that follow. On the interface to the outside world (the PATROL Consoles network), the following filter is needed:
BMC Software, Inc., Confidential and Proprietary Information
B-3
# Allow Source # |Deny IP/port/proto Deny */*/* Allow */*/* Allow */1988/UDP Allow */1989/UDP
Destination IP/port/proto */*/* firewall/*/* */1987/UDP */1987/UDP # # # # Default: deny all To firewall Console-> Agent Agent Config-> Agent
On the interface to the PATROL Agents network, the following filter is needed:
# Allow Source # |Deny IP/port/proto Deny */*/* Allow firewall/*/* Allow */1987/UDP Allow */1987/UDP
# # # #
Default: deny all From firewall Agent-> Console Agent-> Agent Config
The firewall is only marginally weakened by the addition of the PATROL filters. The source and destination port numbers are fixed. You can even further restrict the PATROL traffic allowed through the firewall by including the IP address of your PATROL Console machine in the filter. If you have several consoles, you can include the network number of the network where your PATROL Consoles are running in the filters.
TCP-Based Transport
As with the UDP-based transport, the PATROL Agent binds to a fixed TCP port number. Unfortunately, this port number is used only in the TCP connection protocol. Once a connection has been established, a new pair of pseudo-random port numbers is assigned to the connection. All traffic over the connection is addressed to these ports. This makes it virtually impossible to create filters to allow only the PATROL traffic through the firewall as was discussed previously for UDP.
B-4
PATROL does not support proxies so the only way to use PATROL across a firewall with TCP is to open TCP traffic on all ports above 1500 or, rather, deny traffic on ports below 1500 and traffic on any ports above 1500 that you use for specific services. This basically reduces your firewall to the same level of protection that you get from using a filtering router without a firewall computer. You can block telnets, ftps, and so forth from outside the firewall or restrict them to a single machine, but you are not protected from more malicious attacks such as denial of service attacks.
Start the PATROL KMDS Command Line Interface (CLI) with the following command line:
DsCli -lp 2254
B-5
DsServer -p 2252
To allow the PATROL Console to communicate with the PATROL KMDS, start the console with the following command line:
Patrol -lkp 2255
Use the following filter on the PATROL KMDS Manager/CLI/Console side of the interface.
# Action Source Destination # Allow|Deny IP/port/protoIP/port/proto Deny */*/* */*/* Allow */*/* firewall/*/* Allow */2253/UDP */2252/UDP Allow */2254/UDP */2252/UDP Allow */2255/UDP */2252/UDP
#Comment # # # # # Default: deny all To firewall Manager-> PATROL KMDS CLI-> PATROL KMDS Console-> PATROL KMDS
Use the following filter on the PATROL KMDS side of the interface.
# Action Source Destination # Allow|Deny IP/port/protoIP/port/proto Deny */*/* */*/* Allow */*/* firewall/*/* Allow */2252/UDP */2253/UDP Allow */2252/UDP */2254/UDP Allow */2252/UDP */2255/UDP
#Comment # # # # # Default: deny To firewall PATROL KMDS-> PATROL KMDS-> PATROL KMDS-> all Manager CLI Console
B-6
C-1
Option
-debug -rnc_debug -nonslookup
Description
Toggles the display of details about internal operations for remote installations. The information may be useful in problem tracking. Toggles the display of details about internal operations for local installations. The information may be useful in problem tracking. Turns off the nslookup of available hosts. Use this option if you are performing a local install, there is a problem with using nslookup, or if the list of available hosts is very long. If you use this option, the installation program will not put the names of available hosts in the Select Hosts window. Turns on the nslookup of available hosts. Use this option if you want the installation program to put the names of available hosts in the Select Hosts window Adjusts the GUI dialog box size for screens with a resolution of 800 x 600 or less. Specify the dimensions of the GUI dialog boxes as follows: <x dimension>x<y dimension>+<x offset>+<y offset> For example: -wingeometry 600x300+10+10 Use the -override option if the buttons are cropped on the installation program dialog boxes For example: -wingeometry -override
-nslookup
-wingeometry <dimensions>
Sets the default port for the PATROL Agent. The default can be changed on the Agent Information dialog box during the installation. Sets the internal port for ISI/RNC communications. You should only use this option as directed by BMC Software support.
C-2
Table C-1
Option
-KMDSportnum <port> -batchfileonly
Description
Sets the default port for the PATROL KMDS. If you do not use this option, the default is 2252. Creates a text file of installation commands. You should only use this option as directed by BMC Software support. The text file may be useful in problem tracking. See Appendix D, Installation Troubleshooting, for more information. Starts the installation program in the distribute mode. See the PATROL Knowledge Module Deployment Server Manager User Guide for more information about the distribute process. Points the installation program to a product image other than the one the program was launched from. Use to correct ISI/RNC communications timeout problems. See Appendix D, Installation Troubleshooting, for more information. Use to correct ftp timeout problems. See Appendix D, Installation Troubleshooting, for more information. Use to correct problems with port conflicts. See Appendix D, Installation Troubleshooting, for more information.
-distribute
C-3
Option
-rnc_debug -agentportnum <port> -RNCportnum <port> -cdpath <path> -batchfile -operation <type>
Description
Toggles the display of details about internal operations. The information may be useful in problem tracking. Sets the default port for the PATROL Agent. The default can be changed on the Agent Information text during the installation. Sets the internal port for ISI/RNC communications. See Appendix D, Installation Troubleshooting, for more information. Points the installation program to a product image other than the one the program was launched from. Tells the installation program to use a batchfile as the source for installation specifics and identifies the batchfile to use. Used only with the -batchfile option. Tells the installation program what type of installation to use. The arguments for this option are install and uninstall. Use to correct ISI/RNC communications timeout problems. See Appendix D, Installation Troubleshooting, for more information. Use to correct ftp timeout problems. See Appendix D, Installation Troubleshooting, for more information.
C-4
D
1 1
Installation Troubleshooting
This appendix describes the most common error messages and problems you may encounter when installing PATROL products and discusses the causes for the errors. The descriptions include suggested solutions for resolving the problems. If you cannot resolve the installation problems using the information in this appendix, consult BMC Software Support. Overview of Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Batch File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reviewing the logfile<pid> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnosing Specific Issues with FTP . . . . . . . . . . . . . . . . . . . . . . . . Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2 D-4 D-6 D-6 D-7 D-8 D-9
Installation Troubleshooting
D-1
D-2
6. Using the telnet session, the installation program executes target.sh -e to find the host type and the suffix of rncinst that it needs to send to the target host. ftp and telnet must land in the same home directory. 7. Using the telnet session, the installation program deletes target.sh. 8. Using the telnet session, the installation program determines if the install target directory exists. If it does not exist, it creates the target directory. 9. The installation program creates the following directories on the source host: $HOME/patrolinstall $HOME/patrolinstall/batchfiles $HOME/patrolinstall/hostlists $HOME/patrolinstall/logs $HOME/patrolinstall/prodlists
10. In the ftp session, the installation program changes directory to the install target directory and deploys the appropriate rncinst file in that directory. rncinst is the RNC install executable that listens on port 5146 for attempts by the ISI to connect.The RNC receives and distributes the files from the ISI. 11. Using the telnet session, the installation program changes permission of the rncinst file to make it executable, and then runs the rncinst. 12. The ftp and telnet sessions to the target host are closed. 13. The installation program starts the appropriate isiinst from the source host. isiisnst contacts rncinst running on the target host and sends products over to the rncinst based on the information saved in step 1. 14. rncinst places the files in the appropriate directories. 15. For console and agent installations, the RNC attempts to login as root by executing a straight telnet as root. If the login is successful, the RNC executes configure.sh.
BMC Software, Inc., Confidential and Proprietary Information
D-3
Requirements Checklist
Table D-1 provides a checklist of requirements to consult if the installation does not go as planned. Some of the requirements have troubleshooting tips to help you resolve issues for those requirements.
Table D-1 Requirements and Troubleshooting Tips for the Installation Program Troubleshooting Tip
Requirement Network connectivity between the machines including hostname resolution, ping, telnet, ftp, etc. The network must have enough bandwidth to allow the ISI to communicate with the RNC without timing out.
If this is the problem, the time-out will be visible in the debug output in the debug<pid> log file. The default time-out values (10 seconds) can be overridden by using the -timeout and -ftpsleep options when executing install.sh. Note: The system administrator can institute an auto-timeout feature that causes ftp and telnet to exit if there is no activity within some number of seconds. The auto-timeout will take precedence over the -timeout and -ftpsleep options. In order to change the time-out period, you must supply a value that is greater than 10 but less than the auto-timeout value. It might be necessary to get the system administrator to increase the value of auto-timeout in order for the PATROL installation to be successful.
Login access to installation and root accounts. Telnet access is required to the target host using both the PATROL account and the root account.
Confirm account names, passwords and access rights for the installation account and the root account. Consult BMS Software Support if telnet to the installation account or root account is prohibited from remote access.
A telnet login to the installation account must land at a Unix prompt and not use interactive methodology to verify access.
D-4
Table D-1
Requirements and Troubleshooting Tips for the Installation Program Troubleshooting Tip
Requirement The passwords for the installation account and root account cannot contain special characters such as @ or $. The installation account must be set up with the proper shell and granted ftp access to the target host. (remote installation only) Sufficient disk space (including disk quotas) must be available on the target host to install all selected products. Sufficient disk space (including disk quotas) must be available in /tmp directory on the target host to handle the temporary files that are created during the installation. Sufficient disk space (including disk quotas) must be available on the source directory in the $HOME of the user executing install to accommodate installation log files. Write access is required to the following locations on the target host: the installation directory the home directory of the PATROL account on the target host the /tmp directory Write access is required to the following location on the source host: to the $HOME directory of the user performing the installation Port 5146 must be available on both the source and target hosts.
See the product selection dialog box for an estimate of the space required to install the products you select.
By default, the PATROL Unix installation program uses port 5146. Use the command netstat -na | grep 5146 on both the source and target hosts to look for possible port conflict. You can overwrite the default port by using the -RNCportnum option.
Requirements Checklist
D-5
Table D-1
Requirements and Troubleshooting Tips for the Installation Program Troubleshooting Tip Verify there are no commands setting the TARGET environment variable in the accounts .profile, .cshrc, .login, .kshrc, .bashrc, and /etc/profile files. Make sure TARGET environment variable is unset. Verify that the installation account does not have a cd command in its .cshrc or .profile file that causes telnet session to land in directory different from the home directory.
Requirement TARGET and any other PATROL environment variable must not be set from a previous PATROL target script.
Installation Logs
During the installation, the following log files are created in the $HOME/patrolinstall/logs directory on the source host:
InstallLog_<hostname><pid> is the Install Side Interface (ISI) debug log that is created for each target hostname. This file contains information about the steps that install is performing.
D-6
logfile<pid> contains a quick summary of the major steps attempted during install and shows success or fail for each. debuglog<pid> is created only if the -debug (for remote installations)
or -rnc_debug (for local installations) option is used when executing the install script. The debug output contains expect code seen and returned during the installation process. The log files include the process identification number (<pid>) as part of the file name. However, it may be easier to determine the log files for the most recent installation by checking the time and date stamp on the files. The following log file is created in the installation directory on the target host:
InstallLog_<hostname> is the RNC Log and is installed in the
D-7
Table D-2
Sample logfile<pid>
Explanation
Results of a ping to the target host. If the ping fails, then the installation fails. Results of a test to see ftp can be performed from the source host to the target host. If ftp fails, then the installation fails. Indicates the target platform on the target host. Reports if the installation directory already exists on the target host. The installation directory is created if it did not already exist. A failure or warning may be seen if the directory already exists. Indicates the success or failure of deploying the RNC component, rncinst.<os platform> rncinst.s27 is for a Solaris 2.7 platform. The installation of directories and files finished and exited successfully. The ISI process has finished and exited successfully. The RNC component has been terminated. Termination occurs for both success and failure. Statement that the installation has either completed successfully or failed.
Host topdog target type is Solaris27-sun4 Host topdog subdirectory /opt/KMDS3.3 DOES NOT EXIST Host topdog subdirectory /opt/KMDS3.3 CREATED Host topdog batch.ctl file built OK
Host topdog: PATROL install complete Host topdog Install Side Interface finished OK Host topdog Remote Node Component stop OK Host topdog PATROL install SUCCESSFUL
D-8
Step 1
Determine the shell that installation account is using. The shell used by the installation account either needs to be listed in /etc/shells or the installation account must use one of the following shells: /usr/bin/sh /usr/bin/csh /bin/sh /bin/csh /sbin/sh /sbin/jsh /usr/bin/ksh /bin/ksh /usr/bin/jsh /bin/jsh
Step 2
If the shell account is not on the list of acceptable shells, do one of the following: Choose a different installation account that uses an acceptable shell. Create a file on the target machine named /etc/shells and include the absolute path to desired login shells. Change the login shell of the installation account to a shell allowed by ftp on the target platform.
Error Messages
This section contains information about specific problems or error messages you might encounter while installing or configuring PATROL products.
Problem:
No error message is printed. You cannot correct typing errors in installation program windows when using an X-emulator on a PC to run the Unix installation program. This can be caused by some X emulation software. Usually one of these three controls will delete typed characters: Backspace, Delete, or Ctrl+H.
Cause: Solution:
Error Messages
D-9
Message: Cause 1:
Cant Open Display Your machine does not have permission to open the requested X11 display. Type the following command in the OS login window to permit displays on your terminal:
xhost +<your-hostname>
Solution:
Cause 2: Solution:
Your DISPLAY environment variable is not set or is improperly set. For csh users, set your display variable to point to the DISPLAY terminal by typing the following command:
setenv DISPLAY myworkstation:0.0
For sh or ksh users, you can set your display variable by typing the following command:
DISPLAY=myworkstation:0.0; export DISPLAY
Message: Cause:
PatrolAgent-F-EUSER:PatrolAgent -- not superuser The PATROL configuration script was unable to set the ownership and permissions of the PATROL and PATROL Agent executable files. Run the configure.sh script as described in Configuring PATROL Products on page 5-3. The file attributes should be as follows: (rwsr-sr-x) (root) PatrolAgent
Solution:
D-10
Message:
PatrolAgent-F-EUSER:The variable PATROL_HOME is not set and $HOME is not set The environment variable PATROL_HOME is not set. The PATROL Console and PATROL Agent use the path stored in this variable to locate required files and utilities. BMC Software recommends you always use the PATROL Console startup script (that is, Patrol) or the PATROL Agent startup script (that is, PatrolAgent) in the PATROL installation directory to start the corresponding process. Either script sets the PATROL_HOME variable correctly. If you are a csh user, however, and want to set the PATROL_HOME environment variable manually, do so by changing (cd) to the install directory and entering the following command:
source ./.patrolrc
Cause:
Solution:
For sh or ksh users, set the PATROL_HOME command by changing (cd) to the install directory and entering the following command:
. ./patrolrc.sh
Problem:
No error message is printed. PATROL seems to hang when it is started in the background. $PATROL_CACHE is on an NFS mounted system and NFS is having intermittent network problems. Move $PATROL_CACHE to a local file system.
Cause:
Solution:
Message:
Open Look Window Manager does not respond to mouse movement and freezes the screen while running PATROL
Error Messages
D-11
Cause:
Your management SPARCstation has two or more swap partitions, and not all the partitions are of the same size. You may reconfigure your swap partitions and restart XNeWs. The Motif Window Manager raises a window when clicked anywhere in the window. Motif Window Manager has inappropriate settings for PATROL. Add the following two lines to your .Xdefaults file: Mwm*keyboardFocusPolicy: pointer Mwm*focusAutoRaise: False Run the following command:
xrdb -merge .Xdefaults
Solution: Problem:
Cause: Solution:
Message:
Commands fail with the error Permission denied because the agent tried to execute them in a directory the user doesnt have access to and in which they dont even exist! The version of csh distributed with HP-UX mistakenly searches the command search ($PATH) path for programs to be executed. If the PATROL Agent search path at startup contains directories that the user does not have permission to access, the csh search terminates at the first such directory encountered. The terminated search reports that the command is in that directory but cannot be executed because of insufficient privileges. Start the agent with a minimal PATH that contains only world-readable directories or directories that all PATROL users can access. Make sure that $PATROL_HOME/bin is the first entry in the path, so that no path prior to $PATROL_HOME can cause a PATROL command to fail.
Cause:
Solution:
D-12
For csh users, the following example shows how the setenv command is used to specify the $PATROL_HOME directory as the first directory in the search path: setenv PATH $PATROL_HOME/bin:\ /usr/local/bin:/bin:\ /usr/bin:/etc:/usr/etc For sh or ksh users, the following example shows how the export command is used to specify the $PATROL_HOME directory as the first directory in the search path: PATH = ${PATROL_HOME}/bin:/usr/ local/bin:/bin: /usr/bin:\ /etc:/usr/etc export PATH If you are still having problems, please contact a PATROL product support representative.
Problem:
The PATROL directory tree is located on an NFS-mounted file system and errors are encountered with PATROL Agent initialization concerning file permissions. Create three new directories on a local writable file system, and set environmental variables to point to them. For example: cd /usr/local mkdir patrol cd patrol mkdir history config log The directories should be owned and writable by the default PATROL account, which is usually patrol, or the account defined in PATROL_ADMIN, which is also usually patrol. You can make this change with the xpconfig utility. In csh, the following commands set the environmental variables:
Solution:
Error Messages
D-13
setenv PATROL_HISTORY /usr/local/patrol/history setenv PATROL_CONFIG /usr/local/patrol/config setenv PATROL_LOG /usr/local/patrol/log In sh, the following commands set the environmental variables: PATROL_HISTORY=/usr/local/patrol/history export PATROL_HISTORY PATROL_CONFIG=/usr/local/patrol/config export PATROL_CONFIG PATROL_LOG=/usr/local/patrol/log export PATROL_LOG
The environment commands may be placed in the .patrolrc file (for csh) or patrolrc.sh file (for sh or ksh).
D-14
Index
Index
Symbols
$HOME directory 4-29 $HOME/patrol directory 6-4, A-3, A-8A-11 $PATROL_HOME directory A-3, A-6A-8, D-12 .patrolrc D-14 /tmp/patrol directory A-3, A-11
B
Back button 1-14 batch files building 8-398-41 running 8-428-43
C
Cancel button 1-151-16 colormap option 7-5 Command File Selection text 8-40 command line arguments C-2 configuration 5-2 configure 5-2 configure PATROL 2-16, 4-16, 5-2, 8-17 configure.sh script 2-16, 4-16, 5-25-4, 8-17, 8-29 configuring PATROL 5-3 configure.sh script 2-16, 4-16, 5-25-4, 8-17, 8-29 installation program 2-15, 2-20, 4-16, 4-20, 5-25-4
A
Abort Install dialog box 1-16 Accept License Terms text 8-6 Account Information dialog box 2-13, 3-14, 4-14, 4-30 Account Information text 8-15, 8-16, 8-27, 8-28, 8-34 Advanced button 1-14 Advanced Options-Operating Systems dialog box 2-9, 2-27, 3-10, 3-25, 4-4, 4-5 Agent Information dialog box 2-17, 4-17 Agent Startup text 8-18 AIX 1-7, 1-20, 1-21, 1-24, 1-32 architecture, PATROL 1-31-4
Index
D
DEC UNIX 1-6 default port 2-17, 4-17, 5-6, 5-7, B-3 demonstration license 5-12 Destination Directory text 8-14, 8-15, 8-26, 8-27, 8-32, 8-33 Destination Location dialog box 2-12, 3-13, 4-13, 4-29 dialog boxes Abort Install 1-16 Account Information 2-13, 3-14, 4-14, 4-30 Advanced Options-Operating Systems 2-9, 2-27, 3-10, 3-25, 4-4, 4-5 Agent Information 2-17, 4-17 Destination Location 2-12, 3-13, 4-13, 4-29 Installation Operations 2-7, 3-8, 4-9, 4-26 Installation Setup 4-25 Next Steps 2-21, 2-32 Operation Progress 2-19, 4-33 Operation Status 2-20, 3-18, 4-20, 4-34 PATROL Identification 5-8 PATROL License 5-13 PATROL Products 4-3, 4-5 PATROL Root Password Matrix 2-16, 4-16 Replicate Path 4-12 Root Information 2-15, 4-15 Save Installation Files 2-18, 3-16, 4-18, 4-31 Select Hosts 2-10, 3-11, 4-10, 4-27 User Encryption Key 2-11, 2-18, 3-12, 3-16, 4-11, 4-18, 4-28, 4-32 User Preferences A-7 DIGITAL UNIX 1-21
Digital UNIX 1-20 directories $HOME 4-29 $HOME/patrol 6-4, A-3, A-8A-11 $PATROL_HOME A-3, A-6A-8, D-12 /tmp/patrol A-3, A-11 PATROL Cache 6-46-5 PATROL, list of A-3 patrolinstall 1-13, 1-27, 1-34, 2-20, 2-31, 3-18, 3-29, 4-20, 4-34, 8-5 DISPLAY environment variable 1-241-25, 1-32, D-10 document conventions xviii documentation CD 7-6 for BMC products xvixviii installation 7-6
E
environment variables DISPLAY 1-241-25, 1-32, D-10 LANG 7-3 PATH 7-3 PATROL_BROWSER 7-4 PATROL_CACHE 6-46-5 PATROL_CONFIG D-13 PATROL_HISTORY A-7, D-13 PATROL_HOME D-11 PATROL_LOCAL_PSL_APPS A-10 PATROL_LOG D-13 setting PATROL 5-11 error messages A-8, D-9D-14 Event Log files A-7 Event Manager, PATROL. See PATROL Event Manager eXceed 7-5 exit 2-20, 2-31, 3-18, 3-29, 4-20, 4-34
F
files host list 1-13, 1-15, 2-10, 2-18, 2-27, 2-28, 2-30, 3-12, 3-16, 3-26, 3-28, 4-11, 4-18, 4-27, 4-28, 4-31 locks for Event Manager A-11 parameter history A-6 PATROL A-4A-5 PATROL Agent A-5 permanent event A-7 products 1-13, 1-15, 2-18, 2-30, 3-16, 3-28, 4-18 services 2-17, 4-17, 8-18 session information A-10 temporary lock A-11 firewalls B-1B-5 flow charts installing agents and consoles 2-4 installing KMs to Agents and Consoles 2-23 installing KMs to the PATROL KMDS 3-21 installing the PATROL KMDS 3-4 preparing to install 1-18 replicated installation 4-7 uninstall 4-23
I
Install Status text 8-19, 8-30, 8-36, 8-40 install.sh 1-23, 1-31, 8-5 installation local 2-2, 3-2, 4-22 overview 1-111-12 PATROL Agents 2-32-21 PATROL Consoles 2-32-21 PATROL KMDS 3-33-19 PATROL KMs to agents and consoles 2-222-32 PATROL KMs to the PATROL KMDS 3-203-30 planning 1-31-8 remote 2-2, 3-2, 4-22 replicated 4-24-21 repository 4-34-6 troubleshooting D-1D-14 Installation Operations dialog box 2-7, 3-8, 4-9, 4-26 Installation Operations text 8-7 installation program navigating 1-141-16 quitting 1-151-16 starting 1-171-36 installation program, text based starting 8-58-7 Installation Setup dialog box 4-25 installing a patch 1-10, 2-5, 2-24, 3-5, 3-22, 8-5, 8-42 installing PATROL Agents 2-32-21 installing PATROL Consoles 2-32-21 installing the documentation 7-6
G
GNU 1-8
H
help 7-27-5 histool utility 6-3 host list file 1-13, 1-15, 2-10, 2-18, 2-27, 2-28, 2-30, 3-12, 3-16, 3-26, 3-28, 4-11, 4-18, 4-27, 4-28, 4-31
BMC Software, Inc., Confidential and Proprietary Information
Index
K
KM. See PATROL Knowledge Modules KMDS. See PATROL Knowledge Module Deployment Server Knowledge Module. See PATROL Knowledge Modules
NFS-mounted directory limitation 5-3 NFS-mounted file systems 1-8, D-13 nonslookup 1-24, 1-25, 1-32, 1-33 nslookup 1-24, 1-25, 1-26, 1-32, 1-33, 2-9, 2-10, 2-28, 3-10, 3-11, 3-25, 4-10, 4-11, 4-27
O L
LANG environment variable 7-3 license activating 5-13 demonstration 5-12 dialog box 5-12 PATROL 1-8, 5-125-15 permanent 5-13 local installation 2-2, 3-2, 4-22 log files A-10 logging in to PATROL Console 5-8 Operation Progress dialog box 2-19, 4-33 Operation Status dialog box 2-20, 3-18, 4-20, 4-34 Optional Command File Selection text 8-19, 8-30, 8-36 Override OS text 8-13, 8-25 overview, installation 1-111-12
P
-p start-up option 5-6, 5-8 parameter history A-6 parameter history directory A-6 password 5-13 patching PATROL products 1-10, 2-5, 2-24, 3-5, 3-22, 8-5, 8-42 PATH environment variable 7-3 PATROL architecture 1-31-4 command line arguments C-2 configuring 2-15, 2-16, 2-20, 4-16, 4-20, 5-25-4, 8-17, 8-29 directories A-3 directories and files A-1 license 1-8, 5-125-15 license dialog box 5-12 patching 1-10, 2-5, 2-24, 3-5, 3-22, 8-5, 8-42 setting up 5-9 starting 5-55-11
BMC Software, Inc., Confidential and Proprietary Information
M
Main Product List text 8-10, 8-11, 8-23 managing PATROL files A-1 memory requirements 1-7 messages, error D-9D-14 mounting the CD-ROM 1-191-21
N
navigating the installation program 1-141-16 Netscape Navigator 7-2 Next button 1-14 Next Steps dialog box 2-21, 2-32 NFS Mount 1-201-21 NFS-mounted directories 5-3
4 PATROL for Unix Installation Guide
upgrading 1-9, 6-26-5 using with firewalls B-1B-5 patrol account 1-21 PATROL Agent 1-3 configure 2-16, 4-16, 8-17 disk space requirements 1-6 files A-5 installation 2-32-21 installing 8-88-20 parameter history A-6 starting 5-6 starting by the installation program 2-17, 4-17, 5-2 startup script D-11 PATROL Agent text 8-10 PATROL Cache directory 6-46-5 PATROL components 1-3 PATROL Console 1-3 and Netscape Navigator 7-2 configure 5-2 disk space requirements 1-6 display requirements 1-7 files A-4A-5 installation 2-32-21 list of loaded KMs A-10 logging in to 5-8 memory requirements 1-7 session information files A-10 session user preferences A-10 starting 5-75-9, 6-4 startup script D-11 PATROL Developer Console, starting 5-7 PATROL directories $HOME/patrol A-3 $PATROL_HOME A-3 $PATROL_ROOT A-3 /tmp/patrol A-3 PATROL Event Manager 1-3, 1-4 disk space requirements 1-6 lock files A-11 permanent event files A-7
BMC Software, Inc., Confidential and Proprietary Information
starting 5-10 PATROL Identification dialog box 5-8 PATROL Installation log file path selection text 1-27, 1-34 PATROL Knowledge Module Deployment Server 1-3 disk space requirements 1-6 installation 3-33-19 PATROL Knowledge Module text 8-23 PATROL Knowledge Modules description 1-3 disk space requirements 1-6 installation to agents and consoles 2-222-32, 8-218-30 installation to the PATROL KMDS 3-203-30 PATROL License dialog box 5-13 PATROL Operator Console, starting 5-8 PATROL product set selection text 1-24 PATROL Products dialog box 4-3, 4-5 PATROL products path selection text 1-26, 1-34, 8-6 PATROL Root Password Matrix dialog box 2-16, 4-16 PATROL Username/Password Matrix dialog box 4-31 PATROL_BROWSER environment variable 7-4 PATROL_CACHE environment variable 6-46-5 PATROL_CONFIG environment variable D-13 PATROL_HISTORY environment variable A-7, D-13 PATROL_HOME environment variable D-11 PATROL_LOCAL_PSL_APPS environment variable A-10 PATROL_LOG environment variable D-13 patrolinstall directory 1-13, 1-27, 1-34, 2-20, 2-31, 3-18, 3-29, 4-20, 4-34, 8-5
Index 5
patrolrc.sh D-14 permanent license 5-13 planning, installation 1-31-8 Populate hostlist with nslookup text 1-25, 1-33 port number 2-17, 4-17, 5-6, 5-7, 8-18, A-8, B-3 TCP 5-6 UDP 5-6 Port Override text 8-18, 8-35 problem resolution, installation D-1D-14 product distribution 1-8 Product Selection text 8-9, 8-11, 8-22, 8-24 products file 1-13, 1-15, 2-18, 2-30, 3-16, 3-28, 4-18 PSL scripts, user-written A-9
network 1-8 platform 1-5 priviliges 1-4, 1-19, 1-20 Root Information dialog box 2-15, 4-15 Root Password text 8-16, 8-17, 8-29, 8-35 running the configuration script 5-2
S
Save Installation Files dialog box 2-18, 3-16, 4-18, 4-31 Saving Product and Host Files 1-15 scripts, configure 5-2 Select Hosts dialog box 2-10, 3-11, 4-10, 4-27 services file 2-17, 4-17, 8-18 Set the DISPLAY environment variable text 1-25, 1-32 setting PATROL environment variables 5-11 setting up PATROL 5-9 SINIX 1-7, 1-20, 1-21 Solaris 1-7, 1-20, 1-21 Starting PATROL Installation with the following path names text 1-35, 8-6 Starting PATROL Installation with the following pathnames text 1-27, 8-6 starting PATROL products 5-55-11 starting the installation program 1-171-36 starting the text-based installation program 8-58-7
Q
quitting 1-151-16, 2-20, 2-31, 3-18, 3-29, 4-20, 4-34
R
release notes xviii remote hosts 5-2 remote installation 2-2, 3-2, 4-22 Replicate Path dialog box 4-12 replicated installation 4-24-21 repository installation 4-34-6 requirements CPU and operating system 8-2 cpu and operating system 1-6 disk space 1-51-6 display 1-7 hardware 1-4 licensing 1-8 memory 1-7
T
TCP port 5-6 TCP-based transport B-2, B-4B-5 temporary lock files A-11 text user interface 8-18-43 text-based installation program batch files 8-388-43
BMC Software, Inc., Confidential and Proprietary Information
installing the PATROL Agent 8-88-20 installing the PATROL Knowledge Modules installation to agents and consoles 8-218-30 uninstalling PATROL 8-318-37 troubleshooting, installation D-1D-14
U
UDP port 5-6 UDP-based transport B-2, B-3B-4 umask setting 1-21 uninstalling PATROL 4-224-34, 8-4, 8-318-37 upgrade considerations 1-9 upgrading PATROL 1-9, 6-26-5 user account 1-21, 2-13, 3-14, 4-14, 4-29, 7-3, D-13 User Encryption Key dialog box 2-11, 2-18, 3-12, 3-16, 4-11, 4-18, 4-28, 4-32 User Preferences dialog box A-7 utilities histool 6-3
X
X emulation software 1-7, D-9 xpconfig 5-6, 5-14, D-13 xpconfig utility 5-14
Index
Notes