HP E-PC C10/S10 User Manual

2.1 Edition

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

work (such as translation, transformation, or adaptation) 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 without warranty of any kind, either implied or expressed, including, but not limited to, the implied

warranties of merchantability and fitness for a particular purpose. 3Com may make improvements or changes 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 this documentation and the software described herein are 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 is subject to restrictions set forth in subparagraph (c) (1) (ii) for Restricted

Rights in Technical Data and Computer Software clause at 48 C.F.R. 52.227-7013. 3Com Corporation, 5400 Bayfront Plaza, Santa Clara, California 95052-

8145

For civilian agencies:

Restricted Rights Legend: Use, reproduction or disclosure is subject to restrictions set forth in subparagraph (a) through (d) of the Commercial Computer

Software - Restricted Rights clause at 48 C.F.R. 52.227-19 and the limitations set forth in 3Com Corporation's standard commercial agreement for the

software. Unpublished rights reserved under the copyright laws of the United States.

The software described in this documentation is furnished under a license agreement included with the product either as a separate document or on the

software distribution diskette in a root directory file named LICENSE.TXT. If you are unable to locate a copy, please contact 3Com 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 subsidiaries.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. IBM and OS/2 are registered trademarks of International

Business Machines Corporation. Novell, NetWare, and UNIX are registered trademarks of Novell, Inc. Intel is a 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 trademarks of their respective holders.

April, 1999

CCOONNTTEENNTTSS

CONTENTS ..............................................................................iii

About This Guide..................................................................... vii

What's New in this Release ...................................................... viii

CChhaapptteerr 11:: IInnttrroodduuccttiioonn........................................................................................................................11

Manageable PCs ....................................................................... 1

3Com Managed PC Solutions—Key Capabilities ............................. 1

Managed PC Boot Agent (MBA)................................................... 2

Features.................................................................................. 3

Boot Image Editor .................................................................... 4

Documentation Overview:...................................................... 4

CChhaapptteerr 22:: IInnssttaalllliinngg MMBBAA..................................................................................................................55

PC Requirements...................................................................... 5

Quick Start .............................................................................. 5

MBA ROM Installation................................................................ 6

Types of MBA Installation ...................................................... 6

ROM Installation ................................................................... 6

Boot Image Editor Installation.................................................... 9

CChhaapptteerr 33:: CCoonnffiigguurriinngg MMBBAA........................................................................................................1111

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........................................................14

Configuration Tables ............................................................15

Changing the Options...........................................................24

Using the MBA-Based Configuration .......................................24

Using the MBACFG Utility ......................................................25

Changing Configuration Options Using a Configuration File ........26

Changing Configuration Options from the

MBACFG Command Line .......................................................28

Updating your MBA ROM ..........................................................28

Updating to a Newer MBA Version ..........................................28

Restoring a Previously Backed-up Version ...............................29

CChhaapptteerr 44:: UUssiinngg MMBBAA BBaassee CCooddee..........................................................................................3333

Boot Failure ............................................................................34

Displaying Verbose Status Information (v or Ctrl+Alt) ..................34

Displaying MBA Information (Shift+Shift) ...................................34

Troubleshooting ......................................................................35

Compatibility Problems with Option ROMs for

Hard Disk or SCSI Controllers................................................35

Using ROMSCAN for Troubleshooting and Diagnostics ...............35

CChhaapptteerr 55:: UUssiinngg PPrree--OOSS..................................................................................................................3377

Introduction ...........................................................................37

Pre-OS Framework ..................................................................38

PC Pre-OS Bootup Sequence .................................................39

Creating Pre-OS Boot Images ...................................................39

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 .....................................................42

TCP/IP or PXE Pre-OS Sample ...............................................42

NetWare Pre-OS Sample.......................................................44

Technical Information ..............................................................45

CChhaapptteerr 66:: UUssiinngg MMBBAA iinn TTCCPP//IIPP EEnnvviirroonnmmeennttss..............................................4477

Introduction ...........................................................................47

TCP/IP-Specific Features.......................................................47

Network Requirements .........................................................47

