For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Spidey_29396's avatar
Spidey_29396
Icon for Nimbostratus rankNimbostratus
Mar 10, 2014

Source Load balancing

  Connection initiated from the outside 1. VISA Client(10.10.10.5) establish connection to F5 Virtual IP(10.10.10.1) , let’s say port 4000 2. F5 will choose a server between FEP1(172.16.20.1...
IheartF5_45022's avatar
IheartF5_45022
Icon for Nacreous rankNacreous
Mar 10, 2014

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......