Policy script information, Verification and troubleshooting – Dell Emulex Family of Adapters User Manual
Page 632

Emulex Drivers for Windows User Manual
P010077-01A Rev. A
3. Configuration
NIC Driver Configuration
632
# Host2 example-host2 192.x.x.x {Blue2:5001, Red2:6001}
# [2-1] Host1
#
# (a) Configure Provider Address and Route:
# Get the interface, assign the PA and the default route
Get-NetVirtualizationProviderAddress | where {$_.ProviderAddress -eq "192.x.x.x"} |
Remove-NetVirtualizationProviderAddress;
# (b) Set VirtualSubnetID on the VM network port
Get-VMNetworkAdapter "Blue1" | where {$_.MacAddress -eq "060600000005"} |
Set-VMNetworkAdapter -VirtualSubnetID 0;
Get-VMNetworkAdapter "Red1" | where {$_.MacAddress -eq "080800000005"} |
Set-VMNetworkAdapter -VirtualSubnetID 0;
Policy Script Information
Verify or modify the following list of components for your specific conditions:
Network connection name of the NIC attached to the virtual switch
Binding network connection to the Microsoft filter driver (ms_netwnv)
Caution:
Do not change the filter driver name.
VM Names
VM MAC Addresses
VM SID (Virtual Machine Subnet ID)
HOST IP Address (Provider Address = Physical NIC IP Address for NVGRE)
VM IP Address (Customer Address = IP Address on each vNIC per VM)
Subnet Masks
Verification and Troubleshooting
Verify that the host provider addresses can ping each other, If pings fail, perform the
following steps:
1. Shutdown all VMs on all of the hosts.
2. Remove the policies.
3. Remove the vport0 virtual switch.
4. Reboot the hosts.
5. Create a vport0 switch.
6. On each VM, add a new adapter and use the vswitch name that you just created.
Note: Do not share the NIC with the host operating system.
7. Apply the polices.
8. Power-up the VMs.
9. Ping the provider addresses.