December 1992 - Test - lists.nanog.org

New template.net NACR proposed
by Mark Knopper 18 Dec '92

18 Dec '92

Hi. We have substantially revised the Network Announcement Change Request (NACR) template, as part of our effort to automate the policy routing data base update and configuration process. Please give us your comments on this new template, and we would like to start using it on January 1. Mark [nis.nsf.net:nsfnet/announced.networks/template.net] Version 6.5 18 Dec 1992 NSFNET Configuration Request Template for the NSFNET policy-based routing data base ---- Network Announcement Change Request ---- This document contains information needed for NSFNET regionals, midlevels, and peer networks to add or modify network numbers and routing information in Merit's NSFNET policy-based routing data base. Due to the rapid increase of network numbers in the database, it has become necessary to design and implement a system where requests are automatically parsed to eliminate the need for a similarly increasing labor pool to do the data entry! The template form contained in this document represents the first in a series steps that are planned to streamline the database entry process. While we believe this automation will make the database process for network number registration more efficient, it is also our intention that it remains a cooperative process between Merit and the regional technical network administrators. If you have comments on this document or the template it contains, please send them to ie(a)merit.edu, the Merit/NSFNET Internet Engineering group. General discussion of this template or other NSFNET routing issues can be carried out on the list regional-techs(a)merit.edu. Real-time immediate problems should be reported to trouble(a)noc.ans.net. General feedback to Merit for NSFNET service issues or problem escalation should be sent to nsfnet(a)merit.edu. The Merit/NSFNET Internet Engineering Group 1.0 GENERAL INSTRUCTIONS ------------------------ 1.1 Configuration Instructions -------------------------- Configuration requests should be submitted by e-mail to nsfnet-admin(a)merit.edu by the designated Routing Administrators for the Autonomous Systems of the NSFNET. The text of the message should contain the template given in section 2.0 of this document. The first word of the subject line of the message should be the first IP number for which you are requestiong action. 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 period. Requests should be received by noon (Eastern time) on Monday (for Tuesday morning configs) and noon (Eastern time) on Thursday (for Friday morning configs). Merit will request separate authorization from the National Science Foundation on a per-net basis to allow non-US network numbers to be added. Additions of non-US networks therefore may result in additional delays. Merit maintains mail lists for each Autonomous System (AS) announced on the backbone in the syntax: as<number>@merit.edu. In the interest of improving turnaround time for configuration requests that involve inbound announcements from multiple organizations, we ask that all of the appropriate AS mailing groups be copied when you submit the original request to nsfnet-admin(a)merit.edu. We also ask that the copied Routing Administrators reply to all with their approvals or denials of the requested addition(s) or change(s). An Internet network number must have been assigned by the Network Information Center (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 the NIC. 1.2 Template Instructions --------------------- This form will be read by an automatic parser and bounced back to you if it is unparsable or if required data is missing. Thus, if you wish to add a comment or for other reasons have your request read by a human please replace the word "Yes" with "No" in the "Autoparse:" line at the beginning of the NACR. The organizational information you supply with this form will be checked against that held by the NIC in an attempt to keep our network information synchronized with the NIC. The NACR template information consists of global NACR information followed by one or more network number entries. The global NACR information applies to each network number entry that follows it. However, any line of the global information can be overridden for a particular network by specifying that line in the net number entry. For example, the global information may indicate "Net_Country Code: US" but one net you are submitting might be located in Canada. Thus, you may overide US by including the line: "Net_Country_Code: CA" in the net number entry. See example 4, below (in section 3.0). 2.0 NACR TEMPLATE ----------------- ******************************* CUT HERE ********************************** ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone service agree that traffic from these networks that will transit the NSFNET backbone service complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. %begin nsfnet nacr v6.5% Autoparse: Yes %global nacr info% Organization_Name: Street_Address_1: Street_Address_2: Street_Address_3: City: State_or_Province: Postal_Code: Org_Country_Code: Net_Country_Code: Intended_Use_of_Network(C,E,G,M,R,O): Educational_Organization_Type(4year,4year+,2year,K-12): Backbone: T3 Action_being_requested(A/D/C): Inbound_Announcements_to_NSFNET: Comments: %end global nacr info% %begin network entries% Network_Number: Network_Name: %end network entries% %end nsfnet nacr% ******************************* CUT HERE ********************************** 3.0 EXPLANATION OF SPECIFIC FIELDS IN THE TEMPLATE --------------------------------------------------- Organization responsible for network: The name and address of the organization to which the network belongs should be listed under this section. The country code requested should comply with the two letter ISO 3166 codes. Net_Country Code: This is the country where the network is located (vs. the organization that is responsible for the net). If the net spans multiple countries please try to pick the one which you feel best represents the net. The country code requested on this line must comply with the two letter ISO 3166 codes. A listing of these codes may be ftp'ed from nis.nsf.net:nsfnet/announced.networks/country.codes. Intended Use of Network: Indicate type from this list: Commercial (C), Education (E), Government - non-military (G), Government - military (M), Research (R), Other (O). Educational Organization Type: If the intended use type is Educational, specify the type of educational organization. It is preferred that the Carnegie Classification code be specified here, but if that is not known, indicate broad type: 4year, 4year+, 2year, K-12. The Carnegie Classification codes are included below. Backbone: T3. (Just to avoid any ambiguity. ;-) Action being requested (A/D/C): This line must indicate if the inbound announcements you are requesting for this network will be a change to existing inbound announcements to the NSFNET (C), a compete deletion of all inbound announcements to the NSFNET (D), or if this request is to add a network that is not currently being announced to the NSFNET (A). Inbound Announcements to NSFNET: This input line(s) should be filled out with the Autonomous System numbers which will announce the network(s). Any number of ASes may be listed on this line; at least one is required. The ASes should be listed in order of preference, with the most highly preferred AS listed first, as in 233 177 266. 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 toward the specified network. Comments: Comment lines are most useful when the autoparse option is not in use, though the routing consultants will generally read these comments in the normal process of approving database updates. Please see the first paragraph of the NACR for information on bypassing the parser. Please precede EACH comment line with the "Comments:" string. Network Name: The offical name of the network, as it is registered at the NIC (see whois server), should appear on this input line. 4.0 EXAMPLES ------------ EXAMPLE 1: SINGLE NET ========== 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 the T3 network. Their Network Announcement Change Request follows: ----------------------------------------------------------------------------- ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone service, agree that traffic from these networks that will transit the NSFNET backbone service complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. %begin nsfnet nacr v6.5% Autoparse: Yes %global nacr info% Organization_Name: Merit Network, Inc. Street_Address_1: 1075 Beal Avenue Street_Address_2: Street_Address_3: City: Ann Arbor State_or_Province: MI Postal_Code: 48109 Org_Country_Code: US Net_Country_Code: US Intended_Use_of_Network(C,E,G,M,R,O): E Educational_Organization_Type(4year,4year+,2year,K-12): 4year+ Backbone: T3 Action_being_requested(A/D/C): A Inbound_Announcements_to_NSFNET: 233 177 Comments: %end global nacr info% %begin network entries% Network_Number: 141.214 Network_Name: UMNET4 %end network entries% %end nsfnet nacr% ----------------------------------------------------------------------------- EXAMPLE 2: MULTIPLE NETS, same organization, same inbound announcements, same country locations. ============================================================= Suppose network 192.41.229 (NBB11), 192.41.230 (NBB12) and 192.41.231 (NBB13) wished 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 the T3 network. Their Network Announcement Change Request follows: ----------------------------------------------------------------------------- ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone service, agree that traffic from these networks that will transit the NSFNET backbone service complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. %begin nsfnet nacr v6.5% Autoparse: Yes %global nacr info% Organization_Name: Merit Network, Inc. Street_Address_1: 1075 Beal Avenue Street_Address_2: Street_Address_3: City: Ann Arbor State_or_Province: MI Postal_Code: 48109 Org_Country_Code: US Net_Country_Code: US Intended_Use_of_Network(C,E,G,M,R,O): E Educational_Organization_Type(4year,4year+,2year,K-12): 4year+ Backbone: T3 Action_being_requested(A/D/C): A Inbound_Announcements_to_NSFNET: 233 177 Comments: %end global nacr info% %begin network entries% Network_Number: 192.41.229 Network_Name: NBB11 Network_Number: 192.41.230 Network_Name: NBB12 Network_Number: 192.41.231 Network_Name: NBB13 %end network entries% %end nsfnet nacr% ----------------------------------------------------------------------------- EXAMPLE 3: Multiple nets, same organization, DIFFERING INBOUND ANNOUNCEMENTS, same country locations. =================================================== Suppose network 192.41.229 (NBB11), 192.41.230 (NBB12) and 192.41.231 (NBB13) wished to be announced to the NSFNET. NBB11 and NBB12 wish to have AS 233 as their PRIORITY 1 path and AS 177 as their PRIORITY 2 path on the T3 network while NBB13 wishes to have AS 177 as their PRIORITY 1 path and AS 233 as their PRIORITY 2 path. All three nets are owned by MERIT. Their Network Announcement Change Request follows: ----------------------------------------------------------------------------- ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone service, agree that traffic from these networks that will transit the NSFNET backbone service complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. %begin nsfnet nacr v6.5% Autoparse: Yes %global nacr info% Organization_Name: Merit Network, Inc. Street_Address_1: 1071 Beal Avenue Street_Address_2: Street_Address_3: City: Ann Arbor State_or_Province: MI Postal_Code: 48109 Org_Country_Code: US Net_Country_Code: US Intended_Use_of_Network(C,E,G,M,R,O): E Educational_Organization_Type(4year,4year+,2year,K-12): 4year+ Backbone: T3 Action_being_requested(A/D/C): A Inbound_Announcements_to_NSFNET: 177 233 Comments: %end global nacr info% %begin network entries% Network_Number: 192.41.229 Network_Name: NBB11 Network_Number: 192.41.230 Network_Name: NBB12 Network_Number: 192.41.231 Network_Name: NBB13 Inbound_Announcements_to_NSFNET: 233 177 %end network entries% %end nsfnet nacr% ----------------------------------------------------------------------------- EXAMPLE 4: Multiple nets, same organization, differing inbound announcements, DIFFERING COUNTRY LOCATIONS. ==================================================== Suppose network 192.41.229 (NBB11), 192.41.230 (NBB12) and 192.41.231 (NBB13) wished to be announced to the NSFNET. NBB11 and NBB12 wish to have AS 233 as their PRIORITY 1 path and AS 177 as their PRIORITY 2 path on the T3 network while NBB13 wishes to have AS 177 as their PRIORITY 1 path and AS 233 as their PRIORITY 2 path. All three nets are owned by MERIT but NBB12 is located in Canada. Their Network Announcement Change Request follows: ----------------------------------------------------------------------------- ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone service, agree that traffic from these networks that will transit the NSFNET backbone service complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. %begin nsfnet nacr v6.5% Autoparse: Yes %global nacr info% Organization_Name: Merit Network, Inc. Street_Address_1: 1071 Beal Avenue Street_Address_2: Street_Address_3: City: Ann Arbor State_or_Province: MI Postal_Code: 48109 Org_Country_Code: US Net_Country_Code: US Intended_Use_of_Network(C,E,G,M,R,O): E Educational_Organization_Type(4year,4year+,2year,K-12): 4year+ Backbone: T3 Action_being_requested(A/D/C): A Inbound_Announcements_to_NSFNET: 233 177 Comments: %end global nacr info% %begin network entries% Network_Number: 192.41.229 Network_Name: NBB11 Network_Number: 192.41.230 Network_Name: NBB12 Net_Country_Code: CA Network_Number: 192.41.231 Network_Name: NBB13 Inbound_Announcements_to_NSFNET: 177 233 %end network entries% %end nsfnet nacr% ----------------------------------------------------------------------------- EXAMPLE 5: Multiple nets, DIFFERING ORGANIZATIONS, differing inbound announcements, same country locations. ========================================================= Suppose network 192.41.229 (NBB11), 192.41.230 (NBB12) and 192.41.231 (NBB13) wished to be announced to the NSFNET. NBB11 and NBB12 wish to have AS 233 as their PRIORITY 1 path and AS 177 as their PRIORITY 2 path on the T3 network while NBB13 wishes to have AS 177 as their PRIORITY 1 path and AS 233 as their PRIORITY 2 path. Furthermore, NBB13 is owned by UMICH-UM while NBB11 and NBB12 are owned by MERIT. Their Network Announcement Change Request follows: ----------------------------------------------------------------------------- ---- Network Announcement Change Request ---- The administrators of the following networks for which access is requested to the NSFNET backbone service, agree that traffic from these networks that will transit the NSFNET backbone service complies with the "NSFNET BACKBONE SERVICES ACCEPTABLE USE POLICY" dated June 1992. %begin nsfnet nacr v6.5% Autoparse: Yes %global nacr info% Organization_Name: Merit Network, Inc. Street_Address_1: 1071 Beal Avenue Street_Address_2: Street_Address_3: City: Ann Arbor State_or_Province: MI Postal_Code: 48109 Org_Country_Code: US Net_Country_Code: US Intended_Use_of_Network(C,E,G,M,R,O): E Educational_Organization_Type(4year,4year+,2year,K-12): 4year+ Backbone: T3 Action_being_requested(A/D/C): A Inbound_Announcements_to_NSFNET: 233 177 Comments: %end global nacr info% %begin network entries% Network_Number: 192.41.229 Network_Name: NBB11 Network_Number: 192.41.230 Network_Name: NBB12 Network_Number: 192.41.231 Network_Name: NBB13 Inbound_Announcements_to_NSFNET: 177 233 Organization_Name: University of Michigan Street_Address_1: 101 State Street Street_Address_2: Street_Address_3: City: Ann Arbor State_or_Province: MI Postal_Code: 48109 Org_Country_Code: US %end network entries% %end nsfnet nacr% ----------------------------------------------------------------------------- 5.0 CARNEGIE CLASSIFICATION CODES --------------------------------- Code Description ---- ----------- 2YR Community Colleges, etc. ART Fine Arts BUS Business Colleges C1 Comprehensive I (liberal arts, engineering, etc. with some master's programs) C2 Comprehensive II (fewer programs/degrees than C1) COR ? D1 Doctoral I (doctoral programs, but not much research) D2 Doctoral II (fewer programs than D1) ENG Engineering HLT Health (pharmacy, dentistry, nursing, chiropractic, etc.) K12 Kindergarten through 12th Grade (not an official Carnegie Code) LA1 Liberal Arts I LA2 Liberal Arts II (fewer programs than LA1) LAW Law MED Medicine N/A Not Available OTH Other R1 Research I (broad spectrum research and doctoral programs) R2 Research II (fewer programs than R1) REL Religious TEA Teachers Colleges 6.0 BNF GRAMMAR FOR NACR TEMPLATE --------------------------------- This section contains the Backus-Naur Form for the formal syntax of the NACR template. This syntax is being used for the parser that will interpret incoming requests, and is given here since it may be useful for those who want to generate NACR templates automatically for submission. Note on syntax for syntax: Phrases that are quoted are literal text. Phrases in angle brackets <> are names of phrases that are defined in this syntax. Phrases in square brackets [] are optional. <nacr> ::= "%begin nsfnet nacr v6.5%\n" <preamble> [<global nacr info>] [<network number info>] "%end nsfnet nacr%" <global nacr info> ::= "%global nacr info%\n" <routing request info> "%end global nacr info%\n" <network number info> ::= "%begin network entries%\n" <network number list> "%end network entries%\n" <network number list> ::= <single net num> [<network number list>] <single net num> ::= "Network_Number:" <ip_number> "\n" "Network_Name:" <net name> "\n" [<routing request info>] "\n" "\n" <routing request info> ::= [<organization info>] [<network country code>] [<intended use>] [<educational org status>] [<backbone name>] [<requested action>] [<inbound announcements>] [<comments>] <preamble> ::= "Autoparse:" ("Yes" | "No") "\n" <ip_number> ::= <decimal> ["." <ip_number>] <net name> ::= <string> <string> ::= <A-Za-z0-9 >+ <organization info> ::= "Organization_Name:" <string> "\n" ["Street_Address_1:" <string> "\n"] ["Street_Address_2:" <string> "\n"] ["Street_Address_3:" <string> "\n"] ["City:" <string> "\n"] ["State_or_Province:" <string> "\n"] ["Postal_Code:" <string> "\n"] ["Org_Country_Code:" <iso3166string> "\n"] <intended use> ::= "Intended_Use_of_Network(C,E,G,M,R,O):" ( "C" | "Commercial" | "E" | "Education" | "G" | "Government" | "M" | "Military" | "R" | "Research" | "O" | "Other" ) "\n" <backbone name> ::= "Backbone: T3\n" <requested action> ::= "Action_being_requested(A/D/C):" ("A" | "Add" | "C" | "Change" | "D" | "Delete") "\n" <inbound announcements> ::= "Inbound_Announcements_to_NSFNET:" <metric_AS list> "\n" <metric_AS list> ::= <decimal> [<metric_AS list>] <network country code> ::= "Net_Country_Code: " <iso3166string> "\n" <comments> ::= <comment lines> <comment lines> ::= "Comment: " <string> "\n" [<comment lines>]

1 0

November Backbone Engineering Report
by Mark Knopper 18 Dec '92

18 Dec '92

This report is included in this month's Internet Monthly Report. Mark ANSNET/NSFNET Backbone Engineering Report November 1992 Jordan Becker, ANS Mark Knopper, Merit becker(a)ans.net mak(a)merit.edu Network Status Summary ====================== All remaining T1 backbone traffic was cutover to the T3 backbone and the T1 backbone network was turned off on December 2nd. There were network stability problems observed at several sites prior to, and during the IETF MBONE video/audio multicast event in November. The problems were mostly due to increased traffic, and the inefficient processing of source route packets that caused routing instabilities. Software changes have been deployed on the T3 backbone to reduce the routing instability problems due the MBONE, and to improve the efficiency for downloading large routing updates to the packet forwarding interfaces on the T3 routers. New RS960 FDDI interfaces are being scheduled for deployment to selected T3 ENSS nodes in December. Performance measurements over the T3 network are proceeding at sites that already have FDDI interfaces installed. Backbone Traffic and Routing Statistics ======================================= The total inbound packet count for the T1 network was 3,589,916,970, down 14.8% from October. 598,015,432 of these packets entered from the T3 network. The total inbound packet count for the T3 network was 20,968,465,293, up 10.7% from October. 134,269,388 of these packets entered from the T1 network. The combined total inbound packet count for the T1 and T3 networks (less cross network traffic) was 23,826,097,443 up 5.9% from October. As of November 30, the number of networks configured in the NSFNET Policy Routing Database was 7833 for the T1 backbone, and 7581 for the T3 backbone. Of these, 1642 networks were never announced to the T1 backbone and 1602 were never announced to the T3 backbone. For the T1, the maximum number of networks announced to the backbone during the month (from samples collected every 15 minutes) was 5772; on the T3 the maximum number of announced networks was 5548. Average announced networks on 11/30 were 5707 to T1, and 5495 to T3. T1 NSFNET Backbone Turned Off ============================= The activities required to turn off the T1 backbone were completed during November and the network was officially turned off by disabling routing on the NSS nodes starting at 00:01 EST on 12/2. Several actions were taken in advance of the routing shutdown including installation of the T1 ENSS206 at CERN in Switzerland, reconfiguration of the T1 NSS routers to gateway traffic between CA*net and NSFNET, the deployment of the EON software for OSI encapsulation over IP, and the final installation of T1 backup circuit infrastructure connecting T3 ENSS nodes to secondary CNSS nodes. Remaining Network Cutovers to T3 -------------------------------- AS 68, Los Alamos National Laboratory networks and AS22, operated by MilNet at the San Diego Supercomputer Center were cutover to use the T3 backbone in November. A new T1 ENSS (ENSS206) was installed in CERN, Switzerland to provide connectivity to the T3 backbone for EASInet. ENSS206 is interconnected via a T1 circuit with CNSS35 in New York City. The ENSS was initially configured with less than the recommended memory, and had to be upgraded to overcome some performance problems. Other than that, the installation went smoothly, and EASInet traffic was cutover to the T3 backbone on 12/1. The NSS nodes in Seattle, Ithaca and Princeton were converted for use by CA*net to allow CA*net to peer with the T3 network until the longer term GATED hardware peer configurations are available. The E-PSP nodes for CA*net will be converted to run the CA*net software and operate as part of CA*net's domain. These nodes will run GATED and exchange routes via BGP with the T3 ENSS. OSI Support on T3 Backbone -------------------------- 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. RT PSP routers were configured as EON encapsulators at most regional and peer networks. CLNP traffic on the regional is first routed to the EON machine. The EON machine encapsulates the CLNP packet in an IP packet. The EON machine will send the IP packet to the remote EON machine that is associated with the destination NSAP address prefix in the CLNP packet. The IP packet generated by EON will contain the source address of the EON machine, and the destination address of the EON machine. The following static mapping tables will exist in the EON machines: NSAP Prefix -> remote IP address of EON machine to decapsulate the IP packet into a CLNP packet. For local NETs of Router: NSAP Prefix -> local NET of router on the ethernet to route the traffic off the NSFNET service Changes or requests to be added to these tables should be sent to nsfnet-admin(a)merit.edu. The support for CLNP native switching services on the T3 backbone proceeded to be tested in November. The AIX 3.2 system software that supports CLNP switching is in system test and is expected to be available on the T3 backbone in February '93. T3 ENSS Backup Plan ------------------- The installation and testing of dedicated T1 leased line circuits between all T3 ENSS nodes, and a CNSS T1 router in a secondary POP was completed in November. The topology for T3 ENSS backup is illustrated in a postscript map that is available via anonymous FTP on ftp.ans.net in the file </pub/info/t3enss-backup.ps>. We have begun to work on subsequent optimizations to further improve backup connectivity. There may be situations where a secondary ENSS router is used to terminate T1 backup circuits. T1 Backbone Turned Off ---------------------- These activities required to precede the T1 backbone were concluded on 12/1 and the shutdown of the T1 backbone commenced on 12/2. There were a couple of problems that were quickly corrected during the T1 backbone shutdown. Some regionals that maintained default routing configurations pointing to the T1 backbone lost connectivity for a brief period. Some regional router configurations were changed, and the T3 backbone will continue to announce the T1 backbone address (129.140) from several ENSS nodes for a while longer to ease the transition. Also, there was a problem discovered with the RCP nodes in the "NSS-router" configuration used for the CA*Net interconnection to the T3 network. The RCPs could not manage the full 6000+ network destination routing tables. As a workaround, the three NSS-routers are now configured to advertise the T3 backbone network as a default route to CA*Net. ANSNET/NSFNET Operational Experiences with MBONE ================================================ During the week of 11/9 and 11/16, there were a number of operational problems during the preparation and actual operation of the IETF MBONE packet video/audiocast. The use of loose source route packets, and the large volume of MBONE traffic appears to have caused fairly widespread problems for several Internet service providers. However, the volume of MBONE traffic and source route optioned packets did not seem to adversely affect the ANSNET/NSFNET, as was earlier believed. There were severe routing instabilities with peer networks at several ANSNET/NSFNET border gateways including E128 (Palo Alto), E144 (FIX-E), E145 (FIX-W) and most notably at E133 (Ithaca) due to the MBONE traffic and processing of source route packets. The instability in these peer networks coupled with inefficient handling of very large and frequent routing changes introduced through EGP resulted in some ANSNET/NSFNET instabilities. Networks carrying MBONE traffic frequently stopped being advertised by external peers, and were timed out by the ENSS. The external peer then stabilized and these networks were then advertised to the ENSS by the external peer soon thereafter. This process repeated itself in a cyclical fashion. This caused a few connectivity problems at various places on the ANSNET, but was by far the worst at ENSS133 (Ithaca). One reason that the problem was worse at ENSS133 than at other places was due to the fact that Cornell was on the sending end of a fair number of MBONE tunnels, which meant the card-to-system traffic for unreachable destinations tended to be higher on the ENSS133 router than elsewhere. There were several actions taken during the week of 11/16 (IETF video/audiocast) which reduced the severity of this problem including: (a) ICMP unreachable messages were turned off on the external interfaces of ENSS routers that experienced problems. These messages were not being processed directly on the external ENSS interfaces which resulted in some inefficiency. New software will be deployed in early December to correct this. (b) SprintLink rerouted traffic (and the MBONE tunnel) from the IETF to Cornell from the CIX (via internal PSInet path), to the T3 ANSNET path. This improved stability within PSInet and within ANSNET. (c) Cornell rerouted traffic (MBONE tunnel) to SDSC from the PSInet path to the T3 ANSNET path. (d) One of the two parallel IETF audio/video channels was disabled. (e) A default route was established on ENSS133 pointing to its adjacent internal router (CNSS49). This ensured that card<->system traffic being processed due to unreachable destinations was moved to the CNSS router which was not involved in processing EGP updates. (f) A new version of the routing software was installed on the four ENSS nodes that experienced route flapping to aggregate EGP updates from external peers before sending IBGP messages to other internal T3 routers. The combination of all of these actions stabilized ENSS133 and the other ENSS routers that experienced instabilities. There are several actions which we already have, or will soon implement to avoid ANSNET border router instabilities during future MBONE multicast events: (1) The ENSS EGP software has been enhanced to support improved aggregation of updates from external peers into IBGP update messages. The ENSS will now aggregate EGP derived routes together into a single update before flooding this to other routers across the backbone via IBGP. This improves the efficiency of the ENSS dramatically. (2) A change to the ANSNET router interface microcode has been implemented (and will be deployed during early December) so that problems resulting from large amounts of ENSS card-system traffic will be eliminated when destinations become unreachable. Even if mrouted keeps sending traffic, this will be dropped on the incoming ENSS interface. (3) The T1 NSFNET backbone was disconnected on 12/2. The T1 network (particularly the interconnect points with the T3 system) was a major source of route flapping, and eliminating it should provide an additional margin for handling instability from other peer networks. While the changes we are making to the T3 network will significantly improve T3 network performance in dealing with external EGP peer flapping, and related MBONE routing problems, our changes will *NOT* improve the problems that other Internet networks may experience when processing source route packets, and handling routing transitions with MBONE tunnels. We recommend that each service provider develop their own internal routing plan to address this, we continue to recommend the migration to use of BGP at all border gateways, and we recommend that MBONE software be upgraded to support IP encapsulation to avoid the problems with routers that do not process loose source route optioned packets efficiently. We also are recommending that the MBONE developers explore optimizing the mrouted software to avoid the sustained unidirectional flows to unreachable destinations that we observed. Finally, it is recommended that an mrouted machine be maintained on the ENSS DMZ of each participating regional, and this node be used as a hierarchical distribution point to locations in the local campus and regional. Backhauling of traffic across campuses and regionals should be discouraged. Routing Software on the T3 Network ================================== New routing software was installed on the T3 backbone in November to support various enhancements. There is improved route download performance using asynchronous IOCTL calls. There is new support for static routes, and checks for the size of BGP updates and attributes. New software will be installed in early December that addresses the routing instability problems observed during the MBONE multicast events in November. This will include the code for improved aggregation of EGP updates thereby eliminating any CPU starvation during EGP route flapping. Next AIX 3.1 System Software Release ==================================== New RS6000 system software was deployed on several T3 network nodes in late November and will be fully deployed by early December. The most significant change is the ability to drop packets on the interface which receives them for which there is no route available. During transient routing conditions we may experience high card/system traffic due to route downloads which can cause transient instabilities. This change will improve the efficiency for route installs/deletes between router system memory and the on-card forwarding tables. This code also supports the generation of ICMP network unreachable messages on the card rather than on the system. There are two bug fixes in this software, one for the performance problem that can occur when an IBGP TCP session gets deadlocked, and another that avoids FDDI problems if a T1 backup link on a T3 ENSS gets congested. Also all ENSS interfaces now support MTU path discovery. RS960 FDDI Deployment Status ============================ We are proceeding to schedule RS960 FDDI adapter installations on several ENSS nodes in December including ENSS134 (NEARnet), ENSS130 (Argonne), ENSS145 (FIX-E), ENSS136 (SURAnet), ENSS139 (SESQUInet), ENSS144 (FIX-W), ENSS142 (WestNet), and ENSS143 (NorthWestNet). There are performance tests under way involving Pittsburgh Supercomputer Center, San Diego Supercomputer Center, and National Center for Supercomputer Applications that are designed to exploit the FDDI high bandwidth capability. The MTUs on various interfaces in the T3 backbone have been changed as was described in the October engineering report, and the ENSS nodes will negotiate MTU path discovery with other systems outside the T3 backbone. During the tests performed so far, there have been some observations of low level packet loss (1.6%) between the Cray end systems at the supercomputer centers which has caused performance problems with the large window TCP implementations achieving peak performance over the T3 backbone. The packet loss problems have not been traced to sources inside the T3 backbone, and the problem is being investigated by the supercomputer centers. Network Source/Destination Statistics Collection ================================================ During November, we collected the first full month of T3 network source/destination traffic statistics. This data will be used for topology engineering, capacity planning, and various research projects. RS960 Memory Parity Problem =========================== During November, we experienced two problems on CNSS17 and CNSS65 due to the failure of parity checking logic within the on-card memory on selected RS960 T3 adapters. These outages are very infrequent and do not generally result in ENSS isolation from the network since only a single interface will be affected, and redundant connectivity is employed on other CNSS interfaces. The problems were cleared by a software reset of the interface. The problem is suspected to be due to the memory technology used on some of the cards.

1 0

Holiday routing configuration update schedule
by Steven K. Widmayer 16 Dec '92

16 Dec '92

Holiday greetings! Here is the end of year routing configuration update schedule. Tue, Dec. 22 Thur, Dec. 24 Tue, Dec. 29 Thur, Dec. 31 The Friday morning updates are being pushed back to Thursdays due to the holidays. --Steve Widmayer Merit/NSFNET

1 0

CERT Advisory - ConvexOS and ConvexOS/Secure Vulnerabilities
by CERT Advisory 16 Dec '92

16 Dec '92

CA-92:21 CERT Advisory December 16, 1992 ConvexOS and ConvexOS/Secure Vulnerabilities --------------------------------------------------------------------------- The CERT Coordination Center has received information concerning several vulnerabilities in the following CONVEX Computer Corporation products: ConvexOS/Secure, CONVEX CXbatch, CONVEX Storage Manager (CSM), and ConvexOS EMACS. These vulnerabilities can affect ConvexOS versions V6.2 - V10.2 and ConvexOS/Secure versions V9.5 and V10.0 on all supported architectures. CONVEX is aware of the vulnerabilities, and fixes or workarounds are available. Three of the fixes are implemented as full Engineering Change Notice (ECN) patches and, as such, will be shipped with all new systems as well as being released as upgrades for the products CXbatch, CSM and ConvexOS/Secure. There is a workaround available for the ConvexOS EMACS vulnerability. CONVEX is currently incorporating the fixes to these vulnerabilities into future releases of each product. Future shipments of these products should not be vulnerable to these problems. If you have any questions about the affected products, please contact your CONVEX representative or the CONVEX Technical Assistance Center (TAC) at 1-800-952-0379. ----------------------------------------------------------------------------- ConvexOS/Secure: passwd patch I. Description The "passwd" command in ConvexOS/Secure contains a security vulnerability in versions V9.5 and V10.0 of ConvexOS/Secure. This vulnerability has been fixed in ConvexOS/Secure V10.1. II. Impact Local users can gain unauthorized root access. III. Solution Obtain and install ConvexOS/Secure V10.0.2 - Part No. 710-007815-008. ------------------------------------------------------------------------------ Convex CXbatch: qmgr patch I. Description The "qmgr" command in CONVEX CXbatch versions V1.0 - V2.1.3 contains a security vulnerability. This vulnerability is present in ConvexOS V6.2 - V10.2 on systems that have installed the optional CXbatch facility. II. Impact Local users can gain unauthorized root access. III. Solution A. As root, rename the existing version of /usr/convex/qmgr and modify the permission (from 6755 to 700) to prevent misuse. # /bin/mv /usr/convex/qmgr /usr/convex/qmgr.orig # /bin/chmod 700 /usr/convex/qmgr.orig B. Next, obtain and install CONVEX CXbatch V2.1.4 - Part No. 710-007830-011. ------------------------------------------------------------------------------ Convex CSM: migmgr patch I. Description The "migmgr" command in CONVEX CSM contains a security vulnerability, in ConvexOS version V10.1 of systems that have installed the CSM facility. This vulnerability will be fixed in the next CSM release. II. Impact Local users can gain unauthorized root access. III. Solution A. As root, rename the existing version of /usr/csm/bin/migmgr and modify the permission (from 4755 to 700) to prevent misuse. # /bin/mv /usr/csm/bin/migmgr /usr/csm/bin/migmgr.orig # /bin/chmod 700 /usr/csm/bin/migmgr.orig B. Next, obtain and install CONVEX CSM V1.0.1 - Part No. 710-011315-003 ------------------------------------------------------------------------------ ConvexOS: EMACS editor workaround I. Description The EMACS Editor in ConvexOS contains a security vulnerability, in ConvexOS versions V9.0 - V10.2. II. Impact Local users can gain unauthorized access to /dev/kmem. III. Solution As root, remove the setgid bit from /usr/convex/emacs. # /bin/chmod 755 /usr/convex/emacs ------------------------------------------------------------------------------ The CERT Coordination Center wishes to thank the CONVEX Computer Corporation for their response to these problems. We would also like to thank Bob Vickers from the University of London Computer Centre, London, England, for reporting the CXbatch problem to us. ------------------------------------------------------------------------------ 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

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

15 Dec '92

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: IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 128.254 FMC-NOD C:US D:12/14/92 1:555 131.163 I-CAN C:CA D:12/14/92 1:701 2:702 3:279 134.189 GDFW C:US D:12/14/92 1:1740 134.200 GOODYEAR C:US D:12/14/92 1:174 137.230 CATNET C:US D:12/14/92 1:1224 141.42 CHARITE-NET C:DE D:12/14/92 1:293 2:291 144.124 ABERNET C:GB D:12/14/92 1:297 2:372 151.110 ETN C:US D:12/14/92 1:600 155.99 UTAH-E-NET C:US D:12/14/92 1:210 2:209 156.17 WROCPOLIP C:PL D:12/14/92 1:1800 162.10 ANACOMP-SD C:US D:12/14/92 1:1740 164.8 UNI-MB-NET C:SI D:12/14/92 1:297 2:372 192.12.124 TEC-LAN1 C:US D:12/14/92 1:200 2:201 3:184 4:164 192.51.5 SPTNET C:NO D:12/14/92 1:1800 2:701 192.54.133 ACFP-NE-NET C:US D:12/14/92 1:184 2:164 192.84.90 FERNET C:SI D:12/14/92 1:297 2:372 192.86.66 TEC-LAN2 C:US D:12/14/92 1:200 2:201 192.88.9 ABERNET1 C:GB D:12/14/92 1:297 2:372 192.88.10 ABERNET2 C:GB D:12/14/92 1:297 2:372 192.94.226 OPEN-SYSTEMS C:AT D:12/14/92 1:701 192.108.138 SANET C:CS D:12/14/92 1:513 192.108.148 IAC-NET C:CS D:12/14/92 1:513 192.109.46 DVSHAN C:DE D:12/14/92 1:701 192.129.1 MPIPF-LAN C:DE D:12/14/92 1:293 2:291 192.131.145 NAWCNET C:US D:12/14/92 1:184 2:164 192.150.194 ROLAN-UNIVAQ C:IT D:12/14/92 1:513 192.150.195 LANCO-UNIVAQ C:IT D:12/14/92 1:513 192.150.196 CC-UNIVAQ C:IT D:12/14/92 1:513 192.153.18 UNINET2 C:HU D:12/14/92 1:513 192.154.45 SIGMAXI-NET C:US D:12/14/92 1:81 2:1327 192.154.51 ECS-SLIP C:US D:12/14/92 1:81 2:1327 192.154.52 ECS-FRLY C:US D:12/14/92 1:81 2:1327 192.154.53 LDG-NET C:US D:12/14/92 1:81 2:1327 192.154.54 TAC-NET C:US D:12/14/92 1:81 2:1327 192.154.55 MARTIN-NET C:US D:12/14/92 1:81 2:1327 192.160.172 SOTNET C:HU D:12/14/92 1:513 192.171.131 NERC-NET4 C:GB D:12/14/92 1:297 2:372 192.171.132 NERC-NET5 C:GB D:12/14/92 1:297 2:372 192.171.136 NERC-NET9 C:GB D:12/14/92 1:297 2:372 192.171.141 NERC-NET14 C:GB D:12/14/92 1:297 2:372 192.171.142 NERC-NET15 C:GB D:12/14/92 1:297 2:372 192.171.143 NERC-NET16 C:GB D:12/14/92 1:297 2:372 192.171.144 NERC-NET17 C:GB D:12/14/92 1:297 2:372 192.171.153 NERC-NET26 C:GB D:12/14/92 1:297 2:372 192.171.154 NERC-NET27 C:GB D:12/14/92 1:297 2:372 192.171.157 NERC-NET30 C:GB D:12/14/92 1:297 2:372 192.171.165 NERC-NET38 C:GB D:12/14/92 1:297 2:372 192.171.182 NERC-NET55 C:GB D:12/14/92 1:297 2:372 192.171.184 NERC-NET57 C:GB D:12/14/92 1:297 2:372 192.187.142 NETCOM45 C:US D:12/14/92 1:200 2:201 192.195.32 QUADRALAY C:US D:12/14/92 1:280 2:114 192.206.201 WEDNET C:US D:12/14/92 1:1331 192.215.3 NETBLK-CERFNET-3 C:US D:12/14/92 1:1740 192.215.4 NETBLK-CERFNET-4 C:US D:12/14/92 1:1740 192.231.11 PV-T1-MLF C:US D:12/14/92 1:2002 192.231.63 SCBULLDOGS C:US D:12/14/92 1:279 2:86 192.245.169 POLHEP2 C:PL D:12/14/92 1:513 193.2.1 ARNES-NET C:SI D:12/14/92 1:297 2:372 193.2.4 IJS-NET1 C:SI D:12/14/92 1:297 2:372 193.60.8 ABERNET3 C:GB D:12/14/92 1:297 2:372 193.60.9 ABERNET4 C:GB D:12/14/92 1:297 2:372 193.60.10 ABERNET5 C:GB D:12/14/92 1:297 2:372 193.60.11 ABERNET6 C:GB D:12/14/92 1:297 2:372 193.60.12 ABERNET7 C:GB D:12/14/92 1:297 2:372 193.60.13 ABERNET8 C:GB D:12/14/92 1:297 2:372 193.60.14 ABERNET9 C:GB D:12/14/92 1:297 2:372 193.60.15 ABERNET10 C:GB D:12/14/92 1:297 2:372 198.7.16 UERJ-16 C:BR D:12/14/92 1:1740 198.7.17 UERJ-17 C:BR D:12/14/92 1:1740 198.7.18 UERJ-18 C:BR D:12/14/92 1:1740 198.7.19 UERJ-19 C:BR D:12/14/92 1:1740 198.7.20 UERJ-20 C:BR D:12/14/92 1:1740 198.7.21 UERJ-21 C:BR D:12/14/92 1:1740 198.7.22 UERJ-22 C:BR D:12/14/92 1:1740 198.7.23 UERJ-23 C:BR D:12/14/92 1:1740 198.7.24 UERJ-24 C:BR D:12/14/92 1:1740 198.7.25 UERJ-25 C:BR D:12/14/92 1:1740 198.7.26 UERJ-26 C:BR D:12/14/92 1:1740 198.7.27 UERJ-27 C:BR D:12/14/92 1:1740 198.7.28 UERJ-28 C:BR D:12/14/92 1:1740 198.7.29 UERJ-29 C:BR D:12/14/92 1:1740 198.7.30 UERJ-30 C:BR D:12/14/92 1:1740 198.7.31 UERJ-31 C:BR D:12/14/92 1:1740 198.22.11 DRCNET-6 C:US D:12/14/92 1:1800 2:1240 Network IP: 128.254 Network Name: FMC-NOD Location: FMC Corporation, Northern Ordnance Division, 4800 East River Road, Minneapolis, MN 55421, USA Country Code: US 1:555 Minnesota Supercomputer Center Network (MSCNet) Network IP: 131.163 Network Name: I-CAN Location: Intergraph Canada Ltd., 3115 - 12th Street NE, Calgary, Alberta T2E 7J2, CANADA Country Code: CA 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 134.189 Network Name: GDFW Location: Computer Science Corporation, Mail Zone 5000, 6100 Western Place, Fort Worth, TX 76107, USA Country Code: US 1:1740 CERFnet Network IP: 134.200 Network Name: GOODYEAR Location: Goodyear Technical Center, 1376 Technical Way Drive, Akron, OH 44316, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 137.230 Network Name: CATNET Location: Caterpillar, Inc., P.O. Box 1875, Peoria, IL 61656-1875, USA Country Code: US 1:1224 NCSA, Champaign, IL Network IP: 141.42 Network Name: CHARITE-NET Location: Charite Berlin, Schumannstr. 20-21, D-O-1040 Berlin, GERMANY Country Code: DE 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) Network IP: 144.124 Network Name: ABERNET Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 151.110 Network Name: ETN Location: Eaton Corporation, Eaton Center, 1111 Superior Avenue, Cleveland, OH 44114, USA Country Code: US 1:600 OARNET, Cleveland, OH Network IP: 155.99 Network Name: UTAH-E-NET Location: University of Utah, Computer Center, Merrill Engineering Building, Salt Lake City, UT 84112, USA Country Code: US 1:210 Westnet Regional Network (Utah Attachment) - ENSS 142 2:209 Westnet Regional Network (Colorado Attachment) - ENSS 141 Network IP: 156.17 Network Name: WROCPOLIP Location: Technical University of Wroclaw, Computing Centre, Wybrzeze Wyspianskiego 27, 50-370 Wroclaw, POLAND Country Code: PL 1:1800 ICM (FIX-East) Network IP: 162.10 Network Name: ANACOMP-SD Location: Anacomp, Inc., 12365 Crosthwaite, Poway, CA 92120, USA Country Code: US 1:1740 CERFnet Network IP: 164.8 Network Name: UNI-MB-NET Location: University of Maribor, Maribor, SLOVENIA Country Code: SI 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.12.124 Network Name: TEC-LAN1 Location: Army Topographic Engineering Center, Information Management Office, Information System Engineering Branch, Fort Belvoir, VA 22060-5546, USA Country Code: US 1:200 BARRNet 2:201 BARRNet 3:184 Milnet (FIX-East) 4:164 Milnet (FIX-West) Network IP: 192.51.5 Network Name: SPTNET Location: Spacetec A.S., P.B. 585, N-9001 Tromso, NORWAY Country Code: NO 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.54.133 Network Name: ACFP-NE-NET Location: Air Force Global Weather Central, Building D, Room 7-30, Offutt Air Force Base, NE 68113, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.84.90 Network Name: FERNET Location: Faculty for Electrical and Computer Engineering, University of Ljubljana, SLOVENIA Country Code: SI 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.86.66 Network Name: TEC-LAN2 Location: Army Topographic Engineering Center, Information Management Office, Information System Engineering Branch, Fort Belvoir, VA 22060-5546, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.88.9 Network Name: ABERNET1 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.88.10 Network Name: ABERNET2 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.94.226 Network Name: OPEN-SYSTEMS Location: Open Systems EDV-Beratungs und HandelsgesmbH, Seilerstatte 10/11 A-1010 Wien, AUSTRIA Country Code: AT 1:701 Alternet Network IP: 192.108.138 Network Name: SANET Location: Slovak Technical University, Ilkovicova 3, CS-81219 Bratislava, CZECHO-SLOVAKIA Country Code: CS 1:513 EASInet / CERN Network IP: 192.108.148 Network Name: IAC-NET Location: Institute for Applied Cybernetics, Hanulova 5/a, CS-84416 Bratislava, CZECHO-SLOVAKIA Country Code: CS 1:513 EASInet / CERN Network IP: 192.109.46 Network Name: DVSHAN Location: DVS GmbH, Hannover, DVS GmbH, Krepenstr. 8, D-W-3000 Hannover 1, GERMANY Country Code: DE 1:701 Alternet Network IP: 192.129.1 Network Name: MPIPF-LAN Location: Max-Planck-Institut fuer psychologische Forschung, Leopoldstr. 24, D-W-8000 Muenchen 44, GERMANY Country Code: DE 1:293 Energy Science Network (FIX-East) 2:291 Energy Science Network (FIX-West) Network IP: 192.131.145 Network Name: NAWCNET Location: Information Systems and Technical Services Dept., Naval Air Engg. Center, Building 120, Route 547, Lakehurst, NJ 08733, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 192.150.194 Network Name: ROLAN-UNIVAQ Location: Universita' dell Aquila, L'Aquila-Roio, ITALY Country Code: IT 1:513 EASInet / CERN Network IP: 192.150.195 Network Name: LANCO-UNIVAQ Location: Universita' dell'Aquila, L'Aquila-Coppito, ITALY Country Code: IT 1:513 EASInet / CERN Network IP: 192.150.196 Network Name: CC-UNIVAQ Location: Universita' dell Aquila, L'Aquila, ITALY Country Code: IT 1:513 EASInet / CERN Network IP: 192.153.18 Network Name: UNINET2 Location: Eotvos Lorand University of Sciences, Budapest Puskin U. 5-7, H-1088 Budapest, HUNGARY Country Code: HU 1:513 EASInet / CERN Network IP: 192.154.45 Network Name: SIGMAXI-NET Location: Sigma Xi, P.O. Box 13975, Research Triangle Park, NC 27709, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.51 Network Name: ECS-SLIP Location: UNC Educational Computing Service, PO BOX 12035, Research Triangle Park, NC 27709, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.52 Network Name: ECS-FRLY Location: UNC Educational Computing Service, PO BOX 12035, Research Triangle Park, NC 27709, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.53 Network Name: LDG-NET Location: Logical Design Group, Inc., 6301 Chapel Hill Road, Raleigh, NC 27607, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.54 Network Name: TAC-NET Location: The Alliance Center, 4020 West Chase Blvd., Suite 500, Raleigh, NC 27607, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.154.55 Network Name: MARTIN-NET Location: Martin Information Services, Inc., 4505 Falls of the Neuse Road, Suite 350, Raleigh, NC 27609-6265, USA Country Code: US 1:81 CONCERT 2:1327 ANS Washington D.C. - DNSS 59 Network IP: 192.160.172 Network Name: SOTNET Location: Semmelweis University of Medicine, Kalvaria ter 5., H-1089 Budapest, HUNGARY Country Code: HU 1:513 EASInet / CERN Network IP: 192.171.131 Network Name: NERC-NET4 Location: Research Vessel Services (NERC), No 1 Dock, Barry, South Glamorgan CF6 6UZ, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.132 Network Name: NERC-NET5 Location: Research Vessel Services (NERC), No 1 Dock, Barry, South Glamorgan CF6 6UZ, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.136 Network Name: NERC-NET9 Location: Institute of Terrestrial Ecology, Bush Estate, Penicuik, Midlothian EH26 0QB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.141 Network Name: NERC-NET14 Location: British Geological Survey, Murchison House, West Mains Road, Edinburgh EH9 3LA, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.142 Network Name: NERC-NET15 Location: British Geological Survey, Murchison House, West Mains Road, Edinburgh EH9 3LA, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.143 Network Name: NERC-NET16 Location: British Geological Survey, Murchison House, West Mains Road, Edinburgh EH9 3LA, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.144 Network Name: NERC-NET17 Location: British Geological Survey, Murchison House, West Mains Road, Edinburgh EH9 3LA, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.153 Network Name: NERC-NET26 Location: Institute of Terrestrial Ecology, Merlewood Research Station, Grange-over-Sands, Cumbria LA11 6JU, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.154 Network Name: NERC-NET27 Location: Institute of Terrestrial Ecology, Merlewood Research Station, Grange-over-Sands, Cumbria LA11 6JU, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.157 Network Name: NERC-NET30 Location: British Geological Survey, Murchison House, West Mains Road, Edinburgh EH9 3LA, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.165 Network Name: NERC-NET38 Location: Institute of Hydrology (NERC), Staylittle, Llanbrynmair, Powys, Wales SY19 7DB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.182 Network Name: NERC-NET55 Location: British Geological Survey, Murchison House, West Mains Road, Edinburgh EH9 3LA, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.171.184 Network Name: NERC-NET57 Location: Institute of Terrestrial Ecology, Merlewood Research Station, Grange-over-Sands, Cumbria LA11 6JU, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 192.187.142 Network Name: NETCOM45 Location: Netcom On-line Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.195.32 Network Name: QUADRALAY Location: Quadralay Corporation, 8920 Business Park Drive, Suite 206, Austin, TX 78759, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Network IP: 192.206.201 Network Name: WEDNET Location: Washington Schools Information Processing Cooerative, 2000 - 200th Pl., SW, Lynnwood, WA 98036, USA Country Code: US 1:1331 ANS Seattle - DNSS 91 Network IP: 192.215.3 Network Name: NETBLK-CERFNET-3 Location: CERFnet, PO BOX 85608, San Diego, CA 92186-9784, USA Country Code: US 1:1740 CERFnet Network IP: 192.215.4 Network Name: NETBLK-CERFNET-4 Location: CERFnet, PO BOX 85608, San Diego, CA 92186-9784, USA Country Code: US 1:1740 CERFnet Network IP: 192.231.11 Network Name: PV-T1-MLF Location: IBM Corporation, 704 Quince Orchard Road, Gaithersburg, MD 20878, USA Country Code: US 1:2002 IBM-PV-AS Network IP: 192.231.63 Network Name: SCBULLDOGS Location: South Carolina State College, 300 College Avenue, NE, Orangeburg, SC 29117, USA Country Code: US 1:279 SURANET Regional Network (Georgia Tech) 2:86 SURANET Regional Network (College Park) Network IP: 192.245.169 Network Name: POLHEP2 Location: Polish Atomic Energy Agency, High Energy Physics Departament, ul.Kawiory 26A, PL-30055 Krakow, POLAND Country Code: PL 1:513 EASInet / CERN Network IP: 193.2.1 Network Name: ARNES-NET Location: Academic and Research Network of Slovenia, Ljubljana, SLOVENIA Country Code: SI 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.2.4 Network Name: IJS-NET1 Location: Jozef Stefan Institute, Ljubljana, SLOVENIA Country Code: SI 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.8 Network Name: ABERNET3 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.9 Network Name: ABERNET4 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.10 Network Name: ABERNET5 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.11 Network Name: ABERNET6 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.12 Network Name: ABERNET7 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.13 Network Name: ABERNET8 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.14 Network Name: ABERNET9 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 193.60.15 Network Name: ABERNET10 Location: University of Wales - Aberystwyth, Aberystwyth, Dyfed, Wales SY23 3BB, UNITED KINGDOM Country Code: GB 1:297 Nasa Science Network (FIX-East) 2:372 Nasa Science Network (FIX-West) Network IP: 198.7.16 Network Name: UERJ-16 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.17 Network Name: UERJ-17 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.18 Network Name: UERJ-18 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.19 Network Name: UERJ-19 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.20 Network Name: UERJ-20 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.21 Network Name: UERJ-21 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.22 Network Name: UERJ-22 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.23 Network Name: UERJ-23 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.24 Network Name: UERJ-24 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.25 Network Name: UERJ-25 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.26 Network Name: UERJ-26 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.27 Network Name: UERJ-27 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.28 Network Name: UERJ-28 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.29 Network Name: UERJ-29 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.30 Network Name: UERJ-30 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.7.31 Network Name: UERJ-31 Location: UERJ - UNIVERSIDADE DO ESTADO DO RIO DE JANEIRO, COINFO - COORDENACAO GERAL DE INFORMATICA, AV. Sao Francisco Xavier, 524 - BLOCO F - 1 andar, Maracana - Rio de Janeiro - RJ, CEP 20550, BRAZIL Country Code: BR 1:1740 CERFnet Network IP: 198.22.11 Network Name: DRCNET-6 Location: Dynamics Research Corporation, 60 Frontage Road, Andover, MA 01810, USA Country Code: US 1:1800 ICM (FIX-East) 2:1240 ICM (FIX-West) Network IP: 198.22.19 Network Name: TIESNET Location: Technology and Information Educational Services (TIES), 1935 West County Road B2, Roseville, MN 55113, 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) Total configured T3 networks: 8234 ***************************************************************** 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)merit.edu

