- Test - lists.nanog.org

Re: RS/960 upgrade ... status report
by bmanning＠is.rice.edu 01 May '92

01 May '92

yakov(a)watson.ibm.com > > Ref: Your note of Fri, 1 May 92 7:12:54 CDT > > BGPv2 spec has the following text on the NEXT_HOP subject: > "The NEXT_HOP path attribute defines the IP address of the > border router that should be used as the next hop to the > networks listed in the UPDATE message. This border router > must belong to the same AS as the BGP peer that advertises it." > > BGPv2 spec requires checking NEXT_HOP ONLY for correct syntax > (i.e., NEXT_HOP should carry a syntactically valid IP address). > > There is no specified timeout between consecutive BGP close and > open. > > Yakov. > So, let me get this straight. What is POSSIBLE in version two is prohibited in version four in regards to NEXT_HOP. The latest ANS rcp_routed started enforcing version four semantics. I can not find where this was make public knowledge. Sigh... It also seems clear that a recommendation of how to compute interval times between BGP close and open would be useful for addition to either the BGPv4 or IDPR spec. -- Regards, Bill Manning bmanning(a)rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892

2 1

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

01 May '92

The following networks have been added to the NSFNET policy-based routing database: T1 Network: ---------- Network IP: 128.132 Network Name: LNX-ETHER3 Location: Rome Air Development Center, Grissis Air Force Base, Rome, NY 13441 USA Country Code: US 1:174 NYSERNet Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 132.147 Network Name: SCO Location: SCO Inc., 400 Encinal Street, Santa Cruz, CA 95060, USA Country Code: US 1:701 Alternet 2:702 Alternet 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 132.218 Network Name: CRIM-BNET7 Location: Centre de Recherche Informatique de Montreal, 3744 rue Jean-Brillant, Suite 500, Montreal, Quebec, H3T 1P1, CANADA Country Code: CA 1:603 CA*net router in Quebec 2:601 CA*net router in Toronto 3:602 CA*net router in Montreal Network IP: 136.249 Network Name: HGSNETS Location: Halliburton Geophysical Services, Inc., 7800 Banner Drive, Dallas, TX 75251, 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: 137.13 Network Name: AF-CONC-NET16 Location: SSC/SSMT, Gunter AFB, AL 36114, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 138.156 Network Name: USMC-MIL1 Location: MCCDP/MCCDC, US Marine Corps, Quantico, VA 22134-5010, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 142.74 Network Name: SP-AGENCY Location: Canadian Space Agency, Space Science Program, 100 Sussex Drive, PO Box 7275, Vanier Postal Station, Ottawa, Ontario K1L 8E3, CANADA Country Code: CA 1:601 CA*net router in Toronto 2:602 CA*net router in Montreal 3:603 CA*net router in Quebec Network IP: 147.81 Network Name: TASC Location: Tasc, 55 Walkers Brook Drive, Reading, MA 01867, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 158.228 Network Name: KRONOS Location: Prospect Innovation Network, 62 Fourth Ave., Waltham, MA 02154, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 159.56 Network Name: KODAK-EP-9 Location: EASTMAN KODAK COMPANY, 901 ELMGROVE ROAD, ROCHESTER, NY 14653-5815, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 160.86 Network Name: ODS-NET Location: Optical Data Systems, Inc., 1101 E. Arapaho Road, Richardson, TX 75081, USA Country Code: US 1:701 Alternet 2:702 Alternet 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) 20:279 SURANET Regional Network (Georgia Tech) Network IP: 192.5.156 Network Name: RSI Location: Research Systems, Inc., 777 29th Street, Suite 302, Boulder, CO 80303, USA Country Code: US 1:1262 Nasa Science Network (Boulder, Colorado) 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.48.37 Network Name: NET-SIMTEK Location: Colorado School of Mines, 1500 Illinois, Golden, CO 80401, 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.75.152 Network Name: BWS1 Location: Beame and Whiteside Software Ltd., 259 Fiddler's Green Road, Ancaster, Ontario, L9G 1W9, CANADA Country Code: CA 1:601 CA*net router in Toronto 2:602 CA*net router in Montreal 3:603 CA*net router in Quebec Network IP: 192.76.31 Network Name: OXNET-26 Location: Oxford University Computing Service, 13 Banbury Road, Oxford OX2 6NN, UNITED KINGDOM Country Code: GB 1:274 TWBNET (FIX-East) 2:60 TWBNET (FIX-West) Network IP: 192.77.10 Network Name: EYRING-NET Location: Eyring Research Institute, Inc., Systems Software Division, 1455 West 820 North, Provo, UT 84601 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.77.172 Network Name: NET-FRONTIER-2 Location: Electronic Frontier Foundation, 155 Second Street, Cambridge, MA 02141, USA Country Code: US 1:174 NYSERNet Regional Network / PSI 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.101.140 Network Name: PSC-PPP-TEST Location: Pittsburgh Supercomputing Center, 4400 5th Avenue, Pittsburgh, PA 15213, USA Country Code: US 1:1206 PSCNET Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.124.129 Network Name: ORBSEMI Location: Orbit Semiconductor, Inc., 1230 Bordeaux Drive, Sunnyvale, CA 94086 USA Country Code: US 1:701 Alternet 2:702 Alternet 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) Network IP: 192.138.253 Network Name: AVS Location: Advanced Visual Systems Inc., 300 Fifth Ave., Waltham, MA 02154, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 3:1384 NEARnet Regional Network 4:1383 NEARnet Regional Network 16:750 T1-T3 Network Interconnect (Ann Arbor, MI) 17:756 T1-T3 Network Interconnect (Princeton, NJ) 20:701 Alternet Network IP: 192.139.42 Network Name: SENECA1 Location: Seneca College, 1750 Finch Ave. East, North York, Ontario, M2J 2X5, CANADA Country Code: CA 1:601 CA*net router in Toronto 2:602 CA*net router in Montreal 3:603 CA*net router in Quebec Network IP: 192.148.235 Network Name: NET-COMTIME Location: Commercial Timesharing, Inc., 2650 S. Arlington Rd., Akron, OH 44319, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.236 Network Name: NET-MONOLITH Location: Monolith Software, Inc., 2014 Rolling Meadows Dr., Columbus, OH 43228-9603, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.237 Network Name: NET-DATASERV Location: 37562 Hills Tech Dr., Farmington Hills, MI 48331, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.238 Network Name: NET-TRIONIX Location: Trionix Research Laboratory, Inc., 8037 Bavaria Rd., Twinsburg, OH 44087, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.239 Network Name: NET-OARNET37 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.240 Network Name: NET-OARNET38 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.241 Network Name: NET-OARNET39 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.242 Network Name: NET-OARNET40 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.243 Network Name: NET-OARNET41 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.244 Network Name: NET-OARNET42 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.245 Network Name: NET-OARNET43 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.246 Network Name: NET-OARNET44 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.247 Network Name: NET-OARNET45 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.248 Network Name: NET-OARNET46 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.249 Network Name: NET-OARNET47 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.250 Network Name: NET-OARNET48 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.148.251 Network Name: NET-OARNET49 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.26 Network Name: OARNET17 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.27 Network Name: OARNET18 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.28 Network Name: OARNET19 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.29 Network Name: OARNET20 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.30 Network Name: OARNET21 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.31 Network Name: OARNET22 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.32 Network Name: OARNET23 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.33 Network Name: OARNET24 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.34 Network Name: OARNET25 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.35 Network Name: OARNET26 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.36 Network Name: OARNET27 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.37 Network Name: OARNET28 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.38 Network Name: OARNET29 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.39 Network Name: OARNET30 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.40 Network Name: OARNET31 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.41 Network Name: OARNET32 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:750 T1-T3 Network Interconnect (Ann Arbor, MI) 2:756 T1-T3 Network Interconnect (Princeton, NJ) 10:266 CICNET at MERIT 11:267 CICNET at UIUC Network IP: 192.153.92 Network Name: CAA Location: US ARMY CONCEPTS ANALYSIS AGENCY, 8120 WOODMONT AVENUE, BETHESDA, MD 20814, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) 2:184 Milnet (FIX-East) 3:164 Milnet (FIX-West) Network IP: 192.153.142 Network Name: TINMS-LAN1 Location: DCSOPS, HQ 5th Signal Command, ASQE-OP-OC, APO AE 09056 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.153.143 Network Name: TINMS-LAN2 Location: DCSOPS, HQ 5th Signal Command, ASQE-OP-OC, APO AE 09056 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.153.144 Network Name: TINMS-LAN3 Location: DCSOPS, HQ 5th Signal Command, ASQE-OP-OC, APO AE 09056 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.153.145 Network Name: TINMS-LAN4 Location: DCSOPS, HQ 5th Signal Command, ASQE-OP-OC, APO AE 09056 Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.153.146 Network Name: ARPERCEN-NET Location: USAISC-ARPERCEN, DARP-IMA-N, 9700 Page Blvd., St. Louis, MO 63132, USA Country Code: US 1:164 Milnet (FIX-West) 2:184 Milnet (FIX-East) Network IP: 192.158.1 Network Name: VAMCPALOALT1 Location: Veterans Administration-VA Medical Center, 3801 Miranda Avenue, Palo Alto, CA 94304, 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.158.2 Network Name: VAMCPALOALT2 Location: Veterans Administration-VA Medical Center, 3801 Miranda Avenue, Palo Alto, CA 94304, 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 T1 configured networks: 5291 T3 Network: ---------- Network IP: 128.132 Network Name: LNX-ETHER3 Location: Rome Air Development Center, Grissis Air Force Base, Rome, NY 13441, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 130.71 Network Name: STOLAF Location: St. Olaf College, Academic Computing Center, Northfield, MN 55057, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 132.147 Network Name: SCO Location: SCO Inc., 400 Encinal Street, Santa Cruz, CA 95060, USA Country Code: US 42:702 Alternet 43:701 Alternet Network IP: 136.249 Network Name: HGSNET Location: Halliburton Geophysical Services, Inc., 7800 Banner Drive, Dallas, TX 75251, USA Country Code: US 1:114 SESQUINET Regional Network 2:1700 SESQUINET Regional Network Network IP: 137.13 Network Name: AF-CONC-NET16 Location: SSC/SSMT, Gunter AFB, AL 36114 Country Code: US Network IP: 137.22 Network Name: CARLETONS Location: Carleton College, One North College Street, Northfield, MN 55057-4040, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 138.192 Network Name: HAMLINE Location: Hamline University, 1536 Hewitt Avenue, St. Paul, MN 55104, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 140.88 Network Name: BETHEL-EDU Location: Bethel College, 3900 Bethel Drive, St. Paul, MN 55432, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 140.190 Network Name: MNSMC-NET Location: St. Mary's College of Minnesota, Terrace Heights, Winona, MN 55987-0857, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 140.209 Network Name: STTHOMAS Location: St.Thomas University, 2115 Summit Avenue, St. Paul, MN 55105, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 140.225 Network Name: STKATE-NET Location: College of St. Catherine, 2004 Randolph Avenue, St. Paul, MN 55105 USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 141.140 Network Name: MACALESTER Location: Macalester College, 1600 Grand Avenue, St. Paul, MN 55105-1899, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 141.224 Network Name: AUGSBURG Location: Augsburg College, 731 21st Avenue South, Minneapolis, MN 55454, USA\ Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 147.81 Network Name: TASC Location: Tasc, 55 Walkers Brook Drive, Reading, MA 01867, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 158.228 Network Name: KRONOS Location: Prospect Innovation Network, 62 Fourth Ave., Waltham, MA 02154, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 159.56 Network Name: KODAK-EP-9 Location: EASTMAN KODAK COMPANY, 901 ELMGROVE ROAD, ROCHESTER, NY 14653-5815, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 160.86 Network Name: ODS-NET Location: Optical Data Systems, Inc., 1101 E. Arapaho Road, Richardson, TX 75081, USA Country Code: US 42:702 Alternet 43:701 Alternet Network IP: 192.5.156 Network Name: RSI Location: Research Systems, Inc., 777 29th Street, Suite 302, Boulder, CO 80303, USA Country Code: US 1:1262 Nasa Science Network (Boulder, CO) 2:372 Nasa Science Network (Ames) 3:297 Nasa Science Network (FIX-East) Network IP: 192.48.37 Network Name: NET-SIMTEK Location: Colorado School of Mines, 1500 Illinois, Golden, CO 80401, 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.77.10 Network Name: EYRING-NET Location: Eyring Research Institute, Inc., Systems Software Division, 1455 West 820 North, Provo, UT 84601 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.172 Network Name: NET-FRONTIER-2 Location: Electronic Frontier Foundation, 155 Second Street, Cambridge, MA 02141, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.101.140 Network Name: PSC-PPP-TEST Location: Pittsburgh Supercomputing Center, 4400 5th Avenue, Pittsburgh, PA 15213, USA Country Code: US 1:1206 PSCNET Regional Network 2:204 PSCNET Regional Network Network IP: 192.124.129 Network Name: ORBSEMI Location: Orbit Semiconductor, Inc., 1230 Bordeaux Drive, Sunnyvale, CA 94086 USA Country Code: US 42:702 Alternet 43:701 Alternet Network IP: 192.138.253 Network Name: AVS Location: Advanced Visual Systems Inc., 300 Fifth Ave., Waltham, MA 02154, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network Network IP: 192.148.235 Network Name: NET-COMTIME Location: Commercial Timesharing, Inc., 2650 S. Arlington Rd., Akron, OH 44319, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.236 Network Name: NET-MONOLITH Location: Monolith Software, Inc., 2014 Rolling Meadows Dr., Columbus, OH 43228-9603, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.237 Network Name: NET-DATASERV Location: DataServ, Inc., 37562 Hills Tech Dr., Farmington Hills, MI 48331, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.238 Network Name: NET-TRIONIX Location: Trionix Research Laboratory, Inc., 8037 Bavaria Rd., Twinsburg, OH 44087, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.239 Network Name: NET-OARNET37 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.240 Network Name: NET-OARNET38 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.241 Network Name: NET-OARNET39 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.242 Network Name: NET-OARNET40 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.243 Network Name: NET-OARNET41 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.244 Network Name: NET-OARNET42 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.245 Network Name: NET-OARNET43 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-116, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.246 Network Name: NET-OARNET44 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.247 Network Name: NET-OARNET45 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.248 Network Name: NET-OARNET46 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.249 Network Name: NET-OARNET47 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.250 Network Name: NET-OARNET48 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.148.251 Network Name: NET-OARNET49 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.26 Network Name: OARNET17 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.27 Network Name: OARNET18 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.28 Network Name: OARNET19 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.29 Network Name: OARNET20 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.30 Network Name: OARNET21 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.31 Network Name: OARNET22 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.32 Network Name: OARNET23 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.33 Network Name: OARNET24 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.34 Network Name: OARNET25 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.35 Network Name: OARNET26 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.36 Network Name: OARNET27 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.37 Network Name: OARNET28 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.38 Network Name: OARNET29 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.39 Network Name: OARNET30 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.40 Network Name: OARNET31 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.153.41 Network Name: OARNET32 Location: OARnet, 1224 Kinnear Road, Columbus, OH 43212-1163, USA Country Code: US 1:600 OARNET, Cleveland, OH 2:266 CICNET at MERIT 3:267 CICNET at UIUC Network IP: 192.158.1 Network Name: VAMCPALOALT1 Location: Veterans Administration-VA Medical Center, 3801 Miranda Avenue, Palo Alto, CA 94304, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.158.2 Network Name: VAMCPALOALT2 Location: Veterans Administration-VA Medical Center, 3801 Miranda Avenue, Palo Alto, CA 94304, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Total T3 configured networks: 3547 T3 Special Additions: AS Number: 1262 AS Notes: Nasa Science Network (Boulder, CO) AS Country Code: US ANS: No Gate: 192.43.244.5 - NCAR.NSN.NASA.GOV ENSS 141 -- Boulder, CO ***************************************************************** 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 / Riaz Taherzadeh-Yazdian / Michael O'Neill Merit/NSFNET

