HP E-PC C10/S10 User Manual

2.1 Edition

3Com Corporation n 5400 Bayfront Plaza n Santa Clara, California n 95052-8145

©3Com Corporation, 1999. All rights reserved. No patrt of this document may be reproduced in any form otr by any means or used tomake any derivative work (such as translation, transformation, or adaptattion) without permission from 3Com Corporation.

3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change.

3Com Corporation provides this documentation withoutt warranty of any kind, either implied or expressed,t including, but not limited to, the implied warranties of merchantability and fitness for a partticular purpose. 3Com may make improvements or chantges in the product(s) and/or the program(s) described in this document at any time.

UNITED STATES GOVERNMENT LEGENDS:

If you are a United States government agency, then thtis documentation and the software described herein tare provided to you subject to the following restricted rights:

For units of the Department of Defense:

Restricted Rights Legend: Use, reproduction or disclosure by the government tis subject to restrictions set forth in subparagrapth (c) (1) (ii) for Restricted Rights in Technical Data and Computer Software clause tat 48 C.F.R. 52.227-7013. 3Com Corporation, 5400 Bayfront Plaza, tSanta Clara, California 950528145

For civilian agencies:

Restricted Rights Legend: Use, reproduction or disclosure is subject to restrtictions set forth in subparagraph (a) through (d) of tthe Commercial Computer Software - Restricted Rights clause at 48 C.F.R. 52.227-19 andt the limitations set forth in 3Com Corporation's sttandard commercial agreement for the software. Unpublished rights reserved under the copyright laws of the United States.

The software described in this documentation is furntished under a license agreement included with the ptroduct either as a separate document or on the software distribution diskette in a root directory tfile named LICENSE.TXT. If you are unable to locate a copty, please contact Com3 and a copy will be provided to you.

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries.

3Com®, the 3Com logo, Managed PC Boot Agent®, MBA®, Pre-OS® and DynamicAccess® are trademarks of 3Com Corporation or its subsidiatries.

Microsoft, Windows, and Windows NT are registered tradetmarks of Microsoft Corporation. IBM and OS/2 are registerted trademarks foInternational Business Machines Corporation. Novell, NetWare, and UNtIX are registered trademarks of Novell, Inc. Intel is ta registered trademarks of Intel Corporation. Phoenix is a registered trademark of Phoenix Technologies Limited. Compaq is a registered trademark of Compaq Computer Corporation.

Other brands and trademarks may be registered tradetmarks of their respective holders.

April, 1999

CONTENTS
CONTENTS ...................................................	n...........................		iii
About This Guide...................................................	n..................		vii
What's New in this Release ...................................................		n...	viii
Chapter 1: Introduction ............................................................			1
Manageable PCs ...................................................	n....................		1
3Com Managed PC Solutions—Key Capabilities .............................			1
Managed PC Boot Agent (MBA)...................................................			n 2
Features...................................................	n...............................		3
Boot Image Editor ...................................................	n.................		4
Documentation Overview:...................................................		n...	4
Chapter 2: Installing MBA .........................................................			5
PC Requirements...................................................	n...................		5
Quick Start ...................................................	n...........................		5
MBA ROM Installation...................................................	n.............		6
Types of MBA Installation ...................................................		n...	6
ROM Installation ...................................................	n................		6
Boot Image Editor Installation...................................................			n. 9
Chapter 3: Configuring MBA ....................................................		11
Programming Your MBA ROM Using MBAFLASH ...........................			11
MBA Base Code and UNDI Components ......................................			12
Setting the Boot Order on PCs with BBS BIOS .............................			13
Configuring MBA's Options...................................................		n.....	14
Configuration Tables ...................................................	n.........		15
Changing the Options...................................................	n........		24
Using the MBA-Based Configuration .......................................			24
Using the MBACFG Utility ...................................................		n...	25
Changing Configuration Options Using a Configuration File ........			26
Changing Configuration Options from the
MBACFG Command Line ...................................................		n....	28
Updating your MBA ROM ...................................................	n.......		28
Updating to a Newer MBA Version ..........................................			28
Restoring a Previously Backed-up Version ...............................			29
Chapter 4: Using MBA Base Code.............................................		33
Boot Failure ...................................................	n.........................		34
Displaying Verbose Status Information (v or Ctrl+Alt) ..................			34
Displaying MBA Information (Shift+Shift) ...................................			34

Troubleshooting ...................................................	n...................		35
Compatibility Problems with Option ROMs for
Hard Disk or SCSI Controllers................................................			35
Using ROMSCAN for Troubleshooting and Diagnostics ...............			35
Chapter 5: Using Pre-OS .........................................................			37
Introduction ...................................................	n........................		37
Pre-OS Framework ...................................................		n...............	38
PC Pre-OS Bootup Sequence .................................................			39
Creating Pre-OS Boot Images ...................................................			n39
Defining Boot Image Content ................................................			40
Creating TCP/IP or PXE Pre-OS Boot Images ...........................			41
Creating NetWare Pre-OS Boot Images...................................			42
Sample Pre-OS Frameworks ...................................................			n..42
TCP/IP or PXE Pre-OS Sample ...............................................			42
NetWare Pre-OS Sample...................................................		n....	44
Technical Information ...................................................		n...........	45
Chapter 6: Using MBA in TCP/IP Environments.......................			47
Introduction ...................................................	n........................		47
TCP/IP-Specific Features...................................................		n....	47
Network Requirements ...................................................		n......	47
Quick Setup...................................................	n.........................		48
Setting Up the Server ...................................................		n...........	50
BOOTP Service ...................................................	n.................		50
DHCP Service...................................................	n...................		50
TFTP Service ...................................................	n....................		50
Setting Up the PC...................................................	n.................		50
Creating a Boot Diskette...................................................		n....	51
Creating a Boot Image File Using Boot Image Editor.................			51
Boot Screen ...................................................	n.....................		52
Other Tools ...................................................	n.........................		53
FREEMEM: Free RAM Disk Memory .........................................			53
BPPATCH: Supporting Replaceable Parameters ........................			53
Application Notes ...................................................	n.................		54
Using Memory Managers...................................................		n....	54
Troubleshooting ...................................................	n...................		55
Quick Fixes: What to Check First ...........................................			55
MBA Messages ...................................................	n.................		55
File Transfer Error Messages .................................................			55

Chapter 7: Using MBA in a Wired for Management
Environment Using PXE .........................................			57
Introduction ...................................................	n........................		57
Quick Setup...................................................	n.........................		59
Boot Screen ...................................................	n.....................		59
Creating a PXE Boot Image File Using Boot Image Editor ..........			60
Chapter 8: Using MBA in NetWare Environments.....................			61
Introduction ...................................................	n........................		61
Network Requirements ...................................................		n	......61
Quick Setup...................................................	n.........................		62
Boot Screen ...................................................	n.....................		64
Creating a Boot Image File Using Boot Image Editor ....................			64
Boot Using MBA...................................................	n................		67
Supporting Different PCs with One Boot Image............................			67
Creating Additional Boot Image Files..........................................			68
Creating and Editing the BOOTCONF.SYS Boot Index File ..........			68
Avoiding AUTOEXEC.BAT Conflicts in SYS:LOGIN .....................			70
Using Boot Image Editor to Create Additional
Boot Image Files ...................................................	n..............		70
Selecting Different Images at Boot Time.....................................			70
Multiple Servers: How the MSD NLM Can Help.............................			71
Installing MSD...................................................	n..................		72
MSD Command Line Options ...................................................			n..72
NODEFAULT Mode...................................................	n.............		73
MSD Console Display...................................................		n.........	73
MSD PC Messages...................................................	n.............		73
Other Tools ...................................................	n.........................		74
CHKID: Conditional Execution Based on Node Address..............			74
Boot Image Editor: Edit and View Boot Image Files ..................			75
ROMTYPE: Conditional Execution Based on MBA Type ...............			75
Application Notes ...................................................	n.................		76
Using Novell's Client 32 for DOS/Windows with MBA.................			76
Formatting Diskettes Using Windows ......................................			76
Transferring From the Boot Image to SYS:LOGIN.....................			76
Troubleshooting ...................................................	n...................		77
Quick Fixes: What to Check First............................................			77
MBA Messages ...................................................	n.................		77
Batch File Missing Messages and How to Avoid Them................			79

Chapter 9: Using MBA in
Remote Program Load Environments.....................		81
Introduction ...................................................	n........................	81
RPL-Specific Features...................................................	n........	81
Quick Setup...................................................	n.........................	82
Setting Up the NT Server...................................................	n.......	82
Boot Screen ...................................................	n.....................	83
Application Notes ...................................................	n.................	84
Creating and Editing BootBlock and Configurations for NICs ......		84
Troubleshooting ...................................................	n...................	85
Appendix A: Technical Support................................................		87
Online Technical Services ...................................................	n......	87
3Com World Wide Web Site ..................................................		87
3Com FTP Site ...................................................	n.................	87
3Com Bulletin Board Service .................................................		88
3ComFacts Automated Fax Service ........................................		88
Support from Your Network Supplier ......................................		89
Support from 3Com ...................................................	n..........	89
Returning Products for Repair................................................		93
3Com Corporation LIMITED WARRANTY..................................		97
Glossary ............................................................................		101

About This Guide

The information in this guide is presented as follows:

Chapter 1 - An overview of MBA

Chapter 2 - How to install MBA

Chapter 3 - How to configure MBA for your requirements

Chapter 4 - Procedures involved when you bootstrap with MBA

Chapter 5 - An introduction to Pre-OS technology and its applicationsn

Chapter 6 - Using MBA in TCP/IP environments

Chapter 7 - Using MBA in a Wired for Management environment using PXEn

Chapter 8 - Using MBA on a Novell NetWare LAN

Chapter 9 - Using MBA on RPL LANs, including Microsoft Windows NT, Micrnosoft LAN Manager, IBM LAN Server, IBM Warp Server, Digital Pathworks, and Anrtisoft LANtastic

Appendix A - Technical support

Glossary- A list of preboot technology terms

At the beginning of most chapters, you can find a Quick Setunp list of instructions to assist experienced MBA users. Detailed instructions follow for lessn experienced users. Application Notes and Troubleshooting information are presented near nthe end of each chapter.

What's New in this Release

Since the previous release of this guide, MBA has been unpgraded as shown in this section. The guide has been upgraded to explain the features maden available by the following changes:

WfM 2.0 / PXE 2.0 support

The main enhancement to MBA 4.x is the addition of supportn for the new Wired for Management (WfM) Baseline 2.0 specification which was jointnly developed by industry leaders including 3Com. PXE 2.0 adds the following:

Boot image security using Boot Integrity Services (BIS) when provided by the PC BIOS

If your PC's BIOS has implemented BIS as specified in the WfM 2n.0 specification, then the PXE functionality included in MBA will be compatible wnith it and use it if you have a BIS-enabled environment. Refer to the WfM 2.0 specification nfor more information on BIS.

The ability to separate the NIC-specific UNDI from the protocol-generic base code so the UNDI can be used with other base codes available inn the PC

MBA 4.x is comprised of two components—the MBA base code and nthe Universal Network Device Interface (UNDI). The base code handles all thne core functionality of MBA such as protocol handling, network boot failure handlinng, etc. The UNDI handles the interface with the specific NIC.

