[alcatel-nsp] unbalanced traffic on GigEs in a LAG

Phil Bedard philxor at gmail.com
Mon Mar 8 18:47:39 EST 2010


I guess it's hard to know exactly which services are flowing across the link but if it's only acting as an LSR then it should be hashing based on the MPLS stack (Up to 5 labels), ingress port, and system ID.   Are there any potential really high BW services across the LAG?  With the IOM3/IMM you can have it hash on both the labels and the IPv4 header, but not on the IOM2.  

If there are services originating on the box there are all kinds of rules on how things are hashed on egress, but LSR it's pretty simple.  

Phil 


On Mar 8, 2010, at 6:37 PM, Scott Weeks wrote:

> 
> 
> --- Ryan.Landry at TELUS.COM wrote:
> also, what is 'tools dump lag lag-id <blah>' showing you for each port's bandwidth?
> --------------------------------------
> 
> That one's kinda long, but here it goes...  ;-)
> 
> 
> 
> *A:WLKU7750# tools dump lag lag-id 2
> 
> Port state      : Up
> Selected subgrp : 1
> NumActivePorts  : 2
> ThresholdRising : 12
> ThresholdFalling: 4
> IOM bitmask     : 6
> Config MTU      : 9212
> Oper. MTU       : 9212
> Bandwidth       : 2000000
> 
> multi-chassis   : NO
> 
> ------------------------------------------------------------------------------------
> Indx   PortId   RX pkts   TX pkts   State Active Port  Cfg Oper Speed       BW AP CS
>                                                 Pri   Mtu Mtu
> ------------------------------------------------------------------------------------
>   0    1/1/2 556699363199 311450362191      Up    yes 32768 9212 9212        1000000  0  2
>   1    2/1/2 304080315493 314231853533      Up    yes 32768 9212 9212        1000000  0  2
> 
> ------Port    1/1/2 LACP info------
> 
>    RX sm state......CURRENT
>    PT sm state......FAST_PERIODIC
>    MUX sm state.....COLLECTING_DISTRIBUTING
> 
>    begin............FALSE
>    NTT..............FALSE
>    lacpEnbld........TRUE
>    ready_N..........FALSE
>    selected.........SELECTED
>    portMoved........FALSE
>    portEnabled......TRUE
>    txTimestamp 0....3079994462
>    txTimestamp 1....3079994264
>    txTimestamp 2....3079994362
>    nextTxTimestamp..1
>    pLacpPdu.........0x0
>    subGrpId.........1
>    isCollDistr......TRUE
> 
>    currentWhileTimerExpired..FALSE
>    periodicTimerExpired......FALSE
> 
>    PrtrOprSysPri  : 32768
>    PrtrOprSysId   : 00:03:fa:c1:69:f8
>    PrtrOprkey     : 3331
> 
> ------Port    2/1/2 LACP info------
> 
>    RX sm state......CURRENT
>    PT sm state......FAST_PERIODIC
>    MUX sm state.....COLLECTING_DISTRIBUTING
> 
>    begin............FALSE
>    NTT..............FALSE
>    lacpEnbld........TRUE
>    ready_N..........FALSE
>    selected.........SELECTED
>    portMoved........FALSE
>    portEnabled......TRUE
>    txTimestamp 0....3079994462
>    txTimestamp 1....3079994562
>    txTimestamp 2....3079994662
>    nextTxTimestamp..0
>    pLacpPdu.........0x0
>    subGrpId.........1
>    isCollDistr......TRUE
> 
>    currentWhileTimerExpired..FALSE
>    periodicTimerExpired......FALSE
> 
>    PrtrOprSysPri  : 32768
>    PrtrOprSysId   : 00:03:fa:c1:69:f8
>    PrtrOprkey     : 3331
> 
> 
> 
> _______________________________________________
> alcatel-nsp mailing list
> alcatel-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/alcatel-nsp




More information about the alcatel-nsp mailing list