64591 (The fix in this bug resolves two issues: o PA-3000 Series firewalls could stop passing traffic due to errors in the internal datapath. A registry value was changed in the dataplane packet processor to prevent this error. o When highly compressed traffic is passing through PA-7050, PA-5000 Series, or PA-3000 Series firewalls, this caused some additional latency in other traffic passing through the firewall. This fix prevents the latency from being introduced to the traffic by changing the amount of data being handled by the signature matching FPGA.)
Can you try to upgrade one more PAN OS 6.0.3 to PAN OS 6.0.4. i hope its helpful for you. thanks
Are you sure that bug id 64591 is what is causing this HA link error message?
Reading the notes and associated ticket reports, there is no mention at all of HA in any of them.
Yesterday we upgraded to 6.0.4 version and the issue arises again.
We followed the next steps:
1) We had two HA nodes in 6.0.2 NodeA NodeB 5020
2) We suspended the standby NodeB and install 6.0.4 version
3) We did a reboot NodeB to finish instalation
4) NodeB started without problem and it got in standby mode
5) We suspended the primary NodeA so NodeB took control as primary
6) We installed 6.0.4 version in NodeA an we did a reboot to finish
7) When NodeA was starting we got the issue at NodeB "Internal packet path monitoring failure, restarting dataplane"
😎 NodeA was not still ready to take control so we had a network outage of about 2 minutes.
So... if you are experiencing this problem TAKE CARE in migration, in our case the 6.0.4 version doesn't solve the issue.
We are going to open a case.
PAN requested we try to replicate the issue yesterday evening; the guy did apply this command - set system setting packet-path-test enable no - on the node that had issues before and restarted (he did not require restarting both nodes). The issue did not re-occur, but, this still does not guarantee is not going to in the future.
I don't quite know what this command does, but it looks like you apply it before the reboot, and once the node is up, it is cleared.
Because we were not able to replicate, it is not considered as a solved issue; we are required to call PAN if happening again, so they can collect more information.
Also, yes, I agree, this is the bug we are hitting - BUG-50153, even after upgrading to 6.0.3; we are not going to upgrade to 6.0.4.
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!