Last Modified: Nov 02, 2023
Known Affected Versions:
22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.5, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 15.1.4, 18.104.22.168, 15.1.5, 22.214.171.124, 15.1.6, 126.96.36.199, 15.1.7, 15.1.8, 188.8.131.52, 184.108.40.206, 17.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Dec 15, 2022 Severity: 2-Critical
In a case where traffic is not properly egressing a BIG-IP tenant running on rSeries or VELOS platforms, if any TMM log file contains any line with the text "notice SEP: Tx completion failed", that tenant VM may need to be manually restarted. The BIG-IP is unable to detect the traffic degradation automatically and recover or fail-over; the user must manually intervene to restart the tenant.
Egress traffic may be severely degraded until the tenant with the offending log messages is manually restarted.
This is specific to rSeries and VELOS platforms, and does not affect other BIG-IP platforms or virtual editions. Egress traffic from the affected tenant may appear to be degraded or non-functional. There may be a high number of transmit packet drops. Check the tenant TMM log files for any line containing the text "notice SEP: Tx completion failed" (which may include additional trailing text). The log files of concern reside in the tenant at paths: /var/log/tmm*
Restart the tenant VM by moving the tenant from deployed -> provisioned -> deployed in the partition or system ConfD command line interface. Alternatively, issue the "reboot" command from the tenant bash shell.