1 0

Re: RS/960 upgrade ... status report
by Jessica Yu 01 May '92

01 May '92

Yes, this is related to the problem. However, the issue is if an implementation violating the rule by sending a route to its bgp neighbor with that neighbor as the next_hop. When the neighbor detect the problem, should it CLOSE the session or should it just DISCARD the 'bad' route, log the event and send alter? The latter may be a better one. --Jessica

1 0

RS/960 upgrade ... status report
by yakov＠watson.ibm.com 01 May '92

01 May '92

Ref: Your note of Fri, 1 May 92 7:12:54 CDT BGPv2 spec has the following text on the NEXT_HOP subject: "The NEXT_HOP path attribute defines the IP address of the border router that should be used as the next hop to the networks listed in the UPDATE message. This border router must belong to the same AS as the BGP peer that advertises it." BGPv2 spec requires checking NEXT_HOP ONLY for correct syntax (i.e., NEXT_HOP should carry a syntactically valid IP address). There is no specified timeout between consecutive BGP close and open. Yakov.

1 0

Re: RS/960 upgrade ... status report
by bmanning＠is.rice.edu 01 May '92

01 May '92

Thanks but... The ciscos AND the NSF/ANS routers STILL speak using BGPv2. What does that spec have to say on the matter? Also, is there any information on reccomended interval between a BGP close and open? This would be applicable to the BGPv2 spec as well. -- Regards, Bill Manning bmanning(a)rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892