Quick Setup............................................................................48

Setting Up the Server ..............................................................50

BOOTP Service ....................................................................50

DHCP Service......................................................................50

TFTP Service .......................................................................50

Setting Up the PC....................................................................50

Creating a Boot Diskette.......................................................51

Creating a Boot Image File Using Boot Image Editor.................51

Boot Screen ........................................................................52

Other Tools ............................................................................53

FREEMEM: Free RAM Disk Memory .........................................53

BPPATCH: Supporting Replaceable Parameters ........................53

Application Notes ....................................................................54

Using Memory Managers.......................................................54

Troubleshooting ......................................................................55

Quick Fixes: What to Check First ...........................................55

MBA Messages ....................................................................55

File Transfer Error Messages .................................................55

CChhaapptteerr 77:: UUssiinngg MMBBAA iinn aa WWiirreedd ffoorr MMaannaaggeemmeenntt

EEnnvviirroonnmmeenntt UUssiinngg PPXXEE..................................................................................5577

Introduction ...........................................................................57

Quick Setup............................................................................59

Boot Screen ........................................................................59

Creating a PXE Boot Image File Using Boot Image Editor ..........60

CChhaapptteerr 88:: UUssiinngg MMBBAA iinn NNeettWWaarree EEnnvviirroonnmmeennttss..........................................6611

Introduction ...........................................................................61

Network Requirements .........................................................61

Quick Setup............................................................................62

Boot Screen ........................................................................64

Creating a Boot Image File Using Boot Image Editor ....................64

Boot Using MBA...................................................................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 .................................................................70

Selecting Different Images at Boot Time.....................................70

Multiple Servers: How the MSD NLM Can Help .............................71

Installing MSD.....................................................................72

MSD Command Line Options

.....................................................72

NODEFAULT Mode................................................................73

MSD Console Display............................................................73

MSD PC Messages................................................................73

Other Tools ............................................................................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 ....................................................................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 ......................................................................77

Quick Fixes: What to Check First............................................77

MBA Messages ....................................................................77

Batch File Missing Messages and How to Avoid Them................79

CChhaapptteerr 99:: UUssiinngg MMBBAA iinn

RReemmoottee PPrrooggrraamm LLooaadd EEnnvviirroonnmmeennttss..........................................8811

Introduction ...........................................................................81

RPL-Specific Features...........................................................81

Quick Setup............................................................................82

Setting Up the NT Server..........................................................82

Boot Screen ........................................................................83

Application Notes ....................................................................84

Creating and Editing BootBlock and Configurations for NICs ......84

Troubleshooting ......................................................................85

AAppppeennddiixx AA:: TTeecchhnniiccaall SSuuppppoorrtt................................................................................................8877

Online Technical Services .........................................................87

3Com World Wide Web Site ..................................................87

3Com FTP Site ....................................................................87

3Com Bulletin Board Service .................................................88

3ComFacts Automated Fax Service ........................................88

Support from Your Network Supplier ......................................89

Support from 3Com .............................................................89

Returning Products for Repair................................................93

33CCoomm CCoorrppoorraattiioonn LLIIMMIITTEEDD WWAARRRRAANNTTYY....................................................................9977

GGlloossssaarryy ........................................................................................................................................................110011

AAbboouutt TThhiiss GGuuiiddee

The information in this guide is presented as follows:

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

Chapter 6

Chapter 7

Chapter 8

Chapter 9

Appendix A

Glossary

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

- An overview of MBA

- How to install MBA

- How to configure MBA for your requirements

- Procedures involved when you bootstrap with MBA

- An introduction to Pre-OS technology and its applications

- Using MBA in TCP/IP environments

- Using MBA in a Wired for Management environment using PXE

- Using MBA on a Novell NetWare LAN

- Using MBA on RPL LANs, including Microsoft Windows NT, Microsoft LAN

Manager, IBM LAN Server, IBM Warp Server, Digital Pathworks, and Artisoft LANtastic

- Technical support

- A list of preboot technology terms

WWhhaatt''ss NNeeww iinn tthhiiss RReelleeaassee

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

WfM 2.0 / PXE 2.0 support

The main enhancement to MBA 4.x is the addition of support for the new Wired for Management (WfM) Baseline 2.0 specification which was jointly 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 2.0 specification, then the PXE functionality included in MBA will be compatible with it and use it if you have a BIS-enabled environment. Refer to the WfM 2.0 specification for 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 in the PC

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

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

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) initiative and the acceptance of the PXE specification, the default boot method has been changed to PXE. You can still change this to another boot method if PXE is not suitable for your environment.

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

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

for more information.

User selectable boot control

You can specify the mechanism for MBA to use, to allow itself to execute when the PC boots. This may be useful on some PCs when MBA cannot automatically detect which mechanism to use. Examples of boot control options are INT 18, INT 19, or BBS. Refer to Table 5: Startup

Options for more information.

Network Service Boot (F12) functionality if not implemented in the BIOS

This function prompts the PC user to press the F12 key during the boot process to force a network boot. This is useful where the client PC normally 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 selected 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 of BOOTWARE.IMG. You can now specify an alternative default image filename to be used instead of MBA.IMG, if the filename is not provided by the server. Refer to Table 1: TCP/IP Configuration Options

for more

information.

CChhaapptteerr 1

1

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

With MBA installed, your client PCs can boot from the network regardless of the contents of their local hard drives or, in some cases, without any local 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 preboot management technology to perform operating system and application installations or upgrades as well as desktop disaster recovery. MBA includes the Wired for Management (WfM) standard PXE protocol, but goes beyond that to include legacy boot protocol support for networks such as NetWare and UNIX. MBA is the most universal, pervasive preboot solution available on the market today.

1

MMaannaaggeeaabbllee PPCCss

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

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

33CCoomm MMaannaaggeedd PPCC SSoolluuttiioonnss——KKeeyy CCaappaabbiilliittiieess

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

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

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

2

CChhaapptteerr 1

1

MMaannaaggeedd PPCC BBoooott AAggeenntt ((MMBBAA))

WWhhaattIIttDDooees

s

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

s

BBeenneeffiitts

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

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

HHoowwMMBBAAWWoorrkks

s

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

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

SSttaannddaarrddssSSuuppppoorrtteed

d

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

CChhaapptteerr 1

1

3

WWhhaattYYoouuNNeeeeddttooUUsseeMMBBA

A

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 chip in the Boot ROM socket or through a system BIOS flash upgrade.

A central boot configuration server

IGURE OW ORKS

FFeeaattuurreess

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 be 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 most used protocols including DHCP, BOOTP, NCP/IPX (802.2, 802.3, Ethernet II), and the Wired for Management specification Preboot eXecution Environment (PXE)

For additional features specific to TCP/IP, PXE, NetWare (NCP/IPX), or RPL environments, see the appropriate chapter in this guide. For new feature releases see the 3Com web site at

http://www.3com.com/managedpc

.

4

CChhaapptteerr 1

1

BBoooott IImmaaggee EEddiittoorr

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

Boot Image Editor combines and enhances the IMAGEGEN, IMGGEN, MAPGEN, and Multiple Image File Editor (MULTI_ED) DOS-based utilities available from Lanworks Technologies Co. Although we encourage you to use Boot Image Editor, the DOS-based image utilities (IMAGEGEN, IMGGEN, MAPGEN, and MULTI_ED) are still available on the MBA Utility disk and on the EtherCD. The instructions for these utilities and for the BWLOADHI and UNRPLFIX utilities have been removed from this User Guide and placed 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 the 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 takes a snapshot of a boot diskette. Without Boot Image Editor, creating, examining, and modifying boot image files is a tedious exercise. Although the Boot Image Editor can be installed on any computer, it is usually implemented on a server or a network administration PC. For installation instructions, see “Boot Image Editor Installation

DDooccuummeennttaattiioonnOOvveerrvviieeww:

The main source of information for Boot Image Editor is the Boot 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 NetWare boot diskette), you will be referred to this document.

:

” in Chapter 2 “Installing MBA.”

