With all the aquisitions going on, would't it be strange if a major NSP player started announcing through another major NSP. I don't know about you, but _I_ find that strange. BGP routing table entry for 207.121.184.0/21, version 3907425 Paths: (2 available, best #2, advertised over IBGP) 701 199 192.157.69.60 (metric 17) from 165.117.1.17 (165.117.1.120) Origin IGP, metric 2000000000, localpref 100, valid, internal Community: 2548:666 Originator : 165.117.1.120, Cluster list: 0.38.227.186, 165.117.1.15 701 199 192.41.177.248 from 192.41.177.248 (137.39.3.57) Origin IGP, metric 28, localpref 100, valid, external, best Community: 2548:668 Type escape sequence to abort. Tracing the route to web180b.bbnplanet.com (207.121.185.180) 1 * br1.tco1.alter.net (192.41.177.248) [AS 1800] 4 msec 252 msec 2 431.atm10-0.cr1.tco1.alter.net (137.39.13.14) [AS 701] 236 msec 252 msec 256 msec 3 189.Hssi4-0.CR1.BOS1.Alter.Net (137.39.69.74) [AS 701] 256 msec 256 msec 244 msec 4 311.atm1-0.gw1.bos1.alter.net (137.39.13.233) [AS 701] 284 msec 512 msec 252 msec 5 bbn1-gw.customer.ALTER.NET (157.130.3.106) [AS 701] 260 msec 260 msec 276 ms ec 6 cambridge1-colo2.bbnplanet.net (4.0.2.241) [AS 1] 284 msec 272 msec 260 msec 7 web180b.bbnplanet.com (207.121.185.180) [AS 199] 288 msec * 36 msec
Ya.. I noticed that a couple of days ago. I sent mail to noc, peering, ops etc. at BBNplanet but I haven't gotten a reply as to what is going on over there. You would think in peering with BBN you would get 199 behind AS1 somewhere.. but I only get one route with the ASPath of 1_199_ the rest come from UUnet. core1-Col#sho ip bgp regex _1_199_ Network Next Hop Metric LocPrf Weight Path * i205.159.212.0 198.32.184.19 940 100 0 1 199 i * 198.32.130.39 70 0 5646 1 199 i *>i 192.41.177.2 560 100 0 1 199 i core1-Col#sho ip bgp regex _199_ BGP table version is 22368414, local router ID is 206.183.241.252 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 199.92.136.0 198.32.130.39 70 0 5646 701 199 i * i 206.183.239.142 70 0 3847 701 199 i *> 199.94.217.0 198.32.130.39 70 0 5646 701 199 i * i 206.183.239.142 70 0 3847 701 199 i * i205.159.212.0 198.32.184.19 940 100 0 1 199 i * 198.32.130.39 70 0 5646 1 199 i *>i 192.41.177.2 560 100 0 1 199 i *> 205.181.112.0/22 198.32.130.39 70 0 5646 701 199 i * i 206.183.239.142 70 0 3847 701 199 i *> 207.121.184.0/21 198.32.130.39 70 0 5646 701 199 i * i 206.183.239.142 70 0 3847 701 199 i T..S On Tue, 9 Sep 1997, cameo wrote:
With all the aquisitions going on, would't it be strange if a major NSP player started announcing through another major NSP. I don't know about you, but _I_ find that strange.
BGP routing table entry for 207.121.184.0/21, version 3907425 Paths: (2 available, best #2, advertised over IBGP) 701 199 192.157.69.60 (metric 17) from 165.117.1.17 (165.117.1.120) Origin IGP, metric 2000000000, localpref 100, valid, internal Community: 2548:666 Originator : 165.117.1.120, Cluster list: 0.38.227.186, 165.117.1.15 701 199 192.41.177.248 from 192.41.177.248 (137.39.3.57) Origin IGP, metric 28, localpref 100, valid, external, best Community: 2548:668
Type escape sequence to abort. Tracing the route to web180b.bbnplanet.com (207.121.185.180)
1 * br1.tco1.alter.net (192.41.177.248) [AS 1800] 4 msec 252 msec 2 431.atm10-0.cr1.tco1.alter.net (137.39.13.14) [AS 701] 236 msec 252 msec 256 msec 3 189.Hssi4-0.CR1.BOS1.Alter.Net (137.39.69.74) [AS 701] 256 msec 256 msec 244 msec 4 311.atm1-0.gw1.bos1.alter.net (137.39.13.233) [AS 701] 284 msec 512 msec 252 msec 5 bbn1-gw.customer.ALTER.NET (157.130.3.106) [AS 701] 260 msec 260 msec 276 ms ec 6 cambridge1-colo2.bbnplanet.net (4.0.2.241) [AS 1] 284 msec 272 msec 260 msec 7 web180b.bbnplanet.com (207.121.185.180) [AS 199] 288 msec * 36 msec
participants (2)
-
cameo -
Todd R. Stroup