If the system is automated as suggested by the mailing list,
warning message will be ignored at least.... there is no way
to know critical configuration changes vs. routines tasks.
So far, our discussion is device centric. The way I see NMS
is it should be network centric. That is, if I perform a
change to the network, deploy a VPN or an access list, lets
say I need to touch 5 devices and failed at 3rd device, I
would like to know what "rollback" realy means.
Min
> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de]
> Sent: Monday, April 18, 2005 1:40 AM
> To: Andrew Fort
> Cc: Kirby Files; Network Automation List
> Subject: Re: CLI transactions
>
> On Mon, Apr 18, 2005 at 12:37:10PM +1000, Andrew Fort wrote:
>
> > The way I see it, our base level becomes "transaction failed, (don't
> > save the config) then reload every device?". If device
> types support
> > transactions, we use them.
>
> Reloading is rather painful but seems the only way out. Of course, in
> some environments, reloading is really really painful. Perhaps another
> thing to consider is to print out a very clear warning
> somewhere about
> the device capabilities and its consequences ("sorry, your
> devices xxx
> does not properly support configuration transactions and may
> need to be
> reloaded in case a configuration transaction fails").
>
> /js
>
> --
> Juergen Schoenwaelder International University Bremen
> <http://www.eecs.iu-bremen.de/> P.O. Box 750 561,
> 28725 Bremen, Germany
>
Follow-Ups:
|
|