If your MBA is integrated into your PC's BIOS, then it may hanve been integrated using the new “split ROM” format. This means that the MBA base ncode is available in the BIOS and is separate from the UNDI. This allows another UNDI n(e.g. existing on another NIC) to use the MBA base code from the BIOS and tanke advantage of MBA's functionality. Refer to Table 5: Startup Options for more information.

PC Card support

MBA functionality is now available on PC Card NICs.

PXE is now the default boot method

With the popularity of the Wired for Management (WfM) initinative and the acceptance of the PXE specification, the default boot method has been changend to PXE. You can still change this to another boot method if PXE is not suitable for yonur environment.

New easy-to-use Windows-based Boot Image Editor

Boot Image Editor is a Windows-based utility that enablnes network administrators to create and manipulate TCP/IP, NetWare, and PXE boot images. The boont image files and menu boot files created with the Boot Image Editor allow network clinent PCs to boot from servers instead of local drives or to perform Pre-OS tasks before bootning from the client PC’s hard disk. Boot Image Editor combines and enhances the IMAGEGEnN, IMGGEN, MAPGEN, and Multiple Image File Editor (MULTI_ED) DOS utilities previouslny available from Lanworks Technologies Co.

User selectable boot control

You can specify the mechanism for MBA to use, to allow itselnf to execute when the PC boots. This may be useful on some PCs when MBA cannot automaticanlly detect which mechanism to use. Examples of boot control options are INT 18, INT 19, or BBnS. Refer toTable 5: Startup Options for more information.

Network Service Boot (F12) functionality if not implemente:d in the BIOS

This function prompts the PC user to press the F12 key duringn the boot process to force a network boot. This is useful where the client PC normallyn boots from its local hard disk but must, on occasion, boot from the network server. Refer to Table 5: Startup Options for more information.

The following options are now available if PXE is the se:lected boot method:

Default Boot Method

Enable/Disable Local Booting

Message Timeout

Boot Failure Prompt

Boot Failure

Boot Messages

Refer to Table 2: PXE Configuration Options for more information.

TCP/IP Image Filename

The default TCP/IP image filename is now MBA.IMG instead onf BOOTWARE.IMG. You can now specify an alternative default image filename to be used ninstead of MBA.IMG, if the filename is not provided by the server. Refer to Table 1: TCP/IP Configuration Options for more information.

Chapter 1	1

Thank you for choosing Managed PC Boot Agent (MBA), the wonrld's best-selling network preboot solution for PC networks. MBA is a package of multi-prontocol firmware and software tools that enables the network administrator to remotely nadminister software, operating systems, and applications over the network, eliminating then need to visit the client's desktop in person. MBA is a universal, easy to configure preboot sonlution that is compatible with today's client and network operating systems.

With MBA installed, your client PCs can boot from the netwnork regardless of the contents of their local hard drives or, in some cases, without any locanl drives at all. MBA makes sure your users connect to the network every time.

It's true—You can't compute if you can't boot.

MBA enables new and existing PCs to take advantage of npreboot management technology to perform operating system and application installations or upgnrades as well as desktop disaster recovery. MBA includes the Wired for Management (WnfM) standard PXE protocol, but goes beyond that to include legacy boot protocol support fonr networks such as NetWare and UNIX. MBA is the most universal, pervasive preboot solutionn available on the market today.

Manageable PCs

To take advantage of current and emerging Managed PC applincations, companies need PCs that can cooperate in the management process. These PCs hanve management-ready network interface cards (NICs) with functions implemented in firmware, snoftware, and hardware. While some features are applicable only to newer PCs, many cann be implemented on existing PCs through a software download, flash ROM update or ROM nupgrade.

In selecting management-ready PC NICs, companies can smooth thne transition to a centrally-managed environment by choosing products that supponrt the widest range of industry-standard protocols, existing network administrationn services and tools, and management applications. Wise choices will also help to fnuture-proof investments for what is sure to be a period of emerging technology developments annd rapid change.

3Com Managed PC Solutions—Key Capabilities

3Com, the world's leading supplier of desktop and workgroup nnetworking solutions, offers a full range of Managed PC features for Ethernet, Fast Ethernent, and Token Ring product lines. These products offer consumers a unique advantage: state-of-tnhe-art management intelligence built into industry-leading 3Com NICs, whichn are known for their performance, reliability, and compatibility.

3Com's Managed PC solutions are compatible with leading nmanagement applications, including those from Microsoft, ON Technology Corporation, HP, nTivoli, Platinum Technologies, Network Associates, and Intel. 3Com NICs supponrt new and emerging standards including Preboot eXecution Environment (PXE), Deskntop Management Interface (DMI), Wired for Management (WfM), and Advanced Configuration nand Power Interface (ACPI).

Currently, 3Com's product line supports three key network managenment capabilities: Remote Wake Up, Managed PC Boot Agent for remote preboot capabilitiens, and Desktop Management Interface 2.05 for advanced instrumentation discovery and confinguration.

2

Chapter 1

Managed PC Boot Agent (MBA)

What It Does

The Managed PC Boot Agent (MBA) enables a PC to boot fronm a remote server even if the local operating system (OS) is unable to boot or is nonenxistent. It enables administrators to perform a wide range of preboot management tasks such as viruns scanning, backups, disaster recovery, reconfiguration, and applications and OS innstallation and updates. MBA can also be used to compare desktop profiles to a centralizend software image from a server. MBA can enable a multicast boot, bringing up hundreds of nPCs simultaneously. All of these preboot processes are transparent to the user, since the PC nbehaves as if the boot took place from the local hard drive.

Benefits

