Urgent matter: LACP trunk stops distributing
Mark Schouten
mark at tuxis.nl
Thu Apr 2 11:01:54 UTC 2015
Hi,
So I've changed the configuration last night, eliminating the possibility that the issue was LACP. All traffic was handled by the single igb interface. It didn't help, at all.
This morning the interface stopped working, without any form of messages and started working again after a few minutes. Then, some minutes later it stopped again, to resume after a few minutes.
So now I plugged the switch into an em-port and I tried to move the vlan interfaces to the em-interface. That worked, partially. The server kept the old mac-address in the arp-table. Even after I deleted the vlan interface.
I rebooted the box, and so far so good. But still, any help is appreciated.
Met vriendelijke groeten,
--
Kerio Operator in de Cloud? https://www.kerioindecloud.nl/
Mark Schouten | Tuxis Internet Engineering
KvK: 61527076 | http://www.tuxis.nl/
T: 0318 200208 | info at tuxis.nl
Van: Mark Schouten <mark at tuxis.nl>
Aan: <freebsd-net at freebsd.org>
Verzonden: 1-4-2015 12:07
Onderwerp: Urgent matter: LACP trunk stops distributing
Hi,
I've got an urgent matter on my hands, my FreeBSD iScsibox has dropped it's LACP trunk twice in the last 24 hours, which causes a whole lot of issues on my VPS cluster, using that storage.
It's a FreeBSD box with two igb-interfaces in an LACP trunk with jumboframes and vlans. If the connection drops, the only thing I see is:
Apr 1 10:37:18 zstore02 kernel: igb0: Interface stopped DISTRIBUTING, possible flapping
Apr 1 10:37:28 zstore02 kernel: igb1: Interface stopped DISTRIBUTING, possible flapping
The switch has nothing to say, so it doesn't seem that there are acual linkflaps. I have a feeling that it's this LACP trunk that goes haywire somewhere on the FreeBSD side. If anyone can help me with this, I'd be grateful. If someone (preferably EU-based) wants to help out professionally as a consultant, that would be fine too. Or if anyone knows someone in .nl that offers this level of expertise on consultingbase, let me know.
I'm running 10.1-RELEASE on the box, see the (AFAICS) relevant config below. The switch is a Brocade ICX6430.
[root at zstore02 ~]# ifconfig lagg0
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 0c:c4:7a:12:13:dc
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
laggproto lacp lagghash l2,l3,l4
laggport: em1 flags=0<>
laggport: em0 flags=0<>
laggport: igb1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
laggport: igb0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
[root at zstore02 ~]# sysctl -a | grep lacp
net.link.lagg.lacp.debug: 0
net.link.lagg.0.lacp.lacp_strict_mode: 1
net.link.lagg.0.lacp.debug.rx_test: 0
net.link.lagg.0.lacp.debug.tx_test: 0
Met vriendelijke groeten,
--
Kerio Operator in de Cloud? https://www.kerioindecloud.nl/
Mark Schouten | Tuxis Internet Engineering
KvK: 61527076 | http://www.tuxis.nl/
T: 0318 200208 | info at tuxis.nl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4549 bytes
Desc: Electronic Signature S/MIME
URL: <http://lists.freebsd.org/pipermail/freebsd-net/attachments/20150402/fb95316c/attachment.bin>
More information about the freebsd-net
mailing list