November 2008 - Test - lists.nanog.org

RE: Level 3 OC-12 cut in SanFran/Hayw
by Matthew Huff 20 Nov '08

20 Nov '08

Keep waiting. I've been yet unsuccessful on getting a call back from anyone. They keep saying the same thing "it's part of a oc12 issue, field techs have been dispatch, please wait, no etr". Since that's now over 12 hours, I don't find it acceptable (not the down part, if it's part of a large cut, outage etc, I understand that), but rather their lack of information. I've escalated it to a "level 4 escalation" and they promised a callback within 15 minutes (which was 30 minutes ago). By any chance, were you originally a Broadwing customer? I have a feeling that the oc-12 that was disconnected was a mistake in their db caused by the acquisition, and since they may have lost the original info, they may have no choice but to re-engineer the circuits. -----Original Message----- From: Brandon Shiers [mailto:brandon.shiers@wyoming.com] Sent: Thursday, November 20, 2008 9:06 AM To: Matthew Huff; 'NANOG list' Subject: RE: Level 3 OC-12 cut in SanFran/Hayw I can tell you I have a DS3 here in Wyoming down because of this outage as well. 14 hours now it's been out and we haven't received anything from L3 unless I call and beat it out of them. I am waiting on a CB from a supervisor right now. -----Original Message----- From: nanog-bounces(a)nanog.org [mailto:nanog-bounces@nanog.org] On Behalf Of Matthew Huff Sent: Wednesday, November 19, 2008 10:45 PM To: NANOG list Subject: Level 3 OC-12 cut in SanFran/Hayw We lost a DS3 out of our downtown SF office around 4 hours ago. The Level 3 master ticket for OC-12 outage is #3020259 and is out of Hayworth. Anyone know anything more about this? Getting any info out of level 3 let alone an ETR has been challenging.

1 0

Re: IPv6 routing /48s
by trejrco＠gmail.com 20 Nov '08

20 Nov '08

Ah yes, public-but-not-external IPv4 addresses ... I wish a stern note saying don't do that was feasible ... /TJ ------Original Message------ From: Nathan Ward To: nanog list Subject: Re: IPv6 routing /48s Sent: Nov 19, 2008 15:02 On 20/11/2008, at 4:06 AM, Florian Weimer wrote: > * Michael Sinatra: > >> And it just reinforces the fear that people have against putting AAAA >> records in DNS for their publicly-accessible resources, especially >> www. > > Won't current Windows clients work just fine in this case? > > I have no idea what a fix should look like for some of the non-Windows > systems I care about, unfortunately. No, unfortunately broken 6to4 auto-configuration (ie, in Vista, XPSP2, when on a non-RFC1918 IP address) breaks, and you get 90s timeouts before falling back to IPv4/A. Works fine most of the time, however when that non-RFC1918 address is behind NAT, or some sort of packet filter, then it doesn't work so well, and the client does not have a way to detect that reliably. -- Nathan Ward Sent from my Verizon Wireless BlackBerry

8 13

Blackhole route advertisements by AS14037 of our IP space - please filter them out at your end
by Suresh Ramasubramanian 20 Nov '08

20 Nov '08

Hi We blocked some prefixes belonging to AS14037 (rackvibe llc) due to their hosting spammers. Rackvibe decided to nullroute us back in reply - thats up to them I guess Only they're dumb enough to inject these blackhole announcements into the cloud, and various other networks are picking up on these announcements TIA for filtering these out at your end Our IPs are below - at least 208.36.123/24 seems to be announced as a blackhole route by rackvibe - 205.158.62.0/24 208.36.123.0/24 203.86.166.0/24 65.49.50.0/24 65.49.50.0/24 64.71.166.192/27 64.62.181.80/28 srs Paths: (7 available, best #7, table Default-IP-Routing-Table) Not advertised to any peer 16150 6939 19318 14037 217.75.96.60 from 217.75.96.60 (217.75.96.60) Origin IGP, metric 0, localpref 100, valid, external Community: 16150:63392 16150:65320 16150:65426 3333 1103 1273 19318 14037 193.0.0.56 from 193.0.0.56 (193.0.0.56) Origin IGP, localpref 100, valid, external Community: 1103:1000 1273:21000 1273:21971 14037:6855 19318:999 19318:4000 19318:6855 19318:40012 21698:999 21698:4000 21698:6855 3277 3216 1273 19318 14037 194.85.4.55 from 194.85.4.55 (194.85.4.16) Origin IGP, localpref 100, valid, external Community: 1273:21000 1273:21971 3216:3000 3216:3001 3277:3216 14037:6855 19318:999 19318:4000 19318:6855 19318:40012 21698:999 21698:4000 21698:6855 812 19318 14037

