VMware 5.5 & pfSense 2.2.5: Interface status not reflecting vmx link status
-
Hello,
We are running pfSense 2.2.5 on a VMware ESX 5.5 host. We are using VMNET3 network cards with the standard FreeBSD vmx drivers.
I noticed that, when a network card is disconnected, the interface status keeps showing a "up" status. (The logs reports the corresponding vmx as down.) Also, the link speed is displayed as autoselect and I did not find a way to find the exact negotiated link speed.
As anybody noticed the same or is this a problem specific to my setup? -
so your running 5.5u2 ? Yeah the native drivers and vmx3 don't show the right duplex, etc.. I move back to e1000 because it was causing lots of noise with running cdp and ladvd reporting duplex mismatch.. On my low end system I sure and the hell don't see any sort of issues with just running e1000 vs vmx3 with all the issues that vmx3 brings in other areas like your autoselect you found and ladvd not working right because of that, etc..
-
That just seems to be the nature of the vmx driver in FreeBSD. Outside of the mentioned ladvd circumstance, it doesn't hurt anything, and is more scalable than e1000. So I'd stay with vmxnet unless you need something like ladvd.
-
Thanks for the replies!
We actually moved from E1000 to VMXNET3 to get rid of a problem where som interfaces where reporting "emX: Watchdog timeout – resetting" errors (with success).
We have not installed the LADVD package and have not seen any other problem then the reporting problems mentioned in my original post.
Do you think this could cause problem for Gateway Group configured with a Trigger Level set to Member down? -
Do you think this could cause problem for Gateway Group configured with a Trigger Level set to Member down?
No, member down doesn't mean link down, it means 100% loss.
-
Ok noted. Thanks again!
