DHCP Setup- Sound like a good idea

Hi,

13 branches each with DHCP enabled
1 corporate HQ
WAN Connected

Corporate HQ - DHCP win2k3r2 server hands out SCOPE for it's location
- Also serves a standby disabled scope for branches if
branch server DHCP goes down using IPHELPER on branch router to point to Corp
HQ DHCP

Does this setup sound like a good design?

My question is with the DHCP at corp, how do I ensure the scope that serves
as a backup for branch's in case of emergency is setup correctly?

Should the scope remain disabled?

From what I gather from reading MS article is yes.

In news:9C8CFFFD-5EEF-4AB8-9530-(E-Mail Removed),
Kyle Blake <(E-Mail Removed)> typed:
> Hi,
>
> 13 branches each with DHCP enabled
> 1 corporate HQ
> WAN Connected
>
> Corporate HQ - DHCP win2k3r2 server hands out SCOPE for it's location
> - Also serves a standby disabled scope for
> branches if branch server DHCP goes down using IPHELPER on branch
> router to point to Corp HQ DHCP
>
> Does this setup sound like a good design?
>
> My question is with the DHCP at corp, how do I ensure the scope that
> serves as a backup for branch's in case of emergency is setup
> correctly?
>
> Should the scope remain disabled?
>
> From what I gather from reading MS article is yes.

In this scenario, yes. But what are you going to do about backing up Corp?
Why not create disabled backup scopes on the DHCP servers at each location
to ensure availability?

What article did you read? Please post the link to the article you read.

Microsoft DHCP Best Practices (recommends 80/20)
http://technet2.microsoft.com/window....mspx?mfr=true

Windows Dev Center - Ensuring DHCP Server Availability (says not to use
80/20)
http://www.windowsdevcenter.com/pub/...CP_Server.html


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Hi,

Each branch only has one R2 server and approx 15-30 Xp/Vista Clients.(class c)
So scope at branch could provide 30 ips(x.x.x.50-x.x.x.80), and one at corp
could provide another 30 in upper range (x.x.x.100-x.x.x.130)

This approach makes sense then there is no risk of duplicate ip's being
handed out.

MS Clustering at branch is to expensive and at corporate as well.

Q: At corp the primary dhcp could have the branches "backup scopes" enabled
since there is no real risk right, correct? (local branch dhcp will provide
primary)

Great point, I should make another DHCP server at corp to backup the
corporate one. Not clustering just a hot standby

Seems like a fairly decent dhcp plan for 200?
Backup for branches and backup for corp, all hot standby's!




"Ace Fekay [MVP]" wrote:

> In news:9C8CFFFD-5EEF-4AB8-9530-(E-Mail Removed),
> Kyle Blake <(E-Mail Removed)> typed:
> > Hi,
> >
> > 13 branches each with DHCP enabled
> > 1 corporate HQ
> > WAN Connected
> >
> > Corporate HQ - DHCP win2k3r2 server hands out SCOPE for it's location
> > - Also serves a standby disabled scope for
> > branches if branch server DHCP goes down using IPHELPER on branch
> > router to point to Corp HQ DHCP
> >
> > Does this setup sound like a good design?
> >
> > My question is with the DHCP at corp, how do I ensure the scope that
> > serves as a backup for branch's in case of emergency is setup
> > correctly?
> >
> > Should the scope remain disabled?
> >
> > From what I gather from reading MS article is yes.
>
> In this scenario, yes. But what are you going to do about backing up Corp?
> Why not create disabled backup scopes on the DHCP servers at each location
> to ensure availability?
>
> What article did you read? Please post the link to the article you read.
>
> Microsoft DHCP Best Practices (recommends 80/20)
> http://technet2.microsoft.com/window....mspx?mfr=true
>
> Windows Dev Center - Ensuring DHCP Server Availability (says not to use
> 80/20)
> http://www.windowsdevcenter.com/pub/...CP_Server.html
>
>
> --
> Regards,
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
> MVP Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Infinite Diversities in Infinite Combinations
>
>
>

