- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-14-2011 11:07 AM
After upgrade from 3.1.7 to 4.0.1 and while attempting to configure the botnet reports; I tried to commit and recieved this error:
profiles -> spyware -> Spyware-Alert -> phone-home-detection -> custom -> 12656 -> action -> drop-packets is unexpected
I went to the offending signature and tried to change the action to the default and the system still won't take a commit nor accept the action change. I deactivated everything in the botnet config and tried again, still can't change the action on the sig. Where to from here?
Bing
03-14-2011 12:13 PM
Hi Bing,
It would be nice to have the running config so we can load that to our lab device with the hope of replicating the issue. Would you be able to call into Support so we can troubleshoot it further?
-Renato
03-17-2011 04:28 PM
One thing you can try:
Save to named config
Load named config
Commit
This seems to discard all of the changes made my the customer and restore the profiles to the default behavior.
Steve Krall
03-23-2011 06:33 AM
Final Followup
Sorry for the late reply. Tech Support had me drop back to a previous configuration then switch from my Custom Anti-Spyware Profile to the Simple one. This resolved the immediate problem of the Palo Alto not being able to accept a commit. I haven't gone back in and done any tinkering since, due to our ops policies and lack of a mx window.
Bing
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!