For Abiquo private, external and public networks, the platform can manage their corresponding VLANs with an ISC DHCP server. Abiquo recommends one DHCP server per physical datacenter. Add the DHCP service to Abiquo when creating or editing a datacenter. You can use the Remote Services DHCP server supplied with Abiquo or another compatible server. If you have many virtual networks, you might need a separate relay server to manage VLANs for the DHCP server. For unmanaged networks, you do not need to configure a DHCP server and you must provide the network addresses to the virtual machines outside of Abiquo.
How Abiquo uses DHCP
Abiquo standard VLAN management has the following features:
- Virtual networks as separate VLANs
- The Cloud Administrator defines VLAN tag pools in Abiquo when creating the racks
- External and public networks are created in the infrastructure and define in Abiquo later
- Private networks will be defined by Abiquo from the racks VLAN tag pools
The connections in DHCP are as follows:
- When you deploy a virtual machine, Abiquo (Remotes Services) supplies the network settings for the new VM to the DHCP Server.
- When the new virtual machine powers on, it broadcasts a DHCP request for network configuration.
- The hypervisor passes the DHCP request through a VLAN to the DHCP server.
- The DHCP server broadcasts a lease with the network configuration for the virtual machine over the same VLAN
DHCP Configurations
When configuring DHCP for a datacenter using the remote services, the possible DHCP configurations are as follows.
DHCP Server only, for < 200 VLANs. The DHCP Server listens to all the VLANs. Abiquo recommends that you use a separate DHCP Server (not the Remote Services DHCP Service) in this configuration.
DHCP Server with DHCP Relay, for < 1000 VLANs. The DHCP relay server listens to all the VLANs and forwards the DHCP requests to the DHCP Server. In this configuration you can use the DHCP server on the Remote Services server. Do not configure support for VLANs on the DHCP Server.
DHCP Server with muliptle DHCP Relays, for > 1000 VLANs. Multiple DHCP relay servers allow you to create large networks in a hierarchical forwarding structure.
DHCP Installation Guide
The server managing VLANs must be able to listen to VLANs, so it must be a separate physical machine or a virtual machine on a hypervisor with VLAN support, such as VMware ESXi (see How to configure an ESXi host to support VLAN tagging) or RedHat KVM.
To configure a single DHCP server with VLAN support, see Configuring a DHCP Server.
To install a DHCP Relay server with the Abiquo OVA install - see Automatically Configuring One DHCP Relay Server.
These configurations are designed for multiple VLAN networks, which by definition have separate VLAN tags and isolate DHCP broadcasts. The server managing VLANs (DHCP Relay or DHCP Server) must have one VNIC or NIC with an IP address for each VLAN that will identify the VLAN to the DHCP Server. The DHCP Server and VM communicate through broadcasts, which are also relayed, until the IP address of the VM is set, so there is no specific requirement for the IP address of the VNIC or NIC. However, it is recommended that the IP address range is not part of any other networks. For example, you could use the upper range of the management network. If you have complex requirements, you may need to adapt these configurations.
If you need to use multiple relay servers, see Manually Configuring Multiple DHCP Relay Servers