junos config commit question

Sat Feb 12 09:46:45 UTC 2022

Not long enough to have drive to the DC in the middle of the night :) 

Even "commit confirmed x" is a shield, a better one. 

Regards 
Paschal Masha | Engineering 
Skype ID: paschal.masha 

From: "Dale Shaw" <dale.shaw+nanog at gmail.com> 
To: "Mark Tinka" <mark at tinka.africa> 
Cc: "nanog" <nanog at nanog.org> 
Sent: Saturday, February 12, 2022 12:39:28 PM 
Subject: Re: junos config commit question 

Hey Mark, 

On Sat, 12 Feb 2022 at 8:25 pm, Mark Tinka <mark at tinka.africa> wrote: 

I have often found it interesting how many folk have muscle memory for 
"commit and-quit", including Juniper's own staff when I've had the 
pleasure of being with them on a PoC. It's almost as if I missed an 
entire period of Junos where that was deemed to be good practice :-). 

That’s definitely a practice guaranteed to result in needing to drive to the DC. 

I wonder if it creeps into some folks’ MO because the control plane on many platforms is soooooo slow to commit. Many don’t know that a “commit check” is sufficient to confirm a commit, but even that can take a long time. 

Cheers, 
Dale 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220212/21328795/attachment.html>