How do I troubleshoot devices that cannot be accessed by Datto Technical Support, have stopped checking in, or refuse all connections?
- Datto SIRIS
- Datto ALTO
- Datto NAS
This article discusses troubleshooting in cases where a Datto device does not check in to Datto's monitoring servers, prohibiting Datto technicians from accessing the device.
- Browse to the local IP address assigned to the Datto to see if the Web UI is accessible.
- If you can access the Web UI, log in with the admin account created during registration, then navigate to Configure > Networking to check that the network settings are correct. Also, make sure that at least one Public DNS is present.
- Verify that the ports intended for communication on your network (eth0, eth1, eth2, etc) are not disabled.
- Ping the device on the local network. If it does not respond, make sure it has a gigabit connection from the switch to the LAN.
- Reboot the Datto appliance.
Direct Connection to the Device
You can attempt to connect via IPMI on SIRIS 2 and SIRIS 3 devices. See the following articles for more information:
If connection still fails, connect a keyboard, monitor, and mouse connected to the Datto device. Open a Terminal session by pressing CTRL+ALT+F2. Once logged in, enter the command:
You will be prompted for a password, which is located in the Partner Portal on the Device Status page. you can click on the device name and access the device spec page that will contain the backup-admin password.
- Once logged in as backup-admin, enter the command
- The screen should look similar to the example below:
checkin, and allow it some time to follow through. If the checkin command returns errors, note the error message.
- Run the following command to see if another device on your network is using the same IP address of the Datto appliance.
arping -I eth0 -D (IP address of the Datto appliance)
Check the Switch
If your Datto appliance is does not comple the registration process, or fails to check in, make sure the port on the switch to which it is connected and the Datto appliance's primary NIC are set to negotiate the appropriate speeds:
On the client's switch:
- Log into the switch, and make sure that the Datto appliance's dedicated port is set to a specific speed (ie 1000 mbps).
On the Datto appliance:
- Connect a keyboard, monitor, and mouse to the Datto device. Press CTRL + ALT + F1 to access the Command Line Interface (CLI).
- Log in using the device's backup-admin username and password (if registered), and run the following commands:
sudo -i ethtool -s eth0 speed 1000 duplex full ethtool -s eth0 autoneg off reboot NOW
- Attempt to register or check the device in again.
1. If the error involves general connectivity issues, type
ifconfig to verify that both the primary NIC and
lo are present. If either one is missing, you can manually bring it up:
ifconfig eth0 up]
2. The MAC address of the primary NIC should be the same as the device serial number. If eth0 HWaddr(MAC) shows up differently then what is shown in the Partner Portal, contact Datto Technical Support.
3. If the primary NIC is up and has an IP address, it should look similar to:
4. If there is no address for the primary NIC, run the following command to bring up the interfaces file:
5. Use the arrow keys to navigate around the file. If the primary NIC is supposed to be on a DHCP instead of static, replace the word
dhcp. Make sure to also set the address to an IP outside of the DHCP scope.
If the device runs Ubuntu 12.04 (Siris Business, Siris Enterprise, Siris Professional, Alto2/AltoXL or DattoNAS), the DNS servers are listed under the gateway on a new line, as shown below:
6. When you finish configuring the file, press ctrl and x to exit the file, and then press Y to save and enter to write it to the file:
7. If you edited to this file, restart networking and apply the changes:
On devices running Ubuntu 16.04 and up:
service networking restart
On devices running Ubuntu 12.04 and below:
8. If you want to force a new DHCP address on the primary NIC, type:
9. To edit the DNS interfaces, configure the DNS file with:
10. If both interfaces are up and the primary NIC has an IP, verify the primary NIC has a connection:
11. If there is no link detected, check if the ethernet cable is plugged in to the wrong port. Switch the port to another onboard port and run
ethtool eth# again until you see a link detected. If a link is not detected on any port, try another cable.