search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.47k forks source link

[Inconsistency between doc and actual] Standard_D2d_v4 with Accelerated Networking #79031

Closed torumakabe closed 3 years ago

torumakabe commented 3 years ago

Standard_D2d_v4 has only 2 vCPUs, So, according to the documentation, Accelerated Networking should not be supported.

However, it seems to be enabled in my deployment.

% az vm show -g my-rg -n my-vm --query hardwareProfile.vmSize                              
Result
---------------
Standard_D2d_v4

% id=$(az vm show -g my-rg -n my-vm --query "networkProfile.networkInterfaces[0].id" -o tsv)
% az network nic show  --ids $id --query enableAcceleratedNetworking                          
Result
--------
True

In VM

$ lspci
0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03)
0000:00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
0000:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
0000:00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA
1a40:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80)

$ ethtool -S eth0 | grep vf_
     vf_rx_packets: 2071
     vf_rx_bytes: 26747404
     vf_tx_packets: 3673
     vf_tx_bytes: 622901
     vf_tx_dropped: 0
     cpu0_vf_rx_packets: 486
     cpu0_vf_rx_bytes: 1327522
     cpu0_vf_tx_packets: 1800
     cpu0_vf_tx_bytes: 354270
     cpu1_vf_rx_packets: 1585
     cpu1_vf_rx_bytes: 25419882
     cpu1_vf_tx_packets: 1873
     cpu1_vf_tx_bytes: 268631

Could you confirm that the documentation is correct? Thanks.

Document Details

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

psmanhas commented 3 years ago

@ToruMakabe Thank you for the feedback We will work on it and will keep you updated on the thread

psmanhas commented 3 years ago

@ToruMakabe Apologies for the delay in response and all the inconvenience caused because of the issue.

As per discussion internally it is only supported on one vNIC and there are few documentations which are needs to be updated to reflect same in this documentation as well. Work is underway and got confirmation from internal team that there will be a doc-update for same.

Hope the provided information is helpful.

We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.