Skip to main content

Task 01: Create DHCP Reservations for iDRAC Interfaces

Runbook Azure Dell

Optional

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.

iDRAC Interfaces Only

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​

RequirementDescriptionSource
DHCP Server AccessFortiGate admin rights, Windows DHCP admin, or customer DHCP contactNetwork team
OOB Network SubnetOut-of-band VLAN and DHCP scope configuredinfrastructure.yml: networking.oob.subnet
Node MAC AddressesiDRAC MAC addresses from Dell order documentationOrder documentation or the iDRAC (not a key of infrastructure.yml)
Planned iDRAC IPsAssigned iDRAC IP per nodeinfrastructure.yml: nodes[].bmc.ip_address

Values from infrastructure.yml​

KeyWhat it is
networking.oob.subnetThe out-of-band management network (the DHCP scope)
nodes[].bmc.ip_addressThe planned iDRAC IP address of each node
nodes[].nameThe node host name
nodes[].serial_numberThe 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:

When to use: Azure Local Cloud-managed environments using FortiGate firewalls for DHCP

FortiGate Web UI​

  1. Open browser to https://<fortigate-ip> and log in with admin credentials
  2. Navigate to Policy & Objects → DHCP Server
  3. Select the DHCP server for the OOB management network and click Edit
  4. In the Reserved Addresses section, click Create New for each node:
  • IP Address: nodes[].bmc.ip_address from infrastructure.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>)
  1. 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"

Validation Checklist​

  • DHCP reservation created for every node (one per node)
  • IP addresses match nodes[].bmc.ip_address in infrastructure.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​

IssueCauseResolution
DhcpServer module not foundRSAT not installedInstall-WindowsFeature RSAT-DHCP or run directly on DHCP server
Duplicate reservationReservation already existsRemove existing: Remove-DhcpServerv4Reservation then re-add
Scope not foundWrong scope IDVerify: Get-DhcpServerv4Scope -ComputerName $DHCPServer
Access deniedInsufficient rightsRun as DHCP Administrator role member
FortiGate SSH access deniedSSH not enabled or wrong credentialsEnable SSH on FortiGate admin interface
DHCP server unreachableNetwork connectivityVerify 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.

← Phase 01 Overview↑ Phase 01: Hardware ProvisioningTask 02: Hardware Discovery →

Version Control​

VersionDateAuthorChanges
1.02026-01-01Azure Local CloudInitial document
1.12026-03-04Azure Local CloudFix tab labels, script paths, standards alignment