Task 08: Enable ICMP (Ping)
The automated OS configuration run covers this task in the RemoteManagement step (ICMP echo rules). 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: Firewall configuration
PURPOSE: Enable ICMP ping on all cluster nodes so that network connectivity can be tested and validated throughout the deployment process
MASTER REFERENCE: Phase 03: OS Configuration
Status: Active Estimated Time: 2 minutes per node / 5 minutes with the OS configuration (all nodes)
Overview
Windows Server blocks ICMP by default. Enabling the ICMPv4-In and ICMPv6-In firewall rules allows ping-based connectivity validation from the management server and between nodes — required for cluster health checks, network diagnostics, and Azure Local validation tooling.
What the steps do:
- Enable
File and Printer Sharing (Echo Request - ICMPv4-In) - Enable
File and Printer Sharing (Echo Request - ICMPv6-In) - Verify each rule is enabled and report pass/fail
No configuration variables are required — this task has no values to read from infrastructure.yml.
Prerequisites
| Requirement | Description | Source |
|---|---|---|
| Task 07 complete | NTP configured on all nodes | Task 07: Configure NTP |
| Local admin rights | Required to modify firewall rules | Node credentials |
Execution Options
- SConfig (Recommended)
- Orchestrated Script
On the node console, open SConfig if not already running:
sconfig
Navigate the menu:
- Select
4→ Configure Remote Management - Select
3→ Configure Windows Firewall to allow ICMPv4 responses (ping) - Confirm the prompt — ICMP ping is now enabled
- Select
4→ Back to main menu
SConfig only configures ICMPv4. If ICMPv6 is also required, enable the ICMPv6 rule by hand with Enable-NetFirewallRule, or use the Orchestrated tab.
PowerShell
No script in this task folder. The folder
scripts/deploy/04-cluster-deployment/phase-03-os-configuration/task-08-enable-icmp-pingholds only a placeholder. A placeholder printsNOT IMPLEMENTED, changes nothing and exits with code 3. The earlierEnable-ICMPFirewallRule.ps1is removed. The OS configuration does this task in its RemoteManagement 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. |
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 RemoteManagement
# Apply
./Invoke-AzureLocalOsConfiguration.ps1 -InfrastructureFile ./infrastructure.yml -Step RemoteManagement -Mode Apply
See how the run works.
Validation Checklist
- ICMPv4-In rule enabled on all nodes (
Get-NetFirewallRule -DisplayName "*ICMPv4-In*") - ICMPv6-In rule enabled on all nodes (
Get-NetFirewallRule -DisplayName "*ICMPv6-In*") - Nodes respond to ping from management server (
Test-Connection -ComputerName <node-ip> -Count 2)
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.
Troubleshooting
| Issue | Root Cause | Remediation |
|---|---|---|
| Rule not found | Rule name differs (GPO rename or locale) | Run `Get-NetFirewallRule |
| Rule found but still not enabled | Group Policy overriding local rule | Check GPO firewall policy; may need to configure via GPO |
| OS configuration: node unreachable | WinRM not enabled or firewall blocking | Verify WinRM configured (Task 01); check firewall allows port 5985/5986 |
| Ping still failing after enable | Layer-3 routing or switch ACL | Verify network path; check switch ACLs and VLAN routing |
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 07: Configure NTP | ↑ Phase 03: OS Configuration | Task 09: Disable Unused Adapters → |
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, bare-node 2-tab structure (Direct, Orchestrated), Standalone tab removed, full embedded scripts, Get-ClusterNodes helper, no configuration variables required |