Configure failover failed error 20010

Перейти к содержимому

Настройка DHCP failover. Error: 20010. The specified option does not exist

Windows Server 2012 позволяет довольно просто организовать отказоустойчивую конфигурацию из двух DHCP серверов. Выбираем в контекстном меню протокола или конкретной области «Configure Failover…», указываем тип конфигурации (балансировка нагрузки или режим горячей замены) и настраиваем соответствующие параметры (период синхронизации базы, процент обслуживаемых клиентов и т.д.). После этого все настройки первого сервера (области, параметры) автоматически переезжают на второй сервер.

Но, как всегда, есть нюансы.

В моём случае это вылилось в появление ошибки

Error: 20010. The specified option does not exist.

Причина оказалась в том, что для некоторых областей были созданы кастомные параметры (для телефонии). А как выяснилось, параметры, созданные вручную, сервер не может воссоздать автоматически на партнёре. Прописать на областях может, а создать — нет.

Решение — зайти в «Set Predefined Options…» на втором сервере и воссоздать вручную все кастомные параметры, прописанные на первом сервере. Если создавали их не вы, то отличить кастомные параметры от встроенных поможет кнопка «Delete», которая становится активной только в случае выбора параметра, созданного вручную (см второй скриншот). В моём случае, помимо параметров, пришлось прописать ещё и дополнительный Vendor Class. После чего всё успешно отреплицировалось и заработало.

Источник

DHCP failover error 20010 – How we fix it

Are you looking for a solution to the ‘DHCP failover error 20010’? we can help you with it.

Here at Bobcares, we have seen several such DHCP-related errors as part of our Server Management Services for web hosts and online service providers.

Today we will take a look at the causes for this error and see how to fix it.

What causes DHCP failover error 20010 to occur

Before we discuss the solution to this error message, let’s take a look at why does this error occurs.

This error can occur while configuring DHCP failover for one of the scopes.

Also, this error can occur with any scope that has one or more custom DHCP attributes.

For instance, the error appears as below.

How we fix DHCP failover error 20010

Now let’s take a look at the solution our Support Engineers provide to resolve this error.

1. Ensure that all the custom settings from the primary DHCP server are also mirrored on the other server. Because it is possible that those customizations are vast and numerous. The rule is if you have more customizations to replicate then you are prone to more human errors.

Right-click on IPv4 and select “Set Predefined Options”, here you can confirm if both the DHCP servers had the same custom options created.

2. It is always good to have a backup of the DHCP settings when no one needs it. You can take the backup by clicking on the server name under the DHCP console and select backup. After that, copy the folder that you backed up to the secondary server. Then restore from that backup. Finally, delete all scopes on the secondary server.

[Need any further assistance in fixing DHCP errors? – We are here to help you]

Conclusion

In short, Today, we saw the solution provided by our Support Engineers to this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник

Configure failover failed error 20010

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

MCITP Exchange 2010 | MCTS Exchange 2007 | MCITP Lync Server 2010 | MCTS Windows 2008 | MCSE 2003

Answers

The blogger encountered the same problem with yours and provided a solution, hope this helps with your problem:

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

The blogger encountered the same problem with yours and provided a solution, hope this helps with your problem:

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

I’ve got the same Problem for some of my scopes (Error 20010 The specified Option does not exist). 21 scopes did just fine, but 2 scopes show Error 20010. The scopes are DHCP only and the Options in those scopes do exist in other scopes that I set up for Failover as well. I’ve tried for 2 days now, but nothing worked so far.

I tried the following (all starting with a new 2nd DHCP)

1) Importing the config from the 1st DHCP, then deleting all scopes on the 2nd before configuring Failover, as suggested in the blog Daniel mentioned.

2) Importing only the Server Settings and Options before configuring Failover.

3) Deleting all scope options on source scope before configuring failover

Is there any way to get to the core of the error message and identify the options that prevent the configuration of failover?

Both Servers are virtual 2012 R2 DCs (Hyper-V) of the same Domain on the same site and in the same subnet.

I am having the same problem- went through and manually created the server options, also deleted them and ran a report of those options from my would-be-master DHCP server. Still get the «option doesn’t exist» error. Couldn’t they have a log somewhere PLEASE so I can find what this option is? wasted hours on this so far. I did do an import of a W2003 DHCP database when I migrated the new «DHCP Server1» a while back- I have a feeling there is some hidden or corrupted option in there it isn’t reading correctly. Or perhaps the database i migrated is still in some 2003 format and needs tables to be updated to 2012 R2-proper?

