Oddities in a bad route announcement
Michael Dean
mdean at UU.NET
Sun May 30 01:24:51 UTC 1999
Sean,
We are doing this per the customer's request...
GW2.DCA3#sh ip bgp 192.104.54.3
BGP routing table entry for 192.104.54.0/24, version 31205137
Paths: (1 available, best #1, not advertised to EBGP peer, advertised over IBGP, EBGP)
7046
157.130.39.150 from 157.130.39.150 (192.104.54.253)
Origin IGP, metric 10, localpref 100, valid, external, best
Community: no-export <-----------------------------------------------
GW2.DCA3#sh ip rou 157.130.39.150
Routing entry for 157.130.39.148/30
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via bgp 65488
Advertised by bgp 65488 route-map connected-bgp
Routing Descriptor Blocks:
* directly connected, via Serial1/1/1.500
Route metric is 0, traffic share count is 1
Sean Donelan said:
>
>
> mdl at equinox.shaysnet.COM (M. David Leonard) writes:
> > It looks OK from here right now:
>
> It seems pretty much hosed everywhere outside of UUNET. Now there
> seems to be no route being announced outside to anyone.
>
> paix1>show ip bgp 192.104.54.3
> % Network not in table
> paix1>exit
> --
> Sean Donelan, Data Research Associates, Inc, St. Louis, MO
> Affiliation given for identification not representation
>
>
More information about the NANOG
mailing list