In the previous part we have created a 2-node vRealize Operations 6 High Availability cluster. With its new architecture, vROps unified UI is expected to get lots of HTTPS requests traffic so it only makes sense to load balancing it, no?!
Virtualization, storage and network admins, NOC teams, application owners and more are your potential vROps users. With VMware consistent UI improvement initiative and HTML5 roadmaps, the need to use network load balancers is always something one should consider.
With that been said, the good old vCloud Networking and Security (vCNS) Edge (aka vShield Edge) is considered a valid load balancer device for our vROps cluster solution.
In this post I will not go over the details on how to deploy the vCNS appliance, instead I will focus more on the Edge deployment and load balancing configuration. If you want to learn the basics, jump over to “THEITHOLLOW” by Eric Shanks where he did a very nice and simple “getting started” guide.
Lab Physical Edge Deployment Diagram
In the figure below you can see my Edge deployment diagram. Remember, this is just a lab environment and probably not even close to a datacenter deployment topology – it is here only for some visualization.
Log in to your vCNS, select you datacenter object and under the Network Virtualization tab click on Edges. You are now ready to start the deployment wizard.
In real life, it is unlikely you will configure your firewall with “any-any” rule and so as I. Later we will configure the proper HTTP/HTTPS Allow rule but for now I am leaving it to deny the default traffic policy.
Internal vNIC Configurations
Within the “Configure” tab select “Interfaces” and edit “vNIC1” which will be our Internal Edge interface.
Once again, select the vSwtich/vDS portgroup and assign the right IP and subnet.
Now that you have both your external and internal interfaces in place it’s time to do some LB magic.
Go over to “Load Balancer” tab and under “Pools” click the Plus button to add a new pool. For the purpose of this post I went with the default Services and Health Check parameters.
Go over to “Load Balancer” tab and under “Virtual Servers” click the Plus button to add a new VS.
The last step is to allow HTTP and HTTPS traffic to go through the Edge Firewall.
Under the “Firewall” tab, click the Plus button to add a new FW rule and configure it to accept HTTP and HTTPS request. I’ve created a very basic rule “any to any” rule but outside my lab environment I would have probably change it to be more specific when it comes to source and destination.
That’s it, all that is left now is to open your browser and enter the vROps cluster Virtual Server IP.
If you want a proof that this entire procedure works and the load balancer kicks-in, go to the “Statistic” tab and notice how LB traffic is starting to work in the second you hit the VIP URL.
Congratulations, you now have 2-node vROps High Availability cluster behind a vCNS Edge Load Balancer 🙂