North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: ANS routing problems?
Greetings: Not sure when u saw a routing problem with ANS, but we hear the following routes from you via 3561: 195.238.192.0/19 195.218.64.0/19 195.197.0.0/16 195.74.0.0/19 these routes are being accepted by ANS : examples: kivneet:~> t 195.238.192.1 traceroute to 195.238.192.1 (195.238.192.1), 30 hops max, 40 byte packets 1 147.225.19.2 (147.225.19.2) 4 ms 1 ms 1 ms 2 f1-1.t128-0.Ann-Arbor.t3.ans.net (140.222.128.221) 2 ms 1 ms 1 ms 3 h12-1.t40-2.Cleveland.t3.ans.net (140.223.41.17) 9 ms 10 ms 15 ms 4 core3-fddi1-0.NorthRoyalton.cw.net (206.157.77.9) 21 ms 13 ms 13 ms 5 bordercore2.WestOrange.cw.net (166.48.6.1) 25 ms 30 ms 35 ms 6 telenordia-ab.WestOrange.cw.net (166.48.7.250) 132 ms 132 ms 134 ms 7 tni-sto-ri01-fe11-01.telenordia.se (194.213.91.14) 135 ms 142 ms 133 ms 8 tni-sto-rc25-fe05.telenordia.se (194.213.91.37) 142 ms 135 ms 134 ms 9 sto-atm-k26575.telenordia.se (194.213.64.182) 135 ms 136 ms 135 ms 10 c1r2.saunalahti.net (195.197.56.101) 142 ms 143 ms 141 ms 11 ^C^C kivneet:~> t 195.74.0.1 traceroute to 195.74.0.1 (195.74.0.1), 30 hops max, 40 byte packets 1 147.225.19.2 (147.225.19.2) 2 ms 1 ms 1 ms 2 f1-1.t128-0.Ann-Arbor.t3.ans.net (140.222.128.221) 2 ms 1 ms 1 ms 3 h12-1.t40-2.Cleveland.t3.ans.net (140.223.41.17) 9 ms 24 ms 9 ms 4 core3-fddi1-0.NorthRoyalton.cw.net (206.157.77.9) 24 ms 30 ms 23 ms 5 bordercore2.WestOrange.cw.net (166.48.6.1) 26 ms 34 ms 40 ms 6 telenordia-ab.WestOrange.cw.net (166.48.7.250) 159 ms 142 ms 146 ms 7 tni-sto-ri01-fe11-01.telenordia.se (194.213.91.14) 165 ms 155 ms 141 ms 8 tni-sto-rc25-fe05.telenordia.se (194.213.91.37) 138 ms 150 ms 135 ms 9 sto-atm-k26575.telenordia.se (194.213.64.182) 139 ms 142 ms 144 ms 10 c1r2.saunalahti.net (195.197.56.101) 147 ms 146 ms 144 ms 11 195.74.0.113 (195.74.0.113) 159 ms^C * Also if you are still experiencing problems or any other issues, please call the ANS NOC at (734) 214 7333, its a 24x7 NOC, with first and second level enginering support. Also you reach the noc via e-mail at: [email protected] i think i can reach you folks via e-mail :) kivneet:~> [email protected] Connecting to staff.sci.fi. via esmtp... 220 troi.sci.fi ESMTP Sendmail 8.9.1/8.9.1; Thu, 12 Nov 1998 01:07:43 +0200 (EET) >>> EHLO kivneet.aa.ans.net 250-troi.sci.fi Hello kivneet.aa.ans.net [147.225.19.46], pleased to meet you 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-ONEX 250-ETRN 250-XUSR 250 HELP >>> MAIL From:<[email protected]> SIZE=68 250 <[email protected]>... Sender ok >>> RCPT To:<[email protected]> 250 <[email protected]>... Recipient ok >>> DATA 354 Enter mail, end with "." on a line by itself >>> . 250 BAA03751 Message accepted for delivery [email protected] Sent (BAA03751 Message accepted for delivery) Closing connection to staff.sci.fi. >>> QUIT thank you ---------------------------------------------------------------------------- Gurmeet Singh Network Engineer [email protected] ANS - Access Network Engineering ---------------------------------------------------------------------------- On Wed, 11 Nov 1998 [email protected] wrote: > > Hello, > > We are having routing problems with ANS. They are not > accepting our routes from AS3561. They were excepting > them just fine about a week ago, but around last week > end our routes dissappeared from their AS. > > Current status, with AT&T as an example of a working routing status: > > route-views.oregon-ix.net>sh ip b r ^1673_.+_6667 > > route-views.oregon-ix.net>sh ip b r ^7018_.+_6667 > BGP table version is 4987768, local router ID is 198.32.162.100 > 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 > * 195.74.0.0/19 12.127.0.249 0 7018 3561 5556 6667 i > * 195.197.0.0/16 12.127.0.249 0 7018 3561 5556 6667 i > * 195.218.64.0/19 12.127.0.249 0 7018 3561 5556 6667 i > * 195.238.192.0/19 12.127.0.249 0 7018 3561 5556 6667 i > > Since all their NS and MX records are within their own network, > contacting them is rather impossible, so I turn to the NANO group > for helpful hints on how to resolve the problem. > > -- > Aleksi Suhonen > Network Development > Saunalahden Serveri Oy > AXU-RIPE >
|