Merge pull request #15325 from CristianEdwards/HCINetworkPatternsUpdates

Updates to Network Patterns Content

Author: v-dirichards

azure-stack/hci/plan/choose-network-pattern.md

@@ -13,7 +13,7 @@ ms.date: 03/14/2024
 
 [!INCLUDE [includes](../../includes/hci-applies-to-23h2-22h2.md)]
 
-This article describes a set of network patterns references to architect, deploy, and configure Azure Stack HCI using either one or two physical hosts. Depending on your needs or scenarios, you can go directly to your pattern of interest. Each pattern is described as a standalone entity and includes all the network components for specific scenarios.
+This article describes a set of network patterns references to architect, deploy, and configure Azure Stack HCI using either one, two or three physical hosts. Depending on your needs or scenarios, you can go directly to your pattern of interest. Each pattern is described as a standalone entity and includes all the network components for specific scenarios.
 
 ## Choose a network reference pattern
 
@@ -35,6 +35,19 @@ Use the following table to directly go to a pattern and its content.
 |---------|---------|
 |:::image type="content" source="media/plan-deployment/two-node-switched-non-converged.png" alt-text="Diagram showing two-node storage switched, non-converged, two TOR switches" lightbox="media/plan-deployment/two-node-switched-non-converged.png":::|:::image type="content" source="media/plan-deployment/two-node-switched-converged.png" alt-text="Diagram showing two-node storage switched, fully converged, two TOR switches." lightbox="media/plan-deployment/two-node-switched-converged.png":::|
 
+### Three-node switchless single link
+
+**Go to [Three-node switchless single link deployment](three-node-switchless-two-switches-single-link.md)**
+
+:::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":::
+
+### Three-node switchless dual link
+
+**Go to [Three-node switchless dual link deployment](three-node-switchless-two-switches-two-links.md)**
+
+:::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":::
+
+
 ## Next steps
 
 - [Download Azure Stack HCI](../deploy/download-azure-stack-hci-software.md)

azure-stack/hci/plan/network-patterns-overview.md

@@ -14,52 +14,46 @@ ms.date: 03/14/2024
 
 [!INCLUDE [includes](../../includes/hci-applies-to-23h2-22h2.md)]
 
-In this article, you'll gain an overview understanding for deploying network reference patterns on Azure Stack HCI.
+In this article, gain an overview understanding for deploying network reference patterns on Azure Stack HCI.
 
-A deployment consists of single-server or two-node systems that connect to one or two Top of Rack (TOR) switches. This environment has the following characteristics:
+A deployment consists of single-server or multiple server systems (up to 16 servers per cluster) that connect to one or two Top of Rack (TOR) switches. Those environments have the following characteristics:
 
-- Two storage ports dedicated for storage traffic intent. The RDMA NIC is optional for single-server deployments.
+- At least two network adapters dedicated for storage traffic intent. The only exception to this rule is single-server deployments, where network adapters for storage aren't required if you aren't planning to scale out the cluster in the future.
 
-- One or two ports dedicated to management and compute traffic intents.
+- One or two network adapter dedicated to management and compute traffic intents.
 
-- One optional Baseboard Management Controller (BMC) for OOB management.
+## Storage switchless connectivity considerations
 
-A single-server deployment features a single TOR switch for northbound/southbound (internal-external) traffic. Two-node deployments consist of either a storage switchless configuration using one or two TOR switches; or a storage switched configuration using two TOR switches with either non-converged or fully converged host network adapters.
+The following highlights some considerations of using switchless configurations:
 
-## Switchless advantages and disadvantages
+- Storage switchless deployments in Azure Stack HCI 23H2 only support 1,2 or 3 nodes.
 
-The following highlights some advantages and disadvantages of using switchless configurations:
+- Scale out operations on storage switchless deployments from Azure portal or ARM aren't supported in Azure Stack HCI 23H2 clusters.  
 
-- No switch is necessary for in-cluster (East-West) traffic; however, a switch is required for traffic outside the cluster (North-South). This may result in lower capital expenditure (CAPEX) costs, but is dependent on the number of nodes in the cluster.
+- No switch is necessary for in-cluster (East-West) traffic; however, a physical switch is required for traffic outside the cluster (North-South).
 
-- If switchless is used, configuration is limited to the host, which may reduce the potential number of configuration steps needed. However, this value diminishes as the cluster size increases.
+- Network ATC doesn't support storage network autoIP on 3 nodes switchless deployments. Planning is required for IP and subnet addressing schemes.
 
-- Switchless has the lowest level of resiliency, and it comes with extra complexity and planning if after the initial deployment it needs to be scaled up. Storage connectivity needs to be enabled when adding the second node, which will require to define what physical connectivity between nodes is needed.
-
-- More planning is required for IP and subnet addressing schemes.
-
-- Storage adapters are single-purpose interfaces. Management, compute, stretched cluster, and other traffic requiring North-South communication can't use these adapters.
+- Storage adapters are single-purpose interfaces. Management, compute, stretched cluster, and other traffic requiring North-South communication can't use the storage network adapters.
 
 - As the number of nodes in the cluster grows beyond two nodes, the cost of network adapters could exceed the cost of using network switches.
 
 - Beyond a three-node cluster, cable management complexity grows.
 
-- Cluster expansion beyond two-nodes is complex, potentially requiring per-node hardware and software configuration changes.
-
 For more information, see [Physical network requirements for Azure Stack HCI](../concepts/physical-network-requirements.md).
 
 ## Firewall requirements
 
 Azure Stack HCI requires periodic connectivity to Azure. If your organization's outbound firewall is restricted, you would need to include firewall requirements for outbound endpoints and internal rules and ports. There are required and recommended endpoints for the Azure Stack HCI core components, which include cluster creation, registration and billing, Microsoft Update, and cloud cluster witness.
 
-See the [firewall requirements](/azure-stack/hci/concepts/firewall-requirements?tabs=allow-table) for a complete list of endpoints. Make sure to include these URLS in your allowed list. Proper network ports need to be opened between all server nodes both within a site and between sites (for stretched clusters).
+See the [firewall requirements](/azure-stack/hci/concepts/firewall-requirements?tabs=allow-table) for a complete list of endpoints. Make sure to include these required URLS in your allowed list. Proper network ports need to be opened between all server nodes both within a site and between sites (for stretched clusters).
 
-With Azure Stack HCI the connectivity validator of the [Environment Checker](https://www.powershellgallery.com/packages/AzStackHci.EnvironmentChecker/0.2.3-preview) tool will check for the outbound connectivity requirement by default during deployment. Additionally, you can run the Environment Checker tool standalone before, during, or after deployment to evaluate the outbound connectivity of your environment.
+Azure Stack HCI connectivity validator of the [Environment Checker](https://www.powershellgallery.com/packages/AzStackHci.EnvironmentChecker/0.2.3-preview) tool, checks for the outbound connectivity requirement by default during deployment. Additionally, you can run the Environment Checker tool standalone before, during, or after deployment to evaluate the outbound connectivity of your environment.
 
 A best practice is to have all relevant endpoints in a data file that can be accessed by the environment checker tool. The same file can also be shared with your firewall administrator to open up the necessary ports and URLs.
 
 For more information, see [Firewall requirements](/azure-stack/hci/concepts/firewall-requirements?tabs=allow-table).
 
 ## Next steps
 
-- [Choose a network pattern ](choose-network-pattern.md) to review.
+- [Choose a network pattern ](choose-network-pattern.md) to review.