Bug ID 563641: Cannot set a Message Routing peer to per-client connection-mode and set the source-port in transport-config when using SNAT

Last Modified: Jul 03, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 15.0.0

Opened: Dec 17, 2015
Severity: 4-Minor

Symptoms

The system does not prevent configuring a Message Routing peer with connection-mode per-client together with a transport-config with a source port if you are using SNAT, but that configuration does not work. If SNAT is enabled, and routing through a peer configured with a per-client connection-mode and a transport-config with a non zero source_port, only one client may connect to a server at a time. A second client will not be able to connect until the previous outgoing connection times out.

Impact

Only one client may connect to a server at a time - other clients will be unable to connect until the previous outgoing connection times out.

Conditions

Virtual Server configured with the following features: - Message Routing - Peer configured with connection-mode per-client - Transport Configuration with non-zero source port - Source Address Translation

Workaround

Disable one of the conflicting features: - Configure a different connection-mode for the peer - Disable Source Address Translation - Set source-port to 0 on the transport config (allow the BIG-IP to use any source port)

Fix Information

None

Behavior Change