- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: ProCurve 5412zl DHCP relay not working with VL...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2010 01:22 PM
тАО08-15-2010 01:22 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2010 06:09 PM
тАО08-15-2010 06:09 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2010 06:19 PM
тАО08-15-2010 06:19 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2010 08:13 PM
тАО08-15-2010 08:13 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
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".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2010 08:15 PM
тАО08-15-2010 08:15 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2010 02:13 PM
тАО08-16-2010 02:13 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2010 02:34 PM
тАО08-16-2010 02:34 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2010 05:01 PM
тАО08-16-2010 05:01 PM
Re: ProCurve 5412zl DHCP relay not working with VLANS
I am almost certain that is the issue.
I will try that first thing tomorrow and let you know.
Thanks a bunch :<)
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2010 11:45 AM
тАО08-17-2010 11:45 AM
Re: ProCurve 5412zl DHCP relay not working with VLANS
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2010 01:40 PM
тАО08-17-2010 01:40 PM
SolutionThe 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.