- NANOG - lists.nanog.org

CERT Advisory - AIX crontab Vulnerability
by CERT Advisory 26 May '92

26 May '92

=========================================================================== CA-92:10 CERT Advisory May 26, 1992 AIX crontab Vulnerability --------------------------------------------------------------------------- The Computer Emergency Response Team/Coordination Center (CERT/CC) has received information concerning a vulnerability in crontab(1) in version 3.2 of IBM's AIX operating system. IBM is aware of this problem and a fix is available as apar number "ix26997" for AIX version 3.2. The version information for the patched /usr/bin/crontab is shown in the following what(1) output: % what /usr/bin/crontab 04 1.23 com/cmd/cntl/cron/crontab.c, cmdcntl, bos320, 9218320f 4/8/92 11:50:42 07 1.8 com/cmd/cntl/cron/permit.c, bos, bos320 4/25/91 17:16:59 11 1.15 com/cmd/cntl/cron/cronsub.c, bos, bos320 8/18/91 20:42:32 06 1.9 com/cmd/cntl/cron/funcs.c, bos, bos320 6/8/91 21:22:40 If your crontab contains older modules than the above output indicates, we suggest that you install the fix. --------------------------------------------------------------------------- I. Description The distributed version of /usr/bin/crontab contains a security vulnerability. II. Impact Local users can gain unauthorized root access to the system. III. Solution The CERT/CC suggests that sites install the fix that IBM has made available. As an interim step, we suggests that sites prevent all non-root users from running /usr/bin/crontab by removing (or renaming) the /var/adm/cron/cron.allow and /var/adm/cron/cron.deny files. - Obtain the fix from IBM Support. 1. To order from IBM call 1-800-237-5511 and ask that the fix be shipped. Patches may be obtained outside the U.S. by contacting your local IBM representative. 2. If you are on the Internet, use anonymous ftp to obtain the fix from software.watson.ibm.com (129.34.139.5). Patch Filename Checksum AIX 3.2 pub/aix3/cronta.tar.Z 02324 154 The patch must be retrieved using binary mode. - Install the fix following the instructions in the README file. --------------------------------------------------------------------------- The CERT/CC would like to thank Fuat Baran of Advanced Network & Services, Inc. for bringing this security vulnerability to our attention and IBM 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.org 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.org (192.88.209.5).

1 0

Re: Additions, etc. to the NSFNET policy-based routing database
by Belinda Sue Blair 26 May '92

26 May '92

Regional techs and others, Greetings. Since nsfnet-admin received an incredibly low number of Network Announcement Change Requests over the Memorial Day weekend in this fine nation of ours, I am unilaterally, in the fine Haig tradition, postponing the configuration window one day to Tuesday night/Wednesday morning. NACRs will be accepted for this run until 2pm-ish Tuesday and the installation window will be from 05:00-08:00 Wednesday morning. If you need any configurations installed before then, please message trouble(a)merit.edu and state that you need an emergency config. The NOC can then page me and I will deal with it from there. Apologies for any inconvenience. Thanks, -B. Sue Blair Merit Network Operations

1 0

Handy.node.list available on nis.nsf.net
by bsb 22 May '92

22 May '92

Regional techs, Lastly, there is a handy.node.list available on nis.nsf.net. I removed it from the end of the template.gate and template.as form and put it in its own file, so it will be easier to generate and keep up-to-date with the rest of the exciting, important, and informative NIS reports. A copy is appended below for your convenience. Thanks, -B. Sue Blair Merit / NSFNET --------------- nis.nsf.net: nsfnet/announced.networks/handy.node.list T3 Backbone: T1 Backbone: D/ENSS# City NSS# City ----- ------------- ---- ------------- 11 ANS-San Francisco, CA 5 NSF-Pittsburgh, PA 19 ANS-Los Angeles, CA 6 NSF-San Diego, CA 27 ANS-Chicago, IL 7 NSF-Boulder, CO 35 ANS-New York, NY 8 NSF-Princeton, NJ 43 ANS-Cleveland, OH 9 NSF-College Park, MD 51 ANS-Hartford, CT 10 NSF-Ithaca, NY 59 ANS-Washington D.C. 11 NSF-Houston, TX 67 ANS-Houston, TX 12 NSF-Champaign, IL 75 ANS-Greensboro, NC 13 NSF-Palo Alto, CA 83 ANS-St. Louis, MO 14 NSF-Seattle, WA 91 ANS-Seattle, WA 15 NSF-Salt Lake City, UT 99 ANS-Denver, CO 16 NSF-Lincoln, NE 128 NSF-Palo Alto, CA 17 NSF-Ann Arbor, MI 129 NSF-Urbana-Champaign, IL 18 NSF-Atlanta, GA 130 NSF-Chicago, IL 19 NSF-Boston, MA 131 NSF-Ann Arbor, MI 132 NSF-Pittsburgh, PA 133 NSF-Ithaca, NY 134 NSF-Boston, MA 135 NSF-San Diego, CA 136 NSF-College Park, MD 137 NSF-Princeton, NJ 138 NSF-Atlanta, GA 139 NSF-Houston, TX 140 NSF-Lincoln, NE 141 NSF-Boulder, CO 142 NSF-Salt Lake City, UT 143 NSF-Seattle, WA 144 NSF-Palo Alto, CA #2 - Ames 145 NSF-College Park #2 - Fix-East 150 NSF-Raleigh, NC 151 ANS-Blacksburg, VA 152 ANS-West Lafayette, IN 155 ANS-White Plains, NY 158 ANS-Southfield, MI 160 ANS-Elmsford, NY 163 ANS-New York, NY 164 ANS-Yorktown Heights, NY 165 ANS-Lexington, KY 168 ANS-Columbus, OH 174 ANS-Austin, TX 200 NSF/ANS-ShowNSS-varied locations

