[f-nsp] Link Aggregation on ICX 6450

[Drew Weaver]

Ah, I just noticed that it configured one port as primary and one port as secondary and it appears to be using only one of them.

GigabitEthernet1/1/40 is up, line protocol is up
  ...
  Member of active trunk ports 1/1/40,1/1/41, primary port
  Member of configured trunk ports 1/1/40,1/1/41, primary port
...
  300 second input rate: 656826344 bits/sec, 53948 packets/sec, 66.53% utilization

GigabitEthernet1/1/41 is up, line protocol is up
...
  Member of active trunk ports 1/1/40,1/1/41, secondary port, primary port is 1/1/40
  Member of configured trunk ports 1/1/40,1/1/41, secondary port, primary port is 1/1/40
...
  300 second input rate: 472488 bits/sec, 60 packets/sec, 0.04% utilization
  300 second output rate: 15945648 bits/sec, 26630 packets/sec, 2.01% utilization

Currently I am running iperf from 1 virtual machine inside of the server connected to 1/1/40 & 1/1/41 to multiple VMs which reside on systems connected to multiple different ports.

I would expect that in this case that I could get 2x near 1G streams.

This is the host side's configuration:

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 2
        Actor Key: 17
        Partner Key: 10000
        Partner Mac Address: 74:8e:f8:b6:98:60

Slave Interface: eth4
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: d4:ae:52:a6:51:0e
Aggregator ID: 1

Slave Interface: eth5
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: d4:ae:52:a6:51:0f
Aggregator ID: 1

Thanks,
-Drew

-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Niels Bakker
Sent: Monday, March 25, 2013 11:05 AM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Link Aggregation on ICX 6450

* drew.weaver at thenap.com (Drew Weaver) [Mon 25 Mar 2013, 16:01 CET]:
>I setup a 2 port link-aggregation between an ICX 6450 and a Dell 
>PowerEdge R620 running Linux.
>I configured both sides to use lacp.
>Is there something I need to do to get load balancing? It seems like by 
>default it is using port 1/1/40 for incoming traffic and port
>1/1/41 for outbound traffic.
>I would like there to be load sharing on the ports. Is this something 
>configurable on the ICX, on the server, or perhaps both?

What type of traffic are you sending?  It needs to have enough entropy (src/st MAC, IP address, TCP/UDP port) to balance across individual links, as implementations should try to keep conversations on the same link.  So you'll need to test with more than just one FTP stream.


	-- Niels.

--
_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp