Convert ap to lwap

I have many lightweight APs 1231 and I want to install a WLC in the network. My APs may be lightweight. How can I convert this APs to LWAP?
Thanks.

Have a look at :
http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/prod_white_paper0900aecd804f1a23_ns337_Networking_Solutions_White_Paper.html
and
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html
Rgds
Vincent

Similar Messages

Can I configure Autonomous AP as repeater at LWAP Network

Dear Team ,
I have AP 1602I-E-K9 already,I convert it from LWAP to Autonomous AP with ap1g2-k9w7-tar.152-4.JA1 IOS, can i use it as repeater from LWAP ( AIR-LAP 1042N-E-K9 ) ,
Already I use the attached configuration and don't work.
Please Advise can i use autonomous AP to work as a repeater from LAP.
Thanks,

Dear Scott,
Already the Autonomous AP worked as arepeater with LWAP after i make LWAP in Root mode and the below configuration in Autonomous AP . and i test it by (sh dot11 association), but i face the below error when any user try to connect internet through the Repeater.
Configuration:
AP(config)# dot11 ssid ssid string
AP(config_ssid)#authentication open
AP(config_ssid)#guest mode (to Broadcast SSID)
AP(config_ssid)#infrastructure-ssid(to instruct non root AP and associate with SSID)
AP(config_ssid)#exit
AP(config)#interface dot11radio 0
AP(config_If)#ssid ssid string
AP(config_if)#station-role repeater
AP(config_if)#parent 1 mac address for interface dot11radio 0
AP(config_if)#bridge group 1
AP(config_if)#no shutdown
error:
*Mar 1 00:28:12.434: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 5c0a.5ba5.2928 Associated KEY_MGMT[NONE]
*Mar 1 00:28:43.277: %DOT11-6-DISASSOC: Interface Dot11Radio0, Deauthenticating Station 5c0a.5ba5.2928 Reason: Sending station has left the BSS
Please Advice with steps to solve this issue. Knowing that i can ping to yahoo.com from AAP.
Thanks,

Converting LAP back to autonomous failed

I've a 1130 AP which doesn't boot it's LWAPP image from flash. So I tried to convert it back (with tftp server and so on) but after the message that it's using the "reset IP" it tries again to start the (corrupt?) image.
Is there a way to stop this boot cycles and to check boot parameter? Or any other ideas?

Hi Guys,
Today, I have converted the Cisco LWAP (1140) to Autonomous AP successfully.
Follow the below steps:
1. Download your 1142 image from Cisco --- I chose c1140-k9w7-tar.124-21a.JY.tar (Autonomous IOS Image for LWAP 1142)
2. Copy your 1142 image to your TFTP folder and start your TFTP server
3. Hook up your console cable and open up PuTTY
4. Plug in your 1142 into your POE/non-PoE (use Power Chord) switch.
5. Create one DHCP Pool in 10.0.0.0/24 network and let the LWAP and Laptop takes the IP from that DHCP Pool.
6. When it boots and your DHCP server gives it an IP address, you'll get a prompt (*your AP needs to get to your TFTP server)
Use PuTTY and enter in the commands in bold and modify the address of your TFTP server and image accordingly.
APd0d0.fdae.aea4> enable
Password: Cisco
APd0d0.fdae.aea4#debug lwapp client no-rel    ###### Very Important command
LWAPP ignore internal reload debugging is on
APd0d0.fdae.aea4#debug capwap console cli   ######## After giving the above one, this particular command will activate.
CAPWAP console CLI allow/disallow debugging is on
APd0d0.fdae.aea4# archive download-sw /overwrite /force-reload tftp://10.0.0.10/c1140-k9w7-tar.124-21a.JY.tar    ######## After giving the above command "debug capwap console cli" then the "ARCHIVE" command will activate
It starts upgrading the new IOS to the LWAP. After installing the IOS, reboot twice the AP and you can normally see the prompt “ap>”
Regards,
Praveen Neti.

Possible to convert autonomous AP to LWAPP via CLI?

Hi,
Probably a silly question but was wondering why it is not possible to convert an autonomous AP to LWAPP by using CLI commands?
For example we have over 300 access points to convert and thought about using Linux to automate the task but seems there is only a windows conversion utility.
Cheers,
- Trevor

