LocalLB::ProfileFastL4::set_late_binding_state

Introduced : BIG-IP_v11.6.0
Enables or disables late binding for a set of FastL4 profiles. It is disabled by default. Late binding allows flows to start in L7 performing pool member selection based on tags and FIX messages and then transition to FastL4 in the ePVA to manage all subsequent trading traffic. You need a FIX profile in the Performace FastL4 Virtual Server configuration. Layer 7 to Layer 4 flow migration permits, with constraints, hudfilters and iRules to 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. The client side connection is fully established, and application data is processed, before a server-side connection is established. An iRule uses the application data to select the back-end server to provide a late binding between the client connection and a server connection. This provides application layer intelligence during server load balancing followed by extremely low latency, hardware assisted, packet fowarding via the ePVA.

Prototype

 set_late_binding_state(
    in String [] profile_names,
    in LocalLB__ProfileEnabledState [] states
);

Parameters

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

Return Type

Type Description
void  

Exceptions

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

Warning

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.