2 Replies Latest reply on May 29, 2013 11:40 AM by michal.hrncirik

    Sonar Discovery - Tell Solarwinds/Thwack What You Think


      I'm starting a discussion to express grievances about the Sonar Discovery tool for the entire Thwack community.  It appears that larger environments have multiple issues concerning Sonar.

      It's obvious that Solarwinds expects us to deal with a sub-par tool that is so critical to discovering nodes for Management and Monitoring.


      Full disclosure, I am not a Solarwinds Admin, I am a Network Engineer.  My job description does not include learning the in's and out's of Solarwinds.


      IT shops for larger environments do not always know what is occurring at the farthest reaches of their networks, especially when local IT is thrown into the mix.


      I didn't choose Solarwinds, it already existed at my shop.  Local IT staff add devices all the time that will never be discovered due to Sonar limitations, but guess whose getting chewed out when those devices go down and nobody at Central was notified.  Upper management only cares that the issue was not reported and not resolved in a timely manner, they do not care for excuses about software the company has already paid for.


      I hope that people express their grievances with Sonar and that Solarwinds/Thwack pays attention.


      My grievances:

      - The arbitrary 10 hour max time limit imposed on the discovery process.  The seed router function exists for a reason.  I should have every expectation that adding a seed router to the discovery process and selecting all found routes will ensure that Sonar will discover all nodes until every subnet selected has been searched.


      - The discovered node purge when the above max time has been reached.  If you can't/won't fix the arbitrary timeout, then at least design Sonar to not purge the discovered node database.  I'm not sure Thwack/Solarwinds knows how frustrating this is when doing a full network scan.


      - Better custom dates for auto-discovery.  The current custom date selection is atrocious.  How about a start date and time, and the ability to select run every 1 day, 2 day, 1 week, 2 week, 1 month, 2 month, etc...  I suggest Solarwinds look at Bluecat IPAM for inspiration.  The current run every x-hours makes no sense.


      - Discovery is slow.  Latency for me averages less than 30ms between the Poller and any point on the network, but the discovery process takes to long.  A side-by-side SNMP sweep comparison between Lansweeper and Sonar on the same exact subnet, on the same exact ESX host shows Lansweeper mopping the floor with Sonar.  I can't believe that Solarwinds would allow Sonar to be that resource intensive.


      I appreciate flamers to not post.  Post your "solutions" on other threads.  This is for legitimate grievances that have gone unanswered for far to long. 


      To Thwack moderators, this discussion is not for asinine workarounds, and/or broken promises for future functionality.  Don't ask me specifics, you already know the limitations of your software.  Take it all in, and get the designers to fix it!!!  Please don't take this personal, it's just pure frustration from the software, and interactions between between users and moderators viewed on the Thwack forums.

        • Re: Sonar Discovery - Tell Solarwinds/Thwack What You Think

          Hi JB1981,


          I've sent your comments to the Product Manager and Dev for comment.




          • Re: Sonar Discovery - Tell Solarwinds/Thwack What You Think

            Hi JB1981,


            First of all, thanks for your feedback, I really appreciate it and take it as it is. We got a feedback from our users for Sonar Discovery improvements like this: http://thwack.solarwinds.com/ideas/1173 or this:http://thwack.solarwinds.com/ideas/1291.

            But to be honest, we are not getting complaints about maximum discovery time limitation or technical limitations of our discovery.


            I understand your use case. You are Network Engineer and you are responsible for solving networking issue. That means, you have to know what are those devices so you can watch them. Now how to address your issues, well if you don't give us more details, we can hardly understand what needs to be improved to make your life easier. You said, you didn't choose SolarWinds, is there a product that does exactly what you need in term of discovery? It would help me to understand what we would have to focus on.


            I agree with your points like better scheduler of autodiscovery.

            But regarding the maximum time of discovery, can you tell me if are you willing to wait 10 hours to let discovery finish on such large subnet space? That would mean you would be not able to monitor new nodes quickly? Why don't you split that discovery into multiple ones and let them scan smaller subnets in parallel instead? You are Network Engineer so I guess you are responsible for routers configuration correct, so you what segments of your network are dynamic, static, etc. - Just asking in order to understand your problem. Sonar Discovery allows you to decrease timeout interval which is usually the biggest problem if you scan for huge subnets with less than 50% utilization. I would also remove the amount of "hops" so it won't try to scan for neighbor subnets if you rely on seed router. Have you tried that?


            I can make a short call with you to clarify the points you are describing and again, your feedback is very important to us, since you are a real user of our product so I would truly appreciate more data from you.