Welcome, Guest. Please login or register.

Author Topic: PROBLEM OF DISCOVERY IN BIG NETWORK  (Read 571 times)

jclorenzo

  • Newbie
  • *
  • Posts: 1
    • View Profile
PROBLEM OF DISCOVERY IN BIG NETWORK
« on: July 06, 2017, 08:50:14 AM »
Hello good day.

I first apologize for my level of English as it is something basic.

I have installed Nedi 1.5C on an Ubuntu x64 machine with 4gb ram.
I have a seedlist of more than 7000 entries (different manufacturers, although the great majority are Cisco, 3com, Enterasys and HP). As you can deduce with such a listing, the scanning of the network takes too long.
I have seen that there are people who throw several threads simultaneously but of course I have doubts about how they do it, since if you throw several threads when using the same seedlist, it will always be thrown following the same order, right ?.
I have tried to launch it via GUI and the first thing that happens to me is that it does not finish the scanning as it stops.

How could you launch using multiple threads at once?
How many simultaneous threads could you put at the same time?
How is it better to launch this scan, from GUI or console?

Thank you very much, greetings  ;)

Hannu Liljemark

  • Full Member
  • ***
  • Posts: 130
  • Here to help
    • View Profile
Re: PROBLEM OF DISCOVERY IN BIG NETWORK
« Reply #1 on: July 06, 2017, 09:32:47 AM »

ascii

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
Re: PROBLEM OF DISCOVERY IN BIG NETWORK
« Reply #2 on: July 07, 2017, 10:15:53 AM »
http://forum.nedi.ch/index.php?topic=1989.msg8060#msg8060
i also use paralell discovery.
i use the end of the IP Adress as a filter.
Also skipping most of the stuff during day.

During the night i discovery the whole network based on there location.
meaning paralell discovery for the locations.

Are all you 7000 devices are connected to each other?
if they are in different locations without CDP neighborship than you can start the discovery at the same time.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2558
    • View Profile
    • NeDi
Re: PROBLEM OF DISCOVERY IN BIG NETWORK
« Reply #3 on: July 09, 2017, 07:17:18 PM »
I suspect slow DNS servers can cause such issues, as NeDi blocks the DB while waiting for an answer. I'll change this, but you can try with -n to see if it makes any difference.
« Last Edit: July 11, 2017, 11:40:15 AM by rickli »
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo