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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Looking at the switch there it looks like you might have short timeouts set?

      For reference:

      SSH@ICX6450-24P Switch>show lag
      Total number of LAGs:          1
      Total number of deployed LAGs: 1
      Total number of trunks created:1 (123 available)
      LACP System Priority / ID:     1 / 609c.9f54.14f2
      LACP Long timeout:             90, default: 90
      LACP Short timeout:            3, default: 3
      
      === LAG "lacp1" ID 2047 (dynamic Deployed) ===
      LAG Configuration:
         Ports:         e 1/2/1 e 1/2/3 
         Port Count:    2
         Primary Port:  1/2/1
         Trunk Type:    hash-based
         LACP Key:      22047
         LACP Timeout:  long
      Deployment: HW Trunk ID 1
      Port       Link    State   Dupl Speed Trunk Tag Pvid Pri MAC             Name
      1/2/1      Up      Learn   Full 10G   2047  No  1    0   609c.9f54.150b                 
      1/2/3      Up      Learn   Full 10G   2047  No  1    0   609c.9f54.150b                 
      
      Port       [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
      1/2/1           1        1   22047   Yes   L   Agg  Syn  Col  Dis  No   No   Ope
      1/2/3           1        1   22047   Yes   L   Agg  Syn  Col  Dis  No   No   Ope
                                                                        
      
       Partner Info and PDU Statistics 
      Port          Partner         Partner     LACP      LACP     
                   System ID         Key     Rx Count  Tx Count  
      1/2/1    32768-00e0.ed86.a68c      690        4         4
      1/2/3    32768-00e0.ed86.a68c      690        3         5
      
      1 Reply Last reply Reply Quote 0
      • C
        cyberbot @stephenw10
        last edited by cyberbot

        @stephenw10 said in LACP not working:

        Maybe check debugging is still enabled. You should see some log entries from lacp there.

        Edit: Sorry missed a whole post of yours somehow. Ok I see logs showinh both ends timing out.

        And it still showed flapping with only one NIC connected? em2 there in the logs?

        What do you see if you run: ifconfig -vv lagg0?

        Steve

        Hi Steve
        yes each NIC I connect em0 or em3 it shows the flagging error.
        what do you mean with time out of set?

        root@pfsense:~ # ifconfig -vv lagg0
        lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
                options=8520b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
                ether 00:08:a2:0c:99:7b
                inet6 fe80::208:a2ff:fe0c:997b%lagg0 prefixlen 64 scopeid 0x10
                inet 192.168.15.1 netmask 0xffffff00 broadcast 192.168.15.255
                laggproto lacp lagghash l2,l3,l4
                lagg options:
                        flags=10<LACP_STRICT>
                        flowid_shift: 16
                lagg statistics:
                        active ports: 2
                        flapping: 0
                lag id: [(8000,00-08-A2-0C-99-7B,020B,0000,0000),
                         (8000,74-83-C2-48-2F-67,0042,0000,0000)]
                laggport: igb4 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3d<ACTIVITY,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING>
                        [(8000,00-08-A2-0C-99-7B,020B,8000,0005),
                         (8000,74-83-C2-48-2F-67,0042,0080,0017)]
                laggport: igb5 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3d<ACTIVITY,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING>
                        [(8000,00-08-A2-0C-99-7B,020B,8000,0006),
                         (8000,74-83-C2-48-2F-67,0042,0080,0018)]
                groups: lagg
                media: Ethernet autoselect
                status: active
                nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        
        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

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

          Try changing that.

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