<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000"><div>More like driving with the hand break still engaged.</div><div><br></div><div data-marker="__SIG_PRE__">Always, after changing the candidate config, run " show | compare" - loving junos.<br><br>Regards <br>Paschal Masha | Engineering <br>Skype ID: paschal.masha <br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Mark Tinka" <mark@tinka.africa><br><b>To: </b>"nanog" <nanog@nanog.org><br><b>Sent: </b>Saturday, February 12, 2022 12:23:09 PM<br><b>Subject: </b>DMARC ViolationDKIM ViolationRe: junos config commit question<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">On 2/12/22 00:54, Jon Lewis wrote:<br><br>><br>> Also, get into the habit of never doing a commit without first doing<br>> top show | compare<br>> so you can see what your change is actually doing to the whole config. <br>> i.e. if you did a show | compare at the top of the config and saw the <br>> entire interfaces section of the config was "removed" in the resulting <br>> config diff, you probably wouldn't commit.<br><br>That is always my habit, with plenty of muscle memory... "show | compare".<br><br>I have often found it interesting how many folk have muscle memory for <br>"commit and-quit", including Juniper's own staff when I've had the <br>pleasure of being with them on a PoC. It's almost as if I missed an <br>entire period of Junos where that was deemed to be good practice :-).<br><br>Mark.<br></div></div>
<br><html><body bgcolor=#FFFFFF lang=EN-US link=#339933 text=#000000 vlink=#996600><img src=http://zuku.co.ke/es/sig_img.jpg></body></html>
<br></body></html>