Diagnostics and Troubleshooting
Ping, traceroute and speedtest from the connector interface, log download, restart, and how to read the connector status in the Console.
When a connector does not behave the way you expect, you have two places to look. The Diagnostics page on the connector itself tells you what the device sees, its page in the Console tells you what Sefthy sees.
The tools on the connector
Open the connector web interface and go to Diagnostics, in the left menu under STRUMENTI.
In the Tool field you pick one of three tests.
- Ping towards an address you expect to be reachable, to work out whether the problem is the site network.
- Traceroute to see where the traffic stops.
- Connector Speedtest, which measures the bandwidth of the Cloud Extension, that is the bandwidth you would really have during a Disaster Recovery. While it runs, the connector CPU load chart shows up as well.
Type the Target (valid IP or hostname only) and click Run Test. The outcome appears below, under Results.
Logs, restart and shutdown
At the bottom of the same page, in the Quick Commands section, you get three actions.
- Download Logs builds the system log archive, the one to attach to a ticket.
- Restart asks for confirmation and then waits until the device is back.
- Shutdown asks for confirmation and powers the device off.
The status in the Console
Open Connectors from the menu and pick the connector.
Anteprima video temporaneamente non disponibile.
Apri il file direttamente →The header carries two panels. Connector Status reads Bridged when the link towards the cloud is up and Not bridged when it is not. Next to it, Emergency VPN shows whether the VPN is Not active, Online or Offline.
If the connector goes quiet for more than 12 hours you get the “Offline connector for more than 12 hours” alert, and a second alert when it comes back.