[ipxe-devel] iPXE concurrent use of two interfaces in different subnets not working

Laborde, Louis (HP Servers) louis.laborde at hp.com
Fri Mar 14 00:40:40 GMT 2014


Hello Michael,

Can this "sanhook" command be encoded in an iPXE-specific DHCP option, like keep-san is,
of does this script need to be pointed to by a boot filename URL, to avoid any manual action?

Thanks,
Louis

-----Original Message-----
From: Michael Brown [mailto:mcb30 at ipxe.org] 
Sent: Thursday, March 13, 2014 5:17 PM
To: Laborde, Louis (HP Servers); ipxe-devel at lists.ipxe.org
Subject: Re: [ipxe-devel] iPXE concurrent use of two interfaces in different subnets not working

On 12/02/14 18:51, Laborde, Louis (HP Servers) wrote:
> The problem is that after discovering the not bootable SAN device on 
> net0, and trying to PXE boot over net1, iPXE can't access the SAN 
> device anymore on net0, and the PXE boot over net1 fails.
>
> Here is the spew seen on the console:
> <snip>

You'll need to use a slightly more manual process to avoid the automatic closing of interfaces which iPXE does to conserve memory:

#!ipxe
dhcp net0
sanhook ${root-path}
dhcp net1
chain ${filename}

Michael


More information about the ipxe-devel mailing list