Installing an eG Agent on an HP-UX Server Running an Itanium Processor

There are two approaches to installing an eG agent on HP-UX servers running an Itanium processor:

  • The eG agent software for HP-UX Itanium is available in the eG web site as a tar file and an iAgent script. you can download the tar file and iAgent script from the eG web site, and manually run the iAgent script on the target to install the eG agent. This approach is ideal if you want to deploy HP-UX agents for a single organization - i.e., for the Enterprise deployment of eG.
  • The eG agent software for HP-UX Itanium is provided as a packaged application. You can download the agent packagefrom the eG manager console, extract the contents of the package to any folder in the target host, and silently run a setup script on that host to install and configure the agent at one shot - i.e., to install the agent and also to configure agent-manager communication. If you are deploying eG Enterprise for SaaS, then it is mandatory that your tenants use this approach to install and configure the eG agents in their environment.

Both these approaches are discussed in this section.

Installing HP-UX Itanium Agents for an Enterprise Deployment of the eG Manager

An Enterprise deployment of the eG manager is typically used to monitor only a single organization's IT infrastructure. In this case, it is recommended that the following procedure be used to install eG agents on HP-UX hosts running an Itanium processor:

  1. The eG agent software for Hpux_Itanium is provided as a tar file named eGagent.tar. An accompanying script called iAgent drives the installation process for the agent. You can download the tar file and installation script from the HP-UX Itanium folder in the eG web site. To know how, refer to the eG Quick Installation Guide.
  2. To start the installation process, execute the iAgent script, with the eGagent.tar file located in the same directory as iAgent.

    Note:

    The agent installation must be performed from a super-user account.

  3. Next, specify the user account to be used for executing the eG agent. First enter the name of the eG user. The default value taken is “egurkha”.

    This script will install the eG agent. The eG agent must be installed and executed by a separate user. If you have installed the eG manager on the same system, you must use the same user and the same installation directory for the manager and the agent.
    Enter the name of the eG user [egurkha]:

    Note:

    If the agent is being installed on the same system as the manager, the eG user configured for the agent should be the same as that used for the manager.

  4. Then, enter the group to which the eG user is to be associated with. The default value taken is “egurkha”. The installation will attempt to create the user account if it does not exist on the system. If you specify an existing user name, then this group prompt will not appear.

    Enter the group to which the eG user is to be associated [egurkha]:

  5. The install process will now request the user to confirm installation of the auto-restart feature. This feature will enable the agent to start automatically every time the system hosting the agent reboots. Now, press y to install the auto-restart feature, or n to proceed without installing the same.

    Would you like the eG agent to auto-restart on system boot-up? y/n [n] :

  6. If the agent is installed on the same system as the manager some common files need not be reinstalled.
  7. As in the case of the eG manager, the agent package contains components that need to be installed with the set-uid permissions set. These components must be installed for the agent to function properly. Following this step, the eG agent components are extracted and stored.
  8. The eG agent will be installed in the default /opt base directory. Upon successful installation, the following message will be displayed.

    The eG agent has been successfully installed! Please login as <eG user name> and run the script /opt/egurkha/bin/setup_agent to configure the agent.

If you install an eG agent using the procedure discussed above, then you will have to run a setup procedure later to configure agent-manager communication. To know how setup the eG agent, refer to the Configuring the eG Agent on Unix topic.

Installing HP-UX Itanium Agents for a SaaS Deployment of the eG Manager

As stated earlier, where eG Enterprise needs to support multiple tenants - eg., MSP environments with multiple customers, enterprises with multiple departments/domains - the individual tenants should use only this approach to deploy the eG agent on the Linux hosts in their specific environments.

A key pre-requisite of this approach is that the eG manager should already be deployed and running.

To enable a tenant to install eG agents, the administrator should first make sure that the agent packages that correspond to the tenant's environment are accessible to the tenant from the eG manager console. For that, the administrator should do the following:

  1. Login to the system hosting the eG manager.
  2. From a browser, connect to the URL: https://www.eginnovations.com/eval712/AgentPackages
  3. In this location, you will find a set of zip files. Each zip file is an agent package that corresponds to every operating system on which an eG agent can be installed.
  4. Download the agent packages / zip files that correspond to the hosts in your tenant's environment, to any folder on the eG manager host. The HP-UX agent for Itanium package will be listed therein as HPUX_Itanium.zip.

  5. Copy the downloaded packages to the /opt/egurkha/agents/Universal/Latest folder on the eG manager.

