RFC 308 UNKNOWN ARPANET · MEASUREMENT

ARPANET host availability data

The MIT-DMCG SURVEY program, which knocked on every ARPANET host every 15 minutes to see who was answering.

On rfc-editor.org ↗
PUBLISHED
March 1972
AUTHORS
M. Seriff
STREAM
Legacy
UPDATED BY
RFC 530 — Report on the Survey Project
SURVEY INTERVAL
15 minutes
TARGET
LOGGER, socket 1
SURVEYS REPORTED
6528
REPORTING PERIOD
12/13/71 to 03/20/72
MIT-DMCG REAL UPTIME
about 66%
DOI
10.17487/RFC0308

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                   Marc Seriff
Request for Comments 308                MIT-DMCG
NIC 9259                                13 MARCH 1972
References: RFC 254

                     ARPANET HOST AVAILABILITY DATA

     Several months ago a SURVEY program was implemented on the
MIT-DMCG ITS PDP-10 system to aid in gathering information on the
availability of various HOSTS on the ARPANET.  The purpose of this
Request for Comments is threefold:

     1. to inform the Network Working Group of the
        existence of this information gathering service
        and about getting access to it,

     2. to present the results of SURVEY for its first
        few months, and

     3. to correct errors in our data or collection methods.

     Briefly, the SURVEY program works as follows: At 15-minute
intervals whenever the MIT-DMCG ITS Time-Sharing system is in normal
operation, a SURVEY is started.  The SURVEY program attempts to
establish a connection to the LOGGER (socket 1) of each HOST listed in
its table.  The results of each connection attempt are recorded for
future reference.  The Initial Connection Protocol is aborted prior to
reading the transmitted socket number so as to cause the minimum
amount of processing at SURVEYed HOSTS.  If the LOGGER connection
succeeds, the average request-for connection response time (in
seconds) for the HOST is updated.  This information can later be
viewed in several formats using the MIT-DMCG server TELNET "NETWRK" as
described below.

     Each test results in the assignment of one of the following
five statuses:

     1.  LOGGER available - connection completed.

     2.  LOGGER not responding - RFC sent (HOST-HOST OK), but
         no response (20 seconds allowed).

     3.  LOGGER rejecting - CLOSE returned by NCP.

     4.  NCP not responding - RESET timed out (15 seconds allowed).

     5.  HOST dead - host-dead status returned by IMP.

Below you will find a summary of the information gathered to
date.  It must be remembered that the SURVEY program can only run when
MIT-DMCG ITS Time-Sharing System is in normal operation and the MIT
IMP is operational.  Thus the current figure of 94% for MIT-DMCG is
inaccurate. (It should actually be closer to 66%.)

     There are, in addition, two other shortcomings of which we are
aware.  The first is that SURVEY is on a 24-hour basis and does _not_
consider advertised up time.  For example, MIT-DMCG will never be
better than 67% on a Tuesday since the machine is always unavailable
from 4 p.m. to midnight.  The second shortcoming is the fact that the
Lincoln Lab's TX-2 shows as "never available".  This reflects an as
yet undiagnosed problem currently under investigation.

     To get availability information from DMCG, you must first follow
the scenario in RFC 254.  Once in NETWRK, the DMCG user-TELNET, there
are seven available commands which pertain to SURVEY data:

     SUMMARY.OF.SURVEYS - summarizes most recent information.

     HISTORY.OF. <host name> - gives a detailed recent history
                    of the given host.  This generates a lot
                    of output, so use it sparingly.

     ACTIVE.HOSTS - lists those hosts who accepted a connection
                    at least once during the last 24 hours.

     BEST.SURVEY - lists the best of the recent surveys.

     LONGTERM SUMMARY.OF.SURVEYS - summarizes all past
                    information.  This was used to generate
                    the table on the next page.


     LONGTERM HISTORY.OF <host name> - gives a summary of
                    past history of the given host.  It
                    does not generate as much output as the
                    HISTORY command.

     LONGTERM ACTIVE.HOSTS - lists those hosts who accepted a
                    connection at least once since December 13,
                    1971.

For the above seven commands, "recent" is define as "within the
last 24 hours or less".

     For help in accessing SURVEY data and comments on improving the
admittedly limited SURVEY service, please contact:

          Marc Seriff
          M.I.T. - Project MAC
          545 Main Street
          Cambridge, Mass. 02139
          (617) 864-6900 ext. 1458

