Skip to content

Commit e93e703

Browse files
author
Michael Bender
committed
updates to backend doc
1 parent b25e0c1 commit e93e703

File tree

2 files changed

+21
-2
lines changed

2 files changed

+21
-2
lines changed

articles/load-balancer/cross-subscription-how-to-attach-backend.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,25 @@ $LB = Get-AzLoadBalancer @LBinfo
9494
```
9595
# [Azure CLI](#tab/azurecli)
9696

97+
With Azure CLI, you create a load balancer with [`az network lb create`](/cli/azure/network/lb#az_network_lb_create) and update the backend pool. This example configures the following resources:
98+
99+
- A frontend IP address that receives the incoming network traffic on the load balancer.
100+
- A backend address pool where the frontend IP sends the load balanced network traffic.
101+
102+
```azurecli
103+
104+
# Create a load balancer
105+
az network lb create --resource-group myResourceGroupLB --name myLoadBalancer --sku Standard --public-ip-address myPublicIP --frontend-ip-name myFrontEnd --backend-pool-name BackendPool1 --tags 'IsRemoteFrontend=true'
106+
107+
```
108+
109+
In order to utilize the cross-subscription feature of Azure load balancer, backend pools need to have the syncMode property enabled and a virtual network reference. This section updates the backend pool created prior by attaching the cross-subscription virtual network and enabling the syncMode property.
110+
111+
```azurecli
112+
## Configure the backend address pool and syncMode property
113+
az network lb address-pool update --lb-name myLoadBalancer --resource-group myResourceGroupLB -n myResourceGroupLB --vnet ‘/subscriptions/<subscription A ID>/resourceGroups/{resource group name}/providers/Microsoft.Network/virtualNetwork/{VNet name}’ --sync-mode Automatic
114+
```
115+
97116
---
98117

99118
[!INCLUDE [load-balancer-cross-subscription-health-probe-rules](../../includes/load-balancer-cross-subscription-health-probe-rules.md)]

articles/load-balancer/cross-subscription-how-to-attach-frontend.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -190,13 +190,13 @@ With Azure CLI, you create a load balancer with [`az network lb create`](/cli/az
190190
# Create a load balancer
191191
192192
az network lb create --resource-group myResourceGroupLB --name myLoadBalancer --sku Standard --public-ip-address '/subscriptions/<subscription A ID>/resourceGroups/{resource group name} /providers/Microsoft.Network/publicIPAddresses/{public IP address name}’ --frontend-ip-name myFrontEnd --backend-pool-name MyBackendPool --tags 'IsRemoteFrontend=true'
193-
194193
```
194+
195195
In order to utilize the cross-subscription feature of Azure load balancer, backend pools need to have the syncMode property enabled and a virtual network reference. This section updates the backend pool created prior by attaching the cross-subscription virtual network and enabling the syncMode property.
196196

197197
```azurecli
198198
## Configure the backend address pool and syncMode property
199-
az network lb address-pool update --lb-name myLoadBalancer --resource-group myResourceGroupLB -n myResourceGroupLB --vnet ‘/subscriptions/<subscription A ID>/resourceGroups/{resource group name} /providers/Microsoft.Network/virtualNetwork/{VNet name}’ --sync-mode Automatic
199+
az network lb address-pool update --lb-name myLoadBalancer --resource-group myResourceGroupLB -n myResourceGroupLB --vnet ‘/subscriptions/<subscription A ID>/resourceGroups/{resource group name}/providers/Microsoft.Network/virtualNetwork/{VNet name}’ --sync-mode Automatic
200200
```
201201

202202
---

0 commit comments

Comments
 (0)