Skip to content

Commit e6fc96d

Browse files
Merge pull request #266844 from anavinahar/patch-277
Update load-balancer-test-frontend-reachability.md
2 parents 9401397 + 1c74e4c commit e6fc96d

File tree

1 file changed

+24
-24
lines changed

1 file changed

+24
-24
lines changed

articles/load-balancer/load-balancer-test-frontend-reachability.md

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Test reachability of Azure Public Load Balancer front-ends with ping and traceroute
3-
description: Learn how to test Azure Public Load Balancer front-end IPv4 and IPv6 addresses for reachability from an Azure VM or an external device. Supports ping and traceroute.
2+
title: Test reachability of Azure Public Load Balancer frontends with ping and traceroute
3+
description: Learn how to test Azure Public Load Balancer frontend IPv4 and IPv6 addresses for reachability from an Azure VM or an external device. Supports ping and traceroute.
44
services: load-balancer
55
author: mbender-ms
66
ms.service: load-balancer
@@ -10,39 +10,39 @@ ms.author: mbender
1010
ms.custom: template-how-to
1111
---
1212

13-
# Test reachability of Azure Public Load Balancer front-ends with ping and traceroute
13+
# Test reachability of Azure Public Load Balancer frontends with ping and traceroute
1414

15-
Standard Public Azure Load Balancer front-end IPv4 and IPv6 addresses support testing reachability using ping and traceroute. Testing reachability of a load balancer front-end is useful for troubleshooting inbound connectivity issues to Azure resources. In this article, you learn how to use ping and traceroute for testing a front-end of an existing Standard public load balancer. It can be completed from an Azure Virtual Machine or from a device outside of Azure.
15+
Standard Public Azure Load Balancer frontend IPv4 and IPv6 addresses support testing reachability using ping and traceroute. Testing reachability of a load balancer frontend is useful for troubleshooting inbound connectivity issues to Azure resources. In this article, you learn how to use ping and traceroute for testing a frontend of an existing Standard public load balancer. It can be completed from an Azure Virtual Machine or from a device outside of Azure.
1616

1717
## Prerequisites
1818

1919
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) and access to the Azure portal.
2020

21-
- A standard public load balancer with an IPv4 and IPv6 front-end in your subscription. For more information on creating an Azure Load Balancer, see [Quickstart: Create a public load balancer](/azure/load-balancer/quickstart-load-balancer-standard-public-portal) to load balance VMs using the Azure portal.
21+
- A standard public load balancer with an IPv4 and IPv6 frontend in your subscription. For more information on creating an Azure Load Balancer, see [Quickstart: Create a public load balancer](/azure/load-balancer/quickstart-load-balancer-standard-public-portal) to load balance VMs using the Azure portal.
2222

2323
- An Azure Virtual Machine with a public IP address assigned to its network interface. For more information on creating a virtual machine with a public IP, see [Quickstart: Create a Windows virtual machine in the Azure portal](/azure/virtual-machines/windows/quick-create-portal).
2424

2525
> [!NOTE]
26-
> Testing inbound connectivity to Azure Load Balancer front-ends is only supported for public load balancers. Testing inbound connectivity to internal load balancer front-ends is not supported.
26+
> Testing inbound connectivity to Azure Load Balancer frontends is only supported for public load balancers. Testing inbound connectivity to internal load balancer frontends is not supported.
2727
2828
## Testing from a device outside of Azure
2929
### [Windows](#tab/windows-outside)
3030

31-
This section describes testing reachability of a standard load balancer front-end from a Windows device outside of Azure.
31+
This section describes testing reachability of a standard load balancer frontend from a Windows device outside of Azure.
3232

3333
### [Linux](#tab/linux-outside)
3434

35-
This section describes testing reachability of a standard load balancer front-end from a Linux device outside of Azure.
35+
This section describes testing reachability of a standard load balancer frontend from a Linux device outside of Azure.
3636

3737
---
3838

39-
### Test the load balancer's front-end
39+
### Test the load balancer's frontend
4040

41-
Choose either ping or traceroute to test reachability of a standard load balancer front-end from a device outside of Azure.
41+
Choose either ping or traceroute to test reachability of a standard load balancer frontend from a device outside of Azure.
4242

4343
### [Ping](#tab/ping/windows-outside)
4444

45-
Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Windows device outside of Azure:
45+
Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Windows device outside of Azure:
4646

4747
1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
4848
2. In the command prompt, type the following command:
@@ -55,7 +55,7 @@ Follow these steps to test reachability of a standard public load balancer front
5555

5656
### [Ping](#tab/ping/linux-outside)
5757

58-
Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Linux device outside of Azure:
58+
Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Linux device outside of Azure:
5959

6060
1. Open Terminal.
6161
2. Type the following command:
@@ -68,7 +68,7 @@ Follow these steps to test reachability of a standard public load balancer front
6868

6969
### [Traceroute](#tab/traceroute/windows-outside)
7070

