September 2002 |
|
Prepared By |
|
PSG Marketing |
|
Compaq Computer |
|
Corporation |
|
C O N T E N T S |
|
Introduction .................... |
3 |
List of Terms ......................... |
3 |
Current PXE |
|
Support Products ............ |
4 |
PXE Operation |
|
Flow: Corrupt |
|
Firmware Scenario .......... |
5 |
Replacing Corrupt |
|
FLASH Image Using |
|
NetXfer ............................ |
7 |
PXE Operation |
|
Flow: Good |
|
Firmware Scenario ........ |
11 |
1774-1002A-WWEN
WHITE PAPER
PXE Operation Flow
for Compaq Evo Thin Clients
This paper explains how a Compaq Evo Thin Client communicates with the server in a PXE environment and offers solutions for replacing corrupted firmware.
1
WHITE PAPER (cont.)
Notice
© 2002 Compaq Information Technologies Group, L.P.
Compaq, the Compaq logo, and Evo are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries. Microsoft and Windows are trademarks of Microsoft Corporation in the U.S. and/or other countries.
All other product names mentioned herein may be trademarks of their respective companies.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
PXE Operation Flow for Compaq Evo Thin Clients
North America First Edition (September 2002)
1774-1002A-WWEN
2
WHITE PAPER (cont.)
PXE (Pre-boot Execution Environment) is supported on both the Compaq Evo T20 and T30 NTe PXE and XPe products. Intel’s PXE is a protocol that defines interaction between TCP/IP,
DHCP and TFTP to enable a client to download a pre-boot environment from a server. Before the operating system is started a PXE enabled client broadcasts a DHCPDISCOVER request with an extension tag that identifies it as a PXE request. A DHCP server or DHCP proxy listening for PXE requests then sends the client a list of boot servers. The client uses TFTP to download an ITF Agent, which in turn downloads a complete binary image to the terminal.
For additional information about PXE please see the Preboot Execution Environment (PXE) Specification white paper. This paper is available for download at the following URL:
www.intel.com/labs/manage/wfm/wfmspecs.htm
The following is a list of acronyms used in this paper:
Table 1. List of Terms
Acronym |
Definition |
BIOS |
Basic Input Output System |
BOOTP |
Bootstrap Protocol |
DHCP |
Dynamic Host Configuration Protocol |
Img2Dev |
Image to Device (Agent) |
IP |
Internet Protocol |
ITF |
Internal Transport Function (Agent) |
POST |
Power On Self Test |
PXE |
Preboot eXecution Environment |
TCP |
Transmission Control Protocol |
TFTP |
Trivial File Transfer Protocol |
WOL |
Wake On LAN |
1774-1002A-WWEN
3
WHITE PAPER (cont.)
Table 2. Current PXE Support Products
Model |
Part Number |
Config Code |
O/S |
Description |
|
T30 |
238618-xxx |
JS24 |
NTe |
T30 |
64F/64R NTe PXE w/o Browser |
T20 |
290804-xxx |
JS3K |
NTe |
T20 |
64F/64R NTe PXE w/o Browser |
T30 |
305254-xxx |
JS3M |
NTe |
T30 |
128F/128R NTe PXE with |
|
|
|
|
Browser |
|
T20 |
305253-xxx |
JS3L |
NTe |
T20 |
128F/128R NTe PXE with |
|
|
|
|
Browser |
|
T20 XPe |
308791-xxx |
JS3N |
XPe |
T20 |
300M XPe with PXE 192/256 |
T30 XPe |
308792-xxx |
JS3Q |
XPe |
T30 |
300M XPe with PXE 192/256 |
T30 XPe |
311335-xxx |
JS3S |
XPe |
T30 |
300M XPe with PXE 256/256 |
T20 XPe |
311334-xxx |
JS3R |
XPe |
T20 |
300M XPe with PXE 256/256 |
NOTE: PXE is not supported on CE 2.12 or CE.NET products or on previous NTe products.
1774-1002A-WWEN
4