1 0

RS/960 upgrade ... status report
by yakov＠watson.ibm.com 01 May '92

01 May '92

Ref: Your note of Fri, 01 May 92 00:30:06 -0400 Folks, Here is the text from BGP-4 specs that I think is relevent to the NEXT_HOP discussion: "A BGP speaker must never advertise an address of a neighbor back to that neighbor as a NEXT_HOP, for a route that the speaker is originating. A BGP speaker must never install a route with itself as a next hop." (The full BGP-4 document, bgp.txt, is available via anonymous FTP from ftp.cisco.com) Yakov Rekhter

1 0

RS/960 upgrade ... status report
by yakov＠watson.ibm.com 01 May '92

01 May '92

Ref: Your note of Fri, 01 May 92 00:30:06 -0400 Folks, Here is the text from BGP-4 specs that I think is relevent to the NEXT_HOP discussion: "A BGP speaker must never advertise an address of a neighbor back to that neighbor as a NEXT_HOP, for a route that the speaker is originating. A BGP speaker must never install a route with itself as a next hop." (The full BGP-4 document, bgp.txt, is available via anonymous FTP from ftp.cisco.com) Yakov Rekhter

1 0

Re: RS/960 upgrade ... status report
by bmanning＠is.rice.edu 01 May '92

01 May '92

