Share via


DHCP Failover Configuration: Configure Failover failed. Error:20133

Question

Tuesday, August 9, 2016 1:01 AM

Hi All,

We are currently migrating DHCP from a group of Server 2008 R2 and Server 2003 (SP2, Non R2) servers to Server 2012 R2 with a Failover partnership between DHCPSERVER1 and DHCPSERVER2.

Our current focus is migrating the scopes from Server 2008 R2.  Our approach is to use netsh export and import commands (netsh dhcp server v4 export and netsh dhcp server v4 import), since this will be consistent as we export and import from Server 2003 group of DHCP servers.

The migrations have been working fine up until today when we received the following errors:

Creation of failover
configuration on host server............Failed<o:p></o:p>

The server is reintegrating with it's failover partner server. During reintegration...<o:p></o:p>

Configure failover failed. Error: 20133.  The server is reintegrating with it's failover partner server...

See Screenshot...<o:p></o:p>

We are not having any luck when searching the web for the errors above.  There is a MS article which describes the DHCP error messages but ends at 20132 and we are after 20133. Refer: https://technet.microsoft.com/en-us/subscriptions/index/aa363378(v=vs.85).aspx

Has anyone else experienced these issues and resolved.

Any help much appreciated.

Thanks.

belpad

All replies (4)

Wednesday, September 7, 2016 1:19 AM âś…Answered

Sorry it's been a while since posting any updates.

I can confirm that we did raise a MS PSS support incident, which has now been resolved.

In our scenario, the incident was resolved by removing the DHCP Failover partnership, then re-stablishing this.  Failover configuration for ALL migrated scopes was successfully applied after taking these steps.  The Error: 20133 has not returned. 

Therefore, I can mark this reply as the Answer.

Hope this helps anyone else with the same error in the future.

Thanks.

belpad


Tuesday, August 9, 2016 6:33 AM

Hi All,

We are currently migrating DHCP from a group of Server 2008 R2 and Server 2003 (SP2, Non R2) servers to Server 2012 R2 with a Failover partnership between DHCPSERVER1 and DHCPSERVER2.

Our current focus is migrating the scopes from Server 2008 R2.  Our approach is to use netsh export and import commands (netsh dhcp server v4 export and netsh dhcp server v4 import), since this will be consistent as we export and import from Server 2003 group of DHCP servers.

1. What is the original relationship between DHCP 2008R2 and DHCP 2003? Are they configured with split-scope or cluster? What do you want to do with DHCPSERVER1 and DHCPSERVER2?

2. If DHCP 2008R2 and DHCP 2003 configured with split scope, then before importing the files to new DHCP servers, we need to consolidate the lease database.

Please check the following article to learn the detailed process to migrate to DHCP failover:

https://technet.microsoft.com/en-us/library/dn338990(v=ws.11).aspx

Best Regards,

Anne

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].


Tuesday, August 9, 2016 9:50 PM

Hi Anne,

In answer to your questions:

1. There is no relationship between DHCP 2008 R2 and DHCP 2003, since they are in seperate environments.  Apologies that I didn't make that clear in my summary above.  The scopes from each environment are being migrated into their own DHCPSERVER1 and DHCPSERVER2 instances.

2. There are some scopes on the source DHCP 2008 R2 that are split scopes and we have successfully migrated those across already.

We have opted to use netsh for export and import so the process is consistent across the two environments, since DHCP 2003 doesn't support the Powershell commands.

We have also raised a support incident with Microsoft Premier Support.

Regards

belpad


Friday, August 12, 2016 6:13 AM

Hi belpad,

Thanks for feeding back the above information.

>We have also raised a support incident with Microsoft Premier Support.

If you have any progress, welcome to feed back :)

Best Regards,

Anne

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].