- NANOG - lists.nanog.org

Final agenda for the Merit/NSFNET Regional Techs Meeting
by Sheri M. Repucci 14 Jan '93

14 Jan '93

Here is the final agenda (okay, it may not be the absolute final one but you won't see another one until you arrive in Boulder). :-) Also, I've included a recommended reading list to help prepare for the discussions we will be having. Enjoy! Sheri Repucci (313) 936-2085 ================================================================= AGENDA - Merit/NSFNET Regional Techs Meeting ==================================================================== Thursday January 21, 1993 ------------------------- 8:30-9:00 Registration & Continental breakfast 9:00-9:15 Opening remarks (Sheri Repucci/Merit) 9:15-10:45 GIX, NAPS, Route Servers (Elise Gerich/Merit) 10:45-11:00 short break 11:00-12:30 Transition to "Next Generation NSFNET" (Dan Jordt/NorthWestNet) 12:30-1:30 Lunch 1:30-3:00 Implementation of CIDR (Vince Fuller/BARRNET) 3:00-3:15 short break 3:15-4:45 Address Allocation Strategies with CIDR (Dan Long/NEARNET) 6:00-8:30 Social gathering at the Red Lion Restaurant (in the mountains) 9:00-? Sleigh ride through ghost towns and mining camps Friday January 22, 1992 ----------------------- 8:30-9:00 Continental Breakfast 9:00-9:30 US West tour 9:30-10:30 Virtual Routes (Bilal Chinoy/SDSC) 10:30-12:00 Current Status/Problems (Mark Knopper/Merit) 12:00-1:00 Lunch 1:30-3:30 NCAR tour =================================================================== Reading list suggestions: rfc1338.txt Jun 92 (Fuller) Supernetting: an Address Assignment and Aggregation Strategy rfc1366.txt Oct 92 (Gerich) Guidelines for Management of IP Address Space draft-rekhter-ipaddress-guide-06.txt INTERNET DRAFT Y. Rekhter, T. Li Guidelines for IP Address Allocation Jan 1992 ACM CCR, B. Chinoy and Y. Rekhter Injecting Inter-Autonomous routes into intra-autonomous system routing.

1 0

Re: Fun & Games *after* the Regional Techs Meeting
by prue＠ISI.EDU 14 Jan '93

14 Jan '93

Sheri, I can't find the note but I think Pam Ciesla sent me a note saying a hotel said that there was some unnamed place about 25 miles away, which was about 45 minutes driving time. I just recently heard of Winter Park. I would be all for a free bus trip their. Count me in. If the bus falls through I will drive whomever I can fit in whatever I get for a car. Walt Prue 310-822-1511

2 1

CERT Advisory - Revised Hewlett-Packard NIS ypbind Vulnerability
by CERT Advisory 13 Jan '93

13 Jan '93

============================================================================= CA-93:01 CERT Advisory January 13, 1993 Revised Hewlett-Packard NIS ypbind Vulnerability ----------------------------------------------------------------------------- *** THIS IS A REVISED CERT ADVISORY *** *** IT CONTAINS NEW INFORMATION REGARDING AVAILABILITY OF IMAGE KITS *** *** SUPERSEDES CERT ADVISORY CA-92:17 *** The CERT Coordination Center has received information concerning a vulnerability in the NIS ypbind module for the Hewlett-Packard (HP) HP/UX Operating System for series 300, 700, and 800 computers. HP has provided revised patches for all of the HP/UX level 8 releases (8.0, 8.02, 8.06, and 8.07). This problem is fixed in HP/UX 9.0. The following patches have been superseded: Patch ID Replaced by Patch ID PHNE_1359 PHNE_1706 PHNE_1360 PHNE_1707 PHNE_1361 PHNE_1708 All HP NIS clients and servers running ypbind should obtain and install the patch appropriate for their machine's architecture as described below. ----------------------------------------------------------------------------- I. Description A vulnerability in HP NIS allows unauthorized access to NIS data. II. Impact Root on a remote host running any vendor's implementation of NIS can gain root access on any local host running HP's NIS ypbind. Local users of a host running HP's NIS ypbind can also gain root access. III. Solution 1) All HP NIS clients and servers running ypbind should obtain and install the patch appropriate for their machine's architecture. These patches contain a version of ypbind that only accepts ypset requests from a superuser port on the local host. This prevents a non-superuser program from sending rogue ypset requests to ypbind. They also include the mod from the superseded patches which prevented a superuser on a remote system from issuing a ypset -h command to the local system and binding the system to a rogue ypserver. These patches may be obtained from HP via FTP (this is NOT anonymous FTP) or the HP SupportLine. To obtain HP security patches, you must first register with the HP SupportLine. The registration instructions are available via anonymous FTP at cert.org (192.88.209.5) in the file "pub/vendors/hp/supportline_and_patch_retrieval". The new patch files are: Architecture Patch ID Filename Checksum ------------ -------- -------- -------- Series 300 PHNE_1706 /hp-ux_patches/s300_400/8.X/PHNE_1706 38955 212 Series 700 PHNE_1707 /hp-ux_patches/s700/8.X/PHNE_1707 815 311 Series 800 PHNE_1708 /hp-ux_patches/s800/8.X/PHNE_1708 56971 299 2) The instructions for installing the patch are provided in the PHNE_xxxx.text file (this file is created after the patch has been unpacked). The checksums listed above are for the patch archive files from HP. Once unpacked, each shell archive contains additional checksum information in the file "patchfilename.text". This checksum is applicable to the binary patch file "patchfilename.updt". If you have any questions about obtaining or installing the patches, contact the USA HP SupportLine at 415-691-3888, or your local HP SupportLine number. Please note that the telephone numbers in this advisory are appropriate for the USA and Canada. ----------------------------------------------------------------------------- The CERT Coordination Center wishes to thank Brian Kelley of Ford Motor Company for bringing this vulnerability to our attention. We would also like to thank Hewlett-Packard for their response to this problem. ----------------------------------------------------------------------------- If you believe that your system has been compromised, contact the CERT Coordination Center 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 personnel answer 7:30 a.m.-6:00 p.m. EST(GMT-5)/EDT(GMT-4), on call for emergencies during other hours. CERT Coordination Center 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: Fun & Games *after* the Regional Techs Meeting
by Vince Fuller 13 Jan '93

