1 Reply Latest reply on Sep 15, 2020 11:13 PM by Lalegre

    NSX-T 2.5.0 VM network connectivity not functional after machines provisioned by vRA 8.1 or Horizon 7.12

    future2000 Enthusiast

      Hi,

       

      Wondering if anyone else has seen this. This is a VCF 3.9.0 environment so vSphere 6.7U3

       

      During provisioning of VMs through vRealize Automation 8.1 or Horizon 7.12 vSphere VMs network connections are broken...

      .

      Symptoms

       

      vSphere VM object shows the NIC as connected, disconnecting and reconnecting this from vSphere makes no difference to the problem. The VMtools shows the NICs with APIPA addresses from vCenter

      .

      Guest OS shows 'Media Disconnected' in Windows 10 or Windows Server 2016!

       

      NSX-T shows the ports as operational state down!? If you admin down the ports and then admin up the ports. The machines connect to the network and operational status goes green. The guest NIC is then working.

       

      When provisioning a 6 VM blueprint, one or two of the VMs will be in this state. Same thing with a Horizon View pool (although we have worked around this issue by using a different Template for each pool connected to the respective segment needed for that pool.

       

      Seems entirely unreliable.

       

      I hope NSX-T 2.5.1 will fix these issues.

       

      Cheers

        • 1. Re: NSX-T 2.5.0 VM network connectivity not functional after machines provisioned by vRA 8.1 or Horizon 7.12
          Lalegre Expert

          Hey,

           

          Is is a quite weird issue actually I provisioned with vRA 8.1 using NSX-T 3.0.1.1 (I know that is not the same version) and it worked smoothly more than 50 deployment so far.

           

          Maybe this is not something with NSX or Horizon but with the template you are using. Check the next:

           

          • Make sure you are using VMXNET3
          • That you have the VMware Tools up-to-date
          • Look for hidden network adapters in the Device Manager and uninstall them.
          • Make sure that on your Windows the IPv4 you are using is show as preferred if you run ipconfig /all

           

          Those are really quick tests to do and in my case they solved most of the issues.