Presenting vRA self-service portal using F5 BIG-IP

Hi all, I’m having a bit of trouble using an external load balancer with the vRA self service portal, and I was wondering if anyone has done this before.

We have a new VCF 3.8 deployment which presents the self-service portal to users. The NSX load balancers have their own DNS name for this at the moment (svs-vra.sub.org). We would like to present the portal via our F5 BIG-IP appliances to use a more friendly DNS name (portal.org) and comply with our internal standards.

We have configured a VIP on the F5s and configured the backend in the same way as our usual webapps are presented, using the NSX LB VIP as the backend server. Browsers attempting to connect to [portal.org](https://portal.org) get “connection reset” which, according to our F5 guys, is coming from the backend.

Has anyone else used an F5 appliance to control access to the vRA portal? Is there anything which needs to be configured on the NSX side? Any advice at all would be appreciated, including *”This is a stupid idea, why would you do this?”*

View Reddit by johimselfView Source

Related Articles

Leave a Reply