The most recent content from our members.
I run a Network Sonar Discovery weekly to import new interface connections every week. We have a large network, so each poller we process discovery on takes several minutes to process. When we are running the discovery, any database connection timeouts or other errors runs the risk of causing SolarWinds to import all of…
We are installing hundreds of AV devices. I'd like to add them to NPM - just to get notified of up/down. I would like to be able to add custom properties, at the time of the scan, without modifying the db via SQL. For instance, If I use ICMP to add 300 devices in the 10.0.1.0/23 subnet - I would like to put in a…
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…
Morning all, We run a discovery scan every evening across all of our subnets to capture any machines that may have been missed and to ensure that anything new to these devices are picked up. Each morning I come in and ensure all the "New" devices are added and then add the "Changed" ones where applicable. The issue is,…
I am beginning to implement Network Sonar Discovery in my Orion environment that already has 1,900+ Nodes. The plan is to use it to find systems that have slipped through the cracks and are not in Orion, and to discover new interfaces/volumes that are not being monitored yet. The problem I am having is there is lots of…
If I create a scheduled sonar discovery job with multiple /24 networks does it scan all of those networks simultaneously or one after the other?
One major irritation for us is when we use Network Sonar Discovery to rediscover devices to scan for new volumes, interfaces, AppInsight,etc we need to perform the discovery listing the current polling engine the device is being monitored from. This results in multiple scanning profiles for each polling engine. We would…
I am working with over a thousand nodes, each with 50+ interfaces in the Network Sonar Discovery tool. I think it would be very helpful if on the ScheduledDiscoveryResults.aspx page, if we had the filter tools. In this way we could easily filter the access ports and ignore them, as well as, the virtual interfaces etc until…
After adding a node and it's associated interfaces, volumes, etc. to the database all other (non-selected) components should automatically added to the Ignore List based on the fact that it was not selected to be imported. Another option is to add a "select all new" button to the Scheduled Discovery Results page so all of…
Currently the sonar discovery options are only Daily, Once or Custom (on hourly basis). My issue is that I have 7 different scans I'd like to do and I'd like to run them weekly at 2am. So Scan 1 on Monday at 2am, Scan 2 on Tuesday at 2 am, Scan 3 on Wednesday at 2am etc. Problem is that with the current options, I can't…
It looks like you're new here. Sign in or register to get started.