Install Guide 4x4

4.1.4 4.2.
4 Installation Guide
2008 Quest Software, Inc. ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 USA www.quest.com email: legal@quest.com Refer to our Web site for regional and international office information.
TRADEMARKS
Quest, Quest Software, the Quest Software logo, Aelita, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, InTrust, IT Dad, JClass, JProbe, LeccoTech, LiveReorg, NBSpool, NetBase, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLab Tuner, SQLab Xpert, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, Toad, T.O.A.D., Tag and Follow, Vintela, Virtual DBA, and XRT are trademarks and registered trademarks of Quest Software, Inc. Other trademarks and registered trademarks used in this guide are property of their respective owners.
Disclaimer
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. Foglight Installation Guide Updated - November, 2008 Software Version - 4.1.4/4.2.4
CONTENTS
OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 HOW FOGLIGHT WORKS . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 RELATED DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . .13 ABOUT QUEST SOFTWARE, INC. . . . . . . . . . . . . . . . . . . . . . .13 CONTACTING QUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 CONTACTING QUEST SOFTWARE . . . . . . . . . . . . . . . . . . .14 CONTACTING QUEST SUPPORT . . . . . . . . . . . . . . . . . . . .14 CHAPTER 1 PLANNING YOUR INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . .15 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 SYSTEM AND HARDWARE REQUIREMENTS . . . . . . . . . . . . . . . . .19 REQUIRED TCP/IP COMMUNICATION PORTS . . . . . . . . . . . .20 SYSTEM PERFORMANCE CONSIDERATIONS . . . . . . . . . . . . . . . .23 ADDITIONAL CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . . .23 SECURITY AUTHORIZATION . . . . . . . . . . . . . . . . . . . . . .23 FIREWALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 LANGUAGE CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . .26 INTERNATIONALIZATION . . . . . . . . . . . . . . . . . . . . . . . .26 USING FOGLIGHT TO MONITOR NT CLUSTERS . . . . . . . . . . .26 CHAPTER 2 INSTALLING FOGLIGHT ON UNIX . . . . . . . . . . . . . . . . . . . . . . .29 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 WHAT IS INVOLVED IN A FOGLIGHT INSTALLATION ON UNIX. .30 INSTALLING THE FOGLIGHT MANAGEMENT SERVER . . . . . . . . . . .31 PRE-INSTALLATION TASKS . . . . . . . . . . . . . . . . . . . . . . .31 PERFORMING YOUR FMS INSTALLATION . . . . . . . . . . . . . .33
Quest Foglight
CHAPTER 3 INSTALLING FOGLIGHT ON WINDOWS . . . . . . . . . . . . . . . . . . . .53 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 WHAT IS INVOLVED IN A FOGLIGHT INSTALLATION ON WINDOWS . 54 INSTALLING THE FOGLIGHT MANAGEMENT SERVER . . . . . . . . . . .55 LAUNCHING FOGLIGHT . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 FOGLIGHT MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . .69 CHAPTER 4 INSTALLING FOGLIGHT ON MONITORED HOSTS . . . . . . . . . . . . . .73 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 INSTALLING THE FOGLIGHT CLIENT ON AN MONITORED HOST . . . .75 INSTALLING A WINDOWS CLIENT FROM A WINDOWS WORKSTATION . . . 83 ADDITIONAL CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . . .88 AGENTS APPEAR IN A BROKEN STATE . . . . . . . . . . . . . . . .88 VIRTUALIZATION SUPPORT . . . . . . . . . . . . . . . . . . . . . .88 RESOLVING UNSUPPORTED OPERATING SYSTEM TYPES. . . . . .90 PERFORMANCE COUNTERS . . . . . . . . . . . . . . . . . . . . . . .91 INSTALLING FOGLIGHT MONITORED HOSTS FROM THE COMMAND LINE . . . 91 CHAPTER 5 POST-INSTALLATION TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . .93 POST-INSTALLATION TASKS FOR UNIX SYSTEMS . . . . . . . . . . . .94 AUTOMATIC START . . . . . . . . . . . . . . . . . . . . . . . . . . .94 HOST AUTODISCOVERY . . . . . . . . . . . . . . . . . . . . . . . .94 STARTING AND STOPPING THE FOGLIGHT MANAGEMENT SERVER . . .95 LAUNCHING THE FOGLIGHT OPERATIONS CONSOLE . . . . . . . . . . .95 INSTALLING THE FOGLIGHT OPERATIONS CONSOLE ON OTHER WORKSTATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 INSTALLING THE FOGLIGHT OPERATIONS CONSOLE ON ADDITIONAL UNIX WORKSTATIONS . . . . . . . . . . . . . . . . . . . . . . . . .97 INSTALLING FOGLIGHT CARTRIDGES . . . . . . . . . . . . . . . . . . . .97 INSTALLING CARTRIDGES ON UNIX . . . . . . . . . . . . . . . . .97 INSTALLING CARTRIDGES ON WINDOWS . . . . . . . . . . . . . .98
CHAPTER 6 MONITORING NT CLUSTERS . . . . . . . . . . . . . . . . . . . . . . . . . . 101 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 MONITORING NT CLUSTERS USING THE FOGLIGHT SQLSERVER CARTRIDGE . . . 102 GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 INSTALLING THE MONITORED HOST ON AN ACTIVE-ACTIVE NT CLUSTER . . . 103 INSTALLING THE MONITORED HOST ON AN ACTIVE-PASSIVE NT CLUSTER . . 104 POST INSTALLATION TASKS . . . . . . . . . . . . . . . . . . . . . . . . 107 DEACTIVATING THE FOGLIGHT MANAGER . . . . . . . . . . . . . 107 CREATING A FOGLIGHT NT CLUSTER RESOURCE . . . . . . . . 109 BRINGING THE FOGLIGHT CLUSTER RESOURCE ONLINE . . . . 113 TESTING FAIL-OVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 CHAPTER 7 INSTALLING THE FOGLIGHT TRANSACTION RECORDER AND TRANSACTION PLAYER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 SYSTEM REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . 118 INSTALLING THE FOGLIGHT TRANSACTION RECORDER AND PLAYER . . . 119 CHAPTER 8 UNINSTALLING FOGLIGHT . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 UNINSTALLING FOGLIGHT ON UNIX . . . . . . . . . . . . . . . . . . . 122 UNINSTALLING FOGLIGHT ON WINDOWS . . . . . . . . . . . . . . . . 122 GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Quest Foglight
About Foglight
Overview Whats New In Foglight v4.1.4/4.2.4 How Foglight Works
Quest Foglight
Overview
Foglight helps IT managers understand end-user service levels for their critical business applications by monitoring every tier of the application stack and notifies stakeholders when those service levels are violated, assigning problem resolution tasks to the appropriate domain expert. Using domain-specific agents, Foglight collects data from application end-users, application servers, database, operating systems, Web servers and networks, providing a total picture of performance and reducing the time it takes to find and resolve problems.
How Foglight Works

Unlike traditional monitoring tools, Foglight maps business objectives to both system and application performance information across every tier of the application stack to measure and improve the performance of packaged and custom applications.
In addition to Foglight's core performance management capabilities, Foglight offers specialized monitoring for all application tiers.
APPLICATION TIER End-User Response DESCRIPTION Foglight monitors end-user response times with two components: Foglight for SQL Transactions and Foglight Transaction Recorder.
APPLICATION TIER Applications
DESCRIPTION Cartridges are available to monitor Siebel eBusiness Applications, PeopleSoft, Oracle E-Business Suite, MySAP and Microsoft Exchange, as well as custom applications. Foglight's cartridge for Web Servers allows you to detect, diagnose and resolve potential Web server bottlenecks before they affect end users. Available for Apache or Microsoft Web Services (IIS). Available for BEA WebLogic Server, IBM WebSphere Server, JBoss Server, and the Oracle Application Server. The Application Server cartridge monitors the complex architecture of application server technology. The database cartridge provides comprehensive monitoring for DB2, Oracle, SQL Server, and Sybase. Foglight's Operating System cartridge supports Windows 2000, Windows 2003, Windows NT, AIX, Solaris, HPUX, and Red Hat and Suse Linux.
Web Servers
Application Servers
Databases
Operating Systems
Quest Foglight
10
Preface
About This Guide About Quest
Quest Foglight
About This Guide

This guide is written for Foglight installers and administrators. Included are instructions for: Installing the Foglight Management Server and Monitored Hosts Managing additional configuration and setup needs Monitoring NT Clusters Installing Foglight Transaction Recorder and Player Uninstalling Foglight
Note Please refer to the Foglight v4.1.4/4.2.4 Release Notes for updates on Foglight system requirements, product information, and documentation. Chapter 1 provides a description of Foglight architecture and features. Chapter 2 outlines the system requirements and tasks required to prepare your environment for a Foglight installation. Chapter 3 provides instructions for installing the Foglight Management Server on UNIX operation systems. Chapter 4 provides instructions for installing the Foglight Management Server on Windows operating systems. Chapter 5 provides information needed to perform a Foglight Monitored Host installation. Chapter 6 provides instructions for post-installation tasks and optional functions. Chapter 7 provides instructions for installing Foglight Monitored Hosts in support of an NT Cluster environment.
Chapter 8 provides installation instructions for the Foglight Transaction

Recorder and Player. Chapter 9 provides instructions for uninstalling Foglight.
12
Related Documentation
In addition to this guide, the following Foglight documentation is available. The Foglight documentation PDF files are delivered on the Foglight v4.1.4/4.2.4 Product Documentation CD-ROM. Foglight Administration Guide The Foglight Administration Guide contains information about managing and integrating Foglight. It includes documentation of command line utilities, details about products that integrate with Foglight (such as Big Brother and Enterprise Management Consoles) and descriptions of Foglight processes. This guide is written for the individuals responsible for administrating your Foglight environment. Print copy and PDF. The online help allows you to access information specific to the feature you are using. User guides are available for the Foglight Management Server and for Foglight Cartridges. These guides provide the same information as the Foglight online help in a book layout and are presented in PDF format for portability and ease in printing. Foglight Management Server and Foglight Cartridge Release Notes contain a description of whats new in the release as well as late-breaking information about the product. Release notes are delivered in PDF format.
Foglight Online Help
Foglight User Guides
Release Notes
About Quest Software, Inc.

Quest Software, Inc., a leading enterprise systems management vendor, delivers innovative products that help organizations get more performance and productivity from their applications, databases, Windows infrastructure and virtual environments. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps
13
Quest Foglight
more than 90,000 customers worldwide meet higher expectations for enterprise IT. Quest provides customers with client management as well as server and desktop virtualization solutions through its subsidiaries, ScriptLogic and Vizioncore. Quest Software can be found in offices around the globe and at www.quest.com.
Contacting Quest
Contacting Quest Software
Email: Mail: info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA www.quest.com
Web site:
Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com. From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status.
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
14
1
Planning Your Installation
Getting Started System and Hardware Requirements System Performance Considerations Additional Considerations
If you are upgrading from version 4.1.3 or 4.2.3, refer to the Foglight 4.1.4/4.2.4 Release Notes. They contain instructions for installing the required patches. If you are doing either a full install or an upgrade, see the Release Notes for last-minute changes and a list of resolved issues.
Quest Foglight
Overview
This installation guide is written for the individuals responsible for administrating your Foglight Management Server. We assume you are familiar with relational database concepts and with the operating system environments where you are running Foglight.
Getting Started
Successful installation of a Foglight Management Server depends on planning ahead and understanding your system.
Prepare for your Installation

