North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Intelligent Automation of network tasks
On Cisco it is (generation of config update) veryu complicated (in general case) task. But we always automated every day config changes (acccess lists, as path lists, route maps, interfaces except some special cases, and so on). perl + 'expect+ 'conf net' was key elements. ----- Original Message ----- From: "Jared Mauch" <firstname.lastname@example.org> To: "Ejay Hire" <email@example.com> Cc: <firstname.lastname@example.org> Sent: Tuesday, December 07, 2004 10:53 AM Subject: Re: Intelligent Automation of network tasks > > On Tue, Dec 07, 2004 at 12:39:25PM -0600, Ejay Hire wrote: > > > > In my opinion, every network with more than a dozen or so routers needs > > an automated method to distribute massive configuration changes. There > > is a lot of fear that something will break during updates, but with some > > intelligence, that risk can be minimized. > > juniper and cisco both support taking machine generated > configurations generated by a non-router device (eg: unix host). > > http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801d1dc2.html > > it's not just in 12.3T, it's also in 12.2S.. > > on your juniper, try something like "config, load override" > > - jared > > -- > Jared Mauch | pgp key available via finger from email@example.com > clue++; | http://puck.nether.net/~jared/ My statements are only mine.