Troubleshooting Device Registration

You are here:

Troubleshooting Device Registration

Check the A10 Control Compatibility Matrix before registering the Thunder devices to A10 Control. Some of the commonly faced challenges in registering the devices are listed here.

Modifying the Registered A10 Control Profile

Enter the configuration mode:
```
ACOS(config)#configure
```
Enter the following command to remove the old configuration. The following example shows modifying the username configuration:
```
ACOS(config)#no user-name organization-admin
```
Enter the following command to set new username:
```
ACOS(config-profile)#user-name new-username
```
Enter the following command to deregister the device with old configuration:
```
ACOS(config-profile)#deregister
```
Enter the following command to register the new configuration:
```
ACOS(config-profile)#register
```

Registration Issues

Check the following before contacting Technical Support.

The device is connected to the Internet and can reachA10 Control deployment.
In a VCS setup, primary disk and secondary disk images are of the same version.
A10 Control has valid A10 Control MBU licenses to register devices and they have not expired.
Check the workflow logs in A10 Control for issues.

Time sync Issues

A10 Networks recommends configuring the NTP server to ensure that all devices maintain accurate and synchronized time. For more information about setting up the NTP server, see Setting the NTP Server in the System Configuration and Administration Guide. To check the NTP status, enter the following command:

ACOS#show ntp status

NTP Server                                               Status

time.google.com                                          synchronized

If the NTP server is not set up or unreachable, you may encounter time synchronization issues. To address such issues, perform the following steps to manually set up the clock:

Enter the following command to show clock time:
```
ACOS#show clock
```
Enter the following command to set the clock:
```
ACOS#clock set 16:18:15 April 10 2022
```

DNS Resolution for FQDN based Device Registration

Condition/Error: Kafka down due to failure with DNS resolution when FQDN is used for device registration.

Cause: When ACOS is registered using an FQDN, ACOS must resolve the hostname through DNS. If the DNS server is not reachable through the data interface, DNS resolution fails. As a result, Kafka clients cannot establish a connection, which leads to device health and analytics data not appearing in the A10 Control GUI.

Resolution: Ensure that the DNS server is reachable through the data interface, or configure a static host route so DNS queries are forwarded to the correct gateway.

Example:

ACOS>enable

ACOS#config

ACOS(config)#ip route 10.19.13.54 /32 10.19.12.1

ACOS(config)#write memory

Where, 10.19.13.54 is the DNS Server IP address and 10.19.12.1 is the Management Gateway IP address.