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/virtual-machine-scale-sets/virtual-machine-scale-sets-networking.md
+15-30Lines changed: 15 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,42 +37,27 @@ Azure Accelerated Networking improves network performance by enabling single roo
37
37
}
38
38
```
39
39
40
-
## Create a scale set that references an existing Azure Load Balancer
41
-
When a scale set is created using the Azure portal, a new load balancer is created for most configuration options. If you create a scale set, which needs to reference an existing load balancer, you can do this using the CLI. The following example script creates a load balancer and then creates a scale set, which references it:
40
+
## Azure virtual machine scale sets with Azure Load Balancer
42
41
43
-
```azurecli
44
-
az network lb create \
45
-
-g lbtest \
46
-
-n mylb \
47
-
--vnet-name myvnet \
48
-
--subnet mysubnet \
49
-
--public-ip-address-allocation Static \
50
-
--backend-pool-name mybackendpool
51
-
52
-
az vmss create \
53
-
-g lbtest \
54
-
-n myvmss \
55
-
--image Canonical:UbuntuServer:16.04-LTS:latest \
56
-
--admin-username negat \
57
-
--ssh-key-value /home/myuser/.ssh/id_rsa.pub \
58
-
--upgrade-policy-mode Automatic \
59
-
--instance-count 3 \
60
-
--vnet-name myvnet \
61
-
--subnet mysubnet \
62
-
--lb mylb \
63
-
--backend-pool-name mybackendpool
64
-
```
42
+
When working with virtual machine scale sets and load balancer, the following should be considered:
65
43
66
-
>[!NOTE]
67
-
> After the scale set has been created, the backend port cannot be modified for a load balancing rule used by a health probe of the load balancer. To change the port, you can remove the health probe by updating the Azure virtual machine scale set, update the port and then configure the health probe again.
44
+
***Multiple virtual machine scale sets can't use the same load balancer**.
45
+
***Port Forwarding and inbound NAT rules**:
46
+
* Each virtual machine scale set must have an inbound NAT rule.
47
+
* After the scale set has been created, the backend port cannot be modified for a load balancing rule used by a health probe of the load balancer. To change the port, you can remove the health probe by updating the Azure virtual machine scale set, update the port and then configure the health probe again.
48
+
* When using the virtual machine scale set in the backend pool of the load balancer the default inbound NAT rules get created automatically.
49
+
***Load balancing rules**:
50
+
* When using the virtual machine scale set in the backend pool of the load balancer the default load balancing rule gets created automatically.
51
+
***Outbound rules**:
52
+
* To create outbound rule for a backend pool which is already referenced by a load balancing rule, you need to first mark **"Create implicit outbound rules"** as **No** in the portal when the inbound load balancing rule is created.
68
53
69
-
For more information on load balancer and virtual machine scale sets, see [Virtual networks and virtual machines in Azure](../../articles/virtual-machines/windows/network-overview.md).
The following methods can be used to deploy a virtual machine scale set with an existing Azure load balancer.
72
57
73
-
*[Configure a virtual machine scale set with an existing Azure Load Balancer using the Azure portal](../../articles/load-balancer/configure-vm-scale-set-portal.md).
74
-
*[Configure a virtual machine scale set with an existing Azure Load Balancer using Azure PowerShell](../../articles/load-balancer/configure-vm-scale-set-powershell.md).
75
-
*[Configure a virtual machine scale set with an existing Azure Load Balancer using the Azure CLI](../../articles/load-balancer/configure-vm-scale-set-cli.md).
58
+
*[Configure a virtual machine scale set with an existing Azure Load Balancer using the Azure portal](https://docs.microsoft.com/azure/load-balancer/configure-vm-scale-set-portal).
59
+
*[Configure a virtual machine scale set with an existing Azure Load Balancer using Azure PowerShell](https://docs.microsoft.com/azure/load-balancer/configure-vm-scale-set-powershell).
60
+
*[Configure a virtual machine scale set with an existing Azure Load Balancer using the Azure CLI](https://docs.microsoft.com/azure/load-balancer/configure-vm-scale-set-cli).
76
61
77
62
## Create a scale set that references an Application Gateway
78
63
To create a scale set that uses an application gateway, reference the backend address pool of the application gateway in the ipConfigurations section of your scale set as in this ARM template config:
Copy file name to clipboardExpand all lines: includes/virtual-machines-common-network-overview.md
+1-18Lines changed: 1 addition & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,24 +143,7 @@ This table lists the methods that you can use to create an internal load balance
143
143
144
144
### Virtual machine scale sets
145
145
146
-
When working with virtual machine scale sets and load balancer, the following should be considered:
147
-
148
-
***Multiple virtual machine scale sets can't use the same load balancer**.
149
-
***Port Forwarding and inbound NAT rules**:
150
-
* Each virtual machine scale set must have an inbound NAT rule.
151
-
* When using the virtual machine scale set in the backend pool of the load balancer the default inbound NAT rules get created automatically, this is by design.
152
-
***Load balancing rules**:
153
-
* When using the virtual machine scale set in the backend pool of the load balancer the default load balancing rule gets created automatically, this is by design.
154
-
***Outbound rules**:
155
-
* To create outbound rule for a backend pool which is already referenced by a load balancing rule, you need to first mark **"Create implicit outbound rules"** as **No** in the portal when the inbound load balancing rule is created.
The following methods can be used to deploy a virtual machine scale set with an existing Azure load balancer.
160
-
161
-
*[Configure a virtual machine scale set with an existing Azure Load Balancer using the Azure portal](../articles/load-balancer/configure-vm-scale-set-portal.md).
162
-
*[Configure a virtual machine scale set with an existing Azure Load Balancer using Azure PowerShell](../articles/load-balancer/configure-vm-scale-set-powershell.md).
163
-
*[Configure a virtual machine scale set with an existing Azure Load Balancer using the Azure CLI](../articles/load-balancer/configure-vm-scale-set-cli.md).
146
+
For more information on load balancer and virtual machine scale sets, see [Networking for Azure virtual machine scale sets](https://docs.microsoft.com/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking).
0 commit comments