<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2"> </HEAD> <BODY> Did you configure LACP on your aggr0 or the switch? That's the only way I've been able to get aggregate links to work. <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- Scott LeFevre 317-696-1010 </TD> </TR> </TABLE> On Wed, 2014-09-03 at 13:05 +0200, David Seira wrote: <BLOCKQUOTE TYPE=CITE> I'm testing the OmniOS for our storage system. I have a server with two 10G intel network card using the driver ixgbe. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> I've done the following steps: </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> - Create an aggregation interface: </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> dladm create-aggr -d ixgbe0 -d ixgbe1 aggr0 </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> ipadm create-if aggr0 </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> ipadm create-addr -T static -a <A HREF="http://1.2.3.4/24">1.2.3.4/24</A> aggr0/v4 </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> - Add a flow-control for the aggregation interface: </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> flowadm add-flow -l aggr0 -a local_ip=1.2.3.4 flow_aggr0 </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> After this, if I shutdown one of the interfaces in the switch I loose the connectivity with the server. It seems that the aggregation doesn't forward the traffic to the other interface. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Having one of the ports in the switch down, and without connectivity with the server because of the above issue; If I remove the flow (through the console, of course), the server goes online immediately. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> If I add the flow again, the server is innacessible again. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> It seems an incompatibility with the aggreation interfaces and the flow control. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> I've tested this bug with the r151006 and r151010 releases with the same result. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> The hardware where I've tested is: </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> - Dell PowerEdge R720 with an Intel X520 dual port 10G/SFP </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> - Dell PowerEdge C6220 with 10G mezzanine dual port </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Does anyone know what can be the problem? Has anyone experienced a similar issue? </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> Best regards. </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> -- </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> <IMG SRC="http://www.stackscale.es/stackscale-firma.png" ALIGN="bottom" BORDER="0"> </BLOCKQUOTE> <BLOCKQUOTE TYPE=CITE> <PRE> _______________________________________________ OmniOS-discuss mailing list <A HREF="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</A> <A HREF="http://lists.omniti.com/mailman/listinfo/omnios-discuss">http://lists.omniti.com/mailman/listinfo/omnios-discuss</A> </PRE> </BLOCKQUOTE> </BODY> </HTML>