Skip to content

Commit b6fb32f

Browse files
asudbringasudbring
committed
fixes
1 parent 25f4d00 commit b6fb32f

File tree

1 file changed

+106
-79
lines changed

1 file changed

+106
-79
lines changed

‎articles/load-balancer/load-balancer-multiple-ip.md

Lines changed: 106 additions & 79 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,6 @@ In this section, you'll create a virtual network for the load balancer and virtu
7979
| AzureBastionSubnet address space | Enter **10.1.1.0/26** |
8080
| Public IP Address | Select **Create new**. </br> For **Name**, enter **myBastionIP**. </br> Select **OK**. |
8181

82-
8382
12. Select the **Review + create** tab select **Review + create**.
8483

8584
13. Select **Create**.
@@ -152,9 +151,9 @@ In this section, you'll create two virtual machines to host the IIS websites.
152151
| **Inbound port rules** | |
153152
| Public inbound ports | Select **None** |
154153

155-
3. Select the **Networking** tab, or select **Next: Disks**, then **Next: Networking**.
154+
4. Select the **Networking** tab, or select **Next: Disks**, then **Next: Networking**.
156155

157-
4. In the Networking tab, select or enter:
156+
5. In the Networking tab, select or enter:
158157

159158
| Setting | Value |
160159
|-|-|
@@ -165,11 +164,11 @@ In this section, you'll create two virtual machines to host the IIS websites.
165164
| NIC network security group | Select **Advanced**|
166165
| Configure network security group | Select **Create new**. </br> In **Create network security group**, enter **myNSG** in **Name**. </br> In **Inbound rules**, select **+Add an inbound rule**. </br> In **Service**, select **HTTP**. </br> In **Priority**, enter **100**. </br> In **Name**, enter **myNSGrule** </br> Select **Add** </br> Select **OK** |
167166

168-
7. Select **Review + create**.
167+
6. Select **Review + create**.
169168

170-
8. Review the settings, and then select **Create**.
169+
7. Review the settings, and then select **Create**.
171170

172-
9. Follow the steps 1 to 8 to create another VM with the following values and all the other settings the same as **myVM1**:
171+
8. Follow the steps 1 to 7 to create another VM with the following values and all the other settings the same as **myVM1**:
173172

174173
| Setting | VM 2 |
175174
| ------- | ---- |
@@ -254,25 +253,69 @@ You'll connect to **myVM1** and **myVM2** with Azure Bastion and configure the s
254253

255254
4. In **Overview**, select **Connect** then **Bastion**.
256255

257-
6. Enter the username and password you entered when you created the virtual machine.
256+
5. Enter the username and password you entered when you created the virtual machine.
258257

259-
7. Select **Allow** for Bastion to use the clipboard.
258+
6. Select **Allow** for Bastion to use the clipboard.
260259

261-
8. On the server desktop, navigate to Start > Windows Administrative Tools > Windows PowerShell > Windows PowerShell.
260+
7. On the server desktop, navigate to Start > Windows Administrative Tools > Windows PowerShell > Windows PowerShell.
262261

263-
9. In the PowerShell window, execute the `route print` command, which returns output similar to the following output for a virtual machine with two attached network interfaces:
262+
8. In the PowerShell window, execute the `route print` command, which returns output similar to the following output for a virtual machine with two attached network interfaces:
264263

