ltm policy asm_auto_l7_policy
Hi Experts, We are migrating WAF in an HA pair from i4800 to i5800, UCS is loaded successfully on new pair. while comparing the configurations i found on some policy on previous node the status was legacy and on new node the status is published. what's the difference please? the status is highlighted in red in below config. old node config ltm policy asm_auto_l7_policy__epsite.telenorbank.pk { controls { asm } last-modified 2023-12-08:23:19:30 requires { http } rules { default { actions { 1 { asm enable policy /Common/PTCL-cloud_WAF } } ordinal 1 } } status legacy strategy first-match7 } New Node config ltm policy asm_auto_l7_policy__epsite.telenorbank.pk { controls { asm } last-modified 2024-04-17:13:00:12 requires { http } rules { default { actions { 1 { asm enable policy /Common/PTCL-cloud_WAF } } ordinal 1 } } status published strategy first-match }
Possible to export/import ASM policies via a script?
Is it possible to possible to export ASM policies from one F5 and then import the ASM policies into another F5 via a script? I'd like to export the ASM policies from our prod F5 and then import them into our DR F5 in bulk via a script instead of exporting/importing one by one. Thx
ASM suggestions: Allowing Meta character on URL or globally
Hi Everyone, I'm getting two different suggestions for the illegal metacharacter in URL (same char in both), one of them is suggesting to allow the metacharacter on URL level, the other is suggesting to allow the same metacharacter but in the URL character set, the only difference is that the second suggestion has the manual accept only sign. Keep in mind I only have one wildcard URL(*), so the suggestions must be related to the same URL. is this behavior expected? aren't both suggestions the same given my situation? what is the best practice in general? what does the manual accept indicate? extra info: version 12.1.2 policy type automatic