Support VMXNET3 for K1000
Using a VMXNET3 Adapter for K1000 could substantially improve the network performance on a VMWARE ESX Infrastructure. Currently K1000 only Supports E1000 Adapters.
Completed in SMA 6.4
Eric Pagan commented
I was able to switch the adapter on our K1 to VMXNET3. Use the same MAC address as it's tied to activation counts. Take a snapshot. I had to log into netdiag and do a krestore network for it recognize the new NIC. If I tried to login with konfig I got an "Alert! Unable to connect to remote host" message.
Nathan Wood commented
An admin noted this was completed in SMA 6.4. What does that mean? It's available? Going to be available in a certain version?
Any updates on this? There hasn't been an update for a few years now.
Paul McGuire commented
Any update on this. My virtual appliance is slow responding and we need to increase the network speeds.
Nathan Wood commented
This is an important enhancement for those of us using the virtual appliance. Please bump up the priority on supporting VMXNET3 adapters!
KACE Admins commented
KACE Team, this really should have been done long ago. Please get it done. Thank you!
Let's get with the program! We need our k1000 to have faster than 1 gig access!
As per your own system requirements for physical hardware https://support.quest.com/technical-documents/kace-systems-management-appliance/7.1/technical-specifications-for-virtual-appliances/
Network Interface Devices
Network Interface Card
0 - 8000 - 1 GB Ethernet Port
8000 + - 10 GB Ethernet Port
It does not make sense that physical boxes can push 10gb while virtual environments, which all enterprises are trending towards, are limited.
Please add support for VMXNET3.
Mike McKaughan commented
Please put in support for using the VMXNET 3 Nic instead of the E1000
This needs to happen across the K1k and K2k appliances. Please release an update soon.
Please put this to the top of the list. VMware's best practice is to use the VMXNET3 adapters. This is especially important when using distributed switches. This also requires VMware tools to be updated regularly in order to fix any potential issues. We have seen several issues corrected by using VMXNET3 adapters versus the E1000.
Please support this. E1000 is not a very good driver. When the appliance get's vMotioned in our environment it get's disconnected.
I agree, there is a bug in ESX 5 that causes a purple screen of death with E1000 adapters. the only fix it is change to the VMXNET3 which K1000 does not support. We have since updated to ESX 5.5 which does not have the issue but would still like to see the NIC supported.
it's a good thing, esp. in virtual environment the vmxnet3 adapters are a great alternative