- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-14-2011 06:35 AM
IMO and my opinion only, I'd say 3.1.10 and 4.0.5 respectively.
Regards,
Renato
10-16-2011 10:53 PM
Hi,
Definitely 3.1.10 if you don't need 4.0.x new features, otherwise 4.0.5.
Regards,
Jones
10-18-2011 02:10 AM
Hi all,
First, thanks a lot for your input.
I will move to 4.0.5 (running like a charm in my lab on standalone device) because new features set.
I have another question.
Is is required to run the same sofware version on both members of the cluster.
The idea here is avoiding installing instable software on both members.
In case of problem, I can easily come back to the old version (failover).
Regards,
Hedi
10-18-2011 10:27 AM
It's required. Otherwise, one will be in non-functional state.
10-19-2011 01:28 AM
Hello,
First, thanks a lot your help.
Does this non-functionnal state occurs if we are upgrading in the same MAJOR release train (example from 4.0.3 to 4.0.5) ?
After reading the Document 'Upgrading HA pair from 3.1 to 4.0' is seems that it should not occur
'Were the upgrade taking place for a maintenance release, ie 3.1.6 to 3.1.7, the newly upgraded device would go to a passive state.'
Regards,
Hedi
10-19-2011 07:36 AM
Hi,
This state is continuous if the ha cluster does not have matching panos versions(3.1.x and 4.0.x) even if you try to make the passive device functional. Not the same when you're upgrading from say 4.0.3 to 4.0.5. Assuming both have the same panos after an upgrade and the passive was once non-functional, making it functional will bring it back into passive state.
-Renato
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!