Skip to main content

Task 03: Configure Static IP Address

The automated run does this task for you

The automated OS configuration run covers this task in the Network step. It finds the management port by its MAC and sets the static address there (management modes B and C), or verifies the reserved address (mode A). Use the manual steps below when you can't use the run, or to understand or troubleshoot what it does. See how the run works.

Runbook Azure Dell

DOCUMENT CATEGORY: Runbook
SCOPE: Network IP configuration
PURPOSE: Assign static management IP addresses to all nodes using explicit IP values from infrastructure.yml — not read from DHCP
MASTER REFERENCE: Phase 03: OS Configuration

Status: Active

Overview​

Configure a static IP address on the management network adapter of each Azure Local node. All IP parameters — address, subnet prefix, gateway, and DNS — come from infrastructure.yml. The OS configuration does not keep the current DHCP-assigned address.

Explicit values required — verify before running

All IP values in infrastructure.yml must be correct before you apply. The run locks in whatever address the file gives.

What the Network step of the OS configuration does on each node:

  1. Finds the management port by its MAC address. The adapter name is not needed.
  2. Reads the current address. When it already matches the file, it changes nothing.
  3. Sets the static address, prefix and gateway on that port and turns DHCP off.
  4. Applies the change as a guarded change: the node checks it and rolls it back unless the management host confirms it through a new session.
  5. Reads the node again at the end of the run and compares it with the file.

Prerequisites​

RequirementDescriptionSource
Tasks 01–02 CompleteWinRM and RDP enabled on all nodesTask 01, Task 02
Management IP per nodeStatic IP to assigninfrastructure.yml: nodes[].network_adapters[].ip_address
Subnet prefix lengthe.g. 24 for /24infrastructure.yml: networking.management.subnet
Default gatewayManagement network gatewayinfrastructure.yml: networking.management.gateway
DNS serversPrimary and secondary DNSinfrastructure.yml: networking.management.dns_servers
Management NIC nameExact adapter name on all nodesinfrastructure.yml: nodes[].network_adapters[].name (from Phase 01 hardware discovery)

Values from infrastructure.yml​

The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.


Execution​

Run on each node via iDRAC Virtual Console or RDP.

Identify the Management Adapter Before Starting

The adapter number shown in SConfig varies. Before selecting, run Get-NetAdapter in PowerShell to list all adapters and confirm the correct name. The management adapter name is recorded in infrastructure.yml: nodes[].network_adapters[].name from the iDRAC discovery performed in Phase 01.

Common adapter names by NIC vendor:

VendorTypical Adapter NameNotes
Nvidia / Mellanox ConnectXSlot 3 Port 1 (or Slot X Port 1)Slot number set during Phase 01 iDRAC discovery
Intel (embedded)Embedded NIC 1Standard on Dell PowerEdge embedded Intel NICs
Broadcom (embedded)Embedded NIC 1Standard on Dell PowerEdge embedded Broadcom NICs
  1. Open iDRAC Virtual Console or connect via RDP
  2. Run Get-NetAdapter in PowerShell — note the adapter name matching infrastructure.yml: nodes[].network_adapters[].name
  3. Type SConfig and press Enter (or it auto-launches)
  4. Select option 8 — Network settings
  5. SConfig lists adapters by number — select the number corresponding to your management adapter identified in step 2
  6. Select option 1 — Set Network Adapter Address
  7. Enter S for Static
  8. Enter the static IP address from infrastructure.yml: nodes[].network_adapters[].ip_address
  9. Enter the subnet mask (e.g., 255.255.255.0 for /24, 255.255.255.128 for /25)
  10. Enter the default gateway from infrastructure.yml: networking.management.gateway
  11. Select option 2 — Set DNS Servers; enter primary from infrastructure.yml: networking.management.dns_servers
  12. Enter secondary DNS from infrastructure.yml: networking.management.dns_servers
  13. Repeat for every node

Validation Checklist​

  • Static IP configured on all nodes
  • PrefixOrigin shows Manual on each management adapter
  • DHCP shows Disabled on each management adapter
  • Default gateway reachable from each node
  • DNS servers responding from each node
# Run on each node — verify static assignment
$nic = "Embedded NIC 1" # replace with cluster.management_nic_name from infrastructure.yml
Get-NetIPAddress -InterfaceAlias $nic -AddressFamily IPv4 |
Select-Object IPAddress, PrefixLength, PrefixOrigin

Get-NetIPInterface -InterfaceAlias $nic -AddressFamily IPv4 |
Select-Object InterfaceAlias, Dhcp

# Test gateway and DNS reachability
Test-Connection -ComputerName (Get-NetRoute -AddressFamily IPv4 | Where-Object { $_.DestinationPrefix -eq "0.0.0.0/0" }).NextHop -Count 1 -Quiet
Resolve-DnsName "azure.microsoft.com" -ErrorAction SilentlyContinue | Select-Object Name, IPAddress

Troubleshooting​

IssueCauseResolution
The plan shows the node as BlockedA value the step needs is missing in infrastructure.ymlAdd the value the message names, then run the plan again
Adapter not found errorNIC name in config doesn't match the nodeRun Get-NetAdapter on the node; update nodes[].network_adapters[].name in infrastructure.yml
Node unreachable after the runThe new address cannot be reached from the management hostThe node rolls the guarded change back when the management host does not confirm it. Check the address, VLAN and gateway in infrastructure.yml and the run report
PrefixOrigin shows Dhcp after scriptDHCP not fully disabledRun Set-NetIPInterface -InterfaceAlias '<nic>' -Dhcp Disabled on the node
Wrong IP locked in permanentlyIncorrect value in infrastructure.ymlCorrect nodes[].management.ip_address, then run the OS configuration again. It finds the difference and changes it
Gateway unreachable after configWrong gateway in infrastructure.ymlVerify networking.management.gateway; check upstream switch VLAN
DNS not resolvingDNS not set or wrong serversVerify networking.management.dns_servers; run the Dns step again


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.

← Task 02: Enable RDP↑ Phase 03: OS ConfigurationTask 04: Disable DHCP →

Version Control​

VersionDateAuthorChanges
1.02026-01-31Azure Local CloudInitial document
2.02026-03-04Azure Local CloudFull rewrite to standards — complete frontmatter, 4-tab structure
2.12026-03-04Azure Local CloudEmbed full script code in each tab per provisioning runbook standard
2.22026-03-04Azure Local CloudFix SConfig NIC instructions — add vendor table, Get-NetAdapter step
3.02026-03-04Azure Local CloudReplace DHCP-detection scripts with explicit IP configuration; merge Direct+Standalone into Set-StaticIPAddress.ps1; rewrite Orchestrated with session-loss handling and per-node IP from yml; remove Standalone tab