지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight Agent Manager 5.9.5 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers
Understanding how the Agent Manager communicates with the Management Server Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager Starting or stopping the Agent Manager process Frequently asked questions
Configuring the Agent Manager Advanced system configuration and troubleshooting
Configuring Windows Management Instrumentation (WMI) Configuring Windows Remote Management (WinRM) UNIX- and Linux-specific configuration
Monitoring the Agent Manager performance Deploying the Agent Manager to large-scale environments

Releasing lockboxes to the Agent Manager

Each lockbox in the Management Server contains a set of credentials and keys for their encryption and decryption. Credentials are released to the Agent Manager unencrypted. When a lockbox is released to the Agent Manager, the Agent Manager passes the credential information to its agents. The agents use this information to establish connection with target resources.

When you start the Agent Manager without having first released a lockbox to it from the Management Server, the following message appears in the startup log:

INFO The Credential Manager has not been assigned any lockboxes. Lockboxes are used to decrypt credentials received as a result of an Agent Credential Query. Without any lockbox assignments, credentials received within a credential query result-set will be discarded. You can grant lockboxes to this Agent Manager through the Credential Administrator on the Server.

The lockbox you release to the Agent Manager must contain the credentials necessary for the agents to access the monitored resources.

 
* 
CAUTION: Any agents that have access to an Agent Manager with a released lockbox can potentially query and obtain credential information stored within that lockbox.
To release a lockbox to the Agent Manager:
1
Log in to the Foglight browser interface.
2
On the navigation panel, click Dashboards > Administration > Credentials > Manage Lockboxes.
3
On the Manage Lockboxes dashboard, in the row containing the lockbox that you want to release, click the Release to Credential Clients icon.
4
In the Release Lockbox to Credential Clients dialog box, type the lockbox password (if one exists) and select one or more credential clients (that is, Agent Managers) for lockbox release.
Figure 2. Release Lockbox to Credential Clients dialog box
 
* 
IMPORTANT: The System lockbox that is included by default with the Management Server is not password-protected. Its contents are accessible to all clients in your system.
5
Click Release.
The Release Lockbox to Credential Clients dialog box closes, indicating success.
6
Optional—ensure the Credential Clients column is populated.
a
Using the breadcrumb trail, return to the main Credentials dashboard, and navigate to the View Clients dashboard.
b
On the View Clients dashboard, ensure that the Show lockboxes currently assigned to each client check box is selected.
 
* 
NOTE: This functionality consumes server resources. It can be significant depending on the size of your client list.
The view refreshes, with the Assigned Lockboxes column populated.
c
Return to the main Credentials dashboard.
d
Navigate to the Manage Lockboxes dashboard.
e
On the Manage Lockboxes dashboard, observe the Credential Clients column of the newly released lockbox entry. The column lists the credential clients to which the lockbox is assigned.

When the lockbox is released to the Agent Manager, any credentials that are later added to the same lockbox are also accessible to the Agent Manager and its monitored agents.

Configuring anti-virus exclusion settings

Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory, processes, and executables from being scanned by the anti-virus software.

•
The common installation directory is as follows:
%fglam_home%
•
FglAM related processes and executables are as follows:
•
For Windows:
•
<FglAM Base Folder>\bin\fglam.exe
•
<FglAM Base Folder>\client\<version>\bin\bindDA.exe
•
<FglAM Base Folder>\client\<version>\bin\dcmlist.exe
•
<FglAM Base Folder>\client\<version>\bin\fog4_launcher.exe
•
<FglAM Base Folder>\client\<version>\bin\installer.exe
•
<FglAM Base Folder>\client\<version>\bin\qcn_relauncher.exe
•
<FglAM Base Folder>\client\<version>\bin\qcn_runner.exe
•
<FglAM Base Folder>\client\<version>\bin\qcn_watchdog.exe
•
<FglAM Base Folder>\client\<version>\bin\setDA.exe
•
<FglAM Base Folder>\client\<version>\bin\udp2icmp.exe
•
Non-embedded FglAM: <FglAM Base Folder>\jre\<jre_version>\bin\java.exe
•
For other operating systems:
•
<FglAM Base Folder>/bin/fglam
•
<FglAM Base Folder>/bin/setuid_launcher
•
<FglAM Base Folder>/client/<version>/bin/bindDA
•
<FglAM Base Folder>/client/<version>/bin/dcmlist
•
<FglAM Base Folder>/client/<version>/bin/fog4_launcher
•
<FglAM Base Folder>/client/<version>/bin/installer
•
<FglAM Base Folder>/client/<version>/bin/qcn_relauncher
•
<FglAM Base Folder>/client/<version>/bin/qcn_runner
•
<FglAM Base Folder>/client/<version>/bin/qcn_watchdog
•
<FglAM Base Folder>/client/<version>/bin/setDA
•
<FglAM Base Folder>/client/<version>/bin/udp2icmp
•
Non-embedded FglAM: <FglAM Base Folder>/jre/<jre_version>/bin/java

Troubleshooting

This section provides information about problems that you may encounter while running the Agent Manager and describes the solutions available for these problems.

Errors related to Windows WMI and DCOM configuration

If you encounter errors with WMI or DCOM configuration for remote agents, see Configuring Windows Management Instrumentation (WMI) and Configuring Windows Remote Management (WinRM) .

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택