Avoiding duplicate devices caused by SNMP configuration or credentials

Inconsistent SNMP configuration or responses can cause Auvik to interpret the same device inconsistently and create duplicate device records.

How SNMP issues can create duplicates

Potential causes include:

• SNMPv2c and SNMPv3 both being available but returning different identity data.
• SNMPv3 engine ID changes or user and engine mismatches.
• Different community strings being assigned to views that return partial or inconsistent data.
• Multiple credentials returning different values for sysName, sysObjectID, or serial number.
• Management IP addresses being NATed, reused, or inconsistently reachable.

Recommended SNMP configuration

For each device:

• Use one SNMP version whenever possible. SNMPv3 is recommended when supported.
• Disable unused SNMP versions.
• Keep the SNMPv3 engine ID, username, authentication settings, and privacy settings stable.
• Ensure all credentials that may be used for the device expose the same read-only system OIDs.
• Confirm that SNMP views include the system information required for identification.

Changes to the SNMP version, engine ID, users, views, or device management configuration may require assistance from a network or device administrator.

Review Auvik credentials

In Auvik:

• Confirm the intended credential is assigned to the device.
• If credential order is supported in your environment, place the correct and most complete credential before credentials that provide limited or partial access.
• Use the built-in SNMP test to compare the values returned for:
  • sysName
  • sysObjectID
  • Serial number, where available

The returned identity values should remain consistent across polling attempts.

Recover from duplicate device records

Before deleting any duplicate device, determine whether both records contain history that must be preserved.

1. Identify the record with the most complete and accurate SNMP identity.
2. Compare the device names, IP addresses, MAC addresses, serial numbers, interfaces, and monitoring history.
3. If historical data exists in both records, contact Auvik Support before deleting either record to review available reconciliation options.
4. If one record is confirmed to be redundant and historical data does not need to be preserved, remove or unmanage it according to your normal device-management process.
5. Correct the SNMP configuration and allow discovery to run again.
6. Confirm that the device remains represented by one consistent record.

Deleting a device may remove data associated with that record, and the device may be rediscovered if its IP address remains within the discovery scope.

If duplicates continue to appear

Provide Support with:

• The affected Auvik site.
• Device IDs for the duplicate records.
• Device IP addresses and MAC addresses.
• Returned sysName, sysObjectID, and serial values.
• SNMP versions and credential types configured.
• Any recent SNMP engine ID, credential, view, NAT, or management-IP changes.
• Approximate timestamps for when the duplicates appeared.