‐‐‐ Original Message ‐‐‐
On Tuesday, April 30, 2019 9:29 PM, Lyndon Nerenberg wrote:
> On our systems, we run the 'a' machine as primary and the 'b' machine
> as backup. When upgrading, we do the 'b' machine first, since this
> doesn't disrupt the primary. After the 'b' machine is fully
mabi writes:
> Now I would first like to upgrade the cluster to 6.4 and then to 6.5 and was
> wondering if it is possible to operate that cluster for a short amount of tim
> e having one node running 6.3 and the other node with 6.4 and then the same f
> or going to 6.4 to 6.5.
In general this
mabi(m...@protonmail.ch) on 2019.04.30 08:21:43 +:
> Hello,
>
> I have an OpenBSD 6.3 firewall cluster made out of two nodes (one master, one
> backup) using CARP and pfsync. This cluster also makes use of trunk and vlan
> interfaces.
>
> Now I would first like to upgrade the cluster to
‐‐‐ Original Message ‐‐‐
On Tuesday, April 30, 2019 11:20 AM, Igor Podlesny wrote:
> CARP should be of no worries at all and PF state table's sync is
> easily verified.
> If after backup's upgrade-reboot it has roughly same amount of entries
> you can safely demote master and repeat
On Tue, 30 Apr 2019 at 15:24, mabi wrote:
[...]
> Is this safe? or could there be any incompatibilities in carp/pfsync which
> would prevent me to do that upgrade in two steps while keeping everything
> online?
CARP should be of no worries at all and PF state table's sync is
easily verified.
5 matches
Mail list logo
