Sepheo sa sengoloa sena ke ho nolofatsa tlhophiso ea ts'ebeletso ea DHCP bakeng sa VXLAN BGP EVPN le lesela la DFA ho sebelisa Microsoft Windows Server 2016/2019.
Litokomaneng tsa molao, tšebeletso ea DHCP e thehiloeng ho Microsoft Windows Server 2012 bakeng sa lesela e lokiselitsoe e le SuperScope e nang le letamo la Loopback (sehlahisoa sa letamo lena ke ho tlosoa ha liaterese tsohle tsa IP tsa letamo ho tloha letamong (ho sa kenyelletsoa aterese ea IP = letamo)) le matamo a ho fana ka liaterese tsa IP bakeng sa marang-rang a nnete (mona ke ntlha e hlahelletseng - pholisi e lokiselitsoe - moo DHCP Relay Circuit ID e tlhotliloeng mme ID ena ea potoloho ea DHCP e na le VNI bakeng sa marang-rang, ke hore, bakeng sa letamo le leng la DHCP Relay ID ea potoloho e tla fapana hanyane).
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.Sengoliloeng sena se na le likarabo tsa lipotso tse latelang:
Tse ka hare
-
- ( & )
-
-
Selelekela
Karolo ena e thathamisa lintlha tsohle tsa pele ka bokhutšoanyane: Litaelo tsa ho lokisa lisebelisoa tsa marang-rang, li-RFC tse sebelisoang lipaketeng tsa DHCP lifekthering tsa eVPN, phetoho ea litlhophiso tsa seva sa DHCP ho Microsoft Windows Server 2012 litokomaneng tsa Cisco li fanoe bakeng sa boitsebiso. Hape le tlhahisoleseling e khuts'oane ka Superscope le Policy ts'ebeletso ea DHCP ho Microsoft Windows Servers.
Mokhoa oa ho hlophisa DHCP Relay ho VXLAN BGP EVPN, lesela la DFA
Ho lokisa DHCP Relay holim'a lesela la VXLAN BGP EVPN ha se sehlooho sa sehlooho sena, kaha se bonolo haholo. Ke fana ka lihokelo ho litokomane le spoiler ho li-setting ho lisebelisoa tsa marang-rang.
Mohlala oa ho theha DHCP Relay ho 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
Li-RFC tse kengoang ts'ebetsong ts'ebetsong ea ts'ebeletso ea DHCP Relay ho masela a VXLAN BGP EVPN
RFC#6607: Kgetho-potlana 151(0x97) - Kgetho ya Virtual Subnet
• 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."Lebitso" la VRF leo moreki a leng ho lona le fetisoa.
RFC#5107: Kgetho-potlana 11(0xb) - Phetolelo ya 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.Khetho e sebelisetsoa ho netefatsa hore moreki o romela kopo ea ho nchafatsa aterese ea khiriso ho aterese ea IP e sebelisitsoeng khethong ena. (Ho Cisco VXLAN BGP, EVPN ke aterese ea kamehla ea k'habeche ea Anycast.)
RFC#3527: Khetho-tlase 5(0x5) - Khetho ea Khokahano
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.Aterese ea marang-rang eo moreki a hlokang aterese ea IP ho eona.
Phetoho ea litokomane tsa Cisco mabapi le ho hlophisa DHCP ho Microsoft Windows Server 2012
Ke kenyelelitse karolo ena hobane ho na le mokhoa o motle ka lehlakoreng la morekisi:
Litokomane li bontša feela mokhoa oa ho lokisa DHCP Relay ho lisebelisoa tsa marang-rang.
Sengoloa se seng se sebelisitsoe ho hlophisa DHCP ho Windows Server 2012:
Sengoliloeng sena se bontša hore marang-rang / VNI ka 'ngoe e hloka sephutheloana sa eona sa SuperScope le liaterese tsa eona tsa 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.
E kentsoe Windows 2012 Litlhophiso tsa seva ho litokomane tsa ho theha lisebelisoa tsa marang-rang. Bakeng sa matamo ohle a liaterese a sebelisitsoeng, ho hlokahala SuperScope e le 'ngoe setsing sa data 'me SuperScope ena ke moeli oa setsi sa 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.
Tsohle li hlalositsoe ka bokhutšoanyane haholo:
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 ho 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 ke eng - ke ts'ebetso e u lumellang ho kopanya li-adresse tse 'maloa tsa IP hore e be karolo e le' ngoe ea tsamaiso. Ho bapatsa ho basebelisi marang-rang a tšoanang (ka VLAN e tšoanang) liaterese tsa IP tse tsoang matamong a 'maloa. Haeba kopo e fihlile letotong la liaterese e le karolo ea SuperScope, joale moreki a ka fuoa aterese ho tsoa ho Scope e 'ngoe e kenyellelitsoeng ho SuperScope ena.
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.
Melao - e lumella hore u fane ka liaterese tsa IP ho basebelisi ho itšetlehile ka mofuta oa mosebedisi kapa parameter. Baenjiniere ba Cisco ba sebelisa maano a Windows Server 2012 ho sefa ka VNI (Virtual Network Identifier).
Karolo e kholo
Karolo ena e na le liphetho tsa lipatlisiso, hore na ke hobane'ng ha e sa tšehetsoe, e sebetsa joang (logic), ke eng e ncha le hore na e ncha e tla re thusa joang.
Hobaneng ha Microsoft Windows Server 2000/2003/2008 e sa tšehetsoe?
Microsoft Windows Server 2008 le mefuta ea pejana ha e sebetse khetho ea 82 mme pakete ea ho khutlisa e romelloa ntle le khetho ea 82.
- Kopo e tsoang ho moreki e romelloa ho Broadcast (DHCP Discover).
- Thepa (Nexus) e romela pakete ho seva sa DHCP (DHCP Discover + Option 82).
- DHCP Server e amohela pakete, e sebetsa, e khutlisa, empa ntle le khetho ea 82. (DHCP Offer - ntle le khetho ea 82)
- Thepa (Nexus) e fumana pakete ho tsoa ho seva sa DHCP. (DHCP Offer) Empa ha e romelle pakete ena ho mosebelisi oa ho qetela.
Lintlha tsa Sniffer - ho Windows Server 2008 le ho moreki oa DHCPWindows Server 2008 e fumana kopo ho tsoa lisebelisoa tsa marang-rang. (Kgetho 82 e teng lenaneng)
Windows Server 2008 e romela karabo ho lisebelisoa tsa marang-rang. (Khetho ea 82 ha e thathamisitsoe e le khetho ka har'a sephutheloana)
Kopo ho tsoa ho moreki - DHCP Discover e teng, mme tlhahiso ea DHCP ha e eo
Lipalopalo tsa lisebelisoa tsa marang-rang:
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#
Hobaneng ha tlhophiso e le thata hakaale ho Microsoft Windows Server 2012?
Microsoft Windows Server 2012 ha e so tšehetse RFC#3527 (Khetho ea 82 Sub-option 5(0x5) - Khetho ea Lihokelo)
Empa tšebetso ea Leano e se e kentsoe tšebetsong.
E sebetsa joang:
- Microsoft Windows Server 2012 e na le letamo le leholo (SuperScope) le nang le liaterese tsa Loopback le matamo a marang-rang a nnete.
- Khetho ea letamo bakeng sa ho fana ka aterese ea IP e oela ho SuperScope, kaha karabelo e tsoa ho DHCP Relay le aterese ea Loopback Source e kenyellelitsoeng ho SuperScope.
- U sebelisa Leano, kopo e khetha ho Superscope sebaka sa setho seo VNI e leng ho Option 82 Suboption 1 Agent Circuit ID. ("0108000600"+ 24 bits VNI + 24 bits eo litekanyetso tsa tsona ke sa li tsebeng, empa sniffer e bonts'a boleng ba 0 lebaleng lena.)
Ho seta ho nolofalitsoe joang ho Microsoft Windows Server 2016/2019?
Microsoft Windows Server 2016 e sebelisa tšebetso ea RFC#3527. Ke hore, Windows Server 2016 e ka lemoha marang-rang a nepahetseng ho tsoa ho Option 82 Sub-option 5(0x5) - Sebopeho sa Khetho ea Khokahano.
Ho hlaha lipotso tse tharo hang-hang:
- Na re ka etsa ntle le Superscope?
- Na re ka etsa ntle le Leano mme ra fetolela VNI ho sebopeho sa hexadecimal?
- Na re ka etsa ntle le Scope bakeng sa liaterese tsa Loopback DHCP Source?
Q. Na re ka etsa ntle le Superscope?
A. E, sebaka se ka etsoa hang-hang sebakeng sa liaterese tsa IPv4.
Q. Na re ka etsa ntle le Leano mme ra fetolela VNI ho sebopeho sa hexadecimal?
A. E, khetho ea marang-rang e thehiloe ho Option 82 Suboption 0x5,
Q. Na re ka etsa ntle le Scope bakeng sa liaterese tsa Loopback DHCP Source?
A. Che ha re khone. Hobane Microsoft Windows Server 2016/2019 e na le tšireletso khahlanong le likopo tse mpe tsa DHCP. Ke hore, likopo tsohle tse tsoang ho liaterese tse seng ka har'a letamo la seva sa DHCP li nkuoa li le kotsi.
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.Tseo. Ho lokisa letamo la DHCP bakeng sa fektheri ea VXLAN BGP EVPN ho Microsoft Windows Server 2016/2019, o hloka feela:
- Theha letamo la liaterese tsa Source Relay.
- Theha letamo bakeng sa marang-rang a bareki
Se sa hlokahaleng (empa se ka hlophisoa 'me se tla sebetsa' me se ke ke sa kena-kenana le mosebetsi):
- Etsa Leano
- Theha SuperScope
Mohlala:Mohlala oa ho theha seva sa DHCP (ho na le bareki ba 2 ba sebele ba DHCP - bareki ba hokahane le lesela la VXLAN)
Mohlala oa ho theha letamo la basebelisi:
Mohlala oa ho theha letamo la basebelisi (ho khethoa maano - ho paka hore maano ha aa sebelisoa bakeng sa ts'ebetso e nepahetseng ea letamo):
Mohlala oa ho lokisa letamo bakeng sa liaterese tsa Mohloli oa DHCP (mefuta e mengata ea liaterese bakeng sa phano e lumellana ka botlalo le ho qheleloa ka thoko ho letamo la liaterese):
Ho theha tšebeletso ea DHCP ho Microsoft Windows Server 2019
Ho lokisa letamo la liaterese tsa Loopback (mohloli) bakeng sa DHCP Relay.
Re theha letamo le lecha (Scope) sebakeng sa IPv4.
Wizard ea ho theha letamo. "E latelang >"
Hlophisa lebitso la letamo le tlhaloso ea letamo.
Beha mefuta ea liaterese tsa IP bakeng sa Loopback le mask bakeng sa letamo.
Ho eketsa mekhelo. Sebaka sa ho kenyelletsa se tlameha ho tšoana hantle le sebaka sa pool.
Nako ea ho hira. "E latelang >"
Potso: Na u tla lokisa likhetho tsa DHCP hona joale (DNS, WINS, Gateway, Domain) kapa u tla e etsa hamorao. E ka ba kapele ho araba che, ebe o kenya letamo ka letsoho. Kapa u ee qetellong ntle le ho tlatsa tlhahisoleseding leha e le efe 'me u kenye letamo qetellong ea wizard.
Re netefatsa hore likhetho ha lia hlophisoa mme letamo ha le sebetse. "Qetella"
Re kenya letamo ka letsoho. — Kgetha Scope mme ho menu ya moelelo — kgetha “Kenya tshebetsong”.
Re theha letamo bakeng sa basebelisi / li-server.
Re theha letamo le lecha.
Wizard ea ho theha letamo. "E latelang >"
Hlophisa lebitso la letamo le tlhaloso ea letamo.
Beha mefuta ea liaterese tsa IP bakeng sa Loopback le mask bakeng sa letamo.
Ho eketsa mekhelo. (Ha ho mekhelo e hlokehang ka ho sa feleng) "E latelang >"
Nako ea ho hira. "E latelang >"
Potso: Na u tla lokisa likhetho tsa DHCP hona joale (DNS, WINS, Gateway, Domain) kapa u tla e etsa hamorao. Ha re e hlophiseng jwale.
Lokisa aterese ea kamehla ea heke.
Re lokisa domain name le liaterese tsa li-server tsa DNS.
E lokisa liaterese tsa IP tsa li-server tsa WINS.
Ts'ebetso ea scope.
Letamo le lokisitsoe. "Qetella"
fihlela qeto e
Ho sebelisa Windows Server 2016/2019 ho fokotsa ho rarahana ha ho theha seva sa DHCP bakeng sa lesela la VXLAN (kapa lesela leha e le lefe). (Ha ho hlokahale ho fetisetsa lihokelo tse khethehileng ho litsebi tsa IT: ID ea Potoloho ea Network/Agent ho ngolisa litlhopa.)
Na tlhophiso ea Windows Server 2012 e tla sebetsa ho li-server tse ncha tsa 2016/2019 - ee e tla sebetsa.
Tokomane ena e na le litšupiso tsa liphetolelo tse 2: 7.X le 9.3. Sena se bakoa ke taba ea hore phetolelo ea 7.0 (3) I7 (7) ke Cisco Suggeted tokollo, 'me version 9.3 ke eona e ncha ka ho fetisisa (esita le ho tšehetsa Multicast ka VXLAN Multisite).
Lethathamo la mehloli
Source: www.habr.com