Skip to content

Commit 8d0acc0

Browse files
committed
edits before restart
1 parent 3af17be commit 8d0acc0

File tree

3 files changed

+61
-57
lines changed

3 files changed

+61
-57
lines changed

articles/virtual-network/create-vm-accelerated-networking-cli.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,9 @@ ms.custom: fasttrack-edit, devx-track-azurecli
1616

1717
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.
1818

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).
2022

2123
## Prerequisites
2224

articles/virtual-network/create-vm-accelerated-networking-powershell.md

Lines changed: 58 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@ ms.author: allensu
1515

1616
# Use Azure PowerShell to create a Windows VM with Accelerated Networking
1717

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.
1919

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).
2121

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).
2323

2424
## Prerequisites
2525

@@ -49,19 +49,19 @@ In the following examples, replace the example parameters such as `<myResourceGr
4949
-AddressPrefix "192.168.1.0/24"
5050
```
5151

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.
5353

5454
```azurepowershell
5555
$vnet = New-AzVirtualNetwork -ResourceGroupName "<myResourceGroup>" `
56-
-Location "<myAzureRegion" `
56+
-Location "<myAzureRegion>" `
5757
-Name "<myVnet>" `
5858
-AddressPrefix "192.168.0.0/16" `
5959
-Subnet $Subnet
6060
```
6161

6262
### Create a network security group
6363

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.
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).
6565

6666
```azurepowershell
6767
$rdp = New-AzNetworkSecurityRuleConfig `
@@ -87,7 +87,7 @@ In the following examples, replace the example parameters such as `<myResourceGr
8787
-SecurityRules $rdp
8888
```
8989

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.
9191

9292
```azurepowershell
9393
Set-AzVirtualNetworkSubnetConfig `
@@ -123,7 +123,7 @@ In the following examples, replace the example parameters such as `<myResourceGr
123123

124124
### Create a VM and attach the network interface
125125

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.
127127

128128
```azurepowershell
129129
$cred = Get-Credential
@@ -167,21 +167,23 @@ In the following examples, replace the example parameters such as `<myResourceGr
167167

168168
Once you create the VM in Azure, connect to the VM and confirm that the Ethernet controller is installed in Windows.
169169

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.
171173

172-
2. In the virtual machine list, choose your new VM.
174+
1. On the VM's **Overview** page, select **Connect**.
173175

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**.
175177

176-
4. From the VM overview toolbar, select **Connect** > **RDP** > **Download RDP File**.
178+
1. On the **Native RDP** screen, select **Download RDP file**.
177179

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.
179181

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**.
181183

182-
7. In the **Device Manager** window, expand the **Network adapters** node.
184+
1. In the **Device Manager** window, expand the **Network adapters** node.
183185

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:
185187

186188
![Mellanox ConnectX-3 Virtual Function Ethernet Adapter, new network adapter for accelerated networking, Device Manager](./media/create-vm-accelerated-networking/device-manager.png)
187189

@@ -205,74 +207,74 @@ You can enable Accelerated Networking on an existing VM. The VM must meet the fo
205207

206208
1. Stop or deallocate the VM or, if an availability set, all the VMs in the set:
207209

208-
```azurepowershell
209-
Stop-AzVM -ResourceGroup "myResourceGroup" -Name "myVM"
210-
```
210+
```azurepowershell
211+
Stop-AzVM -ResourceGroup "<myResourceGroup>" -Name "<myVM>"
212+
```
211213

212214
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.
213215

214216
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.
215217

216218
1. Enable Accelerated Networking on the NIC of your VM:
217219

218-
```azurepowershell
219-
$nic = Get-AzNetworkInterface -ResourceGroupName "myResourceGroup" `
220-
-Name "myNic"
221-
222-
$nic.EnableAcceleratedNetworking = $true
223-
224-
$nic | Set-AzNetworkInterface
225-
```
220+
```azurepowershell
221+
$nic = Get-AzNetworkInterface -ResourceGroupName "<myResourceGroup>" `
222+
-Name "<myNic>"
223+
224+
$nic.EnableAcceleratedNetworking = $true
225+
226+
$nic | Set-AzNetworkInterface
227+
```
226228

227229
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).
228230

229-
```azurepowershell
230-
Start-AzVM -ResourceGroup "myResourceGroup" `
231-
-Name "myVM"
232-
```
231+
```azurepowershell
232+
Start-AzVM -ResourceGroup "<myResourceGroup>" `
233+
-Name "<myVM>"
234+
```
233235

234236
### Virtual Machine Scale Sets
235237

236238
Azure Virtual Machine Scale Sets is slightly different but follows the same workflow.
237239

238240
1. Stop the VMs:
239241

240-
```azurepowershell
241-
Stop-AzVmss -ResourceGroupName "myResourceGroup" `
242-
-VMScaleSetName "myScaleSet"
242+
```azurepowershell
243+
Stop-AzVmss -ResourceGroupName "<myResourceGroup>" `
244+
-VMScaleSetName "<myScaleSet>"
243245
```
244246
245247
1. Update the Accelerated Networking property under the NIC:
246248
247-
```azurepowershell
248-
$vmss = Get-AzVmss -ResourceGroupName "myResourceGroup" `
249-
-VMScaleSetName "myScaleSet"
250-
251-
$vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0].EnableAcceleratedNetworking = $true
252-
253-
Update-AzVmss -ResourceGroupName "myResourceGroup" `
254-
-VMScaleSetName "myScaleSet" `
255-
-VirtualMachineScaleSet $vmss
256-
```
249+
```azurepowershell
250+
$vmss = Get-AzVmss -ResourceGroupName "<myResourceGroup>" `
251+
-VMScaleSetName "<myScaleSet>"
252+
253+
$vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0].EnableAcceleratedNetworking = $true
254+
255+
Update-AzVmss -ResourceGroupName "<myResourceGroup>" `
256+
-VMScaleSetName "<myScaleSet>" `
257+
-VirtualMachineScaleSet $vmss
258+
```
257259

258260
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.
259261

260-
```azurepowershell
261-
$vmss.UpgradePolicy.Mode = "Automatic"
262-
263-
Update-AzVmss -ResourceGroupName "myResourceGroup" `
264-
-VMScaleSetName "myScaleSet" `
265-
-VirtualMachineScaleSet $vmss
266-
```
262+
```azurepowershell
263+
$vmss.UpgradePolicy.Mode = "Automatic"
264+
265+
Update-AzVmss -ResourceGroupName "<myResourceGroup>" `
266+
-VMScaleSetName "<myScaleSet>" `
267+
-VirtualMachineScaleSet $vmss
268+
```
267269

268270
1. Restart the scale set:
269271

270-
```azurepowershell
271-
Start-AzVmss -ResourceGroupName "myResourceGroup" `
272-
-VMScaleSetName "myScaleSet"
273-
```
272+
```azurepowershell
273+
Start-AzVmss -ResourceGroupName "<myResourceGroup>" `
274+
-VMScaleSetName "<myScaleSet>"
275+
```
274276

275-
Once you restart and the upgrades finish, the VF appears inside VMs that use a supported OS and VM size.
277+
Once you restart and the upgrades finish, the virtual function (VF) appears inside VMs that use a supported OS and VM size.
276278

277279
### Resize existing VMs with Accelerated Networking
278280

-92.7 KB
Loading

0 commit comments

Comments
 (0)