nanog mailing list archives
Re: BBN issues
From: Danny McPherson <danny () qwest net>
Date: Mon, 13 Dec 1999 17:14:50 -0700
You don't see the NY -> Cali -> NY path? That is a bad thing (tm).
In the first traceroute it did initially seem interesting, although my presumption was that Sprint likely wasn't leaking routes (or providing transit?) "everywhere", and probably only via that specific path, as demonstrated. Another observation to that regard is that the [leaked?] prefix was presumably a more specific, else [theoretically], Genuity would have selected the shorter AS path .. although BBN/GTEI may perhaps be providing that transit via there AS, which would even things out from a path vector perspective. (The reverse path seems somewhat reasonable considering BBN and Genuity are still separate ASs with distinct network and interconnection topologies. I do still see potential brokenness wrt route leakage and the like, so either Sprint is still leaking routes or GTEI is attempting to offload (via a psuedo transit connection) some of that Genuity hosting traffic elsewhere... Of course, I'd really suggest now that we avoid dicussing this specifically on the list and leave the problem resolution to the folks that can actually fix it/them, if they actually exist. -danny
Current thread:
- BBN issues Charles Sprickman (Dec 13)
- Re: BBN issues Deepak Jain (Dec 13)
- <Possible follow-ups>
- Re: BBN issues Danny McPherson (Dec 13)
- Re: BBN issues Charles Sprickman (Dec 13)
- Re: BBN issues Alex Rubenstein (Dec 13)
- Re: BBN issues Danny McPherson (Dec 13)