1 0

New template.as available
by bsb 22 May '92

22 May '92

Regional-techs, Again, greetings. The dreaded template.as has been updated as well. The latest version is 2.2 dated May 22, 1992. A copy is appended for your convenience. Thanks, -B. Sue Blair Merit / NSFNET --------------- [nis.nsf.net:nsfnet/announced.networks/template.as] Version 2.2 22 May 1992 NSFNET Configuration Request Template for the NSFNET policy-based routing data base ---- Autonomous System Contact Information ---- This template is to register new ASes with nsfnet-admin. It sets up the preliminaries and designates individuals who are responsible for the adminstration of an Autonomous System. This information is needed to facilitate smooth operations between the NSFNET and the Autonomous System. This information should be submitted to nsfnet-admin(a)merit.edu. ***************************************************************************** ---- Autonomous System Contact Information---- 1) Is this new information or a change in previous information (new/change): 2) If this is a new AS, please indicate routing restrictions. Please choose type a, b, or c list: If type b, please list ASes that you would like to ignore: type a list) Hear about the backbone only: Example: announcetoAS xxx norestrict ASlist 690 (T3) announcetoAS xxx norestrict ASlist 145 (T1) type b list) Hear about everything except certain ASes: Example: announcetoAS xxx norestrict ASlist 22 26 38 60 68 73 81 86 93 97 101 114 145 164 174 177 178 179 181 etc. type c list) Other. Please explain: 2) Autonomous System number/name: 3) ENSS/NSS number associated with AS: 4) 2 Administrative contacts: --Please provide the names, postal addresses, electronic addresses, and telephone numbers for items 4 - 6. These contacts do not have to be six individuals; some individuals may play dual roles within your organization. 5) At least 2 Technical contacts: 6) At least 2 designated Routing contacts: --The designated Routing contacts are the individuals that the AS designates to represent the AS with the NSFNET staff. 7) NOC phone number and email address: NOC hours: --If you have a NOC and you would like your NOC to be the first point of contact in the event of a problem, please provide the above information. 8) After hours contact procedures: --If you would like to be contacted outside of normal business hours, or outside of your normal NOC hours, please provide any pertinent contact names and phone numbers. 9) Special trouble-shooting instructions for the Merit/NSFNET NOC: 10) Additional comments (optional): --------------------------------------------------------------------- Configurations installations are performed Tuesday and Friday morning from 05:00-08:00 Eastern time, so some instability on the backbones may be experienced during this window. Requests for the Tuesday morning config window should be submitted to nsfnet-admin by noon Monday. Requests for the Friday morning config window should be submitted by noon Thursday. To get a current listing of nodes and node numbers on the T1 and T3 backbone, you can anonymous ftp to nis.nsf.net, cd to /nsfnet/ announced.networks and get the file handy.node.list.

1 0

New Template.gate form available on nis.nsf.net
by bsb 22 May '92

22 May '92

