I have a hub and spoke network in which small offices are connected to regional offices. Rightnow static IPs are configured in branch offices and no dhcp mechanism is enabled.
I am planning to enable dhcp in branch offices. Can anybody tell me what are the options that I could explore. The options that I can look into is:
1) Enable dhcp on the branch router.
2) Put a PC based dhcp server on the Branch LAN.
Anyother option that can be implemented? If I enable dhcp on the router than is their any overhead on the router?
Please help me out.
How big is your branch office?
Putting DHCP on the router will definitely add some CPU cycle on the router.
Another option is adding ip helper-address at the branch and set up the scope at the regional office. The draw back of this is when you lose the WAN, and if someone reboot their PC, they will not able to obtain an IP address.
If the branch is not that big, it should be fine with option 1.
there is a third option commonly deployed:
use centralized DHCP servers and on every branch router use
under client vlan interface
ip helper-address dhcp-serv1-ipaddr
ip helper-address dhcp-serv2-ipaddr
this enables the so called DHCP relay function:
the router modifies the client DHCP request by putting a unicast routable destination address = dhcp server ip address (or subnet directed broadcast)
modifies the source to one ip address of its interfaces and put the GW field inside the packet = ip address of interface that received the original request.
In this way the DHCP server can:
answer to the request
understand from what scope to take the ip address to give to the requesting client.
The router receives the answer and forwards it to the requesting client.
We use this and it is effective.
We have two DHCP servers in two different towns and they serve also our sites abroad.
Hope to help
Thanks for your reply Giuseppe and Jerry.
Let me describe some more points which I did not mentioned previously.
1) I have around 20users per branch and 2 IP Phones working per branch.
2) I am using ce500 and 3com switches in the branches.
3) No vlans are configured in branches.
Now keeping the above mentioned points what option is suitable.
You didn't mention how many WAN link do you have. If you have a single WAN link from the remote to the hub site, I will suggest you to configure it at the remote's router. If you have redundant WAN link, using ip helper-address and centralized DHCP can eliminate some administration overhead.
It is really your decision on the business requirement
1) ip helper-address will give you centralized architecture and single point of admin.
2) Configure it on branch router will give you decentralized architecture and you have to do configuration on multiple places.
I think better option would be to configure two commands of ip helper-address at branch so that if one dhcp server at regional office goes down than other would take over.
What do you think?
one point of attention :
actually router sends out one modified copy for each helper-address and the first DHCP server to answer will serve the client.
It doesn't wait a timeout to send second modified copy.
We have a cluster formed by two Cisco Network Registrar and they communicate, for each scope one is master and one is backup.
They exchange information about current leases on each scope.
So they are able to work together without conflicts.
Other collegues using indipendent DHCP servers have reported to have divided each subnets in two parts one served by DHCP1 and one served by DHCP2.
Hope to help