MBA improves IS productivity and responsiveness as well as nend-user satisfaction by eliminating most of the need for on-site troubleshootingn and disaster recovery. Instead, the vast majority of problems can be solved remotely and rapidly. nStudies show that nearly half of all help desk calls are related to booting problems, whnich are normally impossible to solve remotely. Because boot failures typically make it impossible fonr users to connect with the network, even the most sophisticated enterprise management ntools at the administrator's disposal are of no use.

MBA guarantees that every PC on the network—even those winth damaged operating systems and new PCs with no OS and unformatted hard disks—will connnect to the network. The ability to boot under management control also protects PCs when tnhey are most vulnerable to boot sector viruses. In addition, MBA improves IS productivity by ennabling administrators to configure or update any number of PCs very efficiently by making nchanges to a single image on a network server.

How MBA Works

PCs can be configured to boot from a server using a combinatnion of configuration files, boot image files, and (needed in most cases) software residing non the server's hard disk. MBA retrieves the required information (for example, an operating snystem, memory managers, network drivers) from these files on the server when the wonrkstation starts. This process has commonly been described in the past as remoteboot.

Traditional remoteboot may not be adequate in establishning a complete work environment due to requirements imposed by today's GUI operating systems nand applications. In this case, MBA can become a compelling administrative tool when nconfigured to perform a Pre-OS boot prior to every local boot. Using MBA software and utinlities including Pre-OS, a network administrator can make use of diagnostics, configuration, or nmaintenance tools prior to completing the local boot process.

Standards Supported

MBA supports Wired for Management (WfM). It also supports alln major boot protocols, including not only the new Preboot eXecution Environment n(PXE) protocol originally defined in the Net PC specification, but also existing protocols snuch as BOOTP, DHCP, RPL, and NCP/IPX. 3Com customers thus have the flexibility to use NT nServer or another specialized server that supports PXE, or to “roll their own” management sonlutions using the booting support built into other platforms such as NetWare, HP UX, Sun nSolaris, and OS/2 WARP.

Chapter 1

3

What You Need to Use MBA

To implement the Managed PC Boot Agent you need:

A NIC with preboot agent firmware (MBA). The agent, which acts as an additional layer of BIOS, can also be installed on an existing NIC as a chnip in the Boot ROM socket or through a system BIOS flash upgrade.

A central boot configuration server

IGURE OW ORKS

Features

MBA includes the following features:

Supports local and network operating systems including DOS, Windows 3.x, Windows 9x, Windows NT, UNIX, Novell NetWare, and others

Fully configurable boot options to enable client PCs to use MBA in various environments, with or without local hard drives

Available as a network interface card (NIC) ROM; also available as a BIOS update for motherboards which contain network interface hardware. Can bne in BIOS even if the PC has a separate NIC

Supports flash ROM configuration and update changes locally or over the network, depending on the NIC ROM or BIOS version

Supports multiple boot protocols and network environments such as traditional TCP/IP, NetWare, and RPL; also includes support for all of today's monst used protocols including DHCP, BOOTP, NCP/IPX (802.2, 802.3, Ethernet II), and the Winred for Management specification Preboot eXecution Environment (PXE) n

For additional features specific to TCP/IP, PXE, NetWare (NCP/IPX), onr RPL environments, see the appropriate chapter in this guide. For new feature rneleases see the 3Com web site at http://www.3com.com/managedpc .

4

Chapter 1

Boot Image Editor

Boot Image Editor is a Windows-based utility that enablnes network administrators to create and manipulate TCP/IP, NetWare, and PXE boot images. The boont image files and menu boot files created with the Boot Image Editor allow network clinent PCs to boot from servers instead of local drives or to perform Pre-OS tasks before bootning from the client PC’s hard disk.

Boot Image Editor combines and enhances the IMAGEGEN, IMGGnEN, MAPGEN, and Multiple Image File Editor (MULTI_ED) DOS-based utilities available frnom Lanworks Technologies Co. Although we encourage you to use Boot Image Editor, the DnOS-based image utilities (IMAGEGEN, IMGGEN, MAPGEN, and MULTI_ED) are still available non the MBA Utility disk and on the EtherCD. The instructions for these utilitiens and for the BWLOADHI and UNRPLFIX utilities have been removed from this User Guide and placned into the file OLDUTILS.TXT on the MBA Utility disk and on the EtherCD.

With Boot Image Editor, you can:

Create boot image files (from standard boot diskettes) that contain standard startup files and reside on a server.

View and modify the contents of boot image files directly, without creating or accessing boot diskettes.

Create a menu boot file and designate a list of boot options from which end-users can choose at boot time.

Create special Pre-OS boot image files that can execute third-party desktop management agents on the client PC before it boots from tnhe local drive.

Configure boot image file options, such as whether they are read-only or writeable or have extended or normal capacity.

Convert boot image files between environments, such as TCP/IP images to NetWare images and vice versa.

Like Novell’s legacy DOSGEN utility, the Boot Image Editor tnakes a snapshot of a boot diskette. Without Boot Image Editor, creating, examining, annd modifying boot image files is a tedious exercise. Although the Boot Image Editor can be innstalled on any computer, it is usually implemented on a server or a network administrationn PC. For installation instructions, see “Boot Image Editor Installation” in Chapter 2 “Installing MBA.”

Documentation Overview:

The main source of information for Boot Image Editor is the nBoot Image Editor online help. It covers the following subjects:

Overviews

Option descriptions

Instructions for creating and defining the contents of boot diskettes, boot image files, and menu boot files

Instructions for maintaining and editing boot image files and menu boot files

In some cases (such as when you define the contents of a nNetWare boot diskette), you will be referred to this document.

Chapter 2	5

This chapter contains a Quick Start section for those who are experienced with MBA installation, an MBA ROM Installation section that provnides additional details, and a Boot Image Editor Installation section.

PC Requirements

MBA operates in all Intel-based PCs (386 or higher). Your PC munst have a vacant memory region available in the BIOS ROM attachment area, usuallny located from C800:0h to E000:0h. The size of the required region varies with your NIC.n We have gone to great lengths to ensure MBA memory requirements are as small as ponssible; ROM paging is used when supported by your NIC, and on PCI NICs, MBA shrinks its snize after initialization to the smallest possible memory footprint.

When installed on a PCI or soft-configurable ISA NIC, MBA auntomatically configures itself to the NIC's settings.

Quick Start

These abbreviated instructions are for those who are expenrienced with general MBA installation.

Procedure

If you are installing an MBA ROM on the NIC start at stenp 1. If MBA is integrated into the PC system BIOS or if the ROM is pre-installed in the NIC, startn at step 4.

1.Install the MBA ROM on the NIC, making sure the ROM is nnot damaged by static discharge. Be absolutely certain the ROM is installed sno that Pin 1 of the ROM socket is aligned with Pin 1 of the ROM.

2.Enable the ROM socket of the NIC at a non-conflicting memonry address:

	Adapter Type				Configuration
	PCI NICs and Plug and Play				Often the PC automatically configures
	ISA NICs				the NIC to enable the ROM to a non-
					conflicting address. However,

sometimes you may need to run a utility to enable the ROM socket on the NIC. Refer to the NIC's user guide for information on how to set up the NIC.

ISA (legacy, non Plug and Play) NICs

Use either NIC configuration software or jumpers/switches to enable the ROM region to the desired memory address and size.

6

Chapter 2

3.If you have a 3C90Xx NIC such as 3C905C-TX, run the MBAFLASH.EXE utinlity (on the MBA Utility Disk in the Update directory or on the EtherCD inn the MBA subdirectory of the Installation directory). This utility programs the correct MBAn software into the ROM for the specific NIC that you are using. Refer to “Programming your MBA ROM using MBAFLASH” in Chapter 3 for more details on this utility.

4.Use either the MBA-based configuration facility or the MBACFnG utility to configure MBA's operating parameters.

5.To continue with PC and server installation, refer to then “Quick Setup” instructions in the chapter of this guide appropriate to your network environment n(TCP/IP, PXE, NetWare, or RPL).

MBA ROM Installation

This section shows you how to install an MBA ROM on yonur NIC.

Types of MBA Installation

MBA is available on a PC in one of the following ways: n

MBA Type Installation Additional Steps

Required

	Integrated into			Not needed		Go to Chapter 3
	the PC BIOS by					“Configuring MBA”
	the PC
	manufacturer *
	Contained in a			Not needed		Go to Chapter 3
	ROM that is pre-					“Configuring MBA”
	installed on the
	PC's NIC

Contained in a ROM that must be installed on the PC's NIC.

	Install the ROM. The			Go to Chapter 3
	following section			“Configuring MBA”
	describes how to
	install this ROM.

* You can determine whether the MBA is integrated into the BIOS by viewing the phrase “BIOS integrated” displayed beside the versilon number when MBA is executed, or by viewing the MBA information screen. Relfer to “Displaying MBA Information” in Chapter 4 “Using MBA Base Code.”

ROM Installation

Installing the MBA ROM is a straightforward task, but youn must take care to ensure that components are not damaged. Be sure you understand the folnlowing instructionsbefore installing MBA.

Chapter 2

7

CAUTION: Risk of equipment damage

Before removing a NIC, attach an earth ground to the PC chasnsis. If an earth ground is unavailable, ensure that the power is snwitched off and plug in the PC's grounded AC power cord.

Wear an anti-static wrist strap when handling ROMs. As nan additional measure, do not touch the ROM's connectors. Leave the ROMn in its conductive foam packaging when not in use.

1.If you are installing MBA on a NIC that is already in younr PC, remove the NIC from the PC. If you are not familiar with inserting and removing cardns in your PC, refer to your NIC user guide for instructions.

2.Locate the boot ROM socket on your NIC. You may need to refenr to the NIC's userguide to locate the correct ROM socket.

3.Depending on your NIC, you may have either a DIP socket (rectangnular socket with two rows of pins), or a PLCC socket (small, square socket with pins non all sides). Follow the applicable procedure for either the DIP Socket Installation or nthe PLCC Socket Installation, then follow the procedure Installing the NInC into the PC.

DIP Socket Installation

The DIP socket should have a notch that can be indicated nby a small half circle, a small triangle, or a small indentation at one end of the sockent. The circuit board may also have a white rectangle around the socket which should have a nnotch indicated at the same end. This notch indicates the Pin 1 end of the socket. See Figure 2n.

IGURE NSERTING THE

8

Chapter 2

1.Look at the MBA ROM while it is still in its protectiven foam. When the label on the top of the ROM is right side up, you should see a small half circle at the left edge of the ROM. This indicates the ROM's Pin 1 notch.

2.Remove the MBA ROM from its protective foam. The pins on thne ROM are very delicate, so be careful not to damage them. Align the notch on thne top of the MBA ROM with the notch in the ROM socket on the NIC.

CAUTION: Risk of equipment damage

If you install the MBA ROM backwards, you will destroy it! Mnake sure the notch in the socket is lined up with the notch in the nMBA ROMbefore doing anything else.

3.Align the pins on the ROM with the pin receptacles in tnhe ROM socket. Press down gently and evenly on the ROM to ensure that it is seated corrnectly in the socket.

PLCC Socket Installation

The PLCC socket has three square corners and one angled cornner. The angled corner of the ROM must be oriented to match the angled corner of the soncket. See the top left corner in Figure 3.

IGURE NSERTING THE

1.Remove the MBA ROM from its anti-static packaging, and alignn the angled corner of the MBA ROM with the angled corner of the ROM socket on the nNIC.

2.Press down gently and evenly on the ROM to ensure thatn it is seated correctly in the socket.

Chapter 2

9

Installing the NIC into the PC

Now that the ROM has been inserted into the NIC, you cnan install the NIC into the PC.

1.Insert the NIC into the PC. Refer to the NIC's user guiden for installation instructions.

2.Some NICs have a switch, jumper or software setting that neneds to be changed to enable the boot ROM socket; this is usually determined by the NnIC's bus architecture:

	Adapter Type				Configuration
	PCI NICs and Plug and Play				Often the PC automatically configures
	ISA NICs				the NIC to enable the ROM to a non-
					conflicting address. However,
					sometimes you may need to run a
					utility to enable the ROM socket on

the NIC. Refer to the NIC's user guide for information on how to set up the NIC.

ISA (legacy, non Plug and Play) NICs

Use either NIC configuration software or jumpers/switches to enable the ROM region to the desired memory address and size.

Boot Image Editor Installation

The Boot Image Editor software can be found on the MBA Utinlity Disk or on the MBA subdirectory on the EtherCD.

To install Boot Image Editor:

1.On the PC on which you want to use the Boot Image Editonr (such as a server, a network administration PC, or any network client) create a directory (fonr example, IMGEDIT).

2.Copy the all the files from the IMGEDIT directory on the MBA nUtility Disk to the new directory.

3.Run the IMGEDIT.EXE application. The program detects that thnis is the first time it has been executed on the PC and takes you through a quick insntallation and configuration procedure, where you can select the appropriate network type andn make file associations.

4.Refer to the Boot Image Editor online help for detailed innstallation information. Access the help from the Boot Image Editor windows or double-click nthe IMGEDIT.HLP file to open it.

5.Create a shortcut to the Boot Image Editor on your desktop nor add the application to the Windows Start menu, if desired.

10

Chapter 2

Chapter 3

11

This chapter shows you how to configure MBA's options to nsuit your operating requirements.

Programming Your MBA ROM Using MBAFLASH

If you are using a 3Com 3C90Xx NIC such as 3C905C-TX and if MBA wans not preinstalled on the NIC, the ROM you installed must be programmed with thne correct MBA software for your specific 3C90Xx NIC. To do this, run the MBAFLASH utility that nis included in the UPDATE directory on the MBA Utility Disk, or in the MBA subdirectory onf the INSTALLATION directory on the EtherCD. MBAFLASH is the utility you use to program ynour boot ROM chip with MBA software. The MBA software is contained within MBAFLASH.EXEn itself.

NOTE: If MBA is integrated into the PC BIOS you cannot update it with

MBAFLASH.

NOTE: If you are using Windows, MBAFLASH operates only in MS-DOS reanl mode, not from a DOS window.

MBAFLASH detects which NIC you are using. If your NIC is one nof the supported NICs, MBAFLASH displays three prompts. Use the following steps to renspond to these prompts:

Step 1 - Read the License Agreement

MBAFLASH asks if you agree with the License Agreement. If you nhave not reviewed the License Agreement we recommend that you do so.

1.To view the License Agreement press R to exit the program annd return to DOS. Next run the BWVIEW utility found in the root directory on the MBA Utnility Disk or on the EtherCD in the MBA subdirectory and select the License Agreement mennu item.

2.If you have reviewed and agree with the License Agreementn, press A to continue the MBAFLASH process.

Step 2 - Back up your ROM software

MBAFLASH displays a prompt asking whether you wish to make a bnackup of the current software in your ROM before it programs the ROM withn the new MBA software.

Answer Yes. MBAFLASH reads the current software from your ROM annd saves it to a

.ROM file.

After MBAFLASH has programmed your ROM with the new MBA softwanre, you can revert to the previous software using this .ROM file witnh MBAFLASH. Refer to “Updating your MBA ROM” later in this chapter.

Step 3 - Program your ROM

MBAFLASH displays a prompt asking whether you wish to continune with the process of programming your ROM with the correct MBA software for your NIC. n

12

Chapter 3

1.Answer Yes. MBAFLASH completes the process.

2.When MBAFLASH is complete run the MBACFG utility to verify thnat MBA options are correct for your requirements. Options are shown in the configunration tables in this chapter.

Command Line Options

Although you can use MBAFLASH interactively, you can also auntomate some of the process using command line options. This feature is helpful if youn wish to use MBAFLASH as part of a batch file. The command line options are:

Usage: mbaflash [.ROM Filename] [/?] [/p] [/b] options:

.ROM Filename - filename of a .ROM file that you wish to nprogram into your ROM chip. Refer to “Updating your MBA ROM” later in this chapter. Required only if you want a different version of MBA than tnhe one contained within MBAFLASH.EXE, e.g., to revert to the previonus version using the .ROM file created by MBAFLASH in step 2 nabove.

/? - show this help

/p - display no prompts

/b - do not create a backup of current ROM contents

MBA Base Code and UNDI Components

MBA 4.x is comprised of two components—the MBA base code and nthe Universal Network Device Interface (UNDI). The MBA base code handles all the conre functionality of MBA such as protocol handling, network boot failure handling, etc. nIt is independent of the type of NIC being used. The UNDI handles the interface with the specinfic NIC. It provides NIC initialization, low-level transmit and receive functionalnity, etc. The MBA base code uses the UNDI to interface with the NIC. Other base code modules counld also use the UNDI to obtain low-level transmit and receive functionality with the spencific NIC.

In MBA 4.x, it is the UNDI that acts as the boot device. Wnhen executed, the MBA UNDI uses either of the following:

The MBA base code that accompanies it when both the UNDI and base code are included together in a ROM on a NIC or in the PC's BIOS n