3 6

Quagga on Xen or VMWare etc
by David Curran 19 Nov '08

19 Nov '08

Can anyone provide direction (anecdotal or otherwise) on the use of Quagga in a virtual environment for route servers? Thanks

3 2

Verizon outage between Baltimore and Washington
by Steven Fischer 19 Nov '08

19 Nov '08

Can someone on the list shed some more light on this? Verizon reports the 9 linear oc-48s are impacting 173 ds3s, 3 oc3cs, and 14 oc12cs. There is 1 unprotected oc192c down for TOT-A. OTDR readings from Baltimore place the break at 36.4 miles towards Washington. Additional OTDR readings from Laurel toward Washington indicate cut at 16.25 miles. Any additional info would be appreciated. -- To him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy

3 4

Re: IPv6 routing /48s
by trejrco＠gmail.com 19 Nov '08

19 Nov '08

Yeah, that's part of why it isn't feasible :) Also - a more generalized black-hole detection type mechanism (to also catch PMTUD failures, etc) would be mighty useful ... /TJ ------Original Message------ From: Nathan Ward To: nanog list Subject: Re: IPv6 routing /48s Sent: Nov 19, 2008 15:34 On 20/11/2008, at 10:11 AM, trejrco(a)gmail.com wrote: > Ah yes, public-but-not-external IPv4 addresses ... I wish a stern > note saying don't do that was feasible ... What people do with their addresses is their business. The problem here is XPSP2/Vista assuming that non-RFC1918 = unfiltered/ unNATed for the purposes of 6to4. Well, deeper problem is that they're using 6to4 on an end host I suppose - it's supposed to be used on routers. I was going to write up a qualification mechanism for it so it could detect if 6to4 was OK or not, but code is already out there on umpteen million PCs that aren't going to do their patches. I still plan to.. hopefully I'll get around to it when I feel a bit less jaded :-) -- Nathan Ward Sent from my Verizon Wireless BlackBerry

1 0

Re: Verizon outage between Baltimore and Washington
by Justin M. Streiner 19 Nov '08

19 Nov '08

On Wed, 19 Nov 2008, Steven Fischer wrote: > looks like a single break....Baltimore is about 36.4 miles north of > Washington, and Laurel is about 16.25 miles north of Washington, with > Baltimore being about 20 miles north of Laurel. All this makes sense. The > part that doesn't really make sense is that our headquarters in right > smack-dab along this run in Columbia, MD (about 5-7 miles north of Laruel), > and has been unaffected...but a remote office in Hagerstown, about 50-60 > miles west, north-west of here, is down hard. The circuit between you and your remote office could be DACS'd across several SONET rings between point A and B and if the cut took out one of those rings then you'd lose your circuit. Also, keep in mind that carriers love to call SONET rings redundant even when both the working and protect sides of it ride in the same conduit, or hell, even in the same buffer. That makes them a little more susceptible to backhoe fade. There are other possibilities as well, such as the protect side of the ring being down for maintenance when something hits the working side, the carrier screws up a re-groom, etc... jms

1 0

New Internet study released
by Irwin.Lazar＠nemertes.com 19 Nov '08

19 Nov '08

Hi All, Nemertes Research released a study on Internet Infrastructure this morning, this is an update to our 2007 study looking at Internet demand vs. growth of available bandwidth. This year's update also includes an examination of routing/addressing trends, IPv6 adoption, and potential of other solutions such as LISP and application-based addressing. It's freely available on our web site: http://www.nemertes.com/internet_interrupted_why_architectural_limitations_… thanks, irwin

1 0

Adobe contact
by Jeff Calvert 19 Nov '08

19 Nov '08

Hello, Could someone from Adobe (AS1313) please contact me off list? I'm having some routing issues getting packets back from your network. Thanks, Jeff Calvert jeff(a)jeffcalvert.com jcalvert(a)cyrusone.com 713-821-1260 opt 2 (NOC)

1 0

Router Choice
by Raymond Macharia 18 Nov '08

18 Nov '08

Hello fellow nanogers, I am a long time user of Cisco gear and currently evaluating an alternative for my network expansion. currently the one that looks like it will be able to do the job iare Alcatel-Lucent 7710/7750 service routers. I am looking for real life experience of those who have used it and what I may need to watch out for (if anything) I have seen in some of their documentation features like Non-stop Services (NSS) and Non-stop Routing (NSR). are these features real world deployable. oh, just to add I want to use the routers as P routers in my IP/MPLS core Regards -- Raymond Macharia

7 8