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

Foglight Agent Manager 6.3.0 - 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

Launching the Agent Manager installation interface

You can change many of the settings available in the Agent Manager installer at a later time using the Agent Manager Installation and Configuration interface.

IMPORTANT: On Windows 7 and Vista, it is recommended to run the command fglam ‑‑configure from an administrator version of cmd.exe or PowerShell (not just logged in as administrator) if you installed the Agent Manager as administrator.
4
Review the information in the Introduction step, and click Next.
5
In the Host Display Name step, set the desired options, if applicable, and click Next.
The Update Client ID step appears. This step allows you to reset the unique identifier assigned to this Agent Manager. Change the Agent Manager ID if you discover that its ID is the same as another Agent Manager’s ID.
6
If Quest Support instructs you to reset the unique ID assigned to this Agent Manager instance, select the Yes, reset this client’s ID check box. Otherwise, ensure that the check box is clear.
7
Click Next.
The Server URLs step appears.
8
Continue to navigate through the remaining steps and set the desired options, as prompted. Use the Next and Previous buttons to navigate through the steps. The remaining steps are the same as in the Agent Manager installer interface. For more information, see Installing the Agent Manager using the installer interface.
9
When you navigate to the Summary step, click Finish.

Configuring the Agent Manager to run in FIPS-compliant mode

Whether the Agent Manager is FIPS-compliant is determined by the Foglight Management Server from which the Agent Manager installer is downloaded. That is to say if the Agent Manager installer is downloaded from an FIPS-compliant Foglight Management Server, the Agent Manager will be configured to FIPS-compliant automatically, and vice versa.

You can check the value of the property fips.approved.mode.enabled in <fglam_home>/state/default/config/client.config file to see in which mode this Agent Manager is running. If the property is True, it means this Agent Manager is FIPS-compliant, and vice versa. In case the property is not found, it means this Agent Manager is not FIPS-compliant as well.

NOTE: Do NOT change the value of fips.approved.mode.enabled property, otherwise the Agent Manager won’t work with the Foglight Management Server if their FIPS-compliant modes are inconsistent.

Configuring the Agent Manager from the command line

If you are running multiple instances of the Agent Manager from one installation directory, before you begin, ensure that no other instances are running from the same directory as the instance that you want to configure.

fglam --configure ‑‑headless --no-start-on-exit

For more information about these options in the installation interface, see Step 7: Install init.d Script (Unix) and Step 9: Windows Service .

The AuthToken step appears.
5
Review the information in the Introduction step, and press Enter.
6
In the Host Display Name step, set the desired options, if applicable, and press Enter.
The Update Client ID step appears. This step allows you to reset the unique identifier assigned to this Agent Manager if you discover that this Agent Manager is using the same identifier as another Agent Manager.
The Server URLs step appears.
9
When you navigate to the Summary step, press Enter.
10
Restart the Agent Manager instance in the desired mode. See Starting or stopping the Agent Manager process for information about the different modes in which you can run the Agent Manager.

Configuring the Agent Manager to use SSL certificates

You can configure the Agent Manager to communicate with the Management Server using an HTTPS connection.

You can set this option either while installing the Agent Manager, or after installation. See Installing the Agent Manager , or Configuring the Agent Manager , for more information about configuring the Agent Manager to connect to the Management Server using HTTPS.

By default, Foglight® ships with a self-signed SSL certificate. If you configure the Management Server to use an SSL certificate signed by a third-party Certificate Authority (CA), whose root certificate is already included in the JRE used by the Agent Manager, you do not need to add a new CA to the Agent Manager keystore. Instead, ensure that the Agent Manager connects to the Management Server using HTTPS.

You must add a new CA to the JRE used by the Agent Manager if:

The Agent Manager includes command-line options for managing certificates in the Agent Manager keystore.

You add a new CA by importing a new root certificate for the CA into the certificate store used by the Agent Manager, as described below.

1
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/jre/<jre_version>/jre/bin directory.
keytool --keystore ..\path\cacerts -storepass changeit -list | findstr
<3rd_party_signer>
keytool --keystore ..\lib\security\cacerts -storepass changeit -list | findstr
godaddy
fglam --add-certificate <alias=/path/to/certificate>
If you are using the command-line version of the configuration interface, set the start of the url parameter to https (for example, url=https://server1.example.com:8443).
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択