home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Garbo
/
Garbo.cdr
/
mac
/
source
/
kboot22.zoo
/
kboot22.2
/
README
< prev
Wrap
Text File
|
1991-02-22
|
4KB
|
99 lines
Kboot is a program used to monitor, boot and configure Shiva Fastpaths
from a sun running SunOS 4.x. It was originally written by Dan Tappan
of BBN, and ran under SunOS 3.5. I've ported it to SunOS 4.x and
added support for KSTAR version 8.0 and up. Complaints, suggestions
and bug fixes can be sent to me.
Bob Schwartzkopf
The RAND Corporation
1700 Main Street
PO Box 2138
Santa Monica, Ca. 90407-2138
bobs@rand.org
The kboot package consists of 2 separate programs, kboot and aarpd.
kboot is the program that monitors, configures and downloads Shiva
Fastpaths; aarpd implements some of the Appletalk ARP protocol.
Aarpd obtains an Appletalk node number dynamically for the
local host; kboot queries aarpd via an RPC call to learn the
node number it should use when communicating with Fastpaths.
Please note that kboot and aarpd must be run on a sun on the same
ethernet as the Fastpaths it will be talking to, as it depends on
broadcasts to learn the Appeltalk addresses of each Fastpath specified
in its configuration file.
To build kboot and aarpd:
- Edit Makefile and set ETCDIR and MANDIR
- Edit config.h as necessary
- make
To install:
- make install
- make install.man
Once kboot and aarpd are installed you must create the following
files in ETCDIR:
kbootcf - kboot configuration file.
KSTAR - KSTAR software, which comes with Fastpath Manager and is also
available via anonymous ftp from shiva.com.
You will also need a configuration file for each Fastpath. These
files also are installed in ETCDIR with the name FASTPATH.config
or FASTPATH.state, where FASTPATH is the hostname of the Fastpath.
The .config files are ascii configuration files created by Fastpath
Manager. The .state files are binary files created by kboot, which
has an option to read the state of a currently running Fastpath
and save it to ETCDIR/FASTPATH.state.
The kboot configuration file (ETCDIR/kbootcf) contains a list of
FASTPATH hostnames followed by the name of the KSTAR image to download.
For example, if you have 2 Fastpaths, one running 7.0.1 and the other
running 8.0, you could copy the appropriate KSTAR software to
ETCDIR/KSTAR-7.0.1 and ETCDIR/KSTAR-8.0. Your kbootcf file would
then look like:
fastpath1 KSTAR-7.0.1
fastpath2 KSTAR-8.0
Kboot learns the ethernet address of each configured Fastpath by
looking at the ethernet header of the packets sent to it by each Fastpath.
It verifies that address with the address in the ethers NIS map (or
file if you're not running NIS), so it is necessary that each
configured Fastpath have its ethernet address entered in the ethers map.
Kboot will complain about unknown Fastpaths if the ethers map
is not correct.
NOTE: The appletalk phase II zonelist (specified in Fastpath
Manager) is not included in the Fastpath configuration
structure. Hence it is not downloaded when a Fastpath
is configured. Instead, it is converted into s-records
and downloaded with the KSTAR software. Since a zonelist
is not part of the configuration structure, the configuration
read by kboot and stored in ETCDIR/FASTPATH.state will not
contain the zonelist in use by the Fastpath.
The Fastpath Manager software does include the zonelist in
the ascii configuration file, and kboot knows how to read
it from there, convert it to s-records, and download it to
the Fastpath. Hence, if you're running Appletalk phase II,
and have a non empty zonelist, you cannot use the binary
state files generated by kboot. You must instead use
Fastpath manager to create an ascii configuration file which
includes the zonelist and copy it to ETCDIR.
Since I have no documentation on the Fastpath I had to reverse
engineer the format of the s-records, the address where they're
stored in the Fastpath, and how they're encoded in the
configuration file. My thanks to Phil Budne of Shiva who
helped me with some of this stuff. I don't guarantee this
code is perfect (especially since we're not running phase II
yet), however the one test I ran did seem to work. Please
let me know if you have any problems with zonelists, or any
other part of kboot for that matter.