junos config commit question

Fri Feb 11 22:27:56 UTC 2022

On Fri, Feb 11, 2022 at 5:26 PM Ryan Hamel <ryan at rkhtech.org> wrote:

> If it's before committing the changes just run "top" to get back to the
> root of the configuration tree, then "rollback 0" to go back to the version
> before any changes were made, then just "exit" out.
>
> Ryan
>
>
> On Fri, Feb 11, 2022, 2:20 PM Lyndon Nerenberg (VE7TFX/VE6BBM) <
> lyndon at orthanc.ca> wrote:
>
>> On an EX4300 switch running JunOS 14.1 let's imagine I typed
>>
>>         config
>>         delete interfaces
>>
>>
you may ALSO be interested in the idea that you SHOULD be doing:
  configure exclusive
  fiddle
  fart
  oops!
  exit (safe to exit, your changes will get wiped out)

note that 'configure exclusive' means other people can't ALSO change the
config out from under you (and you have locked the config, so....)

> before coming to my senses.  How am I supposed to back out of that
>> mess?  For the life of me, after a week of reading the 3000 page
>> reference manual, and endless DuckDuckGoing, I cannot see a simple
>> way of just abandoning the commit.  I've got to be missing something
>> stunningly obvious here because it's unthinkable that this functionality
>> doesn't exist.  Help?!?
>>
>> The only way out I can see is to drop into the shell, make an
>> uncompressed copy of juniper.conf.gz, then pop back into the config
>> editor and load that over top of the editor's config view.  Surely
>> there's a saner way of dealing with this.
>>
>> --lyndon
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220211/7d1a95d8/attachment.html>