Merge pull request #17955 from v-sissondan/switchless-cristian

Switchless scale out updates - Cristian

Author: denrea

azure-local/includes/switchless-scale-out.md

@@ -0,0 +1,12 @@
+---
+author: alkohli
+ms.author: alkohli
+ms.service: azure-local
+ms.topic: include
+ms.date: 05/15/2025
+ms.reviewer: alkohli
+ms.lastreviewed: 05/15/2025
+---
+
+> [!NOTE]
+> Remember that scale out operations aren't supported on Azure Local deployments with switchless storage. To add an additional node, redeploy the cluster as you need to reconfigure the storage physical connectivity and the storage networks.

azure-local/plan/four-node-switchless-two-switches-two-links.md

@@ -7,7 +7,7 @@ ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
 ms.custom: devx-track-arm-template
-ms.date: 02/14/2025
+ms.date: 05/15/2025
 ---
 
 # Review four-node storage switchless, dual TOR, dual link deployment network reference pattern for Azure Local
@@ -25,6 +25,8 @@ Scenarios for this network pattern include laboratories, factories, branch offic
 
 Consider implementing this pattern when looking for a cost-efficient solution that has fault tolerance across all the network components.
 
+[!INCLUDE [includes](../includes/switchless-scale-out.md)]
+
 SDN L3 services are fully supported on this pattern. Routing services such as Border Gateway Protocol (BGP) can be configured directly on the TOR switches if they support L3 services. Network security features such as micro segmentation or QoS don't require extra configuration of the firewall device, as they're implemented at virtual network adapter layer.
 
 :::image type="content" source="./media/four-node-switchless-two-switches-two-links/four-node-switchless-components-layout.png" alt-text="Diagram showing four-node switchless, two TOR, two link physical connectivity layout." lightbox="./media/four-node-switchless-two-switches-two-links/four-node-switchless-components-layout.png":::
@@ -306,4 +308,4 @@ You can use the [ARM template for four-node storage switchless, dual TOR and dua
             }
             ]
         },
-```
+```

azure-local/plan/three-node-switchless-two-switches-single-link.md

@@ -7,7 +7,7 @@ ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
 ms.custom: devx-track-arm-template
-ms.date: 02/14/2025
+ms.date: 05/15/2025
 ---
 
 # Review three-node storage switchless, dual TOR, single link deployment network reference pattern for Azure Local
@@ -17,25 +17,27 @@ ms.date: 02/14/2025
 In this article, learn about the three-node storage switchless with two TOR L3 switches and full-mesh single link network reference pattern that you can use to deploy your Azure Local solution.
 
 > [!NOTE]
-> The 3-node switchless network reference patterns described in this article were tested and validated by Microsoft. For information on two-node switchless network patterns, see [Azure Local network deployment patterns](choose-network-pattern.md).
+> The three-node switchless network reference patterns described in this article were tested and validated by Microsoft. For information on two-node switchless network patterns, see [Azure Local network deployment patterns](choose-network-pattern.md).
 
 ## Scenarios
 
 Scenarios for this network pattern include laboratories, factories, retail stores, public sectors, and government.
 
 Consider implementing this pattern when looking for a cost-efficient solution that has fault tolerance across all the network components. Software Defined Network (SDN) L3 services are fully supported on this pattern. Routing services such as Border Gateway Protocol (BGP) can be configured directly on the TOR switches if they support L3 services. Network security features such as micro segmentation or Quality of Service (QoS) don't require extra configuration of the firewall device, as they're implemented at virtual network adapter layer.
 
+[!INCLUDE [includes](../includes/switchless-scale-out.md)]
+
 ## Physical connectivity components
 
 :::image type="content" source="media/three-node-switchless-two-switches-single-link/physical-components-layout.png" alt-text="Diagram showing three-node switchless, two TOR, single link physical connectivity layout." lightbox="media/three-node-switchless-two-switches-single-link/physical-components-layout.png":::
 
-As illustrated in the diagram above, this pattern has the following physical network components:
+As illustrated in the diagram, this pattern has the following physical network components:
 
 - For northbound and southbound communication, the Azure Local instance requires two TOR switches in multi-chassis link aggregation group (MLAG) configuration.
 - Two network cards using SET virtual switch to handle management and compute traffic, connected to the TOR switches. Each NIC is connected to a different TOR.
 - Two RDMA NICs on each node in a full-mesh single link configuration for East-West traffic for the storage.
     > [!NOTE]
-    > For this configuration, there is no redundant network connection between the nodes.
+    > For this configuration, there's no redundant network connection between the nodes.
 
 |Networks|Management and compute|Storage|
 |--|--|--|
@@ -45,7 +47,7 @@ As illustrated in the diagram above, this pattern has the following physical net
 
 ## Logical networks
 
-As illustrated in the diagram below, this pattern has the following logical network components:
+As illustrated in the diagram, this pattern has the following logical network components:
 
 :::image type="content" source="media/three-node-switchless-two-switches-single-link/logical-components-layout.png" alt-text="Diagram showing three-node switchless, two TOR, single link logical connectivity layout." lightbox="media/three-node-switchless-two-switches-single-link/logical-components-layout.png":::
 
@@ -59,7 +61,7 @@ When deploying a three-node switchless configuration, Network ATC has the follow
 
 - Only supports a single VLAN for all the IP subnets used for storage connectivity.
 
