The following is documented in the Agent Manager Guide Configuring an Agent Manager Instance as a Concentrator.
NOTE: A FglAm configured as a Concentrator will not show its status as such in the Agent Status dashboard until it begins receiving data to concentrate and forward to the FMS.
Configure a FglAm concentrator to connect to accept connections on a specific port:
- Edit the $FGLHOME/state/default/config/fglam.config.xml file to specify the downstream port. See attached PDF example extract for setting downstream entry as port 8081.
When running the Agent Manager as a concentrator, 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.
Configure the size of the disk cache used to store messages
- Open the /state//config/fglam.config.xml file for editing.
- Locate the XML element.
- Edit the and blocks that appear after the block
- Change the argument for the max-disk-space attribute in both the and 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 and 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.
Configure the concentrator to listen for connections from downstream instances
1. Open the <fglam_home>/state//config/fglam.config.xml file for editing.
2. Locate the XML element. See attached PDF extract example.
3. After the block, add an child element:
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 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 require 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.