Because of the random nature of finding a particular server (it depends on how
busy a server is, and how quickly it responds), it is absolutely necessary that you
copy all boot image files, AUTOEXEC and other .BAT files, and BOOTCONF.SYS
files across all file servers in your internetwork. Failure to do so may cause MBA to
occasionally issue an “Error Opening Boot File” message as it connects to a server
that doesn't contain the required boot image files.
With the MSD NLM option, you can specify the file server(s) from which an MBA-
equipped PC will boot, and maintain boot image files only on the designated
servers.
A full-featured MSD NLM is provided with MBA. This version is unrestricted and
includes activity logging.
How MSD Works
At boot time, MBA-equipped PCs first broadcast a “Get nearest MSD” request. See
Figure 17. One or more file servers reply with the address of the nearest MSD
NLM. MBA then sends a request to the MSD NLM asking for the name of the server
and image file. Upon receiving this request, the NLM looks for the PC's boot
information in the BOOTCONF.SYS file. If a matching entry is found, MSD replies
to the MBA PC with the information.
If no matching PC entry is found, MSD replies with the name of a boot image file
which is specific to the PC's type of NIC (except in cases where the NODEFAULT
option is used). You can obtain the ROMTYPE number from the MBA Information
screen. Also see “Other Tools:
ROMTYPE: Conditional Execution based on MBA
Type
” in this chapter.
If the PC receives no reply from the MSD NLM in two seconds, MBA defaults to its
normal mode of operation and attempts to boot from the nearest file server.
Installing MSD
The MSD NLM is installed on a NetWare file server, although the boot image files
themselves may exist on any file server in the network.
Copy the file MSD NLM from the MBA Utility Disk to the SYSTEM directory on the
SYS: volume of the server that is used to load the MSD NLM.
The MSD NLM requires the following additional Novell NLMs:
AFTER311.NLM (on NetWare 3.x servers)
CLIB.NLM (must be version 3.12 or higher)
N
N
O
O
T
T
E
E
:
:
If you are using NetWare 3.x you must load AFTER311.NLM
before MSD. CLIB.NLM is loaded automatically by MSD.
MSD is loaded using the LOAD command on the System Console on your NetWare
server. You must have access to the System Console screen of the server, either
directly at the server, or through RCONSOLE.
MSD Command Line Options
There are several command line parameters that can be specified when loading
MSD:
Usage: msd <msd_name> [max=] [nodefault] [log]
options
78