|Enabling DHCP||Extending a reserved dynamic IP range|
|External DHCP and a reserved IP range||DHCP relay|
MAAS enlists and commissions nodes through the use of its DHCP server running on an untagged VLAN. Although this MAAS-managed DHCP can also be part of the deploy phase, an external DHCP server can optionally be used instead for this purpose (on a tagged VLAN). If MAAS detects an external DHCP server, it will display it on the rack controller’s page, accessible by selecting ‘Controllers’ from the top menu in the web UI.
Usually, the machine subnet is on the untagged VLAN. If not, you will need to route DHCP packets between the subnet and the MAAS-provided DHCP subnet. It is also possible to forward DHCP traffic from one VLAN to another using an external DHCP relay service.
Using an external DHCP server for enlistment and commissioning may work, but this is not supported. MAAS cannot manage an external DHCP server, nor can it keep leases synchronised when you return a node to the pool.a High availability and DHCP relay integration (see below) are also dependent upon MAAS-managed DHCP.
This documentation presupposes that MAAS-managed DHCP is used to enlist and commission nodes.
Required reading before continuing:
- Concepts and terms for an explanation of reserved IP ranges
- Commission nodes for an explanation of IP assignment modes
MAAS-managed DHCP needs a reserved dynamic IP range enlist and commission nodes. You should create such a range when you are enabling DHCP with the web UI. See MAAS CLI for instructions for doing this with the CLI.
To enable MAAS-managed DHCP, under the ‘Subnets’ page select the desired VLAN and then:
- Under the ‘Take action’ button select ‘Provide DHCP’. A new window will appear.
- Select the primary rack controller. For DHCP HA, select both the primary and the secondary.
- Create a reserved, dynamic IP range. Fill in the fields ‘Dynamic range start IP’ and ‘Dynamic range end IP’.
- Apply your changes with the ‘Provide DHCP’ button.
Now, addresses in this range will get assigned to machines that are being either enlisted or commissioned.
In addition, if you are deploying a node that has an interface connected to the untagged VLAN, and it has an IP assignment mode set to ‘DHCP,’ then it will also get an address in this range.
Extending a reserved dynamic IP range
If necessary, it is possible to add further portions of the subnet to the dynamic IP range (see IP ranges). Furthermore, since you enabled DHCP on a VLAN basis and a VLAN can contain multiple subnets, it is possible to add a portion from those subnets as well. Just select the subnet under the ‘Subnets’ page and reserve a dynamic range. DHCP will be enabled automatically.
External DHCP and a reserved IP range
If an external DHCP server is used to deploy machines, then a reserved IP range should be created to prevent the address namespace from being corrupted. For instance, address conflicts may occur if you set a node’s IP assignment mode to ‘Auto assign’ in the context of an external DHCP server. See IP ranges to create such a range. It should correspond to the lease range of the external server.
You should not enable DHCP relays in MAAS without sufficient planning. In particular, MAAS does not provide the actual relay. It must be set up as an external service by the administrator. What MAAS does provide is the DHCP configuration that MAAS-managed DHCP requires lin order to satisfy any client requests relayed from another VLAN.
To relay from one VLAN (source) to another VLAN (target):
Ensure the target VLAN has DHCP enabled.
Set up the external relay. This relay is set up independently from MAAS. See DHCP relay for software suggestions.
Configure MAAS-managed DHCP Navigate to the source VLAN page and select the ‘Relay DHCP’ action. Fill in the fields in the resulting form. The crucial setting is the target VLAN (‘Relay VLAN’). Press the ‘Relay DHCP’ button to finish. See MAAS CLI for how to do this with the CLI.
When MAAS manages DHCP, you customise it through the use of DHCP snippets. These are user-defined configuration options that can be applied either globally, per subnet, or per node. You apply a global snippet to all VLANs, subnets, and nodes. All three types end up in
/var/lib/maas/dhcpd6.conf. For information on what options to use, refer to the
dhcpd.conf man page.
Modifications made directly to
dhcpd6.conf.template are not supported.
To manage snippets, as an admin, open the ‘Settings’ page and click on the ‘DHCP snippets’ tab.
For example, to create a new snippet press ‘Add custom snippet’. In the resulting window, choose a name and type for it and enter its associated DHCP configuration. Click ‘Save snippet’ to apply the change, and make sure to activate the checkbox in the ‘Enabled’ column of the snippets list.
See MAAS CLI for doing this with the CLI.