nsx vdi

[MichalCzerwinsk]

Hello!

According to VMware® NSX for vSphere End-User Computing Design Guide 1.2

I wonder how Connection Server created on ComputeCluster and connected to tenant Logical Switch communicates with vCenter Server created on ManagementCluster and connected to VDS management portgroup. Do I have to create logical connection (routed) between tenant network and management network? Or maybe Connection Server should have two interfaces: 1 connected to tenant network and one connected to management network...?

Please tell me how you separate client traffic from management network.

Thank You.

Michał Czerwiński

[Sreec]

The design discuss about separate VDI pods with compute cluster and management cluster. Since Connection Servers are part of Compute Cluster which would be NSX prepared they will be connected to Logical Switches and UAG in edge cluster ( If design demands) can be connected to another set of logical switches and have these components routed via Distributed Logical Router. And you are right for connection server to communicate with vCenter Sever ,we need routing (if they are in different subnets) with port 80&443 opened . Another approach what we can do is to have a dedicated Management/Control Plane cluster populated with Connection Server,Composers,UEM residing in VXLAN/VLAN network and treat Edge Cluster as DMZ facing with UAG populated. For Management cluster we can rely on VLAN backed portgroups and for compute nodes leveraging Desktop Pools and RDSH Hosts connected to VXLAN backed network and DLR/Edges based on routing use cases. I prefer Connection Servers running on dedicated management cluster(AD/VC/Composer/UEM/AppVolume etc) rather than collapsing it with compute nodes.