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

    LACP not working

    Scheduled Pinned Locked Moved General pfSense Questions
    113 Posts 2 Posters 24.9k 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.
    • C
      cyberbot @stephenw10
      last edited by cyberbot

      @stephenw10 said in LACP not working:

      My switch is set for Long LACP timeouts (the TIO flag) and yours it set short.

      Try changing that.

      Are you using a broadcom switch?
      i have changed the timeouts to long

      device(config)# lag blue dynamic
device(config-lag-blue)# lacp-timeout long

      but it stills shows blocked

      === LAG "Pfsense WAN" ID 1 (dynamic Deployed) ===
LAG Configuration:
   Ports:         e 1/1/1 e 2/1/1
   Port Count:    2
   Primary Port:  1/1/1
   Trunk Type:    hash-based
   LACP Key:      20001
Deployment: HW Trunk ID 1
Port       Link    State   Dupl Speed Trunk Tag Pvid Pri MAC             Name
1/1/1      Up      Blocked Full 1G    1     No  141  0   609c.9f4b.808c  WAN1
2/1/1      Up      Blocked Full 1G    1     No  141  0   609c.9f4b.808c  WAN2

Port       [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
1/1/1           1        1   20001   Yes   S   Agg  No   No   No   Def  Exp  Err
2/1/1           1        1   20001   Yes   S   Agg  No   No   No   Def  Exp  Err


 Partner Info and PDU Statistics
Port          Partner         Partner     LACP      LACP
             System ID         Key     Rx Count  Tx Count
1/1/1    4-e839.3511.faab        0        0         1
2/1/1    3-e839.3511.faab        0        0         1
      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        I'm using a Brocade ICX6450 there. It's a value you can set for each lag group:

        SSH@ICX6450-24P Switch(config-lag-lacp1)#lacp-timeout 
  long    Long timeout mode
  short   Short timeout mode

        Steve

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

          @stephenw10 said in LACP not working:

          I'm using a Brocade ICX6450 there. It's a value you can set for each lag group:

          SSH@ICX6450-24P Switch(config-lag-lacp1)#lacp-timeout 
  long    Long timeout mode
  short   Short timeout mode

          Steve

          Thank you Steve, i set it to long.
          see above
          appreciate your support

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

            You might have to redeploy it. The ports still show S in the Tio field.

            That's not something I've ever tried on this switch.

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

              @stephenw10 said in LACP not working:

              You might have to redeploy it. The ports still show S in the Tio field.

              That's not something I've ever tried on this switch.

              Thank you Steve,
              do you mean to remove the ethernets from the lag or delete the lag completed?
              i am getting this error

              Error: LAG WAN is deployed, please undeploy it first.
              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                It's been a while since I had to mess with anything on this switch but I believe, like that error implies, you cannot make changes to the lag while it's deployed. You'll have to 'undeploy' it to switch to long mode timeouts.

                You could also try changing the pfSense LACP timeout mode to fast (short) to match which might be easier. In 2.5 that's a GUI setting, I'm not sure I've ever set that in 2.4.5....

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

                  Ah here we go:

                  [2.4.5-RELEASE][root@7100.stevew.lan]/root: ifconfig lagg0 lacp_fast_timeout
[2.4.5-RELEASE][root@7100.stevew.lan]/root: ifconfig -vv lagg0
lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=500b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO>
        ether 00:e0:ed:86:a6:8c
        inet6 fe80::2e0:edff:fe86:a68c%lagg0 prefixlen 64 scopeid 0x15
        inet 172.21.16.206 netmask 0xffffff00 broadcast 172.21.16.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
        groups: lagg
        laggproto lacp lagghash l2,l3,l4
        lagg options:
                flags=90<LACP_STRICT>
                flowid_shift: 16
        lagg statistics:
                active ports: 2
                flapping: 0
        lag id: [(8000,00-E0-ED-86-A6-8C,02B2,0000,0000),
                 (0001,60-9C-9F-54-14-F2,561F,0000,0000)]
        laggport: ixl0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3f<ACTIVITY,TIMEOUT,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING>
                [(8000,00-E0-ED-86-A6-8C,02B2,8000,0001),
                 (0001,60-9C-9F-54-14-F2,561F,0001,0041)]
        laggport: ixl1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3f<ACTIVITY,TIMEOUT,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING>
                [(8000,00-E0-ED-86-A6-8C,02B2,8000,0002),
                 (0001,60-9C-9F-54-14-F2,561F,0001,0043)]

                  Though I note it did not cause the lagg to break with pfSense set as short and the switch as long...

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

                    @stephenw10 said in LACP not working:

                    ifconfig lagg0 lacp_fast_timeout

                    Thank you Steve,

                    do you mean i have to do it also on the pfsensen side too ?

                    ifconfig lagg0 lacp_fast_timeout
                    1 Reply Last reply Reply Quote 0
                    • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.