asm policy blocking mode to transparent but still blocking the traffic

[herdi]

hello

I have a problem on policy blocking mode change to transparent mode but the traffic still blocking

How to check this case

[Mohamed_Ahmed_Kansoh]

Hi @herdi , 

Do you receive Support IDs after putting the policy in transparent mode ? 

[herdi]

yes on event log report

on log asm the change to transparent mode was success without error but the traffic still block

i am not sure is related after upgrade from os 14.1.4.6 to 17.1.0.3

based on this 

https://my.f5.com/manage/s/article/K67645520

but i donw know how to check 

ASM DCC database got corrupted during the upgrade

[Mohamed_Ahmed_Kansoh]

Hi @herdi , 

Yes maybe you hit in " ASM DCC database got corrupted during the upgrade "

But I am wodering how did you perform this upgrade from 14.1.x to 17.1.x directly, it's not supported in F5 upgrade path you should upgrade first to 15.1.x or 16.1.x and then go for 17.1.x 
https://my.f5.com/manage/s/article/K13845

but anyway , try to perform the workaround in that Article you sent and let me know if this solved it or not yet 

[herdi]

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 ?

[Mohamed_Ahmed_Kansoh]

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 ). 

[herdi]

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 ?

[Mohamed_Ahmed_Kansoh]

Hi @herdi , 

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