                5.7p6 BootP/TFTP Information

This archive contains files which need only be used if you intend to
use Bootp and TFTP to download firmware for your Shiva(R) LanRover(tm)
device.

Your network must have BootP and TFTP servers to use this function of
the Shiva devices; see your system administrator to request
installation of these servers, or to change your BootP configuration
file.

The BootP files contain a set of downloadable versions of the Shiva
device's image and VROM which should be used should it be necessary to
reload the firmware.

LanRover Files
" ble57p6.tar " is a UN*X tar file which contains files for LanRover Ethernet devices.

" blt57p6.tar " is a UN*X tar file which contains files for LanRover Token Ring devices.

1) The tar file may be used to extract the downloadable versions. The
resulting files may be used with Shiva Net Manager for Windows*, with
a UN*X BootP/TFTP server, or with a Windows-based TFTP Server. If
using FTP to transfer files, be sure the transfer is in binary mode.

1a) For the tar file with UN*X enter:

LanRover/E:
tar xvf ble57p6.tar.tar

This will produce four files:

lr20.srec.lre.5.7p6
lre2vrom.srec.6.7p6
nme3vrom.srec.6.7p6
BOOTP.TXT


LanRover/T:
tar xvf blt57p6.tar.tar

This will produce four files:

lr20.srec.lrt.5.7p6
lrt2vrom.srec.6.7p6
nmt3vrom.srec.6.7p6
BOOTP.TXT

2) To verify that the data files transferred correctly (to UN*X) use
the checksum command on each file.  The checksums using the BSD
checksum command (usually "/usr/bin/sum" on BSD UN*X systems) should
be:

For " ble57p6.tar " (LanRover/E): 

lr20.srec.lre.5.7p6	- 56133  1592
lre2vrom.srec.6.7p6	- 18548   185
nme3vrom.srec.6.7p6	- 21862   274


For " blt57p6.tar " (LanRover/T):

lr20.srec.lrt.5.7p6	- 12736  1304
lrt2vrom.srec.6.7p6	- 54334   199
nmt3vrom.srec.6.7p6	- 06287   287


NOTE: If you use the UN*X System V checksumming command (normally
"/usr/5bin/sum") then the checksums are:

For " ble57p6.tar ":

18485 3184 lr20.srec.lre.5.7p6
10973 370 lre2vrom.srec.6.7p6
16682 547 nme3vrom.srec.6.7p6

For " blt57p6.tar ":

4637 2607 lr20.srec.lrt.5.7p6
46102 397 lrt2vrom.srec.6.7p6
42907 574 nmt3vrom.srec.6.7p6

3) You can now move these files to the appropriate TFTP directory for
your system.  You will want to make symbolic links to these files for
each Shiva LanRover you are loading using TFTP.  For an overview of
how to use these files see the BootP/TFTP section of the
Administrator's Guide.

The Correct VROM file for use with each LanRover is as follows:

Model			Serial Number Prefix	VROM File
-------------------------------------------------------------------

LanRover/E		HE			 lre2vrom.srec.6.7p6 
LanRover/T		HT			 lrt2vrom.srec.6.7p6 
LanRover/E PLUS	(all serial numbers)	 nme3vrom.srec.6.7p6 
LanRover/T PLUS	(all serial numbers)	 nmt3vrom.srec.6.7p6 

Note: The files for the LanRover PLUS begin with "nme3" and "nmt3" not
"lre3" and "lrt3."

Filename Conventions
--------------------
There are three files which a Shiva device must load via TFTP: VROM,
image, and configuration.  The names of these files on the TFTP server
must match the names which the Shiva device asks for.  These tables
list the filenames which each type of Shiva device requests:

The correct VROM filename for use with each Shiva device is as follows:

Model                   Serial Number Prefix    VROM filename
--------------------------------------------------------------------
LanRover/E              HE                      lre2vrom.srec
LanRover/T              HT                      lrt2vrom.srec
LanRover/E PLUS         (all serial numbers)    nme3vrom.srec
LanRover/T PLUS         (all serial numbers)    nmt3vrom.srec


The correct image filename for use with each Shiva device is as follows:

