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

Laborde, Louis (HP Servers) louis.laborde at hp.com
Wed Feb 12 18:52:55 UTC 2014


Hello iPXE developers,

I am trying to get iPXE to concurrently use two interfaces each in their own subnet on my 2-port Mellanox adapter:
1st subnet on net0 for access to the SAN device, and 2nd subnet on net1 for access to the PXE server to deploy the OS
(WDS to deploy Windows).

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:

net0: a0:1d:48:b5:00:e4 using ConnectX3 on PCI01:00.0 (open)
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]
Waiting for link-up on net0... ok
DHCP (net0 a0:1d:48:b5:00:e4).......... ok
net0: 192.168.200.10/255.255.255.0
Root path: iscsi:192.168.200.3::::iqn.1991-05.com.microsoft:dl360g72-anders00e4-target1
Registered SAN device 0x80
Booting from SAN device 0x80
Boot from SAN device 0x80 failed: Operation canceled
Preserving SAN device 0x80
net1: a0:1d:48:b5:00:e5 using ConnectX3 on PCI01:00.0 (open)
  [Link:down, TX:0 TXE:0 RX:0 RXE:0]
Waiting for link-up on net1... ok
DHCP (net1 a0:1d:48:b5:00:e5).......... ok
net0: 192.168.200.10/255.255.255.0 (inaccessible)
net1: 15.199.180.143/255.255.248.0 gw 15.199.176.1
Next server: 15.199.178.16
Filename: boot\x86\wdsnbp.com
Root path: iscsi:192.168.200.3::::iqn.1991-05.com.microsoft:dl360g72-anders00e4-target1
Could not open SAN device: Error 0x03852019
No more network devices


Thanks,
Louis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20140212/62cfbc8b/attachment.htm>


More information about the ipxe-devel mailing list