- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Deployment Server boot file problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2013 07:24 AM - edited 02-05-2013 07:27 AM
02-05-2013 07:24 AM - edited 02-05-2013 07:27 AM
Deployment Server boot file problems
Alexander was looking to solve a boot file issue with a customer:
**************
Customer had an Insight Control Deployment Server with DHCP on one machine. But Customer decided to build own deployment network.
They changed DHCP server to external, rebuilt boot images( in PXE configuration), but we have such problem with a certificate error.
***************
Input from Arnout:
***************
Make sure they have set the correct DHCP options.
In short option 60 if PXE and DHCP on same server.
Option 66 if PXE and DHCP on different Server
Option 66 and 03 if PXE and DHCP on different server and different subnet.
And from http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebase/00000138.html
PXE-E53: No boot filename received.
The client received at least one valid DHCP/BOOTP offer, but does not have a boot filename to download. There are several possible causes:
• |
The DHCP Server and the PXE Server were located on the same server, but one of them was moved to a different server. This would result in an incorrect PXE Server configuration. |
• |
The DHCP relay agent, either a Proxy DHCP Server or a switch configured with helper addresses, is not configured correctly. For example, if DHCP and PXE are on separate servers, the DHCP relay agent needs to have both addresses in its configuration. |
• |
If the Microsoft DHCP service is installed on the PXE server, but is disabled or unconfigured, Altiris PXE Setup configures PXE to work with the local DHCP service (even if the DHCP service is disabled). This causes the PXE server to not respond to PXE clients that get a DHCP address from DHCP services running elsewhere on the network.
******************
Any other comments or suggestions?
|
- Tags:
- DHCP