[j-nsp] Class of Service implementation over MLPPP link
Josef Buchsteiner
josefb at juniper.net
Tue Apr 17 17:59:08 EDT 2007
Fahad,
the behavior you see is normal and expected.
First to see the queue statistic on LSQ interface you most
likely forgot to add the subunit number as the interface
queue number will be zero all the time since this is the
entire LSQ interfaces. That's the reason why you configure
per-unit-scheduler on the LSQ interface.
On the egress interface we have to put all into Q0 since you
are not using multiclass mlppp and we have only one SEQ pool
so we will end up all in one queue to prevent re-order. The
queuing is done in LSQ prior to putting on the seq stamps.
We do recommend once there is LFI traffic to configure
scheduler on the egress PIC to make sure it gets the right
priority and served prior to the ML packets and the
interleaving is done there. So with LFI traffic and the
fragmentation-map it would then go into a different egress PIC
queue. If you use ML-MLPPP you will then see all going in
different egress queues.
However the point is that queuing is done on LSQ. So your
configuration is ok and most likely all is working correctly.
Just check if you get the LSQ queue number
<-- example like this, please check on your side
josefb at minsk# run show interfaces queue lsq-1/2/0.0
Logical interface lsq-1/2/0.0 (Index 76) (SNMP ifIndex 65)
Forwarding classes: 4 supported, 4 in use
Egress queues: 4 supported, 4 in use
Burst size: 0
Queue: 0, Forwarding classes: best-effort
Queued:
Packets : 113479 166 pps
Bytes : 170143632 1992000 bps
Transmitted:
Packets : 107498 166 pps
Bytes : 161185344 1992000 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 5981 0 pps
Low, non-TCP : 5981 0 pps
Low, TCP : 0 0 pps
High, non-TCP : 0 0 pps
High, TCP : 0 0 pps
RED-dropped bytes : 8958288 0 bps
Low, non-TCP : 8958288 0 bps
Low, TCP : 0 0 bps
High, non-TCP : 0 0 bps
High, TCP : 0 0 bps
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 84666 170 pps
Bytes : 126999000 2040000 bps
Transmitted:
Packets : 79675 170 pps
Bytes : 119512500 2040000 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 4991 0 pps
Low, non-TCP : 4991 0 pps
Low, TCP : 0 0 pps
High, non-TCP : 0 0 pps
High, TCP : 0 0 pps
RED-dropped bytes : 7486500 0 bps
Low, non-TCP : 7486500 0 bps
Low, TCP : 0 0 bps
High, non-TCP : 0 0 bps
High, TCP : 0 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps
Transmitted:
Packets : 0 0 pps
Bytes : 0 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps
Low, non-TCP : 0 0 pps
Low, TCP : 0 0 pps
High, non-TCP : 0 0 pps
High, TCP : 0 0 pps
RED-dropped bytes : 0 0 bps
Low, non-TCP : 0 0 bps
Low, TCP : 0 0 bps
High, non-TCP : 0 0 bps
High, TCP : 0 0 bps
Queue: 3, Forwarding classes: network-control
Queued:
Packets : 93967 166 pps
Bytes : 140596946 1980544 bps
Transmitted:
Packets : 88376 136 pps
Bytes : 132234860 1632000 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 5581 30 pps
Low, non-TCP : 5581 30 pps
Low, TCP : 0 0 pps
High, non-TCP : 0 0 pps
High, TCP : 0 0 pps
RED-dropped bytes : 8347086 348544 bps
Low, non-TCP : 8347086 348544 bps
Low, TCP : 0 0 bps
High, non-TCP : 0 0 bps
High, TCP : 0 0 bps
Tuesday, April 17, 2007, 8:19:13 AM, you wrote:
FAK> Dan
FAK> This is not working, even with enabling per-unit schedular on constituent
FAK> link and applying schedular-map to their logical unit in Class of Service
FAK> Interface hierarchy as u suggest.
FAK> Results are same, while pushing Gold, Silver or BE traffic, i.e. all goes to
FAK> queue 0 (BE). And in lsq interface, there is no Queue stats available (all
FAK> Queue stats are 0).
FAK> show interfaces e1-0/0/0 extensive
FAK> Physical interface: e1-0/0/0, Enabled, Physical link is Up
FAK> Traffic statistics:
FAK> Input bytes : 21834 0 bps
FAK> Output bytes : 23757 0 bps
FAK> Input packets: 305 0 pps
FAK> Output packets: 332 0 pps
FAK> Input errors:
FAK> Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed
FAK> discards: 0, L3 incompletes: 0, L2 channel errors: 0,
FAK> L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0, Resource
FAK> errors: 0
FAK> Output errors:
FAK> Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU
FAK> errors: 0, Resource errors: 0
FAK> Queue counters: Queued packets Transmitted packets Dropped
FAK> packets
FAK> 0 Besteffort 313
FAK> 313 0
FAK> 1 Silver 0
FAK> 0 0
FAK> 2 Gold 0
FAK> 0 0
FAK> 3 NC 19
FAK> 19 0
FAK> show interfaces e1-0/0/4 extensive
FAK> Physical interface: e1-0/0/4, Enabled, Physical link is Up
FAK> Input bytes : 22186 0 bps
FAK> Output bytes : 23072 0 bps
FAK> Input packets: 300 0 pps
FAK> Output packets: 323 0 pps
FAK> Input errors:
FAK> Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed
FAK> discards: 0, L3 incompletes: 0, L2 channel errors: 0,
FAK> L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0, Resource
FAK> errors: 0
FAK> Output errors:
FAK> Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU
FAK> errors: 0, Resource errors: 0
FAK> Queue counters: Queued packets Transmitted packets Dropped
FAK> packets
FAK> 0 Besteffort 304
FAK> 304 0
FAK> 1 Silver 0
FAK> 0 0
FAK> 2 Gold 0
FAK> 0 0
FAK> 3 NC 19
FAK> 19 0
FAK> show interfaces lsq-0/2/0 extensive
FAK> Physical interface: lsq-0/2/0, Enabled, Physical link is Up
FAK> Interface index: 194, SNMP ifIndex: 260, Generation: 193
FAK> Link-level type: LinkService, MTU: 1504
FAK> Device flags : Present Running
FAK> Interface flags: Point-To-Point SNMP-Traps 16384
FAK> Last flapped : 2007-03-27 13:10:39 PKT (2w6d 21:56 ago)
FAK> Statistics last cleared: 2007-04-17 11:04:24 PKT (00:02:34 ago)
FAK> Traffic statistics:
FAK> Input bytes : 54709 26760 bps
FAK> Output bytes : 58396 28144 bps
FAK> Input packets: 704 44 pps
FAK> Output packets: 782 46 pps
FAK> Frame exceptions:
FAK> Oversized frames 0
FAK> Errored input frames 0
FAK> Input on disabled link/bundle 0
FAK> Output for disabled link/bundle 0
FAK> Queuing drops 0
FAK> Buffering exceptions:
FAK> Packet data buffer overflow 0
FAK> Fragment data buffer overflow 0
FAK> Assembly exceptions:
FAK> Fragment timeout 0
FAK> Missing sequence number 0
FAK> Out-of-order sequence number 0
FAK> Out-of-range sequence number 0
FAK> Hardware errors (sticky):
FAK> Data memory error 0
FAK> Control memory error 0
FAK> Queue counters: Queued packets Transmitted packets Dropped
FAK> packets
FAK> 0 Besteffort 0
FAK> 0 0
FAK> 1 Silver 0
FAK> 0 0
FAK> 2 Gold 0
FAK> 0 0
FAK> 3 NC 0
FAK> 0 0
FAK> Well is it necessary to implement the fragmentation map, multiclass or LFI
FAK> settings. as we are not implementing these.
FAK> Does any one has the practical implmentation experience to implement CoS
FAK> over MLPPP, if yes than please share your sample configuration and comments
FAK> on this issue.
FAK> Thanks and Regards
FAK> Fahad Ali Khan
FAK> 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
>>
>>
FAK> _______________________________________________
FAK> juniper-nsp mailing list juniper-nsp at puck.nether.net
FAK> https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list