Skip to content

Commit 1c36bd8

Browse files
committed
freshness
1 parent 93800f5 commit 1c36bd8

File tree

2 files changed

+12
-9
lines changed

2 files changed

+12
-9
lines changed
-623 Bytes
Loading

articles/network-watcher/network-watcher-next-hop-overview.md

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,22 @@
11
---
2-
title: Next hop
2+
title: Next hop overview
33
titleSuffix: Azure Network Watcher
44
description: Learn about Azure Network Watcher next hop capability that you can use to diagnose virtual machine routing problems.
5-
services: network-watcher
65
author: halkazwini
7-
ms.service: network-watcher
8-
ms.topic: conceptual
9-
ms.date: 03/28/2023
106
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.
1212
---
1313

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.
1519

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.
1720

1821
:::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.":::
1922

@@ -32,6 +35,6 @@ Network Watcher returns the following next hop types:
3235

3336
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).
3437

35-
## Next steps
38+
## Next step
3639

3740
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

Comments
 (0)