Agent Configuration - Interface Management

Introduction

By default, a NetBeez Agent comes configured with DHCP enabled. Once an Agent is plugged into the network, has obtained a DHCP address, and reports back to the central server, you can assign a static IP address. It is recommended that permanent monitoring Agents are configured with a static IP address in order to increase resiliency in case of issues with the network and/or DHCP servers.
 
Warning: Before changing the IP settings on an Agent, it is recommended that you pause all the tests running on that Agent. Once the reconfiguration of the IP settings has been successfully completed, all the paused tests can be resumed. 
 
Note:  Interface Management settings are not available for Docker container Agents. 
 

Set a Static IP Address via the Dashboard

Procedure

To open the Interface Management panel, access the Agent Details panel and then open the Agent Settings menu by clicking the cog icon.
 
screencapture-localhost-2020-07-21-13_12_27-edit.png
 

Update the IP settings on the eth0 interface (Wired, WiFi, Virtual Beez)

  1. Click the eth0 tab.
  2. To enable or disable DHCP select the ON/OFF toggle.
  3. If DHCP is set to OFF, configure the required fields (unless otherwise specified):
    1. IP Address
    2. Subnet Mask
    3. DNS Server 1
    4. DNS Server 2 (optional)
    5. Gateway
  4. Click on Save Settings when completed *.

* Changing the IP settings of an Agent will cause a temporary loss of connectivity between the server and the Agent.

Update the IP settings on the wlan0 interface (WiFi Beez)

  1. click the wlan0 tab.
  2. To enable or disable DHCP select the ON/OFF toggle.
    Note: If the Agent is assigned to a Hopping Group, DHCP will be set to ON automatically.
  3. If DHCP is set to OFF, configure the required fields (unless otherwise specified):
    1. IP Address
    2. Subnet Mask
    3. DNS Server 1
    4. DNS Server 2 (optional)
    5. Gateway
  4. You can assign the Agent to a different WiFi network.  For information on configuring and managing WiFi networks, please see: Add/Edit WiFi Network.
  5. Specify the band, frequency, and BSSID.
    Note: If the Agent is assigned to a Hopping Group, band, frequency, and BSSID are not configurable.
  6. Click on Save Settings when completed *.
* Changing the IP settings of an Agent will cause a temporary loss of connectivity between the server and the Agent.
 

Override the IP address (Cloud Beez)

There is the option to override the IP address of an interface that a cloud agent reports to the dashboard. This override is done by editing the NetBeez configuration file. This option is used if you want to run scheduled tests (e.g. VoIP and iPerf) against external agents running on a public cloud. Please make sure to use the real public IP address of the agent.

  1. Edit the configuration file /etc/netbeez/netbeez-agent.conf (earlier versions may use the /usr/local/netbeez/nbagent_info_prod.txt file)
  2. Add the following string “eth0”:”<REPLACE_WITH_PUBLIC_IP>” to the content of the before the closing "}". It should look something like this: {"host":"some_server_FQDN_or IP","port":"20019","secure_port":"20018","eth0":"2.3.4.5"}
  3. Restart the cloud agent via command line or dashboard.

Override the control and test interfaces

If there is more than one interface on a host, the agent might try to use one as a control interface (for connecting to the server) and another as a test interface (the interface it uses to run the tests). For example, on a host with a wired interface "eth0" and wireless interface "wlan0" will try to use "eth0" as control interface and "wlan0" as test interface.

If there are multiple interfaces on a host (e.g. tunnels, multiple hardware interfaces, etc) the agent might not be able to use the desired control and test interface.

To set a specific control and test interface, you must modify the agent config file (whichever is present):

/usr/local/netbeez/nbagent_info_prod.txt

or

/etc/netbeez/netbeez-agent.conf

The two options you can set are:

"control_interface" and "test_interface."

Keep in mind you must set both control and test interfaces. If you only set one, it will be ignored. You can set them to the same interface if that's desirable.

It should look something like this:

{ "control_interface": "wlan0", "test_interface": "eth0", "agent_uuid":"", "host":"", "port":"", ... }

 

 Note: There is also a similar "interfaces" option which defines which interfaces are available.

"interfaces": ["eth0", "wlan0"]

In this case, the agent will try to decide which one it should use as control and which one as a test interface.

The agent will first look for the "control_interface" and "test_interface" options and then look for the  "interfaces" option.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.