Dell Emulex Family of Adapters - Manual (Page 634)

Emulex Drivers for Windows User Manual P010077-01A Rev. A
3. Configuration
NIC Driver Configuration
634
2. Change the VM IP Address.
For example: change 10.0.0.5 on one host and 10.0.0.7 on the other.
Without NVGRE, you would not be able to use the same IP address as the other
VM.
Ensure that you see the WNVNIC interface using the PowerShell command
get-netadapter.

If you are unable to see the NVGRE Ethernet connection, make sure that the
Hyper-V’s control panel/network connections property and advanced property
windows are all closed. The Control Panel renames the NDI/Params registry
keys and causes the policy scripts to be inoperative.
Cleaning Up Outdated Network Adapter Data
1. Start a win32 console window (command prompt).
2. From the command prompt, type
Set devmgr_show_nonpresent_devices=1
3. Start devmgmt.msc.
4. In the device manager console, go to the view menu and select “Show hidden
devices”.
5. Open the network devices tree view.
6. Uninstall all Emulex entries.
7. Rescan for hardware changes.
8. Uninstall Emulex devices until they are not recognized.
9. Install the new driver.
Configuring RoCE for the OCe14000-Series Adapters
Notes:

Both Windows SMB Direct and Windows NetworkDirect, which are included
as part of the Windows operating system, are required for RoCE.

RoCE is not supported when multichannel is enabled.

RoCE configurations are not supported with SR-IOV.

Windows Server 2012 or Windows Server 2012 R2 is required to use the RoCE
features on RoCE-capable adapters.
Enabling the RoCE Profile on the Client-Side
The RoCE profile can be enabled by using one of the following:

PXESelect BIOS. See the Boot for NIC, iSCSI, FCoE, and RoCE Protocols User
Manual for details of PXE-Select BIOS utility.

OneCommand Manager GUI. See the OneCommand Manager Application Version
User Manual for information about enabling the RoCE profile using
OneCommand Manager GUI.