#sh run all cmd or the #sh run cmd.

[franklinbrown749628471]

I just learned something today. When I look at the file size for the same config using the #show run all" cmd .The file is almost 4 times larger than a #show run" cmd. There is a ton of extra stuff going down under the radar. Try a sh run all cmd and you will be amazed. Now what does this mean when you are trying to back up or restore a switch with notepad? It is probably not going to work. I have been working in a lab environment practicing restoring a Cat 4500 switch in case of an emergency. Copy and pasting large configs is introducing multiple errors. TFTP has been full of  can't find the file, socket problems, etc.  I wonder how you take a network of 10 switches with large configs and make it all work from scratch. Does Cisco have basic scripts they run when they sell a new switch that are developed for each implemntation?

[Flavio Miranda]

Hi @franklinbrown749628471 

 Not sure if you got you but I will try to say how I do to extract configuration from cisco device dont matter the size.

Open up a SSH session and run the command terminal lenght 0. Then, configure your SSH program to save the file somewhere on the PC.

Then run the command you want to take the output from. It does not matter which command.  For example, Wireless Lan Controller output can get easilly at 100MB Txt file)  file for large WLC. Switch dont go far from 1 MB even large ones.

" I wonder how you take a network of 10 switches with large configs and make it all work from scratch. Does Cisco have basic scripts they run when they sell a new switch that are developed for each implemntation?"

 The configuration, for more complex it can be, is built step by step. Not all parameter is placed there by the admin. The device comes with a basic config and what you do is edit the configuration based on your environment.

You can also take the config from similar device and edit the required parts.

[David Ruess]

Hello,

The show run all command is a lot of extra output as you mentioned. It shows the defaults as well as any other entered command. If you are backing up and restoring the same devices they will have the same default config. In this case there is no need to copy the whole 'show run all' command over. 

If you are backing up one device and trying to transfer to another device then you can run into issues as all devices don't have the same default config.

An example of a default config:

If you enable a routing protocol (at least not on much older devices) then by default the no auto-summary command is configured.

If you run the show run after enabling a routing protocol you will not see the no auto-summary under the routing process.

If you issue the show run all command then you will see it as its a default staple in the config

Hope that helps

-David

[franklinbrown749628471]

I have had a breakthrough of sorts. I went on our live network copied the running config (switch#copy running-config tftp:), and then verified it was in the tftp root.  I then took the tftp laptop plugged it into the first port on my lab cat 4500 switch. I opened the config file in the tftp root folder removed the config for 2 blades not installed on that switch. I then configured a static IP (10.0.0.2 255.0.0.0) on the laptop and int vlan 1 (10.0.0.1 255.0.0.0) on the switch. I was able to ping my tftp server now. I successfully copied a 100kb config on the cat 4500 using the (switch#copy tftp: running-config) cmd. I used putty to copy sh run and sh run all notepads. I compared them and realized that that there are more sub commands happening in the background by default. I have had a CCNA for 3+ years and watched at least 4 different CCNA courses on UDEMY and never had this mentioned or explained. I started this conversation to bring some clarity to a new CCNA / rookie like myself.  Thanks for everyones help.