topic Re: 4.0.1 Unable to commit error "drop-packets is unexpected" in General Topics

4.0.1 Unable to commit error "drop-packets is unexpected"

b1989j — Mon, 14 Mar 2011 18:07:16 GMT

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

Re: 4.0.1 Unable to commit error "drop-packets is unexpected"

gswcowboy — Mon, 14 Mar 2011 19:13:38 GMT

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

Re: 4.0.1 Unable to commit error "drop-packets is unexpected"

skrall — Thu, 17 Mar 2011 23:28:18 GMT

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

Re: 4.0.1 Unable to commit error "drop-packets is unexpected"

b1989j — Wed, 23 Mar 2011 13:33:30 GMT

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