edits

Author: v-thepet

articles/virtual-network/accelerated-networking-overview.md

@@ -21,17 +21,17 @@ The following diagram illustrates how two VMs communicate with and without Accel
 
 ![Screenshot that shows communication between Azure VMs with and without Accelerated Networking.](./media/create-vm-accelerated-networking/accelerated-networking.png)
 
-Without Accelerated Networking, all networking traffic in and out of the VM traverses the host and the virtual switch. The virtual switch provides all policy enforcement to network traffic. Policies include network security groups, access control lists, isolation, and other network virtualized services. To learn more about virtual switches, see [Hyper-V Virtual Switch](/windows-server/virtualization/hyper-v-virtual-switch/hyper-v-virtual-switch).
+**Without Accelerated Networking**, all networking traffic in and out of the VM traverses the host and the virtual switch. The virtual switch provides all policy enforcement to network traffic. Policies include network security groups, access control lists, isolation, and other network virtualized services. To learn more about virtual switches, see [Hyper-V Virtual Switch](/windows-server/virtualization/hyper-v-virtual-switch/hyper-v-virtual-switch).
 
-With Accelerated Networking, network traffic that arrives at the VM's network interface (NIC) forwards directly to the VM. Accelerated Networking offloads all network policies that the virtual switch applied, and applies them in hardware. Because hardware applies policy, the NIC can forward network traffic directly to the VM. The NIC bypasses the host and the virtual switch, while it maintains all the policy it applied in the host.
+**With Accelerated Networking**, network traffic that arrives at the VM's network interface (NIC) forwards directly to the VM. Accelerated Networking offloads all network policies that the virtual switch applied, and applies them in hardware. Because hardware applies policy, the NIC can forward network traffic directly to the VM. The NIC bypasses the host and the virtual switch, while it maintains all the policy it applied in the host.
 
 ## Benefits
 
 Accelerated Networking has the following benefits:
 
 - **Lower latency and higher packets per second (pps).** Removing the virtual switch from the data path eliminates the time packets spend in the host for policy processing, and increases the number of packets that the VM can process.
 
-- **Reduced jitter.** Virtual switch processing depends on the amount of policy to apply and the workload of the CPU that does the processing. Offloading policy enforcement to the hardware removes that variability by delivering packets directly to the VM. Offloading also removes the host-to-VM communication, all software interrupts, and all context switches.
+- **Reduced jitter.** Virtual switch processing time depends on the amount of policy to apply and the workload of the CPU that does the processing. Offloading policy enforcement to the hardware removes that variability by delivering packets directly to the VM. Offloading also removes the host-to-VM communication, all software interrupts, and all context switches.
 
 - **Decreased CPU utilization.** Bypassing the virtual switch in the host leads to less CPU utilization for processing network traffic.
 
@@ -78,9 +78,9 @@ The following Linux and FreeBSD distributions from the Azure Gallery support Acc
 
 - Most general-purpose and compute-optimized VM instance sizes with two or more vCPUs support Accelerated Networking. On instances that support hyperthreading, VM instances with four or more vCPUs support Accelerated Networking.
 
-- The individual [VM sizes documentation](../virtual-machines/sizes.md) indicates whether the VM supports Accelerated Networking.
+- To check whether a VM size supports Accelerated Networking, see [Sizes for virtual machines in Azure](../virtual-machines/sizes.md).
 
