Linux PXE Unattended installation appears pxe-e32:tftp OPen Timeout solution

Source: Internet
Author: User
Keywords Linux pxe
Tags address api bios change check client clients code

Pxe-e32:tftp OPen timeout occurs when you do PXE install system in Linux

Find the PXE boot chip error code table that says TFTP is not running

The PXE-E32:TFTP Open timeout tftp "Open" request is not answered to verify that the TFTP service is running.

Restart the XINETD service and determine if the port is listening or not.

[root@localhost/]# Service xinetd restart

Stop xinetd: [OK]

Start xinetd: [OK]

[Root@localhost/]#

[Root@localhost/]# Netstat-anltup | grep:69

UDP 0 0 0.0.0.0:69 0.0.0.0:* 25641/xinetd

[Root@localhost/]#

Try to shut down the firewall, the original firewall is really not off, it appears that the firewall blocked TFTP connection. Then look at the status of the SELinux. SELinux to disable.

[root@localhost/]# service iptables stop

Clear firewall rules: [OK]

Set chains to ACCEPT policy: filter [OK]

Uninstalling Iiptables module: [OK]

[Root@localhost/]#

[Root@localhost/]#

[Root@localhost/]# Geten

Getenforce getent

[Root@localhost/]# Getenforce

Disabled

[Root@localhost/]#

Then try an unattended installation here! ok!

If you receive an error message for the PXE-E32:TFTP OPen timeout, it is possible that you have not shut down the firewall and disabled SELinux

Close the firewall directly with: #service iptables stop

Temporary shutdown selinux:# Setenforce 0

You can also edit

# Vim/etc/selinux/config

Selinux=disabled

Reboot effective

A "PXE boot chip error code table, initialization/boot/Load Bootstrap error code" is attached. Online Search

Pxe-e00:could not find enough free base memory.

The PXE main code and the Undi runtime module are copied from the flash or upper memory to the remaining space in the top 480K (78000h) to 640K (a0000h) of the base memory, which must be filled in by the system BIOS 0 if the memory is not filled 0, PXE The reset code in the ROM will assume that the memory is already occupied by the system BIOS or other boot ROM.

Pxe-e01:pci noun and Device IDs do not match!

This information is not possible in the production BIOS, and when the system BIOS initializes a PCI based ROM, it assumes that the PCI bus/device/module (bus/device/function) value has been audited in the AX register. This error code appears if the PCI device defined in the AX register does not match the Undi device.

Pxe-e04:error reading PCI revisit space

If any PCI BIOS calls cause the PCI settings space to return an error code, this information will appear and will not appear on the production BIOS and hardware.

Pxe-e05:eeprom Checksum Error

This message appears if the contents of the NIC Eeprom are corrupted. The damage to the EEPROM content usually occurs when the system is suddenly reset (reset) or power off when programming the network card EEPROM, and if this information occurs, the PXE ROM will not perform the boot.

Pxe-e06:option ROM requires ddim support

This information will not appear in the production BIOS, and PCI optional ROM usually must be set to ddim optional rom (usually must be placed in read/write upper memory)

PXE-E07:PCI BIOS calls not keyword

This information will not appear in the production BIOS, and the PCI BIOS must have a PCI BIOS service.

pxe-e08:unexpected API error. Api:xxxxh Status:xxxxh

This information appears if the PXE API returns a status code that is not expected by the runtime loader (Runtime Loader)

pxe-e09:unexpected Undi Loader error. Status:xxxxh

This information appears if the Undi runtime loader (Runtime Loader) returns an unexpected status code

ARP Error codes

Pxe-e11:arp Timeout PXE ROM

The ARP request will be retried four times, and if no valid ARP reply can be obtained, this information will often originate from some Network and service setup errors, usually due to:

1. A DHCP class identifier (Option 60) is set on the DHCP master server, but the PROXYDHCP service is installed on another server.

2. Using a router that does not respond to ARP requests

BIOS and BIS error codes

Pxe-e20:bios extended memory copy error. Ah==nn

If the BIOS extended memory Copy service returns an error message, this information will appear and will not encounter this information in the production BIOS, and the code "NN" returns an error code for the BIOS extended memory Copy Service (Int 15h,ah=87h).

Pxe-e21:bis Integrity check failed

This information is displayed if the BIS image in extended memory is corrupted

Pxe-e22:bis image/credential validation failed

Downloaded images and certificates do not match client keywords

Pxe-e23:bis initialization failed BIS

cannot be initialized, no more data available

Pxe-e24:bis shutdown failed BIS

Unable to stop, no more data available

Pxe-e25:bis Get Boot object authorization check flag failed--2

PXE boot chip error code table cannot detect bis enabled/disabled

Pxe-e26:bis Free Memory failed

Unable to free bis allocated memory

Pxe-e27:bis Get signature information failed request BIS certificate Type information cannot be determined.

The BIS entry structure in the Pxe-e28:bis bad entry businessesflat-out checksum SM BIOS table is invalid.

TFTP/MTFTP error code

The PXE-E32:TFTP Open timeout tftp "Open" request is not answered to verify that the TFTP service is running.

PXE-E35:TFTP read timeout did not receive the next TFTP packet

Pxe-e36:error received from TFTP server received an incorrect TFTP packet from the TFTP servers

