Stuck on auto commit

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Stuck on auto commit

L3 Networker

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.

6 REPLIES 6

L7 Applicator

Do you have any more informations/details about a possible reason (provided by your firewall)?

Cyber Elite
Cyber Elite

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 ?

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

L3 Networker

I hope below process helps you

 

https://live.paloaltonetworks.com/t5/Management-Articles/How-to-upgrade-a-High-Availability-HA-pair/...

 

Regards,

Kotresha

Kotresha
ACE

L7 Applicator

I remember this happening once from low disk space during an upgrade.  Check the disk usage and possibly remove old update files.

 

https://live.paloaltonetworks.com/t5/Management-Articles/How-to-Free-Up-Disk-Space-in-PAN-OS-5-0/ta-...

Steve Puluka BSEET - IP Architect - DQE Communications (Metro Ethernet/ISP)
ACE PanOS 6; ACE PanOS 7; ASE 3.0; PSE 7.0 Foundations & Associate in Platform; Cyber Security; Data Center

L0 Member

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. 

L4 Transporter

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

Regards,
Sharief
  • 12428 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!