Forum Discussion

Jake_Robinson_1's avatar
Jake_Robinson_1
Icon for Nimbostratus rankNimbostratus
Feb 25, 2012

No traffic on VE after updating ESXi

I have several LTM VE 10.2 VMs running in my cluster. After upgrading ESXi to 5.0 the LTMs will not pass any traffic if on those hosts. I hypothesize it is the VMXNET3 driver on the LTM VEs does not work with ESX5, but would like to see if any one else has seen this issue. The VMs have not been upgraded to the newest VM hardware for fear of being in a catch 22. I'd rather not update everything to v11 at this time, unless I am absolutely sure it would fix the issue.

 

 

Cheers,

 

 

 

Jake

 

cloud
vmware

4 Replies

Sort By
  • simon_hamilton-'s avatar
    simon_hamilton-
    Icon for Cirrus rankCirrus
    Feb 25, 2012
    Are you running 10.2.3 already? How are you vSwitches / VLANs setup, is your dot1q trunking configured as it needs to be?

     

    10.2.3 should work OK on 5, so I'd start with that. If that makes no difference make a note of your vSwitch / interface config and post here please.
  • Jake_Robinson_1's avatar
    Jake_Robinson_1
    Icon for Nimbostratus rankNimbostratus
    Feb 25, 2012
    I'll check on the exact version, but the vSwitch config has not changed. The only thing that has changed is the upgrade to ESXi 5.
  • Paul_Pindell's avatar
    Paul_Pindell
    Icon for Employee rankEmployee
    Feb 25, 2012
    Jake,

    Your hunch was right. There are differences in the VMXNET3 between vSphere 4.x and 5. The VE 10.2.2 is the first version that supports the updated VMXNET3 spec. If you still have a 4.x host vMotion the VE to it, perform the upgrade to at least 10.2.2, and then you will be able to migrate the VE back to a ESXi 5 host.

     

    Paul

     

  • Jake_Robinson_1's avatar
    Jake_Robinson_1
    Icon for Nimbostratus rankNimbostratus
    Mar 28, 2012
    Thanks gentlemen,

     

     

    I've confirmed with support that the first version that supports vSphere 5 is 10.2.2 HF1. I've tested and confirmed upgrading to 10.2.3 fixes the issue. Thanks again!

     

     

    Cheers,

     

     

    Jake