Ok, here is the relevant section of the config... router bgp 114 distribute-list 9 out static distribute-list 2 out rip distribute-list 9 out igrp 114 distribute-list 9 out igrp 280 distribute-list 4 in default-metric 1 network 128.42.0.0 network 128.241.0.0 redistribute static redistribute rip redistribute igrp 114 redistribute igrp 280 neighbor 128.241.0.94 remote-as 690 neighbor 128.241.0.82 remote-as 145 Where list 9 is to be advertized to the NSFnyet. The single change we made was to add the distribute-list 9 out static line. -- Regards, Bill Manning bmanning(a)rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892

1 0

Re: RS/960 upgrade ... status report
by bmanning＠is.rice.edu 01 May '92

01 May '92

Mark said: observed during RS/960 testing. The problem involved some aberrant behavior of rcp_routed when a misconfigured regional peer router would advertise a route via BGP to an ENSS whose next hop was the ENSS itself. The old rcp_routed could go into a loop sending multiple redirect packets out on to the subnet. The new rcp_routed will close the BGP session if it receives an announcement of such a route. The new rcp_routed software also has support for externally administered inter-AS metrics, an auto-restart capability, and bug fixes for BGP overruns with peer routers. This deployment caused a few problems. One is that this new feature of rcp_routed pointed out a misconfigured peer router at Rice University in Houston. This caused the BGP connection to open and close rapidly which caused further problems on the peer router. Eventually the peer was reconfigured to remove the bad route, which fixed the problem. Another problem was on the Argonne ENSS. This node crashed in such a way that it was ---------------------------------- What he did not say: The new rcp_routed will (virtually) immeadiately after the close, reopen a BGP session and pump all known routes at the BGP peer. If the peer is already working on processing the old ones, this adds an unneeded burden on the regional peer. I have not reviewed the spec in detail, but there should be something in place to prevent a constant cycle of close, open, slam 5k routes, close, open, slam 5k routes, close... well, you get the picture. This points out a configuration problem with BGP in the ANS T3 routers, in addition to the less than optimal configuration that we had in our ciscos. Just my two cents from the other side of the fence. -- Regards, Bill Manning bmanning(a)rice.edu PO Box 1892 713-285-5415 713-527-6099 Houston, Texas R.U. (o-kome) 77251-1892

