Auvik leverages device credentials for many core functions. To learn the basics on how to add, edit, and delete credentials from Auvik, see the Manage Credentials section.
Leveraging the same credential across sites
If you intend to use the same credentials for devices across multiple sites you manage with Auvik, add the credentials at the global view level. Once you’ve added the credentials from the global level, they’ll be inherited by any sites and multi-sites below your global level.
Generally speaking, Auvik recommends that you add credentials for the Cisco API, Datto API, and Meraki API from the global level. If you also leverage a common SNMP community string across sites, or device login credentials across sites, those can be added from the global level as well.
Using SNMP v2c versus SNMP v3
Auvik supports SNMP version 1, 2c, and 3. SNMPv3 is more secure as it implements authorization and encryption protocols, but common practice in network management is to use SNMP v2c. Refer to your company’s security guidelines to determine which SNMP version to use. At minimum, refer to Auvik’s guidelines on credentials to create a more secure SNMP v2c community string.
Controlling how credentials are applied to devices
To support Auvik’s auto-discovery and ease of use capabilities, Auvik tries using all credentials that have been added to Auvik on all relevant devices until it finds the correct credential. Once Auvik finds the correct credential, that credential (SNMP, Login, WMI, VMware, etc.) is used for all subsequent communication with that specific device. In a scenario where the correct credentials haven’t been added to Auvik, all available credentials will continue to be applied.
As an Auvik administrator, you may want to restrict which credentials are attempted against each device or device type when adding them into Auvik. To do so, simply add filters to the Devices field as shown in the screenshot below.
We recommend that you apply filters for login credentials based on device type,, vendor, or IP address. You may also exclude a specific credential from being attempted on a device by using the “not:” filter. It typically isn’t required to apply filters for SNMP, WMI, and VMware credentials. If you do choose to apply filters for these credential types, we recommend using IP address filters or the “not:” filter.
Leveraging the Matches field
On each Add Login Credentials modal, Auvik displays the number of devices a filter matches below the Devices field. Pay attention to how many devices match the filters you’ve applied using the number displayed below the Devices field. If the number displayed is 0, you’ve likely used the wrong identifiers in the Devices field, and these credentials won’t be used on any devices. Make sure the number is approximately the number of devices you’d expect the credential to work on.
SNMP credential inheritance between parent and child sites
SNMP credentials created at a parent or global level are generally inherited by child sites unless a child site has a local credential or override.
When a child site has its own SNMP credential, the local credential takes precedence over the inherited parent credential.
Deleting a child-level credential
Deleting a child-level SNMP credential does not automatically restore a previously inherited parent credential. The child site may continue without the expected credential until its local overrides are removed or the credential is added again.
Restore the inherited credential
To restore parent-level inheritance:
- Review the SNMP credentials configured directly at the child site.
- Remove local SNMP credential overrides that should no longer apply.
- Confirm that the required credential exists at the parent or global level.
- Retry the SNMP credential or allow the next discovery cycle to complete.
- Confirm that the child site is using the inherited credential.
If you prefer site-specific control, add the required SNMP credential directly at the child site instead.
Best practices
- Create common SNMP credentials at the parent or global level whenever possible.
- Document child-site overrides and the reason for each override.
- Before deleting a child-level credential, confirm whether the site should inherit the parent credential or use a different local credential.