CChhaapptteerr 2

2

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

5

PPCC RReeqquuiirreemmeennttss

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

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

QQuuiicckk SSttaarrtt

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

Procedure

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

1. Install the MBA ROM on the NIC, making sure the ROM is not damaged by static

discharge. Be absolutely certain the ROM is installed so 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 memory address:

Adapter Type Configuration

PCI NICs and Plug and Play ISA NICs

ISA (legacy, non Plug and Play) NICs

Often the PC automatically configures the NIC to enable the ROM to a nonconflicting 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.

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

6

CChhaapptteerr 2

3. If you have a 3C90Xx NIC such as 3C905C-TX, run the MBAFLASH.EXE utility (on the

MBA Utility Disk in the Update directory or on the EtherCD in the MBA subdirectory of the Installation directory). This utility programs the correct MBA 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 MBACFG utility to configure MBA's

operating parameters.

5. To continue with PC and server installation, refer to the “Quick Setup” instructions in the

chapter of this guide appropriate to your network environment (TCP/IP

RPL

).

, PXE, NetWare, or

2

MMBBAA RROOMM IInnssttaallllaattiioonn

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

TTyyppeessooffMMBBAAIInnssttaallllaattiioon

n

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

MBA Type

Integrated into the PC BIOS by the PC manufacturer *

Contained in a ROM that is preinstalled on the PC's NIC

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

* You can determine whether the MBA is integrated into the BIOS by viewing the phrase “BIOS integrated” displayed beside the version number when MBA is executed, or by viewing the MBA information screen. Refer to “Displaying MBA

Information” in Chapter 4 “Using MBA Base Code.”

Installation Additional Steps

Required

Not needed Go to Chapter 3

“Configuring MBA”

Not needed Go to Chapter 3

“Configuring MBA”

Install the ROM. The following section describes how to install this ROM.

Go to Chapter 3 “Configuring MBA”

RROOMMIInnssttaallllaattiioon

n

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

CChhaapptteerr 2

2

7

C

AAUUTTIIOON

C

Risk of equipment damage

N

::

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

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

1. If you are installing MBA on a NIC that is already in your PC, remove the NIC from the

PC. If you are not familiar with inserting and removing cards in your PC, refer to your NIC user guide for instructions.

2. Locate the boot ROM socket on your NIC. You may need to refer to the NIC's user guide

to locate the correct ROM socket.

3. Depending on your NIC, you may have either a DIP socket (rectangular socket with two

rows of pins), or a PLCC socket (small, square socket with pins on all sides). Follow the applicable procedure for either the DIP Socket Installation or the PLCC Socket Installation, then follow the procedure Installing the NIC into the PC.

DIP Socket Installation

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

IGURE NSERTING THE

8

CChhaapptteerr 2

1. Look at the MBA ROM while it is still in its protective 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 the ROM are very delicate,

so be careful not to damage them. Align the notch on the top of the MBA ROM with the notch in the ROM socket on the NIC.

2

AAUUTTIIOON

N

Risk of equipment damage

::

C

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

3. Align the pins on the ROM with the pin receptacles in the ROM socket. Press down gently

and evenly on the ROM to ensure that it is seated correctly in the socket.

PLCC Socket Installation

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

IGURE NSERTING THE

1. Remove the MBA ROM from its anti-static packaging, and align the angled corner of the

MBA ROM with the angled corner of the ROM socket on the NIC.

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

socket.

CChhaapptteerr 2

2

Installing the NIC into the PC

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

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

2. Some NICs have a switch, jumper or software setting that needs to be changed to enable

the boot ROM socket; this is usually determined by the NIC's bus architecture:

Adapter Type Configuration

9

PCI NICs and Plug and Play ISA NICs

ISA (legacy, non Plug and Play) NICs

Often the PC automatically configures the NIC to enable the ROM to a nonconflicting 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.

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

BBoooott IImmaaggee EEddiittoorr IInnssttaallllaattiioonn

The Boot Image Editor software can be found on the MBA Utility 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 Editor (such as a server, a network

administration PC, or any network client) create a directory (for example, IMGEDIT).

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

