[alcatel-nsp] LACP+load balance

venkat venkat2313 at gmail.com
Thu Nov 21 07:59:22 EST 2013


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>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> 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 balanced  across both lag ports.what could be
>> solution?
>>
>>
>>  # show lag 1 detail
>>
>>
>>
>>
>> ===============================================================================
>>
>> LAG Details
>>
>>
>> ===============================================================================
>>
>> Description        ::X0000
>>
>>
>> -------------------------------------------------------------------------------
>>
>> Details
>>
>>
>> -------------------------------------------------------------------------------
>>
>> Lag-id              : 1                     Mode                 : network
>>
>> Adm                 : up                    Opr                  : up
>>
>> Thres. Exceeded Cnt : 6                     Port Threshold       : 0
>>
>> Thres. Last Cleared : 08/13/2013 03:10:55   Threshold Action     : down
>>
>> Dynamic Cost        : false                 Encap Type           : null
>>
>> Configured Address  : 00:16:4d:88:3c:9d     Lag-IfIndex          :
>> 1342177281
>>
>> Hardware Address    : 00:16:4d:88:3c:9d
>>
>> Hold-time Down      : 0.0 sec               Port Type            :
>> standard
>>
>> Per FP Ing Queuing  : disabled
>>
>> LACP                : disabled
>>
>> Standby Signaling   : lacp
>>
>>
>>
>>
>> -------------------------------------------------------------------------------
>>
>> Port-id        Adm     Act/Stdby Opr     Primary   Sub-group     Forced
>> Prio
>>
>>
>> -------------------------------------------------------------------------------
>>
>> 1/1/1          up      active    up      yes       1             -
>> 32768
>>
>> 1/1/3          up      active    up                1             -
>> 32768
>>
>>
>>  # show port 1/1/1 and 1/1/3  detail
>>
>>
>>
>>
>> ===============================================================================
>>
>> Ethernet Interface
>>
>>
>> ===============================================================================
>>
>> Description        : :1G:X0000
>>
>> Interface          : 1/1/1                      Oper Speed       : 1 Gbps
>>
>> Link-level         : Ethernet                   Config Speed     : 1 Gbps
>>
>> Admin State        : up                         Oper Duplex      : full
>>
>> Oper State         : up - Active in LAG 1       Config Duplex    : full
>>
>> Physical Link      : Yes                        MTU              : 9212
>>
>> Single Fiber Mode  : No                         Min Frame Length : 64
>> Bytes
>>
>> IfIndex            : 35684352                   Hold time up     : 5
>> seconds
>>
>> Last State Change  : 08/13/2013 03:10:55        Hold time down   : 0
>> seconds
>>
>> Last Cleared Time  : 06/11/2013 03:59:47        DDM Events       : Enabled
>>
>> Phys State Chng Cnt: 5
>>
>>
>>
>> Configured Mode    : network                    Encap Type       : null
>>
>> Dot1Q Ethertype    : 0x8100                     QinQ Ethertype   : 0x8100
>>
>> PBB Ethertype      : 0x88e7
>>
>> Ing. Pool % Rate   : 100                        Egr. Pool % Rate : 100
>>
>> Ing. Pool Policy   : n/a
>>
>> Egr. Pool Policy   : n/a
>>
>> Net. Egr. Queue Pol: Red-Metro-1/10-Gbps
>>
>> Egr. Sched. Pol    : n/a
>>
>> Auto-negotiate     : false                      MDI/MDX          : unknown
>>
>> Accounting Policy  : None                       Collect-stats    :
>> Disabled
>>
>> Acct Plcy Eth Phys : None                       Collect Eth Phys :
>> Disabled
>>
>> Egress Rate        : Default                    Ingress Rate     : Default
>>
>> Load-balance-algo  : Default                    LACP Tunnel      :
>> Disabled
>>
>>
>>
>>   the network load isn´t balanced  across both ports.
>>
>>
>> -------------------------------------------------------------------------------
>>
>> At time t = 20 sec (Mode: Rate)
>>
>>
>> -------------------------------------------------------------------------------
>>
>> 1/1/1     104559807   129110      781841      2289        0          0
>>
>>   % Util  85.71       --          0.66        --          --         --
>>
>> 1/1/3     617208      852         20302995    67692       0          0
>>
>>   % Util  0.50        --          17.32       --          --         --
>>
>>
>> -------------------------------------------------------------------------------
>>
>> Totals    105177014   129962      21084836    69981       0          0
>>
>>   % Util  43.11       --          8.99        --          --         --
>>
>>
>> --
>> Thanks
>> Venkat
>>
>>
>>
>>  _______________________________________________
>> alcatel-nsp mailing listalcatel-nsp at puck.nether.nethttps://puck.nether.net/mailman/listinfo/alcatel-nsp
>>
>>
>>
>> _______________________________________________
>> alcatel-nsp mailing list
>> alcatel-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>>
>>
>
>
> --
> Thanks
> Venkat
> 848-565-8743
>
>
> _______________________________________________
> alcatel-nsp mailing listalcatel-nsp at puck.nether.nethttps://puck.nether.net/mailman/listinfo/alcatel-nsp
>
>
>
> _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp
>
>


-- 
Thanks
Venkat
848-565-8743
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20131121/99fa79d3/attachment-0001.html>


More information about the alcatel-nsp mailing list