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

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

Configuring an Agent Manager instance as a Concentrator

A concentrator is an Agent Manager instance that functions similarly to an HTTP proxy. Configure it to accept connections from other Agent Manager instances (called downstream instances) and forward these connections to an upstream target, either the Management Server or another Agent Manager concentrator.

 
* 
NOTE: Concentrator ports can also be configured to optimize transmission of control messages from the Management Server to the Agent Manager. For more information, see Understanding how the Agent Manager communicates with the Management Server..
Figure 1. A simple Agent Manager concentrator configuration

You can configure one or more Agent Manager instances to act as a concentrator in situations where:

•
You do not want the Agent Manager instances on your monitored hosts to connect directly to the Management Server—for example, if you have a large number of Agent Manager instances running in your monitored environment and you want to reduce the number of connections to the Management Server.
 
* 
IMPORTANT: Using a concentrator reduces the number of connections to the Management Server, not the volume of data sent to the Management Server.
•
The Management Server is not co-located with the monitored hosts and you want to make only a single connection from the remote hosts to the Management Server—for example, if your Management Server is in Sydney and your monitored hosts are in Vancouver, and you only want to make one transpacific connection.
•
The Agent Manager instances cannot connect directly to the Management Server (as in the example below).
Example:

Your firewall configuration does not allow the Agent Manager instances on your monitored hosts to connect directly to the Management Server (running on ManagementServerHost). However, there is an intermediate host in your environment (IntermediateHost) that can accept connections from your monitored hosts and also communicate with the Management Server.

To allow connections from your monitored hosts to be forwarded to the Management Server, you install an Agent Manager instance on IntermediateHost and configure it as a concentrator:

1
While installing the instance on IntermediateHost (using the GUI installer), you specify the host name and port (ManagementServerHost and 8080) of the Management Server to which you want this concentrator to connect in the Configure Server URLs step.
2
When the installation is complete, you ensure that the instance is shut down and configure it as a concentrator by editing its fglam.config.xml file so that it listens for connections from downstream instances on a specified port (8081).
3
You restart the Agent Manager instance on IntermediateHost. This instance is now configured as a concentrator: it listens for connections from downstream instances on port 8081 and forwards data to the Management Server on port 8080.

Now that the concentrator is set up on IntermediateHost, you configure the Agent Manager instances on the monitored hosts to connect to the concentrator:

1
After stopping these Agent Manager instances, you run the Agent Manager configuration interface for each instance.
2
In the configuration interface, you specify the concentrator’s host name and the port on which it is listening (IntermediateHost and 8081) when setting the URL to which the instances connect.
3
Once the instances are re-configured to connect to the concentrator, you restart them.

The Agent Manager instances on the monitored hosts can now connect to the Management Server through the concentrator. You can also perform agent management tasks from the Management Server, such as deploying agent packages to the monitored hosts and creating new agent instances on them. There is no indication that the downstream instances are not connected directly to the Management Server.

Configuring the concentrator

This section describes how to configure the concentrator to connect to the upstream target (either the Management Server or another Agent Manager concentrator) and to listen for connections from downstream Agent Manager instances.

A concentrator’s upstream connection is independent of the downstream connections. For example, several Agent Manager instances on a local subnet can communicate to a concentrator using HTTP while the concentrator forwards requests over an non-secure network to the Management Server using HTTPS (or the other way around).

 
* 
CAUTION: Do not set up a concentrator to forward messages to itself or create any kind of loop or cycle. This causes the Agent Manager to indefinitely feeds messages through the loop.
To configure a concentrator to connect to the upstream target:

You can configure the concentrator to connect to the upstream target in different ways:

•
Using HTTP: Set the upstream target of the concentrator in the same way you typically set the Management Server URL:
•
During installation, use the Agent Manager Installation and Configuration interface, command-line interface, or silent installer. See Installing the Agent Manager for more information.
•
After installation, use the Agent Manager configuration interface. See Configuring the Agent Manager for more information.
•
Using HTTPS: To configure a concentrator connection to the Management Server using a secure connection, follow the instructions in Configuring the Agent Manager to use SSL certificates .

Between connections, the Agent Manager collects all upstream and downstream messages in queues. Queuing messages prevents them from getting lost in the event of a disconnection.

When running the Agent Manager as a concentrator, you must increase the default disk cache sizes.

 
* 
CAUTION: Increasing disk cache sizes is an advanced activity that involves custom tuning. The size of cache that you need depends on the number of hosts that connect to the concentrator and the type of load they put on the concentrator. The 1 GB value shown below is an example only.
To configure the size of the disk cache used to store messages:
1
Open the <fglam_home>/state/<state name>/config/fglam.config.xml file for editing.
2
Locate the <queue-sizes> XML element.
3
Edit the <upstream/> and <downstream/> blocks that appear after the <documentation> block:
•
Change the argument for the max-disk-space attribute in both the <upstream/> and <downstream/> blocks to a value larger than the default setting (1024 KB). For example, to change the default disk cache size to 1 GB, set the max-disk-space attribute in both the <upstream/> and <downstream/> blocks as follows:
max-disk-space="1048576"
The max-disk-space argument sets the amount of disk space (in KB) that can be used to store messages.
4
Save your changes to the fglam.config.xml file.
5
Restart the concentrator.
To configure a concentrator to listen for connections from downstream instances:
 
