pmccubbin Sun, 12/02/2007 - 05:34

No. You cannot convert autonomous APs to LWAPPs with anything but WCS or the Upgrade Tool.

To do the conversion with WCS 4.2 you can use this feature:

The autonomous to LWAPP migration support utility.

You can also convert autonomous APs to LWAPP with the Upgrade tool.

Hope this helps.

Rob Huffman Sun, 12/02/2007 - 06:49

Hi Pirate (ARGHHH!),

Here is a little additional info to go along with the great tips from Paul (5 points for you Paul!);

LWAPP Upgrade Tool Troubleshoot Tips

Access points must run Cisco IOS Release 12.3(7)JA or later before you use the upgrade tool.

System Requirements

You can use the Autonomous to Lightweight Mode upgrade tool to install Cisco IOS Release 12.3(11)JX on these access points:

**All 1100 series access points containing MP21G (802.11g) radios

All 1130, 1230, and 1240 series access points

All modular 1200 series access points running Cisco IOS software and containing these supported radios:

802.11g: MP21G, MP31G

802.11a: AIR-RM21A-x-K9, AIR-RM22A-x-K9

All 1300 series access points in access point mode

Cisco has released a free tool called the "Autonomous to Lightweight Mode Upgrade Tool" that allows selected Cisco Aironet autonomous access point models to be configured for lightweight mode operation.

The Autonomous to Lightweight Mode Upgrade Tool supports the following models:

Cisco Aironet 1240AG Series access points

Cisco Aironet 1230AG Series access points

Cisco Aironet 1200 Series access points that contain 802.11g (AIR-MP21G-x-K9) and/or second-generation 802.11a radios (AIR-RM21A-x-K9 or AIR-RM22A-x-K9)

Cisco Aironet 1130AG Series access points

**Cisco Aironet 1100 Series Access Points that contain 802.11g radios (AIR-AP1121G-x-K9)

Cisco Aironet 1300 Series Access Points/Bridges (AIR-BR1310G-x-K9 or AIR-BR1310G-x-K9-R). A Cisco Aironet 1300 Series operating in Lightweight Access Point Protocol (LWAPP) mode only operates as an access point. This series does not support LWAPP bridging mode.

The Autonomous to Lightweight Mode Upgrade Tool supports a process to migrate an autonomous access point from autonomous mode to lightweight mode. Unlike a VxWorks to Cisco IOS Software upgrade, this process is a Cisco IOS Software upgrade to the existing Cisco IOS Software image-not an operating system "swapout". In converted access points operating in lightweight mode, Cisco IOS Software continues to run on the access point, while LWAPP is used to communicate with a wireless LAN controller. Since LWAPP supports automatic access point configuration, there is no need to retain or convert the original autonomous Cisco IOS Software access point configuration.

Cisco Aironet Access Point Support for Lightweight Access Point Protocol

Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode

Hope this helps!


pirateoftheairwaves Sun, 12/02/2007 - 22:43

hello experts!!

Thanks for all your inputs... appreciate them all, really!

we have some ap's that are still lower than the recommend ios for the upgrade, 12.3(4). we tried using ciscoworks lms2.5 to upgrade these ap's to 12.3(7)JA2. sadly, the ap hangs. the message on the ciscoworks says, the process is still running.. and the log below shows:



Device Name : test-ap-upgrade

Software upgrade result - Failed

Total number of devices scheduled for upgrade : 1

Number of devices upgraded : 0

Number of devices failed : 1

Total time taken for Job - 13 Minutes 14 Seconds

Status of Job - FAILED


Starting Job: ID - 1712

Job Started At : Mon Dec 03 09:14:46 AST 2007

Job running on : cc1001-lms01

Upgrade Mode : Sequential

Reboot Mode : Sequential

Protocol Order for Image Transfer : RCP,TFTP,SCP,HTTP

Protocol Order for Config-operations : TELNET,SSH,TFTP,HTTPS,RCP,SCP

Total number of device(s) to be processed : 1


Image Upgrade Operation Complete

Job Ended At : Mon Dec 03 09:28:00 AST 2007

Job Ended At : Mon Dec 03 09:28:00 AST 2007


Processing Device : test-ap-upgrade

Start Time : Mon Dec 03 09:15:50 AST 2007

Device is locked for exclusive access.

The supported protocols for image transfer are: TFTP

Importing the current running image c1200-k9w7-tar.123-7.JA5.tar from the device flash into the Software Repository.

Image will be copied to rep_sw_788422005462138522 using TFTP.

Could not import c1200-k9w7-tar.123-7.JA5 from the device.

Error Message:

SWIM1124: Failed to copy the image from Flash due to the reason - copyInvalidSourceName :invalid source file name specified For the copy from flash to lex operation.

Retry the operation. If the problem persists, check the Bug Toolkit application for any known issues on the running image version.

Running image import failed, will continue with Upgrade.

Copying c1200-k9w7-tar.123-7.JA2.tar from Software Repository to tftp-specific directory.

Copied successfully to E:/CSCOpx/tftpboot/rep_sw_788422005462171178

Loading image file to flash device : rep_sw_788422005462171178 --> flash:c1200-k9w7-tar.123-7.JA2.tar using TFTP

Completed loading image file to Flash device.

Total time to copy the image - 4 Minutes 3 Seconds

Device will be rebooted.

SWIM5006: Device Reboot operation failed.

The device is not configured for reboot. The SNMP Write Community string might be wrong.

The command SNMP server system shutdown should be in the running configuration on the device.

Device is unlocked.

Device Upgrade Result : Failed

End Time:Mon Dec 03 09:27:37 AST 2007


when the ap is rebooted, we found out that the ios has been upgraded to 12.3(7). however, we wish to do the upgrade of all the lower ios's even though they are still in the production without the hanging problem.

what could be causing the hanging problem? we have entered the following snmp strings:

snmp-server community ****** RW

snmp-server community **** RO

and still the message

Processing Device : test-ap-upgrade

Start Time : Mon Dec 03 09:15:50 AST 2007

Device is locked for exclusive access.

appears on the log.

Rob Huffman Mon, 12/03/2007 - 05:47

Hi Pirate,

A couple of things that I see;

You said that you are trying to upgrade to 12.3(7)JA2 but the upgrade mentions this "Could not import c1200-k9w7-tar.123-7.JA5 from the device." and then this reference "Failed to copy the image from Flash due to the reason - copyInvalidSourceName :invalid source file name specified For the copy"

Is there some problem with the actual filenames?

Hope this helps!



This Discussion



Trending Topics - Security & Network