Hi Trevor,
You can convert AP to LWAP using CLI but this is entirely dependent on the model of AP you're dealing with. 1230, for example, requires the conversion tool. 1130, 1240 and 1250 can be converted using CLI. Here it is ...
Requirements:
â¢ Image file (The recovery file has the prefix ârcvâ in the image name, such as c1200-rcvk9w7-tar.122-15.JA.tar);
â¢ AP is connected to the Wireless LAN Controller; and
â¢ AP can ping the TFTP server where the image is located.
Procedure
1. Copy the recovery file to the AP using the following command:
archive tar /x tftp:/// flash:
2. Let the AP boot on this image:
boot system flash://.bin
3. Reboot the AP.
OPTIONAL
â¢ DO NOT ALLOW THE AP TO JOIN THE WIRELESS LAN CONTROLLER IN ORDER TO USE THE OPTIONAL COMMANDS BELOW.
â¢ IF POSSIBLE, type the following commands:
ï¾ clear lwapp private-config (This will bring the AP to factory default.);
ï¾ clear lwapp ap ip address
ï¾ clear lwapp ap hostname
ï¾ clear lwapp ap controller ip address
4. Let the AP connect to the Wireless LAN controller.
OPTIONAL
If an AP refuses to join the Wireless LAN Controller, type the following command from the AP:
lwapp ap controller ip address

Issue with 1131 AP

AP 1130 (Autonomous) is converted in to LWAP and it has go the recovery image of âc1130-rcvk9w8-tar.123-7JXâ
We tried to associate with WLC in L3 mode by enabling DHCL option 43, LAP is initially getting associated with WLC and downloading the latest software from WLC after that it's getting disconnected from the WLC

Verify the time is set correctly on the wlc. Also, post the log when you are consoled into the ap, so we can see the error, unless the time setting fixes your issues. Check the country code on both the wlc and ap also.

Change IP address for WLC

I want to change IP address for WLC in production, should I convert Access Point from LWAP to IOS then convert again to LWAP ?
Regards,

Hi Friend,
The best way is configure your controlelr as primary controller for all APs. You can do so going to wireless tab and then click on each AP detail and configure this controller as primary controller.
Also if you have WCS you can do the same in one go for all APs and after that even if controller ip address is changed they will stay join to this controller.
HTH
Ankur
*Pls rate all helpfull post

1142 AP disassociate from WISM code 7.0.116.0

We see different 1142 APs disassociate from wisms from time to time. When it happens, we have to do shutdown and no shutdown on the switch port to bring the APs back. It just starts to happen after we upgraded wisms to code 7.0.116.0 and it only happens to c1142 APs. It does not happen very often (about 2 issues each week). Anyone see this issue as well?
Zhenning

Any ideas why we need to upgrade the bootstrap?
There are some issues with the 1140. This is why it's only this model that a boostrap is an optional install (autonomous or capwap use). I'd recommend, if you have the time, to do so.
Unfortunately, I have no idea how you "force" the bootstrap upgrade if you have CAPWAP/LWAP. The only way I can think of is downgrade to autonomous, upgrade the boostrap and convert to CAPWAP/LWAP. Long process.

Issue Converting LWAP to IOS

Good day all, this is my first experience converting LWAP to IOS so please bear with me. I have followed all the major steps such as changing the TFTP server's IP within the range 10.0.0.2 and 10.0.0.30 with subnet 255.255.255.224 as well as changing the desired image name to c1200-k9w7-tar.default. After holding the mode button down till it turns red and releasing it goes into image recovery mode than examines the image, it than gives me the error "Failed to open archive file tftp://255.255.255.255/c1200-k9w7-tar.default" and than resumes with loading its original image. I do see the attempt hit my tftp server (solar winds) but says "error 10.0.0.1 requesting c1200-k9w7-tar.default: file does not exist". I am a bit confused because when initially trying to recover the image the 255.255.255.255 tftp location does not seem right yet it still shows up in the TFTP server log. Any help or insigt is greatly appreciated. Many thanks,
SB

