Great Circle Associates Network-Automation
(April 2005)
 

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

Subject: Re: CLI transactions
From: James Dollar <jdollar @ uplogix . com>
Date: Mon, 18 Apr 2005 16:04:07 -0500
To: <j . schoenwaelder @ iu-bremen . de>, Min Qiu <mqiu @ pop2pop . com>
Cc: Andrew Fort <andrew . fort @ gmail . com>,Kirby Files <ksfiles @ gmail . com>,Network Automation List <network-automation @ greatcircle . com>
In-reply-to: <20050418164144.GA12530@boskop.local>
User-agent: Microsoft-Entourage/11.1.0.040913

Title: Re: CLI transactions
Guys,

My company’s network management appliance (The Uplogix Envoy) builds that kind of transactional wrapper around ad-hoc changes made via the device’s console for Cisco, Tasman, and Nortel.  It takes a snapshot of the running environment before and after a user makes a change and creates a rollback procedure necessary to return the running configuration back to the previous state. It subtracts the additions and adds back the subtractions to minimize the impact on other device functions.  (For Juniper we use Juniper’s built-in functionality)

It applies this “rollback configuration” if the user does not commit the change within a definable timeout (default 75 seconds) - automatically restoring changes that otherwise may have isolated the device from the user management session.  It may also be applied at any time after a commit, as we store 20 versions of the rollback.

j$
GM, Products
Uplogix



From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
Reply-To: <j.schoenwaelder@iu-bremen.de>
Date: Mon, 18 Apr 2005 12:41:44 -0400
To: Min Qiu <mqiu@pop2pop.com>
Cc: Andrew Fort <andrew.fort@gmail.com>, Kirby Files <ksfiles@gmail.com>, Network Automation List <network-automation@greatcircle.com>
Subject: Re: CLI transactions

On Mon, Apr 18, 2005 at 11:37:24AM -0400, Min Qiu wrote:

> 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.

Juniper supports confirmed commits. After a change has been put
into action, you have to get back to the device to commit the change
or otherwise the box rolls back. This is very cool since in case of
a broken transaction, you simply wait for the boxes to roll back
into the previous state. This is especially cool if the change locks
you out of the network. Confirmed commits are another optional
capability of the netconf protocol.

/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: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
Next: Re: CLI transactions
From: Daniel Hagerty <hag@linnaean.org>
Indexed By Thread Previous: Re: CLI transactions
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
Next: Re: CLI transactions
From: "Min Qiu" <mqiu@pop2pop.com>

Google
 
Search Internet Search www.greatcircle.com