Overview
After assigning a Shared Collector to a child site, you may notice that no devices are discovered even though the collector appears online, healthy, and approved.
This behavior is expected. Unlike a collector deployed directly within a site, a Shared Collector does not automatically begin discovering networks in the child site. Networks must be added before discovery can begin.
Symptoms
You may observe one or more of the following:
- The Shared Collector is online and healthy.
- The Shared Collector is approved and assigned to the site.
- No devices appear in the site's inventory.
- Network maps are empty.
- Discovery activity appears limited or inactive.
Cause
Assigning a Shared Collector makes the collector available to the site, but it does not automatically create or assign networks for discovery.
Auvik only discovers devices within networks that have been added and approved for scanning. If no networks exist for the site, the Shared Collector has nothing to discover.
Resolution
Add the networks you want the Shared Collector to scan.
- Navigate to Discovery > Manage Networks.
- Select Add Network.
- Enter the subnet or IP range you want discovered.
- Confirm the network is associated with the correct site.
- Save your changes.
Once the network has been added, the Shared Collector can begin discovery within the approved range.
Verify Discovery
After adding the network:
- Discovery activity should begin automatically.
- Devices will start appearing in the site's inventory as they are discovered.
- Network maps and monitoring data will populate as discovery completes.
The amount of time required depends on the size of the network and the responsiveness of the devices being scanned.
Additional Considerations
- Add all required subnets for the site. Devices outside configured networks will not be discovered.
- If devices still do not appear after adding networks, verify that the Shared Collector is online and assigned to the correct site.