On Jan 31, 2007, at 5:10 AM, matthew zeier wrote:
Steve Gibbard wrote:
If you actually want to do this, you've got four choices:
- Policy route, as mentioned below.
- Get the customer their own connection to Cogent.
- Have a border router that only talks to Cogent and doesn't
receive full
Just curious, the customer wants to purchase cogent bandwidth through
you instead of going directly?
Wouldn't it be easier just to have Cogent run another connection to the
Meet Me Room in your facility and just extend it to their cage or rack?
This seems like a lot of over engineering to
Rick Kunkel wrote:
Hello all,
Being relatively new to the colocation business, we run into a fair number
of issues that we've never run into before. Got a new one today, and
although I can think of kludgey ways to accomplish what he wants, I'd
rather get some other ideas first...
We
Steve Gibbard wrote:
If you actually want to do this, you've got four choices:
- Policy route, as mentioned below.
- Get the customer their own connection to Cogent.
- Have a border router that only talks to Cogent and doesn't receive full
routes from your core, and connect the customer
another way is tunnel them to a border router that
interfaces with Cogent and deal with it at the border
router. QinQ tunnel, GRE, IPSec, or whatever tunnel
type you can support and will service the type of
traffic your customer needs (L2 or L3). If you have
multiple Cogent connections you
We had that same problem and ended up doing it exactly as below, with
limited BGP announcements and policy routing all over. The customer also
demanded high-bandwidth at low cost, without regard to how good the actual
bandwidth was. It was, as you say, graceless.
Luckily we convinced them to
If you actually want to do this, you've got four choices:
- Policy route, as mentioned below.
- Get the customer their own connection to Cogent.
- Have a border router that only talks to Cogent and doesn't receive full
routes from your core, and connect the customer directly to that.
- Do
