Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

Foglight Agent Manager 5.9.8 - Foglight Agent Manager Guide

Navegación de contenido

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 to run in FIPS-compliant mode 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

Configuring anti-virus exclusion settings 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 Permissions on registry keys to configure DCOM command shell connection 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 Enable DNS reverse lookup

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

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

UNIX- and Linux-specific configuration

Agent Manager service can't start automatically when the operating system restarts 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

Are the passwords that are stored in the configuration file, fglam.config.xml, encrypted?

Are the passwords that are stored in the configuration file, fglam.config.xml, encrypted?

Certain passwords that are specified (or stored) in the Agent Manager configuration file <fglam_home>/state/<state name>/config/fglam.config.xml are automatically encrypted when the Agent Manager restarts.

The passwords that are encrypted are the ones set as arguments for the proxy-pass, key-password, keystore-password, and truststore-password attributes in fglam.config.xml. These passwords are encrypted after you manually edit them in fglam.config.xml and then restart the Agent Manager.

The passwords stored as arguments for the key-password, keystore-password, and truststore-password attributes are also encrypted when you start an Agent Manager concentrator for the first time after configuring it to communicate with downstream instances using HTTPS. See Creating a secure connection with downstream instances for more information about this type of configuration.

In addition, you can specify the password that the Agent Manager uses when connecting to the Management Server using a proxy during or after the installation (using the Agent Manager configuration interface). This password is stored in an encrypted form in fglam.config.xml (as the argument for the proxy-pass attribute) when you start the Agent Manager after installation or restart after using the Agent Manager configuration interface. See Configuring Management Server URLs using the installer interface and Configuring Management Server URLs from the command line for more information about setting the proxy password through the Agent Manager installer or configuration interface.

How can I see what parameters are available for the silent installers?

You can see the list of parameters available for the silent Agent Manager installer by running the FglAM-<version>-<platform> command with the --help option.

Why are two URLs displayed for localhost when I search for HA peers?

If you specify a localhost address as the Management Server URL and then search for HA peers (while installing or configuring the Agent Manager), two URLs appear: one that shows the real machine name and one for localhost.

For example, you are installing the Agent Manager on server1, the same machine on which the Management Server is running. You type localhost and 8080 as the host name and port used by the Agent Manager to connect to the Management Server. After you search for HA peers, two URLs are listed: http://localhost:8080 and http://server1.example.com:8080.

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?

There are several reasons why a Management Server (or Agent Manager concentrator) URL may fail the connectivity test, including the following:

•

The Management Server is not running. Verify that the Management Server is running by navigating to the Management Server URL in a browser:

<http|https>://<management_server_host_name>:<management_server_port>

If the Management Server is running, the Foglight Login Page appears. If the Login Page does not appear, follow the applicable instructions in “Starting and Stopping the Foglight Management Server” in the Installation and Setup Guide for the platform and database you are running to start the Management Server.

•

The Agent Manager adapter is either deactivated or uninstalled. Verify that the Agent Manager adapter is running by logging in to Foglight and navigating to Dashboards > Administration > Agents > Agent Adapters using the navigation panel.

If the Agent Manager adapter is running, the Agent Manager adapter (named FglAM) is listed in the Agent Adapters table and an Active icon (

) appears in the row for the adapter.

If the Agent Manager adapter is listed but no Active icon (

) appears in the row for the adapter, select the adapter and click Activate at the bottom of the dashboard.

If the Agent Manager adapter has been uninstalled (it is not listed in the Agent Adapters table), re-install the Agent Manager cartridge. See Deploying the Agent Manager cartridge for instructions.

•

You are attempting to connect the Agent Manager to a concentrator or Management Server over HTTPS, but your certificate has expired. Renew your certificate and test the connection again.

•

You are attempting to connect the Agent Manager to a concentrator or Management Server through a proxy configuration but your proxy is rejecting connections. Ensure that the proxy you specify is accepting connections and test the connection again.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center