Hi Steven,
This sure sounds like a TFTP problem. Have a look at the details in the following threads that all have to do with TFTP. There are some great hints for troubleshooting TFTP problems from some of my favourite NetPros like ScottMac,Stephen from Cisco and JackYoung. The likely culprit may be that you need to uncheck "hide extensions for known file types" on your TFTP server;
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=WLAN%20Radio%20Standards&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddc042b/8#selected_message
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddc03c4/2#selected_message
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddbf271
Hope this helps!
Rob

Converting Autonomous AP to LWAP by using 2500 series WLC

Hello everyone,
I'm a newbie in wireless section and have a problem. I have two autonomous AIR-LAP1041N-E-K9 with IOS "c1140-k9w7-mx.124-25d.JA1" and one 2504 WLC. I need to convert those APs to Lightweight and use with that controller. But, I don't have any power supply for APs and PoE switch. I only got 2504 WLC with 2 port PoE. If I could use WLC's ports as switchports, this will be really easy. Maybe it could be used, but as I see WLC's ports are L3-only.
What is the easiest way to solve this issue?
Thanks now,
Mehmet.

I don't know if that is possible, but you can try. Configure the WLC and then connect one of the AP's to the PoE port. Configure the AP through the command line via the console. Put that ap on the same subnet as the WLC management. Try to ping the WLC IP address from the AP. If that works them your good so far. Now connect a laptop to another port and configure the IP on the laptop to also be on the WLC management. Make sure you can ping the AP from the laptop and vice versa. Then you have to download the code for the AP which will be an rcv image. Follow these links on the conversion.
Using a TFTP Server to Return to a Previous Release
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp160918
https://supportforums.cisco.com/docs/DOC-18268
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp160918
http://www.youtube.com/watch?v=QQ_NuxdRhQ4
https://supportforums.cisco.com/docs/DOC-14960
Sent from Cisco Technical Support iPhone App

LWAP migration of AIR-1131AG-A failed bad mzip file

Hello Experts,
I would like to connect a Cisco LWAP 1131AG-A-K9 with a WLC4402 running on 4.1.171.0
Unfortunately, the software downloaded from the WLC is not correctly unpacked on the AP.
I can see an error on the console stating "bad mzip file".
We did several test with converting back to autonomous and migrating to LWAP again using the Cisco Upgrade Tool
but we are failing constantly, even though the Cisco Upgrade Tool states a successful update.
All our european Cisco LWAPs 1131AG-E-K9 are running fine by the way on the controller.
I have added the Console messages to show the error to You.
Who knows anything about that ?
Please support.
*Mar 1 00:00:08.865: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1130 Software (C1130-RCVK9W8-M), Version 12.4(21a)JA2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Mon 02-Nov-09 18:17 by prod_rel_team
*Mar 1 00:00:08.892: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:00:09.389: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
*Mar 1 00:00:09.839: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:18.494: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 163.157.68.121, mask 255.255.255.0, host
name AP001e.7abd.cf52
Translating "CISCO-CAPWAP-CONTROLLER.corp.skf.net"...domain server (163.157.156.161)
Translating "CISCO-LWAPP-CONTROLLER.corp.skf.net"...domain server (163.157.156.161) [OK]
*Mar 1 00:00:38.814: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:00:38.816: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.corp.skf.net
*Mar 1 00:00:48.819: %CAPWAP-3-ERRORLOG: Go join a lwapp controller
*Mar 1 00:00:48.819: %LWAPP-3-CLIENTERRORLOG: Set Transport AddressCalled
examining image...
extracting info (286 bytes)
Image info:
    Version Suffix: k9w8-.124-3g.JA
    Image Name: c1130-k9w8-mx.124-3g.JA
    Version Directory: c1130-k9w8-mx.124-3g.JA
    Ios Image Size: 3410432
    Total Image Size: 3410432
    Image Feature: WIRELESS LAN|LWAPP
    Image Family: C1130
    Wireless Switch Management Version: 4.1.171.0
