Autonomous APs to LWAPP

I have a project to upgrade the current Autonomous APs 1242 running on a customer site and they want them to be converted to LWAPP and moved over to controller.Is there a way to convert them? Note the APs are about 12-15ft high in the ceiling.

Hi
cisco upgrade tool is available on  cisco web site you can download it and then you need to create a text file which you want to convert them.format is given below
This is simplest way to convert.
Helping document
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html
thanks
Tahir

Similar Messages

  • 802.1x auth fail through WLC but OK on autonomous APs

    Hello,
    I migrate 1310 APs from Autonomous to Lightweight. Migration is OK with Cisco Upgrade Tool, and AP are registered on my 2504 WLC.
    Previously, a 802.1x network was broadcasted by autonomous APs, supplicants were identified on a freeradius server with MSCHAPv2/PEAP method.
    I send you in attachement a AP config which is OK.
    But on the WLC, supplicants can't auth on Radius server.
    I configured a WLAN with WPA/TKIP/802.1x with my radius server in AAA tab.
    When clients try to authenticate, I get these messages where xxx is login:
    AAA Authentication Failure for UserName:821 User Type: WLAN USER
    AAA Authentication Failure for UserName:200 User Type: WLAN USER
    AAA Authentication Failure for UserName:209 User Type: WLAN USER
    Security info on client page is:
    Security Policy Completed
    No
    Policy Type
    WPA
    Encryption Cipher
    TKIP-MIC
    EAP Type
    PEAP
    SNMP NAC State
    Access
    Radius NAC State
    8021X_REQD
    What is strange, there are some clients which are OK in RUN State, and 50 other % which are not.
    In attachment there is a debug client "mac-address" on a device which cannot authenticate through WLC.
    Thank you,
    Clement

    Hi Amjad,
    I'm not using NAC.
    Clients makes a MSCHAPv2/PEAP auth on a FreeRadius server through the WLC.
    Because network is critical, I do a rollback so I passed the light APs into their autonomous original state.
    Now all clients can successfully auth on the network. I don't understand what happens when APs are in lightweight mode :/
    I have more information about the WLAN clients  :
    - Each client is an infrastructure which have a AXIS wireless modem in bridge mode, which is client of the WLAN. This modem have login/password for MSCHAPv2 auth.
    - Behind the AXIS, there is a switch on which 4 devices in static IP are connected.
    - If the AXIS is successfully authenticated on the WLAN, only one device of four is able to ping servers on the LAN. The others cannot, it seems to be a "token ring" like ?!
    The WLAN clients infrastructures are very proprietary, it's very difficult to debug.
    What I know, is all clients are OK on autonomous AP (auth 100% successfull, ping 100% successfull for 4 devices) and when the clients join a lightweight AP it is (auth 50% successfull, ping 100% successfull for 1 device, 0% successfull for 3 others devices)
    Tell me if you need specific debug logs.
    Clement

  • 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

  • Aironet 1520 from Autonomous to Unified (LWAPP)

    Hi
    Can the Aironet 1520 access point be field upgraded from Autonomous to Unified (LWAPP) mode like the Aironet 1240?
    Thanks.
    E

    Hi people
    I saw the message and stay with doubts
    Just to confirm, AP 1520 not accept autonomous image?

  • Do the 1042 Autonomous APs support GRE tunnels?

    Hi,
    Do the 1042 Autonomous APs support GRE tunnels?
    Any help is much appreciated.

    I have found:
    When you configure VLANs on access points, the native VLAN must be VLAN1. In a single architecture, client traffic received by the access point is tunneled through an IP-GRE tunnel, which is established on the access point’s Ethernet interface native VLAN.

  • Mulitple SSIDs and ACLs on Autonomous APs

    This is an unusual situation:
    I have the need to run a few autonomous APs (1262) for some sites on satellite links.
    At a bare minimum I need to run two WLANs.
    One is wide open, and the other with an ACL that heavily restricts access.
    Is there any way to tie two WLANs to a single VLAN, while applying an ACL to just one WLAN?
    Any ideas?

    On autonomous, you cans have multiple ssid pointing to one vlan.  You can on a WLC.
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • Autonomous APs' non-root radio tracking Questions

    Hi guys,
    As you know, we can configure an autonomous AP that is using its .11a radio as "non-root bridge" and its .11b/g as root to track the .11a radio so that if it is down for any reason, then it will shut down the Root Radio. I've some questions about this if someone tested the below scenarios:
    (1) If the .11b/g radio has been shut down, will it stay shutdown and never comeback unless an administrator do it manually? Is there an automated feature like the switches 'errdisable recover cause' method?
    (2) Is there a command like 'show fallback bla bla ..' that will allow us to see that the current radio state has been shut down due to radio tracking?
    B.Regards
    Mahmoud

    Yes, these model you can configure as Root/Non-Root as long as you have an autonomous image loaded. Most of the time feature is depend on the software code.
    Release notes available at below URL for details of the supported/unsupported features of each software version.
    http://www.cisco.com/en/US/products/ps12555/prod_release_notes_list.html
    Here is one basic config example of Root/Non-Root using different AP model, but it may help you to get basic config done for these AP model as well.
    http://mrncciew.com/2013/11/09/wireless-bridge-with-eap-fast/
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • Link-local multicast on autonomous APs

    Hi,
    I have a 877 which I am troubleshooting some mDNS (224.0.0.251:5353) issues.
    One client sends a mDNS request, the router sees it (packet debug) but the packet is not received by any other client on the wireless LAN.
    Given it is link local I don't believe that enabling PIM (which I have done anyway).
    I have investigated if there is anything that I would have to do to enable multicast for my wireless clients, on WLCs there is a multicast and broadcast config command which explicitly enables it.
    Any directions would be appreciated.
    Regards
    Adam

    Make sure that do not use the 239.0.0.X address range or the 239.128.0.X address range. Addresses in these ranges overlap with the link local MAC addresses and will flood out all switch ports even with IGMP snooping turned on.
    Use the show network command to verify the multicast mode on the controller and show lwapp mcast to verify the group on the AP. I hope it may help you

  • Autonomous APs and Roaming

    Hi,
    is it possible to configure auonomous APs to allow clients to roam between them?
    Thanks, Pat

    yes, this is totally possible.
    if you are using a PSK, then all you need to do is configure the AP exactly the same way, with the exception of the IP address on the BVI interface.
    if you are using 802.1x, then you would want to configure WDS for the key caching.
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801c951f.shtml#step1
    HTH,
    Steve
    Please remember to rate useful posts, and mark questions as answered

  • MAC Authentication on autonomous APs

    Hi!
    Has anyone here tried MAC authentication using Aironet 1200 series? If so, can you please tell me how to do it? Because I've been trying to make it work and it just won't work. Thanks!
    Regards

    Hi,
    Are you talking about radius mac-authentication ?
    The steps to configure MAC authentication on the ACS server and AP :
    [1] GO to Server Manager
    In the Corporate Servers -->Current Server List
    -- Select the Radius Server in the drop down.
    -- Specify the Server IP address in the Server: field
    -- Specify the Shared Secret in the Shared Secret: field
    -- Set the Authentication Port (optional): 1645 and the Accounting Port (optional): 1646
    - click on Apply
    -- In the Default Server Priorities aand under MAC Authentication
    -- In the drop down Priority 1: select the IP address of the ACS server and click on Apply
    [2] Goto SSid MAnager
    -- Select the ssid, In case a new SSID needs to be created create a new ssid.
    -- In Authentication Settings --> Methods Accepted: --> check on Open Authentication:
    --> Select with Mac Authentication from the drop down menu.
    - Click on the Apply all button to save this setting
    [3] Goto Advanced Security
    -- In the MAC Address Authentication -->MAC Addresses Authenticated by:
    -- Select Authentication Server Only and click on Apply
    On the ACS server Create Users with user names and password set to the MAC address of the
    clients. These user names/passwords should NOT have any spaces or dots in between them..
    Regards,
    ~JG

  • LWAPP APs not showing in CiscoWorks

    I recently installed a new WiSM bundle and converted a group of Autonomous APs to LWAPP and now CiscoWorks does not see the APs. Any thoughts on this would be appreciated.

    LWAPP APs don't run SNMP, so CiscoWorks can't talk to them. The informatino CW used to retrieve directly from the APs is now available through the controller. However, I'm not sure CW supports controllers yet.

  • WLAN Project

    I have been assigned a wireless LAN project and need some help with where to start hardware, number of access points and how big the footprint is from each of the WAPs and how many WAPs each of the WLAN controllers can support

    Steve, as Scott mentioned there is no one answer for you. His post is an excellent starting point. He gave you the information you would need to gather to start this project.
    - You need to know exact wall types (dry wall is completely different than cement/brick). You are best off with a predictive site survey tool or some APs and a physical site survey tool to determin actual propagation for the environment. You also need to decide the specs for the site survey.
    - If you want to support VoIP, Cisco has some good documents with specific wireless VoIP requirements.
    - If you only want data, what minimum data rate do you want?
    - The type of mounting surface will often determine the type of AP. If it is a wall mount but you need 360 degree coverage, I would go with 1241ag APs. If it is ceiling mount, 1131s are great. For uncontrolled areas, 1241s are great because you can mount them in a NEMA enclosure.
    - The quantity of APs, budget, and the network layout might help determine if you should go with autonomous APs or LWAPP ones. Usually I go with LWAPP for easy of ongoing support, but there are always exceptions.
    We are not trying to be difficult here. This is just how it is. Companies make a lot of money on site surveys, but it is not for nothing. There are a lot of factors that must go into planning, or the project will flop.
    Hope this helps,
    Eric

  • Covert LWAPP AP to autonomous possible?

    Hi Sir,
    I understand that I can convert autonomous AP to Lwapp AP and i know the steps of doing it.
    My customer has lots of LWAPP APs but intend to convert it to autonomous. Can it be done? I find no info on how to convert Lwapp APs to autonomous.
    Pleas advise.
    Thank you.
    Delon

    Hi Delon,
    This is very possible, have a look at the following;
    Reverting the Access Point Back to Autonomous Mode
    It is possible to revert an LWAPP-enabled Cisco Aironet access point back to autonomous mode. Please refer to Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode for detailed instructions on reverting to autonomous mode. Use this URL
    http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp161272
    Converting a Lightweight Access Point Back to Autonomous Mode
    You can convert an access point from lightweight mode back to autonomous mode by loading a Cisco IOS Release that supports autonomous mode (Cisco IOS release 12.3(7)JA or earlier). If the access point is associated to a controller, you can use the controller to load the Cisco IOS release. If the access point is not associated to a controller, you can load the Cisco IOS release using TFTP.
    Using a TFTP Server to Return to a Previous Release
    Follow these steps to revert from LWAPP mode to autonomous mode by loading a Cisco IOS release using a TFTP server:
    Step 1 The static IP address of the PC on which your TFTP server software runs should be between 10.0.0.2 and 10.0.0.30.
    Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 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 c1200-k9w7-tar.default for a 1200 series access point, c1130-k9w7-tar.default for an 1130 series access point, and c1240-k9w7-tar.default for a 1240 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 MODE 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 then release.
    Step 8 Wait until the access point reboots, as indicated by all LEDs turning green followed by the Status LED blinking green.
    Step 9 After the access point reboots, reconfigure it using the GUI or the CLI.
    From this doc;
    http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp161272
    Hope this helps!
    Rob
    Please remember to rate helpful posts.......

  • LWAPP and Autonomous

    hello friends,
    I need your help. We have a 4402-12AP and a 1121G outside the unified wireless network.
    There are 2 vlans confgured on the WLC4402, 101 & 102. The ap-manager, management interface and AIR-1000-AP are on the vlan101. The port on the switch for the management interface is configured as a trunk with 101,102 allowed.
    The 1121G is configured with those vlans with trunk configured on the switch too.
    The problem is that when I associate to the 1121G i can't see the clients of the Unified WLAN.
    Any help would be appreciated.
    Thank you.

    Hi,
    I believe you need to examine the configuration of the switch port your LWAPP is connected to. Here is the documentation:
    "While Cisco WLCs always connect to 802.1Q trunks, Cisco lightweight APs do not
    understand VLAN tagging and so should be connected only to untagged, access ports on
    the neighbor switch. This is fundamentally different from how autonomous APs connect
    to switches, which must be connected to 802.1Q trunking ports."
    Hope this helps. Please let us know if this answers your problem.
    Best,
    Paul

  • Convert AP to LWAPP

    Hi,
    We recently purchased a few more 1131 APs for a remote office. For some reason, only one came as LWAPP AP, and the rests are all Autonomous APs.
    I have successfully upgraded one Auto AP into LWAPP, it is under control of that office's WLC.
    The image I downloaded is the latest one : c1130-rcvk9w8-tar.124-10b.JA3.tar, I am not too sure if I should have used c1130-rcvk9w8-tar.123-11JX1.tar
    However i noticed that the product ID still shows up as AIR-AP1131AG-E-K9 instead of AIR-LAP1131AG-E-K9 like the one came with LWAPP. How to fix this, is this matters. Any help will be highly appreciated.

    The image you used is fine for the conversion. The AP will use the code it gets from the controller anyway, so you don't need to worry there.
    And sorry, but the product ID never changes. The AP was an AP when it was produced, and it will forever remain an AP. It cannot become an LAP, at least as far as the product ID is concerned.

Maybe you are looking for