Troubleshooting Checkin Errors

Follow

1. Scope

This article gives troubleshooting steps for devices that cannot be accessed by Datto Technical Support. It usually results when the device is not checking in or is refusing all connections.

Example: A Datto device was recently deployed, however the device is not checking in to Datto's monitoring servers. If the device can't check in, Datto technicians cannot access the device.

2. Troubleshooting Steps

This section describes the troubleshooting process.

This article uses eth0 as an example of a primary NIC. However, your primary NIC assignment might be different. If this is the case, substitute instances of eth0 in this article with the NIC assignment (such as eth1, eth2, eth3) you are using in your configuration.
SIRIS 3 devices require 10/100/1000 networking to check in successfully. See the Datto Networking Requirements article for more information.

2.1. Check the Switch

If your Datto appliance is having difficulty completing the registration process or failing to check in, make sure that the port on the switch it connects to and the Datto appliance's primary NIC are set to negotiate the appropriate speeds:

On your 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). After you set the port speed, configure it on the Datto device.

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 in the device again.

2.2. Check Communications

  1. Ping the device on the local network. If the device does not respond to ping, try a reboot.
  2. Browse to the local IP address assigned to the Datto to see if the Web UI is accessible.
  3. If the Web UI is accessible, log in with the admin account created during registration and go to the Configure > Networking page to verify that the network settings are correct. Also, make sure that at least one Public DNS is present.

2.3. Direct Connection to the Device

Using a tool like VNC Viewer, try to connect to the local IP of the Datto device. The default password is the first 8 characters of your backup-admin password.

You can also attempt a connection via IPMI on SIRIS 2 and SIRIS 3 devices. See the following articles for more information: 

Alternatively, if you have physical access to the Datto, connect a monitor, keyboard, and mouse.

      1. Once connected to the device, open a Terminal session. Once logged in, enter the command: su backup-admin.
      2. You will be prompted for a password. This password is located on the Partner Portal on the Device Status > Advanced tab.



        On the Status 2.0 page, you can find the backup-admin password by clicking on the appliance's name. The password is listed under the Device Info heading.


      3. Once logged in as backup-admin, enter the command sudo -i.
      4. Once there, the screen should look similar to the example below:



      5. From here, type checkin, and allow it some time to follow through. If the checkin command returns errors, please note the error message as it is helpful for troubleshooting.
      6. Run the following command to see if another device on your network is using the same IP address of the Datto appliance. If there is, you will need to resolve the IP address conflict:
        arping -I eth0 -D (IP address of the Datto appliance)

2.4. Configure NICs

  1. If the error mentions 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 with ifconfig <interface> up 
    [Example: ifconfig eth0 up]

  2. If the primary NIC is up and has an IP address, it should look similar to:



  3. If there is no address for the primary NIC, run the following command: 
    nano /etc/network/interfaces to bring up the interfaces file.



    If the file comes up completely blank, the command may have been typed wrong.
  4. 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 static with dhcp. Make sure to also set the address to an IP outside of the DHCP scope.

  5. 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 to exit the file, and then press to save and enter to write it to the file:

  7. If any changes are made to this file, run the following to restart networking and apply the changes: /etc/init.d/networking restart

  8. If you want to force a new DHCP address on the primary NIC, type:
    dhclient <name of the primary NIC, such as eth0>

  9. To edit the DNS interfaces, you would configure the DNS file with:
    nano /etc/resolv.conf
    NOTE: This will only be done on a device manufactured before 2/1/2014, they were on Ubuntu 10.04.



  10. If both interfaces are up and the primary NIC has an IP, type ethtool <name of the primary NIC, such as eth0> to verify that 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 <name of the primary NIC, such as eth0> again until you see a link detected. If a link is not detected on any ports, try another cable.

2.4. Re-Order the NICs

  1. If there is still no link detected on any port with another cable, you may have to run a NIC reorder to reconfigure the NICs. To run the NIC reorder, be sure to unplug all Ethernet cables, then run the following command:
    php /datto/scripts/reorder.php

    Example: php /datto/scripts/reorder.php

  2. You should see a prompt requesting that the first NIC be identified. ​​The terminal prompt will automatically refresh once it detects that the NIC has been plugged in. It will then ask you to plug in the next NIC. Repeat until you see the message that the NICs have been reordered. The prompt should return you to the root user upon completion.

  3. Connect a live ethernet cable into the primary NIC. Type in dhclient eth0 to get a DHCP address from the network to allow the device to check in with Datto monitoring servers.


    Example: NICs have been reordered
In the event that the Datto NIC Re-ordering Script locates a link on Jack 1 and Jack 2 at the same time, try these steps from the beginning. Typically on the second attempt, this will not see multiple jacks linked at the same time.

2.5. Confirm the Datto NIC Re-ordering Script Was Successful

The following commands can be used once the Datto NIC Re-ordering Script has been performed:

ifconfig

From the terminal prompt check the inet addr (IP) & Mask (Subnet Mask) that are displayed after entering this command.


Example: Output of an ifconfig command run from the terminal prompt

From the terminal prompt check to see if a ping response is received when pinging dattobackup.com by entering this command: ping dattobackup.com

Tip: Unlike the ping command in Windows, the linux command will run until you press CTRL+C.

 
Example: ping requests to dattobackup.com successfully responded

Note that a networking restart ( /etc/init.d/networking restart ) or reboot of the Datto device may be required to apply the changes from the reorder.

If a link is detected, and you verified that the network settings are correct and have been restarted, type checkin again.


Was this article helpful?

5 out of 5 found this helpful

You must sign in before voting on this article.

Want to talk about it? Head on over to our Community Forum!