Saving Configuration Changes In Single Context Mode; Saving Configuration Changes In Multiple Context Mode - Cisco FirePOWER ASA 5500 series Configuration Manual

Chapter 2 Getting Started
•

Saving Configuration Changes in Single Context Mode

To save the running configuration to the startup configuration, enter the following command:
hostname# write memory
Note The copy running-config startup-config command is equivalent to the write memory command.

Saving Configuration Changes in Multiple Context Mode

You can save each context (and system) configuration separately, or you can save all context
configurations at the same time. This section includes the following topics:
•
•
Saving Each Context and System Separately
To save the system or context configuration, enter the following command within the system or context:
hostname# write memory
The copy running-config startup-config command is equivalent to the write memory command.
Note
For multiple context mode, context startup configurations can reside on external servers. In this case, the
security appliance 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.
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:
hostname# write memory all [/noconfirm]
If you do not enter the /noconfirm keyword, you see the following prompt:
Are you sure [Y/N]:
After you enter Y, the security appliance saves the system configuration and each context. Context
startup configurations can reside on external servers. In this case, the security appliance 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.
After the security appliance 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:
•
OL-10088-01
Saving Configuration Changes in Multiple Context Mode, page 2-7
Saving Each Context and System Separately, page 2-7
Saving All Context Configurations at the Same Time, page 2-7
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
Cisco Security Appliance Command Line Configuration Guide
Working with the Configuration
2-7