BEFORE BEGINNING YOUR INSTALLATION, PLEASE COMPLETE THESE TASKS: Read the Documentation Before beginning your installation: 1. Read this manual. 2. Read the Foglight v4.1.4/4.2.4 Release Notes. 3. Check Quest SupportLink for any late-breaking additions or changes to these documents. Plan Your Technical Staff Support An important part of installing your Foglight Management Server is to ensure that you have the internal resources available to prepare and support the installation process. Quest recommends having the following technical staff available: UNIX/Windows System Administrator with root/administrator authority. Network/LAN Administrator. Application Administrator (if installing Foglight ERP/CRM cartridges). Web Administrator (if installing Foglight Web or Application Server cartridges). Important: Only experienced system administrators should install the Foglight products. If you have any questions regarding the installation or expertise necessary, please contact Quest Support at support@quest.com.
16
BEFORE BEGINNING YOUR INSTALLATION, PLEASE COMPLETE THESE TASKS: Review System and Hardware Requirements Review all system and hardware requirements for the Foglight Management Server and Foglight Cartridges. See System and Hardware Requirements on page 19. Foglight Management Server performance can vary depending on several factors. Reviewing these considerations before beginning your installation will help you plan for a successful installation and efficient use of Foglight. See System Performance Considerations on page 23.
Review System Performance Considerations
Collect Your System Information

You will need to have specific system information available while installing your Foglight Management Server.
THE FOLLOWING INFORMATION IS REQUIRED DURING THE INSTALLATION PROCESS Foglight Server name The name of the dedicated server where you plan to install the main Foglight Management Server and monitored host system software. The name of the MySQL database where your MySQL data resides. The username and password used to access the MySQL database. The password used to access the MySQL database as the MySQL administrator (user name root). The name(s) of the server(s) where you plan to install the Foglight client software. The full path to each of these machines on your network. This is required for each Foglight Management Server and is provided by Quest Customer Support during your initial installation process. You must request an additional license key for each Foglight Management Server that you install.
MySQL database name MySQL database username and password MySQL database administrator password Foglight monitored host system names Directory path names for the Foglight Server and monitored hosts Valid Foglight License Key number
17
Quest Foglight
Check for Specific Installation Issues

In addition, perform the following checks: Resolve any firewall obstacles that prevent you from gaining access to a server or host that might need manual (remote) installations. See Firewalls on page 24 of this chapter for more information. Verify your root or psuedo-root privileges (including password) for all servers and hosts where Foglight will be installed. Make sure your directory path for Foglight has enough disk space. See System and Hardware Requirements on page 19 for more information. Resolve any security issues that may block email sent from Foglight to your DBA and System Administrator. The Foglight Management Server sends email from Foglight to the email addresses you set up when configuring Foglight communication. For example, if you define your System Administrators mail ID as "sysadmin@yourcompany.com", Foglight will send mail from "foglight@yourcompany.com". If your system contains Microsoft NT Clusters, there is additional information for you to read in these chapters: Installing Foglight on Windows Installing Foglight on Monitored Hosts Foglight for NT Clusters
An overview of NT Cluster requirements can be found in Using Foglight to Monitor NT Clusters on page 26.
18
System and Hardware Requirements

See the current Foglight release notes for the list of system and hardware requirements, supported platforms for both the Foglight Management Server and Foglight Monitored Hosts, as well as for the Foglight Operations Console and the Foglight Web Console. See the Foglight Cartridge documents for their current version numbers and supported platforms.
Discontinuation of Deprecated Monitored Host OS platforms

Quest will not provide monitored host products for the following platform OS environments after this release of Foglight. This is due to the addition of new, and deprecation of older, OS versions by the respective vendors: AIX 4.3, Solaris 6 & 7, Windows NT 4.0, RedHat 7.x, SuSe 8.
FMS Installation Location

The Foglight v4.1.4/4.2.4 Management Server can be installed in the following configurations: On its own dedicated server On a server shared with an earlier version of the Foglight Management Server (side-by-side installation)
Foglight performance may vary according to the server configuration.
19
Quest Foglight
Required TCP/IP Communication Ports

The Foglight Management Server requires access to specific TCP/IP ports to connect servers and hosts as well as defaults to the following ports for communication purposes. Any changes should be made in the $FGLHOME/WORLD/DBVARS and WEBVARS file. Note In a side-by-side installation, you must assign distinct port settings to each Foglight Management Server. Shared port settings will cause communication errors. Each port can be configured during FMS installation. The installation process verifies port access. You can edit port settings in the DBVARS and WEBVARS files should conflicts arise after installing the product. The following table lists the required ports, their default settings, their required configuration location, and the purpose of each.
PORT MySQL Server Port PURPOSE This port is used for communication with the MySQL database server.. Default: 3306 Fieldname: DBPORT Location: FGLHOME/World/DBVARS Node: Management Server Note: See Firewalls for information about firewall concerns. RAPSD Port This port is used for communication between Foglight agents and the Foglight daemon. Default: 5160 Fieldname: RAPSDPORT Location: FGLHOME/World/DBVARS Node: Management Server and Monitored Host NE This port is used by the Notification Engine. Default: 5157 Fieldname: NEPORT Location: FGLHOME/World/DBVARS Node: Management Server
20
PORT HTTP Port
PURPOSE This port is used for the Apache web listener. It is used to access the Foglight Web Console and to display dynamic web pages. Default (UNIX): 8081 Default (Windows): 80 Fieldname: HTTP_PORT Location: FGLHOME/World/WEBVARS Node: Management Server Note: See Firewalls for information about firewall concerns.
NSS Port
This port is used by the Foglight notification subscription server. Default: 5156 Fieldname: NSSPORT Location: FGLHOME/World/DBVARS Node: Management Server and Monitored Host Note: See Firewalls for information about firewall concerns.
Tomcat AJP Port
This port allows the Apache web listener to communicate with the Tomcat server engine on the Foglight Management Server. default: 8009 Fieldname: AJP_PORT Location: FGLHOME/World/WEBVARS Node: Management Server
Tomcat Shutdown Port
This port allows Foglight to shut down the Tomcat server engine. Default: 8005 Fieldname: TOMCAT_SHUTDOWN_PORT Location: FGLHOME/World/DBVARS Node: Management Server
21
Quest Foglight
PORT RMI Registry Port
PURPOSE This port is used for communications between the Foglight Operations Console and the Foglight Management Server. Default: 1099 Fieldname: RMI_REGISTRY_PORT Location: FGLHOME/World/DBVARS Node: Management Server Note: If you have more than one Foglight installation running on your Foglight Management Server (even temporarily), do not choose port 1099. Make another port selection so your Foglight Operations Console will use a different port. Note: See Firewalls for information about firewall concerns.
JDAL Server Port
This port is for Java Database Access Layer communication. Default: 7000 Fieldname: JDALSVR_PORT Location: FGLHOME/World/WEBVARS Node: Management Server Note: See Firewalls for information about firewall concerns.
Command Servlet Port
This port is for Java command servlet communication. Default: 7001 Fieldname: CMDSERVLET_PORT Location: FGLHOME/World/WEBVARS Node: Management Server Note: See Firewalls for information about firewall concerns.
22
System Performance Considerations

Foglight Management Server performance can vary depending on the following factors. Foglight administrators should take estimates of these variables into account when planning the Foglight environment. Number of open Foglight Operations Consoles and Web Consoles. Number of users. Number and type of hosts and agents installed on the Foglight Management Server. Message rates between agents and the Foglight Management Server. Rule evaluation rates The rate at which the Notification Engine processes incoming information. Purge times. Backup times. Database configuration. Monitored host mapping when running multiple Foglight Management Servers. Estimated growth of monitored hosts and agents.
Contact Quest Professional Services to discuss the specific details of your installation.
Additional Considerations
This section contains information about Foglight installation issues and situations that occur frequently with similar solutions. If your situation is not addressed, please contact customer support or Quest Professional Services for assistance.
Security Authorization
On Windows Operating Systems
Ensure you do not have conflicts between directory permission and user authority for running programs.
23
Quest Foglight
Foglight installations are, by default, performed by a local user with administrator privileges who has control of all programs. Since Foglight installation involves installing a service, you have to be a local administrator.
Foglight Email and Your Email Security

You will need to resolve security issues that may block email sent from Foglight to your DBA and System Administrator. The Foglight Management Server sends email from Foglight to the email addresses you set up when configuring Foglight communication. For example, if you define your System Administrators mail ID as "sysadmin@yourcompany.com", Foglight will send mail from "foglight@yourcompany.com". If your mail server does not allow mail to be sent from Foglight in this manner, you can resolve the issue by adding the FGLADMIN variable in DBVARS to refer to a real mail address.
Firewalls
In a distributed network environment, the Foglight Management Server and its monitored hosts do not always operate within the boundaries of the same firewall. Note Contact Quest Customer Support for assistance with firewall issues.
Identifying Ports
When installing Foglight, firewall owners need to address which ports must be open: When there is a firewall between the Foglight Management Server and a monitored host, you must open the following ports from the monitored host to the Foglight Management Server: MySQL Server Port NSS Port
When there is a firewall between the Foglight management Server and the desktop running the Folight Operations Console or the Web Console, you must open the following ports from the desktop to the Foglgiht Management Server: RMI Registry Port JDAL Server Port Command Servlet Port
24
The port connecting RAPSD and the NSS process from the Foglight Management Server must remain open. You must change this value in the Foglight Management Server and each monitored host. The Foglight Management Server only reads the DBVARS file upon startup, so you must restart the server for these changes to take effect. To restart a Foglight Solaris 8 server, you must have a terminal session open with the server. Please see Required TCP/IP Communication Ports on page 20 for more information about port settings.
IP Address Allocation
When working in a distributed environment, communications between the Foglight Management Server and the Foglight Operations Console rely on the ports for the Web Server and RMI registry remaining open. In addition, the services associated with the command servlet as well as the service managing communication output, JDALSERV, must be defined. To restore communications: 1. On the Foglight Management Server, change the tokens associated with the command servlet and JDALSERV services by editing the commands.properties file. This file is located in the FGLHOME/apache/tomcat/webapps/foglight/WEB-INF directory. a) Uncomment and change the cmdservlet.rmiCommunicationsPort value to the desired port setting for the command servlet. b) Uncomment and change the jdalsrv.rmiCommunications value to the desired port setting for JDALSERV.
Network Address Translation

