- NANOG - lists.nanog.org

Additions to the NSFNET policy-based routing database
by Belinda Sue Blair 16 Apr '92

16 Apr '92

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

1 0

SNMP 'snmppoll' data cruncher program version 1.1
by aggarwal＠nisc.jvnc.net 14 Apr '92

14 Apr '92

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(a)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(a)jvnc.net Vikas Aggarwal JvNCnet vikas(a)jvnc.net

1 0

Additions to the NSFNET policy-based routing database
by Belinda Sue Blair 14 Apr '92

14 Apr '92

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(a)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

1 0

CERFnet Weekly Report for the week of Monday, April 6, 1992.
by Donna Bigley 13 Apr '92

13 Apr '92

############################################################################### 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(a)cerf.net or help(a)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]

1 0

ANSNET/NSFNET Phase-III T3 Network Upgrade Plan
by mak 11 Apr '92

11 Apr '92

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(a)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.

1 0

CERT Advisory - "IRIX" lp Vulnerability
by CERT Advisory 10 Apr '92

10 Apr '92

=========================================================================== 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(a)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.

1 0

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 10 Apr '92

10 Apr '92

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(a)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

1 0

Re: Additions to the NSFNET policy-based routing database
by Jessica Yu 09 Apr '92

09 Apr '92

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(a)aotearoa.sura.net> To: "Belinda Sue Blair" <bsb(a)merit.edu> Cc: nwg(a)merit.edu, noc(a)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(a)home.merit.edu> Date: Tue, 07 Apr 92 14:50:45 -0400 From: Erik Sherk <sherk(a)sura.net> > 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(a)sura.net

3 2

Re: template
by Steven K. Widmayer 09 Apr '92

09 Apr '92

>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

1 0

Re: Additions to the NSFNET policy-based routing database
by Jessica Yu 09 Apr '92

09 Apr '92

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

3 2