1 0

November NSFNET T3 Usage by Services
by Susan.M.Horvath＠um.cc.umich.edu 14 Dec '92

14 Dec '92

NSFNET T3 Usage by Service November 1992 Service Type % Packets % Bytes ============ ========= ======= File exchange 25 46 Networked mail 16 18 Interactive 16 6 Name lookup 5 2 Other TCP/UDP services 36 27 Non TCP/UDP services 2 1 --- --- 100 100 The categories above are defined as follows: File exchange ftp: data and control (tcp ports 20, 21) Networked mail smtp, nntp, vmnet, uucp (tcp ports 25, 119, 175, 540) Interactive telnet, finger, who, login (tcp ports 23, 79, 513, udp port 513) Name lookup domain name service (udp port 53, tcp port 53) Other TCP/UDP services all tcp/udp ports not included above (e.g. irc, talk, X-windows, appletalk) Non-TCP/UDP services icmp, egp, etc. More detailed information is available for anonymous FTP from NIC.MERIT.EDU (the Merit NIC Services machine) in the file "t3-9211.ports" on the nsfnet/statistics/1992 directory.

1 0

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

11 Dec '92

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: IP address Net name Country Date Priority:AS ---------- -------- ------- ---- ----------- 142.222 MOHAWK-NET C:CA D:12/10/92 1:1391 2:1392 3:1393 12:602 152.120 DOTNET1 C:US D:12/11/92 1:1327 155.91 MERCK1 C:US D:12/10/92 1:97 158.189 JGVANDYKE C:US D:12/10/92 1:701 2:702 3:279 158.219 CBO C:US D:12/10/92 1:174 159.97 GRACE C:US D:12/10/92 1:174 163.207 NWSCHS C:US D:12/10/92 1:184 2:164 163.243 GOODYEAR2 C:US D:12/11/92 1:174 192.25.112 HP3-C112 C:US D:12/10/92 1:93 192.75.19 SUN-ONET C:CA D:12/10/92 1:701 2:702 3:279 192.77.52 INRS-ENER-IP C:CA D:12/10/92 1:1393 2:1391 3:1392 13:602 192.84.22 CELTECH C:US D:12/10/92 1:174 192.87.74 PAR-LAN C:NL D:12/11/92 1:513 192.88.124 MIAMI-ECE C:US D:12/10/92 1:297 2:86 192.98.22 VTYH-NET C:FI D:12/11/92 1:1800 2:701 192.104.85 SPSS1 C:US D:12/10/92 1:267 2:1225 3:266 192.139.190 LAMBTON1 C:CA D:12/10/92 1:1391 2:1392 3:1393 12:602 192.150.93 UTPAB C:US D:12/10/92 1:280 2:114 192.187.154 NETCOM57 C:US D:12/10/92 1:200 2:201 192.197.62 NIAGARA1 C:CA D:12/10/92 1:1391 2:1392 3:1393 12:602 192.203.45 ATHENA C:US D:12/10/92 1:701 2:702 3:279 192.203.69 AWS-NET C:US D:12/11/92 1:701 2:702 3:279 192.203.233 MORRIS-NET C:US D:12/10/92 1:97 192.207.159 PPL-1 C:US D:12/10/92 1:210 2:209 192.231.207 RARITANVAL C:US D:12/10/92 1:97 192.231.231 IONA C:US D:12/10/92 1:97 192.231.232 ESSEXCOUNTY C:US D:12/10/92 1:97 192.231.233 BUCKSCOUNTY C:US D:12/10/92 1:97 192.231.234 ITHACA2 C:US D:12/10/92 1:97 192.233.2 ELMS C:US D:12/10/92 1:560 2:281 5:701 192.233.7 MILES4 C:US D:12/10/92 1:560 2:281 5:701 192.233.40 JAXLAB0 C:US D:12/10/92 1:560 2:281 5:701 192.233.41 JAXLAB1 C:US D:12/10/92 1:560 2:281 5:701 192.233.42 JAXLAB2 C:US D:12/10/92 1:560 2:281 5:701 192.233.43 JAXLAB3 C:US D:12/10/92 1:560 2:281 5:701 192.245.119 FRB-MPLS-NET C:US D:12/10/92 1:267 2:1225 3:266 193.120.16 ICLITC-C16 C:IE D:12/10/92 1:701 193.120.17 ICLITC-C17 C:IE D:12/10/92 1:701 193.120.18 ICLITC-C18 C:IE D:12/10/92 1:701 193.120.19 ICLITC-C19 C:IE D:12/10/92 1:701 193.120.20 ICLITC-C20 C:IE D:12/10/92 1:701 193.120.21 ICLITC-C21 C:IE D:12/10/92 1:701 193.120.22 ICLITC-C22 C:IE D:12/10/92 1:701 193.120.23 ICLITC-C23 C:IE D:12/10/92 1:701 193.120.24 ICLITC-C24 C:IE D:12/10/92 1:701 193.120.25 ICLITC-C25 C:IE D:12/10/92 1:701 193.120.26 ICLITC-C26 C:IE D:12/10/92 1:701 193.120.27 ICLITC-C27 C:IE D:12/10/92 1:701 193.120.28 ICLITC-C28 C:IE D:12/10/92 1:701 193.120.29 ICLITC-C29 C:IE D:12/10/92 1:701 193.120.30 ICLITC-C30 C:IE D:12/10/92 1:701 193.120.31 ICLITC-C31 C:IE D:12/10/92 1:701 193.136.224 UALNET-1 C:PT D:12/11/92 1:701 193.166.18 DOMLANG-NET C:FI D:12/11/92 1:1800 2:701 198.17.24 PEOCU-NET-1 C:US D:12/10/92 1:184 2:164 198.17.25 PEOCU-NET-2 C:US D:12/10/92 1:184 2:164 198.17.26 PEOCU-NET-3 C:US D:12/10/92 1:184 2:164 198.17.27 PEOCU-NET-4 C:US D:12/10/92 1:184 2:164 198.17.28 PEOCU-NET-5 C:US D:12/10/92 1:184 2:164 Network IP: 142.222 Network Name: MOHAWK-NET Location: Mohawk College of Applied Arts and Technology, 135 Fennell Avenue West, Hamilton, Ontario L8N 3T2, CANADA Country Code: CA 1:1391 CA*net router in Toronto 2:1392 CA*net router in Montreal 3:1393 CA*net router in Quebec 12:602 CA*net router in Montreal Network IP: 152.120 Network Name: DOTNET1 Location: US Dept. of Transportation, 400 7th St., S.W., Washington, DC 20590, USA Country Code: US 1:1327 ANS Washington D.C. - DNSS 59 Network IP: 155.91 Network Name: MERCK1 Location: Merck and Co., Inc., 126 E. Lincoln Avenue, Rahway, NJ 07065, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 158.189 Network Name: JGVANDYKE Location: J. G. Van Dyke and Associates, 6701 Rockledge Drive, Suite 250, Bethesda, MD 20817, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 158.219 Network Name: CBO Location: Congressional Budget Office, H2-486 Ford HOB, Washington, DC 20515, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 159.97 Network Name: GRACE Location: W.R. Grace & Co., One Town Center Road, Boca Raton, FL 33486, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 163.207 Network Name: NWSCHS Location: Management Engineering and Information Department, Commanding Officer, WPNSTA CHASN CODE 052C, Building 13, Goose Creek, SC 29445-8601, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 163.243 Network Name: GOODYEAR2 Location: Goodyear Technical Center, Department 450B, P. O. Box 3531, Akron, OH 44309-3531, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.25.112 Network Name: HP3-C112 Location: Hilco Technologies, Inc., 3300 Rider Trail South, Suite 300, Earth City, MO 63045, USA Country Code: US 1:93 MIDnet Network IP: 192.75.19 Network Name: SUN-ONET Location: Sun Microsystems of Canada, Inc., 100 Renfrew Drive, Markham, Ontario L3R 9R6, CANADA Country Code: CA 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 192.77.52 Network Name: INRS-ENER-IP Location: INRS-Energie et materiaux, 1650 Montee Sainte Julie, C.P. 1020, Varennes, Quebec J3X 1S2, CANADA Country Code: CA 1:1393 CA*net router in Quebec 2:1391 CA*net router in Toronto 3:1392 CA*net router in Montreal 13:602 CA*net router in Montreal Network IP: 192.84.22 Network Name: CELTECH Location: Cellular Technical Services Company, 2401 Fourth Avenue, Suite 808, Seattle, WA 98121, USA Country Code: US 1:174 NYSERNet Regional Network / PSI Network IP: 192.87.74 Network Name: PAR-LAN Location: Stichting Academisch Rekencentrum, Science Park Watergraafsmeer (WCW), Amsterdam, NETHERLANDS Country Code: NL 1:513 EASInet / CERN Network IP: 192.88.124 Network Name: MIAMI-ECE Location: University of Miami, Department of Electrical and Computer Engineering, McArthur Building, Room 414, 1251 Memorial Drive, Coral Gables, FL 33146, USA Country Code: US 1:297 Nasa Science Network (FIX-East) 2:86 SURANET Regional Network (College Park) Network IP: 192.98.22 Network Name: VTYH-NET Location: Vasa Tekniska Yrkeshoegskola, Wolfskavaegen 33, PB 6, SF-65201 Vasa, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 192.104.85 Network Name: SPSS1 Location: SPSS, Inc., 444 N. Michigan Avenue, Chicago, IL 60611, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 192.139.190 Network Name: LAMBTON1 Location: Lambton College, 1457 London Rd., Box 969, Sarnia, ON N7T 7K4, CANADA Country Code: CA 1:1391 CA*net router in Toronto 2:1392 CA*net router in Montreal 3:1393 CA*net router in Quebec 12:602 CA*net router in Montreal Network IP: 192.150.93 Network Name: UTPAB Location: University of Texas at Brownsville, 1614 Ridgely Road, Brownsville, TX 78520, USA Country Code: US 1:280 SESQUINET Regional Network 2:114 SESQUINET Regional Network Network IP: 192.187.154 Network Name: NETCOM57 Location: Netcom On-line Communications Services, 4000 Moorpark Avenue - Suite 209, San Jose, CA 95117, USA Country Code: US 1:200 BARRNet 2:201 BARRNet Network IP: 192.197.62 Network Name: NIAGARA1 Location: Niagara College of Applied Arts and Technology, P.O. Box 1005, Woodlawn Road, Welland, Ontario, CANADA Country Code: CA 1:1391 CA*net router in Toronto 2:1392 CA*net router in Montreal 3:1393 CA*net router in Quebec 12:602 CA*net router in Montreal Network IP: 192.203.45 Network Name: ATHENA Location: Athena Design, Inc., 17 Saint Mary's Court, Boston, MA 02146, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.69 Network Name: AWS-NET Location: Atlas Wireline Services, 10205 Westheimer, Suite 1000, Houston, TX 77042, USA Country Code: US 1:701 Alternet 2:702 Alternet 3:279 SURANET Regional Network (Georgia Tech) Network IP: 192.203.233 Network Name: MORRIS-NET Location: County College of Morris, 214 Grove Road, Randolph, NJ 07869, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.207.159 Network Name: PPL-1 Location: Pocatello Public Library, Brian Hughes, Idaho State Univeristy, Computer Center, Campus Box 8037, Pocatello, ID 83209-8037, 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.231.207 Network Name: RARITANVAL Location: Raritan Valley Community College, PO Box 3300, Somerville, NJ 08876, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.231.231 Network Name: IONA Location: Iona College, Computing Center, 715 North Avenue, New Rochelle, NY 10801, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.231.232 Network Name: ESSEXCOUNTY Location: Essex County College, 303 University Avenue, Newark, NJ 07102, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.231.233 Network Name: BUCKSCOUNTY Location: Bucks County Community College, Newtown, PA 18940, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.231.234 Network Name: ITHACA2 Location: Ithaca College, OIT, Phillips Hall, Danby Road, Ithaca, NY 14850, USA Country Code: US 1:97 JvNCnet Regional Network Network IP: 192.233.2 Network Name: ELMS Location: College of Our Lady of the Elms, 291 Springfield Street, Chicopee, MA 01013, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.233.7 Network Name: MILES4 Location: Miles Research Center, D1, 400 Morgan Lane, West Haven, CT 06516, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.233.40 Network Name: JAXLAB0 Location: The Jackson Laboratory, Computing Service, 600 Main Street, Bar Harbor, ME 04609, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.233.41 Network Name: JAXLAB1 Location: The Jackson Laboratory, Computing Service, 600 Main Street, Bar Harbor, ME 04609, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.233.42 Network Name: JAXLAB2 Location: The Jackson Laboratory, Computing Service, 600 Main Street, Bar Harbor, ME 04609, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.233.43 Network Name: JAXLAB3 Location: The Jackson Laboratory, Computing Service, 600 Main Street, Bar Harbor, ME 04609, USA Country Code: US 1:560 NEARnet Regional Network 2:281 NEARnet Regional Network 5:701 Alternet Network IP: 192.245.119 Network Name: FRB-MPLS-NET Location: Federal Reserve Bank of Minneapolis, Research Department, 250 Marquette Avenue, Minneapolis, MN 55401, USA Country Code: US 1:267 CICNET at UIUC 2:1225 CICNET at Argonne Labs 3:266 CICNET at MERIT Network IP: 193.120.16 Network Name: ICLITC-C16 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.17 Network Name: ICLITC-C17 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.18 Network Name: ICLITC-C18 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.19 Network Name: ICLITC-C19 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.20 Network Name: ICLITC-C20 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.21 Network Name: ICLITC-C21 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.22 Network Name: ICLITC-C22 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.23 Network Name: ICLITC-C23 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.24 Network Name: ICLITC-C24 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.25 Network Name: ICLITC-C25 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.26 Network Name: ICLITC-C26 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.27 Network Name: ICLITC-C27 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.28 Network Name: ICLITC-C28 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.29 Network Name: ICLITC-C29 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.30 Network Name: ICLITC-C30 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.120.31 Network Name: ICLITC-C31 Location: ICL Information Technology Centre Ltd., South Country Business Park, Leopardstown, Dublin 18, IRELAND Country Code: IE 1:701 Alternet Network IP: 193.136.224 Network Name: UALNET-1 Location: Universidade do Algarve, Campus de Gambelas, 8000 Faro, PORTUGAL Country Code: PT 1:701 Alternet Network IP: 193.166.18 Network Name: DOMLANG-NET Location: Finnish Research Centre for Domestic Languages, Sornaisten Rantatie 25, sf-00500 Helsinki, FINLAND Country Code: FI 1:1800 ICM (FIX-East) 2:701 Alternet Network IP: 198.17.24 Network Name: PEOCU-NET-1 Location: PEO(CU), ATTN: PEO (CU)-B23, WASHINGTON, DC 20361-1014, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 198.17.25 Network Name: PEOCU-NET-2 Location: PEO(CU), ATTN: PEO (CU)-B23, WASHINGTON, DC 20361-1014, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 198.17.26 Network Name: PEOCU-NET-3 Location: PEO(CU), ATTN: PEO (CU)-B23, WASHINGTON, DC 20361-1014, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 198.17.27 Network Name: PEOCU-NET-4 Location: PEO(CU), ATTN: PEO (CU)-B23, WASHINGTON, DC 20361-1014, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 198.17.28 Network Name: PEOCU-NET-5 Location: PEO(CU), ATTN: PEO (CU)-B23, WASHINGTON, DC 20361-1014, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Network IP: 198.17.29 Network Name: PEOCU-NET-6 Location: PEO(CU), ATTN: PEO (CU)-B23, WASHINGTON, DC 20361-1014, USA Country Code: US 1:184 Milnet (FIX-East) 2:164 Milnet (FIX-West) Total configured T3 networks: 8151 The following T3 routers have also been added: AS Number: 602 AS Notes: CA*net router in Montreal AS Country Code: CA ANS: No BkBn: 690 NSS: 140.222.143 - ENSS143 University of Washington Gate: 192.35.180.25 - CA*Net Seattle RT ENSS 143 -- Seattle AS Number: 1740 AS Notes: CERFnet AS Country Code: US ANS: No BkBn: 690 NSS: 140.222.135 - sd-enss San Diego, California Gate: 132.249.32.15 - hang-fddi.cerf.net ENSS 135 - San Diego ***************************************************************** 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)merit.edu

