Hi all,
thank you for the all the feedback, but unfortunately the problem is
still present.
To test LAG, we generate traffic with a packet generator, with 5
different flows (one of 1Gbps and four of 100Mbps, each using different
IP and subnetworks).
We added the per-packet load balancing, but nothing changes.
We have not been able to configure "forwarding-options hash", since it
is not supported on EX3200 (at least with our Junos 10.4R4.7)
Just in case it may help, this is the show of lacp for ae0 on one side
(the other side seems exactly the same)
Aggregated interface: ae0
LACP state:RoleExpDefDistColSynAggrTimeoutActivity
ge-0/0/12ActorNoNoYesYesYesYesFastActive
ge-0/0/12PartnerNoNoYesYesYesYesFastActive
ge-0/0/14ActorNoNoYesYesYesYesFastActive
ge-0/0/14PartnerNoNoYesYesYesYesFastActive
ge-0/0/16ActorNoNoYesYesYesYesFastActive
ge-0/0/16PartnerNoNoYesYesYesYesFastActive
LACP protocol:Receive StateTransmit StateMux State
ge-0/0/12CurrentFast periodic Collecting distributing
ge-0/0/14CurrentFast periodic Collecting distributing
ge-0/0/16CurrentFast periodic Collecting distributing
Thank you for any additional suggestion..
Best,
Filippo
Il 07/03/2013 19.47, Dave Humphrey ha scritto:
This is the key. The LAG will balance using flows, so one flow will only
cross one link. If you add extra flows to your traffic using different
source/destination IP addresses your traffic will balance out.
On 06/03/2013 17:42, "Sreepad Raj P S" <pss...@juniper.net> wrote:
How many flows are you sending?
sreepad | jncip-sp
cube 4.3.1.2.3 | xtn 10689
eabu-aa | juniper
exora | bangalore
"yearn > learn > earn"
-----Original Message-----
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Filippo Cugini
Sent: Wednesday, March 06, 2013 7:46 PM
To: juniper-nsp@puck.nether.net
Cc: andrea.sgambell...@libero.it
Subject: [j-nsp] Problems with Link Aggregation
Hi,
we configured the link-aggregation on two switches EX3200 with JUNOS
software 10.0R4.7.
We configured the aggregated interface (ae0), containing three ge
interfaces (ge-0/0/12, ge-0/0/14, ge-0/0/16).
At the operational level, the state of the aggregated interface (show
interfaces ae0 extensive) shows that the link is up at 3000mbps.
However, when we send traffic on the aggregated link, just one ge works,
and we experience packet loss when we exceed the throughput of 1000mbps.
Indeed, the statistics of all interfaces show that only the ge-0/0/12 is
utilized to forward the data traffic, while the other two interfaces send
and receive only signaling packets.
Any suggestions?
This is our one-side configuration:
chassis {
aggregated-devices {
ethernet {
device-count 1;
}
}
}
interfaces {
ge-0/0/12 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/14 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/16 {
ether-options {
802.3ad ae0;
}
}
...
ae0 {
aggregated-ether-options {
minimum-links 2;
lacp {
active;
}
}
unit 0 {
family inet {
address 10.255.255.2/30;
}
}
}
}
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
