1 of 1 people found this helpful
Are you using Sonar discovery to automatically import nodes into NPM? I've seen the problem you're describing in my environment, when a device is part of multiple network ranges that I want to discover. The discovery thinks each IP on that device is a different device entirely. I used the discovery ignore list to block out all of the interfaces that I didn't want automatically added as nodes. Assuming this is the same thing you're running into, you can go to the Admin page > Network sonar discovery > Scheduled discovery results, locate your device, and add each incorrectly discovered node to the ignore list.
Hope that helps,
The Sonar discovery never seemed to work for me since it would always die about half way through and never complete. I've been putting all of our devices in manually and then selecting the interfaces, etc that I want monitored. I understand adding the certain interfaces to the ignore list but we have hundreds of devices and it would be rather time consuming. I just thought there would be a way to add a device by its loopback and then have every other interface on that device be a child of the loopback to keep it from thinking we have multiple devices versus multiple interfaces.