I did not read any of the replies in order not to get biased. So:
1) Yes, if by "session" you mean what I will describe in point 2. Otherwise, no.
2) I know the "session" concept from Arista. You create a session, configure all the changes without committing them, and at a later point you can either commit all at once into the running config, or discard all your changes by deleting your session.
3) If we're talking about the same thing, it would be nice to be able to have automated roll-backs if after let's say 5 minutes after a session commit you don't ack the change is OK (meaning you lost conectivity - so something is wrong => auto rollback)
4) for me yes, but I might be wrong here.
5) After reading a bit through the posts, it turns out sessions are something completely different than what I had in mind...so nevermind!
1) Yes, if by "session" you mean what I will describe in point 2. Otherwise, no.
2) I know the "session" concept from Arista. You create a session, configure all the changes without committing them, and at a later point you can either commit all at once into the running config, or discard all your changes by deleting your session.
3) If we're talking about the same thing, it would be nice to be able to have automated roll-backs if after let's say 5 minutes after a session commit you don't ack the change is OK (meaning you lost conectivity - so something is wrong => auto rollback)
4) for me yes, but I might be wrong here.
5) After reading a bit through the posts, it turns out sessions are something completely different than what I had in mind...so nevermind!
Statistics: Posted by dot02 — Thu Feb 01, 2024 2:23 am