In a distributed environment, some firewalls or routers are set up to perform network address translation. In these cases, a Foglight Operations Console sitting outside the firewall may be unable to communicate with the Foglight Management Server due to a problem that it will have trying to communicate with the RMI service using the IP address of the Foglight Management Server. To resolve communications: 1. On the Foglight Management Server, change the token associated with the RMI service by editing the web.xml.template file. This file is located in the FGLHOME/apache/tomcat/webapps/foglight/WEB-INF directory. a) Uncomment and change the jdalsrv.rmiSrvHost and cmdservlet.rmiSrvHost values to the IP address of the machine performing the Network Address Translation.
25
Quest Foglight
2.
You must then stop and restart the Foglight Management Server.
For example, a Foglight Management Server is running on a machine named foo with an IP address of 192.168.9.1. The external interface to this machine may be through a network device with an external IP address of 66.94.200.24. A Foglight Operations Console running through the external interface will only work if the web.xml.template file is edited to change the jdalsrv.rmiSrvHost and cmdservlet.rmiSrvHost values to 66.94.200.24. You must then stop and restart the Foglight Management Server.
Language Considerations
Foglight is a product designed in the United States, and all of its text strings are written in English. The Operations Console will work with languages that can work with normal ASCII as inserts into the database. The Foglight Management Server should be installed with its keyboard/input set to English.
Internationalization
Foglight supports system agents on Microsoft Windows 2000, 2003 and NT monitored servers in English, German, and French versions. The Foglight Management Server is supported on the English version only.
Using Foglight to Monitor NT Clusters

Foglight Monitors the following NT Cluster arrays: Foglight Management Server on a Active-Passive NT Cluster Monitored Host on an Active-Passive NT Cluster Monitored Host on an Active-Active NT Cluster Installations of Foglight Management Servers in an Active-Active cluster environment are not supported. You can install a Foglight Management Server on only one node of an active-active cluster. The remaining cluster members may be used for fail-over if desired. Foglight monitoring of NT Cluster arrays begins with your installation of the Foglight Management Server. During the FMS installation and when installing a Foglight Client on a Monitored Host, your cluster array is identified and setup steps specific to NT Clusters are included in the installation processes.
26
Please review Installing Foglight on Windows as well as Installing Foglight on Monitored Hosts before proceeding with the steps in Monitoring NT Clusters.
Monitoring NT Clusters Using the Foglight SQLServer Cartridge

To monitor SQL Servers in a Windows cluster environment you must follow specific installation instructions. For more information, see SQLServer Cluster Handling in the Foglight Operations Console online help.
27
Quest Foglight
28
2
Installing Foglight on UNIX
Overview Installing the Foglight Management Server
Quest Foglight
Overview
Before you can use Foglight, you must install the Foglight Management Server and client software on a dedicated server machine. After this initial installation is completed, additional Foglight Management Servers, Cartridges, and Monitored Hosts can be added as needed. Note Review the terms of your Foglight license agreement for details regarding license keys for additional Foglight Management Servers. Please review Planning Your Installation before beginning your Foglight Installation and refer to the Foglight v4.1.4/4.2.4 Release Notes for updates on Foglight system requirements, product information, and documentation.
What is Involved in a Foglight Installation on UNIX

The Foglight installation proceeds through the following steps: Performing Pre-installation Tasks Performing Your FMS Installation Set the Installation Directory Configure Your Database Connection Configure Foglight Communication and Select Agents Select Foglight Cartridges Enter the Foglight License Key Install the Foglight Management Server Perform Post-Installation Tasks
30
Installing the Foglight Management Server

Note The recommendation for Foglight v4.1.4/4.2.4 is to install as a non-root user. This is a change from prior versions of Foglight.
Pre-installation Tasks
1. Review the Main Installation Menu to familiarize yourself with the installation steps and review the this entire chapter before beginning your installation. Refer to the Foglight v4.1.4/4.2.4 Release Notes for updates on Foglight system requirements, product information, and documentation. Open a terminal window. Create a new user and password for your Foglight installation. This is the user and password you will use during your installation process. Note This is different than the user and password found in the Foglight Operations Console and WebConsole. 5. Create a directory for your Foglight installation.
2.
3. 4.
Looking at the Main Installation Menu

Before launching into the installation, review the main menu so you will be knowledgeable about the basic steps associated with the installation process. The main menu shows where you are in the installation process and displays the choices you have made while in each step. Initially, the installation script checks for and displays the default system information at the top of the main menu screen. This information includes: The license type Agents to be installed Cartridges to be installed
Screen shots throughout this document are representative. Your screens may differ from the ones shown.
31
Quest Foglight
Additional information displays in the top section of the screen as you make choices or entries in each installation step. You should verify the information displayed in this section before moving to the next menu item. In the lower portion of the screen, an arrow indicates which installation step you are currently on and moves to the next item number upon completion of each step. To return to a previous step, enter the step number at the prompt and press Enter. On all other menus in this installation, an arrow next to an item number indicates that item is currently selected. To deselect that item, re-enter its number at the prompt and press Enter. The following Main Menu options are available:
MENU OPTION 0. Enter the Fully Qualified Host Name for this Machine DEFINITION Use this option to specify or change the Foglight Management domain name. Note: In order for the Foglight Management Server to be visible across networks, a fully qualified host name (where the domain name is referenced in the name of the server) must be used. Enter the source directory used to download Foglight.
1. Enter Foglight Source Directory
32
MENU OPTION 2. Enter Installation Directory 3. Configure Database Connection 4. Configure Foglight Communication and Select Agents 5. Select Cartridges 6. Enter License Key 7. Install Foglight Server q. Quit Install
DEFINITION Enter the directory name where you will install Foglight. Configure Foglights connection to the database. Configure Foglight communication ports and select agents to install. Select cartridges to install. Enter the Foglight license key, or obtain a 3-day temporary license. Start the server installation process. You must complete the installation once this process begins. Cancel the installation at any point before Step 7.
Performing Your FMS Installation

1. Open two terminal windows. The second window will be used to type the eject command used to remove each CD-ROM when you are prompted to change CDs. Insert the first Foglight CD-ROM in your CD-ROM drive to start the Foglight installation. Note To abort the installation at any time, press CTRL+C. 3. From the directory you created for your Foglight installation, type: ./install At this time Foglight checks your system to validate space requirements for the installation.
2.
33
Quest Foglight
a) If your system lacks adequate memory to install Foglight the following alert displays: ==================================================== **** System Validation **** ==================================================== Error : To install a Foglight server, this machine must have at least 1024 Megabytes of memory. It has been determined that this system only has 512 Megabytes of memory. Installing a Foglight server on this machine is not recommended. Do you wish to continue with the install? [y/n] : Type y and press Enter to continue. Type n and press Enter to quit the installation.
b) If your system configuration does not allow enough open files per process the following alert displays: ========================================================= **** System Validation **** ========================================================= Error : To install a Foglight server, a machine must allow a soft limit of 1024 open files per process. It has been determined that the current system configuration allows only 256 open files per process. Installing a Foglight server on this machine is not recommended. To change the current settings to meet the Foglight Server Requirements, as the root user, edit /etc/system to add the following one or two lines set rlim_fd_curr=1024 set rlim_fd_max=1024 (unless this value is already set to higher value) and then reboot your system. Do you wish to continue with the install? [y/n] :
Note From a command prompt, type limit to check your system limits. Type y and press Enter to continue. Type n and press Enter to quit the installation.
34
The Foglight Installation Welcome screen displays.
4.
Press Enter to begin the installation. The User Validation screen displays.
5.
Type y and press Enter to confirm the correct User is listed on the User Validation screen.
35
Quest Foglight
Quest strongly recommends that you do not perform your installation using root permissions. If you enter n at the prompt, the installation will terminate. You must return to Pre-installation Tasks and create the user and password for your Foglight installation.
Your Solaris operation system is validated. The installation process verifies that the required Solaris operating system is installed. Note If Foglight detects you a running a Solaris OS that does not require patches, this step takes place in the background. If Your Solaris OS Requires Patches Foglight verifies that required Solaris operating system patches are installed. The installation process indicates if your system is at the correct patch level or lists the patches that must be applied before installing the Foglight Management Server software. If patches are missing, you will receive error messages indicating which patches are not installed and your Foglight installation is terminated. For more information on required patches, see Patch Requirements for Foglight Management Servers on Solaris 8 in the Planning Your Installation chapter of this guide.
36
Set the Installation Directory
6.
Press Enter to select Enter Installation Directory. The Set Installation Directory screen displays.
7.
At the prompt, enter the fully qualified path to the installation script on the CD-ROM and press Enter. Note You must change the source directory to successfully install Foglight. If you attempt to install from the Foglight directory,
37
Quest Foglight
you will be unable to remove the first Foglight CD-ROM from the CD-ROM drive when it is time to insert the second CD-ROM. If your path does not exist, you are prompted to create the directory during the installation. Enter y to create the directory.
Configure Your Database Connection

You will move through a series of screens that prompt you to enter and confirm or change: a) Your database username b) Your database password c) Your MySQL administrator password d) The location of your MySQL database e) The name of your MySQL database f) The MySQL server port
8.
Press Enter to select Configure Database Connection.
38
Enter your database connection parameters as prompted. Note MySQL Database Location Running the MySQL database on another server is not supported in this release. Accept the default database hostname or, if preferred, enter the fully qualified hostname. When you have completed the entry of this information a summary screen displays.
9.
Type y and press Enter to confirm that the entries are correct.
39
Quest Foglight
10. Enter n to return to the Database Connection Parameters step and make changes.
Configure Foglight Communication and Select Agents

Foglight can automatically send system and database messages via email when problems occur. In this step, define the communication ports and email addresses used for communicating these messages.
11. Press Enter to select Configure Foglight and Select Agents. The Configure Foglight Mail Accounts screen displays.
40
12. Enter your system administrators email address. This is the address you want Foglight to use when sending email alerts. Note The email addresses of the database administrator and MySQL Administrator can be identical. You can also enter multiple email addresses, or aliases, as a comma-delimited list. You may need to resolve any security issues that may block email sent from Foglight to your DBA and System Administrator. The Foglight Management Server sends email from Foglight to the email addresses you set up when configuring Foglight communication. For example, if you define your System Administrators mail ID as "sysadmin@yourcompany.com", Foglight will send mail from "foglight@yourcompany.com". See the Security section in the Planning Your Installation chapter of this guide for more information.
41
Quest Foglight
Configure Communication
You will move through a series of screens that prompt you to enter or select defaults for the communication ports used by the Foglight Management Server. The installation program allows configuration of its communication ports. Each ports availability is verified. If the port is not available, a prompt displays directing you to make another selection.
Please refer to Required TCP/IP Communication Ports and Firewalls, Identifying Ports in the Planning Your Installation chapter for details about ports and firewall considerations. If you are a non-root user, you will not be allowed to choose port numbers below 1024. These are well known ports that are, typically, protected for standard communication usage.
Foglight Communication Ports: a) rapsd communication b) MySQL Server c) NSS d) NE e) HTTP f) RMI
Note If you have more than one Foglight installation running on this server (even temporarily), do not choose port 1099. Make another port selection so your Foglight Operations Console will use a different port. g) Tomcat AJP h) Tomcat shutdown i) JDAL Server j) CMDSERVLET
42
Select Agents
13. Select the Foglight Agents you want to install. Type A to select all agents. Type N to select none (or to clear the arrows from the menu). Enter one or more numbers, separated by commas, to select or deselect specific agents. 14. Press Enter to confirm your select.
Select Foglight Clients

