 - The Preboot Execution Environment (PXE) is an industry standard client/server interface that allows networked computers that are not yet loaded with an operating system to be configured and booted remotely by an administrator. The PXE code is typically delivered with a new computer on a read-only memory chip or boot disk that allows the computer (a client) to communicate with the network server so that the client machine can be remotely configured and its operating system can be remotely booted. PXE provides three things:1) The Dynamic Host Configuration Protocol (DHCP), which allows the client to receive an IP address to gain access to the network servers. 2) A set of application program interfaces (API) that are used by the client's Basic Input/Output Operating System (BIOS) or a downloaded Network Bootstrap Program (NBP) that automates the booting of the operating system and other configuration steps. 3) A standard method of initializing the PXE code in the PXE ROM chip or boot disk. The PXE process consists of the client notifying the server that it uses PXE. If the server uses PXE, it sends the client a list of boot servers that contain the operating systems available. The client finds the boot server it needs and receives the name of the file to download. The client then downloads the file using Trivial File Transfer Protocol (Trivia File Transfer Protocol) and executes it, which loads the operating system. If a client is equipped with PXE and the server is not, the server ignores the PXE code preventing disruption in the DHCP and Bootstrap Protocol (BP) operations. The advantages of using PXE include: - The client machine does not necessarily need an operating system or even a hard disk.
- The client machine can be rebooted in the event of hardware or software failure. This allows the administrator to diagnose and perhaps fix the problem.
- Since PXE is vendor-independent, new types of computers can easily be added to the network.
 |
Learn more about LANs (Local Area Networks) |
| LAN administration guide: LAN administration is an arduous task and your responsibilities often involve many different aspects and may include many tasks. This guide will help you with each step and task. |
| LAN network design considerations: What are the steps to be kept in mind while designing a network having three hundred nodes within a three-floor building and one server room? |
| 10 Gigabit Ethernet tutorial: Connecting data centers, storage, LAN and beyond: Learn how to choose 10 Gigabit Ethernet cabling and components, why new Gigabit Ethernet protocols will improve performance, and how it can all result in data center optimization. |
| Best practices for securing your wireless LAN: Learn best practices for securing a wireless LAN (WLAN) in the enterprise, from systematically monitoring your WLAN for intruders to protecting users and the network itself. |
| A basic virtualized enterprise -- from 'Network Virtualization': Learn why and how to virtualize the network in this chapter from 'Network virtualization' by Victor Moreno and Kumar Reddy. |
| Configuring VLANs: Learn how to configure a virtual LAN (VLAN) in this step-by-step, automated, 15-minute demo. |
| Network administration guide: Network administration responsibilities, such as network design, troubleshooting, backup, documentation, security, and managing users are discussed in this guide. |
| LAST UPDATED: |
12 May 2003
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
 |
 |
| |
RELATED GLOSSARY TERMS
| Terms from Whatis.com − the technology online dictionary |
 |
32-bit IP addressing
(SearchNetworking.com)
32-bit IP addressing is the IP address scheme used in Internet Protocol 4 (IPv6 uses a 128-bit system)... (Continued)
|
|
ARCNET
(SearchNetworking.com)
ARCNET is a widely-installed local area network (LAN) technology that uses a token-bus scheme for managing line sharing among the workstations and...
|
|
|
Show me everything on 