NSX allows load balancing on a level 4 (TCP or UDP) layer or level 7 (HTTP or HTTPS) layer.
Learn how to set up load balancing in NSX.
- Being an administrative contact of your Hosted Private Cloud infrastructure to receive login credentials.
- A user account with access to the OVHcloud Control Panel.
- Having NSX deployed with two segments configured in your NSX configuration, you can use the Segment Management in NSX guide for reference.
- Two virtual machines with NGINX enabled on one segment.
We will :
- Enable Load Balancing on the gateway ovh-T1-gw.
- Create a server pool from two virtual machines that use a web server running on port 80.
- Add a virtual server in the Load Balancer configuration which contains our server pool.
- Set a NAT rule to redirect to the virtual server.
Creating the tag on both virtual machines.
To simplify the administration of the Load Balancer, we will use a tag on the two virtual machines in the future server pool.
In the NSX interface go to the
Inventory tab and click on
Virtual Machines on the left.
- Then click on the
three vertical dotsto the left of the first virtual machine.
Editfrom the menu.
Replace Tag with
loadbl, then click
Add Item(s) loadbl below.
Change Scope to
nginx, then click
Add Item(s) nginx below.
+ sign next to your tag to add it to your virtual machine.
When the tag appears, click
three vertical dots to the left of the second virtual machine and choose
Edit from the menu.
Replace Tag with
load and select the
Tag: loadbl Scope: nginx from the list below.
+ sign next to your tag to add it to your second virtual machine.
SAVE to add the tag to your virtual machine.
Stay on Inventory, click
Tags and click on the
number to the right of the marker you created.
You can see your two virtual machines using the same tag. Click
CLOSE when done.
Add group with created tag
Groups on the left and click
nginx-server below Name and click
SET under Compute Members.
+ ADD CRITERION.
Keep Virtual Machine Tag Equals and select your
loadbl tag with its
nginx scope and click
View Members to the right of the group.
The list of virtual machines is automatically added to the group based on the criteria in your tag.
Activating the Load Balancer
Go to the
- In the Network Services section on the left, click on
- Go to the
ADD LOAD BALANCER.
loadbalancer-on-t1 below Name, select
ovh-T1-gw under Attachment and click
The Load Balancer is created and activated on the ovh-T1-gw gateway.
Server pool creation
Go to the
Server Pools tab and click
ADD SERVER POOL.
sp-nginx below Name and click
Select Members under Members/Group.
Select a group and choose the
nginx-servers group you created then click
SAVE to apply your changes.
Your server pool is created with your two virtual machines that are members of the group.
Virtual server creation
Your server pool is created with your two virtual machines which are members of the group. Go to the
Virtual Servers tab and click on
ADD VIRTUAL SERVER.
Fill in this information :
Name : Name of your virtual server
IP Address: Front-end IP address of your virtual server on the same network as your NGINX virtual machines
Port : Port
Load Balancer: Your load balancer
Server Pool: Your server pool
Your virtual server is active. If you connect from a machine that uses a segment on a gateway of type Tier-1 Gateways with this URL
http://192.168.102.3, the Load Balancer will connect to one of the two virtual machines configured in your group.
Adding a NAT rule
NAT in the Network Services section on the left and click
ADD NAT RULE.
to-lb-virtual-server in your rule Name with these options :
Destination IP : A virtual IP address of your T0 such as
Translated IP : IP address of your virtual server
Service PORT : Choose the predefined port
Your rule is active. If you click on
http://virtual-ip-address-on-T0 you will be connected to your virtual server which will redirect the flow to one of the servers in your group.
Having read this guide, you should be able to enable Load Balancing, create a server pool from two virtual machines, add a virtual server in the Load Balancer configuration, and set a NAT rule to redirect to the virtual server.