In news:597FBD75-699F-4B8A-AEFC-(E-Mail Removed),
Kyle Blake <(E-Mail Removed)> typed:
> Hi,
>
> Each branch only has one R2 server and approx 15-30 Xp/Vista
> Clients.(class c) So scope at branch could provide 30
> ips(x.x.x.50-x.x.x.80), and one at corp could provide another 30 in
> upper range (x.x.x.100-x.x.x.130)
>
> This approach makes sense then there is no risk of duplicate ip's
> being handed out.
>
> MS Clustering at branch is to expensive and at corporate as well.

Yes, I agree it is pricey, almost doubling up on hardware.

>
> Q: At corp the primary dhcp could have the branches "backup scopes"
> enabled since there is no real risk right, correct? (local branch
> dhcp will provide primary)

Yes. If you want to go further with this, you could implment a copy of all
scopes on all branch DHCP servers. This way you have total meshed redundacy.
>
> Great point, I should make another DHCP server at corp to backup the
> corporate one. Not clustering just a hot standby
>
> Seems like a fairly decent dhcp plan for 200?
> Backup for branches and backup for corp, all hot standby's!

Yes it does. I think you have a good plan.

Ace

Thank you, could you expand on this statement?

"> Yes. If you want to go further with this, you could implment a copy of all
> scopes on all branch DHCP servers. This way you have total meshed redundacy."

Oh wait, I see, any server anywhere could supply a DHCP and act as anyone's
backup, I believe we'd have to modify the routers IPHELEPER address with
quite an extensive list of all dhcp's in organization.

I mean it sounds possible, I suppose a branch could go down,clients could
grab it from another branch dhcp instead of corporate dhcp.

Interesting.... Would we have to modify the iphelper line on the cisco
router to have a full list of dhcp's in organization to make it fully meshed?

I suppose the order of the list would indicate which backup server is
contacted first?

I wonder!?






"Ace Fekay [MVP]" wrote:

> In news:597FBD75-699F-4B8A-AEFC-(E-Mail Removed),
> Kyle Blake <(E-Mail Removed)> typed:
> > Hi,
> >
> > Each branch only has one R2 server and approx 15-30 Xp/Vista
> > Clients.(class c) So scope at branch could provide 30
> > ips(x.x.x.50-x.x.x.80), and one at corp could provide another 30 in
> > upper range (x.x.x.100-x.x.x.130)
> >
> > This approach makes sense then there is no risk of duplicate ip's
> > being handed out.
> >
> > MS Clustering at branch is to expensive and at corporate as well.
>
> Yes, I agree it is pricey, almost doubling up on hardware.
>
> >
> > Q: At corp the primary dhcp could have the branches "backup scopes"
> > enabled since there is no real risk right, correct? (local branch
> > dhcp will provide primary)
>
> Yes. If you want to go further with this, you could implment a copy of all
> scopes on all branch DHCP servers. This way you have total meshed redundacy.
> >
> > Great point, I should make another DHCP server at corp to backup the
> > corporate one. Not clustering just a hot standby
> >
> > Seems like a fairly decent dhcp plan for 200?
> > Backup for branches and backup for corp, all hot standby's!
>
> Yes it does. I think you have a good plan.
>
> Ace
>
>
>
>

In news:F7EFA3D9-AA75-4A80-ADE5-(E-Mail Removed),
Kyle Blake <(E-Mail Removed)> typed:
> Thank you, could you expand on this statement?
>
> "> Yes. If you want to go further with this, you could implment a
> copy of all
> > scopes on all branch DHCP servers. This way you have total meshed
> > redundacy."
>
> Oh wait, I see, any server anywhere could supply a DHCP and act as
> anyone's backup, I believe we'd have to modify the routers IPHELEPER
> address with quite an extensive list of all dhcp's in organization.
>
> I mean it sounds possible, I suppose a branch could go down,clients
> could grab it from another branch dhcp instead of corporate dhcp.
>
> Interesting.... Would we have to modify the iphelper line on the
> cisco router to have a full list of dhcp's in organization to make it
> fully meshed?
>
> I suppose the order of the list would indicate which backup server is
> contacted first?
>
> I wonder!?

Yes, you would have to modify each router. I didn't say it was easy. :-)

I don;t think any order would do anything for it. I would just have the
backup scope and keep it disabled until needed.

Ace