Task 03: Create DHCP Reservations for Management NICs
DOCUMENT CATEGORY: Runbook
SCOPE: Azure Local hardware provisioning
PURPOSE: Pre-stage DHCP reservations for management NICs so nodes receive consistent IPs on first OS boot, enabling automated remote configuration
MASTER REFERENCE: Phase 01: Hardware Provisioning
Status: Active
Overview
This task is optional but strongly recommended for enterprise deployments. Creating DHCP reservations for management NICs before OS installation enables automated IP discovery, eliminating manual console access or network scanning during initial configuration.
Benefits:
- Nodes receive a known, predictable IP the moment the OS boots for the first time
- Eliminates network scanning or manual console access during Stage 11/12 configuration
- Required for fully automated deployment pipelines
- Consistent IP addressing throughout the deployment lifecycle until static IPs are configured
Create DHCP reservations for in-band management NICs using MAC addresses from infrastructure.yml (populated from Task 02 hardware discovery) and planned IPs from infrastructure.yml. Although these interfaces are ultimately assigned static IPs during OS configuration, DHCP reservations provide consistent temporary addressing for remote automation workflows.
Prerequisites
| Requirement | Description | Source |
|---|---|---|
| Task 02 Complete | Management NIC MACs populated in infrastructure.yml | infrastructure.yml: nodes[].network_adapters[].mac_address |
| DHCP Server Access | FortiGate admin rights, Windows DHCP admin, or customer DHCP contact | Network team |
| Management Network Subnet | Management VLAN DHCP scope configured | infrastructure.yml: networking.management.subnet |
| Planned Management IPs | Assigned management IP per node | infrastructure.yml: nodes[].network_adapters[].ip_address |
Variables from infrastructure.yml
| Path | Type | Description |
|---|---|---|
networking.management.subnet | string | Management network CIDR (e.g., 192.168.203.0/24) |
nodes[].network_adapters[].ip_address | string | Planned management NIC IP address per node |
nodes[].name | string | Node hostname |
nodes[].serial_number | string | Dell service tag |
nodes[].network_adapters[].mac_address | string | Management NIC (onboard port 1 / Management LOM) MAC address |
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 management network and click Edit
- In the Reserved Addresses section, click Create New for each node:
- IP Address:
nodes[].network_adapters[].ip_addressfrominfrastructure.yml - MAC Address:
nodes[].network_adapters[].mac_addressfrominfrastructure.yml - Description:
<hostname>-mgmt (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 "<Management-DHCP-Server-Name>"
config reserved-address
edit "<hostname>-mgmt"
set ip <nodes.<name>.management_ip>
set mac <management-port-mac-address>
set description "Mgmt NIC 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 "mgmt"
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 [Management Network] → Reservations
- Right-click Reservations → New Reservation for each node:
- Reservation name:
<hostname>-mgmt - IP address:
nodes[].network_adapters[].ip_addressfrominfrastructure.yml - MAC address:
nodes[].network_adapters[].mac_addressfrominfrastructure.yml - Description:
Mgmt NIC 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-03-create-dhcp-reservations-for-management-nics/powershell/Invoke-DhcpReservationsMgmt-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 |
|---|---|---|
| Management NIC MAC | nodes[].network_adapters[].mac_address | 00:00:5E:00:53:01 |
| Planned management IP | nodes[].network_adapters[].ip_address | 192.168.203.11 |
| Reservation name | Derived: <hostname>-mgmt | azlocal-node01-mgmt |
| Description | Derived | Mgmt NIC for azlocal-node01 (ST: ABCDE01) |
| DHCP scope | networking.management.subnet | 192.168.203.0/24 |
Coordination Steps
- Extract node data from
infrastructure.yml - Submit request to customer network team with the table above
- Confirm VLAN and DHCP scope 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[].network_adapters[].ip_address - MAC addresses match
infrastructure.yml:nodes[].network_adapters[].mac_address - Reservation names follow convention:
<hostname>-mgmt
Validation Checklist
# Windows DHCP — List management NIC reservations
# The DHCP server and the scope of the management network (networking.management.subnet) come from your network team
$DHCPServer = '<dhcp-server>'
$MgmtScopeId = '<management-scope-id>'
Get-DhcpServerv4Reservation -ComputerName $DHCPServer -ScopeId $MgmtScopeId |
Format-Table -Property Name, IPAddress, ClientId, Description -AutoSize
Expected Output:
Name IPAddress ClientId Description
---- --------- -------- -----------
azlocal-node01-mgmt 192.168.203.11 00-00-5e-00-53-01 Mgmt NIC for azlocal-node01 (ST: ABCDE01)
azlocal-node02-mgmt 192.168.203.12 00-00-5e-00-53-02 Mgmt NIC for azlocal-node02 (ST: ABCDE02)
- DHCP reservation created for every node (one per node)
- IP addresses match
nodes[].network_adapters[].ip_addressininfrastructure.yml - MAC addresses match
nodes[].network_adapters[].mac_addressininfrastructure.yml - Reservation names follow convention:
<hostname>-mgmt - Reservation descriptions include hostname and service tag
- All reservations in the correct management 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 |
MAC address format error | Incorrect format | Use format: AA-BB-CC-DD-EE-FF (hyphens, not colons) |
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
| ← Task 02: Hardware Discovery | ↑ Phase 01: Hardware Provisioning | Task 04: BIOS/iDRAC Validation → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-01-31 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-04 | Azure Local Cloud | Fix tab labels, script paths, variable references, standards alignment |