07-23-2008 03:01 AM - edited 07-03-2021 04:12 PM
Hi,
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.
Solved! Go to Solution.
07-23-2008 11:00 AM
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.
07-24-2008 07:30 AM
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.
07-23-2008 11:00 AM
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.
07-24-2008 07:10 AM
Hi Tim,
Thanks for your reply. It's running 4.2.61.8.
Are you suggesting we leave the other port unused then? I couldn't find that the 526 supported any kind of link aggregation.
07-24-2008 07:30 AM
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.
07-24-2008 09:17 AM
Thanks, I'll give it a try and let you know how I get on. Is it preferred that ap-manager and management interfaces are in the same subnet/vlan?
07-24-2008 09:28 AM
yes, its fairly common to have both the management and AP manager in the same vlan.
07-29-2008 07:36 AM
Changed to use a single trunk port over 4 days ago and have not seen any issues. The previous 'record' was about 8 hours. Looks like this was the solution! Very many thanks.
07-29-2008 07:38 AM
glad I was able to help..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide