Chinangwa chechinyorwa chino ndechekurerutsa marongero eDHCP service yeVXLAN BGP EVPN neDFA fabric uchishandisa Microsoft Windows Server 2016 / 2019.
Mumagwaro epamutemo, sevhisi yeDHCP yakavakirwa paMicrosoft Windows Server Gore ra2012 refekitori rakagadzirwa seSuperScope, rine dziva reLoopback (mudziva iri, chinhu chikuru ndechekusabvisa ma IP address ese kubva mudziva (IP address = dziva)) uye madziva ekupa ma IP address emanetiweki chaiwo (chinhu chikuru pano mutemo uri kugadziriswa, umo ma DHCP Relay Circuit ID anosefetwa, uye iyi DHCP relay Circuit ID ine VNI yenetwork, kureva kuti kune rimwe dziva, iyi DHCP Relay Circuit ID ichave yakasiyana zvishoma).
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.Chinyorwa chino chine mhinduro dzemibvunzo inotevera:
Zviri mukati
- ( & )
Nhanganyaya
Chikamu chino chinotsanangura muchidimbu data rese rekwakabva: Mirayiridzo yekugadzirisa michina yenetwork, maRFC anoshandiswa mumapaketi eDHCP mumafekitori eVPN, gwara rekutarisa kushanduka kwemagadzirirwo eDHCP server paMicrosoft Windows Server 2012 muCisco documentation. Zvakare, ruzivo rupfupi nezve Superscope nePolicy muDHCP service paMicrosoft servers Windows Server.
Maitiro ekugadzirisa DHCP Relay pane VXLAN BGP EVPN, DFA jira
Kugadzirisa DHCP Relay paVXLAN BGP EVPN jira haisi iyo huru yenyaya yechinyorwa ichi, sezvo iri nyore. Ini ndinopa zvinongedzo kune zvinyorwa uye muparadzi pane zvigadziriso panetiweki michina.
Muenzaniso wekugadzirisa DHCP Relay paNexus 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 dzinoitwa mukushanda kweDHCP Relay sevhisi muVXLAN BGP EVPN machira.
RFC#6607: Sub-option 151(0x97) - Virtual Subnet Selection
• 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.Iro "zita" reVRF umo mutengi arimo rinofambiswa.
RFC#5107: Sub-sarudzo 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.Sarudzo iyi inoshandiswa kuona kuti mutengi anotumira chikumbiro chekuvandudza kero yekurojesa kune IP kero inoshandiswa mune iyi sarudzo. (PaCisco VXLAN BGP, EVPN ndiyo mutengi's default gedhi Anycast kero.)
RFC#3527: Sub-sarudzo 5(0x5) - Sarudzo Yekubatanidza
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.Kero yetiweki iyo mutengi anoda IP kero.
Kushanduka kwemagwaro eCisco maererano nekugadziriswa kweDHCP paMicrosoft Windows Server 2012
Ndakasanganisira chikamu ichi nekuti kune maitiro akanaka kune chikamu chemutengesi:
Zvinyorwa zvinongoratidza maitiro ekugadzirisa DHCP Relay pane network network.
Kugadzirisa DHCP pa Windows Server 2012 yakashandisa imwe nyaya yakasiyana:
Ichi chinyorwa chinoratidza kuti network yega yega / VNI inoda yayo SuperScope bundle uye yayo seti yeLoopback kero:
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.
Magadzirirwo akawedzerwa Windows 2012 Server mumagwaro ekugadzirisa zvishandiso zve network. Mapombi ese ekero anoshandiswa anoda SuperScope imwe chete padata center, uye iyi SuperScope ndiyo muganho wedata center:
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.
Zvese zvinotsanangurwa muchidimbu:
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 muMicrosoft Windows Server (superscope & mutemo)
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. Chii chinonzi SuperScope - ibasa rinokutendera kuti ubatanidze akati wandei madziva eIP kero kuita imwe yekutonga unit. Kushambadzira kune vashandisi pane imwecheteyo yemuviri network (muiyo imwe chete VLAN) IP kero kubva kune akati wandei madziva. Kana chikumbiro chakasvika padhamu rekero sechikamu cheSuperScope, mutengi anogona kupihwa kero kubva kune imwe Scope inosanganisirwa muSuperScope iyi.
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. Mitemo - inokutendera kuti upe vashandisi kero dze IP zvichienderana nerudzi rwemushandisi kana paramita. Mainjiniya eCisco vanoshandisa mitemo mu Windows Server 2012 yekusefa neVNI (Virtual Network Identifier).
Chikamu chikuru
Ichi chikamu chine mhedzisiro yetsvagiridzo, nei isingatsigirwe, inoshanda sei (logic), chii chitsva uye kuti chitsva ichi chichatibatsira sei.
Sei isingatsigirwe neMicrosoft? Windows Server 2000/2003/2008?
Microsoft Windows Server Shanduro dza2008 nedzapfuura hadzigadzirise Sarudzo 82 uye hadzitumire pakiti yekudzosa isina Sarudzo 82.
- Chikumbiro kubva kumutengi chinotumirwa kuBroadcast (DHCP Discover).
- Iyo midziyo (Nexus) inotumira pakiti kuDHCP server (DHCP Discover + Option 82).
- DHCP Server inogamuchira pakiti, inoigadzirisa, inoitumira zvakare, asi pasina sarudzo 82. (DHCP Offer - pasina sarudzo 82)
- Iyo midziyo (Nexus) inogamuchira pakiti kubva kuDHCP server. (DHCP Offer) Asi haitumire pakiti iyi kumushandisi wekupedzisira.
Ruzivo rweSniffer - rwakavhurwa Windows Server 2008 uye paDHCP clientWindows Server 2008 yakagamuchira chikumbiro kubva kumidziyo yenetwork. (Sarudzo 82 iripo pane rondedzero)
Windows Server 2008 inotumira mhinduro kumidziyo yenetwork. (Sarudzo 82 haisi pane runyorwa rwesarudzo dziri mupaketi.)
Chikumbiro kubva kumutengi - DHCP Discover iripo uye DHCP Offer haipo
Statistics pane network zvishandiso:
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#
Sei Microsoft? Windows Server Kugadzika kwegore ra2012 kwakaoma kudaro here?
PaMicrosoft Windows Server 2012 haisati yatsigirwa neRFC#3527 (Sarudzo 82 Sub-option 5(0x5) — Link Selection)
Asi kushanda kwePolisi kwakatoitwa.
Inoshanda sei:
- Microsoft Windows Server Muna 2012 kune super-pool (SuperScope) ine kero dzeLoopback uye mapool e network chaiyo.
- Kusarudzwa kwedziva rekuburitsa IP kero inowira muSuperScope, sezvo mhinduro yakabva kuDHCP Relay neLoopback Source kero inosanganisirwa muSuperScope.
- Uchishandisa Policy, chikumbiro chinosarudza kubva kuSuperscope iyo nhengo chiyero ine VNI iri muOption 82 Suboption 1 Agent Circuit ID. ("0108000600"+ 24 bits VNI + 24 bits ine tsika dzandisingazive, asi mufesi anoratidza kukosha kwe0 mundima iyi.)
Maitiro eMicrosoft ekugadzirisa zviri nyore Windows Server 2016 / 2019?
PaMicrosoft Windows Server 2016 RFC#3527 mashandiro akaitwa. Ndizvozvo Windows Server 2016 inogona kuona network chaiyo kubva pane attribute Option 82 Sub-option 5(0x5) — Link Selection
Mibvunzo mitatu inomuka pakarepo:
- Tinogona kuita pasina Superscope?
- Tinogona here kuita pasina Policy uye kushandura VNI kuita hexadecimal fomu?
- Tinogona here kuita pasina Scope yeLoopback DHCP Source kero?
Q. Tinogona kuita pasina Superscope?
A. Ehe, chiyero chinogona kugadzirwa nekukasira munzvimbo yeIPv4 kero.
Q. Tinogona here kuita pasina Policy uye kushandura VNI kuita hexadecimal fomu?
A. Ehe, kusarudzwa kwetiweki kwakavakirwa paSarudzo 82 Suboption 0x5,
Q. Tinogona here kuita pasina Scope yeLoopback DHCP Source kero?
A. Kwete, hatigone. Nekuti paMicrosoft Windows Server Dziviriro kubva kuzvikumbiro zveDHCP zvine hukasha yave kushanda kubvira 2016/2019. Izvi zvinoreva kuti zvikumbiro zvese zvinobva kumakero asiri mudziva reseva yeDHCP zvinoonekwa sezvine hukasha.
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.Izvo. zvekugadzirisa paMicrosoft Windows Server Dziva reDHCP ra2016/2019 rejira reVXLAN BGP EVPN rinongoda chete:
- Gadzira dziva reSource Relay kero.
- Gadzira dziva revatengi network
Izvo zvisingadiwi (asi zvinogona kugadzirwa uye zvichashanda uye hazvizokanganisa basa):
- Gadzira Policy
- Gadzira SuperScope
Muenzaniso:Muenzaniso wekumisikidza sevha yeDHCP (kune 2 chaiyo DHCP vatengi - vatengi vakabatana nejira reVXLAN)
Muenzaniso wekugadzirisa dziva revashandisi:
Muenzaniso wekumisikidza dziva remushandisi (mitemo inosarudzwa - kuratidza kuti marongero haana kushandiswa pakushanda kwakaringana kwedziva):
Muenzaniso wekugadzirisa dziva reSource DHCP Relay kero (huwandu hwemakero ekuburitswa hunoenderana nekusabviswa kubva kudhamu rekero):
Kugadzika sevhisi yeDHCP paMicrosoft Windows Server 2019
Kugadzirisa dziva reLoopback kero (mabviro) eDHCP Relay.
Isu tinogadzira dziva nyowani (Scope) munzvimbo yeIPv4.
Pool kugadzira wizard. "Inotevera >"
Gadzirisa zita redziva uye tsananguro yedziva.
Seta huwandu hwekero dzeIP dzeLoopback uye mask yedziva.
Kuwedzera kusarudzika. Kusarudzika kunofanirwa kunyatsoenderana nechikamu chepool.
Nguva yekuroja. "Inotevera >"
Mubvunzo: Uchagadzirisa sarudzo dzeDHCP izvozvi (DNS, WINS, Gateway, Domain) kana uchazviita gare gare. Zvingava kukurumidza kupindura kwete, uye ipapo activate dziva manually. Kana kuti enda kumagumo usina kuzadza chero ruzivo uye shandisa dziva pamagumo ewizard.
Isu tinosimbisa kuti sarudzo hadzina kugadzirwa uye dziva harina kuitwa. "Pedzisa"
Isu tinomutsa dziva nemaoko. -Sarudza Scope uye mune yemukati menyu - sarudza "Activate".
Isu tinogadzira dziva revashandisi / maseva.
Isu tinogadzira dziva idzva.
Pool kugadzira wizard. "Inotevera >"
Gadzirisa zita redziva uye tsananguro yedziva.
Seta huwandu hwekero dzeIP dzeLoopback uye mask yedziva.
Kuwedzera kusarudzika. (Hapana kunze kunodiwa nekusarudzika) "Inotevera >"
Nguva yekuroja. "Inotevera >"
Mubvunzo: Uchagadzirisa sarudzo dzeDHCP izvozvi (DNS, WINS, Gateway, Domain) kana uchazviita gare gare. Ngatiimise zvino.
Gadzirisa kero yegedhi yakagara iripo.
Isu tinogadzirisa iyo domain uye DNS server kero.
Kugadzirisa IP kero dzeWINS maseva.
Scope activation.
Dziva racho rakagadzirirwa. "Pedzisa"
mhedziso
Shandisa Windows Server 2016/2019 inoderedza kuoma kwekugadzirisa sevha yeDHCP yejira reVXLAN (kana chero rimwe jira). (Hapana chikonzero chekugovera maNetwork/Agent Circuit ID akakosha nenyanzvi dzeIT kuti vagadzirise mafirita.)
Ko magadzirirwo acho achashanda here Windows Server 2012 pamaseva matsva a2016/2019 - hongu, zvichashanda.
Gwaro iri rine mareferensi ezvinyorwa zviviri: 2.X uye 7. Izvi zvinokonzerwa nekuti vhezheni 9.3 (7.0) I3 (7) ndeye Cisco Yakakurudzirwa kuburitswa, uye vhezheni 7 ndiyo inonyanya kuvandudza (kunyangwe inotsigira Multicast kuburikidza neVXLAN Multisite).
Rondedzero yezvinyorwa
Source: www.habr.com
