3 Replies Latest reply: Dec 11, 2012 11:04 AM by Sohail Bhamani RSS

Discovery longer than 600 minutes?

jon0966

Is there any way to have discovery beyond 600 minutes?  Our network is far too large and diverse globally (higher latency) to attempt a scan beyond 0 hops without it timing out.

 

 

J

 
  • Re: Discovery longer than 600 minutes?
    Sohail Bhamani

    My recommendation to you would be to create multiple discovery sessions and stagger them using discovery scheduling.  This way your session will actually complete, you can stagger them so there isn't any massive data flood on the network (although it wouldn't be that much anyway), and you can then control what gets scanned when.

     

    My experience has shown that having multiple sessions versus one massive one is easier to handle, will actually complete, and provides additional abilities as I mentioned above.

     

    Hope it helps.

     

    Sohail Bhamani

    Loop1 Systems

    http://www.loop1systems.com

    • Re: Discovery longer than 600 minutes?
      jon0966

      I've broken the 10.0.0.0/8 into 256 individual scans comprising of 10.x.x.0/16's.  If the Hop count is 0, the scan completes.  Hop counts greater than 0, do not, most times. 

       

      I attempted to scan 10.0.0.0/18, and that did not complete with Hop count greater than 0, either.  This should be an easy feature request for SW.

      • Re: Discovery longer than 600 minutes?
        Sohail Bhamani

        Well increasing the hop count is opening another can of worms.  I always share with my clients to not increase this past 0.  You can cover what needs to be scanned in the networks portion of the sonar discovery wizard so increasing the hop count only adds complexity to the scan.  Why not just define what should be scanned by subnets and leave the hop count at 0.  This way you know exactly whats being scanned.

         

        Sohail Bhamani

        Loop1 Systems

        http://www.loop1systems.com