-
Notifications
You must be signed in to change notification settings - Fork 103
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch '57-finalize' into stage
- Loading branch information
Showing
6 changed files
with
66 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -114,6 +114,21 @@ Cumulus Linux supports DHCP Agent Information Option 82, which allows a DHCP rel | |
|
||
To configure DHCP Agent Information Option 82: | ||
|
||
{{< tabs "TabID117 ">}} | ||
{{< tab "NVUE Commands ">}} | ||
|
||
The following example enables Option 82, enables circuit ID, and sets the remote ID to MAC address 44:38:39:BE:EF:AA: | ||
|
||
``` | ||
cumulus@leaf01:~$ nv set service dhcp-relay <vrf-id> agent enable on | ||
cumulus@leaf01:~$ nv set service dhcp-relay default agent remote-id 44:38:39:BE:EF:AA | ||
cumulus@leaf01:~$ nv set service dhcp-relay <vrf-id> agent use-pif-circuit-id enable on | ||
cumulus@leaf01:~$ nv config apply | ||
``` | ||
|
||
{{< /tab >}} | ||
{{< tab "Linux Commands ">}} | ||
|
||
1. Edit the `/etc/default/isc-dhcp-relay-default` file and add one of the following options: | ||
|
||
To inject the ingress *SVI interface* against which DHCP processes the relayed DHCP discover packet, add `-a` to the `OPTIONS` line: | ||
|
@@ -149,6 +164,9 @@ To configure DHCP Agent Information Option 82: | |
cumulus@leaf01:~$ sudo systemctl restart [email protected] | ||
``` | ||
|
||
{{< /tab >}} | ||
{{< /tabs >}} | ||
|
||
### Control the Gateway IP Address with RFC 3527 | ||
|
||
When you need DHCP relay in an environment that relies on an anycast gateway (such as EVPN), a unique IP address is necessary on each device for return traffic. By default, in a BGP unnumbered environment with DHCP relay, the source IP address is the loopback IP address and the gateway IP address is the SVI IP address. However with anycast traffic, the SVI IP address is not unique to each rack; it is typically shared between racks. Most EVPN ToR deployments only use a single unique IP address, which is the loopback IP address. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters