02-15-2025 11:08 PM
Hi everyone,
I’m facing an issue with the EWC.
My company is migrating from a Cisco 3504 controller to a Cisco EWC (9115) for managing APs.
In our existing setup, the controller has a built-in DHCP server that assigns IP addresses only to wireless clients.
However, after switching to the EWC, the DHCP server is now assigning IP addresses to both LAN and wireless clients, which is not the intended behavior.
I would like to configure the EWC so that its DHCP server releases IP addresses only to wireless clients, just like the previous setup.
Could you please advise on how to achieve this?
Thanks in advance for your help!
02-15-2025 11:42 PM
Assuming your lan have different ip range of wireless, if you create pool only for the wireless range, it should not provide ip address to the wired network.
02-15-2025 11:46 PM
My wired network users are configured with static IP settings, and there is no other DHCP server. However, I currently have a DHCP server running on the EWC, and wired clients are receiving IP addresses from it.
02-16-2025 01:10 AM
Just to add… if your wired devices are static, then how are they getting dhcp, they can’t. Also, best practice is to keep wireless separate from other vlans. Another thing, you are better off using a dhcp server on the network rather than having a controller do it.
The controller will only hand out dhcp to wireless clients so it seems you must have something on the network, or else take a packet capture and really identify where the dhcp is coming from.
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