- Test - lists.nanog.org

issues with AOL Time Warner
by Niaz, Wajahat 21 May '04

21 May '04

Is anyone seeing issues with AOL CNN ?

5 4

RE: issues with AOL Time Warner
by Owens, Loren 21 May '04

21 May '04

South East (Central Florida specifically) is seeing major problems as well. Cfl.rr.com has stopped routing through ATDN all together and is now going out through bbnplanet and level3. Shane -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Gabriel Sent: Friday, May 21, 2004 4:18 PM Cc: 'nanog(a)merit.edu' Subject: Re: issues with AOL Time Warner Same here... We saw all our AIM clients go down for about five minutes. Traceroutes showed lots of apparent troubles in atdn.net, also coming from the west coast. >>Is anyone seeing issues with AOL CNN ? -- Gabriel Cain www.dialupusa.net Senior Systems Administrator gabriel(a)dialupusa.net PGP fingerprint: C0B4 C6BF 13F5 69D1 3E6B CD7C D4C8 2EA4 2B08 1C6D Technology for the sake of business.

2 1

Re: Qwest Utah fiber cut
by sgorman1＠gmu.edu 21 May '04

21 May '04

Now it makes sense - we were missing the fiber route along US HWY 89. We have data on their nation wide OC-192 network and metro fiber, but figured there was something we were missing. Also explains why other providers were not affected - it must be a unique right of way. Appreciate the help. sean ----- Original Message ----- From: "Aaron D. Gifford" <agifford(a)infowest.com> Date: Friday, May 21, 2004 3:39 pm Subject: Re: Qwest Utah fiber cut > sgorman1(a)gmu.edu wrote: > > > > I was hoping someone might be able to shed some light on the > Utah cut. > > > > The news report said that the cut happened near Monroe Utah, > which is several miles off of I 70. Yet the cities that were > reported effected included St. George, Cedar City, and Salt Lake, > which all are adjacent to I 15. > > > > The puzzling part is that in our "best effort" database Qwest > does not have long haul fiber running down I 70, but it does have > a lot of fiber running down I 15. There is Qwest fiber on I 15, > all the cities affected are on I 15 yet the reported cut was near > Monroe off of I 70. > > > > I'm not familiar with Utah geogrpahy and this comes simply from > looking at our maps. Just trying to sort out the seeming > discrepency. Any insight? > > > <<snip>> > > According to this map at > http://atlas.utah.gov/staticmapbin/urta_network.gif the Qwest > fiber in > question runs southward along I-15 from Salt Lake City, through > Utah > Valley (Provo, Utah, etc.) to Nephi, Utah, then turns eastward > away from > the I-15 corridor until it reaches highway 89, which it follows > southward parallel to I-15 but one mountain range to the east. It > continues southward along 89 until I-17, then follows I-70 until > it ends > where it meets I-15, where the fiber continues southward along I- > 15 to > St. George, Utah (where I'm at), the end-of-the-one-lane-dead-end > road. > This route would be consistent with the news reports saying the > cut was > near Monroe, Utah or near Richfield, Utah. > > Such a route would agree with the telecommunication territories as > mapped out at http://atlas.utah.gov/telcom/viewer.htm which shows > Qwest > territories along I-15 except for the central Utah areas where > Qwest's > fiber follows highway 89 (which area IS a Qwest territory). > > While the news articles only mention that cellular, long distance, > 911, > and internet services were affected but local calling was not, > this is > not entirely true. As one affected by the cut, I can attest that > the > resulting additional load on the local switches (perhaps as people > were > calling each other to find out what was happening -- I don't know) > made > many phones utterly useless, including my own. > > A similar cut happened some years go around Springville, Utah. I > had > thought that Quest had since worked with local public safety folks > to > set up emergency 911 services that rely on the fiber to > automatically > fall-over to Qwest's older and lower bandwidth microwave network. > Apparently that plan fell by the wayside, or else I misheard it in > the > first place. > > Local area public safety personnel resorted to using the Emergency > Broadcast System over radio (television translators were also > affected > as many of them receive their video feeds over that same fiber) to > tell > citizens the direct-dial numbers, and in cases (like my home > phone) > where the phone system wasn't working at all (probably due to > overload), > local public safety folks told people to go to their nearest fire > station for emergency help. > > Messages over local radio indicated that the outage not only > affected > southwestern Utah counties (almost 1/3 of the state by area), but > Lincoln County, Nevada, and Mohave and Coconino Counties in > Arizona > (north of the Grand Canyon). I don't know how accurate that > message was. > > Aaron out. > >

