ʻO ke kumu o kēia ʻatikala e maʻalahi i ka hoʻonohonoho ʻana o ka lawelawe DHCP no VXLAN BGP EVPN a me ka lole DFA me ka hoʻohana ʻana iā Microsoft Windows Server 2016/2019.
Ma ka palapala mana, ua hoʻonohonoho ʻia ka lawelawe DHCP e pili ana i ka Microsoft Windows Server 2012 no ka lole ma ke ʻano he SuperScope i loaʻa kahi wai Loopback (ʻo ka mea koʻikoʻi o kēia ʻauʻau ke kāpae ʻana i nā helu IP āpau o ka loko wai mai ka wai (waiho IP address = pool)) a me nā loko no ka hoʻopuka ʻana i nā helu IP no nā pūnaewele maoli (eia ka mea koʻikoʻi - ua hoʻonohonoho ʻia ke kulekele - kahi i kānana ʻia ai ka DHCP Relay Circuit ID a loaʻa i kēia DHCP relay Circuit ID ka VNI no ka pūnaewele, ʻo ia hoʻi. E ʻokoʻa iki ka ID Circuit).
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.Loaʻa i kēia ʻatikala nā pane i kēia mau nīnau:
Nā mea
-
- ( & )
-
-
Hōʻike
Hoʻopuka pōkole kēia ʻāpana i nā ʻikepili mua: ʻO nā kuhikuhi no ka hoʻonohonoho ʻana i nā lako pūnaewele, nā RFC i hoʻohana ʻia i nā ʻeke DHCP i nā hale hana eVPN, ka hoʻomohala ʻana o nā hoʻonohonoho kikowaena DHCP ma Microsoft Windows Server 2012 i ka palapala Cisco i hāʻawi ʻia no ka ʻike. E like me ka ʻike pōkole e pili ana i ka Superscope a me nā kulekele i ka lawelawe DHCP ma Microsoft Windows Servers.
Pehea e hoʻonohonoho ai i ka DHCP Relay ma kahi VXLAN BGP EVPN, DFA lole
ʻO ka hoʻonohonoho ʻana i ka DHCP Relay ma kahi lole VXLAN BGP EVPN ʻaʻole ia ke kumuhana nui o kēia ʻatikala, no ka mea he maʻalahi loa ia. Hāʻawi wau i nā loulou i nā palapala a me kahi mea hao i nā hoʻonohonoho ma nā lako pūnaewele.
Ka laʻana o ka hoʻonohonoho ʻana i ka Relay DHCP ma 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
Nā RFC i hoʻokō ʻia i ka hana o ka lawelawe DHCP Relay ma nā lole VXLAN BGP EVPN
RFC#6607: Koho Sub-koho 151(0x97) - Koho Pūnaewele Pūnaewele.
• 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.Hoʻouna ʻia ka "inoa" o ka VRF kahi i loaʻa ai ka mea kūʻai.
RFC#5107: Koho haʻahaʻa 11(0xb) - Hoʻopau i ka ID kikowaena
• 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.Hoʻohana ʻia ke koho e hōʻoia i ka hoʻouna ʻana o ka mea kūʻai aku i kahi noi e hoʻololi i ka leka uila i ka helu IP i hoʻohana ʻia ma kēia koho. (Ma Cisco VXLAN BGP, ʻo EVPN ka ʻīpuka paʻamau o ka mea kūʻai aku Anycast address.)
RFC#3527: Koho-koho 5(0x5) - Koho loulou
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.Heluhelu o ka pūnaewele kahi e pono ai ka mea kūʻai aku i kahi helu IP.
Evolution o nā palapala Cisco e pili ana i ka hoʻonohonoho ʻana i ka DHCP ma Microsoft Windows Server 2012
Ua hoʻokomo wau i kēia ʻāpana no ka mea aia kahi ʻano maikaʻi ma ka ʻaoʻao o ka mea kūʻai aku:
Hōʻike wale ka palapala i ka hoʻonohonoho ʻana i ka DHCP Relay ma nā lako pūnaewele.
Ua hoʻohana ʻia kekahi ʻatikala e hoʻonohonoho i ka DHCP ma Windows Server 2012:
Hōʻike kēia ʻatikala e koi ana kēlā me kēia pūnaewele/VNI i kāna pūʻulu SuperScope ponoʻī a me kāna mau helu Loopback ponoʻī.
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.
Hoʻohui ʻia nā hoʻonohonoho kikowaena Windows 2012 i ka palapala no ka hoʻonohonoho ʻana i nā lako pūnaewele. No nā pūnāwai helu helu āpau i hoʻohana ʻia, pono hoʻokahi SuperScope no kēlā me kēia kikowaena data a ʻo kēia SuperScope ka palena o ke kikowaena ʻikepili:
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.
Ua wehewehe ʻia nā mea a pau me ka maʻalahi loa:
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 ma 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.
He aha ka SuperScope - he hana ia e hiki ai iā ʻoe ke hoʻohui i kekahi mau loko o nā IP address i hoʻokahi ʻāpana hoʻokele. E hoʻolaha i nā mea hoʻohana ma ka pūnaewele kino like (ma ka VLAN hoʻokahi) IP address mai kekahi mau loko. Inā hiki mai ka noi i kahi pūnāwai o nā helu wahi ma ke ʻano he SuperScope, a laila hiki ke hāʻawi ʻia i ka mea kūʻai aku i kahi helu mai kahi Scope ʻē aʻe i komo i kēia SuperScope.
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.
Nā kulekele - e ʻae iā ʻoe e hāʻawi i nā helu IP i nā mea hoʻohana ma muli o ke ʻano o ka mea hoʻohana a i ʻole ka palena. Hoʻohana nā ʻenekini Cisco i nā kulekele ma Windows Server 2012 e kānana e VNI (Virtual Network Identifier).
ʻO kaʻaoʻao nui
Aia kēia ʻāpana i nā hopena o ka noiʻi, no ke aha i kākoʻo ʻole ʻia ai, pehea e hana ai (logic), he aha ka mea hou a pehea e kōkua ai kēia mea hou iā mākou.
No ke aha i kākoʻo ʻole ʻia ai ʻo Microsoft Windows Server 2000/2003/2008?
ʻAʻole hana ʻo Microsoft Windows Server 2008 a me nā mana mua i ke koho 82 a hoʻouna ʻia ka ʻeke hoʻihoʻi me ke koho 82.
- Hoʻouna ʻia ka noi mai ka mea kūʻai aku i Broadcast (DHCP Discover).
- Hoʻouna ka mea hana (Nexus) i ka ʻeke i ke kikowaena DHCP (DHCP Discover + Option 82).
- Loaʻa ka DHCP Server i ka ʻeke, hana iā ia, hoʻihoʻi iā ia, akā me ke koho ʻole 82. (DHCP Offer - me ke koho ʻole 82)
- Loaʻa i ka lako (Nexus) kahi ʻeke mai ka kikowaena DHCP. (DHCP Offer) Akā ʻaʻole ia e hoʻouna i kēia ʻeke i ka mea hoʻohana hope.
ʻIkepili Sniffer - ma Windows Server 2008 a ma ka mea kūʻai aku DHCPLoaʻa iā Windows Server 2008 kahi noi mai nā lako pūnaewele. (Aia ke koho 82 ma ka papa inoa)
Hoʻouna ʻo Windows Server 2008 i ka pane i ka lako pūnaewele. (ʻAʻole helu ʻia ke koho 82 ma ke ʻano he koho i loko o ka pūʻolo)
Noi mai ka mea kūʻai mai - Aia ʻo DHCP Discover a ʻaʻohe DHCP Offer
Heluhelu ma nā lako pūnaewele:
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#
No ke aha i paʻakikī loa ai ka hoʻonohonoho ʻana ma Microsoft Windows Server 2012?
ʻAʻole kākoʻo ʻo Microsoft Windows Server 2012 iā RFC#3527 (koho 82 Sub-koho 5(0x5) - Koho loulou)
Akā ua hoʻokō ʻia ka hana Policy.
Кто э б:
- Loaʻa iā Microsoft Windows Server 2012 kahi wai puna nui (SuperScope) nona nā helu Loopback a me nā loko no nā pūnaewele maoli.
- ʻO ke koho ʻana o ka loko wai no ka hoʻopuka ʻana i kahi leka uila e hāʻule i SuperScope, ʻoiai ka pane mai ka DHCP Relay me ka Loopback Source address i hoʻokomo ʻia i SuperScope.
- Me ka hoʻohana ʻana i ke kulekele, koho ka noi mai Superscope i ka lālā lālā nona ka VNI i loko o ke koho 82 Suboption 1 Agent Circuit ID. ("0108000600"+ 24 bits VNI + 24 bits i ʻike ʻole ʻia iaʻu nā waiwai, akā hōʻike ka sniffer i nā waiwai o 0 ma kēia kahua.)
Pehea e maʻalahi ai ka hoʻonohonoho ʻana ma Microsoft Windows Server 2016/2019?
Hoʻohana ʻo Microsoft Windows Server 2016 i ka hana RFC#3527. ʻO ia hoʻi, hiki i ka Windows Server 2016 ke hoʻomaopopo i ka pūnaewele kūpono mai ke koho 82 Sub-koho 5(0x5) - Link Selection attribute
ʻEkolu mau nīnau e ala koke mai.
- Hiki iā mākou ke hana me ka ʻole o Superscope?
- Hiki iā mākou ke hana me ka ʻole o ke kulekele a hoʻololi i ka VNI i ke ʻano hexadecimal?
- Hiki iā mākou ke hana me ka ʻole o Scope for Loopback DHCP Source address?
Q. Hiki iā mākou ke hana me ka ʻole o Superscope?
A. ʻAe, hiki ke hana koke ʻia ka pae ma kahi o nā helu IPv4.
Q. Hiki iā mākou ke hana me ka ʻole o ke kulekele a hoʻololi i ka VNI i ke ʻano hexadecimal?
A. ʻAe, hoʻokumu ʻia ke koho pūnaewele ma ke koho 82 Suboption 0x5,
Q. Hiki iā mākou ke hana me ka ʻole o Scope for Loopback DHCP Source address?
A. ʻAʻole hiki iā mākou. No ka mea he palekana ʻo Microsoft Windows Server 2016/2019 i nā noi DHCP ʻino. ʻO ia hoʻi, ʻo nā noi a pau mai nā helu wahi ʻaʻole i loko o ka waihona kikowaena DHCP ua manaʻo ʻia he ʻino.
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.ʻO kēlā mau mea. No ka hoʻonohonoho ʻana i kahi wai DHCP no kahi hale hana VXLAN BGP EVPN ma Microsoft Windows Server 2016/2019, pono wale ʻoe:
- E hana i kahi wai no nā ʻōlelo Relay Source.
- E hana i kahi wai no nā pūnaewele mea kūʻai aku
ʻO ka mea pono ʻole (akā hiki ke hoʻonohonoho ʻia a e hana a ʻaʻole e hoʻopilikia i ka hana):
- Hana i ke Kumukānāwai
- E hana i ka SuperScope
Pākuhi:Ka laʻana o ka hoʻonohonoho ʻana i kahi kikowaena DHCP (aia he 2 mau mea kūʻai aku DHCP maoli - pili nā mea kūʻai aku i ka lole VXLAN)
Ka laʻana o ka hoʻonohonoho ʻana i kahi wai hoʻohana:
He laʻana o ka hoʻonohonoho ʻana i kahi wai hoʻohana (koho ʻia nā kulekele - e hōʻoia ʻaʻole i hoʻohana ʻia nā kulekele no ka hana pololei o ka loko):
ʻO kahi laʻana o ka hoʻonohonoho ʻana i kahi wai puna no nā helu helu DHCP Relay (ʻo ka laulā o nā helu no ka hoʻopuka ʻana e pili pono ana me ka wehe ʻana mai ka waihona helu helu):
Hoʻonohonoho i kahi lawelawe DHCP ma Microsoft Windows Server 2019
Ka hoʻonohonoho ʻana i kahi wai no nā helu Loopback (kumu) no DHCP Relay.
Hoʻokumu mākou i kahi wai puna hou (Scope) ma ka hakahaka IPv4.
Wizard hana loko. "A'e >"
E hoʻonohonoho i ka inoa o ka loko a me ka wehewehe ʻana o ka loko.
E hoʻonoho i ka laulā o nā helu IP no Loopback a me ka mask no ka loko.
Hoʻohui ʻokoʻa. Pono pono ka laula ho'oku'u 'ia me ka laula puna.
Manawa hoolimalima. "A'e >"
Nīnau: E hoʻonohonoho anei ʻoe i nā koho DHCP i kēia manawa (DNS, WINS, Gateway, Domain) a i ʻole e hana ʻoe ma hope. E ʻoi aku ka wikiwiki o ka pane ʻana ʻaʻole, a laila hoʻāʻo i ka pool me ka lima. A i ʻole e hele i ka hopena me ka ʻole o ka hoʻopiha ʻana i kekahi ʻike a hoʻāla i ka loko i ka hope o ka wizard.
Hōʻoia mākou ʻaʻole i hoʻonohonoho ʻia nā koho a ʻaʻole i hoʻāla ʻia ka loko. "Hoʻopau"
Ho'ā lima mākou i ka pool. — E koho i ka Scope a ma ka papa kuhikuhi poʻomanaʻo - koho iā "Activate".
Hana mākou i loko no nā mea hoʻohana / server.
Hoʻokumu mākou i kahi wai hou.
Wizard hana loko. "A'e >"
E hoʻonohonoho i ka inoa o ka loko a me ka wehewehe ʻana o ka loko.
E hoʻonoho i ka laulā o nā helu IP no Loopback a me ka mask no ka loko.
Hoʻohui ʻokoʻa. (ʻAʻohe mea ʻokoʻa i koi ʻia ma ka paʻamau) "Next >"
Manawa hoolimalima. "A'e >"
Nīnau: E hoʻonohonoho anei ʻoe i nā koho DHCP i kēia manawa (DNS, WINS, Gateway, Domain) a i ʻole e hana ʻoe ma hope. E hoʻonohonoho kāua i kēia manawa.
E hoʻonohonoho i ka helu wahi paʻamau.
Hoʻonohonoho mākou i ka domain a me nā helu kikowaena DNS.
Ke hoʻonohonoho nei i nā helu IP o nā kikowaena WINS.
Hoʻoulu ʻia ka laulā.
Hoʻonohonoho ʻia ka loko. "Hoʻopau"
hopena
ʻO ka hoʻohana ʻana i ka Windows Server 2016/2019 e hōʻemi i ka paʻakikī o ka hoʻonohonoho ʻana i kahi kikowaena DHCP no kahi lole VXLAN (a i ʻole kekahi lole ʻē aʻe). (ʻAʻole pono e hoʻololi i nā loulou kūikawā i nā loea IT: Network/Agent Circuit ID e hoʻopaʻa inoa i nā kānana.)
E hana anei ka hoʻonohonoho ʻana no Windows Server 2012 ma nā kikowaena 2016/2019 hou - ʻae.
Loaʻa i kēia palapala nā kuhikuhi i 2 mana: 7.X a me 9.3. ʻO kēia ma muli o ka mana 7.0 (3) I7 (7) he Cisco Suggested release, a ʻo ka mana 9.3 ka mea hou loa (ʻoiai ke kākoʻo nei i ka Multicast ma VXLAN Multisite).
Ka papa inoa o nā kumu
Source: www.habr.com