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/network-watcher-next-hop-overview.md
+12-9Lines changed: 12 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,22 @@
1
1
---
2
-
title: Next hop
2
+
title: Next hop overview
3
3
titleSuffix: Azure Network Watcher
4
4
description: Learn about Azure Network Watcher next hop capability that you can use to diagnose virtual machine routing problems.
5
-
services: network-watcher
6
5
author: halkazwini
7
-
ms.service: network-watcher
8
-
ms.topic: conceptual
9
-
ms.date: 03/28/2023
10
6
ms.author: halkazwini
11
-
ms.custom: template-concept, engagement-fy23
7
+
ms.service: network-watcher
8
+
ms.topic: concept-article
9
+
ms.date: 03/13/2024
10
+
11
+
#CustomerIntent: As an Azure administrator, I want to learn about Next hop feature so I can use it to get the next hop information of any virtual machine (VM) experiencing routing issues to be able to diagnose and fix the issue.
12
12
---
13
13
14
-
# Azure Network Watcher next hop
14
+
# Next hop overview
15
+
16
+
Next hop is a feature of Azure Network Watcher that gives you the *Next hop type*, *IP address*, and *Route table ID* of a specific destination IP address. Knowing the next hop information helps you determine if traffic is being directed to the intended destination, or whether the traffic is being dropped. An improper configuration of routes, where traffic is directed to an on-premises location or a network virtual appliance can lead to connectivity issues.
17
+
18
+
If the route is defined using a user-defined route, next hop returns the route table that has the route. Otherwise, it returns *System Route* as the route table.
15
19
16
-
Traffic from a virtual machine (VM) is sent to a destination based on the effective routes associated with the virtual machines' network interface (NIC). Azure Network Watcher next hop gives you the *Next hop type*, *IP address*, and *Route table ID* of a specific destination IP address. Knowing the next hop helps you determine if traffic is being directed to the intended destination, or whether the traffic is being sent nowhere. An improper configuration of routes, where traffic is directed to an on-premises location, or a network virtual appliance, can lead to connectivity issues. If the route is defined using a user-defined route, the route table that has the route is returned. Otherwise, next hop returns *System Route* as the route table.
17
20
18
21
:::image type="content" source="./media/network-watcher-next-hop-overview/next-hop-view.png" alt-text="Screenshot of Azure Network Watcher next hop view in Azure portal.":::
19
22
@@ -32,6 +35,6 @@ Network Watcher returns the following next hop types:
32
35
33
36
To learn more about each next hop type, see [Virtual network traffic routing](../virtual-network/virtual-networks-udr-overview.md?toc=%2fazure%2fnetwork-watcher%2ftoc.json).
34
37
35
-
## Next steps
38
+
## Next step
36
39
37
40
To learn how to use next hop to diagnose virtual machine routing problems, see Diagnose VM network routing problems using the [Azure portal](diagnose-vm-network-routing-problem.md), [PowerShell](diagnose-vm-network-routing-problem-powershell.md), or the [Azure CLI](diagnose-vm-network-routing-problem-cli.md).
0 commit comments