|
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 "port-channel load-balance src-dst-ip" option. Is
there something similar on the foundry? Here's the "show interface"
for the two members of the LAG: show interface ethernet 3/3 GigabitEthernet3/3 is up, line protocol is up Hardware is GigabitEthernet, address is 000c.dba5.e842 (bia 000c.dba5.e842) Configured speed auto, actual 1Gbit, configured duplex fdx, actual fdx Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING STP configured to ON, priority is level0, flow control enabled mirror disabled, monitor disabled Member of active trunk ports 3/3-3/4, primary port Member of configured trunk ports 3/3-3/4, primary port No port name MTU 9000 bytes 300 second input rate: 253106560 bits/sec, 144914 packets/sec, 27.62% utilization 300 second output rate: 509824184 bits/sec, 232136 packets/sec, 54.69% utilization 143595350 packets input, 30715638578 bytes, 0 no buffer Received 1869 broadcasts, 2135 multicasts, 143591346 unicasts 0 input errors, 0 CRC, 0 frame, 0 ignored 0 runts, 0 giants, DMA received 143595234 packets 228617165 packets output, 63786592895 bytes, 0 underruns Transmitted 1974 broadcasts, 3854 multicasts, 228611337 unicasts 0 output errors, 0 collisions, DMA transmitted 228617164 packets show interface ethernet 3/4 GigabitEthernet3/4 is up, line protocol is up Hardware is GigabitEthernet, address is 000c.dba5.e842 (bia 000c.dba5.e842) Configured speed auto, actual 1Gbit, configured duplex fdx, actual fdx Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING STP configured to ON, priority is level0, flow control enabled mirror disabled, monitor disabled Member of active trunk ports 3/3-3/4, secondary port, primary port is 3/3 Member of configured trunk ports 3/3-3/4, secondary port, primary port is 3/3 No port name MTU 1518 bytes 300 second input rate: 281677768 bits/sec, 158529 packets/sec, 30.70% utilization 300 second output rate: 1224 bits/sec, 1 packets/sec, 0.00% utilization 155802286 packets input, 33799467638 bytes, 0 no buffer Received 11 broadcasts, 1085 multicasts, 155801190 unicasts 0 input errors, 0 CRC, 0 frame, 0 ignored 0 runts, 0 giants, DMA received 155802169 packets 1163 packets output, 121019 bytes, 0 underruns Transmitted 0 broadcasts, 39 multicasts, 1124 unicasts 0 output errors, 0 collisions, DMA transmitted 1163 packets You can see that 3/3 has 54.69% output utilization, while 3/4 has 0%. Thanks. On 06/04/2012 08:19 PM, Mike Allen wrote: 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. |
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
