[rbak-nsp] SE100 and etherchannel ?

[Sridhar]

The config below will work on SE100 if the etherchannel (link-group)
type is ether/dot1q.

SE100 does not support access link-group (say, for terminating PPPoE
subscribers) since the constituent ports have to be on different slots
(and there is only one slot on SE100).

thanks
sridhar

On Mon, Mar 9, 2009 at 12:25 PM, David Freedman
<david.freedman at uk.clara.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> No idea about the SE100 but here is roughly how to do it for SE400/800
>
> !
> link-group mylag ether
>  lacp [ active | passive ]
>  lacp priority [ 1-65535 ]
>  bind interface some_int local
> !
> port eth 1/1
>  link-group mylag
> !
> port eth1/2
>  link-group mylag
> !
>
> For dot1q trunks, use "dot1q" instead of ether
>
>
>
> Dave.
>
>  Marcin Kuczera wrote:
>> hello,
>>
>> is it possible to bind 2 ethernet ports in SE100 just like "aggregate
>> ethernet" in Juniper ?
>>
>> Regards,
>> Marcin
>> _______________________________________________
>> redback-nsp mailing list
>> redback-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/redback-nsp
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkm1bRkACgkQtFWeqpgEZrIOvQCgosrYhPB6dQYX3Kk2YMeTrvXA
> Cf4Anj1yycGFOocPMMGFYcbeSH8ju3DT
> =2dyV
> -----END PGP SIGNATURE-----
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>