3 2

RS/960 upgrade on the T3 backbone: status report
by mak 01 May '92

01 May '92

Phase-III RS960 Deployment Status Report - Week 1 ================================================= Jordan Becker, ANS Mark Knopper, Merit Summary ======= - RS/960 Hardware Deployment Early last Saturday morning, April 25, the first step of the Phase-III RS960 DS3 upgrade to the T3 Backbone was completed. The following T3 backbone nodes are currently running with new T3 hardware and software in a stable configuration: Seattle POP: CNSS88, CNSS89, CNSS91 Denver POP: CNSS96, CNSS97, CNSS99 Regionals: ENSS141 (Boulder), ENSS142 (Salt Lake), ENSS143 (U. Washington) This Friday night 5/1 and Saturday morning 5/2, the second step will occur, with the following nodes being upgraded: Los Angeles POP (barring rioting, etc.): CNSS16, CNSS17, CNSS19 San Francisco POP: CNSS8, CNSS9, CNSS11 Regionals: ENSS128 (Palo Alto), ENSS144 (NASA Ames/FIX-West), ENSS135 (San Diego) - Kernel Build and Routing Software Deployment Early this morning (April 30), all of the network nodes were upgraded with Build 2.78.22 and a new version of rcp_routed. Several nodes (the Step 1 nodes and also the Ann Arbor ENSS) have been running in this configuration since April 27. This software build includes drivers for the RS/960 cards, and several bug fixes. The fixes include reliability improvements to the FDDI software, notably a soft reset for a hung card; and some additional improvements to the T960 ethernet and T1 card support to fix a problem where the card could hang under a heavy load. The rcp_routed change includes a fix to a problem that was observed during RS/960 testing. The problem involved some aberrant behavior of rcp_routed when a misconfigured regional peer router would advertise a route via BGP to an ENSS whose next hop was the ENSS itself. The old rcp_routed could go into a loop sending multiple redirect packets out on to the subnet. The new rcp_routed will close the BGP session if it receives an announcement of such a route. The new rcp_routed software also has support for externally administered inter-AS metrics, an auto-restart capability, and bug fixes for BGP overruns with peer routers. This deployment caused a few problems. One is that this new feature of rcp_routed pointed out a misconfigured peer router at Rice University in Houston. This caused the BGP connection to open and close rapidly which caused further problems on the peer router. Eventually the peer was reconfigured to remove the bad route, which fixed the problem. Another problem was on the Argonne ENSS. This node crashed in such a way that it was not reachable and there was difficulty contacting the site to reboot the machine. Once the reboot was done the ENSS came back up running properly. We are looking into the cause of this crash, as this is the first time this has happened in all of our testing and deployment. The third problem was at the CoNCert ENSS, and this node crashed in such a way that the unix file system was completely lost, and this requires a complete rebuild of the system. This problem has happened in two cases previously, and seems to be related to an AIX problem rather than anything in the new software build. It is an insidious problem since it completely wipes out any trace of what may have caused it. We continue to look into this. In our view, none of these problems are severe enough to call off the deployment of the RS/960 hardware upgrade on the west coast Saturday morning. These problems aren't related to the new hardware or software support for the new cards, but seem to be problems in other parts of the new software build or routing daemon. The following section details our experiences of the first week's deployment. We believe we have an understanding of the problems that occurred and have increased the number of spare cards in the kits that the teams will take out to the sites. Summary of Week 1 (beginning 4/25) RS/960 Deployment ==================================================== Since the deployment, nodes CNSS88 and CNSS96 have been running with mixed technology (i.e. 3xRS960 T3 interfaces, 1xHawthorne T3 interface). Production traffic on the affected ENSS nodes was cutover to the T1 backbone at 2:00 AM EST on 4/25. The Denver POP nodes were returned to full service after approximately 10.5 hours and Seattle after about 13 hrs of work. The new software had been deployed on the affected nodes during the prior week. The physical upgrade consisted of mechanical changes to the RS6000 machines including (1) replacement of the RS6000 I/O planar, (2) replacement of the Hawthorne T3 adapters with RS960 adapters, (3) upgrading the DSU hardware and associated cabling, (4) a modification of the cooling capabilities of the RS6000, (5) updating and standardizing on new labels and (6) local software configuration changes accommodating the use of new hardware. The nodes were then tested and returned to production service. Although the resulting configuration is very stable and gratifying to the team working on the upgrade, the process was not quite as smooth as had been expected. There were 33 RS960 T3 interface adapters, T3 DSUs, and 9 I/O planars installed. Out of these, 5 RS960 adapters and 2 I/O planars had to be replaced to achieve stability. The failing new components were air-shipped back to the staging lab for a complete failure analysis. and a summary of the results are described below. All of the problems involving replaced components have been identified or explained. The post-manufacturing burn-in and staging process consists of a stress test involving card-to-card traffic testing, DSU testing, and power cycling prior to shipping. Lab burn-in and staging procedures have been adjusted based upon our experiences with the first deployment step. The installation procedures will be fine tuned to improve our efficiency and reduce the installation time required. It is therefore our intention to continue with the step 2 deployment plan in the San Francisco and Los Angeles backbone nodes (and adjacent ENSS nodes) on Friday evening 5/1. Installation Problems Encountered ================================= The replacement of the RS6000 I/O planers had to be performed twice on nodes CNSS88 and CNSS91 after the nodes did not come up properly the first time. The original set of planers were returned to the lab for analysis. It was determined that the underside of the planars were damaged during the physical installation process. The procedure for installing these planars in the RS6000 model 930 rack mounted system has been modified to prevent this type of damage from occuring. Adapter re-seating and reconfiguration was required on the asynchronous communications adapter on CNSS89. The dual planar change and troubleshooting work adversely affected the hard disk on CNSS88 and the disk image had to be reloaded from tape. An apparent dysfunctional DSU HSSI card connected to CNSS97 was replaced and was returned for lab failure analysis. The analysis revealed that a DSU microprocessor was not properly seated. T3 Technologies will re-inspect the DSUs for proper seating of all DSU components. The DSU at ENSS142 (Salt Lake City) needed internal work. The analysis revealed a bent pin on the connector between the HSSI card and the DSU backplane. T3 Technologies Inc. (DSU manufacturer) identified a mechanical deficiency in the connector that can cause certain pins to loosen and bend during insertion of the card. T3 Technologies will add a procedure to inspect these connectors prior to shipment for any deficiencies. An RS960 T3 card in CNSS89 did not have the correct electrical isolation spacers installed, and this caused a temporary short circuit. The card was returned to the lab and it was determined that a last-minute change was made to the card to swap an i596 serializer chip and that the spacer was erroneously left off. A visual inspection procedure for spacers and standoffs will be added to the manufacturing and staging inspection process. The RS960 T3 card in CNSS97 came up in a NONAP mode, however the card continued to respond to DSU queries. The card was replaced. During the failure analysis, the card passed all stress tests. This card was swapped prior to a planar change and the NONAP mode has been attributed to the planar problem. When reliable connectivity could not be achieved between CNSS97<->ENSS141, another RS960 T3 card in CNSS97 was replaced. The lab failure analysis revealed that the 20Mhz oscillator crystal on the card was broken due to a mechanical shock. This shock could have occured during shipping or handling. CNSS91 rebooted after the upgrade and exhibited an unstable configuration. Both the I/O planar and the RS960 T3 card were changed before stable operation was achieved. The RS960 card was later found to have a cold solder joint between the RAM module and adapter. The solder joint would allow the card to work when cold, but would fail intermittently when running hot. A simple adapter thermal cycling procedure will be investigated to determine if this problem can be avoided in the future. CNSS88 was the last node to come up. The I/O planar and memory card had to be re-seated, and an RS960 T3 card replacement was necessary. The RS960 card was found to have a solder splash that was overlapping two adjacent pins. A general corrective action for this problem involves adding a procedure involving high magnification visual microchannel interface inspection for shorts. Conclusions =========== Although the Step 1 installation was complicated by several component problems, the entire deployment team (IBM, Merit, ANS, MCI) has a high comfort level with the results of the failure analysis, the stability of the resulting installation, and overall deployment process. We are very encouraged that we have completed this first step and acheived a very stable configuration within the time, human resources, spares and support that was provisioned as part of the deployment plan. The software bring-up and test scripts worked exactly as planned. The teamwork between the 50+ individuals involved at Merit, IBM, MCI and ANS was excellent. The basic installation process is sound, although some minor changes will be implemented in the future installation steps. These will include the RS960 adapter installation, DSU trouble-shooting procedure and the I/O planar change process. Also the number of spares provisioned in a deployment kit will be increased as a pre-caution for future installations. There has been one software problem identified with the new technology on the test network since the end of system testing on 4/17. This involves a microcode bug where a portion of the RS960 on-card memory will not report a parity error to the system if that portion of the memory suffers a failure. All RS960 on-card memory is tested prior to shipment and a microcode fix to this problem will be delivered by IBM for testing within the next week. Only a single RS960 adapter has demonstrated an on-card memory parity error during all test network testing. Next Steps ========== Step 2 of the deployment is currently scheduled to commence at 23:00 local time on 5/1. Step 2 will involve the following nodes/locations: May 1/2 San Francisco, Los Angeles core nodes T3 ENSS Nodes: Palo Alto E128, San Diego E135, Other ENSS Nodes: E144, E159, E156, E170 also affected Second core node visit: Seattle

1 0