topic Re: ProCurve 5412zl DHCP relay not working with VLANS in Switches, Hubs, and Modems

ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Sun, 15 Aug 2010 20:22:53 GMT

Hi all,

I have an HP Procurve 5412zl 96G that I wish to setup multiple VLANS and using only 1 DHCP server which resides on the default VLAN.

I believe I have done everything correctly but it still doesn't work. I have done the following and was wondering if someone could tell me what I have missed ?

Setup 3 VLANS 192.168.1.2/24 VLAN1
192.168.2.1/24 VLAN2
192.168.3.1/24 VALN3
Enabled DHCP Relay
Enabled IP Routing
Set IP Helper on each VLAN 192.168.1.16
Setup 3 Scopes on MS DHCP Server
Gateway/Router = 192.168.1.2 for VLAN1
192.168.2.1 for VLAN2
192.168.3.1 for VALN3

Set the ports I want in the VLAN as untagged
Set the ports where the DHCP server resides as tagged in VLAN2& 3 and in VLAN1 where the DHCP server resides, set the VLAN2 & 3 ports as tagged.

Re: ProCurve 5412zl DHCP relay not working with VLANS

Mark Wibaux — Mon, 16 Aug 2010 01:09:47 GMT

Remove the tagging from the port connected to the DHCP server. All it should need is to be untagged in VLAN 1. The switch will handle forwarding the DHCP request packets from VLAN 2 & 3 to the server located in VLAN 1. Also make sure you don't have dhcp helper defined in the configuration for VLAN 1.

Re: ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Mon, 16 Aug 2010 01:19:19 GMT

Currently I had to put all the ports into the default VLAN so it would work. For now I would like to just get port G12 to acquire an IP from the DHCP server correctly in VLAN2 after which I would assign other ports to be on VLANS 2,3,4, & 5 during a maintenance window.

I think I am real close but seem to be missing something, hopefully someone can spot it and point it out to me.

Thanks in advance,

Steve

Here is my startup config:

Startup configuration:

; J8698A Configuration Editor; Created on release #K.14.60

hostname "HP 5412zl 10th Floor"
time timezone -480
time daylight-time-rule Continental-US-and-Canada
module 1 type J8702A
module 2 type J8705A
module 3 type J8702A
module 4 type J8702A
module 5 type J8702A
module 6 type J8702A
module 7 type J8702A
ip default-gateway 192.168.1.1
ip routing
vlan 1
name "DEFAULT_VLAN"
untagged A1-A24,B1-B24,C1-C24,D1-D24,E1-E24,F1-F24,G1-G11,G13-G24
ip helper-address 192.168.1.16
ip address 192.168.1.2 255.255.255.0
no untagged G12
exit
vlan 2
name "Corporate"
untagged G12
ip helper-address 192.168.1.16
ip address 192.168.2.1 255.255.255.0
tagged B1-B24
exit
vlan 3
name "Call Center 1"
ip helper-address 192.168.1.16
ip address 192.168.3.1 255.255.255.0
exit
vlan 4
name "Call Center 2"
ip address 192.168.4.1 255.255.255.0
exit
vlan 5
name "VOIP"
ip address 192.168.5.1 255.255.255.0
tagged E1-E24,F1-F24
exit
console inactivity-timer 30
no dhcp-relay hop-count-increment
timesync sntp
sntp unicast
sntp 600
sntp server priority 1 132.239.254.49 3
ip route 0.0.0.0 0.0.0.0 192.168.1.1
snmp-server community "public" unrestricted
snmp-server contact "IT Administrator" location "10th Floor"

HP 5412zl 10th Floor# sh dhcp-relay
DHCP Relay Agent : Enabled
DHCP Request Hop Count Increment : Disabled
Option 82 : Disabled
Response validation : Disabled
Option 82 handle policy : append
Remote ID : mac

Client Requests Server Responses

Valid Dropped Valid Dropped
---------- ---------- ---------- ----------
0 0 0 0

HP 5412zl 10th Floor# show ip helper-address

IP Helper Addresses

VLAN: 1
IP Helper Address
-----------------
192.168.1.16

VLAN: 2
IP Helper Address
-----------------
192.168.1.16

VLAN: 3
IP Helper Address
-----------------
192.168.1.16

VLAN: 4
IP Helper Address
-----------------

VLAN: 5
IP Helper Address
-----------------

HP 5412zl 10th Floor# sh ip route

IP Route Entries

