From: HP-France,ex2 ("SANCHEZ-MONGE,ANTONIO)
Date: Mon Mar 22 2004 - 09:39:47 GMT-3
Hi,
I am not a RSVP guru at all but my understanding is that a transit router
needs to know what flows are to be scheduled in the priority RSVP queues.
You achieve that with the command:
ip rsvp pq-profile
Provided that the application sending the flow has signalled and reserved
the path through RSVP.
This is the approach compatible with the IntServ strategy.
Implementing LLQ in the path is the DiffServ approach, which is completely
independent from RSVP (but may led you to the same practical results). You
have to chose ;)
Cheers,
Ato.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Ng,
Kim Seng David (David)
Sent: lunes, 22 de marzo de 2004 12:04
To: ccielab@groupstudy.com
Subject: RSVP support for LLQ: Doc CD vs DQOS book
Hello group,
I am a bit confuse about the what is described in the doc CD compared to the
DQOS book about RSVP support for LLQ. Maybe I totally misunderstand the
whole thing.
1) Doc CD:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos
_
c/fqcprt5/qcfrsllq.htm#1005637
In the doc CD, it describes two required steps to configuring rsvp support
for LLQ. One of them is to configure the interface queueing to WFQ.
However,
2) DQOS book: page 619 and 620
In this book, it mentioned that in order to have rsvp support for LLQ, you
need to ensure LLQ is enabled on the interface via the "service-policy"
command and not by simply configuring WFQ on the interface as explained in
the doc CD.
Is there a difference between this two explainations or I misunderstood??
Thank you
David
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:43 GMT-3