Solved
Forum Discussion
LiefZimmerman
Aug 28, 2023Admin
Rooti - If your post was solved it would be helpful to the community to select *Accept As Solution*.
Thanks for being part of our community.
Finally, i can answer to myself:
The updated version of the Bug shows, that F5 didn't provide the right info:
https://cdn.f5.com/product/bugtracker/ID878641.html
Affected versions still without the 16.x tree, but "Fixed in" 16.1.4.
And i can confirm the bug is fixed in our 16.1.4.
Rooti - If your post was solved it would be helpful to the community to select *Accept As Solution*.
Thanks for being part of our community.