265264
```console
266265
===========================================================================
267266
Interface List
268-
6...00 22 48 86 00 53 ......Microsoft Hyper-V Network Adapter #2
269-
13...00 22 48 83 0b da ......Microsoft Hyper-V Network Adapter #3
267+
4...60 45 bd 9c c7 00 ......Microsoft Hyper-V Network Adapter
268+
11...60 45 bd 8d 44 fa ......Microsoft Hyper-V Network Adapter #3
270269
1...........................Software Loopback Interface 1
271270
===========================================================================
271+
272+
IPv4 Route Table
273+
===========================================================================
274+
Active Routes:
275+
Network Destination Netmask Gateway Interface Metric
276+
0.0.0.0 0.0.0.0 10.1.0.1 10.1.0.4 10
277+
10.1.0.0 255.255.255.0 On-link 10.1.0.4 266
278+
10.1.0.0 255.255.255.0 On-link 10.1.0.6 266
279+
10.1.0.4 255.255.255.255 On-link 10.1.0.4 266
280+
10.1.0.6 255.255.255.255 On-link 10.1.0.6 266
281+
10.1.0.255 255.255.255.255 On-link 10.1.0.4 266
282+
10.1.0.255 255.255.255.255 On-link 10.1.0.6 266
283+
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
284+
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
285+
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
286+
168.63.129.16 255.255.255.255 10.1.0.1 10.1.0.4 11
287+
169.254.169.254 255.255.255.255 10.1.0.1 10.1.0.4 11
288+
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
289+
224.0.0.0 240.0.0.0 On-link 10.1.0.4 266
290+
224.0.0.0 240.0.0.0 On-link 10.1.0.6 266
291+
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
292+
255.255.255.255 255.255.255.255 On-link 10.1.0.4 266
293+
255.255.255.255 255.255.255.255 On-link 10.1.0.6 266
294+
===========================================================================
295+
Persistent Routes:
296+
None
297+
298+
IPv6 Route Table
299+
===========================================================================
300+
Active Routes:
301+
If Metric Network Destination Gateway
302+
1 331 ::1/128 On-link
303+
4 266 fe80::/64 On-link
304+
11 266 fe80::/64 On-link
305+
11 266 fe80::382:8783:5d2:f71e/128
306+
On-link
307+
4 266 fe80::1575:ced8:3e94:f23a/128
308+
On-link
309+
1 331 ff00::/8 On-link
310+
4 266 ff00::/8 On-link
311+
11 266 ff00::/8 On-link
312+
===========================================================================
313+
Persistent Routes:
314+
None
272315
```
273316
In this example, **Microsoft Hyper-V Network Adapter #3 (interface 13)** is the secondary network interface that doesn't have a default gateway assigned to it.
274317

275-
10. In the PowerShell window, execute the `ipconfig /all` command to see which IP address is assigned to the secondary network interface. In this example, **10.1.0.6** is assigned to interface 13. No default gateway address is returned for the secondary network interface.
318+
9. In the PowerShell window, execute the `ipconfig /all` command to see which IP address is assigned to the secondary network interface. In this example, **10.1.0.6** is assigned to interface 13. No default gateway address is returned for the secondary network interface.
276319

277320
```console
278321

@@ -294,15 +337,15 @@ You'll connect to **myVM1** and **myVM2** with Azure Bastion and configure the s
294337
NetBIOS over Tcpip. . . . . . . . : Enabled
295338
```
296339

297-
11. To route all traffic for addresses outside the subnet to the gateway, execute the following command:
340+
10. To route all traffic for addresses outside the subnet to the gateway, execute the following command:
298341

299342
```console
300343
route -p add 0.0.0.0 MASK 0.0.0.0 10.1.0.1 METRIC 5015 IF 13
301344
```
302345

303346
In this example, **10.1.0.1** is the default gateway for the virtual network you created previously.
304347

305-
12. Execute the following commands or copy and paste the code into the PowerShell window to install and configure IIS and the test websites:
348+
11. Execute the following commands or copy and paste the code into the PowerShell window to install and configure IIS and the test websites:
306349

307350
```powershell
308351
## Install IIS and the management tools. ##
@@ -356,11 +399,11 @@ You'll connect to **myVM1** and **myVM2** with Azure Bastion and configure the s
356399

357400
}
358401
Add-Content @para6
359-
360402
```
361-
13. Close the Bastion connection to **myVM1**.
362403

363-
14. Repeat steps 1 through 13 for **myVM2**. Use the following PowerShell code for **myVM2** for the IIS install.
404+
12. Close the Bastion connection to **myVM1**.
405+
406+
13. Repeat steps 1 through 12 for **myVM2**. Use the following PowerShell code for **myVM2** for the IIS install.
364407

