The most recent content from our members.
Right now in SolarWinds NPM, most of the alerts are threshold-based. Either we set static thresholds or use dynamic baselines, but in both cases we end up getting too many false positives or sometimes even missing real issues.In modern networks (hybrid, cloud, SD-WAN, etc.) traffic patterns are not always predictable. A…
When creating a new Network Discovery it would be nice to be able to have the option to start with a clean discovery palette instead of preloading NCM configs/credentials and/or SNMP credentials. It is painful if you have over 100+ SNMP credentials you have to remove if only doing an ICMP add of nodes. In addition, be able…
Yesterday I updated our NPM from 11.5.1 to 11.5.2 (as well as applied the "OrionPlatformv2015 1.2. HotFix1 "). Everything appears to be in working order except Network Sonar Discovery. We had manually entered a list of several subnets we wanted to discover bi-annually and had created specific staggered schedules for. As of…
According to SW they recommend the following when using subnets for for the NSD. Subnets Use this option to scan every IP address in a subnet. SolarWinds recommends scanning at most a /23 subnet (512 addresses max). Scanning a subnet returns everything that responds to ping, so we recommend only scanning subnets where the…
This would potentially be quite a large update to the current discovery system but would make it an extremely more powerful tool that can be made as complicated or as simple as needed by the administrator. Put simply, Network Sonar incorporating the logic system behind alerting. Something everyone will already be familiar…
Even if I select "Select All Nodes" it only selects the nodes, not the interfaces or volumes. I want to clean them all out and start over as it has gotten out of hand. How can I clean out my Discovery Ignore List entirely?
I am going to try to explain some odd interface issues that I have form time to time. 1. I have network sonar configured on my Domains to auto import nodes in select OUs. 2. There are some morning that I come in and have a good handful of nodes that have new NIC cards in them even though nothing has changed. 3. Is there…
We use a lot of Network Sonar Discovery profiles (1 per remote site), the process of creating and maintaining is somewhat cumbersome. I feel that a few tweaks should be done to improve it. 1st, Poll for VMware should not be enabled by default. I even wonder why there is a check box when the windows discovery does not have…
A colleague used the ip range instead of network subnet option in Sonar Discovery... 10.x.x.x to 255.255.255.224 is a really long range to scan. Cancelling the job does not to the job... I have a neverending spinning wheel... Restarting the services or the server did not do the job... As seen here as well: Network Sonar…
In Network Sonar, I would like to have the new devices automatically assigned to a predefined group. ie: * I have multiple discovery tasks that programmed for every segment of my network... a Group is configured for every segment and all devices in the segment are assigned to it. * I could have a group where all recently…
It looks like you're new here. Sign in or register to get started.