How do you load an ASA config from flash?

[jimmyc_2]

I have 5500s, both 7.2, 8.2, and 8.4.

What are the commands to load a file in flash into the running-config at startup?

I don't want the startup file.

I tried the  boot config flash:/saved_config, but it is not working.

I'm guessing I need to change the config-reg, but it's a bit confusing.

thanks.

[Julio Carvajal · Accepted solution]

Hello Jimmy,

So you want to set a file for the next time the ASA boots

boot config flash://test.cfg

Configuring the File to Boot as the Startup Configuration

By default, the ASA boots from a startup configuration that is a hidden file. You can alternatively set any configuration to be the startup configuration by entering the following command:

hostname(config)# boot config {disk0:/ | disk1:/}[path/]filename

For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com

Any question contact me at jcarvaja@laguiadelnetworking.com

Cheers,

Julio Carvajal Segura

[jimmyc_2]

Thanks Julio,

I notice two slashes e.g.  "flash://test.cfg"

The text books say one slash?  

What am I missing?

jc

[jimmyc_2]

I found the missing concept.   When you use the boot config command, then any "copy run start" command overwrites the file in flash that was specifed, as well as the startup config.  Very odd.

[FlorianCokl]

Hey JimmyC :)

Actually - not odd. Usually the startup-config is NOT visible on the ASA. Once you set the boot variable (either through CLI or ASDM) the startup-config becomes "just visible" in flash.

I recently had a similar situation - needed to change IP-Adresses and routing on the outside interface of an ASA without having access to the console - just SSH and or ASDM. Here is what I've found out - what I did.

1. Copied some text-file to the flash
2. Saved the running-config
3. Changed the boot-variable to the name of "some text-file"
4. Saved the running-config

Now - the "some text-file" in flash would be overwritten with the actual running-config of the ASA - ok.

Try this at home with an ASA you have access to via console-cable! Lets do the following:

1. Download the altered "some text-file" to your local PC
2. Make the changes you wanted in that text-file
3. Upload the changed "some text-file" back to ASA i.e. overwrite the existing one in flash
4. Reload the Device
5. Watch carefully the CLI!

What your going to see - well - forget what you see through the boot process. The more interesting part is: will my changes come into play i.e. will I see them now in the running-config?! No I won't! Why? There's this little innocent line at the end of your startup-config "..crypto checksum.."

What could you do instead? Well - create a text-file with exactly the commands you need, to change, what you want to be changed. In my case change interface configuration of the outside and routing (no route.. and route ....)

1. Upload this file to flash
2. Connect via CLI
3. Copy the text-file to running-config (copy <name of file> running-config)
4. Hope that you hadn't made a mistake ;-)

I thought that the running-config would be overwritten - hm - it's merging, to be true. The ASA would only alter the parts of running-configuration that I had mentioned in the file I had uploaded to flash and copied to running-config.

That's how I did it - hope it helps clear out the skys?