Kukonza Microsoft Windows Server 2016/2019 kuti ipereke ntchito za DHCP za VXLAN (DFA)
Cholinga cha nkhaniyi ndikuchepetsa kasinthidwe ka ntchito ya DHCP ya VXLAN BGP EVPN ndi nsalu ya DFA pogwiritsa ntchito Microsoft Windows Server 2016/2019.
M'zolemba zovomerezeka, ntchito ya DHCP yozikidwa pa Microsoft Windows Server 2012 pansaluyo imakonzedwa ngati SuperScope yomwe ili ndi dziwe la Loopback (chinthu chodziwika bwino cha dziwe ili ndikuchotsa ma adilesi onse a IP a dziwe kuchokera padziwe (kupatula IP adilesi = dziwe)) ndi maiwe operekera ma adilesi a IP pamanetiweki enieni (pali chowunikira - ndondomeko yakhazikitsidwa - momwe ID ya DHCP Relay Circuit ID imasefedwa ndipo ID iyi ya DHCP Relay Circuit ID ili ndi VNI ya netiweki, i.e. dziwe linanso DHCP Relay iyi. ID yozungulira idzakhala yosiyana pang'ono).
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.
Gawoli limatchula mwachidule zonse zoyambira: Malangizo okonzekera zida zapaintaneti, ma RFC omwe amagwiritsidwa ntchito m'mapaketi a DHCP m'mafakitale a eVPN, kusinthika kwa ma seva a DHCP pa Microsoft Windows Server 2012 muzolemba za Cisco zaperekedwa kuti zigwiritsidwe. Komanso chidziwitso chachidule cha Superscope ndi Policy mu ntchito ya DHCP pa Microsoft Windows Servers.
Momwe mungasinthire DHCP Relay pa VXLAN BGP EVPN, nsalu ya DFA
Kukonza DHCP Relay pa VXLAN BGP EVPN nsalu si mutu waukulu wa nkhaniyi, chifukwa ndi yosavuta. Ndimapereka maulalo ku zolembedwa ndi wowononga pa zoikamo pa zipangizo maukonde.
Chitsanzo chokhazikitsa DHCP Relay pa 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
Ma RFC omwe akugwiritsidwa ntchito poyendetsa ntchito ya DHCP Relay mu nsalu za VXLAN BGP EVPN
β’ 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.
"Dzina" la VRF momwe kasitomala amakhala amafalitsidwa.
RFC#5107: Sub-option 11(0xb) - Kuphwanya ID ya Seva
β’ 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.
Njirayi imagwiritsidwa ntchito kuwonetsetsa kuti kasitomala atumiza pempho kuti akonzenso adilesi yobwereketsa ku adilesi ya IP yomwe imagwiritsidwa ntchito posankha. (Pa Cisco VXLAN BGP, EVPN ndiye adilesi yokhazikika ya kasitomala ya Anycast.)
RFC#3527: Sub-option 5(0x5) - Kusankha Ulalo
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.
Adilesi ya netiweki yomwe kasitomala amafunikira adilesi ya IP.
Kusintha kwa zolemba za Cisco zokhudzana ndi kukonza DHCP pa Microsoft Windows Server 2012
Ndaphatikiza gawoli chifukwa pali njira yabwino kwa wogulitsa:
Nkhaniyi ikuwonetsa kuti netiweki iliyonse/VNI imafuna mtolo wake wa SuperScope ndi ma adilesi ake a Loopback:
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.
Wowonjezera Windows 2012 Zokonda pa seva pazolemba zokhazikitsa zida zamaneti. Pa maadiresi onse omwe amagwiritsidwa ntchito, SuperScope imodzi pa data center ikufunika ndipo SuperScope iyi ndi malire a malo osungiramo 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.
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 mu Microsoft Windows Server (Superscope & policy)
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.
SuperScope ndi chiyani - ndi ntchito yomwe imakupatsani mwayi wophatikiza ma adilesi angapo a IP kukhala gawo limodzi loyang'anira. Kutsatsa kwa ogwiritsa ntchito pamanetiweki omwewo (mu VLAN yomweyo) ma adilesi a IP ochokera m'madziwe angapo. Ngati pempho lidafika pamaadiresi ambiri monga gawo la SuperScope, ndiye kuti kasitomala angapatsidwe adilesi yochokera ku Scope ina yophatikizidwa mu SuperScope 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.
Ndondomeko - zimakulolani kuti mupereke ma adilesi a IP kwa ogwiritsa ntchito malinga ndi mtundu wa wogwiritsa ntchito kapena parameter. Akatswiri a Cisco amagwiritsa ntchito mfundo mu Windows Server 2012 kuti azisefa ndi VNI (Virtual Network Identifier).
Thupi lalikulu
Gawoli lili ndi zotsatira za kafukufuku, chifukwa chake sizikuthandizidwa, momwe zimagwirira ntchito (logic), zatsopano ndi momwe izi zidzatithandizire.
Chifukwa chiyani Microsoft Windows Server 2000/2003/2008 sichirikizidwa?
Microsoft Windows Server 2008 ndi mitundu yoyambirira samakonza njira 82 ndipo paketi yobwerera imatumizidwa popanda kusankha 82.
Pempho lochokera kwa kasitomala litumizidwa ku Broadcast (DHCP Discover).
Zida (Nexus) zimatumiza paketi ku seva ya DHCP (DHCP Discover + Option 82).
Seva ya DHCP imalandira paketi, kuikonza, kuitumizanso, koma popanda kusankha 82. (DHCP Kupereka - popanda kusankha 82)
Zida (Nexus) zimalandira paketi kuchokera ku seva ya DHCP. (DHCP Offer) Koma sichitumiza paketi iyi kwa wogwiritsa ntchito.
Deta ya Sniffer - pa Windows Server 2008 komanso pa kasitomala wa DHCPWindows Server 2008 ilandila pempho kuchokera ku zida zama network. (Njira 82 ilipo pamndandanda)
Windows Server 2008 imatumiza yankho ku zida zamaneti. (Chosankha 82 sichinalembedwe ngati chosankha mu phukusi)
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#
Chifukwa chiyani kasinthidwe ndizovuta mu Microsoft Windows Server 2012?
Microsoft Windows Server 2012 sikugwirabe ntchito RFC#3527 (Option 82 Sub-option 5(0x5) - Link Selection)
Koma ntchito ya Policy yakhazikitsidwa kale.
Momwe imagwirira ntchito:
Microsoft Windows Server 2012 ili ndi dziwe lapamwamba (SuperScope) lomwe lili ndi maadiresi a Loopback ndi maiwe a maukonde enieni.
Kusankhidwa kwa dziwe loperekera adilesi ya IP kugwera mu SuperScope, popeza yankho linachokera ku DHCP Relay ndi adilesi ya Loopback Source yophatikizidwa mu SuperScope.
Pogwiritsa ntchito Policy, pempholo limasankha kuchokera ku Superscope kuti membala wa membala wake VNI ili mu Option 82 Suboption 1 Agent Circuit ID. ("0108000600"+ 24 bits VNI + 24 bits zomwe sindikuzidziwa, koma wowotcherayo akuwonetsa 0 pagawoli.)
Kodi kukhazikitsidwa kumasinthidwa bwanji mu Microsoft Windows Server 2016/2019?
Microsoft Windows Server 2016 imagwiritsa ntchito RFC#3527. Ndiko kuti, Windows Server 2016 imatha kuzindikira maukonde olondola kuchokera ku Option 82 Sub-option 5(0x5) - Link Selection
Mafunso atatu amabuka nthawi yomweyo:
Kodi tingachite popanda Superscope?
Kodi tingachite popanda Policy ndikusintha VNI kukhala mawonekedwe a hexadecimal?
Kodi tingachite popanda Scope for Loopback DHCP Source adilesi?
Q. Kodi tingachite popanda Superscope? A. Inde, kuchuluka kumatha kupangidwa nthawi yomweyo m'dera la ma adilesi a IPv4. Q. Kodi tingachite popanda Policy ndikusintha VNI kukhala mawonekedwe a hexadecimal? A. Inde, kusankha kwa maukonde kumachokera ku Option 82 Suboption 0x5, Q. Kodi tingachite popanda Scope for Loopback DHCP Source adilesi? A. Ayi sitingathe. Chifukwa Microsoft Windows Server 2016/2019 ili ndi chitetezo ku zopempha zoyipa za DHCP. Ndiko kuti, zopempha zonse kuchokera ku maadiresi omwe sali mu dziwe la seva la DHCP amaonedwa kuti ndi oyipa.
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.
Iwo. Kuti mukonze dziwe la DHCP la fakitale ya VXLAN BGP EVPN pa Microsoft Windows Server 2016/2019, mumangofunika:
Kugwiritsa ntchito Windows Server 2016/2019 kumachepetsa zovuta kukhazikitsa seva ya DHCP ya nsalu ya VXLAN (kapena nsalu ina iliyonse). (Sikofunikira kusamutsa maulalo apadera kwa akatswiri a IT: ID ya Network/Agent Circuit kuti mulembetse zosefera.)
Kodi kasinthidwe ka Windows Server 2012 idzagwira ntchito pa maseva atsopano a 2016/2019 - inde idzagwira ntchito.
Chikalatachi chili ndi maumboni amitundu iwiri: 2.X ndi 7. Izi ndichifukwa choti mtundu wa 9.3(7.0)I3(7) ndiwotulutsidwa wa Cisco Suggested, ndipo mtundu 7 ndiwotsogola kwambiri (ngakhale kuthandizira Multicast kudzera pa VXLAN Multisite).