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

Foglight Agent Manager 7.3.0 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers 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 the Agent Manager to execute commands on remote hosts

ExecuteCommandOnRemoteHostsAction is an action that is used for the Agent Manager to execute a command on remote hosts.

To configure this action for the Agent Manager:
* 
NOTE: Both Adapter and the Agent Manager must be upgraded to version 5.9.2 or later before the following procedure.
1
Add the ExecuteCommandOnRemoteHostsAction action to your rule list. For more information about how to add or edit an action in a rule, refer to the Getting Started: create a new rule or Getting Started: view and edit rule definitions section in the Foglight Administration and Configuration Help.
2
Specify the following parameters for the action as needed, then save your changes:
•
AgentManagerName (Mandatory): The Agent Manager name that is delegated to invoke the command on remote hosts.
•
CommandLine (Mandatory): The command to be executed remotely.
•
RemoteHosts (Mandatory): Target host addresses and platforms map, for example, hostName=Windows!hostIP=Linux. The platform value can be either of the following: Windows or Linux.
•
AgentManagerNameUseRegExp (Optional): The flag indicating whether the AgentManagerName parameter should be treated as regular expressions. This value is either true or false.
•
MatchAll (Optional): The flag indicating whether to run the command on all Agent Managers that matches the selection criteria. If set to false, the command will be executed only on the first matching Agent Manager.
•
Port (Optional): SSH connection port, default is 22. Windows platform does not need to configure this value.
•
Timeout (Optional): Command executing timeout value. Default is 0, which will use the Agent Manager default timeout value.
3
Go to the Dashboards > Administration > Credentials > Manage Credentials dashboard, add credentials for those remote hosts. The credentials usage must set to either “Execute Command On Remote Hosts For Windows” or “Execute Command On Remote Hosts For Unix”.
After saving your configurations and the rule is triggered, you will see the executed results on the server console or logs.

Configuring multiple Agent Manager instances

The files related to the Agent Manager’s run-time state (for example, configuration and log files), are saved in the <fglam_home>/state/ directory tree. Under the state directory, there is a sub-directory for each available Agent Manager instance.

You can run multiple instances of the Agent Manager using a single Agent Manager bin directory.

 
* 
CAUTION: Running multiple instances of the Agent Manager on the same host is intended for cluster and failover support only and is not intended to be used for any other purposes. Installing separate instances of the Agent Manager on the same system is therefore neither recommended nor supported.

In this type of configuration, you create multiple instances and each instance uses a different state directory but runs from a single Agent Manager bin directory. One example of this type of configuration is to test new agent settings without making changes to the agents you are currently using to monitor your production environment.

 
* 
CAUTION: In a configuration where multiple Agent Manager instances share one bin directory, each time you deploy agents, upgrade agents, or deploy Agent Manager upgrades to one instance, all other instances are also updated.

You can also configure multiple physical installations of the Agent Manager to use a corresponding state directory that exists on a single shared drive. One example use of this functionality is running the Agent Manager in cluster environments. See Example: Running multiple instances in a cluster environment for more information.

As described below, you create a new instance (and its associated state sub-directory) by including the --create-state and --location "<state_name>" (or -l "<state_name>") options with the fglam command; you then use the fglam ‑‑location "<state_name>" command to run that new instance.

 
* 
CAUTION: The --create-state and --location command-line options are not recommended for use with the embedded Agent Manager, because the embedded Agent Manager does not include its own JRE. Instead, it is configured by the Management Server to use the same JRE that the Management Server uses.Since the Management Server is not aware of additional state directories that you may have created, it cannot properly configure them. Instead, you need to manually configure and maintain the JVM location in the Management Server installation.

