01-21-2023 04:24 PM
Hello All -
I need to know the answer to this.
You are running Ruckus ZoneDirector and are using it to manage your ruckus WAPs. And you have a separate DHCP server handing out IPs.
Then your company tells you to make a new DHCP server, and make the change in Ruckus so now the new DHCP server is handing out IPs.
Some users are coming to you saying they don't have internet access.
When investigating in Ruckus you see that there's about about 15 pairs of devices that share the same IP. So there's an IP conflict going on. When telling the users to manually pick a different IP on their device they have internet.
It appears in that Ruckus is binding the IP from the previous DHCP server with the MAC address of the devices that were connected to the old server for the lease time assigned by the DHCP server. Is this thought accurate or are the devices retaining the IP from the previous DHCP server for the 24h lease time on their own?
I'm trying to understand if there's something in Ruckus that can be done to prevent an IP conflict when changing DHCP servers. Or is this strictly something that should be done on the DHCP server.
What is the proper way to change DHCP servers?
Is there a way to clear the IP address binding before switching DHCP servers in Ruckus? Does Ruckus even bind Mac address with IP address? I know there's a command to run that shows binding.
Thank you looking forward to hearing your thoughts and answers.
03-16-2023 07:25 AM
In the ZD, we map the VLAN configuration the SSID where the VLAN tagging will be added to the client and client sends broadcast packet to the DHCP server and gets an ip address.
Please make sure your old DHCP server is removed out of the network and also client send the DHCP request packet where previous ip address and its gateway is stored, if the ip is previously saved on the device configuration then same ip request will be assigned to client which cause conflict on the network. The DHCP server should send DHCP deny packet if the same ip address request is coming in to the network which is already been allocated to the client. Please check the option under new DHCP server.
In this scenario, there is no configuration or any troubleshoot is required at RUCKUS end.
03-16-2023 06:34 PM
Zonedirector will not bind any client to the specific IP address, the AP receives the DHCP broadcast packets and will forwards it. It is just a middle man in the external DHCP process. Once the IP is received on the client, AP gathers the client info reported and forwards the info to ZD to display in the GUI.