Sure, but the post I replied to originally was someone stating that commit confirm is problematic when you forget the second commit. I was explaining the easy way to recover from that scenario and it then got taken out of context… Twice now. Owen
On Feb 16, 2022, at 19:54 , Paschal Masha <paschal.masha@ke.wananchi.com> wrote:
edit rollback 0 commit
"rollback 0" discards all your recent changes to the candidate configuration, include "delete interfaces". If you "rollback 0" then run "show | compare" no output will be displayed, meaning your changes have been discarded. Don't run "commit confirm x" when the change is "delete interfaces"
Regards Paschal Masha | Engineering Skype ID: paschal.masha
-----Original Message----- From: "Owen DeLong via NANOG" <nanog@nanog.org> To: "Jay Hennigan" <jay@west.net> Cc: nanog@nanog.org Sent: Thursday, February 17, 2022 01:14:08 AM Subject: Re: junos config commit question
Then you didn’t use “commit confirm” as in the post this replied to.
Owen
On Feb 16, 2022, at 12:23, Jay Hennigan <jay@west.net> wrote:
On 2/16/22 09:56, Owen DeLong via NANOG wrote:
You can also do: config <do something stupid> commit rollback 1 commit
Unless you're remote and <do something stupid> breaks your ability to reach the box. Then you're hosed after the first "commit".
-- Jay Hennigan - jay@west.net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV