When adding 4 or more VMXNET3 NICs to a VLM in VMware, the order is incorrect

When adding 4 or more VMXNET3 Network Interface Controllers (NICs) to a Virtual LoadMaster (VLM) in VMware, the order of the interfaces on the Web User Interface (WUI) does not correspond with the order of the interfaces in machine setting, for example:

NIC 1: eth2
NIC 2: eth1
NIC 3: eth3
NIC 4: eth0

This order has been observed in all cases. It does not matter if the NICs are added before licensing or if they are added later.

eth0 always corresponds to NIC4.

This behaviour does not affect e1000 NICs.

This is a VMware issue and nothing to do with the KEMP LoadMaster. For further information, please refer to the following articles:




Was this article helpful?

0 out of 1 found this helpful



A date on this article would be of great help - as the VM article referenced dates back to 2013 - so no confirmation if this issue still exists today in 2018 with vsphere 6.5 U1

Nick Smylie


Double checked myself on Vsphere 6.5 and this is still the case. Unfortunately this is a VMware issue and I could not find any new relevant articles on this.


I have VMware 6.7, its Aug 2019 and this issue is still there. I actually cannot add more than 4 NICS to the LB.

Justin Federico


We understand your frustration with this issue, but as previously stated in the article, this is a VMware issue that they have not addressed. Based on the SR you submitted, another option would be configuring a trunk on the VMware side and creating the VLANS on the LM. This would require less NICs on the LM and our team would be happy to assist in getting this configured.