05-27-2022 01:42 PM - edited 10-19-2023 11:28 AM
Hi all,
So I have successfully setup mobility from my foreign controller (9800 WLC) to my anchor which is a 9300 Catalyst that is running (17.3.5) with WLC addon (using this to just provide Guest access from local network). Both show up/up. I also get inbound client connections to the anchor DMZ controller, so I know ports and tunnel are working (see pic)...
The issue is that they show up as IP learn and do not get DHCP. Same for every client. I setup a simple DHCP pool on the anchor for simplicity and I have ensured similar profile and tag config, enabled DHCP with wireless management on both foreign and anchor as well. I cannot figure how to get clients an IP.
05-28-2022 03:33 AM
Hi
It seems that your problem is not DHCP yet.
[mm-msg] [1116]: (ERR): Peer IP: 10.74.31.200 Port: 16667 Failed to dispatch dgram msg
Your log shows that no client got to the point to request an IP address. And we keep seeing the message above which suggest some problem on the communication between anchor and foreign WLC.
05-29-2022 05:48 AM
Is it wise to use a feature (EWC on 9300) which is end of life so you can never upgrade the 9300 WLC past 17.3?
Anyway assuming you're happy with that did you read this?
"The EWC on Catalyst switches does not support being used as a guest anchor nor as a guest foreign controller. All guest network configurations will be done on the EWC on the switch."
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