oneconnect profile use

Hi,

the current implementation of OneConnect is designed to be used in combination with HTTP traffic and http profile.

It will respect the tcp idle-timeout settings of assigned tcp-profiles both on client- and serverside (be aware of default "keepalive timer" settings in your tcp-profile).

As it will "re-cycle" a serverside connection by multiplexing multiple clientside connections into a single serverside connection it might make sense to modify the OneConnect profile mask to 32 bit. Now connections from same client IP will be aggregated/pooled on serverside.

Table based persistence records will be updated with new incoming connections/requests only. Watch them by using tmsh:

watch tmsh show ltm persist persist-records    

Configuration changes apply to new connections only. Especially with OneConnect applied this may have confusing effects. I use to clean up the connection table before running new tests with modified config:

tmsh delete sys connection   

Thanks, Stephan