WLC 7.0 discontinues CDP support?

I just upgraded to 7.0.98.0 on a WiSM blade and it is telling me that it no longer supports CDP? Whoa is this right? All of my current APs that were on 6.0 and upgraded to 7.0 still have CDP working... but if I get a new AP out of the box that has not been on a controller yet, and join it to the controller.... if I want to make any changes I have to disable CDP. It says that CDP is not enabled on the controller. Sure enough it isn't, but when I tried to enable, it said it wasn't supported.
Please tell me this is a bug and it will be fixed in the next 7.0 release!

ok.... I am now priming some brand new APs out of the box after upgrading to 7.0. During my priming, I give the AP a more user friendly hostname, assign primary and secondary controllers and assign an AP group to the AP.
Now, I like to do this in WCS in a multiple controller environment. So as the new APs come up, they have the default hostname of AP. So in WCS you can sort them by name and find your new APs. Then click on the AP and change your settings... well, when I do that, WCS throws a message at me saying that the config change failed because cdp is deactivated globally on the controller..... which it is. The entire config failed via wcs. no name changes, no primary controllers set, no AP groups set. So, I tried it again and the same thing. So, I went to the controller itself and tried to enable cdp globally..... it said this controller doesn't support CDP!
Well the controller doesn't really need CDP, but I sure would have liked these new APs to have it, so I went to WCS again and did everything over again, only this time I turned cdp off. WCS was happy and pushed the config to the APs and then CDP was no longer active on the APs.
I then went to the controller these APs were associated to and turned cdp back on and everything was fine. The controller does say the cdp is turned off globally, but it allowed me to turn CDP back on.
Then I primed another batch but this time just used the controller directly and skipped WCS. All was well.
Kind of a weird interesting thing. Not sure where the issue lies. It appears that the controller doesn't want to support CDP on 7.0... at least a WiSM running 7.0. WCS 7.0 is wanting the controller to have cdp turned on globally before it pushes a config to an ap that has cdp turned on, but the controller itself doesn't seem to care.
What I would like to know is does the Wism really not support CDP and why does WCS throw up at that when the controller is ok with it?

Similar Messages

WLC 5760 centralized mode Flexconnect support?

Hi all,
I am currently digging through the documentation about the 5760 WLC and converged access mode and found one particular information, which I need more clarification for.
This is the link
http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps12598/qa_c67-726507.html
And here the specific snippet:
Q. What deployment modes can the Cisco 5760 WLC and Cisco Catalyst 3850 support?
A. The Cisco 5760 WLC can operate in centralized mode (also known as local mode) as well as converged access mode, whereas the Cisco Catalyst 3850 operates in converged access mode. At this time, there is no support for office-extend access points, indoor or outdoor mesh, or FlexConnect access points on the Cisco 5760 WLC and Cisco Catalyst 3850.
Now my questions are:
Does this apply to the converged access mode only or also centralized mode?
Do 5508/WiSM2 WLCs still support APs in the specified modes even when using the new mobility architecture?
When is it planned to add support for the new platforms, if at all?
Hoping for some answers!
Regards,
Patrick

Hi Patrick,
Why not post your question here;
https://supportforums.cisco.com/thread/2220448
There's an open forum Converged Access Q&A session on the go direct with Cisco...
Richard

Adobe Reader Browser Integration after Google and Mozilla Discontinue NPAPI Support?

Hiya everybody,
as you may have heard, the Chrome and Firefox dev teams plan to discontinue supporting the (NP)API which has traditionally been used to load an Adobe Reader document into a browser window instead of spawning an external Reader instance.
Although there are some alternatives on the market, Adobe Reader still remains the best tool for certain uses such as filling forms, 2D barcodes and PDF/A files so some folks still need Reader to work from within their browsers.
What are Adobe's plans concerning this matter? Will they just drop their native browser support or will there be some kind of replacement for the NPAPI plugin?
Regards.
Chris

