[f-nsp] MLX-CER LAG issues (1 port LACP-BLOCKED)?
Fredy Kuenzler
kuenzler at init7.net
Fri Apr 5 07:59:31 EDT 2013
Am 05.04.2013 12:29, schrieb Nick Hilliard:
> On 05/04/2013 10:41, Fredy Kuenzler wrote:
>> Am 05.04.2013 05:53, schrieb Tony Clark:
>>> I've deployed a 2 x 1GE LAG between a CER ('cor2' - running 5.4c) and
>>> MLX ('cor3' - running 5.4b), using identical config. When I bring up
>>> the lag, the secondary port goes into LACP-BLOCKED state and I end up
>>> with no LAG. I feel like I must be missing something here - this
>>> works for me between 2 MLX's, but there seems to be a subtle
>>> difference between the MLX and CER on this issue.
>>
>> I'm not sure but I believe to remember that CER2000 doesn't support LAG
>> on the two 10gig interfaces.
>
> oops! the OP was talking about 1G interfaces, not 10G.
Indeed. Those which can read do have a real advantage...
Sorry for the noise.
--
Fredy Künzler
Init7 (Switzerland) AG
AS13030
St. Georgen-Strasse 70
CH-8400 Winterthur
Skype: flyingpotato
Phone: +41 44 315 4400
Fax: +41 44 315 4401
Twitter: @init7
http://www.init7.net/
More information about the foundry-nsp
mailing list