Merge pull request #288980 from halkazwini/vnet-acc

Accelnet custom image information

Author: prmerger-automator[bot]

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

@@ -1,12 +1,12 @@
 ---
 title: Accelerated Networking overview
 description: Learn how Accelerated Networking can improve the networking performance of Azure VMs.
-author: EllieMelissa
+author: mattreatMSFT
+ms.author: mareat
 ms.service: azure-virtual-network
-ms.custom: linux-related-content
 ms.topic: how-to
-ms.date: 04/18/2023
-ms.author: ealume
+ms.date: 10/22/2024
+ms.custom: linux-related-content
 ---
 
 # Accelerated Networking overview
@@ -100,9 +100,18 @@ You can directly query the list of VM SKUs that support Accelerated Networking b
 
 ### 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.
+If you use a custom image that supports Accelerated Networking, make sure you meet the following requirements.
+
+#### Device and driver support
+Any custom image supporting Accelerated Networking must include drivers that enable Single Root I/O Virtualization for the network interface cards (NIC) which are used on Azure platforms. This hardware list includes NVIDIA ConnectX-3, ConnectX-4 Lx, ConnectX-5 and the [Microsoft Azure Network Adapter (MANA)](accelerated-networking-mana-overview.md).
+
+#### Dynamic binding and revocation of virtual function
+Accelerated Networking requires guest OS images to properly handle the virtual function being removed or added dynamically. Scenarios such as host maintenance or live migration will result in dynamic revocation of the virtual function and restoration after the maintenance event. Additionally, applications must ensure that they bind to the synthetic device and not the virtual function in order to maintain network connectivity during these events. 
 
-Images with cloud-init version 19.4 or later have networking correctly configured to support Accelerated Networking during provisioning.
+For more information about application binding requirements, see [How Accelerated Networking works in Linux and FreeBSD VMs](create-vm-accelerated-networking-cli.md?tabs=windows#handle-dynamic-binding-and-revocation-of-virtual-function). 
+
+#### Configure drivers to be unmanaged
+Accelerated Networking requires network configurations that mark the NVIDIA drivers as unmanaged devices. Images with cloud-init version 19.4 or later have networking correctly configured to support Accelerated Networking during provisioning. We strongly advise that you don't run competing network interface software (such as ifupdown and networkd) on custom images, and that you don't run dhcpclient directly on multiple interfaces.
 
 # [RHEL, CentOS](#tab/redhat)
 
@@ -150,12 +159,19 @@ Unmanaged=yes
 EOF
 ```
 
->[!NOTE]
->We strongly advise that you don't run competing network interface software (such as ifupdown and networkd) on custom images, and that you don't run dhcpclient directly on multiple interfaces.
+#### Network traffic uses the Accelerated Networking data path
+
+For NVIDIA drivers: Verify that the packets are flowing over the VF interface
+- [Linux documentation](accelerated-networking-how-it-works.md#application-usage)
+- [Windows documentation](create-vm-accelerated-networking-cli.md?tabs=windows#confirm-that-accelerated-networking-is-enabled)
+
+For MANA driver: Verify that the traffic is flowing through MANA
+- [Linux documentation](accelerated-networking-mana-linux.md#verify-that-traffic-is-flowing-through-mana)
+- [Windows documentation](accelerated-networking-mana-windows.md#verify-that-traffic-is-flowing-through-mana)
 
 ---
 
-## Next steps
+## Related content
 
 - [How Accelerated Networking works in Linux and FreeBSD VMs](./accelerated-networking-how-it-works.md)
 - [Create a VM with Accelerated Networking by using PowerShell](./create-vm-accelerated-networking-powershell.md)

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

@@ -1,13 +1,14 @@
 ---
 title: Use Azure CLI to create a Windows or Linux VM with Accelerated Networking
 description: Use Azure CLI to create and manage virtual machines that have Accelerated Networking enabled for improved network performance.
-author: steveesp
+author: mattreatMSFT
+ms.author: mareat
 ms.service: azure-virtual-network
 ms.topic: how-to
-ms.date: 04/18/2023
-ms.author: steveesp
+ms.date: 10/22/2024
 ms.custom: fasttrack-edit, devx-track-azurecli, linux-related-content
 ---
+
 # Use Azure CLI to create a Windows or Linux VM with Accelerated Networking
 
 > [!CAUTION]
@@ -197,6 +198,15 @@ Once you create the VM in Azure, connect to the VM and confirm that the Ethernet
 
    The presence of the adapter confirms that Accelerated Networking is enabled for your VM.
 
+1. Verify the packets are flowing over the VF interface from the output of the following command:
+   ```powershell
+   PS C:\ > Get-NetAdapter | Where-Object InterfaceDescription –like "*Mellanox*Virtual*" | Get-NetAdapterStatistics
+
+   Name       ReceivedBytes ReceivedUnicastPackets SentBytes SentUnicastPackets
+   ----       ------------- ---------------------- --------- ------------------
+   Ethernet 2 492447549     347643                 7468446   34991
+   ```
+
 > [!NOTE]
 > If the Mellanox adapter fails to start, open an administrator command prompt on the remote VM and enter the following command:
 >