Traffic Steering with FastL4 problem?

not clear. That SOL states "To work around this issue, you can modify the affected virtual server and change the type from Performace (Layer 4) to Standard."

And in the SOL sol16446: The BIG-IP system now allows a Performance L4 virtual server to have an associated HTTP profile states "Beginning in BIG-IP 11.3.0, the system allows a Performance L4 virtual server to have an associated HTTP profile. This change was introduced as part of the support for the BIG-IP Policy Enforcement Manager (PEM)."

It sounds like prior to v11.3 you shouldn't bind a FastL4 tcp profile and 11.3+ you can do it.