Yes I can create a short cut to internet exp. 32 bit on my desktop and I can even be using Internet expl. 32 bit, but when I try to open a PDF with adobe reader it won't work with internet exp. as my default browser b/c windows will always choose Internet exp. 64 bit which isn't supported yet by adobe reader. With google chrome as my default browser windows can't choose an unsupported 64 bit browser in its place b/c google chrome doesn't have a 64 bit version.
My post was for those people who may not have realized yet that windows would not ever choose Internet expl. 32 bit over Internet expl. 64 bit if both exist on their system. For them it is easiest to just choose a default browser that only has a 32 bit version.
If I understood your reply correctly, you were telling me how to create a shortcut to Internet exp. 32 bit on my desk top. However, having that shortcut on my desk top and opening my browser through it will not prevent the problem of windows choosing my Internet exp. 64 bit browser for pdf's I try to open from the web. Thank you for your response, but I think the problem that I have tried to explain does exist for many users and can only be fixed by using a 32 bit browser that is not Internet explorer as your default browser. At some point if windows fixes the update that always chooses Internet expl. 64 bit over Internet expl. 32 bit, then this will all be irrelevant.
Thanks
Sent from my iPod

CDP support on WiSM?? / Switchport trace

I am running WCS with 2 WiSM and 4 4404 WLC.
I just turn on CDP on all switches and router for switchport trace features on WCS.
When I tried to turn on CDP on access points I get message to turn on Global CDP features.   Problem seem to occur when I tried to turn on cdp on access points that are connect to WiSM.   I have no problem with 4404 controllers.
I am running on 6.0.188.0

Let me explain the problem that I have on CDP issue -
When I update access point to change ap name on Wireless Control System and click save, I get error message which is "Failed to enable Cisco Discovery Protocol, Global CDP on controller 10.128.143.24 is disabled."    I have to turn off Cisco Discovery Protocol features on this ap in order to make change.
To turn on CDP, I need to get on Wireless Lan Controller (WiSM) and check CDP features on access point page. WLC did not submit error report.
Work around to change ap name, I have to do the change on WLC home page and run audit to refresh WCS from controller. I can not even use WCS controller templates to make changes on all ap unless I turn off CDP features.
Bug?
On switchport trace -
I am getting error message related to WiSM and CDP.   I will post error message as soon as I see one. (I have not been able catch rogue ap on our network using this method - It is possible that no one is plugging in rogue ap and am seeing lot of AP outside of our network.

WLC 8510 Time Based ACL Support

Hi,
I see something like this in the Data Sheet of 8510 "A wireless policy engine on the Cisco 8500 Series enables profiling of wireless devices and enforcement of policies such as VLAN assignment, QoS, access control lists (ACLs), and time-of-day- based access." I wonder if does WLC 8500 has time-based ACL support, or data sheet is talking about anything else?
Thank you for replies.
M.S.Temelli / Istanbul Technical University

You want a straight answer or you want an answer coming out from the SALES team?
Sales team will say "YES". Will it be effective? Not one bit. You go to Security > Local Policy. You create a Local Policy (and attached to your SSID) and determine what time/day you want specific criterea (like wireless client manufacturer).
However, if you want what time/day you want the SSID to go down or UP, then you'll need something more robust, like a Layer 3 ACL.
If you want something like a time/day you want the radio(s) of the AP to go down/up then you need something like EnergyWise or WCS/NCS/PI.

SG300 Firmware v1.1 Released!! Gets CDP support

Find it here
http://www.cisco.com/cisco/software/release.html?mdfid=283019666&release=1.1.0.72&relind=AVAILABLE&catid=268438038&softwareid=282463181&rellifecycle=&reltype=latest
I don't see a changelog in the release notes, so what else has changed?
The GUI seems noticeably faster
a

The major features in this release are detailed at the following link:
https://supportforums.cisco.com/docs/DOC-17092
1) A full CLI
2) CDP
3) Auto Smartports
4) Q-in-Q
5) Voice deployment automation
6) BPDU guard
7) SCT
Ivor