2 1

New IPv6 Allocation to ARIN
by Doug Barton 21 May '04

21 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is to inform you that the IANA has allocated the following IPv6 /23 block to ARIN: 2001:3C00::/23 ARIN For a full list of IANA IPv6 allocations please see: http://www.iana.org/assignments/ipv6-tla-assignments - -- Doug Barton General Manager, Internet Assigned Numbers Authority -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFArmPzwtDPyTesBYwRAlMcAJ0QbmVVh32h0UX7CLfeum6I8qGB+wCfRmOi XD6hR9kQpwWB/3sIMqrLhLk= =RHGH -----END PGP SIGNATURE-----

1 0

Re: handling ddos attacks
by Paul Vixie 21 May '04

21 May '04

> Ok, I 'll buy that right now; we have a DDoS Attack on our core nameservers > from 66.165.10.24. Where do we start, do I call the police in Bellingham or > Washington State Police. We have blocked their ips but, we know they will > come in another way. the best thing is if you call the FBI, or NIPC. if you call your local FBI field office and say you're experiencing a cyberattack and could they give you the number for NIPC then it'll probably produce the results you want, even if NIPC has been renamed one or more times since i last talked to them, or if this old functionality within FBI is now handled by DHS, or both.

4 3

Re: Qwest Utah fiber cut
by sgorman1＠gmu.edu 21 May '04

21 May '04

I was hoping someone might be able to shed some light on the Utah cut. The news report said that the cut happened near Monroe Utah, which is several miles off of I 70. Yet the cities that were reported effected included St. George, Cedar City, and Salt Lake, which all are adjacent to I 15. The puzzling part is that in our "best effort" database Qwest does not have long haul fiber running down I 70, but it does have a lot of fiber running down I 15. There is Qwest fiber on I 15, all the cities affected are on I 15 yet the reported cut was near Monroe off of I 70. I'm not familiar with Utah geogrpahy and this comes simply from looking at our maps. Just trying to sort out the seeming discrepency. Any insight? ----- Original Message ----- From: Sean Donelan <sean(a)donelan.com> Date: Friday, May 21, 2004 11:14 am Subject: Qwest Utah fiber cut > > http://www.thespectrum.com/news/stories/20040521/localnews/471985.html > > Businesses feel effects of communications outage > By RACHEL OLSEN > rolsen(a)thespectrum.com > ST. GEORGE -- A major disruption in a communication line caused some > problems for businesses throughout Southern Utah on Thursday. > > Although a Qwest Communications spokesperson could not be reached > Thursday, a reported disruption in a main line Thursday near Monroe > created service failure in most cell phones, long distance, > Internet and > almost every Salt Lake-based television station. > [...] > >

3 2

RE: fiber cut 19 May/PM -> 20 May/AM in Ashburn, VA (lawnmower?!)
by Burton, Chris 21 May '04

21 May '04

I would agree that most Telco's put the initial ring fiber pairs in the same conduit due to cost savings and build out permits; but sometimes the issue is not cost; but laziness on the part of the company or the engineer. In the past I worked for a company that designed and installed MAN rings and more often then not the company would work a ring into a single conduit just because it was easier to do. Chris Burton Network Engineer Walt Disney Internet Group: Network Services The information contained in this e-mail message is confidential, intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please contact Walt Disney Internet Group at 206-664-4000. -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Robert E. Seastrom Sent: Friday, May 21, 2004 5:09 AM To: Dan Armstrong Cc: nanog(a)merit.edu Subject: Re: fiber cut 19 May/PM -> 20 May/AM in Ashburn, VA (lawnmower?!) Dan Armstrong <dan(a)beanfield.com> writes: > Forgive me, but > > Isn't Sonet usually deployed in a ring? Why the heck would a fiber > this important not be? sonet, obviously, does not *have* to be in a ring, but it often is. unfortunately, a fair percentage of the time, the additional protection offered by a ring topology is a mirage, due to a configuration known as "collapsed backbone". in this instance, both pairs of fiber ride in the same conduit for some portion of the distance (most notably laterals to building entrances, but sometimes for a fair distance down the street). the driving factor in building this way is usually cost savings. while this arrangement does protect against failures of optics and electronics (which in fairness are indeed more common than fiber cuts), it provides no protection against hungry construction (or in this case, lawn maintenance) equipment. ---rob

