Cisco Air Lap521g A K9 Manualidades

Cisco Wireless Access Points; Cisco Servers & Bundles; Cisco Bundles; Cisco Modules & Cards; Cisco Transceivers. Cisco Wireless Access Points Aironet 500 & 1000 Series Aironet 1100 Series Aironet 1200 Series.

I have a TAC case opened and they have been looking at this for a few days with no resolution so I thought I would post here. I converted a 521 LWAP to standalone due to a design change (no controller and smaller office space).

I loaded the latest code and also tried 1 rev back (yes, I re-downloaded image to check for corruption. Also, the image appears to save and decompress to flash with no obvious errors). It is running default configuration. I have used multiple browsers to try to access the web GUI to configure via express service page and when clicking the apply button, the page doesn't update and 'error page page' appears in lower left of browser window. Nothing can be configured via express service page.

There are also other pages where settings cannot be configured, but I assume they are all related and I won't detail here. Additionally, I have tried to access via CCA with credentials admin and Cisco and authentication always fails. Also tried Cisco Cisco and cisco Cisco, etc. I can log in the web gui with username and Cisco password. I tried adding a username admin and Cisco for CCA, but authentication still fails.

I used the following command to load the software: archive download-sw /overwrite t I'm using code: c520-k9w7-tar.124-10b.JX.tar and tried c520-k9w7-tar.124-3g.JX1.tar Has anyone seen this behavior before? Thanks in advance. Hi Cndpope, According to the wireless AP Q&A section from

The hardware for the standalone and controller based products is the same. AIR-AP521G-x-K9 (standalone access point). AIR-LAP521G-x-K9 (controller-based access point) The products have different software, but the access points can be converted from standalone mode to the controller-based mode with a simple software upgrade. But no where have i seen it could be converted from controller based to standalone. If i am wrong I'm sure a colleague will correct me, but I think once converted to controller based, you cannot convert back to Standalone mode. I beleive that is why you are having difficulty. Good luck Dave.

@Jason, The firmware you want is under that link you sent, but follow the link for IOS. Then click latest version and on the right, the two IOS's will standalone and the lwap recovery files.SEE COMMENT BELOW BEFORE PROCEEDING- HOWEVER, please let me save you some time. I have worked with 2 different TAC teams and finally have Cisco's position on this: The Lightweight to Standalone conversion is considered a 'back-door hack' and will not be supported as of my case at end of September '09 (things could change if the programmers decide to fix, but see below!). This is unlike the enterprise versions of APs which can be converted as many times as you want to load the OS (so I've heard). After loading the new OS, it breaks the web gui pages as well as shows up as unsupported in CCA. The reason it shows up as unsupported in CCA is because CCA is looking for part number AP521 instead of LAP521 - therefore it doesn't know what to do with it.

So once you convert, you will not have access to web gui or CCA to configure. You may, however, still be able to configure via CLI, but I didn't want to chance that there would be anomalies with configurations in the future. Plus, my client is expecting to be able to see and configure via CCA in the future. TAC and marketing say they are building this for SMB and CCA will be the main interface to configure the APs. I had been told by my distributor's Cisco person that as long as smartnet was on the device, they would support converting standalone to lightweight and lightweight to standalone. TAC says this is not the case.

Perhaps disti is just used to enterprise grade. I was able to get mine RMA'd because of this situation, but I don't know they will be doing that for everyone. I recommend sending back to Disti first. If you can't do that, then try to convince TAC to swap out. It's apparently an issue for TAC to be able to RMA a different part number (AP521 vs LAP521) since an RMA will obviously normally be the same part. By the way, I tried the most recent version and one rev back.

Both tftp without errors, but the newest will show a very short 'input error' of some sort at boot. The older rev didn't do that, but regardless of that error on boot - neither was configurable via web gui or CCA. Oh, and I tried this on 2 brand new LAP's, so it wasn't just my one AP that had the issues.


This document explains how to manually set or reset static configuration information on IOS and ClickOS Access Points (APs)



Cisco recommends that you have knowledge of these topics:

  • Basic knowledge of the configuration of CAPWAP APs and Cisco Wireless LAN Controllers (WLC)

  • Basic knowledge of Control And Provisioning of Wireless Access Points protocol

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco 5520 WLC that runs firmware release

  • Cisco AIR-CAP3702I-E-K9 Series AP

  • Cisco AIR-AP4800-E-K9 Series AP

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.


Refer to Cisco Technical Tips Conventions for more information on document conventions.

Manually configure the AP

In a new installation, when an AP is unable to find a WLC using the discovery algorithms, you can statically configure the information necessary to join a controller via the console port and the AP’s Command Line Interface (CLI). Refer to Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC) for more information on the WLC discovery algorithms and the LAP registration process.

In order to manually configure static information on a LAP using the AP CLI interface, you can use these EXEC mode CLI commands:

Nokia 5130 music player theme download nokia.Ovi.player.(

  • For IOS based APs:
  • For ClickOS based APs:

Note: You must issue these commands while in enable mode. The default enable password is Cisco.

The static information configured with the CLI commands is used by the AP to join a controller. After joining the controller, the user can configure new settings on the LAP via the controller.

Reset the LWAPP Configuration on the LAP

When you move your AP to a different location in your network and the LAP cannot join the previous WLC, or if you want to manually reconfigure the AP to join another WLC, you have to enter the new controller information in order to allow your AP to associate with a different controller.

Reset LAP through WLC

In addition to the previous methods, you can also reset the configuration of the LAP from the WLC. When the LAP is registered to the controller, you can use these commands from the controller in order to reset the configuration on the LAP:

  • Use clear ap config <ap-name> keep-ip-config How to crack steam accounts 2017. command in order to clear all of the AP's configurations to default, except for the AP's static IP configuration.

  • Use clear ap config <ap-name> command in order to clear all of the AP's configurations to default, which includes the AP's static IP configuration.

Reset LAP through CLI

In order to use that method you need to login to AP console mode in priviledge exec mode:

  • For IOS based APs:
  • For ClickOS based APs:

Reset LAP through with reset button.

In order to use that method you need to have physical access to AP. Process is the same for both IOS and ClickOS APs.

  1. Disconnect power from AP.
  2. Press and hold 'Mode button' on AP and provide power to AP.
  3. Keep mode button hold for 20seconds or more.
  • On IOS based APs:
  • On ClickOS based APs:

How to Disable the Reset Button on the AP Registered to the Controller

In order to disable the reset button on the AP registered to the controller, use this CLI command:


You can use this debug command on a LAP with a console port to troubleshoot problem related to IP address assignment:

  • On IOS based APs:
    • debug ip udp
  • On ClickOS based APs:
    • debug dhcp events
    • debug dhcp errors
    • debug dhcp packets

Note: If the AP has no console port, it is necessary to take a wired sniffer trace of the port that the LAP is plugged into to see what packets are being received by and transmitted to the LAP.

You can use these debug commands in order to monitor the discovery process through the WLC CLI.

On IOS and ClickOS based APs:

  • debug capwap client events
  • debug capwap client errors
  • debug capwap client detail