Bug ID 656901: MRF add 'existing_connection_only' and 'outgoing_connection_instance_seed' two iRule commands

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,

Fixed In:

Opened: Apr 07, 2017
Severity: 3-Major


If the MRF 'existing_connection_only' is not there, then MRF will forward the new message to either the existing connection or creating a new connection. If the MRF 'outgoing_connection_instance_seed' is not there, then the generation of the connection's instance number will use some internal originating connection id. Same client IP with different src_port may end up to different outgoing connection.


1. Won't always reuse the existing connection. 2. The requests from same client IP with different src_port, the outgoing connection may be different.


If these two new iRule commands were not there.


There is no workaround at this time.

Fix Information

MR::message existing_connections_only <boolean> Gets or sets a flag that instructs the MRF to only forward the message using existing connections, and if a connection to the selected host does not exist then the route will fail. MR::message outgoing_connection_instance_seed <integer>Gets or if been set by this iRule then this seed will be used to generate the connection instance number instead of this generated by some internal originating connection id. (See MR::connection_instance iRule command). If the number received is larger than 32 bit then the 64 bit number will be hashed to 32 bit number.

Behavior Change