The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2003-Jan> msg00058



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: QoS

  • From: Santiago Alvarez <saalvare@cisco.com>
  • Date: Thu, 16 Jan 2003 09:49:05 -0800
  • CC: mpls-ops@mplsrc.com, saalvare@cisco.com
  • Resent-Date: Thu, 16 Jan 2003 14:34:40 -0500
  • To: Eddy Tedjasaputra <eddyt@sistelindo.com>

If you're looking for _min_bw_guarantees_during_congestion_, you need to
have output policies on the gw and the internet router and have
customers queued separately.  Not a scalable solution since the number
of customers can go beyond the queuing/scheduling capabilities of those
two nodes (e.g. 10,000 customers).  Aside from mgmt issues (e.g. you may
not have control over the two nodes, you may not want to touch those
routers every time you add a customer).  You could also try to implement
a solution policing individual customers, but your SLA would be
different (no _min_bw_guarantees_during_congestion_ kind of guarantee). 
In that case, you could implement all your policies on the gw, but
you'll also hit scalability issues as the customer base grows and you
might face similar mgmt issues.  If you really want to have per-customer
SLAs for internet traffic, you're best bet it to implement all policies
(upstream/downstream) on the PE (for unmanaged service) or on the CPE
(for managed service).  Some downstream bandwidth will be wasted since
it'll be dropped right before reaching the customer and after having
consumed backbone bandwidth, but that's the price you'd have to pay. 
Should I say, the customer would have to pay...
Cheers.

SA
--
Eddy Tedjasaputra 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
> 
> [Image]
> 
> 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

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


  • Follow-Ups:
    • Re: QoS
      • From: "Bruce" <bruce_reid202@hotmail.com>
  • References:
    • QoS
      • From: "Eddy Tedjasaputra" <eddyt@sistelindo.com>