* 
NOTE: If you want to create a secure connection between the concentrator and downstream Agent Manager instances using HTTPS, follow the instructions in Creating a secure connection with downstream instances .
1
Open the <fglam_home>/state/<state name>/config/fglam.config.xml file for editing.
2
Locate the <http-downstreams> XML element.
3
After the <documentation> block, add an <http-downstream/> child element:
<config:http-downstream port="port_number" [address="network_address"]/>
a
Replace port_number with an available port number. This is the port on which the concentrator listens for connections from downstream Agent Manager instances.
b
Optional. If required, you can also bind the concentrator to single network address. To do so, include the attribute address="network_address" in the http-downstream child element (shown as an optional attribute in Step 3), replacing network_address with the network address where you want the concentrator to receive connections from the downstream instances.
The optional address attribute is useful when a machine has two or more network addresses, and you want the connections to the Management Server to go out from one, and the connections from the downstream instances to come in to another.
4
If required, configure the concentrator to listen for connections on multiple different ports by adding additional <http-downstream/> elements and setting the port number (and, optionally, the network address), as described above.
This is useful in situations where the concentrator machine has multiple network connections, and you want the concentrator to listen on different network connections with different ports. For example, the concentrator listens on network connection 1 with port 8081 and listens on network connection 2 with port 8082.
5
Restart the concentrator.

Configuring downstream Instances

This section describes how to configure the downstream Agent Manager instances to connect to the concentrator.

To configure the downstream instances to connect to the concentrator:
1
Configure downstream instances in the same way you configure any Agent Manager:
•
During installation, use the Agent Manager GUI, command-line, or silent installer. See Installing the Agent Manager for more information.
•
After installation, use the Agent Manager configuration interface. See Configuring the Agent Manager for more information.
2
At the step where you set the URL for Management Server, specify the host name and port for the concentrator instead of the Management Server.
3
If you want the downstream instance to connect to the concentrator using a secure connection, follow the instructions in Creating a secure connection with downstream instances .

Creating a secure connection with downstream instances

The following procedure can be used to create a secure connection between the concentrator and downstream Agent Manager instances using HTTPS.

To create a secure connection between the concentrator and downstream instances:
1
Stop the Agent Manager concentrator.
1
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/jre/<jre_version>/<jre>/bin/ directory.
2
If you do not already have an SSL certificate for the concentrator host, you can create a self-signed certificate by executing the following command on the concentrator machine, where <password> is replaced with your desired password:
keytool -genkeypair -alias fglam -keystore </path/to/fglam.kesytore> -storepass <password>
3
Respond to the prompts from keytool. Only the “first and last name” are required, all other fields can be left blank. The “first and last name” form the common name (CN) for this key pair and this needs to be provided to the Management Server (for reverse polling) or downstream Agent Managers (as the ssl-cert-common-name). You can type anything you want into this field, but the host name is the most common choice. The default value, if left blank, is Unknown.
4
Press Enter to set the key password to the same value as the keystore.
5
Open the file <fglam_home>/state/<state name>/config/fglam.config.xml for editing.
6
Between the existing <http-downstreams> and </http-downstreams> tags, add an <https-downstream/> child element:
<https-downstream key-password=<password> keystore=<path_to_keystore> port=<port_number> [address=<network_address>]/>
Where:
•
<password> is the same password you specified in Step 2 for -storepass. The password is saved in an encrypted form in fglam.config.xml when you restart the Agent Manager.
•
<path_to_keystore> is the path to the Agent Manager keystore.
•
<port_number> is the port number on which you want the concentrator to listen for connections from downstream Agent Manager instances.
•
<network_address> is the network address, to which the concentrator is bound when receiving connections from the downstream instances. This argument is optional. It is useful when a machine has two or more network addresses and you want the connections to the Management Server to go out from one, and the connections from the downstream instances to come in to another.
 
* 
IMPORTANT: Other optional attributes are available for the <https-downstreams> element. See the file fglam.config.xml for details.
7
If required, configure the concentrator to listen for connections on multiple different ports by adding additional <https-downstream/> elements and setting the arguments as described above.
This is useful in situations where the machine on which the concentrator runs has multiple network connections and you want the concentrator to listen on different network connections with different ports. For example, the concentrator listens on network connection 1 with port 8081 and listens on network connection 2 with port 8082.
8
Restart the Agent Manager concentrator.
9
Configure each downstream Agent Manager instance that connects to the Agent Manager concentrator using this secure connection so that:
•
It connects using HTTPS.
•
It accepts self-signed certificates.
•
It accepts a certificate with an unexpected common name (host name), and the common name for the certificate is set to Unknown.
See Configuring Management Server URLs using the installer interface or Step 10: Change service credentials [Optional] for information about these parameters, which you can set through the Agent Manager installer or configuration interface.
* 
NOTE: It is not recommended to enable the ssl-allow-self-signed configuration when the downstream Agent Manager is running in FIPS-compliant mode. If this configuration is disabled, you have to add the concentrator's certificate to the downstream Agent Manager's keystore in order to connect to the concentrator using HTTPS.
To export certificate from concentrator:
1. Locate the element <config:http-downstream> in <fglam_home>/state/default/config/fglam.config.xml file on concentrator Agent Manager, and get the path of the keystore corresponding to the downstream Agent Manager. If it is a relative path, it is relative to the path of "<fglam_home>/state/default/".
2. Launch a command shell and navigate to the <fglam_home>/jre/<jre_version>/jre/bin directory.
3. Issue the following command to export concentrator's certificate:
keytool -exportcert -noprompt -rfc -alias fglam-cert -file <exported-cert-filename> -keystore </path/to/keystore> -storepass <key-password> -storetype BCFKS -providerpath "<fglam_home>\client\<build-version>\lib\bc-fips.jar" -providername BCFIPS -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
To import the exported certificate to downstream Agent Manager:
1. Launch a command shell and navigate to the <fglam_home>/bin on the downstream Agent Manager.
2. Issue the following command to import certificate:
fglam --add-certificate <alias=/path/to/exported-cert-filename>
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택