On Fri, Apr 15, 2005 at 11:18:06AM -0400, Kirby Files wrote:
> So, please respond with any equipment you know of, whether it supports
> transactions, either on its CLI or through an API, or even with a
> vendor-supplied NMS-system.
>
> I'll start with equipment I've seen come through the lab:
>
> Juniper JunOS: 2- and 3-phase commits on CLI and JunoScript
> Tasman Networks: none
> Alcatel 7750 SR: none on CLI; 3-phase transactions allegedly through
> expensive NMS
> Extreme: none
> ANDA Etherrearch: menu-based; no transactions
> Redback SMS: none
> Cisco IOS: In some situations, the very intrusive use of configuration
> archive could give you rollback. Yuk!
A rather frustrating collection. Without proper support by the devices,
one will never to be able to create a robust and adaptable piece of a
network configuration system.
Putting the rollback logic on the NMS is a broken concept as it requires
that the NMS knows quite a bit about the internals of the device. The
lack of proper primitives on the devices is probably the reason why NMS
software is so bloated, device specific and does provide so little
functionality (since writing all the rollback code to make things
somewhat robust and interoperable is a big pain).
/js
P.S. The rollback capability in NetConf is optional and the list above
explains quite well why.
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
Follow-Ups:
References:
|
|
