Show system status/Show interface status
To inspect the current status of the Test Agent and its interfaces, navigate to Show system status and Show interface status respectively in the text-based menu.
On the System status screen the Test Agent (Probe) ID is shown. This ID is the unique identifier of a Test Agent, which simplifies correlation with the Test Agents you see in the GUI (the URL of the above Test Agent is https://app.netrounds.com/<your_account>/genalyzer/55/).
Connection status can have the following values: not registered, connecting, or logged in.
- Not registered: The Test Agent is not registered to the Netrounds account.
- Connecting: The Test Agent is trying to connect to the Netrounds server.
- Logged in: The Test Agent is connected and logged in to the Netrounds server.
Test status is one of the following: free, updating, or in use.
- Free: The Test Agent is idle.
- Updating: The Test Agent is downloading and installing the latest firmware. Note: Do NOT power off the Test Agent during updates.
- In use: The Test Agent is performing tests or monitoring.
The Interface status screen shows the status of all available interfaces of the Test Agent. In the example shown, "eth0" is the management interface with link and IP address, while "eth1" has no IP.
Configuring the management interface on a Test Agent
For configuration of Test Agent management over a mobile network interface, see this page.
- In the text-based menu, navigate to Configure management.
- Select which interface should handle management traffic to and from the server (preferably, "eth0").
Configuration of the other interfaces is done via the Netrounds server; see Test Agent interface configuration.
- Then select interface speed and duplex on the management port.
- You are also asked whether to use a VLAN tag for the management interface. Choose Yes or No. If you choose Yes, enter the VLAN ID, for example "100" as in the screenshot.
- Next, select address type: DHCP or static.
- The NTP server setting follows. You can use either the default NTP server, ntp.netrounds.com, or a local one (specified as an IP address or host name).
- If you selected "DHCP" as address type, no more configuration is needed. Just verify the setup: for example, Interface = "eth0.100" meaning VLAN ID 100 on the "eth0" Ethernet interface.
- If you selected "static" as address type, you need to configure IP, Network mask, Gateway, and DNS in the format shown in the screenshot. The NTP server setting follows; it defaults to ntp.netrounds.com.
- Finally, confirm the settings for the management port.
- To check the configuration, navigate to Show interface status.
Example 1: "eth0" configured as management interface with no VLAN tag and address type = DHCP.
Example 2: "eth0" configured as management interface with no VLAN tag and address type = static.
Example 3: "eth0" configured as management interface with VLAN tag and address type = DHCP.
Using Test Agent utilities
To access the Test Agent utilities, navigate to Utilities in the text-based menu. The utilities are: Reboot, Shutdown, Change login server, Ping, Traceroute, and Troubleshoot management connection.
Changing login server
Note: The Test Agent must be registered in order for this function to be applicable.
- To use Netrounds' proprietary proxy function or a standard HTTP (web) proxy, navigate to Change login server. The concept of Test Agent proxy is described here.
- To be able to use the Test Agent proxy function, you need to change the login server here to point to the static IP address of the proxy Test Agent.
- Choose No if you are not using a standard HTTP proxy.
- Check that the settings are correct, then choose Yes.
- To use an HTTP proxy, answer Yes to the question "Do you want to use an HTTP proxy?" above, and proceed to fill in the proxy address.
- For HTTP proxy authentication, the options are "none" and "basic". Make the appropriate selection.
- Fill in the requested credentials.
- Select interface and enter the host to ping.
The outcome is displayed as follows.
- Select interface and enter the host to traceroute.
This function tests the management connection to verify that it is working.
The outcome is a pass/fail test result. An example of each is shown in the screenshots below.