Junos OS

Would anyone please like to share their list of pre and post check commands which are normally run prior to (and after), making changes.

Production environment obviously.

Thanks in advance !

The specifics would depend on the network topology, the type of change and what protocols are running in the environment.

If you are interested in more automated solutions then the jSnapy tool may be of interest.

https://forums.juniper.net/t5/Day-One-Books/Day-One-Enabling-Automated-Network-Verifications-with-JSNAPy/ba-p/302104

For any changes in terms of configuration. ensure that there are no other operator(s), making any configuration changes (at config mode). Enter using "configure exclusive" mode so that other users can enter and exit configuration mode, but they cannot commit the configuration. 

Pre and Post show commands really depend on type of configuration change you attempt to make.

The one common command for pre check is "show | compare" command which is after you input your desired configurayion but before the "commit" operation, so that you know what is exact pre-config you added and about to commit.

Post check command of that commit config is "show | compare rollback x" (in config mode) or show config | compare rollback x". 

"x" represents the number of pre-committed configs ranging from last "0 to 50".

The gerenal practise for production pre & post confiiguration changes:

1. Input the desired config -> check "show | compare" This indicates the configure you about to commit and also the changes (in + or -) that are replaced/added.
2. "commit check" -> Verify the syntax of the configuration, but do not activate it.
3. commit confirm 5-> require that the commit be confirmed within the specified amount of time. In this example, its 5 mins. If the commit is not confirmed within the time limit, the configuration rolls back automatically.
4. commit the configure "commit".

commit check /confirm are optional but are useful & safe for production commits.

Other check commands specfically depends on type of configuration.

Additionally, for the general show commands, collect the RSI (request support information | no-more) pre and post the configuration which includes all basic & some if advance general show command output followedby the suggestion i recommend in my previous post!