Ebumnuche nke edemede a bụ ime ka nhazi nke ọrụ DHCP dị mfe maka VXLAN BGP EVPN na akwa DFA site na iji Microsoft Windows Server 2016/2019.
N'ime akwụkwọ gọọmentị, a na-ahazi ọrụ DHCP dabere na Microsoft Windows Server 2012 maka akwa ahụ dị ka SuperScope nwere ọdọ mmiri Loopback (ihe pụtara ìhè nke ọdọ mmiri a bụ mwepụ nke adreesị IP niile nke ọdọ mmiri na ọdọ mmiri (ewepu adreesị IP =). ọdọ mmiri)) na ọdọ mmiri maka ịnye adreesị IP maka netwọkụ n'ezie (nke a bụ isi ihe - a na-ahazi amụma - nke a na-enyocha ID nke DHCP Relay na nke a DHCP relay Circuit ID nwere VNI maka netwọkụ, ya bụ maka ọdọ mmiri ọzọ DHCP Relay a. ID circuit ga-adịtụ iche).
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.Isiokwu a nwere azịza ajụjụ ndị a:
Ihe
-
- ( & )
-
-
Okwu Mmalite
Akụkụ a depụtara nkenke data mbụ niile: Ntuziaka maka ịhazi akụrụngwa netwọkụ, RFC ejiri na ngwugwu DHCP na ụlọ ọrụ eVPN, mgbanwe nke ntọala DHCP na Microsoft Windows Server 2012 na akwụkwọ Cisco ka enyere maka ntụle. Yana nkenke ozi gbasara Superscope na amụma dị na ọrụ DHCP na Microsoft Windows Servers.
Otu esi ahazi DHCP Relay na akwa VXLAN BGP EVPN, DFA
Ịhazi DHCP Relay na akwa VXLAN BGP EVPN abụghị isi isiokwu nke isiokwu a, n'ihi na ọ dị mfe. Ana m enye njikọ na akwụkwọ na onye na-emebi ihe na ntọala na akụrụngwa netwọkụ.
Ọmụmaatụ nke ịtọlite DHCP Relay na 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
RFC nke etinyere n'ọrụ nke DHCP Relay service na VXLAN BGP EVPN akwa.
RFC#6607: Nkebi nke 151(0x97) - Nhọrọ subnet mebere
• 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.A na-ebufe "aha" nke VRF nke onye ahịa nọ na ya.
RFC#5107: Nkebi-nhọrọ 11(0xb) - Nchụpụ ihe nkesa
• 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.A na-eji nhọrọ ahụ iji hụ na onye ahịa na-ezigara arịrịọ ka ọ megharịa ụlọ ọrụ mgbazinye na adreesị IP ejiri na nhọrọ a. (Na Cisco VXLAN BGP, EVPN bụ adreesị Anycast ndabara nke onye ahịa.)
RFC#3527: Nkebi nke 5 (0x5) - Nhọrọ njikọ
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.Adreesị netwọkụ nke onye ahịa chọrọ adreesị IP.
Evolution nke akwụkwọ Cisco gbasara ịhazi DHCP na Microsoft Windows Server 2012
Etinyere m ngalaba a n'ihi na enwere usoro dị mma n'akụkụ onye na-ere ahịa:
Akwụkwọ a na-egosi naanị otu esi ahazi DHCP Relay na akụrụngwa netwọkụ.
Eji edemede ọzọ hazie DHCP na Windows Server 2012:
Edemede a na-egosi na netwọk ọ bụla/VNI chọrọ ngwugwu SuperScope ya na adreesị Loopback nke ya:
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.
Agbakwunyere ntọala sava Windows 2012 na akwụkwọ maka ịtọlite akụrụngwa netwọkụ. Maka ọdọ mmiri niile ejiri, a chọrọ otu SuperScope kwa ebe data yana SuperScope a bụ oke nke etiti 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.
A kọwara ihe niile n'ụzọ dị nkenke:
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 na Microsoft Windows Server (superscope & amụma)
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.
Gịnị bụ SuperScope - ọ bụ ọrụ na-enye gị ohere ijikọta ọtụtụ ọdọ mmiri nke adreesị IP n'ime otu nhazi ngalaba. Iji kpọsaa ndị ọrụ n'otu netwọkụ anụ ahụ (na otu VLAN) adreesị IP site na ọdọ mmiri dị iche iche. Ọ bụrụ na arịrịọ ahụ bịara na ọdọ mmiri dị ka akụkụ nke SuperScope, mgbe ahụ enwere ike ịnye onye ahịa adreesị site na mpaghara ọzọ agụnyere na SuperScope a.
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.
Amụma – na-enye gị ohere ikenye ndị ọrụ adreesị IP dabere n'ụdị onye ọrụ ma ọ bụ oke. Ndị injinia Cisco na-eji atumatu na Windows Server 2012 nyocha site na VNI (Virtual Network Identifier).
Isi akụkụ
Nkebi a nwere nsonaazụ nyocha, ihe kpatara na anaghị akwado ya, ka o si arụ ọrụ (echiche), ihe dị ọhụrụ na otu ọhụrụ a ga-esi enyere anyị aka.
Kedu ihe kpatara na anaghị akwado Microsoft Windows Server 2000/2003/2008?
Microsoft Windows Server 2008 na ụdị ndị mbụ anaghị ahazi nhọrọ 82 yana ezipu ngwugwu nloghachi na-enweghị nhọrọ 82.
- A na-eziga arịrịọ sitere n'aka onye ahịa na Mgbasa ozi (DHCP Discover).
- Akụrụngwa (Nexus) na-eziga ngwugwu ahụ na sava DHCP (DHCP Discover + Nhọrọ 82).
- Ihe nkesa DHCP na-enweta ngwugwu ahụ, hazie ya, ziga ya azụ, mana enweghị nhọrọ 82. (DhCP Offer - enweghị nhọrọ 82)
- Akụrụngwa (Nexus) na-enweta ngwugwu sitere na sava DHCP. (Nnyefe DHCP) Mana ezipụghị ngwugwu a na onye ọrụ njedebe.
Data Sniffer - na Windows Server 2008 yana onye ahịa DHCPWindows Server 2008 na-enweta arịrịọ sitere na akụrụngwa netwọkụ. (Nhọrọ 82 dị na ndepụta a)
Windows Server 2008 na-eziga nzaghachi na akụrụngwa netwọkụ. (Edepụtaghị nhọrọ 82 dị ka nhọrọ na ngwugwu)
Arịrịọ sitere n'aka onye ahịa - DHCP Discover dị na onyinye DHCP na-efu
Ọnụọgụ na akụrụngwa netwọkụ:
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#
Kedu ihe kpatara nhazi ji sie ike na Microsoft Windows Server 2012?
Microsoft Windows Server 2012 anaghị akwado RFC#3527 (Nhọrọ 82 Sub-nhọrọ 5(0x5) - Nhọrọ njikọ)
Mana arụrụ ọrụ Amụma ahụ abanyelarị.
Ngwaọrụ Ngwaọrụ:
- Microsoft Windows Server 2012 nwere nnukwu ọdọ mmiri (SuperScope) nke nwere adreesị Loopback na ọdọ mmiri maka ezigbo netwọkụ.
- Nhọrọ nke ọdọ mmiri maka ịnye adreesị IP na-adaba na SuperScope, ebe nzaghachi sitere na DHCP Relay nwere adreesị Loopback Source gụnyere na SuperScope.
- N'iji amụma, arịrịọ a na-ahọrọ site na Superscope nke onye otu VNI dị na Nhọrọ 82 Suboption 1 Agent Circuit ID. ("0108000600"+ 24 bits VNI + 24 ibe n'ibe ndị ụkpụrụ ha na-amaghị m, ma sniffer na-egosi ụkpụrụ nke 0 na ubi a.)
Kedu otu esi eme ka ntọlite dị mfe na Microsoft Windows Server 2016/2019?
Microsoft Windows Server 2016 na-arụ ọrụ RFC#3527. Nke ahụ bụ, Windows Server 2016 nwere ike ịmata netwọkụ ziri ezi site na Nhọrọ 82 Nhọrọ 5 (0x5) - njirimara nhọrọ njikọ.
Ajụjụ atọ bilitere ozugbo:
- Anyị nwere ike ime na-enweghị Superscope?
- Anyị nwere ike ime na-enweghị Iwu ma tụgharịa VNI ka ọ bụrụ ụdị hexadecimal?
- Anyị nwere ike ime na-enweghị oke maka adreesị Iyi Loopback DHCP?
Q. Anyị nwere ike ime na-enweghị Superscope?
A. Ee, enwere ike ịmepụta ohere ozugbo na mpaghara adreesị IPv4.
Q. Anyị nwere ike ime na-enweghị Iwu ma tụgharịa VNI ka ọ bụrụ ụdị hexadecimal?
A. Ee, nhọrọ netwọkụ dabere na Nhọrọ 82 Subboption 0x5,
Q. Anyị nwere ike ime na-enweghị oke maka adreesị Iyi Loopback DHCP?
A. Mba anyị enweghị ike. N'ihi na Microsoft Windows Server 2016/2019 nwere nchebe megide arịrịọ DHCP ọjọọ. Ya bụ, arịrịọ niile sitere na adreesị na-adịghị na ọdọ mmiri nkesa DHCP ka a na-ewere dị ka obi ọjọọ.
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.Ndị ahụ. Iji hazie ọdọ mmiri DHCP maka ụlọ ọrụ VXLAN BGP EVPN na Microsoft Windows Server 2016/2019, naanị ị ga-achọ:
- Mepụta ọdọ mmiri maka adreesị Relay Source.
- Mepụta ọdọ mmiri maka netwọk ndị ahịa
Ihe na-adịghị mkpa (ma enwere ike ịhazi ya ma ọ ga-arụ ọrụ ma ọ gaghị egbochi ọrụ):
- Mepụta amụma
- Mepụta SuperScope
Ihe nlele:Ọmụmaatụ nke ịtọlite sava DHCP (enwere ezigbo ndị ahịa DHCP abụọ - ndị ahịa ejikọrọ na akwa VXLAN)
Ọmụmaatụ nke ịtọlite ọdọ mmiri onye ọrụ:
Ihe atụ nke ịtọlite ọdọ mmiri ndị ọrụ (a na-ahọrọ amụma - iji gosi na ejighị atumatu maka ịrụ ọrụ ọdọ mmiri ahụ nke ọma):
Ọmụmaatụ nke ịhazi ọdọ mmiri maka adreesị DHCP Relay (ụdị adreesị maka ịnye ya dabara nke ọma na mwepụ na ọdọ mmiri):
Ịtọlite ọrụ DHCP na Microsoft Windows Server 2019
Ịhazi ọdọ mmiri maka adreesị Loopback (isi iyi) maka DHCP Relay.
Anyị na-emepụta ọdọ mmiri ọhụrụ (Scope) na oghere IPV4.
Ọkachamara okike ọdọ mmiri. "Ọzọ >"
Hazie aha ọdọ mmiri na nkọwa nke ọdọ mmiri ahụ.
Tọọ ọtụtụ adreesị IP maka Loopback yana ihe mkpuchi maka ọdọ mmiri.
Na-agbakwụnye ewepu. Oke mwepu ga-adakọrịrị na oke ọdọ mmiri.
Oge mgbazinye. "Ọzọ >"
Ajụjụ: Ị ga-ahazi nhọrọ DHCP ugbu a (DNS, WINS, Gateway, Domain) ma ọ bụ ị ga-eme ya ma emechaa. Ọ ga-adị ngwa ngwa ịza mba, wee jiri aka rụọ ọdọ mmiri ahụ. Ma ọ bụ gaa na njedebe na-enweghị dejupụta ozi ọ bụla ma mee ka ọdọ mmiri dị na njedebe nke ọkachamara ahụ.
Anyị na-akwado na nhọrọ adịghị ahazi na ọdọ mmiri adịghị arụ ọrụ. "Mechaa"
Anyị na-eji aka mee ka ọdọ mmiri ahụ rụọ ọrụ. - Họrọ oke na na onodu menu - họrọ "Mee ka ọ rụọ ọrụ".
Anyị na-emepụta ọdọ mmiri maka ndị ọrụ/sava.
Anyị na-emepụta ọdọ mmiri ọhụrụ.
Ọkachamara okike ọdọ mmiri. "Ọzọ >"
Hazie aha ọdọ mmiri na nkọwa nke ọdọ mmiri ahụ.
Tọọ ọtụtụ adreesị IP maka Loopback yana ihe mkpuchi maka ọdọ mmiri.
Na-agbakwụnye ewepu. (Ọnweghị ihe ọ bụla achọrọ na ndabara) "Ọzọ>"
Oge mgbazinye. "Ọzọ >"
Ajụjụ: Ị ga-ahazi nhọrọ DHCP ugbu a (DNS, WINS, Gateway, Domain) ma ọ bụ ị ga-eme ya ma emechaa. Ka anyị guzobe ya ugbu a.
Hazie adreesị ọnụ ụzọ ámá ndabara.
Anyị na-ahazi ngalaba na adreesị sava DNS.
Na-ahazi adreesị IP nke sava WINS.
Nkwalite oke.
A haziri ọdọ mmiri ahụ. "Mechaa"
nkwubi
Iji Windows Server 2016/2019 na-ebelata mgbagwoju anya nke ịtọlite sava DHCP maka akwa VXLAN (ma ọ bụ akwa ọ bụla ọzọ). (Ọ dịghị mkpa ịnyefe njikọ pụrụ iche na ndị ọkachamara IT: Network/Agent Circuit ID iji debanye aha nzacha.)
Nhazi maka Windows Server 2012 ga-arụ ọrụ na sava 2016/2019 ọhụrụ - ee ọ ga-arụ ọrụ.
Akwụkwọ a nwere ntụnyere aka na ụdị 2: 7.X na 9.3. Nke a bụ n'ihi n'eziokwu na ụdị 7.0 (3) I7 (7) bụ ntọhapụ akwadoro Cisco, na ụdị 9.3 bụ ihe kachasị ọhụrụ (ọbụlagodi na-akwado Multicast site na VXLAN Multisite).
Ndepụta isi mmalite
isi: www.habr.com