I am trying to figure out about using multiple time "commit confirmed" command.
First I added only one statement into the current configuration and then I did "commit confirmed". While CLI prompt pointing that rollback in 4 minutes, I did add second a different statement and then I did again "commit confirmed 15". In order to get more time I did third time "commit confirmed 20"...
After my test on new added two statement, Junos said rollback will be in 4 mins. After 4 mins, Junos prompt pointed that rollback completed.
But after that when I checked the configuration, two newly added statements were still there! Can I ask about why junos didn't do rollback?
But still I have a question....! How to extend the timer of "commit confirmed"?
First I did a small change and then performed "commit confirmed 3". After executing that I released that 3 mins is not enough and some other reasons I need more time for my further troubleshooting. In this case, how to extend commit confirmed time? If there is no any way to extending timer of commit confirmed, what you guys are typically doing?
There is no way to extend the timer during the rollback countdown. It is meant to serve as an insurance in case you lose access to the device after the commit. Hence does not have any such mechanism.
If you have not lost device access after the commit confirmed, I would just commit the changes to stop the timer. You can start a fresh rollback timer before the next set of changes/for the next commit.