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/network-watcher/diagnose-communication-problem-between-networks.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: halkazwini
7
7
ms.service: network-watcher
8
8
ms.topic: tutorial
9
9
ms.workload: infrastructure-services
10
-
ms.date: 02/23/2023
10
+
ms.date: 02/28/2023
11
11
ms.author: halkazwini
12
12
ms.custom: template-tutorial, engagement-fy23
13
13
# Customer intent: I need to determine why resources in a virtual network can't communicate with resources in a different virtual network over a VPN connection.
# Customer intent: I want to diagnose virtual machine (VM) network routing problem that prevents communication to different destinations.
13
13
---
14
14
15
15
# Tutorial: Diagnose a virtual machine network routing problem using the Azure portal
16
16
17
-
When you deploy a virtual machine (VM), Azure creates several [system default routes](/articles/virtual-network/virtual-networks-udr-overview.md#system-routes?toc=%2Fazure%2Fnetwork-watcher%2Ftoc.json&tabs=json) for it. You can create [custom routes](/articles/virtual-network/virtual-networks-udr-overview.md#custom-routes?toc=%2Fazure%2Fnetwork-watcher%2Ftoc.json&tabs=json) to override some of Azure's system routes. Sometimes, a custom route can result in a VM not being able to communicate with the intended destination. You can use Azure Network Watcher to troubleshoot and diagnose the VM routing problem that's preventing it from correctly communicating with other resources.
17
+
When you deploy a virtual machine (VM), Azure creates several [system default routes](/articles/virtual-network/virtual-networks-udr-overview.md#system-routes?toc=%2Fazure%2Fnetwork-watcher%2Ftoc.json&tabs=json) for it. You can create [custom routes](/articles/virtual-network/virtual-networks-udr-overview.md#custom-routes?toc=%2Fazure%2Fnetwork-watcher%2Ftoc.json&tabs=json) to override some of Azure's system routes. Sometimes, a custom route can result in a VM not being able to communicate with the intended destination. You can use Azure Network Watcher [next hop](network-watcher-next-hop-overview.md) capability to troubleshoot and diagnose the VM routing problem that's preventing it from correctly communicating with other resources.
18
18
19
19
In this tutorial, you learn how to:
20
20
@@ -40,7 +40,7 @@ Sign in to the [Azure portal](https://portal.azure.com).
40
40
41
41
In this section, you create a virtual network.
42
42
43
-
1. In the search box at the top of the portal, enter *virtual network*. Select **Virtual networks** in the search results.
43
+
1. In the search box at the top of the portal, enter *virtual networks*. Select **Virtual networks** in the search results.
44
44
45
45
:::image type="content" source="./media/diagnose-vm-network-routing-problem/virtual-network-azure-portal.png" alt-text="Screenshot shows searching for virtual networks in the Azure portal.":::
46
46
@@ -85,7 +85,7 @@ In this section, you create two virtual machines: **myVM** and **myNVA**. You us
85
85
86
86
### Create first virtual machine
87
87
88
-
1. In the search box at the top of the portal, enter *virtual machine*. Select **Virtual machines** in the search results.
88
+
1. In the search box at the top of the portal, enter *virtual machines*. Select **Virtual machines** in the search results.
89
89
90
90
2. Select **+ Create** and then select **Azure virtual machine**.
91
91
@@ -174,7 +174,7 @@ Use the next hop capability of Network Watcher to determine which route Azure is
174
174
175
175
To further analyze routing, review the effective routes for **myVM** network interface.
176
176
177
-
1. In the search box at the top of the portal, enter *virtual machine*. Select **Virtual machines** in the search results.
177
+
1. In the search box at the top of the portal, enter *virtual machines*. Select **Virtual machines** in the search results.
178
178
179
179
1. Under **Settings**, select **Networking**, then select the network interface.
180
180
@@ -198,7 +198,7 @@ Next, you create a static custom route to override Azure default system routes a
198
198
199
199
In this section, you create a static custom route (user-defined route) in a route table that forces all traffic destined outside the virtual network to a specific IP address. Forcing traffic to a virtual network appliance is a common scenario.
200
200
201
-
1. In the search box at the top of the portal, enter *route table*. Select **Route tables** in the search results.
201
+
1. In the search box at the top of the portal, enter *route tables*. Select **Route tables** in the search results.
202
202
203
203
1. Select **+ Create** to create a new route table. In the **Create Route table** page, enter or select the following values:
# Customer intent: I need to log the network traffic to and from a virtual machine (VM) so I can analyze it for anomalies.
@@ -290,11 +290,11 @@ When no more logging is needed, you can disable the NSG flow log that you previo
290
290
291
291
1. Select **NSG flow logs** under **Logs**.
292
292
293
-
1. Select the ellipsis **...** to the right of **myVM-nsg-myresourcegroup-flowlog** flow log or right-click it and select **Disable**. To resume logging, enable the flow log.
293
+
1. Select the ellipsis **...** to the right of **myVM-nsg-myresourcegroup-flowlog** flow log or right-click it and select **Disable**.
294
294
295
295
1. In **Disable NSG flow log**, select **Disable**.
296
296
297
-
:::image type="content" source="./media/network-watcher-nsg-flow-logging-portal/nsg-log-file.png" alt-text="Screenshot showing the nsg flow log disabled in the Azure portal.":::
297
+
:::image type="content" source="./media/network-watcher-nsg-flow-logging-portal/nsg-flow-log-disabled.png" alt-text="Screenshot showing the nsg flow log disabled in the Azure portal.":::
0 commit comments