directory.

3. Run the IMGEDIT.EXE application. The program detects that this is the first time it has

been executed on the PC and takes you through a quick installation and configuration procedure, where you can select the appropriate network type and make file associations.

4. Refer to the Boot Image Editor online help for detailed installation information. Access

the help from the Boot Image Editor windows or double-click the IMGEDIT.HLP file to open it.

5. Create a shortcut to the Boot Image Editor on your desktop or add the application to the

Windows Start menu, if desired.

110

0

CChhaapptteerr 2

2

CChhaapptteerr 3

3

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

111

1

PPrrooggrraammmmiinngg YYoouurr MMBBAA RROOMM UUssiinngg MMBBAAFFLLAASSHH

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

N

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

E

OOTTE

N

:

MBAFLASH.

E

N

If you are using Windows, MBAFLASH operates only in MS-DOS real mode,

OOTTE

N

::

not from a DOS window.

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

Step 1 - Read the License Agreement

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

1. To view the License Agreement press R to exit the program and return to DOS. Next run

the BWVIEW utility found in the root directory on the MBA Utility Disk or on the EtherCD in the MBA subdirectory and select the License Agreement menu item.

2. If you have reviewed and agree with the License Agreement, 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 backup of the current software in your ROM before it programs the ROM with the new MBA software.

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

After MBAFLASH has programmed your ROM with the new MBA software, you can revert to the previous software using this .ROM file with 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 continue with the process of programming your ROM with the correct MBA software for your NIC.

2

112

CChhaapptteerr 3

1. Answer Yes. MBAFLASH completes the process.

2. When MBAFLASH is complete run the MBACFG utility to verify that MBA options are

correct for your requirements. Options are shown in the configuration tables in this chapter.

Command Line Options

Although you can use MBAFLASH interactively, you can also automate some of the process using command line options. This feature is helpful if you 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 program 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 the one contained within MBAFLASH.EXE, e.g., to revert to the previous version using the .ROM file created by MBAFLASH in step 2 above.

/? - show this help /p - display no prompts /b - do not create a backup of current ROM contents

3

MMBBAA BBaassee CCooddee aanndd UUNNDDII CCoommppoonneennttss

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

In MBA 4.x, it is the UNDI that acts as the boot device. When 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

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 NIC and the MBA base code is disabled

CChhaapptteerr 3

3

UNDI Execution

113

3

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

UNDI uses base code on NIC UNDI tries to locate and use

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

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

SSeettttiinngg tthhee BBoooott OOrrddeerr oonn PPCCss wwiitthh BBBBSS BBIIOOSS

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

E

N

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

OOTTE

N

:

Multiboot.

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

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

114

4

CChhaapptteerr 3

3

CCoonnffiigguurriinngg MMBBAA''ss OOppttiioonnss

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

Some versions of MBA may not allow you to configure all the options listed in the tables, or a version of MBA may have some extra options for your specific NIC. Refer to the Configuration

Supplement for a description of any exceptions or additions for your version of MBA. Configuration Supplements are text files that can be found on the Utility Disk or in the MBA

subdirectory in the Installation directory of the EtherCD. You 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 exactly as listed in this guide.

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

CChhaapptteerr 3

3

115

5

CCoonnffiigguurraattiioonnTTaabbllees

s

Tables on the following pages show the configuration options available for each boot method. To see the available options, select your boot method and 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 Name

Protocol DHCP, BOOTP Choose the specific protocol for TCP/IP boot

Default Boot

Local Boot Enabled

Config Menu

Config Message

Possible Values

Network

Local

Disabled

Enabled

Disabled

Enabled

Disabled

Description Default

method.

Choose whether MBA will perform a network boot or a local hard disk boot by default. If Network 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.

Choose between allowing or disallowing a local boot from a hard disk or diskette. When local 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.

Choose whether to prevent access to the Configuration Screen that is built into the MBA 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.

Choose whether to display or hide the message the MBA displays indicating to the user which hot 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.

DHCP

Local

Enabled

116

6

