Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
13.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 13.1.1, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.4, 18.104.22.168, 13.1.5, 22.214.171.124
Opened: Sep 18, 2017
With a virtual server configured with a FastL4 profile and a FIX profile where the FastL4 profile is configured with late binding and explicit flow migration, the first connection after a setup or restart may not correctly execute FIX iRules if the flow is not handed off to ePVA after the first FIX message.
The iRules may not trigger on the second and further messages sent to the FIX virtual server on the first connection after the restart.
-- Configure a virtual server with a FastL4 profile and a FIX profile. -- Configure the FastL4 profile to have late binding and explicit flow migration. -- Place iRules on the virtual server that trigger on FIX_MESSAGE or FIX_HEADER. -- Restart the BIG-IP, connect to the virtual server and begin sending FIX messages.