DATA SHEET

3Com Boot Services Enabling Centralized Desktop Management to Lower Your Total Cost of Ownership

Key Benefits

Introducing 3Com Boot Services

Highlights of 3Com Boot Services

From PC workstations to file servers to networked appliances, 3Com Boot Services has your network booting needs covered. 3Com Boot Services is a comprehensive remote booting and pre-booting solution for virtually any operating system, including Windows, DOS, UNIX, LINUX, and NetWare environments. Boot Services includes DOS, PXE, BOOTP, and TFTP based components, as well as tools to administer boot image and client boot parameter files.

• Compatible with WfM 2.0 PXE

Pre-OS network booting In conjunction with a boot ROM, 3Com Boot Services allows a pre-OS network boot connection to be established. This pre-OS connection enables the loading and executing of centrally administered desktop management agents before the local OS is loaded from the hard drive.

Lowered total cost of ownership. The overall effect of saving administrators time, keeping end users productive, and protecting your data is lower IT ownership costs.

Increased enterprise productivity Facilitates central control and repair of network clients, reducing administrator “travel time ” to individual PCs and ensuring system availability for end users.

• Fully compatible with 3Com Managed PC Boot Agent (MBA), PXE boot ROMs, & Lanworks BootWare® ROMs • PXE, BOOTP, and TFTP applications can run as executables on Windows 9x, Windows NT, & Windows 2000 • PXE, BOOTP, and TFTP services run as native Windows NT and Windows 2000 system services • Simple, user friendly application interface includes detailed on-line help

Guaranteed compatibility 3Com Boot Services is compatible with today’s most widely used operating systems and client management utilities — for a universal network solution. Support for industry standards Compliance with industry standards — including Wired for Management (WfM) 2.0, Preboot Execution Environment (PXE), DHCP, BOOTP, TFTP, and NCP/IPX — enables you to realize the benefits of remote booting and pre-OS booting.

3COM BOOT SERVICES

The Advantages of Pre-OS Booting

The Advantages of Pre-OS Booting

Booting clients from the network is not a new concept, but with 3Com Boot Services, administrators can now deploy a comprehensive array of management tasks or repairs from a central management station. Remote booting and pre-OS booting services can be used for installing and configuring new PCs, performing OS and software upgrades, remotely diagnosing and repairing system failures, reconfiguring multiple systems, backing up and restoring hard drives, and scanning for viruses. What’s more, IT managers have centralized control over whether remote PCs receive any or all of their boot-up instructions from the network. After network pre-boot completes, the PC’s local hard drive commences with the normal boot operation. PXE Service

Components of 3Com Boot Services

The PXE protocol is an extension of DHCP, designed, among other things, to standardize network booting operations. It is used primarily in WfM environments where desktops have PXE-compatible boot ROMs. Using the PXE boot service, networked PCs can be configured to establish a pre-OS connection with a network server. The PXE boot service requires a DHCP server that issues a dynamic IP address to the remote PCs and a PXE server to name the network bootstrap program (NBP) file — the boot image file that contains the executable desktop management agents. With 3Com MBA installed in your desktops, you also have pre-boot management capabilities for DHCP, BOOTP, and NetWare environments. TFTP Service

TFTP is a simple, streamlined form of FTP without its security features such as directory listings, password protection, and user authentication. TFTP is used to transfer files between a client and server on a TCP/IP network—such as boot image files or

NBPs. TFTP facilitates remote and pre-OS booting clients with boot ROMs. TFTP can also be used to download updates to X-terminals, switches, routers, and print servers. BOOTP Service

BOOTP can be used in place of DHCP services to respond to IP address requests from clients that have BOOTPcompatible boot ROMs. The BOOTP service searches the client boot parameter database (BOOTPTAB) for the proper static IP address, boot image filename, and configuration information using the client’s MAC address, and then responds to the client. Boot Image Editor

The Boot Image Editor is a Windowsbased utility that lets you easily create, view, and modify the contents of PXE, DHCP, BOOTP and NetWare boot image files. The Boot Image Editor consolidates the system files and net-work drivers needed to boot a PC into one boot image file. For example, in DOS these may include COMMAND.COM, MSDOS.SYS, IO.SYS, DRVSPACE.BIN, AUTOEXEC.BAT, CONFIG.SYS, and network drivers. Boot image files can also include memory managers, device drivers, configuration-related files, third-party management agents, virus checkers, and other programs that can be loaded onto the client PC to automate management tasks. You can also use the Boot Image Editor to administer menu boot files. These files allow a menu to be displayed on the desktop at boot time so the end user can select a desired action. Menu boot files include a default boot option that automatically loads after a specified interval of time.

3COM BOOT SERVICES

Components of 3Com Boot Services cont...

BOOTPTAB Editor

DOS Utilities

