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@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@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 | i...@tuxis.nl
smime.p7s
Description: Electronic Signature S/MIME
