Hi,
I am not sure if you are actually asking about 2 different things here.
If you have an existing Security Context configured in the System Context space of the ASA then to change the Security Context name I think you would have to do the following things during maintanance break
- Create new Security Context with the desired name
- Allocate the same interfaces to the Security Context than in the original
- Remove the original Security Context
- Only now add the existing actual firewall configuration file to the the new Security Context with the "config-url" command so it loads the same original configuration
That to my understanding could be the steps needed for the change of the Security Context name in the System Context space. Naturally it causes outage to the services when you have to remove the Security Context and make it again.
I presume that you should first remove the old Context before adding the configuration to the new Context as otherwise the ASA would probably ignore commands when loading the configuration into the Context as there would be shared interfaces on the ASA with the same IP addresses.
You also talk about having a template for new firewalls. I guess in this case you are better of creating a new blank Context and copy/paste its configuration to some text editor software you use and start building the base Context configurations from that.
When you have a configuration template that applies to all firewalls you could then probably copy this file to the ASA flash and then make a copy of that file with a new file name on the Flash and then assign that file as the configuration source for the new Context.
I don't think you can use the same file for each of your Contexts. You will have to copy the base configuration file to its own file and upload it to the ASA Flash and assign it to the new Context when you create one. Naturally the interfaces IDs will be different in most if not all Contexts so you can't really create a template for those.
- Jouni
