Tujuan tulisan ieu nyaéta pikeun nyederhanakeun konfigurasi layanan DHCP pikeun VXLAN BGP EVPN sareng DFA fabric nganggo Microsoft. Windows Server 2016 / 2019.

Dina dokuméntasi resmi, layanan DHCP dumasar kana Microsoft Windows Server 2012 kanggo pabrik dikonfigurasi salaku SuperScope, ngandung kumpulan Loopback (dina kumpulan ieu, sorotan nyaéta ngaluarkeun sadaya alamat IP tina kumpulan (alamat IP anu dikaluarkeun = kumpulan)) sareng kumpulan pikeun ngaluarkeun alamat IP pikeun jaringan nyata (sorotan di dieu nyaéta kawijakan anu dikonfigurasi, dimana ID Sirkuit Relay DHCP disaring, sareng ID Sirkuit relay DHCP ieu ngandung VNI pikeun jaringan, nyaéta pikeun kumpulan anu sanés, ID Sirkuit Relay DHCP ieu bakal rada béda).
To configure DHCP on Windows server.
1. Create a super scope. Within the super scope, create scope B, S1, S2, S3, …, Sn for the subnet B and the subnets for each segment.
2. 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).
3. For every segment scope Si, specify a policy that matches on Agent Circuit ID with value of '0108000600XXXXXX', where '0108000600' is a fixed value for all segments, the 6 numbers "XXXXXX" is the segment ID value in hexadecimal. Also ensure to check the Append wildcard(*) check box.
4. Set the policy address range to the entire range of the scope.Artikel ieu ngandung jawaban kana patarosan di handap ieu:
eusi
- ( & )
perkenalan
Bagian ieu sacara ringkes ngadaptar sadaya data sumber: Pitunjuk pikeun ngonpigurasikeun alat jaringan, RFC anu dianggo dina pakét DHCP di pabrik eVPN, pituduh rujukan pikeun évolusi setélan server DHCP dina Microsoft Windows Server 2012 dina dokumentasi Cisco. Ogé, inpormasi ringkes ngeunaan Superscope sareng Kawijakan dina layanan DHCP dina server Microsoft Windows Server.
Kumaha ngonpigurasikeun DHCP Relay dina VXLAN BGP EVPN, lawon DFA
Ngonpigurasikeun DHCP Relay dina lawon VXLAN BGP EVPN sanes topik utama artikel ieu, sabab cukup basajan. Kuring nyadiakeun Tumbu ka dokuméntasi sarta spoiler on setélan dina alat jaringan.
Conto nyetel Relay DHCP dina Nexus 9000V v9.2(3)
service dhcp
ip dhcp relay
ip dhcp relay information option
ip dhcp relay information option vpn
interface loopback10
vrf member VRF1
ip address 10.120.0.1/32 tag 1234567
interface Vlan12
no shutdown
vrf member VRF1
no ip redirects
ip address 10.120.251.1/24 tag 1234567
no ipv6 redirects
fabric forwarding mode anycast-gateway
ip dhcp relay address 10.0.0.5
ip dhcp relay source-interface loopback10
RFCs anu dilaksanakeun dina operasi layanan DHCP Relay di VXLAN BGP EVPN fabrics
RFC#6607: Sub-pilihan 151(0x97) - Pilihan Subnet Virtual
• Sub-option 151(0x97) - Virtual Subnet Selection (Defined in RFC#6607)
Used to convey VRF related information to the DHCP server in an MPLS-VPN and VXLAN EVPN multi-tenant environment."Ngaran" tina VRF dimana klien aya dikirimkeun.
RFC # 5107: Sub-pilihan 11 (0xb) - Server ID Override
• Sub-option 11(0xb) - Server ID Override (Defined in RFC#5107.)
The 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’s proprietary implementation is sub-option 152(0x98). You can use the ip dhcp relay sub-option type cisco command to manage the function.Pilihan ieu dipaké pikeun mastikeun yén klien ngirimkeun pamundut pikeun renew alamat ngajakan ka alamat IP dipaké dina pilihan ieu. (Dina Cisco VXLAN BGP, EVPN mangrupikeun alamat Anycast gateway standar klien.)
RFC # 3527: Sub-pilihan 5 (0x5) - Pamilihan Tumbu
Sub-option 5(0x5) - Link Selection (Defined in RFC#3527.)
The 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’s proprietary implementation is sub-option 150(0x96). You can use the ip dhcp relay sub-option type ciscocommand to manage the function.Alamat jaringan dimana klien peryogi alamat IP.
Évolusi dokuméntasi Cisco ngeunaan konfigurasi DHCP dina Microsoft Windows Server 2012
Kuring kalebet bagian ieu kusabab aya tren positip dina bagian anu ngajual:
Dokuméntasi ngan ukur nunjukkeun kumaha ngonpigurasikeun DHCP Relay dina alat jaringan.
Pikeun ngonpigurasikeun DHCP dina Windows Server 2012 nganggo artikel anu béda:
Tulisan ieu nunjukkeun yén unggal jaringan / VNI butuh bungkusan SuperScope sorangan sareng set alamat Loopback sorangan:
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.
Setélan anu ditambahkeun Windows 2012 Server dina dokuméntasi konfigurasi alat jaringan. Sadaya kumpulan alamat anu dianggo meryogikeun hiji SuperScope per pusat data, sareng SuperScope ieu mangrupikeun wates pusat data:
Create Superscope for all scopes you want to use for Option 82-based policies.
Note
The Superscope should combine all scopes and act as the administrative boundary.
Sadayana dijelaskeun sacara ringkes:
Let us assume the switch is using the address from subnet B (it can 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, …, Sn for segment s1, s2, s3, …, sn.
To configure DHCP on Windows server.
1. Create a super scope. Within the super scope, create scope B, S1, S2, S3, …, Sn for the subnet B and the subnets for each segment.
2. 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).
3. For every segment scope Si, specify a policy that matches on Agent Circuit ID with value of '0108000600XXXXXX', where '0108000600' is a fixed value for all segments, the 6 numbers "XXXXXX" is the segment ID value in hexadecimal. Also ensure to check the Append wildcard(*) check box.
4. Set the policy address range to the entire range of the scope.
DHCP dina Microsoft Windows Server (superscope & kawijakan)
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. Naon SuperScope - éta fungsionalitas nu ngidinan Anjeun pikeun ngagabungkeun sababaraha pools alamat IP kana hiji Unit administrasi. Pikeun Ngaiklan ka pamaké dina jaringan fisik sarua (dina VLAN sarua) alamat IP ti sababaraha pools. Upami pamundut sumping ka kolam renang alamat salaku bagian tina SuperScope, teras klien tiasa dipasihan alamat ti Wengkuan sanés anu kalebet dina SuperScope ieu.
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.
The 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. Kawijakan – ngamungkinkeun anjeun pikeun masihan alamat IP ka pangguna dumasar kana jinis atanapi parameter pangguna. Insinyur Cisco nganggo kawijakan dina Windows Server 2012 pikeun panyaringan ku VNI (Virtual Network Identifier).
utama
Bagian ieu ngandung hasil panalungtikan, naha teu didukung, kumaha gawéna (logika), naon nu anyar jeung kumaha anyar ieu bakal nulungan urang.
Naha éta henteu dirojong ku Microsoft? Windows Server 2000/2003/2008?
Microsoft Windows Server Versi 2008 sareng anu sateuacanna henteu ngolah Pilihan 82 sareng ngirim pakét pangbalikan tanpa Pilihan 82.
- Paménta ti klien dikirim ka Broadcast (DHCP Discover).
- Parabot (Nexus) ngirimkeun pakét ka server DHCP (DHCP Discover + Option 82).
- DHCP Server nampi pakét, ngolah éta, ngirimkeunana deui, tapi tanpa pilihan 82. (Tawaran DHCP - tanpa pilihan 82)
- Parabot (Nexus) narima pakét ti server DHCP. (DHCP Panawaran) Tapi teu ngirim pakét ieu ka pamaké tungtung.
Data pangintip - hurung Windows Server 2008 sareng dina klien DHCPWindows Server 2008 nampi pamundut ti alat jaringan. (Pilihan 82 aya dina daptar)

Windows Server 2008 ngirimkeun réspon ka alat jaringan. (Pilihan 82 teu aya dina daptar pilihan dina pakét.)

Paménta ti klien - DHCP Discover hadir sareng DHCP Offer leungit

Statistik alat jaringan:
NEXUS-9000V-SW-1# show ip dhcp relay statistics
----------------------------------------------------------------------
Message Type Rx Tx Drops
----------------------------------------------------------------------
Discover 8 8 0
Offer 8 8 0
Request(*) 0 0 0
Ack 0 0 0
Release(*) 0 0 0
Decline 0 0 0
Inform(*) 0 0 0
Nack 0 0 0
----------------------------------------------------------------------
Total 16 16 0
----------------------------------------------------------------------
DHCP L3 FWD:
Total Packets Received : 0
Total Packets Forwarded : 0
Total Packets Dropped : 0
Non DHCP:
Total Packets Received : 0
Total Packets Forwarded : 0
Total Packets Dropped : 0
DROP:
DHCP Relay not enabled : 0
Invalid DHCP message type : 0
Interface error : 0
Tx failure towards server : 0
Tx failure towards client : 0
Unknown output interface : 0
Unknown vrf or interface for server : 0
Max hops exceeded : 0
Option 82 validation failed : 0
Packet Malformed : 0
Relay Trusted port not configured : 0
DHCP Request dropped on MCT : 0
* - These counters will show correct value when switch
receives DHCP request packet with destination ip as broadcast
address. If request is unicast it will be HW switched
NEXUS-9000V-SW-1#
Naha Microsoft? Windows Server Naha persiapan taun 2012 sakitu héséna?
Dina Microsoft Windows Server 2012 tacan dirojong ku RFC#3527 (Pilihan 82 Sub-pilihan 5(0x5) — Pilihan Tautan)
Tapi fungsionalitas Kabijakan parantos dilaksanakeun.
Kumaha jalanna:
- Microsoft Windows Server Dina taun 2012 aya super-pool (SuperScope) anu ngandung alamat Loopback sareng pool pikeun jaringan nyata.
- Pilihan kolam renang pikeun ngaluarkeun alamat IP digolongkeun kana SuperScope, sabab résponna asalna tina DHCP Relay sareng alamat Sumber Loopback anu kalebet dina SuperScope.
- Ngagunakeun Kawijakan, pamundut milih ti Superscope yén wengkuan anggota anu VNI dikandung dina Pilihan 82 Suboption 1 Agen Circuit ID. ("0108000600" + 24 bit VNI + 24 bit anu nilaina teu dipikanyaho ku kuring, tapi sniffer nunjukkeun nilai 0 dina widang ieu.)
Kumaha Microsoft ngagampangkeun setelan Windows Server 2016 / 2019?
Dina Microsoft Windows Server Fungsi RFC#3527 2016 parantos dilaksanakeun. Éta téh Windows Server 2016 tiasa mikawanoh jaringan anu leres tina atribut Pilihan 82 Sub-pilihan 5(0x5) — Pilihan Tautan
Tilu patarosan langsung timbul:
- Naha urang tiasa ngalakukeun tanpa Superscope?
- Dupi urang ngalakukeun tanpa Sarat jeung Kaayaan sarta ngarobah VNI kana formulir hexadecimal?
- Naha urang tiasa ngalakukeun tanpa Skop pikeun alamat Sumber DHCP Loopback?
Q. Naha urang tiasa ngalakukeun tanpa Superscope?
A. Leres, ruang lingkup tiasa didamel langsung di daérah alamat IPv4.
Q. Dupi urang ngalakukeun tanpa Sarat jeung Kaayaan sarta ngarobah VNI kana formulir hexadecimal?
A. Leres, pilihan jaringan dumasar kana Pilihan 82 Suboption 0x5,
Q. Naha urang tiasa ngalakukeun tanpa Skop pikeun alamat Sumber DHCP Loopback?
A. Teu, urang teu tiasa. Kusabab di Microsoft Windows Server Ti mimiti taun 2016/2019, panyalindungan ngalawan pamundut DHCP anu jahat parantos berlaku. Ieu ngandung harti yén sadaya pamundut ti alamat anu teu aya dina kumpulan server DHCP dianggap jahat.
Note
All 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 Windows DHCP Server will not acknowledge DHCP client requests from those relay agents.
A special scope can be created to "authorize" relay agents. Create a scope with the GIADDR (or multiple if the GIADDR's 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.Éta. pikeun ngonpigurasikeun dina Microsoft Windows Server Kumpulan DHCP 2016/2019 pikeun lawon VXLAN BGP EVPN ngan ukur meryogikeun:
- Jieun kolam renang pikeun alamat Sumber Relay.
- Jieun kolam renang pikeun jaringan klien
Naon anu henteu diperyogikeun (tapi tiasa dikonpigurasi sareng éta bakal tiasa dianggo sareng moal ngaganggu padamelan):
- Jieun Kawijakan
- Jieun SuperScope
contoConto nyetel server DHCP (aya 2 klien DHCP nyata - klien disambungkeun ka lawon VXLAN)

Conto nyetel pool pamaké:

Conto netepkeun kolam renang pangguna (kabijakan dipilih - pikeun ngabuktikeun yén kawijakan henteu dianggo pikeun operasi kolam renang anu leres):

Conto ngonpigurasikeun kolam renang pikeun alamat Sumber DHCP Relay (kisaran alamat pikeun penerbitan saluyu sareng pangaluaran tina kolam renang alamat):

Nyetél layanan DHCP dina Microsoft Windows Server 2019
Ngonpigurasikeun kolam renang pikeun alamat Loopback (sumber) pikeun DHCP Relay.
Urang nyieun kolam renang anyar (wengkuan) dina spasi IPv4.

Wizard nyiptakeun kolam renang. "Salajengna >"

Ngonpigurasikeun ngaran kolam renang jeung pedaran kolam renang nu.

Setel kisaran alamat IP pikeun Loopback sareng topéng pikeun kolam renang.

Nambahan iwal. Kisaran pangaluaran kedah persis cocog sareng rentang kolam renang.

waktos nyéwa. "Salajengna >"

Patarosan: Naha anjeun bakal ngonpigurasikeun pilihan DHCP ayeuna (DNS, WINS, Gateway, Domain) atanapi anjeun badé ngalakukeun engké. Eta bakal leuwih gancang mun ngajawab euweuh, lajeng ngaktipkeun kolam renang sacara manual. Atawa buka tungtung tanpa eusian informasi wae tur aktipkeun kolam renang di tungtung wizard nu.

Kami mastikeun yén pilihan henteu ngonpigurasi sareng kolam renang henteu diaktipkeun. "Rengse"

Urang ngaktipkeun kolam renang sacara manual. — Pilih Lingkup sareng dina ménu kontéks — pilih "Aktipkeun".

Urang nyieun kolam renang pikeun pamaké / server.
Urang nyieun kolam renang anyar.

Wizard nyiptakeun kolam renang. "Salajengna >"

Ngonpigurasikeun ngaran kolam renang jeung pedaran kolam renang nu.

Setel kisaran alamat IP pikeun Loopback sareng topéng pikeun kolam renang.

Nambahan iwal. (Teu aya pengecualian anu diperyogikeun sacara standar) "Next>"

waktos nyéwa. "Salajengna >"

Patarosan: Naha anjeun bakal ngonpigurasikeun pilihan DHCP ayeuna (DNS, WINS, Gateway, Domain) atanapi anjeun badé ngalakukeun engké. Hayu urang nyetél éta ayeuna.

Konpigurasikeun alamat gateway standar.

Urang ngonpigurasikeun domain sareng alamat pangladén DNS.

Ngonpigurasikeun alamat IP tina server WINS.

aktivasina wengkuan.

kolam renang geus ngonpigurasi. "Rengse"

kacindekan
pamakean Windows Server 2016/2019 ngirangan kompleksitas ngonpigurasikeun server DHCP pikeun fabric VXLAN (atanapi fabric anu sanés). (Teu kedah ngabagi ID Sirkuit Jaringan/Agén khusus ka spesialis IT pikeun ngonpigurasikeun filter.)
Naha konfigurasina bakal tiasa dianggo pikeun Windows Server 2012 dina server 2016/2019 anyar – enya, éta bakal tiasa dianggo.
Dokumén ieu ngandung rujukan ka 2 versi: 7.X sareng 9.3. Ieu alatan kanyataan yén versi 7.0 (3) I7 (7) release Cisco Disarankeun, jeung versi 9.3 teh paling inovatif (malah ngarojong Multicast via VXLAN Multisite).
Daptar sumber
sumber: www.habr.com
