The MPLS-OPS Archive

["Gopal@Yahoo" <gnaganab@yahoo.com>]

Hi Eddy,
For the incoming traffic(coming from internet):
We can't do much with the intf-X congestion. We can
QOS the traffic in your Network all the way to the
cust-A.
So,
1)On PE3 intf-X(incoming intf), classify the traffic
and mark the classes for identification across the
network.
2)On PE3 outgoing intf(intf towards your cloud) treat
the classes the way you want by applying proper qos.
You may apply appropriate qos on the outgoing
interfaces on all routers in the core and the egress
edge to treat the classes.

As you stated in the other emails that the policing is
not working, could you provide us:
sho policy interface <interface>
or,
sho interface <intf> rate
and associated ACLs?

Thanks,
Gopal


--- Eddy Tedjasaputra <eddyt@sistelindo.com> wrote:
> Hi Gopal, 
> 
> What we're trying to limit is the 'incoming
> traffic'.
> Following your suggestion..
> Point 1), means classify traffic on the incoming
> inteface of PE3, 
> Point 2), means apply qos on the outgoing interface
> of PE1 and PE2
> My question is how can PE3 know that  a specific
> traffic destined to CustA 
> have to use a certain qos
> as the traffic is not reach PE1 (where the qos
> defined) yet.
> 
> Thanks, Eddy
> 
> 
> 
> 
> "Gopal@Yahoo" <gnaganab
> 16/01/2003 14:54
> 
>  
>         To:     Eddy Tedjasaputra
> <eddyt@sistelindo.com>, mpls-ops@mplsrc.com
>         cc: 
>         Subject:        Re: [MPLS-OPS]: QoS
> 
> 
> Eddy, 
> when you talk about 'traffic' be specific as to
> which
> direction. let's say: incoming-traffic = traffic
> coming from Internet; out-going traffic = traffic
> going to Internet. 
> 
> Internet-----PE3-YourCloud--PE1------cust-A
>                           \-PE2------cust-b
> 
> basic rules: 1)classify traffic on the incoming edge
> interface
> 2)apply qos on the outgoing interfaces on all edge
> routers. (if you design well no need to apply qos on
> the core routers. if yours is not, then apply qos on
> out intf of the core rtrs also)
> 
> Now, if you have any questions, pls ask.
> 
> rgds,
> GOpal
> 
> PS: you applied policing which limits traffic. it
> won't guarantee.
> 
> --- Eddy Tedjasaputra <eddyt@sistelindo.com> wrote:
> > Hello everybody, 
> > 
> > I'm setting up the following configuration.
> > An MPLS cloud with 3 PEs :
> >    PE1 is connected to CPE A (customer A)
> >    PE2 is connected to CPE B (customer B)
> >    PE3 (Internet Gateway) is connected to an
> > Internet router
> > 
> > 
> > 
> > 
> > 
> > I tried to use a policy map below to guarantee the
> > b/w (32K) is available 
> > to Cust A during congestion period.
> > This policymap is applied on the incoming
> interface
> > of PE3 (interface X)
> > >>>
> > policymap Test
> > class CustA
> >      police cir 32000 bc 4000 pir 128000 be 4000
> > conform-action transmit 
> > exceed-action set-prec-transmit 2 violate-action
> > drop
> > >>>
> > Can someone please advise me the best way how to
> > guarantee a minimum 
> > thruput (ie. CIR) for every customer when 
> > a CONGESTION is occured between Internet G/W and
> > Internet router ?
> > 
> > Appreciate for any comments.
> > Thanks, Eddy
> > 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up
> now.
> http://mailplus.yahoo.com
> 
> 
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml