02-27-2015 06:25 AM - edited 07-05-2021 02:37 AM
I have the same SSIDs set up across multiple buildings but have different controller interfaces and subnets at each building. I'm seeing that clients who move from building to building are keeping their IP address instead of pulling new ones. This is causing a problem because the device cannot discover local resources (printers, Apple TV, etc) but instead still see the resources from the previous building.
Solved! Go to Solution.
02-27-2015 02:19 PM
Shouldn't clients that do a ipconfig /release and /renew pull a new IP address though? Or if they are rebooted?
No, most of the time client is requesting the previous IP it had. Most of the cases your DHCP server will issue the same IP for the client unless that IP address given away to any other client. What is the DHCP lease time for those clients ?
In general when a client associate to AP, then the WLC who manage that AP will check any other WLCs in the mobility group to see if that client is a "new association" or a "roamed client". If any other WLC has that client information (not cleared from its database) then it will treat as roamed client & traffic is tunnel back to original WLC (anchor), even though client is associated to an AP managed by a different WLC (foreign). In that way client IP will remain, even though client roam from place to place.
HTH
Rasika
**** Pls rate all useful responses ****
02-27-2015 11:03 AM
This is the expected behaviour & primarily to provide smooth roaming.
Let's say client is having a voice call (if you given voice over wireless) & move building to building. If he change IP when goes from building to another, voice call get drops every time.
HTH
Rasika
**** Pls rate all useful responses ****
02-27-2015 11:10 AM
Rasika - thanks for your response. Shouldn't clients that do a ipconfig /release and /renew pull a new IP address though? Or if they are rebooted? I am telling people that need to get a new IP address to connect to local resources to reboot once they get to the new building but they are still being assigned the old IP from the previous building.
02-27-2015 02:19 PM
Shouldn't clients that do a ipconfig /release and /renew pull a new IP address though? Or if they are rebooted?
No, most of the time client is requesting the previous IP it had. Most of the cases your DHCP server will issue the same IP for the client unless that IP address given away to any other client. What is the DHCP lease time for those clients ?
In general when a client associate to AP, then the WLC who manage that AP will check any other WLCs in the mobility group to see if that client is a "new association" or a "roamed client". If any other WLC has that client information (not cleared from its database) then it will treat as roamed client & traffic is tunnel back to original WLC (anchor), even though client is associated to an AP managed by a different WLC (foreign). In that way client IP will remain, even though client roam from place to place.
HTH
Rasika
**** Pls rate all useful responses ****
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