サポートと今すぐチャット

オンラインヘルプの参照
登録の完了

サインイン

価格設定をリクエスト

営業担当に連絡

Foglight Agent Manager 5.9.3 - Foglight Agent Manager Guide

コンテンツのナビゲーション

Configuring the embedded Agent Manager

Getting started Interacting with the embedded Agent Manager

Automatic configuration of the Management Server host name and port number

Installing external Agent Managers

Understanding how the Agent Manager communicates with the Management Server

Syntax conventions

Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager

Installing the Agent Manager using the installer interface

Configuring Management Server URLs using the installer interface

Installing the Agent Manager from the command line

Configuring Management Server URLs from the command line

Using the Agent Manager silent installer Installing the Agent Manager as a Windows service

Starting or stopping the Agent Manager process

Identifying the Agent Manager process About platform-specific identification

Frequently asked questions

How do I upgrade the Agent Manager? How do I uninstall the Agent Manager? Where can I find the Agent Manager installation log files? Why does the message "Created system preferences directory in java.home" appear after I finish installing the Agent Manager on AIX? Are the passwords that are stored in the configuration file, fglam.config.xml, encrypted? How can I see what parameters are available for the silent installers? Why are two URLs displayed for localhost when I search for HA peers? I tested the connection between the Agent Manager and a Management Server, but the Management Server URL failed the connectivity test. Why did this happen? When I try to install the Agent Manager using the installer interface on Solaris x86 VMware, it fails and a warning message related to fonts appears. Why does this occur? Why does an AIX compatibility warning appear when I run the Agent Manager installer?

Configuring the Agent Manager

Operating system patches Launching the Agent Manager installation interface Configuring the Agent Manager from the command line Configuring the Agent Manager to use SSL certificates Configuring an Agent Manager instance as a Concentrator

Configuring the concentrator Configuring downstream Instances Creating a secure connection with downstream instances Excluding SSL ciphers from upstream or downstream Connections Excluding Specific SSL Protocols from Downstream Connections

Configuring the Agent Manager to accept connections from the Management Server Configuring the Agent Manager to execute commands on remote hosts Configuring multiple Agent Manager instances

Example: Running multiple instances in a cluster environment

Controlling the polling rate Configuring the Agent Manager to work in HA mode

Assigning Agent Managers to HA partitions Adding cartridges to the HA deployment whitelist About agent fail-over About non-HA deployments

Negotiating Agent Manager resources at runtime

Disabling runtime resource negotiation

Disabling agent-specific changes to the upstream queue

Configuring credentials

Managing lockboxes Releasing lockboxes to the Agent Manager

Troubleshooting

Errors related to Windows WMI and DCOM configuration Resolving DATA_COLLECTION_FAILED errors Adjusting the maximum polling interval

Advanced system configuration and troubleshooting

Configuring Windows Management Instrumentation (WMI)

WMI IPv6 connection support Windows Firewall interference Minimum requirements for Windows Management Instrumentation

Promoting remote users to administrators on local machines through the Domain Controller Granting required permissions to individual remote users

WMI access violation and OS connectivity verification failure WMI and Quota Violation error Known WMI issues in Windows Server 2008 Tuning WMI connections Modifying registry key ownership on Windows Server 2008 R2 Configuring registry settings for Windows Server 2008 R2 and Windows 7 Resolving Access Denied errors when connecting to Windows XP Professional OS collection fails with a Local_Limit_Exceeded error Access to DCOM objects and registry is denied Configuring registry settings for WinShell access through DCOM Enabling agents to connect from UNIX machines

Disabling UAC Granting access to dllhost.exe when Windows Firewall is enabled

Enabling agents to connect locally on Windows Releasing a locked MySQL process

Configuring Windows Remote Management (WinRM)

WinRM IPv6 connection support

About the cross-realm negotiate authentication behavior

About WinRM authentication and the Agent Manager Configuring the target (monitored) system Configuring the Agent Manager (monitoring) system Generating a configuration file required for WinRM Negotiate authentication Configuring command-shell connection settings About WinRM connection ports Troubleshooting

Verifying setup Identifying common causes of WinRM failures Reviewing application event logs Enabling connection type debugging

UNIX- and Linux-specific configuration

SSH IPv6 connection support About supported remote monitoring protocols Configuring the Agent Manager to run as a daemon

Locating the init.d script Obtaining the Agent Manager daemon status

Configuring Agent Manager agent privileges

Using sudo to configure secure launcher permissions Using setuid_launcher to configure secure launcher permissions

Using the HP patch checking tool About Agent Manager installations on AIX Preventing Agent Manager core dumps on Linux

Monitoring the Agent Manager performance

Investigating Agent Manager diagnostics

Exploring the Adapter Details tab

Message Processing tab XML Serialization tab Servlets tab

Exploring the Client Details tab

Agent Manager Clients view Message Processing tab Clock Skew tab Bandwidth tab Misbehaving Clients tab XML Serialization tab CPU Usage tab Memory Usage tab CDT Submission tab Queue Utilization tab

Deploying the Agent Manager to large-scale environments

Using Agent Manager silent installer Parameters Example: Deploying the Agent Manager to multiple UNIX hosts

Working with this example

Before you begin

Example: Creating and running an Agent Manager deployment script

Part 1: Create the working directory and script file Part 2: Create a list of hosts Part 3: Add the script parameters Part 4: Specify the script commands Part 5: Run the script

Example: Deploying the Agent Manager to multiple Windows hosts

Example: Using a software deployment tool and silent installer parameters

Part 1: Provide the silent installer parameters Part 2: Make the Agent Manager installers accessible Part 3: Run the software deployment tool

Part 5: Run the script

Once you have finished editing the deployment script, it is ready to run to deploy the Agent Manager to the remote UNIX hosts.

NOTE: This part of the example describes using one type of login method (passwords) for connecting to remote machines using SSH. However, if you have private keys configured in your environment, then you might encounter one of the following scenarios when establishing an SSH connection:

•

You do not need to provide a password because the host to which you are connecting is a trusted host.

•

You are prompted for a passphrase instead of a password.

1

Ensure that remote_install_fglam_example.sh is executable.

2

Execute the remote_install_fglam_example.sh script.

If Wget is not found on a host or if the operating system listed for a host in the hostnames file does not match the operating system types listed in the script, the script continues deploying the Agent Manager to the rest of the hosts that you specified in the hostnames file.

3

Provide a password for each host when you are prompted to do so.

The Agent Manager is installed and running on the specified hosts.

Example: Deploying the Agent Manager to multiple Windows hosts

The recommended method of deploying the Agent Manager to a large number of Windows hosts is to use a software deployment tool such as Microsoft® Systems Management Center.

Example: Using a software deployment tool and silent installer parameters

The example in this section outlines a scenario in which you use a software deployment tool and provide it with Agent Manager silent installer parameters to install the Agent Manager on multiple Windows hosts.

CAUTION: Using a deployment tool and Agent Manager silent installer parameters is an advanced activity. You should do so only if both of the following conditions apply:

•

You are a Foglight administrator who is familiar with configuring the Agent Manager.

•

You are certain of the setup that is required for your environment.


	NOTE: If you are not certain which installation options you need, run the interactive GUI or command-line installer on each machine instead.

Part 1: Provide the silent installer parameters

Provide the software deployment tool with the Agent Manager silent installer parameters that are required for your environment. See Using Agent Manager silent installer Parameters for more information.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約プライバシー Cookie Preference Center