Меню

dhcp сбой настройки отработки отказа ошибка 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 сбой настройки отработки отказа ошибка 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?

Читайте также:  установка windows программе не удалось создать новый

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.

источник

DHCP Failover – Error 20010 The specified option does not exist

Problem:

When configuring DHCP failover for one of my scopes the process kept failing with the message “Configure failover failed. Error 20010. The specified option does not exist”

Читайте также:  razer blackwidow chroma настройка подсветки

Workaround:

Right-clicking on IPv4 and selecting “Set Predefined Options” I confirmed that both DHCP servers had the same custom options created. This is the normal cause of this message, however in my case even though both servers had the exact same predefined options configured the message persisted.

I narrowed the issue down to a particular option by creating a new test scope with the same options and removing the configured options one-by-one until replication worked. I still don’t know what the exact cause was but I determined I no longer required this option on the scope so I removed in from the scope configuration.

My guess is it had something to do with that the scope coming over from a 2003 server to a 2016 server via the netsh export/import commands. I can only guess there is a bit of dodgy configuration around this predefined option but everything else seems fine.

Below is a screenshot of the option that was causing me pain;

About The Author

Phil Eddies

I am an IT Operations Manager, managing all aspects of the IT infrastructure and service for a mid sized UK based company. I have been working full time in IT since 2001 in 1st to 3rd line and System Administration roles. MCSA, MCSE, CCNA, Citrix CCA

источник

Dhcp сбой настройки отработки отказа ошибка 20010

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.

All replies

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

Читайте также:  модем дсл 2640u настройка

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.

источник

Добавить комментарий

Adblock
detector