{"id":76225,"date":"2020-04-01T01:42:48","date_gmt":"2020-03-31T23:42:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa"},"modified":"2020-04-01T01:42:48","modified_gmt":"2020-03-31T23:42:48","slug":"nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa","title":{"rendered":"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>The purpose of this article is to simplify the configuration of the DHCP service for the VXLAN BGP EVPN and DFA factory using Microsoft Windows Server 2016\/2019.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/f9380c07801612786865f7756042df07.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nIn the official documentation, the DHCP service based on Microsoft Windows Server 2012 for the factory is configured as a SuperScope, which includes a Loopback pool (the highlight here is the exception from the pool of all IP addresses in the pool (excluded IP address = pool)) and pools for assigning IP addresses for real networks (the highlight here is configuring policies that filter the DHCP Relay Circuit ID, and this DHCP relay Circuit ID contains the VNI for the network, i.e., for another pool, this DHCP Relay Circuit ID will be slightly different). <\/p>\n<pre><code class=\"plaintext\">To configure DHCP on Windows Server.  \n\n1. Create a super scope. Within the super scope, create scope B, S1, S2, S3, \u2026, Sn for subnet B and the subnets for each segment.  \n2. In scope B, specify the 'Exclusion Range' to be the entire address range (so that the offered address range must not be from this scope).  \n3. For every segment scope Si, specify a policy that matches on Agent Circuit ID with the value of '0108000600XXXXXX', where '0108000600' is a fixed value for all segments, the 6 numbers \"XXXXXX\" represent the segment ID value in hexadecimal. Also, ensure to check the Append wildcard(*) checkbox.  \n4. Set the policy address range to the entire range of the scope.<\/code><\/pre>\n<p>\nThis article addresses the following questions:<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/#WhyVXLANDHCPRelayDoNotSupportWindows2008andEarley\">Why are Microsoft Windows Server 2000\/2003\/2008 not supported?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/#WhyWindows2012DHCPSoHardToConfigure\">Why is the configuration so complicated in Microsoft Windows Server 2012?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/#howsimplifiedsetupwindows20162019\">How has the configuration been simplified in Microsoft Windows Server 2016\/2019?<\/a><\/noindex><\/li>\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<b class=\"spoiler_title\">Content<\/b><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#introduction\">Introduction<\/a><\/noindex>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#ConfigurationNexusDHCPRelay\">How to configure DHCP Relay in the VXLAN BGP EVPN factory<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#RFCDHCPRelayVXLAN\">RFCs used in DHCP Relay with the VXLAN BGP EVPN factory<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#CiscoDocumentationEvalution\">The evolution of Cisco documentation regarding DHCP configuration on Microsoft Windows Server 2012<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#DHCPSuperScopeAndPolicy\">DHCP in Microsoft Windows Server<\/a><\/noindex> (<noindex><a rel=\"nofollow\" href=\"#DHCPSuperScope\">superscope<\/a><\/noindex> &amp; <noindex><a rel=\"nofollow\" href=\"#DHCPPolicy\">, containing our policy file:<\/a><\/noindex>)<\/li>\n<\/ul>\n<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#Common\">Main Section<\/a><\/noindex>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#WhyVXLANDHCPRelayDoNotSupportWindows2008andEarley\">Why are Microsoft Windows Server 2000\/2003\/2008 not supported?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#WhyWindows2012DHCPSoHardToConfigure\">Why is the configuration so complicated in Microsoft Windows Server 2012?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#howsimplifiedsetupwindows20162019\">How has the configuration been simplified in Microsoft Windows Server 2016\/2019?<\/a><\/noindex>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#windows20162019dhcpexample\">Example<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#windows20162019dhcpsetup\">Configuring the DHCP service on Microsoft Windows Server 2019<\/a><\/noindex><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#finale\">Conclusion<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#listofsources\">List of sources<\/a><\/noindex><\/li>\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"introduction\"><\/a><\/noindex><\/p>\n<h2>Introduction<\/h2>\n<p>\nThis section briefly lists all the source data: Instructions for configuring network equipment, RFCs used in DHCP packets in eVPN factories, and an overview of the evolution of DHCP server settings on Microsoft Windows Server 2012 in Cisco documentation. It also includes brief information about Superscope and Policy in the DHCP service on Microsoft Windows Server.<br \/>\n<noindex><a rel=\"nofollow\" name=\"ConfigurationNexusDHCPRelay\"><\/a><\/noindex><\/p>\n<h4>How to configure DHCP Relay in the VXLAN BGP EVPN, DFA factory<\/h4>\n<p>\nConfiguring DHCP Relay in the VXLAN BGP EVPN factory is not the main topic of this article, as it is quite simple. I provide links to documentation and some details on configurations for network equipment.<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/7-x\/vxlan\/configuration\/guide\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x_appendix_0110.html\">Nexus 9000 VXLAN Configuration Guide 7.X <\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/93x\/vxlan\/configuration\/guide\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x_appendix_010111.html#id_103149\">Nexus 9000 VXLAN Configuration Guide 9.3<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/dfa\/configuration\/b-dfa-configuration\/segment-id-support-for-dhcp-relay.html\">DFA (Cisco Dynamic Fabric Automation)<\/a><\/noindex><\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">Example configuration of DHCP Relay on Nexus 9000V v9.2(3)<\/b><\/p>\n<pre><code class=\"plaintext\">service dhcp\nip dhcp relay\nip dhcp relay information option\nip dhcp relay information option vpn\ninterface loopback10\n  vrf member VRF1\n  ip address 10.120.0.1\/32 tag 1234567\ninterface Vlan12\n  no shutdown\n  vrf member VRF1\n  no ip redirects\n  ip address 10.120.251.1\/24 tag 1234567\n  no ipv6 redirects\n  fabric forwarding mode anycast-gateway\n  ip dhcp relay address 10.0.0.5\n  ip dhcp relay source-interface loopback10\n<\/code><\/pre>\n<p><noindex><a rel=\"nofollow\" name=\"RFCDHCPRelayVXLAN\"><\/a><\/noindex><\/p>\n<h4>RFCs implemented in the operation of the DHCP Relay service in VXLAN BGP EVPN fabrics<\/h4>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/93x\/vxlan\/configuration\/guide\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x_appendix_010111.html#id_103141\">List of RFCs for Nexus 9000 v9.3<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/7-x\/vxlan\/configuration\/guide\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x_appendix_0110.html#concept_wm1_f5k_4fb\">List of RFCs for Nexus 9000 v7.x<\/a><\/noindex><\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">RFC#6607: Sub-option 151(0x97) \u2014 Virtual Subnet Selection<\/b><\/p>\n<pre><code class=\"plaintext\">\u2022\tSub-option 151(0x97) - Virtual Subnet Selection (Defined in RFC#6607)\nUsed to convey VRF related information to the DHCP server in an MPLS-VPN and VXLAN EVPN multi-tenant environment.<\/code><\/pre>\n<p>\nThe \"name\" of the VRF in which the client is located is transmitted.<\/p>\n<p><b class=\"spoiler_title\">RFC#5107: Sub-option 11(0xb) \u2014 Server ID Override<\/b><\/p>\n<pre><code class=\"plaintext\">\u2022\tSub-option 11(0xb) - Server ID Override (Defined in RFC#5107.) \nThe server identifier (server ID) override sub-option allows the DHCP relay agent to specify a new value for the server ID option, which is inserted by the DHCP server in the reply packet. This sub-option allows the DHCP relay agent to act as the actual DHCP server such that the renew requests will come to the relay agent rather than the DHCP server directly. The server ID override sub-option contains the incoming interface IP address, which is the IP address on the relay agent that is accessible from the client. Using this information, the DHCP client sends all renew and release request packets to the relay agent. The relay agent adds all of the appropriate sub-options and then forwards the renew and release request packets to the original DHCP server. For this function, Cisco\u2019s proprietary implementation is sub-option 152(0x98). You can use the ip dhcp relay sub-option type cisco command to manage the function.<\/code><\/pre>\n<p>\nThis option is used for the client to send a request to renew the lease on the IP address used in this option. (In Cisco VXLAN BGP EVPN, this is the Anycast gateway address by default for the client.)<\/p>\n<p><b class=\"spoiler_title\">RFC#3527: Sub-option 5(0x5) \u2014 Link Selection<\/b><\/p>\n<pre><code class=\"plaintext\">Sub-option 5(0x5) - Link Selection (Defined in RFC#3527.) \n\nThe link selection sub-option provides a mechanism to separate the subnet\/link on which the DHCP client resides from the gateway address (giaddr), which can be used to communicate with the relay agent by the DHCP server. The relay agent will set the sub-option to the correct subscriber subnet and the DHCP server will use that value to assign an IP address rather than the giaddr value. The relay agent will set the giaddr to its own IP address so that DHCP messages are able to be forwarded over the network. For this function, Cisco\u2019s proprietary implementation is sub-option 150(0x96). You can use the ip dhcp relay sub-option type cisco command to manage the function.<\/code><\/pre>\n<p>\nThe network address from which the client needs the IP address.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"CiscoDocumentationEvalution\"><\/a><\/noindex><\/p>\n<h4>The evolution of Cisco documentation regarding DHCP configuration on Microsoft Windows Server 2012<br \/>\n<\/h4>\n<p>\nI included this section because a positive trend is observed from the vendor:<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/7-x\/vxlan\/configuration\/guide\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x_appendix_0110.html\">Nexus 9000 VXLAN Configuration Guide 7.3<\/a><\/noindex> <\/p>\n<p>The documentation only includes the configuration of DHCP Relay on network equipment.<\/p>\n<p>Another article was used for configuring DHCP on Windows Server 2012:<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/support\/docs\/switches\/nexus-9000-series-switches\/200248-Configuring-Microsoft-Windows-Server-201.html\">Configuring Microsoft Windows Server 2012 to provide DHCP services in an eVPN Scenario (VXLAN, Cisco One Fabric, etc)<\/a><\/noindex><\/p>\n<p>This article states that each network\/VNI requires its own SuperScope pairing and its own set of Loopback addresses:<\/p>\n<pre><code class=\"plaintext\">If multiple DHCP Scopes are required for multiple subnets, you need to create one LoopbackX per subnet\/vlan on all LEAFS and create a superscope with a loopbackX range scope and actual client IP subnet scope per vlan.<\/code><\/pre>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/93x\/vxlan\/configuration\/guide\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x_appendix_010111.html#id_103149\">Nexus 9000 VXLAN Configuration Guide 9.3<\/a><\/noindex><\/p>\n<p>Added Windows 2012 Server settings to the network equipment configuration documentation. One SuperScope is required for all address pools in the data center, and this SuperScope serves as the boundary of the data center:<\/p>\n<pre><code class=\"plaintext\">Create Superscope for all scopes you want to use for Option 82-based policies.\nNote\nThe Superscope should combine all scopes and act as the administrative boundary.<\/code><\/pre>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/dfa\/configuration\/b-dfa-configuration\/segment-id-support-for-dhcp-relay.html#concept_3347D39EEA1B44B1839904FBAA4708EE\">Cisco Dynamic Fabric Automation<\/a><\/noindex><\/p>\n<p>Everything is described very succinctly:<\/p>\n<pre><code class=\"plaintext\">Let us assume the switch is using the address from subnet B (which may be the backbone subnet, management subnet, or any customer-designated subnet for this purpose) to communicate with the Windows DHCP server. In DFA, we have subnets S1, S2, S3, \u2026, Sn for segments s1, s2, s3, \u2026, sn.  \n\nTo configure DHCP on Windows Server.  \n\n1. Create a super scope. Within the super scope, create scope B, S1, S2, S3, \u2026, Sn for subnet B and the subnets for each segment.  \n2. In scope B, specify the 'Exclusion Range' to be the entire address range (so that the offered address range must not be from this scope).  \n3. For every segment scope Si, specify a policy that matches on Agent Circuit ID with the value of '0108000600XXXXXX', where '0108000600' is a fixed value for all segments, the 6 numbers \"XXXXXX\" represent the segment ID value in hexadecimal. Also, ensure to check the Append wildcard(*) checkbox.  \n4. Set the policy address range to the entire range of the scope.\n<\/code><\/pre>\n<p>\n<noindex><a rel=\"nofollow\" name=\"DHCPSuperScopeAndPolicy\"><\/a><\/noindex><\/p>\n<h4>DHCP in Microsoft Windows Server (superscope &amp; policy)<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" name=\"DHCPSuperScope\"><\/a><\/noindex><\/p>\n<h4><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/openspecs\/windows_protocols\/ms-dhcpm\/4b3dafe4-70e5-4085-969e-4bb402d9c68b\">SuperScope<\/a><\/noindex><\/h4>\n<p><\/p>\n<pre><code class=\"plaintext\">Superscope is an administrative feature of a DHCP server that can be used to group multiple scopes as a single administrative entity. Superscope allows a DHCP server to provide leases from more than one scope to clients on a single physical network. Scopes added to a superscope are called member scopes.<\/code><\/pre>\n<p>\nWhat is a SuperScope \u2013 it\u2019s functionality that allows grouping multiple pools of IP addresses into one administrative unit. To announce IP addresses from several pools to users within a single physical network (within one VLAN). If a request came to a pool of addresses within a SuperScope, then an address can be issued to the client from another Scope that is part of this SuperScope.<br \/>\n<noindex><a rel=\"nofollow\" name=\"DHCPPolicy\"><\/a><\/noindex><\/p>\n<h4><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/previous-versions\/windows\/it-pro\/windows-server-2012-r2-and-2012\/dn425039(v%3Dws.11)\">Policy<\/a><\/noindex><\/h4>\n<p><\/p>\n<pre><code class=\"plaintext\">The DHCP Server role in Windows Server 2012 introduces a new feature that allows you to create IPv4 policies that specify custom IP address and option assignments for DHCP clients based on a set of conditions.\n\nThe policy-based assignment (PBA) feature allows you to group DHCP clients by specific attributes based on fields contained in the DHCP client request packet. PBA enables targeted administration and greater control of the configuration parameters delivered to network devices with DHCP.<\/code><\/pre>\n<p>\nPolicies \u2013 allow assigning IP addresses to users based on the type of user or parameter. Cisco engineers use policies in Windows Server 2012 to filter by VNI (Virtual Network Identifier). <br \/>\n<noindex><a rel=\"nofollow\" name=\"Common\"><\/a><\/noindex><\/p>\n<h2>Main Section<\/h2>\n<p>\nThis section presents the research results on why it is not supported, how it works (logic), what is new, and how this new aspect will help us.<br \/>\n<noindex><a rel=\"nofollow\" name=\"WhyVXLANDHCPRelayDoNotSupportWindows2008andEarley\"><\/a><\/noindex><\/p>\n<h4>Why are Microsoft Windows Server 2000\/2003\/2008 not supported?<\/h4>\n<p>\nMicrosoft Windows Server 2008 and earlier versions do not process Option 82 and return the reverse packet without Option 82.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/social.technet.microsoft.com\/Forums\/windowsserver\/en-US\/e093f0ea-9cee-4d65-85ce-20100038d9c7\/win2k8-r2-dhcp-problem-with-option82?forum=winserverNIS\">Win2k8 R2 DHCP problem with Option 82<\/a><\/noindex><\/p>\n<ol>\n<li>A request from the client is sent as a Broadcast (DHCP Discover).<\/li>\n<li>The equipment (Nexus) sends a packet to the DHCP server (DHCP Discover + Option 82).<\/li>\n<li>The DHCP server receives and processes the packet, sending back a response, but without Option 82. (DHCP Offer \u2013 without Option 82)<\/li>\n<li>The equipment (Nexus) receives a packet from the DHCP server. (DHCP Offer) However, it does not send this packet to the end user.<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">Sniffer data \u2014 on Windows Server 2008 and on the DHCP client<\/b>Windows Server 2008 receives a request from the network equipment. (Option 82 is present in the list)<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/267332ca80f1f1a2522307d791074644.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nWindows Server 2008 sends a response to the network equipment. (Option 82 is absent from the options list in the packet)<br \/>\n<img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/dea552f68344f7c1c4e7904c67859e40.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nRequest from the client \u2013 DHCP Discover is present and DHCP Offer is absent<br \/>\n<img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/611e7c61971d92813fad5e85541c1926.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nStatistics on network equipment:<\/p>\n<pre><code class=\"plaintext\">NEXUS-9000V-SW-1# show ip dhcp relay statistics \n----------------------------------------------------------------------\nMessage Type             Rx              Tx           Drops  \n----------------------------------------------------------------------\nDiscover                  8               8               0\nOffer                     8               8               0\nRequest(*)                0               0               0\nAck                       0               0               0\nRelease(*)                0               0               0\nDecline                   0               0               0\nInform(*)                 0               0               0\nNack                      0               0               0\n----------------------------------------------------------------------\nTotal                    16              16               0\n----------------------------------------------------------------------\n\nDHCP L3 FWD:\nTotal Packets Received                           :         0\nTotal Packets Forwarded                          :         0\nTotal Packets Dropped                            :         0\nNon DHCP:\nTotal Packets Received                           :         0\nTotal Packets Forwarded                          :         0\nTotal Packets Dropped                            :         0\nDROP:\nDHCP Relay not enabled                           :         0\nInvalid DHCP message type                        :         0\nInterface error                                  :         0\nTx failure towards server                        :         0\nTx failure towards client                        :         0\nUnknown output interface                         :         0\nUnknown vrf or interface for server              :         0\nMax hops exceeded                                :         0\nOption 82 validation failed                      :         0\nPacket Malformed                                 :         0\nRelay Trusted port not configured                :         0\nDHCP Request dropped on MCT                      :         0\n*  -  These counters will show correct value when switch \nreceives DHCP request packet with destination ip as broadcast\naddress. If request is unicast it will be HW switched\nNEXUS-9000V-SW-1#<\/code><\/pre>\n<p>\n<noindex><a rel=\"nofollow\" name=\"WhyWindows2012DHCPSoHardToConfigure\"><\/a><\/noindex><\/p>\n<h4>Why is the configuration so complicated in Microsoft Windows Server 2012?<\/h4>\n<p>\nRFC#3527 (Option 82 Sub-option 5(0x5) \u2014 Link Selection) is not yet supported in Microsoft Windows Server 2012<br \/>\nHowever, the Policy functionality has already been implemented.<\/p>\n<p>How it works:<\/p>\n<ul>\n<li>Microsoft Windows Server 2012 has a super-scope (SuperScope) that includes Loopback addresses and pools for real networks.<\/li>\n<li>The selection of the pool for IP address assignment falls into the SuperScope, since the response came from DHCP Relay with a Source address of Loopback, which is part of the SuperScope.<\/li>\n<li>Using Policy, the request selects from the Superscope the member scope, whose VNI is contained in Option 82 Suboption 1 Agent Circuit ID. (\"0108000600\" + 24 bits of VNI + 24 bits of values which are unknown to me, but the sniffer shows 0 in this field.)<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"howsimplifiedsetupwindows20162019\"><\/a><\/noindex><\/p>\n<h4>How has the configuration been simplified in Microsoft Windows Server 2016\/2019?<\/h4>\n<p>\nMicrosoft Windows Server 2016 has implemented the functionality of RFC#3527. This means that Windows Server 2016 can recognize the correct network from Option 82 Sub-option 5(0x5) \u2014 Link Selection. <\/p>\n<p>This immediately raises three questions:<\/p>\n<ul>\n<li>Can we do without Superscope?<\/li>\n<li>Can we do without Policy and converting VNI to hexadecimal?<\/li>\n<li>Can we do without Scope for Loopback addresses DHCP Source?<\/li>\n<\/ul>\n<p>\n<b>Q.<\/b> Can we do without Superscope?<br \/>\n<b>A.<\/b> Yes, scopes can be created directly within the IPv4 address range.<br \/>\n<b>Q.<\/b> Can we do without Policy and converting VNI to hexadecimal?<br \/>\n<b>A.<\/b> Yes, the selection of the network occurs based on Option 82 Suboption 0x5,<br \/>\n<b>Q.<\/b> Can we do without Scope for Loopback addresses DHCP Source?<br \/>\n<b>A.<\/b> No, we cannot. Because in Microsoft Windows Server 2016\/2019, there is protection against malicious DHCP requests. This means that all requests from addresses not in the DHCP server pool are considered malicious.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/windows-server\/networking\/technologies\/dhcp\/dhcp-subnet-options\">DHCP Subnet Selection Options<\/a><\/noindex><\/p>\n<pre><code class=\"plaintext\"> Note  \nAll relay agent IP addresses (GIADDR) must be part of an active DHCP scope IP address range. Any GIADDR outside of the DHCP scope IP address ranges is considered a rogue relay, and the Windows DHCP Server will not acknowledge DHCP client requests from those relay agents.  \n\nA special scope can be created to \"authorize\" relay agents. Create a scope with the GIADDR (or multiple if the GIADDRs are sequential IP addresses), exclude the GIADDR address(es) from distribution, and then activate the scope. This will authorize the relay agents while preventing the GIADDR addresses from being assigned.<\/code><\/pre>\n<p>\nThat is, for setting up a DHCP pool on Microsoft Windows Server 2016\/2019 for the VXLAN BGP EVPN fabric, you only need to:<\/p>\n<ul>\n<li>Create a pool for Relay Source addresses.<\/li>\n<li>Create a pool for client networks.<\/li>\n<\/ul>\n<p>\nWhat is not necessary (but can be configured and will work, without hindering operation):<\/p>\n<ul>\n<li>Create Policies.<\/li>\n<li>Create a SuperScope.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"windows20162019dhcpexample\"><\/a><\/noindex><b class=\"spoiler_title\">Example<\/b>Example configuration of a DHCP server (there are 2 real DHCP clients \u2014 clients connected to the VXLAN fabric)<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/c3a49fb7581aa7e60b85765499fd0d49.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nExample configuration of a custom pool:<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/c4bf4f6457f6cab564a3b6c16c0e0ed6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nExample configuration of a custom pool (policies selected \u2014 to prove that policies were not used for the correct operation of the pool):<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/58dde157b1aaf61d1810b33905fa41e0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nExample configuration of a pool for Source addresses of DHCP Relay (the range of addresses for assignment completely corresponds to the exclusion from the pool of addresses):<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/ff17e07ac6e9b5531bbcadc202752d37.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<noindex><a rel=\"nofollow\" name=\"windows20162019dhcpsetup\"><\/a><\/noindex><b class=\"spoiler_title\">Configuring the DHCP service on Microsoft Windows Server 2019<\/b><\/p>\n<h4>Configuring a Pool for Loopback Addresses (source) for DHCP Relay.<\/h4>\n<p>\nCreating a new pool (Scope) in the IPv4 space.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/828cdb37e1ab759b35b73c5f7dd6ff54.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPool creation wizard. \"Next &gt;\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/6a95b404d2b8555fe4c2f7dc995d7136.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nSetting the pool name and description.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/4de21b9090e089c61014bda5a51a4b4d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDefining the range of IP addresses for Loopback and the mask for the pool.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/48ac2949da64e3c3af09bc4405907e58.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAdding exceptions. The range of exceptions must exactly match the pool range.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/08e8e5cc77234f06e98eed868bee67ec.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nLease time. \"Next &gt;\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/0b664ecaec68d98562af26b8ca7b0e81.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nRequest: Will you configure DHCP options now (DNS, WINS, Gateway, Domain) or do it later? It's quicker to answer no and then activate the pool manually. Or go to the end without filling in any information and activate the pool at the end of the wizard.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/6e7e01ee34e365c448f41a3b20078920.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfirming that options are not configured, and the pool is not activated. \"Finish\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/698fa93bf8a0fe0ade26fa10bdc6549f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nActivating the pool manually. \u2014 Select Scope and in the context menu \u2014 choose \"Activate.\" <\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/3db2846b071f7b1462263114bbad2081.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h4>Creating a pool for users\/servers.<\/h4>\n<p>\nCreating a new pool.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/8458c23bf19e02fbec43c743f518d8c5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPool creation wizard. \"Next &gt;\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/f8d1617a6562985240ec481c540a3e0d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nSetting the pool name and description.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/3be102f86f31a219722dfb86c441c62c.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDefining the range of IP addresses for Loopback and the mask for the pool.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/95961214f5cf35f1e25692e4e008eee7.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAdding exceptions. (By default, no exceptions are needed) \"Next &gt;\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/8a84a14fa2f403e5341caf7b769f68a3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nLease time. \"Next &gt;\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/36a3d8f03abe3c904a1603e7734d62e8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nRequest: Will you configure DHCP options now (DNS, WINS, Gateway, Domain) or do it later? Yes, let's configure now.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/822ecc9ef6376ead20b2a34069ef548d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nSetting the default gateway address.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/3878daaaab73e0af2d9dda3ad1cdc379.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfiguring the domain and DNS server addresses.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/4a873e8dfda51d687ddff132e5a4d3cd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nSetting the IP addresses of the WINS servers.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/85abf769a1ecb995da55375c178470d3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nActivating Scope.<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/4c1c52ee5e6aaa245f350c71e568fa28.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nThe pool is configured. \"Finish\"<\/p>\n<p><img decoding=\"async\" alt=\"Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/dce3cbed37e029d7de297f0b5c0cde40.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<noindex><a rel=\"nofollow\" name=\"finale\"><\/a><\/noindex><\/p>\n<h2>Conclusion<\/h2>\n<p>\nUsing Windows Server 2016\/2019 reduces the complexity of configuring the DHCP server for a VXLAN fabric (or any other fabric). (No special bundles are required to transfer to IT specialists: Network\/Agent Circuit ID for writing filters.)<\/p>\n<p>Will the configuration for Windows Server 2012 work on the new servers 2016\/2019 \u2013 yes, it will work.<\/p>\n<p>This document includes references to 2 versions: 7.X and 9.3. This is because version 7.0(3)I7(7) is the Cisco Suggested release, while version 9.3 is the most innovative (including support for Multicast over VXLAN Multisite).<br \/>\n<noindex><a rel=\"nofollow\" name=\"listofsources\"><\/a><\/noindex><\/p>\n<h2>List of sources<\/h2>\n<p><\/p>\n<ol>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/7-x\/vxlan\/configuration\/guide\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x\/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_7x_appendix_0110.html\">Nexus 9000 VXLAN Configuration Guide 7.x<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/93x\/vxlan\/configuration\/guide\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x\/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-93x_appendix_010111.html#id_103149\">Nexus 9000 VXLAN Configuration Guide 9.3<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/switches\/datacenter\/dfa\/configuration\/b-dfa-configuration\/segment-id-support-for-dhcp-relay.html\">DFA (Cisco Dynamic Fabric Automation)<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/en\/us\/support\/docs\/switches\/nexus-9000-series-switches\/200248-Configuring-Microsoft-Windows-Server-201.html\">Configuring Microsoft Windows Server 2012 to provide DHCP services in an eVPN Scenario (VXLAN, Cisco One Fabric, etc)<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/openspecs\/windows_protocols\/ms-dhcpm\/4b3dafe4-70e5-4085-969e-4bb402d9c68b\">3.4 DHCP Superscopes<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/previous-versions\/windows\/it-pro\/windows-server-2012-r2-and-2012\/dn425039(v%3Dws.11)\">Introduction to DHCP Policies<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/social.technet.microsoft.com\/Forums\/windowsserver\/en-US\/e093f0ea-9cee-4d65-85ce-20100038d9c7\/win2k8-r2-dhcp-problem-with-option82?forum=winserverNIS\">Win2k8 R2 DHCP problem with Option 82<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/windows-server\/networking\/technologies\/dhcp\/dhcp-subnet-options\">DHCP Subnet Selection Options<\/a><\/noindex><\/li>\n<\/ol>\n<p>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u2013 \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 DHCP \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u0434\u043b\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0438 VXLAN BGP EVPN and DFA \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c Microsoft Windows Server 2016\/2019. \u0412 \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u043e\u0439 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u0438 DHCP \u0441\u0435\u0440\u0432\u0438\u0441 \u043d\u0430 \u0431\u0430\u0437\u0435 Microsoft Windows Server 2012 \u0434\u043b\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0438 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u043a\u0430\u043a SuperScope, \u0441\u043e\u0434\u0435\u0440\u0436\u0430\u0449\u0438\u0439 \u043f\u0443\u043b Loopback (\u0432 \u0434\u0430\u043d\u043d\u043e\u043c \u043f\u0443\u043b\u0435 \u2013 \u0438\u0437\u044e\u043c\u0438\u043d\u043a\u0430 \u044d\u0442\u043e \u0438\u0441\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u0435 \u0438\u0437 \u043f\u0443\u043b\u0430 \u0432\u0441\u0435\u0445 IP \u0430\u0434\u0440\u0435\u0441\u043e\u0432 \u043f\u0443\u043b\u0430 (excluded IP [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":76226,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-76225","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u2013 \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 DHCP \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u0434\u043b\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0438 VXLAN BGP EVPN and DFA \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c Microsoft Windows Server 2016\/2019.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 Microsoft Windows Server 2016\/2019 \u0434\u043b\u044f \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f DHCP \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u0434\u043b\u044f VXLAN (DFA) | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u2013 \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 DHCP \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u0434\u043b\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0438 VXLAN BGP EVPN and DFA \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c Microsoft Windows Server 2016\/2019.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-03-31T23:42:48+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-03-31T23:42:48+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Configuring Microsoft Windows Server 2016\/2019 to provide DHCP services for VXLAN (DFA) | ProHoster","description":"The purpose of this article is to simplify the configuration of the DHCP service for the VXLAN BGP EVPN and DFA factory using Microsoft Windows Server 2016\/2019.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0430 Microsoft Windows Server 2016\/2019 \u0434\u043b\u044f \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0438\u044f DHCP \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432 \u0434\u043b\u044f VXLAN (DFA) | ProHoster","og:description":"\u041d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u2013 \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 DHCP \u0441\u0435\u0440\u0432\u0438\u0441\u0430 \u0434\u043b\u044f \u0444\u0430\u0431\u0440\u0438\u043a\u0438 VXLAN BGP EVPN and DFA \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c Microsoft Windows Server 2016\/2019.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-03-31T23:42:48+00:00","article:modified_time":"2020-03-31T23:42:48+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"76225","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:40:53","updated":"2022-10-01 00:58:51","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/76225","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=76225"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/76225\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/76226"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=76225"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=76225"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=76225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}