Let’s go Microsoft- give us a way to get more diagnostics on this.

I think I finally found a workaround to this problem:

First, I checked that all custom Options were present on the 2nd Server.

Then I deactivated these options on the source DHCP. Now the configuring failover process worked just fine.

As a last step I reactivated the options on both servers.

Pls i really need help here. i have set up windows server 2012r2, install DHCP, DNS, ADCS, ADDS and REMOTE ACCESS.
I have also set up the REMOTE ACCESS with VPN using DOMAIN NAME pointing to PUBLIC IP given by MY ISP in my domain service host. EG (xyz.biz to 187.234.76.167).. I HAVE forward PORT on my mikrotic router to ports 80: and 443: .. pointing to the internal static IP of the server.. i have no error on the remote access configuration page . but i cant access my server when i tried using . (REMOTE.XYZ.BIZ) on another system . and also i get error connecting thru vpn .. HELP HELP I WANT TO CRY.

If you look at the Scope Options section on the scope you are trying to configure for the failover you will notice that there have been some custom Scope Option values configured. The custom option fields must be created on the destination failover server to eliminate this error. You can recreate the custom scope options by following the below instructions.

Open DHCP.
In the console tree, click the applicable DHCP server.
On the Action menu, click Set Predefined Options.
In Predefined Options and Values, click Add.
In Option Type, type the required information to define the new option, and then click OK.

After you create the custom option fields, go to the scope on the source failover server and right-click and select Replicate Scope.

Источник

Configure failover failed error 20010

Вопрос

MCITP Exchange 2010 | MCTS Exchange 2007 | MCITP Lync Server 2010 | MCTS Windows 2008 | MCSE 2003

Ответы

The blogger encountered the same problem with yours and provided a solution, hope this helps with your problem:

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Все ответы

The blogger encountered the same problem with yours and provided a solution, hope this helps with your problem:

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

I’ve got the same Problem for some of my scopes (Error 20010 The specified Option does not exist). 21 scopes did just fine, but 2 scopes show Error 20010. The scopes are DHCP only and the Options in those scopes do exist in other scopes that I set up for Failover as well. I’ve tried for 2 days now, but nothing worked so far.

I tried the following (all starting with a new 2nd DHCP)

1) Importing the config from the 1st DHCP, then deleting all scopes on the 2nd before configuring Failover, as suggested in the blog Daniel mentioned.

2) Importing only the Server Settings and Options before configuring Failover.

3) Deleting all scope options on source scope before configuring failover

Is there any way to get to the core of the error message and identify the options that prevent the configuration of failover?

Both Servers are virtual 2012 R2 DCs (Hyper-V) of the same Domain on the same site and in the same subnet.

I am having the same problem- went through and manually created the server options, also deleted them and ran a report of those options from my would-be-master DHCP server. Still get the «option doesn’t exist» error. Couldn’t they have a log somewhere PLEASE so I can find what this option is? wasted hours on this so far. I did do an import of a W2003 DHCP database when I migrated the new «DHCP Server1» a while back- I have a feeling there is some hidden or corrupted option in there it isn’t reading correctly. Or perhaps the database i migrated is still in some 2003 format and needs tables to be updated to 2012 R2-proper?

Let’s go Microsoft- give us a way to get more diagnostics on this.

I think I finally found a workaround to this problem:

First, I checked that all custom Options were present on the 2nd Server.

Then I deactivated these options on the source DHCP. Now the configuring failover process worked just fine.

As a last step I reactivated the options on both servers.

Pls i really need help here. i have set up windows server 2012r2, install DHCP, DNS, ADCS, ADDS and REMOTE ACCESS.
I have also set up the REMOTE ACCESS with VPN using DOMAIN NAME pointing to PUBLIC IP given by MY ISP in my domain service host. EG (xyz.biz to 187.234.76.167).. I HAVE forward PORT on my mikrotic router to ports 80: and 443: .. pointing to the internal static IP of the server.. i have no error on the remote access configuration page . but i cant access my server when i tried using . (REMOTE.XYZ.BIZ) on another system . and also i get error connecting thru vpn .. HELP HELP I WANT TO CRY.

If you look at the Scope Options section on the scope you are trying to configure for the failover you will notice that there have been some custom Scope Option values configured. The custom option fields must be created on the destination failover server to eliminate this error. You can recreate the custom scope options by following the below instructions.

