future2000
Enthusiast
Enthusiast

Horizon fails to provision successfully on NSX-T segments

Jump to solution

Hi,

We're using Horizon 7.12 and NSX-T 2.5.0

Building instant clone pools on NSX-T segments. With the network selected for the pool . from the parent image.

On building the pool a number of the VMs appear not to connect to the network correctly.

Symptoms

vSphere VM object shows the NIC connected, disconnecting and reconnecting this makes no difference to the problem.

Guest OS shows 'Media Disconnected' in Windows 10.

Resetting the machines from View will sometimes fix this issue, sometimes it won't.

NSX-T shows the ports as operational state down!? If you admin down the ports for 30 seconds or more and then admin up the ports. The machines connect to the network and operational status goes green. View then blows them away again, obviously, they are instant clones, and they come back up broken again.

Seems entirely unreliable.

Anyone seen this?

Cheers.

0 Kudos
1 Solution

Accepted Solutions
future2000
Enthusiast
Enthusiast

WORKAROUND -

Do not use the select a NSX-T network segment for your pool during the pool creation wizard. Clone your template out for each pool you need. Configure the VM as being on the segment you want for the specific pool and when you create the pool just leave at default 'Use network from parent image'. The Instant clones all then are connected and no issues occur.

Must be a bug with the customization process and NSX-T.

View solution in original post

0 Kudos
4 Replies
future2000
Enthusiast
Enthusiast

WORKAROUND -

Do not use the select a NSX-T network segment for your pool during the pool creation wizard. Clone your template out for each pool you need. Configure the VM as being on the segment you want for the specific pool and when you create the pool just leave at default 'Use network from parent image'. The Instant clones all then are connected and no issues occur.

Must be a bug with the customization process and NSX-T.

View solution in original post

0 Kudos
future2000
Enthusiast
Enthusiast

Have now seen the same behavior occurring when provisioning multi-machine blueprints with vRealize Automation 8.1. This therefore appears to be some kind of issues with vSphere 6.7U3 and NSX-T 2.5.0. Not Horizon per say.

Cheers

0 Kudos
vBritinUSA
Hot Shot
Hot Shot

Just FYI, A little late to this but IC require the port bindings to be static. NSX-T segments are created using ephemeral port bindings by default.

Someone posted this very question in the NSX forum.

Static port binding on NSX T distrubuted port group

Please mark helpful or correct if my answer resolved your issue.
future2000
Enthusiast
Enthusiast

Thanks for the information @vBritinUSA

These are overlay segment networks though on a NSX-T 2.5.0 NVDS. I'm not sure if they act the same or not. We have the same thing happening in vRA8.1 provisioned VMs as well now!

0 Kudos