Lessons · Network switches · saving it, last
Save last, and mean it
Everything you have done lives in memory. The switch boots from a different file, and until you copy one onto the other, a reload undoes the whole evening.
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
That is also the reason to wait. Before you save, a reload is a free undo. After it, the state you would return to is the one you just wrote.
How to think about it
Verify first -- VLANs, ports, reachability -- and save when there is nothing left you would want to take back.
Worked example
enableIn.
configure terminalConfiguring.
hostname CLOSET-3A change, in memory.
endDone.
show startup-configRefused, and the refusal is the lesson: there is nothing saved to show.
copy running-config startup-configFrom the live one, to the one that boots.
show startup-config | include hostnameNow it exists, and the name is in it. That is what survives the power cut.
Your turn
Save the running configuration so it survives a power cut.
copy running-config
Console into a switch
The trap
Saving as you go. Everywhere else that is a good habit; during the twenty minutes you are proving a restore it throws away your undo.