Re: [Netdisco] Netdisco - Multiple Campuses

[DeShong, K. <kde...@he...>]

So do I need to adjust anything manually once I kick off my discovery? From looking at your response, it seems those lines are from your netdisco.crontab weekly discovery. Right now I've only got my main switch listed. 

# Walk network for new devices once a week (Wed @ 14:00)
0 14 * * 3    /usr/local/netdisco/netdisco -b -r 10.119.1.5


Ken DeShong
Network Engineer:
USF Health Information Systems
University of South Florida
12901 Bruce B. Downs Blvd.,MDC 51
kde...@he...
813-974-6288

 

"There are 10 types of people in the world. Those who understand binary, and those who don't"


-----Original Message-----
From: Ian Henderson [mailto:ia...@ia...] 
Sent: Tuesday, November 02, 2010 7:30 PM
To: DeShong, Ken
Cc: net...@li...
Subject: Re: [Netdisco] Netdisco - Multiple Campuses

On 03/11/2010, at 5:00 AM, DeShong, Ken wrote:

> I probably don't have a unique issue but I would like some experienced advice on how to implement. I have my existing Netdisco server setup and running strong on our Core network of about 400 switches. We have an outlying campus where I would like Netdisco to poll and give me information (the two campuses cannot see one another)

Hi Ken,

All you need to do is start discovery from one device in each location. I've got six  sites with an L3VPN between them - the crontab on the Netdisco box starts discovery for each different location on different days of the week.

0 14 * * 1 netdisco /usr/local/netdisco/netdisco -b -r capetown-router
0 14 * * 2 netdisco /usr/local/netdisco/netdisco -b -r mascot-router
0 14 * * 3 netdisco /usr/local/netdisco/netdisco -b -r perth-router
0 14 * * 4 netdisco /usr/local/netdisco/netdisco -b -r melbourne-router
0 14 * * 5 netdisco /usr/local/netdisco/netdisco -b -r ultimo-router
0 14 * * 6 netdisco /usr/local/netdisco/netdisco -b -r auckland-router

Once discovery is complete, the regular hourly polls just work.

Rgds,



- I.