RE: Aggregate traffic management
We are a RouteScience customer. We are using this box and it rules. We
have been extremely happy with the results. We have multiple OC-x
circuits that we are engineering traffic over, and this box gives us the
ability to "see" things that we could not see before.
It also really allows us to differentiate our upstream providers - or
tell that they are really all the same. The reports it produces are
excellent. We have even used it to negotiate better SLAs and pricing
with our bandwidth providers.
Feel free to email me off-list if you want more information.
Sincerely,
Todd A. Blank
IPOutlet LLC
-Original Message-
From: Kyle C. Bacon [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 5:43 PM
To: Stanislav Rost
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Aggregate traffic management
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: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]>
Laboratory for Computer Science, MIT
Re: Aggregate traffic management
Hopefully I can stay within the bounds of NANOG's traditions against marketing material if I limit myself to thanking Kyle for his comments, and encourage anyone attending NANOG 27 who would like more info on automated control of routing for load objectives to come find me at the meeting. Mike Lloyd CTO, RouteScience Kyle C. Bacon wrote: 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: [EMAIL PROTECTED] 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 <[EMAIL PROTECTED]> Laboratory for Computer Science, MIT
Re: Aggregate traffic management
Stanislav, It depends what control mechanism you are using: o routes learned via an IGP - ECMP would work and if it's a single destination host, per-packet loadbalancing between the outgoing links is your only practical choice; rest of ECMP schemes work by distributing flows or routes amongst links o learned via BGP and the traffic consists of a variety of flows that all use the same reachability information (BGP route); you could de-aggregate the announcement locally if you have an idea how the per-flow volume maps into the route; BGP Multipath feature set exists in most router implementations, but the distribution methods are statistically different For the latter, several systems exist in the market place that try to automate TE for BGP-learned routes, one of which is ours. These system require a closed feedback loop for traffic volume per flow and link mappings; this needs to occur close to real time to be effective. - Serge Thus spake Stanislav Rost ([EMAIL PROTECTED]): > > 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 <[EMAIL PROTECTED]> > Laboratory for Computer Science, MIT
Re: Aggregate traffic management
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: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]>
Laboratory for Computer Science, MIT
Re: Aggregate traffic management
It can be done several ways, but the question is "how are you differentiating"? This is an incomplete list of methods for differentiating, each of which is supported by one or more vendors or open-source solutions: - destination address - specific prefix matching - prefix length matching (.../23, /24, etc.) - destination AS # - destination AS path length - destination (fill in the blank for other BGP or IGP specific tricks) - source address (see "destination address" for list of possible match criteria) - protocol (UDP, TCP, ICMP) - port (source or destination) - ToS bits - URL for port 80 traffic - MAC address of source machine - amount of throughput to a particular source/destination path There are even some methods that don't differentiate, but do random traffic distribution (for some highly imperfect value of "random", which I won't debate here.) - round-robin gateway specification - DNS round-robin (limited use, usually for servers producing traffic) If you could be more specific on what your distinguishing method would be for choosing one path over the other, some specific examples could be distilled from this group, I'm sure. Though, of course, we here in North America don't have to worry ourselves about these issues, and we route everything through our most congested peer. Is this simply to get a survey of all possible routing decision concepts, or are you looking for answers only at one layer of the OSI model? You do say "router" in your description, but I'm still uncertain if that is a limiting factor in your question. JT 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 <[EMAIL PROTECTED]> Laboratory for Computer Science, MIT
Re: Aggregate traffic management
From: "Stanislav Rost" > 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. > To my knowledge it is somewhat vendor specific. I've used policy routes and tag switching in dividing and altering traffic flows. I do know that with some vendors, it is important to make sure you activate the optimizations for things such as policy routing to save mass amounts of cpu time. I'm still a neophyte when it comes to tag switching. Others might help better in that. Jack Bates BrightNet Oklahoma
Aggregate traffic management
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 <[EMAIL PROTECTED]> Laboratory for Computer Science, MIT