13 Jan '93

Vince and other Skiing Fans- Well, I wouldn't really classify myself as a "skiiing fan" (but it seemed like the "think to do" during winter in Colorado...) - I'm actually not much of a skiier, so I hope we can find a place with a relatively large number of easy runs... --Vince

1 0

Re: Fun & Games *after* the Regional Techs Meeting
by Sheri M. Repucci 13 Jan '93

13 Jan '93

Vince and other Skiing Fans- Due to a rather unexpected set of events I have just been offered free round trip bus service for us to the ski resort in Winter Park for Saturday the 23rd. However, as with all of these sorts of things I need to see what the level of interest is before committing the bus. So...all parties interested in skiing at Winter Park on Saturday please stand up and be counted. By the way, I have no idea if Winter Park is a good place to ski or not...my contact there claims it's the best place near Boulder...but I suspect his view is somewhat prejudiced by the fact that he is employeed by the place...so unbiased advise is welcome. The bus would leave Boulder about 7:30am and return about 3:30pm. No doubt they would be willing to pick up and drop off at the Clarion if that is where the majority of folks are staying. I would like to go (although I doubt I will strap on a pair of skiis)...so we have a count of 1 so far for Winter Park. Sheri Repucci Merit/Internet Engineering (313) 936-2085 (phone) (313) 747-3745 (fax)

2 1

Re: Fun & Games *after* the Regional Techs Meeting
by Sheri M. Repucci 13 Jan '93

13 Jan '93

Walt- What is the name of the ski are you were referring to in your message below? Do you know anything about Winter Park? I was told it was 1 1/2 hours away from Boulder. -Sheri Repucci

1 0

Re: Fun & Games *after* the Regional Techs Meeting
by prue＠ISI.EDU 12 Jan '93

12 Jan '93

Vince, I'm planning on staying until Sunday AM. I am going to try to go skiing if my knee is feeling well enough from the last time I went. You are welcome to come with me if I do go. I got word that there is a ski area about 25 miles away which is reportedly about 45 minutes away from Boulder. It is hard to believe the differences in prices of air fares by staying an extra day and a half. Walt

