Troubleshoot login credentials

From the entity navigation on the device dashboard, hover over the Discovery button and click Troubleshooting.

For login credentials, there are seven steps that need to be verified before a device can be authorized.

• Step 1 - Device must be managed
• Step 2 - CLI service must be enabled for the device
• Step 3 - SSH or Telnet service must be enabled for the device
• Step 4 - Device must be running SSH or Telnet
• Step 5 - Device must have valid login credentials
• Step 6 - Auvik must have necessary privileges to communicate with the device
• Step 7 - Auvik must support the device

Step 1 - Device must be managed

1. To manage the device click re-enable management.
2. Update the management status from Unmanaged to Managed
3. Click Save.

Note: If you don’t see a green checkmark for SNMP, confirm that SNMP has been set correctly on the device.

Step 2 - CLI service must be enabled for the device

1. Click must enable the CLI service.
2. From the Enabled drop-down menu, select Yes, use this service to gather data.
3. Click Save.

If CLI has been enabled on the device, but it appears disabled in Auvik, you need to enable the device on the CLI service.

1. Click add this device to the CLI service group.
2. In the Devices to use this service field, add the device by name or device type. If there's an exclusion for the device or type, remove it.
3. Click Save.

Step 3 - SSH or Telnet service must be enabled for the device

1. Click either SSH or Telnet.
2. From the Enabled drop-down menu, select Yes, use this service to gather data.
3. Click Save.

If SSH or Telnet has been enabled on the device, but it appears disabled on the device in Auvik, you need to enable the device on the appropriate service.

1. Click either SSH or Telnet
2. In the Devices to use this service field, add the device by name or device type. If there's an exclusion for the device or type, remove it.
3. Click Save.

Step 4 - Device must be running SSH or Telnet

If SSH or Telnet isn't running on the device as expected, make sure that SSH or Telnet have been enabled.

After you've confirmed that SSH or Telnet is running on the device, check that the correct ports are configured in Auvik.

1. Click either SSH or Telnet.
2. From the Use Default Ports drop-down menu, select No - Custom Ports. To specify multiple ports for a service, click the + sign to add the next port.
3. Click Save.

Step 5 - Device must have valid login credentials

1. Click Add Login Credentials.
2. Fill in the Add Login Credential form. When adding an entity for the credential, you can filter devices. See How to filter data in Auvik for more detail.
3. Select the credential connection type.
   • For Telnet or SSH, Telnet only, or SSH only, enter the credentials as they apply. These could be:
     1. Username only
     2. Username and password
     3. Username, password, and CLI enable password
     4. Password only
     5. Password and CLI enable password
   • For SSH key, enter the username and paste in the SSH key. If applicable to the credential, enter the SSH key passphrase and CLI enable password.
4. Select Save.

Step 6 - Auvik must have necessary privileges to communicate with the device

If Auvik is able to log into the device using SSH or Telnet, but we're missing the CLI enable credential or the credential no longer matches what's configured on the device, you should update the password.

1. Click update the CLI enable password.
2. Enter in a CLI enable password. To confirm the correct password was entered before saving, click the eye () in the password or passphrase fields to show the password or passphrase.
3. Click Save.

Step 7 - Auvik must support the device

If the credentials are fully authenticated, but Auvik can't fully log in, you may see a message of Oh no! It looks like we don’t support this device yet. It could be the appropriate CLI specification isn't yet available for your device.

If that happens, submit a request to Auvik Support to check the device and make sure that CLI is not supported.

Congratulations!

Your device is fully authenticated for login and we’ll start gathering information about your device.