Introduced : BIG-IP_v11.6.0
Enables or disables late binding explicit flow migration for a set of FastL4 profiles. It is disabled by default. The late binding explicit flow migration state indicates whether connections are automatically migrated into the hardware (disabled) or they must be explicitly migrated to hardware by the iRule command BIGTCP::release_flow (enabled). Having this enabled will allow specifying iRules that will analyze Layer 7 data, select a back-end server, and then push the client and server-side flows down to the ePVA for low latency processing at Layer 4. Notice that none of this is possible at Layer 4.


    in String [] profile_names,
    in LocalLB__ProfileEnabledState [] states


Parameter Type Description
profile_names String [] Names of the FastL4 profiles to modify.
states ProfileEnabledState [] The late binding explicit flow migration state.

Return Type

Type Description


Exception Description
Common::AccessDenied Raised if the client credentials are not valid.
Common::InvalidArgument Raised if one of the arguments is invalid.
Common::OperationFailed Raised if an operation error occurs.

See Also


The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.

Sample Code

The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.