From: Jonathan V Hays (jhays@jtan.com)
Date: Wed Apr 02 2003 - 00:35:13 GMT-3
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> Behalf Of Hunt Lee
> Sent: Tuesday, April 01, 2003 8:51 AM
> To: ccielab@groupstudy.com
> Subject: RSVP requirement question
>
>
> Hi,
>
> I have searched the GroupStudy archive, but I can't find the
> answer to my question(I have also asked this question before,
> but unfortunately no-one responded)...
>
> Anyway, what I want to ask is that for RSVP to work, do I
> need to also enable Weighted Fair Queueing or Weighted Random
> Early Detection on all the interfaces along the way from the
> RSVP source to destination, or does RSVP can work by itself
> (without WFQ nor WRED on the interfaces)?
>
RSVP provides signaling, requesting that RSVP routers give priority to
certain traffic. But RSVP will not queue or send packets. So once the
reservation is make, WFQ or WRED does the work.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/
qos_c/qcprt5/qcdsig.htm#xtocid192422
"RSVP does not perform its own routing; instead it uses underlying
routing protocols to determine where it should carry reservation
requests. As routing changes paths to adapt to topology changes, RSVP
adapts its reservation to the new paths wherever reservations are in
place. This modularity does not prevent RSVP from using other routing
services. RSVP provides transparent operation through router nodes that
do not support RSVP.
RSVP works in conjunction with, not in place of, current queueing
mechanisms. RSVP requests the particular QoS, but it is up to the
particular interface queueing mechanism, such as WFQ or WRED, to
implement the reservation."
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:35:45 GMT-3