Skip to content

Commit fadb955

Browse files
authored
Merge pull request #248592 from mbender-ms/lb-ILB-qs
load balancer - freshness - ILB QS
2 parents 90a0b3f + 0ee3f3d commit fadb955

File tree

1 file changed

+111
-120
lines changed

1 file changed

+111
-120
lines changed

articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md

Lines changed: 111 additions & 120 deletions
Original file line numberDiff line numberDiff line change
@@ -6,18 +6,21 @@ services: load-balancer
66
author: mbender-ms
77
ms.service: load-balancer
88
ms.topic: quickstart
9-
ms.date: 07/18/2022
9+
ms.date: 08/17/2023
1010
ms.author: mbender
11-
ms.custom: mvc, mode-ui, template-quickstart, engagement-fy23
11+
ms.custom: mvc, mode-ui, template-quickstart, engagement-fy24
1212
#Customer intent: I want to create a internal load balancer so that I can load balance internal traffic to VMs.
1313
---
1414

1515
# Quickstart: Create an internal load balancer to load balance VMs using the Azure portal
1616

17-
Get started with Azure Load Balancer by using the Azure portal to create an internal load balancer for a backend pool with two virtual machines. Additional resources include Azure Bastion, NAT Gateway, a virtual network, and the required subnets.
17+
Get started with Azure Load Balancer by using the Azure portal to create an internal load balancer for a backend pool with two virtual machines. Other resources include Azure Bastion, NAT Gateway, a virtual network, and the required subnets.
1818

1919
:::image type="content" source="media/quickstart-load-balancer-standard-internal-portal/internal-load-balancer-resources.png" alt-text="Diagram of resources deployed for internal load balancer.":::
2020

21+
> [!NOTE]
22+
> In this example you'll create a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed and 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)
23+
> For more information about outbound connections in Azure, see [Source Network Address Translation (SNAT) for outbound connections](../load-balancer/load-balancer-outbound-connections.md)
2124
## Prerequisites
2225

2326
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -26,6 +29,41 @@ Get started with Azure Load Balancer by using the Azure portal to create an inte
2629

