03-16-2021 03:15 AM
I had 2 VM-series firewalls running 10.0.3 in AWS which I had connected to my on-prem Panorama also running 10.0.3.
All looked fine until I made a change to the security policy and executed a commit & push to the VM's.
After this the Panorama commit status seemed to hand and then eventually came back with an error "job failed because of configd restart". After this I noticed that the VM's had disconnected from Panorama.
However, what was very strange was that the VM were still accessible and had not been restarted and they reported a connected status from a "show panorama-status" command!!
Has anyone else experienced this isssue? Any ideas what might be the cause? or haw to check & confirm cause?
Any help would be greatly appreciated.
04-09-2021 08:24 PM
You may want to upgrade your panorama to 10.0.5 if not done already.
Check the release notes here and search for "PAN-152813"
If that does not fix the issue, then I would suggest to open a support case with the tech support from panorama attached.
Hope this helps,
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!