Task 01: Create DHCP Reservations for iDRAC Interfaces
DOCUMENT CATEGORY: Runbook
SCOPE: Azure Local hardware provisioning
PURPOSE: Pre-stage DHCP reservations so iDRAC interfaces receive consistent IP addresses from the moment hardware is powered on
MASTER REFERENCE: Phase 01: Hardware Provisioning
Status: Active
Overview
Create DHCP reservations for iDRAC out-of-band management interfaces using MAC addresses and planned IPs from infrastructure.yml. This task is performed before hardware arrives on site — MAC addresses come from the Dell order documentation (packing slip or TechDirect), not from a discovery scan.
This task configures DHCP reservations for iDRAC (out-of-band) interfaces only. Management NIC (in-band) reservations are an optional separate task (Task 03). Management NIC static IPs are configured during OS installation.
This task may be skipped if iDRACs have already been assigned static IP addresses prior to deployment.
Prerequisites
| Requirement | Description | Source |
|---|---|---|
| DHCP Server Access | FortiGate admin rights, Windows DHCP admin, or customer DHCP contact | Network team |
| OOB Network Subnet | Out-of-band VLAN and DHCP scope configured | infrastructure.yml: networking.oob.subnet |
| Node MAC Addresses | iDRAC MAC addresses from Dell order documentation | Order documentation or the iDRAC (not a key of infrastructure.yml) |
| Planned iDRAC IPs | Assigned iDRAC IP per node | infrastructure.yml: nodes[].bmc.ip_address |
Values from infrastructure.yml
| Key | What it is |
|---|---|
networking.oob.subnet | The out-of-band management network (the DHCP scope) |
nodes[].bmc.ip_address | The planned iDRAC IP address of each node |
nodes[].name | The node host name |
nodes[].serial_number | The Dell service tag |
The iDRAC MAC address and the DHCP server are not keys of infrastructure.yml. Take the MAC address from the order documentation or the iDRAC, and ask the network team for the DHCP server.
Execution Options
Select the tab matching your DHCP infrastructure:
- FortiGate DHCP
- Windows DHCP Server
- Customer-Managed DHCP
When to use: Azure Local Cloud-managed environments using FortiGate firewalls for DHCP
FortiGate Web UI
- Open browser to
https://<fortigate-ip>and log in with admin credentials - Navigate to Policy & Objects → DHCP Server
- Select the DHCP server for the OOB management network and click Edit
- In the Reserved Addresses section, click Create New for each node:
- IP Address:
nodes[].bmc.ip_addressfrominfrastructure.yml - MAC Address: the iDRAC MAC address from the order documentation (it is not a key of
infrastructure.yml) - Description:
<hostname>-iDRAC (Service Tag: <service-tag>)
- Click OK to save
FortiOS CLI (from Management Server)
Connect via SSH from the management server and run the following for each node. Replace values with actual entries from infrastructure.yml.
# ============================================================================
# FortiGate DHCP Reservation — FortiOS CLI
# Execution: SSH FROM management server TO FortiGate
# Prerequisites: SSH access to FortiGate, admin rights
# ============================================================================
ssh admin@<fortigate-ip>
config system dhcp server
edit "<OOB-DHCP-Server-Name>"
config reserved-address
edit "<hostname>-iDRAC"
set ip <nodes[].bmc.ip_address>
set mac <idrac-mac-address>
set description "iDRAC for <hostname> (ST: <service_tag>)"
next
end
next
end
save config
exit
Repeat the edit block for each node.
Validation
# Verify reservations on FortiGate
show system dhcp server | grep -A5 "iDRAC"
When to use: Azure Local Cloud-managed environments using Windows Server DHCP
Windows DHCP Console
- Run
dhcpmgmt.mscon the DHCP server or an admin workstation with RSAT installed - Connect to the DHCP server
- Expand server → IPv4 → Scope [OOB Network] → Reservations
- Right-click Reservations → New Reservation for each node:
- Reservation name:
<hostname>-iDRAC - IP address:
nodes[].bmc.ip_addressfrominfrastructure.yml - MAC address: the iDRAC MAC address from the order documentation (it is not a key of
infrastructure.yml) - Description:
iDRAC for <hostname> (Service Tag: <service-tag>) - Click Add
Scripts
The toolkit has no script for DHCP reservations. They are the task of the network team. The task folder (scripts/deploy/04-cluster-deployment/phase-01-hardware-provisioning/task-01-create-dhcp-reservations-for-idrac-interfaces/powershell/Invoke-DhcpReservationsIdrac-Orchestrated.ps1) holds only a placeholder: it prints NOT IMPLEMENTED, changes nothing and exits with code 3. Use the console steps above.
When to use: DHCP infrastructure is managed by the customer network team
Information to Provide to Customer
Extract and provide the following from infrastructure.yml:
| Field | infrastructure.yml Path | Example |
|---|---|---|
| iDRAC MAC address | the iDRAC MAC address from the order documentation (it is not a key of infrastructure.yml) | 00:00:5E:00:53:11 |
| Planned iDRAC IP | nodes[].bmc.ip_address | 198.51.100.11 |
| Reservation name | Derived: <hostname>-iDRAC | iic-azl-n01-iDRAC |
| Description | Derived | iDRAC for iic-azl-n01 (ST: SERIAL01) |
| DHCP scope | networking.oob.subnet | 198.51.100.0/24 |
Coordination Steps
- Extract node data from
infrastructure.yml - Submit request to customer network team with the table above
- Confirm scope and VLAN with network team
- Obtain confirmation that reservations have been created
- Validate (see below)
Validation
- Customer confirms all reservations created
- IP addresses match
infrastructure.yml:nodes[].bmc.ip_address - MAC addresses match the iDRAC MAC address from the order documentation (it is not a key of
infrastructure.yml) - Reservation names follow convention:
<hostname>-iDRAC
Validation Checklist
- DHCP reservation created for every node (one per node)
- IP addresses match
nodes[].bmc.ip_addressininfrastructure.yml - MAC addresses match the iDRAC MAC address from the order documentation (it is not a key of
infrastructure.yml) - Reservation names follow convention:
<hostname>-iDRAC - Reservation descriptions include hostname and service tag
- All reservations in the correct OOB DHCP scope
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
DhcpServer module not found | RSAT not installed | Install-WindowsFeature RSAT-DHCP or run directly on DHCP server |
Duplicate reservation | Reservation already exists | Remove existing: Remove-DhcpServerv4Reservation then re-add |
Scope not found | Wrong scope ID | Verify: Get-DhcpServerv4Scope -ComputerName $DHCPServer |
Access denied | Insufficient rights | Run as DHCP Administrator role member |
FortiGate SSH access denied | SSH not enabled or wrong credentials | Enable SSH on FortiGate admin interface |
DHCP server unreachable | Network connectivity | Verify management server can reach DHCP server |
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Navigation
| ← Phase 01 Overview | ↑ Phase 01: Hardware Provisioning | Task 02: Hardware Discovery → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-01-01 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-04 | Azure Local Cloud | Fix tab labels, script paths, standards alignment |