I wanted to upgrade our PAN 2050 yesterday evening from 4.1.8 to 5.0.1
directly and had issue with error message on my active unit seeing that (peer
non functional and peer version no compatible or not the same as local,
something like that).
After searching and didn't find any doc that explain the process upgrade
from 4.1.x to 5.0.X I did a downgrade, and today I saw this discussion that is
very helpful. do you thing that I have follow the same process described here
to upgrade to 5.0.1 and do you thing that is really mandatory to pass first by
5.0.0 before going to 5.0.1.?
Thanks for your help
When upgrading to a major release in you case from 4.1.8 to 5.0.1 you have to always install the base release of the Major release.
So in other words when upgrading from 4.1.8 you first have to download 5.0.0 and then download and install 5.0.1.
Hopefully this helps.
Thanks for your quick answer, but in fact I already did that, i mean I downloaded on both my devices active and passive first v5.0.0 (without installing as was specified by the device, just download) and after that I downloaded the v5.0.1 and installed on passive unit, but after the reboot of the passive unit I had the status non fonctional and on the active I saw the HA status ( something like peer non fonctional (peer version nocompatible or mismatch) so I did the downgrade.
Could be very helpfull from Palo to have a official process or doc for that, I really dont understand way there is no doc for that.
Thanks for the link, but I followed the process described on
this doc till point 4. And I had the status of the HA (no fonctional “peer
version mismatch or not the same”) and
at this point my understanding is that the HA is not functional and if I went
to point 6 to suspend the second device I
have had a loss of connectivity and didn’t know if the upgraded device will
take the active role and if yes after how many time, as I didn’t plan on this
evening any downtime of our internet line I did a rollback
Thanks for your comment
I get why you'd be concerned, and the document could be improved by describing what is expected to happen at step 6. As you stated, it appears like you have a broken cluster and so FUD creeps in and so you are reluctant to pull the trigger and finish the upgrade.
In reality, all is well and when you suspend the active device at step 6, the newly upgraded device will take over, it just isn't documented or explained anywhere that I've seen. You might drop a couple of pings but that's it.
I'd like to hear from PAN support to explain what's going on at step 6. If I had to guess, it would have something to do with the HA interfaces being smart and taking action on the cluster, even though it looks broken at the time.
Open a support case and talk to them about it, then give it a shot!
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 Live Community as a whole!
The Live Community thanks you for your participation!