<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Mike, thanks for your response. My source and destination IP
addresses are definitely different, but all outbound traffic is
going through the first interface. Are you sure that it uses source
and destination IP by default? Is there a setting for this that I
can set explicitly? I had the same problem on the cisco, until I
set the "<i>port-channel load-balance src-dst-ip" option. </i>Is
there something similar on the foundry? Here's the "show interface"
for the two members of the LAG:<br>
<br>
show interface ethernet 3/3<br>
GigabitEthernet3/3 is up, line protocol is up <br>
Hardware is GigabitEthernet, address is 000c.dba5.e842 (bia
000c.dba5.e842)<br>
Configured speed auto, actual 1Gbit, configured duplex fdx, actual
fdx<br>
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING<br>
STP configured to ON, priority is level0, flow control enabled<br>
mirror disabled, monitor disabled<br>
Member of active trunk ports 3/3-3/4, primary port<br>
Member of configured trunk ports 3/3-3/4, primary port<br>
No port name<br>
MTU 9000 bytes<br>
300 second input rate: 253106560 bits/sec, 144914 packets/sec,
27.62% utilization<br>
300 second output rate: 509824184 bits/sec, 232136 packets/sec,
54.69% utilization<br>
143595350 packets input, 30715638578 bytes, 0 no buffer<br>
Received 1869 broadcasts, 2135 multicasts, 143591346 unicasts<br>
0 input errors, 0 CRC, 0 frame, 0 ignored<br>
0 runts, 0 giants, DMA received 143595234 packets<br>
228617165 packets output, 63786592895 bytes, 0 underruns<br>
Transmitted 1974 broadcasts, 3854 multicasts, 228611337 unicasts<br>
0 output errors, 0 collisions, DMA transmitted 228617164 packets<br>
<br>
show interface ethernet 3/4 <br>
GigabitEthernet3/4 is up, line protocol is up <br>
Hardware is GigabitEthernet, address is 000c.dba5.e842 (bia
000c.dba5.e842)<br>
Configured speed auto, actual 1Gbit, configured duplex fdx, actual
fdx<br>
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING<br>
STP configured to ON, priority is level0, flow control enabled<br>
mirror disabled, monitor disabled<br>
Member of active trunk ports 3/3-3/4, secondary port, primary port
is 3/3<br>
Member of configured trunk ports 3/3-3/4, secondary port, primary
port is 3/3<br>
No port name<br>
MTU 1518 bytes<br>
300 second input rate: 281677768 bits/sec, 158529 packets/sec,
30.70% utilization<br>
300 second output rate: 1224 bits/sec, 1 packets/sec, 0.00%
utilization<br>
155802286 packets input, 33799467638 bytes, 0 no buffer<br>
Received 11 broadcasts, 1085 multicasts, 155801190 unicasts<br>
0 input errors, 0 CRC, 0 frame, 0 ignored<br>
0 runts, 0 giants, DMA received 155802169 packets<br>
1163 packets output, 121019 bytes, 0 underruns<br>
Transmitted 0 broadcasts, 39 multicasts, 1124 unicasts<br>
0 output errors, 0 collisions, DMA transmitted 1163 packets<br>
<br>
You can see that 3/3 has 54.69% output utilization, while 3/4 has
0%.<br>
<br>
Thanks.<br>
<br>
On 06/04/2012 08:19 PM, Mike Allen wrote:
<blockquote
cite="mid:CAAqdaXKQdYLLUHESeAuttdRYwcG9_mk=LrKVhaVeLCMzrCi_cQ@mail.gmail.com"
type="cite">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 moz-do-not-send="true"
href="mailto:ed@entetel.com" target="_blank">ed@entetel.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<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 moz-do-not-send="true" href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a>
<a moz-do-not-send="true" 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 moz-do-not-send="true"
href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a moz-do-not-send="true"
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>
</blockquote>
<br>
</body>
</html>