-- You can directly query the list of VM SKUs that support Accelerated Networking by using the Azure CLI [az vm list-skus](/cli/azure/vm#az-vm-list-skus) command. Although NC and NV sizes appear in the command output, those sizes don't support Accelerated Networking. Enabling Accelerated Networking on NC or NV VMs has no effect.
+- You can directly query the list of VM SKUs that support Accelerated Networking by using the Azure CLI [az vm list-skus](/cli/azure/vm#az-vm-list-skus) command.
 
   ```azurecli-interactive
   az vm list-skus \
@@ -91,9 +91,11 @@ The following Linux and FreeBSD distributions from the Azure Gallery support Acc
     --output table
   ```
 
-### Custom or Azure compute gallery images
+  Although NC and NV sizes appear in the command output, those sizes don't support Accelerated Networking. Enabling Accelerated Networking on NC or NV VMs has no effect.
 
-If you use a custom image that supports Accelerated Networking, make sure you have the required drivers to work with Mellanox ConnectX-3, ConnectX-4 Lx, and ConnectX-5 NICs on Azure. Accelerated Networking also requires network configurations that exempt configuring the virtual functions on mlx4_en and mlx5_core drivers. Images that have cloud-init >=19.4 have networking correctly configured to support Accelerated Networking during provisioning.
+### Custom VM images
+
+If you use a custom image that supports Accelerated Networking, make sure you have the required drivers to work with Mellanox ConnectX-3, ConnectX-4 Lx, and ConnectX-5 NICs on Azure. Accelerated Networking also requires network configurations that exempt configuration of the virtual functions on the mlx4_en and mlx5_core drivers. Images with cloud-init version 19.4 or greater have networking correctly configured to support Accelerated Networking during provisioning.
 
 The following example shows a sample configuration drop-in for `NetworkManager` on RHEL or CentOS:
 

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

@@ -1,6 +1,6 @@
 ---
 title: Use Azure CLI to create a Linux VM with Accelerated Networking
-description: Learn how to use Azure CLI to create and manage Linux virtual machines with Accelerated Networking enabled.
+description: Learn how to use Azure CLI to create and manage Linux virtual machines that have Accelerated Networking enabled.
 services: virtual-network
 author: asudbring
 manager: gedegrac
@@ -14,14 +14,13 @@ ms.custom: fasttrack-edit, devx-track-azurecli
 ---
 # Use Azure CLI to create a Linux VM with Accelerated Networking
 
-This article provides steps to create a Linux virtual machine (VM) with Accelerated Networking (AccelNet) 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.
+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.
 
-You can also create a VM with Accelerated Networking by using the [Azure portal](../virtual-machines/linux/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) or [Azure PowerShell](../virtual-network/create-vm-accelerated-networking-powershell.md).
+You can also create a Linux VM with Accelerated Networking enabled by using the [Azure portal](../virtual-machines/linux/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json) or [Azure PowerShell](../virtual-network/create-vm-accelerated-networking-powershell.md). To manage Accelerated Networking on VMs by using the Azure portal, see [Portal management].
 
 ## Prerequisites
 
 - An Azure account with an active subscription. You can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-
 - The latest version of [Azure CLI installed](/cli/azure/install-azure-cli). Sign in to Azure by using the [az login](/cli/azure/reference-index#az-login) command.
 
 ## Create a VM with Accelerated Networking
@@ -30,7 +29,7 @@ In the following examples, replace the example parameters such as `<myResourceGr
 
 ### Create a virtual network
 
-1. Use [az group create](/cli/azure/group) to create a resource group to contain the resources. Be sure to select a supported Linux region listed in [Linux Accelerated Networking](https://azure.microsoft.com/updates/accelerated-networking-in-expanded-preview).
+1. Use [az group create](/cli/azure/group) to create a resource group to contain the resources. Be sure to select a supported Linux region as listed in [Linux Accelerated Networking](https://azure.microsoft.com/updates/accelerated-networking-in-expanded-preview).
 
    ```azurecli
    az group create --name <myResourceGroup> --location <myAzureRegion>
@@ -76,15 +75,15 @@ In the following examples, replace the example parameters such as `<myResourceGr
 
 ### Create a network interface with Accelerated Networking
 
-1. Use [az network public-ip create](/cli/azure/network/public-ip) to create a public IP address. The VM doesn't need a public IP address if you don't access it from the internet, but you need the public IP to complete the steps for this article.
+1. Use [az network public-ip create](/cli/azure/network/public-ip) to create a public IP address. A VM doesn't need a public IP address if you don't access it from the internet, but you need the public IP to complete the steps for this article.
 
    ```azurecli
    az network public-ip create \
      --name <myPublicIp> \
      --resource-group <myResourceGroup>
    ```
 
-1. Use [az network nic create](/cli/azure/network/nic) to create a network interface (NIC) with Accelerated Networking enabled. The following example creates a network interface in the subnet of the virtual network, and associates the NSG to the NIC.
+1. Use [az network nic create](/cli/azure/network/nic) to create a network interface (NIC) with Accelerated Networking enabled. The following example creates a NIC in the subnet of the virtual network, and associates the NSG to the NIC.
 
    ```azurecli
    az network nic create \
@@ -114,7 +113,7 @@ az vm create \
   --nics <myNic>
 ```
 
-When the VM is created, you get output similar to the following example. Take note of the `publicIpAddress`, which you use to access the VM in later steps.
+After the VM is created, you get output similar to the following example. Take note of the `publicIpAddress`, which you use to access the VM in later steps.
 
 ```output
 {
@@ -147,7 +146,7 @@ When the VM is created, you get output similar to the following example. Take no
    > [!NOTE]
    > Other kernel versions may be supported. For an updated list, see the compatibility tables for each distribution at [Supported Linux and FreeBSD virtual machines for Hyper-V](/windows-server/virtualization/hyper-v/supported-linux-and-freebsd-virtual-machines-for-hyper-v-on-windows), and confirm that SR-IOV is supported. You can find more details in the release notes for [Linux Integration Services for Hyper-V and Azure](https://www.microsoft.com/download/details.aspx?id=55106). * 
 
-1. Use the `lspci` command to confirm that the Mellanox VF device is exposed to the VM. The returned output is similar to the following example:
+1. Use the `lspci` command to confirm that the Mellanox VF device is exposed to the VM. The returned output should be similar to the following example:
 
    ```output
    0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03)
@@ -170,18 +169,20 @@ When the VM is created, you get output similar to the following example. Take no
 
 ## Handle dynamic binding and revocation of virtual function
 
-Binding to the synthetic NIC that's exposed in the VM is a mandatory requirement for all applications that take advantage of Accelerated Networking. If an application runs directly over the VF NIC, it doesn't receive all packets that are destined to the VM, because some packets show up over the synthetic interface. Run an application over the synthetic NIC to guarantee that the application receives all packets that are destined to it. Binding to the synthetic NIC also ensures that the application keeps running even if the VF is revoked during host servicing.
+Binding to the synthetic NIC that's exposed in the VM is a mandatory requirement for all applications that take advantage of Accelerated Networking. If an application runs directly over the VF NIC, it doesn't receive all packets that are destined to the VM, because some packets show up over the synthetic interface.
+
+You must run an application over the synthetic NIC to guarantee that the application receives all packets that are destined to it. Binding to the synthetic NIC also ensures that the application keeps running even if the VF is revoked during host servicing.
 
 For more information about application binding requirements, see [How Accelerated Networking works in Linux and FreeBSD VMs](./accelerated-networking-how-it-works.md#application-usage).
 
 <a name="enable-accelerated-networking-on-existing-vms"></a>
 ## Manage Accelerated Networking on existing VMs
 
-It's possible to enable Accelerated Networking on an existing VM that doesn't have this feature. The VM must meet the following requirements to support Accelerated Networking:
+It's possible to enable Accelerated Networking on an existing VM. The VM must meet the following requirements to support Accelerated Networking:
 
 - Be a supported size for Accelerated Networking.
 - Be a supported Azure Marketplace image and kernel version for Linux.
-- Be stopped or deallocated before you can enable Accelerated Networking on any NIC. This requirement applies to all individual VMs or VMs in an availability set or Azure Virtual Machine Scale Set.
+- Be stopped or deallocated before you can enable Accelerated Networking on any NIC. This requirement applies to all individual VMs or VMs in an availability set or Azure Virtual Machine Scale Sets.
 
 ### Enable Accelerated Networking on individual VMs or VMs in availability sets
 
@@ -193,7 +194,7 @@ It's possible to enable Accelerated Networking on an existing VM that doesn't ha
      --name <myVm>
    ```
 
-   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 enable Accelerated Networking on any of the NICs.
+   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.
 
 1. Once the VM is stopped, enable Accelerated Networking on the NIC of your VM.
 
@@ -204,7 +205,7 @@ It's possible to enable Accelerated Networking on an existing VM that doesn't ha
      --accelerated-networking true
    ```
 
-1. Restart your VM, or all the VMs in the availability set, and confirm that Accelerated Networking is enabled.
+1. Restart your VM, or all the VMs in the availability set, and [confirm that Accelerated Networking is enabled](#confirm-that-accelerated-networking-is-enabled).
 
    ```azurecli
    az vm start --resource-group <myResourceGroup> \
@@ -219,8 +220,8 @@ Azure Virtual Machine Scale Sets is slightly different but follows the same work
 
    ```azurecli
    az vmss deallocate \
-     --name myvmss \
-     --resource-group myrg
+     --name <myVmss> \
+     --resource-group <myResourceGroup>
    ```
 
 1. Once the VMs are stopped, update the Accelerated Networking property under the network interface.
@@ -254,26 +255,25 @@ Once you restart and the upgrades finish, the VF appears inside VMs that use a s
 
 VMs with Accelerated Networking enabled can be resized only to sizes that also support Accelerated Networking. You can't resize a VM with Accelerated Networking to a VM instance that doesn't support Accelerated Networking by using the resize operation. Instead, use the following process to resize these VMs:
 
-1. Stop and deallocate the VM or all the VMs in the availability set or Virtual Machine Scale Set.
-1. Disable Accelerated Networking on the NIC of the VM or all the VMs in the availability set or Virtual Machine Scale Set.
+1. Stop and deallocate the VM or all the VMs in the availability set or Virtual Machine Scale Sets.
+1. Disable Accelerated Networking on the NIC of the VM or all the VMs in the availability set or Virtual Machine Scale Sets.
 1. Move the VM or VMs to a new size that doesn't support Accelerated Networking, and restart them.
 
-## Portal creation
-
-You can also create a VM with Accelerated Networking by using the [Azure portal](../virtual-machines/linux/quick-create-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
-
-- When you create a VM in the Azure portal that uses a [supported operating system](./accelerated-networking-overview.md#supported-operating-systems) and [VM size](./accelerated-networking-overview.md#supported-vm-instances), the **Enable accelerated networking** checkbox on the **Networking** tab of the **Create a virtual machine** screen is automatically selected. If Accelerated Networking isn't supported, the checkbox isn't selected, and a message explains the reason.
+### Manage Accelerated Networking through the portal
 
-- You can enable only Azure Marketplace-supported operating systems through the portal. To create a VM with a custom OS image that supports Accelerated Networking, you must use Azure CLI or PowerShell.
+When you [create a VM in the Azure portal](/azure/virtual-machines/linux/quick-create-portal) that uses a [supported operating system](./accelerated-networking-overview.md#supported-operating-systems) and [VM size](./accelerated-networking-overview.md#supported-vm-instances), the **Enable accelerated networking** checkbox on the **Networking** tab of the **Create a virtual machine** screen is automatically selected. If Accelerated Networking isn't supported, the checkbox isn't selected, and a message explains the reason.
 
-- The Accelerated Networking setting in the portal shows the user-selected state. Accelerated Networking allows choosing **Disabled** even if the VM size requires Accelerated Networking. VM sizes that require Accelerated Networking enable Accelerated Networking at runtime regardless of the user setting in the portal.
+>[!NOTE]
+>- You can enable Accelerated Networking during portal VM creation only for Azure Marketplace supported operating systems. To create and enable Accelerated Networking for a VM with a custom OS image, you must use Azure CLI or PowerShell.
+>
+>- The Accelerated Networking setting in the portal shows the user-selected state. Accelerated Networking allows choosing **Disabled** in the portal even if the VM size requires Accelerated Networking. VM sizes that require Accelerated Networking enable Accelerated Networking at runtime regardless of the user setting in the portal.
 
-- To enable or disable Accelerated Networking for an existing VM through the Azure portal:
+To enable or disable Accelerated Networking for an existing VM through the Azure portal:
 
-  1. From the portal page for the VM, select **Networking** from the left menu.
-  1. On the **Networking** page, select the **Network Interface**.
-  1. At the top of the NIC **Overview** page, select **Edit accelerated networking**.
-  1. Select **Automatic**, **Enabled**, or **Disabled**, and then select **Save**.
+1. From the portal page for the VM, select **Networking** from the left menu.
+1. On the **Networking** page, select the **Network Interface**.
+1. At the top of the NIC **Overview** page, select **Edit accelerated networking**.
+1. Select **Automatic**, **Enabled**, or **Disabled**, and then select **Save**.
 
 ## Next steps