the answer to the question is that uunet prefers the sprint path
internally over its own customer path. uunet does not (by default)
localpref customers higher, so the decision is made at the as-path length
step. therefore, uunet would not be announcing a path to a peer.
try setting one of uunet's communities which corresponds to a higher
internal localpref.
BR
On Tue, 19 Oct 1999, Vijay Gill wrote:
> On Tue, 19 Oct 1999, Eric J Merkel wrote:
>
> > >As for the original poster, how do you know your routes disappear? Are you
> > >using some sort of looking glass? What may be happening is that if you
> > >prepend enough times to UUNET, the path becomes unattractive, even
> > >internally, and all traffic starts to go over sprint. Since the UUNET
> > >path is no longer the best path for almost any router, and only the best
> > >path is propagated further, it may lead to a disappearance of the uunet
> > >path from looking glasses.
>
> >
> > Well, the routes with AS701 in them completely vanish from all looking
> > glasses. I also did a traceroute from UUNET trace server and it PREFERRED
> > Sprint over itself(UUNET) and the traffic incoming dropped to 0 so I am
> > fairly certain that the route were completely gone.
>
> That is the point. See my original paragraph above.
>
> /vijay
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:06 EDT