The tenant can now proceed to install the eG agent using the procedure discussed hereunder:

  1. Using a browser, connect to the URL of the eG management console.
  2. Login to the eG management console using the credentials you used (corporate email ID and password) to register with eG Enterprise for SaaS.
  3. Click the icon in the top, right corner of the page that appears to download eG agents.
  4. Figure 1 will appear. By default, Figure 1 lists the 'internal agent packages' that have been uploaded to the eG manager - i.e., agent packages to be used for monitoring components in an agent-based manner. If you want to deploy a remote agent, click the agentless monitoring link in Figure 1. Likewise, to deploy an external agent, click the external monitoring link in the page.

    Figure 1 : eG's internal agent packages available for download from the eG manager console

    Note:

    Though the eG management console lists the packages meant for agent-less, agent-based, and external monitoring in separate pages, the procedure to download and install these packages remains the same across monitoring approaches.

  5. To download an agent package for HP-UX Itanium, click on the package named HP-UX Itaniumin Figure 1.
  6. If the host to which you have downloaded the package is the target HP-UX host for agent installation, then login to that HP-UX host as super-user. On the other hand, if you want to install the eG agent on a host different from the one on which the package has been downloaded, then first copy the agent package to any location on the target HP-UX host. Then, login to that host as a super-user.
  7. From the prompt, open the folder to which the zip file has been copied/downloaded. Then, run the following command at the prompt to unzip the file and extract its contents.

    unzip <Zip_File_Name>

  8. The following files will then be extracted:

    • A tar file: Upon unzipping HPUX_Itanium.zip, you will find a tar file named eGagent.tar.gz.
    • iAgent script: This is the script that installs the eG agent on an HP-UX host. An iAgent script will be extracted from HPUX_Itanium.zip .
    • setup.sh: This is the shell script that drives the silent installation of the eG agent. Running setup invokes the iAgent script and silently installs the agent on the target host.
    • eg_uaid: In a multi-tenant setup, once a tenant - eg., a user representing a customer / a department / a domain - registers with eG Enterprise to use its monitoring services, eG automatically generates a unique UAID and assigns the same to that tenant. If that tenant later logs into the eG management console using the registered credentials (email ID and password) and downloads the agents, each agent so downloaded is automatically tagged with that UAID. The downloaded agents, once installed and configured, will automatically start discovering applications on their respective hosts. eG Enterprise auto-manages the discovered applications and auto-assigns them to the user who has the same UAID as the eG agent that discovered these applications. The eg_uaid file contains the UAID of the tenant who downloaded agent packages from the eG management console; this is the same UAID that will be assigned to each agent installed by that tenant.
  9. Next, to install the eG agent on the HP-UX host silently, from the command prompt, switch to the folder to which the files have been extracted. Then, run the setup.sh script by issuing the following command:

    ./setup.sh

  10. Running setup will automatically install an eG agent on the target HP-UX host, and will also automatically configure agent-manager communication. This eG agent will automatically report metrics to the eG manager from which the agent package was downloaded. Also, the hostname of such an agent is automatically set as its nick name.

    In a multi-tenant setup, a hostname may not be unique across tenant environments. To avoid nick name duplication, eG Enterprise automatically employs the following algorithm when assigning nick names:

    • At the time of setting the hostname of an agent host as its nick name, eG first checks if that hostname has already been assigned to any existing agent.
    • If it finds that the hostname has already been taken, then it will attempt to assign the FQDN - the fully qualified domain name - of the agent host as the nick name.
    • In the process, if eG finds that the FQDN is also in use, then it will break-down the FQDN into smaller strings, and try to assign each of these strings, one after another, to the agent.
    • If all these FQDN strings have already been assigned to other agents, then the eG agent will suffix the hostname of the agent host with the number 0, and try to assign this as the nick name of the eG agent. For instance, if the hostname of the eG agent host is winpc, then the nick name assigned to that agent will be winpc0.
    • If this nick name is also taken, then eG will increment the number 0, which suffixes the hostname, by 1, and will try to assign the resultant string to the eG agent,. This way, eG will keep incrementing the number suffix until an unused string is found. Such a string will finally be assigned to the agent as its nick name.

      Note:

      • In a SaaS deployment, if a tenant manually adds components to be monitored by an eG agent, then you should only assign that agent's nick name to each of the components it monitors.
      • If you are installing the eG agent on an imaging system (e.g. for Citrix Provisioning services), or on a snapshot (for Citrix Machine Creation Services), or on a VM template for virtual servers, you will need to make sure that the nick name is NOT set for the agent on the imaging system/snapshot/VM template. In such environments, when installing the eG agent, make sure that you do not provide a nick name for that agent when prompted. If you are downloading the agent from the eG manager in a SaaS environment, the installation will automatically start the agent and assign the hostname of the system as the nick name automatically. In such a case, you need to:

        • On the snapshot / golden image / master VM, open the eg_nick.ini file in the <EG_AGENT_INSTALL_DIR>\agent\config directory.
        • Check to see if the Nick parameter in that file is set to any value. If this parameter has no value, it implies that no nick name was set for the eG agent on that snapshot / golden image / master VM. On the other hand, if the Nick parameter has a value, it indicates that a nick name was set for the eG agent. In this case, make sure that you delete the eg_nick.ini file on the snapshot / golden image / master VM before you proceed further.