Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Upgrade a cluster of fw

    Problems Installing or Upgrading pfSense Software
    3
    4
    3.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jdh
      last edited by

      Hi !

      I have 2 cluster of 2 firewall pfSense 1.2.2 using CARP …

      I'm considering the upgrade of these firewall.
      The howto is perfect for a single firewall but doesn't describe the procedure for a CARP cluster.

      Which method is better (or only successfull) :

      • upgrade the master firewall then the slave firewall,
      • upgrade the slave firewall then the master firewall,
      • save the config, break the carp, upgrade the slave (without network), restore the config, plug the slave on network, upgrade the "master" and redefine carp.

      Do you have experiences on this ?
      Thanks.

      Albert EINSTEIN : Si vous ne pouvez pas l'exprimer simplement, c'est que vous ne le comprenez pas assez bien. (If you can’t explain it simply, you don’t understand it well enough.)

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        I always upgrade the slave first. Then after checking that everything looks good, I upgrade the master.

        1 Reply Last reply Reply Quote 0
        • J
          jdh
          last edited by

          Thanks for this quick reply.

          Indeed, this seems the usual way IMHO, the usual first idea.

          The first step is obvious : upgrade the slave.
          But after the slave reboot and after synchronize from master, we need to test if slave could run alone (during the upgrade of the master).
          I suppose I can unplug the master and look if the slave become master ?
          It's easy to come back at this time if the slave doesn't run well (reinstall the previous 1.2.2 and resynchronise)

          So you consider :

          • backup config,
          • upgrade slave,
          • test unplug master (regression : reinstall 1.2.2 + resynchro from master),
          • when Ok, upgrade master, during slave act as "master",
          • after master reboot, test unplug slave (regression : reinstall 1.2.2 + restore config),
          • plug slave,
          • try unplug any and look,
          • then site B the same !

          Ok, I will try this plan on next saturday morning available (with nobody working !)

          • if Ok

          Albert EINSTEIN : Si vous ne pouvez pas l'exprimer simplement, c'est que vous ne le comprenez pas assez bien. (If you can’t explain it simply, you don’t understand it well enough.)

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            You can just disable CARP on the master to force it to fail over. Or shut down the master. Normally I do what dotdash recommended.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.