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

npaulo_213434's avatar
npaulo_213434
Icon for Nimbostratus rankNimbostratus
Aug 04, 2015

LTM to LB a proprietary queuing app on test environment

Hi all,   we have a client developing a proprietary queuing app. Most of their clients work with F5 LTM to manage this connections and now this partner wants to create a test environment to see ho...
application delivery
deployment
devops
iRules
LTM
performance
VernonWells's avatar
VernonWells
Icon for Employee rankEmployee
Aug 04, 2015

I'll start by recommending that you reach out to your F5 Account team. The attached SE should be of great value here.

 

Having said that, what data is required depends on the functions the BIG-IP is intended to provide. Assuming the primary interest is local load-balancing, if load-balancing is by-flow [1], then there isn't much that you need (but you'll want to figure out if some sort of persistence is needed). If the load-balancing is based on information above layer4 (that is, in the application data or protocol), then things get trickier. If the data need to be manipulated, things get even trickier.

 

[1] For TCP, a flow is a connection (handshake through RST or FIN sequence); for UDP, a flow is all segments with a common 5-tuple until a timeout is reached without any further segments in the timeout period.