If you plan to monitor additional types of hosts in the future, you can save client installation files in a compressed format. For example, if you run Sun workstations at your site but plan to add HP servers later, you can choose to retain compressed HPUX agent files. If you choose not to retain these files now and need additional client support later, you must manually copy them from the Foglight installation CD-ROMs. Use the Foglight Installation Wizard located on the Foglight Operations Console toolbar to add monitored hosts after completing your initial Foglight installation. For instructions, refer to the Using the Foglight Installation Wizard topic in the Foglight Operations Console online help.
43
Quest Foglight
15. Select the Foglight client files you want to retain for future use. The default selection is All.
Type A to select all clients. Type N to select none (or to clear the arrows from the menu). Enter one or more numbers, separated by commas, to select specific clients. To deselect an agent name, enter the item number at the prompt and press Enter. An arrow will appear to the left of the clients you select. 16. Press Enter to confirm your select.
44
Select Foglight Cartridges
17. Press Enter to choose Select Cartridges. A list of cartridges displays.
Type A to select all cartridges. Type N to select none (or to clear the arrows from the menu).
45
Quest Foglight
Enter one or more numbers, separated by commas, to select specific clients. To deselect an agent name, enter the item number at the prompt and press Enter. An arrow will appear to the left of the clients you select. 18. Press Enter to confirm your select. Installing Cartridges After an Initial FMS Installation To install Foglight cartridges at a later date, see the Installing Cartridges section in the Post-Installation Tasks chapter of this guide.
Enter the Foglight License Key

A license key is valid only for the Foglight Management Server for which it is registered. License keys are encrypted and can be permanent or expire within a preset number of days. While you can install Foglight software without a valid license key, you cannot use the application until the license key is entered. You must have a license key for every Foglight Management Server you install.
19. Press Enter to select Enter License Key.
46
The Enter Foglight License Information screen displays.
Type y and press Enter if you have a Foglight License Key. Type n and press Enter if you do not have a Foglight License Key. If you have a Foglight License Key:
a) Enter your License Key and press Enter to continue.
47
Quest Foglight
If you do not have a Foglight License Key:
a) Contact Quest Customer Support to request your License Key. b) Press Enter to continue.
c) Type y and press Enter.
48
20. Enter your License Key and press Enter to continue. Note If you are working with a License Key that has an expired time limit, you cannot start Foglight until you obtain and apply a valid license key.
49
Quest Foglight
Install the Foglight Management Server

You are now ready to install the Foglight software. Review your installation choices summarized in the top portion of the Main Menu and make changes if necessary.
21. Press Enter to choose Install Foglight Server. a) Enter y and press Enter to confirm you want to start the Foglight installation. b) Enter n and press Enter if you do not want to start the Foglight installation.
You cannot abort the installation once you start Step 7.
Progressing Through the Installation Process

As the installation progresses, you will be asked to change CDs. To do so, type eject in your second terminal console window. Depending on the your environment, you may not need to use the entire CD-ROM set. When finished, a final message displays indicating the installation was successful.
50
Post-Installation Tasks
22. The final step in the installation process provides instructions for optional steps and additional post-installation considerations you may want to perform at this time. Note These tasks are listed in their entirety in the Post-Installation Task chapter. a) Limits for Open Files Per Process If you received a warning that your soft limit for open files per process did not meet the Foglight requirement , and you did not correct these values before continuing the installation, you must do so at this time. b) Optional steps If you installed Foglight with the recommended non-root user, you should perform the optional steps displayed at this point to automatically start Foglight when your Foglight Management Server is rebooted and to scan your network for hosts to install: Automatic Start Host Autodiscovery
c) Additional Considerations These options give you the information needed to: Start and Stop the Foglight Management Server Launch the Foglight Operations Console Install the Foglight Operations Console on other workstations
Note When installing as non-root, some Foglight agents and cartridges may appear in a broken state. To resolve these issues, you may have to configure the agents using Edit, ASPs from the Foglight Operations Console toolbar or you may have to set permissions of certain files to execute as non-root.
Installation Completes
You are returned to the command prompt and Foglight starts immediately upon completion of installation. Agents are bound to the server and immediately begin data collection unless the agent has secondary agent startup parameters (ASPs) that need to be configured. For more information about ASPs, see About Agent Startup Parameters in the Foglight Operations Console online help. You can review the installation history in the install.log file.
51
Quest Foglight
52
3
Installing Foglight on Windows
Overview Installing the Foglight Management Server Launching Foglight
Quest Foglight
Overview
Before you can use Foglight, you must install the Foglight Management Server and client software on a dedicated server machine. After this initial installation is completed, additional Foglight Management Servers, Cartridges, and Monitored Hosts can be added as needed. Note Review the terms of your Foglight license agreement for details regarding license keys for additional Foglight Management Servers. Please review Planning Your Installation before beginning your Foglight Installation and refer to the Foglight v4.1.4/4.2.4 Release Notes for updates on Foglight system requirements, product information, and documentation.
What is Involved in a Foglight Installation on Windows

The Foglight installation proceeds through the following steps: Installing the Foglight Management Server Additional Steps for NT Cluster Environments Continuing the Foglight Server Installation Installing Foglight Cartridges Completing the Foglight Server installation
Foglight Management Server and NT Clusters

Installations of Foglight Management Servers in an Active-Active cluster environment are not supported. You can install a Foglight Management Server on only one node of an active-active cluster. The remaining cluster members may be used for fail-over if desired.
Please read Installing Foglight on an NT Cluster before beginning your Foglight Management Server installation. Before installing the Foglight Management Server, both NT Cluster nodes must have valid license keys. The keys are stored in the LICENSE.HOSTNAME file in the WORLD directory (the same directory as the current Foglight Management Server license file). After installing Foglight, you will also need to create a cluster resource and bring the resource online.
54
SQLServer Clusters
The Foglight SQLServer Agent monitors SQL Servers running in a Windows cluster environment. To monitor SQL Servers in a Windows cluster environment you must follow specific installation instructions. For more information, see the SQLServer Cluster Handling online help topic.
Installing the Foglight Management Server

Do not install a Foglight Monitored Host and a Foglight Management Server on the same machine.
If you are installing a patch release, such as Foglight 4.1.4/4.2.4, on a Windows machine, do not use your FGL_HOME directory or any of its subdirectories as this temporary location. Use the -d flag to change the target directory when unzipping files
1.
Insert Disk 1 of the Foglight v4.1.4/4.2.4 Windows Installation bundle in your CD-ROM drive. From the CD-ROM directory, double-click setup.exe to begin the installation process. Setup preparation begins. When the preparation process completes the Foglight Server Setup Welcome screen displays.
55
Quest Foglight
2.
Click Next to continue. The License Agreement screen displays.
3.
After reading the Quest Software License Agreement, click Yes to accept the terms of the agreement and proceed with your installation. The Choose Destination Location screen displays.
To install in a different folder, click Browse and select a new folder. 4.

56
To install in the folder displayed, click Next to continue.
Note If you do not have an NT Cluster environment, proceed to Step 5. Additional Steps for NT Cluster Environments a) If you have an NT Cluster, Foglight identifies the server as part of a cluster.
Click Yes if you have an active-passive array. Click No if you have an active-active array. The Foglight Server Alternate Hostname screen displays.
Set the local hostname to the cluster alias or to a name of your choice. The local host name you select will appear on the Foglight Operations Console. b) Click Next to continue with the installation.
57
Quest Foglight
Continuing the Foglight Server Installation The Select Program Folder screen displays.
Select a program folder from the Existing Folder list or enter a new folder name in the Program Folder field. 5. Click Next to continue. The Foglight Server Instance Description screen displays.
Enter the name of your Foglight Management Server in the Description field. This is the title that displays on the Foglight Server
58
Manager and indicates which Foglight Management Server you are starting. 6. Click Next to continue. The Start Copying Files screen displays. Review your selections at this time.
Click Back to review or change settings. 7. Click Next to begin copying files. The Select Components screen displays.
59
Quest Foglight
Select the checkbox next to the components you want to install. The amount of disk space require for files displays so you can confirm you have enough space on your C drive for your selections. 8. Click Next to continue. The selected files are copied. The License Key screen displays. To continue with the installation, you must enter a Foglight License Key.
Select Yes if you have a Foglight License Key and continue to Step 9. Select No if you do not have a Foglight License Key. Most new installations do not have a valid license key prior to install. a) The License Key String window displays. The dynamic licensing process generates an alpha numeric string unique to your server.
60
Submit the generated string to Quest Customer Support. In return, you will receive a key to activate your system. Click Back to continue the installation. 9. After entering your License Key, click Next to continue. The License Key window displays. Note Quest Customer Support will inform you of the Foglight User Name and Password that is compatible with the type of license you purchased.
Enter your Foglight License Key in the License field.

61
Quest Foglight
10. Click Next to continue. The DBRepository Location screen displays.
DBRepository is configured. The default is C:\Program Files\Quest Software\Foglight-Server\DBRepository. Click Yes to select a different location. Click No to accept the default location. 11. Click Next to continue installation. The Configuration Parameters screen displays.
62
Click the Help button for information and instructions pertinent to User Name, Passwords, and port numbers.
Please refer to Required TCP/IP Communication Ports and Firewalls, Identifying Ports in the Planning Your Installation chapter for details about ports and firewall considerations. If you are a non-root user, you will not be allowed to choose port numbers below 1024. These are well known ports that are, typically, protected for standard communication usage. Foglight Database Hostname Running the MySQL database on another server is not supported in this release. Select the default database hostname or, if preferred, enter the fully qualified hostname.
12. Click OK to continue. Installing Foglight Cartridges The Cartridge Install screen displays.
Click Yes to install Foglight cartridges on your server.
63
Quest Foglight
Click No to finish the installation without loading any cartridge files. If you select No, you will continue your installation with Completing the Foglight Server Installation. Installing Cartridges After an Initial FMS Installation To install Foglight cartridges at a later date, see Installing Cartridges in the Post-Installation Tasks chapter of this guide. 13. Insert the Foglight Application Cartridge disk.
Enter your CD-ROM drive or click Browse to select the location of your CD-ROM drive. Note If you are installing cartridges after your initial Foglight Management Server installation, you will see an additional step at this time which allows you to indicate the Foglight Management Server installation you wish to use. See Installing Cartridges in the Post-Installation Tasks chapter of this guide for more information. 14. Click OK to continue. The Select Cartridges screen displays.
64
Select the checkbox next to the cartridges you want to install. Deselect any cartridge operation systems you do not want to install. The amount of disk space required for files displays so you can confirm you have enough space on your C drive for your selections. 15. Click Next to continue. The Setup Status screen displays and the cartridges you selected are installed.
If prompted for the additional FGL Cartridge Setup disk, insert the disk in your CD-ROM drive.
65
Quest Foglight
Enter your CD-ROM drive or click Browse to select the location of your CD-ROM drive. 16. Click OK to continue When the installation is complete the final Cartridge Setup InstallShield screen displays.
Click Finish. Completing the Foglight Server installation Foglight notifies you of important system information using email. Use the SMTPHOST Name and Administration E-Mail ID windows to enter the addresses you want Foglight to use for communication of system messages.
66
Enter the Name of the mail server you want the Foglight Management Server to use to send system messages. 17. Click Next to continue. The Administrator E-Mail ID screen displays.
Enter the SysAdmin email address you want the Foglight Management Server to use to send system and administrative messages. Note You may need to resolve any security issues that may block email sent from Foglight to your DBA and System
67
Quest Foglight
Administrator. The Foglight Management Server sends email from Foglight to the email addresses you set up when configuring Foglight communication. For example, if you define your System Administrators mail ID as "sysadmin@yourcompany.com", Foglight will send mail from "foglight@yourcompany.com". See the Security section in the Planning Your Installation chapter of this guide for more information. 18. Click Next to continue. The InstallShield Wizard Complete screen displays and the Foglight Server Setup is complete.
Sometimes the library libz.so is not found and an error is reported. This may be a failure in the wizard, but can be identified directly by running foglight doping. To resolve this, add /usr/local/lib (if that is where libz.so is located) to LD_LIBRARY_PATH.
Select the Launch Foglight Operations Console checkbox to launch Foglight at the completion of installation. When the installation is complete, the Foglight Management Server is added to your Windows Start menu. Shortcuts to the Foglight Manager and the Foglight Operations Console are added to your desktop. 19. Click Finish to complete the installation process.
68
Launching Foglight
If you selected the Launch Foglight Operations Console checkbox before clicking Finish, the Login dialog displays when the installation is complete.
Enter your Server Name or choose your server from the drop-down list. Enter the User Name and Password provided by Quest Customer Service. Click OK.
Foglight Manager
The Foglight Manager window displays, showing your Foglight Management Servers and Clients and their status. Note Launching Foglight from your desktop using the Foglight Server icon also launches the Foglight Manager window.
Select the tab for the Foglight Management Server or Client you wish to view.
69
Quest Foglight
You can use Foglight Manager to perform the following operations: Start or stop your Foglight Management Server or Foglight Client Update your Foglight License key Configure your Foglight Service Launch the Foglight Operations Console
Starting or Stopping Foglight

