I recently added the ms-lync-online app to a rule in my PA-500. We decided we didn't need it and removed it. After a month of commits and saves that app is still showing up in the commit window summary and asking for a required app with it. I have checked everywhere and that app is not part of any rule but the PA unit still thinks it is. Any ideas how to clear this.
While you are applying a commit on this firewall, it should show the "rule name" along with the warning messages.
Example:: Rule 'XYZ' application dependency warning:
Application 'ms-lync-base' requires 'kerberos' be allowed, but 'kerberos' is denied in Rule 'DenyAny'
Application 'ms-lync-base' requires 'sip' be allowed, but 'sip' is denied in Rule 'DenyAny'
Application 'ms-lync-base' requires 'soap' be allowed, but 'soap' is denied in Rule 'DenyAny'
Could you please verify that rule once. If that rule is not having an application "MS-LYNC" added, then do a "commit force" from CLI else, Deactivate that rule >>> commit and activate again >>> commit.
Hope this helps
We can commit the whole config and just not the differential config. This is how we do.
Once this is done can you test if you still see this.
If still seen can we do config Audit for the latest 2 config versions ( ALL for the lines ) and search for keyword ms-lync-online.
Also we can export the running configuration to a xml file and do search for the keyword ms-lync-online.
These should resolve or direct the resolution.
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!