1 0

Fun & Games *after* the Regional Techs Meeting
by Vince Fuller 12 Jan '93

12 Jan '93

Is anyone else going to be hanging around Boulder through Saturday night to get the cheap fare ($283 vs. $850 for me)? Any plans or ideas for things to do on Friday night/Saturday? Anyone looking to put together a ski day for Saturday (not that I'm much of a skiier)? --Vince

2 1

Additions to the NSFNET policy-based routing database
by Steven K. Widmayer 12 Jan '93

12 Jan '93

The following additions have been made to the NSFNET policy-based routing database and will be installed on the T3 backbone by 08:00 EST Tuesday: Total configured T3 networks: 8686 IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 138.113 ANASAZI C:US D:01/11/93 1:174 141.131 CIRRUS C:US D:01/11/93 1:174 151.141 ETSUNET C:US D:01/11/93 1:279 2:86 161.134 EMPROS C:US D:01/10/93 1:267 2:1225 3:266 4:555 162.70 AMSWAN4 C:US D:01/11/93 1:701 2:702 3:279 164.42 UIPRNET-B C:US D:01/11/93 1:86 2:279 192.42.145 UW-ACSNET C:US D:01/10/93 1:73 2:685 3:101 192.108.146 UOCHBNET C:CS D:01/11/93 1:513 2:1800 192.108.147 IMGNET C:CS D:01/11/93 1:513 2:1800 192.147.179 NWNET29 C:US D:01/10/93 1:73 2:685 3:101 192.149.2 CCISHP C:US D:01/10/93 1:93 192.152.191 CIC C:US D:01/10/93 1:1206 2:204 192.154.56 RJRT-NET C:US D:01/10/93 1:81 2:1327 192.154.57 NETLINK-NET C:US D:01/10/93 1:81 2:1327 192.154.58 TBIRD-NET C:US D:01/10/93 1:81 2:1327 192.154.59 FSUFAY-NET C:US D:01/10/93 1:81 2:1327 192.154.60 LRC-NET C:US D:01/10/93 1:81 2:1327 192.155.11 CMP-COM3 C:US D:01/11/93 1:174 192.155.12 CMP-COM4 C:US D:01/11/93 1:174 192.155.13 CMP-COM5 C:US D:01/11/93 1:174 192.155.14 CMP-COM6 C:US D:01/11/93 1:174 192.155.15 CMP-COM7 C:US D:01/11/93 1:174 192.155.16 CMP-COM8 C:US D:01/11/93 1:174 192.155.23 CMP-COM15 C:US D:01/11/93 1:174 192.155.24 CMP-COM16 C:US D:01/11/93 1:174 192.203.71 FISONS-1 C:US D:01/11/93 1:701 2:702 3:279 192.203.72 FET-C-004 C:US D:01/11/93 1:701 2:702 3:279 192.203.73 FET-C-005 C:US D:01/11/93 1:701 2:702 3:279 192.203.247 CHIANGMAI C:TH D:01/11/93 1:701 2:702 192.204.6 CHATHAM C:US D:01/10/93 1:1206 2:204 192.231.177 PTSEM-1 C:US D:01/11/93 1:97 192.231.178 PTSEM-2 C:US D:01/11/93 1:97 192.231.214 PACE C:US D:01/11/93 1:97 192.234.106 LVHTN C:US D:01/10/93 1:1206 2:204 192.234.182 CDBS2000 C:US D:01/11/93 1:19 2:568 192.239.40 GVILLE-NET C:US D:01/11/93 1:279 2:86 193.112.251 MPREAD C:GB D:01/11/93 1:701 2:1800 198.3.1 FET-C-001 C:US D:01/11/93 1:701 2:702 3:279 198.3.2 FNET-C-002 C:US D:01/11/93 1:701 2:702 3:279 198.3.3 FET-C-003 C:US D:01/11/93 1:701 2:702 3:279 198.22.45 BEREAN C:US D:01/10/93 1:93 Network IP: 138.113 Network Name: ANASAZI Location: Anasazi, Inc., 7500 Dreamy Draw Drive, Suite 120, Phoenix, AZ 85020, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 141.131 Network Name: CIRRUS Location: Cirrus Logic Inc., 1463 Centre Point Drive, Milpitas, CA 95035, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 151.141 Network Name: ETSUNET Location: East Tennessee State University, Computer Services, Box 24, 340-A, Johnson City, TN 37614, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 161.134 Network Name: EMPROS Location: Empros Systems International, 2300 Berkshire Ln. N., Plymouth, MN 55441, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT 4:555 Minnesota Supercomputer Center Network (MSCNet) Network IP: 162.70 Network Name: AMSWAN4 Location: American Management Systems, Inc., 1777 N. Kent Street, Arlington, VA 22209, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 164.42 Network Name: UIPRNET-B Location: Interamerican University of Puerto Rico, Central Administration, P.O. Box 363255, San Juan, PR 00936-3255, USA Country Code: US 1:86 SURANET Regional Network (College Park) 2:279 SURANET Regional Network (Georgia Tech) Network IP: 192.42.145 Network Name: UW-ACSNET Location: University of Washington, Academic Computing Services, 3737 Brooklyn Avenue, NE, Seattle, WA 98105, USA Country Code: US 1:73 NorthWestNet Regional Network 2:685 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.108.146 Network Name: UOCHBNET Location: Institute of Organic Chemistry and Biochemistry, Flemingovo nam. 2, 166 10 Prague 6, CZECHO-SLOVAKIA Country Code: CS 1:513 EASInet / CERN 2:1800 ICM (FIX-East) Network IP: 192.108.147 Network Name: IMGNET Location: Institute of Molecular Genetics, Flemingovo nam. 2, 166 10 Prague 6, CZECHO-SLOVAKIA Country Code: CS 1:513 EASInet / CERN 2:1800 ICM (FIX-East) Network IP: 192.147.179 Network Name: NWNET29 Location: NorthWestNet, 15400 SE 30th Place, Suite 202, Bellevue, WA 98007, USA Country Code: US 1:73 NorthWestNet Regional Network 2:685 NorthWestNet Regional Network 3:101 NorthWestNet Regional Network Network IP: 192.149.2 Network Name: CCISHP Location: Columbia College, 1001 Rogers Street, Columbia, MO 65216, USA Country Code: US 1:93 MIDnet Network IP: 192.152.191 Network Name: CIC Location: The Counsil of Independent Colleges, One Dupont Circle, Suite 320, Washington, DC 20036, USA Country Code: US 1:1206 PSCNET Regional Network 2:204 PSCNET Regional Network Network IP: 192.154.56 Network Name: RJRT-NET Location: R J Reynolds Tobacco Co., 611-12 Reynolds Blvd., PO Box 2959, Winston-Salem, NC 27102, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.57 Network Name: NETLINK-NET Location: Netlink, Inc., 3214 Spring Forest Road, Raleigh, NC 27604, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.58 Network Name: TBIRD-NET Location: Thunderbird Technologies, Inc., 1000 Perimeter Park Drive, Suite G, Morrisville, NC 27560, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.59 Network Name: FSUFAY-NET Location: Fayetteville State University, 1200 Murchison Road, Fayetteville, NC 28301-4298, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.60 Network Name: LRC-NET Location: Lenoir-Rhyne College, Hickory, NC 28603, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.155.11 Network Name: CMP-COM3 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.12 Network Name: CMP-COM4 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.13 Network Name: CMP-COM5 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.14 Network Name: CMP-COM6 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.15 Network Name: CMP-COM7 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.16 Network Name: CMP-COM8 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.23 Network Name: CMP-COM15 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.155.24 Network Name: CMP-COM16 Location: CMP Publications Inc., 600 Community Drive, Manhasset, NY 11030, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.203.71 Network Name: FISONS-1 Location: Fisons Corporation, PO Box 1710, 755 Jefferson Road, Rochester, NY 14623, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.72 Network Name: FET-C-004 Location: Furukawa Electric Technologies, Inc., 900 Lafayette Street, Suite 401, Santa Clara, CA 95050, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.73 Network Name: FET-C-005 Location: Furukawa Electric Technologies, Inc., 900 Lafayette Street, Suite 401, Santa Clara, CA 95050, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.247 Network Name: CHIANGMAI Location: Chiangmai University, Computer Service Center, Chiangmai 50002, THAILAND Country Code: TH 1:701 Alternet 2:702 Alternet Network IP: 192.204.6 Network Name: CHATHAM Location: Chatham College, Woodland Road, Pittsburg, PA 15232, USA Country Code: US 1:1206 PSCNET Regional Network 2:204 PSCNET Regional Network Network IP: 192.231.177 Network Name: PTSEM-1 Location: Princeton Theological Seminary, 64 Mercer Street, Princeton, NJ 08540, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.231.178 Network Name: PTSEM-2 Location: Princeton Theological Seminary, 64 Mercer Street, Princeton, NJ 08540, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.231.214 Network Name: PACE Location: Pace University Law School, 78 North Broadway, Preston Hall, Room 27A, White Plains, NY 10603, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.234.106 Network Name: LVHTN Location: Lehigh Valley Hospital, Information Services, 2024 Lehigh Street, Allentown, PA 18103, USA Country Code: US 1:1206 PSCNET Regional Network 2:204 PSCNET Regional Network Network IP: 192.234.182 Network Name: CDBS2000 Location: LOGICON, 1831 Wiehle Avenue, Reston, VA 22090, USA Country Code: US 1:19 Milnet (FIX-East) 2:568 Milnet (FIX-West) Network IP: 192.239.40 Network Name: GVILLE-NET Location: Greenville Technical College, P.O. Box 5616, Greenville, SC 29606, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 193.112.251 Network Name: MPREAD Location: MasPar Computer Ltd, 8 Commerce Park, Brunel Road, Theale, Reading RG7 4AB, UNITED KINGDOM Country Code: GB 1:701 Alternet 2:1800 ICM (FIX-East) Network IP: 198.3.1 Network Name: FET-C-001 Location: Furukawa Electric Technologies, Inc., 900 Lafayette Street, Suite 401, Santa Clara, CA 95050, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 198.3.2 Network Name: FNET-C-002 Location: Furukawa Electric Technologies, Inc., 900 Lafayette Street, Suite 401, Santa Clara, CA 95050, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 198.3.3 Network Name: FET-C-003 Location: Furukawa Electric Technologies, Inc., 900 Lafayette Street, Suite 401, Santa Clara, CA 95050, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 198.22.45 Network Name: BEREAN Location: Berean Academy, 201 South Main, Elbing, KS 67041, USA Country Code: US 1:93 MIDnet The following T3 routers have also been added: AS Number: 73 AS Notes: NorthWestNet Regional Network AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.143 - ENSS143 University of Washington Gate: 192.147.179.10 - hoover.cac.washington.edu ENSS 143 / University of Washington ***************************************************************** The configuration reports which reflect today's update will be available for anonymous ftp on nis.nsf.net by 08:00 EST: configuration reports -- nis.nsf.net:nsfnet/announced.networks: ans_core.now as-as.now as-gw.now as-site.now as.now country.now gate-gw.now net-comp.now net-ter.now net-net.now netcount.now non-us.now nss-as.now nss-gw.now nss.now networks sorted by AS -- nis.nsf.net:nsfnet/announced.networks: nets.as_<AS number> NSS routing software configuration files -- nis.nsf.net:nsfnet/backbone.configuration: nss<NSS number>.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 skw(a)merit.edu --Riaz Taherzadeh-Yazdian NSFNET/ANSNET rty(a)ans.net

1 0

December Backbone Engineering Report
by Mark Knopper 11 Jan '93

11 Jan '93

Hi. This report will appear in this month's Internet Monthly Report. Mark ANSNET/NSFNET Backbone Engineering Report December 1992 Jordan Becker, ANS Mark Knopper, Merit becker(a)ans.net mak(a)merit.edu Network Status Summary ====================== Following the T1 backbone disconnection on Dec. 2nd, the T3 is now supporting all NSFNET services. A 2nd ethernet interface was installed in ENSS136 to support interim connectivity to the MAE-East facility. The former T1 backbone class B address (129.140) was returned to the NIC. CA*Net peer router hardware reconfigurations will be completed in January to allow direct T3 network peering. A plan has been developed to dismantle and remove the RT routers at regional sites. Following the software changes resulting from instabilities observed during the MBONE multicasts in November, the T3 backbone routing stability has been very good in December. Daily reports are now generated on internal and external peer network routing stability. Seven new RS960 FDDI interfaces were installed on ENSS nodes in December. Reliability and performance of the FDDI hardware has been very good. Backbone Traffic and Routing Statistics ======================================= The total inbound packet count for the T3 Backbone (measured using SNMP interface counters) was 22,009,352,089 up 5.0% from November. As of December 31, the number of networks configured in the NSFNET Policy Routing Database was 8561 for the T3 backbone. Of these, 1760 were never announced to the T3 backbone. The maximum number of networks announced to the T3 backbone during the month (from samples collected every 15 minutes) was 6187. Average announced networks on 12/31 were 6154. Previously when the T1 Backbone was operational the overall average number of networks announced via the primary configured AS path was around 88%. Since the T1 Backbone was dismantled this average has gone to around 95%. Graphs of this information are available for anonymous ftp on merit.edu, in pub/nsfnet/offnet, as postscript files. Routing Software and Stability on the T3 Network ================================================ Higher than usual MBONE activity in November resulted in exterior routing instabilities and routing instability internal to ANSnet. Following the immediate corrective actions that were taken in November, a number of software changes were made in December. Changes to the RS960 microcode and efficiency improvements in the routing software have resulted in improved ANSnet internal routing stability (regardless of the presence of external route flapping). The MBONE participants have made changes to route MBONE traffic over the T3 backbone whenever possible, resulting in improved routing stability within certain US regional networks. Detailed reports of internal ANSnet and external peer network routing instabilities are now generated on a daily basis. The ANSnet internal report attempts to summarize outages based on number and duration of the IBGP disconnects. The program that generates this report looks at IBGP disconnects in a short time window. It tries to assign the outage to the node with the most disconnects, and then eliminate all disconnects on other machines associated with that router. If after eliminating disconnects related to the router assigned to the outage, more disconnects remain in the same time window, the process is repeated, assigning secondary and tertiary responsibility for the outage and so on until all disconnects are accounted for. The time window is extended to cover all disconnects that are not separated by more than a five minute period in which there is no change to internal routing in the network. Using this method, data sufficient to generate reports on internal ANSnet routing stability has been collected continuously since October '92. Over the course of December '92, all but two ANSnet nodes reported 99.0% internal routing stability (no changes to internal routing). These two nodes reported 98.9% stability, mostly due to a problem early in December. Most nodes reported 99.0% to 99.5% stability. Two reported better than 99.5% stability. The vast majority of this instability is due to the regular configuration updates and scheduled maintenance. With the dismantling of the T1 backbone, activities are underway to reduce the duration of time required to process the bi-weekly router configuration runs, and scheduled maintenance. Similar data on external routing stability has been collected continuously since December '92. The external routing stability reports will record an external route which is withdrawn from the ANSnet due to: (1) an EGP route timing out (not being advertised by an external peer), (2) an explicit BGP unreachable received from an external peer, (3) the loss of an external EGP or BGP session that is not accompanied by loss of internal IBGP sessions. Excluded are the following cases: (1) we do not observe changes in the next hop at the ENSS, (2) the route is replaced by another route on the same ENSS, (3) a route is lost and backed up by another route on the same ENSS, (4) connectivity is lost due to ANSnet internal problems (e.g. configuration runs or other). Some of this data has already been shared with specific regional networks to get feedback. In January, these reports will be fully automated and distributed to peer networks which are advertising networks that are withdrawing reachability excessively (e.g. exhibiting great instability). After the recent FIX-East reconfiguration, a bug in rcp_routed was observed that would result in an ENSS installing a route locally that had previously been advertsized by a peer, where the route was rejected on the ENSS due to policy constraints (no NACR request). Such a route would incorrectly be installed on the ENSS (but not advertised) when the destination becomes completely unreachable. On ENSS136, the existence of multiple peers coupled with the use of default routing by some peers could form a routing loop when this occurs. This problem in the rcp_routed software has been corrected and is deployed on ENSS136. Deployment of the same changes across the rest of the ANSnet is scheduled for early January. Another planned change to rcp_routed in January involves fixing the metric_in function for EGP. This will allow regional peer routers to be able to have an EGP session with the same ENSS on two different interfaces (FDDI and ethernet) and prefer the FDDI via metrics. RS960 FDDI Deployment Status ============================ During the month of December, we installed RS960 FDDI adapters at the following 7 locations: Boston (E134), Argonne (E130), FIX-E (E145), Houston (E139), Ithaca (E133), FIX-W (E144), Seattle (E143). Domain Name Service for ANSnet ============================== In December, ANS made two adjustments to the DNS administration of the ANS backbone. First, the "t3.nsf.net" domain was renamed to "t3.ans.net", and second, we added geographical designators to all CNSS nodes. ENSS names were not changed other than in being moved to the "t3.ans.net" domain. The following excerpt of a traceroute from ANS Elmsford to Merit in Ann Arbor illustrates the ANSnet DNS conventions. 3 t1-2.New-York-cnss35.t3.ans.net (140.222.35.4) 7 ms 7 ms 7 ms ANS Elmsford's ENSS is attached to T1 Port #2 on CNSS35 (a T1 concentrator in the New York POP). 5 t3-3.New-York-cnss32.t3.ans.net (140.222.32.4) 8 ms 8 ms 8 ms 6 t3-1.Cleveland-cnss40.t3.ans.net (140.222.40.2) 23 ms 22 ms 24 ms The T3 point-to-point line between the New York POP and the Cleveland POP is on these two T3 ports on CNSS32 and CNSS40. 7 t3-0.Cleveland-cnss41.t3.ans.net (140.222.41.1) 22 ms 23 ms 23 ms The Ann Arbor ENSS is attached to T3 Port #0 on CNSS41 (the T3 concentrator in the Cleveland POP). 8 t3-0.enss131.t3.ans.net (140.222.131.1) 30 ms 27 ms 27 ms 9 merit.edu (35.1.1.42) 29 ms 39 ms 31 ms The merit.edu machine is one hop from ENSS131 which is physically located in a University of Michigan building. While every effort was taken to ensure the accuracy of the DNS data, typos and glitches may have crept in. If you notice any problems, please report them by sending mail to hostmaster(a)ans.net. OSI Support on T3 Backbone ========================== In early December, OSI CLNP forwarding over the T3 backbone was configured via encapsulation of CLNP over IP packets using the EON method (RFC1070) until native CLNP switching services are available on the T3 routers. One RT from the T1 NSS node at each midlevel/peer site is being used for the EON encapsulation function. It is our intention to keep this RT and one other for statistics collection purposes running at each site. CA*Net Reconfiguration Status ============================= CA*Net is working with Merit and ANS to complete their plan to change their connections to the US (at Seattle, Ithaca and Princeton) so that the US nodes will run the CA*Net RT kernel and become logically part of the Canadian routing domain. This project has not yet been completed, and so currently the three NSS nodes from the T1 Backbone (but without the T1 circuits) are being used to route traffic between CA*Net and NSFNET. Once the software installation is complete the circuits will be moved over to these RTs and the full NSS noes will be disabled. AIX 3.2 Migration Plan ====================== System testing continued in December for the new AIX 3.2 operating system for the RS/6000 routers. This software will be installed on the T3 test network in January for final system testing prior to deployment in early February. GATED Routing Software Development ================================== Work continued on the development of GATED as replacement for rcp_routed software on the T3 backbone. The same Interior Gateway Protocol (IGP) used by rcp_routed will be supported initially on GATED as a transitional measure to simplify the deployment of GATED. Full IS-IS integrated routing will follow in GATED, along with BGP4 with CIDR routing capability. New ANSnet Nodes Installed ========================== ENSS Customer Access Date Active ---- -------- ------ ----------- 206 CERN T1 12-01-92 187 CIX T1 12-04-92 209 H.W. Wilson T1 12-04-92 207 Siemens 56k 12-07-92 177 N.Y. Bank T1 12-09-92 199 Dept. of Trans. 56k 12-11-92 179 MCNC Backup 56k 12-15-92 Cisco PROM Upgrade on ANSNET ============================ We are finalizing tests that will allow us to upgrade the software level on all ANSnet Cisco routers to 9.0(3). This will fix several bugs that currently exist on the current 8.3.X that is installed across the network.

1 0