Model                   Serial Number Prefix    Image filename
--------------------------------------------------------------------
LanRover/E              HE                      lr20.srec
LanRover/T              HT                      lr20.srec
LanRover/E PLUS         (all serial numbers)    nme3imag.srec
LanRover/T PLUS         (all serial numbers)    nmt3imag.srec


The correct configuration filename for use with each Shiva device is as
follows:

Model                   Serial Number Prefix    Config filename
--------------------------------------------------------------------
LanRover/E              HE                      lr20.conf
LanRover/T              HT                      lr20.conf
LanRover/E PLUS         (all serial numbers)    nme3conf.conf
LanRover/T PLUS         (all serial numbers)    nmt3conf.conf

The Shiva device requests the filenames given in the above tables.
However, there is a convention to name the files on the BootP/TFTP
server with the above filenames plus an additional suffix of the
hostname of the device.  The hostname is specified in the BootP
configuration file (normally called "bootptab").

The following examples demonstrate this convention.  In each example
the hostname, as would be configured in the bootptab file for each
device, is appended to the filename which the Shiva device will
request:

For a LanRover/E PLUS with hostname "saleslre" the filenames for this
device on the TFTP server should be:

nme3vrom.srec.saleslre
nme3imag.srec.saleslre
nme3conf.conf.saleslre

For a LanRover/T with hostname "support" and a serial number beginning
with HT the filenames should be:

lrt2vrom.srec.support
lr20.srec.support
lr20.conf.support

Note that this naming convention is used by the BootP daemon from
Carnegie-Mellon University, which is available via anonymous ftp from
"ftp.net.cmu.edu".  Other BootP daemons may use other naming
conventions, and one should make sure to follow the conventions
appropriate for the BootP daemon being used.


The Device Bootstrap Process
----------------------------
The following provides more detail on how a Shiva device boots using
BootP and TFTP.

When a Shiva device is pin reset, or given a Clear & Download command
from Shiva Net Manager, it goes through a five stage bootstrap
process:

(1) The boot PROM in the Shiva device uses BootP to learn its IP
address and name (and perhaps other configuration as provided in the
BootP server's configuration file). (Note: the Shiva device
simultaneously uses RARP to try to learn its IP address. See the
BootP/TFTP section of the Administrator's Guide for more information.)

(2) The PROM then uses TFTP to load the VROM file.

(3) Once the PROM is sure the VROM is valid it transfers control to
the VROM.  The VROM uses TFTP to load the configuration file.

(4) The UVROM also TFTP's the Shiva device's image file.

(5) Once the VROM is sure the image and configuration are valid it
transfers control to the image and the Shiva device completes its boot
process.

All BootP and TFTP requests at all stages of the bootstrap process use
a retry algorithm which includes an increasing randomized backoff in
order to avoid packet storms if a large number of Shiva devices boot
at the same time.

General Notes
-------------
(1) In Shiva Net Manager on the "IP General" page there is a checkbox
called "Always retrieve image configuration from BootP server."  If
this checkbox is checked then the Shiva device will always go through
the bootstrap process starting at step (3) everytime it is cold booted
(such as a power cycle). If this checkbox is not checked then the
Shiva device will only attempt to use BootP as needed. This means that
in most cases the device will not use BootP after a cold boot because
once it has loaded the VROM, image, and configuration they are
preserved in memory, even across a power cycle.

However, it should be noted that even when the checkbox is not checked
if the Shiva device needs to load the VROM, image, or configuration it
will try to use BootP to do this; not checking the ckeckbox does NOT
prevent the device from ever using BootP, only using BootP at every
cold boot.

(2) If one wants to prevent Shiva device from loading via BootP then
remove it from the bootptab configuration file. Do not try to download
a device's VROM or image using Shiva Net Manager at the same time that
the device is using BootP/TFTP to load these files.

Shiva(R) and LanRover(TM) are a trademark and registered trademark of
Intel Corporation or its subsidiaries in the United States and other
countries.

* Other names and brands may be claimed as the property of others.


[File generated Thursday August 15  12:33:48 EST 2002 ]


