I opened ticket with both 701 and 19094 when we did failover 2 weeks ago. Both 701 and 19094 insist that they just take the route and send it out to the rest of the world. And at that time, I thought it was RADB problem and agreed to close the tix. Now that RADB is fixed, I'm back at square one with more confusions :( I will open case with both 701 and 19094 soon. I am making sure that I'm not missing a smoking gun. --- "Christopher L. Morrow" <christopher.morrow@mci.com> wrote:
On Wed, 19 Oct 2005, Kyaw Khine wrote:
Hmmm.. When /24 gets to those ISP (direct connected to 19094/telcove), shouldn't they prefer 701/mci path?
depends on their relationship with 701 probably, and their internal decision criteria... they might filter or pref or... who knows :(
AS-PATH is longer through 19094 than through 701 ... provided that those ISP are accepting/receiving path from 701.
yup, looking at route-views.oregon-ix.net there seem to be plenty of paths (47 total reported)
Did you open a support ticket with 701?
--- "Christopher L. Morrow" <christopher.morrow@mci.com> wrote:
On Thu, 20 Oct 2005, Jon Lewis wrote:
On Wed, 19 Oct 2005, Kyaw Khine wrote:
routeviews is seeing both paths.
64.9.17.0/24 AS 33105
ISP-A = 701 :) ISP-B = 19094
You might talk to 701 about why for instance,
I see is your
prepended path via 19094 through 3356, 6461, 4323, and 19962.
Maybe 701 is only propogating your route to customers?
shouldn't be the case, it's not looking like it's tagged anything 'special'. :) the other folks might see telecove as a better path (assuming telecove/19094 is also multihomed to
all these
other asn's you have above)
__________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/
__________________________________ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/