pxe-e38:tftp cant open connection A hardware error occurred while trying to send a TFTP "open" package

Pxe-e39:tftp cant read from connection A hardware error occurred while trying to send a TFTP answer package

Pxe-e3a:tftp too many packages. This information means that one of the following two situations occurs: 1. You are attempting to download a file 2 that is larger than the allocated buffer by using TFTP. You start downloading a file as a client using Slave from (mtftp) clients, And when you become a primary (master) client, the size of this file changes.

The file requested by Pxe-e3b:tftp Error–file not found cannot be found on the TFTP server.

Pxe-e3c:tftp error–access violation has found the requested file on the TFTP server, but the TFTP service does not have sufficient access rights to open/Read files.

PXE-E3F:TFTP packet the size is invalid received a TFTP packet size exceeding 1456bytes BOOTP error code

Pxe-e51:no DHCP or PROXYDHCP offers were received clients do not receive any valid DHCP, BOOTP, or PROXYDHCP responses.

PXE-E52:PROXYDHCP offers were received. No DHCP offers were received client received no valid DHCP or BOOTP answer, but the client received at least one valid PROXYDHCP response.

Pxe-e53:no boot filename received client received at least one valid BOOTP answer, but no boot filename is available to download.

PXE-E55:PROXYDHCP Service did not reply to request on port 4011 clients send a PROXYDHCP request to the DHCP server 4011 port and did not receive a reply.

Undi error code

Pxe-e60:invalid Undi API function number a API used by the CODEBASE cannot be executed in Undi ROM.

Pxe-e61:media Test Failed,check cable network cable is not plugged in or not connected, may be a bad network, network card bad or connectivity problems.

Pxe-e63:error while initializing the NIC has an error initializing the NIC hardware, it is recommended to change the NIC.

Pxe-e64:error while initializing an error occurred while attempting to initialize the PHY hardware, it is recommended that you change the NIC.

Pxe-e65:error while reading the revisit data reads the network card to set up the datum to have the error, recommends the change network card.

Pxe-e66:error while reading the initialization data read the NIC initialization error, we recommend that you change the network card.

Pxe-e67:invalid MAC address is stored in this network card MAC addresses are not valid, it is recommended to change the network card

Pxe-e68:invalid EEPROM checksum EEPROM checksum error, EEPROM content has been corrupted, recommended to change the NIC

Pxe-e69:error while setting interrupt cannot configure hardware interrupts, it is recommended to change the NIC.

Bootstrap and Discovery error codes

Pxe-e74:bad or missing PXE menu and/or prompt information has detected a PXE identity but the boot menu and/or boot command prompt identity is not found/does not exist

Pxe-e76:bad or missing multicast discovery address multicast creation started but multicast creation addresses identity mismatch

Pxe-e77:bad or missing Discovery Server List multicast and broadcast Creation (discovery) are disabled or enabled with the server list, but the server list identity is not found/does not exist

Pxe-e78:could not locate boot server valid bootstrap answer not received by client

PXE-E79:NBP is too large to fit in free base memory NBP too big, exceeding client base memory capacity

Pxe-e7a:client could not locate Asecure server displays this information when the client does not receive any security information from the boot server and the BIS on the client is enabled.

Pxe-e7b:missing mtftp Server IP address this information is displayed when the ROM does not receive a PXE create identity or PROXYDHCP response and the DHCP siaddr zone is set to 0.0.0.0.

Unclassified error Codes

Pxe-ea0:network boot canceled by keystroke user pressed the "ESC" or "Ctrl C" key during dhcp/creation/tftp

Base Code/undi loader error code

The Pxe-ec1:basecode ROM ID businessesflat-out is not found Undi boot module could not find the underlying code ROM ID structure. If there is an underlying code ROM image in the system, it may be corrupted

Pxe-ec3:basecode ROM ID businessesflat-out is invalid the underlying code ROM ID structure is problematic and the underlying code ROM image is corrupted

Pxe-ec4:undi ROM ID businessesflat-out is not found base code load module cannot be positioned in Undi ROM ID structure

Pxe-ec5:undi ROM ID businessesflat-out is invalid Undi rom image is corrupted

Pxe-ec6:undi driver image is invalid Undi ROM image has been corrupted

pxe-ec8:! PXE Businessesflat-out is not found in Undi driver code segment Undi ROM image has been corrupted or could not be loaded by the BIOS, this error message is usually caused by one or three of the following reasons:

1. The point-in-time of a LOM image will be invoked immediately, and the network card image is being programmed into the BIOS

2. Before the PXE optional ROM starts, the PXE optional ROM loading self-test memory Manager (Post Memory Manager, $PMM) is corrupted or deleted during memory allocation.

3. The undi_loader structure was not loaded correctly during the load ROM structure

Pxe-ec9:pxenv Businessesflat-out is not found in Undi driver code segment the ROM image may be corrupted or not loaded by the BIOS, this error message is usually caused by the following three reasons:

1. The point-in-time of a LOM image will be invoked immediately, and the network card image is being programmed into the BIOS

2. Before the PXE optional ROM starts, the PXE optional ROM loading self-test memory Manager (Post Memory Manager, $PMM) is corrupted or deleted during memory allocation.

3. The undi_loader structure was not loaded correctly during the load ROM structure.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

Tags Index: