From: Bit Gossip (bit.gossip@chello.nl)
Date: Tue Jul 03 2007 - 03:35:40 ART
I agree on this approach but I have one comment:
the classes within a policy-map are tested in the same order as they
appear so if a pkt matches the first class it is treated accordingly and
then it exits the service-policy; so it can not match any subsequent
class just like ACL
This means that it is not necessary:
 match not dscp ef
 match not dscp af31
 match not protocol rtp audio
for classes CLIENTx
Thanks,
bit.
On Mon, 2007-07-02 at 16:12, Salau, Yemi wrote:
> Why would you want to give 90% of a serial link to voice and 10% to
> data, that is weird from my own view. That's about 1389.6kbps for voice
> and 46kbps for each customer's data traffic .... (Assuming the serial
> interface is 1544kbps)
> 
> There are so many ways to achieve this, this is one of them ... 
> 
> !
> class-map match-any VOICE
>  match  dscp ef
>  match  dscp af31
>  match protocol rtp audio
> class-map match-all CLIENT1
>  match access-group name CLIENT1
>  match not dscp ef
>  match not dscp af31
>  match not protocol rtp audio
> class-map match-all CLIENT2
>  match access-group name CLIENT2
>  match not dscp ef
>  match not dscp af31
>  match not protocol rtp audio
> class-map match-all CLIENT3
>  match access-group name CLIENT3
>  match not dscp ef
>  match not dscp af31
>  match not protocol rtp audio
> !
> policy-map PRIORITY
>  class VOICE
>   priority percent 90
>  class CLIENT1
>   bandwidth percent 3
>  class CLIENT2
>   bandwidth percent 3
>  class CLIENT3
>   bandwidth percent 3
> !
> Int s0/0/0
>  max-reserved-bandwidth 100
> !
> 
> Then configure ip extended access-lists CLIENT1, CLIENT2 and CLIENT3 to
> respectively match any traffic destined for your individual clients
> 
> Many Thanks
>  
> Yemi Salau
> 
> 
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> hadek.el-ayachi@nsn.com
> Sent: Monday, July 02, 2007 1:54 PM
> To: ninajoe123@gmail.com; ccielab@groupstudy.com
> Subject: RE: qos problem
> 
> I don't understand.
> In my point of view, use PQ for voice traffic only, then exclude voice
> traffic fron ACL 101 102 103 and use a normal service policy without
> hierarchical MQC like this:
>    service policy qos
>      class voip
>       priority 90 ! Because max-reservable you set is 90%
>      class client1
>       bwd 33
>      class client1
>       bwd 33
>      class client1
>       bwd 33
> 
> Also, note that in your configuration below, you applied the qos only to
> voice traffic and no qos is garanted for class-default!
> 
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> ext Joe Higgins
> Sent: lundi 2 juillet 2007 11:50
> To: ccielab@groupstudy.com
> Subject: qos problem
> 
> I have the following scenerio that I need some help .  I have a link on
> a serial interface that passes voice and data traffic to three clients.
> My qos requirement is to give strict priority to all voice traffic
> regardless to which client it is destined. I then have to give each
> client one third of
> any bandwidth that is still available.   The following is my proposed
> configuration.
> 
> 
> class-map match-all rtptraffic
> 
>  match protocol rtp voice
> 
> 
> 
> class-map match-all client1
> 
>  match access-group 101
> 
> 
> 
> class-map match-all client2
> 
>  match access-group 102
> 
> 
> 
> class-map match-all client3
> 
>  match access-group 103
> 
> 
> 
> policy-map othertraffic
> 
>  class client1
> 
>   bandwidth percent 33
> 
> class client2
> 
>   bandwidth percent 33
> 
> class client3
> 
>   bandwidth percent 33
> 
> 
> 
> policy-map voice
> 
>  class  rtptraffic
> 
>   priority percent 100
> 
>   service-policy othertraffic
> 
> 
> 
> interface serial 1/0
> 
> max-reserved-bandwidth 90
> 
> service-policy output voice
> 
> _______________________________________________________________________
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
> 
> _______________________________________________________________________
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
> 
> _______________________________________________________________________
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:39 ART