ProHoster > ááá±á¬á· > á¡á¯ááºáá»á¯ááºáá±áž > VXLAN (DFA) á¡ááœáẠDHCP áááºáá±á¬ááºááŸá¯áá»á¬áž áá¶á·ááá¯ážáá±ážáááºá¡ááœáẠMicrosoft Windows Server 2016/2019 ááᯠááŒááºáááºááŒááºáž
VXLAN (DFA) á¡ááœáẠDHCP áááºáá±á¬ááºááŸá¯áá»á¬áž áá¶á·ááá¯ážáá±ážáááºá¡ááœáẠMicrosoft Windows Server 2016/2019 ááᯠááŒááºáááºááŒááºáž
á€áá±á¬ááºážáá«ážááááºááœááºáá»ááºááŸá¬ Microsoft Windows Server 2016/2019 ááá¯á¡áá¯á¶ážááŒá¯á VXLAN BGP EVPN ááŸáá·áº DFA áááºá¡ááœáẠDHCP áááºáá±á¬ááºááŸá¯áááœá²á·á ááºážáá¯á¶ááᯠááá¯ážááŸááºážá á±áááºááŒá áºáááºá
ááá¬ážáááºá á¬ááœááºá á¬áááºážááœááºá á¡áááºá¡ááœáẠMicrosoft Windows Server 2012 áá±á«áºá¡ááŒá±áá¶á DHCP áááºáá±á¬ááºááŸá¯ááᯠLoopback áá±áá°ážáááºáá«ááŸááá±á¬ SuperScope á¡ááŒá áºáááºááŸááºáá¬ážáá«áááºá áá±áá°ážáááº)) ááŸáá·áº á á áºááŸááºáá±á¬ááœááºáááºáá»á¬ážá¡ááœáẠIP ááááºá á¬áá»á¬ážáá¯ááºáá±ážááŒááºážááá¯ááºáá¬áá°ážááœá²áá»á¬áž (á€áá±áá¬ááœáẠáá®ážáá±á¬ááºážááá¯ážááŒáá¬ážááẠ- áá°áá«áááᯠá á®á ááºáááºááŸááºáá¬ážááẠ- áááºážááœáẠDHCP Relay Circuit ID ááᯠá á áºáá¯ááºááŒá®áž ဠDHCP áááºááá·áºááá¯ááºáááºáááºážááŒá±á¬ááºáž ID ááœáẠááœááºáááºá¡ááœáẠVNI áá«ááŸááááºá ááá¯ááá¯áááºááŸá¬ ဠDHCP Relay á¡ááŒá¬ážá¡á¯ááºá á¯á¡ááœáẠCircuit ID á¡áááºážáááºááœá²ááŒá¬ážáá«áááºá)
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.
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
⢠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.
RFC#5107- ááœá±ážáá»ááºááŸá¯ááœá² 11(0xb) - áá¬áᬠID ááᯠá¡á á¬ážááá¯ážáá«á
⢠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.
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.
áá±á¬ááºáááºááẠIP ááááºá ᬠááá¯á¡ááºááá·áº ááœááºáááºáááááºá á¬á
Microsoft Windows Server 2012 ááœáẠDHCP ááᯠââconfigure áá¯ááºááŒááºážááá¯ááºáᬠCisco documentation á ááá·áºáá²ááŒá áºá ááº
Windows Server 2012 ááœáẠDHCP ááᯠââconfigure áá¯ááºááẠá¡ááŒá¬ážáá±á¬ááºážáá«ážááᯠá¡áá¯á¶ážááŒá¯áá²á·áááºá
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.
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.
Microsoft Windows Server ááœáẠDHCP (á á°áá«á áá¯ááºááŸáá·áº áá°áá«á)
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.
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.
áá°áá«ááá»á¬áž - á¡áá¯á¶ážááŒá¯áá°á¡áá»áá¯ážá¡á á¬áž ááá¯á·ááá¯áẠááá·áºáááºáá»ááºá¡áá±á«áºáá°áááºá á¡áá¯á¶ážááŒá¯áá°áá»á¬ážá¡á¬áž IP ááááºá á¬áá»á¬ážááᯠáááºááŸááºááœáá·áºááŒá¯áááºá Cisco á¡ááºáá»ááºáá®áá¬áá»á¬ážááẠVNI (Virtual Network Identifier) ââááᯠá á áºáá¯ááºááẠWindows Server 2012 ááœáẠáá°áá«ááá»á¬ážááᯠá¡áá¯á¶ážááŒá¯áááºá
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#
Microsoft Windows Server 2012 ááœáẠconfiguration ááẠá¡áááºááŒá±á¬áá·áº á¡ááœááºááŸá¯ááºááœá±ážááááºážá
Microsoft Windows Server 2012 ááẠRFC#3527 ááᯠááá¶á·ááá¯ážááá±ážáá« (ááœá±ážáá»ááºááŸá¯ 82 ááœá²ááœá±ážáá»ááºááŸá¯ 5(0x5) - ááá·áºááºááœá±ážáá»ááºááŸá¯)
ááá¯á·áá±á¬áº áá°áá«áá áá¯ááºáá±á¬ááºááá¯ááºá áœááºážááᯠá¡áá±á¬ááºá¡áááºáá±á¬áºááŒá®ážááŒá áºáááºá
Microsoft Windows Server 2012 ááœáẠáááá·áºááœááºáááºáá»á¬ážá¡ááœáẠLoopback ááááºá á¬áá»á¬ážááŸáá·áº áá±á«ááºážáá°ážáá»á¬ážáá«ááŸááá±á¬ á á°áá«áá°ážááœá² (SuperScope) áá«ááŸááááºá
Microsoft Windows Server 2016/2019 ááœáẠá áá áºááá·áºááœááºážááŸá¯ááᯠáááºááá¯á·ááá¯ážááŸááºážá á±ááááºážá
Microsoft Windows Server 2016 ááẠRFC#3527 áá¯ááºáá±á¬ááºááá¯ááºá áœááºážááᯠá¡áá±á¬ááºá¡áááºáá±á¬áºáááºá ááá¯ááá¯áááºááŸá¬á Windows Server 2016 ááẠOption 82 Sub-option 5(0x5) - Link Selection attribute á០ááŸááºáááºáá±á¬ááœááºáááºááᯠá¡ááá¡ááŸááºááŒá¯ááá¯ááºáááº
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.
á¡á²áá«ááœá±á Microsoft Windows Server 2016/2019 ááŸá VXLAN BGP EVPN á ááºáá¯á¶á¡ááœáẠDHCP pool ááᯠconfigure áá¯ááºáááºá áááºáᬠááá¯á¡ááºáááº-
Source Relay ááááºá á¬áá»á¬ážá¡ááœáẠpool áá áºáá¯áááºáá®ážáá«á