Does Apple plan to discontinue support/update for 2nd Generation iPod touch as latest iOS release for it is 4.2.1?

I have 2nd Generation iPod touch and latest iOS release for it is 4.2.1. Most of the Apps on iTunes now require iOS 4.3 at minimum. Isn't it outrageous that Apple is not supporting such iOS update for older iPod? Is there plan to discontinue such support?

I have a 2nd generation iPod Touch too and I currently have 24 Apps that I cannot update. Unlike you however, I hold the App developers responsible for the fact that they (the App developers) are not supporting iOS 4.2.1.
It is the App devloper who decides to modify their App so that it then requires a particular version of the iOS. Since a developer can have a free and a paid version of an App, it begs the question why don't they have the older and newer versions.
I now check the requirements for an App before I click on update. If it still only requires iOS 4.2.1, then I can update. If it requires a higher iOS, the I simply don't update it. One good thing is that by now, most of the older Apps are quite stable and bug free, so the update is usually to give something extra. Since I cannot update the App, I simply forgo the "extras".

Can't ping, telnet, SSH or find APs in ARP, but associated to WLC & has clients

Hi All,
I have an interesting problem. I have a Cisco 2504 WLC, and six Access Points that are associated to it. I can reach 4 of the access points, which are connected to Cisco 300 POE switches, but the other 2 I cannot ping, telnet, SSH or find in the ARP table on the network. However, they are both associated to the WLC and as far as I can tell, they have clients associated to them. If I reboot them from the WLC, they find their way back to the correct WLC, and the WLC sees them in CDP, but I still can't access them in any way.
The two problem APs appear to be connected to ports 3 & 4 on the WLC, which are the POE ports. I read some documentation that says that those ports don't support Access Points but basically that you can still connect them and have it work, but don't expect any help from Cisco if you run into problems. I've confirmed that POE is being supplied in the port configs, and I have other sites with WLC's that are configured identically with APs on ports 3 & 4 that are up and not having any issues.
Wondering if anyone has had similar issues and if so, can you shed any light on this strange behavior?
Thanks.

please
https://supportforums.cisco.com/discussion/11288621/2500-wlc-attach-ap

How can I keep my MacBook safe is Apple is no longer supporting Snow Leopard? My MacBook was purchased in 2006 and cannot be upgraded to the newer operating systems.

I have a MacBook which I purchased in 2006. It cannot upgrade to newer operating systems.Since Apple has stopped support to Snow Leopard, how can I keep my MacBook safe? Buying another computer is not an option. Any ideas or suggestions? Many thanks.

