Hello, got a question... I've read in HP documentation that more than one DHCP relay can be defined on a Procurve switch. Whichever one responds first is the relay that handles the DHCP request. I'm working with someone who is telling me that adding a second relay results in no devices getting a DHCP request. I've asked for the config from the switch, but at the same time, I want to make sure that I read things correctly regarding multiple DHCP relays defined on a Procurve. Anyone here with HP switch experience want to comment on this?
Quote from: deanwebb on April 03, 2018, 08:45:21 AM
Hello, got a question... I've read in HP documentation that more than one DHCP relay can be defined on a Procurve switch. Whichever one responds first is the relay that handles the DHCP request. I'm working with someone who is telling me that adding a second relay results in no devices getting a DHCP request. I've asked for the config from the switch, but at the same time, I want to make sure that I read things correctly regarding multiple DHCP relays defined on a Procurve. Anyone here with HP switch experience want to comment on this?
I do believe, and don't quote me on this, that the DHCP request is sent to all DHCP servers at the same time, and the one that responds first wins.
this is based on Cisco devices, I have not HP Procurve experience.
^ True, it works in the Cisco world and I've got hands-on success with that. The HP docs read like it works that way, as well, but this guy...
...if that second server is over a slow link, true, true, you'd never get an IP from it...
Both DHCP servers should send a reply and the client will return the request for whatever came first. Unless there's some fancy DHCP feature configured where the DHCP servers are in active/passive, or in some sort of weighted load balancing which is configured or behaving incorrectly. But that's already beyond the Procurve question, it should work with two helpers configured.
Can't you just blame the firewall, btw?
:notthefirewall:
I work for a NAC company so, yes, I can blame the firewall.