Lessons · Network switches · the order a restore goes in
Check, restore, verify, then save
Saving is the last step of a swap, and it is last on purpose: until you write it, a reload is a free undo.
Hone is a place to practise programming. This is one of its lessons, written out in full and free to read without an account.
What it is for
A restore that is wrong in a way you cannot immediately fix is recoverable while nothing has been saved. Save first and the half-finished restore becomes what the switch boots as.
How to think about it
Check the new box's software and ports, put the configuration on, read it back, and only then write it to startup-config.
Worked example
enableIn, on the replacement.
show versionWhat it runs, and how many ports it has.
show inventoryWhich box this is, for the ticket.
configure terminalStand in for the restore.
hostname IDF3As if the file had landed.
endOut.
show running-config | include hostnameRead it back before committing to it.
copy running-config startup-configAnd only now, save.
Your turn
Commit the verified configuration so the switch boots as it.
copy running-config
Console into a switch
The trap
Saving as you go. It is a good habit everywhere except the twenty minutes when you are still finding out whether it worked.