1 0

Re: Additions to the NSFNET policy-based routing database
by Susan Horvath 10 Dec '92

10 Dec '92

> Date: Wed, 9 Dec 92 15:03:44 EST > To: skw(a)merit.edu (Steven K. Widmayer) > Cc: nwg(a)merit.edu > From: aggarwal(a)nisc.jvnc.net (Vikas Aggarwal) > Any idea to make this entire structure available via gopher+wais ? > It would make things a lot easier to remember. The entire collection available via Anonymous FTP is indeed available via gopher. "Merit Network" is registered on the main gopher server at the University of Minnesota. Once you have reached our server, choose Option 2: "Anonymous FTP - nic.merit.edu". We are considering making the configuration part of the tree available more directly within our gopher server, as well as WAIS-ifying it. We will post to this group if additional facilities are added. -Susan Horvath Merit/NSFNET Information Services

1 0

CERT Advisory - Cisco Access List Vulnerability
by CERT Advisory 10 Dec '92

10 Dec '92

CA-92:20 CERT Advisory December 10, 1992 Cisco Access List Vulnerability ----------------------------------------------------------------------------- The CERT Coordination Center has received information concerning a vulnerability with Cisco routers when access lists are utilized. This vulnerability is present in Cisco software releases 8.2, 8.3, 9.0 and 9.1. Cisco Systems and CERT strongly recommend that sites using Cisco routers for firewalls take immediate action to eliminate this vulnerability from their networks. This vulnerability is fixed in Cisco software releases 8.3 (update 5.10), 9.0 (update 2.5), 9.1 (update 1.1) and in all later releases. Customers who are using software release 8.2 and do not want to upgrade to a later release should contact Cisco's Technical Assistance Center (TAC) at 800-553-2447 (Internet: tac(a)cisco.com) for more information. The following interim releases are available via anonymous FTP from ftp.cisco.com (131.108.1.111). Note: this FTP server will not allow filenames to be listed or matched with wildcards. You also cannot request the file by its full pathname. You must first cd to the desired directory (beta83_dir, beta90_dir, or beta91_dir) and then request the file desired (gs3-bfx.83-5.10, etc.). Release (Update) Filename Size Checksum 8.3 (5.10) /beta83_dir/gs3-bfx.83-5.10 1234696 02465 1206 9.0 (2.5) /beta90_dir/gs3-bfx.90-2.5 1705364 47092 1666 9.1 (1.1) /beta91_dir/gs3-k.91-1.1 2005548 59407 1959 These releases are also available on Cisco's Customer Information On-Line (CIO) service for those customers having a maintenance contract. Other customers may obtain these releases through Cisco's Technical Assistance Center or by contacting their local Cisco distributor. ----------------------------------------------------------------------------- I. Description A vulnerability in Cisco access lists allows some packets to be erroneously routed which one would expect to be filtered by the access list and vice-versa. This vulnerability can allow unauthorized traffic to pass through the gateway and can block authorized traffic. II. Problem If a Cisco router is configured to use extended IP access lists for traffic filtering on an MCI, SCI, cBus or cBusII interface, and the IP route cache is enabled, and the "established" keyword is used in the access list, then the access list can be improperly evaluated. This can permit packets which should be filtered and filter packets which should be permitted. III. Workaround This vulnerability can be avoided by either rewriting the extended access list to not use the "established" keyword, or by configuring the interface to not use the IP route cache. To disable the IP route cache, use the configuration command "no ip route-cache". Example for a serial interface: router>enable Password: router#configure terminal Enter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Z interface serial 0 no ip route-cache ^Z router#write memory IV. Solution Obtain and install the appropriate interim release listed above. Sites which are not experienced at this installation process should contact the TAC center at 800-553-2447 for assistance. --------------------------------------------------------------------------- The CERT Coordination Center wishes to thank Keith Reynolds of the Santa Cruz Operation for his assistance in identifying this problem and Cisco Systems for their assistance in providing technical information for this advisory. --------------------------------------------------------------------------- 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

