Last Modified: Apr 05, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.5.0
Opened: Jan 12, 2024 Severity: 2-Critical
There is known issue article about it - https://my.f5.com/manage/s/article/K000138092 When a hot-plug network event occurs, it may lead to a TMM crash and TMM may not restart properly because of new interface names in the linux.
User data traffic gets affected because of the tmm's restart due to SIGABRT. Even after restarting the tmm, it may not come up cleanly.
When a hot-plug network event occurs in Azure cloud for a BIG-IP VE, it may cause the interface name changes at the OS level. This interface name change invalidates the mapping that TMM keeps to identify dataplane interfaces, thus causing a tmm crash with following error in the tmm.log: notice stp_state_set: err - undefined ifnet for interface 1.1
MLNX_OFED (Mellanox OpenFabrics Enterprise Distribution) drivers needs to be upgraded. In Neptune we have used upgraded version of MLNX_OFED, so Neptune is not affected by this bug. For other release a MLNX_OFED patch (clean-up vlan rule) is applied. BIG-IP VE should be restarted to make sure the TMOS controlplane and dataplane can cleanly regenerate the dataplane interface mapping.
None