11-10-2021 05:59 AM
I have deployed /25 network for APs but it is already exhausted so I had to add /24 network and I promoted /24 network to the primary address.
So, the current configuration is:
interface Vlan100
description AP
ip address 192.168.227.129 255.255.255.128 secondary
ip address 192.168.241.1 255.255.255.0
ip helper-address x.x.x.x
When the lease time of the /25 network is over, a device will get the newly deployed /24 network's IP address. Is there any way to expedite this process?
Solved! Go to Solution.
11-15-2021 05:49 AM
As you said, there is no effective way for this. Even if the lease expires, the device continues to renew the /25 IP address instead of the /24, which is the primary network.
11-18-2021 11:52 PM - edited 11-20-2021 01:48 PM
Hello
when you change the primary addressing on an interface its that primary ip address that will be used for the gateway ip address in the dhcp packet - Now if the dhcp server scope is exhausted for the primary ip address or for some reason it isn’t able to respond on that primary ip then dhcp allocation is lost because by default the secondary ip addressing isn’t utilised by dhcp, However this can be changed by using a global feature called ip dhcp smart-relay which will relate the secondary addressing assigned to that interface as the giaddr in the dhcp packet sent to the dhcp server.
11-21-2021 12:38 PM
Hello,
what are you using as DHCP server (e.g. Windows Server 2012 R2) ?
11-10-2021 06:21 AM - edited 11-10-2021 06:23 AM
The best approach is, take the maintenance window and change to new IP,
11-11-2021 11:44 PM
If I understand the original post correctly the question is about hosts which currently have IP addresses from the /25 network and if there is a way to get them to acquire a new address before the expiration of the current lease. If I understand the suggestion from @balaji.bandi correctly he is suggesting that in a maintenance window that you remove the /25 and replace it with the /24 (no secondary IP). The result would be that all clients still using the old /25 address would stop working. Eventually users would get frustrated that their device was not working and would reboot, then would acquire a new address and would work. So it would work (sort of) but would be a very user unfriendly solution.
Realistically I do not see any effective and user friendly solution other than waiting for current leases to expire (the secondary address solution). How long are the leases of the /25 devices?
11-15-2021 05:49 AM
As you said, there is no effective way for this. Even if the lease expires, the device continues to renew the /25 IP address instead of the /24, which is the primary network.
11-15-2021 08:29 AM
Glad all working well and you able to resolve the issue, apprciated your input.
11-19-2021 07:11 AM - edited 11-19-2021 07:13 AM
Hello
@ethanpark0726 wrote:
the device continues to renew the /25 IP address instead of the /24, which is the primary network.
This is not the case if the primary ip address is changed, the dhcp scope related to the /24 should begin to be serviced.
11-18-2021 11:52 PM - edited 11-20-2021 01:48 PM
Hello
when you change the primary addressing on an interface its that primary ip address that will be used for the gateway ip address in the dhcp packet - Now if the dhcp server scope is exhausted for the primary ip address or for some reason it isn’t able to respond on that primary ip then dhcp allocation is lost because by default the secondary ip addressing isn’t utilised by dhcp, However this can be changed by using a global feature called ip dhcp smart-relay which will relate the secondary addressing assigned to that interface as the giaddr in the dhcp packet sent to the dhcp server.
11-21-2021 12:38 PM
Hello,
what are you using as DHCP server (e.g. Windows Server 2012 R2) ?
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