-- `StorageAutoIP` parameter must be set to false, `Switchless` parameter must be set to true,  and you are responsible to specify the IPs on the ARM template used to deploy the Azure Local instance from Azure.
+- `StorageAutoIP` parameter must be set to false, `Switchless` parameter must be set to true,  and your'e responsible to specify the IPs on the ARM template used to deploy the Azure Local instance from Azure.
 
 - For Azure Local cloud deployments:
 
@@ -132,7 +134,7 @@ For more information, see [Deploy host networking with Network ATC](../deploy/ne
 
 ## ARM template Storage intent network configuration example
 
-You can use the [ARM template for 3-node storage switchless, dual TOR and single link](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.azurestackhci/create-cluster-3Nodes-Switchless-SingleLink).
+You can use the [ARM template for three-node storage switchless, dual TOR and single link](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.azurestackhci/create-cluster-3Nodes-Switchless-SingleLink).
 
 Here's a snippet from the template:
 
@@ -185,4 +187,4 @@ Here's a snippet from the template:
             }
         ]
       },
-```
+```

azure-local/plan/three-node-switchless-two-switches-two-links.md

@@ -7,7 +7,7 @@ ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
 ms.custom: devx-track-arm-template
-ms.date: 02/14/2025
+ms.date: 05/15/2025
 ---
 
 # Review three-node storage switchless, dual TOR, dual link deployment network reference pattern for Azure Local
@@ -25,6 +25,8 @@ Scenarios for this network pattern include laboratories, factories, branch offic
 
 Consider implementing this pattern when looking for a cost-efficient solution that has fault tolerance across all the network components. SDN L3 services are fully supported on this pattern. Routing services such as Border Gateway Protocol (BGP) can be configured directly on the TOR switches if they support L3 services. Network security features such as micro segmentation or QoS don't require extra configuration of the firewall device, as they're implemented at virtual network adapter layer.
 
+[!INCLUDE [includes](../includes/switchless-scale-out.md)]
+
 ## Physical connectivity components
 
 :::image type="content" source="media/three-node-switchless-two-switches-dual-link/physical-components-layout.png" alt-text="Diagram showing three-node switchless, two TOR, two link physical connectivity layout." lightbox="media/three-node-switchless-two-switches-dual-link/physical-components-layout.png":::
@@ -59,7 +61,7 @@ When deploying three nodes in a switchless configuration, Network ATC has the fo
 
 - Only supports a single VLAN for all the IP subnets used for storage connectivity.
 
-- `StorageAutoIP` parameter must be set to false, `Switchless` parameter must be set to true, and you are responsible to specify the IPs on the ARM template used to deploy the Azure Local instance from Azure.
+- Set `StorageAutoIP` parameter to false and `Switchless` parameter to true. Specify the IPs on the ARM template used to deploy the Azure Local instance from Azure.
 
 - For Azure Local cloud deployments:
 
@@ -230,4 +232,4 @@ You can use the [ARM template for 3-node storage switchless, dual TOR and dual l
         }
         ]
       },
-```
+```

azure-local/plan/two-node-switchless-single-switch.md

@@ -6,7 +6,7 @@ author: alkohli
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
-ms.date: 02/14/2025
+ms.date: 05/15/2025
 ---
 
 # Review two-node storage switchless, single switch deployment network reference pattern for Azure Local
@@ -23,7 +23,7 @@ Scenarios for this network pattern include laboratories, factories, retail store
 
 Consider this pattern for a cost-effective solution that includes fault-tolerance at the system level, but can tolerate northbound connectivity interruptions if the single physical switch fails or requires maintenance.
 
-You can scale out this pattern, but it requires workload downtime to reconfigure storage physical connectivity and storage network reconfiguration. Although SDN L3 services are fully supported for this pattern, the routing services such as BGP must be configured on the firewall device on top of the TOR switch if it doesn't support L3 services. Network security features such as microsegmentation and QoS don't require extra configuration on the firewall device, as they're implemented on the virtual switch.
+[!INCLUDE [includes](../includes/switchless-scale-out.md)]
 
 ## Physical connectivity components
 

azure-local/plan/two-node-switchless-two-switches.md

@@ -6,7 +6,7 @@ author: alkohli
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
-ms.date: 02/14/2025
+ms.date: 05/15/2025
 ---
 
 # Review two-node storage switchless, two switches deployment network reference pattern for Azure Local
@@ -21,7 +21,9 @@ For information on other network patterns, see [Azure Local network deployment p
 
 Scenarios for this network pattern include laboratories, branch offices, and datacenter facilities.
 
-Consider implementing this pattern when looking for a cost-efficient solution that has fault tolerance across all the network components. It's possible to scale out the pattern, but requires workload downtime to reconfigure storage physical connectivity and storage network reconfiguration. SDN L3 services are fully supported on this pattern. Routing services such as BGP can be configured directly on the TOR switches if they support L3 services. Network security features such as micro-segmentation and QoS don't require extra configuration for the firewall device as they're implemented at the virtual network adapter layer.
+Consider implementing this pattern when looking for a cost-efficient solution that has fault tolerance across all the network components.
+
+[!INCLUDE [includes](../includes/switchless-scale-out.md)]
 
 ## Physical connectivity components