- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: PXE Boot problem
Switches, Hubs, and Modems
1752805
Members
5330
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-04-2009 04:53 AM
тАО05-04-2009 04:53 AM
PXE Boot problem
we have several vlans routed on a procurve 9300 core switch using udp helper addresses configured for each client vlan.
a client sends out a dhcp request that is forwarded via subnet directed broadcast (that is udp helper address 1.2.3.255 as an example). The client receives offers from all relevant dhcp servers but one. We are using Enteo as a RIS server that is configured to answer dhcp requests. It will offer no IP addresses but only the required boot image information.
The Enteo server receives the dhcp request from the client and sends out the offer with ip address 0.0.0.0 and the boot filename as an dhcp option. Apparently the udp helper on the 9300 core switch does not forward the offer to the requesting dhcp client.
Any ideas?
a client sends out a dhcp request that is forwarded via subnet directed broadcast (that is udp helper address 1.2.3.255 as an example). The client receives offers from all relevant dhcp servers but one. We are using Enteo as a RIS server that is configured to answer dhcp requests. It will offer no IP addresses but only the required boot image information.
The Enteo server receives the dhcp request from the client and sends out the offer with ip address 0.0.0.0 and the boot filename as an dhcp option. Apparently the udp helper on the 9300 core switch does not forward the offer to the requesting dhcp client.
Any ideas?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 01:18 AM
тАО05-06-2009 01:18 AM
Re: PXE Boot problem
Hi, maboko4711 !
At the first step a dhcp client uses a broadcast sending request to a dhcp server.
Afterwards both dhcp server and client use unicasts communicating with each other.
0.0.0.0 means an unknown address.
To be able to communicate with the dhcp server and to accept the dhcp offer the client should have a KNOWN ip address distinct from 0.0.0.0.
If the client and server reside in different ip networks (within different vlans) both should know the routes to each other.
Good luck,
Dmitry
At the first step a dhcp client uses a broadcast sending request to a dhcp server.
Afterwards both dhcp server and client use unicasts communicating with each other.
0.0.0.0 means an unknown address.
To be able to communicate with the dhcp server and to accept the dhcp offer the client should have a KNOWN ip address distinct from 0.0.0.0.
If the client and server reside in different ip networks (within different vlans) both should know the routes to each other.
Good luck,
Dmitry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2009 03:21 AM
тАО05-07-2009 03:21 AM
Re: PXE Boot problem
Add a extra iphelper to your pxe server. That should do the trick.
That means one Iphelper forwarding to your dhcp server and one to your pxe per vlan.
That means one Iphelper forwarding to your dhcp server and one to your pxe per vlan.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP