From Susan.M.Horvath@um.cc.umich.edu Wed Apr 1 11:16:28 1992 Received: from terminator.cc.umich.edu by merit.edu (5.65/1123-1.0) id AA10312; Wed, 1 Apr 92 11:16:28 -0500 Received: from um.cc.umich.edu by terminator.cc.umich.edu (5.65/1123-1.0) id AA02438; Wed, 1 Apr 92 11:16:18 -0500 Date: Wed, 1 Apr 92 10:49:34 EST From: Susan.M.Horvath@um.cc.umich.edu Reply-To: nsfnet-info To: Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, Douglas.E.Van.Houweling@um.cc.umich.edu, nsfnet-reports Message-Id: <12623098@um.cc.umich.edu> X-Mts-Userid: LG15 Subject: March NSFNET T1 Usage by Service NSFNET T1 Usage by Service March 1992 Service Type % Packets % Bytes ============ ========= ======= File exchange 29 52 Networked mail 21 22 Interactive 14 5 Name lookup 7 4 Other TCP/UDP services 27 16 Non TCP/UDP services 2 1 --- --- 100 100 The categories above are defined as follows: File exchange ftp: data and control (tcp ports 20, 21) Networked mail smtp, nntp, vmnet, uucp (tcp ports 25, 119, 175, 540) Interactive telnet, finger, who, login (tcp ports 23, 79, 513, udp port 513) Name lookup domain name service (udp port 53, tcp port 53) Other TCP/UDP services all tcp/udp ports not included above (e.g. irc, talk, X-windows, appletalk) Non-TCP/UDP services icmp, egp, etc. More detailed information is available for anonymous FTP from NIC.MERIT.EDU (the Merit NIC Services machine) in the file "t1-9203.ports" on the nsfnet/statistics/1992 directory. - - - - - - - - - - - - - - - - - From @pucc.Princeton.EDU:MARTIN@CEARN.BITNET Wed Apr 1 11:54:21 1992 Received: from pucc.Princeton.EDU by merit.edu (5.65/1123-1.0) id AA11506; Wed, 1 Apr 92 11:54:21 -0500 Message-Id: <9204011654.AA11506@merit.edu> Received: from CEARN.cern.ch by pucc.Princeton.EDU (IBM VM SMTP V2R2) with BSMTP id 9633; Wed, 01 Apr 92 11:53:08 EST Received: from CEARN by CEARN.cern.ch (Mailer R2.07B) with BSMTP id 4608; Wed, 01 Apr 92 18:44:47 SET Date: Wed, 01 Apr 92 18:28:44 SET From: Olivier Martin Subject: Re: March NSFNET T1 Usage by Service To: Susan.M.Horvath@um.cc.umich.edu Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, Douglas.E.Van.Houweling@um.cc.umich.edu, nsfnet-reports@merit.edu, nsfnet-info@merit.edu cc: Elise Gerich , Jessica Yu , "Stefan Fassbender (GMD/EASInet)" In-Reply-To: Message of Wed, 1 Apr 92 10:49:34 EST from Thank you for your very interesting tarffic reports, there is a question which I have been trying to get answered without much success for some time, which is the following: Why is the traffic from ASN 590 (EASINet) into the T1 backbone so small whereas the traffic to ASN 590 is so high (ratio 1/1000 in february). (To be more precise: 78.736 Megabytes In, 82.14 Gigabytes Out)! My personal explanation is that you only take into account the incoming traffic and that for some reason, accounting has been disabled at the EASINET entry into the T1 backbone, therefore only the traffic coming via alternate access points (i.e. secondary or ternary) is really accounted for, however, I could never get any confirmation of this "theory". If this theory happened to be right, I would very much appreciate that adequate mention to it be made inside the files containing the traffic statistics. Olivier - - - - - - - - - - - - - - - - - From jaw Wed Apr 1 13:36:54 1992 Received: from tyche.merit.edu by merit.edu (5.65/1123-1.0) id AA14923; Wed, 1 Apr 92 13:36:54 -0500 Received: by tyche.merit.edu (4.1/client-0.9) id AA01177; Wed, 1 Apr 92 13:36:53 EST Date: Wed, 1 Apr 92 13:36:53 EST From: jaw Message-Id: <9204011836.AA01177@tyche.merit.edu> To: MARTIN%CEARN.BITNET@pucc.Princeton.EDU Subject: March NSFNET T1 Usage by Service Cc: Douglas.E.Van.Houweling@um.cc.umich.edu, Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, epg, jaw, jyy, nsfnet-info, nsfnet-reports, smh, stf@easi.net Olivier, The use of NNStat for statistics collection on the T1 backbone has not been disabled at any point of entry. Ultimately, drastically differing in and out counts are not unusual. On average, 27% of the packets and 50% of the bytes are from ftp: Jan 1992 28% packets 50% bytes Feb 1992 27% packets 50% bytes Mar 1992 29% packets 52% bytes Using the net primarily for ftp will appear as a small amount of traffic into the backbone and a significantly larger traffic volume out. Washington University at St. Louis (MO) exhibits a similar statistical measurement: Pkts (millions) Bytes (billions) IN OUT IN OUT Dec 1991 294 157 126 12 Jan 1992 332 212 139 17 Feb 1992 338 214 142 17 Perennially, they are the 1st or 2nd highest volume net on the NSFNET, apparently due to a very large PC archive accessed primarily via ftp. Similar numbers are noted with other high volume nets. It's not surprising that other nets will show the reverse of this IN/OUT volume relationship. We hope this information helps explain your concerns. Please let us know if we might provide further clarification. With sincere apologies for the delay in sending this information on to you, and thanks to Susan Horvath for her analysis and review, Jo Ann Ward Merit/NSFNET Information Services ********************************************************************************** Message: 12625724, 33 lines Imported: 12:01pm EST, Wed Apr 1/92 Subject: Re: March NSFNET T1 Usage by Service To: Merit/NSFNET Information Services-Interested Parties, Susan M. Horvath From: MARTIN%CEARN.BITNET@pucc.Princeton.EDU Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, Douglas.E.Van.Houweling@um.cc.umich.edu, nsfnet-reports@merit.edu, nsfnet-info@merit.edu cc: Elise Gerich , Jessica Yu , "Stefan Fassbender (GMD/EASInet)" In-Reply-To: Message of Wed, 1 Apr 92 10:49:34 EST from Thank you for your very interesting tarffic reports, there is a question which I have been trying to get answered without much success for some time, which is the following: Why is the traffic from ASN 590 (EASINet) into the T1 backbone so small whereas the traffic to ASN 590 is so high (ratio 1/1000 in february). (To be more precise: 78.736 Megabytes In, 82.14 Gigabytes Out)! My personal explanation is that you only take into account the incoming traffic and that for some reason, accounting has been disabled at the EASINET entry into the T1 backbone, therefore only the traffic coming via alternate access points (i.e. secondary or ternary) is really accounted for, however, I could never get any confirmation of this "theory". If this theory happened to be right, I would very much appreciate that adequate mention to it be made inside the files containing the traffic statistics. Olivier - - - - - - - - - - - - - - - - - From sgoldste@cise.cise.nsf.gov Wed Apr 1 15:08:59 1992 Received: from cise.cise.nsf.gov by merit.edu (5.65/1123-1.0) id AA17562; Wed, 1 Apr 92 14:41:26 -0500 Received: by cise.cise.nsf.gov id ; Wed, 1 Apr 92 14:41:20 -0500 Message-Id: <9204011941.AA06615@cise.cise.nsf.gov> To: jaw Cc: MARTIN%CEARN.BITNET@pucc.princeton.edu, Douglas.E.Van.Houweling@um.cc.umich.edu, Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, epg, jyy, nsfnet-info, nsfnet-reports, smh, stf@easi.net Subject: Re: March NSFNET T1 Usage by Service In-Reply-To: Your message of "Wed, 01 Apr 92 13:36:53 EST." <9204011836.AA01177@tyche.merit.edu> Date: Wed, 01 Apr 92 14:41:12 EST From: Steve Goldstein--Ph 202-357-9717 Which just goes to illustrate that traffic-based cost-sharing models for [intercontinental] links are complicated by things like FTP where the origin address sends huge amounts of data for which it did not initiate the session. Some countries/entities turn out to be (grossly) net exporters of data. --SG - - - - - - - - - - - - - - - - - From jcurran@nic.near.net Wed Apr 1 15:35:18 1992 Received: from nic.near.net by merit.edu (5.65/1123-1.0) id AA19564; Wed, 1 Apr 92 15:35:18 -0500 Message-Id: <9204012035.AA19564@merit.edu> To: Steve Goldstein--Ph 202-357-9717 Cc: jaw, MARTIN%CEARN.BITNET@pucc.princeton.edu, Douglas.E.Van.Houweling@um.cc.umich.edu, Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, epg, jyy, nsfnet-info, nsfnet-reports, smh, stf@easi.net Subject: Re: March NSFNET T1 Usage by Service In-Reply-To: Your message of Wed, 01 Apr 92 14:41:12 -0500. <9204011941.AA06615@cise.cise.nsf.gov> Date: Wed, 01 Apr 92 15:34:48 -0500 From: John Curran -------- ] From: Steve Goldstein--Ph 202-357-9717 ] Subject: Re: March NSFNET T1 Usage by Service ] Date: Wed, 01 Apr 92 14:41:12 EST ] ] Which just goes to illustrate that traffic-based cost-sharing models for ] [intercontinental] links are complicated by things like FTP where the origin ] address sends huge amounts of data for which it did not initiate the ] session. Some countries/entities turn out to be (grossly) net exporters ] of data. --SG As transport costs decrease, it is likely that there will be a shift towards information based billing (i.e. billing for access to archives, information servers, etc.) It's interesting to consider the impact that such a shift would have on today's network service providers. Networks that exist primarily to provide access to other organizations' data may have a difficult transition ahead. /John - - - - - - - - - - - - - - - - - From @pucc.Princeton.EDU:MARTIN@CEARN.BITNET Thu Apr 2 04:51:25 1992 Received: from pucc.Princeton.EDU by merit.edu (5.65/1123-1.0) id AA10207; Thu, 2 Apr 92 04:51:25 -0500 Message-Id: <9204020951.AA10207@merit.edu> Received: from CEARN.cern.ch by pucc.Princeton.EDU (IBM VM SMTP V2R2) with BSMTP id 4793; Thu, 02 Apr 92 04:50:50 EST Received: from CEARN by CEARN.cern.ch (Mailer R2.07B) with BSMTP id 1601; Thu, 02 Apr 92 11:51:20 SET Date: Thu, 02 Apr 92 11:48:37 SET From: Olivier Martin Subject: Re: March NSFNET T1 Usage by Service To: Steve Goldstein--Ph 202-357-9717 , jaw Cc: MARTIN%CEARN.BITNET@pucc.Princeton.EDU, Douglas.E.Van.Houweling@um.cc.umich.edu Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, Elise Gerich , Jessica Yu , nsfnet-info@merit.edu, nsfnet-reports@merit.edu, smh@merit.edu, "Stefan Fassbender (GMD/EASInet)" In-Reply-To: Message of Wed, 01 Apr 92 14:41:12 EST from On Wed, 01 Apr 92 14:41:12 EST you said: >Which just goes to illustrate that traffic-based cost-sharing models for >[intercontinental] links are complicated by things like FTP where the origin >address sends huge amounts of data for which it did not initiate the >session. Some countries/entities turn out to be (grossly) net exporters >of data. --SG Yes, but I still contend that the MERIT provided traffic figures for the incoming EASINet traffic are completely wrong by a factor 1000, sorry for looking stubborn, but wrong statistics are worse than no statistics. Olivier - - - - - - - - - - - - - - - - - From @pucc.Princeton.EDU:MARTIN@CEARN.BITNET Thu Apr 2 04:48:15 1992 Received: from pucc.Princeton.EDU by merit.edu (5.65/1123-1.0) id AA10045; Thu, 2 Apr 92 04:48:15 -0500 Message-Id: <9204020948.AA10045@merit.edu> Received: from CEARN.cern.ch by pucc.Princeton.EDU (IBM VM SMTP V2R2) with BSMTP id 4781; Thu, 02 Apr 92 04:47:40 EST Received: from CEARN by CEARN.cern.ch (Mailer R2.07B) with BSMTP id 1555; Thu, 02 Apr 92 11:48:11 SET Date: Thu, 02 Apr 92 11:21:17 SET From: Olivier Martin Subject: Re: March NSFNET T1 Usage by Service To: jaw, MARTIN%CEARN.BITNET@pucc.Princeton.EDU Cc: Douglas.E.Van.Houweling@um.cc.umich.edu Merit/NSFNET.Information.Services-Interested.Parties@um.cc.umich.edu, Elise Gerich , Jessica Yu , nsfnet-info@merit.edu, nsfnet-reports@merit.edu, smh@merit.edu, "Stefan Fassbender (GMD/EASInet)" In-Reply-To: Message of Wed, 1 Apr 92 13:36:53 EST from On Wed, 1 Apr 92 13:36:53 EST you said: >Olivier, > >The use of NNStat for statistics collection on the T1 backbone has >not been disabled at any point of entry. Ultimately, drastically >differing in and out counts are not unusual..................... it may be, but in the case of CERN they are, as CERN is also a data source. >................................................................ >Using the net primarily for ftp will appear as a small amount of >traffic into the backbone and a significantly larger traffic >volume out. >................................................................ >We hope this information helps explain your concerns. Please let >us know if we might provide further clarification. > The reason I am very suspicious, is that we are collecting the cisco accounting frequently enough that we do not lose too much of it, and we are therefore in a good position to cross-check our results with those of MERIT. Whereas, our figures agree with the NSFNet ones regarding the traffic out of the T1 backbone, there is a complete mismatch regarding the traffic into the T1 backbone. For example, MERIT reports 358,200 bytes coming from 128.141, the main CERN network, whereas we measure 5,239 Gigabytes (factor 14,000). However, we agree for the traffic to CERN from the US, 5,212 Gigabytes (MERIT), 5,239 Gigabytes (CERN). Back to EASINet as a whole, I do not think it is realistic to believe that the real traffic patterns are as distorted as I reported yesterday, namely: From EASINet--->NSFNet 78.73 Megabytes (which would be less than the CERN originated traffic, according to us) **** YES, this is Megabytes, NOT in Gigabytes ************ From NSFNet---->EASINet 82.14 Gigabytes (which is probably all right, but we can only crosscheck part of it because some of the routers at CERN are not controlled by us, what we could measure is: 43.73 GBytes). To put these figures in perspective, the International Connection Manager (ICM) which is handling the lines from Cornell to Stokholm (Nordunet) and INRIA (France) would have, according to MERIT: 68.29 Gigabytes (out) and 43.42 Gigabytes (in) which is more like the 1/3 2/3 rule of thumb which we observed in 1991, and which shows that even though the USA are exporting more data than they receive, the balance is not that bad, especially considering the small number of FTP servers in Europe, Finland excepted. Olivier - - - - - - - - - - - - - - - - - From bsb Fri Apr 3 08:06:05 1992 Received: by merit.edu (5.65/1123-1.0) id AA23726; Fri, 3 Apr 92 08:06:10 -0500 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA23718; Fri, 3 Apr 92 08:06:05 -0500 Received: by home.merit.edu (4.1/client-0.9) id AA13256; Fri, 3 Apr 92 08:06:04 EST Date: Fri, 3 Apr 92 08:06:04 EST Message-Id: <9204031306.AA13256@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ----------- Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 138.165 REGION-CS1 184 164 NCTC, NAVTASC, Building 31, Redlind Drive, Cheltanhem, MD 20397, USA 138.160 NAVNET 184 164 Naval Air Station, Building 603, Pensacola, FL 32508, USA 142.132 UWPGNET 603 601 University of Winnipeg, Computer Services, Winnipeg, MB, R3B 2E9, CANADA 192.149.223 USPS-NET 86 279 US Postal Service, 475 L'Enfant Plaza, SW, Washington, DC 20260-6444, USA 192.147.218 REDE-PARA 293 291 Universidade Federal Do Para, Belem - Para' - BRAZIL 192.147.210 UFPA 293 291 Universidade Federal Do Para, Belem - Para' - BRAZIL 192.147.148 LON-UNIV-2 274 60 University of London, London, UNITED KINGDOM 192.146.229 GOELDI 293 291 Emilio Goeldi Museum, Belem - Para' - BRAZIL 192.102.241 SURA-NET1 86 279 SURAnet, 8400 Balt. Boulevard, College Park, MD 20740, USA 192.94.173 GLERL 233 177 Great Lakes Environmental Research Laboratory, Michigan, USA 192.54.253 TCLARINET 200 201 ClariNet Communications Corp., 1113 Lochinvar Ave, Sunnyvale, CA 94087, USA 158.222 LLOYD2 200 201 Lloyd and Associates, 3420 Sudbury Rd, Cameron Park, CA 95682, USA 155.247 TEMPLE-EDU 1206 204 Temple University, Computer Room 763, Broad & Montgomery Ave. Philadelphia, PA 19122, USA 192.150.177 MANLAN-1 274 60 University of Manchester, Computing Centre, Oxford Road, Manchester, M13 9PL, UNITED KINGDOM 192.150.122 AIXSERV-DMZ 750 756 IBM Corporation, 11400 Burnet Road, Internal Zip 2900, Building 42, Austin, TX 78758, USA 192.149.148 NGDC 209 210 National Geophysical Data Center, NOAA/NGDC, 325 Broadway EGC4, Boulder, CO 80303, USA 192.138.214 SUFFOLK-NET3 560 281 Suffolk University, 8 Ashburton Place, Boston, MA 02108, USA 192.153.23 PPLD-NET 209 210 Pikes Peak Library District, 5550 North Unios Blvd, Colorado Springs, CO 80918, USA 192.153.10 COGWHEEL-COM 209 210 COGWHEEL, INC., POB 1354, BOULDER, CO 80306-1354, USA 192.138.213 SUFFOLK-NET2 560 281 Suffolk University, 8 Ashburton Place, Boston, MA 02108, USA 158.98 TRANSARC-B 1206 204 Transarc Corporation, 707 Grant St., Pittsburgh, PA 15219, USA 137.182 PGCOM 750 756 Procter and Gamble, Procter and Gamble Plaza, P.O. Box 599, Cincinnati, OH 45201, USA 150.161 UFPE-ANPE 293 291 Universidade Federal de Pernambuco, Caixa Postal 7851 - DEP 50739, Recife - PE, BRAZIL Total NSFNET T1 announced networks: 4998 T3 network: ----------- Network IP: 137.182 Network Name: PGCOM Location: Procter and Gamble, Procter and Gamble Plaza, P.O. Box 599, Cincinnati, OH 45201, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 152.159 Network Name: MHP-NET Location: McGraw-Hill, Inc.,, Princeton Rd.,, Highstown, NJ 08520, USA Country Code: US 1:1324 ANS New York City - DNSS 35 Network IP: 158.98 Network Name: TRANSARC-B Location: Transarc Corporation, 707 Grant St., Pittsburgh, PA 15219, USA Country Code: US 1:1206 PSCNET Network IP: 158.222 Network Name: LLOYD2 Location: Lloyd and Associates, 3420 Sudbury Rd, Cameron Park, CA 95682, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.54.253 Network Name: TCLARINET Location: ClariNet Communications Corp., 1113 Lochinvar Ave, Sunnyvale, CA 94087, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.94.173 Network Name: GLERL Location: Great Lakes Educational Research Laboratory, Michigan, USA Country Code: US 1:237 MERIT network Network IP: 192.102.241 Network Name: SURA-NET1 Location: SURAnet, 8400 Balt. Boulevard, College Park, MD 20740, USA Country Code: US 1:86 SURANET Regional Network 2:279 Georgia Tech Network IP: 192.149.223 Network Name: USPS-NET Location: US Postal Service, 475 L'Enfant Plaza, SW, Washington, DC 20260-6444, USA Country Code: US 1:86 SURANET Regional Network 2:279 Georgia Tech Network IP: 192.150.122 Network Name: AIXSERV-DMZ Location: IBM Corporation, 11400 Burnet Road, Internal Zip 2900, Building 42, Austin, TX 78758, USA Country Code: US 1:1782 AIXSERV-AS, ENSS 174 Total T3 configured networks: 2728 ************************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From tli@cisco.com Fri Apr 3 13:17:32 1992 Received: from lager.cisco.com by merit.edu (5.65/1123-1.0) id AA05638; Fri, 3 Apr 92 13:17:32 -0500 Received: by lager.cisco.com; Fri, 3 Apr 92 10:17:30 -0800 Date: Fri, 3 Apr 92 10:17:30 -0800 From: Tony Li Message-Id: <9204031817.AA28493@lager.cisco.com> To: bgpd, regional-techs Subject: FYI: New test version of cisco BGP I have a new test image which I believe will support multiple BGP neighbors without a problem. If you would like to try it, please pick up testtli.bgp2 and/or testtli.bgp2-igs from ftp.cisco.com. This version is based on 8.3(2.3). This code has been tested somewhat, but should be considered armed and dangerous. These changes will be incorporated into a future 8.3 build. I will also be modifying these changes to work in 9.0 in the near future. Tony - - - - - - - - - - - - - - - - - From donnab@CERF.NET Mon Apr 6 18:51:17 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA21821; Mon, 6 Apr 92 18:51:17 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA28640; Mon, 6 Apr 92 15:51:06 PDT Date: Mon, 6 Apr 92 15:51:06 PDT From: Donna Bigley Message-Id: <9204062251.AA28640@nic.cerf.net> To: broidoj@Sds.Sdsc.Edu, help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, March 30, 1992 ############################################################################### This is the CERFnet weekly activity report for the period of Monday, March 30th through Sunday, April 5th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 5-april-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 872 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: MON. 3-30-92 10:04 TIME ENDED: MON. 3-30-92 13:53 TIME ELAPSED: 3 hours 49 min. (Intermittent Outages) REASON: Equipment Trouble TICKET #: 880 SITE: SPARTA SITES AFFECTED: SPARTA TIME STARTED: MON. 3-30-92 12:12 TIME ENDED: MON. 3-30-92 12:19 TIME ELAPSED: 7 min. REASON: Power Outage TICKET #: 877 SITE: DATAPRODUCTS SITES AFFECTED: DATAPRODUCTS TIME STARTED: MON. 3-30-92 12:50 TIME ENDED: MON. 3-30-92 17:28 TIME ELAPSED: 4 hours 38 min. (Intermittent Access) REASON: Link Failure TICKET #: 879 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: MON. 3-30-92 17:25 TIME ENDED: TUE. 3-31-92 01:24 TIME ELAPSED: 7 hours 59 min. (Intermittent Outages) REASON: Link Failure TICKET #: 881 SITE: DATAPRODUCTS SITES AFFECTED: DATAPRODUCTS TIME STARTED: TUE. 3-31-92 10:28 (Telco Testing) TIME ENDED: TUE. 3-31-92 11:42 TIME STARTED: TUE. 3-31-92 13:27 TIME ENDED: TUE. 3-31-92 15:10 TIME ELAPSED: 2 hours 57 min. (Intermittent Outages) REASON: Link Failure TICKET #: 850 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: TUE. 3-31-92 23:16 TIME ENDED: TUE. 3-31-92 23:31 TIME ELAPSED: 15 min. REASON: Link Failure TICKET #: 882 SITE: ENSS T3 SITES AFFECTED: ENSS T3 TIME STARTED: WED. 4-1-92 09:08 TIME ENDED: WED. 4-1-92 09:14 TIME ELAPSED: 6 min. REASON: Equipment Trouble (Hung FDDI Interface) TICKET #: 884 SITE: Hang10 SITES AFFECTED: SDSU, BIOSYM, AGI, SCIENCE HORIZONS, XEROX, UCR, LLUMC, and CERFnet NETBLAZER. TIME STARTED: WED. 4-1-92 11:11 TIME ENDED: WED. 4-1-92 11:30 TIME STARTED: WED. 4-1-92 12:26 TIME ENDED: WED. 4-1-92 12:30 TIME ELAPSED: 23 min. REASON: Equipment Trouble TICKET #: 885 SITE: BIOSYM SITES AFFECTED: BIOSYM TIME STARTED: THU. 4-2-92 10:47 TIME ENDED: FRI. 4-3-92 17:49 TIME ELAPSED: 1 day 7 hours 2 min. REASON: Site Scheduled Maintenance TICKET #: 893 SITE: QUOTRON SITES AFFECTED: QUOTRON TIME STARTED: FRI. 4-3-92 23:27 TIME ENDED: SAT. 4-4-92 11:16 TIME ELAPSED: 11 hours 49 min. REASON: Power Outage TICKET #: 894 SITE: CITY OF HOPE SITES AFFECTED: CITY OF HOPE TIME STARTED: SAT. 4-4-92 23:46 TIME ENDED: SUN. 4-5-92 00:20 TIME ELAPSED: 34 min. REASON: Unscheduled Site Maintenance TICKET #: 888 SITE: UCLA SITES AFFECTED: DATAPRODUCTS, ISX, SMC, QUOTRON, PEPPERDINE, UCSB, UCLA DIAL N' CERF, UCLA NETBLAZER, AND LOS NETTOS. TIME STARTED: SUN. 4-5-92 14:05 TIME ENDED: SUN. 4-5-92 17:53 TIME ELAPSED: 3 hours 48 min. REASON: Power Outage TICKET #: 890 SITE: UCLA NetBlazer SITES AFFECTED: UCLA NetBlazer TIME STARTED: SUN. 4-5-92 14:06 TIME ENDED: MON. 4-6-92 08:15 TIME ELAPSED: 18 hours 9 min. REASON: Equipment Trouble ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps No Capacities for this week. (New Line) SDSC/CALTECH 1.544 mbps 11.5% 11:00 SDSC/UCI 1.544 mbps 07.5% 18:00 SDSC/UCLA 1.544 mbps 05.7% 12:00 SDSC/UCOP 1.544 mbps 03.4% 11:00 UCI/UCLA 1.544 mbps 00.3% 17:00 SDSC/UCR 512 kbps 02.1% 19:00 UCLA/UCSB 512 kbps 08.8% 13:00 SDSC/AGI 1.544 mbps 00.1% 16:00 SDSC/BIOSYM 1.544 mbps 00.2% 14:00 SDSC/GA 1.544 mbps 00.3% 12:00 SDSC/GD 1.544 mbps 02.2% 08:00 SDSC/SAIC 1.544 mbps 00.8% 12:00 SDSC/SCAQMD 1.544 mbps 00.1% 12:00 SDSC/SDSU 1.544 mbps 01.4% 19:00 UCI/CSU CO(SWRL) 1.544 mbps 02.1% 16:00 UCOP/APPLE 1.544 mbps 00.9% 19:00 UCOP/CISCO 1.544 mbps 00.8% 12:00 UCR/LLUMC 1.544 mbps 00.1% 10:00 CALTECH/CADAM 56 kbps 00.5% 18:00 CALTECH/CITY OF HOPE 56 kbps 00.2% 15:00 CALTECH/CLAREMONT 56 kbps 21.4% 15:00 CALTECH/DISNEY 56 kbps 04.3% 10:00 CALTECH/OXY 56 kbps 10.2% 10:00 SDSC/AJS 56 kbps 01.4% 10:00 SDSC/KOREA 56 kbps 09.1% 00:00 SDSC/QUALCOMM 56 kbps 09.0% 10:00 SDSC/SCIH 56 kbps No Capacities available for this week. SDSC/USD 56 kbps 07.7% 13:00 SDSC/USIU 56 kbps 00.5% 12:00 SDSC/XEROX 56 kbps 00.6% 11:00 UCI/CMD 56 kbps 03.3% 20:00 UCI/EMULEX 56 kbps 01.2% 14:00 UCI/FULLERTON 56 kbps 01.5% 13:00 UCI/HUGHES 56 kbps 09.0% 11:00 UCI/MTI 56 kbps 03.2% 08:00 UCI/SPARTA 56 kbps 03.8% 12:00 UCI/UNOCAL 56 kbps 08.1% 11:00 UCLA/ISX 56 kbps 01.2% 17:00 UCLA/PEPPERDINE 56 kbps 01.9% 11:00 UCLA/QUOTRON 56 kbps 09.3% 17:00 UCLA/SMC 56 kbps 02.2% 00:00 UCOP/FARALLON 56 kbps 05.3% 17:00 UCOP/INTEL 56 kbps No Capacities available for this week. UCOP/LSIL 56 kbps 08.1% 20:00 UCOP/NETLABS 56 kbps 13.7% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Apr. 6th, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 08 days 05 hours 41 minutes SDSC LongBoard [134.24.99.254] Up: 03 days 03 hours 35 minutes [Unknown] SDSC Drzog [132.249.16.13] Up: 17 days 07 hours 00 minutes SDSC Hang10 [132.249.16.15] Up: 04 days 10 hours 46 minutes [Equipment Trouble - See Ticket #884] SDSC Drzog [132.249.16.13] Up: 17 days 07 hours 00 minutes UCI [128.200.1.101] Up: 87 days 16 hours 07 minutes UCLA [128.97.130.10] Up: 00 days 06 hours 28 minutes [Power Outage - See Ticket #888] UCOP [134.24.52.112] Up: 12 days 16 hours 38 minutes UCR [134.24.108.105] Up: 15 days 06 hours 48 minutes CERF 1544 AGI [134.24.202.110] Up: 52 days 13 hours 54 minutes APPLE [134.24.70.200] Up: 161 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 02 days 05 hours 27 minutes [Unknown] CISCO Systems [134.24.54.200] Up: 26 days 04 hours 20 minutes CSUCO/SWRL [130.150.102.200] Up: 03 days 18 hours 49 minutes [Unknown] GA [134.24.221.200] Up: 16 days 19 hours 56 minutes GD [134.24.60.200] Up: 35 days 13 hours 31 minutes LLUMC [134.24.208.200] Up: 138 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 92 days 08 hours 34 minutes SCAQMD [134.24.234.200] Up: 108 days 14 hours 27 minutes SDSU [192.77.100.101] Up: 118 days 16 hours 31 minutes UCSB [134.24.107.107] Up: 138 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 79 days 14 hours 17 minutes CADAM [134.24.229.200] Up: 61 days 13 hours 01 minutes CLAREMONT [134.24.206.109] Up: 09 days 17 hours 39 minutes CMD [134.24.218.200] Up: 69 days 13 hours 14 minutes DATAPRODUCTS [134.24.211.104] Up: 05 days 09 hours 33 minutes [Unknown] DISNEY [134.24.207.211] Up: 67 days 00 hours 33 minutes EMULEX [134.24.209.212] Up: 113 days 15 hours 48 minutes FARALLON [134.24.56.200] Up: 07 days 02 hours 24 minutes FULLERTON [134.24.214.217] Up: 21 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 143 days 07 hours 21 minutes INTEL [134.24.55.200] Up: 08 days 11 hours 34 minutes LSIL [134.24.72.200] Up: 57 days 13 hours 08 minutes MTI [134.24.216.100] Up: 93 days 13 hours 39 minutes NETLABS [134.24.71.200] Up: 11 days 08 hours 51 minutes OXY [134.24.205.108] Up: 30 days 15 hours 26 minutes PEPPERDINE [134.24.203.218] Up: 43 days 13 hours 14 minutes QUALCOMM [134.24.200.201] Up: 03 days 13 hours 34 minutes [Equipment Trouble] QUOTRON [134.24.230.202] Up: 01 days 12 hours 00 minutes [Power Outage - See Ticket #893] SANTA MONICA [134.24.210.219] Up: 23 days 12 hours 40 minutes SCI-HOR [134.24.109.205] Up: 10 days 04 hours 27 minutes SERI/KOREA [134.24.223.200] Up: 16 days 16 hours 06 minutes SPARTA [134.24.215.200] Up: 06 days 10 hours 57 minutes [Power Outage - See Ticket #880] UNOCAL [134.24.217.200] Up: 31 days 01 hours 57 minutes USD [134.24.201.106] Up: 10 days 06 hours 12 minutes USIU [134.24.222.215] Up: 274 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 158 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 27 days 05 hours 09 minutes DNC-UCI [134.24.2.2] Up: 89 days 03 hours 24 minutes DNC-UCLA [134.24.3.2] Up: 00 days 06 hours 25 minutes [Power Outage - See Ticket #888] DNC-CALTECH [134.24.4.2] Up: 08 days 05 hours 42 minutes DNC-UCOP [134.24.5.2] Up: 57 days 08 hours 58 minutes - - - - - - - - - - - - - - - - - From bsb Tue Apr 7 07:16:36 1992 Received: by merit.edu (5.65/1123-1.0) id AA10405; Tue, 7 Apr 92 07:16:39 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA10401; Tue, 7 Apr 92 07:16:36 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA02898; Tue, 7 Apr 92 07:16:35 EDT Date: Tue, 7 Apr 92 07:16:35 EDT Message-Id: <9204071116.AA02898@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 147.33 CHEMNET 590 Prague Institute of Chemical Technology, Computer Center, Technicka 5, Prague 6 166 28, CZECHOSLOVAKIA 134.196 TIMPLEX-NET 97 750 Timplex, 400 Chestnut Ridge Rd., Woodcliff Lk, NJ 07675, USA 131.219 PPL-NET 701 702 Utah Power and Light, 1407 W. North Temple, Salt Lake City, UT 84140 USA 192.147.164 NWNET14 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.163 NWNET13 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.161 NWNET11 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 158.170 INTER-CHILE2 86 279 SECOM, MATUCANA 28-D, ESTACION CENTRAL, SANTIAGO, CHILE 157.139 NYH 97 750 New York Hospital, 525 East 68th Street, New York NY 10021, USA 155.36 NEMC-NET 1384 1383 New England Medical Center Hospital, 35 Kneeland Street, Boston, MA 02111, USA 192.153.155 CNPQ-C-A-NET 293 291 CNPQ, CSPR/SIN, Av W/3 Norte, Quadra 507, Bloco B, Brasilia, DF, Brazil 192.153.120 BR-UFSM 293 291 Universidade Federal de Santa Maria, Cidade Universitaria, 97119 - Santa Maria - RS - BRAZIL 192.152.5 PRS-NET 97 750 Princeton Regional Schools, Princeton High School, 151 Moore Street, Princeton, NJ 08540, USA 192.149.147 SPIE-NET 685 73 SPIE-The International Society for Optical Eng, PO Box 10, Bellingham, WA 98227-0010, USA 192.147.239 CATLIN 685 73 The Catlin Gabel School, 8825 SW Barnes Rd., Portland, OR 97225, USA 192.147.167 NWNET17 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.166 NWNET16 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.165 NWNET15 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Total T1 announced networks: 5012 T3 Network: ---------- Network IP: 192.152.5 Network Name: PRS-NET1 Location: Princeton Regional Schools, Princeton High School, 151 Moore Street, Princeton, NJ 08540, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 134.196 Network Name: TIMPLEX-NET Location: Timplex, 400 Chestnut Ridge Rd., Woodcliff Lk, NJ 07675, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 131.219 Network Name: PPL-NET Location: Utah Power and Light, 1407 W. North Temple, Salt Lake City, UT 84140 USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 157.139 Network Name: NYH Location: New York Hospital, 525 East 68th Street, New York NY 10021, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 155.36 Network Name: NEMC-NET Location: New England Medical Center Hospital, 35 Kneeland Street, Boston, MA 02111, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Total configured T3 networks: 5012 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From nwg-owner Tue Apr 7 11:51:07 1992 Received: by merit.edu (5.65/1123-1.0) id AA19388; Tue, 7 Apr 92 11:51:23 -0400 Received: from is.rice.edu by merit.edu (5.65/1123-1.0) id AA19377; Tue, 7 Apr 92 11:51:07 -0400 Received: from san-miguel.is.rice.edu by is.rice.edu (AA06307); Tue, 7 Apr 92 10:51:05 CDT Received: by san-miguel.is.rice.edu (AA01005); Tue, 7 Apr 92 10:51:04 CDT From: bmanning@is.rice.edu (William Manning) Message-Id: <9204071551.AA01005@san-miguel.is.rice.edu> Subject: template To: nsfnet-admin Date: Tue, 7 Apr 92 10:51:03 CDT Cc: nwg X-Mailer: ELM [version 2.3 PL8] Is there an update to the announcment template? v5.0 still references the interim NSF AUP. -- Regards, Bill Manning bmanning@rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892 - - - - - - - - - - - - - - - - - From nwg-owner Tue Apr 7 14:50:53 1992 Received: by merit.edu (5.65/1123-1.0) id AA25788; Tue, 7 Apr 92 14:50:59 -0400 Received: from aotearoa.sura.net by merit.edu (5.65/1123-1.0) id AA25784; Tue, 7 Apr 92 14:50:53 -0400 Received: by aotearoa.sura.net with SMTP (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA17439; Tue, 7 Apr 92 14:50:46 -0400 Message-Id: <9204071850.AA17439@aotearoa.sura.net> To: "Belinda Sue Blair" Cc: nwg, noc@sura.net Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of "Tue, 07 Apr 92 07:16:35 EDT." <9204071116.AA02898@home.merit.edu> Date: Tue, 07 Apr 92 14:50:45 -0400 From: Erik Sherk > The following networks have been added to the NSFNET policy-based routing > database: > > T1 Network: > ---------- > > Total T1 announced networks: 5012 > > > T3 Network: > ---------- > > Total configured T3 networks: 5012 > > ***************************************************************** Belinda, Is this right? Are there really 5012 T3 routes? Erik Sherk sherk@sura.net - - - - - - - - - - - - - - - - - From nwg-owner Tue Apr 7 15:36:24 1992 Received: by merit.edu (5.65/1123-1.0) id AA27439; Tue, 7 Apr 92 15:36:30 -0400 Received: from MrBill.CAnet.CA by merit.edu (5.65/1123-1.0) id AA27432; Tue, 7 Apr 92 15:36:24 -0400 Received: by MrBill.CAnet.CA id <105487>; Tue, 7 Apr 1992 15:36:02 +0100 From: Dennis Ferguson To: sherk@sura.net Subject: Re: Additions to the NSFNET policy-based routing database Cc: bsb, noc@sura.net, nwg Message-Id: <92Apr7.153602bst.105487@MrBill.CAnet.CA> Date: Tue, 7 Apr 1992 15:35:49 +0100 Erik, There may be 5000 networks in the NSFnet policy database, but the biggest routing table I've ever seen so far is about 3850. The difference between the size of the NSFnet policy database and the number of networks actually being carried in Internet routing was on the order of 400 networks for the longest time, but took a big jump last fall for some reason. Dennis - - - - - - - - - - - - - - - - - From nwg-owner Tue Apr 7 15:52:26 1992 Received: by merit.edu (5.65/1123-1.0) id AA28183; Tue, 7 Apr 92 15:52:28 -0400 Received: from aotearoa.sura.net by merit.edu (5.65/1123-1.0) id AA28179; Tue, 7 Apr 92 15:52:26 -0400 Received: by aotearoa.sura.net with SMTP (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA17587; Tue, 7 Apr 92 15:52:12 -0400 Message-Id: <9204071952.AA17587@aotearoa.sura.net> To: Dennis Ferguson Cc: bsb, noc@sura.net, nwg, sherk@sura.net Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of "Tue, 07 Apr 92 15:35:49 BST." <92Apr7.153602bst.105487@MrBill.CAnet.CA> Date: Tue, 07 Apr 92 15:52:11 -0400 From: Erik Sherk > Erik, > > There may be 5000 networks in the NSFnet policy database, but the biggest > routing table I've ever seen so far is about 3850. The difference between > the size of the NSFnet policy database and the number of networks actually > being carried in Internet routing was on the order of 400 networks for the > longest time, but took a big jump last fall for some reason. > > Dennis Dennis, But last week there were on the order of ~4900 T1 networks and ~2700 T3 networks. I have been watching this closely, since I am waiting for the time that it will be more efficient to hear T1 only routes from the NSS and point default at the ENSS. Erik - - - - - - - - - - - - - - - - - From jyy Tue Apr 7 17:23:28 1992 Received: by merit.edu (5.65/1123-1.0) id AA00918; Tue, 7 Apr 92 17:23:33 -0400 Received: from kiddo.merit.edu by merit.edu (5.65/1123-1.0) id AA00913; Tue, 7 Apr 92 17:23:28 -0400 Received: Tue, 7 Apr 92 17:21:31 -0400 by kiddo.merit.edu (AIX/1.6) Date: Tue, 7 Apr 92 17:21:31 -0400 From: Jessica Yu Message-Id: <9204072121.AA18405@kiddo.merit.edu> To: dennis@MrBill.CAnet.CA, sherk@sura.net Subject: Re: Additions to the NSFNET policy-based routing database Cc: bsb, noc@sura.net, nwg Erik, The total net numbers CONFIGURED in the NSFNET policy database <> the total routes actually ADVERTISED to the backbone. The number that announced to nwg every Tue and Fri is the configured number. In order to get the actually advertised routes to T1, get on your T1 nss and do a netstat -Nn |wc. That is the real time advertised number, it may fractuate a bit due to the tempary outage of particular networks. But you will get a general idea of the number. --Jessica - - - - - - - - - - - - - - - - - From jyy Tue Apr 7 17:52:23 1992 Received: by merit.edu (5.65/1123-1.0) id AA01895; Tue, 7 Apr 92 17:52:29 -0400 Received: from kiddo.merit.edu by merit.edu (5.65/1123-1.0) id AA01890; Tue, 7 Apr 92 17:52:23 -0400 Received: Tue, 7 Apr 92 17:50:26 -0400 by kiddo.merit.edu (AIX/1.6) Date: Tue, 7 Apr 92 17:50:26 -0400 From: Jessica Yu Message-Id: <9204072150.AA17003@kiddo.merit.edu> To: dennis@MrBill.CAnet.CA, sherk@sura.net Subject: Re: Additions to the NSFNET policy-based routing database Cc: bsb, noc@sura.net, nwg Erik, My response is based on the mail you exchanged with Dennis which I thought you had a question of why it is announced 5000 some nets on T1 but actually you do not get that much. Apparently you were asking something else, looking at your original message. Here is the answer of your original question: >> T1 Network: >> ---------- >> >> Total T1 announced networks: 5012 >> >> >> T3 Network: >> ---------- >> >> Total configured T3 networks: 5012 >Is this right? Are there really 5012 T3 routes? I think it is a typo. The number of nets CONFIGURED on T3 as of today is 2731. --Jessica Received: by merit.edu (5.65/1123-1.0) id AA25788; Tue, 7 Apr 92 14:50:59 -0400 Received: from aotearoa.sura.net by merit.edu (5.65/1123-1.0) id AA25784; Tue, 7 Apr 92 14:50:53 -0400 Received: by aotearoa.sura.net with SMTP (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA17439; Tue, 7 Apr 92 14:50:46 -0400 Message-Id: <9204071850.AA17439@aotearoa.sura.net> To: "Belinda Sue Blair" Cc: nwg@merit.edu, noc@sura.net Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of "Tue, 07 Apr 92 07:16:35 EDT." <9204071116.AA02898@home.merit.edu> Date: Tue, 07 Apr 92 14:50:45 -0400 From: Erik Sherk > The following networks have been added to the NSFNET policy-based routing > database: > > T1 Network: > ---------- > > Total T1 announced networks: 5012 > > > T3 Network: > ---------- > > Total configured T3 networks: 5012 > > ***************************************************************** Belinda, Is this right? Are there really 5012 T3 routes? Erik Sherk sherk@sura.net - - - - - - - - - - - - - - - - - From nwg-owner Tue Apr 7 18:17:41 1992 Received: by merit.edu (5.65/1123-1.0) id AA02927; Tue, 7 Apr 92 18:17:43 -0400 Received: from aotearoa.sura.net by merit.edu (5.65/1123-1.0) id AA02923; Tue, 7 Apr 92 18:17:41 -0400 Received: by aotearoa.sura.net with SMTP (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA17806; Tue, 7 Apr 92 18:17:40 -0400 Message-Id: <9204072217.AA17806@aotearoa.sura.net> To: Jessica Yu Cc: noc@sura.net, nwg Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of "Tue, 07 Apr 92 17:21:31 EDT." <9204072121.AA18405@kiddo.merit.edu> Date: Tue, 07 Apr 92 18:17:39 -0400 From: Erik Sherk > Erik, > > The total net numbers CONFIGURED in the NSFNET policy database <> the total > routes actually ADVERTISED to the backbone. The number that announced > to nwg every Tue and Fri is the configured number. In order to get the > actually advertised routes to T1, get on your T1 nss and do a netstat -Nn |wc. > That is the real time advertised number, it may fractuate a bit due to the > tempary outage of particular networks. But you will get a general idea of > the number. > > --Jessica Jessica, I understand the difference between configured vs. announced networks. That is not what I am asking. I must have been unclear in my previous question, let me try again. If you grep "Total" from the March 10th network configuration announcment, you get this: aotearoa:[~/Mail/inbox] grep Total inbox/806 Total NSFNET T1 announced networks: 4835 Total NSFNET T3 announced networks: 2501 The total number of networks on each of the backbones has been different in all of the announcements send out by Merit that I have seen. But today, we find that they are the same: aotearoa:[~/Mail/inbox] grep Total inbox/1233 Total T1 announced networks: 5012 Total configured T3 networks: 5012 Oh, I see! You have changed the announcment to list "T1 announced" and "T3 configured". Would it be too much trouble to ask you to go back to the old style? Erik - - - - - - - - - - - - - - - - - From bsb Tue Apr 7 18:15:35 1992 Received: by merit.edu (5.65/1123-1.0) id AA02878; Tue, 7 Apr 92 18:15:38 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA02873; Tue, 7 Apr 92 18:15:35 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA17104; Tue, 7 Apr 92 18:15:34 EDT Date: Tue, 7 Apr 92 18:15:34 EDT Message-Id: <9204072215.AA17104@home.merit.edu> To: nwg Subject: Correction: Additions to the NSFNET database Er, I would like to make a correction regarding the number of T3 configured networks :-): Apologies for any confusion. The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 147.33 CHEMNET 590 Prague Institute of Chemical Technology, Computer Center, Technicka 5, Prague 6 166 28, CZECHOSLOVAKIA 134.196 TIMPLEX-NET 97 750 Timplex, 400 Chestnut Ridge Rd., Woodcliff Lk, NJ 07675, USA 131.219 PPL-NET 701 702 Utah Power and Light, 1407 W. North Temple, Salt Lake City, UT 84140 USA 192.147.164 NWNET14 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.163 NWNET13 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.161 NWNET11 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 158.170 INTER-CHILE2 86 279 SECOM, MATUCANA 28-D, ESTACION CENTRAL, SANTIAGO, CHILE 157.139 NYH 97 750 New York Hospital, 525 East 68th Street, New York NY 10021, USA 155.36 NEMC-NET 1384 1383 New England Medical Center Hospital, 35 Kneeland Street, Boston, MA 02111, USA 192.153.155 CNPQ-C-A-NET 293 291 CNPQ, CSPR/SIN, Av W/3 Norte, Quadra 507, Bloco B, Brasilia, DF, Brazil 192.153.120 BR-UFSM 293 291 Universidade Federal de Santa Maria, Cidade Universitaria, 97119 - Santa Maria - RS - BRAZIL 192.152.5 PRS-NET 97 750 Princeton Regional Schools, Princeton High School, 151 Moore Street, Princeton, NJ 08540, USA 192.149.147 SPIE-NET 685 73 SPIE-The International Society for Optical Eng, PO Box 10, Bellingham, WA 98227-0010, USA 192.147.239 CATLIN 685 73 The Catlin Gabel School, 8825 SW Barnes Rd., Portland, OR 97225, USA 192.147.167 NWNET17 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.166 NWNET16 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA 192.147.165 NWNET15 685 73 NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Total T1 announced networks: 5012 T3 Network: ---------- Network IP: 192.152.5 Network Name: PRS-NET1 Location: Princeton Regional Schools, Princeton High School, 151 Moore Street, Princeton, NJ 08540, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 134.196 Network Name: TIMPLEX-NET Location: Timplex, 400 Chestnut Ridge Rd., Woodcliff Lk, NJ 07675, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 131.219 Network Name: PPL-NET Location: Utah Power and Light, 1407 W. North Temple, Salt Lake City, UT 84140 USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 157.139 Network Name: NYH Location: New York Hospital, 525 East 68th Street, New York NY 10021, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 155.36 Network Name: NEMC-NET Location: New England Medical Center Hospital, 35 Kneeland Street, Boston, MA 02111, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Total configured T3 networks: 2731 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* Thanks, -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From nwg-owner Tue Apr 7 18:23:22 1992 Received: by merit.edu (5.65/1123-1.0) id AA03275; Tue, 7 Apr 92 18:23:25 -0400 Received: from aotearoa.sura.net by merit.edu (5.65/1123-1.0) id AA03271; Tue, 7 Apr 92 18:23:22 -0400 Received: by aotearoa.sura.net with SMTP (5.65b/($Id: sendmail.cf,v 1.17 1991/02/11 14:07:23 jmalcolm Exp $)) id AA17832; Tue, 7 Apr 92 18:23:17 -0400 Message-Id: <9204072223.AA17832@aotearoa.sura.net> To: Jessica Yu Cc: dennis@MrBill.CAnet.CA, sherk@sura.net, bsb, noc@sura.net, nwg, sherk@sura.net Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of "Tue, 07 Apr 92 17:50:26 EDT." <9204072150.AA17003@kiddo.merit.edu> Date: Tue, 07 Apr 92 18:23:16 -0400 From: Erik Sherk > Erik, > > My response is based on the mail you exchanged with Dennis which I thought > you had a question of why it is announced 5000 some nets on T1 but actually > you do not get that much. Apparently you were asking something else, > looking at your original message. Here is the answer of your original > question: > > >> T1 Network: > >> ---------- > >> > >> Total T1 announced networks: 5012 > >> > >> > >> T3 Network: > >> ---------- > >> > >> Total configured T3 networks: 5012 > > >Is this right? Are there really 5012 T3 routes? > > I think it is a typo. The number of nets CONFIGURED on T3 as of today is 2731. > > --Jessica Jessica, Confusion reigns again :-) This is exactly what had me puzzled. Thanks for the info! On a different note, do you keep track of T1 only sites? I.e. Sites that are only reachable via the T1 backbone? Erik - - - - - - - - - - - - - - - - - From nwg-owner Wed Apr 8 12:33:33 1992 Received: by merit.edu (5.65/1123-1.0) id AA10991; Wed, 8 Apr 92 12:33:37 -0400 Received: from LABS-N.BBN.COM by merit.edu (5.65/1123-1.0) id AA10984; Wed, 8 Apr 92 12:33:33 -0400 Message-Id: <9204081633.AA10984@merit.edu> To: Merit Network Operations Center Cc: nwg Subject: Re: Clarafi Clarafication: 04/07/92 NSS 9 College Park AS 86 unreachable 21:06 - 00:11 EDT In-Reply-To: Your message of Wed, 08 Apr 92 00:37:58 -0400. <9204080437.AA14471@merit.edu> Date: Wed, 08 Apr 92 12:31:06 -0400 From: skennedy@BBN.COM >> Date: Wed, 8 Apr 92 00:37:58 -0400 >> From: Merit Network Operations Center >> Message-Id: <9204080437.AA14471@merit.edu> >> To: nsr@merit.edu >> Subject: Clarafi Clarafication: 04/07/92 NSS 9 College Park AS 86 unreachable 21:06 - 00:11 EDT >> >> >> Clarafication: 04/07/92 NSS 9 College Park AS 86 unreachable 21:06 - 00:11 >> This affected only AS 86, the SURA Net regional networks. >> Also, Sura Net is backed up on the T3 backbone. >> >> -Philip Chuang >> Merit Network Operations Please send a futher clarification to NSR indicating that the TWBnet was affected by this outage. Our Fix-East peer 192.80.214.247 was down for over two hours. Our EGP session at Fix-West provided backup connectivity between the TWB, and NSFnets, but this outage did not "(affect) only AS 86." Sean - - - - - - - - - - - - - - - - - From mjd Wed Apr 8 18:32:36 1992 Received: by merit.edu (5.65/1123-1.0) id AA24806; Wed, 8 Apr 92 18:32:38 -0400 Received: by merit.edu (5.65/1123-1.0) id AA24802; Wed, 8 Apr 92 18:32:36 -0400 Date: Wed, 8 Apr 92 18:32:36 -0400 From: "Michele J. Davis" Message-Id: <9204082232.AA24802@merit.edu> To: nwg, skennedy@BBN.COM Subject: Correction: 04/07/92 NSS 9 College Park AS 86 and AS 274 regionals unreachable 21:06 - 00:11 EDT. Sorry I did not get back to you sooner but the Correction message was sent out earlier. The reason for this mishap was because the documentation was not correct regarding the networks being announced from College Park. Michele Davis MERIT/NSFNet - - - - - - - - - - - - - - - - - From bsb Wed Apr 8 21:29:03 1992 Received: by merit.edu (5.65/1123-1.0) id AA28395; Wed, 8 Apr 92 20:35:57 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA28387; Wed, 8 Apr 92 20:35:43 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA12022; Wed, 8 Apr 92 20:35:43 EDT Message-Id: <9204090035.AA12022@home.merit.edu> To: Erik Sherk Cc: Jessica Yu , noc@sura.net, nwg Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of Tue, 07 Apr 92 18:17:39 EDT. <9204072217.AA17806@aotearoa.sura.net> Date: Wed, 08 Apr 92 20:35:42 -0400 Erik, I've changed the NWG format to be consistent. It lists the number of CONFIGURED networks. It makes no sense to list the announced networks since this number is constantly changing (duh!). Thanks for bringing up this point. -B. Sue Blair Merit Network Operations ------------------------- >To: Jessica Yu >Cc: noc@sura.net, nwg@merit.edu >Subject: Re: Additions to the NSFNET policy-based routing database >In-Reply-To: Your message of "Tue, 07 Apr 92 17:21:31 EDT." > <9204072121.AA18405@kiddo.merit.edu> >Date: Tue, 07 Apr 92 18:17:39 -0400 >From: Erik Sherk > > > >> Erik, >> >> The total net numbers CONFIGURED in the NSFNET policy database <> the total >> routes actually ADVERTISED to the backbone. The number that announced >> to nwg every Tue and Fri is the configured number. In order to get the >> actually advertised routes to T1, get on your T1 nss and do a netstat -Nn |wc. >> That is the real time advertised number, it may fractuate a bit due to the >> tempary outage of particular networks. But you will get a general idea of >> the number. >> >> --Jessica > >Jessica, > I understand the difference between configured vs. announced networks. >That is not what I am asking. I must have been unclear in my previous question, >let me try again. > > If you grep "Total" from the March 10th network configuration announcment, >you get this: > >aotearoa:[~/Mail/inbox] grep Total inbox/806 >Total NSFNET T1 announced networks: 4835 >Total NSFNET T3 announced networks: 2501 > >The total number of networks on each of the backbones has been different >in all of the announcements send out by Merit that I have seen. But today, >we find that they are the same: > >aotearoa:[~/Mail/inbox] grep Total inbox/1233 > Total T1 announced networks: 5012 > Total configured T3 networks: 5012 > >Oh, I see! You have changed the announcment to list "T1 announced" and "T3 >configured". Would it be too much trouble to ask you to go back to the old >style? > >Erik - - - - - - - - - - - - - - - - - From skw Wed Apr 8 22:47:39 1992 Received: by merit.edu (5.65/1123-1.0) id AA02503; Wed, 8 Apr 92 22:47:43 -0400 From: "Steven K. Widmayer" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA02499; Wed, 8 Apr 92 22:47:39 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA13929; Wed, 8 Apr 92 22:47:38 EDT Date: Wed, 8 Apr 92 22:47:38 EDT Message-Id: <9204090247.AA13929@home.merit.edu> To: bmanning@is.rice.edu, nsfnet-admin Subject: Re: template Cc: nwg >Is there an update to the announcment template? v5.0 still references the >interim NSF AUP. Bill, There is a new template.net form (version 5.1). Thanks for the reminder. --Steve Widmayer Merit/NSFNET - - - - - - - - - - - - - - - - - From bsb Thu Apr 9 03:22:20 1992 Received: by merit.edu (5.65/1123-1.0) id AA09119; Thu, 9 Apr 92 03:22:41 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA09109; Thu, 9 Apr 92 03:22:20 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA18261; Thu, 9 Apr 92 03:22:18 EDT Message-Id: <9204090722.AA18261@home.merit.edu> To: Erik Sherk Cc: Jessica Yu , dennis@MrBill.CAnet.CA, bsb, noc@sura.net, nwg Subject: Re: Additions to the NSFNET policy-based routing database In-Reply-To: Your message of Tue, 07 Apr 92 18:23:16 EDT. <9204072223.AA17832@aotearoa.sura.net> Date: Thu, 09 Apr 92 03:22:15 -0400 >Jessica, > Confusion reigns again :-) This is exactly what had me puzzled. >Thanks for the info! On a different note, do you keep track of T1 only >sites? I.e. Sites that are only reachable via the T1 backbone? > >Erik Folks (if I may butt in), Greetings. Yes, in fact, if you subtract the number of T3 configured networks from the number of T1 configured networks, you will have the number of nets configured on the T1 only. Essentially, the list of T3 networks is a subset of the T1 networks, since even the "T3 only" nets must have at least an interconnect configuration on the T1 side. -B. Sue Blair Merit Network Operations ------------------------- >To: Jessica Yu >Cc: dennis@MrBill.CAnet.CA, sherk@sura.net, bsb@merit.edu, noc@sura.net, > nwg@merit.edu, sherk@sura.net >Subject: Re: Additions to the NSFNET policy-based routing database >In-Reply-To: Your message of "Tue, 07 Apr 92 17:50:26 EDT." > <9204072150.AA17003@kiddo.merit.edu> >Date: Tue, 07 Apr 92 18:23:16 -0400 >From: Erik Sherk > > > >> Erik, >> >> My response is based on the mail you exchanged with Dennis which I thought >> you had a question of why it is announced 5000 some nets on T1 but actually >> you do not get that much. Apparently you were asking something else, >> looking at your original message. Here is the answer of your original >> question: >> >> >> T1 Network: >> >> ---------- >> >> >> >> Total T1 announced networks: 5012 >> >> >> >> >> >> T3 Network: >> >> ---------- >> >> >> >> Total configured T3 networks: 5012 >> >> >Is this right? Are there really 5012 T3 routes? >> >> I think it is a typo. The number of nets CONFIGURED on T3 as of today is 2731. >> >> --Jessica > >Jessica, > Confusion reigns again :-) This is exactly what had me puzzled. >Thanks for the info! On a different note, do you keep track of T1 only >sites? I.e. Sites that are only reachable via the T1 backbone? > >Erik - - - - - - - - - - - - - - - - - From skw Fri Apr 10 09:05:15 1992 Received: by merit.edu (5.65/1123-1.0) id AA29744; Fri, 10 Apr 92 09:05:23 -0400 From: "Steven K. Widmayer" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA29738; Fri, 10 Apr 92 09:05:15 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA17201; Fri, 10 Apr 92 09:05:14 EDT Date: Fri, 10 Apr 92 09:05:14 EDT Message-Id: <9204101305.AA17201@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 128.224 EPILOGUE 560 281 Epilogue Technology Corporation, 40 Gavin Circle, Reading, MA 01867, USA 134.229 REGION-PEN1 184 164 NCTS PENSACOLA, BLD. 603, NAS PENSACOLA, FL 32508, USA 138.40 UKCITY-NET 274 60 City University, 10 Northampton Sq., London EC1V 0HB, UNITED KINGDOM 138.136 REGION-WAS1 184 164 NCTS WASHINGTON, BLD. 196,8TH & M ST. SE, WASHINGTON, DC 20374-5024, USA 138.137 REGION-JAC1 184 164 NCTS JACKSONVILLE, P.O. BOX 111, BLD. 919, NAS JACKSONVILLE, FL 32212, USA 138.138 REGION-PR1 184 164 NAS PATUXENT RIVER, BLD. 420A, RM. 115, P.R., MD 20770, USA 138.139 REGION-CP1 184 164 REGIONAL AUTOMATED SERVICES CENTER, MS 6, BLD. 159, DCED, CODE 54, MCAS, CHERRY POINT, NC 28533-5000, USA 138.140 REGION-SD1 164 184 NCTS SAN DIEGO, BLD. 1482, SAN DIEGO, CA 92135, USA 138.141 REGION-SF1 164 184 NARDAC SAN FRANCISCO, BLD. 62, CODE 54, ALAMEDA, CA 94501, USA 138.142 REGION-NO1 164 184 NCTS NOLA, 4400 DAUPHINE ST., NEW ORLEANS, LA 70145-7700, USA 138.143 REGION-NOR1 184 164 NCTS NORFOLK, CODE 232, BLD. V53, NORFOLK, VA 23511, USA 138.144 REGION-WAS2 184 164 NCTS WASHINGTON, BLD. 196,8TH & M ST. SE, WASHINGTON, DC 20374-5024, USA 138.146 REGION-PHI1 184 164 NETWORK CONTROL CENTER - DATA CENTER, 700 ROBINS AVE., BLD. 2B, CODE 4342.01, PHILADELPHOA, PA 19112, USA 138.147 REGION-ORL1 184 164 NAVAL TRAINING SYSTEMS CENTER, ANNEX BLD., CODE 52, 12350 RESEARCH PKWY., ORLANDO, FL 32826, USA 138.148 REGION-MEM1 184 164 NETPMSA DET MEMPHIS, BLD. S-237, MILLINGTON, TN 38054, USA 138.149 REGION-GL1 184 164 NAVDAF GREAT LAKES, CODE 54, BLD. 3400, 2500 GREENBAY RD., N. CHICAGO IL 60064-3013, USA 138.150 REGION-CC1 164 184 US NAVAL STATION, BLD/ 10, CODE 52, CORPUS CRISTI, TX 78419, USA 138.152 REGION-PS1 164 184 NAVCOMMSTA PUGET SOUND, SUBBASE BANGER, SILVERDALE, WA 98315-5600, USA 138.153 REGION-YOK1 164 184 NAVCOMTELSTA JAPAN, ATTN: EMO, PSC473, BOX 3, JAPAN 138.154 REGION-GAU1 164 184 GUAM 138.155 REGION-MEC1 184 164 SPCC MECHANICSBURG, BLG. 308, CODE 4332, SECOND DECK, MECHANICSBURG, PA 17055-0788, USA 138.158 REGION-RR1 184 164 NAVCOMSTA PUERTO RICO, US NAVAL STAT., ROOSEVELT ROADS, BLD. 831-3042, CODE N3, CEIBE, PUERTO RICO 00635, FPO MIAMI, FL, P.O. BOX 3022 30451, USA 138.159 REGION-CRY1 184 164 NAVSEA CRYSTAL CITY - NATIONAL CENTER, 2521 JEFFERSON HWY., BLD. 2, CODE 05K1, ROOM 1W76, ARLINGTON, VA 22202, USA 138.166 REGION-KEY1 164 184 NUWES KEYPORT, CODE 75C3, NUWES KEYPORT, WA 98345-5000, USA 138.169 REGION-CRA1 184 164 NAVAL SURFACE WARFARE CENTER, BLD. 3173, CODE 331, CRANE, IN 47522-5000, USA 138.170 REGION-LOU2 184 164 NAVAL ORDNANCE STATION, BLD. W-N1, LOUISVILLE, KY 40214-5001, USA 138.171 REGION-KEF1 184 164 NCTS NEW YORK, BOX 22, FPO NEW YORK, NY 09511-0822, USA 138.173 REGION-PM1 164 184 NAVAL AIR WAREFARE CENTER - WEAPONS DIV., BLD. 36, RM. 1050, CODE 341, POINT MUGU, CA 09511-5000, USA 139.77 REGION-NEW1 184 164 NCTS NEWPORT, BLD. 11, NEWPORT, RI 02841-5053, USA 146.102 VSE-NET 590 Prague School of Economics, Winston Churchill sq. 4; CS-136 67 Prague 3, CZECHOSLOVAKIA 151.111 MINNESOTADOT 267 266 Minnesota Department of Transportation, 395 John Ireland Boulevard, St. Paul, MN 55155, USA 152.81 LORIA 1238 LORIA, ampus Scientifique, 615 rue du Jardin Botanique, BP 101, 54600 Villers les Nancy, FRANCE 157.111 NAKANET 291 293 Japan Atomic Energy Research Institute Naska Fusion, JAPAN 157.161 IMPROWARE 701 Improware AG & SKW Engineering AG, Improware AG, Schneckelerstrasse 4, CH-4414 Fuellinsdorf, SWITZERLAND 158.114 BDM 209 210 BDM International, Inc., 7915 Jones Branch Drive, McLean, VA 22102-3396, USA 158.154 GOLDSTONE 372 297 Goldstone Deep Space Communications Complex, PO Box 997, Barstow, CA 92311, USA 192.6.150 HP-AND 1384 1383 Hewlett Packard, 3000 Minuteman Rd., Andover, MA 01810, USA 192.42.102 ARAMIS 1238 ARAMIS, c/o Centre Inter-universitaire de Calcul de Grenoble BP 53X, F-38041 Grenoble CEDEX, FRANCE 192.72.3 SEED-NET-3 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.4 SEED-NET-4 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.5 SEED-NET-5 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.6 SEED-NET-6 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.7 SEED-NET-7 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.8 SEED-NET-8 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.9 SEED-NET-9 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.10 SEED-NET-10 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.11 SEED-NET-11 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.12 SEED-NET-12 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.13 SEED-NET-13 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.14 SEED-NET-14 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.15 SEED-NET-15 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.16 SEED-NET-16 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.17 SEED-NET-17 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.18 SEED-NET-18 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.19 SEED-NET-19 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.20 SEED-NET-20 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.21 SEED-NET-21 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.22 SEED-NET-22 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.23 SEED-NET-23 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.24 SEED-NET-24 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.25 SEED-NET-25 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.26 SEED-NET-26 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.27 SEED-NET-27 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.28 SEED-NET-28 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.29 SEED-NET-29 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.30 SEED-NET-30 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.31 SEED-NET-31 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.72.32 SEED-NET-32 1250 750 Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN 192.80.43 UAROUTERNET 210 209 The University of Arizona, Computer Center, Tucson, AZ 85721, USA 192.87.36 SNET-AT-TUD 590 1238 SURFnet BV, P.O. Box 19035; NL-3501 DA Utrecht, NETHERLANDS 192.93.249 FNET-ILL 1238 Institut LAUE-LANGEVIN, B.P. 156 X, 38042 Grenoble CEDEX, FRANCE 192.108.150 FESNET 590 Federal Educational and Scientific network, Czech Technical University; Zikova 4; CS-166 35 Praha 6, CZECHOSLOVAKIA 192.124.124 PGROUP 701 702 The Portland Group, 9150 S.W. Pioneer Court, Suite H, Wilsonville, OR 97070, USA 192.132.248 CNU-NET2 1740 754 ChungNam National University, 220 ung-Dong, Youseong-Ku, Taejeon 305-764, KOREA 192.132.252 IDSIA 701 IDSIA, Corso Elvezia 36, CH-6900 Lugano, SWITZERLAND 192.135.231 QMW-DCS-NET1 274 60 Queen Mary and Westfield College, Mile End Road, London E1 4NS, England, UNITED KINGDOM 192.136.138 ICSROBERTS 164 184 USAISC SATCONSTA, P.O. BOX 479, SAN MIGUEL, CA 93451-0479, USA 192.138.66 AMEDDDIX 184 164 WALSON ARMY COMM. HOSP., HSXG-IM, FT. DIX, NJ 08640-6600, USA 192.138.67 AMEDD-DEVENS 184 164 CUTLER ARMY COMM. HOSP., HSXF-IM, FT. DEVENS, MA 01433-6401, USA 192.138.170 NASM-NET 297 372 National Air & Space Museum, NASM 3790, smithsonian Institute, Washington, DC 20560, USA 192.138.216 KAY-NET 1384 1383 Kay Technical Research Inc, 9 Maple Lane, Thompson, CT 06277, USA 192.149.125 ERSNETWORK 280 114 Employees Retirement System of Texas, 1801 Brazos St., Austin, TX 78701, USA 192.150.30 NSI-NET10 372 297 NASA Ames Research Center, NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA 192.150.113 SEASPACE 1740 754 SeaSpace Company, 3655 Nobel Dr., Ste 160, San Diego CA 92122, USA 192.150.210 ANGELO 280 114 Angelo State University, 2601 West Avenue N, San Angelo, TX 76901, USA 192.150.242 GAT2 291 293 General Atomics, Fusion User Service Center, 3550 General Atomics Ct., San Diego, CA 92121, USA 192.153.125 CYBRSPSTN 1740 754 The Cyberspace Station, 439 Village Run East, Encinitas, CA 92024, USA 192.153.156 CERFNET-OP2 1740 754 CERFnet, PO BOX 85608, San Diego CA 92186-9784, USA 192.153.169 NET-CSN-1 209 210 Colorado SuperNet Inc, Colorado School of Mines, 1500 Illinois, Golden, CO 80401, USA Total T1 configured networks: 5097 T3 Network: ---------- 343 T1 configured NASA-FIX-West (AS 372) networks (not listed here) have been added to the T3 database. 82 T1 configured MIDnet (AS 93) networks (not listed here) have been added to the T3 database. 75 T1 configured CICnet (AS 266/267) networks (not listed here) have been added to the T3 database. Network IP: 128.224 Network Name: EPILOGUE Location: Epilogue Technology Corporation, 40 Gavin Circle, Reading, MA 01867, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 151.111 Network Name: MINNESOTADOT Location: Minnesota Department of Transportation, 395 John Ireland Boulevard, St. Paul, MN 55155, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT Network IP: 155.247 Network Name: TEMPLE-EDU Location: Temple University, Computer Room 763, Broad & Montgomery Avenue, Philadelphia, PA 19122, USA Country Code: US 1:1206 PSCNET Network IP: 158.154 Network Name: GOLDSTONE Location: Goldstone Deep Space Communications Complex, PO Box 997, Barstow, CA 92311, USA Country Code: US 1:372 AS 372 - Nasa Ames 2:297 Nasa Science Network (FIX-East) Network IP: 158.170 Network Name: INTER-CHILE2 Location: SECOM, MATUCANA 28-D, ESTACION CENTRAL, SANTIAGO, CHILE Country Code: CL 1:86 SURANET Regional Network 2:279 Georgia Tech Network IP: 192.6.150 Network Name: HP-AND Location: Hewlett Packard, 3000 Minuteman Rd., Andover, MA 01810, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.72.3 Network Name: SEED-NET-3 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.4 Network Name: SEED-NET-4 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.5 Network Name: SEED-NET-5 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.6 Network Name: SEED-NET-6 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.7 Network Name: SEED-NET-7 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.8 Network Name: SEED-NET-8 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.9 Network Name: SEED-NET-9 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.10 Network Name: SEED-NET-10 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.11 Network Name: SEED-NET-11 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.12 Network Name: SEED-NET-12 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.13 Network Name: SEED-NET-13 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.14 Network Name: SEED-NET-14 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.15 Network Name: SEED-NET-15 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.16 Network Name: SEED-NET-16 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.17 Network Name: SEED-NET-17 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.18 Network Name: SEED-NET-18 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.19 Network Name: SEED-NET-19 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.20 Network Name: SEED-NET-20 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.21 Network Name: SEED-NET-21 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.22 Network Name: SEED-NET-22 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.23 Network Name: SEED-NET-23 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.24 Network Name: SEED-NET-24 Location: 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.25 Network Name: SEED-NET-25 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.26 Network Name: SEED-NET-26 Location: 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.27 Network Name: SEED-NET-27 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.28 Network Name: SEED-NET-28 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.29 Network Name: SEED-NET-29 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.30 Network Name: SEED-NET-30 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.31 Network Name: SEED-NET-31 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.72.32 Network Name: SEED-NET-32 Location: Institution for Information Industry, 10th Floor 106, Ho-Ping East Road, Section 2, Taipei, R.O.C., TAIWAN Country Code: TW 1:97 ENSS 137 - Princeton Network IP: 192.124.124 Network Name: PGROUP Location: The Portland Group, 9150 S.W. Pioneer Court, Suite H, Wilsonville, OR 97070 USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 192.132.248 Network Name: CNU-NET2 Location: ChungNam National University, 220 ung-Dong, Youseong-Ku, Taejeon 305-764, KOREA Country Code: KR 1:1740 CERFnet Network IP: 192.138.170 Network Name: NASM-NET Location: National Air & Space Museum, NASM 3790, smithsonian Institute, Washington, DC 20560, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:372 AS 372 - Nasa Ames Network IP: 192.138.216 Network Name: KAY-NET Location: Kay Technical Research Inc, 9 Maple Lane, Thompson, CT 06277, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.149.125 Network Name: ERSNETWORK Location: Employees Retirement System of Texas, 1801 Brazos St., Austin, TX 78701, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Network IP: 192.150.30 Network Name: NSI-NET10 Location: NASA Ames Research Center, NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA Country Code: US 1:372 AS 372 - Nasa Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.150.113 Network Name: SEASPACE Location: SeaSpace Company, 3655 Nobel Dr., Ste 160, San Diego CA 92122, USA Country Code: US 1:1740 CERFnet Network IP: 192.150.210 Network Name: ANGELO Location: Angelo State University, 2601 West Avenue N, San Angelo, TX 76901, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Network IP: 192.153.125 Network Name: CYBRSPSTN Location: The Cyberspace Station, 439 Village Run East, Encinitas, CA 92024, USA Country Code: US 1:1740 CERFnet Network IP: 192.153.156 Network Name: CERFNET-OP2 Location: CERFnet, PO BOX 85608, San Diego CA 92186-9784, USA Country Code: US 1:1740 CERFnet Total T3 configured networks: 3271 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Steve Widmayer Merit/NSFNET - - - - - - - - - - - - - - - - - From cert-advisory-request@cert.sei.cmu.edu Fri Apr 10 14:56:04 1992 Received: from tictac.cert.sei.cmu.edu by merit.edu (5.65/1123-1.0) id AA12318; Fri, 10 Apr 92 14:56:04 -0400 Received: by tictac.cert.sei.cmu.edu (5.65/2.5) id AA00587; Fri, 10 Apr 92 14:48:10 -0400 Message-Id: <9204101848.AA00587@tictac.cert.sei.cmu.edu> From: CERT Advisory Date: Fri, 10 Apr 92 14:47:50 EDT To: cert-advisory@cert.sei.cmu.edu Subject: CERT Advisory - "IRIX" lp Vulnerability Organization: Computer Emergency Response Team =========================================================================== CA-92:08 CERT Advisory April 10, 1992 Silicon Graphics Computer Systems "IRIX" lp Vulnerability --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a method of unauthorized root access in the lp software in Silicon Graphics Computer Systems (SGI) IRIX operating systems. This vulnerability is present in all current versions of IRIX. Silicon Graphics Computer Systems and the CERT/CC strongly recommend that sites take immediate action to eliminate this vulnerability from their systems. This vulnerability will be fixed in IRIX 4.0.5 and is NOT present in any version of the Trusted IRIX/B product. --------------------------------------------------------------------------- I. Description When IRIX pre-4.0.5 systems are installed or updated using either the basic system software ("eoe1.sw.unix") or the system manager software ("eoe2.sw.vadmin") media, a vulnerability is introduced in the lp software. II. Impact Any user logged into the system can gain root access. III. Solution As root, execute the following commands: # cd /usr/lib # chmod a-s,go-w lpshut lpmove accept reject lpadmin # chmod go-ws lpsched vadmin/serial_ports vadmin/users vadmin/disks # cd /usr/bin # chmod a-s,go-w disable enable # chmod go-ws cancel lp lpstat If the eoe2.sw.vadmin software is not installed, you may ignore any warning messages from chmod such as: "chmod: WARNING: can't access vadmin/serial_ports" If system software should ever be reinstalled from pre-4.0.5 media or restored from a backup tape created before the patch was applied, repeat the above procedure before enabling logins by normal users. --------------------------------------------------------------------------- The CERT/CC would like to thank Silicon Graphics Computer Systems for bringing this security vulnerability to our attention and for their quick response to this problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT/CC or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: cert@cert.sei.cmu.edu Telephone: 412-268-7090 (24-hour hotline) CERT/CC personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. Computer Emergency Response Team/Coordination Center (CERT/CC) Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available for anonymous ftp from cert.sei.cmu.edu (192.88.209.5). Please note: cert.sei.cmu.edu is soon to become cert.org. - - - - - - - - - - - - - - - - - From mak Fri Apr 10 21:44:40 1992 Received: from fox.merit.edu by merit.edu (5.65/1123-1.0) id AA24983; Fri, 10 Apr 92 21:44:40 -0400 Received: by fox.merit.edu (4.1/client-0.9) id AA26774; Fri, 10 Apr 92 21:44:51 EDT Date: Fri, 10 Apr 92 21:44:51 EDT From: mak Message-Id: <9204110144.AA26774@fox.merit.edu> To: regional-techs Subject: ANSNET/NSFNET Phase-III T3 Network Upgrade Plan Phase-III T3 Network Upgrade Plan Summary ========================================= Jordan Becker, ANS Mark Knopper, Merit ANS & Merit are planning a major upgrade to the ANS/NSFNET T3 backbone service beginning in late April which is scheduled to complete at the end of May. The upgrade involves changing all of the T3 interface adapters in the RS/6000 T3 routers as well as the DSUs. The new T3 adapter (called RS960) supports on-card packet forwarding which will dramatically improve the performance, as packet forwarding will not require support by the main RS6000 CPU. The mechanism used will allow a T3 adapter to send data directly to another adapter across the RS6000 bus. The concept is roughly comparable to an evolution of the architecture of T1 nodes on the NSFNET, since all the processors are in a single system sharing a common bus. The reliability of the new RS960 adapter is much greater than the existing T3 adapter (known as "Hawthorne T3 adapter"). We will also upgrade the DSU to provide "C-bit parity" over the T3 links. C-bit parity (based on ANSI T1.107A spec.) will provide improved end-to-end real-time link level network management information. C-bit parity is conceptually comparable to Extended Super Framing (ESF) over T1 circuits. Other minor changes on the router include the replacement of the fan, the I/O planar card, and associated cabling to support the adapter upgrade. The result of this upgrade will be higher speed packet switching and increased SNMP functionality, better T3 link monitoring, higher T3 router reliability and availability, and better diagnostic and repair capability. The deployment of this upgrade will temporarily affect T3 network connectivity while the core node (CNSS) and end node (ENSS) routers are upgraded. In order to minimize down time, all nodes will be upgraded during off-hours on weekends. The target start date for the phase-III upgrade is April 24. This is contingent upon successful completion of the test plan described below. Implementation of the deployment is planned to cover six steps, each step taking place over a Friday night/Saturday morning 8 hour window. Each step will correspond to the upgrade of all CNSS's located at two adjacent POPs and all of the T3 ENSS nodes supported by those CNSS's. T3 network outages at NSFNET midlevel T3 network sites are expected to average 2 hours per step, although we have provisioned a 8 hour window to accomplish the upgrade to the T3 ENSS and adjacent CNSS nodes. NSFNET T3 midlevel networks will be cutover to the T1 backbone prior to the scheduled upgrade and will remain on the T1 until the affected nodes are upgraded and network reachability has been successfully re-established. During the outage period where the T3 CNSS routers are upgraded (expected to be 2 hours), traffic from other T1 and lower speed ENSS nodes, as well as T1 CNSS transit traffic will be continue to be routed via the T1 safetynet circuits. All upgrades will start on a Friday night, with a starting time of approximately 23:00 local time. There will be two exceptions: changes to the Denver and Cleveland facilities will be starting at approximately 24:00 local time. There will be a scheduled visit to your site by the local CE on the Thursday prior to the Friday installation in order to ensure that all parts have been received on site in preparation for the installation. Each CNSS site should take about 8 hours to complete, with the exception of the New York City core node. At the New York City site, we will also be physically moving the equipment within the POP and expect this move to add about 4 hours to the upgrade there. Although each upgrade is expected to require 8 hours to complete, we are reserving the 48hour window from approximately 23:00 local time on Friday to 24:00 local time on Sunday, for possible disruptions to service. This window will allow enough time to debug any unforeseen problem that may arise. A second visit to core nodes will be required to replace a single remaining old-technology T3 adapter. This will result in a T3 outage of approximately 105 minutes at sites as indicated below. We have established a tentative upgrade schedule which is contingent upon successful completion of all testing (described below). If any unforseen problems are encountered during the deployment we will postpone subsequent upgrades until the problems we encounter are resolved. The current upgrade schedule by CNSS/ENSS site is as follows: Step 1, April 24/25 Denver, Seattle core nodes T3 ENSS Nodes: Boulder E141, Salt Lake E142, U. Washington E143 Step 2, May 1/2 San Francisco, Los Angeles core nodes T3 ENSS Nodes: Palo Alto E128, San Diego E135, Other ENSS Nodes: E144, E159, E156, E170 also affected Second core node visit: Seattle Step 3, May 8/9 Chicago, Cleveland, New York City, Hartford core nodes T3 ENSS Nodes: Argonne E130, Ann Arbor E131, Pittsburgh E132, Ithaca E133, Boston E134, Princeton E137 Other ENSS Nodes: E152, E162, E154, E158, E167, E168, E171, E172, CUNY E163, E155, E160, E161, E164, E169 also affected Second core node visit: San Francisco Step 4, May 15/16 St. Louis, Houston core nodes T3 ENSS Nodes: Champaign E129, Lincoln E140, Rice U. E139 Other ENSS Nodes: U. Louisville E157, E165 also affected Second core node visit: Los Angeles, Denver, Chicago Step 5, May 22/23 Washington D.C., Greensboro core nodes T3 ENSS Nodes: College Park E136, FIX-E E145, Georgia Tech E138 Other ENSS Nodes: Concert E150, VPI E151, E153, E166 also affected Second core node visit: Houston, New York City, Hartford It is anticipated that with the exception of the T3 ENSS indicated site outages other ENSS nodes and transit traffic services will be switched across the safetynet and T1 CNSS concentrators during the upgrades. However brief routing transients or instabilities may be observed. NSR messages will be posted 48 hours in advance of any scheduled changes and questions or comments on the schedule or plan may be directed to the ie@merit.edu mailing list. T3 Research Network RS960 Test Plan and Experiences =================================================== This upgrade is the culmination of several months of development and lab and network testing of the new technology. Many of the problems identified during the deployment of the phase-II T3 network have been corrected in the new hardware/software. A summary of the experiences we have had with this technology on the T3 Research network is described below. ANS/Merit and their partners maintain a full wide area T3/T1 Research network for development and testing of new hardware, software, and procedures prior to introduction on the production networks. The T3 Research network includes 3 core node locations with multiple fully configured CNSS routers. There are 5 ENSS sites at which we maintain full T3 ENSS routers as well as local ethernet and FDDI LANs that interconnect multiple peer routers and test hosts. The Research network is designed to emulate the production network configuration as much as possible. There wide area Research network interconnects with multiple testbed at each of the 5 ENSS locations. These testbeds are configured to emulate regional and campus network configurations. General Testing Goals and Methods --------------------------------- Unit and system testing of all phase-III technology is conducted first in the development laboratories, and then regression tested on the development testbeds at each of the participating sites. The primary goal for testing of the phase-III technology on the T3 Research network is to determine whether the new technology meets several acceptance criterion for deployment on the production network. These criterion include engineering requirements such as routing, packet forwarding, manageability, and fault tolerance. They also include regression testing against all known problems that have been corrected to date on the T3 system, including all of its components. The following are secondary goals that the test plan includes: 1. To gain experience with new components so that the NOC and engineering staffs can recover from problems once in production. 2. To identify any problems resulting from attempts to duplicate production network traffic load and distributions on the Test Network. 3. To perform load saturation, route flapping, and other stress tests to measure system response and determine failure modes and performance limits. 4. To duplicate selected system and unit tests in a more production-like environment. 5. To design and execute tests and that reflect "end-user perceptions" of network performance and availability. 6. To isolate new or unique components under test to evaluate new criterion or performance objectives for testing those specific new components. Regression testing against the entire system is also emphasized. 7. To independantly evaluate the validity of specific tests to ensure their usefulness. Phase-III Components to be tested ================================= The RS960 interface upgrade consists of two new hardware components: 1. RS960 DS3/HSSI interfaces 2. New T3 DSU adapters a. Communication card with c-bit parity (ANSI T1.107A) b. High Speed Serial Interface (HSSI) interface card (HSSI - Developed by Cisco & T3plus Inc. is defacto standard comparable to V.35 or RS-422). There will be several new software components tested for the target production network AIX 3.1 operating system level: 1. RS960 DS3 driver & kernel modifications 2. SNMP software a. SNMP Daemon, DSU proxy subagent b. T3 DSU logging and interactive control programs 3. RS960 adapter firmware 4. New RS960 utility programs for AIX Operating System a. ifstat - Interface statistics b. ccstat - On-Card Statistics General Areas Tested ==================== The following areas comprise the areas where test objectives are exercised. Extensive testing is done to ensure that we meet these objectives. 1) Packet Forwarding a. Performance and stress testing b. Reliability under stress conditions 2) Routing a. Focus on consistency of routes - across system tables and smart card(s) tables - after interface failure - after network partitioning - after rapid node/circuit/interface transitions - under varying traffic load conditions b. Limit testing - determine limits on: - number of routes - number of AS's - packet sizes - number of networks - number of nets at given metric per node - system behavior when these limits are exceeded c. Interoperability with Cisco BGP testing 3) System monitoring via SNMP a. RS960 hardware, driver, microcode b. DSU functions, C-bit parity end-to-end connectivity and performance 4) End to End Tests a. Connection availability - does TCP connection stay open in steady state? b. Throughput - measure throughput on host to host connection through network c. Delay - measure packet delays from user point of view - observe round trip, and unidirectional delays d. Steady State Performance - evaluate effect on TCP connection due to network changes 5) Unit Test Verification a. Repeat selected regression tests performed by development b. Exercize DSU functions - measure packet loss - perform loopback tests c. Induce random & deterministic noise into circuits and evaluate interface hardware/software response 6) Deployment Phase Testing a. Test all machine configurations that will be used during the deployment transition phases b. Measure throughput under production load across transitional configurations (RS960 T3 <-> Hawthorne T3 path) 7) NOC Procedure Testing a. During testing, identify all possible failure modes b. Install & document specific recovery procedures c. Train NOC staff on test network Test Schedule Summary ===================== DATE EVENT 3/1 Development unit & system testing complete, code review o Build AIX system for testnet o Freeze all fix buckets 3/6-3/10 Install RS960 on testnet with transition configurations 3/20 Disconnect testnet from production net o Bring back Richardson - White Plains T3 link o Burn-in and swap out any failed or hardware components. o Prepared for testbed regression tests o Install new build (3/19) 3/21-3/24 Steady state traffic flow testing, stability testing o Configure external Ciscos with static routes o Inject routes and traffic with copy tools and packet generators to induce non-overload of traffic. o Configure and start end hosts for application tests. 3/25 Throughput testing 1 o Stress test 3xHawthorne T3-> 1xRS960 T3 CNSS flow on WP3, lesser flow in reverse direction. Measure degredation with timestamped echo request packets, as well as analyze memory used. check all links for dropped or lost packets. 3/26 Throughput testing 2 o Repeat 3/23 test on White Plains CNSS2 with 3xRS960s->1xHawthorne T3 CNSS config. Throughput testing 3 o Repeat above on BW5 POP with all RS960 CNSS config. Look for any system degredation, or pathological route_d effects. 3/27 Upgrade testnet to match post-deployment configuration o White Plains CNSS3-Elmsford ENSS and White Plains CNSS3 <-> Yorktown ENSS become RS960 links 3/27 Routing testing 1 o Configure & validate cisco route injection setup o Copy tools loaded with matching configs for routes. o Install utility to diff netstat -r and ifstat -r tables o Vary traffic load & distribution with traffic generators and copy tools, run scripts to look for incorrect route entries o End to end applications running with changing routes and loads, look for errors (timeouts) and throughput. 3/30 Routing testing 2 o MCI to get error noise injector for T3 at White Plains, on Bridgewater-White Plains T3 link. ANS to operate noise injecto r. o Repeat 3/25 tests with - Intentionally crashed card (Use Milford utility to crash card) - Partitioned network (pull HSSI cables in White Plains) - Injected line errors (ANS to inject in White Plains on MCI equipment) 3/31 Routing limit testing o as defined in testplan: - routes - AS's - packet sizes - number of nets at given metric per nodes 4/01 SNMP RS960 tests o as defined in testplan: - RS960 hardware - RS960 driver - RS960 microcode 4/02 SNMP DSU tests o as defined in testplan: - DSU functions - C-bit parity 4/03 Regression End-to-End tests o Induce background traffic load with packet generators and copy tools, run end-user applications and also transit end-end 1x10**6 packets to an idle machine with pkt generators. Count packets dropped. 4/06 Regression Configuration Conversion o Upgrade any adapters, DSUs, system software, microcode that are not uplevel, make sure that DSUs are now configured for SNMP control o repeat everything Phase-III Test Experiences and Results To-Date Summary ====================================================== Testing is scheduled to continue up until 4/17. We will then freeze the test network in preparation for deployment on 4/24. The software build that supports the new technology will be installed on selected nodes between 4/17 and 4/24 to burn-in prior to the 4/24 hardware upgrades. Testing on the test network will continue throughout the deployment. Overall Testnet Observations ---------------------------- The performance of the RS960 technology is far superior to that of the existing Hawthorne T3 adapter technology. Although peak performance throughput tests have not yet been conducted, the steady state performance for card-card transfers has been measured in excess of 20KPPS with excellent stability. During the early deployment of the RS960 and DSU technology on the testnetwork, we observed several new transmission facility problems that were not observed in the lab tests, or in earlier DS3 adapter tests. We found a new form of data pattern sensitivity where under certain conditions the new DSU can generate a stream of 010101 bits that induce an Alert Indicator Signal (blue alarm) within the MCI network. The RS960 and existing Hawthorne T3 card do not interoperate over a serial link. However they will interoperate if both are installed within a single CNSS node using specially developed driver software which uses the main RS6000 CPU for packet forwarding between the RS960 and Hawthorne T3 cards. As part of the phase-III migration period we had originally planned to support an interim CNSS configuration of 3xHawthorne T3 adapters and 1xRS960 adapter as well as a 1xHawthorne T3 & 3xRS960 T3 interim CNSS configuration. Unfortunately during the performance tests we determined that the 3xHawthorne T3 & 1xRS960 T3 configuration creates a performance bottleneck that could cause congestion under heavy load. This is due to the interim state RS960 <-> Hawthorne interface software driver bottlneck where the main RS6000 CPU is used for packet forwarding between dis-similar adapters. We have therefore eliminated this configuration from the deployment plan and will support only the 1xHawthorne, 3xRS960 configuration as an interim state during the deployment. We are also looking various deployment strategies that will avoid any congestion across an interim RS960<->Hawthorne path. These strategies include interior T3 link metric adjustment, safetynet link load splitting, careful placement of these transition links to avoid hot-spots, or temporary addition of new DS3 links that will short-cut these transition links. We are using something called a copy tool that was developed as a host system that interfaces on a production network ethernet, and test network ethernet whereby all production ethernet packets are promiscuously copied on the host, given a new destination address, and injected into the Research network to simulate production traffic flows within the Research network. We have found a bug in the copy tool that has caused problems on the test ethernets at a couple of Research network locations. Everytime the copy tool is re-booted, we experience congestion on the test ethernets due to an erroneous broadcast of a copied packet onto a test ethernet. We are fixing this problem before we run these tests again. We have run numerous route flapping tests where will install and delete routes repeatedly on all installed RS960 cards and have not encountered any chronic problems so far. The installation and deletion of 6000 routes on the card is fast enough that we can not measure an inconsistencies between different on-card route tables. We have compiled a limit of 6000 routes on the card for now since this reflects the deployment configuration, however we can support up to 14000 IP routes on the card if necessary. We have opened and closed over 100 problems during the several months of lab and Research network testing on RS960. There are currently 14 open problems remaining from our tests to date and we can provide some details on this for anyone interested. We have fixes for most of these problems that will be regression tested on the Research network next week. We expect to close these problems prior to deployment of RS960 on 4/24. - - - - - - - - - - - - - - - - - From donnab@CERF.NET Mon Apr 13 14:39:58 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA25559; Mon, 13 Apr 92 14:39:58 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA26680; Mon, 13 Apr 92 11:39:50 PDT Date: Mon, 13 Apr 92 11:39:50 PDT From: Donna Bigley Message-Id: <9204131839.AA26680@nic.cerf.net> To: broidoj@Sds.Sdsc.Edu, help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, April 6, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, April 6th through Sunday, April 12th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 12-april-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 896 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: MON. 4-6-92 23:09 TIME ENDED: MON. 4-6-92 23:37 TIME ELAPSED: 28 min. REASON: Unknown TICKET #: 902 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: WED. 4-8-92 14:34 TIME ENDED: WED. 4-8-92 22:06 TIME ELAPSED: 7 hours 32 min. (Intermittent Outages) REASON: Unknown TICKET #: 901 SITE: HANG10 SITES AFFECTED: SDSU, UCR, XEROX, AGOURON, BIOSYM, SEASPACE, UCOP, UCOP Dial n' CERF, CIX, FARALLON, NETLABS, LSILOGIC, APPLE, and CISCO. TIME STARTED: THU. 4-9-92 07:46 TIME ENDED: THU. 4-9-92 07:51 TIME ELAPSED: 5 min. REASON: CERFnet/Site Scheduled Maintenance TICKET #: 903 SITE: PEPPERDINE SITES AFFECTED: PEPPERDINE TIME STARTED: FRI. 4-10-92 01:03 TIME ENDED: FRI. 4-10-92 02:35 TIME ELAPSED: 1 hour 32 min. (Intermittent Outages) REASON: Site Activity/Power Outage TICKET #: 904 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: SAT. 4-11-92 11:01 TIME ENDED: SAT. 4-11-92 12:04 TIME ELAPSED: 1 hour 3 min. REASON: Site Scheduled Maintenance ------------------------------------------------------------------------ NETWORK ACTIVITY: Mark V Systems, Encino, became a new CERF14.4 member on Monday, April 6, 1992. SeaSpace, San Diego, became a new CERF1544 member on Wednesday, April 8, 1992. Cyberspace Station, Encinitas, became a new DIAL N' CERF Plus member on Thursday, April 9, 1992. ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps No capacities available this week. (New Line) SDSC/CALTECH 1.544 mbps 10.0% 14:00 SDSC/UCI 1.544 mbps 08.2% 14:00 SDSC/UCLA 1.544 mbps 06.9% 14:00 SDSC/UCOP 1.544 mbps 03.6% 15:00 UCI/UCLA 1.544 mbps 00.9% 14:00 SDSC/UCR 512 kbps 02.4% 22:00 UCLA/UCSB 512 kbps 10.2% 14:00 SDSC/AGI 1.544 mbps 00.1% 19:00 SDSC/BIOSYM 1.544 mbps 00.2% 09:00 SDSC/GA 1.544 mbps 00.3% 14:00 SDSC/GD 1.544 mbps 01.0% 10:00 SDSC/SAIC 1.544 mbps 01.7% 14:00 SDSC/SCAQMD 1.544 mbps 00.01% 16:00 SDSC/SDSU 1.544 mbps 01.5% 23:00 UCI/CSU CO(SWRL) 1.544 mbps 02.2% 16:00 UCOP/APPLE 1.544 mbps 01.0% 13:00 UCOP/CISCO 1.544 mbps 00.2% 11:00 UCR/LLUMC 1.544 mbps 00.1% 08:00 CALTECH/CADAM 56 kbps 02.2% 16:00 CALTECH/CITY OF HOPE 56 kbps 00.2% 16:00 CALTECH/CLAREMONT 56 kbps 25.8% 14:00 CALTECH/DISNEY 56 kbps 02.7% 16:00 CALTECH/OXY 56 kbps 08.1% 12:00 SDSC/AJS 56 kbps 01.2% 13:00 SDSC/KOREA 56 kbps 07.7% 05:00 SDSC/QUALCOMM 56 kbps 08.3% 18:00 SDSC/SCIH 56 kbps 02.4% 02:00 SDSC/USD 56 kbps 07.2% 14:00 SDSC/USIU 56 kbps 00.4% 15:00 SDSC/XEROX 56 kbps 00.5% 18:00 UCI/CMD 56 kbps 05.4% 20:00 UCI/EMULEX 56 kbps 01.0% 10:00 UCI/FULLERTON 56 kbps 01.4% 13:00 UCI/HUGHES 56 kbps 08.0% 10:00 UCI/MTI 56 kbps 06.0% 17:00 UCI/SPARTA 56 kbps 04.7% 14:00 UCI/UNOCAL 56 kbps 07.7% 10:00 UCLA/ISX 56 kbps 03.5% 09:00 UCLA/PEPPERDINE 56 kbps 02.1% 11:00 UCLA/QUOTRON 56 kbps 06.0% 13:00 UCLA/SMC 56 kbps 01.1% 23:00 UCOP/FARALLON 56 kbps 04.3% 13:00 UCOP/INTEL 56 kbps No capacities available this week. UCOP/LSIL 56 kbps 08.4% 22:00 UCOP/NETLABS 56 kbps 14.7% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on April 13, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 15 days 05 hours 41 minutes SDSC LongBoard [134.24.99.254] Up: 04 days 14 hours 56 minutes [Equipment Trouble] SDSC Drzog [132.249.16.13] Up: 24 days 07 hours 00 minutes SDSC Hang10 [132.249.16.15] Up: 03 days 16 hours 26 minutes [Unscheduled Outage] UCI [128.200.1.101] Up: 94 days 16 hours 07 minutes UCLA [128.97.130.10] Up: 07 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 19 days 16 hours 38 minutes UCR [134.24.108.105] Up: 22 days 06 hours 48 minutes CERF 1544 AGI [134.24.202.110] Up: 59 days 13 hours 54 minutes APPLE [134.24.70.200] Up: 168 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 09 days 05 hours 27 minutes CISCO Systems [134.24.54.200] Up: 33 days 04 hours 20 minutes CSUCO/SWRL [130.150.102.200] Up: 10 days 18 hours 49 minutes GA [134.24.221.200] Up: 23 days 19 hours 56 minutes GD [134.24.60.200] Up: 42 days 13 hours 31 minutes LLUMC [134.24.208.200] Up: 145 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 99 days 08 hours 34 minutes SCAQMD [134.24.234.200] Up: 115 days 14 hours 27 minutes SDSU [192.77.100.101] Up: 125 days 16 hours 31 minutes UCSB [134.24.107.107] Up: 145 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 86 days 14 hours 17 minutes CADAM [134.24.229.200] Up: 68 days 13 hours 01 minutes CLAREMONT [134.24.206.109] Up: 16 days 17 hours 39 minutes CMD [134.24.218.200] Up: 76 days 13 hours 14 minutes DATAPRODUCTS [134.24.211.104] Up: 12 days 09 hours 33 minutes DISNEY [134.24.207.211] Up: 02 days 10 hours 00 minutes [Unknown] EMULEX [134.24.209.212] Up: 01 days 12 hours 12 minutes [Site Scheduled Maintenance - See Ticket #904] FARALLON [134.24.56.200] Up: 14 days 02 hours 24 minutes FULLERTON [134.24.214.217] Up: 28 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 01 days 03 hours 08 minutes [Unknown] INTEL [134.24.55.200] Up: 15 days 11 hours 34 minutes LSIL [134.24.72.200] Up: 64 days 13 hours 08 minutes MTI [134.24.216.100] Up: 100 days 13 hours 39 minutes NETLABS [134.24.71.200] Up: 18 days 08 hours 51 minutes OXY [134.24.205.108] Up: 06 days 16 hours 27 minutes [Unknown] PEPPERDINE [134.24.203.218] Up: 02 days 21 hours 42 minutes [Site Activity/Power Outage - See Ticket #903] QUALCOMM [134.24.200.201] Up: 04 days 01 hours 42 minutes [Site Scheduled Maintenance] QUOTRON [134.24.230.202] Up: 08 days 12 hours 00 minutes SANTA MONICA [134.24.210.219] Up: 30 days 12 hours 40 minutes SCI-HOR [134.24.109.205] Up: 17 days 04 hours 27 minutes SERI/KOREA [134.24.223.200] Up: 06 days 00 hours 40 minutes [Unknown] SPARTA [134.24.215.200] Up: 13 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 38 days 01 hours 57 minutes USD [134.24.201.106] Up: 17 days 06 hours 12 minutes USIU [134.24.222.215] Up: 281 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 165 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 34 days 05 hours 09 minutes DNC-UCI [134.24.2.2] Up: 96 days 03 hours 24 minutes DNC-UCLA [134.24.3.2] Up: 07 days 06 hours 25 minutes DNC-CALTECH [134.24.4.2] Up: 15 days 05 hours 42 minutes DNC-UCOP [134.24.5.2] Up: 02 days 17 hours 01 minutes [Unknown] - - - - - - - - - - - - - - - - - From bsb Tue Apr 14 09:46:19 1992 Received: by merit.edu (5.65/1123-1.0) id AA28748; Tue, 14 Apr 92 09:46:23 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA28744; Tue, 14 Apr 92 09:46:19 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA28954; Tue, 14 Apr 92 09:46:18 EDT Date: Tue, 14 Apr 92 09:46:18 EDT Message-Id: <9204141346.AA28954@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Net # Net Name Primary Secondary Location -------- ----------- ------- --------- -------- 132.146 BTRL-NET 701 1238 British Telecom Research Laboratories, Martlesham Heath, Ipswich, Suffolk, UNITED KINGDOM 138.123 DELAWARETECH 86 279 Delaware Technical and Community College, Dover, DE 19903, USA 138.198 INMOS 701 1238 INMOS Limited, 1000 Aztec West, Bristol, UNITED KINGDOM 141.43 HFB-NET 754 751 Hochschule fuer Bauwesen Cottbus, D-O-7500 Cottbus, GERMANY 150.130 AIEG-MOT 266 267 Network and Communication Systems, Motorola, Automotive and Industrial Electronics Group, 4000 Commercial Avenue, Northbrook, IL 60062, USA 150.175 GSI 701 1238 GSI, 25 Bd de l'Amiral Bruix, 75116 Paris, FRANCE 153.98 XLINK-BNET6 754 751 University of Karlsruhe, XLINK-Project, Am Fasanengarten 5, D-W-7500 Karlsruhe, GERMANY 158.4 CARSON-NET1 164 184 USAISC Ft. Carson, USAISC, Bld. 1014, Ft. Carson, CO 80913, USA 158.43 PIPEX-NET 701 702 PIPEX, 216 Cambridge Science Park, Milton Road, Cambridge, CB4 4WA, UNITED KINGDOM 158.64 RESTENA 590 Restena Ministry of Education Grand-Duchy of, 6, rue Coudenhove-Kalergi, L-1359 Luxembourg 192.26.234 INMOS-C 701 1238 INMOS Limited, 1000 Aztec West, Bristol, UNITED KINGDOM 192.82.147 FAMULAN 279 86 Florida A & M University, Perry Paige Building, Room 107, Tallahassee, FL 32307, USA 192.91.201 BJNET 701 1238 Boldon James Limited, Brundrett House, Sandbach Road South, Alsager, Stoke-on-Trent ST7, 2LT, UNITED KINGDOM 192.129.37 XLINK-CNET5 754 751 GENIAS, Erzgebirgsstr. 2, W-8402 Neutraubling, GERMANY 192.148.172 AIXSERV-NET 754 751 IBM Corporation, 11400 Burnet Road, Internal Zip 2900, Building 42, Austin, TX 78758, USA 192.153.193 LAMPHERE 233 177 Lamphere Schools, John Page Middle School, 29615 Tawas, Madison Heights, MI 48071, USA Total T1 configured networks: 5113 T3 Network: ---------- Network IP: 138.123 Network Name: DELAWARETECH Location: Delaware Technical and Community College, Dover, DE 19903, USA Country Code: US 1:86 SURANET Regional Network 2:279 Georgia Tech Network IP: 141.43 Network Name: HFB-NET Location: Hochschule fuer Bauwesen Cottbus, D-O-7500 Cottbus, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 150.130 Network Name: AIEG-MOT Location: Network and Communication Systems, Motorola, Automotive and Industrial Electronics Group, 4000 Commercial Avenue, Northbrook, IL 60062, USA Country Code: US 1:266 CICNET at MERIT 2:267 CICNET at UIUC Network IP: 153.98 Network Name: XLINK-BNET6 Location: University of Karlsruhe, XLINK-Project, Am Fasanengarten 5, D-W-7500 Karlsruhe, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 158.43 Network Name: PIPEX-NET Location: PIPEX, 216 Cambridge Science Park, Milton Road, Cambridge, CB4 4WA, UNITED KINGDOM Country Code: GB 42:702 Alternet Router 43:701 Alternet Router Network IP: 192.82.147 Network Name: FAMULAN Location: Florida A & M University, Perry Paige Building, Room 107, Tallahassee, FL 32307, USA Country Code: US 1:279 Georgia Tech 2:86 SURANET Regional Network Network IP: 192.129.37 Network Name: XLINK-CNET5 Location: GENIAS, Erzgebirgsstr. 2, W-8402 Neutraubling, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 192.148.172 Network Name: AIXSERV-NET Location: IBM Corporation, 11400 Burnet Road, Internal Zip 2900, Building 42, Austin, TX 78758, USA Country Code: US 1:1782 AIXSERV-AS, ENSS 174 Network IP: 192.153.193 Network Name: LAMPHERE Location: Lamphere Schools, John Page Middle School, 29615 Tawas, Madison Heights, MI 48071, USA Country Code: US 1:237 MERIT network Total configured T3 networks: 3280 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From aggarwal@nisc.jvnc.net Tue Apr 14 17:09:15 1992 Received: from nisc.jvnc.net by merit.edu (5.65/1123-1.0) id AA13985; Tue, 14 Apr 92 17:09:15 -0400 Received: by nisc.jvnc.net (5.65/1.34) id AA00573; Tue, 14 Apr 92 17:09:12 -0400 From: aggarwal@nisc.jvnc.net (Vikas Aggarwal) Message-Id: <9204142109.AA00573@nisc.jvnc.net> Subject: SNMP 'snmppoll' data cruncher program version 1.1 To: njm, oswg-l@wugate.wustl.edu, snmp@nisc.psi.net, regional-techs Date: Tue, 14 Apr 92 17:09:10 EDT Cc: vikas@jvnc.net X-Mailer: ELM [version 2.3 PL11] At the last IETF I had mentioned that I had developed an application for compacting the SNMP data collected by the PSI 'snmppoll' program. The 'opstat' IETF group was also working on data exchange format and all that,,, This might give them ideas, Well, the application is called 'snmppoll-dc' (for snmppoll data cruncher) and it reduces a 60 MB data file to about 10MB (a reduction of about 6 times). It can handle any type of data, and the output format is still ascii. The program has a lot more capabilities like acting like a filter, generating data for 'xgraph', etc. An accompanying program, 'snmppoll-reporter' is a reporting application for the processed data. (As an example, gives octets per 10 minutes for each hour of the day). It can also generate output for plotting on a 3-D plotting program (like GNUplot). Anyway, the README file is attached below. If folks do make improvements, I will gladly incorporate into my code. The source is available from: ftp.jvnc.net under ~ftp/pub/snmppoll-dc1.1.tar.Z -vikas vikas@jvnc.net (609) 258-2403 JvNCnet, Princeton, NJ -------------------------------------------------------------------------- README file for snmppoll-cruncher ---------------------------------- This software compacts the snmp data collected via the PSI 'snmppoll' data collecting agent, and is also capable of various types of data manipulations on the raw/processed data. It was developed mainly to improve the storage requirements of SNMP (without resorting to a database) and also for ease of extracting and manipulating data. The various programs contained in this directory are: snmppoll-dc - (snmppoll data cruncher). This program changes the long/raw format of 'snmppoll' from: TIME VARIABLE HEXVALUE VALUE into VARIABLE SITENAME START-TIME END-TIME START-VALUE END-VALUE TIMESTAMP VALUE TIMESTAMP VALUE TIMESTAMP VALUE TIMESTAMP VALUE TIMESTAMP VALUE TIMESTAMP VALUE By avoiding the repetition of the variable name each time, the program reduces the data by a factor of about 6 or better. The program can also handle string data, and can also read its earlier processed data. In this mode, it can act like a filter or be used for concatenating several pre-processed data files. It can also generate output suitable for being piped into 'xgraph'. Incidentally, it can reconvert the processed data back to the original raw snmppoll format (except that the hexvalue is replaced with the decimal value instead). snmppoll-reporter - generates reports from the data provided in the 'snmppoll-dc' format. This program presently just calculates the deltas in the specified time periods, but can be easily modified to do more things like rate, mean, etc. slists - Collection of routines for singly linked lists. getdate - converts date strings into a long integer. Straight from the GNU distribution for those systems that lack this library call. In fact, I would recommend using this one over your system lib (in case you have it). strstr.c - return the offset of one string within another. From the GNU distribution for those systems that lack this library call. zaphod-airport1.ds1 - A sample of the raw snmp data collected by the PSI 'snmppoll' program. Can be used for testing purposes. Man pages are provided. The version number of this release will be in the file 'version.h'. All comments to vikas@jvnc.net Vikas Aggarwal JvNCnet vikas@jvnc.net - - - - - - - - - - - - - - - - - From bsb Thu Apr 16 06:16:36 1992 Received: by merit.edu (5.65/1123-1.0) id AA18098; Thu, 16 Apr 92 06:16:38 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA18094; Thu, 16 Apr 92 06:16:36 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA11990; Thu, 16 Apr 92 06:16:35 EDT Date: Thu, 16 Apr 92 06:16:35 EDT Message-Id: <9204161016.AA11990@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- No additions Total configured T1 networks: 5113 T3 Network: ---------- AS 194 - NCAR (National Center for Atmospheric Research) Regional Network ENSS 141 moved 12 nets to the T3 backbone AS 209 - Westnet Regional (Colorado Attachment) ENSS 141 moved 100 nets to the T3 backbone AS 210 - Westnet Regional (Utah attachment) ENSS 142 moved 8 nets to the T3 backbone Total configured T3 networks: 3399 ***************************************** -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From skw Fri Apr 17 11:58:38 1992 Received: by merit.edu (5.65/1123-1.0) id AA09431; Fri, 17 Apr 92 11:58:45 -0400 From: "Steven K. Widmayer" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA09423; Fri, 17 Apr 92 11:58:38 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA17586; Fri, 17 Apr 92 11:58:36 EDT Date: Fri, 17 Apr 92 11:58:36 EDT Message-Id: <9204171558.AA17586@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 128.53 Network Name: SRI-ERG-NET Location: SRI International, 333 Ravenswood Ave, Menlo Park, CA, 94025, USA Country Code: US 1:200 BARRNET Regional Network 2:201 BARRNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 139.11 Network Name: UNIBWH Location: Universitaet der Bundeswehr Hamburg, Universitaet der Bundeswehr Hamburg, Rechenzentrum, Holstenhofweg 85, D-W-2000 Hamburg 70, GERMANY Country Code: DE 1:701 Alternet Network Network IP: 141.37 Network Name: FH-KN Location: Fachhochschule Konstanz, Hochschule fuer Technik, Brauneggerstrasse 55, D-W-7750 Konstanz, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 141.58 Network Name: UNI-STG-F-NET Location: University of Stuttgart, Computer Center, Allmandring 30, D-7000 Stuttgart 80, GERMANY Country Code: DE 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 141.200 Network Name: KAE-CASE-NET Location: Atlas Elektronik, Abt. EZF1, Postfach 448545, D-W-2800 Bremen 44, GERMANY Country Code: DE 1:701 Alternet Network Network IP: 147.4 Network Name: NET-HOFSTRA-NET Location: Hofstra University, 1000 Fulton Avenue, Hempstead, NY 11550, USA Country Code: US 1:174 NYSERNET Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 147.240 Network Name: TACOM-NET1 Location: Directorate of Information Management, US Army Tank-Automotive Command (TACOM), ATTN: ASQNC-TAC, Warren, Michigan 48397-5000, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 157.27 Network Name: IVRUNIV-NET Location: Universita di Verona; Centro di Informatica e Calcolo Automatico (C.I.C.A.), Via dell Artigliere 19; I-37100 Verona, ITALY Country Code: IT 1:590 EASInet Regional Network Network IP: 158.46 Network Name: PEINET Location: Protocol Engines, Incorporated, 301 W. Evelyn, Mountain View, CA 94043, USA Country Code: US 1:200 BARRNET Regional Network 2:201 BARRNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.67.77 Network Name: UTOS-NMO Location: United Technologies Optical Systems, 1601 Randolph Road, Suite 100 South, Albrquerque, NM 87106, USA Country Code: US 1:209 WestNet Regional network (East) 2:210 Westnet Regional Network (West) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.102.230 Network Name: SANGAMON Location: Sangamon State University, Springfield, IL 62794-9243, USA Country Code: US 1:267 CICNET Regional Network (UIUC connection) 2:266 CICNET Regional Gateway 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.107.167 Network Name: CIT-PALOMAR Location: Palomar Observatory/Caltech, P.O. Box 200, Palomar Mountain, CA 92060, USA Country Code: US 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.108.17 Network Name: TAHC Location: Texas Animal Health Commission, 210 Barton Springs Road, Austin, TX 78704-0210, USA Country Code: US 1:280 Sesquinet Regional Network 2:114 Sesquinet 3:1700 Sesquinet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.146.240 Network Name: ACCDVM Location: Alamo Community College District, 811 W. Houston St., San Antonio, TX 78207, USA Country Code: US 1:280 Sesquinet Regional Network 2:114 Sesquinet 3:1700 Sesquinet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.146.241 Network Name: INFOSERV Location: InfoServ, 20 Harold St, Suite 33, San Jose, CA, USA Country Code: US 1:200 BARRNET Regional Network 2:201 BARRNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.150.115 Network Name: B-W Location: Baldwin Wallace College, 275 Eastland Road, Berea, OH 44017, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.160 Network Name: COLOSPGSCTA Location: CTA, INCORPORATED, 7150 Campus Drive, Suite 100, Colorado Springs, CO 80920, USA Country Code: US 1:209 WestNet Regional network (East) 2:210 Westnet Regional Network (West) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.244 Network Name: SIMAPS-ENET Location: SIMA/NRMTF Puget Sound, PSNS Supply Pier C, Bremerton, WA 98314-5320, USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.153.245 Network Name: CTFGUAM-NET Location: COMNAVSURFGRU WESTPAC CTF-73 Rep. GUAM, Officer in Charge, COMNAVSURFGRU WESTPAC Rep. GUAM CTF-73, PSC 455 Box 184, FPO AP 96540-1085, GUAM Country Code: GU 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.153.246 Network Name: PERACV-ENET Location: Naval Sea Systems Command Detachment PERA (CV), 1305 Ironsides Ave., Bremerton, WA 98310, USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.156.81 Network Name: CSL-NET Location: Commander, Submarine Force, U.S. Atlantic Fleet, Norfolk, RTD&E Division, Code 651, 271 Catalina Blvd., San Diego, CA 92152-65651, USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.156.82 Network Name: CTF63-NAP Location: Commander, Task Force SIX THREE, Naples, ITALY, 271 Catalina Blvd., San Diego, CA 92152-65651, USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.156.83 Network Name: FISH-NET Location: Naval Command, Control and Ocean Surveillance Center / San Diego, 271 Catalina Blvd., San Diego, CA 92152-65651 USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.156.84 Network Name: PRC-NET2 Location: PRC, Inc., 468 Viking Drive, Virginia Beach, VA 23452, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.85 Network Name: RSG-NOR-NET Location: Readiness Support Group, Norfolk, Shore Intermediate Maintenance Activity, Norfolk, VA 23511-6135, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.86 Network Name: SIMA-CHS-NET Location: Shore Intermediate Maintenance Activity, Charleston, Charleston, SC 20408-5950 USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.87 Network Name: SIMA-ISD-NET Location: Shore Intermediate Maintenance Activity, Ingleside, Ingleside, TX 78362-5000 USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.156.88 Network Name: SIMA-LCK-NET Location: Shore Intermediate Maintenance Activity, Little Creek, Little Creek, VA 23521-5250 USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.89 Network Name: SIMA-MOB-NET Location: Shore Intermediate Maintenance Activity, Mobile, Mobile, AL 36605-6099 USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.90 Network Name: SIMA-MYP-NET Location: Shore Intermediate Maintenance Activity, Mayport, Mayport, FL 32228 USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.91 Network Name: SIMA-NOR-NET Location: Shore Intermediate Maintenance Activity, Norfolk, Norfolk, VA 23511-6135 USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.92 Network Name: SIMA-NWP-NET Location: Shore Intermediate Maintenance Activity, Newport, Bldg. 68, Pier 2, Newport, RI 02841 USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.93 Network Name: SIMA-PGL-NET Location: Shore Intermediate Maintenance Activity, Pascagoula, Sima Bldg. 40, Naval Station, Pascagoula, MS 39567-5000, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.94 Network Name: SIMA-PTM-NET Location: Shore Intermediate Maintenance Activity, Portsmouth, Portsmouth, VA 23702-5001, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.95 Network Name: SIMA-STI-NET Location: Shore Intermediate Maintenance Activity, New York, 355 Front Street, Staten Island, NY 10304, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.156.96 Network Name: SRU-BAH-NET Location: COMNAVSURFGRU-MED DETACHMENT BAHRAIN, PSC 451, Box 29, SRU Det-Bahrain, FPO AE 09834-2829, SAUDI ARABIA Country Code: SA 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Total T1 configured networks: 5148 T1 Special Additions: AS# NSS Gate IP Protocol Description ---- ---- ------------ ---------- ------------- 1207 5 192.5.146.13 BGP DEC DS/5000 PSCNET Regional Network AS# NSS Gate IP Protocol Description ---- ---- ------------ ---------- ------------- 568 13 192.52.195.26 BOTH cisco Milnet at FIX-West T3 Network: ---------- Network IP: 128.53 Network Name: SRI-ERG-NET Location: SRI International, 333 Ravenswood Ave, Menlo Park, CA, 94025, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 141.37 Network Name: FH-KN Location: Fachhochschule Konstanz, Hochschule fuer Technik, Brauneggerstrasse 55, D-W-7750 Konstanz, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 141.58 Network Name: UNI-STG-F-NET Location: University of Stuttgart, Computer Center, Allmandring 30, D-7000 Stuttgart 80, GERMANY Country Code: DE 1:1324 ANS New York City - DNSS 35 Network IP: 147.4 Network Name: NET-HOFSTRA-NET Location: Hofstra University, 1000 Fulton Avenue, Hempstead, NY 11550, USA Country Code: US 1:174 NYSERNET Regional Network / PSI Network IP: 158.46 Network Name: PEINET Location: Protocol Engines, Incorporated, 301 W. Evelyn, Mountain View, CA, 94043, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.67.77 Network Name: UTOS-NMO Location: United Technologies Optical Systems, 1601 Randolph Road, Suite 100 South, Albrquerque, NM 87106, USA Country Code: US 1:209 Westnet Regional (Colorado Attachment) - ENSS 141 2:210 Westnet Regional (Utah Attachment) - ENSS 142 Network IP: 192.102.230 Network Name: SANGAMON Location: Sangamon State University, Springfield, IL 62794-9243, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 192.107.167 Network Name: CIT-PALOMAR Location: Palomar Observatory/Caltech, P.O. Box 200, Palomar Mountain, CA 92060, USA Country Code: US 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.108.17 Network Name: TAHC Location: Texas Animal Health Commission , 210 Barton Springs Road, Austin, TX 78704-0210, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network 3:1700 SESQUINET Regional Network Network IP: 192.146.240 Network Name: ACCDVM Location: Alamo Community College District, 811 W. Houston St., San Antonio, TX 78207, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network 3:1700 SESQUINET Regional Network Network IP: 192.146.241 Network Name: INFOSERV Location: InfoServ, 20 Harold St, Suite 33, San Jose, CA, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.150.115 Network Name: B-W Location: Baldwin Wallace College, 275 Eastland Road, Berea, OH 44017, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 192.153.160 Network Name: COLOSPGSCTA Location: CTA, INCORPORATED, 7150 Campus Drive, Suite 100, Colorado Springs, CO 80920, USA Country Code: US 1:209 Westnet Regional (Colorado Attachment) - ENSS 141 2:210 Westnet Regional (Utah Attachment) - ENSS 142 Total configured T3 networks: 3411 T3 Special Additions: AS Number: 574 AS Notes: PSCNET Regional Network AS Country Code: US ANS: No Gate: 192.5.146.13 - snipe.psc.edu ENSS 132 - Pittsburgh AS Number: 1207 AS Notes: PSCNET Regional Network AS Country Code: US ANS: No Gate: 192.88.114.13 - snipe.psc.edu ENSS 132 - Pittsburgh AS Number: 1225 AS Notes: CICNET at Argonne Labs AS Country Code: US ANS: No Gate: 192.5.180.23 - anl.cic.net Argonne Labs, Chicago, Illinios ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Steve Widmayer / Riaz Taherzadeh-Yazdian / Michael O'Neill Merit/NSFNET - - - - - - - - - - - - - - - - - From donnab@CERF.NET Mon Apr 20 15:15:26 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA28541; Mon, 20 Apr 92 15:15:26 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA18159; Mon, 20 Apr 92 12:15:18 PDT Date: Mon, 20 Apr 92 12:15:18 PDT From: Donna Bigley Message-Id: <9204201915.AA18159@nic.cerf.net> To: broidoj@Sds.Sdsc.Edu, help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, April 13th, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, April 13th through Sunday, April 19th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 19-april-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 906 SITE: UCLA SITES AFFECTED: UCLA-UCSB T1 TIME STARTED: MON. 4-13-92 13:34 TIME ENDED: MON. 4-13-92 15:29 TIME STARTED: MON. 4-13-92 16:26 TIME ENDED: MON. 4-13-92 16:33 TIME ELAPSED: 2 hour 2 min. (Intermittent Access) REASON: Link Failure (GTE Telco Problems) TICKET #: 906 SITE: UCLA SITES AFFECTED: UCLA-SDSC T1 TIME STARTED: MON. 4-13-92 13:38 TIME ENDED: MON. 4-13-92 16:26 TIME ELAPSED: 2 hours 48 min. REASON: Link Failure (GTE Telco Problems) TICKET #: 906 SITE: UCLA SITES AFFECTED: UCLA-UCI T1 TIME STARTED: MON. 4-13-92 13:38 TIME ENDED: MON. 4-13-92 17:00 TIME ELAPSED: 3 hours 22 min. (Intermittent Access) REASON: Link Failure (GTE Telco Problems) TICKET #: 907 SITE: Los Nettos (Caltech side) SITES AFFECTED: Los Nettos TIME STARTED: TUE. 4-14-92 12:00 TIME ENDED: TUE. 4-14-92 12:15 TIME ELAPSED: 15 min. REASON: Site Scheduled Maintenance TICKET #: 911 SITE: CICESE SITES AFFECTED: CICESE TIME STARTED: WED. 4-15-92 11:43 TIME ENDED: WED. 4-15-92 13:27 TIME ELAPSED: 1 hour 44 min. REASON: Site Scheduled Maintenance TICKET #: 910 SITE: Los Nettos (UCLA side) SITES AFFECTED: Los Nettos TIME STARTED: WED. 4-15-92 12:38 TIME ENDED: WED. 4-15-92 12:53 TIME ELAPSED: 15 min. REASON: Site Scheduled Maintenance TICKET #: 914 SITE: Qualcomm SITES AFFECTED: Qualcomm TIME STARTED: WED. 4-15-92 15:00 TIME ENDED: WED. 4-15-92 15:05 TIME ELAPSED: 5 min. REASON: Equipment Trouble TICKET #: 913 SITE: UCLA-SDSC T1 SITES AFFECTED: UCLA-SDSC T1 TIME STARTED: THU. 4-16-92 01:36 TIME ENDED: THU. 4-16-92 04:25 TIME ELAPSED: 2 hours 49 min. REASON: Vendor Scheduled Maintenance TICKET #: 919 SITE: SDSU SITES AFFECTED: SDSU TIME STARTED: FRI. 4-17-92 20:04 TIME ENDED: SAT. 4-18-92 12:00 TIME ELAPSED: 15 hours 56 min. REASON: Site Scheduled Maintenance TICKET #: 921 SITE: UCI-UCLA T1 SITES AFFECTED: UCI-UCLA T1 TIME STARTED: SAT. 4-18-92 06:00 TIME ENDED: SAT. 4-18-92 14:02 TIME ELAPSED: 8 hours 2 min. REASON: Unknown TICKET #: 916 SITE: GTE SITES AFFECTED: GTE TIME STARTED: SAT. 4-18-92 16:44 TIME ENDED: SUN. 4-19-92 09:32 TIME ELAPSED: 16 hours 48 min. REASON: Site Scheduled Maintenance ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps No capacities available this week. SDSC/CALTECH 1.544 mbps 10.0% 15:00 SDSC/UCI 1.544 mbps 07.8% 14:00 SDSC/UCLA 1.544 mbps 07.3% 14:00 SDSC/UCOP 1.544 mbps 03.6% 11:00 UCI/UCLA 1.544 mbps 01.1% 13:00 SDSC/UCR 512 kbps 02.5% 08:00 UCLA/UCSB 512 kbps 07.5% 16:00 SDSC/AGI 1.544 mbps 00.1% 08:00 SDSC/BIOSYM 1.544 mbps 00.1% 09:00 SDSC/GA 1.544 mbps 00.3% 14:00 SDSC/GD 1.544 mbps 00.6% 10:00 SDSC/SAIC 1.544 mbps 00.9% 14:00 SDSC/SCAQMD 1.544 mbps 00.01% 02:00 SDSC/SDSU 1.544 mbps 01.7% 12:00 UCI/CSU CO(SWRL) 1.544 mbps 02.1% 13:00 UCOP/APPLE 1.544 mbps 00.8% 08:00 UCOP/CISCO 1.544 mbps 00.1% 10:00 UCR/LLUMC 1.544 mbps 00.1% 23:00 CALTECH/CADAM 56 kbps 01.5% 14:00 CALTECH/CITY OF HOPE 56 kbps 00.5% 08:00 CALTECH/CLAREMONT 56 kbps 22.3% 14:00 CALTECH/DISNEY 56 kbps 05.3% 15:00 CALTECH/OXY 56 kbps 10.2% 21:00 SDSC/AJS 56 kbps 01.3% 14:00 SDSC/KOREA 56 kbps 04.9% 00:00 SDSC/QUALCOMM 56 kbps 09.9% 17:00 SDSC/SCIH 56 kbps 03.2% 02:00 SDSC/USD 56 kbps 06.3% 16:00 SDSC/USIU 56 kbps 00.5% 11:00 SDSC/XEROX 56 kbps 00.4% 18:00 UCI/CMD 56 kbps 06.3% 20:00 UCI/EMULEX 56 kbps 01.7% 15:00 UCI/FULLERTON 56 kbps 01.4% 13:00 UCI/HUGHES 56 kbps 11.6% 10:00 UCI/MTI 56 kbps 04.0% 15:00 UCI/SPARTA 56 kbps 06.5% 01:00 UCI/UNOCAL 56 kbps 06.0% 16:00 UCLA/ISX 56 kbps 01.4% 10:00 UCLA/PEPPERDINE 56 kbps 01.7% 08:00 UCLA/QUOTRON 56 kbps 08.5% 13:00 UCLA/SMC 56 kbps 01.4% 12:00 UCOP/FARALLON 56 kbps 03.2% 09:00 UCOP/INTEL 56 kbps No capacities available for this week. UCOP/LSIL 56 kbps 07.0% 21:00 UCOP/NETLABS 56 kbps 12.5% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Apr. 20, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 22 days 05 hours 41 minutes SDSC LongBoard [134.24.99.254] Up: 11 days 14 hours 56 minutes SDSC Drzog [132.249.16.13] Up: 31 days 07 hours 00 minutes SDSC Hang10 [132.249.16.15] Up: 10 days 16 hours 26 minutes UCI [128.200.1.101] Up: 101 days 16 hours 07 minutes UCLA [128.97.130.10] Up: 14 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 26 days 16 hours 38 minutes UCR [134.24.108.105] Up: 29 days 06 hours 48 minutes CERF 1544 AGI [134.24.202.110] Up: 66 days 13 hours 54 minutes APPLE [134.24.70.200] Up: 175 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 16 days 05 hours 27 minutes CISCO Systems [134.24.54.200] Up: 40 days 04 hours 20 minutes CSUCO/SWRL [130.150.102.200] Up: 17 days 18 hours 49 minutes GA [134.24.221.200] Up: 30 days 19 hours 56 minutes GD [134.24.60.200] Up: 49 days 13 hours 31 minutes LLUMC [134.24.208.200] Up: 152 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 106 days 08 hours 34 minutes SCAQMD [134.24.234.200] Up: 122 days 14 hours 27 minutes SDSU [192.77.100.101] Up: 01 days 12 hours 17 minutes [Site Scheduled Maintenance - Ticket #919] UCSB [134.24.107.107] Up: 152 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 93 days 14 hours 17 minutes CADAM [134.24.229.200] Up: 75 days 13 hours 01 minutes CLAREMONT [134.24.206.109] Up: 23 days 17 hours 39 minutes CMD [134.24.218.200] Up: 83 days 13 hours 14 minutes DATAPRODUCTS [134.24.211.104] Up: 19 days 09 hours 33 minutes DISNEY [134.24.207.211] Up: 09 days 10 hours 00 minutes EMULEX [134.24.209.212] Up: 08 days 12 hours 12 minutes FARALLON [134.24.56.200] Up: 21 days 02 hours 24 minutes FULLERTON [134.24.214.217] Up: 35 days 16 hours 57 minutes HUGHES [134.24.204.200] Up: 08 days 03 hours 08 minutes INTEL [134.24.55.200] Up: 22 days 11 hours 34 minutes LSIL [134.24.72.200] Up: 71 days 13 hours 08 minutes MTI [134.24.216.100] Up: 107 days 13 hours 39 minutes NETLABS [134.24.71.200] Up: 25 days 08 hours 51 minutes OXY [134.24.205.108] Up: 13 days 16 hours 27 minutes PEPPERDINE [134.24.203.218] Up: 09 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 04 days 09 hours 11 minutes [Equipment Trouble - Ticket #914] QUOTRON [134.24.230.202] Up: 15 days 12 hours 00 minutes SANTA MONICA [134.24.210.219] Up: 37 days 12 hours 40 minutes SCI-HOR [134.24.109.205] Up: 24 days 04 hours 27 minutes SERI/KOREA [134.24.223.200] Up: 13 days 00 hours 40 minutes SPARTA [134.24.215.200] Up: 20 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 45 days 01 hours 57 minutes USD [134.24.201.106] Up: 24 days 06 hours 12 minutes USIU [134.24.222.215] Up: 288 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 172 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 41 days 05 hours 09 minutes DNC-UCI [134.24.2.2] Up: 103 days 03 hours 24 minutes DNC-UCLA [134.24.3.2] Up: 14 days 06 hours 25 minutes DNC-CALTECH [134.24.4.2] Up: 22 days 05 hours 42 minutes DNC-UCOP [134.24.5.2] Up: 09 days 17 hours 01 minutes - - - - - - - - - - - - - - - - - From bsb Tue Apr 21 08:41:14 1992 Received: by merit.edu (5.65/1123-1.0) id AA28227; Tue, 21 Apr 92 08:41:16 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA28223; Tue, 21 Apr 92 08:41:14 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA02541; Tue, 21 Apr 92 08:41:13 EDT Date: Tue, 21 Apr 92 08:41:13 EDT Message-Id: <9204211241.AA02541@home.merit.edu> To: nwg Subject: Re: Additions to the NSFNET policy-based routing database Folks, I lied. The reports did not make it out to the NIS.NSF.NET machine. There is an ftp problem on the system that supports the database. We'll send a message to nwg when the reports make their way to the NIS machine. Apologies, -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From noc Tue Apr 21 08:16:24 1992 Received: by merit.edu (5.65/1123-1.0) id AA27434; Tue, 21 Apr 92 08:16:28 -0400 From: "Merit Network Operations Center" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA27430; Tue, 21 Apr 92 08:16:24 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA02208; Tue, 21 Apr 92 08:16:23 EDT Date: Tue, 21 Apr 92 08:16:23 EDT Message-Id: <9204211216.AA02208@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 138.209 Network Name: LTVAD Location: LTV Aerospace and Defense, 9314 W. Jefferson, Dallas, TX 75265, USA Country Code: US 1:174 NYSERNET Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.88.12 Network Name: UTEXAS-LANDS Location: University of Texas System, Office of Telecommunication Services, Balcones Research Center, CMS1.156, 10100 Burnet Road, Austin, TX 78758-4497, USA Country Code: US 1:280 Sesquinet Regional Network 2:114 Sesquinet 3:1700 Sesquinet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.100.12 Network Name: NSI-TEMP-NET4 Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA Country Code: US 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 18:754 T1-T3 Network Interconnect (Houston, TX) 19:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.133.3 Network Name: BELL-ATL-COM Location: Bell Atlantic Corp., 1717 Arch St., 24W, Philadelphia, PA 19103, USA Country Code: US 1:1206 PSCNET 2:204 PSCNET Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.150.172 Network Name: ACCELR8-NET Location: Accelr8 Technology Corporation, 303 East 17th Avenue, Suite 108, Denver, CO 80203, USA Country Code: US 1:209 WestNet Regional network (East) 2:210 Westnet Regional Network (West) 18:754 T1-T3 Network Interconnect (Houston, TX) 19:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.89 Network Name: UBILAB Location: UBILAB (UBS Informatics Laboratory), SBG UBILAB, Flurstr. 62, CH-8048 ZURICH, SWITZERLAND Country Code: CH 1:590 EASInet Regional Network Network IP: 192.153.218 Network Name: RANDOMACCESS Location: Random Access, Inc., 8000 East Iliff, Denver, CO 80231, USA Country Code: US 1:209 WestNet Regional network (East) 2:210 Westnet Regional Network (West) 18:754 T1-T3 Network Interconnect (Houston, TX) 19:751 T1-T3 Network Interconnect (San Diego, CA) Total T1 configured networks: 5155 T3 Network: ---------- Network IP: 138.129 Network Name: CORD Location: Concordia College, 901 South 8th Street, Moorhead, MN 56560, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 138.209 Network Name: LTVAD Location: LTV Aerospace and Defense, 9314 W. Jefferson, Dallas, TX 75265, USA Country Code: US 1:174 NYSERNET Regional Network / PSI Network IP: 138.236 Network Name: GACNET Location: Gustavus Adolphus College, Academic Computing, St. Peter, MN 56082, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 143.110 Network Name: CSS-NET Location: College of St. Scholastica, 1200 Kenwood Avenue, Duluth, MN 5581, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 157.187 Network Name: NAVSSES Location: Naval Ship Systems Engineering Station, Philadelphia Naval Base, Philadelphia, PA 19112, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.88.12 Network Name: UTEXAS-LANDS Location: University of Texas System, Office of Telecommunication Services, Balcones Research Center, CMS1.156, 10100 Burnet Road, Austin, TX 78758-4497, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network 3:1700 SESQUINET Regional Network Network IP: 192.100.12 Network Name: NSI-TEMP-NET4 Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA Country Code: US 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.133.3 Network Name: BELL-ATL-COM Location: Bell Atlantic Corp., 1717 Arch St., 24W, Philadelphia, PA 19103, USA Country Code: US 1:1206 PSCNET Regional Network Network IP: 192.150.172 Network Name: ACCERLR8-NET Location: Accelr8 Technology Corporation, 303 East 17th Avenue, Suite 108, Denver, CO 80203, USA Country Code: US 1:209 Westnet Regional (Colorado Attachment) - ENSS 141 2:210 Westnet Regional (Utah Attachment) - ENSS 142 Network IP: 192.153.218 Network Name: RANDOMACCESS Location: Random Access, Inc., 8000 East Iliff, Denver, CO 80231, USA Country Code: US 1:209 Westnet Regional (Colorado Attachment) - ENSS 141 2:210 Westnet Regional (Utah Attachment) - ENSS 142 Total configured T3 networks: 3421 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From bsb Tue Apr 21 09:08:00 1992 Received: by merit.edu (5.65/1123-1.0) id AA29207; Tue, 21 Apr 92 09:08:02 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA29202; Tue, 21 Apr 92 09:08:00 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA02993; Tue, 21 Apr 92 09:07:59 EDT Date: Tue, 21 Apr 92 09:07:59 EDT Message-Id: <9204211307.AA02993@home.merit.edu> To: nwg Subject: Re: Additions to the NSFNET policy-based routing database Greetings. The spiffy new nis.nsf.net files have finally made their way to their humble lodgings. Apologies for any any inconvenience. -B. Sue Blair Merit Network Operations - - - - - - - - - - - - - - - - - From jyy Tue Apr 21 15:48:49 1992 Received: from kiddo.merit.edu by merit.edu (5.65/1123-1.0) id AA12218; Tue, 21 Apr 92 15:48:49 -0400 Received: Tue, 21 Apr 92 15:47:01 -0400 by kiddo.merit.edu (AIX/1.6) Date: Tue, 21 Apr 92 15:47:01 -0400 From: Jessica Yu Message-Id: <9204211947.AA14534@kiddo.merit.edu> To: bgpd, regional-techs Subject: Routing Policy Description Form Cc: jyy Hi, Now you can ftp the Routing Policy Description Form from nis.nsf.net at internet/routing.policies/routing.policy.form. For those who needs to know more about the form, please read rpform.explanation in the same directory. Please ftp it and fill it out. Please send the completed form for you AS to rpform-admin@merit.edu and it will be installed in the directory internet/ routing.policies on nis.nsf.net. All the completed forms will be available for anonymous ftp from that directory. Thanks! --Jessica - - - - - - - - - - - - - - - - - From mak Wed Apr 22 01:28:04 1992 Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA00069; Wed, 22 Apr 92 01:28:04 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA21384; Wed, 22 Apr 92 01:28:02 EDT Date: Wed, 22 Apr 92 01:28:02 EDT From: mak Message-Id: <9204220528.AA21384@home.merit.edu> To: regional-techs Subject: Phase III RS-960 Deployment Status Update Phase-III Deployment Status Update ================================== Jordan Becker, ANS Mark Knopper, Merit The phase-III deployment schedule involving the replacement of "Hawthorne" T3 interface adapters and DSU cards in the RS/6000 T3 routers is progressing on-schedule. We have completed our system testing and are conducting on-going regression tests on the test network (recent testing and upgrade activies described below). Pending any un-foreseen problems that come up, the hardware upgrades will begin on Friday 4/24 at 23:00 local time at the Seattle CNSSs, Denver CNSSs, Seattle ENSS143, Boulder ENSS141, and Salt Lake ENSS142. In preparation for the upgrade, we have been making software changes to the production T3 system in advance to support the hardware upgrades that are scheduled to begin on 4/24. These changes include a new system software build that supports the RS960 drivers, kernel, and microcode. We are also installing a new SNMP program that support the new c-bit parity DSU function, and several bug fixes for existing FDDI and T960 ethernet freeze problems. The proposed maintainance window for these network software upgrades is as follows: 1. 4/21 at 12-1am EDT: Install build 2.78.22 on Seattle CNSS's 88, 89 and 91; Denver CNSS's 96, 97, and 99; University of Washington ENSS 143; Boulder ENSS 141; and Salt Lake ENSS 142. (done) 2. 4/22 at 6am EDT: Install build 2.78.22 on San Francisco CNSS's 8, 9, and 11; Los Angeles CNSS's 16, 17, and 19; Palo Alto ENSS 128; NASA Ames/FIX-W ENSS 144; and San Diego ENSS 135. With the cutover of traffic from T1->T3 of FIX-W, Westnet-E, CICnet, NCAR and Midnet in the last 2 weeks, we will halt any additional regional traffic cut-overs until after the phase-III upgrades are stabilized. We are in the process of contacting each regional individually to discuss the upgrade and what you can do to help us ensure that this goes as smoothly as possible. We will be requesting coordination with regionals in the use of the T1 backbone as backup to the T3 system during different points in the upgrade schedule. This may require employing emergency procedures such as disabling AS peer sessions to the T3 backbone on some regionals if we run into trouble (not that we anticipate that, since we are confident that testing has been very thorough). During the upgrade schedule, there will be a growing router cloud that supports the RS960 T3 technology and a shrinking router cloud that supports the Hawthorne T3 technology. We have designed the interface points between these clouds to try and minimize traffic flow across them at any give time since the T3 system is carrying considerable traffic and these "hybrid links" represent a potential performance bottleneck. A internal T3 routing link metric assignment plan is being generated to minimize Hawthorne-cloud to RS960-cloud traffic (by assigning an increased metric to selected T3 hybrid links). We are performing an AS-AS regional traffic simulation to design these internal link metrics in an way that balances traffic flow across the T3 system and avoids over-loading of the hybrid links. We have already done some initial experimentation with different link metrics and validated the results. These link metrics will be changed manually by our engineers at different points in the deployment process to spread the load across the hybrid links and thus minimize load on any single hybrid machine. An appendix to this message contains some more information on metric adjustments and how these were determined and verified. This work is credited to Elise Gerich of the Merit IE group. We would like to develop a procedure and plan with each regional for cutover to the T1 backbone during scheduled periods, and during possible unscheduled periods in the event that a hybrid link should get too close to saturation. We would like to coordinate a plan where our engineers maintain a pre-designated list of T3 ENSS nodes in each phase of the deployment that get configured down (off-line), in conjuction with a regional switching their routing over to divert traffic to the T1 backbone. Phase-III Technology Testing Status =================================== Since our last update on phase-III deployment testing, we have closed several problems that were identified and we will continue to regression test up to and during the deployment, and maintain a scaled down replica of the T3 system configuration on the T3 research network during the deployment. This will allow us to continue testing and support any needed tests for problems that may be identified during the deployment. Since the last report, we have been focusing our test efforts in the following areas: 1. Regression tests for bug fixes in the current T3 system. We have fixed several bugs in the current production T3 network FDDI driver, T960 ethernet/T1 interface driver and associated microcode. These fixes have been merged into the production RS960 system software build scheduled for deployment this week and have been regression tested. 2. Stress testing of the new build. We have corrected an earlier problem we were experiencing with a test tool that copies all production ethernet traffic with a new destination address onto the T3 Research network to simulate real production network traffic flows. This so called "copy tool" is working on the test network and has been a major component of our stress testing. 3. Full RS960 (4 interface) configuration testing. We have focused much of our testing over the last couple of months on the mixed technology configurations (e.g. Hawthorne T3 adapters and RS960 T3 adapters co-resident in the same router and network) since we were most concerned about the actual deployment process. We have most recently tested the full RS960 (4 interfaces in a CNSS) configuration which we are less concerned about. 4. FDDI peering tests. We have tested ENSS configurations that include an FDDI interface and an RS960 T3 interface that peer with with 2 FDDI equipped Cisco routers. 5. Noise injection testing on T3 lines. We have tested noise injection on the T3 test network circuits with the aid of a test tool provided with the T3Plus Inc. BMX45 bandwidth manager. The results of these tests demonstrated a T3 technologies DSU problem involving SNMP sub-agent signalling. We have addressed this problem for now with a change to the SNMP sub-agent. A PROM change to the DSU will be installed at a later date to avoid any additional SNMP sub-agent overhead required to address this problem. Noise testing on the research network is ongoing, in an attempt to find additional problems during stress and other traffic load tests. 5. T3 routing software testing. One of the tests that we have always wanted to conduct on the T3 Research network is the simulation of 60+ internal routing peers that generate IS-IS LSPs which most accurately mimics the production T3 network. We never had enough nodes on the T3 Research network to generate more than 10 of these internal IBGP peer sessions before. We are now testing with a modified version of our routing software that generates multiple IBGP internal sessions so that we can simulate internal IS-IS routing exchanges with several more internal peers. This will improve our routing software test environment now and in the future. 6. T3 routing software enhancements. There are several new enhancements to the T3 routing software that we have tested with the RS960 technology including an auto-restart function in the event of a daemon failure, BGP version negotiation support, and correct support for the interpretation of inter-AS external metrics. These software changes are independant of the phase-III deployment and will be scheduled for deployment during a maintainence window that does not interfere with the phase-III deployment activities. Other Activities Related to RS960 Deployment -------------------------------------------- NOC training - The NOC requires well documented debugging procedures that operators can understand and execute without problems. This includes new man pages from engineers on RS960 utilities and commands (e.g. ifstat, ccstat, etc.). A disaster recovery procedures checklist has been drafted that includes information on how to recover from problems during and following the deployment. Appendix: Metric Adjustments on the T3 Network by Elise Gerich, Merit/NSFNET Internet Engineering (To fully appreciate the details here it would be appropriate to refer to the map in the file pub/maps/t3topo.ps on merit.edu.) With the advent of the RS960 card rollout, there has been some concern about the performance limits of nodes which have up to three RS960 T3 cards and at least one Hawthorne T3 card. One of the strategies proposed to avoid congestion on the Hawthorne- to-system-to-RS960 interaction is to bypass using links which terminate in this configuration by tuning the link metrics. Since there are multiple paths between any two pairs, it is important to evaluate the effect changing link metrics has on the network as a whole. Since the RS960 card deployment is staged in five phases, we approached the problem by identifying the interfaces where packets would have to traverse both flavors of cards and the system, in each of the four phases of the deployment. The next step was to identify within each phase interfaces which may be underutilized so that we could potentially adjust the metrics to divert traffic from more heavily loaded interfaces to the more lightly loaded interfaces. In phase one, both interfaces are lightly loaded, and it was felt that there was no danger of approaching the performance bottleneck threshold number of packets thru either interface. Therefore, the recommendation is to leave the link metrics unchanged for phase one. In phase two, it is obvious that the majority of the traffic from and to the west coast traverses two interfaces, CNSS8 to 16; and CNSS16 to 64. The objective was to reduce traffic through these two interfaces and to increase traffic through the interface at CNSS96 to 80. In evaluating the multiple paths from the east to the west coast (primarily between Hartford, San Francisco, and Los Angeles it appeared that we could achieve our objective by raising by two the link metrics on two links, 8 to 24 and 16 to 64. In order to test our hypothesis, we raised the link metrics on the links 8-24 and 16-64 from one to three on April 13, 1922 at approximately 16:15 GMT. It was immediately noticeable that traffic was diverted from 8-24 and 16-64 to 80-96. We left these metrics in place for approximately 20 hours. Using the xdview4 program that Bill Norton has written, we graphed the packets per second in and out of the various interfaces on the network. Comparisons of the sample period with the pre and post data samples, indicate that we accomplished our goal of reducing traffic through 8 and 16 and of increasing traffic through 96. In phase three, there will be one purely RS960 path from coast to coast. The objective for this phase was to eliminate multiple, lowest cost paths between Hartford and the west coast nodes of San Francisco, Los Angeles, Seattle, and Denver, and to make the RS960 path (48-32-40-24-8) the lowest cost path (according to link metrics) from coast to coast. After evaluating the multiple paths between Hartford-San Francisco, Hartford-Los Angeles, Hartford-Seattle, and Hartford-Denver, we thought that we could adjust the metrics across the network so that the lowest cost path was the purely RS960 path. This would require changing the metrics on six links. All link metrics on the network would be one, except for 8-24 which is 3, 16-64 which is 3, 96-80 which is 2, 24-80 which is 2, 32-56 which is 2, and 48-72 which is 4. Since this change would force all the east- west traffic onto five nodes, we were hesitant to test the hypothesis on the real network. However, since April 19 was a holiday weekend and the traffic load on the network was very light, we chose to adjust the metrics for a period of five and one half hours. The results of this test were as expected with one exception. I had made a mathematical error when calculating the paths to Denver from Seattle, so the lowest cost path between that pair did not traverse the RS960 path. There was a noticeable reduction of traffic through the following interfaces: 16 to 64, 72 to 48, and 48 to 72. Even 80 to 96 saw less traffic than when the metrics were configured as in phase two. Other observations were, that there appears to be an increase in traffic through interface 32 to 56. That might be attributed to the fact that the lowest link cost between Washington DC and Hartford was then via New York, not Greensboro; however, this may be offset by having two equal cost paths between Hartford and Greensboro. We have not yet completed our evaluation for phase four. The recommendation for phase one is that we leave the link metrics as they are currently; every T3 link is one. The conclusions that we draw for phase two from these experiments are that we can reduce the load on two of the hybrid boxes by diverting traffic to the third, lightly utilized hybrid. We recommend that prior to that phase that the link metrics be increased from one to three on two links: 8-24 and 16-64. As for phase three, significant gains can be made by diverting the majority of traffic to the RS960 path, but we recommend that we investigate further to see if we can eliminate the RS960-Hawthorne-RS960 path between Hartford and Denver. As we conclude our evaluation of phase four, we will publish these results also. - - - - - - - - - - - - - - - - - From long@nic.near.net Wed Apr 22 02:00:34 1992 Received: from nic.near.net by merit.edu (5.65/1123-1.0) id AA01032; Wed, 22 Apr 92 02:00:34 -0400 Message-Id: <9204220600.AA01032@merit.edu> To: mak Cc: regional-techs, nearnet-tc@nic.near.net Subject: Re: Phase III RS-960 Deployment Status Update In-Reply-To: Your message of Wed, 22 Apr 92 01:28:02 -0400. <9204220528.AA21384@home.merit.edu> Date: Wed, 22 Apr 92 02:00:28 -0400 From: Dan Long Mark, Thanks for the update. One thing that hasn't been clearly called out is the procedure for reporting on the progress of the rollout and the criteria that will be used for deciding whether all is well and the rollout should continue. When we last spoke, you said you were planning to make weekly status reports on how things were going. I think that's a very good idea. May I suggest that you send something out (Wednesdays?) that addresses the following points: - what changes were planned for the previous weekend - what changes actually were made on the previous weekend - what problems arose (if any) - what problems remain (if any) - what your plan is for the following weekend (the go/no-go question) This level of detail would enable us to help keep a watchful eye out for any operational problems and it would allow everyone some time to get feedback to you before the next set of upgrades. Possible? Thanks, Dan - - - - - - - - - - - - - - - - - From mak Wed Apr 22 10:46:35 1992 Received: from fox.merit.edu by merit.edu (5.65/1123-1.0) id AA09649; Wed, 22 Apr 92 10:46:35 -0400 Received: by fox.merit.edu (4.1/client-0.9) id AA17876; Wed, 22 Apr 92 10:46:47 EDT From: mak Message-Id: <9204221446.AA17876@fox.merit.edu> To: Dan Long Cc: regional-techs, nearnet-tc@nic.near.net Subject: Re: Phase III RS-960 Deployment Status Update In-Reply-To: Your message of "Wed, 22 Apr 92 02:00:28 EDT." <9204220600.AA01032@merit.edu> Date: Wed, 22 Apr 92 10:46:45 -0400 Dan, This is a good idea. I will send out such a summary today and each Wednesday (approx.) for the duration of the RS/960 deployment. Mark > From: Dan Long > To: mak@merit.edu > CC: regional-techs@merit.edu, nearnet-tc@nic.near.net > > > Mark, > > Thanks for the update. One thing that hasn't been clearly called out is > the procedure for reporting on the progress of the rollout and the criteria > that will be used for deciding whether all is well and the rollout should > continue. > > When we last spoke, you said you were planning to make weekly status > reports on how things were going. I think that's a very good idea. May I > suggest that you send something out (Wednesdays?) that addresses the > following points: > > - what changes were planned for the previous weekend > - what changes actually were made on the previous weekend > - what problems arose (if any) > - what problems remain (if any) > - what your plan is for the following weekend (the go/no-go question) > > This level of detail would enable us to help keep a watchful eye out for > any operational problems and it would allow everyone some time to get feedbac k > to you before the next set of upgrades. > > Possible? > > Thanks, > Dan - - - - - - - - - - - - - - - - - From skw Fri Apr 24 08:18:18 1992 Received: by merit.edu (5.65/1123-1.0) id AA07706; Fri, 24 Apr 92 08:18:28 -0400 From: "Steven K. Widmayer" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA07700; Fri, 24 Apr 92 08:18:18 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA12173; Fri, 24 Apr 92 08:18:17 EDT Date: Fri, 24 Apr 92 08:18:17 EDT Message-Id: <9204241218.AA12173@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 44 Network Name: AMPRNET Location: Bell Communications Research, Morris Research and Engineering Center, MRE 2P-357, 445 South Street, Morristown, NJ 07960-1910, USA Country Code: US 1:195 SDSC Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 129.41 Network Name: IBM-RSCH-NET1 Location: IBM Bethesda, 6705 Rockledge Drive, Bethesda, MD 20817 USA Country Code: US 1:701 Alternet Network 2:702 Alternet at Boston 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 133.8 Network Name: GUNMA-U Location: Gunma University, JAPAN Country Code: JP 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 133.60 Network Name: HIRODAINET Location: Hirosaki University, Information Processing Center, JAPAN Country Code: JP 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 133.71 Network Name: EHMNET Location: Ehime University, JAPAN Country Code: JP 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 133.144 Network Name: HITNET Location: Hitachi Ltd., JAPAN Country Code: JP 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 136.219 Network Name: LIVORNO-NET1 Location: DOD Dependents School - Mediteranean Region, APO AE 09614, ITALY Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 137.7 Network Name: AF-CONC-NET11 Location: Air Force Concentrator Network, Scott AFB, IL 62225-6346, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 138.29 Network Name: USCGA Location: Coast Guard Academy, 15 Mohegan Avenue, New London, CT 06320, USA Country Code: US 1:97 JvNCnet Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 148.163 Network Name: HCC Location: Hoechst Celanese Corporation, P.O. Box 32414, Charlotte, NC 28232, USA Country Code: US 1:97 JvNCnet Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 149.144 Network Name: LTUCNV Location: La Trobe University College of Northern Victoria, Computing Services Centre, P.O. Box 199, Bendigo, Victoria 3550, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 150.80 Network Name: AIC-NET1 Location: Advanced Intelligent Communication Systems, 663 Minami Yoshinari, Aoba-ku, Sendai 989-32, JAPAN Country Code: JP 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 150.150 Network Name: KARINET Location: Korea Aerospace Research Institute, P.O. Box 15, Daeduck Science Town, Daejun, 305-606, KOREA Country Code: KR 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 151.149 Network Name: SEARSNET Location: Sears Technology Services, Inc., 231 North Martingale Road, Schaumburg, IL 60173-2254, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 3:754 T1-T3 Network Interconnect (Houston, TX) 4:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 155.187 Network Name: ERIN Location: Environmental Resources Information Network, GPO Box 636, Canberra ACT 2601, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 155.205 Network Name: NTDME Location: Department of Mines and Energy, PO Box 2901, Darwin, NT 0800, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 157.82 Network Name: UTNET2 Location: University of Tokyo, JAPAN Country Code: JP 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 157.85 Network Name: OURIMBAH Location: University Computing Services, University of Newcastle, N S W 2308, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 157.128 Network Name: DCENET Location: Department of Conservation & Environment, 250 Victoria Parade, East Melbourne, Victoria 3002, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 158.40 Network Name: AUST-PMC Location: Department of Prime Minister and Cabinet, 3-5 National Circuit, BARTON ACT 2600, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 158.45 Network Name: EPAVIC Location: Environment Protection Authority, 3-5 National Circuit, 6/477 Collins Street, Melbourne VIC 3000, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 158.101 Network Name: SYNNET-NET Location: Synernetics, 85 Rangeway Road, North Billerica, MA 01862 USA Country Code: US 1:701 Alternet Network 2:702 Alternet at Boston 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 160.31 Network Name: SPTGCS Location: 542d CS/SCOK, Bld. 20604, Kirtland AFB, Albuquerque, NM 87117, USA Country Code: US 1:164 Milnet at FIX-West 2:184 Milnet at FIX-East Network IP: 192.65.182 Network Name: CORINET Location: Corinthian Industries Pty, Ltd., 383 West Botany Street, Rockdale, New South Wales 2216, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.104.81 Network Name: VRINET Location: Vector Research, Inc., 901 S. Highland St., Arlington, VA 22204, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.108.185 Network Name: NCCS-STI-GW Location: Naval Electronic Syst. Eng. Activity, NCCS Div. 2170, Code 2172/DDN, Bld. 185, St. Inigos, MD 29684-0010, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.111.51 Network Name: AMERITECH15 Location: Ameritech Services-Science & Technologies, The Meadows Corporation Center, 2820 West Golf Road, Rolling Meadows, IL 60008, USA Country Code: US 1:267 CICNET Regional Network (UIUC connection) 2:266 CICNET Regional Gateway 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.124.51 Network Name: NRHSnet Location: New Richmond Senior High School, 152 East 4th St., New Richmond, WI 54017, USA Country Code: US 1:291 Energy Science National Network 2:293 Energy Science Network National Network Network IP: 192.124.54 Network Name: WHSnet Location: Woodrow Wilson High School, Chesapeake and Nebraska Avenue, NW, Washington, DC 20016, USA Country Code: US 1:291 Energy Science National Network 2:293 Energy Science Network National Network Network IP: 192.124.117 Network Name: CSIRO-DHN-ADL Location: CSIRO Division of Human Nutrition, PO Box 10041, Gouger Street, Adelaide, South Australia 5000, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.131.13 Network Name: PEGASUS Location: Pegasus Networks Communications Pty Ltd, P.O. Box 424, Byron Bay 2481, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.131.30 Network Name: OTC-LINK Location: OTC Ltd., 255 Elizabeth Street, Sydney NSW 2001, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.131.251 Network Name: UNI-CEN-NET Location: University Centre, 210 Clarence St., SYDNEY. NSW. 2000, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.132.41 Network Name: CONCEPT Location: Concept Personnel Services Pty. Ltd., 97 Mogill Road, Taringa, Brisbane, Queensland 4066, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.132.253 Network Name: IDP Location: International Development Program, GPO Box 2006, Canberra ACT 2601, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.133.126 Network Name: TSTC Location: Texas State Technical College, Fentress Center, Building 25-27, 3801 Campus Drive, Waco, TX 76705, USA Country Code: US 1:114 Sesquinet 2:1700 Sesquinet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.136.139 Network Name: NATICK-ILCN Location: Information Management Directorate, Natick R.D.&E., Kansas St., Natick, MA 01760-5036, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.138.100 Network Name: DAPARM Location: Commonwealth Scientific and Industrial, CSIRO Division of Animal Production, Pastoral Research Laboratory, Armidale 2350 NSW, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.239 Network Name: TAMU-2 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.240 Network Name: TAMU-3 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.241 Network Name: TAMU-4 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.242 Network Name: TAMU-5 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.243 Network Name: TAMU-6 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.244 Network Name: TAMU-7 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.245 Network Name: TAMU-8 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.246 Network Name: TAMU-9 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.247 Network Name: TAMU-10 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.147.235 Network Name: UNISUPER Location: UniSuper Limited, Premises of Co-Cam Computer Group, 18 Trenerry Crescent, Abbotsford, Victoria 3067 AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.223 Network Name: ACUNET1 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.224 Network Name: ACUNET2 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.225 Network Name: ACUNET3 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.226 Network Name: ACUNET4 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.227 Network Name: ACUNET5 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.228 Network Name: ACUNET6 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.229 Network Name: ACUNET7 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.148.230 Network Name: ACUNET8 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.149.36 Network Name: CSIRODOGPER Location: Commonwealth Scientific & Industrial Research, 39 Fairway, Nedlands, WA 6009, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.150.129 Network Name: MHS Location: Message Handling Systems, 1st Floor, 2 King St, Newtown NSW 2042, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.150.144 Network Name: UNIFORUMNZ Location: Uniforum NZ, PO Box 585, Hamilton, NEW ZEALAND Country Code: NZ 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.152.55 Network Name: CCSU-NET Location: Corpus Cristi State University, 6300 Ocean Dr., Corpus Cristi, TX 78412, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.152.56 Network Name: CXLSU-NET Location: Laredo State University, One West End Washington St., Laredo, TX 78040-9960, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.152.57 Network Name: WTSU-NET Location: West Texas State University, Computing Center, WT Box 218, West Texas State University, Canyon, TX 79016, USA Country Code: US 1:114 Sesquinet 2:280 Sesquinet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.132 Network Name: WATERTOWN1 Location: Information Management Directorate, Natick R.D.&E., Kansas St., Natick, MA 01760-5036, USA Country Code: US 1:184 Milnet at FIX-East 2:164 Milnet at FIX-West Network IP: 192.153.158 Network Name: COOP-BOOKS Location: University Co-Operative Bookshop, 80 Bay Street, Broadway NSW 2007, AUSTRALIA Country Code: AU 1:372 NASA Science Network (West Coast) National Network 2:297 Nasa Science Network (SURANET connection) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.157.64 Network Name: ICMNET-1 Location: Sprint, Government Systems Division, 13221 Woodland Park Road, Herndon, VA 22071, USA Country Code: US 1:1240 USSPRINT - Palo Alto, CA Total T1 configured networks: 5220 T3 Network: ---------- Network IP: 44 Network Name: AMPRNET Location: Bell Communications Research, Morris Research and Engineering Center, MRE 2P-357, 445 South Street, Morristown, NJ 07960-1910, USA Country Code: US 1:195 SDSC Regional network Network IP: 128.157 Network Name: JSC-NET Location: JSC Central Net, NASA Ames Research Center, Moffett Field, San Jose, CA, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 129.41 Network Name: IBM-RSCH-NET1 Location: IBM Bethesda, 6705 Rockledge Drive, Bethesda, MD 20817 USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 133.8 Network Name: GUNMA-U Location: Gunma University, JAPAN Country Code: JP 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 133.60 Network Name: HIRODAINET Location: Hirosaki University, Information Processing Center, JAPAN Country Code: JP 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 133.71 Network Name: EHMNET Location: Ehime University, JAPAN Country Code: JP 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 133.144 Network Name: HITNET Location: Hitachi Ltd., JAPAN Country Code: JP 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 134.118 Network Name: JSCFMNET Location: NASA/Johnson Space Center, Mail Stop FD32, Houston, TX 77058, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 138.29 Network Name: USCGA Location: Coast Guard Academy, 15 Mohegan Avenue, New London, CT 06320, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 141.205 Network Name: JSC-NET Location: NASA/Johnson Space Center, Mail Code: PT32, Houston, TX 77058, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 146.154 Network Name: JESNETX Location: NASA/Johnson Space Center, Mail Code : PS2, Houston, TX 77058, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 148.163 Network Name: HCC Location: Hoechst Celanese Corporation, P.O. Box 32414, Charlotte, NC 28232, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 149.144 Network Name: LTUCNV Location: La Trobe University College of Northern Victoria, Computing Services Centre, P.O. Box 199, Bendigo, Victoria 3550, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 150.80 Network Name: AIC-NET1 Location: Advanced Intelligent Communication Systems, 663 Minami Yoshinari, Aoba-ku, Sendai 989-32, JAPAN Country Code: JP 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 150.150 Network Name: KARINET Location: Korea Aerospace Research Institute, P.O. Box 15, Daeduck Science Town, Daejun, 305-606, KOREA Country Code: KR 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 151.149 Network Name: SEARSNET Location: Sears Technology Services, Inc., 231 North Martingale Road, Schaumburg, IL 60173-2254, USA Country Code: US 1:1323 ANS Chicago - DNSS 27 Network IP: 155.187 Network Name: ERIN Location: Environmental Resources Information Network, GPO Box 636, Canberra ACT 2601, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 155.205 Network Name: NTDME Location: Department of Mines and Energy, PO Box 2901, Darwin, NT 0800, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 157.82 Network Name: UTNET2 Location: University of Tokyo, JAPAN Country Code: JP 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 157.85 Network Name: OURIMBAH Location: University Computing Services, University of Newcastle, N S W 2308, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 157.128 Network Name: DCENET Location: Department of Conservation & Environment, 250 Victoria Parade, East Melbourne, Victoria 3002, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 158.40 Network Name: AUST-PMC Location: Department of Prime Minister and Cabinet, 3-5 National Circuit, BARTON ACT 2600, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 158.45 Network Name: EPAVIC Location: Environment Protection Authority, 3-5 National Circuit, 6/477 Collins Street, Melbourne VIC 3000, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 158.101 Network Name: SYNNET-NET Location: Synernetics, 85 Rangeway Road, North Billerica, MA 01862 USA Country Code: US 42:702 Alternet Router 43:701 Alternet Router Network IP: 192.52.209 Network Name: JSCNETC12 Location: NASA/Johnson Space Center, Mail Code FD32, Houston, TX 77058, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 192.52.211 Network Name: JSCNETC14 Location: NASA/Johnson Space Center, Mail Code FD32, Houston, TX 77058, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 192.65.182 Network Name: CORINET Location: Corinthian Industries Pty, Ltd., 383 West Botany Street, Rockdale, New South Wales 2216, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.73.54 Network Name: WCU Location: West Chester University, F.H. Green Library Room 308, West Chester, PA 19383, USA Country Code: US 1:204 PSCNET Regional Network 2:1206 PSCNET Regional Network Network IP: 192.88.38 Network Name: JSCNET38 Location: NASA/Johnson Space Center, Mail Code: PT32, Houston, TX 77058, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 192.101.147 Network Name: NSI-TEMP-NET5 Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 192.111.51 Network Name: AMERITECH15 Location: Ameritech Services-Science & Technologies, The Meadows Corporation Center, 2820 West Golf Road, Rolling Meadows, IL 60008, USA Country Code: US 1:1225 CICNET at Argonne Labs 2:267 CICNET at UIUC 3:266 CICNET at MERIT Network IP: 192.124.117 Network Name: CSIRO-DHN-ADL Location: CSIRO Division of Human Nutrition, PO Box 10041, Gouger Street, Adelaide, South Australia 5000 AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.131.13 Network Name: PEGASUS Location: Pegasus Networks Communications Pty Ltd, P.O. Box 424, Byron Bay 2481, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.131.30 Network Name: OTC-LINK Location: OTC Ltd., 255 Elizabeth Street, Sydney NSW 2001, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.131.251 Network Name: UNI-CEN-NET Location: University Centre, 210 Clarence St., SYDNEY. NSW. 2000, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.132.41 Network Name: CONCEPT Location: Concept Personnel Services Pty. Ltd., 97 Mogill Road, Taringa, Brisbane, Queensland 4066, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.132.89 Network Name: NMHU-NET Location: New Mexico Highlands University, New Mexico Highlands University, Computer Center, Las Vegas, NM 87701, USA Country Code: US 1:771 NASA AS - ENSS 139, Houston, TX 2:372 Nasa Science Network -- Ames 3:297 Nasa Science Network (FIX-East) Network IP: 192.132.253 Network Name: IDP Location: International Development Program, GPO Box 2006, Canberra ACT 2601, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.133.126 Network Name: TSTC Location: Texas State Technical College, Fentress Center, Building 25-27, 3801 Campus Drive, Waco, TX 76705, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.138.100 Network Name: DAPARM Location: Commonwealth Scientific and Industrial, CSIRO Division of Animal Production, Pastoral Research Laboratory, Armidale 2350 NSW, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.138.239 Network Name: TAMU-2 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.240 Network Name: TAMU-3 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.241 Network Name: TAMU-4 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.242 Network Name: TAMU-5 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.243 Network Name: TAMU-6 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.244 Network Name: TAMU-7 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.245 Network Name: TAMU-8 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.246 Network Name: TAMU-9 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.138.247 Network Name: TAMU-10 Location: Computing Services Center, Texas A&M University, College Station, TX 77843-3142, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.147.235 Network Name: UNISUPER Location: UniSuper Limited, Premises of Co-Cam Computer Group, 18 Trenerry Crescent, Abbotsford, Victoria 3067, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.223 Network Name: ACUNET1 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.224 Network Name: ACUNET2 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.225 Network Name: ACUNET3 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.226 Network Name: ACUNET4 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.227 Network Name: ACUNET5 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.228 Network Name: ACUNET6 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.229 Network Name: ACUNET7 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.148.230 Network Name: ACUNET8 Location: Australian Catholic University, Christ Campus, Oakleigh VIC 3166, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.149.36 Network Name: CSIRODOGPER Location: Commonwealth Scientific & Industrial Research, 39 Fairway, Nedlands, WA 6009,AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.150.129 Network Name: MHS Location: Message Handling Systems, 1st Floor, 2 King St, Newtown NSW 2042, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.150.144 Network Name: UNIFORUMNZ Location: Uniforum NZ, PO Box 585, Hamilton, NEW ZEALAND Country Code: NZ 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Network IP: 192.152.55 Network Name: CCSU-NET Location: Corpus Cristi State University, 6300 Ocean Dr., Corpus Cristi, TX 78412, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.152.56 Network Name: CXLSU-NET Location: Laredo State University, One West End Washington St., Laredo, TX 78040-9960, USA Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.152.57 Network Name: WTSU-NET Location: West Texas State University, Computing Center, WT Box 218, West Texas State University, Canyon, TX 79016 Country Code: US 1:114 SESQUINET Regional Network 2:280 SESQUINET Regional Network Network IP: 192.153.158 Network Name: COOP-BOOKS Location: University Co-Operative Bookshop, 80 Bay Street, Broadway NSW 2007, AUSTRALIA Country Code: AU 1:372 Nasa Science Network -- Ames 2:297 Nasa Science Network (FIX-East) Total configured T3 networks: 3486 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* --Steve Widmayer / Riaz Taherzadeh-Yazdian / Michael O'Neill Merit/NSFNET - - - - - - - - - - - - - - - - - From nwg-owner Sat Apr 25 09:03:24 1992 Received: by merit.edu (5.65/1123-1.0) id AA18243; Sat, 25 Apr 92 09:03:27 -0400 Received: from CORNELLC.CIT.CORNELL.EDU by merit.edu (5.65/1123-1.0) id AA18239; Sat, 25 Apr 92 09:03:24 -0400 Received: from dns.cit.cornell.edu by CORNELLC.cit.cornell.edu (IBM VM SMTP V2R2) with TCP; Sat, 25 Apr 92 09:01:54 EDT Received: from icm1.icp.net by dns.cit.cornell.edu (4.1/2.0) id AA13359; Sat, 25 Apr 92 09:02:05 EDT Received: by icm1.icp.net (4.1/SMI-4.1) id AA14465; Sat, 25 Apr 92 09:01:02 EST Date: Sat, 25 Apr 92 09:01:02 EST From: rcollet@icp.net (Robert D. Collet) Message-Id: <9204251401.AA14465@icm1.icp.net> To: fepg-big@nri.reston.va.us, fepg@nri.reston.va.us, goldstein@note.nsf.gov, icm@nmc.cit.cornell.edu, iepg@aarnet.edu, nsr, nwg, oros@NMC.CIT.CORNELL.EDU, rcollet@icm1.icp.net, rcollet@sprint.com, wgc@fnc.gov Subject: Transition of ICM NOC from Cornell to Sprint In January of 1991 Sprint entered into a cooperative agreement with the National Science Foundation to provide International Connections Management (ICM) to NSFNET. The international network service is called ICMnet. As part of the Sprint Team Cornell University provides the ICMnet Network Operations Center (NOC). Sprint and Cornell University have mutually agreed to the transfer of NSF ICMnet NOC duties to the SprintLink Public Data Internet (PDI) NOC. Sprintlink, which provides "acceptable use" and "commercial" nationwide IP routing services, is now operational. The consolidation of ICMnet functions with SprintLink will streamline operations and eliminate duplication of effort. The precise cut-over schedule, points-of-contact list and other associated information will be distributed within two weeks. Cut- over of individual links is tentatively scheduled for mid May. I would like to thank Cornell University for their hard work and superior performance. Their dedication has yielded an international network with an enviable record for availability and stability. In particular, I would like to recognize Mark Oros for his focused efforts in implementing a well-managed, responsive NOC. If there are any questions concerning the transition please use the following. Bob Robert D. Collet Principal Investigator, NSFNET International Connections Manager Sprint Government Systems Division 13221 Woodland Park Road Herndon, VA 22071 USA Mail Stop: VAHRNA604 Tel: +1-703-904-2230 Fax: +1-703-904-2119 e-mail: rcollet@sprint.com rcollet@icm1.icp.net - - - - - - - - - - - - - - - - - From nwg-owner Sun Apr 26 15:12:07 1992 Received: by merit.edu (5.65/1123-1.0) id AA06522; Sat, 25 Apr 92 22:03:07 -0400 Received: from noc.sura.net by merit.edu (5.65/1123-1.0) id AA06511; Sat, 25 Apr 92 22:02:36 -0400 Received: by noc.sura.net for nsr@merit.edu id AA19304 (5.65+/(SURAnet $Revision: 1.27 $)); Sat, 25 Apr 92 22:01:29 -0400 Date: Sat, 25 Apr 92 22:01:29 -0400 From: Nicholas Vargish Message-Id: <9204260201.AA19304@noc.sura.net> To: hornlo@uw1301.millsaps.edu Cc: rcollet@icp.net, fepg-big@nri.reston.va.us, fepg@nri.reston.va.us, goldstein@note.nsf.gov, icm@nmc.cit.cornell.edu, iepg@aarnet.edu, nsr, nwg, oros@nmc.cit.cornell.edu, rcollet@icm1.icp.net, rcollet@sprint.com, wgc@fnc.gov, hornlo@uw1301.millsaps.edu In-Reply-To: hornlo@uw1301.millsaps.edu's message of Sat, 25 Apr 92 20:53:32 -0500 <9204260153.AA15255@uw1301.millsaps.edu> Subject: Transition of ICM NOC from Cornell to Sprint Haven't a clue what the problem is, but I've been getting it pretty regularly too. Wish it would _stop_! -- Nick Vargish SURAnet Operations vargish@sura.net - - - - - - - - - - - - - - - - - From nwg-owner Sun Apr 26 15:15:19 1992 Received: by merit.edu (5.65/1123-1.0) id AA06455; Sat, 25 Apr 92 22:02:06 -0400 Received: from relay2.UU.NET by merit.edu (5.65/1123-1.0) id AA06437; Sat, 25 Apr 92 22:01:45 -0400 Received: from cfmartin.UU.NET by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA07565; Sat, 25 Apr 92 22:01:09 -0400 Received: by cfmartin.UU.NET (5.61/UUNET-mail-leaf) id AA18773; Sat, 25 Apr 92 22:00:56 -0400 Date: Sat, 25 Apr 92 22:00:56 -0400 From: ebersman@uunet.uu.net (Paul Ebersman) Message-Id: <9204260200.AA18773@cfmartin.UU.NET> To: hornlo@uw1301.millsaps.edu Cc: wgc@fnc.gov, rcollet@sprint.com, rcollet@icm1.icp.net, oros@nmc.cit.cornell.edu, nwg, nsr, iepg@aarnet.edu, icm@nmc.cit.cornell.edu, goldstein@note.nsf.gov, fepg@nri.reston.va.us, fepg-big@nri.reston.va.us, rcollet@icp.net (Robert D. Collet) Subject: Re: Transition of ICM NOC from Cornell to Sprint References: <9204251401.AA14465@icm1.icp.net> <9204260153.AA15255@uw1301.millsaps.edu> Organization: UUNET Technologies, Inc. hornlo> I keep getting this message -- is there a mail loop somewhere? Yes. This was copy 19 for me... -- Paul A. Ebersman @ UUNET Technologies, Inc. uunet!ebersman or ebersman@uunet.uu.net The difference between theory and practice in practice is greater than the difference between theory and practice in theory. - - - - - - - - - - - - - - - - - From nwg-owner Sun Apr 26 15:24:29 1992 Received: by merit.edu (5.65/1123-1.0) id AA06236; Sat, 25 Apr 92 21:56:12 -0400 Received: from uw1301.millsaps.edu by merit.edu (5.65/1123-1.0) id AA06232; Sat, 25 Apr 92 21:56:09 -0400 Received: by uw1301.millsaps.edu (5.57/Ultrix3.0-C) id AA15255; Sat, 25 Apr 92 20:53:33 -0500 Posted-Date: Sat, 25 Apr 92 20:53:32 -0500 Message-Id: <9204260153.AA15255@uw1301.millsaps.edu> To: rcollet@icp.net (Robert D. Collet) Cc: fepg-big@nri.reston.va.us, fepg@nri.reston.va.us, goldstein@note.nsf.gov, icm@nmc.cit.cornell.edu, iepg@aarnet.edu, nsr, nwg, oros@nmc.cit.cornell.edu, rcollet@icm1.icp.net, rcollet@sprint.com, wgc@fnc.gov, hornlo@uw1301.millsaps.edu Subject: Re: Transition of ICM NOC from Cornell to Sprint In-Reply-To: Your message of "Sat, 25 Apr 92 09:01:02 EST." <9204251401.AA14465@icm1.icp.net> Date: Sat, 25 Apr 92 20:53:32 -0500 From: hornlo@uw1301.millsaps.edu X-Mts: smtp I keep getting this message -- is there a mail loop somewhere? - - - - - - - - - - - - - - - - - From nwg-owner Sun Apr 26 15:32:13 1992 Received: by merit.edu (5.65/1123-1.0) id AA19025; Sun, 26 Apr 92 07:26:00 -0400 Received: from ncc.ripe.net by merit.edu (5.65/1123-1.0) id AA19021; Sun, 26 Apr 92 07:25:50 -0400 Received: from reif.ripe.net by ncc.ripe.net with SMTP id AA01839 (5.65a/NCC-CWI-2.8); Sun, 26 Apr 1992 13:24:27 +0200 Message-Id: <9204261124.AA01839@ncc.ripe.net> To: hornlo@uw1301.millsaps.edu, postmaster, action Cc: rcollet@icp.net (Robert D. Collet), fepg-big@nri.reston.va.us, fepg@nri.reston.va.us, goldstein@note.nsf.gov, icm@nmc.cit.cornell.edu, iepg@aarnet.edu, nsr, nwg, oros@nmc.cit.cornell.edu, rcollet@icm1.icp.net, rcollet@sprint.com, wgc@fnc.gov Subject: Re: Transition of ICM NOC from Cornell to Sprint In-Reply-To: Your message of Sat, 25 Apr 92 20:53:32 CDT. <9204260153.AA15255@uw1301.millsaps.edu> From: Daniel Karrenberg X-Organization: RIPE Network Coordination Centre X-Phone: +31 20 592 5065 Date: Sun, 26 Apr 92 13:24:15 +0200 Sender: Daniel.Karrenberg@ripe.net > hornlo@uw1301.millsaps.edu writes: > I keep getting this message -- is there a mail loop somewhere? From the Received lines I infer that it is being re-sent from merit.edu about once an hour. Could someone Please stop this: Received: from mcsun.EU.net by ncc.ripe.net with SMTP id AA01694 (5.65a/NCC-CWI-2.8); Sun, 26 Apr 1992 06:31:54 +0200 Received: from relay2.UU.NET by mcsun.EU.net with SMTP id AA16982 (5.65b/CWI-2.160); Sun, 26 Apr 1992 06:31:47 +0200 Received: from ftp.UU.NET by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA19398; Sun, 26 Apr 92 00:31:55 -0400 Received: from rodan.UU.NET by ftp.UU.NET with SMTP (5.61/UUNET-guest-mail-drop) id AA23473; Sun, 26 Apr 92 00:31:57 -0400 Received: from relay2.UU.NET by rodan.UU.NET with SMTP (5.61/UUNET-mail-drop) id AA04410; Sun, 26 Apr 92 00:31:26 -0400 Received: from merit.edu by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA19384; Sun, 26 Apr 92 00:31:35 -0400 Return-Path: Received: by merit.edu (5.65/1123-1.0) id AA18248; Sat, 25 Apr 92 09:04:23 -0400 Received: from CORNELLC.CIT.CORNELL.EDU by merit.edu (5.65/1123-1.0) id AA18239; Sat, 25 Apr 92 09:03:24 -0400 Received: from dns.cit.cornell.edu by CORNELLC.cit.cornell.edu (IBM VM SMTP V2R2) with TCP; Sat, 25 Apr 92 09:01:54 EDT Received: from icm1.icp.net by dns.cit.cornell.edu (4.1/2.0) id AA13359; Sat, 25 Apr 92 09:02:05 EDT Received: by icm1.icp.net (4.1/SMI-4.1) id AA14465; Sat, 25 Apr 92 09:01:02 EST Date: Sat, 25 Apr 92 09:01:02 EST From: rcollet@icp.net (Robert D. Collet) Message-Id: <9204251401.AA14465@icm1.icp.net> To: fepg-big@nri.reston.va.us, fepg@nri.reston.va.us, goldstein@note.nsf.gov, icm@nmc.cit.cornell.edu, iepg@aarnet.edu, nsr@merit.edu, nwg@merit.edu, oros@NMC.CIT.CORNELL.EDU, rcollet@icm1.icp.net, rcollet@sprint.com, wgc@fnc.gov Subject: Transition of ICM NOC from Cornell to Sprint - - - - - - - - - - - - - - - - - From nwg-owner Mon Apr 27 10:12:28 1992 Received: by merit.edu (5.65/1123-1.0) id AA29993; Mon, 27 Apr 92 10:12:44 -0400 Received: from ncar.ucar.edu by merit.edu (5.65/1123-1.0) id AA29979; Mon, 27 Apr 92 10:12:28 -0400 Received: from niwot.scd.ucar.edu by ncar.ucar.EDU (5.65/ NCAR Central Post Office 04/10/90) id AA11466; Mon, 27 Apr 92 08:11:39 MDT Date: Mon, 27 Apr 92 08:11:30 MDT From: morris@niwot.scd.ucar.EDU (Don Morris) Message-Id: <9204271411.AA09549@niwot.scd.ucar.EDU> Received: by niwot.scd.ucar.EDU (5.65/ NCAR Mail Server 04/10/90) id AA09549; Mon, 27 Apr 92 08:11:30 MDT To: hornlo@uw1301.millsaps.edu, rcollet@icp.net Subject: Re: Transition of ICM NOC from Cornell to Sprint Cc: fepg-big@nri.reston.va.us, fepg@nri.reston.va.us, goldstein@note.nsf.gov, icm@nmc.cit.cornell.edu, iepg@aarnet.edu, nsr, nwg, oros@nmc.cit.cornell.edu, rcollet@icm1.icp.net, rcollet@sprint.com, wgc@fnc.gov I keep getting this message -- is there a mail loop somewhere? Yeh .... maybe they should have just left things alone like they were at Cornell.... Oh well....sigh....guess it just takes a while for the commercial people to get the hang of it. - - - - - - - - - - - - - - - - - From cert-advisory-request@cert.sei.cmu.edu Mon Apr 27 15:46:48 1992 Received: from tictac.cert.sei.cmu.edu by merit.edu (5.65/1123-1.0) id AA12209; Mon, 27 Apr 92 15:46:48 -0400 Received: by tictac.cert.sei.cmu.edu (5.65/2.5) id AA29100; Mon, 27 Apr 92 15:35:21 -0400 Message-Id: <9204271935.AA29100@tictac.cert.sei.cmu.edu> From: CERT Advisory Date: Mon, 27 Apr 92 15:34:25 EDT To: cert-advisory@cert.sei.cmu.edu Subject: CERT Tools - AIX Anonymous FTP Vulnerability Organization: Computer Emergency Response Team : 412-268-7090 =========================================================================== CA-92:09 CERT Advisory April 27, 1992 AIX Anonymous FTP Vulnerability --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a vulnerability in the anonymous FTP configuration in all versions of AIX. IBM is aware of this problem and a fix is available as apar number "ix23944". This patch is available for all AIX releases from "GOLD". IBM customers may call IBM Support (800-237-5511) and ask that the fix be shipped to them. Patches may be obtained outside the U.S. by contacting your local IBM representative. The fix will appear in the upcoming 2009 update and the next release of AIX. --------------------------------------------------------------------------- I. Description Previous versions of the anonymous FTP installation script, /usr/lpp/tcpip/samples/anon.ftp, incorrectly configured various files and directories. II. Impact Remote users can execute unauthorized commands and gain access to the system if anonymous FTP has been installed. III. Solution A. Obtain the fix from IBM Support. The fix contains three files: a "readme" file (README.a23944), the fix installation script (install.a23944), and an archive containing the updated files (PATCH.a23944.Z). B. Install the fix following the instructions in the README file. --------------------------------------------------------------------------- The CERT/CC would like to thank Charles McGuire of the Computer Science Department, the University of Montana for bringing this security vulnerability to our attention and IBM for their response to the problem. --------------------------------------------------------------------------- If you believe that your system has been compromised, contact CERT/CC or your representative in FIRST (Forum of Incident Response and Security Teams). Internet E-mail: cert@cert.sei.cmu.edu Telephone: 412-268-7090 (24-hour hotline) CERT/CC personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. Computer Emergency Response Team/Coordination Center (CERT/CC) Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Past advisories, information about FIRST representatives, and other information related to computer security are available for anonymous ftp from cert.sei.cmu.edu (192.88.209.5). Please note: cert.sei.cmu.edu is soon to become cert.org. - - - - - - - - - - - - - - - - - From bsb Tue Apr 28 11:42:35 1992 Received: by merit.edu (5.65/1123-1.0) id AA07615; Tue, 28 Apr 92 11:42:40 -0400 From: "Belinda Sue Blair" Received: from home.merit.edu by merit.edu (5.65/1123-1.0) id AA07610; Tue, 28 Apr 92 11:42:35 -0400 Received: by home.merit.edu (4.1/client-0.9) id AA27186; Tue, 28 Apr 92 11:42:37 EDT Date: Tue, 28 Apr 92 11:42:37 EDT Message-Id: <9204281542.AA27186@home.merit.edu> To: nwg Subject: Additions to the NSFNET policy-based routing database The following networks have been added to the NSFNET policy-based routing database. T1 Network: ---------- Network IP: 141.57 Network Name: DFN-WIN57 Location: Technische Hochschule Leipzig, Karl-Liebknecht-Str. 132, D-O-7030 Leipzig, GERMANY Country Code: DE 1:293 Energy Science Network National Network 2:291 Energy Science National Network Network IP: 157.91 Network Name: IHETSDATANET Location: Indiana Higher Education Telecommunication System, 957 West Michigan Street, Indianapolis, IN 46202-5184, USA Country Code: US 1:267 CICNET Regional Network (UIUC connection) 2:266 CICNET Regional Gateway 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 160.39 Network Name: CIESIN-CRDC Location: CIESIN, 2250 Pierce Rd., University Center, MI 48710, USA Country Code: US 1:233 Merit Regional Network 2:177 Merit Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.12.81 Network Name: IRONMPI Location: Max Planck Institut fuer Eisenforschung, Max Planckstrasse 1, D-4000 Duesseldorf 1, GERMANY Country Code: DE 1:293 Energy Science Network National Network 2:291 Energy Science National Network Network IP: 192.86.2 Network Name: GLC-MI Location: Imagination and Information, Inc., 617 Spartan Drive, Rochester Hills, MI 48309, USA Country Code: US 1:174 NYSERNET Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.92.1 Network Name: MOBDIG Location: Mobile Digital Corp, 980 Atlantic Ave, Suite 103, Alameda, CA 94501, USA Country Code: US 1:200 BARRNET Regional Network 2:201 BARRNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.124.25 Network Name: MPIB-TUE Location: MPI/Biologie, Corrensstr. 38, D-W-7400 Tuebingen, GERMANY Country Code: DE 1:293 Energy Science Network National Network 2:291 Energy Science National Network Network IP: 192.124.26 Network Name: MPIK-TUE Location: MPI/Biologie, Corrensstr. 38, D-W-7400 Tuebingen, GERMANY Country Code: DE 1:293 Energy Science Network National Network 2:291 Energy Science National Network Network IP: 192.124.27 Network Name: MPIE-TUE Location: MPI/Biologie, Corrensstr. 38, D-W-7400 Tuebingen, GERMANY Country Code: DE 1:293 Energy Science Network National Network 2:291 Energy Science National Network Network IP: 192.124.28 Network Name: MPIM-TUE Location: MPI/Biologie, Corrensstr. 38, D-W-7400 Tuebingen, GERMANY Country Code: DE 1:293 Energy Science Network National Network 2:291 Energy Science National Network Network IP: 192.133.100 Network Name: ALBQREPS Location: Albuquerque Public Schools, APS Career Enrichment Center, 807 Mountain Rd. N.E., Albuquerque, NM 88102, USA Country Code: US 1:209 WestNet Regional network (East) 2:210 Westnet Regional Network (West) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.138.131 Network Name: CLIC Location: Cooperative Libraries in Consortium, 1457 Grand Ave., Suite N, St. Paul, MN 55103, USA Country Code: US 1:267 CICNET Regional Network (UIUC connection) 2:266 CICNET Regional Gateway 18:754 T1-T3 Network Interconnect (Houston, TX) 19:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.152 Network Name: MVHS Location: Monta Vista High School, 21840 McClellan Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNET Regional Network 2:201 BARRNet Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.153.190 Network Name: ETSU2 Location: East Texas State University, Data Processing Services, Commerce, TX 75429, USA Country Code: US 1:280 Sesquinet Regional Network 2:114 Sesquinet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Total T1 configured networks: 5233 T3 Network: ---------- Network IP: 157.91 Network Name: IHETSDATANET Location: Indiana Higher Education Telecommunication System, 957 West Michigan Street, Indianapolis, IN 46202-5184, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 3:1225 CICNET at Argonne Labs Network IP: 160.39 Network Name: CIESIN-CRDC Location: CIESIN, 2250 Pierce Rd., University Center, MI 48710, USA Country Code: US 1:237 MERIT network 2:233 MERIT network Network IP: 192.86.2 Network Name: NET-GLC-MI Location: Imagination and Information, Inc., 617 Spartan Drive, Rochester Hills, MI 48309, USA Country Code: US 1:174 NYSERNET Regional Network / PSI Network IP: 192.92.1 Network Name: MOBDIG Location: Mobile Digital Corp, 980 Atlantic Ave, Suite 103, Alameda, CA 94501, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.133.100 Network Name: ALBQREPS Location: Albuquerque Public Schools, APS Career Enrichment Center, 807 Mountain Rd. N.E., Albuquerque, NM 88102, USA Country Code: US 1:209 Westnet Regional (Colorado Attachment) - ENSS 141 2:210 Westnet Regional (Utah Attachment) - ENSS 142 Network IP: 192.138.131 Network Name: CLIC Location: Cooperative Libraries in Consortium, 1457 Grand Ave., Suite N, St. Paul, MN 55103, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 192.153.152 Network Name: MVHS Location: Monta Vista High School, 21840 McClellan Road, Cupertino, CA 95014, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.153.190 Network Name: ETSU2 Location: East Texas State University, Data Processing Services, Commerce, TX 75429, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Total configured T3 networks: 3492 ***************************************************************** The configuration reports, map information sheets, and configuration files which reflect these changes are available for anonymous ftp on nis.nsf.net as usual. nsfnet/announced.networks - configuration reports latest report for: - NSFNET T1 has the file extension .now - NSFNET T3 has the file extension 3.now nsfnet/backbone.configuration - configuration files for the routing software for each NSS latest report for: - NSFNET T1 has the file format config.nss# - NSFNET T3 has the file extension .t3p Please send all requests for configuration changes to nsfnet-admin@merit.edu using the NSFNET configuration forms. The forms are available on-line. from the nis.nsf.net machine. Use ftp and the anonymous login to get on the machine. Do a "cd nsfnet/announced.networks" and get the files TEMPLATE.NET, TEMPLATE.GATE, and TEMPLATE.AS. ******************************* -B. Sue Blair Merit / NSFNET - - - - - - - - - - - - - - - - - From donnab@CERF.NET Tue Apr 28 19:02:54 1992 Received: from nic.cerf.net by merit.edu (5.65/1123-1.0) id AA23462; Tue, 28 Apr 92 19:02:54 -0400 Received: by nic.cerf.net (4.1/CERFnet-1.0) id AA02237; Tue, 28 Apr 92 16:03:00 PDT Date: Tue, 28 Apr 92 16:03:00 PDT From: Donna Bigley Message-Id: <9204282303.AA02237@nic.cerf.net> To: broidoj@Sds.Sdsc.Edu, help@CERF.NET, nsfnet-reports, ops@cerf.net Subject: CERFnet Weekly Report for the week of Monday, April 20th, 1992. ############################################################################### This is the CERFnet weekly activity report for the period of Monday, April 20th through Sunday, April 26th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 26-april-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab@cerf.net or help@cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 922 SITE: MARK V SITES AFFECTED: MARK V TIME STARTED: MON. 4-20-92 13:29 TIME ENDED: MON. 4-20-92 15:57 TIME ELAPSED: 2 hour 28 min. REASON: Link Failure TICKET #: 928 SITE: UCLA-SDSC T1 SITES AFFECTED: UCLA-SDSC T1 TIME STARTED: TUE. 4-21-92 01:03 TIME ENDED: TUE. 4-21-92 03:57 TIME ELAPSED: 2 hours 54 min. REASON: Vendor Scheduled Maintenance TICKET #: 925 SITE: HUGHES SITES AFFECTED: HUGHES TIME STARTED: TUE. 4-21-92 12:19 TIME ENDED: TUE. 4-21-92 13:56 TIME ELAPSED: 1 hour 37 min. REASON: Site Activity TICKET #: 931 SITE: HUGHES SITES AFFECTED: HUGHES TIME STARTED: THU. 4-23-92 12:04 TIME ENDED: THU. 4-23-92 12:09 TIME ELAPSED: 5 min. REASON: Site Scheduled Maintenance TICKET #: 934 SITE: QUALCOMM SITES AFFECTED: QUALCOMM TIME STARTED: THU. 4-23-92 14:48 TIME ENDED: THU. 4-23-92 14:50 TIME ELAPSED: 2 min. REASON: Equipment Trouble TICKET #: 929 SITE: SDSU SITES AFFECTED: SDSU TIME STARTED: FRI. 4-24-92 01:19 TIME ENDED: FRI. 4-24-92 03:43 TIME ELAPSED: 2 hours 24 min. REASON: Site Scheduled Maintenance TICKET #: 932 SITE: CSUCO/SWRL SITES AFFECTED: CSUCO/SWRL TIME STARTED: FRI. 4-24-92 06:01 TIME ENDED: FRI. 4-24-92 06:09 TIME ELAPSED: 8 min. REASON: Site Scheduled Maintenance TICKET #: 933 SITE: GA-SDSC SITES AFFECTED: GA-SDSC TIME STARTED: FRI. 4-24-92 06:27 TIME ENDED: FRI. 4-24-92 09:07 TIME ELAPSED: 2 hours 40 min. REASON: Power Outage ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PDT) UCI/CALTECH 45.000 mbps No capacities available this week. (New Line) SDSC/CALTECH 1.544 mbps 08.9% 13:00 SDSC/UCI 1.544 mbps 07.2% 14:00 SDSC/UCLA 1.544 mbps 08.9% 14:00 SDSC/UCOP 1.544 mbps 03.6% 10:00 UCI/UCLA 1.544 mbps 00.8% 14:00 SDSC/UCR 512 kbps 02.1% 20:00 UCLA/UCSB 512 kbps 07.6% 15:00 SDSC/AGI 1.544 mbps 00.1% 17:00 SDSC/BIOSYM 1.544 mbps 00.1% 12:00 SDSC/GA 1.544 mbps 00.3% 11:00 SDSC/GD 1.544 mbps 01.0% 07:00 SDSC/SAIC 1.544 mbps 00.9% 14:00 SDSC/SCAQMD 1.544 mbps 00.1% 17:00 SDSC/SDSU 1.544 mbps 01.9% 14:00 UCI/CSU CO(SWRL) 1.544 mbps 02.8% 15:00 UCOP/APPLE 1.544 mbps 01.1% 18:00 UCOP/CISCO 1.544 mbps 00.2% 19:00 UCR/LLUMC 1.544 mbps 00.1% 18:00 CALTECH/CADAM 56 kbps 00.4% 09:00 CALTECH/CITY OF HOPE 56 kbps 00.4% 13:00 CALTECH/CLAREMONT 56 kbps 21.1% 17:00 CALTECH/DISNEY 56 kbps 04.7% 14:00 CALTECH/OXY 56 kbps 07.6% 23:00 SDSC/AJS 56 kbps 01.4% 14:00 SDSC/KOREA 56 kbps 03.6% 18:00 SDSC/QUALCOMM 56 kbps 08.0% 11:00 SDSC/SCIH 56 kbps 06.1% 15:00 SDSC/USD 56 kbps 07.2% 11:00 SDSC/USIU 56 kbps 00.6% 14:00 SDSC/XEROX 56 kbps 00.4% 14:00 UCI/CMD 56 kbps 06.1% 20:00 UCI/EMULEX 56 kbps 01.8% 15:00 UCI/FULLERTON 56 kbps 01.4% 13:00 UCI/HUGHES 56 kbps 11.2% 14:00 UCI/MTI 56 kbps 02.9% 21:00 UCI/SPARTA 56 kbps 08.0% 01:00 UCI/UNOCAL 56 kbps 05.7% 14:00 UCLA/ISX 56 kbps 01.4% 17:00 UCLA/PEPPERDINE 56 kbps 00.8% 10:00 UCLA/QUOTRON 56 kbps 08.0% 17:00 UCLA/SMC 56 kbps 01.5% 18:00 UCOP/FARALLON 56 kbps 04.4% 18:00 UCOP/INTEL 56 kbps No capacities available this week. (Available next week.) UCOP/LSIL 56 kbps 07.0% 22:00 UCOP/NETLABS 56 kbps 14.7% 19:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on April 27, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 29 days 05 hours 41 minutes SDSC LongBoard [134.24.99.254] Up: 18 days 14 hours 56 minutes SDSC Drzog [132.249.16.13] Up: 38 days 07 hours 00 minutes SDSC Hang10 [132.249.16.15] Up: 17 days 16 hours 26 minutes UCI [128.200.1.101] Up: 108 days 16 hours 07 minutes UCLA [128.97.130.10] Up: 21 days 06 hours 28 minutes UCOP [134.24.52.112] Up: 33 days 16 hours 38 minutes UCR [134.24.108.105] Up: 36 days 06 hours 48 minutes CERF 1544 AGI [134.24.202.110] Up: 73 days 13 hours 54 minutes APPLE [134.24.70.200] Up: 182 days 06 hours 15 minutes BIOSYM [134.24.57.200] Up: 23 days 05 hours 27 minutes CISCO Systems [134.24.54.200] Up: 47 days 04 hours 20 minutes CSUCO/SWRL [130.150.102.200] Up: 02 days 18 hours 08 minutes [Site Scheduled Maintenance - See Ticket #932] GA [134.24.221.200] Up: 02 days 15 hours 08 minutes [Power Outage - See Ticket #933] GD [134.24.60.200] Up: 56 days 13 hours 31 minutes LLUMC [134.24.208.200] Up: 159 days 12 hours 22 minutes SAIC [134.24.53.208] Up: 113 days 08 hours 34 minutes SCAQMD [134.24.234.200] Up: 129 days 14 hours 27 minutes SDSU [192.77.100.101] Up: 02 days 20 hours 33 minutes [Site Scheduled Maintenance - See Ticket #929] UCSB [134.24.107.107] Up: 159 days 07 hours 38 minutes CERF 56 AJS [134.24.225.101] Up: 100 days 14 hours 17 minutes CADAM [134.24.229.200] Up: 82 days 13 hours 01 minutes CICESE [134.24.227.200] Up: 11 days 10 hours 58 minutes CITY_OF_HOPE [134.24.233.200] Up: 03 days 10 hours 43 minutes [Unknown] CLAREMONT [134.24.206.109] Up: 30 days 17 hours 39 minutes CMD [134.24.218.200] Up: 90 days 13 hours 14 minutes DATAPRODUCTS [134.24.211.104] Up: 26 days 09 hours 33 minutes DISNEY [134.24.207.211] Up: 16 days 10 hours 00 minutes EMULEX [134.24.209.212] Up: 15 days 12 hours 12 minutes FARALLON [134.24.56.200] Up: 28 days 02 hours 24 minutes FULLERTON [134.24.214.217] Up: 42 days 16 hours 57 minutes GTE [134.24.212.200] Up: 07 days 14 hours 44 minutes HUGHES [134.24.204.200] Up: 05 days 10 hours 48 minutes [Site Activity - See Ticket #925] INTEL [134.24.73.200] Up: 29 days 11 hours 34 minutes LSIL [134.24.72.200] Up: 78 days 13 hours 08 minutes MTI [134.24.216.100] Up: 01 days 09 hours 34 minutes [Unknown] NETLABS [134.24.71.200] Up: 32 days 08 hours 51 minutes OXY [134.24.205.108] Up: 20 days 16 hours 27 minutes PEPPERDINE [134.24.203.218] Up: 16 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 00 days 00 hours 12 minutes [Unscheduled Outage] QUOTRON [134.24.230.202] Up: 22 days 12 hours 00 minutes SANTA MONICA [134.24.210.219] Up: 44 days 12 hours 40 minutes SEASPACE [134.24.80.200] Up: 18 days 11 hours 26 minutes SCI-HOR [134.24.109.205] Up: 31 days 04 hours 27 minutes SERI/KOREA [134.24.223.200] Up: 20 days 00 hours 40 minutes SPARTA [134.24.215.200] Up: 27 days 10 hours 57 minutes UNOCAL [134.24.217.200] Up: 52 days 01 hours 57 minutes USD [134.24.201.106] Up: 31 days 06 hours 12 minutes USIU [134.24.222.215] Up: 295 days 17 hours 07 minutes XEROX [134.24.51.207] Up: 179 days 23 hours 22 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 05 days 12 hours 50 minutes [Equipment Trouble] DNC-UCI [134.24.2.2] Up: 110 days 03 hours 24 minutes DNC-UCLA [134.24.3.2] Up: 21 days 06 hours 25 minutes DNC-CALTECH [134.24.4.2] Up: 29 days 05 hours 42 minutes DNC-UCOP [134.24.5.2] Up: 16 days 17 hours 01 minutes SDSC-NETBLAZER [192.102.249.25] Up: 04 days 12 hours 08 minutes [Unknown] UCLA-NETBLAZER [134.24.93.2] Up: 20 days 16 hours 01 minutes - - - - - - - - - - - - - - - - - From nwg-owner Thu Apr 30 10:52:25 1992 Received: by merit.edu (5.65/1123-1.0) id AA25563; Thu, 30 Apr 92 10:52:40 -0400 Received: from boole.ece.cmu.edu by merit.edu (5.65/1123-1.0) id AA25554; Thu, 30 Apr 92 10:52:25 -0400 Received: by boole.ece.cmu.edu (5.54-ECE2/5.17) id AA25086; Thu, 30 Apr 92 10:52:12 EDT Date: Thursday, 30 April 1992 10:52:09 EDT From: Gene.Hastings@boole.ece.cmu.edu To: njm, nwg Cc: techcomm@farnet.org Subject: 3/24/92 Alternet map on ftp.uu.net Message-Id: <1992.4.30.14.49.41.Gene.Hastings@boole> as /uunet-info/AlterNet.ps.Z. Check it out. South Africa via Portland, OR. Wow. G - - - - - - - - - - - - - - - - - From mak Thu Apr 30 23:21:57 1992 Received: from fox.merit.edu by merit.edu (5.65/1123-1.0) id AA20472; Thu, 30 Apr 92 23:21:57 -0400 Received: by fox.merit.edu (4.1/client-0.9) id AA10371; Thu, 30 Apr 92 23:22:09 EDT Date: Thu, 30 Apr 92 23:22:09 EDT From: mak Message-Id: <9205010322.AA10371@fox.merit.edu> To: regional-techs Subject: RS/960 upgrade on the T3 backbone: status report Phase-III RS960 Deployment Status Report - Week 1 ================================================= Jordan Becker, ANS Mark Knopper, Merit Summary ======= - RS/960 Hardware Deployment Early last Saturday morning, April 25, the first step of the Phase-III RS960 DS3 upgrade to the T3 Backbone was completed. The following T3 backbone nodes are currently running with new T3 hardware and software in a stable configuration: Seattle POP: CNSS88, CNSS89, CNSS91 Denver POP: CNSS96, CNSS97, CNSS99 Regionals: ENSS141 (Boulder), ENSS142 (Salt Lake), ENSS143 (U. Washington) This Friday night 5/1 and Saturday morning 5/2, the second step will occur, with the following nodes being upgraded: Los Angeles POP (barring rioting, etc.): CNSS16, CNSS17, CNSS19 San Francisco POP: CNSS8, CNSS9, CNSS11 Regionals: ENSS128 (Palo Alto), ENSS144 (NASA Ames/FIX-West), ENSS135 (San Diego) - Kernel Build and Routing Software Deployment Early this morning (April 30), all of the network nodes were upgraded with Build 2.78.22 and a new version of rcp_routed. Several nodes (the Step 1 nodes and also the Ann Arbor ENSS) have been running in this configuration since April 27. This software build includes drivers for the RS/960 cards, and several bug fixes. The fixes include reliability improvements to the FDDI software, notably a soft reset for a hung card; and some additional improvements to the T960 ethernet and T1 card support to fix a problem where the card could hang under a heavy load. The rcp_routed change includes a fix to a problem that was observed during RS/960 testing. The problem involved some aberrant behavior of rcp_routed when a misconfigured regional peer router would advertise a route via BGP to an ENSS whose next hop was the ENSS itself. The old rcp_routed could go into a loop sending multiple redirect packets out on to the subnet. The new rcp_routed will close the BGP session if it receives an announcement of such a route. The new rcp_routed software also has support for externally administered inter-AS metrics, an auto-restart capability, and bug fixes for BGP overruns with peer routers. This deployment caused a few problems. One is that this new feature of rcp_routed pointed out a misconfigured peer router at Rice University in Houston. This caused the BGP connection to open and close rapidly which caused further problems on the peer router. Eventually the peer was reconfigured to remove the bad route, which fixed the problem. Another problem was on the Argonne ENSS. This node crashed in such a way that it was not reachable and there was difficulty contacting the site to reboot the machine. Once the reboot was done the ENSS came back up running properly. We are looking into the cause of this crash, as this is the first time this has happened in all of our testing and deployment. The third problem was at the CoNCert ENSS, and this node crashed in such a way that the unix file system was completely lost, and this requires a complete rebuild of the system. This problem has happened in two cases previously, and seems to be related to an AIX problem rather than anything in the new software build. It is an insidious problem since it completely wipes out any trace of what may have caused it. We continue to look into this. In our view, none of these problems are severe enough to call off the deployment of the RS/960 hardware upgrade on the west coast Saturday morning. These problems aren't related to the new hardware or software support for the new cards, but seem to be problems in other parts of the new software build or routing daemon. The following section details our experiences of the first week's deployment. We believe we have an understanding of the problems that occurred and have increased the number of spare cards in the kits that the teams will take out to the sites. Summary of Week 1 (beginning 4/25) RS/960 Deployment ==================================================== Since the deployment, nodes CNSS88 and CNSS96 have been running with mixed technology (i.e. 3xRS960 T3 interfaces, 1xHawthorne T3 interface). Production traffic on the affected ENSS nodes was cutover to the T1 backbone at 2:00 AM EST on 4/25. The Denver POP nodes were returned to full service after approximately 10.5 hours and Seattle after about 13 hrs of work. The new software had been deployed on the affected nodes during the prior week. The physical upgrade consisted of mechanical changes to the RS6000 machines including (1) replacement of the RS6000 I/O planar, (2) replacement of the Hawthorne T3 adapters with RS960 adapters, (3) upgrading the DSU hardware and associated cabling, (4) a modification of the cooling capabilities of the RS6000, (5) updating and standardizing on new labels and (6) local software configuration changes accommodating the use of new hardware. The nodes were then tested and returned to production service. Although the resulting configuration is very stable and gratifying to the team working on the upgrade, the process was not quite as smooth as had been expected. There were 33 RS960 T3 interface adapters, T3 DSUs, and 9 I/O planars installed. Out of these, 5 RS960 adapters and 2 I/O planars had to be replaced to achieve stability. The failing new components were air-shipped back to the staging lab for a complete failure analysis. and a summary of the results are described below. All of the problems involving replaced components have been identified or explained. The post-manufacturing burn-in and staging process consists of a stress test involving card-to-card traffic testing, DSU testing, and power cycling prior to shipping. Lab burn-in and staging procedures have been adjusted based upon our experiences with the first deployment step. The installation procedures will be fine tuned to improve our efficiency and reduce the installation time required. It is therefore our intention to continue with the step 2 deployment plan in the San Francisco and Los Angeles backbone nodes (and adjacent ENSS nodes) on Friday evening 5/1. Installation Problems Encountered ================================= The replacement of the RS6000 I/O planers had to be performed twice on nodes CNSS88 and CNSS91 after the nodes did not come up properly the first time. The original set of planers were returned to the lab for analysis. It was determined that the underside of the planars were damaged during the physical installation process. The procedure for installing these planars in the RS6000 model 930 rack mounted system has been modified to prevent this type of damage from occuring. Adapter re-seating and reconfiguration was required on the asynchronous communications adapter on CNSS89. The dual planar change and troubleshooting work adversely affected the hard disk on CNSS88 and the disk image had to be reloaded from tape. An apparent dysfunctional DSU HSSI card connected to CNSS97 was replaced and was returned for lab failure analysis. The analysis revealed that a DSU microprocessor was not properly seated. T3 Technologies will re-inspect the DSUs for proper seating of all DSU components. The DSU at ENSS142 (Salt Lake City) needed internal work. The analysis revealed a bent pin on the connector between the HSSI card and the DSU backplane. T3 Technologies Inc. (DSU manufacturer) identified a mechanical deficiency in the connector that can cause certain pins to loosen and bend during insertion of the card. T3 Technologies will add a procedure to inspect these connectors prior to shipment for any deficiencies. An RS960 T3 card in CNSS89 did not have the correct electrical isolation spacers installed, and this caused a temporary short circuit. The card was returned to the lab and it was determined that a last-minute change was made to the card to swap an i596 serializer chip and that the spacer was erroneously left off. A visual inspection procedure for spacers and standoffs will be added to the manufacturing and staging inspection process. The RS960 T3 card in CNSS97 came up in a NONAP mode, however the card continued to respond to DSU queries. The card was replaced. During the failure analysis, the card passed all stress tests. This card was swapped prior to a planar change and the NONAP mode has been attributed to the planar problem. When reliable connectivity could not be achieved between CNSS97<->ENSS141, another RS960 T3 card in CNSS97 was replaced. The lab failure analysis revealed that the 20Mhz oscillator crystal on the card was broken due to a mechanical shock. This shock could have occured during shipping or handling. CNSS91 rebooted after the upgrade and exhibited an unstable configuration. Both the I/O planar and the RS960 T3 card were changed before stable operation was achieved. The RS960 card was later found to have a cold solder joint between the RAM module and adapter. The solder joint would allow the card to work when cold, but would fail intermittently when running hot. A simple adapter thermal cycling procedure will be investigated to determine if this problem can be avoided in the future. CNSS88 was the last node to come up. The I/O planar and memory card had to be re-seated, and an RS960 T3 card replacement was necessary. The RS960 card was found to have a solder splash that was overlapping two adjacent pins. A general corrective action for this problem involves adding a procedure involving high magnification visual microchannel interface inspection for shorts. Conclusions =========== Although the Step 1 installation was complicated by several component problems, the entire deployment team (IBM, Merit, ANS, MCI) has a high comfort level with the results of the failure analysis, the stability of the resulting installation, and overall deployment process. We are very encouraged that we have completed this first step and acheived a very stable configuration within the time, human resources, spares and support that was provisioned as part of the deployment plan. The software bring-up and test scripts worked exactly as planned. The teamwork between the 50+ individuals involved at Merit, IBM, MCI and ANS was excellent. The basic installation process is sound, although some minor changes will be implemented in the future installation steps. These will include the RS960 adapter installation, DSU trouble-shooting procedure and the I/O planar change process. Also the number of spares provisioned in a deployment kit will be increased as a pre-caution for future installations. There has been one software problem identified with the new technology on the test network since the end of system testing on 4/17. This involves a microcode bug where a portion of the RS960 on-card memory will not report a parity error to the system if that portion of the memory suffers a failure. All RS960 on-card memory is tested prior to shipment and a microcode fix to this problem will be delivered by IBM for testing within the next week. Only a single RS960 adapter has demonstrated an on-card memory parity error during all test network testing. Next Steps ========== Step 2 of the deployment is currently scheduled to commence at 23:00 local time on 5/1. Step 2 will involve the following nodes/locations: May 1/2 San Francisco, Los Angeles core nodes T3 ENSS Nodes: Palo Alto E128, San Diego E135, Other ENSS Nodes: E144, E159, E156, E170 also affected Second core node visit: Seattle - - - - - - - - - - - - - - - - -