IMP/TIP preventive maintenance schedule
Lists the monthly preventive maintenance schedule for IMP and TIP machines.
McKenzie, A.M., "IMP/TIP preventive maintenance schedule", RFC 638, DOI 10.17487/RFC0638, April 1974, <https://www.rfc-editor.org/info/rfc638>.
@misc{rfc638,
series = {Request for Comments},
number = 638,
howpublished = {RFC 638},
publisher = {RFC Editor},
doi = {10.17487/RFC0638},
url = {https://www.rfc-editor.org/info/rfc638},
author = {A.M. McKenzie},
title = {{IMP/TIP preventive maintenance schedule}},
pagetotal = 4,
year = 1974,
month = apr,
} RFC text
Network Working Group Alex A. McKenzie
Request for Comments: 638 BBN-NET
NIC: 30538 April 25, 1974
IMP/TIP Preventive Maintenance Schedule
This RFC corrects numerous inaccuracies in RFC #633. Rather than
trying to list all the changes, I urge all Liaisons and other
interested parties to look carefully at the times now listed for
the sites they are interested in.
This note presents the current IMP/TIP Preventive Maintenance
schedule. Preventive Maintenance is scheduled on a monthly basis and
a given machine is normally scheduled at the same time each month;
wherever possible the time is chosen to coincide with the PM time for
the Host(s) at the site.
It is sometimes necessary to reschedule PM's because of network
connectivity considerations or for other reasons. Whenever this is
necessary we will follow the usual procedure for scheduling down time
with our "primary contact" at the site. Permanent changes to the
schedule will he announced via the RFC mechanism.
PM's normally do not require the IMP/TIP to be taken down. However,
machines must be taken down in some cases, so no one should rely on
the machine remaining available through the PM period.
PLEASE REMEMBER THAT TUESDAY MORNINGS FROM 7am TO 9am ARE RESERVED
FOR NETWORK SOFTWARE MAINTENANCE.
All times shown below are Eastern Time.
First Monday (of each month)
5 BBN IMP [0830-1130]
40 NCC TIP [1130-1430]
47 WRIGHT-PATTERSON [1300-1700]
First Tuesday
30 BBN TIP [0830-1130]
3 UCSB [1130-1430]
First Wednesday
14 CARNEGIE [0830-1130]
2 SRI [1200-1500]
First Thursday
26 SDAC [0830-1130]
4 UTAH [1030-1330]
41 NORSAR [0830-1130]
42 LONDON [0830-1130]
Second Monday
6 MIT-MAC [0830-1130]
44 MIT-IPC [1200-1500]
25 DOCB [1030-1330]
Second Tuesday
17 MITRE [0830-1130]
23 USC [1130-1430]
Second Wednesday
31 CCA [0830-1130]
11 STANFORD [1200-1500]
32 XEROX [1400-1700]
18 RADC [0900-1200]
Second Thursday
27 BELVOIR [0830-1130]
35 UCSD [1130-1430]
37 RML [0930-1230]
Second Friday
43 TYMSHARE [1200-1500]
Third Monday
9 HARVARD [0830-1130]
1 UCLA [1000-1300]
48 KIRTLAND [1600-1900]
Third Tuesday
7 RAND [1130-1430]
8 SDC [1530-1830]
Third Wednesday
12 ILLINOIS [0930-1230]
28 ARPA [1700-2000]
15 AMES IMP [1200-1500]
16 AMES TIP [1300-1600]
36 HAWAII [1430-1730]
45 MOFFETT [1400-1700]
Third Thursday
20 ETAC [0830-1130]
33 FNWC [1300-1600]
Third Friday
21 LLL [1230-1530]
Fourth Monday
13 CASE [0830-1130]
Fourth Tuesday
19 NBS [0830-1130]
Fourth Wednesday
10 LINCOLN [0830-1130]
46 RUTGERS [1000-1400]
Fourth Thursday
24 GWC [1500-1800]
22 ISI [1300-1600]
29 ABERDEEN [1300-1600]
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 2/2000 ]
ISO Plain Language
On this page
§1Correcting the Earlier Schedule
RFC 638 corrects numerous inaccuracies in RFC 633. Rather than listing every change, the author asks liaisons and interested parties to check the times for the sites they care about.
The schedule covers IMP and TIP preventive maintenance, which is normally arranged monthly at a recurring time for each machine.
The previous schedule contained many inaccuracies. The author asks readers to check the corrected time for each site.
§2Maintenance and Availability
Where possible, the maintenance time is chosen to coincide with preventive maintenance for hosts at the site. Rescheduling may be necessary for network connectivity or other reasons, and changes are coordinated with the site's primary contact.
Maintenance normally does not require the IMP or TIP to be taken down, but some cases do. The RFC says not to rely on a machine remaining available during maintenance and reserves Tuesday mornings from 7am to 9am for network software maintenance.
Maintenance is usually coordinated with the site's host schedule. The machine may be unavailable during the window, and Tuesday morning time is reserved for software maintenance.
§3How to Read the Schedule
All listed times are Eastern Time. Sites are grouped under the first, second, third or fourth weekday of each month, with a time range for each machine.
The RFC provides entries across the month rather than one shared maintenance time for every site. It says permanent schedule changes will be announced through the RFC mechanism.
Each machine has a slot identified by the week, weekday and time range. All times in the table are Eastern Time.