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

    Upgrading Dual-WAN + CARP?

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    6 Posts 3 Posters 2.0k Views
    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
      jasonlitka
      last edited by

      Any suggestions on how to go about upgrading a dual-wan + CARP setup from 1.2.3 to 2.0 (either now, as RC3, or when final)?  Do I upgrade the master or slave first?

      I can break anything.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        For any cluster, the suggestion is the same:

        • Upgrade the secondary, make sure it boots and runs OK
        • Fail over to the secondary as a test, make sure things still work like they should
        • If that test failed, reinstall back to the old version on the slave. If it passed, upgrade the master.
        • After both are upgraded, repeat any necessary failover tests.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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

          Ok, thanks.

          I can break anything.

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

            I would add one step going from 1.2.3 to 2.0, disable the config sync otherwise 1.2.3 will overwrite the config in the wrong format on the 2.0 box (2.0 has a check that prevents config sync to different config versions but 1.2.3 does not)

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

              @cmb:

              I would add one step going from 1.2.3 to 2.0, disable the config sync otherwise 1.2.3 will overwrite the config in the wrong format on the 2.0 box (2.0 has a check that prevents config sync to different config versions but 1.2.3 does not)

              Oh, good one.  If I disable the carp sync, will the CARP IPs still fail over to the second box?  If not, how exactly do I test the secondary system after the update?

              I can break anything.

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                Disabling the configuration sync won't disable CARP failover.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

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