RE: Problem with routing from AS15694 to some US networks
From the output there, it looks like that is the chap that is aggregating
the /20 that encompasses your block. How large is your ip block? -----Original Message----- From: Adam Obszynski [mailto:awo@atm.com.pl] Sent: Thursday, August 09, 2001 11:55 AM To: nanog@merit.edu Subject: Problem with routing from AS15694 to some US networks Hello NONAG! I'm speaking from Poland, and would like to ask you about help in finding some kind of contact to ZephyrTele NOC/NMC becouse they absent in irrd and they recorc in arin is very simple. They anounce our network without BGP session established to our AS 15694, here is sample output which i found after some time of problems with US IP regions (the same hapends in direction to AOL.net but cannot find his looking-glass or route server) Next issue: is there any good way to avoid those situations ? Everybody could redistribute static "sh*s" to BGP and spread it around.. here is sample output from my small investigation: telnet ner-routes.bbnplanet.net [..] ner-routes>trace 217.17.34.10 Type escape sequence to abort. Tracing the route to 217.17.34.10 1 e0-1-5.burlma1-ops1.bbnplanet.net (4.2.34.162) 144 msec 8 msec 240 msec 2 s7-0-4.bstnma1-cr7.bbnplanet.net (4.0.3.181) 4 msec 4 msec 4 msec 3 p5-0.bstnma1-ba2.bbnplanet.net (4.24.4.225) 4 msec 4 msec 4 msec 4 p7-0.bstnma1-br2.bbnplanet.net (4.24.7.121) 4 msec 4 msec 4 msec 5 p2-0.bstnma1-br1.bbnplanet.net (4.24.7.113) 0 msec 4 msec 4 msec 6 p9-0.nycmny1-nbr2.bbnplanet.net (4.24.6.50) 12 msec 12 msec 8 msec 7 p15-0.nycmny1-nbr1.bbnplanet.net (4.24.10.209) 12 msec 12 msec 8 msec 8 p1-0.nycmny1-cr9.bbnplanet.net (4.24.8.162) 8 msec 12 msec 12 msec 9 h0.zephyrtel.bbnplanet.net (4.24.188.50) 12 msec 12 msec 12 msec 10 gr1-ny.ip.zephyrtele.com (12.35.239.4) 8 msec 12 msec 12 msec 11 * * * 12 * * * 13 * * * 14 * * * 15 * 12.124.183.37 !A * ner-routes>sh ip bgp reg _15694$ BGP table version is 1340345, local router ID is 4.2.34.165 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 * i217.17.32.0/20 4.24.188.50 100 0 16499 7018 1239 1755 8246 15694 i ner-routes>sh ip bg 217.17.32.1 BGP routing table entry for 217.17.32.0/20, version 0 Paths: (1 available, no best path) 16499 7018 1239 1755 8246 15694, (aggregated by 15694 217.17.34.1) 4.24.188.50 (inaccessible) from 4.24.0.48 (4.24.1.60) Origin IGP, localpref 100, valid, internal, atomic-aggregate Community: 1:1000 Originator : 4.24.0.225, Cluster list: 4.24.0.48, 4.24.0.131 -- ATM S.A., ul. Grochowska 21a, 04-186 Warszawa +48-607-608701, +48-22-5156418, http://www.atm.com.pl/
Witaj Ejay,
From the output there, it looks like that is the chap that is aggregating the /20 that encompasses your block. How large is your ip block?
in "real world" it is /20 too and some other tranisit prefixes as addition to our paths
Network Next Hop Metric LocPrf Weight Path * i217.17.32.0/20 4.24.188.50 100 0 16499 7018 1239 1755 8246 15694 i
-- ATM S.A., ul. Grochowska 21a, 04-186 Warszawa +48-607-608701, +48-22-5156418, http://www.atm.com.pl/
Adam, It looks like they are hearing and propagating your route. route-views.oregon-ix.net shows that your network is being heard by Genuity (AS1) via Zephyr Telecommunications (AS16499), but they are not getting your traffic through. 1 16499 7018 1239 1755 8246 15694 You still need to contact them, but they are propagating, not originating your route. (I'm guessing that they are not a preferred transit provider from AT&T to Genuity...) -Steve On Thu, 9 Aug 2001, Adam Obszynski wrote:
Witaj Ejay,
From the output there, it looks like that is the chap that is aggregating the /20 that encompasses your block. How large is your ip block?
in "real world" it is /20 too and some other tranisit prefixes as addition to our paths
Network Next Hop Metric LocPrf Weight Path * i217.17.32.0/20 4.24.188.50 100 0 16499 7018 1239 1755 8246 15694 i
participants (3)
-
Adam Obszynski
-
Hire, Ejay
-
Steve Schaefer