This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FW Update Procedure on ASG-525 Cluster

Hi All,

I've got an ASG-525 active/passive cluster running on 8.102 which is rock solid.

Now that 8.300 has been released with the "import weblog" function I'm really keen to bump up to the latest version however I cannot seem to find any documentation on how to perform the upgrade in a clustered environment.

I've performed updates on stand-alone ASGs a stack of times.

Is it simply a matter of "update to latest version now" in the Up2Date and the ASGs sort it out or do I need to do something in addition such as power down the slave node or break the cluster and do one at a time?

Thought I would ask the question as we've 8 RED tunnels, some from overseas and I really want to minimize risk of extended downtime.

Apprecaite any input.

Cheers,
Mattrus

This thread was automatically locked due to age.

0 trollvottel over 13 years ago

Simply click the "Update to latest Version" button at Management >> Up2Date. All nodes will update, one adter the other to minimize downtime (if at all)
Cancel
Vote Up 0 Vote Down

Cancel
0 UrsWeiss over 13 years ago

Hi Mattrus

You can update a cluster just like a normal standalone ASG. It's doing everything for you if you click update to latest version now. In an active/active cluster you normally don't recognize a long downtime, if any. Maybe some seconds. Don't think it's much more if it is doing a controlled failover on an active/passive setup.

Even some time ago, when i updated an active/active cluster from 7.5xx to 8.0xx it haven't lost one ping to the firewall which was very impressing.

But i would wait a week or two before updating anyway, just to be sure there is no other bug they haven't found in the beta.

Urs
Cancel
Vote Up 0 Vote Down

Cancel
0 maygyver over 13 years ago in reply to UrsWeiss

Hi,

to minimze downtime, you should switch one node off.
Update the other one (now you have a planned downtime).
If something went wrong, you just switch on the second (and off the first) and everthing is fine.
If everthing is OK you just switch on the second, it then joins the Cluster and updates itself. (When you like to do this, wait until 8.3 is pushed through update channel)

Sven

Astaro user since 2001 - Astaro/Sophos Partner since 2008
Cancel
Vote Up 0 Vote Down

Cancel
0 mattrus over 13 years ago

Thanks All,

Great advice, much more confident to proceed now. Many thanks!

Cheers,
Mattrus
Cancel
Vote Up 0 Vote Down

Cancel