Skip to content

Commit 7f6cf9e

Browse files
committed
Updated media folder names to match .md file name.
1 parent 039ab93 commit 7f6cf9e

File tree

5 files changed

+7
-7
lines changed

5 files changed

+7
-7
lines changed

azure-stack/hci/upgrade/install-enable-network-atc.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ronmiab
55
ms.author: robess
66
ms.topic: how-to
77
ms.reviewer: alkohli
8-
ms.date: 08/14/2024
8+
ms.date: 08/19/2024
99
#Customer intent: As a Senior Content Developer, I want to provide customers with content and steps to help them successfully install and enable Network ATC on their existing Azure Stack HCI, version 22H2 cluster.
1010
---
1111

@@ -132,7 +132,7 @@ In this example, there are two intents that are managed across cluster nodes.
132132
1. **Management and compute**: This intent uses a dedicated pair of network adapter ports.
133133
2. **Storage**: This intent uses a dedicated pair of network adapter ports.
134134

135-
:::image type="content" source="media/install-and-enable-network-atc/group-management-and-compute.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped management and compute intent." lightbox="media/install-and-enable-network-atc/group-management-and-compute.png":::
135+
:::image type="content" source="media/install-enable-network-atc/group-management-and-compute.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped management and compute intent." lightbox="media/install-enable-network-atc/group-management-and-compute.png":::
136136

137137
Here's an example to implement this host network pattern:
138138

@@ -148,7 +148,7 @@ In this example, there's a single intent managed across cluster nodes.
148148
149149
- **Management, Compute, and Storage**: This intent uses a dedicated pair of network adapter ports.
150150
151-
:::image type="content" source="media/install-and-enable-network-atc/group-all-traffic.png" alt-text="Screenshot of an Azure Stack HCI cluster with all traffic on a single intent." lightbox="media/install-and-enable-network-atc/group-all-traffic.png":::
151+
:::image type="content" source="media/install-enable-network-atc/group-all-traffic.png" alt-text="Screenshot of an Azure Stack HCI cluster with all traffic on a single intent." lightbox="media/install-enable-network-atc/group-all-traffic.png":::
152152
153153
Here's an example to implement this host network pattern:
154154
@@ -163,7 +163,7 @@ In this example, there are two intents that are managed across cluster nodes.
163163
1. **Management**: This intent uses a dedicated pair of network adapter ports.
164164
2. **Compute and Storage**: This intent uses a dedicated pair of network adapter ports.
165165
166-
:::image type="content" source="media/install-and-enable-network-atc/group-compute-and-storage.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped compute and storage intent." lightbox="media/install-and-enable-network-atc/group-compute-and-storage.png":::
166+
:::image type="content" source="media/install-enable-network-atc/group-compute-and-storage.png" alt-text="Screenshot of an Azure Stack HCI cluster with a grouped compute and storage intent." lightbox="media/install-enable-network-atc/group-compute-and-storage.png":::
167167
168168
Here's an example to implement this host network pattern:
169169
@@ -181,7 +181,7 @@ In this example, there are three intents that are managed across cluster nodes.
181181
2. **Compute**: This intent uses a dedicated pair of network adapter ports.
182182
3. **Storage**: This intent uses a dedicated pair of network adapter ports.
183183
184-
:::image type="content" source="media/install-and-enable-network-atc/fully-disaggregated.png" alt-text="Screenshot of an Azure Stack HCI cluster with a fully disaggregated intent." lightbox="media/install-and-enable-network-atc/fully-disaggregated.png":::
184+
:::image type="content" source="media/install-enable-network-atc/fully-disaggregated.png" alt-text="Screenshot of an Azure Stack HCI cluster with a fully disaggregated intent." lightbox="media/install-enable-network-atc/fully-disaggregated.png":::
185185
186186
Here's an example to implement this host network pattern:
187187
@@ -233,7 +233,7 @@ If the **ConfigurationStatus** shows **Failed**, check to see if the error messa
233233

234234
In this step, you move from the node deployed with Network ATC to the next node and migrate the VMs from this second node. You must verify that the second node has the same `VMSwitch` name as the node deployed with Network ATC.
235235

236-
This is a non-disruptive change and can be done on all the nodes simultaneously. Run the following command:
236+
This is a nondisruptive change and can be done on all the nodes simultaneously. Run the following command:
237237

238238
```powershell
239239
#Run on the node where you configured Network ATC
@@ -269,4 +269,4 @@ Resume-ClusterNode
269269
270270
## Next step
271271

272-
Learn how to [Assess solution upgrade readiness for Azure Stack HCI](./validate-solution-upgrade-readiness.md).
272+
Learn how to [Assess solution upgrade readiness for Azure Stack HCI](./validate-solution-upgrade-readiness.md).

0 commit comments

Comments
 (0)