You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-stack/hci/manage/manage-network-atc.md
+46-8Lines changed: 46 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Manage Network ATC
3
3
description: This topic covers how to manage your Network ATC deployment.
4
4
author: jasongerend
5
5
ms.topic: how-to
6
-
ms.date: 10/01/2024
6
+
ms.date: 10/15/2024
7
7
ms.author: jgerend
8
8
zone_pivot_groups: windows-os
9
9
---
@@ -28,7 +28,17 @@ This article discusses how to manage Network ATC after it has been deployed. Net
28
28
29
29
## Add a server node
30
30
31
-
You can add nodes to a cluster. Each node in the cluster receives the same intent, improving the reliability of the cluster. The new server node must meet all requirements as listed in the Requirements and best practices section of [Host networking with Network ATC](../deploy/network-atc.md).
31
+
:::zone pivot="azure-stack-hci"
32
+
33
+
You can add nodes to a cluster. Each node in the cluster receives the same intent, improving the reliability of the cluster. The new server node must meet all requirements as listed in the Requirements and best practices section of [Host networking with Network ATC](../deploy/network-atc.md?pivots=azure-stack-hci).
34
+
35
+
::: zone-end
36
+
37
+
:::zone pivot="windows-server"
38
+
39
+
You can add nodes to a cluster. Each node in the cluster receives the same intent, improving the reliability of the cluster. The new server node must meet all requirements as listed in the Requirements and best practices section of [Host networking with Network ATC](../deploy/network-atc.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking).
40
+
41
+
::: zone-end
32
42
33
43
In this task, you add additional nodes to the cluster and observe how a consistent networking configuration is enforced across all nodes in the cluster.
The 'clusterOverride' variable has the following properties:
270
+
The 'clusterOverride' variable has the following properties:
261
271
262
272
:::image type="content" source="media/manage-network-atc/cluster-override.png" alt-text="Screenshot of Cluster Override Object." lightbox="media/manage-network-atc/cluster-override.png":::
263
273
@@ -297,7 +307,7 @@ AutoDetect: AutoDetect is a true or false parameter that dictates if Web Proxy A
297
307
298
308
AutoConfigUrl: The AutoConfigUrl parameter takes a string with the URL of the proxy server to use for http and/or https traffic as input. For both traffic classes, use a semi-colon to separate. This is a required parameter.
299
309
300
-
AutoDetect: Similar to the AutoDetect parameter above, this is a true or false parameter that dictates if Web Proxy Auto-Discovery (WPAD) should be enabled.
310
+
AutoDetect: Similar to the AutoDetect parameter above, this is a true or false parameter that dictates if Web Proxy Auto-Discovery (WPAD) should be enabled.
301
311
302
312
##### Setting-up proxy
303
313
@@ -460,14 +470,30 @@ The tasks to complete following a Network ATC deployment is depending on the Azu
460
470
461
471
-**Stretched cluster configuration:** To add Stretch S2D to your Network ATC managed system you must manually add the appropriate configuration (including vNICs, etc.) after Network ATC has implemented the specified intent.
462
472
463
-
Automatic IP Addressing for Storage Adapters, SMB Bandwidth Limits, and Stretch configurations can now be deployed with Network ATC in Azure Stack HCI 22H2. For more information, please see:
473
+
:::zone pivot="azure-stack-hci"
474
+
475
+
Automatic IP Addressing for Storage Adapters, SMB Bandwidth Limits, and Stretch configurations can now be deployed with Network ATC in Azure Stack HCI 22H2. For more information, please see:
464
476
465
-
-**Automatic Storage IP Addressing**: [Automatic Storage IP Addressing with Network ATC](../deploy/network-atc.md#automatic-storage-ip-addressing)
477
+
-**Automatic Storage IP Addressing**: [Automatic Storage IP Addressing with Network ATC](../deploy/network-atc.md?pivots=azure-stack-hci#automatic-storage-ip-addressing)
466
478
467
-
-**Cluster Network Settings and SMB Configuration**: [Automatic Storage IP Addressing with Network ATC](../deploy/network-atc.md#cluster-network-settings)
479
+
-**Cluster Network Settings and SMB Configuration**: [Automatic Storage IP Addressing with Network ATC](../deploy/network-atc.md?pivots=azure-stack-hci#cluster-network-settings)
468
480
469
481
-**Stretch cluster configuration**: [Set-up Stretch Clustering with Network ATC](../deploy/create-cluster-powershell.md#step-54-set-up-stretch-clustering-with-network-atc)
470
482
483
+
::: zone-end
484
+
485
+
:::zone pivot="windows-server"
486
+
487
+
Automatic IP Addressing for Storage Adapters, SMB Bandwidth Limits, and Stretch configurations can now be deployed with Network ATC in Azure Stack HCI 22H2. For more information, please see:
488
+
489
+
-**Automatic Storage IP Addressing**: [Automatic Storage IP Addressing with Network ATC](../deploy/network-atc.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking#automatic-storage-ip-addressing)
490
+
491
+
-**Cluster Network Settings and SMB Configuration**: [Automatic Storage IP Addressing with Network ATC](../deploy/network-atc.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking#cluster-network-settings)
492
+
493
+
-**Stretch cluster configuration**: [Set-up Stretch Clustering with Network ATC](../deploy/create-cluster-powershell.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking#step-54-set-up-stretch-clustering-with-network-atc)
494
+
495
+
::: zone-end
496
+
471
497
## Validate automatic remediation
472
498
473
499
Network ATC ensures that the deployed configuration stays the same across all cluster nodes. In this optional section, we modify our configuration (without an override) emulating an accidental configuration change and observe how the reliability of the system is improved by remediating the misconfigured property.
@@ -512,6 +538,18 @@ For more validation examples, see the [Network ATC demo](https://youtu.be/Z8UO6E
512
538
513
539
## Next steps
514
540
515
-
- Learn more about [Network ATC](../concepts/network-atc-overview.md).
541
+
:::zone pivot="azure-stack-hci"
542
+
543
+
- Learn more about [Network ATC](../concepts/network-atc-overview.md?pivots=azure-stack-hci).
516
544
- Understand Network ATC in more detail by taking a look at some [Frequently Asked Questions](network-atc-faq.md)
517
545
- Learn more about [Stretched clusters](../concepts/stretched-clusters.md).
546
+
547
+
::: zone-end
548
+
549
+
:::zone pivot="windows-server"
550
+
551
+
- Learn more about [Network ATC](../concepts/network-atc-overview.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking).
552
+
- Understand Network ATC in more detail by taking a look at some [Frequently Asked Questions](network-atc-faq.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking)
553
+
- Learn more about [Stretched clusters](../concepts/stretched-clusters.md?pivots=windows-server&context=/windows-server/context/windows-server-edge-networking).
0 commit comments