PXE and BOOTP servers read their configuration information from a client boot parameter database file (BOOTPTAB). The BOOTPTAB file contains the MAC address, static IP address (if DHCP service is not being used), boot image filename, and configuration information for each PXE- or BOOTP-enabled client. Each BOOTPTAB file supports an unlimited number of client entries and multiple BOOTPTAB templates. Although BOOTPTAB information is stored as ASCII text, administering it using simple text editors may result in errors that are difficult to track. 3Com’s BOOTPTAB Editor is a simpleto-use, Windows-based configuration utility that helps locate and fix syntax errors.

Boot Services includes three useful DOS utilities—BPPATCH, FREEMEM, and PBOOT. • BPPATCH replaces parameters from the DHCP or BOOTP reply packets into text files, such as batch files, INI files, and system files. This gives multiple client PCs the ability to share one common boot image file that still includes configurations specifically tailored to individual PCs. • FREEMEM releases the memory used by the boot image file after the PC has booted. • PBOOT is used in pre-OS environments to terminate the preboot connection between the client PC and the server, enabling the PC to continue its normal booting process from its local hard drive without requiring system reboot.

Sit tight With 3Com’s Boot Services you have centralized pre-boot control of your PCs

Components of 3Com Boot Services Server

Administration

Client

PXE Service

Boot Image Editor

Menu Boot Files and Image Files

TFTP Service

BOOTPTAB Editor

Pre-OS Executables

BOOTP Service

DOS License* Other Applications*

*DOS License and other applications are not included

3 C O M B O O T S E R V I C E S F E AT U R E S A N D B E N E F I T S

Feature

Benefit

General Wired for Management-compliant server, administrator, and client tools

Unlocks the value from WfM-enabled clients

BOOTP, TFTP, legacy NetWare support

Provides network boot/pre-OS boot solutions for all major platforms

Open management environment, supports many popular third-party client management tools

Vendor-agnostic, lets network administrators roll their own purpose-built solutions

BOOTP, TFTP and PXE applications run as executables

Can monitor, add and configure new clients on the fly

BOOTP, TFTP and PXE services run as native Window NT and Windows 2000 Services

Remains active even when the user is not logged on to the server

Server log report summary

Summarizes to log file, on-screen log, or to Windows NT Event Viewer, allowing administrator to monitor server and client activity

PXE Boot Services & Applications NBP requests made from PXE Server

- No need to reconfigure the DHCP server - Remote boot and preboot activity can be enabled without accessing the DHCP server - A new network boot server can be added to an existing network without changing the original setup - Unique NBPs can be specified for multiple clients via the BOOTPTAB database file

TFTP Services & Applications Fully supports TFTP secure mode

Can prohibit end users from traversing directories

TFTP server supports RFC 1350,1783, and 2348

Follows industry-standard specifications, assures interactivity with third-party TFTP clients

Supports TFTP transfer size, timeout, and blocksize option extension

When these options are utilized by client devices, TFTP transfer can be more efficent

BOOTP Services & Applications Functions as a stand-alone static IP address issuing services

Provides boot image file names or configuration information

Supports both unicast and broadcast packet replies

Extends support to legacy boot ROMs

Automatically checks for updates to BOOTPTAB database file

Ensures that the latest BOOTPTAB file is cached to optimize server response time

Complies with RFC 951 and 1084

Follows industry-standard specifications, ensures interactivity with third-party clients

BOOTPTAB Editor Windows-based user interface

Allows for easy-to-use management

Syntax Checker

Allows users to easily locate and fix syntax and other errors

Search, sort, display BOOTPTAB files on any field

Enables quick access to information for large client (host) databases

Boot Image Editor Boot image files created from standard boot diskette

Enables easy migration from existing boot floppies

Special pre-OS boot image files

Enables execution of third-party desktop management agents on the client PC before it boots from the local drive, allowing management of the client before potential problems arise or in off-hours

Boot image file conversions

Easily converts boot image files from one networking environment to another, e.g. TCP/IP images to Netware images

Boot image file configuration

Allows administrator variations in configuring options for the boot images file, e.g. read-only or writeable, extended or normal capacity, etc. depending on end user requirements.

Boot file menu creation

Can present multiple boot options from which end users can choose at boot time

DOS Utilities BPPATCH

Converts parameters from BOOTP or DHCP reply packets to text files so that multiple client PCs can use one common boot image file, thus lowering time spent on managing multiple boot image files

FREEMEM

Releases the memory used by the boot image file after the client PC has booted

PBOOT

Enables the PC to continue the regular booting process from its local hard drive, without requiring a hard or soft reset

3COM BOOT SERVICES

Boot Services in Motion

Putting Boot Services in Motion