Klaus1 wrote:
Apple still sell, and therefore support, Snow Leopard.
For what it's worth, from my reading of the Snow Leopard EULA (and I would assume that there is similar language in the EULAs for all other operating systems, as well), I'm not seeing any obligation on the part of Apple to provide Security Updates of any kind, period/full stop. The wording appears to be completely "use at your own risk." I have no idea whether this "use at your own risk" would survive a legal challenge, or if such a legal challenge would depend on whether or not Apple is still selling (or even giving away for free) an OS, or whether local law would, according to this, override the EULA. Perhaps this is why Apple never formally announces EOL or discontinuance of support for an OS. They can always claim that they are still supporting an OS, whether or not in any practical sense, they are. There was even a very late Flashback detection and removal script which Apple issued for 10.5 well after it was clear that they had stopped supporting Leopard. This hardly constituted ongoing support, but perhaps it was to deter the threat of legal action, or maybe it was simply out of benevolence. I don't know.
Besides that, even when Apple was still actively "supporting" Snow Leopard, which I don't think it is any longer, "use at your own risk" would still have applied to a case where Apple may have been late with a patch, or a response, or an adequate response, to a zero-day threat, such as Flashback was, which was constantly evolving. Many thousands were affected by that, and, to my knowledge, at least, there was no legal action directed at Apple throughout or after that episode. If there was any, I don't think it succeeded.
7. Disclaimer of Warranties. YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, USE OF THE APPLE SOFTWARE AND ANY SERVICES PERFORMED BY OR THROUGH THE APPLE SOFTWARE (COLLECTIVELY “SERVICES”) IS AT YOUR SOLE RISK AND THAT THE ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFORMANCE, ACCURACY AND EFFORT IS WITH YOU. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE APPLE SOFTWARE AND SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE”, WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND, AND APPLE AND APPLE'S LICENSORS (COLLECTIVELY REFERRED TO AS “APPLE” FOR THE PURPOSES OF SECTIONS 7 and 8) HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH RESPECT TO THE APPLE SOFTWARE AND SERVICES, EITHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES AND/OR CONDITIONS OF MERCHANTABILITY, OF SATISFACTORY QUALITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF ACCURACY, OF QUIET ENJOYMENT, AND NON-INFRINGEMENT OF THIRD PARTY RIGHTS. APPLE DOES NOT WARRANT AGAINST INTERFERENCE WITH YOUR ENJOYMENT OF THE APPLE SOFTWARE AND SERVICES, THAT THE FUNCTIONS CONTAINED IN, OR SERVICES PERFORMED OR PROVIDED BY, THE APPLE SOFTWARE WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE APPLE SOFTWARE OR SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT ANY SERVICES WILL CONTINUE TO BE MADE AVAILABLE, THAT THE APPLE SOFTWARE OR SERVICES WILL BE COMPATIBLE OR WORK WITH ANY THIRD PARTY SOFTWARE, APPLICATIONS OR THIRD PARTY SERVICES, OR THAT DEFECTS IN THE APPLE SOFTWARE OR SERVICES WILL BE CORRECTED. INSTALLATION OF THIS SOFTWARE MAY AFFECT THE USABILITY OF THIRD PARTY
SOFTWARE, APPLICATIONS OR THIRD PARTY SERVICES. YOU FURTHER ACKNOWLEDGE THAT THE APPLE SOFTWARE AND SERVICES ARE NOT INTENDED OR SUITABLE FOR USE IN SITUATIONS OR ENVIRONMENTS WHERE THE FAILURE OR TIME DELAYS OF, OR ERRORS OR INACCURACIES IN THE CONTENT, DATA OR INFORMATION PROVIDED BY, THE APPLE SOFTWARE OR SERVICES COULD LEAD TO DEATH, PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE, INCLUDING WITHOUT LIMITATION THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, LIFE SUPPORT OR WEAPONS SYSTEMS. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY APPLE OR AN APPLE AUTHORIZED REPRESENTATIVE SHALL CREATE A WARRANTY. SHOULD THE APPLE SOFTWARE OR SERVICES PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS ON APPLICABLE STATUTORY RIGHTS OF A CONSUMER, SO THE ABOVE EXCLUSION AND LIMITATIONS MAY NOT APPLY TO YOU.
8. Limitation of Liability. TO THE EXTENT NOT PROHIBITED BY APPLICABLE LAW, IN NO EVENT SHALL APPLE BE LIABLE FOR PERSONAL INJURY, OR ANY INCIDENTAL, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION OR ANY OTHER COMMERCIAL DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OR INABILITY TO USE THE APPLE SOFTWARE AND SERVICES OR ANY THIRD PARTY SOFTWARE OR APPLICATIONS IN CONJUNCTION WITH THE APPLE SOFTWARE, HOWEVER CAUSED, REGARDLESS OF THE THEORY OF LIABILITY (CONTRACT, TORT OR OTHERWISE) AND EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OF LIABILITY FOR PERSONAL INJURY, OR OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS LIMITATION MAY NOT APPLY TO YOU. In no event shall Apple's total liability to you for all damages (other than as may be required by applicable law in cases involving personal injury) exceed the amount of fifty dollars ($50.00). The foregoing limitations will apply even if the above stated remedy fails of its essential purpose.
http://images.apple.com/legal/sla/docs/osx_snow_leopard_sec_upd.pdf

