Idi ti nkan yii ni lati ṣe irọrun iṣeto ni iṣẹ DHCP fun VXLAN BGP EVPN ati aṣọ DFA ni lilo Microsoft Windows Server 2016/2019.
Ninu iwe aṣẹ osise, iṣẹ DHCP ti o da lori Microsoft Windows Server 2012 fun aṣọ naa ni tunto bi SuperScope ti o ni adagun-odo Loopback kan (aami pataki ti adagun-odo yii ni iyasoto ti gbogbo awọn adirẹsi IP ti adagun-odo lati adagun naa (iyasọtọ adiresi IP = adagun)) ati awọn adagun-odo fun ipinfunni awọn adirẹsi IP fun awọn nẹtiwọọki gidi (eyi ni afihan - eto imulo ti tunto - ninu eyiti DHCP Relay Circuit ID ti wa ni filtered ati pe ID Circuit yii DHCP ni VNI fun nẹtiwọọki, ie fun adagun omi ikudu miiran DHCP yii. ID Circuit yoo jẹ iyatọ diẹ).
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.Nkan yii ni awọn idahun si awọn ibeere wọnyi:
Awọn akoonu
-
- ( & )
-
-
Ifihan
Apakan yii ṣe atokọ ni ṣoki gbogbo data akọkọ: Awọn ilana fun atunto ẹrọ nẹtiwọọki, awọn RFC ti a lo ninu awọn apo-iwe DHCP ni awọn ile-iṣẹ eVPN, itankalẹ ti awọn eto olupin DHCP lori Microsoft Windows Server 2012 ni iwe Sisiko ti pese fun itọkasi. Bii alaye kukuru nipa Superscope ati Ilana ninu iṣẹ DHCP lori Awọn olupin Windows Microsoft.
Bii o ṣe le tunto DHCP Relay lori VXLAN BGP EVPN, aṣọ DFA
Iṣatunṣe DHCP Relay lori aṣọ VXLAN BGP EVPN kii ṣe koko akọkọ ti nkan yii, nitori pe o rọrun pupọ. Mo pese awọn ọna asopọ si iwe ati apanirun lori awọn eto lori ohun elo nẹtiwọọki.
Apẹẹrẹ ti iṣeto DHCP Relay sori Nesusi 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
Awọn RFC ti o ti ṣe imuse ni iṣẹ ti iṣẹ isọdọtun DHCP ni awọn aṣọ VXLAN BGP EVPN
RFC#6607: Aṣayan-Ipin 151(0x97) - Aṣayan Subnet Foju
• 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.“Orukọ” ti VRF ninu eyiti alabara wa ni gbigbe.
RFC # 5107: iha-aṣayan 11 (0xb) - Server ID idojuk
• 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ṣayan naa ni a lo lati rii daju pe alabara firanṣẹ ibeere kan lati tunse iyalo adirẹsi si adiresi IP ti a lo ninu aṣayan yii. (Lori Sisiko VXLAN BGP, EVPN jẹ ẹnu-ọna aiyipada ti alabara adirẹsi Anycast.)
RFC # 3527: iha-aṣayan 5 (0x5) - Asopọmọra Yiyan
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.Adirẹsi ti nẹtiwọọki lati eyiti alabara nilo adiresi IP kan.
Itankalẹ ti iwe Sisiko nipa atunto DHCP lori Microsoft Windows Server 2012
Mo ṣafikun apakan yii nitori aṣa rere kan wa ni apakan ti olutaja:
Awọn iwe nikan fihan bi o ṣe le tunto DHCP Relay lori ẹrọ nẹtiwọọki.
Nkan miiran ni a lo lati tunto DHCP lori Windows Server 2012:
Nkan yii tọkasi pe nẹtiwọọki kọọkan/VNI nilo idii SuperScope tirẹ ati ṣeto awọn adirẹsi Loopback tirẹ:
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.
Awọn eto olupin Windows 2012 ti a ṣafikun si iwe-ipamọ fun eto ohun elo nẹtiwọọki. Fun gbogbo awọn adagun-odo adirẹsi ti a lo, SuperScope kan fun ile-iṣẹ data ni a nilo ati SuperScope yii ni aala ti ile-iṣẹ 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.
Ohun gbogbo ti ṣe alaye ni ṣoki:
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 ni Microsoft Windows Server (superscope & eto imulo)
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.
Kini SuperScope - o jẹ iṣẹ ṣiṣe ti o fun ọ laaye lati ṣajọpọ awọn adagun omi pupọ ti awọn adirẹsi IP sinu ẹyọ iṣakoso kan. Lati ṣe ipolowo si awọn olumulo lori nẹtiwọọki ti ara kanna (ni VLAN kanna) awọn adirẹsi IP lati awọn adagun omi pupọ. Ti ibeere naa ba wa si adagun awọn adirẹsi gẹgẹbi apakan ti SuperScope, lẹhinna a le fun alabara ni adirẹsi lati Dopin miiran ti o wa ninu SuperScope yii.
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.
Awọn eto imulo – gba ọ laaye lati fi awọn adirẹsi IP si awọn olumulo da lori iru olumulo tabi paramita. Cisco Enginners lo imulo ni Windows Server 2012 fun àlẹmọ nipa VNI (Virtual Network idamo).
Apa akọkọ
Abala yii ni awọn abajade iwadi naa, idi ti ko ṣe atilẹyin, bawo ni o ṣe n ṣiṣẹ (logbon), kini tuntun ati bii tuntun yii yoo ṣe ran wa lọwọ.
Kini idi ti Microsoft Windows Server 2000/2003/2008 ko ṣe atilẹyin?
Microsoft Windows Server 2008 ati awọn ẹya iṣaaju ko ṣe ilana aṣayan 82 ati pe apo-pada ti firanṣẹ laisi aṣayan 82.
- Ibere lati ọdọ alabara ni a fi ranṣẹ si Broadcast (DHCP Discover).
- Ẹrọ naa (Nexus) nfi apo-iwe ranṣẹ si olupin DHCP (DHCP Discover + Aṣayan 82).
- DHCP Server gba apo-iwe naa, ṣe ilana, firanṣẹ pada, ṣugbọn laisi aṣayan 82. (Ifunni DHCP – laisi aṣayan 82)
- Ẹrọ naa (Nexus) gba apo-iwe kan lati olupin DHCP. (Ifilọ DHCP) Ṣugbọn ko firanṣẹ apo-iwe yii si olumulo ipari.
Awọn data Sniffer - lori Windows Server 2008 ati lori alabara DHCPWindows Server 2008 gba ibeere lati ẹrọ nẹtiwọki. (Aṣayan 82 wa ninu atokọ naa)
Windows Server 2008 firanṣẹ esi si ẹrọ nẹtiwọọki. (Aṣayan 82 ko ṣe atokọ bi aṣayan ninu package)
Ibere lati ọdọ alabara - Iwari DHCP wa ati pe Ifunni DHCP sonu
Awọn iṣiro lori ẹrọ nẹtiwọọki:
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#
Kini idi ti iṣeto ni idiju ni Microsoft Windows Server 2012?
Microsoft Windows Server 2012 ko tii ṣe atilẹyin RFC#3527 (Aṣayan 82 Sub-aṣayan 5(0x5) - Yiyan Ọna asopọ)
Ṣugbọn iṣẹ-ṣiṣe Ilana naa ti ni imuse tẹlẹ.
Bawo ni o ṣe n ṣiṣẹ:
- Microsoft Windows Server 2012 ni adagun nla kan (SuperScope) eyiti o ni awọn adirẹsi Loopback ati awọn adagun-odo fun awọn nẹtiwọọki gidi.
- Aṣayan adagun-odo fun ipinfunni adiresi IP kan ṣubu sinu SuperScope, niwọn igba ti idahun wa lati DHCP Relay pẹlu adirẹsi Orisun Loopback ti o wa ninu SuperScope.
- Lilo Ilana, ibeere naa yan lati Superscope ti ọmọ ẹgbẹ ti VNI wa ninu Aṣayan 82 Suboption 1 Agent Circuit ID. ("0108000600"+ 24 die-die VNI + 24 die-die ti iye wọn jẹ aimọ si mi, ṣugbọn sniffer fihan iye ti 0 ni aaye yi.)
Bawo ni iṣeto ni irọrun ni Microsoft Windows Server 2016/2019?
Microsoft Windows Server 2016 ṣe iṣẹ ṣiṣe RFC # 3527. Iyẹn ni, Windows Server 2016 le ṣe idanimọ nẹtiwọọki ti o pe lati Aṣayan 82 Sub-aṣayan 5 (0x5) - Ẹya Aṣayan Ọna asopọ
Awọn ibeere mẹta waye lẹsẹkẹsẹ:
- Njẹ a le ṣe laisi Superscope?
- Njẹ a le ṣe laisi Ilana ati yi VNI pada si fọọmu hexadecimal?
- Njẹ a le ṣe laisi Dopin fun awọn adirẹsi Orisun Loopback DHCP?
Q. Njẹ a le ṣe laisi Superscope?
A. Bẹẹni, iwọn le ṣee ṣẹda lẹsẹkẹsẹ ni agbegbe awọn adirẹsi IPv4.
Q. Njẹ a le ṣe laisi Ilana ati yi VNI pada si fọọmu hexadecimal?
A. Bẹẹni, yiyan nẹtiwọki da lori Aṣayan 82 Suboption 0x5,
Q. Njẹ a le ṣe laisi Dopin fun awọn adirẹsi Orisun Loopback DHCP?
A. Rara a ko le. Nitori Microsoft Windows Server 2016/2019 ni aabo lodi si awọn ibeere DHCP irira. Iyẹn ni, gbogbo awọn ibeere lati awọn adirẹsi ti ko si ni adagun olupin DHCP ni a ka irira.
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.Awon. Lati tunto adagun DHCP kan fun ile-iṣẹ VXLAN BGP EVPN lori Microsoft Windows Server 2016/2019, o nilo nikan:
- Ṣẹda adagun kan fun awọn adirẹsi Relay Orisun.
- Ṣẹda adagun kan fun awọn nẹtiwọki onibara
Ohun ti ko ṣe pataki (ṣugbọn o le tunto ati pe yoo ṣiṣẹ ati kii yoo dabaru pẹlu iṣẹ):
- Ṣẹda Ilana
- Ṣẹda SuperScope
Apeere:Apẹẹrẹ ti iṣeto olupin DHCP kan (awọn alabara DHCP gidi 2 wa - awọn alabara ti sopọ mọ aṣọ VXLAN)
Apẹẹrẹ ti iṣeto adagun-odo olumulo kan:
Apeere ti iṣeto adagun-odo olumulo kan (awọn ilana ti yan - lati fi mule pe awọn eto imulo ko lo fun ṣiṣe deede ti adagun-odo):
Apeere ti atunto adagun-odo kan fun awọn adirẹsi DHCP Relay Orisun (ibiti awọn adirẹsi fun ipinfunni ni kikun ni ibamu pẹlu imukuro lati adagun adirẹsi):
Ṣiṣeto iṣẹ DHCP kan lori Microsoft Windows Server 2019
Ṣiṣeto adagun-odo kan fun awọn adirẹsi Loopback (orisun) fun DHCP Relay.
A ṣẹda adagun-odo tuntun (Dopin) ni aaye IPv4.
Oluṣeto ẹda adagun. "Ntele >"
Tunto pool orukọ ati apejuwe ti awọn pool.
Ṣeto ibiti awọn adirẹsi IP fun Loopback ati iboju-boju fun adagun-odo naa.
Fifi awọn imukuro. Awọn sakani iyasoto gbọdọ pato baramu awọn pool ibiti.
Yiyalo akoko. "Ntele >"
Ibeere: Ṣe iwọ yoo tunto awọn aṣayan DHCP ni bayi (DNS, WINS, Gateway, Domain) tabi iwọ yoo ṣe nigbamii. Yoo yara lati dahun rara, ati lẹhinna mu adagun-omi ṣiṣẹ pẹlu ọwọ. Tabi lọ si opin laisi kikun alaye eyikeyi ki o mu adagun-odo ṣiṣẹ ni opin oluṣeto naa.
A jerisi pe awọn aṣayan ko ba wa ni tunto ati awọn pool ti ko ba mu ṣiṣẹ. "Pari"
A mu awọn pool pẹlu ọwọ. - Yan Dopin ati ninu akojọ aṣayan ọrọ - yan “Mu ṣiṣẹ”.
A ṣẹda adagun kan fun awọn olumulo / olupin.
A ṣẹda titun kan pool.
Oluṣeto ẹda adagun. "Ntele >"
Tunto pool orukọ ati apejuwe ti awọn pool.
Ṣeto ibiti awọn adirẹsi IP fun Loopback ati iboju-boju fun adagun-odo naa.
Fifi awọn imukuro. (Ko si awọn imukuro ti a beere nipasẹ aiyipada) "Niwaju>"
Yiyalo akoko. "Ntele >"
Ibeere: Ṣe iwọ yoo tunto awọn aṣayan DHCP ni bayi (DNS, WINS, Gateway, Domain) tabi iwọ yoo ṣe nigbamii. Jẹ ká ṣeto soke bayi.
Tunto adiresi ẹnu-ọna aiyipada.
A tunto agbegbe ati awọn adirẹsi olupin DNS.
Ṣiṣeto awọn adirẹsi IP ti awọn olupin WINS.
Imuṣiṣẹ dopin.
Awọn pool ti wa ni tunto. "Pari"
ipari
Lilo Windows Server 2016/2019 dinku idiju ti iṣeto olupin DHCP kan fun aṣọ VXLAN (tabi eyikeyi aṣọ miiran). (Ko ṣe pataki lati gbe awọn ọna asopọ pataki si awọn alamọja IT: Nẹtiwọọki / ID Circuit Aṣoju lati forukọsilẹ awọn asẹ.)
Ṣe iṣeto ni fun Windows Server 2012 ṣiṣẹ lori awọn olupin 2016/2019 tuntun - bẹẹni yoo ṣiṣẹ.
Iwe yii ni awọn itọkasi si awọn ẹya 2: 7.X ati 9.3. Eyi jẹ nitori otitọ pe ẹya 7.0 (3) I7 (7) jẹ idasilẹ Sisiko ti a daba, ati ẹya 9.3 jẹ imotuntun julọ (paapaa atilẹyin Multicast nipasẹ VXLAN Multisite).
Akojọ ti awọn orisun
orisun: www.habr.com