Bug ID 644565: MRF Message metadata lost when routing message to a connection on a different TMM

Last Modified: Oct 10, 2018

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3

Opened: Feb 12, 2017
Severity: 3-Major

Symptoms

The system might choose to create a new outgoing connection when there is an available exiting connection that can be used.

Impact

Messages should be delivered correctly as the metadata is lost after routing. There might be an impact if routing is retried and the ignore-peer-port setting is lost. This might cause a new connection to be created when an available existing connection exists.

Conditions

When a message is forwarded to another TMM for delivery, an internal state might be lost.

Workaround

None.

Fix Information

The system now ensures that the ignore-peer-port flag is preserved when forwarding a message to a connection on another TMM.

Behavior Change