[55410] in North American Network Operators' Group
Re: Aggregate traffic management
daemon@ATHENA.MIT.EDU (Kyle C. Bacon)
Tue Jan 28 17:46:32 2003
To: Stanislav Rost <stanrost@lcs.mit.edu>
Cc: nanog@merit.edu, owner-nanog@merit.edu
From: "Kyle C. Bacon" <kbacon@fnsi.net>
Date: Tue, 28 Jan 2003 17:43:27 -0500
Errors-To: owner-nanog-outgoing@merit.edu
Take a look at a product called "Path Control" by RouteScience.
http://www.routescience.com/
I have seen their product in action and it is very slick. Does exactly
what you want,
plus a whole lot more and does it transparently (so if it fails you aren't
SOL) via
manipulating BGP tables and nexthop based on a multitude of criteria.
K
Stanislav
Rost To: nanog@merit.edu
<stanrost@lcs cc:
.mit.edu> Subject: Aggregate traffic management
Sent by:
owner-nanog@m
erit.edu
01/28/2003
04:59 PM
Dear NANOGers,
I have a very hands-on question:
Suppose I am a network operator for a decent-sized ISP, and I decide
that I want to "divide" aggregate traffic flowing through a router
toward some destination, in order to then send some of it through one
route and the remainder through another route. Thus, I desire to
enforce some traffic engineering decision.
How would I be able to accomplish this "division"? What technologies
(even if vendor-specific) would I use?
I can think of some methods like prefix-matching classification and
ECMP, but I am still not sure exactly how the latter works in practice
(at the router level) and how one may set them up to achieve such
load-sharing.
Thank you for your expertise and lore,
--
Stanislav Rost <stanrost@lcs.mit.edu>
Laboratory for Computer Science, MIT
