Junos OS

 View Only
last person joined: 4 days ago 

Ask questions and share experiences about Junos OS.

  • 1.  What is a commit "via button" in Junos?

    Posted 27 days ago

    I am seeing unexpected behavior whereby when upgrading SSDs on an MX router with RE-S-2X00x6 routing engines in a dual routing engines chassis configuration,  a commit "via button" is performed.   But I do not know what a commit "via button" is.  See entry #1 below:

    user@LabMX240-RE1# rollback ?
Possible completions:
  <[Enter]>            Execute this command
  0                    2025-02-18 16:00:34 EST by root via cli commit synchronize
  1                    2025-02-18 15:36:24 EST by root via button 
  2                    2025-02-18 15:33:57 EST by user via synchronize 
  3                    2025-02-18 15:31:04 EST by root via other 
  revision             Rollback to given configuration revision
  |                    Pipe through a command

    Any idea what a commit "via button" means?

    Clarke Morledge



  • 2.  RE: What is a commit "via button" in Junos?

     
    Posted 26 days ago

    Not seen this myself, but show system commit | Junos OS | Juniper Networks


    Original Message


  • 3.  RE: What is a commit "via button" in Junos?

    Posted 26 days ago

    I'm guessing "via button" means using the physical button on the device to load the rescue config. I think if you hold it for a set period of time it will load whatever config you last saved as the "rescue config".


    Original Message


  • 4.  RE: What is a commit "via button" in Junos?

    Posted 26 days ago
    That's what I originally suspected.... except for the fact that none of us here have touched the physical button on the routing engine.  Mmmmm.... still a mystery.


    Clarke Morledge
    Network Engineer
    Information Technology
    William & Mary



    Original Message


  • 5.  RE: What is a commit "via button" in Junos?

    Posted 12 days ago

    JTAC reports that this issue can happen when the SSDs are replaced, and the system automatically performs a file system check (fsck), and notices that the SSDs were in fact replaced. You must wait at least 5 minutes for the fsck procedure to complete.  Otherwise, if you commit before the fsck procedure finishes, the "root via button" procedure will automatically run; i.e. no human intervention, and wipe out any previous configuration changes, leaving you with a default config.

    Not only is the config returned back to the factory default, all of the log messages are deleted as well.

    Mystery solved.


    Original Message