Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 26 subscribers
  • Views 1919 views
  • Users 0 members are here
Options
Suggested
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

How to migrate an existing port to LAG

MarcelStürtz

Hi there

We have an HA setup with two XG210's. Currently, port 1 is used for our LAN. I want to connect the two SFP ports (port7 and port8) with LACP to my stack of core switches and have the traffic of port1 over this LAG. So the LAG interface replaces port1 and all of its traffic. The benefit of this is the increased bandwidth (2gbit) and the redundancy (two interfaces on two different switches).

I can think of different strategies to accomplish this.

  1. assign different IP to port1 in same range, assign previous IP from port1 to LAG, change all the firewall and NAT rules, clear IP from port1
  2. assign different IP to port1 in another range, manage it from port1, assign previous IP from port1 to LAG, change all the firewall and NAT rules.
  3. do something smart from the CLI, not figured this one out yet.

But I could totally break the setup. Since I have HA, is it possible to disconnect the auxiliary, configure it the way I want it, test it and connect the auxiliary unit to establish HA, but if it is broken continu on the auxiliary? And synchronise back to restore the working settings? Or should I just use the backup and restore command from the GUI?

  • Does port1 allways have to be reachable? Probably yes.
  • Is the XG manageable from a LAG interface? Probably yes,
  • Should any of these scenario performed from any other interface than port1 and/or the LAG? Probably yes also...

I'm open to suggestions! Thanks!



This thread was automatically locked due to age.
Parents
  • 0

    Hi Marcel,

    You wouldn't be able to do this in production with little down time that is for sure.

    Unless you have specifically assigned BAPs, static routes or DHCP servers to the Port1 interface this would be the quickest solution:

    • Deconfigure Port1 (zone to none)
    • Configure LAG of SFP ports with IP of Port1
    • Recreate any missing/broken config from the move

    You could make a LAG of Port1, Port7 and Port8 I think would be the only other way but either way any configuration attached to Port1 is going to be deleted as interfaces are destroyed and remade when LAG/Bridging is done.

    You will have to break HA and rebuild it once you have done because you cannot modify the monitored ports without rebuilding, I would not both doing the break this and move that method then try and synchronise you're in a for a world of potential pain if you try that, I would just take a backup file and if the brown stuff hits the spinny thing just revert to backup.

    Answers to your Qs:

    • All ports are just interfaces, I would always recommend having a backup port i can directly connect to
    • Yes, the LAG is just a big interface made up of smaller ones
    • Not sure of the question but i'm going to awkwardly say "yess..?"

    Hope that helps!

    Emile

Reply
  • 0

    Hi Marcel,

    You wouldn't be able to do this in production with little down time that is for sure.

    Unless you have specifically assigned BAPs, static routes or DHCP servers to the Port1 interface this would be the quickest solution:

    • Deconfigure Port1 (zone to none)
    • Configure LAG of SFP ports with IP of Port1
    • Recreate any missing/broken config from the move

    You could make a LAG of Port1, Port7 and Port8 I think would be the only other way but either way any configuration attached to Port1 is going to be deleted as interfaces are destroyed and remade when LAG/Bridging is done.

    You will have to break HA and rebuild it once you have done because you cannot modify the monitored ports without rebuilding, I would not both doing the break this and move that method then try and synchronise you're in a for a world of potential pain if you try that, I would just take a backup file and if the brown stuff hits the spinny thing just revert to backup.

    Answers to your Qs:

    • All ports are just interfaces, I would always recommend having a backup port i can directly connect to
    • Yes, the LAG is just a big interface made up of smaller ones
    • Not sure of the question but i'm going to awkwardly say "yess..?"

    Hope that helps!

    Emile

Children
No Data