There are two methods for converting a non-IOS Access Point (AP) to Cisco IOS Software:
You can use the Wireless LAN Solution Engine (WLSE) web interface and create conversion jobs that you can schedule at a desired time. This method is recommended if you have a WLSE.
If you do not have a WLSE, you can download and install the Cisco Aironet Conversion Tool from Cisco.com and manually convert APs. For information on this tool, refer to the Cisco Aironet Conversion documentation on Cisco.com.
To perform the conversions using the WLSE, perform these steps:
Satisfy the prerequisites.
Configure the APs to be converted.
Configure the WLSE for Cisco IOS Software conversions.
Create a conversion template on the WLSE.
Create and run the conversion job.
Check the results.
The WLSE automatically converts most of the non-IOS configuration data to IOS-style configuration. However, certain key data are not automatically converted and must be specified as part of the upgrade job. Therefore, when you use the WLSE to convert to Cisco IOS Software, you must first define a non-IOS configuration template that includes certain parameters. This template is assigned to the devices during the upgrade process.
Note: After you convert a non-IOS AP to Cisco IOS Software, you cannot reverse the process. The AP cannot be converted back to non-IOS firmware.
I have a 2960x-48fpd-l running 15.2.2E3 connected to a 3702 AP. Port config pasted below. The AP is in local switching mode so all the clients get dropped off at the switch - hence the trunk and multiple vlans because of the various ssid's and radius over...
Hi all, There are two core routers with equal cost paths to them from the distribution switches. One core router needs to be taken down. If this is done gracefully how quickly will the distribution switches change its preferred route to use the ...
Hello everyone,,I can't seem to find decent information regarding this.DNAC can provision the underlay network, but i find no details on how it does so.Suppose i have a 3-level campus network: Access, Distribution, Core and Border nodes.The underlay deplo...
If I have two separate fabric sites separated by an IP transit, but a common VN configured in both (different subnet per site), how do I create one authorization policy in ISE for that users of that vn? When I go to create an authorization result to ...