Quick troubleshooting procedure
An agent may not be able to connect to the NetBeez server for various reasons, such as:
- The agent is not powered on
- Check the status lights on hardware agents
- The agent can't resolve the server's address (FQDN)
- Ping the server
- A network firewall is blocking the agent
- Telnet to the server port 20018
- The server doesn't have a valid license or maxed out
- Check the license in the NetBeez settings
- The agent is faulty
- Open an RMA case with NetBeez support
Detailed troubleshooting procedure
Step 1 - Agent is powered up and shows activity
This step applies to hardware sensors. If you are troubleshooting a software or virtual agent, verify that the host or virtual appliance is powered up.
If you are troubleshooting a FastEthernet and WiFi beez
These sensors are based on the Raspberry Pi platform. The Raspberry Pi has two LEDs:
Power Led - Solid, it signals that the unit is receiving power via power supply or PoE.
Green Led - Blinking based on SD card activity.
A unit where the red led is solid, but the green one doesn’t show any activity for 10 seconds or so may be faulty (SD card corruption). In this case, open an RMA to support [at] netbeez [dot] net.
If you are troubleshooting a GigE beez
Gigabit Ethernet sensors are based on the Intel Up-Board platform. The Up-Board has one blue LEDs that is visible from the top of the case. You can verify that the blue light is one, and eventually that there's network activity on the Ethernet interface:
A unit where the blue light is not visible, or the Ethernet doesn't show any activity, may be faulty. In this case, open an RMA to support [at] netbeez [dot] net.
Step 2 - Is the network configured to enable agent-server communication?
For an agent to successfully connect to the dashboard, the network must be configured to resolve the server's Fully Qualified Domain Name (FQDN) and allow the agent to establish a TCP connection to port 20018.
1- Verify that the agent is able to resolve the server's fully qualified domain name (FQDN):
2- Verify with telnet that no network firewalls are blocking agent's connection to the NetBeez server:
telnet <server_FQDN> 20018
Step 3 - Is the agent receiving a DHCP lease?
Verify that the DHCP server has offered an IP address to the agent’s MAC address. The agent's MAC address can be located on the case.
Step 4 - Check the NetBeez license file
Check your license file by clicking the NetBeez Settings gear icon in the upper right corner and then the License tab.
Check if you are licensed for the agent you trying to connect to your dashboard. For example, if you are licensed for three virtual agents and you already have three virtual agents connected, then any additional virtual agents trying to connect to your dashboard will be rejected.
If you would like to replace a virtual agent with a new one, you must delete an existing virtual agent and then spin up the new virtual agent. For instructions for deleting an agent, please see the following article:
Agent Configuration - Delete Agent
- If you are able to ssh or console to the agent, please send to support [at] netbeez [dot] net the last 100 lines of the agent log file with the following command:
tail -n 100 /var/log/netbeez/*agent*.log
- If a WiFi agent can't associate to a WiFi network, please read this article