DHCP Standard Practise

[Ian_Broadway]

I have a question regarding DHCP.

Whats the standard practise for implementing DHCP helpers.

Our current setup, we use UDP profile on all our vlans on our core switches that require dhcp services. this is an inherited design before my time.

would it be more beneficial to go down the bootprelay route?

are there any other options? pros and cons for each?

Many Thanks
Ian

[Ian_Broadway]

Hi,

the scenario is, we have two DHCP servers and I would like all DHCP requests for 20 VLANs to go to these servers.

is it a case of;

configure bootprelay add "DHCP Server IP 1"
configure bootprelay add "DHCP Server IP 2"

configure bootprelay vlan "vlan 1"
configure bootprelay vlan "vlan 2"

and so on.

[Jarek]

Ian, it depend what you need .

Oscar, I think you can use bootprelay with more DHCP servers, with additional config on server: agent.circuit-id, agent.remote-id, class, allow members of ... and so on.
It will respond only to configured "class members".

--
Jarek

[Ian_Broadway]

We use 2 DHCP servers for all our vlans, I assume you can specify more than one server within the bootprelay config?

[Jarek]

For example rel. notes 15.6 says that the maximum number of BOOTP or DHCP servers per virtual router is 4

--
Jarek

[OscarK]

In early days UDP helper was the only method to be able to distinguish between vlans and DHCP servers.
Nowadays you can enable bootprelay per vlan so you can use bootprelay without enabling it for all vlans. Still I think if you need different DHCP servers for different vlans UDP profile is the only config possible.