Network Management
Scheduled Discovery results show duplicate entries for agent-polled nodes across multiple discovery profiles
Agent-polled nodes appear as duplicate entries in Scheduled Discovery Results across multiple discovery profiles.
First published date
Last published date
Overview
When multiple Network Sonar Discovery profiles are configured with unique, non-overlapping subnet ranges, the Scheduled Discovery Results page may still show the same node appearing once per profile - each with a status of "Changed" and identical discovered resources.
This behavior affects agent-polled nodes and occurs even though the node's IP address is only included in the subnet scope of one profile.
Product section
Cause
Multiple discovery profiles have the "Check existing nodes polled by an agent for node changes and updates" option enabled on the Agents tab of the Network Sonar Wizard.
Resolution
-
Navigate to Settings > Network Discovery.
-
Edit each discovery profile and go to the Agents tab.
-
Uncheck "Check existing nodes polled by an agent for node changes and updates" on all profiles except the one that should be responsible for discovering agent node changes.
-
Save and close.
After the next scheduled run, agent-polled nodes will only appear in the single profile where this option remains enabled.
Note: If the duplicate entries are caused by Discovery Import Deduplicator weights set to 0 in the Settings table instead, refer to Disable Duplicate Detector for Discovery Engine.