Software or PHP/PERL scripts for simple network management?

William Allen Simpson william.allen.simpson at gmail.com
Wed Jun 20 00:39:54 UTC 2007


alex at pilosoft.com wrote:
> Neither 'show ip route' or 'have a text file' scale beyond a hundred 
> customers. 
> 
Hogwash.  Used text file allocation for ~3,000 customers.  After all, it
is *REQUIRED* to exist (for bind).  You need *a* canonical place that is
authoritative for all others.  Existing tools easily track commits.

DNS should always reflect reality.  Then automated tools will show human
readable information.  Someday, it may even be authenticated (but I've
been beating that horse for a decade).  I'm sick and tired of bad NS data.

Yes, we used a separate database for billing, and maybe could have
automatically generated the text file.  Didn't want the customer
service/billing folks to have access to network configuration.... ;-)

Any time you have more than a single location for maintaining network
configuration data, or allow technicians to just slap a route into a router
on a whim, you are bound for future difficulties!

And when the routing table doesn't match, withdraw the route, and fire the
miscreant that failed to properly maintain the allocation data!




More information about the NANOG mailing list