In some cases, Test Agent (TA) is registered towards the Netrounds Control Center(NCC), it appears in the system but is shown as offline.

When registration of a TA in NCC is successful, it will show the TA as online in the Test Agent tab in the UI. The system status on TA CLI should display connection status as "Logged IN".
But, if the TA appears as offline post-registration, then in TA CLI, you will see connection status as " connecting ".

Potential causes:

1. The NTP is not synced between the Test Agent and Control Center
   When the Test Agent is establishing the management tunnel it will first send a registration request containing the Test Agent ID to the Control Center on the management port (default: 6000). Once received by the Server, it will proceed to create VPN certificates containing the Test Agent ID previously communicated before initializing the OpenVPN services and establishing the VPN tunnel using those certificates.
   In the first step, when generating the certificates, the Test Agent will show up in the control center as registered. However, these certificates are also time-stamped, which naturally means that they will be invalid until the Test Agent clock reaches the time of the validity TS.

2. DPI is blocking VPN connections
   If there’s a Deep Packet Inspector between the Test Agent and the Server, this could detect and prevent any VPN tunnel from being established. This will happen after the initial handshake has taken place and the certificates have been generated. This again means that the Test Agent will appear in Netrounds, but will appear as offline.

3. The correct port hasn’t been configured for the login server on the Test Agent
   If one tries to register a Test Agent on another port than the one configured (default: 6000) – assuming connections on that port is not blocked in the firewall, the Test Agent will again appear in the Control Center as registered, but offline. The main differentiator here in comparison to the other problem descriptions is that the interfaces will be missing from the Test Agent when navigating into it using the Control Center UI.

The following workaround or checks will help you get your TA successfully registered in NCC:

1. The NTP is not synced between the Test Agent and Control Center:
   Solution:
   Reconfigure the NTP servers on both the Test Agent and Control Center so that they’re synced in time (ntpq -np). Proceed by removing the certificates on the server (rm /var/lib/openvpn/*) and generate new ones (dpkg-reconfigure netrounds-probe-login). Once these steps are completed a re-registration can be attempted. 

2. DPI is blocking VPN connections
   Solution:
   Allow VPN connections on the management port specified. 

3. The correct port hasn’t been configured for the login server on the Test Agent
   Solution:
   On the Test Agent, navigate into Utilities > Change Login Server and configure the correct port. *(Default 6000)