Bug ID 866021: Diameter Mirror connection lost on the standby due to "process ingress error"

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(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.4,, 12.1.5,, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,, 14.1.0,,,,,, 14.1.2,,,,, 15.0.0, 15.0.1,,,, 15.1.0,,,,

Fixed In:

Opened: Jan 02, 2020
Severity: 3-Major


In MRF/Diameter deployment, mirrored connections on the standby may be lost when the "process ingress error" log is observed only on the standby, and there is no matching log on the active.


Diameter mirror connections are lost on the standby. When failover occurs, these connections may need to reconnect.


This can happen when there is a large amount of mirror traffic, this includes the traffic processed by the active that requires mirroring and the high availability (HA) context synchronization such as persistence information, message state, etc.



Fix Information

Diameter mirror connection no longer lost due to "process ingress error" when there is high mirror traffic.

Behavior Change