RE: [Netdisco] different mac_suck intervals

[David K. <dk...@um...>]

Actually the easiest way to probably do some of this is with netdisco -M and
a 2 small perl scripts.  1 to pull your core and 1 to pull the rest of your
switches.

I carved netdisco out to do a dump on it's IPs to files, and then use those
files to do be able to run multiple processes at once (I'm pulling about
1700 devices on an hour interval looking to head for a half hour interval
with a large campus, lots of dhcp and wireless and things changing very
often).  It's not pretty but it works.

You could probably do the same thing provided you're not adding a lot of
devices frequently.  Instead of doing dumping the database IPs, just use a
set of flat files and then a perl script to run netdisco -M perl IP at the
two separate intervals (You can do it the other way but the scripts become a
slightly more involved to separate out your core IPs).

	David

-----Original Message-----
From: net...@li...
[mailto:net...@li...] On Behalf Of Ralf Gross
Sent: Friday, August 26, 2005 4:29 AM
To: net...@li...
Subject: [Netdisco] different mac_suck intervals

Hi,

we have a rather large network with about 800 devices. Right now netdisco
works very well. Only the networkmap is not really useable with so many
devices...

I was asked, if it would be possible to have different mac_suck intervals
for core switches. These switch ports are mainly used for servers, so they
don't change that frequently nad we want to keep the network load as low
as possible.

I came to the conclusion that there are 2 options, which are both not very
convenient.

1. use 'netdisco -M $device'  for all devices and don't use 'netdisco -m'
at all. Not very realistic...

2. change the netdisco config in the crontab periodically and add the IP
address of the core devices to 'macsuck_no' option.

We do a mac_suck every 2 hours at the moment.

# netdisco crontab

5 */2 * * * /usr/local/netdisco/netdisco -b -m

I'd have to change the netdisco crontab from the (root?) crontab a few
minutes before the next mac_suck cycle would begin (or after the last
cycle).

# root crontab

0 11,19 * * * crontab -u netdisco
/usr/local/netdisco/netdisco.crontab.exclude-core

0 10,18 * * * crontab -u netdisco
/usr/local/netdisco/netdisco.crontab.include-core

The result would be that mac_suck for core devices only takes place two
times a day. Downside is, that I have 2 crontab files for netdisco that
have to be kept in sync and the macsuck_no list that I also have to care
about.

Any comments or better ideas?

Thnaks, Ralf






-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Netdisco mailing list
net...@li...
https://lists.sourceforge.net/lists/listinfo/netdisco-users

!DSPAM:430ed35e285071745663798!