I've got some problems with discovery and IBM servers (x3550 M5) with
mulple nics.
The IBM servers are configured as follows:
> asu show BootOrder.BootOrder
BootOrder.BootOrder="PXE Network=Hard Disk 0"
The server has 4 nics that are connected to the same VLAN where foreman
lives.
If server is in build stage, everything works as expected: discovery image
gets downloaded, server sends facts about itself to foreman, I can click
autoprovision, server reboots, OS gets installed, then anaconda reboots the
server and problem arise:
server boots from NIC1 with PXE, as this MAC address is recognized by tftp
the server gets
LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT 0
and I've got 'Booting from local disk…' sign
then follows
PXE-M0F: Exiting Broadcom PXE ROM
then IBM server (for some reason) tries to boot from the next NIC
of course Foreman/TFTP knows nothing about this NIC (MAC-address) and
discovery image gets downloaded and now I've new 'Discovered host',
effectively server never boots into OS
Please advice me how to workaround this situation?
from IBM manuals I've learnt that it's not possible to PXE boot only from
one nic (at least, I've failed to discovery that kind of possibility).
···
On Friday, 19 February 2016 00:16:36 UTC+3, Александр Костырев wrote:
>
> Hello!
>
> I've got some problems with discovery and IBM servers (x3550 M5) with
> mulple nics.
> The IBM servers are configured as follows:
>
> > asu show BootOrder.BootOrder
> BootOrder.BootOrder="PXE Network=Hard Disk 0"
>
> The server has 4 nics that are connected to the same VLAN where foreman
> lives.
>
> If server is in build stage, everything works as expected: discovery image
> gets downloaded, server sends facts about itself to foreman, I can click
> autoprovision, server reboots, OS gets installed, then anaconda reboots the
> server and problem arise:
>
> server boots from NIC1 with PXE, as this MAC address is recognized by tftp
> the server gets
>
> LABEL local
> MENU LABEL (local)
> MENU DEFAULT
> LOCALBOOT 0
>
>
> and I've got 'Booting from local disk...' sign
> then follows
> PXE-M0F: Exiting Broadcom PXE ROM
>
> then IBM server (for some reason) tries to boot from the next NIC
> of course Foreman/TFTP knows nothing about this NIC (MAC-address) and
> discovery image gets downloaded and now I've new 'Discovered host',
> effectively server never boots into OS
>
> Please advice me how to workaround this situation?
>
> from IBM manuals I've learnt that it's not possible to PXE boot only from
> one nic (at least, I've failed to discovery that kind of possibility).
>
> thanks!
>
>
server still tries to acquire IP-address from dhcp.
So it still bothers me
···
On Friday, 19 February 2016 22:28:47 UTC+3, Александр Костырев wrote:
>
> RTFM
>
> http://kostyrev.blogspot.ru/2016/02/ibm-disable-pxebooting-on-nics.html
>
> On Friday, 19 February 2016 00:16:36 UTC+3, Александр Костырев wrote:
>>
>> Hello!
>>
>> I've got some problems with discovery and IBM servers (x3550 M5) with
>> mulple nics.
>> The IBM servers are configured as follows:
>>
>> > asu show BootOrder.BootOrder
>> BootOrder.BootOrder="PXE Network=Hard Disk 0"
>>
>> The server has 4 nics that are connected to the same VLAN where foreman
>> lives.
>>
>> If server is in build stage, everything works as expected: discovery
>> image gets downloaded, server sends facts about itself to foreman, I can
>> click autoprovision, server reboots, OS gets installed, then anaconda
>> reboots the server and problem arise:
>>
>> server boots from NIC1 with PXE, as this MAC address is recognized by
>> tftp the server gets
>>
>> LABEL local
>> MENU LABEL (local)
>> MENU DEFAULT
>> LOCALBOOT 0
>>
>>
>> and I've got 'Booting from local disk...' sign
>> then follows
>> PXE-M0F: Exiting Broadcom PXE ROM
>>
>> then IBM server (for some reason) tries to boot from the next NIC
>> of course Foreman/TFTP knows nothing about this NIC (MAC-address) and
>> discovery image gets downloaded and now I've new 'Discovered host',
>> effectively server never boots into OS
>>
>> Please advice me how to workaround this situation?
>>
>> from IBM manuals I've learnt that it's not possible to PXE boot only from
>> one nic (at least, I've failed to discovery that kind of possibility).
>>
>> thanks!
>>
>>
> asu show BroadcomGigabitEthernet*.LegacyBootProtocol
BroadcomGigabitEthernetBCM5719-40F2E9BA7038.LegacyBootProtocol=PXE
BroadcomGigabitEthernetBCM5719-40F2E9BA7039.LegacyBootProtocol=NONE
BroadcomGigabitEthernetBCM5719-40F2E9BA703A.LegacyBootProtocol=NONE
BroadcomGigabitEthernetBCM5719-40F2E9BA703B.LegacyBootProtocol=NONE
problem solved!
···
On Friday, 19 February 2016 22:54:09 UTC+3, Александр Костырев wrote:
>
> it turned out that even with
>
> PXE.NicPortPxeMode.2=Disabled
> PXE.NicPortPxeMode.3=Disabled
> PXE.NicPortPxeMode.4=Disabled
>
> server still tries to acquire IP-address from dhcp.
>
> So it still bothers me
>
> On Friday, 19 February 2016 22:28:47 UTC+3, Александр Костырев wrote:
>>
>> RTFM
>>
>> http://kostyrev.blogspot.ru/2016/02/ibm-disable-pxebooting-on-nics.html
>>
>> On Friday, 19 February 2016 00:16:36 UTC+3, Александр Костырев wrote:
>>>
>>> Hello!
>>>
>>> I've got some problems with discovery and IBM servers (x3550 M5) with
>>> mulple nics.
>>> The IBM servers are configured as follows:
>>>
>>> > asu show BootOrder.BootOrder
>>> BootOrder.BootOrder="PXE Network=Hard Disk 0"
>>>
>>> The server has 4 nics that are connected to the same VLAN where foreman
>>> lives.
>>>
>>> If server is in build stage, everything works as expected: discovery
>>> image gets downloaded, server sends facts about itself to foreman, I can
>>> click autoprovision, server reboots, OS gets installed, then anaconda
>>> reboots the server and problem arise:
>>>
>>> server boots from NIC1 with PXE, as this MAC address is recognized by
>>> tftp the server gets
>>>
>>> LABEL local
>>> MENU LABEL (local)
>>> MENU DEFAULT
>>> LOCALBOOT 0
>>>
>>>
>>> and I've got 'Booting from local disk...' sign
>>> then follows
>>> PXE-M0F: Exiting Broadcom PXE ROM
>>>
>>> then IBM server (for some reason) tries to boot from the next NIC
>>> of course Foreman/TFTP knows nothing about this NIC (MAC-address) and
>>> discovery image gets downloaded and now I've new 'Discovered host',
>>> effectively server never boots into OS
>>>
>>> Please advice me how to workaround this situation?
>>>
>>> from IBM manuals I've learnt that it's not possible to PXE boot only
>>> from one nic (at least, I've failed to discovery that kind of possibility).
>>>
>>> thanks!
>>>
>>>
