Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Linux \ Linux PXE unattended installation PXE-E32: TFTP OPen timeout the solution     - What factors affect the performance of Java calls (Programming)

- Java executable file to read information from a database copy (Programming)

- Binary search and modification (Programming)

- jQuery get value drop-down list and select text (Programming)

- Strategy Games Ubuntu installation of Wesnoth 1.12.1 (Linux)

- Ubuntu 14.04 LTS 64-bit install GNS3 1.3.7 (Linux)

- How to query the role of Linux services (Linux)

- C ++ virtual functions Classic Insights (Programming)

- Ubuntu Gnome and Fedora 22 Gnome desktop, extended to achieve global menu (Linux)

- Apache Mina framework Practice (Programming)

- PostgreSQL with the C Completing the storage process instances (Database)

- Dual system Linux (Ubuntu) into the Windows NTFS partition's mount error (Linux)

- Installation on the way to the root source Ubuntu Server 14.04 LTS version Odoo8.0 (Server)

- Linux server security settings to close unused ports (Linux)

- Based on Python: OpenCV simple image manipulation (Programming)

- CentOS 6.4 dial-up Raiders (Linux)

- Merge sort Java implementation (Programming)

- Nginx-1.9.7 TCP reverse proxy (Server)

- Zabbix using Omsa monitor hardware information of Dell server (Server)

- Linux, modify the fstab file system can not start causing solve one case (Linux)

 
         
  Linux PXE unattended installation PXE-E32: TFTP OPen timeout the solution
     
  Add Date : 2018-11-21      
         
         
         
  PXE-E32: TFTP OPen timeout when using Linux to do pxe installation system

Find PXE boot chip error code table, is that tftp is not running

PXE-E32: TFTP open timeout The TFTP "Open" request did not answer and verify that the TFTP service is running.

Restart xinetd service, and determine whether to monitor the port, or have this problem

