Tech Support > Microsoft Windows > Windows Server > DHCP and procurve 2524 switches
DHCP and procurve 2524 switches
Posted by connor_a@hotmail.com on January 27th, 2008


Hi everyone,

I have a W2k3 DC which services about 240 clients so I'm running out
of DHCP leases.

There are approximately 10 procurve 2524 switches in the building
servicing 5 floors.

What is the best way to migrate from the existing DHCP scope to the
new 10.x.y.z scopes that offer more subnets/hosts.

Thanks.

Posted by Kevin Longley on January 27th, 2008


What ip range are you presently using?

<connor_a@hotmail.com> wrote in message
news:21808656-0d74-4601-bea9-e48082021a3e@i29g2000prf.googlegroups.com...

Posted by connor_a@hotmail.com on January 27th, 2008


On Jan 28, 8:23*am, "Kevin Longley" <kwlong...@cirtronics.com> wrote:
Currently 147.109.x.y is the subnet in use. DC with DHCP has about 20
leases left.

I need to migrate 147.109.x.y to a 10.x.y.z/23 which gives me 510
hosts across (10.16.128.0 / 10.16.129.0) subnets.

Will the following work:

Create an additional vlan on each switch

define ip helper_address for new 10.x.y.z subnet in this vlan

Gradually migrate each PC to the new vlan.

The question is can the same vlan exist across multiple switches???

Thanks.

Posted by Richard M. on January 28th, 2008


<<
<connor_a@hotmail.com> a écrit dans le message de news:
e398eebc-0c66-4825-a683-25bfa354f710...oglegroups.com...
On Jan 28, 8:23 am, "Kevin Longley" <kwlong...@cirtronics.com> wrote:
Currently 147.109.x.y is the subnet in use. DC with DHCP has about 20
leases left.

I need to migrate 147.109.x.y to a 10.x.y.z/23 which gives me 510
hosts across (10.16.128.0 / 10.16.129.0) subnets.

Will the following work:

Create an additional vlan on each switch

define ip helper_address for new 10.x.y.z subnet in this vlan

Gradually migrate each PC to the new vlan.

The question is can the same vlan exist across multiple switches???

Thanks.

This is the very purpose of vlan to span multiple switches.
That's why is it "Virtual" : not linked to the physical location.

You can as well simply change the existing VLan definition and reboot all
the PC.
They will change their IP at once.
Just take care manually of the printer and other fixed address devices.

You can even to that without having to go to each PC.
For instance, says that you perform the change during a week-end.
Decrease the lease's duration to 1 day. The gradual lease renewal will take
care of IP change.

Yet another way : Once the Vlan definition done, simply shut and reopen each
switch port
(on cisco : using "int range fa0/1-47, shut, no shut")
This is the same as removing the network cable. And force DHCP renewal.

I used it more than once !

--RiM.




Similar Posts