3 |
Run the Agent Manager from the command-line with the --configure option: |
IMPORTANT: On Windows 7 and Vista, it is recommended to run the command fglam ‑‑configure from an administrator version of cmd.exe or PowerShell (not just logged in as administrator) if you installed the Agent Manager as administrator. |
4 |
5 |
6 |
If Quest Support instructs you to reset the unique ID assigned to this Agent Manager instance, select the Yes, reset this client’s ID check box. Otherwise, ensure that the check box is clear. |
7 |
Click Next. |
8 |
Continue to navigate through the remaining steps and set the desired options, as prompted. Use the Next and Previous buttons to navigate through the steps. The remaining steps are the same as in the Agent Manager installer interface. For more information, see Installing the Agent Manager using the installer interface. |
9 |
10 |
2 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory. |
4 |
Review the information provided in this step. If you do not want to make any changes to the auth-token, press Enter. |
5 |
Review the information in the Introduction step, and press Enter. |
6 |
In the Host Display Name step, set the desired options, if applicable, and press Enter. |
7 |
If Quest Support instructs you to reset the unique ID assigned to this Agent Manager instance, type Y at the prompt and press Enter. |
8 |
9 |
When you navigate to the Summary step, press Enter. |
10 |
Restart the Agent Manager instance in the desired mode. See Starting or stopping the Agent Manager process for information about the different modes in which you can run the Agent Manager. |
You can set this option either while installing the Agent Manager, or after installation. See Installing the Agent Manager , or Configuring the Agent Manager , for more information about configuring the Agent Manager to connect to the Management Server using HTTPS.
By default, Foglight™ ships with a self-signed SSL certificate. If you configure the Management Server to use an SSL certificate signed by a third-party Certificate Authority (CA), whose root certificate is already included in the JRE used by the Agent Manager, you do not need to add a new CA to the Agent Manager keystore. Instead, ensure that the Agent Manager connects to the Management Server using HTTPS.
You must add a new CA to the JRE used by the Agent Manager if:
1 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/jre/1.8.0.72/jre/bin directory. |
1 |
Launch a command shell on the Agent Manager machine, and navigate to the <fglam_home>/bin directory. |
a |
6 |
You can configure one or more Agent Manager instances to act as a concentrator in situations where:
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:
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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center