Skip to content

Commit 33cdb1f

Browse files
committed
added vm nic chaining to portal doc
1 parent d7d2aff commit 33cdb1f

File tree

3 files changed

+29
-4
lines changed

3 files changed

+29
-4
lines changed
106 KB
Loading
122 KB
Loading

articles/load-balancer/tutorial-gateway-portal.md

Lines changed: 29 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -226,7 +226,7 @@ In this section, you'll create the configuration and deploy the gateway load bal
226226
| IP Version | Select **IPv4** or **IPv6** depending on your requirements. |
227227
| Frontend IP address | Select **MyFrontend**. |
228228
| Backend pool | Select **myBackendPool**. |
229-
| Health probe | Select **Create new**. </br> In **Name**, enter **myHealthProbe**. </br> Select **HTTP** in **Protocol**. </br> Leave the rest of the defaults, and select **OK**. |
229+
| 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**. |
230230
| Session persistence | Select **None**. |
231231

232232
:::image type="content" source="./media/tutorial-gateway-portal/add-load-balancing-rule.png" alt-text="Screenshot of create load-balancing rule." border="true":::
@@ -237,10 +237,11 @@ In this section, you'll create the configuration and deploy the gateway load bal
237237

238238
19. Select **Create**.
239239

240-
## Add network virtual appliances to the Gateway Load Balancer backend pool
241-
Deploy NVAs through the Azure Marketplace. Once deployed, add the NVA virtual machines to the backend pool by navigating to the Backend pools tab of your Gateway Load Balancer.
240+
## Add network virtual appliances to the gateway load balancer backend pool
242241

243-
## Chain load balancer frontend to gateway load balancer
242+
Deploy NVAs through the Azure Marketplace. Once deployed, add the NVA virtual machines to the backend pool by navigating to the backend pools tab of your gateway load balancer.
243+
244+
## Chain load balancer frontend to the gateway load balancer
244245

245246
In this example, you'll chain the frontend of a standard load balancer to the gateway load balancer.
246247

@@ -262,6 +263,30 @@ You'll add the frontend to the frontend IP of an existing load balancer in your
262263

263264
:::image type="content" source="./media/tutorial-gateway-portal/select-gateway-load-balancer.png" alt-text="Screenshot of addition of gateway load balancer to frontend IP." border="true":::
264265

266+
## Chain a VM NIC configuration to the gateway load balancer
267+
268+
Instead of chaining a load balancer frontend to the gateway load balancer, you can chain a virtual machine's NIC configuration to the gateway load balancer. To chain the NIC configuration, add the configuration to the gateway load balancer frontend.
269+
270+
> [!IMPORTANT]
271+
> A virtual machine must have a public IP address assigned before attempting to chain the NIC configuration to the frontend of the gateway load balancer.
272+
273+
1. In the search box in the Azure portal, enter **Virtual machine**. In the search results, select **Virtual Machines**.
274+
275+
2. In **Virtual machines**, select the virtual machine that you want to add to the gateway load balancer. In this example, the virtual machine is named **myVM1**.
276+
277+
3. In the overview of the virtual machine, select **Networking** in **Settings**.
278+
279+
4. In **Networking**, select the name of the network interface attached to the virtual machine. In this example, it's **myvm1229**.
280+
281+
:::image type="content" source="./media/tutorial-gateway-portal/vm-nic.png" alt-text="Screenshot of virtual machine networking overview." border="true":::
282+
283+
5. In the network interface page, select **IP configurations** in **Settings**.
284+
285+
6. Select **myFrontend** in the **Gateway Load balancer** pull-down box.
286+
287+
:::image type="content" source="./media/tutorial-gateway-portal/vm-nic-gw-lb.png" alt-text="Screenshot of nic IP configuration." border="true":::
288+
289+
7. Select **Save**.
265290

266291
## Clean up resources
267292

0 commit comments

Comments
 (0)