{"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\/ro\/blog\/administrirovanie\/nastrojka-microsoft-windows-server-2016-2019-dlya-predostavleniya-dhcp-servisov-dlya-vxlan-dfa","title":{"rendered":"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Scopul acestui articol este de a simplifica configurarea serviciului DHCP pentru fabrica VXLAN BGP EVPN \u0219i DFA folosind Microsoft Windows Server 2016\/2019.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/f9380c07801612786865f7756042df07.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00cen documenta\u021bia oficial\u0103, serviciul DHCP bazat pe Microsoft Windows Server 2012 pentru fabric\u0103 este configurat ca SuperScope, care con\u021bine un interval Loopback (\u00een acest interval - specificitatea este excluderea din interval a tuturor adreselor IP din interval (excluded IP address = pool)) \u0219i intervale de alocare a adreselor IP pentru re\u021belele reale (aici specificitatea \u2013 sunt configurate politici \u2013 \u00een care se filtreaz\u0103 circuitul ID DHCP Relay, iar acest circuit ID DHCP Relay con\u021bine VNI pentru re\u021bea, adic\u0103 pentru un alt interval acest circuit ID DHCP Relay va fi pu\u021bin diferit). <\/p>\n<pre><code class=\"plaintext\">Pentru a configura DHCP pe serverul Windows. \n\n1. Crea\u021bi un superscop. \u00cen cadrul superscopului, crea\u021bi domeniul B, S1, S2, S3, \u2026, Sn pentru subnetul B \u0219i subre\u021belele pentru fiecare segment. \n2. \u00cen domeniul B, specifica\u021bi 'Intervalul de Excludere' ca fiind \u00eentreaga gam\u0103 de adrese (astfel \u00eenc\u00e2t gama de adrese oferite s\u0103 nu fac\u0103 parte din acest domeniu). \n3. Pentru fiecare domeniu de segment Si, specifica\u021bi o politic\u0103 care se potrive\u0219te cu ID-ul Circuitului Agentului av\u00e2nd valoarea '0108000600XXXXXX', unde '0108000600' este o valoare fix\u0103 pentru toate segmentele, iar cele 6 numere \"XXXXXX\" reprezint\u0103 valoarea ID-ului segmentului \u00een hexazecimal. De asemenea, asigura\u021bi-v\u0103 c\u0103 bifa\u021bi caseta de selectare pentru Append wildcard(*). \n4. Seteaz\u0103 gama de adrese a politicii la \u00eentreaga gam\u0103 a domeniului.<\/code><\/pre>\n<p>\nAcest articol con\u021bine r\u0103spunsuri la urm\u0103toarele \u00eentreb\u0103ri:<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/#WhyVXLANDHCPRelayDoNotSupportWindows2008andEarley\">De ce nu sunt acceptate Microsoft Windows Server 2000\/2003\/2008?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/#WhyWindows2012DHCPSoHardToConfigure\">De ce configurarea \u00een Microsoft Windows Server 2012 este at\u00e2t de complicat\u0103?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/494850\/#howsimplifiedsetupwindows20162019\">Cum se simplific\u0103 configurarea \u00een 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\">Cuprins<\/b><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#introduction\">Introducere<\/a><\/noindex>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#ConfigurationNexusDHCPRelay\">Cum se configureaz\u0103 DHCP Relay pe fabrica VXLAN BGP EVPN<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#RFCDHCPRelayVXLAN\">RFC-urile utilizate \u00een DHCP Relay cu fabrica VXLAN BGP EVPN<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#CiscoDocumentationEvalution\">Evolu\u021bia documenta\u021biei Cisco \u00een ceea ce prive\u0219te configurarea DHCP pe Microsoft Windows Server 2012<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#DHCPSuperScopeAndPolicy\">DHCP \u00een Microsoft Windows Server<\/a><\/noindex> (<noindex><a rel=\"nofollow\" href=\"#DHCPSuperScope\">superscope<\/a><\/noindex> &amp; <noindex><a rel=\"nofollow\" href=\"#DHCPPolicy\">policy<\/a><\/noindex>)<\/li>\n<\/ul>\n<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#Common\">Partea principal\u0103<\/a><\/noindex>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#WhyVXLANDHCPRelayDoNotSupportWindows2008andEarley\">De ce nu este acceptat Microsoft Windows Server 2000\/2003\/2008?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#WhyWindows2012DHCPSoHardToConfigure\">De ce configurarea \u00een Microsoft Windows Server 2012 este at\u00e2t de complicat\u0103?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#howsimplifiedsetupwindows20162019\">Cum se simplific\u0103 configurarea \u00een Microsoft Windows Server 2016\/2019?<\/a><\/noindex>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"#windows20162019dhcpexample\">Exemplu<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#windows20162019dhcpsetup\">Configurarea serviciului DHCP pe Microsoft Windows Server 2019<\/a><\/noindex><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#finale\">Concluzie<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"#listofsources\">Lista surselor<\/a><\/noindex><\/li>\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"introduction\"><\/a><\/noindex><\/p>\n<h2>Introducere<\/h2>\n<p>\n\u00cen aceast\u0103 sec\u021biune sunt enumerate pe scurt toate datele de baz\u0103: Instruc\u021biuni pentru configurarea echipamentelor de re\u021bea, RFC-urile utilizate \u00een pachetele DHCP \u00een fabricile eVPN, este prezentat\u0103 evolu\u021bia configura\u021biilor serverului DHCP pe Microsoft Windows Server 2012 \u00een documenta\u021bia Cisco. De asemenea, informa\u021bii scurte despre Superscope \u0219i Politica \u00een serviciul DHCP pe serverele Microsoft Windows Server.<br \/>\n<noindex><a rel=\"nofollow\" name=\"ConfigurationNexusDHCPRelay\"><\/a><\/noindex><\/p>\n<h4>Cum se configureaz\u0103 DHCP Relay pe fabrica VXLAN BGP EVPN, DFA<\/h4>\n<p>\nConfigurarea DHCP Relay pe fabrica VXLAN BGP EVPN nu este subiectul principal al acestui articol, deoarece este destul de simpl\u0103. Ofer linkuri c\u0103tre documenta\u021bie \u0219i un spoiler privind configura\u021biile pe echipamentele de re\u021bea.<\/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\">Ghid de Configurare VXLAN Nexus 9000 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\">Ghid de Configurare VXLAN Nexus 9000 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\">Exemplu de configurare DHCP Relay pe Nexus 9000V v9.2(3)<\/b><\/p>\n<pre><code class=\"plaintext\">serviciul dhcp\nip dhcp relay\nop\u021biunea de informa\u021bii ip dhcp relay\nop\u021biunea de informa\u021bii ip dhcp relay vpn\ninterfa\u021b\u0103 loopback10\n  membru vrf VRF1\n  adres\u0103 ip 10.120.0.1\/32 etichet\u0103 1234567\ninterfa\u021b\u0103 Vlan12\n  f\u0103r\u0103 oprire\n  membru vrf VRF1\n  f\u0103r\u0103 redirec\u021bion\u0103ri ip\n  adres\u0103 ip 10.120.251.1\/24 etichet\u0103 1234567\n  f\u0103r\u0103 redirec\u021bion\u0103ri ipv6\n  modul de forwarding al fabricii anycast-gateway\n  adres\u0103 ip dhcp relay 10.0.0.5\n  sursa interfe\u021bei ip dhcp relay loopback10\n<\/code><\/pre>\n<p><noindex><a rel=\"nofollow\" name=\"RFCDHCPRelayVXLAN\"><\/a><\/noindex><\/p>\n<h4>RFC-urile implementate \u00een func\u021bionarea serviciului DHCP Relay \u00een fabricile VXLAN BGP EVPN<\/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\">Lista RFC pentru 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\">Lista RFC, Nexus 9000 v7.x<\/a><\/noindex><\/li>\n<\/ul>\n<p>\n<b class=\"spoiler_title\">RFC#6607: Sub-op\u021biunea 151(0x97) \u2014 Selec\u021bia Subnetului Virtual<\/b><\/p>\n<pre><code class=\"plaintext\">\u2022\tSub-op\u021biunea 151(0x97) - Selec\u021bia Subnet virtuale (Definit\u0103 \u00een RFC#6607)\nSe folose\u0219te pentru a transmite informa\u021bii legate de VRF c\u0103tre serverul DHCP \u00eentr-un mediu multi-tenant MPLS-VPN \u0219i VXLAN EVPN.<\/code><\/pre>\n<p>\nNumele VRF \u00een care se afl\u0103 clientul este transmis.<\/p>\n<p><b class=\"spoiler_title\">RFC#5107: Sub-op\u021biunea 11(0xb) \u2014 Suprascrierea ID-ului Serverului<\/b><\/p>\n<pre><code class=\"plaintext\">\u2022\tSub-op\u021biunea 11(0xb) - Suprascrierea ID-ului serverului (Definit\u0103 \u00een RFC#5107.) \nSub-op\u021biunea de suprascriere a ID-ului serverului permite agentului de relay DHCP s\u0103 specifice o nou\u0103 valoare pentru op\u021biunea ID a serverului, care este inserat\u0103 de serverul DHCP \u00een pachetul de r\u0103spuns. Aceast\u0103 sub-op\u021biune permite agentului de relay DHCP s\u0103 ac\u021bioneze ca serverul DHCP efectiv, astfel \u00eenc\u00e2t cererile de re\u00eennoire vor veni la agentul de relay \u00een loc de serverul DHCP direct. Sub-op\u021biunea de suprascriere a ID-ului serverului con\u021bine adresa IP a interfe\u021bei de intrare, care este adresa IP a agentului de relay accesibil\u0103 din partea clientului. Folosind aceste informa\u021bii, clientul DHCP trimite toate cererile de re\u00eennoire \u0219i eliberare c\u0103tre agentul de relay. Agentul de relay adaug\u0103 toate sub-op\u021biunile corespunz\u0103toare \u0219i apoi \u00eenainteaz\u0103 cererile de re\u00eennoire \u0219i eliberare c\u0103tre serverul DHCP original. Pentru aceast\u0103 func\u021bie, implementarea proprietar\u0103 a Cisco este sub-op\u021biunea 152(0x98). Pute\u021bi folosi comanda ip dhcp relay sub-option type cisco pentru a gestiona func\u021bia.<\/code><\/pre>\n<p>\nOp\u021biunea este folosit\u0103 pentru ca clientul s\u0103 trimit\u0103 o cerere de re\u00eennoire a \u00eenchirierii adreselor pe adresa IP utilizat\u0103 \u00een aceast\u0103 op\u021biune. (\u00cen Cisco VXLAN BGP EVPN \u2013 aceasta este adresa Anycast a gateway-ului implicit pentru client.)<\/p>\n<p><b class=\"spoiler_title\">RFC#3527: Sub-op\u021biunea 5(0x5) \u2014 Selec\u021bia Leg\u0103turii<\/b><\/p>\n<pre><code class=\"plaintext\">Sub-op\u021biunea 5(0x5) - Selec\u021bia Link-ului (Definit\u0103 \u00een RFC#3527.) \n\nSub-op\u021biunea de selec\u021bie a link-ului ofer\u0103 un mecanism pentru a separa subnet-ul\/link-ul pe care se afl\u0103 clientul DHCP de adresa gateway (giaddr), care poate fi utilizat\u0103 pentru a comunica cu agentul de relay de c\u0103tre serverul DHCP. Agentul de relay va seta sub-op\u021biunea la subnet-ul corect al beneficiarului, iar serverul DHCP va folosi acea valoare pentru a aloca o adres\u0103 IP \u00een loc de valoarea giaddr. Agentul de relay va seta giaddr la propria adres\u0103 IP astfel \u00eenc\u00e2t mesajele DHCP s\u0103 poat\u0103 fi transmise peste re\u021bea. Pentru aceast\u0103 func\u021bie, implementarea proprietar\u0103 a Cisco este sub-op\u021biunea 150(0x96). Pute\u021bi folosi comanda ip dhcp relay sub-option type cisco pentru a gestiona func\u021bia.<\/code><\/pre>\n<p>\nAdresa re\u021belei din care clientul necesit\u0103 o adres\u0103 IP.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"CiscoDocumentationEvalution\"><\/a><\/noindex><\/p>\n<h4>Evolu\u021bia documenta\u021biei Cisco \u00een ceea ce prive\u0219te configurarea DHCP pe Microsoft Windows Server 2012<br \/>\n<\/h4>\n<p>\nAm inclus aceast\u0103 sec\u021biune deoarece se observ\u0103 o tendin\u021b\u0103 pozitiv\u0103 din partea furnizorului:<\/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\">Ghid de Configurare Nexus 9000 VXLAN 7.3<\/a><\/noindex> <\/p>\n<p>Documenta\u021bia prezint\u0103 doar configurarea DHCP Relay pe echipamentele de re\u021bea.<\/p>\n<p>O alt\u0103 articol\u0103 a fost folosit\u0103 pentru configurarea DHCP pe 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\">Configurarea Microsoft Windows Server 2012 pentru a oferi servicii DHCP \u00eentr-un scenariu eVPN (VXLAN, Cisco One Fabric, etc)<\/a><\/noindex><\/p>\n<p>Acest articol precizeaz\u0103 c\u0103 pentru fiecare re\u021bea\/VNI este necesar un SuperScope propriu \u0219i un set de adrese Loopback proprii:<\/p>\n<pre><code class=\"plaintext\">Dac\u0103 sunt necesare mai multe Scopuri DHCP pentru subre\u021bele multiple, trebuie s\u0103 crea\u021bi un LoopbackX pentru fiecare subre\u021bea\/vlan pe toate LEAFS \u0219i s\u0103 crea\u021bi un superscope cu un interval loopbackX \u0219i un interval de subre\u021bea IP client efectiv pentru fiecare 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\">Ghid de Configurare VXLAN Nexus 9000 9.3<\/a><\/noindex><\/p>\n<p>Am ad\u0103ugat set\u0103rile pentru Windows 2012 Server \u00een documenta\u021bia de configurare a echipamentului de re\u021bea. Pentru toate re\u021belele de adrese utilizate este necesar un singur SuperScope \u00een Data Center, iar acest SuperScope reprezint\u0103 limita Data Center-ului:<\/p>\n<pre><code class=\"plaintext\">Creeaz\u0103 un Superscope pentru toate scopurile pe care dori\u021bi s\u0103 le utiliza\u021bi pentru politicile bazate pe Op\u021biunea 82. Not\u0103: Superscope-ul ar trebui s\u0103 combine toate scopurile \u0219i s\u0103 ac\u021bioneze ca o limit\u0103 administrativ\u0103.<\/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>Foarte concis se vorbe\u0219te despre tot:<\/p>\n<pre><code class=\"plaintext\">S\u0103 presupunem c\u0103 switch-ul folose\u0219te adresa din subnetul B (poate fi subnetul de backbone, subnetul de management sau orice subnet desemnat de client \u00een acest scop) pentru a comunica cu serverul DHCP Windows. \u00cen DFA avem subre\u021bele S1, S2, S3, \u2026, Sn pentru segmentele s1, s2, s3, \u2026, sn. \n\nPentru a configura DHCP pe serverul Windows. \n\n1. Crea\u021bi un superscop. \u00cen cadrul superscopului, crea\u021bi domeniul B, S1, S2, S3, \u2026, Sn pentru subnetul B \u0219i subre\u021belele pentru fiecare segment. \n2. \u00cen domeniul B, specifica\u021bi 'Intervalul de Excludere' ca fiind \u00eentreaga gam\u0103 de adrese (astfel \u00eenc\u00e2t gama de adrese oferite s\u0103 nu fac\u0103 parte din acest domeniu). \n3. Pentru fiecare domeniu de segment Si, specifica\u021bi o politic\u0103 care se potrive\u0219te cu ID-ul Circuitului Agentului av\u00e2nd valoarea '0108000600XXXXXX', unde '0108000600' este o valoare fix\u0103 pentru toate segmentele, iar cele 6 numere \"XXXXXX\" reprezint\u0103 valoarea ID-ului segmentului \u00een hexazecimal. De asemenea, asigura\u021bi-v\u0103 c\u0103 bifa\u021bi caseta de selectare pentru Append wildcard(*). \n4. Seteaz\u0103 gama de adrese a politicii la \u00eentreaga gam\u0103 a domeniului.\n<\/code><\/pre>\n<p>\n<noindex><a rel=\"nofollow\" name=\"DHCPSuperScopeAndPolicy\"><\/a><\/noindex><\/p>\n<h4>DHCP \u00een Microsoft Windows Server (superscope &amp; politic\u0103)<\/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-ul este o caracteristic\u0103 administrativ\u0103 a unui server DHCP care poate fi utilizat\u0103 pentru a grupa mai multe scopuri ca o singur\u0103 entitate administrativ\u0103. Superscope permite unui server DHCP s\u0103 ofere chirii din mai multe scopuri c\u0103tre clien\u021bi pe o singur\u0103 re\u021bea fizic\u0103. Scopurile ad\u0103ugate \u00eentr-un superscope se numesc scopuri membre.<\/code><\/pre>\n<p>\nCe este SuperScope \u2013 este o func\u021bionalitate care permite combinarea mai multor grupuri de adrese IP \u00eentr-o singur\u0103 unitate administrativ\u0103. Scopul este de a anun\u021ba utilizatorilor dintr-o singur\u0103 re\u021bea fizic\u0103 (\u00een acela\u0219i VLAN) adrese IP din mai multe grupuri. Dac\u0103 o solicitare a venit la un grup de adrese parte din SuperScope, atunci este posibil s\u0103 se emit\u0103 clientului o adres\u0103 dintr-un alt Scope ce face parte din acest 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)\">Politica<\/a><\/noindex><\/h4>\n<p><\/p>\n<pre><code class=\"plaintext\">Rolul serverului DHCP \u00een Windows Server 2012 introduce o nou\u0103 caracteristic\u0103 care v\u0103 permite s\u0103 crea\u021bi politici IPv4 ce specific\u0103 atribuiri personalizate de adrese IP \u0219i op\u021biuni pentru clien\u021bii DHCP pe baza unui set de condi\u021bii. \n\nFunc\u021bia de atribuire bazat\u0103 pe politic\u0103 (PBA) permite gruparea clien\u021bilor DHCP dup\u0103 atribute specifice bazate pe c\u00e2mpuri con\u021binute \u00een pachetul de solicitare al clientului DHCP. PBA permite o administrare \u021bintit\u0103 \u0219i un control mai mare asupra parametrilor de configurare livra\u021bi dispozitivelor de re\u021bea cu DHCP.<\/code><\/pre>\n<p>\nPoliticile \u2013 permit atribuirea adreselor IP utilizatorilor \u00een func\u021bie de tipul de utilizator sau parametru. Inginerii Cisco folosesc politicile \u00een Windows Server 2012 pentru filtrarea dup\u0103 VNI (Identificatorul de re\u021bea virtual). <br \/>\n<noindex><a rel=\"nofollow\" name=\"Common\"><\/a><\/noindex><\/p>\n<h2>Partea principal\u0103<\/h2>\n<p>\nAceast\u0103 sec\u021biune prezint\u0103 rezultatele cercet\u0103rilor asupra motivelor pentru care nu este acceptat, cum func\u021bioneaz\u0103 (logica), ce este nou \u0219i cum ne va ajuta aceast\u0103 noutate.<br \/>\n<noindex><a rel=\"nofollow\" name=\"WhyVXLANDHCPRelayDoNotSupportWindows2008andEarley\"><\/a><\/noindex><\/p>\n<h4>De ce nu este acceptat Microsoft Windows Server 2000\/2003\/2008?<\/h4>\n<p>\nMicrosoft Windows Server 2008 \u0219i versiunile anterioare nu proceseaz\u0103 op\u021biunea 82 (Option 82) \u0219i returneaz\u0103 pachetul f\u0103r\u0103 op\u021biunea 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\">Problema DHCP pe Win2k8 R2 cu Option82<\/a><\/noindex><\/p>\n<ol>\n<li>Cererea de la client este trimis\u0103 prin Broadcast (DHCP Discover).<\/li>\n<li>Echipamentul (Nexus) trimite pachetul c\u0103tre serverul DHCP (DHCP Discover + Option 82).<\/li>\n<li>Serverul DHCP prime\u0219te pachetul, \u00eel proceseaz\u0103 \u0219i trimite un r\u0103spuns \u00eenapoi, dar f\u0103r\u0103 op\u021biunea 82. (DHCP Offer \u2013 f\u0103r\u0103 op\u021biunea 82)<\/li>\n<li>Echipamentul (Nexus) prime\u0219te pachetul de la serverul DHCP. (DHCP Offer) Dar nu trimite acest pachet utilizatorului final.<\/li>\n<\/ol>\n<p>\n<b class=\"spoiler_title\">Datele snifferului \u2014 pe Windows Server 2008 \u0219i pe clientul DHCP<\/b>Windows Server 2008 prime\u0219te cererea de la echipamentul de re\u021bea. (Op\u021biunea 82 este prezent\u0103 \u00een list\u0103)<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/267332ca80f1f1a2522307d791074644.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nWindows Server 2008 trimite r\u0103spunsul c\u0103tre echipamentul de re\u021bea. (Op\u021biunea 82 nu este prezent\u0103 \u00een lista op\u021biunilor din pachet)<br \/>\n<img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/dea552f68344f7c1c4e7904c67859e40.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nCererea de la client \u2013 prezen\u021ba DHCP Discover \u0219i absen\u021ba DHCP Offer<br \/>\n<img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/611e7c61971d92813fad5e85541c1926.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nStatistici pe echipamentul de re\u021bea:<\/p>\n<pre><code class=\"plaintext\">NEXUS-9000V-SW-1# show ip dhcp relay statistics \n----------------------------------------------------------------------\nTip mesaj             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 pachete primite                           :         0\nTotal pachete forwardate                        :         0\nTotal pachete eliminate                          :         0\nNon DHCP:\nTotal pachete primite                           :         0\nTotal pachete forwardate                        :         0\nTotal pachete eliminate                          :         0\nDROP:\nDHCP Relay nu este activat                      :         0\nTip mesaj DHCP invalid                          :         0\nEroare de interfa\u021b\u0103                              :         0\nE\u0219ec la trimiterea c\u0103tre server                  :         0\nE\u0219ec la trimiterea c\u0103tre client                  :         0\nInterfa\u021b\u0103 de ie\u0219ire necunoscut\u0103                 :         0\nvrf sau interfa\u021b\u0103 necunoscut\u0103 pentru server      :         0\nNum\u0103rul maxim de hop-uri dep\u0103\u0219it                 :         0\nValidarea op\u021biunii 82 a e\u0219uat                   :         0\nPachet malformat                                 :         0\nPortul de \u00eencredere al relay-ului DHCP nu este configurat :         0\nCererea DHCP eliminat\u0103 pe MCT                    :         0\n*  -  Aceste contoare vor ar\u0103ta valoarea corect\u0103 c\u00e2nd switch-ul \nprime\u0219te pachetul cererii DHCP cu IP-ul de destina\u021bie ca adres\u0103 broadcast.\nDac\u0103 cererea este unicast, va fi comutat\u0103 la HW\nNEXUS-9000V-SW-1#<\/code><\/pre>\n<p>\n<noindex><a rel=\"nofollow\" name=\"WhyWindows2012DHCPSoHardToConfigure\"><\/a><\/noindex><\/p>\n<h4>De ce configurarea \u00een Microsoft Windows Server 2012 este at\u00e2t de complicat\u0103?<\/h4>\n<p>\n\u00cen Microsoft Windows Server 2012 \u00eenc\u0103 nu este suportat RFC#3527 (Op\u021biunea 82 Sub-op\u021biunea 5(0x5) \u2014 Selec\u021bia link-ului)<br \/>\nDar func\u021bionalitatea Policy este deja implementat\u0103.<\/p>\n<p>Cum func\u021bioneaz\u0103:<\/p>\n<ul>\n<li>Microsoft Windows Server 2012 are un super-pool (SuperScope) \u00een care se afl\u0103 adrese Loopback \u0219i pool-uri pentru re\u021bele reale.<\/li>\n<li>Selec\u021bia pool-ului pentru emiterea adresei IP cade \u00een SuperScope, deoarece r\u0103spunsul a venit de la DHCP Relay cu adresa surs\u0103 Loopback, care face parte din SuperScope.<\/li>\n<li>Folosind Policy, cererea selecteaz\u0103 din Superscope acel member scope, al c\u0103rui VNI se reg\u0103se\u0219te \u00een Op\u021biunea 82 Sub-op\u021biunea 1 Agent Circuit ID. (\u201c0108000600\u201d+ 24 de bi\u021bi VNI + 24 de bi\u021bi al c\u0103ror valori nu sunt cunoscute, dar snifferul arat\u0103 valori 0 \u00een acest c\u00e2mp.)<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"howsimplifiedsetupwindows20162019\"><\/a><\/noindex><\/p>\n<h4>Cum se simplific\u0103 configurarea \u00een Microsoft Windows Server 2016\/2019?<\/h4>\n<p>\n\u00cen Microsoft Windows Server 2016 este implementat\u0103 func\u021bionalitatea RFC#3527. Adic\u0103, Windows Server 2016 poate recunoa\u0219te re\u021beaua corect\u0103 din atributul Op\u021biunea 82 Sub-op\u021biunea 5(0x5) \u2014 Selec\u021bia link-ului. <\/p>\n<p>Se nasc imediat 3 \u00eentreb\u0103ri:<\/p>\n<ul>\n<li>Putem s\u0103 ne descurc\u0103m f\u0103r\u0103 Superscope?<\/li>\n<li>Putem s\u0103 ne descurc\u0103m f\u0103r\u0103 Policy \u0219i conversia VNI \u00een form\u0103 hexazecimal\u0103?<\/li>\n<li>Putem s\u0103 ne descurc\u0103m f\u0103r\u0103 Scope pentru adresele Loopback DHCP Source?<\/li>\n<\/ul>\n<p>\n<b>\u00centrebare.<\/b> Putem s\u0103 ne descurc\u0103m f\u0103r\u0103 Superscope?<br \/>\n<b>R\u0103spuns.<\/b> Da, scope-uri pot fi create imediat \u00een domeniul adreselor IPv4.<br \/>\n<b>\u00centrebare.<\/b> Putem s\u0103 ne descurc\u0103m f\u0103r\u0103 Policy \u0219i conversia VNI \u00een form\u0103 hexazecimal\u0103?<br \/>\n<b>R\u0103spuns.<\/b> Da, selec\u021bia re\u021belei se face pe baza Op\u021biunii 82 Sub-op\u021biunea 0x5,<br \/>\n<b>\u00centrebare.<\/b> Putem s\u0103 ne descurc\u0103m f\u0103r\u0103 Scope pentru adresele Loopback DHCP Source?<br \/>\n<b>R\u0103spuns.<\/b> Nu, nu putem. Deoarece \u00een Microsoft Windows Server 2016\/2019 exist\u0103 protec\u021bie \u00eempotriva solicit\u0103rilor DHCP mali\u021bioase. Adic\u0103 toate cererile din adrese care nu sunt \u00een pool-ul serverului DHCP sunt considerate mali\u021bioase.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/windows-server\/networking\/technologies\/dhcp\/dhcp-subnet-options\">Op\u021biuni de Selec\u021bie Subnet DHCP<\/a><\/noindex><\/p>\n<pre><code class=\"plaintext\"> Not\u0103\nToate adresele IP ale agentului de retransmisie (GIADDR) trebuie s\u0103 fac\u0103 parte dintr-o gam\u0103 activ\u0103 de adrese IP ale domeniului DHCP. Orice GIADDR \u00een afara celor din domeniile IP ale DHCP este considerat un agent de retransmisie nedorit \u0219i serverul DHCP Windows nu va recunoa\u0219te solicit\u0103rile clien\u021bilor DHCP din partea acelor agen\u021bi de retransmisie.\n\nSe poate crea un domeniu special pentru a \"autorizare\" agen\u021bii de retransmisie. Crea\u021bi un domeniu cu GIADDR (sau multiple, dac\u0103 GIADDR-urile sunt adrese IP secven\u021biale), exclude\u021bi adresa GIADDR din distribu\u021bie \u0219i apoi activa\u021bi domeniul. Aceasta va autoriza agen\u021bii de retransmisie, prevenind \u00een acela\u0219i timp asignarea adreselor GIADDR.<\/code><\/pre>\n<p>\nAdic\u0103, pentru configurarea unui pool DHCP pe Microsoft Windows Server 2016\/2019 pentru fabrica VXLAN BGP EVPN este necesar doar:<\/p>\n<ul>\n<li>Crearea unui pool pentru adresele surs\u0103 Relay.<\/li>\n<li>Crearea unui pool pentru re\u021belele clientului.<\/li>\n<\/ul>\n<p>\nCe nu este necesar (dar se poate configura \u0219i va func\u021biona, f\u0103r\u0103 a deranja func\u021bionarea):<\/p>\n<ul>\n<li>Crearea Policy-ului.<\/li>\n<li>Crearea Superscope-ului.<\/li>\n<\/ul>\n<p>\n<noindex><a rel=\"nofollow\" name=\"windows20162019dhcpexample\"><\/a><\/noindex><b class=\"spoiler_title\">Exemplu<\/b>Exemplu de configurare a serverului DHCP (sunt prezen\u021bi 2 clien\u021bi DHCP reali \u2014 clien\u021bii sunt conecta\u021bi la fabrica VXLAN).<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/c3a49fb7581aa7e60b85765499fd0d49.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nExemplu de configurare a unui pool personalizat:<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/c4bf4f6457f6cab564a3b6c16c0e0ed6.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nExemplu de configurare a unui pool personalizat (sunt selectate politicile \u2014 pentru a demonstra c\u0103 politicile nu au fost utilizate pentru func\u021bionarea corect\u0103 a pool-ului):<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/58dde157b1aaf61d1810b33905fa41e0.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nExemplu de configurare a unui pool pentru adresele surs\u0103 DHCP Relay (intervalul de adrese pentru emitere corespunde complet excluderii din pool-ul adreselor):<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru 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\">Configurarea serviciului DHCP pe Microsoft Windows Server 2019<\/b><\/p>\n<h4>Configurarea pool-ului pentru adresele Loopback (source) pentru DHCP Relay.<\/h4>\n<p>\nCream un nou pool (Scope) \u00een spa\u021biul IPv4.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/828cdb37e1ab759b35b73c5f7dd6ff54.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nMaestrul de creare a pool-ului. \u201eUrm\u0103torul &gt;\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/6a95b404d2b8555fe4c2f7dc995d7136.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfigur\u0103m numele pool-ului \u0219i descrierea (Description) pool-ului.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/4de21b9090e089c61014bda5a51a4b4d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDefinim intervalul de adrese IP pentru Loopback \u0219i masca pentru pool.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/48ac2949da64e3c3af09bc4405907e58.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAd\u0103ug\u0103m excep\u021bii. Intervalul excep\u021biilor trebuie s\u0103 corespund\u0103 perfect intervalului pool-ului.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/08e8e5cc77234f06e98eed868bee67ec.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nTimpul de \u00eenchiriere. \u201eUrm\u0103torul &gt;\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/0b664ecaec68d98562af26b8ca7b0e81.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00centrebare: Ve\u021bi configura op\u021biunile DHCP acum (DNS, WINS, Gateway, Domain) sau le ve\u021bi face mai t\u00e2rziu? Va fi mai rapid s\u0103 r\u0103spunde\u021bi nu \u0219i s\u0103 activa\u021bi pool-ul manual. Sau pute\u021bi trece p\u00e2n\u0103 la final f\u0103r\u0103 a completa vreo informa\u021bie \u0219i la finalul wizard-ului s\u0103 activa\u021bi pool-ul.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/6e7e01ee34e365c448f41a3b20078920.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfirm\u0103m c\u0103 op\u021biunile nu sunt configurate, pool-ul nu este activat. \u201eFinalizare\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/698fa93bf8a0fe0ade26fa10bdc6549f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nActiv\u0103m pool-ul manual. \u2014 Select\u0103m Scope \u0219i din meniul contextual \u2014 alegem \u201eActiveaz\u0103\u201d. <\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/3db2846b071f7b1462263114bbad2081.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h4>Cre\u0103m un pool pentru utilizatori\/servere.<\/h4>\n<p>\nCream un nou pool.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/8458c23bf19e02fbec43c743f518d8c5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nMaestrul de creare a pool-ului. \u201eUrm\u0103torul &gt;\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/f8d1617a6562985240ec481c540a3e0d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfigur\u0103m numele pool-ului \u0219i descrierea (Description) pool-ului.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/3be102f86f31a219722dfb86c441c62c.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDefinim intervalul de adrese IP pentru Loopback \u0219i masca pentru pool.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/95961214f5cf35f1e25692e4e008eee7.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAd\u0103ug\u0103m excep\u021bii. (Implicit, excep\u021biile nu sunt necesare) \u201eUrm\u0103torul &gt;\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/8a84a14fa2f403e5341caf7b769f68a3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nTimpul de \u00eenchiriere. \u201eUrm\u0103torul &gt;\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/36a3d8f03abe3c904a1603e7734d62e8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00centrebare: Ve\u021bi configura op\u021biunile DHCP acum (DNS, WINS, Gateway, Domain) sau le ve\u021bi face mai t\u00e2rziu? Da, le configur\u0103m acum.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/822ecc9ef6376ead20b2a34069ef548d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfigur\u0103m adresa gateway-ului implicit.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/3878daaaab73e0af2d9dda3ad1cdc379.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfigur\u0103m domeniul \u0219i adresele serverelor DNS.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/4a873e8dfda51d687ddff132e5a4d3cd.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nConfigur\u0103m adresele IP ale serverelor WINS.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/85abf769a1ecb995da55375c178470d3.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nActivarea Scope-ului.<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA)\" src=\"\/wp-content\/uploads\/2020\/03\/4c1c52ee5e6aaa245f350c71e568fa28.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPool-ul este configurat. \u201eFinalizare\u201d<\/p>\n<p><img decoding=\"async\" alt=\"Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru 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>Concluzie<\/h2>\n<p>\nUtilizarea Windows Server 2016\/2019 reduce complexitatea configur\u0103rii serverului DHCP pentru fabrici VXLAN (sau orice alt\u0103 fabric\u0103). (Nu este necesar\u0103 transmiterea unor pachete speciale c\u0103tre speciali\u0219tii IT: Network\/Agent Circuit ID pentru scrierea filtrelor.)<\/p>\n<p>Va func\u021biona configura\u021bia pentru Windows Server 2012 pe noile servere 2016\/2019 \u2013 da, va func\u021biona.<\/p>\n<p>\u00cen acest document sunt prezentate link-uri c\u0103tre 2 versiuni: 7.X \u0219i 9.3. Acest lucru se datoreaz\u0103 faptului c\u0103 versiunea 7.0(3)I7(7) \u2014 este versiunea sugerat\u0103 de Cisco, iar versiunea 9.3 \u2014 este cea mai inovatoare (inclusiv suport pentru Multicast prin VXLAN Multisite).<br \/>\n<noindex><a rel=\"nofollow\" name=\"listofsources\"><\/a><\/noindex><\/p>\n<h2>Lista surselor<\/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\">Ghid de Configurare VXLAN pentru Nexus 9000 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\">Ghid de Configurare VXLAN Nexus 9000 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\">Configurarea Microsoft Windows Server 2012 pentru a oferi servicii DHCP \u00eentr-un scenariu eVPN (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 Superscopes DHCP<\/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)\">Introducere \u00een politicile DHCP<\/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\">Problema DHCP pe Win2k8 R2 cu Option82<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.microsoft.com\/en-us\/windows-server\/networking\/technologies\/dhcp\/dhcp-subnet-options\">Op\u021biuni de Selec\u021bie Subnet DHCP<\/a><\/noindex><\/li>\n<\/ol>\n<p>Sursa: <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.1 - 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\/ro\/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.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/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\udd47Configurarea Microsoft Windows Server 2016\/2019 pentru furnizarea de servicii DHCP pentru VXLAN (DFA) | ProHoster","description":"Scopul acestui articol este de a simplifica configurarea serviciului DHCP pentru fabrica VXLAN BGP EVPN \u0219i DFA folosind Microsoft Windows Server 2016\/2019.","canonical_url":"https:\/\/prohoster.info\/ro\/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":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/76225","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=76225"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/76225\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/76226"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=76225"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=76225"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=76225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}