This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About codyh
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About codyh
03-08-2023
3Posts
0Likes
0Solutions
Mar 08, 2023Last Visited
User
Activity
User
Profile
Latest posts by codyh
| Subject | Views | Posted |
|---|---|---|
| 1811 | 11-03-2022 09:47 PM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 4 Likes | |||
| 2 Likes | |||
| 1 Like |
User Badges
Community Statistics
| Member Since | 01-30-2018 03:38 PM |
| Date Last Visited | 03-08-2023 05:03 PM |
| Posts | 3 |
11-03-2022
09:47 PM
We also ran into the same issue on an HA Active/Passive pair of PA-5220s. Our upgrade path was 9.1.14-h4 -> 10.0.11-h1 -> 10.1.8. We noticed on the dashboard that HA was down, and also all of the interfaces showed down and not configured. In Tasks we were getting the Auto Commit failure repeatedly with details of:
configured traffic quota of 0 MB is less than the minimum 32 MB. Invalid configuration. Please fix errors and try again.
Our uptime was 87 minutes when the Auto Commit finally completed. Once that was done everything appeared to be working as expected. Only one firewall in the pair had this happen, the other upgraded in a normal time window (15ish minutes).
As a note, you can check on RAID with cli command: show system raid detail
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks