Altostratus
NimbostratusHi Oleksandr,
Did you get an answer on this? The Bug document only mentions 15.1.x releases as affected. Unsure if this is accurate, but could mean it's not an issue in v16?
AltostratusHi AP,
Interesting question. When I asked if this bug would be fixed in a newer version, a TAC engineer said that it would definitely be fixed, however BugIDs are managed by the F5 Product Development top management and unfortunatelly they do not share any detail regarding the schedule.
As a workaround, the implementation of Layered virtual server solution was proposed. (https://my.f5.com/manage/s/article/K03113285)
If you will have a proper answer to your question, please share it also with me.
Thank you in advance,
BR,
Oleksandr
NimbostratusHi,
No, I don't have any new information. It's a bit vague in the documentation, however I agree that it sounds like it won't be an issue in v16.
Regards.
AltostratusHi AP,
I received a confirmation that this bug is still not fixed in any BIG-IP version and it does not have a high priority at the moment. So I can assume that it will not be fixed soon.
BR,
Oleksandr
NimbostratusHi Oleksandr,
Thanks for the update. Appreciate it! Good to know.
Regards,
AP