Regional-techs, Greetings. There is a spiffy new template.gate form appended below for your convenience. It is available on nis.nsf.net via anonymous ftp in the nsfnet/announced.networks directory. It is dated May 22, 1992 (version 3.2) and erases some of the ambiguity of the previous version while maintaining the old esoteric lameness. Enjoy! -B. Sue Blair Merit / NSFNET --------------- [nis.nsf.net:nsfnet/announced.networks/template.gate] Version 3.2 22 May 1992 NSFNET Configuration Request Template for the NSFNET policy-based routing data base ---- EGP/BGP Peer Change Request ---- This template is to request announcement of EGP/BGP peers to the NSFNET backbone. Configuration requests may only be submitted by the designated routing contacts for the Autonomous Systems of the NSFNET. Configuration requests should be submitted to nsfnet-admin(a)merit.edu. Please read the explanation at the bottom of this form if you are unfamiliar with its contents. --------------------------------- CUT HERE ----------------------------------- ---- EGP/BGP Peer Change Request ---- Router Internet Address: Router Internet Name: Router AS Number: Is this a new AS (y/n): (If so, please fill out a template.as form as well) ENSS and/or NSS number colocated with router: Router physical location (if different than ENSS/NSS): Should BGP1, BGP2, or EGP be used: For BGP1 only: linktype H or D: EGP metric out (T1 default=128 / T3 default=127): BGP metric out (T1 default=128 / T3 default=127): Router Type/Manufacturer: Software Version: Addition, Deletion or Change?(A/D/C): Additional Comments (optional): --------------------------------- CUT HERE ----------------------------------- ***************************************************************************** EXAMPLE: Suppose a New Cisco HyBridge with the Internet address 35.1.1.125 and the domain name NSFNET-GW.MERIT.EDU should be co-located with NSS 17 (Ann Arbor), running BGP as using the Autonomous System number 233. It should not receive routing information from the DDN/MILNET (AS 164 and AS 184) and its own routed should not be advertised into AS 177. Their EGP/BGP peer change request would be filled in as follows: ---- EGP/BGP Peer Change Request ---- Router Internet Address: 35.1.1.125 Router Internet Name: NSFNET-GW.MERIT.EDU Router AS Number: 233 Is this a new AS (y/n): n ENSS and/or NSS number colocated with router: NSS17 Router physical location (if different than ENSS/NSS): Should BGP1, BGP2, or EGP be used: BGP1 For BGP1 only: linktype D or H: H EGP metric out (T1 default=128 / T3 default=127): BGP metric out (T1 default=128 / T3 default=127): Router Type/Manufacturer: Cisco HyBridge Software version: 8.1 Addition, Deletion or Change?(A/D/C): A Additional Comments (optional): ----------------------------------------------------------- Configurations installations are performed Tuesday and Friday morning from 05:00-08:00 Eastern time, so some instability on the backbones may be experienced during this window. Requests for the Tuesday morning config window should be submitted to nsfnet-admin by noon Monday. Requests for the Friday morning config window should be submitted by noon Thursday. To get a current listing of nodes and node numbers on the T1 and T3 backbone, you can anonymous ftp to nis.nsf.net, cd to /nsfnet/ announced.networks and get the file handy.node.list.

1 0

Additions to the NSFNET policy-based routing database
by Riaz Taherzadeh-Yazdian 22 May '92

