Forum Discussion
PEM Policy Rule Classification Didnt Match
i have tried select url filter only but still didnt match.
let me try iRule if it works..
Also it is interesting if you can check if the subscriber is matching the default second policy as mentioned in https://techdocs.f5.com/kb/en-us/products/big-ip-pem/manuals/product/pem-implementations-13-1-0/30.html Maybe also try to see if you can enable extra logging under Policy Enforcement > Subscribers > Activity Log > Configuration as you can use a local publisher to see the data on the F5 device itself.
That are my final ideas as this could be a lab related issue as PEM is usually not available for LAB VM and maybe with the URL DB not licensed even the custom URL categories could having issues but I can't confirm this.
- hasmadihadiMar 24, 2023Altostratus
i didnt find the second policy in the link you provided. maybe you can point any quotes so can find it.
i am quite sure the static subcriber match the policy and it just didnt match rule even with higher precedence than any rule in the same policy.
if i enable URL filtering and PEM URL filtering license, is there any conflict?
- Nikoolayy1Mar 24, 2023MVP
I meant second rule not second policy, my mistake.
About "if i enable URL filtering and PEM URL filtering license, is there any conflict?" I have not enabled them at the same time to give you an answer to that question. Better check with the sales/solutions engineer that probably is helping you for the PoC.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com