If you do not create multiple instances (by following the instructions below), the Agent Manager creates an instance called default and stores the state files in the state/default directory.

 
* 
IMPORTANT: On UNIX® platforms, the entire Agent Manager installation — including all state directories — must be owned by the same system user.
To create a new Agent Manager instance:
1
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory.
2
Issue the following command:
fglam --create-state --location "<state_name>"
Where <state_name> is the name of the new instance.
A new state directory is created in <fglam_home>/state/<state_name>.
To run an Agent Manager instance:
1
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory.
2
Issue the following command:
fglam --location "<state_name>"
Where <state_name> is the same instance name you specified above.

When you deploy agents to the instance, files related to the run-time state for these agents (including log files) are stored under the <fglam_home>/state/<state_name>/agents directory for that instance.

Example: Running multiple instances in a cluster environment

 
* 
IMPORTANT: This section is provided as an example only. The commands shown are fully supported, but the example itself does not describe a configuration that is supported as part of the product warranty.

One example use of this functionality is running the Agent Manager in cluster environments, since it allows the next assigned host in the cluster to relaunch an Agent Manager instance—and the specific agents it manages—when cluster failover occurs.

In this type of installation, there are multiple physical installations of the Agent Manager on different failover nodes. When one node fails and shuts down, the next one starts and its Agent Manager instance accesses the latest changes stored in its state directory on a shared drive.

The process of running multiple Agent Manager instances in a cluster environment follows the outline presented below.

Part 1: Install the Agent Manager on each node in the cluster

Begin by installing the Agent Manager on each node in your cluster. See Installing the Agent Manager for installation instructions.

Part 2: Initialize a state directory on the shared drive

When the Agent Manager installation is available to the nodes in the cluster, the next step is to initialize a state directory for an instance on the shared drive that is used by the cluster. When setting the state location locally from one of the nodes, you must define the full path to the remotely-mounted state directory.

In the following example, <state_dir> is a path to a state directory on a shared network server that is accessible locally from all machines. For example: on Windows clients, the <state_dir> can be f:\cluster_shared_dir\fglam_states\STATENAME_A, while on UNIX® clients, it is /mnt/cluster_shared_dir/fglam_states/STATENAME_A.

To set the state location, use the following command:

fglam --create-state --location <state_dir>

 
* 
NOTE: When you provide a full path with the --location parameter, the state directory can be located anywhere on the shared drive, it does not need to be in a subdirectory of an Agent Manager installation.
Part 3: Launch the Agent Manager from the active node

Run the Agent Manager from the active node and provide the full path to this instance’s state directory on the shared drive. For example:

fglam --location <state_dir>

The files related to the Agent Manager instance’s run-time state—for example, configuration and log files—are stored under its remote state directory on the shared drive.

Part 4: Deploy agents and create agent instances

When the Agent Manager is running, you can deploy agents to it and create agent instances. Files related to the run-time state for these agents (including log files) are stored under the remote state directory for this Agent Manager instance. Using the example above, they are stored in <state_dir>.

Part 5: Ensure exclusive access to the shared state directory

Ensure that only one instance of the Agent Manager that uses a particular state directory is running at a time. Do not run two instances of the Agent Manager on separate machines (or separate active nodes in the cluster) and cause these instances to use the same shared state directory simultaneously.

Controlling the polling rate

The FglAMAdapter, a component included with the Management Server, controls how often the connected downstream Agent Managers and agent instances connect and poll for messages. In general, the more hosts that are connected to the server, the less often they should be instructed to poll. The properties included with the FglAMAdapter control the polling behavior. They can be found on the Agent Properties dashboard. In most cases, changes to these properties are not required. Doing so is only recommended when instructed by Quest Support.

The polling rate is controlled by the following properties:

•
Minimum Polling Interval (seconds): The minimum polling interval, in seconds.
•
Maximum Polling Interval (seconds): The maximum polling interval, in seconds.
•
Polling Timeout (seconds): A time-out/grace period (in seconds) that the FglAMAdapter waits for a host to respond, before considering it as disconnected. This is used to account for clock skews and changes in timing typically seen on heavily loaded VMware images.

For more information about the Agent Properties dashboard, see the Administration and Configuration Help.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택