Advice on BGP traffic engineering for classified traffic
I'm curious if anyone has a pointer on traffic manipulation for classified traffic. Basics, I have a really cheap transit connection that some customers are paying reduced rates to only use that connection (and not my other transits). Though I've considered support for cases where NSP peering disputes break out. While I can advertise their networks out the correct transit for return traffic, I still have to figure out how to handle egress traffic. I'm guessing the crux of it is policy routing based on source address, but I'm interested in ways to engineer it to easy management and scalability. I've considered the possibility of an l3vpn to interconnect customers that are not requiring full routes, and possibly some type of vpls tunnel terminated at the necessary router for customers who need full routes. Thoughts, pointers, suggestions? Jack
----- Original Message -----
From: "Jack Bates" <jbates@brightok.net>
I'm curious if anyone has a pointer on traffic manipulation for classified traffic.
Based on the remainder of your post, I'm going to go ahead and assume that you don't mean "classified traffic" in the sense that most people would infer from that phrasing. Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
On 10/24/2011 10:47 PM, Jay Ashworth wrote:
----- Original Message -----
From: "Jack Bates"<jbates@brightok.net> I'm curious if anyone has a pointer on traffic manipulation for classified traffic. Based on the remainder of your post, I'm going to go ahead and assume that you don't mean "classified traffic" in the sense that most people would infer from that phrasing.
Yeah, I was at a loss for terminology, and never could write a good subject line. Does, I need to do least cost routing for a substandard low-cost product work? Hey, I work for a telco, why fight it. :) Jack
I have contemplated this exact scenario numerous times on how to provide various "tiers" of blended bandwidth. Ingress is handled by ip assignment + announcements, but egress almost *always* comes back to some sort extra core/distribution device to handle each tier, plus either mpls/l2vpn/dedicated-xcon/spanned-vlan to get the customer on that network. Cludgy at best, imo. I'd also love to hear how other datacenters or ISPs do this. Randal On Mon, Oct 24, 2011 at 4:24 PM, Jack Bates <jbates@brightok.net> wrote:
I'm curious if anyone has a pointer on traffic manipulation for classified traffic. Basics, I have a really cheap transit connection that some customers are paying reduced rates to only use that connection (and not my other transits).
Jack Bates wrote:
I'm curious if anyone has a pointer on traffic manipulation for classified traffic.
Basics, I have a really cheap transit connection that some customers are paying reduced rates to only use that connection (and not my other transits). Though I've considered support for cases where NSP peering disputes break out. While I can advertise their networks out the correct transit for return traffic, I still have to figure out how to handle egress traffic.
I'm guessing the crux of it is policy routing based on source address, but I'm interested in ways to engineer it to easy management and scalability. I've considered the possibility of an l3vpn to interconnect customers that are not requiring full routes, and possibly some type of vpls tunnel terminated at the necessary router for customers who need full routes.
Thoughts, pointers, suggestions?
One simple way to do this is with two routers each with a different table. One for your expensive transit and one for your cheap transit. Each customer's vlan is on both routers with vrrp preference set to the desired router for non-bgp customers. expensive transit customers have the ability to failover to the cheap router. you may or not want to allow the reverse to occur. - Kevin
participants (4)
-
Jack Bates -
Jay Ashworth -
Kevin Loch -
randal k