Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Nodes with the same host name but different IP addresses are not added after discovery

Nodes with the same host name but different IP addresses are not added after discovery

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 995 Votes: 1 Revisions: 3

Overview

When Network Sonar Discovery discovers nodes with the same host name but different IP addresses, only the first node is added.

Environment

All NPM versions

Cause 

By design, Network Sonar Discovery only adds a single node in case of duplicates.

Resolution

Perform any of the following actions:

  • Add the nodes manually one by one. 
  • Disable node de-duplication.
    ​Warning: SolarWinds strongly recommends that you only edit configuration files as instructed. Any additional modifications to the configuration file may result in system performance issues or may create an error state.
    1. Go to %Program Files%\SolarWinds\Orion
    2. Open the SolarWinds.Orion.Discovery.Job.dll.config file in a text editor.
    3. In the following lines, change the value from "false" to "true":
      <add key="DisableSysNameDuplicateDetector" value="false"/>
      <add key=“DisableDNSDuplicateDetector" value="false"/>
    4. Save the file.
    5. Restart all services in the Orion Service Manager.

 

Last modified

Tags

Classifications

Public