NimbostratusHi guys
When I upgraded TMOS from 16.1.4.3 to 16.1.5, all traffic arrived at f5 ASM blocked by attack signature and I had to downgrade to 161.4.3 again. Do any have this problem?
tnx
CirrusI think most people are skipping version 16 since it's not supported on rSeries or VELOS platforms. Do you have any details about the signature? And the state of the signature prior to the upgrade?
MVPomidrostami_1994 Downgrading because of a signature blocking is not for me the best action as you could have just allowed the traffic.
It is possible that after the upgrade the signature file to be newer (if for example you have not maintained your AWAF/ASM signatures up to date 😉) or in some rare cases older than what was previously on your older AWAF system version, so after TMOS upgrade just upgrade the signature sets. I suggest doing a live update now on your old version cleaning any false positives then upgrade to the new TMOS version and do again a live update and see if there is an issue.