Extracting files...
c1130-k9w8-mx.124-3g.JA/ (directory) 0 (bytes)
extracting c1130-k9w8-mx.124-3g.JA/info (286 bytes)
extracting c1130-k9w8-mx.124-3g.JA/6701.img (131328 bytes)
*Mar 1 00:00:48.831: %LWAPP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 9 12:37:21.242: %LWAPP-5-CHANGED: CAPWAP changed state to IMAGE
extracting c1130-k9w8-mx.124-3g.JA/c1130-k9w8-mx.124-3g.JA (3138988 bytes)
extracting c1130-k9w8-mx.124-3g.JA/7101.img (13132
*Dec 9 12:38:19.147: %SYS-4-PUPDATECLOCK: Periodic Clock update with ROMMON failed, because size left in ROMMON (4294967295), size
needed (29), error code (-1)
*Dec 9 12:38:19.148: %SYS-5-RELOAD: Reload requested by lwapp image download proc. Reload Reason: NEW IMAGE DOWNLOAD.
*Dec 9 12:38:19.148: %LWAPP-5-CHANGED: CAPWAP changed state to DOWN8 bytes)
extracting info.ver (286 bytes)
New software image installed in flash:/c1130-k9w8-mx.124-3g.JA
Configuring system to use new image...done.
archive download: takes 58 seconds
Writing out the event log to nvram...
Xmodem file system is available.
flashfs[0]: 11 files, 3 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 15998976
flashfs[0]: Bytes used: 6035968
flashfs[0]: Bytes available: 9963008
flashfs[0]: flashfs fsck took 30 seconds.
Base ethernet MAC Address: 00:1e:7a:bd:cf:52
Initializing ethernet port 0...
Reset ethernet port 0...
Reset done!
ethernet link up, 100 mbps, full-duplex
Ethernet port 0 initialized: link is up
Loading "flash:/c1130-k9w8-mx.124-3g.JA/c1130-k9w8-mx.124-3g.JA"...#################################################################
###################################################################################################################################b
ad mzip file, unknown zip method
Error loading "flash:/c1130-k9w8-mx.124-3g.JA/c1130-k9w8-mx.124-3g.JA"
Interrupt within 5 seconds to abort boot process.
Loading "flash:/c1130-rcvk9w8-mx/c1130-rcvk9w8-mx"...###############################################################################
File "flash:/c1130-rcvk9w8-mx/c1130-rcvk9w8-mx" uncompressed and installed, entry point: 0x3000
executing...

We are using right now only Lightweight-APs with ETSI-Standards on several Controllers without having that problem.
The problem appears during the migration from AUutonomous to Lightweight of an 1131AP with American-Standard.
The according WLC is configured to support US-Country of course.
I cannot believe that this is the problem. This would mean different LWAPP-images per regulation domain.
Who knows more about this damned mzip-error during the extracting phase of the LWAPP-image ?

Converting back AP 2600 from Autonomous to LWAPP

Hello,
I have Cisco AP 2600, Previously i had converted it from LWAPP mode into Autonomous-Mode. But now I need to revert it back to LWAPP mode.
Can anyone send me the link on how to do it ?

HI Imran,
Yes you can convert it to lightweight. Just need the lightweight recovery image.
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html
For the LWAP conversion, use the recovery image (example: c1140-rcvk9w8-tar.124-25d.JAL.tar). after thatuse the command on the autonomous AP priviledge mode.
AP#archive download-sw /force-reload /overwrite tftp://10.10.10.1/c1140-rcvk9w8-tar.124-25d.JA.tar
more detial ..follow this post:
http://mrncciew.com/2012/10/20/lightweight-to-autonomous-conversion/
Regards
Dont forget to rate helpful posts

Converting AP1230B to Lightweight AP?

Hi everyone, we've got quite a few 1230B's that we'd like to leverage in our upcoming WLC deployment and I'm wondering if we can convert these autonomous AP's to be Lightweights?

Hi!
For all IOS-based 1200 series modular access point (1200/1220 Cisco IOS Software Upgrade, 1210 and 1230 AP) platforms, it depends on the radio:
-if 802.11G, MP21G and MP31G are supported
-if 802.11A, RM21A and RM22A are supported
The 1200 series access points can be upgraded with any combination of supported radios: G only, A only, or both G and A.
You cannot upgrade access points with 802.11b-only or first-generation 802.11a radios.
Thus, 1230B can't be upgraded to LWAP.
Please take a look:
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp157130
HTH
-Jai

