How can we help?

Split incorrectly merged devices

Follow

When endpoints do not expose reliable unique identifiers, Auvik may incorrectly combine two separate devices into one record. This can occur with some IP phones, including Yealink phones that do not expose SNMP data.

What you may see

  • Two phones appear as one device with multiple alternating IP addresses.
  • Device history appears combined.
  • Interfaces, names, or availability data are inconsistent.
  • The merged device changes location or identity as IP addresses change.

Request a non-destructive split

Do not delete the merged device if you need to preserve its existing history.

Open a Support ticket and provide:

  • The current merged device ID.
  • The MAC address of each device.
  • The current or last-known IP address for each device.
  • Switch port information for each device, if available.
  • LLDP/CDP details or switch MAC-address table snapshots showing that the devices are connected to different ports.
  • The Auvik site and approximate time when the merge was first noticed.

Auvik Support will review the records and determine whether the devices can be split while preserving existing monitoring data where possible.

Prevent the devices from merging again

Stabilize IP identity

  • Create DHCP reservations for each device based on its MAC address.
  • Use consistent static IP addresses if appropriate for your environment.
  • Avoid frequent IP changes for devices that do not provide reliable identifiers.

Use unique device names

  • Assign a unique hostname to each phone through the phone interface or provisioning server.
  • If DHCP Option 12 or Option 61 is used, confirm that each phone provides unique values.

Improve switch visibility

Ask the network administrator to:

  • Enable SNMP on the access switches.
  • Ensure Auvik can poll the switches from the collector.
  • Enable LLDP or CDP so Auvik can associate each phone with its individual switch port.

Remove ambiguous data

Review the network configuration for:

  • Stale DHCP leases associated with old MAC and IP address pairs.
  • Overlapping discovery subnets.
  • Proxy or NAT configurations that cause multiple devices to appear behind the same address.

If devices merge again

Capture a 10–15 minute window containing:

  • Switch MAC-address tables for the affected ports.
  • ARP entries for the devices’ IP addresses.
  • DHCP lease records for the devices’ MAC addresses.
  • Device names, MAC addresses, and timestamps.

Attach this information to the existing Support ticket so Auvik can investigate the merge behavior and determine whether additional safeguards are available.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Auvik System Status

Check system status