Foglight Agent Manager 7.1.0 - Foglight Agent Manager Guide


	NOTE: All of the command-line options that you can specify when starting the Agent Manager installer also work with the --configure option that is used to launch the Agent Manager Installation and Configuration interface.

To launch the Agent Manager Installation and Configuration interface:

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

Stop the Agent Manager instance you want to configure.

Run the Agent Manager from the command-line with the --configure option:

<fglam_home>/bin/fglam --configure


	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.

The Agent Manager Installation and Configuration dialog box appears.

Review the information in the Introduction step, and click Next.

The Host Display Name step appears. For more information, see Installing the Agent Manager using the installer interface.

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.


	IMPORTANT: Do not reset the Agent manager ID unless Quest Support instructs you to do that.

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.

Click Next.

The Server URLs step appears.

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.

When you navigate to the Summary step, click Finish.

Restart the Agent Manager instance in the desired mode. For information about the available modes, see Starting or stopping the Agent Manager process .

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.

To launch the Agent Manager configuration command-line interface:

Stop the Agent Manager instance that you want to configure.

Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory.

Issue the following command:

fglam --configure ‑‑headless


	NOTE: If you want to install Agent Manager as a Windows service, or as a Unix deamon, the configuration interface appears with pre-selected options, indicating that the Agent Manager will start immediately after the installation. You can force these options to appear disabled by default (and enable them, if required, during the installation), if you start the fglam command with the --no-start-on-exit option: 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.

Review the information provided in this step. If you do not want to make any changes to the auth-token, press Enter.

A message appears while the configuration interface starts. When the configuration interface finishes loading, the Introduction step appears.

Review the information in the Introduction step, and press Enter.

The Host Display Name step appears. For more information, see Installing the Agent Manager from the command line.

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.


	IMPORTANT: Do not reset the Agent manager ID unless Quest Support instructs you to do that.

If Quest Support instructs you to reset the unique ID assigned to this Agent Manager instance, type Y at the prompt and press Enter.

Otherwise, accept the default option (N), and press Enter.

The Server URLs step appears.

Continue to navigate through the remaining steps and set the desired options, as prompted. The steps are the same as in the Agent Manager installer interface. For more information, see Installing the Agent Manager from the command line.

When you navigate to the Summary step, press Enter.

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.


	NOTE: If the root certificate for the third-party CA is not included in the JRE, follow the instructions in To add a new CA to the Agent Manager certificate store: .

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

•

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

and

•

The Management Server uses an SSL certificate signed by a private CA. This certificate must be checked for a valid signer.

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.

To check if a third-party CA is included in the JRE:

Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/jre/<jre_version>/jre/bin directory.

Issue the following command:

keytool --keystore ..\path\cacerts -storepass changeit -list | findstr

<3rd_party_signer>

For example:

keytool --keystore ..\lib\security\cacerts -storepass changeit -list | findstr

godaddy

godaddyclass2ca, Jan 20, 2005, trustedCertEntry,

godaddyrootg2ca, Jul 18, 2014, trustedCertEntry,

To add a new CA to the Agent Manager certificate store:

Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory.

Import a new root certificate for a CA that you want to add. To do that, issue the following command:

fglam --add-certificate <alias=/path/to/certificate>


	IMPORTANT: The certificate file that you import should be the public certificate for the CA that signed the SSL certificate, not the SSL certificate itself.