Azure Local Network ATC ProvisioningFailed on storage network after node power failure

Ian Maddox 5 Reputation points
2025-08-20T10:11:01.0433333+00:00

We have a 2 node Azure Local Cluster. A power cut knocked out 1 node (UPS was overloaded).

The cluster is now running ok again on both nodes but we are getting a NetworkAtc ProvisioningFailed error for the storage network on the surviving node.

I have tried running Set-NetIntentRetryState but it has not fixed the issue.

Does this need a node reboot or does anyone have any other suggestions?

Azure Local
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Satish Mada 350 Reputation points Microsoft External Staff Moderator
    2025-08-20T11:57:01.4366667+00:00

    Hi Ian Maddox,

    Welcome to the Azure Q&A portal.

    This error typically means that Network ATC failed to apply the storage intent due to a configuration inconsistency or a blocked provisioning state.

    To troubleshoot the NetworkAtc ProvisioningFailed error on your Azure Local Cluster, consider the following steps:

    1.Check the Cluster State

    • Ensure both nodes are in a healthy state and check the network configuration using PowerShell:
          Get-ClusterNode | Get-ClusterResource
      

    2.Validate Network Configuration

    • Make sure that the virtual switch and the network adapter settings are correct. Check if the storage network is configured correctly on both nodes:
          Get-NetAdapter | Where-Object {$_.Status -eq 'Up'}
      

    3.Assign Retry State Again

    • As you have already tried Set-NetIntentRetryState, ensure you use the correct parameters:
        Set-NetIntentRetryState -NodeName "YourNodeName" -RetryState 0
        
      
      • This can help reset the provisioning state.

    4.Check Storage Connectivity

    • Confirm that the storage is accessible from both nodes.
          Test-Path \<StoragePath>
      
      Use:Replace <StoragePath> with your actual storage path.

    5.Consider Node Reboot

    • If the above steps don’t resolve the issue, a node reboot may be necessary as it can reset the network drivers and refresh settings.
          Restart-Computer -ComputerName "YourNodeName" -Force
      

    6.Check Logs for Errors

    • Look into the Event Viewer logs (Applications and Services Logs > Microsoft > Windows > FailoverClustering > Operational) for more specific error messages related to networking or storage that might illuminate the problem.

    Please refer https://docs.azure.cn/en-us/azure-local/manage/cluster-powershell


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.