22 May '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 146.149 Network Name: JPMORGAN Location: JP Morgan, 60 Wall Street, 8th Floor, New York, New York 10260, 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: 146.164 Network Name: REDE-UFRJ Location: Federal University of Rio de Janeiro, Nucleo de Computacao Eletronica, Caixa Postal 2324, CEP 20.001, Rio de Janeiro, RJ, BRAZIL Country Code: BR 1:1740 CERFnet 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 157.99 Network Name: FNET-PASTEUR Location: Institut Pasteur, 25 rue du Docteur Roux, 75724 PARIS Cedex 15, FRANCE Country Code: FR 1:1800 ICM-FIX-E 2:1238 ICM-NORDUNET Network IP: 161.33 Network Name: IMAGEN Location: QMS Inc., 1 Magnum Pass Road, Mobile, AL, USA Country Code: US 1:701 Alternet 2:702 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.82.231 Network Name: CHORUS-USA Location: Chorus, 15262 NW Greenbrier Parkway, Beaverton, OR 97006-5764, USA Country Code: US 1:701 Alternet 2:702 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.84.123 Network Name: AFSOC Location: Air Force Special Operations Command, AFSOC/SCX Bld. 1, Hurlburt Field, FL 32544-5000, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.109.59 Network Name: YAN-MS Location: Zentralamt fuer Mobilfunk, Referat Z2, Roddestrasse 12, D-W-4400, Muenster, GERMANY Country Code: DE 1:701 Alternet 2:1800 ICM-FIX-E 3:1238 ICM-NORDUNET Network IP: 192.121.34 Network Name: SE-NFR Location: NFR, Bos 6711, S-113 85 Stockholm, Sweden Country Code: SE 1:701 Alternet Network IP: 192.124.130 Network Name: RASTEROPS Location: RasterOps, 2500 Walsh Avenue, Santa Clara, CA 95050, USA Country Code: US 1:701 Alternet 2:702 Alternet 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.133.32 Network Name: N-POLAR Location: Norwegian Polar Research Institute, Boks 158, N-1330 Oslo Lufthavn, NORWAY Country Code: NO 1:701 Alternet Network IP: 192.138.220 Network Name: NEB-NET Location: New England Biolabs, Inc., 32 Tozer Road, Beverly, MA 01915, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.147.12 Network Name: ADELPHI2 Location: Adelphi University, South Avenue, Garden City, Long Island, NY 11010, USA Country Code: US 1:97 JvNCnet Regional Network 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.148.222 Network Name: KENTLAW Location: Chicago-Kent College of Law at IIT, 565 West Adams, Chicago, IL 60661, USA Country Code: US 1:267 CICNET at UIUC 2:266 CICNET at MERIT 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) 11:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.153.150 Network Name: FTBENNINGEMH Location: UASISC-Ft. Benning, Director, USAISC-Fort Benning, ASQNB-ZBO-I, Ft. Benning, GA 31905-6204, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.153.151 Network Name: STEWART-NET5 Location: TAFZP-IMM (TCC), Bldg. 9, Ft. Stewart, GA 31314-5000, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.156.133 Network Name: IBM-IRAD-DMZ Location: IBM Federal Sector Corporation, MC 5600, 3700 Bay Area Blvd, Houston TX 77058, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.160.73 Network Name: CABLELABS Location: Cable Television Laboratories, Inc., 1050 Walnut Street, Suite 500, Boulder, CO 80302, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) 2:210 Westnet Regional Network (Utah Attachment) 12:754 T1-T3 Network Interconnect (Houston, TX) 13:751 T1-T3 Network Interconnect (San Diego, CA) Network IP: 192.169.16 Network Name: CORNERSTONE1 Location: Cornerstone Research, 1000 El Camino Real, ste. 250, 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: 192.169.17 Network Name: CORNERSTONE2 Location: Cornerstone Research, 1000 El Camino Real, ste. 250, 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: 192.169.18 Network Name: CORNERSTONE3 Location: Cornerstone Research, 1000 El Camino Real, ste. 250, 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) Total configured T1 networks: 5484 T3 Network: ---------- Network IP: 139.82 Network Name: PUC-RIO Location: Pontificia Universidade Catolica do Rio de Janeiro, Rua Marques de Sao Vicente 225, Gavea, CEP 22453 - Rio De Janeiro - RJ, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 146.134 Network Name: LNCC Location: Laboratorio Nacional de Computacao Cientifica, R. Lauro Muller 455, 22.290-Rio de Janeiro, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 146.149 Network Name: JPMORGAN Location: JP Morgan, 60 Wall Street, 8th Floor, New York, New York 10260, USA Country Code: US 1:1324 ANS New York City - DNSS 35 Network IP: 146.164 Network Name: REDE-UFRJ Location: Federal University of Rio de Janeiro, Nucleo de Computacao Eletronica, Caixa Postal 2324, CEP 20.001, Rio de Janeiro, RJ, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 147.65 Network Name: IMPA Location: Instituto de Matematica Pura e Aplicada, Estrada Dona Castorina, 110 Horto, CEP 22460 Rio de Janeiro RJ, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 152.84 Network Name: LAFEX-B Location: Laboratorio Fisica Experimental Altas Energias/LAFEX (NET-LAFEX-B), R. Dr.Xavier Sigaud 150 5oAND., CEP 22290 Rio Janeiro, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 152.92 Network Name: IPRJ Location: Instituto Politecnico do Rio de Janeiro, C.P. 97282, Nova Friburgo RJ 28630, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 157.86 Network Name: FIOCRUZ Location: Fundacao Oswaldo Cruz (Oswaldo Cruz Foundation), Rio de Janeiro, RJ, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 161.33 Network Name: IMAGEN Location: QMS Inc., 1 Magnum Pass Road, Mobile, AL, USA Country Code: US 42:702 Alternet 43:701 Alternet Network IP: 192.82.231 Network Name: CHORUS-USA Location: Chorus, 15262 NW Greenbrier Parkway, Beaverton, OR 97006-5764, USA Country Code: US 42:702 Alternet 43:701 Alternet Network IP: 192.124.130 Network Name: RASTEROPS Location: RasterOps, 2500 Walsh Avenue, Santa Clara, CA 95050, USA Country Code: US 42:702 Alternet 43:701 Alternet Network IP: 192.132.35 Network Name: OBSN Location: CNPz Observatorio Nacional, Rua General Jose Cristino, 77 - Rio de Janeiro, CEP 20921 - BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 192.138.220 Network Name: NEB-NET Location: New England Biolabs, Inc., 32 Tozer Road, Beverly, MA 01915, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.147.12 Network Name: ADELPHI2 Location: Adelphi University, South Avenue, Garden City, Long Island, NY 11010, USA Country Code: US 1:97 ENSS 137 - Princeton Network IP: 192.148.222 Network Name: KENTLAW Location: Chicago-Kent College of Law at IIT, 565 West Adams, Chicago, IL 60661, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 192.153.88 Network Name: REDE-IBASE Location: Instituto Brasileiro de Analises Sociais, Rua Vicente de Souza, 29, Rio de Janeiro 22251, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 192.156.133 Network Name: IBM-IRAD-DMZ Location: IBM Federal Sector Corporation, MC 5600, 3700 Bay Area Blvd, Houston TX 77058, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 192.160.73 Network Name: CABLELABS Location: Cable Television Laboratories, Inc., 1050 Walnut Street, Suite 500, Boulder, CO 80302, USA Country Code: US 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 Network IP: 192.169.16 Network Name: CORNERSTONE1 Location: Cornerstone Research, 1000 El Camino Real, ste. 250, Menlo Park, CA, 94025, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.169.17 Network Name: CORNERSTONE2 Location: Cornerstone Research, 1000 El Camino Real, ste. 250, Menlo Park, CA, 94025, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.169.18 Network Name: CORNERSTONE3 Location: Cornerstone Research, 1000 El Camino Real, ste. 250, Menlo Park, CA, 94025, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Total configured T3 networks: 3666 ***************************************************************** 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 / NSFNET Riaz Taherzadeh-Yazdian Merit / NSFNET

