October 2001 - Test - lists.nanog.org

well, that failed miserably (route-views.oregon-ix.net)
by David Meyer 02 Oct '01

02 Oct '01

Apparently zebra bgpd has problems with 60+ ebgp multihop peers. I will try to debug it tomorrow (the cisco is running there now). Sorry about the inconvenience. Dave

1 0

route-views.oregon-ix.net will be down for a few minutes
by David Meyer 02 Oct '01

02 Oct '01

Folks, I'll be cutting route-views.oregon-ix.net over to the new box in a few minutes. In theory this should only take a few minutes. Thanks Joel Jaeggli and Jon Miyake for all their help with this. Thanks, Dave

1 0

OT: Wanted, a few testers
by Eric Germann 02 Oct '01

02 Oct '01

Looking for a few people to make a test voice call for me. Seem to have call routing problems and want far and wide test points. Contact me unicast and I will send the information. Thanks Eric

1 0

Re: RE: Three months until circuits repaired
by Frank Coluccio 02 Oct '01

02 Oct '01

Our local ISP's T circuits are still down hard in the South Street Seaport, and our POTS phone lines have been forwarded to a number of newly created cellular accounts. > I have 14 circuits down to 140 West CO. > > shawn. > > -----Original Message----- > From: Frank Coluccio [mailto:fcoluccio@dticonsulting.com] > Sent: Tuesday, October 02, 2001 12:22 AM > To: sean(a)donelan.com > Cc: nanog(a)merit.edu > Subject: Re: Three months until circuits repaired > > > > All, earlier I stated that the West Street C.O. next to the WTC would very > likely > be gutted, entirely. In a modified approach it now appears that four floors > of > the building will continue to support limited carrier system and switching > operations, while the remainder of the building is done anew. Once done, the > four > floors that are now still operational will be treated similarly. No time-to- > completion date has been given yet. > > -FAC > > > > > > > How many people still have circuits outside of New York City > > down? I've heard Worldcom is telling people they won't have > > everything repaired before December 31. Is this similar for > > all carriers? > > > > > > > >

2 1

SNMPv3 deployment survey
by RJ Atkinson 02 Oct '01

02 Oct '01

In order to advance SNMPv3 from Draft Standard to Full Standard, a deployment summary needs to be created for IETF purposes. If anyone here has any deployment of SNMPv3 (whether or not you actually enable the crypto bits) as different from SNMPv2c or SNMPv1, it would be most appreciated if you'd drop me a unicast reply with roughly this data: Organisation Name: Organisation Contact Person: name & email is ideal Which SNMPv3-capable products are deployed: Both boxes being managed (e.g. Brand X router, Brand Y switch) & the SNMP manager (e.g. UCD SNMP, OpenView with SNMPv3 plug-in, etc) If possible, some notion of the scale of the deployment (e.g. limited, internal corporate only, in production ISP network, field trial with plan to go production on <date>) If there are issues with giving the above level of detail because of company policy on proprietary/confidential information, then please send me an email with whatever you are allowed to say. The more specific answers will be more helpful, but we'll take anything we can get. Again, please send me UNICAST replies, not to the list. If there is broad interest, I am happy to summarise back to the list in a few weeks. Thanks, Ran rja(a)inet.org

1 0

Perhaps OT?: Genuity/BBN
by Christopher Wolff 02 Oct '01

02 Oct '01

Hello again, So many questions, so many great answers, thanks again list for all the great info. I hope I have something to give back to everyone soon (Free 56k accounts? :) I think I'm going to be in the market for a new backbone provider to add to my existing mix (Qwest, GBLX, Broadwing). I'm thinking one of these might go away. The criteria will be to have great nationwide backbone quality, low response times, no fuss customer support, etc. I'm wondering what everyone thinks of Genuity. They say "all the right things" and from the traceroutes I've run off of their route server the national network seems pretty well managed. Any ideas? I'll be happy to hear them all. Thanks in advance, Christopher J. Wolff, CIO Broadband Labs