71-
Follow these steps to test reachability of a standard public load balancer front-end using `tracert` from a Windows device outside of Azure:
71+
Follow these steps to test reachability of a standard public load balancer frontend using `tracert` from a Windows device outside of Azure:
7272

7373
1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
7474
2. In the command prompt, type the following command:
@@ -81,7 +81,7 @@ Follow these steps to test reachability of a standard public load balancer front
8181

8282
### [Traceroute](#tab/traceroute/linux-outside)
8383

84-
Follow these steps to test reachability of a standard public load balancer front-end using `traceroute` from a Linux device outside of Azure:
84+
Follow these steps to test reachability of a standard public load balancer frontend using `traceroute` from a Linux device outside of Azure:
8585

8686
1. Open Terminal.
8787
2. Type the following command:
@@ -96,7 +96,7 @@ Follow these steps to test reachability of a standard public load balancer front
9696

9797
## Testing from an Azure Virtual Machine
9898

99-
This section describes how to test reachability of a standard public load balancer front-end from an Azure Virtual Machine. First, you create an inbound Network Security Group (NSG) rule on the virtual machine to allow ICMP traffic. Then, you test reachability of the front-end of the load balancer from the virtual machine with ping or traceroute.
99+
This section describes how to test reachability of a standard public load balancer frontend from an Azure Virtual Machine. First, you create an inbound Network Security Group (NSG) rule on the virtual machine to allow ICMP traffic. Then, you test reachability of the frontend of the load balancer from the virtual machine with ping or traceroute.
100100

101101
### Configure inbound NSG rule
102102

@@ -130,26 +130,26 @@ This section describes how to test reachability of a standard public load balanc
130130

131131
### [Windows](#tab/windowsvm)
132132

133-
This section describes testing reachability of a standard load balancer front-end from a Windows Virtual Machine on Azure.
133+
This section describes testing reachability of a standard load balancer frontend from a Windows Virtual Machine on Azure.
134134

135135
1. Return to **Overview** in the virtual machine’s menu and select **Connect**.
136136
1. Sign in to your virtual machine using RDP, SSH, or Bastion.
137137

138138
### [Linux](#tab/linuxvm/)
139139

140-
This section describes testing reachability of a standard load balancer front-end from a Linux Virtual Machine on Azure.
140+
This section describes testing reachability of a standard load balancer frontend from a Linux Virtual Machine on Azure.
141141

142142
1. Return to **Overview** in the virtual machine’s menu and select **Connect**.
143143
1. Sign in to your virtual machine using SSH or Bastion.
144144
---
145145

146-
### Test the load balancer's front-end
146+
### Test the load balancer's frontend
147147

148-
Choose either ping or traceroute to test reachability of a standard public load balancer front-end from an Azure Virtual Machine.
148+
Choose either ping or traceroute to test reachability of a standard public load balancer frontend from an Azure Virtual Machine.
149149

150150
### [Ping](#tab/ping/windowsvm)
151151

152-
Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Windows virtual machine:
152+
Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Windows virtual machine:
153153

154154
1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
155155
2. In the command prompt, type the following command:
@@ -162,7 +162,7 @@ Follow these steps to test reachability of a standard public load balancer front
162162

163163
### [Ping](#tab/ping/linuxvm)
164164

165-
Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Linux virtual machine:
165+
Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Linux virtual machine:
166166

167167
1. Open Terminal.
168168
2. Type the following command:
@@ -175,7 +175,7 @@ Follow these steps to test reachability of a standard public load balancer front
175175

176176
### [Traceroute](#tab/traceroute/windowsvm)
177177

178-
Follow these steps to test reachability of a standard public load balancer front-end using `tracert` from a Windows virtual machine:
178+
Follow these steps to test reachability of a standard public load balancer frontend using `tracert` from a Windows virtual machine:
179179

180180
1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
181181
2. In the command prompt, type the following command:
@@ -188,7 +188,7 @@ Follow these steps to test reachability of a standard public load balancer front
188188

189189
### [Traceroute](#tab/traceroute/linuxvm)
190190

191-
Follow these steps to test reachability of a standard public load balancer front-end using `traceroute` from a Linux virtual machine:
191+
Follow these steps to test reachability of a standard public load balancer frontend using `traceroute` from a Linux virtual machine:
192192

193193
1. Open Terminal.
194194
2. Type the following command:
@@ -203,7 +203,7 @@ Follow these steps to test reachability of a standard public load balancer front
203203

204204
## Expected replies with ping
205205

206-
Based on the current health probe state of your backend instances, you receive different replies when testing the Load Balancer’s front-end with ping. Review the following scenarios for the expected reply:
206+
Based on the current health probe state of your backend instances, you receive different replies when testing the Load Balancer’s frontend with ping. Review the following scenarios for the expected reply:
207207

208208
| **Scenario** | **Expected reply** |
209209
| --- | --- |

0 commit comments

Comments
 (0)