Skip to content

Commit 205d289

Browse files
halkazwinihalkazwini
committed
fix blocking issue
1 parent c04ff22 commit 205d289

File tree

1 file changed

+60
-4
lines changed

1 file changed

+60
-4
lines changed

‎articles/network-watcher/network-watcher-connectivity-overview.md

Lines changed: 60 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,11 @@ Connection troubleshoot provides the capability to check TCP or ICMP connections
3636
- Azure Bastion instances
3737
- Application gateways (except v1)
3838

39+
> [!IMPORTANT]
40+
> Connection troubleshoot requires that the virtual machine you troubleshoot from has the `AzureNetworkWatcherExtension` extension installed. The extension is not required on the destination virtual machine.
41+
> - 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).
42+
> - 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).
43+
3944
Connection troubleshoot can test connections to any of these destinations:
4045

4146
- Virtual machines
@@ -57,10 +62,61 @@ Connection troubleshoot can detect the following types of issues that can impact
5762
- Missing address resolution protocol entries for Azure ExpressRoute circuits
5863
- Servers not listening on designated destination ports
5964

60-
> [!IMPORTANT]
61-
> Connection troubleshoot requires that the virtual machine you troubleshoot from has the `AzureNetworkWatcherExtension` extension installed. The extension is not required on the destination virtual machine.
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).
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).
65+
## Response
66+
67+
The following table shows the properties returned when connection troubleshoot has finished running.
68+
69+
|**Property** |**Description** |
70+
|---------|---------|
71+
|ConnectionStatus | The status of the connectivity check. Possible results are **Reachable** and **Unreachable**. |
72+
|AvgLatencyInMs | Average latency during the connectivity check, in milliseconds. (Only shown if check status is reachable) |
73+
|MinLatencyInMs | Minimum latency during the connectivity check, in milliseconds. (Only shown if check status is reachable) |
74+
|MaxLatencyInMs | Maximum latency during the connectivity check, in milliseconds. (Only shown if check status is reachable) |
75+
|ProbesSent | Number of probes sent during the check. Max value is 100. |
76+
|ProbesFailed | Number of probes that failed during the check. Max value is 100. |
77+
|Hops | Hop by hop path from source to destination. |
78+
|Hops[].Type | Type of resource. Possible values are **Source**, **VirtualAppliance**, **VnetLocal**, and **Internet**. |
79+
|Hops[].Id | Unique identifier of the hop.|
80+
|Hops[].Address | IP address of the hop.|
81+
|Hops[].ResourceId | ResourceID of the hop if the hop is an Azure resource. If it's an internet resource, ResourceID is **Internet**. |
82+
|Hops[].NextHopIds | The unique identifier of the next hop taken.|
83+
|Hops[].Issues | A collection of issues that were encountered during the check at that hop. If there were no issues, the value is blank.|
84+
|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.|
85+
|Hops[].Issues[].Severity | The severity of the issue detected. Possible values are **Error** and **Warning**. |
86+
|Hops[].Issues[].Type |The type of issue found. Possible values are: <br/>**CPU**<br/>**Memory**<br/>**GuestFirewall**<br/>**DnsResolution**<br/>**NetworkSecurityRule**<br/>**UserDefinedRoute** |
87+
|Hops[].Issues[].Context |Details regarding the issue found.|
88+
|Hops[].Issues[].Context[].key |Key of the key value pair returned.|
89+
|Hops[].Issues[].Context[].value |Value of the key value pair returned.|
90+
91+
The following is an example of an issue found on a hop.
92+
93+
```json
94+
"Issues": [
95+
{
96+
"Origin": "Outbound",
97+
"Severity": "Error",
98+
"Type": "NetworkSecurityRule",
99+
"Context": [
100+
{
101+
"key": "RuleName",
102+
"value": "UserRule_Port80"
103+
}
104+
]
105+
}
106+
]
107+
```
108+
## Fault types
109+
110+
Connection troubleshoot returns fault types about the connection. The following table provides a list of the current fault types returned.
111+
112+
|**Type** |**Description** |
113+
|---------|---------|
114+
|CPU | High CPU utilization. |
115+
|Memory | High Memory utilization. |
116+
|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. |
117+
|DNSResolution | DNS resolution failed for the destination address. |
118+
|NetworkSecurityRule | Traffic is blocked by an NSG Rule (Rule is returned) |
119+
|UserDefinedRoute|Traffic is dropped due to a user defined or system route. |
64120

65121
### Next steps
66122

0 commit comments

Comments
 (0)