Cisco 7604 Configuration Manual page 62

Managing the Configuration
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
FWSM 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 FWSM saves the system configuration and each context. Context startup
configurations can reside on external servers. In this case, the FWSM 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 FWSM 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:
•
•
•
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide using ASDM
3-4
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' .
Chapter 3 Connecting to the Firewall Services Module and Managing the Configuration
OL-20748-01