Re: Basic QoS config

Actually neither option restricts bandwidth for SMTP. They both guarantee a
minimum amount of bandwidth, but in no congestion will allow it to use the
full 512K. Whether to do traffic shaping is entirely a different question,
but I think in a 512K link, if you can you probably should. Also curious
that you call your policy-map CBWFQ but don't actually explicitly call for
weighted fair queue. I think since the link is under 2Mb it would do cbwfq
by default though.

On Wed, Mar 13, 2013 at 10:07 AM, ftt <femi0802_at_gmail.com> wrote:

> Hi
>
> Without labbing this up, it looks to me like method 1 does two things,
> restricts snmp traffic to 256k and restricts total bandwidth to 512k.
> Method 2 restricts snmp traffic to 256k, but doesn't control total traffic
> (i.e any other types of traffic).
>
> Therefore i will say, because your question was about restricting snmp
> traffic ONLY, both methods meet the requirement as there are no
> requirements about total traffic not exceeding 512k.
>
>
>
>
> On Sun, Mar 10, 2013 at 11:43 AM, Sarad <tosara_at_gmail.com> wrote:
>
> > Hi Guys,
> >
> > I came up with the bellow doubt in my mind while labing some QoS stuff,
> > appreciate if you can share your opinion on this
> > R1 & R2 connected with a 512 Kbps link, We need to gurantee snmp will get
> > 256Kbps in a congested scenario. Between two methods bellow what do you
> > think most appropriate method? Issue I see with method 2 is bandwidth
> > command on the interface will not limit the traffic as a result traffic
> can
> > go up to the physical interface rate. So I believe option 1 is more
> > accurate. Please let me know what your openion on this.
> >
> >
> >
> > *Methos 1*
> >
> > access-list extended SMTP_TO_SERVER
> > permit tcp any host any eq smtp
> >
> >
> > class-map match-all SMTP_TO_SERVER
> > match access-group name SMTP_TO_SERVER
> >
> > *policy-map CBWFQ
> > class class-default
> > shape-average 512000
> > class SMTP_TO_SERVER
> > bandwidth 256
> > *
> > interface Serial0/0/0
> > bandwidth 512
> > service-policy output CBWFQ
> >
> >
> >
> > interface Serial0/0/0
> > bandwidth 512
> > service-policy output CBWFQ
> >
> >
> >
> >
> ---------------------------------------------------------------------------------------
> > *Method 2*
> >
> > interface Serial0/0/0
> > bandwidth 512
> > service-policy output CBWFQ
> > ip access-list extended SMTP_TO_SERVER
> > permit tcp any host any eq smtp
> >
> >
> > class-map match-all SMTP_TO_SERVER
> > match access-group name SMTP_TO_SERVER
> >
> > *policy-map CBWFQ
> > class SMTP_TO_SERVER
> > bandwidth 256*
> >
> > interface Serial0/0/0
> > bandwidth 512
> > service-policy output CBWFQ
> >
> > Thanks
> > Sara
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Marc Abel
CCIE #35470
(Routing and Switching)
Blogs and organic groups at http://www.ccie.net