You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-balancer/quickstart-load-balancer-standard-public-portal.md
+27-36Lines changed: 27 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.devlang: na
15
15
ms.topic: quickstart
16
16
ms.tgt_pltfrm: na
17
17
ms.workload: infrastructure-services
18
-
ms.date: 03/20/18
18
+
ms.date: 08/21/2018
19
19
ms.author: kumud
20
20
ms.custom: mvc
21
21
---
@@ -26,24 +26,29 @@ Load balancing provides a higher level of availability and scale by spreading in
26
26
27
27
If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
28
28
29
-
## Log in to Azure
29
+
## Sign in to Azure
30
30
31
-
Log in to the Azure portal at [http://portal.azure.com](http://portal.azure.com).
31
+
Sign in to the Azure portal at [http://portal.azure.com](http://portal.azure.com).
32
32
33
33
## Create a public load balancer
34
34
35
35
In this section, you create a public load balancer that helps load balance virtual machines. Standard Load Balancer only supports a Standard Public IP address. When you create a Standard Load Balancer, and you must also create a new Standard Public IP address that is configured as the frontend (named as *LoadBalancerFrontend* by default) for the Standard Load Balancer.
36
36
37
37
1. On the top left-hand side of the screen, click **Create a resource** > **Networking** > **Load Balancer**.
38
-
2. In the **Create a load balancer** page enter these values for the load balancer:
39
-
-*myLoadBalancer* - for the name of the load balancer.
40
-
-**Public** - for the type of the load balancer.
41
-
-*myPublicIP* - for the **New** Public IP that you create.
42
-
-*myResourceGroupSLB* - for the name of the **New** resource group that you select to create.
43
-
-**westeurope** - for the location.
44
-
3. Click **Create** to create the load balancer.
45
-
46
-

38
+
2. In the **Create load balancer** page, enter or select the following information, accept the defaults for the remaining settings, and then select **Create**:
39
+
40
+
| Setting | Value |
41
+
| --- | --- |
42
+
| Name |*myLoadBalancer*|
43
+
| Type | Public |
44
+
| SKU | Standard |
45
+
| Public IP address | Select **Create new** and type *myPublicIP* in the text box. The Standard SKU for the Public IP address is selected by default. For **Availability zone**, select **Zone-redundant**. |
46
+
| Subscription | Select your subscription. |
47
+
|Resource group | Select **Create new**, and then type *myResourceGroupSLB*. |
48
+
| Location | Select **West Europe**. |
49
+
50
+
51
+

47
52
48
53
49
54
## Create backend servers
@@ -63,18 +68,18 @@ In this section, you create a virtual network, create two virtual machines for t
63
68
64
69
1. On the top left-hand side of the screen, click **New** > **Compute** > **Windows Server 2016 Datacenter** and enter these values for the virtual machine:
65
70
-*myVM1* - for the name of the virtual machine.
66
-
-*azureuser* - for the administrator user name.
67
71
-*myResourceGroupSLB* - for **Resource group**, select **Use existing**, and then select *myResourceGroupSLB*.
68
72
2. Click **OK**.
69
73
3. Select **DS1_V2** for the size of the virtual machine, and click **Select**.
70
74
4. Enter these values for the VM settings:
71
-
-*myAvailabilitySet* - for the name of the new Availability set that you create.
72
-
-*myVNet* - ensure it is selected as the virtual network.
73
-
-*myBackendSubnet* - ensure it is selected as the subnet.
74
-
-*myNetworkSecurityGroup* - for the name of the new network security group (firewall) that you must create.
75
+
1. Ensure that *myVNet* is selected as the virtual network, and *myBackendSubnet* is selected as the subnet.
76
+
2. For **Public IP address**, in the **Create Public IP address** pane, select **Standard**, and then select **OK**.
77
+
3. For **Network Security Group**, select **Advanced**, and then do the following:
78
+
1. Select *Network security group (firewall), and the **Choose network security group** page, select **Create new**.
79
+
2. In the **Create network security group** page, for **Name**, enter *myNetworkSecurityGroup*, and then select **OK**.
75
80
5. Click **Disabled** to disable boot diagnostics.
76
81
6. Click **OK**, review the settings on the summary page, and then click **Create**.
77
-
7.Create a second VM, named, *VM2* with *myAvailibilityset* as the Availability set, *myVnet* as its virtual network, *myBackendSubnet* and its subnet, and **myNetworkSecurityGroup* as its network security group using steps 1-6.
82
+
7.Using steps 1-6, create a second VM, named, *VM2* with *myAvailibilityset* as the Availability set, *myVnet* as its virtual network, *myBackendSubnet* and its subnet, and **myNetworkSecurityGroup* as its network security group.
78
83
79
84
### Create NSG rules
80
85
@@ -93,17 +98,6 @@ In this section, you create NSG rules to allow inbound connections using HTTP an
93
98
-*Allow HTTP* - for description
94
99
4. Click **OK**.
95
100
96
-

97
-
5. Repeat steps 2 to 4 to create another rule named *myRDPRule* to allow for an inbound RDP connection using port 3389 with the following values:
98
-
-*Service Tag* - for **Source**.
99
-
-*Internet* - for **Source service tag**
100
-
-*3389* - for **Destination port ranges**
101
-
-*TCP* - for **Protocol**
102
-
-*Allow* - for **Action**
103
-
-*200* for **Priority**
104
-
-*myRDPRule* for name
105
-
-*Allow RDP* - for description
106
-
107
101
### Install IIS
108
102
109
103
1. Click **All resources** in the left-hand menu, and then from the resources list click **myVM1** that is located in the *myResourceGroupLB* resource group.
@@ -120,7 +114,7 @@ In this section, you create NSG rules to allow inbound connections using HTTP an
120
114
121
115
## Create load balancer resources
122
116
123
-
In this section, you configure load balancer settings for a backend address pool and a health probe, and specify load balancer and NAT rules.
117
+
In this section, you configure load balancer settings for a backend address pool and a health probe, and specify a load balancer rule.
124
118
125
119
126
120
### Create a backend address pool
@@ -130,14 +124,11 @@ To distribute traffic to the VMs, a backend address pool contains the IP address
130
124
1. Click **All resources** in the left-hand menu, and then click **myLoadBalancer** from the resources list.
131
125
2. Under **Settings**, click **Backend pools**, then click **Add**.
132
126
3. On the **Add a backend pool** page, do the following:
133
-
- For name, type *myBackEndPool, as the name for your backend pool.
134
-
- For **Associated to**, from the drop-down menu, click **Availability set**
135
-
- For **Availability set**, click, **myAvailabilitySet**.
136
-
- Click **Add a target network IP configuration** to add each virtual machine (*myVM1* & *myVM2*) that you created to the backend pool.
127
+
- For name, type *myBackendPool*, as the name for your backend pool.
128
+
- For **Virtual network**, select *myVNet*.
129
+
- Add *myVM1* and *my VM2* under **Virtual Machine** along with their corresponding IP addresses, and then select **Add**.
137
130
- Click **OK**.
138
131
139
-

140
-
141
132
3. Check to make sure your load balancer backend pool setting displays both the VMs **VM1** and **VM2**.
0 commit comments