CERFnet Weekly Report for the week of Monday, November 30, 1992.
by Donna Bigley 10 Dec '92

10 Dec '92

############################################################################### This is the CERFnet weekly activity report for the period of Monday, November 30th through Sunday, December 6th, 1992. This report is also available through anonymous FTP from NIC.CERF.NET [192.102.249.3] in the cerfnet/cerfnet_stats subdirectory. The filename is: 6-dec-92.txt All times are in Pacific Standard Time, and in the 24-hour format. Please direct any questions or comments to: donnab(a)cerf.net or help(a)cerf.net ****************************************************************************** NETWORK OUTAGES: TICKET #: 1498 SITE: IRVINE COMPILER (ICC) SITES AFFECTED: IRVINE COMPILER (ICC) TIME STARTED: MON. 11-30-92 02:30 TIME ENDED: MON. 11-30-92 08:41 TIME STARTED: MON. 11-30-92 09:29 TIME ENDED: MON. 11-30-92 13:52 TIME STARTED: TUE. 12-01-92 15:07 TIME ENDED: TUE. 12-01-92 15:35 TIME ELAPSED: 10 hours 2 min. REASON: Equipment Trouble TICKET #: 1493 SITE: AJS SITES AFFECTED: AJS TIME STARTED: MON. 11-30-92 05:19 TIME ENDED: MON. 11-30-92 11:57 TIME ELAPSED: 6 hours 38 min. REASON: Link Failure TICKET #: 1504 SITE: CLAREMONT SITES AFFECTED: CLAREMONT TIME STARTED: TUE. 12-01-92 04:30 TIME ENDED: TUE. 12-01-92 04:49 TIME ELAPSED: 19 min. REASON: Site Activity TICKET #: 1512 SITE: SERI/KOREA SITES AFFECTED: SERI/KOREA TIME STARTED: THU. 12-03-92 04:32 TIME ENDED: THU. 12-03-92 05:05 TIME STARTED: FRI. 12-04-92 08:04 TIME ENDED: FRI. 12-04-92 15:32 TIME ELAPSED: 8 hours 1 min REASON: Link Failure (In Korea) TICKET #: 1515 SITE: API SITES AFFECTED: API TIME STARTED: THU. 12-03-92 09:19 TIME ENDED: THU. 12-03-92 09:30 TIME ELAPSED: 11 min REASON: CERFnet Scheduled Maintenance TICKET #: 1509 SITE: GETTY SITES AFFECTED: GETTY TIME STARTED: THU. 12-03-92 09:47 TIME ENDED: THU. 12-03-92 11:51 TIME ELAPSED: 2 hours 4 min REASON: Site Activity TICKET #: 1511 SITE: PAGESAT SITES AFFECTED: PAGESAT TIME STARTED: THU. 12-03-92 15:05 TIME ENDED: FRI. 12-04-92 15:39 TIME ELAPSED: 34 min REASON: Equipment Trouble TICKET #: 1513 SITE: REDE RIO/BRAZIL SITES AFFECTED: REDE RIO/BRAZIL TIME STARTED: THU. 12-03-92 18:05 TIME ENDED: FRI. 12-04-92 12:44 TIME ELAPSED: 18 hours 39 min REASON: Software Trouble (Intermittent Access during this time.) TICKET #: 1514 SITE: EMULEX SITES AFFECTED: EMULEX TIME STARTED: THU. 12-03-92 23:38 TIME ENDED: FRI. 12-04-92 23:52 TIME ELAPSED: 14 min REASON: Unknown TICKET #: 1518 SITE: CITOH SITES AFFECTED: CITOH TIME STARTED: SAT. 12-05-92 04:30 TIME ENDED: MON. 12-07-92 09:01 TIME ELAPSED: 2 days 4 hours 31 min REASON: Equipment trouble TICKET #: 1532 SITE: UCI SITES AFFECTED: CCCD, FULLERTON, EMULEX, UNOCAL, MTI, SPARTA, CMD, MDC, BECKMAN, IRVINE COMPILER CORPORATION, SYMBOL, WDC, CITOH AND UCI DIAL N' CERF. TIME STARTED: SAT. 12-05-92 10:58 TIME ENDED: SAT. 12-05-92 11:22 TIME ELAPSED: 24 min REASON: Site Scheduled Maintenance ------------------------------------------------------------------------ NETWORK ACTIVITY/OUTAGES SCHEDULED: OUTAGE DATE/TIME REASON SITES AFFECTED ------ --------- ------ -------------- SDSC DEC. 14 Router Upgrade SAIC, QUALCOMM, 18:00 - 20:00 USD, SERI/KOREA, USIU, CICESE, SDGE, API, CERF_GA, REDE RIO, SCI-HORIZON, LJCRF, AGI, BIOSYM, SEASPACE, PAGESAT, UCSD, AND SDSC DIAL N' CERF ------------------------------------------------------------------------ CERFNET TRAFFIC CAPACITY USAGE AT EACH CIRCUIT LINK LINK SPEED CAPACITY PEAK HOUR (PST) UCI/CALTECH 45.000 mbps 00.2% 14:00 SDSC/GA 10.000 mbps 00.2% 02:00 SDSC/CALTECH 1.544 mbps 14.8% 15:00 SDSC/UCI 1.544 mbps 8.9% 12:00 SDSC/UCLA 1.544 mbps 9.3% 17:00 SDSC/UCOP 1.544 mbps 5.5% 15:00 SDSC/UCR 1.544 mbps 1.1% 17:00 UCI/UCLA 1.544 mbps 1.4% 14:00 UCLA/UCSB 512 kbps 10.5% 14:00 CALTECH/HUGHES 1.544 mbps 0.1% 13:00 SDSC/AGI 1.544 mbps 0.1% 05:00 SDSC/BIOSYM 1.544 mbps 0.2% 13:00 SDSC/GD 1.544 mbps 1.1% 10:00 SDSC/PAGESAT 1.544 mbps 1.8% 11:00 SDSC/SAIC 1.544 mbps 1.6% 13:00 SDSC/SEASPACE 1.544 mbps 0.3% 12:00 UCI/CSU CO(SWRL) 1.544 mbps 5.1% 16:00 UCI/MDC 1.544 mbps 2.6% 12:00 UCLA/GETTY 1.544 mbps 0.3% 17:00 UCOP/APPLE 1.544 mbps will be available next week. UCOP/CISCO 1.544 mbps will be available next week. UCR/LLUMC 1.544 mbps 1.4% 17:00 CALTECH_CUST/AJS 56 kbps 2.6% 14:00 CALTECH_CUST/CADAM 56 kbps 1.8% 10:00 CALTECH_CUST/CITY OF HOPE 56 kbps 2.4% 08:00 CALTECH_CUST/CLAREMONT 56 kbps 28.2% 15:00 CALTECH_CUST/DASSAULT 56 kbps 0.4% 11:00 CALTECH_CUST/DISNEY 56 kbps 8.0% 09:00 CALTECH_CUST/OXY 56 kbps 12.9% 13:00 CALTECH_CUST/SCAQMD 56 kbps 0.2% 11:00 SDSC/API 56 kbps 6.1% 23:00 SDSC/CICESE 56 kbps 2.1% 09:00 SDSC/KOREA 56 kbps 13.2% 21:00 SDSC/LJCRF 56 kbps 0.7% 15:00 SDSC/QUALCOMM 56 kbps 14.3% 15:00 SDSC/REDE-RIO 56 kbps 10.1% 11:00 SDSC/SCIH 56 kbps 6.3% 18:00 SDSC/SDG&E 56 kbps 0.7% 19:00 SDSC/USD 56 kbps 9.8% 11:00 SDSC/USIU 56 kbps 3.4% 20:00 UCI/BECKMAN 56 kbps 7.3% 18:00 UCI/CCCD 56 kbps 3.7% 16:00 UCI/CMD 56 kbps 0.6% 21:00 UCI/EMULEX 56 kbps 3.0% 09:00 UCI/FULLERTON 56 kbps 2.5% 14:00 UCI/HUGHES 56 kbps 15.6% 15:00 UCI/ICC 56 kbps 6.1% 21:00 UCI/MTI 56 kbps 4.4% 17:00 UCI/SPARTA 56 kbps 8.2% 02:00 UCI/SYMBOL 56 kbps 0.4% 20:00 UCI/UNOCAL 56 kbps 9.8% 14:00 UCLA/CRSS 56 kbps 0.3% 15:00 UCLA/CSMC 56 kbps 3.4% 09:00 UCLA/DATAPRODUCTS 56 kbps 1.5% 10:00 UCLA/GTE 56 kbps 4.4% 09:00 UCLA/ISX 56 kbps 2.9% 13:00 UCLA/LITTON 56 kbps 0.5% 15:00 UCLA/PEPPERDINE 56 kbps 1.5% 07:00 UCLA/QUOTRON 56 kbps 6.4% 06:00 UCLA/SMC 56 kbps 6.0% 19:00 UCOP/FARALLON 56 kbps 7.5% 18:00 UCOP/INTEL 56 kbps 26.8% 10:00 UCOP/LSIL 56 kbps 7.3% 22:00 UCOP/NETLABS 56 kbps 8.5% 22:00 ------------------------------------------------------------------------------ SITE CISCO BOX UPTIME SINCE LAST REBOOT (as of 00:15 PST on Dec. 7, 1992): CERFnet BACKBONE CALTECH [131.215.139.253] Up: 30 days 06 hours 08 minutes CALTECH_CUST [134.24.94.2] Up: 73 days 11 hours 26 minutes SDSC LongBoard [134.24.99.254] Up: 38 days 13 hours 15 minutes SDSC Drzog [132.249.16.13] Up: 59 days 07 hours 12 minutes SDSC Hang10 [132.249.16.15] Up: 46 days 06 hours 55 minutes UCI [128.200.242.101] Up: 01 days 17 hours 50 minutes [Site Scheduled Maintenance - See Ticket #1532] UCI_CUST [134.24.92.3] Up: 01 days 17 hours 50 minutes [Site Scheduled Maintenance - See Ticket #1532] UCLA [128.97.130.10] Up: 31 days 05 hours 23 minutes UCOP [134.24.52.112] Up: 02 days 12 hours 57 minutes [CERFnet Site Activity] UCR [134.24.108.105] Up: 33 days 06 hours 56 minutes CERF 1544 AGI [134.24.202.110] Up: 37 days 03 hours 12 minutes APPLE [134.24.70.200] Up: 04 days 05 hours 05 minutes [CERFnet Site Activity] BIOSYM [134.24.57.200] Up: 178 days 07 hours 13 minutes CISCO Systems [134.24.54.200] Up: 03 days 10 hours 32 minutes [CERFnet Site Activity] CSUCO/SWRL [130.150.102.200] Up: 128 days 18 hours 22 minutes GA [134.24.20.10] Up: 33 days 04 hours 51 minutes GD [134.24.60.200] Up: 00 days 13 hours 47 minutes [Site Activity] GETTY [134.24.235.200] Up: 115 days 07 hours 02 minutes HUGHES_CIT [134.24.103.200] Up: 77 days 11 hours 11 minutes LLUMC [134.24.208.200] Up: 127 days 13 hours 45 minutes MDC [134.24.65.200] Up: 114 days 08 hours 00 minutes PAGESAT [134.24.62.200] Up: 02 days 08 hours 55 minutes [Equipment Trouble] SAIC [134.24.53.208] Up: 207 days 14 hours 10 minutes UCSB [134.24.107.107] Up: 34 days 08 hours 41 minutes WDC [134.24.82.200] Up: 16 days 16 hours 07 minutes CERF 56 AJS [134.24.104.200] Up: 117 days 13 hours 24 minutes API [134.24.224.200] Up: 44 days 08 hours 20 minutes BECKMAN [134.24.237.200] Up: 33 days 10 hours 15 minutes CADAM [134.24.239.200] Up: 43 days 11 hours 46 minutes CCCD [134.24.219.200] Up: 44 days 09 hours 29 minutes CICESE [134.24.227.200] Up: 35 days 04 hours 09 minutes CITY_OF_HOPE [134.24.233.200] Up: 23 days 11 hours 49 minutes CLAREMONT [134.24.206.109] Up: 05 days 19 hours 27 minutes [Site Activity - See Ticket #1504] CMD [134.24.218.200] Up: 93 days 07 hours 29 minutes CRSS [134.24.232.200] Up: 123 days 12 hours 16 minutes CSMC [134.24.243.200] Up: 03 days 13 hours 55 minutes [CERFnet Site Activity] DASSAULT [134.24.229.200] Up: 43 days 12 hours 16 minutes DATAPRODUCTS [134.24.211.200] Up: 35 days 17 hours 29 minutes DISNEY [134.24.207.211] Up: 111 days 19 hours 57 minutes EMULEX [134.24.209.212] Up: 16 days 17 hours 07 minutes FARALLON [134.24.56.200] Up: 13 days 09 hours 05 minutes FULLERTON [134.24.214.217] Up: 45 days 13 hours 14 minutes GTE [134.24.212.200] Up: 40 days 19 hours 15 minutes HUGHES [134.24.204.200] Up: 72 days 13 hours 34 minutes INTEL [134.24.73.200] Up: 253 days 11 hours 34 minutes ICC [134.24.238.200] Up: 02 days 11 hours 04 minutes [Unknown] LITTON [134.24.213.200] Up: 12 days 08 hours 11 minutes LJCRF [134.24.244.200] Up: 00 days 09 hours 57 minutes [Power Outage] LSIL [134.24.72.200] Up: 55 days 13 hours 24 minutes MTI [134.24.216.100] Up: 103 days 08 hours 48 minutes NETLABS [134.24.71.200] Up: 38 days 14 hours 03 minutes OXY [134.24.205.108] Up: 46 days 15 hours 32 minutes PEPPERDINE [134.24.203.218] Up: 240 days 21 hours 42 minutes QUALCOMM [134.24.200.201] Up: 19 days 04 hours 44 minutes QUOTRON [134.24.230.202] Up: 105 days 06 hours 06 minutes REDE_RIO [134.24.112.200] Up: 23 days 20 hours 12 minutes SANTA MONICA [134.24.210.219] Up: 130 days 13 hours 40 minutes SCAQMD [134.24.234.200] Up: 16 days 08 hours 47 minutes SCI-HOR [134.24.109.205] Up: 208 days 06 hours 02 minutes SDG&E [134.24.226.200] Up: 52 days 08 hours 03 minutes SEASPACE [134.24.80.200] Up: 33 days 12 hours 52 minutes SERI/KOREA [134.24.223.200] Up: 06 days 01 hours 04 minutes [Unknown] SPARTA [134.24.215.200] Up: 15 days 13 hours 03 minutes SYMBOL [134.24.245.200] Up: 31 days 13 hours 36 minutes UNOCAL [134.24.217.200] Up: 275 days 01 hours 57 minutes USD [134.24.201.106] Up: 118 days 17 hours 00 minutes USIU [134.24.222.215] Up: 64 days 13 hours 43 minutes DIAL n' CERF Plus 14.4 CITOH [161.1.1.1] Down at the time. [Equipment Trouble - See Ticket #1518] EXPERSOFT [192.231.76.1] Up: 16 days 14 hours 01 minutes GOMPERS [192.207.233.2] Up: 12 days 10 hours 03 minutes MARKV [192.122.251.6] Up: 59 days 12 hours 65 minutes PEREGRINE [192.72.253.97] Up: 36 days 23 hours 44 minutes DIAL n' CERF DNC-SDSC [134.24.1.2] Up: 76 days 04 hours 58 minutes DNC-UCI [134.24.2.2] Up: 01 days 17 hours 50 minutes [Site Scheduled Maintenance - See Ticket #1532] DNC-UCLA [134.24.3.2] Up: 23 days 15 hours 05 minutes DNC-CALTECH [134.24.4.2] Up: 10 days 10 hours 00 minutes DNC-UCOP [134.24.5.2] Up: 160 days 04 hours 29 minutes CIT-NETBLAZER [130.152.104.1] Up: 73 days 08 hours 35 minutes SDSC-NETBLAZER [192.102.249.25] Up: 16 days 06 hours 41 minutes UCI-NETBLAZER [134.24.92.2] Up: 01 days 08 hours 41 minutes [Site Scheduled Maintenance - See Ticket #1532] UCLA-NETBLAZER [134.24.93.2] Up: 31 days 16 hours 30 minutes UCOP-NETBLAZER [134.24.250.2] Up: 257 days 23 hours 54 minutes

1 0