The database servers for umich.edu are moving to a new
network address.  This places the database servers
on an FDDI network rather than ethernet; which should
lead to better reliability and performance.  This is
a rather extreme change, in the sense that it will
break anything that is not updated, but one we hope
will not be needed again for many years.

There are up to 3 issues that affect machines that use the
umich.edu cell.

1.______CellServDB

The old database servers were (in CellServDB format):
>umich.edu                #University of Michigan - Campus
141.211.168.24                  #beachhead.ifs.umich.edu
141.211.168.25                  #toehold.ifs.umich.edu
141.211.168.28                  #bastion.ifs.umich.edu

The new servers are:
>umich.edu                #University of Michigan - Campus
141.211.1.32                    #fear.ifs.umich.edu
141.211.1.33                    #surprise.ifs.umich.edu
141.211.1.34                    #ruthless.ifs.umich.edu

As an interim measure, we are currently running 6 database
servers; so the old addresses will continue to work.  It turns out,
however, that using only the original 3 only works in a "read-only"
fashion; for full functionality, all sites should upgrade to the new
set of three in /usr/vice/etc/CellServDB as soon as possible.
This "read-only" access doesn't affect file access (files can be
read and written as usual) but does affect changing kerberos passwords
and updating PTS entries.  The old addresses are not guaranteed to
work past 23:59 EST Friday, November 13, 1992.  (My lucky day.)

The CellServDB files
/afs/umich.edu/group/itd/umich/admin/cellservdb/default/CellServDB
/afs/umich.edu/group/itd/umich/admin/cellservdb/default/CellServDB.local
have already been updated to reflect this change.  Workstations
in the umich.edu cell that update their CellServDB via the appropriate
cron script (such as
/afs/umich.edu/group/itd/umich/admin/cellservdb/.cellupdate.host)
should soon pick this change up automatically.

2.______krb.conf

For places that use MIT style kerberos with the umich.edu
cell, the file /etc/krb.conf should also be changed.

old entries:
UMICH.EDU beachhead.ifs.umich.edu admin server
UMICH.EDU toehold.ifs.umich.edu admin server
UMICH.EDU bastion.ifs.umich.edu admin server

new entries:
UMICH.EDU fear.ifs.umich.edu admin server
UMICH.EDU surprise.ifs.umich.edu admin server
UMICH.EDU ruthless.ifs.umich.edu admin server

As a conversion aid, at the same time the uniqname server is moved,
the DNS addresses for beachhead, toehold, and bastion will be changed
to point to fear, surprise, and ruthless - see next section.

A copy of krb.conf (and krb.realms) can be found in
the directory /afs/umich.edu/group/itd/etc, and this will be updated
when the uniqname server is moved.  Most umich.edu machines can probably
use this file without change (ie, symlinks).

There is no reason *NOT* to immediately upgrade any machine with
krb.conf files referencing UMICH.EDU, *except* for umich machines on which
the uniqname client software (uns, unq, uniqcreate) is run.

3.______uniqname

Uniqname is used by the University of Michigan to allocate
loginids.  This is not an issue for machines outside of
the university of michigan.

The krb.conf entries are of special importance for uniqname
administrators - the uniqname server is located on the first
host in the krb.conf file, and is not replicated.  Therefore,
at the same time that the uniqname server is moved, the
DNS names will be changed to point to the new server.
Therefore, machines on which the uniqname client software 
IS run, should not be changed until the uniqname server
is moved.  This will happen late Wednesday night, that is,
the night of November 11-12, 1992.

                        -Marcus Watts
                        UM ITD RS Umich Systems Group

Reply via email to