Ap not showing up in wlc

Hey All,
i have an AP that is not showing up in the wlc. when i place the WLC on a diffrent vlan to the WLC it shows up in the WLC but once it is placed on the same vlan to the WLC it dosnt show at all. the vlan the WLC on has spare IP's in DHCp so its not that. here is a log from wlc when that AP is not on the same Vlan:
Last AP Connection Failure -
Last Error Occurred Lwapp join request rejected
Last Error Occurred Reason Reachability info not found
client's are joinning up with the AP ( very odd??).
but once it is on the same vlan as the wlc it dosnt show up.
thanks

we are running ver:
7.0.98.0
shows up on the switch for cdp but not on the wlc ( tested in diffrent vlans)
the ap is running
AIR-LAP1231G-A-K9
also the ap has an IP in the 1 vlan but when it goes to the 10 vlan ( the vlan with the wlc on it) in cdp neighbors it still have the ip from vlan 1

Wlc-2504-k9 ap license upload issue

Hi i have 20 access points and wlc controller with 15 ap supported .I got 5 ap license but am not able to upload .
Temproray i have enabled evaluation license which is valid 12 weeks . but when i tried to upload the liecense its giving me error .
Can anybody help me the exact steps .

Hi Breeze,
I think its normal behaviour for Cisco WLCs.
Example: It happend with me.
Old licence was for 15APs
if you add 5 more ap licence to WLC then old Licence will go in inactive state but evaluation License will be in use.
After evaluation period you will get the total 20 AP licence in in use status.
This happend with me.
I think this guy I also have similer issue: https://supportforums.cisco.com/thread/2205144
If you still have doubts or issues then please go for TAC case.
Hope it helps.
Regards

WLC 5508 problem

Hi
I have one 5508 and about 70 Cisco1140 AP and spred around in to about 5 sites.
We use a Microsoft IAS server as radius server with auth from the AD with dot1x and certificate in the clinents to verify the clientents
The clients are IBM and Dell laptops
Some clients loses the connection to the network time to time
I have some errors in the WLC logg
dot1xMsgTask: Jan 18 11:23:34.254: %DOT1X-3-MAX_EAP_RETRANS: 1x_ptsm.c:426 Max EAP retransmissions
exceeded for client 00:24:d7:22:0e:e0
*apfMsConnTask_3: Jan 18 11:21:13.118: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:273 Could not che
ck supported rates. Missing Supported Rate. Length :0. Mobile MAC: b8:ff:61:8f:df:25.
*Dot1x_NW_MsgTask_0: Jan 18 11:15:31.521: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Receiv
ed invalid EAPOL-key M2 msg in START state - invalid secure bit; len 40, key type 1, client 00:21:6a
:50:21:80
*spamApTask0: Jan 18 11:14:34.630: %LWAPP-3-VALIDATE_ERR: spam_lrad.c:9090 Validation of SPAM Vendor
Specific Payload failed - AP 30:37:a6:c9:53:20
*dot1xMsgTask: Jan 18 11:14:19.850: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2914 Max EAP identity re
quest retries (14) exceeded for client 00:1f:3b:16:aa:ef
Decrypt error occurred for clienten 00:24:d7:69:fb:7c using WPA2 key on 802.11a interface of AP e8:04:62:60:a0:10
Any sugestions ?

Looking at the error messages, they don't point to a singlular fault with the WLC, more like a client issue. Below I'll explain the messages you are seeing.
dot1xMsgTask: Jan 18 11:23:34.254: %DOT1X-3-MAX_EAP_RETRANS: 1x_ptsm.c:426 Max EAP retransmissions
exceeded for client 00:24:d7:22:0e:e0
      This means, the WLC has sent an EAP request to the client, and has not received a response. This could be because either the cleint didn't hear the request, or the AP didn't hear the response. It could also be the client ignored the request. You may want to take a look at the following document and see if you want to change the EAP timer values
