Техническая Инструкция для Cisco Cisco 2000 Series Wireless LAN Controller
In the case of the SSC APs, no certificate is created on the controller. The upgrade tool has the AP generate a
Rivest, Shamir, and Adelman (RSA) key pair that is used to sign a self−generated certificate (the SSC). The
upgrade tool adds an entry to the controller authentication list with the MAC address of the AP and public
key−hash. The controller needs the public key−hash in order to validate the SSC signature.
Rivest, Shamir, and Adelman (RSA) key pair that is used to sign a self−generated certificate (the SSC). The
upgrade tool adds an entry to the controller authentication list with the MAC address of the AP and public
key−hash. The controller needs the public key−hash in order to validate the SSC signature.
If the entry has not been added to the controller, check the output CSV file. There should be entries for each
AP. If you find the entry, import that file into the controller. If you use the controller command−line interface
(CLI) (with use of the config auth−list command) or the switch web, you must import one file at a time. With
a WCS, you can import the whole CSV file as a template.
AP. If you find the entry, import that file into the controller. If you use the controller command−line interface
(CLI) (with use of the config auth−list command) or the switch web, you must import one file at a time. With
a WCS, you can import the whole CSV file as a template.
Also, check the regulatory domain.
Note: If you have a LAP AP but you want Cisco IOS functionality, you need to load an autonomous Cisco
IOS image on it. Conversely, if you have an autonomous AP and want to convert it to LWAPP, you can install
an LWAPP recovery image over autonomous IOS.
IOS image on it. Conversely, if you have an autonomous AP and want to convert it to LWAPP, you can install
an LWAPP recovery image over autonomous IOS.
You can complete the steps to change AP image with the MODE button or CLI archive download
commands. Refer to Troubleshooting for more information on how to use the MODE button image reload,
which works with autonomous IOS or recovery image named to AP model default filename.
commands. Refer to Troubleshooting for more information on how to use the MODE button image reload,
which works with autonomous IOS or recovery image named to AP model default filename.
The next section discusses some of the commonly seen issues in the upgrade operation and the steps to resolve
these issues.
these issues.
Problem
Symptom
The AP does not join the controller. The Solutions section of this document provides the causes in order of
probability.
probability.
Solutions
Use this section to solve this problem.
Cause 1
The AP cannot find the controller via LWAPP discovery, or the AP cannot reach the controller.
Troubleshoot
Complete these steps:
Issue the debug lwapp events enable command at the controller CLI.
Look for the LWAPP discovery > discovery response > join request > join response sequence. If you
do not see the LWAPP discovery request, it means the AP cannot or does not find the controller.
do not see the LWAPP discovery request, it means the AP cannot or does not find the controller.
Here is an example of a successful JOIN REPLY from the Wireless LAN Controller (WLC) to the
converted Lightweight AP (LAP). This is the output of the debug lwapp events enable command:
converted Lightweight AP (LAP). This is the output of the debug lwapp events enable command:
Thu May 25 06:53:54 2006: Received LWAPP DISCOVERY REQUEST from AP
00:15:63:e5:0c:7e to 00:0b:85:33:84:a0 on port '1'
Thu May 25 06:53:54 2006: Successful transmission of LWAPP Discovery−Response to AP
1.