2730
Sign in to the [Azure portal](https://portal.azure.com).
2831

32+
## Create NAT gateway
33+
34+
All outbound internet traffic traverses the NAT gateway to the internet. Use the following example to create a NAT gateway for the hub and spoke network.
35+
36+
1. Sign in to the [Azure portal](https://portal.azure.com).
37+
38+
1. In the search box at the top of the portal, enter **NAT gateway**. Select **NAT gateways** in the search results.
39+
40+
1. Select **+ Create**.
41+
42+
1. In the **Basics** tab of **Create network address translation (NAT) gateway** enter or select the following information:
43+
44+
| Setting | Value |
45+
| ------- | ----- |
46+
| **Project details** | |
47+
| Subscription | Select your subscription. |
48+
| Resource group | Select **Create new**. </br> Enter **CreateIntLBQS-rg** in Name. </br> Select **OK**. |
49+
| **Instance details** | |
50+
| NAT gateway name | Enter **myNATgateway**. |
51+
| Region | Select **East US**. |
52+
| Availability zone | Select **None**. |
53+
| Idle timeout (minutes) | Enter **15**. |
54+
55+
1. Select the **Outbound IP** tab or select the **Next: Outbound IP** button at the bottom of the page.
56+
57+
1. Select **Create a new public IP address** under **Public IP addresses**.
58+
59+
1. Enter **myNATgatewayIP** in **Name** in **Add a public IP address**.
60+
61+
1. Select **OK**.
62+
63+
1. Select the blue **Review + create** button at the bottom of the page, or select the **Review + create** tab.
64+
65+
1. Select **Create**.
66+
2967
## Create the virtual network
3068

3169
When you create an internal load balancer, a virtual network is configured as the network for the load balancer.
@@ -34,61 +72,62 @@ A private IP address in the virtual network is configured as the frontend for th
3472

3573
An Azure Bastion host is created to securely manage the virtual machines and install IIS.
3674

37-
In this section, you'll create a virtual network, subnet, and Azure Bastion host.
75+
In this section, you create a virtual network, subnet, and Azure Bastion host.
3876

3977
1. In the search box at the top of the portal, enter **Virtual network**. Select **Virtual Networks** in the search results.
4078

41-
2. In **Virtual networks**, select **+ Create**.
79+
1. In **Virtual networks**, select **+ Create**.
4280

43-
3. In **Create virtual network**, enter or select this information in the **Basics** tab:
81+
1. In **Create virtual network**, enter or select this information in the **Basics** tab:
4482

4583
| **Setting** | **Value** |
4684
|------------------|-----------------------------------------------------------------|
4785
| **Project Details** | |
4886
| Subscription | Select your Azure subscription |
49-
| Resource Group | Select **Create new**. </br> In **Name** enter **CreateIntLBQS-rg**. </br> Select **OK**. |
87+
| Resource Group | Select **CreateIntLBQS-rg**. |
5088
| **Instance details** | |
5189
| Name | Enter **myVNet** |
52-
| Region | Select **West US 3** |
90+
| Region | Select **East US** |
5391

54-
4. Select the **IP Addresses** tab or select the **Next: IP Addresses** button at the bottom of the page.
92+
1. Select the **IP Addresses** tab or select the **Next** button at the bottom of the page.
5593

56-
5. In the **IP Addresses** tab, enter this information:
94+
1. In the **IP Addresses** tab, enter this information:
5795

5896
| Setting | Value |
5997
|--------------------|----------------------------|
6098
| IPv4 address space | Enter **10.1.0.0/16** |
6199

62-
6. Under **Subnet name**, select the word **default**.
100+
1. Under **Subnets**, select the word **default**.
63101

64-
7. In **Edit subnet**, enter this information:
102+
1. In **Edit subnet**, enter this information:
65103

66104
| Setting | Value |
67105
|--------------------|----------------------------|
68106
| Subnet name | Enter **myBackendSubnet** |
69107
| Subnet address range | Enter **10.1.0.0/24** |
108+
| **Security** | |
109+
| NAT Gateway | Select **myNATgateway**. |
70110

71-
8. Select **Save**.
111+
1. Select **Add**.
72112

73-
9. Select the **Security** tab.
113+
1. Select the **Security** tab.
74114

75-
10. Under **BastionHost**, select **Enable**. Enter this information:
115+
1. Under **BastionHost**, select **Enable**. Enter this information:
76116

77117
| Setting | Value |
78118
|--------------------|----------------------------|
79119
| Bastion name | Enter **myBastionHost** |
80-
| AzureBastionSubnet address space | Enter **10.1.1.0/27** |
81-
| Public IP Address | Select **Create new**. </br> For **Name**, enter **myBastionIP**. </br> Select **OK**. |
120+
| AzureBastionSubnet address space | Enter **10.1.1.0/26** |
121+
| Public IP Address | Select **Create new**. </br> Enter **myBastionIP** in Name. </br> Select **OK**. |
82122

83123
> [!IMPORTANT]
84-
85124
> [!INCLUDE [Pricing](../../includes/bastion-pricing.md)]
86125
87126
>
88127
89-
11. Select the **Review + create** tab or select the **Review + create** button.
128+
1. Select the **Review + create** tab or select the **Review + create** button.
90129

91-
12. Select **Create**.
130+
1. Select **Create**.
92131

93132

94133
> [!NOTE]
@@ -98,67 +137,61 @@ In this section, you'll create a virtual network, subnet, and Azure Bastion host
98137

99138
In this section, you create a load balancer that load balances virtual machines.
100139

101-
During the creation of the load balancer, you'll configure:
140+
During the creation of the load balancer, you configure:
102141

103-
* Frontend IP address
104-
* Backend pool
105-
* Inbound load-balancing rules
142+
- Frontend IP address
143+
- Backend pool
144+
- Inbound load-balancing rules
106145

107146
1. In the search box at the top of the portal, enter **Load balancer**. Select **Load balancers** in the search results.
108147

109-
2. In the **Load balancer** page, select **Create**.
148+
1. In the **Load balancer** page, select **Create**.
110149

111-
3. In the **Basics** tab of the **Create load balancer** page, enter, or select the following information:
150+
1. In the **Basics** tab of the **Create load balancer** page, enter, or select the following information:
112151

113-
| Setting | Value |
114-
| --- | --- |
152+
| Setting | Value |
153+
| --- | --- |
115154
| **Project details** | |
116155
| Subscription | Select your subscription. |
117156
| Resource group | Select **CreateIntLBQS-rg**. |
118157
| **Instance details** | |
119-
| Name | Enter **myLoadBalancer** |
120-
| Region | Select **West US 3**. |
158+
| Name | Enter **myLoadBalancer** |
159+
| Region | Select **East US**. |
121160
| SKU | Leave the default **Standard**. |
122-
| Type | Select **Internal**. |
161+
| Type | Select **Internal**. |
123162
| Tier | Leave the default of **Regional**. |
124163

125-
126164
:::image type="content" source="./media/quickstart-load-balancer-standard-internal-portal/create-standard-internal-load-balancer.png" alt-text="Screenshot of create standard load balancer basics tab." border="true":::
127165

128-
4. Select **Next: Frontend IP configuration** at the bottom of the page.
129-
130-
5. In **Frontend IP configuration**, select **+ Add a frontend IP configuration**.
131-
132-
6. Enter **myFrontend** in **Name**.
133-
134-
7. Select **myBackendSubnet** in **Subnet**.
135-
136-
8. Select **Dynamic** for **Assignment**.
137-
138-
9. Select **Zone-redundant** in **Availability zone**.
139-
140-
10. Select **Add**.
141-
142-
11. Select **Next: Backend pools** at the bottom of the page.
143-
144-
12. In the **Backend pools** tab, select **+ Add a backend pool**.
145-
146-
13. Enter **myBackendPool** for **Name** in **Add backend pool**.
166+
1. Select **Next: Frontend IP configuration** at the bottom of the page.
147167

148-
14. Select **NIC** or **IP Address** for **Backend Pool Configuration**.
168+
1. In **Frontend IP configuration**, select **+ Add a frontend IP configuration**, then enter or select the following information:
149169

150-
15. Select **IPv4** or **IPv6** for **IP version**.
151-
152-
16. Select **Add**.
153-
154-
17. Select the **Next: Inbound rules** button at the bottom of the page.
155-
156-
18. In **Load balancing rule** in the **Inbound rules** tab, select **+ Add a load balancing rule**.
157-
158-
19. In **Add load balancing rule**, enter or select the following information:
170+
| Setting | Value |
171+
| ------- | ----- |
172+
| Name | Enter **myFrontend** |
173+
| Private IP address version | Select **IPv4** or **IPv6** depending on your requirements. |
159174

160175
| Setting | Value |
161176
| ------- | ----- |
177+
| Name | Enter **myFrontend** |
178+
| Virtual network | Select **myVNet** |
179+
| Subnet | Select **myBackendSubnet** |
180+
| Assignment | Select **Dynamic** |
181+
| Availability zone | Select **Zone-redundant** |
182+
183+
1. Select **Add**.
184+
1. Select **Next: Backend pools** at the bottom of the page.
185+
1. In the **Backend pools** tab, select **+ Add a backend pool**.
186+
1. Enter **myBackendPool** for **Name** in **Add backend pool**.
187+
1. Select **IP Address** for **Backend Pool Configuration**.
188+
1. Select **Save**.
189+
1. Select the **Next: Inbound rules** button at the bottom of the page.
190+
1. In **Load balancing rule** in the **Inbound rules** tab, select **+ Add a load balancing rule**.
191+
1. In **Add load balancing rule**, enter or select the following information:
192+
193+
| **Setting** | **Value** |
194+
| ----------- | --------- |
162195
| Name | Enter **myHTTPRule** |
163196
| IP Version | Select **IPv4** or **IPv6** depending on your requirements. |
164197
| Frontend IP address | Select **myFrontend**. |
@@ -169,61 +202,18 @@ During the creation of the load balancer, you'll configure:
169202
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe**. </br> Select **TCP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
170203
| Session persistence | Select **None**. |
171204
| Idle timeout (minutes) | Enter or select **15**. |
172-
| TCP reset | Select **Enabled**. |
173-
| Floating IP | Select **Disabled**. |
174-
175-
20. Select **Add**.
176-
177-
21. Select the blue **Review + create** button at the bottom of the page.
178-
179-
22. Select **Create**.
180-
181-
> [!NOTE]
182-
> In this example you'll create a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed and 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)
183-
> For more information about outbound connections in Azure, see [Source Network Address Translation (SNAT) for outbound connections](../load-balancer/load-balancer-outbound-connections.md)
184-
185-
## Create NAT gateway
186-
187-
In this section, you'll create a NAT gateway for outbound internet access for resources in the virtual network.
188-
189-
1. In the search box at the top of the portal, enter **NAT gateway**. Select **NAT gateways** in the search results.
190-
191-
2. In **NAT gateways**, select **+ Create**.
205+
| Enable TCP reset | Select **checkbox** . |
206+
| Enable Floating IP | Leave the default of unselected. |
192207

193-
3. In **Create network address translation (NAT) gateway**, enter or select the following information:
208+
1. Select **Save**.
194209

195-
| Setting | Value |
196-
| ------- | ----- |
197-
| **Project details** | |
198-
| Subscription | Select your subscription. |
199-
| Resource group | Select **CreateIntLBQS-rg**. |
200-
| **Instance details** | |
201-
| NAT gateway name | Enter **myNATgateway**. |
202-
| Region | Select **West US 3**. |
203-
| Availability zone | Select **None**. |
204-
| Idle timeout (minutes) | Enter **15**. |
205-
206-
4. Select the **Outbound IP** tab or select the **Next: Outbound IP** button at the bottom of the page.
210+
1. Select the blue **Review + create** button at the bottom of the page.
207211

208-
5. In **Outbound IP**, select **Create a new public IP address** next to **Public IP addresses**.
209-
210-
6. Enter **myNATgatewayIP** in **Name** in **Add a public IP address**.
211-
212-
7. Select **OK**.
213-
214-
8. Select the **Subnet** tab or select the **Next: Subnet** button at the bottom of the page.
215-
216-
9. In **Virtual network**, select **myVNet**.
217-
218-
10. Select **myBackendSubnet** under **Subnet name**.
219-
220-
11. Select the blue **Review + create** button at the bottom of the page, or select the **Review + create** tab.
221-
222-
12. Select **Create**.
212+
1. Select **Create**.
223213

224214
## Create virtual machines
225215

226-
In this section, you'll create two VMs (**myVM1** and **myVM2**) in two different zones (**Zone 1** and **Zone 2**).
216+
In this section, you create two VMs (**myVM1** and **myVM2**) in two different zones (**Zone 1** and **Zone 2**).
227217

228218
These VMs are added to the backend pool of the load balancer that was created earlier.
229219

@@ -240,7 +230,7 @@ These VMs are added to the backend pool of the load balancer that was created ea
240230
| Resource Group | Select **CreateIntLBQS-rg** |
241231
| **Instance details** | |
242232
| Virtual machine name | Enter **myVM1** |
243-
| Region | Select **(US) West US 3** |
233+
| Region | Select **(US) East US** |
244234
| Availability Options | Select **Availability zones** |
245235
| Availability zone | Select **1** |
246236
| Security type | Select **Standard**. |
@@ -289,7 +279,7 @@ These VMs are added to the backend pool of the load balancer that was created ea
289279

290280
## Create test virtual machine
291281

292-
In this section, you'll create a VM named **myTestVM**. This VM will be used to test the load balancer configuration.
282+
In this section, you create a VM named **myTestVM**. This VM is used to test the load balancer configuration.
293283

294284
1. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines** in the search results.
295285

@@ -304,10 +294,10 @@ In this section, you'll create a VM named **myTestVM**. This VM will be used to
304294
| Resource Group | Select **CreateIntLBQS-rg** |
305295
| **Instance details** | |
306296
| Virtual machine name | Enter **myTestVM** |
307-
| Region | Select **(US) West US 3** |
297+
| Region | Select **(US) East US** |
308298
| Availability Options | Select **No infrastructure redundancy required** |
309299
| Security type | Select **Standard**. |
310-
| Image | Select **Windows Server 2019 Datacenter - Gen2** |
300+
| Image | Select **Windows Server 2022 Datacenter - x64 Gen2** |
311301
| Azure Spot instance | Leave the default of unselected. |
312302
| Size | Choose VM size or take default setting |
313303
| **Administrator account** | |
@@ -372,7 +362,7 @@ In this section, you'll create a VM named **myTestVM**. This VM will be used to
372362

373363
## Test the load balancer
374364

375-
In this section, you'll test the load balancer by connecting to the **myTestVM** and verifying the webpage.
365+
In this section, you test the load balancer by connecting to the **myTestVM** and verifying the webpage.
376366

377367
1. In the search box at the top of the portal, enter **Load balancer**. Select **Load balancers** in the search results.
378368

@@ -388,13 +378,14 @@ In this section, you'll test the load balancer by connecting to the **myTestVM**
388378

389379
7. Enter the username and password entered during VM creation.
390380

391-
8. Open **Internet Explorer** on **myTestVM**.
381+
8. Open **Microsoft Edge** on **myTestVM**.
392382

393383
9. Enter the IP address from the previous step into the address bar of the browser. The custom page displaying one of the backend server names is displayed on the browser. In this example, it's **10.1.0.4**.
394384

395385
:::image type="content" source="./media/quickstart-load-balancer-standard-internal-portal/load-balancer-test.png" alt-text="Screenshot shows a browser window displaying the customized page, as expected." border="true":::
396386

397-
To see the load balancer distribute traffic across both VMs, you can force-refresh your web browser from the client machine.
387+
1. To see the load balancer distribute traffic across both VMs, navigate to the VM shown in the browser message, and stop the VM.
388+
1. Refresh the browser window. The page should still display the customized page. The load balancer is now only sending traffic to the remaining VM.
398389

399390
## Clean up resources
400391

@@ -404,11 +395,11 @@ When no longer needed, delete the resource group, load balancer, and all related
404395

405396
In this quickstart, you:
406397

407-
* Created an internal Azure Load Balancer
398+
- Created an internal Azure Load Balancer
408399

409-
* Attached 2 VMs to the load balancer
400+
- Attached 2 VMs to the load balancer
410401

411-
* Configured the load balancer traffic rule, health probe, and then tested the load balancer
402+
- Configured the load balancer traffic rule, health probe, and then tested the load balancer
412403

413404
To learn more about Azure Load Balancer, continue to:
414405
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)