From: Tim (ccie2be@nyc.rr.com)
Date: Mon Nov 07 2005 - 08:22:01 GMT-3
Hey Steve,
For your requirement, I don't think RSVP is the way to go.
RSVP's role in QoS isn't so much low latency as much as pre-allocating
resources along the path.
To guarantee low latency, you want to prioritize said traffic ahead of other
traffic. You might also want to fragment traffic to reduce the
serialization delay (the amount of time it takes to put the traffic on the
wire.) By using fragmentation, you reduce the time your prioritize traffic
has to wait behind a large non-prioritized packet.
You might also want to implement WRED in such a way that your prioritized
traffic is less likely to be dropped when the queue starts filling up. You
could do this by marking your prioritized traffic with a higher ip prec or
dscp value compared to other traffic and then configure WRED to drop the
non-priority traffic if and when the queue starts getting to full.
HTH, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
steven richards
Sent: Sunday, November 06, 2005 7:32 PM
To: ccielab@groupstudy.com
Subject: Choosing QoS method for between routers
I need a low latency real time data stream of traffic optimized to 128K for
traffic incoming from router A ser 01 and going through ser 0/0 to router B.
I want to guarentee the 128k of low latency between the connection of Router
A and B. I think the best way to do this is through RSVP. Would I just need
to do this command on Router A or would I need to add this on B as well? If
I needed to just guareentee the bandwidth from A to B would I just add the
command like below on A? Does anyone have any other ways to do this ? Like
maybe fragmenting traffic over the link?
Thank you in advance
Router A
int ser 0/0
ip rsvp bandwidth 128
ser 0/1 Router A ser 0/0 <-> Router B
-----> Traffic --------------->
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:05 GMT-3