Installing the Endpoint Agent

IGEL enables deployment of a third-party tool such as eG enterprise via a feature called Custom partitions in the IGEL UMS console. Using this feature, a separate partition is created in each IGEL endpoint that is connected to the UMS server. To deploy the Endpoint Agent on each IGEL Endpoint managed by the IGEL UMS and where the eG manager is directly accessible to the IGEL Endpoints, follow the steps mentioned below:

1. In the IGEL UMS console, first, specify the name of the partition and the size of the partition as shown in Figure 1.

2. Then, in the Partition Parameters section (see Figure 1), specify the name of the IGEL Endpoints component, the host name/IP address of the eG manager on which the IGEL Endpoints component is managed, the port number and whether the eG Manager is SSL-enabled or not.

   

   Figure 1 : Specifying the Partition Parameters

3. Click the Apply and send to device button to save the partition parameters and send them to the IGEL Endpoint. The custom partition will now be automatically created on each IGEL Endpoint.

4. Once the custom partition is created, you need to upload the following files relevant to the Endpoint Agent to a location in the IGEL UMS. Note that this is applicable only for the IGEL Endpoints that are directly managed by the IGEL UMS.

   • eGvmagent_IGEL.bz2 - This file is the actual Endpoint agent file

     

     Figure 2 : Uploading the Endpoint agent file

   • eGagent_IGEL.inf - This file contains information relevant to the Endpoint Agent such as name of the Endpoint Agent, size of the Endpoint Agent etc.

     

     Figure 3 : Uploading the Endpoint Agent information file

5. After you successfully upload the files as shown in Figure 2 and Figure 3, you need to specify the exact URL using which the IGEL Endpoints should download the Endpoint Agent from the IGEL UMS console (see Figure 4). For this, you need to navigate through the System -> Firmware Customization -> Custom Partition -> Download menu sequence in the IGEL UMS console. Also, you need to specify the credentials of the user who is authorized to access the IGEL UMS.

   

   Figure 4 : Specifying the agent files for download by the IGEL Endpoints

6. If the IGEL Endpoints connect to the IGEL UMS through IGEL Cloud Gateway, then, you are allowed to upload the eGvmagent_IGEL.bz2 and eGagent_IGEL.inf files to a web server that can be accessed by the IGEL Endpoints. For this, specify the exact location of the uploaded eGagent_IGEL.inf file in the web server in the URL text box. Specify the credentials of the user who is authorized to access the web server.

7. Now, in order to collect metrics from the Endpoint Agent without interruption, you need to execute the igel_vmagent.sh script by issuing the following command to automatically start the Endpoint Agent. The Endpoint Agent will be started soon automatically after that agent is downloaded by the IGEL Endpoint and whenever the IGEL Endpoint is rebooted.

   /bin/sh /custom/egvmagent/igel_vmagent.sh

   This command should be specified in the Final network command list box (see Figure 5) that appears when you navigate through the menu sequence: System -> Firmware Customization -> Custom Partition -> Custom Commands -> Network in the IGEL UMS console.

   

   Figure 5 : Specifying the command to execute the script file

8. Once the Endpoint Agents are started, the IGEL Endpoints component managed by eG Enterprise will start reporting metrics relevant to the IGEL Endpoints that are included for monitoring by the target component.

Alternately, if the users from a remote location access IGEL Endpoints registered on IGEL UMS via IGEL Cloud Gateway i.e., if the Endpoint Agent could not connect to the eG manager directly, then, follow the steps mentioned below to deploy the Endpoint Agent:

1. In the IGEL UMS console, first, specify the name of the partition and the size of the partition as shown in Figure 1.

2. Then, in the Partition Parameters section (see Figure 6), specify the name of the IGEL Endpoints component, the IP address of the remote agent to which the Endpoint Agent should communicate to and the port number of the remote agent.

   

   Figure 6 : Specifying the Partition Parameters when eG manager is inaccessible

3. Click the Apply and send to device button to save the partition parameters and send them to the IGEL Endpoint. The custom partition will now be automatically created on each IGEL Endpoint.

4. As soon as the Custom partition is created, the Endpoint Agents will be deployed and the IGEL Endpoints component managed by eG Enterprise will start reporting metrics relevant to the IGEL Endpoints that are included for monitoring by the target component.