Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DHCP: router vs. server...

Hello all,

I am simply looking for justification to move my network's DHCP scopes from NetWare based servers to our Cisco multilayer switches and routers. We have one centralized data center with 60 branchs in our city. Each branch has its own DHCP server with its own subnet. We also have a centralized DHCP for our main office. We have been having trouble with our "Server Team" handling their responsibilites on the DHCP end. Also, as a member of the "Network Team," I would like to have access to that DHCP info (IP, MAC, Lease info, etc) for troubleshooting purposes. I have been on Experts-Exchange and other forums. All I can find there are "Windows Honks" who only support a Windows based solution. I disagree. I believe that a network based solution is best. Also, less hops for the traffic to make = less congestion.

Like I said, I am simply looking for some technical concrete info that I may take into battle with me against the dreaded "Server Team."


Thanks in advance everyone,



Re: DHCP: router vs. server...

Let them deal with it :-) Our server team uses Linux for DHCP and yes it can be pain but it's one less thing I have to deal with (until it doesn't work and we get blamed that our helpers are wrong).

New Member

Re: DHCP: router vs. server...

Personally, I would prefer to avoid putting them on the Cisco kit.

Our organisation is in the process of rebuilding our entire estate as a green field site. We're removing all static IPs and only using 2 Microsoft AD servers for DHCP. For devices that need static we're using reservations instead and mirroring them across both servers. That way, 'surprises' shouldn't happen in the future.

Reservations are handled by a couple of guys in the Server team who deal with Directory Services, i.e., looking after the logical AD structure.

There are downsides. Windows DHCP, even on Server 2003, is very buggy. Which is why we're looking at a 3rd party commercial option which is better than Windows, Netware and linux standard options. You get what you pay for, though, and we're large enough to justify that cost (50K users).

Think about how many sites and users you want to manage. And whether you want the hassle of maintaining static IP lists...

New Member

Re: DHCP: router vs. server...

set up each branch with a PIX let the pix do the DHCP assignment. You can have your ip scheme as - for your networks. Easy enough setup then MPLS or however your WAN is connected back to your main site. Then you can have access and manage all your stuff.

CreatePlease login to create content