Chat now with support
Chat with Support

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

Installing External Agent Managers

A Foglight™ agent is a component hosted by the Agent Manager that:
•
collects data from monitored resources
•
if necessary, manipulates data into the format required by the Management Server
•
submits the data to the Management Server using the Agent Manager
The Agent Manager is a middleware application that:
•
hosts agents
•
manages agent lifecycle (such as start, stop, and restart)
•
manages the connection to the Management Server
•
provides centralized services to agents
The Agent Manager supplies a centralized communications link between the Management Server and monitoring agents. It also provides a number of support services such as installation, upgrade, and the ability to configure agents.
•
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

Understanding How the Agent Manager Communicates with the Management Server

By default, the Agent Manager initiates communication with the Management Server. However, this communication is not always uni-directional. In some cases, the Management Server can initiate a reverse connection to the Agent Manager.
If the Agent Manager is configured with an open concentrator port, and the Management Server can resolve and connect to the Agent Manager host address, then the Management Server attempts to open a reverse connection to the Agent Manager as an optimization. This enables the Management Server to send agent control messages (for example, for starting or stopping the agent, configuration changes, or callbacks) without waiting for the Agent Manager to initiate a connection.
Configuring an open concentrator port is an optional step. If there is no concentrator, or if the Agent Manager cannot be reached by the Management Server due to NAT or a firewall, the Management Server buffers the messages until the Agent Manager polls. Therefore, Agent Manager connections through NAT or a firewall are fully supported.
Embedded Agent Managers always open a private concentrator port that is restricted to connections from localhost only. This automatically enables reverse connections without requiring any configuration.
For more information, see Configuring an Agent Manager Instance as a Concentrator.
By default, the Agent Manager installer uses the system-defined temporary directory (for example, /tmp or C:\TEMP) to unpack and execute the files required during installation. In some cases, such as when /tmp is mounted noexec, you may need to specify an alternate temporary location. To override the default temporary installation location, simply set the TMP, TEMP, or TMPDIR environment variable to point to a different location.
 
* 
NOTE: These variables are checked in the order listed. If more than one is set, the first valid setting is used.

Syntax conventions

•
[option1|option2] is used in file names at points where you must type, select, or otherwise specify one of multiple options. For example, FglAM‑[all|<platform>]‑<version>.car might be used in a step where you need to choose between the file FglAM‑all‑<version>.car or the file FglAM‑<platform>‑<version>.car.
•
<platform> represents the appropriate name for your platform. For example, FglAM‑linux‑x86_64‑<version>.car, for a 64-bit Linux® platform. For more information, see Downloading the Agent Manager Installer.
•
<version> represents the version number of the Agent Manager that you are installing. For example, FglAM‑<platform>‑6_0_1.car.

Deploying the Agent Manager Cartridge

Several types of Agent Manager cartridges are available in the FoglightClient‑FglAM‑<version> folder in the Server directory on Disk1 of your Foglight™ installation media or for download from our Support Portal.
The type of Agent Manager cartridge you deploy depends on your needs and the monitored environment:
•
The cartridge file FglAM-all-<version>.car contains Agent Manager installers for all supported platforms. Deploy this cartridge if you plan to install the Agent Manager on multiple platforms in your environment.
•
The cartridge files FglAM-<platform>-<version>.car contain platform-specific Agent Manager installers. Deploy a platform-specific cartridge if you do not plan to install the Agent Manager on more than one platform in your environment. Consult the table below for the appropriate installer name for your platform.
•
The cartridge file FglAM-patch-<version>.car can only be used to upgrade certain versions of the Agent Manager to the current version; it cannot be used for a new install. See the Foglight Upgrade Guide for more information.
The following table outlines which cartridges contain the appropriate Agent Manager installers for your platforms. HP-UX PARISC discontinued in Nightcrawler.
 
* 
NOTE: The cartridge FglAM-patch-<version>.car is not listed below. See the Foglight Upgrade Guide for more information about using this cartridge during the upgrade process.
 
Table 1. FglAM Cartridges available per OS
Operating System
Architecture
FglAM Cartridge
Multiple
Multiple
FglAM-all-<version>.car
HP-UX
PARISC
FglAM-hpux-parisc-<version>.car
HP-UX
ia64
FglAM-hpux-ia64-<version>.car
IBM® AIX®
POWER
FglAM-aix-powerpc-<version>.car
Linux®
ia32
FglAM-linux-ia32-<version>.car
x86-64
FglAM-linux-x86_64-<version>.car
Microsoft® Windows®
ia32
FglAM-windows-ia32-<version>.car
ia64
FglAM-windows-ia32-<version>.car (emulated)
x86-64
FglAM-windows-x86_64-<version>.car
Oracle® Oracle Solaris®
SPARC
FglAM-solaris-sparc-<version>.car
x86-64
FglAM-solaris-x86_64-<version>.car
To deploy the Agent Manager cartridge:
1
Log in to Foglight.
2
Navigate to the Cartridge Inventory dashboard (Dashboards > Administration > Cartridges > Cartridge Inventory).
3
On the Installed Cartridges tab, click Install Cartridge.
4
In the Install Cartridge dialog box, click Browse to navigate to and select the appropriate FglAM‑[all|<platform>]‑<version>.car file.
5
Ensure that the Enable on Install check box is selected.
 
* 
IMPORTANT: If the Enable on Install check box is not selected, you must manually enable all cartridges that are contained within the FglAM‑[all|<platform>]‑<version>.car file you are deploying.
6
Click Install Cartridge.
After you deploy the applicable cartridge for the Agent Manager, you can download the installer for your platform and install the Agent Manager. See Downloading the Agent Manager Installer , and Installing the Agent Manager .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating