Networking Connectivity
Intel® Boot Agent
NetWare* Remote Boot Installation

This information is provided solely as a convenience to Intel customers. If you have questions about NetWare* or the remoteboot process, consult your NetWare documentation or contact Novell for assistance.

This page covers the following topics:

Setting up a remote boot or diskless workstation requires 2 steps:

  1. Configuring the file server (with either a single boot image or multiple boot image).
    spacer graphic
  2. Configuring the workstation.

Configuring the File Server

Note: Your file server should have the latest patches from Novell, especially the RBOOT.RPL and RPL.NLM files

The Intel® Boot Agent RPL is ODI/802.2 based, and requires the IPX protocol and RPL to be loaded and bound to the 802.2 frame type on the server. For example,

LOAD E100B SLOT=xxx FRAME=ETHERNET_802.2 NAME=LAN1 BIND IPX TO LAN1 NET=xx LOAD RPL BIND RPL TO LAN1
Sample AUTOEXEC.NCF file with multiple frame types:
File Server Name RPLSERVER IPX Internal Net 0378047 load e100b slot=101 frame=ethernet_802.2 name=rpl_lan
bind ipx to rpl_lan net=200 load rpl bind rpl to rpl_lan load e100b slot=101 frame=ethernet_802.3 name=lan1
bind ipx to lan1 net=100
Setting Up A Single Boot Image
A single boot image should be used if all your remote boot workstations will use the same boot up files and DOS version. Otherwise, refer to "Setting up multiple boot images" under the Hints and Tips section at the end of this document for details on multiple boot images.

Create a DOS bootable disk that contains these files:

COMMAND.COM AUTOEXEC.BAT
CONFIG.SYS
NET.CFG
LSL.COM
E100BODI.COM
IPXODI.COM
VLM.EXE (plus all associated .VLM files)
Sample AUTOEXEC.BAT (for ODI workstations)
prompt $p$g
set nwlanguage=english
lsl
e100bodi
ipxodi
vlm
Sample CONFIG.SYS
files=50
buffers=25
lastdrive=Z
Sample NET.CFG
preferred server=<server_name> NetWare DOS Requester
first network drive = F link driver E100BODI
frame ethernet_802.2
frame ethernet_II

LSL.COM, IPXODI.COM, NETX.EXE and VLM.EXE (and related files) are Novell files. E100BODI.COM is the DOS ODI driver for the Intel® PRO adapter family. Include any other drivers you plan to load on this boot disk. Insure that you can boot from this diskette and attach to the server.

Log onto the network with supervisory rights and verify that these mappings exist:

SYS:LOGIN SYS:SYSTEM
If they don't, you will need to create them:
MAP F:=SYS:LOGIN MAP G:=SYS:SYSTEM
Put the DOS bootable disk in drive A. Change to the LOGIN directory and type:
G:DOSGEN
Note: For DOSGEN to work correctly, you should run DOSGEN from the LOGIN directory not the SYSTEM directory. DOSGEN creates a file called NET$DOS.SYS in the SYS:LOGIN directory.

NET$DOS.SYS contains all the files from your boot disk.

Change the attributes of NET$DOS.SYS to: Shareable, Read/Write.
FLAG NET$DOS.SYS SRW (NetWare 3.11 and 3.12)
FLAG NET$DOS.SYS SHRW (NetWare 4.x)

Setting up the Workstation

ONLY AFTER SETTING UP A BOOT IMAGE ON THE SERVER
Configure the Intel Boot Agent so it is set for RPL remote boot. This can be done the first time you plug the adapter in and turn the power on. Press CTRL-S to enter the setup screen when prompted during boot up.

Set the Network Boot Protocol to RPL.

Change the boot order as needed for your implementation. If your computer supports BBS, your only option will be "Use BIOS Setup Boot Order". In that case, you must configure the boot order in your computers BIOS settings instead.

Press F4 to save your configuration changes when finished.

Hints and Tips