Click the Start button to start your Foglight Management Server or Foglight Client. If the Start button is disabled, the Foglight Management Server or Client is already running. Click the Stop button to stop the FMS or Foglight Client. If the Stop button is disabled, the Foglight Management Server or Client is already stopped. The status bar of the Foglight Manager displays the current status of the Foglight Management Server
70
Launching the Foglight Operations Console

Click the Operations Console button to launch the Foglight Operations Console. A dialog displays, prompting for your Foglight Server name, username, and password. Note You can only launch the Foglight Operations Console for your Foglight Management Server using the Foglight Manager. To launch the Foglight Operations Console for a Foglight Client, click the appropriate icon on your desktop or the Start menu.
Updating Your Foglight License

If you are running your Foglight Management Server with a temporary license, you will need to upgrade the Foglight License to a Permanent license. The status bar of the Foglight Manager displays your current License Key type. To update your Foglight License: Click the Update License button. The Foglight License Update dialog displays.
The generated string you must supply to Quest Customer Support displays on this dialog. To change your License Key, enter a new License Key and click Verify. Note You must stop and start Foglight after changing your License Key.
71
Quest Foglight
Configuring Your Foglight Service

Click the Configure Server button to change your Foglight service configuration. The Foglight Service Configuration dialog displays.
Service startup Select the Autostart Foglight service on reboot checkbox to start your Foglight Management Server when you reboot your machine. The advantage to starting the service at restart time is that Foglight will automatically start and begin monitoring your infrastructure. Run Service as Note Quest does not recommend changing from System to User unless this is required for the functionality of your Foglight Cartridges. Select the System radio button to run your Foglight service as System. The Login and Password fields are unavailable for change if you choose this option. Select the User radio button to run your Foglight service as a specific User. Note You must stop and restart your Foglight Management Server after you make changes to the Foglight service.
72
4
Installing Foglight on Monitored Hosts
Overview Installing the Foglight Client on a Monitored Host Installing a Windows Client from a Windows Workstation Additional Considerations
Quest Foglight
Overview
Foglight client software can be installed as: Push installations: The Installation Wizard, located on the Foglight Operations Console, is used to install Foglight client software on a host you want to monitor. From your Foglight Management Server, running on either UNIX or Windows, you can push the Foglight Client out to any UNIX or Windows host. Note You can create a Windows monitored host from your Windows Foglight Management Server without logging directly onto the host machine. Pull installations: Performing the client installation from the monitored host.
To perform a client installation, you need permissions to log on to your Monitored Host. On Windows hosts, this is administrator privileges (username, password, and domain). For UNIX hosts, this is the userid and password. Note If you install as non-root on UNIX on certain platforms, there are post installation tasks you must perform to ensure that particular agents will run. See Installing Foglight Monitored Hosts from the Command Line on page 91 for details.
Verifying Performance Counters for Windows Monitored Hosts

