[ipxe-devel] switch causing DHCP timeout

Christian Hesse list at eworm.de
Mon May 5 11:39:01 BST 2014


Wissam Shoukair <wissams at mellanox.com> on Mon, 2014/05/05 10:19:
> Hi,
> I'm trying to chain-load undi-only using net0. My setup has a PXE client
> and a DHCP server and a switch between them. (there are other machines
> connected to the same switch) After fetching the undi_only from the DHCP
> server, it opens its own net0 and eventually the lower net0 net device.
> After it opens the devices, it tries to send DHCP DISCOVER to the server.
> Apparently, the switch takes a long time to settle down after the port came
> up, and because of this the DHCP DISCOVER is not received by the server.
> 
> To confirm that this is a timing issue, I delayed the DHCP packet by
> inserting a sleep for 25 seconds right after the chainloaded undi opened
> the net device, and it did fix the issue. A good solution for this might be
> implementing ARP PING, and instead of the sleep, we can change it by doing
> ARP PING until we get a response and then we can send the DHCP packet.
> 
> Does anyone know a better and a simpler solution for this switch issue ?

I've seen problems like this with Cisco switches. Default port configuration
waits a long time (30 seconds?) to make sure there is no loop or similar.
Every client having a timeout below 30 seconds is affected.

Setting these ports to mode "PortFast" fixes the timeout problem. Be aware
that the port does not go through the complete spanning tree initialization
procedure then. Make sure to take a look at the documentation.

Other brands probably do have similar configuration options.
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Chris           get my mail address:    */=0;b=c[a++];)
putchar(b-1/(/*               gcc -o sig sig.c && ./sig    */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20140505/c56e360e/attachment.asc>


More information about the ipxe-devel mailing list