Ap to lwapp upgrade tool

This document also provides information on how to rectify these issues. The upgrade utility is supported on the Windows and Windows XP platforms. Either of these Windows operating system versions must be used. The series access points can be upgraded with any combination of supported radios: G only, A only, or both G and A. For an access point that contains dual radios, if one of the two radios is an LWAPP-supported radio, the upgrade tool still performs the upgrade.

The tool adds a warning message to the detailed log that indicates which radio is unsupported. These Cisco wireless LAN controllers support autonomous access points upgraded to lightweight mode:. You can download the latest version of the upgrade utility from the Cisco Software Downloads page.

Refer to Cisco Technical Tips Conventions for more information on document conventions. The user runs an upgrade utility that accepts an input file with a list of access points and their credentials. The utility telnets to the access points in the input file a series of Cisco IOS commands to prepare the access point for the upgrade, which includes the commands to create the self-signed certificates.

Also, the utility telnets to the controller to program the device to allow authorization of specific self-signed certificate access points. After the access point joins the controller, it downloads a complete Cisco IOS version from it.

The upgrade utility generates an output file that includes the list of access points and corresponding self-signed certificate key-hash values that can be imported into the WCS management software.

The WCS can then send this information to other controllers on the network. This upgrade tool is used to upgrade an autonomous AP to lightweight mode provided the AP is compatible for this upgrade. The upgrade tool performs the basic tasks necessary to upgrade from autonomous to lightweight mode.

These tasks include:. Basic condition checking—Verifies whether the AP is a supported one, whether it runs a minimum software revision, and whether the radio types are supported.

On a successful download, this reboots the AP. Generates an output file that consists of AP MAC addresses, the certificate type, and a secure key-hash, and automatically updates the controller. The output file can be imported into WCS and exported to other controllers. If you want to retain the static IP address, netmask, hostname, and default gateway of access points after conversion and reboot, you must load one of these autonomous images on the access points before you covert the access points to LWAPP:.

If you upgrade access points to LWAPP from one of these autonomous images, the converted access points do not retain their static IP address, netmask, hostname, and default gateway:. The LWAPP upgrade tool does not release Windows operating system memory resources when the upgrade process is complete. Memory resources are released only after you exit the upgrade tool.

If you upgrade several batches of access points, you must exit the tool in between batches to release memory resources. If you do not exit the tool in between batches, performance of the upgrade station quickly degrades because of excessive memory consumption.

Connectivity to the AP. This procedure can be done remotely via telnet or SSH , but a serial console connection works, of course. Do not use this procedure if the connection to the AP uses the wireless interface of the AP you want to convert. Please note: Following this procedure the AP will reboot without a config. Convertion The convertion consists of three main steps: Creating a self signed certificate for the AP Install a number of trusted root certificates Install the LWAPP Upgrade software Self signed certificate Connect to the AP and make sure you have the appropriate privileges: ap sh privilege Current privilege level is 15 The self signed certificate will contain the MAC address of the ethernet interface, so this needs to be determined first.

Trustpoint CA certificate accepted. Trackback specific URI for this entry. Display comments as Linear Threaded. GJ, thanks. Hi, your missing a step, atleast on a So they get trashed when trying your method. When i run the cisco tool in the detailed log it as a lines: Saving the configuration into memory certs stored in nvram: so im guessing theres a command to save them on the flash not the config.

Thanks for the information. I'll try to get my hands on a and see what's different about it. I had the same problem with a Fortunately I had a copy of Wireshark handy.

During the Reload step, the AP prompts if you want to save config changes to nvram. Load the config into each new AP and run the crypto key generate command. I came across this and am trying this on a N WAP. I am having a problem though on the image transfer.

It outputs Error opening If the code versions are different, the controller either upgrades or downgrades the AP. From there, the controller can handle the rest.

This is the software application you need to perform the upgrade. This software installs on a Windows computer. Select the link to download the software you need.

Because you want the IP Setup Utility for this task, click that link. After it is installed, you can perform the upgrade. Keep in mind that after you do the upgrade from autonomous to lightweight, the AP cannot function without the controller, and the console port is no longer useful.

To begin the upgrade, first check to see if you are running a code version on the AP that is capable of being upgraded. In Figure , the code version is This indicates that the version is compatible. After you have verified the IOS version, you need to make sure that the controller and the AP are on the same subnet or that the controller is reachable after the upgrade. The next step is to prepare a text file of APs that you want to upgrade.

I recommend using Notepad so that you can save it as a. In the text file, the format should resemble the following:. Create a new line for each AP that you want to convert.

When you are finished with the text file, save it somewhere that you can find it, and name it something like APList. You are going to browse to this file in the Upgrade tool interface. As a final preparation step, you need to make sure that the upgrade code is on the local machine.