1 0

RS/960 Upgrade for T3 Backbone - 5th Week of 5
by mak 21 May '92

21 May '92

Phase-III T3 Network Deployment - Step 4 Status Report ====================================================== Jordan Becker, ANS Mark Knopper, Merit Step 4 of the phase-III network was successfully completed last Saturday 5/16. All T3 nodes were back on-line within the scheduled maintainance window with the exception of the Houston CNSS67 T1 concentrator due to software configuration problem, and ENSS129 (Champaign) due to a T3 circuit problem. The upgrade of all other nodes were completed by 10:00 EST on 5/16. The following T3 backbone nodes are currently running with new T3 RS960 hardware and software in a stable configuration: Seattle POP: CNSS88, CNSS89, CNSS91 Denver POP: CNSS96, CNSS97, CNSS99 San Fran. POP: CNSS8, CNSS9, CNSS11 L.A. POP: CNSS16, CNSS17, CNSS19 Chicago POP: CNSS24, CNSS25, CNSS27 Cleveland POP: CNSS40, CNSS41, CNSS43 New York City POP: CNSS32, CNSS33, CNSS35 Hartford POP: CNSS48, CNSS49, CNSS51 St. Louis POP: CNSS80, CNSS81, CNSS83 Houston POP: CNSS64, CNSS65, CNSS67 Regionals: ENSS141 (Boulder), ENSS142 (Salt Lake), ENSS143 (U. Washington) ENSS128 (Palo Alto), ENSS144 (FIX-W), ENSS135 (San Diego) ENSS130 (Argonne), ENSS131 (Ann Arbor), ENSS132 (Pittsburgh), ENSS133 (Ithaca), ENSS134 (Boston) ENSS137 (Princeton), ENSS129 (Champaign), ENSS140 (Lincoln) ENSS139 (Rice) The CNSS32, CNSS48, CNSS64 nodes are now running with mixed technology (e.g. 3xRS960 T3 interfaces, 1xHawthorne T3 interface). Step 4 Deployment Difficulties ============================== The RS960 week 4 deployment was successful with two exceptions. The first problem involved the link between ENSS129 (Champaign) and CNSS81 (St. Louis POP). The second problem was the T1 concentrator in Houston (C67). This affected ENSS174 (IBM Austin) and ENSS173 (ITESM). On ENSS129, a jumper was initially found to be missing from the HSSI board and the jumper was added. ENSS129 was then successfully brought up online at 6:20 EST. Later in the morning, the ENSS129<->CNSS81 link began to experience packet loss. The DSUs were reporting coding violations and bipolar violations on the E129<->C81 link. The problem turned out to be a bad DS3 radio circuit between ENSS129->CNSS81 and MCI swapped the radio channel to clear the problem. At the Houston POP, CNSS64 and CNSS65 were upgraded and came up without problems. ENSS139 (Rice U.) also came up without any problems. However CNSS67 (the T1 concentrator) had complex problems. CNSS67 was taken down around 00:00 and the mechanical modifications were completed and bootup began at 2:15 EST. The machine rebooted and we started troubleshooting. All RS960 cards and the planar board were replaced in various combinations. After considerable analysis of the ODM configuration database, we suspected some ODM problems and we chose to re-install the system software from a tape built from another machine. The machine came right up on the first try at 14:00 EST with the same original hardware installed (including the original new RS960 card). This was clearly a system software corruption problem and there are no suspected hardware failures resulting from this. At the St. Louis POP, CNSS80, CNSS81, and CNSS83 were all upgraded and came up without any problems, 3 hours ahead of schedule at 4:45 EST. At the Denver POP, a loose serial port connector delayed the upgrade start time by a few minutes. We could not access the DSU through the out-of-band modem. An ODM adapter configuration problem was also fixed where cards were coming up up in the wrong slots. However these problems were solved and the Denver maintainence was completed well within the scheduled window. Routing was enabled and traffic flow started through the southern route (through Houston POP) by 9:35 EST even though the Houston T1 concentrator was still down so that the RS960 hybrid link upgrade at CNSS24 in the Chicago POP and the scheduled CNSS25 RS960 card replacement could begin on schedule. When CNSS24 would not come up smoothly with the new RS960 card, it was replaced without attempting to troubleshoot the system or the card. The replaced RS960 card will be returned to IBM for failure analysis. The RS960 card in CNSS25 was replaced as scheduled due to DMA under-runs which we observed last week. This installation went as planned and the machine came up 10:50 EST. New T3 internal link metrics have been installed to support load balancing of traffic across the 3 different hybrid technology links that now exist (e.g. CNSS64<->CNSS72, CNSS48<->CNSS72, CNSS32<->CNSS56). Step 5 Deployment Scheduled for 5/22 ==================================== Based upon the successful completion of step 4 of the deployment, step 5 is currently scheduled to commence at 23:00 local time on 5/22. Step 5 is the final phase-III upgrade step and will complete the deployment. This will involve the following nodes/locations: Greensboro POP: CNSS72, CNSS73, CNSS75 Washington D.C. POP: CNSS56, CNSS57, CNSS58, CNSS59 2nd Site Visit: CNSS32 (New York POP), CNSS64 (Houston POP) CNSS48 (Hartford POP) Regionals: ENSS138 (Georgia Tech.), ENSS136 (College Park) ENSS145 (FIX-E) Other Nodes Affected: ENSS150 (Concert), ENSS151, ENSS153, ENSS166 Following the step 5 deployment, all T3 internal link metrics will be re-adjusted to their normal metrics since no hybrid technology links will exist.

