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

LAGG and L2 redundancy confusion

L2/Switching/VLANs
2
8
977
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.
  • K
    Krisbe
    last edited by Oct 29, 2018, 4:40 PM

    Hi

    I'm setting up an environment with two pfSense firewalls and two (Mikrotik) switches. But I'm confused how to use LAGG and LACP. Is the setup the same when using LAGG between one firewall and one switch?

    See the attached image. Do I use the settings correct?
    On SW01, do I put both links to both firewalls in one LAG group? Or in two groups like in the image?

    login-to-view

    Thanks all

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Derelict Oct 29, 2018, 6:28 PM Oct 29, 2018, 6:26 PM

      That would be up to the switches.

      Are they physically stacked? If so, you should be able to just create an LACP LAGG using a port on each switch.

      If they are not stacked they'll need to support something like Multi-Chassis Trunking.

      It would be two LACP LAGGs - one to each firewall with the same VLAN(s) on them.

      Chattanooga, Tennessee, USA
      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
      Do Not Chat For Help! NO_WAN_EGRESS(TM)

      1 Reply Last reply Reply Quote 0
      • K
        Krisbe
        last edited by Oct 29, 2018, 7:27 PM

        Hi

        No, the switches are not stackable.

        "It would be two LACP LAGGs - one to each firewall with the same VLAN(s) on them."
        You mean two LAGG groups on both switches? Eg. like: in LAG1 both eth0 ports from fw01 and fw02 and in LAG2 both eth1 ports from fw01 and fw02? Or do I get that wrong?

        1 Reply Last reply Reply Quote 0
        • D
          Derelict LAYER 8 Netgate
          last edited by Oct 29, 2018, 7:29 PM

          I doubt you can create those laggs if the switches are not stackable.

          login-to-view

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • K
            Krisbe
            last edited by Oct 29, 2018, 8:33 PM

            Hi

            Hmm no okay, the switches are not stackable, so LAG won't be an option for now.
            My best option is to create the setup like described in https://www.netgate.com/docs/pfsense/book/highavailability/layer-2-redundancy.html I guess?

            Other ideas are welcome.

            1 Reply Last reply Reply Quote 0
            • D
              Derelict LAYER 8 Netgate
              last edited by Oct 29, 2018, 8:34 PM

              Yes. Without stacked switches (or MCT) that is probably your best guide.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • K
                Krisbe
                last edited by Oct 30, 2018, 6:35 AM

                What about the "FAILOVER" protocol instead of LACP? That is active/passive I think? Isn't that a solution for the 2-switch setup? Then I just need to create this LAGG on pfSense, but not on the switches?

                1 Reply Last reply Reply Quote 0
                • D
                  Derelict LAYER 8 Netgate
                  last edited by Oct 30, 2018, 3:35 PM

                  You can try it and test it. I've never done it.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

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