WLC + LWAP Moving from L2 to L3

Hi
I'm migrating a remote site from a L2 to L3 WAN link.
This means the AP at the remote site will no longer be able to talk directly(over the same VLAN) to the WLC at HQ.
The AP will receive an IP from the DHCP server(Cisco router) at the remote site. If I understand the LWAP registration process providing there is routing between the AP and the WLC this should just work?
Is there anything I need to be aware of? Note - there is already an existing remote site using L3 LWAP.

You should be fine. The AP is already joining the WLC, so it knows the IP address of the management interface. So when you convert that link to an L3, the AP will get it's new IP address and will attempt to join the last WLC that it was working on.
You could add in Option 43 in the DHCP scope the AP uses, if you wanted. It would help for any new AP that come up on that site.
HTH.
Steve

Converting a 1260AP from Autonomous to Lightweight mode

Is the process for converting 1260 APs to lightweight mode any different from converting 1140s or 1250s? I've converted several APs to LWAP mode but this is my first 1260. Four 1260s need to be converted.
I have one in a remote location that seems to be comatose. Here are the steps I took to convert the AP. Did skip/miss a step?
1. uploaded code to the AP ap3g1-rcvk9w8-tar.152-2.JB.tar
2. configured the AP for DHCP. It successfully leased a DHCP address. Controller information is provided via DHCP Option 43.
3. saved the configuration
4. verified the code, successful
5. disabled wireless radios
6. installed the lightweight code using the command archive download-sw /safe flash:/ap3g1-rcvk9w8-tar.152-2.JB.tar
The installation was successful
7. rebooted the AP
After that nothing. The AP has not leased another IP address. The switchport is active. The APs MAC address is registering in the switches MAC address table. The AP is receiveing PoE from the switch. I noticed that this AP is only receiving 6.2W of power where the three are getting anywhere between 8.8W and 9.3W. I am unable to ping the old static IP of the AP too.
Any suggestions?

can you console into the AP and post it's boot up cycle? Let it capture for two reboots of the AP.
Can you also share the config of the switchport this AP is connected to?
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

5508 controller coexisting with Autonomous and LWAPs

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:50%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
I have a question for the group and was curious if anyone has done this. I am looking through the docs on CCO and have gone through several books:
Controller-Based Wireless LAN Fundamentals – very good and updated 2010 publication and Deploying and Troubleshooting Cisco Wireless LAN Controllers also very good but from 2009.
I have a new install coming up over a legacy install. What I mean is we have a classic autonomous AP based setup on the campus with one vlan. We now want to deploy 5508 controllers and new N based AP. My questions are for migration approach. One school of thought is to deploy the controllers and convert all the autonomous fat APs to LWAPs then replace each LWAPs with a new N unit one or x at a time at our convenience. Then convert the removed FAT to converted LWAPs back to FAT (IOS) for another special classic non controller use.
I was curious if I can save this conversion step and deploy the controllers thus letting the users continue to use their classical FAT architecture while I add the N based APs one at a time. So, for example, I have the fat architecture now, deploy controllers, and on one floor where there is 5 fat APs swap one with an N AP. Now anyone in that N cell range will go through the controller but the other folks in the other cells can continue to authenticate and associate using the fat system in place. Can the controllers and Autonomous systems reside together? The only immediate protocol mechanics related issue here is roaming. I want to avoid any issues related to converting the FAT aps to LW aps in production(bugs, rollbacks etc that can slow things down). This way I can get the controllers and new APs in place quickly utilizing some known RF variables and slowly push the older APs out of use. Kinda like a SIN routing protocol migration flip with Admin distance flipping.
Is this possible and has anyone done this? Just curious. I am still looking though the docs. An thoughts are greatly appreciated.

This is possible. But don't expect any collaboration between WLC and IOS APs.
So roaming between lwapp aps and ios aps won't be smooth. The Lwapp aps will also consider the IOS APs as rogue unless you manually declare them friendly ...
Co-existence is not something recommended if you are peaky about those details.
If you only have data usage and a few hard-cut roaming doesn't scare you, then why not.
Nicolas
===
don't forget to rate answers that you find useful

Convert ap to lwap

Similar Messages

Maybe you are looking for