[c-nsp] QOS difference behavior for GSR and 7609

[Xu Hu]

Ok, do you heard about the MDRR in the GSR? What's the main purpose of this QOS approach?

Thanks and regards,
Xu Hu

On 15 May, 2012, at 0:34, Mack McBride <mack.mcbride at viawest.com> wrote:

> Your question is not clear.
> Yes the GSR and 7609 are very different.
> The 7609 can only do policing and match criteria are limited.
> The GSR is much more flexible.
> 
> Mack
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of jstuxuhu0816
> Sent: Monday, May 14, 2012 5:18 AM
> To: cisco-nsp
> Subject: [c-nsp] QOS difference behavior for GSR and 7609
> 
> Hi Team Experts,
> Does anyone encounter the qos different behavior from GSR and 7609-S.
> Since the GSR is using MDRR, 7609 using PQ/WRED instead. I don't understand the difference between this two.
> 
> Attach one example configuration as bellow:
> class-map match-any Q1
>          match ip dscp 54
> class-map match-any Q2
>          match ip dscp 34
> class-map match-any Q3
>          match ip dscp 18 
> class-map match-any Q4       
>         match ip dscp 12
> 
> Policy-map Main-Output
> class Q1-inelastic
>      priority
> police cir percent 35
> class Q2-elastic
>      bandwidth percent 10
> random-detect dscp-based
> class Q3-elastic
>      bandwidth percent 15
> random-detect dscp-based
> class Q4-elastic
>      bandwidth percent 20
>      random-detect dscp-based
> class class-default
>      random-detect dscp-based
> 
> 
> 
> 
> Thanks and Regards,
> Hu Xu
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/