1 0

Re: fiber cut 19 May/PM -> 20 May/AM in Ashburn, VA (lawnmower?!)
by sgorman1＠gmu.edu 21 May '04

21 May '04

This is from a previous thread on the topic of fiber cuts but I thought it fit this discussion well, epsecially since it concerns Verizon. Apologize for not being able to recall who originally posted it - only have the citation. In an August 5th, 2003 court case involving the Maine Public Utility Commission an expert witness from Verizon stated that only 10% of the fiber rings in Maine are fully redundant, and 90% are at least partially collapsed and vulnerable to single cut failures (Maine PUC, 2003) Maine PUC, 2003, “Docket Number 2002243” http://www.state.me.us/mpuc/misctranscripts/2002-243%20080503.htm Appears it should not be a suprise at all it was not redundant. On a related note another researcher at GMU has collected all the outage reports that "were" posted on the FCC website and put them in a database form, and we are going to try and run correlations between outage location and the density of fiber located there. ----- Original Message ----- From: Joe Abley <jabley(a)isc.org> Date: Friday, May 21, 2004 10:23 am Subject: Re: fiber cut 19 May/PM -> 20 May/AM in Ashburn, VA (lawnmower?!) > > > On 21 May 2004, at 08:09, Robert E. Seastrom wrote: > > > sonet, obviously, does not *have* to be in a ring, but it often is. > > unfortunately, a fair percentage of the time, the additional > > protection offered by a ring topology is a mirage, due to a > > configuration known as "collapsed backbone". in this instance, both > > pairs of fiber ride in the same conduit for some portion of the > > distance > > ... or even as two wavelengths on the same pair of fibre. > > It's a sick, sick, twisted world. > > > Joe > > >

2 1

RE: Dell power connect switches.
by Joel Perez 21 May '04

21 May '04

Wow, I got more responses than I thought. I tend to agree with the majority of the opinions. I tested a 3048,3348 and 6024 in our lab. We will be creating about 12 VLANS total. While that isn't a lot per say, the 3048 couldn't handle more than one VLAN on it. The 3348 let us add several vlan's but then I couldn't trunk them together.. The 6024 we really didn't experience any problems with so far. But, I don't want some of the switches to work correctly some of the time. I am going to make my stand against buying these for our network and try to pitch Cisco for L3 stuff and RiverStone for L2 stuff. I know some people don't like RiverStone, but I have several years of experience with them at my previous place of employment. I agree that for L3 they aren't worth it, but for L2 I never had any issues. Well... worms love to melt RiverStones, but that is another story. Another thing that bugs me is that the existing Dell switches have had ports go bad on them. At least with the RiverStones I can replace the Ethernet cards. With the Dell's I have to replace the whole switch. Thanks again to everyone! ------------------------------------- Joel Perez | Network Engineer jperez(a)uspgi.com | www.USPGI.com ------------------------------------- -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Joel Perez Sent: Thursday, May 20, 2004 4:11 PM To: nanog(a)merit.edu Subject: Dell power connect switches. Good afternoon, We are planning to deploy several Dell PowerConnect 3324, 3348 and 6024 switches on our network. We currently have between 200-300 users and servers that these switches will service. We are also planning to add about 300-400 more users in the next 2-3 mos. 85% of the users are for our call center where they all use Terminal clients and connect to W2K TS. The rest is regular staff and our application servers. Can anyone tell me any good/bad points about them? I originally proposed using RiverStone as L2 switches but price was a factor in our decision to go with Dell. That is my main concern at this point. The Dell switches are very cheap compared to other L2 switches out there. Will this be a case of "you get what you pay for" or are they really good performing units? I really have not been able to find any lists or other sources with comments on these units. I'd appreciate any info you guys might have. Regards, ------------------------------------- Joel Perez | Network Engineer jperez(a)uspgi.com | www.USPGI.com -------------------------------------

1 0

Qwest Utah fiber cut
by Sean Donelan 21 May '04

21 May '04

http://www.thespectrum.com/news/stories/20040521/localnews/471985.html Businesses feel effects of communications outage By RACHEL OLSEN rolsen(a)thespectrum.com ST. GEORGE -- A major disruption in a communication line caused some problems for businesses throughout Southern Utah on Thursday. Although a Qwest Communications spokesperson could not be reached Thursday, a reported disruption in a main line Thursday near Monroe created service failure in most cell phones, long distance, Internet and almost every Salt Lake-based television station. [...]

1 0