Remote Boot Process
When you power on a remote-boot workstation, the ROM finds the server by looking for the nearest RPL server with 802.2 frame type. Once connected to the server, it looks for a BOOTCONF.SYS file. If it finds this file AND it finds a line with its Ethernet address it executes the XXXX.sys file. If it does not find its Ethernet address (or a BOOTCONF.SYS file), it looks for NET$DOS.SYS and executes that file.

Non-802.2 Servers
The Boot Agent is configured for a FRAME type of 802.2. If you are using a different FRAME type (i.e. Ethernet Type II), the server must be configured to include both 802.2 and the other FRAME type. You will also need to include a NET.CFG file in the boot image. This NET.CFG files must also include both FRAME types.

Computer won't boot from network
If the remote boot workstation does not have a floppy drive, try another computer with the SAME configuration. Make sure the computer will boot from the EXACT floppy disk used for DOSGEN (BEFORE configuring the adapter so it is set for ODI remote boot).

If you are using a memory manager, make sure you EXCLUDE the memory for the flash ROM address.

If an RPL counter appears while trying to boot and continues to increment, make sure the server has the correct frame types loaded, that RPL is bound to the 802.2 frame type, and ensure the cables are working properly.

VLMs for remote boot
Below is a list of VLMs you should use for remote booting.

VLM.EXE
AUTO.VLM
CONN.VLM
FIO.VLM
GENERAL.VLM
IPXNCP.VLM
NMR.VLM
NWP.VLM
PNW.VLM
PRINT.VLM
REDIR.VLM
TRAN.VLM
Remote booting to an SFT III server
If you are remote booting to a SFT III server, the bind rpl line requires the GetNearestServer parameter in the IOSTART.NCF file.

For Example:

LOAD E100B.LAN SLOT=101 FRAME=ETHERNET_802.2 NAME=LAN1
BIND IPX LAN1 NET=4444
LOAD RPL
BIND RPL TO LAN1 GNS

Setting up multiple boot images
Create a DOS 5.0 or 6.xx bootable disk that contains the files as listed in step 2 under the single boot image section.

The AUTOEXEC.BAT file should contain only one line: xxxx.BAT
Where xxxx is a name you assign to the remote boot workstation. Each remote boot workstation will have its own xxxx.BAT file. The xxxx.BAT file should contain the information as listed in the appropriate AUTOEXEC.BAT file under Sample configuration files above.

Copy the xxxx.bat file to the LOGIN subdirectory on the server. You can execute other commands by including them in the xxxx.bat file.

Log onto the network as supervisor and verify that these mappings exist:

SYS:LOGIN
SYS:SYSTEM
If they don't, you will need to create them:
MAP F:=SYS:LOGIN
MAP G:=SYS:SYSTEM
Put the DOS bootable disk in drive A. Change to the LOGIN directory and type:
G:DOSGEN a: XXXX.sys
There MUST be a space between a: and XXXX.sys.

Change the attributes of the new file to Shareable, Read/Write:

FLAG XXXX.SYS SRW (NetWare 3.11 and 3.12)
FLAG XXXX.SYS SHRW (NetWare 4.x)
Change to the LOGIN directory and create an ASCII file called BOOTCONF.SYS Each line in this file defines a unique remote-boot workstation. The format for this file is: 0xYYY,AAAAAAAAAAAA=XXXX.sys
Where 0xYYY is the network address of the remote-boot workstation (It should start with 0x). This is the NET=# that is specified on the BIND IPX line of the 802.2 segment.

AAAAAAAAAAAA represents the 12 digit Ethernet address of the adapter. This address is printed on the board or can be displayed by running DIAG100 (DOS) or PROSet (Windows*).

XXXX.sys is the name of the boot image for this workstation. You entered this name when you ran DOSGEN.

For additional information on setting up multiple boot images refer to your Novell documentation.

Related Links
Download Software for RPL Boot

This applies to:

Intel® Boot Agent

Solution ID: CS-008192
Last Modified: 09-Jan-2012
Date Created: 11-Jan-2004
Back to Top