Date: Thu, 20 Oct 2016 08:20:24 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Message-ID: <bug-213606-2472-KvITyenCUy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213606-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-213606-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 Borja Marcos <borjam@sarenet.es> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |borjam@sarenet.es --- Comment #8 from Borja Marcos <borjam@sarenet.es> --- Deja vu with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D150249 The main symptom was lagg refusing to work in LACP mode.=20 In this case, the reason was that the driver didn't detect media properly, = and the "paperwork" with the kernel failed: the interface wasn't marked as full duplex. As a result, LACP (which checks the full-duplex flag for the interf= ace) refused to use it. Remember that full-duplex is a prerequisite for LACP. This seems to be a case of incomplete paperwork as well, although the neces= sary bits seem to be in place. In my case this was the problem with LACP (ieee8023ad_lacp.c): --------- /* * If the port is not an active full duplex Ethernet link then it c= an * not be aggregated. */ if (IFM_TYPE(media) !=3D IFM_ETHER || (media & IFM_FDX) =3D=3D 0 || ifp->if_link_state !=3D LINK_STATE_UP) { lacp_port_disable(lp); } else { lacp_port_enable(lp); } --------- But according to ifconfig the interface is marked as full duplex and media seems to be Ethernet. I would add some printf's here to check if this is re= ally the case and some other check is failing. What does ifconfig -m say of the interfaces? But that lack of options looks like a driver bug. And it would help to see its capabilities as reported by ifconfig. This is an example with an "em" interface. --------- % ifconfig -m -v -v em0 em0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 = mtu 1500 =20=20=20=20=20=20=20 options=3D4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_= MAGIC,VLAN_HWTSO> =20=20=20=20=20=20=20 capabilities=3D15399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO= 4,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,NETMAP> ether 68:05:ca:XX:YY:ZZ inet 192.168.1.202 netmask 0xffffff00 broadcast 192.168.1.255=20 inet 192.168.1.203 netmask 0xffffffff broadcast 192.168.1.203=20 nd6 options=3D23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP --------- --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213606-2472-KvITyenCUy>