This works fine but it is a bit of a hassle going to all that trouble and it means you have to connect the switch to the network, so you have to be very careful with things like VTP and spanning tree. I found the best way around this problem was to set up the device with an IP address, put it on a limited access network that has a TFTP sever and copy over the configuration file, either to the startup-config or running-config. Now while if you only have a small size configuration file this is not an issue as it is quite easy to check, hundreds of lines become very hard to validate. I could see that while things like VLAN’s where being created and the device was pausing, the following lines would some times get lost or corrupted. With really large configuration files (500+ lines of configuration), I was watching the console windows and could see it was skipping some of the configuration when doing this connected through the serial port. However I was doing this today and hit an issues. Ctrl-A to select it all, copy and paste to the device. In the past this is also how I have always copied backed up configurations on to a new switch/router.

set up one interface, copy the config to notepad, update it as you wish and past it back in… A real time saver and why we all love CISCO more than Microsoft ). One of the things every one seems to love about CISCO is the fact you can simple copy and past configurations in to the terminal emulator window. However I came across something today, that I have known about for a while but never really used much. I have still been doing a bit of study and planing some more ROUTE posts, but with a broken down car and house sale looking like its falling through haven’t had time to do any actually real posting. Last week at work now, so been rushing to get things sorted out.

Xmodem terminal