Loading...
Loading...
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 kernel.
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
None
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.