On 4/16/05, Kirby Files <ksfiles@gmail.com> 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.
Alteon: none
Foundry: none
Enterasys/Riverstone: none
...
Need we go on.
Obviously, for us to build a tool people will feel comfortable using,
we need some method of backing out of changes. We have devices which
don't support anything, and we have Juniper.. (or the alcatel api)..
What then? Do we support levels of "default blah" on cisco? For the
cisco-like CLIs that don't provide any way to get a known state (i.e.,
you can "no" things, but the semantics of "no" are not always the
same, e.g. across version changes, etc), what do we do?
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.
Any other options?
-andrew
Follow-Ups:
References:
|
|
