Task 09 — Post-Deployment Verification
DOCUMENT CATEGORY: Implementation Runbook — Task
SCOPE: Azure Local cluster — all Phase 06 tasks
PURPOSE: Confirm all Phase 06 post-deployment configuration tasks completed successfully before proceeding to operational foundations MASTER REFERENCE: Azure Local Deployment Validation
Status: Active
Verify that all Phase 06 tasks completed successfully. This task must pass before the cluster is handed off for operational foundations work.
Prerequisites:
- Tasks 01–07 complete
- Administrative access to cluster and management server
- Azure credentials with Reader access to the cluster resource group
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.
Verification Checklist
| Task | Check | Expected |
|---|---|---|
| 02 | Quorum type configured | CloudWitness or FileShareWitness |
| 02 | Quorum state | Normal |
| 03 | Admin AD group in Administrators on all nodes | Present |
| 03 | Operator AD group in Remote Management Users on all nodes | Present |
| 04 | sshd service running on all nodes | Running |
| 04 | Port 22 reachable on all nodes | TcpTestSucceeded : True |
| 05 | Storage pool health (S2D) | Healthy |
| 05 | CSV volumes mounted and online | Count matches design |
| 05 | SAN LUN health (SAN only, FC or iSCSI) | Healthy for all SAN disks |
| 05 | MPIO path count (SAN only) | ≥2 paths per LUN |
| 05 | UniqueId of SAN disks identical on every node (SAN only) | Same set on all nodes |
| 10 | Hybrid only: MSDSM IDs registered, Test-Cluster -Include Storage passes, SAN storage paths registered | See Task 10 |
| All | Get-SolutionHealthSummary (new in 2610) shows no critical or important health issues; for SAN clusters collect the SANDiagnostics log role if a storage check fails | Summary clean |
| 06 | VM images in Azure | Provisioning state Succeeded |
| 07 | Logical networks in Azure | Provisioning state Succeeded |
Verify Phase 06
- Manual Checklist
- Orchestrated Script
- Azure CLI
When to use: Step-by-step verification from the portal or console. Use when confirming individual tasks after they complete or when CLI/PSRemoting access is unavailable.
Task 02 — Cluster Quorum
On a cluster node, run:
Get-ClusterQuorum | Format-List Cluster, QuorumResource, QuorumType
Confirm a witness is set (CloudWitness or FileShareWitness). The script on the other tab also checks that the quorum state is Normal.
Task 03 — Security Groups
On each cluster node, run:
Get-LocalGroupMember -Group "Administrators" | Where-Object ObjectClass -eq "Group"
Get-LocalGroupMember -Group "Remote Management Users" | Where-Object ObjectClass -eq "Group"
Each should return at least one AD group entry.
Task 04 — SSH Connectivity
From the management server:
Test-NetConnection -ComputerName iic-01-n01 -Port 22
Test-NetConnection -ComputerName iic-01-n02 -Port 22
Expected: TcpTestSucceeded : True for all nodes.
Task 05 — Storage
S2D deployments:
- On a cluster node, run
Get-ClusterSharedVolumeandGet-VirtualDisk— confirm all CSV volumes are Online and Healthy - In Azure Portal → Azure Local →
iic-clus01→ Storage paths — confirm all show Succeeded
SAN deployments:
- Verify FC disk health:
Get-PhysicalDisk | Where-Object BusType -eq 'Fibre Channel'— allHealthStatus = Healthy - Verify MPIO paths:
mpclaim -s -d— ≥2 paths per workload LUN - Confirm CSVs are
Online:Get-ClusterSharedVolume - In Azure Portal — confirm Azure storage paths show
Succeeded
Task 06 — VM Images
In Azure Portal → Azure Local → iic-clus01 → VM images — confirm all required images
show provisioning state Succeeded.
Task 08 — Logical Networks
In Azure Portal → Azure Local → iic-clus01 → Logical networks — confirm all required
logical networks show provisioning state Succeeded and VLAN IDs match the site network plan.
PowerShell
When to use: Verify the deployed instance from a management workstation. The script is read only.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-06-post-deployment/task-09-post-deployment-verification/powershell/Invoke-VerifyPostDeployment.ps1 | Verifies a deployed Azure Local instance against infrastructure.yml. Read only. Supports -WhatIf (lists the checks and runs none). |
It checks, in this order:
- Cluster nodes: every node of
nodes[]is a cluster node and its state is Up. - Identity: with
scenario.identityactive_directory, every node is joined toidentity.active_directory.domain_fqdnand its secure channel works. Withlocal_identity, every node is in a workgroup and the cluster name resource hasADAware2. - Quorum: a quorum type is set and the quorum state is Normal. The deployment creates the witness from
cluster.witness. - Security groups: each node has at least one group in Administrators and in Remote Management Users (from
identity.active_directory.security_groups[].local_groups). Active Directory only. - SSH: sshd runs on each node and TCP 22 answers.
- Storage: a non-primordial storage pool is healthy, at least one cluster shared volume exists and every one is Online.
- VM images in Azure: the number of images that Succeeded is not below the number in
storage.vm_images[]. - Logical networks in Azure: the number that Succeeded is not below the number in
networking.logical_networks[].
The login is -Credential, else the account the file names: the LCM user (identity.active_directory.lcm_user) with Active Directory, the local administrator (identity.local_admin) with local identity. The password is a secret reference. The script never prompts: with neither it stops with exit code 2. Exit codes: 0 every check passed; 1 a check failed; 2 a value in the file is missing or there is no login.
Invoke-PostDeploymentVerification-Orchestrated.ps1 in the task folder is a placeholder (exit code 3). The Azure CLI tab has a script for the checks that read Azure.
Requires: PowerShell 7; modules FailoverClusters, Storage; the Azure CLI, signed in, for checks 7 and 8.
Run
./Invoke-VerifyPostDeployment.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Invoke-VerifyPostDeployment.ps1 -InfrastructureFile ./infrastructure.yml
./Invoke-VerifyPostDeployment.ps1 -InfrastructureFile ./infrastructure.yml -TargetNode iic-azl-n01
Azure CLI
When to use: Check the task from a host that has the Azure CLI and not the Az PowerShell modules. The script is PowerShell 7 that calls
azand only reads Azure.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-06-post-deployment/task-09-post-deployment-verification/azurecli/Invoke-VerifyPostDeployment.azcli.ps1 | Verifies the Azure side of a deployed Azure Local instance against infrastructure.yml with the Azure CLI. Read only. Supports -WhatIf (lists the checks and runs none). |
Requires: PowerShell 7 and the Azure CLI, signed in with az login --tenant <azure.tenant_id>. Needs the Azure CLI extensions connectedmachine, stack-hci, stack-hci-vm, customlocation (az extension add --name connectedmachine, az extension add --name stack-hci, az extension add --name stack-hci-vm, az extension add --name customlocation); the script does not install them.
It checks the Arc machines and their extensions (including WindowsOpenSSH), the instance, the custom location, the cloud witness account, and that the numbers of storage paths, VM images, logical networks and network security groups in Azure are not below the numbers in the file. It does not reach the nodes: the cluster state, domain membership, quorum, local groups, sshd, storage pool and cluster shared volumes are checked by the PowerShell script. -TargetNode limits the machine checks.
Run
./Invoke-VerifyPostDeployment.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Invoke-VerifyPostDeployment.azcli.ps1 -InfrastructureFile ./infrastructure.yml
./Invoke-VerifyPostDeployment.azcli.ps1 -InfrastructureFile ./infrastructure.yml -TargetNode <node-name>
Phase 06 Completion Criteria
All of the following must be true before proceeding to Phase 17:
- Cluster quorum configured and state is
Normal - Security groups applied to all cluster nodes (
Administrators+Remote Management Users) - SSH running on all cluster nodes, port 22 reachable
- Storage pool healthy, CSV volumes mounted and online
- Storage paths registered in Azure with provisioning state
Succeeded - VM images staged with provisioning state
Succeeded - Logical networks created for all workload VLANs, provisioning state
Succeeded - VLAN IDs validated against site network plan
- Verification script executed with zero failures
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Verification script reports failures on storage paths | Storage path registration incomplete or ARB sync pending | Re-run New-StoragePath.ps1 (it leaves existing paths alone); wait 10 minutes for sync; verify: az stack-hci-vm storagepath list |
| VLAN validation fails against network plan | Logical network VLAN IDs don't match site design | Compare az stack-hci-vm network lnet list output against site network plan; recreate mismatched logical networks |
| Multiple verification items fail simultaneously | Cluster health issue affecting dependent services | Start with Get-ClusterNode and Get-ClusterGroup to assess overall cluster health before addressing individual failures |
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
| ← Previous | Task 08 — Logical Network Creation |
| ↑ Phase Index | Phase 06 — Post-Deployment Index |
| → Next | Part 5 — Operational Foundations |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2025-03-25 | Azure Local Cloud | Initial release |