365408
```powershell
366409
## Install IIS and the management tools. ##
@@ -424,7 +467,7 @@ With zone-redundancy, one or more availability zones can fail and the data path
424467
During the creation of the load balancer, you'll configure:
425468

426469
* Two frontend IP addresses, one for each website.
427-
* Backend pool
470+
* Backend pools
428471
* Inbound load-balancing rules
429472

430473
1. In the search box at the top of the portal, enter **Load balancer**. Select **Load balancers** in the search results.
@@ -447,98 +490,82 @@ During the creation of the load balancer, you'll configure:
447490

448491
4. Select **Next: Frontend IP configuration**.
449492

450-
5. In **Frontend IP configuration**, select **+ Add a frontend IP**.
493+
5. In **Frontend IP configuration**, select **+ Add a frontend IP configuration**.
451494

452-
6. Enter **Frontend-contoso** in **Name**.
495+
6. Enter or select the following information in **Add frontend IP configuration**:
453496

454-
7. Select **IPv4** for the **IP version**.
497+
| Setting | Value |
498+
| ------- | ----- |
499+
| Name | Enter **Frontend-contoso**. |
500+
| IP version | Select **IPv4**. |
501+
| IP type | Select **IP address**. |
502+
| Public IP address | Select **Create new**. </br> Enter **myPublicIP-contoso** for **Name** </br> Select **Zone-redundant** in **Availability zone**. </br> Leave the default of **Microsoft Network** for **Routing preference**. </br> Select **OK**. |
455503

456504
> [!NOTE]
457505
> IPv6 isn't currently supported with Routing Preference or Cross-region load-balancing (Global Tier).
458-
459-
8. Select **IP address** for the **IP type**.
460-
461-
> [!NOTE]
506+
>
462507
> For more information on IP prefixes, see [Azure Public IP address prefix](../virtual-network/ip-services/public-ip-address-prefix.md).
463-
464-
9. Select **Create new** in **Public IP address**.
465-
466-
10. In **Add a public IP address**, enter **myPublicIP-contoso** for **Name**.
467-
468-
11. Select **Zone-redundant** in **Availability zone**.
469-
470-
> [!NOTE]
508+
>
471509
> In regions with [Availability Zones](../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json#availability-zones), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear. </br> For more information on availability zones, see [Availability zones overview](../availability-zones/az-overview.md).
472510

473-
12. Leave the default of **Microsoft Network** for **Routing preference**.
474-
475-
13. Select **OK**.
476-
477-
14. Select **Add**.
478-
479-
14. Select **+ Add a frontend IP**.
511+
7. Select **Add**.
480512

481-
15. Enter **Frontend-fabrikam** in **Name**.
513+
8. Select **+ Add a frontend IP configuration**.
482514

483-
7. Select **IPv4** for the **IP version**.
515+
9. Enter or select the following information in **Add frontend IP configuration**:
484516

485-
8. Select **IP address** for the **IP type**.
486-
487-
9. Select **Create new** in **Public IP address**.
488-
489-
10. In **Add a public IP address**, enter **myPublicIP-fabrikam** for **Name**.
490-
491-
11. Select **Zone-redundant** in **Availability zone**.
492-
493-
12. Leave the default of **Microsoft Network** for **Routing preference**.
494-
495-
13. Select **OK**.
517+
| Setting | Value |
518+
| ------- | ----- |
519+
| Name | Enter **Frontend-fabrikam**. |
520+
| IP version | Select **IPv4**. |
521+
| IP type | Select **IP address**. |
522+
| Public IP address | Select **Create new**. </br> Enter **myPublicIP-fabrikam** for **Name** </br> Select **Zone-redundant** in **Availability zone**. </br> Leave the default of **Microsoft Network** for **Routing preference**. </br> Select **OK**. |
496523

497-
14. Select **Add**.
524+
10. Select **Add**.
498525

499-
15. Select **Next: Backend pools**.
526+
11. Select **Next: Backend pools**.
500527

501-
16. In the **Backend pools** tab, select **+ Add a backend pool**.
528+
12. In the **Backend pools** tab, select **+ Add a backend pool**.
502529

503-
17. Enter or select the following information in **Add a backend pool**:
530+
13. Enter or select the following information in **Add a backend pool**:
504531

505532
| Setting | Value |
506533
| ------- | ----- |
507534
| Name | Enter **myBackendPool-contoso**. |
508535
| Virtual network | Select **myVNet**. |
509536
| Backend Pool Configuration | Select **NIC**. |
510537

511-
21. In **IP configurations**, select **+ Add**.
538+
14. In **IP configurations**, select **+ Add**.
512539

513-
22. Select **myVM1** and **myVM2** that correspond with **ipconfig1 (10.1.0.4)** and **ipconfig1 (10.1.0.5)**.
540+
15. Select **myVM1** and **myVM2** that correspond with **ipconfig1 (10.1.0.4)** and **ipconfig1 (10.1.0.5)**.
514541

515-
23. Select **Add**.
542+
16. Select **Add**.
516543

517-
21. Select **Save**.
544+
17. Select **Save**.
518545

519-
22. Select **+ Add a backend pool**.
546+
18. Select **+ Add a backend pool**.
520547

521-
23. Enter or select the following information in **Add a backend pool**:
548+
19. Enter or select the following information in **Add a backend pool**:
522549

523550
| Setting | Value |
524551
| ------- | ----- |
525552
| Name | Enter **myBackendPool-fabrikam**. |
526553
| Virtual network | Select **myVNet**. |
527554
| Backend Pool Configuration | Select **NIC**. |
528555

529-
21. In **IP configurations**, select **+ Add**.
556+
20. In **IP configurations**, select **+ Add**.
530557

531-
22. Select **myVM1** and **myVM2** that correspond with **ipconfig1 (10.1.0.6)** and **ipconfig1 (10.1.0.7)**.
558+
21. Select **myVM1** and **myVM2** that correspond with **ipconfig1 (10.1.0.6)** and **ipconfig1 (10.1.0.7)**.
532559

533-
23. Select **Add**.
560+
22. Select **Add**.
534561

535-
21. Select **Save**.
562+
23. Select **Save**.
536563

537-
22. Select **Next: Inbound rules**.
564+
24. Select **Next: Inbound rules**.
538565

539-
23. In **Load balancing rule** in the **Inbound rules** tab, select **+ Add a load balancing rule**.
566+
25. In **Load balancing rule** in the **Inbound rules** tab, select **+ Add a load balancing rule**.
540567

541-
24. In **Add load balancing rule**, enter or select the following information:
568+
26. In **Add load balancing rule**, enter or select the following information:
542569

543570
| Setting | Value |
544571
| ------- | ----- |
@@ -549,18 +576,18 @@ During the creation of the load balancer, you'll configure:
549576
| Protocol | Select **TCP**. |
550577
| Port | Enter **80**. |
551578
| Backend port | Enter **80**. |
552-
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe-contoso**. </br> Select **HTTP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
579+
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe-contoso**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
553580
| Session persistence | Select **None**. |
554581
| Idle timeout (minutes) | Enter or select **15**. |
555582
| TCP reset | Select **Enabled**. |
556583
| Floating IP | Select **Disabled**. |
557584
| Outbound source network address translation (SNAT) | Leave the default of **(Recommended) Use outbound rules to provide backend pool members access to the internet.** |
558585

559-
25. Select **Add**.
586+
27. Select **Add**.
560587

561-
26. Select **Add a load balancing rule**.
588+
28. Select **Add a load balancing rule**.
562589

563-
27. In **Add load balancing rule**, enter or select the following information:
590+
29. In **Add load balancing rule**, enter or select the following information:
564591

565592
| Setting | Value |
566593
| ------- | ----- |
@@ -571,18 +598,18 @@ During the creation of the load balancer, you'll configure:
571598
| Protocol | Select **TCP**. |
572599
| Port | Enter **80**. |
573600
| Backend port | Enter **80**. |
574-
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe-fabrikam**. </br> Select **HTTP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
601+
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe-fabrikam**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
575602
| Session persistence | Select **None**. |
576603
| Idle timeout (minutes) | Enter or select **15**. |
577604
| TCP reset | Select **Enabled**. |
578605
| Floating IP | Select **Disabled**. |
579606
| Outbound source network address translation (SNAT) | Leave the default of **(Recommended) Use outbound rules to provide backend pool members access to the internet.** |
580607

581-
25. Select **Add**.
608+
30. Select **Add**.
582609

583-
26. Select the blue **Review + create** button at the bottom of the page.
610+
31. Select the blue **Review + create** button at the bottom of the page.
584611

585-
27. Select **Create**.
612+
32. Select **Create**.
586613

587614
> [!NOTE]
588615
> In this example we created a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed as it's optional isn't needed with the NAT gateway. For more information on Azure NAT gateway, see [What is Azure Virtual Network NAT?](../virtual-network/nat-gateway/nat-overview.md)

0 commit comments

Comments
 (0)