立即与支持人员聊天
与支持团队交流

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

Enabling connection type debugging

If the only information you are interested in is the types of connections that are being established, there is a command-line setting that enables logging the connection types.
Run the Agent Manager with the following switch:
-Dquest.debug.windowsinfo.types
 
* 
NOTE: This logging occurs every time a connection is established and can be very verbose. It is recommended for debugging purposes only.

UNIX- and Linux-Specific Configuration

Thistopic contains platform-specific configuration information for configuring the Foglight Agent Manager on UNIX® or Linux®.
If your database is installed on an HP-UX server, regardless of the operating system, see Using the HP Patch Checking Tool .

About the Supported Remote Monitoring Protocols

The Agent Manager supports the SSH (secure shell) protocol for remote monitoring of hosts running Linux® and UNIX® operating systems. SSH is a protocol which encrypts all traffic between the client and the server, and supports a wide variety of secure authentication mechanisms. SSH is available for installation on all platforms supported for remote monitoring by Foglight.
The Agent Manager does not support the older Telnet protocol for remote monitoring. Telnet is an insecure protocol which does not encrypt traffic, and requires that the passwords used to authenticate collections are sent in the clear. For that reason, supporting Telnet as a remote monitoring protocol potentially exposes monitored systems to trivial network eavesdropping attacks, disclosing passwords to attackers.
While it is possible to create a closed network with strong security boundaries within which it is safe to run the Telnet protocol, this use case is not common, and it is impossible for the Agent Manager to determine if Telnet is safe to use before offering it as an option for connectivity. Further, the effort required on the part of the user to maintain such a secure environment is far less than that required to simply enable SSH connections on a host. For these reasons, the Agent Manager does not support Telnet as a remote monitoring protocol.

Configuring the Agent Manager to Run as a Daemon

As described in Installing the Agent Manager using the Installer Interface and Installing the Agent Manager from the Command Line , you can install an init.d-style script called dell-fglam in the init.d directory on your system. This script is called when the host on which the Agent Manager is installed starts or shuts down, allowing it to run as a daemon.
Even if you choose not to install the init.d script during the installation, or if you do not perform the installation as the root user, the installer generates scripts that can perform the necessary setup.
These scripts are fglam-init-script-installer.sh and fglam-init-script.sh, and they are located in the <fglam_home>/state/default/ directory.
The script fglam-init-script-installer.sh installs the script fglam-init-script.sh into your system’s init.d directory as dell-fglam. Your system’s init.d process then uses dell-fglam to run the Agent Manager as a daemon.
To install the init.d script:
1
Launch a command shell on the Agent Manager machine and navigate to the <fglam_home>/state/default/ directory.
2
Optional. If you want to make any edits to fglam-init-script.sh to customize it for your system, do so prior to running fglam-init-script-installer.sh.
 
* 
IMPORTANT: Any customizations that you make to the script fglam-init-script.sh are not supported by Dell Inc..
3
Switch to the root user.
4
From the command shell, run the script fglam-init-script-installer.sh with the install option:
./fglam-init-script-installer.sh install
 
* 
IMPORTANT: This script must be run as root.
The setup script fglam-init-script-installer.sh installs the init.d script dell-fglam. See Locating the init.d Script for the location in which it is installed.
5
To start or stop the Agent Manager daemon manually, follow the instructions in To run the Agent Manager as a daemon on UNIX®: .
To remove the init.d script, follow the instructions in To remove the init.d script used to run the Agent Manager as a daemon on UNIX®: .
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级