Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi There,I'm working on migrating autonomous WAPs to lightweight mode in a WLC 5508. Some of the older WAPs are being decommissioned at the same time.One issue I have found is that after replacing an old WAP in autonomous mode with a new WAP (3502); ...
Hi There,I have upgraded the software version of a WLC 5508 that was running version 6.0.182.0 to 7.0.235.0 version. Looking at the show sysinfo on the controller (as shown below), I notice the Field Recovery Image Version has the previous version. A...
Hi There,Can you please wit the following question in regards to the deployment of a new WLC and new LAPs,I have configured and connected a 5508 WLC and 3500 series LAP.LAG is enabled in the WLC and successfully connected to the neighboring switch (u...
Hi There,Planning to migrate existing WAPs (which models are supported in LW mode and by the controller, already checked), currently running in Autonomous mode. My question is what will happen when I bring the WLC online in the same LAN as these exi...
Hi There,I have a site that has two internet connections; and i'm using Policing Based Routing to force a particular host to go out to the internet via the secondary link. The configuration is pretty straight forward as shown below,route-map backup-l...
I've been able to fix the issue as well. I did have the route pattern configured in CUCM for the particular 4 digit extension I was using for testing. Looking at the SIP stack and S4 logging in the lync front end servers, I found that there was a SIP...
Hi There,I'm experiencing a similar issue with an integration of lync 2013 and CUCM 7.1. Outgoing calls work fine from a lync client to cisco IP phones or externally; but incoming calls don't. When a call is made from a cisco ip phone to a lync clien...
Hi Scott,Thanks for your response. Indeed the issue was the clients were configured with a SSID profile with WPA enterprise + TKPI. Changed the profile to WPA2 Enterprise + AES and clients are connecting fine. Cheers,Esteban
HI Scott,Thanks for you reply. Yes the SSID configuration is the same in the new LWAPP as it was in the old WAP and the same as the currently active WAP in autonomous mode.I have made sure the SSID is broadcasting in the new system. I can confirm ...