[11653] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: UUNET - PSI - ?

daemon@ATHENA.MIT.EDU (Andrew Bangs)
Thu Aug 7 10:59:14 1997

To: jamie@intuition.iagnet.net
Date: Thu, 7 Aug 1997 15:46:22 +0100 (BST)
From: Andrew Bangs <andrewb@demon.net>
Cc: nanog@merit.edu
In-Reply-To: <199708071351.JAA22317@intuition.iagnet.net> from "Jamie Rishaw" at Aug 7, 97 09:51:15 am

jamie g.k. rishaw wrote:
> 
> Something wrong with this?
> 
> 
> 
> > sho ip bgp 137.39.0.0 255.255.0.0
> BGP routing table entry for 137.39.0.0/16, version 533944
> Paths: (2 available, best #2, advertised over IBGP)
>   174
>     192.41.177.245 from 192.41.177.245
>       Origin IGP, metric 30, localpref 100, valid, external
>       Community: 2548:668
>   701
>     198.32.186.248 from 198.32.186.248 (137.39.3.57)
>       Origin IGP, metric 2, localpref 100, valid, external, best
>       Community: 2548:668
> 
> *174*?
> 

Hmm. That route looks ok to us where we learn it from PSI in New York:
100 BGP          137.39/16 195.11.50.2     (2529) 174 701 IGP 


However, something is certainly odd somewhere:

GateD-beech.router.demon.net> show ip routes
100 IP radix tree: 94528 nodes, 49200 routes
GateD-beech.router.demon.net> 

We have a few thousand more routes than normal, including this 
more specific route that includes 'www.uu.net' that we see via
EBONE->ICM->Sprint but not via PSI or MCI.

GateD-beech.router.demon.net> show ip walkup 199.170.0.30
100 BGP         199.170/24 194.159.252.88  (2529) 5417 1755 1800 1239 701 IGP 
100 BGP         199.170/15 195.11.50.2     (2529) 174 701 IGP


Anyone else seeing weirdness ?


 Regards,
 Andrew
-- 
Andrew Bangs, Network Engineering Team Leader, Demon Internet Ltd
andrewb@demon.net    http://www.demon.net/   http://www.demon.nl/

home help back first fref pref prev next nref lref last post