Commit Warning for Antispyware

[Hamid.Saffarzadeh]

Hi guys,

Trust all is well. After the firewall upgrade to version 10.2.1/ 10.2.2, we are getting the following errors after each firewall. Changes/commits are executed successfully. And everything seems to be working without problems.

Warning: spyware-profile AntiSpy-Alarm-Only(id: 251) is considered duplicate of AntiSpy-D(id: 258)
Warning: spyware-profile AntiSpy-Block-IP(id: 252) is considered duplicate of AntiSpy-D(id: 258)

Any idea?

Thank you in advance.

[BPry]

If you look at the firewall is the profile AntiSpy-D actually visible in the GUI or the CLI? I'd see if you actually utilize that profile in your configuration at all or not, and if you don't I'd just remove it as it seems likely that this was a configuration migration error when you upgraded. 

[Hamid.Saffarzadeh]

Hi BPry,

Thank you for your reply. The three Spyware profiles are being used under many security rules and it is not possible to delete one of them. We also created a dummy Spyware profile to no avail. Warnings are still present.

[kiwi]

Hi @Hamid.Saffarzadeh ,

Root cause for this issue might be because configuration details of two profiles are exactly same, the profiles will be identified as duplicate ones.

This is considered a cosmetic bug and will not interfere on operational level. Targeted to be fixed in PAN OS 10.2.4 but please reach out to support to confirm if you're hitting this exact same bug.

Cheers,

-Kiwi.

[Hamid.Saffarzadeh]

Hi team,

I have just got a confirmation on the fix. It will be included in the PAN-OS 10.2.4.

Cheers,
Hamid

[VinceM]

Hi all,

Hamid, have you got bug ID for this issue ?

Rgds

Vincent

[VinceM]

Just got info: ref PAN-194988 target to be solved in Version 10.2.4.

[AlexNC]

We are facing the same issue after upgrading to 10.2.3
But in our case the Spyware profiles do not match.
Spy-Alert-Only = crit,high,med to Alert (rest is default)
Spy-Outbound ) crit,high  to reset-both / med,low,inf to Alert

So the profiles are not the same, but still we get the working that our Alert Profile is a duplicate of our Outbound.
Is that also expected buggy behaviour 

Cheers

Alex