Skip to content

Commit 0a0655b

Browse files
author
Sreekanth Iyer (Ushta Te Consultancy Services)
committed
Format changes
1 parent a2de75f commit 0a0655b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/hdinsight/load-balancer-migration-guidelines.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ In this case, there are two options to create a cluster
3434

3535
**Approach 1:** Create the cluster with a new subnet
3636

37-
1. Choose the outbound connectivity for your cluster Follow this doc [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and choose one method to provide outbound connectivity for the new cluster. The most recommended way is to attach a NAT gateway and a Network Security Group (NSG) to the subnet.
37+
1. Choose the outbound connectivity for your cluster, and follow this document [Use Source Network Address Translation (SNAT) for outbound connections](/azure/load-balancer/load-balancer-outbound-connections), and choose one method to provide outbound connectivity for the new cluster. The most recommended way is to attach a NAT gateway and a Network Security Group (NSG) to the subnet.
3838

3939
1. (Optional) Create a new NAT gateway and a new network security group (NSG).
4040

@@ -43,7 +43,7 @@ In this case, there are two options to create a cluster
4343
>
4444
> Follow the docs [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
4545
>
46-
> You can refer to the doc [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
46+
> You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
4747
4848
1. Create a new subnet and associate the subnet with the NAT gateway and network security group.
4949

@@ -66,9 +66,9 @@ To upgrade your existing custom virtual network to integrate Azure standard load
6666

6767
> [!NOTE]
6868
> You could associate an existing NAT gateway and NSG or the newly created ones.
69-
> Follow the docs [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
69+
> Follow this doccument [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
7070
>
71-
> You can refer to the doc [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
71+
> You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
7272
7373
1. Associate the NAT gateway with your subnet along with a network security group.
7474

@@ -84,7 +84,7 @@ To upgrade your existing custom virtual network to integrate Azure standard load
8484
8585
### Scenario 2: The existing subnet has HDInsight clusters with basic load balancers.
8686

87-
**Approach 1:** The most recommended way is to associate a NAT gateway to the subnet along with Network security group.
87+
**Approach 1:** The most recommended way is to associate a NAT gateway to the subnet along with network security group.
8888

8989
According to [Azure NAT Gateway frequently asked questions](/azure/nat-gateway/faq#are-basic-sku-resources--basic-load-balancer-and-basic-public-ip-addresses--compatible-with-a-nat-gateway), the subnet with NAT gateway and Azure standard load balancer isn't compatible.
9090

@@ -96,9 +96,9 @@ To associate with a NAT Gateway, perform the following steps.
9696

9797
> [!NOTE]
9898
> You could associate an existing NAT gateway and NSG or the newly created ones.
99-
> Follow the docs [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
99+
> Follow thi document [Quickstart: Create a NAT gateway - Azure portal](/azure/nat-gateway/quickstart-create-nat-gateway-portal), and [Create, change, or delete an Azure network security group](/azure/virtual-network/manage-network-security-group?tabs=network-security-group-portal#create-a-network-security-group) to create a new NAT gateway and a new network security group.
100100
>
101-
> You can refer to the doc [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
101+
> You can refer to this document [Control network traffic in Azure HDInsight](./control-network-traffic.md#hdinsight-with-network-security-groups) to set up correct NSG rules.
102102
103103
1. Associate the subnet with the NAT gateway and network security group.
104104

0 commit comments

Comments
 (0)