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
Follow-Ups:
References:
|
|
