Enterprise Recon 2.0.28

Linux Agent

Install the Node Agent

  1. On your Web Console, go to DOWNLOADS > NODE AGENT DOWNLOADS.
  2. On the Node Agent Downloads page, click on the Filename for your Platform.

Select an Agent Installer

Select an Agent installer based on the Linux distribution of the host you are installing the Agent on. The following is a table of installation packages available at DOWNLOADS > NODE AGENT DOWNLOADS:

Host Operating System Linux Kernel Version Debian-based Linux Distributions RPM-based Linux Distributions
32-bit 2.4.x er2-2.0.xx-linux24-x32.deb er2-2.0.xx-linux24-x32.rpm
32-bit 2.6.x er2-2.0.xx-linux26-x32.deb er2-2.0.xx-linux26-x32.rpm
64-bit 2.6.x er2-2.0.xx-linux26-x64.deb er2-2.0.xx-linux26-rh-x64.rpm
64-bit 3.x er2-2.0.xx-linux3-x64.deb -
  • Examples of Debian-based distributions are Debian, Ubuntu, and their derivatives.
  • Examples of RPM-based distributions are CentOS, Fedora, openSUSE, Red Hat and its derivatives.

Debian-based Linux Distributions

To install the Node Agent on Debian or similar Linux distributions:

# Install Linux Agent, where 'er2_2.0.x-linux26-x64.deb' is the location of the deb package on your computer. dpkg -i er2_2.0.x-linux26-x64.deb

RPM-based Linux Distributions

To install the Node Agent on a RPM-based or similar Linux distributions:

# Remove existing ER2 packages rpm -e er2
# Install Linux Agent, where 'er2-2.0.x-linux26-rh-x64.rpm' is the location of the rpm package on your computer. rpm -ivh er2-2.0.x-linux26-rh-x64.rpm

Install GPG Key for RPM Package Verification

From ER 2.0.19, Node Agent RPM packages are signed with a Ground Labs GPG key.

For instructions on how to import GPG keys, see GPG Keys (RPM Packages).

Configure the Node Agent

After you have installed the Node Agent, configure the Node Agent to:

  1. Point to the Master Server.
  2. (Optional) Use the Master Public Key (see Server Information) when connecting to the Master Server.
  3. (Optional) Specify Target initial group.
  4. Test the connection settings.

To configure the Node Agent, choose either mode:

  • Interactive Mode
  • Manual Mode

For the changes to take effect, you must Restart the Node Agent.

Interactive Mode

Running this command helps you to quickly configure the Node Agent:

er2-config -interactive

The interactive mode asks you for the following information to help you configure the Node Agent.

Interactive Mode Command Prompts Description
Master server host name or IP Address [10.1.100.0] Specify a Master Server’s host name or IP address.
(Optional) Master server public key Enter the Master Public Key. See Install Node Agents.
(Optional) Target initial group Specify Target initial group.
Test connection settings (Y/n) Test the Node Agent’s connection settings to the Master Server, enter Y.

For the changes to take effect, you must Restart the Node Agent.

Manual Mode

To configure the Node Agent without interactive mode, run:

## Required for connecting to the Master Server # -i <hostname|ip_address>: Master Server IP address or host name. ## Optional parameters # -t: Tests if the Node Agent can connect to the given host name or IP address. # -k <master_public_key>: Sets the Master Public Key. # -g <target_group>: Sets the default Target Group for scan locations added for this Agent.
er2-config -i <hostname|ip_address> [-t] [-k <master_public_key>] [-g <target_group>]

For the changes to take effect, you must Restart the Node Agent.

Use Custom configuration File

To run the Node Agent using a custom configuration file:

  1. Generate a custom configuration file:

    # Where 'custom.cfg' is the location of the custom configuration file. # Run the interactive configuration tool. er2-config -c custom.cfg -interactive
    # (Optional) Manual configuration. er2-config -i <hostname|ip_address> [-t] [-k <master_server_key>] [-g <target_group>]
    ## Required # -i : MASTER SERVER ip or host name. ## Optional parameters # -t : Tests if NODE AGENT can connect to the given host name or ip address. # -k <master server key> : Sets the Master Public Key. # -g <target group> : Sets the default TARGET GROUP for scan locations added for this AGENT.

  2. Change the file owner and permissions for the custom configuration file:

    chown erecon:root custom.cfg chmod 644 custom.cfg

  3. Restart the Node Agent.
  4. Start the Node Agent with the custom configuration flag -c.

    er2-agent -c custom.cfg -start

To check which configuration file the Node Agent is using:

ps aux | grep er2
# Displays output similar to the following, where 'custom.cfg' is the configuration file used by the 'er2-agent' process: # erecon 2537 0.0 2.3 32300 5648 ? Ss 14:34 0:00 er2-agent -c custom.cfg -start

Install RPM in Custom Location

To install the Node Agent RPM package in a custom location:

  1. Download the Node Agent from the Master Server. The Master Server must be version 2.0.21 and above.
  2. Install the package in a custom location.

    ## Install the Node Agent package into the '/opt/er2' directory. # Syntax: 'rpm --prefix=<custom_location> -ivh <NODE_AGENT_rpm_package>'
    rpm --prefix=/opt/er2 -ivh er2-2.0.21-xxxxxxx-x64.rpm

  3. Configure the package: ## Configure the Node Agent package. # Run 'er2-config' binary from the custom install location, i.e. '<custom_location>/usr/sbin/er2-config' # Specify the location of the configuration file. The location of the configuration file is '<custom_location>/var/lib/er2/agent.cfg'
    /opt/er2/usr/sbin/er2-config -c /opt/er2/var/lib/er2/agent.cfg -interactive
  4. Restart the Node Agent.

Upgrade Node Agents

See Agent Upgrade for more information.

Restart the Node Agent

For your configuration settings to take effect, you must restart the Node Agent:

## Run either of these options # Option 1 /etc/init.d/er2-agent restart
# Option 2 er2-agent -stop # stops the agent er2-agent -start # starts the agent