[j-nsp] Class of Service implementation over MLPPP link

[Eric Van Tol]

I assume that you are classifying traffic by using filters on each of
the T1s.  Can you post those filters?  They are also not applied to the
LSQ interface in the original post.  If you don't have the filter
applied to the LSQ logical interface, your traffic will not get
classified and therefore all will be in the BE queue.

-evt


-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of FAHAD ALI KHAN
Sent: Tuesday, April 17, 2007 2:19 AM
To: Dan Rautio
Cc: juniper-nsp
Subject: Re: [j-nsp] Class of Service implementation over MLPPP link

Dan

This is not working, even with enabling per-unit schedular on
constituent
link and applying schedular-map to their logical unit in Class of
Service
Interface hierarchy as u suggest.

Results are same, while pushing Gold, Silver or BE traffic, i.e. all
goes to
queue 0 (BE). And in lsq interface, there is no Queue stats available
(all
Queue stats are 0).

show interfaces e1-0/0/0 extensive
Physical interface: e1-0/0/0, Enabled, Physical link is Up
  Traffic statistics:
   Input  bytes  :                21834                    0 bps
   Output bytes  :                23757                    0 bps
   Input  packets:                  305                    0 pps
   Output packets:                  332                    0 pps
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed
discards: 0, L3 incompletes: 0, L2 channel errors: 0,
    L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0,
Resource
errors: 0
  Output errors:
    Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU
errors: 0, Resource errors: 0
  Queue counters:       Queued packets  Transmitted packets      Dropped
packets
    0 Besteffort                   313
313                    0
    1 Silver                         0
0                    0
    2 Gold                           0
0                    0
    3 NC                            19
19                    0

show interfaces e1-0/0/4 extensive
Physical interface: e1-0/0/4, Enabled, Physical link is Up
    Input  bytes  :                22186                    0 bps
   Output bytes  :                23072                    0 bps
   Input  packets:                  300                    0 pps
   Output packets:                  323                    0 pps
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed
discards: 0, L3 incompletes: 0, L2 channel errors: 0,
    L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0,
Resource
errors: 0
  Output errors:
    Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU
errors: 0, Resource errors: 0
  Queue counters:       Queued packets  Transmitted packets      Dropped
packets
    0 Besteffort                   304
304                    0
    1 Silver                         0
0                    0
    2 Gold                           0
0                    0
    3 NC                            19
19                    0

show interfaces lsq-0/2/0 extensive
Physical interface: lsq-0/2/0, Enabled, Physical link is Up
  Interface index: 194, SNMP ifIndex: 260, Generation: 193
  Link-level type: LinkService, MTU: 1504
  Device flags   : Present Running
  Interface flags: Point-To-Point SNMP-Traps 16384
  Last flapped   : 2007-03-27 13:10:39 PKT (2w6d 21:56 ago)
  Statistics last cleared: 2007-04-17 11:04:24 PKT (00:02:34 ago)
  Traffic statistics:
   Input  bytes  :                54709                26760 bps
   Output bytes  :                58396                28144 bps
   Input  packets:                  704                   44 pps
   Output packets:                  782                   46 pps
  Frame exceptions:
    Oversized frames                  0
    Errored input frames              0
    Input on disabled link/bundle     0
    Output for disabled link/bundle   0
    Queuing drops                     0
  Buffering exceptions:
    Packet data buffer overflow       0
    Fragment data buffer overflow     0
  Assembly exceptions:
    Fragment timeout                  0
    Missing sequence number           0
    Out-of-order sequence number      0
    Out-of-range sequence number      0
  Hardware errors (sticky):
    Data memory error                 0
    Control memory error              0
  Queue counters:       Queued packets  Transmitted packets      Dropped
packets
    0 Besteffort                     0
0                    0
    1 Silver                         0
0                    0
    2 Gold                           0
0                    0
    3 NC                             0
0                    0

Well is it necessary to implement the fragmentation map, multiclass or
LFI
settings. as we are not implementing these.

Does any one has the practical implmentation experience to implement CoS
over MLPPP, if yes than please share your sample configuration and
comments
on this issue.

Thanks and Regards

Fahad Ali Khan




On 4/16/07, Dan Rautio <drautio at juniper.net> wrote:
>
> Fahad,
>
> Did you ever get an answer to your question?  Check this out:
>
>
http://www.juniper.net/techpubs/software/junos/junos82/swconfig82-servic
> es/html/lsq-config20.html
>
>
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp