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.
Your software release may not support all of the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Access points that are converted to lightweight mode do not support Wireless Domain Services (WDS). Converted access points communicate only with Cisco wireless LAN devices and cannot communicate with WDS devices. However, the device provides functionality that is equivalent to WDS when an access point is associated to it.
All Cisco lightweight access points support 16 Basic Service Set Identifiers (BSSIDs) per radio and a total of 16 wireless LANs per access point. When a converted access point is associated to a device, only wireless LANs with IDs 1 through 16 are pushed to the access point, unless the access point is a member of an access point group.
Access points that are converted to lightweight mode must get an IP address and discover the device using DHCP, DNS, or IP subnet broadcast.
You can convert autonomous Cisco Aironet access points to lightweight mode. When you upgrade the access points to lightweight mode, the access point communicates with the device and receives a configuration and software image from the device.
After you convert an autonomous access point to lightweight mode, you can convert the access point from a lightweight unit back to an autonomous unit by loading a Cisco IOS release that supports autonomous mode (Cisco IOS Release 12.3(7)JA or earlier releases). If the access point is associated with a device, you can use the device to load the Cisco IOS release. If the access point is not associated to a device, you can load the Cisco IOS release using TFTP. In either method, the access point must be able to access a TFTP server that contains the Cisco IOS release to be loaded.
Cisco Aironet Access Points use the type-length-value (TLV) format for DHCP option 43. You must program the DHCP servers to return the option based on the access point’s DHCP Vendor Class Identifier (VCI) string (DHCP option 60).
See the product documentation for your DHCP server for instructions on configuring DHCP option 43. The Converting Autonomous Access Points to Lightweight Mode document contains example steps for configuring option 43 on a DHCP server.
If the access point is ordered with the Service Provider Option - AIR-OPT60-DHCP selected, the VCI string for that access point will be different than those strings listed in the previous table. The VCI string has the following suffix: ServiceProvider, for example, a 1260 with this option returns the VCI string Cisco AP c1260-ServiceProvider.
 Note |
