Skip to content

Commit d4aaf3d

Browse files
committed
More changes
1 parent aee762c commit d4aaf3d

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

azure-local/plan/choose-network-pattern.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,4 +49,4 @@ Use the following table to directly go to a pattern and its content.
4949

5050
## Next steps
5151

52-
- [Download Azure Local](../deploy/download-software.md)
52+
- [Download Azure Local](../deploy/download-software.md).

azure-local/plan/cloud-deployment-network-considerations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The following diagram shows the various decisions and steps that define the netw
2626

2727
To help determine the size of your Azure Local instance, use the [Azure Local sizer tool](https://azurestackhcisolutions.azure.microsoft.com/#/sizer), where you can define your profile such as number of virtual machines (VMs), size of the VMs, and the workload use of the VMs such as Azure Virtual Desktop, SQL Server, or AKS.
2828

29-
As described in the Azure Local [system machine requirements](../concepts/system-requirements-23h2.md#machine-and-storage-requirements) article, the maximum number of machines supported on Azure Local instance is 16. Once you complete your workload capacity planning, you should have a good understanding of the number of machine nodes required to run workloads on your infrastructure.
29+
As described in the Azure Local [machine requirements](../concepts/system-requirements-23h2.md#machine-and-storage-requirements) article, the maximum number of machines supported on Azure Local instance is 16. Once you complete your workload capacity planning, you should have a good understanding of the number of machine nodes required to run workloads on your infrastructure.
3030

3131
- **If your workloads require four or more nodes**: You can't deploy and use a switchless configuration for storage network traffic. You need to include a physical switch with support for Remote Direct Memory Access (RDMA) to handle storage traffic. For more information on Azure Local instance network architecture, see [Network reference patterns overview](./network-patterns-overview.md).
3232

azure-local/plan/single-server-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,4 +110,4 @@ Optional - this pattern doesn't require a storage network.
110110
111111
## Next steps
112112
113-
Learn about two-node patterns - [Azure Local network deployment patterns](choose-network-pattern.md).
113+
Learn about [Two-node Azure Local network deployment patterns](choose-network-pattern.md).

azure-local/plan/two-node-switched-converged.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 02/14/2025
1313

1414
[!INCLUDE [includes](../includes/hci-applies-to-23h2-22h2.md)]
1515

16-
In this article, you'll learn about the two-node storage switched, fully converged with two TOR switches network reference pattern that you can use to deploy your Azure Local instance solution. The information in this article will also help you determine if this configuration is viable for your deployment planning needs. This article is targeted towards the IT administrators who deploy and manage Azure Local instance in their datacenters.
16+
In this article, you'll learn about the two-node storage switched, fully converged with two TOR switches network reference pattern that you can use to deploy your Azure Local instance solution. The information in this article will also help you determine if this configuration is viable for your deployment planning needs. This article is targeted towards the IT administrators who deploy and manage Azure Local instances in their datacenters.
1717

1818
For information on other network patterns, see [Azure Local network deployment patterns](choose-network-pattern.md).
1919

0 commit comments

Comments
 (0)