Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
06-06-2016 01:39 AM
I had PA200 in active/passive. Upgraded from 7.0.2 to 7.0.6. Rebooted passive unit. Keeps on failing auto commit. Which happned around 10 times and then just sitting there . Interfaces down. Rebooted again same thing.
I tries commit force. Disconnected HA port still same issue.
06-06-2016 05:11 AM
unless your passive link state is set to auto it would be normal for the interfaces to stay down. if you do a
> show jobs id <ID_of_autocommit>
, does it provide additional details why it failed ?
06-07-2016 05:30 AM
I hope below process helps you
Regards,
Kotresha
06-10-2016 04:19 PM
I remember this happening once from low disk space during an upgrade. Check the disk usage and possibly remove old update files.
06-26-2017 03:50 PM
I faced a similar issue while moving from 7.0.8 to 7.1.9
Turned out the captive portal was enabled & did not had the "authentication profile" linked to it. We did not use captive portal on this firewall thats the reason no one cared to check , but that costed some serious HA issues.
CP was later disabled & auto commit went through fine.
06-27-2017 02:34 AM
I had this issue before, auto commit kept failing without showing any error. I was reverting back to old configurations one by one till the commit was successfull, I turned out that during migration the NAT rule was not properly configured.
Regards,
Sharief
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!
