Troubleshooting Configuration Backups in Auvik

1. Check Device Support & Access

   • Click on Inventory
     
     

   • Go to Devices

   • Confirm the device is listed

   • Click on Discovery
     
     

   • Go to Manage Credentials

   • Ensure valid and working login credentials are added under Manage Credentials

   • Verify SSH or Telnet is enabled on the device
     Note: Avoid multiple failed login attempts that may trigger device lockouts

     • Target credentials to specific devices or device types

     • Avoid applying credentials to all devices

2. Check Backup Status

   From the device dashboard:

   • Look for the configuration backup status indicator

   • Check the last successful backup timestamp

   • Compare it with the expected polling interval under Discovery > Discovery Settings (default: every hour)

3. Common Issues

   • No Backups Recorded:

     • Ensure the device is classified as a network element

     • Verify manual login works from the collector subnet

   • Backups Stopped Working:

     • Review timestamp of last backup

     • Check if anything changed recently (e.g., firmware updates, credential changes)

   • Login Passes, But No Backup Appears:

     • Confirm that Auvik’s credentials match those needed for CLI commands like show run or show config

4. VPN or Interface Issues

   If the device is behind a VPN, ensure:

   • The source IP seen by Auvik matches the configured IP

   • An IP is explicitly assigned to the egress tunnel interface (common for FortiGates)

5. Get Help from Auvik Support

   • Go to the collector shell and run the copylogs command

     • For more information click here

   • Reach out to Support with the device name and any context (changes made, symptoms, etc.).

Can I see or change the CLI or API commands Auvik uses?

Auvik does not expose the exact per-device CLI or API sequence used for configuration backups, and the command sequence cannot be customized for an individual device through the Auvik interface.

Depending on the device and supported collection method, Auvik generally uses read-only CLI commands or vendor APIs to identify the device and retrieve its configuration.

Credential and Permission Requirements

A successful login does not guarantee that Auvik can create a configuration backup. Many devices allow read-only identification commands but require elevated permissions to run configuration export or backup commands.

FortiGate

For SSH or CLI-based backups:

• Assign the Auvik user to the super_admin profile.
• Confirm the account can retrieve the complete running configuration.

For API-based backups:

• Use a FortiGate REST API administrator.
• Assign the API administrator the permissions required to export the configuration, including any required read/write access.

SonicWall

SonicWall may reject configuration backup or export commands when the account is read-only.

Use an account that has permission to export the current configuration.

Other vendors

Auvik primarily uses read-only show or equivalent commands to retrieve device configuration. Some vendors and device models require elevated privilege to run commands such as:

• show running-config
• show configuration
• Configuration export commands

Ensure the Auvik account can execute the commands required to retrieve the complete configuration.

Update and test the credentials

These steps should be performed by an authorized device administrator:

1. Update the credential set in Auvik at the site or device level.
2. If changing accounts, such as moving to an auvikadmin account, prioritize the new credential and de-prioritize or remove the old credential.
3. Sign in to the device using the same account configured in Auvik.
4. Run the required show, export, or backup commands.
5. Confirm that the account can retrieve the complete configuration without permission errors or interactive prompts.
6. Re-run the backup in Auvik.
7. Verify that a new configuration snapshot is saved.

If the backup still fails, provide Support with the device make, model, firmware version, credential type, last successful backup time, and any relevant device log messages. Do not include passwords, API keys, or other secrets.

For Fortinet devices that use the REST API, see Backing Up Fortinet Configurations via API.