Task 02: Customer Network Service Verification
DOCUMENT CATEGORY: Runbook
SCOPE: Customer network service validation
PURPOSE: Verify customer-provided DNS and NTP services are operational
MASTER REFERENCE: Microsoft Learn - Network Requirements
Status: Active Estimated Time: 30 minutes
Overview
Verify that customer-provided network services (DNS, NTP) are operational from the management network. These services should already be configured by the customer network team as part of their infrastructure prerequisites.
This step validates customer-provided services only - services that should work before Azure Local Cloud configures switches and firewall rules in Phase 03.
Azure and Dell endpoint connectivity testing occurs in Phase 03 Step 4 after network infrastructure is configured.
Performed by: Engineer on management VLAN workstation
Prerequisites
| Requirement | Description |
|---|---|
| Validation workstation | Windows machine on management VLAN |
| PowerShell | Version 5.1 or later |
| Discovery data | DNS server IPs, NTP server, AD domain from infrastructure.yml |
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.
DNS Resolution Tests
- Manual Verification
- Orchestrated Script
- Open PowerShell on the management workstation.
- Use
Resolve-DnsNameto test each AD domain controller hostname. - Use
nslookupto verify against specific DNS server IPs. - Record results (hostname, resolved IP, pass/fail).
- If any resolution fails, coordinate with the customer DNS team before proceeding.
PowerShell
No script in this task folder. The folder holds only a placeholder. A placeholder prints
NOT IMPLEMENTED, changes nothing and exits with code 3. The earlierSet-InfrastructurePrep.ps1is removed. The OS configuration sets the Windows features and the time source, and the pre-cluster verification checks the node services.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-03-os-configuration/Invoke-AzureLocalOsConfiguration.ps1 | The OS configuration. It runs Set-AzureLocalNodeConfiguration.ps1 on each node: it reads each node, changes only what differs from infrastructure.yml (for example the Time and Dns steps), and reports. |
scripts/deploy/04-cluster-deployment/phase-05-cluster-deployment/Invoke-AzureLocalPreClusterVerification.ps1 | The pre-cluster verification. Read only. Checks ND-001 to ND-012 cover the nodes: WinRM, name, OS build, NTP source, DNS servers, pending restart, processors and memory, boot disk, Windows features, Secure Boot and TPM, and cluster membership. |
Run
./Invoke-AzureLocalPreClusterVerification.ps1 -InfrastructureFile ./infrastructure.yml -Mode Verify -Category nodes
Validation Checklist
| Service | Test | Expected Result | Status |
|---|---|---|---|
| DNS | AD Domain Controllers | Resolved to IPs | ☐ |
| DNS | Planned Node FQDNs | Resolved or warning (optional) | ☐ |
| NTP | Time Source | Configured and responding | ☐ |
| NTP | Time Skew | < 5 minutes | ☐ |
| Ping | OpenGear Console | Reachable | ☐ |
| Ping | Default Gateway | Reachable | ☐ |
Acceptance Criteria
- DNS resolves Active Directory domain controllers
- NTP server responds and time is synchronized (< 5 minute skew)
- OpenGear console server responds to ping
- Default gateway responds to ping
- Results documented for sign-off
Azure and Dell endpoint connectivity testing (management.azure.com, login.microsoftonline.com, dl.dell.com, etc.) will be performed in Phase 03 Step 4 after network infrastructure is configured.
Troubleshooting
| Issue | Likely Cause | Resolution |
|---|---|---|
| DNS resolution fails | Wrong DNS server configured | Verify DNS server IPs from discovery |
| AD DCs don't resolve | DNS not configured for AD zone | Work with customer DNS team |
| NTP not responding | Firewall blocking UDP 123 | Verify NTP server IP and firewall rules |
| OpenGear not reachable | Cabling or IP issue | Check NET1 connection in Step 1 |
| Gateway not reachable | VLAN or routing issue | Verify management VLAN connectivity |
Next Steps
| Step Complete? | Next Action |
|---|---|
| ✅ Yes | Proceed to Task 3: OpenGear Verification |
| ❌ No | Work with customer network team to resolve issues |
Scripts for this task are located in the azurelocal-toolkit repository under scripts/deploy/ in the appropriate task folder.
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 01: Hardware Inspection | ↑ Part 3: On-Premises Readiness | Task 03: OpenGear Verification → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-01-31 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-03 | Azure Local Cloud | Standardized runbook format |
End of Task