Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Disable Duplicate Detector for Discovery Engine

Disable Duplicate Detector for Discovery Engine

Created by John Wallace, last modified by Matthew.Orr on Sep 07, 2017

Views: 107 Votes: 2 Revisions: 6


Nodes are not being discovered through Network Discovery but they can be added manually without any issues. The Duplicate Detector may be removing selections if nodes are duplicated on entries such as MAC address, SysName, or DNS. Turning off this option allows the use of Network Discovery to add these nodes in bulk regardless of the check.


NPM 11.5.X


There are duplicates for one entry after running Network Discovery with verbose logging turned on.

The Duplicate Detector did not allow the Network Discovery to list these.


Resolution 1:


If this occurs during the discovery job itself, this is de-duplicating the same nodes within the same discovery profile

  1. Stop the services.
  2. Go to C:\Program Files (x86)\SolarWinds\Orion\ and edit the SolarWinds.Orion.Discovery.Job.dll.config in a Notepad as an admin.
  3. Scroll to bottom of the file and look for the following:
    <add key>="DisableMacDuplicateDetector" value="false" />
    <add key>="DisableSysNameDuplicateDetector" value="false" />
    <add key>="DisableDNSDuplicateDetector" value="false" />
  4. Change the values to True.
  5. Run Network Discovery and verify that all undiscovered nodes are there.


Note: Revert to the previous (or default) setting if there will be issues going forward caused by this change.


Resolution 2:


If this occurs during importing discovery results, this will occur still regardless of the first resolution since it is designed differently due to a calculation based on weights (e.g. in default: two devices have same sysname, but different MAC and DNS then it is not duplicate, etc


In the Database, go to the Settings table:

-Discovery-Import-SysNameDeDuplicator-Weight 25
-Discovery-Import-DNSDeDuplicator-Weight 27
-Discovery-Import-MacDuplicateDetector-Weight 26

If you change the weight value for one of these related items to 0, then duplicate detection will not occur for such item (sysname, dns or mac)



Last modified