6528 Surveys from 09:55:18 on 12/13/71 to 08:50:41 on 03/20/72
--HOST-- -#- -%-UP- -RESP- *
ucla-nmc 001  064%   00.93
sri-arc  002  064%   02.96
ucsb-75  003  048%   00.53
utah-10  004  057%   03.23
bbn-ncc  005  000%   00.00
multics  006  047%   05.60
rand-rcc 007  000%   00.13
sdcadept 010  000%   02.60
harv-10  011  022%   00.23
ll-67    012  021%   03.70
su-sail  013  000%   00.00
ill-11   014  000%   00.06
case-10  015  000%   00.00
cmu-10   016  034%   00.23
burr     017  000%   00.00
ames-67  020  000%   00.00
radc-645 022  000%   00.00 **
nbs-11   023  000%   00.00 **
tink-418 025  000%   00.00 **
usc-44   027  000%   01.13 **
ncar7600 031  000%   00.00 **
ucla-ccn 101  070%   00.30
sri-ai   102  000%   02.26
tenex    105  060%   02.40
mit-dmcg 106  093%   01.10 ***
rand-csg 107  013%   02.96 **
harv-1   111  000%   00.23
ll-tx2   112  000%   01.76
ill-6500 114  000%   00.00
burrtest 117  000%   00.00 **
tenexb   205  018%   02.93
mit-ai   206  000%   00.00
harv-11  211  000%   00.00

* Remember that "UP is defined as "Logger Accepting connections."
** Surveyed only since February 18, 1972.
*** MIT-DMCG is actually up about 66% of the time.


       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                   12/96   ]

AI ELI5

On this page
PROBLEMUsers and implementers had no regular record of which ARPANET hosts were reachable or how quickly they responded.
MECHANISMA SURVEY program on the MIT-DMCG ITS PDP-10 tries a connection to the LOGGER (socket 1) of each listed host every 15 minutes and records one of five statuses and the response time.
THE CATCHThe RFC reports the first months of data and admits its limits, such as counting scheduled downtime against hosts. The unit metadata lists RFC 530 as an update to it.

§1The SURVEY Program

Several months before this March 1972 note, a SURVEY program was implemented on the MIT-DMCG ITS PDP-10 to gather information on host availability. The RFC has three aims: announce the service and how to reach it, present the first few months of results, and correct errors in the data or methods.

Whenever the ITS time-sharing system is in normal operation, a survey starts at 15-minute intervals. It tries to connect to the LOGGER (socket 1) of each host in its table and records the result. The Initial Connection Protocol is aborted before the socket number is read, to cause the least processing at the surveyed hosts. If the connection succeeds, the host's average response time, in seconds, is updated.

Every fifteen minutes the robot rings each computer's doorbell and runs away before anyone opens, just to see if someone is home and how fast they come.

§2The Five Statuses and the Commands

Each test ends in one of five statuses: LOGGER available (connection completed), LOGGER not responding (RFC sent but no response in 20 seconds), LOGGER rejecting (CLOSE returned by the NCP), NCP not responding (RESET timed out after 15 seconds) and HOST dead (host-dead status returned by the IMP).

To see the data, follow the scenario in RFC 254 and reach NETWRK, the DMCG user Telnet. Seven commands relate to survey data, including SUMMARY.OF.SURVEYS, HISTORY.OF., ACTIVE.HOSTS, BEST.SURVEY and long-term versions covering everything since December 13, 1971. Recent means within the last 24 hours or less.

The robot writes one of five notes for each knock: someone answered, nobody answered, the door was slammed, the whole house was not listening, or the street was empty.

SURVEY STATUS RESULTS (RFC 308)
  • 1LOGGER available — Connection completed.
  • 2LOGGER not responding — RFC sent but no response; 20 seconds allowed.
  • 3LOGGER rejecting — CLOSE returned by the NCP.
  • 4NCP not responding — RESET timed out; 15 seconds allowed.
  • 5HOST dead — Host-dead status returned by the IMP.

§3Results and Their Limits

The table covers 6528 surveys from 09:55:18 on 12/13/71 to 08:50:41 on 03/20/72, listing each host's percentage up and average response. Examples include ucla-ccn at 070% and mit-dmcg at 093%; several hosts show 000%.

The authors name shortcomings. SURVEY only runs when the MIT-DMCG system and its IMP are up, so the 94% figure for MIT-DMCG is inaccurate and should be closer to 66%. It runs around the clock and ignores advertised uptime, so MIT-DMCG can never exceed 67% on a Tuesday. And the Lincoln Lab TX-2 shows as never available because of an undiagnosed problem under investigation. Here, up means that the Logger is accepting connections.

The robot's chart has mistakes it admits to: it only works when its own house has power, and it counts times when computers were announced to be closed.

§4References