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-connectivity-overview.md
+11-66Lines changed: 11 additions & 66 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,18 +20,17 @@ The connection troubleshoot feature of Azure Network Watcher helps reduce the am
20
20
21
21
Connection troubleshoot reduces the Mean Time To Resolution (MTTR) by providing a comprehensive method of performing all connection major checks to detect issues pertaining to network security groups, user-defined routes, and blocked ports. It provides the following results with actionable insights where a step-by-step guide or corresponding documentation is provided for faster resolution:
22
22
23
-
- Connectivity test with different destination types (VM, URI, FQDN, or IP Address).
24
-
- Configuration issues that impact reachability.
25
-
- All possible hop by hop paths from the source to destination.
26
-
- Hop by hop latency.
27
-
- Latency (minimum, maximum, and average between source and destination).
28
-
- Graphical topology view from source to destination.
29
-
- Number of probes failed during the connection troubleshoot check.
30
-
23
+
- Connectivity test with different destination types (VM, URI, FQDN, or IP Address)
24
+
- Configuration issues that impact reachability
25
+
- All possible hop by hop paths from the source to destination
26
+
- Hop by hop latency
27
+
- Latency (minimum, maximum, and average between source and destination)
28
+
- Graphical topology view from source to destination
29
+
- Number of probes failed during the connection troubleshoot check
31
30
32
31
## Supported source and destination types
33
32
34
-
Connection troublehoot provides the capability to check TCP or ICMP connections from any of these Azure resources:
33
+
Connection troubleshoot provides the capability to check TCP or ICMP connections from any of these Azure resources:
35
34
36
35
- Virtual machines
37
36
- Azure Bastion instances
@@ -44,6 +43,8 @@ Connection troubleshoot can test connections to any of these destinations:
44
43
- Uniform resource identifiers (URIs)
45
44
- IP addresses
46
45
46
+
## Issues detected by connection troubleshoot
47
+
47
48
Connection troubleshoot can detect the following types of issues that can impact connectivity:
48
49
49
50
- High VM CPU utilization
@@ -61,63 +62,7 @@ Connection troubleshoot can detect the following types of issues that can impact
61
62
> - To install the extension on a Windows VM, see [Azure Network Watcher Agent virtual machine extension for Windows](../virtual-machines/extensions/network-watcher-windows.md?toc=%2fazure%2fnetwork-watcher%2ftoc.json).
62
63
> - To install the extension on a Linux VM, see [Azure Network Watcher Agent virtual machine extension for Linux](../virtual-machines/extensions/network-watcher-linux.md?toc=%2fazure%2fnetwork-watcher%2ftoc.json).
63
64
64
-
## Response
65
-
66
-
The following table shows the properties returned when connection troubleshoot has finished running.
67
-
68
-
|**Property**|**Description**|
69
-
|---------|---------|
70
-
|ConnectionStatus | The status of the connectivity check. Possible results are **Reachable** and **Unreachable**. |
71
-
|AvgLatencyInMs | Average latency during the connectivity check, in milliseconds. (Only shown if check status is reachable) |
72
-
|MinLatencyInMs | Minimum latency during the connectivity check, in milliseconds. (Only shown if check status is reachable) |
73
-
|MaxLatencyInMs | Maximum latency during the connectivity check, in milliseconds. (Only shown if check status is reachable) |
74
-
|ProbesSent | Number of probes sent during the check. Max value is 100. |
75
-
|ProbesFailed | Number of probes that failed during the check. Max value is 100. |
76
-
|Hops | Hop by hop path from source to destination. |
77
-
|Hops[].Type | Type of resource. Possible values are **Source**, **VirtualAppliance**, **VnetLocal**, and **Internet**. |
78
-
|Hops[].Id | Unique identifier of the hop.|
79
-
|Hops[].Address | IP address of the hop.|
80
-
|Hops[].ResourceId | ResourceID of the hop if the hop is an Azure resource. If it's an internet resource, ResourceID is **Internet**. |
81
-
|Hops[].NextHopIds | The unique identifier of the next hop taken.|
82
-
|Hops[].Issues | A collection of issues that were encountered during the check at that hop. If there were no issues, the value is blank.|
83
-
|Hops[].Issues[].Origin | At the current hop, where issue occurred. Possible values are:<br/> **Inbound** - Issue is on the link from the previous hop to the current hop<br/>**Outbound** - Issue is on the link from the current hop to the next hop<br/>**Local** - Issue is on the current hop.|
84
-
|Hops[].Issues[].Severity | The severity of the issue detected. Possible values are **Error** and **Warning**. |
85
-
|Hops[].Issues[].Type |The type of issue found. Possible values are: <br/>**CPU**<br/>**Memory**<br/>**GuestFirewall**<br/>**DnsResolution**<br/>**NetworkSecurityRule**<br/>**UserDefinedRoute**|
86
-
|Hops[].Issues[].Context |Details regarding the issue found.|
87
-
|Hops[].Issues[].Context[].key |Key of the key value pair returned.|
88
-
|Hops[].Issues[].Context[].value |Value of the key value pair returned.|
89
-
90
-
The following is an example of an issue found on a Hop.
91
-
92
-
```json
93
-
"Issues": [
94
-
{
95
-
"Origin": "Outbound",
96
-
"Severity": "Error",
97
-
"Type": "NetworkSecurityRule",
98
-
"Context": [
99
-
{
100
-
"key": "RuleName",
101
-
"value": "UserRule_Port80"
102
-
}
103
-
]
104
-
}
105
-
]
106
-
```
107
-
## Fault types
108
-
109
-
The Connection troubleshoot feature returns fault types about the connection. The following table lists the current fault types returned.
110
-
111
-
|**Type**|**Description**|
112
-
|---------|---------|
113
-
|CPU | High CPU utilization. |
114
-
|Memory | High Memory utilization. |
115
-
|GuestFirewall | Traffic is blocked due to a virtual machine firewall configuration. <br><br> Note that a TCP ping is a unique use case in which, if there's no allowed rule, the firewall itself responds to the client's TCP ping request even though the TCP ping doesn't reach the target IP address/FQDN. This event isn't logged. If there's a network rule that allows access to the target IP address/FQDN, the ping request reaches the target server and its response is relayed back to the client. This event is logged in the Network rules log. |
116
-
|DNSResolution | DNS resolution failed for the destination address. |
117
-
|NetworkSecurityRule | Traffic is blocked by an NSG Rule (Rule is returned) |
118
-
|UserDefinedRoute|Traffic is dropped due to a user defined or system route. |
119
-
120
65
### Next steps
121
66
122
-
- Learn more about [Network Watcher](network-watcher-monitoring-overview.md)
67
+
- Learn more about [Network Watcher](network-watcher-monitoring-overview.md).
123
68
- Learn how to use connection troubleshoot using the [Azure portal](network-watcher-connectivity-portal.md), [PowerShell](network-watcher-connectivity-powershell.md), the [Azure CLI](network-watcher-connectivity-cli.md), or [REST API](network-watcher-connectivity-rest.md).
0 commit comments