Wireless Edge Services zl Module Release Notes WT.01.39

2
Software Management
Saving Configurations
Saving Configurations
The module operates with two configuration files:
■ Running-Config File: Exists in volatile memory and controls module operation. Rebooting the module erases the
current running-config file and replaces it with an exact copy of the current startup-config file. To save a configuration
change, you must save the current configuration in the running-config file to the startup-config file.
■ Startup-Config File: Exists in flash (non-volatile) memory and preserves the most recently-saved configuration as
the “permanent” configuration. When the module reboots for any reason, an exact copy of the current startup-config
file becomes the new running-config file in volatile memory.
In the wireless-services context of the CLI, you may use the write memory command to save changes made to the running-
config file to the startup-up config file. Also, the system prompts you to save any unsaved changes when you leave the wireless-
services context.
Saving the Current Configuration as the Start-Up Configuration
When you use the CLI to make a configuration change, the module places the change in the running-config file. If you want
to preserve the change across reboots, you must save the change to the startup-config file. Otherwise, the next time the module
reboots, the change will be lost.
To save configuration changes while using the CLI:
1. From the wireless-services context:
Switch E5406zl(wireless-services-B)#write memory
[OK]
Switch E5406zl(wireless-services-B)#
2. Verify that the [OK] message displays, indicating that the configuration was saved successfully. The current configuration
is now saved as the startup configuration file, and the module will execute the file at each power-up.
See the module’s Management and Configuration Guide (5991-8626) for more information on managing module configuration
files.