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
This article describes how to create a Linux virtual machine (VM) with Accelerated Networking (AccelNet) enabled by using the Azure command-line interface, Azure CLI. The article also discusses application binding requirements, and how to enable and manage Accelerated Networking on existing VMs.
18
18
19
-
You can also create a VM with Accelerated Networking enabled by using the [Azure portal](/azure/virtual-machines/linux/quick-create-portal) or [Azure PowerShell](../virtual-network/create-vm-accelerated-networking-powershell.md). To view and manage Accelerated Networking on VMs through the Azure portal, see [Manage Accelerated Networking through the portal](#manage-accelerated-networking-through-the-portal).
19
+
You can also create a VM with Accelerated Networking enabled by using the [Azure portal](quick-create-portal.md). For more information about managing Accelerated Networking on VMs through the Azure portal, see [Manage Accelerated Networking through the portal](#manage-accelerated-networking-through-the-portal).
20
+
21
+
To use Azure PowerShell to create a Windows VM with Accelerated Networking enabled, see [Use Azure CLI to create a Linux VM with Accelerated Networking](create-vm-accelerated-networking-cli.md).
Copy file name to clipboardExpand all lines: articles/virtual-network/create-vm-accelerated-networking-powershell.md
+58-56Lines changed: 58 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ ms.author: allensu
15
15
16
16
# Use Azure PowerShell to create a Windows VM with Accelerated Networking
17
17
18
-
This article describes how to create a Windows virtual machine (VM) with Accelerated Networking (AccelNet) enabled by using Azure PowerShell. The article also discusses application binding requirements, and how to enable and manage Accelerated Networking on existing VMs.
18
+
This article describes how to use Azure PowerShell to create a Windows virtual machine (VM) with Accelerated Networking (AccelNet) enabled. The article also discusses application binding requirements, and how to enable and manage Accelerated Networking on existing VMs.
19
19
20
-
You can also create a Windows VM with Accelerated Networking enabled by using the [Azure portal](quick-create-portal.md). To manage Accelerated Networking on VMs through the Azure portal, see [Manage Accelerated Networking through the portal](#manage-accelerated-networking-through-the-portal).
20
+
You can also create a VM with Accelerated Networking enabled by using the [Azure portal](quick-create-portal.md). For more information about managing Accelerated Networking on VMs through the Azure portal, see [Manage Accelerated Networking through the portal](#manage-accelerated-networking-through-the-portal).
21
21
22
-
To create a Linux VM with Accelerated Networking enabled, see [Use Azure CLI to create a Linux VM with Accelerated Networking](create-vm-accelerated-networking-cli.md).
22
+
To use Azure CLI to create a Linux VM with Accelerated Networking enabled, see [Use Azure CLI to create a Linux VM with Accelerated Networking](create-vm-accelerated-networking-cli.md).
23
23
24
24
## Prerequisites
25
25
@@ -49,19 +49,19 @@ In the following examples, replace the example parameters such as `<myResourceGr
49
49
-AddressPrefix "192.168.1.0/24"
50
50
```
51
51
52
-
1. Use [New-AzVirtualNetwork](/powershell/module/az.Network/New-azVirtualNetwork) to create a virtual network with the`<mySubnet>` subnet.
52
+
1. Use [New-AzVirtualNetwork](/powershell/module/az.Network/New-azVirtualNetwork) to create the virtual network with the subnet.
1. A network security group (NSG) contains several default rules, one of which disables all inbound access from the internet. Use [New-AzNetworkSecurityRuleConfig](/powershell/module/az.Network/New-azNetworkSecurityRuleConfig) to create a new rule so that you can remotely connect to the VM.
64
+
1. A network security group (NSG) contains several default rules, one of which disables all inbound access from the internet. Use [New-AzNetworkSecurityRuleConfig](/powershell/module/az.Network/New-azNetworkSecurityRuleConfig) to create a new rule so that you can remotely connect to the VM via Remote Desktop Protocol (RDP).
65
65
66
66
```azurepowershell
67
67
$rdp = New-AzNetworkSecurityRuleConfig `
@@ -87,7 +87,7 @@ In the following examples, replace the example parameters such as `<myResourceGr
87
87
-SecurityRules $rdp
88
88
```
89
89
90
-
1. Use [Set-AzVirtualNetworkSubnetConfig](/powershell/module/az.Network/Set-azVirtualNetworkSubnetConfig) to associate the NSG to the `<mySubnet>`subnet. The NSG rules are effective for all resources deployed in the subnet.
90
+
1. Use [Set-AzVirtualNetworkSubnetConfig](/powershell/module/az.Network/Set-azVirtualNetworkSubnetConfig) to associate the NSG to the subnet. The NSG rules are effective for all resources deployed in the subnet.
91
91
92
92
```azurepowershell
93
93
Set-AzVirtualNetworkSubnetConfig `
@@ -123,7 +123,7 @@ In the following examples, replace the example parameters such as `<myResourceGr
123
123
124
124
### Create a VM and attach the network interface
125
125
126
-
1. Use [Get-Credential](/powershell/module/microsoft.powershell.security/get-credential) to set your VM credentials to the `$cred` variable, which prompts you to sign in.
126
+
1. Use [Get-Credential](/powershell/module/microsoft.powershell.security/get-credential) to set credentials for the VM and store them in the `$cred` variable, which prompts you to sign in.
127
127
128
128
```azurepowershell
129
129
$cred = Get-Credential
@@ -167,21 +167,23 @@ In the following examples, replace the example parameters such as `<myResourceGr
167
167
168
168
Once you create the VM in Azure, connect to the VM and confirm that the Ethernet controller is installed in Windows.
169
169
170
-
1. Go to the [Azure portal](https://portal.azure.com) to manage your VMs. Search for and select **Virtual machines**.
170
+
1. In the [Azure portal](https://portal.azure.com), search for and select *virtual machines*.
171
+
172
+
1. On the **Virtual machines** page, select your new VM.
171
173
172
-
2. In the virtual machine list, choose your new VM.
174
+
1. On the VM's **Overview** page, select **Connect**.
173
175
174
-
3. In the VM overview page, if the **Status**of the VM is listed as **Creating**, wait until Azure finishes creating the VM. The **Status** will be changed to **Running** after VM creation is complete.
176
+
1. On the **Connect**screen, select **Native RDP**.
175
177
176
-
4. From the VM overview toolbar, select **Connect** > **RDP**> **Download RDP File**.
178
+
1. On the **Native RDP**screen, select **Download RDP file**.
177
179
178
-
5. Open the RDP file, and then sign in to the VM with the credentials you entered in the [Create a VM and attach the network interface](#create-a-vm-and-attach-the-network-interface) section. If you've never connected to a Windows VM in Azure, see [Connect to virtual machine](../virtual-machines/windows/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json#connect-to-virtual-machine).
180
+
1. Open the downloaded RDP file, and then sign in to the VM with the credentials you entered when you created the VM.
179
181
180
-
6. After the remote desktop session for your VM appears, right-click the Windows Start button and choose**Device Manager**.
182
+
1. On the remote VM, right-click the Windows **Start** button and select**Device Manager**.
181
183
182
-
7. In the **Device Manager** window, expand the **Network adapters** node.
184
+
1. In the **Device Manager** window, expand the **Network adapters** node.
183
185
184
-
8. Confirm that the **Mellanox ConnectX-3 Virtual Function Ethernet Adapter** appears, as shown in the following image:
186
+
1. Confirm that the **Mellanox ConnectX-4 Lx Virtual Ethernet Adapter** appears, as shown in the following image:
185
187
186
188

187
189
@@ -205,74 +207,74 @@ You can enable Accelerated Networking on an existing VM. The VM must meet the fo
205
207
206
208
1. Stop or deallocate the VM or, if an availability set, all the VMs in the set:
If you created your VM individually without an availability set, you must stop or deallocate only the individual VM to enable Accelerated Networking. If you created your VM with an availability set, you must stop or deallocate all VMs in the set before you can enable Accelerated Networking on any of the NICs. The VMs then end up on a cluster that supports Accelerated Networking.
213
215
214
216
The stop or deallocate requirement is unnecessary if you disable Accelerated Networking. Clusters that support Accelerated Networking also work fine with NICs that don't use Accelerated Networking.
215
217
216
218
1. Enable Accelerated Networking on the NIC of your VM:
3. Restart your VM, or all the VMs in the availability set, and [confirm that Accelerated Networking is enabled](#confirm-the-ethernet-controller-is-installed).
228
230
229
-
```azurepowershell
230
-
Start-AzVM -ResourceGroup "myResourceGroup" `
231
-
-Name "myVM"
232
-
```
231
+
```azurepowershell
232
+
Start-AzVM -ResourceGroup "<myResourceGroup>" `
233
+
-Name "<myVM>"
234
+
```
233
235
234
236
### Virtual Machine Scale Sets
235
237
236
238
Azure Virtual Machine Scale Sets is slightly different but follows the same workflow.
1. Virtual Machine Scale Sets has an upgrade policy that applies updates by using automatic, rolling, or manual settings. Set the upgrade policy to automatic so that the changes are immediately picked up.
0 commit comments