1 0

This mornings configurations on the T1 backbone
by Kraig J. Owen 19 May '92

19 May '92

Hello, The configuration changes which were to have taken place this morning on the T1 backbone, did not take affect. The configuration files were generated from the database, but were not installed on the backbone nodes. The changes will be installed tomorrow morning, 05/20/92, between 03:00 and 04:00 EDT. Thank You, Kraig Owen Merit/ANS NNAF

1 0

Additions to the NSFNET policy-based routing database
by Belinda Sue Blair 19 May '92

19 May '92

FYI...This is a resend of the nwg message. Some mail bounced... > >The following networks have been added to the NSFNET policy-based routing > database: > >T1 Network: >- ---------- > > Network IP: 136.184 > Network Name: LIBERTY > Location: Liberty Mutual Insurance Company, 225 Borthwick Avenue, > Portsmouth, NH 03801, USA > Country Code: US > > 1:1384 NEARnet Regional Network > 2:1383 NEARnet Regional Network > 3:560 NEARnet Regional Network > 4:281 NEARnet Regional Network > 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) > 11:756 T1-T3 Network Interconnect (Princeton, NJ) > 20:701 Alternet > > > Network IP: 139.184 > Network Name: NET-SUSSEX-UNIV > Location: Computing Service, University of Sussex, Falmer, Brighton, > East Sussex, BN1 9QJ, GREAT BRITAIN > Country Code: GB > > 1:274 TWBNET (FIX-East) > 2:60 TWBNET (FIX-West) > > > Network IP: 158.143 > Network Name: LSE > Location: London School of Economics and Political Science, Houghton > Street, London WC2A 2AE, GREAT BRITAIN > Country Code: GB > > 1:274 TWBNET (FIX-East) > 2:60 TWBNET (FIX-West) > > > Network IP: 161.28 > Network Name: UVCC-EDU-B > Location: Utah Valley Community College, 800 West 1200 South, Orem, UT > 84058 USA > Country Code: US > > 1:210 Westnet Regional Network (Utah Attachment) > 2:209 Westnet Regional Network (Colorado Attachment) > 12:754 T1-T3 Network Interconnect (Houston, TX) > 13:751 T1-T3 Network Interconnect (San Diego, CA) > > > Network IP: 192.33.16 > Network Name: COGS > Location: Computing Service, University of Sussex, Falmer, Brighton, > East Sussex, BN1 9QJ, GREAT BRITAIN > Country Code: GB > > 1:274 TWBNET (FIX-East) > 2:60 TWBNET (FIX-West) > > > Network IP: 192.35.205 > Network Name: EAPSNET > Location: Computing Service, University of Sussex, Falmer, Brighton,onnect (San Diego, CA) > > > Network IP: 192.133.90 > Network Name: TURING > Location: The Turing Institute Ltd, George House, North Hanover Street, > Glasgow G1 2AD, GREAT BRITAIN > Country Code: GB > > 1:274 TWBNET (FIX-East) > 2:60 TWBNET (FIX-West) > > > Network IP: 192.138.199 > Network Name: AEROASTRO > Location: Aeroastro, 520 Huntmar Park Drive, Suite 100A, Herndon, VA > 22070, USA > Country Code: US > > 1:297 Nasa Science Network (FIX-East) > 2:372 Nasa Science Network (FIX-West) > 10:750 T1-T3 Network Interconnect (Ann Arbor, MI) > 11:756 T1-T3 Network Interconnect (Princeton, NJ) > > > Network IP: 192.147.162 > Network Name: NWNET12 > Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA > 98007, USA > Country Code: US > > 1:685 NorthWestNet Regional Network > 2:73 NorthWestNet Regional Network > 3:101 NorthWestNet Regional Network > 12:754 T1-T3 Network Interconnect (Houston, TX) > 13:751 T1-T3 Network Interconnect (San Diego, CA) > > > Network IP: 192.147.248 > Network Name: SUNNYSIDE > Location: Sunnyside Computing, Inc., P.O. Box 299, Palo Alto, CA, > 94302, 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.149.92 > Network Name: SDGEMISSION > Location: San Diego Gas and Electric Co., P.O. Box 1831, San Diego, CA > 92112, USA > Country Code: US > > 1:1740 CERFnet > 12:754 T1-T3 Network Interconnect (Houston, TX) > 13:751 T1-T3 Network Interconnect (San Diego, CA) > > > Network IP: 192.150.32 > Network Name: NSI-NET12 > Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, > USA > Country Code: US > > 1:771 Nasa Science Network (Houston) > 2:372 Nasa Science Network (FIX-West) > 3:297 Nasa Science Network (FIX-East) > 12:754 T1-T3 Network Interconnect (Houston, TX) > 13:751 T1-T3 Network Interconnect (San Diego, CA) > > > Network IP: 192.150.33 > Network Name: NSI-NET13 > Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, > USA > Country Code: US > > 1:771 Nasa Science Network (Houston) > 2:372 Nasa Science Network (FIX-West) > 3:297 Nasa Science Network (FIX-East) > 12:754 T1-T3 Network Interconnect (Houston, TX) > 13:751 T1-T3 Network Interconnect (San Diego, CA) > > > Network IP: 192.156.211 > Network Name: METACARD-NET > Location: MetaCard Corporation, 4710 Shoup pl., Boulder, CO 80303, USA > Country Code: US > > 1:209 Westnet Regional Network (Colorado Attachment) > 2:210 Westnet Regional Network (Utah Attachment) > 12:754 T1-T3 Network Interconnect (Houston, TX) > 13:751 T1-T3 Network Interconnect (San Diego, CA) > >Total configured T1 networks: 5464 > > >T3 Network: >- ---------- > > Network IP: 136.184 > Network Name: LIBERTY > Location: Liberty Mutual Insurance Company, 225 Borthwick Avenue, > Portsmouth, NH 03801, USA > Country Code: US > > 1:560 NEARnet Regional Network > 2:281 NEARnet Regional Network > > > Network IP: 161.28 > Network Name: UVCC-EDU-B > Location: Utah Valley Community College, 800 West 1200 South, Orem, UT > 84058 USA > Country Code: US > > 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 > 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 > > > Network IP: 192.77.158 > Network Name: INTEROP-EAST > Location: Advanced Network & Services, Inc., 100 Clearbrook Road, > Elmsford, NY 10523, USA > Country Code: US > > 1:1666 ShowAS: Interop '92 - Washington, D.C. > > > Network IP: 192.138.199 > Network Name: AEROASTRO > Location: Aeroastro, 520 Huntmar Park Drive, Suite 100A, Herndon, VA > 22070, USA > Country Code: US > > 1:297 Nasa Science Network (FIX-East) > 2:372 Nasa Science Network (FIX-West) > > > Network IP: 192.147.162 > Network Name: NWNET12 > Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA > 98007, USA > Country Code: US > > 1:685 NorthWestNet Regional Network > 2:73 NorthWestNet Regional Network > > > Network IP: 192.147.167 > Network Name: nsfnet > Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA > 98007, USA > Country Code: US > > 1:685 NorthWestNet Regional Network > 2:73 NorthWestNet Regional Network > > > Network IP: 192.147.248 > Network Name: SUNNYSIDE > Location: Sunnyside Computing, Inc., P.O. Box 299, Palo Alto, CA, > 94302, USA > Country Code: US > > 1:200 BARRNet > 2:201 BARRNet > > > Network IP: 192.149.92 > Network Name: SDGEMISSION > Location: San Diego Gas and Electric Co., P.O. Box 1831, San Diego, CA > 92112, USA > Country Code: US > > 1:1740 CERFnet > > > Network IP: 192.150.32 > Network Name: NSI-NET12 > Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, > USA > Country Code: US > > 1:771 Nasa Science Network (Houston) > 2:372 Nasa Science Network (FIX-West) > 3:297 Nasa Science Network (FIX-East) > > > Network IP: 192.150.33 > Network Name: NSI-NET13 > Location: NASA Ames Research Center, MS 233-8, Moffett Field, CA 95014, > USA > Country Code: US > > 1:297 Nasa Science Network (FIX-East) > 2:372 Nasa Science Network (FIX-West) > > > Network IP: 192.156.211 > Network Name: METACARD-NET > Location: MetaCard Corporation, 4710 Shoup pl., Boulder, CO 80303, USA > Country Code: US > > 1:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 > 2:210 Westnet Regional Network (Utah Attachment) - ENSS 142 > > >Total configured T3 networks: 3645 > >***************************************************************** > >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. > >******************************* >- -Riaz Taherzadeh-Yazdian -Merit / NSFNET >- -Michael O'Neill -Merit / NSFNET >- -B. Sue Blair -Merit / NSFNET > >------- End of Forwarded Message >

