You must have a mechanism to assign IP addresses and enable discovery by DHCP for automatic device discovery to work. Bare Metal Orchestrator has three DHCP deployment mode options, and two automatic discovery options. The three DHCP options are:
- None
- No DHCP. IP addresses are manually assigned and static. Choosing this option means devices must be manually discovered.
- Relay
- The Bare Metal Orchestrator DHCP server is deployed in relay mode. It acts as a proxy and forwards requests to the DHCP server of the customer. Note: You must provide the DHCP relay interface name in the
interfaces
field and the external DHCP server forwarding IP address in thedhcpForwardIpAddress
field so Bare Metal Orchestrator knows where to forward the requests.
Automatic discovery does not work in relay mode.
- Server
- A DHCP manager pod is created when
dhcpDeployMode
is set to server. The DHCP server is a service that Bare Metal Orchestrator manages, and it is packaged and deployed as part of Bare Metal Orchestrator.Note: You must define the subnet, IP address pool, lease, and netmask values and interface names.
The two automatic discovery options are:
- Auto
- When
discoveryViaDhcp
is set to auto, Bare Metal Orchestrator attempts to automatically find devices. - None
- When
discoveryViaDhcp
is set to none, there is no automatic device discovery.
There are parameters you must pass to Bare Metal Orchestrator to enable DHCP. All DHCP configuration options are defined and passed in a YAML file. Customers must specify the IP addresses and interfaces in the YAML file.
DHCP YAML fields
DHCP options must be included in the YAML file that is passed when you create or edit a site. See DHCP fields for a table of Bare Metal Orchestrator DHCP options.
See Sample DHCP configuration YAML file for an example YAML file that shows the fields you need to define to configure DHCP.