List Info

Thread: Class of Service implementation over MLPPP link




Class of Service implementation over MLPPP link
user name
2007-04-05 02:32:33
Guys....im stuck in implementing CoS over MLPPP link (E1s).
My scenario is,
CE---PE===(2E1s MLPPP)===PE---CE
My configuration is as under,
chassis {
    fpc 0 {
        pic 2 {
            adaptive-services {
                service-package layer-2;
            }
        }
    }
interfaces {
    e1-0/0/0 {
        unit 0 {
            family mlppp {
                bundle lsq-0/2/0.0;
            }
        }
    }
     e1-0/0/1 {
        unit 0 {
            family mlppp {
                bundle lsq-0/2/0.0;
            }
        }
    }
interfaces lsq-0/2/0
per-unit-scheduler;
unit 0 {
    encapsulation multilink-ppp;
    family inet {
        address X.X.X.X/30;
    }
    family mpls;
}
class-of-service{
forwarding-classes {
    queue 0 Besteffort;
    queue 1 Silver;
    queue 2 Gold;
    queue 3 NC;
}
interfaces {
    e1-0/0/0 {
        scheduler-map CoS-MLPPP;
    }
    e1-0/0/1 {
        scheduler-map CoS-MLPPP;
    }
    lsq-0/2/0 {
        unit 0 {
            scheduler-map CoS-MLPPP;
            classifiers {
                dscp dscp
                exp exp
          }
            rewrite-rules {
                dscp dscp
               exp exp
          }
        }
    }
}
scheduler-maps {
    CoS-MLPPP {
        forwarding-class Besteffort scheduler
MLPPP-BestEffort;
        forwarding-class Silver scheduler MLPPP-Silver;
        forwarding-class Gold scheduler MLPPP-Gold;
        forwarding-class NC scheduler MLPPP-NC;
    }
}
schedulers {
    MLPPP-BestEffort {
        transmit-rate percent 40;
        buffer-size remainder;
        priority low;
    }
    MLPPP-Silver {
        transmit-rate percent 30;
        buffer-size percent 30;
        priority high;
    }
    MLPPP-Gold {
        transmit-rate percent 25;
        buffer-size remainder;
        priority strict-high;
    }
    MLPPP-NC {
        transmit-rate percent 5;
        buffer-size percent 5;
        priority high;
    }
}
same on the other PE side.....but the problem is......when
we classified CE
traffic as Gold or Silver.....lsq interface queue stats
shows....no packets
in the queue....means...0 queue/transfered packets from lsq
queue/buffer.
Also its contituent links (E1s) shows all packets goes from
its BE
queue...not in Silver (Q1) and Gold (Q2).

Kindly check the configuration and suggest is there any
configurational
issue or some other workarround is avaiable. HW is M10i with
10-CH-E1-IQ PIC
and AS-2 PIC.

Regards

Fahad
_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-16 10:59:06
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


Could you try changing this:

> class-of-service{
[..]
> interfaces {
>     e1-0/0/0 {
>         scheduler-map CoS-MLPPP;
>     }
>     e1-0/0/1 {
>         scheduler-map CoS-MLPPP;
>     }

to this:

> class-of-service{
[..]
> interfaces {
>     e1-0/0/0 {
        unit 0                      
<<<<<<< add this
>         scheduler-map CoS-MLPPP;
>     }
>     e1-0/0/1 {
         unit 0                      
<<<<<<< add this
>         scheduler-map CoS-MLPPP;
>     }


You may also want to consider fragmentation maps.



- Dan


> -----Original Message-----
> From: juniper-nsp-bouncespuck.nether.net 
> [mailto:juniper-nsp-bouncespuck.nether.net] On Behalf
Of 
> FAHAD ALI KHAN
> Sent: Thursday, April 05, 2007 2:33 AM
> To: juniper-nsp
> Subject: [j-nsp] Class of Service implementation over
MLPPP link
> 
> 
> Guys....im stuck in implementing CoS over MLPPP link
(E1s). 
> My scenario is,
> CE---PE===(2E1s MLPPP)===PE---CE
> My configuration is as under,
> chassis {
>     fpc 0 {
>         pic 2 {
>             adaptive-services {
>                 service-package layer-2;
>             }
>         }
>     }
> interfaces {
>     e1-0/0/0 {
>         unit 0 {
>             family mlppp {
>                 bundle lsq-0/2/0.0;
>             }
>         }
>     }
>      e1-0/0/1 {
>         unit 0 {
>             family mlppp {
>                 bundle lsq-0/2/0.0;
>             }
>         }
>     }
> interfaces lsq-0/2/0
> per-unit-scheduler;
> unit 0 {
>     encapsulation multilink-ppp;
>     family inet {
>         address X.X.X.X/30;
>     }
>     family mpls;
> }
> class-of-service{
> forwarding-classes {
>     queue 0 Besteffort;
>     queue 1 Silver;
>     queue 2 Gold;
>     queue 3 NC;
> }
> interfaces {
>     e1-0/0/0 {
>         scheduler-map CoS-MLPPP;
>     }
>     e1-0/0/1 {
>         scheduler-map CoS-MLPPP;
>     }
>     lsq-0/2/0 {
>         unit 0 {
>             scheduler-map CoS-MLPPP;
>             classifiers {
>                 dscp dscp
>                 exp exp
>           }
>             rewrite-rules {
>                 dscp dscp
>                exp exp
>           }
>         }
>     }
> }
> scheduler-maps {
>     CoS-MLPPP {
>         forwarding-class Besteffort scheduler
MLPPP-BestEffort;
>         forwarding-class Silver scheduler
MLPPP-Silver;
>         forwarding-class Gold scheduler MLPPP-Gold;
>         forwarding-class NC scheduler MLPPP-NC;
>     }
> }
> schedulers {
>     MLPPP-BestEffort {
>         transmit-rate percent 40;
>         buffer-size remainder;
>         priority low;
>     }
>     MLPPP-Silver {
>         transmit-rate percent 30;
>         buffer-size percent 30;
>         priority high;
>     }
>     MLPPP-Gold {
>         transmit-rate percent 25;
>         buffer-size remainder;
>         priority strict-high;
>     }
>     MLPPP-NC {
>         transmit-rate percent 5;
>         buffer-size percent 5;
>         priority high;
>     }
> }
> same on the other PE side.....but the problem
is......when we 
> classified CE
> traffic as Gold or Silver.....lsq interface queue stats

> shows....no packets
> in the queue....means...0 queue/transfered packets from
lsq 
> queue/buffer.
> Also its contituent links (E1s) shows all packets goes
from its BE
> queue...not in Silver (Q1) and Gold (Q2).
> 
> Kindly check the configuration and suggest is there any

> configurational
> issue or some other workarround is avaiable. HW is M10i
with 
> 10-CH-E1-IQ PIC
> and AS-2 PIC.
> 
> Regards
> 
> Fahad
> _______________________________________________
> juniper-nsp mailing list juniper-nsppuck.nether.net
> 
https://puck.nether.net/mailman/listinfo/juniper-nsp
> 

_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-17 01:19:13
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 <drautiojuniper.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-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-17 07:53:20
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-bouncespuck.nether.net
[mailto:juniper-nsp-bouncespuck.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 <drautiojuniper.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-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-17 07:56:33
Sorry, I meant classifying traffic by using filters on each
of the MLPPP
LSQ bundles. 

-evt

-----Original Message-----
From: juniper-nsp-bouncespuck.nether.net
[mailto:juniper-nsp-bouncespuck.nether.net] On Behalf
Of Eric Van Tol
Sent: Tuesday, April 17, 2007 8:53 AM
To: FAHAD ALI KHAN
Cc: juniper-nsp
Subject: Re: [j-nsp] Class of Service implementation over
MLPPP link

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-bouncespuck.nether.net
[mailto:juniper-nsp-bouncespuck.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 <drautiojuniper.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-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-17 16:59:08
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

josefbminsk# 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 <drautiojuniper.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-nsppuck.nether.net
FAK> 
https://puck.nether.net/mailman/listinfo/juniper-nsp
 
_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-18 00:47:11
>
> Dear Josef
>
> Thanks for your valuable information, and yes you got
right....i was
> checking on interface extensive, which not showing any
Q stats...while on
> *sh interface queue, *the packets are actually going to
those specific
> queue.
>
> Kindly can you explain this is little bit detail...as i
cant get it
> clearly.....
> " 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."
>
> What is the significance of MultiClass MLPPP, cant i
get the
> Gold/Silver/BE/NC traffic with out configuring this
parameter?
>
> Also while checking on consituent link stats (sh
interface extensive or sh
> interface queue) both shows the packets are going
through BE queue, where as
> at lsq level they are flowing through Gold or Silver.
>
> Can you provide this information.
>
> Regards
>
> Fahad
>
>
>  On 4/18/07, Josef Buchsteiner <josefbjuniper.net> wrote:
> >
> > 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
> >
> > josefbminsk# 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
> >
>
_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: Class of Service implementation over MLPPP link
user name
2007-04-18 02:30:54
    

Wednesday, April 18, 2007, 7:47:11 AM, you wrote:
>>
>> Dear Josef
>>
>> Thanks for your valuable information, and yes you
got right....i was
>> checking on interface extensive, which not showing
any Q stats...while on
>> *sh interface queue, *the packets are actually
going to those specific
>> queue.
>>
>> Kindly can you explain this is little bit
detail...as i cant get it
>> clearly.....
>> " 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."
>>
>> What is the significance of MultiClass MLPPP,


   one  of  the  main driver for multiclass is that you can
load-share
   different  class  of mlppp traffic across the bundles.
Without this
   you  can only load-share *one* mlppp class and LFI
traffic needs to
   be hashed on *one* single member link to avoid
re-ordering.



>>  cant i get the
>> Gold/Silver/BE/NC traffic with out configuring this
parameter?


   which  you  have  already  at  the LSQ level. Don't think
about the
   queue   on   the   PIC.  Just  see the egress interface
as one FIFO
   and  traffic is already arriving at the scheduler you
have defined.
   
   We  should not see queuing on the egress PIC and if it
does because
   the line has errors then you will drop but only for queue
0. If you
   would  send the ml traffic with one seq# pool into
different egress
   queues  and  you start dropping them according to the
scheduler you
   have  applied to the LSQ interface we will get massive
re-order and
   huge  jitter  sine  the remote side is waiting for the
frames for a
   certain period of time.
   
   The  scheduler  according  to your configuration is
applied already
   *before*  the  ML Sequence stamps is build which is the
right thing
   to  do. Never but ML traffic which has one seq# pool into
different
   queues.


>>
>> Also while checking on consituent link stats (sh
interface extensive or sh
>> interface queue) both shows the packets are going
through BE queue, where as
>> at lsq level they are flowing through Gold or
Silver.

   which is correct. you have done queuing/shaping/scheduler
actions
   already at lsq level.


           Josef


   

>>
>> Can you provide this information.
>>
>> Regards
>>
>> Fahad
>>
>>
>>  On 4/18/07, Josef Buchsteiner <josefbjuniper.net> wrote:
>> >
>> > 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
>> >
>> > josefbminsk# 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
>> >
>>

 
_______________________________________________
juniper-nsp mailing list juniper-nsppuck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp

[1-8]

about | contact  Other archives ( Real Estate discussion Medical topics )