PDF(69.1 KB) View with Adobe Reader on a variety of devices
ePub(105.5 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(177.2 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 14, 2018
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Clear Configuration Files on the Wireless Access Point (WAP)
Configuration files are cleared because the files may get corrupted when a test is performed or if the previous configuration files need to be reloaded in order for the device to work properly.
When a device is turned on, the Startup Configuration file is created while it is booting up. If the Startup Configuration file is cleared, the Backup Configuration file becomes active the next time the device is rebooted.
For example, the Wireless Access Point (WAP) needs to revert to its previous configuration for it to work properly again. In order to achieve this, the Startup configuration file has to be cleared so that the previous configuration that has been saved in the Backup Configuration files can be reloaded when the WAP reboots.
Note: If the Backup Configuration file is cleared, you need to create a new backup file. To learn how, click here.
This article explains how to clear configuration files such as Startup and Backup configuration files on the Wireless Access Point.
22.214.171.124 — WAP121, WAP321
126.96.36.199 — WAP131, WAP351
188.8.131.52 — WAP150, WAP361
184.108.40.206 — WAP371
220.127.116.11 — WAP551, WAP561
18.104.22.168 — WAP571, WAP571E
Clear Configuration Files
Note: It is highly recommended to refrain from creating unnecessary configuration files since it would consume more memory space.
Step 1. Log in to the access point web-based utility and choose Administration > Configuration Files Properties.
Note: If you are using WAP131, WAP150, WAP351, or WAP361, choose Administration > Manage Configuration File.
In the Configuration Files Properties area, the Configuration File Table displays the following information:
Configuration File Name — The name of the configuration file. Up to three configuration files are available:
- Startup Configuration — The configuration file saved to flash memory. This file is kept in the NVRAM and the contents are retained after a reboot.
- Backup Configuration — An additional configuration file saved on the access point for use as a backup.
- Mirror Configuration — If the Running Configuration is not modified for at least 24 hours, it is automatically saved to the Mirror Configuration file, and a log message with severity alert is generated to indicate that a new Mirror Configuration is available. This feature allows the administrator to view the previous version of the configuration before it is saved to the Startup Configuration file type or to copy the Mirror Configuration file type to another configuration. The Mirror configuration is preserved even after a reboot. If the device is not able to boot with startup or backup then it uses mirror configuration to boot.
Creation Time — The time the configuration file was created.
Note: The Running Configuration file is now shown because it cannot be cleared.
Step 2. Check the check box beside the configuration file that you wish to be cleared in the Configuration File Table.
Step 3. Click Clear Files to clear the configuration file.
Step 4. Click OK in the confirm window to continue.
Step 5. An Alert window will display confirming that the chosen configuration file has been deleted. Click OK.
You should now have successfully cleared the desired configuration file from your access point.