• Diventare un professionista del portale
• Scaricare
• Stampa
• I miei download ()

• Supporto
• Documentazione tecnica
• Foglight Agent Manager 7.3.0
• Foglight Agent Manager 7.3.0 - Foglight Agent Manager Guide

Foglight Agent Manager 7.3.0 - Foglight Agent Manager Guide

Table of Contents  

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? 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?

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

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

Next steps

• Viewing Topics 97 - 100 of 144

×

Identifying common causes of WinRM failures

The following conditions can result in a WinRM failure:

•	The WinRM listener is not configured on the remote machine.

•	The AllowUnencrypted WinRM service configuration setting is false, and HTTP is used on the remote machine.

•	The expected authentication type is not enabled for the WinRM service on remote machine. For example, Basic authentication is expected to be used, but it is not enabled.

•	A fully qualified domain name is not specified in the user credential created on the Management Server.

•	An incorrect Kerberos configuration file is used. For example, the file does not exist on a UNIX system, or the realm is not set up for cross-realm authentication.

Reviewing application event logs

WinRM logs activity to an event log on the target machine. This includes both success and failure messages for authentication.

To view application event logs:

1	On the target machine, right-click My Computer and select Manage.

2	In the navigation tree on the left, choose System Tools > Event Viewer > Applications and Services Logs > Microsoft > Windows > Windows Remote Management > Operational.

The default Operational log contains the most common events.

To enable additional debug logging information:

1	Click View.

2	Click Show Analytic and Debug Logs.

3	Right-click the log file you want to view.

4	Select Enable Log.

Enabling connection type debugging

If the only information you are interested in is the types of connections that are being established, there is a command-line setting that enables logging the connection types.

Run the Agent Manager with the following switch:

-Dquest.debug.windowsinfo.types

 

NOTE: This logging occurs every time a connection is established and can be very verbose. It is recommended for debugging purposes only.

UNIX- and Linux-specific configuration

This contains platform-specific configuration information for configuring the Foglight Agent Manager on UNIX® or Linux®.

This section provides solutions for the following issues:

•	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

•	Configuring Agent Manager agent privileges

•	Preventing Agent Manager core dumps on Linux

•  Precedente
• Viewing Topics 97 - 100 of 144
• Successiva 

Cerca in questo documento Cerca in tutti i documenti

×

 Questo è il portale del supporto

Puoi trovare aiuto e supporto online per Quest *prodotto* sul sito di supporto di un affiliato. Fai clic su Continua per essere reindirizzato ai contenuti e all'assistenza corretti per *prodotto*.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione

© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center