Steve McAuliffe
asked on
DHCP Failover Relationship caveats
Hi mates,
looking to reinstall DHCP server(Serv-A) from 2012 to 2012R2 with same name and IP. This is partner server in dhcp relationship of two servers.
2nd partner(Serv-B) is already on 2012R2(installed couple of months before). MCLT of failover relationship is 1 hour and it is in load balance mode. Enable message authentication is checked with shared secret.
Now question is
1-)Is it necessary to remove relationship before demoting serv-A as the installation will took more than 1 hour?
Reason this is bothering me to have 2nd opinion is, last time when i was rebuilding serv-B from 2012 to 2012R2, i didnt break failover relationship between DHCPs. every configuration remain the same post promotion(i.e: IP, hostname, new certs in personal store). but under the failover status for partner server, it said: state of the server :DOWN
So then i had to remove relationship and add both servers(New and Old) in new relationship, and replicate scopes from Serv-A to Serv-B to make them work in load balance mode onwards.
Looking for some guidelines around my question and best way of achieving this task.
Thanks
looking to reinstall DHCP server(Serv-A) from 2012 to 2012R2 with same name and IP. This is partner server in dhcp relationship of two servers.
2nd partner(Serv-B) is already on 2012R2(installed couple of months before). MCLT of failover relationship is 1 hour and it is in load balance mode. Enable message authentication is checked with shared secret.
Now question is
1-)Is it necessary to remove relationship before demoting serv-A as the installation will took more than 1 hour?
Reason this is bothering me to have 2nd opinion is, last time when i was rebuilding serv-B from 2012 to 2012R2, i didnt break failover relationship between DHCPs. every configuration remain the same post promotion(i.e: IP, hostname, new certs in personal store). but under the failover status for partner server, it said: state of the server :DOWN
So then i had to remove relationship and add both servers(New and Old) in new relationship, and replicate scopes from Serv-A to Serv-B to make them work in load balance mode onwards.
Looking for some guidelines around my question and best way of achieving this task.
Thanks
Yes, remove the relationship of the old server. Even if the new server name and IP match the old server, the server's AD SID is different.
ASKER
Thanks eeRoot, i also wondering some precise guidelines about adding new server(coupling up) into new DHCP relationship. Though gone through some useful technet blogs/articles and have some knowledgebase from past but wanting to vet my below plan.
1-)After building server(serv-a) and adding AD, DNS, DHCP Role. stop dhcp server service and cleanup dhcp folder under system32, then start dhcp server service.
2-)On serv-a, from powershell - Create a failover relationship via add-dhcpserverv4Failover -ComputerName serv-a.abc.com -PartnerServer serv-b.abc.com -Name dhcp1-dhcp2 -ScopeID 10.1.0.0 -LoadBalancePercent 80 -SharedSecret **** -Force
3-)Now on dhcp console of serv-b , underneath in ipv4, click on configure failover scopes and select all scopes and trigger failover scopes replication.
Is this correct?
any sanity check before/after or additional steps or considerations around?
1-)After building server(serv-a) and adding AD, DNS, DHCP Role. stop dhcp server service and cleanup dhcp folder under system32, then start dhcp server service.
2-)On serv-a, from powershell - Create a failover relationship via add-dhcpserverv4Failover -ComputerName serv-a.abc.com -PartnerServer serv-b.abc.com -Name dhcp1-dhcp2 -ScopeID 10.1.0.0 -LoadBalancePercent 80 -SharedSecret **** -Force
3-)Now on dhcp console of serv-b , underneath in ipv4, click on configure failover scopes and select all scopes and trigger failover scopes replication.
Is this correct?
any sanity check before/after or additional steps or considerations around?
Yes, that looks correct.
ASKER
Sorry to be a pain..but looking for some detail answer as
i am slightly confused about the scope id parameter in creating relationship
ScopeID 10.1.0.0
What is this for ? and is this need to be already exist on new server? any tips and tricks
i am slightly confused about the scope id parameter in creating relationship
ScopeID 10.1.0.0
What is this for ? and is this need to be already exist on new server? any tips and tricks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Footech