We have recently installed a WLC526. We have an issue whereby the unit becomes unpingable via its management address and wireless connectivity is lost untill the unit is rebooted. This will happen every few hours. Console connectivity is unaffected - the device does not seem to have crashed.
The 526 has now been replaced but this has not resolved the issue. Any ideas?
More information - the WLC is connected to a pair of Catalyst 3560s. One port is connected to an access port on the switch and has untagged management and ap-manager interfaces, the second port is connected to a trunk and has a single tagged interface for the user vlan. We used the console startup wizard and GUI to do the configuration, not the Cisco Configuration Assistant.
OK, you are running the current code level which is good. The wlc526 does not support any type of link aggregation. Typically, I have folks just setup a trunk port to the wlc526 and have all the vlan go over that link instead of using multiple ports. I've seen some instability using 1 port for user traffic and another port for management/ap manager traffic.
What controller software version are you running? Typically its better to just use one connection (trunked) to the wlc from your switch for all of your traffic, then to try to split off user and management/ap manager traffic due to how the controller handles traffic flows.