We did a push from Panorama for a HA pair, it succeeded on the Passive member, but Commit Timed Out on the Active member.
However, when looking at the firewall we do see that the commit was Succeeded looking in Monitor>Logs>Configuration, and it is in sync with the configuration pushed on the Passive. And the push was completed at the same time on both devices.
The sending /receiving timeout values in Panorama are set to default 240 seconds.
Could someone help us in understanding why are we seeing the timeout issue on the Panorama and how do we fix this issue?
Running on 9.1.15-h1
Hi @Param_Upadhyay ,
If you are seeing on the firewall that the commit is in fact successful, I would increase the default timeout from 240 to 300 seconds to see if that gives it enough time.
Is this behavior experienced on every commit and push?
Just experienced the same issue in our environment. Azure Panorama running on PAN-OS 10.2.4, and FW running on 10.1.8-h2. Panorama says it timed out, however, the config status (shared policy & template) is correct and the same as on other FWs in the same device group/template. FW locally says in config logs, that the commit succeeded.
Receive/Send timeout for connection to Device is set to 120 sec.
However, this does not seem to be an issue with timeout itself, since the config actually goes through to the firewall and then it's successful.
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!