AppliancesExabeam Appliance Setup Guide

Table of Contents

Exabeam Appliance Network Configuration

Set up the network configuration to install the OS and Exabeam software.

In order to install the operating system and Exabeam software on your appliance, it must have its network presence established. Before configuring the network interface of your host, determine the address assignment of your host and network details, including:

  • IP address

  • Subnet

  • Network gateway

  • DNS addresses

  • Use of DHCP or on-board address assignment

Warning

Exabeam does not support IPv6.

To configure the network interface of your host:

  1. Log in to the console with the username exabeam. The unique password for your appliance is found on a label at the back of the unit.

  2. Initiate a screen session. This will prevent accidental termination of your session.

    screen -LS [yourname]_[todaysdate]
  3. Start the program to configure the network settings by entering the following command on the command prompt:

    sudo nmtui

    Use the down, up, and tab keys to move through the program

  4. Select Edit a connection, and then press Enter:

    Network1.png
  5. Select eno1, and then Edit.

    Network2.png
  6. You can a) obtain a static leased DCHP address or b) set the IP address at the host.

    Note

    You must configure a static lease at your DHCP server if you are serving addresses from DCHP. Otherwise, edit records in the nmtui UI.

    1. For a DCHP address assignment:

      1. Open the menu next to IPv4 and select Automatic.

        INF-DHCP-nmtui-1.jpg
      2. Ensure IPv6 is configured as Ignore.

    2. For persistent address assignment at the host:

      1. Open the menu next to IPv4 and select Manual.

        Network3.jpg
      2. Choose to <Show> the IPv4 details:

        Network4.jpg
      3. Enter the IPv4 Addresses and Gateway.

        Caution

        When entering the IP address, the address must be specified in CIDR notation. For example, if the IP address is 10.10.10.10 with a netmask of 255.255.255.0, the IP address must be specified as 10.10.10.10/24. Failure to do this will result in an incorrect subnet mask being assigned.

        Network5.jpg
  7. Select OK, and then press Enter.

    INF-DHCP-nmtui-2.jpg
  8. Select Quit, and then press Enter.

    PLT-Physical-Appliance-Network-Config-6.png
  9. Restart the network by entering the following command on the command prompt:

    sudo systemctl restart network

Note

NOTE: Once the setup is complete, use the username exabeam. (Please contact Exabeam Technical Support for the password.)

Appliance Network Teaming Configuration

NIC teaming consists of aggregating network interfaces on a server. In this scenario, two interfaces share one published static IP address in your network. Traffic is routed to the shared IP and onto the network device that is active or answering. NIC teaming can be used to increase the network bandwidth available in a network and provide redundancy to support higher availability. The attributes shown are the Exabeam supported configurations.

Apply the steps based on the environment your hosts operate with:

  • DHCP (with static IP lease), or

  • Static IP

DHCP Teaming Configuration

Set up a named session to connect to the host and establish administrator credentials. This allows the process to continue in the event you lose connection to the host.

screen -LS [session_name]
sudo su -

Go to the network configuration directory.

cd /etc/sysconfig/network-scripts/

Backup existing network interface configuration files, for example, to /home/exabeam/. (Do not place backups into /etc/sysconfig/network-scripts.)

cp ifcfg-eno* /home/exabeam/

Create and bind network interfaces. In this example, the host interfaces eno1 and eno2 are aggregated to make team0 for the runner state activebackup.

nmcli connection add type team con-name team0 ifname team0 config '{"runner": {"name": "activebackup"}}'
nmcli connection add type team-slave con-name team0-slave1 ifname eno1 master team0 
nmcli connection add type team-slave con-name team0-slave2 ifname eno2 master team0 

Restart your interfaces. At this point, you may experience 5-10 seconds of unresponsive SSH.

ifdown team0;ifup team0 
ifdown eno2;ifup eno2 
systemctl restart network 

Verify that the new state activebackup is configured.

teamdctl team0 state 

The status should return that one of interface links is up and the runner's active port is routing to the interface that is up. The response should resemble:

runner:

active port: eno1 

Optionally, verify that your throughput for one interface is up.

teamnl team0 ports 

The response should resemble:

eno2: down 0Mbit HD 
eno1: up 1000Mbit FD 

Static IP Teaming Configuration

Set up a named session to connect to the host and establish administrator credentials. This allows the process to continue in the event you lose connection to the host.

screen -LS [session_name]
sudo su -

Go to the network configuration directory.

cd /etc/sysconfig/network-scripts/

Backup existing network interface pointers to, for example, /home/exabeam/. (Do not place backups into /etc/sysconfig/network-scripts.)

cp ifcfg-eno* /home/exabeam/

Create and bind network interfaces. In this example, the host interfaces eno1 and eno2 are aggregated to make team0 for the runner state activebackup.

nmcli connection add type team con-name team0 ifname team0 config '{"runner": {"name": "activebackup”}}' [hostname] [host_ip/CIDR] [gateway_name] [gateway_ip]
nmcli connection add type team-slave con-name team0-slave1 ifname eno1 master team0
nmcli connection add type team-slave con-name team0-slave2 ifname eno2 master team0

Restart your interfaces. At this point, you may experience 5-10 seconds of unresponsive SSH.

ifdown team0;ifup team0
ifdown eno2;ifup eno2
systemctl restart network 

Verify that the new state activebackup is configured.

teamdctl team0 state

The status should return that one of interface links is up and the runner's active port is routing to the interface that is up. The response should resemble:

runner:
  active port: eno1

You can also verify that your throughput for one interface is up.

teamnl team0 ports

The response should resemble:

eno2: down 0Mbit HD 
eno1: up 1000Mbit FD