[c-nsp] Virtual Interface to the Internet

[Oliver Boehmer (oboehmer)]

Ray Burkholder <> wrote on Friday, October 03, 2008 5:30 AM:

> I have a customer with two sites.  Site 1 connects to Router A.  Site
> 2 connects to Router B.  We have an internet connection on Router C. 
> Router A connects to Router C and Router B connects to Router C.
> 
> The customer wishes to be billed for a total of X amount of bandwidth,
> regardless of whether it comes from Site 1 or Site 2 or both.
> 
> Is there some sort of multipoint virtual circuit I can engineer to
> aggregate two sites, rate-shape or police at Router C, and get them
> to the internet? VRF's or L2TPV3 come to mind.  But how to connect
> them with a virtual interface on Router C?  Use a loopback or ..... ?
 
Hmm, so your requirement is to limit (shape/police) the amount of BW the
customer can use towards the Internet, and impose no limits for Site
A<-->B traffic? If that's the case, I guess there is no real nice (and
scalable) solution. 

You could create a MPLS-VPN between A, B and C and create a physical
loop at router C connecting this VRF/VPN to the global Routing table and
shape/police on this interface. Traffic between the customer sites A and
B will not be affected, only everything leaving the egress/looped
interface on Router C.
But I would not do this, especially if you're offering full routes to
the customer as you would need to carry the full routes in the VPN as
well...

"QoS Policy Propagation via BGP" could actually be a nice solution,
however this is not supported on all platforms. 

I guess there are "non-technical" approaches as well, i.e. account the
traffic and have them pay a premium if they exceed the contracted
rate/volume..

	oli