Online Expert Day - HPE Data Storage - Live Now
April 24/25 - Online Expert Day - HPE Data Storage - Live Now
Read more
ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

New DHCP Scope not assigning IP to VLAN

SOLVED
Go to solution
JiLi
Visitor

New DHCP Scope not assigning IP to VLAN

Hi

We have 7 HP Procurve Switches around the building, and 1 DHCP windows server 2008.

On server 2008, there are already 8 dhcp scopes. On Switches, there are 8 VLANs pointing back to DHCP server with ip helper-address 10.89.31.6.

Problem is:

On the server 2008 DHCP, I created a new scope:

NEW-WIFI

IP Scope: 10.89.41.5 to 10.89.41.250

subnet mask: 255.255.255.0

Gateway: 10.89.41.1

 

On the core switch, I created vlan 70:

 

VLAN 70

name “NEW-WIFI”

ip helper-address 10.89.31.6

ip address 10.89.41.1 255.255.255.0

tagged 44-48

exit

 

On one of hub switches, I created vlan 70 also:

VLAN 70

name “NEW-WIFI”

untagged 40

tagged 45-48

no ip address

exit

 

Then I plugged a device in, it’s not getting ip address from dhcp.

 

Where did I do wrong?

 

Many thanks in advance!

 

Ji

3 REPLIES
16again
Respected Contributor

Re: New DHCP Scope not assigning IP to VLAN

1st step is checking routing

Can server2008 ping the new VLAN interface 10.89.31.6  ?

JiLi
Visitor

Re: New DHCP Scope not assigning IP to VLAN

10.89.31.6 is the windows dc server itself.

From the server, I can ping 10.89.41.1 which is the gateway of the new scope and ip address for new vlan.

But my laptop or WAP just not getting any IP assigned.

JiLi
Visitor
Solution

Re: New DHCP Scope not assigning IP to VLAN

Found the problem.

The switch I tested with was not connected to core switch directly. But via another switch in a different hub room.

New VLAN was not setup on that switch, although no port was used.

Had to create vlan on all switches and it is working now.

Cheers

Ji