Manual Chapter :
Transport
Applies To:
Show Versions
BIG-IP LTM
- 17.1.0, 17.0.0, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
Transport
Each connection is created using the parameters of a transport object (either a virtual server
or a transport-config). The transport specifies the profiles, SNAT and iRule scripts of the
connection. When a message is routed, MRF will scan the list of connections for a connection
created with the same transport specified. Even if the two transports contain the same
parameters, a connection created with a different transport will not be used.
A pool object only allows specification of a transport-config as the outgoing connection
transport. If the peer object does not specify the transport config, the transport of the
message's originating connection will be used. If the system wishes to potentially deliver a
message through an existing connection created with by different virtual server on the same
router, the MR::message route iRule command must be used. For example:
MR::message route virtual "/Common/internal_vs" host [IP::local_addr]:5060
