Skip to content

Commit aee762c

Browse files
committed
More changes
1 parent e0c874b commit aee762c

File tree

2 files changed

+4
-5
lines changed

2 files changed

+4
-5
lines changed

azure-local/concepts/firewall-requirements.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Depending on additional Azure services you enable for Azure Local, you may need
8282

8383
## Firewall requirements for internal rules and ports
8484

85-
Ensure that the proper network ports are open between all nodes, both within a site and between sites for stretched instances (stretched instance functionality is only available in Azure Local, version 22H2.). You'll need appropriate firewall rules to allow ICMP, SMB (port 445, plus port 5445 for SMB Direct if using iWARP RDMA), and WS-MAN (port 5985) bi-directional traffic between all nodes in the cluster.
85+
Ensure that the proper network ports are open between all nodes, both within a site and between sites for stretched instances (stretched instance functionality is only available in Azure Stack HCI, version 22H2). You'll need appropriate firewall rules to allow ICMP, SMB (port 445, plus port 5445 for SMB Direct if using iWARP RDMA), and WS-MAN (port 5985) bi-directional traffic between all nodes in the cluster.
8686

8787
When using the **Creation wizard** in Windows Admin Center to create the cluster, the wizard automatically opens the appropriate firewall ports on each server in the cluster for Failover Clustering, Hyper-V, and Storage Replica. If you're using a different firewall on each machine, open the ports as described in the following sections:
8888

@@ -92,7 +92,7 @@ Ensure that the following firewall rules are configured in your on-premises fire
9292

9393
| Rule | Action | Source | Destination | Service | Ports |
9494
|:--|:--|:--|:--|:--|:--|
95-
| Allow inbound/outbound traffic to and from the Azure Local service on Azure Local instance machines | Allow | Instance nodes | Instance nodes | TCP | 30301 |
95+
| Allow inbound/outbound traffic to and from the Azure Local service on Azure Local machines | Allow | Instance nodes | Instance nodes | TCP | 30301 |
9696

9797
### Windows Admin Center
9898

@@ -198,5 +198,4 @@ This section shows how to configure Microsoft Defender firewall to allow IP addr
198198
For more information, see also:
199199
200200
- The Windows Firewall and WinRM 2.0 ports section of [Installation and configuration for Windows Remote Management](/windows/win32/winrm/installation-and-configuration-for-windows-remote-management#windows-firewall-and-winrm-20-ports)
201-
- See [About Azure Local deployment](../deploy/deployment-introduction.md)
202-
````
201+
- [About Azure Local deployment](../deploy/deployment-introduction.md).

azure-local/manage/azure-arc-vm-management-prerequisites.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ For Arc VM images to be used on Azure Local, make sure to satisfy the following
4444

4545
## Firewall requirements
4646

47-
Make sure the requirements as listed in [Required firewall URLs for Azure Local deployments](../concepts/firewall-requirements.md#required-firewall-urls-for-azure-local-version-23h2-deployments) are satisfied to allow communication between the Arc VMs running on Azure Local and Azure Arc.
47+
Make sure the requirements as listed in [Required firewall URLs for Azure Local deployments](../concepts/firewall-requirements.md#required-firewall-urls-for-azure-local-deployments) are satisfied to allow communication between the Arc VMs running on Azure Local and Azure Arc.
4848

4949
## Azure Command-Line Interface (CLI) requirements
5050

0 commit comments

Comments
 (0)