I have a network that currently has the DHCP Service running in the firewall (172.27.187.1) and it is giving out IPs on the 172.27.187.0/24 range. All of this is happening in Vlan1
I will move this service to a Windows Server (10.10.88.100) currently running in Vlan88.
Both Vlans exist in the same Cisco Stack and there is intra vlan routing up and running well right now.
The new DHCP server will be giving away IP addresses in the 10.10.70.0/24 range, and the old DHCP service (172.27.187.0/24) will be disabled.
I have already added a secondary IP to my Cisco Stack (10.10.70.1) to Vlan1 and I have tested with a static IP configuration in a test PC.
This is a 24/7 production environment so I can't test this new DHCP server, but I think that all I have to do now during the window I will request is to disable the current DHCP service in the Firewall, (172.27.187.1) and enable the new DHCP Service in the Windows Server(10.10.88.100).
Then go PC by PC running the following commands:
That action should trigger a new DHCP request, and since the only DHCP Server running is my new 10.10.88.100 it will find it and get an IP from the new IP range (10.10.70.0/24)
My questions are:
Am I missing something here?
I want to see this also from the routing perspective, my thinking is that as long as there is intra vlan routing the DHCP request from a PC in Vlan1 should go into Vlan88 and find the DHCP Server, am I correct?