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
- content: "To capture traffic on a VM, Azure Network Watcher requires:"
17
-
choices:
18
-
- content: "Network Watcher Agent VM Extension"
19
-
isCorrect: true
20
-
explanation: "The Network Watcher Agent VM Extension is required when you capture traffic on a VM. It's automatically installed when you start a packet capture session in the Azure portal."
21
-
- content: "Azure Traffic Manager"
22
-
isCorrect: false
23
-
explanation: "The Network Watcher Agent VM Extension is required when you capture traffic on a VM. It's automatically installed when you start a packet capture session in the Azure portal."
24
-
- content: "An Azure storage account"
25
-
isCorrect: false
26
-
explanation: "The Network Watcher Agent VM Extension is required when you capture traffic on a VM. It's automatically installed when you start a packet capture session in the Azure portal."
27
-
- content: "To resolve latency issues on the network, which Azure Network Watcher features can you use?"
28
-
choices:
29
-
- content: "IP flow verify"
30
-
isCorrect: false
31
-
explanation: "IP flow verify checks if packets are allowed or denied to or from a virtual machine, but it doesn't show latencies. Use the connection troubleshoot tool to diagnose latencies."
32
-
- content: "Next hop"
33
-
isCorrect: false
34
-
explanation: "Next hop shows the type and IP address of the next hop in a network route, but it doesn't show latencies. Use the connection troubleshoot tool to diagnose latencies."
35
-
- content: "Connection troubleshoot"
36
-
isCorrect: true
37
-
explanation: "Connection troubleshoot displays the latency associated with each hop in a route."
- content: "To capture traffic on a virtual machine (VM), Azure Network Watcher requires:"
17
+
choices:
18
+
- content: "Network Watcher Agent VM Extension"
19
+
isCorrect: true
20
+
explanation: "The Network Watcher Agent VM Extension is required when you capture traffic on a VM. It's automatically installed when you start a packet capture session in the Azure portal."
21
+
- content: "Azure Traffic Manager"
22
+
isCorrect: false
23
+
explanation: "The Network Watcher Agent VM Extension is required when you capture traffic on a VM. It's automatically installed when you start a packet capture session in the Azure portal."
24
+
- content: "An Azure storage account"
25
+
isCorrect: false
26
+
explanation: "The Network Watcher Agent VM Extension is required when you capture traffic on a VM. It's automatically installed when you start a packet capture session in the Azure portal."
27
+
- content: "To resolve latency issues on the network, which Azure Network Watcher features can you use?"
28
+
choices:
29
+
- content: "IP flow verify"
30
+
isCorrect: false
31
+
explanation: "IP flow verify checks if packets are allowed or denied to or from a virtual machine, but it doesn't show latencies. Use the connection troubleshoot tool to diagnose latencies."
32
+
- content: "Next hop"
33
+
isCorrect: false
34
+
explanation: "Next hop shows the type and IP address of the next hop in a network route, but it doesn't show latencies. Use the connection troubleshoot tool to diagnose latencies."
35
+
- content: "Connection troubleshoot"
36
+
isCorrect: true
37
+
explanation: "Connection troubleshoot displays the latency associated with each hop in a route."
You can create complex and flexible setups in Azure that connect many virtual machines (VMs) to meet your needs. Just like in an on-premises network, configuration errors can result in problems that are challenging to troubleshoot. When you have to diagnose network problems in Azure, use Azure Network Watcher.
2
2
3
-
Suppose you're the Azure architect for an engineering company. You've deployed a VM in Azure, and the VM has network connectivity issues. You want to learn how to troubleshoot and fix the problem so you can help your colleagues to do the same if they face similar issues in the future.
3
+
Suppose you're the Azure architect for an engineering company. You deployed a VM in Azure, and the VM has network connectivity issues. You want to learn how to troubleshoot and fix the problem so you can help your colleagues to do the same if they face similar issues in the future.
4
4
5
-
In this module, you'll learn about core Network Watcher features. Engineers use Network Watcher to monitor, diagnose, and gain insight into their network health and performance with metrics. You can break down the elements into four areas: monitoring, network diagnostic tools, metrics, and logs.
5
+
In this module, you learn about core Network Watcher features. Engineers use Network Watcher to monitor, diagnose, and gain insight into their network health and performance with metrics. You can break down the elements into four areas: monitoring, network diagnostic tools, metrics, and logs.
6
6
7
-
By the end of this module, you'll be able to troubleshoot connectivity problems by using Network Watcher so that you can fix them.
7
+
By the end of this module, you're able to troubleshoot connectivity problems by using Network Watcher so that you can fix them.
8
8
9
9
## Learning objectives
10
10
11
-
- Identify the tools available to manage and troubleshoot network connectivity in Azure
12
-
- Select the proper tool to manage and troubleshoot network connectivity for various use cases
11
+
- Identify the tools available to manage and troubleshoot network connectivity in Azure.
12
+
- Select the proper tool to manage and troubleshoot network connectivity for various use cases.
13
13
14
14
## Prerequisites
15
15
16
-
- Basic familiarity with Azure networking concepts such as IP addressing, subnetting, routing, and network security groups
17
-
- Basic familiarity with Azure network integration concepts such as VPNs, Azure ExpressRoute, and peering
16
+
- Basic familiarity with Azure networking concepts such as IP addressing, subnetting, routing, and network security groups.
17
+
- Basic familiarity with Azure network integration concepts such as VPNs, Azure ExpressRoute, and peering.
Copy file name to clipboardExpand all lines: learn-pr/azure/troubleshoot-azure-network-infrastructure/includes/2-troubleshoot-networking-with-network-watcher.md
+21-15Lines changed: 21 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ Azure Network Watcher includes several tools you can use to monitor your virtual
2
2
3
3
In your engineering company, you want to help your staff to choose the right Network Watcher tool for each troubleshooting task. They need to understand all the options available and the kinds of problems that each tool can solve.
4
4
5
-
Here, you'll look at the Network Watcher tool categories, the tools in each category, and how each tool is applied in example use cases.
5
+
Here, you look at the Network Watcher tool categories, the tools in each category, and how each tool is applied in example use cases.
6
6
7
7
## What is Network Watcher?
8
8
@@ -12,7 +12,7 @@ Network Watcher is an Azure service that combines tools in a central place to di
12
12
- Network diagnostic tools
13
13
- Traffic logging tools
14
14
15
-
With tools to monitor for and diagnose problems, Network Watcher gives you a centralized hub for identifying network glitches, CPU spikes, connectivity problems, memory leaks, and other issues before they affect your business.
15
+
Network Watcher has tools to monitor for and diagnose problems. It gives you a centralized hub for identifying network glitches, CPU spikes, connectivity problems, memory leaks, and other issues before they affect your business.
16
16
17
17
## Network Watcher monitoring tools
18
18
@@ -49,7 +49,7 @@ You use the Azure portal to view the topology of an Azure network. In the Azure
49
49
50
50
The Connection Monitor tool provides a way to check that connections work between Azure resources. Use this tool to verify that two VMs can communicate if you want them to.
51
51
52
-
This tool also measures the latency between resources. It can catch changes that will affect connectivity, such as changes to the network configuration or changes to network security group (NSG) rules. It can probe VMs at regular intervals to look for failures or changes.
52
+
This tool also measures the latency between resources. It can catch changes that affect connectivity, such as changes to the network configuration or changes to network security group (NSG) rules. It can probe VMs at regular intervals to look for failures or changes.
53
53
54
54
If there's an issue, Connection Monitor tells you why it occurred and how to fix it. Along with monitoring VMs, Connection Monitor can examine an IP address or fully qualified domain name (FQDN).
55
55
@@ -63,7 +63,7 @@ You can use Network Performance Monitor to monitor endpoint-to-endpoint connecti
63
63
64
64
- Between branches and datacenters
65
65
- Between virtual networks
66
-
- For your connections between on-premises and the cloud
66
+
- For your connections, between on-premises and the cloud
67
67
- For Azure ExpressRoute circuits
68
68
69
69
## Network Watcher diagnostic tools
@@ -88,9 +88,15 @@ This tool uses a 5-tuple packet parameter-based verification mechanism to detect
88
88
89
89
### What is the NSG diagnostic tool?
90
90
91
-
The Network Security Group (NSG) Diagnostics tool provides detailed information to help you understand and debug the security configuration of your network.
91
+
The Network Security Group (NSG) Diagnostics tool provides detailed information to help you understand and debug the security configuration of your network.
92
92
93
-
For a given source-destination pair, the tool shows you the NSGs that will be traversed, the rules that will be applied in each NSG, and the final allow/deny status for the flow. By understanding which traffic flows will be allowed or denied in your Azure Virtual Network, you can determine if your NSG rules are configured correctly.
93
+
For a given source-destination pair, the tool shows you:
94
+
95
+
- The NSGs that will be traversed.
96
+
- The rules that will be applied in each NSG.
97
+
- The final allow/deny status for the flow.
98
+
99
+
By understanding which traffic flows will be allowed or denied in your Azure Virtual Network, you can determine if your NSG rules are configured correctly.
94
100
95
101
### What is the next hop tool?
96
102
@@ -104,7 +110,7 @@ The effective security rules tool in Network Watcher displays all the effective
104
110
105
111
Network security groups (NSGs) are used in Azure networks to filter packets based on their source and destination IP address and port numbers. NSGs are vital to security because they help you carefully control the surface area of the VMs that users can access. Keep in mind, though, that a mistakenly configured NSG rule might prevent legitimate communication. As a result, NSGs are a frequent source of network problems.
106
112
107
-
For example, if two VMs can't communicate because an NSG rule blocks them, it can be difficult to diagnose which rule is causing the problem. You'll use the effective security rules tool in Network Watcher to display all the effective NSG rules and help you diagnose which rule is causing the specific problem.
113
+
For example, if two VMs can't communicate because an NSG rule blocks them, it can be difficult to diagnose which rule is causing the problem. You use the effective security rules tool in Network Watcher to display all the effective NSG rules and help you diagnose which rule is causing the specific problem.
108
114
109
115
To use the tool, you choose a VM and its network adapter. The tool displays all the NSG rules that apply to that adapter. It's easy to determine a blocking rule by viewing this list.
110
116
@@ -130,7 +136,7 @@ If the connection is successful, information about the communication appears, in
130
136
- The number of probe packets sent.
131
137
- The number of hops in the complete route to the destination.
132
138
133
-
If the connection is unsuccessful, you'll see details of the fault. Fault types include:
139
+
If the connection is unsuccessful, you see details of the fault. Fault types include:
134
140
135
141
-**CPU**. The connection failed because of high CPU utilization.
136
142
-**Memory**. The connection failed because of high memory utilization.
@@ -166,7 +172,7 @@ Network Watcher includes the two following traffic tools:
166
172
167
173
### What is the flow logs tool?
168
174
169
-
Flow logs allows you to log information about IP traffic flowing through a network security group. Flow logs stores data in Azure storage. Flow data is sent to Azure Storage from where you can access it and export it to any visualization tool, security information and event management (SIEM) solution, or intrusion detection system (IDS) of your choice. You can use this data to analyze traffic patterns and troubleshoot connectivity issues.
175
+
Flow logs allows you to log information about IP traffic flowing through a network security group. Flow logs stores data in Azure storage. From Azure Storage, you can access your flow data and export it to any visualization tool, security information and event management (SIEM) solution, or intrusion detection system (IDS) of your choice. You can use this data to analyze traffic patterns and troubleshoot connectivity issues.
170
176
171
177
Flow logs use cases can be categorized into two types. Network monitoring and usage monitoring and optimization.
172
178
@@ -180,7 +186,7 @@ Flow logs use cases can be categorized into two types. Network monitoring and us
180
186
#### Usage monitoring and optimization
181
187
182
188
- Identify top talkers in your network.
183
-
-Combine with GeoIP data to identify cross-region traffic.
189
+
-Identify cross-region traffic by combing flow data with GeoIP data.
184
190
- Understand traffic growth for capacity forecasting.
185
191
- Use data to remove overly restrictive traffic rules.
186
192
@@ -201,7 +207,7 @@ Let's examine some scenarios that you can investigate and troubleshoot by using
201
207
202
208
### There are connectivity issues in a single-VM network
203
209
204
-
Your colleagues have deployed a VM in Azure and are having network connectivity issues. Your colleagues are trying to use Remote Desktop Protocol (RDP) to connect to the virtual machine, but they can't connect.
210
+
Your colleagues deployed a VM in Azure and are having network connectivity issues. Your colleagues are trying to use Remote Desktop Protocol (RDP) to connect to the virtual machine, but they can't connect.
205
211
206
212
To troubleshoot this issue, use the IP flow verify tool. This tool lets you specify a local and remote port, the protocol (TCP/UDP), the local IP, and the remote IP to check the connection status. It also lets you specify the direction of the connection (inbound or outbound). IP flow verify runs a logical test on the rules in place on your network.
207
213
@@ -211,17 +217,17 @@ Suppose the result shows that access was denied because of the NSG rule **Defaul
211
217
212
218
### A VPN connection isn't working
213
219
214
-
Your colleagues have deployed VMs in two virtual networks and can't connect between them.
220
+
Your colleagues deployed VMs in two virtual networks and can't connect between them.
215
221
216
222
To troubleshoot a VPN connection, use Azure VPN troubleshoot. This tool runs diagnostics on a virtual network gateway connection, and returns a health diagnosis. You can run this tool from the Azure portal, PowerShell, or the Azure CLI.
217
223
218
-
When you run the tool, it checks the gateway for common issues and returns the health diagnosis. You can also view the log file to get more information. The diagnosis will show whether the VPN connection is working. If the VPN connection isn't working, VPN troubleshoot will suggest ways to resolve the issue.
224
+
When you run the tool, it checks the gateway for common issues and returns the health diagnosis. You can also view the log file to get more information. The diagnosis shows whether the VPN connection is working. If the VPN connection isn't working, VPN troubleshoot suggests ways to resolve the issue.
219
225
220
-
Suppose the diagnosis shows a key mismatch. To resolve the problem, reconfigure the remote gateway to make sure the keys match on both ends. Pre-shared keys are case-sensitive.
226
+
Suppose the diagnosis shows a key mismatch. To resolve the problem, reconfigure the remote gateway to make sure the keys match on both ends. Preshared keys are case-sensitive.
221
227
222
228
### No servers are listening on designated destination ports
223
229
224
-
Your colleagues have deployed VMs in a single virtual network and can't connect between them.
230
+
Your colleagues deployed VMs in a single virtual network and can't connect between them.
225
231
226
232
Use the connection troubleshoot tool to troubleshoot this issue. In this tool, you specify the local and remote VMs. In the probe setting, you can choose a specific port.
0 commit comments