Great Circle Associates Network-Automation
(April 2005)
 

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

Subject: Re: CLI transactions
From: Juergen Schoenwaelder <j . schoenwaelder @ iu-bremen . de>
Date: Mon, 18 Apr 2005 07:39:58 +0200
To: Andrew Fort <andrew . fort @ gmail . com>
Cc: Kirby Files <ksfiles @ gmail . com>,Network Automation List <network-automation @ greatcircle . com>
In-reply-to: <7654d9d05041719376de82fb9@mail.gmail.com>
References: <425FDB2E.8080502@gmail.com> <7654d9d05041719376de82fb9@mail.gmail.com>
Reply-to: j . schoenwaelder @ iu-bremen . de
User-agent: Mutt/1.5.8i

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


References:
Indexed By Date Previous: Re: CLI transactions
From: Andrew Fort <andrew.fort@gmail.com>
Next: Re: CLI transactions
From: "Min Qiu" <mqiu@pop2pop.com>
Indexed By Thread Previous: Re: CLI transactions
From: Andrew Fort <andrew.fort@gmail.com>
Next: Re: CLI transactions
From: "Min Qiu" <mqiu@pop2pop.com>

Google
 
Search Internet Search www.greatcircle.com