Configuring the eG Agent on Unix

After installing the eG agent and before beginning agent configuration, make sure that the <EG_AGENT_INSTALL_DIR> is added to the Anti-virus exclusion list. If not, then sometimes, the CPU usage on the agent host may increase.

If you have installed the eG agent by downloading the tar file and installation script from the eG web site and then manually running the installation script on the target host, then, post successful installation, you will have to run setup separately on the agent host to configure manager-agent communication. To do this, it is essential to login as the eG user. The licensing terms for eG Enterprise are mentioned in the file /opt/egurkha/license_agreement. It is mandatory that you read this before proceeding any further.

The steps involved in configuring the eG agent are the same for all Unix systems, and are listed below:

1. For configuring, type the following command at the command prompt.

   /opt/egurkha/bin/setup_agent

2. The following message will be displayed and the process seeks the user’s confirmation.

   The licensing terms for eG products are mentioned in the file           

   /opt/egurkha/license_agreement. PLEASE READ THIS FILE BEFORE      

   PROCEEDING FURTHER.    

   Please indicate if you accept the eG licensing terms y/n [n]:

3. After the configuration process verifies that the licensing terms are acceptable to the user, it attempts to configure the agent’s operational environment with the details of the eG manager that the agent should communicate with. For this purpose, the configuration process prompts the user for the hostname (or IP address) and the port number of the eG manager. The hostname should be used if DNS is enabled in the target environment. Otherwise, the IP address should be used.

   Setup of manager/agent communication path

   Enter the hostname (or IP address) of the eG Manager:

   Enter the port number of the eG Manager [7077]:

4. The configuration process then requires to know if the user needs an HTTP proxy for the eG manager - agent communication. If yes, the user has to provide the name of the proxy server followed by the port number of the proxy server. If further authentication is required, the user name and the corresponding password have to be provided.

   Please indicate if you want to use a proxy for the eG Agent to communicate with the eG Manager? y/n [n] :

    

   Note:

   • If the eG agent is configured to communicate with the eG manager via a proxy server, then, whenever the eG agent attempts to remotely monitor an application by connecting to it via HTTP/HTTPS, it may automatically use the proxy server to establish this connection; this in tun may cause problems while monitoring those applications. To avoid this, before configuring the eG agent-manager communication via a proxy, make sure that the agent will be able to connect to remote applications also via the same proxy.

5. Then, indicate whether you want to enable SSL for the eG agent.

   The eG Agent can use HTTP or HTTP/SSL to communicate with the eG Manager. In order to use HTTP/SSL, please make sure that the eG Manager has been configured to support SSL.
   Do you want to configure the eG Agent to use SSL for communication with the eG Manager? y/n [n] :

   Entering y here will enable SSL support for the agent, and n will disable it.

6. If SSL support is enabled, then setup will request your confirmation to allow trusted certificates alone.

   Do you want to allow trusted certificates only? y/n [n]:

    

   Note:

   Ensure that the manager IP/hostname provided when setting up the agent matches the IP/hostname provided when generating the certificate on the manager.

   Enter y if the agent is expected to communicate only with a manager that has a trusted SSL certificate. If you enter n, the agent accepts any certificate provided by the manager at the time when the SSL connection is established. If you have chosen to allow trusted certificates alone, then, you need to indicate the trust relationship to the agent. Towards this end, follow the instructions detailed in the Enabling the eG Agent to Allow Trusted Certificates topic once agent installation completes.

   Note:

   While configuring an eG agent on AIX, setup will not prompt you to confirm whether you want the eG agent to allow trusted certificates alone.

7. The setup will now request you to indicate whether you wish to assign nick name(s) for the eG agent’s host. Instead of remembering the IP address/ host name of a host, users can assign one or more nick names to the host and manage all applications on the host using the same.

   Please indicate if you want to assign a nick name(s) for this host? y/n [n] :

   To assign nick names, press y. Setup will then request you to specify the nick name(s) to be assigned to the host.

   Please enter the nick name(s) to be used for this host:

   While providing multiple nick names, ensure that they are separated by a ‘:’. Also, ensure that a nick name does not contain any white spaces, and that all nick names are in lower case.

8. Upon successful termination of the agent setup process, the following message is displayed:

   The eG Agent has been configured successfully.

   Please use the commands /opt/egurkha/bin/start_agent and

   /opt/egurkha/bin/stop_agent to start and stop the agent.

   To provide feedback and report errors, please contact support@eginnovations.com