Open DHCP.
In the console tree, click the applicable DHCP server.
On the Action menu, click Set Predefined Options.
In Predefined Options and Values, click Add.
In Option Type, type the required information to define the new option, and then click OK.

After you create the custom option fields, go to the scope on the source failover server and right-click and select Replicate Scope.

Источник

Are you trying to fix «DHCP failover error 20010»? This guide will help you fix it.

What triggers DHCP failover error 20010?

Progress of failover configuration

The log below shows the progress of the various tasks for configuring failover including any errors encountered.

Add scopes on partner server .... In progress

Add scopes on partner server .... Failed

The specified option does not exist.

Roll back - delete scopes on partner.... Successful

Configure failover failed. Error: 20010. The specified option does not exist.

How to solve DHCP failover error 20010?

Need support in solving DHCP errors? We are available to help you today.

Windows Server 2012 DHCP Failover feature is really something we should have a long time ago. Before this feature, when we wanted to achieve DHCP service redundancy, we had to have at least two DHCP servers and we had to split each of our scopes into two. For example, if we had a 192.168.0.0/24 scope, we set up one DHCP server to hand out addresses from 192.168.0.1 to 192.168.0.129 and another DHCP server handing out addresses from 192.168.0.129 to 192.168.0.254. This is just an example. And it is an easy one. If had network such as /27 or /21, a math could be a little bit more complicated.

Thankfully, this is over. Now we can have one DHCP server setup correctly for a particular scope, let’s say 192.168.0.0/24, handing out all addresses from 192.168.0.1 to 192.168.0.254, and add another DHCP server that can hand out addresses if primary server fails, or handing out addresses along with the primary server. We can achieve this with only few mouse clicks!

So, here is our scenario…

We have two domain controllers running Windows 2012R2 Server Core with DHCP server role installed. Both DHCP servers are authorized to the domain. Only the DC-CORE-1 is setup with a test scope:

And we can verify that our client received the IP parameters from DC-CORE-1:

Before we create our failover, let’s add some custom DHCP options to our first server. These options are common in many enterprises and will help us later to see how they can cause us problems.

These custom options we will create:

•  150 TFTP Servers
• 161 Wyse FTPServers
• 162 Wyse FTP Starting Path

First option lists TFTP servers for IP phones, for example, and last two are used for VDI environment, or Virtual Desktop Infrastructure. These are just examples. We can have other options as well, such as option that LWAP access points use for finding a wireless LAN controller. Bottom line is we have these options and they can cause problems, as we shall see.

Let’s create option 150…

In the DHCP Manager, expand DC-CORE-1.popravak.local, right click IPv4 and click “Set Predefined Options…“:

Then we click Add and create our TFTP custom option:

Then we add our TFTP servers:

This is just example of creating a custom option. Other options are created in a similar fashion…

Now let’s try setting up our DHCP Failover Cluster.

Right click the scope and click “Configure Failover…“:

Then complete the wizard…

We select scope or scopeS.

Then chose our partner server.

Give a name to this relationship, select if we want active/passive or active/active mode and percentage of IP address distribution. We also give a shared secret to be used for authentication purposes.

Finally, we complete the wizard.

We can see that the failover setup was successful.

Fine. But before we test the failover, let’s add custom attributes into play. For this we will create another scope for IP phones. This scope will use 192.168.0.0/24 address space and each IP phone requires one ore more TFTP server’s IP addresses. So we add previously created option 150.

Now let’s replicate this pool with our partner server.

Whoops!

We can see that now the failover of our pool that uses custom options failed with the error message:

Configure failover failed. Error: 20010. The specified option does not exist.

This will happen with any scope that has one or more custom DHCP attributes. This is what causes our replication to fail:

Because we have to have these attributes, what are we going to do? Well, we have to create the same custom attributes on our partner server and then try to replicate our scope. We don’t need to create scopes on partner server, because they will replicate, but just create the attributes that will be used in particular scope we are trying to replicate. The 150 attribute in this case. So we go through the “Set Predefined Options…” on the partner server. Once we do that, we can try to replicate our IP phones scope.

Now we have a success!

We don’t have the same parameters within the custom attributes we create in our partner scope. For example, IP addresses of TFTP servers don’t have to match those on the primary server. Perhaps types don’t have to match either. Only Code has to match.  A setup such as this may or may not make sense, but that’s another story.

Now, let’s shutdown the DHCP service on primary server.

This will simulate the DC-CORE-1 server failure. From the DHCP standpoint of course. Now we renew our IP address. And we can see that we received our IP address from the partner server.

Very nice feature 🙂