- Test - lists.nanog.org

RE: Cisco vs Adtran vs Juniper
by Paul Stewart 21 Jul '08

21 Jul '08

Thanks guys so far for the responses.... Adtran has a 5 year warranty and support for free as of today - I'm not aware of this changing but we've had a number of other companies change that policy in the past couple of years after purchasing a LOT of gear from them (Motorola, Redline come to mind among others). Cisco has "lifetime hardware warranty" on some of their gear but nobody has ever been able to tell me what that *really* means and how you would ever get it covered if you did NOT have Smartnet coverage...;) UC500's - nice boxes ... pure cost issues around this one. You need to add a 24 port switch if you want some form of density at additional cost... makes it 3X the Adtran price so gets a lot of attention here... Keep it coming guys.. appreciate it... Paul -----Original Message----- From: Smith, Steve B [mailto:ss4414@att.com] Sent: Friday, July 18, 2008 11:44 AM To: Chris Heighway; Paul Stewart Cc: nanog Subject: RE: Cisco vs Adtran vs Juniper And remember Adtran has a 5 year warranty and support for free. -----Original Message----- From: Chris Heighway [mailto:heighway@gmail.com] Sent: Friday, July 18, 2008 10:22 AM To: Paul Stewart Cc: nanog Subject: Re: Cisco vs Adtran vs Juniper On your last note Cisco also offers a all-in-one with all the features you talked about and more. They are called UC500's. _Chris On Fri, Jul 18, 2008 at 10:18 AM, Paul Stewart <pstewart(a)nexicomgroup.net> wrote: > Hi there.. > > I'm looking for some constructive feedback on **real world** > experiences please... > > We're primarily a Cisco shop today - our core and distribution are all > Cisco driven and will continue to be (won't change that so not worth > discussing today). > > My question is oriented towards two other markets primarily: > > Security Devices > Remote Office/Customer Site Devices > > Let me elaborate a bit more... > > Security - today, we've been deploying Cisco ASA boxes (was PIX before > that) with pretty good success. However, in comparison to Juniper the > Cisco boxes are *really* expensive - at least to us anyways. Juniper > has nice products so I'm looking at proposing a solution internally to > move towards the Juniper security appliances. Feedback from folks on > them vs Cisco ASA?? > > Remote Office/Customer Site Devices - today, we do a lot of "managed > routers" to customer sites. Again, cost driven, I'm being pushed > towards looking at Adtran devices for customer sites that we maintain. > I have nothing against Adtran but haven't viewed them to date as being > in the same "arena" as Cisco/Juniper etc.. these routers are mainly > providing basic firewalling/NAT and some very small VPN activity at > times. > > To take this one step further, some of our voice folks are really > enjoying the Adtran boxes as it offers an "all in one solution" which > is a router, firewall, "voice" box (many options - PRI handoff, T1, > FXS/FXO) and in some of their boxes 24 POE switch ports as well. This > is kinda cool I'll admit but the approach in the past has been to drop > in a Cisco router, Adtran for voice applications, and then Cisco POE > switches if required. This is very costly compared to Adtran's all in > one approach.... so am I being stubborn on this or is the Adtran > products in this case in the same league?? I had some terrible track > record with Adtran a number of years ago so my back gets up when their > name is mentioned...;) > > Any feedback would be very appreciated - we're going to have meetings > internally in the next while to decide which product lines fit with > which service offerings the best.... > > Thanks, > > Paul > > > > > > > ---------------------------------------------------------------------- > ------ > > "The information transmitted is intended only for the person or entity > to which it is addressed and contains confidential and/or privileged material. > If you received this in error, please contact the sender immediately > and then destroy this transmission, including all attachments, without > copying, distributing or disclosing same. Thank you." > > ***** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA622

3 3

Re: Savvis Related Routing Issue
by Brendan Mannella 20 Jul '08

20 Jul '08

My setup is fairly simple, i dont really know where to look... M7i border routers, one with a Fast-E to Mizma and GLBX and one with Sprint Fast-E, they both run IBGP with BI4k (jetCore), out to L2s. I have seen this issue across both the Mzima link and the GLBX link, the only common thing with them is they are on the same router and 4 port PIC card, and they both travel via a L2 MPLS link to Ashburn, VA via the same transport provider. Brendan ----- Original Message ----- From: "Daniel Senie" <dts(a)senie.com> To: "Brendan Mannella" <bmannella(a)teraswitch.com> Sent: Saturday, July 19, 2008 10:53:12 PM GMT -05:00 US/Canada Eastern Subject: Re: Savvis Related Routing Issue The fact that changing the target IP address by one changes things makes me think you may have a multi-wire trunking setup between some Ethernet switches, and that trunking is spreading load based on hashing IP addresses. Look close to home, or in your link to your upstream as likely places for this. Might not be your issue, but I've seen this kind of thing before, and found the issue in switch-to-switch trunking or the equivalent in multi-circuit load balancing between routers (e.g. multiple T1's between two routers, where ML-PPP should have been used, and wasn't). At 10:36 PM 7/19/2008, you wrote: >Hello, > >I am seeing a really weird routing issue. I have customers who are >having trouble connecting to hosts on the internet. The common item >seems to be Savvis. > >orange:~>traceroute mail.tecumsehherald.com >traceroute to mail.tecumsehherald.com (64.14.74.42) >1 204.16.245.97 (204.16.245.97) 0.580 ms 0.800 ms 1.020 ms >2 204.16.241.225 (204.16.241.225) 0.496 ms 0.478 ms 0.699 ms >3 64.209.102.233 (64.209.102.233) 7.177 ms 7.420 ms 7.417 ms >4 te1-3-10g.ar2.DCA3.gblx.net (67.17.108.145) 7.630 ms 7.870 ms 8.105 ms >5 * * * >6 * * * > >Hop 5 is a Savvis router. > >Now if i go to Global Crossings looking glass and run a trace from >their DC router to the same host, it makes it. > >1 64.214.14.161 (64.214.14.161) 0.457 ms 0.429 ms >2 te7-1-10G.ar2.DCA3.gblx.net (67.17.109.34) 1.401 ms 1.658 ms >3 savvis-1.ar2.DCA3.gblx.net (64.212.107.26) 1.567 ms 1.339 ms >4 ber1-tenge-2-1.virginiaequinix.savvis.net (204.70.193.6) 1.586 ms 1.511 ms >5 cr1-tengig0-7-2-0.washington.savvis.net (204.70.197.242) 2.367 ms 2.547 ms >6 cr1-pos-0-0-0-0.boston.savvis.net (204.70.193.177) 15.163 ms 15.836 ms >7 hr1-pos-1-0-0.Waltham2bo2.savvis.net (208.172.51.66) 11.702 ms 11.780 ms >8 csr1-ve242.Waltham1bo1.savvis.net (64.14.70.19) 12.202 ms 11.728 ms >9 64.14.67.130 (64.14.67.130) 11.570 ms 11.592 ms >10 ns2.s426.sureserver.com (64.14.74.42) 11.811 ms 11.927 ms > >Now to top it all of, if i run a trace to the 64.14.74.41, instead >of 64.14.74.42 it works... > >agg1.pit#traceroute 64.14.74.41 >Type Control-c to abort >Tracing the route to IP node 64.14.74.41 from 1 to 30 hops > >1 <1 ms <1 ms <1 ms 204.16.241.225 >2 7 ms 7 ms 6 ms 64.209.102.233 >3 7 ms 6 ms 6 ms te1-3-10g.ar2.DCA3.gblx.net [67.17.108.145] >4 6 ms 6 ms 6 ms savvis-1.ar2.DCA3.gblx.net [64.212.107.26] >5 45 ms 6 ms 7 ms ber1-tenge-2-1.virginiaequinix.savvis.net [204.70.193.6] >6 14 ms 14 ms 15 ms cr1-tengig0-7-2-0.washington.savvis.net [204.70.197.242] >7 21 ms 22 ms 23 ms cr1-pos-0-0-0-0.boston.savvis.net [204.70.193.177] >8 20 ms 19 ms 20 ms hr1-pos-1-0-0.Waltham2bo2.savvis.net [208.172.51.66] >9 19 ms 20 ms 19 ms csr1-ve242.Waltham1bo1.savvis.net [64.14.70.19] >10 20 ms 19 ms 19 ms 64.14.67.130 >11 20 ms 20 ms 20 ms s426.sureserver.com [64.14.74.41] > >Does anyone have and ideas? > >Thanks, > >Brendan

1 0

Re: Ubiquity<->Mzima routing loop
by Guy_Shields＠Stream.Com 20 Jul '08

20 Jul '08

No, a true routing loop will transit several hops and end back up at the same routers. A bouncing route between 2 routers is usually a directly connected route on an interface that goes down thereby "pulling" the route with out a nail down route it will send unkown route back out its default gateway. ----- Original Message ----- From: "Paul Wall" [pauldotwall(a)gmail.com] Sent: 07/18/2008 10:25 PM AST To: Guy Shields Cc: nanog <nanog(a)merit.edu> Subject: Re: Ubiquity<->Mzima routing loop Isn't that what a routing loop is, when it loops back out to the transit/interface from which it entered? Paul On Fri, Jul 18, 2008 at 7:07 PM, <Guy_Shields(a)stream.com> wrote: > This is not a routing loop. It is simply a route that was not tied down via a static route to NULL with a weight of 254. > > > ----- Original Message ----- > From: "Paul Wall" [pauldotwall(a)gmail.com] > Sent: 07/18/2008 06:57 PM AST > To: "William Pitcock" <nenolod(a)systeminplace.net> > Cc: nanog(a)merit.edu > Subject: Re: Ubiquity<->Mzima routing loop > > > > I'd like to rip on Mzima as much as the next guy, but I'm not sure how > they could "fix" this routing loop, shy of some creative ACLs. > > You should try contacting Ubiquity, as this traceroute looks like an > issue on their (Mzima's customer's) side. > > Paul Wall > > On Fri, Jul 18, 2008 at 3:27 PM, William Pitcock > <nenolod(a)systeminplace.net> wrote: >> Hi, >> >> Can someone at Ubiquity or Mzima fix this routing loop: >> >> traceroute to hg.atheme.org (72.37.225.164), 30 hops max, 40 byte >> packets >> 1 64.62.134.193 12.402 ms 12.370 ms 12.363 ms >> 2 ge5-0.cr01.ord01.mzima.net (206.223.119.62) 16.003 ms 15.985 ms >> 15.964 ms >> 3 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.139 ms 14.858 >> ms 14.838 ms >> 4 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.875 ms 15.854 ms >> 16.497 ms >> 5 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.747 ms 14.763 >> ms 14.745 ms >> 6 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 16.405 ms 8.773 ms >> 8.758 ms >> 7 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 9.831 ms * * >> 8 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.417 ms 4.403 ms >> 4.381 ms >> 9 * * * >> 10 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.293 ms 4.933 ms >> 4.914 ms >> 11 * * * >> 12 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.527 ms 14.526 ms >> 14.438 ms >> 13 * * * >> 14 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.352 ms 14.335 ms >> 3.770 ms >> 15 * * * >> 16 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.684 ms 13.897 ms >> 13.897 ms >> 17 * * * >> 18 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.599 ms 8.581 ms >> 8.668 ms >> 19 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.246 ms >> 20 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.584 ms 8.565 ms >> 8.545 ms >> 21 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.119 ms >> 22 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.456 ms 8.931 ms >> 8.913 ms >> 23 * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 6.049 ms * >> 24 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.862 ms 15.754 ms >> 15.736 ms >> 25 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 7.132 ms * 7.092 >> ms >> 26 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.293 ms 15.998 ms >> 10.752 ms >> 27 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 5.353 ms 5.336 >> ms * >> 28 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.800 ms 3.854 ms >> 3.823 ms >> 29 * * * >> 30 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.228 ms 4.426 ms >> 13.019 ms >> >> Thanks! >> >> William >> >> >> > >

2 1

Savvis Related Routing Issue
by Brendan Mannella 20 Jul '08

20 Jul '08

Hello, I am seeing a really weird routing issue. I have customers who are having trouble connecting to hosts on the internet. The common item seems to be Savvis. orange:~>traceroute mail.tecumsehherald.com traceroute to mail.tecumsehherald.com (64.14.74.42) 1 204.16.245.97 (204.16.245.97) 0.580 ms 0.800 ms 1.020 ms 2 204.16.241.225 (204.16.241.225) 0.496 ms 0.478 ms 0.699 ms 3 64.209.102.233 (64.209.102.233) 7.177 ms 7.420 ms 7.417 ms 4 te1-3-10g.ar2.DCA3.gblx.net (67.17.108.145) 7.630 ms 7.870 ms 8.105 ms 5 * * * 6 * * * Hop 5 is a Savvis router. Now if i go to Global Crossings looking glass and run a trace from their DC router to the same host, it makes it. 1 64.214.14.161 (64.214.14.161) 0.457 ms 0.429 ms 2 te7-1-10G.ar2.DCA3.gblx.net (67.17.109.34) 1.401 ms 1.658 ms 3 savvis-1.ar2.DCA3.gblx.net (64.212.107.26) 1.567 ms 1.339 ms 4 ber1-tenge-2-1.virginiaequinix.savvis.net (204.70.193.6) 1.586 ms 1.511 ms 5 cr1-tengig0-7-2-0.washington.savvis.net (204.70.197.242) 2.367 ms 2.547 ms 6 cr1-pos-0-0-0-0.boston.savvis.net (204.70.193.177) 15.163 ms 15.836 ms 7 hr1-pos-1-0-0.Waltham2bo2.savvis.net (208.172.51.66) 11.702 ms 11.780 ms 8 csr1-ve242.Waltham1bo1.savvis.net (64.14.70.19) 12.202 ms 11.728 ms 9 64.14.67.130 (64.14.67.130) 11.570 ms 11.592 ms 10 ns2.s426.sureserver.com (64.14.74.42) 11.811 ms 11.927 ms Now to top it all of, if i run a trace to the 64.14.74.41, instead of 64.14.74.42 it works... agg1.pit#traceroute 64.14.74.41 Type Control-c to abort Tracing the route to IP node 64.14.74.41 from 1 to 30 hops 1 <1 ms <1 ms <1 ms 204.16.241.225 2 7 ms 7 ms 6 ms 64.209.102.233 3 7 ms 6 ms 6 ms te1-3-10g.ar2.DCA3.gblx.net [67.17.108.145] 4 6 ms 6 ms 6 ms savvis-1.ar2.DCA3.gblx.net [64.212.107.26] 5 45 ms 6 ms 7 ms ber1-tenge-2-1.virginiaequinix.savvis.net [204.70.193.6] 6 14 ms 14 ms 15 ms cr1-tengig0-7-2-0.washington.savvis.net [204.70.197.242] 7 21 ms 22 ms 23 ms cr1-pos-0-0-0-0.boston.savvis.net [204.70.193.177] 8 20 ms 19 ms 20 ms hr1-pos-1-0-0.Waltham2bo2.savvis.net [208.172.51.66] 9 19 ms 20 ms 19 ms csr1-ve242.Waltham1bo1.savvis.net [64.14.70.19] 10 20 ms 19 ms 19 ms 64.14.67.130 11 20 ms 20 ms 20 ms s426.sureserver.com [64.14.74.41] Does anyone have and ideas? Thanks, Brendan

1 0

Bogon Filter Update Request
by Stan Barber 19 Jul '08

19 Jul '08

Greetings NANOGers, Yes, I know it has been many years since I have been more than a lurker here on the NANOG list. It is gratifying to see the group continue to facilitate discussions among those that "get it done" in keeping the Internet up and running. Recently, I have moved back into a more operational role and I hope to renew my involvement here as I settle back in. So, to the point of my note: Bogon filter updates! I want to tell you that I am very appreciative of those operators out there that follow the changes in status of IP space and keep there BOGON filters updated. Unfortunately, it appears that there are many that are not doing this regularly. I have been working on getting BOGON filter updates for the 174/8 space (IANA allocated this to ARIN back in February) with upwards of 35 providers (some of the Tier 1 providers are among these) over the last several weeks. Please help me (and others who are getting allocations) by reviewing your BOGON filters and insure you are really filtering out BOGONs and not space that is allocated. If you need a pointer, the authorataive list is maintained at http://www.iana.org/assignments/ipv4-address-space. Thanks for your attention and I hope to see some of you at an upcoming NANOG meeting. Stan Barber sob(a)academ.com (called "the other SOB on the Internet" by Scott Bradner many years ago in his first column for Network World magazine)

2 1

Re: Ubiquity<->Mzima routing loop
by Sena, Rich 19 Jul '08

19 Jul '08

Man it's been awhile... "Godwin..." errr maybe it's "Nazi" - or perhaps "Boursey" damn how do we stop this again?!?! Please only reply if you remember the magic word to make this thread stop! -- via the Blackberry Xpress! ----- Original Message ----- From: Guy_Shields(a)Stream.Com <Guy_Shields(a)Stream.Com> To: Paul Wall <pauldotwall(a)gmail.com> Cc: nanog <nanog(a)merit.edu> Sent: Fri Jul 18 22:33:12 2008 Subject: Re: Ubiquity<->Mzima routing loop No, a true routing loop will transit several hops and end back up at the same routers. A bouncing route between 2 routers is usually a directly connected route on an interface that goes down thereby "pulling" the route with out a nail down route it will send unkown route back out its default gateway. ----- Original Message ----- From: "Paul Wall" [pauldotwall(a)gmail.com] Sent: 07/18/2008 10:25 PM AST To: Guy Shields Cc: nanog <nanog(a)merit.edu> Subject: Re: Ubiquity<->Mzima routing loop Isn't that what a routing loop is, when it loops back out to the transit/interface from which it entered? Paul On Fri, Jul 18, 2008 at 7:07 PM, <Guy_Shields(a)stream.com> wrote: > This is not a routing loop. It is simply a route that was not tied down via a static route to NULL with a weight of 254. > > > ----- Original Message ----- > From: "Paul Wall" [pauldotwall(a)gmail.com] > Sent: 07/18/2008 06:57 PM AST > To: "William Pitcock" <nenolod(a)systeminplace.net> > Cc: nanog(a)merit.edu > Subject: Re: Ubiquity<->Mzima routing loop > > > > I'd like to rip on Mzima as much as the next guy, but I'm not sure how > they could "fix" this routing loop, shy of some creative ACLs. > > You should try contacting Ubiquity, as this traceroute looks like an > issue on their (Mzima's customer's) side. > > Paul Wall > > On Fri, Jul 18, 2008 at 3:27 PM, William Pitcock > <nenolod(a)systeminplace.net> wrote: >> Hi, >> >> Can someone at Ubiquity or Mzima fix this routing loop: >> >> traceroute to hg.atheme.org (72.37.225.164), 30 hops max, 40 byte >> packets >> 1 64.62.134.193 12.402 ms 12.370 ms 12.363 ms >> 2 ge5-0.cr01.ord01.mzima.net (206.223.119.62) 16.003 ms 15.985 ms >> 15.964 ms >> 3 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.139 ms 14.858 >> ms 14.838 ms >> 4 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.875 ms 15.854 ms >> 16.497 ms >> 5 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.747 ms 14.763 >> ms 14.745 ms >> 6 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 16.405 ms 8.773 ms >> 8.758 ms >> 7 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 9.831 ms * * >> 8 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.417 ms 4.403 ms >> 4.381 ms >> 9 * * * >> 10 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.293 ms 4.933 ms >> 4.914 ms >> 11 * * * >> 12 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.527 ms 14.526 ms >> 14.438 ms >> 13 * * * >> 14 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.352 ms 14.335 ms >> 3.770 ms >> 15 * * * >> 16 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.684 ms 13.897 ms >> 13.897 ms >> 17 * * * >> 18 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.599 ms 8.581 ms >> 8.668 ms >> 19 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.246 ms >> 20 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.584 ms 8.565 ms >> 8.545 ms >> 21 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.119 ms >> 22 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.456 ms 8.931 ms >> 8.913 ms >> 23 * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 6.049 ms * >> 24 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.862 ms 15.754 ms >> 15.736 ms >> 25 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 7.132 ms * 7.092 >> ms >> 26 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.293 ms 15.998 ms >> 10.752 ms >> 27 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 5.353 ms 5.336 >> ms * >> 28 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.800 ms 3.854 ms >> 3.823 ms >> 29 * * * >> 30 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.228 ms 4.426 ms >> 13.019 ms >> >> Thanks! >> >> William >> >> >> > >

2 1

Re: Ubiquity<->Mzima routing loop
by Guy_Shields＠Stream.Com 19 Jul '08

19 Jul '08

This is not a routing loop. It is simply a route that was not tied down via a static route to NULL with a weight of 254. ----- Original Message ----- From: "Paul Wall" [pauldotwall(a)gmail.com] Sent: 07/18/2008 06:57 PM AST To: "William Pitcock" <nenolod(a)systeminplace.net> Cc: nanog(a)merit.edu Subject: Re: Ubiquity<->Mzima routing loop I'd like to rip on Mzima as much as the next guy, but I'm not sure how they could "fix" this routing loop, shy of some creative ACLs. You should try contacting Ubiquity, as this traceroute looks like an issue on their (Mzima's customer's) side. Paul Wall On Fri, Jul 18, 2008 at 3:27 PM, William Pitcock <nenolod(a)systeminplace.net> wrote: > Hi, > > Can someone at Ubiquity or Mzima fix this routing loop: > > traceroute to hg.atheme.org (72.37.225.164), 30 hops max, 40 byte > packets > 1 64.62.134.193 12.402 ms 12.370 ms 12.363 ms > 2 ge5-0.cr01.ord01.mzima.net (206.223.119.62) 16.003 ms 15.985 ms > 15.964 ms > 3 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.139 ms 14.858 > ms 14.838 ms > 4 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.875 ms 15.854 ms > 16.497 ms > 5 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.747 ms 14.763 > ms 14.745 ms > 6 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 16.405 ms 8.773 ms > 8.758 ms > 7 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 9.831 ms * * > 8 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.417 ms 4.403 ms > 4.381 ms > 9 * * * > 10 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.293 ms 4.933 ms > 4.914 ms > 11 * * * > 12 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.527 ms 14.526 ms > 14.438 ms > 13 * * * > 14 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.352 ms 14.335 ms > 3.770 ms > 15 * * * > 16 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.684 ms 13.897 ms > 13.897 ms > 17 * * * > 18 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.599 ms 8.581 ms > 8.668 ms > 19 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.246 ms > 20 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.584 ms 8.565 ms > 8.545 ms > 21 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.119 ms > 22 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.456 ms 8.931 ms > 8.913 ms > 23 * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 6.049 ms * > 24 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.862 ms 15.754 ms > 15.736 ms > 25 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 7.132 ms * 7.092 > ms > 26 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.293 ms 15.998 ms > 10.752 ms > 27 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 5.353 ms 5.336 > ms * > 28 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.800 ms 3.854 ms > 3.823 ms > 29 * * * > 30 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.228 ms 4.426 ms > 13.019 ms > > Thanks! > > William > > >

3 2

Ubiquity<->Mzima routing loop
by William Pitcock 18 Jul '08

18 Jul '08

Hi, Can someone at Ubiquity or Mzima fix this routing loop: traceroute to hg.atheme.org (72.37.225.164), 30 hops max, 40 byte packets 1 64.62.134.193 12.402 ms 12.370 ms 12.363 ms 2 ge5-0.cr01.ord01.mzima.net (206.223.119.62) 16.003 ms 15.985 ms 15.964 ms 3 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.139 ms 14.858 ms 14.838 ms 4 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.875 ms 15.854 ms 16.497 ms 5 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 14.747 ms 14.763 ms 14.745 ms 6 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 16.405 ms 8.773 ms 8.758 ms 7 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 9.831 ms * * 8 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.417 ms 4.403 ms 4.381 ms 9 * * * 10 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 4.293 ms 4.933 ms 4.914 ms 11 * * * 12 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.527 ms 14.526 ms 14.438 ms 13 * * * 14 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 14.352 ms 14.335 ms 3.770 ms 15 * * * 16 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.684 ms 13.897 ms 13.897 ms 17 * * * 18 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.599 ms 8.581 ms 8.668 ms 19 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.246 ms 20 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.584 ms 8.565 ms 8.545 ms 21 * * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 8.119 ms 22 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 8.456 ms 8.931 ms 8.913 ms 23 * ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 6.049 ms * 24 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.862 ms 15.754 ms 15.736 ms 25 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 7.132 ms * 7.092 ms 26 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 15.293 ms 15.998 ms 10.752 ms 27 ge0-ubiquity.cust.ord01.mzima.net (72.37.148.158) 5.353 ms 5.336 ms * 28 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.800 ms 3.854 ms 3.823 ms 29 * * * 30 ge0-12.cr01.ord01.mzima.net (72.37.148.157) 3.228 ms 4.426 ms 13.019 ms Thanks! William

4 6

Looking for Network Solutions mail admin
by randal k 18 Jul '08

18 Jul '08

NANOGers, We're getting the run around from Network Solutions e-mail front-end support personnel and only canned replies from the postmaster, with no escalation available because we're the sender (i.e. not paying). Basic problem is that we have a client mail gateway that is unable to send mail to a particular netsol-hosted domain; acts like an RBL issue, even though the IP is squeeky clean. Can a NetSol email admin with some clue drop me a line? Thanks in advance -- Randal

3 4

Weekly Routing Table Report
by Routing Analysis Role Account 18 Jul '08

18 Jul '08

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 19 Jul, 2008 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 263570 Prefixes after maximum aggregation: 129383 Deaggregation factor: 2.04 Unique aggregates announced to Internet: 128648 Total ASes present in the Internet Routing Table: 28709 Prefixes per ASN: 9.18 Origin-only ASes present in the Internet Routing Table: 25036 Origin ASes announcing only one prefix: 12109 Transit ASes present in the Internet Routing Table: 3673 Transit-only ASes present in the Internet Routing Table: 76 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 19 Max AS path prepend of ASN ( 3816) 15 Prefixes from unregistered ASNs in the Routing Table: 585 Unregistered ASNs in the Routing Table: 215 Number of 32-bit ASNs allocated by the RIRs: 50 Prefixes from 32-bit ASNs in the Routing Table: 8 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 778 Number of addresses announced to Internet: 1894510496 Equivalent to 112 /8s, 235 /16s and 239 /24s Percentage of available address space announced: 51.1 Percentage of allocated address space announced: 62.1 Percentage of available address space allocated: 82.3 Percentage of address space in use by end-sites: 72.7 Total number of prefixes smaller than registry allocations: 128645 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 60485 Total APNIC prefixes after maximum aggregation: 22626 APNIC Deaggregation factor: 2.67 Prefixes being announced from the APNIC address blocks: 57467 Unique aggregates announced from the APNIC address blocks: 25516 APNIC Region origin ASes present in the Internet Routing Table: 3307 APNIC Prefixes per ASN: 17.38 APNIC Region origin ASes announcing only one prefix: 882 APNIC Region transit ASes present in the Internet Routing Table: 518 Average APNIC Region AS path length visible: 3.5 Max APNIC Region AS path length visible: 19 Number of APNIC addresses announced to Internet: 368124960 Equivalent to 21 /8s, 241 /16s and 36 /24s Percentage of available APNIC address space announced: 78.4 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 APNIC Address Blocks 58/8, 59/8, 60/8, 61/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 121119 Total ARIN prefixes after maximum aggregation: 65323 ARIN Deaggregation factor: 1.85 Prefixes being announced from the ARIN address blocks: 90675 Unique aggregates announced from the ARIN address blocks: 35130 ARIN Region origin ASes present in the Internet Routing Table: 12293 ARIN Prefixes per ASN: 7.38 ARIN Region origin ASes announcing only one prefix: 4747 ARIN Region transit ASes present in the Internet Routing Table: 1155 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 15 Number of ARIN addresses announced to Internet: 352742688 Equivalent to 21 /8s, 6 /16s and 109 /24s Percentage of available ARIN address space announced: 72.5 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 ARIN Address Blocks 24/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 173/8, 174/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 56703 Total RIPE prefixes after maximum aggregation: 34477 RIPE Deaggregation factor: 1.64 Prefixes being announced from the RIPE address blocks: 51898 Unique aggregates announced from the RIPE address blocks: 34879 RIPE Region origin ASes present in the Internet Routing Table: 11614 RIPE Prefixes per ASN: 4.47 RIPE Region origin ASes announcing only one prefix: 6089 RIPE Region transit ASes present in the Internet Routing Table: 1740 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 18 Number of RIPE addresses announced to Internet: 366805568 Equivalent to 21 /8s, 221 /16s and 2 /24s Percentage of available RIPE address space announced: 84.1 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-48127 RIPE Address Blocks 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 20673 Total LACNIC prefixes after maximum aggregation: 5279 LACNIC Deaggregation factor: 3.92 Prefixes being announced from the LACNIC address blocks: 18896 Unique aggregates announced from the LACNIC address blocks: 10693 LACNIC Region origin ASes present in the Internet Routing Table: 966 LACNIC Prefixes per ASN: 19.56 LACNIC Region origin ASes announcing only one prefix: 316 LACNIC Region transit ASes present in the Internet Routing Table: 162 Average LACNIC Region AS path length visible: 4.1 Max LACNIC Region AS path length visible: 18 Number of LACNIC addresses announced to Internet: 53626880 Equivalent to 3 /8s, 50 /16s and 72 /24s Percentage of available LACNIC address space announced: 53.3 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 186/8, 187/8, 189/8, 190/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 4008 Total AfriNIC prefixes after maximum aggregation: 1190 AfriNIC Deaggregation factor: 3.37 Prefixes being announced from the AfriNIC address blocks: 4300 Unique aggregates announced from the AfriNIC address blocks: 1895 AfriNIC Region origin ASes present in the Internet Routing Table: 241 AfriNIC Prefixes per ASN: 17.84 AfriNIC Region origin ASes announcing only one prefix: 75 AfriNIC Region transit ASes present in the Internet Routing Table: 47 Average AfriNIC Region AS path length visible: 3.9 Max AfriNIC Region AS path length visible: 14 Number of AfriNIC addresses announced to Internet: 12311296 Equivalent to 0 /8s, 187 /16s and 219 /24s Percentage of available AfriNIC address space announced: 36.7 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4755 1671 342 176 Videsh Sanchar Nigam Ltd. Aut 17488 1219 84 96 Hathway IP Over Cable Interne 9583 1170 89 481 Sify Limited 4766 852 6390 347 Korea Telecom (KIX) 23577 829 35 703 Korea Telecom (ATM-MPLS) 4134 824 13539 334 CHINANET-BACKBONE 9498 711 547 58 BHARTI BT INTERNET LTD. 4780 707 351 63 Digital United Inc. 18101 690 167 32 Reliance Infocom Ltd Internet 4808 617 1111 137 CNCGROUP IP network: China169 Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 209 3008 3859 625 Qwest 6389 2662 3260 195 bellsouth.net, inc. 6298 1606 233 782 Cox Communicatons 4323 1482 1061 379 Time Warner Telecom 2386 1477 646 873 AT&T Data Communications Serv 7018 1415 6247 988 AT&T WorldNet Services 11492 1210 149 32 Cable One 1785 1087 510 104 AppliedTheory Corporation 18566 1045 296 10 Covad Communications 20115 1041 1059 558 Charter Communications Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 3292 414 1792 372 TDC Tele Danmark 3301 332 1460 303 TeliaNet Sweden 3320 322 7047 270 Deutsche Telekom AG 8452 319 188 11 TEDATA 8866 317 77 21 Bulgarian Telecommunication C 5462 296 666 27 Telewest Broadband 8551 287 269 38 Bezeq International 3215 286 2758 90 France Telecom Transpac 680 274 2047 264 DFN-IP service G-WiN 6746 269 126 244 Dynamic Network Technologies, Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 1384 2590 225 UniNet S.A. de C.V. 11830 612 299 9 Instituto Costarricense de El 22047 565 270 14 VTR PUNTO NET S.A. 7303 471 232 63 Telecom Argentina Stet-France 16814 426 27 10 NSS, S.A. 6471 414 85 48 ENTEL CHILE S.A. 11172 408 118 71 Servicios Alestra S.A de C.V 10620 406 106 64 TVCABLE BOGOTA 14117 375 23 9 Telefonica del Sur S.A. 20299 335 23 98 NEWCOM AMERICAS Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 476 61 24 LINKdotNET AS number 20858 398 34 3 EgyNet 3741 270 853 225 The Internet Solution 2018 209 204 102 Tertiary Education Network 6713 143 135 11 Itissalat Al-MAGHRIB 33783 135 10 12 EEPAD TISP TELECOM & INTERNET 5713 130 556 75 Telkom SA Ltd 5536 120 8 17 Internet Egypt Network 29571 107 13 8 Ci Telecom Autonomous system 33776 99 6 7 Starcomms Nigeria Limited Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 209 3008 3859 625 Qwest 6389 2662 3260 195 bellsouth.net, inc. 4755 1671 342 176 Videsh Sanchar Nigam Ltd. Aut 6298 1606 233 782 Cox Communicatons 4323 1482 1061 379 Time Warner Telecom 2386 1477 646 873 AT&T Data Communications Serv 7018 1415 6247 988 AT&T WorldNet Services 8151 1384 2590 225 UniNet S.A. de C.V. 17488 1219 84 96 Hathway IP Over Cable Interne 11492 1210 149 32 Cable One Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 6389 2662 2467 bellsouth.net, inc. 4755 1671 1495 Videsh Sanchar Nigam Ltd. Aut 11492 1210 1178 Cable One 8151 1384 1159 UniNet S.A. de C.V. 17488 1219 1123 Hathway IP Over Cable Interne 4323 1482 1103 Time Warner Telecom 18566 1045 1035 Covad Communications 1785 1087 983 AppliedTheory Corporation 22773 971 907 Cox Communications, Inc. 6478 1003 835 AT&T Worldnet Services Complete listing at http://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 16927 UNALLOCATED 12.0.252.0/23 701 UUNET Technologies, 22492 UNALLOCATED 12.2.46.0/24 7018 AT&T WorldNet Servic 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet Servic 13632 UNALLOCATED 12.20.55.0/24 6517 Yipes Communications 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet Servic 13632 UNALLOCATED 12.31.25.0/24 6517 Yipes Communications 27220 UNALLOCATED 12.35.204.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.48.244.0/23 7843 Adelphia Corp. 24.51.159.0/24 7843 Adelphia Corp. 24.54.23.0/24 7843 Adelphia Corp. 24.54.224.0/19 20001 HoldCo LLC - Road Runner 24.75.160.0/19 7843 Adelphia Corp. 24.75.192.0/18 7843 Adelphia Corp. 24.142.40.0/21 7018 AT&T WorldNet Services 24.142.160.0/19 7018 AT&T WorldNet Services 24.246.0.0/17 7018 AT&T WorldNet Services 24.246.128.0/18 7018 AT&T WorldNet Services Complete listing at http://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:19 /9:9 /10:16 /11:45 /12:146 /13:287 /14:517 /15:1041 /16:10011 /17:4336 /18:7517 /19:15887 /20:18525 /21:18193 /22:22730 /23:23637 /24:137913 /25:837 /26:1030 /27:778 /28:82 /29:7 /30:1 /31:0 /32:6 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 209 1760 3008 Qwest 6389 1664 2662 bellsouth.net, inc. 6298 1582 1606 Cox Communicatons 11492 1194 1210 Cable One 2386 1174 1477 AT&T Data Communications Serv 17488 1033 1219 Hathway IP Over Cable Interne 18566 1026 1045 Covad Communications 9583 1025 1170 Sify Limited 4755 1023 1671 Videsh Sanchar Nigam Ltd. Aut 6478 994 1003 AT&T Worldnet Services Complete listing at http://thyme.apnic.net/current/data/sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:7 8:125 12:2091 13:2 15:22 16:3 17:5 18:13 20:35 24:1092 25:1 32:61 38:450 40:92 41:657 43:1 44:2 47:12 52:3 55:3 56:3 57:25 58:524 59:507 60:452 61:1009 62:1206 63:2031 64:3288 65:2386 66:3509 67:1229 68:735 69:2266 70:799 71:118 72:1961 73:5 74:1064 75:155 76:315 77:749 78:748 79:203 80:934 81:840 82:592 83:377 84:559 85:960 86:413 87:687 88:338 89:1316 90:15 91:1386 92:224 93:691 94:56 96:40 97:31 98:253 99:2 112:1 113:1 114:90 115:3 116:843 117:320 118:190 119:440 120:59 121:562 122:796 123:363 124:890 125:1168 128:361 129:199 130:132 131:410 132:66 133:9 134:186 135:33 136:223 137:91 138:147 139:94 140:493 141:98 142:406 143:325 144:384 145:51 146:366 147:157 148:517 149:198 150:129 151:180 152:144 153:136 154:10 155:251 156:174 157:291 158:187 159:239 160:279 161:118 162:210 163:154 164:525 165:452 166:318 167:330 168:621 169:138 170:423 171:32 172:10 188:1 189:287 190:2206 192:5798 193:4095 194:3231 195:2525 196:1042 198:3734 199:3270 200:5566 201:1462 202:7639 203:8045 204:3987 205:2132 206:2383 207:2762 208:3422 209:3510 210:2592 211:1074 212:1411 213:1610 214:164 215:49 216:4426 217:1195 218:343 219:421 220:1059 221:465 222:306 End of report

1 0