Destination Gateway VLAN Type Sub-Type Metric Dist.
------------------ --------------- ---- --------- ---------- ---------- -----
0.0.0.0/0 192.168.1.1 1 static 1 1
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
192.168.1.0/24 DEFAULT_VLAN 1 connected 1 0
192.168.2.0/24 Corporate 2 connected 1 0
192.168.5.0/24 VOIP 5 connected 1 0

Re: ProCurve 5412zl DHCP relay not working with VLANS

kianwei — Mon, 16 Aug 2010 03:13:30 GMT

Hi,

Try to ping from source VLAN 2 using this command from your 5412zl core switch.
"ping 192.168.1.16 so 2"
Do you getting reply? If not please check your DHCP server gateway. I suspect currently your DHCP server gateway to "192.168.1.1" instead of "192.168.1.2".

Re: ProCurve 5412zl DHCP relay not working with VLANS

kianwei — Mon, 16 Aug 2010 03:15:27 GMT

Before you do that, try to make sure your VLAN2 is up first. (at least connect something to VLAN member port)

Re: ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Mon, 16 Aug 2010 21:13:25 GMT

I set port G12 to be untagged in VLAN 2 and removed the IP helper address from VLAN 1 and then connected a laptop to port G12 and was not able to obtain an IP.

I then set a static IP OF 192.168.2.22 on the laptop and tried to ping the dhcp server 192.168.1.16 and could not.

Re: ProCurve 5412zl DHCP relay not working with VLANS

Mark Wibaux — Mon, 16 Aug 2010 21:34:00 GMT

What's the default gateway of your DHCP server? Make sure it is the switch (192.168.1.2).
Also make sure the routing device at 192.168.1.1 has routes that tell it how to get to the rest of the subnets you have added to the switch.
Also remove the "ip default-gateway 192.168.1.1" from the config. This is only needed if you do not have routing enabled on the switch. With routing enabled the 0.0.0.0 route takes precedence.

Re: ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Tue, 17 Aug 2010 00:01:33 GMT

Mark you are a genius !

I am almost certain that is the issue.

I will try that first thing tomorrow and let you know.

Thanks a bunch :<)

Steve

Re: ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Tue, 17 Aug 2010 18:45:33 GMT

Getting real close..

I setup static routes in the 192.168.1.1 SonicWall that are as folows:

Source: VLANS 2,3,4,5
Destination: VLAN 1
Gateway: HP Switch 192.168.1.2

And then a recursive one to that.

I removed the default gateway: 192.168.1.1
in the switch config

I set the DHCP server's GW to 192.168.1.2

I can now receive IP's from the dhcp server but can't get out to the internet

Re: ProCurve 5412zl DHCP relay not working with VLANS

Mark Wibaux — Tue, 17 Aug 2010 20:40:48 GMT

Not sure from your last bit if you've set the sonicwall to route based on VLANs or IP subnet.
The routes you need to specify on the Sonicwall should be based on IP subnet. So something like this

Destination Subnet Mask Gateway
192.168.2.0 255.255.255.0 192.168.1.2
192.168.3.0 255.255.255.0 192.168.1.2
192.168.4.0 255.255.255.0 192.168.1.2
192.168.5.0 255.255.255.0 192.168.1.2

Try doing some traceroutes from a client machine to see where the machine can route to. NOTE: if using windows you can add a "-d" to the commmand to stop it trying to resolve each IP address to a hostname which will speed up the trace a bit e.g. tracert -d xx.xx.xx.xx

You should also be able to do this from the SonicWall just to see if your routes on it are working correctly to the new subnets.

Re: ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Wed, 01 Sep 2010 03:32:45 GMT

Ultimately Mark had it on the money and I had left out a key bit of information which was that I had a Barracuda Web Filter just before the SonicWall device at 192.168.1.3
I took that out temporarily and it all worked and then put it back after I set the default route in the switch to the Barracuda at 192.168.1.3 and added some static routes to the Barracuda.

Thanks again Mark ! !

Re: ProCurve 5412zl DHCP relay not working with VLANS

Steve K Harris — Wed, 01 Sep 2010 03:35:49 GMT

With Mark's assistance and a little light bulb that went off in my head after he pointed the way all is working now.

Thanks Everyone

Steve

Re: ProCurve 5412zl DHCP relay not working with VLANS

miwh — Thu, 06 Jan 2011 22:04:14 GMT

Steve I have a similiar setup, with barracuda devices in front of the firewall. Would you mind showing me your configs?