Hi!
Earlier I wrote a blog post about creating a Reverse Proxy with Avi for my Nexus Repository. So I already have an existing Virtual Service in Avi that presents the Nexus Repository website on port 443. The VIP is 10.10.60.15.
Current Setup
Component | Details |
Nexus Repository Virtual Service Name | potus-nexusrepo |
Nexus Repository Virtual Service VIP | 10.10.60.15 |
Nexus Repository Virtual Service Port | 443 |
Nexus Repository Server IP Address | 10.10.30.35 |
Nexus Repository Ports | 8081 (Website) 5000 (Docker Repository) |
What do we want to achieve?
Now I would like to present my Nexus Docker Repository over HTTPS using the same VIP. We will be adding a new Service Port (5000) to the existing Virtual Service VIP.
Avi Configuration
Let’s get started!
1. Browse to your Avi’s Website and login
2. Go to the ‘Applications‘ view and select ‘create virtual service‘ on the top right of your page and select ‘Advanced Setup‘:

3. Give your Virtual Service a Name

4. Click on ‘Switch to Advanced‘

5. Select your existing Virtual Service:

6. Under ‘Profiles‘ make sure to select ‘System-TCP-Proxy‘ and ‘System-Secure-HTTP‘ as shown below:

7. We will need to create a new Pool for the Nexus Repository Server on Port 5000. Under ‘Pool‘ click ‘Create Pool‘:

8. Enter the required Details to create the Pool

A | Enter a name for your Pool (e.g.: nexus-repo-pool-5000) |
B | Enter your Default Server Pool (e.g.: 5000) |
C | Choose your preferred Load Balance method (e.g.: Least Connections) |
D | Enable Passive Health Monitoring |
E | Enter the amount of Health Checks should be OK in order to consider the service Up |
F | Choose ‘System-TCP’ Health Check |
G | Select ‘System-Analytics-Profile’ as the Analytics Profile |
H | Make sure to check ‘Enable real time metrics’ if needed |
I | Disable SSL, meaning that the Avi LB will communicate using HTTP towards the backend servers |
9. Click Next to go to the ‘Servers’ tab and add your Server & Port

10. Now you should see your Server listed in the Pool:


11. Enter the Port to which the Service should listen on and enable the SSL check:


Let’s test it, right?

That’s it! Now you have 2 Virtual Services running behind the same VIP!
Stay tuned for more!