Skip to content

Commit e32d43e

Browse files
committed
fixes
1 parent e7d3480 commit e32d43e

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/virtual-network/diagnose-network-routing-problem.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In this article, you learn how to diagnose routing problems by viewing the effec
1919

2020
You attempt to connect to a VM, but the connection fails. To determine why you can't connect to the VM, you can view the effective routes for a network interface using the Azure [portal](#diagnose-using-azure-portal), [PowerShell](#diagnose-using-powershell), or the [Azure CLI](#diagnose-using-azure-cli).
2121

22-
The steps that follow assume you have an existing VM to view the effective routes for. If you don't have an existing VM, first deploy a [Linux](/azure/virtual-machines/linux/quick-create-portal?toc=%2fazure%2fvirtual-network%2ftoc.json) or [Windows](/azure/virtual-machines/windows/quick-create-portal?toc=%2fazure%2fvirtual-network%2ftoc.json) VM to complete the tasks in this article with. The examples in this article are for a VM named *myVM* with a network interface named *nic-1*. The VM and network interface are in a resource group named *test-rg*, and are in the *East US* region. Change the values in the steps, as appropriate, for the VM you're diagnosing the problem for.
22+
The steps that follow assume you have an existing VM to view the effective routes for. If you don't have an existing VM, first deploy a [Linux](/azure/virtual-machines/linux/quick-create-portal?toc=%2fazure%2fvirtual-network%2ftoc.json) or [Windows](/azure/virtual-machines/windows/quick-create-portal?toc=%2fazure%2fvirtual-network%2ftoc.json) VM to complete the tasks in this article with. The examples in this article are for a VM named *vm-1* with a network interface named *vm-1445*. The VM and network interface are in a resource group named *test-rg*, and are in the *East US* region. Change the values in the steps, as appropriate, for the VM you're diagnosing the problem for.
2323

2424
## Diagnose using Azure portal
2525

@@ -52,11 +52,11 @@ Though effective routes were viewed through the VM in the previous steps, you ca
5252

5353
You can run the commands that follow in the [Azure Cloud Shell](https://shell.azure.com/powershell), or by running PowerShell from your computer. The Azure Cloud Shell is a free interactive shell. It has common Azure tools preinstalled and configured to use with your account. If you run PowerShell from your computer, you need the Azure PowerShell module, version 1.0.0 or later. Run `Get-Module -ListAvailable Az` on your computer, to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-azure-powershell). If you're running PowerShell locally, you also need to run `Connect-AzAccount` to log into Azure with an account that has the [necessary permissions](virtual-network-network-interface.md#permissions).
5454

55-
Get the effective routes for a network interface with [Get-AzEffectiveRouteTable](/powershell/module/az.network/get-azeffectiveroutetable). The following example gets the effective routes for a network interface named *nic-1* in a resource group named *test-rg*:
55+
Get the effective routes for a network interface with [Get-AzEffectiveRouteTable](/powershell/module/az.network/get-azeffectiveroutetable). The following example gets the effective routes for a network interface named *vm-1445* in a resource group named *test-rg*:
5656

5757
```azurepowershell-interactive
5858
$Params = @{
59-
NetworkInterfaceName = "nic-1"
59+
NetworkInterfaceName = "vm-1445"
6060
ResourceGroupName = "test-rg"
6161
}
6262
Get-AzEffectiveRouteTable @Params | Format-Table
@@ -80,20 +80,20 @@ You receive output similar to the following example:
8080
```output
8181
NetworkInterfaces
8282
-----------------
83-
{/subscriptions/<ID>/resourceGroups/test-rg/providers/Microsoft.Network/networkInterfaces/nic-1
83+
{/subscriptions/<ID>/resourceGroups/test-rg/providers/Microsoft.Network/networkInterfaces/vm-1445
8484
```
8585

86-
In the previous output, the network interface name is *nic-1*.
86+
In the previous output, the network interface name is *vm-1445*.
8787

8888
## Diagnose using Azure CLI
8989

9090
You can run the commands that follow in the [Azure Cloud Shell](https://shell.azure.com/bash), or by running the CLI from your computer. This article requires the Azure CLI version 2.0.32 or later. Run `az --version` to find the installed version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli). If you're running the Azure CLI locally, you also need to run `az login` and log into Azure with an account that has the [necessary permissions](virtual-network-network-interface.md#permissions).
9191

92-
Get the effective routes for a network interface with [az network nic show-effective-route-table](/cli/azure/network/nic#az-network-nic-show-effective-route-table). The following command gets the effective routes for a network interface named *nic-1* that is in a resource group named *test-rg*:
92+
Get the effective routes for a network interface with [az network nic show-effective-route-table](/cli/azure/network/nic#az-network-nic-show-effective-route-table). The following command gets the effective routes for a network interface named *vm-1445* that is in a resource group named *test-rg*:
9393

9494
```azurecli-interactive
9595
az network nic show-effective-route-table \
96-
--name nic-1 \
96+
--name vm-1445 \
9797
--resource-group test-rg
9898
```
9999

0 commit comments

Comments
 (0)