Hello
I have a VMware Horizon 7 solution that I am looking to provide load balancing for using NSX Load Balancer
I have a server environment with its own vCenter and hosts
I have a VDI environment with its own vCenter and hosts
I want to install NSX in Cross-vCenter mode with an NSX Primary Manager in the server environment and Secondary in the VDI.
Having read the documentation, I will have a 3 node controller cluster in the Server env.
In the Cross-vCenter documentation is states
Logical Load Balancer - No
Does this mean that I cannot load balance ANY services (such as Horizon Connection Servers) in my server =environment?.
I do not need any load balancing services in my VDI vCenter as only desktops run here)
Thanks in advance
Sean
The issue with cross-VC load balancing is that load balancing occurs on an ESG, and an ESG can only be associated with a single NSX Manager/vCenter. That said, you'll see in the NSX-V Multi-site Options and Cross-VC NSX Design Guide on page 92 that the workaround is to just manually re-create everything in the second vCenter. In your case, however, you don't need to worry about any of that since your workloads won't be migrating between vCenters so there's really no impact to load balancing as it pertains to your scenario.
The issue with cross-VC load balancing is that load balancing occurs on an ESG, and an ESG can only be associated with a single NSX Manager/vCenter. That said, you'll see in the NSX-V Multi-site Options and Cross-VC NSX Design Guide on page 92 that the workaround is to just manually re-create everything in the second vCenter. In your case, however, you don't need to worry about any of that since your workloads won't be migrating between vCenters so there's really no impact to load balancing as it pertains to your scenario.
Hi lhoffer
I do not ever need to LB services across vCenters or even ever do cross vCenter vMotion. The application services I need to LB are all located in vCenter-01 (and always will be).
Reading the document it seems it is possible for this to still be configured on the ESG. I think what confuse me was that it mentioned logical load balancer not being supported (but I guess this is different anyway)
Thanks
Sean