ABLE CONTINUED ONFIGURATION PTIONS

CChhaapptteerr 3

3

Option Name

Message Timeout

Boot Failure Prompt

Boot Failure Next Boot

TFTP Secure Mode

Booting Messages

TCP/IP Image Filename

Possible Values

3

6

12

Forever

Wait for Timeout

Wait for Key

Device

Reboot

Enabled

Disabled

(User Defined)

Description Default

The amount of time (in seconds) that the prompt message is displayed and waits for user input. This includes messages such as the Configuration Message, the Local and Network Boot Messages, and the Boot Failure Prompt.

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.

If a network boot cannot be completed, choose whether MBA displays a message and then waits for the user to press a key before continuing or waits for 3 seconds before continuing. MBA continues by following the behavior specified by the Boot Failure option.

If a network boot cannot be completed, choose whether MBA will reboot the PC or allow the PC to boot from the next boot device. On a PC with a BBScompliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBS-compliant BIOS, the next boot device is normally the hard disk.

Choose whether MBA uses the secure mode feature of TFTP. In secure mode, only the filename is sent to the TFTP Service.

Choose the message text and hot key that is used to instruct the user how to boot locally when the Default Boot is set to Network, and how to boot from the network when the Default Boot is set to Local. Not available with BIOS-integrated MBA.

Default filename of the boot image file if a filename is not provided in either the DHCP or BOOTP response from the server.

3

Wait for Timeout

Next Boot Device

Disabled

“Press H to boot from Hard Disk”

“Press N to boot from Network”

MBA.IMG

CChhaapptteerr 3

3

ABLE ONFIGURATION PTIONS

117

7

Option Name

Default Boot

Local Boot Enabled

Config Menu

Config Message

Message Timeout

Boot Failure Prompt

Possible Values

Network

Local

Disabled

Enabled

Disabled

Enabled

Disabled

3

6

12

Forever

Wait for Timeout

Wait for Key

Description Default

Choose whether MBA will perform a network boot or a local hard disk boot by default. If Network 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.

Choose between allowing or disallowing a local boot from a hard disk or diskette. When local 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.

Choose whether to prevent access to the Configuration Screen that is built into the MBA 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.

Choose whether to display or hide the message the MBA displays indicating to the user which hot 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.

The amount of time (in seconds) that the prompt message is displayed and waits for user input. This includes messages such as the Configuration Message, the Local and Network Boot Messages, and the Boot Failure Prompt.

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.

If a network boot cannot be completed, choose whether MBA displays a message and then waits for the user to press a key before continuing or waits for 3 seconds before continuing. MBA continues by following the behavior specified by the Boot Failure option.

Local

Enabled

3

Wait for Timeout

118

8

ABLE CONTINUED ONFIGURATION PTIONS

CChhaapptteerr 3

3

Option Name

Boot Failure Next BBS

Booting Messages

Possible Values

Device

Reboot

(User Defined)

ABLE ET ARE ONFIGURATION PTIONS

Option Name

Protocol 802.2,

Default Boot

Local Boot Enabled

Config Menu

Possible Values

802.3, Ethernet II

Network

Local

Disabled

Enabled

Disabled

Description Default

If a network boot cannot be completed, choose whether MBA will reboot the PC or allow the PC to boot from the next boot device. On a PC with a BBS-compliant BIOS, the next boot device is the next device in the boot order list. On a PC that does not have a BBS-compliant BIOS, the next boot device is normally the hard disk.

Choose the message text and hot key that is used to instruct the user how to boot locally when the Default Boot is set to Network, and how to boot from the network when the Default Boot is set to Local. Not available with BIOS-integrated MBA.

Next BBS Device

“Press H to boot from Hard Disk”

“Press N to boot from Network”

Description Default

Choose the specific frame type for NetWare boot methods.

Choose whether MBA will perform a network boot or a local hard disk boot by default. If Network 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 BBSBIOS.

Choose between allowing or disallowing a local boot from a hard disk or diskette. When local 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.

Choose whether to prevent access to the Configuration Screen that is built into the MBA 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.

802.3

Local

Enabled