Hi all !
HI just made an edge that has the loadbalancer service, with one interface redirecting traffic between two servers, the problem is that when I check the transparent option in the pool the LBL stop working.
Thanks you!!
When you say you have one interface on the load balancer, are you referring to a "one armed" topology as described in the Logical Load Balancer section of the admin guide? If so, "inline mode" is the recommended topology to keep the LB in the layer 3 path. With a one armed topology, it'll only work if you set the load balancer as the default gateway for the servers in the pool (otherwise the LB won't get the return traffic from pool members back to the client and un-NAT it before sending back to the client).
When you say you have one interface on the load balancer, are you referring to a "one armed" topology as described in the Logical Load Balancer section of the admin guide? If so, "inline mode" is the recommended topology to keep the LB in the layer 3 path. With a one armed topology, it'll only work if you set the load balancer as the default gateway for the servers in the pool (otherwise the LB won't get the return traffic from pool members back to the client and un-NAT it before sending back to the client).
Hi! Yes I think that is a kind of one armed topology, the problem is that we don´t use NSX to route the network, ( we still haven't cross this bridge haha).
I tried using the VIP of the LB as gateway, it works redirecting the traffic but with this the vm lost comunication with all the others elements of the network the became unreacheable.
Do you have a default gateway or default route configured on the ESG where your Loadbalancer is running? Once you define it as the default gateway for your pool members, it'll need to know the next hop to forward traffic to for destinations outside of the local subnet.
Thank you! I gonna test that. But the transparent method works just as needed!