1 0

Buffers and TCPWindowsize...WAS: PTP latency
by Christopher Wolff 02 Oct '01

02 Oct '01

Dear list, Thank you for all the great responses regarding the PTP latency issue. This was very thorough information that will help me make a decision. A related, yet somewhat separate issue that I would like some advice on is what kind of circumstances would cause a tcp congestion window to be reduced over a WAN connection, assuming that the servers on both sides are not busy (or even barely utilized). Assuming that a 1472 byte packet could pass freely from WAN point A to WAN point B without being defragmented, it has been suggested to me that somehow windowing is playing a role in poor throughput. I understand the role that windowing plays in tcp/ip, I guess what I'm wondering is how that packet could get 'squeezed' as it passes through a WAN. Thank you, Christopher

2 1

Re: Three months until circuits repaired
by Frank Coluccio 02 Oct '01

02 Oct '01

All, earlier I stated that the West Street C.O. next to the WTC would very likely be gutted, entirely. In a modified approach it now appears that four floors of the building will continue to support limited carrier system and switching operations, while the remainder of the building is done anew. Once done, the four floors that are now still operational will be treated similarly. No time-to- completion date has been given yet. -FAC > > > How many people still have circuits outside of New York City > down? I've heard Worldcom is telling people they won't have > everything repaired before December 31. Is this similar for > all carriers? > > >

1 0

Re: New use for AOL CDs (was Re: Your customer's ...)
by rs＠seastrom.com 01 Oct '01

01 Oct '01

Sean Donelan <sean(a)donelan.com> writes: > A dumb suggestion, but why doesn't Microsoft hire AOL to include all its > recommended patches for Windows on the CD's AOL sends to everyone on > the planet? That way users don't have to wait for hours for all the > patches downloading on their 28k modems. Because upgrades to the AOL software come out every few months, whereas (security-related) patches to Microsoft software come out every few days. The supply chain logistics alone would be unreal. ---Rob

1 0

RE: Long haul latency calculation?
by Martin, Christian 01 Oct '01

01 Oct '01

Christopher, The factors influencing latency are propagation delay (Pd), transmission delay (Td), and queueing or processing delay (Qd). For simplicity, assume Qd is negligible, then L = Pd + Td. Pd, as suggested by others, is: distance/.66c Transmission delay is the time it takes to transmit X bits over a link of bandwidth Y, without acknowledgement. For the single packet case, this reduces to a worst case scenario of the MTU/Bandwidth. For TCP applications, assuming a fully realized window WIN = (min{cwnd, rwnd}), this reduces to WIN/BW. Since it is simpler to dicuss the MTU case, you get the folowwing formula: L = ((MTU/BW) + (dist/(.66c))) So, given a T1 that traverses 4000 meters and an MTU of 1500 bytes (8000 bits), you get a one-way Latency: L = ((8000/1.536E6) + (4e6/(.66*3E8)) = 25.4 msec. For an OC-48 L = ((8000/2.448E9) + (4e6/(.66*3E8)) = 20.2 msec For 2900 mile circuit, you get L = ((8000/1.536E6) + (2900*1.6e3/(.66*3E8)) = 28.2 msec Note that distance begins to dominate the delay as distance increases. That is, a short OC-48 transmits 1500 bytes much faster than a T1, but an OC-48 to Jupiter transmits the data at nearly the same rate as a T1 (both take a really long time!) chris > -----Original Message----- > From: Christopher Wolff [mailto:chris@bblabs.com] > Sent: Sunday, September 30, 2001 10:09 PM > To: nanog(a)merit.edu > Subject: Long haul latency calculation? > > > > Dear Nanog: > > I was wondering if there is a benchmark for long-haul circuit > latency... For example if I had a T1 circuit with 2900 miles > between the two end-points (and assuming the provider is best > case scenario) can I do something like (miles*latencyfactor) > = 5 ms for 2900 miles? > > Thanks, > Christopher >

1 0