Azure-docs: Question: Azure VM offering with accelerating networking using Mellanox nic type ConnectX-4 or ConnectX-5

[dcasota]

Using for example the Standard_DS3_v2 offering , includes the Accelerating Networking feature, but, it uses the nic type ConnectX-3® / Pro.

The vendor Mellanox describes its products in matrix rows with driver type (Linux,Windows), supported speeds, Ethernet: RoCE versions, VXLAN, GENEVE, SR-IOV Ethernet, iSER, N-VDS ENS.

The Azure docs https://docs.microsoft.com/en-us/azure/virtual-network/create-vm-accelerated-networking-powershell describes for a Windows VM the use of ConnectX-3 Ethernetadapter only.

How to found / is there already an Azure VM offering with accelerating networking specifically using a newer Mellanox nic type ConnectX®-4 / Lx or ConnectX®-5 / Ex?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e4be8e45-460a-fab4-519b-32d83382005c
• Version Independent ID: 36a002a6-5813-da00-0a57-068eeaf491cf
• Content: Create an Azure VM with Accelerated Networking - Azure PowerShell
• Content Source: articles/virtual-network/create-vm-accelerated-networking-powershell.md
• Service: virtual-network
• GitHub Login: @gsilva5
• Microsoft Alias: gsilva

[Karishma-Tiwari-MSFT]

Thanks for the question. We are currently investigating and will update you shortly.

[SubhashVasarapu-MSFT]

@dcasota , Appreciate your patience. There is no possibility for now for checking/selecting the Mellanox driver for specific VM size before deploying. And also from the reproduced scenario, I found that a basic VM SKU which supports accelerated networking is carrying the same Mellanox ConnectX-3 network adapter as the Standard E64s v3 (64 vcpus, 432 GiB memory) VM which is largest among the SKU. So, as of now Azure by default provide you with the Mellanox ConnectX-3 network adapter. If you would like to install the Mellanox driver manually then please go through this manual.

We are closing this issue for now.If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet

[dcasota]

Okay, thanks for clarifying. Really appreciate you answer! I switched from v2 to the Standard_E4s_v3 offering. From lessons learned, the Mellanox ConnectX-3 driver is included in newer product drivers.
The Azure docs for a Windows Server Virtual Machine is really good. And in respect to the vendors' reference for other OS the Mellanox driver could be installed manually.

[zhuguang11111]

Could Azure provides the Mellanox ConnectX-4 network adapter now?

[bsmetzer]

Fsv_2 series offers Mellanox ConnectX-4 beginning with the F8s_v2 size

[harikalyank]

I tried with Fsv_2 series still its support Mellanox X-3.Could you please help is there any series really supports X-4 or latest

[nikhilno1]

In my experience, X-3 or X-4 gets assigned randomly which can change during VM restart.
If you add multiple interfaces, you may get X-4.

[harikalyank]

after adding multiple interfaces I have got X-4M.
Thank you !!