1 0

New template.net form
by bsb 19 May '92

19 May '92

Regional techs, Greetings. There is a new template.net form available nis.nsf.net in the nsfnet/announced.networks directory. (I've appended a copy below for your convenience). It is version 5.2 dated May 18, 1992 and is by far the hippest version to date. I'm just kidding; the primary change is that you have the option of 'T1', 'T3', or 'both' for network type. There are also more helpful hints on how to submit NACRs as well as information on when the config deadlines are and when the config installation windows are. Enjoy. Please send feedback to nsfnet-admin(a)merit.edu. Thanks, -B. Sue Blair Merit Network Operations ------------------------- [nis.nsf.net:nsfnet/announced.networks/template.net] Version 5.2 18 May 1992 NSFNET Configuration Request Template for the NSFNET policy-based routing data base ---- Network Announcement Change Request ---- This template is to request announcement of networks to the NSFNET backbone. Configuration requests may only be submitted by the designated Routing contacts for the Autonomous Systems of the NSFNET. Configuration requests should be submitted to nsfnet-admin(a)merit.edu. Please read the explanation at the bottom of this form if you are unfamiliar with its contents. ***************************************************************************** ---- Network Announcement Change Request ---- The networks which request access to the NSFNET backbone agree that traffic from the networks that will transit the NSFNET backbone comply with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated February 1992. Inbound Announcements Add/Del Network: to NSFNET or Change T1, T3 ----------------------- --------- Network Number/Name or both 1st AS# 2nd AS# 3rd AS# A/D/C Country ------------------- -------- ------- ------- ------- --------- ------- Network Name: Organization Name: Organization Address: Additional Comments (optional): ***************************************************************************** EXAMPLE: Suppose network 141.214 (UMNET4), wishes to be announced to the NSFNET. Furthermore, they wish to have AS 233 as their PRIORITY 1 path and AS 177 as their PRIORITY 2 path on both the T1 and T3 networks. Their network announcement change request would be filled in as follows: ***************************************************************************** ---- Network Announcement Change Request ---- The networks which request access to the NSFNET backbone agree that traffic from the networks that will transit the NSFNET backbone comply with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated February 1992. Inbound Announcements Add/Del Network: to NSFNET or Change T1, T3, ----------------------- --------- Network Number/Name or both 1st AS# 2nd AS# 3rd AS# A/D/C Country ------------------- -------- ------- ------- ------- --------- ------- 141.214 both 233 177 A USA Network Name: (UMNET4) Organization Name: University of Michigan Organization Address: 1075 Beal Avenue, Ann Arbor, MI 48109 If the announcements on the T1 and T3 sides of the network were going to be different, the form would be filled out: Inbound Announcements Add/Del Network: to NSFNET or Change T1, T3, ----------------------- --------- Network Number/Name or both 1st AS# 2nd AS# 3rd AS# A/D/C Country ------------------- -------- ------- ------- ------- --------- ------- 141.214 T1 233 177 A USA T3 233 177 266 Also, in this example, Merit would like AS 266 to act as a backup on the T3 side. Merit could copy the as266(a)merit.edu mailgroup on the addition request to nsfnet-admin(a)merit.edu. This would aid in faster approval response time from the AS 266 admin folks. *********************************************************************** ***** Explanation of this form ***** Network Addition Request: PLEASE NOTE: (1) The individual submitting this request affirms that traffic from the networks recommended for inclusion in the NSFNET routing tables conforms to the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY." (2) An Internet network number must have been assigned by the NIC.DDN.MIL prior to its addition to the NSFNET routing database. If it was not assigned by the time of this request, a message will be sent by Merit to the requestor stating that the network has not been added to the NSFNET policy-based routing database. It is then up to the requestor to resubmit the application after registration with NIC.DDN.MIL. (3) Merit has to request a separate authorization from the National Science Foundation on a per-net basis to allow foreign network numbers to be added. Additions of foreign networks therefore may result in additional delays. Configurations are typically done by Merit on Tuesday and Friday mornings of every week. The installation of new configuration files is performed Tuesday and Friday mornings from 05:00-08:00 (Eastern time), so some backbone instability may be experienced during this timeframe. Requests should be received by noon on Monday (for Tuesday morning configs) and noon on Thursday (for Friday morning configs). The columns headed '1st AS#', '2nd AS#' and '3rd AS#' should be filled with the Autonomous System numbers which are to have priorities (or path weights) 1, 2 and 3 respectively. Please note that these are inbound routing announcements TO the NSFNET backbone; which means that the specified priority impacts the path of how packets are routed towards the specified network. It is possible to have more than three priorities. The offical name of the network, as it is registered at the NIC.DDN.MIL, should appear on the line following the network number. Finally, the name and address of the organizaion to which the network belongs should be listed following the network name.

1 0