[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 turn off the firewall, the original firewall is really not closed, it seems that the firewall blocked the tftp connection. Then check the status of selinux. Selinux to disable.

[Root @ localhost /] # service iptables stop

Clear firewall rule: [OK]

Set the chain to ACCEPT policy: filter [OK]

Uninstalling the Iiptables module: [OK]

[Root @ localhost /] #

[Root @ localhost /] #

[Root @ localhost /] # geten

Getenforce getent

[Root @ localhost /] # getenforce

Disabled

[Root @ localhost /] #

Then try unattended installation here! OK!

If PXE-E32: TFTP OPen timeout error message appears, there may be no firewall and disable selinux

Close the firewall directly with: #service iptables stop

Temporarily close selinux: # setenforce 0

Can also be edited

# Vim / etc / selinux / config

SELINUX = disabled

Reboot takes effect

Attached a PXE boot chip error code table, initialize / boot / load Bootstrap error code. Online to find

PXE-E00: Could not find enough free base memory.

PXE master code and UNDI runtime module from the flash memory or the upper memory copy to the basic memory top 480K (78000h) to 640K (A0000h) the remaining space position, this memory must be system BIOS fill zero, if these memory is not zero, PXE The re-arrangement code in the ROM will assume that the memory has been occupied by the system BIOS or other boot ROM.

PXE-E01: PCI Vendor and Device IDs do not match!

When the system BIOS initializes the PCI-based ROM, it will assume that the value of the PCI bus / device / module has been verified in the AX register. If the AX register defines the value in the AX register, The PCI device does not match the UNDI device and this error code will appear.

PXE-E04: Error reading PCI configuration space

If any PCI BIOS calls cause the PCI Setup space to return an error code, this message will appear and this message will not appear on the finished BIOS and hardware.

PXE-E05: EEPROM checksum error

This message appears if the NIC's EEPROM contents are corrupted. Damage to the EEPROM contents usually occurs when the system is suddenly reset (Reset) or powered down while the EEPROM is being programmed, and PXE ROM will not boot if this message appears.

PXE-E06: Option ROM requires DDIM support

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

PXE-E07: PCI BIOS calls not supported

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

PXE-E08: Unexpected API error.API: xxxxh Status: xxxxh

This message appears if the PXE API returns a status code that is not expected by the Runtime Loader

PXE-E09: Unexpected UNDI loader error.Status: xxxxh

This message appears if the UNDI run-time loader returns an unexpected status code

ARP error code

PXE-E11: ARP timeout PXE ROM

Will retry the ARP request four times, if you can not get any valid ARP reply, this information will appear, this information is usually derived from some network and service settings error, the usual reasons are:

1. Set the DHCP class identifier (Option 60) on the DHCP master server but install the ProxyDHCP service on the other server.

2. Use 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 message will appear and will not be encountered in the finished BIOS. The code "nn" is the error code returned by the BIOS Extended Memory Copy Service (Int 15h, AH = 87h).

PXE-E21: BIS integrity check failed

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

PXE-E22: BIS image / credential validation failed

The downloaded image and certificate do not match the client key

PXE-E23: BIS initialization failed BIS

Unable to initialize, 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 Can not detect BIS Enabled / Disabled

PXE-E26: BIS free memory failed

Failed to free BIS allocated memory

PXE-E27: BIS get signature information failed Request BIS certificate type information can not be determined.

PXE-E28: BIS bad entry structure checksum The BIS entry structure in the SM BIOS table is invalid.

TFTP / MTFTP error code

PXE-E32: TFTP open timeout The TFTP "Open" request did not answer and verify that the TFTP service is running.

PXE-E35: TFTP read timeout The next TFTP packet was not received

PXE-E36: Error received from TFTP server Received an erroneous TFTP packet from the TFTP server

PXE-E38: TFTP can not open connection A hardware error occurred when attempting to send a TFTP "Open" packet

PXE-E39: TFTP can not read from connection A hardware error occurred while attempting to send a TFTP reply packet.

PXE-E3A: TFTP too many packages. This message means that one of the following occurs: 1. You tried to use TFTP to download a larger file than the allocated buffer 2. You as a slave (Slave) client Side uses MTFTP to start downloading a file, and when you become a master (Master) client, the file size has changed.

PXE-E3B: TFTP error-File not found The requested file could not be found on the TFTP server.

PXE-E3C: TFTP error-Access violation The requested file was found on the TFTP server, but the TFTP service does not have sufficient access to open / read the file.

PXE-E3F: TFTP packet size is invalid The received TFTP packet size exceeds 1456 bytes. BOOTP / DHCP error code

PXE-E51: No DHCP or proxyDHCP offers were received The client has not received any valid DHCP, BOOTP, or proxyDHCP replies.

PXE-E52: proxyDHCP offers were received.No DHCP offers were received The client has not received any valid DHCP or BOOTP replies, but the client has received at least one valid proxyDHCP response.

PXE-E53: No boot filename received The client has received at least one valid DHCP / BOOTP reply, but no boot file name is available for download.

PXE-E55: proxyDHCP service did not reply to request on port 4011 The client sent a proxyDHCP request to the DHCP server on port 4011 and did not receive a reply.

UNDI error code

PXE-E60: Invalid UNDI API function number An API that is used by the underlying code can not be executed in UNDI ROM.

PXE-E61: Media test failed, check cable The network cable is not plugged in or not connected. The network cable may be bad, the network card is bad, or the connection is faulty.

PXE-E63: Error while initializing the NIC initialization NIC hardware error, it is recommended to change the network card.

PXE-E64: Error while initializing the PHY attempt to initialize the PHY hardware error, the proposed network card.

PXE-E65: Error while reading the configuration data Read the network card setup data error, the proposed network card.

PXE-E66: Error while reading the initialization data read card initialization data error, it is recommended to change the network card.

PXE-E67: Invalid MAC address MAC address stored in this card is invalid, it is recommended to change the network card

PXE-E68: Invalid EEPROM checksum EEPROM checksum error, EEPROM content is damaged, it is recommended to change the network card

PXE-E69: Error while setting interrupt Can not configure the hardware interrupt, it is recommended to change the network card.

Bootstrap and Discovery error codes

PXE-E74: Bad or missing PXE menu and / or prompt information PXE identification detected but boot menu and / or boot command prompt identified Not found / not present

PXE-E76: Bad or missing multicast discovery address The multicast creation was started but the multicast creation address identifier does not match

PXE-E77: Bad or missing discovery server list Both multicast and broadcast discovery (Discovery) are disabled or enabled using the server list, but the server list identifies no discovery / absence

PXE-E78: Could not locate boot server A valid boot server response was not received by the client

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

PXE-E7A: Client could not locate asecure server This message is displayed when the client does not receive any security information from the boot server and BIS on the client is enabled.

PXE-E7B: Missing MTFTP server IP address This message is displayed when the ROM does not receive the PXE Create Identity or proxyDHCP response and the DHCP SIADDR area is set to 0.0.0.0.

Uncategorized error code

PXE-EA0: Network boot canceled by keystroke The user presses "Esc" or "Ctrl C" during DHCP / Create / TFTP.

The base code / UNDI Loader error code

PXE-EC1: BaseCode ROM ID structure was not found The UNDI boot module could not discover the underlying code ROM ID structure. If the system has a base code ROM image, it may be corrupted

PXE-EC3: BaseCode ROM ID structure is invalid Base code ROM ID structure is defective, base code ROM image is corrupted

PXE-EC4: UNDI ROM ID structure was not found The base code load module can not be located in the UNDI ROM ID structure

PXE-EC5: UNDI ROM ID structure is invalid UNDI ROM image is corrupt

PXE-EC6: UNDI driver image is invalid UNDI ROM image is corrupt

PXE-EC8:! PXE structure was not found in UNDI driver code segment The UNDI ROM image is corrupt or can not be loaded by the BIOS. This error message is usually caused by one or more of the following reasons:

1. When the point at which a LOM image is about to be called, the NIC image is being programmed into the BIOS

2. The PXE optional ROM is corrupted or deleted during the memory allocation of the self-test memory manager (POST Memory Manager, $ PMM) until the PXE optional ROM begins to boot.

3. The UNDI_Loader structure was not loaded correctly during loading of the ROM structure

PXE-EC9: PXENV structure was not found in UNDI driver code segment The UNDI ROM image may be corrupted or not loaded by the BIOS. This error message is usually caused by three reasons:

1. When the point at which a LOM image is about to be called, the NIC image is being programmed into the BIOS

2. The PXE optional ROM is corrupted or deleted during the memory allocation of the self-test memory manager (POST Memory Manager, $ PMM) until the PXE optional ROM begins to boot.

3. The UNDI_Loader structure was not loaded correctly during loading of the ROM structure.
     
         
         
         
  More:      
 
- Nginx + ownCloud + PHP + MySQL to build personal private cloud under CentOS7 (Server)
- Using Libreoffice under ubuntu (Linux)
- CentOS7 iptables (Linux)
- Oracle database with test data insertion speed (Database)
- Linux remote wake the computer original code [C] (Linux)
- Java Adapter Mode (Programming)
- How to install the NVIDIA 358.16 driver in Ubuntu 15.10,14.04 (Linux)
- Oracle local user login authentication fails ORA-01031 insufficient privileges (Database)
- Import and export myloader accelerate mydumper (Database)
- Elaborate .NET Multithreading: Using Task (Programming)
- Ubuntu install ruby (Linux)
- Exploring the Android Listview display confusion (Programming)
- Based Docker build stand-alone high-availability cluster Hadoop2.7.1 Spark1.7 (Server)
- Manually generate AWR reports (Database)
- HAproxy let IP recording back-end RS (Server)
- Ubuntu 12.04 install RTL8723BE wireless network card driver (Programming)
- GitLab installation configuration notes (Linux)
- Mahout source code analysis: FP-Growth algorithm parallelization (Programming)
- Setting the RedHat9 Intrusion Detection System (Linux)
- Phoenix agents use P2P WebRTC development (Programming)
     
           
     
  CopyRight 2002-2020 newfreesoft.com, All Rights Reserved.