03-19-2013 08:03 AM - edited 07-03-2021 11:45 PM
Hi,
I've read several of these discussions already, but I can't seem to find a solution for my issues with WLAN controllers.
I have two WLCs 5508s sitting in my network, and a third 5508 sitting in the DMZ. The control and data path will not come up to the Anchor controller sitting in the DMZ. We've opened the firewall up to make sure all traffic is allowed between the three WLCs, but still the paths do not come up.
I can ping the anchor controller no problem, but it won't mping or eping.
I did notice in the logs, this morning, that yesterday when I rebooted the anchor controller in the DMZ, the control path came up to one of the WLCs in the network for roughly 10 seconds and then went down and won't come back up.
All three are in the same mobility group, and the mobility group is setup on all three. I've double checked the IP addresses and MAC addresses several times. I'm not sure what I could be missing in the config that won't allow the paths to come up.
Any thoughts?
Thanks.
Christopher.
Solved! Go to Solution.
03-22-2013 07:53 AM
So, as it turns out. It was a problem with the NAT configurations. The ASA, dude had to add in some new ones, and then we got Mobility up to both devcies, and then he had to do a 'clear conn' command in order for the Data paths to come up. Everything seems to be working like a charm there now.
I am however having a problem getting the Web Auth working properly. The DHCP is local to the anchor controller, and guests are getting the proper IP address, but everyone is getting authorized without the getting redirected to the Web Auth pages on the Anchor Controller. I tried going to http://1.1.1.1/login.html, but I can't seem to get there.
EDIT: New info here. So, this looks like it may have bee na routing issue on my side, partically. I can now access https://1.1.1.1/login.html from my cell phone, couldn't before until I changed some routing. However, it doesn't automatically take me to the Login page for Web Auth. I was able to authenticate on the page, but then still couldn't get to any website after being authenticated.
ALSO, my work laptop has proxy server information in the internet browsers, could that be causing an issue? As I still can't access https://1.1.1.1/login.html from my laptop.
Thanks.
03-31-2013 10:08 AM
Thanks for sharing the result.
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