[alcatel-nsp] LACP+load balance

[Ruslan Pustovoitov]

Generally, you speak about H-VPLS case, not P-P case.
So, hash-label is not needed for you because If your traffic is IP then 
src/dst IP address hashing is performed.
But you tell us that traffic don't distributed over available links.
I can assume that you have one src/dst IP pair in your traffic.
In this case nothing could help you.
You must remember that hash-label (rfc 6931) or entropy label (rfc 6790, 
do not supported by ALU) or native hashing can help only when sufficient 
random data exist in the traffic.



21.11.2013 16:59, venkat пишет:
> thank you for responding ...I need to test it
>
> *we are using VPLS traffic over MPLS  and to enable entropy label
> *
> *below command is right?
> *
> *configure service vpls <svc-id> mesh-sdp <sdp-ip:vc-id> hash-label
>
>         vpls 600341 customer 266 create
>               spoke-sdp 1040:600341 create
>                 no shutdown
>             exit
>             mesh-sdp 4011:600341 create
>                 no shutdown
> *
>
>
> *enable entropy label below commands are sufficient or do we need to 
> any more commands
> *
> *configure service vpls ***600341* mesh-sdp ***1040:600341* **hash-label*
> *configure service vpls***600341* mesh-sdp ***4011:600341* **hash-label*
>
>
>
> On Thu, Nov 21, 2013 at 1:05 AM, Ruslan Pustovoitov 
> <rus-p at mostelekom.net <mailto:rus-p at mostelekom.net>> wrote:
>
>     Hi venkat,
>
>     lsr-loadbalancing lbl-ip aplicailable only for IPv4/IPv6 traffic,
>     not for epipe and vpls if you are speaking about P-P link.
>     Also, this feature depends on HW and SW. Not all sw versions
>     support it in mode "b" and on IOM 1&2 .
>     You have to check ALU doc carefully )
>     If you have epipe or vpls traffic on P-P link (ethernet header
>     after MPLS) then only solution to spray packets better is entropy
>     label.
>
>
>     20.11.2013 18:25, venkat пишет:
>>         system
>>             name "PEESVIG04"
>>             chassis-mode b
>>             l4-load-balancing
>>             lsr-load-balancing lbl-ip
>>
>>     We have tried it does not help..do you think any other issue
>>
>>
>>     On Wed, Nov 20, 2013 at 12:58 AM, Alexander Saveliev
>>     <saveliev at mostelekom.net <mailto:saveliev at mostelekom.net>> wrote:
>>
>>         Hello!
>>
>>         Hashing on LAG depends on types of traffic that flow through it.
>>         For example, if your LAG is a P-P MPLS link and if most of
>>         your traffic belongs only to single L3VPN, than by default
>>         this traffic will flow through single link of LAG. ALU
>>         allocates one MPLS label per L3VPN. ALU makes hashing based
>>         on MPLS stack by default.
>>         ALU has several options to improve situation. You can use
>>         Entropy Label for example, or you can change the hashing
>>         procedure to use L3 headers
>>         ("config>system>lsr-load-balancing" command) etc. Of course
>>         there is a dependancy on the software version that you have.
>>
>>         On 20.11.2013 08:59, venkat wrote:
>>>         .....
>>>
>>>         the network load isn´t balancedacross both ports.
>>>
>>>         -------------------------------------------------------------------------------
>>>
>>>         At time t = 20 sec (Mode: Rate)
>>>
>>>         -------------------------------------------------------------------------------
>>>
>>>         1/1/1104559807129110781841228900
>>>
>>>         % Util85.71--0.66------
>>>
>>>         1/1/3617208852203029956769200
>>>
>>>         % Util0.50--17.32------
>>>
>>>         -------------------------------------------------------------------------------
>>>
>>>         Totals105177014129962210848366998100
>>>
>>>         % Util43.11--8.99------
>>>
>>>
>>>
>>>         -- 
>>>         Thanks
>>>         Venkat
>>>
>>>
>>>
>>>         _
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20131122/61c34eee/attachment.html>