Cisco ASA Series Cli Configuration Manual page 133

Chapter 1 Getting Started
Saving All Context Configurations at the Same Time
To save all context configurations at the same time, as well as the system configuration, enter the
following command in the system execution space:
Command
write memory all [/noconfirm]
Example:
hostname# write memory all /noconfirm
After the ASA saves each context, the following message appears:
'Saving context 'b' ... ( 1/3 contexts saved ) '
Sometimes, a context is not saved because of an error. See the following information for errors:
•
•
•
•
•
Copying the Startup Configuration to the Running Configuration
Copy a new startup configuration to the running configuration using one of the following options.
Purpose
Saves the running configuration to the startup configuration for all contexts
and the system configuration.
If you do not enter the /noconfirm keyword, you see the following prompt:
Are you sure [Y/N]:
After you enter Y, the ASA saves the system configuration and each
context. Context startup configurations can reside on external servers. In
this case, the ASA saves the configuration back to the server you identified
in the context URL, except for an HTTP or HTTPS URL, which do not let
you save the configuration to the server.
For contexts that are not saved because of low memory, the following message appears:
The context 'context a' could not be saved due to Unavailability of resources
For contexts that are not saved because the remote destination is unreachable, the following message
appears:
The context 'context a' could not be saved due to non-reachability of destination
For contexts that are not saved because the context is locked, the following message appears:
Unable to save the configuration for the following contexts as these contexts are
locked.
context 'a' , context 'x' , context 'z' .
A context is only locked if another user is already saving the configuration or in the process of
deleting the context.
For contexts that are not saved because the startup configuration is read-only (for example, on an
HTTP server), the following message report is printed at the end of all other messages:
Unable to save the configuration for the following contexts as these contexts have
read-only config-urls:
context 'a' , context 'b' , context 'c' .
For contexts that are not saved because of bad sectors in the flash memory, the following message
appears:
The context 'context a' could not be saved due to Unknown errors
Working with the Configuration
Cisco ASA Series CLI Configuration Guide
1-25