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.
Symptoms
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC without any...
Hi there,
You are correct, as management or redundancy management interface related details cannot be easily changed on-the-fly once HA-SSO is formed. You will want to scheduled a maintenance window as you will need to disabled HA-SSO, let both WLC...
That's great to hear! Glad the console is now responsive to your whims.
Since your AP is running a lightweight recovery image, sadly no such luck. There is no GUI or the like you can access for the AP even after manually configuring a BVI address an...
Hi Lukas,
To echo what Leo stated, it would be good to possibly migrate to a newer and recommended version of AireOS on your WLC:
https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-TAC-Recommended-AireOS.htm...
Sure thing, my pleasure.
If you're not getting any keyboard input recognized whatsoever, then this is likely attributed to a) incorrect settings on your terminal emulator program of choice (i.e. putty, secureCRT, etc.), or b) bad hardware (either Ci...
Hi there,
The AP will only use DHCP option 43 to help discover a WLC, it won't utilize option 150 or the like to reach out to a TFTP server directly.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/...
