Skip to content

Commit 12162ae

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #15955 from robinharwood/roharwoo-ws-network-atc
Updating Network ATC article set for Windows Server 2025
2 parents 6420415 + 8ef3ef1 commit 12162ae

File tree

4 files changed

+526
-122
lines changed

4 files changed

+526
-122
lines changed

‎azure-stack/hci/concepts/network-atc-overview.md

Lines changed: 119 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,34 @@
11
---
22
title: Network ATC overview
3-
description: This topic introduces Network ATC for Azure Stack HCI.
4-
author: dcuomo
5-
ms.topic: how-to
6-
ms.date: 04/22/2022
3+
description: This article introduces Network ATC for Azure Stack HCI and Windows Server.
4+
author: parammahajan5
5+
ms.topic: overview
6+
ms.date: 10/15/2024
77
ms.author: jgerend
88
ms.reviewer: JasonGerend
9+
zone_pivot_groups: windows-os
910
---
1011

1112
# Network ATC overview
1213

14+
:::zone pivot="azure-stack-hci"
15+
1316
[!INCLUDE [hci-applies-to-22h2-21h2](../../includes/hci-applies-to-22h2.md)]
1417

15-
Deployment and operation of Azure Stack HCI networking can be a complex and error-prone process. Due to the configuration flexibility provided with the host networking stack, there are many moving parts that can be easily misconfigured or overlooked. Staying up to date with the latest best practices is also a challenge as improvements are continuously made to the underlying technologies. Additionally, configuration consistency across HCI cluster nodes is important as it leads to a more reliable experience.
18+
Deployment and operation of Azure Stack HCI networking can be a complex and error-prone process. Due to the configuration flexibility provided with the host networking stack, there are many moving parts that can be easily misconfigured or overlooked. Staying up to date with the latest best practices is also a challenge as improvements are continuously made to the underlying technologies. Additionally, configuration consistency across HCI cluster nodes is important as it leads to a more reliable experience. Network ATC is the complete product name and not an acronym.
19+
20+
::: zone-end
21+
22+
:::zone pivot="windows-server"
23+
24+
>Applies to: Windows Server 2025 (preview)
25+
26+
> [!IMPORTANT]
27+
> Network ATC in Windows Server 2025 is in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.
28+
29+
Deployment and operation of Windows Server cluster networking can be a complex and error-prone process. Due to the configuration flexibility provided with the host networking stack, there are many moving parts that can be easily misconfigured or overlooked. Staying up to date with the latest best practices is also a challenge as improvements are continuously made to the underlying technologies. Network ATC applies a consistency configuration across Windows Server cluster nodes to create a more reliable experience. As Network ATC is designed for Windows Server clusters, it requires Windows Server Datacenter edition and the Failover Clustering feature. Network ATC is the complete product name and not an acronym.
30+
31+
::: zone-end
1632

1733
Network ATC can help:
1834

@@ -21,34 +37,115 @@ Network ATC can help:
2137
- Ensure configuration consistency across the cluster
2238
- Eliminate configuration drift
2339

24-
## Definitions
40+
## Features
41+
42+
Network ATC provides the following features:
43+
44+
- **Windows Admin Center deployment**: Network ATC is integrated with Windows Admin Center to provide an easy-to-use experience for deploying host networking.
45+
46+
:::zone pivot="azure-stack-hci"
47+
48+
- **Network symmetry**: Network ATC configures and optimizes all adapters identically based on your configuration. Beginning with Azure Stack HCI 22H2, Network ATC also verifies the make, model, and speed of your network adapter to ensure network symmetry across all nodes of the cluster.
49+
50+
::: zone-end
51+
52+
:::zone pivot="windows-server"
53+
54+
- **Network symmetry**: Network ATC configures and optimizes all adapters identically based on your configuration. Network ATC also verifies the make, model, and speed of your network adapter to ensure network symmetry across all nodes of the cluster.
55+
56+
::: zone-end
57+
58+
- **Storage adapter configuration**: Network ATC automatically configures the following components for your storage network.
59+
60+
- Physical adapter properties
61+
62+
- Data Center Bridging
63+
64+
- Determines if a virtual switch is needed, and if so, creates the required virtual adapters
65+
66+
- Maps the virtual adapters to the appropriate physical adapter
67+
68+
- Assigns VLANs
69+
70+
:::zone pivot="azure-stack-hci"
71+
72+
- Beginning with Azure Stack HCI, version 22H2, Network ATC automatically assigns IP Addresses for storage adapters.
2573

