Provisioning host with multiple NICs - no PXE

Support
1

There is no problem provisioning a host with a single NIC. Once a second
one is added I get
"PXE-EC8: !PXE structure was not found in UNDI driver code segment
PXE-M0F: Exiting Intel PXE ROM
Operating system not found"
I'm using foreman 1.8.2, API(REST) v2.
I'm setting all interfaces_attributes to managed=False, provision=False,
except for the one I am attaching to the right switch and that one is: provision=True,
primary=True, managed=True.
Is there anything I'm missing configuring the host interfaces_attributes?

2

Hello,

> There is no problem provisioning a host with a single NIC. Once a second
> one is added I get
> "PXE-EC8: !PXE structure was not found in UNDI driver code segment
> PXE-M0F: Exiting Intel PXE ROM
> Operating system not found"

What kind of NIC is the one you've added? Can you provide full name and
lspci output?

> I'm using foreman 1.8.2, API(REST) v2.
> I'm setting all interfaces_attributes to managed=False, provision=False,
> except for the one I am attaching to the right switch and that one is: provision=True,
> primary=True, managed=True.
> Is there anything I'm missing configuring the host interfaces_attributes?

How are you provisioning the server. Is this standard PXE booting for
already registered host? Bootdisk? Discovery?

··· -- Later, Lukas #lzap Zapletal
3

Hi Lukas,
Thanks for your interest in my problem.
I should've provided more info. The compute resource I'm provisioning on is
VMware, the NICs are E1000 and VMXNET3(distributed port switch). The hosts
are created from ground up so no, they are not already registered.

··· On Thursday, March 31, 2016 at 4:31:51 PM UTC+3, Lukas Zapletal wrote: > > Hello, > > > There is no problem provisioning a host with a single NIC. Once a second > > one is added I get > > "PXE-EC8: !PXE structure was not found in UNDI driver code segment > > PXE-M0F: Exiting Intel PXE ROM > > Operating system not found" > > What kind of NIC is the one you've added? Can you provide full name and > lspci output? > > > I'm using foreman 1.8.2, API(REST) v2. > > I'm setting all interfaces_attributes to *managed=False, > provision=False*, > > except for the one I am attaching to the right switch and that one is: > *provision=True, > > primary=True, managed=True*. > > Is there anything I'm missing configuring the host > interfaces_attributes? > > How are you provisioning the server. Is this standard PXE booting for > already registered host? Bootdisk? Discovery? > > -- > Later, > Lukas #lzap Zapletal >
4

> I should've provided more info. The compute resource I'm provisioning on is
> VMware, the NICs are E1000 and VMXNET3(distributed port switch). The hosts

E1000 drivers are known to be buggy, use VMXNET3 for both NICs. How are
you provisioning? Is this plain PXE booting into PXELinux or Bootdisk
provisioning? Bootdisk does not work with E1000 for sure, but there is a
workaround - upgrade iPXE firmware on Foreman host and regenerate disks.

··· -- Later, Lukas #lzap Zapletal
5

Actually there are 3 NICs, 2 of them are VMXNET3 (the provision interface
is VMXNET3). The weird thing is that PXE works if I just leave foreman pick
the provision/primary NIC. If I provision from an image I have to select
the NIC either wise foreman fails on SSH connection . I want to be
consistent on both cases. It is basic PXE.

··· On Tue, Apr 5, 2016 at 10:30 PM, Lukas Zapletal wrote:

I should’ve provided more info. The compute resource I’m provisioning on
is
VMware, the NICs are E1000 and VMXNET3(distributed port switch). The
hosts

E1000 drivers are known to be buggy, use VMXNET3 for both NICs. How are
you provisioning? Is this plain PXE booting into PXELinux or Bootdisk
provisioning? Bootdisk does not work with E1000 for sure, but there is a
workaround - upgrade iPXE firmware on Foreman host and regenerate disks.

–
Later,
Lukas #lzap Zapletal

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/P0JICyEFhVg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

6

> Actually there are 3 NICs, 2 of them are VMXNET3 (the provision interface
> is VMXNET3). The weird thing is that PXE works if I just leave foreman pick
> the provision/primary NIC. If I provision from an image I have to select
> the NIC either wise foreman fails on SSH connection . I want to be
> consistent on both cases. It is basic PXE.

The error message says "Intel", you had to be booting the E1000.

··· -- Later, Lukas #lzap Zapletal
7

Setup all the interfaces as VMXNET3 and got the same error PXE-EC8 and
PXE-M0F

··· On Tue, Apr 5, 2016 at 11:12 PM, Lukas Zapletal wrote:

Actually there are 3 NICs, 2 of them are VMXNET3 (the provision interface
is VMXNET3). The weird thing is that PXE works if I just leave foreman
pick
the provision/primary NIC. If I provision from an image I have to select
the NIC either wise foreman fails on SSH connection . I want to be
consistent on both cases. It is basic PXE.

The error message says “Intel”, you had to be booting the E1000.

–
Later,
Lukas #lzap Zapletal

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/P0JICyEFhVg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

8

Wanted to add that if I don't set the right interface as provision and
primary OS installation finishes successfully, but the wrong IP is set to
that NIC since foreman sets the first interface as provision/primary.
So I still need help on this

··· On Tue, Apr 5, 2016 at 11:23 PM, Adrian Ghidu wrote:

Setup all the interfaces as VMXNET3 and got the same error PXE-EC8 and
PXE-M0F

On Tue, Apr 5, 2016 at 11:12 PM, Lukas Zapletal lzap@redhat.com wrote:

Actually there are 3 NICs, 2 of them are VMXNET3 (the provision
interface
is VMXNET3). The weird thing is that PXE works if I just leave foreman
pick
the provision/primary NIC. If I provision from an image I have to select
the NIC either wise foreman fails on SSH connection . I want to be
consistent on both cases. It is basic PXE.

The error message says “Intel”, you had to be booting the E1000.

–
Later,
Lukas #lzap Zapletal

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/P0JICyEFhVg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.