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

    Lagg - lacp not working after upgrade

    Scheduled Pinned Locked Moved
    Hardware
    5
    16
    3.8k
    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.
    • M
      mcrook
      last edited by

      Yes of course I did that. Still nothing.

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • M
        mcrook
        last edited by

        Apr 16 00:10:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:10:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:10:16 kernel: partner.state=0
        Apr 16 00:10:16 kernel: maxdelay=0
        Apr 16 00:10:46 kernel: dc2: lacpdu transmit
        Apr 16 00:10:46 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0003)
        Apr 16 00:10:46 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:10:46 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:10:46 kernel: partner.state=0
        Apr 16 00:10:46 kernel: maxdelay=0
        Apr 16 00:10:46 kernel: dc3: lacpdu transmit
        Apr 16 00:10:46 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0004)
        Apr 16 00:10:46 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:10:46 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:10:46 kernel: partner.state=0
        Apr 16 00:10:46 kernel: maxdelay=0
        Apr 16 00:11:16 kernel: dc2: lacpdu transmit
        Apr 16 00:11:16 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0003)
        Apr 16 00:11:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:11:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:11:16 kernel: partner.state=0
        Apr 16 00:11:16 kernel: maxdelay=0
        Apr 16 00:11:16 kernel: dc3: lacpdu transmit
        Apr 16 00:11:16 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0004)
        Apr 16 00:11:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:11:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:11:16 kernel: partner.state=0
        Apr 16 00:11:16 kernel: maxdelay=0
        Apr 16 00:11:46 kernel: dc2: lacpdu transmit
        Apr 16 00:11:46 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0003)
        Apr 16 00:11:46 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:11:46 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:11:46 kernel: partner.state=0
        Apr 16 00:11:46 kernel: maxdelay=0
        Apr 16 00:11:46 kernel: dc3: lacpdu transmit
        Apr 16 00:11:46 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0004)
        Apr 16 00:11:46 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:11:46 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:11:46 kernel: partner.state=0
        Apr 16 00:11:46 kernel: maxdelay=0
        Apr 16 00:12:16 kernel: dc2: lacpdu transmit
        Apr 16 00:12:16 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0003)
        Apr 16 00:12:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:12:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:12:16 kernel: partner.state=0
        Apr 16 00:12:16 kernel: maxdelay=0
        Apr 16 00:12:16 kernel: dc3: lacpdu transmit
        Apr 16 00:12:16 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0004)
        Apr 16 00:12:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:12:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:12:16 kernel: partner.state=0
        Apr 16 00:12:16 kernel: maxdelay=0
        Apr 16 00:12:46 kernel: dc2: lacpdu transmit
        Apr 16 00:12:46 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0003)
        Apr 16 00:12:46 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:12:46 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:12:46 kernel: partner.state=0
        Apr 16 00:12:46 kernel: maxdelay=0
        Apr 16 00:12:46 kernel: dc3: lacpdu transmit
        Apr 16 00:12:46 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0004)
        Apr 16 00:12:46 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:12:46 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:12:46 kernel: partner.state=0
        Apr 16 00:12:46 kernel: maxdelay=0
        Apr 16 00:13:16 kernel: dc2: lacpdu transmit
        Apr 16 00:13:16 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0003)
        Apr 16 00:13:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:13:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)
        Apr 16 00:13:16 kernel: partner.state=0
        Apr 16 00:13:16 kernel: maxdelay=0
        Apr 16 00:13:16 kernel: dc3: lacpdu transmit
        Apr 16 00:13:16 kernel: actor=(8000,00-30-6E-5F-25-5E,0166,8000,0004)
        Apr 16 00:13:16 kernel: actor.state=4d <activity,aggregation,sync,defaulted>Apr 16 00:13:16 kernel: partner=(FFFF,00-00-00-00-00-00,0000,FFFF,0000)</activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted></activity,aggregation,sync,defaulted>

        1 Reply Last reply Reply Quote 0
        • M
          mcrook
          last edited by

          Bump

          Doesn't anyone else face this problem?

          Should I file a bug report since the turn table is being ignored?

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

            The tunable works fine. What does the output of "ifconfig" show for the lagg interface(s)?

            1 Reply Last reply Reply Quote 0
            • R
              robi
              last edited by

              What turn table, dude? :o

              1 Reply Last reply Reply Quote 0
              • M
                mcrook
                last edited by

                lagg0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                options=80008 <vlan_mtu,linkstate>ether 00:30:6e:5f:25:5e
                inet6 fe80::230:6eff:fe5f:255e%lagg0 prefixlen 64 scopeid 0xb
                inet 192.168.25.19 netmask 0xfffffc00 broadcast 192.168.27.255
                nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
                status: active
                laggproto lacp lagghash l2,l3,l4
                laggport: dc3 flags=0<>
                laggport: dc2 flags=0<></performnud,auto_linklocal></vlan_mtu,linkstate></up,broadcast,running,simplex,multicast>

                1 Reply Last reply Reply Quote 0
                • M
                  mcrook
                  last edited by

                  I know its been awhile but I would like to get this working

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

                    Maybe that's a regression in the dc driver in FreeBSD 10.x (it's for ancient NICs and probably not widely tested in more advanced configs, and not at all by us). Might want to try a different type of NIC, one like em or igb that's widely used with LACP. Or the latest 2.3 snapshot to see if it's something that was fixed between 10.1-REL and 10-STABLE.

                    1 Reply Last reply Reply Quote 0
                    • M
                      mcrook
                      last edited by

                      I'll try a snapshot, but it seems really silly that what worked in BSD9 doesn't in BSD10, but maybe it was over looked. As far as replacing the nic, its a 4 port that came with my rack server and I have limited funds to work with, but thank you for the idea though. I might keep an eye out for a more recent switch.

                      the switch by the way is an Avaya p133

                      1 Reply Last reply Reply Quote 0
                      • M
                        mcrook
                        last edited by

                        I have changed NICs and get the same result.

                        $ ifconfig lagg0
                        lagg0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                        options=8009b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,linkstate>ether 00:21:9b:fc:d4:fd
                        inet6 fe80::221:9bff:fefc:d4fd%lagg0 prefixlen 64 scopeid 0xb
                        inet 192.158.25.19 netmask 0xfffffc00 broadcast 192.158.27.255
                        nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect
                        status: active
                        laggproto lacp lagghash l2,l3,l4
                        laggport: bge1 flags=0<>
                        laggport: bge0 flags=0<></performnud,auto_linklocal></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,linkstate></up,broadcast,running,simplex,multicast>

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