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

    LACP not working

    Scheduled Pinned Locked Moved
    General pfSense Questions
    2
    113
    18.6k
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      It would be better to change that on the switch if you can but, as a test, you can set fast(short) mode in pfSense and that should also match each end.

      Steve

      C 1 Reply Last reply Reply Quote 0
      • C
        cyberbot @stephenw10
        last edited by cyberbot

        @stephenw10 said in LACP not working:

        It would be better to change that on the switch if you can but, as a test, you can set fast(short) mode in pfSense and that should also match each end.

        Steve

        Thank you Steve, ive done hte fast timeout on the pfsense unfortunately it still blocking the ports

        on the switch too

        === LAG "wan" ID 5 (dynamic Not Deployed) ===
LAG Configuration:
   Ports:
   Port Count:    0
   Primary Port:  none
   Trunk Type:    hash-based
   LACP Key:      20005
   LACP Timeout:  long

        both switches are stacked maybe forgot to mention, maybe its relevant .

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Ah, OK. Yes it could well be, have you configured it for cross-chassis lag?

          I have no experience of doing that with Brocade but I imagine it has to be configured for it.

          Steve

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Also check the switch logs. There is likely a reason those ports show as blocked and it should be shown there.

            C 1 Reply Last reply Reply Quote 0
            • C
              cyberbot @stephenw10
              last edited by

              @stephenw10 said in LACP not working:

              Also check the switch logs. There is likely a reason those ports show as blocked and it should be shown there.

              i cannot seems to find the cause yet.
              we are still investigating i am affraid the switch and pfsense are not a good friends.
              i will try to use a different switch maybe unifi switch L:ayer 3 switch

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Are you able to test a lagg to a single switch rather than cross-chassis?

                Or even just connect the ports individually outside of a lagg to be sure they come up as not blocked?

                Steve

                C 1 Reply Last reply Reply Quote 0
                • C
                  cyberbot @stephenw10
                  last edited by

                  @stephenw10 said in LACP not working:

                  Are you able to test a lagg to a single switch rather than cross-chassis?

                  Or even just connect the ports individually outside of a lagg to be sure they come up as not blocked?

                  Steve

                  i havent done that yet, need to drive to the Datacenter to try,

                  i remeber it working with one cable untill i connect the second cable.,

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    It seems like a loop that the switch is blocking then.

                    I would expect to see something in the switch logs.

                    C 1 Reply Last reply Reply Quote 0
                    • C
                      cyberbot @stephenw10
                      last edited by

                      @stephenw10 said in LACP not working:

                      It seems like a loop that the switch is blocking then.

                      I would expect to see something in the switch logs.

                      i've been kicking my head down to find the log of the switch.
                      cannot seems how to see them.
                      what are the commands for brodcad switches to see the logs?

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        On the ICX6450 I have it's show logging at least to get basic logs. I've never tried to get more.

                        C 1 Reply Last reply Reply Quote 0
                        • C
                          cyberbot @stephenw10
                          last edited by

                          @stephenw10 said in LACP not working:

                          On the ICX6450 I have it's show logging at least to get basic logs. I've never tried to get more.

                          Thank you Steve,
                          i know about the logging but thought i need seperate log check for the LAG only.

                          Dynamic Log Buffer (50 lines):
Nov 26 02:29:40:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:40:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:40:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:40:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:40:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:40:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:39:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:39:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:33:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:33:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:33:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:33:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:33:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:33:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:32:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:32:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:26:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:26:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:26:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:26:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:26:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:26:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:25:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:25:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:19:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:19:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:19:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:19:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:19:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:19:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:18:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:18:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:12:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:12:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:12:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:12:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:12:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:12:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:11:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:11:I:System: Interface ethernet 1/1/1, state up
Nov 26 02:29:11:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:05:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:05:I:Trunk: Group (2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:05:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:05:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:05:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:04:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is up.
Nov 26 02:29:04:I:System: Interface ethernet 2/1/1, state up
Nov 26 02:29:01:I:Trunk: Group (2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:01:I:System: dynamic lag 1, has new peer info (priority=32768,id=e839.3511.faab,key=715) (N/A)
                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Hmm, well I'm not familiar with that peer info mismatch but it doesn't look good!

                            I would think if you can resolve that it will come up OK.

                            Looks like this: http://docs.ruckuswireless.com/fastiron/08.0.80/fastiron-08080-l2guide/GUID-6298B5C2-295F-476A-9B99-E465BC0E4B0D.html

                            You have custom peer info values configured causing the mismatch?

                            Steve

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

                              @stephenw10 said in LACP not working:

                              You have custom peer info values configured causing the mismatch?

                              Thank you Steve
                              what do you mean with You have custom peer info values configured causing the mismatch? on the pfbox or switch?

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                On the switch, as shown in that doc.

                                C 1 Reply Last reply Reply Quote 0
                                • C
                                  cyberbot @stephenw10
                                  last edited by

                                  @stephenw10 said in LACP not working:

                                  On the switch, as shown in that doc.

                                  i always thought it on the switch, i dont understand about the mismatch value thing,
                                  but i need to do some research to see if i can fix it.

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    It's possible to set the peer-info value in the switch and that will break the lag if it doesn't match what the peer is actually sending.
                                    Without any peer-info set it accepts the first info it sees as dynamic.

                                    Check the lag config on the switch.

                                    Steve

                                    C 1 Reply Last reply Reply Quote 0
                                    • C
                                      cyberbot @stephenw10
                                      last edited by

                                      @stephenw10 said in LACP not working:

                                      It's possible to set the peer-info value in the switch and that will break the lag if it doesn't match what the peer is actually sending.
                                      Without any peer-info set it accepts the first info it sees as dynamic.

                                      Check the lag config on the switch.

                                      Steve

                                      Thank you Steve,
                                      to be honest i am a Cisco guy so dont know how to do this peer-info.
                                      as i understand i have to run this command on the lag ?

                                      peer-info sys-mac 609c.609c.609c sys-pri 10 key 29999
                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        Hmm, interesting. That doesn't match this:

                                        priority=4,id=e839.3511.faab,key=0

                                        Also unclear how the ports there appear to have a different priority set.

                                        What you are seeing appears to be the Brocade end MAC also.

                                        This is not something I've ever had to deal with either. 😉

                                        Steve

                                        C 1 Reply Last reply Reply Quote 0
                                        • C
                                          cyberbot @stephenw10
                                          last edited by

                                          @stephenw10

                                          where this comes from ?

                                          priority=4,id=e839.3511.faab,key=0
                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            From your switch log.

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