This article explains how to convert a local or remote Autonomous / Standalone Cisco Aironet Access Point to Lightweight and register it to a Cisco WLC Controller. Included are detailed steps, commands, full text logs of the conversion process and screenshots to ensure an easy and successful upgrade - WLC registration.
Converting an Autonomous AP to Lightweight Mode is a straight forward process however it is important to keep a few things in mind before performing the conversion procedure as there are some restrictions users should be aware of.
Depending on the level of experience some of these notes/restrictions might be considered basic or redundant knowledge. For sake of simplicity we are presenting them in bullet format:
- All Cisco lightweight access points are capable of supporting up to 16 BSSIDs per radio and a total of 16 WLANs per access point.
- Access points converted to lightweight mode require a DHCP server to obtain an IP address and discover the WLC via DNS or IP broadcast.
- Lightweight access points do not support Wireless Domain Services (WDS). All lightweight APs communicate with the WLC.
- Lightweight AP console port provides read-only access to the AP.
Before we begin the conversion process it is necessary to download the CAPWAP software file that matches the Access Point to be converted. These files can be downloaded from Cisco’s website and usually require an active Smartnet contract. Alternatively, a search on the web might reveal other sources from which they can be downloaded.
There are two type of AP CAPWAP software files we can download and install:
- Fully functional CAPWAP Image file (full image) – Identified by the k9w8 string in their filename and are usually large in size (10-20Mb). Once loaded, the AP is able to join the WLC and download its configuration. Example file name: ap3g1-k9w8-tar.152-4.JB6.tar
- Recovery mode CAPWAP Image file – Identified by the rcvk9w8 string in their filename. These are smaller in size (5-8Mb) and used to help the AP boot and join the controller so it can then download the full image from the WLC. Example filename: ap3g1-rcvk9w8-tar.152-4.JB6.tar
Regardless of the type of image loaded during the conversion process, the AP will always download the full image from the WLC as soon as it joins. The only exception to this rule is when the fully functional CAPWAP image file loaded on the AP is the same version as the one contained in the WLC.
First download a fully functional or recovery mode CAPWAP file suitable for the AP model. In our example we will be converting a Cisco 3502 AP and decided to download the appropriate recovery mode file: ap3g1-rcvk9w8-tar.152-4.JB6.tar.
Since the AP will automatically download the full image from the WLC once it joins, using the recovery mode file will speed up the conversion process.
We’ll need to have a FTP server running so we can configure the AP to download the file from it.
STEP 1: Power up the Autonomous AP & Configure a FTP server form where the AP will download the image
STEP 2: Connect the Autonomous AP to a network switch or directly to the workstation serving the AP image via a FTP server.
STEP 3: Configure the AP with an IP address appropriate for the network or set it to DHCP
In our example we configure the AP to obtain its IP address from a DHCP server:
ap(config)# interface bvi1
ap(config-if)# ip address dhcp
*Mar 1 00:27:53.248: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.2.83, mask 255.255.255.0, hostname ap
The AP confirms once it has successfully obtained an IP address from the DHCP server.
Note: BVI interface indicates that the Radio interface (e.g Dot11Radio0) and Ethernet interface (e.g GigabitEthernet0) are bridged (bridge-group x). If this is not your case, apply the configuration to the AP’s Ethernet interface.
STEP 4: Configure the AP with the FTP user account credentials as configured on the FTP server. This will allow the AP to access and download the image file. Once configured, begin the software download procedure using the archive download-sw command.
Here is the complete text log of the procedure:
ap# configure terminal
ap(config)# ip ftp username admin
ap(config)# ip ftp password cisco1234
ap# archive download-sw /force-reload /overwrite ftp://192.168.2.61/ap3g1-rcvk9w8-tar.152-4.JB6.tar
Mar 1 00:30:46.348: %SYS-5-CONFIG_I: Configured from console
Mar 1 00:30:50.563: Loading ap3g1-rcvk9w8-tar.152-4.JB6.tar
extracting info (264 bytes)!
Version Suffix: rcvk9w8-
Image Name: ap3g1-rcvk9w8-mx
Version Directory: ap3g1-rcvk9w8-mx
Ios Image Size: 123392
Total Image Size: 7936512
Image Feature: WIRELESS LAN|LWAPP
Image Family: AP3G1
Wireless Switch Management Version: 188.8.131.52
MwarVersion:07066400.First AP Supported Version:07000000.
Image version check passed
*Mar 1 00:30:46.348: Loading ap3g1-rcvk9w8-tar.152-4.JB6.tar
ap3g1-rcvk9w8-mx/ (directory) 0 (bytes)
extracting ap3g1-rcvk9w8-mx/ap3g1-rcvk9w8-mx (121199 bytes)
extracting ap3g1-rcvk9w8-mx/ap3g1-boot-m_upg (393216 bytes)!!
extracting ap3g1-rcvk9w8-mx/u-boot.bin (393216 bytes)!
extracting ap3g1-rcvk9w8-mx/ap3g1-rcvk9w8-xx (7016987 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!
extracting ap3g1-rcvk9w8-mx/info (264 bytes)
extracting ap3g1-rcvk9w8-mx/file_hashes (712 bytes)
extracting ap3g1-rcvk9w8-mx/final_hash (141 bytes)
extracting ap3g1-rcvk9w8-mx/img_sign_rel.cert (1375 bytes)
extracting ap3g1-rcvk9w8-mx/img_sign_rel_sha2.cert (1371 bytes)!
extracting info.ver (264 bytes)
[OK - 7946240/4096 bytes]
Deleting target version: flash:/ap3g1-rcvk9w8-mx...done.
Deleting current version: flash:/ap3g1-k9w7-mx.153-3.JF5...
Set booting path to recovery image: ''...done.
New software image installed in
Writing out the event log to flash:/event.log ...
Configuring system to use new image...done.
Requested system reload in progress...
archive download: takes 221 seconds
*Mar 1 00:34:31.088: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to IOS reload
*Mar 1 00:34:31.088: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to IOS reload
*Mar 1 00:34:31.094: %SYS-5-RELOAD: Reload requested by Exec. Reload Reason: Reason unspecified.
The /force-reload parameter will automatically reload the AP as soon as the new software image is installed while the /overwrite parameter is required to replace the autonomous image with the CAPWAP image.
Console cable can be used for the conversion process of local APs. Alternatively SSH/Telnet can be used for the conversion of both local and remote APs.
Once the CAPWAP image has been successfully loaded on the AP it reload and begin searching to register with a WLC Controller. As soon as the AP successfully registers with the WLC it will compare its image with that of the controller and if found different begin to download and install it.
It is important to ensure there is an active DHCP server on the same VLAN/network as the AP to provide it with an IP address, subnetmask, gateway and DNS parameters. DNS parameters are not mandatory but will speed up the WLC discovery processes if the DNS server contains an “A Type” resource record of “CISCO-CAPWAP-CONTROLLER” pointing to the WLC’s IP address.
In the logs below we can see our AP searching for the WLC (Translating "CISCO-CAPWAP-CONTROLLER"...domain server) after its initial reload (we’ve just installed recovery mode image). It then discovers the WLC (both WLC and AP are on the same VLAN), registers and downloads the WLC full CAPWAP image:
Click to enlarge
Mar 1 00:00:41.806: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C3560CX-12PC-S (0076.8697.b603)
*Mar 1 00:00:46.122: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.50.12, mask 255.255.255.0, hostname APe05f.b9a7.e290
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (184.108.40.206)
*Mar 1 00:00:57.113: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP. (220.127.116.11)
*Mar 1 00:01:15.119: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 1 00:01:25.120: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 6 09:54:05.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.50.5 peer_port: 5246
extracting info (287 bytes)
Version Suffix: k9w8-.153-3.JD4
Image Name: ap3g1-k9w8-mx.153-3.JD4
Version Directory: ap3g1-k9w8-mx.153-3.JD4
Ios Image Size: 9042432
Total Image Size: 10138112
Image Feature: WIRELESS LAN|LWAPP
Image Family: AP3G1
Wireless Switch Management Version: 18.104.22.168
ap3g1-k9w8-mx.153-3.JD4/ (directory) 0 (bytes)
extracting ap3g1-k9w8-mx.153-3.JD4/u-boot.bin (393216 bytes)
*Sep 6 09:54:07.258: %CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 192.168.50.5 peer_port: 5246
The following screenshot was taken after the AP joined the WLC and begun automatically downloading the new image:
As soon as the AP downloads and installs the new image, it will automatically reload and register with the WLC again. At this point the AP is ready to be configured and used as required.
Finally notice the date/time correction (*Sep 6 09:54:05.000) as soon as the AP registers with the WLC controller. This is the first indication its registered correctly with the WLC at IP address 192.168.50.5
This article showed how to convert an Autonomous or Standalone Cisco Access Point to Lightweight mode and join it to a Cisco WLC Controller. We covered the different restrictions and considerations during the AP conversion process, explained the difference between the fully functional CAPWAP (k9w8) and recovery mode CAPWAP (rcvk9w8) image files. Finally we provided the necessary commands & tips to configure the AP, transfer the image and register it with the WLC.