Navigation

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

    HA Sync interfaces mismatch solved

    HA/CARP/VIPs
    1
    1
    465
    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.
    • G
      gesture1968 last edited by gesture1968

      For your information:

      As explained in the manual, when using High Availability all servers must have the same interfaces defined. Sometimes the networks defined on those interfaces do not match, usually due to incorrect configuration or even using different hardware for the servers. I had a simular problem when replacing the master, where the slave had a different interface order. Searching the internet gave me tips about changing the names of the interfaces in the config.xml, but this is only a visual renaming, it does not change the internal names of the interfaces. I ended up with renamed interfaces, but the CARP sync still gave a lot of issues.
      I eventually found the solution that I could not find on the internet: in the console one can reassign the interfaces to the networks by using option 1) Assign Interfaces. If you follow the following procedure you can get all interfaces back in sync and make the CARP sync function properly:

      • Check the internal interface names of the master:
        • In the console it is within parenthesis after the name (i.e. WAN (wan), LAN (lan), Network1 (opt1) etc)
        • The internal names for the interfaces in the slave should match those in the master, so check them there as well
      • If there is a mismatch between master and slave (i.e. opt1 in the master points to network1, while in the slave it points to network2), change the interface assignment in the slave:
        • Select option 1) Assign Interfaces in the console of the slave
        • Assign the correct interfaces to the WAN and LAN
        • Assign all OPTx interfaces to the networks matching the master
        • Go into the Web Configurator
        • Remove the non-matching interfaces (WAN and LAN should match) through the menu option Interfaces -> Interface Assignments on the slave
        • Now add the OPTx interfaces again in the same order as on the master. By default, they will appear as OPTx , so rename them to your desired network names and configure them with their respective network settings
        • Restart the slave after you have checked that the interfaces now have the correct order matching the master

      If all went well, the interfaces on both master and slave should match, the HA can be configured and the CARP should function correctly.

      Hope this helps.
      Regards

      1 Reply Last reply Reply Quote 0
      • First post
        Last post