Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!NISC.JVNC.NET!heker From: heker@NISC.JVNC.NET (Sergio F. Heker) Newsgroups: comp.protocols.tcp-ip Subject: Re: Serious Routing Problems Message-ID: <9007271220.AA03294@nisc.jvnc.net> Date: 27 Jul 90 12:20:09 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 109 Phil, While the number of hops is large over JvNCnet (don't forget that the network extends over eight states) I don't see a "serious routing loop" on your trace, in fact I don't see any routing loop. For your information, the JvNCnet network is a ring of T1s connecting backbone nodes colocated at the phone company point of presence with two cisco routers at each point of presence to add capacity and for reliability purposes. The backbone nodes are located at Trenton NJ, Newark, NJ, New York City, New Haven, CT, Providence, RI, Boston, Mass and Philadelphia, PA. On a test performed just now and attached below, 5 packets were lost of 1000 with an average round trip of 51 ms on the path from one of our hosts at the new JvNCnet headquarters at Princeton University and MIT. This is quite reasonable. We have been monitoring access to NEARnet due to the importance of NEARnet as a whole and specially since the last three weeks we have experienced excellent performance. This was also observed by the NSFNET NOC. Previously we were affected by a limitation to the amount of traffic carried by the JvNCnet together with the routing table size (of about 300 networks) which accounted for memory limitations. Two major changes took place three weeks ago on the JvNCnet cisco routers, the first one was an upgrade of all firmware (400 PROMS) to cisco 8.1 which improved the way cisco 7.1 handled changes of routing information. The second change was a reduction of the cisco image running on the routers. We are very happy with the results and the cooperation of cisco and the JvNCnet members as well as RCI our long distance provider to make these changes expedioustly. In anticipation of the installation of the new NSS for NEARnet, JvNCnet will work with NEARnet in the installation of a temporary direct access T1 line connecting NEARnet and JvNCnet directly at the JvNCnet NSS in Princeton. The JvNCnet and NEARnet NOCs are working together to make this new NSS transition become transparent to the users. We always welcome comments on the network, however you should probably send them to a list more dedicated to this purpose than "tcp-ip". If you do see a loop or a performance problem could you please send a message to our NOC. We can be reached at "noc@nisc.jvnc.net". Thank you very much. -- Sergio -- begin forwarded message -- From owner-tcp-ip Thu Jul 26 18:24:56 1990 Received: by nisc.jvnc.net (5.61/1.34) id AA01801; Thu, 26 Jul 90 18:24:54 -0400 Received: from jvncb.csc.org by nisc.jvnc.net (5.61/1.34) id AA01797; Thu, 26 Jul 90 18:24:52 -0400 Received: from NIC.DDN.MIL by jvncb.csc.org (5.61/1.34) id AA02895; Thu, 26 Jul 90 18:29:44 -0400 Received: from WOLF.BRL.MIL by NIC.DDN.MIL with TCP; Thu, 26 Jul 90 08:42:22 PDT Received: by WOLF.BRL.MIL id aa14006; 26 Jul 90 11:33 EDT Date: Thu, 26 Jul 90 11:25:38 EDT From: Mike Muuss To: TCP-IP@nic.ddn.mil Subject: Serious Routing Problems Message-Id: <9007261125.aa13838@WOLF.BRL.MIL> Status: RO This is one of the most painful trips from Maryland to Boston I have ever seen! -Mike From: Phil Dykstra For ha ha's check this out: traceroute to expo.lcs.mit.edu (18.30.0.212), 30 hops max, 40 byte packets 1 ext328 (128.63.4.22) 21 ms 21 ms 26 ms 2 MOFFETT-FLD-MB.DDN.MIL (26.20.0.16) 586 ms 632 ms 272 ms 3 Palo_Alto.CA.NSS.NSF.NET (192.52.195.254) 238 ms * 200 ms 4 Salt_Lake_City.UT.NSS.NSF.NET (129.140.79.13) 426 ms 497 ms 261 ms 5 Ann_Arbor.MI.NSS.NSF.NET (129.140.81.15) 275 ms 263 ms 367 ms 6 Princeton.NJ.NSS.NSF.NET (129.140.72.17) 303 ms 257 ms 248 ms 7 zaphod-gateway.jvnc.net (192.12.211.65) 271 ms 294 ms 250 ms 8 hotblack-gateway.jvnc.net (130.94.0.67) 271 ms 384 ms 287 ms 9 capital1-gateway.jvnc.net (130.94.1.9) 556 ms 472 ms 300 ms 10 cheesesteak2-gateway.jvnc.net (130.94.33.250) 459 ms 294 ms 666 ms 11 * * cheesesteak1-gateway.jvnc.net (130.94.32.1) 306 ms 12 * beantown2-gateway.jvnc.net (130.94.27.250) 335 ms 311 ms 13 near-gateway.jvnc.net (130.94.27.10) 335 ms 328 ms 385 ms 14 ihtfp.mit.edu (192.54.222.1) 774 ms * 353 ms 15 SEWAGE.MIT.EDU (18.68.0.8) 576 ms * 303 ms 16 * MOSS.LCS.MIT.EDU (18.10.0.11) 344 ms 365 ms The MILNET throws it as far away as it possibly can, NSFNET spends four (nice orderly) hops getting it to Princeton, and then JVNC spends 7(!) hops getting it to Boston. From "picasso.jvnc.net" to 18.10.0.11, 7/27/90 8:00am EST ..... 18 bytes from 18.10.0.11: icmp_seq=997. time=29. ms 18 bytes from 18.10.0.11: icmp_seq=998. time=31. ms 18 bytes from 18.10.0.11: icmp_seq=999. time=27. ms ----18.10.0.11 PING Statistics---- 1000 packets transmitted, 995 packets received, 0% packet loss round-trip (ms) min/avg/max = 26/51/932 ______________________________________________________________________________ Sergio Heker Phone # (609)520-2000 (until 8/18) Director, JvNCnet Phone # (609)258-2400 (after 8/18) Email "heker@nisc.jvnc.net" ______________________________________________________________________________