A basic pre-OS connection and pre-boot procedure are accomplished as follows: • The networked client, PC, laptop, or other device is powered up, either locally by an end user or through the network using a remote wake up (RWU) signal. • The boot ROM in a client PC connects to the network server and discovers its IP address. This IP address can be issued by a service such as DHCP, or BOOTP. • The boot ROM also obtains the filename of the boot image file to be downloaded. It obtains the filename from a service such as a DHCP, BOOTP, or PXE. The boot ROM then requests the boot image file from a TFTP service.

Example of centralized client OS deployment and disaster recovery using 3Com Boot Services and a third-party drive imaging tool

• Using TFTP, the network server transfers the appropriate boot image file to the client. No intervention is required, but a menu can be displayed that allows end users to choose booting options and server downloads. • When the entire boot image file is loaded into the client’s memory, the boot ROM transfers control to the boot image file, which then executes. • Desktop maintenance applications specified in the boot image file are executed in the client prior to loading the OS. These can include disk drive imaging tools, virus scanners, and BIOS updates. When pre-OS actions have completed, the boot image operation automatically terminates. • At this point, the client either shuts down, reboots, or proceeds to load the OS from its hard drive and the end user logs into the network as usual.

step 2

• Using BOOTPTAB Editor, administrator defines client boot parameters

Server step 1

Administrator

• Using Boot Image Editor,administrator creates pre-OS boot image file containing drive image tool and PBOOT

• Administrator loads either PXE Server or BOOTP Server along with TFTP Server • Server contains boot image files, client drive images from step 1

• Using 3rd-party drive imaging tool,administrator creates snapshot of client desktop

step 3 Client

• User or administrator uses boot firmware to boot menu,chooses Disaster Recovery image • Drive imaging tool (re-) initializes client desktop,then PC runs PBOOT to directly boot from newly (re-) deployed client OS on the hard drive

3COM BOOT SERVICES

System Requirements

Server Software

BOOTP Server

The network server must be running:

• Supports RFC 951 and 1084

• TCP/IP

• Reads structured ASCII client boot parameter database file (created by included BOOTPTAB Editor)

• Microsoft Windows 95 OSR 2 • Windows 98 • Windows NT Version 3.51 (Service Pack 5 or higher)

• Selectable unicast/broadcast replies • Configurable event logging

• Windows NT Version 4.0 (Service Pack 3 or higher)

Administrator Software

• Windows 2000

• Windows-based

• Windows Socket version 2.0 or higher (for TFTP)

• Creates/edits/views PXE, DHCP, BOOTP, and NetWare boot image files and associated menu files

Client PC Firmware

• WfM-compliant boot ROMs • 3Com managed PC boot agent

Boot Image Editor

• Handles boot images of up to 16 MB in size Menu files:

• Lanworks BootWare ROMs

• Support 16 entries per menu; sub-menus supported

• PXE boot ROMs.

• Configurable default image, timeout

Specifications

BOOTPTAB Editor

Server Software

• Windows-based

All servers can run as applications under Windows 2000, Windows NT, or Windows 9x; may also run as native services under Windows 2000 and Windows NT.

• Supports unlimited number of client entries, multiple BOOTPTAB entries • Advanced error checking

PXE Server

Client PC Software

• Wired for Management-compliant

Client PC tools run in standard DOS environments;client platform must contain active boot firmware or equivalent (see list below).

• Reads structured ASCII client boot parameter database file (created by included BOOTPTAB Editor)

• 3Com managed PC boot agent (MBA)

• Selectable DHCP proxy feature

• 3Com disk-based Managed PC Boot Agent

• Configurable event logging

• 3Com TriROM • Lanworks BootWare boot ROM

TFTP Server

• Supports RFCs 1350, 1783, and 2348

• WfM 1.0-or 2.0-compliant PXE boot ROM

• Supports transfer size, timeout interval, and blocksize option extensions • Configurable event logging • Programmable retries (3-10) and timeouts (1-255s) • Selectable port number (1-5000)

Ordering Information

More Product Information

Ordering Information Description

3Com Part Number

3Com Boot Services software on CD with 10 client licenses.

3CDA120-10

3Com Boot Services 50 client license pack.

3CDA120-50PK

Web: www.3com.com/bootservices Email: [email protected]

3Com Corporation, Corporate Headquarters, 5400 Bayfront Plaza, P.O. Box 58145, Santa Clara, CA 95052-8145 To learn more about 3Com solutions, visit www.3com.com. 3Com Corporation is publicly traded on Nasdaq under the symbol COMS. 3Com Boot Services was formally know as 3Com DynamicAccess Boot Services.

Copyright © 2001 3Com Corporation. All rights reserved. 3Com, the 3Com logo, DynamicAccess and BootWare are registered trademarks of 3Com Corporation. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Netware is a registered trademark of Novell, Inc. All other company and product names may be trademarks of their respective companies. All specifications are subject to change without notice. Printed in the Canada on recycled paper.

DA120-MRK-DS3 03/01 Rev 4