Task 03: Configure Static IP Address
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.
DOCUMENT CATEGORY: Runbook
SCOPE: Network IP configuration
PURPOSE: Assign static management IP addresses to all nodes using explicit IP values frominfrastructure.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.
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:
- Finds the management port by its MAC address. The adapter name is not needed.
- Reads the current address. When it already matches the file, it changes nothing.
- Sets the static address, prefix and gateway on that port and turns DHCP off.
- 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.
- Reads the node again at the end of the run and compares it with the file.
Prerequisites
| Requirement | Description | Source |
|---|---|---|
| Tasks 01–02 Complete | WinRM and RDP enabled on all nodes | Task 01, Task 02 |
| Management IP per node | Static IP to assign | infrastructure.yml: nodes[].network_adapters[].ip_address |
| Subnet prefix length | e.g. 24 for /24 | infrastructure.yml: networking.management.subnet |
| Default gateway | Management network gateway | infrastructure.yml: networking.management.gateway |
| DNS servers | Primary and secondary DNS | infrastructure.yml: networking.management.dns_servers |
| Management NIC name | Exact adapter name on all nodes | infrastructure.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
- SConfig Utility
- Orchestrated Script
Run on each node via iDRAC Virtual Console or RDP.
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:
| Vendor | Typical Adapter Name | Notes |
|---|---|---|
| Nvidia / Mellanox ConnectX | Slot 3 Port 1 (or Slot X Port 1) | Slot number set during Phase 01 iDRAC discovery |
| Intel (embedded) | Embedded NIC 1 | Standard on Dell PowerEdge embedded Intel NICs |
| Broadcom (embedded) | Embedded NIC 1 | Standard on Dell PowerEdge embedded Broadcom NICs |
- Open iDRAC Virtual Console or connect via RDP
- Run
Get-NetAdapterin PowerShell — note the adapter name matchinginfrastructure.yml:nodes[].network_adapters[].name - Type
SConfigand press Enter (or it auto-launches) - Select option 8 — Network settings
- SConfig lists adapters by number — select the number corresponding to your management adapter identified in step 2
- Select option 1 — Set Network Adapter Address
- Enter S for Static
- Enter the static IP address from
infrastructure.yml:nodes[].network_adapters[].ip_address - Enter the subnet mask (e.g.,
255.255.255.0for /24,255.255.255.128for /25) - Enter the default gateway from
infrastructure.yml:networking.management.gateway - Select option 2 — Set DNS Servers; enter primary from
infrastructure.yml:networking.management.dns_servers - Enter secondary DNS from
infrastructure.yml:networking.management.dns_servers - Repeat for every node
PowerShell
No script in this task folder. The folder
scripts/deploy/04-cluster-deployment/phase-03-os-configuration/task-03-configure-static-ip-addressholds only a placeholder. A placeholder printsNOT IMPLEMENTED, changes nothing and exits with code 3. The earlierSet-StaticIPAddress.ps1is removed. The OS configuration does this task in its Network step.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-03-os-configuration/Invoke-AzureLocalOsConfiguration.ps1 | The one entry point of the OS configuration. It runs Set-AzureLocalNodeConfiguration.ps1 for each node: it reads the node, changes only what differs from infrastructure.yml, and reports. -Step limits the run to one step. |
A change of the management address is a guarded change: the node applies it, checks it and rolls it back unless the management host confirms it through a new session.
The timings of the guard are run settings (registry 5.0.60), given in the JSON file of -SettingsFile or in -Settings. Keep the defaults unless a node needs more time:
| Setting | Default | What it does |
|---|---|---|
startDelaySeconds | 20 | Pause between staging a change and the node's first change, so the call that staged it has returned |
checkSeconds | 300 | Longest the node waits for its checks to stay green for networkStableSeconds (at least networkStableSeconds + 120) |
repairSeconds | 45 | After each step of the repair ladder, how long the checks get to pass before the next step |
vlanLinkDownSeconds | 120 | Added to the node's deadline when a VLAN changes (the adapter restarts and the switch has to forward the new VLAN) |
hostnameConfirmExtraMinutes | 10 | Added to the confirmation window when the computer name changes with a restart |
The nodes' local administrator comes from identity.local_admin of infrastructure.yml (the password is a secret reference), or from -Credential. The script never prompts. Run settings go in a JSON file given with -SettingsFile.
Run
# Plan (the default): read every node and list what would change
./Invoke-AzureLocalOsConfiguration.ps1 -InfrastructureFile ./infrastructure.yml -Step Network
# Apply
./Invoke-AzureLocalOsConfiguration.ps1 -InfrastructureFile ./infrastructure.yml -Step Network -Mode Apply
See how the run works.
Validation Checklist
- Static IP configured on all nodes
-
PrefixOriginshowsManualon each management adapter -
DHCPshowsDisabledon 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
| Issue | Cause | Resolution |
|---|---|---|
| The plan shows the node as Blocked | A value the step needs is missing in infrastructure.yml | Add the value the message names, then run the plan again |
Adapter not found error | NIC name in config doesn't match the node | Run Get-NetAdapter on the node; update nodes[].network_adapters[].name in infrastructure.yml |
| Node unreachable after the run | The new address cannot be reached from the management host | The 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 script | DHCP not fully disabled | Run Set-NetIPInterface -InterfaceAlias '<nic>' -Dhcp Disabled on the node |
| Wrong IP locked in permanently | Incorrect value in infrastructure.yml | Correct nodes[].management.ip_address, then run the OS configuration again. It finds the difference and changes it |
| Gateway unreachable after config | Wrong gateway in infrastructure.yml | Verify networking.management.gateway; check upstream switch VLAN |
| DNS not resolving | DNS not set or wrong servers | Verify 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.
Navigation
| ← Task 02: Enable RDP | ↑ Phase 03: OS Configuration | Task 04: Disable DHCP → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-01-31 | Azure Local Cloud | Initial document |
| 2.0 | 2026-03-04 | Azure Local Cloud | Full rewrite to standards — complete frontmatter, 4-tab structure |
| 2.1 | 2026-03-04 | Azure Local Cloud | Embed full script code in each tab per provisioning runbook standard |
| 2.2 | 2026-03-04 | Azure Local Cloud | Fix SConfig NIC instructions — add vendor table, Get-NetAdapter step |
| 3.0 | 2026-03-04 | Azure Local Cloud | Replace 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 |