No valid URL filtering license warnings on firewalls that are not supposed to have the license

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

No valid URL filtering license warnings on firewalls that are not supposed to have the license

L2 Linker

I have several firewalls which use URL filtering and are licensed for it, and several that do not.  In Panorama, all the firewalls that do not use it constantly have the Warning:

commit warning (2).png

 

If I click in to the details I see:

 

  • . Warning: No valid threat content package exists
  • . Warning: No valid Antivirus content package exists
  • . vsys1
  • . Warning: in vsys1, 3 warnings for profiles and profile groups: No valid URL filtering license,
  • . (Module: device)

 

How do I prevent this?  it is potentially masking legitimate problems. 

 

2 accepted solutions

Accepted Solutions

Cyber Elite
Cyber Elite

this means you are pushing URL filtering profiles to the not-licensed firewalls as well

you can solve this by splitting licensed and non-licensed devices into device groups so the URL filtering profiles are not pushed to the firewalls without license, or create double rules in the same device group and use 'target' to assign URL filtering enabled rules only to licensed firewalls

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

View solution in original post

L2 Linker

Thanks,  I managed to find the rogue rule, which cleared the error on the Policies last commit.  To clear the Template last commit state warning, I had to remove the Dynamic Updates for Threats and Antivirus for those firewalls.

View solution in original post

2 REPLIES 2

Cyber Elite
Cyber Elite

this means you are pushing URL filtering profiles to the not-licensed firewalls as well

you can solve this by splitting licensed and non-licensed devices into device groups so the URL filtering profiles are not pushed to the firewalls without license, or create double rules in the same device group and use 'target' to assign URL filtering enabled rules only to licensed firewalls

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

L2 Linker

Thanks,  I managed to find the rogue rule, which cleared the error on the Policies last commit.  To clear the Template last commit state warning, I had to remove the Dynamic Updates for Threats and Antivirus for those firewalls.

  • 2 accepted solutions
  • 5206 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!