Source Load balancing

Nice diagrams BTW - makes it so much easier to understand.

using F5, it is load balancing the connection, not the data, for example, VISA Client(10.10.10.5) establish connection to F5 Virtual IP(10.10.10.1) and FEP1(172.16.20.111) is selected by F5, all data will be sent to FEP1(172.16.20.111)

Applying the oneconnect profile to the FEP Virtual IP should fix this - each HTTP request will be examined and load-balanced individually.

*Connection initiated from inside(LAN)1.FEP1(172.16.20.111) and FEP2 (172.16.20.112) will established connection to VISA VIP(172.16.20.1)2.F5 throws the to VISA Client(10.10.10.5)3. When VISA Client(10.10.10.5) sends data, only one server should receive the data(FEP1 or FEP2) ***using F5, since FEP1(172.16.20.111) and FEP2 (172.16.20.112) have established connections going to VISA Client, both server receives the data which is unacceptable to the client.

I'm not quite understanding the issue here. If both FEP1 and FEP2 send requests to VISA Client via the VISA VIP, then both will receive responses. Obviously I am missing something here though......

Hi iHeartf5,

They wanted both servers have active connections to Visa Client but when VISA client responded,only one server should receive the data.

Thanks! Ferdz

So...if FEP1/2 act as clients to virtual VISA with serverside "VISA client", then when one client sends a request, the response will be sent only to the client that initiated the request. If you don't believe that is happening, then we need to troubleshoot that.

Try adding this to your virtual to help you see;-

when HTTP_REQUEST {
    set prefix [expr {int(rand()*10000)}]
    log local0. "$prefix [HTTP::uri]"
}
when HTTP_RESPONSE {
    log local0. "$prefix [HTTP::status], [HTTP::header Content_Length], [IP::remote_addr]"
}