Welcome, Guest. Please login or register.

Author Topic: Device discovery time increasing  (Read 3346 times)

nerdi

  • Guest
Device discovery time increasing
« on: January 29, 2010, 05:15:41 PM »
On 1.0.5 -Discovery time per device seems to increase the further into discovery we get. Here's the stats from our most recent discovery.
 Took 3240 minutes
   3252
   3253 Devs:   1132 devices discovered
   3254 Node:   19413 nodes read () from nedi.nodes
   3255 Node:   18056 IP and 3598 non-IP nodes processed
   3256 Track:  2464 IP and 11619 IF changes detected
   3257 Node:   27071 nodes written to nedi.nodes

I expect the larger core switches to take a couple hundred seconds each, but sparsely populated edge switches are taking way to long. The examples below first show the time logged in the run above and then compared to a test run. I'm not sure how comparable these are, but the disparity is large.

 xxx.xxx.xxx.xxx s162-wsom195    v7 i58  Jvj1 p0/1 m1     a3      PuFi1 Fp1 Fi192 Fp192 f230      808/146-106s
 xxx.xxx.xxx.xxx s162-wsom195    v7 i58  Jvj1 p0/0 m1     a3      PuFi1 Fp1 Fi192 Fp192 f341Pu      0/1-8s

xxx.xxx.xxx.xxx      shaw275-e218    v12 i59 Jvj1 p0/1 m1     a5      HsTpHsTpHsTpHsTpHsTpHsTpHsTpHsTpHsTpHsTpHsTpTuFi1 Fp1 Fi499         Fp499 f2522         415/1110-344s
 xxx.xxx.xxx.xxx      shaw275-e218    v12 i59 Jvj1 p1/0 m1     a5      PuFi1 Fp1 Fi499 Fp499 f2542       1/1-5s

Host systems performance seems good, with most cpu time in user, on Nedi. Swaping isn't an issue, and memory increases overtime but does notexhaust available. Watching each device, Nedi gets VLAN info and then appears to process for minutes without any more I/O.

Anyy suggestions or ideas would be appreciated.
Thanks


I

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2786
    • View Profile
    • NeDi
Re: Device discovery time increasing
« Reply #1 on: February 02, 2010, 06:33:07 PM »
I can see a lot of failed login attempts. Turn on logging to find out why...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

nerdi

  • Guest
Re: Device discovery time increasing
« Reply #2 on: February 16, 2010, 07:30:52 PM »
Thanks - a missing userid value in nedi.conf was causing the problem.

shadowcaster

  • Guest
Re: Device discovery time increasing
« Reply #3 on: February 25, 2010, 09:25:10 AM »
I wasn't deep into investigation yet, but I was not able to use 1.0.5 because it crossed 3 hours discovery interval. I use snmp only, no cli access, because cli requires to use "enable", and thats what I cannot afford due to security considerations.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2786
    • View Profile
    • NeDi
Re: Device discovery time increasing
« Reply #4 on: February 25, 2010, 10:46:27 PM »
1oh5 is slower  :o
Can you pin down where it loses time?
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

isc

  • Guest
Re: Device discovery time increasing
« Reply #5 on: March 03, 2010, 10:37:16 AM »
try the parameter -I and if you have ipphones you might get a delay if your ipphone browser is deactivated. we had that problem too, but you can make nedi skip it by editing the source.

this two points made our discovery run much faster ...

greets

nerdi

  • Guest
Re: Device discovery time increasing
« Reply #6 on: April 07, 2010, 10:01:47 PM »
1oh5 is slower  :o
Can you pin down where it loses time?

I see a pause getting ifHCIn and Out Octects  when running nedi.pl -t of about 15sec, where there same switch when running nedi.pl -pb on the entire network  pauses for 90 seconds between SNMP get response and get request.
I don't see any other pauses running nedi.pl -t but nedi.pl -pb has lots of pauses from this point  forward in the device discovery.

The testing I did ran the nedi.pl -t while an entire network nedi.pl -pb was running so I'm not thinking resources on the server.