26-
Here is some new terminology:
74+
:::zone-end
75+
76+
<br />
77+
78+
:::zone pivot="windows-server"
79+
80+
- Network ATC automatically assigns IP Addresses for storage adapters.
81+
82+
:::zone-end
83+
84+
- **Cluster network naming**: Network ATC automatically names the cluster networks based on their usage. For example, the storage network might be named _storage_compute(Storage\_VLAN711)_.
85+
86+
- **Live Migration guidelines**: Network ATC keeps you up to date with the recommended guidelines for Live Migration based on the operating system version (you can always override). Network ATC manages the following Live Migration settings:
87+
88+
- The maximum number of simultaneous live migrations
89+
90+
- The live migration network
91+
92+
- The live migration transport
93+
94+
- The maximum amount of SMBDirect (RDMA) bandwidth used for live migration
95+
96+
- **Proxy configuration**: Network ATC can help you configure all cluster nodes with the same proxy configuration information if your environment requires it
97+
98+
- **Stretch S2D cluster support**: Network ATC deploys the configuration required for [the storage replica networks](host-network-requirements.md#stretched-clusters). Since these adapters need to route across subnets, Network ATC doesn't assign any IP addresses, so you need to assign the IP address.
99+
100+
- **Scope detection**: Beginning with Azure Stack HCI 22H2, Network ATC automatically detects if you’re running the command on a cluster node. Meaning, you won’t need to use the `-ClusterName` parameter because it automatically detects the cluster that you're on.
101+
102+
To learn more about the features in Network ATC, see [Network ATC: What's coming](https://techcommunity.microsoft.com/t5/networking-blog/network-atc-what-s-coming-in-azure-stack-hci-22h2/ba-p/3598442).
103+
104+
## Terminology
105+
106+
To understand Network ATC, you need to understand some basic concepts. Here's some terminology used by Network ATC:
27107

28108
**Intent**: An intent is a definition of how you intend to use the physical adapters in your system. An intent has a friendly name, identifies one or more physical adapters, and includes one or more intent types.
29109

30-
An individual physical adapter can only be included in one intent. By default, an adapter does not have an intent (there is no special status or property given to adapters that don't have an intent). You can have multiple intents; the number of intents you have will be limited by the number of adapters in your system.
110+
An individual physical adapter can only be included in one intent. By default, an adapter doesn't have an intent (there's no special status or property given to adapters that don't have an intent). You can have multiple intents; the number of adapters in your system limits the number of intents you have.
111+
112+
**Intent type**: Every intent requires one or more intent types. Any combination of the intent types can be specified for any specific single intent. Here are the currently supported intent types and the maximum number of intents they can be defined in:
31113

32-
**Intent type**: Every intent requires one or more intent types. The currently supported intent types are:
114+
Management: Adapters are used for management access to nodes. This intent type can be defined in a maximum of one intent.
115+
Compute: Adapters are used to connect virtual machine (VM) traffic to the physical network. This intent type can be defined in unlimited intents.
116+
Storage: Adapters are used for SMB traffic, including Storage Spaces Direct. This intent type can be defined in a maximum of one intent.
117+
Stretch: Adapters are set up similarly to a storage intent, except RDMA can't be used with stretch intents. This intent type can be defined in a maximum of one intent
33118

34-
- Management - adapters are used for management access to nodes
35-
- Compute - adapters are used to connect virtual machine (VM) traffic to the physical network
36-
- Storage - adapters are used for SMB traffic including Storage Spaces Direct
37-
- Stretch - adapters are set up in a similar manner as a storage intent with the exception of RDMA not used for stretch adapters.
119+
**Override**: By default, Network ATC deploys the most common configuration, asking for the smallest amount of user input. Overrides allow you to customize your deployment if necessary. For example, you might choose to modify the VLANs used for storage adapters from the defaults.
38120

39-
Any combination of the intent types can be specified for any specific single intent. However, certain intent types can only be specified in one intent:
121+
Network ATC allows you to modify all configuration that the OS allows. However, the OS limits some modifications to the OS and Network ATC respects these limitations. For example, a virtual switch doesn't allow modification of SR-IOV after it has been deployed.
40122

41-
- Management: Can be defined in a maximum of one intent
42-
- Compute: Unlimited
43-
- Storage: Can be defined in a maximum of one intent
44-
- Stretch: Can be defined in a maximum of one intent
123+
## Deployment example
45124

46-
**Override**: By default, Network ATC deploys the most common configuration, asking for the smallest amount of user input. Overrides allow you to customize your deployment if required. For example, you may choose to modify the VLANs used for storage adapters from the defaults.
125+
The following video provides an overview of Network ATC using the [Copy-NetIntent](/powershell/module/networkatc/copy-netintent) command to copy an intent from one cluster to another. To learn more about the demonstration, see our Tech Community article [Deploying 100s of production clusters in minutes](https://techcommunity.microsoft.com/t5/networking-blog/deploying-100s-of-production-clusters-in-minutes/ba-p/3724977).<br /><br />
47126

48-
Network ATC allows you to modify all configuration that the OS allows. However, the OS limits some modifications to the OS and Network ATC respects these limitations. For example, a virtual switch does not allow modification of SR-IOV after it has been deployed.
127+
> [!VIDEO https://www.youtube.com/embed/AZBE_3LCiHQ]
49128
50129
## Next steps
51130

52-
- Review Network ATC defaults and example deployment options. See [Deploy host networking with Network ATC](../deploy/network-atc.md).
131+
To get started with Network ATC, review the following articles:
132+
133+
:::zone pivot="azure-stack-hci"
134+
135+
- Review Network ATC defaults and example deployment options. See [Deploy host networking with Network ATC](../deploy/network-atc.md?pivots=azure-stack-hci).
53136
- Configure Network ATC using PowerShell. See [Step 4: Configure host networking](../deploy/create-cluster-powershell.md#step-4-configure-host-networking).
54-
- Manage Network ATC after deployment. See [Manage host networking using Network ATC](../manage/manage-network-atc.md).
137+
- Manage Network ATC after deployment. See [Manage host networking using Network ATC](../manage/manage-network-atc.md?pivots=azure-stack-hci).
138+
- [Migrate an existing cluster to Network ATC](https://techcommunity.microsoft.com/t5/networking-blog/migrate-an-existing-cluster-to-network-atc/ba-p/3843606).
139+
- To learn more about the latest networking announcements, build your skills, and connect with the Microsoft Edge Networking community, see the [Tech Community Networking Blog](https://techcommunity.microsoft.com/t5/networking-blog/bg-p/NetworkingBlog).
140+
141+
::: zone-end
142+
143+
:::zone pivot="windows-server"
144+
145+
- Review Network ATC defaults and example deployment options. See [Deploy host networking with Network ATC](../deploy/network-atc.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking).
146+
- Configure Network ATC using PowerShell. See [Step 4: Configure host networking](../deploy/create-cluster-powershell.md?context=/windows-server/context/windows-server-edge-networking#step-4-configure-host-networking).
147+
- Manage Network ATC after deployment. See [Manage host networking using Network ATC](../manage/manage-network-atc.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking).
148+
- [Migrate an existing cluster to Network ATC](https://techcommunity.microsoft.com/t5/networking-blog/migrate-an-existing-cluster-to-network-atc/ba-p/3843606).
149+
- To learn more about the latest networking announcements, build your skills, and connect with the Microsoft Edge Networking community, see the [Tech Community Networking Blog](https://techcommunity.microsoft.com/t5/networking-blog/bg-p/NetworkingBlog).
150+
151+
::: zone-end

0 commit comments

Comments
 (0)