Forum Discussion
hello ahmed
Upgrade to 16.1.0 first and then 17.1.0.3
What is impact running this workaround, does asm policy disable because this is production and is this sync to stanby device ?
as long there is no any notes in the article says that performing these procedures will not make negative impact.
So you should do that in a maintenance window.
Disabling this policy from virtual server should solve your issue and shouldn't make any negative impact in your production traffic as you remove an additional layer of security ( ASM policy ).
- Anzine321Oct 16, 2023Altocumulus
base on support f5, they found related to this bug
BIG-IP becomes offline/inoperative after upgrading to 17.1.0 (f5.com)
but iam not sure how to check name virtual server morethan 64 characters, as i know on my configure the virtual server less than 45 characters, is that related to description will count to ?
- Oct 16, 2023
Hi Anzine321 ,
Have you tried to rollback the upgrade from 17.1.0.3 to 16.1.0 again and check if the same behavior happens.
because if this confirmed a bug you will need to request a hot fix from F5 support.
If you don't know the number characters of your virtual server , you can delete it and create it again with very little characters :
https://my.f5.com/manage/s/article/K31352021