.   https://supportforums.cisco.com/docs/DOC-12110
*apfMsConnTask_3: Jan 18 11:21:13.118: %APF-3-CHECK_SUPP_RATES_FAILED: apf_utils.c:273 Could not che
ck supported rates. Missing Supported Rate. Length :0. Mobile MAC: b8:ff:61:8f:df:25.
   The WLC was reading a message from the client, and the client did not tell the WLC what rates it could support. This could happen because the packet from the client wasn't heard fully. As well, some clients will see the WLC that they are associated to, and not the individual AP. In this case, it is possible that the client didnt' send the supported rates, as it didn't see a change in BSSID>
*Dot1x_NW_MsgTask_0: Jan 18 11:15:31.521: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Receiv
ed invalid EAPOL-key M2 msg in START state - invalid secure bit; len 40, key type 1, client 00:21:6a
:50:21:80
   The client tried to send a key, when the PEM state on the WLC was START. More than likely the client thought it could roam, but the WLC thought differently
*spamApTask0: Jan 18 11:14:34.630: %LWAPP-3-VALIDATE_ERR: spam_lrad.c:9090 Validation of SPAM Vendor
Specific Payload failed - AP 30:37:a6:c9:53:20
   Bad packet.
*dot1xMsgTask: Jan 18 11:14:19.850: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2914 Max EAP identity request retries (14) exceeded for client 00:1f:3b:16:aa:ef
   WLC is sending EAP Identity request to the client, and it is not repsonding.
Decrypt error occurred for clienten 00:24:d7:69:fb:7c using WPA2 key on 802.11a interface of AP e8:04:62:60:a0:10
Couldn't decrypt the packet. Could be a bad key, or could be we didnt' get the full packet, thus making the decrypt fail.
    For the most part, these are commonly seen issues. Could be the result of RF issues, so you may want to take a look and make sure the coverage at the site is clean.   Some of these can also be caused by WZC, which likes to ignore EAP messages, and has a tendancy to use the login credentials that get cached. Which if these are not domain credentials can cause issues as well.
Cheers,
Steve
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

WLC 5508 7.4.100.0 HA standby reboot loop

Hi.....
We have been running two 5508 WLCs in HA mode for a while now connecting 25 2602 APs. We disconnected the heartbeat utp cbale to change the positision of the standby WLC in the rack. We did not power it off. After we plugged back the Heartbeat cable the standby WLC goes into a reboot loop and gives the following error message
Error:Unable to add Licenses on secondary Controller
Now I did not try to reboot the primary one as users are connected and am afraid I will have two WLCs down instead of one. From what I have been reading it seemed that several HA issues were resolved in code 7.4.100.0...
I hope there is simple fix/workaround for this situation.
All help is appreciated

Hello,
As per your query i can suggest you the following solution -
This document provides information on the theory of operation and configuration for the Cisco Unified Wireless LAN Controller (WLC) as it pertains to supporting stateful switchover of access points (AP SSO).
The new High Availability (HA) feature (that is, AP SSO) set within the Cisco Unified Wireless Network software release version 7.3 allows the access point (AP) to establish a CAPWAP tunnel with the Active WLC and share a mirror copy of the AP database with the Standby WLC. The APs do not go into the Discovery state when the Active WLC fails and the Standby WLC takes over the network as the Active WLC.
There is only one CAPWAP tunnel maintained at a time between the APs and the WLC that is in an Active state. The overall goal for the addition of AP SSO support to the Cisco Unified Wireless LAN was to reduce major downtime in wireless networks due to failure conditions that may occur due to box failover or network failover.
For more information please refer to the link-
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml
Hope this will help you.

WLC 5508 - Failed to connect from LMS 3.2

Hello.
I am trying to include a WLC 5508 in our LMS 3.2.
I have defined the device and credentials, but the LMS server cannot get access to it.
If I try to check de device credentials from the Device Center I get a "failed to connect", but if I a try a telnet session, also from Device Center, I get a connection.
I checked the credentails are OK.
Thank you.

