I can only think of one way to do it, and it prevents your as from recieving
any sprint traffic.
If you are the customer on the far end, (the sbc customer) you could try
prepending sprint's as onto the advertisement you send to sbc... If they
don't filter that sort of thing then the sprint routers should ignore this
route on ingress, and you'll use sbc's other peers/transit.
Doing this would prevent you from recieving any traffic for this netblock
from sprints' as, so you'd want to advertise a larger aggregate route
without the sprint-as-prepend.
this is a kludge and should not be implemented only in extreme
circumstances.
-ejay
Subject: Help with forcing traffic to avoid Sprint?
From: "Colo Host" <ispcolohost@...>
Date: Mon, 07 Feb 2005 20:39:41 -0500
X-Message-Number: 1
Hi All, if you're familiar with Level 3 and/or Global Crossing, do you have
any suggestions on how one could get traffic to traverse the country
from the east on one of their networks on its way to AS 7132 (SBC/Pacbell)
in order to avoid crossing the country on AS 1239 (Sprint)? I'm a
customer of both of theirs and have a customer on SBC in California
and we're having really poor throughput and latency which appears to
be caused by Sprint. During the day it's extremely slow and a few of the
Sprint hops have very high latency, here's three examples of bad hops
as I force things out different providers on my side:
9 sl-bb22-sj-10-0.sprintlink.net (144.232.20.186) 75.943 ms 76.430 ms
76.447 ms
10 sl-bb25-sj-12-0.sprintlink.net (144.232.3.210) 238.981 ms 218.339 ms
211.598 ms
11 sl-bb23-ana-6-0.sprintlink.net (144.232.20.158) 77.479 ms 77.968 ms
77.485 ms
12 sl-bb25-sj-12-0.sprintlink.net (144.232.3.210) 78.981 ms 78.476 ms
78.487 ms
13 sl-bb23-ana-6-0.sprintlink.net (144.232.20.158) 297.452 ms 227.955 ms
247.473 ms
14 sl-bb21-ana-10-0.sprintlink.net (144.232.1.185) 82.481 ms 94.978 ms
79.473 ms
15 sl-st20-la-13-0.sprintlink.net (144.232.20.67) 98.478 ms 210.561 ms
243.475 ms
8 sl-bb23-rly-6-0.sprintlink.net (144.232.20.151) 31.351 ms 31.340 ms
31.242 ms
9 sl-bb27-rly-10-0.sprintlink.net (144.232.14.142) 230.592 ms 212.958 ms
227.975 ms
10 sl-bb22-rly-10-0.sprintlink.net (144.232.14.177) 31.356 ms 31.225 ms
31.484 ms
11 sl-bb22-sj-10-0.sprintlink.net (144.232.20.186) 77.980 ms 78.226 ms
77.858 ms
12 sl-bb25-sj-12-0.sprintlink.net (144.232.3.210) 143.086 ms 118.462 ms
189.726 ms
I've mailed Sprint but since I'm not a direct customer I just get the
standard
our network is functioning normally response. If I could get my traffic to
stay
on Level 3 to California and then dump it off to whoever, even Sprint, that
would
be much nicer, 50 ms versus 250 ms. I've tried to force my traffic out
Level 3
while also sending communities to Level 3 to prepending once or twice
towards
Sprint's AS only but the traffic still takes that route; maybe Sprint is
SBC's
only transit?
** ISPCON Fall 2004 - Santa Clara Convention Center **
** The ISP and WISP event - http://www.ispcon.com **
** Fill your brain. Meet the people. Join the industry gathering. **
________________________________________________________
---
You are currently subscribed to isp-bgp as: ejayhire@...
To unsubscribe send a blank email to
leave-isp-bgp-572285L@...
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
Copyright 2005 Jupitermedia Corporation All Rights Reserved.
