SRX

Hi all,

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?  

commit confirmed do rollback only for last "commit confirmed"

Your second and third "commit confirmed" confirm first and second "commit confirmed"

Hi Arix,

Your 2nd/3rd and n "commit confirmed" will add the time and not rollback at 1st commit confirmed time (4 min in your case).

Plus the 2nd commit confirmed will commit the last commit confirmed and will leave the one which did not recieve the commit.

Test from Lab:-

++++++++++

[edit]
root@a1# set system host-name z1

[edit]
root@a1# commit confirmed 2
commit confirmed will be automatically rolled back in 2 minutes unless confirmed
commit complete

# commit confirmed will be rolled back in 2 minutes
[edit]
root@z1# set system login user z1 class super-user

# commit confirmed will be rolled back in 1 minute
[edit]
root@z1# commit confirmed 2
commit confirmed will be automatically rolled back in 2 minutes unless confirmed
commit complete

# commit confirmed will be rolled back in 2 minutes
[edit]
root@z1# set system login user z2 class super-user

# commit confirmed will be rolled back in 1 minute
[edit]
root@z1# commit confirmed 2
commit confirmed will be automatically rolled back in 2 minutes unless confirmed
commit complete

# commit confirmed will be rolled back in 2 minutes
[edit]
root@z1#

# commit confirmed will be rolled back in less than 1 minute
[edit]
root@z1#

# commit confirmed will be rolled back in less than 1 minute
[edit]

Broadcast Message from root@z1
(no tty) at 10:39 UTC...

Commit was not confirmed; automatic rollback complete.

[edit]
root@z1#

[edit]
root@z1#

[edit]
root@z1#

[edit]
root@z1#

[edit]
root@z1# show | display set | match user
set system login user z1 uid 2002
set system login user z1 class super-user

<---- You do not see z2

Regards,

Rahul

each commit confirmed commits the changes of the previous one and rolls back the changes pertaining to the "current" commit confirmed.

Another tip when the timer is counting down a commit check swiftly commits your changes.

hope that helps!

Arix,

In a nutshell, let say you've given commit confirmed consecutively for 3 times; only the 3rd change will get rolled back while the 1st two gets committed.

Hello Arix,

Any command starting with "commit" issued after a "commit confirmed" while the timer has not expired yet, will commit the configuration.

Best example is "commit check" .

Thanks!

Thanks all, I appreciated your answers...

But still I have a question....!  How to extend the timer of "commit confirmed"?

For instance,

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? 

I usally only use commit confirmed if I expect to lose external connectivity to the site or produce some other issues which might cause the device to be unmanageable. 

If you need more time for troubleshooting and still have OAM access to all devices necessary I would just confirm the commit. 

You can do a "rollback" at any time if you deem it necessary. 

Cheers,

Hello,

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.

Regards,

Vikas

HI Arix,

No way to increase as mentioned, its only the rollback "n" that will revert,  here is an example:- 

{secondary:node1}
root@jtac-srx> configure
warning: Clustering enabled; using private edit
warning: uncommitted changes will be discarded on exit
Entering configuration mode

{secondary:node1}[edit]
root@jtac-srx# set system host-name abc

{secondary:node1}[edit]
root@jtac-srx# commit confirmed 2

node1:

configuration check succeeds
commit confirmed will be automatically rolled back in 2 minutes unless confirmed
node0:
commit complete

commit confirmed will be automatically rolled back in 2 minutes unless confirmed

node1:
commit complete

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]   << (change got committed and awaits 2 min to get a commit or else rollbacks)
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc#

# commit confirmed will be rolled back in 2 minutes

{secondary:node1}[edit]
root@abc# rollback 1
load complete

# commit confirmed will be rolled back in 1 minute

{secondary:node1}[edit]
root@abc# show | compare   <<< shows the change (commit will remove the said change rather than add)
[edit system]
- host-name abc;

# commit confirmed will be rolled back in 1 minute
{secondary:node1}[edit]
root@abc# commit
node1:
configuration check succeeds
node0:
commit complete
node1:
commit complete

{secondary:node1}[edit]
root@jtac-srx#   <<<< Hostname did not change