The Foglight monitored host installation checks for any performance counters that have been disabled, as this may adversely affect the client operation. On monitored hosts with Windows 2000 operating systems and above, the system disables performance counters under certain circumstances without any warnings or messages (see Microsoft Knowledge base article Q248993). This verification involves checking for the value "Disable Performance Counters" within the registry key(s): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ <servicename>\Performance If the value exists and its data value is 1, the <servicename> has been disabled` and a dialog box displays, asking you to confirm the re-enabling of the disabled performance counter. Click Yes to re-enable the performance counter. This will not require a reboot or any other user action.
74
Installing the Foglight Client on an Monitored Host

1. 2. Launch the Foglight Operations Console. Choose Wizards, Install from the Foglight Operations Console menu. The Installation Wizard Step 1 dialog displays. Note If your Windows host operation system type is not recognized by your UNIX Server, see Operating System Recognition on page 76 for instructions.
Discovered Hosts and Selected Hosts

Select the hosts you want to install and use the arrow buttons to move them into the Selected Hosts list.
Host Lookup
If the target host is not included in the Discovered Hosts list, use the Host Lookup button to search your network for additional hosts. Click Host Lookup. The Find Host dialog box displays.
75
Quest Foglight
Type the target host name in the Host Name field and click Find. If the host is found, the host name and IP address display. Click the OS Type field and select the operating system from the drop-down list. If the host is not found, the Install Wizard displays a prompt asking if you want to add the host. Click Yes to add the host.
The Host Name field is populated. Enter the IP address the IP Address field Select the operating system type from the OS Type drop-down. Click OK to close the Add Host dialog box, then click OK to close the Find Host dialog. Proceed to Step 3.
Operating System Recognition

If your host operation system type is not recognized by your Foglight Management Server, the Edit Host OS Types dialog displays.
76
Highlight the hosts and click OS Type. A drop-down list displays. Select the OS Type from the list. Highlight the host and click Remove to delete an item from the list of selected hosts. Note Once the OS Type is selected, the Install Supported column displays whether it is supported or not. If it is not supported, see Resolving Unsupported Operating System Types on page 90. 3. Click Next to continue. The Foglight Installation Wizard Step 2 screen displays.
Set the configuration parameters for each operating system used by the hosts selected in Step 1.
77
Quest Foglight
Note For this example, the WinNT tab is used. The selections on the Linux, Solaris, HP, and AIX tabs match the configuration requirements for those operating systems. Login Name Password Target Directory Port Number: Enter your userID or Username. Enter your Password. Enter the directory where you want to install the Foglight client. Enter the port number used by the host to communicate with your Foglight Management Server. Enter the temporary location for Foglight client installation files.
Windows Install Dir.:
Security
Select the SSH checkbox for encrypted communication between the Foglight Management Server and client during the installation. Note You may have to initiate SSH from a command prompt to set up and verify SSH connections. Select the SUDO checkbox if you wish to use SUDO permissions. Note SUDO is not available if you have logged on as root.
Agents
Choose the agents you wish to install by selecting the checkbox next to the agent name.
Choosing other operating systems

If you want to install hosts that use other platforms, you may want to populate your Foglight Compress directory with files from your installation CD-ROM. 4. Click Next to continue. The Foglight Installation Wizard Step 3 screen displays. In this step, you can customize each host in the list by: Selecting Agents to Bind Changing Login Information Advanced Setup for NT Clusters and IP Addresses
78
To customize a host, select the host from the list displayed. The option buttons are available once a host is selected.
Selecting Agents to Bind

Click the Select Agents button to choose the agents you want to install on the monitored host. The Select Agent dialog box displays.
Select the agents you want to install. Click OK.

79
Quest Foglight
Changing Login Information

Click the Login Info button to set login information for each selected monitored host during the monitored host installation process. The Edit Login Info dialog displays
Change information as required. Click OK to continue.
Advanced Setup
Use this button to: Enter optional information for your NT Cluster. Add an IP address if your server and monitored host are on separate subnets.
Click the Advanced Setup button. The Advanced Setup dialog box displays. NT Cluster Information Optional process: If you want to monitor your NT Cluster by its logical name, you must enter the logical name of your NT Cluster at this time.
80
Enter the logical cluster name or IP address in the Cluster Name field. The cluster name writes to the $FGLHOME/World/DBVARS LOCAL_HOSTNAME variable. Foglight Server IP Setup If the Foglight Management Server and monitored host are on separate subnets, you can use the Foglight Management Servers IP address instead of its hostname for communications with the monitored host.
Select the Use IP checkbox and enter the server IP Address. 5. Click OK to save your changes.
81
Quest Foglight
6.
Click Finish to save your settings and start the installation. The Foglight Installation Summary dialog box displays.
This window contains two tabs: Summary Logs The Summary tab shows the installation status for each host. The Logs tab shows each step in these processes. The information is also written to the dactl.log file in the Foglight home logs. Problems display on the Logs tab. If the installation failed the first time, click Retry. If the process fails a second time, check the Logs tab and correct any problems recorded there. Re-run the installation by clicking Finish on the Installation Wizard Step 3 dialog.
Once the installation is successful, click OK to close the wizard.
82
Installing a Windows Client from a Windows Workstation

Foglight supplies a separate executable file, FglClient.exe, for installing Foglight Client software on a Windows workstation. During the installation process, you must configure the monitored host to communicate with the server and database. Download the Foglight Client executable: 1. 2. From the Windows monitored host, open a browser and navigate to the Foglight Management Server. If the http process associated with the Foglight Management Server is not listening on port 80 you need to log into the Foglight Web Console as http://<foglight hostname>:httpport where httpport is, by default, 80. Login with your user name and password. By default this is foglight, foglight. The Web Console displays.
3.
4.
Click the Downloads icon. The Downloads page displays.
5.
Click the Foglight NT Client link to download the client installation executable.
83
Quest Foglight
Install the Foglight Client 1. Double-click the FglClient.exe file to start the Foglight Client InstallShield Wizard.
Select a location to unpack the installation files. Your temporary directory is the default location for unpacking. If you do not have enough room in your default temporary location, click Change to point to a location with more free space. 2. Click Next to continue.
84
The Choose Destination Location screen displays.
Click Browse to change the path name to the folder where you want the Foglight monitored host to install. 3. Click Next to continue. The Select Program Folder screen displays.
4.
Click Next to continue.
85
Quest Foglight
The Foglight Client Setup Configuration Parameters screen displays.
Foglight Server Parameters Enter your Foglight Database Hostname. This is typically your Foglight Management Server. Enter your Foglight Server Hostname. Foglight Client Parameters RAPSD Port Number: Enter the RAPSDPORT number from your $FGLHOME/World/DBVARS file. NSS Port Number: Enter the NSSPORT number from your $FGLHOME/World/DBVARS file. MySQL Parameters User Name and Password: Enter the USERNAME from your $FGLHOME/World/DBVARS file. Enter the corresponding password. MySQL Server Port Number: Enter the DBPORT number from your $FGLHOME/World/DBVARS file. Database Name: Enter the SERVERNAME from your $FGLHOME/World/DBVARS file.
86
5.
Click OK to continue. The NT Agent List screen displays.
Select the NT Agents to bind to this monitored host. 6. Click Next to bind the agents to the monitored host. This process can take several minutes depending on the number of agents being installed. The InstallShield Wizard Complete screen displays.
7.
Click Finish to exit the wizard.

87
Quest Foglight
Additional Considerations
Agents Appear in a Broken State
When installing as non-root, some Foglight agents and cartridges may appear in a broken state. To resolve these issues, you may have to configure the agents using Edit, ASPs from the Foglight Operations Console toolbar or you may have to set permissions of certain files to execute as non-root.
Virtualization Support
Foglight 4.x.3+ running on AIX DLPARS/LPARS
Foglight System agents now function when installed and operated on AIX Dynamic Logical Partitions or Static Logical Partitions. Running on AIX D/LPARS reports correct system performance metrics. A key difference with the 4.1.2 release is the ability to collect most data with user-level permissions. Note: if you have been collecting data using root permissions and you want to change to user-level permissions, you will need root permissions to effect the change.
Foglight AIX Agents AIX_Console
Minimum Permission user, but root permission is required to pick up the su log entries
Note When using the AIX_Console on Foglight 4.x.3 and running as a non-root user, failed attempts to sudo are not shown even when the su log is properly specified.
AIX_MPStat AIX_System DiskIO FS_AIX_DiskIO FS_AIX_NIC

88
user user user user user
Foglight AIX Agents FS_AIX_System FileSystem NIC Process User user user user user user
Minimum Permission
Solaris Zones
Foglight 4.x.3+ has the ability to monitor Solaris 10 Zones. New Platform support for 4.1.4/4.2.4: Solaris 10x86 (including system agents) Foglight System Agent Minimum Permissions for Solaris 10x86 and Sparc root user root user user user, however root required and running in the global zone for Disk, Controller and Volume data to be collected user user
SUN_Console FileSystem NIC Process User DiskIO
SUN_MPStat SUN_System
89
Quest Foglight
Foglight System Agent
Minimum Permissions for Solaris 10x86 and Sparc Sun_TCP relies on /dev/ip to read network packets. On SunOS5.10, /dev/ip can only be accessed in the global zone as root. It is explicitly not available in non-global zones for security reasons. This means that the Sun_TCP agent can be installed only if: a) the foglight client is running in the global zone b) the foglight client is installed as root (or via sudo)
SUN_TCP
Resolving Unsupported Operating System Types

During server installation, you can select which monitored host operating system files to support. In the case of installation on a server running Solaris 5.8, you can select from a list of compatible Solaris-compatible operating systems. Selecting these options installs the necessary files into the /Compress directory to support monitored host installations of that OS type. If you do this, all of the files required to install monitored hosts on the supported OS Types are installed into the a /Compress directory. If you install from a server when OS type files have not been installed into the /Compress directory, you will receive an OS Type not supported message. For a Foglight Server running on Solaris 9: 1. 2. Obtain the installation CD-ROM. Copy the Client.<OSType>.<Foglight Version>.fgl.pax.Z* files from the installation CD-ROM into the $FGLHOME/Compress directory. Note The system environment variables %FGLHOME%, %FGLARCH%, %RAPSHOME% and %RAPSARCH% are not delivered with the Foglight installation and must be set manually. 3. Re-run the Install Wizard.
90
Performance Counters
When re-enabling performance counters during a Foglight Client installation on Windows, a registry key name displays with the following message: First call to RegDBQueryKey failed Unable to read registry key. This message indicates that Foglight is unable to query the key because the key is locked or the installer lacks read permission. You must either change your permissions or call Quest Customer Support for further instructions.
Installing Foglight Monitored Hosts from the Command Line

You can use the dactl and bindda commands to install Foglight monitored host software from the command line. For more information, see Command Line Utilities in the Foglight Administration Guide.
91
Quest Foglight
92
5
Post-Installation Tasks for UNIX Systems Stopping and Starting the Foglight Management Server Launching the Foglight Operations Console Installing the Foglight Operations Console on other workstations Installing Cartridges
Quest Foglight
Post-Installation Tasks for UNIX Systems

If you installed Foglight with the recommended non-root user, you should perform the following two steps to automatically start Foglight when your Foglight Management Server is rebooted and to scan your network for possible Foglight remote hosts. Note These tasks are also listed as part of the final steps of the Foglight Installation on UNIX.
Automatic Start
The install script created two files in the $FGLHOME/tmp directory. $FGLHOME is the Foglight installation directory. The S99_42FGL file needs to be placed in the /etc/rc2.d directory by the root user and the K03_42FGL file needs to be placed in the /etc/rc0.d directory by the root user. If these two files are not found in the $FGLHOME/tmp directory, the files S99_42FGL.tmpl and K03_42FGL.tmpl, also located in the $FGLHOME/tmp directory can be edited, replacing the FGLHOME place holder with the path to $FGLHOME, saving the files without the .tmpl extension, and placing these files in the appropriate /etc/rt*.d directories. Note If you have more than one Foglight 4.1.4/4.2.4 Server running on the same machine, you should edit the existing /etc/rc2.d/S99_42FGL and /etc/rc0.d/K03_42FGL files, adding the entries for the new server.
Host Autodiscovery
This process will display some of the Foglight clients that you may want to install using the Installation Wizard from the Foglight Operations Console. If you do not perform this step as the root user, you will need to provide the names of hosts you want to monitor. As the root user, from the Foglight installation directory ($FGLHOME), run ./foglight autodisc -c -q to automatically find many of the possible Foglight monitored hosts that you can install. You can view the discovery process in the $FGLHOME/logs/autodisc.logs file.
94
Starting and Stopping the Foglight Management Server

Foglight can be stopped and started manually. Perform the following steps to launch the Foglight Management Server. To shut down the Foglight Management Server on a UNIX system From the Foglight installation directory ($FGLHOME), enter the following command: ./foglight stopfgl To start up the Foglight Server on a UNIX system From the Foglight installation directory ($FGLHOME), enter the following command: ./foglight startfgl To start up or shut down the Foglight Management Server on a Windows 2003 system 1. 2. Double-click the Foglight Server Manager icon. Click the Start Foglight Server or Stop Foglight Server button as desired.
Launching the Foglight Operations Console

You can view a Foglight Management Server from another system by installing the Foglight Operations Console. The operations console can be installed on Microsoft Windows or UNIX machines. To launch the Foglight Operations Console from UNIX 1. From the fji directory, type the following command: ./startfji Note As a shortcut, you can also type ./startfji YourSrvr foglight and skip step 2. 2. Run the command: ./foglight or ./foglight -debug
95
Quest Foglight
3.
To log in to your FOC, log in as: Server Name hostname: rmiport User: foglight Password: foglight Where hostname should be the Foglight Management Server hostname or IP address and rmiport is the RMI_REGISTRY_PORT number as seen in the $FGLHOME/World/WEBVARS file. The default Foglight user name is foglight and the default password is foglight. This can be changed in the FOC by selecting Tools, Access Manager.
4.
Click OK.
To launch the Foglight Operations Console from Windows 1. Double click the FOC desktop icon. To log in to your FOC, log in as: Server Name hostname: rmiport User: foglight Password: foglight Where hostname should be the Foglight Management Server hostname or IP address and rmiport is the RMI_REGISTRY_PORT number as seen in the $FGLHOME/World/WEBVARS file. The default Foglight user name is foglight and the default password is foglight. This can be changed in the FOC by selecting Tools, Access Manager. 2. Click OK.
Installing the Foglight Operations Console on Other Workstations

The Foglight Operations Console is automatically installed on the Foglight Management Server. You have the option of installing the operations console on other workstations. To run the Foglight Operations Console on a remote workstation, you must first download the appropriate files from the Downloads page in the Foglight Web Console. Installing the Foglight Operations Console on additional Windows workstations Open the Foglight Web Console, click the 3rd icon (Download) in the top right corner, then download and run the fji.exe file, following the steps in the Install Wizard.
96
Installing the Foglight Operations Console on additional UNIX workstations Open the Foglight Web Console, click the 3rd icon (Download) in the top right corner, then download the fji.shar.gz file and uncompress and extract its contents to a working directory.
Installing Foglight Cartridges

Foglight Cartridges can be installed after completion of an initial Foglight Management Server installation.
Installing Cartridges on UNIX

Follow this example to install Foglight Cartridges after completion of an initial Foglight Management Server installation. Example For this example, $FGLHOME is at /export/home/foglight and the CD-ROM is mounted at /cdrom. The user wishes to add the WebLogic cartridge. 1. 2. Change directory to $FGLHOME cd $FGLHOME From the cd, copy the WebLogic cartridge files from the /cdrom/Compress directory to the $FGLHOME/Compress directory. Note Note: Unix versions end in fgl.pax.Z. Only cartridge files that match the client operating systems you chose during your initial FMS installation can be installed. For Example: If you want to install the Foglight Cartridge for WebLogic on Linux and SunOS5.7, issue these commands: cp -p /cdrom/Compress/WebLogic.Linux.2.4.v42.000.*.fgl.pax.Z $FGLHOME/Compress cp -p /cdrom/Compress/WebLogic.SunOS5.7.v42.000.*.fgl.pax.Z $FGLHOME/Compress 3. Copy the DCMs for the WebLogic cartridge from the cd to $FGLHOME/DCMs directory: cp /cdrom/Compress/DCMs.WebLogic.zip $FGLHOME/DCMs 4. Change directory to $FGLHOME/DCMs:
97
Quest Foglight
cd $FGLHOME/DCMs 5. 6. 7. 8. 9. Unzip the WebLogic DCM file: $FGLHOME/tools/bin/SunOS/unzip -o -aa DCMs.WebLogic.zip Remove the WebLogic zip file from the DCMs directory: rm $FGLHOME/DCMs/DCMs.WebLogic.zip Change directory to $FGLHOME: cd $FGLHOME Copy the cartridge version file to the World Directory: cp /cdrom/Compress/WebLogic.ver $FGLHOME/World Perform a fglloadagent for the cartridge: $FGLHOME/foglight fglloadagent WebLogic -noNeUpdate 10. Update the existing host before adding the WebLogic agent by running this command from the Foglight Management Server: FGLHOME/foglight setHostState <host_name> 4
Installing Cartridges on Windows

The post- FMS installation of Foglight Cartridges includes an additional step to the initial cartridge installation, allowing you to choose the Foglight Management Server you wish to use for your cartridge installation. To install a Foglight Cartridge after Your FMS Installation: 1. Open this guide to Installing Foglight Cartridges in the Installing Foglight on Windows chapter. The post- FMS Cartridge installation starts with Step 13. Insert the Foglight Application Cartridge CD in your CD-ROM drive. This CD starts the Cartridge installation process. Confirm the location of your CD-ROM drive by clicking OK. The Cartridge Install screen displays.
2. 3.
98
Your current Foglight Management Server installation is detected. The location of this installation populates the FGLHOME field. Type the location of another Foglight Management Server if this is not the location where you wish to install cartridges. For example, you may have multiple Foglight Management Server installations on one machine and want to choose which FMS installation you wish to use for your cartridge installation. 4. 5. Click Next to continue the cartridge installation process. Follow the steps for Installing Foglight Cartridges in the Installing Foglight on Windows chapter to complete your installation.
99
Quest Foglight
100
6
Monitoring NT Clusters
Overview Getting Started Installing a Monitored Host on an Active-Active NT Cluster Installing a Monitored Host on an Active-Passive NT Cluster Post Installation Tasks Testing Fail-Over
Quest Foglight
Overview
Foglight monitoring of NT Cluster arrays begins with your installation of the Foglight Management Server. During the FMS installation and when installing a Foglight Client on a Monitored Host, your cluster array is identified and setup steps specific to NT Clusters are included in the installation processes. Please review Installing Foglight on Windows as well as Installing Foglight on Monitored Hosts before proceeding with the steps in this chapter.
Foglight Monitors the following NT Cluster arrays

Foglight Management Server on a Active-Passive NT Cluster Monitored Host on an Active-Passive NT Cluster Monitored Host on an Active-Active NT Cluster Installations of Foglight Management Servers in an Active-Active cluster environment, except for fail-over, are not supported. You can install a Foglight Management Server on only one node of an active-active cluster. The remaining cluster members may be used for fail-over.
Monitoring NT Clusters Using the Foglight SQLServer Cartridge

To monitor SQL Servers in a Windows cluster environment you must follow specific installation instructions. For more information, see SQLServer Cluster Handling in the Foglight Operations Console online help.
102
Getting Started
Not all portions of this chapter pertain to all NT Cluster environments, nor is it necessary to follow the instructions in sequence. Please refer to the section that pertains to your NT Cluster array. To install Foglight on your Monitored Host 1. 2. Choose the section that pertains to your environment and follow the installation steps. After installation is complete, perform the post installation tasks.
Note After installing Foglight, you will also need to create a cluster resource and bring the resource online.
Installing the Monitored Host on an Active-Active NT Cluster

These steps set the Foglight monitored host to run on one or more nodes of the cluster at any given time, reporting data to the Foglight Management Server. To install the monitored host: 1. As the Foglight Client installation program runs, the following dialog box displays as part of the Install Wizard.
103
Quest Foglight
Click Browse to select the directory where you want to install the monitored host. Click Next to continue. 2. A Question dialog displays, stating the node is part of an NT Cluster.
For an active-active environment, click No. 3. Click Next and follow the prompts to complete the installation wizard. Completing the installation wizard concludes this section.
Installing the Monitored Host on an Active-Passive NT Cluster

The Foglight monitored host must be installed on the cluster member that currently owns the shared disk on which you wish to install the Foglight monitored host. To install the monitored host: 1. As the Foglight Client installation program runs, the following dialog displays as part of the Install Wizard.
104
Click Browse to select the directory where you want to install the monitored host. For an active-passive cluster, the directory you choose must be on a shared disk. 2. A Question dialog displays, stating the node is part of an NT Cluster.
For an active-passive environment, select Yes. 3. A dialog displays with the local hostname (the name of your local workstation).
105
Quest Foglight
Set the LOCAL_HOST_NAME to the cluster alias. The local hostname that you set is what will appear on the Foglight GUI. 4. Click Next and follow the prompts to complete the installation wizard.
When you have completed the installation wizard see Deactivating the Foglight Manager on page 107 to continue setting up your NT Cluster environment.
106
Post Installation Tasks

Review these tasks and apply those that pertain to your environment.
Deactivating the Foglight Manager

For an active-passive cluster array, this optional process ensures the Foglight Manager is deactivated on node where your monitored host resides. Using the Foglight Manager to start or stop Foglight may interfere with the NT Cluster service manager. To turn off the Foglight Manager: 1. Stop the Foglight monitored host and make sure the Auto-Start Foglight Service on Reboot check box on the Configure Service dialog is not selected.
107
Quest Foglight
2.
On the Windows toolbar, hide the Foglight Manager.
3.
Delete the Foglight Manager shortcut from the Desktop.
4.
Delete the Foglight Manager shortcut from the Windows Start menu.
When you have deactivated the Foglight Client Manager, see Creating a Foglight NT Cluster Resource on page 109 to continue setting up your NT Cluster environment.
108
Creating a Foglight NT Cluster Resource

These steps create the NT Cluster Resource that controls the Foglight monitored host or server for failover. To create the resource: 1. Open the Cluster Administrator and select File, New, Resource.
2.
Create a new Generic Service and click Next.
3.
Select the nodes of the cluster that this resource will be in. Select a node from the Available nodes list and click Add to move them into
109
Quest Foglight
the Possible owners list.
Click Next to continue. 4. Add the shared disk that the Foglight monitored host is installed on as a Resource Dependency. Select a resource from the Available Resources list and click Add to move them to the Resource Dependencies list.
Click Next to continue. 5. Enter the Foglight Service in the Service Name field. Leave the Start parameters field blank. Click Next to continue.
110
Note For a Foglight Management Server, the Service Name will be Foglight Service. For a Foglight monitored host, the Service Name will be FglClient - Hostname, where Hostname is the hostname of the monitored host Click Next to continue. 6. Click Add to add the Registry Key System\CurrentControlSet\Services\Foglight Service.
Note For a Foglight Management Server, the Service Name will be Foglight Service. For a Foglight monitored host, the Service
111
Quest Foglight
Name will be FglClient - Hostname, where Hostname is the name of the monitored host. 7. Enter the name of the root registry key and click OK.
A message displays indicating that the Foglight cluster resource is created.
When you have created the Foglight Cluster Resource, see Bringing the Foglight Cluster Resource Online on page 113 to continue setting up your NT Cluster environment.
112
Bringing the Foglight Cluster Resource Online

These steps activate the Foglight Cluster Resource, starting the Foglight monitored host or server and enabling fail-over. To bring the cluster resource online: 1. Right-click the newly created resource and select Bring Online to start the service.
113
Quest Foglight
2.
Open Windows Task Manager to confirm that the process is online.
3.
Click End Process.
114
Testing Fail-Over
The following is an example of testing the process. Note If this test is being performed by a Quest Professional Services representative, be advised that the customer must give permission to run this test. To test fail-over: 1. Right-click Cluster Group. Select Move Group. This will fail over the cluster group to the other cluster member.
You are still on PCCLUSTER1. The owner is now PCCLUSTER2. No Foglight monitored host is running.
The Foglight monitored host is running on PCCLUSTER2.
115
Quest Foglight
116
7
Installing the Foglight Transaction Recorder and Transaction Player
Overview Installing the Foglight Transaction Recorder and Player
Quest Foglight
Overview
The Foglight Transaction Recorder (FTR) and the Foglight Transaction Player (FTP) allow users to perform web application performance monitoring on Windows-based systems.
Foglight Transaction Recorder

The Foglight Transaction Recorder has the same look and feel of an Internet browser. The Foglight Transaction Recorder allows you to create synthetic transactions that resemble actions performed by web site users. Service level objective times of a web site can be gathered and compared, showing actual response time versus expected response time, to provide feedback when response time has degraded. After recording a web site, the Foglight Transaction Recorder saves the recorded transaction in a script. The scripts created in the Foglight Transaction Recorder are uploaded to the Foglight Management Server.
Foglight Transaction Player Agent

The Foglight TransactionPlayer Agent plays the scripts recorded with the Foglight Transaction Recorder back at regular intervals and reports the results to Foglight. From Foglight, users can view a variety of graphs that provide detailed results on the transaction response time, transaction availability, and other statistics vital to web end user performance monitoring.
System Requirements
Foglight Transaction Recorder: Internet Explorer version 6.0 or higher Windows 2000/XP
Foglight Transaction Player: Internet Explorer version 6.0 or higher Windows 2000
118
Installing the Foglight Transaction Recorder and Transaction Player
Installing the Foglight Transaction Recorder and Player

Installing the Foglight Transaction Recorder and Transaction Player components is a two-part process: 1. 2. Installing the Foglight Transaction Recorder on a Windows OS. Installing the Foglight Transaction Player on a Foglight Monitored Host.
Note The following installation steps assume the Foglight Management Server and Foglight Operations Console have been installed. To begin the installation: 1. From Internet Explorer, navigate to the Foglight Web Console on the Foglight Management Server, http:// <Foglight Server Name>. The Foglight Login console displays. Note If the Foglight Management Server was installed on a port other than the default port of 80, be sure to append the port number to the URL. For example, http://fglserver:8080. 2. 3. 4. Enter your username and password. Click Login. Click the Download hyperlink in the upper right-hand corner of the screen.
5.
Scroll down and locate the Transaction Recorder and Player section of the Downloads page.
119
Quest Foglight
To Install the Foglight Transaction Recorder a) Click Transaction Recorder. b) The File Download dialog displays. Click Open. c) The InstallShield Wizard displays. Click Next. The Choose Destination Location dialog displays. Accept the default or browse to the desired folder location. Click Next. d) The Select Program Folder window displays. Accept the default location. Click Next. e) The Foglight Transaction Recorder installs. f) The InstallShield Wizard Complete window displays. Click Finish. To Install the Foglight Transaction Player a) Click Transaction Player. b) The File Download dialog displays. Click Open. c) The InstallShield Wizard displays. Click Next. d) The Setup Status window is displayed while the Foglight Transaction Player installs. If the restart option displays, click the Yes, restart my computer now radio button. Click Finish.
120
8
Uninstalling Foglight
Uninstalling Foglight on UNIX Uninstalling Foglight on Windows
Quest Foglight
Uninstalling Foglight on UNIX

To uninstall Foglight from a UNIX system: 1. 2. On each Foglight host, type the following command to stop Foglight: ./stopfgl From each Foglight host, type the following command to remove the Foglight directory: rm -rf $FGLHOME 3. On your Foglight Management Server, type the following command to stop Foglight: $FGLHOME/script/stopfgl 4. From your Foglight Management Server, type the following command to remove the Foglight directory: rm -rf $FGLHOME
Uninstalling Foglight on Windows

Use Windows Add/Remove Programs to uninstall Foglight. Note The Foglight program will be removed using this process, but you will have to clean your database separately.
122
Glossary
This glossary has been provided to assist you in defining words and phrases you encounter in reading this guide. This is not meant to redefine common industry phrases that do not appear in the glossary.
A
Agent Rules A category in the Rule Browser, these rules are associated with an agent. Agent Startup Parameters (ASP) Parameters determining the scope of data collection for the agent. Applications Part of service groups in Service Models, applications are groups of tiers, rolled up through the hosts. Application maps Display servers associated with an application and are automatically generated. Application maps are available for PeopleSoft, mySAP.com, Siebel, and WebLogic.
B
Blackouts See Rule blackouts.
C
Cartridge A group of agents specially designated for a particular system, such as PeopleSoft, SAP, and Siebel. Categories Used in the Rule Browser, different types of rules are associated with particular categories. These are three categories in the Rule Browser: Agent Rules, Custom Rules, and Policy Rules. Client The Foglight Client software used for monitoring hosts.
123
Quest Foglight
Common agent startup parameters These include purging and weeding parameters and are found on the first page of every agent startup parameter dialog. Custom maps Also known as user-defined maps, allow you to manage larger environments by organizing your server population into a manageable set of maps rather than having all server icons display in a single IP Map. Custom Rules A group of rules you create that use data collection by more than one agent on more than one host. Custom Rules are a category in the Rule Browser. A custom rule crosses agents and/or hosts.
D
DBVARS File containing many Foglight Management Server parameters, including port settings and database parameters. A subset of this file is passed on to monitored hosts during installation. Directories Listable The BEA WebLogic Server property weblogic.httpd.indexDirectories is true. If the property is true, then a URL that points to a directory returns the contents of the directory, as long as it is in the public html location. If the property is false, then pointing to the directory only allows index.html to be viewed. Domain In the Foglight Registry, a domain houses variables used in rule definitions or with the Network Services agent. These domains include the Rule domain, Services domain, System domain, and World domain. Dynamic reports Displays data for all nodes below the point where it is bound on the map. For example, a FileSystem agent is bound to host A and host B. A dynamic report for the FileSystem agent is bound at a node above hosts A and B. Therefore, the report displays data from both hosts. Global or dynamic views can be used in dynamic reports.
124
Glossary
Dynamic views Displays data for all nodes below the point where it is bound on the map. For example, FileSystem agents may be associated with Host A and Host B on a map. A dynamic view for FileSystem agent data that is bound to a node above those hosts will include data from FileSystem agents on both Hosts A and B. Dynamic views can be used in dynamic reports.
E
Email actions See Rule actions. Evaluation parameters See Rule evaluation parameters. Exist status codes Codes used in e-mail notifications from scheduled tasks to communicate job status.
F
Folders Folders are an organizational node used in custom maps and Service Level Policy definitions. Foglight Client The Foglight Client software used for monitoring hosts. Foglight Registry Collection of variables that control Foglight in the database. FMS Foglight Management Server FOC Foglight Operations Console
G
Global views Global views are associated with a specific agent@hostname. Groups See Security groups or Registry groups.
125
Quest Foglight
H
Hostname The name of the host machine.
I
IP Map The main map that displays a master grouping of all servers, which is automatically generated. See also Application maps and Custom maps.
L
List variables A list variable contains one or more variables. List variables require a unique name to identify and define the list. Local reports Local Reports are associated with a specific agent@hostname. Only global views are used in local reports. Locations Used in Service Models, locations are part of service groups and indicate where the services are consumed.
M
Maps See Performance maps. Monitored Host A system monitored by the Foglight Client software.
N
NE The Foglight Notification Engine. It applies rules to database samples in order to locate conditions on networked computers and dispatch informational and corrective actions.
O
OID Object Identifier. The unique ID used in Foglight to specify an object.
126
Glossary
P
Passivations The process of transferring an enterprise bean from memory to secondary storage. In the WebLogic agent, it is the current number of beans deactivated per minute. Performance maps A term that includes all Foglight maps: IP Map, Application maps, and Custom maps. Policy See Service Level Policy. Policy Rules A group of rules you created to support a policy. Policy Rules are a category in the Rule Browser. Purging The process that deletes data samples from the Foglight database. You determine how often purging occurs in the agent startup parameters.
R
Registry groups A group context is a group of hosts used to resolve a variable. You can assign a variable to all hosts at the same time by putting those hosts in a group and defining a variable at the group level. The variable assigned to a certain group is resolved according to a top-down hierarchy. Remote executable action Program that runs on behalf of the RAPSD program as a result of firing a rule. REPORTS domain The REPORTS domain contains the threshold variables for various reports that are used by the web console. REX action See Remote executable action. Root Exposure In the WebLogic agent, the port number is on port 80, or any other port number less than 1024, and the BEA WebLogic Server property weblogic.syste.enableSetUID is
127
Quest Foglight
true. This indicates that the Bea WebLogic Server is running with root privileges, which is a serious security risk. Rule A rule is the logical expression of a condition that is continuously evaluated by Foglight to be either true or false. Rule actions Rule actions are fired when a rule is satisfied. There are five types of rule actions: Email actions, agent actions, REX actions, and SNMP actions. Within SNMP actions, there are generic SNMP, NetCool, and HPOpenView. Rule blackouts Periods of time when a rule is disabled. Schedule rule blackouts using the Scheduler tool. Rule domain This domain contains variables used in rule definitions. It is not visible in the Foglight Registry. Rule evaluation parameters There are two types of rule evaluations, immediate and over a specified sample period. Rule families The various severities of one rule. There are four severities: normal, warning, critical, and fatal.
S
Security groups A security designation plus map level security are attached to each group. Users are then assigned to a group. Service groups Used in Service Models, service groups consist of three elements: Services, Applications, and Locations. Service Level Policy A Service Level Policy is used to track application availability. Each policy utilizes a hierarchy of rules and the state of those rules. A policy monitors hosts, agents, and rules with fatal events. Use the Policy Browser and Policy Editor to create policies.
128
Glossary
Services Used in Service Models, services are an element of service groups. Services are measured by Foglight Transaction Recorder scripts which correspond to logical physical hosts defined by foglight during installation. Services domain This domain contains services and variables used with the Network Services agent. Servlet Allowed The BEA WebLogic Server property weblogic.httpd.register.servlets equals the property weblogic.servlet.ServletServlet. If this value is equal to 1, then servlets can be run without registering them. BEA cautions about enabling this in a production environment because of security exposure. System domain This domain contains variables used in rule definitions. It is not visible in the Foglight Registry.
T
Tag A name for a transaction category. It is used with the Netscape Server agent transaction list.
U
User-defined maps See Custom maps.
V
Views Graphs or tabular presentations of data collected by agents. Tabular views are not the database tables that you can browse using the Data Browser.
W
Web Application Archive file In WebLogic, a file used to install the WebLogic cartridge. The WAR file is located by default in the config/weblogic/java directory under the Foglight home directory $FGLHOME. The file is named QuestApp.war.
129
Quest Foglight
WEBVARS File containing port settings and interface parameters for the Foglight Operations Console and the Foglight Web Console. World domain This domain contains variables used in rule definitions. It is visible in the Foglight Registry. You will use the World domain if you create custom variables for rule definitions. Workspace A unique named context within the WebLogic server where a client can store and retrieve arbitrary objects, and make objects available to other clients for sharing.
Z
Zooming The ability to enlarge a specific area of a graph.
130
INDEX
A about Quest Software 13 agent selecting 33 AJP Connector 21 Apache 21 C cartridge selecting 33 changing TCP/IP ports 20 command line monitored host installation 91 communication 33 communications resolving IP address issues 25 D database connection configuration 33 DBVARS file implementing changes 25 documentation online help 13 dynamic IP address resolving allocation 25 F fail-over testing, NT Cluster 115 firewall issues ports 25 Foglight architecture 8 license key 30, 54 selecting product 32 Solaris 5.8 installation 29 Solaris 5.8 server installation 32 starting 93 stopping 93 uninstalling on Solaris 5.8 121 UNIX host, command line installation 91 Foglight AJP Connector 21 Foglight Apache web listener port 21 Foglight Client Manager deactivating 107
Foglight Installation Wizard 43 Foglight NE port 20 Foglight Operations Console 43 Foglight RMI port 22 Foglight server configuration options 19 Foglight TCP/IP port 20 I installation directory 33 Foglight on Solaris 5.8 29 Foglight Solaris 5.8 server 32 Foglight UNIX host from command line 91 IP address resolving communications 25 resolving dynamic allocation 25 J JDALSERV editing 25 L language support 26 license key 17, 30, 33, 54 M monitored host installation log 82 N NE 20 notification engine 20 notification subscription support 21 NSS (notification subscription support) 21 NSSPORT 21 NT Cluster active-active client installation 103 active-passive installation 104 active-passive monitored host installation 104 bringing cluster resource online 113 creating cluster resource 109 deactivating Foglight client manager 107 testing fail-over 115
131
Quest Foglight
O operating system diagnosing unsupported errors 90 P ports AJP Connector 21 Apache web listener 21 DBCONN_ENCRYPT token 25 FoglightDBserver 20 NE 20 NSSPORT 20, 21 NSSPORT value 25 required open 25 RMI 22 TCP/IP 20 Tomcat shutdown 21 product, selecting 32 Q quit 33 R removing Foglight software Solaris 5.8 122 RMI 22 S security issues 23 selecting Foglight product 32 Solaris 5.8 Foglight installation 29 Foglight server installation 32 uninstall Foglight 121 source directory 32 starting Foglight 93 stopping Foglight 93 system requirements 19 T TCP/IP 20 changing ports 20 Tomcat shutdown port 21 Transaction Recorder requirements 118 TransactionPlayer requirements 118
U uninstall Foglight on Solaris 5.8 121 UNIX Foglight host installation from command line 91 unsupported OS 90
132

Install Guide 4x4

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Install Guide 4x4

Transféré par

Droits d'auteur :

Formats disponibles

4.1.4 4.2.

2008 Quest Software, Inc. ALL RIGHTS RESERVED.

How Foglight Works

APPLICATION TIER Applications

About This Guide

Chapter 8 provides installation instructions for the Foglight Transaction

Foglight Online Help

Foglight User Guides

About Quest Software, Inc.

Contacting Quest Support

Prepare for your Installation

Planning Your Installation

Review System Performance Considerations

Collect Your System Information

Check for Specific Installation Issues

Planning Your Installation

System and Hardware Requirements

Discontinuation of Deprecated Monitored Host OS platforms

FMS Installation Location

Foglight performance may vary according to the server configuration.

Required TCP/IP Communication Ports

Planning Your Installation

PORT HTTP Port

Tomcat AJP Port

Tomcat Shutdown Port

PORT RMI Registry Port

JDAL Server Port

Command Servlet Port

Planning Your Installation

System Performance Considerations

Foglight Email and Your Email Security

Planning Your Installation

Network Address Translation

Using Foglight to Monitor NT Clusters

Planning Your Installation

Monitoring NT Clusters Using the Foglight SQLServer Cartridge

What is Involved in a Foglight Installation on UNIX

Installing Foglight on UNIX

Installing the Foglight Management Server

Looking at the Main Installation Menu

1. Enter Foglight Source Directory

Installing Foglight on UNIX

Performing Your FMS Installation

Installing Foglight on UNIX

The Foglight Installation Welcome screen displays.

Installing Foglight on UNIX

Set the Installation Directory

Configure Your Database Connection

Press Enter to select Configure Database Connection.

Installing Foglight on UNIX

Configure Foglight Communication and Select Agents

Installing Foglight on UNIX

Installing Foglight on UNIX

Select Foglight Clients

Installing Foglight on UNIX

Select Foglight Cartridges

17. Press Enter to choose Select Cartridges. A list of cartridges displays.

Enter the Foglight License Key

19. Press Enter to select Enter License Key.

Installing Foglight on UNIX

The Enter Foglight License Information screen displays.

a) Enter your License Key and press Enter to continue.

If you do not have a Foglight License Key: