Introduction
In multi-site Auvik environments under the same root level, a single device may appear in more than one site. While these entries represent the same physical device, Auvik treats them as separate instances because discovery is performed independently by each site’s collector.
This article explains why this happens and how to resolve it.
Symptoms
You may observe the following:
- The same device (same IP) appears in multiple sites
- Each instance has a different device ID
- Removing the device from one site does not remove it from others
- The device generates monitoring data or alerts at more than one site
Root Cause
This behaviour occurs when both of the following conditions are true:
- Collectors from different sites can reach the same IP address, and
- That IP address (or its subnet) is included in the discovery scope of multiple collectors
This means the device, or the network it belongs to, has effectively been assigned to more than one collector from different sites. As a result, each collector:
- Scans the IP or subnet
- Independently discovers the device
- Creates a separate device entry within its site
Auvik does not correlate or merge these entries across sites, even within the same MSP.
How to Confirm
To verify this is the cause:
- Identify the device IP address appearing in multiple sites
- In each site, navigate to Discovery → Manage Networks
- Check whether the same IP or subnet is configured in more than one site
- Validate that multiple collectors have network reachability to that IP
If both discovery overlap and reachability exist, this behaviour is expected.
Resolution
1. Ensure Subnets Are Assigned to Only One Site
A device or a subnet should be added to only one site, and not multiple sites.
Steps:
- Go to Discovery → Manage Networks
- Identify overlapping subnets across sites
- Remove the subnet from all non-owning sites
2. Use IP Exclusions for Shared Devices
If a device must remain reachable across sites:
- Add its IP as an exclusion in all non-owning sites
- Allow only one site to actively monitor it
3. Define Device Ownership
Establish a clear rule for which site is responsible for monitoring shared infrastructure.
- Assign a single “owning” site
- Remove or exclude the device from all others
Important Notes
- This is expected behaviour, not a system error
- Auvik performs site-specific discovery per collector
- Devices are not deduplicated or merged across sites, even within the same root level.
- Deleting a device from one site does not affect other sites
Summary
A single device can appear in multiple sites when multiple collectors within the same root level can reach it and are configured to scan its IP or subnet.
To resolve this:
- Ensure each subnet is only assigned to one site
- Limit collector reachability
- Use exclusions for shared IPs
- Define clear monitoring ownership
These steps ensure accurate site separation and prevent the same device from appearing across multiple sites.