Author: blueflashylights

Introduction

Network ATC is an intent-based approach to network configuration that was introduced with Azure Stack HCI OS (21H2) and is the preferred network configuration method to use when deploying your Azure Stack HCI cluster.

Network ATC assists with the following:

• Reduce overall network configuration deployment time, complexity, and reduce human errors due to erroneous input
• Deploy the latest Microsoft validated and supported network configuration best practices
• Ensure configuration consistency across the nodes in the cluster
• Eliminate configuration drift with periodic checks every 15 minutes
  
  For more information, please see:
  Network ATC Overview – Azure Stack HCI | Microsoft Learn
  Deploy Network ATC – Azure Stack HCI | Microsoft Learn
  Manage Network ATC – Azure Stack HCI | Microsoft Learn

Whether you are wanting to deploy a Non-Converged, Fully Converged, or Switchless network topology for your Azure Stack HCI cluster, Network ATC can be leveraged.

The following sections will help guide you through an Azure Stack HCI network deployment leveraging Network ATC while covering some of the parameters and configuration overrides you may need depending on your environment.

Continue reading “Network ATC – Overview”

Environment Details
OS: Azure Stack HCI (22H2)
Network Configuration: NetworkATC
Network Topology: Non-Converged

Recently encountered the following error while attempting to perform live migration of VMs in my cluster:

Live migration of 'Virtual Machine vm-base-A0640R33C02N01-001' failed.

Failed to get the network address for the destination node 'A0640R33C02N02': A cluster network is not available for this operation. (0x000013AB).

For some reason, valid cluster networks were excluded for migration. I was able to validate this running the following command:

$clusterResourceType = Get-ClusterResourceType -Name 'Virtual Machine'
Get-ClusterParameter -InputObject $clusterResourceType

This returned the following which explained why the VMs were unable to live migrate:

Object          Name                          Value
------          ----                          -----
Virtual Machine MigrationExcludeNetworks      b7afa7a2-ff32-4f8c-9a33-a5660c632e2b;00C578DA-B7C3-422F-9C58-CDE3757DE984;CBD466D2-3E53-4793-B3F0-460964E7B56A
Virtual Machine MigrationNetworkOrder         
Virtual Machine MoveTypeThreshold             1000
Virtual Machine ReportNetworkFailure          1
Virtual Machine MaxClusterShutdownTimeout     4294967295
Virtual Machine SkipMigrationDestinationCheck 0

I removed the valid networks from the migration exclusion and then set my migration network order accordingly:

Object          Name                          Value
------          ----                          -----
Virtual Machine MigrationExcludeNetworks      b7afa7a2-ff32-4f8c-9a33-a5660c632e2b
Virtual Machine MigrationNetworkOrder         00C578DA-B7C3-422F-9C58-CDE3757DE984;CBD466D2-3E53-4793-B3F0-460964E7B56A
Virtual Machine MoveTypeThreshold             1000
Virtual Machine ReportNetworkFailure          1
Virtual Machine MaxClusterShutdownTimeout     4294967295
Virtual Machine SkipMigrationDestinationCheck 0