Lightweight access-point joined the wireless controller but no radio channels

a customer  wireless controller 2106  he use  access-point AIR-LAP1252G-E-K9  the access point the leds indicate
etherner and radio is blinking green and status is green.
please help i am in the customer company now

The AP1252 has higher power requirements than some of the Cisco PoE switches provide.  Depending on the switch you are plugging them into you will get enough power to power up the device and connect to a controller but not enough to power up the antennas.  Options that can work include:
1) Removing one of the antennas if you are not gonig to use it (or as a temporary workaround to get some wireless)
2) Using an external power supply
3) Using an external inline power appliance system that supplies enough power (http://www.microsemi.com/powerdsine/ is one example).
4) Depending on the type of switch you are connecting to you may be able to upgrade code to provide a higher amount of power to the port.  For instance, a Catalyst 6500 by default supplies 15.8 watts of power to a port.  But if you upgrade the code to 12.2(33)SXH2? I believe you can get 16.8 watts of power and this is enough to bring up both antennas on the AP.  But even then you don't have enuf power to run the upper N speeds - I think anything above 72 Mbps is unattainable.
Other AP models such as the 1140 have lower power requirements and may work better for you.

Similar Messages

  • Manually add Access Point to 2504 Wireless Controller

    We have a 2504 Wireless Controller and it works great!
    We currently have 6 Access Points (Aironet 1252) connected.
    We just added the sixth one a few weeks ago and with a properly configured and fully functioning Wireless Controller, it was super easy.
    Now, I have been assigned to add another Access Point, but at a remote site.
    The plan is to have up to three or more APs at this remote location and we want them to talk back to the Wireless Controller.
    We have plenty of licences on our current Wireless Controller.
    Do do not want to spend the funds for another Wireless Controller and more licenses.
    1. How does one manually add a Aironet 1252 to the 2504 Wireless Controller
    2. If the AP is on a different subnet than the Wireless Controller, how does one get it registered?
    3. The best for last: Can a Aironet 1252 talk to a 2504 Wireless Controller over a WAN link?
    If so, how?
    Thank you!
    Bryan Smith

    Here are some links
    AP join
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
    FlexConnect
    http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_flexconnect.html
    Sent from Cisco Technical Support iPhone App

  • Can I use the Ethernet Port for a computer when it is also used as a wireless network with an Airport Extreme as the access point for the wireless network

    Can I use the Ethernet Port  of the A1264 Airport Express to connect to the Ethernet port of a computer that does not have wireless capability when the Airport Express is also used on a wireless network with an Airport Extreme 5th generation as the access point for the network?
    I have AE 5th gen
    looking to buy (from ebay) the AEX A1264
    Various computers, printers and hubs for the network
    Is this possible to do?

    Bob, Thanks for the info. I have read different articles that said yes, but I wanted to make sure before I commit to buy. I have an older A1084 which I could not use the Ethernet port. I know at one point I was able to when I was on 10.4. Now that I am on an Intel processor and 10.8 I am going to have to upgrade some of my Apple wireless hardware.
    Thanks Again.

  • 3750G - cannot access GUI on the wireless controller

    I am not able to access the GUI of the wireless controller - If I console into the wireless controller I can ping the management IP address but if I console into the switch I cannot ping the wireless controller.
    I think someone may have screwed up the configuration files - is there somewhere I can download the "factory" configuration from?

    To recovery to factory default, you will need to be on the console of the controller, and reboot. Once you are at the user login prompt you can login with recover-config, this will reset the controller to factory defaults. Prior to doing that, hit the CLI from the console port, and issue the command show interface summary. Take a look at the VLAN assigned to the management interface. Then take a look at the switch, and look at Port-Channel 40, should be there by default fo for the port channel to the controller. Want you want to check for is, the native VLAN on the port-channel. This is a dot1q trunk, so if they are tagged the same on both sides traffic will get dropped. For example, if you are using 10.20.1.2/24 for the management interface and this is VLAN 20, then on the port channel you should have switchport trunk native vlan 20, and on the controllers management interface you would want to set the VLAN for 0, untagged. If you need to change this from the CLI of the controller, first issue the command config wlan disable 1, to shutdown the first wlan, then issue the command config interface vlan management 0, this will set the management interface to be untagged. Once you have done this, try to access the GUI again. Once in, you can make the same change to the ap-manager, if it is on the same VLAn as the management.
    Steve

  • Access points As a Wireless Controller

    Dear
    I need a proposal for the fully meshed 9 wireless access points. In which 
    One can behave as wireless controller
    Dual Radio connectivity
    Poe on each AP or extra port of Ethernet
    Warm Regards
    Hassan Sarfraz Ali

    I see what you're asking, Since virtual controller concept is evolving and no one wants single point of failure i.e., single controller for smaller deployment and remote offices, what you're asking is quite logical for local and flex mode. For Mesh, considering awpp convergence may not suite is what i believe.
    Until 7.3 Cisco don't have this feature. Whatever you're looking could be what Cisco's future making or already work in progress, you may want to check with Cisco via TAC.

  • Can you hard code the speed and duplex on lightweight access points

    I have a client that want to set the spped and duplex on the switch port. Is there a way you can configure the fastethernet port on a lightweight access point for speed and duplex.

    Try this step
    configure terminal
    Enter global configuration mode.
    Step 2
    interface fastethernet0
    Enter configuration interface mode.
    Step 3
    speed {10 | 100 | auto}
    Configure the Ethernet speed. Cisco recommends that you use auto, the default setting.
    Step 4
    duplex {auto | full | half}
    Configure the duplex setting. Cisco recommends that you use auto, the default setting.
    Step 5
    end
    Return to privileged EXEC mode.
    Step 6
    show running-config
    Verify your entries.
    Step 7
    copy running-config startup-config

  • Is Cisco air-ap1230a a lightweight access point?

    Is Cisco air-ap1230a a lightweight access point? Can it be use for the new CCNP training?
    Thanks

    Hi Bao,
    The 1230 is not a Lightweight AP, but can be upgraded to LWAPP with the A Radio model listed below (Note that this model is EOS/EOL) this is probably not the best choice for your studies;
    Solution Requirements
    Migration from autonomous access point mode to lightweight mode is possible on these Cisco Aironet access point platforms:
    All 1130AG access points
    All 1240 AG access points
    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.
    All 1310 AG access points
    From this good doc;
    http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html
    Cisco Aironet 1200 Series Access Point Ordering Guide
    http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00800c9435.html
    EOS & EOL for the Cisco Aironet 1200 Series 802.11a Access Points
    http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_eol_notice0900aecd801e5303.html
    Understanding the Lightweight Access Point Protocol (LWAPP)
    http://www.cisco.com/en/US/netsol/ns340/ns394/ns348/ns337/networking_solutions_white_paper0900aecd802c18ee.shtml
    Lightweight Access Point FAQ
    http://www.cisco.com/en/US/products/ps6306/products_qanda_item09186a00806a4da3.shtml
    Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC)
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
    **You are probably better off with something like the LAP 1131. Have a look here;
    http://www.cisco.com/en/US/products/hw/wireless/products_category_buyers_guide.html#access_points
    Hope this helps! I noticed your other post regarding the WLC suggestions and have responded there as well :)
    Rob

  • Access point not online on controller

    Hi,
    I have been trying to get a 1262AP registered to wireless lan controller.
    The core switch has three 2 vlans in it, management which is vlan 41 and AP interaction vlan which is vlan 51.
    Controller also has both these vlans.
    Vlan 41 - 192.168.40.x/23 ( management vlan)
    Vlan 61 - 192.168.61.x/24 (AP vlan)
    WLC management interface IP is 192.168.40.18
    WLC AP interface IP is 192.168.6.241
    Now , during the initial steps, the access points are attached to the switchports on vlan41, wherein they get the dhcp ip from the temporary pool created on the controller and get registered.
    But, these access points in actual environment needs to be on static ip address. When it's ip is changed to a static IP address from the controller , it fails to register to the controller. the switchport is put on vlan6 as access port , after  static ip is assigned to the access point.
    The error i receive is ;
    %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1
    the core switch we are using in this new setup is a 2960 with a lanbase image. I realised the switch is not routing enabled. it doesn't accept the command "ip routing". Will this be creating a problem for the access points? 
    From the switch , the controller management and AP vlan IP address can be pinged. similarly, from the controller, AP and management vlan interface ip address of the switch can be pinged.
    Please help.

    Did you get it to work?  The thing you have to understand is how the AP is able to join the WLC and the process the AP goes through to try to join.  Here is a document that will help you understand the process and the various ways an AP can join or find the WLC.  The easiest almost fool proof way is to place the ap in the same subnet as the management of the WLC.  If the AP joins, then the AP will know of the ip of that WLC it joined or any in the mobility group if defined.  Take a look at the doc as it explains it better than I can:)
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
    Thanks,
    Scott
    Help out other by using the rating system and marking answered questions as "Answered"

  • Connection between lightweight access point and switch?

    Hello everybody,
    I am a bit confused about cisco 1000 series access point connection. On wireless lan controller and lightweight access point basic configuration example document id 69719 (http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a0080665cdf.shtml), I understood the access point has two vlans associated with (vlan 3 and 4). Am I correct?
    Why is connection between access point and catalyst port just access port rather 802.1q trunk? How vlan traffic can traverse from the access point to controller?
    Please advice.
    Many thanks,
    Nitass

    Nitass,
    The AP itself does not need to be a trunked port, but the uplink to the controller does. When using a Lightweight enviroment, all the traffic passes thru an encrypted LWAPP tunnel from the AP to the controller, and then gets sent out the correct VLAN interface on the controller.

  • Access Points Joining Random WLC

    My environment contains 4 seperate controllers.  1 controller in the datacenter which remote offices use with HREAP and discover this WLC using DNS  We will call this Controller WLC1.  2 more controllers (WLC 2 and WLC 3) in the corporate headquarters to support >40 access points in a N+1 configuration and finally an anchor controller which doesnt matter in this post.
    What I am experiencing is Access points in the Corporate office are using DHCP option 43 to discover the WLC2. every night or after long periods of time a random number of my access points are either rebooting or most likely sleeping.  Then are attaching them selves to WLC 1 which is in the datacenter and is not supporting DHCP from that location which to clients make the wireless network seem to be down.
    I think that with using a hybrid of DHCP and DNS is partly my issue but it shouldnt be. I have primed all the Access point to look at primary controller WLC1 and secondary controller WLC2 both by name and using the IP address of the respective management ports.
    Can there be any explaination for this and why this seems to be so random?
    WLCs are 5508
    Corporate Access points are 1142
    ***EDIT
    After some more investigation this isnt completely random rebooting the access points in question are connected to a new 4506-E chassis with the Sup 6-E while the other access points are connected to a 6509-E.. not sure how much this matters but I am seeing in the access point logs that about every 2-3 hours they are accessing DHCP again and sometime not successfully.  Is there some EnergyWise or power savings happening on the 4500 possibly??

    I understand that all and here is a screen shot (see attached) of an ap that was on WLC 2 last night at midnight when i wrote this orginally and now how jumped to WLC 2..  The major issue here is that WLC 1 does not give out DHCP because it is used for HREAP and remote office that have other local DHCP servers.
    I am running code 6.0.199.4
    Now yes all controllers WLC1,2,and3 are in the same mobilty group.  Maybe I should move the WLC1 out of the mobility group and that might solve the issue.  Here is a log too.  See timing is 3 hours and then its trying to find another controller.  I see a retransmission count exceeded here. What can cause that?  I have 4 port LAG configured on both WLC2 and WLC3 and they are both on seperate 6500 switches.  This access point is on a seperate floor connected to a 4500 with uplink to each of the 6500's
    **********LOG from Access Point***********
    *Oct 14 02:41:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.104.210.21 peer_port: 5246 This Is correct
    *Oct 14 02:41:21.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 
    *Oct 14 02:41:21.826: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.104.210.21 peer_port: 5246
    *Oct 14 02:41:21.827: %CAPWAP-5-SENDJOIN: sending Join Request to 10.104.210.21
    *Oct 14 02:41:21.827: %CAPWAP-5-CHANGED: CAPWAP changed state to  
    *Oct 14 02:41:21.911: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Oct 14 02:41:22.047: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
    *Oct 14 02:41:22.052: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
    *Oct 14 02:41:22.173: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller nwcp01-1211-02b
    *Oct 14 02:41:22.254: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[0]
    *Oct 14 02:41:22.255: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to WMM is not enabled
    *Oct 14 02:41:22.257: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[0]
    *Oct 14 02:41:22.259: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[1]
    *Oct 14 02:41:22.261: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[1]
    *Oct 14 02:41:22.263: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to WMM is not enabled
    *Oct 14 02:41:22.263: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 2 due to WMM is not enabled
    *Oct 14 02:41:22.264: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 2 due to WMM is not enabled
    *Oct 14 02:41:22.274: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
    *Oct 14 05:57:40.164: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_ECHO_REQUEST
    ., 3)
    *Oct 14 05:57:40.164: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
    *Oct 14 05:57:40.164: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.104.210.21:5246  *** This is correct
    *Oct 14 05:57:40.206: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
    *Oct 14 05:57:40.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 14 05:57:40.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Oct 14 05:57:50.229: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Oct 14 05:57:49.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.98.10.20 peer_port: 5246 **This is the controller it should never get on.
    *Oct 14 05:57:49.000: %CAPWAP-5-CHANGED: CAPWAP changed state to 
    *Oct 14 05:57:49.844: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.98.10.20 peer_port: 5246
    *Oct 14 05:57:49.845: %CAPWAP-5-SENDJOIN: sending Join Request to 10.98.10.20
    *Oct 14 05:57:49.845: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
    *Oct 14 05:57:49.930: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
    *Oct 14 05:57:50.078: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
    *Oct 14 05:57:50.078: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
    *Oct 14 05:57:50.206: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller nep00WLC00e
    *Oct 14 05:57:50.293: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[0]
    *Oct 14 05:57:50.298: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[0]
    *Oct 14 05:57:50.303: %LWAPP-3-CLIENTEVENTLOG: SSID Roswifi added to the slot[1]
    *Oct 14 05:57:50.309: %LWAPP-3-CLIENTEVENTLOG: SSID RosGuest added to the slot[1]
    *Oct 14 05:57:50.414: %WIDS-6-ENABLED: IDS Signature is loaded and enabled

  • Access points joining different WLC

    hi
    i have a wireless controller module( NME-AIR-WLC25-K9) installed in a Cisco 2851 ISR, this setup is in my remote site, we are connected through MAN network. In our main office i have a cisco 4402 wireless controller. so whenever i install a AP in my remote site instead of joiining the remote site WLC, the access point joins my main office 4402 controller, i dont why it is happening, the AP is not even trying to join the remote site WLC.. i have not configured high availability and both these controller are in separate RF network.
    the firmware version in NME-AIR-WLC25-K9 is 7.0.98.0 ...
    the version in the other controller is 6.0.196.0
    Please let me know what is else i need to check asap
    Thanks
    karthik

    Hi,
      Did you even see the AP trying to join the local controller?  If the controller are in different domains, the AP will prefer the remote controller since it join that one first.  Since you are running 5.2, try configure on the AP the primary controller with the name, and local IP address of the local controller, and then reboot the AP.  See if after that the AP join. run debug capwap events enable to see if you see the AP event trying to join the controller.
    Regards,
    Manuel

  • Is there any way I can control which specific access point I connect (and stay connected) to from amongst a set of access points with the same SSID?

    I'm working from a boat in a harbor in which the ISP has deployed numerous access points around the periphery.  All the access points share the same SSID and each is configured to use either channel 1, 6 or 11.   From my location, there are over a dozen of these access points "visible" (based on the the output of WiFi Scanner) with a range of RSSI and S/N values that vary over time.
    The ISP has told me that the quality of my connection should be "perfectly fine" for any access point with an RSSI value better than -75, but I know from experience that my connection quality is miserable (i.e. < 50Kbps download) for almost all of these, including those with RSSI values better than -75.  There is at least one exception, however, which gives me on the order of 2Mbps download, which is "great" in this context.
    I've tried using a more powerful USB antenna plugged into my MacBook Air (mid 2011), but as far as I can tell, it really doesn't make much difference.  Neither does my location within the boat.   The overriding factor seems to be which access point I happen to connect up to.
    I should point out that the closest access points are about 75 yards away, with many of them being several hundred yards away or more.  I'm guessing that even though the signal strength of some of the distant access points is causing them to get "chosen" some times, the results are unacceptable due to the distance.
    I'm hoping that I can determine, through experimentation, which access point(s) provide(s) acceptable performance and then configure my Mac to limit my connection to those points through whatever mechanism I need to use (e.g. channel, MAC id, etc.).

    Establishing a wireless connection with a client computer is left to the access point for various reasons. One reason that your Mac may not connect to the strongest access point is that it may have reached a limit of the number of clients it can serve, leaving it unable to accept a connection with another. The limit may not be very large.
    Suppose that happens, and your Mac establishes a connection with a more distant access point having a weaker signal. Then, suppose a client drops off the network. Doesn't this mean your Mac will switch to the stronger access point? Not necessarily. The throughput delivered to and from your Mac would have to drop below a threshold specified in the AP for it to drop the client, leaving your Mac free to connect with another one. The reason for this is to prevent rapid switching from one AP to another in an area in which two signals are of approximately equal quality. If that were to occur the frequent and repetitive handshaking between the two devices would slow throughput to zero.
    In an environment in which several access points are broadcasting the same SSID, Apple provides no insight as to how it determines which access point to choose. This is the reason I suspect this "choice" is a function of the router, or access point. The connection originates with it, not the Mac.
    Now, what would solve your dilemma would be to determine a way to control the access point with which your Mac connects, by specifying the access point's unique MAC address for example. In this happy circumstance, you could maintain an editable "whitelist" or "blacklist" of the harbor's access points and be able to choose which among them you prefer.
    I do not believe OS X maintains such a record of MAC addresses though, only those of the routers it uses. If I am correct about that, such a solution is unlikely to exist. Don't let that discourage you from searching for one though... I would concentrate on something like "selecting access point by specific MAC address".
    I did find this patent application though:
    Roaming Network Stations Using A Mac Address Identifier To Select New Access Point
    Perhaps it's a start

  • Is there a way to configure win 8 Laptop to airport express?  I can see theN connection to the wireless network, but troubleshooter suggests there's t

    Is there a way to configure win 8 Laptop to airport express?  I can see the connection to the wireless network, but troubleshooter suggests there's there is no gateway and of course no internet. The connection
    shows limited.  Any help you could provide would be most appreciated.  Further, should I simply buy another router for the windows machine?  If I did that, would it interfere with the airport?

    The internal HDDs must be formatted in either EXT3 or EXT4 file system because NSS uses Linux OS.  This is mainly because the RAM designed to fit with the customized Linux OS's size.
    You can connect to an external HDD via a  USB or eSATA port. The external HDD's file system can be NTFS, FAT32, AFT or EXT3/4 to be recognized for read/write. You can connect a 2TB USB/eSATA drive connec to the NSS via USB port to format your HDD for NTFS, AFT, FAT32, or EXT3/4 partition.
    You can join the NSS to a Windows domainr so all domain users to access NSS. You cannot replace the NSS for the Windows 2003 SP2 server. They are two different products and do different jobs. Windows server is features sets server while the NSS is the files/data server.
    Hope that helps!!

  • APs join the wrong controller

    When I set up access points , for some reason some of them want to join the wrong controller. I have set the dhcpd option 43 as well as have the dns name in our server. We are running the 4.0.179.11 version of the software. Also, two access points that were on the correct switch, are now on the wrong one. Anyone have any ideas what I am missing?
    Thanks in advance.
    konrad

    Hi Konrad,
    Have a look at the methods the AP uses to determine which of the WLC's to register to;
    WLCs embed this important information in the LWAPP discovery response:
    The controller sysName
    The controller type
    The controller AP capacity and its current AP load
    The Master Controller flag
    An AP-manager IP address
    The LAP uses this information to make a controller selection, with use of these precedence rules:
    If the LAP has previously been configured with a primary, secondary, and/or tertiary controller, the LAP examines the controller sysName field (from the LWAPP discovery responses) in an attempt to find the WLC that is configured as primary. If the LAP finds a matching sysName for the primary controller, the LAP sends an LWAPP join request to that WLC. If the LAP cannot find its primary controller or if the LWAPP join fails, the LAP tries to match the secondary controller sysName to the LWAPP discovery responses. If the LAP finds a match, it then sends an LWAPP join to the secondary controller. If the secondary WLC cannot be found or the LWAPP join fails, the LAP repeats the process for its tertiary controller.
    The LAP looks at the Master Controller flag field in the LWAPP discovery responses from the candidate WLCs if one of these items is true:
    No primary, secondary, and/or tertiary controllers have been configured for an AP.
    These controllers cannot be found in the candidate list.
    The LWAPP joins to those controllers have failed.
    If a WLC is configured as a Master Controller, the LAP selects that WLC and send it an LWAPP join request.
    If the LAP cannot successfully join a WLC on the basis of the criteria in step 1 and step 2, the LAP attempts to join the WLC that has the greatest excess capacity.
    From this good doc;
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
    Hope this helps!
    Rob

  • Shuting down an lightweight access point

    We setup an access point at a remote location as a test.  We would now like to remotely shut it down.  Is there a way of shutting down an access point (lightweight) remotely to free up its AP license off of our controller?
    I appreciate any suggestions.
    Thanks

    Hi,
    1 - If you have remote access to local switch to whom your access-point (POE) is connected, just shutdown that port, by this way you can power-off the access-point.
    2 - As far as AP license off is concern
    If you have licensed DTLS image on your controller then AP license off of controller can be achieve by disabling the DTLS of the specific AP by controller.
    you can enable or disable DTLS data encryption for a specific access point or for all access points using the config ap link-encryption {enable | disable} {Cisco_AP | all} command

Maybe you are looking for