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.
Copied some text-file to the flash
Saved the running-config
Changed the boot-variable to the name of "some text-file"
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:
Download the altered "some text-file" to your local PC
Make the changes you wanted in that text-file
Upload the changed "some text-file" back to ASA i.e. overwrite the existing one in flash
Reload the Device
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 ....)
Upload this file to flash
Connect via CLI
Copy the text-file to running-config (copy <name of file> running-config)
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?
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :