Struggling with VLANs and DHCP on HP5406

[Wirral_Wonderer]

I am preparing for BYOD at the moment and have hit a brick wall (many times!)

 

I have 3 VLANs 1 (default) and 20 (BYOD-Stu)

Our DCs are on VM Sphere and setup VLAN 20 on each of the hosts

One DC has an extra NIC on VLAN 20 and an static IP 10.0.0.11, and will deliver an IP to a workstation on another host, however if I connect a workstation to a port (B13) which is "untagged" against Vlan 20 I can ping 10.0.0.11 but it will not give me an IP address!!!

 

Each of the hosts NICs have the VLAN 20 tagged

 

The Switch is a HP Procurve 5406 and the config is below.

 

Any ideas before I set up another server with DHCP enabled?

 

vlan 1

name "DEFAULT_VLAN"

no untagged A21-A22,B13,B21-B24

untagged A1-A20,A23-A24,B1-B12,B14-B20,C1-C24

ip address dhcp-bootp

ip igmp

exit

vlan 20

name "BYOD-Stu"

untagged B13

tagged A2,A4,A7,A9,A11,A17,B2-B7,B19

no ip address

ip helper-address 10.0.0.11

exit

spanning-tree

[synaesthesia]

Why set up a separate NIC for the DC. Keep it in it's own VLAN or wherever you want to keep and let the switch do the routing.

Don't forget that your vsphere box is effectively a switch, so treat it regarding your tagging like one. (the ports for your vsphere box will therefore typically be untagged on your default vlan (1) and tagged for all traffic otherwise.) As long as the ip helper is there it'd take care of itself

[localzuk]

I'd have it set up as follows:

 

All servers untagged on the same VLAN (in this case VLAN 1). Then you have the IP address of the DHCP server set as the helper-address on VLAN 20 (whatever its normal IP is, not a second card). IP routing should be enabled on the switch, and then the switch handles the inter-vlan routing.

[Wirral_Wonderer]

I've got to go and teach now, but I will have a look at this after.

 

Thanks

[Wirral_Wonderer]

Thanks for your input I had a go at that and failed!

 

I have been dragged onto something else for the moment, so I will do some reading up and see where I am going wrong. It will most likely be me!

 

Thanks again

[Wirral_Wonderer]

OK, I have had a bit more time to look at this now and I am getting out of my depth.

 

Here is my setup:

 

DHCP + DNS X 2 on 172.0.0.11 & 172.0.0.12 SN 255.255.248.0 DG 172.0.0.20 (ISA server)

Currently all workstations are on the default VLAN

Core switch Layer 3 HP 5406 connected to 2610s and 4208 (Layer 2s?)

5406 IP is 172.0.1.15 SN 255.255.248.0 DG 172.0.1.15 (its self)

 

I am finally trying to segregate my traffic for BYOD and also to reduce network broadcasts.

I have created another scope on my DHCP servers 172.0.20.0-172.0.23.255 SN 255.255.252.0

VLAN on my 5406 called BYOD-Stu VLAN:20

There is another VLAN – LEA VLAN:02 which connects our internet feed from the old server room to the new one but no VLAN IPs are set

IP 172.0.20.15 SN 255.255.252.0 DG 172.0.20.15 IP Helper-address – 172.0.0.11 & 172.0.0.12

Nothing else is setup on the switch apart from STP, DHCP Relay and IP routing is enabled.

 

I have created a VM connected to a NIC untagged to VLAN:20, however it will not get an IP address, any thoughts on what I am missing?

:-(

[Mustang]

Are you sure you are using 172.0.0.11 and other addresses in this range?? As 172.0.0.0 to 172.15.255.255 isn't a private address range and is owned by AT&T.

If you are using these IPs you need to change them ASAP.

 

Private address for class B are 172.16.0.0 to 172.31.255.255

 

you also shouldn't be using the vlan 1 (default_vlan) HP always recommend not using it.

 

I think you should sort these problems out first before you try and get the BYOD working.

[GeekyPete]

.Re-reading more carefully this time. Edited February 4, 2014 by GeekyPete

[Wirral_Wonderer]

Thanks for the query, the tagged ports are connected to the VM hosts. 3 hosts each with 4 NICs.

 

I configured them when I was trying to configure extra NICs for the DHCP severs for the VLAN 20 before I was told that I should use the routing options of the switch. Currently the NICs are disabled on the VM servers.

 

I hope this makes sense and is right!

[Wirral_Wonderer]

Big oops on the ip range, however we are nat'ed via the LA, it's not caused an issue yet, but something I need to sort out. Thanks

[Wirral_Wonderer]

Just realised that we paid a firm a lot of money 7 years ago to setup our network from scratch and they did the DHCP!

 

Not that changes anything, apart from not feeling a total numpty!

Edited February 4, 2014 by Wirral_Wonderer

[Liam]

Had this. You can't communicate with the default vlan from other vlans.

 

To test this I created another dhcp server on vlan 2 for example then I added multiple vlans with a dhcp helper and hey presto.

 

I'm going through the same thing now. Just to look me a while to get there.

[Liam]

If you want some more assistance pm me. As the others said it is not recommended to use the default vlan anyway.

[Wirral_Wonderer]

I think in have sorted my issue. The DG was set to our ISA and not the switch. I need to test it fully tomorrow though! It works with my test VM.

 

I had better get an early start tomorrow just in case!

[Wirral_Wonderer]

Thanks Liam, I will take you up on your offer.

 

The way the network is configured is not ideal anyway so I need to start planning a way forward.