Hi,
You need to download and install the last package : WLC.RME431.v2-1.zip : http://www.cisco.com/cisco/software/cart.html?imageGuId=E3A42793DA29A1B6AC3024C088F9FBC2B324EC8B&i=rs
You must install : MDF 1.37
You must install packages before WLC.RME431.v2-1.zip:
SharedSwimWLC.RME431.v1-2.zip
SharedDcmaWLC.RME431.v1-1.zip
SharedSwimIOS.RME431.v2-5-4.zip
LibSwim.RME431.v2-5-3.zip
LibCommon.RME431.v2-4-2.zip
Elisabeth
WLC.RME431.v2-1.readme:
Supported Devices
=================
Device Type : Cisco 5500 Series Wireless LAN Controllers
Cisco 3750 Switch with Wireless LAN Controller
Devices/Modules Supported :
Cisco 5508 Wireless LAN Controller : 1.3.6.1.4.1.9.1.1069
Cisco 3750 24+2 port 10/100/1000 Switch with integrated Cisco 4402 Wireless Controller: 1.3.6.1.4.1.9.1.747
Features Supported:
Inventory Manager : Yes
Syslog Analyzer : Yes
Config.Mgmt : Yes
Software Mgmt : Yes
Minimum Software : 6.0.188.0
Hardware and Software Requirements
==================================
Hardware and software requirements are the same as those needed for Resource Manager
Essentials 4.3.1 installation.
You must install Resource Manager Essentials 4.3.1 and MDF 1.37 before installing the
device package.
For a detailed list of requirements, as well as instructions for installing Resource
Manager Essentials 4.3.1, go to Cisco.com.
For documentation on Resource Manager Essentials, see:
http://www.cisco.com/en/US/products/sw/cscowork/ps2073/tsd_products_support_series_home.html
Package Dependencies
====================
To install the WLC Package, you must install the
following dependent packages:
SharedSwimWLC.RME431.v1-2.zip
SharedDcmaWLC.RME431.v1-1.zip
SharedSwimIOS.RME431.v2-5-4.zip
LibSwim.RME431.v2-5-3.zip
LibCommon.RME431.v2-4-2.zip

Adding a WLC to the network

My network has many remote locations. Currently I have a WLC 2106 that has been supporting our LWAPs. We have reached the licensed max that it supports (25). In order to add more LWAPs to our Northern region, we decided to get a WLC for the Northern region and have the LWAPs in that region connect to their regional WLC instead of the Southern one. So, now I have a WLC 5508 to add to the Northern region of my network. My concern is, that when I connect it, if a LWAP reboots, what will determine which WLC it will join? I read some of the Cisco doco on the hunting process, but that just seems to address the WLC selection when you have a master WLC identified and the second one is a backup. It also speaks of the LWAPs selecting the WLC with the highest capacity ( i.e. load-balancing ). I don't really want either. I want the LWAPs in the northern region to select the northern WLC (5508) and the southern region LWAPs to select the southern WLC (2106). How do I go about making sure that the LWAPs only select the WLC that they are supposed to?
Thanks!

No problem.. here is the solution.. manualy configure the APs to joing the northern WLC by providing the IP of the WLC using the below link..
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a00808e2d27.shtml#backinfo
Now the AP joins the northern WLC if we have the backend conenctivity to it configured corectly.. now to make sure the AP will not joing the southern WLC.. we need to configure the primary, secondary and tertiary WLC to that AP.. so that the AP will alwways join the primary and then move to secondary if primary id un available.. when we set the primary as the northern. then when the AP reloads.. it will try to join the primary always!! the below link will help you out in configuring the high availability..
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml#c4
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809a3f5d.shtml
let me know how this ansred your question!!
Regards
Surendra

WLC 7.0 discontinues CDP support?

Similar Messages

Maybe you are looking for