[OCCAID] New path to KAME

[Scott J. Clifford]

On Fri, Jan 28, 2005 at 01:40:20AM -0500, James wrote:
> On Fri, Jan 28, 2005 at 12:21:59AM -0600, Michael Nicks wrote:
> > Seems there is a new path to KAME which is no longer taking ISC.
> > Any reason as to why? Thanks :)
> > 
> > $ traceroute6 www.kame.net
> > traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:4830:2014:1::2, 64 hops max, 12 byte packets
> >  1  2001:4830:2014:1::1 (2001:4830:2014:1::1)  0.525 ms  0.221 ms  0.165 ms
> >  2  11.ip-0-1-0.cr1.ord1.us.occaid.net (2001:4830:e5::1)  13.484 ms  12.234 ms  12.568 ms
> >  3  67.gr-0-1-0.cr1.ewr2.us.occaid.net (2001:4830:ff:1301::1)  33.959 ms  33.835 ms  34.145 ms
> >  4  2001:5014:100:1::1 (2001:5014:100:1::1)  35.860 ms  35.463 ms  36.620 ms
> >  5  so-0-0-0-ecr1.sfo.cw.net (2001:5000:0:2f::2)  111.757 ms  111.717 ms  111.916 ms
> >  6  so-0-0-0-zpr1.pal.cw.net (2001:5000:0:31::2)  114.141 ms  115.235 ms  113.981 ms
> >  7  3ffe:80a::b2 (3ffe:80a::b2)  115.090 ms  114.645 ms  114.992 ms
> >  8  hitachi1.otemachi.wide.ad.jp (2001:200:0:4401::3)  214.476 ms  214.135 ms  214.899 ms
> >  9  pc3.yagami.wide.ad.jp (2001:200:0:1c04::1000:2000)  228.609 ms  228.187 ms  228.941 ms
> > 10  gr2000.k2.wide.ad.jp (2001:200:0:4819::2000:1)  230.541 ms  232.280 ms  244.243 ms
> > 11  orange.kame.net (2001:200:0:8002:203:47ff:fea5:3085)  217.131 ms  220.013 ms  216.455 ms
> > 
> > 
> 
> Thanks for the traceroute. The problem appears to be a product of hot-potato.
> We do not peer with ISC per se, but they are our native upstream transit
> provider out in the west coast. So local preference is set to 100 like other
> transitnets. While routes from west coast takes ISC due to ISC being a closer
> exit, routes in Chicago and Dallas and the whole eastern seaboard are
> moving toward EWR first before exiting, as EWR is closer to exit than SFO2..
> 
> I have set a higher LP* at SFO2 for ^3557(_2500)+(_7500)*$ so paths to kame
> should vastly improve for users in central US (Chicago/Dallas/KCM, etc).
> You should be able to view it under 30071:30071 (External Traffic Engineering)
> community-tagged routes.
> 
> Let me know if problem still persists or if all is better..

Sorry if I'm hijacking your thread.. But speaking of 30071:30071 community routes, I
have a question.

2001:770::/35       *[BGP/170] 21:29:29, MED 0, localpref 100, from 3ffe:401d:f00::1
                      AS path: 30071 1273 3549 1213 1213 1213 1213 I
                    > to 2001:468:d01:3c::1 via fe-0/0/0.0

Any reason to why we are doing this? We have transit from 3549 where HEAnet is
downstream of it. AFAIK, 3549 does not run a low performance network that are
seen in 30071:6969 routes.

Thanks!!

Scott.