The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2001-Nov> msg00106



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

Re: Bandwidth Reservation

  • From: Robert Raszuk <raszuk@cisco.com>
  • Date: Tue, 20 Nov 2001 20:27:46 +0100
  • CC: Carlos Parada <carlos-f-parada@ptinovacao.pt>, mpls-ops@mplsrc.com, "'Javier Antich'" <javier.antich@telindus.es>
  • Organization: Signature: http://www.employees.org/~raszuk/sig/
  • Resent-Date: Tue, 20 Nov 2001 17:55:57 -0500
  • To: Vipul Sharma <vsharma@zagrosnetworks.com>


Yes you are correct. The scheduler classes are per CoS not fec for now.
When L-LSPs come in this statement may no longer apply.

R.

> Vipul Sharma wrote:
> 
> Robert,
>         My understanding is that in the data plane resource reservation is done per
> CoS (each Class may be defined by DSCP marking for example). This resource
> reservation is generally static and to change it is a traffic interrupting
> event. It is based on the network archtecture and design requirements. Each
> flow coming into the user port on a line card maps to one of the many CoS.
>         It is the responsibility of the control plane to make sure that flows
> resource requirements are within the resources that have been allocated for
> CoS. The flows resource requirements may be signalled (i.e. RSVP-TE or CR
> LDTE for MPLS).
>         My understanding is that leaky bucket of BW provisioning is done for CoS
> only... Is that correct? Or is it done per flow (per fec)??
> 
> Vip
> -----Original Message-----
> From: Robert Raszuk [mailto:raszuk@cisco.com]
> Sent: Tuesday, November 20, 2001 12:33 PM
> To: Carlos Parada
> Cc: 'mpls-ops@mplsrc.com'; 'Javier Antich'
> Subject: Re: Bandwidth Reservation
> 
> Carlos,
> 
> >         I though that this reservation is supposed to be a strict resource
> > reservation (like IntServ).
> 
> All I can say is that You are not the only one who tought that way :).
> 
> >         In this case, how can I implement the 'pipe model', where an
> amount
> > of bandwidth between two PEs must be assured ? Make sense these kinds of
> > reservations without strict reservations ?
> 
> Use diffserv-aware TE. It will still _NOT_ reserver for you any
> interface resources (like IntServ would do), but it will provide you
> with possibility to use pre-reserved & pre allocated queuing/scheduling
> resources in your boxes.
> 
> R.
> 
> > Carlos Parada wrote:
> >
> > Hola Javier,
> >
> > > Hi Carlos,
> > >
> > >     TE tunnels provide no real reservation, it is just in the control
> > > plane,
> > > not in the forwarding plane. There are no specific buffer space assigned
> > > to
> > > that tunnel which guarantees anything, it is just that now you have
> > > 2000-500=1500 left for new "reservations".
> > >
> >         [Carlos Parada]
> >         I though that this reservation is supposed to be a strict resource
> > reservation (like IntServ).
> >         In this case, how can I implement the 'pipe model', where an
> amount
> > of bandwidth between two PEs must be assured ? Make sense these kinds of
> > reservations without strict reservations ?
> >
> >
> > >    Regards.
> > >    Javier.
> > >
> > >                                           ^   ^
> > > ==============ooo====(.)v(.)====ooo=====
> > > Javier Antich Romaguera
> > > Network Consultant
> >
> > --------------------------------------------------------------------------
> > > -
> > > TELINDUS
> > > Pza. Ciudad de Viena, 6-2º
> > > 28040 Madrid
> >
> > --------------------------------------------------------------------------
> > > -
> > > javier.antich@telindus.es
> > > tel: +34 91 456 00 08
> > > fax: +34 91 536 10 74
> >
> > --------------------------------------------------------------------------
> > > -
> > > For more information about our products and services,
> > > please visit our website http://www.telindus.com
> >
> > --------------------------------------------------------------------------
> > > -
> > > Full connectivity & mobility
> > > ==================ooo0===0ooo========
> > >
> > >
> > >
> > > > -----Mensaje original-----
> > > > De: Carlos Parada [SMTP:carlos-f-parada@ptinovacao.pt]
> > > > Enviado el: martes 20 de noviembre de 2001 13:07
> > > > Para:       'mpls-ops@mplsrc.com'
> > > > Asunto:     Bandwidth Reservation
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > I'm configuring a bandwidth reservation for a VPN/MPLS tunnel in a
> Cisco
> > > > 7200 IOS 12.1(5)T7. The problem is that it doesn't work. The bandwidth
> > > not
> > > > guaranteed, having the traffic rate a strange random behavior.
> > > >
> > > > I'm using just the command
> > > > tunnel mpls traffic-eng bandwidth 500
> > > > in the tunnel, and
> > > > ip rsvp bandwidth 2000 2000
> > > > for interfaces. (NOTE: this command is accepted but when I type '?'
> the
> > > > possible commands are not displayed since 'ip rsvp').
> > > >
> > > > Anybody knows if this version has any bug ? or I'm missing something ?
> > > >
> > > > Thanks in advance.
> > > >
> > > > Best Regards.
> > > >
> > > >
> > > >
> > > > Carlos Parada
> > > >
> > > > **********
> > > > Carlos Fonseca Parada
> > > > Portugal Telecom INovação, S.A.
> > > > MSI - Multimédia e Serviços IP - Redes MultiServiço
> > > > MIS - Multimedia and IP Services - MultiService Networks
> > > > *   Rua Engº José Ferreira Pinto Basto - 3810 Aveiro - Portugal
> > > > * Ext: 1317             (+351 234 403317)
> > > >
> > > >
> > > > -------
> > > > The MPLS-OPS Mailing List
> > > > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> >
> > -------
> > The MPLS-OPS Mailing List
> > Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

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