Great Circle Associates Network-Automation
(April 2005)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: CLI transactions
From: <albert @ research . att . com>
Date: Tue, 19 Apr 2005 11:53:29 -0400
To: <andrew . fort @ gmail . com>, <network-automation @ greatcircle . com>
Thread-index: AcVEf7DTV9UdMGf3Rj+88HPaeDTymgAd+Yog
Thread-topic: CLI transactions

Hi Andrew,  I don't quite follow the example and the point, and would
you mind elaborating?  -- Albert

> -----Original Message-----
> From: network-automation-owner@greatcircle.com
[mailto:network-automation-
> owner@greatcircle.com] On Behalf Of Andrew Fort
> Sent: Monday, April 18, 2005 9:33 PM
> To: network-automation@greatcircle.com
> Subject: Re: CLI transactions
> 
> On 4/19/05, albert@research.att.com <albert@research.att.com> wrote:
> > Hi Juergen,  Other than the castrophic cases you called attention to
> (and others we can think of where you lose the router or the ability
to
> reset the router), could you elaborate on the cases you worry about
where
> the simple policy of rollback to the last known good config does not
> converge to an acceptable state?
> > -- Albert
> >
> > Albert Greenberg
> 
> And given that there are already (large) operators that use the "see
> you on the other side, hope your configuration updated!" to do major
> changes with "reload soft" on cisco boxen, are any of these operators
> on this list and would care to comment on the nature of such changes?
> 
> -andrew



Follow-Ups:
Indexed By Date Previous: Re: CLI transactions
From: Paxton <paxton@binsh.com>
Next: Re: CLI transactions
From: Andrew Fort <andrew.fort@gmail.com>
Indexed By Thread Previous: Re: CLI transactions
From: "Georg Magschok" <gio@epygi.de>
Next: Re: CLI transactions
From: Andrew Fort <andrew.fort@gmail.com>

Google
 
Search Internet Search www.greatcircle.com