Last Modified: Jan 17, 2020
See more info
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52
14.0.0, 184.108.40.206, 13.0.1, 12.1.3
Opened: May 17, 2017
Related AskF5 Article: K31190471
The most common symptom is a reboot of the unit without much detail in the normal tmm or ltm logs. From there, inspect the SEL logs. In the SEL logs, you will see a message about a bad_tlp_status, followed shortly by a message about completion_time_out_status. Those two messages together indicate this known issue.
The unit intermittently reboots.
-- There are empty 10 GB ports or 10 GB ports that have optics but are not connected to a proper link. -- Running on one of the following platforms: i2600, i2800, i4600, i4800.
To prevent the issue from occurring, you must populate all 10 Gb ports with optic cables and ensure they are connecting to a working peer link. A single 10 Gb empty or improperly connected port can cause a system reboot. If that is not possible, however, there is no workaround, and you must contact F5 Technical Support to request a software update or engineering hotfix. Important: A device Return Materials Authorization (RMA) will not prevent this issue.
There is a BIG-IP system software update to disable the 10 Gb FPGA mac receiver until a valid link is detected. This eliminates the issue and prevents the ultra jumbo packet from being sent to the FPGA datapath.