Edward, seems like there is confusion about trunking lately on the list...:) So as mentioned in my previous post to the list, there are two different trunking options in the FastIron code base. You are already configured for 802.3ad Link Aggregation dynamically, and your trunk is up and operational. You do not need the static trunking, and that is why you see that error.<div>
<br></div><div><font class="Apple-style-span" face="arial, helvetica, sans-serif">As for the hash diversity, it all depends on what your flows look like. By default for ip traffic, it uses Source and destination IP addresses, and source and destination TCP/UDP ports for the hash, so as long as those are different, you should see outbound traffic spread accordingly. Note that unknown unicast, broadcast, and multicast traffic will all usually take on the first port. Unicast traffic is what would be load balanced.</font></div>
<div><font class="Apple-style-span" face="arial, helvetica, sans-serif"><br></font></div><div><font class="Apple-style-span" face="arial, helvetica, sans-serif">Mike</font></div><div><br><div class="gmail_quote">On Mon, Jun 4, 2012 at 6:11 PM, Edward Rosinzonsky <span dir="ltr"><<a href="mailto:ed@entetel.com" target="_blank">ed@entetel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff" text="#000000">
Shameless bump.<br>
When I try to trunk the lacp ports, I get an error:<br>
<br>
trunk ethernet 3/3 to 3/4<br>
error - trunk ports contain LACP-enabled ports.<br>
<br>
<br>
<br>
Here's the relevant part of the config:<br>
<br>
interface ethernet 3/3<br>
mtu 9000<br>
link-aggregate configure key 10000<br>
link-aggregate active<br>
!<br>
interface ethernet 3/4<br>
link-aggregate configure key 10000<br>
link-aggregate active<br>
!<br>
<br>
<br>
<br>
<br>
show link-ag:<br>
System ID: 000c.dba5.e840<br>
Long timeout: 90, default: 90<br>
Short timeout: 3, default: 3<br>
Port [Sys P] [Port P] [ Key ]
[Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]<br>
3/3 1 1 10000 Yes L Agg Syn Col Dis No
No Ope<br>
3/4 1 1 10000 Yes L Agg Syn Col Dis No
No Ope<br>
<br>
<br>
<br>
<br>
<br>
show trunk:<br>
Configured trunks:<br>
<br>
Trunk ID: 66<br>
Type: Switch<br>
Ports_Configured: 2<br>
Primary Port Monitored: Jointly<br>
<br>
Ports 3/3 3/4 <br>
Port Names none none <br>
Port_Status enable enable <br>
Monitor off off <br>
Mirror Port N/A N/A <br>
Monitor Dir N/A N/A <br>
<br>
Operational trunks:<br>
<br>
Trunk ID: 66<br>
Type: Switch<br>
Duplex: Full<br>
Speed: 1G<br>
Tag: No<br>
Priority: level0<br>
Active Ports: 2 <br>
<br>
<br>
Ports 3/3 3/4 <br>
Link_Status active active <br>
LACP_Status ready ready <br>
Load Sharing<br>
Mac Address 6 5 <br>
IP 0 0 <br>
IPX 0 0 <br>
Apple Talk 0 0 <br>
Multicast 0 0 <br><div><div class="h5">
<br>
<br>
<br>
On 04/12/2012 07:16 PM, Edward Rosinzonsky wrote:
</div></div><blockquote type="cite"><div><div class="h5">
Hi,<br>
<br>
I'm trying to setup LAG between my si350 and the cisco switch. I
set up the LAG without problems, but all traffic just defaults to
the first port in the LAG. <br>
<br>
On the cisco, I solve this problem with the following command:<br>
<i>port-channel load-balance src-dst-ip</i><br>
<br>
But, I can't find anything similar for the foundry. Anyone know
how to do this?<br>
<br>
Thanks.<br>
</div></div><pre><fieldset></fieldset>
_______________________________________________
foundry-nsp mailing list
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br></blockquote></div><br></div>