Another PXE-compliant base code that the MBA UNDI tries to locate and use (which could reside in the PC's BIOS) if MBA is in a ROM on a NnIC and the MBA base code is disabled

Chapter 3

UNDI Execution

UNDI code in ROM with MBA base code in ROM on NIC enabled

UNDI uses base code on NIC

13

UNDI code in ROM with MBA base code in ROM on NIC disabled

UNDI tries to locate and use another PXE-compatible base code (which could reside in BIOS)

UNDI code in ROM with MBA base code in BIOS

UNDI uses MBA base code in BIOS

Setting the Boot Order on PCs with BBS BIOS

If your PC was purchased recently, it may be Plug and Play BBS-BIOSn (BIOS Boot Specification) compatible. A PC that supports Plug and Play cann automatically detect and set up devices such as CD-ROM drives, hard disks, and NICs. Then BBS specification (developed by Compaq, Phoenix, and Intel) specifies how the system BIOS idnentifies boot devices in a PC, allows the user to select the boot order of these denvices, and then sequentially attempts to boot from each device in the specified order.

NOTE: PC manufacturers may call their BBS support by other names such as Multiboot.

PCs that are Plug and Play BBS-BIOS compatible allow you to snpecify the boot order in the PC’s BBS-BIOS Setup menus. Because these BIOSs can detect the nexistence of MBA UNDI, you can specify the position of MBA UNDI in the boot order winth respect to the other boot devices. If you want the PC to always boot from the netwonrk first, be sure to put MBA UNDI at the top of the boot order list. You can also use then MBACFG utility to make MBA UNDI first in the BBS boot order. MBACFG provides a menu command that mnakes MBA UNDI the first boot device.

If the PC's BIOS is not BBS-compliant, MBA UNDI attempts to contronl the boot process (this behavior is configurable with MBA UNDI) and perform a network nor local boot, depending on the configured options.

14

Chapter 3

Configuring MBA's Options

MBA has many operating options that you can configure. For an complete list of all possible options refer to the configuration tables in this chapter.n

Some versions of MBA may not allow you to configure all thne options listed in the tables, or a version of MBA may have some extra options for your specific NICn. Refer to theConfiguration Supplement for a description of any exceptions or additions for your versnion of MBA.

Configuration Supplements are text files that can be found on the Utility Disk or inn the MBA subdirectory in the Installation directory of the EtherCD. Ynou can view them with the BWVIEW utility. If there is no Configuration Supplement for your NIC then there are no exceptions or additions. In this case, use the options exnactly as listed in this guide.

With few exceptions, the current settings for the options anre stored in the NIC’s soft setup storage area (EEPROM) or they may be stored in the PC's CMnOS memory if the MBA base code is integrated into the PC BIOS. One possible reasonn for the unavailability of some options is that the NIC or PC CMOS does not provide enonugh storage area to save all the options. In cases where some options are not available, ans many options as possible are made configurable and the others are set to their defaultn values. In the case where an option is not available, it is not displayed.

Chapter 3

15

Configuration Tables

Tables on the following pages show the configuration onptions available for each boot method. To see the available options, select your boot method annd go to the appropriate table.

	Boot Method				Go To
	TCP/IP				Table 1: TCP/IP Configuration Options
	PXE				Table 2: PXE Configuration Options
	NetWare				Table 3: NetWare Configuration Options
	RPL				Table 4: RPL Configuration Options

In addition, MBA UNDI startup options are shown in Table 5: Startup Options.

ABLE ONFIGURATION PTIONS

Option		Possible		Description		Default
Name		Values
Protocol		DHCP, BOOTP		Choose the specific protocol for TCP/IP boot		DHCP
				method.
Default		Network		Choose whether MBA will perform a network boot		Local
Boot				or a local hard disk boot by default. If Network
		Local		boot is chosen as the default, the Local Boot
				Message is displayed at boot time (if a bootable
				device exists and Local Boot is enabled). If Local
				boot is chosen as the default, the Network Boot
				message is displayed at boot time. Not available
				with BBS-BIOS.
Local Boot		Enabled		Choose between allowing or disallowing a local		Enabled
				boot from a hard disk or diskette. When local
		Disabled		booting is disabled, the PC is forced to boot from
				the network even if a bootable diskette is inserted
				in drive A:, or if the local hard disk contains an
				active partition. Not available with BBS-BIOS.
Config		Enabled		Choose whether to prevent access to the		Enabled
Menu				Configuration Screen that is built into the MBA
		Disabled		ROM. When Disabled, the Configuration Message is
				not displayed. Also, when Disabled, the only
				method to modify the MBA options is by using the
				MBACFG utility.
Config		Enabled		Choose whether to display or hide the message		Enabled
Message				the MBA displays indicating to the user which hot
		Disabled		keys to press to enter the MBA Configuration
				Screen, i.e. “Press Ctrl+Alt+B to configure…”. You
				may want to hide this message so users do not
				know how to change MBA options, possibly making
				MBA function incorrectly in your environment.
				When the message is hidden, the hot keys can still
				be pressed to enter the Configuration Screen. To
				display the message, set this option to Enabled. To
				hide the message, set this option to Disabled.

16											Chapter 3
ABLE			CONTINUED			ONFIGURATION PTIONS
Option			Possible			Description				Default
Name			Values
Message			3			The amount of time (in seconds) that the prompt				3
Timeout						message is displayed and waits for user input. This
			6			includes messages such as the Configuration
						Message, the Local and Network Boot Messages, and
			12			the Boot Failure Prompt.
			Forever			The Forever setting only applies to the Local and
						Network Boot Messages. If Forever is selected, the
						other messages default to 3 seconds. This setting
						takes affect the next time the PC is booted.
Boot Failure			Wait for			If a network boot cannot be completed, choose				Wait for
Prompt			Timeout			whether MBA displays a message and then waits for				Timeout
						the user to press a key before continuing or waits fora
			Wait for			3 seconds before continuing. MBA continues by
			Key			following the behavior specified by the Boot Failure
						option.
Boot Failure			Next Boot			If a network boot cannot be completed, choose				Next Boot
			Device			whether MBA will reboot the PC or allow the PC to				Device
						boot from the next boot device. On a PC with a BBS-
			Reboot			compliant BIOS, the next boot device is the next
						device in the boot order list. On a PC that does nota
						have a BBS-compliant BIOS, the next boot device is
						normally the hard disk.
TFTP			Enabled			Choose whether MBA uses the secure mode feature				Disabled
Secure						of TFTP. In secure mode, only the filename is sent to
Mode			Disabled			the TFTP Service.
Booting			(User			Choose the message text and hot key that is used to				“Press H to
Messages			Defined)			instruct the user how to boot locally when the				boot from
						Default Boot is set to Network, and how to boot from	a			Hard Disk”
						the network when the Default Boot is set to Local.
						Not available with BIOS-integrated MBA.				“Press N
										to boot
										from
										Network”
TCP/IP			(User			Default filename of the boot image file if a filename				MBA.IMG
Image			Defined)			is not provided in either the DHCP or BOOTP
Filename						response from the server.

Chapter 3						17
ABLE			ONFIGURATION PTIONS
Option			Possible		Description		Default
Name			Values
Default			Network		Choose whether MBA will perform a network boot or		Local
Boot					a local hard disk boot by default. If Network boot is a
			Local		chosen as the default, the Local Boot Message is
					displayed at boot time (if a bootable device exists
					and Local Boot is enabled). If Local boot is chosen asa
					the default, the Network Boot message is displayed
					at boot time. Not available with BBS-BIOS.
Local Boot			Enabled		Choose between allowing or disallowing a local boot a		Enabled
					from a hard disk or diskette. When local booting is
			Disabled		disabled, the PC is forced to boot from the network
					even if a bootable diskette is inserted in drive A:, or a
					if the local hard disk contains an active partition. aNot
					available with BBS-BIOS.
Config			Enabled		Choose whether to prevent access to the		Enabled
Menu					Configuration Screen that is built into the MBA ROM.
			Disabled		When Disabled, the Configuration Message is not
					displayed. Also, when disabled, the only method to
					modify the MBA options is by using the MBACFG
					utility.
Config			Enabled		Choose whether to display or hide the message the		Enabled
Message					MBA displays indicating to the user which hot keys to
			Disabled		press to enter the MBA Configuration Screen, i.e.
					“Press Ctrl+Alt+B to configure…”. You may want to
					hide this message so users do not know how to
					change MBA options, possibly making MBA function
					incorrectly in your environment. When the message
					is hidden, the hot keys can still be pressed to entera
					the Configuration Screen. To display the message,
					set this option to Enabled. To hide the message, set a
					this option to Disabled.
Message			3		The amount of time (in seconds) that the prompt		3
Timeout					message is displayed and waits for user input. This
			6		includes messages such as the Configuration
					Message, the Local and Network Boot Messages, and
			12		the Boot Failure Prompt.
			Forever		The Forever setting only applies to the Local and
					Network Boot Messages. If Forever is selected, the
					other messages default to 3 seconds. This setting
					takes affect the next time the PC is booted.
Boot Failure			Wait for		If a network boot cannot be completed, choose		Wait for
Prompt			Timeout		whether MBA displays a message and then waits for		Timeout
					the user to press a key before continuing or waits fora
			Wait for		3 seconds before continuing. MBA continues by
			Key		following the behavior specified by the Boot Failure
					option.

18								Chapter 3
ABLE			CONTINUED		ONFIGURATION PTIONS
Option			Possible		Description		Default
Name			Values
Boot Failure			Next BBS		If a network boot cannot be completed, choose		Next BBS
			Device		whether MBA will reboot the PC or allow the PC to		Device
					boot from the next boot device. On a PC with a
			Reboot		BBS-compliant BIOS, the next boot device is the
					next device in the boot order list. On a PC that doesa
					not have a BBS-compliant BIOS, the next boot
					device is normally the hard disk.
Booting			(User		Choose the message text and hot key that is used		“Press H to
Messages			Defined)		to instruct the user how to boot locally when the		boot from
					Default Boot is set to Network, and how to boot		Hard Disk”
					from the network when the Default Boot is set to
					Local. Not available with BIOS-integrated MBA.		“Press N to
							boot from
							Network”

ABLE			ET ARE	ONFIGURATION PTIONS
Option			Possible				Description				Default
Name			Values
Protocol			802.2,				Choose the specific frame type for NetWare boot				802.3
			802.3,				methods.
			Ethernet II
Default			Network				Choose whether MBA will perform a network boot or				Local
Boot							a local hard disk boot by default. If Network boot is	a
			Local				chosen as the default, the Local Boot Message is
							displayed at boot time (if a bootable device exists
							and Local Boot is enabled). If Local boot is chosen
							as the default, the Network Boot message is
							displayed at boot time. Not available with BBS-
							BIOS.
Local Boot			Enabled				Choose between allowing or disallowing a local boot	a			Enabled
							from a hard disk or diskette. When local booting is
			Disabled				disabled, the PC is forced to boot from the network
							even if a bootable diskette is inserted in drive A:, or	a
							if the local hard disk contains an active partition. a
							Not available with BBS-BIOS.
Config			Enabled				Choose whether to prevent access to the				Enabled
Menu							Configuration Screen that is built into the MBA
			Disabled				ROM. When Disabled, the Configuration Message is
							not displayed. Also, when disabled, the only method
							to modify the MBA options is by using the MBACFG
							utility.