Welcome, Guest. Please login or register.

Author Topic: How to initiate parallel discovery in a large campus network  (Read 1862 times)

otbl

  • Guest
I would like to update node attached to devices, interfaces counters, and bandwith as quick as possible.

I think about lauch multiple discovery, but how to split my network and how to get get only pertinent data.

dobst

  • Full Member
  • ***
  • Posts: 153
    • View Profile
Re: How to initiate parallel discovery in a large campus network
« Reply #1 on: June 12, 2013, 05:13:00 PM »
I'm using the following crontab triggered script to update the database with five parallel threads:

Code: [Select]
/opt/nedi/nedi.pl -A 'RIGHT(INET_NTOA(devip), 1) IN (0, 5)' > /dev/null 2>&1 &
/opt/nedi/nedi.pl -A 'RIGHT(INET_NTOA(devip), 1) IN (1, 6)' > /dev/null 2>&1 &
/opt/nedi/nedi.pl -A 'RIGHT(INET_NTOA(devip), 1) IN (2, 7)' > /dev/null 2>&1 &
/opt/nedi/nedi.pl -A 'RIGHT(INET_NTOA(devip), 1) IN (3, 8)' > /dev/null 2>&1 &
/opt/nedi/nedi.pl -A 'RIGHT(INET_NTOA(devip), 1) IN (4, 9)' > /dev/null 2>&1 &

The script calls 5 instances of nedi. Each processes devices whoes last number of their ip is in (x, y), eg (1, 6). I played a bit and found out that my update process needs just 7 minutes instead of 25 with a single instance to update >400 devices. Running more than 5 instances or querying not all snmp variables doesn't gave me any more enhancement.