Junos: Confirm a commit cleanly27 July 2018 • Posted in Networking
For years, I have loved the fact that Junos allows you to perform a
commit confirmed to apply the configuration with an automatic rollback in a certain number of minutes.
I have always believed that the only way to confirm the commit (i.e. stop the automatic rollback) was to
commit again. This creates two commits in the commit history, one containing the actual config diff, and an empty one purely used to stop the rollback. I’ve always thought that this creates a somewhat messy commit history, and confuses the use of
show | compare rollback:
However, today I learnt that a
commit check is enough to stop the rollback, and doesn’t create an empty commit! My commit histories are now much cleaner, and
show | compare rollback commands a lot easier to work out what you’re actually looking at.