Ensure that the device IP address that you obtain from the DHCP server is a unicast IP address. Do not configure the device IP address as a multicast address when configuring DHCP option 43. |
Cisco Wave2 APs support strings with length up to 256 characters only.
Note |
When the string length exceeds the limit, the default value is sent during the DHCP discover process. |
When a converted access point unexpectedly reboots, the access point stores a crash file on its local flash memory at the time of the crash. After the unit reboots, it sends the reason for the reboot to the device. If the unit rebooted because of a crash, the device pulls up the crash file using existing CAPWAP messages and stores it in the device flash memory. The crash information copy is removed from the access point flash memory when the device pulls it from the access point.
By default, access points converted to lightweight mode do not send memory core dumps to the device. This section provides instructions to upload access point core dumps using the device GUI or CLI.
There are some differences in the way that controllers display the MAC addresses of converted access points on information pages in the controller GUI:
On the AP Summary window, the controller lists the Ethernet MAC addresses of the converted access points.
On the AP Detail window, the controller lists the BSS MAC addresses and Ethernet MAC addresses of the converted access points.
On the Radio Summary page, the device lists converted access points by the radio MAC address.
If you want to specify an IP address for an access point rather than having one assigned automatically by a DHCP server, you can use the controller GUI or CLI to configure a static IP address for the access point. Static IP addresses are generally used only for deployments with a limited number of APs.
An access point cannot discover the device using domain name system (DNS) resolution if a static IP address is configured for the access point, unless you specify a DNS server and the domain to which the access point belongs. You can configure these parameters using either the device CLI or the GUI.
Note |
If you configure an access point to use a static IP address that is not on the same subnet on which the access point’s previous DHCP address was, the access point falls back to a DHCP address after the access point reboots. If the access point falls back to a DHCP address, enter the show ap config general Cisco_AP CLI command to show that the access point is using a fallback IP address. However, the GUI shows both the static IP address and the DHCP address, but it does not identify the DHCP address as a fallback address. |
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enters privileged EXEC mode. |
||
| Step 2 |
ap name Cisco_AP tftp-downgrade tftp_server_ip_address tftp_server_image_filename Example: |
Converts the lightweight access point back to autonomous mode.
|
| Step 1 |
Configure the PC on which your TFTP server software runs with a static IP address in the range of 10.0.0.2 to 10.0.0.30. |
||
| Step 2 |
Make sure that the PC contains the access point image file (such as c1140-k9w7-tar.123-7.JA.tar for a 1140 series access point) in the TFTP server folder and that the TFTP server is activated. |
||
| Step 3 |
Rename the access point image file in the TFTP server folder to c1140-k9w7-tar.default for a 1140 series access point. |
||
| Step 4 |
Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable. |
||
| Step 5 |
Disconnect power from the access point. |
||
| Step 6 |
Press and hold the MODE button while you reconnect power to the access point.
|
||
| Step 7 |
Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button. |
||
| Step 8 |
Wait until the access point reboots as indicated by all the LEDs turning green followed by the Status LED blinking green. |
||
| Step 9 |
After the access point reboots, reconfigure the access point using the GUI or the CLI. |
You can enable or disable the Reset button on access points that are converted to lightweight mode. The Reset button is labeled MODE on the outside of the access point.
Note |
The procedure to perform this task using the controller GUI is not currently available. |
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enters privileged EXEC mode. |
||
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
| Step 3 |
no ap reset-button Example: |
Disables the Reset buttons on all converted access points that are associated to the device.
|
||
| Step 4 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
||
| Step 5 |
ap name cisco_ap reset-button Example: |
Enables the Reset button on the converted access point that you specify. |
Note |
The procedure to perform this task using the device GUI is not currently available. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enters privileged EXEC mode. |
| Step 2 |
show ap crash-file Example: |
Verifies whether the crash file is downloaded to the device. |
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enters privileged EXEC mode. |
||
| Step 2 |
ap name Cisco_AP static-ip ip-address static_ap_address netmask static_ip_netmask gateway static_ip_gateway Example: |
Configures a static IP address on the access point. This command contains the following keywords and arguments:
The access point reboots and rejoins the device, and the static IP address that you specify is pushed to the access point. After the static IP address has been sent to the access point, you can configure the DNS server IP address and domain name. You must perform Steps 3 and Step 4 after the access points reboot. |
||
| Step 3 |
enable Example: |
Enters privileged EXEC mode. |
||
| Step 4 |
configure terminal Example: |
Enters global configuration mode. |
||
| Step 5 |
ap static-ip name-server nameserver_ip_address Example: |
Configures a DNS server so that a specific access point or all access points can discover the device using DNS resolution.
|
||
| Step 6 |
ap static-ip domain static_ip_domain Example: |
Configures the domain to which a specific access point or all access points belong.
|
||
| Step 7 |
end Example: |
Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
||
| Step 8 |
show ap name Cisco_AP config general Example: |
Displays the IP address configuration for the access point. |
| Step 1 |
Choose . |
| Step 2 |
On the All Access Points section, click on an AP Name. |
| Step 3 |
In the Edit AP window that is displayed, go to the IP Config section. |
| Step 4 |
Select the Static IP (IPv4/IPv6) check box. This activates the static IP details pane. |
| Step 5 |
Enter the Static IP, Netmask, Gateway, and DNS IP Address. |
| Step 6 |
Click Update & Apply to Device. |
| Step 1 |
Download the required recovery image from Cisco.com (ap3g2-k9w8-tar.152-2.JA.tar) and install it in the root directory of your TFTP server. |
| Step 2 |
Connect the TFTP server to the same subnet as the target access point and power-cycle the access point. The access point boots from the TFTP image and then joins the device to download the oversized access point image and complete the upgrade procedure. |
| Step 3 |
After the access point has been recovered, you can remove the TFTP server. |
This example shows how to display the IP address configuration for an access point:
Device# show ap name AP03 dot11 24ghz config general
Cisco AP Identifier.............. 4
Cisco AP Name............................. AP6
IP Address Configuration.................. Static IP assigned
IP Address................................ 10.10.10.118
IP NetMask................................ 255.255.255.0
Gateway IP Addr........................... 10.10.10.1
Domain.................................... Domain1
Name Server............................... 10.10.10.205
...This example shows how to display access point crash file information. Using this command, you can verify whether the file is downloaded to the device.
Device# show ap crash-file
Local Core Files:
lrad_AP1130.rdump0 (156)
The number in parentheses indicates the size of the file. The size should
be greater than zero if a core dump file is available.Ethernet VLAN Tagging on Access Points
You can configure VLAN tagging on the Ethernet interface either directly on the AP console or through the controller. The configuration is saved in the flash memory and all CAPWAP frames use the VLAN tag as configured, along with all the locally switched traffic, which is not mapped to a VLAN.
| Step 1 |
Choose . |
| Step 2 |
Click the name of the AP Join Profile or click Add to create a new one. |
| Step 3 |
In the Add/Edit AP Join Profile window that is displayed, click the CAPWAP tab and then click the Advanced tab. |
| Step 4 |
Check the Enable VLAN Tagging check box to enable VLAN tagging for the AP Join Profile. |
| Step 5 |
Click Update & Apply to Device. |
Follow the procedure given below to configure Ethernet VLAN tagging on APs.
VLAN tagging is not supported on MAPs that are in bridge mode. The feature is automatically disabled when the APs are set to bridge mode.
If VLAN tagging is enabled, flex native VLAN ID cannot be configured for an AP.
APs in flexconnect standalone mode (with VLAN tag enabled) may reload at every 10 minutes, if the APs fail to discover the wireless controller during failover.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
ap name ap-name vlan-tag vlan-id Example: |
Configures VLAN tagging for a non-bridge AP. Use the no form of this command to disable the configuration. |
| Step 2 |
ap vlan-tag vlan-id Example: |
Configure VLAN tagging for all nonbridge APs. Use the no form of this command to disable the configuration. |
| Step 3 |
show ap config general Example: |
(Optional) Shows the common information of all the APs. |
Feedback