[rbak-nsp] link-group access on SE-100
Marcin Kuczera
marcin at leon.pl
Sat Aug 16 11:12:17 EDT 2014
On 2014-08-15 18:58, Tudor Capatina wrote:
> Hello Marcin,
>
> The reason why it made sense to me is the need for more bandwidth for
> the subscriber circuits. So the only solution would be to look at an
> upgrade of the platform? Or in my specific case i guess i could split
> the 200 vlan's on two ports - 100 each, it should get me more
> bandwidth - and not use link-group?
Just distribute vlans to other ports.
>
> Would it make any difference if i would have the constituent ports of
> the link-group on different MIC cards in the SE-100?
No, this will not help.
Marcin
>
> Thanks!
>
> Best regards,
> Tudor Capatina
> Xenosite BV
> ------------------------------------------------------------------------
> *From:* redback-nsp [redback-nsp-bounces at puck.nether.net] on behalf of
> Marcin Kuczera [marcin at leon.pl]
> *Sent:* 15 August 2014 19:25
> *To:* redback-nsp at puck.nether.net
> *Subject:* Re: [rbak-nsp] link-group access on SE-100
>
> On 2014-08-15 16:09, Tudor Capatina wrote:
>> Hi folks,
>
> In my opinion - access mode on SE100 makes no sense...
> SmartEdge in this mode sends traffic only via signle link.
> It makes sense when you have 2 linecards and link-group spans between
> linecards.
> Than, in case of linecard crash traffic continues to flow.
>
> Other modes - dot1q - will do load sharing, but you can't have
> subscriber circuits on them (pppoe, clips).
>
> Marcin
>
>
>>
>> I configured an access link-group between a SE-100 and a Brocade MLX.
>> The problem i face is that traffic from the Brocade towards the
>> Redback is being split among the links but the other way around, the
>> Redback sends traffic using just one link. I have set the link-group
>> both with LACP and static but the result was the same.
>> I have tried both round-robin / interface-based, created the
>> link-group both as access and access-economical, had the link-group
>> both static and lacp - same result was reached.
>> I was wondering if this is a limitation of the SE-100 unit or i am
>> missing something?
>>
>> Brocade config and some outputs:
>> lag "se100" dynamic id 1
>> ports ethernet 1/1 to 1/2
>> primary-port 1/1
>> deploy
>> port-name "rd1-se100-lag" ethernet 1/1
>> port-name "rd1-se100-lag" ethernet 1/2
>>
>> #sh int e 1/1 | i rate
>> 30 second input rate: 111758468 bits/sec, 19734 packets/sec, 11.49%
>> utilization
>> 30 second output rate: 64714241 bits/sec, 11604 packets/sec, 6.65%
>> utilization
>> #sh int e 1/2 | i rate
>> 30 second input rate: 34 bits/sec, 0 packets/sec, 0.00% utilization
>> << not used
>> 30 second output rate: 33963516 bits/sec, 10184 packets/sec, 3.56%
>> utilization
>>
>> Redback config and some outputs:
>>
>> link-group rd2-lag access
>> encapsulation dot1q
>> dot1q pvc on-demand 1000 through 1199 aaa
>> idle-down 600
>> maximum-links 2
>> lacp active
>> protect-group incoming-port
>>
>> #sh link-group rd2-lag det
>>
>> Link-Group: rd2-lag, ID : 27, State : Up
>> ------------------------------------------------------------------------------
>> Ccct count : 2 Grouping : LoadShare
>> Card Type : carrier Type : access
>> Bindings : Unbound Minimum-links : 1
>> Maximum-links : 2
>> Prot-Group-Type : round-robin
>> Internal Handle : 255/22:1:28/1/1/4610
>> Description :
>> Constituent Circuits:
>> 1. 2/15 (Up )| 0.13%
>> 2. 2/16 (Up )| 0.00%
>>
>> #sh la act
>> Port Port Oper Recv Seln
>> Lg-id Port State Priority key State State
>> ----------------------------------------------------------------------
>> 27 2/15 0x3f 32767 27 exchg active
>> 27 2/16 0x3f 32767 27 exchg active
>>
>> Just as a note, non-access link-groups btw the Brocade MLX and the
>> Redback unit work fine.
>>
>> Best regards,
>> Tudor Capatina
>>
>>
>> _______________________________________________
>> redback-nsp mailing list
>> redback-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/redback-nsp
>
>
> --
>
> Marcin Kuczera / Specjalista d/s telekomunikacji, Wiceprezes Zarządu
> +48 32 440 80 71/ marcin.kuczera at leon.pl <mailto:marcin.kuczera at leon.pl>
>
> Leon Sp. z o.o.
> ul. Kilińskiego 33d, 44-200 Rybnik
> http://www.leon.pl/
>
> INTERNET | TELEWIZJA | TELEFON
>
> Facebook <https://www.facebook.com/LeonInternet?ref=hl>
>
> KRS 0000223101 Sąd Rejonowy w Gliwicach
> Kapitał zakładowy 200.000 zł
> NIP: 6332068698
>
--
Marcin Kuczera / Specjalista d/s telekomunikacji, Wiceprezes Zarządu
+48 32 440 80 71/ marcin.kuczera at leon.pl <mailto:marcin.kuczera at leon.pl>
Leon Sp. z o.o.
ul. Kilińskiego 33d, 44-200 Rybnik
http://www.leon.pl/
INTERNET | TELEWIZJA | TELEFON
Facebook <https://www.facebook.com/LeonInternet?ref=hl>
KRS 0000223101 Sąd Rejonowy w Gliwicach
Kapitał zakładowy 200.000 zł
NIP: 6332068698
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20140816/8961c1e5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 554 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20140816/8961c1e5/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: facebook.png
Type: image/png
Size: 554 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20140816/8961c1e5/attachment-0003.png>
More information about the redback-nsp
mailing list