Users Guide

16–SR-IOV
SR-IOV and Storage Functionality
249 BC0054508-00 J
To verify SR-IOV in ESXi CLI:
1. Issue the lspci command
~ # lspci | grep -i ether
Following is a sample output.
0000:03:01.0 Network controller: Broadcom Corporation
NetXtreme II BCM57810 10 Gigabit Ethernet Virtual Function
[PF_0.3.0_VF_0]
2. To list the SR-IOV-enabled NIC, issue the esxcli command:
~ # esxcli network sriovnic list
Following is a sample output.
Name PCI Device Driver Link Speed Duplex MAC Address MTU Description
------ ------------- ------ ---- ----- ------ ---------------- ---- -----------
vmnic0 0000:003:00.0 bnx2x Up 10000 Full 3c:d9:2b:f6:71:50 1500 Broadcom Corpo
vmnic1 0000:003:00.1 bnx2x Down 0 Full 3c:d9:2b:f6:71:54 1500 Broadcom Corpo
SR-IOV and Storage Functionality
You can enable storage functionality (FCoE or iSCSI) on an SR-IOV-enabled
adapter. However, if storage is used on an NPAR-enabled physical function (PF),
the quantity of virtual functions for that PF is set to zero; therefore, SR-IOV is
disabled on that PF.
This limitation applies only when the adapter is configured in NPAR mode. It is not
relevant when the adapter is configured in single-function (SF) mode.
In ESX, after enabling SR-IOV in the OS for SF mode, the storage adapter will not
be discovered.
SR-IOV and Jumbo Packets
If SR-IOV is enabled on a virtual function (VF) on the adapter, ensure that the
same jumbo packet settings is configured on both the VF and the Microsoft
synthetic adapter. You can configure these values using Windows Device
Manager, Advanced properties.
If there is a mismatch in the values, the SR-IOV function is shown the degraded
state in Hyper-V, Networking Status.